Related
Hi everyone, I finally got a little time to put together a guide to flashing stuff on the LeEco Le Pro 3 X727.
This phone comes with an unlockable bootloader out of the box, but we found some ways to get around that.
This guide will help anyone with a new X727 unlock the bootloader, install TWRP and root it.
First, I'd like to give huge props to @dr4stic for his excellent work on making it easier to unlock the phone, and for helping me get back to the US ROM after installing the Chinese rom.
On to the flashing...
If you want to take the long way around, this was the first method used for unlocking the bootloader:
First method is using the stock Chinese ROM & renaming it update.zip, place it in the root directory then use the Update app (or in settings) to select that update, then let it do its thing. It takes a while to boot back up so be patient.
Stock Chinese ROM: https://www.androidfilehost.com/?fid=529152257862681546
Once the Chinese ROM is installed and booted up, enable Developer Options, make sure OEM Unlocking is turned on, then enable USB Debugging.
For these next steps, I'm quoting @dr4stic:
Have ADB/Fasboot tools on your computer (I am not helping you here, it you're lucky, maybe your friends will help)
Make sure you have enabled the developer tools, turned on USB debugging, and authorized your computer on your device (again, I'm not helping with that)
Make sure adb can see your device when you run "adb devices"
Run "adb reboot bootloader"
Run "fastboot devices" to make sure you see your device
Run "fastboot oem unlock-go" to unlock your device temporarily
Run "fastboot oem device-info" to verify unlock status
Your bootloader is now permanently unlocked (well, until you re-lock it on purpose).
The second, and much shorter method, is outlined in @dr4stic's thread here: http://forum.xda-developers.com/le-pro3/development/x727-model-persistent-bootloader-unlock-t3500388
Once your bootloader is unlocked, you'll want to install TWRP.
Here are a couple options for TWRP:
https://www.androidfilehost.com/?fid=529152257862668751 (Chinese version)
https://www.androidfilehost.com/?fid=385035244224398544 (GrossoShop version)
Download either of those (or both if you want to try both), extract them and place the .img file(s) into the folder your ADB & Fastboot files are. To make the flashing easier, rename the twrp files to twrp.img. If you still have your command prompt window open, great! If not, open one again.
Now:
Run "fastboot flash recovery twrp.img" (or whatever the twrp image filename is on your computer) to flash TWRP.
When flashing is complete, reboot into TWRP by pressing and holding Power Button and Volume Up Button at the same time and holding until you see the TWRP splash screen.
If TWRP boots up in Chinese, tap the big button on the lower right to open the language settings and choose the language you can understand.
Alright, now you have an unlocked bootloader and custom recovery installed. Your world has opened up a little bit more
The main problem with installing the stock Chinese ROM is that it does not have Google Play and there is no band 12 support (at least for T-Mobile), but at least bands 2 & 4 still work.
It's easy enough to find methods to get that installed, but I tried the GrossoShop ROM which is a very good ROM, but if you must have band 12, you'll need to read down a little farther.
Link to GrossoShop ROM: https://www.androidfilehost.com/?fid=529152257862686304
Okay, if you chose to use the long route and installed the Chinese ROM, you can still get back to the full US version, complete with all LTE bands. dr4stic is responsible for this gem, and was my way back to US ROMdom.
To go from Chinese or Custom ROM back to Stock US version:
The file is located in his Android File Host space here: https://www.androidfilehost.com/?fid=601275311581036717
It's a little tricky to install, so follow these steps:
1. Enter TWRP and from Advanced Wipe, wipe Dalvick/ART Cache, Cache, System and Data (Leave Internal Storage untouched if that's where you copied the new ROM zip).
2. Install CN5.8.018s-to-US5.8.019s.zip
3. DO NOT REBOOT DIRECTLY AFTER FLASHING (Phone just vibrates forever if you reboot directly after flashing)
4. Go back to TWRP Home, then tap Reboot, then tap System.
The phone should reboot after that, and it might take a while. Then follow the setup process as you normally would and it should go through the Google setup as well.
To install root, I use SuperSU. Sometimes it's kinda hard to find the most up to date version, so I'll post the latest one that I have: https://www.androidfilehost.com/?fid=457095661767120474
There's probably a newer version already, but I haven't looked.
Simply download and flash that file in TWRP, reboot and you're rooted. Easy peasy.
To flash only the US modem to restore band 12 on any ROM:
Download: https://www.androidfilehost.com/?fid=601300970940399635
Extract the zip file and place it in your adb & fastboot folder.
From your abd & fastboot files folder (with the modem image in there too) open a command prompt and run
fastboot flash modem modem-5.8.019s.img
Then reboot your phone.
Keep this file handy because you'll need it every time you flash a ROM that doesn't have a US modem.
With the methods listed above, you should now be able to take a new LeEco Le Pro 3 X727 and unlock the bootloader, install TWRP, flash whatever ROMs you want, and restore US modem.
Again, big big thanks to @dr4stic to getting us to this point for the easy unlock option AND big thanks to all of you folks here in the forums for all of you suggestions, efforts and enthusiasm!
I imagine there will be some refinements and/or corrections to this guide as questions and suggestions come up, so please, if you see something in here that is wrong or unclear, please let me know.
Thank you for the good guide.
well done. Please keep it updated...
suhridkhan said:
well done. Please keep it updated...
Click to expand...
Click to collapse
lilila said:
Thank you for the good guide.
Click to expand...
Click to collapse
Thank you and you're welcome. I'll try to keep this updated as new info or procedures come up :good:
hondajohn88 said:
Hi everyone, I finally got a little time to put together a guide to flashing stuff on the LeEco Le Pro 3 X727.
This phone comes with an unlockable bootloader out of the box, but we found some ways to get around that.
This guide will help anyone with a new X727 unlock the bootloader, install TWRP and root it.
First, I'd like to give huge props to @dr4stic for his excellent work on making it easier to unlock the phone, and for helping me get back to the US ROM after installing the Chinese rom.
On to the flashing...
If you want to take the long way around, this was the first method used for unlocking the bootloader:
First method is using the stock Chinese ROM & renaming it update.zip, place it in the root directory then use the Update app (or in settings) to select that update, then let it do its thing. It takes a while to boot back up so be patient.
Stock Chinese ROM: https://www.androidfilehost.com/?fid=529152257862681546
Once the Chinese ROM is installed and booted up, enable Developer Options, make sure OEM Unlocking is turned on, then enable USB Debugging.
For these next steps, I'm quoting @dr4stic:
Have ADB/Fasboot tools on your computer (I am not helping you here, it you're lucky, maybe your friends will help)
Make sure you have enabled the developer tools, turned on USB debugging, and authorized your computer on your device (again, I'm not helping with that)
Make sure adb can see your device when you run "adb devices"
Run "adb reboot bootloader"
Run "fastboot devices" to make sure you see your device
Run "fastboot oem unlock-go" to unlock your device temporarily
Run "fastboot oem device-info" to verify unlock status
Your bootloader is now permanently unlocked (well, until you re-lock it on purpose).
The second, and much shorter method, is outlined in @dr4stic's thread here: http://forum.xda-developers.com/le-pro3/development/x727-model-persistent-bootloader-unlock-t3500388
Once your bootloader is unlocked, you'll want to install TWRP.
Here are a couple options for TWRP:
https://www.androidfilehost.com/?fid=529152257862668751 (Chinese version)
https://www.androidfilehost.com/?fid=385035244224398544 (GrossoShop version)
Download either of those (or both if you want to try both), extract them and place the .img file(s) into the folder your ADB & Fastboot files are. To make the flashing easier, rename the twrp files to twrp.img. If you still have your command prompt window open, great! If not, open one again.
Now:
Run "fastboot flash recovery twrp.img" (or whatever the twrp image filename is on your computer) to flash TWRP.
When flashing is complete, reboot into TWRP by pressing and holding Power Button and Volume Up Button at the same time and holding until you see the TWRP splash screen.
If TWRP boots up in Chinese, tap the big button on the lower right to open the language settings and choose the language you can understand.
Alright, now you have an unlocked bootloader and custom recovery installed. Your world has opened up a little bit more
The main problem with installing the stock Chinese ROM is that it does not have Google Play and there is no band 12 support (at least for T-Mobile), but at least bands 2 & 4 still work.
It's easy enough to find methods to get that installed, but I tried the GrossoShop ROM which is a very good ROM, but if you must have band 12, you'll need to read down a little farther.
Link to GrossoShop ROM: https://www.androidfilehost.com/?fid=529152257862686304
Okay, if you chose to use the long route and installed the Chinese ROM, you can still get back to the full US version, complete with all LTE bands. dr4stic is responsible for this gem, and was my way back to US ROMdom.
To go from Chinese or Custom ROM back to Stock US version:
The file is located in his Android File Host space here: https://www.androidfilehost.com/?fid=601275311581036717
It's a little tricky to install, so follow these steps:
1. Enter TWRP and from Advanced Wipe, wipe Dalvick/ART Cache, Cache, System and Data (Leave Internal Storage untouched if that's where you copied the new ROM zip).
2. Install CN5.8.018s-to-US5.8.019s.zip
3. DO NOT REBOOT DIRECTLY AFTER FLASHING (Phone just vibrates forever if you reboot directly after flashing)
4. Go back to TWRP Home, then tap Reboot, then tap System.
The phone should reboot after that, and it might take a while. Then follow the setup process as you normally would and it should go through the Google setup as well.
To install root, I use SuperSU. Sometimes it's kinda hard to find the most up to date version, so I'll post the latest one that I have: https://www.androidfilehost.com/?fid=457095661767120474
There's probably a newer version already, but I haven't looked.
Simply download and flash that file in TWRP, reboot and you're rooted. Easy peasy.
With the methods listed above, you should now be able to take a new LeEco Le Pro 3 X727 and unlock the bootloader, install TWRP, and flash whatever ROMs you want.
Again, big big thanks to @dr4stic to getting us to this point for the easy unlock option AND big thanks to all of you folks here in the forums for all of you suggestions, efforts and enthusiasm!
I imagine there will be some refinements and/or corrections to this guide as questions and suggestions come up, so please, if you see something in here that is wrong or unclear, please let me know.
Click to expand...
Click to collapse
Nice one John
seffmono said:
Nice one John
Click to expand...
Click to collapse
Thank you kind sir
"...It's easy enough to find methods to get that installed, but I tried the GrossoShop ROM which is a very good ROM, but if you must have band 12, you'll need to read down a little farther..."
Did I miss the part on how to keep the Band 12 capabilities?
Thanks John, you have been very kind and helpful! So here what my setup is...
1. I installed Chinese ROM on 727.
2. Unlocked bootloader
3. Installed twrp, installed CM13.
I'm happy with this setup. All I want is the T-Mobile band 12 support. Can you please post steps on this part as well?
I see a long process where I can install CN.x.x.to.US.x.x.zip file via twrp. But will this lock the bootloader again and replace it with stock recovery? I didn't know that TWRP can update bootloader so I'm curious. If so I can follow dr4stic's guide to unlock the bootloader and then install twrp and restore the backup of my CM13.
Sent from my LEX720 using Tapatalk
ceo.mtcl said:
Thanks John, you have been very kind and helpful! So here what my setup is...
1. I installed Chinese ROM on 727.
2. Unlocked bootloader
3. Installed twrp, installed CM13.
I'm happy with this setup. All I want is the T-Mobile band 12 support. Can you please post steps on this part as well?
I see a long process where I can install CN.x.x.to.US.x.x.zip file via twrp. But will this lock the bootloader again and replace it with stock recovery? I didn't know that TWRP can update bootloader so I'm curious. If so I can follow dr4stic's guide to unlock the bootloader and then install twrp and restore the backup of my CM13.
Sent from my LEX720 using Tapatalk
Click to expand...
Click to collapse
Flashing the CN-US ROM will not relock the bootloader, so you're safe there.
I followed the shorter version to unlock the bootloader and flashed twrp, and it worked. Once I reboot, and go back in recovery, it goes to stock recovery. I wonder if I need to delete the stock recovery?
Sent from my SM-N930V using Tapatalk
rob_z11 said:
I followed the shorter version to unlock the bootloader and flashed twrp, and it worked. Once I reboot, and go back in recovery, it goes to stock recovery. I wonder if I need to delete the stock recovery?
Sent from my SM-N930V using Tapatalk
Click to expand...
Click to collapse
If you install TWRP from fastboot (fastboot flash recovery twrp.img), it should replace the factory recovery.
rob_z11 said:
I followed the shorter version to unlock the bootloader and flashed twrp, and it worked. Once I reboot, and go back in recovery, it goes to stock recovery. I wonder if I need to delete the stock recovery?
Click to expand...
Click to collapse
In fastboot mode type "fastboot flash recovery recovery.img".... Fastboot boot recovery.img will only boot it and return back to stock after reboot. Flash will make it remain.
seffmono said:
In fastboot mode type "fastboot flash recovery recovery.img".... Fastboot boot recovery.img will only boot it and return back to stock after reboot. Flash will make it remain.
Click to expand...
Click to collapse
i will try that.
I am really interested in flashing my phone with cyanogen but I am a total newbie at this. Could someone post a video tutorial for 727 model?
worries said:
I am really interested in flashing my phone with cyanogen but I am a total newbie at this. Could someone post a video tutorial for 727 model?
Click to expand...
Click to collapse
I hate to speak for everyone here but it's highly unlikely someone will take the time to do that. I suggest you instead do as much research as you can, and make a video for the next person like yourself that prefers it. Speaking from experience most people on XDA will recommend spending as much time reading and learning as you can, and then taking the "leap" on your own. Rooting and unlocking is not for the faint of heart, and a bit of confidence in your own abilities can go a long way! I hope this doesn't sound condescending, but just my advice. Best of luck!
I just installed the stock chinese ROM and when it boots it asks for a password to start Android. Has anyone else seen this. Do you know what the password is?
---------- Post added at 05:55 AM ---------- Previous post was at 05:29 AM ----------
Nevermind. Booted into recovery and formatted the system then it ran fine.
huemedia said:
I just installed the stock chinese ROM and when it boots it asks for a password to start Android. Has anyone else seen this. Do you know what the password is?
Click to expand...
Click to collapse
It had this happen and If i remember correctly, their is a bug in the system and it wont let you past that screen regardless what. Just boot to twrp do a data backup. Format everything else except internal storage and reflash your rom
I followed this guide and flashed the US modem zip on top of stock 19s. However, my SIM is recognized and the "Mobile Networks" setting page is grayed out. However, my phone is still booting with Chinese text in the bootloader. How do I fix this?
Anyone tried this method on stock 20s. Build to unlock bootloader
LeEco Pro3
toanau said:
Anyone tried this method on stock 20s. Build to unlock bootloader
LeEco Pro3
Click to expand...
Click to collapse
I am trying the long way and it's failing (20s)
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device product name: [le_zl1_oversea]
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Serial console enabled: false
(bootloader) Serial hw output enabled: false
(bootloader) Display panel:
OKAY [ 0.083s]
finished. total time: 0.083s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock-go
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.011s
Im dumb, nevermind
I got a ZF3 Deluxe from Italy, is TIM branded, and stuck on MM 6.0, no updated released for this brand, so a friend of mine told me there is of course android 7 for ZF3Deluxe, so i wanted to manually upgrade system to 7.0 Nougat, i downloaded the Stock ROM from asus (2.15ghz cpu, i've checked of course) but when i try to flash it from the Stock Recovery i get this error (see the attachment) i also attach the software informations, (looking at the error i receive it may see the archive is corrupted, but i've tried to download it from Asus many and many times)
You have a carrier rom on your phone and the international version fails the upgrade check.
If you could get your bootloader unlocked that would be a way around it but you need to upgrade to a certain rom version to do that and the carrier hasn't supplied that rom...
You're essentially screwed until the carrier either releases the bootloader unlockable rom or upgrades the rom to nougat...
LeGrim said:
I got a ZF3 Deluxe from Italy, is TIM branded, and stuck on MM 6.0, no updated released for this brand, so a friend of mine told me there is of course android 7 for ZF3Deluxe, so i wanted to manually upgrade system to 7.0 Nougat, i downloaded the Stock ROM from asus (2.15ghz cpu, i've checked of course) but when i try to flash it from the Stock Recovery i get this error (see the attachment) i also attach the software informations, (looking at the error i receive it may see the archive is corrupted, but i've tried to download it from Asus many and many times)
Click to expand...
Click to collapse
You should try to flash stock recovery of WW in fastboot.
And then flash 6.0 WW rom by WW recovery.
Even though ,I didn't sure that if it will work(because I don't have Z016S),but you can try it.
samson1357924 said:
You should try to flash stock recovery of WW in fast boot.
And then flash 6.0 WW rom by WW recovery.
Even though ,I didn't sure that if it will work(because I don't have Z016S),but you can try it.
Click to expand...
Click to collapse
Ok thanks, i can give a try, but where i can download the WW stock recovery? There is no recovery.img inside the WW_user.zip ROM
LeGrim said:
Ok thanks, i can give a try, but where i can download the WW stock recovery? There is no recovery.img inside the WW_user.zip ROM
Click to expand...
Click to collapse
Here it comes~
ZenFone 3 Deluxe ZS570KL_WW stock recovery
Ok guys, i think i've found a way to debrand my Zenfon 3 Deluxe, im testint the procedure right now, i will post the whole procedure if i succeed
Install : ADB & Minimal Fastboot.
Install : pyton 3.6 https://www.python.org/downloads/
Download the latest WW-4.12.40.1698 (For 2.15GHz CPU or 2.40GHz CPU) from Asus WebSite.
Download "Dat to img by stupdroid.com" (search it with google).
Extract Dat to img by stupdroid.com in a Folder.
Open the Firmware ZIP and copy system.new.dat, system.transfer.list e file_contexts in the Dat2IMG's folder.
Execute system.new.dat 2 flashable img converter.exe and just press ENTER and wait till the end of procedure, you will receive 2 files : system.raw.img e system.new.img.
Copy system.new.img in your Fastboot's folder.
Put the Phone into Fastboot mode.
Open fastboot and put this command: " fastboot flash system system_new.img "
Wait the end of flash procedure and type : Fastboot Reboot.
Enter recovery wipe data and cache.
Done.
LeGrim said:
Install : ADB & Minimal Fastboot.
Install : pyton 3.6 https://www.python.org/downloads/
Download the latest WW-4.12.40.1698 (For 2.15GHz CPU or 2.40GHz CPU) from Asus WebSite.
Download "Dat to img by stupdroid.com" (search it with google).
Extract Dat to img by stupdroid.com in a Folder.
Open the Firmware ZIP and copy system.new.dat, system.transfer.list e file_contexts in the Dat2IMG's folder.
Execute system.new.dat 2 flashable img converter.exe and just press ENTER and wait till the end of procedure, you will receive 2 files : system.raw.img e system.new.img.
Copy system.new.img in your Fastboot's folder.
Put the Phone into Fastboot mode.
Open fastboot and put this command: " fastboot flash system system_new.img "
Wait the end of flash procedure and type : Fastboot Reboot.
Enter recovery wipe data and cache.
Done.
Click to expand...
Click to collapse
I forgot to say, after this procedure, just flash the stock WW recovery via Fastboot, then download from asus the lastest 7.0 firmware SKU WW, all perfect. tested by me.
Ok I already have system.new.img, I copied it to the root folder of the SD. Device restart in Fastboot mode (power + vol.up key). Exit screen with message Fastboot mode and does nothing.
Install in the computer the pyton 3.6, I suppose that it serves for the process of generating system.new.img.
I do not know how to do the first step "Install: ADB & Minimal Fastboot.".
Thank you and forgive my translator
If i want to unlock the bootloader for root and unbrand this phone what i have to do? I need unbranded nougat with root but the phone is TIM branded
Ryder. said:
If i want to unlock the bootloader for root and unbrand this phone what i have to do? I need unbranded nougat with root but the phone is TIM branded
Click to expand...
Click to collapse
What version is your phone right now??
Now only have official unluck
For 2.15GHz:8996(None-PRO) UnlockTool
For 2.4GHz:8996P(PRO) UnlockTool
If you are WW version right now,try these tools.
samson1357924 said:
What version is your phone right now??
Now only have official unluck
For 2.15GHz:8996(None-PRO) UnlockTool
For 2.4GHz:8996P(PRO) UnlockTool
If you are WW version right now,try these tools.
Click to expand...
Click to collapse
It's not WW. I'ts from italy and it's tim branded
Ryder. said:
If i want to unlock the bootloader for root and unbrand this phone what i have to do? I need unbranded nougat with root but the phone is TIM branded
Click to expand...
Click to collapse
Try this
or try flash ZenFone 3 Deluxe ZS570KL_WW stock recovery of 4.12.40.1698 and flash UL-Z016-WW-4.12.40.1698-user.zip in recovery (by micro sd or adb sideload)not sure if it work(need verification,I wish you to try first).
Please help me, my model is the Z016S
I can convert UL-Z016-WW-4.12.40.1698-user.zip img and flash with fastboot.
Reboot and it works, but I do not know how to get into recovery.
I have also installed the Z016-WW-4.11.40.1085_recovery.img. The TIM DISAPPEARED
Then I copied the UL-Z016-WW-5.14.44.1898-user.zip into the internal memory and it does not install well.
I have proven the same with UL-Z016-WW-5.14.44.1898-user.zip and it does not work me it stays in a non-comands and will not boot.
greetings and thanks
P.S. At least you do not see the TIM anywhere.
barbapapa said:
Please help me, my model is the Z016S
I can convert UL-Z016-WW-4.12.40.1698-user.zip img and flash with fastboot.
Reboot and it works, but I do not know how to get into recovery.
I have also installed the Z016-WW-4.11.40.1085_recovery.img. The TIM DISAPPEARED
Then I copied the UL-Z016-WW-5.14.44.1898-user.zip into the internal memory and it does not install well.
I have proven the same with UL-Z016-WW-5.14.44.1898-user.zip and it does not work me it stays in a non-comands and will not boot.
greetings and thanks
P.S. At least you do not see the TIM anywhere.
Click to expand...
Click to collapse
So,what is your system version right now?4.12.40.1698?
Why not flash the recovery of 4.12.40.1698?
samson1357924 said:
So,what is your system version right now?4.12.40.1698?
Why not flash the recovery of 4.12.40.1698?
Click to expand...
Click to collapse
This is my situation
samson1357924 said:
So,what is your system version right now?4.12.40.1698?
Why not flash the recovery of 4.12.40.1698?
Click to expand...
Click to collapse
I have done this and it installs,
fastboot flash recovery Z016-WW-4.12.40.1698_recovery.img
reboot, boot system, detect update file is installed, reboot and then gives error (3) unknown.
barbapapa said:
I have done this and it installs,
fastboot flash recovery Z016-WW-4.12.40.1698_recovery.img
reboot, boot system, detect update file is installed, reboot and then gives error (3) unknown.
Click to expand...
Click to collapse
Tow solution you can try
1.install the rom of 4.12.40.1698 again(some of tile,such as xbl,devcfg,devcfgbak..... may be still TIM versio.install it in recovery may turn it into WW version)
2.If fail, try flash these files in fastboot.(I will upload these files for you to flash,also you can draw by yourself)
Ok already worked, the solution is to unlock as you put in # 11.
Thank you
barbapapa said:
Ok already worked, the solution is to unlock as you put in # 11.
Thank you
Click to expand...
Click to collapse
Good!
Can you share what step did you do? Which might help another TIM user.
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!!
Mohammadreza76646 said:
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!!
Click to expand...
Click to collapse
Doing the update second time is fine, and best way to restore full stock. But you needed to use Oreo version of no-check recovery and the Oreo partition to flash it to.
So if still able to get into twrp, can try with correct no-check recovery and correct partition it's flashed to.
Also
With multi tool , make sure you put check mark on emui 8. Up in upper right corner. That way it uses Oreo partition names and file not nougat.
The partition length over message usually means nougat file or partition name used on Oreo system
mrmazak said:
Doing the update second time is fine, and best way to restore full stock. But you needed to use Oreo version of no-check recovery and the Oreo partition to flash it to.
So if still able to get into twrp, can try with correct no-check recovery and correct partition it's flashed to.
Also
With multi tool , make sure you put check mark on emui 8. Up in upper right corner. That way it uses Oreo partition names and file not nougat.
The partition length over message usually means nougat file or partition name used on Oreo system
Click to expand...
Click to collapse
Thank you for your answer.
But I try to extract update.app (oreo version) but its failed! huawei update extractor cant open it and 7zip cant extract it with (unexpected error...)!
And unfortunately my TWRP dos not work anymore
Mohammadreza76646 said:
Thank you for your answer.
But I try to extract update.app (oreo version) but its failed! huawei update extractor cant open it and 7zip cant extract it with (unexpected error...)!
And unfortunately my TWRP dos not work anymore
Click to expand...
Click to collapse
I give my phone to a friend to work on it. If he can't fix it I try new multi tools version to flash phone.
Mohammadreza76646 said:
Thank you for your answer.
But I try to extract update.app (oreo version) but its failed! huawei update extractor cant open it and 7zip cant extract it with (unexpected error...)!
And unfortunately my TWRP dos not work anymore
Click to expand...
Click to collapse
On the extractor app. On options tab uncheck the verify header option, it should extract then.
Then perhaps first do these three partitions.
Kernel.img
Ramdisk.img
Then
twrp_ramdisk or for stock use recovery_ramdisk
Mohammadreza76646 said:
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!!
Click to expand...
Click to collapse
I ever have similiar problem with you dude, but it's solved now, if you always stuck on " its OK but when my phone want to start its stuck on google page "just a sec...", its call google accont verification, i'll by bypass with this script, save as to .bat and put on adb folder
adb devices
adb shell content insert --uri content://settings/secure --bind name:s:user_setup_complete --bind value:s:1
adb shell am start -n com.google.android.gsf.login/
adb shell am start -n com.google.android.gsf.login.LoginActivity
pause
in fastboot type:
fastboot -w
after all it's works to me to bypass google account verification
and if now your problem is
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
i solve with re-flash system from this
https://androidfilehost.com/?fid=673956719939830152
fastboot flash system system.img
and doing TWRP Flashing
https://forum.xda-developers.com/devdb/project/?id=25826#downloads
fastboot flash recovery_ramdisk complete_twrp_ramdisk.img
and voila my problem solved..
mrmazak said:
On the extractor app. On options tab uncheck the verify header option, it should extract then.
Then perhaps first do these three partitions.
Kernel.img
Ramdisk.img
Then
twrp_ramdisk or for stock use recovery_ramdisk
Click to expand...
Click to collapse
Hello again dude.
Finally I flashed my phone and I got the system installed.
But now my phones IMEI is lost. and I cant put sim on it!!!
what should I do now???
FRP is locked! (
Mohammadreza76646 said:
Hello again dude.
Finally I flashed my phone and I got the system installed.
But now my phones IMEI is lost. and I cant put sim on it!!!
what should I do now???
FRP is locked! (
Click to expand...
Click to collapse
So now is locked frp. Does phone have twrp or stock now.?
I think when you tried to install the oreo update for second time, you followed same tutorial as the first time. And that made you problem worse. The tutorial has you flash no-check recovery to 2 partition by block number. 22 & 29. On nougat that is "recovery" and "recovery2". On Oreo partion table it is "reserved2" & "erecovery_vendor"
I don't know how to fix imei. Have hope that if to ucan have a full ota install , maybe can be fixed.
There is available a "service rom" (used to fix most all problem) for Europe region with l21.
I can share link to site with service rom if you want , but I have not used it myself so not gonna be much help with it.
Link is to rusian language page. Google should translate for you.
https://4pda.ru/forum/index.php?showtopic=879524&view=findpost&p=73818595
mrmazak said:
So now is locked frp. Does phone have twrp or stock now.?
I think when you tried to install the oreo update for second time, you followed same tutorial as the first time. And that made you problem worse. The tutorial has you flash no-check recovery to 2 partition by block number. 22 & 29. On nougat that is "recovery" and "recovery2". On Oreo partion table it is "reserved2" & "erecovery_vendor"
I don't know how to fix imei. Have hope that if to ucan have a full ota install , maybe can be fixed.
There is available a "service rom" (used to fix most all problem) for Europe region with l21.
I can share link to site with service rom if you want , but I have not used it myself so not gonna be much help with it.
Link is to rusian language page. Google should translate for you.
https://4pda.ru/forum/index.php?showtopic=879524&view=findpost&p=73818595
Click to expand...
Click to collapse
It have stock recovery.
Mohammadreza76646 said:
It have stock recovery.
Click to expand...
Click to collapse
in summery. because i have been going back and forth in multiple different groups, multiple problem, i cant remember it all.
you have broken system, from failed root attempt, followed by failed update.
device condition is as follows.
--system not booting
--stock recovery loads
--fastboot/bootloader loads, but is in frp lock status
options are limited, at best.
I think "dload" method with service rom is best.
other option is maybe paid service like dc-unlock. But I can recall some note on there service about frp-unlock, that can only be used on device with working system. (of course if was working system, wouldn't need dc-unlock)
mrmazak said:
in summery. because i have been going back and forth in multiple different groups, multiple problem, i cant remember it all.
you have broken system, from failed root attempt, followed by failed update.
device condition is as follows.
--system not booting
--stock recovery loads
--fastboot/bootloader loads, but is in frp lock status
options are limited, at best.
I think "dload" method with service rom is best.
other option is maybe paid service like dc-unlock. But I can recall some note on there service about frp-unlock, that can only be used on device with working system. (of course if was working system, wouldn't need dc-unlock)
Click to expand...
Click to collapse
No. System boot successfully!
I will send you screenshot:
Mohammadreza76646 said:
No. System boot successfully!
I will send you screenshot:
Click to expand...
Click to collapse
here you are
Mohammadreza76646 said:
here you are
Click to expand...
Click to collapse
what about the "about phone" screen
what does it show for version?
If is all stock you should be able to go into deveolper options and enable "oem unlock". If it is greyed out and cannot switch it. Try First to remove google account (all accounts ). and reboot. See if can change then. If not, try Second to do "fastboot oem relock [enter your bootloader code here]
after relock and rebooted oem switch should be enabled again.
****RELOCK IS ONLY ADVISED IF 100% STOCK ROM****
otherwise relock could make more trouble.
Still not sure how to get IMEI back even if unlocked frp though.
**And please stop posting in other threads , the same problem , because you are getting help here.
your post in recovery thread is off topic to that thread and just makes the forum harder to maintain.
mrmazak said:
what about the "about phone" screen
what does it show for version?
If is all stock you should be able to go into deveolper options and enable "oem unlock". If it is greyed out and cannot switch it. Try First to remove google account (all accounts ). and reboot. See if can change then. If not, try Second to do "fastboot oem relock [enter your bootloader code here]
after relock and rebooted oem switch should be enabled again.
****RELOCK IS ONLY ADVISED IF 100% STOCK ROM****
otherwise relock could make more trouble.
Still not sure how to get IMEI back even if unlocked frp though.
**And please stop posting in other threads , the same problem , because you are getting help here.
your post in recovery thread is off topic to that thread and just makes the forum harder to maintain.
Click to expand...
Click to collapse
Thanks )
I'm so sorry for my posts, it's because I don't have a stable connection and I can't see notification of my thread.
I gave my phone to friend an he fix IMEI (I don't know how)
But OEM is steel lock.
I think he did it with using special box.
Mohammadreza76646 said:
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!![/QUOTE
Are u able.to boot into twrp ?
Click to expand...
Click to collapse
Hello I have a Huawei Mate-SE (with bootloader unlocked and rooted with magisk v16). I have been using the android custom rom RRO v6 (RR-O-v6.0.0-20180401-bnd-OpenKirin) for around a month now. I got this exact same problem about the White Screen saying "ERROR MODE Attention...." since I updated the Magisk to latest version (from the installed application) and rebooted my phone. SInce I rebooted I am getting that same error which makes the phone loops into it for a few times and then it loads the Huawei eRecovery that offers me some options that I am not sure what would do to my phone.
I have been trying to connect to adb tools/fastboot but it doesn't detect the phone and im pretty sure I have the device drivers installed on my computer since nothing have changed in my pc for a month now since I flashed RRO on it.
Is there any other mode besides recovery that would allow me to connect adb/fastboot to it? Or does anyone knows how should I proceed?
IonDEfeso said:
Hello I have a Huawei Mate-SE (with bootloader unlocked and rooted with magisk v16). I have been using the android custom rom RRO v6 (RR-O-v6.0.0-20180401-bnd-OpenKirin) for around a month now. I got this exact same problem about the White Screen saying "ERROR MODE Attention...." since I updated the Magisk to latest version (from the installed application) and rebooted my phone. SInce I rebooted I am getting that same error which makes the phone loops into it for a few times and then it loads the Huawei eRecovery that offers me some options that I am not sure what would do to my phone.
I have been trying to connect to adb tools/fastboot but it doesn't detect the phone and im pretty sure I have the device drivers installed on my computer since nothing have changed in my pc for a month now since I flashed RRO on it.
Is there any other mode besides recovery that would allow me to connect adb/fastboot to it? Or does anyone knows how should I proceed?
Click to expand...
Click to collapse
I have seen where the magisk update screwed up and patches the kernel intead of the ramdisk.
Power off , long press power button.
Hold volume down and plug in USB from PC.
This should cause it to boot into fastboot mode.
Then flash the stock kernel. And the stock or first patched ramdisk. (From earlier root)
mrmazak said:
I have seen where the magisk update screwed up and patches the kernel intead of the ramdisk.
Power off , long press power button.
Hold volume down and plug in USB from PC.
This should cause it to boot into fastboot mode.
Then flash the stock kernel. And the stock or first patched ramdisk. (From earlier root)
Click to expand...
Click to collapse
Hi thank you I was able to finally detect the device now. I am unsure about the kernel is that the recovery.img or system.img files I downloaded (i saved every file i used when I installed the rom) or do I need to look for the kernel somewhere else? I do have the complete_twrp_ramdisk.img file though.
Edit, I did more research and found the stock kernel is withing the boot.img file which I dont have so I looked up for the official BND-L34 oreo update and im currently downloading to extract the stock boot.img from the update.zip and flash it. Since that download was going to take me a while anyway i tried flashing the twrp recovery file without success (didn't changed anything) so i guess I should follow the instructions you gave me by flashing the kernel first then the twrp recovery.
mrmazak said:
I have seen where the magisk update screwed up and patches the kernel intead of the ramdisk.
Power off , long press power button.
Hold volume down and plug in USB from PC.
This should cause it to boot into fastboot mode.
Then flash the stock kernel. And the stock or first patched ramdisk. (From earlier root)
Click to expand...
Click to collapse
Do you know what the boot.img files name is after extraction?
I have extracted all 3 update zips and cannot find anything called boot.img
By the way, thank you.. After updating magisk I have been dealing with failed recovery and failed boot for over a week and this is the first reply anywhere that looks promising
IonDEfeso said:
Hi thank you I was able to finally detect the device now. I am unsure about the kernel is that the recovery.img or system.img files I downloaded (i saved every file i used when I installed the rom) or do I need to look for the kernel somewhere else? I do have the complete_twrp_ramdisk.img file though.
Edit, I did more research and found the stock kernel is withing the boot.img file which I dont have so I looked up for the official BND-L34 oreo update and im currently downloading to extract the stock boot.img from the update.zip and flash it. Since that download was going to take me a while anyway i tried flashing the twrp recovery file without success (didn't changed anything) so i guess I should follow the instructions you gave me by flashing the kernel first then the twrp recovery.
Click to expand...
Click to collapse
if you were on oreo. then there is not a boot.img, instaed there is seperate ramdisk.img and kernel.img.
i have all the files already extracted for oreo and a backup from nougat as well.
https://androidfilehost.com/?w=files&flid=265998
make sure you know what you are doing before flashing.
for example. on oreo the boot and recovery share one kernel image. SO if kernel is messed up you will not be able to boot "boot" or "recovery"
I decided to make this thread so people won't brick their devices/lose their IMEI/explode their phone when trying to update to the recently leaked/released Oreo Motorola ROM.
This is very information dense. Please, read this and the linked threads carefully and do not miss any step unless told so.
WARNING: This will erase all your data, reset all your settings. MAKE BACKUPS.
I also do not hold responsibility for any negative outcomes out of following this tutorial.
Always look for as many sources of information as you can. There is always something that isn't 100% correct in every tutorial.
Also, making it clear. This is for those who are currently on an Oreo CUSTOM ROM such as Lineage, Pixel Experience or other.
Preparation Steps:
Backup all your important files to your PC. You should do that since everything will be reset.
Make sure your phone is well charged. 80% at least. You want to be safe.
Boot into fastboot.
Install Minimal ADB and Fastboot.
In the command prompt of Minimal ADB and Fastboot, type:
Code:
fastboot getvar all
You will see a bunch of lines come up on the screen. Scroll and look for
Code:
(bootloader) ro.build.fingerprint[0]
.
This will tell the last version of the Stock ROM (Nougat) you had installed.
Example: "NPNS25.137-92-4" Yours won't/may not be the same.
Write it down somewhere. You will need this version number.
Open this link https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/ to download the exact version you found. If anything, download a version above the one you found. Never an inferior. Those are Motorola's Official Nougat ROMs.
Keep it somewhere accessible in your PC and extract the zip. Remember where you put it, you will need it later.
You will now proceed to check your persist partition. Aka: The thing everyone overlooks and screws your IMEI.
IMPORTANT: Take a look at https://forum.xda-developers.com/g5-plus/how-to/fix-persist-resolve-imei0-explanation-t3825147 to find out if your persist partition has permission issues and see if it's recoverable. It is 99% likely that if you are on a custom Oreo ROM that the permissions won't be intact.
If that is the case (most likely), download NZedPred's TWRP Persist Restore zip into your phone.
Feel free to skip these last steps if you have a backup of your persist and efs.
Reboot into recovery and using the most recent TWRP make a backup of your persist and efs. (Information about this can be found on the second post of the "Fix Persist" thread. I am not willing to write a thousand instructions on one thread for the sake of not overcomplicating things.) //****ty steps: have/flash most recent TWRP > backup > select persist and efs > profit
These backups should be on a TWRP folder of the internal storage of your Moto G5. Reboot the phone (or mount USB) and copy that folder to your PC. In case anything goes wrong you will have a copy of your persist.
Steps:
Reboot into recovery (TWRP) using your preferred method. (Be it by the buttons, or via ADB (adb reboot recovery)).
Flash the TWRP Persist Restore zip.
Reboot into bootloader
Open (on your PC ofc) the folder with the extracted files of the Stock ROM zip (NOUGAT).
Open the extracted files folder then press Shift+RMB (Right Mouse Click/Button) and select "Open Command Prompt here" (It may work with Powershell??? If anything, write a post here)
For a quick test, type
Code:
fastboot
In case an error pops-up and tells you that it can't recognize such a command. Follow this article https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/ to add Minimal ADB and Fastboot to your system environment variables
Now, make sure that the path to the left of the typing cursor is the path of the folder where you have your extracted Nougat ROM files.
Please, for your phone's OTA update ability sake. Make sure that you are flashing the exact version you had before. The version you found by running fastboot getvar all.
The commands below will attempt to update the bootloader and gpt. You should NEVER flash an older version of the bootloader.
If you wish, you can skip the GPT/Bootloader commands. I haven't done myself because I flashed the correct version I had before anyway.
Copy and paste these commands and press enter in the CMD.
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
This will flash the Stock Nougat ROM you have downloaded and will reboot your phone. If all goes well you will be back on Nougat, set up your device as normal.
Attention, everything has been reset, erased, wiped.
Oreo OTA Steps:
After setting up everything, check for OTA's. You should be safe to install them. If you are on a recent firmware, you may only need to install security ones. Keep installing and checking until it says there are no more updates available.
This is where people **** up when they downgrade their bootloader by flashing an older Stock ROM than the one they had before.
Before proceeding, double check that there aren't any OTAs available or that Oreo is available at the time of reading this.
If Oreo is officially available, skip all of these steps and be happy.
Otherwise, if at the time of reading, there is a ZIP of the Oreo ROM that matches your region. Download it.
In case of RETLA, RETBR, and RETIN, at the time of writing, this is the correct file:
https://mega.nz/#!DxdSVaJb!5VEht-s6HYCNOZ2hXXVIPdFBqmWCuAvQL1Wzmp7rhZk or https://drive.google.com/open?id=1ZmtSW40oZi1EXD0PsRib3dqIeF9vauAY
In case you are on RETUS, RETAPAC, RETEU, etc. You may need another file that may not be available. The best course of action would be to wait for the Official OTA. :good:
Download it and put in the root of the internal storage of your Moto G5 Plus.
Go to the Settings app. In the Settings app, you'll want to find the OTA App (Motorola Update Services) by showing System apps and enable storage permissions.
Before you proceed: This is apparently indeed the official OTA that they will ship, which seems to be the same as the Soak 4. It's seemingly stable here, so, you should be fine to use that.
Check on your phone for an OTA.
Reboot it.
Check for an update again. There will be a prompt telling you about copying "system" files. Accept it.
After a while, another prompt will ask you about the update. There won't be a changelog, this is normal. Make sure your device is charged and install it.
Wait for the update to complete and you're done.
Tips:
You can also refer to this thread for some more information about fastboot flashing:
https://forum.xda-developers.com/g5-plus/development/stock-firmware-npn25-137-67-5-fastboot-t3694738
Refer to this thread if you need persist information:
https://forum.xda-developers.com/g5-plus/how-to/fix-persist-resolve-imei0-explanation-t3825147
Google and XDA are your friends.
It's good practice to wipe/reset your phone after you're done. Updates usually leave dirt behind. I haven't personally done this myself and everything is OK, but still...
Feel free to correct me on any mistake. It took me about an hour (or more) to write this and I could have potentially overlooked an important detail.
I flashed OPS28.85-13 by TWRP and when I put fastboot getvar all show me: ro.build.fingerprint[0] OPS28.85-13, so what should I do to flash the official OTA without troubles?, I read that probably I should flash nougat flashable by TWRP and then install Official Nougat and then Official Oreo , what do you think? Thanks!
TheGameExtreme said:
I flashed OPS28.85-13 by TWRP and when I put fastboot getvar all show me: ro.build.fingerprint[0] OPS28.85-13, so what should I do to flash the official OTA without troubles?, I read that probably I should flash nougat flashable by TWRP and then install Official Nougat and then Official Oreo, what do you think? Thanks!
Click to expand...
Click to collapse
Maybe I didn't explain the purpose of this thread...
This is meant for those who are currently in a CUSTOM Oreo ROM such as Lineage, Pixel Experience.
I assume you have the correct firmware installed already. No need to revert anything.
Well, that's what it says here.
Code:
(bootloader) ro.build.fingerprint[0]: motorola/potter_nt/potter_nt:8.1.0/OPS28.85-13/b8ea:user/release-keys
I don't think you need to do anything.
However, what's the bootloader version? Should be:
Code:
(bootloader) version-bootloader: moto-msm8953-C0.92
I had hardbricked my phone and am using a tarp flashablr stock ROM. Can I use this method to go back to stock?
BlackScout said:
Maybe I didn't explain the purpose of this thread...
This is meant for those who are currently in a CUSTOM Oreo ROM such as Lineage, Pixel Experience.
I assume you have the correct firmware installed already. No need to revert anything.
Well, that's what it says here.
Code:
(bootloader) ro.build.fingerprint[0]: motorola/potter_nt/potter_nt:8.1.0/OPS28.85-13/b8ea:user/release-keys
I don't think you need to do anything.
However, what's the bootloader version? Should be:
Code:
(bootloader) version-bootloader: moto-msm8953-C0.92
Click to expand...
Click to collapse
It says: version-bootloader: moto-msm8953-C0.8C, I think it's an older version because before to install Oreo by TWRP I had Nougat with the March security patch
TheGameExtreme said:
It says: version-bootloader: moto-msm8953-C0.8C, I think it's an older version because before to install Oreo by TWRP I had Nougat with the March security patch
Click to expand...
Click to collapse
Yeah, your bootloader is still from Nougat. One day, that could become a problem (hard brick) when taking OTA's.
You can easily fix that by going back to Nougat. (Just make sure to flash the exact version (or one above) the one you had before. Remember, never downgrade your bootloader.).
I think you can just fastboot flash NPNS-25.137.92-14 (since the difference between that and the base 92 patch is just security patches...), download the OTA zip that's been posted around and follow the last set of instructions here (The ones labeled Oreo OTA Steps)
Remember, flashing those TWRP zips made by NZedPred is technically not the same thing as fastboot flashing or taking an OTA. These zips don't upgrade your bootloader and the OP of those threads do not recommend you to take any OTAs.
Quoting from the source: https://forum.xda-developers.com/g5-plus/development/twrp-flashable-stock-builds-t3813351
The partition table and bootloader are not included, which makes it safer to up/downgrade.
Do not attempt to apply standard OTAs over these builds. They'll probably fail, worst case they will brick your phone
So if you want to take the Oreo OTA and have an upgraded bootloader (C0.92), don't flash these. Flash the official Stock ROM (Nougat) images using fastboot then take the OTA.
I got all the information from this guide thanx but one doubt is there , i have my own efs nd persist and i have also backed it up so do i need to restore the restore zip or m i good to just fastboot flash nougat rom and update it via OTA to oreo? I m using custom oreo rom right now and i have never lost 4g or imei that means my efs and persist is my original..
I successfully flashed nougat thnx to your guide.i have downloaded the oreo update but where to put it the update is not being detected in system update
I m an Indian user so retin variant and dwnlf the oreo file provided by you.
karan3660 said:
I successfully flashed nougat thnx to your guide.i have downloaded the oreo update but where to put it the update is not being detected in system update
I m an Indian user so retin variant and dwnlf the oreo file provided by you.
Click to expand...
Click to collapse
The zip file needs to be placed in the internal memory and not within any folder in the internal memory (i.e in the root directory of internal memory), after that you need to give storage permission to the updater app and reboot. After reboot, you need to check for updates and the updater app should now be able to pick up the zip file you placed in internal memory as a new system update
psychopac said:
The zip file needs to be placed in the internal memory and not within any folder in the internal memory (i.e in the root directory of internal memory), after that you need to give storage permission to the updater app and reboot. After reboot, you need to check for updates and the updater app should now be able to pick up the zip file you placed in internal memory as a new system update
Click to expand...
Click to collapse
I have to directly place the zip file?? I extracted it into folder maybe thats why updater app didnt detected
Let me try again.
Tried after placing the zipe file directly into the root of internal storage and gave motorola update service storage permission then rebooted
Still not detevtion the zip file.
karan3660 said:
I have to directly place the zip file?? I extracted it into folder maybe thats why updater app didnt detected
Let me try again.
Tried after placing the zipe file directly into the root of internal storage and gave motorola update service storage permission then rebooted
Still not detevtion the zip file.
Click to expand...
Click to collapse
There's no need to extract the file. Simply place the zip in the root directory. You must be on June 137-92-14 update to install it.
psychopac said:
There's no need to extract the file. Simply place the zip in the root directory. You must be on June 137-92-14 update to install it.
Click to expand...
Click to collapse
I was on 93-10 version thats y it didnt detect update.
Flashed 92-14 nd updated to stock oreo
Thanks for the guide
karan3660 said:
I was on 93-10 version thats y it didnt detect update.
Flashed 92-14 nd updated to stock oreo
Thanks for the guide
Click to expand...
Click to collapse
Just for your info: 93-10 is a firmware for reteu/retus/retapac devices, 92-14 is for retin/rebra.
So you won't receive future OTA as you are on the wrong software channel.
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
Just for your info: 93-10 is a firmware for reteu/retus/retapac devices, 92-14 is for retin/rebra.
So you won't receive future OTA as you are on the wrong software channel.
Click to expand...
Click to collapse
It's actually quite possible that future otas will still be picked up (although I wouldn't recommend that others try this). Flashing another channel was important before, but given that Moto seem to have unified the builds.
NZedPred said:
It's actually quite possible that future otas will still be picked up (although I wouldn't recommend that others try this). Flashing another channel was important before, but given that Moto seem to have unified the builds.
Click to expand...
Click to collapse
That would be a nice move from Moto/Lenovo.
So I should have said:
So you probably won't receive future OTA as you are on the wrong software channel.
Sent from my Moto G5 Plus using XDA Labs
The stock OTA update for retus can be found here: https://technoplanners.blogspot.com/...S28.85-13.html
I downloaded this to root internal storage and changed storage permissions but System update doesn't find it. I also tried putting it in the sdcard root with same result. I tried to adb sideload it but it failed because Nougat has to be at Build number NPNS25.137-92. Since I had previously installed the OTA June security patches I'm at Build number NPNS25.137-93. So I seem to be between a rock and a hard place.
Any suggestions has to how to get upgraded to oreo OTA?
nvrpayretail said:
The stock OTA update for retus can be found here: https://technoplanners.blogspot.com/...S28.85-13.html
I downloaded this to root internal storage and changed storage permissions but System update doesn't find it. I also tried putting it in the sdcard root with same result. I tried to adb sideload it but it failed because Nougat has to be at Build number NPNS25.137-92. Since I had previously installed the OTA June security patches I'm at Build number NPNS25.137-93. So I seem to be between a rock and a hard place.
Any suggestions has to how to get upgraded to oreo OTA?
Click to expand...
Click to collapse
This Oreo OTA requires the Brazil or Indian firmware to flash onto (possibly Latin America firmware). As you've found out, this OTA is NOT compatible with US devices as they're on a different stock build. You'd have to wait for the EU, APAC or US OTA updates to be leaked or released. You'd also have to be on the NPNS25.137-93-14 update to apply the OTA update when it arrives.
The OTA I linked to is for the retus version - Blur_Version.28.51.16.potter.retail.en.US.zip
nvrpayretail said:
The OTA I linked to is for the retus version - Blur_Version28.potter.retail.en.US.zip
Click to expand...
Click to collapse
Yup, I've checked the link and it's linking to the Brazil Oreo OTA update. Despite the suffix 'en.US', this does not necessarily mean this update is for the US devices.
Furthermore, looking at the OTA updater script, it specifically requires NPNS25.137-92-14 or OPS28.85-13:
Code:
Package expects build thumbprint of 8.1.0/OPS28.85-13/b8ea:user/release-keys or 7.0/NPNS25.137-92-14/16:user/release-keys
Since you have mentioned you have NPNS25.137-93-14 this OTA simply will not flash to your device. You must wait for the compatible OTA to be released.
nvrpayretail said:
The OTA I linked to is for the retus version - Blur_Version.28.51.16.potter.retail.en.US.zip
Click to expand...
Click to collapse
Despite its name, it is not the us ota.
TWRP 3.3.1 & Root for Moto 1 VisionThanks to the efforts of yuri-2016 and and my humble contribution, the TWRP 3.3.1 was made from scratch and a new method of Root was tested.
Accept this gift from the bottom of your heart! :highfive:
Instructions
USB debugging must be enabled on the phone and the bootloader must be unlocked!
1. Download attached archive TWRP_Root_Motne_Vision.zip and extract files from it in the following order::
- .bat executive file and vbmeta.img to the folder with the firmware files;
- TWRP-3.3.1_Motorola_One_Vision.img to \adb\ folder.
- TWRP-3.3.1_Installer_Motorola_One_Vision.zip, Disable_Dm-Verity_ForceEncrypt.zip, Magisk Installer, MagiskManager copy to External SDcard in your phone.
2. Load phone in fastboot mode, then connect it to PC, then start an executive file .bat. At the end of flashing the phone will reboot into bootloader-mode and then TWRP again.
3. In the Recovery at the very beginning we put a checkmark in the checkbox to avoid this request in future, and give permission to modify the system for writing.
4. Go to the Wipe page and run the Format Data for decryption. Enter "yes" for the request. Exit to the Main Menu and reboot to Bootloader.
5. Attention! You mus BOOT into Recovery mode (DO NOT INSTALL it !), through the command:
Code:
fastboot boot C:\adb\TWRP-3.3.1_Motorola_One_Vision.img
6. Flash an archive TWRP-3.3.1_Installer_Motorola_One_Vision.zip which will make TWRP permanent.
NOTE: If you want to keep the stock Recovery , do not install this archive, but in order to boot into TWRP you will need to run the command from Step 5 every time.
7. Configure TWRP via “Settings”-page (time, time zone, language, etc.) as you want.
8. Go to “Install” page and flash the Magisk Installer , and flash Disable_Dm-Verity_ForceEncrypt.zip
9. Reboot in System. Phone will reboot several times, don`t worry. Perform initial settings again.
10. Install MagiskManager.apk, because the application installed in the system generates an error and does not start.
Now your device has a custom recovery TWRP and Root rights! :good: :victory:
01/10/2019 New instruction have been made
30/09/2019 New build TWRP !!!
Fixed: Removed the "Enable MTP" button.
Note: Who will reinstall the new TWRP build over the old one, follow these steps:
1. Download new TWRP_Root_Motne_Vision.zip
2. Load into Recovery mode via the command:
Code:
fastboot boot C:\adb\TWRP-3.3.1_Motorola_One_Vision.img
3. Install TWRP-3.3.1_Installer_Motorola_One_Vision.zip
4. Flash Magisk installer, Disable_Dm-Verity_ForceEncrypt.zip.
5. Reboot in the Recovery again.
6. Try to adjust the brightness, connect USB-OTG, check the absence of the "Enable MTP" button.
Old instructions
Friends! I got the Root for this device.
I'm not saying it's the only way to get a Root. I suggest something I used on my own device.
You are responsible for everything you do with your device!
Getting Root was performed on firmware XT1970-3_KANE_RETEU_DS_9.0_PSA29.160-30
Attention! The process of receiving the Root will delete all your data from the device.
1. The bootloader must be unlocked on the device beforehand.
2. Extract files from the archive https://drive.google.com/open?id=1xgTVlIXOFWq59I1-D9bnRlj1heJycT_I :
- vbmeta.img, vbmeta_patch.img and boot_patch.img to the adb folder;
- MagiskManager-v7.3.4.apk to a convenient folder for you. It will then need to be copied either to the phone memory or to the SD Card.
3. Load the device into fastboot mode and connect it to your PC.
4. Flash vbmeta.img with the command:
Code:
fastboot flash vbmeta_a vbmeta.img
5. Flash boot_patch.img with the command:
Code:
fastboot flash boot_a boot_patch.img
6. Flash vbmeta_patch.img command:
Code:
fastboot flash vbmeta_a vbmeta_patch.img
7. Load the device into the system by pressing the Start button. Phone will reboot in Recovery where there will be a warning that it is necessary to execute Factory reset. It is necessary to give your consent.
The phone will reboot several times again, don't worry.
8. Perform the initial setup. Install MagiskManager-v7.3.4.apk.
9. Launch the MagiskManager application. He will offer to update the application, click the Yes button. The phone will reboot.
Your device now has Root permissions and access to the system!
ilia3367 said:
Friends! I got the Root for this device. Tomorrow I will try to describe in detail the process of getting the Root.
Click to expand...
Click to collapse
Thank you so much!
That's incredible. I hope it works on Moto One Action too.
ilia3367 said:
Friends! I got the Root for this device. Tomorrow I will try to describe in detail the process of getting the Root.
Click to expand...
Click to collapse
This is excellent news, thanks !
Unlock the bootloader
Download the stock rom
Install magisk manager
Click install and chose patch boot image
Copy the patched boot image to your PC
Flash the new image using ADB
I think these are the steps to root the phone
SnoopDoggyStyleDogg said:
Unlock the bootloader
Download the stock rom
Install magisk manager
Click install and chose patch boot image
Copy the patched boot image to your PC
Flash the new image using ADB
I think these are the steps to root the phone
Click to expand...
Click to collapse
Those step give you the validation img error
I'm continuing with my friend to create TWRP
SnoopDoggyStyleDogg said:
Unlock the bootloader
Download the stock rom
Install magisk manager
Click install and chose patch boot image
Copy the patched boot image to your PC
Flash the new image using ADB
I think these are the steps to root the phone
Click to expand...
Click to collapse
That's what a lot of people think. I thought so too.
Thank you so much for the guide... I'll try in the afternoon
@ilia3367
Hello
I have a One Action, could you help me to get root?
Do I need to patch all those images with Magisk?
Thanks in advanced.
sfoot13 said:
@ilia3367
Do I need to patch all those images with Magisk?
Click to expand...
Click to collapse
Make a modified boot.img with Magisk and take my other files. Try to do it according to the instructions.
ilia3367 said:
Make a modified boot.img with Magisk and take my other files. Try to do it according to the instructions.
Click to expand...
Click to collapse
Thank you so much for your help and work!
I'll do that when I arrive at home
Hey! That's really good news pal. Do you think I can flash your Vision's vbmeta.img and vbmeta_patch.img and my magisk-patched boot.img on my Motorola One Action?
Tuandroidaldia said:
Hey! That's really good news pal. Do you think I can flash your Vision's vbmeta.img and vbmeta_patch.img and my magisk-patched boot.img on my Motorola One Action?
Click to expand...
Click to collapse
Replied on the previous page.
ilia3367 said:
Replied on the previous page.
Click to expand...
Click to collapse
Nope, it's not working on Motorola One Action, it says: "<bootloader> validation image failed" using my Magisk Patched Boot.img. Did you patched your boot using another tool or how?
Thanks.
@ilia3367 Finally Rooted. Thank you so much for your work. Very appreciate!
Tuandroidaldia said:
Nope, it's not working on Motorola One Action, it says: "<bootloader> validation image failed" using my Magisk Patched Boot.img. Did you patched your boot using another tool or how?
Thanks.
Click to expand...
Click to collapse
what about vbmeta? was possible to flash it?
@ilia3367 before Root and after unlock the bootloader when I touched the system update option, it said: "system integrity is compromised" now after Root when i touch it , it check for update again. It means that I can update the firmware via ota?
AndresOrue said:
@ilia3367 before Root and after unlock the bootloader when I touched the system update option, it said: "system integrity is compromised" now after Root when i touch it , it check for update again. It means that I can update the firmware via ota?
Click to expand...
Click to collapse
Magisk probably hides the bootloader status so that update check works, but it will most likely fail during install. At least that's how it works on moto one and moto one power.
On moto one I either reflash current build without wipe and then take ota and re-root after, or just flash the update if I get them early, and re-root-
AndresOrue said:
It means that I can update the firmware via ota?
Click to expand...
Click to collapse
I don't think it's possible. The system must be completely virgin to update the OTA. Then why do I need a Root? I need it to customize the system.
ilia3367 said:
I don't think it's possible. The system must be completely virgin to update the OTA. Then why do I need a Root? I need it to customize the system.
Click to expand...
Click to collapse
Thanks a lot. I just unlocked my BL for the second time and this root method is working fine.
May I ask if you just used magisk manager to patch boot, cause when I do I get error on flash.
Code:
(bootloader) is-logical:boot_a: not found
Sending 'boot_a' (33792 KB) OKAY [ 1.172s]
Writing 'boot_a' FAILED (Status read failed (Too many links))
And how did you patch vbmeta?
I'm just curious since this patched boot isn't the latest and I wonder how to make this work with the latest boot.img from September patch update.