Hey all, I am thinking about selling my HOX+ and the buyer doesn't want the phone rooted for warranty purposes. Is there a way for me to remove root and restore everything to stock? Thanks in advance!
Please reboot in bootloader and tell me your hboot version and confirm AT&T/TELUS version.
I see HBOOT version but not the AT&T/Telus version.
Here's everything I see
EVITARE_UL PVT SHIP S-ON RL
HBOOT 1.32.0000
CPLD-None
MICROP-None
RADIO-SSD:1.09.55.17
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM TYPE: MDM921
Oct 20 2012, 13:45:56
eyecrispy said:
I see HBOOT version but not the AT&T/Telus version.
EVITARE_UL PVT SHIP S-ON RL
Click to expand...
Click to collapse
Sure, this is the confirmation.
You need this RUU for your AT&T
Reboot in bootloader mode
Plug in your USB cable
Open a adb command window
At the prompt type>fastboot oem lock
Your phone will reboot.
Again in bootloader mode with FASTBOOT USB highlighted simply run the RUU downloaded
Your phone will be completely wiped including SD card.
What exactly is the RUU? What does it do?
Also, once I do that, how do I get the stock ROM back on it?
Also, once I get back to stock recovery how do I get back to bootloader?
RUU = ROM Update Utility
This will update and restore your phone to it's original state including boot, recovery, rom, etc. Your phone will be exactly like it was the first time you press the Power button.
To access Bootloader simply hold your Volume down rocker and press Power button.
I ran the RUU a few times and it has been stuck on the "Verifying information on your Android phone. Please wait ..." screen for a long time. How long does the RUU run?
I am running win7 from a virtual machine. Not sure if that makes a difference. But the RUU didn't seem to work. Do you have a MD5 for the RUU file you posted?
Would that work if you registered your phone on htcdev.com? Warranty will be void if you unlocked your device, it doesn't matter if its locked again.
eyecrispy said:
I ran the RUU a few times and it has been stuck on the "Verifying information on your Android phone. Please wait ..." screen for a long time. How long does the RUU run?
I am running win7 from a virtual machine. Not sure if that makes a difference. But the RUU didn't seem to work. Do you have a MD5 for the RUU file you posted?
Click to expand...
Click to collapse
Yes maybe the VM can be a problem, I will do search about this. One thing I know. some people says the needed many try before it worked.
MD5 : 3B951A3195E60712A62A4DB6AC181CC7
You can try this one if you want an alternative : RUU_EVITARE_UL_JB_45_Cingular_US
Thanks. What's the difference between the two exe files?
They are the same, only the source is different. Since I am having an TELUS phone I can't test if any of those files are working so I gave you two different source to download the file just "in case..."
In bootloader it will state re-locked after locking bootloader again so its not possible to get back all stock again.
Sent from my HTC One X+ using xda premium
Related
So I rooted my HTC Rezound a months ago, since ICS didn't launch when I wanted it to lol..Any way I decided I want to unroot my phone so I can trade it in on a new one. I followed the guidelines a user posted on XDA to the T and I keep getting either a message failed my version is newer or older than the one im installing? I did however download a ICS fake update before I rooted and wasn't sure if that has anything to do with it. As of right now I am stuck in the Bootloader screen I can not do anything. Please help, I need this phone for work since I am supposed to be On Call everyday. If you need any numbers from the bootloader screen I am sure I have them memorized lol.
Unrooting Guide I followed
Was here in XDA
The easiest way I've found to re-lock your rezound is to download the attached "tools.zip" and extract to your desktop.
Boot your rezound into fastboot by removing your battery, putting the battery back in, holding down on the volume rocker and power. Then plug your rezound into your computer. Assuming you used your computer to unlock the rezound then you should already have the required drivers.
Open command prompt and enter the following:
cd C:\Users\[Your Name Here]\desktop\tools
Then run the command
fastboot oem lock
Your bootloader is now locked and ready to begin restoring stock recovery and rom from Stock RUU.
2. Downloading the stock RUU
*Will Update As New RUU's Are Released*
2.02.605.11 STOCK RUU EXE
download
1.02.605.6 STOCK RUU EXE
download
(will add PH98IMG.zip download for 2nd method soon)
You can do this one of two ways. You can use the exe ruu which i like to use, its simple straight forward and guides you through the process
-or-
Extract the RUU zip from the exe or download from XDA its all over.
Rename the zip PH98IMG.ZIP put on root of SD card and boot into HBOOT hit
yes with appropriate volume key and let it do its thing.
I personaly perfer running the exe. Makes life easy. But whatever floats your boat.
SIDE NOTE: IF YOU WISH TO ROOT AGAIN
the one click root tool might not work properly and will not have proper permision to install SU, If this happens flash amon through fastboot. And under development section install su / superuser, you are now rooted again
Credit for user cotribution:
DrSadistic ( Fastboot section )
***this was a quick write up so if you think anything should be added or removed, or there is some wrong information let me know so i can fix it***
VIGOR PUT SHIP S-ON RL
HBOOT-2.25.0000
RADIO-1.22.10.0421r/1.22.10.0424r
OpenDSP-v13.6.0.7611.00.0104
eMMC-boot
Apr 12 2012, 16:47:46
This is what is on my Rezound
krayz22 said:
VIGOR PUT SHIP S-ON RL
HBOOT-2.25.0000
RADIO-1.22.10.0421r/1.22.10.0424r
OpenDSP-v13.6.0.7611.00.0104
eMMC-boot
Apr 12 2012, 16:47:46
This is what is on my Rezound
Click to expand...
Click to collapse
Looks like you have ICS installed.
That tutorial was for Gingerbread.
Just flash the 3.14.605.12 RUU.
i rooted my girlfriends sprint evo 3d using unknownforce's down grade method, i wanna return her phone back to complete stock how would i do that? she is s-off right now. thanks for the advice
You could flash an ruu from bootloader since your s-off. Here's a link for a list of ruu pick the one that says ics shooter 35 s 2.89 1.09.00.0706 spcs wwe to that nature http://www.filefactory.com/f/4ef0ef536face67a/. Just remember to rename the file PG86IMG in all caps and place on the root of your sdcard. Power down your phone, and boot up into bootloader and let your phone detect the file and confirm to update. Next you might want to get a drink or something to eat. It'll take like 10 minutes. Hope that helps
Jsparta26 said:
You could flash an ruu from bootloader since your s-off. Here's a link for a list of ruu pick the one that says ics shooter 35 s 2.89 1.09.00.0706 spcs wwe to that nature http://www.filefactory.com/f/4ef0ef536face67a/. Just remember to rename the file PG86IMG in all caps and place on the root of your sdcard. Power down your phone, and boot up into bootloader and let your phone detect the file and confirm to update. Next you might want to get a drink or something to eat. It'll take like 10 minutes. Hope that helps
Click to expand...
Click to collapse
that will revert the s-off to right?
wikedone said:
that will revert the s-off to right?
Click to expand...
Click to collapse
No.
You need to issue the "fastboot oem writescureflag 3" command with the phone in fastboot USB mode after flashing the RUU to reset the S-OFF status to S-ON. Make sure you have the stock bootloader installed before you do that.
ramjet73
ramjet73 said:
No.
You need to issue the "fastboot oem writescureflag 3" command with the phone in fastboot USB mode after flashing the RUU to reset the S-OFF status to S-ON. Make sure you have the stock bootloader installed before you do that.
ramjet73
Click to expand...
Click to collapse
ok the file i downloaded is RUU_Shooter_ICS_35_S_Sprint_WWE_2.89.651.2_Radio_1.09.00.0706__NV_NV_SPCS_1.43_release_271101_signed.exe i just rename that to PG86IMG or what cuz when i run the ruu in windows it errors out with usb connectio error
wikedone said:
ok the file i downloaded is RUU_Shooter_ICS_35_S_Sprint_WWE_2.89.651.2_Radio_1.09.00.0706__NV_NV_SPCS_1.43_release_271101_signed.exe i just rename that to PG86IMG or what cuz when i run the ruu in windows it errors out with usb connectio error
Click to expand...
Click to collapse
The .exe version of the RUU needs to be run from Windows. Make sure your phone is in the "fastboot usb" mode in the bootloader and the "fastboot devices" command returns your serial number before you run the RUU.
There's also a .zip version of the RUU around somewhere on these forums that can be run from the bootloader, but I don't have a link to that. It would be safer to extract it yourself from the RUU.exe using this procedure.
ramjet73
ramjet73 said:
The .exe version of the RUU needs to be run from Windows. Make sure your phone is in the "fastboot usb" mode in the bootloader and the "fastboot devices" command returns your serial number before you run the RUU.
There's also a .zip version of the RUU around somewhere on these forums that can be run from the bootloader, but I don't have a link to that. It would be safer to extract it yourself from the RUU.exe using this procedure.
ramjet73
Click to expand...
Click to collapse
ok i got the ruu to run and the phone is updated to ICS the hboot says
*** LOCKED ***
SHOOTER XC SHIP S-OFF RL
HBOOT-1.58.0000
RADIO-1.09.00.0706
OpenADSP-v02.6.0.2226.00.0217
eMMC-boot
May 17 2012, 15:06:44
How do i know if i have the stock bootloader so i can Make it S-On
wikedone said:
ok i got the ruu to run and the phone is updated to ICS the hboot says
*** LOCKED ***
SHOOTER XC SHIP S-OFF RL
HBOOT-1.58.0000
^^^^^^^^^^^
How do i know if i have the stock bootloader so i can Make it S-On
Click to expand...
Click to collapse
That's the stock bootloader, which was installed by the RUU. Most of the custom bootloaders (Revolutionary, Juopunutbear) have their name where the "*** LOCKED ***" status shows on your phone.
ramjet73
It's also courtesy to hit the thank you button when someone has helped you (meaning ramjet) Just thought I would throw that out.
I have been trying to root my 3d for liek 2 days now and have searched every where and tried ever trick i can find. No matter what i cannot seem to figure out what is going on.
I am hboot 1.58 S-ON i keep getting an error that the RUU i have is not the right one i have downloaded 3 different ones and all say the same thing i have read many thread and tried many ways to root this thing. I relock before using RUU but no matter what i get this message. It also will not flash any recovery, It just gets stuck at "sending"
i have the right drivers and everything. my computer sees my phone when i type "fastboot devices". any help would be so great.
lulzy1 said:
I have been trying to root my 3d for liek 2 days now and have searched every where and tried ever trick i can find. No matter what i cannot seem to figure out what is going on.
I am hboot 1.58 S-ON i keep getting an error that the RUU i have is not the right one i have downloaded 3 different ones and all say the same thing i have read many thread and tried many ways to root this thing. I relock before using RUU but no matter what i get this message. It also will not flash any recovery, It just gets stuck at "sending"
i have the right drivers and everything. my computer sees my phone when i type "fastboot devices". any help would be so great.
Click to expand...
Click to collapse
Based on your bootloader version, it sounds like you have a Sprint Evo 3D. I have a guide here that should help you get the the right RUU flashed, then get root and S-OFF.
ramjet73
ramjet73 said:
Based on your bootloader version, it sounds like you have a Sprint Evo 3D. I have a guide here that should help you get the the right RUU flashed, then get root and S-OFF.
ramjet73
Click to expand...
Click to collapse
your guide is the first guide I tried with no luck.. and yes im sprint
lulzy1 said:
your guide is the first guide I tried with no luck.. and yes im sprint
Click to expand...
Click to collapse
Then you need to give more specifics. If you can post the header information displayed in your bootloader here, and give the text of the error messages you are getting when you try to flash the RUU contained in the download, that will make it easier to help.
Also, please issue the following commands from fastboot and post the output here:
fastboot getvar cid
fastboot getvar mainver
ramjet73
Definitely post up the information ramjet73 is asking for.
Btw ramjet, you are quick. You always beat me to it!
Also curious if you are running the Ruu while booted up or from fastboot?
This seems blaringly obvious but if you are s-on, did you relock the bootloader?
Sent from my PG86100 using Tapatalk 2
ramjet73 said:
Then you need to give more specifics. If you can post the header information displayed in your bootloader here, and give the text of the error messages you are getting when you try to flash the RUU contained in the download, that will make it easier to help.
Also, please issue the following commands from fastboot and post the output here:
fastboot getvar cid
fastboot getvar mainver
ramjet73
Click to expand...
Click to collapse
bootloader header
***unlocked*** (currently, as I relock it to run RUU)
SHOOTER XC SHIP S-ON RL
HBOOT-1.58.0000
eMMC-boot
C:\Users\lulzyl\Desktop\QADERSO\Root>fastboot getvar cid
cid: SPCS_001
finished. total time: -0.000s
C:\Users\lulzyl\Desktop\QADERSO\Root>fastboot getvar mainver
mainver: SPCS_001
finished. total time: 0.005s
My battery is too low to run RUU right and im about to go to sleep I will update with the exact wording tomorrow but it says that Do not have the right RUU for my device. and if i am remembering correctly it says error 155 but I cant be 100% positive.
what i am using is RUU_Shooter_ICS_35_S_Sprint_WWE_2.89.651.2_Radio_1.09.00.0706__NV_NV_SPCS_1.43_release_271101_signed
Brian706 said:
Also curious if you are running the Ruu while booted up or from fastboot?
This seems blaringly obvious but if you are s-on, did you relock the bootloader?
Click to expand...
Click to collapse
He said in the OP that "I relock before using RUU but no matter what i get this message", but that's why I want to see his bootloader info and the text of the message he is getting.
I always recommend starting the RUU.exe with the phone in "fastboot usb" mode, but in theory it should work even if he is booted into Android.
Let's see what he has to say.
lulzy1 said:
C:\Users\lulzyl\Desktop\QADERSO\Root>fastboot getvar mainver
mainver: SPCS_001
finished. total time: 0.005s
Click to expand...
Click to collapse
That mainver doesn't look right. I should be 2.89.651.2 if you are on hboot 1.58. If that's really the current mainver it would explain why you can't flash the RUU. I have no idea how that could have been changed without flashing something with an incorrect android-info.txt in a PG86IMG.zip file, which requires S-OFF, or someone setting the mainver incorrectly via ADB. Did you get the phone new or used?
Please verify that is correct, and if it is, it will need to changed before the RUU will take.
Also, when you try to run the RUU.exe again make sure the phone is in fastboot USB mode.
ramjet73
I will rerun the comand later to make sure, I always run it from fastboot usb. Also i got the phone as an insurance replacement. sprint sucks so bad there is no telling if the phone is actually new or not
ok.. update I redid your command this morning and got what you were looking for.
C:\Users\lulzy\Desktop\QADERSO\Root>fastboot getvar mainver
mainver: 2.89.651.2
finished. total time: 0.000s
here is what RUU continues to give me no matter if im in fastboot usb or just the home screen
ERROR [155]: UNKNOWN ERROR
The ROM Update Utility cannot update your android phone.
Please get the correct ROM Update Utility and try again.
This is using the one you have in your RUU file ramjet and when this happens i get the black HTC screen but it has no loading bar and nothing in all the corners
lulzy1 said:
here is what RUU continues to give me no matter if im in fastboot usb or just the home screen
ERROR [155]: UNKNOWN ERROR
The ROM Update Utility cannot update your android phone.
Please get the correct ROM Update Utility and try again.
This is using the one you have in your RUU file ramjet and when this happens i get the black HTC screen but it has no loading bar and nothing in all the corners
Click to expand...
Click to collapse
So your CID and mainver look OK.
The 155 error usually means your current bootloader is unlocked.
Try relocking your your bootloader, then remove and and replace the battery and start the bootloader. Since your bootloader is currently unlocked, the status should show as "*** RELOCKED ***". Make sure it does and that you are connected to your PC in "fastboot usb" mode, then try it again.
If that doesn't work, you can try downloading just the RUU.exe from here. It's the same one that is in the QADERSO .zip file, but it's worth a try.
ramjet73
during my previous attempt it was relocked, anytime i try running RUU from fastboot it says it cant run because my battery is too low (i have 93% battery and i dont get the warning if i run from the home screen) i cannot run RUU from fastboot because this is all i ever see even after re downloading
lulzy1 said:
during my previous attempt it was relocked, anytime i try running RUU from fastboot it says it cant run because my battery is too low (i have 93% battery and i dont get the warning if i run from the home screen) i cannot run RUU from fastboot because this is all i ever see even after re downloading
Click to expand...
Click to collapse
The battery low indicator in fastboot mode sounds like a hardware problem to me. If your battery isn't charging correctly it may be a problem with your cable or USB port. Many people have gotten the RUU.exe to flash successfully by changing to a different cable and/or PC, but if you can't do that I suggest fully charging the battery with the A/C adapter that came with the phone before trying to flash the RUU.exe again.
Flashing the RUU.exe with the phone in Android mode may be masking the problem, but something is not right with your hardware.
ramjet73
all done!! different computer and cord works.
Thanks alot
How do you relock the hboot? I'm getting the same error. Thanks.
"fastboot OEM lock"
Phone:
Sprint HTC EVO 3D
Root & S-Off(JBear)
HBoot: JBear 1.58.5858
Firmware: 2.89.651.5
Radio: 1.09.00.0706
Rom: FroZenROM Ep 2.1
Kernel: AnthraX 2.7.0
Recovery: TWRP 2.3.3.0
SDCard: San Disk 64GB Extreme Class 10 UHS-1 (Low External Storage Wizard? Uninstall)
i need help
i need some help fixing my phone i rooted it had it working well for about 2 hours changed somthing now im stuck on the htc green and white sceen
my bootloader says relocked ive been trying to follow the guides but nothing seems to work, right now the phone is in the bootloader as thats all ive been able to access i have a virgin mobile evo 3d with hboot 1.58..can somebody please help me? or is my phone screwed?
Your phone is not screwed
What did you change? I'm guessing you either flashed a rom that's incompatible with your current hboot or you are s-on and need to flash the kernel separately.
What recovery do you have installed?
Brian706 said:
Your phone is not screwed
What did you change? I'm guessing you either flashed a rom that's incompatible with your current hboot or you are s-on and need to flash the kernel separately.
What recovery do you have installed?
Click to expand...
Click to collapse
thanks for the response but i actually managed to fix it yesterday. idk what i changed but i was using the clockworld recovery but it wouldnt install the stock shooter file so i used 4ext and its all bueno now except it boots as a sprint phone now but whatever i can deal with that
Glad you got it!
I'd stick with 4ext. I have heard cwm doesn't play well with this device but have not experienced it first hand.
Yea I won't be putting that back on my phone now I have a question I believe I have the vmobile stock shooter on my pc I need to fast boot that to get my splash screen and stuff back right? Cause right now when I turn it on it says sprint
Hi.
I unlocked a bootloader and rooted my htc one. Then I flashed viperOne rom.
The problem is I need to get back to stock so my warranty is still valid.
How do i do that? I am scared of those long-named firmware zips and exes.
I dont know which info will be useful so I'm postin' all of it:
***TAMPERED***
***UNLOCKED***
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.17.3250.14
OpenDSP-v31.120.274.0617
OS-2.24.401.1
eMMC-boot 2048MB
adammo666 said:
Hi.
I unlocked a bootloader and rooted my htc one. Then I flashed viperOne rom.
The problem is I need to get back to stock so my warranty is still valid.
How do i do that? I am scared of those long-named firmware zips and exes.
I dont know which info will be useful so I'm postin' all of it:
***TAMPERED***
***UNLOCKED***
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.17.3250.14
OpenDSP-v31.120.274.0617
OS-2.24.401.1
eMMC-boot 2048MB
Click to expand...
Click to collapse
Download and run an RUU
Clownzer said:
Download and run an RUU
Click to expand...
Click to collapse
I know that but I don't know which one...
adammo666 said:
I know that but I don't know which one...
Click to expand...
Click to collapse
htcdev website has RUU for every version. Just filter the one for AT&T and that is it.
The easiest way to do that is to put the device into Fastboot Mode:
1. Boot the device into bootloader (Disable Fastboot, Power off device, Press + hold volume down and power on)
2. Navigate to Fastboot using the volume buttons. Select with power
3. Connect device to PC. “Fastboot” should change to say “Fastboot USB”
4. Execute the RUU (Rom Update Utility)
You can also do it using HTC Sync Manager. I will provide you with the instructions.
1. Download and install HTC Sync Manager from http://www.htc.com/www/software/htc-sync-manager/
2. Once it is installed proceed with step three.
3. Power down the phone
4. Power on the phone by holding volume down + power
5. Fastboot is already highlighted by default, tap power to go into it and plug the phone into the computer.
a. Note: If all drivers installed properly, you should see a change on the screen that says “fastboot usb” in red.
6. Run the RUU that was downloaded from the website and follow the on-screen directions.
a. Note: If done correctly, the screen on the phone will change to solid black and say “HTC” in grey letters and proceed to flash the phone
:3
All in One toolkit should help. Just use the commands tab and follow the steps :3
http://forum.xda-developers.com/showthread.php?t=2183942
You're not going to get far. 1.54 HBOOT and S-ON. Big problem. RUU won't work since the HBOOT is newer and because the device is S-ON. Need to either have the same HBOOT as the RUU, or S-OFF to prevent the security check.
Best you can do is flash a stock AT&T rom, but you will still be tampered and unlock in the bootloader.
So I've been struggling for the last 4 days now with the following situation:
A part of my touchscreen (a horizontal line in the middle of my screen), stopped working and I want to make use of the warranty.
Since I've unlocked and flashed my phone I'll need to return it to stock first.
I've tried a lot of RUU's all saying "ROM Image Error". (Of course relocked my phone everytime before running a RUU).
The things I already tried hoping the RUU would work:
- flashing different roms
- flashing different kernels
- flashing different recovery's
- restoring someone else's backup using TWRP
At the moment I'm close to giving up, leaving me with this actual state:
***UNLOCKED***
ENRC2B_U PVT SHIP S-ON RL
HBOOT 1.72.0000
CPLD-NONE
MICROP-NONE
RADIO 3.1204.171.33
eMMC-bootmode: Disabled
CPU-bootmode: Disabled
HW Secure boot: Enabled
MODEM PATH: OFF
TWRP 2.3.2.3
CyanogenMod 10.2.1-enrc2b
Android 4.3.1
Kernel version 3.1.10-g0324fc1
(also tried it on Windows 7 instead of a Windows 8.1)
I can't imagine there isn't a solution to get a RUU working.
jimscheltus said:
So I've been struggling for the last 4 days now with the following situation:
A part of my touchscreen (a horizontal line in the middle of my screen), stopped working and I want to make use of the warranty.
Since I've unlocked and flashed my phone I'll need to return it to stock first.
I've tried a lot of RUU's all saying "ROM Image Error". (Of course relocked my phone everytime before running a RUU).
The things I already tried hoping the RUU would work:
- flashing different roms
- flashing different kernels
- flashing different recovery's
- restoring someone else's backup using TWRP
At the moment I'm close to giving up, leaving me with this actual state:
***UNLOCKED***
ENRC2B_U PVT SHIP S-ON RL
HBOOT 1.72.0000
CPLD-NONE
MICROP-NONE
RADIO 3.1204.171.33
eMMC-bootmode: Disabled
CPU-bootmode: Disabled
HW Secure boot: Enabled
MODEM PATH: OFF
TWRP 2.3.2.3
CyanogenMod 10.2.1-enrc2b
Android 4.3.1
Kernel version 3.1.10-g0324fc1
(also tried it on Windows 7 instead of a Windows 8.1)
I can't imagine there isn't a solution to get a RUU working.
Click to expand...
Click to collapse
Your right, you can't restore using an RUU past hboot version 0.4. However here is the latest stock backup. If you restore in TWRP and then flash the firmware.zip you end up with at least a look alike stock. I think you can also modify the "relocked" message in the bootloader to "locked" once more. This should fool the shop/retailer easily!
file are here: http://forum.xda-developers.com/showthread.php?t=2414238
I had an issue with the file service though. If that happens then just download the megadownloader program to download it properly
Hope this helps.
Dr.ripsaw said:
Your right, you can't restore using an RUU past hboot version 0.4. However here is the latest stock backup. If you restore in TWRP and then flash the firmware.zip you end up with at least a look alike stock. I think you can also modify the "relocked" message in the bootloader to "locked" once more. This should fool the shop/retailer easily!
file are here: http://forum.xda-developers.com/showthread.php?t=2414238
I had an issue with the file service though. If that happens then just download the megadownloader program to download it properly
Hope this helps.
Click to expand...
Click to collapse
Alright, It's worth the try. Also, will this change my Hboot version?
I also found out it's impossible to get the 'LOCKED' message back. Relocked is as close we can get :')
But that doesn't automatically mean that the warranty won't pay the repair. When they find a custom rom on your phone it's a different story though. This because a custom rom could mean I overclocked my CPU for example.
jimscheltus said:
Alright, It's worth the try. Also, will this change my Hboot version?
I also found out it's impossible to get the 'LOCKED' message back. Relocked is as close we can get :')
But that doesn't automatically mean that the warranty won't pay the repair. When they find a custom rom on your phone it's a different story though. This because a custom rom could mean I overclocked my CPU for example.
Click to expand...
Click to collapse
Well When I got my phone I allowed it to update to the latest version of android and so it upgraded my Hboot version. To get the latest version you need to flash the latest firmware. I think restoring a backup that is the newest version of stock will automatically update your Hboot. Don't take my word for it as I've said my Hboot was fully updated before I started Modding.