Related
Ok, you can get into BL, flash roms, but no recovery and the phone doesnt boot, basicly a boot loop. Now if i RMA this phone and they go into bootloader and see the S-Off flag, will this more than likely void my warrenty or would they have any clue about this? If so, i guess i could flash a radio and pull the battery during the flash to ensure they cant read that lol.
Any help/info is appreciated, thanks
K, guess no one has a answer for wether or not HTC Service & Repair center will know what S-Off means if they put my phone in bootloader when i send them back a phone that wont boot so i cant reverse the unrevoked forever as far as i know, if im wrong, maybe someone can correct me. Would hate to have them not warrenty the phone due to being able to see the S-Off flag in bootloader.
I guess i could brick it bad enough they cant get into bootloader, just was hoping for some feedback so i didnt have to damage the phone more than it already is lol.
anderd said:
K, guess no one has a answer for wether or not HTC Service & Repair center will know what S-Off means if they put my phone in bootloader when i send them back a phone that wont boot so i cant reverse the unrevoked forever as far as i know, if im wrong, maybe someone can correct me. Would hate to have them not warrenty the phone due to being able to see the S-Off flag in bootloader.
I guess i could brick it bad enough they cant get into bootloader, just was hoping for some feedback so i didnt have to damage the phone more than it already is lol.
Click to expand...
Click to collapse
There is an S-ON tool on the Unrevoked Forever page. You can use that.
If you used Toast's method, all you have to do is get back to a SHIP bootloader. You can do that easily by running an RUU.
anderd said:
Ok, you can get into BL, flash roms, but no recovery and the phone doesnt boot, basicly a boot loop. Now if i RMA this phone and they go into bootloader and see the S-Off flag, will this more than likely void my warrenty or would they have any clue about this? If so, i guess i could flash a radio and pull the battery during the flash to ensure they cant read that lol.
Any help/info is appreciated, thanks
Click to expand...
Click to collapse
Your phone boots -> it is not bricked. Don't RMA it until you try to resolve the problem.
To answer your question.....yes if they figure out you put unapproved firmware on the phone they do have the right to void your warranty..yes its legal now but htc or sprint can choose to void..that being said like jerryparid mentioned if it boots its not bricked so try to fix, do some searching you might just find an answer that helps.....also I'd get your flame suit on because it might get hot in here.
jerryparid said:
Your phone boots -> it is not bricked. Don't RMA it until you try to resolve the problem.
Click to expand...
Click to collapse
He's right. If your phone boots at all, even if it's just into the bootloader then it is fixable.
There may be better ways of doing it but I would suggest you download the ENG HBOOT from toasts rooting part 2 thread, put it on the root of your sdcard and boot into your bootloader and just let it run. You'll have to set everything back up, including updating your recovery image but at this point there is no reason to have it replaced just yet.
Let us know how it goes, if you need any help bringing your phone back to life we're here for ya!
User Name
Ok let me try and clarify this...
I can get into bootloader, i can flash a rom, radio, hell even RUU from PC, all complete 100%, can not get into recovery, even if i flash a recovery image. The phone DOES NOT BOOT, starts at white HTC start up screen, stay on for about 4 seconds, reboots. You can clear storage, reload roms, radios, none of that gets the phone to boot or do anything other than reboot every 4 seconds.
So nothing i can think of will fix this, ive tried roms loaded via SD card, via RUU from PC when phones in bootloader, reflashing radios, reflashing recovery, nothing works. Phone continuesly reboots after first 4 seconds of being powered on. Never boots past HTC screen. I guess i should just try and brick it 100% so they cant get into boot loader and see the S-Off flag.
Damn phones.. lol...
** EDIT **
In short i guess basicly all im saying in the above, is ive tried everything already mentioned so far prior to my post and none of that did jack squat for me... lol.
How are you flashing roms from the bootloader?
And if you cant get into recovery how are you "clearing storage"?
No offense, I understand your frustration but I have to think you're not doing something right.. You'd be the first (not saying it's impossible) person to have a phone that gets into the bootloader but is not fixable..
nebenezer said:
How are you flashing roms from the bootloader?
And if you cant get into recovery how are you "clearing storage"?
No offense, I understand your frustration but I have to think you're not doing something right.. You'd be the first (not saying it's impossible) person to have a phone that gets into the bootloader but is not fixable..
Click to expand...
Click to collapse
Ok, yet again, a clarification, i cant get into a Custom Recovery, power+vol down, all that works fine, can flash rom (load the zip on the sd card, detects, lets you flash via zip) or via RUU in windows this method, now if you scroll down to "recovery" on the menu and click on it, it starts to load then phone reboots and back to square one. Sorry if my hboot/bootloader/recovery understandings are slightly off or differ from anyone elses.
** EDIT **
Ill see if i can make a youtube video with my crappy webcam here in a bit and upload it and maybe that will make it easier to understand whats going on. I had also taken it to a sprint repair center and they couldnt figure it out themselfs lol. So if i can fix it myself, im going to get it to HTC before i my luck runs out some how and they wont fix it lol. THanks for the help guys, i appreciate the replys and help so far!
WEll as you can see i am stuck on the bootloader screen adn i cant see to get out as i tried to s-off and relocked my phone i cant factory reset becasue it just bring me back up to the bootloader and i cant even unlock it again becasue it will just hang on unlocking tried to flash an RUU file and it just checks but doesnt flash at all i am in serious need of help so anyone please help? i am hboot .98 6.01.605.05 radio 1.09.01.0312
I am not an expert as I just rooted my phone for the first time this week. However I have had the issue where a rom didn't install correctly and I was able to boot into recovery and install a backup. Not sure if this will help you but thought I would mention it. Hope someone can get you lined out asap.
Well I can't really do that since I'm relocked
Ok so this is what i did
i installed stock recovery and locked bootloader using this TUT http://forum.xda-developers.com/showthread.php?t=2470340&highlight=unlock+bootloader
everything went good had some issue with update and nandroided back to original took the updates everything good to this point now on 4.3
I am still s off boot loader shows locked now my problems started
tried to unlock using same TUT as above won't go
made sure debug was checked
adb does not see my device but fastboot does
tried to fastboot flash recovery no go says remote not allowed
tried to fastboot flash boot image no go says remote not allowed
I think it has to do with boot loader being locked but without adb how do I unlock any help would be appreciated
update
I have removed and reinstalled the latest drivers I can see phone in windows and browse it no problems.
I reinstalled adb and rumrunner for my version .15 do i need to ruu something?
any help appreciated
bregga said:
I have removed and reinstalled the latest drivers I can see phone in windows and browse it no problems.
I reinstalled adb and rumrunner for my version .15 do i need to ruu something?
any help appreciated
Click to expand...
Click to collapse
This isn't gonna be what you want to hear probably.
You should not have relocked your bootloader before taking the OTA.
In my opinion, you should not have taken the OTA at all.
I made rooted stock roms, so that 3,000 people didnt have to do the stock rom, recovery, restore boogie.
This also reduces the risk of these types of mishaps.
The bootloader does not need to be relocked to take an ota.
You now have a locked bootloader and are on an OTA version which does not yet have a Rumrunner version.
If you cannot get your unlock token to take, you are SOL until Rumrunner updates.
You said you grabbed the version for .15, well that is what you were on prior to the OTA, you are now on 2.10.605.1 as far as I know.
If I am wrong, someone else correct me. Maybe I am missing something here...it has been a long day.
EDIT:
Sounds like you got it somewhat worked out.
A rooted boot.img would help your adb situation, such as the one I put in the stock rooted roms.
another update
I ran ruu and installed rumrunner hboot and flashed a twrp recovery both went fine using fastboot commands and i have a custom recovery again
and root but still cant adb its weird I have never had a issue with adb before
santod040 said:
This isn't gonna be what you want to hear probably.
You should not have relocked your bootloader before taking the OTA.
In my opinion, you should not have taken the OTA at all.
I made rooted stock roms, so that 3,000 people didnt have to do the stock rom, recovery, restore boogie.
This also reduces the risk of these types of mishaps.
The bootloader does not need to be relocked to take an ota.
You now have a locked bootloader and are on an OTA version which does not yet have a Rumrunner version.
If you cannot get your unlock token to take, you are SOL until Rumrunner updates.
You said you grabbed the version for .15, well that is what you were on prior to the OTA, you are now on 2.10.605.1 as far as I know.
If I am wrong, someone else correct me. Maybe I am missing something here...it has been a long day.
EDIT:
Sounds like you got it somewhat worked out.
A rooted boot.img would help your adb situation, such as the one I put in the stock rooted roms.
Click to expand...
Click to collapse
I had no problem taking the OTA myself.
I posted how i did it earlier here step 2: http://forum.xda-developers.com/showpost.php?p=48677845&postcount=2
I am kinda lost on a few things as to why you should not take the OTA if a can flash superuser after wards?
carm01 said:
I had no problem taking the OTA myself.
I posted how i did it earlier here step 2: http://forum.xda-developers.com/showpost.php?p=48677845&postcount=2
I am kinda lost on a few things as to why you should not take the OTA if a can flash superuser after wards?
Click to expand...
Click to collapse
I'm not saying that you can't take the OTA. Obviously you can, I posted roms made from it, right?
I did say there is no need to relock.
I'm not gonna go over it a bunch as to why it's just not a wise idea for the common user.
But you must have noticed the flood of users getting confused, and/or stuck when trying to do so.
It's not that hard to do it successfully, no.
Is it really necessary to go through that, when the same thing can be had by simply flashing the firmware and rooted rom?
I guess my point isn't so much that you can't take the OTA, as much as it is, why? It's a bad habit for a rooted user to get into honestly.
Why go through that? You can flash the stock rooted firmware and rom and not have to do the hokey pokey and turn yourself around.
But maybe I see it differently, I don't know.
santod040
I locked the bootloader because in the threads it says it needs to be locked to take update.
in the TUT it also states that
"this thread will let you unlock your bootloader without htcdev,or let you change your hboot watermark from relocked or locked back to stock."
Thought it spoofed the software to make it think it was locked oh well no biggie I thought if bootloader was unlocked or relocked ota's would fail like mine was getting error 410
santod040 I have been looking at your roms and "i'm not trying to kiss your but" they look nice and get good reviews but I wanted to stay stock
nusense is the one i was really looking at hard but like i said wanted to run stock
I can wait for a new rumrunner no problem there and if it never gets done oh well I am now rooted and have twrp installed and kitkat next month "well the way verizon is everyone else will have kitkat and we will have to wait a month or so before we get it"
and i have not seen anyone else say that adb does not work with 4.3 update that is why I was asking about it to see if anyone else had a issue with adb not working after update and what if anything they did to get it back without adb rumrunner is not going to work for me anyway
bregga said:
I locked the bootloader because in the threads it says it needs to be locked to take update.
in the TUT it also states that
"this thread will let you unlock your bootloader without htcdev,or let you change your hboot watermark from relocked or locked back to stock."
Thought it spoofed the software to make it think it was locked oh well no biggie I thought if bootloader was unlocked or relocked ota's would fail like mine was getting error 410
santod040 I have been looking at your roms and "i'm not trying to kiss your but" they look nice and get good reviews but I wanted to stay stock
nusense is the one i was really looking at hard but like i said wanted to run stock
I can wait for a new rumrunner no problem there and if it never gets done oh well I am now rooted and have twrp installed and kitkat next month "well the way verizon is everyone else will have kitkat and we will have to wait a month or so before we get it"
and i have not seen anyone else say that adb does not work with 4.3 update that is why I was asking about it to see if anyone else had a issue with adb not working after update and what if anything they did to get it back without adb rumrunner is not going to work for me anyway
Click to expand...
Click to collapse
I can understand wanting to stay stock.
I was just suggesting flashing a pure stock rooted rom.
As I said though, relocking was not necessary.
Okay I'm really getting sick of this thing. I've totally no idea what I've done but after 2 hours of trying, I'm back to the same thing. Finally managed to get the proper USB drivers for my computer so the phone and the computer could talk to each other.
I've followed this guide on how to unroot the phone:
http://theunlockr.com/2014/07/15/how-to-unroot-the-htc-desire-816/
First, when I relock the bootloader, I still got ***Tampered*** and ***Security Warning*** although it says relocked. I couldnt boot into the OS. Can't do anything at all. Unlocking it again solves the problem.
Secondly, I wasn't able to get to S-Off mode. Anyone can shine some light on this? I'm really stuck here. I can't flash the stock RUU.zip as it says signature failed.
Would be glad that someone could assist me on this... I really need to get rid of the phone as soon as possible as I'm sick of this thing.
And, BTW, mine is the single SIM with LTE version.
Thank you.
Is yours the a5_chl or the a5_ul? The a5_chl is the one on VM.
did you flash the correct stock recovery to replace your custom recovery before you re-locked it?
also, there is no S-off for this model yet so don't waste time looking for it
edit
FoxyDrew said:
Is yours the a5_chl or the a5_ul? The a5_chl is the one on VM.
Click to expand...
Click to collapse
a5_ul.
Where can I get the files for a5_ul?
seekfind said:
did you flash the correct stock recovery to replace your custom recovery before you re-locked it?
also, there is no S-off for this model yet so don't waste time looking for it
Click to expand...
Click to collapse
I couldn't find the proper stock recovery.
But I thought S-Off needs to be off before everything else can be done?
No need for S-off to unlock/relock bootloader or flash custom/stock recovery/ROM. none of us here have S-off and yet we all use custom delights provided by XDA devs
this will probably help you with the stock recovery, tho I'm not sure if it works for single SIM or not:
http://forum.xda-developers.com/desire-816/help/how-to-install-stock-recovery-img-t2937667
This may seem like an amateur question, but how do you tell if your phone is a5_chl or a5_ul?
jamiedenton said:
This may seem like an amateur question, but how do you tell if your phone is a5_chl or a5_ul?
Click to expand...
Click to collapse
you restart your phone to bootloader.
1. Disable fastboot. Settings>Battery>uncheck fastboot.
2. Power off
3. Press and hold Volume Down and power
it's written in there
Hello. My htc is CID 332 latam, and i´m S-ON. Unfortunately, while i was trying to install crdroid, something went wrong and now i have locked bootloader and no recovery... Can´t boot, can´t format... Only enter in fastboot mode, but as i said, i´m s-on and with bootloader locked... I´m out of options... Please help me...
TinkerWind said:
Hello. My htc is CID 332 latam, and i´m S-ON. Unfortunately, while i was trying to install crdroid, something went wrong and now i have locked bootloader and no recovery... Can´t boot, can´t format... Only enter in fastboot mode, but as i said, i´m s-on and with bootloader locked... I´m out of options... Please help me...
Click to expand...
Click to collapse
Why on earth did you lock your BL !!! You have a recovery but it's not stock and with a locked BL you can't reach TWRP..... but it's still there.
Only thing i can think of is to download the RUU.exe file that fits your firmware and run it with the phone booted to the bootloader.
I was trying to install crdroid to reverse from oreo to nougat. Then, when trying to install stock ruu via twrp, i locked it to install the OTA, and then... The apocalypsis, hehe. Is there any human way to fix it? Please, if i can do it, i swear not to mess up with this kid anymore... By the way, the corresponding RUU, gives the error ¨Image too big¨, and is not an .exe
TinkerWind said:
I was trying to install crdroid to reverse from oreo to nougat. Then, when trying to install stock ruu via twrp, i locked it to install the OTA, and then... The apocalypsis, hehe. Is there any human way to fix it? Please, if i can do it, i swear not to mess up with this kid anymore... By the way, the corresponding RUU, gives the error ¨Image too big¨, and is not an .exe
Click to expand...
Click to collapse
You can't run zips from the bootloader, maybe only a ruu.exe. not stock and a locked BL is big-time error. Not much to do when you cant reach download mode
I can reach fastboot, and RUU mode. I´ve been digging all day yesterday, but not found any solution. Maybe you, who have more experience, could help me save this phone... Please, let´s give it a try. Doesn´t wanna drop this to the trash can... Thanks form answer so soon.
TinkerWind said:
I can reach fastboot, and RUU mode. I´ve been digging all day yesterday, but not found any solution. Maybe you, who have more experience, could help me save this phone... Please, let´s give it a try. Doesn´t wanna drop this to the trash can... Thanks form answer so soon.
Click to expand...
Click to collapse
Well if you can't reach download mode or recovery there is nothing i can suggest to help you. A ruu.exe from the bootloader might work.
Helped many but relocking a non stock device is like locking yourself in in Alcatraz .......