So I deleted a few apps and am curious as to how I go about restoring them to the phone if I say, deleted them by accident. I made a backup of all of the apps on my pc in the SDK Tools subdirectory so they are all there. Also, will installing an .odex file be the same as an .apk file? Do I need to restore the .odex files or will they automatically be rebuilt?
How did you perform this backup? With adb? Then it will be easy to put the apps back. You should just be able to use adb with the install command. Just type in adb at the command prompt and read the help instructons for install. Not sure if the install command takes care of the .odex files. You could try it and then copy them over manually if they dont get copied. I am sure once you boot the phone the default .odex will be built, just a quess on that though.
anika200 said:
How did you perform this backup? With adb? Then it will be easy to put the apps back. You should just be able to use adb with the install command. Just type in adb at the command prompt and read the help instructons for install. Not sure if the install command takes care of the .odex files. You could try it and then copy them over manually if they dont get copied. I am sure once you boot the phone the default .odex will be built, just a quess on that though.
Click to expand...
Click to collapse
I would think that pushing the files back to the original location from recovery would be the safest bet. ADB install will install it to /data and I would think that the apps being system apps originally then they don't have the signatures anyway to allow an ADB install.
I think you're right
I believe I originally used ADB to put them in Android SDK Tools/Desktop/~ folder. When I tried installing them back I don't believe it worked. I specifically remember receiving an error when trying to install the .odex file about a database issue. Assuming it's a system file I'm trying to restore, does someone have the syntax for the push command or how I go about doing that?
If you have the .apk and .odex files on your computer, or really backed up anywhere, you can install them a few ways:
ADB Method
#Prerequisites:
Make sure you have the APK files in AndroidSDK/tools.
1. Connect the phone to your computer
2. Launch a command prompt and enter the following commands:
cd C:\AndroidSDK\tools
Replace "C:\AndroidSDK\tools" with the path to the tools folder in your SDK installation.
adb install filename.apk
Replace "filename.apk" with the name of the file you're trying to install.
Actually, **** it, the ADB method works anyway, why list a bunch lol
No wait, these are original files so you should probably put them back in their original location.
Just use "adb push filename.apk /system/app", replacing filename.apk with your filename, of course..
Push it
Okay, thanks for the tips. So I guess when you have files in the system/app directory on the phone it knows automatically to look there for program installs. This is good to know.
Could anyone please check and see if they have the adbd service in /sbin/adbd, using root explorer. I don't have it and am wondering if that is why my device is seen as offline.
Edit:
How to:
I don't know how or why this is happening yet, but if your Atrix is seen as offline by ADB for some reason like mine was, just copy this adbd file using root explorer to the /sbin directory and change the permissions to match the other files in the /sbin directory (rwxr-xr-x). (Extract the file from the zip first)
There is still one issue for me though. After a reboot the file disappears and I have to move another copy to the /sbin directory to get ADB working again. It seems as though the file is removed on shutdown, so I have not been able able to get the Early USB Enumeration working yet. Hopefully a solution will be found for this soon.
It is present on my phone.
Do you need me to upload it for you?
Yes please! That might fix my problem! For some reason I dont have it and I think that is why my phone is seen by my computer but is always offline. Hopefully this will work!
Sent from my MB860 using Tapatalk
Anyone that has the adbd service in /sbin/adbd, could you please upload it here for me. I would really appreciate it!
Sent from my MB860 using Tapatalk
here you go.
unzip and that's it. the file has no extension.
Let me know if this solved the ADB problem
Thanks a lot, I will let you know how it goes. Hopefully it works.
Sent from my MB860 using Tapatalk
clubtech said:
here you go.
unzip and that's it. the file has no extension.
Let me know if this solved the ADB problem
Click to expand...
Click to collapse
Holy crap, it worked!!! My device is not offline any more and adb is working!! For four days now I have been trying to figure this out. Thank you for the file!!
One weird thing though, after a reboot the file is gone and I have to copy it over to /sbin again to get it working. Now I need to figure out why it gets removed on a reboot. Anyone have any ideas?
airbillion said:
Could anyone please check and see if they have the adbd service in /sbin/adbd, using root explorer. I don't have it and am wondering if that is why my device is seen as offline.
Edit:
How to:
I don't know how or why this is happening yet, but if your Atrix is seen as offline by ADB for some reason like mine was, just copy this adbd file using root explorer to the /sbin directory and change the permissions to match the other files in the /sbin directory (rwxr-xr-x). (Extract the file from the zip first)
There is still one issue for me though. After a reboot the file disappears and I have to move another copy to the /sbin directory to get ADB working again. It seems as though the file is removed on shutdown, so I have not been able able to get the Early USB Enumeration working yet. Hopefully a solution will be found for this soon.
Click to expand...
Click to collapse
It gets removed because the ramdisk extracts it to that directory on boot
designgears said:
It gets removed because the ramdisk extracts it to that directory on boot
Click to expand...
Click to collapse
Is there a way to keep it in /sbin permanently? I think this is why early usb enumeration does not work for me.
Can I install your deodexed rom? I am nervous because I cant get the early usb enumeration working when the adbd file gets removed on reboot. Does the deodexed rom do anything requiring adb on the shutdown or reboot? Would I be ok without the adbd service until I reboot and replace the file?
airbillion said:
Is there a way to keep it in /sbin permanently? I think this is why early usb enumeration does not work for me.
Can I install your deodexed rom? I am nervous because I cant get the early usb enumeration working when the adbd file gets removed on reboot. Does the deodexed rom do anything requiring adb on the shutdown or reboot? Would I be ok without the adbd service until I reboot and replace the file?
Click to expand...
Click to collapse
on my phone, it is always in /sbin (before and after reboot).
The fact that on your phone it is getting deleted is strange.
Do you see other files under /sbin?
clubtech said:
on my phone, it is always in /sbin (before and after reboot).
The fact that on your phone it is getting deleted is strange.
Do you see other files under /sbin?
Click to expand...
Click to collapse
Yes a bunch: acpi_available, alsactl, apm_available, badblocks, blkid, blockdev.....vol_id. There are about 40 files, but the adbd seems to disappear after a reboot and my early usb enumeration does not work. I think it is because it adbd gets removed on a reboot. Is there a way to keep it in there after a reboot that you know of or to get usb early enumeration working?
not sure about a fix but as a work around, in theory you can try to create a script that runs on boot that always pushes the adbd file back into the /sbin folder. you can use a combination of programs like gscript to create the script and then a program like tasker to executive the script on boot or some other type of autostart program.
NguyenHuu said:
not sure about a fix but as a work around, in theory you can try to create a script that runs on boot that always pushes the adbd file back into the /sbin folder. you can use a combination of programs like gscript to create the script and then a program like tasker to executive the script on boot or some other type of autostart program.
Click to expand...
Click to collapse
Thanks, i will look into this.
What about adding it in then changing permissions on it to disable the system from deleting it?
Sent from my SAMSUNG-SGH-I897 using XDA App
Changing your adbd permissions back to stock may help, as the file in the .zip won't have the proper permissions. Do this:
Code:
chmod 0750 /sbin/adbd
The one in the zip will be 0777, which gives everyone read and write access, which isn't set normally.
Atrix ADB offline issue
clubtech said:
on my phone, it is always in /sbin (before and after reboot).
The fact that on your phone it is getting deleted is strange.
Do you see other files under /sbin?
Click to expand...
Click to collapse
I have the same problem! Any solutions found?
How do it get this onto a phone that is not rooted, so that I can root it?
Thanks.
Atrix Rooted Deodexed ADB Offine Issue
When I received my Atrix I used the program superoneclick to root the atrix and then Fully Deodexed, i enabled the sideloading of apps with the same program.
I then went to my external sd card where I had saved the apk's for titanium backup and adfree and installed them without any issues.Over the next few days I used my phone without any problems at all.I had some apk's on my computer that i wanted to push to my atrix so i tried to connect via adb and my phone was seen as offline no matter what computer, usb port or cable I used.I then thought that a hard reset might solve the issue so I went to the recovery menu and performed a system restore.This did not fix the problem.For days I tried to figure out how to fix it, until I realized that the adbd service in /sbins was missing so i got a copy and placed it in /sbins and adb worked again. However, after a reboot the adbd file is removed from /sbin and to get adb working again I have to place my copy of the adbd service back into the folder.The problem now though is that early usb enumeration in the recovery does not enable adb, the phone just boots normally after about 5 seconds.Thank you for your help and interest in my problem.Mroadster
airbillion said:
Could anyone please check and see if they have the adbd service in /sbin/adbd, using root explorer. I don't have it and am wondering if that is why my device is seen as offline.
Edit:
How to:
I don't know how or why this is happening yet, but if your Atrix is seen as offline by ADB for some reason like mine was, just copy this adbd file using root explorer to the /sbin directory and change the permissions to match the other files in the /sbin directory (rwxr-xr-x). (Extract the file from the zip first)
There is still one issue for me though. After a reboot the file disappears and I have to move another copy to the /sbin directory to get ADB working again. It seems as though the file is removed on shutdown, so I have not been able able to get the Early USB Enumeration working yet. Hopefully a solution will be found for this soon.
Click to expand...
Click to collapse
I really wish I could tell you how I did it, but I was going through this very same issue with loss of ADB after doing the SuperOneClick with a subsequent reset. After resetting the device I was not able to obtain ADB.
I got to a point where I decided I was going to just get rid of root and try to remove Superuser however every time I ran the script to remove it, it was still there. The script was running but no connection to ADB resulted in no execution.
I reset the device a couple more times and uninstalled all Motorola drivers from my computer. When I went through the initial setup and driver install again, it installed all the drivers like normal including the ADB communication. I confirmed ADB via "adb devices" and I everything seemed good to go.
I then used DG's aRoot to root once again without any issues at all. Every time I attempt to use ADB, it now connects flawlessly.
I have this problem as well and it is driving me insane as I bit off more than I could chew just trying to root my phone... Hopefully we can figure something out in the future.
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?