Related
We can no longer unlock your bootloader with codes. Please do not ask me or ash for bootloader unlock codes. We can not help you.
This thread is now here for historical purposes representing times when people were free to do what they wanted with their devices. Fsck yourself with a rake, Verizon.
The bootloader has been unlocked. Let's get our freaking root on.
Disclaimer: Read through these instructions in their entirety. If these don't make sense to you, you do not need to be rooting your phone. Nobody here has the time required to teach you how to use cmd in Windows. We will not baby step you through how to use ClockworkMod Recovery. Root is not a mythical land with fairies and unicorns where nothing ever goes bad. If you don't know how to properly install a driver in Windows, you probably don't need an Android device to begin with, let alone a rooted one.
These instructions are intentionally left vague. Do your research on these terms. Understand what you are doing before you do it.
tldr: if you fsck your phone up, it's on you and only you.
Easy Way (YRMV!)
This is by far the easiest method. You will have to read between the lines here. I will not detail all the steps. Please record your experiences in this thread and let me know how it all goes! We're all still learning. This is basically copied from Bin4ry's CWMR Thread so thanks go to him! The easy steps below assume a lot of basic knowledge steps. Like unlocking the bootloader. If you're unsure of what to do, you probably shouldn't be doing it.
Download the CWM recovery from multiupload
Boot off of that file (DO NOT FLASH): fastboot boot recoveryPLAY.img
Copy this to your memory card and flash it with the booted recovery
Reboot and test root
Second Method: Advanced User Instructions
Unlock your bootloader. Check out Ash's thread: thread
Download Doom's all in one kernel from here
Use fastboot to "hot boot" the kernel: fastboot boot boot.img
Your phone may or may not boot. It doesn't matter. Let it be for a while, then power it off.
Doom's kernel will have rooted your stock system.
If You're On A Mac...
Or maybe just need some general help with some more detailed insturctions than are labeled here, check out the awesome post that Cubsfan3493 made for everyone. He's even got a downloadable PDF with pictures. Go give him some thanks at his post!
Is the R800x running 2.3.2 or 2.3.3. There's reports that Gingerbreak and alternatives are no longer working in 2.3.3.
It's running 2.3.2 right now. OTA updates say its up to date. I'm trying to figure out if I'm just having a generic issue with the breaks (like memory cards for example) or if Verizon maybe patched the exploit in their 2.3.2 build.
I have tried pretty much everything as well, I really hope some dev's start to pop their noises in here as I am a bit sad about the activity so far
I've been trying to root mine as well. The discussion I've been having is in this thread
http://forum.xda-developers.com/showthread.php?t=1097856
I'll keep an eye on both threads, but I have had no luck so far.
I'm guessing it's something they fixed in the final Verizon build before release. Curious... What's your build #? Mine is 3.0.A.2.184.
Sent from my R800a using XDA App
axiomjunglist said:
I'm guessing it's something they fixed in the final Verizon build before release. Curious... What's your build #? Mine is 3.0.A.2.184.
Click to expand...
Click to collapse
Yes i think verizon fixed the exploit gingerbreak uses before releasing the handset in the usa. When i was on build number 3.0.A.2.184 (uk xplay R800i) it rooted in like 30 seconds.
But in the new update 3.0.1.A.0.145 the exploit has been fixed. So all devices around the world have been left unrootable (for now ) the devs will figure away out.
I think the uk version 2.3.3 build 3.0.1.A.0.145 has been rooted (for unlocked bootladers) http://forum.xda-developers.com/showthread.php?t=1098736 So if your bootloader is unlocked soon it maybe possible. If its locked your stuck waiting with the rest of us for a rooting method on locked devices.
I saw you updated from another post, did you lose root access after the update?
Sent from my R800a using XDA App
axiomjunglist said:
I'm guessing it's something they fixed in the final Verizon build before release. Curious... What's your build #? Mine is 3.0.A.2.184.
Click to expand...
Click to collapse
build number - 3.0.E.2.89
A shame they didn't let us all have unlocked bootloaders.
axiomjunglist said:
I saw you updated from another post, did you lose root access after the update?
Click to expand...
Click to collapse
Yes i did. But the fixes added in the update are worth loosing root, for the time being . Being unable to root only applies to people with a locked bootloader. But im guessing devs from the arc and play forum are possibly looking for ways to root with a locked bootloader
Yeah I have the option to unlock my bootloader but don't want to just yet. I'll hold off on the update until a new version of gingerbreak arrives
Sent from my R800a using XDA App
For the record, it seems like the bootloader is unlockable on the R800x. Fastboot is totally accessible by the same means and the oem unlock command is recognized, the phone is responsive, it's just looking for a key, the same as the GSM counterpart. The only difference is that the Verizon version doesn't have an IMEI (or does it.... since it does have a sim card slot....), just an ESN. So obviously you can't obtain an unlock key from this number.
Mills00013 said:
For the record, it seems like the bootloader is unlockable on the R800x. Fastboot is totally accessible by the same means and the oem unlock command is recognized, the phone is responsive, it's just looking for a key, the same as the GSM counterpart. The only difference is that the Verizon version doesn't have an IMEI (or does it.... since it does have a sim card slot....), just an ESN. So obviously you can't obtain an unlock key from this number.
Click to expand...
Click to collapse
Wonder if you pop a pre-paid SIM in the slot (or try a friend's AT&T/T-Mobile SIM) and disabled the CDMA radio if you could get an IMEI to pop up on the keypad using *#06#. Might work? I have no clue... and you'd still have to send it to SE and hope they clear it.
I have a few SIMs here that I could try. Ill see what I come up with in a little bit. My gut is telling me that Verizon probably has the SIM slot firmware disabled. Thats only because they havn't officially mentioned it anywhere. In fact, the slot itself is actually hidden by a piece of plastic that you have to remove. One wouldnt have any idea it was there unless you were looking for it and even then you feel like you're breaking your phone to access it.
I also considered hooking it up to QPST to see if it would grab some serial numbers out of the device. Can anyone confirm if this is a qualcomm chip inside the phone?
I just tried a T-mo and an AT&T SIM, neither give me any sort of insertion notification or acknowledgement that they are present. So I'd say the slot is firmware disabled. But it should still have an IMEI, right? That would be programmed by Qualcomm out of the factory before Ericsson would have even installed it. Or am I taking crazy pills?
do a ADB devices on your phone it gives what I think is a IMEI number and if you put the first 14 in on sony's site it gives you a unlock code, i am to much of a wussy to try it tho lol.
b00sted said:
do a ADB devices on your phone it gives what I think is a IMEI number and if you put the first 14 in on sony's site it gives you a unlock code, i am to much of a wussy to try it tho lol.
Click to expand...
Click to collapse
more than willing to be take a chance on mine. i ran adb devices. got code. first 14 digits (minus the b) sent to sony and got an unlock code.
next steps i'm confused on. how do i boot to fastboot mode? i tried holding menu key and inserting usb... didnt' seem to do anything...
ran
9. In the cmd windows type in fastboot.exe -i 0x0fce getvar version
and it did nothing just sat there (waiting for device).
Is there an indication you are in fastboot mode? should 0fce be different on our phones? any ideas?
EDIT: its hold search, not menu, got it to fastboot mode and got response.. trying now. will post results
EDIT 2 : and fail.
ace518 said:
more than willing to be take a chance on mine. i ran adb devices. got code. first 14 digits (minus the b) sent to sony and got an unlock code.
next steps i'm confused on. how do i boot to fastboot mode? i tried holding menu key and inserting usb... didnt' seem to do anything...
ran
9. In the cmd windows type in fastboot.exe -i 0x0fce getvar version
and it did nothing just sat there (waiting for device).
Is there an indication you are in fastboot mode? should 0fce be different on our phones? any ideas?
EDIT: its hold search, not menu, got it to fastboot mode and got response.. trying now. will post results
EDIT 2 : and fail.
Click to expand...
Click to collapse
ya I just tried too and fail :/ #sadpanda
Neither the adb devices nor the fastboot devices codes have anything to do with the IMEI number.
Enviado desde mi R800i usando Tapatalk
I am willing to donate towards the first person that can get root and CWM on this!
1)can some one give me a link to the most easiest and current way to root? ((Ive looked every where and im not even sure what i am to look for)) Also i am fully updated.
2)after i root,,,can i keep the phone basically the way it is meaning stock and sense?really just want to root as to get rid of all the bloatware and possibly over clock it.
3)Is there away to back up the phone pre-root in case i dont like root and wish to return to stock?
Any help in these matters would be greatly appreciated.
So, here's my $0.02 worth:
1) The easiest is not the best. If you want to root your phone, you need to learn how to use ADB. It's not difficult. You will need it at some point in the future. Here's a link to root your Thunderbolt > http://forum.xda-developers.com/showthread.php?t=996616
Here's a noob's guide to ADB >http://forum.xda-developers.com/showthread.php?t=532719
2) Yes you can.
3) I'm not sure, but here is a link that will return your phone to stock > http://forum.xda-developers.com/showthread.php?t=1009423
Plus one on learning adb its way easier than youd think. i always tried to use the one click methods and whatnot but i finally had to in adb and it was way easier. no worry about something wrong with the auto root. also try mybackup app from the market. i used it to backup everything initially then use titanium bacckup after you root since its way better
Advice on rooting flashing Thunderbolt?
Hi all,
I am so frustrated With my Moto atrix 4g and the fact that it has a locked boot loader with the new 2.3.4 stock rom....I have a real simple question;
If I obtain a Thunderbolt, does Verizon force HTC to keep anything locked or make the Thunderbolt difficult to root, unlock boot loader and ultimately flash non-stock roms from XDA ?
If it is like past HTC phones then it should be a rom flasher's dream, correct? It is able to be unlocked and i can flash roms from this wonderful forum?
Please advise....much appreciated.
maddie01 said:
Hi all,
I am so frustrated With my Moto atrix 4g and the fact that it has a locked boot loader with the new 2.3.4 stock rom....I have a real simple question;
If I obtain a Thunderbolt, does Verizon force HTC to keep anything locked or make the Thunderbolt difficult to root, unlock boot loader and ultimately flash non-stock roms from XDA ?
If it is like past HTC phones then it should be a rom flasher's dream, correct? It is able to be unlocked and i can flash roms from this wonderful forum?
Please advise....much appreciated.
Click to expand...
Click to collapse
Bro, really, take just 2 minutes to look around! There's a root guide right at the top of the dev forum!
To the OP: learning ADB and some basic Linux commands will become more useful than you know. Like quickly and easily checking an md5 without some stupid app or a computer. Plus, jcase is very easy to find and very helpful if there's a problem. I really can't endorse doing it the jcase way enough.
***LOCKED*** On Bootloader
Hello All,
First of all thanks for the awesome easy guide !!
This is the first time I am rooting my HTC Tbolt and have had an issue to start with.
Used the instructions in the link below:
http://forum.xda-developers.com/showthread.php?t=1401959
After I download the 2.11.605.5 downgrade zip, I rename it, put in on the SD Card and go to HBOOT and it installs the downgrade just fine.
But at the end of this process, when I try to get the MR4 Radio onto the SD Card and install it, it simply does not happen. HBoot checks for the file, finds it, but nothing happens. I have renamed in properly and followed instructions to the dot.
I also noticed a ***LOCKED*** right on top of the screen and I think this could be an issue.
Can I go ahead and proceed with the Revolutionary Root Technique ? Would this be possible at this point ?
Is there anyway I can get Flash the MR4 Radio before I actually root ?
Also, would I be able to flash the MR4 Radio onto my device after Rooting ?
Any help is much appreciated !
Thanks in advance !
Cheers !
I'm in over my head. Very much so. I've been flashing for years and a friend of mine has handed off his ATT atrix after making some big mistakes. He was rooted and somehow/for some reason deleted CWM and the new OTA ended up getting his device to this point (photo in attachment). I'm not very familiar with RSD, as luckily I've never found myself in a predicament like this. I've been all over this forum, the pudding/fruitcake/fastboot threads, and although I've seen the 'Don't SBF' warnings everywhere, I don't know what else to do, and I don't want to take any more action without knowing the consequences. I think this is a pretty unique situation. I'm asking for a detailed instruction on getting this phone restored (I've seen some say it's not possible, but other places saying a guy figured out a way). I need the specific links, and specific steps (as I've had much issue with broken links). I have access to ubuntu and windows so whichever is more simple is fine. I could try my luck but I'd rather reach out to someone who knows before hand.
*As far as I know the battery is high enough to flash (it's sitting with the battery pulled for now)
I don't care about retaining root, having a custom recovery or anything of that nature. I just need this phone to be in working condition again. Upon that happening we'd be happy to throw 20$ (via paypal) to whoever can get us there. Thanks in advance.
maybe this will help
I was rescued previously by the nice folks on atrixforums. you can reference this link http://www.atrixforums.com/forum/rescue-squad/6164-se-flash-olympus-help.html
Should be able to flash Romracers CWM via fastboot > http://forum.xda-developers.com/showthread.php?t=1204500 then get back into recovery. You can also flash a Fruitcake in fastboot mode > http://forum.xda-developers.com/showthread.php?t=1163009.
From your picture it looks like the bootloader was unlocked before, and maybe need to issue the unlock command again. This thread may help you > http://forum.xda-developers.com/showthread.php?t=1182871
Looks like ya just need to do the fastboot oem unlock commands to unlock the BL and finish the process....
thanks
Thanks for the quick responses guys, I'm off to work now but I'll try this tonight. Once again thank you.
I had the exact same problem, same thing happened with my phone, don't worry, you're okay!
First, are you sure that's the right SBF? I would confirm whether it is because that's the easiest way. Next, do what others have said and try to flash a recovery on it, from there on you can just unlock the phone and flash any rom.
Hope you get it sorted out.
G-Man. said:
Looks like ya just need to do the fastboot oem unlock commands to unlock the BL and finish the process....
Click to expand...
Click to collapse
brandonmangan - based on your screenshot you posted, you need to do the fastboot oem unlock commands, you flashed the pudding sbf with the unlockable bootloader. Get the fastboot drivers installed and then run the commands as they are listed in the pudding thread. Thats ALL you need to do.
Good ghod what a state I've managed to get myself into: I've been unlocking/re-locking my phone (ROM: OTA ICS, S-On, Unlocked, Rooted) for right at a year now, but, during the recent OTA update push, I managed to get it into a state where it will no longer unlock. My (long, sorry) story follows...
I started receiving the recent OTA push two or three weeks ago. The problem is that I'd renamed the HTClinkifydispacher apk and odex files, and added a couple of things to /system/app/build.prop so the update would fail. Why was this such an immediate problem? Because I use my phone for an alarm clock and would wake up on random days to see it booted to recovery---after having overslept. Grrr.
Being the impulsive guy that I am, rather than just ask here how to stop the f$*kin' update, I found and saved the OTA.zip file to my sdcard, fixed the two problems I was having, re-locked the bootloader, and booted to recovery. Next, I *thought* I picked the OTA zip file to install... but I was wrong.
For at least one reason (I wanted to install a kernel with tun.ko installed so I could use a VPN network connection), I had a copy of SebastianFM's 1.4 overclocked kernel zip on my sdcard and mistakenly picked *it* instead of the OTA zip (hey, the fonts are small in Amon Ra). Well, that install failed, and, when I saw what I'd done, I thought "uh oh," so I rebooted the phone fully to see if I'd done any damage. None was apparent. So I moved on, once again re-booting into recovery and (this time successfully) installing the OTA zip.
Woo-hoo!
I thought I was golden, but I was wrong: Using my original unlock code and an up-to-date copy of the Android SDK on my linux box, I tried to reflash the unlocktoken partition using the fastboot command. My cursor froze/still freezes at something like "[0kb downloaded]..." It's almost like I've lost permission to write to that partition in the bootloader.
After the first sixteen times of trying various re-flashes of the August OTA, I thought "Gee, maybe it's something to do with the firmware," and since doing something is almost always worse than doing nothing (yes, that's what I meant to say), I did the only thing I could do: I flashed the Global Update RUU zip from October that I got off of Android Police's site. It's a great ROM; unfortunately, I still cannot unlock my bootloader.
In anticipation of some possible questions, let me add that
(1) I've factory reset any number of times;
(2) When I did the flashes, I immediately re-flashed a second time to ensure that the flashes took;
(3) When I connect my USB cable, I see "Fastboot USB" light up in the fastboot section of HBOOT.
(4) When I issue any other fastboot command, such as "fastboot devices" or "fastboot get_identifier_token", I get responses from the phone.
(5) Even though I have my original Unlock_code.bin file from HTCdev, I went through the whole unlock process from that site (sent a new identifier token; got the Unlock_code.bin back; tried "fastboot flash unlocktoken Unlock_code.bin") on two other occasions. Interestingly, the identifier_tokens would vary, but any new Unlock_code.bin files have all been identical---if the md5sum hash can be trusted to distinguish them.
Can anyone out there in expert-land help me figure out how to re-unlock my bootloader?! !? Beer can be involved.
Many thanks for your patience and kind consideration...
cheers,
john
Hey All,
So, I'd like to first say thanks to all of you who read and considered throwing in an opinion on how I might move forward with my little problem.
Secondly, I have some followup from HTC, which spawns a followup question. Please read on...
Since my OP, I have been in a back and forth with HTC about what I did to my phone that has left me unable to re-unlock it. Their answer, in a nutshell, was that I'd accepted the update while my phone had a 3rd-party recovery on it. Guilty as charged, I did; Amon Ra 3.15.
More specifically, they wrote: "If any portion of this check fails due to the stock recovery not being present, the update may load but the security sector will not authenticate. This may be blocking the re-unlock."
If you're like me, you'll note that there are a couple of "may"s in those two sentences that have left me wondering if they're just giving me a stock "I really don't know what the hell happened to your phone" answer.
So just to satisfy my curiosity, has anyone else out there ever had a problem flashing OTAs while having a 3rd-party recovery on their phones?
thanks again,
john
There's a couple threads about the recent OTA, one in General and one in this section. People posted about their various experiences, you might find some useful info in those.
I wonder if you can s-off at this point and fix your issue? I don't know if you need to be unlocked to s-off, I know you end up locked, but if not, that would give you the freedom to flash what you want without needing to be "unlocked".
feralicious said:
There's a couple threads about the recent OTA, one in General and one in this section. People posted about their various experiences, you might find some useful info in those.
Click to expand...
Click to collapse
Yes, I've looked through them and had no luck finding anything relevant to my case.
feralicious said:
I wonder if you can s-off at this point and fix your issue? I don't know if you need to be unlocked to s-off, I know you end up locked, but if not, that would give you the freedom to flash what you want without needing to be "unlocked".
Click to expand...
Click to collapse
The phone has to be unlocked to do the s-off thing.
thanks,
john
Update: Problem Solved!
Hey All,
As the post title states, I finally did get this sorted out.
The solution? Borrowing a windows 7 computer, downloading the HTC device drivers, fastboot and adb, and then merely running the 'fastboot flash' thing. Like I'd done a thousand times already on my linux system. Sheesh.
Thanks to all who read or contributed to this thread...
cheers,
john
I just got this device, and I love it, so I don’t want to screw this up. I’ve spent the last 4 days researching how to do this, and I want some expertise before I jump in. I have tried to keep the noob questions to a minimum. Please be kind; this is my first time working with Android at all. What I’m trying to accomplish with rooting, because the XZU is so beautiful and big, is the ability to modify the DPI on the device to make it more like a tablet. I may even try Paranoid Android on it, but I will try that after just screwing with the DPI. I am going to lay out the steps I am going to take. Please let me know if the steps I am taking are wrong or if I’ve left out something important. Also, I’ve put my own questions in BOLD. Please answer those if possible.
As I noted, my device is a C6806, its bootloader is able to be unlocked, and I am currently running .757, having just upgraded yesterday. Here are the steps I am going to take:
1. Downgrade to .532 by flashing NUT’s .532 firmware, the .FTF file found here (http://forum.xda-developers.com/devdb/project/dl/?id=3442), with latest version of Flashtool (0.9.16.0). QUESTION: NUT’s FTF file is C6833_14.1.B.1.532_NUT.ftf. I assume the C6833 refers to that device number. But I have a C6806. Will flashing this FTF negatively affect my C6806 in any way? Will it be a problem at all? I assume it won’t be, but I want to make sure.
2. Root the device by using the instructions found here: http://forum.xda-developers.com/showthread.php?t=1886460.
3. I will then backup my TA Partition by following this guide: http://forum.xda-developers.com/showthread.php?t=2292598.
4. I will then unlock the bootloader by following the steps here: http://unlockbootloader.sonymobile.com/.
5. I will then upgrade to .757 following the instructions here: http://forum.xda-developers.com/showthread.php?t=2714511. QUESTION: I cannot find the .757 FTF at that link. I can find the .681 FTF at https://www.youtube.com/watch?v=uFSeSe8gQOY (which should use the same steps as .757). I could just upgrade to .681, but is there a place I can get a good .757 FTF to flash?
I should, at this point, have the latest (or near latest) build rooted. Am I correct in thinking this? If you see any problems, please let me know. If you have any other tips or tricks, please throw those in as well. Thank you. I really appreciate it.
4. You can take a "shortcut" by using Flashtool to unlock your bootloader after getting your unlock key from Sony. Just press the "BLU" button in Flashtool and enter your IMEI and unlock key.
5. That's the root kernel that you need to flash once you're on .757. You can find the .757 firmware here.
BUT BUT BUT, one thing before you start. This could quickly kill your rooting plans before you've even begun. Open the dialer and dial *#*#7378423#*#*, go to "Service Info" and then "Configuration". What does it say under "Rooting status"?
Spoiler: C6806s from Rogers are bootloader locked, and are impossible to unlock, so it gets much more complicated to root them while being on a newer firmware. It's also impossible to flash custom ROMs on them, so pray to something that you don't have an Ultra from Rogers
So if it says "No" under "Rooting status"... then you can't unlock your bootloader, and you should go to the bathroom and cry. On the bright side.. the other steps in your "guide" looks good, so good job and thank you for researching on your own.
LordManhattan said:
4. You can take a "shortcut" by using Flashtool to unlock your bootloader after getting your unlock key from Sony. Just press the "BLU" button in Flashtool and enter your IMEI and unlock key.
5. That's the root kernel that you need to flash once you're on .757. You can find the .757 firmware here.
BUT BUT BUT, one thing before you start. This could quickly kill your rooting plans before you've even begun. Open the dialer and dial *#*#7378423#*#*, go to "Service Info" and then "Configuration". What does it say under "Rooting status"?
Spoiler: C6806s from Rogers are bootloader locked, and are impossible to unlock, so it gets much more complicated to root them while being on a newer firmware. It's also impossible to flash custom ROMs on them, so pray to something that you don't have an Ultra from Rogers
So if it says "No" under "Rooting status"... then you can't unlock your bootloader, and you should go to the bathroom and cry. On the bright side.. the other steps in your "guide" looks good, so good job and thank you for researching on your own.
Click to expand...
Click to collapse
Thank you for the response! I have just gotten to Step 4 with a few snags in the process. The device is currently rooted with .532 and the TA partition is backed up. Sony just e-mailed me the unlock code. I am not on Rogers and I did confirm before starting this that the bootloader can be unlocked. So, luckily no Rogers. I bought the device directly from Sony.
As to the point you made on step 5, do I flash the firmware that you linked there with Flashtool and THEN flash the Kernel? I do both? I'm a little confused on that last step. Any guidance would be greatly appreciated.
And thanks for the encouragement. I think I might make a little guide to explain the little snags I ran into. They confused me for a while!=
Snarge said:
Thank you for the response! I have just gotten to Step 4 with a few snags in the process. The device is currently rooted with .532 and the TA partition is backed up. Sony just e-mailed me the unlock code. I am not on Rogers and I did confirm before starting this that the bootloader can be unlocked. So, luckily no Rogers. I bought the device directly from Sony.
As to the point you made on step 5, do I flash the firmware that you linked there with Flashtool and THEN flash the Kernel? I do both? I'm a little confused on that last step. Any guidance would be greatly appreciated.
And thanks for the encouragement. I think I might make a little guide to explain the little snags I ran into. They confused me for a while!=
Click to expand...
Click to collapse
yep you will need to flash both the FTF (in flash mode) and then the rootable kernel (in fastboot mode)