Hi guys, over the past few weeks, I have noticed that many people are having problems rooting their Jetstreams. So because of this, I thought I would put together an all in one guide to help alleviate everyone's problems.
So what this will show you how to do:
Unlock the bootloader
Flash a custom recovery
Grant root access
Prepare the device for S-OFF
Included files:
HTC Drivers
ADB
Fastboot
TWRP 2.4.1.0
SuperSU 1.51
Note: This guide is for windows only
Ok, so lets begin:
Download attached zip
http://www.mediafire.com/download/ao1ykdpx5jn2uni/Root_HTC_Jetstream.zip
Extract the zip to an appropriate place on your computer
Install the HTC drivers
Do so by double clicking the HTCDriver_4.2.0.001.exe from the zip
Run the RUU if needed
I am assuming you are on a completely stock HTC Jetstream with no modifications what so ever. I am also assuming you are on the latest software 1.30.502.1 for AT&T users or 1.26.631.4 for Rodgers users. If you are not, please download and run the latest RUU from the following website:
http://forum.xda-developers.com/showthread.php?t=2094375
Please note that running the RUU will completely WIPE your device of all personal data, so backup accordingly
To run the RUU, make sure the Jetstream is turned on and is fully booted into Android
Make sure "USB Debugging" is enabled under development settings
Make sure "Fastboot" is disabled under power settings
Simply attach the Jetstream to your computer with the appropriate USB cord
Double click on the downloaded RUU .exe file to run the program
If for some reason you cannot boot into Android, you can do the following:
With the device turned off, hold the volume down button and simple press the power button for a second or two
The device will boot into the bootloader, from there use the volume buttons to navigate to fastboot and the power button to select
Once in fastboot, connect the device to the computer with the USB cord and then double click the downloaded RUU .exe
Now lets unlock the bootloader
Please note that unlocking the bootloader will also WIPE your device
Go to http://www.htcdev.com/
Create an account if you do not already have one
Click on "Unlock Bootloader" and then "Get Started"
In the drop down box, select "HTC Jetstream"
Agree to all the legal terms
Follow all the instructions to obtain your unlock token
To easily do this:
Make sure "USB Debugging" is enabled under development settings
Make sure "Fastboot" is disabled under power settings
Connect the device to the computer with the USB cable
Navigate to the extracted folder of the attached zip
Hold the shift key and right click in the folder, then select "Open Command Window Here"
Type the following in the command window
Code:
adb reboot bootloader
Once the device has booted into fastboot, type the following in the command window
Code:
fastboot oem get_identifier_token
Copy the appropriate text according to the website and submit it
You will then be emailed an "Unlock_code.bin" and a link to continue the unlock process
Download the "Unlock_code.bin" and place it in the extracted folder from earlier
Now type the following in the command window
Code:
fastboot flash unlocktoken Unlock_code.bin
On the device you will be prompted to unlock the device, use the volume keys to navigate to "Yes" and use power to select
The device will reboot back into Android
Now lets flash a custom recovery
Connect the device to the computer with the USB cable
In the extracted folder open a command window by holding the shift key, right clicking, and selecting "Open Command Window Here"
Type the following in the command window
Code:
adb reboot bootloader
Once the device has booted into fastboot, type the following into the command window
Code:
fastboot flash recovery htc_jetstream_twrp_recovery_2.4.1.0.img
Once the custom recovery has been successfully flashed, type the following into the command window
Code:
fastboot reboot
The device will then boot back into android
Now lets get root
Connect the device to the computer with the USB cable
Copy the "SuperSU-v1.51.zip' to the root of you SD card
Go to the extracted folder, hold the shift key, right click, and select "Open Command Window Here"
Now type the following into the command window
Code:
adb reboot recovery
While at the recovery main menu, select the wipe option and wipe cache and dalvik cache
Next go back to the main menu and select install
Navigate to the SuperSU zip we placed on the SD card and flash the zip
Once it flashes, go back to the main menu and reboot back into system
The device will boot back into Android and the device will now be rooted!
So what now?
After completing the step above, you device should have an unlocked bootloader, and custom recovery installed, and also have root access. After having all of this you may now go on to install any custom ROMs you may want, however, I would recommend obtaining S-OFF to give yourself full control over your device.
This following link should help to explain what S-OFF is exactly:
http://forum.xda-developers.com/showpost.php?p=42455824&postcount=1
This next link is to the JuopunutBear S-OFF method:
http://forum.xda-developers.com/showthread.php?t=1906353
People I would like to thank:
DoomLoRD - for his initial work with rooting the HTC Jetstream
jmz - for giving us a custom recovery and hosting all the RUUs for us
TeamWin - for TWRP
Chainfire - for his amazing work with Android and SuperSU
Fuses and the rest of Team Unlimited - for giving us an S-OFF method
Disclaimer:
Just to be clear, unlocking and rooting your HTC Jetstream voids your warranty, so anything you do to it is your decision and I am in no way responsible for anything that happens to your device
great work!
@DNarsingh
Windows 8 64 finally can ADB to Jetstream and Sensation XL.
Thanks for driver file HTCDriver_4.2.0.001.exe containing within the zip you attached. The driver within htc_sync_setup_3.3.10.exe couldn't seem to get through.
Did a factory reset on my jetstream, and lost root. When I used CWM for recovery, I tried re-rooting using the guide in this thread. After another factory reset, root was still there, so I handed the jetstream to its new owner. However, the new owner has told me that the pen icon doesn't show up when using the pen. He did another factory reset (which took longer than usual), but still nothing. Anyone know what went wrong?
Notontherugman said:
Did a factory reset on my jetstream, and lost root.
Click to expand...
Click to collapse
I've never heard of a factory reset breaking root. The components that enable root usually exist on the /system partition and it is untouched by a factory reset.
The other root method (that I am unfamiliar) with is an insecure kernel. I don't know how this works, but I am pretty sure that a factory reset should not break it.
finniest said:
I've never heard of a factory reset breaking root. The components that enable root usually exist on the /system partition and it is untouched by a factory reset.
The other root method (that I am unfamiliar) with is an insecure kernel. I don't know how this works, but I am pretty sure that a factory reset should not break it.
Click to expand...
Click to collapse
I'm not a dev, and have just been following how-tos on XDA up to now (from back in the days of HTC HD2); therefore, I can't give details since I am inexperienced.
After the factory reset, Titanium Backup was denied SU, I could not browse the root directories/folders and all the software that needed root to work would not.
My question still stands: the pen icon won't show up. Anyone know what went wrong or what he may be doing wrong? In desperate need for help.
Notontherugman said:
After the factory reset, Titanium Backup was denied SU, I could not browse the root directories/folders and all the software that needed root to work would not.
Click to expand...
Click to collapse
Did you try to install the superuser app that you were formerly using from the market? My guess is that you lost the /data/app/su.apk that manages superuser, but that the binary is still in your /system/xbin/su directory somewhere. You probably removed the seemingly redundant /system/app/su.apk while using Titanium Backup, but are now left without a copy of it.
Notontherugman said:
My question still stands: the pen icon won't show up. Anyone know what went wrong or what he may be doing wrong? In desperate need for help.
Click to expand...
Click to collapse
If you are using Hive ROM then the pen icon will not appear, but the pen will still work with most apps. If you are using a different ROM then I really have no idea why the pen icon is not working. Are you certain that the pen battery still has a charge?
finniest said:
If you are using Hive ROM then the pen icon will not appear, but the pen will still work with most apps. If you are using a different ROM then I really have no idea why the pen icon is not working. Are you certain that the pen battery still has a charge?
Click to expand...
Click to collapse
Not using any ROMs.
I had removed most of the bloatware when I was using it, but the pen icon was there and I could use it just fine (before the factory reset).
Now, after the factory reset and the root method above, he tried his Flyer's pen on the Jetstream as well, so the battery is not a problem.
Notontherugman said:
I had removed most of the bloatware when I was using it, but the pen icon was there and I could use it just fine (before the factory reset).
Click to expand...
Click to collapse
Try using logcat to diagnose the problem. I suspect something will show up during boot or when you press where the pen icon should be.
http://www.xda-developers.com/android/help-your-developers-pull-a-logcat-when-issues-arise
I got the Jetstream back today.
I had managed to make a backup before using Clockwork Mod.
After the above rooting method, CWM is gone, and I can't use the backup files to restore using TWRP.
The link for CWM is gone. This is becoming extremely frustrating.
Notontherugman said:
I got the Jetstream back today.
I had managed to make a backup before using Clockwork Mod.
After the above rooting method, CWM is gone, and I can't use the backup files to restore using TWRP.
The link for CWM is gone. This is becoming extremely frustrating.
Click to expand...
Click to collapse
I have a copy of the CWM recovery.img. When I get home tonight, I will upload it for you.
I would recommend redoing your backup in TWRP afterward. In my experience, this recovery is a bit more up to date..
DNarsingh said:
I have a copy of the CWM recovery.img. When I get home tonight, I will upload it for you.
I would recommend redoing your backup in TWRP afterward. In my experience, this recovery is a bit more up to date..
Click to expand...
Click to collapse
Definitely.
And thank you!
EDIT: found CWM on an old hard disk. Managed to get ADB working. Restoring should fix most of the problems.
Thanks very much for the post
Sent from my SGH- I317M (Note II) running CM 11 using XDA Mobile App
every thing is ok
my device is fully rooted with twrp recovery and unlocked bootloader
but I have a problem.
I have sim card signal Icon but my device can not confirm simcard
what can I do?
Thanks!
Since I have rooted my device I can no longer access downloads from the google play store. I constantly get RPC:S-7:AEC-0 or -7 errors. I have tried all the tricks on various
forums but have had no luck. Do you have any fixes related to the jetstream?
Thanks, Mike
GROTEU said:
Since I have rooted my device I can no longer access downloads from the google play store. I constantly get RPC:S-7:AEC-0 or -7 errors. I have tried all the tricks on various
forums but have had no luck. Do you have any fixes related to the jetstream?
Thanks, Mike
Click to expand...
Click to collapse
It doesn't sound related to rooting. I would suggest a backup (there are many means of accomplishing this) and then a factory restore. If that doesn't work then install a custom ROM.
rooting issues
i have been trying to root my jetstream so i can get some lift out of it but when i get to the fast boot the system just hangs there any suggestions please if you know a complete way to root a htc from rogers i would love the support thanks
Related
This post is just my attempt to help less savvy users go from a fully locked/unrooted Rezound to unlocked, rooted, and running Ziggy's kernel. Really, this is just a list of links that should be followed in order (and maybe a few extra notes for clarification). Be sure to thank the respective devs for their efforts.
As of the time I'm writing this, there is no way to get the phone back to "Locked" once you've "Unlocked" it. The phone will show "Re-locked" if you relock it so know that until someone figures something out, Verizon WILL KNOW that you've unlocked your phone once you do it IF they bother to check and know how. It's your gamble, but to date, I've not heart of Verizon detecting root/unlock and refusing service to one person I can confirm. Said another way, you can "un-root" your phone (remove su and SuperUser), but that won't hide the more important fact that you've unlocked it. Consider this before continuing. Unlocking VOIDS YOUR WARRANTY. You accept responsibility for following this guide. Myself and other devs only provide information.
In general, here is what you will be doing:
Using the HTCDev.com site to submit your phones key and get an unlock.bin that you can use with fastboot to unlock your phone. NOTE: This WILL WIPE YOUR PHONE. I suggest using a temp-root method to first install Titanium or similar app, and do a app/data backup. This way when you're done, you can restore apps/data and be just about where you were when you started, only better.
Use the zergrush perm-root method to obtain permanent root and install SuperUser.
Install a customer recovery that will allow you to do a nandbackup and then install other roms/kernels (needed for the next step also).
Install Ziggys custom kernel which addresses some important issues for this phone and provides some other nice features.
NOTE: If you intend on flashing one of the newer ROMs ("newer" as of 2012-03-24) that require the 3.11.602.22 firmware, use Scott's directions HERE then come back and continue.
Now for the actual steps:
UNLOCKING - First visit THIS post for detailed instructions on how to unlock your device. This is required for permanent root and just about everything else following. This WILL VOID your warranty as the post says. This will also WIPE your device so again, I suggest first using THIS temp-root method so you can install an app like Titanium Backup to backup your apps/data.
PREPARING ADB - Once you have unlocked and your phone has rebooted, hit the home key to skip HTC Setup (no point doing it just yet really). Now hit, menu, settings, Applications, and check "Unknown Sources" (for good measure), then "Development" and check the box "USB debugging". I recommend then backing up a screen and un-checking "Start automatically", but that's my preference, not a requirement.
CONFIRMING ADB - At this point, I'm going to assume you already have ADB installed and known how to invoke the command because there are at least 9,999,999 tutorials online explaining this. Go ahead and open a cmd prompt and run "adb kill-server" and then "adb devices" and ensure that your device (if you see one, then you should be fine) shows up.
ROOTING - Now visit THIS thread and hit the less-than-obvious link titled "Download - OneClickRoot" to download the zip containing the tool. Follow the directions in that thread to permanently root your phone.
Boot fully into Android before proceeding.
RECOVERY
PREPARE RECOVERY.IMG - Visit THIS thread and download the attachment. Extract "recovery.img" from the zip and place it in a folder from which you can successfully run ADB. NOTE: If you haven't already, putting the adb.exe files folder in your PATH will let you run adb from anywhere. Same goes for fastboot. This makes life with Android tweaking/hacking MUCH easier.
FLASH RECOVERY 1/2 - Now "CD" into the folder (HERE you can find more about the CD command) with recovery.img and run the following command: "adb reboot bootloader". Once the phone has rebooted into the bootloader (a white screen with text menu, should say "*** UNLOCKED ***" at the top now). In white with a red background you should see "FASTBOOT USB". If so continue, if not, ask for help
FLASH RECOVERY 2/2 - The moment you run the following command, you should see a vertical bar on the upper-right hand corner of your phones screen. If so, it's working as expected. In your CMD window, run the following command "Now "CD" into the folder with recovery.img and run the following command: "fastboot flash recovery recovery.img"
REBOOT TO RECOVERY - If you have't touched the volume keys, "BOOTLOADER" is selected and pressing power will take you to the bootloader where you can then use the arrow keys to select "RECOVERY" and again press the power button to get into recovery. Otherwise, reboot any way you see fit and once running, use "ADB reboot recovery" to get into recovery easily.
KERNEL
DOWNLOAD FILES - First download the two files from THIS post (NOTE: The OP most may end up with more updated files, but as of the time I'm writing this, these are the way I suggest).
PUSH FILEs 1/2 - If you haven't already rebooted into recovery, review the previous steps and get your phone into recovery ("ADB reboot recovery" is my preference). Now "CD" into the folder containing the two files downloaded in the previous post. From here, I will use the file names as they were when I downloaded. Yours could be slightly different so adjust accordingly. In the recovery use the volume keys to navigate to the "Mounts" menu and then "Mount /sdcard". Use the Power button each time to select the menu option.
PUSH FILEs 2/2 - Now from your CMD window (the one in the folder containing the two kernel files), run the following commands: "adb push FlashMeInRecovery.zip /sdcard/" and then "adb push PH98IMGZIGGYUNSIGNED.zip /sdcard/PH98IMG.zip".
FLASH FILE 1/2 - Now use the back arrow (the capacitive one) to go back to the main menu and then select "Flash zip menu" and then "Choose zip from sdcard". You'll then get a list of sdcard contents. The file is likely toward the bottom. Select "FlashMeInRecovery.zip" and follow the directions to confirm flashing.
FLASH FILE 2/2 - Select the "Return" menu option, then "Developer Menu" and then "Reboot to bootloader". By default "BOOTLOADER" is already highlighted and you just need to use the power button to select it. The phone will now scan the SDCARD for "PH98IMG.zip" and when it finds it, you will be prompted to Press "<VOL UP> Yes" to flash the files.
If you get the notorious "MainVer Error", use one of the following guides to get past the error. NOTE: Neither of these are for the faint-of-heart and the first I consider easier, does carry some real danger if done incorrectly.
Option 1 - Follow the guide HERE <-- Requires the use of a HexEditor and one is recommended if you don't have a preferred one yet.
Option 2 - Follow the guide HERE <-- Requires modification of the PH98IMG.zip you're trying to flash and sometimes this can be problematic. Either way, it provides an excellent description of why the error occurs.
FINISH - Once the 2nd kernel file is flashed and you're prompted, press power to reboot. After your phone is running again, use the following command to rename the kernel file so it doesn't cause you trouble later in the bootloader (but still keep it handy): "adb mv /sdcard/ext_sd/PH98IMG.zip /sdcard/ext_sd/PH98IMGZIGGYUNSIGNED.zip"
If this guide has helped you and you want to show thanks, just hit the "Thanks" button at the bottom of this post. It's not a donation or anything like that, just a counter used here on XDA
I will try to keep this post refreshed as newer files become available, as things get easier, or things change. If you see an error/typo/concern with these directions, PLEASE PM me and don't muddy up the thread. If YOU will do this, "I" will not only try to maintain the post, but I will also try to add/maintain an FAQ post as needed.
Btw, in case you recognize me and are wondering why I've posted here, it's because my site is dead due to childish drama, I still want to help the community and this seems the most reasonable way to do so for now.
EDITS:
20111230_1804 - Added a hint and link about the "CD" command for users who aren't familiar with "DOS" like commands.
20120101_1923 - Added a direction to boot into Android after rooting.
20120101_2325 - Added warning about unlock/relock and warranty in BIG RED text.
20120208_1709 - Added instructions on how to handle the "MainVer" error.
20120324_1636 - Added note about using 3.11.602.22 based ROMs and linked to Scott's (CleanROM) directions.
Great guide, thanks! Worked just fine and wow this thing is fast as BALLS
Using SetCPU to tweak and monitor, any clue on what the best governor is for this kernel?
EDIT: Reading original post about kernel from Ziggy, "lagfree" governor is available, using that now.
Thanks!!!!!
may i flash kernels on custom rom
or has to be stock rooted?
qudwis said:
may i flash kernels on custom rom
or has to be stock rooted?
Click to expand...
Click to collapse
this kernel is based off of the one made for gingerbread, so as long as the ROM you're running is a Gingerbread ROM, you can, or should be able to use this kernel with it.
*EDIT* I believe it may matter whether the ROM is Sense or AOSP based as well. currently we only have sense roms so it doesnt much matter, but it will down the road.
one more question.
i have cwm for recovery. since cwm don't have developer menu,
do i need to change to Amon Ra recovery?
and if i do, how do i change?
The guide is clear, succinct, and accurate. Everything worked perfectly - thanks so much.
I could've got so much more work done over the last two days if I had a tutorial like this! Untold hours have been spent combing these boards to piece together this whole process. Thanks for taking the time to do this for everyone.
Seemed to work!
I only did the recovery / kernel part since I had done the rest previously. For some reason it partially wiped my phone storage and SD card. Directories are there, but nothing is in them. No idea what happened, but oh well.
At least now I can start messing with stuff.
How do you unroot from the HTCdev method? I need to return my Rezound and get a different one tomorrow. Can someone please point to the correct guide or tutorial? Thank you very much!
-brett
bal1985 said:
How do you unroot from the HTCdev method? I need to return my Rezound and get a different one tomorrow. Can someone please point to the correct guide or tutorial? Thank you very much!
-brett
Click to expand...
Click to collapse
Unrooting is just a matter of deleting "su" and uninstalling SuperUser, but it will hardly matter since your device will still be marked as "re-locked" if you use fastboot to relock it. There's no way at this point to hide that it's been tampered with and that's why I and most other devs have made such a point of clarifying that your warranty will be void one you unlock.
On the other hand, I can tell you that out of the 15,000+ users on my site and years in the Android community, I've never ONCE heard of Verizon saying "your device is rooted so we won't...."
Just uninstall SuperUser and do a factory reset/wipe and hope for the best. It's hardly worth their time to check and in the stores, more reps are too ignorant to know to check, let alone how to do it or if they do, they're likely unmotivated to do so since a warranty return won't go against them (unlike a return).
rainabba said:
This post is just my attempt to help less savvy users go from a fully locked/unrooted Rezound to unlocked, rooted, and running Ziggy's kernel. Really, this is just a list of links that should be followed in order (and maybe a few extra notes for clarification). Be sure to thank the respective devs for their efforts.
FLASH FILE 1/2 - Now use the back arrow (the capacitive one) to go back to the main menu and then select "Flash zip menu" and then "Choose zip from sdcard". You'll then get a list of sdcard contents. The file is likely toward the bottom. Select "FlashMeInRecovery.zip" and follow the directions to confirm flashing.
FLASH FILE 1/2 - Select the "Return" menu option, then "Developer Menu" and then "Reboot to bootloader". By default "BOOTLOADER" is already highlighted and you just need to use the power button to select it. The phone will now scan the SDCARD for "PH98IMG.zip" and when it finds it, you will be prompted to Press "<VOL UP> Yes" to flash the files.
Click to expand...
Click to collapse
This looks very clear and helpful. I'm not ready to use it yet, still need to study up on all this root stuff but thanks for posting.
Just wanted to point out that there may be a small and not so important typo. Both flash files are 1/2, shouldn't the second one be 2/2?
I have downloaded both files into my sd card, flashmeinrecovery.zip worked fine. The pmhimg.zip keeps saying aborted. I am running cwm, should I be running a different rom? What can I do to get the pmh zip to work?
I downloaded them via the qr codes, and they are in the download folder on my sd card. I did change the name on the second zip.
You have to put the ph zip in the root of the sd card. Not in a folder
sent from my newly unlocked Rezound
pwned3 said:
You have to put the ph zip in the root of the sd card. Not in a folder
sent from my newly unlocked Rezound
Click to expand...
Click to collapse
Ok, I did that. Now when I get into hboot, it just asks if I want to update, if I do, it updates, what I dont know, then wants me to reboot, and if I boot back into hboot, it wants me to update again. But I can power up normally. Is this correct or am I missing something?
Just reboot normally after flashing
sent from my cm7 rooted fire
And move the file. It will read it every time you go into the bootloader
sent from my cm7 rooted fire
Followed instructions and kernel would not flash. All steps completed without errors and still has same kernel. Any advice?
rainabba said:
Unrooting is just a matter of deleting "su" and uninstalling SuperUser, but it will hardly matter since your device will still be marked as "re-locked" if you use fastboot to relock it. There's no way at this point to hide that it's been tampered with and that's why I and most other devs have made such a point of clarifying that your warranty will be void one you unlock.
On the other hand, I can tell you that out of the 15,000+ users on my site and years in the Android community, I've never ONCE heard of Verizon saying "your device is rooted so we won't...."
Just uninstall SuperUser and do a factory reset/wipe and hope for the best. It's hardly worth their time to check and in the stores, more reps are too ignorant to know to check, let alone how to do it or if they do, they're likely unmotivated to do so since a warranty return won't go against them (unlike a return).
Click to expand...
Click to collapse
so I just unistall SU from the Market? Or do I have to go in with Root Explorer and delete the file? once that is done don't I have to lock the bootloader using that htcdev guide again?
remmy5r said:
Ok, I did that. Now when I get into hboot, it just asks if I want to update, if I do, it updates, what I dont know, then wants me to reboot, and if I boot back into hboot, it wants me to update again. But I can power up normally. Is this correct or am I missing something?
Click to expand...
Click to collapse
Following step 7 specifically prevents you from having to deal with that. So long as the PH file exists in your sdcard root, when you go into bootloader, you will be prompted. Once your running normally, just go follow step 7 and you'll be good to go.
I just went through the unlock and root it is fresh in the mind. These directions ASSUME AN SD CARD IS INSTALLED to the tablet and a WINDOWS OS!
Downloads, get them and put them in a folder on your computer:
Asus Unlock Tool download link from ASUS:
http://support.asus.com/Download.as...ck_Device_App_V6.apk#UnLock_Device_App_V6.apk
Fastboot EXE:
I got fastboot.exe when I downloaded Ultimate Backup Tool from here:
http://goo.gl/iOUwe
Unzip it so you have fastboot.exe
TWRP:
Get TWRP for TF201Jellybean, here is their page I have posted the download link below:
TWRP Page
On that page are instructions including a download link.THIS LINK IS FOR TF201 RUNNING JB BOOTLOADER ONLY! DO NOT USE IT IF YOU ARE NOT SURE WHAT YOU ARE RUNNING STOP NOW!
TWRP Download for TF201 running STOCK JellyBean OS:
http://techerrata.com/file/twrp2/tf201/openrecovery-twrp-2.3.1.0-tf201-jb.blob
MD5 Checker:
When TWRP is downloaded you can compare the MD5 hash of what you downloaded to confirm it is the a good download. If you don' do this and flash a bad copy of TWRP your tablet is now garbage. You can find something like winMD 5 generator:
http://www.winmd5.com/download/winmd5free.zip
Unzip the above download and run WinMD5.exe to generate an MD5 hash of the TWRP file you downloaded. Compare it to what it says the files MD5 hash is on the download web page. If I remember correctly I had to manually type in the MD5 hash from the page because it was an image I couldnt just copy. Or you can just visually verify with the one generated by winmd5.
Once the MD5 is verified rename the TWRP you downloaded to TWRP.blob just to shorten the name for scripts later and copy it to where you have fastboot unzipped.
ADB command:
I got ADB from several sources but this "root method" http://forum.xda-developers.com/showthread.php?t=1886460 from bin4ry is what I have been using: (And no, it doesnt work for the prime because the exploit he uses to run the device in emulator mode doesnt work for us)
Download bin4ry's root tool to get the ADB file
SuperSU:
Finally download SuperSU zip file from:
http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip
How To Use The Downloads:
Unlock Device:
First we need to unlock the device. Copy the unlocker APK to the root of your SD card for your tablet via the USB cable or putting the SDCARD in to your computer directly or with the ADB PUSH command if you know how to do that. Run the built in file explorer on our tablet and browse to the SD card (/Removable/MicroSD). Tap the Unlock APK to install. Once installed run the Icon for the unlocker and follow directions. There are several warnings etc.. You will need wifi connected and it will unlock your device and VOID YOUR WARRANTY!.
The unlock will take a few minutes and reboot one or more times. When it is successfull you will see a notice on device boot up that says the device is unlocked.
Flash TWRP:
Once unlocked, power it off. Once off power it on by holding BOTH volume down and power buttons. When you see the menu appear the first option is RCK. press Volume Down to change the cursor to be over the USB logo (two presses of the button) and press volume up. This puts your device in fastboot mode
Back on your computer you should hopefully see a successfull driver install for fastboot. I got all my drivers from downloading and installing the Android SDK so you may or may not need to do that. Android SDK
If all is prepared and you are in fastboot with drivers loaded:
On your computer hold shift and right click on the folder where fastboot and the twrp.blob file are and you will see a context menu. Click on "Open Command Window Here" (Vista + only or if you installed powertools on 2000/XP)
If you don't get the command window here option then you will have to open a command prompt. Open the run dialog and type CMD and hit enter. This will get a dos command windows. Use the change directory (CD) command to change the current folder in the DOS window to where your fastboot file and TWRP.blob are.
In the command window copy and paste the following line:
fastboot -i 0x0b05 flash recovery twrp.blob
and hit enter
Let it runs its course. When done I had a black screen with ASUS in the middle and a blue-ish bar across the bottom that was filled. I had to hold power until it rebooted. ( I waited about 5 minutes with that blue bar filled before looking up onilne to power off. I would recommend waiting a couple of minutes to be sure/safe)
Install SuperSU:
Once I confirmed my Stock OS loaded I copied the Super SU zip file we downloaded above over to the device via the USB cable to the root of my SD card, or by inserting SDCARD in to my computer and copy it over to ROOT of card or with ADB PUSH. Once the copy completes shutdown the device again.
Once off, power it on and press and hold both the power buttons and volume down again. When the menu appears you should already have RCK (recovery) highlighted so press volume up to load TWRP recovery.
OPTIONAL - BACKUP IF YOU WANT TO:
In TWRP there is a backup option. I chose to backup to my SD CARD and made sure to backup everything and generate an MD5. It takes a While but you can flash this back ANYTIME to put your device back to the STOCK JB OS without root. You can use the backup anytime you like to preserve your devices COMPLETE STATE. Just use the restore option in TWRP to put it back.
To flash root, once TWRP loads, the top left option is "Install" tap that.
You will see a few choices, select the radio button to install from SD card (external source it may say). Tap the super su zip file: Superuser-3.1.3-arm-signed.zip to choose it.
Slide the slider at the bottom to the right.
This will flash superSU to your device. When successfully done, reboot (flash should only take a few seconds).
When you boot up SuperSU is installed.
To test root with ADB:
Your tablet must be plugged in to the USB port of the computer of course.
If you installed the SDK tools ADB is there or use the one from bin4ry's root tool as follows:
Unzip the downloaded root tool from bin4ry mentioned above. Use the shift and right click method in explorer on the "STUFF" folder for the unzipped files or use the command windows to change directory of the unzipped folder and further in to the "STUFF" folder.
In the command windows type:
adb shell
<hit enter>
after a few seconds you should see a $ prompt and your are in to the console of your tablet.
Type:
su root
<hit enter>
Superuser will prompt you to grant root permissions and I set the setting so it doesnt prompt me every time.
Your prompt will change to # and thats it, you are root.
I don't seem to have the command sudo on my tab so every time I want root in a terminal I type that su root to get the # prompt.
Any apps that need root can now ask for it, you will get that same "Grant" prompt and do so if that is what you want.
ADB will now yield Root when you type: SU root and hit enter (grant root privs in the popup)etc...
Final thoughts:
There are other ways to copy content to the device such as using ADB PUSH etc... and I am sure this could be mostly if not all scripted but now that my tablet is rooted I am not going to write one and flash SuperSU over and over and possibly screw up my device. Follow the directions above and you will be successfull. If someone wants to write a script based on the above knock yourself out.
I HIGHLY recommend checking ALL MD5 hashes of downloads to confirm you got what you were supposed to. This will help prevent bricks.
Nice to see another guide on unlocking and flashing TWRP
McJesus15 said:
Nice to see another guide on unlocking and flashing TWRP
Click to expand...
Click to collapse
I was thinking a "how to root without unlock" one should be next....
hx4700 Killer said:
I was thinking a "how to root without unlock" one should be next....
Click to expand...
Click to collapse
Haha we have to wait for the amazingly smart people here to find an exploit for Jelly Bean. Although unlocking and flashing a custom rom is the way to go
Sent from my Zio using xda app-developers app
McJesus15 said:
Haha we have to wait for the amazingly smart people here to find an exploit for Jelly Bean. Although unlocking and flashing a custom rom is the way to go
Sent from my Zio using xda app-developers app
Click to expand...
Click to collapse
Yeah, the How to was going to be:
Step1) You can't.
So you finally did it... Did your warranty run out or did the frustration finally get to you?
I'm still holding off for now. In a way its a good thing an exploit hasn't been found, it means google have made the system fairly secure.
Next weekend I'm going to give finding an exploit one last red hot go. Failing that (and I'm sure i will) I'll be joining you.
abazz said:
So you finally did it... Did your warranty run out or did the frustration finally get to you?
I'm still holding off for now. In a way its a good thing an exploit hasn't been found, it means google have made the system fairly secure.
Next weekend I'm going to give finding an exploit one last red hot go. Failing that (and I'm sure i will) I'll be joining you.
Click to expand...
Click to collapse
I wanted to flash the Energy rom because of the near double quadrant scores people were posting. Little did I (or the chef) know that the Kernel was set to 1.8GHZ and constantly running 1.6. CPU throttling did little to inhibit that and even if you set it back to 1.4 it still ran 1.6 when max CPU was needed The back cover temp went from 90 deg while playing an interactive game for 20 minutes to 108.5 deg when playing the same game for 20 minutes. I had to think that was compromising stability and longevity as well as battery life so I flashed back my stock backup I made via TWRP and rooted as above.
I wouldnt mind going back when the kernel is more controllable. I'm actually playing with backtrack 5 now that I am rooted and EDS with mounts to truecrypt volumes so glad I am rooted, would have rather not voided the warranty
I think the policy should be that if you unlock things like the screen and wireless etc.. should still be covered but since they can't control overclocking etc... those kinds of issues are not.
Between 3 kids events, Holiday stuff I barely have the time to do the things I want to do let alone invest time in hacking this device =/
Thanks for the guide. Picked up a second hand Prime + Dock online with a locked boot loader. Following your guide I had it unlocked, rooted, and with CM10 in about half an hour or less.
Thanks!
Sent from my One X using xda premium
jetpackjeff said:
Thanks for the guide. Picked up a second hand Prime + Dock online with a locked boot loader. Following your guide I had it unlocked, rooted, and with CM10 in about half an hour or less.
Thanks!
Sent from my One X using xda premium
Click to expand...
Click to collapse
Glad it was helpful.
I guess I need to go look in to CM10, I see plenty of people using it and talking about it.
hx4700 Killer said:
Glad it was helpful.
I guess I need to go look in to CM10, I see plenty of people using it and talking about it.
Click to expand...
Click to collapse
As far as I know the kernel issue is fixed. Androwook never had the issue. It'll still get hot but not enough to cause concern
Sent from my Zio using xda app-developers app
worked for me :thumbup:
Sent from my Transformer Prime TF201 using xda app-developers app
And for me, didn't get much easier - or idiot proof
Thanks worked perfectly, I'm on CM10 now
Btw, you should change this line (because it's kinda wrong):
Let it runs its course. When done I had a black screen with ASUS in the middle and a blue-ish bar across the bottom that was filled. I had to hold power until it rebooted. ( I waited about 5 minutes with that blue bar filled before looking up onilne to power off. I would recommend waiting a couple of minutes to be sure/safe)
For this part the blue bar across the bottom did show up but not the ASUS logo, for me the tablet stayed on the same page with the USB logo and the other stuff and the blue bar across the bottom (not the Asus logo).
wrong thread
I have always been locked, and RMAed previously. I was able to successfully do this last night, thanks for the links.
Yay! After reading the forums and triple checking every thing I finaly got ROOT!
Thanks! Now I'm off to install the Energy Rom and hopefully enjoy GTA on a 42" TV with a USB controller
Fail
Doesn't work for me. I'm trying to switch to TWRP from an ever flakier CWM that won't do a backup. I'm already unlocked and rooted but still with stock ROM (which won't update any more because I'm rooted.)
The fastboot flash finishes ok but when I try to boot into recovery I get the message that it is loading the recovery kernel and then it just boots into Android. I have no recovery at all now which is kind of scary.
(God I hate this device for noodling with. Whenever you miss a beat you're looking at a 5 minute uninteruptable boot/shutdown cycle to try again. Everything outside of the Andorid zone itself is so baroque, archaic and intricate that feels like Windows 1.0. More than once mine has come within a nat's ass of being introduced to the wall at high velocity.)
---------- Post added at 11:59 PM ---------- Previous post was at 11:28 PM ----------
DonGateley said:
Doesn't work for me.
Click to expand...
Click to collapse
Oh, how utterly silly of me. Because I rooted long ago I didn't get the JB upgrade OTA so I'm still with ICS. The blob I needed was
http://techerrata.com/file/twrp2/tf201/openrecovery-twrp-2.3.3.0-tf201-ICS.blob
(At least I determined that flashing the JB blob onto ICS is not catastrophic.)
Maybe I'm not the only one in this state. It might be a good idea in the text to tell others of the ICS option.
The reason I'm here is that I want to install CM10 so I wanted to back up first. When I do that upgrade I assume this ICS TWRP will cease working and I will then need to fastboot flash the JB blob, right? Or might I have a "Can't get there from here" kind of problem?
Thanks for the links and write up.
2 questions.
Do I need an SD card or is the internal storage ok to use.
And, what part of this process roots the device?
Thanks!
**EDIT**
Never mind, I am a bonehead. I had my prime replaced due to a camera defect, so they shipped me a new one running JB.
So I have been away from teh forum a couple of months...didn't realize a way to get around locked, un-rooted, JB had been found.
Thanks again!
Sent from my Transformer Prime TF201 using xda app-developers app
Thanks for writing this up, I can't thank you enough. About a month ago I hard bricked my prime and had to send it in to Asus to have it repaired (thankfully I didn'y get charged). I tried installing twrp but didn't check the md5; this was well written. Wish I could give you a hug.
I know maybe some people will think I'm dumb now or something... But I want to ask before I begin and maybe brick it
So this really WORKS with the LATEST OTA update from Asus? I searched everywhere for days/weeks/months already and found this today so I'm a little bit sceptic, hope you understand me.
Keep in mind bootloader unlock will not work if you have done the latest OTA update without previously using supercid. See bootloader unlock guide below for more details.
This procedure is designed to be EXTREMELY EASY and for people using windows. Following this guide will give you the knowledge you need to use ADB and Recovery menus in order to flash all of the ROMs, Kernels and APK (apps) files that you want. I am not responsible if anything undersireable happens in this procedure that makes you sad, poo yourself or ends the world.
Even if you have accidentally formatted your internal storage and you have no files on your phone, this section is down the bottom of the thread. Only follow this if you have no access to your phone and have nothing installed on your sdcard. For everybody else simply follow from step 1.
WINDOWS DRIVERS
You will need the USB drivers for your phone to communicate with your computer. You can search around and get these drivers separately or if that is not possible then please download and install The HTC Sync Manager from here
UNLOCKING YOUR BOOTLOADER
Since the new method came out, it is ridiculously easy to unlock your bootloader now. If you haven't unlocked your bootloader than please visit this thread and follow the instructions. I found this video on youtube that will make this process easier for you too.
INSTALLING ADB/FASTBOOT (SDK) (Please read this even if you have already installed this)
I would recommend following the guide to install adb (sdk) I have included below. If you have already done this step then keep in mind you should always have sdk updated and to make life easier rename your 'platform-tools' folder to something easier, for example rename the folder to android-adb. Now copy the 'android-adb' folder to a convenient location on your PC e.g: root of the C: so it will now look like this c:\android-adb *If you're having trouble locating this folder it will usually be here c:android-sdk-windows\platform-tools or something along those lines* At this stage the Windows’s Path Environment Variables will now have to suit this change, which in this case is: ;C:\android-adb - If you would prefer to leave things as they are than so be it and continue reading.
If this is all sounding too hard than you really need to start again and follow the EASY!!!!!! guide below
Make sure you have SDK installed and updated. If you haven't already than follow this extremely easy guide
DOWNLOADING REQUIRED FILES FOR FLASHING
(Download the following items listed below)
1. CWM Recovery This is what you will be using ALL THE TIME to flash ROMs and Kernel Modules. There is an alternative recovery called TWRP which can be found here but I am not using that right now so for the purpose of this guide please use CWM, if for some reason you need to use TWRP then the steps will be very similar just look on screen for the right area and touch the screen to select, pretty straight forward right?
2. Your desired ROM I would 100% recommend ViperDNA from HERE if not you can grab a different one from HERE or HERE
3. You now need all required kernel files you are planning to use with the ROM you have selected. If you don't have the kernel installed correctly you will face bugs, the most common is WiFi not working correctly (keeps searching) or something else like that. Now for the Droid DNA at the moment the kernel is broken down in to 2 parts. The first file is kernel modules and the second file is the the boot.img. Now whatever ROM you choose to download and install, it should already be using a specific kernel. When you flash a ROM the kernel modules will already be installed for the specific kernel the ROM is using.
For example If you listened to my advice and are going to use ViperDNA, this ROM already comes with the kernel modules required for the kernel it is using. The only thing that is left for you to do is download the second part of the kernel which is the boot.img file. Every kernel needs both the kernel modules and boot.img files to work 100% without fault, and every kernel has different modules and a boot.img that will only work for that specific kernel.
Each ROM should give you a download link for the required boot.img so just make sure to read the first few posts - If you are planning to use ViperDNA then it can be found on the first page post number 2 of the ViperDNA thread and it is named Stock DSB System Write Boot.img -
* If that wasn't already clear enough I would like to say that if you are download a complete kernel zip separately (which you can do) then you will get both files required. The first is the "already included in the ROM" kernel modules and the second file will be the boot.img - You can find all of the different kernels here - as you can see in this list the kernel included in ViperDNA is the one named "[KERNEL]Droid DNA Cubed Kernel Stock" - Once you have finished installing a ROM then I would recommend having a look at some different kernels if you want. Down the very bottom of this post I have included instructions on how to flash a kernel so please check it out.*
Now read this next part carefully. before doing anything else, I want you to prepare the files that you are going to be flashing with ADB.
PREPARING FILES FOR FLASHING
1. ** Using your computer, unzip your CWM Recovery zip and move the recovery.img to your platform-tools folder which you may or may not have renamed by now. this is where adb and fastboot.exe files are. for example If you have followed the guide I provided it will be c:\android-adb if not it will be whatever you have named it as, and wherever you have installed it to. Usually c:android-sdk-windows\platform-tools or something along those lines. I'm assuming by this stage you have changed the Windows’s Path Environment Variables, if not then you really should be following the very simple guide above!
(if you don't have a zip program, use this one)
2. ** Next I need you move the boot.img (for your kernel) to the same location you just moved your recovery.img (If you have followed my advice then you can get this file from the first page of the ViperDNA thread) if you didn't then the boot.img file might be on the first page of your desired ROM. *If you have downloaded the same kernel used in the ROM, but as a complete zip then you will need to unzip the kernel zip to access the boot.img and continue as above*.
Do not close the folder where you have copied these files, simply leave it open
3. ** Now connect your phone to a USB port. Sometimes it's best to stick to USB 2 rather than USB 3. Copy and paste the ROM.zip (Whatever the name of your ROM is, you don't need to rename it ) file that you want to flash over to your phone (make sure to not accidentally drop it in to an already existing folder) So as soon as you open the contents of your device it should be pasted right there - Once this is complete disconnect the phone and switch it off.
4. ** Boot your phone in to bootloader by holding down the "power button" and the "volume down" key at the same time until you see the bootloader screen on your phone. Now press the power button once to make sure you're in fastboot (If you don't your phone will not be found by ADB and will be constantly "waiting for device") - Now connect your phone to your computer again and continue reading
5. ** Back to your computer, while still in the same folder you have copied your recovery.img and boot.img I want you to hold the shift button at the same time as right clicking on a blank space inside the folder and click on "open command window here"
FLASHING YOUR FILES IN FASTBOOT
Now you are ready to flash your files. Starting with your recovery.img file and then followed by your kernels boot.img - In your command window type the following commands
1. ** To flash a recovery you will need to type**
fastboot flash recovery recovery.img
2. ** To flash your kernels boot.img you need to type**
fastboot flash boot boot.img
Before flashing the boot.img, you can in fact flash your ROM.zip with the instructions given below. However, it is strongly recommended to do it before you flash the boot.img. This is the standard procedure that should be used for every single ROM.
USING CWM FOR THE ROM INSTALLATION AND A CLEAN WIPING PROCEDURE
Go back to your phone and scroll down to where it says recovery and hit the power button. Your phone will now reboot in to CWM Recovery. (If you can't see the recovery option then you might be in the main bootloader menu screen, try pressing the power button once to change back to fastboot). Your phone should now reboot and display a white HTC screen and up the top it will read "Entering Recovery" - After it has finished you can now navigate through CWM Recovery by using the volume keys and pressing the power button to enter. Some versions of CWM you can also touch the screen to make selections. Lets begin
*WARNING* Although you don't have to, but if you do choose to use the recommended Step 3 which is found below, it will wipe all of your games and apps including saved game data and such. Don't worry all of your photos and music will be fine. Make sure to sync your contacts with your Google account**
1. Scroll down to -advanced and hit power, then do as follows
- wipe dalvik cache
-***go back***
2. Scroll down to -mounts and storage and hit power then:
-format system
-press your back key on the phone to go back
3. Scroll down to -wipe data/factory reset and hit the power button
"you can skip this process but it is a highly recommended one if you want less bugs in the ROM" (If you decide to skip make sure you you also -wipe cache partition which is in the same menu)
4. Scroll down to install zip from sdcard and hit power and then:
-choose zip from sdcard. (Locate your ROM.zip and hit power)
- Wait for this process to finish or follow on screen prompts from here on.
- go back to the main menu and reboot your device if it isn't already
This method will work with every other zip file that is flashable through CWM including kernel modules. You will not however need to follow all of the steps for wiping and such, simply just start from step 4
This is the end of my guide!. If you already have a ROM installed and you want to change the kernel, then scroll all the way to the bottom of this post
__________________________________________________________________________________________________________________________
*NOTE* KEEP SCROLLING DOWN IF YOU ARE LOOKING AT HOW TO FLASH A DIFFERENT KERNEL. THIS SECTION IS FOR PEOPLE WHO HAVE ACCIDENTALLY FORMATTED THEIR INTERAL STORAGE. OR FOR ANY OTHER RANDOM REASON YOU CAN'T USE A COMPUTER TO DROP AND DRAG FILES TO YOUR PHONE.
Place desired ROM, kernel modules, recovery files, or APK (apps) files inside the same folder your adb/fastboot.exe files. It's usually found here c:android-sdk-windows\platform-tools or something along those lines unless you have moved or renamed it. If you are having trouble then please follow the ADB installation guide I have listed at the beginning of this thread.
Now while your phone is booted in Android and you make sure to have USB Debugging on, we are going to push these files depending on the file type by typing in commands:
adb push ROM.zip /sdcard/ROM.zip ***replace the word ROM with the exact name of the file you are pushing***
For example if you were using ViperDNA ROM you would type: adb push ViperDNA-version2.3.zip /sdcard/ViperDNA-version2.3.zip
And if it was a kernel (boot) file you would change the name respectively. For example: adb push cubedversion1000.boot/sdcard/cubedversion1000.boot
Now for applications such as games etc. You can either install the game directly or push the file to you phone to be installed later. Personally I always like to install from my phone so I always just push the file. But I will give you both options. ***To clarify if you are confused right now: adb push will copy any file to the phone, whereas adb install will only accept an apk file, and will install it onto the device***
To install an apk, it is quite simple, however it has a different path than what we have spoken about previously. The files will automatically push install themself in the correct area with your current installed apps .
If you want to install apps then you would type:
adb install apkfile
***For example if it is the game temple run, it would look like this: adb install templerun.apk
If you would prefer to manually install the game from your phone than you will need to push the file like we have mentioned already with the other file types:
adb push templerun.apk/sdcard/templerun.apk
Now remember if your phone is working correctly you can simply copy and paste all of these files directly to your phone and then flash in recovery for your ROMs or if you want to install apps you would then use a file explorer and locate the apk on your sdcard of the phone and then install it all from your phone. This was simply written for people that have no files on their sdcard due to accidental formatting of internal memory
INSTALLING ANOTHER KERNEL
If you have flashed a ROM and do want to use a kernel that isn't included with your ROM, then you can get another one from HERE Now this process is exactly the same as the stuff you have already done. Instead you will need to flash both of the kernel files included in the kernel zip file.
The first part is identical to what you did earlier. Move the boot.img file to the same place I mentioned earlier in this guide, and flash it the same way I mentioned in fastboot. This time the path will need to be changed because it is a boot file not a recovery file. So use this command: fastboot flash boot boot.img
In this second part move the kernel modules file to your phone and do exactly the same as you did in order to flash the ROM in CWM Recovery as mentioned earlier, only this time start from step 9 section 4.
That is all. Keep in mind things like wifi might not work if you forget to flash the kernel modules! - Just be sure it is always a 2 step process.
*Credits*
nitsuj17 for the greatest ROM on our phone ViperDNA
Jailbreak Eye for the wonderful ADB guide
DroidModd3rX for his video
dsb9938 for his awesome kernel work
jcase and beaups for their unlocking methods
htcdev.com for the unlocking
All of the fantastic developers for Android
Good guide. I would suggest adding a link to unlocking the phone because you have the about everything else. I really like that you included changing PATH and such in your guide because a lot of people kept getting the adb not found stuff.
I need a video. Its hard for me to learn so much by reading, esp when you could brick your phone.
good write up though!
Followed instructions and it says
sending 'recovery' (6944 KB)... OKAY [ 1.162s]
writing 'recovery'... OKAY [ 0.760s]
finished. total time: 1.924s
Then i go back to the recovery and go to it, does the HTC recovery..Also going back into the boot screen, the top says unlocked but also now says tampered on top.
treahuggs said:
I need a video. Its hard for me to learn so much by reading, esp when you could brick your phone.
good write up though!
Followed instructions and it says
sending 'recovery' (6944 KB)... OKAY [ 1.162s]
writing 'recovery'... OKAY [ 0.760s]
finished. total time: 1.924s
Then i go back to the recovery and go to it, does the HTC recovery..
Click to expand...
Click to collapse
I would reboot the phone in to bootloader mode and then press the power button once to switch to the fastboot menu. Now scroll down to recovery again and press the power button. If this doesn't work than try flashing the recovery again using the step for it. When you do in fact click on recovery in your bootloader, does it reboot in to a white HTC screen that says up the top Entering recovery?
A video would be extremely tedious to make for this guide. If you have already unlocked your bootloader than the bricking of this device would be drastically minimised. I wouldn't worry too much at this stage.
uppon2 said:
I would reboot the phone in to bootloader mode and then press the power button once to switch to the fastboot menu. Now scroll down to recovery again and press the power button. If this doesn't work than try flashing the recovery again using the step for it. When you do in fact click on recovery in your bootloader, does it reboot in to a while screen that says up the top Entering recovery?
A video would be extremely tedious to make for this guide. If you have already unlocked your bootloader than the bricking of this device would be drastically minimised. I wouldn't worry too much at this stage.
Click to expand...
Click to collapse
Yes it says that.
Let me ask some questions, you say copy the complete ROM.zip over to the phone. Where at on the phone? Does it have to be named ROM.zip?
Does the CWM need to be copied over too? Using your guide to download the viper files and the second boot.img is confusing since the .zip with the viper has a boot.img with it, should we use that, ignore it, or what?
I thank you for taking the time to write a guide but with so many variables that are being used and referenced, there needs to be more specific instructions.
ALL i want to do is use mt titanium backup to get my old apps and app data on my DNA. Is it really this many steps just to gain root access to the DNA? With the Razr maxx it was just connecting it to the computer in debugging mode, and running a batch file.
:victory:
---------- Post added at 06:21 PM ---------- Previous post was at 06:15 PM ----------
:silly:
treahuggs said:
Yes it says that.
Let me ask some questions, you say copy the complete ROM.zip over to the phone. Where at on the phone? Does it have to be named ROM.zip?
Does the CWM need to be copied over too? Using your guide to download the viper files and the second boot.img is confusing since the .zip with the viper has a boot.img with it, should we use that, ignore it, or what?
I thank you for taking the time to write a guide but with so many variables that are being used and referenced, there needs to be more specific instructions.
ALL i want to do is use mt titanium backup to get my old apps and app data on my DNA. Is it really this many steps just to gain root access to the DNA? With the Razr maxx it was just connecting it to the computer in debugging mode, and running a batch file.
Click to expand...
Click to collapse
1. Sorry I didn't mean to put complete at the beginning of ROM.zip and no you do not need to rename the ROM zip file
2. To avoid confusing anybody, please ignore the boot.img file inside of the ROM
3. If you read the whole guide you will know exactly what to do with CWM file and every other file
4. It is unfortunately an annoying process to root this phone. However if you follow the guide completely you will have root. I'm not sure about a batch process for the DNA, sorry. It makes it very hard that we can't write to system easily, if and only if we gain this access will we be able to pack the the files which installs the su binary and busybox in to the kernels like you would find with other phones such as Samsung etc. Then you would be able to just flash a kernel and have root, without installing a custom ROM. (I could be wrong and would like further education here from other users as there might in fact be a file flashable through fastboot or recovery that gives you root and nothing else, I simply don't know about this file)
Ok where do you put the downloaded files onto the phone. When you plug the phone in you get many different windows pop up that is gives you access to different parts in the phone.
EDIT: of the three opitions that pop up when you plug the phone in only one is large enough for the viper rom so it has the viper folder AS WELL as the .zip onto it now.
My paths are "C:\android" for all my android files like the adb and the boot.img and recovery.img. I am able to write the two .img files to the phone with the console telling me it wrote ok.
I go to the recovery on the phone and it says entering recovery on the top of the phone screen but then it boots straight into android.
I will redownload all of the files, if anyone else has any ideas id love to hear.
EDIT 2: Got it to work, i think the CWM files were the problem. I just used the TWRP files and it is flashing now! Also found this video which was a huge help. http://www.youtube.com/watch?v=vAwfgi0suJQ
treahuggs said:
Ok where do you put the downloaded files onto the phone. When you plug the phone in you get many different windows pop up that is gives you access to different parts in the phone.
EDIT: of the three opitions that pop up when you plug the phone in only one is large enough for the viper rom so it has the viper folder AS WELL as the .zip onto it now.
My paths are "C:\android" for all my android files like the adb and the boot.img and recovery.img. I am able to write the two .img files to the phone with the console telling me it wrote ok.
I go to the recovery on the phone and it says entering recovery on the top of the phone screen but then it boots straight into android.
I will redownload all of the files, if anyone else has any ideas id love to hear.
EDIT 2: Got it to work, i think the CWM files were the problem. I just used the TWRP files and it is flashing now! Also found this video which was a huge help. http://www.youtube.com/watch?v=vAwfgi0suJQ
Click to expand...
Click to collapse
I'm glad you got it working
Kinda, i have wifi issues. Ive read thats because of the boot.img. Ive tried both boot.img files that you can get with the ViperDNA page and both dont seem to work.
Nvm... again. I have been writing "fastboot flash recovery boot.img" instead of boot... I feel like a noob to reading.
treahuggs said:
Kinda, i have wifi issues. Ive read thats because of the boot.img. Ive tried both boot.img files that you can get with the ViperDNA page and both dont seem to work.
Nvm... again. I have been writing "fastboot flash recovery boot.img" instead of boot... I feel like a noob to reading.
Click to expand...
Click to collapse
Hehe, I did mention that I tried to be as clear as possible with my instructions - How are you liking ViperDNA? Be sure to check out all of the options in viper tweaks
2. ** To flash your kernels boot.img you need to type**
fastboot flash boot boot.img
Before flashing the boot.img, you can in fact flash your ROM.zip with the instructions given below. However, it is strongly recommended to do it before you flash the boot.img. This is the standard procedure that should be used for every single ROM.
Click to expand...
Click to collapse
I find this part a bit confusing. Can you reword? Am I supposed to flash boot.img first then flash my rom or flash my rom first and then flash the boot.img? The "however" is making me hesitant!
Thanks for this wonderful guide!
---------- Post added at 01:49 AM ---------- Previous post was at 01:20 AM ----------
ro roh,
I am now stuck at the htc white screen with the red lettering at the bottom. I held the power button down and the power + vol down and both times the three lights at the bottom (back key, home, and recent apps) just flash at me.
I got it to go back into HBOOT by holding down power + vol down for about 12 secs, it restarts itself.. and when i tell it to reboot, it just goes back to the same screen and gets stuck.
I think i fixed it now. I went back to fastboot, flashed the recovery.img, the boot.img and then launched into cwm and reflashed viper rom. Looks like its working again.
adamjamess said:
I find this part a bit confusing. Can you reword? Am I supposed to flash boot.img first then flash my rom or flash my rom first and then flash the boot.img? The "however" is making me hesitant!
Thanks for this wonderful guide!
---------- Post added at 01:49 AM ---------- Previous post was at 01:20 AM ----------
ro roh,
I am now stuck at the htc white screen with the red lettering at the bottom. I held the power button down and the power + vol down and both times the three lights at the bottom (back key, home, and recent apps) just flash at me.
I got it to go back into HBOOT by holding down power + vol down for about 12 secs, it restarts itself.. and when i tell it to reboot, it just goes back to the same screen and gets stuck.
I think i fixed it now. I went back to fastboot, flashed the recovery.img, the boot.img and then launched into cwm and reflashed viper rom. Looks like its working again.
Click to expand...
Click to collapse
That's great news. I'm glad you worked it out. Because it is such a long guide, it does get a little bit repetitive and hard to concentrate on. You can flash the kernels boot.img before or after the ROM. You might have random issues with the ROM until you do flash the boot.img. It's really not dangerous or anything. I would say if this was your first time ever flashing a ROM on to the device, it would be safest to flash the boot.img first.
I might take this information out that you have brought up because I think I am giving too much information that is not needed right now. Even though it is factual, it can sometimes confuse people. I will leave it in there for now but if 1 more person is a bit held back because of it I'm going to reword it
I love ViperDNA Do you like it so far?
So far i like it. I tried their theme first but i dont like all the red cause i feel like it is telling me something is wrong so i re did it without the theme, Now only the clock is red and i still want to find a way to change that.
Also this phone will be sent back to verizon tomorrow for a replacement. Can i put it back to stock and also get rid of the "tampered" in the boot screen?
I was pretty impressed with the ViperDNA video review. So far it's given me what I was looking for: 3 dot menu gone, wifi nag, and gps reticule gone. I like the red accents. Although the round icons that are all red are ugly. I have the employee edition of the dna so some red goes well with the back. Again thanks for this!
Edit: The status bar tweaks don't allow me to hide NFC icon!
Edit 2: How do I get the sweep to lock and unlock to work?
Sent from my HTC6435LVW using Tapatalk 2
adamjamess said:
I was pretty impressed with the ViperDNA video review. So far it's given me what I was looking for: 3 dot menu gone, wifi nag, and gps reticule gone. I like the red accents. Although the round icons that are all red are ugly. I have the employee edition of the dna so some red goes well with the back. Again thanks for this!
Edit: The status bar tweaks don't allow me to hide NFC icon!
Edit 2: How do I get the sweep to lock and unlock to work?
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
I believe it will depend on your kernel too. If you use cubed it will work, I tested with elkays and it didn't work. If you are not sure how to activate this then open up viper tweaks. For slide2wake the option is in lockscreen and another good feature is hold back to kill which is in the buttons tab. Good luck
Sent from my HTC6435LVW using Tapatalk 2
uppon2 said:
I believe it will depend on your kernel too. If you use cubed it will work, I tested with elkays and it didn't work. If you are not sure how to activate this then open up viper tweaks. For slide2wake the option is in lockscreen and another good feature is hold back to kill which is in the buttons tab. Good luck
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
For some reason the option is grayed out.
Sent from my HTC6435LVW using Tapatalk 2
adamjamess said:
For some reason the option is grayed out.
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
The bottom one "Enable slide 2 unlock" you already have checked is all you need for it to work. This is the only option I have checked out of the last 4 options and it works fine for me. Try to uncheck the option to "Block Pulldown" if you are having problems? I did try to enable "Block Pulldown" but I could not reproduce your problem. Mine is working fine.
Which kernel are you using?
Dsb's cubed. The one recommended in your guide.
Sent from my HTC6435LVW using Tapatalk 2
adamjamess said:
Dsb's cubed. The one recommended in your guide.
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
Should be working. You might want to leave a comment in the kernel and ViperDNA threads. As long as that bottom option is checked it should work with Cubed
Phone: ATT HTC One X +
Hi everyone,
This problem has been beat to death on this site but it's very hard to follow with other phones and trying to find the files and everything needed to fix it. This is my first time to try and root a phone so I tried to piece it together and screwed it up. Still trying to learn.
So far I successfully unlocked the bootloader through the HTCDEV site so I have SDK with fastboot and adb. I found OneXRoot but it just said "waiting for device". So, I found RootBoot-1.14.206.16-O2, ran it from the file I downloaded it to and not the fastboot/adb location (might have been the problem) and it said "waiting for device" so I unplugged my phone and plugged it back in. It was supposed to restart my phone 3 times and root my phone through magic but instead it restarted once and only goes to HTC white screen.
I've looked all through for a solution and the best thing I've come across was this link http://forum.xda-developers.com/showthread.php?p=30863908 . I was going to try this but I don't know my CID and my phone doesn't boot to figure it out. Am I headed in the right direction?
My goal here was to root the phone to get rid of HTC Sense. I'm thinking I should flash the boot.img or do the kernal thing. Not sure though it's very confusing. Right now I need to get it to boot so I can try the root again (the correct way, whatever that might be). Any help would be very appreciated, my phone is a paper weight right now.
http://teamw.in/project/twrp2/131 downloaded the recovery image here and going to try that. It says the batter is too low now so i'm guessing it will work after the battery is recharged. That's direction I am taking atm.
Update: I've finally figured out how to get the TWRP recovery booted. Now working on trying to get my phone to boot up an OS of some sort. Very slowly but surely.
bullmurf said:
Phone: ATT HTC One X +
Hi everyone,
This problem has been beat to death on this site but it's very hard to follow with other phones and trying to find the files and everything needed to fix it. This is my first time to try and root a phone so I tried to piece it together and screwed it up. Still trying to learn.
So far I successfully unlocked the bootloader through the HTCDEV site so I have SDK with fastboot and adb. I found OneXRoot but it just said "waiting for device". So, I found RootBoot-1.14.206.16-O2, ran it from the file I downloaded it to and not the fastboot/adb location (might have been the problem) and it said "waiting for device" so I unplugged my phone and plugged it back in. It was supposed to restart my phone 3 times and root my phone through magic but instead it restarted once and only goes to HTC white screen.
I've looked all through for a solution and the best thing I've come across was this link http://forum.xda-developers.com/showthread.php?p=30863908 . I was going to try this but I don't know my CID and my phone doesn't boot to figure it out. Am I headed in the right direction?
My goal here was to root the phone to get rid of HTC Sense. I'm thinking I should flash the boot.img or do the kernal thing. Not sure though it's very confusing. Right now I need to get it to boot so I can try the root again (the correct way, whatever that might be). Any help would be very appreciated, my phone is a paper weight right now.
http://teamw.in/project/twrp2/131 downloaded the recovery image here and going to try that. It says the batter is too low now so i'm guessing it will work after the battery is recharged. That's direction I am taking atm.
Click to expand...
Click to collapse
Press the power down button while turning on your device to see if you can get to boot loader - this will give you the basic information about your device.
Use the original RUU from the following post to flash your device in bootloader mode (I think it should work...):
http://forum.xda-developers.com/showthread.php?t=2140442
Use this to unlock your bootloader / root your device / blah blah blah. Too many people have succeeded in rooting / unlocking their device through this. So, there is a good chance that you will too...
http://forum.xda-developers.com/showthread.php?t=1994961
Addicted2xda said:
Press the power down button while turning on your device to see if you can get to boot loader - this will give you the basic information about your device.
Use the original RUU from the following post to flash your device in bootloader mode (I think it should work...):
http://forum.xda-developers.com/showthread.php?t=2140442
Use this to unlock your bootloader / root your device / blah blah blah. Too many people have succeeded in rooting / unlocking their device through this. So, there is a good chance that you will too...
http://forum.xda-developers.com/showthread.php?t=1994961
Click to expand...
Click to collapse
OK it looks like the OS was wiped before it was backed up with a rom folder to use after rooting. Now I have no OS so I can't get to files to put on a ROM or do much of anything. It's not booting past the HTC screen because there is no OS now ^^. I have no idea what to do about that. Going to try to figure out how to put a new OS on there. Any help would be appreciated.
bullmurf said:
OK it looks like the OS was wiped before it was backed up with a rom folder to use after rooting. Now I have no OS so I can't get to files to put on a ROM or do much of anything. It's not booting past the HTC screen because there is no OS now ^^. I have no idea what to do about that. Going to try to figure out how to put a new OS on there. Any help would be appreciated.
Click to expand...
Click to collapse
If your device is locked - you can get the current RUU of your specific device from the post I have mentioned.
BTW what is your hboot version?
If your device is unlocked - install TWRP using hasoon's toolkit and then use sideload to copy / install a custom ROM...
Addicted2xda said:
If your device is locked - you can get the current RUU of your specific device from the post I have mentioned.
BTW what is your hboot version?
If your device is unlocked - install TWRP using hasoon's toolkit and then use sideload to copy / install a custom ROM...
Click to expand...
Click to collapse
"use sideload to copy / install a custom ROM..." OK I don't know anything about this but it will point me in the right direction. I have the phone unlocked. The HBOOT version is 1.40.0000. I'll see if I can do what you suggested, thanks.
Update: Atempting an adb sideload using TWRP which seems to be the only option for me.
ADB Sideload
What is ADB sideload?
--------------------------------------------------------------------------------
ADB sideload is a new feature that was added to AOSP recovery in Jelly Bean. As of version 2.3, TWRP now supports ADB sideload mode. ADB sideload is a different ADB mode that you can use to push and install a zip using one command from your computer. Most likely ADB sideload won't be very useful for your average recovery user, but ADB sideload can be a huge time-saver for a ROM developer.
How do I use ADB sideload?
--------------------------------------------------------------------------------
1.Have a recovery installed on your device that supports ADB sideload like TWRP 2.3 or higher
2.Have newer ADB binaries installed on your computer. If it's been a while since you installed ADB on your computer, you may need to get the latest ADB binaries in platform-tools from the Android SDK. You will need version 1.0.29 or higher. You can find your current version by typing "adb version" at the command line.
3.Set the device into ADB sideload mode. In TWRP you do this by going to Advanced then ADB Sideload.
4.From the command line, type adb sideload /path/to/rom.zip
The file will be copied to your device to whatever the current storage location is that you have selected in the mount page. It will always be placed in the root of that storage location and named sideload.zip (e.g. /sdcard/sideload.zip) and it will automatically delete / overwrite any existing sideload.zip you may have on your device. As soon as the file is copied to your device, it will automatically be installed. When the install is finished you will be presented with a reboot system button so that you can reboot to test your zip.
Note that sideload mode is a separate ADB mode. While in sideload mode, regular ADB commands will not work. Once the zip has been copied to the device and the install starts (or if you hit the cancel button) regular ADB mode will resume.
Click to expand...
Click to collapse
I can't link on this board yet so I quoted the sideloading instructions for a .zip from the TWRP website. I have the latest version of SDK and when I try to sideload it gives me a list of commands in the command prompt. I looked through them and didn't see sideload as a command. What's the easiest way to sideload this zip so I can install it in TWRP to get my phone booted? I know you can do "adb install \path.apk) but I don't have an rom in .apk format, only zip.
bullmurf said:
I can't link on this board yet so I quoted the sideloading instructions for a .zip from the TWRP website. I have the latest version of SDK and when I try to sideload it gives me a list of commands in the command prompt. I looked through them and didn't see sideload as a command. What's the easiest way to sideload this zip so I can install it in TWRP to get my phone booted? I know you can do "adb install \path.apk) but I don't have an rom in .apk format, only zip.
Click to expand...
Click to collapse
Update: after trying the same thing 100 times it decided to send "sideload". command line was adb sideload name.zip. Installing Viper ROM for HOX+ atm. I'll see if it fixes all of my problems. Thanks for all of the help to this point. I'll type up a guide of what went wrong with my root and how we managed to get it fixed.
Update: Phone is booting to HTC white screen and then shutting off. Now trying to figure that one one out.
Update" Phone is booting to HTC white screen now and staying there. In TWRP under reboot is says "no os installed, do you still wish to reboot". Still digging in the forums to figure this one out and how to fix it. I installed the Viper ROM fine but when it asked to reboot now it just rebooted to HTC white screen. Missing something here? The phone is S-ON, does that make a difference in using the TWRP?
Is there an RUU exe file I can run from my computer? I relocked the phone but the links you gave me are for installing the ap through google play. Not sure how you do that with a phone that wont boot past htc screen.
Update: I've found an RUU application from these boards that is supposed to work for HOX+ so i'm downloading it. It really is taking forever to find the information I need along the way from this board but it's here....somewhere...I think...Will keep plugging away but feel free to throw me a bone ever once in a while! =)
Update: The version that worked for others isn't the same version I have. Going to dig again for 1.19.502.1 version.
Update: Found the version in the last place I thought it would be...HTC website...Downloading it and just hoping its and application I can run on my computer.
Problem Fixed:
Problem: While trying to root phone I didn't back it up. Unlock was successful but root was not. OS was lost and phone would not boot past HTC white screen.
Solution: Relocked phone using fastboot oem relock. Downloaded manual ROM installation of the same version and intalled it while phone plugged in.
Thanks for the help in pointing me in the right direction. Now to try and root it again to install viper. If it screws up I know how to get back :laugh:
bullmurf said:
Problem Fixed:
Problem: While trying to root phone I didn't back it up. Unlock was successful but root was not. OS was lost and phone would not boot past HTC white screen.
Solution: Relocked phone using fastboot oem relock. Downloaded manual ROM installation of the same version and intalled it while phone plugged in.
Thanks for the help in pointing me in the right direction. Now to try and root it again to install viper. If it screws up I know how to get back :laugh:
Click to expand...
Click to collapse
I would suggest you to use hasoon's all in one toolkit
I went with another Rom. Honestly I tried the toolkit and ity worried fine at first but later it wouldn't work for me. After doing this for two straight days I learned to do it the hard way. New Rom is great. trying to explore my new freedoms now. I really want to change my lock screen.
bullmurf said:
I went with another Rom. Honestly I tried the toolkit and ity worried fine at first but later it wouldn't work for me. After doing this for two straight days I learned to do it the hard way. New Rom is great. trying to explore my new freedoms now. I really want to change my lock screen.
Click to expand...
Click to collapse
There is a great lockscreen called CLocker
Addicted2xda said:
There is a great lockscreen called CLocker
Click to expand...
Click to collapse
looking for it now. Trying to figure out how to replace the ring one from HTC. Is that possible? Probably in the boards somewhere
bullmurf said:
looking for it now. Trying to figure out how to replace the ring one from HTC. Is that possible? Probably in the boards somewhere
Click to expand...
Click to collapse
You will find it in the playstore itself
You need to set lockscreen to None
Addicted2xda said:
You will find it in the playstore itself
You need to set lockscreen to None
Click to expand...
Click to collapse
Thanks again man. I got it and the ring is gone \0/ Phone looks freakin amazing now with that lock screen and Elegancia rom. Glad you stopped by to help :good: Still learning my way around the forums and my rooted phone. It's great to not be stressed about bricking it ^^
suppils soars
bullmurf said:
Problem Fixed:
Problem: While trying to root phone I didn't back it up. Unlock was successful but root was not. OS was lost and phone would not boot past HTC white screen.
Solution: Relocked phone using fastboot oem relock. Downloaded manual ROM installation of the same version and intalled it while phone plugged in.
Thanks for the help in pointing me in the right direction. Now to try and root it again to install viper. If it screws up I know how to get back :laugh:
Click to expand...
Click to collapse
Hi there, I'm a noob and got the same problem, by mistake I formatted the system folder of my phone, now I'm stuck in the white HTC screen too, could you please post the links for the tools you used to bring the phone back to life? some instructions would be great to, thanks in advance...
mrmagoogt said:
Hi there, I'm a noob and got the same problem, by mistake I formatted the system folder of my phone, now I'm stuck in the white HTC screen too, could you please post the links for the tools you used to bring the phone back to life? some instructions would be great to, thanks in advance...
Click to expand...
Click to collapse
If you have installed TWRP - go to hasoon's thread, download the toolkit and use the function adb sideload to copy a rom your choice.
Flash the ROM using TWRP. Flash the kernel from hasoon's toolkit.
Addicted2xda said:
If you have installed TWRP - go to hasoon's thread, download the toolkit and use the function adb sideload to copy a rom your choice.
Flash the ROM using TWRP. Flash the kernel from hasoon's toolkit.
Click to expand...
Click to collapse
Thanks, phone is rooted but has CWM v6.0.2.7 installed, however, I can see the "install zip from sideload" option, when I choose this option it says "Now send the package you want to apply to the device with "adb sideload <filename>"", I don't know how to do that...
mrmagoogt said:
Thanks, phone is rooted but has CWM v6.0.2.7 installed, however, I can see the "install zip from sideload" option, when I choose this option it says "Now send the package you want to apply to the device with "adb sideload <filename>"", I don't know how to do that...
Click to expand...
Click to collapse
Flash TWRP man!
If you just browse through the forum - you will see that CWM is discouraged....
Addicted2xda said:
Flash TWRP man!
If you just browse through the forum - you will see that CWM is discouraged....
Click to expand...
Click to collapse
Thanks, I used a script to charge my battery, relock bootloader and installed ruu file to get back to stock, rooted again using Hasoon2000's all in one kit...
Hey everyone, (It's a long story: But I would really appreciate any help...)
[I know the easy solution: Boot into RECOVERY MODE and factory reset the phone and if all goes well...DONE.]
I'm running on Android 4.4.(the latest I think its '2'), Stock Firmware, 4G LTE form MetroPCS, and able to get into a so called 'recovery mode' (you can only factory reset the phone) and download mode. I can't get into safe-mode. and I'm Currently stuck in a bootloop or a 'soft-brick'.
Here's what happened:
I've recently been messing around with the tether_dun_required on my LG in order to get it be able to tether WiFi to my laptop.
The phone was rooted using this method: [GUIDE] New Root Method for LG Devices
[ROOT was successful]
I tried various SQLite3 editing apps to try and change the tether_dun_required record in settings.db in data/data/com.android.providers.settings/databases but after looking ant the SuperSU logs I got this error: Cannot [mount or chmod] ... because the filesystem is Read-Only...
So, I decided to use ES-File Explorer to pull the settings.db file to my computer and modified it using SQLite Studio then I copied the files to sdcard and renamed the old settings.db to settings_old.db using ES-File Explorer. (all over WiFi) Then I ran ADB shell and got root using 'su'. I remounted '/' , '/data', and '/system' as RW using "mount -o rw,remount /" and etc... Then, I used the "cp" command to copy the files from "/sdcard/settings.db" to "/data/data/com.providers.settings/databases". I assumed you needed to reboot. So I rebooted the phone. AND....bootloop.
I was going to make a nandroid backup or atleast copy anything important out of the phone but: being a noob... I didn't.
I can't get ADB to run either of the Download or Recovery modes.
I know (have a feeling...) I can fix the phone if I can rename the settings.db to something else and the settings_old.db to settings.db but I don't have access to the filesystem because I can't start ADB.
Ophidian_DarkCore said:
if your savvy with the shell, aroma fm has a built in terminal.
flash this in recovery http://forum.xda-developers.com/showthread.php?t=1646108
then cd to the directory.
rm settings.db
mv settings_old.db settings.db
Click to expand...
Click to collapse
Thanks you for you reply. I have one question though, I have no idea if my bootloader or my kernal or any of that is 'unlocked' I only rooted my phone. If I try to flash aroma fm and they are locked or something would that actually really brick my phone?
ALSO: I don't have an SDCARD... I don't think it's possible to flash anything then? Because flashing from the Internal Storage might brick the device. right?
ALSO: I don't think the LG Optimus F60 has ARM Neon support... & the "Recovery mode" doesn't have any flashing support. It's all STOCK.
LG Optimus F60 Specifications
Any Ideas?
Ophidian_DarkCore said:
well damn, if you have a custom recovery usb-otg you can make a flashable zip that runs some shell commands.
flashing wont brick a device. putting unsigned boot/recovery imgs usually bricks locked devices.
as with all lg devices, there is download mode to load stock firmware/updates. [LOL apparently I can't post outside links yet even, if their a quote...]
Click to expand...
Click to collapse
That's RIGHT! But, sorry for the noob question: What is a custom recovery usb-otg and how do I make a flashable zip that runs some commands? (For example: maybe one that just runs the commands but doesn't actually change the recovery software or the boot just one that can rename the files?)
Also, I don't think it would work but, would flashing the recovery to stock not delete any data, and have the phone be able to boot?
If it's too much to explain that's okay just show me some related posts that can show me how.
Thanks again for your time.
Ophidian_DarkCore said:
maybe try this http://forum.xda-developers.com/showpost.php?p=59637778&postcount=62
EDIT: Disregard below
you need a custom recovery before anything. and apparently your device supports fastboot.... so give this a go http://forum.xda-developers.com/and...8-5-0-touch-recovery-lg-t3049800#post59310323
and later you might get android L
Click to expand...
Click to collapse
I'm not sure, because the phone already has the factory boot and I haven't flashed anything into the Boot Partition. It's probably an error that happens when it tries to validate the settings.db or the permissions it has [chmod or that its mounted read write]. [To my understanding] what TWRP boot loop fix does is install fastboot then the custom recovery and the stock boot again. Which should do about the same thing because the phone is already stock. Right?
Would installing a custom recovery then allow me to access adb or the filesystem? (If so any recommendations?) Or how would I run a script from download mode?
Thanks for your time.
Ophidian_DarkCore said:
you only need to flash the recovery. not the boot img.
installing a custom recovery will either give you adb, or an on device shell.
Click to expand...
Click to collapse
That's right, Thank you. I'm going to try flashing one right now. Do you know of any that give you access to adb? (and maybe have low risk of bricking LG phones?)
Ophidian_DarkCore said:
the one in that thread should work.
fyi, recoveries, roms, and kernels are specialised software usually only compatible with one model. so no mixxy matchy
i guess using those instructions you could try the img from here http://forum.xda-developers.com/and...8-5-0-touch-recovery-lg-t3049800#post59310323
Click to expand...
Click to collapse
How would I install the img? I would need to install fastboot, right? Then run fastboot ****.img?
Is fatboot run from adb or from SendCommand.exe?
Thanks again for all your help.
Ophidian_DarkCore said:
yea, just grab a fastboot binary, the lg driver, go into whatever mode in that thread and
Code:
fastboot flash *.img
edit: fastboot is it's own binary. so it's run in a command shell on your pc like adb is.
Click to expand...
Click to collapse
One last question (Need to make sure...): I have fastboot.exe from the SDK tools, so all I need to do is:
1. Connect the USB
2. Boot into Download Mode
3. Run fastboot flash *.img
4. When finished unplug the USB and take the battery out.
5. Then boot back into Download mode or Recovery Mode to get TWRP?
6. Then try to see if I can get ADB to work?
Also, sorry for all the questions: But If I ever needed to, will a factory reset delete TWRP or will I need to flash it again with the Stock recovery?
Thanks for your time. You are awesome.
Hi, thank you for using XDA Assist. Unfortunately there is no device specific forum for your device. I'm going to ask a moderator to move your thread here, http://forum.xda-developers.com/android/help
Solved it.
I used an exploit to access the filesystem and fix the corrupt db.
crazy_code said:
Hey everyone, (It's a long story: But I would really appreciate any help...)
[I know the easy solution: Boot into RECOVERY MODE and factory reset the phone and if all goes well...DONE.]
I'm running on Android 4.4.(the latest I think its '2'), Stock Firmware, 4G LTE form MetroPCS, and able to get into a so called 'recovery mode' (you can only factory reset the phone) and download mode. I can't get into safe-mode. and I'm Currently stuck in a bootloop or a 'soft-brick'.
Here's what happened:
I've recently been messing around with the tether_dun_required on my LG in order to get it be able to tether WiFi to my laptop.
The phone was rooted using this method: [GUIDE] New Root Method for LG Devices
[ROOT was successful]
I tried various SQLite3 editing apps to try and change the tether_dun_required record in settings.db in data/data/com.android.providers.settings/databases but after looking ant the SuperSU logs I got this error: Cannot [mount or chmod] ... because the filesystem is Read-Only...
So, I decided to use ES-File Explorer to pull the settings.db file to my computer and modified it using SQLite Studio then I copied the files to sdcard and renamed the old settings.db to settings_old.db using ES-File Explorer. (all over WiFi) Then I ran ADB shell and got root using 'su'. I remounted '/' , '/data', and '/system' as RW using "mount -o rw,remount /" and etc... Then, I used the "cp" command to copy the files from "/sdcard/settings.db" to "/data/data/com.providers.settings/databases". I assumed you needed to reboot. So I rebooted the phone. AND....bootloop.
I was going to make a nandroid backup or atleast copy anything important out of the phone but: being a noob... I didn't.
I can't get ADB to run either of the Download or Recovery modes.
I know (have a feeling...) I can fix the phone if I can rename the settings.db to something else and the settings_old.db to settings.db but I don't have access to the filesystem because I can't start ADB.
Maybe it's the fact the system was still mounted as Read-Write when I rebooted and the stock firmware just doesn't like that...
I'm new to android but love to code C, C++, and C#. Does anybody know of any API's that might help me access the filesystem in download mode. Because I'm almost certain the root method I used, used that as an exploit to root the phone.
Or can someone at least point me in the right direction as to how to UN-softbrick the phone without 'factory-resetting' it. I would really love to be able to recover my contacts and pictures.
Click to expand...
Click to collapse
I did the same thing, you installed the wrong model FW. just install the base rom and start over.
crazy_code said:
Hey everyone, (It's a long story: But I would really appreciate any help...)
[I know the easy solution: Boot into RECOVERY MODE and factory reset the phone and if all goes well...DONE.]
I'm running on Android 4.4.(the latest I think its '2'), Stock Firmware, 4G LTE form MetroPCS, and able to get into a so called 'recovery mode' (you can only factory reset the phone) and download mode. I can't get into safe-mode. and I'm Currently stuck in a bootloop or a 'soft-brick'.
Here's what happened:
I've recently been messing around with the tether_dun_required on my LG in order to get it be able to tether WiFi to my laptop.
The phone was rooted using this method: [GUIDE] New Root Method for LG Devices
[ROOT was successful]
I tried various SQLite3 editing apps to try and change the tether_dun_required record in settings.db in data/data/com.android.providers.settings/databases but after looking ant the SuperSU logs I got this error: Cannot [mount or chmod] ... because the filesystem is Read-Only...
So, I decided to use ES-File Explorer to pull the settings.db file to my computer and modified it using SQLite Studio then I copied the files to sdcard and renamed the old settings.db to settings_old.db using ES-File Explorer. (all over WiFi) Then I ran ADB shell and got root using 'su'. I remounted '/' , '/data', and '/system' as RW using "mount -o rw,remount /" and etc... Then, I used the "cp" command to copy the files from "/sdcard/settings.db" to "/data/data/com.providers.settings/databases". I assumed you needed to reboot. So I rebooted the phone. AND....bootloop.
I was going to make a nandroid backup or atleast copy anything important out of the phone but: being a noob... I didn't.
I can't get ADB to run either of the Download or Recovery modes.
I know (have a feeling...) I can fix the phone if I can rename the settings.db to something else and the settings_old.db to settings.db but I don't have access to the filesystem because I can't start ADB.
Maybe it's the fact the system was still mounted as Read-Write when I rebooted and the stock firmware just doesn't like that...
I'm new to android but love to code C, C++, and C#. Does anybody know of any API's that might help me access the filesystem in download mode. Because I'm almost certain the root method I used, used that as an exploit to root the phone.
Or can someone at least point me in the right direction as to how to UN-softbrick the phone without 'factory-resetting' it. I would really love to be able to recover my contacts and pictures.
Click to expand...
Click to collapse
i need to restore my lg f60 (i'm in the us and the carrier it supports is metropcs). i have TWRP recovery on it. can someone link to stock firmware/rom (whatever the terminology is...basically the operating system that the phone came w/), usb drivers, software tool to install the firmware, and everything i need to restore my phone back to how it was when i bought it.
i was curious and tried lollipop (i think i tried both 5.0 something or 5.1 something or just one of them ended up working) but the camera was completely non-functional so now i need to go back to the phone being how it was when i bought it.
the firmware i've installed on the phone right now is MS39510G_00 (i think "MS39510G" is the actual identifier of the firmware, and the 00 is probably not useful for anything; the site i got it from maybe just appends it for some reason). but this firmware doesn't seem like what the phone came with or i'm not using/not doing everything i need to to restore it back to normal.
couple of things that strike me as odd and make me think that i don't have the right firmware or just didn't do something right:
there's a weird white area at the bottom, which i think was transparent and took on the color of the wallpaper on the phone when you just bought it & didn't mess around w/it
some of the icons are just the generic green android icon. a lot of apps have this same icon instead of different icons of their own
the lock screen seems also seems kind of different. it doesn't look like the lock screen of a new lg f60. maybe i was using a custom lock screen (i doubt it, but it's possible) but still it doesn't look like the standard lock screen to me
how do i restore my us metropcs lg f60 phone back to stock?
i need to restore my lg f60 (i'm in the us and the carrier it supports is metropcs). i have TWRP recovery on it. can someone link to stock firmware/rom (whatever the terminology is...basically the operating system that the phone came w/), usb drivers, software tool to install the firmware, and everything i need to restore my phone back to how it was when i bought it
i was curious and tried lollipop (i think i tried both 5.0 something or 5.1 something or just one of them ended up working) but the camera was completely non-functional so now i need to go back to the phone being how it was when i bought it.
the firmware i've installed on the phone right now is MS39510G_00 (i think "MS39510G" is the actual identifier of the firmware, and the 00 is probably not useful for anything; the site i got it from maybe just appends it for some reason). but this firmware doesn't seem like what the phone came with or i'm not using/not doing everything i need to to restore it back to normal.
couple of things that strike me as odd and make me think that i don't have the right firmware or just didn't do something right:
there's a weird white area at the bottom, which i think was transparent and took on the color of the wallpaper on the phone when you just bought it & didn't mess around w/it
some of the icons are just the generic green android icon. a lot of apps have this same icon instead of different icons of their own
the lock screen also seems kind of different. it doesn't look like the lock screen of a new lg f60. maybe i was using a custom lock screen (i doubt it, but it's possible) but still it doesn't look like the standard lock screen to me
Help Help
Help anyone, i have LG f60 (390n) running with 5.0.1 lollipop. I wanted to instal custom recovery and install custom rom CM. But i have two problems:
1. If i want to boot to download mode - i have error "SECURE BOOT ERROR" (but it boots up normally, and work normally)
2.If i want to boot to recovery mode - i have error "LOADING KETSTORE FAILED STATUS 5"
Please help.
I am not able to flash it trough LG Flash tool, and i am not able to boot into custom recovery.