I seem to have soft bricked my m9 hima while trying to go back to stock in order to update the firmware to the latest rev. (Yes, I have read the other threads, but I Think this might be a little more unique to my situation? )
I cannot get into my stock recovery, or my TWRP(which is what I used before).
Download mode appears to work.
I can't install TWRP with fastboot/adb, might be because device is S-on.
Tried running RUU, but says my device isn't compatible.
I would really appreciate anyones' input!
Nanometer45 said:
I seem to have soft bricked my m9 hima while trying to go back to stock in order to update the firmware to the latest rev. (Yes, I have read the other threads, but I Think this might be a little more unique to my situation? )
I cannot get into my stock recovery, or my TWRP(which is what I used before).
Download mode appears to work.
I can't install TWRP with fastboot/adb, might be because device is S-on.
Tried running RUU, but says my device isn't compatible.
I would really appreciate anyones' input!
Click to expand...
Click to collapse
Useful information that will help us help you:
CID (Carrier ID)
MID (Model ID)
Firmware version that you're currently on
Steps you took that led to your current situation
Like you said, this is a soft brick. Odds are good we can help.
---------- Post added at 04:39 PM ---------- Previous post was at 04:32 PM ----------
If you're new to ADB & fastboot, check out this thread
Once you've installed those:
- plug your phone into your computer while it is in download mode
- open a command prompt
- run the command "fastboot getvar all"
Phone is:
MID 0PJA11000
CID CWS__001
Firmware I tried to flash was this:
RUU_HIMA_UL_L51_SENSE70_ATT_MR_Cingular_US_2.11.502.18
It looks like the firmware update failed, but when the RUU program tries to read the firmware it now shows as the new one listed above.
I got to this point by trying to update the firmware. I had problems getting the new TWRP working, and I got impatient :-\
Make sure you double check the md5 hash and filesize of twrp before you flash it.
Sent from my HTC One M9 using Tapatalk
I tried flashing TWRP, and it seems to have taken it, but phone says it cannot boot intothe boot loader, it said that before I started running into soft brick issues i believe.
Try my copy https://drive.google.com/folderview?id=0B4vTiHTBB629QmxGTkpyZWlCR28
Sent from my HTC One M9 using Tapatalk
Which do you recommend, your twrp?
I know mine works..
Sent from my HTC One M9 using Tapatalk
Can't get it to flash:
C:\Program Files (x86)\ClockworkMod\Universal Adb Driver>fastboot flash recovery T1F.img
target reported max download size of 800000000 bytes
sending 'recovery' (30912 KB)...
OKAY [ 2.444s]
writing 'recovery'...
(bootloader) HOSD CL#591203
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 2.651s]
finished. total time: 5.096s
Says:
Failed to boot to recovery mode
Flash the twrp 2.9.0.1 in the link i gave. See what that does.
Sent from my HTC One M9 using Tapatalk
Nanometer45 said:
Can't get it to flash:
C:\Program Files (x86)\ClockworkMod\Universal Adb Driver>fastboot flash recovery T1F.img
target reported max download size of 800000000 bytes
sending 'recovery' (30912 KB)...
OKAY [ 2.444s]
writing 'recovery'...
(bootloader) HOSD CL#591203
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 2.651s]
finished. total time: 5.096s
Says:
Failed to boot to recovery mode
Click to expand...
Click to collapse
I'm pretty sure 2.9.x and later versions only work on MM, and you're on LP firmware. Try one of the 2.8.x versions from here: https://dl.twrp.me/hima/
Doesn't boot into TWRP. Maybe S-off is a problem.
Missed your post, I'll try an older build. Though I was running Cyanogenmod 13, so I don't see how that invited the problem. Doesn't hurt to try.
Older TWRP worked. Now I just need to get the latest firmware on it without android installed. Any tips?
Was able to finally get the RUU to take. Thanks for helping out. Is there no MM update for the ATT M9? That would explain some of the issues I was having. Only custom roms for options then.
Related
Hello everyone, I started to play around with all the diff things you can do with a rooted phone had plans for getting a custom ROM for my phone. Let me stat by saying that I am very new to all this.
I day ago i was getting ready to install the custom ROM for viper (ViperOneM8_1.7.1) reason being is coming from a htc one m7 with sense i wanted to get back to sense from my stock GPe m8.
I was able to unlock my bootloader and get my phone rooted I fallowed this video (How to Root your HTC One M8 - Full Guide) From Sakitech... or least I think im rooted still... I'll come back to you as to why I say "I think I'm rooted".
I thought it would be very simple just fire up the custom recovery and flash the ROM and sit back while it flashed, well everything went down hill from this point. Let me tell you what i did.
First i got to the custom recovery and I did a wipe I did advanced wipe and checked the boxes this is where I think I deleted the OS(after this I could not get back on the phone to do anything only will boot to recovery and it say no OS installed then asks if I want to get SuperSU installed this is where I already thought I was rooted but maybe on not??? I'm very confused about that
Then I used the sideload method to push the rom zip and try to flash the rom at this point I cant get it to flash. First I was getting the MD5 error I checked that off now it will just fail either saying error executing the binary from the zip or that zip is corrupted. (I tried re-downloading the ROM even from mirror link)
At this point I am very frustrated and feel helpless. I tried my best to keep from posting this and try to research to see if i can find the solution myself but I'm having no luck I have my days off from work to get my phone up and running or ill just have to go but another phone. At this point I really need some help. All I want is a working phone if i can get back to GPe stock that would be fine or make the ViperOne work.
Attempts to solve my problem: I tried flashing GPE4.4.3_m8.zip and other stock GPe ROMs nothing works
Thanks for reading and all your help I will sit nest to my comp and answer anything to try make everything as clear as possible. Thank you again
So I tried ViperOne again and it was starting to install but then fails. I searched around and I found that i need to have s-off to be able to install the ROM.
Can I get s-off from the recovery or bootloader/fastboot?
Demonwarrior said:
So I tried ViperOne again and it was starting to install but then fails. I searched around and I found that i need to have s-off to be able to install the ROM.
Can I get s-off from the recovery or bootloader/fastboot?
Click to expand...
Click to collapse
no offense, buy you need to read before you continue anything else.
rbouza1 said:
no offense, buy you need to read before you continue anything else.
Click to expand...
Click to collapse
None taken, I appreciate the reply and I will continue to do more research. Do you have any info I could use?
Demonwarrior said:
None taken, I appreciate the reply and I will continue to do more research. Do you have any info I could use?
Click to expand...
Click to collapse
Try this :
Do a full wipe in the recovery, install viper rom but do not choose to do a full wipe in the aroma installer. Once finished you flash the boot.img via fastboot and then reboot the phone.
You do not need s-off to flash custom roms. But the GPE thingy can be the problem....
Mr Hofs said:
Try this :
Do a full wipe in the recovery, install viper rom but do not choose to do a full wipe in the aroma installer. Once finished you flash the boot.img via fastboot and then reboot the phone.
You do not need s-off to flash custom roms. But the GPE thingy can be the problem....
Click to expand...
Click to collapse
I got the boot img from the ViperOne zip and ran the rom through sideload. what command do i run to flash the boot.img?
Code:
fastboot flash boot.img
?
also the ViperOne install failed said status 7 and some synlinks failed
Demonwarrior said:
I got the boot img from the ViperOne zip and ran the rom through sideload. what command do i run to flash the boot.img?
Code:
fastboot flash boot.img
?
also the ViperOne install failed said status 7 and some synlinks failed
Click to expand...
Click to collapse
fastboot flash img boot.img
---------- Post added at 06:28 PM ---------- Previous post was at 06:25 PM ----------
try that command, and what model did you have originally and did you convert to gpe or flash a gpe ROM.
gave me an error
Code:
FAILED (remote: signature verify fail)
Its a stock Google play edition I bought from the Google paly store, I didnt flash any other rom the ViperOne rom was going to be the first flash on the phone
Do you have an SD reader on your laptop? You can buy a big SD that you can put a small SD card inside it, then put the ROM zip file inside the SD card, after that plug it in your M8 and flash it via twrp.
Let me know if you couldn't understand any point cuz my English is not that good.
iHagbani said:
Do you have an SD reader on your laptop? You can buy a big SD that you can put a small SD card inside it, then put the ROM zip file inside the SD card, after that plug it in your M8 and flash it via twrp.
Let me know if you couldn't understand any point cuz my English is not that good.
Click to expand...
Click to collapse
I know how to push the rom trough adb to flash it thats not the problem the problem is that i cant get it to install properly. Thanks for the reply though i appreciate it.
Demonwarrior said:
I got the boot img from the ViperOne zip and ran the rom through sideload. what command do i run to flash the boot.img?
Code:
fastboot flash boot.img
?
also the ViperOne install failed said status 7 and some synlinks failed
Click to expand...
Click to collapse
Correct command is fastboot flash boot boot.img
status 7 means you don't have right recovery for that ROM
Also search about Stock GPE partition layout, is it same as normal non-GPE. I doubt it as I seen somewhere about people do full conversion to GPE, they need to reflash firmware to correct the partition for Sense ROM. This is what I understand from this thread : http://forum.xda-developers.com/showthread.php?t=2708589
ckpv5 said:
Correct command is fastboot flash boot boot.img
status 7 means you don't have right recovery for that ROM
Also search about Stock GPE partition layout, is it same as normal non-GPE. I doubt it as I seen somewhere about people do full conversion to GPE, they need to reflash firmware to correct the partition for Sense ROM. This is what I understand from this thread : http://forum.xda-developers.com/showthread.php?t=2708589
Click to expand...
Click to collapse
I have researched about the partition layout and I think you are right. How do i get the right partition layout? this is all a learning experience for me lol. I just hope i can get my phone working again.
In thats case then i might be worse off then i though my phone is s-on an there is no way for me to get it s-off in its current bricked state... to the the Ruu to install
correct me if im wrong but then what i have to do is just flash the stock rom for gpe beacuse since my phone was already stock GPe the the frieware(partition layout) will apcct it... right?
I want to thank everyone at the this point it looks like i have a lot of learning to do. Thank you
Demonwarrior said:
I know how to push the rom trough adb to flash it thats not the problem the problem is that i cant get it to install properly. Thanks for the reply though i appreciate it.
Click to expand...
Click to collapse
I know, but I told you this way in case that the adb didn't flash the whole zip file!
Demonwarrior said:
I have researched about the partition layout and I think you are right. How do i get the right partition layout? this is all a learning experience for me lol. I just hope i can get my phone working again.
In thats case then i might be worse off then i though my phone is s-on an there is no way for me to get it s-off in its current bricked state... to the the Ruu to install
correct me if im wrong but then what i have to do is just flash the stock rom for gpe beacuse since my phone was already stock GPe the the frieware(partition layout) will apcct it... right?
I want to thank everyone at the this point it looks like i have a lot of learning to do. Thank you
Click to expand...
Click to collapse
Follow the link in the post you quoted:
http://forum.xda-developers.com/showthread.php?t=2708589
You should really read carefully before doing stuff with your phone, especially when you are unexperienced.
If you are unsure about anything, ask before you try messing with something and hope that it will work.
You didnt, and now you have the mess.
But now even now you are not able to follow the instructions people are giving you.
In the post you just quoted there are instructions how to go from GPE to Sense and also back (#1 and #2 post)
j to the 4n said:
Follow the link in the post you quoted:
http://forum.xda-developers.com/showthread.php?t=2708589
You should really read carefully before doing stuff with your phone, especially when you are unexperienced.
If you are unsure about anything, ask before you try messing with something and hope that it will work.
You didnt, and now you have the mess.
But now even now you are not able to follow the instructions people are giving you.
In the post you just quoted there are instructions how to go from GPE to Sense and also back (#1 and #2 post)
Click to expand...
Click to collapse
I tried the instruction on the thread it didnt work... I think its because i have s-on
Code:
C:\Users\owner\Desktop\htc one\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.058s]
finished. total time: 0.061s
C:\Users\owner\Desktop\htc one\platform-tools>fastboot flash zip RUU-HTC_One_M8_
GPE_4.4.4-2.12.1700.1_rooted.zip
target reported max download size of 1830617088 bytes
sending 'zip' (569179 KB)...
OKAY [ 19.483s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 19.846s
C:\Users\owner\Desktop\htc one\platform-tools>fastboot flash zip RUU-HTC_One_M8_
GPE_4.4.4-2.12.1700.1_rooted.zip
target reported max download size of 1830617088 bytes
sending 'zip' (569179 KB)...
OKAY [ 19.484s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 19.665s
C:\Users\owner\Desktop\htc one\platform-tools>fastboot flash zip RUU-HTC_One_M8_
GPE_4.4.4-2.12.1700.1_rooted.zip
target reported max download size of 1830617088 bytes
sending 'zip' (569179 KB)...
OKAY [ 19.479s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 19.662s
C:\Users\owner\Desktop\htc one\platform-tools>fastboot flash zip RUU-HTC_One_M8_
GPE_4.4.4-2.12.1700.1_rooted.zip
target reported max download size of 1830617088 bytes
sending 'zip' (569179 KB)...
OKAY [ 19.478s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 19.661s
C:\Users\owner\Desktop\htc one\platform-tools>fastboot flash zip RUU-HTC_One_M8_
GPE_4.4.4-2.12.1700.1_rooted.zip
target reported max download size of 1830617088 bytes
sending 'zip' (569179 KB)...
OKAY [ 19.458s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 19.641s
C:\Users\owner\Desktop\htc one\platform-tools>
C:\Users\owner\Desktop\htc one\platform-tools>fastboot flash zip RUU-HTC_One_M8_
GPE_4.4.4-2.12.1700.1_rooted.zip
target reported max download size of 1830617088 bytes
sending 'zip' (569179 KB)...
OKAY [ 19.470s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 19.650s
C:\Users\owner\Desktop\htc one\platform-tools>
The post says to try it a few times but still giving me the say error
I've read around on the forums here and other places but some of it doesn't make any sense to me and I watched a YouTube video about unlocking the bootloader then rooting the phone unfortunately i didn't do a nandroid back up before rooting (using supersu) and i am wondering if it is possible to flash to a stock rom so that in the future i can ota update in the future.
here is what i have at the moment
international phone (im on o2 in the uk anyway)
android version: 5.0.2
Software number: 1.32.401.15
unlocked bootloader
rooted
s-off
SuperCID
Also if someone can guide me through this i would be extremely thankful.
Thanks for your help guys.
You would need to either get a nandroid of your particular carriers ROM, or download the correct RUU from HTC.
BillTheCat said:
You would need to either get a nandroid of your particular carriers ROM, or download the correct RUU from HTC.
Click to expand...
Click to collapse
as far as i know there are these 2 RUUs which are the same version as mine
androidruu.com/getdownload.php?file=M9/0PJAIMG_HIMA_UHL_L50_SENSE70_HTC_Europe_1.32.401.15_R1_Radio_01.01_U11440261_56.02.50306G_2_F_release_426891_signed.zip
androidfilehost.com/?fid=96039337900114679
are these fine to flash to my device?
linton85 said:
as far as i know there are these 2 RUUs which are the same version as mine
androidruu.com/getdownload.php?file=M9/0PJAIMG_HIMA_UHL_L50_SENSE70_HTC_Europe_1.32.401.15_R1_Radio_01.01_U11440261_56.02.50306G_2_F_release_426891_signed.zip
androidfilehost.com/?fid=96039337900114679
are these fine to flash to my device?
Click to expand...
Click to collapse
I have no idea, since you haven't told us what version your phone is. I think you ought to wait for feedback from someone else who can advise you better.
linton85 said:
as far as i know there are these 2 RUUs which are the same version as mine
androidruu.com/getdownload.php?file=M9/0PJAIMG_HIMA_UHL_L50_SENSE70_HTC_Europe_1.32.401.15_R1_Radio_01.01_U11440261_56.02.50306G_2_F_release_426891_signed.zip
androidfilehost.com/?fid=96039337900114679
are these fine to flash to my device?
Click to expand...
Click to collapse
Yes your s-off you can use those RUU
hmm i cant seem to use them, i go to flash it then i get this;
Code:
C:\Users\Jack\Desktop\HTC ROOT + UNLOCK\platform-tools>fastboot oem rebootRUU
...
OKAY [ 0.020s]
finished. total time: 0.021s
C:\Users\Jack\Desktop\HTC ROOT + UNLOCK\platform-tools>fastboot flash zip 0PJAIM
G.zip
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
sending sparse 'zip' (88044 KB)...
OKAY [ 6.331s]
writing 'zip'...
(bootloader) HOSD CL#506785
(bootloader) ERR [SD_UPDATE_ERR] update_fb_ZIP_buf: can not find ZIP hea
(bootloader) der
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 22
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 22
(bootloader) [email protected]
FAILED (remote: 22: fail to flash via downloadzip)
finished. total time: 8.430s
any idea?
linton85 said:
hmm i cant seem to use them, i go to flash it then i get this;
Code:
C:\Users\Jack\Desktop\HTC ROOT + UNLOCK\platform-tools>fastboot oem rebootRUU
...
OKAY [ 0.020s]
finished. total time: 0.021s
C:\Users\Jack\Desktop\HTC ROOT + UNLOCK\platform-tools>fastboot flash zip 0PJAIM
G.zip
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
sending sparse 'zip' (88044 KB)...
OKAY [ 6.331s]
writing 'zip'...
(bootloader) HOSD CL#506785
(bootloader) ERR [SD_UPDATE_ERR] update_fb_ZIP_buf: can not find ZIP hea
(bootloader) der
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 22
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 22
(bootloader) [email protected]
FAILED (remote: 22: fail to flash via downloadzip)
finished. total time: 8.430s
any idea?
Click to expand...
Click to collapse
your using the wrong fastboot
you need htc_fastboot >> https://www.androidfilehost.com/?fid=96039337900114016
it's also easy to rename the RUU.zip to 0PJAIMG.ZIP, place it on a ext sd card formatted in FAT32 (a 16 or 32gig one should work), reboot into DOWNLOAD_MODE, agree and it should flash.
it's also easy to rename the RUU.zip to 0PJAIMG.ZIP, place it on a ext sd card formatted in FAT32 (a 16 or 32gig one should work), reboot into DOWNLOAD_MODE, agree and it should flash.
Click to expand...
Click to collapse
ok managed to flash it back successfully couple of things though:
i couldnt copy the file when it was named 0JAIMPG.ZIP to the sd card (was in the phone not sure if i had to take it out and put it on)
it still says "software status modified" "unlocked" "s-off" afaik you can't get software status back to normal, to get unlocked back to locked would mean me relocking the bootloader and s-off shouldnt matter with ota update?
if i was to now re-install twrp but before rooting i took a nandroid backup would this allow me to get ota updates if i then restore to that after rooting or would one of the things above prevent me?
if not is there anyway i can get ota updates again?
linton85 said:
ok managed to flash it back successfully couple of things though:
i couldnt copy the file when it was named 0JAIMPG.ZIP to the sd card (was in the phone not sure if i had to take it out and put it on)
it still says "software status modified" "unlocked" "s-off" afaik you can't get software status back to normal, to get unlocked back to locked would mean me relocking the bootloader and s-off shouldnt matter with ota update?
if i was to now re-install twrp but before rooting i took a nandroid backup would this allow me to get ota updates if i then restore to that after rooting or would one of the things above prevent me?
if not is there anyway i can get ota updates again?
Click to expand...
Click to collapse
If you used the htc_fastboot to flash it will not reset the modified tag
you have to do it yourself >> http://forum.xda-developers.com/one-m9/general/how-to-restore-software-status-original-t3092882
To set unlocked to locked you have to do this >> http://forum.xda-developers.com/one-m9/general/how-to-lock-unlock-bootloader-htcdevs-t3092036
and yes, you can get OTA update with unlocked and s-off
Thank you so much for taking the time to help me out and providing links I am very grateful
clsA said:
your using the wrong fastboot
you need htc_fastboot >> https://www.androidfilehost.com/?fid=96039337900114016
it's also easy to rename the RUU.zip to 0PJAIMG.ZIP, place it on a ext sd card formatted in FAT32 (a 16 or 32gig one should work), reboot into DOWNLOAD_MODE, agree and it should flash.
Click to expand...
Click to collapse
Do I rename this file to fastboot.exe and delete the original fastboot?
I seem to always get the 90 pre-update FAIL when I flash different firmware.
bigp951 said:
Do I rename this file to fastboot.exe and delete the original fastboot?
I seem to always get the 90 pre-update FAIL when I flash different firmware.
Click to expand...
Click to collapse
Just leave it as htc_fastboot. They can coexist.
Dude, what's it tell you after you get the error 90? Flash again immediately, right? EVERYONE gets error 90 when flashing firmware. It's a pre-check before actually doing anything. If you're phone reboots to OS after getting 90, then just leave your command/terminal window open and put your phone back in download mode and re-run the exact same command to start the flash again.
jollywhitefoot said:
Just leave it as htc_fastboot. They can coexist.
Dude, what's it tell you after you get the error 90? Flash again immediately, right? EVERYONE gets error 90 when flashing firmware. It's a pre-check before actually doing anything. If you're phone reboots to OS after getting 90, then just leave your command/terminal window open and put your phone back in download mode and re-run the exact same command to start the flash again.
Click to expand...
Click to collapse
That's what I have been doing.... Did not know EVERYONE gets that error. Thanks for the info though. From what I read elsewhere is that the htc_fastboot will reboot back into download mode instead of os. That's why I mentioned it.
bigp951 said:
That's what I have been doing.... Did not know EVERYONE gets that error. Thanks for the info though. From what I read elsewhere is that the htc_fastboot will reboot back into download mode instead of os. That's why I mentioned it.
Click to expand...
Click to collapse
No problem bro. I think I've gotten reboots to is using HTC_fastboot, too.
clsA said:
your using the wrong fastboot
you need htc_fastboot >> https://www.androidfilehost.com/?fid=96039337900114016
it's also easy to rename the RUU.zip to 0PJAIMG.ZIP, place it on a ext sd card formatted in FAT32 (a 16 or 32gig one should work), reboot into DOWNLOAD_MODE, agree and it should flash.
Click to expand...
Click to collapse
Sir After installing 5.1 update my phone got stuck at boot screen.
Now I am unable to boot into recovery. Also locked My bootloader accidentally. While trying to flash a zip through fastboot I am getting below error. Could you please help me out.
OTA_HIMA_UHL_L50_SENSE70_hTC_Asia_HK_1.40.708.9-1.32.708.15_R1_release_436199
amit_coolcampus said:
Sir After installing 5.1 update my phone got stuck at boot screen.
Now I am unable to boot into recovery. Also locked My bootloader accidentally. While trying to flash a zip through fastboot I am getting below error. Could you please help me out.
OTA_HIMA_UHL_L50_SENSE70_hTC_Asia_HK_1.40.708.9-1.32.708.15_R1_release_436199
Click to expand...
Click to collapse
I'm sorry to tell you but if you updated to 5.1 and did not go into developer options and check to allow bootloader unlock, and then locked your bootloader theirs is nothing you can do but flash a RUU. Are you s-off ? If no your most likely stuck.
I have no idea what the file name you posted above is for... Edit: This may be the help you need >> https://www.androidfilehost.com/?fid=24052804347810886
Sir I am S-On. I am trying to flash a RUU but getting error everytime. Tried from SD card. tried via fastboot.
Also my M9 is HTC Asia (Hongkong). So I have tried flashing below one. Can I try flashing TW version given by you??
https://www.androidfilehost.com/?fid=24269982087001508
clsA said:
I'm sorry to tell you but if you updated to 5.1 and did not go into developer options and check to allow bootloader unlock, and then locked your bootloader theirs is nothing you can do but flash a RUU. Are you s-off ? If no your most likely stuck.
I have no idea what the file name you posted above is for... Edit: This may be the help you need >> https://www.androidfilehost.com/?fid=24052804347810886
Click to expand...
Click to collapse
amit_coolcampus said:
Sir I am S-On. I am trying to flash a RUU but getting error everytime. Tried from SD card. tried via fastboot.
Also my M9 is HTC Asia (Hongkong). So I have tried flashing below one. Can I try flashing TW version given by you??
https://www.androidfilehost.com/?fid=24269982087001508
Click to expand...
Click to collapse
With S-ON it's not possible to downgrade or to flash RUUs that were made for other SKUs (Taiwan is 709 and Hongkong is 708). Since you can't use the RUU in my AFH folder because it's older than your actual firmware and there is no other RUU for the SKU 708 (or at least none I know) than that one you linked your only hope might be the RUU service on llabtoofer's website.
Edit @clsA: That file amit_coolcampus mentioned earlier is one of the OTAs for the Hongkong version of the M9.
Flippy498 said:
With S-ON it's not possible to downgrade or to flash RUUs that were made for other SKUs (Taiwan is 709 and Hongkong is 708). Since you can't use the RUU in my AFH folder because it's older than your actual firmware and there is no other RUU for the SKU 708 (or at least none I know) than that one you linked your only hope might be the RUU service on llabtoofer's website.
Edit @clsA: That file amit_coolcampus mentioned earlier is one of the OTAs for the Hongkong version of the M9.
Click to expand...
Click to collapse
Thanks Sir. Can I get this repaired if i visit HTC service center? Will they be having 2.11.708.30 RUU?
amit_coolcampus said:
Thanks Sir. Can I get this repaired if i visit HTC service center? Will they be having 2.11.708.30 RUU?
Click to expand...
Click to collapse
Honestly, I don't know. I've always been able to recover my phones without the help of the HTC service center or the RUU service. My guess is that the RUU service might be cheaper but that's only a guess. Maybe someone else here had to use one or both of these services and can share his/her experience...
Hi all, long term lurker first time poster so please go easy on me.
After having many successes on rooting and flashing various device over the years thanks to this forum, I have finally completely knackered my M8 I think.
Awhile ago I rooted and flashed Venom Rom which worked perfectly. I then decided I wanted Revolution HD rom but obviously didn't follow the guide correctly as afterwards I couldn't get wifi. I still used the phone for a few months until yesterday when I finally decided to do something about it. So using Minimal ADB Fastboot I flashed a Lollipop firmware and was going to flash another ROM.
However, the phone won't boot into recovery, just the bootloader. Can anyone please tell me (in simple terms ) where I can go from here or whether I now have a brick?
If it helps the phone is "Relocked" and S-ON.
pastyal said:
Hi all, long term lurker first time poster so please go easy on me.
After having many successes on rooting and flashing various device over the years thanks to this forum, I have finally completely knackered my M8 I think.
Awhile ago I rooted and flashed Venom Rom which worked perfectly. I then decided I wanted Revolution HD rom but obviously didn't follow the guide correctly as afterwards I couldn't get wifi. I still used the phone for a few months until yesterday when I finally decided to do something about it. So using Minimal ADB Fastboot I flashed a Lollipop firmware and was going to flash another ROM.
However, the phone won't boot into recovery, just the bootloader. Can anyone please tell me (in simple terms ) where I can go from here or whether I now have a brick?
If it helps the phone is "Relocked" and S-ON.
Click to expand...
Click to collapse
post your fastboot getvar all please without imei and serial number
did the firmware flash complete successfully ?
---------- Post added at 10:40 AM ---------- Previous post was at 10:34 AM ----------
also forgot to add, if the firmware flash went through fine then you will now have stock recovery on your phone, this will just look like a big red exclamation mark on your phone.
at this point you either need to find a stock RUU for your phone and run it now or unlocked your bootloader again at HTC dev, flash a custom recovery and then flash a custom rom.
if you have anything custom / non stock on your phone right now, it wont boot or load with a relocked bootloader.
Seanie280672 said:
post your fastboot getvar all please without imei and serial number
did the firmware flash complete successfully ?
---------- Post added at 10:40 AM ---------- Previous post was at 10:34 AM ----------
also forgot to add, if the firmware flash went through fine then you will now have stock recovery on your phone, this will just look like a big red exclamation mark on your phone.
at this point you either need to find a stock RUU for your phone and run it now or unlocked your bootloader again at HTC dev, flash a custom recovery and then flash a custom rom.
if you have anything custom / non stock on your phone right now, it wont boot or load with a relocked bootloader.
Click to expand...
Click to collapse
Many thanks for the reply. I don't think the Firmware flashed succesfully, I tried three times and each time got the same response:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip firmware.zip
target reported max download size of 1830711296 bytes
sending 'zip' (49565 KB)...
OKAY [ 2.770s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 6.410s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip firmware.zip
target reported max download size of 1830711296 bytes
sending 'zip' (49565 KB)...
OKAY [ 2.787s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 6.431s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip firmware.zip
target reported max download size of 1830711296 bytes
sending 'zip' (49565 KB)...
OKAY [ 2.790s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 6.415s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.013s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 1830711296 bytes
sending 'recovery' (17034 KB)...
OKAY [ 1.706s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.455s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 1830711296 bytes
sending 'recovery' (17034 KB)...
OKAY [ 1.713s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.463s
Click to expand...
Click to collapse
And heres the getvar all
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
pastyal said:
Many thanks for the reply. I don't think the Firmware flashed succesfully, I tried three times and each time got the same response:
And heres the getvar all
Click to expand...
Click to collapse
which firmware did you download ? description or link if possible.
also you cant flash custom recovery as your bootloader is locked, and you need stock recovery and HTC dev unlock token to unlock it.
remove your imei and serial number from your getvar all, also, as you are s-on, you need to make sure that the firmware you flashed is ORANG001 firmware as per your cid, at a guess it will be something like 4.xx.61.x the 61 is the key, this will relate to region / carrier 61 is orange / EE, and the 4 is the latest android version firmware for the HTC one M8, as your version main is missing I cant fully confirm this, this is a fault from flashing earlier versions of TWRP recovery.
alternatively, you can flash a custom rom and get s-off via sunshine s-off @ $25 and convert your phone.
Seanie280672 said:
which firmware did you download ? description or link if possible.
also you cant flash custom recovery as your bootloader is locked, and you need stock recovery and HTC dev unlock token to unlock it.
remove your imei and serial number from your getvar all, also, as you are s-on, you need to make sure that the firmware you flashed is ORANG001 firmware as per your cid, at a guess it will be something like 4.xx.61.x the 61 is the key, this will relate to region / carrier 61 is orange / EE, and the 4 is the latest android version firmware for the HTC one M8, as your version main is missing I cant fully confirm this, this is a fault from flashing earlier versions of TWRP recovery.
alternatively, you can flash a custom rom and get s-off via sunshine s-off @ $25 and convert your phone.
Click to expand...
Click to collapse
Ooops thanks for the heads up on removing the info!
Aaah thats the mistake I made by using the wrong firmware. I will locate the correct firmware and try that later on today. I did look at the Sunshine option but was unsure if it would help me at this moment in time. Think i'll try the correct firmware first.
Will update here later with good news hopefully!
Seanie280672 said:
post your fastboot getvar all please without imei and serial number
did the firmware flash complete successfully ?
---------- Post added at 10:40 AM ---------- Previous post was at 10:34 AM ----------
also forgot to add, if the firmware flash went through fine then you will now have stock recovery on your phone, this will just look like a big red exclamation mark on your phone.
at this point you either need to find a stock RUU for your phone and run it now or unlocked your bootloader again at HTC dev, flash a custom recovery and then flash a custom rom.
if you have anything custom / non stock on your phone right now, it wont boot or load with a relocked bootloader.
Click to expand...
Click to collapse
Ok, I have now succesfully flashed the correct (I think ) firmware. I flashed twice to be sure. In cmd I rebooted to Fastboot but all I have now is the screen you mentioned with the red exclamation mark within a triangle. Where do I go from here as the phone won't do anything, not even turn off. It does occasionally turn off itself and I try to enter bootloader but it just loads to the red exclamation mark again.?
pastyal said:
Ok, I have now succesfully flashed the correct (I think ) firmware. I flashed twice to be sure. In cmd I rebooted to Fastboot but all I have now is the screen you mentioned with the red exclamation mark within a triangle. Where do I go from here as the phone won't do anything, not even turn off. It does occasionally turn off itself and I try to enter bootloader but it just loads to the red exclamation mark again.?
Click to expand...
Click to collapse
hold volume up, volume down and power button for about 15 to 20 seconds, phone will go off, before it comes back on quickly release all buttons and just hold volume down only, it should boot to the bootloader.
Thank you for that, that gets me into the bootloader but it won't load into fastboot now?
pastyal said:
Thank you for that, that gets me into the bootloader but it won't load into fastboot now?
Click to expand...
Click to collapse
what do you mean wont load into fastboot ? do you mean your computer just says waiting for device, which firmware did you flash ?
Seanie280672 said:
what do you mean wont load into fastboot ? do you mean your computer just says waiting for device, which firmware did you flash ?
Click to expand...
Click to collapse
Yes pc says waiting for device. I flashed a firmware from here, not sure which one it was now though http://forum.xda-developers.com/showthread.php?t=2701376
Do I need to flash a stock recovery now? If so do I need to be able to get the phone to load into fastboot?
pastyal said:
Yes pc says waiting for device. I flashed a firmware from here, not sure which one it was now though http://forum.xda-developers.com/showthread.php?t=2701376
Do I need to flash a stock recovery now? If so do I need to be able to get the phone to load into fastboot?
Click to expand...
Click to collapse
no you don't need to flash stock recovery, I don't see any firmware files for your phone in that link, and as your s-on, they shouldn't of been successful, nothing should of changed.
waiting for device is generally a driver problem, check device manager whilst your phone is plugged into your computer, should say android devices - MyHTC
Seanie280672 said:
no you don't need to flash stock recovery, I don't see any firmware files for your phone in that link, and as your s-on, they shouldn't of been successful, nothing should of changed.
waiting for device is generally a driver problem, check device manager whilst your phone is plugged into your computer, should say android devices - MyHTC
Click to expand...
Click to collapse
I can't see any android devices listed under device manager. I installed HTC Sync yesterday though which I thought loaded the drivers? What should i do now?
pastyal said:
I can't see any android devices listed under device manager. I installed HTC Sync yesterday though which I thought loaded the drivers? What should i do now?
Click to expand...
Click to collapse
Try to uninstall HTC Sync and any HTC drivers. Then see if the phone shows up in Device Manager. If so, select to manually pick drivers, and pick the generic MTP device.
Might not work for you, but this is what I had to do to get fastboot/adb working on my PC with the M8.
pastyal said:
I can't see any android devices listed under device manager. I installed HTC Sync yesterday though which I thought loaded the drivers? What should i do now?
Click to expand...
Click to collapse
Also make sure in bootloader it says FASTBOOT USB and not HBOOT
redpoint73 said:
Try to uninstall HTC Sync and any HTC drivers. Then see if the phone shows up in Device Manager. If so, select to manually pick drivers, and pick the generic MTP device.
Might not work for you, but this is what I had to do to get fastboot/adb working on my PC with the M8.
Click to expand...
Click to collapse
ssantos132 said:
Also make sure in bootloader it says FASTBOOT USB and not HBOOT
Click to expand...
Click to collapse
Sorted it, was a simple matter of swapping USB ports. I have a new laptop and forgot one of the ports was USB 3.0 which the phone was connected with. Evidently it prefers a USB 2.0 port.
So I assume now I need to find the correct firmware, of which I'm struggling with a little. Can anyone po8nt me in the right direction? I have been through a lot of threads here and can't seem to find anything.
pastyal said:
Sorted it, was a simple matter of swapping USB ports. I have a new laptop and forgot one of the ports was USB 3.0 which the phone was connected with. Evidently it prefers a USB 2.0 port.
Click to expand...
Click to collapse
That's right, USB 3.0 does not play well with this device.
pastyal said:
So I assume now I need to find the correct firmware, of which I'm struggling with a little. Can anyone po8nt me in the right direction? I have been through a lot of threads here and can't seem to find anything.
Click to expand...
Click to collapse
I can't find the firmware for your CID either. You may have better luck updating the firmware by OTA.
To do that, you will need to restore the stock ROM and stock recovery, using the files and instructions here: http://forum.xda-developers.com/showthread.php?t=2701376
After restoring stock ROM and stock recovery, you will need to update up to Lollipop, which will probably include a few (3) OTA updates.
Once you've updated to current firmware by OTA, you can install custom recovery again, and run the current custom ROMs.
redpoint73 said:
That's right, USB 3.0 does not play well with this device.
I can't find the firmware for your CID either. You may have better luck updating the firmware by OTA.
To do that, you will need to restore the stock ROM and stock recovery, using the files and instructions here: http://forum.xda-developers.com/showthread.php?t=2701376
After restoring stock ROM and stock recovery, you will need to update up to Lollipop, which will probably include a few (3) OTA updates.
Once you've updated to current firmware by OTA, you can install custom recovery again, and run the current custom ROMs.
Click to expand...
Click to collapse
I'm getting myself in a right mess I think. I've just tried installing the stock recoveries from https://www.androidfilehost.com/?w=files&flid=25064 as linked to from this thread http://forum.xda-developers.com/showthread.php?t=2694994 which I thought woud be perfect for me but I get an error of "FAILED (remote: signature verify fail)" in cmd. If I reboot the phone into recovery I get the red exclamation mark again.
Any ideas on what i'm doing wrong? Am i right in thinking I need to flash a stock recovery and THEN a stock ROM, or should it be the other way around?
pastyal said:
I'm getting myself in a right mess I think. I've just tried installing the stock recoveries from https://www.androidfilehost.com/?w=files&flid=25064 as linked to from this thread http://forum.xda-developers.com/showthread.php?t=2694994 which I thought woud be perfect for me but I get an error of "FAILED (remote: signature verify fail)" in cmd. If I reboot the phone into recovery I get the red exclamation mark again.
Any ideas on what i'm doing wrong? Am i right in thinking I need to flash a stock recovery and THEN a stock ROM, or should it be the other way around?
Click to expand...
Click to collapse
Multiple mistakes here:
1) You need the stock ROM and recovery that corresponds with your hboot (3.16) which would indicate a 1.x software and corresponding recovery. The files you linked are for software 3.x and 4.x.
2) I'm also not sure why you are stumbling around in threads that aren't even for your CID when I already gave you a link to the proper location for the stock nandroid for your CID version. You want to restore the stock nandroid for ORANG001, which is 1.54.61.5 and the stock recovery 1.54.xx
3) You need to flash the stock ROM (restore stock nandroid) before the stock recovery. Once you've restored stock recovery, you cannot flash a ROM or nandroid. You need custom recovery to do that.
3) Lollipop recoveries for other CID won't work. But a KitKat recovery for another CID will work (as mentioned in item 2 above, you want a 1.54.xx recovery to correspond to the stock ROM 1.54.61.5 since a recovery doesn't seem to be posted for your exact software 1.54.61.5
redpoint73 said:
Multiple mistakes here:
1) You need the stock ROM and recovery that corresponds with your hboot (3.16) which would indicate a 1.x software and corresponding recovery. The files you linked are for software 3.x and 4.x.
2) I'm also not sure why you are stumbling around in threads that aren't even for your CID when I already gave you a link to the proper location for the stock nandroid for your CID version. You want to restore the stock nandroid for ORANG001, which is 1.54.61.5 and the stock recovery 1.54.xx
3) You need to flash the stock ROM (restore stock nandroid) before the stock recovery. Once you've restored stock recovery, you cannot flash a ROM or nandroid. You need custom recovery to do that.
3) Lollipop recoveries for other CID won't work. But a KitKat recovery for another CID will work (as mentioned in item 2 above, you want a 1.54.xx recovery to correspond to the stock ROM 1.54.61.5 since a recovery doesn't seem to be posted for your exact software 1.54.61.5
Click to expand...
Click to collapse
Thanks very much for that, the reason why i was stumbling around is because i had already tried that Nandroid backup but i think i must have used incorrect instructions. I read I had to open the zip file and flash the boot.img, but I just get the same error as before if I do that.
Could you please tell me how to restore the stock Nandroid. i promise you I am going around in circles lol
pastyal said:
i had already tried that Nandroid backup but i think i must have used incorrect instructions. I read I had to open the zip file and flash the boot.img, but I just get the same error as before if I do that.
Click to expand...
Click to collapse
Instruction on restoring a nandroid are in post #3 of the stock nandroid collection thread I linked before. Click where it says Questions & Answers, and you will see the 2nd question is how to restore a stock nandroid: http://forum.xda-developers.com/showpost.php?p=58128936&postcount=3
I think you may have seen these instructions, but you only did one part, not the remaining parts of the process. The boot.img is essentially just the kernel; technically a few other things too, but either way its like 1% of what you need to have a working ROM. Namely, if you only flashed boot.img, you didn't do the steps I've highlighted in orange below:
- Place the nandroid backup unpacked on the sdcard of the phone in the right backup folder
* Philz touch uses - Clockworkmod\Backups\
* TWRP uses - TWRP\Backups\ or TWRP/Backups/serialnum/ (replace serialnum with your device's serial number. To have TWRP create the proper directory structure for you, just do a simple backup of just the boot partition and put the backup files in there) thanks to garyd9 for the additional info
- Flash the boot.img or boot.emmc.win file from the nandroid backup
- Make a full wipe in the recovery
- Restore the nandroid backup and reboot
You need to unzip the downloaded file, then place the entire folder contents to the proper location on the phone. Then boot recovery (probably TWRP) and use the restore function to install the nandroid. I actually do not think you need to extract and flash boot.img separately.
After that, install the stock recovery with the fastboot command: fastboot flash recovery filename.img
Where "filename.img" is the actual name of the desired stock recovery file.
---------- Post added at 11:03 AM ---------- Previous post was at 10:57 AM ----------
pastyal said:
If it helps the phone is "Relocked" and S-ON.
Click to expand...
Click to collapse
Are you currently unlocked again? The above is from your top post, but I don't know if you've changed this (unlocked again).
You can only do the above mentioned steps (restore nandroid, stock recovery, etc.) if you are bootloader unlocked.
Bought Japan Variant HTC 10,
S-off, Bootloader Unlocked.
[flashed TWRP once and did Backup.]<-yeah i did
Changed CID to US Unlocked one and RUUed Android 7.0
All went great at this point.
Then I tried to flash TWRP again and now i just can't boot into it.
flashing went smoothly, at leat log says;
fastboot flash recovery twrp.img
target reported max download size of 1579200000 bytes
sending 'recovery' (21992 KB)...
OKAY [ 1.717s]
writing 'recovery'...
(bootloader) HOSD CL#831921
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 2.529s]
finished. total time: 4.249s
fastboot reboot-bootloader
AAAAAAAAAAAAAAAND I just can't boot into TWRP.
Phone just showing htc logo for a while and reboot to ROM.
So i tried fastboot boot twrp.img method, still not working.
download mode screen
Am I missing sth? like key combo to show twrp or bug at twrp 3.0.2.6?
I had the exact same problem, I solved it by flasing the twrp 3.0.3-0 unofficial version that you can find on the twrp recovery's thread
Edit: I don't know if this is the right way to do it, it worked for me but I'm new in the modding world and I'm not sure it will work for you too or if it's safe. Maybe is better to wait for someone that knows more than me.
solved
Since I did OTA from 2.28.617.8 to 2.38.617.6,
I googled and RUUed 2.38.617.6, not 2.28.617.8 from official HTC US hp.
and I flashed twrp 3.0.3.0 unofficial, instead of 3.0.2.6 official.
I don't know which one was critical, but everything went fluently.
Seems like 3.0.3.0 was the critical one.
Thx @fratorga100, for the reply.
I recently got a replacement HTC 10 unit from HTC. I am attempting to install TWRP on it, but am unable to.
I did the standard unlock method from HTCdev.com. Everything there worked fine and the device is unlocked.
I have downloaded multiple versions of the twrp.img but am having the same issue across the board. I can't figure out what is wrong, as I had no issues on my previous HTC 10 unit.
C:\HTC>fastboot flash recovery twrp.img
target reported max download size of 1579200000 bytes
sending 'recovery' (47708 KB)...
OKAY [ 2.668s]
writing 'recovery'...
(bootloader) HOSD CL#857212
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 3.074s]
finished. total time: 5.773s
Everything seems like it's fine, but when I try to boot into bootloader and then recovery it gives me the htc, this build is intended for develpment purposes... screen and then goes directly into the rom never loading TWRP.
I can't figure this out, as I never had any issue before. My device is updated with the latest US version.
Can anyone help?
Thanks
I was having the exact same issue and was literally typing the same post as you when I saw yours.
I found this link with the unofficial TWRP builds and flashed 3.0.3.3. That finally got me into TWRP. You'll still see the gray HTC letters with the red disclaimer, but wait a few seconds and it should boot into recovery.
Hopefully that helps.
yoderz said:
I was having the exact same issue and was literally typing the same post as you when I saw yours.
I found this link with the unofficial TWRP builds and flashed 3.0.3.3. That finally got me into TWRP. You'll still see the gray HTC letters with the red disclaimer, but wait a few seconds and it should boot into recovery.
Hopefully that helps.
Click to expand...
Click to collapse
That worked!
Thanks!