Words of wisdom ... or warning!
By following this guide, you are agreeing that neither I nor anyone else apart from yourself is responsible for any damage, loss of earnings, fire, theft, the milk not being delivered or bricking your device - you are doing the modding so you are to blame if anything goes wrong!
I will credit the original authors of all the files I have included in my guide as best as I can, if I have missed you out then I do apologise.
With thanks to: kennethpenn, SamCripp, Stevendeb25, eval-, Edgan, Mossys, papy-polo, the2dcour, plus anyone that I have missed.
Note: I have linked file downloads from the guides I used when I rooted, unlocked and flashed my device. I will included a link to the thread so if the links are broken then you should look in the threads for updated links - also just let me know and I'll try to fix them.
Right on with the guide...
Rooting:
Downloads:
- Atrix drivers - Download: 32-bit | 64-bit
- Gingerbreak - Download
Instructions:
1. Install drivers
2. Run gingerbreak.exe
3. Give the phone a minute or two and then open the app drawer to find "Gingerbreak"
4. Run gingerbreak from your phone
5. Click 'root now'
6. Wait for your phone to reboot
Whayy! Your now rooted - If all went well.
Tegrapart?.. You need this to flash the correct boot.img later on.
Downloads:
Terminal emulator - Download from market
Instructions:
1. Download and run 'Terminal emulator'
2. Enter:
Code:
su
- you may be prompted to by SuperUser, press remember and then press 'Allow'
3. Now enter:
Code:
cat /proc/cmdline
4.a. That command will return quite a large string of text, scan through it untill you find something that starts something like this: 'tegrapart=mbr:'
4.b. If you see tegrapart=mbr:d00:100:800,kpanic:2100:400:800: then just remember that your device is d00
4.c. If you see tegrapart=mbr:1100:100:800,kpanic:2500:400:800: then you need to remember that your device is 1100
Unlocking the bootloader:
Downloads:
- RSD Lite 5.3.1 - Download - Thread
- Drivers - Download - Thread
- Fastboot - Download - Thread
- IHOP_Bell pudding - Download - Thread
Instructions:
a. Extract the file from IHOP_Bell into a location your will remember
b. Extract the files from Fastboot package to a location you will remember - I will use C:\fastboot\ in my example
1. Turn off you phone
2. For safety measures, take out your SIM card and microSD card
3. Boot into RSD Mode by holding volume up and the power button at the same time until "Starting RSD protocol support" is displayed on the screen
4. Run RSD Lite on your pc
5. Press the [...] box next to the box named 'Filename'
6. Locate the file from IHOP_Bell that you extracted earlier
7. Load the file
8. Plug your phone into your pc
9. RSD Lite should recognise your device and should say something like "Model: NS Flash Olympus" mine said "SE Flash Olympus" and it should also say "Connected..."
10. Press the 'Start' Button
11. Be paitient while the phone reboots as it may take a loooong time
12. Once the phone has rebooted, open a command prompt window
13. Type in CD followed by a space and then the directory where you extracted the fastboot package - I will use C:\Fastboot\ in my example so I would type
Code:
CD C:\Fastboot\
14. Turn off your phone
15. Unplug your phone from the usb port
16. Hold the volume down button and the power button until you see 'Fastboot' on the screen
17. Press volume up to select fastboot, you will see "Starting Fastboot protocol support" on screen
18. Plug your phone into the usb port
19. Then in the command prompt window, type in the following command:
Code:
fastboot oem unlock
20. You will see a warning along with a unique device ID
21. Type in the following commands but use your unique device ID in place of the '#####'
Code:
fastboot oem unlock #####
fastboot -w
fastboot reboot
22. Now wait for your device to boot, whilst booting you should see 'Unlocked' on the boot screenFlashing 2.3.4 (Orange FR):
Downloads:
Moto-fastboot - Download - Thread
OrangeFR system - Download - Thread
OrangeFR webtop - Download - Thread
(Remember your Tegrapart you found out earlier.. download the right one for your device)
d00 - Download - Thread
1100 - Download - Thread
Instructions:
a. Unzip the moto-fastboot package into a directory you will remember, again I will place mine in a directory named motofastboot in my C: drive.
b. Extract the system, webtop and the correct tegrapart boot.img and place them inside your motofastboot directory
1. Turn off your phone and unplug it from the usb port if it is connected
2. Boot into fastboot mode by holding volume down and the power button untill you see 'Fastboot' on screen.
3. When you see fastboot, press volume up.
4. Open a command prompt and CD to the directory you placed your moto-fastboot package, I would enter:
Code:
CD C:\motofastboot
5. Now enter:
Code:
moto-fastboot flash system ORFR234-system.img
6. Once complete, enter:
Code:
moto-fastboot flash webtop webtop.img
7. And finally enter either:
Code:
moto-fastboot flash boot ORFR234-tegrapart-d00100.boot.img
OR
Code:
moto-fastboot flash boot ORFR234-tegrapart-1100100.boot.img
Depending on your Tegrapart number.
8. Turn off your phone, boot it back up and you should now be rocking Orange 2.3.4 GingerBread.
briliant guide mate! could you add some kernels and roms thats working with UK's atrix
Cheers
Thanks, this is exactly what I needed in terms of clear, complete information all in one thread.
Sorry if this is a stupid question but I'm new to the Atrix and there's so much info all over the place my head is already spinning! I'm on UK T-mobile, I assume the unlocking and rooting part is still the same, but should I still flash the Orange file or would this mess up my phone? All I really want to do is root/unlock so I can flash a custom rom.
Many thanks.
eggshaped said:
Thanks, this is exactly what I needed in terms of clear, complete information all in one thread.
Sorry if this is a stupid question but I'm new to the Atrix and there's so much info all over the place my head is already spinning! I'm on UK T-mobile, I assume the unlocking and rooting part is still the same, but should I still flash the Orange file or would this mess up my phone? All I really want to do is root/unlock so I can flash a custom rom.
Many thanks.
Click to expand...
Click to collapse
No, it won't. In fact, even Orange FR and Orange UK are as different as AT&T and T-Mobile UK. Also, ALL AT&T ROMS WORK! All you need to do is to flash faux123's kernel over the top of the ROM, just to get back your RAM. Even if you don't flash the kernel, you will not brick, just have the limited RAM issue.
Finally, most of us should be on the N_01.95.00R radio. What speeds and battery life do you get out of this on Orange UK?
It seems I have been capped to 1.9mbps
kartik50 said:
No, it won't. In fact, even Orange FR and Orange UK are as different as AT&T and T-Mobile UK. Also, ALL AT&T ROMS WORK! All you need to do is to flash faux123's kernel over the top of the ROM, just to get back your RAM. Even if you don't flash the kernel, you will not brick, just have the limited RAM issue.
Finally, most of us should be on the N_01.95.00R radio. What speeds and battery life do you get out of this on Orange UK?
It seems I have been capped to 1.9mbps
Click to expand...
Click to collapse
Thanks for replying...I think I understand what you're saying.
However, I'm on T-mobile UK not Orange. I only ever use wifi for data so not sure about speed, but battery life seems to be just over a day although I've only had the phone a few days so far. Just trying to make sense of it all .
I wish there was one definitive thread on what you need to do to get the phone to a point where you can flash a custom rom. Don't get me wrong, I'm not lazy and don't mind reading up and researching, I'm just really confused at the moment about whether I need to follow the pudding thread and flash sbf files (it says to put Pudding on the phone, whatever that is) or use Gingerbreak or SuperOneClick, and how to get cwm recovery on the phone.
....more reading up is in order I guess, until it all sinks in
Anyone know why it's stuck on the boot screen with this? I even SBF'd back to stock Orange 2.2.2 before hand. I also fastboot -w it. Is there nothing you can just flash for this?
this is what i get when trying to flash???
C:\Users\kris\Desktop\motorola>fastboot flash system ORFR234-system.img
sending 'system' (327680 KB)...
(bootloader) Image is too big, use 0x10000000 bytes chunks
FAILED (remote: (00000006))
finished. total time: 0.003s
C:\Users\kris\Desktop\motorola>moto-fastboot flash system ORFR234-system.img
'moto-fastboot' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\kris\Desktop\motorola>moto -fastboot flash system ORFR234-system.img
'moto' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\kris\Desktop\motorola>fastboot flash system ORFR234-system.img
sending 'system' (327680 KB)...
(bootloader) Image is too big, use 0x10000000 bytes chunks
FAILED (remote: (00000006))
finished. total time: 0.002s
C:\Users\kris\Desktop\motorola>moto-fastboot
'moto-fastboot' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\kris\Desktop\motorola>fastboot flash system ORFR234-system.img
sending 'system' (327680 KB)...
(bootloader) Image is too big, use 0x10000000 bytes chunks
FAILED (remote: (00000006))
finished. total time: 0.002s
C:\Users\kris\Desktop\motorola>moto-fastboot
'moto-fastboot' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\kris\Desktop\motorola>fastboot flash system ORFR234-system.img
sending 'system' (327680 KB)...
(bootloader) Image is too big, use 0x10000000 bytes chunks
FAILED (remote: (00000006))
finished. total time: 0.002s
C:\Users\kris\Desktop\motorola>
cheers
ok then, the link supplied for moto-fastboot is incorrect - found in the instruction link http://forum.xda-developers.com/showthread.php?t=1138092 - the guide also needs to add to press the up arrow to transfer the images. moto-fastboot.exe is not included in the original link.
I assume the initial link is for linux.
Nope that's what I used on windows 7 x64 mate, and I didnt have to press up to transfer the images either :S
I had no problem with the moto-fastboot, but it does just get stuck on the loading screen with unlocked.
When I run Gingerbreak, nothing happens?
EDIT: Fixed.
usb debugging on and usb storage
I heard that people are reporting bluetooth problems after rooting their atrix. Can anyone confirm that their bluetooth are working after rooting here??
airheli1201 said:
I heard that people are reporting bluetooth problems after rooting their atrix. Can anyone confirm that their bluetooth are working after rooting here??
Click to expand...
Click to collapse
I didn't have any issues
another quick question. Will the data on my internal storage be somewhat erased by following these steps???
edit: found out... yes it does, yes it does. haha. lost all my application data! oh well.
Hi,
followed all the steps on unlocking the bootloader and all went well, expect now it appears stuck on rsd saying executed 100%, but 'please manually reboot power up this phone'. Oddly though the phone is already on, what should I do?
Hi ive rooted and unlocked the bootloader and was following the guide to a T...
on the part of flashing 2.3.4 ORANGE i downloaded all the relevant files and placed them the motofastboot folder. it says to then turn the phone off and boot into fast mode which i have done. and then pressed volume up and now states tarting Fastboot protocol support
I then connect the phone to the computer and started step 5. and it says its not recognised as an internal or external command....etc etc! what am i doing wrong? i tried to put cd before the command prompt and it just says system can not find the path??? but i have everything in the correct place? help plssss
Have you put renamed the motofastbootx86 or x64 to just motobootfastboot and then your commands will work. Hope that helps
Am desperate to get Gingerbread installed on my Atrix I have followed all the above steps carefully (atleast I think I have) but when I get to the stage of flashing at the cmd prompt I get:
The program can't start because adbWinApi.dll is missing from your computer. Try reinstalling the program to fix this problem.
What am I doing wrong ??? Thanks in advance
---------- Post added at 10:18 PM ---------- Previous post was at 09:53 PM ----------
Roberts56 I had that problem at 1st and founf that the motofastboot file is corrupt, I did a search and downloaded it from elsewhere and it all worked fine.
Well it did untill I got my error message above ;-(
Here is the working version with the dll files that I was missing, hope this helps.
Sorted me out in the end and I have to say it has given my Atrix a new lease of life.
Am well impressed
Related
so i ran the fastboot oem lock so i could flash the tmous leak. It worked but says
***relocked***
*** security warning***
now everytime i try to boot anything like recovery, or just reboot phone it keeps bringing me to the hboot screen.
when I choose reboot bootloader option in fast boot it reboots and says ***relocked*** and no security warning like before.
so i dont think its bricked, i just dont know where to go from here
edit: could be a brick. adb wont recognize and I cant get into recovery
thanks in advance
anyone here know what I can do? i really need to get this fixed asap
thanks
Make sure you are giving the fastboot command from the proper directory in command prompt (most likely need to type "cd (to change directory) C:\Android\platform-tools" is prolly where it is, but might be just the \Android directory depending on how you set it up.
Find where OEM_lock is on your pc
Sent from my HTC Ruby running Sense 3.6
i ran fastboot from correct area. I have it in an android directory and the platform_tools. does it make a diff which one I use?
and how to check oem token on pc?
thanks
the thing is I cant get adb to recognize my device when running adb devices. when I reboot bootloader it catches the device for about 1second then its like its not being read anymore(if that makes any sense)
i get this when trying to unlock bootloader
fastboot oem unlock(from platformtools directory)
<bootloader> [ERR] Command error !!!
okay [ 0.007s]
finished. total time: 0.007s
screw it i just had tham send me another phone...they even knocked off 200 bucks from the original priuce of device!!!
but if someone can fix this issue i am more than happy to be learned lol
I was on the same situation as you. All I do and works was:
*Some steps maybe unnecessary but i do it.
1. Pull Battery out
2. Remove Sim card
3. Redownload the PH85IMG.zip (The original "football" post in FileFactory not the mirrors)
4. Put in Sd Card 2 (microSD)
5.Press Volume- and Power
6. Update (Wait for Process)
7. Press Power for Reboot
** Maybe we got a corrupted file, try redownloading the original file.
Pray for Misery
NoWey said:
I was on the same situation as you. All I do and works was:
*Some steps maybe unnecessary but i do it.
1. Pull Battery out
2. Remove Sim card
3. Redownload the PH85IMG.zip (The original "football" post in FileFactory not the mirrors)
4. Put in Sd Card 2 (microSD)
5.Press Volume- and Power
6. Update (Wait for Process)
7. Press Power for Reboot
** Maybe we got a corrupted file, try redownloading the original file.
Pray for Misery
Click to expand...
Click to collapse
tried all that last night and no love.
there has to be an easy fix you would think
Hi All,
I've been using CM7 on my HTC aria for more than an year without any problems. yesterday i decided to do S-OFF my phone and followed the below mentioned steps
Post#84 of the following linkhttp://forum.xda-developers.com/showthread.php?t=1122574&page=9
For windows users using CM7:
Note 1: This is assuming you already have the SDK installed and know how to use ADB, that you have CM7 installed.
Prerequisites:
- USBDeview - http://download.cnet.com/USBDeview/3...-10614190.html
- HTC Sync - http://www.htc.com/www/SupportViewNe...73&news_id=907
- clockwork2501.zip - http://forum.xda-developers.com/atta...5&d=1305031790
- fastboot - http://forum.xda-developers.com/atta...9&d=1230278653
- HTC Aria 2.2 - http://member.america.htc.com/downlo...ROM_Update.exe
alpharevx - http://alpharev.nl/x/beta/
1. Download all of the items listed above.
1a. Make a NANDROID backup!!!
2. USBDeview...delete (uninstall) all HTC related drivers.
3. Install HTC Sync
4. Plug phone in and allow windows to install the drivers.
5. Boot into fastboot (while powered down, press and HOLD trackball button and power button).
6. plug phone in to computer and run the HTC Aria for ATT Android 2.2 ROM Update (2.2 RUU).
7. Once you get 2.2 installed, and booted into the ROM, run the alpharevx executable.
8. It should notice your phone right away (make sure USB Debugging is enabled!!) and do it's thing, and then ask you for your beta key (get it from website, with your serial number) and then it will reboot a couple times and you're good to go.
9. Once you've got your S-OFF, boot into the ROM.
10. Place fastboot.exe and clockwork2501.zip into the folder where alpharevx.exe is (if you don't do this, you'll get an error about a missing .DLL (which happens to be included in the alpharevx download)).
11a. Open up command prompt and change directory ("cd") to your tools folder for Android SDK. Run the first command under step 12 (adb reboot bootloader)
11b. Open up command prompt and change directory ("cd") to wherever your fastboot.exe is (i.e. cd c:\users\username\desktop\alpharevx). Now run the rest of the commands under step 12.
12. Run the following commands:
Code:
Code:
adb reboot bootloader
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip clockwork2501.zip
fastboot reboot
12a. After "fastboot oem rebootRUU" your phone will be stuck at an HTC screen. This is when you should type the next command.
13. You should now be able to get into clockwork and restore your nandroid.
14. Boot into your CM7 and enjoy your S-OFF
This is going off of sheer memory but I am pretty sure it's exactly how i did it. If I have missed any steps or said anything wrong, someone feel free to correct me. If you have any questions, as always, feel free to ask.
Again, enjoy
+1 to alpharev team and whomever else made this possible!
Click to expand...
Click to collapse
i executed all the above steps in order. got froyo 2.2 and then did S-OFF (success). everythign was good until i faced some issues in STEP#12. while i executed the following command , i got the below mentioned error.
Code:
fastboot flash zip clockwork2501.zip
Code:
Error message:
[COLOR="Red"]FAILED (remote: 51 partition update fail)[/COLOR]
Since then, the phone booting to a black screen with "HTC" in the middle
and "warning" triangles at the corners.
HELP!!! please help me in fixing this issue.
Thanks guys
Are you able to boot into fastboot?
Theonew said:
Are you able to boot into fastboot?
Click to expand...
Click to collapse
thanks for your reply.
how do i check about fastboot? (tell me some commands that can run & check)
all i can say is, i'm not able to goto boot options-recovery (i.e clockworkmod). Before doing S-OFF,i had done a nandroid backup which i want to restore now.
I've tried many times to run "fastboot flash zip clockwork2501.zip". and also tried to download different version of clockworkmod recovery from the below link (for htc aria). none of them seem to work
http://forum.xda-developers.com/showpost.php?p=14693680&postcount=1
Open the clockwork2501.zip (from your computer) and extract the contents. You want the recovery.img file that is inside the zip file. Then, while the phone is in FASTBOOT mode and USB cable connected to computer, issue:
Code:
fastboot flash recovery recovery.img
If you don't know how to get to fastboot mode, the easiest way is to completely turn the phone off (pull battery if necessary), then hold down the trackball button and press power button, then release trackball button after the screen turns on.
the problem is i'm not able to get into either fastboot or hboot recovery bootscreen.
i took off battery, then hold down trackball , then pressed power button. still i get a black screen with "HTC" in the middle and "warning" triangles at the corners.
i took off battery, then hold 'volume -' button and then pressed power button. still i boot only into black screen with 'HTC' in the middle and triangles at four corners.
i get a feel that i still didn't install clockwork successfully. but the only problem is i couldn't figure out how to flash clockwork recovery. every time i try fastboot commands
Code:
fastboot flash zip clockwork2501.zip
or
fastboot flash recovery recovery.img
Code:
[COLOR="Red"]c:\Downloads\HTC aria\Jun 2012\revolutionary-0.4pre4>fastboot flash recovery recovery.img
sending 'recovery' (4224 KB)... OKAY
writing 'recovery'... FAILED (remote: image update error)
c:\Downloads\HTC aria\Jun 2012\revolutionary-0.4pre4>fastboot flash zip clockwor
k2501.zip
sending 'zip' (2702 KB)... OKAY
writing 'zip'... INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOstart image[recovery] unzipping & flushing...
INFO[RUU]UZ,recovery,0
INFO[RUU]UZ,recovery,24
INFO[RUU]UZ,recovery,64
INFO[RUU]UZ,recovery,100
INFO[RUU]WP,recovery,0
INFO[RUU]WP,recovery,24
INFO[RUU]WP,recovery,48
INFO[RUU]WP,recovery,72
INFO[RUU]WP,recovery,96
FAILED (remote: 51 partition update fail)[/COLOR]
singularthing said:
i took off battery, then hold 'volume -' button and then pressed power button. still i boot only into black screen with 'HTC' in the middle and triangles at four corners.
Click to expand...
Click to collapse
Just to make sure, you are continuing to hold down the 'volume -' button even after pressing power button, right? Don't let go too early. Also, make sure the USB cable is NOT plugged in while doing this. Plug the USB cable in after you're already in HBOOT or FASTBOOT.
If you're still having problems, I'd suggest attempting to run the official 2.2.2 RUU on your phone to see if it can revert your phone to a working state.
drumist said:
Just to make sure, you are continuing to hold down the 'volume -' button even after pressing power button, right? Don't let go too early. Also, make sure the USB cable is NOT plugged in while doing this. Plug the USB cable in after you're already in HBOOT or FASTBOOT.
If you're still having problems, I'd suggest attempting to run the official 2.2.2 RUU on your phone to see if it can revert your phone to a working state.
Click to expand...
Click to collapse
awesome! i re-installed HTC sync and ran the official 2.2.2 RUU exe file. viola i'm able to go into 2.2.2 and make calls , send text etc!! But, i still love my CM7. so i decided to do 'nandroid restore'. but i couldn't get into clockworkmod recovery screen
when i hold 'volume -' button and power on i see the following
Code:
LIBERTY PVT SHIP S-OFF
HBOOT -6.02.1002
MICROP-031B
TOUCH PANEL-STN21_03
RADIO-7.16.35.11
NOV 4 2010,23:12:58
HBOOT
RECOVERY
SIMLOCK ..
When i use volume keys and come down to 'RECOVERY' and press power button, i get some error screen (a black screen showing a small phone picture and a red triangle with exclamation mark).
i then tried the below two options.
1. rebooted the phone into 2.2.2 OS. enabled USB Debugging. Ran revolutionary.exe (it was handing in first step with message waiting for device) for a very long time. 15 mins after which i killed that in task manager.
2. rebooted phone. when into HBOOT. (waited for SD card diagnosis and then selected HBOOT via volume keys and then pressed power button). then connected USB cable and executed the following commands
Code:
c:\Downloads\HTC aria\Jun 2012\revolutionary-0.4pre4>fastboot flash zip clockwork2501.zip
< waiting for device >
^C
c:\Downloads\HTC aria\Jun 2012\revolutionary-0.4pre4>fastboot flash recovery recovery.img
< waiting for device >
^C
looks like i'm still not able to goto clockwork recovery/ and do nandroid restore.
singularthing said:
looks like i'm still not able to goto clockwork recovery/ and do nandroid restore.
Click to expand...
Click to collapse
Yeah, sorry if I wasn't clear, but even if you had CWM installed earlier, running the 2.2.2 RUU will remove it and bring you back to stock. I just told you to use the 2.2.2 RUU to bring the phone back to a working state. However, the RUU will NOT remove S-OFF, which is good.
The next step is to install CWM. I advise you to install the latest version, NOT the one you were previously using. The nandroid backup should still work fine. Here's what you should do:
Download 5.0.2.8 recovery (or a different one of your choice) here: http://forum.xda-developers.com/showpost.php?p=25490394&postcount=66
Put your phone into FASTBOOT, then connect USB cable, and then do:
Code:
fastboot flash recovery filename.img
drumist said:
Yeah, sorry if I wasn't clear, but even if you had CWM installed earlier, running the 2.2.2 RUU will remove it and bring you back to stock. I just told you to use the 2.2.2 RUU to bring the phone back to a working state. However, the RUU will NOT remove S-OFF, which is good.
The next step is to install CWM. I advise you to install the latest version, NOT the one you were previously using. The nandroid backup should still work fine. Here's what you should do:
Download 5.0.2.8 recovery (or a different one of your choice) here: http://forum.xda-developers.com/showpost.php?p=25490394&postcount=66
Put your phone into FASTBOOT, then connect USB cable, and then do:
Code:
fastboot flash recovery filename.img
Click to expand...
Click to collapse
Many Many thanks drumist. yes as soon as i tried recent CWM things started to work (i tried 5.0.2.8). now i'm doing nandroid restore. i will do some basic checking tonight and report back tomorrow(tomorrow i will mark the thread resolved). i'm pretty confident everything should be okay.
Step-by-step guide for unbricking a Photon from an ota update brick and recovering from a "failed to boot 2" or "failed to boot 3" error when booting.
Also, big note, this is NOT for 2.3.4 users!
EXTREME thanks to peetr_ for ALL of this info and getting myself and probably countless others fixed. All the links are files he uploaded personally and all these instructions come directly from him. Be sure to thank the crap out of him if you get your device fixed through this method.
1) Make sure you have all the motorola drivers (I assume you do otherwise you wouldn't have been able to brick your device).
2) Make sure you have a FULL ass charge. Not 90%, but FULL! I know it doesn't charge when it's in the failed to boot mode. I bought an external battery wall charger from Overstock for under $10 shipped, I suggest you do the same.
3) Enter Fastboot mode by holding the volume up key while powering on your device.
4) Connect your phone via USB to your computer.
5) Open command line on your computer (Windows key + "R", then type in "cmd") or (Windows 7: Open the start menu and type "cmd").
6) Download and extract this file: (uploaded by peetr_) http://d-h.st/xl8 (if no hyperlink, copy and paste the previous text in your browser). There should be a "boot.img" file and a "recovery.img" file.
7) It is VERY helpful to have all your files in one directory, all your fastboot files, ADB and all that jazz should be in the same directory as well as all the files you've downloaded to flash.
8) In command line type in "moto-fastboot flash boot boot.img" (assuming you followed step 7). It will say "sending" and then "writing" and should only take a few seconds. Your device will say some things too. After this, restart your device and your phone should boot in for the first time since you bricked it. (That was the greatest thing to watch after being bricked for 3 weeks!)
9) You're not quite out of the woods yet, 4G and WiFi will not work yet. Hold the power button up while powering on once again to enter fastboot mode.
10) Once again in command line (assuming your phone is still hooked up) type in "moto-fastboot flash recovery recovery.img" and it will send and write.
11) If your phone wasn't previously rooted or if somehow you lost root go ahead and root it now (just google the oneclick method).
12) Download these modules http://d-h.st/aAi and store them on your device, SD card or internal memory.
13) Download the RootExplorer app and navigate to the zip on your device, set it to Read/Write on the top of the app and hold the zip down until you get a menu, hit permissions and set them.
14) Hold volume up while powering device on and you should get into Bootstrap recovery.
15) Hit "install zip from SD card" and navigate to the file and install it.
16) Boot the device normally and congratulations! You now have working WiFi and 4G on an electrify flashed Photon! OTA updates will NOT work and you will NOT be able to unlock the bootloader via pudding for Custom ROM installs. If you hate blur like I do, download "GO Launcher" or my personal favorite "SPB Shell".
I appreciate your effort. Just highlighting some inaccuracies.
This is only for failed to boot (2 or 3) after ota 2.3.5 update. Not after flashing Electrify sbf. You never flashed that.
And you cannot flash modules with android recovery option in bootloader menu, you had to install bootstrap recovery or copy with root explorer and set permissions one by one.
And give there a big warning, that this is not for 2.3.4 users.
Other than this, it's good.
Edited! Hopefully it's good enough to help some people now.
bdotr said:
Edited! Hopefully it's good enough to help some people now.
Click to expand...
Click to collapse
I dont have any error like failed boot 2 or 3..
But i am stuck to dual core screen.... so what to do....???
Help!
I am trying to follow your directions. I sure F'd my photon up tonight... I have about decided to go and file a warranty claim and accept that it is done for...
When trying to flash your files using fast-boot it just says waiting for device. any ideas? Thanks alot !
Need help!
I bricked my photon when I was trying to install a custom rom..
I get the error failed to boot 2.
When I try to follow the steps u have mentioned ...
In the first step itself when I want my phone to be back to stock I am not able to do it...When im trying to transfer the sbf file I get "Failed flashing process. Unable to retrieve interface handle. (0x7027)"
Please guide me what to do.
got failed to boot 2
hello dear all member i need help really i try to install jb in my motorol Sprint Photon 4g but when it reboot i get failed to boot 2 i dont understand what to do i dont have backup and i dont have any file when i type in command that moto-fastboot flash boot boot.img it dont work and i have only 2 files that downloaded from ur link boot.img and other 1 but they dont work
i dont have any ADB file or other directory to copy them there so help me plzzzzzzzzz
folks im at my nerves end... (hello btw)
firstly a thousand apologies to the mods if im posting this in the wrong place and a thousand apologies more to the rest of you for asking a question that has probably been answered time and time again.....
I can't get round it, iv been able to unlock bootloader and I thought that would have been the hardest part.... but I think I cant get my hands on the right, up to date files, in order to root my current system... iv been doing a ton of reading and just as many rooting attempts on my phone but to no avail......
the closest iv got in the command window was "error: device 'null' not found", to my understanding this is a driver related issue?...I dont know... if someone could hold my hand (im scared) and walk me through the process step by step I would be very, VERY grateful....
P.s; in exchange I can help you install CFW on a PSP.....lol right? (I actually made a pandora battery back in the day and im still rather proud of that)
UPDATE:........ So i think I was able to flash the proper Kernel (adroid plus kernal V42) but was unable to do flash recovery?
rootcheck says "root access is not properly installed on this device" still.....
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (14956 KB)...
OKAY [ 0.479s]
writing 'boot'...
OKAY [ 0.143s]
finished. total time: 0.624s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-2.8
.7.0-E6653-20151114_material.img
error: cannot load 'twrp-2.8.7.0-E6653-20151114_material.img'
UPDATE:
So i was able to do a flash recovery by renaiming the twrp file to simply twrp and adapting the code typed in the command window...... this caused my phone to soft brick or enter a bootloop....
after some swearing and more reading I was able to do a flash recovery with twrp-3.0.2-0-E5823.img (again by typing the exact name of the .img file in the command window....duuhhhh).... this allowed my phone to boot properly (thank God)... but root checker still says "root access is not properly installed on this device".....
I feel as if im close to my goal, what am I doing wrong!?......that soft brick served me as a cold shower and a lesson....this is kinda fun!
FINAL UPDATE:
BOOOM!!! success..... only took me all day...... still one thing though, i was unable to back my system due to lack of space on my SD card.... am I boned in this regard or can I create a back up later?
Thanks for the updates, i will try to follow your guide. how did you finally achieve success ?
Hey Rath,
First off im not responsibly for any damage caused to your device by the following guide....
....on to business...
Assuming your phones bootloader is unlocked, you have correctly installed ADB tools and the drivers required, allowed USB debugging and you know your build number you'll need to head over to this site...
https://kernel.andro.plus/kitakami_r2.html
scroll down....there you will see two sets of requirements one for the Xperia Z5 [E6653 / E6603] and one for the Xperia Z5 Compact [E5823 / E5803]
we are interested in the compact requirements.... you'll see that it says "32.2.A.5.11 -> v42 -" this means that for build number 32.2.A.5.11 you will need kernel version 42....
so keep scrolling down once you've figured out what version you need and click on "google drive V32 and later" for the Xperia Z5 Compact this will open a page with all the files inside (google drive)...either hover over with your mouse each file until you find "Z5C_AndroPlusKernel_v42.zip" or organize the files by clicking "last modified" in list view, this should show you the most recent file (v42) at the top of the list....
once you have found this file DL it and extract it to your desktop...copy ONLY the "boot.img" file into your platform-tools folder (android->sdk->platform-tools)....
next you'll need a recovery file or "twrp" to go with that, so head on over here...
https://www.androidfilehost.com/?fid=24459283995304864
and download that file, again copy it to your desktop (no need to extract) then copy this file as well to your platform-tools folder......copy the exact name of the file(TWRP-3.0.0.0-suzuran without the .img part...if youre on windows the .img will not show anyway..)...you'll need it later...
next open the command window by clicking on an empty space IN THE PLATFORM-TOOLS folder, then press shift+right click and select "open command window here" this will open adb tools...connect your phone via usb cable to your pc if it not already connected and type in the command window "adb devices" and hit enter....you should see your device listed...
if so type "adb reload bootloader" your phone should turn off and boot into bootloader (a blue led light should show in the top right corner of your phone)
if so type "fastboot devices" and hit enter...your device should show again on the list...
if so then type "fastboot flash boot boot.img" this will flash the kernel V.42 to your system....
you should see a couple of "OKAY"s and the time it took to flash the device....
next type "fastboot flash recovery *right click after the space and paste the exact name of the twrp file you copied earlier*.img
E.g: fastboot flash recovery TWRP-3.0.0.0-suzuran.img
and hit enter.... again you should see a couple of "OKAY"s and flashing times....
if all goes well you want to then type "fastboot reboot", your phone should then reboot...once you see a yellow light turn on on the top right corner press the down volume key several times until you enter the TWRP recovery menu.... if so, and the twrp is stable (ie it doesnt turn off on its own and reload) then the hardest part is done.....
click "reboot" on your phone and then click "system"...this will reboot your phone, this time let it run to see if it doenst get stuck in a bootloop....once your phone has loaded you'll want to install superSU....
go to the play store and DL rootchecker.... run the app and it will most likely tell you that your system isnt rooted yet (because we havent installed superSu) so head on over here...
http://www.supersu.com/download
scroll down and DL Recovery "Flashable.zip"...then take the file WITHOUT EXTRACTING IT and put it in the SD of your phone... reboot into recovery using the command window (adb reboot recovery) or turn off your phone, turn it back on and when you see the yellow light click volume down button repeatedly....
once in recovery select INSTALL click on the ZIP file you just added and the phone will install supersu, once done reboot your system and VOILA! check with the root checker app if your phone is root and have fun!....
I found this video to help me out a lot....he uses really old files and is rooting an xperia z5 but its essentially the same....
https://www.youtube.com/watch?v=dTlosea6SJE&t=709s
SwisSwiss said:
UPDATE:........ So i think I was able to flash the proper Kernel (adroid plus kernal V42) but was unable to do flash recovery?
rootcheck says "root access is not properly installed on this device" still.....
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (14956 KB)...
OKAY [ 0.479s]
writing 'boot'...
OKAY [ 0.143s]
finished. total time: 0.624s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-2.8
.7.0-E6653-20151114_material.img
error: cannot load 'twrp-2.8.7.0-E6653-20151114_material.img'
UPDATE:
So i was able to do a flash recovery by renaiming the twrp file to simply twrp and adapting the code typed in the command window...... this caused my phone to soft brick or enter a bootloop....
after some swearing and more reading I was able to do a flash recovery with twrp-3.0.2-0-E5823.img (again by typing the exact name of the .img file in the command window....duuhhhh).... this allowed my phone to boot properly (thank God)... but root checker still says "root access is not properly installed on this device".....
I feel as if im close to my goal, what am I doing wrong!?......that soft brick served me as a cold shower and a lesson....this is kinda fun!
FINAL UPDATE:
BOOOM!!! success..... only took me all day...... still one thing though, i was unable to back my system due to lack of space on my SD card.... am I boned in this regard or can I create a back up later?
Click to expand...
Click to collapse
i wonder if you backup the DRM keys\TA partition
In regards to why i was unable to create a back up right away? Not sure, think it was simply a matter of volume...
Had a crappy 4gb micro sd In there....
Hi all, i have a problem that i can't solve, is the oem unlocking on my blu life one x2. I downloaded adb and fastboot (windows user), phone and adb drivers, and when i put the phone on bootloader mode, i run the "fastboot oem unlock" command, and the command prompt say: "need user wipe data, do fastboot oem unlock-go", so i put these command, and the oem is not unlocked yet, so I repeat those steps and the command prompt keeps showing me the same message (need user wipe data, do fastboot oem unlock-go). At this point, I have no idea what I'm doing wrong, I made the factory format many times, and I cannot unlock the OEM.
Can help me pls? I want to root my device, but because of this problem, I can not go to other steps :crying: :crying:
Thanks
Jonsonrocky said:
Hi all, i have a problem that i can't solve, is the oem unlocking on my blu life one x2. I downloaded adb and fastboot (windows user), phone and adb drivers, and when i put the phone on bootloader mode, i run the "fastboot oem unlock" command, and the command prompt say: "need user wipe data, do fastboot oem unlock-go", so i put these command, and the oem is not unlocked yet, so I repeat those steps and the command prompt keeps showing me the same message (need user wipe data, do fastboot oem unlock-go). At this point, I have no idea what I'm doing wrong, I made the factory format many times, and I cannot unlock the OEM.
Can help me pls? I want to root my device, but because of this problem, I can not go to other steps :crying: :crying:
Thanks
Click to expand...
Click to collapse
any here? ...
Jonsonrocky said:
any here? ...
Click to expand...
Click to collapse
Hi there, I have THE VERY SAME PROBLEM. Done the same, with same lame results... BOOTLOADER STILL UNLOCKED!!
It is really frustrating... been through many posts and guides but can't finish them... fastboot OEM unlock with the user data eraser switch didn't work out well in any case.
IS THERE ANYBODY OUT THERE WITH A COMPLETE WORKING GUIDE WILLING TO SHARE IT?
Thanks in advance.
J.
I have the same problem also, I have posted on another thread but no responses. here is my error:
"FAILED (remote: Need wipe userdata. Do 'fastboot oem unlock-go')
finished. total time: 0.003s"
Has anyone figured out how to onlock the NEW BOOTLOADER?
I have a new life one x2 that BLU sent me.
pvkid said:
I have the same problem also, I have posted on another thread but no responses. here is my error:
"FAILED (remote: Need wipe userdata. Do 'fastboot oem unlock-go')
finished. total time: 0.003s"
Has anyone figured out how to onlock the NEW BOOTLOADER?
I have a new life one x2 that BLU sent me.
Click to expand...
Click to collapse
I guess no one knows the answer to this problem. This phone used to be rootable but I guess Blu changed something in their latest release of the Life One X2
How to root a Blu life one X2
I actually still use this device and should be able to get you through this.
I'm not sure where are you on the device i.e. partly unlocked ect.
I'll start you from the top and I'll let you pickup wherever you like.
First, let's get our links ready (because I had these ready to go for myself).
I just checked it now, the device specific links still work.
ADB: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
TWRP: https://drive.google.com/file/d/0B6_iuhJQH7aGM0JkOXJkUHdlRHM
MAGISK: https://www.apkmirror.com/apk/topjohnwu/magisk-manager/
STOCK: https://drive.google.com/file/d/0B6_iuhJQH7aGUFdVVkkzUk8yYWs
DRIVER: https://drive.google.com/file/d/0B6_iuhJQH7aGa3Q1cmN3eHI3QUE
DOWNLOAD: https://drive.google.com/file/d/0B6_iuhJQH7aGR05CSnlhWm1HWWc
1) Download The driver, download program, and stock ROM.
2) Install the first two files.
3) Go to: C:\Program Files (x86)\Qualcomm\QPST\bin
4) When your device is off; Hold down the vol up AND down while turning on the device and wait until the text disappears
5) Plug in the phone to the PC and a red light should start blinking
5) Unzip the stock rom (when done, it can take a while).
6) Open QFIL.exe
7) You should see "(COM8)" on the top for the connection
8) Click on the first Browse button and select the mbn file from the extracted stock ROM folder
9) Click on LOAD XML and click rawprogram_unsparse_upgrade and then patch0
10) Click download until the phone reboots into test mode; click reboot to start the 'new' phone
-----------------------------------------------------------------------------------------------------------------------
1) Do the generic phone stuff to unlock the bootloader by enabling dev options and then enable BOTH OEM unlocking AND USB debugging
2) Download and install magisk from the link above and then download the zip file it gives you to flash
3) Download the TWRP image and ADB files listed above and do whatever you need/want to do (boot, flash, or both)
4) Flash the magisk zip file and your done
-----------------------------------------------------------------------------------------------------------------------
Delete the folders fota, fota-updater, and fire from the system partition in TWRP as these are the spyware/adware that BLU added
If you want to disable and other apps that BLU added, you can just rename the file from *.apk to *.ap
I'll try to be around if you have any questions
Thank you for this. I just left on vacation and will not be able to try this till next week, hope you are around then as I am sure I will have questions.
dougo007 said:
I actually still use this device and should be able to get you through this.
I'm not sure where are you on the device i.e. partly unlocked ect.
I'll start you from the top and I'll let you pickup wherever you like.
First, let's get our links ready (because I had these ready to go for myself).
I just checked it now, the device specific links still work.
ADB: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
TWRP: https://drive.google.com/file/d/0B6_iuhJQH7aGM0JkOXJkUHdlRHM
MAGISK: https://www.apkmirror.com/apk/topjohnwu/magisk-manager/
STOCK: https://drive.google.com/file/d/0B6_iuhJQH7aGUFdVVkkzUk8yYWs
DRIVER: https://drive.google.com/file/d/0B6_iuhJQH7aGa3Q1cmN3eHI3QUE
DOWNLOAD: https://drive.google.com/file/d/0B6_iuhJQH7aGR05CSnlhWm1HWWc
1) Download The driver, download program, and stock ROM.
2) Install the first two files.
3) Go to: C:\Program Files (x86)\Qualcomm\QPST\bin
4) When your device is off; Hold down the vol up AND down while turning on the device and wait until the text disappears
5) Plug in the phone to the PC and a red light should start blinking
5) Unzip the stock rom (when done, it can take a while).
6) Open QFIL.exe
7) You should see "(COM8)" on the top for the connection
8) Click on the first Browse button and select the mbn file from the extracted stock ROM folder
9) Click on LOAD XML and click rawprogram_unsparse_upgrade and then patch0
10) Click download until the phone reboots into test mode; click reboot to start the 'new' phone
-----------------------------------------------------------------------------------------------------------------------
1) Do the generic phone stuff to unlock the bootloader by enabling dev options and then enable BOTH OEM unlocking AND USB debugging
2) Download and install magisk from the link above and then download the zip file it gives you to flash
3) Download the TWRP image and ADB files listed above and do whatever you need/want to do (boot, flash, or both)
4) Flash the magisk zip file and your done
-----------------------------------------------------------------------------------------------------------------------
Delete the folders fota, fota-updater, and fire from the system partition in TWRP as these are the spyware/adware that BLU added
If you want to disable and other apps that BLU added, you can just rename the file from *.apk to *.ap
I'll try to be around if you have any questions
Click to expand...
Click to collapse
Any luck?
We have ROOT in BLU Life One X2
dougo007 said:
Any luck?
Click to expand...
Click to collapse
Sorry it has taken so long for me to get back to you but I have been traveling out of the county and have not had time to try this.
I have been successful in rooting 2 Life One X2 phones with this prosses. One was new out of the box and the second one was an older one about 2 years old.
Thank you for all your help when no one ele knew the answer.
My next project is to root an Oukitel OK6000, there does not seem to be much information on this phone. If you hear of anything please let me know.
Links aren't working
dougo007 said:
I actually still use this device and should be able to get you through this.
I'm not sure where are you on the device i.e. partly unlocked ect.
I'll start you from the top and I'll let you pickup wherever you like.
First, let's get our links ready (because I had these ready to go for myself).
I just checked it now, the device specific links still work.
ADB: Link works
TWRP: Link does not work
MAGISK: Link works
STOCK: Link does not work
DRIVER: Link does not work
DOWNLOAD: Link does not work
1) Download The driver, download program, and stock ROM.
2) Install the first two files.
3) Go to: C:\Program Files (x86)\Qualcomm\QPST\bin
4) When your device is off; Hold down the vol up AND down while turning on the device and wait until the text disappears
5) Plug in the phone to the PC and a red light should start blinking
5) Unzip the stock rom (when done, it can take a while).
6) Open QFIL.exe
7) You should see "(COM8)" on the top for the connection
8) Click on the first Browse button and select the mbn file from the extracted stock ROM folder
9) Click on LOAD XML and click rawprogram_unsparse_upgrade and then patch0
10) Click download until the phone reboots into test mode; click reboot to start the 'new' phone
-----------------------------------------------------------------------------------------------------------------------
1) Do the generic phone stuff to unlock the bootloader by enabling dev options and then enable BOTH OEM unlocking AND USB debugging
2) Download and install magisk from the link above and then download the zip file it gives you to flash
3) Download the TWRP image and ADB files listed above and do whatever you need/want to do (boot, flash, or both)
4) Flash the magisk zip file and your done
-----------------------------------------------------------------------------------------------------------------------
Delete the folders fota, fota-updater, and fire from the system partition in TWRP as these are the spyware/adware that BLU added
If you want to disable and other apps that BLU added, you can just rename the file from *.apk to *.ap
I'll try to be around if you have any questions
Click to expand...
Click to collapse
Hello dougo007,
Some of the links are dead and I am stuck and cannot figure out how to get passed the failed error on OEM unlock. It just keeps saying try unlock go.
Could you please provide new links or point me to someplace that I can use to oem unlock my BLU Life ONE X2. I searched and can't seem to find anything.
Having the same issue as you were and the links don't work
pvkid said:
Sorry it has taken so long for me to get back to you but I have been traveling out of the county and have not had time to try this.
I have been successful in rooting 2 Life One X2 phones with this prosses. One was new out of the box and the second one was an older one about 2 years old.
Thank you for all your help when no one ele knew the answer.
My next project is to root an Oukitel OK6000, there does not seem to be much information on this phone. If you hear of anything please let me know.
Click to expand...
Click to collapse
Hi pvkid, do you happen to have the files from the link? or new places I can find them I am stuck in the same place you were and can't for the life of me find anything anywhere else that helps.