Hello everyone?
My brother just emailed me a question the question in the topic. I told him to ask himself here, but hes at work at XDA is a site he cant access from work.
He had unlocked his bootloader and installed a version of Ginbergread. He then decided to flash back to stock and install the official Gingerbread OTA update, and it worked. Now when he starts his phone up the unlocked indicator is gone, so is he still unlocked and if so, how does he tell?
I think his main goal here is installing CWM Recovery so he can then root using the CWM Recory Root, but honestly, I dont know. Im simply asking the question. So with all that being said, is there a wait to tell if his bootloader is still unlocked or is it always going to be unlocked even if it no longer says unlcoked during the phones start up process?
Now, just in case he asks me, can he install CWM and the CWM Root with official OTA GB Update if he had previously unlocked his bootloader?
I (and my brother) appreciate any info.
if the unlocked text is gone during boot then he will have to unlock the bootloader again but this is not necessary if he only wants to install CWM.
neotekz said:
if the unlocked text is gone during boot then he will have to unlock the bootloader again but this is not necessary if he only wants to install CWM.
Click to expand...
Click to collapse
When bootloader is unlocked, it remains unlocked. You do not have to unlock it again! The word unlocked disappears when you flash back.
Once unlocked, always unlocked!
Sounds good. So if he wants to install CWM, can he just follow this guide: http://forum.xda-developers.com/showthread.php?t=1138541 to install CWM?
I had assumed thats what he wanted to while I was waiting for a reply I emailed him and I was right. He plans on installing CWM and then then root.zip. Will that work?
JohnnyDanger said:
Sounds good. So if he wants to install CWM, can he just follow this guide: http://forum.xda-developers.com/showthread.php?t=1138541 to install CWM?
I had assumed thats what he wanted to while I was waiting for a reply I emailed him and I was right. He plans on installing CWM and then then root.zip. Will that work?
Click to expand...
Click to collapse
he can follow instructions in that post or he can root, download rom manager from market and install cwm recovery from within the app.
although tenfar's recovery works flawlessly on ATRIX and cwm can't wipe or read from external sd card.
to reiterate, ONCE UNLOCKED, ALWAYS UNLOCKED!!!
hope this helps.
Sent from my MB860 using XDA App
That does help. Thanks a lot. Im hoping to get him involved here. I think he can learn a lot. The Atrix is his first smartphone and I think he is just starting to really dig in. Hes not so concerned with messing things up as he has a lot of expendable income, but I think the more he knows, the more he will enjoy his phone.
With this one you can not fool around, why I said this, because if you unlock your bootloader and have the "unlocked" tag at boot but then you flash by RSD MOTO 2.3.4/4.5.91 sbf you will lost the tag at boot, actually your bootloader still unlocked but not funtional until you reflash pudding again. But my point if someone want to service their phone and want to reflash MOTO 2.3.4/4.5.91 sbf so the simple customer service guy did not figure out that you mess with your phone unlocking it, yeap it work for the simple CS guy but for tech guy nope because of the following statement:
If you want to confirm your status:
adb->su->and "cat /sys/firmware/fuse/ReservedOdm" or just open the file in Root Explorer. If you see something like:
10000000000010001000100004000
Here is the mean of some of those numbers:
10000000000010001000100004000
4= BL "unlock" Bootloader Unlock out of warranty unit
0= BL lock
10000000000010001000100004000
1=NO UPDATE BL TO AP20 Ver. , so you applied GB by moto-fastboot process or by CDW (fruit cake, etc)
3=YOU HAVE A NEW BL AP20 Ver., so you indeed applied GB MOTO OTA<- this guy can NOT RSD ANY MOTO SBF DOWNGRADE 1.26 / 1.57 / 1.83
I hope it help!
CaelanT said:
When bootloader is unlocked, it remains unlocked. You do not have to unlock it again! The word unlocked disappears when you flash back.
Once unlocked, always unlocked!
Click to expand...
Click to collapse
Yeap TRUE , but when you lost the "unlocked" tag because you reflash 2.3.4 SBF you will lost the "unlocked" tag, so unit still with bootloader unlocked but is not 100% functional, you will not able to moto-fastboot partitions until you reapply pudding again and I think this due to the microboot partition (I think CG47)
rafkong said:
he can follow instructions in that post or he can root, download rom manager from market and install cwm recovery from within the app.
although tenfar's recovery works flawlessly on ATRIX and cwm can't wipe or read from external sd card.
to reiterate, ONCE UNLOCKED, ALWAYS UNLOCKED!!!
hope this helps.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
tenfar's CWM can read both the internal and external SD card, you must have the most up-to-date version though. 4.0.0.2 i believe.
mramirezusa said:
If you want to confirm your status:
adb->su->and "cat /sys/firmware/fuse/ReservedOdm" or just open the file in Root Explorer. If you see something like:
10000000000010001000100004000
Here is the mean of some of those numbers:
10000000000010001000100004000
4= BL "unlock" Bootloader Unlock out of warranty unit
0= BL lock
10000000000010001000100004000
1=NO UPDATE BL TO AP20 Ver. , so you applied GB by moto-fastboot process or by CDW (fruit cake, etc)
3=YOU HAVE A NEW BL AP20 Ver., so you indeed applied GB MOTO OTA<- this guy can NOT RSD ANY MOTO SBF DOWNGRADE 1.26 / 1.57 / 1.83
Click to expand...
Click to collapse
That was brilliant, thanks! My Atrix reports the following:
cat /sys/firmware/fuse/ReservedOdm
30000000000030001000300004000
so is it safe to assume that it's unlocked. I'm curious to know what the starting digit (3 in my case) means, as it's different from your example.
Mine looks nothing like your lol
20000000000020002000200004000
I can downgrade all the way back to 2.2
Related
I was previously on 2.3.4 with CherryBlur, but i downgraded back to 1.8.3 (Froyo) through SBF.
When i boot up it no longer says "Unlocked", but i read around and i believe my Phone still has an unlocked bootloader. (Quick Question: How do i get it back to say "Unlocked" without losing any data?)
Now I installed ROM Manager from the Market, and Installed CWM, because i think i lost CWM when i downgraded.
Question: Am i ready to download and install Roms now. Also when i click Download Roms in the Rom Manager i get an error getting list.
theres a cmd in the unlock thread that let you know if youre still unlocked. and i dont know of any rom that are downloadable from there yet.
primeboss said:
I was previously on 2.3.4 with CherryBlur, but i downgraded back to 1.8.3 (Froyo) through SBF.
When i boot up it no longer says "Unlocked", but i read around and i believe my Phone still has an unlocked bootloader. (Quick Question: How do i get it back to say "Unlocked" without losing any data?)
Now I installed ROM Manager from the Market, and Installed CWM, because i think i lost CWM when i downgraded.
Question: Am i ready to download and install Roms now. Also when i click Download Roms in the Rom Manager i get an error getting list.
Click to expand...
Click to collapse
reflash the pudding for your device and fastboot oem unlock again
joe ferreira said:
reflash the pudding for your device and fastboot oem unlock again
Click to expand...
Click to collapse
all you have to do is reflash the pudding. i've done it multiple times. if you try to fastboot oem unlock again it'll say already unlocked. reflashing the pudding restores the prestigious Unlock text at boot
Hello everyone I was hoping I could get some help with my ATT Atrix 4G, as of right now I have my Atrix running 1.5.7 and rooted. For some reason about a week ago my Wifi just stopped working and says error. So I did a little looking around and didnt see a fix besides flashing the phone so I thought I might as well update to the latest and greatest. Now I did my phone so long ago that I have Tenfar's CWM recovery for Motorola Atrix 4G on it. I would like to flash to Flashable SBF: Full 2.3.4 with preinstall root and pudding bootloader unlock, full sbf but Im not sure the steps I need to take. Over all this is what I would like to do.
Number 1. Put CWM Recovery Mod for Atrix 4G and take off Tenfar's CWM
Number 2. Unlock the phone Pudding
Number 3. Flash to Flashable SBF: Full 2.3.4 with preinstall root and pudding bootloader unlock, full sbf
Number 4. Get wireless tether working.
One thing I don't fully understand is do you need to unlock the phone using pudding before you flash Full 2.3.4 with preinstall root and pudding bootloader unlock or can you just flash and have it unlocked?
So what I really need to know is the order of everything, CWM Recovery Mod for Atrix says you need to be unlocked to use it. So do I need to unlock the phone like in number 2 to before I do number 1 and 3 or can I flash number three and the will unlock the phone? Then do Number 1 and skip number 2 altogether? And as far as number 4 goes if some one could point me in the right direction for working wifi tether on 2.3.4 ATT that would be great.
One other thing I was wondering is it safe to flash for 1.5.7 to 2.3.4 or should I flash to 1.8.3 and then to 2.3.4?
Thanks so much and any and all help is greatly appreciated
Jay
1. You need too unlock first
http://forum.xda-developers.com/showthread.php?p=16018910#post16018910
2. You need to install Tenfars (not rom managers) CWM recovery for atrix unlocked.
http://forum.xda-developers.com/showthread.php?t=1138541
3. Install whatever ROM you feel you will like. I recommend Kenns ROMS
http://forum.xda-developers.com/showthread.php?t=1186537
or
http://forum.xda-developers.com/showthread.php?t=1160649 from Nav.
Both good roms.
Thanks JayRolla but do I need to flash to Full 2.3.4 with preinstall root and pudding bootloader unlock before I install the 2.3.4 roms you linked to up there?
Jay Dogg said:
Thanks JayRolla but do I need to flash to Full 2.3.4 with preinstall root and pudding bootloader unlock before I install the 2.3.4 roms you linked to up there?
Click to expand...
Click to collapse
As far as I understand, at the moment you are on 1.8.3.
In that case the very first thing you should do is flash pudding (BL unlock sbf).
After that install CWM and do a full backup.
When you have that you can install whichever room you want (don't sbf back to 1.8.3 tho - hard brick), you can install stock 2.3.4 via CWM and root it afterwords manually if you want. It's all a matter of which rom you prefer. Hell, you can try them all as CWM makes it all really easy.
Pudding needs to be flashed only at step 1 and it stays with your forever as long as you dont' SBF. Which you really don't need to do since we have CWM and fastboot.
Have a quick question, what is the difference between the automatic unlock script and the SBF that unlocks and roots via preinstall?
I am on stock 4.5.91 OTA with no modifications at all. Which method should I use? Which is safest/easiest.
I am on win7 64 bit with latest moto drivers installed.
dcarpenter85 said:
Have a quick question, what is the difference between the automatic unlock script and the SBF that unlocks and roots via preinstall?
I am on stock 4.5.91 OTA with no modifications at all. Which method should I use? Which is safest/easiest.
I am on win7 64 bit with latest moto drivers installed.
Click to expand...
Click to collapse
Automatic script is supposed to automate (duh ) some of the unlocking steps for you, but I personally wouldn't recommend it. It failed for me and for many other people too if you read their thread.
With the manual pudding unlock - you can't screw up if you follow all of the steps precisely. But you do have to do all the steps manually, which is a good learning process if you ask me.
If you are on 4.5.91, after flashing pudding and doing the fastboot unlock commands you will get failed to boot error. This is normal and all you have to do is repeat the fastboot commands for the second time and all will be fine.
Do not under the fear of death SBF back to 1.8.3 or you will brick your phone.
Here is the link to the pudding SBF -
http://forum.xda-developers.com/showthread.php?t=1136261
Here are the specific steps laid out in a very straightforward way -
http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
Just make sure you install the drivers before doing them. For example, you can download Windows 7 x64 drivers here -
http://forum.xda-developers.com/attachment.php?attachmentid=634880&d=1308872277
xploited said:
Automatic script is supposed to automate (duh ) some of the unlocking steps for you, but I personally wouldn't recommend it. It failed for me and for many other people too if you read their thread.
With the manual pudding unlock - you can't screw up if you follow all of the steps precisely.
Here are the specific steps laid out in a very straightforward way -
http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
Just make sure you install the drivers before doing them. For example, you can download Windows 7 x64 drivers here -
http://forum.xda-developers.com/attachment.php?attachmentid=634880&d=1308872277
Click to expand...
Click to collapse
Thanks for the info
One last question, should I use the small (10mb) pudding sbf or the full SBF that does unlock + root all in one?
dcarpenter85 said:
Thanks for the info
One last question, should I use the small (10mb) pudding sbf or the full SBF that does unlock + root all in one?
Click to expand...
Click to collapse
I would recommend using the smaller pudding sbf, since that's what I used. But from what I read, both SBFs work without problems.
You can root manually afterwords. It's very easy.
xploited said:
As far as I understand, at the moment you are on 1.8.3.
Click to expand...
Click to collapse
Im on 1.5.7 rooted right now, not sure if that makes any kind of difference, do I need to be on 1.8.3 or higher before I do pudding?
Jay Dogg said:
Im on 1.5.7 rooted right now, not sure if that makes any kind of difference, do I need to be on 1.8.3 or higher before I do pudding?
Click to expand...
Click to collapse
Nope. The process slightlt differs between 2.3.4 and prior.
But besides that you can unlock 1.5.7 just fine.
Jay Dogg said:
Im on 1.5.7 rooted right now, not sure if that makes any kind of difference, do I need to be on 1.8.3 or higher before I do pudding?
Click to expand...
Click to collapse
No you don't need to be on 1.83 but for easy I would recommend also if it helps these are the steps I took.
1. Unlock bootloader using auto script http://forum.xda-developers.com/showthread.php?t=1182871 (I was running 1.83) (**I did have an issue after doing this where it wiped my phone and wouldn't let me go past the MOTOBLUR login so I just flashed back down to 1.26 OTA back to 1.83 then reran the script just to make sure I was still unlocked now I only read about that happening to one other person on their forum so chances are slim of it happening**)
2. Using RSD (the latest one 5.x.x) I flashed the 2.34 sbf that comes prerooted/unlocked although the root doesn't actually work then you have to follow the preinstall root method they describe on that same post for the sbf.
I never installed CWM but I would suggest doing that one last
**Edit: yes I did forget to mention my circumstance where I flashed back to 1.26 was Im sure pure luck that I did not hard brick my phone. This is not recommended. Why my phone did not brick is still unknown.
From unlocked/rooted GB Atrix
I'm on 1.8.3, unlocked, rooted, with Gingerblur and webtop hacks (web2sd, without dock, full ubuntu).
So I'm confused as to why I cant just flash ATT-2.3.4_Pudding_preroot.sbf, it has 2.3.4/2.5.91, unlocked, root preinstalled.
Would this not give me unlocked 2.3.4 with root ready to set-up? Would I have to "clean" it or is that just optional?
People are saying to install pudding using the automatic script first, but then why create the above sbf file?
What about the 1.8.3, unlocked, root preinstall sbf file?
So if I cant use the unlocked 2.3.4 sbf file, I would first flash pudding on my phone then which 2.3.4/4.5.91 sbf file would I flash with since the OTA update won't work due to mods, and because I didnt think we should use OTA.
I want to do the method that will prevent any bricking, but I also dont want to waste time or do unnecessary flashing.
BE CAREFULLY .... IT SEEM HE/SHE WAS LUCKY WHEN HE/SHE FLASH BACK TO 1.26... IF YOU RUN THE SCRIPT AND PASS STEP 3 YOU HAVE PUDDING SO IF YOU FLASH BACK TO 1.26 YOU WILL END WITH A HARD BRICK... IT IS WELL DETAILED IN THE SCRIPT ONCE YOU HAVE PUDDING YOU CAN NOT RSD ANY DOWNGRADE VERSION OF MOTO SBF FOR EX 1.26 1.57 OR 1.83
drock212 said:
No you don't need to be on 1.83 but for easy I would recommend also if it helps these are the steps I took.
1. Unlock bootloader using auto script http://forum.xda-developers.com/showthread.php?t=1182871 (I was running 1.83) (**I did have an issue after doing this where it wiped my phone and wouldn't let me go past the MOTOBLUR login so I just flashed back down to 1.26 OTA back to 1.83 then reran the script just to make sure I was still unlocked now I only read about that happening to one other person on their forum so chances are slim of it happening**)
2. Using RSD (the latest one 5.x.x) I flashed the 2.34 sbf that comes prerooted/unlocked although the root doesn't actually work then you have to follow the preinstall root method they describe on that same post for the sbf.
I never installed CWM but I would suggest doing that one last
From unlocked/rooted GB Atrix
Click to expand...
Click to collapse
Sent from my MB860 using XDA App
I flashed the full SBF of 2.3.4 with pudding and preroot already installed and I was left with a 0x1000 error which i was able to fix by simply rebooting into fastboot mode and then running 'fastboot oem unlock'. I was really scared when I saw the error but I was able to fix it. Just an fyi for anyone else that might run into that problem.
A few weeks ago when the bootloader was unlocked, and hktw craze began I was happily running GB, a couple days into it my phone started acting crazy, would constantly act if someone was touching it, and I noticed a very small portion of the touch screen quit responding, this happened out of no where, I took the phone back to at&t and they shipped a new one to me.
Now that has nothing to do with your phone but what I am trying to say is that if hardware on your phone randomly quit working more than likely having nothing to do with mods you've done to it.. take it back, get a new one, if you can.
Goodluck
Sent from my MB860 using XDA Premium App
dcarpenter85 said:
I flashed the full SBF of 2.3.4 with pudding and preroot already installed and I was left with a 0x1000 error which i was able to fix by simply rebooting into fastboot mode and then running 'fastboot oem unlock'. I was really scared when I saw the error but I was able to fix it. Just an fyi for anyone else that might run into that problem.
Click to expand...
Click to collapse
This is a known issue and you resolved it correctly by redoing fastboot commands.
Many other people weren't so luck (didn't read instructions) and opted for an SBF back, causing them to hardbrick.
Now just so make sure before I do this, should I take path a or b
PATH A
1. You need too unlock first
http://forum.xda-developers.com/show...0#post16018910
2. You need to install Tenfars (not rom managers) CWM recovery for atrix unlocked.
http://forum.xda-developers.com/show....php?t=1138541
3. Install whatever ROM you feel you will like. I recommend Kenns ROMS
http://forum.xda-developers.com/show....php?t=1186537
or
http://forum.xda-developers.com/show....php?t=1160649 from Nav.
PATH B
1. You need too unlock first
http://forum.xda-developers.com/show...0#post16018910
2. You need to install Tenfars (not rom managers) CWM recovery for atrix unlocked.
http://forum.xda-developers.com/show....php?t=1138541
3 .Flash to Flashable SBF: Full 2.3.4 with preinstall root and pudding bootloader unlock, full sbf
4. Install whatever ROM you feel you will like. I recommend Kenns ROMS
http://forum.xda-developers.com/show....php?t=1186537
or
http://forum.xda-developers.com/show....php?t=1160649 from Nav.
Jay Dogg said:
Now just so make sure before I do this, should I take path a or b
PATH A
1. You need too unlock first
http://forum.xda-developers.com/show...0#post16018910
2. You need to install Tenfars (not rom managers) CWM recovery for atrix unlocked.
http://forum.xda-developers.com/show....php?t=1138541
3. Install whatever ROM you feel you will like. I recommend Kenns ROMS
http://forum.xda-developers.com/show....php?t=1186537
or
http://forum.xda-developers.com/show....php?t=1160649 from Nav.
PATH B
1. You need too unlock first
http://forum.xda-developers.com/show...0#post16018910
2. You need to install Tenfars (not rom managers) CWM recovery for atrix unlocked.
http://forum.xda-developers.com/show....php?t=1138541
3 .Flash to Flashable SBF: Full 2.3.4 with preinstall root and pudding bootloader unlock, full sbf
4. Install whatever ROM you feel you will like. I recommend Kenns ROMS
http://forum.xda-developers.com/show....php?t=1186537
or
http://forum.xda-developers.com/show....php?t=1160649 from Nav.
Click to expand...
Click to collapse
Path A. After flashing pudding i would avoid SBFs entirely, unless there's no other way. Any rom can be flashed via fastboot or CWM, so use that as it's much safer.
Mine says the upgrade to 4.5.141 is available to download. My Atrix is rooted with locked bootloader, I presuming I am going to lose root with the upgrade.
If so, what rooting method will work?
Thanks for your help.
PS: Will this worK?
https://market.android.com/details?id=org.projectvoodoo.otarootkeeper
charlyee said:
Mine says the upgrade to 4.5.141 is available to download. My Atrix is rooted with locked bootloader, I presuming I am going to lose root with the upgrade.
If so, what rooting method will work?
Thanks for your help.
PS: Will this worK?
https://market.android.com/details?id=org.projectvoodoo.otarootkeeper
Click to expand...
Click to collapse
Just unlock your bootloader and flash a new ROM on your phone. Most of the ROMs available for our phone have that update or better already on the ROM.
Sent from Neutrino, a planet far, far away...
cwburns32 said:
Just unlock your bootloader and flash a new ROM on your phone. Most of the ROMs available for our phone have that update or better already on the ROM.
Sent from Neutrino, a planet far, far away...
Click to expand...
Click to collapse
Thanks, but I don't want to take the route of custom ROMs, sorry.
I had to unlock my bootloader first using RSDlite and the small .sbf file (pudding.rar) Click here to download
My bootloader was supposed to be already unlocked but I guess the updated firmware didn't realize it. I couldn't run fastboot flash without getting an error
I then rooted by flashing preinstall.img and running commands to install the superuser binary and .apk. Instructions here
I don't know of a way to root 4.5.141 without unlocking the bootloader first. If you find a way let me know
http://briefmobile.com/motorola-atrix-4g-root should work.
lauterm said:
http://briefmobile.com/motorola-atrix-4g-root should work.
Click to expand...
Click to collapse
Same thing I used... different source. Still it requires an unlocked bootloader to flash images.
I believe the OP is looking for a root option that will work with a locked bootloader.
charlyee said:
Thanks, but I don't want to take the route of custom ROMs, sorry.
Click to expand...
Click to collapse
Just wondering.. Why not? ;o
nthon9 said:
Just wondering.. Why not? ;o
Click to expand...
Click to collapse
It's kind of a "Been there, done that" kind of thing from my Win Mob days. lol
I am pefectly happy with stock Atrix ROMs, and just want to be able to retain root or re root to use a couple of apps like Titanium Backup.
Has anyone with an unlocked bootloader/rooted Atrix tried the update?
I like to stick with the stock rom for now but I haven't found directions for updating to 141 yet. I'd like to keep root and not hard brick my Atrix...After the 2nd time Moto might get suspicious
I wasn't able to use the OTA updates once I rooted (even before I unlocked my bootloader). Of course, that could be Bell building in a check. I even tried unrooting (using GingerBreak) and that still wouldn't allow me to use an OTA update.
I would think you'll have to root, unlock bootloader, and then flash an firmware file from this tread: http://forum.xda-developers.com/showthread.php?t=1125944.
Actually, you're right in that the OTA update will probably fail without me going to a more "out of the box" state. I suppose I'd have to first create a nandroid, a titanium backup then flash my phone with a 4.5.91 stock image using fastboot, do the OTA, then re-root, and restore the titanium backup to get back to where I was. And if anything fails restore from my nandroid.
Does that sound right?
I've heard there could be issues relating to going back to a locked bootloader file. So I'm not sure on specifics there. I just run CyanogenMod to avoid all that stuff.
penderway said:
Same thing I used... different source. Still it requires an unlocked bootloader to flash images.
I believe the OP is looking for a root option that will work with a locked bootloader.
Click to expand...
Click to collapse
preinstall fastboot method works on a locked bootloader...at least it does for me (locked, rooted and on 141).
gnahc79 said:
preinstall fastboot method works on a locked bootloader...at least it does for me (locked, rooted and on 141).
Click to expand...
Click to collapse
So...in fastboot mode, you were able to run fastboot flash preinstall preinstall.img and thus successfully create the "preinstall\" partition with the necessary files on your phone without getting an error message???
My bootloader was unlocked long ago but I still couldn't flash the preinstall partition without running the pudding unlock .sbf first. Idk
I wasn't even able to boot into fastboot without unlocking the bootloader first.
penderway said:
So...in fastboot mode, you were able to run fastboot flash preinstall preinstall.img and thus successfully create the "preinstall\" partition with the necessary files on your phone without getting an error message???
Click to expand...
Click to collapse
yep, followed all of the steps and every one is successful. I'm very risk-averse when it comes to messing with my phone, so I've never unlocked my phone. Only root.
I love how no one is answering your question just telling you to unlock your bootloader...
I downloaded the ota update, installed and got failed to boot 4 starting rsd node.. i had unlocked bootloader before update help please!! I pulled the battery for now.
gnahc79 said:
yep, followed all of the steps and every one is successful. I'm very risk-averse when it comes to messing with my phone, so I've never unlocked my phone. Only root.
Click to expand...
Click to collapse
Well then, that settles it. The OP (who also doesn't have an unlocked bootloader) should be able to do the same.
gnahc79 said:
yep, followed all of the steps and every one is successful. I'm very risk-averse when it comes to messing with my phone, so I've never unlocked my phone. Only root.
Click to expand...
Click to collapse
Is there any way to get step by step instructions for this
This METHOD was developed ONLY for an UNLOCKED Motorola Droid Razr Maxx HD XT926m phone that is already updated to the last version of KitKat 4.4.2 (System version "183.46.15.XT926.Verizon.en.US").
IF YOU HAVE AN LOCKED BOOTLOADER AND TRY THIS METHOD IT WILL BE ONLY YOUR RESPONSABILITY IF YOU DAMAGE YOUR PHONE !!!
My Motorola XT926m had an UNLOCKED BOOTLOADER (ICS 4.0.4) and I flashed via RSD Lite the last stock firmware, "183.46.15"... After that, I was, of course, unhappy, because I read on different forums that this firmware version didn't support root... I tried to download the Hydrogen Peroxide xt926 application that others users recommended here on XDA forum, without success.
But now, after I applied this method, my phone is again rooted... Enjoy the steps, but be carefull, it was developed for XT926 phones with UNLOCKED BOOTLOADER!
1. Download the files "VZW_XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml" and "VZW_XT926_4.4.2-KDA20.62-15.1_CFC_1FF.xml" from the Motorola firmware site: "motofirmware.com/files/file/"...
2. Unpack the files...
3. Substitute/replace the "gpt", "tz" files (FROM the folder with "15.1" version TO the folder with "10.1" version)... You should replace all the files that "RSD Lite" will tell you that don't fit when you try to flash the new stock firmware. You will obtain a MODIFIED version of "183.46.10" stock KitKAt 4.4.2 firmware!!!
4. Flash this MODIFIED "10.1" firmware with "RSD Lite v6.1.5 Multi-Flash" (without using Rsd Script Generator.jar), but don't forget to remove the first two 'getvar' lines in the xml file.
5. Download and install the "Towel Root.apk" and root the phone...
6. Now your phone should be ROOTED.
What to do NEXT:
7.Download from the Play Store and install "Superuser.apk" made by ClockWordMode and after reboot the application will ask you to update SU binary. In my case, the SU binary didn't support an online update and I installed the "Superuser.zip" file downloaded from the ClockWorkMode site, via recovery method, in order to gain this update (you can do this as well, if you already have a TWRP or CWM recovery installed on your phone). With the other version of superuser, like "SuperSU.apk" or "Superuser.apk" ("eu.chainfire.supersu-2.apk", the last version, 5.6mb, for example) you will need to follow the same steps...
8. Using "Total Commander.apk", you can go to "File System root"/"Etc"/"installrecovery.sh", and finally rename this last file... Or you can use "ES3 File Explorer.apk" in order to rename the same "installrecovery.sh" file in "Device"/"Etc" folder (choose, for example, the name "installrecovery.shbak")...
9. Flash with "Flashify.apk" (downloaded form PLay Store) a new "recovery img.": "TWRP.img" (2.8.3.0) or "CWM.img" (6.0.4.8) for KitKat... You can find them on "rootjunkysdl.com/?device=Droid%20Razr%20HD&folder=Firmware"...
10. If you flashed "TWPR recovery.img" you will need to install "Stericson.busybox-1.apk" (from Play Store...), because TWRP works with this busy box... (You could install "TWRP.apk" as well, but you must be careful, because you will need to be able to boot into Recovery mode directly from your phone (with the combination key), not from this app... Many times, the phone is able to boot into recovery mode from TWRP application, but not from the bootloader... That's why it is better to uninstall TWRP application if you have this problem). If you flashed a "CWM.img" you can install "RomManager.apk".
11.Now it is the time to backup your system to SD card!
That's it. My phone was unlocked, and I didn't have any issue following all this steps... If you're locked don't try it.
But.. If you're locked you could instead use an application named 'Safestrap' for some purposes (read more here on XDA forum please), because is destinated for the phones with locked bootloader...
Hi ,
Since this is a guide it does not belong to XDA Assist
Please Read The Purpose of XDA Assist
Please Standby when Moderators Move the Thread To Your Device Specific Forum
RAZR HD General
jackeagle said:
Hi ,
Since this is a guide it does not belong to XDA Assist
Please Read The Purpose of XDA Assist
Please Standby when Moderators Move the Thread To Your Device Specific Forum
RAZR HD General
Click to expand...
Click to collapse
THANKS!
I know you took a lot of time to write this up, but there is a downgrade method posted on here already. Also, there is no need to rename recovery.sh. All you need to do after flashing recovery is power off the phone and immediately boot straight back into recovery so the install script completes.
To answer your question, no, you can't unlock .15.
RikRong said:
I know you took a lot of time to write this up, but there is a downgrade method posted on here already. Also, there is no need to rename recovery.sh. All you need to do after flashing recovery is power off the phone and immediately boot straight back into recovery so the install script completes.
To answer your question, no, you can't unlock .15.
Click to expand...
Click to collapse
Thank you, I wasn't able to find another downgrade method, could you give me the link, please?
http://forum.xda-developers.com/showthread.php?t=2789743
But... to flash CWM or TWRP for update the binaries, you need to be bootloader unlocked... to flash a custom recovery...
joel_sinbad said:
But... to flash CWM or TWRP for update the binaries, you need to be bootloader unlocked... to flash a custom recovery...
Click to expand...
Click to collapse
Correct. That's why this method is flawed and probably should be pulled before someone bricks their phone.
RikRong said:
Correct. That's why this method is flawed and probably should be pulled before someone bricks their phone.
Click to expand...
Click to collapse
Yeah, unfortunately this post makes no sense, I mean, if you accidently flash the gpt.bin, you're screwed... and so many risks, plus, you can't flash custom recovery, and you can maybe downgrade the system and boot, but you still can't downgrade the bootloader...
joel_sinbad said:
Yeah, unfortunately this post makes no sense, I mean, if you accidently flash the gpt.bin, you're screwed... and so many risks, plus, you can't flash custom recovery, and you can maybe downgrade the system and boot, but you still can't downgrade the bootloader...
Click to expand...
Click to collapse
This method is for an XT926 with UNLOCKED BOOTLOADER, with the last 183.46.15 update and the root access lost. I only described the steps that I already done with my phone. My Maxx HD is working and has root access again... I flashed custom recovery too (TWRP 2.8.3.0), I haven't any other problem.
RikRong said:
http://forum.xda-developers.com/showthread.php?t=2789743
Click to expand...
Click to collapse
Thank you, unfortunately is not working for the xt 926 phone that already took the last 183.46.15 update:
"..........************WARNING*************
this guide only works completely if you did NOT take the 183.46.15 update rolling out around 9/9/14 .............".
Until now I don't have any other option, I'm forced to preserve the method that I mentioned in my thread.
ciprianv. said:
Thank you, unfortunately is not working for the xt 926 phone that already took the last 183.46.15 update:
"..........************WARNING*************
this guide only works completely if you did NOT take the 183.46.15 update rolling out around 9/9/14 .............".
Until now I don't have any other option, I'm forced to preserve the method that I mentioned in my thread.
Click to expand...
Click to collapse
The piece you are referring to that doesn't work on .15 is the unlock and root. The downgrade should work on an unlocked phone.
That aside, your steps are very confusing and could easily cause a locked user to brick their phone. Please clarify or I will continue reporting this thread until it gets removed.
RikRong said:
The piece you are referring to that doesn't work on .15 is the unlock and root. The downgrade should work on an unlocked phone.
That aside, your steps are very confusing and could easily cause a locked user to brick their phone. Please clarify or I will continue reporting this thread until it gets removed.
Click to expand...
Click to collapse
I just edited the post. I clearly specified that this methid is ONLY FOR UNLOCKED BOOTLOADERS (XT926M).
ciprianv. said:
I just edited the post. I clearly specified that this methid is ONLY FOR UNLOCKED BOOTLOADERS (XT926M).
Click to expand...
Click to collapse
Thanks for doing that, I just want to make sure no one messes up their phone.
Hi!! I just recently rooted my phone. I heard Safestrap was the only recovery that would work with my sm-n900v. I installed 3.65 saftstrap, with busybox, and selected install recovery. then i hit reboot recovery. Instead of going into recovery, it just rebooted. so, no what. Would like to know what I did wrong or what I need to do to fix this and or another recovery that will work and not trip a security warning when the phone boots and show the yellow triangle of doom as i call it. any help will be appreciated.
Thanks in advance.
Safestrap no longer works with lollipop. Flashfire is the only real way to install zips after android 5.0.
Cheers,
B.D.
Nakerenski said:
Hi!! I just recently rooted my phone. I heard Safestrap was the only recovery that would work with my sm-n900v. I installed 3.65 saftstrap, with busybox, and selected install recovery. then i hit reboot recovery. Instead of going into recovery, it just rebooted. so, no what. Would like to know what I did wrong or what I need to do to fix this and or another recovery that will work and not trip a security warning when the phone boots and show the yellow triangle of doom as i call it. any help will be appreciated.
Thanks in advance.
Click to expand...
Click to collapse
Yeah I'm having the same problem EXACT problem, feel like I bought this phone for no reason. But, I'm having the idea of downgrading to 4.3 somehow (If it's even possible, Odin maybe?) and installing SafeStrap there, and from there I'll install a custom 6.0 ROM.
You can't downgrade from 5.x to any version of 4.x afaik.
As the prior respondents noted, Safestrap doesn't work with 5.x.
So it's a non-starter if you are already on OB6 or OF1.
From any root shell it is possible to (manually, using "dd") overwrite the recovery/boot partition with whatever recovery/boot image you prefer, but that will do you no good as unsigned kernels can not be booted unless the bootloader is unlocked. You will simply get your "triangle of doom" if the bootloader is still locked.
From OB6 or OF1, the sequence is:
- get rooted
- get unlocked
- do what you want*
*making sure you never over flash your unlocked bootloader.
bftb0 said:
You can't downgrade from 5.x to any version of 4.x afaik.
As the prior respondents noted, Safestrap doesn't work with 5.x.
So it's a non-starter if you are already on OB6 or OF1.
From any root shell it is possible to (manually, using "dd") overwrite the recovery/boot partition with whatever recovery/boot image you prefer, but that will do you no good as unsigned kernels can not be booted unless the bootloader is unlocked. You will simply get your "triangle of doom" if the bootloader is still locked.
From OB6 or OF1, the sequence is:
- get rooted
- get unlocked
- do what you want*
*making sure you never over flash your unlocked bootloader.
Click to expand...
Click to collapse
Ahh Ok, good to know. But how should I unlock my bootloader, if it's even possible? And by
bftb0 said:
- get unlocked
Click to expand...
Click to collapse
do you mean to SIM-unlock? Cheers.
GoatH3ad said:
Ahh Ok, good to know. But how should I unlock my bootloader, if it's even possible? And by do you mean to SIM-unlock? Cheers.
Click to expand...
Click to collapse
Bootloader unlock, not SIM/carrier unlock
http://forum.xda-developers.com/ver...l/official-note-3-verizon-bootloader-t3359370
Use the binary provided in post #218, not in the OP
It's a good idea to read the entire thread before you dive in.
bftb0 said:
Bootloader unlock, not SIM/carrier unlock
http://forum.xda-developers.com/ver...l/official-note-3-verizon-bootloader-t3359370
Use the binary provided in post #218, not in the OP
It's a good idea to read the entire thread before you dive in.
Click to expand...
Click to collapse
So I downloaded the manual unlocker app the guy (donc113) said i needed, didn't install the app. Then I downloaded his binary (unlock.zip) and put it in /system/bin/ like he said, I also extracted the contents in /system/bin/ as well. I installed the manual unlocker app he provided, ran it twice as he stated I needed to do. Went to ROM Manager by Clockworkmod and went to Recovery Setup, Install ClockworkMod Recovery, Selected my phone, clicked Flash ClockworkMod Recovery. Rebooted to Recovery and it still says I need to take the phone to the Verizon store. What exactly did I do wrong? I've done everything Donc113 provided and my bootloader is STILL locked apparently.
GoatH3ad said:
So I downloaded the manual unlocker app the guy (donc113) said i needed, didn't install the app. Then I downloaded his binary (unlock.zip) and put it in /system/bin/ like he said, I also extracted the contents in /system/bin/ as well. I installed the manual unlocker app he provided, ran it twice as he stated I needed to do. Went to ROM Manager by Clockworkmod and went to Recovery Setup, Install ClockworkMod Recovery, Selected my phone, clicked Flash ClockworkMod Recovery. Rebooted to Recovery and it still says I need to take the phone to the Verizon store. What exactly did I do wrong? I've done everything Donc113 provided and my bootloader is STILL locked apparently.
Click to expand...
Click to collapse
Did you:
- Check to make sure your phone CID value starts with 0x15 ?
- Record any error messages that occurred in either of the two runs of the unlocker program?
- Boot into Odin Mode to see if it says "MODE: DEVELOPER" in the last line of text over in the upper left hand side of the Odin/Download screen?
The symptoms you mention sound as if you are rooted, but failed to unlock the bootloader.
I note that you would not be asking these questions if you had read THE WHOLE THREAD as I suggested. Would you prefer that I stop helping?