OK, so i need to ship my phone back to wirefly because its screen has static-like things on it (noticeable against black). So i need to install the RUU butttttttttttttt it has been absolute hell trying to figure out how to lock it again so i can install it!
If someone would please tell me that would be great. Every other site is just a bunch of people as lost as me.
xkelx said:
OK, so i need to ship my phone back to wirefly because its screen has static-like things on it (noticeable against black). So i need to install the RUU butttttttttttttt it has been absolute hell trying to figure out how to lock it again so i can install it!
If someone would please tell me that would be great. Every other site is just a bunch of people as lost as me.
Click to expand...
Click to collapse
Assuming you're on a GB ROM, and have the stock kernel flashed.
1)Reboot your phone back into fastboot
2)hook it up your computer and in command prompt type
" fastboot oem lock "
3) Run RUU
dejahboi said:
Assuming you're on a GB ROM, and have the stock kernel flashed.
1)Reboot your phone back into fastboot
2)hook it up your computer and in command prompt type
" fastboot oem lock "
3) Run RUU
Click to expand...
Click to collapse
More importantly, make sure you have flashed the stock recovery if your on a custom recovery otherwise the RUU won't work.
Will this give you a *LOCKED* or *RE-LOCKED* bootloader?
kmcspecial said:
Will this give you a *LOCKED* or *RE-LOCKED* bootloader?
Click to expand...
Click to collapse
With us having S-on devices it will say Re-Locked. Until , they crack S-off or you have an S-off developer phone that is the best we can do .
I had that static on my first rezound
Sent from my ADR6425LVW using XDA App
Let us know if you get charged for the Re-Locked phone. Only reason I'm not unlocking mine
xkelx said:
OK, so i need to ship my phone back to wirefly because its screen has static-like things on it (noticeable against black). So i need to install the RUU butttttttttttttt it has been absolute hell trying to figure out how to lock it again so i can install it!
If someone would please tell me that would be great. Every other site is just a bunch of people as lost as me.
Click to expand...
Click to collapse
go here and do #1~3
http://forum.xda-developers.com/showthread.php?t=1466474
Related
Hey,
I have a Telus Amaze 4G and I have lost my radio. Phone says it has an unknown Baseband/IMEI. Not sure where I went wrong/ lost my radio but this is a run down of what I've done to my handset so far:
- Rooted
- Flashed CWM recovery.
- Flashed EnergyRom.
- Sent phone to HTC because of suspected warranty issue. (Wouldn't Charge)
- Phone returned un-repaired from HTC.
- Charged battery externally, phone finally booted.
- Replaced CWM with 4EXT.
- Ran the Telus GB RUU exe from windows.
- Did the OTA ICS from the phone.
- Attempted upgrade to SpeedRom, failed because the OTA had failed, didn't realize this until the next around, this is where I think it went wrong. Had done a full wipe of all partitions, except SD from 4EXT in the process.
- Re-applied original Telus GB RUU.
- Re-applied Telus ICS OTA. this is when I realized I had no radio. I had not put in my SIM-Card since the phone was returned from HTC so not exactly sure when it stopped working but the OTA had installed correctly this time.
- Re-rooted.
- Did the wire-trick and obtained S-OFF.
- Flashed the latests JP hboot.
- Used fastboot to flash several radio.img files from various TMO and Telus RUUs, nada.
- Flashed the T-Mobile ICS RUU via hboot, still no radio.
- Extracted the rom from the Telus GB RUU and applied that via hboot, still no radio.
The only thread I could find where someone had mentioned the missing baseband on an amaze 4g, the only suggested fix was to reflash a stock, GB rom but that didn't work. Now I am at a loss at to what I could try next.
Any suggestions would be greatly appreciated.
found this thread fro you maybe that will help you get a idea http://forum.xda-developers.com/showthread.php?t=1627565
Jay_Rulen said:
found this thread fro you maybe that will help you get a idea http://forum.xda-developers.com/showthread.php?t=1627565
Click to expand...
Click to collapse
He means the built in antenna radio software drivers. Your best call would be warranty replacement, probably a bad chipset issue.
Dark Nightmare said:
He means the built in antenna radio software drivers. Your best call would be warranty replacement, probably a bad chipset issue.
Click to expand...
Click to collapse
Not cool.... so Telus/HTC already know that I've had third party software on my handset after I returned it the last time. If I was to reverse *everything* I've done, do you think I could get it back to a point in which they would still honor the warranty?
Thanks!
inluck said:
Not cool.... so Telus/HTC already know that I've had third party software on my handset after I returned it the last time. If I was to reverse *everything* I've done, do you think I could get it back to a point in which they would still honor the warranty?
Thanks!
Click to expand...
Click to collapse
You said you're s-off, rights? Flash a pure stock ruu, lock the bootloader via fastboot using the command fastboot oem lock. Check the bootloader to make sure it says locked, then in fastboot use the command fastboot OEM writesecureflag 3 to s-on. Once you're all done, give 'm a call again. Said it happened when you updated to ics or something.
Sent from an Amaaaaaazing place :-D
Dark Nightmare said:
You said you're s-off, rights? Flash a pure stock ruu, lock the bootloader via fastboot using the command fastboot oem lock. Check the bootloader to make sure it says locked, then in fastboot use the command fastboot OEM writesecureflag 3 to s-on. Once you're all done, give 'm a call again. Said it happened when you updated to ics or something.
Sent from an Amaaaaaazing place :-D
Click to expand...
Click to collapse
Okay, I can totally do all that. One last question though, when my phone was last returned to HTC, they discovered I had 3rd party software on the phone and refused to look at it any further, do you think this will have an effect on a second return?
inluck said:
Okay, I can totally do all that. One last question though, when my phone was last returned to HTC, they discovered I had 3rd party software on the phone and refused to look at it any further, do you think this will have an effect on a second return?
Click to expand...
Click to collapse
I can't say, just keep your fingers crossed that it doesn't.
Dark Nightmare said:
You said you're s-off, rights? Flash a pure stock ruu, lock the bootloader via fastboot using the command fastboot oem lock. Check the bootloader to make sure it says locked, then in fastboot use the command fastboot OEM writesecureflag 3 to s-on. Once you're all done, give 'm a call again. Said it happened when you updated to ics or something.
Sent from an Amaaaaaazing place :-D
Click to expand...
Click to collapse
Know off the top of your head how to remove the *RELOCKED* from the bootloader?
inluck said:
Know off the top of your head how to remove the *RELOCKED* from the bootloader?
Click to expand...
Click to collapse
How did you lock the bootloader? Manually or via hasoons tool? Did you s-on as yet or still s-off?
Sent from an Amaaaaaazing place :-D
Dark Nightmare said:
How did you lock the bootloader? Manually or via hasoons tool? Did you s-on as yet or still s-off?
Sent from an Amaaaaaazing place :-D
Click to expand...
Click to collapse
I had extracted the rom.zip from the Telus GB RUU and flashed it to the handset from hboot. This removed the jp hboot and put it back to stock.
I then booted into fastboot and issued these commands from the cli:
fastboot.exe oem lock
fastboot.exe oem writesecureflag 3
So to answer your questions, manually and I am now S-ON.
I get the feeling I need to issue those commands from the jp hboot instead of the stock. Am I right?
inluck said:
I had extracted the rom.zip from the Telus GB RUU and flashed it to the handset from hboot. This removed the jp hboot and put it back to stock.
I then booted into fastboot and issued these commands from the cli:
fastboot.exe oem lock
fastboot.exe oem writesecureflag 3
So to answer your questions, manually and I am now S-ON.
I get the feeling I need to issue those commands from the jp hboot instead of the stock. Am I right?
Click to expand...
Click to collapse
You should've made sure the bootloader said locked first -_-, oh well, unless you wanna s-off again, hope they don't make an issue out of it. Why did you put exe at the end of fastboot? You did it before s-on, it should say locked, odd.
Sent from an Amaaaaaazing place :-D
Dark Nightmare said:
You should've made sure the bootloader said locked first -_-, oh well, unless you wanna s-off again, hope they don't make an issue out of it. Why did you put exe at the end of fastboot? You did it before s-on, it should say locked, odd.
Sent from an Amaaaaaazing place :-D
Click to expand...
Click to collapse
It said relocked, I wasn't sure at which point that was supposed to disappear/changed.
I'll S-OFF again once the thing gets another charge.
I have a feeling it was because I was in the stock GB hboot and not the modified jb hboot.
Don't want to leave anything for them to complain about.
inluck said:
It said relocked, I wasn't sure at which point that was supposed to disappear/changed.
I'll S-OFF again once the thing gets another charge.
I have a feeling it was because I was in the stock GB hboot and not the modified jb hboot.
Don't want to leave anything for them to complain about.
Click to expand...
Click to collapse
It's not the hboot. I gotta find the s-on thread, since you have to be on a stock bootloader before you s-on. I probably missed something.
Sent from an Amaaaaaazing place :-D
http://forum.xda-developers.com/showthread.php?t=1647728
I just remembered another trick as well, when you s-off the device, it relock your bootloader but it says "locked" not relocked, therefore when you s-off, do not flash the jb hboot when they ask you if you wanna flash it, then simply s-on via the fastboot command, voila!
Sent from an Amaaaaaazing place :-D
So I'm still S-ON but I'm rooted and running Clean Rom 4.5
I need to take my phone back to Verizon as the USB port is crapping out on me and it's a pain to charge the phone. So I found the latest OTA ROM, here..
http://www.androidpolice.com/2012/0...cream-sandwich-ruu-for-final-ota-3-14-605-12/
And do I just need to rename it to PH98 and then flash it via recovery or is the process much more detailed?
AlmostTactful said:
So I'm still S-ON but I'm rooted and running Clean Rom 4.5
I need to take my phone back to Verizon as the USB port is crapping out on me and it's a pain to charge the phone. So I found the latest OTA ROM, here..
http://www.androidpolice.com/2012/0...cream-sandwich-ruu-for-final-ota-3-14-605-12/
And do I just need to rename it to PH98 and then flash it via recovery or is the process much more detailed?
Click to expand...
Click to collapse
PH98IMG is what you will want to name it, but essentially that's all you need if your s-on. they don't really check the bootloader screen so you'll be ok. I've turned in 2 already haha, one i left S-Off
Awesome!!! Thanks
Make sure you relock the bootloader first.
fastboot oem lock
shrike1978 said:
Make sure you relock the bootloader first.
fastboot oem lock
Click to expand...
Click to collapse
I literally go into fastboot, then oem, then lock? Then after that I go through the HBOOT and flash the ROM?
AlmostTactful said:
I literally go into fastboot, then oem, then lock? Then after that I go through the HBOOT and flash the ROM?
Click to expand...
Click to collapse
Yep. I've done it before by putting the PH98IMG on the sdcard, running "adb reboot bootloader" (which will take you straight to fastboot), "fastboot oem lock", then select BOOTLOADER from the fastboot menu and let it flash.
dalvear88 said:
PH98IMG is what you will want to name it, but essentially that's all you need if your s-on. they don't really check the bootloader screen so you'll be ok. I've turned in 2 already haha, one i left S-Off
Click to expand...
Click to collapse
I had a funny one....my rez was over heating and I brought it in and they popped out the battery...put it back in and then went straight to the h boot screen....I'm s-on still...but it said tampered and I thought I was screwed....but they still sent me a new one....sweet....I was elated
Sent from my ADR6425LVW using xda premium
hey guys/gals, let me start off by saying that i knew better but as always i screwed up by letting my add get the best of me! i relocked bootloader to RUU to stock . problem is that i didnt load the correct splash1 first! now when i try to flash anything i get the signature error. im hoping that a work-around is available. i tried the htcdev but get an error 160 MID not allowed. tried the toolkit(s) available, NO ADB!!! soooo here i am hoping that you guys might have experienced a moment of dumbness as i did....i get a multitude of errors when trying to flash stuff (error 12 sig failure,wrong main version error)...was unlocked and rooted per rumrunner (THANKS BEAUPS!!!!!) prior to my screw up... heres what i have
s-on
hboot-1.33.0001
radio-1.01.1112
baseband-1.01.01.1112
version main-3.06.605.4
cid-VZW_001
bootloader-041a62aa
(lmk if any further info is needed)
like i stated before , i know i needed to flash splash1 BEFORE locking bootloader but in my defense i had my 11 week old son in my arms (multitasking FAIL) , so if you guys have ANY suggestion please feel free to lmk...THANKS IN ADVANCE as this is a new problem for me!
and btw, i spent yesterday sifting through threads to try to solve this ,to no avail....i didnt want to tie you guys up prematurely
i did try to re run rumrunner and moonshine (even though i knew moonshine wouldnt work) but as i said , i have no adb and usb debugging s questionable, although i can use fastboot to rebootRUU
stephenculkin6277 said:
i did try to re run rumrunner and moonshine (even though i knew moonshine wouldnt work) but as i said , i have no adb and usb debugging s questionable, although i can use fastboot to rebootRUU
Click to expand...
Click to collapse
Try this, access to fastboot first then connect usb to pc
http://forum.xda-developers.com/showpost.php?p=48680578&postcount=44
i get the error:remote not allowed....I had those files downloaded yesterday
i just tried in the rebootRUU status (blask screen with HTC logo and got error 43 main versio check fail?
i got firmware2 to run (both times) ... do i need to try to reset to stock from bootloader now?
or is the 2nd one no good without the 1st? im sorry , i just dont want to screw up anymore than i already have ya know
stephenculkin6277 said:
or is the 2nd one no good without the 1st? im sorry , i just dont want to screw up anymore than i already have ya know
Click to expand...
Click to collapse
Reboot bootloader, the second firmware is the new Hboot 1.54.0000 need it to run the new Ruu. hope it help
after reboot bootloader confirm that your hboot is the new. so you can go ahead with the ruu
k thanks, but I think the problem im having running the RUU is the image...whatever that is, I think the splash1 I forgot to load...I will try running the jb_50 RUU now though , thanks
finanandroid said:
Try this, access to fastboot first then connect usb to pc
http://forum.xda-developers.com/showpost.php?p=48680578&postcount=44
Click to expand...
Click to collapse
finanandroid said:
Reboot bootloader, the second firmware is the new Hboot 1.54.0000 need it to run the new Ruu. hope it help
after reboot bootloader confirm that your hboot is the new. so you can go ahead with the ruu
Click to expand...
Click to collapse
sorry , I spoke too soon...I just finished running RUU and you have solved the mystery!!! much gracias my friend!!! I cant thank you enough!!!
stephenculkin6277 said:
sorry , I spoke too soon...I just finished running RUU and you have solved the mystery!!! much gracias my friend!!! I cant thank you enough!!!
Click to expand...
Click to collapse
You're welcome! glad that you can back on business. :victory:
Instructions clearly said the splash image was only for custom splash images. It is not a necessary step.
Sent from my DLX using xda app-developers app
See that's the thing, I was running pro bam which had a non stock splash img so I assumed I had to, my bad
You may need to reinstall adb?
thayl0 said:
You may need to reinstall adb?
Click to expand...
Click to collapse
Yeah, I did as a precaution.... The firmware2 file let me run RUU after I flashed it... I still can't believe I made such a bone head mistake! Now I just wish I could get my Bootloader unlock token for future screw ups lol But I just get error 160 MID not allowed when I try, At least rumrunner worked for me!
stephenculkin6277 said:
Yeah, I did as a precaution.... The firmware2 file let me run RUU after I flashed it... I still can't believe I made such a bone head mistake! Now I just wish I could get my Bootloader unlock token for future screw ups lol But I just get error 160 MID not allowed when I try, At least rumrunner worked for me!
Click to expand...
Click to collapse
You can no longer do that any more.
That sucks donkey balls!
If you're s-off you can set cid to 22222222 and get an unlock token at htcdev
Thank you sir! I now have the token I have been needing!
Sent from my HTC6435LVW using xda app-developers app
So right now, my DNA is s-on and relocked(by accident). What im trying to do is get my hboot to stock so i can flash the RUU and get my phone back to its normal state. My problem right now is that im trying to unlock bootloader but i use the command fastboot fastboot flash unlocktoken unlock_code.bin, accept, then it reboots. But it still says its relocked and refuses to unlock. I don't know how to unlock it another way with S-on
You need to s-off, then go stock
Phaded said:
You need to s-off, then go stock
Click to expand...
Click to collapse
How would I s-off?
Rumrunner.us type that in your browser and download the one for the DNA.
Sent from my DNA using my mind.
Update:
So i did some stuff( I honestly don't even know what) and i was able to unlock bootloader. Next i'm unsure of what to do to get the RUU on my phone. Anyways, i tried the rumrunner but it just ended because it couldn't detect any adb connection to my phone. That was also one of the problems i forgot to mention
Uzephi said:
Rumrunner.us type that in your browser and download the one for the DNA.
Sent from my DNA using my mind.
Click to expand...
Click to collapse
We don't know what version he is on...
OP what version are you on?
I flashed a backup from twrp recovery then it was successful but when I rebooted my device it was stuck on an endless boot. I was able to get to twrp recovery then i bootedinto the bootloader I dont know why but i relocked the bootloader using oem lock. then it booted up and now is stock on the htc logo. i thought it would boot up then i was going to unlock the bootloader again thinking it would fix it. i was not thinking straight. now my phone is not being picked by my pc when using adb devices. please help
please
thank you
JOE180360 said:
i was going to unlock the bootloader again thinking it would fix it. i was not thinking straight.
Click to expand...
Click to collapse
I think you mean you relocked the bootloader again, since that is what it said in your PM to me; and it makes more sense (based on what you are saying).
Relocking as you now know, is not (in itself) going to return you to stock. Think about that, where would the necessary stock ROM and other files magically come from?
JOE180360 said:
now my phone is not being picked by my pc when using adb devices. please help
Click to expand...
Click to collapse
adb only works when the phone is booted, and possibly in recovery. It will never work in bootloader or fastboot mode.
Check to see if the command works in fastboot mode: fastboot devices
If so, since you are already RELOCKED, just run the 4.28.502.2 RUU (as I've seen you asked for in another thread, which I also answered).
Thanks man.
redpoint73 said:
I think you mean you relocked the bootloader again, since that is what it said in your PM to me; and it makes more sense (based on what you are saying).
Relocking as you now know, is not (in itself) going to return you to stock. Think about that, where would the necessary stock ROM and other files magically come from?
adb only works when the phone is booted, and possibly in recovery. It will never work in bootloader or fastboot mode.
Check to see if the command works in fastboot mode: fastboot devices
If so, since you are already RELOCKED, just run the 4.28.502.2 RUU (as I've seen you asked for in another thread, which I also answered
I am charging m phone right now. hopefully everything goes well. thanks for finding the ruu.
Click to expand...
Click to collapse
help
redpoint73 said:
I think you mean you relocked the bootloader again, since that is what it said in your PM to me; and it makes more sense (based on what you are saying).
Relocking as you now know, is not (in itself) going to return you to stock. Think about that, where would the necessary stock ROM and other files magically come from?
adb only works when the phone is booted, and possibly in recovery. It will never work in bootloader or fastboot mode.
Check to see if the command works in fastboot mode: fastboot devices
If so, since you are already RELOCKED, just run the 4.28.502.2 RUU (as I've seen you asked for in another thread, which I also answered).
Click to expand...
Click to collapse
the command works but the ruu is saying it cant pickup the device
will the ruu work if there's no image version on the phone.
JOE180360 said:
the command works but the ruu is saying it cant pickup the device
Click to expand...
Click to collapse
theres no image version on the phone. will it still work
the ruu started and is stuck at 14% sening.....
JOE180360 said:
theres no image version on the phone. will it still work
Click to expand...
Click to collapse
it stated uo great then now is stuck at 14%. what should i do?
TAHNK YOU!!!!!!!
JOE180360 said:
it stated uo great then now is stuck at 14%. what should i do?
Click to expand...
Click to collapse
Your a real life saver man. thanks to you i got my phone back. i probably would have never found the ruu with out you.
Thanks so much.