Related
ok so i had my hero on the stock fresh rom from his kitchen and i decided to try out the new dc2.08.1 to see if there were still bugs that made me not want to use the older 2.1 roms. after flashing it no audio worked at all not even when talking on the phone. so i did a nandroid restore of a backup i made right before flashing DC. everything seemed to be back to normal but then i realized my audio is still not working but in calls it is working. i figured the restore messed up so i tried again and it didnt work for some reason. then i downloaded gumbo1.5c from my phone and flashed that and everything was perfect once again. the whole day my phone was flawless until last night at 2am i went to set an alarm clock and for some reason that triggered the audio to go off again. so i restarted my phone and figured it might fix itself but it didnt and i already deleted gumbo off my sd. i downloaded it again and then my phone seemed to start getting sluggish and finally completely froze after a while. i removed the battery and tried to turn it back on but it got stuck at the htc screen. then i tried to get into recovery but that doesnt work either now... fastboot does boot up and i tried to ruu from it but when the ruu is rebooting to bootloader my phone just stays off and doesnt reboot.. i did notice on fastboot it says "touch panel-fail".
before installing or restoring any roms i did wipe everything does anyone know what i have to do to restore my hero or am i just completely screwed D:
do a search for ruu error 110. try doing what it says and you should be able to get back to stock, and either take your phone in or flash again.
alright i will try that but i didnt have the 110 error any other possible solutions if this dont work? thx for the response
dylan6879 said:
alright i will try that but i didnt have the 110 error any other possible solutions if this dont work? thx for the response
Click to expand...
Click to collapse
What's he's saying is that if your phone has hardware issues, then you need to do the RUU to put it back to stock or sprint might not fix it under warranty.
I agree with the above, sounds like a hardware issue although the timing of the issue with a flash sounds strange.
yea i thought it might be a hardware issue but it just seems odd how it happened after flashing 2.1 and then reverting to 1.5. I want to bring it back to sprint but dont want to get screwed over because of it being rooted. i want to ruu but the phone just seems to be dead and doesnt want to do anything besides fastboot and show the htc screen
Some people have problems with the RUU, but the steps to fix the Error 110 after RUU'ing, should work anytime regardless if you RUUed or not. Your recovery could have gotten deleted. Try flashing it from fastboot. There are directions in this forum on how to do it from fastboot.
ok well i kept trying to do the ruu and i got it to run once and it completed succesfully... so i thought maybe i had fixed it but then it still wont boot and only shows the htc screen but fastboot still works so can someone link me to the thread that tells hows to reflash recovery from fastboot. ill look for it but just incase i cant find it.
dylan6879 said:
ok well i kept trying to do the ruu and i got it to run once and it completed succesfully... so i thought maybe i had fixed it but then it still wont boot and only shows the htc screen but fastboot still works so can someone link me to the thread that tells hows to reflash recovery from fastboot. ill look for it but just incase i cant find it.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=674788
EVERYTHING, including the 110 fix is in that post.
i looked there i know the 110 error fix is in there but i cant find anything on flashing recovery through fastboot
dylan6879 said:
i looked there i know the 110 error fix is in there but i cant find anything on flashing recovery through fastboot
Click to expand...
Click to collapse
Did you try following his procedure? it should resolve your issue.
otherwise: fastboot flash recovery recoveryimagefilename
Pro tip: in a windows command prompt if you go to your androidsdk\tools directory and type 'fastboot' it will give you all the options.
alright so ive tried the 110 error fix and i cant get past the first step because my command prompt wont recognize the device.
thx for telling me how to get to fastboot commands and i tried installing a new rom from there but i cant type it correctly im not sure what i typed wrong. it say the syntax of the command is incorrect. im trying to do the command "update <filename>" so i typed in "fastboot update <update.zip>".
dylan6879 said:
alright so ive tried the 110 error fix and i cant get past the first step because my command prompt wont recognize the device.
thx for telling me how to get to fastboot commands and i tried installing a new rom from there but i cant type it correctly im not sure what i typed wrong. it say the syntax of the command is incorrect. im trying to do the command "update <filename>" so i typed in "fastboot update <update.zip>".
Click to expand...
Click to collapse
You don't need the < > in there.
fastboot update update.zip should work.
thx i tried it that way and it it went through but then said
"archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt"
dylan6879 said:
thx i tried it that way and it it went through but then said
"archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt"
Click to expand...
Click to collapse
What exactly are you trying to flash? What's the filename, and what's it for?
If this is a ROM you don't want update.
If it's a recovery image:
fastboot flash recovery recoveryimagename.zip
oh yeah i was trying to flash a rom. i thought u could do that from there. where should i have the recovery img before i flash it. and is it possible to flash a rom through here?
ok so i put the recovery in the same place i had the roms and it went through but now it failed saying "sending 'recovery' <2326 KB>... FAILED <remote: not allow>".
dylan6879 said:
ok so i put the recovery in the same place i had the roms and it went through but now it failed saying "sending 'recovery' <2326 KB>... FAILED <remote: not allow>".
Click to expand...
Click to collapse
It's probably possible to flash a rom through fastboot, but I've never done it.
What recovery image are you using? And what is the exact name of the recovery image file? Where exactly did you put the recovery image file?
i tried the clockwork 1.7.6 and 1.5.2 and i tried them zipped up and as img files. i put them in the tools folder in android-sdk-windows. btw thx for all ur help
the name of the recovery image files are clockwork.zip, clockwork.img, 152.zip, and 152.img those are the four files i tried
dylan6879 said:
i tried the clockwork 1.7.6 and 1.5.2 and i tried them zipped up and as img files. i put them in the tools folder in android-sdk-windows. btw thx for all ur help
the name of the recovery image files are clockwork.zip, clockwork.img, 152.zip, and 152.img those are the four files i tried
Click to expand...
Click to collapse
Never used it, and 1.5.2 is old. I suggest downloading AmonRA's 1.6.2
You can't use zip files with fastboot...it wants the actual image (at least in this case, because those zip files aren't updates, they're just zip files).
So you should put the 152.img in the same directory as fastboot (Android-sdk-windows\tools)
Then you should do: fastboot flash recovery 1.5.2.img
What happens when you do that?
i tried flashing the 1.6.2.img and got the same result it says "sending 'recovery' <3720 KB>... FAILED <remote: not allow>".
Hi there.
So I wanted to install cyanogenmod on my htc incredible s. So i rooted my phone without big problems. Then I tried to install cyanogenmod through 4ext recovery via zip file. And now all I have is a static white screen. I tried over 10 ruu's that supposed to be installed from pc and phone. I tried another recovery, custom OS, hard reset through recovery and bootloader, goldcard and some other things that I cant even remember. I also tried to lock bootloader, unlock it, reset root etc.
android version before brick was 4.0.4, sense 3.6.
vivo s-on
hboot 2.02.0002
radio 3831.18.00.11_M
Also when i install cm or some other custom OS through 4ext zip install it says OK but when i reload nothing changes.
Help?
Killa_vatt said:
Hi there.
So I wanted to install cyanogenmod on my htc incredible s. So i rooted my phone without big problems. Then I tried to install cyanogenmod through 4ext recovery via zip file. And now all I have is a static white screen. I tried over 10 ruu's that supposed to be installed from pc and phone. I tried another recovery, custom OS, hard reset through recovery and bootloader, goldcard and some other things that I cant even remember. I also tried to lock bootloader, unlock it, reset root etc.
android version before brick was 4.0.4, sense 3.6.
vivo s-on
hboot 2.02.0002
radio 3831.18.00.11_M
Also when i install cm or some other custom OS through 4ext zip install it says OK but when i reload nothing changes.
Help?
Click to expand...
Click to collapse
With an unlocked bootloader 2.02.0002, you need to extract the boot.img from the CM ROM's zip.file and manually flash it in FASTBOOT USB mode.
You cannot simply flash a custom ROM from 4EXT recovery when you only have an unlocked bootloader. There are plenty of sticky threads in this forum that document the procedure you need to follow. You need to read, study and understand before you try modding your phone.
tpbklake said:
With an unlocked bootloader 2.02.0002, you need to extract the boot.img from the CM ROM's zip.file and manually flash it in FASTBOOT USB mode.
You cannot simply flash a custom ROM from 4EXT recovery when you only have an unlocked bootloader. There are plenty of sticky threads in this forum that document the procedure you need to follow. You need to read, study and understand before you try modding your phone.
Click to expand...
Click to collapse
Still stuck at HTC boot screen. Maybe bad cm file?
I readed many guides on tons of sites but all of them says different things =\
Killa_vatt said:
Still stuck at HTC boot screen. Maybe bad cm file?
I readed many guides on tons of sites but all of them says different things =\
Click to expand...
Click to collapse
if the cm.zip is bad; recovery itself tells BAD ZIP
BTW why dont you flash another rom??
there are much better roms than CM!!
try it!!
so that we will know whether the problem is in phone or rom that you are flashing???
prunzzz said:
if the cm.zip is bad; recovery itself tells BAD ZIP
BTW why dont you flash another rom??
there are much better roms than CM!!
try it!!
so that we will know whether the problem is in phone or rom that you are flashing???
Click to expand...
Click to collapse
I have already tried many ways to install many other roms. What will you recommend?
Killa_vatt said:
I have already tried many ways to install many other roms. What will you recommend?
Click to expand...
Click to collapse
what kind of errors did you get when you flashed other roms??
prunzzz said:
what kind of errors did you get when you flashed other roms??
Click to expand...
Click to collapse
If I am flashing from exe file through fastboot I get ERROR [131]: CUSTOMER ID ERROR.
If I use fastboot flash boot boot.img I get no errors but it still stucks on HTC screen.
If I flash using 4ext install zip mode I still get no errors but it stucks.
I also got error that I dont have boot.prop in my system.
I cant remember other errors that I had.
Killa_vatt said:
If I am flashing from exe file through fastboot I get ERROR [131]: CUSTOMER ID ERROR.
If I use fastboot flash boot boot.img I get no errors but it still stucks on HTC screen.
If I flash using 4ext install zip mode I still get no errors but it stucks.
I also got error that I dont have boot.prop in my system.
I cant remember other errors that I had.
Click to expand...
Click to collapse
have you tried flashing through HBOOT??
prunzzz said:
have you tried flashing through HBOOT??
Click to expand...
Click to collapse
That is done by renaming a file to PG98***?
Killa_vatt said:
If I am flashing from exe file through fastboot I get ERROR [131]: CUSTOMER ID ERROR.
If I use fastboot flash boot boot.img I get no errors but it still stucks on HTC screen.
If I flash using 4ext install zip mode I still get no errors but it stucks.
I also got error that I dont have boot.prop in my system.
I cant remember other errors that I had.
Click to expand...
Click to collapse
The ERROR 131 means that you are trying to flash an official RUU for a different carrier/region. You need to create a goldcard in order to successfully flash a RUU.
Why don't you try flashing a custom ROM from recovery and then flash the boot.img file.
tpbklake said:
The ERROR 131 means that you are trying to flash an official RUU for a different carrier/region. You need to create a goldcard in order to successfully flash a RUU.
Why don't you try flashing a custom ROM from recovery and then flash the boot.img file.
Click to expand...
Click to collapse
Ive created a goldcard.
I tried to flash a custom rom-still stuck at whitescreen.
Killa_vatt said:
Ive created a goldcard.
I tried to flash a custom rom-still stuck at whitescreen.
Click to expand...
Click to collapse
OK, after re-reading your posts, here are some additional tips:
When flashing a custom ROM from 4EXT, please make sure you do a full system wipe and then clear both Cache and Dalvik cache before you flash the ROM.
After you flash the ROM, then you need to immediately flash the ROM's boot.img file contained in the zip file using FASTBOOT USB mode.
As for trying to flash 10 different RUU's there ERROR 131 indicates that you have a bad goldcard.
Killa_vatt said:
That is done by renaming a file to PG98***?
Click to expand...
Click to collapse
Hey not PG98!!!!
PG32IMG.zip!!!!!
Try it now
Also consider what tpbklake said
HIT THANKS IF I HELPED YOU
tpbklake said:
When flashing a custom ROM from 4EXT, please make sure you do a full system wipe and then clear both Cache and Dalvik cache before you flash the ROM.
After you flash the ROM, then you need to immediately flash the ROM's boot.img file contained in the zip file using FASTBOOT USB mode.
Click to expand...
Click to collapse
prunzzz said:
Hey not PG98!!!!
PG32IMG.zip!!!!!
Try it now
Click to expand...
Click to collapse
I mean PG32IMG,forgot that.
I fully wiped everything.
I did not flashed rom's boot.img,thanks! Gonna try it later.
tpbklake said:
After you flash the ROM, then you need to immediately flash the ROM's boot.img file contained in the zip file using FASTBOOT USB mode.
Click to expand...
Click to collapse
Thank you very much! I feel dummy now =)
Flashing rom's boot.img fixed all problems. Most of roms works now. Thanked everyone in topic.
Hellos guys,
I am trying to find the stock recovery for T-mobile US 6.10.531.10 (NOT 6.10.531.9) . Does anybody has it or point me on the right direction? I want to update my phone through OTA so I can get lollipop however I cannot find the stock recovery.
I am S-On all stock except for the recovery, I had TWRP so I can make backups. Now I want to install back the stock recovery so i can upgrade but I don't seem to find it anywhere. I managed to find the RUU but the recovery image is not inside the "rom.zip" on my Temp folder when I run it. These are the only files that it shows:
android-info.txt
dzdata_16g.hdr
dzdata_32g.hdr
dzdata_64g.hdr
tp_HMX852XD.img
boot_signed.img
dzdata_16.img
dzdata_32.img
dzdata_64.img
Am I missing something? Please help. I have tried to find it the whole day with no luck.
Also see the the screenshot.
adtamez said:
Hellos guys,
I am trying to find the stock recovery for T-mobile US 6.10.531.10 (NOT 6.10.531.9) . Does anybody has it or point me on the right direction? I want to update my phone through OTA so I can get lollipop however I cannot find the stock recovery.
I am S-On all stock except for the recovery, I had TWRP so I can make backups. Now I want to install back the stock recovery so i can upgrade but I don't seem to find it anywhere. I managed to find the RUU but the recovery image is not inside the "rom.zip" on my Temp folder when I run it. These are the only files that it shows:
android-info.txt
dzdata_16g.hdr
dzdata_32g.hdr
dzdata_64g.hdr
tp_HMX852XD.img
boot_signed.img
dzdata_16.img
dzdata_32.img
dzdata_64.img
Am I missing something? Please help. I have tried to find it the whole day with no luck.
Also see the the screenshot.
Click to expand...
Click to collapse
just run the Lollipop RUU, same as the OTA but its the full thing rather than an OTA: http://www.htc.com/us/support/htc-one-t-mobile/news/ follow the manual update instructions, download is at the bottom.
edit: it will wipe your phone, so backup anything you want to keep first.
Seanie280672 said:
just run the Lollipop RUU, same as the OTA but its the full thing rather than an OTA: http://www.htc.com/us/support/htc-one-t-mobile/news/ follow the manual update instructions, download is at the bottom.
edit: it will wipe your phone, so backup anything you want to keep first.
Click to expand...
Click to collapse
Seanie, thank you for your reply. I need the stock recovery because precisely I was trying to avoid wiping my phone. I am just a very small step away to be able to update without wiping, I just can't find this stock recovery. Why is it that the recovery.img it is not inside the rom.zip RUU? Am I missing something?
Currently I flashed the stock recovery 6.10.5310.9 and i tried to install the OTA but when it gets to the recovery it looks like it starts installing moving the green line a little bit but soon after I get a red triangle and stops, which I am assuming it is because i do not have the proper recovery.
Any help so i do not need to wipe will be greatly appreciate it.
Thanks!
adtamez said:
Seanie, thank you for your reply. I need the stock recovery because precisely I was trying to avoid wiping my phone. I am just a very small step away to be able to update without wiping, I just can't find this stock recovery. Why is it that the recovery.img it is not inside the rom.zip RUU? Am I missing something?
Currently I flashed the stock recovery 6.10.5310.9 and i tried to install the OTA but when it gets to the recovery it looks like it starts installing moving the green line a little bit but soon after I get a red triangle and stops, which I am assuming it is because i do not have the proper recovery.
Any help so i do not need to wipe will be greatly appreciate it.
Thanks!
Click to expand...
Click to collapse
ok, you cant take it out of the RUU.zip as its an encrypted RUU, so take it out of the OTA.
download the OTA as normal, but select install later, then plug your phone into the computer and copy the OTA.zip to your computer from your phone, its in the internal storage, downloads folder, its just a zip file, so once its on your computer, open it with WinRAR or whatever you use to open zip files and in there you will see firmware.zip, open that too and take out recovery.img, flash it like any other recovery, then reboot and try and update again.
If the OTA then fails again, it will be down to modified system files or root, you will have no choice but to backup and use the full RUU.
Seanie280672 said:
ok, you cant take it out of the RUU.zip as its an encrypted RUU, so take it out of the OTA.
download the OTA as normal, but select install later, then plug your phone into the computer and copy the OTA.zip to your computer from your phone, its in the internal storage, downloads folder, its just a zip file, so once its on your computer, open it with WinRAR or whatever you use to open zip files and in there you will see firmware.zip, open that too and take out recovery.img, flash it like any other recovery, then reboot and try and update again.
Click to expand...
Click to collapse
oh I see. Thank you very much...quick question though: I am currently on version 6.10.513.10 the OTA is to upgrade to version 7.18.513.2, if i extract the recovery from this OTA i will be flashing the 7.18. recovery, isn't? Don't I need the recovery from 6.10 in order to be able to upgrade? If so, this is why i was looking also for the 6.10.513.10 OTA but I cannot find it.
Thank you again!
adtamez said:
oh I see. Thank you very much...quick question though: I am currently on version 6.10.513.10 the OTA is to upgrade to version 7.18.513.2, if i extract the recovery from this OTA i will be flashing the 7.18. recovery, isn't? Don't I need the recovery from 6.10 in order to be able to upgrade? If so, this is why i was looking also for the 6.10.513.10 OTA but I cannot find it.
Thank you again!
Click to expand...
Click to collapse
the OTA will check to see if you have 6.10.513.10 or 7.18.513.2 recovery, cant be anything earlier than those 2, current or previous, recovery update by the OTA will just be skipped.
Seanie280672 said:
the OTA will check to see if you have 6.10.513.10 or 7.18.513.2 recovery, cant be anything earlier than those 2, current or previous, recovery update by the OTA will just be skipped.
Click to expand...
Click to collapse
I see! Great news! Good to know. So the OTA can be install with a newer stock recovery (matching the OTA I presume).
I am currently at work without my cell phone but I will try this, as soon as I get back home and post the results.
One last thing, to flash the stock recovery is as simple as "fastboot flash recovery recovery.img" (or whatever the recovery file .img name is), correct?
I do not need to lock the bootloader in order to upgrade using the OTA as long as everything else is still stock. ...I do have root though, but I also read that this shouldn't be a problem either, correct?
Thank you sooo much!
adtamez said:
I see! Great news! Good to know. So the OTA can be install with a newer stock recovery (matching the OTA I presume).
I am currently at work without my cell phone but I will try this, as soon as I get back home and post the results.
One last thing, to flash the stock recovery is as simple as "fastboot flash recovery recovery.img" (or whatever the recovery file .img name is), correct?
I do not need to lock the bootloader in order to upgrade using the OTA as long as everything else is still stock. ...I do have root though, but I also read that this shouldn't be a problem either, correct?
Thank you sooo much!
Click to expand...
Click to collapse
No need to lock the bootloader for an ota, root might be a problem as it modifies system files, just give it a go, and yes, the flash of the recovery is the same as any other recovery file.
Seanie280672 said:
No need to lock the bootloader for an ota, root might be a problem as it modifies system files, just give it a go, and yes, the flash of the recovery is the same as any other recovery file.
Click to expand...
Click to collapse
Got it. I'll try and post results. Thank you very much.
adtamez said:
Got it. I'll try and post results. Thank you very much.
Click to expand...
Click to collapse
Seanie, all went as expected! It worked. I was able to extract the recovery.img file from the firmware.zip inside the 7.18 OTA zip file that was downloaded to the internal storage. Then proceed to flash it as any other recovery with fastboot. Afer that, the OTA update installed with o problem. Having root did not mattered. I did have to root it again though.
Thank you so much for your support!!! :good:
Worked for me as well, thank you.
I really messed my phone up its got no OS and its stuck in bootloop iv tried pushing cm-12 onto it and installing it but i keep getting error codes with what you see in the picture. can anyone help.
Burky1996 said:
I really messed my phone up its got no OS and its stuck in bootloop iv tried pushing cm-12 onto it and installing it but i keep getting error codes with what you see in the picture. can anyone help.
Click to expand...
Click to collapse
Try re download the zip (or try an other rom)maybe you just got an false download. i also had some trouble with my m7 back in the day.
But in your case now you are stuck with no os or bootloop, i give you as advice to follow an soft unbrick method it worked for me, or if you have an usb otg cable and usb or and usb otg thumbstick, put the rom on that usb and connect it to your phone and then try to flash it (if your using twrp you have an option to choose from wich storage you want to use)
Also a piece of advice, when flashing roms, kernels etc please have your phone charged above 50% (just in case).
Sent from my HUAWEI P7-L10 using XDA Free mobile app
---------- Post added at 09:28 PM ---------- Previous post was at 09:27 PM ----------
its the peanut said:
Try re download the zip (or try an other rom)maybe you just got an false download. i also had some trouble with my m7 back in the day.
But in your case now you are stuck with no os or bootloop, i give you as advice to follow an soft unbrick method it worked for me, or if you have an usb otg cable and usb or and usb otg thumbstick, put the rom on that usb and connect it to your phone and then try to flash it (if your using twrp you have an option to choose from wich storage you want to use)
Also a piece of advice, when flashing roms, kernels etc please have your phone charged above 50% (just in case).
Sent from my HUAWEI P7-L10 using XDA Free mobile app
Click to expand...
Click to collapse
Also make sure you downloaded the rom made for your phone model!
Sent from my HUAWEI P7-L10 using XDA Free mobile app
Burky1996 said:
I really messed my phone up its got no OS and its stuck in bootloop iv tried pushing cm-12 onto it and installing it but i keep getting error codes with what you see in the picture. can anyone help.
Click to expand...
Click to collapse
Can you please post the output of
Code:
fastboot getvar all
please remove your imei and serial number.
Depending on which variant of the M7 you have you probably just need a different version of recovery to install a CM rom. I think they prefer TWRP 2.7.x.x. Post the getvar and we can see what you have. then I can give you a better informed instruction. :good:
P.s also check the md5 of the rom zip you downloaded. Use this tool www.winmd5.com the correct md5 should be listed with the link you downloaded the rom from
failed to mount /dev/block/blah blah blah = needs "block:by-name" support which twrp 2.6.3.3 doesn't have
everything explained here
So update your recovery
and do what danny said above so he can confirm you have the right rom/recovery for your device.
Burky1996 said:
I really messed my phone up its got no OS and its stuck in bootloop iv tried pushing cm-12 onto it and installing it but i keep getting error codes with what you see in the picture. can anyone help.
Click to expand...
Click to collapse
Your getvar looks fine this rom should work fine with your device. Download this version of TWRP https://www.androidfilehost.com/?fid=23501681358561860 (2.7.1.2). dropthe file in your fastboot folder and flash it with fastboot.
Code:
fastboot flash recovery "name-of-recovery".img
fastboot erase cache
fastboot reboot-bootloader
Once thats done reflash the rom with the new version of TWRP. It should flash just fine :good:
iv managed to flash cm12.1 now, thanks guys, is there anyway i could get the HTC software back on.
Burky1996 said:
iv managed to flash cm12.1 now, thanks guys, is there anyway i could get the HTC software back on.
Click to expand...
Click to collapse
There are a number of ways to return to stock software. You can simply flash a stock rom through twrp or use a stock nandroid. look for rom that match your version main. 7.19.401.22
I think there is even an lollipop 7.19.401.22 RUU for your device but I'm not sure if it will work with s-on though because it's a zip but it certainly wouldnt hurt to try it though. You will need to relock your bootloader and flash it with fastboot.
I'll edit this post with links when I find them unless some one beats me to it
Hey Dan do you think we could skype and you could talk me through it, it would be much easier?
Burky1996 said:
Hey Dan do you think we could skype and you could talk me through it, it would be much easier?
Click to expand...
Click to collapse
Sorry I am at work so availability is scetchy. I found the ruu but it's for the older 7.19.401.2 lollipop, this won't work for you because your s-on. Downgrading firmware is only possible with s-off.
You can use this stock rom though http://forum.xda-developers.com/htc-one/development/rom-100-pure-stock-5-0-2-7-19-401-2-t3044041 just flash it with twrp. The thread recommends TWRP 2.8.5.X no need to relock the bootloader or anything silly, just flash it like any other rom :good:
You'll notice that this rom is also for the older 7.19.401.2 so you will need to install the last OTA update to bring your rom in line with your firmware. Flash this recovery with the same method as twrp. (Stock recovery required for installing the OTA) http://sourceforge.net/projects/htcone/files/Recovery/STOCK/7.19.401.2_recovery.img/download reboot then just go to Settings>About>Check for updates.
Danny201281 said:
Sorry I am at work so availability is scetchy. I found the ruu but it's for the older 7.19.401.2 lollipop, this won't work for you because your s-on. Downgrading firmware is only possible with s-off.
You can use this stock rom though http://forum.xda-developers.com/htc-one/development/rom-100-pure-stock-5-0-2-7-19-401-2-t3044041 just flash it with twrp. The thread recommends TWRP 2.8.5.X no need to relock the bootloader or anything silly, just flash it like any other rom :good:
You'll notice that this rom is also for the older 7.19.401.2 so you will need to install the last OTA update to bring your rom in line with your firmware. Flash this recovery with the same method as twrp. (Stock recovery required for installing the OTA) http://sourceforge.net/projects/htcone/files/Recovery/STOCK/7.19.401.2_recovery.img/download reboot then just go to Settings>About>Check for updates.
Click to expand...
Click to collapse
i did what you said when i applied the system update my phone turned on booted to a white screen with the green htc logo then it turned off the battery symbol came up its like its turned off. i tryed to lock the boot loader to see if it would work then but it never, when i appy the update it dosent even boot into the recovery.
i did what you said when i applied the system update my phone turned on booted to a white screen with the green htc logo then it turned off the battery symbol came up its like its turned off. i tryed to lock the boot loader to see if it would work then but it never, when i appy the update it dosent even boot into the recovery.
Burky1996 said:
i did what you said when i applied the system update my phone turned on booted to a white screen with the green htc logo then it turned off the battery symbol came up its like its turned off. i tryed to lock the boot loader to see if it would work then but it never, when i appy the update it dosent even boot into the recovery.
Click to expand...
Click to collapse
Okay try this. Download the OTA but select the option "Install Later" connect your m7 to your pc and browse your storage. In the download folder on your phone you should find the OTA in zip format. Copy it to your pc.
Now open the OTA zip on your pc. Inside you'll find another zip called "firmware.zip" extract it then open it. Inside you'll find a recovery.img. extract the recovery file and flash it with fastboot. Now reboot to android and continue to install the OTA. :fingers-crossed:
Sent from my SM-T230 using Tapatalk
im going to have to unlock the boot loader again and then do it
Burky1996 said:
im going to have to unlock the boot loader again and then do it
Click to expand...
Click to collapse
Yes you will need to unlock the bootloader to flash the recovery, Dont forget to fastboot erase cache after flashing the recovery that is cruicial. You don't need to be relocked to install the OTA though.
When you select install now, the device should reboot to the Stock Recovery. At first the screen will just be black for a short while. Then you'll see an image of a phone with a Green ring and download arrow. If you hold Volume up and press the power button you will see the Stock Recovery and its progress in installing the OTA.
I'm not sure why your device was hanging on boot after installing the OTA. Maybe a bad recovery.img. that's why I say to get the recovery from the OTA file.
its still not working so i mite just install twrp and restore to cm12.1
Burky1996 said:
im going to have to unlock the boot loader again and then do it
Click to expand...
Click to collapse
Yes you will need to unlock the bootloader to flash the recovery, Dont forget to fastboot erase cache after flashing the recovery that is cruicial. You don't need to be relocked to install the OTA though.
When you select install now, the device should reboot to the Stock Recovery. At first the screen will just be black for a short while. Then you'll see an image of a phone with a Green ring and download arrow. If you hold Volume up and press the power button you will see the Stock Recovery and its progress in installing the OTA.
I'm not sure why your device was hanging on boot after installing the OTA. Maybe a bad recovery.img. that's why I say to get the recovery from the OTA file.
Danny201281 said:
Sorry I am at work so availability is scetchy. I found the ruu but it's for the older 7.19.401.2 lollipop, this won't work for you because your s-on. Downgrading firmware is only possible with s-off.
You can use this stock rom though http://forum.xda-developers.com/htc-one/development/rom-100-pure-stock-5-0-2-7-19-401-2-t3044041 just flash it with twrp. The thread recommends TWRP 2.8.5.X no need to relock the bootloader or anything silly, just flash it like any other rom :good:
You'll notice that this rom is also for the older 7.19.401.2 so you will need to install the last OTA update to bring your rom in line with your firmware. Flash this recovery with the same method as twrp. (Stock recovery required for installing the OTA) http://sourceforge.net/projects/htcone/files/Recovery/STOCK/7.19.401.2_recovery.img/download reboot then just go to Settings>About>Check for updates.
Click to expand...
Click to collapse
could it be not working coz my hboot has changed to 1.51.
Burky1996 said:
could it be not working coz my hboot has changed to 1.51.
Click to expand...
Click to collapse
Your still stuck with this? Try starting the process over, but do not relock your bootloader at any point.
Wipe system data and cache partitions with TWRP Advanced wipe
Flash the Rom with twrp as a clean install.
Reboot and download the OTA. Choose install later, then copy the OTA to your pc. Extract the Stock Recovery and flash it with fastboot. Reboot and install the OTA.
But do not relock your boot loader. Because when you unlock the bootloader, it wipes the device including the data/preload folder. If the preload folder is not intact the OTA will fail
Sent from my M7 Running ARHD 92.x
Unlocked
S-Off
Cid spcs-001
Hboot 3.19
Radio 1.09
Open dsp v 51.2.2
Os 6.20.651.3
I've run the firmware twice, but it boots into a boot loop in between installs. I've tried multiple versions of the new stock Rom. Only non-hk of course. Currently trying the download straight from HTC.
Any ideas?
Please, I'm desperate.
Sounds like you flashed the Full Firmware if you have a backup you should be able to restore it without any problem or you could run the latest RUU and start fresh.
Sloth said:
Sounds like you flashed the Full Firmware if you have a backup you should be able to restore it without any problem or you could run the latest RUU and start fresh.
Click to expand...
Click to collapse
I cannot get twrp back on it. I've tried to run adb devices and cannot see anything. I originally posted ROM, but I've actually been trying to install the RUU by renaming it and putting it on my sd. It looks like is installing it, then says press power to reboot. I do, and I get back to the boot loop from bad boyz Rom
TWRP is installed from fastboot/bootloader so you would type fastboot devices
Timeline:
Had Bad Boyz rom, wanted marshmallow
Unroot, back to stock ruu
Updated to marshmallow
Updated all apps and then wanted root back
Installed twrp. All good at this point
Installed supersu, got boot loop
Had bad boyz backup, twrp installed this backup
All working today, but wanted to get back to marshmallow
Tried to sd install ruu, and now I'm here.
I know I should've backed up when I first installed twrp, but sometimes I'm confident that I know what I'm doing, and this happens...
I would suggest running the RUU from your PC it is an .exe file as far as I know so renaming it most likely won't work.
Sloth said:
TWRP is installed from fastboot/bootloader so you would type fastboot devices
Click to expand...
Click to collapse
I'm such a jackass. You're freaking awesome!
Now that I have twrp back on my machine, do you have any suggestions as to how I might go about getting marshmallow on it? I can't seem to make any of the RUUs install properly on top of this ROM.
I may have just answered my own question. I have to unroot again, don't I?
You could copy a MM rom to your phone and flash it from twrp
Sloth said:
I would suggest running the RUU from your PC it is an .exe file as far as I know so renaming it most likely won't work.
Click to expand...
Click to collapse
Cool, I'll try it that way. At least I know now that I can twrp the bad boyz if I can't make it work. Thank you! I'll let you know how it goes.
I have run the original RUU by formatting my sd in fat32 and renaming the RUU 0P6BIMG.ZIP many times, but I'm assuming that the new one won't run that way.
CableGuy77 said:
Cool, I'll try it that way. At least I know now that I can twrp the bad boyz if I can't make it work. Thank you! I'll let you know how it goes.
I have run the original RUU by formatting my sd in fat32 and renaming the RUU 0P6BIMG.ZIP many times, but I'm assuming that the new one won't run that way.
Click to expand...
Click to collapse
I don't think you can rename an .exe file as a .zip
Edit:
You should be able to run this one from your ext sdcard
https://www.androidfilehost.com/?fid=24391638059059322
0P6BIMG_Sprint_HTC_One_M8_6.20.651.3_RUU.zip (get rid of everything after 0P6BIMG and you should be golden)
Make sure you install the latest version of SU, also, otherwise you'll boot loop. Obviously if you end up flashing a rooted ROM like Bad Boyz there is no reason to install SU.