Here's one for the genius'
1. I rooted my phone successfully
2. I edited the settings.db file to allow side apps
3. I copied to copy the original settings.db file (that I think I may have corrupted) back and when I restarted my phone, I get a blank screen.... it will not boot into android.
I have a backup of the original settings.db file, but I need to know if there is there a way that I can copy this file back from recovery mode so that I can boot. I do get command line access in through adb, but it will not let me gain su access. Any help would be great.
I would say just hard reset the phone. It'll restore the settings.db back to the factory one.
masterofthebass said:
I would say just hard reset the phone. It'll restore the settings.db back to the factory one.
Click to expand...
Click to collapse
is it possible to do a hard reset without booting into android? I didn't know about that drats!
systoxity said:
is it possible to do a hard reset without booting into android? I didn't know about that drats!
Click to expand...
Click to collapse
I'm fairly sure there's a way to completely reset the phone while in recovery mode. Haven't done it, but I read about it somewhere.
I did a reset, but the phone still goes blank after the Galaxy logo. If I can mount the sdcard in recovery I think I can fix it. But I can't get it mounted.
take it back and ask for a replacement. Use your imagination.
If this fails and you have a brick phone that you cant do anything with, then i personally would try to open it up and see if that internal microsd card can be removed and hooked up to a card reader. Ofc this is very risky, and i am in no way telling you that you should follow in my theoretical footsteps. Be careful and good luck.
Is there a way to mount the internal sdcard. I have adb access in recovery mode, but not root. I have removable sdcard, but it does not seem to access that one from the recovery mode.
Also, I see the drives in "My Computer", but when I click them they ask me to insert a card. Is there a way to manually mount it from the ADB shell?
you have adb access? So when you have it plugged in and you go to cmd and type adb devices, the phone pops up as connected?
Yes... I have shell access, just can't get root or mount anything. I had already rooted the phone before all this began.
Try this.
Boot into recovery and type this into your computer
"adb shell"
"mount /sdcard"
"exit"
"adb push <whateverfile> /<path>/<whateverfile>"
"adb shell"
"umount /sdcard"
"exit"
I haven't tried this on my phone, but it should work. Please post back if you have any problems.
That will fail because /<path>/<whateverfile> isn't readable/writeable by non-root users (aka adbd). It's /dbdata or something like that, if memory serves.
For the record, booting into recovery mode and clearing all user data will NOT restore a working settings.db. I think the OP is SOL, although I'd love to learn that I'm wrong! :-(
Yeah I tried "mount /sdcard" already.... No luck, it just tells me "usage: mount [-r] [-w] [-o options] [-t type] device directory"
I forgot that you can't get root. The only thing i can tell you is to wait for the dump of the original rom whenever that comes out or take it to your ATT store and tell them it broke.
Mostly new to android, but could you create an update.zip which contains a valid dbsettings file and run it using the bootloader (hold down volume buttons and power up)? Would that then install it to the appropriate place?
If you can't recover the settings.db just take it back to the store and tell them the phone just started booting into a black screen. Leave it at that, turn it on for them to show them it does indeed do that. Then they will exchange it for you because it is so soon after the release date. (ask me how I know) :-/. Always check the db file before you copy it over.
centex99 said:
Mostly new to android, but could you create an update.zip which contains a valid dbsettings file and run it using the bootloader (hold down volume buttons and power up)? Would that then install it to the appropriate place?
Click to expand...
Click to collapse
tbae2 said:
If you can't recover the settings.db just take it back to the store and tell them the phone just started booting into a black screen. Leave it at that, turn it on for them to show them it does indeed do that. Then they will exchange it for you because it is so soon after the release date. (ask me how I know) :-/. Always check the db file before you copy it over.
Click to expand...
Click to collapse
both posts +1
If you can access the phone in adb shell, then you might be able to access the recovery console by going to your computer's command line, getting into the SDK tools folder, and typing "adb shell reboot recovery"
I used Unrevoked to root my desire earlier today. It went through all the steps fine, saying at the end that it was "victorious" and done. I re-booted, and got into the ClockwordMod, so I assume it worked as intended.
I'm trying to delete the stock bloatware off of my device (USCC Desire), but when I used the CMD line to remove some of the .apk files, it tells me they are read only. Does this mean I didn't get Root?
I noticed 3 things after using unrevoked.
1. My boot screen still shows that S-ON, and I was under the impression that Unrevoked turned this off.
2. I can get into clockwordmod, unlike before
3. I have the superuser app showing up on my app's list.
Am I missing something obvious?
BR3W CITY said:
I used Unrevoked to root my desire earlier today. It went through all the steps fine, saying at the end that it was "victorious" and done. I re-booted, and got into the ClockwordMod, so I assume it worked as intended.
I'm trying to delete the stock bloatware off of my device (USCC Desire), but when I used the CMD line to remove some of the .apk files, it tells me they are read only. Does this mean I didn't get Root?
I noticed 3 things after using unrevoked.
1. My boot screen still shows that S-ON, and I was under the impression that Unrevoked turned this off.
2. I can get into clockwordmod, unlike before
3. I have the superuser app showing up on my app's list.
Am I missing something obvious?
Click to expand...
Click to collapse
To test that you are infact rooted, please do the following:
1. Open command prompt/shell
2. cd into your AndroidSDK directory
3. Issue the command:: adb shell (if you see the # mark, then you are rooted -- otherwise type, su.)
To answer your questions:
1. When your phone says its "read-only file system"; this means that you need to issue the adb remount command; this will remount the system as RW (read/write), at which point you can go on deleting any apps you no longer want.
2. If you still have S-ON, that means you did not run the Unrevoked FOREVER file. You've only ran the Unrevoked 3 file. Notice when going to the Unrevoked site, that there are two different downloads.
3. Clockworkmod/superuser will exist because you are rooted and the process was successful.
alright.
So, I use adb shell, and get the $, type SU and it gives me the #. From there I go to do the remount, but it seems that all I get is "adb not found" I can do the list just fine from this point, but any adb commands result in not found.
I have also done the same commands (remount, remount with a specific directory) and it says "remount not found"
I can get the app list as mentioned, and have attempted to uninstall/remove a stock app, but get the "read-only" file system error. So it sound like the problem comes in either mounting the folder, or getting it to switch to read/write.
n/m, didn't read previous post properly
BR3W CITY said:
alright.
So, I use adb shell, and get the $, type SU and it gives me the #. From there I go to do the remount, but it seems that all I get is "adb not found" I can do the list just fine from this point, but any adb commands result in not found.
I have also done the same commands (remount, remount with a specific directory) and it says "remount not found"
I can get the app list as mentioned, and have attempted to uninstall/remove a stock app, but get the "read-only" file system error. So it sound like the problem comes in either mounting the folder, or getting it to switch to read/write.
Click to expand...
Click to collapse
What kind of phone? Some phones won't reliably mount the system partition read-write while running in normal mode. You should be able to do it from the clockwork recovery system though.
htc desire on 2.1, from USCC. I have not yet tried to do it from clockwork yet. I will try that later
Thanks!
Thanks for the help, putting her into ClockwordMod and using it to Mount /system solved the problem. Stock crap is gone yay!
I installed a custom font on my Tab. I decided to try and replace the Roboto_Bold.ttf, and that's why my Tab started to boot loop. (Long story short: I did the same thing to my Nexus, but I was able to salvage what I could and am now in the process of flashing a new ROM). I wiped the Cache/Dalvik on my Tab and flashed the ROM I had on it, over itself without wiping--thinking it would give me enough control to be able to flash a new ROM. I was wrong. I install the latest CWM (v5.5.0.4) and I go into Recovery mode. CWM won't let me Wipe Data. It just sits there, then ultimately kicks me back to the CWM "Home" screen; the same thing happens when I use an older version of CWM (v4.0.0.4). I've tried restoring backups and nothing works. I even had difficulty mounting the Tab on my laptop long enough to transfer over the newer ROM.
I have no clue what to do, and I feel so powerless. I usually can fix this kind of stuff by myself, but I can't this time.
Any and all help is appreciated.
Flash to stock using Odin ...I think you'll be able to reach downloading mode.
Of not try via adb of You are sure that debugging is checked
Sent from my GT-S5360 using Tapatalk
kishorsidu said:
Flash to stock using Odin ...I think you'll be able to reach downloading mode.
Of not try via adb of You are sure that debugging is checked
Sent from my GT-S5360 using Tapatalk
Click to expand...
Click to collapse
I can reach Download mode--but I have no clue how to flash anything from ODIN. -_-
Shameless bump.
Autocorrected from my GNexus
Here is a good guide to start over (is the last part "Re-“Stocking” Yer System…"): The Guide. The only problem is that you'll lose all your data.
I had a similar problem, but instead of going back to stock, I manually wiped the data/cache folders via adb, some folder was the culprit, it couldn't be deleted with its content, so first I deleted everything inside the folder and then the folder (in terms of commands, I did a rmdir instead of rm -r).
MapleSyrup said:
Here is a good guide to start over (is the last part "Re-“Stocking” Yer System…"): The Guide. The only problem is that you'll lose all your data.
I had a similar problem, but instead of going back to stock, I manually wiped the data/cache folders via adb, some folder was the culprit, it couldn't be deleted with its content, so first I deleted everything inside the folder and then the folder (in terms of comands, I did a rmdir instead of rm -r).
Click to expand...
Click to collapse
I don't mind losing the data; however, would you mind sharing the commands with me?
natezire71 said:
I don't mind losing the data; however, would you mind sharing the commands with me?
Click to expand...
Click to collapse
This is not a step by step guide, be careful if you decide to use this method, so you won't delete anything important.
First, to access the tablet shell
Code:
adb shell
To gain root permissions
Code:
su
To remove/wipe the data
Code:
rm -r /data/data/*
That's when I encountered the problem, I had to delete directories by groups until I found the problematic one. In my case was com.google.android.tts/
Then I did:
Code:
rm -r /data/data/com.google.android.tts/*
Code:
rmdir /data/data/com.google.android.tts/
MapleSyrup said:
This is not a step by step guide, be careful if you decide to use this method, so you won't delete anything important.
First, to access the tablet shell
Code:
adb shell
To gain root permissions
Code:
su
To remove/wipe the data
Code:
rm -r /data/data/*
That's when I encountered the problem, I had to delete directories by groups until I found the problematic one. In my case was com.google.android.tts/
Then I did:
Code:
rm -r /data/data/com.google.android.tts/*
Code:
rmdir /data/data/com.google.android.tts/
Click to expand...
Click to collapse
So, what was the problem you had? Couldn't you have just wiped in Clock Work?
Autocorrected from my GNexus
natezire71 said:
So, what was the problem you had? Couldn't you have just wiped in Clock Work?
Click to expand...
Click to collapse
That was the problem, I couldn't do it in cwm.
Just wanted to put it out there that I erased the data using Super Manager. Not a clean enough delete for preparing it for sale but good enough for my intentions.
Hi, i need a fix for this and fast !!! I've tried all that is listed on xda about this issue, but to no avail. Anyway, i forgot my pattern and went to the forgot pattern menu. My wifi was off, so i figured it would give a prompt of some kind to turn on the wifi and then log on to my google account. But nooooo, google supposes that everyone's wifi is on all the time. Please help, what do i do ? I rebooted to recovery, i made a nandroid and currently i am adb pulling the twrp folder from my N7. I would have just factory reseted it, no probs, but i remembered i have some EXTREMELY important works in colornote that i can't afford to lose. Please help, what do i do ?????
Looks like you answered your own question. Unless your Android isn't encrypted, just boot into TWRP and backup your data using adb:
adb pull /data/data C:\backup
Click to expand...
Click to collapse
The main thing you will have to concern about is restoring those data and make it readable by the app. There are several ways, but you can either:
adb push C:\backup\colornotes /data/data/colornotes
Click to expand...
Click to collapse
Don't forget some devices you need to give it write permission first: adb remount rw, though should not be needed with TWRP. Or just copy the folder back using a rooted file manager.
Then go into adb shell and fix permission of the files so the app can get access to them:
adb shell
su - (again shouldn't be needed wile in TWRP)
chmod -R 644 /data/data/colornotes (or 777 for full access)
Click to expand...
Click to collapse
Tips while in adb shell:
Check permissions of files by typing: ls -la
Check what partition is mounted and whether you have write privilege to it by typing: cat /etc/fstab
Also, if you use a custom rom like CyanogenMod or AOKP, there is an option to enable all widgets on the lockscreen. Just put the Power Control widget on the lockscreen, then you can toggle WiFi on and off. (Can't remember if this is also possible with stock.)
Have fun.
OR have a look here.
Looks like either of the two methods suggested would be feasible with only a recovery running, but the 2nd one is easiest (as a custom recovery wouldn't necessarily provide a statically-linked sqlite3 utility).
if it works it doesn't require any wiping.
BTW guess how I found this.... wait for it .... wait for it.... wait for it.... I used google search.
Hi, i forgot to mention that i made the twrp backup while i was locked out and whenever i try to restore from the backup after a factory reset, it goes back to square one... And when i did a full wipe and hoped to use titanium backup to extract stuff from the nandroid, it just gives me and empty list, but the backup is there, all 5gb of it
iAndroidOS said:
Hi, i forgot to mention that i made the twrp backup while i was locked out and whenever i try to restore from the backup after a factory reset, it goes back to square one...
Click to expand...
Click to collapse
Well, that is to be expected, is it not? You are restoring exactly what is already there - effectively a no-op.
OK, I just booted into TWRP (2.4.1.0) and confirmed that the (equivalent of the) following disabled my pattern lock on the next boot:
cd /data/system
mkdir foo
mv locksettings.* foo
mv gesture.key foo
I did all of the above (the 'cd' command is implicit) using TWRPs touch interface - didn't even need adb.
ymmv as I am using jdq39/4.2.2 and my tablet was not in a "locked-out" state, but its an easy thing to try.
I have successfully recovered the Kindle Fire HDX 8.9 from the soft brick which occurs from removing or altering system files.
THIS IS SPECIFICALLY FOR THOSE THAT REMOVED (PERSONALLY OR VIA SCRIPT) SOMETHING FROM THE SYSTEM PARTITION OR MESSED WITH THE BUILD.PROP. This guide focuses on a fix for ONE specific issue, so read it, determine what your issue is & then make the necesarry changes, or ask what changes need to be made. I have a bit of time over the next few days before going back to my job as a mechanical engineer, which means come the second week of January, I will be EXTREMELY busy.
I will be available via hangouts & IRC to guide you through recovery of your device when possible. The IRC channel will be #HDX & I will occasionally check in.
To recover your device, you must be rooted. Rooting may be possible while in boot loop, but it is VERY difficult & everything is about timing.
Firstly, you need to have everything from the root post by jcase to get started. You will also need adb & the Android SDK installed. Since it seems most of you are on Windows, I have forgone my linux distro & focused on finding a Windows solution, though this should work on Linux or Mac as well.
My particular brick was on purpose. It was based on the softbrick that can occur when using the root/Play store script by Ptiwee that is found here: http://forum.xda-developers.com/showpost.php?p=48739126&postcount=1
In this instance, if any part of the odex removal/replacement fails, you will be stuck in a bootloop. If you factory reset after being stuck, you complicate issues, because init is not able to complete & you then have an empty /data partition. This means that the fix differs depending on whether or not you did indeed perform a factory reset from the HDX recovery menu.
If you did perform a reset, then you need to do the following:
Download the HDX 8.9 root & follow jcase instructions from here: http://forum.xda-developers.com/showthread.php?t=2542456.
It will fail because the /data/local/tmp directory does not exist yet.
After completing these steps & failing, open cmd prompt & issue "adb shell" command.
Issue "su" command.
In the SU shell, issue the following set of commands:
mkdir /data
mkdir /data/local
mkdir /data/local/tmp
chmod 755 /data
chmod 755 /data/local
chmod 755 /data/local/tmp
adb shell
su
mount -o rw,remount /system
I then ran through the exploit from jcase again.
Then I opened a cmd window & did the following
adb root
adb shell
su
mount -o remount /system
This is where things get specific for my issue, which was the new services.odex that the ptiwee script installed.
for this issue, I opend a second terminal window & did the following:
adb push services.odex /data/local/tmp/services.odex
adb push DownloadProvider.odex /data/local/tmp/DownloadProvider.odex
adb push DownloadProviderUi.odex /data/local/tmp/DownloadProviderUi.odex
Now go back to your first cmd shell window & do the following (you may need to unplug the usb cable & quickly reinsert it):
adb shell
su
mount -o remount /system
exit
chmod 755 /data/local/tmp/services.odex
chmod 755 /data/local/tmp/DownloadProvider.odex
chmod 755 /data/local/tmp/DownloadProviderUi.odex
su
rm /system/framework/services.odex
cp /data/local/tmp/services.odex /system/framework/services.odex
chmod 755 /system/framework/services.odex
(for me on this issue, which was confirmed via logcat in Linux using Qtadb, the device screeen fully booted at this point, by itself)
However, you may need to also do this:
cp /data/local/tmp/DownloadProvider.odex /system/app/DownloadProvider.odex
cp /data/local/tmp/DownloadProviderUi.odex /system/app/DownloadProviderUi.odex
This would also apply to a modified build.prop bootloop. You would of course change the file you are move & chmod to build.prop & adjust the target directory accordingly.
My device is 100% working again & using this info, if you are stuck in a bootloop from changing, removing or whatever files, you should be able to similarly recover using a modified version of the data above.
Again, you really need to know what you were doing that caused the issue in the first place, but if you have a good idea what did it, then chances are you can recover.
Now hit thanks & let me know how you goofed up your device & we'll see if we can't fix it.S
Thanks for this. I tried this method to get google play working, which was no doubt something I did wrong in the process as others had success there (could be 8.9 vs 7 but I was willing to try). It was stuck with the orange Fire logo lit, but luckily ADB still recognized it, though windows wouldn't detect it as a USB drive. I had an issue when replacing services.odex with another, and this caused mine to immediately crash and never fully boot right when I changed the file. It was 0 bytes when viewed from the shell.
I was really rattled last night trying to figure out how to get the files back in place, as I could not get su to work from the shell, so permission denied on chmod and any attempt to remount /system as rw. Thankfully, I had the foresight to get the files pulled to my PC before I did the factory reset (I backed up all amazon files I was changing). Your instructions got me going again, and I finally got su to work and put those files back in place. It still wouldn't boot, so I did another factory reset (desperation) and re-rooted it.
Unfortunately, where it was once to the point with the Fire lit up, it vanishes when it would normally do that and is now stuck on a blank screen, though still recognized by adb. I can even get in the shell, but am at a loss as to what I might do next to get this thing booting. The only files I go around to modifying were DownloadProvider/ui apk and odex, along with services.odex. I'd very much appreciate any advice at this point.
I feel hopeful just to have su and still have access to adb with the files back in place, just confused on how it could be failing at this point. I'm obviously a novice and shouldn't have gone poking around too much until more experienced people had figured the 8.9 out, but I was too excited to get authentication from the Play Store working on this thing and willing to take the risk. If I get it working again, I'll be glad I've done all this, just because of how much I've learned from the process.
Edit: Yesss! chmod 755 on /system/framework did the trick. it was not executable Thank you so much for your effort here.
Followed the guide, Kindle is back again at least works...
But when I try to open the camera app... It never opens and just stays there until it closes... Any ideas?
(Will find more stuff and post just in case)
Poesini said:
Followed the guide, Kindle is back again at least works...
But when I try to open the camera app... It never opens and just stays there until it closes... Any ideas?
(Will find more stuff and post just in case)
Click to expand...
Click to collapse
@Poesini
Once you have it working, to the point of booting into the OS, grab the update.bin from Amazon (update-kindle-14.3.1.0_user_310079820.bin) here:
https://s3.amazonaws.com/kindle-fire-updates/update-kindle-14.3.1.0_user_310079820.bin
Once downloaded, grab a root level file explorer. I use the paid Root Explorer because it has built in root acess, a text editor & a ro/rw toggle button, but others should surely work. Make sure that the /System partition/directory is mounted as RW, then open the file build.prop & edit all the entries that say "310079820" to be"310079819".
You will find them in the build.prop as follows:
ro.build.version.incremental=14.3.1.0_user_310079820
ro.build.version.number=310079820
ro.build.description=apollo-user 4.2.2 JDQ39 14.3.1.0_user_310079820 release-keys
ro.build.fingerprint=Amazon/apollo/apollo:4.2.2/JDQ39/14.3.1.0_user_310079820:user/release-keys
Do not add the parenthesis, just change the last three number to 819 & then be sure to save the file. Open it again to ensure the edits were made, so you are certain that the device directory was indeed RW. Once that is done, make sure the permissions are set to 0644, or rw-r--r-- & check the ownership to make certain the owner & group are both set to "Root". If you do not work on the "live" build.prop, then copy the edited build.prop to the root folder (/) first, then check permissions or change them using adb chown & chmod commands as required.
Again, I suggest copying the file to your PC as a backup, though you will have a copy in the downloaded update.bin (which is just a zip archive). I also suggest using a root explorer with a built in text editor, like Root Explorer.
Once this is done & you are certain the build.prop has been edited, copy the update.bin to the storage (sdcard) root & reboot the device.
Once the device has reboot, go into settings, device, system updates & select the install update button. Follow the directions & the device will reboot again & install the firmware. Any mods made to the System directory will be gone & everything should work again.
chratcliff said:
Thanks for this. I tried this method to get google play working, which was no doubt something I did wrong in the process as others had success there (could be 8.9 vs 7 but I was willing to try). It was stuck with the orange Fire logo lit, but luckily ADB still recognized it, though windows wouldn't detect it as a USB drive. I had an issue when replacing services.odex with another, and this caused mine to immediately crash and never fully boot right when I changed the file. It was 0 bytes when viewed from the shell.
I was really rattled last night trying to figure out how to get the files back in place, as I could not get su to work from the shell, so permission denied on chmod and any attempt to remount /system as rw. Thankfully, I had the foresight to get the files pulled to my PC before I did the factory reset (I backed up all amazon files I was changing). Your instructions got me going again, and I finally got su to work and put those files back in place. It still wouldn't boot, so I did another factory reset (desperation) and re-rooted it.
Unfortunately, where it was once to the point with the Fire lit up, it vanishes when it would normally do that and is now stuck on a blank screen, though still recognized by adb. I can even get in the shell, but am at a loss as to what I might do next to get this thing booting. The only files I go around to modifying were DownloadProvider/ui apk and odex, along with services.odex. I'd very much appreciate any advice at this point.
I feel hopeful just to have su and still have access to adb with the files back in place, just confused on how it could be failing at this point. I'm obviously a novice and shouldn't have gone poking around too much until more experienced people had figured the 8.9 out, but I was too excited to get authentication from the Play Store working on this thing and willing to take the risk. If I get it working again, I'll be glad I've done all this, just because of how much I've learned from the process.
Edit: Yesss! chmod 755 on /system/framework did the trick. it was not executable Thank you so much for your effort here.
Click to expand...
Click to collapse
Glad to get you pointed in the right direction. This is what XDA used to be. How I learned anything at all. I am a mechanical engineer, not a software or hardware guy. Just a guy that will not give up on something broken.
It's all about taking little queues from here & there & then trying to assemble parts of different things into accomplishing what it is you are working on. All of this was based on things I tried or read in the past, working to root devices like the Xoom, etc... After reading about the exploit we had applied (what it is & how it works, some of which was beyond me), I was able to surmise that the exploit we used was still there as was the ability to access root permission, but that the tablet had "forgotten" we had root access rights because of the wipe. We just had to use adb to give it the files "memory" of our access to root & the permission to use them, in essence, tell it what we wanted. Working with a Linux or Android device is like working with the smartest person in the world that is also a 5 year old. It can do anything, yet hasn't the common sense to get it done. We need to provide that for it's brilliance to become useful.
As mentioned above, I highly recommend modding the build.prop & re-flashing the update.bin to have a clean slate.
GSLEON3 said:
Working with a Linux or Android device is like working with the smartest person in the world that is also a 5 year old. It can do anything, yet hasn't the common sense to get it done.
Click to expand...
Click to collapse
This is the damned truth never better spoken lol
Sent from my SPH-L900 using xda app-developers app
GSLEON3 said:
Ahhhhh.... XDA! The thrill of it all, you desperately want something now, you're a smart guy, you can do it & nothing beats that feeling of your sphincter tightening up, your heart racing, as you wait for that device to reboot....wait.....maybe another minute.....okay....crap... what do I do now? I love that feeling! I mean YOLO. Livin' dangerous dog, lol... Okay, I "bricked my device on PURPOSE, since there is a Play Store script in a ceertain tool that seems to be broken, or is missing information from the instructions, such as safestrap, or something.... That part I haven't figured out. I asked the creator to take a look at what he did & in the mean time, this should get you fixed up. It is actually much easier is you were not panicked to the point of factory resetting, but either way, the info below will get you sorted out.
I have successfully recovered the Kindle Fire HDX 8.9 from the soft brick which occurs from removing or altering system files.
THIS IS SPECIFICALLY FOR THOSE THAT REMOVED (PERSONALLY OR VIA SCRIPT) SOMETHING FROM THE SYSTEM PARTITION OR MESSED WITH THE BUILD.PROP. This guide focuses on a fix for ONE specific issue, so read it, determine what your issue is & then make the necesarry changes, or ask what changes need to be made. I have a bit of time over the next few days before going back to my job as a mechanical engineer, which means come the second week of January, I will be EXTREMELY busy.
I will be available via hangouts & IRC to guide you through recovery of your device when possible. The IRC channel will be #HDX & I will occasionally check in.
To recover your device, you must be rooted. Rooting may be possible while in boot loop, but it is VERY difficult & everything is about timing.
Firstly, you need to have everything from the root post by jcase to get started. You will also need adb & the Android SDK installed. Since it seems most of you are on Windows, I have forgone my linux distro & focused on finding a Windows solution, though this should work on Linux or Mac as well.
My particular brick was on purpose. It was based on the softbrick that can occur when using the root/Play store script by Ptiwee that is found here: http://forum.xda-developers.com/showpost.php?p=48739126&postcount=1
In this instance, if any part of the odex removal/replacement fails, you will be stuck in a bootloop. If you factory reset after being stuck, you complicate issues, because init is not able to complete & you then have an empty /data partition. This means that the fix differs depending on whether or not you did indeed perform a factory reset from the HDX recovery menu.
If you did perform a reset, then you need to do the following:
Download the HDX 8.9 root & follow jcase instructions from here: http://forum.xda-developers.com/showthread.php?t=2542456.
It will fail because the /data/local/tmp directory does not exist yet.
After completing these steps & failing, open cmd prompt & issue "adb shell" command.
Issue "su" command.
In the SU shell, issue the following set of commands:
mkdir /data
mkdir /data/local
mkdir /data/local/tmp
chmod 755 /data
chmod 755 /data/local
chmod 755 /data/local/tmp
adb shell
su
mount -o rw,remount /system
I then ran through the exploit from jcase again.
Then I opened a cmd window & did the following
adb root
adb shell
su
mount -o remount /system
This is where things get specific for my issue, which was the new services.odex that the ptiwee script installed.
for this issue, I opend a second terminal window & did the following:
adb push services.odex /data/local/tmp/services.odex
adb push DownloadProvider.odex /data/local/tmp/DownloadProvider.odex
adb push DownloadProviderUi.odex /data/local/tmp/DownloadProviderUi.odex
Now go back to your first cmd shell window & do the following (you may need to unplug the usb cable & quickly reinsert it):
adb shell
su
mount -o remount /system
exit
chmod 755 /data/local/tmp/services.odex
chmod 755 /data/local/tmp/DownloadProvider.odex
chmod 755 /data/local/tmp/DownloadProviderUi.odex
su
rm /system/framework/services.odex
cp /data/local/tmp/services.odex /system/framework/services.odex
chmod 755 /system/framework/services.odex
(for me on this issue, which was confirmed via logcat in Linux using Qtadb, the device screeen fully booted at this point, by itself)
However, you may need to also do this:
cp /data/local/tmp/DownloadProvider.odex /system/app/DownloadProvider.odex
cp /data/local/tmp/DownloadProviderUi.odex /system/app/DownloadProviderUi.odex
This would also apply to a modified build.prop bootloop. You would of course change the file you are move & chmod to build.prop & adjust the target directory accordingly.
My device is 100% working again & using this info, if you are stuck in a bootloop from changing, removing or whatever files, you should be able to similarly recover using a modified version of the data above.
Again, you really need to know what you were doing that caused the issue in the first place, but if you have a good idea what did it, then chances are you can recover.
Now hit thanks & let me know how you goofed up your device & we'll see if we can't fix it.
Click to expand...
Click to collapse
What should I do if I connect my kindle to PC without any reaction? I had done factory reset before. ADB cannot be recognized, nor do any special USB stuff. I thought mine got bricked for build.pro and I can just turn it to original recovey. Can you help me, please?
TOM XIE said:
What should I do if I connect my kindle to PC without any reaction? I had done factory reset before. ADB cannot be recognized, nor do any special USB stuff. I thought mine got bricked for build.pro and I can just turn it to original recovey. Can you help me, please?
Click to expand...
Click to collapse
Need more info & less quote. lol...
Does it turn on at all? What is on the screen? Is it lit, but looks like it's off? What EXACTLY did you change in the build.prop? Even a brick is usually recognized as SOMETHING when the device is attached (at least in Windows), so if nothing is being recognized, you may have an issue with PATH or just a finicky sdk installation. Are you on Windows or Linux?
GSLEON3 said:
Need more info & less quote. lol...
Does it turn on at all? What is on the screen? Is it lit, but looks like it's off? What EXACTLY did you change in the build.prop? Even a brick is usually recognized as SOMETHING when the device is attached (at least in Windows), so if nothing is being recognized, you may have an issue with PATH or just a finicky sdk installation. Are you on Windows or Linux?
Click to expand...
Click to collapse
Thank you for helping me! I followed this http://forum.xda-developers.com/showthread.php?t=2582773 and replaced buil.prop offered. I can turn it on by holding power button for several seconds and it showed the gray "kindle fire" logo for a few seconds,then turn off again.By the way,I am using win7 and I have no idea about PATH and sdk.
Tried, and failed... Since my kindle fire stopped at the sliver kindle fire screen and it reboots again and again, I can't even get the access to adb...
I think maybe I need to request a replacement from Amazon...Or someone could give me a usable System image and fastboot.exe.....
EDIT: Weird....After 10 minute's rebooting, my kindle suddenly works....Everything seems to be fine....
TOM XIE said:
Thank you for helping me! I followed this http://forum.xda-developers.com/showthread.php?t=2582773 and replaced buil.prop offered. I can turn it on by holding power button for several seconds and it showed the gray "kindle fire" logo for a few seconds,then turn off again.By the way,I am using win7 and I have no idea about PATH and sdk.
Click to expand...
Click to collapse
@TOM XIE If you used that build.prop provided in that thread, then you replaces yours with one meant for the 7" HDX. You need to download the update.bin from Amazon & extract it (it is just an archive zip). You will then have wht you need.
scx110a said:
Tried, and failed... Since my kindle fire stopped at the sliver kindle fire screen and it reboots again and again, I can't even get the access to adb...
I think maybe I need to request a replacement from Amazon...Or someone could give me a usable System image and fastboot.exe.....
EDIT: Weird....After 10 minute's rebooting, my kindle suddenly works....Everything seems to be fine....
Click to expand...
Click to collapse
Not weird at all. This will occasionally happen until the corrected changes make it into the Dalvik. Tense stuff I know, but jcase finding the device vulnerable to the master key #2 is a blessing in disguise. Hard for simple errors to really mess things up. Not saying go at it, but simple changes of most things (do not mess with bin, xbin or any of the basic systemui framewor-res) will not be a total loss.
Now I just need to take the time to decompile tiwee's Play Store mod & see if I can't find a typo or something amiss.
GSLEON3 said:
@TOM XIE If you used that build.prop provided in that thread, then you replaces yours with one meant for the 7" HDX. You need to download the update.bin from Amazon & extract it (it is just an archive zip). You will then have wht you need.
Click to expand...
Click to collapse
I have downloaded update.bin from Amazon. The most difficult part is that my kindle cannot be recognized as anything.
TOM XIE said:
I have downloaded update.bin from Amazon. The most difficult part is that my kindle cannot be recognized as anything.
Click to expand...
Click to collapse
Are you running Windows or Linux?
Also, do you have the Android SDK & the JDK installed.
Both of these are important steps. Also, was the device rooted & if you plug it into the USB port in a windows machine, do you see anything happen in Device Manager? It should fail to install the device (MTP) but if you have everything installed, you should try running it in a terminal directly in the sdk tools directory.
Also, have you updated your environmental or pam.environmental file as well in your bash file?
EDIT: I just went out on a limb again & I pushed the HDX7 build.prop to my device & rebooted. I was able to cp the repaired build.prop, so tell me everything you have done (what you tried & changed, modded or installed into system or root on the HDX) & check the above tips.
GSLEON3 said:
Not weird at all. This will occasionally happen until the corrected changes make it into the Dalvik. Tense stuff I know, but jcase finding the device vulnerable to the master key #2 is a blessing in disguise. Hard for simple errors to really mess things up. Not saying go at it, but simple changes of most things (do not mess with bin, xbin or any of the basic systemui framewor-res) will not be a total loss.
Now I just need to take the time to decompile tiwee's Play Store mod & see if I can't find a typo or something amiss.
Click to expand...
Click to collapse
Hope you good luck.... That's really a complex thing since Amazon did so many changes to the DownloadProvider....
May ask you a question? plz
GSLEON3 said:
Are you running Windows or Linux?
Also, do you have the Android SDK & the JDK installed.
Both of these are important steps. Also, was the device rooted & if you plug it into the USB port in a windows machine, do you see anything happen in Device Manager? It should fail to install the device (MTP) but if you have everything installed, you should try running it in a terminal directly in the sdk tools directory.
Also, have you updated your environmental or pam.environmental file as well in your bash file?
EDIT: I just went out on a limb again & I pushed the HDX7 build.prop to my device & rebooted. I was able to cp the repaired build.prop, so tell me everything you have done (what you tried & changed, modded or installed into system or root on the HDX) & check the above tips.
Click to expand...
Click to collapse
I have still brick my device my device is hdx7. My latop os window7.
Connect my kindle to laptop's usb port. My laptop is.shown qhsusb_bulk so i follow your step but
Not booting my device. Now i know my device 's system erase. Second step i connect nomal cable but shown unknown
MTP device. Plz help me. Do you know adb work? On my win7 laptop?
Or another method? Plz please help.me sorry for my english
cjdfyd2 said:
I have still brick my device my device is hdx7. My latop os window7.
Connect my kindle to laptop's usb port. My laptop is.shown qhsusb_bulk so i follow your step but
Not booting my device. Now i know my device 's system erase. Second step i connect nomal cable but shown unknown
MTP device. Plz help me. Do you know adb work? On my win7 laptop?
Or another method? Plz please help.me sorry for my english
Click to expand...
Click to collapse
Need to leave device alone for an hour or more while unpluged, no PC, no power.
After that hour, then press & hold the power button for 3 minutes, or until device starts. If it does not start into bootloap, then release the power button & let sit for a few minutes. Try to turn it on again.
Also, what did you do to the device? What did you mod, or change or add that caused the issue?
As for Windows, I have found that for adb to work on the HDX, you need to have the SDK installed & that sometimes it will not recognize the device from anywhere but the sdk folder.
Also, I had some issues getting some of the commands to work occasionally in Windows, which is why I choose to do these things in Linux.
GSLEON3 said:
@Poesini
Once you have it working, to the point of booting into the OS, grab the update.bin from Amazon (update-kindle-14.3.1.0_user_310079820.bin) here:
(still can't post links)
Once downloaded, grab a root level file explorer. I use the paid Root Explorer because it has built in root acess, a text editor & a ro/rw toggle button, but others should surely work. Make sure that the /System partition/directory is mounted as RW, then open the file build.prop & edit all the entries that say "310079820" to be"310079819".
You will find them in the build.prop as follows:
ro.build.version.incremental=14.3.1.0_user_310079820
ro.build.version.number=310079820
ro.build.description=apollo-user 4.2.2 JDQ39 14.3.1.0_user_310079820 release-keys
ro.build.fingerprint=Amazon/apollo/apollo:4.2.2/JDQ39/14.3.1.0_user_310079820:user/release-keys
Do not add the parenthesis, just change the last three number to 819 & then be sure to save the file. Open it again to ensure the edits were made, so you are certain that the device directory was indeed RW.
Again, I suggest copying the file to your PC as a backup, though you will have a copy in the downloaded update.bin (which is just a zip archive). I also suggest using a root explorer with a built in text editor, like Root Explorer.
Once this is done & you are certain the build.prop has been edited, copy the update.bin to the storage (sdcard) root & reboot the device.
Once the device has reboot, go into settings, device, system updates & select the install update button. Follow the directions & the device will reboot again & install the firmware. Any mods made to the System directory will be gone & everything should work again.
Click to expand...
Click to collapse
Tried using this method after the installation of gapps failed due to system directory being full (1gb)... I already gave up on this device until I saw this... Many Thanks! :highfive:
Thanks your answer and happy new year, i was wonder if could you help me?
GSLEON3 said:
Need to leave device alone for an hour or more while unpluged, no PC, no power.
After that hour, then press & hold the power button for 3 minutes, or until device starts. If it does not start into bootloap, then release the power button & let sit for a few minutes. Try to turn it on again.
Also, what did you do to the device? What did you mod, or change or add that caused the issue?
As for Windows, I have found that for adb to work on the HDX, you need to have the SDK installed & that sometimes it will not recognize the device from anywhere but the sdk folder.
Also, I had some issues getting some of the commands to work occasionally in Windows, which is why I choose to do these things in Linux.
Click to expand...
Click to collapse
my device is kindle 7", i had followed step Cpasjuste's http://forum.xda-developers.com/showthread.php?t=2577826 and i delete these files
"/system/app/amazonmp3_4010410.apk" -> amazon mp3 ..
"/system/app/Email_310006810.apk" -> email app, replaced by gmail which is currently broken !
"/system/app/Photos_7016610.apk" -> photos app
"/system/app/OfficeSuiteViewer.apk" -> office ..
"/system/app/S2Service.apk" -> something to do with cellular i think
"/system/app/Launcher-release-signed_81224610.apk" -> amazon launcher
"/system/app/AmazonWebViewLib_1109110.apk" -> slik browser
"/system/app/com.amazon.cloud9-platform_38038110.apk" -> amazon cloud/sync
and flashing he's gapps file. and then my device is bricked. it's shown grey kindle fire logo only, so i reboot many times but still shown kindle fire logo only.
So i install ubuntu my laptop, and follow your step jcase's file download on my computer.
but i don't know how next step? how open "su" file? by sdk? work on window os? or linux os? sorry for many question plz help me..and happy new year
Hello,
My kindle is bootlooping on the grey kindle and orange fire logo. This is a HDX 7.
I rooted, went a bit crazy with uninstalling kindle bloatware, screen went black, thought factory reset would do the trick, end up in bootloop.
My computer recognizes the kindle so what should I do?