cause the newest evo's arent rootable? lol i just got my evo yesterday and ive searched everywhere that the newest hboot 2.02 and 3.30 cant get rooted? the evo is pretty good but im all customizations. i read that the epic is super easy to root.
It can be rooted you just have to work harder at it. Dont take it back you'll regret it.
Clearly you haven't done any searching in the Android Development section.
But that's OK. Go ahead and get an Epic. Enjoy your screwed-up GPS and all that, and make sure to change your password on here to something you won't remember, so we never have to see you again.
mainguy21 said:
cause the newest evo's arent rootable? lol i just got my evo yesterday and ive searched everywhere that the newest hboot 2.02 and 3.30 cant get rooted? the evo is pretty good but im all customizations. i read that the epic is super easy to root.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=829045
there you go. Just follow the directions and make sure you use the correct file locations.
real problem
What he really meant to say is . I am 16 and have Attention deficit hyperactivity disorder and cant bother myself to use the search button above me nor can i follow simple written instructions on rooting phone . If it dont have one click root i wont do it ........ i have both phones and the devs on evo are much better
thats funny i just typed in the search bar root evo hboot 2.02 and the first thread was the guide on how to do it.
@op if you are going to lie about searching the forum do it somewhere else. we know when a search isnt performed.
mainguy21 said:
and ive searched everywhere
Click to expand...
Click to collapse
Sure you have, buddy... sure you have.
ohhhhhhhhhhhhhh
You have been misinformed due to stupid people making stupid and false posts such as this one:
http://forum.xda-developers.com/showpost.php?p=9578042&postcount=8
Kingmac38 said:
What he really meant to say is . I am 16 and have Attention deficit hyperactivity disorder and cant bother myself to use the search button above me nor can i follow simple written instructions on rooting phone . If it dont have one click root i wont do it ........ i have both phones and the devs on evo are much better
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App
I am 20 and have ADHD and search is my best friend plus I've followed many rooting guides successfully so op has no excuse
Second that my girls epic is a pain in the ass and she kinda of.wish she got my phonr instead
Sent from my PC36100 using XDA App
thanks for help even though i searched everywhere.
but since i cant root my phone im stuck in the middle of it with a red triangle can i atleast go back to my phone? like unroot or something even though i didnt get all the way to root? please thanks
Follow these revised instructions from illogos pg 121 of hboot 2.02 root guide and everything should work. I've already rooted two hboot 2.02 hw 004 and in process of doing another one now. Everything works just fine if you understand and follow the instructions. Anyways, this was a lot simpler than the old school toast part 1 and 2 root methods so acquire some knowledge so you can someday help others and not be such a newbie.
thats what i followed and im still stuck at steps 10-11..my phone says in bootloader its "s-off" but i cant get that file to read after rebooting. ive tried over and over from the start and nada i even downloaded the file like 5 times.
mainguy21 said:
thats what i followed and im still stuck at steps 10-11..my phone says in bootloader its "s-off" but i cant get that file to read after rebooting. ive tried over and over from the start and nada i even downloaded the file like 5 times.
Click to expand...
Click to collapse
Which instructions though? Please follow these ones by illogos-
illogos said:
1. Make sure that you downloaded and installed HTC Sync from HTC website.
2. Unzip hboot202-s_off-V8.zip to a folder in your C: drive. I used C:\hroot
3. This hroot folder should have a folder inside it called root. If you have a folder called hboot202-s_off-V8 then you need to move all the files from that subfolder to c:\hroot.
4. In Vista/7 slick on the start button and type in cmd. You will see in the program list the command prompt. Right click and open as Administrator.
5. In the command prompt type cd c:\hroot
6. On phone goto-> Setting>Applications>Debugging make sure usb debugging is on.
7. Connect the usb cable to your computer and phone. The phone should change it's screen to ask you what type of connection mode you want. Make sure that it is on charge only. Do not mount.
8. Type into the command prompt: adb push root/unrevoked-forever.zip /sdcard/ After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
9. Type into the command prompt: adb push root/mtd-eng.img /sdcard/ After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
10. Type into the command prompt: adb push pc36img/PC36IMG-ENG.zip /sdcard/PC36IMG.zip After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
11. Type into the command prompt: adb push pc36img/PC36IMG-MR.zip /sdcard/PC36IMG-MR.zip After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
12. Type into the command prompt: adb push root/flash_image /data/local/ After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
13. Type into the command prompt: adb push root/rageagainstthecage /data/local/tmp After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
14. Type into the command prompt:adb shell You should see a $, this means that you are "in" the phone.
15. Type into the command prompt:chmod 0755 /data/local/tmp/rageagainstthecage You should see this echoed on your screen. This is normal. You should still have $ on your cmd line.
16. Type into the command prompt: chmod 0755 /data/local/flash_image You should see this echoed on your screen. This is normal. You should still have a $ on your cmd line.
17. Type into the command prompt:./data/local/tmp/rageagainstthecage A message will pop up on the screen. It will take a few seconds, and your will be kicked "out" of the phone. The $ should now be gone.
18. Type into the command prompt: adb shell You should have a # on your command line instead of a $. # means you have temporary root in your phone. If you do not have #, then start over.
19. Type into the command prompt that has #: ./data/local/flash_image misc /sdcard/mtd-eng.img
20. Type into the command prompt that has #: sync
21. Type into the command prompt that has #: reboot bootloader
22. Your phone will be rebooting now. Eventually your phone will be at the bootloader menu. On your phone use volume up/down to highlight bootloader and press the power button once. It will start loading the PC36img.zip file.
23.After it loads, it will ask if you want to flash. Press Volume UP to say yes. It will now flash, which can take some time. You may see some red fail messages. This is normal.
24.When it is done flashing it will ask you if you want to reboot. Press Volume Down to say now to reboot.
25. Use volume up/down to highlight recovery. Press the power button once. This will try to boot into recovery mode but fail and load a screen with a red triangle. This is normal because you have not installed recovery yet.
26. Go back to your computer screen and your command prompt. You should not have a #
27. Type into the command prompt: adb push recovery /
28. Type into the command prompt: adb shell busybox --install /sbin
29. Type into the command prompt: adb shell nohup /sbin/recovery &
30. After a pause you should see a new screen on your phone. It should be green text with your recovery options.
31. Highlight backup/restore. Press the power button. Highlight backup nand and press the power button. Press the power button again to confirm the action. Your phone is now doing a nandroid backup. This will backup your wimax keys amongst other things.
32. It will take a little time to do the backup. After it is done press the power button once to return to the recovery menu.
33. Highlight enable USB-MS and press the power button.
34. On your computer, you should see a new drive in my computer or a pop up asking you for an action. Click on Explore, or open the drive in my computer, to access your phone like you would a thumb drive.
35. Rename the file named PC36IMG.zip to PC36IMG-ENG.zip and then rename PC36IMG-MR.zip to PC36IMG.zip
36. On your phone, press the power button to disable USB-MS mode. You should be back at the recovery menu.
37. Highlight the option to flash image from zip. Press the power button.
38. Highlight unrevoked-forever.zip and press the power button. Press the power button again to confirm if told to do so.
39. When it completes flashing the image, select reboot from the menu.
40. When it reboots a few things could happen. If you think your phone is frozen, you are okay because that is a normal occurrence on this step.
----->Your phone gets "stuck" on a white screen with the word HTC on it for more than a minute. You need to take the back case off your phone and pull your battery out. Put the battery back in and put the back case on again. Hold down Volume Down and press(and release) the power button while you continue to hold down the volume down button. Your phone should go into the boot loader like it did at the start of the guide.
----->You phone started up and fully booted. You need to completely power off.Hold down Volume Down and press(and release) the power button while you continue to hold down the volume down button. Your phone should go into the boot loader like it did at the start of the guide.
----->The phone returns to the boot loader.
41. No matter which of the 3 scenarios occurred to you in the last step, you are now in the boot loader. Obviously the 3rd scenario is the best, but all are OKAY.
42. The phone should find PC36img.zip. It then loads this file and asks if you want to flash. Use volume up for yes. When it asks to reboot press volume up for yes.
43. When it is done booting, return to your computer screen and type adb shell mv /sdcard/PC36IMG.zip /sdcard/PC36IMG-MR.zip into the command prompt.
44. Type into the command prompt: adb reboot recovery
45. Highlight backup/restore in recovery and then press power. Highlight backup nand and press power. Press power again to confirm. Wait for the backup to complete.
46. Press power to return to recovery menu. Highlight reboot phone and press power.
47. Your phone is now rooted, S-OFF, and booted into stock 3.30.651.2.
-------------------------------------------------------------------------
After Root:
1. Run through setup and get to the actual phone screens.
2. Try to turn on 4G/wifi/etc and see if it all works. It may not and this does not mean disaster.
For me, I had to flash Stock RUU root 3.30.651.3 to get 4G to work. Here is what I did next:
1. Download stock RUU root 3.30.651.3(I opted for Odexed version) from http://forum.xda-developers.com/showthread.php?t=836728
2. Reboot phone into recovery by completely powering off. Hold down volume down and press power. When you get into the boot loader it will try to find PC36img.zip and fail (we renamed that file remember?) and that is normal. Use volume up/down to highlight recovery and press the power button.
3. In recovery highlight USB-MS and press power to enable.
4. Your phone should be mounted as a drive in your computer again like before. Copy the whole zip file that you downloaded for RUU 3.30.651.3 rooted odexed to your phone. Wait for it to finish the transfer.
5. On your phone press power to turn off USB-MS mode.
6. On the recovery menu highlight wipe and press power.
7. Highlight the first wipe option which is something like wipe cache/factory reset. Press power. Press power again to confirm if needed.
8. Hightlight the second wipe option which is wipe cache. Press power and then press power again if needed.
9. Highlight the third wipe option which is wipe dalvik-cache. Press power and then press power again if needed.
10. Return recovery menu.
11. Hightlight flash image from zip and press power.
12. Highlight the file that you just transfered over that is for RUU 3.30.651.3 and press power. Press power again to confirm if asked. It will start flashing the image to your phone, but you will not see progress bars. It will take a few minutes.
13. When it is complete select the option to reboot the phone.
14. The phone should fully boot up into the stock rooted 3.30.651.3 rom.
15. Now try to turn 4G/wifi/etc on and make sure it works. It did for me.
16. Assuming that everything is working fine, fully power off, boot into recovery, and do another backup. This newest backup is your holy grail backup. It is stock rooted S-OFF and 4G working backup.
Note: these last 15 steps can be used to flash any custom rom too. Just make sure that you get your "holy grail" backup first before you experiment.
Click to expand...
Click to collapse
my wife got an evo on black friday from radio shack and i rooted it with unrevoked in like 5 minutes.
I have adhd... I wonder if 4g transmissions cause an increase in autistic spectrum disorders!?!?
Sent from my PC36100 using XDA App
animal7296 said:
It can be rooted you just have to work harder at it. Dont take it back you'll regret it.
Click to expand...
Click to collapse
he wouldn't regret getting the epic, it's a cool ass phone. if you want a crisper lcd and a keyboard get the epic.
fixxxer2008 said:
If you want a cheap-ass plasticky POS, get the epic.
Click to expand...
Click to collapse
Fixed that for you.
tejasrichard said:
Fixed that for you.
Click to expand...
Click to collapse
Thank you. It seems all these Samsung phones feel like garbage. Way too flimsy. Now I have a friend with an LG Optimus S which I just rooted for her, and I have to say the build quality is very nice.
Related
EPE54B (new N1- AT&T) -> FRF50 -> FRF83 & beyond (hopefully) in 20 minutes
and FROYO IS AWESOME !!! Believe me , it's really worth making this effort .
Ok guys , I think it's time for me to contribute some documentation for the XDA forum. As mentioned in the Topic's header , I moved to Froyo y'day night and wanted to share the process with the AT&T N1 ppl on the forum who are ready to unlock the bootloader but are lazy/frightened to go about the so-called lengthy process.
I am a new N1 & a new android user (just a month old ) who has spent sleepless nights like some of the people in this forum and most of the people (here) waiting for the Froyo OTA to hit their N1's. After a 3 week sleep disorder I finally went in for the kill. Thanks to Paul for his guide and others in the forum because of which,this it was accomplished in just 20 minutes.
AT&T N1 (EPE54B) owners who are bold enough to unlock their boot loader ... here's the way to glory.
Senior XDA members please correct the process if you feel something is not right.
I will be using most of the info provided by Paul in his post (here) and I hope he wouldn't mind , if I use his info.And believe me guys , it seriously takes only 20 minutes.
DISCLAIMER
1) I do not take credit for any of the stuff posted here. It's mostly from Paul's guide and other sources. All credits go to the original up-loaders.
2) This is a step-by-step guide which I have prepared from the process I have followed to reach FROYO and am not responsible if it doesn't work for you.
2)You agree that by doing this process, I'm not responsible for any bricked devices.
Unlocking the bootloader will void your warranty.
This process will erase all of your phone's data.
INITIAL SETUP
1) Download android-sdk_r06-windows.zip
2) Unzip to C:\ drive so it looks like C:\android-sdk-windows\
3) Run SDK Setup.exe
4) In the screen that pops out - Double click everything so it has a red X except for green check mark next to "USB Driver Package"
( which means just have to install the USB Driver)
5) On you Nexus 1 - Navigate to 'Settings -> Application -> Development -> enable USB debugging'.
6) Connect your nexus one to the computer through the USB cable provided with your phone.
7) Wait for the PC to install the device driver.
- If it doesn't then --- 'New Hardware Found -> Point the install location to C:\android-sdk-windows\usb_driver\'
8) Once the driver is found and installed ; On your computer open a command window. 'start -> Run -> type 'cmd' -> hit 'ENTER'.
9) On the command screen: Type "cd c\" ; Hit 'ENTER' key
10) Then Type: "cd C:\android-sdk-windows\tools" ; Hit 'ENTER' key
11) Type: adb devices ; Hit 'ENTER' key
- It should say something similar to "HT123P123456 device" (this is your phone's serial number).
- If it says "cannot find" or "invalid path" etc, make sure you're typing *exactly* what the green text above says.
- If it says something else, try to reinstall the USB Driver package and restart your PC.
12) If it works, your PC is correctly recognizing the phone. Continue on to the next step!
UNLOCK BOOTLOADER
1) Turn off your nexus one.
2) Press and hold the trackball and also press the power button ( while still holding the trackball pressed).
3) A white screen with three droids at the bottom appears.
4) A RED background highlights "FATSBOOT" which changes to "FASTBOOT USB" in a second or two.
5) Now, On your computer open a command window. 'start -> Run -> type 'cmd' -> hit 'ENTER'.
6) On the command screen: Type "cd c\" ; Hit 'ENTER' key
7) Then Type: "cd C:\android-sdk-windows\tools" ; Hit 'ENTER' key
8) Now on your computer; TYPE: fastboot devices
- It should say something similar to "HT123P123456 fastboot" (this is your phone's serial number). If it doesn't say this, something is wrong.
- If you are typing fastboot devices and it just returns a blank line or ???????? (ie Windows 7 64-bit users), try using USB drivers in the PdaNet install:
http://www.junefabrics.com/android/download.php
9) If it shows the device number , then you are set to go.
10) On the command window opened previously ; TYPE: fastboot oem unlock
11) Read the screen carefully. If you click on unlock it will wipe all your DATA!! and also Unlock your phone .
12) Use the volume control keys on your nexus one to switch options and then press the power key to select the option.
13) An "unlocked padlock" appears while booting and YAY!! you are unlocked!!!!
14) Shut down your phone and boot into the boot loader ( Trackball pressed + power button )
INSTALL(FLASH) RECOVERY
1) Download the latest Amon_RA's recovery img from here
2) move it to "C:\android-sdk-windows\tools" .
3) On your computer open a command window. 'start -> Run -> type 'cmd' -> hit 'ENTER'.
4) On the command screen: Type "cd c\" ; Hit 'ENTER' key
5) Then Type: "cd C:\android-sdk-windows\tools" ; Hit 'ENTER' key
6) On you computer's command window -- Type: fastboot devices and make sure your device's number is showing up.
7) On you computer's command window -- Type: fastboot flash recovery recovery-RA-nexus-v1.7.0.img
8) It should say: sending 'recovery' (3962 KB)... OKAY . . . . . writing 'recovery'... OKAY This should take a few seconds.
9) If flashing the recovery was successful, use the menu options to boot directly into recovery, or restart your phone normally.(without going to the bootloader screen).
Rooting
1) Download the nexus-addon-0.1-signed.zip from here.
2) Copy the file onto your SD card. ( It should be in the root folder of your SD card i.e don't put it under any directories).
3) Shut down your nexus one
4) Boot into the boot loader ( Trackball pressed + power button )
5) Press the power button once ( quickly and for a very short time ).
6) The screen changes and you move to the Fastboot screen.
7) Do Not do anything for about 8-10 seconds. It scans for some files and returns to the "FastBoot Screen"
8) Now use the "volume down" button to select "Recovery" and press the power button.
9) Do this step only if you didn't use Superboot: Use trackball -> "Flash zip from from sdcard" -> nexus-addon-0.1-signed.zip
- If you get a Triangle with a ! in the middle alongside an Android for 5+ minutes, you MAY have to remove battery and re-flash recovery (I had to do this once.) (Make absolutely sure that nothing is happening on your phone, as removing the battery when it's doing something can cause a brick.)
- Alternatively, try the optional Superboot method, and then re-flash Amon_RA's recovery image.
10) Select Reboot.
Phew .. that was hard ... but here comes the best part !!!
INSTALL FRF50 with Radio
1) Download the FRF50 with Radio zip file from here (Paul's FRF50 ROM).
2) Copy the file onto your SD card. ( It should be in the root folder of your SD card i.e don't put it under any directories).
3) Rename it to update.zip and make sure it's not "update.zip.zip". ( if you have the extension names off ).
4) Shut down your nexus one.
5) Boot into the boot loader ( Trackball pressed + power button )
6) Press the power button once ( quickly and for a very short time ).
7) The screen changes and you move to the Fastboot screen.
8) Do Not do anything for about 8-10 seconds. It scans for some files and returns to the "FastBoot Screen"
9) Now use the "volume down" button to select "Recovery" and press the power button.
10) The phone now boots into Recovery.
11) Use your phone's "Trackball" to Navigate and press the "trackball" to execute the selection.
12) Run the following
a) Backup/Restore -> Nand backup
b) Wipe -> Wipe data/factory reset
c) Wipe -> Dalvik Cache
13) Then press the "volume down" button to return to the main recovery screen.
14) Now , select "Flash zip from sdcard" and in the next screen select the "update.zip" file.
15) You get an "install completed" message after about 15-20 seconds.
16) Reboot and you are into the wonderful world of "FROYO".
FRF50 -> FRF83
1) Ok, now I think you are already enjoying your delicious dessert. Let's add some strawberries to it.
2) Download the PAUL modified FRF50 -> FRF83 zip file from HERE.
3) Connect your phone to the USB cable and mount the card.
4) Remove the existing update.zip file from the SDcard.
5) Copy the downloaded FRF83 file into the SDcard's root folder and rename it to "update.zip".
6) Shut down your nexus one.
7) Boot into the boot loader ( Trackball pressed + power button )
8) Press the power button once ( quickly and for a very short time ).
9) The screen changes and you move to the Fastboot screen.
10) Do Not do anything for about 8-10 seconds. It scans for some files and returns to the "FastBoot Screen"
11) Now use the "volume down" button to select "Recovery" and press the power button.
12) The phone now boots into Recovery.
13) Select "Flash zip from sdcard" and in the next screen select the "update.zip" file
14) Wait for the most annoying 15-25 seconds and reboot.
15) VOILA , you are on the latest and greatest android update for Nexus one.!!!!
I think I'll wait, but excellent work on putting all of that together!
Thanks for the step by step. I believe another approach is to not root (just unlock the bootloader) and to flash back to the TMO ROM and use the leaked official updates. I'm trying to determine which to do.
AvengerBB said:
Thanks for the step by step. I believe another approach is to not root (just unlock the bootloader) and to flash back to the TMO ROM and use the leaked official updates. I'm trying to determine which to do.
Click to expand...
Click to collapse
As far as the info goes from this forum .. I came to know that unlocking the bootloader will void warranty. SO I felt that it's worth rooting the phone after unlocking it as we have advantages like Titanium backup and a lot more ...
I did a similar procedure, flashing my phone to ERE54B--->ERE27-->FRF50-->FRF83
I unlocked the bootloader/rooted in the process, but in the end I end.. I installed FRF50--FRF83 to my unrooted nexus one on ATT.
I wish I had tried applying the ERE27 original ROM to my phone with a locked bootloader, I don't know if it would of worked or not.
Either way, I am an ATT Nexus one on FRF83. It's quite nice
Nice instructions, good job compiling!
However, there is no need to flash FRF50 first, and then FRF83. You can just flash Paul's FRF83, and the radio separately.
AvengerBB, a prerequisite of Amon_RA's recovery image is a rooted phone. I am not sure exactly why it requires root, though.
jmorgan6 said:
I wish I had tried applying the ERE27 original ROM to my phone with a locked bootloader, I don't know if it would of worked or not.
Click to expand...
Click to collapse
It wouldn't have.
Just to clarify for me..
I understand unlocking bootloader is what 'voids' your warranty is required to root. It is also not possible to 'undo'.
Is having a 'rooted' phone what prevents you from getting OTA updates, or is having an unlocked bootloader?
If you have a phone with an unlocked bootloader, but not rooted... does google/android OS know any different? (Not warranty claims, but for S/W updates)?
Basically, if/when the ERE54B-->2.2 Update goes official, can I flash back to ERE54B and get the 'original' upgrade intended for my phone if I unroot it. Or will I from here on out have to manually update my phone?
Would you guys PLEASE take a look at this and tell me if you are having this trouble too!
nice work, very well documented, glad someone did this. Thank you.
I think I will continue to wait out the official OTA, but if I get antsy this weekend I know where to come for instructions.
stick this thread!
I have a rooted and bootloader unlocked AT&T version nexus one and I have already installed the FRF50 WITHOUT the radio. Should I go back and reinstall FRF50 with the radio before upgrading to FRF83? On by current build the phone sometimes doesn't reconnect to AT&T service once it has lost service and I need to restart the phone. Does Paul's FRF50 ROM have a radio that supports AT&T? Kinda a noob, sorry. Thanks in advance for the help.
andrewluccio said:
I have a rooted and bootloader unlocked AT&T version nexus one and I have already installed the FRF50 WITHOUT the radio. Should I go back and reinstall FRF50 with the radio before upgrading to FRF83? On by current build the phone sometimes doesn't reconnect to AT&T service once it has lost service and I need to restart the phone. Does Paul's FRF50 ROM have a radio that supports AT&T? Kinda a noob, sorry. Thanks in advance for the help.
Click to expand...
Click to collapse
You need to flash the newer 12_7 radio. The radio image remains the same for ATnT or T-mobile, the actual frequencies are decided by hardware. No need to re-flash FRF50 - just flash the new radio from here - http://n0rp.chemlab.org/android/nexus/radio-4.06.00.12_7.img
You can use "fastboot flash radio radio...img" command to flash it. After flashing new radio, flash FRF83. It is highly recommended that you flash only compatible OS and radio versions.
Man
I have followed all the steps but when I go to flash the update from the sdcard it gives me the an error that says there is no signature and install aborted. What could this be from? I have tried those steps again and again. Please help.
jmorgan6 said:
Just to clarify for me..
I understand unlocking bootloader is what 'voids' your warranty is required to root. It is also not possible to 'undo'.
Is having a 'rooted' phone what prevents you from getting OTA updates, or is having an unlocked bootloader?
If you have a phone with an unlocked bootloader, but not rooted... does google/android OS know any different? (Not warranty claims, but for S/W updates)?
Basically, if/when the ERE54B-->2.2 Update goes official, can I flash back to ERE54B and get the 'original' upgrade intended for my phone if I unroot it. Or will I from here on out have to manually update my phone?
Click to expand...
Click to collapse
You can't re-lock the bootloader without being very lucky, you need an S-OFF SPL. Just having an unlocked bootloader won't effect your ability to get OTA updates, it's custom ROMs and recoveries that do that.
If you're going through all that trouble, just use Paul's superboot to FRF83.
Finally got it to work! It didn't fix my video recording bug though. When I switch from camera to video it just freezes and reboots. Did they ever find a workaround for this? I would appreciate the help.
Shouldn't need a work around, mine doesn't suffer from it.
rohandhruva said:
You need to flash the newer 12_7 radio. The radio image remains the same for ATnT or T-mobile, the actual frequencies are decided by hardware. No need to re-flash FRF50 - just flash the new radio from here - http://n0rp.chemlab.org/android/nexus/radio-4.06.00.12_7.img
You can use "fastboot flash radio radio...img" command to flash it. After flashing new radio, flash FRF83. It is highly recommended that you flash only compatible OS and radio versions.
Click to expand...
Click to collapse
Arent you guys facing troubles with this radio?
My gps is innacurate... i think that is because of the radio image!
If with the oficial froyo it does not is fixed i will flash back my 4.04 radio!
Take a look at this to read about my trouble please!
Need some help. Everything worked up to this point.
INSTALL FRF50 with Radio
1) Download the FRF50 with Radio zip file from here (Paul's FRF50 ROM).
2) Copy the file onto your SD card. ( It should be in the root folder of your SD card i.e don't put it under any directories).
3) Rename it to update.zip and make sure it's not "update.zip.zip". ( if you have the extension names off ).
4) Shut down your nexus one.
5) Boot into the boot loader ( Trackball pressed + power button )
6) Press the power button once ( quickly and for a very short time ).
7) The screen changes and you move to the Fastboot screen.
8) Do Not do anything for about 8-10 seconds. It scans for some files and returns to the "FastBoot Screen"
9) Now use the "volume down" button to select "Recovery" and press the power button.
10) The phone now boots into Recovery.
11) Use your phone's "Trackball" to Navigate and press the "trackball" to execute the selection.
12) Run the following
a) Backup/Restore -> Nand backup
b) Wipe -> Wipe data/factory reset
c) Wipe -> Dalvik Cache
13) Then press the "volume down" button to return to the main recovery screen.
14) Now , select "Flash zip from sdcard" and in the next screen select the "update.zip" file.
15) You get an "install completed" message after about 15-20 seconds.
16) Reboot and you are into the wonderful world of "FROYO".
Click to expand...
Click to collapse
I didn't get an "install completed" message. Instead it says, "Reboot via vol-up+vol-down or menu to complete installation." Then when I reboot it goes to the android falling out of the box image, and then boots back into recovery. I can restore with the nand backup just fine, but this method doesn't seem to work for me. I believe it's the damn radio upgrade that is causing the problems because right before the reboot it says "Writing radio image...". Anybody else experienced this?
thmst30 said:
Need some help. Everything worked up to this point.
I didn't get an "install completed" message. Instead it says, "Reboot via vol-up+vol-down or menu to complete installation." Then when I reboot it goes to the android falling out of the box image, and then boots back into recovery. I can restore with the nand backup just fine, but this method doesn't seem to work for me. I believe it's the damn radio upgrade that is causing the problems because right before the reboot it says "Writing radio image...". Anybody else experienced this?
Click to expand...
Click to collapse
Have you tried doing "Reboot phone" after it boots back into recovery?
as easy as every forum makes it seem to do a nandroid back up, i found these instructions. just have a question on them:
1. Boot into Recovery Mode* by turning off your device then powering it on while holding Power+Home.
2. If you should get a triangle icon with an exclamation point, hit ALT + L to get to the menu.
3. Once in Recovery Mode, select "Create Nandroid backup." This will create a folder on your sdcard named "nandroid."
4. Wait for it to complete.
Having a hero, i have no keyboard to hit ALT + L.
anyone have a link to a thread that makes nandroid backup itself easy?
kjfrost091 said:
as easy as every forum makes it seem to do a nandroid back up, i found these instructions. just have a question on them:
1. Boot into Recovery Mode* by turning off your device then powering it on while holding Power+Home.
2. If you should get a triangle icon with an exclamation point, hit ALT + L to get to the menu.
3. Once in Recovery Mode, select "Create Nandroid backup." This will create a folder on your sdcard named "nandroid."
4. Wait for it to complete.
Having a hero, i have no keyboard to hit ALT + L.
anyone have a link to a thread that makes nandroid backup itself easy?
Click to expand...
Click to collapse
Those are old, if you get the exclamation point you aren't rooted. Hold the home button while turning the phone on, then the phone will boot in recovery after that just follow the on screen menu's there very self explanatory.
If you stuck stop and post again and I'll help.
Um I don't know were u got those from but that's wrong u just power down hold home and power for like 10 or 15 seconds then ur in recovery once there choose backup& restore then hit nand backup or u can hold down the volume down key and press the power bottom this will take u to a white screen once there hit the home button and wait like 10 or 15 sec and ur recovery should show up and then just repeat what I said above for making a nandroid backup once in recovery if ur seeing a triangle with a exclamation mark I think u have to reroot again
Root-Hack-Mod-Always™
damn. im 100% positive im rooted, and all it keeps doing is showing the red triangle with the exclamation point that i cant get past.
sorry about the old directions, ive been looking everywhere for nandroid backup directions. it sounds so easy, but im running into this problem.
How are you 100% postive ur rooted I'm puzzled????
Root-Hack-Mod-Always™
a friend of mine emailed me the qr code for universal androot, i followed the instructions, he then said to install busy box which gave me super user permission, and busybox itself recognized that my phone is rooted. im assuming its correct?
kjfrost091 said:
a friend of mine emailed me the qr code for universal androot, i followed the instructions, he then said to install busy box which gave me super user permission, and busybox itself recognized that my phone is rooted. im assuming its correct?
Click to expand...
Click to collapse
You goto adb and type adb shell. and then type su do you see a # or $ in the prompt. If you see a pound you have root you just need to flash an custom recovery.
Yup ur right have u set up adb???
Root-Hack-Mod-Always™
i have not set up adb, (and of course im a noob) do you have a link to show me how? i know youve run into probably tons of noobs that need annoying info, so i dont want to waste your time.
Dude no prob I can't paste I'm mobile no one helped me wen I first started either so I'm glad to any ways I just Googled how to setup adb on whatever OS ur using prepare for some reading time though or if you search xda I'm 100% sure u can find a guide for it to make it real simple once u download the sdk and the HTC sync drivers let me know but your gonna have to either Google or XDA search I just left my home ill b mobile for a while but ill b on here if you run into any problem and if I'm not these people on here are super friendly especially for people just starting out good luck
Root-Hack-Mod-Always™
i just rooted my phone 10 minutes ago and now i cant get into recovery to restore the back up i made. the only recov i can get into is H-boot then from there it just gets stuck at the htc white screen.. did i brick it ???? i cant find any recent posts on this please help AGAIN sorry
stevo760 said:
i just rooted my phone 10 minutes ago and now i cant get into recovery to restore the back up i made. the only recov i can get into is H-boot then from there it just gets stuck at the htc white screen.. did i brick it ???? i cant find any recent posts on this please help AGAIN sorry
Click to expand...
Click to collapse
So you are at the white screen that says hboot? It should be the second option on that screen saying recovery, use the volume keys to move to it, then use the power button to select it.
Sent from my Xoom using Tapatalk
you can boot into your rom and then reflash recovery, I flash mine a few times as rarely its there the first time
Grab the PC36IMG.zip file from the Amon Ra thread and put it on your SD card. Boot to the bootloader, let it find the file, and update to flash the amon ra recovery. I hate clockworkmod. It's never been as consistent for me as Amon Ra.
you wiped your boot or system partition didn't you?
hold volume down while turning your phone on and it should bring a menu with three android guys at the bottom, once there use the volume buttons to select recovery and then push power to select it. That will get you into the recovery where you can flash a ROM. If it doesn't let you get into the recovery from there and you still have the autoroot folder on your computer you can run the file 'FlashZip' script and tell it to flash the SprintLovers_AmonRA... file. Just put it in fastboot mode before hand by selecting fastboot instead of recovery from the hboot
bwcorvus said:
So you are at the white screen that says hboot? It should be the second option on that screen saying recovery, use the volume keys to move to it, then use the power button to select it.
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
i did that and i just takes me to a black screen with a triangle in it
xHausx said:
you wiped your boot or system partition didn't you?
hold volume down while turning your phone on and it should bring a menu with three android guys at the bottom, once there use the volume buttons to select recovery and then push power to select it. That will get you into the recovery where you can flash a ROM. If it doesn't let you get into the recovery from there and you still have the autoroot folder on your computer you can run the file 'FlashZip' script and tell it to flash the SprintLovers_AmonRA... file. Just put it in fastboot mode before hand by selecting fastboot instead of recovery from the hboot
Click to expand...
Click to collapse
you gotta help me man!!!! how do i flash just the recovery in auto root commands??????
stevo760 said:
you gotta help me man!!!! how do i flash just the recovery in auto root commands??????
Click to expand...
Click to collapse
It sounds like you have the old debug firmware installed, the screen with the red triangle is the stock recovery. Pushing vol up + power in it should bring up a menu although there is nothing in there that is of use except reboot.
With the triangle showing on your phone run the FlashZip script and it should reboot you in to the bootloader, once it does that hit enter when it warns you about your bootloader being unlocked and it will give a list of different PC36IMG files. You'll want to flash the one that says SprintLovers-AmonRA to make sure everything is up to date.
xHausx said:
It sounds like you have the old debug firmware installed, the screen with the red triangle is the stock recovery. Pushing vol up + power in it should bring up a menu although there is nothing in there that is of use except reboot.
With the triangle showing on your phone run the FlashZip script and it should reboot you in to the bootloader, once it does that hit enter when it warns you about your bootloader being unlocked and it will give a list of different PC36IMG files. You'll want to flash the one that says SprintLovers-AmonRA to make sure everything is up to date.
Click to expand...
Click to collapse
in the triangle recovery screen no button will bring up any menu... i think im ****ed man this blows
stevo760 said:
in the triangle recovery screen no button will bring up any menu... i think im ****ed man this blows
Click to expand...
Click to collapse
what did it say when you ran the FlashZip script?
stevo760 said:
in the triangle recovery screen no button will bring up any menu... i think im ****ed man this blows
Click to expand...
Click to collapse
i can do it in fast boot mode but as soon as i select number 1 and press enter the dos screen goes away and nothing happens
stevo760 said:
i can do it in fast boot mode but as soon as i select number 1 and press enter the dos screen goes away and nothing happens
Click to expand...
Click to collapse
k, it's not working right then. Can you do me a favor and use the StartShell file then run it from there. If it fails again right click -> select all and then copy and paste it.
To run it from the dos prompt just type flashzip and enter
xHausx said:
k, it's not working right then. Can you do me a favor and use the StartShell file then run it from there. If it fails again right click -> select all and then copy and paste it.
To run it from the dos prompt just type flashzip and enter
Click to expand...
Click to collapse
[1] C:\Documents and Settings\Steven Cirocco\Desktop\AutoRoot_v2.3\res\PC36IMG-S
printLovers-AmonRA_2.3-hausmod.zip
[2] C:\Documents and Settings\Steven Cirocco\Desktop\AutoRoot_v2.3\res\PC36IMG_A
monRA-v2.3-hausmod.zip
[3] C:\Documents and Settings\Steven Cirocco\Desktop\AutoRoot_v2.3\res\PC36IMG_U
D.zip
[4] Cancel
Type a number and press Enter/>1
ERROR: File 'C:\Documents' does not exist!
C:\Documents and Settings\Steven Cirocco\Desktop\AutoRoot_v2.3>
xHausx said:
k, it's not working right then. Can you do me a favor and use the StartShell file then run it from there. If it fails again right click -> select all and then copy and paste it.
To run it from the dos prompt just type flashzip and enter
Click to expand...
Click to collapse
if you can fix this world of **** im in im donating for sure dude
ok, I see what it's doing. Copy and paste the following into the prompt to do it manually
Code:
fastboot oem rebootRUU
Code:
fastboot flash zip res\PC36IMG-SprintLovers-AmonRA_2.3-hausmod.zip
then once it finishes...
Code:
fastboot reboot
xHausx said:
ok, I see what it's doing. Copy and paste the following into the prompt to do it manually
Code:
fastboot oem rebootRUU
Code:
fastboot flash zip res\PC36IMG-SprintLovers-AmonRA_2.3-hausmod.zip
then once it finishes...
Code:
fastboot reboot
Click to expand...
Click to collapse
it says sending zip with blinking cursor and no status meter on my phone but it does say htc
stevo760 said:
it says sending zip with blinking cursor and no status meter on my phone but it does say htc
Click to expand...
Click to collapse
give it a second, it's a big file
xHausx said:
give it a second, it's a big file
Click to expand...
Click to collapse
ok it finished it rebooted and now its at htc quality brilliant screen for 2 minutes and counting
When I experienced the red triangle and inability to boot into recovery, following step #10 of the link below pushed a temporary recovery onto the phone.
http://forum.xda-developers.com/showthread.php?t=829045
You still need to flash (by some means), a permanent recovery.
You can do so using either the PC36IMG.zip method, adb shell, or through console.
holy f !!!!! you developin son of *****!!!!! you are the man!!!!! you literally just saved my life i just got this phone yesterday and my girlfreind is on her way to kill me... so now what do i do about recovery and am i still rooted... and how do i give you money???
Edited May 16 2012
Hi all,
Due to confusion and scared people I have decided to post simple instructions on how to unlock the bootloader on GB 2.3.4. I just received my Bell Atrix 4G, unlocked it for rogers and then rooted and unlocked the bootloader. I was confused by the pudding instructions, so I decided to recreate them In my own wording.
I take no responsibility for anything that happens to your phone or your heart stopping while you wait for your phone to reboot or if it is stuck on moto screen etc...
Credit for original tutorials go to the2dcour, romracer, Nottach, Faux123 and the others for all of their hard work.
Requirements:
1.Create a folder on your desktop named motounlock
2.Go here: forum.xda-developers.com/showthread.php?t=1136261
Scroll down to where it says "RSDLite/Windows Drivers/Sbf_flash"
UPDATE: Download RSDLite from here : http://www.multiupload.com/T6NOEBKKLO . If you need x64 bit Drivers use the other link. thanks AnguishedEnd!
download the first two files for windows (RSDLite 5.5 link, x64 Windows drivers)
download the third file for linux/mac
3.Scroll until you see the big word "Unlock"
where it says "Unlocker only SBFs" download the second file UNLESS you are on ATT.
4. Scroll down to the word "Root" and download 'Fastboot' for your OS
5.unzip all of the files you just downloaded into the motounlock folder on your desktop
6. open the folder, install RSDLite, and afterwards install the Drivers.
Then follow these instructions
Power Down your atrix
Take out your microSD card and SIM card for the flashing process
While turning the phone on, hold the Volume Up button until it acknowledges RSD. Your device will say “Starting RSD protocol support”
Run “RSD Lite” on your computer
Press the “. . .” button next to the box labeled “Filename”
Navigate to your desktop and open the motounlock folder and select the file named intl-fix-try1.sbf ( IT WILL BE DIFFERENT IF U ARE DOING THIS FOR ATT)
Plug your device into your computer. RSD Lite should recognize your device and say “Model: NS Flash Olympus” and “Connected…” The acronym 'NS' may be different for your device people!!
Press the “Start” button. The Flash actually failed for me, wait for it to complete to 100% it may FAIL or PASS! just make sure it gets to 100% leave your phone sitting for about 10 minutes AFTER RSD SAYS FAIL/SUCCESS.
If nothing is happening after 10mins, perform a battery pull. Power the phone on while pressing vol-down. “Fastboot” Will show up on screen. DONT PLUG IT IN YET. Press volume up and let your phone sit. You will see “Starting Fastboot protocol support" LEAVE IT UNPLUGGED
press the windows key + R on your computer, type cmd and press enter
command prompt will open. type cd C:\users\YOURNAME\desktop\motounlock press 'enter'
Plug your device back into usb now
back in your command prompt window type "fastboot oem unlock" no quotes
You will now receive a warning along with a unique device ID
Type the following commands using your unique device ID (the numbers in the command prompt) in place of the ####
fastboot oem unlock ####
fastboot reboot
your moto will reboot. UNLCOKED!!!!!!!!!!!!!
Proper Recovery:
1. After your bootloader unlocked go to this link http://forum.xda-developers.com/showthread.php?t=1204500
2. Scroll down to where it says "ALL USERS" and download your favourite colour. (NOT THE ZIP VERSION) Place it in the motounlock folder that you have on your desktop.
3. Press the windows key + R on your computer, type cmd and press enter
4. A Command prompt will open. type cd C:\users\YOURNAME\desktop\motounlock press 'enter'
5. type "fastboot devices" Press Enter.
5b. type "fastboot erase recovery" Press Enter.
5c. type "fastboot flash recovery recovery-atrix5.img" Press Enter.
Wait for the command prompt to say : "writing 'recovery'... OKAY ['The amount of seconds it took here']"
5d.type "fastboot reboot"
DO NOT FORGET TO DO THIS PART: After the install of RomRacers recovery boot up your phone. Open up your favourite file browser (I used Astro file manager to do this ) and navigate to /system/etc/ and delete the file called 'install-recovery.sh'
You will be set 100% !
Installing a custom ROM (Any custom rom will work as long as it has unified kernel/Faux Kernel)
MOST ROMS WILL COME PRE-ROOTED! Just saying, to avoid confusion.
I will be using Nottach's Darkside ROM as an example, because Cyanogenmod does not have features included with original moto rom (this one is way more NOOB friendly) But this is COMMON PROCEDURE for almost every rom so be sure to follow this for whatever ROM you want to use.
1. Go here http://forum.xda-developers.com/showthread.php?t=1222108
2. Scroll down to where it says 'DOWNLOADS' and download the most current version.
3. When it is finished downloading you will have a ZIP file named something like "TheDarkSidev2.8.0-Wipe.zip"
4. Plug your phone in to your computer and transfer that file to your INTERNAL MEMORY.
5. MAKE SURE YOUR PHONE HAS DECENT CHARGE! I would say at least 50 percent. 70+ is recommended, I have done it with 40 + though.
6. Power Down your Phone.
7. Hold The POWER Button + VOL DOWN. DONT PRESS VOLUME UP WHEN YOU SEE FASTBOOT! Instead...
8. After fastboot shows up click volume down until " Android Recovery " shows up, about 7 down clicks. THEN press volume up.
9.
***FIRST TIME ROM FLASHERS ONLY!!!!!!***
WE ARE GOING TO BACKUP YOUR ORIGINAL ROM SO THAT IF YOU EVER DERP YOU WIL ALLWAYS HAVE A SOLID BACKUP
Press VOLUME DOWN and go to backup and restore. Press the POWER BUTTON
Press the POWER button on backup
Select where you want to put your backup (internal or external memory)
Backup INCLUDING WEBTOP! (if you ever think you will use it)
Wait for it to finish.
***********************************
10. Ok now that you are in android recovery you have to do a few things before flash.
a. Scroll down to "wipe data/factory reset" PRESS POWER. say yes to EVERYTHING until it goes back to the main screen.
b. scroll down to "wipe cache partition" PRESS POWER. say YES. Wait for return to main menu
c. Scroll down to"advanced", click "wipe dalvik cache" Go back to "advanced", "wipe battery stats
11. At the main menu, Scroll to "install Zip from SDcard" Press POWER.
12.scroll down to "choose zip from internal sdcard"
13. select the ZIP file that you saved to your INTERNAL memory. If you're using darkside the file name is "TheDarkSidev2.8.0-Wipe.zip"
14. Scroll down to "YES - install TheDarkSidev2.8.0-Wipe.zip" Press POWER
15. Let your phone work its magic!
16. When it is finished installing, you will be returned to the recovery main menu.
17. click "reboot system now"
18. Let it boot! This can take anywhere from 10 seconds to 5+ MINUTES! if you dont see it move from the "unlocked" screen after 10 minutes Perform a battery pull and power on again. If it hangs then all you have to do is go into recvoery click "backup and restore" and restore your original ROM. Or like me, have one of every kind of ROM on your storage in case I feel the need to change it on the go!
19. YOUR PHONE HAS BEEN SUCCESSFULLY TURNED INTO A FULLY OPEN DROID Pat yourself on the back and have a drink to your accomplishments . We on XDA knew you could do it!
Some solutions to issues:
As ar31791 said,
Anyone having issues not being able to boot into CWM recovery after flashing it (such as seeing android guy with exclamation mark):
Delete or rename /system/etc/install-recovery.sh AND /etc/install-recovery.sh I renamed mine to bkup.install-recovery.sh in case i ever wanted to use them again for some reason.
/etc/install-recovery.sh will automatically be placed in /system/etc if /system/etc/install-recovery.sh is not found on boot.
So, you must delete or rename both, THEN INSTALL CWM recovery.
rename the files using ROM Toolbox's root explorer as some file explorers will not give you the proper access levels to delete or rename the files correctly.c
Hope this helps it worked for me. I was afraid of a brick because nobody clarified the steps that were involved in RSDLite. It may be nerve racking, but it does work!! Enjoy and thanks again to the2dcour, romracer, Nottach, Faux123 and anybody else who has helped in the scene that I didnt have a chance to mention. PM me if I forgot you!
Oh, and just to let everybody know when your bootloader is successfully unlocked it will say unlocked at the top left of your screen everytime you turn it on. just wait, this is normal.
OMG thank you so much tayshun!! I just spent 2 hours reading through that pudding post mess trying to figure out how to do this for a 2.3.4 bell atrix....
I was very nervous about trying something without clear directions in case I brick my phone. You're a lifesaver
noobler said:
OMG thank you so much tayshun!! I just spent 2 hours reading through that pudding post mess trying to figure out how to do this for a 2.3.4 bell atrix....
I was very nervous about trying something without clear directions in case I brick my phone. You're a lifesaver
Click to expand...
Click to collapse
I understand your grief hahaha. Feel free to press the thank you button at the bottom of my post. I'm trying to get a good reputation around here as I am going to school for programming and I will probably be in these dev forums daily to get help cooking Roms!
Has anybody else had success with my simplified instructions? Results?
this instructions seem simple
http://forum.xda-developers.com/showthread.php?t=1182871
what do you think?
sanriver12 said:
this instructions seem simple
http://forum.xda-developers.com/showthread.php?t=1182871
what do you think?
Click to expand...
Click to collapse
Are you sure it works on a Bell/Int'l Atrix?
Thanks heaps for the instructions Just used them to unlock a Telstra Atrix which I updated to 2.3.4 this morning! Worked a treat.
---------- Post added at 12:06 PM ---------- Previous post was at 11:58 AM ----------
Maybe i spoke to soon...I just noticed it has reset to factory defaults. Not a big deal as I already backed everything up but i certainly wasn't expecting it!
What about android version 2.2.2 and system Version.4.2.11.MB860.Retail.end.FR
Build: OLYEM_ U4_2.1.1
IT'S bell phone atrix 4g unlocked and running on Rogers
In just afraid of ruining it,, I've bricked a vibrant by just updating it from Samsung utility which is weird.
Thanks
Sent from my HTC-A510a using xda premium
timfoote said:
Maybe i spoke to soon...I just noticed it has reset to factory defaults. Not a big deal as I already backed everything up but i certainly wasn't expecting it!
Click to expand...
Click to collapse
you would have expected this if you had informed yourself as you should, before performing this kind of procedure on your phone.
Worked perfectly for me. My phone wouldnt complete the flash, so I went into CMD and unlocked it.
I've been trying to do this before, and many failed attempts.
So thank you.
worked
Fantastic summary.
Worked like a charm.
Bell Atrix with retail updates.
Thanks a million!
...Damnit, still can't remove Kobo; wtf!
Super guide
Thanks for the very clear instructions. Worked first time. The one thing that always seemed ambiguous to me was the memory fix. Do we need to apply it?
xeidy said:
What about android version 2.2.2 and system Version.4.2.11.MB860.Retail.end.FR
Build: OLYEM_ U4_2.1.1
IT'S bell phone atrix 4g unlocked and running on Rogers
In just afraid of ruining it,, I've bricked a vibrant by just updating it from Samsung utility which is weird.
Thanks
Sent from my HTC-A510a using xda premium
Click to expand...
Click to collapse
I also have an unlocked bell atrix 4g on rogers. If you dont have 2.3.4 you would have to update your phone with the bell original software. It wont take away your unlock as unlocks are permanent. after you upgrade follow this guide to unlock the Bootloader and feel free to use custom roms!
nabicat said:
Thanks for the very clear instructions. Worked first time. The one thing that always seemed ambiguous to me was the memory fix. Do we need to apply it?
Click to expand...
Click to collapse
well after I unlocked my bootloader I installed romracers CWM and DarkSide v2.1 to my phone. No issues with ram so far. I dont know if you intend on installing customs ( I assume so because what other reason would you have to unlock the bootloader? lol) but after the install my ram readouts seemed correct
Yes, you're correct. I checked available memory and its over 800 mb, so the fix must be in there.
Cheers
Working very well with Bell Atrix.
Thanks for big help.
Wondering if this instruction works with Hong Kong's ME860 2.3.4 also?
I'd love to try this!
MrJcc said:
Wondering if this instruction works with Hong Kong's ME860 2.3.4 also?
I'd love to try this!
Click to expand...
Click to collapse
I'm not sure if it works with hong kong version. If you check the link that I posted, it leads to a thread on here called international house of pudding. in that thread at the beginning it says that " China version ??: DANGER: Brick after OTA 2.2.2" So you would definitely have to ask someone around the forums or search to see if somebody has done it successfully
It is possible to remove the unlocked during the boot?
Sent from my MB860 using XDA App
MoFo will NOT work on 5.1 so do NOT upgrade to the 5.1 bootloader or partition table if you want to use MoFo.
This method involves purchasing a piece of software named mofo.exe that allows you to flash a modified, unsigned system image to your device despite its locked bootloader. The cost is $20. Links to the modified images for the XT1096 and XT1097 are found in the OP of the MoFo support thread:
http://forum.xda-developers.com/general/paid-software/mofo-root-turbo-t3064404
This Method Does Not Disable Write Protection. Please read the following post if you don't know what that means:
http://forum.xda-developers.com/showpost.php?p=60412113&postcount=292
This Method Trips the Root Checker and Your qe Will Convert to qe 1/1 Permanently! What this means is that if you boot your phone into recovery, you will see qe 1/1, which means you are currently running modified software. The qe will stay at 1/1 even if you flash back to stock.
1. Check Your Software Version and Enable USB Debugging
Go to Settings -> About Phone and read your Android Version – it should say 5.0 on the XT1096 and 5.0.2 on the XT1097. If not, and it says 4.4.4, you are still on 4.4.4 and as long as you have not modified your system by flashing using mofo.exe, you should still be stock and can take the 5.0 or 5.0.2 OTA.
If you haven’t already, go into Settings -> About Phone and click on Build Number repeatedly until you get the message you are developer now (or something like that). Then hit the back button and you will see that the Developer Options now appear. Click on Developer Options and check USB Debugging.
2. Install Motorola Device Manager (MDM) and Drivers to Your Computer
You can download MDM and the drivers here:
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Install MDM on your computer after you download it. MDM should install the drivers.
3. Download Copies of Adb and Fastboot
You can get these from the Adroid SDK but you don’t need the whole Android SDK. Root Junky has the files you need on his site here:
http://rootjunkysdl.com/?device=Adb Fastboot Files
I made a folder on my computer named c:\mx2014 and put the zip file in there. Then I unzipped it with 7-zip.
http://www.7-zip.org/
4. Download a Copy of the Official Firmware
Root Junky has a copy of the XT1096 5.0 official firmware here:
http://rootjunkysdl.com/?device=Moto X 2014&folder=Official Firmware
and the XT1097 5.0.2 fxz is here:
http://www.filefactory.com/file/1cekivswpakf/VICTARA_ATT_XT1097_5.0.2_LXE22.46-34_cid1_CFC.xml.zip
You should download it into a separate folder (I put mine in a folder named c:\mx2014\lollipop) and unzip it so if you have any problems you can flash back to stock. Place a copy of fastboot.exe, adb.exe, AdbWinApi.dll and AdbWinUsbApi.dll in the folder with the lollipop official firmware.
Also if you are planning on taking the 5.1 OTA when it is released, you would need to flash your system back to stock so it is a good to have it ready. And if you are planning to update to 5.1 via MDM I would still flash back to stock because if you don't, IME MDM will detect that you are running a modified software and will wipe your device when it upgrades you to 5.1. If you flash back to stock first, MDM will not wipe your data and sdcard when it upgrades you to 5.1.
5. Test the Drivers and Adb
Once you have completed Steps 1-3, you can test the drivers and adb. Power on your phone and after it boots, connect it to your computer via the data cable. Open a command prompt, and then navigate to the directory where you have adb and fastboot by typing:
cd c:\mx2014 (or wherever you have adb and fastboot stored)
and hitting enter. Then type:
adb devices
You should then see a prompt on your phone asking you to authorize your computer. Check always allow and click OK. Adb should show you the serial number (not the IMEI) of your device.
Now type:
adb reboot bootloader
to get into bootloader (BL) mode (aka fastboot mode).
6. Test the Drivers and Fastboot
Once you are in BL mode, double check that on your phone’s screen right above the first green line you see this:
Transfer Mode: USB Connected.
If it does not say that, go to Root Junky’s site and download the Motorola drivers and manually install them.
http://rootjunkysdl.com/?device=Android Drivers&folder=Motorola
Then type:
fastboot devices
and hit enter. Fastboot should return your device’s serial number.
7. Test Getting into Recovery and Wiping Cache
While in BL mode, scroll down to Recovery by pressing the vol dwn button to highlight Recovery. Then select Recovery by pressing vol up. You should see the dead android with a red triangle having an exclamation point in it coming out of its stomach. Then press the pwr button for a couple of seconds and then press and release the vol up button and then release the pwr button to get into the recovery menu. Use the vol dwn button to scroll to wipe cache partition and then press the pwr button to select it. You should see that the cache is being formatted.
When cache is done being wiped, the recovery menu should reappear and you should hit the pwr button to reboot into system.
8. Test That You Know How to Get Into Bootloader Mode Using Buttons
Disconnect your phone from your PC, power down your phone and then hold down volume down and then press and hold the power button. Hold both buttons simultaneously for about 4 seconds and then release the power button and then the volume down button. This should put you in Bootloader mode (aka fastboot flash mode). Alternatively, you can try pressing volume down + volume up + power and holding for about 4 seconds then releasing.
Once in BL mode, you can either hit the power button to boot back into Android or if you want to test that you know how to flash back to a stock system, complete the instructions in Step 9.
NOTE – flashing the system partition does NOT affect your apps/settings/text messages/call history, which are stored on the data partition, not the system partition. Updates to system apps since 5.0/5.0.2 was rolled out will be lost as well as any system app settings that are relevant to the updates or stored on the system partition.
NOTE – flashing the system partition does NOT affect your stored media (e.g, pictures, music, videos), which are stored on the sdcard partition, not the system partition.
9. Test That You Know How to Flash Stock System (Optional)
While in BL mode you can test that you know how to flash back to a stock system. This is optional but if you have never done it before, it is a good idea to do it IMO. When you flash a system.img, you do not lose your apps/data/texts or your media unless the app is a system app, then you will lose the updates since 5.0 was rolled out (but those can be re-downloaded from the Playstore). However, it is always a good idea to backup before you flash in case you do something wrong. I use SMS Backup and Restore to backup my texts and my photos are backed up to my Google account.
Put your device in BL mode and then connect it to your computer. Open a command prompt and navigate to where you have the stock 5.0/5.0.2 image stored on your computer. Type the following:
fastboot flash system system.img_sparsechunk1
and then hit enter to flash the first sparsechunk. Repeat for the other sparsechunks until you have flashed all 9 of them. Then boot into recovery, wipe cache and boot into system.
10. Purchase MoFo.exe
First you should go to:
http://forum.xda-developers.com/general/paid-software/mofo-root-turbo-t3064404
and read all of the information. And be sure to watch Root Junky’s video here:
https://www.youtube.com/watch?v=AXAYjbf76II&feature=youtu.be
The high level summary of what you will be doing is this:
1. Verifying that your device qualifies for purchasing mofo.exe by using MoVerify;
2. Using the link generated by MoVerify to navigate to where you can purchase mofo.exe; and
3. Purchasing and downloading mofo.exe.
11. Download, UnZip and Flash a Pre-rooted Ext4 Image
The OP of the MoFo thread has links to the pre-rooted images that are available for the XT1096 and XT1097. Once you download one of them, unzip it and move the image file to wherever you have mofo.exe stored on your computer. Put your device into BL mode and connect it to your PC. Then navigate to where mofo.exe is stored on your computer, click on mofo_gui.bat and a command window will open. Type the following at the command prompt:
mofo.exe flash [Insert name of image file here]
then hit enter. Of course you do not put brackets around the name of the image file. Once the pre-rooted image has been flashed (about 25 minutes), boot into recovery and wipe the cache then boot into system.
It may take a few seconds for the boot animation to start so don’t panic. Once the system has booted, to check that you are rooted, download root checker basic from the Playstore and confirm that you are rooted. Your device will also bypass the subscription check when you turn on WiFi hotspot.
The copy of mofo.exe that you buy is specific to your device. It cannot be used on any other device, including any warranty replacement devices that you may get in the future. But you can use it on your device as much as you want once you purchase it - unless you upgrade to a higher version of Android. If you upgrade to a higher version of Android, once that higher version of Android is supported by MoFo for your device, you can re-download mofo.exe for the higher Android version.
http://forum.xda-developers.com/showpost.php?p=60471334&postcount=432
Mofo will NEVER be updated to support 5.1 as the exploit was closed with the 5.1 bootloader.
Thank you for the guide and for the testing - its a great service to Moto X owners.
Tried going through it this morning but it appears the Mofo site is down... Anyone else having trouble?
HTC-OH_SNAP said:
Tried going through it this morning but it appears the Mofo site is down... Anyone else having trouble?
Click to expand...
Click to collapse
It is best to ask on the MoFo support thread where you are more likely to get maiko1's attention.
http://forum.xda-developers.com/general/paid-software/mofo-root-turbo-t3064404
Adding this to the OP
This is from the MoFo support forum - there appears to be some confusion about mofo.exe being device specific. The copy of mofo.exe you buy is specific to your device. It cannot be used on any other device, including any warranty replacement devices that you may get in the future. But you can use it on your device as much as you want once you purchase it.
http://forum.xda-developers.com/showpost.php?p=60471334&postcount=432
JulesJam said:
1. Verifying that your device qualifies for purchasing mofo.exe by using MoVerify;
Click to expand...
Click to collapse
might want to expand the MoVerify process with little baby steps.... the Mofo site and the Mofo forum here are again very sparse on details.
1) download and unzip the MoVerify program
2) connect you phone to computer
3) open cmd window
4) navigate to c:\mx2014 (or wherever you have adb and fastboot stored)
5) type adb devices
6) type adb reboot bootloader
7) navigate to the MoVerify folder
8) go to the folder that represents your computer's OS; let's assume Windows here
9) in the Windows folder, double click on "mofoverify_gui.bat"
10) MoVerify will open a cmd window and return back that your devices was found and give a link that looks like
https://mofo.disekt.org/verify/ [big long alphanumeric string]
11) right click anywhere in the text that is in the MoVerify cmd window and select "Select All" and then hit enter
12) open Notepad or other text editor and past the text
13) cut and paste the https address into your browser
14) follow steps to purchase Mofo
i have purchased but have not gotten farther yet... may have some more suggestions later...
Nice job putting this together. And thanks for all of your testing during the process!
is there any difference in getting into BL mode by pressing phone buttons versus connecting phone to computer and using adb?
i ask b/c there are several places in the directions above where you say "put you phone into BL mode, then connect it to your computer"
could those equally say, "connect your phone to your computer, open a cmd window, navigate to c:/mx2014, and type adb reboot bootloader to get into BL mode"
i find it is easier to go the adb route to get into BL mode, as pressing the buttons is more of a skill. if these two merhids are equivalent for this mofo process, maybe both options should be stated in the step by step.
is there any time when the button method MUST be used?
---------- Post added at 06:40 AM ---------- Previous post was at 06:33 AM ----------
one more question more out of curiousity than need to know... why does flashing back to the stock system take sequential flashing 9 "sparse chunks" (as in your step 9), whereas the mofo flash of the modified sys img is a single step?
[email protected] said:
is there any difference in getting into BL mode by pressing phone buttons versus connecting phone to computer and using adb?
Click to expand...
Click to collapse
No.
[email protected] said:
i ask b/c there are several places in the directions above where you say "put you phone into BL mode, then connect it to your computer"
Click to expand...
Click to collapse
I tend to use the buttons so that is why I wrote it up that way.
[email protected] said:
could those equally say, "connect your phone to your computer, open a cmd window, navigate to c:/mx2014, and type adb reboot bootloader to get into BL mode"
Click to expand...
Click to collapse
Yes, that would work.
[email protected] said:
i find it is easier to go the adb route to get into BL mode, as pressing the buttons is more of a skill.
Click to expand...
Click to collapse
True but if you soft brick your phone, the buttons are the only way to get into bootloader mode so best to be familiar with this way.
Did you try holding vol dwn/up and pwr simultaneously for 4 seconds and then releasing? After the lollipop update I swear that works the best for me. Let me know if that works more reliably for you - it does for me.
[email protected] said:
is there any time when the button method MUST be used?
Click to expand...
Click to collapse
If you get into a bootloop or your screen goes black and the phone is unresponsive.
[email protected] said:
one more question more out of curiousity than need to know... why does flashing back to the stock system take sequential flashing 9 "sparse chunks" (as in your step 9), whereas the mofo flash of the modified sys img is a single step?
Click to expand...
Click to collapse
Standard fastboot has a size limitation on how large of a file it can flash. So system images above that size limitation have to be broken down into smaller chunks. The version of the 5.0 Official firmware that is available to us is the one on Root Junky's site and that one is broken down into chunks.
Motorola made a modified version of fastboot, often referred to as mfastboot, that can flash larger files. However, I cannot find a version of mfastboot that can flash the 5.0 system.img (fxz) that we have available to us. If anyone has a version of mfastboot that can flash the 5.0 fxz system.img, then you could flash it. RSD Lite may be able to flash it, idk I didn't try it.
As for mofo.exe - mofo.exe has a way to avoid the size limitations of standard fastboot. Idk why standard fastboot has a size limitation in the first place. But it does and so large files have to be broken down into chunks when you use standard fastboot to flash. Mofo.exe doesn't have that same size limitation.
JulesJam said:
Once you download one of them, unzip it and move the image to wherever you have mofo.exe stored on your computer. Put your device into BL mode and connect it to your PC. Then navigate to where mofo.exe is stored on your computer, click on mofo_gui.bat and a command window will open. Type the following at the command prompt:
mofoe.exe flash XT1096_5.0_22.21.11_rooted.img
then hit enter.
Click to expand...
Click to collapse
ok. so i attempted this today
1) powered off phone
2) booted in BL mode using power and volume buttons (yes it does work very well, esp after taking the phone OUT of the case so buttons are more fully accessible) - phone screen says "AP Fastboot Flash Mode (S)" at very top
3) plugged phone into computer
4) double clicked the mofo_gui.bat to open cmd window
5) copy and pasted your text exactly
6) after hitting enter, i got the following error
======================================
'mofoe.exe' is not recognized as an internal or external command,
operable program or batch file.
======================================
methinks you have a typo in your mofo command... extra "e" that should not be there??
taking out the "e" worked and it flashed
it then said
=====================
Flashing 'XT1096_5.0_22.21.11_rooted.img' to device. Do not interrupt.
Progress: 100%
Complete. Press power to start.
=====================
i pushed the power button. it passed though a screen showing the battery level at 97%, but it has not fully booted up... black screen for like ?5 minutes!
if i hit the power button again, it still showed the battery level screen
so i pressed and held BOTH the power and volume buttons, and it booted!
when i power down, it goes to the batter level screen. and i can't seem to get into BL mode using the power and volume buttons
however, i can get to BL, then Recovery using adb, and was able to wipe cache partition
i installed and ran Root Checker Basic ... make sure you click "Grant" when it asks for permission while checking root access, or it will return a "no root access" message.
i now have wifi tethering! yahoo!
unfortuantely, the wifi hotspot toggle widgets i have tried from the Play Store seem to be able to turn hotspot on from the homescreen... i tried like the first two or three that came up when i searched for "wifi hotspot toggle"... anyone have one that works??
i am running Nova Launcher... could that be the issue with the widget not working?
otherwise, i have to go into Settings to turn it on/off... which is better than NOT having hotspot at all!
[email protected] said:
methinks you have a typo in your mofo command... extra "e" that should not be there??
Click to expand...
Click to collapse
Oops! Thanks for catching that - I will edit!
[email protected] said:
i pushed the power button. it passed though a screen showing the battery level at 97%, but it has not fully booted up... black screen for like ?5 minutes!
Click to expand...
Click to collapse
Disconnect it from your PC and then press the power button to turn it on.
[email protected] said:
when i power down, it goes to the batter level screen.
Click to expand...
Click to collapse
That is b/c it is connected to your computer. The same thing will happen if you have it plugged into the wall.
[email protected] said:
i now have wifi tethering! yahoo!
Click to expand...
Click to collapse
Yay!!!! I am at over 50GB this month from all of the downloading of images I did to test them, lol! I have never used that much before.
[email protected] said:
unfortuantely, the wifi hotspot toggle widgets i have tried from the Play Store seem to be able to turn hotspot on from the homescreen... i tried like the first two or three that came up when i searched for "wifi hotspot toggle"... anyone have one that works??
Click to expand...
Click to collapse
Go to your app drawer - there is a Mobile Hotspot icon there. Just press and hold it and drag it to your homescreen.
JulesJam said:
Go to your app drawer - there is a Mobile Hotspot icon there. Just press and hold it and drag it to your homescreen.
Click to expand...
Click to collapse
tried that... that does take you into Settings so you can turn on the hotspot.
i was hoping to get an app or widget that would turn the hotspot on/off from the home screen with one click, w/o having to do multiple clicks.
[email protected] said:
i was hoping to get an app or widget that would turn the hotspot on/off from the home screen with one click, w/o having to do multiple clicks.
Click to expand...
Click to collapse
you want a hotspot toggle then, but idk of any off hand.
JulesJam said:
Disconnect it from your PC and then press the power button to turn it on.
Click to expand...
Click to collapse
might want to just add the words "disconnect the phone fromthe usb cable" somehwere in the OP directions, you know, just for all those noobs out there that might get panicked
JulesJam said:
Disconnect it from your PC and then press the power button to turn it on.
Click to expand...
Click to collapse
After mofo runs and says complete, it says to hit the power button to restart. What you really want to do is hit the volume up button to activate the highlighted "normal bootup" option in the bootloader menu. This avoids all the weirdness if you're connected to power and using the power button.
---------- Post added at 10:24 AM ---------- Previous post was at 10:21 AM ----------
JulesJam said:
Go to your app drawer - there is a Mobile Hotspot icon there. Just press and hold it and drag it to your homescreen.
Click to expand...
Click to collapse
The image with busybox in it also enables the hotspot QS tile which works great to enable/disable the hotspot. If WiFi is on, it turns off the WiFI, then turns on the hotspot. If the WiFi was on, it remembers to re-enable it when turning the hotspot off.
mikeoswego said:
After mofo runs and says complete, it says to hit the power button to restart. What you really want to do is hit the volume up button to activate the highlighted "normal bootup" option in the bootloader menu. This avoids all the weirdness if you're connected to power and using the power button.
Click to expand...
Click to collapse
thanks! I suggest booting into recovery and wiping cache before you boot back into Android.
mikeoswego said:
The image with busybox in it also enables the hotspot QS tile which works great to enable/disable the hotspot. If WiFi is on, it turns off the WiFI, then turns on the hotspot. If the WiFi was on, it remembers to re-enable it when turning the hotspot off.
Click to expand...
Click to collapse
yeah I noticed that last night, it is great!
[email protected] said:
tried that... that does take you into Settings so you can turn on the hotspot.
i was hoping to get an app or widget that would turn the hotspot on/off from the home screen with one click, w/o having to do multiple clicks.
Click to expand...
Click to collapse
There is a Hotspot toggle in quick settings. From your lock screen, just swipe down from the top of the screen to see it. From your home screen, swipe down with 2 fingers.