Its been done on the Incredible and Evo, now the Slide. This SHOULD BE IT. Here is their post with exact method. Adjust for the N1 and test on an unrooted phone. ASAP. This should be it!!!!!
QUOTED FORM EUGENE373 @ MT3GS FORUM:
Originally Posted by brokensanity
How-TO Root the Slide
First!! - Go to Settings > Application > Development and turn on USB Debugging. This should save you headaches.
NOW… Power Off the Slide
Download This Package > Slide Root.zip
kingofyo1's Video How-to > http://www.youtube.com/watch?v=sVjoKvy-YZg
Step 1.
Place the Contents of "Slide Root.zip" into your Android SDK Tools folder.
Step 2.
Open Command Prompt or Terminal and CD to the SDK/Tools Directory.
Step 3.
Power on the Slide into the bootloader by Holding Down ( Volume Down + Power Button )
Step 4.
Now run your loop file from the prompt (either type "loop" in windows or "./loop.sh" in a *nix like)
Step 5.
Once your loop is running in your prompt, select Recovery from the bootloader menu.
Step 6.
When recovery loads, you should Have an Offline Device. You can use ctrl+c to stop your script & see.
If this doesn't happen, Power Off and try again..
Step 7.
Un-plug your USB cable from the back of your phone & Plug it back in for it to Detect ADB Correctly!!! This is an important step. At this point you can adb devices to see if you can see your device and that it is in recovery mode.
Step 8.
Select Update.zip from the menu. (This will fail, but we already know that! Select it anyway).
Step 9.
adb push ota.zip /sdcard/update.zip (*nixlike users add a ./ in front of all terminal commands please.)
Step 11.
adb push slideroot.zip
Step 12.
This is Very important!! Have this Command ready in your prompt before applying update.zip again!!
adb push update.zip /sdcard
step 13.
Hit run update.zip, as soon as you see a Little Bar appear under the text push Enter to execute the command in your prompt (adb push update.zip /sdcard )
Step 14.
In successful, you should see Clockwork Recovery. If unsuccessful, repeat steps 12 & 13.
Step 15.
Now, go to the Partitions menu and Mount System
step 16.
Go back one level & select install any zip from sdcard. Select slideroot.zip & apply update from zip (This will finish the Root process).
Step 17.
Reboot your phone & wait for it to load completely. To confirm that your slide is connected as a device use the command adb devices. If this works, you will see it as a device. Your prompt will say something like:
$ ./adb devices
List of devices attached
HT05YUP12710 device
Step 18.
adb install Superuser.apk (If this looks like it works, but says it cannot locate directories, make sure you can find your device using adb devices… If things still don't work, my best advice is to start over)
Step 19.
After Superuser is installed try to use adb to shell to your device.
adb shell
you will get a $
Then type su
Superuser should pop-up asking if you give permission, do so.
Your $ should turn into a #. If so, you have root.
Congrats.
Special Thanks to:
Paul O'Brien:
Koushik K. Dutta:
&
The Guys using the Incredible OTA Spoofing Method
Why don't you test it out and let us know the results? ;-)
why do we care about the bootloader since both HTC and Google are ok with us unlocking it?
Im waitn for someone to try this out... hahaahah
b9nez said:
why do we care about the bootloader since both HTC and Google are ok with us unlocking it?
Click to expand...
Click to collapse
If people don't unlock the bootloader they get to keep their warranty
PhantomRampage said:
If people don't unlock the bootloader they get to keep their warranty
Click to expand...
Click to collapse
Most of the time, they'll replace our equipment. It's been done before, i'm witness to that.
I don't argue this would be a good idea but it's not THAT necessary. :\
Edit: only real upside i can see is getting rid of that annoying unlock icon but since i'm already unlocked there's no point.
This would be pretty good for people like me, who has an unrooted Nexus One
whorehay said:
This would be pretty good for people like me, who has an unrooted Nexus One
Click to expand...
Click to collapse
The key is that we need a DEV with an unlocked phone in hand. I can switch my purple-tinted screen out and get it over to a good one, but that could take a few weeks, anyone else have the tools ready?
I read that whole thread and there was no mention of bootloader at all. If someone can confirm it isn't touched I might be willing to give this a go with my new ATT N1.
If I somehow manage kill it, is there a way to recover a stock image without root?
Santoro said:
I read that whole thread and there was no mention of bootloader at all. If someone can confirm it isn't touched I might be willing to give this a go with my new ATT N1.
If I somehow manage kill it, is there a way to recover a stock image without root?
Click to expand...
Click to collapse
If it is messing with just the image then im 99% sure yeah you can.
I have a mytouch slide also and this method works. Were having problems getting a recovery to stick on the phone though. I have no idea if this works on n1. Id try but my bootloaders already unlocked.
Santoro said:
I read that whole thread and there was no mention of bootloader at all. If someone can confirm it isn't touched I might be willing to give this a go with my new ATT N1.
If I somehow manage kill it, is there a way to recover a stock image without root?
Click to expand...
Click to collapse
I can say that it wont hurt the phone. I tried a process similar to this before I had the details with one of the better known devs from XDA this weekend for a few hours. Even though we couldn't get the timing right, at the end of the day, I still had my original Rom, and it haven't even been hit with a recovery.
i have exchanged my N1 with an unlocked bootloader without any issues. and many other people have as well. if its a hardware issue they will ALWAYS honor warranty. if your phone is bricked by something you flashed they won't honor that
FishFan319 said:
I can say that it wont hurt the phone. I tried a process similar to this before I had the details with one of the better known devs from XDA this weekend for a few hours. Even though we couldn't get the timing right, at the end of the day, I still had my original Rom, and it haven't even been hit with a recovery.
Click to expand...
Click to collapse
So I know just enough to be dangerous. I need to understand a little more before I try this on my N1.
This slide_root.zip, are it's contents phone-specific? You said we should modify the process for the N1, are you saying that the contents of the file need modification? Or just the navigation around the recovery?
I am pretty leery until I understand what the slide_root file does and if it is compatible with my phone. Anyone know?
If I do it and it fails, does anyone have a link to how I would reinstall a stock image via USB?
edit: grammar
I developed a screen problem and had to pay to get it repaired because the bootloader was unlocked. Nothing to do with ROM or anything, a section accross the top of the screen went unresponsive to touch. So I know for a fact that they DON'T always honor warranty after unlock. I guess I must've gotten the a*hole operator/technician then for my call...
Jr33 said:
i have exchanged my N1 with an unlocked bootloader without any issues. and many other people have as well. if its a hardware issue they will ALWAYS honor warranty. if your phone is bricked by something you flashed they won't honor that
Click to expand...
Click to collapse
That really is a matter of interpretation by the tech you get at HTC. Based on the poster just above this, the warranty is not ALWAYS honored. Right?
Santoro said:
That really is a matter of interpretation by the tech you get at HTC. Based on the poster just above this, the warranty is not ALWAYS honored. Right?
Click to expand...
Click to collapse
right. I could not get mine repaired for the dusts under screen problem with unlocked bootloader.
I think most of them slipped through since they could swap in US
kaiser_tytnii said:
right. I could not get mine repaired for the dusts under screen problem with unlocked bootloader.
I think most of them slipped through since they could swap in US
Click to expand...
Click to collapse
I stupidly got mine etched. Had I thought about the fact that it would preclude me from getting cross-shipped warranty work, I'd have reconsidered.
I WISH I COULD TYPE IN ALL CAPS IN TITLES TOO...
Anyway....
I'm assuming the OP didnt intend for yet another thread to devolve into the warrantly debate.
bobtentpeg said:
I WISH I COULD TYPE IN ALL CAPS IN TITLES TOO...
Anyway....
I'm assuming the OP didnt intend for yet another thread to devolve into the warrantly debate.
Click to expand...
Click to collapse
yep, i agree. let's stop the warranty debate here.
i probably will find someone who has a unrooted phone to try it out
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've noticed some people looking for a working temp root for software versions 2.08.651.2 and .3 (and now 2.17.651.5) so that they can backup all their files with Titanium Backup before the HTC Unlock, here ya be.
I take absolutely no credit for this.
from jcase's post on tacoroot
jcase said:
This vulnerability was independently discovered by Justin Case (http://twitter.com/teamandirc) and Dan Rosenberg (https://twitter.com/#!/djrbliss). Unrevoked and (http://twitter.com/unrevoked) and AlphaRev (https://twitter.com/#!/alpharevx) were also aware of it as well. TacoRoot was written by Justin Case (jcase), with the help of Reid Holland (erishasnobattery).
Click to expand...
Click to collapse
I transcribed the root from tacoroot.sh off jcase's git
The license for tacoroot is included in the zip
The basics for getting local superuser access on the phone I took from a batch file written by Eugene373
Extract all the files.
Make sure wifi is disabled. - Thanks DreamWalkerGuy
Run root.bat
This will require a bit of interaction from the user, namely, rebooting from stock recovery back to system, twice. And you have to unplug the phone toward the end. Just follow all the prompts carefully. When it's says rebooting into recovery, wait for the black screen with the red triangle
This is very unstable. The status bar drop down will probably not work, neither will vibrate.
After your done, you can run unroot.bat to make the phone operational again.
I make no claims about the long terms effects of this, I mean for you to run this, back-up your apps and data, then use the HTCdev Unlock which wipes the phone. And of course if this breaks your phone, sets it on fire, and burns your house to the ground with your dog inside... totally not my fault. Do this at your own risk.
I also personally recommend only using this if you already understand what everything in the batch file is doing.
And make sure you understand what the HTCdev Unlock does to the phone, I'm so tired of people *****ing about some such ROM being broken because they don't know how to flash a ROM with HBOOT 1.50
If you use this, please head to the original threads and give them a thanks, or a donation.
I haven't seen eugene since my T-Mobile Vibrant days, he is a beast of a dev.
I still don't understand what is this for. I have an htc unlocked device with s-on, flashed a custom recovery and then flashed a rooted rom on my phone. My phone is basically fully rooted.
why just temp root?
What we people with hboot1.5 are looking for is S-OFF and not root access.
When you used the HTCdev Unlock it wiped all your data. Some people have been looking for a temp root so they can use an app like Titanium Backup to backup everything, and then restore it after the unlock. It won't do any good if you've already unlocked your phone.
doesnt work on the 2.17 update
Crsdr37 said:
doesnt work on the 2.17 update
Click to expand...
Click to collapse
This is going to require HTCDEV method to unlock the bootloader.
Might be a dumb question but, what would happen if you had temp root then used a program like boot manager?
faugnom1 said:
Might be a dumb question but, what would happen if you had temp root then used a program like boot manager?
Click to expand...
Click to collapse
Nothing much. To make permanent changes to /boot you must have nand unlocked. Otherwise all changes are undone on reboot. And that if you don't get a read only file system error. Sorry.
Crsdr37 said:
doesnt work on the 2.17 update
Click to expand...
Click to collapse
Yup, looks like they patched zergRush
Code:
C:\Users\Administrator\Android\Android-SDK\platform-tools\root>adb shell /data/l
ocal/zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00000118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
C:\Users\Administrator\Android\Android-SDK\platform-tools\root>
TacoRoot works for 2.17.651.5 with some tweaking.
Edit: ah, snap, I'm retarded. finishing up now, will update the OP tonight
updated op
2.17
When I reboot into recovery, I get ADB device not found. Works fine when phone is booted to OS. Any ideas?
lyric911 said:
2.17
When I reboot into recovery, I get ADB device not found. Works fine when phone is booted to OS. Any ideas?
Click to expand...
Click to collapse
From what little I know, ADB is only achievable when the phone is powered on and the OS is running.
Recovery is used locally on the phone itself, outside of the OS.
fastboot commands are used to push items outside the recovery, such as the boot.img/splash.img
Maybe, you could access ADB commands while the phone is in fastboot? Not sure.
intrlude said:
From what little I know, ADB is only achievable when the phone is powered on and the OS is running.
Recovery is used locally on the phone itself, outside of the OS.
fastboot commands are used to push items outside the recovery, such as the boot.img/splash.img
Maybe, you could access ADB commands while the phone is in fastboot? Not sure.
Click to expand...
Click to collapse
I should have been more specific I guess. I tried running the root.bat first (due to some things @ work I had to return to stock. Just want to restore some of my items with TI now that I'm stock.)
The first time the batch reboots to recovery, the job just freezes. So I decided I'd try to run the steps manually - then I get the adb device not found.
---------- Post added at 07:24 PM ---------- Previous post was at 06:55 PM ----------
Ignore my posts, I have it working now.
intrlude said:
From what little I know, ADB is only achievable when the phone is powered on and the OS is running.
Recovery is used locally on the phone itself, outside of the OS.
fastboot commands are used to push items outside the recovery, such as the boot.img/splash.img
Maybe, you could access ADB commands while the phone is in fastboot? Not sure.
Click to expand...
Click to collapse
ADB will not work in fastboot usb mode, only fastboot will. ADB will work in any ROM in which the adroid debugging bridge feature is enabled. This is an option you must chose to enable in stock ROMs but is default in most others. ADB can be used to communicate with a recovery image if the image is programmed to allow it, this is the case with custom recoveries like TWRP and CWM. However, the HTC stock recovery image is not configured to allow it. Otherwise I would have programmed the batch file to issue an ADB command to reboot from recovery.
lyric911 said:
I should have been more specific I guess. I tried running the root.bat first (due to some things @ work I had to return to stock. Just want to restore some of my items with TI now that I'm stock.)
The first time the batch reboots to recovery, the job just freezes. So I decided I'd try to run the steps manually - then I get the adb device not found.
---------- Post added at 07:24 PM ---------- Previous post was at 06:55 PM ----------
Ignore my posts, I have it working now.
Click to expand...
Click to collapse
Code:
adb wait-for-device
is a command that pauses the job to allow the user time to manually reboot the phone. When the phone reaches the point in the boot process where it initialized the debugging bridge, ADB allows the batch to continue. The command is usually used to allow users to interact with the phone during scripted processes, or to prevent a script from erroring out while a phone reboots itself during a script. Or to allow nerds to know exactly when there phone is up and linked again... seriously big time and patience saver
lyric911 I'm glad you resolved your issue, so take this not as directed at you, but rather using you as an object lesson to others. By the by, glad you got root
Read the OP, completely.
USSENTERNCC1701E said:
This will require a bit of interaction from the user, namely, rebooting from stock recovery back to system, twice
Click to expand...
Click to collapse
USSENTERNCC1701E said:
I also personally recommend only using this if you already understand what everything in the batch file is doing.
Click to expand...
Click to collapse
from the file said:
please press Volume+, Volume- and Power at the same time, and reboot the system
Click to expand...
Click to collapse
I wasn't chosing to ignore anyone or blow you off by not responding. I'm Army Reserves, this was a drill weekend, so... sorry for the delay However, I'm really not motivated to be kind about questions which I've already given all the answers to.
blizzard1017 said:
I haven't seen eugene since my T-Mobile Vibrant days, he is a beast of a dev.
Click to expand...
Click to collapse
Now he's got his Galaxy S2 over on the T989 forums. It's going to be so beast.
Having Trouble
Hey guys, I'm not getting this to work, so I have a couple questions:
1. am I supposed to extract the files into the Android SDK? Or can they be anywhere?
2. when it gets to "wait for the phone to finish booting, unplug the usb, wait for the led to go out, plug the phone back in" I unplug it and my screen quickly shuts off like the phone dies or something. I plug it back it and it doesn't turn back on. So when it tries to go through all the push commands it fails and claims I have temp root but I don't...
Any ideas will help! Thanks!
jddunkley said:
Hey guys, I'm not getting this to work, so I have a couple questions:
1. am I supposed to extract the files into the Android SDK? Or can they be anywhere?
2. when it gets to "wait for the phone to finish booting, unplug the usb, wait for the led to go out, plug the phone back in" I unplug it and my screen quickly shuts off like the phone dies or something. I plug it back it and it doesn't turn back on. So when it tries to go through all the push commands it fails and claims I have temp root but I don't...
Any ideas will help! Thanks!
Click to expand...
Click to collapse
The zip contains all the adb files necessary for it to run.
When do you unplug the phone? I realize finish booting can be a little arbitrary.
I mean when the Sense interface is functional again, mind you the pull down bar won't work, but basically when you can unlock the screen and Rosie loads it is good to go.
Two things to try.
1. Unplug your phone, if it turns off, pull the battery, turn it back on. When it finishes booting, plug it in.
2. Run Unroot.bat, then try root.bat again.
If those don't work please give me every detail you can.
USSENTERNCC1701E said:
The zip contains all the adb files necessary for it to run.
When do you unplug the phone? I realize finish booting can be a little arbitrary.
I mean when the Sense interface is functional again, mind you the pull down bar won't work, but basically when you can unlock the screen and Rosie loads it is good to go.
Two things to try.
1. Unplug your phone, if it turns off, pull the battery, turn it back on. When it finishes booting, plug it in.
2. Run Unroot.bat, then try root.bat again.
If those don't work please give me every detail you can.
Click to expand...
Click to collapse
I'm unplugging it while it's still locked so that may be the problem. I'm kind of OCD how I run my phone so i didn't think to unlock it first. I'll try it tomorrow and let you know. Thanks for the quick response!
Hey that worked, thanks so much for your help! Just FYI, I'm on the latest OTA 2.17.651.5, so maybe it'll be useful to write the .bat again to say unlock the screen and let Rosie load. Up to you I guess...or they could just read what we've already said haha. Thanks again!
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.
OMG! I'm not going into details on what I did, I'd just like to request the Stock ROM that came with it so I could restore my phone. It has android 4.1.2 and I just want to install it using the "Apply Update From sdcard." And if you must know, I edited the Build.prop file (The internet told me to.) And it messed up and wouldn't start up and got stuck in "Bootloop" so I tried factory reset and it didn't and I really need my phone because if I don't fix it I'll have to try to send it in to Huawei or T-Mobile or who ever. Plllllllz help.
Solution may be here soon.
No one has the stock rom on hand yet. We are working on building a custom recovery for the phone, so please be patient.
Hopefully we can have a working recovery by this weekend, then you will have a way to still access your phone.
What files did you mess up on your phone? If i know the files, I can get someone to upload the files and then you can push the files to your phone using adb. If you haven't yet, I would recommend unlocking your bootloader via the instructions here:
http://forum.xda-developers.com/showthread.php?t=2546455
By unlocking the bootloader, you will be eligible to test the custom recovery as soon as it is available. Also, list the foiles you messed up, so that we can possibly upload them for you.
It will be a while until someone can form a stock rom update.zip for you.
Also, you can view the progress that we are making on the custom recovery.
amamartin999 said:
OMG! I'm not going into details on what I did, I'd just like to request the Stock ROM that came with it so I could restore my phone. It has android 4.1.2 and I just want to install it using the "Apply Update From sdcard." And if you must know, I edited the Build.prop file (The internet told me to.) And it messed up and wouldn't start up and got stuck in "Bootloop" so I tried factory reset and it didn't and I really need my phone because if I don't fix it I'll have to try to send it in to Huawei or T-Mobile or who ever. Plllllllz help.
Click to expand...
Click to collapse
You don't want to go into details but you still want someone to help you? Hahahahaha!!!
Good luck with that plan!
CtrlAltDelIrl said:
You don't want to go into details but you still want someone to help you? Hahahahaha!!!!
Click to expand...
Click to collapse
Show some compassion - I'm sure most of the people here have messed up, and hit their heads against the wall for it.
Deeeno said:
Show some compassion - I'm sure most of the people here have messed up, and hit their heads against the wall for it.
Click to expand...
Click to collapse
Yes and in those cases they're usually eager to share all the details required, unlike the OP.
When the proper details are supplied it's easy to help, nobody likes to mindread here.
CtrlAltDelIrl said:
When the proper details are supplied it's easy to help, nobody likes to mindread here.
Click to expand...
Click to collapse
Probably doesn't know exactly what they did to mess up.. so doesn't know how to explain it.
Merely asked for the stock application to try and fix it themselves is what I gathered.
But Whatever
Explanation.
Was using Android tweaker 2 and accidentally hit the "On Screen Navigation Keys" and then when I went to turn it off it wouldn't switch. It stayed on. Updated the T weaker app, hoping for a fix but the option disappeared and I was stuck with them. Searching the internet I found a option that allowed to disable the soft keys in the Build.prop. But when I save it and restarted the phone was stuck at the T-Mobile screen.
Also I never figured out how to do ABD it tried for a long time but it didn't work. Since I got it in October, I need to know who to send it to be repaired, since I have a warranty (But I don't really want to send it away so that's why I asked.) So, there's and explanation. I'd tell you what I edited if I could find the website.
ADB
Okay, I got ADB working. But if I unlock Bootloader, does that that void my warranty?
And basically I need a default Build.Prop. Thats the only file I edited.
Return the phone since you are under warranty, you won't be without a phone
If you are under warranty with tmobile, you should be able to get a replacement if you are on their JUMP insurance, even if it was accidental.
I would recommend first going to your tmobile store and asking them to send you a replacement(and to waive the restock fee). They will send you one by mail in a few days, then all you have to do is send the old phone back to them in the prepaid shipping package(instructions are included).
I would recommend doing this instead of unlocking your bootloader and waiting for a recovery and custom rom to come out. My belief is that unlocking your bootloader does NOT directly void your warranty, unless the company can prove that the unlocking directly bricked your phone(which it doesn't). A thread with the legality of unlocking your bootloader is found here: http://forum.xda-developers.com/showthread.php?t=2250113
Again, I recommend just bringing in your phone and saying your phone just refuses to boot anymore since an update or something of that like. You won't have to wait long. Also, the phone is $63 on ebay, if you are uneasy about going to tmobile to return it.
build.prop for Android 4.1.1
default Prism 2 build.prop file for Android 4.1.1 attached below. Don't know if this will work with 4.1.2, so make a backup of your build.prop before replacing it!
Prism 2 said:
default Prism 2 build.prop file for Android 4.1.1 attached below. Don't know if this will work with 4.1.2, so make a backup of your build.prop before replacing it!
Click to expand...
Click to collapse
Dont do this, you will brake it even more, every version has specific build prop.
Okay, but no.
Not on insurance....
They didn't offer it at Walmart, that I know of. The real reason I got it was that I was sick of my unlocked Pantech Link (An AT&T on T-Mobile...)
And plus, I'm just broke right now -_-
Are you sure you have Android 4.1.2? I have the latest stock T-mobile rom (just tried updating today) and I'm "up to date" with 4.1.1
How do you have 4.1.2?
That's strange. Can any other users confirm that their Prism Ii has 4.1.2?
Well...
Well.. I may be mistaken. But I can't check =/
Almost certain you have 4.1.1
Doubt they would push an OTA just to upgrade from 4.1.1 to 4.1.2, but if someone can verify they have 4.1.2 i am open for correction.
I think pushing the new build.prop to your phone is worth the shot, and it would not effect your bootloader since it is locked, and you are already softbricked.
To push the build.prop to your phone, you have to rename the old one in adb, and then use the adb push command to push the file into the appropriate folder ( /system )in this case.
If you need help organizing the files or using the actual commands, let me know. Also, you want to place the build.prop file in the same folder you installed adb.
Also, to run adb, you have to open cmd and change your directory(the command is cd) to the folder you installed adb to, in order to use the adb command.
The adb command only runs when you are in that folder in the command prompt, because adb is not a systemwide command
streetdev22 said:
Doubt they would push an OTA just to upgrade from 4.1.1 to 4.1.2, but if someone can verify they have 4.1.2 i am open for correction.
I think pushing the new build.prop to your phone is worth the shot, and it would not effect your bootloader since it is locked, and you are already softbricked.
To push the build.prop to your phone, you have to rename the old one in adb, and then use the adb push command to push the file into the appropriate folder ( /system )in this case.
If you need help organizing the files or using the actual commands, let me know. Also, you want to place the build.prop file in the same folder you installed adb.
Also, to run adb, you have to open cmd and change your directory(the command is cd) to the folder you installed asb to, in order to use the adb command.
The adb command only runs when you are in that folder in the command prompt, because adb is not a systemwide command
Click to expand...
Click to collapse
Pushed the Build.Prop, but still does the same thing. Lost the old one though, because I forgot to rename it.
Try Factory Reset once more
You are stuck in a bootloop? Try factory resetting once more.
If that does not work, you may be our first live install recovery image tester, and you'd just have to wait until a custom ROM was released.
Reseted... Still stuck.
Omg. They must make these phones just to make us upset when they break.
Wait until I get the unlock code from Huawei, also some other things to try
It should be any minute now, and I will see if there are other fixes. For now, unlock your bootloader according to the guide.
We will need access to recovery anyway, through recovery, we will try wiping cache/dalvik cache if available, and that may be the fix you need.
Also: I think you may need to change the permissions on the build.prop you pushed!
You would have to change the permissions to 644 according to this thread: http://forum.xda-developers.com/showthread.php?t=2152850&page=2
To do this, we would still need to use adb.
Commands in adb:
adb shell
remount rw
chmod 644 /system/build.prop
Also, are you sure that the file actually pushed successfully?
I want to help out the people who are having trouble reverting back to stock, rooting, and unlocking. I am no dev, no pro, and no expert. I have been unlocking and rooting phones since the days of HTC Droid Eris. I have some experience and want to share it. My information may not be 100% right. Please don't bash me. This is a guide aimed to help noobs who are new to this kind of stuff. When I got my ladies G3 I had a some what hard time gathering what I needed to do. Here is my break down with added info for noobs.
How to install ADB & Fastboot?
If you want to unlock the LG G3 phone you will need ADB ONLY. LG G3 has no fastboot. However, fastboot is very common on other platforms. There is a tool available that allows you to install Minimal ADB and Fastboot. Follow the xda link and install for whatever system you are running. It sets everything up for you.
http://forum.xda-developers.com/showthread.php?t=2317790
Thanks @shimp208
I Took the OTA Update (11C) can I still root and unlock?
You recently bought your new LG G3 and it installs the latest update. As of now, there is no way to root or unlock on 11C. However, you can roll back the update to stock 10b. Follow this guide to a Tee and you will be able to revert back to stock. On 10b, you are able to root and unlock.
http://forum.xda-developers.com/verizon-lg-g3/general/guide-flash-to-stock-10b-kdz-method-t2928140
Thanks @annoyingduck
I've flashed back to stock 10b....what now?
You've KDZ'd back to STOCK. Do not accept the OTA (duh). It is time to root (needed to unlock). Download this app and follow directions to a tee. It will take 3-5mins to work! Give it time! Make sure once completed to install SU from the market.
http://forum.xda-developers.com/verizon-lg-g3/general/root-easiest-to-root-lg-g3-t2883089
Thanks @azoller1
I'm rooted on 10b what now?
Now it is time to unlock (Bump) the phone! First thing to do is to enable usb debugging on your device. On your rooted STOCK phone go to settings > about phone > software information > tap on build number 5 times. This will unlock developer options. Go back to settings and scroll down, you will now see developer options. Turn on USB debugging (Make sure USB isn't plugged in or it will be grayed out). Remember those ADB/Fastboot tool you installed? Time to use it. On Windows go to My Computer > C drive (local drive) > adb. Inside this folder, hold the shift key and right click. "Open Command Window Here." Plug your phone in and make sure it's on MTP connected. Type...."adb devices" (without quotes). It will come back and say unauthorized. Your phone screen will say "Allow USB debugging" (turn your phone screen on to see it if not on already lol). Once you allow it type "adb devices" again. You will now see the device. Once you have this going, follow this link to bump (unlock) your phone and follow it to a Tee!!!!
http://forum.xda-developers.com/ver...pment/bump-unlock-lg-g3-twrp-verizon-t2900590
Thanks @thecubed
@d08speed3 nice post, clear and concise. I'll link this when needed, and hopefully this will keep many of our threads a little cleaner.... A bit of dirty-ness is certainly ok, but many threads are getting ridiculous!
Also, another common noobie-boobie: Saying thanks in a reply post is not what "thanking" someone is referring to...Tap the little "thanks button" under each helpful post, or in Tapatalk, the little "thumbs up" button!! Making a post to say thanks just takes up space, that's what the button is for...
Very nice noob guide! Thank you
Good guide one suggestion you should side note vs985 has no fastboot.just not to confuse the noobs with that device!
WHATSAMATTA U ALUMNI
I was able to use the Flashify app from the Play Store to flash the bumped TWRP image. Much simpler than using adb in Windows.
Sent from LG G3
devo1929 said:
I was able to use the Flashify app from the Play Store to flash the bumped TWRP image. Much simpler than using adb in Windows.
Sent from LG G3
Click to expand...
Click to collapse
Yeah but adb is vital and this a perfect starting piece dd that/sdcard/recovery.img to dev/block/platform/msm_sdcc.1/by-name/recovery a couple commands to get you up and running a couple commands to pull and push img a nice place to start
WHATSAMATTA U ALUMNI
deathsquad737 said:
Yeah but adb is vital and this a perfect starting piece dd that/sdcard/recovery.img to dev/block/platform/msm_sdcc.1/by-name/recovery a couple commands to get you up and running a couple commands to pull and push img a nice place to start
WHATSAMATTA U ALUMNI
Click to expand...
Click to collapse
Couldn't agree more. Adb is a staple when modifying android phones. If you can read up on how to root and unlock bootlaoders, you can read up on using adb. With adb, you know exactly what is getting flashed to the correct block. Sure using a app is nice, fast, and convenient but it can lead to flashing the wrong block which can result in flashing a recovery to your system one and then end up with no OS. I like seeing the output before rebooting. I NEVER let an app flash anything for me.
annoyingduck said:
@d08speed3 nice post, clear and concise. I'll link this when needed, and hopefully this will keep many of our threads a little cleaner.... A bit of dirty-ness is certainly ok, but many threads are getting ridiculous!
Also, another common noobie-boobie: Saying thanks in a reply post is not what "thanking" someone is referring to...Tap the little "thanks button" under each helpful post, or in Tapatalk, the little "thumbs up" button!! Making a post to say thanks just takes up space, that's what the button is for...
Click to expand...
Click to collapse
I had asked twice in past forums where the "thank you" button was and was told where, but my account as I just now realized was set to view forums in "classic view". I just changed to 2013 view.
very nice
d08speed3 said:
I want to help out the people who are having trouble reverting back to stock, rooting, and unlocking. I am no dev, no pro, and no expert. I have been unlocking and rooting phones since the days of HTC Droid Eris. I have some experience and want to share it. My information may not be 100% right. Please don't bash me. This is a guide aimed to help noobs who are new to this kind of stuff. When I got my ladies G3 I had a some what hard time gathering what I needed to do. Here is my break down with added info for noobs.
How to install ADB & Fastboot?
If you want to unlock the LG G3 phone you will need ADB ONLY. LG G3 has no fastboot. However, fastboot is very common on other platforms. There is a tool available that allows you to install Minimal ADB and Fastboot. Follow the xda link and install for whatever system you are running. It sets everything up for you.
http://forum.xda-developers.com/showthread.php?t=2317790
Thanks @shimp208
I Took the OTA Update (11C) can I still root and unlock?
You recently bought your new LG G3 and it installs the latest update. As of now, there is no way to root or unlock on 11C. However, you can roll back the update to stock 10b. Follow this guide to a Tee and you will be able to revert back to stock. On 10b, you are able to root and unlock.
http://forum.xda-developers.com/verizon-lg-g3/general/guide-flash-to-stock-10b-kdz-method-t2928140
Thanks @annoyingduck
I've flashed back to stock 10b....what now?
You've KDZ'd back to STOCK. Do not accept the OTA (duh). It is time to root (needed to unlock). Download this app and follow directions to a tee. It will take 3-5mins to work! Give it time! Make sure once completed to install SU from the market.
http://forum.xda-developers.com/verizon-lg-g3/general/root-easiest-to-root-lg-g3-t2883089
Thanks @azoller1
I'm rooted on 10b what now?
Now it is time to unlock (Bump) the phone! First thing to do is to enable usb debugging on your device. On your rooted STOCK phone go to settings > about phone > software information > tap on build number 5 times. This will unlock developer options. Go back to settings and scroll down, you will now see developer options. Turn on USB debugging (Make sure USB isn't plugged in or it will be grayed out). Remember those ADB/Fastboot tool you installed? Time to use it. On Windows go to My Computer > C drive (local drive) > adb. Inside this folder, hold the shift key and right click. "Open Command Window Here." Plug your phone in and make sure it's on MTP connected. Type...."adb devices" (without quotes). It will come back and say unauthorized. Your phone screen will say "Allow USB debugging" (turn your phone screen on to see it if not on already lol). Once you allow it type "adb devices" again. You will now see the device. Once you have this going, follow this link to bump (unlock) your phone and follow it to a Tee!!!!
http://forum.xda-developers.com/ver...pment/bump-unlock-lg-g3-twrp-verizon-t2900590
Thanks @thecubed
Click to expand...
Click to collapse
imwatcinu a said:
Click to expand...
Click to collapse
No reason to quote the entire OP. Ever. But especially when only adding emoticons, lol. Just an FYI for newbs.
Sent from my LG-VS980 using Tapatalk
Question about un-rooting. I know how to un-root. After unrooting will it get rid of the su binary inside xbin?