Related
STOCK LOLLIPOP ROM FOR HUAWEI Y5II-CUN L03
MEDIATEK 6735
You are not PERMITTED to share or mirror my ROM to other portals like Mega,Mediafire,ShareBiz,Dropbox, Box, etc..., (!!! without my permission !!!)
REMINDER:!!!You are not allowed to share my Rom via Videoportals like Youtube, Vimeo etc.. without my permission!!!.
Here are the following actions i took into this ROM :good:
DISCLAIMER
Your warranty is now void. I will not be responsible
for bricked android phones, dead sd cards,
or any happy ending with your device.
if you point that finger at me, i will laugh at you :v
CHANGELOG ROM ODOEX
Removed.
{ *libSwypeCore.so
*Huawei_Swype.apk
*Drive, Gmail2, Hangouts, Music, talkback, Videos, Youtube, Email. (Debloaded) :v
*Pre-loaded: music & pictures }
* Zipaling
* EXT4 Optimizing
* SQLLITE Optimizing
CHANGELOG ROM DEOEX
Removed
.{*libSwypeCore.so
*Huawei_Swype.apk
*Pre-loaded: music & pictures}
*Init. d "Support"
* Ode-oxed
* Zipaling
* Debloated
* Busybox
* EXT4 Optimizing
* SQLLITE Optimizing
* Custom Asserts
* Custom Debloat list support
* Sign zips
* AND OTHERS
TestedY5II- CUN-L03
NO WORKING FOR HUAWEI Y5 II CUN-L23,CUN-L21, CUN-L01
INSTALLATION PROCEDURE:
Thanks Beta testers
————————————— ☆ Instructions for installing a ROM ☆ —————————————
(TWRP)
1. Restart the phone in recovery mode (Power and Volume +)
2. Select Wipe option
3. Choose Advanced Wipe
4. Choose Dalvik Cache, cache, data (#opcional internal storage, system )
5. Swipe to wipe
6. Go Back and choose Install zip from SD External, select the file you downloaded in your SD and installation will begin, vibrate after installation, then give you reboot system.
wait up to 5 minutes until the cell starts with the system properly
7. Let the rom is properly seated about 10 minutes and restart again
(TWRP)
1. Reiniciar el celular en modo recovery (Encendido y Volumen +)
2. Elegir la opción Wipe
3. Elegir Advanced Wipe
4. Elegir Dalvik Cache, cache, data (#opcional internal storage, system)
5. Swipe to wipe
6. Go Back y elegir Install .zip from External SD, elegir el archivo que descargaron en su SD y la instalación comenzará, vibrara al terminar la instalacion, despues le dan reboot system.
esperen máximo 5 minutos hasta que su celular inicie con el sistema correctamente
7. Dejen que la rom se asiente correctamente unos 10 minutos y vuelvan a reiniciar
[/CENTER]
ROM ODEX :good:
DOWNLOAD:
https://www.androidfilehost.com/?fid=457095661767152943
ROM DEODEX
DOWNLOAD:
https://www.androidfilehost.com/?fid=529152257862718992
Credits/Thanks:
@SuperR. for amazing kitchen :fingers-crossed: :good:
pieroDLT, @bogdanwp @mangakame @veto64 for testing the ROM. :laugh:
HIT THANKS IF YOU LIKED IT. :laugh: :good: :fingers-crossed:
ROM OS Version: Built from stock 5.1.x Lollipop
ROM Kernel: Stock kernel
ROM Firmware Required: Stock Lollipop Android 5.1.x
Stable Release Date: 13/04/2017
gracias hermano probandolo
Thanks brother i was waiting for you , Proving him
hi guys, Did anyone test the rom?
Tried it on a Y5II CUN-L02 Philippine version. The ROM installed fine and most of the features worked except the SIM card was not detected.
finally 2 roms what i could install to a huawei CUN-L22,
unfortunately the dual-simcards do not work.
thanks
i got the sims working
this is what i did:
with twrp i installed this zip
Rom-stock.zip
https://myridia.com/downloads/huawei_cun-l22/Rom-stock.zip
but the sim card was not working,,
than i extracted the update.app from the huawai download stock rom
and flashed the system.iso via fastboot
the extractor and the original romzip you find there:
https://myridia.com/downloads/huawei_cun-l22/
Can work on cun-l22 ?
tested on cun l03
id tested on my cun l03 it doesnt work if you wipe sytem cache dalkv data an internal and you choose the deodexed one
im gonna try with the odexed one
same result with the deodexed one
ok i did tested the rom works perfectly cause my problem was a file called libmemtrack.so that i removed from the lib system so i decide to reinstall the whole package of update.app then put the twrp recovery and then delete the system folder completely so i did install the deodexed package and works smooth just one little detail the apn doesnt let me open thats the only thing that doesnt work the rest works perfectly
Hi, this rom can work with CUN-AL00?
for y6
any custom roms have to huawei y6 scc-u21?
Need help Cun-L01 sim not working and i cant find official rom for this model. Help i cant use my phone!
Can`t a flashable ril be created for Cun-L21 from official B115 Romanian rom ? Or please tell me a solution to the sim not recognized thing.
Marcii96 said:
Need help Cun-L01 sim not working and i cant find official rom for this model. Help i cant use my phone!
Click to expand...
Click to collapse
Marci , CUN-L01 firmware for you :
http://consumer.huawei.com/md/support/downloads/detail/index.htm?id=94085
bogdanwp said:
Marci , CUN-L01 firmware for you :
http://consumer.huawei.com/md/support/downloads/detail/index.htm?id=94085
Click to expand...
Click to collapse
How can i use update.app? I dont have stock recovery and cant install it..:/
Marcii96 said:
How can i use update.app? I dont have stock recovery and cant install it..:/
Click to expand...
Click to collapse
Do you have TWRP ? If yes , you use Huawei Update Extractor and extract system.img from the update.app. You connect the phone to usb and reboot to fastboot , go to adb folder on pc , copy system.img there , open a cmd and flash the system.img from there. I did the same , here a post from me :
https://forum.xda-developers.com/showpost.php?p=73799988&postcount=205
I have a CUN-L21 and i flashed the stock rom from this thread , everything was working fine except sim was not recognized , so i found a firmware compatible with my CUN-L21 and did like i told you above and now everything is working. I hope it works for you. Mind you , research around , i`m not that tech savvy. Not responsible if anything bad happens , it worked for me.
Rom Stock Emui 3.1 tested on CUN-L21 , confirmed everything working except sim not recognized. Please update original thread.
how to fix sim not recogdnized on cun l21 ?
hello friends, I have never counted on this device, sorry for answering alone, I have been busy for work and university tasks
file
hi anyone have scatter file for cun-l02 please
whats is better, odex or deodex?
What is Google’s Project Treble?
You should read here some Frequently Asked Questions (FAQ) thanks to Recognized Developer @phhusson
This is an index for (all) Treble Projects or also Generic System Image (GSI) list.
This is the known compatible device list.
This is a Guide to build Project Treble GSI ROMs from source
Motorola Z2 Force is NOT a Project Treble compatible device, but it IS a semi-compatible. This means that you can move toward Treble ROMs with some previous steps.
Moving from Lineage 15.1 toward Oreo Treble ROMs
1. Unlock your bootloader or, if it is already unlocked, you can, optionally, download and use a flashall solution to turn back to stock if necessary.
2. Flash and boot Lineage ROM 15.1. Here you have guides to do it. Better if you flash to both slots (changing between then via fastboot set_active other command. This is necessary to get boot and vendor partitions compatible with Treble images.
3. Backup everything you need (see step n.6 below).
4. Remove PINs, passwords, fingerprints.
Now you can follow the default flashing GSI procedures:
1. Download an Android 8.1 (Oreo) Treble system image (ARM 64 with partition type A/B in our case) and move it to phone sdcard (or external one).
2. Remove all PIN, password, fingerprint security and allow USB Debugging.
3. Uninstall Magisk and reboot the phone. Then reboot again into bootloader.
4. Boot (not flash) TWRP Treble (via fastboot boot <twrp.img file name>)
5. Flash the downloaded Treble system image.
6. Flash Open GApps (Platform ARM64, Android 8.1) (if the GSI image does not include them).
7. Factory reset (or wipe data, Dalvik and cache partitions). You'll lose all your data.
8. Boot the phone and set it up, allowing USB Debugging.
9. Boot TWRP image file and then flash zip file it to make it permanent.
10. Reboot into flashed TWRP (mandatory).
11. Flash Magisk and reboot.
Know issues - Oreo
1. So-called "Technicolor" bug when moving into or out dark mode, or when using Substratum themes, when icons and the screen got weird colors effects and stripes. Generally, you could boot into recovery and wipe Dalvik/Cache.
2. ViPER4Android not always compatible with Treble.
3. VoLTE.
Moving from Lineage 15.1 toward Pie Treble ROMs
1. Requirements: have an Oreo Treble ROM already running.
2. Download an Android 9.0 (Pie) Treble system image (ARM 64 with partition type A/B in our case) and move it to phone sdcard (or external one).
3. Remove all PIN, password, fingerprint security and allow USB Debugging.
4. Uninstall Magisk and reboot the phone. Then reboot again into bootloader.
5. If you do not have TWRP yet, flash TWRP image via fastboot flash <twrp.img file name>
6. Reboot into TWRP.
7. Flash the downloaded Treble system image.
8. Flash Open GApps (Platform ARM64, Android 9) (if the GSI image does not include them).
9. Check if vendor partition is mounted via TWRP. If not, mount it.
10. Flash POST-sGSI 3 zip file. More info here.
11. Reflash TWRP.
12. Factory reset (or wipe data, Dalvik and cache partitions). You'll lose all your data (not sdcard).
13. Boot the phone and set it up, allowing USB Debugging. Reboot into TWRP.
14. Flash Magisk and reboot.
Old method:
1-9: The same as above.
10. Flash POST-sGSI zip files -1- and -2-.
11. Flash the Permissiver zip.
12. Factory reset (or wipe data, Dalvik and cache partitions). You'll lose all your data (not sdcard).
13. Boot the phone and set it up, allowing USB Debugging. If you can't boot, return to TWRP, flash/sideload the FBE_Disabler zip and wipe data as stated here. In this last case, you'll lose all your data including sdcard.
14. Flash Magisk and reboot.
Know issues - Pie
1. Message on each boot: "Android System: There's an internal problem with your device. Contact your manufacturer for details". Solution proposed by @palbadi. In details, fix for vendor mismatch popup:
A. In a root file manager, backup both \vendor\build.prop and \system\build.prop files.
B. Open \system\build.prop original file with a root text editor. Copy the line with ro.build.fingerprint variable, for instance:
Code:
ro.build.fingerprint=Android/treble_arm64_bvN/phhgsi_arm64_ab:9/PQ1A.181105.017.A1/64:userdebug/test-keys
C. Open \vendor\build.prop original file with a root text editor. Find the the line with ro.build.fingerprint variable, for instance:
Code:
ro.vendor.build.fingerprint=motorola/nash/nash:8.0.0/OPXS27.109-34-10/5:user/release-keys
D. Paste the copied system variable over the vendor one (replace).
E. Save the \vendor\build.prop file.
F. Reboot.
2. ViPER4Android not always compatible with Treble.
3. VoLTE.
4. The combination of TWRP + Magisk could let you without WiFi. You can try not flashing TWRP in any steps above, just booting it: fastboot boot <twrp.file.name>.img
Moving from Lineage 16 toward Pie Treble ROMs
1. Requirements: have Lineage 16 (Pie) already running.
2. Download an Android 9.0 (Pie) Treble system image (ARM 64 with partition type A/B in our case) and move it to phone sdcard (or external one).
3. Remove all PIN, password, fingerprint security and allow USB Debugging.
4. Uninstall Magisk (if you have it) and reboot the phone. Then reboot again into bootloader.
5. If you do not have TWRP yet, flash TWRP image via fastboot flash <twrp.img file name>
6. Reboot into TWRP.
7. Flash the downloaded Treble system image.
8. Flash Open GApps (Platform ARM64, Android 9) (if the GSI image does not include them).
9. Factory reset (or wipe data, Dalvik and cache partitions). You'll lose all your data (not sdcard).
10. Boot the phone and set it up, allowing USB Debugging. Reboot into TWRP.
11. Flash Magisk and reboot.
Know issues - Pie
1. Message on each boot about Vendor is not up-to-date.
2. ViPER4Android not always compatible with Treble. There is a solution here.
3. VoLTE.
4. The combination of TWRP + Magisk could let you without WiFi. You can try not flashing TWRP in any steps above, just booting it: fastboot boot <twrp.file.name>.img
5. If anytime you lost Wi-Fi (or your Mac address become 02:00:00:00:00:00), see this post.
Support
Discord support channel.
XDA Treble-Enabled Device Questions and Answers.
XDA Treble-Enabled Device Guides, News, & Discussion.
Treble-Enabled ROMs Development.
Muchas gracias por tu apoyo, estaba buscando esta información después de ver los links en tu firma
Google translate
Thank you very much for your support, I was looking for this information after seeing the links in your signature
Thank you. I wish I'd seen this a few days ago, I was trying to get a treble gsi running, but had a hell of a time figuring out what I was doing wrong, turns out there were several thing. I do have one question though, you say as step 4 in moving towards pie to flash twrp. I'm assuming you mean just boot it and not flash? If my assumption is incorrect, which zip did you flash? As there isn't one for treble twrp.
asislife20 said:
Thank you. I wish I'd seen this a few days ago, I was trying to get a treble gsi running, but had a hell of a time figuring out what I was doing wrong, turns out there were several thing. I do have one question though, you say as step 4 in moving towards pie to flash twrp. I'm assuming you mean just boot it and not flash? If my assumption is incorrect, which zip did you flash? As there isn't one for treble twrp.
Click to expand...
Click to collapse
Only boot it from the TWRP that used for flash LineageOS
asislife20 said:
Thank you. I wish I'd seen this a few days ago, I was trying to get a treble gsi running, but had a hell of a time figuring out what I was doing wrong, turns out there were several thing. I do have one question though, you say as step 4 in moving towards pie to flash twrp. I'm assuming you mean just boot it and not flash? If my assumption is incorrect, which zip did you flash? As there isn't one for treble twrp.
Click to expand...
Click to collapse
I have changed the guide and added link. Is it clear now? Thanks.
omnismart said:
Muchas gracias por tu apoyo, estaba buscando esta información después de ver los links en tu firma
Google translate
Thank you very much for your support, I was looking for this information after seeing the links in your signature
Click to expand...
Click to collapse
hola podrias ayudarme a hacer esto en mi dispositivo por favor...
AlucardMemnoch said:
hola podrias ayudarme a hacer esto en mi dispositivo por favor...
Click to expand...
Click to collapse
Aún no me muevo a esta rom, he estado un poco ocupado y requiere respaldar toda la memoria interna para evitar problemas, eso me implica depurar whatsapp.
Revisa el siguiente enlace, tal vez y te ayude un poco por si tienes algún problema y quieras volver a stock.
I still do not move to this rom, I've been a bit busy and requires backup all internal memory to avoid problems, that means I debug whatsapp.
Check the [URL = "https://www.htcmania.com/showpost.php?p=29253595&postcount=2"] next link [/ URL], maybe and it will help you a bit in case you have a problem and you want to go back to stock
Flashed PE 9 img (PE-AB-2018-09-20) instead of 8 over lineage-15.1-20181009-nightly-nash-signed.zip by mistake.... and it happened to be ok ))
So far everything works fine ....
Maybe it's time to optimize Guide?
pakhan8 said:
Maybe it's time to optimize Guide?
Click to expand...
Click to collapse
In which point?
Technical said:
In which point?
Click to expand...
Click to collapse
I think he means the need to first install an 8.1 GSI rom before doing a 9 (Pie) GSI?
CykloneFij said:
I think he means the need to first install an 8.1 GSI rom before doing a 9 (Pie) GSI?
Click to expand...
Click to collapse
Well, I never said that. Anyway, I've updated the guide to make it clear the movement from Lineage 15.1 toward Oreo or Pie.
Does Moto Mods work?
Hello, I would like to know if Moto Mods work with this project. Thank you in advance for your attention.
Pedro Gomes said:
Hello, I would like to know if Moto Mods work with this project. Thank you in advance for your attention.
Click to expand...
Click to collapse
Yes, in theory, all mods work. Some controls and apps (and their functions) could not, though.
You can always test and revert to stock if you want
Technical said:
Yes, in theory, all mods work. Some controls and apps (and their functions) could not, though.
You can always test and revert to stock if you want
Click to expand...
Click to collapse
Okay, thanks for the reply. The warranty on my z2 force is over, so I'll risk installing it following your tutorial. The z2 force is more complicated, but with a little patience I think it will work ...
Latest magisk 17.1 leads to "no wifi and no mobile internet" on pie PixelExperience 9 img (PE-AB-2018-09-20)
Does anybody know how to solve it?
did you get the magisk wifi issue sorted out?
McRoberts said:
did you get the magisk wifi issue sorted out?
Click to expand...
Click to collapse
No. I've tested Magisk v17, beta and also older versions (16.7).
anyone tried and make it work successfully with this guide to follow ?
i check all the replies but no one seem to come back and claim it work .
if you are the one pls let me know , thank you.
fisummer said:
anyone tried and make it work successfully with this guide to follow ?
i check all the replies but no one seem to come back and claim it work .
if you are the one pls let me know , thank you.
Click to expand...
Click to collapse
Yes. it works
mattlowry said:
Yes. it works
Click to expand...
Click to collapse
thanks bro,i really appreciated for your comfirmation.
Hello there. Hope this helps!
FIRST OF ALL, this WILL VOID your waranty. Read the steps BEFORE doing anything.
WEWEWEWE lessgooo:
UNLOCK BOOTLOADER: It's not "easy" at all (You'll have to open your tab).
Go to device info on tab settings.
Press compilation number for several times until "you're a dev" message appears (It'll prolly ask your pattern/password to continue).
Go to dev options and enable OEM unlocking.
Shut down the tab.
Download PotatoNV sofware from here. (Credits to mashed-potatoes)
Download minimal adb and fastboot from here.
Prepare your environment:
Open your tablet
Grab a clip or a cable
Keep your cool
Follow the steps shown here.
Here you have an image of where the testpoint is.
FLASH TWRP INTO THE TAB:
Follow CAREFULLY this steps:
Shut down the tab
Connect the tab to the PC and hold vol- & pwr button.
Now it'll appear a white screen with some text. If it appears "OEM unlock" in green, then everything's fine. IF NOT, follow unlock bootloader steps again. Then try rebooting into fastboot mode again (vol- & pwr).
Download most compatible TWRP from here.
Open Minimal ADB and Fastboot and write this:
"fastboot flash recovery_ramdisk path_of_twrp.img" (Move twrp to minimal adb folder for no complications)
It should appear everything OK.
Type "fastboot reboot"
Fastly disconnect the tab from PC and hold vol+ & pwr button before Huawei logo appears (if it appears, just do a hard reboot (hold pwr button) and try again.
You're now booting into TWRP!
DOWNLOAD RESOURCES AND PREPARE YOURSELF FOR THE PARTY (This is the most important step)
Download data decrypter from attached files below the post (decryptemui8.zip)
Download ROM from here (credits: @DarkJoker360 ) DarkJoker's Post here
(OPTIONAL) Download Nikgapps from here
ONCE in TWRP, flash decrypter (decryptemui8.zip) on "install" option
Go to wipe>advanced wipe and select: dalvink/art cache, cache, data, internal storage and system.
Return to main menu and go to reboot>reboot bootloader
Connect your device to the PC (while rebooting) and wait to be into bootloader (white screen with a droid).
Open minimal adb and fastboot tools and type:
"fastboot flash system path_of_rom.img" (it MUST be decompressed to an .img file)
Wait...
Once it has finished, type: "fastboot reboot"
DONE! you have LOS18.1 now!
(optional gapps on next step)
GAPPS INSTALLATION ON MEDIAPAD T5 IT'S DIFFERENT FROM OTHER PHONES!!!!!!!
FOLLOW THIS STEPS VERY CAREFULLY!!!
Move gapps zip and add-ons to an sd card
Reboot to TWRP
Go to mount>select system. Return to main menu
Go to advanced>file manager
Go to system>system_ext>apex.
Once in apex, enter on vndk27 and vndk28 and delete them (once in vndk27/vndk28 folder, in the bottom-right corner, it'll appear a symbol with a folder with a "tick" on it. Just tap it)
LEAVE ONLY VNDK CURRENT AND VNDK26 FOLDERS (and the rest obviously. Just delete 27/28)
Return to main menu
Go to wipe>advanced wipe. Select system and tap on repair/resize partition (slide to continue)
Then go to main menu>install and install gapps as usual (sliding lol)
FOR ROOT METHOD:
Just follow the steps shown on the main post.
WORKING ROOT CAN ONLY BE DONE WITH MAGISK METHOD (installing apk for using preroot MUST perform random SystemUI reboots ; ).
---------CREDITS---------
Amazing rom: @DarkJoker360
HI6250 support group here.
JOIN T5 SUPPORT GROUP CLICKING HERE
Hey,
I've tried this, but cant get it too boot.
My device is Huawei AGS2-W09.
I've unlocked the bootloader/installed twrp, flashed the decrypter etc.
Then after i do fastboot reboot, it loads up the Lineage OS splash/loading screen, but stays on that for about 10 mins, then reboots and goes to Huawei eRecovery screen.
I've tried repeating the steps, in case it didn't flash properly.
Any ideas?
hobbitjack said:
Hey,
I've tried this, but cant get it too boot.
My device is Huawei AGS2-W09.
I've unlocked the bootloader/installed twrp, flashed the decrypter etc.
Then after i do fastboot reboot, it loads up the Lineage OS splash/loading screen, but stays on that for about 10 mins, then reboots and goes to Huawei eRecovery screen.
I've tried repeating the steps, in case it didn't flash properly.
Any ideas?
Click to expand...
Click to collapse
For those facing problems:
PM Me via telegram @Fosanz
JOIN T5 SUPPORT GROUP
I will post the solutions here on the main post as problems appear
Hello,
I have tried too, and I have had exactly the same problem. I couldn’t boot into system.
I followed all the steps as described. I have AGS2-W09 and I was on Lineage 16.0.
Now I’m back again on Lineage 16.0, waiting if there is a solution.
borja113 said:
Hello,
I have tried too, and I have had exactly the same problem. I couldn’t boot into system.
I followed all the steps as described. I have AGS2-W09 and I was on Lineage 16.0.
Now I’m back again on Lineage 16.0, waiting if there is a solution.
Click to expand...
Click to collapse
Recover system with eRecovery and follow steps again. Instructions modified. Making a factory reset is not neccesary
@Fosanz can you share how's the performance of LOS18.1 on MediaPad T5
what is working and what not?
how is the battery on LOS18.1?
my battery sucked on LOS16, hardly 3 hours
kamilmirza said:
@Fosanz can you share how's the performance of LOS18.1 on MediaPad T5
what is working and what not?
how is the battery on LOS18.1?
my battery sucked on LOS16, hardly 3 hours
Click to expand...
Click to collapse
Everything works. No face unlock as LOS16. Animations are simply beautiful, very optimized. Here you can pass safetyNet with some easy tweaks. Battery it's amazing. 1% in 6h deep sleep. While using it (6-7 hours of gaming, instagram, telegram, etc.) battery drain it's amazing. I'll share some screenshots on the telegram group
Fosanz said:
Recover system with eRecovery and follow steps again. Instructions modified. Making a factory reset is not neccesary
Click to expand...
Click to collapse
Follow steps again….Yes, but what will change if I do it again. Same tablet, same instructions. I would like to know first what was wrong. I want to avoid spending hours trying and after that restoring, until I’m sure it will work for me.
Anybody else managed to install LOS18 ? If yes please describe how you did it and from which environment you’re coming.
Does it work for AGS2-L03?
Or this ROM only work for some Variant?
I think mine only has 16GB storage and 2GB RAM.
Also the eRecovery, does it only update or can it flash the full image?
borja113 said:
Follow steps again….Yes, but what will change if I do it again. Same tablet, same instructions. I would like to know first what was wrong. I want to avoid spending hours trying and after that restoring, until I’m sure it will work for me.
Anybody else managed to install LOS18 ? If yes please describe how you did it and from which environment you’re coming.
Click to expand...
Click to collapse
Join support group duh.
theflyingsquirrel said:
Does it work for AGS2-L03?
Or this ROM only work for some Variant?
I think mine only has 16GB storage and 2GB RAM.
Also the eRecovery, does it only update or can it flash the full image?
Click to expand...
Click to collapse
Yeah it should work. Same processor but different amount of Ram. Try it out! Join t5 (Bottom of the main post) support group if you're facing problems!
Fosanz said:
Join support group duh.
Click to expand...
Click to collapse
OK, so, if anybody wants to try to install L0S18, go right away and join Telegram group of this member, beacuse the suport is not provided here (entendi bien?). What is the purpose of this forum then?
borja113 said:
OK, so, if anybody wants to try to install L0S18, go right away and join Telegram group of this member, beacuse the suport is not provided here (entendi bien?). What is the purpose of this forum then?
Click to expand...
Click to collapse
Debido a que tú pregunta no tiene nada que ver con la instalación, sino que estás preguntando por los cambios hechos, no voy a empezar ni una discusión ni una conversación por un hilo con tal de evitar overflooding de mensajes. Así que por favor y si no te molesta, te asistiré por Telegram, de manera que el problema que tú tengas pueda ser solucionado lo más rápido posible para yo poder modificar lo que pueda estar mal en el hilo principal y así no hacer que la gente que quiere instalar Lineage solo mirando el thread principal (que lo hace la gran mayoría) tenga el mismo error que tú y vuelva a preguntarme lo mismo.
Y si, hay gente que ha logrado instalar Lineage os 18.1 correctamente y gracias a que se unió al grupo pude modificar partes de la instalación que eran cruciales para otros modelos de mediapadt5.
Un saludo
Has anyone else successfully installed LO18? I tried going from LO16 to 18 and this didn't work for me. I'm gonna give it a second try when I have more time on my hands. Maybe I'll have more luck going from EMUI to LO18.
Firts of all thanks for the efford you guys spend into a working solution for our device. Second I apology for not joining Telegram group, I simply don't use it.
Device: AGS2-W09 - came from stock
Yesterday the device was successfully booting into LOS18. Might have to do with the new Huawei-Decrypt file. Before I was also getting a boot loop.
LOS is working quite well as I can tell until now.
Aditionally installed apps (sideloaded or alternative store) are freezing after a while. I suspected a dependency to gapps. The apps I tested Brave Browser, Aurora Store, VLC.
Tried to install Nikgapps (core and then basic) but it didn't work. TWRP console tells me installation was successful, but no gapps appear after the boot. I tired BiTGApps package and that was successful.
Additionally installed apps still freezing after a while.
korale said:
Firts of all thanks for the efford you guys spend into a working solution for our device. Second I apology for not joining Telegram group, I simply don't use it.
Device: AGS2-W09 - came from stock
Yesterday the device was successfully booting into LOS18. Might have to do with the new Huawei-Decrypt file. Before I was also getting a boot loop.
LOS is working quite well as I can tell until now.
Aditionally installed apps (sideloaded or alternative store) are freezing after a while. I suspected a dependency to gapps. The apps I tested Brave Browser, Aurora Store, VLC.
Tried to install Nikgapps (core and then basic) but it didn't work. TWRP console tells me installation was successful, but no gapps appear after the boot. I tired BiTGApps package and that was successful.
Additionally installed apps still freezing after a while.
Click to expand...
Click to collapse
Hey Hi!.
Glad to hear you booted! The problem was at the decrypter.
Also, a lot of people are having trouble installing NikGapps. It seems that the package is "wrong" in some way for our device. Reported the issue. Until July 2021 update, devices go very slow. Hopefully, there's a way to fix it .
adb root && adb remount /system
adb push local.prop /system/product/etc/prop/local.prop
Credits to @DarkJoker360
Extracted from HI6250 support group
local.prop file is on "attached files"
I finally had some time to try installing LineageOS 18.1 again. Works beautifully, Magisk and everything. Make you sure you go straight from EMUI to LineageOS 18.1, it doesn't work if you switch from Lineage 16 to 18.1.
In my case I needed to open to the tablet again after doing a Huawei system restore back to EMUI, it relocked my tablet, just be aware of that, that was mildly annoying.
Also make sure you use the Magisk mentioned in the thread if you want root. After installing, don't let Magisk update itself from within the app, updating the ramdisk will remove TWRP and the system will bootloop until you reflash TWRP. It will boot again normally with your stuff still intact after the TWRP reflash.
Been playing around with it for a bit, doesn't seem to have some of the annoying LineageOS 16 bugs. It has full screen navigation controls which I really wanted and was missing earlier. Android 11 (Juli 2021 security update), MicroG is working, seems responsive and smooth. Great! I am very happy with this.
Thanks and special shout out to all the people making this possible, y'all are amazing.
Just as a hint. I don't think you need to open your tablet again.
Keep the unlock code generated by PotatoNV save. In my case I relocked and unlocked the tablet several times with the unlock code without the testpont method.
hi, i just got to the part that i have to make a img file out of the rom zip file....
help pls
can i flash the other img files on the site? (the 650 mb files)
can i flash the new rom from twrp?
thx
kamilmirza said:
@Fosanz can you share how's the performance of LOS18.1 on MediaPad T5
what is working and what not?
how is the battery on LOS18.1?
my battery sucked on LOS16, hardly 3 hours
Click to expand...
Click to collapse
Fosanz said:
Hello there. Hope this helps!
FIRST OF ALL, this WILL VOID your waranty. Read the steps BEFORE doing anything.
WEWEWEWE lessgooo:
UNLOCK BOOTLOADER: It's not "easy" at all (You'll have to open your tab).
Go to device info on tab settings.
Press compilation number for several times until "you're a dev" message appears (It'll prolly ask your pattern/password to continue).
Go to dev options and enable OEM unlocking.
Shut down the tab.
Download PotatoNV sofware from here. (Credits to mashed-potatoes)
Download minimal adb and fastboot from here.
Prepare your environment:
Open your tablet
Grab a clip or a cable
Keep your cool
Follow the steps shown here.
Here you have an image of where the testpoint is.
FLASH TWRP INTO THE TAB:
Follow CAREFULLY this steps:
Shut down the tab
Connect the tab to the PC and hold vol- & pwr button.
Now it'll appear a white screen with some text. If it appears "OEM unlock" in green, then everything's fine. IF NOT, follow unlock bootloader steps again. Then try rebooting into fastboot mode again (vol- & pwr).
Download most compatible TWRP from here.
Open Minimal ADB and Fastboot and write this:
"fastboot flash recovery_ramdisk path_of_twrp.img" (Move twrp to minimal adb folder for no complications)
It should appear everything OK.
Type "fastboot reboot"
Fastly disconnect the tab from PC and hold vol+ & pwr button before Huawei logo appears (if it appears, just do a hard reboot (hold pwr button) and try again.
You're now booting into TWRP!
DOWNLOAD RESOURCES AND PREPARE YOURSELF FOR THE PARTY (This is the most important step)
Download data decrypter from attached files below the post (decryptemui8.zip)
Download ROM from here (credits: @DarkJoker360 ) DarkJoker's Post here
(OPTIONAL) Download Nikgapps from here
ONCE in TWRP, flash decrypter (decryptemui8.zip) on "install" option
Go to wipe>advanced wipe and select: dalvink/art cache, cache, data, internal storage and system.
Return to main menu and go to reboot>reboot bootloader
Connect your device to the PC (while rebooting) and wait to be into bootloader (white screen with a droid).
Open minimal adb and fastboot tools and type:
"fastboot flash system path_of_rom.img" (it MUST be decompressed to an .img file)
Wait...
Once it has finished, type: "fastboot reboot"
DONE! you have LOS18.1 now!
(optional gapps on next step)
GAPPS INSTALLATION ON MEDIAPAD T5 IT'S DIFFERENT FROM OTHER PHONES!!!!!!!
FOLLOW THIS STEPS VERY CAREFULLY!!!
Move gapps zip and add-ons to an sd card
Reboot to TWRP
Go to mount>select system. Return to main menu
Go to advanced>file manager
Go to system>system_ext>apex.
Once in apex, enter on vndk27 and vndk28 and delete them (once in vndk27/vndk28 folder, in the bottom-right corner, it'll appear a symbol with a folder with a "tick" on it. Just tap it)
LEAVE ONLY VNDK CURRENT AND VNDK26 FOLDERS (and the rest obviously. Just delete 27/28)
Return to main menu
Go to wipe>advanced wipe. Select system and tap on repair/resize partition (slide to continue)
Then go to main menu>install and install gapps as usual (sliding lol)
FOR ROOT METHOD:
Just follow the steps shown on the main post.
WORKING ROOT CAN ONLY BE DONE WITH MAGISK METHOD (installing apk for using preroot MUST perform random SystemUI reboots ; ).
---------CREDITS---------
Amazing rom: @DarkJoker360
HI6250 support group here.
JOIN T5 SUPPORT GROUP CLICKING HERE
Click to expand...
Click to collapse
Thx alot for the guide and the help in instegram.
It's working for me with my mediapad t5.
Some things that are still a bit dissfunction:
Mobile network dissconnect every 30 seconds and reconnect.
No support for sd card (can't format it in the tablet).
Thanks again,
Ilan
Greetings.
I would like to know what would be the best option to root this terminal. I'm thinking of switching to the Miuimix rom but maybe someone can advise me on a less intrusive way. I want to do it mainly so that I can make complete backups, with the applications and their data; and that you do not have to be with a little notebook writing down passwords.
Thank you all very much in advance.
root is root, rom is rom...
for rooting you must enable magisk after fashing your rom (miui, arrow, lineage... is not important, is the same )
i raccomend flashing last version of magisk
after system boot, from magisk manager enable zygist and flash module safety 2.2.1 for passing safety net
I was commenting about the Miuimix ROM because it is the one that practically comes pre-rooted and in two steps you already have it; but I don't like its appearance very much; I am also very comfortable with xiaomi.eu even if it is a highly criticized rom.
How do I flash magisk? There is no recovery that works well on Android 12.
Is there any tutorial to do it?
I've been searching the forum and what little there is on the subject doesn't work for everyone.
Thanks for everything again.
gintony said:
How do I flash magisk? There is no recovery that works well on Android 12.
Is there any tutorial to do it?
I've been searching the forum and what little there is on the subject doesn't work for everyone.
Thanks for everything again.
Click to expand...
Click to collapse
recovery for a12 work, you must flash last twrp... only problem with this is that your internal memory is not visible... you must have all on external sd for flashing.. rom, magisk etc.. but is simple... usually when you enter in recovery select external sd, flash rom, flash magisk (magisk is .apk, rename.zip before flashing), format and reboot..
aleMarvel said:
la recuperación para el trabajo a12, debe flashear el último twrp ... el único problema con esto es que su memoria interna no está visible ... debe tener todo en sd externo para flashear ... rom, magisk, etc. pero es simple... Por lo general, cuando ingrese a la recuperación, seleccione sd externa, flash rom, flash magisk (magisk es .apk, rename.zip antes de flashear), formatee y reinthanks
Click to expand...
Click to collapse
Gracias por tu respuesta.
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about this recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
Working features:
* Flashing of zip and img files.
* Backup and restore.
* MTP, ADB, FastbootD.
* ADB Sideload
* CPU Temperature, Battery percentage, Clock.
* Etc...
Installation
1) Download the files: twrp tar, vbmeta_disabled tar and magisk apk
2) Open Odin in your pc.
3) Boot to download mode
4) Load the recovery tar into AP slot and the vbmeta_disabled tar into BL slot and click "Start".
5) As soon as the screen turns off, release all keys and press power + volume up keys till you boot into twrp (the phone has to be connected to PC all the time).
6) Go to Wipe > Format Data > type yes
7) Reboot to recovery.
8) Flash Magisk.
9) Reboot to system, Enjoy.
Download
TWRP and vbmeta_disabled: here
Magisk: here
Thanks
TWRP team
afaneh92
Sources:
Device tree
TWRP recovery
nice
lnwbas569 said:
Is there has 0mb internal storage issue?
Click to expand...
Click to collapse
That's probably because your storage is encrypted, read steps 4 and 5.
lnwbas569 said:
Nvm I got bootloop after follow method 2
My device : A336E
Basebrand A336EDXU4BVKB
Click to expand...
Click to collapse
what did you do exactly? and what is bootlooping, the twrp or the system?
lnwbas569 said:
After I had done in odin and did terminal instruction by type multidisabler, then format data and reboot into recovery again.
Once its done, I tried to boot into system then got bootloop
Click to expand...
Click to collapse
Okay, try to flash stock "AP" file and read the instructions again, but this time without multidisabler step. May fix your issue
lnwbas569 said:
Have tried, I'm sorry but still even got bootloop. I cannot boot into system
Click to expand...
Click to collapse
The problem is that you formatted data, don't format it, I've updated instructions
What is vbmeta for?
lnwbas569 said:
I wasn't format anything in recovery but still can't boot into system
Click to expand...
Click to collapse
Are you sure? Some guy just pmed me on telegram and he booted to system perfectly
in the A336M variant I got bootlopp when doing format data the system does not start, then I installed recovery stock by odin and it started perfectly, then I reinstalled twrp without formatting data and the system started fine but in vain because nothing can be done everything Flashing gives me a fail, hopefully it will be corrected in the A336M variant
lnwbas569 said:
For me, It doesnt boot into system since I haven't format data via twrp or even reinstall stock AP.tar over then reinstall twrp again. Seems no solved for me recently
Click to expand...
Click to collapse
you can install twrp without formatting data and the system starts but it is of no use since the storage is encrypted, You need to do yes or yes format data to decrypt, but there is the problem that the system does not start after doing format data
Hello everybody.
I got SM-336B phone recently, the system has been upgraded to android 13.
Bootloader is unlocked yet; I cleared user data several times, but after installing TWRP I have the same bootloop problem.
The messages says "can't mount /data partition"
I've tried also to flash SuperSU.zip, with no result, and the same error.
Anyone has a solution for mount error?
Thanks.
Beatnik71 said:
Hello everybody.
I got SM-336B phone recently, the system has been upgraded to android 13.
Bootloader is unlocked yet; I cleared user data several times, but after installing TWRP I have the same bootloop problem.
The messages says "can't mount /data partition"
I've tried also to flash SuperSU.zip, with no result, and the same error.
Anyone has a solution for mount error?
Thanks.
Click to expand...
Click to collapse
I think we all have the same problem friend, I think the developer will correct it soon
lnwbas569 said:
I saw the multidisabler in twrp which said some kind of " multidisabler android version: 12" while im installing this twrp on android 13 device as well. Hope this maybe to be solved soon cause I wanna flash custom stuffs in twrp so bad xd.
Click to expand...
Click to collapse
yes exactly but the twrp works on android 12 and 13, I also want to do things on my device but I don't know when they will correct the twrp
I was curious about the multidisabler script you mentioned, can the people getting boot loops with "can't mount /data partition" try to post system logs?
I see multidiabler runs a sed script on fstab to disable encryption, is the bug here? Seems likely.
peggeddroid said:
I was curious about the multidisabler script you mentioned, can the people getting boot loops with "can't mount /data partition" try to post system logs?
I see multidiabler runs a sed script on fstab to disable encryption, is the bug here? Seems likely.
Click to expand...
Click to collapse
multidisabler doesn't fix anything, bootloop still the same try millions of things but system still won't boot
Gollo99 said:
multidisabler doesn't fix anything, bootloop still the same try millions of things but system still won't boot
Click to expand...
Click to collapse
There's a HOWTO on using getting system logs with adb:
How to take system logcats
Since you're all getting messages indicating it's a mount error, I read through the multidisabler script source and I kind of suspect there's an error where multidisabler modifies the fstab file.
maybe line 109
peggeddroid said:
There's a HOWTO on using getting system logs with adb:
How to take system logcats
Since you're all getting messages indicating it's a mount error, I read through the multidisabler script source and I kind of suspect there's an error where multidisabler modifies the fstab file.
maybe line 109
Click to expand...
Click to collapse
yes perhaps, for example in mediatek and ext4 you have to modify fstab for the system to start, but in the case of A33 f2fs partition I don't know how fstab works
Gollo99 said:
yes perhaps, for example in mediatek and ext4 you have to modify fstab for the system to start, but in the case of A33 f2fs partition I don't know how fstab works
Click to expand...
Click to collapse
Oh that's interesting, samsung switched to f2fs for their in-house chips.
multidisabler is I gather a first time run script that turns off a bunch of options that aren't or can't be supported on a 3rd party ROM without vendor magic. The line that deals with fstab is a sed script that modifies the fstab to turn off full disk encryption, it might be wrecking fstab and preventing mounts.
But this is a new filesystem. Is this TWRP distro being compiled with a f2fs module anyway?
Looks like there's f2fs support in the base distribution. Looks like me-cafebabe has done the recent work on encrypted filesystem support in TWRP and has worked on some older samsung profiles. So this is probably just some simple questions and debugging.
peggeddroid said:
Oh that's interesting, samsung switched to f2fs for their in-house chips.
multidisabler is I gather a first time run script that turns off a bunch of options that aren't or can't be supported on a 3rd party ROM without vendor magic. The line that deals with fstab is a sed script that modifies the fstab to turn off full disk encryption, it might be wrecking fstab and preventing mounts.
But this is a new filesystem. Is this TWRP distro being compiled with a f2fs module anyway?
Looks like there's f2fs support in the base distribution. Looks like me-cafebabe has done the recent work on encrypted filesystem support in TWRP and has worked on some older samsung profiles. So this is probably just some simple questions and debugging.
Click to expand...
Click to collapse
yes, samsung changed the partitions but there are still many questions and few answers, let's hope this is solved quickly and we can get twrp 100% functional
Gabriel260BR said:
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about this recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
Working features:
* Flashing of zip and img files.
* Backup and restore.
* MTP, ADB, FastbootD.
* CPU Temperature, Battery percentage, Clock.
* Etc...
Errores actuales:
* Descifrado
* carga lateral adb
Instalación
Método 1
1) Si ya tiene twrp en su teléfono, extraiga recovery.img del archivo tar usando Zarchiver o Winrar.
2) Reinicie su teléfono e inicie la recuperación.
3) Flashear el recovery.img como "recuperación"
4) Finalmente, reinicie la recuperación para disfrutar de la nueva recuperación de twrp
Método 2
1) Si está instalando una recuperación personalizada por primera vez, abra Odin en su PC. Descargue el último archivo de recuperación adjunto a continuación. Inicie su teléfono en modo de descarga.
2) Flashee el archivo tar que descargó en la ranura AP.
3) Tan pronto como la pantalla se apague, suelte todas las teclas y presione las teclas de encendido + subir volumen hasta que inicie twrp (el teléfono debe estar conectado a la PC todo el tiempo).
4) Ahora tienes twrp
Advertencia: no formatee los datos, por alguna razón el sistema se reiniciará si lo hace... Estoy buscando una solución
Descargar
El archivo se adjunta a continuación
Gracias
equipo TWRP
afaneh92
Guillermo por probar el recovery
Fuentes:
Árbol de dispositivos
Recuperación TWRP
Click to expand...
Click to collapse
Puedo instalarlo desde la app de twrp