Related
Okay guys, i flashed the 2.3.4 ota as soon as it came out (before all this trouble with it of course) and now i am stuck because i was under the impression that the new bootloader would be unlocked so i had never even though about eating any pudding before the fact. Now i come to my trouble, im running a totally stock 2.3.4 att and i cant seem to find a way out.
Question #1- If i have a locked bootloader can i fruitcake back?
Question #2- Is there a possible way to unlock the new bootloader?
Question #3- How in heck do i get root, im on windows 7 and i recently tried the two bat files that one of the devs released and they were a no go, it didnt seem to flash the preinstall when i tried to look for it, it wasnt there. I have been quietly trying to fix this on my own for days now i am asking for a little help. Im stumped.
I got root using the /preinstall method with those 2 .bat files posted yesterday.
From page 30-35 is the guidance I followed from mramirezusa.
Other than that we are in the same boat.. I read puddings will flash relatively safely.http://forum.xda-developers.com/showthread.php?t=1159950&page=30
cthomas5714 said:
Okay guys, i flashed the 2.3.4 ota as soon as it came out (before all this trouble with it of course) and now i am stuck because i was under the impression that the new bootloader would be unlocked so i had never even though about eating any pudding before the fact. Now i come to my trouble, im running a totally stock 2.3.4 att and i cant seem to find a way out.
Question #1- If i have a locked bootloader can i fruitcake back?
Question #2- Is there a possible way to unlock the new bootloader?
Question #3- How in heck do i get root, im on windows 7 and i recently tried the two bat files that one of the devs released and they were a no go, it didnt seem to flash the preinstall when i tried to look for it, it wasnt there. I have been quietly trying to fix this on my own for days now i am asking for a little help. Im stumped.
Click to expand...
Click to collapse
Question #2- Is there a possible way to unlock the new bootloader? yes use pudding
cthomas5714 said:
Okay guys, i flashed the 2.3.4 ota as soon as it came out (before all this trouble with it of course) and now i am stuck because i was under the impression that the new bootloader would be unlocked so i had never even though about eating any pudding before the fact. Now i come to my trouble, im running a totally stock 2.3.4 att and i cant seem to find a way out.
Question #1- If i have a locked bootloader can i fruitcake back?
Question #2- Is there a possible way to unlock the new bootloader?
Question #3- How in heck do i get root, im on windows 7 and i recently tried the two bat files that one of the devs released and they were a no go, it didnt seem to flash the preinstall when i tried to look for it, it wasnt there. I have been quietly trying to fix this on my own for days now i am asking for a little help. Im stumped.
Click to expand...
Click to collapse
hey man first things first. dont panic, you are not stuck. this is temporary at best, in the mean while theres plenty of stuff you can do, sbf is not safe to begin with. so actually be gladd you only got to use RSD one time
first things first, get yourselfed unlocked, pudding will do the trick. once after pudding, you never have to touch RSD
Once you are done with pudding go ahead and get tenfars unlocked cwm
once you are done with that you are free to flash pretty much all the roms, as usually custom roms, or fruit cakes dont have bl, only the rest
enjoy
Okay guys, thanks for your help. but let me get this clear, i do not have a unlocked bootloader, im a pudding virgin. I can simply rsd the 1.83 with pudding and thats it? No worries no nothing?
cthomas5714 said:
Okay guys, thanks for your help. but let me get this clear, i do not have a unlocked bootloader, im a pudding virgin. I can simply rsd the 1.83 with pudding and thats it? No worries no nothing?
Click to expand...
Click to collapse
Yes but you still can't use any other sbf. I'd use the raw pudding sbf, unlock, then use CWM from here on out. No more rsd
Sorry about that. There is just the unlock and then the unlock packaged with 1.8.3. The one that has has been causing bricks from my understanding is the packaged one. Be sure you flash just the unlock.
Anyone know what exactly will be erased from /data after flashing the unlock? Also I don't want to restore backed up files that will conflict with new ones. Any guidance on this is appreciated.
snudmusk said:
Sorry about that. There is just the unlock and then the unlock packaged with 1.8.3. The one that has has been causing bricks from my understanding is the packaged one. Be sure you flash just the unlock.
Anyone know what exactly will be erased from /data after flashing the unlock? Also I don't want to restore backed up files that will conflict with new ones. Any guidance on this is appreciated.
Click to expand...
Click to collapse
All user data is wiped when unlocking. The 1.8.3 sbf with pudding is safe to flash but i recommend just using pudding and then CWM and ditch rsd.
jruweaver said:
All user data is wiped when unlocking. The 1.8.3 sbf with pudding is safe to flash but i recommend just using pudding and then CWM and ditch rsd.
Click to expand...
Click to collapse
Agree, just use the pudding only sbf. to unlock , then preinstall to get root.
Make sure to have 50 or so battery so you don't run into the trouble I had with battery being to low to fastboot. Also once you flash pudding you wont be able to boot the phone, don't panic just follow steps to fastboot oem unlock and phone will boot fine afterwards.
Sent from my MB860 using Tapatalk
woahh no bad idea, im scared. I did exactly as you all said and it acts like its hard bricked, SVF:105 error but then it says no OS detected and i have 14 options
1RSD
2Fastboot
3Nvflash
4-9BP something
9Android recovery
10Boot android (no bp)
11Device UID
12Console
13early usb enumeration
14BP tools
WHAT DO I DO?
cthomas5714 said:
woahh no bad idea, im scared. I did exactly as you all said and it acts like its hard bricked, SVF:105 error but then it says no OS detected and i have 14 options
1RSD
2Fastboot
3Nvflash
4-9BP something
9Android recovery
10Boot android (no bp)
11Device UID
12Console
13early usb enumeration
14BP tools
WHAT DO I DO?
Click to expand...
Click to collapse
Which did you flash? Pudding or 1.8.3 with pudding?
Try connecting your phone to pc select fastboot and finish the pudding instructions (fastboot oem unlock)
It might boot then.
Sent from my MB860 using XDA Premium App
Here is what I did.
1. If you were to update to the OTA 4.5.91. Or already on the OTA 4.5.91 you can still unlock your bootloader.
2. Flash pudding only SBF so you can unlock the bootloader. http://diamantephoto.com/fastboot.rar direct link. Flash this one.
http://forum.xda-developers.com/show....php?t=1136261 Original Post about pudding.
It will go to a text only 14 option screen and say something like boot failed 0x1000. Don't freak out and tell me you bricked you phone blah blah blah. You still have to unlock the bootloader by choosing fastboot from your phone and connecting it to the computer via usb. Make sure you have ADB with fastboot tools installed on you computer.
Open command prompt from you computer and type fastboot oem unlock. It'll display warning about voiding warranty and a unique device id. Type again fastboot oem unlock ############. The # are the unique device numbers. Don't type # it wont work. The instructions are posted on the pudding thread if you would like to read more about it.
Then type fastboot reboot to reboot. Unlock should be displayed on top left of screen and it'll take 5 long mins to boot up.
3.Then you need to install CWM and root.
You'll find instructions in the developers form. But if your lazy here is the CWM link. http://forum.xda-developers.com/show....php?t=1138541 follow the instructions or every time you reboot you will loose CWM. For root there are two available for gingerbread. http://forum.xda-developers.com/show....php?t=1140110 I used this one and got root.
http://forum.xda-developers.com/show....php?t=1138204 I hear this works too.. Haven't tested read the post if you want to use this method.
As always don't blame me for bricking if you happen to do so. DO IT AT YOUR OWN RISK. these are the steps I took to unlock and everything works great. Absolutely no problems with my phone after wards.
One thing unlocking your bootloader will format/erase data. Basically a factory data reset so make sure you backup everything with titanium or you favorite app. I would not restore system apps as i've had a few problems with email and motoblur force closes.
Is there a way to root without unlocking the bootloader?
five3zero said:
Is there a way to root without unlocking the bootloader?
Click to expand...
Click to collapse
Yes.
Follow the instructions listed on here:
http://forum.xda-developers.com/showthread.php?p=15023030
The 3rd post has the instructions I followed.
If you have problems be sure to read through the thread as someone else has most likely already had the same issue.
This worked for me.
cthomas5714 said:
woahh no bad idea, im scared. I did exactly as you all said and it acts like its hard bricked, SVF:105 error but then it says no OS detected and i have 14 options
1RSD
2Fastboot
3Nvflash
4-9BP something
9Android recovery
10Boot android (no bp)
11Device UID
12Console
13early usb enumeration
14BP tools
WHAT DO I DO?
Click to expand...
Click to collapse
Just do: fastboot oem unlock (or whatever tthe code is)
Them: fastboot reboot
Sent from my MB860 using XDA App
So guys I really wanna unlock the bootloader and flash some roms but this is my third atrix. Im using the 14 day grace period very very graciously. Anyways first atrix kept locking up- exchanged. Second one I tried to unlock it with pudding. Did the rsd thing with the. Sbf file and I was doing it. Then toward the end it failed. Complete brick- exchanged.
Anyways is there something else I should do, possibly a different route? Im using an AT&T atrix. Thanks.
Wait for official release and get it officially unlocked?
Sent from my MB860 using XDA Premium App
tsouza said:
Wait for official release and get it officially unlocked?
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
I can wait for the release, but are they unlocking it with it. For sure?
Well, IMO better hope for it than risk another brick...
Sent from my MB860 using XDA Premium App
tsouza said:
Well, IMO better hope for it than risk another brick...
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
True. Very true.
magicriggs said:
So guys I really wanna unlock the bootloader and flash some roms but this is my third atrix. Im using the 14 day grace period very very graciously. Anyways first atrix kept locking up- exchanged. Second one I tried to unlock it with pudding. Did the rsd thing with the. Sbf file and I was doing it. Then toward the end it failed. Complete brick- exchanged.
Anyways is there something else I should do, possibly a different route? Im using an AT&T atrix. Thanks.
Click to expand...
Click to collapse
I think you might have returned the first 2 prematurely.
1st one probably could have factory reset or flashed a new sbf
2nd one was probably a fixable soft brick.
So I'd say you're safe, but up to you as there's always a risk.
Here is what I did.
1. If you were to update to the OTA 4.5.91. Or already on the OTA 4.5.91 you can still unlock your bootloader.
2. Flash pudding only SBF so you can unlock the bootloader. http://diamantephoto.com/fastboot.rar direct link. Flash this one.
http://forum.xda-developers.com/showthread.php?t=1136261 Original Post about pudding.
It will go to a text only 14 option screen and say something like boot failed 0x1000. Don't freak out and tell me you bricked you phone blah blah blah. You still have to unlock the bootloader by choosing fastboot from your phone and connecting it to the computer via usb. Make sure you have ADB with fastboot tools installed on you computer.
Open command prompt from you computer and type fastboot oem unlock. It'll display warning about voiding warranty and a unique device id. Type again fastboot oem unlock ############. The # are the unique device numbers. Don't type # it wont work. The instructions are posted on the pudding thread if you would like to read more about it.
Then type fastboot reboot to reboot. Unlock should be displayed on top left of screen and it'll take 5 long mins to boot up.
3.Then you need to install CWM and root.
You'll find instructions in the developers form. But if your lazy here is the CWM link. http://forum.xda-developers.com/showthread.php?t=1138541 follow the instructions or every time you reboot you will loose CWM. For root there are two available for gingerbread. http://forum.xda-developers.com/show....php?t=1140110 I used this one and got root.
http://forum.xda-developers.com/show....php?t=1138204 I hear this works too.. Haven't tested read the post if you want to use this method.
As always don't blame me for bricking if you happen to do so. DO IT AT YOUR OWN RISK. these are the steps I took to unlock and everything works great. Absolutely no problems with my phone after wards.
One thing unlocking your bootloader will format/erase data. Basically a factory data reset so make sure you backup everything with titanium or you favorite app. I would not restore system apps as i've had a few problems with email and motoblur force closes.
Sent from my MB860 using Tapatalk
magicriggs said:
I can wait for the release, but are they unlocking it with it. For sure?
Click to expand...
Click to collapse
not sure. i got a leaked 4.5.91 build, it's not unlocked (although early beta does). you still have to flash the pudding img yourself.
delect this post
The returns were genuine. I did a factory reset on the first one and it still kept locking up, on the wake up. Had to pull battery out to turn back on. Multiple times. Second one was a complete brick. I couldn't get into rsd, wouldn't turn on and computer didn't recognize it in any mode. Im pretty familiar with rsd, used it with OG and X but this one got me walking om egg shells.
magicriggs said:
The returns were genuine. I did a factory reset on the first one and it still kept locking up, on the wake up. Had to pull battery out to turn back on. Multiple times. Second one was a complete brick. I couldn't get into rsd, wouldn't turn on and computer didn't recognize it in any mode. Im pretty familiar with rsd, used it with OG and X but this one got me walking om egg shells.
Click to expand...
Click to collapse
hmm you are very unlucky then. You're the only one to hard brick from pudding. Probably advise you not to do anything with your phone.
Jnewell05 said:
Here is what I did.
1. If you were to update to the OTA 4.5.91. Or already on the OTA 4.5.91 you can still unlock your bootloader.
Click to expand...
Click to collapse
im on build number 4_1.8.3 and i check for updates and it says my device is up to date. any
ideas?
magicriggs said:
im on build number 4_1.8.3 and i check for updates and it says my device is up to date. any
ideas?
Click to expand...
Click to collapse
4.1.83 is a great point to unlock the bootloader. DO NOT install the 4.5.91 OTA udpate, too risky to hard brick if you flashed an sbf. Of course, you don't have to sbf back anymore, but I would steer way clear of that when there are perfectly good options available. Only use customized ones like Kenneth's or the CherryBlur ROM. More will start flowing soon.
So what your advising is not to even unlock it. All I really want is volume wake.
magicriggs said:
So what your advising is not to even unlock it. All I really want is volume wake.
Click to expand...
Click to collapse
That's the exact opposite of what I'm advising. I knew I was taking some level of risk when I unlocked, but it's a risk well worth taking. Very, very low failure rate. Recoverable. But I can't accept the risk for your phone.
OSNPA said:
That's the exact opposite of what I'm advising. I knew I was taking some level of risk when I unlocked, but it's a risk well worth taking. Very, very low failure rate. Recoverable. But I can't accept the risk for your phone.
Click to expand...
Click to collapse
Oh gotcha. Thanks for the info.
Jnewell05 said:
Here is what I did.
1. If you were to update to the OTA 4.5.91. Or already on the OTA 4.5.91 you can still unlock your bootloader.
2. Flash pudding only SBF so you can unlock the bootloader. http://diamantephoto.com/fastboot.rar direct link. Flash this one.
http://forum.xda-developers.com/showthread.php?t=1136261 Original Post about pudding.
It will go to a text only 14 option screen and say something like boot failed 0x1000. Don't freak out and tell me you bricked you phone blah blah blah. You still have to unlock the bootloader by choosing fastboot from your phone and connecting it to the computer via usb. Make sure you have ADB with fastboot tools installed on you computer.
Open command prompt from you computer and type fastboot oem unlock. It'll display warning about voiding warranty and a unique device id. Type again fastboot oem unlock ############. The # are the unique device numbers. Don't type # it wont work. The instructions are posted on the pudding thread if you would like to read more about it.
Then type fastboot reboot to reboot. Unlock should be displayed on top left of screen and it'll take 5 long mins to boot up.
3.Then you need to install CWM and root.
You'll find instructions in the developers form. But if your lazy here is the CWM link. http://forum.xda-developers.com/showthread.php?t=1138541 follow the instructions or every time you reboot you will loose CWM. For root there are two available for gingerbread. http://forum.xda-developers.com/show....php?t=1140110 I used this one and got root.
http://forum.xda-developers.com/show....php?t=1138204 I hear this works too.. Haven't tested read the post if you want to use this method.
As always don't blame me for bricking if you happen to do so. DO IT AT YOUR OWN RISK. these are the steps I took to unlock and everything works great. Absolutely no problems with my phone after wards.
One thing unlocking your bootloader will format/erase data. Basically a factory data reset so make sure you backup everything with titanium or you favorite app. I would not restore system apps as i've had a few problems with email and motoblur force closes.
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
i used update.zip ..did not flash back to 1.83...update.zip (blur 1.83 etc etc) was from leaked moto servers...i have new bootloader cause my andriod recovery is different...of course BL is locked....can i still unlock??
HI hope someone can help me with this, i have tried without success to unlock my bootloader, i have updated to hboot 1.02 but when i try to do the fastboot flash unlocktoken Unlock_code.bin it sits at 0percent and doesn't move and no errors, i've tried this with my goldcard in and out of the phone and with cyanogen and b08 roms, also for some reason i can't flash the stock rom so i can get the required update from htc(thinking that's y the unlock code won't go), i've tried getting numerous ruu's and i was getting signature verification fails every time, i tried with windows the exe and also exracted the rom.zip and still no luck, i prefer using linux and adb though and tried numerous ways to get this to work with no success, i've also tried signing a rom.zip and the phone just says no signature, also tried renaming to LEGEIMG.zip and update.zip and just can't flash stock rom, also made a new goldcard thinking the other was bad and did the htcdev for the unlock code with a goldcard and without, also tried the ruu.exe in windows with new said goldcard and i think the other was bad because i get a different error now for reason it can't update my rom(was using the rom i originally rooted with which has sense). it says wrong bootloader version when i try and update, anyone know what i can do, i'm running outta ideas, thanks in advance
I Unlocked my bootloader with HTCdev. You said you tried. What went wrong?
If you have updated your phone to one of the ruus HTC gives you ( execute the exe ), there shouldn't be any problem : the HTC guide is clear and easy. If you have successuffly unlocked the bootloader, now you have to flash the clockwork recovery.
when i go to fastboot it stays on copying at 0 percent with the unlock_code.bin....My phone has root access before i ran the hboot update and still does but i can't flash the new ruu, it won't allow me to, i tried running the htc ruu and it fails with can't update, bootloader version incorrect, i tried with the b-08 rom, i can't get back to stock
Have you tried flashing this? ----> http://forum.xda-developers.com/showthread.php?t=1497357
If you don't install one of the updates given by HTC, bootloader unlock won't work. If you have the same problems that I had ( my Legend also wasn't rooted ) the RUUs won't install, right? I flashed first this one and then one of the HTC RUUs and after this everything worked perfectly.
nope, i didn't try that one yet, but the thing is my legend was rooted before i tried flashing these htc ruus, i just want my bootloader unlocked, i had cyanogen on it then flashed a rooted one with sense (b08) thinking that would let me update but it didn't, so i'm downloading that one you pointed me to now, i'll try and flash it and let you know how it goes.
When i flash that rom i get a main version is older error when i rename it to LEGEIMG and flash it via fastboot, what can i do now?
I followed Blayo's guide http://forum.xda-developers.com/showpost.php?p=22613990&postcount=62 with my already rooted Legend. Try to follow exactly. You said using a gold card - don't think this is even necessary. At least I did not use one, and it is working perfectly.
After flashing the new bootloader, did you really unlock?
(last step of guide above: follow the instructions on HTCdev from Step 8 to unlock)
Wait, all the RUUs you have to flash before unlocking are HTC's executable files ( .exe ). You have updated your phone executing them, haven't you? After that I just rebooted my phone to fastboot and connected it. I found the unlock code, sent it to HTCdev, received an e-mail with the file to complete unlock and then unlocked. I never used anything like UPDATE.zip or LEGEIMG. I tried following the BlaYo's instructions but they didn't work for me. I just did what HTC said ( easyer and safer ).
hmmmmm
hello guys... pwde ba ko mag unlock ng bootloader my x8 stiker is 11w48?
astig_king24 said:
hello guys... pwde ba ko mag unlock ng bootloader my x8 stiker is 11w48?
Click to expand...
Click to collapse
keyboard error?!
i solved my problem, i sold the phone and bought another legend. LOL, no seriously though, i did sell it and got another but i tried everything and couldn't unlock bootloader, i tried the exe files from htc, tried extracting the zip files, tried fastboot and renaming to LEGEIMG, just couldn't get it unlocked, so i flashed the latest cyanogen 7.2 and sold the darn thing, now i got another and made 50$ in the process as i bought the new one 50$ cheaper and i'm going to go through the htc channels to unlock the bootloader but does anyone know if i'll be able to flash cm7 after i do that?
bootloader
I have a similar problem with my Legend i had already rooted my legend following this guide http://chrg.zxq.net/htc-legend-root.html. I decided to unlock the bootloader folowing the guide on HTC dev to the letter and it worked fine bootloader unlocked. Only prolem is after rooting the phone again and flashing cm7 the bootloader is now locked again. What to do any ideas id be very greatfull.
sam0056 said:
I have a similar problem with my Legend i had already rooted my legend following this guide http://chrg.zxq.net/htc-legend-root.html. I decided to unlock the bootloader folowing the guide on HTC dev to the letter and it worked fine bootloader unlocked. Only prolem is after rooting the phone again and flashing cm7 the bootloader is now locked again. What to do any ideas id be very greatfull.
Click to expand...
Click to collapse
What do you mean with 'rooting again'? Once you have unlocked bootloader, you are able to flash a recovery, and then CM, which is rooted. See http://forum.xda-developers.com/showthread.php?p=24102979 for latest Recovery and latest CM7.2 builds
Ok just to update i flashed the HTC dev bin file again and had restore cm7 backup and bootloader is unlocked once again.
got her goin good now, unlocked bootloader with htcdev, fastboot flashed cwm, then i was able to flash cm7.2 and gapps no problem at all, now if we could only s-off the legend???
dantheman1977 said:
... now if we could only s-off the legend???
Click to expand...
Click to collapse
For what reason? It's quite similar
Because it's still not totally unlocked
dantheman1977 said:
i solved my problem, i sold the phone and bought another legend. LOL, no seriously though, i did sell it and got another but i tried everything and couldn't unlock bootloader, i tried the exe files from htc, tried extracting the zip files, tried fastboot and renaming to LEGEIMG, just couldn't get it unlocked, so i flashed the latest cyanogen 7.2 and sold the darn thing, now i got another and made 50$ in the process as i bought the new one 50$ cheaper and i'm going to go through the htc channels to unlock the bootloader but does anyone know if i'll be able to flash cm7 after i do that?
Click to expand...
Click to collapse
After unlocking boot loader:
1. Use htcsupertoolv3 to root
2. Install rom manager and titanium backup
3. Run titanium backup. It will ask you to update su. accept (i'm not sure if this step is required, but this is how i done it)
4. Copy recovery-clockwork-5.0.2.0-legend to your Android folder created during bootloader unlock
5. With your phone on fastboot mode open terminal in your PC android folder and type:
fastboot flash recovery recovery-clockwork-5.0.2.0-legend.img
Your phone will go to recovery mode.
6. Reboot your phone in normal mode
7. From now on, each time you want to go into recovery, use rom manager
Done
dantheman1977 said:
Because it's still not totally unlocked
Click to expand...
Click to collapse
So for what I have understood from HTCdev, you can do everything similar to S-OFF, with one exception: you cannot unlock a SIM lock.
Oops... said:
So for what I have understood from HTCdev, you can do everything similar to S-OFF, with one exception: you cannot unlock a SIM lock.
Click to expand...
Click to collapse
True, you can't. I'm not sure if flashing a custom rom will unlock it, as my phone sim card was unlocked from very beginning. Probably not?
So I discovered a slight gap on certain edges of my One, which I got a week ago, and want to return it to AT&T for one that hopefully has no issues, but I've rooted, unlocked the bootloader, and flashed CM 10.1 on there. I searched through google and the forums here on XDA to find a method to relock the bootloader and go back to stock, but my search was fruitless. Apparently something called an RUU was needed? And according to the last post in this thread, that isn't available.
Is the RUU available now? Or is it currently impossible to relock the bootloader?
If so, would I be able to pull off just flashing the stock ROM back onto the phone and bringing it into AT&T? I feel like the only way they would realize something was different with the phone would be if they rebooted it, as I highly doubt most of the people in that store could even get into the bootloader screen. They had trouble syncing my google account.
Unless, of course, they send it back to the manufacturer and then THEY say that the warranty is voided because of the unlocked bootloader... but I don't know if they go through all that trouble in this situation?
Thanks for the help.
CAC1291 said:
So I discovered a slight gap on certain edges of my One, which I got a week ago, and want to return it to AT&T for one that hopefully has no issues, but I've rooted, unlocked the bootloader, and flashed CM 10.1 on there. I searched through google and the forums here on XDA to find a method to relock the bootloader and go back to stock, but my search was fruitless. Apparently something called an RUU was needed? And according to the last post in this thread, that isn't available.
Is the RUU available now? Or is it currently impossible to relock the bootloader?
If so, would I be able to pull off just flashing the stock ROM back onto the phone and bringing it into AT&T? I feel like the only way they would realize something was different with the phone would be if they rebooted it, as I highly doubt most of the people in that store could even get into the bootloader screen. They had trouble syncing my google account.
Unless, of course, they send it back to the manufacturer and then THEY say that the warranty is voided because of the unlocked bootloader... but I don't know if they go through all that trouble in this situation?
Thanks for the help.
Click to expand...
Click to collapse
For a quick and easy way, just boot into fast boot and cmd "fastboot oem lock"
The only problem with that is that if they DO boot into the bootlaoder, it will say "RELOCKED" instead of "LOCKED"
The longer way, is to S-OFF (find it in the international forum) and then follow instructions there to put the "LOCKED" text back.
CAC1291 said:
So I discovered a slight gap on certain edges of my One, which I got a week ago, and want to return it to AT&T for one that hopefully has no issues, but I've rooted, unlocked the bootloader, and flashed CM 10.1 on there. I searched through google and the forums here on XDA to find a method to relock the bootloader and go back to stock, but my search was fruitless. Apparently something called an RUU was needed? And according to the last post in this thread, that isn't available.
Is the RUU available now? Or is it currently impossible to relock the bootloader?
If so, would I be able to pull off just flashing the stock ROM back onto the phone and bringing it into AT&T? I feel like the only way they would realize something was different with the phone would be if they rebooted it, as I highly doubt most of the people in that store could even get into the bootloader screen. They had trouble syncing my google account.
Unless, of course, they send it back to the manufacturer and then THEY say that the warranty is voided because of the unlocked bootloader... but I don't know if they go through all that trouble in this situation?
Thanks for the help.
Click to expand...
Click to collapse
Get S-OFF, I was able to remove TAMPERED and change my UNLOCKED to LOCKED. You can also flash a modded HBoot that will take the red letters away and change the text from S-OFF to S-ON this will allow it to look like you never touched a thing
To get S-OFF I recommend http://forum.xda-developers.com/showthread.php?t=2314582
To mod your HBoot go through the post from here http://forum.xda-developers.com/showthread.php?t=2316726 (to download the HBOOT and here http://forum.xda-developers.com/showthread.php?t=1786498 to download the tool to create the modified HBOOT
But to let you know, I have returned 2 HTC Ones with unlocked bootloaders and AT&T did not say anything. Just flash the stock rom, make sure fastboot in enabled and leave it booted to the set up screen. Above is for if you want to be thorough and make sure you cover all your bases.
hi i need help. so here is what happened. i have a sprint htc one max. i unlocked the bootloader and rooted the phone. flashed a custom rom on it and had it flashed to page plus and no problems with the phone. when i saw that it could be unlocked. i tried the steps to relock my bootloader and then things when wrong. i relocked my bootloader but now i am stuck in bootloader mode and cant enter recovery. i have been reading in the forums but nothing seems to be a clear solution to me. i tried to install the RUU from sprint and it wont load. i get ERROR 133 (if i am not mistaken) and when i try to find the phone on adb it wont show up. so now i am hoping someone can guide me or show me what i need to do. if not i guess i have a new fancy paper weight hahaha. thanks guys appreciate it.
luisdelvalle1 said:
hi i need help. so here is what happened. i have a sprint htc one max. i unlocked the bootloader and rooted the phone. flashed a custom rom on it and had it flashed to page plus and no problems with the phone. when i saw that it could be unlocked. i tried the steps to relock my bootloader and then things when wrong. i relocked my bootloader but now i am stuck in bootloader mode and cant enter recovery. i have been reading in the forums but nothing seems to be a clear solution to me. i tried to install the RUU from sprint and it wont load. i get ERROR 133 (if i am not mistaken) and when i try to find the phone on adb it wont show up. so now i am hoping someone can guide me or show me what i need to do. if not i guess i have a new fancy paper weight hahaha. thanks guys appreciate it.
Click to expand...
Click to collapse
Does bootloader mode work? If so, you can use the ruu zip on an sd card to fix your phone. You can follow the instructions in my vzw ruu thread for option to. Just make sure you use the Sprint zip instead of mine.
dottat said:
Does bootloader mode work? If so, you can use the ruu zip on an sd card to fix your phone. You can follow the instructions in my vzw ruu thread for option to. Just make sure you use the Sprint zip instead of mine.
Click to expand...
Click to collapse
do you have a link to see how to make the zip file. i was searching and i dont know if i am overlooking it.
:cyclops:
dude. from bootloader, reflash unlock_code.bin you had from htc
then you can flash recovery and restore a backup
japodude said:
dude. from bootloader, reflash unlock_code.bin you had from htc
then you can flash recovery and restore a backup
Click to expand...
Click to collapse
thanks that did it. appreciate it.now i need to see how to unlock the sim on this thing hahaha. ok well now off to read some more
luisdelvalle1 said:
thanks that did it. appreciate it.now i need to see how to unlock the sim on this thing hahaha. ok well now off to read some more
Click to expand...
Click to collapse
i think when you soff it unlocks radio for anysim (i think) otherwise ebay does htc unlock code for a pound!