Related
Download this file RC30 or this one for RC8, extracted all the files to the root of the SD Card. Shut down the phone and turn it on holding the power and camera button. Follow the instructions on the phone to downgrade to RC29/RC7. Once you're on RC29/RC7 it's time to install the test keys.
Reboot the phone, When it has finished booting hit enter twice and type the following at the home screen. It will start searching your contacts, but don't worry about that. Also, you won't see any visible sign that the first command worked. Just go ahead and type the second command straight afterwards:
Code:
cd sdcard<press enter>
sh install<press enter>
After a moment your phone should reboot itself.
switch off the phone again and then hold down the home key while you switch it on. Keep the home key held down until you see the recovery screen (with the "!" triangle and the picture of the phone). Then press Alt+L on the keyboard and if you see "Using test keys" on the second line of text then the modified recovery image is installed and you can now install the modified firmware by hitting Alt-S. You should now be on JF 1.41 RC30/RC8. Enjoy...
*Optional but highly recommended*
To install the modified bootloader rename Hard_SPL_update.zip to update.zip and switch the phone off and then hold down the home key while you switch it on again. Keep the home key held down until you see the new recovery menu, hit Alt-S to apply the new bootloader. Congrats you now have the modified bootloader with the skating androids.
You can only see the skating androids when you power up holding the Power and Camera buttons, it replaces the multicolor recovery bootloader. The boot loader allows you to use fastboot in recovery mode. Once you've done with the files on the SD card they can be discarded.
Source
root of the sd card?
How do I make sure that files are on the root of my sd card? When I connect my g1 to a computer via usb it brings up another directory f:\ in my case. When I open the directory to view the files all I see are the files that I've downloaded and then copied/pasted to the f:\ directory. I'm not seeing any other files.
ritz256 said:
How do I make sure that files are on the root of my sd card? When I connect my g1 to a computer via usb it brings up another directory f:\ in my case. When I open the directory to view the files all I see are the files that I've downloaded and then copied/pasted to the f:\ directory. I'm not seeing any other files.
Click to expand...
Click to collapse
you can't turn on USB
ritz256 said:
How do I make sure that files are on the root of my sd card? When I connect my g1 to a computer via usb it brings up another directory f:\ in my case. When I open the directory to view the files all I see are the files that I've downloaded and then copied/pasted to the f:\ directory. I'm not seeing any other files.
Click to expand...
Click to collapse
The root of the sd card is the same as "F:\" in your example. When you transfer the file, put them on the f: drive, without putting them in any subfolders. Only use one update at a time. To check to make sure they are written to the sd card, use one of the file manager apps available from the market and make sure your usb cable is not in the phone. If you are on a wireless network, you may want to look at getting Discover form the market. It will allow you to do wireless file transfers to/from the sd card.
without the links to the files the original post is fairly pointless and confusing. Should have just linked to the other forum and left the copy/paste job out.
i tried this and every single time i turn on my g1 is goes to the tri colored bootloader screen and it wont even go to recovory mode.... any solution?
recovery would be booting holding down home and power key.
Not camera and power
Credit goes to eugene373 and attn1. These are mostly their instructions, but I did change, clarify, and add a few steps. If you can't get any of the other methods working, try this one.
Prerequisites...
Note: If you're in Linux, you only need to do Step 4, Step 6, and Step 7.
Step 0.
Download and install HTC Sync: http://www.htc.com/us/support/aria-att/downloads/
Step 1.
Download and unzip the Android SDK: http://developer.android.com/sdk/index.html
Step 2.
Go into the folder where you unzipped the Android SDK and open "SDK Setup.exe".
If you aren't greeted with a failed to fetch URL error, proceed to Step 3. If you did receive this error, go to Settings in the "Choose Packages to Install" window and check "Force https;//... sources to be fetched using http://..."
Close and re-open "SDK Setup.exe".
Step 3.
When the "Choose Packages to Install" window pops up, make sure the package "Usb Driver package, revision x" is checked. You can uncheck everything else. Click Install. After it downloads and installs, close "Android SDK and AVD Manager".
Step 4.
With your device unplugged from your computer, go to Settings > Application > Development on your device and turn on USB Debugging.
Step 5.
Now plug your device in to your computer. This is just to make sure the USB drivers are installed.
Once they are installed, unplug your device and turn it off.
Step 6.
This step is optional, but it may prevent an error later on in the process. If you've never formatted your SD card from a computer, remove it from the phone and format it in Windows or OSX with an external card reader. Then place the formatted card back in your phone, but leave the phone off.
Step 7.
Download the updated Root.zip from eugene373's guide: Root the Slide & Other HTC Devices*6/15/2010* How-To Updated 6/29/2010
Now let's get started...
Step 0.
Unzip Root.zip
Step 1.
Place the contents ("update.zip", "ota.zip", and "loop") into the Android SDK tools folder.
Step 2.
Open Command Prompt or Terminal and CD to the SDK tools directory.
Step 3.
Power on your device into the bootloader by holding the "Volume Down" key and simultaneously pressing Power.
Once you're in the bootloader, wait about 30 seconds until some diagnostic checking is done.
Press "Volume Down" to highlight Recovery, but do not push Power to execute just yet.
Step 4.
Now run your loop file from the prompt (either type "loop" in Windows or "./loop.sh" in Linux) (refer to ice3186's post for Mac instructions)
Note: The loop does nothing but show you the connection status of your phone. It's not technically required, but we'll use it in this guide.
Step 5.
Once the loop is running in your prompt, get ready to connect the phone to the computer with the USB cable, but don't connect one end quite yet. With Recovery still highlighted on your phone, you will need to push the Power button and then immediately plug in the other end of the USB cord.
Step 6.
After a few seconds, you should see your device listed in the loop.
Step 7.
Unplug the USB cable from the bottom of your phone and plug it back in. You probably don't need to do this, but let's be safe. Wait for your device to show up in the loop again. Hit CTRL-C to terminate the loop.
Step 8.
You should see a triangle/exclaimation over a phone graphic.
Hold the "Volume Up" key (note it's Volume UP this time) and simultaneously press Power.
After the menu comes up, use the volume and power buttons to select and run update.zip. (This will fail, but we already know that! Select it anyway.)
Step 9.
Paste the following command into your prompt and press Enter.
adb push ota.zip /sdcard/update.zip (*OSX users add a ./ in front of all terminal commands please)
Step 10.
This is very important!! Have this next command ready in your prompt before running update.zip again!!
This is the command. Paste it into your prompt, but DO NOT press Enter yet.
adb push update.zip /sdcard
Step 11.
Run update.zip and as soon as you see a faint progress bar appear behind the text at the bottom of the screen, push Enter to execute the command in your prompt.
Step 12.
If successful, you should see Clockwork Recovery and you now have Su and Superuser.apk installed! You can now reboot your phone into the OS to verify. If unsuccessful, repeat steps 11 and 12.
Step 13.
This step is optional, but it will save you the pain of going through all of these steps again in the future.
Unrevoked team: Recovery reflash tool (updated - Now for Aria/Liberty!)
I think some trouble shooting comments should be mentioned, so I'll just write a few things I noticed while rooting my device (for 7 frustration filled hours).
If you cannot see your device show up in 'adb devices' in recovery, boot into the OS normally and see if it shows up. If it does not, then it's a safe bet that you have one of two problems - you do not have all the drivers installed, or you do not have 'usb debugging' enabled. This can be enabled in 'settings->applications->development->usb debugging'. To avoid driver issues, it's highly recommended that you do this process in linux or osx.
If, on the other hand, your phone DOES show up in Android but not in recovery, or if it just blips on the screen for a second (when running the loop) as an offline device, then it might be the formatting of your sd card. Do NOT format your sd card from your phone or within Android. The ONLY time I managed to get the phone to show up in recovery without disappearing immediately was by removing the sd card, formatting it in windows or osx with an external card reader, copying the files over (new rom or rooting files), and then replacing it in the phone while the phone is off. After putting the card back in your phone, try the procedure again - go to the bootloader->hboot->recovery (while the cable is unplugged), then press the power button and immediately after plug the cable in (usually works when you plug the cable in about .2-.5 seconds later). If it does not show up at all, reboot the phone and try again, but do NOT let it boot back to Android. You can get back in to the bootloader by waiting until the 'HTC quietly brilliant' screen shows up and typing 'adb reboot bootloader' with the usb cable attached.
It took me a really long time to figure that out. I don't think the type of sd card matters so much as the formatting of it. I actually used the 2gb card that came with the phone, and it worked almost every single time after I reformatted the card.
Also, if you manage to get it working and root the phone, do yourself a huge favor and install the custom Unrevoked recovery image mentioned in the original rooting thread, so you never have to deal with this nonsense ever again.
Also also, if you get to the step where you do 'adb push ota.zip /sdcard/update.zip' and you get an error:0, installation aborted message, you did something wrong. The problem is that you aren't actually supposed to flash ota.zip. What you're supposed to do is push ota.zip to your phone as update.zip, and leave it there. Don't touch anything else. What you will do after that is type 'adb push update.zip /sdcard/update.zip' in the command prompt (WITHOUT hitting enter yet, just get ready to). You will then select 'sdcard:update.zip' and press power and IMMEDIATELY AFTER pressing power, you will press enter on the command prompt to execute your adb push command. What this does is causes recovery to read the ota.zip file you uploaded and recognize it as a legit update, but you replace it with update.zip before it actually gets extracted (if your timing is good). So recovery reads the signature of ota.zip, but actually extracts the stuff in update.zip and runs that instead.
Hope that helps with some common problems I observed. Good luck, dudes.
okay so I think I the only one using a Mac in this rooting process. A few things I have learned and may already be known but I thought I would clarify.
1.) to get a loop to run on the mac i had to re-write the file loop.bat
this is the code that works for me and how to do it.
a.) rename the file to end in .sh not .bat the way it came
b.) open the file with TextEdit
c.) delete all of the text in it and write this in there
Code:
while [ "0" ]
do
{
./adb devices
}
done
d.) save the file back in the sdk/tools folder
e.) in terminal the command once you cd to the folder is ./loop.sh
2.) i have yet to be successful in the attempt to root so anyone knowing anything to help would be appreciated! But i am still cracking i think i am going to wear out the plug before i am done though.
it should be pointed out that the loop does nothing except tell you if you have a connection or not. When you plug in the usb port, it will respond after a few seconds, or it won't. Try again.
gtg465x said:
Credit goes to eugene373 and attn1. These are mostly their instructions, but I did change, clarify, and add a few steps. If you can't get any of the other methods working, try this one.
Prerequisites...
Step 0.
Download and install HTC Sync: http://www.htc.com/us/support/aria-att/downloads/
Step 1.
Download and unzip the Android SDK: http://developer.android.com/sdk/index.html
Step 2.
Go into the folder where you unzipped the Android SDK and open "SDK Setup.exe"
When the "Choose Packages to Install" window pops up, make sure the package "Usb Driver package, revision x" is checked. You can uncheck everything else. Click Install. After it downloads and installs, close "Android SDK and AVD Manager".
Step 3.
With your device unplugged from your computer, go to Settings > Application > Development on your device and turn on USB Debugging.
Step 4.
Now plug your device in to your computer. This is just to make sure the USB drivers are installed.
Once they are installed, unplug your device and turn it off.
Step 5.
Download Root.zip from eugene373's guide: http://forum.xda-developers.com/showpost.php?p=6820344&postcount=1
Now let's get into it...
Step 0.
Unzip Root.zip
Step 1.
Place the contents ("update.zip", "ota.zip", and "loop") into the Android SDK tools folder.
Step 2.
Open Command Prompt or Terminal and CD to the SDK tools directory.
Step 3.
Power on your device into the bootloader by holding down the "Volume Down" key and simultaneously pressing Power.
Once you're in the bootloader, wait about 30 seconds, until some diagnostic checking is done.
Press "Volume Down" to highlight Recovery, but do not push Power to execute just yet.
Step 4.
Now run your loop file from the prompt (either type "loop" in Windows or "./loop.sh" in a *nix like) ( ./ Is used For OSX )
Step 5.
Once the loop is running in your prompt, get ready to connect the phone to the computer with the USB cable, but don't connect one end quite yet. With Recovery still highlighted on your phone, you will need to push the Power button and then immediately plug in the other end of the USB cord.
Step 6.
After a few seconds, you should see your device listed in the loop.
Step 7.
Unplug your USB cable from the bottom of your phone and plug it back in. You probably don't need to do this, but let's be safe. Wait for your device to show up in the loop again. Hit CTRL-C to terminate the loop.
Step 8.
You should see a triangle/exclaimation over a phone graphic.
Hold down the "Volume Up" key (note it's Volume UP this time) and simultaneously press Power.
After the menu comes up, use the volume and power buttons to select and run update.zip. (This will fail, but we already know that! Select it anyway.)
Step 9.
Paste the following command into your prompt and press Enter.
adb push ota.zip /sdcard/update.zip (*OSX users add a ./ in front of all terminal commands please.)
Step 11.
This is very important!! Have this next command ready in your prompt before running update.zip again!!
This is the command. Paste it into your prompt, but DO NOT press Enter yet.
adb push update.zip /sdcard
step 12.
Run update.zip and as soon as you see a faint progress bar appear behind the text at the bottom of the screen, push Enter to execute the command in your prompt.
Step 13.
If successful, you should see Clockwork Recovery and you now have Su & Superuser.apk installed! You can now reboot your phone into the OS to verify.
If unsuccessful, repeat steps 11 & 12.
Click to expand...
Click to collapse
This isn't complete - this just gets you to clockwork and you haven't installed anything yet. You need to add steps to add root acces or flash a rom that is rooted. Also, make sure to reference the unrevoked tool to install Clockwork after root so this whole ordeal can be avoided next time.
Yes! The secret was formatting the sd card outside of the phone. I am now rooted and liberated! Thanks for plugging along with all the advice guys!
modest_mandroid said:
I think some trouble shooting comments should be mentioned, so I'll just write a few things I noticed while rooting my device (for 7 frustration filled hours).
If you cannot see your device show up in 'adb devices' in recovery, boot into the OS normally and see if it shows up. If it does not, then it's a safe bet that you have one of two problems - you do not have all the drivers installed, or you do not have 'usb debugging' enabled. This can be enabled in 'settings->applications->development->usb debugging'. To avoid driver issues, it's highly recommended that you do this process in linux or osx.
If, on the other hand, your phone DOES show up in Android but not in recovery, or if it just blips on the screen for a second (when running the loop) as an offline device, then it might be the formatting of your sd card. Do NOT format your sd card from your phone or within Android. The ONLY time I managed to get the phone to show up in recovery without disappearing immediately was by removing the sd card, formatting it in windows or osx with an external card reader, copying the files over (new rom or rooting files), and then replacing it in the phone while the phone is off. After putting the card back in your phone, try the procedure again - go to the bootloader->hboot->recovery (while the cable is unplugged), then press the power button and immediately after plug the cable in (usually works when you plug the cable in about .2-.5 seconds later). If it does not show up at all, reboot the phone and try again, but do NOT let it boot back to Android. You can get back in to the bootloader by waiting until the 'HTC quietly brilliant' screen shows up and typing 'adb reboot bootloader' with the usb cable attached.
It took me a really long time to figure that out. I don't think the type of sd card matters so much as the formatting of it. I actually used the 2gb card that came with the phone, and it worked almost every single time after I reformatted the card.
Also, if you manage to get it working and root the phone, do yourself a huge favor and install the custom Unrevoked recovery image mentioned in the original rooting thread, so you never have to deal with this nonsense ever again.
Also also, if you get to the step where you do 'adb push ota.zip /sdcard/update.zip' and you get an error:0, installation aborted message, you did something wrong. The problem is that you aren't actually supposed to flash ota.zip. What you're supposed to do is push ota.zip to your phone as update.zip, and leave it there. Don't touch anything else. What you will do after that is type 'adb push update.zip /sdcard/update.zip' in the command prompt (WITHOUT hitting enter yet, just get ready to). You will then select 'sdcard:update.zip' and press power and IMMEDIATELY AFTER pressing power, you will press enter on the command prompt to execute your adb push command. What this does is causes recovery to read the ota.zip file you uploaded and recognize it as a legit update, but you replace it with update.zip before it actually gets extracted (if your timing is good). So recovery reads the signature of ota.zip, but actually extracts the stuff in update.zip and runs that instead.
Hope that helps with some common problems I observed. Good luck, dudes.
Click to expand...
Click to collapse
Really good tips. I hope you don't mind - I am going to link to this to my original thread.
Troubleshooting Tip on Prerequisite Step 2: If you're working behind a firewall, router, or proxy server, you're going to have to configure SDK Setup to use an open port on that device, in order to download updates.
I won't go through the exact steps here, but if SDK setup is hanging, this is the most likely culprit.
Regards,
Corporate Dog
Corporate Dog said:
Troubleshooting Tip on Prerequisite Step 2: If you're working behind a firewall, router, or proxy server, you're going to have to configure SDK Setup to use an open port on that device, in order to download updates.
I won't go through the exact steps here, but if SDK setup is hanging, this is the most likely culprit.
Regards,
Corporate Dog
Click to expand...
Click to collapse
get a copy of linux livecd and then you don't have to actually set up the SDK or worry about any drivers.
attn1 said:
This isn't complete - this just gets you to clockwork and you having installed anything yet. You need to add steps to root or flash a rom that is rooted. Also, make sure to reference the unrevoked tool to install Clockwork after root so this whole ordeal can be avoided next time.
Click to expand...
Click to collapse
If you made it to clockwork using this method then you're rooted. Check eugene's updated instructions. Look at the 6/29/2010 update on his original post... http://forum.xda-developers.com/showpost.php?p=6820344&postcount=1
I will add a reference to the unrevoked tool.
modest_mandroid said:
If, on the other hand, your phone DOES show up in Android but not in recovery, or if it just blips on the screen for a second (when running the loop) as an offline device, then it might be the formatting of your sd card. Do NOT format your sd card from your phone or within Android. The ONLY time I managed to get the phone to show up in recovery without disappearing immediately was by removing the sd card, formatting it in windows or osx with an external card reader, copying the files over (new rom or rooting files), and then replacing it in the phone while the phone is off. After putting the card back in your phone, try the procedure again - go to the bootloader->hboot->recovery (while the cable is unplugged), then press the power button and immediately after plug the cable in (usually works when you plug the cable in about .2-.5 seconds later). If it does not show up at all, reboot the phone and try again, but do NOT let it boot back to Android. You can get back in to the bootloader by waiting until the 'HTC quietly brilliant' screen shows up and typing 'adb reboot bootloader' with the usb cable attached.
It took me a really long time to figure that out. I don't think the type of sd card matters so much as the formatting of it. I actually used the 2gb card that came with the phone, and it worked almost every single time after I reformatted the card.
Click to expand...
Click to collapse
Excellent troubleshooting tips. I added a note about formatting your SD card to the prerequisites.
ice3186 said:
okay so I think I the only one using a Mac in this rooting process. A few things I have learned and may already be known but I thought I would clarify.
1.) to get a loop to run on the mac i had to re-write the file loop.bat
this is the code that works for me and how to do it.
a.) rename the file to end in .sh not .bat the way it came
b.) open the file with TextEdit
c.) delete all of the text in it and write this in there
Code:
while [ "0" ]
do
{
./adb devices
}
done
d.) save the file back in the sdk/tools folder
e.) in terminal the command once you cd to the folder is ./loop.sh
2.) i have yet to be successful in the attempt to root so anyone knowing anything to help would be appreciated! But i am still cracking i think i am going to wear out the plug before i am done though.
Click to expand...
Click to collapse
Thanks. Added a reference to your post.
attn1 said:
it should be pointed out that the loop does nothing except tell you if you have a connection or not. When you plug in the usb port, it will respond after a few seconds, or it won't. Try again.
Click to expand...
Click to collapse
Noted in the original post.
Corporate Dog said:
Troubleshooting Tip on Prerequisite Step 2: If you're working behind a firewall, router, or proxy server, you're going to have to configure SDK Setup to use an open port on that device, in order to download updates.
I won't go through the exact steps here, but if SDK setup is hanging, this is the most likely culprit.
Regards,
Corporate Dog
Click to expand...
Click to collapse
Thanks. Added the workaround.
attn1 said:
get a copy of linux livecd and then you don't have to actually set up the SDK or worry about any drivers.
Click to expand...
Click to collapse
Thanks. Added a note to the top of the prerequisites.
gtg465x said:
Step 12.
If successful, you should see Clockwork Recovery and you now have Su and Superuser.apk installed! You can now reboot your phone into the OS to verify. If unsuccessful, repeat steps 11 and 12.
Step 13.
This step is optional, but it will save you the pain of going through all of these steps again in the future.
Unrevoked team: Recovery reflash tool (updated - Now for Aria/Liberty!)
Click to expand...
Click to collapse
In no way, shape or form are you done after set 12.
You need to do more than just get into Clockwork. That alone doesn't root the phone.
gtg465x said:
If you made it to clockwork using this method then you're rooted. Check eugene's updated instructions. Look at the 6/29/2010 update on his original post... http://forum.xda-developers.com/showpost.php?p=6820344&postcount=1
I will add a reference to the unrevoked tool.
Click to expand...
Click to collapse
My mistake. He not only updated his instructions, he updated his update.zip. That should do it.
Good job!
I was just wondering If I have device issues after it is rooted, is it possible to remove the root and flash everything back to factory defaults for warranty purposes like the windows phones or is it once the warranty is gone it is gone?
steezee said:
I was just wondering If I have device issues after it is rooted, is it possible to remove the root and flash everything back to factory defaults for warranty purposes like the windows phones or is it once the warranty is gone it is gone?
Click to expand...
Click to collapse
Dunno if you can reflash the stock recovery again if you replaced it with clockwork, but you can definitely flash the stock ATT rom again. You can download it from HTC's site: http://member.america.htc.com/download/Web_materials/Manual/HTC_Aria_ATT/HTCAriaOriginalShipROM.exe
Banging my head on the wall. Got it to detect device once on loop. Never again after that. Phone shows up in device manager. Formatted 8gb and 2 gb cards several times.
urge growing. ... want to . . break.. . . .. . .random objects. . .
attn1 said:
My mistake. He not only updated his instructions, he updated his update.zip. That should do it.
Good job!
Click to expand...
Click to collapse
Sorry, I should have mentioned that he updated his update.zip.
You guys are right , there are missing step in the tutorial to fully root Aria.
after i get in to the clockwork from the step above. i have to install the custom rom that can be found in the forum.
when i try to install "Unrevoked team: Recovery reflash tool (updated - Now for Aria/Liberty!) " . the process goes throught but the recovery is still the same HTC blue color recovery screen.
so before you insert your sd card into the phone after you format the sd card. remember to copy the rooted rom into the sd card so when you successfully get into the clockwork. you want to install the rom then your aria is rooted with superuser icon on the application.
after then you do the "Unrevoked team: Recovery reflash tool (updated - Now for Aria/Liberty!) step .
There are no steps missing from the first post. I rooted my Aria using that method. Just make sure you have the latest Root.zip from eugene's thread. He updated it the other day and if you try to use the older version of Root.zip with this method it will not work.
What you are doing is installing a custom rom, which is fine, but it's not required to root the Aria.
i was trying to get the clockwork to install and it only work after i load the liberated_aria_b003_signed.zip
before i load liberated_aria_b003_signed.zip , it still give me the default HTC recovery screen.
after i load liberated_aria_b003_signed.zip and install "Unrevoked team: Recovery reflash tool (updated - Now for Aria/Liberty!) " . i get the clockwork screen as the recovery screen .
i still can't get the side loading to show after i follow the step from here
•COMMON:
•Enable USB debugging (settings > applications > development > USB Debugging)
•adb remount
•adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
Linux/OS X:
•echo "update secure set value = 1 where name = 'install_non_market_apps';"|sqlite3 settings.db
WINDOWS:
•echo update secure set value = 1 where name = 'install_non_market_apps';|sqlite3 settings.db
COMMON:
•adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
•Reboot phone and sideloading works. (thanks to fluffyarmada)
.
I received my transformer today and looked on google for how to root it.
I followed these instructions posted by UBRock on androidforums.com: (as I'm new I cannot post outside links, so I copied the instructions at the end)
After step 4a, my TF booted up like it normally would, with the EE pad screen. Then my screen went to what is shown in the attachment.
I'll turn the screen off, and it will turn on and off by itself.
I've googled and haven't found any issues with rooting this device.
Did I just kill this thing in a few hours? I followed every instruction and had no issues until this.
I bought it off amazon if that matters in case I have to return it. I really hope there's a solution, I got it for a vacation I'm leaving for on Monday.
instructions:
I used this to root my Transformer after the official 3.1 update and it works great. Fast and easy!
The only thing you have to do with ADB is to make sure you have adb installed properly on your computer. Everything is done via scripts.
xda-developers - View Single Post - [ROM] Transformer 3.1 pure root
Quote:
Originally Posted by fone_fanatic View Post
Ok, just did this and worked flawlessly, have root and CWM in under 10 minutes!
I'll replay step by step what i did to help those that are still confused. (it looks long but its really not, i was just very detailed causing this to be more of a "take my hand and i'll walk you through it")
Some background info. Highly recommend reading these if you don't know what either is!
Rooting Explained + Top 5 Benefits of Rooting by androidpolice.com
What is ClockWorkMod recovery and how to use it by addictivetips.com
STEP 1. Make sure you have all the correct asus drivers installed. Not sure if this is necessary but i had them all installed previously and i didn't run into a single issue.
1a. Head over to Asus Support/download page for the transfomer
1b. Select your PC's operating system from the drop down box.
1c. Download and install the USB driver, Asus Sync, and EEE Pad Pc Suite (don't think this one is needed but i installed them all when i first got my tf).
Step 2. Verify that you have adb running properly.
Since adb.exe is included in the download, you really don't need the sdk or adb from elsewhere.
2a. connect your tf via USB to your PC after installing the driver and other apps from step 1.
2b. Open Command prompt on your pc (win key+R) and open (and extract) Tf_rootkit_31 (link at bottom of post).
2c. Navigate to /tf_rootkit_31/root_app/ folder from the downloaded and extracted file, drag "adb.exe file to the open command prompt window.
(it should read something like C:\....\tf_rootkit_31\adb.exe)
2d. After the "adb.exe" press space bar and type "devices" (w/o quotes ofcourse) press enter.
If it says "List of Devices attached" and under that a 15 mixed numbers and letters (serial number) followed by device then adb is working!
If NOT, look at the stickies or search on google on getting adb to work on your OS.
STEP 3. Now the fun begins Here we will put the TF in APX mode and install the APX driver.
3a. Shut your TF off and while plugged into your PC, hold the volume UP and Power button until your PC makes that USB device plugged in sound and there is a notification about installing drivers.
3b. Open up the driver install thing in status bar and press on cancel (or whatever it is to get it to stop searching online for the driver).
3c. Open Device manager, scroll down to "Other Devices" (might be named something else in xp or vista) and you should see APX something with a small exclamation mark in a yellow triangle.
3d. Right click it, select "Update Driver Software..." -> "Browse my computer for driver software" -> "let me pick from list ..." -> click next -> "have disk" -> Browse -> navigate to the downloaded tf_rootkit_31 folder, open usbpcdriver folder and select "NvidiaUsb.inf" -> open, and all it to install, Ignore the unsigned error, let it install anyway.
STEP 4. Get to installing! Now your TF should be in APX Mode (if memory serves me right the screen should turn on.
4a. Go to the downloaded tf_rootkit_31 folder and double click on root.bat (on the TF screen it should say something along the line of "...update successful..."
4b. (OPTIONAL) if you want clockwork mod recovery, then go ahead and double click cwm.bat [Follow STEP 6 to update CWM]
4c. Restart TF, once rebooted make sure USB Debugging is enabled (Settings->Applications->Development)
4d. double click root_app.bat (this installs su and superuser.apk via adb, so command prompt will open up and do its adb thing and reboot your TF)
STEP 5. Confirm completion and CELEBRATE!
5a. Open your app drawer up after reboot and check to see if the Superuser app is there, if so install an app that requires root access (root explorer, adfree, titanium backup etc) and once you open it up, if you get a box requesting super user permission the you got it working!
5b. do a naked/underwear dance!
STEP 6. Update CWM recovery!! You will need a microSD card
6a. Go over to the CWM thread and download latest version of CWM recovery
6b. Place that downloaded .zip (DO NOT UNPACK) on your microSD card
6c. power TF off, then hold voume down + power button, when you see white writing in the top left of the screen press volume up and you should now bee in CWM recovery. Use volume up/down to move through the options and power button to select.
6d. Scroll down to "Install zip from sdcard" press power button then select "Choose zip from sdcard" and now it should list what is on your microsd, Scroll down and select the .zip you downloaded (as of this writing latest version is named recovery-3.1.0.1-solarnz-R3-240511-1908.zip)
6e. Follow instructions on screen, should be straightforward. And now your CWM is updated!
Tf_RootKit_31: Megaupload AND dropbox mirror: Dropbox (thanks tharonald1981)
Click to expand...
Click to collapse
well after running the NVFlash back to stock it went back to what it was when i opened the box and seems to be working with no issues. I'm definitely scared to flash again
MoldyPoldy said:
well after running the NVFlash back to stock it went back to what it was when i opened the box and seems to be working with no issues. I'm definitely scared to flash again
Click to expand...
Click to collapse
how did you do this becuase i followed the same instructions as you and all i was left with the the asus startup splash screen but won't boot further..
gtaguy said:
how did you do this becuase i followed the same instructions as you and all i was left with the the asus startup splash screen but won't boot further..
Click to expand...
Click to collapse
I can't post links, but it's the thread "Asus Transformer NVFlash Stock 3.1 Recovery Roms" on transformerforums.com
You guys extracting the 3 img files and putting it in the NVFlash root folder?
after sweating it for alittle while i was able to do as you guys said above.. downloaded the files placed them in the nvflash folder and recovered the system back to original state. Happy to say that im back to 3.1 now i have to work on trying to get the 3.2 pushed ota.. I do think this rom i just pushed into it is not factory original cuase now i can see the post and the 3.1 rom is rooted.. but im just glad to be back up and running with this amazing tablet..
Hello everyone, Im making a new rooting tutorial for the Samsung Galaxy S Relay 4G as the last tutorial [root]\{cm9} samsung galaxy relay 4g (updated 11/19) wasn't working for me. This tutorial will also have more details so will be easier to follow for the less technical.
BEFORE I START I AM IN NO WAY RESPONSIBLE IF YOU BRICK YOUR DEVICE. ROOTING YOUR PHONE WILL VOID YOUR WARRANTY..
1. Follow this guide for setting up the SDK. If you already have SDK, great move on to step 2
2. Download Drivers and install them. If you already have your drives installed move on to stop 3
3. Download Odin v3.04
4. Unzip the Odin archive. Put it somewhere you can find it, on the root of your C:\ drive is a good place.
5. Download ClockworkMod-based Recovery
6. Unzip cwm.tar.zip into Odin3-v3.04 folder that you unzipped in step 4
7. Download Super User
8. Place UPDATE-SuperSU-v1.25.zip on your phones sdcard.
9. Run the Odin executable "Odin3 v3.04.exe" in the Odin3-v3 folder
9.5 Go into your phone settings and click on Develop Option then make sure USB Debugging is checked.
10. Power off your Samsung Galaxy S Relay 4G and connect the USB adapter to the computer and to your Samsung Galaxy S Relay 4G
11. Boot the Samsung Galaxy S Relay 4G into download mode by holding down Home, Volume Down and Power
NOTE: To confirm the device is connected and working, look for the blue COM box with the word Added!! inside
12. Uncheck the box labeled Auto Reboot
13. Press the dialog box labeled PDA and select the ClockworkMod-based Recovery named "cwm.tar.md5"
14. Press start and a blue transfer bar will appear on the device showing the recovery being transferred
15. Once the recovery has been transferred you should see a Green PASSED. At his point disconnect the Samsung Galaxy S Relay 4G and remove the battery
14. Put your battery back in your Samsung Galaxy S Relay 4G and Immediately boot into recovery by holding down Home, Volume Up and Power
15. Once in recovery use volume down to select install zip from sdcard and hit power
16. Use volume down key to select UPDATE-SuperSU-v1.25.zip and hit power.
17. Now you are rooted but we are not done yet, Reboot your phone and make sure super user is showing up in the app drawer.
18. Now open up a cmd window by going to the start menu of windows and typing in cmd in the search or by clicking on run on the right hand side.
19. In the cmd window navigate to adb which is part of the SDK kit you installed in step one.
20. Once you are in the same directory as adb.exe type adb shell.
21. Now type su and a pop up will show up on your phone
22. Click grant permission yes
23. Now type mount -o remount rw /system
24. Type cd system
25. Type rm recovery-from-boot.p
26. Type cd etc
27. Type rm install-recovery.sh
28. Repeat steps 9 to 14 BUT SKIP STEP 12
9. Run the Odin executable "Odin3 v3.04.exe" in the Odin3-v3 folder
10. Power off your Samsung Galaxy S Relay 4G and connect the USB adapter to the computer and to your Samsung Galaxy S Relay 4G
11. Boot the Samsung Galaxy S Relay 4G into download mode by holding down Home, Volume Down and Power
NOTE: To confirm the device is connected and working, look for the blue COM box with the word Added!! inside
13. Press the dialog box labeled PDA and select the ClockworkMod-based Recovery named "cwm.tar.md5"
14. Press start and a blue transfer bar will appear on the device showing the recovery being transferred.
Phone will restart and you now have a custom recovery and are rooted.
Thanks Jay
Jay Dogg said:
Hello everyone, Im making a new rooting tutorial for the Samsung Galaxy S Relay 4G as the last tutorial [root]\{cm9} samsung galaxy relay 4g (updated 11/19) wasn't working for me. This tutorial will also have more details so will be easier to follow for the less technical.
BEFORE I START I AM IN NO WAY RESPONSIBLE IF YOU BRICK YOUR DEVICE. ROOTING YOUR PHONE WILL VOID YOUR WARRANTY..
1. Follow this guide for setting up the SDK. If you already have SDK, great move on to step 2
2. Download Drivers and install them. If you already have your drives installed move on to stop 3
3. Download Odin v3.04
4. Unzip the Odin archive. Put it somewhere you can find it, on the root of your C:\ drive is a good place.
5. Download ClockworkMod-based Recovery
6. Unzip cwm.tar.zip into Odin3-v3.04 folder that you unzipped in step 4
7. Download Super User
8. Place UPDATE-SuperSU-v1.25.zip on your phones sdcard.
9. Run the Odin executable "Odin3 v3.04.exe" in the Odin3-v3 folder
9.5 Go into your phone settings and click on Develop Option then make sure USB Debugging is checked.
10. Power off your Samsung Galaxy S Relay 4G and connect the USB adapter to the computer and to your Samsung Galaxy S Relay 4G
11. Boot the Samsung Galaxy S Relay 4G into download mode by holding down Home, Volume Down and Power
NOTE: To confirm the device is connected and working, look for the blue COM box with the word Added!! inside
12. Uncheck the box labeled Auto Reboot
13. Press the dialog box labeled PDA and select the ClockworkMod-based Recovery named "cwm.tar.md5"
14. Press start and a blue transfer bar will appear on the device showing the recovery being transferred
15. Once the recovery has been transferred you should see a Green PASSED. At his point disconnect the Samsung Galaxy S Relay 4G and remove the battery
14. Put your battery back in your Samsung Galaxy S Relay 4G and Immediately boot into recovery by holding down Home, Volume Up and Power
15. Once in recovery use volume down to select install zip from sdcard and hit power
16. Use volume down key to select UPDATE-SuperSU-v1.25.zip and hit power.
17. Now you are rooted but we are not done yet, Reboot your phone and make sure super user is showing up in the app drawer.
18. Now open up a cmd window by going to the start menu of windows and typing in cmd in the search or by clicking on run on the right hand side.
19. In the cmd window navigate to adb which is part of the SDK kit you installed in step one.
20. Once you are in the same directory as adb.exe type adb shell.
21. Now type su and a pop up will show up on your phone
22. Click grant permission yes
23. Now type mount -o remount rw /system
24. Type cd system
25. Type rm recovery-from-boot.p
26. Type cd etc
27. Type rm install-recovery.sh
28. Repeat steps 9 to 14 BUT SKIP STEP 12
9. Run the Odin executable "Odin3 v3.04.exe" in the Odin3-v3 folder
10. Power off your Samsung Galaxy S Relay 4G and connect the USB adapter to the computer and to your Samsung Galaxy S Relay 4G
11. Boot the Samsung Galaxy S Relay 4G into download mode by holding down Home, Volume Down and Power
NOTE: To confirm the device is connected and working, look for the blue COM box with the word Added!! inside
13. Press the dialog box labeled PDA and select the ClockworkMod-based Recovery named "cwm.tar.md5"
14. Press start and a blue transfer bar will appear on the device showing the recovery being transferred.
Phone will restart and you now have a custom recovery and are rooted.
Click to expand...
Click to collapse
Does this root method work for Jelly Bean 4.1.2 running Relay devices?
Sent from my SGH-T699 using xda app-developers app
Chrizuki said:
Does this root method work for Jelly Bean 4.1.2 running Relay devices?
Sent from my SGH-T699 using xda app-developers app
Click to expand...
Click to collapse
yes this should would with any firmware
Jay Dogg said:
Hello everyone, Im making a new rooting tutorial for the Samsung Galaxy S Relay 4G as the last tutorial [root]\{cm9} samsung galaxy relay 4g (updated 11/19) wasn't working for me. This tutorial will also have more details so will be easier to follow for the less technical.
BEFORE I START I AM IN NO WAY RESPONSIBLE IF YOU BRICK YOUR DEVICE. ROOTING YOUR PHONE WILL VOID YOUR WARRANTY..
1. Follow this guide for setting up the SDK. If you already have SDK, great move on to step 2
2. Download Drivers and install them. If you already have your drives installed move on to stop 3
3. Download Odin v3.04
4. Unzip the Odin archive. Put it somewhere you can find it, on the root of your C:\ drive is a good place.
5. Download ClockworkMod-based Recovery
6. Unzip cwm.tar.zip into Odin3-v3.04 folder that you unzipped in step 4
7. Download Super User
8. Place UPDATE-SuperSU-v1.25.zip on your phones sdcard.
9. Run the Odin executable "Odin3 v3.04.exe" in the Odin3-v3 folder
9.5 Go into your phone settings and click on Develop Option then make sure USB Debugging is checked.
10. Power off your Samsung Galaxy S Relay 4G and connect the USB adapter to the computer and to your Samsung Galaxy S Relay 4G
11. Boot the Samsung Galaxy S Relay 4G into download mode by holding down Home, Volume Down and Power
NOTE: To confirm the device is connected and working, look for the blue COM box with the word Added!! inside
12. Uncheck the box labeled Auto Reboot
13. Press the dialog box labeled PDA and select the ClockworkMod-based Recovery named "cwm.tar.md5"
14. Press start and a blue transfer bar will appear on the device showing the recovery being transferred
15. Once the recovery has been transferred you should see a Green PASSED. At his point disconnect the Samsung Galaxy S Relay 4G and remove the battery
14. Put your battery back in your Samsung Galaxy S Relay 4G and Immediately boot into recovery by holding down Home, Volume Up and Power
15. Once in recovery use volume down to select install zip from sdcard and hit power
16. Use volume down key to select UPDATE-SuperSU-v1.25.zip and hit power.
17. Now you are rooted but we are not done yet, Reboot your phone and make sure super user is showing up in the app drawer.
18. Now open up a cmd window by going to the start menu of windows and typing in cmd in the search or by clicking on run on the right hand side.
19. In the cmd window navigate to adb which is part of the SDK kit you installed in step one.
20. Once you are in the same directory as adb.exe type adb shell.
21. Now type su and a pop up will show up on your phone
22. Click grant permission yes
23. Now type mount -o remount rw /system
24. Type cd system
25. Type rm recovery-from-boot.p
26. Type cd etc
27. Type rm install-recovery.sh
28. Repeat steps 9 to 14 BUT SKIP STEP 12
9. Run the Odin executable "Odin3 v3.04.exe" in the Odin3-v3 folder
10. Power off your Samsung Galaxy S Relay 4G and connect the USB adapter to the computer and to your Samsung Galaxy S Relay 4G
11. Boot the Samsung Galaxy S Relay 4G into download mode by holding down Home, Volume Down and Power
NOTE: To confirm the device is connected and working, look for the blue COM box with the word Added!! inside
13. Press the dialog box labeled PDA and select the ClockworkMod-based Recovery named "cwm.tar.md5"
14. Press start and a blue transfer bar will appear on the device showing the recovery being transferred.
Phone will restart and you now have a custom recovery and are rooted.
Thanks Jay
Click to expand...
Click to collapse
I've done most of the instructions said and everything seems fine with my phone. I have SU and it is rooted, but I'm stuck on "25. Type rm recovery-from-boot.p" because when I type it in, it says that the rm failed because there was no such file or directory. Is it really important/necessary to have a custom recovery?
Chrizuki said:
I've done most of the instructions said and everything seems fine with my phone. I have SU and it is rooted, but I'm stuck on "25. Type rm recovery-from-boot.p" because when I type it in, it says that the rm failed because there was no such file or directory. Is it really important/necessary to have a custom recovery?
Click to expand...
Click to collapse
Quick answer is no you do not need the custom recovery but it is a good idea to have it. As far as step 25 goes make sure you are in the correct directory. Once you have gotten into your phone using adb shell type cd system. Then type pwd and make sure you are in /system. If you are in system type "ls" and see if the file "recovery-from-boot.p" is there. Repeat these steps for the "install-recovery.sh" file. Now if both file are gone off your phone you can Repeat steps 9 to 14 BUT SKIP STEP 12 or even better if the files didn't exist at all then your should be rooted and already have the custom recovery. You can check to see if you have the custom recovery by booting into recovery by holding down Home, Volume Up and Power or by typing adb reboot recovery but make sure you are not in adb shell.
I wrote this tutorial because the Samsung Galaxy Relay 4g I was rooting had these files "recovery-from-boot.p" and "install-recovery.sh" which was more or less a fail safe for the phones recovery. Every time the phone booted it was checking the recovery and replacing it with the stock recovery by using those two files. So my work around was to get the phone rooted and delete those two files then reflash the custom recovery.
This procedure worked perfectly for me, thanks. I just bought this phone for my Wife. It auto-upgraded to Jelly Bean OTA, and I was ready to root and load recovery. I'm now rooted, and took my first nandroid backup.
The only thing I had to figure out, was how to boot to download mode and recovery. I've done this procedure on many phones and tablets, including a Samsung Galaxy S2, but this phone was a little different. After pressing the volume key, home, and power, you have to release all buttons as soon as you see any text on the screen. For download mode, I had to immediately press volume up within 2 seconds, or it would continue to something else.
I'm curious about this clockwork recovery too. Was it originally written for another device? It works good. I just don't see it offered for this phone in Rom Manager.
Again thanks for taking time to type up this procedure, and for the extra steps at the end for the override.
CWM isn't in ROM Manager probably because we haven't submitted it to them
cannot cannot for the life of me get this phone to go in recovery. Basically stuck right at step 11. Nothing doing. I hold V down, power, home then I get a msg that tells me V down to power off and V up to start download. Anything I do, phone will just reboot. What am I missing?
devis said:
cannot cannot for the life of me get this phone to go in recovery. Basically stuck right at step 11. Nothing doing. I hold V down, power, home then I get a msg that tells me V down to power off and V up to start download. Anything I do, phone will just reboot. What am I missing?
Click to expand...
Click to collapse
Step 11 is to boot into download mode not recovery but in post 6 Jorakal said "The only thing I had to figure out, was how to boot to download mode and recovery. I've done this procedure on many phones and tablets, including a Samsung Galaxy S2, but this phone was a little different. After pressing the volume key, home, and power, you have to release all buttons as soon as you see any text on the screen. For download mode, I had to immediately press volume up within 2 seconds, or it would continue to something else." I didn't have to do it that way but if it worked for Jorakal it may work for you.
If that doesn't work for you, you can always try using adb to reboot into download mode the command is "adb reboot download", this will work for you but you may run into problems on step 14 if you can't boot into recovery using "Home, Volume Up and Power" because by the time you can use adb to boot into recovery the phone has already replaced your custom recovery with the stock one.
I'll try... thanks!
14. Press start and a blue transfer bar will appear on the device showing the recovery being transferred
15. Once the recovery has been transferred you should see a Green PASSED.
Click to expand...
Click to collapse
I conclude it is in Odin program.
But on the phone even when its finished in Odin, still white Downloading... And green : Do not turn off target.
Is it right, as I have some problems after reboot.
It is like crashing 3 or 4 times, you can see that on my video.
http://youtu.be/3V24FbY0jH8
I used Odin 3.07 and Super User 1.34
In phone I can see :
Qualcomm secureboot : enable - is that OK?
UPDATE:
All is working fine now.
I follow all steps again.
We don't need to do it with adb, all related commands to adb could be done in shell apk.
Regards and thanks for tutorial.
Jay Dogg said:
Hello everyone, Im making a new rooting tutorial for the Samsung Galaxy S Relay 4G as the last tutorial [root]\{cm9} samsung galaxy relay 4g (updated 11/19) wasn't working for me. This tutorial will also have more details so will be easier to follow for the less technical.
BEFORE I START I AM IN NO WAY RESPONSIBLE IF YOU BRICK YOUR DEVICE. ROOTING YOUR PHONE WILL VOID YOUR WARRANTY..
1. Follow this guide for setting up the SDK. If you already have SDK, great move on to step 2
2. Download Drivers and install them. If you already have your drives installed move on to stop 3
3. Download Odin v3.04
4. Unzip the Odin archive. Put it somewhere you can find it, on the root of your C:\ drive is a good place.
5. Download ClockworkMod-based Recovery
6. Unzip cwm.tar.zip into Odin3-v3.04 folder that you unzipped in step 4
7. Download Super User
8. Place UPDATE-SuperSU-v1.25.zip on your phones sdcard.
9. Run the Odin executable "Odin3 v3.04.exe" in the Odin3-v3 folder
9.5 Go into your phone settings and click on Develop Option then make sure USB Debugging is checked.
10. Power off your Samsung Galaxy S Relay 4G and connect the USB adapter to the computer and to your Samsung Galaxy S Relay 4G
11. Boot the Samsung Galaxy S Relay 4G into download mode by holding down Home, Volume Down and Power
NOTE: To confirm the device is connected and working, look for the blue COM box with the word Added!! inside
12. Uncheck the box labeled Auto Reboot
13. Press the dialog box labeled PDA and select the ClockworkMod-based Recovery named "cwm.tar.md5"
14. Press start and a blue transfer bar will appear on the device showing the recovery being transferred
15. Once the recovery has been transferred you should see a Green PASSED. At his point disconnect the Samsung Galaxy S Relay 4G and remove the battery
14. Put your battery back in your Samsung Galaxy S Relay 4G and Immediately boot into recovery by holding down Home, Volume Up and Power
15. Once in recovery use volume down to select install zip from sdcard and hit power
16. Use volume down key to select UPDATE-SuperSU-v1.25.zip and hit power.
17. Now you are rooted but we are not done yet, Reboot your phone and make sure super user is showing up in the app drawer.
18. Now open up a cmd window by going to the start menu of windows and typing in cmd in the search or by clicking on run on the right hand side.
19. In the cmd window navigate to adb which is part of the SDK kit you installed in step one.
20. Once you are in the same directory as adb.exe type adb shell.
21. Now type su and a pop up will show up on your phone
22. Click grant permission yes
23. Now type mount -o remount rw /system
24. Type cd system
25. Type rm recovery-from-boot.p
26. Type cd etc
27. Type rm install-recovery.sh
28. Repeat steps 9 to 14 BUT SKIP STEP 12
9. Run the Odin executable "Odin3 v3.04.exe" in the Odin3-v3 folder
10. Power off your Samsung Galaxy S Relay 4G and connect the USB adapter to the computer and to your Samsung Galaxy S Relay 4G
11. Boot the Samsung Galaxy S Relay 4G into download mode by holding down Home, Volume Down and Power
NOTE: To confirm the device is connected and working, look for the blue COM box with the word Added!! inside
13. Press the dialog box labeled PDA and select the ClockworkMod-based Recovery named "cwm.tar.md5"
14. Press start and a blue transfer bar will appear on the device showing the recovery being transferred.
Phone will restart and you now have a custom recovery and are rooted.
Thanks Jay
Click to expand...
Click to collapse
I had to struggle with two points. But got them afterwards. Hence it would be great if you update the instructions:
11. Boot the Samsung Galaxy S Relay 4G into download mode by holding down Home, Volume Down and Power
For me, I also had to need to hold down these buttons, but then after message text is coming up, I also then had to release all the buttons and then press Volume up within one second, 2 seconds are too late. Please for that reason just give a note mentioning this in case if its not enough.
please also complete the notice:
NOTE: To confirm the device is connected and working, look for the blue COM box with the word Added!! inside the message box
otherwise I was really confused because in the COM box there is no such text coming in it, and didnt know if I can go ahead or not.
Please check and rewrite the numbers in correct order after 14 - 15 - 14
also because of this:
16. Use volume down key to select UPDATE-SuperSU-v1.25.zip and hit power.
That was the most difficult part for me as I was getting the message: "E: failed to verify whole-file signature" and the installation failed. I found the solution after many google tries. which is in our case to restart the instruction from 15. and go ahead without failing each steps till 16.
Hence, note: In case of failure, repeat the steps from 15 again.
Jay Dogg said:
28. Repeat steps 9 to 14 BUT SKIP STEP 12
...
Phone will restart and you now have a custom recovery and are rooted.
Click to expand...
Click to collapse
Can I ask what the significance of running step 28 (the repeat step) is?
Is it necessary for recovery to work properly? I only ask because i installed the recovery following these steps up to but not including step 16, and then tried installing the new bootloader, modem, and latest CM nightly, but it's not getting past the CM splash screen
well I got CM to boot by just rewiping and reflashing, but I'm still curious about step 28. I find every phone can have their quirks and it's important to learn them if your'e going to be flashing
Do I need to root te device to flash other roms ? I've red somewhere that I don't have to do this on this device.
My device has the latest official jelly been, so it has the latest radio & bootloader.
edit: It this the correct order ? (I always wipe all partitions before flashing a rom, expect recovery):
http://forum.xda-developers.com/showpost.php?p=46578334&postcount=8
Ziida said:
Can I ask what the significance of running step 28 (the repeat step) is?
Is it necessary for recovery to work properly? I only ask because i installed the recovery following these steps up to but not including step 16, and then tried installing the new bootloader, modem, and latest CM nightly, but it's not getting past the CM splash screen
well I got CM to boot by just rewiping and reflashing, but I'm still curious about step 28. I find every phone can have their quirks and it's important to learn them if your'e going to be flashing
Click to expand...
Click to collapse
Because of these files "recovery-from-boot.p" and "install-recovery.sh" which was more or less a fail safe for the phones recovery. Every time the phone booted it was checking the recovery and replacing it with the stock recovery by using those two files. So my work around was to get the phone rooted and delete those two files then reflash the custom recovery. Because at this point when you reboot the phone to delete those to files they have already ran and you don't have a custom recovery, all you have is root which is what you need to delete those two files =). It appears some people didn't have these files because they had already rooted there phone be for or where not on the most current OTA. If they didn't have the files then they were done at step 17 and if they had tried to go further would of gotten a errors at steps 25 and 27. But if they had the files and stopped at 17 they would no longer have a custom recovery after they had rebooted the phone. So over all steps repeat steps are just to make sure you have a custom recovery installed.
Thanks Jay
Jay Dogg said:
Because of these files "recovery-from-boot.p" and "install-recovery.sh" which was more or less a fail safe for the phones recovery. Every time the phone booted it was checking the recovery and replacing it with the stock recovery by using those two files. So my work around was to get the phone rooted and delete those two files then reflash the custom recovery. Because at this point when you reboot the phone to delete those to files they have already ran and you don't have a custom recovery, all you have is root which is what you need to delete those two files =). It appears some people didn't have these files because they had already rooted there phone be for or where not on the most current OTA. If they didn't have the files then they were done at step 17 and if they had tried to go further would of gotten a errors at steps 25 and 27. But if they had the files and stopped at 17 they would no longer have a custom recovery after they had rebooted the phone. So over all steps repeat steps are just to make sure you have a custom recovery installed.
Thanks Jay
Click to expand...
Click to collapse
That's very informative. Thank you so much for the response! I guess I just didn't have to continue past step 17!
I get pit error: on heimdall and odin, what's the problem ?
Get PIT for mapping:
Complete(Write) operation failed!
Added!
edit: using another pc and it worked fine with heimdall (very easy to use).
Worked like a champ for me this morning, followed the steps closely. 4th phone rooted...still going strong...
Hello root experts!
I just downloaded all files needed for root and I've got one last question...after these 28 steps procedure whats about my personal data? It will be deleted? Like call log,sms, emails, settings etc... Or it will be untouched?
If no...please can You give me advice for any useful backup app
Many thanks in advance!
EDIT: Already rooted and everything seems to be fine
Having trouble getting superuser zip to intall
I keep getting signature verification failed. tried several places to get superuser zip; same error no matter where. Anyone had this issue?
Thx!
Any help would be much appreciated... Haven't toyed around with phones for some time but I must have gotten into the deep end with this Sony Xperia 5 II, not sure what to do here.
Using OrangeFox recovery, I must have unmounted or done something to the phone's /system mount point because I can't flash any ROMs or restore anything without /system available. While a "System" option does appear in the "Mount" menu's checklist, tapping on it does nothing and I can only mount "Data" and "oem".
Here's what's happening when I try to remount the system via adb:
mount -o remount,rw /system which returns:
mount: /system: mount point does not exist.
Out of curiosity I tried this as well if it's even related:
adb disable-verity but get:
Overlayfs setup failed with error No such device or address
verity not enabled - ENG build
Is there a way to mount /system as a partition given the above doesn't work?
Are you sure partition /system physically exists?
If it doesn't exist then re-flash Stock ROM.
Is there a way to check? And if it should exist, can it be created?
Currently the only partitions on the phone are metadata, Data and a pair of storage/sdcard1.
Prior to this issue (or before I mucked around in the recovery), I was able to successfully flash a ROM's system.img but cannot do the same now due to "no such file or directory".
As a result I'm suspecting it might have been there before, but could be wrong.
Ok I'll try getting the stock ROM tomorrow, at the moment the Sony Mobile Flasher tool by Androxyde is stuck on Sending getvar: product so the phone might even have trouble flashing via flash mode.
Are there any other known tools/programs for Sony devices to flash stock firmware with? Or a direct link to a flashable rom could work wonders.
Ok there was no luck using either the Xperia Flash Tool or Newflasher as they both yielded errors or just hang at an early stage in the ROM flashing, made sure it wasn't a driver or USB issue which begets the question...
Does the bootloader need to be re-locked? Currently at work but if there are some ideas worth throwing around I'm all ears.
Resolved, might as well say exactly what worked for me in case it happens to anyone else:
1. Perform a format through the recovery.
2. Download the right firmware through XperiFirm 5.6.1.
3. Move/Copy the downloaded firmware files into Newflasher 4.2. No making subfolders or anything, just move all these files into the same path the newflasher application is in.
4. Not sure if it was a necessary step but I used Unsin 1.13 to extract the boot_X-FLASH-ALL-2389.sin file created from step 2 which created an image (drag and drop this boot_x-etc-etc SIN file into the Unsin executable to extract it).
5. Place the boot_x-etc.img file created via Unsin into the Newflasher folder, just along with all the other files in the directory.
6. Ensure the Xperia 5 II is powered off. Hold the volume down key while plugging it into a USB 2.0 port until the phone's LED goes green.
7. Launch newflasher, and press f. For all other prompts, press n. You should see the stock firmware getting flashed in newflasher.
Will take a few minutes, but is an important step as it rebuilds the system, even going as far as restoring the bootloader to the stock one which you'll see can get booted into rather than a custom recovery as done in step 9 later.
8. Once step 7 is done, unplug the phone to turn it off (or press the power button until the LED goes away).
9. Hold both the power button and volume down keys, and let go of just the power button to enter the bootloader.
10. This is where the option to /mount system can be selected and was successfully mounted (a custom recovery like the one I had could not do this).
11. Now that /system is actually mounted, you can proceed to open fastboot from within the bootloader and go flashing whatever. For example, what I did immediately after mounting /system was open fastboot, plug my phone into the computer and ran all the commands in step 4 for this particular ROM: https://forum.xda-developers.com/t/...icial-lineageos-18-1-for-xperia-5-ii.4221435/
Pretty explicit, but it explains that all along it was just a matter of reflashing the stock firmware via newflasher which let me enter the default bootloader and mount /system without further problems.
Hope this helps anyone else in the future.