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?
Let me start by saying I have already read homeiss guide for upgrading to 2.2 but when I get to where I have to type in the command line it says cannot load recovery.alt.img: what I'm asking is for full instructions from 2.1 to 2.2 no partial instructions because I've never had this much trouble flashing a rom!
Sent from my Dell Streak using XDA App
dkwelton said:
Let me start by saying I have already read homeiss guide for upgrading to 2.2 but when I get to where I have to type in the command line it says cannot load recovery.alt.img: what I'm asking is for full instructions from 2.1 to 2.2 no partial instructions because I've never had this much trouble flashing a rom!
Sent from my Dell Streak using XDA App
Click to expand...
Click to collapse
Assuming your ADB and all that is set up...and you already downloaded the Release 1 of Froyo ROM.
Install clockworkMod recovery : Do this by downloading this:
http://loadbalancing.modaco.com/download.php?url=paul/streak/2.5.0.1-streak-clockworkrecovery.zip
and follow this instruction.
Download the recovery image zip file above and extract to a directory
Put your device in bootloader mode (Unplug the device from your PC, remove the device battery, then replace it and turn device on with the camera button pressed. Select the 'fastboot' text on the top right, wait around 10 seconds then plug the device into your PC. The screen display should change to 'FASTBOOT MODE'. If it doesn't, repeat and retry
WINDOWS - double click 'install-recovery-windows.bat'
(I've had instances where I had to literally run this batch file twice to ensure it was picked up by the device.
THEN, place the update-new.zip onto your sd card
Now boot streak into recovery by shutting down and holding vol up and down as you press power, select update from .pkg option and wait for Clockwork to load. Ignore errors regarding Misc...blah, blah...
-select flash zip from sd
-choose select zip from sd and find the update-new.zip and flash it
-Afterwards, press the power button to go back until you see the optiong to reboot. Enjoy your FROYO.
when i press the shutter button to install it gives me two errors: no signature annd verification failed or something like that i never see anything thats says install from zip
dkwelton said:
when i press the shutter button to install it gives me two errors: no signature annd verification failed or something like that i never see anything thats says install from zip
Click to expand...
Click to collapse
If youre at that part it should go like this...
1) Keep both volume buttons down and then power on. Sometimes its better to power on, once you see your back, home, and menu button light up, immediately press the 2 volume buttons and keep it pressed. If successful you should be faced with the Stock Recovery Screen. This will give you 4 options, and option 2 is install Update.pkg. Ensuring there is not file on root of SD Card that is labeled Update.pkg, select Option 2.
2) If you do this it will go black and a message saying.."Android....." and then you'll be faced with Koush's custom recovery. You'll know you're in custom recovery because you have to hold the Streak upside down. (3 buttons on top and earpiece at the bottom). If you see this then you're successful and should be straightforward from there. Follow the rest of the instructions provided in my previous post.
-------
-select flash zip from sd
-choose select zip from sd and find the update-new.zip and flash it
-Afterwards, press the power button to go back until you see the optiong to reboot.
this is frustrating. ... when I did it_it went to the stock recovery and when I press shutter button it doesn't go to the custom recovery and I know I flashed it
Sent from my Dell Streak using XDA App
nevermind i finally got it
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.
Ok I've looked everywhere, maybe not well enough but I have and I can't find the answer to my question. I installed the new official 2.2 on the 10th when it came out in canada here. My phone has worked "ok" for the past 2 days. (lots of new force closes and some major lag in some spots that didn't happen in 2.1) but that's besides the point. Today i was trying to set up a new wallpaper and all of a sudden the screen started flashing on and off. I couldn't do anything to stop it except pull the battery. Now when I turn on the phone it just flashes the opening screen that says "Galaxy S blah blah". and the only way I can stop that is pull the batt. I've tried hard resetting and all that but it always gets stuck at the openning screen. Now I'm still noobish to android stuff. Was too scared to flash anything before the official so if you have any advice that involves other programs/pc i'd appreciate a point in the direction of a walkthrough.
I'd hate to have to send it in and wait the 2 months it takes samsung canada to get it back to me.
Thanks.
http://forum.xda-developers.com/showthread.php?t=732458
tried that, can't get into download mode. as soon as i plug it in it starts looping the boot screen.
canadianrider said:
tried that, can't get into download mode. as soon as i plug it in it starts looping the boot screen.
Click to expand...
Click to collapse
Look up the "jig" solution. That will be guaranteed to set your device on Download Mode.
It was the same problem with my Vibrant. Solved with JTAG controller. But you'll waste your warranty in that way. Try jig solution first
Adb?
Sent from my SGH-T959 using XDA App
ok i have android sdk/adb from when i pulled screen shots with 2.1 ... how could i use that to try and boot my phone
canadianrider said:
ok i have android sdk/adb from when i pulled screen shots with 2.1 ... how could i use that to try and boot my phone
Click to expand...
Click to collapse
option 1
METHOD 2: STUCK AT VIBRANT SCREEN:
(and are not able to use vol+ vol- methods to access downloader/recovery)
You will need the samsung ADB drivers installed for your phone as well as ADB...
ACCESS DOWNLOAD MODE
1) remove back cover and take our sim card and sd-card.
2) take out the battery
3) hold ALL 3 buttons down at the same time. (Vol +, Vol -, Power)
4) while holding down those 3 buttons put the battery back in
5) continue holding all 3 buttons until the vibrant disappears and reappears... once it reappears, release all 3 buttons
6) Setup ODIN and get it all setup and ready... (if you are flashing your phone via odin)
6) now connect your phone to your pc via USB cable
7) open a cmd prompt and navigate to the folder with ADB and type ADB REBOOT DOWNLOAD
8) Your phone will reboot into the download screen... go back to ODIN - A com port should now appear for your phone...
9) Click start and wait for your phone to do its thing
Option 2
***First you must have ROOT***
Download Terminal Emulator from the Market
open terminal emulator
**you may need to change to default android keyboard for proper inputting
1.) type "su" and press enter
a dialog box will appear asking for root access and say yes (obviously)
2.) type "reboot recovery" and press enter
at that moment, ur phone should reboot into Download Mode to load Alternate firmwares for like Eugene's Vibrant4 ROM etc......
this it what it should look like...
#su
#reboot download
Option 3
or you can download and install quick boot from the market which you then can make a shortcut to reboot into recovery with just one click
Sometimes it takes more than one try to get into download mode. I just take the battery out for a little while. Put it back in and hold only the volume up and down buttons while it is off and plug in the USB cable.
One thing though, when holding down the up and down volume buttons, it is very easy to mistakenly press the power button because it is exactly opposite of it.
I went through a lot of searching and trouble to install CM11 on my Xperia Tablet Z, and I'd like to share a tutorial I made for anyone who is also wanting to accomplish this.
All links are in Dark Green because I cannot post links yet.
1. Download and extract the ADB+Fastboot+Drivers zip (alexpja.com/sony/adb-fastboot-win.zip)
2. Now we’ll unlock the bootloader.
a. If you do not have a Phone app (like I don’t on the SGP351), you can either get the IMEI from About -> Status in the settings OR you can find the IMEI right after the IC code, nearby the barcode on the bottom of the tablet.
b. If you do have a Phone app, enter *#06# to retrieve the IMEI.
c. Save this for later use.3. Place the tablet into fastboot mode and connect it to the computer.
a. Power off the device
b. Connect USB to computer
c. While plugging in the other side of the USB cable into the tablet, hold down the Vol + button.
d. If your speakers are on, you should a sound.
e. We have to install the drivers for fastboot. Open devmgmt.msc via the Run window or in the Start menu and in Other Devices section, you should see S1 Service or S1 Fastboot (anything containing S1).
i. If it is showing a yellow exclamation mark: Follow 3.e.i.1. If it is not, continue to 3.f.
1. We need to download Flashtool and use the driver setup. Download Flashtool (unrestrict.li/flashtool) and install it.
2. Find cmd.exe, right click it, and select Run as administrator.
a. Type in
Code:
bcdedit /set testsigning on
and press enter.
b. Reboot your computer.3. Once you have rebooted the computer, open the folder where you installed Flashtool (default: C:\Flashtool).
4. Open up the drivers folder and open Flashtool-drivers.exe.
5. Select the first two driver choices (Flashmode and Fastboot) and select “Xperia Tablet Z Drivers” and continue.
6. A new window will appear, continue on with that.
7. A window like this may appear a few times, just press Install this driver software anyway.
8. Run 3.e.2. again and run
Code:
bcdedit /set testsigning off
. Reboot your PC now or after the tutorial.f. The LED pulse light above it should be emitting a blue-ish color. The screen will be dark.4. Now we’ll verify if you have fastboot running.
a. Open the tools folder that was extracted from the ADB ZIP and double-click on START.cmd to open Command Prompt in the current directory (all it does is literally open cmd.exe, you can edit the script to verify).
b. Run the command
Code:
fastboot -i 0x0fce getvar version
. If you get
Code:
<waiting for device>
, then you did something wrong. Retrace your steps! (For example, I get
Code:
version: 0.5
)5. Go to (unlockbootloader.sonymobile.com) and continue until you reach the screen where you put type in the IMEI and an email address. Type in the first 14 digits of the IMEI (remove the last one) and your email address (not sure if name is required). You should get an email instantly with the key.
6. In the Command Prompt, run
Code:
fastboot -i 0x0fce oem unlock 0xKEY
where KEY is the key you received in the email from Sony.
7. Download whatever release you would like to use on the tablet (I’m using CM 11 nightly) from (download.cyanogenmod.org/?device=pollux)
a. Optional: Also download gapps for Google apps such as Gmail, Google Play Services, etc. (wiki.cyanogenmod.org/w/Google_Apps)8. Extract the ZIP file (but don’t delete it either) and copy boot.img to the tools folder.
9. If your device is still turned off, turn it on and enable USB storage mode. Copy the CM zip to either the internal storage (sdcard) or, if one is inserted, the microSD card (sdcard1).
10. Place it into fastboot mode again (#3).
11. Go back into the Command Prompt and enter:
a.
Code:
fastboot -i 0xfce flash boot boot.img
b.
Code:
fastboot -i 0xfce reboot
c. Enter recovery.
1. Once it shuts down, rapidly tap the Vol + button in order to get into the recovery.
2. Grep_The_Truth's tip: Look at the LED. It will turn orange and afterwards it'll turn purple. You want to press Vol+ as soon as it changes colors.12. Select “wipe data/factory reset” and wipe it. Afterwards, go back to main menu.
13. Select “Install zip” and either select “Choose zip from /sdcard” (internal storage) or “Choose zip from /storage/sdcard1” (microSD card).
I’ve had varying experience with installing from the /sdcard because sometimes it doesn’t want to mount /data while wiping (/data/media which is /sdcard is safe in wipe) the tablet, so if you were to install the zip from /sdcard with the error present, it would screw things up. I prefer the microSD card route (/storage/sdcard1), and you don’t even need a big one. 512MB works just fine. The actual path would be /sdcard/0/ when looking for the cm.zip in the internal storage.
14. When you have chosen to install from either /sdcard or /storage/sdcard1, select the cm.zip and install it.
a. If you downloaded gapps.zip, install it the same way as you did with the cm.zip.15. Go back to the main menu now and select “reboot system now”
a. Once, I had the option to install root access before rebooting, I declined (was planning on rooting after tutorial) but it gave me root anyway.
That’s it! You can now use CyanogenMod with the Sony Xperia Tablet Z.
Getting in to recopvery
I just struggled with entering recovery for way too long and I want to help others avoid this. I kept finding vague instructions.
The step I want to clarify is:
c. Once it shuts down, rapidly tap the
Code:
Vol +
button in order to get into the recovery.
Click to expand...
Click to collapse
This didn't work for me because if you press Vol+ too soon it goes right back in to fastboot mode. If you press it too late you will miss the recovery mode. You only have to press Vol+ once.
Please change step c. to read:
Look at the LED. It will turn Orange and then Purple. You want to press Vol+ as soon as it changes from Orange to Purple to enter recovery mode.
Grep_The_Truth said:
I just struggled with entering recovery for way too long and I want to help others avoid this. I kept finding vague instructions.
The step I want to clarify is:
This didn't work for me because if you press Vol+ too soon it goes right back in to fastboot mode. If you press it too late you will miss the recovery mode. You only have to press Vol+ once.
Please change step c. to read:
Look at the LED. It will turn Orange and then Purple. You want to press Vol+ as soon as it changes from Orange to Purple to enter recovery mode.
Click to expand...
Click to collapse
I'll add it along with mine, because I can do it with no problem.
alexpja said:
I'll add it along with mine, because I can do it with no problem.
Click to expand...
Click to collapse
alexpja Thanks for your tutorial, this is very detailed and easy to follow.
my Xperia is SGP321.
I put it into practice and the results it gives me the "oem unlock" is:
FAILED: (remote: Command nor allowed).
I guess you should treat my tablet has the bootloader locked and not allowed (for now??) the unlocked.
I hope someone gives us the opportunity to unlock the devices and in the future can be unlocked.
I had the same experience where at times the steps were a little confusing, especially for a beginner. Each set of instructions would either leave something out or skim over it as if everyone already knew it. That's understandable since they were probably written for that audience. I soft-bricked my SGP311 at least 10 times.
I was even going to write something like this but I got lazy.
One suggestion I would offer is to request the bootloader unlock key first since it sometimes takes a little while and a person can reduce the possibility of having to stop and wait just when they are making progress.
And for anyone going this route for the first time, don't make my mistake - flash exactly what the instructions say to flash, particularly boot.img. Once you have that recovery flashed you have a lot more control over your device. If something goes wrong in a following step like getting boot loops you can still fix it. But if you get annoyed and start poking at it then you can mess up the recovery. Then you have to reset everything to stock and just about start over.
While I don't want to say something stupid like claiming the tablet is indestructible, I found that whether I got stuck in a boot loop I couldn't get out of or screwed it up so bad that all I could get from the tablet was an occasional LED flash, I could always restore it using Emma. It's annoying to have to start all over but it's a huge relief when it boots normally.
for me flashing was fine and without any error but my Tab doesn't boot up with CM flashed...any idea?
Hanging at reboot
Hi.
I tried this procedure on my sony xperia tablet z 311. It unlocked fine and wrote boot.img fine but on reboot command, I get a red light and it hangs there.
I've managed to get it back to fastboot mode (pressing power and vol+, some white blinking lights).
But that's it, that's all I can do with this right now. It's a brick that can get into fastboot mode and that's it. Any time I write a boot.img (have tried a different one also), it writes fine but hangs with a red light at reboot.
Edit:
Used Sony's Emma in flash mode to get back to stock, tried again and it worked.
Maybe the problem was using the pollux instead of pollux_windy download, my bad.
Guess my bootloader won't be unlocked. This is A lot of work. Good job on the write up though maybe one day I'll tackle it.
BOOT LOOP Step 9
All was going well, but step 9 powering on device, now its looping.....Ill use flash tools to put jelly bean on and try again, since i was trying with kitkat...why i suspect kitkat is the issue, before i used to be able to unlock and lock boot-loader with jelly bean but with kitkat it didn't work, which i then forced it via cmd
No GPS
I used the tutorial for my Pollux Windy (WiFi Only) and used the latest nightly. everything went well but my GPS is now broken. Is this a known issue?
kevinsickles said:
Is this a known issue?
Click to expand...
Click to collapse
yep! use search to find out more.
mulebreath said:
Hi.
I tried this procedure on my sony xperia tablet z 311. It unlocked fine and wrote boot.img fine but on reboot command, I get a red light and it hangs there.
I've managed to get it back to fastboot mode (pressing power and vol+, some white blinking lights).
But that's it, that's all I can do with this right now. It's a brick that can get into fastboot mode and that's it. Any time I write a boot.img (have tried a different one also), it writes fine but hangs with a red light at reboot.
Edit:
Used Sony's Emma in flash mode to get back to stock, tried again and it worked.
Maybe the problem was using the pollux instead of pollux_windy download, my bad.
Click to expand...
Click to collapse
Hi,
I've been trying with my Xperia Tablet Z Wi-Fi SGP311. Ran into the same problem. On reboot command the LED was stuck on red for 10 minutes and the cmd window was still open. I unplugged the USB and the LED would not turn off. Tried some things, I don't remember specifically what, but it got the LED to turn off. Now my device can't be detected. I've downloaded Emma and it is not recognising my tablet. I've tried to plug the USB in while hold Vol +, Vol -, and the Power button. No detection for any. All I can do with my tablet is make the LED flash white, purple and red in rapid succession by holding Vol + and Power for 5 seconds.
Anyone know what's happened? I suspect I've completely bricked it :L
EDIT: Apparently there are different modes which you can cycle through. If you hold down Vol + and Power for 5 seconds, the LED will flash according to which mode the tablet is in. The different modes give these flashes:
- 1 White flash
- 3 Rapid which flashes
- A white, purple and red flash in quick succession
To switch between the modes, I hold down Vol+ and Power, and after 5 seconds it will take around 3 more seconds to change modes. One of these modes will not appear unless plugged into a PC. What do these mean and can I do anything with it? Tablet is still bricked.
EDIT2: I've managed to get Emma to recognise my tablet. Turns out the modes do have different purposes. I should be fine now, problem solved. I will just leave the solution here in case anyone runs into the same problem.
Unplug your device and hold Vol + and Power for 10 seconds. At the 5 second mark your LED should flash white ONCE. Keep both buttons held and within 5 more seconds, your LED will flash white THREE times consecutively. This will allow you to enter Flashmode (plug in USB while holding Vol -) and Fastboot (plug in USB while holding Vol +). For Emma to recognise your device, enter Flashmode and you can restore and try again.
Bootloop
I've tried many times to flash cyanogenmod onto my Xperia Tablet Z (SGP311). This is a Wi-Fi only tablet and I have downloaded the versions of CM from (download.cyanogenmod.org/?device=pollux_windy) I've followed all of the steps and tried all of the versions of CM down to 10.2 (I used GApps10.2 for CM10.2). Each version gets stuck in bootloop. I've cleared all data (in CWM - wipe data/factory reset, wipe cache partition, wipe delvik cache) before flashing CM and GApps; however, when I try to clear data I get an error. This is what the tablet says:
-- Wiping Data...
Formatting /data...
Error mounting /data!
Skipping format...
Formatting /cacha
Formatting /sd-ext...
Formatting /sdcard/.android_secure!
Skiiping format...
Data wipe complete.
Click to expand...
Click to collapse
I'm thinking the "Error mounting /data" is the problem, but I'm not entirely sure, nor am I sure of how to fix it.
Any suggestions?
EDIT: Turns out I'm just really bad with Android stuff. I ended up flashing the original Xperia software, unlocking the bootloader (according to this tutorial's instructions), then I downgraded to 4.1.2, rooted my tablet (forum.xda-developers.com/showpost.php?p=53063218&postcount=14) and installed the PhilZ and TWRP custom recoveries. I didn't get to use them in the end. For some reason CWM kept coming up no matter what combination of buttons I pressed while rebooting. After downgrading and rebooting, I followed the rest of the instructions on this tutorial (from step 7). This time I got no errors while cleaning the disk, cache and delvik cache. Flashed the zip files, rebooted the device and voila, Cyanogenmod11!
Again, I'll leave this edit here in case someone runs into a similar problem. I couldn't get any version of CM until I rooted first.
I followed this guide and bricked my device. If anyone has any tips - PLEASE HELP!
I tried to flash CM11, all seemed to be going great until CM11 and Gapps where installed any I hit "Reboot system now" in CVM. The device never booted again (I which I knew why!), and is now pretty much dead. I can however:
- Enter Flashmode
- Enter Fastboot mode
- Relock/Unlock bootloader
- Emma recognizes my device just fine in flashmode.
So I still think there is some hope, right?
I have tried installing the firmware that Emma suggests, doesn't work.
I have tried flashing a firmware I found on the internet with Flashtool, doesn't work.
I have tried relocking the bootloader and trying to repair the device through SUS, doesn't work.
So, PLEASE, help my sort this out! I would be forever greatful!
tp_88 said:
I followed this guide and bricked my device. If anyone has any tips - PLEASE HELP!
I tried to flash CM11, all seemed to be going great until CM11 and Gapps where installed any I hit "Reboot system now" in CVM. The device never booted again (I which I knew why!), and is now pretty much dead. I can however:
- Enter Flashmode
- Enter Fastboot mode
- Relock/Unlock bootloader
- Emma recognizes my device just fine in flashmode.
So I still think there is some hope, right?
I have tried installing the firmware that Emma suggests, doesn't work.
I have tried flashing a firmware I found on the internet with Flashtool, doesn't work.
I have tried relocking the bootloader and trying to repair the device through SUS, doesn't work.
So, PLEASE, help my sort this out! I would be forever greatful!
Click to expand...
Click to collapse
download a proper stock (not bricked) firmware for your device and flash with flashtool.
Rootk1t said:
download a proper stock (not bricked) firmware for your device and flash with flashtool.
Click to expand...
Click to collapse
What makes you think that the stock firmwares I've tried are bricked? I've since my post tried one which I downloaded through Flashtool - same result.