Related
Ok so this is whats been happening. I have an eris im trying to load a custom rom on after I did the 2.1OTA
When I came out to XDA to use the root I was at first confused since it was all going from 1.5 to 2.1. After reading further I read reports that 2.1OTA is rootable just like 1.5 as long as I follow the proper steps.
I: Gaining root
An unlocked hboot will allows us to flash in a modified IMG ROM signed with test keys as supposed to requiring an official ROM from HTC. This will open us to be able to flash a modified recovery.
1. Download this file: PB00IMG.zip (md5: 63eacc5ede3b179f95dc22d8ef585f94)
2. Place PB00IMG.zip onto the root directory of your sdcard.
3. Power down your phone.
4. Hold Volume Down while you Power On. This should bring you to a screen saying "HBOOT" and some other stuff. Wait for it to load the image, and it will say Push Activate. Push the trackball button to continue. The process will take around 5-10 minutes. The first time your phone boots up it will take a lot longer than normal.
Click to expand...
Click to collapse
I think this is where things go wrong. When this was attempted it I saw that my bootloader was now reading 1.49 (phone never been rooted before) instead of the one people report you need to root which is 1.47
It loaded up under 2.1 still and I believe its still the 2.1OTA so I head on to next step for recovery img. something seems to have gone wrong with it too (possibly me messing up the sdk) as now when I try to load any recovery images via fastboot "FAILED <remote: not allow>
Now the more trouble part is now that its ready I follow the instructions on how to actually load the rom through the recovery and SD card method. I believe my recovery is not what its supposed to be either as when it loads I see an android next to a caution symbol with a yellow ! and when the recovery screen is brought up I only have 4 options. Ill type abit what I see
"
Android system recovery <2e>
Use volume key to highlight:
click power key to select.
Reboot system now
Apply sdcard:update.zip
Wipe data/factory reset
Wipe cache partition
E:Can't open /cache/recovery/command"
Now I have tried the instruction of wiping first with a data and cache wipe but it does not give me any options after that on to flash from sdcard
IV: Flashing a custom ROM
1. Download the Rooted 2.1 v0.8T2 zip file.
2. Copy the WHOLE zip file to the root directory of your SD card. (You can enable USB-MS enable from your shiny new recovery to mount your phone as a USB Mass Storage device.)
3. Choose Wipe. Choose data/factory Reset (In the stock ROM, the dalvik is stored in the data and you don't have an EXT partition... yet.)
4. Choose Flash zip from sdcard. Find the eris_0_3.zip file.
5. Wait until it shows as complete and choose reboot system now.
Click to expand...
Click to collapse
I have tried putting different ROM's on my sdcard. I attempted to downgrade using the tutorial provided and using the official RUU from PCD's website. (which both didnt work as downgrade would stop at recovery or RUU states wrong bootloader version towards the middle of the load) and I tried even renaming the ROM's to update.zip the message I get everytime is the same with 2 results one for the rom without the update.zip and one with it.
(with update.zip)
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted
(without update.zip)
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted
Also for those wondering I followed the method of installing drivers and using debugging mode ....all drivers seem to be working fine.
Also just for further info when I run the RUU to try and downgrade my bootloader goes back to showing 1.47 but the radio is still 2.40 if this gives and help
If some could first tell me where I went wrong and then where to go from here I will be most appreciative and im even willing on putting out a reward if someone can do this for me quickly (I am poor some it wont be a big reward but it will be something)
Thanks for any help.
This means you are on the leaked version now and there is nothing that can be done as of right now.
K well thanks for the short and sweet answer. Can anyone tell me how I went from stock 2.1OTA to getting the leaked verision? was it step number one that did it? something didnt load correctly after that?
ca2l3vin said:
K well thanks for the short and sweet answer. Can anyone tell me how I went from stock 2.1OTA to getting the leaked verision? was it step number one that did it? something didnt load correctly after that?
Click to expand...
Click to collapse
So you saying you had 1.5, then got the OTA update from Verizon?
If that is true, are you sure you downloaded the correct root image? Cuz if I remember correctly, the non root one is named the samething. But I could be wrong as I never tried leak.
sounds like you got a bad pb001.img file.
ca2l3vin, it sounds like you may have downloaded and flashed the wrong PB00IMG.zip file. Where did you get it from?
nevermind addressed my issue
As far as I understood I got it from the tutorial was the first place I got it. After I started to have issues I downloaded it from another site thinking I could just update with correct one. Same name same file size and unfortunately same results.
also I did forget to put in my build number like the above post so ill drop that in now.
Firmware Version
2.1
Baseband Version
2.40.00.01.22
Kernel Version
2.6.29-5898f66b
[email protected] #1
Build Number
2.19.605.1 CL123435 test-keys
Software Number
2.19.605.1
Browser version
webKit 3.1
PRI Version
2.11_002
PRL Version
51866 (I know this is just area based)
ERI Version
5
ca2l3vin said:
As far as I understood I got it from the tutorial was the first place I got it. After I started to have issues I downloaded it from another site thinking I could just update with correct one. Same name same file size and unfortunately same results.
also I did forget to put in my build number like the above post so ill drop that in now.
Firmware Version
2.1
Baseband Version
2.40.00.01.22
Kernel Version
2.6.29-5898f66b
[email protected] #1
Build Number
2.19.605.1 CL123435 test-keys
Software Number
2.19.605.1
Browser version
webKit 3.1
PRI Version
2.11_002
PRL Version
51866 (I know this is just area based)
ERI Version
5
Click to expand...
Click to collapse
I hate linking back to another forum, but I used this guide and it worked flawlessly for me.
http://androidforums.com/all-things-root-eris/53963-guide-stock-1-5-latest-root-2-1-a.html
Did not check your link to see if its teh same but I can vouch that this one is 100% working.
af man...seriously!
out of curiously i reboot my phone via power + volume up and saw my hboot version 1.49.... it's werid because I had my phone rooted long ago when I was running on 1.50. Anyway, I'm still able to boot into Amon_RA's recovery and using Tainted Vanilla ROM as of now. I'm thinking it might be because of *228 actually reprogrammed SPL somehow, because i saw glimpse of message during programming phase, it said "SPL unlocked" and "OTA update completed"
HAAZAAAA!!!! Thanks to droidkevlar
So what happened was the wording on the original tutorial confused me quite abit. basically on the recovery step I skipped over it completely due to the fact that it was worded as an optional step for just creating your own recovery point. Once I read the guide linked by droidkevlar I see that THAT is the actually Amon's Recovery image needed to load the custom ROMS in the first place.
ITS A NEEDED STEP not really an optional one (unless your a dev I guess)
I just did my first flash to the EvilEris Rom and now will be trying others out.
I think the tut should be possibly re-worded as I have seen others that seem to be in the same boat I was in. or atleast put in that all steps are needed.
Anyways all the steps and files are the same on both so just follow them both out all the way and it works with 2.1OTA
ca2l3vin said:
HAAZAAAA!!!! Thanks to droidkevlar
So what happened was the wording on the original tutorial confused me quite abit. basically on the recovery step I skipped over it completely due to the fact that it was worded as an optional step for just creating your own recovery point. Once I read the guide linked by droidkevlar I see that THAT is the actually Amon's Recovery image needed to load the custom ROMS in the first place.
ITS A NEEDED STEP not really an optional one (unless your a dev I guess)
I just did my first flash to the EvilEris Rom and now will be trying others out.
I think the tut should be possibly re-worded as I have seen others that seem to be in the same boat I was in. or atleast put in that all steps are needed.
Anyways all the steps and files are the same on both so just follow them both out all the way and it works with 2.1OTA
Click to expand...
Click to collapse
Glad I could help. Aloysius is also a very good one to check out. Heard there are issues with v12 but v11 maps is solid!
Alright, just bought a Thunderbolt as of Friday night and didn't get to root it until 11AM Saturday due to random issues (It was just a pain between ADB not wanting to work, EasyRoot freezing, etc.) so I figured I'd post this method.
All credit goes to Saboture for writing his guide for the EVO using the same method and for helping me.
Please note: This method does NOT root your phone, but unlocks your bootloader (sets flag to S-OFF) and flashes a recovery so that you can simply install a rooted ROM. Do this at your own risk! I am not responsible for any bricked phones or issues, all that good jazz. Also, only Windows and Linux are supported (At this time.)
Step one: Install HTC Fastboot drivers (The utility will not work if you have HTC Sync installed.) Link: http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
Step two: As always, make sure your phone is at least charged to 80%, but 100% is fully recommended. Plug your phone into your computer and set to Charge Mode.
Step three: Go to http://revolutionary.io and scroll down and click the proper download link. The file will start to download (Or you will get a prompt depending on browser) Followed by a Beta Key menu opening on the website. From here, input the basic information (Serial Number, H-Boot version, etc.) Once this is done, you will get a beta key.
Step four: Once done downloading Revolutionary-0.4, extract the contents of the folder and run .exe
Step five: If drivers are installed and your phone is properly connected, follow the onscreen instructions (and install the custom recovery for ease of use) After a full reboot sequence...done! Your S flag is now set to off!
Now you've unlocked your phone, simply flash a ROM in recovery (Following proper methods such as loading radios and all that goodness.)
Hope this helps those who are as frustrated as I was!
kekeke. Good write up man. Hopefully this will do as you hope and save some others the trouble.
lol nice post... if you would would have looked at the top of the page you might have saved yourself some time rooting and also writting this thread
http://forum.xda-developers.com/showthread.php?t=996616
see the big red letters at the top of the post?
OUTDATED
Augest 14 2011
Unrevoked and AlpharevX released a new version of their http://revolutionary.io/ tool, use it, and preserve your data.
Hello everyone! My names Danny, sorry I'm extremely frustrated at the moment and apologize for not introducing myself properly in what ever you call your newcomer section here, but I'm ripping my hair out at the moment.
So last night for the 4th time I tried to root my Galaxy S4, again unsuccessfully. While I admit I am no programmer, computer whiz, or rocket scientist, I have previously rooted my old S3 and my girlfriend's Moto Photon successfully in the past, on the 1st try (although they were pretty simple 1 click roots no more difficult than the one I used here, or so I thought.) Now last night I tried to use the CF-Autoroot again for the 3rd time, which i figured after the first 2 attempts was doomed to failure also. This may be due to the fact that I updated it, but I don't know. I'm hoping someone here can point me in the direction of a root that will work with my phone, show me where I may have went wrong in the install,or give some instruction on how to delete the update so I can use the CF-Autoroot. As long as my phone will still function as normal, I could care less which option is used, however I do not have any programming experience whatsoever, so a simpler root would be excellent. I'll give you all the info I can below.
Software version: L720VPUAMF9
Hardware version: L720.08
Model #: SPH-L720
Android version: 4.2.2
Baseband version: L720PUAMF9
Kernal version: 3.4.0-953334
[email protected] # 1
Tue Jun 25 09:36:29 KST 2013
Build #: JDQ39.L720VPUAMF9
SE Linux Status: Permissive
Secure boot status: Type: Samsung
Device Status: Custom (No Triangle Away quite yet, as I'm not sure if it is yet supported on the S4, or if I even need it since I plan on keeping the phone)
Root was done on HP Windows 7 laptop 64-bit, with the phone in camera mode prior to turning off and going into download mode.
I followed the instructions on honai-android.blogspot(dotcom) using CF-Autoroot and Odin V3.07 to the T, except I have yet to get the drivers to install correctly (or so it tells me, everything works fine,) and in Step 4 it says the box should turn yellow and a port number displays, but in my case did not. It did display the "Added" message in the little box like it should have, but it did go through the whole process and I got a PASS notification as it says I should have. I have no idea why it won't work, other than maybe the drivers are screwing me. Ran Root Checker and it tells me "Please wait for Root Check to complete. System appears to be running very slow," and Titanium Backup won't work either. Root checker stayed like this all night last night while I slept.
Also I would appreciate some help reverting it back from the root I apparently didn't install, although I know some of it went through, or Root Checker would just say I didn't have superuser access.
I'm hoping one of you guys here might be able to help me out with this problem, and I greatly appreciate any help I can get. If anymore information is needed, just ask. Much thanks in advance.
You said you used Odin in camera mode? Did you mean download mode? I didn't have to install any drivers to get Odin to work. If you didn't get a yellow box with a com number in it the Odin didn't write anything to your phone. If you look here in the dev section there is a thread titled cf auto root. Download the zip file there and follow those directions and give it another try.
SGS4 Sent
ifly4vamerica said:
You said you used Odin in camera mode? Did you mean download mode? I didn't have to install any drivers to get Odin to work. If you didn't get a yellow box with a com number in it the Odin didn't write anything to your phone. If you look here in the dev section there is a thread titled cf auto root. Download the zip file there and follow those directions and give it another try.
SGS4 Sent
Click to expand...
Click to collapse
No my S4 was in camera mode. There are 2 options when I plug my phone in via USB to the PC, either camera mode or media device mode, PTP and MTP respectively. This is how it was set up before I turned the phone off to go into download mode, didn't think it made a difference, but I wanted to give as much info as possible. The phone went through all the downloading stuff on-screen with the red pirate android guy and everything while Odin was downloading to the phone, and Odin also said Added in the message box so I figure Odin recognized the device was present. I'll check out that thread though, thank you:good: I'll be back here if it doesn't rectify the situation.
I see my first problem, stupid tutorial I used the first time said to put Odin in Repartition and F-Reboot. QBKing says only Autoreboot. Man I hate crappily done tutorials.
Just also noticed he mentions the yellow box and com/port number are vital to the success of the root, something I overlooked all 3 times I tried it.
Stuck at the stupid com box again, now it wont change at all and i'm not getting the added message either....
Downloaded the drivers for the phone he gave also and still nothing....tried 3 different USB cables like he suggested too and still stuck.
Think I might need to unroot or delete the other crap I installed before? I'm out of ideas.
pumpdatbass420 said:
Stuck at the stupid com box again, now it wont change at all and i'm not getting the added message either....
Downloaded the drivers for the phone he gave also and still nothing....tried 3 different USB cables like he suggested too and still stuck.
Think I might need to unroot or delete the other crap I installed before? I'm out of ideas.
Click to expand...
Click to collapse
ok try this from the beginning
1. reset phone factory reset via recovery ( hold power up - home - and power button ) simultaneously and once you see blue recovery text top left corner let all the buttons go. select factory reset and proceed with reboot.
2. press ##3424# and select pda and make sure you have MTP-ADB selected
3. try rooting your phone via ODIN
PS: if it does not work change step 2 under PDA setting to DM-MODEM-ADB then root and once rooted change it back to step MTP-ADB
let us know if this works for you
saj070 said:
ok try this from the beginning
1. reset phone factory reset via recovery ( hold power up - home - and power button ) simultaneously and once you see blue recovery text top left corner let all the buttons go. select factory reset and proceed with reboot.
2. press ##3424# and select pda and make sure you have MTP-ADB selected
3. try rooting your phone via ODIN
PS: if it does not work change step 2 under PDA setting to DM-MODEM-ADB then root and once rooted change it back to step MTP-ADB
let us know if this works for you
Click to expand...
Click to collapse
Step 2...am I doing this on the phone or in Odin? MTP-ADB as well?
pumpdatbass420 said:
Step 2...am I doing this on the phone or in Odin? MTP-ADB as well?
Click to expand...
Click to collapse
step 2 is open dialer on the phone - how else you going to press ##3424#
i thought that was a given sorry
It's cool, I ask just in case. While I do consider myself a bright individual, I do not know very much about newer cell phones or android (this is only my 2nd smart phone, before the Photon I had been using my Blackjack without net. That phone lasted forever!) And before the Photon had never modded any cell phone in any way save an extended battery.
pumpdatbass420 said:
It's cool, I ask just in case. While I do consider myself a bright individual, I do not know very much about newer cell phones or android (this is only my 2nd smart phone, before the Photon I had been using my Blackjack without net. That phone lasted forever!) And before the Photon had never modded any cell phone in any way save an extended battery.
Click to expand...
Click to collapse
no problem better be safe than sorry ')
let us know how it went.
It's aliiiiiiive
Ok so oddly enough, after I performed steps 1 & 2, when I rebooted my phone I notice SuperSU was in my apps list. So for $#*^$ and giggles I downloaded Root checker to test it out and sure enough it says device is rooted. Go figure.
Thanks so much for your help guys, my girlfriend was starting to worry about me out here smashing keys and grunting like an animal trying to get this to work. :highfive:
pumpdatbass420 said:
Hello everyone! My names Danny, sorry I'm extremely frustrated at the moment and apologize for not introducing myself properly in what ever you call your newcomer section here, but I'm ripping my hair out at the moment.
So last night for the 4th time I tried to root my Galaxy S4, again unsuccessfully. While I admit I am no programmer, computer whiz, or rocket scientist, I have previously rooted my old S3 and my girlfriend's Moto Photon successfully in the past, on the 1st try (although they were pretty simple 1 click roots no more difficult than the one I used here, or so I thought.) Now last night I tried to use the CF-Autoroot again for the 3rd time, which i figured after the first 2 attempts was doomed to failure also. This may be due to the fact that I updated it, but I don't know. I'm hoping someone here can point me in the direction of a root that will work with my phone, show me where I may have went wrong in the install,or give some instruction on how to delete the update so I can use the CF-Autoroot. As long as my phone will still function as normal, I could care less which option is used, however I do not have any programming experience whatsoever, so a simpler root would be excellent. I'll give you all the info I can below.
Software version: L720VPUAMF9
Hardware version: L720.08
Model #: SPH-L720
Android version: 4.2.2
Baseband version: L720PUAMF9
Kernal version: 3.4.0-953334
[email protected] # 1
Tue Jun 25 09:36:29 KST 2013
Build #: JDQ39.L720VPUAMF9
SE Linux Status: Permissive
Secure boot status: Type: Samsung
Device Status: Custom (No Triangle Away quite yet, as I'm not sure if it is yet supported on the S4, or if I even need it since I plan on keeping the phone)
Root was done on HP Windows 7 laptop 64-bit, with the phone in camera mode prior to turning off and going into download mode.
I followed the instructions on honai-android.blogspot(dotcom) using CF-Autoroot and Odin V3.07 to the T, except I have yet to get the drivers to install correctly (or so it tells me, everything works fine,) and in Step 4 it says the box should turn yellow and a port number displays, but in my case did not. It did display the "Added" message in the little box like it should have, but it did go through the whole process and I got a PASS notification as it says I should have. I have no idea why it won't work, other than maybe the drivers are screwing me. Ran Root Checker and it tells me "Please wait for Root Check to complete. System appears to be running very slow," and Titanium Backup won't work either. Root checker stayed like this all night last night while I slept.
Also I would appreciate some help reverting it back from the root I apparently didn't install, although I know some of it went through, or Root Checker would just say I didn't have superuser access.
I'm hoping one of you guys here might be able to help me out with this problem, and I greatly appreciate any help I can get. If anymore information is needed, just ask. Much thanks in advance.
Click to expand...
Click to collapse
try doomlord easy root
Thanks for the tip but I already got it rooted. Just took a few more steps than I thought due to some overlooked details with the initial install.
New problem!
Trying to get QBKings Native Hotspot mod to work and it wont let me transfer services.odex to the system folder but services.jar is transferring fine? Any ideas? I'm baffled here yet again. Tried 3 different root browsers but JUST services.odex wont transfer!!!!!
Sorry for joining late, but how are you transferring the file? ADB, SD?
Greetings XDA Members,
I am seeing alot of people repeating this same question again and again like "Hey, I have messed up I flashed this and this and now I want to get all setup to take the official Lollipop OTA of MOTO X, Please help" the same question over and over again in several other threads so I thought it might be a good idea to sum up everything in one thread and make this easier for other members to point any person having issue like these to this thread. Now keep in mind that I am not a professional developer, Im just here to tell the basics of flashing a stock firmware, IF I make any mistake please let me know and also this thread will be a long briefly explained one so please read carefully and consider everything before applying anything.
To start off, the point of this thread is to help our new members of XDA to have an idea of what to do and how to do, Now the main topic of this thread is to point our newbie fellows on how to flash a stock firmware on a messed up MOTO X (Any Model), By messed up I mean: Either the user corrupted or damaged or somehow got stuck between anything like bootloops,not getting signals,phone not working properly and all sorts of basic software problems. If you are having such problems with your phone and want to get back to the newly fresh Moto X like when you bought it, it was shiny and all the software was fresh etc And also you want to get all setup to receive the Lollipop OTA.. you are at the right place mate. Keep reading.
Have a look at this thread also for more useful information about getting ready to take the OTA its for the kitkat ota but still its all the same so this could be very useful! by @KidJoe http://forum.xda-developers.com/moto-x/general/faq-kit-kat-how-to-prepare-carriers-t2536735
or If you have an unlocked bootloader and are rooted, and the only change you did to your phone was replacing recovery to root.. Here is another option to flash Stock Recovery back on your phone to get ready to install the latest OTA -> http://forum.xda-developers.com/moto...ooted-t3027079 credits goes to @KidJoe .
PRECAUTIONS (A MUST READ BEFORE PROCEEDING ANY FURTHER)
I am not responsible if anything happens to your device during this process because I am just explaining here what to do I wont be the one who is applying the instructions on any phone so in no matter or aspect I am the responsible for damage caused to your device. So again do this on your own risk. I wont be responsible for any damage to your phone.
1: NEVER DOWNGRAED FIRMWARE/BOOTLOADER VERSION!
Okay so you want to downgrade to get the advantages of the previous android version of your phone. THE ANSWER IS A BIG NO! if you try to downgrade your phone and mess up with motoboot.img or gpt.bin you will get a hard brick! Never try to downgrade! Refer to this thread http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202 by @KidJoe to know all the facts about downgrading.
2: Downlaod the exact and correct firmrware, before flashing
Flashing another carriers rom on your phone would be a stupidity. MAKE yourself 100% sure that you have downloaded the correct/exact firmware of your phone, never flash some random firmware on your particular moto x. Flashing another carriers rom would give you a hard brick probably.. Never play with different firmwares. (I will be mentioning further in the thread, how to make sure to download the correct firmware.)
3:You must consider of having an Unlocked Bootloader before proceeding any further, Or if you have a locked bootloader this method might work on the locked bootloaders also but, again flashing different carriers firmware on a locked bootloader device will get you more screwed up
This method should also work for the locked bootloaders but be 100% sure that you are flashing the correct signed firmware of your specific carrier. As for the Bootloader Unlock, There are not much of options for now, You can unlock your bootloader either from the motorola official site or use sunshine unlocker to unlock your bootloader. Refer to this thread : http://forum.xda-developers.com/moto-x/general/request-help-exploit-moto-x-bl-t2828471 by @samwathegreat to have an idea about the sunshine unlocking method.
Also refer to this also for info about gaining root and unlocking bootloader http://forum.xda-developers.com/moto-x/general/one-stop-shop-how-root-moto-x-confusion-t2826159 by @KidJoe.
4:You messed up your stock rom and freezed some apps
If you have rooted, put xposed etc. Dont plan to revert back by restoring the freezed apps and Instead just flash the stock firmware from RSD. Restoring back freezed apps etc will cause more problems. But make sure you uninstall all of the frameworks of xposed before proceeding to flash stock firmware.
5:This method will wipe your data completely
As the Title says this method will obviously wipe every single piece of your personal data stored on this phone such as pictures,contacts,videos and pretty much everything. So be sure to backup your data on your pc or anywhere.
Grab Your Phones Its time to start the process. Make sure its charged more than 60%.
Okay enough theory, lets get this over with.
Download and install motorola drivers : https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481 and restart you computer and proceed.
STEP 1: Identifying the correct name or model number of your Moto X
1: If the original motorola back cover is on the phone, there is some very fine/small print at the bottom of the back. It will have the FCC ID, Model number, etc. It could be hard to see, So you might have to tilt/twist the phone so the light shines off it just right and the model no appears. The Model No of your MOTO X should start with XT. Make a note of that. (credits goes to @KidJoe for explaining this in detail.)
2:Another way to find the model is by checking the Settings>About Phone of your X.
3:More ways to find out your model no, Connect the phone with the pc and see what does it shows on the pc when connected on USB MASS STORAGE. It should mention the XT10xx (Model name) of your phone on pc
NOTE:BEFORE you flash away from Stock, on the phone you first go App Drawer -> Settings -> About Phone... Make note of what is listed under System Version, Android Version, and build number. Then visit one (or all) of the sites until that host the leaked SBF files until you find the SBF that matches and down load the file to your PC for use later.. The file name will usually contain parts or all of that info listed under settings, and possibly the carrier name, or acronym for the carrier name (Verizon might be VZW, Rogers Canada might be RCI, etc).
So for example: If your phone model is XT1058 and under about phone it reports...
android version is 4.4.4
system version is 212.44.26. ghost_row.RCI.en.ca
build nunber is KXA21.12-L1.26
That tells me you have a Rogers Canada (RCI) XT1058 with 4.4.4 ROM on it. When you look at the file factory site for your SBF, you want to look for a file that contains some/all of that info, like... XT1058_RCI-CA_4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF.xml.zip
(notice the parts of the "about phone" info and file name which are highlighted in Bold to help illustrate the example)
IF you are already running a CUSTOM or 3Rd party rom, like CM, system version and build number will not match STOCK Moto SBF files. credits goes to @KidJoe for adding this additional info about figuring out what ROM is on your phone.
STEP 2: Identifying and downloading the correct firmware for your model of X
1:So now that you have identified, your Moto X is XT10xx, Now you will be downloading the correct firmware of your phone which should match the System/Build Version of your phone.
For Example: If your phone is from Rogers,ATT,Sprint,T-Mobile,US-CELLULAR,Europe etc. IT should be mentioned in the Settings>About Phone section below build version. Make a note of the whole build version/system version on a piece of paper or anything you like. Because the system/build version is the main key to have the proper knowledge about your phone before flashing any firmware.
Additional Info about bootloaders according to android version(This will give an idea about bootloaders, read it carefully and match the version of you bootloader in order with this dont downgrade):
(Android Version: Bootloader)
4.2.2: 30.70
4.2.2/camera patch OTA: 30.71
4.4: 30.B2
4.4.2: 30.B4
4.4.4: 30.B7
2:Now this part must get hard for the newbie guys but I will try my best to keep everything clear and easy. All The firmwares you need for your X is available at this site: http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=100&page=1
Now start by searching the model no and system version of your moto x. For example: if your phone is from Rogers Canada it must have "XT1058 RCI_CA " in it.. XT1058:Model Name Rci: Rogers CA: Canada. You get this right? on the firmware there should be mentioned a little bit hint or info you need to identify your firmware. Go ahead and download it. Again for the newbie guys I cant explain much easier than i've explained above, Still if you cannot find the correct firmware let me know I will try to find it out. But please first try your best from your own side first, I cant spoonfeed you [emoji14] . ATTENTION: Please download the 4.4.4 Version of your carrier because it will be easy to receive the 5.1 OTA on a 4.4.4 rom.
STEP 3: Getting ready to flash through RSD LITENote: I wont be explaining a method to flash through fastboot as from my opinion I dont like fastboot it can cause you a serious problem if you type anything wrong. If you want to try the fastboot method there is also another similar guide on how to flash through fastboot refer to this thread http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515 by @TechSavvy2
1: Download RSD LITE 6.1.5 (RSD LITE SETUP IS ATTACHED download from there) and install it in your PC Windows. (I dont have a mac dont know anything about mac.)
2:Make a new folder and unzip the firmware zip file in that new folder
3: Open the XML FILE and edit the .XML file and remove any lines with "getvar" written in them, Remove that whole line which has "getvar" in it, and (CTRL+S) save that edited file.
3: RUN RSD LITE IN ADMINISTRATIVE RIGHTS on rsd lite right click and run as administrator, IF you dont run as administrator rsd lite wont flash anything.
4: Now on rsd lite press the three dotted "..." button and select the XML File from the "new folder" you made moments ago.
STEP 4: Getting your phone in fastboot mode
If you are totally fine and running your software normally: Power off your phone, wait for 5 seconds then press and hold the power/lock button and volume down button simultaneously for 5 seconds, then release those buttons after 5 seconds. You will be in the fastboot mode of your phone now plugin your phone on usb cable of your computer make sure the bootloader says "USB CONNECTED." If it doesnt shows usb connected sign, Change the usb cable or try another usb slot.
For the people who have damaged and corrupted the software and having black screens stuck and nothing else or either they did something naive and somehow cant get in the fastboot mode: Hook up your phone to an A/C Charger and wait for about 30mins to atleast recharge it. Then remove your phone from charger and dont press the power button! Do this: Press and hold the power/lock button and volume down button simultaneously for 5 seconds, then release those buttons after 5 seconds,If you are not properly bricked you will be on the fastboot now probably, now plugin your phone on usb cable of your computer make sure the bootloader says "USB CONNECTED." If it doesnt shows usb connected sign, Change the usb cable or try another usb slot.
For the people stuck on bootloop after flashing a 3rd party custom rom or stuck on the motorola logo etc. Do this: Press and hold the Power/lock button, Volume Up Button and Volume Down button, all the three buttons simultaneously for about 15 seconds, when the screen turns off, Quickly press the Power button and volume down button repeatedly (this time dont press and hold! Press both buttons repeatedly!) You will be on the fastboot mode of your phone plugin the phone on usb port and your bootloader should say "USB CONNECTED" AFAIK. If you are not bricked!
STEP 5:Flashing the firmware
On Rsd lite, make sure that your device is showing "Connected" Now, Press the start button on the rsd lite and wait for about maximum 30-40Mins to get your firmware flashed in the phone successfully. ATTENSION: Dont touch or power off your phone or computer during the flashing process untill or unless your device reboots and comes to its homescreen on the factory settings, make sure the usb cable is connected properly not loose. If you mess up anything during flashing process you are risking your whole phone so do this when you are calm enough.
Flashing Process Done Now You Are All Set Up To Receive The Latest OTA OF 5.1!
For the people who have flashed the 5.1 soak test/leak and are stuck at some certain point
So you couldn't wait and flashed the LEAKED test/soak versions of 5.02 and 5.1 and your bootloader is upgraded to 30.BC or 30.BD you are stuck on a bootloop and cant get your phone to work ----> There is nothing you could really do to save your self till now only one thing you can do is wait! DO NOT DOWNGRADE YOUR BOOTLOADER/FIRMWARE as that will risk bricking, but rather WAIT and hope a 5.1 SBF for their model/carrier leaks in the coming weeks/months, then fully flash it to return to stock. credits goes to @KidJoe for adding this info.
Good luck mates!
Thats all I can sum up in one thread, I hope this helps the new people. Peace Out.
whizinc said:
Greetings XDA Members,
I am seeing alot of people repeating this same question again and again like "Hey, I have messed up I flashed this and this and now I want to get all setup to take the official Lollipop OTA of MOTO X, Please help" the same question over and over again in several other threads so I though it might be a good idea to sum up everything in one thread and make this easier for other members to point any person having issue like these to this thread. Now keep in mind that I am not a professional developer, Im just here to tell the basics of flashing a stock firmware, IF I make any mistake please let me know and also this thread will be a long briefly explained one so please read carefully and consider everything before applying anything.
To start off, the point of this thread is to help our new members of XDA to have an idea of what to do and how to do, Now the main topic of this thread is to point our newbie fellows on how to flash a stock firmware on a messed up MOTO X (Any Model), By messed up I mean: Either the user corrupted or damaged or somehow got stuck between anything like bootloops,not getting signals,phone not working properly and all sorts of basic software problems. If you are having such problems with your phone and want to get back to the newly fresh Moto X like when you bought it, it was shiny and all the software was fresh etc And also you want to get all setup to receive the Lollipop OTA.. you are at the right place mate. Keep reading.
Have a look at this thread also for more useful information about getting ready to take the OTA its for the kitkat ota but still its all the same so this could be very useful! by @KidJoe http://forum.xda-developers.com/moto-x/general/faq-kit-kat-how-to-prepare-carriers-t2536735
PRECAUTIONS (A MUST READ BEFORE PROCEEDING ANY FURTHER)
I am not responsible if anything happens to your device during this process because I am just explaining here what to do I wont be the one who is applying the instructions on any phone so in no matter or aspect I am the responsible for damage caused to your device. So again do this on your own risk. I wont be responsible for any damage to your phone.
1: NEVER DOWNGRAED FIRMWARE/BOOTLOADER VERSION!
Okay so you want to downgrade to get the advantages of the previous android version of your phone. THE ANSWER IS A BIG NO! if you try to downgrade your phone and mess up with motoboot.img or gpt.bin you will get a hard brick! Never try to downgrade! Refer to this thread http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202 by @KidJoe to know all the facts about downgrading.
2: Downlaod the exact and correct firmrware, before flashing
Flashing another carriers rom on your phone would be a stupidity. MAKE yourself 100% sure that you have downloaded the correct/exact firmware of your phone, never flash some random firmware on your particular moto x. Flashing another carriers rom would give you a hard brick probably.. Never play with different firmwares. (I will be mentioning further in the thread, how to make sure to download the correct firmware.)
3:You must consider of having an Unlocked Bootloader before proceeding any further
There are not much of options for now, You can unlock your bootloader either from the motorola official site or use sunshine unlocker to unlock your bootloader. Refer to this thread : http://forum.xda-developers.com/moto-x/general/request-help-exploit-moto-x-bl-t2828471 by @samwathegreat to have an idea about the sunshine unlocking method.
Also refer to this also for info about gaining root and unlocking bootloader http://forum.xda-developers.com/moto-x/general/one-stop-shop-how-root-moto-x-confusion-t2826159 by @KidJoe.
3:You messed up your stock rom and freezed some apps
If you have rooted, put xposed etc. Dont plan to revert back by restoring the freezed apps and Instead just flash the stock firmware from RSD. Restoring back apps freezed etc will cause more problems. But make sure you uninstall all of the frameworks of xposed before proceeding to flash stock firmware.
Grab Your Phones Its time to start the process. Make sure its charged more than 60%.
Okay enough theory, lets get this over with.
Download and install motorola drivers : https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481 and restart you computer and proceed.
STEP 1: Identifying the correct name or model number of your Moto X
1: If the original motorola back cover is on the phone, there is some very fine/small print at the bottom of the back. It will have the FCC ID, Model number, etc. It could be hard to see, So you might have to tilt/twist the phone so the light shines off it just right and the model no appears. The Model No of your MOTO X should start with XT. Make a note of that. (credits goes to @KidJoe for explaining this in detail.)
2:Another way to find the model is by checking the Settings>About Phone of your X.
3:More ways to find out your model no, Connect the phone with the pc and see what does it shows on the pc when connected on USB MASS STORAGE. It should mention the XT10xx (Model name) of your phone on pc
STEP 2: Identifying and downloading the correct firmware for your model of X
1:So now that you have identified, your Moto X is XT10xx, Now you will be downloading the correct firmware of your phone which should match the System/Build Version of your phone.
For Example: If your phone is from Rogers,ATT,Sprint,T-Mobile,US-CELLULAR,Europe etc. IT should be mentioned in the Settings>About Phone section below build version. Make a note of the whole build version/system version on a piece of paper or anything you like. Because the system/build version is the main key to have the proper knowledge about your phone before flashing any firmware.
Additional Info about bootloaders according to android version(This will give an idea about bootloaders, read it carefully and match the version of you bootloader in order with this dont downgrade):
(Android Version: Bootloader)
4.2.2: 30.70
4.2.2/camera patch OTA: 30.71
4.4: 30.B2
4.4.2: 30.B4
4.4.4: 30.B7
2:Now this part must get hard for the newbie guys but I will try my best to keep everything clear and easy. All The firmwares you need for your X is available at this site: http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=100&page=1
Now start by searching the model no and system version of your moto x. For example: if your phone is from Rogers Canada it must have "XT1058 RCI_CA " in it.. XT1058:Model Name Rci: Rogers CA: Canada. You get this right? on the firmware there should be mentioned a little bit hint or info you need to identify your firmware. Go ahead and download it. Again for the newbie guys I cant explain much easier than i've explained above, Still if you cannot find the correct firmware let me know I will try to find it out. But please first try your best from your own side first, I cant spoonfeed you [emoji14] . ATTENTION: Please download the 4.4.4 Version of your carrier because it will be easy to receive the 5.1 OTA on a 4.4.4 rom.
STEP 3: Getting ready to flash through RSD LITENote: I wont be explaining a method to flash through fastboot as from my opinion I dont like fastboot it can cause you a serious problem if you type anything wrong. If you want to try the fastboot method there is also another similar guide on how to flash through fastboot refer to this thread http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515 by @TechSavvy2
1: Download RSD LITE 6.1.5 (RSD LITE SETUP IS ATTACHED download from there) and install it in your PC Windows. (I dont have a mac dont know anything about mac.)
2:Make a new folder and unzip the firmware zip file in that new folder
3: Open the XML FILE and edit the .XML file and remove any lines with "getvar" written in them, Remove that whole line which has "getvar" in it, and (CTRL+S) save that edited file.
3: RUN RSD LITE IN ADMINISTRATIVE RIGHTS on rsd lite right click and run as administrator, IF you dont run as administrator rsd lite wont flash anything.
4: Now on rsd lite press the three dotted "..." button and select the XML File from the "new folder" you made moments ago.
STEP 4: Getting your phone in fastboot mode
If you are totally fine and running your software normally: Power off your phone, wait for 5 seconds then press and hold the power/lock button and volume down button simultaneously for 5 seconds, then release those buttons after 5 seconds. You will be in the fastboot mode of your phone now plugin your phone on usb cable of your computer make sure the bootloader says "USB CONNECTED." If it doesnt shows usb connected sign, Change the usb cable or try another usb slot.
For the people who have damaged and corrupted the software and having black screens stuck and nothing else or either they did something naive and somehow cant get in the fastboot mode: Hook up your phone to an A/C Charger and wait for about 30mins to atleast recharge it. Then remove your phone from charger and dont press the power button! Do this: Press and hold the power/lock button and volume down button simultaneously for 5 seconds, then release those buttons after 5 seconds,If you are not properly bricked you will be on the fastboot now probably, now plugin your phone on usb cable of your computer make sure the bootloader says "USB CONNECTED." If it doesnt shows usb connected sign, Change the usb cable or try another usb slot.
For the people stuck on bootloop after flashing a 3rd party custom rom or stuck on the motorola logo etc. Do this: Press and hold the Power/lock button, Volume Up Button and Volume Down button, all the three buttons simultaneously for about 15 seconds, when the screen turns off, Quickly press the Power button and volume down button repeatedly (this time dont press and hold! Press both buttons repeatedly!) You will be on the fastboot mode of your phone plugin the phone on usb port and your bootloader should say "USB CONNECTED" AFAIK. If you are not bricked!
STEP 5:Flashing the firmware
On Rsd lite, make sure that your device is showing "Connected" Now, Press the start button on the rsd lite and wait for about maximum 30-40Mins to get your firmware flashed in the phone successfully. ATTENSION: Dont touch or power off your phone or computer during the flashing process untill or unless your device reboots and comes to its homescreen on the factory settings, make sure the usb cable is connected properly not loose. If you mess up anything during flashing process you are risking your whole phone so do this when you are calm enough.
Flashing Process Done Now You Are All Set Up To Receive The Latest OTA OF 5.1!
Note: Currently please dont and I repeat DONT flash any soak test or any 5.1 leaked release of stock rom. All you will be getting by doing this would be A messed up bootloader,motoboot,gpt etc. Dont be so impatient just wait for the ota to show up on your phone!
Good luck mates!
Thats all I can sum up in one thread, I hope this helps the new people. Peace Out.
Click to expand...
Click to collapse
That's exactly what I did last night to make sure that I can get the OTA of Lollipop 5.1 when it finally comes out. I have a feeling that it will be rolling out here pretty soon.
Mod Edit : HIDE tags added by @Darth ... No need to quote long Opening posts, or use hide tags if you must. Thanks!
cindylike24 said:
That's exactly what I did last night to make sure that I can get the OTA of Lollipop 5.1 when it finally comes out. I have a feeling that it will be rolling out here pretty soon.
Click to expand...
Click to collapse
Yeah its already rolling out in some areas of US.. Good luck
Sent from my ghost using Tapatalk
whizinc said:
Yeah its already rolling out in some areas of US.. Good luck
Sent from my ghost using Tapatalk
Click to expand...
Click to collapse
Not in my area yet.
Cindy
cindylike24 said:
Not in my area yet.
Cindy
Click to expand...
Click to collapse
Not across the river, either! *Waves from Illinois*
hbar98 said:
Not across the river, either! *Waves from Illinois*
Click to expand...
Click to collapse
Where are you from? I'm from Vincennes, Indiana.
Sent from my Samsung Galaxy Tab 4 8" model using Tapatalk
cindylike24 said:
Where are you from? I'm from Vincennes, Indiana.
Sent from my Samsung Galaxy Tab 4 8" model using Tapatalk
Click to expand...
Click to collapse
Now I live around Fairfiled, IL, but I grew up in Keensburg and Mt. Carmel.
hbar98 said:
Now I live around Fairfiled, IL, but I grew up in Keensburg and Mt. Carmel.
Click to expand...
Click to collapse
Cool! Small world, isn't it?!
Sent from my Samsung Galaxy Tab 4 8" model using Tapatalk
cindylike24 said:
Cool! Small world, isn't it?!
Sent from my Samsung Galaxy Tab 4 8" model using Tapatalk
Click to expand...
Click to collapse
Yep! I don't think that 5.1 is rolling out in the states yet... you'd think that whichever carrier rolled it out first would make some noise about it. I'll be ready, though! I really like 5.1.1 on my 2013 Nexus 7.
If you have an unlocked bootloader and are rooted, and the only change you did to your phone was replacing recovery to root.. Here is another option to flash Stock Recovery back on your phone -> http://forum.xda-developers.com/moto-x/general/ref-return-to-stock-recovery-rooted-t3027079
----
@whizinc , Something else to add to the OP on figuring out what ROM is on your phone...
Normally I would suggest BEFORE you flash away from Stock, on the phone you first go App Drawer -> Settings -> About Phone... Make note of what is listed under System Version, Android Version, and build number. Then visit one (or all) of the sites until that host the leaked SBF files until you find the SBF that matches and down load the file to your PC for use later.. The file name will usually contain parts or all of that info listed under settings, and possibly the carrier name, or acronym for the carrier name (Verizon might be VZW, Rogers Canada might be RCI, etc).
So for example: If your phone model is XT1058 and under about phone it reports...
android version is 4.4.4
system version is 212.44.26. ghost_row.RCI.en.ca
build nunber is KXA21.12-L1.26
That tells me you have a Rogers Canada (RCI) XT1058 with 4.4.4 ROM on it. When you look at the file factory site for your SBF, you want to look for a file that contains some/all of that info, like... XT1058_RCI-CA_4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF.xml.zip
(notice the parts of the "about phone" info and file name which are highlighted in Bold to help illustrate the example)
IF you are already running a CUSTOM or 3Rd party rom, like CM, system version and build number will not match STOCK Moto SBF files.
-------
You also might want to add info for those who couldn't wait, and flashed the LEAKED test/soak versions of 5.02 and 5.1 that now have bootloader 30.BC or 30.BD... as they will NOT want to downgrade to 4.4.4 as that will risk bricking, but rather WAIT and hope a 5.1 SBF for their model/carrier leaks in the coming weeks/months, then fully flash it to return to stock.
KidJoe said:
If you have an unlocked bootloader and are rooted, and the only change you did to your phone was replacing recovery to root.. Here is another option to flash Stock Recovery back on your phone -> http://forum.xda-developers.com/moto-x/general/ref-return-to-stock-recovery-rooted-t3027079
----
@whizinc , Something else to add to the OP on figuring out what ROM is on your phone...
Normally I would suggest BEFORE you flash away from Stock, on the phone you first go App Drawer -> Settings -> About Phone... Make note of what is listed under System Version, Android Version, and build number. Then visit one (or all) of the sites until that host the leaked SBF files until you find the SBF that matches and down load the file to your PC for use later.. The file name will usually contain parts or all of that info listed under settings, and possibly the carrier name, or acronym for the carrier name (Verizon might be VZW, Rogers Canada might be RCI, etc).
So for example: If your phone model is XT1058 and under about phone it reports...
android version is 4.4.4
system version is 212.44.26. ghost_row.RCI.en.ca
build nunber is KXA21.12-L1.26
That tells me you have a Rogers Canada (RCI) XT1058 with 4.4.4 ROM on it. When you look at the file factory site for your SBF, you want to look for a file that contains some/all of that info, like... XT1058_RCI-CA_4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF.xml.zip
(notice the parts of the "about phone" info and file name which are highlighted in Bold to help illustrate the example)
IF you are already running a CUSTOM or 3Rd party rom, like CM, system version and build number will not match STOCK Moto SBF files.
-------
You also might want to add info for those who couldn't wait, and flashed the LEAKED test/soak versions of 5.02 and 5.1 that now have bootloader 30.BC or 30.BD... as they will NOT want to downgrade to 4.4.4 as that will risk bricking, but rather WAIT and hope a 5.1 SBF for their model/carrier leaks in the coming weeks/months, then fully flash it to return to stock.
Click to expand...
Click to collapse
All the information that you suggested has been added to the OP. Thank you! :good:
https://docs.google.com/open?id=0B5XNxZ2OcfKtdDROTk5kb21ObU0 for asia retail only XT1052_RETAIL-ASIA_4.4.4_KXA21.12-L1.26_18_cid7_CFC_1FF.xml.zip
miju12 said:
https://docs.google.com/open?id=0B5XNxZ2OcfKtdDROTk5kb21ObU0 for asia retail only XT1052_RETAIL-ASIA_4.4.4_KXA21.12-L1.26_18_cid7_CFC_1FF.xml.zip
Click to expand...
Click to collapse
what do you mean by this?
Sent from my ghost using Tapatalk
whizinc said:
what do you mean by this?
Sent from my ghost using Tapatalk
Click to expand...
Click to collapse
factory image for XT1052. if you download from the file factory site it takes a lot of time.
miju12 said:
factory image for XT1052. if you download from the file factory site it takes a lot of time.
Click to expand...
Click to collapse
file factory is the only site present and online for now which has all the firmwares in it... So that's why i preferred it, ignoring the problem of the download speeds...
Sent from my ghost using Tapatalk
whizinc said:
file factory is the only site present and online for now which has all the firmwares in it... So that's why i preferred it, ignoring the problem of the download speeds...
Sent from my ghost using Tapatalk
Click to expand...
Click to collapse
yeah i know. if someone uploads the file to some other cloud like drive, won't it be easy to others to download? i have posted the link because if someone needs the asia retail factory image, it would be easy and fast to download from this link. and for others the file factory website is there. and the problem from downloading file from file factory is it can't be resume so if there is a network error you have to download the file from begining.
miju12 said:
yeah i know. if someone uploads the file to some other cloud like drive, won't it be easy to others to download? i have posted the link because if someone needs the asia retail factory image, it would be easy and fast to download from this link. and for others the file factory website is there. and the problem from downloading file from file factory is it can't be resume so if there is a network error you have to download the file from begining.
Click to expand...
Click to collapse
I agree with you, But i dont think someone will do that because its not easy to upload such big files on a private drive like clouds etc...
Sent from my ghost using Tapatalk
Do you know the file name for the Verizon Dev Edition?
whizinc said:
I agree with you, But i dont think someone will do that because its not easy to upload such big files on a private drive like clouds etc...
Sent from my ghost using Tapatalk
Click to expand...
Click to collapse
yeah its a pain to upload such big file. but the link i posted someone have uploaded file so its easy for XT1052 asia retail users to download
---------- Post added at 05:24 PM ---------- Previous post was at 05:16 PM ----------
mbush78 said:
Do you know the file name for the Verizon Dev Edition?
Click to expand...
Click to collapse
check this link for the file as it was uploaded in google drive. before flashing confirm it is for your model with the dev http://forum.xda-developers.com/moto-x/development/vzw-4-4-kitkat-fastboot-factory-image-t2537398
check this page of motorola https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
mbush78 said:
Do you know the file name for the Verizon Dev Edition?
Click to expand...
Click to collapse
Follow the link @miju12 suggested that would be the firmware for verizon dev edition... and dont execute the oem lock command... It will relock your bootloader if you have it unlocked.
Sent from my ghost using Tapatalk
Update March 8 2017: As you can probably tell, this is very old. I have not worked on the device in several months and I have no idea if these methods are still safe. Please proceed with caution. I will be using one of these on a daily basis in the near future, so I probably will get back into development, and hope to release new content for the phone to help out the community. Please accept this as an official warning that the following is probably out of date and that you should be very careful should you decide to try it. The original post in it's entirety is spoilered below. You have been warned.
Update: A new update was released for the Prime model, V6.6, which replaces the preloader and completely breaks SPFT. If you unlocked your bootloader (so you can use fastboot) in any capacity before taking that update, there may be hope for you yet, but as of right now V6.6 is unsupported. Update: If you used this method to safely* take* the V6.6* update*, this will still work.
Update: I just checked the stats, and this has been downloaded more than 3 thousand times. I never thought my humble little conversion guide would help out so many people. I have also added a new mirror at [REDACTED], so anyone in North America who was having trouble with the Europe mirror, give that one a shot. It should be faster! I have updated all links in the guide to use the new North America mirror, and added a separate Europe mirror link after each link.
Hello! This is a tutorial for converting the Amazon Prime Edition BLU R1 HD to the OEM BLU version. This will overwrite the relevant partitions on your Amazon version of the device with the non-Amazon version. The physical model number on your device will still be a tell (obviously), but besides that, there will be no way to tell your device apart from the regular model! You can also use this method to convert non-Prime to Prime version, and undo OTAs or system modifications. This will restore a 100% out of the box image from either edition on your device.
This will work if you have software version...
V12
V6.1
V6.4
V6.5
SAFE V6.6 FROM THIS THREAD
This will NOT work on software version...
V6.6
The V6.6 update brought a new preloader that breaks our ability to use SPFT. I am currently working on ways to reverse the damage, but as of right now, there is no way to convert (or downgrade) from software V6.6
You can use this on any 16/2 R1 HD with supported software version to...
Convert to the non-Prime OEM version
Convert to the Prime version
Remove ads (via conversion to non-Prime version)
Unroot
Downgrade to V6.1
Downgrade to V12
Undo system alterations/tampers
Restore the system image to the way it was when you first opened the box
Unbrick a device (if bricked because of bad system/recovery/boot image)
There are a handful of reports about this working flawlessly on the 8/1 model as well. I have not personally tested this, so there is still some risk factor.
This only overwrites the system, recovery, and boot partitions. Any other partitions that have been altered will not be restored. In most cases, other partitions should not have been altered, so this is not a concern. I have a full system backup of all partitions, but there is currently evidence to suggest that it is not safe to flash all of the partitions, so I will not release that backup until more is known.
You *should* be able to safely pull this off without wiping your data. This does not require your phone to be rooted or have any other modifications. You can pull it straight out of the box and do this process! If your phone is rooted, you'll lose it. This will make your phone EXACTLY like the non-Prime version comes out of the box! You can also convert a non-Prime device (or a converted Prime device back) to a Prime device using the same method, but I'm not exactly sure why you would want to. I did this all on Linux, but the Windows should work fine too as long as you have drivers dealt with. If you don't have drivers dealt with, I'm not your guy. I'll just tell you to use a better operating system. You'll also need an archive program that can deal with tar.gz files, because that's how my computer zipped them.
And the standard disclaimer: If this bricks your phone or makes it become sentient and plot with other sentient phones to murder your entire family, it's not my fault. That's all on you, buddy.
Ok, without further ado, on to the tutorial!
First, you need these things. Some of the files are quire large, so it might take a while to download:
You'll need the latest version of Smart Phone Flash Tools, or SPFT for short. You can download that from this site, or from [REDACTED]. Please use the latest version for your OS.
You'll need to download the system image. If you're converting to the non-Prime version, [REDACTED]. If you're converting to the Prime version, [REDACTED]
You need the scatter file. This will tell SPFT where the partitions are. This is the same for both variants, so just download [REDACTED]
Once you have those things, you can start actually flashing your phone:
Power your phone completely OFF! This will not work if your phone is powered on. SPFT writes directly to the phone's memory, bypassing all security measures the phone has, so it requires the phone to be completely OFF to get safe and exclusive access to the memory. DO NOT PLUG IN YOUR PHONE YET!
Extract SPFT into a folder on your computer. If you can't figure out how to do that, please stop tinkering with your phone. It's only a matter of time until you break something.
Extract the system image into the same folder you put SPFT in. The three files (boot.img, recovery.img, system.img) should be in the same folder as all the other SPFT files, including the binaries.
Run SPFT. On Windows, simply double clicking the SPFT executable should do the trick. On Linux, you must run the flash_tool.sh script as root. Open a terminal emulator, cd to the SPFT folder, and run `sudo ./flash_tool.sh`. If you recieve an error about permissions, run `chmod +x flash_tool.sh` and try the first command again.
Go to the Download tab in SPFT and click the Scatter-loading button on the far right side. DO NOT click the Download Agent button. When the file picker dialog pops up, find and open the r1hd-spft-scatter.txt file you downloaded earlier.
You should see a list of partitions. Only three of them (boot, recovery, system) should be checked, and the location should point to the files you extracted from the tar.gz file earlier. If this is not the case, double-click the location block of the boot, recovery, and system partitions, and select the boot.img, recovery.img, and system.img files from your filesystem respectively. After selecting the files, the boxes should check themselves.
From the dropdown in the upper left of the partition list, make sure Download Only is selected. Any other option could damage your device.
Click the Download button in the upper left.
While your phone is OFF, plug it into your computer with a data safe USB cable. The cable that came in the box from the factory is ideal, but any good quality cable will work just fine.
SPFT should start overwriting your phone. If you receive an error from SPFT, unplug your phone, close SPFT, and repeat steps 4 through 9. The whole process takes about 10 minutes, after which you should see a window with a large green checkmark. Once you see that window, you can safely unplug your phone and start it up. You're all done!
And as a bonus, I've also included a guide for unlocking the bootloader, getting custom recovery, and rooting the device after you've done this in post #2. That makes this your one stop shop for getting a brand new Prime phone out of the box!!
HUGE THANKS TO @mrmazak FOR THEORIZING THIS METHOD AND GETTING ME THE NON-PRIME SYSTEM IMAGE TO USE!
As always, if you have any questions, just ask in a thread reply or send me a private message on XDA. And by the way, hit the Thanks button in the lower right corner of the post if my guide helps you. It motivates me to keep this up to date and write more helpful guides. If you feel like giving me even more motivation and help fund future development, [REDACTED].
{OUTDATED}[GUIDE][OEM][Stock] Bootloader Unlock, TWRP, and root!
Update March 8 2017: As you can probably tell, this is very old. I have not worked on the device in several months and I have no idea if these methods are still safe. Please proceed with caution. I will be using one of these on a daily basis in the near future, so I probably will get back into development, and hope to release new content for the phone to help out the community. Please accept this as an official warning that the following is probably out of date and that you should be very careful should you decide to try it. The original post in it's entirety is spoilered below. You have been warned.
Ok, now you've converted your brand new Prime phone to the non-Prime version. How do you unlock this sucker? The conversion process actually unlocks the standard unlock method from the factory, so it's VERY simple! No hoops to jump through or anything. You'll need adb and fastboot. You can get those as part of the official Android developer kit, your distro's repos (on Linux) or Homebrew (on Mac). Of course, this guide works for the normal non-converted non-Prime version as well. This WILL wipe your phone, so make sure you back up any important data before doing this.
This guide is for the OEM (non-Prime) version. If you have the Prime version, convert it to OEM using the guide above BEFORE doing this guide.
The standard disclaimer from above still applies.
This guide is broken up into two parts. Unlocking the bootloader, and rooting the phone. If you are preparing to install Magisk, do the bootloader unlock, skip the rooting part and move on to the Magisk guide. You do not need the files above if you are only unlocking the bootloader. If your bootloader is already unlocked, skip the bootloader unlocking part and skip to rooting the phone. If you are preparing to install Magisk and your bootloader is already unlocked, you shouldn't be here. Also please note that the bootloader can sometimes re-lock itself after completing a conversion/restore from the guide above, especially to/from the Prime version, so if you're not sure, play it safe and re-unlock your bootloader.
Part 1 - Unlocking the bootloader:
Boot up your phone. If you haven't already gone through the initial setup process, go through it. The bootloader unlock process will wipe your phone, so skip as many questions as possible so you don't waste your time.
Open the Settings app, go to About device, fine the Build number (it's toward the bottom), and tap on it 8-10 times (until it says you are now a developer. If it says there's no need and you're already a developer, you can skip to the next step)
Go back to the main Settings menu. You should see a new option where About device used to be, Developer options! Click on it.
Toward the top of the long list of developer options, there is an option called "OEM unlocking". If it's switched off, switch it on. If it's switched on, switch it off and back on again. You may get a warning saying that device protection features won't work. Click Enable and proceed. You may also be prompted to enter your password/PIN/pattern lock if you have one.
Scroll down a little bit to reveal USB debugging. Switch it on if it's not already.
Connect your phone to your computer using a data safe cable. Do not disconnect it until the very end.
On your computer, open a terminal emulator (or Command Prompt with ADB access) and run `adb reboot bootloader`. If you get a message complaining about keys or authorization, check your phone. There should be a window asking for permission for your computer to access the device. Allow it and run the command again.
Your phone will reboot into fastboot mode.
On your computer, run `fastboot oem unlock`. On the phone you will get a warning message talking about the implications of unlocking the bootloader. Press Volume Up to accept them. If everything goes smoothly, your bootloader should now be unlocked. You're not ready to flash quite yet! Flashing at this stage WILL brick your phone, so it's important that you continue following the guide carefully.
On your computer, run `fastboot reboot`. Your phone should reboot anywhere from 3 to 5 times. If it reboots more than that, your phone is bricked and you need to start again by following the guide above again.
Once Android starts up again, you should see the setup wizard. Your bootloader is now unlocked!
Part 2 - rooting the phone:
BEFORE YOU PROCEED: If you want your phone to be encrypted AND rooted, it's important that you unlock the bootloader using the steps above first, then use the encryption APK to encrypt your phone BEFORE installing TWRP and rooting your device. This device is an exception to the general rule of flashing TWRP first and then rooting afterwards. Repeat, if you want your phone encrypted and rooted, unlock the bootloader FIRST, then encrypt SECOND, then flash TWRP THIRD, and root your phone LAST.
This is the guide for rooting the actual phone. You must unlock the bootloader using the steps above before doing this part.
First, you'll need these things on your computer.
The TWRP image for the R1 HD. You can download [REDACTED]).
A copy of the latest SuperSU zip from Chainfire. You can get it from the official forum post, or Chainfire's website.
Linux Users: On Linux, you must add `sudo` to the beginning of all fastboot commands, because most Linux distributions will not give you enough access to the hardware without being root.
And finally, the guide:
Hold Volume Up and Power until the phone turns on with the boot menu. Once the boot menu appears, use the volume keys to scroll to [Fastboot Mode] and press the power button to select it. It's the middle option.
On your computer, cd to the folder where you downloaded twrp-3.0.2-1-r1hd-lopestom.img and do `fastboot flash recovery twrp-3.0.2-1-r1hd-lopestom.img`.
On your computer, do `fastboot boot twrp-3.0.2-1-r1hd-lopestom.img`.
Once TWRP boots up, dismiss the prompt about mounting the system, go to Reboot, then choose Recovery. Your device will reboot back into TWRP. I know this step seems odd, but just trust me.
Make a backup if you want. It's not a bad idea, but seeing how you just unlocked your bootloader so your data is gone and we have the images in case you somehow brick the system, I doubt you actually need it.
In TWRP, go to Advanced, then ADB Sideload. Slide the confirmation slider all the way to the right to confirm.
On your computer, cd to the folder where you downloaded SuperSU and run `adb sideload [SuperSU-zip-name.zip]`, replacing the last argument with the name of the SuperSU zip you downloaded, of course. If your computer says "waiting for device" for a long time, cancel with Ctrl+C, run `adb kill-server`, then run the first command again but with `sudo` in front this time.
Reboot the phone. If everything worked correctly, you should now have a rooted phone with SuperSU, bootloader unlocked, and custom recovery! Yay for cheap phones!
As always, if you have any questions, just ask in a thread reply or send me a private message on XDA. And by the way, hit the Thanks button in the lower right corner of the post if my guide helps you. It motivates me to keep this up to date and write more helpful guides. If you feel like giving me even more motivation and help fund future development, [REDACTED].
reserved 3
reserved 4
reserved 5
Can you verify the image you uploaded for the non-Prime version? I'm getting unexpected EOF errors when extracting in Windows using 7Zip and TarTool, and I'm also getting an "operation not permitted" error when extracting using the built in Archive Utility in OS X.
abs0lute said:
Can you verify the image you uploaded for the non-Prime version? I'm getting unexpected EOF errors when extracting in Windows using 7Zip and TarTool, and I'm also getting an "operation not permitted" error when extracting using the built in Archive Utility in OS X.
Click to expand...
Click to collapse
Yeah, that's because the image isn't fully uploaded. My internet is very slow, so it's taking a while to upload. Sorry about that. I was hoping it would be finished by the time I finished writing this, but alas, nope. I will have all files uploaded by tomorrow, along with .md5 files so you can verify the checksums, so come back then. Again, sorry. I guess I should have posted this _after_ I got those uploaded. Oh! And I have North America mirrors coming within the next couple months. It seems a little oxy-moronic to host files for a US only device on an EU server, but unfortunately, servers in the US are significantly more expensive.
ColtonDRG said:
Yeah, that's because the image isn't fully uploaded. My internet is very slow, so it's taking a while to upload. Sorry about that. I was hoping it would be finished by the time I finished writing this, but alas, nope. I will have all files uploaded by tomorrow, along with .md5 files so you can verify the checksums, so come back then. Again, sorry. I guess I should have posted this _after_ I got those uploaded. Oh! And I have North America mirrors coming within the next couple months. It seems a little oxy-moronic to host files for a US only device on an EU server, but unfortunately, servers in the US are significantly more expensive.
Click to expand...
Click to collapse
No problem - thanks for your work on this!
abs0lute said:
No problem - thanks for your work on this!
Click to expand...
Click to collapse
Just finished uploading the non-Prime version. I will start the other upload before sleeping and update the post removing the warning when I awaken, assuming everything has gone well. You're free to attempt a non-Prime conversion now. Just don't do it the other way around yet.
Sent from my LG G4 using XDA Labs
Can't wait to give this a shot. Well, at least after someone else reports success first...
followed post 1 convert to non prime steps on windows, did not do the bootloader unlock steps.
phone booted up ok, followed by android is upgrading x of 37.
phone working and no ad's on lock screen
the amazon apps are still there but appear to be disabled, causing errors at first boot.
disabled or uninstall the apps. - used cleanmaster
everything seems ok now
Hello, I have now finished uploading the files, so you can now safely flash away! Enjoy! @abs0lute
bupkis said:
Can't wait to give this a shot. Well, at least after someone else reports success first...
Click to expand...
Click to collapse
I report success. Of course I did everything in the guide here before posting it. I'm not irresponsible. It's completely safe. I just finished uploading the files, so please go ahead and give it a shot.
ColtonDRG said:
I report success. Of course I did everything in the guide here before posting it. I'm not irresponsible. It's completely safe. I just finished uploading the files, so please go ahead and give it a shot.
Click to expand...
Click to collapse
ok, away we go! :laugh:
When I try to download the scatter file it just opens the file in a new browser window.
>nevermind, figured it out...success!
...on to bootloader unlock, TWRP, root...
bupkis said:
...
When I try to download the scatter file it just opens the file in a new browser window.
...
Click to expand...
Click to collapse
Yeah, that's a problem with my server configuration. I'll fix it later. For now, you can save the file by opening it in a browser window and pressing Ctrl+S
I have completed the process successfully-TWRP, root, no ads but do still have all the Amazon apps so something is screwy but not the end of the world.
bupkis said:
I have completed the process successfully-TWRP, root, no ads but do still have all the Amazon apps so something is screwy but not the end of the world.
Click to expand...
Click to collapse
Nope, it's not screwy. The non-Amazon version does include a lot of the Amazon apps. You can uninstall some of them the normal way (they're pre-installed user apps), and others you can either disable or uninstall using your favourite system app remover.
Anyone else missing Encrypt section in Settings > Security after converting to non-prime?
When I try to load the scatter, SPFT says "Error: Initializing scatter file failed. Please check the name of scatter file which you load is legal." I downloaded it from both the primary link and your mirror, same error. Any ideas? Thanks.
EDIT: Looks like I downloaded the oldest version, not the newest version of SPFT. Whoops! I'll leave my mistake on here to help others who may assume the first link is the right one.
notfix said:
Anyone else missing Encrypt section in Settings > Security after converting to non-prime?
Click to expand...
Click to collapse
It is missing. How peculiar. I will attempt to implement a workaround in a little bit. Sorry about that.
Update: The Encryption activity exists on the phone, we just can't get to it from the settings menu. You can launch it by manually launching com.android.settings.Settings$CryptKeeperSettingsActivity using your preferred method for launching arbitrary activities. I will release an app that will launch this activity for you ASAP!