Related
Hello Developers,
I am a HK Version Hero user. My region started the OTA 2.1 update for HERO.
I have already restore my Nanbackup to the first 1.5 backup.
When it finished the download, my phone reboot to the recovery mode and start the update and prompted:
E:No signature (231 files)
E:Verification failed
Installation aborted.
My need rom version should be 2.73.721.91.
Anyway that I can update to the new stock rom?
Thanks for the help !!
I got the link for the first OTA download, but I am a new user I cannot post it out.
Is it I just delete the recovery.img file? and it will work?
Thanks again
hero-err said:
I got the link for the first OTA download, but I am a new user I cannot post it out.
Is it I just delete the recovery.img file? and it will work?
Thanks again
Click to expand...
Click to collapse
No, you'd have to re-sign the zipfile. If a file is added/removed or editted, the hashes don't match anymore and no one will be able to flash it.
Learn how to re-sign, or just upload it @ multishare as-is, and request re-signing of it. Mayb someone will help you out .
just take the recovery img out of the ruu and flash it then try to update.Should work then
I have the same problem. I really didnt understand what you just said..
My file is a .zip and can not be flashed with flashrec.
can you explain better for a n00b like me?
sundrik said:
I have the same problem. I really didnt understand what you just said..
My file is a .zip and can not be flashed with flashrec.
can you explain better for a n00b like me?
Click to expand...
Click to collapse
you don't flash files with flashrec, you flash them from recovery mode.
and just because something is a .zip doesn't mean it can be flashed. it has to be signed with the appropriate update script.
It like this.
I got an OTA for the 2.1. This generated an error when updating. So i thought i just download the file and do it from recovery mode.
Downloaded the file from here: liveimage.htc.com//OTA_Hero_ChungHwa_3.31.751.1_R-2.73.751.13_release048gnt2ecw16ubyr.zip
The link is not active anymore.
But i still get the same error.
I tried to do a factory reset and do the update after that, but without any luck.
I know this is the update for my phone, but i cant do it. And you guys speak about signing the file before, but i dont know how.
Probably same error for topic starter.
to do what i said you have to boot the phone in recovery.take the files out of the update.zip (or if it a RUU go HERE) in the .zip file should be boot.img,recovery.img,userdata.img,system.img,HBOOT and a few others....
Take out the recovery.img
and flash via fastboot (turn phone one holding back)
open cmd window (windows key + r) type cmd
fastboot flash recovery (drag and drop recover.img into cmd window) press enter
Then try updating
I dont get it to work.
I take out the recovery.img
Turn the phone on by holding 'back' while power on. (Screen with three android skaters)
Then i plug in the usb.
The text 'FASTBOOT' change to 'FASTBOOT USB'
Open cmd (windowskey + r and type cmd adn enter)
Drag and drop the recovery.img to command window and press enter.
This makes the DVD burning application on the computer to start and wants to burn the file.
sundrik said:
I dont get it to work.
I take out the recovery.img
Turn the phone on by holding 'back' while power on. (Screen with three android skaters)
Then i plug in the usb.
The text 'FASTBOOT' change to 'FASTBOOT USB'
Open cmd (windowskey + r and type cmd adn enter)
Drag and drop the recovery.img to command window and press enter.
This makes the DVD burning application on the computer to start and wants to burn the file.
Click to expand...
Click to collapse
Maybe you should use fastboot - the program for your pc?
The steps that were told to you were right, but I think you didn't do the last one as you should. Once in the command-line, you have to type "fastboot flash recovery " (yep, there's a space at the end) and then write the path of the recovery image (i.e., if it's in C:\asd\recovery.img, it would be "fastboot flash recovery \asd\recovery.img"), or drag and drop the file to the cmd, and it will write the path.
You know where to get this fastboot program...
I only find this from 2008. Should be a better one with not so much tweaking?
http://forum.xda-developers.com/showthread.php?t=463627
Nope, not really, I use linux.
Thanks for all the help!! I finally upgraded.
I restore to my 1.5 backup and down the update part by part.
I pull out the recovery.img and zip it back and re-sign it, copy to my phone and rename it to Update.zip and flash the first part. Reboot and copy the OTA2 to the phone and also rename it to Update.zip, flash it again. Final reboot, its now the official 2.1 android update. Also the root is still there.
OTA1
Badongo file 23546527
OTA2
Badongo file 23546783
THANKS again!!!
(sorry about the link, they won't let me post it ><)
hero-err said:
Thanks for all the help!! I finally upgraded.
I restore to my 1.5 backup and down the update part by part.
I pull out the recovery.img and zip it back and re-sign it, copy to my phone and rename it to Update.zip and flash the first part. Reboot and copy the OTA2 to the phone and also rename it to Update.zip, flash it again. Final reboot, its now the official 2.1 android update. Also the root is still there.
OTA1
Badongo file 23546527
OTA2
Badongo file 23546783
THANKS again!!!
(sorry about the link, they won't let me post it ><)
Click to expand...
Click to collapse
PM u, thank you.
Could you tell me the Second HK OTA Package filename?
I really need it, if anyone who know it, please tell me.
Thank you very much.
hello, I flashed RUU_Hero_hTC_Asia_HK_WWE_3.34.721.1_R_Radio_63.18. 55.06P_6.35.15.14_release_signed on my taiwaan hero using goldcard and now i cannot flash my RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoD river. . . please help me! it says error - invalid update tool! WTF ... i have used that ruu many times but now it aint working. it strucks at updating signature.
and even the flash recovery software aint working !
hello, I flashed RUU_Hero_hTC_Asia_HK_WWE_3.34.721.1_R_Radio_63.18. 55.06P_6.35.15.14_release_signed on my taiwaan hero using goldcard and now i cannot flash my RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoD river. . . please help me! it says error - invalid update tool! WTF ... i have used that ruu many times but now it aint working. it strucks at updating signature.
and even the flash recovery software aint working !
I think u need to restore it back to your 1.5 backup first.
Thanks for Hero-err.. I have solved my problem too by following his hints ^_^
i dont have flashed recovery so how would i do nandroid restore ?
Hi guys! I downloaded the "A500BootLogo_105_v8plus_win" tool that changes the boot logo of the bootloader, opened the "bootloader_v8_blue.bin" and changed the splash screen and some colors, saved it and flashed through the fastboot, but when I restart my A500, nothing happens. Any guess?
If you want to update bootloader using fastboot you need to modify and use the blob file instead of bin.
Bin file can be successfully flashed only by downloading it to tablet with nvflash in APX mode.
I tried to update as *.blob but still nothing happend.
Do I have to put a specific name to flash? (I named it custombootloader.blob)
I'm using the command "fastboot flash recovery custombootloader.blob"
Is that right?
Why are you flashing recovery partition with bootloader? The update command is: fastboot flash bootloader custombootloader.blob . The tablet will automatically reboot after the flashing finishes.
verzzolla said:
I tried to update as *.blob but still nothing happend.
Do I have to put a specific name to flash? (I named it custombootloader.blob)
I'm using the command "fastboot flash recovery custombootloader.blob"
Is that right?
Click to expand...
Click to collapse
You can't just "re-name" a file to xxxxxxxxxx.blob. Won't work (at least I wouldn't do it that way). You have to save the file as a true "blob". Surprised you didn't fubar the tab
In the bootloader app., ckick the dropdown at the bottom, and you can save it as a "blob" file instead of "bin"
MD
Thanks very much Skrilax_CZ, it worked!
That was the problem.
@Moscow Desire
That's what I did... saved it as *.blob.
The rename which I was referring was to the name of the file.
verzzolla said:
Thanks very much Skrilax_CZ, it worked!
That was the problem.
@Moscow Desire
That's what I did... saved it as *.blob.
The rename which I was referring was to the name of the file.
Click to expand...
Click to collapse
Great! Glad it's running.
Yeah, everytime somebody says "rename",,,,, ohhhhhhh....
I love the ones "update.zip.zip"
Hi, I was trying to flash back to stock using the utility for the RAZR M. I was able to successfully flash back but then the OTA update stuck me in AP Fastboot Flash (s). The only screen I can get to says:
AP Fastboot Flash Mode (S)
10.9B(*)(sha-1e9f557,2013-05-24 14:49:34)
eMMC Info: Size 8GB
Device Is LOCKED(I did unlock this no idea why it is saying locked), Status Code:0
BatteryK
Connect USB
Data Cable (or USB Connected)
downgraded security version
update gpt_main version failed
Failed to hab check for gpt_backup:0x35
failed to load GPT
CID Read Failure
Invalid CID Status 0x69
This is the only screen I have been able to get to. I have looked around and haven't found any answers. Anything is appreciated.
just fixed mine
KamexxTheWolf said:
Hi, I was trying to flash back to stock using the utility for the RAZR M. I was able to successfully flash back but then the OTA update stuck me in AP Fastboot Flash (s). The only screen I can get to says:
AP Fastboot Flash Mode (S)
10.9B(*)(sha-1e9f557,2013-05-24 14:49:34)
eMMC Info: Size 8GB
Device Is LOCKED(I did unlock this no idea why it is saying locked), Status Code:0
BatteryK
Connect USB
Data Cable (or USB Connected)
downgraded security version
update gpt_main version failed
Failed to hab check for gpt_backup:0x35
failed to load GPT
CID Read Failure
Invalid CID Status 0x69
This is the only screen I have been able to get to. I have looked around and haven't found any answers. Anything is appreciated.
Click to expand...
Click to collapse
I had exact thing happen. droidrzr.com/house of razr .House of Moto. I couldn't get utility to work but I grabbed new sbf file for update extracted it grabbed his support script for m razr extracted it grabbed RSD FULL script only dropped it in my xml file opened RSD navigated to script inside xml opened n RSD and it ran!! woop woop I was 3 days screwed like u..when it booted I only have 4 present left ...close but all good now
jimyv said:
I had exact thing happen. droidrzr.com/house of razr .House of Moto. I couldn't get utility to work but I grabbed new sbf file for update extracted it grabbed his support script for m razr extracted it grabbed RSD FULL script only dropped it in my xml file opened RSD navigated to script inside xml opened n RSD and it ran!! woop woop I was 3 days screwed like u..when it booted I only have 4 present left ...close but all good now
Click to expand...
Click to collapse
ok I did that. It said a lot of things but kept getting
sending <partition>
...okay
writing <partition>
...failed [no such partition]
u did this?
KamexxTheWolf said:
ok I did that. It said a lot of things but kept getting
sending <partition>
...okay
writing <partition>
...failed [no such partition]
Click to expand...
Click to collapse
Default try
Quote:
Originally Posted by A. Nonymous View Post
Same thing. Getting the "failed no such partition" errors as well.
grab this VRZ_XT907_9.8.1Q-94-1_CFC.xml at http://sbf.droid-developers.org/ exract it. grab this http://www.mediafire.com/download/tq...Moto-xt907.zip . extract all. grab this only FULL_xt907.out of/ rsd_scripts / folder drop in ur extracted sbf file open RSD lit v 6.1.5 . navigate to the script u dropped inside ur extracted sbf file add select the FULL_xt907 script udropped and run..fixed mine not my work just made a luck guess combination that worked for me...thank House of Moto guy for script over at droidrzr.com.,.,I used the RSD lite that is in the Houseof Moto http://www.droidrzr.com/index.php/to...house-of-moto/ All thanks it his WORK/ extract it all and go to HouseOfMoto_1.4/HouseOfMoto/rsd/SDL/ run that one I don't know if theres goodies in threr that help or what but it worked for me that way only...of course have drivers installed / I didn't need adb setup just make sure ur run as administrater
jimyv said:
Default try
Quote:
Originally Posted by A. Nonymous View Post
Same thing. Getting the "failed no such partition" errors as well.
grab this VRZ_XT907_9.8.1Q-94-1_CFC.xml at http://sbf.droid-developers.org/ exract it. grab this http://www.mediafire.com/download/tq...Moto-xt907.zip . extract all. grab this only FULL_xt907.out of/ rsd_scripts / folder drop in ur extracted sbf file open RSD lit v 6.1.5 . navigate to the script u dropped inside ur extracted sbf file add select the FULL_xt907 script udropped and run..fixed mine not my work just made a luck guess combination that worked for me...thank House of Moto guy for script over at droidrzr.com.,.,I used the RSD lite that is in the Houseof Moto http://www.droidrzr.com/index.php/to...house-of-moto/ All thanks it his WORK/ extract it all and go to HouseOfMoto_1.4/HouseOfMoto/rsd/SDL/ run that one I don't know if theres goodies in threr that help or what but it worked for me that way only...of course have drivers installed / I didn't need adb setup just make sure ur run as administrater
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2528132 guess it worked for him . good luck!
Droid Razr M Is Stuck In AP Fastboot After OTA Update!
I cant get anything to work the same thing happened to mine cant figure this out please help!
Hello!
I have the Nexus 6P and I have successfully rooted 16 phones over the past 4 years and never had a problem I couldn't fix. Today I made a mess of my new phone.
I had a perfectly working custom ROM with an unlocked boot loader with TWRP (2.8.7.2) installed. I installed some custom soft keys and got into a boot loop. I went and flashed what I thought was the stock ROM according to the website I was following, and I re locked my boot loader like a fool and was going to eventually unlock it.... turns out I was still boot looped.
I have tried:
sideloading 3 different zips, always get the message "cannot read zip" whatever the zip is
I tried changing the names, doing the full names, doing a stock rooted zipped ROM, nothing works.
I have used SkipSoft and Wugs toolkit and I can't flash ANYTHING or transfer files onto the phone unless the bootloader is unlocked.
I have installed the Google drivers multiple times, ADB devices always works, it seems to not be a driver issue because I can do everything else fine.
I have let the phone sit for 35 minutes in bootloop waiting for it to come back online so I can tick that "OEM unlock" button in the settings menu.
I have also done a dozen other things, the problem is nothing I have done or tried allows me to get any ROM or any file onto the device to flash in TWRP.
Help?
ok shot in the dark here. I had a boot loop until I flashed the flashable vendors zip
I got it in this thread:
http://forum.xda-developers.com/nexus-6p/development/rom-pure-nexus-layers-fi-wifi-calling-t3244563
Give it a whirl if you haven't already.
Found this in the Pure Nexus Project thread, so props to them for providing this.
-MotoNexus- said:
Hello!
I have the Nexus 6P and I have successfully rooted 16 phones over the past 4 years and never had a problem I couldn't fix. Today I made a mess of my new phone.
I had a perfectly working custom ROM with an unlocked boot loader with TWRP (2.8.7.2) installed. I installed some custom soft keys and got into a boot loop. I went and flashed what I thought was the stock ROM according to the website I was following, and I re locked my boot loader like a fool and was going to eventually unlock it.... turns out I was still boot looped.
I have tried:
sideloading 3 different zips, always get the message "cannot read zip" whatever the zip is
I tried changing the names, doing the full names, doing a stock rooted zipped ROM, nothing works.
I have used SkipSoft and Wugs toolkit and I can't flash ANYTHING or transfer files onto the phone unless the bootloader is unlocked.
I have installed the Google drivers multiple times, ADB devices always works, it seems to not be a driver issue because I can do everything else fine.
I have let the phone sit for 35 minutes in bootloop waiting for it to come back online so I can tick that "OEM unlock" button in the settings menu.
I have also done a dozen other things, the problem is nothing I have done or tried allows me to get any ROM or any file onto the device to flash in TWRP.
Help?
Click to expand...
Click to collapse
Thanks, the problem is I can't find a way to sideload anything or move a file over. Everything results in a myriad of errors.
tigercranestyle said:
at worst, you would have to invoke the flash-all command via adb once you extracted the couple of times that you have to. directions are on google's factory image site.
may not be the answer that you were looking for, but it always feels great having a clean device to work with. i mean as it stands, you would have to set everything back up on whatever rom anyway if you somehow got out of the problems you were having. you would spend more time doing that instead of just going the factory image route.
toolkits are fun, but learning your way around them is even more so.
Click to expand...
Click to collapse
I'm gonna check the flash all,I've never done that before. I think that would be all the images in the tgz factory image? Anything to get my phone back yeah, I just need it working again.
-UPDATE- I tried the flash all batch in the system image and I tried the flash all batch command and neither work.
Hey man - crazy story - I literally just got done messing with a toolkit and the EXACT same situation happened to me. Locked bootloader, bootloop, everything. What you need to do is do a complete wipe of everything in TWRP so you can access /data from your PC (unless it isn't messed up currently, and you can decrypt within TWRP, I couldn't...) Then, download Cataclysm (maybe something else will work, idk, but I just did it with cataclysm) and bam - it boots, head to developer options and get the box checked.
Stock images didn't work, nothing did... was scared I had a brick. The saving grace for us is that we both got TWRP installed. No more toolkits for me!
Melamunna said:
Hey man - crazy story - I literally just got done messing with a toolkit and the EXACT same situation happened to me. Locked bootloader, bootloop, everything. What you need to do is do a complete wipe of everything in TWRP so you can access /data from your PC (unless it isn't messed up currently, and you can decrypt within TWRP, I couldn't...) Then, download Cataclysm (maybe something else will work, idk, but I just did it with cataclysm) and bam - it boots, head to developer options and get the box checked.
Stock images didn't work, nothing did... was scared I had a brick. The saving grace for us is that we both got TWRP installed. No more toolkits for me!
Click to expand...
Click to collapse
I have already done the advance wipe and the format data, I just tried again and my computer will not read it as storage with MTP enabled.
Thanks though!
tigercranestyle said:
after extracting the tgz file, it should become a tar file. after extracting that tar file, it should become the six files listed below. these files should be in platform-tools to start from scratch.
bootloader-angler-angler-02.45.img
flash-all.bat
flash-all.sh
flash-base.sh
image-angler-mmb29m.zip
radio-angler-angler-02.50.img
once they are, open command line in that directory (platform-tools) and then "flash-all" should work. if it doesn't make sure you post the error that you're getting on your computer so that others can help.
Click to expand...
Click to collapse
I followed all these steps, I unzipped it and everything and put it in my fastboot folder. I still get the "unknown partition "all" " orrr flash is not recognized as an internal or external command, operable program or batch file. In an attempt with desperation I tried opening every version of the batch file, in the tgz and tar and unzipped AND in the fastboot and it all gives the radio img error.
I still do have my fastboot device connected, to my knowledge that means it can't be a driver problem right?
-MotoNexus- said:
I followed all these steps, I unzipped it and everything and put it in my fastboot folder. I still get the "unknown partition "all" " orrr flash is not recognized as an internal or external command, operable program or batch file. In an attempt with desperation I tried opening every version of the batch file, in the tgz and tar and unzipped AND in the fastboot and it all gives the radio img error.
I still do have my fastboot device connected, to my knowledge that means it can't be a driver problem right?
Click to expand...
Click to collapse
You can't flash anything in fastboot with a locked bootloader. The only way you can get your device to work is by using TWRP to flash a rom.
The flash all command doesn't work because the extracted tar file has A zipped folder inside that has to be extracted also with radio and I think recovery zipped up. You have to extract those two files to put them in the tar file and then you might be able to flash all. But as long as you can fastboot devices you should be able to flash all 6 files and have a brand new device.
tigercranestyle said:
sorry for the late reply. not always here.
1. did you unlock the bootloader again before doing all of this?
2. list the files that are in your platform-tools folder.
3. when you executed the "flash-all" command earlier, you did do it with the dash in between flash and all... right? also, you're doing it without the quotation marks, right?
sorry if they seem silly. just never really know.
Click to expand...
Click to collapse
He can't unlock the bootloader without booting into a rom. He needs to use twrp to flash a full system but I am not sure how to help with that when he can't sideload.
just an unrelated question... why did you lock the bootloader again? what was the purpose?
also, as mentioned... locked bootlader, odds arre USB debugging and OEM unlock are also not checked.... afaik, youre in trouble... hopefully someone else can sav you, im out of ideas
akellar said:
You can't flash anything in fastboot with a locked bootloader. The only way you can get your device to work is by using TWRP to flash a rom.
Click to expand...
Click to collapse
Are you telling me that I'm bricked?
I have no way of transfering files to the devices, it won't read as anything to transfer files and ADB won't sideload anything.
tigercranestyle said:
sorry for the late reply. not always here.
1. did you unlock the bootloader again before doing all of this?
2. list the files that are in your platform-tools folder.
3. when you executed the "flash-all" command earlier, you did do it with the dash in between flash and all... right? also, you're doing it without the quotation marks, right?
sorry if they seem silly. just never really know.
Click to expand...
Click to collapse
Neither am I , I just got back from a trip. I have the fastboot exe adb exe mfastboot exe the ADB api files, and the ROMs I tried to sideload along with all the images I pushed to the device.
Originally I had the bootloader unlocked, like I said I was being a fool blindly following a tutorial to get back to stock and I locked it too soon.
Yeah, I tried flash-all flash all and flash flash-all / flash flash all
dontbeweakvato said:
The flash all command doesn't work because the extracted tar file has A zipped folder inside that has to be extracted also with radio and I think recovery zipped up. You have to extract those two files to put them in the tar file and then you might be able to flash all. But as long as you can fastboot devices you should be able to flash all 6 files and have a brand new device.
Click to expand...
Click to collapse
Okay I unzipped that folder and put all the files in the fastboot folder, I still get the same error. The thing that scares me here is I can use the batch file now and it just gives me an error saying it can't flash because it's bootloader is locked.
Soulfly3 said:
just an unrelated question... why did you lock the bootloader again? what was the purpose?
also, as mentioned... locked bootlader, odds arre USB debugging and OEM unlock are also not checked.... afaik, youre in trouble... hopefully someone else can sav you, im out of ideas
Click to expand...
Click to collapse
They are default unchecked, hence the reason I can't unlock the bootloader again. I said it in my first post, I was being a fool following some guide to get back to stock and ******* up a step.
rift999 said:
He can't unlock the bootloader without booting into a rom. He needs to use twrp to flash a full system but I am not sure how to help with that when he can't sideload.
Click to expand...
Click to collapse
Is there not a way to fix the sideload? Or a way to get my computer to read it as a media devices so I can transfer files or something? It's always worked with previous phones but my computer reads the 6P differently. (even when it was working)
Stop trying to fastboot flash anything, it will not work as I've already started multiple times. The only option you have is to get something moved to storage and flash it from twrp.
akellar said:
Stop trying to fastboot flash anything, it will not work as I've already started multiple times. The only option you have is to get something moved to storage and flash it from twrp.
Click to expand...
Click to collapse
I've tried every driver from Google and Nexus 6P, I can't get it to read the MTP for a file transfer, what would you suggest I do? it doesn't show up as my old phones used to in the computers drives.
I have found 0 success with getting a file on through file transfer or ADB push file.
-MotoNexus- said:
I've tried every driver from Google and Nexus 6P, I can't get it to read the MTP for a file transfer, what would you suggest I do? it doesn't show up as my old phones used to in the computers drives.
I have found 0 success with getting a file on through file transfer or ADB push file.
Click to expand...
Click to collapse
Can't help too much personally, but you might give this a shot:
http://forum.xda-developers.com/showpost.php?p=64317181&postcount=20
Sent from my Nexus 6P using XDA Free mobile app
So I just got it............!!!!! I have spent a total of 16 hours with videos, forums and trial and error. When I was going back the 5th around time messing with drivers I turned my ADB driver into a USB composite because I had no idea I could and instantly I was able to file transfer!!!! Problem solved, I have my ROM on now.
Thank you all for your help! I am so sorry I derped at this, I have been doing this a long time and just got sloppy.
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