I believe I habe the kfsowi model. it is 11.3.1.0 it is rooted and I am wanting to factory reset it but I dont have a factory cable. just a normal usb cable that I've been using adb to transfer and even instlal some files because through tweaking it, it lead to a missing status bar in which i change the qmenu = to 0 and 1 or whatever in build.prop but no matter what it doesnt keep the status bar active at all times like it should be. it is non existent until i click on an app in apex, adw or any launcher ive tried then it flashes and disappears. during this flash it is not usable no matter how fast i click it.
also a small issue it has is ever reboot, it says kindle is upgrading but it is not upgrading at all because i have tried to click check now in settings to check for updates but every time it says update failed. next after that message it says starting applications for about 20 seconds. long bootup. i have probably messed with tweak i shouldnt have with pimp my rom and also android tweaker 2 and pro before it became 2. so the status bar is non existent. sucks cause cant even get facebook notifications lol.
i did factory reset it by the menu and also by using andromizer app to click recovery mode and do it that way.
(without status bar i been using all in one gestures but now recently i switched to using LMT.
this kindle has a few issues since i made it kinda as minimal as i could and probably uninstalled a couple things i shouldnt of lol like it only installs apps with adb install and adb install -r sometimes as well as through 1mobile market which is awesome. it will not sideload anything now because through uninstalling an extra deal or two i should of, it wont allow me to enable unknown sources installation through menus. if anyone knows a way to do this through terminal of linux that would be great
thanks to any help
or would there be any way to use the water beta without the cable and only using adb or any other steps. which to my understanding is the only rom so far. thanks
If you are rooted You should I think be able to run these commands from a terminal in Linux, if you meant a terminal on your kindle then take off the and shell in the commands I list to run.
Code:
adb shell
su
reboot bootloader
I think if you are rooted it will kick it into fastboot and you can restore without a cable.
Sent from my LG-P769 using Tapatalk
thanks for the quick reply. yeah i am speaking of terminal from debian/ubuntu. I enter those commands you give me and it is recognizing the device. With adb I can even push files to install since it is screwed up and I can't access the menu part for installing from unknown sources. that is the worst part of the few issues I have with it.
after I enter those commands it only reboots normally. it doesn't go into the bootloader. I can get it to go into recovery mode where I am able to just do a normal wipe of the device but that is about it.
just to make sure I understand this. with a fastboot cable and all it is a different method from just a normal "wipe and reset" isn't it? it is using an untouched .img or something to put back to actual FACTORY as if bought from store? cause the normal wipe and factory reset doesn't put back the items I uninstalled of course from system and what not.
also is this safe to do without a factory cable. I just haven't ever needed one before and even if there is an extra step or two I don't mind instead of waiting a week for a cable.
Actually you might not even need the fastboot cable, if I remember correctly the restore method for that device would normally flash a system image that is smaller and incomplete because the system IMG is to big for fastboots 's buffer, then when it was just bootable enough to have adb push a file, it would push a amazon update file and run a command that forces the system partition to update back to stock from the update zip. So you should be able to simply push the update file for your amazon os version or older/newer and force update it. I don't have instructions handy right now for doing this and its late so maybe I post them tomorrow.
Sent from my Amazon Tate using Tapatalk
stunts513 said:
Actually you might not even need the fastboot cable, if I remember correctly the restore method for that device would normally flash a system image that is smaller and incomplete because the system IMG is to big for fastboots 's buffer, then when it was just bootable enough to have adb push a file, it would push a amazon update file and run a command that forces the system partition to update back to stock from the update zip. So you should be able to simply push the update file for your amazon os version or older/newer and force update it. I don't have instructions handy right now for doing this and its late so maybe I post them tomorrow.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
if you could do that that'd be awesome. thanks. I just read up about a locked bootloader but I've seen it's made some progress. I just need to be sure to not turn it into a drink coaster lol.
I finally found a way to do factory reset thanks to gran pc
How to reinstall FireOS
Botched your /system partition beyond recognition? Everything is broken? Dropped your #Kindle in a sea of piss and need to RMA it? Fear not! You can just reinstall FireOS and get it looking just as if we had never touched it!
First of all, you'll have to root your tablet. I'm assuming you know how to do this!
Once that's done, put this file -- https://s3.amazonaws.com/kindle-fire-updates/update-kindle-11.3.1.0_user_310084920.bin -- in /sdcard/ (you can use adb push).
Then run these commands:
jesunoiMac:multidownload granpc$ adb shell
[email protected]:/$ su -
[email protected]:/# cp /sdcard/update-kindle-11.3.1.0_user_310084920.bin /cache/update.zip
[email protected]:/# echo --update_package=/cache/update.zip > /cache/recovery/command
[email protected]:/# exit
[email protected]:/$ exit
jesunoiMac:multidownload granpc$ adb reboot recovery
If everything went well, you should see the 'installing update' screen -- and once you're booted, we're back to stock! We did it!!!!!!
s3.amazonaws.com/kindle-fire-updates/update-kindle-11.3.1.0_user_310084920.bin
funny thing is I rerooted after the clean update and forgot all about OTA's being automatic of course. The damn thing upgraded to 11.3.2.2 which I searched has NO root exploit right now. I am wondering if I can do the same above steps to go back to 11.3.1 but that is a downgrade and I am worried about a brick although amazon new update is like an iphone you can't tell any difference haha
also is the above way how you install ICE or hellfire?
slixz85 said:
I finally found a way to do factory reset thanks to gran pc
How to reinstall FireOS
Botched your /system partition beyond recognition? Everything is broken? Dropped your #Kindle in a sea of piss and need to RMA it? Fear not! You can just reinstall FireOS and get it looking just as if we had never touched it!
First of all, you'll have to root your tablet. I'm assuming you know how to do this!
Once that's done, put this file -- https://s3.amazonaws.com/kindle-fire-updates/update-kindle-11.3.1.0_user_310084920.bin -- in /sdcard/ (you can use adb push).
Then run these commands:
jesunoiMac:multidownload granpc$ adb shell
[email protected]:/$ su -
[email protected]:/# cp /sdcard/update-kindle-11.3.1.0_user_310084920.bin /cache/update.zip
[email protected]:/# echo --update_package=/cache/update.zip > /cache/recovery/command
[email protected]:/# exit
[email protected]:/$ exit
jesunoiMac:multidownload granpc$ adb reboot recovery
If everything went well, you should see the 'installing update' screen -- and once you're booted, we're back to stock! We did it!!!!!!
s3.amazonaws.com/kindle-fire-updates/update-kindle-11.3.1.0_user_310084920.bin
funny thing is I rerooted after the clean update and forgot all about OTA's being automatic of course. The damn thing upgraded to 11.3.2.2 which I searched has NO root exploit right now. I am wondering if I can do the same above steps to go back to 11.3.1 but that is a downgrade and I am worried about a brick although amazon new update is like an iphone you can't tell any difference haha
also is the above way how you install ICE or hellfire?
Click to expand...
Click to collapse
ah good you found it before i could look it up. It will downgrade just fine, but you will probably need a fastboot cable to do it. If ICE or hellfire are roms then no, the 2013 isn't flashable with the exception of kindlewater. Since the bootloader is locked we are limited to using amazon's bootimg(kernel+intram fs).
stunts513 said:
ah good you found it before i could look it up. It will downgrade just fine, but you will probably need a fastboot cable to do it. If ICE or hellfire are roms then no, the 2013 isn't flashable with the exception of kindlewater. Since the bootloader is locked we are limited to using amazon's bootimg(kernel+intram fs).
Click to expand...
Click to collapse
ok sounds like I need to find out if putting water on this without a fastboot cable is possible then
Related
I have sucessfully rooted my nook and I can load apks from dropbox, installers or via adb so I am a happy camper, all is good....
But I got greedy. The ComicViewer doesn't work well without menu keys so I decided to install softkeys.apk and that is where the trouble started, something is amiss.
I am not an expert here, just a novice, so forgive my patchwork explanation.
Here's what I know and what I did, maybe someone can spot my error?
I can fully access adb.
I remember installing SuperUser and SU using the commands:
# adb shell
# cd /system/bin
# mount -o remount,rw /dev/block/mmcblk0p5 /system
# cat /data/local/su > su
# chmod 6755 su
# ls -l su
And all was fine, SuperUser shows up in the drawer. Then I tried installing SoftKeys and it never showed up or worked.
So I figured I fubared the SuperUser install somehow or have an old version of SU or SuperUser. So I downloaded the most recent versions and went to uninstall the original with uninstall utilities and it's not listed in any of them, so I tried using adb (adb shell ls /data/app) and it's still not in the list.
I even reset the Nook to factory and rooted again with nooter and when I tried to install SuperUser again (downloaded the latest version here on the forum) it said "Install Failed already exists!"
So I cannot uninstall the SuperUser or overwrite it with a newer version, and a factory reset doesn't fix it??
I cannot use any root utilities like SuperUser or z4root, SuperUser has all blank screens and I cannot update it and 4zroot just doesn't seem to do anything but reboot the nook.
Titanium Backup says I don't have root access and other utilities say the same thing,
I can mount system partition as read-write
> adb shell
# mount -o remount rw /system
# exit
That works...
So I tried the commands again to install SuperUser and SU and when I try to install SU
# cd /system/bin
# mount -o remount,rw /dev/block/mmcblk0p5 /system
are OK but when I do:
# cat /data/local/su > su
I get:
Cannot create su: remote access failed
I have also tried a few other things that seem to be available to root users and all come back with write or access errors.
What could I be doing wrong?
Note: I also tried to do a full wipe by using that Power and Volume Down and nothing happens...
Power the nook on and off immediately 8 times until it does a full factory reset. When I've done the Power+VolUp+Nook button reset it doesn't always seem to do a FULL reset. When the nook fails to boot 8 times it does a different reset that takes a good deal longer and (at least in my experience) seems to be the real deal.
z4root will work and install superuser for you.
mhoepfin said:
z4root will work and install superuser for you.
Click to expand...
Click to collapse
I have already mentioned that that did not work, but thanks for the suggestion anyway.
Ok, something VERY weird is going on.
I have reset it to factory twice
Each time I did it by powering on and off 8 times in a row
The first time after it indicated it was updating th software, it went into a stuck at NookColor Logo boot loop again.
The second time I left in the nooter microSD card and it booted properly.
But it booted to a "clean" system with all my programs.
All my settings and data was gone, but all my apks were still installed.
So what exactly did it reset? Just data?
I tried to get it to flash both ways, the quick (power/home/volume) and now twice with the 8 power cycles. Neither reset the Nook entirely.
Am I screwed?
I want to go back to factory to fix this thing
EDIT:
Looks like I am locked out of the system entirely, none of my apps work, some of them come back and say no write access.
I cannot do an app listing like:
adb shell ls /data/app
I get:
opendir failed, Permission denied
I can't do a simple mount
mount -o remount rw /system
I get:
mount: operation not permitted
This should help you with what type of reset you want to do. I think you should do another 8 power on/off reset followed by a power-up-home reset to get it fully reset.
axe2 said:
This should help you with what type of reset you want to do. I think you should do another 8 power on/off reset followed by a power-up-home reset to get it fully reset.
Click to expand...
Click to collapse
I tried that...
Now it's completely dead.
Won't power up at all.
It had plenty of battery life left and plugging it in will not boot it either...
gormly said:
I tried that...
Now it's completely dead.
Won't power up at all.
It had plenty of battery life left and plugging it in will not boot it either...
Click to expand...
Click to collapse
Well that's a bummer! Maybe something went wrong in one of the resets. Did they seem to complete? If it's not a hardware problem you should still be able to revive it via nooter. I would suggest PMing pokey9000 and see if he can walk you through a recovery. You might be the first near brick that requires running some of the recovery commands by hand. I think Pokey9000 knows the most about that.
axe2 said:
Well that's a bummer! Maybe something went wrong in one of the resets. Did they seem to complete? If it's not a hardware problem you should still be able to revive it via nooter. .
Click to expand...
Click to collapse
Yea, but it won't respond to anything, it won't boot meaning no power at all.
It's just completely black screen.
Nothing I do does anything.
gormly said:
Yea, but it won't respond to anything, it won't boot meaning no power at all.
It's just completely black screen.
Nothing I do does anything.
Click to expand...
Click to collapse
Whatever you do make sure the battery is getting charged somehow.. Try to leave it plugged into the wall or in a usb. Does the computer see the device when plugged in? HAve you tried to remove the SD card from the NC while powering up?
norkoastal said:
Whatever you do make sure the battery is getting charged somehow.. Try to leave it plugged into the wall or in a usb. Does the computer see the device when plugged in? HAve you tried to remove the SD card from the NC while powering up?
Click to expand...
Click to collapse
Yep tried all those things...very frustrating afternoon so far
However...I did get it to boot.. here is how:
Press and hold the power button while inserting the USB charger connected to a computer, continue to hold (I think it was 10 seconds or so).
I remember doing this to reset a device a long time ago, not sure what.
But it worked, not only that but I was able to do a pwer/up/home rest and this time it completely wiped the nook. It looks like I am back to factory!
YES!!
Thanks for alll the help and suggestions guys. Hopefully this struggle will help someone else in the future.
gormly said:
But it worked, not only that but I was able to do a pwer/up/home rest and this time it completely wiped the nook. It looks like I am back to factory!
YES!!
Thanks for alll the help and suggestions guys. Hopefully this struggle will help someone else in the future.
Click to expand...
Click to collapse
OK. This time around, do this:
(1) nooter
(2) use ADB to enable Non-Market Apps
(3) use ADB to enable multitouch
(4) Use ADB to push z4root over to the NC
(5) Run z4root and do a full-root (whatever is NOT the "temp" option)
(6) Use ADB to install Astro
(7) Use ADB or Astro to install a market
(8) Install the rest of your apps however you choose.
johnopsec said:
OK. This time around, do this:
(1) nooter
(2) use ADB to enable Non-Market Apps
(3) use ADB to enable multitouch
(4) Use ADB to push z4root over to the NC
(5) Run z4root and do a full-root (whatever is NOT the "temp" option)
(6) Use ADB to install Astro
(7) Use ADB or Astro to install a market
(8) Install the rest of your apps however you choose.
Click to expand...
Click to collapse
I did 1,2,3,6,7,8 and in place of 4/5 I used the most recent version of SU and SuperUser and all is good on my Nook! Not sure what happened before but it must have been a bad version of su or superuser. In any case, all seems fine, only Titanium doesn't work, all the rest of the root requesting apps work fine.
Thanks!
I'm just sayin' I hope that we get to see some love and get the CM9 rom for the OB. I would really like to get ICS before the middle of next year. Is there somewhere we can put in some kind of request? or is there a way to use an existing CM9 build to port it to the OB using something from a CM7 build? I've had the phone for about 5 months and getting tired of running 2.2 Froyo just still debating whether to take the plunge and root and put on CM7 or wait it out a little longer. I really have never messed with an android phone before but I read alot on the forum and it seems relatively easy to get the CM7 on there just afraid to root and lose my warranty and something break lol.
Just hack away, don't worry about your warranty. You might get your phone stuck in a bootloop, i've done that several times already, lol. It sucks when it happens, but you can always connect it to your windows pc and restore it to factory settings, unrooted and everything. No one will ever know your phone was rooted
And just to add something, if you can install Android SDK on your computer, you can use ADB Reboot Recovery (if you put recovery on your phone of course). It save me great time.
Sent from my LG-P970 using xda premium
how do u restore the phone? if I know I can unroot it and it won't affect my warrenty ill do it lol I have v10a and have never been able to update higher then that. do I use gingerbreak and the app says it can unroot? like I said if I can unroot it and keep warrenty ill do it
Sent from my LG-P970g using xda premium
I would like Sobralobo to elaborate what he is talking about, sounds like it could save some time after a screwup. However, no matter the condition of your software, you can remove battery, hold vol+ and connect the microusb to your pc. On your pc, you run a LG app, input your imei, and the app will identify your device. It will also tell you if a new software is available. Even if it says it isn't, you can click Options > Recovery (or something like that, i write from my own memory now), and force a update. I'm also pretty sure you'll get V10d or V10e if you do. This process equals to format you phone and install everything from scratch, the way LG intended it to be. All of your personal stuff will be gone, all apps etc. (Obviously, not the stuff you got stored on your sd card, and apps you already bought are linked to your google account and will always follow you
Gingerbreak works for V10a/b afaik, if you get V10c/d/e, you can use this method:
xantaro said:
I got the EU Version of 10c rootet with this method:
1. Download and start SuperoneClick 1.9.5, click Shell Root
2. When it hangs up on a black CMD windows, close this Window. (You should have Shell Root now)
3. Unpack the attached File in your ADB Folder.
4. open a Command Prompt and enter "adb push su /tmp/" & adb push superuser.apk /tmp/"
5. Type "adb shell" ( When Shellroot worked, you should se a "#" on the shell
6. Enter the following commands in shell:
Code:
mount -o rw,remount -t ext3 /dev/block/mmcblk0p8 /system
cat /tmp/su > /system/bin/su
cat /tmp/superuser.apk > /system/app/Superuser.apk
chown root.root /system/bin/su
chmod 06755 /system/bin/su
chown root.root /system/app/Superuser.apk
chmod 0644 /system/app/Superuser.apk
reboot
7. The Phone will now reboot, after reboot it´s rooted again
Click to expand...
Click to collapse
hulkhaugen said:
I would like Sobralobo to elaborate what he is talking about, sounds like it could save some time after a screwup. However, no matter the condition of your software, you can remove battery, hold vol+ and connect the microusb to your pc. On your pc, you run a LG app, input your imei, and the app will identify your device. It will also tell you if a new software is available. Even if it says it isn't, you can click Options > Recovery (or something like that, i write from my own memory now), and force a update. I'm also pretty sure you'll get V10d or V10e if you do. This process equals to format you phone and install everything from scratch, the way LG intended it to be. All of your personal stuff will be gone, all apps etc. (Obviously, not the stuff you got stored on your sd card, and apps you already bought are linked to your google account and will always follow you
Gingerbreak works for V10a/b afaik, if you get V10c/d/e, you can use this method:
Click to expand...
Click to collapse
What Sobralobo said is that just installing Android SDK (Search Google and you get more thousands of tutorials to install SDK and everything you need. Even in O Black section I think there is one with Black drivers and all. Maybe is this one.) you can use "adb reboot recovery" when your Black is in a bootloop or whatever, then you just flash/restore and you are done way faster than reflashing stock firmware. And in certain occasions (for example when you have a certain ROM and you try to flash a modded file in flashable zip that breaks it, you can just flash your ROM without wipe just to fix it and you lose nothing).
PS: You don't even need SDK. There are standalone adb packages, and with LG Black drivers, you can do the same.
This is needed when you mess up with the phone testing all the freaking day like I used to and many others do now.
OK, cool. I'm using adb for rooting and pull/push framework-res.apk and other small mods, didn't know it was compatible with nandroid backups. That can save me a lot of time and trouble next time i mess it up
hulkhaugen said:
OK, cool. I'm using adb for rooting and pull/push framework-res.apk and other small mods, didn't know it was compatible with nandroid backups. That can save me a lot of time and trouble next time i mess it up
Click to expand...
Click to collapse
Well, not directly related to nandroid backups. Just do "adb reboot recovery" (without the "") when you are in trouble. Depending on the situation you will have to input that many times (up arrow and enter fast and many times) if it's bootlooping to find the proper moment when the phone actually receives the command, but it's easy. Once in recovery, you do what you need to do.
aha. so i suppose it won't work with stock bootloader, since LG says "ERROR, LG Security team!!". Still neat that i can restore my backup from bootloader
hulkhaugen said:
aha. so i suppose it won't work with stock bootloader, since LG says "ERROR, LG Security team!!". Still neat that i can restore my backup from bootloader
Click to expand...
Click to collapse
Hmm I think you are partially right. I think in Black bootloader is never changed. When "ERROR, LG Security team!!" is because you really messed up and I believe you have nothing else than flashing. But if you have Clockworkmod recovery (you have if you do nandroid backups), it's worth a try.
I was talking more about bootloops, but maybe when "ERROR, LG Security team!!", if you take the battery off and when put it in again you play with adb reboot recovery, it may work. I can't remember.
antonio1475 said:
Hmm I think you are partially right. I think in Black bootloader is never changed. When "ERROR, LG Security team!!" is because you really messed up and I believe you have nothing else than flashing. But if you have Clockworkmod recovery (you have if you do nandroid backups), it's worth a try.
I was talking more about bootloops, but maybe when "ERROR, LG Security team!!", if you take the battery off and when put it in again you play with adb reboot recovery, it may work. I can't remember.
Click to expand...
Click to collapse
It won't work with adb reboot recovery,I've tried it and failed,won't detect the phone
At least,in my case, it happened when i tried to do a nandroid restore from cm7 to stock (v10a, wiped)
Sent from my heart into yours
I'm interested in knowing if there is any method to unroot the Kindle Fire HD. A method to get back to stock would be useful as well. Just in case I had to send it back to Amazon. I've been searching several forums (finding nothing) before asking this question. Thanks!
tamoquera said:
I'm interested in knowing if there is any method to unroot the Kindle Fire HD. A method to get back to stock would be useful as well. Just in case I had to send it back to Amazon. I've been searching several forums (finding nothing) before asking this question. Thanks!
Click to expand...
Click to collapse
They have some tools that can un root. And I believe if you do a factory reset it erases root.
Chelle01 said:
They have some tools that can un root. And I believe if you do a factory reset it erases root.
Click to expand...
Click to collapse
Yes, a factory reset from within the stock KF recovery will break root and revert the device to stock.
I'm going to say that this is not entirely correct. Using the factory reset will break an app's ability to perform rooted tasks (because Superuser will be gone), but it's not going to return the device back to stock. The su binary will still be in place on the system. To really go back to stock, you'll have to go in as root, remount the system read/write, delete the su binary and reboot.
kinfauns said:
I'm going to say that this is not entirely correct. Using the factory reset will break an app's ability to perform rooted tasks (because Superuser will be gone), but it's not going to return the device back to stock. The su binary will still be in place on the system. To really go back to stock, you'll have to go in as root, remount the system read/write, delete the su binary and reboot.
Click to expand...
Click to collapse
Thanks for all your answers. So If I'm right doing what you said (erasing the su binary) and performing a factory reset the device could be sent back to amazon, I guess that Google Play and all that stuff will desappear without leaving any trace. Am I right? Thanks again
tamoquera said:
Thanks for all your answers. So If I'm right doing what you said (erasing the su binary) and performing a factory reset the device could be sent back to amazon, I guess that Google Play and all that stuff will desappear without leaving any trace. Am I right? Thanks again
Click to expand...
Click to collapse
I just tried this as I wanted to start over and do a clean load after root now that I have a better idea of what I'm doing. Upon starting after factory reset, the kindle presented the dialog box asking me to choose a default launcher. This would indicate anything you install into the system folder needs to be deleted prior to resetting.
Factory reset does not unroot the system. I've done this multiple times.
I sent my rooted but factory reset KFHD back to amazon for a refund. I made sure to delete any files I put in system/apps and anywhere else in the system folders. The factory reset will not clear those files out.
I took the risk and I received a refund a couple hours after they received my device. Most likely it will go back to whomever refurbs their kindle fires and then it will be returned to full stock. I did not find any info so far as to unrooting the KFHD.
Might be different scenario if you sent it back for service.
PS. I made sure to drain the battery and turned off the device and packed it up. Also if you are using anything such as a secondary launcher, I would go back to KF launcher and then delete. Deleting it while using such might cause it to go into a force close loops. Same for keyboard, etc.
alkemist80 said:
Factory reset does not unroot the system. I've done this multiple times.
I sent my rooted but factory reset KFHD back to amazon for a refund. I made sure to delete any files I put in system/apps and anywhere else in the system folders. The factory reset will not clear those files out.
I took the risk and I received a refund a couple hours after they received my device. Most likely it will go back to whomever refurbs their kindle fires and then it will be returned to full stock. I did not find any info so far as to unrooting the KFHD.
Might be different scenario if you sent it back for service.
PS. I made sure to drain the battery and turned off the device and packed it up. Also if you are using anything such as a secondary launcher, I would go back to KF launcher and then delete. Deleting it while using such might cause it to go into a force close loops. Same for keyboard, etc.
Click to expand...
Click to collapse
Happy to hear that. I thought that doing a factory reset wasn't enough, but I was waiting for a confirmation.
You were lucky that amazon has such an amazing customer service.
Thanks so much!!
alkemist80 said:
Factory reset does not unroot the system. I've done this multiple times.
I sent my rooted but factory reset KFHD back to amazon for a refund. I made sure to delete any files I put in system/apps and anywhere else in the system folders. The factory reset will not clear those files out.
I took the risk and I received a refund a couple hours after they received my device. Most likely it will go back to whomever refurbs their kindle fires and then it will be returned to full stock. I did not find any info so far as to unrooting the KFHD.
Might be different scenario if you sent it back for service.
PS. I made sure to drain the battery and turned off the device and packed it up. Also if you are using anything such as a secondary launcher, I would go back to KF launcher and then delete. Deleting it while using such might cause it to go into a force close loops. Same for keyboard, etc.
Click to expand...
Click to collapse
Hi can i know after a factory reset, will all the default software and apk be restored as well? I deleted some system/app file and it causes some problem for me. And does that mean I do not need to root again after the reset? thks
What permissions need to exist on /data/local/tmp if it needs to be recreated (no longer a symlink back to /data), or will the OS recreate the tmp subdir if the symlink is removed?
Edit: Answered my own question. If you remove the symlink, it appears that init.rc takes care of recreating the directory at next boot. You could recreate manually with:
rm /data/local/tmp
mkdir /data/local/tmp
chown shell.shell /data/local/tmp
chmod 0771 /data/local/tmp
Click to expand...
Click to collapse
Complete process to unroot
Working from previous gen Kindle HOWTOs, I managed to work out a full process to revert the Kindle Fire HD device back to stock (assuming you haven't added or removed any other apps from the /system or /data partitions).
This assumes you have the Android SDK and/or the "adb" utility installed. Mac/Linux users may need to substitute "adb" for "./adb" if you don't have your current working directory in your path.
Code:
[I]# On USB Host[/I]
[B]adb shell[/B]
[I]# Inside ADB Shell, get root if you don't have it already[/I]
[B]su[/B]
[I]# Remove SuperUser app and ALL traces[/I]
[B]rm /data/app/com.noshufou.android.su*.apk[/B]
[I]# Remove SuperUser app data and dalvek cache[/I]
[B]rm -r /data/data/com.noshufou.android.su
rm /data/dalvik-cache/[email protected]@com.noshufou.android.su*[email protected][/B]
[I]# /system is read-only - remount /system as read-write[/I]
[B]mount -o remount,rw /system[/B]
[I]# Remove SU binary[/I]
[B]rm /system/xbin/su[/B]
[I]# Restore TMP directory - Remove symlink from rooting effort[/I]
[B]rm /data/local/tmp[/B]
[I]# Recreate symlink dir with correct perms (or let init.rc recreate at reboot)[/I]
[B]mkdir /data/local/tmp
chown shell.shell /data/local/tmp
chmod 0771 /data/local/tmp [/B]
[I]# exit SU[/I]
[B]exit[/B]
[I]# Exit adb shell[/I]
[B]exit[/B]
[I]# On host computer, reboot the Kindle to complete the process[/I]
[B]adb reboot[/B]
Just unrooted my Kindle. Super easy. You will need root to complete it, but it works.
I needed to send my KF2 back to Amazon for a battery defect. Didn't want any problems to go down if they saw the root.
Here is what I did:
Keep root, go to your file explorer and make sure that the system folder is writable, navigate to your /app folder in the system folder, delete the google apps, the google app infrastructure and the SU app. Make sure that you got everything, then do a factory reset. You should now be root free! Congratulations!
Hope that works for you all.
Kindle Fire HD 7.30 root woes
kinfauns said:
I'm going to say that this is not entirely correct. Using the factory reset will break an app's ability to perform rooted tasks (because Superuser will be gone), but it's not going to return the device back to stock. The su binary will still be in place on the system. To really go back to stock, you'll have to go in as root, remount the system read/write, delete the su binary and reboot.
Click to expand...
Click to collapse
I rooted my Kindle fire HD prior to version 7.30. My auto update was not turned off and version 7.30 screwed up my rooted Kindle.
Now I can't root it again. I don't have access to root. I have been trying KFFirstAide but I keep getting "/system/bin/sh: su: not found".
KFF sees the device. The Kindle boots fine and is recognized in Windows 7 32bit. I have been trying for 2 days. I have reset back to factory settings via the Kindle reset. No luck rooting. I don't know what to do. Any help would be greatly appreciated.
fldennis said:
I rooted my Kindle fire HD prior to version 7.30. My auto update was not turned off and version 7.30 screwed up my rooted Kindle.
Now I can't root it again. I don't have access to root. I have been trying KFFirstAide but I keep getting "/system/bin/sh: su: not found".
KFF sees the device. The Kindle boots fine and is recognized in Windows 7 32bit. I have been trying for 2 days. I have reset back to factory settings via the Kindle reset. No luck rooting. I don't know what to do. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Try the manual method described in here http://forum.xda-developers.com/showthread.php?t=2069117 (it's near the bottom of the first post)
Download the Root Many Android application
32-bit
64-bit
Then follow the guide from there.
Usually works for me!
changing ROMs
Hello everyone....
I have a kindle fire HD 7" 7.4.6
I rooted and added TWRP with 7.2.3 bootloader
I installed CM11 Kitkat the ROM is a bit buggy but nice.
I tried to go from kitkat to kinology which allows use of Amazon and Google services.
But flashing failed.... I can't seem to get kinology to work.
This is the set of walkthroughs I used.
To root & add TWRP. I used a rootjunkie YouTube video ( can't post link)
To install cm 11:
also a rootjunkie video
knowing this, I tried installing kinology using this walkthrough:
Original kinology page.
No luck, does anyone know how I can move my system to kinology?
please help,
Thanks to all in advance
Hey everyone,
first off, I have my Kindle for a few weeks now and it's my first Androit device. I started reading into rooting and adb commands only a few days ago, so please excuse me if I'm not writing accurately with some terms. Additionally, I could not find a similar problem via searching.
Here's my problem (I'll try to be as detailed as possible):
I rooted my KFSOWI running 11.3.1.0 yesterday using Moronigs rooting method. It went well and I had full root access (typing su in an adb shell resulted in an # and all that).
Today I wanted to edit the framework-res.apk to exchange some images. Stupid as I tend to be I wanted to rename the original file and then paste my modified one. The device started giving out various crashes, telling me that lots of apps stopped working. Only then I realised that the file is needed to run the system. Unfortunately the Kindle had shut down at some point and when I boot it now it only gives me a black screen (although the backlight is still on).
Here's what I tried so far:
1. I wanted to adb push the modified file to the system/framework folder, but it tells me that the folder is read-only.
2. So I wanted to change permissions but it seems I don't have root access anymore (I don't even get the # output in the adb-shell after typing su).
3. I tried installing the package via adb but it says "Error: COuld not access package manager. Is the system running?"
I guess it doesn't boot up the package manager and root access. You guys have any idea what I can do right now? Seems like a lost cause to me. And if so, can I try sending it back via warranty?
Any help is very much appreciated. And thanks for all the great work on these forums.
Does nobody have an idea? Would be very sad if I couldn't use it anymore. Although I'm the only one to blame. Does someone have experience on sending it back to amazon for warranty? As far as I know rooted devices lose their warranty.. :-/
Karelian_ said:
Hey everyone,
first off, I have my Kindle for a few weeks now and it's my first Androit device. I started reading into rooting and adb commands only a few days ago, so please excuse me if I'm not writing accurately with some terms. Additionally, I could not find a similar problem via searching.
Here's my problem (I'll try to be as detailed as possible):
I rooted my KFSOWI running 11.3.1.0 yesterday using Moronigs rooting method. It went well and I had full root access (typing su in an adb shell resulted in an # and all that).
Today I wanted to edit the framework-res.apk to exchange some images. Stupid as I tend to be I wanted to rename the original file and then paste my modified one. The device started giving out various crashes, telling me that lots of apps stopped working. Only then I realised that the file is needed to run the system. Unfortunately the Kindle had shut down at some point and when I boot it now it only gives me a black screen (although the backlight is still on).
Here's what I tried so far:
1. I wanted to adb push the modified file to the system/framework folder, but it tells me that the folder is read-only.
2. So I wanted to change permissions but it seems I don't have root access anymore (I don't even get the # output in the adb-shell after typing su).
3. I tried installing the package via adb but it says "Error: COuld not access package manager. Is the system running?"
I guess it doesn't boot up the package manager and root access. You guys have any idea what I can do right now? Seems like a lost cause to me. And if so, can I try sending it back via warranty?
Any help is very much appreciated. And thanks for all the great work on these forums.
Click to expand...
Click to collapse
At this point, I would send it back to Amazon. all they will check for is physical damage and send it back to China. I hear some people bricking their tablet several times and getting a replacement. Thing is that Amazon's warranty questions are only water damage and did you drop it questions. So you don't even have to BS them to get a replacement.
If you have a fast boot cable you might restore it. Now it's not the cable that came with Kindle, it's a special programming cable that will put it into fast boot mode.
Sent from my Amazon Kindle Fire2 using xda app-developers app
braider said:
If you have a fast boot cable you might restore it. Now it's not the cable that came with Kindle, it's a special programming cable that will put it into fast boot mode.
Sent from my Amazon Kindle Fire2 using xda app-developers app
Click to expand...
Click to collapse
There are no exploits for this boot loader yet. Don't think a fastboot cord will do much at the time.
Sent from Nexus 7 flo running SinLess ROM 4.2.2 using xda app-developers app
Did noone come up with a solution, because i did the same thing, with the framework-res.apk
i can make a fastboot cable if itll do any good without an unlocked bootloader. could i possibly push the most recent update.bin from amazon and restore the device to stock???
---------- Post added at 04:06 AM ---------- Previous post was at 03:10 AM ----------
i wouldnt take bricked for an answer and i found a fix
what i did was make sure the kindle was connected to adb and typed the following
adb reboot
adb wait-for-device shell su
the shell managed to snag the SU file and displayed # before the device looped thru all of the boot apps over and over, but then CMD froze.
so i tried this
adb reboot
adb wait-for-device shell su mount -o remount,rw -t ext4 /dev/block/platform/omap/omap.hsmmc.1/by-name/system /system
and in one line got root access and remounted the system as RW
my problem was that framework-res APK was replaced with ZIP so all i had to do was rename it
# cp /system/framework/framework-res.zip /system/framework/framework-res.apk
and success!!
# exit
$ exit
adb reboot
and she booted right up!!!!
First response so please be kind. My KFSOWI is stuck in the bootloop too. I have a factory cable and can get into fastboot but don't have any factory images to restore. Anyone have any ideas?
Do you get any adb access? I don't think casebook will be any help until someone unlocks the bootloader
Sent from my KFSOWI using XDA Premium 4 mobile app
Last night I sideloaded the 5.1.1 update to my Droid Turbo. While playing around with it this morning, I accidentally clicked the 'Force RTL' option under accessories. Immediately after, my phone crashed, and on boot would display 'system ui has stopped working' indefinitely. The wallpaper would load, and the alert modal would appear, but clearing it just kicked up another 'system ui has stopped working' modal a few seconds later.
I cleared the cache, and now when I reboot the device, it comes up with the Recovery Andy image with 'no command' below. I don't mind doing a factory reset, but I have a LOT of data I'd lose in the process. All of my pictures are backed up to Dropbox/G+, but I have a lot of other files and backups that I neglected to save externally prior to the update ... because I'm a genius.
When I try to reapply the update, I get a message indicating "/system/app/3c_main.apk" has unexpected contents. I've tried to push from SD and from ADB, both with no luck. At this point I'm happy to just reset the device, but I want my data off first. All ADB commands with the exception of SIDELOAD return 'error: closed', so I can't even backup my files.
Ideas? Help?! ANYTHING?!
spikejnz said:
Last night I sideloaded the 5.1.1 update to my Droid Turbo. While playing around with it this morning, I accidentally clicked the 'Force RTL' option under accessories. Immediately after, my phone crashed, and on boot would display 'system ui has stopped working' indefinitely. The wallpaper would load, and the alert modal would appear, but clearing it just kicked up another 'system ui has stopped working' modal a few seconds later.
I cleared the cache, and now when I reboot the device, it comes up with the Recovery Andy image with 'no command' below. I don't mind doing a factory reset, but I have a LOT of data I'd lose in the process. All of my pictures are backed up to Dropbox/G+, but I have a lot of other files and backups that I neglected to save externally prior to the update ... because I'm a genius.
When I try to reapply the update, I get a message indicating "/system/app/3c_main.apk" has unexpected contents. I've tried to push from SD and from ADB, both with no luck. At this point I'm happy to just reset the device, but I want my data off first. All ADB commands with the exception of SIDELOAD return 'error: closed', so I can't even backup my files.
Ideas? Help?! ANYTHING?!
Click to expand...
Click to collapse
Did you use the zip from Rootjunky?
Sent from my Droid Turbo using Tapatalk
zefir738 said:
Did you use the zip from Rootjunky?
Sent from my Droid Turbo using Tapatalk
Click to expand...
Click to collapse
Yes
spikejnz said:
Yes
Click to expand...
Click to collapse
You might have to wait until the OTA is available for manual download and then flash it via RSD Lite. The way the zip works is it'll only install if you have version 21.44.12.en.us installed. You have 23.11.38 so it won't install now.
Sent from my Droid Turbo using Tapatalk
zefir738 said:
You might have to wait until the OTA is available for manual download and then flash it via RSD Lite. The way the zip works is it'll only install if you have version 21.44.12.en.us installed. You have 23.11.38 so it won't install now.
Sent from my Droid Turbo using Tapatalk
Click to expand...
Click to collapse
Yikes. OTA is supposed to drop today, so hopefully that becomes available soon thereafter. Not sure how long I can survive without my phone.
spikejnz said:
Last night I sideloaded the 5.1.1 update to my Droid Turbo. !
Click to expand...
Click to collapse
I assume you mean the 5.1 update? or did you try to use a 5.1.1 update for some other phone by mistake? if so there may be no easy solution.
I don't accept defeat. Everyone said my data was a lost cause, and that Factory Reset was my only hope. Yeah, well who's copying data off his device right now?
THIS GUY.
I downloaded the firmware, removed the "erase userdata" line from the batch file, and ran it to restore the images and partitions.
I then cleared the cache (again) and rebooted my device.
Back to the 'System UI has stopped' loop
Tried unsuccessfully to send ADB commands to the device
Opened and ADB Shell in Cerberus Dashboard, but kept getting disconnected
Sent an Unlock command in Cerberus Dashboard to my device ... voilla!
UI is still crashing, but Windows is now attempting to install drivers
After trying to manually install drivers for an extended period of time, decided to attempt it on my Mac
BOOM, FS mounts and Android File Transfer is now accessing all the files, even if my display is all jacked!
Next comes the factory reset. I knew there was a reason I installed Cerberus on my non-rooted device.
Fix RTL via ADB
I had this problem on my turbo after reading about a possible fix for snapchat image problems.
After a bit of googling, I came up with this simple fix.
This will only work if ADB Debugging is enabled and your PC is already authorized.
No need for root.
Code:
adb devices
adb shell
settings put global debug.force_rtl 0
reboot
And I suppose if you do NOT already have ADB enabled et al, you're SOL?
AnoraxAudio said:
And I suppose if you do NOT already have ADB enabled et al, you're SOL?
Click to expand...
Click to collapse
If your phone has a secure lock screen, it will not recognize a usb port for file transfer or ADB mode until the password/pin/pattern/etc. has been entered. The Cerberus method described above worked because it was able to meet this requirement. With this in mind, you have the following options depending on your lock screen situation:
1. Insecure lock screen, ADB previously enabled: use the ADB method described above.
2. Insecure lock screen, ADB disabled: Plug in the USB, transfer over your important files, reboot the phone in bootloader mode, select recovery mode, perform a factory reset.
3. Secure lock screen (all cases, assuming you can't unlock it with Cerberus or something similar): Wipe cache through recovery to see if that helps anything. If it doesn't, you can try reflashing the system image via mofo or fastboot to see if that helps anything. If not, bite the bullet and perform a factory reset. You will lose your data.
Now if you have mofo, you might be able to flash a rooted rom that can perform the adb method using a su.d script, but I'm not entirely sure about that.