Related
This is the official RUU file for the HTC Desire 815 a5_chl, the variant for Virgin Mobile. I got it straight from HTC's website and re-uploaded it for you guys.
Download links:
KitKat RUU
EXE File (Google Drive): https://drive.google.com/file/d/0B4NAwrQOaS7Qa1ZxN29oZWN1Y00/view?usp=sharing
Rom.zip File (Google Drive): https://drive.google.com/file/d/0B4NAwrQOaS7QNXVfUkZwUlhYSzg/view?usp=sharing
Original link (Official HTC): http://www.htc.com/us/support/htc-desire-816-virgin-mobile/news/
Lollipop RUU
EXE File (Google Drive): https://drive.google.com/file/d/0B4NAwrQOaS7QclowVm9RQ1J1RjQ/view
Original link (Official HTC): http://www.htc.com/us/support/htc-desire-816-virgin-mobile/news/
If you are rooted and on a custom ROM, this RUU will still work, you just need to follow some steps.
1. If you can flash a stock backup, do it, just to be safe.
2. Open up super SuperSU, and remove all root from device.
Steps 1 and 2 aren't required, but there precautionary measures.
Now at this point you should boot into HBoot, and be in Fastboot mode.
3. Flash the stock recovery (attached below) and flash it through fastboot with the command "fastboot flash recovery StockRecovery.img"
4. After that, lock your bootloader with the command "fastboot oem lock"
5. After your bootloader is locked and your on the stock recovery, you can RUN the EXE file provided in the download section above. Just follow the instructions the program tells you and everything should run smoothly from there.
6. Profit.
Now, if you don't like the exe, you can also flash the RUU from your phone, without the need for a computer. However you will need an external SD card and the Rom.zip file I've provided above.
1. If you can, flash a stock backup, just to be safe.
2. Open up SuperSU, and remove all root from device.
Steps 1 and 2 aren't required, but there precautionary measures.
Now at this point you should boot into HBoot, and be in Fastboot mode.
3. Flash the stock recovery (attached below) and flash it through fastboot with the command "fastboot flash recovery StockRecovery.img"
4. After that, lock your bootloader with the command "fastboot oem lock"
5. After your bootloader is locked and your on the stock recovery, you can remove the external SD card from the device, and take the Rom.zip file, rename it to "0P9CIMG.zip" and place it on the ROOT of the sdcard.
6. Reboot into Hboot, and as it's rebooting put the sdcard back in the phone. It should automatically detect the RUU file and flash it.
7. Profit.
Download stock recovery HERE.
If you'd like mirrors for the files tell me.
Thanks !
Recovery Issue
I The provided StockRecovery.img will not flash for me apparently because of signature verification. I tried downloading multiple times on phone and PC which is old Windows Vista and may be bad at downloading. Though the file size after download always seems correct. I did restore my stock backup at first BUT it re-roots after reboot.
Fastboot in cmd:
C:\Windows\System32>fastboot flash rec
ery.img
sending 'recovery' (16384 KB)...
OKAY [ 1.886s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 3.064s
Recovery won't start. It shows for A second the "this build is for development purposes only..." flag like from CWM and goes back to bootloader. I should be able to flash A custom recovery again though. Do you know of any "official" recovery downloads for Virgin Mobile A5? I don't know what it is but I have always had trouble finding and flashing stock recoveries for my HTC phones. Even on XDA's DevDB page.
I then tried the RUU exe and that got stuck at "sending... 1/7", assuming because of no recovery. Weird thing is bootloader shows "OS- (1.50.652.3)" in red but it boots to what i had before.
I have not tried to let hboot attempt to install rom.zip.
CrazyJ36 said:
I The provided StockRecovery.img will not flash for me apparently because of signature verification. I tried downloading multiple times on phone and PC which is old Windows Vista and may be bad at downloading. Though the file size after download always seems correct. I did restore my stock backup at first BUT it re-roots after reboot.
Fastboot in cmd:
C:\Windows\System32>fastboot flash rec
ery.img
sending 'recovery' (16384 KB)...
OKAY [ 1.886s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 3.064s
Recovery won't start. It shows for A second the "this build is for development purposes only..." flag like from CWM and goes back to bootloader. I should be able to flash A custom recovery again though. Do you know of any "official" recovery downloads for Virgin Mobile A5? I don't know what it is but I have always had trouble finding and flashing stock recoveries for my HTC phones. Even on XDA's DevDB page.
I then tried the RUU exe and that got stuck at "sending... 1/7", assuming because of no recovery. Weird thing is bootloader shows "OS- (1.50.652.3)" in red but it boots to what i had before.
I have not tried to let hboot attempt to install rom.zip.
Click to expand...
Click to collapse
That's odd. It worked flawlessly for me...
CrazyJ36 said:
I The provided StockRecovery.img will not flash for me apparently because of signature verification. I tried downloading multiple times on phone and PC which is old Windows Vista and may be bad at downloading. Though the file size after download always seems correct. I did restore my stock backup at first BUT it re-roots after reboot.
Fastboot in cmd:
C:\Windows\System32>fastboot flash rec
ery.img
sending 'recovery' (16384 KB)...
OKAY [ 1.886s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 3.064s
Recovery won't start. It shows for A second the "this build is for development purposes only..." flag like from CWM and goes back to bootloader. I should be able to flash A custom recovery again though. Do you know of any "official" recovery downloads for Virgin Mobile A5? I don't know what it is but I have always had trouble finding and flashing stock recoveries for my HTC phones. Even on XDA's DevDB page.
I then tried the RUU exe and that got stuck at "sending... 1/7", assuming because of no recovery. Weird thing is bootloader shows "OS- (1.50.652.3)" in red but it boots to what i had before.
I have not tried to let hboot attempt to install rom.zip.
Click to expand...
Click to collapse
Are you making sure to flash the stock recovery BEFORE re-locking bootloader?
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
Even tried to Download the OTA Normally. Nothing works.
Duh
Thanks. Saw "relocked" on the bootloader and realized I should sleep more.
Updated with exe and now have A fresh phone.
Is there anything special in the update?
jayblaze406
Today, 08:51 PM
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
Even tried to Download the OTA Normally. Nothing works.
3/7 right now on the .exe. thanks. hope this works
jayblaze406 said:
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
Even tried to Download the OTA Normally. Nothing works.
Click to expand...
Click to collapse
Can you get into recovery? If your having the same problem I did then foxydrews suggestion helped.
CrazyJ36 said:
Can you get into recovery? If your having the same problem I did then foxydrews suggestion helped.
Click to expand...
Click to collapse
The .exe just worked perfectly. the OTA Installation from my notification bar kept failing. THANKS for this thread. I previously un-rooted. flashed everything stock. I'm good now. Phone just booted up! Now on the other hand, if ViPER4ANDROID worked on un-rooted phones, I wouldn't have to had gone through all of this lol (and if Google let you uninstall their crap apps).
jayblaze406 said:
The .exe just worked perfectly. the OTA Installation from my notification bar kept failing. THANKS for this thread. I previously un-rooted. flashed everything stock. I'm good now. Phone just booted up! Now on the other hand, if ViPER4ANDROID worked on un-rooted phones, I wouldn't have to had gone through all of this lol (and if Google let you uninstall their crap apps).
Click to expand...
Click to collapse
Glad you figured it out
Custom Rom will be up sometime this week for you guys then insertcoin may follow.
xXminiWHOOPERxX said:
Custom Rom will be up sometime this week for you guys then insertcoin may follow.
Click to expand...
Click to collapse
Just for the VM variant?
Thanks for posting this, had a bit of a scare with my desire this afternoon (ended up just reflashing a backup) but this'll be a good thing to have in my back pocket in case i need it
This saved me today as I was having an issue with a family member's phone not wanting to update OTA because I unlocked and rooted it. Your guide help me put it back to stock and it is now very much stable and usable again. Thank you.
Checksum Please?
FoxyDrew said:
This is the official RUU file for the HTC Desire 815 a5_chl, the variant for Virgin Mobile. I got it straight from HTC's website and re-uploaded it for you guys.
Download links:
EXE File (Google Drive): https://drive.google.com/file/d/0B4NAwrQOaS7Qa1ZxN29oZWN1Y00/view?usp=sharing
Rom.zip File (Google Drive): https://drive.google.com/file/d/0B4NAwrQOaS7QNXVfUkZwUlhYSzg/view?usp=sharing
Original link (Official HTC): http://www.htc.com/us/support/htc-desire-816-virgin-mobile/news/
If you are rooted and on a custom ROM, this RUU will still work, you just need to follow some steps.
1. If you can flash a stock backup, do it, just to be safe.
2. Open up super SuperSU, and remove all root from device.
Steps 1 and 2 aren't required, but there precautionary measures.
Now at this point you should boot into HBoot, and be in Fastboot mode.
3. Flash the stock recovery (attached below) and flash it through fastboot with the command "fastboot flash recovery StockRecovery.img"
4. After that, lock your bootloader with the command "fastboot oem lock"
5. After your bootloader is locked and your on the stock recovery, you can RUN the EXE file provided in the download section above. Just follow the instructions the program tells you and everything should run smoothly from there.
6. Profit.
Now, if you don't like the exe, you can also flash the RUU from your phone, without the need for a computer. However you will need an external SD card and the Rom.zip file I've provided above.
1. If you can, flash a stock backup, just to be safe.
2. Open up SuperSU, and remove all root from device.
Steps 1 and 2 aren't required, but there precautionary measures.
Now at this point you should boot into HBoot, and be in Fastboot mode.
3. Flash the stock recovery (attached below) and flash it through fastboot with the command "fastboot flash recovery StockRecovery.img"
4. After that, lock your bootloader with the command "fastboot oem lock"
5. After your bootloader is locked and your on the stock recovery, you can remove the external SD card from the device, and take the Rom.zip file, rename it to "0P9CIMG.zip" and place it on the ROOT of the sdcard.
6. Reboot into Hboot, and as it's rebooting put the sdcard back in the phone. It should automatically detect the RUU file and flash it.
7. Profit.
Download stock recovery HERE.
If you'd like mirrors for the files tell me.
Click to expand...
Click to collapse
i know we are not supposed to request or ask for ETA's i have seen you all over this forum foxy drew and first want to say thank you but i must ask do you think you could provide us with a MD5Checksum In the OP so we can have something match it against it would really suck to attempt to RUU an invalid zip file for people who are not rooted, i only ask because i am assuming you still have the original file on your computer , if not , i would be happy to download the one from htcs site and yours and verify them and provide it to you , if this is not something you are willing or able to do , well i still thank you for all your effort ,
Failed First Time
Think it was because i was rooted and made to many system changes to the framework jar and build.prop and other various changes, when running RUU it caused fastboot to crash just want every one to know if this happens just run the RUU or the .Zip file again and it should work the second time around not sure if it was already mentioned but everything in this guide seems to have worked just thought i would add my experience.
Thank you so much i made so many system changes it was impossible to OTA and i just wanted to get rid of the notification i dont really care about the update (but did want it) i even tried changing my build number was still getting the notification thank you to the OP GREAT JOB
FoxyDrew said:
This is the official RUU file for the HTC Desire 815 a5_chl, the variant for Virgin Mobile. I got it straight from HTC's website and re-uploaded it for you guys.
Download links:
EXE File (Google Drive): https://drive.google.com/file/d/0B4NAwrQOaS7Qa1ZxN29oZWN1Y00/view?usp=sharing
Rom.zip File (Google Drive): https://drive.google.com/file/d/0B4NAwrQOaS7QNXVfUkZwUlhYSzg/view?usp=sharing
Original link (Official HTC): http://www.htc.com/us/support/htc-desire-816-virgin-mobile/news/
If you are rooted and on a custom ROM, this RUU will still work, you just need to follow some steps.
1. If you can flash a stock backup, do it, just to be safe.
2. Open up super SuperSU, and remove all root from device.
Steps 1 and 2 aren't required, but there precautionary measures.
Now at this point you should boot into HBoot, and be in Fastboot mode.
3. Flash the stock recovery (attached below) and flash it through fastboot with the command "fastboot flash recovery StockRecovery.img"
4. After that, lock your bootloader with the command "fastboot oem lock"
5. After your bootloader is locked and your on the stock recovery, you can RUN the EXE file provided in the download section above. Just follow the instructions the program tells you and everything should run smoothly from there.
6. Profit.
Now, if you don't like the exe, you can also flash the RUU from your phone, without the need for a computer. However you will need an external SD card and the Rom.zip file I've provided above.
1. If you can, flash a stock backup, just to be safe.
2. Open up SuperSU, and remove all root from device.
Steps 1 and 2 aren't required, but there precautionary measures.
Now at this point you should boot into HBoot, and be in Fastboot mode.
3. Flash the stock recovery (attached below) and flash it through fastboot with the command "fastboot flash recovery StockRecovery.img"
4. After that, lock your bootloader with the command "fastboot oem lock"
5. After your bootloader is locked and your on the stock recovery, you can remove the external SD card from the device, and take the Rom.zip file, rename it to "0P9CIMG.zip" and place it on the ROOT of the sdcard.
6. Reboot into Hboot, and as it's rebooting put the sdcard back in the phone. It should automatically detect the RUU file and flash it.
7. Profit.
Download stock recovery HERE.
If you'd like mirrors for the files tell me.
Click to expand...
Click to collapse
i download the rom.zip three different times three different computers all hard wired connections attempted a Linux distro and windows used multiple compression tools 7zip, build in , peazip, winzip , and a few others and the rom file just fails to open , i was however able to extract it from the RUU by running it and pulling it from the temp directory ( i will not post a guide to tihs and you can easily google the procedure or just think about it hard enough if you are technical enough
[email protected] said:
i download the rom.zip three different times three different computers all hard wired connections attempted a Linux distro and windows used multiple compression tools 7zip, build in , peazip, winzip , and a few others and the rom file just fails to open , i was however able to extract it from the RUU by running it and pulling it from the temp directory ( i will not post a guide to tihs and you can easily google the procedure or just think about it hard enough if you are technical enough
Click to expand...
Click to collapse
That's the same way I got the Rom.zip. Your not supposed to open it up?
And don't quote the OP
Help me!!!
Can you help me to get this ruu file on HTC's website??The file broken on internet and didn't work on my desire 816X.
RUU file named 0P9CIMG_A5_UL_K44_DESIRE_SENSE60_hTC_Asia_TW_1.54.709.2_Radio_1.101.1102.17.0506_10.20.4149.00L_release_388245_signed_2.zip
Also Thanks for posting !!!:good::good::good::good:
How to unbrick or get back stock on your Huawei Mate 8. There are many reasons why you would want to do that.
In my case my device (AL10) was stuck at "your device cannot be trusted" after updating from B180 to B321.
First I got to thank acer73 for his software. ajsmsg78 and Kris Chen for their links to the right ROMs.
Also thanks to DarkSilentSC for his help, especially with the L29, great support.
He has a L29, which I don't have, so I'm glad he provides help with that device.
This worked for me on my AL10 to get it back on track, should work on other models too. Just have to find the right ROMSs as according to your model. However, I am not responsible if this does not work for you or if it bricks your phone even more.
And remember: don't forget turning on usb debugging whenever you can!
Unbrick (return to Stock)
1. Find yourself a stock ROM.zip according to your model and extract from the zip the update.app (I used one from a B172 (AL10) Stock ROM, I was running a B180 custom ROM, it worked.)
2. Download the Huawei Update Extractor http://forum.xda-developers.com/showthread.php?t=2433454
3. Extract boot.img, recovery.img, system.img and cust.img with the HuaweiUpateExtractor from the Update.App you find in the ROM to somewhere where you can find them easily
4. Head over to http://forum.xda-developers.com/mate-8/development/rayglobe-italian-knife-t3295526 (You can also do it with fastboot commands, but Acer73's tool makes it easier)
5. get yourself the Italian Knife (btw you probably have to turn off your anti-virus program), extract it in a directory on your PC and start Rayglobe_knife.exe
6. Put the images you have extracted into the folder Unbrick (same directory where you extracted Rayglobe Knife in). The folder was created after you started Rayglobe_Knife.exe
7. Boot your phone into bootloader.
8. In the Rayglobe Knife tool choose Unbrick and choose the option where it says you have placed all the images in the unbrick folder.
9. let the magic work. The phone will restart and it will probably take 15 minutes, make sure its charged enough.
After all that I quickly updated to the latest Stock ROM version, in my case B321, which you need to do if you want to flash later a custom B321. See second post if you want to do that as well or continue with unlocking the bootloader.
Now lets get the bootloader unlocked (for some reason mine was still unlocked)
1. Get Minimal ADB https://www.androidfilehost.com/?fid=24521665358595410
2. Hopefully you still have your unlock code (cause you need it otherwise it won't work)
3. Put your phone in Bootloader Mode (Press & hold power and volume down)
4. Extract Minimal ADB zip and run command.bat
5. Type <fastboot oem unlock xxxxxxxxxxxxx> (where xxxx is your bootloader unlock code)
6. Done
Now lets get twrp set up
1. For that we need minimal ADB again
2. Headover to http://forum.xda-developers.com/mate-8/development/recovery-twrp-huawei-mate-8-t3298567
3. Download TWRP according to your EMUI (For B321 it's EMUI 4.1)
4. Place the image in the directory of the Minimal ADB
5. Rename it to just twrp.img (not necessary but simplifies things)
6. Put your phone in Bootloader Mode (Press & hold power and volume down)
7. Run command.bat
8. Type <fastboot flash recovery twrp.img>
9. Then type fastboot reboot
10. Now you can hold volume up and power until your phone boots into TWRP
11. You need to format data (you'll lose everything on your phone)
12. Done
Remember: don't forget turning on usb debugging whenever you can!
!!!FOR L29 scroll down to DarkSilentSC's instructions!!!
After unbricking I quickly updated my AL10 to the latest version, in this case B321. Should work with all B3xx
1. Head over to Kris Chen's thread (this I used for the AL10)
http://forum.xda-developers.com/mate-8/development/rom-verison-t3324164
Or ajsmsg78's (also AL10 and L09)
http://forum.xda-developers.com/showpost.php?p=66776194&postcount=58 to get the Stock B321
2. Download the ROM and after downloading the zip file, extract update.app from it. Copy the UPDATE.APP to the internal memory of your HM8 in a folder called - dload (you may have to create it). Then press [volume+]+
[volume-]+[power] together to force the update.
3. Voila B321
-----------
!!![For the L29 you should try DarkSilentSC's instructions, which you find below or in post #54 on page 6 http://forum.xda-developers.com/mate-8/general/unbrick-updating-to-b321-t3375934/page6 don't forget to hit thanks!!!
1. Start from stock B170 firmware with TWRP ready
2. Extract BOOT, CUST, RECOVERY, SYSTEM from B321 UPDATE.APP
3. Add firmware .zip file (which contains META-INF folder and UPDATE.APP) and place it into internal storage
4. Make sure internal storage data is fully backed up
5. Delete All Accounts in Settings
6. Go to Recovery, Wipe Cache, Delvik Cache, Data, System
7. Flash that .zip file! (Getting errors is okay at this time) [This is what I didn't do before!]
8. Boot straight to bootloader
9. fastboot flash boot, cust, and system
10. let it boot. Let it proceed with encryption process in chinese and fully boot into EMUI
11. NOW I'M AT EMUI 4.1!
12. Reboot to fastboot and fastboot flash insecure_boot and flash TWRP
13. Reboot to recovery (TWRP) and then flash whatever rom you want to place in!
14. Enjoying it!
Great, was looking for details instructions like that, was stuck at cannot be trusted screen
Hello. Also i stuck today when i try to update. I try at my own all what did you said ......everything greast but when i try to flash rom from update.app proccess no pass more than 5:%.
My phone was also al-10 but 2 months ago i debrand with internation rom of acer. Nothing i cant flash . phone reboot work but can flash i thing my problem is the oem info file. Can anyone please help me
ganjbass said:
Hello. Also i stuck today when i try to update. I try at my own all what did you said ......everything greast but when i try to flash rom from update.app proccess no pass more than 5:%.
My phone was also al-10 but 2 months ago i debrand with internation rom of acer. Nothing i cant flash . phone reboot work but can flash i thing my problem is the oem info file. Can anyone please help me
Click to expand...
Click to collapse
Which update.app did you use? Maybe your download is corrupt?
BTW I debranded mine too with Acer's to international.
GerManiac said:
Which update.app did you use? Maybe your download is corrupt?
BTW I debranded mine too with Acer's to international.
Click to expand...
Click to collapse
NXT-AL10C00B321 i extract i unbrick from acer tool and then i use uppdate.app t but no pass more than 5%
What method you used for deprand? mine after debrand no able to use wifi recovery also no let me update even if i install factory recovery.
ganjbass said:
NXT-AL10C00B321 i extract i unbrick from acer tool and then i use uppdate.app t but no pass more than 5%
Click to expand...
Click to collapse
But you first used different ROM images to unbrick and then tried to update to B321.
really sounds as if your file is corrupted. Would try to download it again
GerManiac said:
But you first used different ROM images to unbrick and then tried to update to B321.
really sounds as if your file is corrupted. Would try to download it again
Click to expand...
Click to collapse
ok i will try tommorow......thanks for help by theway the phone booted but if i flash recovery for root no boot.... very strange....sometimes aloud to flash from boot some times no ohhhhhhh(((
Or something no correct with huawei extractor..... Can you provide extracted files?
Thanks in advance.
So I unbricked with B170 and then tried force flashing B321. My first attempt at flashing B321 ended up getting stuck at 5%. Tried flashing again and it said it was incompatible with the current firmware version of my phone. Any ideas on what I should do next?
Edit: Nevermind. I mistakenly copied the UPDATE.APP from B170 to the dload folder instead of the one from B321. lol
Now on B321. Thanks!
AndroidBestieRE said:
Great, was looking for details instructions like that, was stuck at cannot be trusted screen
Click to expand...
Click to collapse
Used this stock ROM for L29 to unbrick, it worked well following OP instructions
update.hicloud.com:8180/TDS/data/files/p3/s15/G1076/g104/v46463/f1/full/update.zip
hi, i have follow unbrick guide with knife, flash from knife and phone reboot. when phone reboot in settings, info phones, serial number is b321. is corretcly??
danielg90 said:
hi, i have follow unbrick guide with knife, flash from knife and phone reboot. when phone reboot in settings, info phones, serial number is b321. is corretcly??
Click to expand...
Click to collapse
Don't know which ROM you used to unbrick.
But seems that you used an B321 if that worked for you and you have no problems then that is great.
Could mean that wet can unbrick straight with the most current ROM available. If someone else could confirm?
GerManiac said:
Don't know which ROM you used to unbrick.
But seems that you used an B321 if that worked for you and you have no problems then that is great.
Could mean that wet can unbrick straight with the most current ROM available. If someone else could confirm?
Click to expand...
Click to collapse
i have AL10, please link stock rom that you used
danielg90 said:
i have AL10, please link stock rom that you used
Click to expand...
Click to collapse
Can't find the link right now, am in the car, but I've found this link to B170
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G884/g77/v43738/f1/full/update.zip:
Did not check though if it works
GerManiac said:
Can't find the link right now, am in the car, but I've found this link to B170
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G884/g77/v43738/f1/full/update.zip:
Did not check though if it works
Click to expand...
Click to collapse
sorry, is possible flash with knife if bootloader is locked? my bootloader is locked
hello, my phone is still stuck.. i tried other cust/system/recovery/boot from other update.app, but its still stuck at: your device has been unlocked... im on l29
Have NXT-L29, downloaded stock L09 file from posted link, placed UPDATE.APP into 'dload' folder which I created, but still hanging at 5%. What to do?? Exactly where do I create this 'dload' folder? Just at 'Internal Storage'?
danielg90 said:
sorry, is possible flash with knife if bootloader is locked? my bootloader is locked
Click to expand...
Click to collapse
Bootloader has to be unlocked. You can unlock best with DC unlocker, it's fast and only costs around 5 dollars.
Unless you already have your unlock code then you can unlock following instructions see my first post
GerManiac said:
Bootloader has to be unlocked. You can unlock best with DC unlocker, it's fast and only costs around 5 dollars.
Unless you already have your unlock code then you can unlock following instructions see my first post
Click to expand...
Click to collapse
ok how can i unlocked bootloader with b321 stock?
DarkSilentSC said:
Have NXT-L29, downloaded stock L09 file from posted link, placed UPDATE.APP into 'dload' folder which I created, but still hanging at 5%. What to do?? Exactly where do I create this 'dload' folder? Just at 'Internal Storage'?
Click to expand...
Click to collapse
What are you trying to do? Unbrick or update?
The folder has to be created in internal storage
Reasons to go back
- SIM Unlock tool doesn't work in Marshmallow (The SIM unlock app has a bug)
- Want to check out custom ROMs built on Lollipop
- Just because you can
Once you take the OS update to Marshmallow either through OTA or RUU exe file from HTC website, you can't go back to previous versions of the OS. This is because the misc partition keeps a copy of the version number and if the RUU you want to install is lower than that of what your phone has, it'll stop upgrading.
This is a big problem especially if you haven't SIM unlocked your MetroPCS HTC 626s yet, but upgraded the OS, and the current MetroPCS SIM unlock tool doesn't work. I was stuck in this situation without knowing what the cause was and wasted so much time. I called customer support several times, visited MetroPCS stores twice, all they could offer me was a replacement to a refurbished device and $20 out of pocket.
Instruction
Anyways, assuming you are on on Marshmallow (2.17.1550.1) the procedure to go back to Lollipop (1.23.1550.3) is the following:
1. Install TWRP for a32e. This is done in download mode through "fastboot flash recovery [twrpimage.img]" command.
Code:
https://twrp.me/devices/htcdesire626s.html
2. Install SuperSU 2.78 zip file inside TWRP recovery menu. Download the file, copy it in to your phone, reboot to recovery mode to TWRP, install the zip from there.
Code:
http://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
3. Restore the edited misc.img to your phone's partition. You can use my misc.img file attached in this thread. I only changed the version number from 2.17.1550.1 to 1.00.0000.0 using a hex editor. I compressed the misc.img file, so extract this file before proceeding.
Code:
http://forum.xda-developers.com/attachment.php?attachmentid=3873126&stc=1&d=1473705500
You can do:
"adb push misc.img /sdcard/".
"adb shell"
"su"
"dd if=/sdcard/misc.img of=/dev/block/bootdevice/by-name/misc"
These commands will overwrite your misc partition so that the main version is set to 1.00.0000.0. This allows the lower version Lollipop RUU to be installed.
There's no need to reboot. Just run the Lollipop RUU exe and let it reinstall the stock ROM and you are done.
After all this you can run the MetroPCS SIM unlock app, and it'll work properly and let you permanent SIM unlock as long as you are eligible (after 90 days of service).
Stock RUU downloads:
Marshmallow 2.17.1550.1 Stock RUU exe from HTC.com:
Code:
http://dl3.htc.com/application/RUU_A32E_UL_M60_DESIRE_SENSE70_MR_MetroPCS_US_2.17.1550.1.exe
Lollipop 1.23.1550.3 Stock RUU exe from HTC.com:
Code:
http://dl3.htc.com/application/RUU_A32E_UL_L51_DESIRE_SENSE70_MetroPCS_US_1.23.1550.3.exe
Credits
Big thanks and credit to: @GotHeart @BigCountry907
I posted this write-up since I have just recently gone through the process.
Other details, but not needed for performing the job here:
I tried mainver changing tools from old threads, but they didn't work.
To backup your misc partition in case you want to edit it yourself:
"dd if=/dev/block/bootdevice/by-name/misc of=/sdcard/misc.img"
Then bring the misc.img file to a computer and use any hex editor and look for the version number 2.17.1550.1 if you have the current Marshmallow, change it to 1.00.0000.0. That is the attached misc.img file in this thread.
Update: There is an update to this version ROM which is 2.17.1550.13. I don't know what changes there were from 2.17.1550.1 but hey it's something. I'm going to install the update and then root again. It might be a fix with the broken MetroPCS SIM Unlock app, but I don't know as mine is already SIM unlocked.
edit on 7/25/2017--
Latest version stock ROM as of 7/25/2017
Marshmallow 2.17.1550.23 Stock RUU exe from HTC.com
I had to redo all the flash recovery parition to install teamwin and install SuperSU, but after everything root is working fine.
hp79 said:
Reasons to go back
- SIM Unlock tool doesn't work in Marshmallow (The SIM unlock app has a bug)
- Want to check out custom ROMs built on Lollipop
- Just because you can
Once you take the OS update to Marshmallow either through OTA or RUU exe file from HTC website, you can't go back to previous versions of the OS. This is because the misc partition keeps a copy of the version number and if the RUU you want to install is lower than that of what your phone has, it'll stop upgrading.
This is a big problem especially if you haven't SIM unlocked your MetroPCS HTC 626s yet, but upgraded the OS, and the current MetroPCS SIM unlock tool doesn't work. I was stuck in this situation without knowing what the cause was and wasted so much time. I called customer support several times, visited MetroPCS stores twice, all they could offer me was a replacement to a refurbished device and $20 out of pocket.
Instruction
Anyways, assuming you are on on Marshmallow (2.17.1550.1) the procedure to go back to Lollipop (1.23.1550.3) is the following:
1. Install TWRP for a32e. This is done in download mode through "adb flash recovery [twrpimage.img]" command.
2. Install SuperSU 2.78 zip file inside TWRP recovery menu. Download the file, copy it in to your phone, reboot to recovery mode to TWRP, install the zip from there.
3. Restore the edited misc.img to your phone's partition. You can use my misc.img file attached in this thread. I only changed the version number from 2.17.1550.1 to 1.00.0000.0 using a hex editor. I compressed the misc.img file, so extract this file before proceeding.
You can do:
"adb push misc.img /sdcard/".
"adb shell"
"su"
"dd if=/sdcard/misc.img of=/dev/block/bootdevice/by-name/misc"
These commands will overwrite your misc partition so that the main version is set to 1.00.0000.0. This allows the lower version Lollipop RUU to be installed.
There's no need to reboot. Just run the Lollipop RUU exe and let it reinstall the stock ROM and you are done.
After all this you can run the MetroPCS SIM unlock app, and it'll work properly and let you permanent SIM unlock as long as you are eligible (after 90 days of service).
Stock RUU downloads:
Marshmallow 2.17.1550.1 Stock RUU exe from HTC.com:
Lollipop 1.23.1550.3 Stock RUU exe from HTC.com:
Credits
Big thanks and credit to: @[email protected]
I posted this write-up since I have just recently gone through the process.
Other details, but not needed for performing the job here:
I tried mainver changing tools from old threads, but they didn't work.
To backup your misc partition in case you want to edit it yourself:
"dd if=/dev/block/bootdevice/by-name/misc of=/sdcard/misc.img"
Then bring the misc.img file to a computer and use any hex editor and look for the version number 2.17.1550.1 if you have the current Marshmallow, change it to 1.00.0000.0. That is the attached misc.img file in this thread.
Click to expand...
Click to collapse
Much appreciated pal!!thanks for the guide!
GotHeart said:
Much appreciated pal!!thanks for the guide!
Click to expand...
Click to collapse
Hi GotHeart, once you went back to Lollipop, did the computer recognize the device properly?
I'm on Lollipop right now, maybe it needs another factory reset, or it may be something else related to the USB drivers since I'm using Parallels virtual machine on a Mac, but my phone is not being recognized no matter what I try. Maybe while going back some files were not able to really go back to the lower version?
edit: Never mind. It was something related to my setting with Parallels. After rebooting into native Windows 10 it's being recognized fine.
hp79 said:
Hi GotHeart, once you went back to Lollipop, did the computer recognize the device properly?
I'm on Lollipop right now, maybe it needs another factory reset, or it may be something else related to the USB drivers since I'm using Parallels virtual machine on a Mac, but my phone is not being recognized no matter what I try. Maybe while going back some files were not able to really go back to the lower version?
Click to expand...
Click to collapse
Ive never used this device on a Mac so i cant speak for that OS specifically,but it does recognize my phone just fine on a Windows Based PC.however,download mode takes alot longer to load up,and it says "SD not mounted".i dont know if this error is in relation to the downgrade.after you downgrade,i would think a factory reset is a good idea tbh.
help same problem
hp79 said:
Reasons to go back
- SIM Unlock tool doesn't work in Marshmallow (The SIM unlock app has a bug)
- Want to check out custom ROMs built on Lollipop
- Just because you can
Once you take the OS update to Marshmallow either through OTA or RUU exe file from HTC website, you can't go back to previous versions of the OS. This is because the misc partition keeps a copy of the version number and if the RUU you want to install is lower than that of what your phone has, it'll stop upgrading.
This is a big problem especially if you haven't SIM unlocked your MetroPCS HTC 626s yet, but upgraded the OS, and the current MetroPCS SIM unlock tool doesn't work. I was stuck in this situation without knowing what the cause was and wasted so much time. I called customer support several times, visited MetroPCS stores twice, all they could offer me was a replacement to a refurbished device and $20 out of pocket.
Instruction
Anyways, assuming you are on on Marshmallow (2.17.1550.1) the procedure to go back to Lollipop (1.23.1550.3) is the following:
1. Install TWRP for a32e. This is done in download mode through "fastboot flash recovery [twrpimage.img]" command.
Code:
https://twrp.me/devices/htcdesire626s.html
2. Install SuperSU 2.78 zip file inside TWRP recovery menu. Download the file, copy it in to your phone, reboot to recovery mode to TWRP, install the zip from there.
Code:
http://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
3. Restore the edited misc.img to your phone's partition. You can use my misc.img file attached in this thread. I only changed the version number from 2.17.1550.1 to 1.00.0000.0 using a hex editor. I compressed the misc.img file, so extract this file before proceeding.
Code:
http://forum.xda-developers.com/attachment.php?attachmentid=3873126&stc=1&d=1473705500
You can do:
"adb push misc.img /sdcard/".
"adb shell"
"su"
"dd if=/sdcard/misc.img of=/dev/block/bootdevice/by-name/misc"
These commands will overwrite your misc partition so that the main version is set to 1.00.0000.0. This allows the lower version Lollipop RUU to be installed.
There's no need to reboot. Just run the Lollipop RUU exe and let it reinstall the stock ROM and you are done.
After all this you can run the MetroPCS SIM unlock app, and it'll work properly and let you permanent SIM unlock as long as you are eligible (after 90 days of service).
Stock RUU downloads:
Marshmallow 2.17.1550.1 Stock RUU exe from HTC.com:
Code:
http://dl3.htc.com/application/RUU_A32E_UL_M60_DESIRE_SENSE70_MR_MetroPCS_US_2.17.1550.1.exe
Lollipop 1.23.1550.3 Stock RUU exe from HTC.com:
Code:
http://dl3.htc.com/application/RUU_A32E_UL_L51_DESIRE_SENSE70_MetroPCS_US_1.23.1550.3.exe
Credits
Big thanks and credit to: @GotHeart @BigCountry907
I posted this write-up since I have just recently gone through the process.
Other details, but not needed for performing the job here:
I tried mainver changing tools from old threads, but they didn't work.
To backup your misc partition in case you want to edit it yourself:
"dd if=/dev/block/bootdevice/by-name/misc of=/sdcard/misc.img"
Then bring the misc.img file to a computer and use any hex editor and look for the version number 2.17.1550.1 if you have the current Marshmallow, change it to 1.00.0000.0. That is the attached misc.img file in this thread.
Click to expand...
Click to collapse
can you explain me how to do the misc img step please
Adb says su not found
I get to the part where you have to put adb shell then su but it says su not found, my phone is rooted, it's systemless root though, does that make a difference? Is there a way to do this without using adb? Using su on Terminal Emulator when the phone is booted does work
machucogp said:
I get to the part where you have to put adb shell then su but it says su not found, my phone is rooted, it's systemless root though, does that make a difference? Is there a way to do this without using adb? Using su on Terminal Emulator when the phone is booted does work
Click to expand...
Click to collapse
I'm not sure what a systemless root is. I don't know how you'd do it without regular root. Why don't you try to install normal root? I think it was a pretty easy process to root.
Also, not a good idea to quote the whole original post. Just saying.. Have a good day!
is their a process to do when switching carriers from metropcs after sim unlocked?
Here is a link to Lollipop 5.1 for SPRINT in case anyone needs it.
https://drive.google.com/open?id=0B8jitdIyh2NtUHQ2YWd5T2RCUFk
Sorry for being such a noob but how do i add the misc.img file tried on fastboot no luck ? any help thank you
Error 131
hp79 said:
Reasons to go back
- SIM Unlock tool doesn't work in Marshmallow (The SIM unlock app has a bug)
- Want to check out custom ROMs built on Lollipop
- Just because you can
Once you take the OS update to Marshmallow either through OTA or RUU exe file from HTC website, you can't go back to previous versions of the OS. This is because the misc partition keeps a copy of the version number and if the RUU you want to install is lower than that of what your phone has, it'll stop upgrading.
This is a big problem especially if you haven't SIM unlocked your MetroPCS HTC 626s yet, but upgraded the OS, and the current MetroPCS SIM unlock tool doesn't work. I was stuck in this situation without knowing what the cause was and wasted so much time. I called customer support several times, visited MetroPCS stores twice, all they could offer me was a replacement to a refurbished device and $20 out of pocket.
Instruction
Anyways, assuming you are on on Marshmallow (2.17.1550.1) the procedure to go back to Lollipop (1.23.1550.3) is the following:
1. Install TWRP for a32e. This is done in download mode through "fastboot flash recovery [twrpimage.img]" command.
Code:
https://twrp.me/devices/htcdesire626s.html
2. Install SuperSU 2.78 zip file inside TWRP recovery menu. Download the file, copy it in to your phone, reboot to recovery mode to TWRP, install the zip from there.
Code:
http://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
3. Restore the edited misc.img to your phone's partition. You can use my misc.img file attached in this thread. I only changed the version number from 2.17.1550.1 to 1.00.0000.0 using a hex editor. I compressed the misc.img file, so extract this file before proceeding.
Code:
http://forum.xda-developers.com/attachment.php?attachmentid=3873126&stc=1&d=1473705500
You can do:
"adb push misc.img /sdcard/".
"adb shell"
"su"
"dd if=/sdcard/misc.img of=/dev/block/bootdevice/by-name/misc"
These commands will overwrite your misc partition so that the main version is set to 1.00.0000.0. This allows the lower version Lollipop RUU to be installed.
There's no need to reboot. Just run the Lollipop RUU exe and let it reinstall the stock ROM and you are done.
After all this you can run the MetroPCS SIM unlock app, and it'll work properly and let you permanent SIM unlock as long as you are eligible (after 90 days of service).
Stock RUU downloads:
Marshmallow 2.17.1550.1 Stock RUU exe from HTC.com:
Code:
http://dl3.htc.com/application/RUU_A32E_UL_M60_DESIRE_SENSE70_MR_MetroPCS_US_2.17.1550.1.exe
Lollipop 1.23.1550.3 Stock RUU exe from HTC.com:
Code:
http://dl3.htc.com/application/RUU_A32E_UL_L51_DESIRE_SENSE70_MetroPCS_US_1.23.1550.3.exe
Credits
Big thanks and credit to: @GotHeart @BigCountry907
I posted this write-up since I have just recently gone through the process.
Other details, but not needed for performing the job here:
I tried mainver changing tools from old threads, but they didn't work.
To backup your misc partition in case you want to edit it yourself:
"dd if=/dev/block/bootdevice/by-name/misc of=/sdcard/misc.img"
Then bring the misc.img file to a computer and use any hex editor and look for the version number 2.17.1550.1 if you have the current Marshmallow, change it to 1.00.0000.0. That is the attached misc.img file in this thread.
Click to expand...
Click to collapse
Hi I do your tutorial and when ruu start to copy the fIles I get error 131, do you something About this error
BigCountry907 said:
Here is a link to Lollipop 5.1 for SPRINT in case anyone needs it.
https://drive.google.com/open?id=0B8jitdIyh2NtUHQ2YWd5T2RCUFk
Click to expand...
Click to collapse
Not quite sure what this is, or how to use it. (Just getting a zip, full of other zips that i cant open)
It is a RUU for the sprint version of the desire 626s.
To use it you have to rename the file to ( 0PM9IMG.zip ) and copy it to the external sdcard of the phone.
Then boot the phone to download mode...........
It will ask you if you want to flash.
Hit the volume up key and it will flash the ruu. This restores the device to out of the box condition.
The ruu is the complete firmware for the device.
It is encrypted. To unzip and do anything with separate files you have to decrypt them.
See here.
http://forum.xda-developers.com/showthread.php?t=2084470
Or a good tool.
http://forum.xda-developers.com/chef-central/android/tool-universal-htc-ruu-rom-decryption-t3382928
The ruu packages are perfect for fixing you phone if you have bricked it or bootloop or if you just want to start fresh like factory reset.
BigCountry907 said:
It is a RUU for the sprint version of the desire 626s.
To use it you have to rename the file to ( 0PM9IMG.zip ) and copy it to the external sdcard of the phone.
Then boot the phone to download mode...........
It will ask you if you want to flash.
Hit the volume up key and it will flash the ruu. This restores the device to out of the box condition.
The ruu is the complete firmware for the device.
It is encrypted. To unzip and do anything with separate files you have to decrypt them.
See here.
http://forum.xda-developers.com/showthread.php?t=2084470
Or a good tool.
http://forum.xda-developers.com/chef-central/android/tool-universal-htc-ruu-rom-decryption-t3382928
The ruu packages are perfect for fixing you phone if you have bricked it or bootloop or if you just want to start fresh like factory reset.
Click to expand...
Click to collapse
Thanks, hopefully going back to L will help with stability. At least on my phone the stock MM rom isn't even stable
I prefer lollipop over marshmallow for testing.
Marshmallow has a ton of new security.
Download the ADB Files f
I did figure out how to push misc and all this final step, however, when i go to run the Lollipop RUU exe it still reads the same 2.17.1550.1 version like nothing changed. I went ahead and it does the "update" to Lollipop 1.23.1550.3 but withing 3 minutes of running i get Unknown Error [155]. But I tried again with the same RUU and finally worked.
The problem now is the unlock app that keeps saying; "Device not recognized by your service provider. Please call customer care."
I performed hard reset, app cashe and memory wipe and still the same.
Any solutions on this issue so far?
Thanks
comphy said:
I did figure out how to push misc and all this final step, however, when i go to run the Lollipop RUU exe it still reads the same 2.17.1550.1 version like nothing changed. I went ahead and it does the "update" to Lollipop 1.23.1550.3 but withing 3 minutes of running i get Unknown Error [155]. But I tried again with the same RUU and finally worked.
The problem now is the unlock app that keeps saying; "Device not recognized by your service provider. Please call customer care."
I performed hard reset, app cashe and memory wipe and still the same.
Any solutions on this issue so far?
Thanks
Click to expand...
Click to collapse
i did the procedure and do like a charm, only need onluck bootloader first and change en command to push misc.img the /sdcard/ for only /
regards!
picaron1 said:
i did the procedure and do like a charm, only need onluck bootloader first and change en command to push misc.img the /sdcard/ for only /
regards!
Click to expand...
Click to collapse
I did tooo, but my problem is the unlock app that keeps saying; "Device not recognized by your service provider. Please call customer care."
I performed hard reset, app cashe and memory wipe and still the same message. How did you work this issue out or what message did you get from unlock app?
hp79 said:
Reasons to go back
- SIM Unlock tool doesn't work in Marshmallow (The SIM unlock app has a bug)
- Want to check out custom ROMs built on Lollipop
- Just because you can
Once you take the OS update to Marshmallow either through OTA or RUU exe file from HTC website, you can't go back to previous versions of the OS. This is because the misc partition keeps a copy of the version number and if the RUU you want to install is lower than that of what your phone has, it'll stop upgrading.
This is a big problem especially if you haven't SIM unlocked your MetroPCS HTC 626s yet, but upgraded the OS, and the current MetroPCS SIM unlock tool doesn't work. I was stuck in this situation without knowing what the cause was and wasted so much time. I called customer support several times, visited MetroPCS stores twice, all they could offer me was a replacement to a refurbished device and $20 out of pocket.
Instruction
Anyways, assuming you are on on Marshmallow (2.17.1550.1) the procedure to go back to Lollipop (1.23.1550.3) is the following:
1. Install TWRP for a32e. This is done in download mode through "fastboot flash recovery [twrpimage.img]" command.
Code:
https://twrp.me/devices/htcdesire626s.html
2. Install SuperSU 2.78 zip file inside TWRP recovery menu. Download the file, copy it in to your phone, reboot to recovery mode to TWRP, install the zip from there.
Code:
http://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
3. Restore the edited misc.img to your phone's partition. You can use my misc.img file attached in this thread. I only changed the version number from 2.17.1550.1 to 1.00.0000.0 using a hex editor. I compressed the misc.img file, so extract this file before proceeding.
Code:
http://forum.xda-developers.com/attachment.php?attachmentid=3873126&stc=1&d=1473705500
You can do:
"adb push misc.img /sdcard/".
"adb shell"
"su"
"dd if=/sdcard/misc.img of=/dev/block/bootdevice/by-name/misc"
These commands will overwrite your misc partition so that the main version is set to 1.00.0000.0. This allows the lower version Lollipop RUU to be installed.
There's no need to reboot. Just run the Lollipop RUU exe and let it reinstall the stock ROM and you are done.
After all this you can run the MetroPCS SIM unlock app, and it'll work properly and let you permanent SIM unlock as long as you are eligible (after 90 days of service).
Stock RUU downloads:
Marshmallow 2.17.1550.1 Stock RUU exe from HTC.com:
Code:
http://dl3.htc.com/application/RUU_A32E_UL_M60_DESIRE_SENSE70_MR_MetroPCS_US_2.17.1550.1.exe
Lollipop 1.23.1550.3 Stock RUU exe from HTC.com:
Code:
http://dl3.htc.com/application/RUU_A32E_UL_L51_DESIRE_SENSE70_MetroPCS_US_1.23.1550.3.exe
Credits
Big thanks and credit to: @GotHeart @BigCountry907
I posted this write-up since I have just recently gone through the process.
Other details, but not needed for performing the job here:
I tried mainver changing tools from old threads, but they didn't work.
To backup your misc partition in case you want to edit it yourself:
"dd if=/dev/block/bootdevice/by-name/misc of=/sdcard/misc.img"
Then bring the misc.img file to a computer and use any hex editor and look for the version number 2.17.1550.1 if you have the current Marshmallow, change it to 1.00.0000.0. That is the attached misc.img file in this thread.
Update: There is an update to this version ROM which is 2.17.1550.13. I don't know what changes there were from 2.17.1550.1 but hey it's something. I'm going to install the update and then root again. It might be a fix with the broken MetroPCS SIM Unlock app, but I don't know as mine is already SIM unlocked.
Click to expand...
Click to collapse
I've followed every step and it's all good except when I try to do the last step.
When I type "dd if=/sdcard/misc.img of=/dev/block/bootdevice/by-name/misc" I get a return message saying :no such file or directory found, even thou the misc.img file is in the same folder
Can anyone help with this?
need help
Sir / brother i have htc desire 626s sprint i exdently updated my phone in to marshmallow but after upgrade my sim is locked if i tried this misc edited img file for come to lower version but i have not ruu lollipop file for my phone please give me link for this file code are a32ewhl , sorry 4 my English thanks in advance
Hi,
I have a problem. I tried to flash stock rom, but I forgot about hifi image.
There's a photo of my phone.
imgur.com/aVUBTRD
I have unlocked bootloader, but I can't flash hifi. "Command not allowed."
I tried method with put microsd card with update.app in dload into smartphone and I when I pressed power button
and VOLUME UP and VOLUME DOWN nothing happened.
I tried just flash all partitions separately, with huawei update extractor, again nothing.
I saw the same problem in this site, but I don't know how he solwed this.
Please help me :crying:
Flash a Huawei recovery, a old one b584 or something, then download b596 DS or b597 SS i don't know your device, extract update.app and copy to sd card dload folder, try to flash it!
persona78 said:
Flash a Huawei recovery, a old one b584 or something, then download b596 DS or b597 SS i don't know your device, extract update.app and copy to sd card dload folder, try to flash it!
Click to expand...
Click to collapse
I flashed recovery and nothing happened, I can't get into recovery mode, only fastboot.
I have the same phone.
adamektv said:
I flashed recovery and nothing happened, I can't get into recovery mode, only fastboot.
I have the same phone.
Click to expand...
Click to collapse
You flashed the recovery and everything say okay, right?
Now flash a rom with dload and the 3 keys, do you know how?
.
persona78 said:
You flashed the recovery and everything say okay, right?
Now flash a rom with dload and the 3 keys, do you know how?
.
Click to expand...
Click to collapse
I don't know, when I pressed three buttons I didn't enter to recovery mode, but to rescue mode, as if recovery wasn't flashed.
adamektv said:
I don't know, when I pressed three buttons I didn't enter to recovery mode, but to rescue mode, as if recovery wasn't flashed.
Click to expand...
Click to collapse
Do you have a dload folder with update.app inside, in sd card?
With that and pressing vol +, vol - and power at same time you enter in flash mode and start to flash the rom
persona78 said:
Do you have a dload folder with update.app inside, in sd card?
With that and pressing vol +, vol - and power at same time you enter in flash mode and start to flash the rom
Click to expand...
Click to collapse
Yes, I have, and it's still not working
I can't charge battery, so i don't think it's software.
Maybe it's motherboard
adamektv said:
Yes, I have, and it's still not working
I can't charge battery, so i don't think it's software.
Maybe it's motherboard
Click to expand...
Click to collapse
How da start it???
adamektv said:
Yes, I have, and it's still not working
I can't charge battery, so i don't think it's software.
Maybe it's motherboard
Click to expand...
Click to collapse
Try opening the phone and disconnecting the battery .. do it if u only gave up with other methods someone said it worked
adamektv said:
Hi,
I have a problem. I tried to flash stock rom, but I forgot about hifi image.
There's a photo of my phone.
imgur.com/aVUBTRD
I have unlocked bootloader, but I can't flash hifi. "Command not allowed."
I tried method with put microsd card with update.app in dload into smartphone and I when I pressed power button
and VOLUME UP and VOLUME DOWN nothing happened.
I tried just flash all partitions separately, with huawei update extractor, again nothing.
I saw the same problem in this site, but I don't know how he solwed this.
Please help me :crying:
Click to expand...
Click to collapse
Hi Have got succeeded or not, if not follow the guide.
Is your phone being detected by PC if yes then you have chances of recovering your phone.
1. Download 15 Seconds ADB and Fastboot Drivers. Visit the official XDA forum for download and installation instructions.
2. Install Huawei HiSuite which will install drivers .
3. If HiSuite doesn't install Install drivers then install universal drivers for your device .
Now connect your device to pc and open HiSuite and click on system recovery it will show options for recovery if it is success then you are fine if not then proceed to this method.
Connect your phone to PC.
Open Command Prompt in the directory where you have extracted the ADB files by holding Shift and Right Mouse Button and finally click Open Command Prompt window here in the context menu.
Completely power off your device.
While holding Volume Down button, connect your device to PC via USB cable to boot to Fastboot Mode.
1. Type the following command in ADB :
Code:
adb devices
If your device is being detected and it shows list of devices attached and its serial number.
2.Now download the firmware of the phone before your phone got bootlooped extract the update using the file here
3.Now copy the following files ( boot.img, recovery.img and system.img ,cust.img ) from the extracted files to the ADB files directory.
4.Now Execute these commands one at a time using the command prompt.
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cust cust.img
fastboot reboot
5.Now Perform a Factory Reset if your phone got recovered.
If not then download the stock recovery of your Device and try steps 2,3,4.
Even if it doesn't get succeeded then try this option .
If your device got bootlooped while on Lollipop or Marshmallow then you have one more way to recover .
6.Now download the latest TWRP from here and boot into TWRP recovery if you cant enter TWRP recovery for this version then try the previous TWRP versions like 2.8.7 ,
7.Use the following command to flash the TWRP recovery
Code:
fastboot flash recovery twrp.img
8.Then download any of the custom ROMs or ask any of the XDA members for TWRP backup for your device and flash them through Recovery.
Then Reboot your Device.
You would most probably recover your device from any of the above methods . I too had the same problem and My device was use less for almost 6 months but after several trial and error methods my device got recovered.
Credits:
1.https://forum.xda-developers.com/honor-4c/how-to/huawei-honor-4c-index-troubleshooting-t3293110
2.https://forum.xda-developers.com/showthread.php?t=2433454
miststudent2011 said:
Hi Have got succeeded or not, if not follow the guide.
Is your phone being detected by PC if yes then you have chances of recovering your phone.
1. Download 15 Seconds ADB and Fastboot Drivers. Visit the official XDA forum for download and installation instructions.
2. Install Huawei HiSuite which will install drivers .
3. If HiSuite doesn't install Install drivers then install universal drivers for your device .
Now connect your device to pc and open HiSuite and click on system recovery it will show options for recovery if it is success then you are fine if not then proceed to this method.
Connect your phone to PC.
Open Command Prompt in the directory where you have extracted the ADB files by holding Shift and Right Mouse Button and finally click Open Command Prompt window here in the context menu.
Completely power off your device.
While holding Volume Down button, connect your device to PC via USB cable to boot to Fastboot Mode.
1. Type the following command in ADB :
Code:
adb devices
If your device is being detected and it shows list of devices attached and its serial number.
2.Now download the firmware of the phone before your phone got bootlooped extract the update using the file here
3.Now copy the following files ( boot.img, recovery.img and system.img ,cust.img ) from the extracted files to the ADB files directory.
4.Now Execute these commands one at a time using the command prompt.
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cust cust.img
fastboot reboot
5.Now Perform a Factory Reset if your phone got recovered.
If not then download the stock recovery of your Device and try steps 2,3,4.
Even if it doesn't get succeeded then try this option .
If your device got bootlooped while on Lollipop or Marshmallow then you have one more way to recover .
6.Now download the latest TWRP from here and boot into TWRP recovery if you cant enter TWRP recovery for this version then try the previous TWRP versions like 2.8.7 ,
7.Use the following command to flash the TWRP recovery
Code:
fastboot flash recovery twrp.img
8.Then download any of the custom ROMs or ask any of the XDA members for TWRP backup for your device and flash them through Recovery.
Then Reboot your Device.
You would most probably recover your device from any of the above methods . I too had the same problem and My device was use less for almost 6 months but after several trial and error methods my device got recovered.
Credits:
1.https://forum.xda-developers.com/honor-4c/how-to/huawei-honor-4c-index-troubleshooting-t3293110
2.https://forum.xda-developers.com/showthread.php?t=2433454
Click to expand...
Click to collapse
I have already done this and still stuck in rescue
adamektv said:
I have already done this and still stuck in rescue
Click to expand...
Click to collapse
Did you try flashing different variant ROM ie different builds?
Actually I too got the same problem bootlooped on LP but cant flash the LP ROM back so I flashed different Region ROM.
Give a try to TWRP Method It should give you success.
Imp:
Try the previous ROM where you got Bootloop, or the version earlier to it.If it doesn't succeed try the rom which you got initially on your mobile.
PS: If your phone is being detected by your PC you have good chances of recovering your phone.
WARNING: Flashing an unapproved firmware can cause unexpected issues. The OP will not be liable for any bricked device which resulted because of the use of this method. Everything is done at user's discretion. Also, ensure that you're using the correct firmware file (matches your model and is not corrupt).
Important notes for updating from Oreo -> Oreo
If you're on Oreo, don't download the recoveries mentioned in the guide below. Instead grab the one below (thanks to TeamMT for the patched recovery):
Code:
https://drive.google.com/open?id=1HmFAMYm1pU7RdKkOq_TMdthCxZJflzv9
Note that this is only 1 recovery. So whenever you see the command:
Code:
fastboot flash recovery FRD_RECOVERY_NoCheck.img
Replace it with:
Code:
fastboot flash recovery_ramdisk FRD_RECOVERY_RAMDISK_NoCheck.img
For recovery2:
Code:
fastboot flash erecovery_ramdisk FRD_RECOVERY_RAMDISK_NoCheck.img
I know it's the same recovery being flashed on two different partitions but it doesn't matters
Happy flashing !
What will you achieve...
With this guide you can flash FullOTA-MF firmwares which are unapproved for installation (also called 'online firmwares', shows errors when flashing in TWRP or authentication errors when using Firmware Finder proxy) on your device by bypassing the authentication checks at stock recovery. PV (Point Version) firmwares should not be flashed by this method since they can be already flashed via TWRP.
I successfully updated my FRD-L09 from B392SP01 to B394. I'm writing down two methods, you can use any
Method 1 Using RedLotus
RedLotus is an open source huawei proxy that allows you to push any update to your device through HiSuite.
A) PREPARATION / Device
Download the modified (NoCheck, authentication removed) stock recovery:
Code:
Recovery 1: https://drive.google.com/file/d/0B4SPRmBNsTefSWZLSWxpWGd6QkE/view?usp=drivesdk&resourcekey=0-cZTB6Ze_tUOaJsTPPvErYQ
Recovery 2: https://drive.google.com/file/d/0B4SPRmBNsTefSVhxMWFoa01wams/view?usp=drivesdk&resourcekey=0-DuV9zTB1sSKCYrCGgMv0_Q
These recoveries have authentication checks removed allowing you to flash any firmware.
Flash both recoveries via fastboot:
Code:
fastboot flash recovery FRD_RECOVERY_NoCheck.img
fastboot flash recovery2 FRD_RECOVERY2_NoCheck.img
Reboot your device.
B) PREPARATION / Setting up HiSuite and RedLotus
Download and install HiSuite and nodejs:
Code:
HiSuite: consumer.huawei.com/minisite/HiSuite_en/
nodejs: https://nodejs.org/en/download/
Visit RedLotus Github repository and download it (find the green Clone / Download button)
Code:
https://github.com/lukx/redlotus
Extract the downloaded file to any directory. Inside that directory, hold down left Shift button and click right mouse button. In the context menu that appears select Open Command Window / Powershell Window here. Do not close this window till the end of the instructions.
Execute the following command inside the CMD / Powershell window.
Code:
npm install
You will now download the firmware you want to flash (for example FRD-L09C432B394, only FullOTA-MF supported). Goto TeamMT Firmware Finder and search for the firmware you wish to download. Copy the link to the filelist.xml of that firmware (for example filelist of FRD-L09C432B394: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1585/g104/v93530/f1/full/filelist.xml)
Execute the following command inside the CMD / Powershell window.
Code:
npm run download path-to-firmware-xml (replace last part with actual link)
Wait for the download to complete.
Navigate to C:\Windows\system32\drivers\etc. Open hosts file as Administrator and add this line at the end of it:
Code:
127.0.0.1 query.hicloud.com
This will set up a redirection resolving all hicloud queries to your localhost server.
Execute the following command inside the CMD / Powershell window:
Code:
npm run listen-hisuite
C) INSTALLATION
Connect the device to computer and ensure that HiSuite is recognizing the attached device. If it isn't go to Settings -> Developer Options and ensure ADB Debugging is enabled.
Hit the Update button in HiSuite. You'll see a message reading a new update is available and the update will be named RedLotus-OTA.
Start the update process and wait patiently.
Your device will eventually reboot to stock recovery and update will start installing. The update might seem to stuck at some percentage. It's normal, wait patiently for the update to install.
You're now updated to the firmware you chose.
OPTIONAL: In case of bootloops, factory reset the device and also unlock bootloader if the device automatically relocked.
Method 2 Using Root
A) PREPARATION / Downloading the required files
Download the modified (NoCheck, authentication removed) stock recovery:
Code:
Recovery 1: https://drive.google.com/open?id=0B4SPRmBNsTefSWZLSWxpWGd6QkE
Recovery 2: https://drive.google.com/open?id=0B4SPRmBNsTefSVhxMWFoa01wams
These recoveries have authentication checks removed allowing you to flash any firmware. Move both recovery files to internal storage or any path of your choice (this guide will assume you copied both files to /sdcard)
You will now download the firmware you want to flash (for example FRD-L09C432B394, only FullOTA-MF supported). Goto TeamMT Firmware Finder and search for the firmware you wish to download. Open the filelist.xml of that firmware and download all the files mentioned inside it. For example, the links for FRD-L09C432B394 are
Code:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1585/g104/v93530/f1/full/update.zip
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1585/g104/v93530/f1/full/public/update_data_full_public.zip
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1585/g104/v93530/f1/full/FRD-L09_hw_eu/update_full_FRD-L09_hw_eu.zip
Copy the firmware files to /sdcard/HWOTA (ensure the files are inside HWOTA, it doesn't matters whether you copied the files to internal or external).
B) PREPARATION / Device
Flash the downloaded recoveries via fastboot:
Code:
fastboot flash recovery FRD_RECOVERY_NoCheck.img
fastboot flash recovery2 FRD_RECOVERY2_NoCheck.img
Reboot your device.
B) INSTALLATION
After your device is rebooted back to system, open any file manager that supports root.
Navigate to /data/ and create a new folder update/HWOTA.
Copy all the three downloaded zips to the folder created above.
Now using either Terminal Emulator or ADB Shell, grant SU privileges by executing su within the app or shell and further execute the following commands:
Code:
echo "--update_package=/data/update/HWOTA/update.zip" > /cache/recovery/command
echo "--update_package=/data/update/HWOTA/update_data_full_public.zip" >> /cache/recovery/command
echo "--update_package=/data/update/HWOTA/update_full_FRD-L09_hw_eu.zip" >> /cache/recovery/command
You need to replace the file names (of the zip files) with the ones you've downloaded.
With everything done reboot your device to recovery:
Code:
reboot recovery
OPTIONAL: In case of bootloops, factory reset the device and also unlock bootloader if the device automatically relocked.
Credits:
@mankindtw : he originally patched the Mate 9 recovery removing the authentication. I patched Honor 8 recovery by identifying his edits and adding them.
@OldDroid : for hinting about how to patch the image and because this guide is inspired by his similar guide in Honor 8 Pro forums.
It appears that some information is not shown when using the XDA Labs apps. View in a browser so that you can see all the instructions
Edit - this is a known bug if XDA has been loaded into ram for a while. Close app and restart XDA if you encounter this.
Great. Very well explained. Keep it up mate.
For now use RedLotus method. There might be some problems with TWRP method. I'll try to find the root of the issue but until then, enjoy.
May I use RedLotus method without unlocking bootloader?
slonislaw said:
May I use RedLotus method without unlocking bootloader?
Click to expand...
Click to collapse
Yes you can use but it depends on the update you're trying to flash. Updates have built in verification and authentication checks and hence will fail.
That's where the modified recovery comes in which bypasses those checks and allows you to flash any firmware. Unfortunately, flashing modified recovery requires an unlocked bootloader.
I copied the FRDLO9-C432B396 FULL OTA MF downloaded from another device. My device is FRDL09-C185. I have the three files of my PC.
update.zip
update_full_FRD-L09_hw_eu.zip
update_data_full_public.zip
Which step is ideal for me to use?
vanbayor said:
I copied the FRDLO9-C432B396 FULL OTA MF downloaded from another device. My device is FRDL09-C185. I have the three files of my PC.
update.zip
update_full_FRD-L09_hw_eu.zip
update_data_full_public.zip
Which step is ideal for me to use?
Click to expand...
Click to collapse
Hmm...
Go with TWRP method since you already have the files.
thanks bro
@hackslash thanks for the detailed method. Can we do something similar for Honor 6x users as well. It may help in debranding or installing the other firmwares as well.
shashank1320 said:
@hackslash thanks for the detailed method. Can we do something similar for Honor 6x users as well. It may help in debranding or installing the other firmwares as well.
Click to expand...
Click to collapse
It is possible but I won't be able to confirm if the recovery works. I'll try to patch the image and will release a recovery for 6X too soon.
hackslash said:
It is possible but I won't be able to confirm if the recovery works. I'll try to patch the image and will release a recovery for 6X too soon.
Click to expand...
Click to collapse
Great. Let me know if i can contribute in any way, for files for testing anything.
Good luck. Hope to see some really useful tool for 6X too.
When I hit update in HiSuite it gives me an error saying "No Internet Connection. Please Check Your Network Settings."
Gus194 said:
When I hit update in HiSuite it gives me an error saying "No Internet Connection. Please Check Your Network Settings."
Click to expand...
Click to collapse
Did you run 'npm run listen-hisuite' before checking for updates. Follow the steps exactly as ordered and explained.
hackslash said:
Did you run 'npm run listen-hisuite' before checking for updates. Follow the steps exactly as ordered and explained.
Click to expand...
Click to collapse
Yup, followed all the steps. It says "Okay, Listening for HiSuite" Then I go to HiSuite and click update and it gives me the error.
Edit: What version of HiSuite did you use to flash the update? I updated HiSuite before doing the instructions, do you think that that has something to do with it?
Edit 2: Nevermind I think I fixed it, I just changed the Host line to to be in middle instead of the very end. Thanks for the help though
Guys is it possible to create a modded rollback package with inside these modded recovery images? I saw on firmware extractor something related to re-packing an update, would it be possible to create this package? It could be used to flash firmwares without unlock our bootloader? I suppose yes because rollback package has something of "magic" inside....it flashes everytime on a nougat firmware
In twrp, terminal " mkdir /data/update" is false " mkdir: can't creat directory '/data/update': File exists "
help me !
I have use RedLotus done. but end is erecovery?
now how should i do?
Gus194 said:
Yup, followed all the steps. It says "Okay, Listening for HiSuite" Then I go to HiSuite and click update and it gives me the error.
Edit: What version of HiSuite did you use to flash the update? I updated HiSuite before doing the instructions, do you think that that has something to do with it?
Edit 2: Nevermind I think I fixed it, I just changed the Host line to to be in middle instead of the very end. Thanks for the help though
Click to expand...
Click to collapse
I get the same error after doing the exact steps in the tutorial, can you tell me how did you fix it?
Cheers
flip360 said:
I get the same error after doing the exact steps in the tutorial, can you tell me how did you fix it?
Cheers
Click to expand...
Click to collapse
Instead of the host line being at the very end I put it in the middle.