Related
Hi -
Thanks for any help in advance. I'm a bit of a rookie round here, I've rooted and flashed my past 3 HTC phones but taken the easy route every time.
But today, I've used ADB commands to flash the revone binary and unlock and get s-off on my HTC one m7. It took me several tries, but it eventually worked (or at least said successful). So my HBOOT 1.44 says UNLOCKED & S-OFF.
So onto the next step. fastboot flash recovery recoverytwrp.img
...
Another success!
So, I reboot into bootloader and prompt recovery boot like I'm about to get HAM on twrp and flash some superuser files. It shows me a developer screen full of red print saying that it's booting into recovery, and then after a while, it just rebooted back into system.
It does this every time. I reflashed the image, I flashed the stock image, I tried the hansoon tool. each time I can't actually get into the recovery.
So this is where I'm stuck. Why can't I get anywhere with this?
EDIT & ANSWER;
Sprint phone needed Sprint TWRP image
Have you tried
fastboot erase cache
BenPope said:
Have you tried
fastboot erase cache
Click to expand...
Click to collapse
This.
Just do evrything again until you finish installing custom recoveries. Before rebooting, erase the cache with "fastboot erase cache"
ryryzz said:
This.
Just do evrything again until you finish installing custom recoveries. Before rebooting, erase the cache with "fastboot erase cache"
Click to expand...
Click to collapse
Gave that all a shot all over again. Still can't boot into recovery
Is fast boot off?
Use the original cable your One came with, go into bootloader power/vol - then open a cmd window
Now connect the One with your computer, don't use a USB 3.0 connection, and a different one then before.
In bootloader choose fastboot, that should change to fastboot USB
In cmd window point to your fastboot directory where you also copied the recovery to, I would try CWM touch for now.
Type cd c:\fastboot (or what your toolfolder is called)
fastboot erase cache
fastboot flash recovery recovery.img
fastboot erase cache
That installs the recovery, you can select it in bootloader abd boot into it.
Sent from my HTC One using xda premium
---------- Post added at 06:28 PM ---------- Previous post was at 06:23 PM ----------
BenPope said:
Is fast boot off?
Click to expand...
Click to collapse
You mean the fastboot option under Power Settings is unticked when booted up normally?
Sent from my HTC One using xda premium
hardstuffmuc said:
Use the original cable your One came with, go into bootloader power/vol - then open a cmd window
Now connect the One with your computer, don't use a USB 3.0 connection, and a different one then before.
In bootloader choose fastboot, that should change to fastboot USB
In cmd window point to your fastboot directory where you also copied the recovery to, I would try CWM touch for now.
Type cd c:\fastboot (or what your toolfolder is called)
fastboot erase cache
fastboot flash recovery recovery.img
fastboot erase cache
That installs the recovery, you can select it in bootloader abd boot into it.
Sent from my HTC One using xda premium
---------- Post added at 06:28 PM ---------- Previous post was at 06:23 PM ----------
You mean the fastboot option under Power Settings is unticked when booted up normally?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Same deal. On it's way to booting into recovery it goes blank, resets and reboots into system
C:\adt\sdk\platform-tools>fastboot erase cache
erasing 'cache'...
OKAY [ 0.078s]
finished. total time: 0.078s
C:\adt\sdk\platform-tools>fastboot flash recovery recovery.img
sending 'recovery' (7422 KB)...
OKAY [ 1.139s]
writing 'recovery'...
OKAY [ 0.640s]
finished. total time: 1.778s
C:\adt\sdk\platform-tools>fastboot erase cache
erasing 'cache'...
OKAY [ 0.062s]
finished. total time: 0.062s
C:\adt\sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.047s
There's the last log - and then on it's way to recovery there's a red disclaimer and a pink text saying "Entering Recovery"...then after 20 seconds it resets
Did you try various recovery (versions) ? May be , you just have corrupted recovery image.
tash2013 said:
Did you try various recovery (versions) ? May be , you just have corrupted recovery image.
Click to expand...
Click to collapse
at this point I've tried stock, twrp and cwm. All with the same results
Jman12000 said:
at this point I've tried stock, twrp and cwm. All with the same results
Click to expand...
Click to collapse
Ok , I see mysterious problem ))
Try, remaining unlocked, go back to s-on (you can always take s-off again) and check your recovery (enter and flashing) under s-on.
tash2013 said:
Ok , I see mysterious problem ))
Try, remaining unlocked, go back to s-on (you can always take s-off again) and check your recovery (enter and flashing) under s-on.
Click to expand...
Click to collapse
Is that something I can do with the revone binary? To be honest, I have no idea how to turn security back on. I can relock it and that may be about it.
I stumbled upon another thread, shares a common theme as my issue, but with a different twist. Using a superboot.img as a rooting method instead of flashing it via recovery. It somewhere says that the boot.img needs to be flashed as well, however I can't find a decent boot.img to flash. The superboot tool seems like unproven territory right now.
Here's the other thread, I've leafed through it and found no determinable answer for my particular issue.
http://forum.xda-developers.com/showthread.php?p=39852757#post39852757
Do not apply revone to return s-on!
Use fastboot by "fastboot oem writesecureflag 3".
Be convinced that bootloader is unlocked before return to s-on.
Regarding your issue: I suspect that a certain code in HBOOT tries to install TAMPERED flag when sees custom recovery, but isn't able to do it correctly because s-off (bypassing security) and a certain mistake or exception conducts to reset phone.
Jman12000 said:
Hi -
Thanks for any help in advance. I'm a bit of a rookie round here, I've rooted and flashed my past 3 HTC phones but taken the easy route every time.
But today, I've used ADB commands to flash the revone binary and unlock and get s-off on my HTC one m7. It took me several tries, but it eventually worked (or at least said successful). So my HBOOT 1.44 says UNLOCKED & S-OFF.
So onto the next step. fastboot flash recovery recoverytwrp.img
...
Another success!
So, I reboot into bootloader and prompt recovery boot like I'm about to get HAM on twrp and flash some superuser files. It shows me a developer screen full of red print saying that it's booting into recovery, and then after a while, it just rebooted back into system.
It does this every time. I reflashed the image, I flashed the stock image, I tried the hansoon tool. each time I can't actually get into the recovery.
So this is where I'm stuck. Why can't I get anywhere with this?
Click to expand...
Click to collapse
try to install recovery again
you can download recovery from here
http://www.clockworkmod.com/rommanager
tash2013 said:
Do not apply revone to return s-on!
Use fastboot by "fastboot oem writesecureflag 3".
Be convinced that bootloader is unlocked before return to s-on.
Regarding your issue: I suspect that a certain code in HBOOT tries to install TAMPERED flag when sees custom recovery, but isn't able to do it correctly because s-off (bypassing security) and a certain mistake or exception conducts to reset phone.
Click to expand...
Click to collapse
Code:
C:\Users\Justin\Desktop\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>ad
b reboot bootloader
C:\Users\Justin\Desktop\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>fa
stboot oem writesecureflag 3
...
(bootloader) writesecureflag: partitions siganture pass
OKAY [ 1.665s]
finished. total time: 1.666s
C:\Users\Justin\Desktop\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>fa
stboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.045s]
finished. total time: 0.046s
C:\Users\Justin\Desktop\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>ad
b reboot bootloader
error: device not found
C:\Users\Justin\Desktop\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>ad
b reboot bootloader
So here's where I'm at
Right now I've done all the above, I've got a *** TAMPERED *** and ***UNLOCKED*** and S-ON
I've been through 4 boots, 2 of them attempts to get to recovery. Now instead of recovery rebooting into system, it just shuts off now.
Where do you think I go from here?
I've just skimmed through the posts and didn't see this mentioned
If you are still able to boot into the system, download either GooManager (for TWRP) or RomManager (for CWM) and use either of those apps to install recovery. Once done, you can use the app to boot into recovery instead of the fancy ADB commands or button presses.
Jman12000 said:
So here's where I'm at
Right now I've done all the above, I've got a *** TAMPERED *** and ***UNLOCKED*** and S-ON
I've been through 4 boots, 2 of them attempts to get to recovery. Now instead of recovery rebooting into system, it just shuts off now.
Where do you think I go from here?
Click to expand...
Click to collapse
This topic seems like your problem :
http://forum.xda-developers.com/showthread.php?t=2328983&page=3
The man resolved this by flashing the same recovery many many times.
And more.. Please print here your recovery flashing process
tash2013 said:
This topic seems like your problem :
http://forum.xda-developers.com/showthread.php?t=2328983&page=3
The man resolved this by flashing the same recovery many many times.
And more.. Please print here your recovery flashing process
Click to expand...
Click to collapse
So both that method through ADB shell and GooManager require root. Every rooting method requires recovery, so I don't have perm root yet.
You quoted me, but answered not to me.
Read a post #26 from my link above
Possible Solution
Hello I have the same problem and the solution was:
1. Settings - Energy- Fastboot uncheked
2. Flash Recovery usin one all-in-one-kit
3. Erase Cache 3 times
4. Unplug to PC, and load into system normal
5. Turn off phone - via stock menu NOT FORCE TO OFF pressing the off button
6. Wait 2 minutes, and boot into HBOOT - Power + Volume(-) pressing
7. Choose recovery
Ready.. May these work for you! Let me know
i have updated my htc one to kitkat and i don't want to install a custom recovery but i want to root the device. on my nexus 7 2013 i could boot the custom recovery without flashin using this comman:
./adb boot reco.img
is there a way to do this on the htc one running kit kat? i have tried different recoveries.
./fastboot boot recovery-clockwork-6.0.4.5-m7ul.img
downloading 'boot.img'...
OKAY [ 0.288s]
after that the device is stuck in fastboot mode and i have to force the shutdown. any ideas?
fastboot boot doesn't work on HTC One unfortunately. I've tried even just using different kernel images.
Just flash clockworkmod and get root [i'd toss in an adblocking host file too] and then reboot to fastboot and re-flash your stock recovery.img takes two minutes.
rouvenkutter said:
i have updated my htc one to kitkat and i don't want to install a custom recovery but i want to root the device. on my nexus 7 2013 i could boot the custom recovery without flashin using this comman:
./adb boot reco.img
is there a way to do this on the htc one running kit kat? i have tried different recoveries.
./fastboot boot recovery-clockwork-6.0.4.5-m7ul.img
downloading 'boot.img'...
OKAY [ 0.288s]
after that the device is stuck in fastboot mode and i have to force the shutdown. any ideas?
Click to expand...
Click to collapse
rouvenkutter said:
i have updated my htc one to kitkat and i don't want to install a custom recovery but i want to root the device. on my nexus 7 2013 i could boot the custom recovery without flashin using this comman:
./adb boot reco.img
is there a way to do this on the htc one running kit kat? i have tried different recoveries.
./fastboot boot recovery-clockwork-6.0.4.5-m7ul.img
downloading 'boot.img'...
OKAY [ 0.288s]
after that the device is stuck in fastboot mode and i have to force the shutdown. any ideas?
Click to expand...
Click to collapse
ipfreelytech said:
fastboot boot doesn't work on HTC One unfortunately. I've tried even just using different kernel images.
Just flash clockworkmod and get root [i'd toss in an adblocking host file too] and then reboot to fastboot and re-flash your stock recovery.img takes two minutes.
Click to expand...
Click to collapse
"fastboot boot recovery.img" does work, BUT only on hboot 1.44
nkk71 said:
"fastboot boot recovery.img" does work, BUT only on hboot 1.44
Click to expand...
Click to collapse
that explains it. i was on hboot 1.44 up until two days ago when i flashed kit kat.
ipfreelytech said:
fastboot boot doesn't work on HTC One unfortunately. I've tried even just using different kernel images.
Just flash clockworkmod and get root [i'd toss in an adblocking host file too] and then reboot to fastboot and re-flash your stock recovery.img takes two minutes.
Click to expand...
Click to collapse
thanks, i'm doing it like this right now.
That explains it. I've never had hboot 1.44 on my One. It's such a useful feature, sucks that HTC removed it.
nkk71 said:
"fastboot boot recovery.img" does work, BUT only on hboot 1.44
Click to expand...
Click to collapse
ipfreelytech said:
That explains it. I've never had hboot 1.44 on my One. It's such a useful feature, sucks that HTC removed it.
Click to expand...
Click to collapse
not sure they removed it on purpose, someone disassembled the code and it looks like they used a bad memcpy command, so whether it was intentional or not is unclear.
I was following Vomer's guide on my One, which has been working great. I had HBOOT 1.54, S-Off, SuperCID, and pushed the firmware twice, got the success message, and waited and when it says finished used adb to tell it to reboot. Now I get the splash, with the lock gone, as expected, and then the screen goes black. If I hold power, or power and down, the hardware keys start blinking and then nothing. A few seconds later I get the splash again, then blank again.
It appears to be communicating briefly over USB because my laptop starts trying to install a HTC MTP device (drive is already on the PC and has been fine) before it looses comms and drops out. I can't seem to get adb device to recognize it....
PLEASE tell me someone can help me recover my phone!!! I will be immensely grateful.
And what the HBOOT version you wanted to downgrade to?
Ivanovic said:
And what the HBOOT version you wanted to downgrade to?
Click to expand...
Click to collapse
I wasn't trying to downgrade HBOOT, just rather ensure my firmware was up to date. I'd had mine set up as a GPE and was flashing the DE (after supercid).
By way of an update, I've been able to get into bootloader and I'm a bit scared on what to do next so I dont screw this up. I notice that I still have S-OFF, but HBOOT is now showing 1.56 and it says RELOCKED at the top. My plan was to use rumrunner (just because of the HBOOT, but it is erroring anyway) to unlock bootloader, and then to look up the fastboot commands to push a ROM and recovery. Any advice?
Downgrade to 1.44 and change cid according to the Rom you want. Then unlock or set your bootloader to LOCKED
Here is the file for 1.44 http://www69.zippyshare.com/v/95229262/file.html
Sent from my HTC One using Tapatalk
Can you help me with the adb commands to flash that boot zip? Also, should I run " fastboot flash unlocktoken Unlock_code.bin" to unlock my bootloader first?
vettejock99 said:
Can you help me with the adb commands to flash that boot zip? Also, should I run " fastboot flash unlocktoken Unlock_code.bin" to unlock my bootloader first?
Click to expand...
Click to collapse
You can unlock if you want to flash custom recovery.
Place the file i gave you to the fastboot folder. Boot into bootloader and choose FASTBOOT.
Run the following : fastboot oem rebootRUU
fastboot flash zip filename.zip *where filaname the actual filename of the file i gave you
You will get FAILED or sth so do this command again to succesfully flash the firmware.
Ivanovic said:
You can unlock if you want to flash custom recovery.
Place the file i gave you to the fastboot folder. Boot into bootloader and choose FASTBOOT.
Run the following : fastboot oem rebootRUU
fastboot flash zip filename.zip *where filaname the actual filename of the file i gave you
You will get FAILED or sth so do this command again to succesfully flash the firmware.
Click to expand...
Click to collapse
Awesome. So I've got HBOOT 1.44, S-OFF, bootloader unlocked, supercid, and TWRP 2.6.3.3 flashed again, and I tried sideloading ARHD rom. It all looked good but same thing for the moment, I get the splash and then black......I can't figure out why I can't boot into a rom right now. About to try flashing ROM again.
Okay, so didnt' work. After sideload flashing gets to 100% it just does nothing. Manually rebooting gets me back into the splash then blackness bootloop......
Can you issue fastboot clear cache in bootloader and see the outcome?
Also as you are Soff, you can run dev ruu
SaHiLzZ said:
Can you issue fastboot clear cache in bootloader and see the outcome?
Also as you are Soff, you can run dev ruu
Click to expand...
Click to collapse
The former didn't get me anywhere, but I did follow your thinking and decided to use the RUU and start over. I'm happy to report that got me going, and then I was able to get AR HD on. I probably had to do that all along once I wiped the ROM and recovery, as sideloading clearly wasn't going to work (in retrospect) as it has an AROMA installer.
Thanks so much everyone!!
SaHiLzZ said:
Can you issue fastboot clear cache in bootloader and see the outcome?
Also as you are Soff, you can run dev ruu
Click to expand...
Click to collapse
Nice that everything is solved now.
Verstuurd van mijn HTC One
First of all I would like to apologize if I posted this in the wrong forum or section. I just registered this account to ask for help regarding my bricked HTC One (m7ul). I am not a newbie to XDA as I have visited this site more than once to learn the fundamentals of rooting android phone and so on. I unlocked my bootloader via HTCDev and rooted it using CWM Touch Recovery 6.0.4.5. 3 weeks ago I flashed my HTC One to Probam (AOSB) custom rom, no problems were present, everything ran smoothly and perfectly. Then, 2 weeks ago, I decided to flash ElementalX kernel, being ignorant on purpose to the fact that it was meant for Sense Roms. Upom completion through Aroma Installer, I selected reboot system in recovery. Upon exit, the recovery told me that my phone could have possibly lost its root access and prompted me to root it so i just agreed. There came the problem upon reboot, I could not boot into my OS and I was stuck on the HTC screen. (May I add that I bought my HTC this year March. I S-offed it via Firewater as my Hboot version was 1.56 and Rumrunner couldn't help me S-Off. Advice for those who have hboot versions higher than 1.55 and want to S-off, Firewater is my suggestion. Just make sure you follow the guid also here on XDA forums accurately and I assure you can get s-off) As I was saying, as soon as that happened, I looked for solutions. I tried hasson 2000 all in one toolkit, I tried relocking my bootloader and runming RUU.exe file to return to stock firmware, I tried sideloading a rom in recovery, I tried mounting usb storage to copy a .zip rom into my internal storage but nothing happened. I tried flashing directly via fastboot but the cmd keep saying it couldnt run the file. I couldn't enter adb as the recovery said there is no os present. I really have no more idea what else I can do and I think I've tried just about everything. Please help as it's been 2 weeks into the brick and I'm really desperate. Please help
CID: HTC_044
Hboot:1.56
If there is more information needed please ask as I'm really desperate to fix my phone :C
boksquare said:
First of all I would like to apologize if I posted this in the wrong forum or section. I just registered this account to ask for help regarding my bricked HTC One (m7ul). I am not a newbie to XDA as I have visited this site more than once to learn the fundamentals of rooting android phone and so on. I unlocked my bootloader via HTCDev and rooted it using CWM Touch Recovery 6.0.4.5. 3 weeks ago I flashed my HTC One to Probam (AOSB) custom rom, no problems were present, everything ran smoothly and perfectly. Then, 2 weeks ago, I decided to flash ElementalX kernel, being ignorant on purpose to the fact that it was meant for Sense Roms. Upom completion through Aroma Installer, I selected reboot system in recovery. Upon exit, the recovery told me that my phone could have possibly lost its root access and prompted me to root it so i just agreed. There came the problem upon reboot, I could not boot into my OS and I was stuck on the HTC screen. (May I add that I bought my HTC this year March. I S-offed it via Firewater as my Hboot version was 1.56 and Rumrunner couldn't help me S-Off. Advice for those who have hboot versions higher than 1.55 and want to S-off, Firewater is my suggestion. Just make sure you follow the guid also here on XDA forums accurately and I assure you can get s-off) As I was saying, as soon as that happened, I looked for solutions. I tried hasson 2000 all in one toolkit, I tried relocking my bootloader and runming RUU.exe file to return to stock firmware, I tried sideloading a rom in recovery, I tried mounting usb storage to copy a .zip rom into my internal storage but nothing happened. I tried flashing directly via fastboot but the cmd keep saying it couldnt run the file. I couldn't enter adb as the recovery said there is no os present. I really have no more idea what else I can do and I think I've tried just about everything. Please help as it's been 2 weeks into the brick and I'm really desperate. Please help
CID: HTC_044
Hboot:1.56
If there is more information needed please ask as I'm really desperate to fix my phone :C
Click to expand...
Click to collapse
you do realize what you posted is not readable... right? sorry, but i sort of tried reading it, but
break it down into smaller parts.
nkk71 said:
you do realize what you posted is not readable... right? sorry, but i sort of tried reading it, but
break it down into smaller parts.
Click to expand...
Click to collapse
he flashed a sense kernel to an aosp rom and is in bootloop as near as i can tell
he's s-off hboot 1.56 and needs a RUU I assume
boksquare said:
(...)
I unlocked my bootloader via HTCDev and rooted it using CWM Touch Recovery 6.0.4.5.
(...)
I flashed my HTC One to Probam (AOSB) custom rom, no problems were present,
(...)
I decided to flash ElementalX kernel, being ignorant on purpose to the fact that it was meant for Sense Roms.
(...)
I could not boot into my OS and I was stuck on the HTC screen.
(...)
I S-offed it via Firewater
(...)
Click to expand...
Click to collapse
Did you tried to flash an AOSP compatible kernel after you realized you couldn't boot the phone?
boksquare said:
I tried hasson 2000 all in one toolkit
Click to expand...
Click to collapse
You should use fastboot and adb from cmd prompt instead of toolkit.
boksquare said:
I tried relocking my bootloader and runming RUU.exe file to return to stock firmware,
Click to expand...
Click to collapse
Re-locking bootloader to run a ruu.exe is not required when you have S-OFF. Anyway what was the error code when the RUU exe failed? And what was the ruu version?
boksquare said:
I tried sideloading a rom in recovery
Click to expand...
Click to collapse
What happened? What was the error? What rom?
boksquare said:
I tried mounting usb storage to copy a .zip rom into my internal storage but nothing happened.
Click to expand...
Click to collapse
If you can mount your usb storage with your rom.zip on it, you don't need to copy it to your sdcard! Just install the rom from your mounted usb storage... You said ''nothing happened'' Was there any error code?
boksquare said:
I tried flashing directly via fastboot but the cmd keep saying it couldnt run the file.
Click to expand...
Click to collapse
Wait?! You can't flash a rom.zip from fastboot, only from custom recovery. The only thing you can flash from fastboot is a recovery or a ruu/firmware from fastboot RUU mode.
boksquare said:
I couldn't enter adb as the recovery said there is no os present.
Click to expand...
Click to collapse
ADB should work from custom recovery even if you don't have an OS installed.
boksquare said:
(...)
CID: HTC_044
Hboot:1.56
Click to expand...
Click to collapse
post the output of ''fastboot getvar all'' except IMEI. With S-OFF it should be quite easy to make your phone boot again...
clsA said:
he flashed a sense kernel to an aosp rom and is in bootloop as near as i can tell
he's s-off hboot 1.56 and needs a RUU I assume
Click to expand...
Click to collapse
still... if (yes IF) i learned anything in school "run-on" sentences are a NO-NO!! (and i'm not even talking about english schools)
alray said:
Did you tried to flash an AOSP compatible kernel after you realized you couldn't boot the phone?
Click to expand...
Click to collapse
- No, I downloaded and flashed the kernel on my One while I was outstation, so I couldn't do anything when it was stuck on bootloop.
You should use fastboot and adb from cmd prompt instead of toolkit.
Click to expand...
Click to collapse
-I couldn't get into adb through fastboot with the command on cmd "adb reboot bootloader" (attachment below [capture])
Re-locking bootloader to run a ruu.exe is not required when you have S-OFF. Anyway what was the error code when the RUU exe failed? And what was the ruu version?
Click to expand...
Click to collapse
-That's the problem, there was no error code or anything, it just didn't work, nothing happened. [Capture3]
What happened? What was the error? What rom?
Click to expand...
Click to collapse
-It said device not found. [Capture1]
If you can mount your usb storage with your rom.zip on it, you don't need to copy it to your sdcard! Just install the rom from your mounted usb storage... You said ''nothing happened'' Was there any error code?
Click to expand...
Click to collapse
- I believe you and I have a different understanding of usb storage which obviously I'm misinformed. I thought USB Storage is just mounting your CPU storage to your phone.
ADB should work from custom recovery even if you don't have an OS installed.
Click to expand...
Click to collapse
-Not sure, nothing worked.
post the output of ''fastboot getvar all'' except IMEI. With S-OFF it should be quite easy to make your phone boot again...
Click to expand...
Click to collapse
-Capture2 below.
Again I apologize for any inconvenience caused, I'm still new to using XDA forums instead of just reading it for info, thanks and please reply ASAP, desperate and losing hope
boksquare said:
-It said device not found. [Capture1]
Click to expand...
Click to collapse
check you check FAQ #2 in my guide (forget the guide, just the FAQ#2) http://forum.xda-developers.com/showthread.php?t=2541082
nkk71 said:
check you check FAQ #2 in my guide (forget the guide, just the FAQ#2) http://forum.xda-developers.com/showthread.php?t=2541082
Click to expand...
Click to collapse
The problem is, my phone won't even show up in my computer, I've no idea why.
nkk71 said:
check you check FAQ #2 in my guide (forget the guide, just the FAQ#2) http://forum.xda-developers.com/showthread.php?t=2541082
Click to expand...
Click to collapse
I would like to try your method for using the RUU.exe through downgrading hboot all those, but if I downgraded my hboot and everything, and the RUU.exe doesn't work, will my phone go beyond saving? Please advice.
boksquare said:
I would like to try your method for using the RUU.exe through downgrading hboot all those, but if I downgraded my hboot and everything, and the RUU.exe doesn't work, will my phone go beyond saving? Please advice.
Click to expand...
Click to collapse
i think you're rushing things, but since you're s-off, go for ruu.zip method, shows much more information, but beware Win8.1 as mentioned in the FAQs.
(also there's no need to LOCK since you're s-off, and dont even think about S-On, the guide was meant as return to stock for warranty.
i'm sure you can Device Manager fixed, it's probably somewhere there, just needs corrected/updated drivers, and by the way, don't use TWRP 2.7.0.0 it has problems with adb.
nkk71 said:
i think you're rushing things, but since you're s-off, go for ruu.zip method, shows much more information, but beware Win8.1 as mentioned in the FAQs.
(also there's no need to LOCK since you're s-off, and dont even think about S-On, the guide was meant as return to stock for warranty.
i'm sure you can Device Manager fixed, it's probably somewhere there, just needs corrected/updated drivers, and by the way, don't use TWRP 2.7.0.0 it has problems with adb.
Click to expand...
Click to collapse
Okay, I will get to it right away, but before that, I was using CWM Touch 6.0.4.5 but I still can't get adb in cmd. Once I've entered recovery I will automatically find adb through "adb devices" command without having to do anything special? And do I need to remove tampered all those before running RUU.Zip? Or is it just for going back to stock? I am sorry, as there are just a lot of things I'm not clear about or understand. Please advice :/
boksquare said:
I was using CWM Touch 6.0.4.5 but I still can't get adb in cmd. Once I've entered recovery I will automatically find adb through "adb devices" command without having to do anything special?
Click to expand...
Click to collapse
if adb devices doesn't list your device, then you have to check Windows Device Manager and fix the driver problems.
boksquare said:
And do I need to remove tampered all those before running RUU.Zip? Or is it just for going back to stock?
Click to expand...
Click to collapse
You can leave everything as is, tampered doesn't matter in any case, and unlocked won't matter with S-OFF.
DO NOT GO S-ON.
boksquare said:
I am sorry, as there are just a lot of things I'm not clear about or understand. Please advice :/
Click to expand...
Click to collapse
No problem, better to ask before, otherwise you could end up in a worse situation.
But still don't understand why want to go all the trouble of ruu. can you explain (briefly, not a huge paragraph :angel
By the way, if you're stuck in a bootloop because you were flashing a 4.4 ROM using CWM 6.0.4.5, then that would be the problem, you need TWRP 2.6.3.3 or higher.
nkk71 said:
if adb devices doesn't list your device, then you have to check Windows Device Manager and fix the driver problems.
You can leave everything as is, tampered doesn't matter in any case, and unlocked won't matter with S-OFF.
DO NOT GO S-ON.
No problem, better to ask before, otherwise you could end up in a worse situation.
But still don't understand why want to go all the trouble of ruu. can you explain (briefly, not a huge paragraph :angel
By the way, if you're stuck in a bootloop because you were flashing a 4.4 ROM using CWM 6.0.4.5, then that would be the problem, you need TWRP 2.6.3.3 or higher.
Click to expand...
Click to collapse
Don't worry I won't enter S-On.
But before the brick there were no problems with the drivers as I had installed HTC Sync Drivers. After the brick my phone just couldn't be detected in my computer. I just assumed this problem is linked with the brick.
Because I have no idea what other methods can save my phone, please advice if there are other methods beside RUU
boksquare said:
Don't worry I won't enter S-On.
But before the brick there were no problems with the drivers as I had installed HTC Sync Drivers. After the brick my phone just couldn't be detected in my computer. I just assumed this problem is linked with the brick.
Because I have no idea what other methods can save my phone, please advice if there are other methods beside RUU
Click to expand...
Click to collapse
So after reading your first post i see you tried flashing a 4.4 rom using CWM 6.0.4.5, so
get TWRP from:
2.6.3.3: http://techerrata.com/browse/twrp2/m7
or 2.6.3.4: http://techerrata.com/browse/twrp2/m7ul
(make sure MD5 is correct, that site does not play nice with download managers)
in bootloader/FASTBOOT USB:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then install the ROM again.
nkk71 said:
So after reading your first post i see you tried flashing a 4.4 rom using CWM 6.0.4.5, so
get TWRP from:
2.6.3.3: http://techerrata.com/browse/twrp2/m7
or 2.6.3.4: http://techerrata.com/browse/twrp2/m7ul
(make sure MD5 is correct, that site does not play nice with download managers)
in bootloader/FASTBOOT USB:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then install the ROM again.
Click to expand...
Click to collapse
But the ROM is not in my Htc, how do I move it there? I had no way of moving it there that's why I went for the RUU
boksquare said:
But the ROM is not in my Htc, how do I move it there? I had no way of moving it there that's why I went for the RUU
Click to expand...
Click to collapse
you have 3 choices to get the ROM onto your phone (once you have custom recovery):
1- OTG cable
2- adb sideload
3- adb push
If you don't have OTG cable, I personally like adb push (example below), though many like adb sideload (plenty of guides and how tos around).
Code:
C:\ADB3>[B][COLOR="Blue"]adb version[/COLOR][/B]
Android Debug Bridge version 1.0.31
C:\ADB3>[B][COLOR="Blue"]fastboot devices[/COLOR][/B]
HT34xxxxxxxx fastboot [I][SIZE="1"]<- you are in bootloader[/SIZE][/I]
C:\ADB3>[B][COLOR="Blue"]fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img[/COLOR][/B]
target reported max download size of 1514139648 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.209s]
writing 'recovery'...
OKAY [ 1.144s]
finished. total time: 2.354s
C:\ADB3>[B][COLOR="Blue"]fastboot erase cache[/COLOR][/B]
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.120s]
finished. total time: 0.120s
C:\ADB3>[B][COLOR="Blue"]fastboot reboot-bootloader[/COLOR][/B]
rebooting into bootloader...
OKAY [ 0.160s]
finished. total time: 0.160s
-> enter RECOVERY
Code:
C:\ADB3>[B][COLOR="Blue"]adb devices[/COLOR][/B]
List of devices attached
HT34xxxxxxxx recovery [I][SIZE="1"]<- you are now in recovery[/SIZE][/I]
C:\ADB3>[B][COLOR="Blue"]adb push Android_Revolution_HD-One_52.0.zip /sdcard/[/COLOR][/B]
2990 KB/s (1172224138 bytes in 382.835s) [B][I]<- yes, it took over 5 mins,
without showing any progress[/I][/B]
[I][U][SIZE="1"]Just to double-check the file is not corrupt[/SIZE][/U][/I]
C:\ADB3>[B][COLOR="Blue"]adb shell md5sum /sdcard/Android_Revolution_HD-One_52.0.zip[/COLOR][/B]
2eff0d37fec5789b946c43f7da2c13bf /sdcard/Android_Revolution_HD-One_52.0.zip
[INDENT]from the OP:
Android Revolution HD 52.0 -- MD5 sum: 2EFF0D37FEC5789B946C43F7DA2C13BF --
==> so all is good :)[/INDENT]
C:\ADB3>
-> in recovery, select "install" and install the ROM
.
nkk71 said:
you have 3 choices to get the ROM onto your phone (once you have custom recovery):
1- OTG cable
2- adb sideload
3- adb push
If you don't have OTG cable, I personally like adb push (example below), though many like adb sideload (plenty of guides and how tos around).
Code:
C:\ADB3>[B][COLOR="Blue"]adb version[/COLOR][/B]
Android Debug Bridge version 1.0.31
C:\ADB3>[B][COLOR="Blue"]fastboot devices[/COLOR][/B]
HT34xxxxxxxx fastboot [I][SIZE="1"]<- you are in bootloader[/SIZE][/I]
C:\ADB3>[B][COLOR="Blue"]fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img[/COLOR][/B]
target reported max download size of 1514139648 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.209s]
writing 'recovery'...
OKAY [ 1.144s]
finished. total time: 2.354s
C:\ADB3>[B][COLOR="Blue"]fastboot erase cache[/COLOR][/B]
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.120s]
finished. total time: 0.120s
C:\ADB3>[B][COLOR="Blue"]fastboot reboot-bootloader[/COLOR][/B]
rebooting into bootloader...
OKAY [ 0.160s]
finished. total time: 0.160s
-> enter RECOVERY
Code:
C:\ADB3>[B][COLOR="Blue"]adb devices[/COLOR][/B]
List of devices attached
HT34xxxxxxxx recovery [I][SIZE="1"]<- you are now in recovery[/SIZE][/I]
C:\ADB3>[B][COLOR="Blue"]adb push Android_Revolution_HD-One_52.0.zip /sdcard/[/COLOR][/B]
2990 KB/s (1172224138 bytes in 382.835s) [B][I]<- yes, it took over 5 mins,
without showing any progress[/I][/B]
[I][U][SIZE="1"]Just to double-check the file is not corrupt[/SIZE][/U][/I]
C:\ADB3>[B][COLOR="Blue"]adb shell md5sum /sdcard/Android_Revolution_HD-One_52.0.zip[/COLOR][/B]
2eff0d37fec5789b946c43f7da2c13bf /sdcard/Android_Revolution_HD-One_52.0.zip
[INDENT]from the OP:
Android Revolution HD 52.0 -- MD5 sum: 2EFF0D37FEC5789B946C43F7DA2C13BF --
==> so all is good :)[/INDENT]
C:\ADB3>
-> in recovery, select "install" and install the ROM
.
Click to expand...
Click to collapse
Okay, I'm downloading the drivers after checking the device manager. You were right, the drivers were gone. I had no idea why. I installed Sync Manager before with all the drivers present, no idea why is it gone now.
Still, once the download is finished I will do as you said and will update you ASAP. Thanks in advance. :good::laugh:
boksquare said:
Okay, I'm downloading the drivers after checking the device manager. You were right, the drivers were gone. I had no idea why. I installed Sync Manager before with all the drivers present, no idea why is it gone now.
Still, once the download is finished I will do as you said and will update you ASAP. Thanks in advance. :good::laugh:
Click to expand...
Click to collapse
No problem, good luck
nkk71 said:
No problem, good luck
Click to expand...
Click to collapse
OMG OMG OMG OMG OMG OMG OMG OMG OMG !!!! It worked !!!! At first I was disappointed as I couldn't fix my drivers by reinstalling HTC Sync Manager. I was going to ask you but I took a look back into your guide at FAQ #2 and followed it exactly and I got it reinstalled )))) I pushed the ROM in and flashed in Recovery and I just booted my phone ! Thanks for all your time and advices, really appreciated it. How I wish I could thank you in person or something. Thanks man, really thanks a lot
boksquare said:
OMG OMG OMG OMG OMG OMG OMG OMG OMG !!!! It worked !!!! At first I was disappointed as I couldn't fix my drivers by reinstalling HTC Sync Manager. I was going to ask you but I took a look back into your guide at FAQ #2 and followed it exactly and I got it reinstalled )))) I pushed the ROM in and flashed in Recovery and I just booted my phone ! Thanks for all your time and advices, really appreciated it. How I wish I could thank you in person or something. Thanks man, really thanks a lot
Click to expand...
Click to collapse
My pleasure glad everything worked out, and xda has a nice little thanks button that you can press when a post is useful
and if you could also edit the main thread title to include [SOLVED] (go to 1st post click EDIT, at the bottom of the edit window click GO ADVANCED, then you can edit the main title), thanks
Hi. I have been searching for two days on how to restore my phone to a stock Rom. I flashed some lame Rom that I can't remember the name of (has a blue firebird boot screen...) and now that's the only Rom I can flash. I tried many rims but haven't had any luck. I know the lame Rom I flashed made me first flash a boot image. I trtried reflashing a stock boot image but it doesn't help. The stock roms succeed but stay stuck on the lock screen totally unresponsive except for the power button to hard reset... I'm trying to get S-Off with FireWire but it fails saying that it cannot s-Off my device. Cannot RUU since I'm s-on and have no clue what to do.
The boot loader reads that the O.S. is version 4.19.531.10 but I currently have no O.S. installed since I wiped.
The boot loader is version 1.56 and it's a T-Mobile USA version.
ADB Sideload works but the install is faulty as described.
Thanks.
OfficialLocdoGg said:
Hi. I have been searching for two days on how to restore my phone to a stock Rom. I flashed some lame Rom that I can't remember the name of (has a blue firebird boot screen...) and now that's the only Rom I can flash. I tried many rims but haven't had any luck. I know the lame Rom I flashed made me first flash a boot image. I trtried reflashing a stock boot image but it doesn't help. The stock roms succeed but stay stuck on the lock screen totally unresponsive except for the power button to hard reset... I'm trying to get S-Off with FireWire but it fails saying that it cannot s-Off my device. Cannot RUU since I'm s-on and have no clue what to do.
The boot loader reads that the O.S. is version 4.19.531.10 but I currently have no O.S. installed since I wiped.
The boot loader is version 1.56 and it's a T-Mobile USA version.
ADB Sideload works but the install is faulty as described.
Thanks.
Click to expand...
Click to collapse
update your recovery to 2.6.3.3 and flash your rom again.
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
you can also use the latest RUU.exe which will restore your phone back to stock and updated to the latest version. (better option imo)
http://www.htc1guru.com/dld/ruu_m7_..._10-33e-1718-01l_release_387953_signed_2-exe/
I'm going to try to update the recovery first because when I try to relock the bootloader even after flashing stock recovery it just boots to the bootloader even with a rom installed. (Even if its the erroring stock rom)
alray said:
update your recovery to 2.6.3.3 and flash your rom again.
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
you can also use the latest RUU.exe which will restore your phone back to stock and updated to the latest version. (better option imo)
http://www.htc1guru.com/dld/ruu_m7_..._10-33e-1718-01l_release_387953_signed_2-exe/
Click to expand...
Click to collapse
OfficialLocdoGg said:
I'm going to try to update the recovery first because when I try to relock the bootloader even after flashing stock recovery it just boots to the bootloader even with a rom installed. (Even if its the erroring stock rom)
Click to expand...
Click to collapse
its fine to flash a ruu with phone booted in bootloader btw.
alray said:
its fine to flash a ruu with phone booted in bootloader btw.
Click to expand...
Click to collapse
Okay well I'm having no luck. Trying to flash the RUU wont work and updating the recovery didn't work. The ruu just hangs at 5% Checking headers. I tried extracting the rom.zip from the ruu but I get the invalid size crap and when trying to open the rom.zip it gives me an invalid error. I don't know what to do here.
OfficialLocdoGg said:
Okay well I'm having no luck. Trying to flash the RUU wont work and updating the recovery didn't work. The ruu just hangs at 5% Checking headers. I tried extracting the rom.zip from the ruu but I get the invalid size crap and when trying to open the rom.zip it gives me an invalid error. I don't know what to do here.
Click to expand...
Click to collapse
Let try this using the version just above your base version:
Download, rename to firmware.zip and place in your adb/fastboot folder: firmware 5.14.531.1
Boot into bootloader/FASTBOOT USB
Type:
Code:
[B][I]fastboot oem lock[/I][/B]
Type:
Code:
[B][I]fastboot oem rebootRUU [/I][/B]
NOTE: You should see a silver HTC logo come up on your phone after executing this command.
NOTE: if this command freezes, just disconnect the USB cable and hold the power and volume down buttons until the device reboots. Then, repeat the steps above again.
Finally:
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
Repeat the same command: IMPORTANT
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
NOTE: The green bar on the phone may not go to 100% of the bar ... but If you see completed on your computer command window, wait for a few seconds and move on.
Last Step:
Code:
[B][I]fastboot reboot[/I][/B]
Click to expand...
Click to collapse
Now run this RUU 5.14.531.1
If this is successful you can try to achieve S-OFF with firewater. Of course, you will need to unlock your bootloader and install TWRP 2.6.3.3 recovery. Or, you can retry the RUU in alray's post.
majmoz said:
Let try this using the version just above your base version:
Download, rename to firmware.zip and place in your adb/fastboot folder: firmware 5.14.531.1
Now run this RUU 5.14.531.1
If this is successful you can try to achieve S-OFF with firewater. Of course, you will need to unlock your bootloader and install TWRP 2.6.3.3 recovery. Or, you can retry the RUU in alray's post.
Click to expand...
Click to collapse
Thanks. This restored the phone to a usable state. I'm going to try firewater now.