Okay, so I ordered a USED Thunderbolt on ebay last week and it should be here tomorrow. I'm not entirely new to rooting and such as I have a droid 2 global now, but that's motorola which seems to be fairly different from HTC. Anyway I've been reading threads and have come up with a few questions.
For instance if my phone is rooted when I get it, how can I get back to stock. I won't know how it was rooted, and some guides say it matters, while others don't. Plus many guides say not to just flash an RUU over a rooted phone, but if it replaces the bootloader, radio, and system, why not. Isn't that basically like an SBF on a motorola phone? Can I then also do a data wipe from the hboot bootloader thing on my phone and end up with a perfect stock device without any risk? From what I understand some roots block this entirely on the phone though so maybe I can't. I'm not really sure how to know what is safe to do on a phone that I didn't previously own and would love a guide to how to check these things and what to do so I don't brick the phone.
Also I can't seem to find a functional link to any of the latest radios, does anyone have a working link, and do people recommend the leaked radio from the most recent leaked build, or an official radio? and if so what radio is official? the one ending in 906 seems to be the most recent that I think is official but I'm not sure, though I am almost certain the 916 one isn't official, it appears to have been released in january on rootzwiki, while the most recent leaked build was less than a week ago from what I understand, but I don't know if it has a new radio or not.
Aside from that I think I've got it all down. figure out how to get phone to most recent stock OTA update. get 4g lte sim card, activate, root using this method.
http://rootzwiki.com/topic/20864-tool-root-2116059-and-19-no-downgrade-or-data-wipe/
then if I don't have the most recent radio I can flash it in the hboot thing, and can use cwm to flash any rom I want and a recommended kernel (I'm thinking thundershed 1.5 for starters though wouldn't mind some recommendations. I love Cyanogenmod)
Does this sound about right?
Also I'm not sure how hboot on htc phones works aside from booting on power+vol down button, but does the hboot allow for clearing data and cache as well as flashing things? On my droid 2 global there is a bootloader than can only be used to flash sbf files to get back to stock ota, and then there is a motorola stock recovery on the phone that is used for flashing updated ota updates that are signed or wiping data/cache. Are these the same on htc or are there a 2 different ones on that phone as well? I do understand that no PC is required for the htc as the tool to flash an ruu is built into the phone even if it is an older one than what the phone is currently on right?
Getting the Failed to boot 3 error.
I've been working at this for days now trying to reflash an sbf image to the phone to no avail. Every single time RSDLite (5.6) gives me the error saying it failed to re-enumerate the device no matter which sbf file I use. I am running as admin, and have all the drivers installed. Any help on this would be VERY much appreciated. Any info you need, just ask.
Hows the charge on the battery.
Sent from my MB855 using xda app-developers app
Well, I keep trying to get it to flash so it runs out a lot but I have a battery charger and I periodically charge it for a few hours. There's no way for me to tell how much of a charge it has but I assume it's somewhere around 75%.
"SVF: 108: 1: 2
Failed to boot 3
Starting RSD mode"
is what is says on the phone.
Always gets stuck on "Waiting for re-enumeration" in RSD Lite.
I get this error:
Phone did re-enumerate after RAM downloader was sent. (0x703e). Phone connected.
This is not much info, we need to know, if you were unlocked, locked, what sbf did you flashed last before this, if you flashed some OTA update, or radio, which sbf are you flashing now, if you can boot into fastboot after this error, and anything, that you think might be important to know.
But if you didn't do anything special, first try redownloaing the sbf.
I never successfully unlocked my bootloader, and I think this is where the brick occured so as far as I know it is locked still. I never flashed any sbf prior to this, I was trying to install a different ROM (I don't like blur very much). As far as I know I am able to boot into fastboot (power + volume up button) and it says fastboot on my phone and when it is plugged into my computer RSD lite displays it as fastboot mode but I can't flash anything to it, it'll give me an error in fastboot. When I hold power + volume down, it says something about NVFlash which I believe is an NVidia tool except the phone just shuts off almost immediately after this. The SBF I am flashing is the Sprint 2.3.5 version, and I've tried downloading and redownloading it from about 4 different locations to no avail. I purchased an external battery charger so I can keep trying different things, so the battery is almost always at a 100% charge. As of now I believe the phone to be unrecoverably bricked, and it's pretty sad because I had the photon for all of maybe 10 hours. Safe to say I've learned my lesson about flashing non HTC devices. My EVO 4G was so easy to do, I guess Motorola really doesn't like people messing with their devices.
Edit: If there is anymore information you think would be helpful let me know.
So you can get into rsd lite or not? There is no flashable 2.3.5 sbf, except the electrify one. All these sprint test sbfs, who knows, what it is for, but there is no signature and no full partition smgs. I think it won't even start flashing. Or? If it started to flash in your case, then your phone is bricked. But if you never flashed anything like 2.3.5 ota or 2.3.5 electrify or 2.3.5 pudding, and you can get into rsd lite or fastboot, I don't think it's unrecoverablly bricked.
peetr_ said:
So you can get into rsd lite or not? There is no flashable 2.3.5 sbf, except the electrify one. All these sprint test sbfs, who knows, what it is for, but there is no signature and no full partition smgs. I think it won't even start flashing. Or? If it started to flash in your case, then your phone is bricked. But if you never flashed anything like 2.3.5 ota or 2.3.5 electrify or 2.3.5 pudding, and you can get into rsd lite or fastboot, I don't think it's unrecoverablly bricked.
Click to expand...
Click to collapse
Yes I am able to get into RSD lite, and it recognizes my phone just fine everytime with no trouble. I believe it starts flashing, or it at least creates the image but everytime it gets stuck on "waiting for re-enumeration" and it fails there with an error like "phone did not re-enumerate" or something along those lines. I've tried flashing a 2.3.4 sbf as well but it gives me the same error as if I were to flash one of the 2.3.5 files.
Ok. If it was 2.3.4 - 198_7 or 198_6 sbf and did not even re-enumerated, you need to get unlocked. Try flashing pudding unlock and recovery from fastboot or try flashing this - http://d-h.st/WKD or use this method - http://forum.xda-developers.com/showthread.php?p=25826491
peetr_ said:
Ok. If it was 2.3.4 - 198_7 or 198_6 sbf and did not even re-enumerated, you need to get unlocked. Try flashing pudding unlock and recovery from fastboot or try flashing this - http://d-h.st/WKD or use this method - http://forum.xda-developers.com/showthread.php?p=25826491
Click to expand...
Click to collapse
Pudding unlock in fastboot gives me the error "Failed flashing process. Unable to retrieve interface handle(0x7027) phone connected."
Deblur gives me the same error as before, "failed to re-enumerate".
The link to the third method is really hard for me to understand. I understand the basics in which he speed hacks it, but I don't understand which files I will need to put in and where to get those files and which ones are correct etc.
I've found the directory with all the .smg files that I'm assuming is the image. Which files would I need to speed hack to have a chance at saving this thing?
Also, my phone fails to flash anything. I'm pretty sure it doesn't actually get anything done except to create the image.
In the command line when I type in "moto-fastboot oem unlock" it says INFOOEM unlock not implemented so I take it that means I'm still locked for sure.
When I try to manually write stuff via command line with the command "moto-fastboot flash recovery derpunlock" and any of the .smg files, it sends it fine but it fails on writing it.
bdotr said:
When I try to manually write stuff via command line with the command "moto-fastboot flash recovery derpunlock" and any of the .smg files, it sends it fine but it fails on writing it.
Click to expand...
Click to collapse
thats because deprunlock is a bootloader not a recovery.
step by step what have to done to get this error. sounds like your have a error in recovery.
mof9336 said:
thats because deprunlock is a bootloader not a recovery.
step by step what have to done to get this error. sounds like your have a error in recovery.
Click to expand...
Click to collapse
Well it would never get far enough to let me flash a recovery. I'm not able to flash any .sbf's through RSD lite either. The error it gives me every time is "device failed to re-enumerate".
I'm trying it through the ramloader now. I'm pretty sure I'm stuck on an bum electrify install. When I use the electrify ramloader it reboots to a blank screen with the motorola logo on it and when I try to flash derpunlock over through command line it doesn't say anything past "writing 'boot'".
Pudding must be flashed in rsd lite too.
Fastboot oem unlock is useless right now. You need to get there unlockable bootloader there first.
You need to speedhack CG42 it's bootloader, and it's preventing from re-enumeration, because it is not booting to rsd after re-enumeration. Try that one CG42 from pudding first. You need to split that with moto android depacker. But I have suspicion, that your bootloader or ramdownloader was switched to another signature version.
Last chance, but really the last, is flashing Electrify sbf.
****, now I noticed that, you should never ever flash electrify ramdownloader there. You changed rdl signature version. Now you have only the last chance. Download and flash full electrify sbf. But you will have no 4g, no more ota, and I am not sure if it flashes electrify radio or not, so maybe you will have no service.
If you really want, you can try some combination with creating custom sbf for recovering, but you need to read the whole thread in dev section and get much more familiar with that situation.
peetr_ said:
Pudding must be flashed in rsd lite too.
Fastboot oem unlock is useless right now. You need to get there unlockable bootloader there first.
You need to speedhack CG42 it's bootloader, and it's preventing from re-enumeration, because it is not booting to rsd after re-enumeration. Try that one CG42 from pudding first. You need to split that with moto android depacker. But I have suspicion, that your bootloader or ramdownloader was switched to another signature version.
Last chance, but really the last, is flashing Electrify sbf.
Click to expand...
Click to collapse
It now says fail to boot 2. I'm going to try the speedhack when I get home from work today and I'll let you know how it goes. No 4G I can do without, no ota as well I'm fine with. The radio thing might bug me though. So do I drop pudding's CG42 file into the 2.3.5 image while it's being created? Or do I flash just the CG42?
You cannot get unlocked anymore with cg42 from pudding, even with speed hack. You must read whole how to make custom sbf thread if you want to try custom combinations. If nothing will help, your only solution is flashing Electrify 2.3.5 sbf or wait, if some similar photon sbf comes out (I doubt).
Hi,
I have a new AT&T atrix 4g.
I unlocked the bootloader and found out that i have the famous wifi error problem.
I want to return the phone to the seller but would like to remove the unlocked text from the startup.
I read in the forum about hard brick during flashing 4.5.141 sbf. So im afraid of doing so.
I have no experience in flashing/rooting/etc... the only thing i did was unlock the bootloader with the automatic script. I still have the original at&t os.
Here is all my phone details:
4.5.141.BM860.ATT.en.US
android 2.3.6
kernel 2.6.32.9
build
4.5.141
I'd be happy if someone could help me out here...
I have also atrix 4g ...I have also unlocked the bootloader for rooting the mobile ...
I did this to my own Motorola Atrix 4g running rom: HB 2.3.4 oc 1.3ghz ext4 with the newest cwm installed
***i take no responsibility if this messes up your phone. I just did it to mine tonight before the replacement arives and wanted to help anyone else worried about being charged $399 for unlocking our bootloader
1) you need to download
//www35.megaupload.com/files/70b7d352e9514672c426f9dda58d3f6e/AUTOMATIC_UNLOCK_V4.2.zip
just incase something goes wrong you can unbrick it
2) RSD lite 5.3.1
//crackflashers.com/b16/Atrix/RSDLite5.3.1.msi
3) Newest moto update 2.3.4
//gitbrew.org/~dasmoover/android/atrix/1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf.gz
boot into rsd mode and flash the official update using rsd lite, it will stop at 100% but never finish. once you see the at&t logo you can unplug if it takes forever and just wait for it to load.
after you will no longer have cwm or the "unlocked" text at boot, but all your data will still be on the phone so dont forget to wipe after.
***link #1 is only if you have problems booting after using rsd lite (i didnt need it)
Hi,
What you are writing is correct for 2.3.4. I have the a 2.3.6 and 4.5.141.
I know this worked for 4.5.91 But im afraid that on my version it won't work...
Anyone?
I buy the Motorola Atrix 4g with the Android 2.3.
So i read everything, and i sense if i try to unlock the bootloader i get a hardbrick, right?
So how can i unlock my bootloader to install Custom Kernels and Custom Roms?
Unlocking from 2.3 won't give you a hard brick. It either gives you an error when trying to flash pudding, or nothing happens at all. Though, you can try because no one knows which batch of Atrixes can't be unlocked.
You can only be hard bricked if you try to flash a Froyo SBF. NEVER ATTEMPT TO DO SO.
Sent from that Atrix.
I needed to see about getting my electrify courier unlocked from USC. Phone was bootloader unlocked, rooted and running Paranoid Android 2.99. Guys at USC could not unlock because the phone did not have motorola tools on it? So they suggested that I put the phone back to factory and then bring it back. So I snagged the 2.3.4 stock USC image and attempted to RSD it to the phone. Got through about half of the flash and the phone crashed? Log states "Error switching phone to BP Pass through mode." Now the device states "Failed to boot 1" when powering on normally, cannot access RSD mode but I can access fastboot mode. Is there anything I can do?
read through several threads over the past few days. Got the phone to RSD using temp bootloader unlock and tried to flash 2.3.5 sbf just so I could get going. Now I am stuck with locked bootloader and no access to RSD looks like the electrify is a paperweight now.
nubleeet said:
read through several threads over the past few days. Got the phone to RSD using temp bootloader unlock and tried to flash 2.3.5 sbf just so I could get going. Now I am stuck with locked bootloader and no access to RSD looks like the electrify is a paperweight now.
Click to expand...
Click to collapse
This forum is pretty dead, like most of the phones. However, your critical failure was in applying the 2.3.5 SBF. Motorola booby trapped it such that it locked the boot loader permanently. There are no workarounds for an OTA/SBF installed version of 2.3.5, so even if you were able to get it up and running, you are forever stuck with it.
That said, you can probably still get into RSD mode using the bootloader to attempt a reflash of 2.3.5. There is a boot menu option for enabling it. I can't seem to find the thread, but it's around here somewhere.