Related
Who should read this post?
You have updated your One X to a newer version via OTA, then you want to restore the software/ return stock but the latest RUU is not available. (boot to fastboot mode and type the following command "fastboot getvar version-main", This is the true version of your phone!)
You have some basic skills to flash things using "fastboot"
Those who want to back to stock and wait for the JB OTA.
Those with ICS hboot should works without any problem, someone had test it on JB hboot and works(updated in step 6, 7). but we need more testers.
The concept behind.
1. Fool the RUU to make it believe that it is flashing the latest ROM, but actually, we are flashing an older version.
2. after that, boot up the phone with older version of software, then OTA and update the phone to latest software.
How to do that?
0. backup all your stuff including those in SD, all your stuff in your phone will be lost. Then wipe all data (including SD) using your custom recovery. (important! Otherwise, you may not be able to receive OTA).
1. You have to download a "custom RUU" that can be found here.
http://db.tt/z8ajRTuH
Feel free to give a thanks to billd2439, he provide this working link to download the custom RUU.
Just go to #115 http://forum.xda-developers.com/showthread.php?p=35139501#post35139501 and give him a thanks
2. Download the ROM file, it should be in zip format. (You can also extract the rom file by running a RUU, just run the RUU, don't click anything and search the computer for "rom.zip") (In my case, I have an older version 1.29.708.15 rom extracted from RUU)
you may want to find RUU here http://www.htcruu.com
3. unzip the customRUU.zip to a folder, e.g. "customRUU"
4. unzip and extract "android-info.txt", "boot_signed.img" and "system.img" to a folder
5. open android-info.txt with "notepad" (notepad++ is highly recommended)
6. type the following command to get the information from your phone.
fastboot getvar all
you should pay attention to the following information
modelid:
cidnum:
mainver:
hbootpreupdate:
7. edit the value of "modelid", "cidnum", "mainver" and "hbootpreupdate" to match the information you get from step 6.
by doing this your will try to fool the RUU to belive that you are going to flash a newer version e.g (I have OTA my phone to 2.17.708.7, but now I want to fool the RUU with this old rom with a version number of 1.29.708.15, so I change the value to 2.17.708.7 )
Thanks ahmedaljaf for telling me to modify hbootpreupdate to makes JB downgrade works
8. save the file.
9. zip "android-info.txt", "boot_signed.img" and "system.img" and rename the zip to "rom.zip". (remember only zip the files, not the whole folder!)
10. place the "rom.zip" you just created to the "customRUU" folder
11. make sure your phone is still "unlock", remember to turn on USB Debugging, unplug the USB cable and reboot your phone, then goto fastboot mode and connect the USB cable.
(important, do the above to avoid error messages in RUU)
12. run the file "ARUWizard.exe" inside the folder "customRUU" (see the Attached Readme_Eng.pdf if the customRUU cannot display in correct language)
You can change the customRUU to English version by just delete or rename the language file "ARUWizard_Eng.lng" (Thanks ahmedaljaf for telling me this :good
13. follow the on screen instruction,
14. your phone should reboot and boot up with and old version of software.
15. restart the phone and go to fastboot mode.
16. extract the "recovery_signed.img" from your old "rom.zip" (not the rom.zip you create! ) and place it to some where.
17. flash the recovery by typing the following command "fastboot flash recovery recover_signed.img"
18. relock the phone
19. boot up the phone and try OTA
18. if the OTA download finish but fail to reboot to recovery update automatically, just manually boot to recovery and the update will be ok.
If you can return stock with this method, please reply and list the version here. And you can give me a "thanks" :good:
I wonder, if you put in the "rom.zip" the "hboot_0.95.0000.img" from an older RUU will you be able to downgrade the 1.28 hboot also?
There's NO way to downgrade hboot unless you have s-off.
Sent from my HTC One X using xda premium
ionut.micu said:
I wonder, if you put in the "rom.zip" the "hboot_0.95.0000.img" from an older RUU will you be able to downgrade the 1.28 hboot also?
Click to expand...
Click to collapse
They are somebody on chinese forum who use this method claimed he was able to do hboot downgrade through this method, but no one seem suceed so for.
Well, technically this method able to get you spoof ROM version because it check on your PC. While for hboot it validate the signature and version on the phone before upgrading itself. You can see the process if you push the firmware yourself via fastboot.
HebeGuess said:
They are somebody on chinese forum who use this method claimed he was able to do hboot downgrade through this method, but no one seem suceed so for.
Well, technically this method able to get you spoof ROM version because it check on your PC. While for hboot it validate the signature and version on the phone before upgrading itself. You can see the process if you push the firmware yourself via fastboot.
Click to expand...
Click to collapse
What if we hex edit the 0.95.0000 before we put it into the rom.zip to make it think that it's a newer version, will that brake the signature?
Sorry but I don't have the guts to try it myself
a good link
hokoonho said:
Who should read this post?
You have updated your One X to a newer version via OTA, then you want to restore the software/ return stock but the latest RUU is not available.
You have some basic skills to flash things using "fastboot"
Those who want to back to stock and wait for the JB OTA.
The concept behind.
1. Fool the RUU to make it believe that it is flashing the latest ROM, but actually, we are flashing an older version.
2. after that, boot up the phone with older version of software, then OTA and update the phone to latest software.
How to do that?
0. backup all your stuff including those in SD, all your stuff in your phone will be lost.
1. You have to download a "custom RUU" that can be found here (you can also found a rom that for One X for HK only).
http://pan.baidu.com/share/link?shareid=64762&uk=1042525484
If your phone is from other region, you may want to find the rom or RUU here http://www.htcruu.com
2. Download the ROM file, it should be in zip format. (You can also extract the rom file by running a RUU, just run the RUU, don't click anything and search the computer for "rom.zip") (In my case, I have an older version 1.29.708.15 rom extracted from RUU)
3. unzip the customRUU.zip to a folder, e.g. "customRUU"
4. unzip and extract "android-info.txt", "boot_signed.img" and "system.img" to a folder
5. open android-info.txt with "notepad" (notepad++ is highly recommended)
6. edit the value of"cidnum" to match your phone, e.g. ("HTC__622" for HK, "HTC__621" for Taiwan)
7. edit the value of "mainver" to the current software version your phone. e.g (I have OTA my phone to 2.17.708.7, but now I want to fool the RUU with this old rom with a version number of 1.29.708.15, so I change the value to 2.17.708.7 )
8. save the file.
9. zip "android-info.txt", "boot_signed.img" and "system.img" and rename the zip to "rom.zip". (remember only zip the files, not the whole folder!)
10. place the "rom.zip" you just created to the "customRUU" folder
11. make sure your phone is still "unlock"
12. run the file "ARUWizard.exe" inside the folder "customRUU"
13. follow the on screen instruction,
14. your phone should reboot and boot with and old version of software.
15. restart the phone and go to fastboot mode.
16. extract the "recovery_signed.img" from your old "rom.zip" (not the rom.zip you create! ) and place it to some where.
17. flash the recovery by typing the following command "fastboot flash recovery recover_signed.img"
18. relock the phone
19. boot up the phone and try OTA
18. if the OTA download finish but fail to reboot to recovery update automatically, just manually boot to recovery and the update will be ok.
Click to expand...
Click to collapse
link to custom ruu its dead. any alternative?
ionut.micu said:
I wonder, if you put in the "rom.zip" the "hboot_0.95.0000.img" from an older RUU will you be able to downgrade the 1.28 hboot also?
Click to expand...
Click to collapse
No, if you include the old hboot, the process will be fail.
Sent from my HTC One X using xda premium
darckreign1984 said:
link to custom ruu its dead. any alternative?
Click to expand...
Click to collapse
link updated, enjoy
Sent from my HTC One X using xda premium
or you could just cook yourself a flashable zip from the rom.zip. Then fastboot flash rec and boot. Chances are ics wont boot on the newer hboots. Still the ota can be flashed as update.zip maybe.
usefull for some case
bookmarked
BRILLIANT! Absolutely brilliant! Thanks a million hokoonho. This method worked like a treat on my HK_621 HOX which was running ARHD 9.7.2
unsucces
speedofheat said:
BRILLIANT! Absolutely brilliant! Thanks a million hokoonho. This method worked like a treat on my HK_621 HOX which was running ARHD 9.7.2
Click to expand...
Click to collapse
arhd 12 and hboot 1.28 - not working
the 10 min time to flash its useles.... nothing its flashing in this time
darckreign1984 said:
arhd 12 and hboot 1.28 - not working
the 10 min time to flash its useles.... nothing its flashing in this time
Click to expand...
Click to collapse
The method works well with ICS, even with other HTC model as well, but I am not sure if it still work will JB and latest hboot. But it won't kill your phone.
Sent from my HTC One X using xda premium
I have followed the instructions, and now I am at the point where I run "ARUWizard" and follow the onscreen instructions...
However, The test is not English, it is funny looking as if the language is corrupt/unrecognised.
See attachment.
Any advice?
lukems said:
I have followed the instructions, and now I am at the point where I run "ARUWizard" and follow the onscreen instructions...
However, The test is not English, it is funny looking as if the language is corrupt/unrecognised.
See attachment.
Any advice?
Click to expand...
Click to collapse
It's OK, The RUU may not be able to select the right language to display, but It still works, since the RUU only use adb and fastboot to finish its process, and all these adb and fastboot are run in English...
A brief translation was made for those cannot Open the customRUU in correct language. go to OP for the pdf file
hokoonho said:
It's OK, The RUU may not be able to select the right language to display, but It still works, since the RUU only use adb and fastboot to finish its process, and all these adb and fastboot are run in English...
I am translating the Text to English and will upload a guide, just follow the guide to click the buttons... wait for a few minutes please.
Click to expand...
Click to collapse
No problem, I have found an English version.
I am finding that I get a Error 170 USB error... I believe this is because I have an unlocked bootloader.
So I re-locked the bootloader... and found myself unable to get past the bootloader.
I managed to run the RUU whilst phone was at the bootloader screen,
Replaced the temp rom.img with the created rom.img in your guide,
But it ended up failing with a Error 132 signature check.
I am not sure how to proceed.
lukems said:
No problem, I have found an English version.
I am finding that I get a Error 170 USB error... I believe this is because I have an unlocked bootloader.
So I re-locked the bootloader... and found myself unable to get past the bootloader.
I managed to run the RUU whilst phone was at the bootloader screen,
Replaced the temp rom.img with the created rom.img in your guide,
But it ended up failing with a Error 132 signature check.
I am not sure how to proceed.
Click to expand...
Click to collapse
Could you provide a ling to the English version you've got ? Thanks
lukems said:
No problem, I have found an English version.
I am finding that I get a Error 170 USB error... I believe this is because I have an unlocked bootloader.
So I re-locked the bootloader... and found myself unable to get past the bootloader.
I managed to run the RUU whilst phone was at the bootloader screen,
Replaced the temp rom.img with the created rom.img in your guide,
But it ended up failing with a Error 132 signature check.
I am not sure how to proceed.
Click to expand...
Click to collapse
Don't relock at this moment, otherwise, you will not be able to flash the stock recovery. Unlock it first. Make sure USB debugging is on, then REBOOT to fastboot and start the RUU. Or...Try another USB cable, DON'T connect via a USB hub...
Sent from my HTC One X using xda premium
hokoonho said:
Don't relock at this moment, otherwise, you will not be able to flash the stock recovery. Unlock it first. Make sure USB debugging is on, then REBOOT to fastboot and start the RUU. Or...Try another USB cable, DON'T connect via a USB hub...
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Ok will try now.
Edit: I am now waiting for it to finish... we will see soon enough if it works.
Screenshot showing upgrade screen uploaded.
Edit 2: It completed successfully
build downgraded from 2.17.401.2 to 1.28.771.9
lukems said:
I have followed the instructions, and now I am at the point where I run "ARUWizard" and follow the onscreen instructions...
However, The test is not English, it is funny looking as if the language is corrupt/unrecognised.
See attachment.
Any advice?
Click to expand...
Click to collapse
lukems said:
Ok will try now.
Click to expand...
Click to collapse
I have updated step 11. should disconnect the USB cable during reboot. If it still not work, restart both your phone and PC.
Hello guys ,
i hope some one can help me in that case . i just a m8 one mobile from an online site
it's good but when i have tried to update it this message appeared :
'Variant system version - We have determined that your phone may be running a modified version of its system software. For your protection, we cannot update your phone. Please revert your phone to the official HTC system software to update your phone. If you did not modify your system software or would like help reverting your system please contact us via the support section at HTC - Mobile Phones, Smartphones, Cell Phones, Tablets'
And that some of information what i can got .
***Software status: Modified***
***UNLOCKED***
M8_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.24.21331147A1.09G
OpenDSP-v48.2.2-00564-M8974_FO.1211
OS-4.18.708.12
eMMC-boot 2048MB
Jan 15 2015, 23:49:38.0
Software number : 3.28.709.5
Baseband Version : 1.24.21331147A1.09G_20.68.4196.01_F
Build number : 3.28.709.5 CL389838 release-keys
So If you want more information tell me how i can get it to you
So please help me guys
Hello,
Please provide your phone's CID & MLDELID. To solve this problem, you need to either restore a stock firmware & stock twrp backup, or flash a stock RUU. Either way, the firmware & software must have matching cid & modelid.
As of right now, the data you posted indicate that your phone has mismatching firmware & software (x.xx.708 and x.xx.709).
Cheers
I'm really sorry i don't know how to get the information so, Could you please tell me how i can provide you phone's CID & MLDELID ? i mean the steps for it !
Mike Smaan said:
I'm really sorry i don't know how to get the information so, Could you please tell me how i can provide you phone's CID & MLDELID ? i mean the steps for it !
Click to expand...
Click to collapse
Install Terminal Emulator for Android from Google Play Store. Run commands:
getprop ro.cid
getprop ro.mid
rv_30 ! Thank you man
i got them my cid : HTC_622
And my Mid : OP6B63000
shirreer said:
Hello,
Please provide your phone's CID & MLDELID. To solve this problem, you need to either restore a stock firmware & stock twrp backup, or flash a stock RUU. Either way, the firmware & software must have matching cid & modelid.
As of right now, the data you posted indicate that your phone has mismatching firmware & software (x.xx.708 and x.xx.709).
Cheers
Click to expand...
Click to collapse
i got them my cid : HTC_622
And my Mid : OP6B63000
Mike Smaan said:
i got them my cid : HTC_622
And my Mid : OP6B63000
Click to expand...
Click to collapse
Your device is Asia-HK-CHT variant.
Please visit the link below to find answers and links that resolve your exact issue:
http://forum.xda-developers.com/htc-one-m8/help/help-returning-to-stock-hon-kong-htc-t3005829
There are links to stock RUU directly from HTC as well as twrp backup+firmware for you.
Good luck
shirreer said:
Your device is Asia-HK-CHT variant.
Please visit the link below to find answers and links that resolve your exact issue:
http://forum.xda-developers.com/htc-one-m8/help/help-returning-to-stock-hon-kong-htc-t3005829
There are links to stock RUU directly from HTC as well as twrp backup+firmware for you.
Good luck
Click to expand...
Click to collapse
Thank you for trying help me , but unfortunately the link from jan,2015 it's not working or missed . and i'm really want back to to stop or do any thing to update the phone
I'm sorry for bothering you sir
Mike Smaan said:
Thank you for trying help me , but unfortunately the link from jan,2015 it's not working or missed . and i'm really want back to to stop or do any thing to update the phone
I'm sorry for bothering you sir
Click to expand...
Click to collapse
It's no bother, but, you missed the post that says:
Originally Posted by xunholyx *
Okay. So I did a little research and came up with an official HTC RUU for your phone. As far as I know, it is the latest for the Hong Kong version (4.4.3). I say as far as I know because I don't deal with HK versions very often here.
Hook up to your PC and get into ADB/fastboot.
Download the official RUU from HTC's website by clicking here.
http://dl4.htc.com/RomCode/Source_and_Binaries/m8uhl-3.4.0-gf17cce1.zip
Reply
Thanks to your help, I have successfully returned to stock! Thank you for the kind and quick reply!
shirreer said:
It's no bother, but, you missed the post that says:
Originally Posted by xunholyx *
Okay. So I did a little research and came up with an official HTC RUU for your phone. As far as I know, it is the latest for the Hong Kong version (4.4.3). I say as far as I know because I don't deal with HK versions very often here.
Hook up to your PC and get into ADB/fastboot.
Download the official RUU from HTC's website by clicking here.
http://dl4.htc.com/RomCode/Source_and_Binaries/m8uhl-3.4.0-gf17cce1.zip
Reply
Thanks to your help, I have successfully returned to stock! Thank you for the kind and quick reply!
Click to expand...
Click to collapse
that link isn't exist and when i downloaded the offical rom for M8 called :
RUU_M8[email protected]50319A_40.45.C33065.00_F_release_446225_signed_2
while updating error came called " Model ID ERROR " ..
So what i should do now ?
Mike Smaan said:
that link isn't exist and when i downloaded the offical rom for M8 called :
RUU_M8[email protected]50319A_40.45.C33065.00_F_release_446225_signed_2
while updating error came called " Model ID ERROR " ..
So what i should do now ?
Click to expand...
Click to collapse
Here's a thread with a link for the firmware you need. Follow the instructions on how to properly install your firmware. http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
---------- Post added at 01:58 PM ---------- Previous post was at 01:54 PM ----------
The firmware you tried to install is not the correct one for your phone. Scroll down to the firmware for your CID: HTC__622 and MID: 0P6B63000 and you should be fine.
Mike Smaan said:
that link isn't exist and when i downloaded the offical rom for M8 called :
RUU_M8[email protected]50319A_40.45.C33065.00_F_release_446225_signed_2
while updating error came called " Model ID ERROR " ..
So what i should do now ?
Click to expand...
Click to collapse
You can't just flash any file you please. RUU & firmware you want to flash MUST be specific for your device's region and variant model - in your case, you must flash ASIA-HK-CHT firmware & software. ATT & CINGULAR are US specific, and will not flash on your phone without modifications.
Instead, download the 1.60.x.x from the link provided by @Jerrel7, and the TWRP stock backup from 1.60.708.x provided below:
https://mega.co.nz/#!e8AFCCQZ!2-2Lx1vxkg1xBq_Yhg_Sk9AOzdZsPrX2oOlxy-PLTF0
Flashing the 1.60.x.x firmware and restoring the 1.60.x.x twrp backup will put your device in a stock condition that will allow you to receive official updates from HTC.
Cheers
P.S. let us know if you need help restoring the backup or flashing the firmware.
shirreer said:
You can't just flash any file you please. RUU & firmware you want to flash MUST be specific for your device's region and variant model - in your case, you must flash ASIA-HK-CHT firmware & software. ATT & CINGULAR are US specific, and will not flash on your phone without modifications.
Instead, download the 1.60.x.x from the link provided by @Jerrel7, and the TWRP stock backup from 1.60.708.x provided below:
https://mega.co.nz/#!e8AFCCQZ!2-2Lx1vxkg1xBq_Yhg_Sk9AOzdZsPrX2oOlxy-PLTF0
Flashing the 1.60.x.x firmware and restoring the 1.60.x.x twrp backup will put your device in a stock condition that will allow you to receive official updates from HTC.
Cheers
P.S. let us know if you need help restoring the backup or flashing the firmware.
Click to expand...
Click to collapse
Sir i'm going to try it .. but unfortunately i don't know the way to flashing firmware and install twrp or recovery ! i'm always got unknown error like in Fastboot i don't Device offline ... daemon not running - something like that .. ! so please i need step by step what i have to do first because it's my first time to do software
Thank you for your time
Hello. I had the same problem. Just solved it yesterday. The whole problem was in my MID. You have to change it for the RUU you want to install.
I was with MID for Singapore and i wanned to install European version. So i can't install the updates. After i changed the MID now i'm able to install every update.
Just follow this thread and you're done. Good luck, mate!
http://forum.xda-developers.com/showthread.php?t=2708581
Jared89 said:
Hello. I had the same problem. Just solved it yesterday. The whole problem was in my MID. You have to change it for the RUU you want to install.
I was with MID for Singapore and i wanned to install European version. So i can't install the updates. After i changed the MID now i'm able to install every update.
Just follow this thread and you're done. Good luck, mate!
http://forum.xda-developers.com/showthread.php?t=2708581
Click to expand...
Click to collapse
@Mike Smaan problem is a bit different from yours and he has a S-On device.
His problem is his device is running a Taiwan ROM on a Hong Kong variant device.
He needs to run a Hong Kong ROM to solve his problem and the right ROM version (4.18.708.12)
then he can OTA to the latest Marshmallow 6.16.708.1
Should he followed the link provided by @Jerrel7 on post #11, he should be able to fix his problem as simple as ABC.
Mike Smaan said:
Sir i'm going to try it .. but unfortunately i don't know the way to flashing firmware and install twrp or recovery ! i'm always got unknown error like in Fastboot i don't Device offline ... daemon not running - something like that .. ! so please i need step by step what i have to do first because it's my first time to do software
Thank you for your time
Click to expand...
Click to collapse
Very well. Assuming you downloaded the twrp backup and stock firmware from my previous post, proceed as follows:
1. Download HTC Sync from the link below:
http://www.htc.com/uk/support/software/htc-sync-manager.aspx
If you already have HTC Sync installed, then upgrade it to the latest version. Otherwise, install the one from the link provided.
Reboot your PC.
2. Download the FASTBOOT PACKAGE from the link below:
https://drive.google.com/file/d/0B8L4pkbzdlR3eTlJSjdKVEdHX1U/view
Extract the file to "c:\fastboot" folder.
3. Download twrp 2.7.0.2 from:
https://dl.twrp.me/m8/
Extract the file to "c:\fastboot" folder.
4. Put the 1.60.708.x firmware zip you downloaded from my previous post into the "c:\fastboot" folder but don't extract it.
Summary:
You should now have:
A. the latest HTC SYNC installed.
B. A folder called fastboot in the root directory of your C:\ drive.
C. Your fastboot folder has the following files:
I. twrp 2.7.0.2.img
II. The zip file for 1.60.x.x firmware
III. htc _fastboot.exe
Let me know when you're done.
shirreer said:
Very well. Assuming you downloaded the twrp backup and stock firmware from my previous post, proceed as follows:
1. Download HTC Sync from the link below:
http://www.htc.com/uk/support/software/htc-sync-manager.aspx
If you already have HTC Sync installed, then upgrade it to the latest version. Otherwise, install the one from the link provided.
Reboot your PC.
2. Download the FASTBOOT PACKAGE from the link below:
https://drive.google.com/file/d/0B8L4pkbzdlR3eTlJSjdKVEdHX1U/view
Extract the file to "c:\fastboot" folder.
3. Download twrp 2.7.0.2 from:
https://dl.twrp.me/m8/
Extract the file to "c:\fastboot" folder.
4. Put the 1.60.708.x firmware zip you downloaded from my previous post into the "c:\fastboot" folder but don't extract it.
Summary:
You should now have:
A. the latest HTC SYNC installed.
B. A folder called fastboot in the root directory of your C:\ drive.
C. Your fastboot folder has the following files:
I. twrp 2.7.0.2.img
II. The zip file for 1.60.x.x firmware
III. htc _fastboot.exe
Let me know when you're done.
Click to expand...
Click to collapse
I did all that but what do you mean about the zip file for 1.60.xx firmware .. do you mean M8_1.60.708.2.zip ?
And tell me the next step
Mike Smaan said:
I did all that but what do you mean about the zip file for 1.60.xx firmware .. do you mean M8_1.60.708.2.zip ?
And tell me the next step
Click to expand...
Click to collapse
Yes, I did mean M8_1.60.708.2.zip
Now, buckle up...
There are 4 easy steps to accomplish the task:
1. Flash twrp custom recovery. 2. Restore the twrp backup. 3. Flash the stock firmware. 4. Profit.
Let's get down to business:
1. Flash twrp custom recovery:
A. Boot your phone into fastboot. You do this by turning your phone off, then hold Vol- and power button. You're presented with a menu, choose fastboot (navigate the menu using vol+ and vol-) and press power to select.
B. connect your phone to your PC. Open a cmd window:
Type:
cd c:\fastboot
fastboot flash recovery twrp-2.7.0.2-m8.img
Flashing will take a few seconds, when its done, type:
fastboot erase cache
Now, on your phone, select "hboot", then "recovery", to boot into twrp.
2. Restore the twrp backup:
Unfortunately, twrp doesn't immediately create the directory structure for where you'll put the backup file you downloaded. So, we're going to start by creating a backup of your current ROM:
A. Select Backup button in twrp. Select "external sdcard" from the menu at the top, and proceed to create the backup.
B. On your computer, extract the twrp backup file you downloaded, and copy the extracted directory to your phone's sd card. Put it in:
/sdcard/twrp/backups/"serial number"/
C. On your phone, tap restore, and choose the backup directory you just copied to your sdcard. Proceed to restore.
D. Choose to restart your phone and select Bootloader.
E. Select fastboot.
3. Flash the stock firmware:
A. On your PC's cmd window, type:
fastboot oem rebootRUU
B. WAIT UNTIL your phone displays black screen with HTC in white, then type:
fastboot flash firmware M8_1.60.708.2.zip
C. Once more, type:
fastboot flash firmware M8_1.60.708.2.zip
D. Reboot by Typing:
fastboot reboot
4Profit.
shirreer said:
Yes, I did mean M8_1.60.708.2.zip
Now, buckle up...
There are 4 easy steps to accomplish the task:
1. Flash twrp custom recovery. 2. Restore the twrp backup. 3. Flash the stock firmware. 4. Profit.
Let's get down to business:
1. Flash twrp custom recovery:
A. Boot your phone into fastboot. You do this by turning your phone off, then hold Vol- and power button. You're presented with a menu, choose fastboot (navigate the menu using vol+ and vol-) and press power to select.
B. connect your phone to your PC. Open a cmd window:
Type:
cd c:\fastboot
fastboot flash recovery twrp-2.7.0.2-m8.img
Flashing will take a few seconds, when its done, type:
fastboot erase cache
Now, on your phone, select "hboot", then "recovery", to boot into twrp.
2. Restore the twrp backup:
Unfortunately, twrp doesn't immediately create the directory structure for where you'll put the backup file you downloaded. So, we're going to start by creating a backup of your current ROM:
A. Select Backup button in twrp. Select "external sdcard" from the menu at the top, and proceed to create the backup.
B. On your computer, extract the twrp backup file you downloaded, and copy the extracted directory to your phone's sd card. Put it in:
/sdcard/twrp/backups/"serial number"/
C. On your phone, tap restore, and choose the backup directory you just copied to your sdcard. Proceed to restore.
D. Choose to restart your phone and select Bootloader.
E. Select fastboot.
3. Flash the stock firmware:
A. On your PC's cmd window, type:
fastboot oem rebootRUU
B. WAIT UNTIL your phone displays black screen with HTC in white, then type:
fastboot flash firmware M8_1.60.708.2.zip
C. Once more, type:
fastboot flash firmware M8_1.60.708.2.zip
D. Reboot by Typing:
fastboot reboot
4Profit.
Click to expand...
Click to collapse
I did all steps and i got backup ! but unfortunately when i wrote fastboot flash firmware M8_1.60.708.2.zip i got error called " error : cannot open ' M8_1.60.708.2.zip '
Should i try it with that way :-
B. On your computer, extract the twrp backup file you downloaded, and copy the extracted directory to your phone's sd card. Put it in:
/sdcard/twrp/backups/"serial number"/
C. On your phone, tap restore, and choose the backup directory you just copied to your sdcard. Proceed to restore.
D. Choose to restart your phone and select Bootloader.
Mike Smaan said:
I did all steps and i got backup ! but unfortunately when i wrote fastboot flash firmware M8_1.60.708.2.zip i got error called " error : cannot open ' M8_1.60.708.2.zip '
Click to expand...
Click to collapse
I know that you ignored my previous posts and other people post who tried to help you with proper method .. but I still pity you and I don't want to see you'll end up in a brick or soft brick due to wrong commands/instructions.
You get error when flashing firmware - reasons :
1. That command given to you to flash firmware - fastboot flash firmware M8_1.60.708.2.zip - is wrong.
The right command is fastboot flash zip M8_1.60.708.2.zip
Running a wrong command may brick your device but you are lucky because your device is S-On, so no harm just error.
2. Being a S-On device, you won't be able to install a very low version firmware 1.60.708.2 when your current one is 4.18.708.12
Only S-Off device can do that. To have S-Off you need to spend USD25 for the app .. and are you willing to spend USD25 to S-Off when you can fix your problem with proper method free of charge and needs only 2 main steps : ?
1. Restore 4.18.708.12 TWRP backup
2. Install 4.18.708.12 stock recovery.img
then you can update to the latest - 6.16.708.1
Mike Smaan said:
Should i try it with that way :-
B. On your computer, extract the twrp backup file you downloaded, and copy the extracted directory to your phone's sd card. Put it in:
/sdcard/twrp/backups/"serial number"/
C. On your phone, tap restore, and choose the backup directory you just copied to your sdcard. Proceed to restore.
D. Choose to restart your phone and select Bootloader.
Click to expand...
Click to collapse
You can try these B., C., and D.
But, again using a very low version 1.60.708.2 backup on a Lollipop firmware 4.18.708.12, you may have one of these :
1. It will be successful updates but you need to do many OTAs
1.60.708.2 --> 2.11.708.2 --> 3.32.708.4 --> 4.18.708.12 --> 6.16.708.1
If it is successful then it's good but if it is not, you'll get below.
2. You may have a blank screen either between OTA 1.60.708.2 --> 2.11.708.2 or OTA 2.11.708.2 --> 3.32.708.4
3. You may lost your wifi connectivity either between OTA 1.60.708.2 --> 2.11.708.2 or OTA 2.11.708.2 --> 3.32.708.4 but you can proceed further with your mobile data or use a Internet Pass through on your PC
One last note ... never use a 2.7.0.2 TWRP recovery as that is the most buggiest TWRP which will remove your OS version on your bootloader.
Good luck.
You may find that you need to return to stock/locked bootloader for various reasons. You can find how to do this by digging throughout various threads on this forum. decided to simplify things and bring it together in a single thread. After restoring you will be able to do OTA updates as well.
FLASHING FACTORY 5.8.019S
STEP 1: Download the backup
-- Source Thread: https://forum.xda-developers.com/le-pro3/how-to/le-pro-3-lex727-twrp-backup-eui-5-8-019s-t3504761
-- FILE: https://drive.google.com/file/d/0B5xyvHc4wgEVWHFKMWZqLWEyTTg/view?usp=sharing
Note: There is a TWRP backup for 20s currently on this forum. I do not recommend using it. Many have had issues booting after restoring it (me included).
STEP 2: Setup TWRP Backup Directory
If you download it to your PC use adb to push it to your device. You should have an existing directory within /sdcard/TWRP/BACKUPS/ that holds your backups. I believe the directory is your device id.
If the directory does not exist, you need to get the info from your device.
Code:
Run adb devices
It will be the hash listed by your device. Make a directory in TWRP/BACKUPS/ with the device id. Mine is "6293eaef".
For example, any backups that I want to restore to my device from TWRP need to be located in a sub-directory within: /sdcard/TWRP/BACKUPS/6293eaef/
At that point you should have the directory you need to copy the backup into.
STEP 2: Copy the Backup (originally named TWRP.zip) to /sdcard/TWRP/BACKUPS/6293eaef/stock
Do the following if you downloaded it to your computer:
Code:
adb push TWRP.zip /sdcard/TWRP/BACKUPS/DEVICE_ID/stock/
adb shell
cd /sdcard/TWRP/BACKUPS/DEVICE_ID/stock/
unzip TWRP.zip
If you downloaded to your device, you just need to move the zip file to the TWRP backups directory and extract it.
STEP 3: Restore in TWRP
Boot into TWRP recovery (if not already there).
Code:
adb reboot recovery
OR
Code:
hold volume up and press power button
RESTORE the backup.
I selected everything. This will install default recovery and remove TWRP.
Do a FULL wipe AFTER flashing. Be sure to wipe the data partition to clear any encryption.
[OPTIONAL] RESTORE LOCKED BOOTLOADER X727
This should not be necessary for X720 devices because the bootloader comes unlocked. I would only suggest re-locking if you need to return your device for warranty support.
To lock the bootloader you need to flash emmc_appsboot.mbn and xbl.elf from an OTA
Step 1: Get 5.8.020s OTA
-- File: https://www.androidfilehost.com/?fid=457095661767124419
After downloading extract 5.8.020S_sta.zip.
Inside the firmware-update folder are 2 files: xbl.elf, and emmc_appsboot.mbn. You need to flash both of these files in the bootloader to relock it.
Step 2: Boot to fastboot
Code:
adb reboot bootloader
OR
Code:
From power off, hold volume down and then press the power button.
Step 3: Flash stock bootloader from OTA zip
Run the following commands while in the firmware-update folder you extracted from 5.8.020S_sta.zip
Code:
fastboot flash xbl xbl.elf
fastboot flash aboot emmc_appsboot.mbn
The bootloader is now locked again.
Run
Code:
fastboot reboot bootloader
and then
Code:
fastboot oem device-info
to verify.
NOTE: I found that after using this method to re-lock the bootloader I could no longer use the guide for persistent bootloader unlocking.
If you want to unlock the bootloader again later, you need to manually flash the emmc_appsboot.mbn from the file in this thread:
https://forum.xda-developers.com/le...7-model-persistent-bootloader-unlock-t3500388
FILE: https://www.androidfilehost.com/?fid=313042859668275431
I hope that some of you find this helpful. Please let me know if there is any additional information that I should add to this thread. I will update it as needed.
Cheers!
STEP 1
file in google drive not found
Sorry, the file you have requested does not exist.
Make sure that you have the correct URL and the file existed.
ajegile said:
STEP 1
file in google drive not found
Sorry, the file you have requested does not exist.
Make sure that you have the correct URL and the file existed.
Click to expand...
Click to collapse
Fixed! That's what I get for copy/pasting the text vs the actual URL.
Hi, sorry to bring up an old thread. I plan to restore my leeco (US version ) running lineage back to stock. Will this method still work?
neozengar said:
Hi, sorry to bring up an old thread. I plan to restore my leeco (US version ) running lineage back to stock. Will this method still work?
Click to expand...
Click to collapse
Yes, this method will still work. It should also work for restoring to newer versions of stock (if needed).
Thank you so much. I notice the boot loader file is for le1. Are they same as that for Le eco pro 3?
neozengar said:
Thank you so much. I notice the boot loader file is for le1. Are they same as that for Le eco pro 3?
Click to expand...
Click to collapse
Yes
Will this work with Lineage 14.1?
Cuvillier said:
Will this work with Lineage 14.1?
Click to expand...
Click to collapse
This will take you back to stock regardless of what ROM you are currently running.
Ok, do you will update the tutorial with new files ? As newer firmware is now 23s version.
Cuvillier said:
Ok, do you will update the tutorial with new files ? As newer firmware is now 23s version.
Click to expand...
Click to collapse
Ill try to get some time to find links for the newer firmwares and update for those. We just had a new little one join the family so I'm pretty busy and tires nowadays .
Regardless, you can always update once you get back to stock in this guide.
Ok thank you.
This will work on x720 too ?
new small ota update for x720 just came out
Cuvillier said:
This will work on x720 too ?
Click to expand...
Click to collapse
Yes
slgooding said:
Yes
Click to expand...
Click to collapse
bootloader in x720 is already unlocked from LeEco
Hello folks,
I am using T.A.R.S. 21S EUI 5.8 USA version and TWRP 3.1.0
How do I return to stock? stock recovery, locked bootloader, and stock ROM so that I can get OTA updates?
I already tried:
https://forum.xda-developers.com/le-...oader-t3539513
I am able to restore successfully, but I am not able to install any OTA update with this and device is stuck with 19S only. I tried both local update and OTA update. UE boots into EUI recovery and says "Installation failed". I tried both 20S and 21S updates.
I think latest is 23S now.
Thanks
Brar
What device?
Hello. I want to return to stock x720 ROM. I won't to flash US version, so I need CN backup? Or how to do?
I flashed custom Recovery (TWRP), Kernel (BlackScreen), OS (AICP) and Root (Magiskv12). Should I flash trough recovery lastest official OS version?
I had to send the phone back to LeEco for repair, so needed to go stock.
Glad I found this post, thanks OP.
I tried the steps, all seemed to work okay, but now I am stuck at the leeco boot logo.
I can get to bootloader:
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
I can also get to stock recovery, wipe data and update with update.zip
I think the phone is missing OS or something.
Please help.
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.
So after you unlocked the boot loader ( see my previous post)
you can start rooting with magisk manager / patching the boot.img from the original firmware
I used this thread in order to get root ; i modified the contents so it would fit the moto phone a bit better:, but thnx goes to Ibolito over at the pixel 3 forums
1 ) Download the latest Android factory image for your device ("see this guide on where to find it.
2 ) Extract the "boot.img" file from the downloaded image and copy it to your phone.
Warning! Make absolutely sure the firmware is exactly the same as the installed one. If not, you might loose touch.
Be aware that LMSA will download the latest firmware, even if it is not yet installed. That might break your touchscreen
Click to expand...
Click to collapse
3 ) Download latest Magisk Manager application on your phone and install it :
Link
4 )Press on the Install Magisk button (the one on the top, not the Magisk Manager), then Install > Select and Patch a File and now select the Boot.img file you extracted earlier. When the process is done, just put the patched boot.img file on your computer in the same folder as your ADB and FASTBOOT tools, the file's name is magisk_patched.img
edit: i received a comment that the name might be something like Magisk_patched_somerandomletters_.img since the latest magisk update
5 ) Enable adb debugging on your phone and connect it to your computer via USB.
Open a command prompt on your computer and migrate to the folder where the ADB and Fastboot tools are located.
(for exemple, for me it's : cd C:\adb).
7 ) Reboot your phone to fastboot by typing adb reboot bootloader
8 ) Flash the Boot.img you just patched with magisk by typing fastboot flash boot magisk_patched.img
extra: You could test a single boot with that image by typing "fastboot boot magisk_patched.img"
if it boots fine you should have root for this single boot / magisk would show as installed.
9 ) When it's done, reboot by typing fastboot reboot
10 ) Open your Magisk Manager app and check if everything is good, and it should be
extra info:
I did worry a bit because the original boot.img is 64 megs , while the patched version is only 12
but i went with it, and it was fine.
good luck to you all
Edit: rewritten entire post so it would look more like a guide, and extra warning because a lot of people seem to loose touch if they don't have the exact same firmware downloaded as on their phone.
Thanks for posting this. I unlocked my bootloader and would like to root like you did.
Do you install magisk first on your phone, then get the magisk_patched file from your phone? Or is the magisk_patched file obtained somewhere else?
testtubebaby said:
Thanks for posting this. I unlocked my bootloader and would like to root like you did.
Do you install magisk first on your phone, then get the magisk_patched file from your phone? Or is the magisk_patched file obtained somewhere else?
Click to expand...
Click to collapse
You need to install the magisk manager
In magisk manager you can click on "install (magisk)"--> "by patching a file"
then you select the file to be patched ( extracted from the original rom )
after that you can copy the patched file from your phone back to the pc and install it via fastboot.
After that magisk is installed
i hope you succeed
pjottrr said:
You need to install the magisk manager
In magisk manager you can click on "install (magisk)"--> "by patching a file"
then you select the file to be patched ( extracted from the original rom )
after that you can copy the patched file from your phone back to the pc and install it via fastboot.
After that magisk is installed
i hope you succeed
Click to expand...
Click to collapse
The firmware I see is the EU firmware. I don't see the GB firmware in the link you posted (it's RETGB). Any idea where I can find the correct firmware?
Sorry, no idea, i found the provided link via google,
testtubebaby said:
The firmware I see is the EU firmware. I don't see the GB firmware in the link you posted (it's RETGB). Any idea where I can find the correct firmware?
Click to expand...
Click to collapse
https://mirrors.lolinet.com/firmware/moto/sofiar/official/
zuggi_m said:
https://mirrors.lolinet.com/firmware/moto/sofiar/official/
Click to expand...
Click to collapse
@zuggi_m , how does posting the same url help?
i don't see a retgb here ....
Maybe someone with more dev experience can tell if you need the exact same firmware or if the version numbers are the same it is ok to use that file ?
No fastbootd?
One Hyper needs fastbootd in order to flash boot and root
mingkee said:
No fastbootd?
One Hyper needs fastbootd in order to flash boot and root
Click to expand...
Click to collapse
i don't really understand the question i guess,
a magisk patched boot is flashed via fastboot. after that you have magisk installed and root access.
pjottrr said:
i don't really understand the question i guess,
a magisk patched boot is flashed via fastboot. after that you have magisk installed and root access.
Click to expand...
Click to collapse
Yours should be G8 Power (9)
Native Android 10 uses fastbootd to flash boot, dtbo, and recovery
mingkee said:
Yours should be G8 Power (9)
Native Android 10 uses fastbootd to flash boot, dtbo, and recovery
Click to expand...
Click to collapse
maybe i'm missing your point here, my description is just so people who have to figure it out can just use my steps to get root, it is indeed based on fastboot flashing . so i'm not sure what you are trying to say, or am i misinterpreting something?
https://forum.xda-developers.com/motorola-one-hyper/development/rom-omnirom-t4044405
I did root on One Hyper (shipped with Android 10) using fastbootd method
Used old method soft brick my One Hyper
That's why I'd like to know
pjottrr said:
so after you unlocked the boot loader ( see my previous post)
you can start rooting with magisk manager / patching the boot.img from the original firmware
I used this thread in order to get root
you need to download the firmware for our device,
That can be found here;
https://mirrors.lolinet.com/firmware/moto/sofiar/official/RETEU/
after that, extract, patch, fastboot install patched version, done.
I did have some issues with the current magisk manager ( from highonandroid, i did find another source, installed version 7.5.1 of the magisk manager from this source
and that one was able to patch the boot.img
I did worry a bit because the original boot.img is 64 megs , while the patched version is only 12
but i went with it, and it was fine.
good luck to you all
Click to expand...
Click to collapse
There's a head up
US version: Sofia
The rest: Sofiar
I will buy US G Power in May and let's the fun begin
Check out One Hyper general to install Dolby Atmos and it can be toggle on/off.
Has anyone tried copying something to the root of the phone or making build.prop edits? I have the Stylus and have achieved root using the same method, however there is something not quite right with the permissions. I cannot make changes to any root files.
CCivale said:
Has anyone tried copying something to the root of the phone or making build.prop edits? I have the Stylus and have achieved root using the same method, however there is something not quite right with the permissions. I cannot make changes to any root files.
Click to expand...
Click to collapse
So you should know G Stylus ROM is Sofiap.
Be aware the way Android 10 flashing is different.
Download and install the latest ADB in order to access fastbootd (fastboot reboot fastboot) and flash boot, recovery, dtbo, vbmeta, and super
Hmmmm, I will have to read more about fastbootd in your other thread.
I did use the boot.img for the sofiap.
Hello,
I followed all the instructions in the first post and was able unlock the bootloader, install magisk, and use it to make the magisk_patched.img file from a boot.img file.
The only variation, was that I got my boot.img file from mirrors.lolinet.com/firmware/moto/sofia/official/RETUS/XT2041-4_SOFIA_RETUS_10_QPM30.80-13-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip since my phone is a US retail model.
After flashing, the phone boots up properly but the touchscreen does not work.
The side buttons do work and I was able to reboot into recovery. In recovery, the build on the phone is indicated as QPM30.80-51. The build in the above indicated file is QPM30.80-13-2. Could this be the source of the problem?
I have tried flashing the original boot.img (from the file above) back and the touchscreen still does not work. I have also tried “wipe data/factory reset” in recovery.
hazd said:
Hello,
I followed all the instructions in the first post and was able unlock the bootloader, install magisk, and use it to make the magisk_patched.img file from a boot.img file.
The only variation, was that I got my boot.img file from mirrors.lolinet.com/firmware/moto/sofia/official/RETUS/XT2041-4_SOFIA_RETUS_10_QPM30.80-13-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip since my phone is a US retail model.
After flashing, the phone boots up properly but the touchscreen does not work.
The side buttons do work and I was able to reboot into recovery. In recovery, the build on the phone is indicated as QPM30.80-51. The build in the above indicated file is QPM30.80-13-2. Could this be the source of the problem?
I have tried flashing the original boot.img (from the file above) back and the touchscreen still does not work. I have also tried “wipe data/factory reset” in recovery.
Click to expand...
Click to collapse
maybe try with the "correct" firmware? ( not sure if the minor diference changes anything, but you could try....
i found it here:
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
pjottrr said:
maybe try with the "correct" firmware? ( not sure if the minor diference changes anything, but you could try....
i found it here:
rsdsecure-cloud.motorola.com/download/SOFIA_RETAIL_QPM30.80-51_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Thanks for finding this link.
Unfortunately i am not able to download this for some reason. I get an access denied error message.
edit:
I was able to find the most recent firmware here:
github.com/AndroidDumps/motorola_sofia_dump/tree/sofia_retail-user-10-QPM30.80-51-bd0b4-release-keys
I downloaded just the boot.img file and flashed it. That fixed the touchscreen issue. I then used magisk to batch the boot.img and I now have root.
Just to be clear, this worked on a US retail moto g power purchased unlocked from best buy. The phone model number is XT2041-4.
Hope this helps.
hazd said:
Thanks for finding this link.
Unfortunately i am not able to download this for some reason. I get an access denied error message.
edit:
I was able to find the most recent firmware here:
github.com/AndroidDumps/motorola_sofia_dump/tree/sofia_retail-user-10-QPM30.80-51-bd0b4-release-keys
I downloaded just the boot.img file and flashed it. That fixed the touchscreen issue. I then used magisk to batch the boot.img and I now have root.
Just to be clear, this worked on a US retail moto g power purchased unlocked from best buy. The phone model number is XT2041-4.
Hope this helps.
Click to expand...
Click to collapse
I downloaded the kernel and waiting for the unit.
I can flash full ROM with fastboot and fastbootd, but just flashing kernel would be much faster.
Moreover, check One Hyper general to get Dolby Atmos because you can turn on and off anytime you want.