Related
OK. Firstly, I have extensive experience with rooting moto droids and custom roms. That said I got cocky and didn't do enough homework trying to root my girls Eris and proceeded following the instructions in the "1.5 to rooted 2.1" thread. Step 1 went fine. I THINK I have root access. Anyway, like I was tired and couldn't get adb shell working so I left it at that with intent to finish today when I get home from work. Now she's telling me her icons are different and some are linking to different programs. Any ideas? Second, can someone point me in the direction of an adb shell how to, on my Droid I can just use terminal emulation and don't actually need a computer so I'm not too familiar with the process... sorry for the stupid newborn questions, don't pull the flame throwers out yet, thanks!
You can use terminal emulator, same thing for the most part as adb... I use that more then adb, faster then having to connect to a pc IMO.
I tried the terminal emulator and got adb not found or not allowed or some craziness like that. Does that mean I didn't root like I thought? Also, any clue about the icon s changing or linking to other apps like shes claiming? I'm going to try again when she gets home
In the terminal emulator you would not need to type adb.. adb is the program you would be using on a pc to talk to the phone... what is it that you are trying to type through adb or the terminal?
III: Flashing a Custom Recovery
Flashing a custom recovery will make your life easier when flashing ROMs in the future.
1. Download this file: Recovery.zip
2. Extract file contents to your \tools\ directory of your Android SDK.
3. Open up a command prompt and go to your tools directory, and execute these commands:
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery.img /sdcard
adb push flash_image /system/bin
adb shell chmod 755 /system/bin/flash_image
adb shell flash_image recovery /sdcard/recovery.img
4. Success! You now have a recovery partition installed on your phone. You can access it by running "adb shell reboot recovery" or by powering off your phone, holding "Volume Up + Power On"
step 3. im an ass. ok so dont type the adb. like i said, not much exp in this part... im guessing i dont tye shell either, but i do type mount?
evilsway said:
III: Flashing a Custom Recovery
Flashing a custom recovery will make your life easier when flashing ROMs in the future.
1. Download this file: Recovery.zip
2. Extract file contents to your \tools\ directory of your Android SDK.
3. Open up a command prompt and go to your tools directory, and execute these commands:
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery.img /sdcard
adb push flash_image /system/bin
adb shell chmod 755 /system/bin/flash_image
adb shell flash_image recovery /sdcard/recovery.img
4. Success! You now have a recovery partition installed on your phone. You can access it by running "adb shell reboot recovery" or by powering off your phone, holding "Volume Up + Power On"
step 3. im an ass. ok so dont type the adb. like i said, not much exp in this part...
Click to expand...
Click to collapse
Oh I see, for that yes you will need to get the SDK setup on your PC as per step 2... There is another thread that has a batch file that does all of this for you. You still need the SDK though.
see: http://forum.xda-developers.com/showthread.php?t=651669
ok, i have the sdk, i followed these instructions to the letter, and i still couldnt get it running last night, where in the sdk do i do this from or is it a command promp, or can i use the terminal emulator?
yes in the command prompt, typically adb.exe will be in your tools folder.
also, and i know im being a pain now, but by adb does it mean the adb in the tools directory of the sdk, i click it and it runs a script then dissapears.
evilsway said:
also, and i know im being a pain now, but by adb does it mean the adb in the tools directory of the sdk, i click it and it runs a script then dissapears.
Click to expand...
Click to collapse
yes, adb needs to be ran through the command prompt, if you click on it in windows it wont work... read the thread I linked you to, you wont need to run adb if you use that method, it does it all for you.
yeah im downloading the file now, but im just curious, now i want to be able to do it just to do it. i hate when i cant figure crap like this out,
so far ive done this, opened command promp, put in C:\androidsdk\android-sdk-windows\tools\adb.exe and it runs a script then nothing
evilsway said:
yeah im downloading the file now, but im just curious, now i want to be able to do it just to do it. i hate when i cant figure crap like this out,
so far ive done this, opened command promp, put in C:\androidsdk\android-sdk-windows\tools\adb.exe and it runs a script then nothing
Click to expand...
Click to collapse
go to start, run and type cmd and enter. then in that window
you have to change to the tools directory at the command prompt like so"
cd androidsdk\android-sdk-windows\tools
then type adb
Renocat said:
go to start, run and type cmd and enter. then in that window
you have to change to the tools directory at the command prompt like so"
cd androidsdk\android-sdk-windows\tools
then type adb
Click to expand...
Click to collapse
Yeah, once you do what he states and type...
cd androidsdk\android-sdk-windows\tools ... or where ever you have your SDK saved at on your computer ... you should be good to start running those scripts in the directions.
Backuped the Infusion 2.0 rom in cwm recovery 4.0.0.8 and i cannot restore it in cwm 4.0.0.2 in cf-root. The MD5 sum does not match!:
Can i do anything to fix this, it`s quite annoying.
I solved my problem bit i`d like to know for future events.
-SOLVED-
I'm really really sorry to tell you but when the MD5 does not match, you're stuck.
prodygee said:
I'm really really sorry to tell you but when the MD5 does not match, you're stuck.
Click to expand...
Click to collapse
thank you for jour answer, does this have anything to do with different recovery versions?
gee2012 said:
thank you for jour answer, does this have anything to do with different recovery versions?
Click to expand...
Click to collapse
Guess it`s just a bad flash
Try restoring the parts manually using an "advanced restore". that should work.
use this
http://forum.xda-developers.com/showthread.php?t=1356401&highlight=md5
and this tutorial on how to use ADB
Check if your phone is detected by ADB
Open up Command Prompt (Go to run, type in cmd, press enter)
Type in:
cd C:\**your sdk name**\tools (Press Enter)
adb devices (Enter) You should see your device listed
adb shell (Enter) you should see $ in the next line
**After you obtain root**
su (Enter) you should see # in the next line if you are already rooted
**you may need to allow adb shell to run as root. Look at the phone and see if Superuser.apk is asking for your permission to allow adb root access. Click on "Remeber my selection" and select yes.
Now you are all set to run adb commands as root or as a regular user
# cd /sdcard/clockworkmod/backup/2010-06-29.20.22.53
# rm nandroid.md5
# md5sum *img > nandroid.md5
**Note: for a list of commands that you can type using adb type "adb" in cmd
Lil' Help... New stock SGS2 phone arrived today... I successfully flashed Entropy512's "stock kernel + rooted stock system image" via Odin3 (v1.85). Worked perfect, phone rebooted, now I have root. 2nd step, I extracted the zImage from Codeworkx's CWM tar file (put zImage in same PC desktop folder as my adb.exe files). I want to use adb push to push zImage file to phone so I can avoid the triangle/counter of death. Anyway, I got this error in my CMD window:
C:\Android\android-sdk-windows\platform-tools>adb push zImage /sdcard/zImage
error: device not found
What went wrong? The "phone" and "card" are recognized by windows explorer, but when trying to use adb commands, get "error: device not found"
Thx.
DoctorQMM said:
Lil' Help... New stock SGS2 phone arrived today... I successfully flashed Entropy512's "stock kernel + rooted stock system image" via Odin3 (v1.85). Worked perfect, phone rebooted, now I have root. 2nd step, I extracted the zImage from Codeworkx's CWM tar file (put zImage in same PC desktop folder as my adb.exe files). I want to use adb push to push zImage file to phone so I can avoid the triangle/counter of death. Anyway, I got this error in my CMD window:
C:\Android\android-sdk-windows\platform-tools>adb push zImage /sdcard/zImage
error: device not found
What went wrong? The "phone" and "card" are recognized by windows explorer, but when trying to use adb commands, get "error: device not found"
Thx.
Click to expand...
Click to collapse
Try to start by verifying that adb can see your phone.
type "adb devices" (no quotes)
This should return a number, if not, the phone is not being seen by adb.
If not check drivers, cable, try different usb port.
If it does return a number you are properly connected.
Proceed to:
adb push zImage /sdcard/zImage
adb shell dd if=/sdcard/zImage of=/dev/block/mmcblk0p5
Might need to as su if prompt shows $ instead of #
Try adb remount
i didnt realize so many people cared about a little triangle that you see for about 3 seconds on boot.
DoctorQMM said:
Lil' Help... New stock SGS2 phone arrived today... I successfully flashed Entropy512's "stock kernel + rooted stock system image" via Odin3 (v1.85). Worked perfect, phone rebooted, now I have root. 2nd step, I extracted the zImage from Codeworkx's CWM tar file (put zImage in same PC desktop folder as my adb.exe files). I want to use adb push to push zImage file to phone so I can avoid the triangle/counter of death. Anyway, I got this error in my CMD window:
C:\Android\android-sdk-windows\platform-tools>adb push zImage /sdcard/zImage
error: device not found
What went wrong? The "phone" and "card" are recognized by windows explorer, but when trying to use adb commands, get "error: device not found"
Thx.
Click to expand...
Click to collapse
You're missing drivers or haven't enabled USB debugging. Drivers for USB Mass Storage are built into Windows, drivers for ADB are not. Not sure what the procedure is for installing Windows ADB drivers... It's one of the reasons I almost never use Windows for working with my phone.
I've heard Droid Explorer might come with a drivers package, not sure.
Entropy512 said:
You're missing drivers or haven't enabled USB debugging. Drivers for USB Mass Storage are built into Windows, drivers for ADB are not. Not sure what the procedure is for installing Windows ADB drivers... It's one of the reasons I almost never use Windows for working with my phone.
I've heard Droid Explorer might come with a drivers package, not sure.
Click to expand...
Click to collapse
PDANET is free and simple to install on any Windows based machine. Less than 30 seconds and it recognises every phone I have tried so far. You just need to be sure to get the right one for you OS, 64 or 32 bit.
I sent to my kids that are too lazy to install the Android SDK.....
SNadler said:
Try to start by verifying that adb can see your phone.
type "adb devices" (no quotes)
This should return a number, if not, the phone is not being seen by adb.
If not check drivers, cable, try different usb port.
If it does return a number you are properly connected.
Proceed to:
adb push zImage /sdcard/zImage
adb shell dd if=/sdcard/zImage of=/dev/block/mmcblk0p5
Might need to as su if prompt shows $ instead of #
Click to expand...
Click to collapse
I appreciate everyone's input... OK, here's where I stand:
adb does now recognize phone. After typing "adb devices", cmd window showed my phone in list of devices attached. I then proceeded to "adb push zImage /sdard/zImage... that seemed to work also [cmd window came back with "2544 KB/s (6718048 bytes in 2.578s)]. Next, I typed "adb shell dd if=/sdcard/zImage of=/dev/block/mmcblk0p5" [cmd window came back with "/dev/block/mmcblk0p5: cannot open for write: Permission denied"]
so is still a drivers issue? cable issue? or something else? Thx again
EDIT: one additional clue for all the experts: the zImage is now on my /sdcard. When I type "adb shell", I do get "$" instead of "#" in cmd window... and I know I have root on phone. When I type "adb shell su" in cmd window, I get "Permission denied".
Sometimes the root install won't completely work until you go to the Superuser app once manually. (e.g. in Applications).
Also, another possibility may be that there are two ways to run adb shell:
One is
Code:
adb shell <command>
Where it'll run <command> and then exit
Then there is
Code:
adb shell
<command1>
<command2>
exit
In the second, when you first type "adb shell" you'll get a shell prompt on your phone.
Then you'll type su (this will give you superuser privileges)
Then you run the dd command
Then you should be good.
The difference is: If you have a custom "insecure" kernel, an ADB shell defaults to root privileges. If you have a stock kernel, ADB shell defaults to "mortal user", and you need to manually use su to get root privileges.
Pushing the file to the SD card does not require root, writing the kernel to the kernel partition (mmcblk0p5) does.
Entropy512 said:
Sometimes the root install won't completely work until you go to the Superuser app once manually. (e.g. in Applications).
Also, another possibility may be that there are two ways to run adb shell:
One is
Code:
adb shell <command>
Where it'll run <command> and then exit
Then there is
Code:
adb shell
<command1>
<command2>
exit
In the second, when you first type "adb shell" you'll get a shell prompt on your phone.
Then you'll type su (this will give you superuser privileges)
Then you run the dd command
Then you should be good.
The difference is: If you have a custom "insecure" kernel, an ADB shell defaults to root privileges. If you have a stock kernel, ADB shell defaults to "mortal user", and you need to manually use su to get root privileges.
Pushing the file to the SD card does not require root, writing the kernel to the kernel partition (mmcblk0p5) does.
Click to expand...
Click to collapse
===============
Entropy512... you da man! I'm good to go now. As you recommended, even though I've been using Root Explorer and I know I was 'rooted', had to open SuperUser app on phone... then in the cmd window when I typed "adb shell" I got the "$" prompt. So at the $ prompt I typed "su"... this gave me the "#" prompt. SuperUser App then asked for SU permission acceptance. Then did the "dd xxxxxxxx" command, and it came back with:
13121 +1 records in
13121 +1 records out
6718048 bytes transferred in 2.895 secs (2320569 bytes/sec).
Rebooted phone to recovery, and have the light blue CWM Recovery 5.0.2.3.
Now I'm rooted, have CWM, and no triangle/counter of death. Hope this helps anyone else with a similar situation.
Again, a BIG shoutout to Entropy512, SNadler, jivy26, et al., for your constructive and quick replies. This forum is the best!
DocQ
One last [Q] Do I have to leave the large "zImage" file (6.41mb) in the /sdcard folder, or can it be removed /moved now that CWM successfully flashed?
DoctorQMM said:
One last [Q] Do I have to leave the large "zImage" file (6.41mb) in the /sdcard folder, or can it be removed /moved now that CWM successfully flashed?
Click to expand...
Click to collapse
No need to leave it, although I keep a bunch of various kernels in /sdcard/kernels myself - it's up to you.
I bricked my Kindle hdx 7" and am looking for help. i JUST COULDN'T LEAVE IT ALONE. rooted wth towelroot, rolled back to 13.2.2.8, Safestrap, Nexus 1.02 for safestrap on rom slot 1. Could not get instant video, so attempted update to 13.4.5.2 to see if that would work. Realized I forgot to backup like I am supposed to do and stopped update. After no boot it went to stock recovery and I did a factory reset, just like everyone says not to do, and now I am in bootloop. Gray Kindle Fire logo for about 45 seconds, then black screen for about 45 seconds. I can communicate throught abd, but I don't know what to enter. I have found TUT from r3pwn which seems really helpful, I just cannot use keyboard fast enough to get it in,(nerve damage from brain tumor). I have seen at some point that I should get into fastboot mode, I can do that, I just don't have Windows drivers. I have been all around XDA and cannot remember where I saw things. can someone point me in the right direction? Thank you.
It took a while, but, accomplished it with help from @Davey126, reading posts from @draxie, @ONYXis, @EncryptedCurse and others. Too many to list.
Fastboot mode is useless to you anyways, as you haven't unlocked the bootloader.
The important thing is that you still have ADB access. If you can't enter the commands in time, just make a batch script to do it for you.
Code:
adb wait-for-device
adb shell
su
mount -o rw,remount /cache
mkdir /cache/recovery
echo install /cache/kindleupdate.bin > /cache/recovery/openrecoveryscript
chmod 0777 /cache/recovery/openrecoveryscript
exit
exit
adb push your-downloaded-update.bin /cache/kindleupdate.bin
adb reboot recovery
As far as I know, you only need to add adb wait-for-device before it tries to run any of the other commands.
Save the above code as .bat in your text editor of choice (i.e. Notepad). Remember to change the local path (in the second to last line) to wherever the .bin is on your computer.
EncryptedCurse said:
Fastboot mode is useless to you anyways, as you haven't unlocked the bootloader.
The important thing is that you still have ADB access. If you can't enter the commands in time, just make a batch script to do it for you.
Code:
adb wait-for-device
adb shell
su
mount -o rw,remount /cache
mkdir /cache/recovery
echo install /cache/kindleupdate.bin > /cache/recovery/openrecoveryscript
chmod 0777 /cache/recovery/openrecoveryscript
exit
exit
adb push your-downloaded-update.bin /cache/kindleupdate.bin
adb reboot recovery
As far as I know, you only need to add adb wait-for-device before it tries to run any of the other commands.
Save the above code as .bat in your text editor of choice (i.e. Notepad). Remember to change the local path (in the second to last line) to wherever the .bin is on your computer.
Click to expand...
Click to collapse
Thank you for your help, I will do this after work.
I couldn't connect with adb on laptop, connected today and batch file stops.
adb wait-for-device
adb shell
[email protected]:/ $
Then when kindle powers off for boot loop, cmd window exits.
Any ideas?
my new batch file and logcat. is it hopeless, or more to come on learning adb?
notjoken958 said:
It took a while, but, accomplished it with help from @Davey126, reading posts from @draxie, @ONYXis, @EncryptedCurse and others. Too many to list.
Click to expand...
Click to collapse
Glad you got it working. Like most complex device recovery efforts it take a lot of reading/filtering and trial/error/retries before being rewarded with meaningful successes. As you probably learned each journey is a little different; almost impossible to develop step-by-step recovery guide that wouldn't eventually have dozens of amendments covering 'special circumstances'. Enjoy your revived HDX!
I was trying to install gapps and now when I reboot I am stuck and the Play Store language select screen. When I click next, it takes me to settings. I have no home or back button so I cant get anywhere other than the settings menu. I have tried a factory reset with no avail. I also tried a manual update, but I have disable OTA updates so it wont recognize the .bin file on my SD. If only I could get to ES File Explorer. Any tips on fixing this problem?
Code:
adb shell "su -c 'mount -o rw,remount /system'"
adb shell "su -c 'mv /system/priv-app/SetupWizard.apk /system/priv-app/SetupWizard.apk.old'"
adb shell "su -c 'mount -o ro,remount /system'"
ONYXis said:
Code:
adb shell "su -c 'mount -o rw,remount /system'"
adb shell "su -c 'mv /system/priv-app/SetupWizard.apk /system/priv-app/SetupWizard.apk.old'"
adb shell "su -c 'mount -o ro,remount /system'"
Click to expand...
Click to collapse
Care to elaborate? I am a complete noob and shouldn't have been trying this at all. I can't access anything on my Kindle other than settings. Do I run this in command prompt on windows?
Edit: I also wanted to add that I am not one of the guys who sits around waiting for an answer without researching the problem lol
You need install adb on your PC - http://forum.xda-developers.com/showthread.php?t=2317790
Install drivers for our tablet (no need to reboot fastboot just manual install drivers for your kindle at device manager) - http://forum.xda-developers.com/showpost.php?p=59268023&postcount=8
Open CMD (cd C:\Program Files (x86)\Minimal ADB and Fastboot>)and paste these commands. I assume you rooted if you can block ota.
ONYXis said:
You need install adb on your PC - http://forum.xda-developers.com/showthread.php?t=2317790
Install drivers for our tablet (no need to reboot fastboot just manual install drivers for your kindle at device manager) - http://forum.xda-developers.com/showpost.php?p=59268023&postcount=8
Open CMD (cd C:\Program Files (x86)\Minimal ADB and Fastboot>)and paste these commands. I assume you rooted if you can block ota.
Click to expand...
Click to collapse
Apparently I no longer have root since I reset to factory. I do have the adb drivers installed, but I get stuck when using the command prompt because I dont have su access. Anyway for me to root it with only access to settings? I am on 4.5.2
are you sure?
earlier I had root even after hard reset on 4.5.2
anyway you could try install kingroot but I do not sure
I think @Cl4ncy and @Davey126 may clarify this.
ONYXis said:
are you sure?
earlier I had root even after hard reset on 4.5.2
anyway you could try install kingroot but I do not sure
I think @Cl4ncy and @Davey126 may clarify this.
Click to expand...
Click to collapse
Yes, I no longer had root access. Thanks to all of your other help and suggestions, I have been able to successfully get my Fire HDX working again. With all of the info you gave I was able to research and piece together what I needed. I was able to install Kingroot through cmd and then use the commands you gave to get rid out of settings. Thanks alot!