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!
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.
Okay well its not as urgent as the title but I am having some problems rooting my thunderbolt. I am using the root method here http://forum.xda-developers.com/showthread.php?t=996616 however, I getting stuck. The first three commands provide a return in terminal but the last two
adb shell chmod 777 /data/local/psneuter
adb shell chmod 777 /data/local/busybox
just return to C:\sdk\platform-tools. I proceeded to the next command adb shell and I get a # instead of $. Any ideas? I have tried it in both charge only and disk drive with usb debugging enabled and fast boot off. In the instructions I am following it didnt specify what to do with the exploits contents so I dropped them all in the platform-tools folder.
http://chat.andirc.net:9090/?channels=#
type in your name and #thunderbolt
I got a ton of help rooting my phone yesterday
I've been hacking about with this tablet and all is going well and I've learned a lot about the Android OS so far, but I've reached a point where I need some assistance.
I rebooted the device and this time, it simply did not come up. It is at the boot logo and won't go any further. I can still use ADB to enter the shell of the tablet, and I got a logcat.
pastebin com 5LjMD00U
Sorry for the broken URL... new user.
This is the logcat I have of it.
If any one has any ideas I'd appreciate it. Thanks.
#################EDIT#################
Apparently the build.prop file in /system had the wrong permissions set.
If you get this error, it's likely because you changed it at some point.
Make sure you can see the device through adb,
then type 'adb remount' to make /system rw
Then type 'adb shell' , and type 'chmod 664 /system/build.prop'
exit adb, and type 'adb reboot'.
That should be it.
Okay, basically I used Teamwin and superuser to root my Dell Streak 7 with this tutorial:
watch?v=u302zKspk2E
^put the YouTube url before this, apparently I have to make 10 posts before posting links (THANKS A LOT)
It worked, but now I have a serious problem. When I open the command prompt and everything, I type adb devices and there's no problem, the device is detected and all is good. But after typing
adb shell
$su
#
when I type:
#adb devices
Error: device not found
I'm trying to make /system writable long enough to add my own files in, but I can't do that without superuser mode!
Anyone have a problem like this?
Specs: Windows 8 64-bit on a Dell Streak 7 [Teamwin + Superuser]
HackAttack37 said:
Okay, basically I used Teamwin and superuser to root my Dell Streak 7 with this tutorial:
watch?v=u302zKspk2E
^put the YouTube url before this, apparently I have to make 10 posts before posting links (THANKS A LOT)
It worked, but now I have a serious problem. When I open the command prompt and everything, I type adb devices and there's no problem, the device is detected and all is good. But after typing
adb shell
$su
#
when I type:
#adb devices
Error: device not found
I'm trying to make /system writable long enough to add my own files in, but I can't do that without superuser mode!
Anyone have a problem like this?
Specs: Windows 8 64-bit on a Dell Streak 7 [Teamwin + Superuser]
Click to expand...
Click to collapse
It detects your device in adb. When you are in adb shell, that is the same as running a Terminal app on the phone. It's not going to see an adb device because it IS the device. Just skip the adb devices while in shell and continue.
es0tericcha0s said:
It detects your device in adb. When you are in adb shell, that is the same as running a Terminal app on the phone. It's not going to see an adb device because it IS the device. Just skip the adb devices while in shell and continue.
Click to expand...
Click to collapse
Okay, so just typing "sysrw" should work for making the system writable once in adb shell su?
Have to mount the system with this command in adb shell:
mount -t yaffs2 /dev/block/mtdblock6 /system
What exactly are you trying to do? Seems like it might be easier with a file explorer that has root access. With that you can mount the system, copy stuff in, change the permissions and reboot. Works for a lot of things on most devices, but depends on the ultimate goal.
HackAttack37 said:
Okay, so just typing "sysrw" should work for making the system writable once in adb shell su?
Click to expand...
Click to collapse
mind the guy above. When you are at the # prompt. You use this code to remount /system, (you should have busybox installed).
Code:
busybox mount -o remount,rw /system
Lgrootnoob said:
mind the guy above. When you are at the # prompt. You use this code to remount /system, (you should have busybox installed).
Code:
busybox mount -o remount,rw /system
Click to expand...
Click to collapse
The command I posted is specifically for the Dell Streak 7 from their forums. The generic one might work, but I always find specific answers to be best.
es0tericcha0s said:
The command I posted is specifically for the Dell Streak 7 from their forums. The generic one might work, but I always find specific answers to be best.
Click to expand...
Click to collapse
Alright, fair enough.
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!