Hi Guys,
I have a question/problem in regards to the recent OTA update to Jelly Bean (4.1.2) for my Droid 4. I just recently installed the update and, as expected, lost root just like with any other OTA update. So I ran motofail like I normally do to restore root. After the reboot, I noticed that "Superuser" was back on the apps screen. So I went ahead to reconfigure Titanium Backup and it says that I don't have root privileges.
Upon doing some more research, I found out that motofail does not work with Jelly Bean and I was pointed to the RAZR BLADE exploit. After running the exploit to completion, I ended up exactly where I started. "Superuser" was still there and I still couldn't use Titanium Backup. Root Checker, unsurprisingly, says that the device is not rooted properly.
My question is, where do I go from here? I would really like to restore root, but I am unsure of what to do next. Searching has yielded no results. As you can see, I am a complete noob when it comes to these devices. Any help will be greatly appreciated.
DarkMatterM4 said:
Hi Guys,
I have a question/problem in regards to the recent OTA update to Jelly Bean (4.1.2) for my Droid 4. I just recently installed the update and, as expected, lost root just like with any other OTA update. So I ran motofail like I normally do to restore root. After the reboot, I noticed that "Superuser" was back on the apps screen. So I went ahead to reconfigure Titanium Backup and it says that I don't have root privileges.
Upon doing some more research, I found out that motofail does not work with Jelly Bean and I was pointed to the RAZR BLADE exploit. After running the exploit to completion, I ended up exactly where I started. "Superuser" was still there and I still couldn't use Titanium Backup. Root Checker, unsurprisingly, says that the device is not rooted properly.
My question is, where do I go from here? I would really like to restore root, but I am unsure of what to do next. Searching has yielded no results. As you can see, I am a complete noob when it comes to these devices. Any help will be greatly appreciated.
Click to expand...
Click to collapse
Flash the jb XML through rsd lite or droid 4 utility. Then rerun RAZR blade. You'll be good to go
Sent from my DROID4 using xda app-developers app
or use the all in one tool
http://forum.xda-developers.com/showthread.php?t=2207384
sbf your phone
then re-root
Sorry to ask, but what does sbf mean?
Sbf is lazy for fastboot. Long story short what you want to do is use a sbf(.xml) file to restore your device to stock. Once you have done that you should be able to get a proper root by using the tools above. I hope i helped a bit and try not to brick
Sent from my XT894 using that xda app
DarkMatterM4 said:
Sorry to ask, but what does sbf mean?
Click to expand...
Click to collapse
.sbf is the old file format, the new is .xml
contains the phones software and is flashed with rsd lite or the droid 4 utility
Sent from my MILESTONE3 using xda premium
Alright. I ran the DROID 4 Utility. Reflashed to the official Jelly Bean (No Data Wipe). After the phone booted back up, I ran the RAZR BLADE exploit again. I am still in the same boat. Superuser is there in the apps screen, but still no root. I got the same errors with the exploit that I got the first time around. A screen capture of what I got is attached.
Where do I go from here? I really don't want to wipe all the data from the phone.
DarkMatterM4 said:
Alright. I ran the DROID 4 Utility. Reflashed to the official Jelly Bean (No Data Wipe). After the phone booted back up, I ran the RAZR BLADE exploit again. I am still in the same boat. Superuser is there in the apps screen, but still no root. I got the same errors with the exploit that I got the first time around. A screen capture of what I got is attached.
Where do I go from here? I really don't want to wipe all the data from the phone.
Click to expand...
Click to collapse
Well my friend. Try updating su/supersu binary? If not then unfortunately you will have to wipe data. :-/
Sent from my DROID4 using xda app-developers app
looks like you have razr edge root (maybe) not razr blade
see my pic
---------- Post added at 09:27 PM ---------- Previous post was at 09:25 PM ----------
are you running linux?
---------- Post added at 09:29 PM ---------- Previous post was at 09:27 PM ----------
because I just checked, razrs edge says razrs edge in windows
edit: are you running the root from the droid 4 utility?
maybe try the original root
---------- Post added at 09:41 PM ---------- Previous post was at 09:29 PM ----------
also do you have SuperSU or Superuser?
Superuser should have gotten wiped with flashing .xml, because it's installed as a system app, if it's still there
your flash failed, reflash xml with utility or try rsd lite
I GOT ROOT! I'm going to structure this post in such a way so that it will be easily searchable by those who are having the same problem.
The issue that I was having was that the RAZR Blade exploit was giving me the following errors when trying to root:
failed on '/data/logger' - Permission denied
mkdir failed for /data/logger, File Exists
Unable to chmod /data/logger: Operation not permitted
link failed File exisits
Device: Droid 4
Network: Verizon
System: XT894
Android version: 4.1.2
What I did to solve the problem:
-Settings > Apps > Smart Actions > Clear data
-Settings > Storage > ≡ Button > USB computer connection > Select "Media device (MTP)
-Ran the exploit again. Went through with no errors. Upon reboot I had root access.
After I had root access, I went back to the USB computer connection and changed back to Mass Storage mode.
Thanks for all of the help you guys gave me. I really appreciate it!
DarkMatterM4 said:
Sorry to ask, but what does sbf mean?
Click to expand...
Click to collapse
sd_shadow said:
.sbf is the old file format, the new is .xml
contains the phones software and is flashed with rsd lite or the droid 4 utility
Sent from my MILESTONE3 using xda premium
Click to expand...
Click to collapse
sbf means set back to factory
xml is one of the files used by rsdlite to do this
Two Qs follow-up
DarkMatterM4 said:
I GOT ROOT! I'm going to structure this post in such a way so that it will be easily searchable by those who are having the same problem.
The issue that I was having was that the RAZR Blade exploit was giving me the following errors when trying to root:
failed on '/data/logger' - Permission denied
mkdir failed for /data/logger, File Exists
Unable to chmod /data/logger: Operation not permitted
link failed File exisits
Device: Droid 4
Network: Verizon
System: XT894
Android version: 4.1.2
What I did to solve the problem:
-Settings > Apps > Smart Actions > Clear data
-Settings > Storage > ≡ Button > USB computer connection > Select "Media device (MTP)
-Ran the exploit again. Went through with no errors. Upon reboot I had root access.
After I had root access, I went back to the USB computer connection and changed back to Mass Storage mode.
Thanks for all of the help you guys gave me. I really appreciate it!
Click to expand...
Click to collapse
Thanks for paving the way darkmatter> I have two quick follow-up questions:
1) Does the "Clear Data" wipe a lot of data off the phone? and,
2) Can you point me to the proper exploit to use for my Droid 4 (recently updated to 4.1.2 but have now lost root- and root keeper didn't work).
THANKS!
you only need to wipe data, in smart actions, if razr blade root fails
link to razr blade root, in my list, look in root section
sd_shadow's list of links for Droid FAQs, SBF, Rooting, ROMs.... https://docs.google.com/document/d/1Goawxdx_UBF4Y8lqzHYWf8Ha3yUcRK4faq0UWIlXLWA/edit
Sent from my XT862 using xda premium
What's the process for using the razor_blade.zip exactly? Hook up the phone to the pc, have the .zip ready, then what?
Thanks
Just follow the on screen directions... its pretty easy...
Sent from my DROID4 using xda app-developers app
SBF is NOT a verb...
ovelayer said:
sbf means set back to factory
xml is one of the files used by rsdlite to do this
Click to expand...
Click to collapse
SBF is a file type and stands for Single Binary File that is the older format of Motorola flash files for use with RSD lite or other flash tools.
They include all of the code groups, header files and checksums as well as a RAM Downloader for all of the device partition images in a single file and flashed from the legacy boot loader enumerated as a flash device.
The new format for all dual core Motorola devices is zip archive of fastboot images and an XML file that can be used with RSD lite to flash in a single operation or flashed as individual images using the fastboot binary and DLLs in the Android SDK from the fastboot boot loader and enumerated as an ADB device.
These are entirely different modes of access and operation and SBF is both wrong and a misnomer for the firmware files for current devices.
The fast boot interface provides far more flexibility and safety for flashing than the old flash interface and avoids all kinds of problems that would arise from managing and updating he firmware on newer chipset devices.
It is an extremely important distinction to make and understanding to have about how these phones work.
Please stop using SBF when referring to XML.zip files.
The current acronym for Motorola firmware files is FXZ and means Full XML ZIP file.
FXZ is a made up term.
SBF is an official Motorola file type as is an XML.zip or tar.gz
thank you, I was hoping someone would clear that up, better than I could
Sent from my XT862 using xda premium
ovelayer said:
sbf means set back to factory
xml is one of the files used by rsdlite to do this
Click to expand...
Click to collapse
Dude, that's not true. Sbf stands for system binary file.
Sent from my XT894 using Xparent Cyan Tapatalk 2
edit: wrong thread
still no luck
i'm still having the same problem as darkmatter, even after trying the steps posted above. any other advise? i've tried it in both windows xp and ubuntu
Related
Hey guys,
Trying to help a buddy at work unlock his driod1 - he updated to FFRG22D - now any of the single click root methods do not work..
My phone is a nexus1 and did not have these issues: As I am not a Droid owner / user I am hoping people in the forums here help to get him rooted.
I would like to get him on to ClockWork - so we can flash CM6 on his droid.
Can someone point me to a good guide to rooting this?
Cheers,
hey if he is OTA FRG22D can you please post his build.prop file for me to take a look at, it can be found under /system on phone memory, i am working out a market fix for rooted frg01b users like my self, i wont update until after frg22d is rooted for real but i can spoof the version and fingerprint if i have that file contents
i found what i was looking for after a while, thanks.
vitosans said:
Hey guys,
Trying to help a buddy at work unlock his driod1 - he updated to FFRG22D - now any of the single click root methods do not work..
My phone is a nexus1 and did not have these issues: As I am not a Droid owner / user I am hoping people in the forums here help to get him rooted.
I would like to get him on to ClockWork - so we can flash CM6 on his droid.
Can someone point me to a good guide to rooting this?
Cheers,
Click to expand...
Click to collapse
Have you had any luck? My buddy had his phone replaced and the new one has this update, but he would like me to root it again for him.
can you not just download the old froyo, put it in the sd as update.zip, flash that then root?
FRG22D hotspot app
I have the OTA FRG22D stock unrooted. In-order to root it, I used the following procedure, from droidforums:
"Root Droid 1 - regardless of OS version". After installing the custom recovery:
"MC1_A855_1282081087_Recovery-Only_SPRecovery_0.99.3b.sbf", I was then successful installing a wifi hotspot app
bpickens said:
I have the OTA FRG22D stock unrooted. In-order to root it, I used the following procedure, from droidforums:
"Root Droid 1 - regardless of OS version". After installing the custom recovery:
"MC1_A855_1282081087_Recovery-Only_SPRecovery_0.99.3b.sbf", I was then successful installing a wifi hotspot app
Click to expand...
Click to collapse
little bit more than that but +1. Thanks for that thread though, trying to root a friend of mines Droid after he got that frd22 build it wont let him use rootme
Check this link for both Odexed/DeOdexed rooted builds of FRG22D:
peteralfonso.com/p/downloads.html
Sent from my Droid using XDA App
So to root I just rename the file to update.zip and install it that way?
Sent from my SAMSUNG-SGH-I897 using XDA App
The one click root apps do not work with FRG22D. The exploit those apps used was patched with this release.
The FRG01B & FRG22B stock/odex/deodex only work for devices that are already rooted. Meaning that if you do manage to imstall them you will not have root.
You need to do a *sbf* back to 2.1 or2.01.
root droid regardless of os version.
http://www.droidforums.net/forum/droid-labs/74028-root-droid-1-regardless-os-version.html
Sent from my Droid using XDA App
look around for motocache post
Installed latest stock
Flashed Sprecovery
Flashed his package which roots and disables the attempt at the droid to unroot
well, ****. I'm new so I can't post outside links yet, but go to droidforums and search "[HowTo] Root, Deodex, and Theme Droid Froyo 2.2 FRG22D"
worked fine for me, no issues so far.
Use the rsdlite process, hold the x down on your phone when it says rebooting
Sent from my HTC Magic using XDA App
I'm new to the Droid 1 I came from the Eris and it is easy!!!!
Okay so I did it with out even having internet on my pc or Linux laptop which thank god I finally got internet today!!!! Use the rageagainstthecage-arm5.bin method... Super easy I actually downloaded using my D1 transfered file from my phone to Linux laptop and changed the Windows commands to Linux commands and it worked and then I went in to market and flashed Clockwork!!!! Oh and yes I'm on FRG22D the phone came as a replacement for my Eris and it already had this build on it... PM me if you have any questions...
hi all,
i just get used moto droid, i check the firmware seems already using FRG22D
how to check wheter my phone has been rooted or not ?
thanks before
Try using a root required free app from the market and if you are root it will work if your not it wont... Easy as that!!!!
May UniversalAndroot works?
Sent from my XT702 using XDA App
Hexchain said:
May UniversalAndroot works?
Sent from my XT702 using XDA App
Click to expand...
Click to collapse
It doesn't.
The method that RodNoc_eR just mentioned above just worked for me. Here's the link again: http://www.droidforums.net/forum/droid-labs/74028-root-droid-1-regardless-os-version.html
for those of you who are doing this the complicated way, THERE IS a ONE-CLICK METHOD, since I cant post links, Google SuperOneClick, download and find instructions, its pretty much as easy as downloading the .zip, extracting it to where ever you want, right click on SuperOneClick application and Run as Administrator, make sure USB debugging is checked, DO NOT mount as USB storage device, click root button on the program, let it do its thing, and wa-la!
You have acheived root! Be sure to download the Custom Recovery of your choice, which is as easy as DLing Rom Manager from the Market and flashing ClockworkMod, I just did this and am now happy I spent time searching and not typing commands into the SDK, super easy and it works for the DROID 1 FRG22d, I just did it.
Enjoy!
Used P3's 1-click to get back on the upgrade path and take my phone to 901 and lost root. I was rooted prior with forever root applied. The script appeared to run fine and 901 was applied with the phone running okay ... except root is no longer there. Titanium ran okay prior. All other things about the phone work great ... 4G does appear to be a bit more responsive.
One thing of note was that during the script when zergRush was being applied I remember seeing a "Hellions with BLUE flame" popped up in the script.
Any help will be appreciated.
Mine did the same thing. Are you sure you were rooted before with forever root? And are you sure you dont have super user?
TheMuffStuff said:
Mine did the same thing. Are you sure you were rooted before with forever root? And are you sure you dont have super user?
Click to expand...
Click to collapse
I definitely had root prior to the 1-click ... I have been running Titanium Backup for a few months now. And yes, I still have SuperUser on my phone.
If you go to P3s post at MDW, realbbb has a download on page 4 that works perfectly. I simply ran his script straight over the results ofP3's script and had no issues whatsoever.
Sent from my DROID BIONIC using xda premium
cappiez said:
If you go to P3s post at MDW, realbbb has a download on page 4 that works perfectly. I simply ran his script straight over the results ofP3's script and had no issues whatsoever.
Sent from my DROID BIONIC using xda premium
Click to expand...
Click to collapse
Were you on 901 when you reran the bbb script over the top of p3's? I'm assuming "reran over the top" means no additional pushes, etc., just used the bbb batch file instead.
Yes realbbb's fixed script will work if run again over the BionicPathSaver. Be sure you have unzipped his BPS fix.zip into the same directory and use the runmebbb.bat file.
cellzealot said:
Yes realbbb's fixed script will work if run again over the BionicPathSaver. Be sure you have unzipped his BPS fix.zip into the same directory and use the runmebbb.bat file.
Click to expand...
Click to collapse
Thanks CZ.
Strange thing happening now. When the bbb batch tries to push the first files over to the sd I'm getting an "error:device not found".
I've got the latest Moto drivers installed. Even uninstalled and reinstalled. Using USB cable that was shipped with the phone. USB debug is definitley on. Phone is definitely set to charge only.The device was recognized before when I did the P3 1-click.
Win7-64 bit recognizes the phone and the sd-ext card when I change to mass storage. I've tried to manually push files and same error.
adb shell command works. cd /data/local works along with the ls command of what's in those directories. Just won't allow a push.
EDIT: Well, I dusted off the old stone knives and bear skins and loaded up XP from the dual boot. Put the Moto drivers on there and Bam, I'm in. Guess my Win 7 64 bit has some old Moto driver bits floating around somewhere ... or perhaps just a bit of preanimate matter caught in the matrix. Either way ... 901 update has a few more minutes on its install. Thanks again.
i'll be giving this a try.
i used the 1click upgrade path (which don't get me wrong is AMAZING!) but i'm really, really surprised that there's no warning of loosing root access.
5.9.901 does seem to have fixed ALOT for me though and i know i'll have root again soon...
anyone using the one click coming from a version of 5.7.893 without the webtop?
I've seen posts of people without the webtop getting stuck in bootloops
Worked for me and restored Web top.
Sent from my DROID BIONIC using xda premium
I rebooted the phone when I got the error:device not found, and head no troubles afterwards.
I bootlooped when coming from 5.7.893 with no webtop. I flashed back with released & forever root. Then, BPS. Lost root at that put.
So, if you have 5.7.893 flash back to 5.5.893, then do realbbb's BPS fix and you should be good.
I am trying to update to ics from 2.3.6 I have uninstalled safestrap and frozen root with otarootkeeper. I get hung up during install, so I checked my error log. It seems I am missing files from /preinstall specifically from /knowyourdevice which no longer exists. Is there a way of getting a copy so I don't need to go through fast boot? There was a link up elsewhere, but it's dead. Any help is greatly appreciated.
I recommend to flash fastboot 4.0.4 files.
I know, but this has turned into a pet project for me. I was really hoping to do it the hard way. There was a link up in the dev forum, but it's dead now...
I had the same issue when upgrading. Turns out, the update scans your system for ANY modifications that would signify you were, or had been rooted. You either need to completely remove anything that signifies you are rooted and any apps that require root, or sbf to either gb or ics. Doing a simple factory format still leaves files behind. Honestly, just doing an sbf would easier, as it ensures your system is 100% clean. If you need new links to the one click sbf, I can pm you a link later.
Sent from my DROID4 using xda premium
I had this problem and just downloaded the fastboot files, extracted the /preinstall archive from there, and copied it to my phone using adb. Simple.
Sent from my DROID4 using Tapatalk
has anyone found a way to root the latest offical ICS 4.0.4 build 6.7.246? i lost root after installing it. thanks.
Motofail for ICS
I was able 2 using razors edge jus make sure debuggin and custom apps are checked
Sent from my DROID BIONIC using xda app-developers app
it worked!
hey thanks, it worked!!!
Sir_Eagle said:
Motofail for ICS
Click to expand...
Click to collapse
Phone not showing ICS
I can't get my son's phone to show the update as available. Has anyone posted the zip file out there for other users to install the ICS update?
shduong said:
hey thanks, it worked!!!
Click to expand...
Click to collapse
Mind sharing where you found it? I'm finding links but not sure which is right. I'd rather just use whatever you used since I know it will work.
uggghhhh. I was just going to use OTA Rootkeeper but ever since I updated to .905 my adb does not work. My phone will not mount to the computer at all, it won't read my SD Card, only charge the phone. So I tried to fix it by flashing a FXZ through RSDLite, because that fixed it last time it happened 6 months ago, and it didn't work. So I'm just going to install the update, and hopefully it will fix my adb. If not, I have no clue how I'm going to root this ******* phone!!! its so frustrating! If anyone knows of a way that I could edit some rooting script to connect through adb wireless, please let me know. I would even be willing to pay someone like ten or fifteen bucks if they could give me a working script to root through adb wireless, or some other way, which I've never heard of.
shduong said:
hey thanks, it worked!!!
Click to expand...
Click to collapse
Please let us know where you found the motofail-ics download that you used. Also, did you just have usb debugging checked or did you need to check other options as well?
Motofail-ics is included in the thread at the top of the page titled 905 to ICS update... worked for me
Sent from my DROID BIONIC using xda app-developers app
---------- Post added at 09:03 PM ---------- Previous post was at 08:21 PM ----------
It is included in the guide in the sticky section..
Sent from my DROID BIONIC using xda app-developers app
bonzai276 said:
Motofail-ics is included in the thread at the top of the page titled 905 to ICS update... worked for me
Sent from my DROID BIONIC using xda app-developers app
---------- Post added at 09:03 PM ---------- Previous post was at 08:21 PM ----------
It is included in the guide in the sticky section..
Sent from my DROID BIONIC using xda app-developers app
Click to expand...
Click to collapse
I also used the motofail-ics posted in the guide and had no issues.
sytech55 said:
I can't get my son's phone to show the update as available. Has anyone posted the zip file out there for other users to install the ICS update?
Click to expand...
Click to collapse
https://docs.google.com/file/d/0B7z9xJrt55a6bFM0YUV1amhLZVU/edit?pli=1 enjoy
Instructions Links
Mobifail-ics
Source: http://forum.xda-developers.com/showthread.php?t=1771993&highlight=motofail - Original post
In addition to that post you will be able to get everything you need to download and install the latest ICS version and root your device.
- Cheers
motofail ics failed for me
Just hot a replacement bionic in the mail and am about to send back my rooted 2.3.4 running eclipse 3.0. I updated the replacement w 4.0.4 and tried the wonderfully simplified motofail ics, usb debugged (not in mtp mode) it recognized device, started daemon, then stalled out for 20 min....? I unplugged read up some more switched to mtp mode and now it claims its waiting for device to be ready..... i am a unlimited data grandfather who relies on my unlocked wifi tether.... any guidance?!
tonamaste said:
Just hot a replacement bionic in the mail and am about to send back my rooted 2.3.4 running eclipse 3.0. I updated the replacement w 4.0.4 and tried the wonderfully simplified motofail ics, usb debugged (not in mtp mode) it recognized device, started daemon, then stalled out for 20 min....? I unplugged read up some more switched to mtp mode and now it claims its waiting for device to be ready..... i am a unlimited data grandfather who relies on my unlocked wifi tether.... any guidance?!
Click to expand...
Click to collapse
How did you update to ICS? Over the air update? I ask because if you updated it via FXZ and Fastboot mode with RSD Lite, then what I'm about to suggest is moot. But if you took the OTA update, then it makes more sense.
I'm betting that either your computer doesn't have the right Moto drivers on them, or that you're plugging it into a bad port. They can be finicky.
Go here: http://forum.xda-developers.com/showthread.php?t=1771993
Grab the USB drivers mentioned in step (4).
Then make sure that you're plugging your phone into a USB port on the back of your computer, not an external USB hub. Also don't plug it into USB 3.0. This may not actually be the issue but I accidentally used my USB 3.0 port once to Motofail and it didn't work at all. If you already tried one of the back ports, or are on a laptop, just try another port.
MrChupon is spot on. I had the exact same problem until i went Motorola and grabbed the very latest drivers. Worked like a champ after that.
Sent from my DROID BIONIC using Tapatalk 2
It was over the air, from a fresh stock VZW replacement. For what ever unknown reason it stalled out once it started daemon..... I pre maturely ejected it, and I think it left the device in a partial state, and when reattempting in my 2.o port it was confused and left me hanging.... so in my sleep i decided to try a factory reset to flush the cache so to say and motofail proved to be a fantastic success! (Using my wifi right now thanks to some sqlite value adjustments! Thanks for the wisdom and words regardless!
tonamaste said:
It was over the air, from a fresh stock VZW replacement. For what ever unknown reason it stalled out once it started daemon..... I pre maturely ejected it, and I think it left the device in a partial state, and when reattempting in my 2.o port it was confused and left me hanging.... so in my sleep i decided to try a factory reset to flush the cache so to say and motofail proved to be a fantastic success! (Using my wifi right now thanks to some sqlite value adjustments! Thanks for the wisdom and words regardless!
Click to expand...
Click to collapse
Premature ejection will get you every time!
Sent from my DROID BIONIC using Tapatalk 2
Hey guys,
Long story short, I am currently on the JB Leak'sOTA update. Problem: My phone is a little slow and the Root Checker app says my system is running slow, I think my kernel or something is damaged from how I kept root through the OTA. I can't go back to ICS or the JB leak from where I am so my only option for a fresh start would be to flash stock Jellybean. Is this possibly yet? I know the bootloader is locked but are the Fastboot files available? I had already pmed a couple devs about this a while back.
I am getting my HTC One X+ this weekend soI can test any untested Fastboot files that have risk of bricking of Atrix HD. It isn't vital, I would just like to get it back to full speed if it's possible!
I'd use rsd lite and flash the sbf for jb.
Need stock JB
Youngunn2008 said:
I'd use rsd lite and flash the sbf for jb.
Click to expand...
Click to collapse
I have sort of the same problem. Bought the phone with stock JB installed. Rooted with new exploit yesterday, left my brain in another room, and started uninstalling things left and right in Titanium Backup - of course without making a backup.
Of course now the phone is starting to act up - hardware wise - and I need to get it back to stock before sending it in to Moto. So would the sbf for jb be the solution, and where could it be downloaded? Also - would it delete that nasty "qe 1/1" message in stock recovery - you know, the one ratting out that you've been naughty?
Thanks!
Flash using RSD (remember to edit the xml the same way)
You won't have issues, however you'll have to root again
Sent from my Atrix HD using Tapatalk app
BreakShadow said:
Flash using RSD (remember to edit the xml the same way)
You won't have issues, however you'll have to root again
Sent from my Atrix HD using Tapatalk app
Click to expand...
Click to collapse
"remember to edit the xml the same way" - I don't understand that part. What file am I to edit, and what am I adding/replacing?
You have a zip file right? If you don't, the FXZs are in zip/rar format.
You need to extract it. It contains the stock data and an xml file.
When flashing using RSD you have to point to the xml file.
Open up the xml using notepad, ctrl+f and search for 'getvar', there'll be two lines containing it, remove those lines and save the file. Continue.
It'll work without issues
Sent from my Atrix HD using Tapatalk app
Youngunn2008 said:
I'd use rsd lite and flash the sbf for jb.
Click to expand...
Click to collapse
Do you mind linking me to the downloads?? Just want to make sure I get the right stuff. Just the standard US ATT version of the phone.
BreakShadow said:
You have a zip file right? If you don't, the FXZs are in zip/rar format.
You need to extract it. It contains the stock data and an xml file.
When flashing using RSD you have to point to the xml file.
Open up the xml using notepad, ctrl+f and search for 'getvar', there'll be two lines containing it, remove those lines and save the file. Continue.
It'll work without issues
Sent from my Atrix HD using Tapatalk app
Click to expand...
Click to collapse
Well that didn't work out too well...I was on stock JB. Rooted with new exploit. Installed bootstrap and custom ROM. Wanted to get back to stock, so I uninstalled bootstrap, and flashed MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip.
RSD failed with 'getvar' and 'oem'. I then edited the xml, removed 'getvar' and 'oem', and retried the flash. RSD failed at system.img.
I then booted the phone into fastboot and did the whole thing manually thru fastboot and terminal. This time everything went through okay. I rebooted the phone into stock recovery and erased cache. But now the phone is stuck in bootloop on the red m logo.
What am I missing?
Use RSD again, use 6.1.4
I remember mine failed at least 2 times, I kept retrying and it worked. Mine was stuck at the system.img too, just retried and it went througj
Sent from my Atrix HD using Tapatalk app
It´s time to unify those informations in a single thread..
Root ICS, Root JB, Install SS, back to stock ICS, back to stock JB and maybe a ROM index (only joker and batakang for now, I know, but other ROMs are probably comming)