Hey guys I have been reading through this forum and I think I get most stuff now. There is only one thing confusing me, when talking about bootloaders and unlocking them, everyone says its irreversible and you loose warranty and drm keys.
My question is, why? Can't we just backup it with CWM or similar? Can't we just make a backup when we receive the device from factory and then if we need warranty for something can't we just flash back and put everything original, including bootloader and stuff?
Thank you
shamelessly dumping to first page
Your warranty is never truly lost. Just remember, if they can't turn it on, they don't know it was rooted.
lowandbehold said:
Your warranty is never truly lost. Just remember, if they can't turn it on, they don't know it was rooted.
Click to expand...
Click to collapse
thank you, but my curiosity extends to the technical level, not just in the practical sense
gtype said:
thank you, but my curiosity extends to the technical level, not just in the practical sense
Click to expand...
Click to collapse
Ok, well the technical answer is once you unlock it, it can't be locked. Recovery does not back up your bootloader. A better alternative is flashing a different bootloader. There are some phones where the engineering bootloader used by OEM devs is available, so you can always go back to the stock bootloader.
EDIT: Actually now that I think about it, you can make a backup. I honestly have not dealt much with Samsung phones, so I am not sure if it is the same. But when you first root an HTC you take an initial image, which you store on your SD card or computer and you use it to unroot. When you unroot using that method it sets your bootloader back to factory. Also when you use a factory image, such as a PDxx.img and flash that through hboot, it gives you a stock bootloader as well.
lowandbehold said:
Ok, well the technical answer is once you unlock it, it can't be locked. Recovery does not back up your bootloader. A better alternative is flashing a different bootloader. There are some phones where the engineering bootloader used by OEM devs is available, so you can always go back to the stock bootloader.
Click to expand...
Click to collapse
isnt the bootloader in the boot partition?
gtype said:
isnt the bootloader in the boot partition?
Click to expand...
Click to collapse
Yes, the bootloader and the kernel are in the boot partition.
lowandbehold said:
Yes, the bootloader and the kernel are in the boot partition.
Click to expand...
Click to collapse
sorry if I'm being thick, but since the bootloader is part of the partition, what stops me from backuping all the partitions, unlock the bootloader, and then after some time flash the original dumped stuff?
gtype said:
sorry if I'm being thick, but since the bootloader is part of the partition, what stops me from backuping all the partitions, unlock the bootloader, and then after some time flash the original dumped stuff?
Click to expand...
Click to collapse
Hey, you can try it. That is a very sensitive partition to mess with. The main issue is, how many times have you flashed a ROM and for some reason it just doesnt flash right and you get a boot loop? Easy fix, wipe everything, reflash, good to go. If you flash the bootloader and reboot your phone and something went wrong with the flash...you have a hard brick. No coming back, period. So, experiment wisely. It is the same thing with flashing through terminal. If you get 1 space, 1 character wrong in the command line...hard brick.
actually I don't own a smartphone yet, but I'm going to soon. Since I'm well versed in Linux I was checking out the Android OS in general and that question popped up in my mind and I just couldn't find any info about it. Does that make kernel flashing dangerous too, since it's in the same partition as the bootloader?
gtype said:
actually I don't own a smartphone yet, but I'm going to soon. Since I'm well versed in Linux I was checking out the Android OS in general and that question popped up in my mind and I just couldn't find any info about it. Does that make kernel flashing dangerous too, since it's in the same partition as the bootloader?
Click to expand...
Click to collapse
No, kernel flashing is fine. A bad flash just ends in a bootloop, no big deal. Bootloaders and radios..those are the ones you have to be careful with.
lowandbehold said:
No, kernel flashing is fine. A bad flash just ends in a bootloop, no big deal. Bootloaders and radios..those are the ones you have to be careful with.
Click to expand...
Click to collapse
Alright, thank you very much.
Actually, it just struck me, why is it dangerous if it doesn't flash properly, the recovery partition is separate and you can make the device boot from it right?
gtype said:
Alright, thank you very much.
Actually, it just struck me, why is it dangerous if it doesn't flash properly, the recovery partition is separate and you can make the device boot from it right?
Click to expand...
Click to collapse
I am assuming you could if you have one backed up. But when a bootloader doesn't flash right and you get a brick, you can't even get into recovery. Most of the time the phone won't even power on. Because booting into recovery requires the bootloader.
lowandbehold said:
I am assuming you could if you have one backed up. But when a bootloader doesn't flash right and you get a brick, you can't even get into recovery. Most of the time the phone won't even power on. Because booting into recovery requires the bootloader.
Click to expand...
Click to collapse
I see. Thanks a lot for your time
gtype said:
I see. Thanks a lot for your time
Click to expand...
Click to collapse
Hey, no problem. Just sitting here on the front end of my 12 hour shift..nothing better to do!
lowandbehold said:
Hey, no problem. Just sitting here on the front end of my 12 hour shift..nothing better to do!
Click to expand...
Click to collapse
New question, if you are still around. What exactly is a locked bootloader? Is it just a bool in the bootloader code? Where are the DRM keys and why are they lost?
gtype said:
New question, if you are still around. What exactly is a locked bootloader? Is it just a bool in the bootloader code? Where are the DRM keys and why are they lost?
Click to expand...
Click to collapse
It depends on the device. A bootloader is usually unlocked by an unlock.bin for that device. I'm not an expert on bootloaders though...
dmeadows013 said:
It depends on the device. A bootloader is usually unlocked by an unlock.bin for that device. I'm not an expert on bootloaders though...
Click to expand...
Click to collapse
I was talking physically, like are the keys in the bootloader, is S_OFF etc bool variables etc. I guess I'll try to dig it up somewhere. thanks
gtype said:
New question, if you are still around. What exactly is a locked bootloader? Is it just a bool in the bootloader code? Where are the DRM keys and why are they lost?
Click to expand...
Click to collapse
A locked bootloader doesn't allow you to change key parts of the system such as a kernel. So you can still root your phone, but all of the custom ROM's have to use the stock kernel. So if you are on a gingerbread stock ROM, you can't run Ice cream sandwich because you can't change kernels. The DRM keys are what is used to encrypt the bootloader, so if you unlock the bootloader the keys are lost.
Related
me and my sister have the same phone Nexus S but in my boot I see werid sign and her phone the boot is ok. whats the problem?
http://youtu.be/54rRMryRUX0
Is her phone connected to a computer?
Sent from my Nexus S using XDA App
in the video is my phone. i tried to connected her phone to computer and no sign in the boot
d3one said:
me and my sister have the same phone Nexus S but in my boot I see werid sign and her phone the boot is ok. whats the problem?
http://youtu.be/54rRMryRUX0
Click to expand...
Click to collapse
that unlocked padlock mean that your bootloader is unlocked.
Presumably you're talking about the icon at the bottom, that looks like a padlock, then it indicates that your phone (i.e. it's boot-loader) is unlocked. Nothing to worry about... unless you'd like to return your phone to the manufacturer (perhaps to claim warranty) or store, from which you bought it; In which case you'll probably have to have your phone re-locked.
simms22 said:
that unlocked padlock mean that your bootloader is unlocked.
Click to expand...
Click to collapse
what u mean bootloader is unlocked. its good or bad? everyong have that?
its hard to lock it?
d3one said:
what u mean bootloader is unlocked. its good or bad? everyong have that?
its hard to lock it?
Click to expand...
Click to collapse
its good. its like freedom for your phone. it means you can flash a custom recovery and flash custom roms. locking is easy to do.
simms22 said:
its good. its like freedom for your phone. it means you can flash a custom recovery and flash custom roms. locking is easy to do.
Click to expand...
Click to collapse
im sorry but im noob in android
what u mean "it means you can flash a custom recovery and flash custom roms"
d3one said:
im sorry but im noob in android
what u mean "it means you can flash a custom recovery and flash custom roms"
Click to expand...
Click to collapse
Just means you can put customized/modified versions of android, whenever you feel like. This is what makes Google's Android powerful/unique and different from Apple's iOS (for iPhone) and Microsoft's Windows Phone(OS), for example.
I have Asus Eee Pad TransformerTF101 with an unlockbootloader is there any way to get the device back with locked bootloader ?
and how i can lock the bootloader again ?
The bootloader does not 'lock and unlock'. What are you trying to do? Unroot the device? Reinstall android OEM recovery and return to stock?
The 'locked' or 'unlocked' bootloader simply refers to the fact that the bootloader is encrypted, and for some versions we have the encryption key and can manually unlock via NVFlash to restore a bricked device, yet on other versions the bootloader key is unknown thus it is considered 'locked'.
I suggest reading up a bit more. If you don't know what you are trying to do and able to explain your problem then we can't possibly help you.
There is no concept of locked or unlocked in the tf101 bootloader, in the most general sense it is unlocked as it allows booting of unsigned kernels, and flashing of unsigned blobs.
the leaked key allows lower level communication (bootrom) with the device and can recover from bootloader errors.
hi Brothers
I applied these steps
http://www.youtube.com/watch?feature=player_embedded&v=VMHXeYMgPy4
Now i would like to return bootloader lock
thanx
You are not "back with a locked bootloaded" please use the right terminology..
luna_c666 said:
You are not "back with a locked bootloaded" please use the right terminology..
Click to expand...
Click to collapse
Haha I knew this one would be good!!!!!!!
I love how every once in awhile little stevie comes from nowhere and hands someone's ass back to them on a silver platter (done it to me a few times to lol)
One day i will be like himand you luna one day
Sent from my Transformer TF101 using xda premium
hi Brothers
Im sorry guyz i did n't explain to you what i wanted exactly ,
I applied these steps
http://www.youtube.com/watch?feature=player_embedded&v=VMHXeYMgPy4
Now i would like to return bootloader lock
thanx
lo3ti said:
hi Brothers
Im sorry guyz i did n't explain to you what i wanted exactly ,
I applied these steps
Now i would like to return bootloader lock
thanx
Click to expand...
Click to collapse
Maybe you're trying to say you want to unroot and return to stock?
Because the bootloader questions have been answered for you
by luna_c666 and lilstevie above.
baseballfanz said:
Maybe you're trying to say you want to unroot and return to stock?
Because the bootloader questions have been answered for you
by luna_c666 and lilstevie above.
Click to expand...
Click to collapse
I'm curious if the fellow is confusing the 'bootloader' with the recovery mode? From the sounds of it...he either has little understanding of english and can't/hasn't read my guide or is just dense, I'm leaning towards the first scenario
Hi All,
OK, bootloader is unlocked, I am working on recovery, so the next challenge is....................S-OFF!!! Aw, f%@ck, I thought i had my life back...
I invite all users with ideas and/or knowledge to jump in and tell me what they think I am doing right and what makes me a moron. I have no pride, so lay it on me.
I will post progress reports in Post #2.
Anyway, here's to getting this done quickly.
Steve
Moderator Edit
This Thread has been moved back to the development section in an effort to put an end to the off topic discussion.
Given the size of this thread I'm going to suggest that you USE the Search thread feature located at the top to make sure your suggestion or idea has not been attempted already.
ANY OFF TOPIC POSTS WILL BE DELETED!
Progress Reports
Just starting out...
One More
This is just in case...
Excellent.
JSLEnterprises said:
Excellent.
Click to expand...
Click to collapse
Thought I'd get out of your thread and the root thread....
sk806 said:
Thought I'd get out of your thread and the root thread....
Click to expand...
Click to collapse
I had to send another message to red not to reopen the think tank thread (title would have been edited obviously), but to still go ahead with the cleanups... lol
Sorry if I'm totally off base here but I do believe reading on XDA somewhere that with the HTC One series phones when you unlock the bootloader it locks the phone from being able to flash recoverys.
This is the reason why I have waited to do the bootloader unlock I didnt want to screw myself from ever being able to flash custom roms.
you have to use this unlock method for the bootloader so why would it screw anything else up? It opens up all possibilities, not close them.
killathenoob said:
Sorry if I'm totally off base here but I do believe reading on XDA somewhere that with the HTC One series phones when you unlock the bootloader it locks the phone from being able to flash recoverys.
This is the reason why I have waited to do the bootloader unlock I didnt want to screw myself from ever being able to flash custom roms.
Click to expand...
Click to collapse
Nope. I have flashed CWM recovery at least 4 times on an international One X AFTER unlocking the bootloader. I wish that were it....
I think you may be thinking of firmware, which is a real mess, because unlocking your bootloader can set your CID to "none", and thus, you can't flash different firmware (i.e., an EU firmware on an Asian phone)...not that that would matter for these carrier-branded phones...
Good job and great progress. Unfortunately, none of us AT&T users can join in on the fun.
killathenoob said:
Sorry if I'm totally off base here but I do believe reading on XDA somewhere that with the HTC One series phones when you unlock the bootloader it locks the phone from being able to flash recoverys.
This is the reason why I have waited to do the bootloader unlock I didnt want to screw myself from ever being able to flash custom roms.
Click to expand...
Click to collapse
If that was completely true, then the Tegra 3 model's would not have cwm recovery... yet they do.
We just havent figured out a working method for ours.
JSLEnterprises said:
If that was completely true, then the Tegra 3 model's would not have cwm recovery... yet they do.
We just havent figured out a working method for ours.
Click to expand...
Click to collapse
i think what Killathehnoob is trying to say is that its only the ROGERS version of the ONE X that when unlocking the BLer HTC has somehow lock the other partitions so that custom recoveries and kernels are not able to be flashed to the phone...which essentially could be the case because all they said they will "unlock" the BLer...BUT they never said they would NOT do anything else in the process. maybe its a possibillity that has been over looked...just THINK TANKING is all
LNKNPRKFN said:
i think what Killathehnoob is trying to say is that its only the ROGERS version of the ONE X that when unlocking the BLer HTC has somehow lock the other partitions so that custom recoveries and kernels are not able to be flashed to the phone...which essentially could be the case because all they said they will "unlock" the BLer...BUT they never said they would NOT do anything else in the process. maybe its a possibillity that has been over looked...
Click to expand...
Click to collapse
I understand what you mean
I wonder if the fact that its new proprietary qualcomm chip is the reason why its being 'limited'... so we may have to rethink the whole initialization process.
we cant even get to the point that the logcat is able to start logging. So we're flying blind.
We've extended the time between loading to the soft reboot after the flash... but that doesnt tell us much.
I found the artice I read check it out
http://mobilesyrup.com/2012/05/02/i...bootloader-unlock-tool-on-one-series-devices/
killathenoob said:
I found the artice I read check it out
http://mobilesyrup.com/2012/05/02/i...bootloader-unlock-tool-on-one-series-devices/
Click to expand...
Click to collapse
Interesting. I think the lack is fastboot boot is what they are referring to. This would prevent custom kernel development on an s-off device, but should still allow flashing of insecure stock boot images, as with the int. HOX, althoug i read it again, anf maybe they are talking about more than that. I am not sure that the article is saying that there is something different with the Rogers version vs other versions, but it seems like there may be, and obviously with the Att version. I think I will spend a day just reading, trying to pick other devs' brains, and start fresh...thanks for the input.
Steve
sk806 said:
Interesting. I think the lack is fastboot boot is what they are referring to. This would prevent custom kernels being flashed on an s-off device, but should still allow flashing of insecure stock boot images, as with the int. HOX. I am not sure that the article is saying that there is something different with the Rogers version, but it seems like there may be, and obviously with the Att version. I think I will spend a day just reading, trying to pick other devs' brains, and start fresh...thanks for the input.
Steve
Click to expand...
Click to collapse
The 'fastboot boot' command works however, its how we got root in the first place.
... delegated to a Nigerian prince. Send money.
killathenoob said:
I found the artice I read check it out
http://mobilesyrup.com/2012/05/02/i...bootloader-unlock-tool-on-one-series-devices/
Click to expand...
Click to collapse
Here is the actual rootzwikk article
http://rootzwiki.com/news/_/articles/dear-htc-can-we-have-our-phones-back-r709
JSLEnterprises said:
The fastboot boot command works however, its how we got root in the first place.
... delegated to a Nigerian prince. Send money.
Click to expand...
Click to collapse
Whoa, very interesting. I was certain it did not on the Int one x.
JSLEnterprises said:
The 'fastboot boot' command works however, its how we got root in the first place.
... delegated to a Nigerian prince. Send money.
Click to expand...
Click to collapse
Just to be clear, you are not referring to fastboot flash boot, right?
Edit, nevermind, jut looked at Paul's post, it is fastboot boot. Wow.
killathenoob said:
I found the artice I read check it out
http://mobilesyrup.com/2012/05/02/i...bootloader-unlock-tool-on-one-series-devices/
Click to expand...
Click to collapse
Again thanks for this. Back to the drawing board!!!!
Hi,
I followed the instructions here (http://forum.xda-developers.com/showthread.php?t=1525100) and after trying to revert back (fastboot oem lock and then flash stock ruu), I now have RELOCKED on the bootloader as opposed to LOCKED. Is there any way I can solve this (preferably without downgrading hboot)?
Thanks in advance.
No, there isn't.
you can S-OFF and then take the S-OFF and UNLOCKED tags off with this:
http://www.xda-developers.com/android/bootloader-customization-now-open-to-more-s-off-htc-devices/
tep_kubo said:
Hi,
I followed the instructions here (http://forum.xda-developers.com/showthread.php?t=1525100) and after trying to revert back (fastboot oem lock and then flash stock ruu), I now have RELOCKED on the bootloader as opposed to LOCKED. Is there any way I can solve this (preferably without downgrading hboot)?
Thanks in advance.
Click to expand...
Click to collapse
in my experience after the downgrade the banner "relocked" disappeared... but just through the downgrade..
i guess that's just what the older version bootloader looks like... i was looking for a way to do it for hboot 2.00 etc but i think the bootloader customisation is the only way...
thanks for the help guys
Jack_R1 said:
No, there isn't.
Click to expand...
Click to collapse
Jack knows. Believe it.
TatoValverde thanks a lot, the program worked a treat.
to anyone thinking of unlocking via htcdev, don't... downgrade and then flash engineered hboot.
From my experience, downgrading Hboot using the RUU can help to make it ***LOCKED*** again (which happened to me), but if you have ever used HTCDev, then although it is Locked, HTC would know that it is actually RE-LOCKED.. That's if HTC bother to dig out their database deeper during repair..
My advice: Don't use HTCDev, or if you have, don't bother about it, just enjoy your freed phone..
Wouldn't something like this work for our device as well? The partition and offset would likely differ, but I think it's doable. http://forum.xda-developers.com/showthread.php?t=1970252
jneapan said:
Wouldn't something like this work for our device as well? The partition and offset would likely differ, but I think it's doable. http://forum.xda-developers.com/showthread.php?t=1970252
Click to expand...
Click to collapse
I have checked this some time ago but unfortunately on my device (htcdev unlocked to escape a bad brick) there is no HTCL nor HTCU on any partition so they probably used another methodology on the DS
Sent from my HTC Desire S
amidabuddha said:
I have checked this some time ago but unfortunately on my device (htcdev unlocked to escape a bad brick) there is no HTCL nor HTCU on any partition so they probably used another methodology on the DS
Sent from my HTC Desire S
Click to expand...
Click to collapse
Well that's a bit disappointing, it made sense in my mind that they would use the same method on all their phones, because of convenience if nothing else.
jneapan said:
Well that's a bit disappointing, it made sense in my mind that they would use the same method on all their phones, because of convenience if nothing else.
Click to expand...
Click to collapse
I hoped they did...
Actually I have made a lot of digging in this area and for example on HTC Wildfire the Relocked/Locked state can be manipulated in the misc partition only. This differs from the guide you linked as well.
I have searched through all of the 30 partitions on my device and have found no trace of the manipulation the unlock_token did. So eventually I gave up, but if someone finds the solution I will be happy. There are still 6 months in my warranty
amidabuddha said:
I hoped they did...
Actually I have made a lot of digging in this area and for example on HTC Wildfire the Relocked/Locked state can be manipulated in the misc partition only. This differs from the guide you linked as well.
I have searched through all of the 30 partitions on my device and have found no trace of the manipulation the unlock_token did. So eventually I gave up, but if someone finds the solution I will be happy. There are still 6 months in my warranty
Click to expand...
Click to collapse
I've still got 8 months left on mine, so I'll be waiting to see if anyone else figures this out. Times like this, I regret not learning anything about this sort of development/hacking, because I'd very much like to fiddle with this myself
Phone was rooted using TWRP. I locked the bootloader and now I can't boot up into anything but the page with the TAMPERED RELOCKED screen, also has bootloader, reboot, reboot bootloader, power down. Am I screwed? I just wanted to revert my rooted phone back to the original OS and it's been a freaking NIGHTMARE ):
XHaGGeNx said:
Phone was rooted using TWRP. I locked the bootloader and now I can't boot up into anything but the page with the TAMPERED RELOCKED screen, also has bootloader, reboot, reboot bootloader, power down. Am I screwed? I just wanted to revert my rooted phone back to the original OS and it's been a freaking NIGHTMARE ):
Click to expand...
Click to collapse
So you've relocked the bootloader, and then nothing else?
Run the RUU from the bootloader screen. Make sure the RUU is for YOUR phone
That's the thing, I can't get into it! I can't get into that screen where I could access stuff to INSTALL, MOUNT, etc.. it keeps taking me to the white screen with bootloader,reboot, etc.
XHaGGeNx said:
That's the thing, I can't get into it! I can't get into that screen where I could access stuff to INSTALL, MOUNT, etc.. it keeps taking me to the white screen with bootloader,reboot, etc.
Click to expand...
Click to collapse
Seeing as though you have relocked the bootloader you can either a. unlock the phone again so you can install a custom rom or b. run a ruu to get it back to stock.
Yeah because the problem is i have no OS to boot into. It just goes into recovery mode. Can you point me in the direction on how I can unlock the bootloader again?
XHaGGeNx said:
Yeah because the problem is i have no OS to boot into. It just goes into recovery mode. Can you point me in the direction on how I can unlock the bootloader again?
Click to expand...
Click to collapse
No no no. You said you wanted to go back to stock correct?
Download your stock RUU, and run from that white menu that says RE-LOCKED at the top. That's your bootloader
Ok, when you mean run from that white menu that says RELOCKED, how can I run it from that menu if I cant get into anything from this menu? Do you mean just run the RUU program from my computer and have my phone connected to the PC? I used to be able to go into that TWRP screen when i was in bootloader but now I can't.
XHaGGeNx said:
Ok, that's what I am doing already. I am downloading the RUU for my phone. Hope to gawd this will save my phone. I am just worried because it's literally stuck at this bootloader menu screen. I can't do anything else.
Click to expand...
Click to collapse
Believe me, the fact your screen is on is a sign you are not bricked. Run the RUU (Make sure it's one that is easily rootable, like the 1.85 for ATT), and go through the process of bootloader and unlock and rooting. Hope this helped
I am glad to hear that. It's almost done downloading, about 4 minutes left. I really want to thank you for helping me out here. I am such a screw up with this stuff. Sigh. anyways, I'll let you know what happens here shortly. Thank you so much once again. Really..
Honestly man once you get back to stock, don't worry about unlocking and rooting it. You have no business rooting your phone and flashing roms if you can accidentally delete your os, backup file, and the recovery partition. Not trying to be rude, but think about it, you could of destroyed your phone with one more bad flash
It's working! It's updating and everything. Phew! No offense taken, I hear ya and agree. Just being a noob at all this can put me into a lot of trouble. I have learned a lot of stuff though lol. Anyways, thank you everyone for helping me! I should be good from here
Glad to hear its working
Cheers man, good to hear everything is fixed.
If you need anything else, contact me. There are a bunch of ways to.
As for rooting again? Just read up and you'll be set.
mgutierrez87 said:
Honestly man once you get back to stock, don't worry about unlocking and rooting it. You have no business rooting your phone and flashing roms if you can accidentally delete your os, backup file, and the recovery partition. Not trying to be rude, but think about it, you could of destroyed your phone with one more bad flash
Click to expand...
Click to collapse
Hate to bump heads with ya dude but this isn't the way to be, I frown upon threads like this as well but I encourage others to root no matter who they are. Granted they do need to take the time to research what they are doing and how to get themselves out of a hole like this but someone has to help them learn
This is a community working towards a common goal, you never know maybe this dude will make his way towards development somewhere in the future. Or more likely since others helped him in his time in need he will turn around and try to do the same for someone else
Just my two cents
Sent from my HTC One XL using Tapatalk 2
mgutierrez87 said:
Honestly man once you get back to stock, don't worry about unlocking and rooting it. You have no business rooting your phone and flashing roms if you can accidentally delete your os, backup file, and the recovery partition. Not trying to be rude, but think about it, you could of destroyed your phone with one more bad flash
Click to expand...
Click to collapse
A simple "Be more careful next time because of ..." would have been just fine.
superchilpil said:
Hate to bump heads with ya dude but this isn't the way to be, I frown upon threads like this as well but I encourage others to root no matter who they are. Granted they do need to take the time to research what they are doing and how to get themselves out of a hole like this but someone has to help them learn
This is a community working towards a common goal, you never know maybe this dude will make his way towards development somewhere in the future. Or more likely since others helped him in his time in need he will turn around and try to do the same for someone else
Just my two cents
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
My apologies. We had been PMing for over an hour before this thread trying to get his phone back. I came off a little rude on that last post but he knows how hard I was trying to help him and that he can always come here for answers. Most forum guys would tell him to "search it"
please
how did you fix your phone i almost have same problem
He didn't delete ROM, recovery or anything. He relocked his bootloader. It just won't let you reboot unless you relock with a stock recovery flashed.
Sent from my One X using Tapatalk 2
http://forum.xda-developers.com/showthread.php?t=1982968
Could u guys stop by my thread and help me out?
I kinda have the same problem, and RUU tells me phone is off, error 170.
Thanks