Hey there.
Had a hard time getting my HTC One from S-off to stock o2 Germany (O2___102). After several ours of problems i finally had my phone got working again. It booted up, with the O2 nand backup and stock recovery and it gave me an OTA notification. Was happy like a little kit. Then I started it.
So now thats the problem. It started, but it got stuck in the middle. I cannot do anything, neither power it off nor restarting. Its a mess. What can i do. Is there a special button combo? Wait until battery is fully drained? But what comes after that....
PLS HELP!
CarlosCalderon said:
Hey there.
Had a hard time getting my HTC One from S-off to stock o2 Germany (O2___102). After several ours of problems i finally had my phone got working again. It booted up, with the O2 nand backup and stock recovery and it gave me an OTA notification. Was happy like a little kit. Then I started it.
So now thats the problem. It started, but it got stuck in the middle. I cannot do anything, neither power it off nor restarting. Its a mess. What can i do. Is there a special button combo? Wait until battery is fully drained? But what comes after that....
PLS HELP!
Click to expand...
Click to collapse
Not sure I understand you correctly, but to reboot:
press and hold POWER + VOLDOWN (under a bright light, I'm not kidding!!), when it reboots (about 20 to 30 seconds), let go of POWER but keep holding VOLDOWN, that will get you to bootloader.
(if it doesnt work the first time, try again, sometimes takes me 2 to 3 times to get it working, and remember the bright light is important!!)
Bright light?! You mean under a lamp? Sounds really curious...
Anyway... An update: have been to work and I just left it updating. Battery went low and the phone turned off. Now that I'm back I charged it a bit and the phone turned on and resumed updating. After it had finished, the phone turned itself immediately off. Now it's just black and when I'm trying to turn it on only the capacitive buttons flashes. That's it... Maybe the battery is still too low.
I'm going to sleep now and hope tomorrow there will be hope for my one... But I think it's hard bricked...
Gesendet von meinem Nexus 7 mit Tapatalk
Why would it be hard bricked? Why did you go from S-off to stock when you can have the latest release and update the firmware with S-off anyway? Can you, as asked already, boot into bootloader or not?
Sent from my HTC One
nkk71 said:
(under a bright light, I'm not kidding!!), when it reboots (about 20 to 30 seconds), remember the bright light is important!!)
Click to expand...
Click to collapse
You're the man. This is how I turned it back to life again, after nothing works anymore... Bright light?! Why does it works.... Like magic, but its definitetly weird
CarlosCalderon said:
You're the man. This is how I turned it back to life again, after nothing works anymore... Bright light?! Why does it works.... Like magic, but its definitetly weird
Click to expand...
Click to collapse
The light sensor thingy is no joke, told you I wasn't kidding
I believe it's to avoid reboots, if the phone is in your pocket (for example).
I had to use a kitchen lamp.... So pretty light. Otherwise it didn't work... But now I feel so lucky, I will try the other OTA files also
We will see. Thank you so much!
Last issue to fix this thing.
I'm now fully stock on o2___102 CID. Last thing I have to do is, to lock und remone S-OFF. So I used revone. But I think I need Root. Can i have root without touching the recovery and leave anything stock? How can i remove revone and root afterwards?
Please, help me the last time to fix this beast
CarlosCalderon said:
I had to use a kitchen lamp.... So pretty light. Otherwise it didn't work... But now I feel so lucky, I will try the other OTA files also
We will see. Thank you so much!
Click to expand...
Click to collapse
The bathroom seems a popular place too :silly:
CarlosCalderon said:
Last issue to fix this thing.
I'm now fully stock on o2___102 CID. Last thing I have to do is, to lock und remone S-OFF. So I used revone. But I think I need Root. Can i have root without touching the recovery and leave anything stock? How can i remove revone and root afterwards?
Click to expand...
Click to collapse
can you rephrase, i didnt understand, you want to use revone to S-Off? or you want to lock and remove revone and S-On?? ... careful!!
Please explain in more detail (what, how, and why) you're doing this, thanks
No problem Thanks first for your help.
I have to send the phone in under warranty. At the moment the phone is ***UNLOCKED*** and S-off with stock Germany O2 Firmware (O2___102).
What do I want to do? Get rid of S-Off and the UNLOCKED status. So I tried to push revone via adb push revone /data/local/tmp/
Then I did:
adb shell
cd /data/local/tmp
chmod 755 revone <---This does not work without root, so revone basicly does not work. Now I'm trying to root the phone, without touching anything else, because I'm so happy that it does work right now. So, is there a way to grant root, without touching hboot, recovery, firmware and rom?!
Thank you!
CarlosCalderon said:
No problem Thanks first for your help.
I have to send the phone in under warranty. At the moment the phone is ***UNLOCKED*** and S-off with stock Germany O2 Firmware (O2___102).
What do I want to do? Get rid of S-Off and the UNLOCKED status. So I tried to push revone via adb push revone /data/local/tmp/
Then I did:
adb shell
cd /data/local/tmp
chmod 755 revone <---This does not work without root, so revone basicly does not work. Now I'm trying to root the phone, without touching anything else, because I'm so happy that it does work right now. So, is there a way to grant root, without touching hboot, recovery, firmware and rom?!
Thank you!
Click to expand...
Click to collapse
ah warranty, please check my guide: http://forum.xda-developers.com/showthread.php?t=2541082
This will return to 100% stock (including S-On if YOU choose), but has to be done in exactly in the order I mentioned in the guide, to avoid possible problems.
If you have questions, please feel free to ask
That does not help me.... Because I dont have a fitting recovery for this o2___102 CID. Its everything finished... If I remove unlocked and tempered with the guru method, i need a custom recovery. But i see no way to flash it back to stock... Can you understand, where my problem is? my CID is pretty screwed
CarlosCalderon said:
That does not help me.... Because I dont have a fitting recovery for this o2___102 CID. Its everything finished... If I remove unlocked and tempered with the guru method, i need a custom recovery. But i see no way to flash it back to stock... Can you understand, where my problem is? my CID is pretty screwed
Click to expand...
Click to collapse
A) you just need a stock recovery "close" to your version, http://forum.xda-developers.com/showthread.php?t=2463387
during the 1st OTA update, the stock recovery may get stuck once (possibly twice), perfectly normal, it's cause the "reboot" command isn't able to do it correctly, so you manually reboot (as mentioned above) to let it reboot back to stock recovery and continue it's update.
(possibly twice)
or
B) do you have the 1st OTA file? if so you can extract stock recovery from it.
==> once the first OTA is applied successfully, everything will be 100% stock (including stock recovery for your CID)
I'm starting to hate this phone...why is this so freakin difficult. In your guide you are saying boot a recovery img: fastboot boot CWM.img
but this will just freeze the phone again What a surprise. Too bad i'm on the newest version from o2...
So what is close to stock recovery? My software number is 3.62.206.1...
CarlosCalderon said:
I'm starting to hate this phone...why is this so freakin difficult. In your guide you are saying boot a recovery img: fastboot boot CWM.img
but this will just freeze the phone again What a surprise. Too bad i'm on the newest version from o2...
So what is close to stock recovery? My software number is 3.62.206.1...
Click to expand...
Click to collapse
1- Do you intend on going S-On? If yes, then just for info, this is what is likely going to happen:
you do the S-Off to S-On command, after a few reboots, your phone will say "tamper detected - rebooting" and TAMPERED is back in bootloader.
I cannot confirm this to be 100% of all cases, but it has happened more than a few times, trust me.
2- closest recovery for 3.62.206.1, I would say 3.62.401.1 (unless you can find the OTA file)
3- "fastboot boot <name of recovery>.img" will only work on hboot 1.44
My guide was written in a very specific order, with very specific commands, versions, etc. to avoid any potential problems.
There are always multiple ways of doing things, depending on you situation, and you're free to do it any which way you like.
Good luck
I restarted from the scratch and used your guide. Everything's prefect, locked, removed tempered. But after the first ota it got stuck again. 2 times. The first time I managed it to reboot. After the second is black.
At the moment not even light can turn it on... You have a special trick again?
Gesendet von meinem Nexus 5 mit Tapatalk
CarlosCalderon said:
I restarted from the scratch and used your guide. Everything's prefect, locked, removed tempered. But after the first ota it got stuck again. 2 times. The first time I managed it to reboot. After the second is black.
At the moment not even light can turn it on... You have a special trick again?
Gesendet von meinem Nexus 5 mit Tapatalk
Click to expand...
Click to collapse
under a bright light?
Try holding POWER + VOLDOWN (phone under a bright light, not kidding!!) after about 5 seconds, buttons should start blinking, and after 20 to 30 seconds, phone should reboot.
you may need to try 2 or 3 times, to get it to work.
Thank you for helping me out. That was awesome!
Problem solved, Locked, S-On, Stock O2! Ready for warranty
CarlosCalderon said:
Thank you for helping me out. That was awesome!
Problem solved, Locked, S-On, Stock O2! Ready for warranty
Click to expand...
Click to collapse
:laugh:
Good luck, hope you get it back soon
oh and if you could edit main thread title to include [SOLVED], thanks
Related
You can find it on:
http://alpharev.nl/
HBOOT 1.0+ is NOT supported
MOD EDIT: No shouting please!
Boot from ISO and follow instructions yea? Is it safe to boot from USB?
i have 1.0
it works
Damn, why not at my device....?!
http://forum.xda-developers.com/showpost.php?p=10176241&postcount=130
aikon96 said:
Damn, why not at my device....?!
http://forum.xda-developers.com/showpost.php?p=10176241&postcount=130
Click to expand...
Click to collapse
Nand backup CM 6.1, pull the backup to your PC (just to be sure). Install a rooted stock ROM, then try.
ogo2 said:
it works
Click to expand...
Click to collapse
I can't get it to work.. can't access fastboot in step 1 tried power for several minutes..
whitetigerdk said:
I can't get it to work.. can't access fastboot in step 1 tried power for several minutes..
Click to expand...
Click to collapse
Here is the same with Hboot: 0.43.0001. its get complete freezed until I remove the battery, but its not bricked
Suppe123 said:
Here is the same with Hboot: 0.43.0001. its get complete freezed until I remove the battery, but its not bricked
Click to expand...
Click to collapse
Jeeeezz-US! You were lucky...
Ok maybe we should use this thread
Suppe123 said:
Here is the same with Hboot: 0.43.0001. its get complete freezed until I remove the battery, but its not bricked
Click to expand...
Click to collapse
Same problem, haven't been able to find a solution so far
when cell is in hboot usb plug, before turn in fastboot try to navigate with vol+ and vol - and when you see it isn't freeze, push anykey of pc and when it says turn your phone into fastboot do it.
juanporrero said:
when cell is in hboot usb plug, before turn in fastboot try to navigate with vol+ and vol - and when you see it isn't freeze, push anykey of pc and when it says turn your phone into fastboot do it.
Click to expand...
Click to collapse
Tried that, even tried going into fastboot, and back to HBOOT doesn't work either
I've got bootloader 0.43.001 I had the keep it simple froyo rom installed when trying. I'll try the keep it simple eclair rom now
JonasDroid said:
Tried that, even tried going intofastboot, and back to HBOOT doesn't work either
I've got bootloader 0.43.001 I had the keep it simple froyo rom installed when trying.
Click to expand...
Click to collapse
Same thing is here
does this mean we can now change the partitions sizes?
eclair rom didn't help either, didn't really expect it to help but it was worth the try.
Any other suggestions? looks like much off us have this problem
How did you burn the iso (the ones with the fastboot problem)?
I burned it using the build in windows image burner onto a CD. I might try a USB later on but I'll stop trying for now
i do it with azure
Threadstarter,
Can you provide us a complete steps (Tutorial)on how to S-OFF the Hboot ? I totally do not understand, as i have never flash such thing before. I'm using the rooted HTC official Froyo ROM found in xda forum
foosoomin said:
Threadstarter,
Can you provide us a complete steps (Tutorial)on how to S-OFF the Hboot ? I totally do not understand, as i have never flash such thing before. I'm using the rooted HTC official Froyo ROM found in xda forum
Click to expand...
Click to collapse
Burn the iso and boot from it. The rest of the instructions are given to you as you go
Swyped from my HTC Legend
Is it normal that you need to press the power at the right time 2ce?
I managed to get past the first by some pretty stupid method which I'm not going to make public if I'm not sure that it works (cause it's pretty risky)
But that same method doesn't work the second time in step 2/3.
Or isn't it supposed to ask for that a 2nd time?
So I had to pull my battery out in the 2nd step and it showed a message that it was unable to flash the HBoot but luckily the old was still intact.
S-OFF on first try
I used unetbootin to make a usb boot pen, then boot into tiny core, followed instructions and S-OFF
Like AlphaRev, I am NOT responsible if your phone gets bricked.
The size is a bit bigger than the stock alpharev iso, probably because of the way I packed it, I successfully s-off'd my Bell Mobility Legend!
There was one little part, when it was flashing the HBOOT, it froze on step 3 just past the MD5 check saying flashing... OK. I waited a few mins, then rebooted my phone. All was fine, S-OFF.
Thanks to ariaxu for the necessary information to add in the alpharev script!
Link to my repacked .iso below.
http://uploading.com/files/m6c95a4d/alpharevBellMOD_rev2.iso/
MEGAUPLOAD Link
Edit: Changed the size of the iso, I forgot I had a copy of the archive inside a folder in the root of the filesystem, removed that. Now is ~20 mb smaller
Edit: To make the step process easier, use the counting method. On the first sequence that needs user interaction, count from 21, 22, 23 (3 seconds) then press power. On the second sequence, count from 21, 22, 23, 24 (4 seconds) then press power.
Nice job.. Hope you will help out a lot of other Bell owners out there..
Sent from my S-OFF'ed HTC Legend
Nice job dude. I don't think I'm quite in the mindset to perform such surgery right now, but I'm sure i'll get to it pretty soon.
It's fairly easy to do, just follow the instructions.
Sent from my S-OFF Bell HTC Legend using XDA App
Good job man! I wish that someone will figured it out how to S-OFF phones with hboot 1.01!
Sent from my Legend using XDA App
Cool ! Much thanks !
Running CM7 nightly on my Virgin Legend. Didn't work last night on stock firmware, LOL.
Worked first attempt, following your tips and some picked up in the main AlphaRev thread:
- wait for "HBOOT" on phone to change to "HBOOT-USB_PLUG" before hitting "Any Key".
- Count 3 seconds (1 missisippi, 2..., 3...) then hold power down for 10 seconds or so. When I did this I hit the power button SLIGHTLY before the message appeared on the screen.
And yeah, feel AWFUL nervous rebooting after the flash... Only way I found to reboot was to run "adb reboot". Didn't wanna pull batteries to reboot for sure.
I have no idea why it froze on the last step though, alpharev would probably know more if they had a Bell Legend...
Successfully flashed, woot.
Just attempted this for my Bell Legend and the counting method worked for me up until step 3 but at step 3 my timing must have been off and it got frozen when I tried to select fastboot.. Waited about 10 minutes for something to happen before finally deciding to pull the battery and then do a nandroid restore so I could try the whole thing all over again. However, after completing the restore, my phone rebooted but just stayed at the HTC boot up screen for about 20 minutes, just wouldn't boot, so I did another battery pull to try it again. Is it possible my phone is bricked?
Also, if it helps anyone, during the alpharev process I chose 'yes' when prompted to install clockworkmod recovery... should I not have?
Tried deleting the cache in recovery?
Kwen said:
Tried deleting the cache in recovery?
Click to expand...
Click to collapse
Hmm.. I didn't think to try that but doesn't the cache get overwritten anyway when I restore a backup?
UPDATE: Okay, so I tried deleting the cache and it's no good.. still unable to boot the phone, but I am still able to get into fake-flash menu.. so I'm kind of at a loss, not sure whether I am bricked or not or what to do about it
Try wiping everything on fake flash or you can try and restore using an older RUU and root again...
Sent from my S-OFF Bell Canada HTC Legend.
marclh1992 said:
Try wiping everything on fake flash or you can try and restore using an older RUU and root again...
Sent from my S-OFF Bell Canada HTC Legend.
Click to expand...
Click to collapse
Yeah, that was going to be my next course of action but luckily I determined that my nandroid backup was somehow corrupted.. I managed to restore an earlier backup with no problems. Thanks for the advice though
No problem! I was just scared that flashing the recovery would intentionally brick the Bell Legend. (It IS unsupported by Alpharev)
marclh1992 said:
No problem! I was just scared that flashing the recovery would intentionally brick the Bell Legend. (It IS unsupported by Alpharev)
Click to expand...
Click to collapse
No sweat man. Haha I decided that I'd bite the bullet and give it another go, which brings me to one more question. This time around I got through steps 1 and 2 just fine, and now at the third step I believe it's frozen at 'Flashing new bootblock: OK' just like you described in your first post.
I'm leaving it for a bit to see if it'll resolve itself on its own because I'm worried now that rebooting the phone at this stage may brick it perhaps?
For reference, my pc screen shows 'Waiting for flashing to complete...'
and on my phone it says
'Dumping old HBOOT.
Flashing Alpharev HBOOT: SUCCESS!
HBOOT Md5sum: b8c9de531c5e828abf0a8607732a9071.
Flashing new bootblock: OK'
I assume all this is normal but I'm not sure how to proceed
I have no idea why it freezes on that part for Bell Legends, but just unplug the USB and do a battery pull. You should be S-OFF.
Haha so I was clearly too damn impatient/excited and used adb reboot as mikereidis did (too nervous to pull the battery). And it worked, I'm S-OFF, wooo!!
Thanks a lot!
el.dizzee said:
Haha so I was clearly too damn impatient/excited and used adb reboot as mikereidis did (too nervous to pull the battery). And it worked, I'm S-OFF, wooo!!
Thanks a lot!
Click to expand...
Click to collapse
Congrats !
AFAIK, if the phone comes up and does much of anything, like displaying a logo, your phone is not truly and ir-reversibly bricked.
To be truly bricked IMO, absolutely nothing would show up on screen, not even a recharging logo. I had that happen to my last phone; absolutely no sign of life.
And BTW, when I say "ir-reversibly bricked", I mean unrecoverable by the usual relatively "simple" methods most of us use. Specialized hardware and techniques can unbrick just about any phone, if you have the right hardware and/or know the special techniques.
Is the Bell Legend significantly different from European / normal Legend models? I have an HTC Legend bought from United Kingdom (unbranded and unlocked). Would I have a problem trying out this method? My phone comes with HBOOT 1.01 and I have not yet been able to revert it to the older one. Even flashing official RUU with Goldcard allows the entire process to go through except for step 1 (it claims that there is no need to downgrade HBOOT).
1+ HBoots are not supported yet, sorry. Even alpharev has not found out a way to S-OFF it.
Hello all,
I'm sorry to interrupt you all, but this is rather important!
I tried to root my girlfriends Velocity 4G which she got with her contract with A1 (austrian carrier).
I already flashed a One S and knew of the complications a root for HTC could bring.
So I tried to get everything together before flashing and then I did it...
Got the bootloader unlocked, installed TWRP and flashed sun_dreams rom.
Don't worry, I wiped all clean and think I did it the right way (already flashed 4 other phones, but samsungs').
But I seem to have missed something as I got in a neverending bootanimation (white background with green htc logo).
I know, that you sometimes have to wait a few minutes, but after about 5 minutes or so, I thought I was stuck on boot loop.
So I rebooted, flashed it again and rebooted and nothing changed.
I then read about the boot.img... So I extracted the boot.img and did a full wipe, then installed it, after that the rom and then (just to be safe) three times again the boot.img.
Rebooted and now I got the reboot loop (white background with green logo, then black, then white background again and so on)
I tried everything and as I was about to give up, read about the final solution: the RUU or PH39IMG.zip.
Now the problem is: I cant get either of them to work. At all. When trying to flash the RUU (with bootloader relocked), the programm says: "ERROR 170: No device connected".
I read about some other people having the same problem, so I tried the solution given to them: go to the first screen, then to your temp data, extract the rom.zip, rename it and flash that one, via putting it on the external sd and booting into bootloader.
Didn't work either: Wrong CID. Same for all RUUs I could find even closely related to my phone.
As I couldn't find the real correct RUU, I tried to cheat and use the goldcard to overgo the cid-problem.
Because I couldn't boot up the Velocity 4G I tried to make one with my own Galaxy S2, which worked.
Seems to be the wrong way, since it's the wrong CID anyways, when trying to install the PH39IMG (still all RUUs say ERROR 170).
I might need to mention I didn't do the S-OFF thing, as I didn#t want to mess with the hardware... Is that necessary for my problem to getting fixed?
Maybe I just need the one correct RUU for my model, but I can't find it anywhere!
please help me somebody, as I feel very guilty because of wrecking my girlfriends phone! :crying:
any help is appreciated!!!
greetings
deweini said:
Hello all,
I'm sorry to interrupt you all, but this is rather important!
I tried to root my girlfriends Velocity 4G which she got with her contract with A1 (austrian carrier).
I already flashed a One S and knew of the complications a root for HTC could bring.
So I tried to get everything together before flashing and then I did it...
Got the bootloader unlocked, installed TWRP and flashed sun_dreams rom.
Don't worry, I wiped all clean and think I did it the right way (already flashed 4 other phones, but samsungs').
But I seem to have missed something as I got in a neverending bootanimation (white background with green htc logo).
I know, that you sometimes have to wait a few minutes, but after about 5 minutes or so, I thought I was stuck on boot loop.
So I rebooted, flashed it again and rebooted and nothing changed.
I then read about the boot.img... So I extracted the boot.img and did a full wipe, then installed it, after that the rom and then (just to be safe) three times again the boot.img.
Rebooted and now I got the reboot loop (white background with green logo, then black, then white background again and so on)
I tried everything and as I was about to give up, read about the final solution: the RUU or PH39IMG.zip.
Now the problem is: I cant get either of them to work. At all. When trying to flash the RUU (with bootloader relocked), the programm says: "ERROR 170: No device connected".
I read about some other people having the same problem, so I tried the solution given to them: go to the first screen, then to your temp data, extract the rom.zip, rename it and flash that one, via putting it on the external sd and booting into bootloader.
Didn't work either: Wrong CID. Same for all RUUs I could find even closely related to my phone.
As I couldn't find the real correct RUU, I tried to cheat and use the goldcard to overgo the cid-problem.
Because I couldn't boot up the Velocity 4G I tried to make one with my own Galaxy S2, which worked.
Seems to be the wrong way, since it's the wrong CID anyways, when trying to install the PH39IMG (still all RUUs say ERROR 170).
I might need to mention I didn't do the S-OFF thing, as I didn#t want to mess with the hardware... Is that necessary for my problem to getting fixed?
Maybe I just need the one correct RUU for my model, but I can't find it anywhere!
please help me somebody, as I feel very guilty because of wrecking my girlfriends phone! :crying:
any help is appreciated!!!
greetings
Click to expand...
Click to collapse
OK... Vodafone is still on gingerbread...
Soooo... You need a gingerbread ROM... And a gingerbread boot.img... Then get it to boot...
After that I would s-off, super cid, get to ICS hboot... Then flash the ROM of your choice
rignfool said:
OK... Vodafone is still on gingerbread...
Soooo... You need a gingerbread ROM... And a gingerbread boot.img... Then get it to boot...
After that I would s-off, super cid, get to ICS hboot... Then flash the ROM of your choice
Click to expand...
Click to collapse
So far so good... but where do I get it from?
I have this one:
RUU_HOLIDAY_SENSE3_5_Vodafone_DE_2.38.162.1_Radio_3.02.4740.09_34.20.701040.19_release_241518_signed
But this one won't work either...
What complicates the search, is that this phone goes by so many different names (vivid, velocity, holiday, raider, etc...)
Should I post a getvar all?
Concerning your further steps: I would be very happy to get it to run at all, maybe then think of reflashing something.
I don't know if I manage that s-off thing and I don't want to hard brick it and give it the final punch...
anyways, thanks for the fast response!
Can you get the ph39img from it?
Sent from my Vivid 4G using Tapatalk
rignfool said:
Can you get the ph39img from it?
Sent from my Vivid 4G using Tapatalk
Click to expand...
Click to collapse
I already did that with all the RUUs I found, but none worked...
EDIT: so I tried a solution offered by another poster in another forum which said to install CM10 on a clean wipe.
did that and it booted in the cm boot screen and loads the "first install wizard"... well, at least to the language selection screen, then it freezes and reboots again.
but at least we bought us some time at the start.
deweini said:
I already did that with all the RUUs I found, but none worked...
EDIT: so I tried a solution offered by another poster in another forum which said to install CM10 on a clean wipe.
did that and it booted in the cm boot screen and loads the "first install wizard"... well, at least to the language selection screen, then it freezes and reboots again.
but at least we bought us some time at the start.
Click to expand...
Click to collapse
Its because of a wrong hboot...
It will happen with all of the ICS+ ROMs...
I wish you hadn't relocked your bootloader...
Can you reunlock...
Iirc there is a thread with hboot updated... Maybe try that... Or download the Wcxroot thingy and flash the juopenut hboot...
Sent from my Vivid 4G using Tapatalk
rignfool said:
Its because of a wrong hboot...
It will happen with all of the ICS+ ROMs...
I wish you hadn't relocked your bootloader...
Can you reunlock...
Iirc there is a thread with hboot updated... Maybe try that... Or download the Wcxroot thingy and flash the juopenut hboot...
Sent from my Vivid 4G using Tapatalk
Click to expand...
Click to collapse
so, you're basically saying i might be able to get it to work without any RUUs or PH39IMGs?
Wow, that would be good news at last.
I already reunlocked before i flashed the CM10 rom and i didn't forget to flash the boot.img afterwards and even went back again to recovery to wipe cache and dalvik and fixed permissions.
Which one should i try?
thank you for your help!! :good:
is updating the hboot even possible without s-off?
so it seems i have to obtain s-off to flash anything else than stock rom...
as far as i read you have to be on stock ruu to obtain s-off, is that correct?
because that would be bad, as i don't have the stock ruu for my phone.
is it possible to acquire s-off without being on stock rom and would it be possible with the state my phone is in?
deweini said:
is updating the hboot even possible without s-off?
so it seems i have to obtain s-off to flash anything else than stock rom...
as far as i read you have to be on stock ruu to obtain s-off, is that correct?
because that would be bad, as i don't have the stock ruu for my phone.
is it possible to acquire s-off without being on stock rom and would it be possible with the state my phone is in?
Click to expand...
Click to collapse
I think homeslice s-offed his phone on a non stock ROM...
Sent from my Vivid 4G using Tapatalk
rignfool said:
I think homeslice s-offed his phone on a non stock ROM...
Sent from my Vivid 4G using Tapatalk
Click to expand...
Click to collapse
i already wrote a pm. do you have any ideas left? maybe try and install a gb rom and then try that ruu again?
ps: i did manage to start the ruu.exe (by reinstalling the htc sync) and it stopped with the error 131. installing the rom.zip (or PH39IMG.zip) still won't work as it says customer id check failed...
deweini said:
i already wrote a pm. do you have any ideas left? maybe try and install a gb rom and then try that ruu again?
ps: i did manage to start the ruu.exe (by reinstalling the htc sync) and it stopped with the error 131. installing the rom.zip (or PH39IMG.zip) still won't work as it says customer id check failed...
Click to expand...
Click to collapse
Okay, so I did manage to fix it, as it seems... :laugh:
This is what I did:
1. reunlocked bootloader
2. installed TWRP and booted into recovery
3. mounted the internal SD as mass storage
4. copied over VJRaiders GB rom
5. did a full wipe
6. installed VJRaiders rom
7. rebooted into bootloader
8. fastboot flashed the kernel found in the rom thread (twice)
9. rebooted and it worked...
I don't know how and why, but the problem seemed to be that I always tried to flash non-GB roms. As simple as that.
I have no idea why the RUU and PH39IMG didn't work tho...
Well. I won't touch that thing for a looong time, as it works and I had enough problems getting there!
The reason that you had problems with ics and upward roms is because your phone still has the gb hboot. This is because boss never released the ics update. To install ics roms you need the ics hboot.
Sent from my HTC One
WildfireDEV said:
The reason that you had problems with ics and upward roms is because your phone still has the gb hboot. This is because boss never released the ics update. To install ics roms you need the ics hboot.
Sent from my HTC One
Click to expand...
Click to collapse
Which I'm only able to attain with s-off, am I right?
Correct, I believe. If you didn't get an official update to ICS, you'll have to S-Off. It's honestly not as bad as it sounds, I did mine with some speaker wire...probably the worst part of it is getting the cover off of the section where you have to ground out the point. Just take your time, and make sure you're in a well lit area, with a little bit of working space, and you'll be fine.
well, the problem is, that we are not longer on a stock rom and can't seem to flash the original ruu, as we don't find it anywhere...
and as far as i know it is not recommended or possible to go s-off without being on stock rom!?
AFAIK it is UNTESTED... Not impossible
Sent from my Vivid 4G using Tapatalk
If this is anything like other HTC devices, i'd say your best shot if you're willing to try an untested idea, would be to give it a shot with a sense rom, as they tend to be (under the hood anyways) a lot closer to stock than non sense roms.
Im sending my phone back to HTC for repair.
I have two questions...
Would they look at the CID?
Can I change it back to my original CID if I've already installed a RUU that doesn't allow my CID? (sounds like a dumb question)
stanny2k said:
Im sending my phone back to HTC for repair.
I have two questions...
Would they look at the CID?
Can I change it back to my original CID if I've already installed a RUU that doesn't allow my CID? (sounds like a dumb question)
Click to expand...
Click to collapse
I read your other post http://forum.xda-developers.com/showthread.php?t=2599739 and probably a lot of others too, no answer because I have none.
So here's a small summary:
1- you're S-ON again, so changing CID cannot be done
2- you have a .401. software version which means it cannot be CID H3G, so HTC__001 is correct for that software version
3- you've removed TAMPERED and set to LOCKED (not relocked)
4- I don't know how the service center will react, and whether they would bother checking CID, etc. (from what I've seen the UK centers are quite lenient)
If you really want to go back fully to your carrier version, and "out of the box", you can take a look at my guide: http://forum.xda-developers.com/showthread.php?t=2541082
but that means starting the procedure all the way from the start again, ie
-- unlocking (and you're gonna have to do that with HTCdev)
-- s-off using rumrunner.
then follow the rest of the guide.
Don't know if it's worth the hassle; but if you need help with it, post back there.
cheers
nkk71 said:
I read your other post http://forum.xda-developers.com/showthread.php?t=2599739 and probably a lot of others too, no answer because I have none.
So here's a small summary:
1- you're S-ON again, so changing CID cannot be done
2- you have a .401. software version which means it cannot be CID H3G, so HTC__001 is correct for that software version
3- you've removed TAMPERED and set to LOCKED (not relocked)
4- I don't know how the service center will react, and whether they would bother checking CID, etc. (from what I've seen the UK centers are quite lenient)
If you really want to go back fully to your carrier version, and "out of the box", you can take a look at my guide: http://forum.xda-developers.com/showthread.php?t=2541082
but that means starting the procedure all the way from the start again, ie
-- unlocking (and you're gonna have to do that with HTCdev)
-- s-off using rumrunner.
then follow the rest of the guide.
Don't know if it's worth the hassle; but if you need help with it, post back there.
cheers
Click to expand...
Click to collapse
Thanks for taking the time in responding mate. The issue I have is that I can't get a stock RUU for my H3G CID... It just doesn't seem to exist anywhere... I think a few other people are asking the same question... Which is why I've had to change my CID to HTC__001..
stanny2k said:
Thanks for taking the time in responding mate. The issue I have is that I can't get a stock RUU for my H3G CID... It just doesn't seem to exist anywhere... I think a few other people are asking the same question... Which is why I've had to change my CID to HTC__001..
Click to expand...
Click to collapse
Well if you checked my guide, you'd see that method 3 (CWM Backup), works, and there is a H3G__001 backup out there; as a matter of fact, the example I used was for H3G__001.
nkk71 said:
Well if you checked my guide, you'd see that method 3 (CWM Backup), works, and there is a H3G__001 backup out there; as a matter of fact, the example I used was for H3G__001.
Click to expand...
Click to collapse
In that case, I take that back I'm going to follow your guide again tonight.
The last thing I want is for HTC to say No, they cant do my repair cause I've messed about with my phone...
Oh, and have a "thanks"
stanny2k said:
In that case, I take that back I'm going to follow your guide again tonight.
The last thing I want is for HTC to say No, they cant do my repair cause I've messed about with my phone...
Oh, and have a "thanks"
Click to expand...
Click to collapse
I'm going to recommend this CWM recovery, just cause the newer versions are taking close to an hour to backup/restore:
recovery-clockwork-touch-6.0.3.2-m7--v2.img 7.2 MB
https://mega.co.nz/#!6E8RiIrQ!GF5LyhmEdg8OQJxuQVVjwSxBljxhW7xsZAHLzjVACsc
MD: 1c6afb14db3f305b0ad7d85d5af80bef
Also, please follow the instruction properly, no jumping, skipping or adding steps
The only slightly tricky part (as mentioned), is in Step 6, where when the phone reboots to "stock recovery" it could hang somewhere between 25% to 50%, and you have to manually reboot, and (possibly) again towards the end, and you have to reboot manually again.
This is a known side effect because stock recovery is not exactly the same as your version, but it's not a problem.
After the FIRST (and only the FIRST) OTA update, should you go back S-On, because hboot 1.55 has a patch that will force TAMPERED to come back if you go from s-off to s-on.
NB: after the first OTA, you're phone will be 100% stock.
If you have any trouble (hopefully not), post back in my thread, as I get instant notifications on that (and if i'm still awake, i'm 2 hours ahead), and I'll try to help out.
Cheers.
---------- Post added at 06:50 PM ---------- Previous post was at 06:48 PM ----------
stanny2k said:
Oh, and have a "thanks"
Click to expand...
Click to collapse
Thanks, I like those
nkk71 said:
I'm going to recommend this CWM recovery, just cause the newer versions are taking close to an hour to backup/restore:
recovery-clockwork-touch-6.0.3.2-m7--v2.img 7.2 MB
https://mega.co.nz/#!6E8RiIrQ!GF5LyhmEdg8OQJxuQVVjwSxBljxhW7xsZAHLzjVACsc
MD: 1c6afb14db3f305b0ad7d85d5af80bef
Click to expand...
Click to collapse
Ok, I'll grab this!
nkk71 said:
Also, please follow the instruction properly, no jumping, skipping or adding steps
Click to expand...
Click to collapse
Will do! Don't worry, word for word!
nkk71 said:
The only slightly tricky part (as mentioned), is in Step 6, where when the phone reboots to "stock recovery" it could hang somewhere between 25% to 50%, and you have to manually reboot, and (possibly) again towards the end, and you have to reboot manually again.
This is a known side effect because stock recovery is not exactly the same as your version, but it's not a problem.
Click to expand...
Click to collapse
Noted.
nkk71 said:
After the FIRST (and only the FIRST) OTA update, should you go back S-On, because hboot 1.55 has a patch that will force TAMPERED to come back if you go from s-off to s-on.
NB: after the first OTA, you're phone will be 100% stock.
Click to expand...
Click to collapse
When you say "should you go back S-On" do I let the first OTA update install, then manually go back to S-ON, then let the other updates install once I've got S-ON back?
nkk71 said:
If you have any trouble (hopefully not), post back in my thread, as I get instant notifications on that (and if i'm still awake, i'm 2 hours ahead), and I'll try to help out.
Cheers.
Click to expand...
Click to collapse
Appreciate it, thank you
stanny2k said:
When you say "should you go back S-On" do I let the first OTA update install, then manually go back to S-ON, then let the other updates install once I've got S-ON back?
Click to expand...
Click to collapse
yep, exactly, after the 1st OTA, your phone will be 100% "out-of-the-box"; once the OTA updates successfully it will mean
1- your entire firmware was updated (hboot, recovery, kernel, radio, etc)
2- your ROM will also be updated, proving everything is 100%
otherwise, the OTA would not be able to complete.
Now due to a patch in later hboots (in particular 1.55 as far as i know), going from s-off to s-on, will (after a few reboots) result in "tamper detected - rebooting" and TAMPERED is back.
so in summary, if you really need to go S-On, you do so after first successful OTA (using the command mentioned in my guide), and then you can take any OTAs you like.
hope that makes sense
Perfect sense!
I'll have a bash at this tonight! Thanks a lot
Well, that was an eventful evening
Followed your guide to the letter. Everything went ok apart from a few things..
Pushing files via adb whilst in recovery causes me no end of issues... I kept getting no device found, luckily I was able to boot up and transfer the files manually.
I then flashed the wrong stock recovery (recovery 1.28.401.7.img) so I had to unlock the bootloader again to flash a different one, thankfully the one I did flash (recovery 2.24.771.3 - TRE.img), which matched the first OTA update, everything installed fine after that
Thanks a lot mate. I'll happy to send my device away for repair with no worries now.
Regards, Ryan
stanny2k said:
Well, that was an eventful evening
Followed your guide to the letter. Everything went ok apart from a few things..
Pushing files via adb whilst in recovery causes me no end of issues... I kept getting no device found, luckily I was able to boot up and transfer the files manually.
I then flashed the wrong stock recovery (recovery 1.28.401.7.img) so I had to unlock the bootloader again to flash a different one, thankfully the one I did flash (recovery 2.24.771.3 - TRE.img), which matched the first OTA update, everything installed fine after that
Thanks a lot mate. I'll happy to send my device away for repair with no worries now.
Regards, Ryan
Click to expand...
Click to collapse
Sorry to hear you had some troubles , are you on Windows 8 or 8.1, is that why adb wasn't working.
Also have a two questions about stock recovery you used,
1- when you used 1.28.401.7 the OTA didnt work, or you didnt try?
2- when you used 2.24.771.3 did the OTA hang at any point, or did it reboot (twice, I believe), correctly and by itself?
would be nice if you could give me some more info, it would probably be helpful to others too.
Thanks
nkk71 said:
Sorry to hear you had some troubles , are you on Windows 8 or 8.1, is that why adb wasn't working.
Also have a two questions about stock recovery you used,
1- when you used 1.28.401.7 the OTA didnt work, or you didnt try?
2- when you used 2.24.771.3 did the OTA hang at any point, or did it reboot (twice, I believe), correctly and by itself?
would be nice if you could give me some more info, it would probably be helpful to others too.
Thanks
Click to expand...
Click to collapse
I'm on Windows 7 mate. It just seemed really intermittent. May have been my USB lead/port.
1.28.401.7 - Downloaded the OTA fine, when the phone rebooted to install, it just hung on the "Entering Recovery" screen... Didnt get past that.
2.24.771.3 - Downloaded the OTA fine, booted into Recovery fine, hung on the first quarter (had to manually reboot) after that it installed straight away.
Hope this helps.
stanny2k said:
I'm on Windows 7 mate. It just seemed really intermittent. May have been my USB lead/port.
1.28.401.7 - Downloaded the OTA fine, when the phone rebooted to install, it just hung on the "Entering Recovery" screen... Didnt get past that.
2.24.771.3 - Downloaded the OTA fine, booted into Recovery fine, hung on the first quarter (had to manually reboot) after that it installed straight away.
Hope this helps.
Click to expand...
Click to collapse
hmm: it just hung on the "Entering Recovery" screenit just hung on the "Entering Recovery" screen
did you do a "fastboot erase cache", after flashing it? that's usually the only reason it could get stuck (or perhaps a corrupt download, did you check MD5; i've had some issues downloading from dev-host sometimes).
But thanks anyway, glad all worked out, and hope you get your device back soon
cheers.
nkk71 said:
hmm: it just hung on the "Entering Recovery" screenit just hung on the "Entering Recovery" screen
did you do a "fastboot erase cache", after flashing it? that's usually the only reason it could get stuck (or perhaps a corrupt download, did you check MD5; i've had some issues downloading from dev-host sometimes).
But thanks anyway, glad all worked out, and hope you get your device back soon
cheers.
Click to expand...
Click to collapse
Yup, I did fastboot erase cache before and after flashing it, both were successful as well. I didnt check the MD5, I just installed it after I downloaded it.. it was midnight by the time I got that far! I was tired!
Yeah and thanks a lot for your help mate. Really appreciate it.
I'll let you know the outcome with HTC Hopefully they find nothing untoward!
stanny2k said:
I'm on Windows 7 mate. It just seemed really intermittent. May have been my USB lead/port.
1.28.401.7 - Downloaded the OTA fine, when the phone rebooted to install, it just hung on the "Entering Recovery" screen... Didnt get past that.
2.24.771.3 - Downloaded the OTA fine, booted into Recovery fine, hung on the first quarter (had to manually reboot) after that it installed straight away.
Hope this helps.
Click to expand...
Click to collapse
Sorry, one last question, when you manually rebooted, did you have to keep holding VOLDOWN during boot-up, or did it enter stock recovery by itself
nkk71 said:
Sorry, one last question, when you manually rebooted, did you have to keep holding VOLDOWN during boot-up, or did it enter stock recovery by itself
Click to expand...
Click to collapse
I'm not sure if it enters recovery by itself as I just followed your guide of holding VOLDOWN
My thumbs were killing me by the end of the night!
stanny2k said:
I'm not sure if it enters recovery by itself as I just followed your guide of holding VOLDOWN
My thumbs were killing me by the end of the night!
Click to expand...
Click to collapse
finger gymnastics :laugh:
stanny2k said:
Well, that was an eventful evening
Pushing files via adb whilst in recovery causes me no end of issues... I kept getting no device found, luckily I was able to boot up and transfer the files manually.
Click to expand...
Click to collapse
Looks like I have to express my apologies on that, I believe I found the problem; the "quicker way"
I really should avoid those shortcuts, until I've tested them 100% (or at least 98%).... I'll let you know what the problem was / is when i update the guide, and sorry again for the headache!!
nkk71 said:
Looks like I have to express my apologies on that, I believe I found the problem; the "quicker way"
I really should avoid those shortcuts, until I've tested them 100% (or at least 98%).... I'll let you know what the problem was / is when i update the guide, and sorry again for the headache!!
Click to expand...
Click to collapse
:laugh: thats alright mate. No issues.
Let me know once you've updated the guide and I'll take a look at it
stanny2k said:
:laugh: thats alright mate. No issues.
Let me know once you've updated the guide and I'll take a look at it
Click to expand...
Click to collapse
problem is with the CWM i recommended, works just fine when flashed, but when using "fastboot boot CWM.img" looks like 6.0.3.2 doesnt work properly with adb, 6.0.4.5 on the other hand works with "fastboot boot"
I'll update my guide with some more "visuals" whenever I get a chance....
Ok so before I begin, I've read everything online and cannot figure this out. I've searched the forums for hours and still no luck.
I have the HTC One M7 with T-Mobile
I've had it since December with no issues at all, and still in mint condition. Never dropped.
I have it rooted, with boot unlocked
ViperOne ROM Installed, stock kernel.
Ok so Tuesday night I was going to bed (phone still on and working) and plugged my phone in to the charger to charge for the night as I usually do every night. Wake up in the morning and hit the power button to unlock the phone and to my surprise the display doesn't come on. As I said I've never dropped this phone in the entire 9 months I've had it, nor has it ever gotten wet.
This is NOT the first time this has happened either. I've had the phone display flicker on/off and after a couple times it will just stay on. It's also went off and I've fixed it by holding a light to the sensor in the top left and it came on. This time I'm not having any luck.
Please help! It's rooted, with custom ROM, and boot unlocked, therefore I cannot send it in for repair as warranty is voided. I've tried restoring it back to stock the best I can via mirror Android to PC program, but it's very difficult. I've restored it once before, I just don't get why it's not working again with me holding the light to the sensor. Any help and/or suggestions would be greatly aprreciated!! Thank you!
Kev_McCall said:
Ok so before I begin, I've read everything online and cannot figure this out. I've searched the forums for hours and still no luck.
I have the HTC One M7 with T-Mobile
I've had it since December with no issues at all, and still in mint condition. Never dropped.
I have it rooted, with boot unlocked
ViperOne ROM Installed, stock kernel.
Ok so Tuesday night I was going to bed (phone still on and working) and plugged my phone in to the charger to charge for the night as I usually do every night. Wake up in the morning and hit the power button to unlock the phone and to my surprise the display doesn't come on. As I said I've never dropped this phone in the entire 9 months I've had it, nor has it ever gotten wet.
This is NOT the first time this has happened either. I've had the phone display flicker on/off and after a couple times it will just stay on. It's also went off and I've fixed it by holding a light to the sensor in the top left and it came on. This time I'm not having any luck.
Please help! It's rooted, with custom ROM, and boot unlocked, therefore I cannot send it in for repair as warranty is voided. I've tried restoring it back to stock the best I can via mirror Android to PC program, but it's very difficult. I've restored it once before, I just don't get why it's not working again with me holding the light to the sensor. Any help and/or suggestions would be greatly aprreciated!! Thank you!
Click to expand...
Click to collapse
Well issues like this are common with custom roms. You would need to pull a log cat or DSM message and send it to the developers.
Kev_McCall said:
Ok so before I begin, I've read everything online and cannot figure this out. I've searched the forums for hours and still no luck.
I have the HTC One M7 with T-Mobile
I've had it since December with no issues at all, and still in mint condition. Never dropped.
I have it rooted, with boot unlocked
ViperOne ROM Installed, stock kernel.
Click to expand...
Click to collapse
If you are not S-OFF, then you will have to relock your bootloader with this command: fastboot oem lock
Then run this RUU 5.14.531.11 That will put you back at stock and if you want to put a custom rom or root you can try it again.
zelendel said:
Well issues like this are common with custom roms. You would need to pull a log cat or DSM message and send it to the developers.
Click to expand...
Click to collapse
Thanks for the reply, so how would I go about pulling log cat and DSM?
majmoz said:
If you are not S-OFF, then you will have to relock your bootloader with this command: fastboot oem lock
Then run this RUU 5.14.531.11 That will put you back at stock and if you want to put a custom rom or root you can try it again.
Click to expand...
Click to collapse
Thanks man! I've tried other RUU's with no luck. So just to be certain, in order to flash an RUU, you need S-Off wit Bootloader locked? Is it not possible to flash RUU with S-On? Going to do this now. I'll let you know. I'll keep you guys updated. Feeling good about this.
Kev_McCall said:
Thanks man! I've tried other RUU's with no luck. So just to be certain, in order to flash an RUU, you need S-Off wit Bootloader locked? No, if you S-OFF you can leave it unlocked.
Is it not possible to flash RUU with S-On? No, if S-ON you can only flash it if your bootloader is locked and the same OS version or higher.
Going to do this now. I'll let you know. I'll keep you guys updated. Feeling good about this.
Click to expand...
Click to collapse
See comments above.
majmoz said:
See comments above.
Click to expand...
Click to collapse
Ok so I succesfully Installed the RUU and back to stock rom, but upon rebooting, my screen did not turn back on. I've read of dozens of other users who have experienced this same thing. I guess the next step would be to fully return it to stock, turning S-On, removing tampered, unrooting, etc, and just returning it for another phone. @majmoz
Kev_McCall said:
Ok so I succesfully Installed the RUU and back to stock rom, but upon rebooting, my screen did not turn back on. I've read of dozens of other users who have experienced this same thing. I guess the next step would be to fully return it to stock, turning S-On, removing tampered, unrooting, etc, and just returning it for another phone. @majmoz
Click to expand...
Click to collapse
If you successfully ran the RUU, then you are stock with a relocked bootloader. The downside is you have to be S-OFF to remove the tampered and to change the "relocked" to "locked".
If you are S-OFF, then you would have to put TWRP 2.6.3.3 or 2.7.1.2 and install this Bootloader Reset Tool. Then flash a stock recovery. You are now completely back to stock.
majmoz said:
If you successfully ran the RUU, then you are stock with a relocked bootloader. The downside is you have to be S-OFF to remove the tampered and to change the "relocked" to "locked".
If you are S-OFF, then you would have to put TWRP 2.6.3.3 or 2.7.1.2 and install this Bootloader Reset Tool. Then flash a stock recovery. You are now completely back to stock.
Click to expand...
Click to collapse
Yea. I turned S-Off before I even ran the RUU. So there's one thing I'm confused about. If I'm trying to return to complete stock state, why would I install Twrp or CWM if those don't come with it? Is there any other way to do this? As I have no back-light and it's been very hard to do all that I've done so far. Screen hasn't come on, so I'm working blind here. Lucky for me I remember where most of the buttons are at and with the help of ADB, I've gotten this far. @majmoz
Kev_McCall said:
Yea. I turned S-Off before I even ran the RUU. So there's one thing I'm confused about. If I'm trying to return to complete stock state, why would I install Twrp or CWM if those don't come with it? Is there any other way to do this? As I have no back-light and it's been very hard to do all that I've done so far. Screen hasn't come on, so I'm working blind here. Lucky for me I remember where most of the buttons are at and with the help of ADB, I've gotten this far. @majmoz
Click to expand...
Click to collapse
Yes, look at nkk71 guide in my signature he has the steps in post 3 or 4. I'm away from the house so I can't post the link.
majmoz said:
Yes, look at nkk71 guide in my signature he has the steps in post 3 or 4. I'm away from the house so I can't post the link.
Click to expand...
Click to collapse
@majmoz
Hey bro thank you so much for the help so far, I really appreciate it. I just have one last problem. I've already talked with HTC and they're going to be sending me a replacement and I have to send my phone back in within 10 days but they said they would be checking for root.
So question 1. When you restore phone to stock ROM via RUU it unroots the phone correct?
Second problem. Now that I've restored the stock rom, usb debugging isn't enabled and I can re-enable it due to not being able to see the screen. So because USB Debugging is not enabled ADB is no longer recognizing it when I run "adb devices"
Because of this I can't turn bootloader, tampered, and lock stats back on. I'm really nervous sending my phone back in like this. I hate to keep bothering you, but you seem to know your stuff a lot more than I, and I'd hate to start a new thread. Thanks again bro.
Kev_McCall said:
@majmoz
So question 1. When you restore phone to stock ROM via RUU it unroots the phone correct?
Second problem. Now that I've restored the stock rom, usb debugging isn't enabled and I can re-enable it due to not being able to see the screen. So because USB Debugging is not enabled ADB is no longer recognizing it when I run "adb devices"
Because of this I can't turn bootloader, tampered, and lock stats back on. I'm really nervous sending my phone back in like this. I hate to keep bothering you, but you seem to know your stuff a lot more than I, and I'd hate to start a new thread. Thanks again bro.
Click to expand...
Click to collapse
1. RUU unroots the phone.
2. Yes, you need USB Debugging enabled and a custom recovery (nkk71 uses CWM).
I have been racking my brain all night. This is a long shot, but if HTC is sending you a replacement before you have to ship yours back then here is an idea. With the replacement phone side by side; memic the commands to open Settings on both phones doing the replacement phone first, then the old phone. The location of the items should be in the same place on both screens. It may take a couple of tries but you seem adapt at reading blank screens. I'm still researching a way to turn it on remotely, but this is the only solution I could come up with presently.
When you get USB Debugging enabled, use nkk71's guide to install CWM on your phone. Then complete the manual steps to remove "Tampered" and to "Locked" the phone. Reboot the phone into bootloader per the instructions. Now we need to put the stock recovery back on the phone. You can get the stock recovery out of the last OTA. Download it to your PC, then open the zip file. Within the zip is the firmware.zip, open it and you will see recovery.img file this is the stock recovery. Just extract it and flash it like you did the custom recovery earlier. Going back to nkk71's guide, complete the fastboot command to return to S-ON. Now you are completely stock with no hint of root.
@majmoz
I'm beast! lol Ok so quick update to my problem. So I got the bright idea to use the Power+Volume Down to take screenshots of my display as I blindly tapped and used that as a guide and moved forward to unlocking developer options, then enabling USB debugging. I can now see my device in ADB once again. Should be pretty cake from here. Thank you so much bro! And also, HTC has agreed to send me a new phone, but I must first send mine in. They would have sent me one first and then I send mine in later, but they wanted to place a $600 credit hold on my card. **** THAT. The rep told me they would be checking for other damages as well as if it rooted.
Kev_McCall said:
@majmoz
I'm beast! lol Ok so quick update to my problem. So I got the bright idea to use the Power+Volume Down to take screenshots of my display as I blindly tapped and used that as a guide and moved forward to unlocking developer options, then enabling USB debugging. I can now see my device in ADB once again. Should be pretty cake from here. Thank you so much bro! And also, HTC has agreed to send me a new phone, but I must first send mine in. They would have sent me one first and then I send mine in later, but they wanted to place a $600 credit hold on my card. **** THAT. The rep told me they would be checking for other damages as well as if it rooted.
Click to expand...
Click to collapse
You are a genius!!! I will have to remember that if this type of situation arises again.
@majmoz
Ok so I've been reading those sites and I know I'm so close to being back to 100% stock, but now I'm stuck. I'm confused as to what order to things.
I restore stock recovery, then lock bootloader, turn S-ON,and remove tampered and return to Locked status?
Here are my fastboot getvar details. Just trying to get this done as soon as possible as I'm also in the process of moving and wont have net here much longer. So as soon as I get this done I can send my phone back in and get the replacement. Really hate being without a phone.
Kev_McCall said:
@majmoz
Ok so I've been reading those sites and I know I'm so close to being back to 100% stock, but now I'm stuck. I'm confused as to what order to things.
I restore stock recovery, then lock bootloader, turn S-ON,and remove tampered and return to Locked status?
Here are my fastboot getvar details. Just trying to get this done as soon as possible as I'm also in the process of moving and wont have net here much longer. So as soon as I get this done I can send my phone back in and get the replacement. Really hate being without a phone.
Click to expand...
Click to collapse
Here I put them in your new post.
Alright cool thanks! I really shouldn't have created a new thread, but I wasn't sure if you would be on for much longer. Reading it now.
Kev_McCall said:
Alright cool thanks! I really shouldn't have created a new thread, but I wasn't sure if you would be on for much longer. Reading it now.
Click to expand...
Click to collapse
it doesn't take 5 threads to fix one problem does it ?
clsA said:
it doesn't take 5 threads to fix one problem does it ?
Click to expand...
Click to collapse
Probably not, you're right. But when other people don't respond to my initial thread it's kind of hard. I'm still stuck And just trying to get this finished up. Would you care to help? It's not much.
Kev_McCall said:
Probably not, you're right. But when other people don't respond to my initial thread it's kind of hard. I'm still stuck And just trying to get this finished up. Would you care to help? It's not much.
Click to expand...
Click to collapse
we all have other lives besides XDA .. you have to be patient
I have a few min where are you now in the recovery process ?