Whole rundown of the situation:
Wanted to be able to root my phone, do some research, mainly with http://androidforums.com/threads/ro...ecovery-guide-for-htc-desire-601-zara.817068/ and the one-click-root
Attempted one-click-root first as I did not want to mess with my phone too much, ended up not working.
Try to manually root my phone, unlocked the bootloader, installed SuperSU.zip via the guide above
Check to see if I have root access, did not; attempted to do a full restart where I factory reset everything after another backup
Phone starts hanging on the HTC logo screen
Do some more research and eventually get to this soft-brick solution guide http://forum.xda-developers.com/showpost.php?p=55850035&postcount=23
Followed the steps and am now currently booting into the fastboot screen permanently; even when attempting to power down, phone keeps booting back up.
Did some more research and found a semi-related question pertaining to this question with no definitive solution: http://forum.xda-developers.com/htc-one-m8/help/phone-booting-fastboot-mode-t2949325
Some info on the phone itself:
Code:
*** TAMPERED ***
*** UNLOCKED ***
ZARA_UL PVT SKIP S-ON RL
HBOOT-2.22.0000
RADIO-1.26.40e.00.14
OpenDSP-v18.2.0268.0925
OS-2.14.613.3
eMMC-boot 1024MB
Feb 26 2014, 12:27:49.0
version: 0.5
version-bootloader: 2.22.0000
version-baseband: 1.26.40e.00.14
version-cpld: None
version-microp: None
version-main: 2.14.631.3
version-misc: PVT SHIP S-ON
serialno: FA42TWK00711
imei: 357601052070301
meid:
product: zara_ul
platform: HBOOT-8930
modelid: 0P4E20000
cidnum: ROGER001
battery-status: good
battery-voltage: 4314mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-ae8bbb39
hbootpreupdate: 11
gencheckpt: 0
I'm kind of new to the mobile platform, but am relatively competent with a computer, any help with this problem is greatly appreciated!
Do you have custom recovery? If yes, can you boot into recovery via the hboot screen? If not, I would suggest you to flash KK recovery via fastboot, this one, and see if you can reboot into it.
I have TWRP 2.7.0.0 currently as my custom recovery, and I can boot into recovery from the hboot menu, but still keep rebooting. I'll try out the kitkat version.
Edit: Tried out the kitkat version, all seemed well before reboot, no errors/missing files mentioned, rebooted and the phone still keeps only booting into fastboot. Double checked, tried to boot normally, just hangs at the HTC logo screen now.
Sythe777 said:
I have TWRP 2.7.0.0 currently as my custom recovery, and I can boot into recovery from the hboot menu, but still keep rebooting. I'll try out the kitkat version.
Edit: Tried out the kitkat version, all seemed well before reboot, no errors/missing files mentioned, rebooted and the phone still keeps only booting into fastboot. Double checked, tried to boot normally, just hangs at the HTC logo screen now.
Click to expand...
Click to collapse
In TWRP go to Wipe and select System, Data, Cache and Dalvik cache and wipe them. Then download this stock rom zip, then copy it to your SD and flash it.
Related
Figured I'd ask the XDA community before I give up. I was working on an HTC Rezound that a kid had water damage on. Finally got it running but with the weirdest issues I've seen. I've tried alot, can't remember everything off the top of my head but I wanted to double check with you guys before I give up tomorrow.
First off Its HTCDev unlocked, S-ON with HBOOT 2.28. There is no ROM or OS on it, nor will it boot to any Recovery I successfully flash over. I can send and receive commands on fastboot, and sometimes can send them when I select REBOOT RECOVERY. That leads me to a black screen but adb devices shows it under recovery.
Tried flashing TWRP, using the All In One tool, flashing a Custom ROM, the RUU zip and exe, and Amon-Ra recovery. All leads to the same thing basically, loads into HBOOT fine but never boots into any recovery. I get signature verify failed sometimes when flashing but honestly it sends and successfully writes a recovery.img but wont load into it. Is it brain dead somewhere or what?
Thanks guys! I'll post the getvar
C:\Users\AZ's Gaming>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.28.0000
(bootloader) version-baseband: 2.23.10.0123r/2.23.10.0124r
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.00.000.0
(bootloader) serialno: HT19VS219499
(bootloader) imei: 990000336135878
(bootloader) product: vigor
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PH9810000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3746mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: cecc19f7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
DO THIS ADVICE ONLY IF NOBODY ELSE HAS BETTER IDEA..
Flash the latest ruu thru bootloader boot into recovery image while on stock to see if it works if it does then unlock hboot then flash recovery if it doesn't well we will have to dig a lil deeper
Sent from my Infected Rezound using xda app-developers app
Put the recovery.img file from the latest TWRP into your adb directory, then issue:
fastboot boot recovery.img (Note the BOOT command, not flash!)
and see if that gets you to TWRP, if not, you are probably in trouble... if it does, wipe everything except boot and flash in a known stable ROM image like Global OTA Stock/Rooted, Infection, Beanstalk, or something like that.
Your fastboot getvar looks fine, except battery voltage is really low (should be around 3.9-4.2) and the version-main is messed up, meaning it doesn't see a ROM installed.
acejavelin said:
Put the recovery.img file from the latest TWRP into your adb directory, then issue:
fastboot boot recovery.img (Note the BOOT command, not flash!)
and see if that gets you to TWRP, if not, you are probably in trouble... if it does, wipe everything except boot and flash in a known stable ROM image like Global OTA Stock/Rooted, Infection, Beanstalk, or something like that.
Your fastboot getvar looks fine, except battery voltage is really low (should be around 3.9-4.2) and the version-main is messed up, meaning it doesn't see a ROM installed.
Click to expand...
Click to collapse
I tried this first because it was the only thing I haven't done, and I got nothing. It boots into a recovery I think because it shows up under adb devices but still get a black screen. I think the phone is toast.
NINJA EDIT: The menu and home buttons vibrate when I hit them, so it must be booted into recovery, just for some reason nothing is displayed.
I attempted to install the latest Viper ROM over the Viper I had currently on my HTC One. It said it installed, then went to reboot, and stayed on the white screen for a while. I rebooted, but it did the same thing again. I got to looking in TWRP and it didn't have an OS installed, and it had wiped my backups. Now, I can get to TWRP, and I can get to Fastboot, but I can't connect with ADB. I have an OTG USB cable, but when I try to install a zip from my USB drive, I get the error message, "E:Unable to mount '/system'". When I go to MOUNT in TWRP, it won't let me select System to mount it.
I thought this would be the perfect time to go with the GPE RUU, but I can't connect with ADB.
What do I do? (deep breaths taken already)
try formating your data in twrp then reboot into recovery then mount usb-otg and flash or transver then rom to sd card
rushwal said:
I attempted to install the latest Viper ROM over the Viper I had currently on my HTC One. It said it installed, then went to reboot, and stayed on the white screen for a while. I rebooted, but it did the same thing again. I got to looking in TWRP and it didn't have an OS installed, and it had wiped my backups. Now, I can get to TWRP, and I can get to Fastboot, but I can't connect with ADB. I have an OTG USB cable, but when I try to install a zip from my USB drive, I get the error message, "E:Unable to mount '/system'". When I go to MOUNT in TWRP, it won't let me select System to mount it.
I thought this would be the perfect time to go with the GPE RUU, but I can't connect with ADB.
What do I do? (deep breaths taken already)
Click to expand...
Click to collapse
did you flash the newest version of TWRP 2.6.3.3 ?
When I flash from the usb otg adapter
I shut the phone completely off
hookup the cable and flash drive
bootup recovery / select wipe/ factory reset / then install
on the install screen I browse to the usb otg by tapping the Storage: and choosing usb otg
then back and when you choose install again you should be in the root of the flash drive
choose your rom and install. first boot up sometimes takes over 5 min to complete be patient before you give up and reboot the phone from the white htc screen.
clsA said:
did you flash the newest version of TWRP 2.6.3.3 ?
When I flash from the usb otg adapter
I shut the phone completely off
hookup the cable and flash drive
bootup recovery / select wipe/ factory reset / then install
on the install screen I browse to the usb otg by tapping the Storage: and choosing usb otg
then back and when you choose install again you should be in the root of the flash drive
choose your rom and install. first boot up sometimes takes over 5 min to complete be patient before you give up and reboot the phone from the white htc screen.
Click to expand...
Click to collapse
How do I install new version of TWRP other than by methods on the TWRP web page? If I can't adb, can't do it by app?
http://teamw.in/project/twrp2/164
When I try to Factory Reset, I get the cannot mount SYSTEM error.
When I try to install, I get the cannot mount SYSTEM error.
Terror starting to creep in despite deep breaths.
rushwal said:
How do I install new version of TWRP other than by methods on the TWRP web page? If I can't adb, can't do it by app?
http://teamw.in/project/twrp2/164
When I try to Factory Reset, I get the cannot mount SYSTEM error.
When I try to install, I get the cannot mount SYSTEM error.
Terror starting to creep in despite deep breaths.
Click to expand...
Click to collapse
Here is the recovery flashable version of twrp 2.6.3.3
Turn the phone completely off (hold power for 10-15 seconds)
now boot to recovery power + vol down
then flash the file below and repeat the power off
thanks!
clsA said:
Here is the recovery flashable version of twrp 2.6.3.3
Turn the phone completely off (hold power for 10-15 seconds)
now boot to recovery power + vol down
then flash the file below and repeat the power off
Click to expand...
Click to collapse
Still getting Unable to mount System error.
rushwal said:
Still getting Unable to mount System error.
Click to expand...
Click to collapse
can you post the results for fastboot getvar all and maybe you can RUU back to stock
clsA said:
can you post the results for fastboot getvar all and maybe you can RUU back to stock
Click to expand...
Click to collapse
I'm not able to connect via ADB.
rushwal said:
I'm not able to connect via ADB.
Click to expand...
Click to collapse
Have you tried fastboot from the bootloader screen?
What os is on your PC?
How did you unlock the bootloader to get twrp?
Sent from my HTC One using Tapatalk
clsA said:
Have you tried fastboot from the bootloader screen?
What os is on your PC?
How did you unlock the bootloader to get twrp?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
If I power up the device, it starts up into TWRP. If I hold down pwr+vol down, I can get into fastboot, but I haven't found anything I can do from there except boot into recovery.
I've been using my Windows 8.1 laptop, but I also have access to a Windows 7.
I used the HTC dev web site to unlock back when I got it. I had to do the change to Rogers device in order to unlock. It's been a while since I did this, and I've been running Viper ROM for so long, I don't remember everything I've done.
Thanks for your help!
rushwal said:
If I power up the device, it starts up into TWRP. If I hold down pwr+vol down, I can get into fastboot, but I haven't found anything I can do from there except boot into recovery.
I've been using my Windows 8.1 laptop, but I also have access to a Windows 7.
I used the HTC dev web site to unlock back when I got it. I had to do the change to Rogers device in order to unlock. It's been a while since I did this, and I've been running Viper ROM for so long, I don't remember everything I've done.
Thanks for your help!
Click to expand...
Click to collapse
From the win 7 PC boot to the bootloader fastboot USB and run the command fastboot getvar all and post your results
This will tell what hboot your on and the mainver of your firmware, so you can determine which RUU will return your phone to Stock
Sent from my HTC One using Tapatalk
clsA said:
From the win 7 PC boot to the bootloader fastboot USB and run the command fastboot getvar all and post your results
This will tell what hboot your on and the mainver of your firmware, so you can determine which RUU will return your phone to Stock
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Thanks, I will try when I get home.
clsA said:
From the win 7 PC boot to the bootloader fastboot USB and run the command fastboot getvar all and post your results
This will tell what hboot your on and the mainver of your firmware, so you can determine which RUU will return your phone to Stock
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Ok, finally got ADB working on the W7 machine.
C:\Users\Walter>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4211mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.046s
rushwal said:
Ok, finally got ADB working on the W7 machine.
C:\Users\Walter>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4211mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.046s
Click to expand...
Click to collapse
Fantastic your phone has never been updated.. it will be easy to s-off with revone
you should do that right away. after that thier are a bunch of AT&T files you can use to get your phone back into new condition.
http://www.htc1guru.com/downloads/ruu-file-downloads/
all the files with cingular in the name will work on your phone
I would go directly to US 3.17.502.3 after you get s-off
edit your post and remove you serial and iemi like I did in the quote
clsA said:
Fantastic your phone has never been updated.. it will be easy to s-off with revone
you should do that right away. after that thier are a bunch of AT&T files you can use to get your phone back into new condition.
http://www.htc1guru.com/downloads/ruu-file-downloads/
all the files with cingular in the name will work on your phone
I would go directly to US 3.17.502.3 after you get s-off
edit your post and remove you serial and iemi like I did in the quote
Click to expand...
Click to collapse
What if I want to put GPE on it. Easy?
clsA said:
Fantastic your phone has never been updated.. it will be easy to s-off with revone
you should do that right away. after that thier are a bunch of AT&T files you can use to get your phone back into new condition.
http://www.htc1guru.com/downloads/ruu-file-downloads/
all the files with cingular in the name will work on your phone
I would go directly to US 3.17.502.3 after you get s-off
edit your post and remove you serial and iemi like I did in the quote
Click to expand...
Click to collapse
I keep getting device not found when I try to ADB.
rushwal said:
I keep getting device not found when I try to ADB.
Click to expand...
Click to collapse
adb only works in recovery or when the phone is booted to android
you can convert to GPE, but you need to run the AT&T RUU first to make sure all your partitions are correct
and your phone is working correctly. I still recommend getting s-off first
and here's a tutorial on RUU
http://www.andromods.com/unroot-locking/how-to-restore-to-stock-unbrick-unrooting-htc-one-m7.html
clsA said:
adb only works in recovery or when the phone is booted to android
you can convert to GPE, but you need to run the AT&T RUU first to make sure all your partitions are correct
and your phone is working correctly. I still recommend getting s-off first
and here's a tutorial on RUU
http://www.andromods.com/unroot-locking/how-to-restore-to-stock-unbrick-unrooting-htc-one-m7.html
Click to expand...
Click to collapse
While in recovery, when I try to ADB following the instructions to get S-OFF using revone, I am getting device not found.
Ok, I'm back running again! Thanks for your help!
Now to get GPE on there.
@clsA
My HTC one is caught in a bootloop, i recently tried to flash the Android Revolution 41.0 rom on clockworkmod recovery (idk if that is the issue since the thread recommended me to use twrp) anyway the installation worked fine until the last step (i dont remember unfortunately), i skipped it accidentally and thus began the bootloop. i tried to go into recovery and would only get the CWM 6.0.4.3 logo for a few seconds and then it would boot back to the htc logo. I was using windows 8.1 and tried to flash a new recovery, rom, whatever. the problem was windows would not recognize my usb device. I read some threads and decied to re install all the android software i had on my computer (htc sync,SDK, etc.) still no go. I went ahead and booted up my pc with Ubuntu 13.10, im still having the same initial issue of USB recognition. anytime i type adb devices i get the list of devices with nothing, everytime i try to run a fastboot command nothing happens. anyway this is what on my bootloader screen and getvar:
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.14.3250.13off
OpenDSP-v26.120.274.0202
eMMc-boot
when i run fastboot getvar all i get <waiting for devices> and nothing else happens, @clsA might be correct about my phone not being s-off ill see how to fix that and update as i go, thanks in advance for any other help. not that i am currently using ubuntu
went ahead and tried running the moonshine s-off when tryingto check for updates there was an error and the program stopped...
!! Do NOT for any reason touch, unplug, lick or maim your device !!
Checking for updates......
ERROR: Cannot check for updates
Click to expand...
Click to collapse
qibz said:
went ahead and tried running the moonshine s-off when tryingto check for updates there was an error and the program stopped...
Click to expand...
Click to collapse
yeah your not going to have any luck with windows 8.1, your hboot on your phone has to be 1.55.000 before windows 8 will work.
So your basically stuck learning Ubuntu till you get your phone updated.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.12
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT359W918802
(bootloader) imei: 354439052875079
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4284mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 3.666s
Click to expand...
Click to collapse
fially got the fastboot getvar all command to work on my other windows 8 machine. wet ahead and fastboot cachee clear still stuck in bootloop, will try other methods sice this machine does recognize my phoe, thanks again
qibz said:
fially got the fastboot getvar all command to work on my other windows 8 machine. wet ahead and fastboot cachee clear still stuck in bootloop, will try other methods sice this machine does recognize my phoe, thanks again
Click to expand...
Click to collapse
reflash recovery
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then install root http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip
then try and get s-off
http://forum.xda-developers.com/showthread.php?t=2314582
clsA said:
reflash recovery
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then install root http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip
then try and get s-off
http://forum.xda-developers.com/showthread.php?t=2314582
Click to expand...
Click to collapse
I tried to flash recovery, no go, I am however able to fastboot boot recovery.img I went ahead and wiped dalvik cache system cache and data. went back to the bootloader and tried to flash the recovery again, no go. I wanted to try and boot up a rom and maybe be able to flash a recovery that way, rom wont boot.
if i am able to boot into twrp via boot can i flash a recovery or rom that way, i dont want to do anything else and brick my phone.
thanks again
qibz said:
I tried to flash recovery, no go, I am however able to fastboot boot recovery.img I went ahead and wiped dalvik cache system cache and data. went back to the bootloader and tried to flash the recovery again, no go. I wanted to try and boot up a rom and maybe be able to flash a recovery that way, rom wont boot.
if i am able to boot into twrp via boot can i flash a recovery or rom that way, i dont want to do anything else and brick my phone.
thanks again
Click to expand...
Click to collapse
what is the error you get flashing recovery ?
did you md5 check your download.
paste the command window here so I can see whats happening
clsA said:
what is the error you get flashing recovery ?
did you md5 check your download.
paste the command window here so I can see whats happening
Click to expand...
Click to collapse
PROBLEM SOLVED!!
booting the recovery was the key to my solution
fastboot boot<name of recovery>.img
once i was in twrp i cleared the cache, data, system, and anything other thing i could find. i then went and flashed htc dumlock and reflashed recovery within twrp. i was then able to reboot into recover (cwm 6.0.4.3). from there i just used adb sideload to flash CM 10.2 and GAPPS 4.3 and finally got my phone back up and running.
thanks again for everything, i hope my solution can help others who have my problem
qibz said:
PROBLEM SOLVED!!
booting the recovery was the key to my solution
fastboot boot<name of recovery>.img
once i was in twrp i cleared the cache, data, system, and anything other thing i could find. i then went and flashed htc dumlock and reflashed recovery within twrp. i was then able to reboot into recover (cwm 6.0.4.3). from there i just used adb sideload to flash CM 10.2 and GAPPS 4.3 and finally got my phone back up and running.
thanks again for everything, i hope my solution can help others who have my problem
Click to expand...
Click to collapse
Glad to here your back up and running
After unsuccessfully trying to manually update to 4.4.2 I have semi-bricked my phone.
Bootloader menu currently has Tampered, Relocked, Security Warning and S-On. I accidentally wiped data while in recovery while attempting to flash something. I had flashed (I believe) a modified stock kernel for 4.4 (or 4.3, not sure). Edit: Hboot 1.55
-Because it's not S-Off, I can't run an RUU.exe and downgrade.
-I can't seem to enter recovery either. It says "entering recovery" and then goes back to the bootloader screen. When I try to flash a new recovery, I get a "remote: signature verify fail" error. Any sort of recovery.img file gets this same error. I've tried installing a different recovery and the same error shows up.
-I've tried using revone: http://forum.xda-developers.com/showthread.php?t=2314582 except I it says "error: device not found" when I try to initiate it.
Is it possible to find a 4.3/4.4.2 RUU zip/exe and try to flash/run a current/higher version firmware? If anybody could also post a link to the stock 4.3 kernel it would be appreciated.
Thanks.
I need the phone for use very soon. Something tells me I did revone wrong. Any options I have? Isn't there a desktop program that lets you restore your HTC back to factory stock?
mch277 said:
After unsuccessfully trying to manually update to 4.4.2 I have semi-bricked my phone.
Bootloader menu currently has Tampered, Relocked, Security Warning and S-On. I accidentally wiped data while in recovery while attempting to flash something. I had flashed (I believe) a modified stock kernel for 4.4 (or 4.3, not sure).
-Because it's not S-Off, I can't run an RUU.exe and downgrade.
-I can't seem to enter recovery either. It says "entering recovery" and then goes back to the bootloader screen. When I try to flash a new recovery, I get a "remote: signature verify fail" error. Any sort of recovery.img file gets this same error. I've tried installing a different recovery and the same error shows up.
-I've tried using revone: http://forum.xda-developers.com/showthread.php?t=2314582 except I it says "error: device not found" when I try to initiate it.
Is it possible to find a 4.3/4.4.2 RUU zip/exe and try to flash/run a current/higher version firmware? If anybody could also post a link to the stock 4.3 kernel it would be appreciated.
Thanks.
I need the phone for use very soon. Something tells me I did revone wrong. Any options I have? Isn't there a desktop program that lets you restore your HTC back to factory stock?
Click to expand...
Click to collapse
Can you get into fastboot? If so, post the results of fastboot getvar all (minus IMEI and SN).
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.19.3263.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4320mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
If you are attempting to get s-off revone will not work on you... You should try rumrunner instead
Sent from my HTC One using XDA Premium 4 mobile app
TopoX84 said:
If you are attempting to get s-off revone will not work on you... You should try rumrunner instead
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I've tried. Except rumrunner needs you to be able to boot into Android first. I accidentally wiped data while in recovery (ROM, etc) and now I only have fastboot. I can't even access recovery/flash a new recovery/flash anything at all really. I can get into the silver HTC logo with "fastboot oem rebootRUU" but that's about it. Anything I attempt to flash while doing that will get a signature verification fail.
Update: I unlocked the bootloader again and can now enter recovery. The issue is, it appears that I have no "SD card". I can't access or even mount it to computer so I can put a ROM inside when I select "choose zip from /sdcard.
Yesterday, I wanted to root my HTC One Max (t6ul)
version: 0.5
version-bootloader: 2.49.0000
version-baseband: 4T.27.3218.14
version-cpld: None
version-microp: None
version-main: 3.23.707.1
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: t6ul
platform: HBOOT-8064
modelid: 0P3P52000
cidnum: HTC__044
battery-status: good
battery-voltage: 3985mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-0e1af350
hbootpreupdate: 11
gencheckpt: 0
I was under the impression that you needed to be S-OFFed in order to be rooted
What I did:
Downloaded [SUPER-TOOL] Team PWN Stars' HTC One Max Super-Tool v1.2 FOR ALL HTC ONE MAX VARIANTS
Followed the tool's guide:
Code:
1- Unlock your bootloader
-this allows us to make modifications to the device
2- Use the RumRunner tool to gain S-OFF (in the S-OFF Tools Menu) I DID NOT CREATE THIS> All that the kit does is download it for you.
-this will be used later to make your device appear Stock
3- Install a Custom Recovery
-this allows us to "flash" files. It will be used to gain Root access
4- Root your Device
-this installs the package that grants you Root permissions.
OPTIONAL-
5- Lock your bootloader
-this will make your device appear stock for warranties and crap
Successfully unlocked the bootloader via HTCDev (at this point bootloader shows **UNLOCKED**)
Tried S-OFFing via rumrunner. This failed since my hboot is v2.49
Tried S-OFFing again following this guide: [FAQ] How to S-OFF @ hboot 2.49.000
After flashing both recovery and boot.img, i tried to do the next step "Factory reset the device"
Here the bootloader now shows **TAMPERED** above **UNLOCKED**
And selecting "Factory reset device" would boot me into recovery mode
I then formatted /cache, /data and then rebooted the phone
After the HTC One screen, the screen turns cyan then magenta while playing the 'boot-up' sound. It then stays in the HTC One screen
Thought that it was my ROM (it was stock 3.15, I believe. It was the one with the 'customizable fonts' update). I flashed a new one (odex): [ROM][International] Stock ROM Sense 6 | Kitkat 4.4.2 | 3.15.1540.1 | Rooted
Now it boots past the HTC One screen, and I'm greeted with the lockscreen. Unlocking it will show the HTC One screen again (and sometimes shows "htc.dialer has stopped working") and then restarts (I can swipe down to show the notifications bar but I can't pull it down)
If I don't unlock it, it would reboot after a while
Is there a way to more or less "revert" back to stock? Or at least have my phone properly boot?
I suspect its because I flashed in the boot.img? If this is the case, is there a "stock boot.img" i can use to fix it?
I just want a rooted stock :crying: