Hi XDA,
I think I might need your help. Just got a new Kindle HDX 7. For once I decided to not root a device - sideload seemed sufficient for me. So I let it update from 13.3.0.5 up to 13.4.5.1, everything worked fine and I started to install apps. Following the new description here even managed to install GApps. Device worked for some time until recently. After a reboot the device was softbricked - colored kindle fire logo flashing. Luckily I have ADB access, hope that's worth something
Situation: Unrooted stock 4.5.1, GApps installed, soft brick, ADB access //solved http://forum.xda-developers.com/showpost.php?p=57084104&postcount=4
Last actions before softbrick: Add my google mail account to the built in mail function, GMail was also installed and configured. Switched on ADB over TCIP, just to check if it works. After a restart: Congratulations, device won't boot. Of course I wonder how my device could get bricked, since I never rooted...
Before digging into that further, would a factory reset be possible? Usuallly this would be the first thing to do, but for the Kindle this just seems to make the problem even worse. Or should I just do it anyway, see what happens, and if it fails send it back to Amazon? As mentioned: never rooted, so warranty shouldn't be voided.
Access via ADB: I'm not that familiar with Linux/Android, but it tried to look into it. (So far I haven't tampered with anything)
top shows com.androi.systemui woking at 50% cpu.
logcat: here comes the interesting part, apparantly com.google.android.gms crashes all the time and is restarted, on and on and on, causing the bootloop.. (Logcat attached for the curious ones) Nope, not the cause, tried to boot with the wifi router of (still bricked), different logcat. Attached it. Apparently google crashing is "normal". Any special tool to look at the logcat? Some IDE to search for/analyse critical errors? // Found a guide -> http://forum.xda-developers.com/showthread.php?t=2274119
Now I can only tell what the tablet is doing during the bootloop, but not what the main cause is, or even how to fix it. At first I tried to uninstall com.google.android.gms. Resulting in: failure, nothing changed.. Maybe the solution lies somewhere withing the capacities of the package manager?
In the logcat, at the end you can see that com.google.android.gms gets startet over and over again. yeah, for the first one, still trying to figure out the second one.
So, that's it, another guy whining about his broken tablet I hope that "new kind" of bootloop is a bit of a motivating challenge for all the experts here. Thank you very much!
Best regards, Grtschnk
You can do hard reset, no problem with this in your case.
And you can try something like this while bootlop:
Code:
adb uninstall com.google.android.gms
or maybe
Code:
adb shell
pm disable com.google.android.gms
need to try
Thank you very much for your answer! As mentioned hard reset would have been my first option, but was afraid to break it even more.
I already tried the commands you mentioned, no success, but things have changed anyway... edited my first post.
Is hard reset still possible? I'm studying the logcat to localize the error (ugh, feeling like 13 again when I tried to delete system32.exe on windows ME because it was causing errors xD ).
If hard reset, how to do on Kindle?
Code:
//Press Power + Volume Down
//Recovery Mode
//Reset
or
Code:
adb shell
recovery --wipe_data
or maybe give a first try by
Code:
adb shell
recovery --wipe_cache
Thank you very much again for your time! I really appreciate it. As someone who grew up with Windows 3.11, it's hard for me to get warm with the linux file system
//Press Power + Volume UP
//Recovery Mode
//Reset
about other commands, you can try, but I guess you cannot do any recovery commands without root.
ONYXis said:
//Press Power + Volume UP
//Recovery Mode
//Reset
about other commands, you can try, but I guess you cannot do any recovery commands without root.
Click to expand...
Click to collapse
Yay, worked! Dzięki! Up, down - always get them confused..
Related
So I decided to try to apply a hide bar/status bar toggle i found online which required replacing the services.jar found in system/framework with a custom services.jar. Unfortunately, after rebooting, I'm stuck at the asus logo boot loop and if I try to recover it just goes to an Android on it's back with an exclamation mark. Any help would be appreciated!
setup adb and see if you can get the device to be recognized by doing adb devices
Yeah, adb isn't recognizing it
That's why I never do mods like that, too risky.
GOOD LUCK ln getting it back running.
songmeesay said:
So I decided to try to apply a hide bar/status bar toggle i found online which required replacing the services.jar found in system/framework with a custom services.jar. Unfortunately, after rebooting, I'm stuck at the asus logo boot loop and if I try to recover it just goes to an Android on it's back with an exclamation mark. Any help would be appreciated!
Click to expand...
Click to collapse
First of all: If it's turning on and the screens showing the ASUS logo and the Android on its back its NOT BRICKED! Brick = Paperweight which yours is not.
If you can get ADB working then pushing out the replacement files again should be fairly simple. Got into the same issue when I was trying to find a way to root mine - would bootloop and ADB was only available for 5-10 seconds before it would reboot again. Eventually made a .bat file to perform the remounting of /system and copying of files.
"Adb wait-for-device" is a handy command to use - it'll pause until it sees a device connect. If it's at the start of a script it'll wait till it sees the device before it runs anything else.
If this still fails you could try googling for a way to manually update? Not sure how lucky you'll be.
If this fails then the only way is to re-flash it. Unfortunately we don't yet have a way of doing this (and won't have until ASUS unlocks the bootloader) so your only option is to wait around hoping it's sooner rather than later, or send it back to ASUS and pay to have it repaired.
Hope you get it fixed.
Cool, I'll try the above and if it fails I don't mind waiting around to re-flash. Kept my GT 10.1 for situations like this. Thanks.
hartej said:
First of all: If it's turning on and the screens showing the ASUS logo and the Android on its back its NOT BRICKED! Brick = Paperweight which yours is not.
If you can get ADB working then pushing out the replacement files again should be fairly simple. Got into the same issue when I was trying to find a way to root mine - would bootloop and ADB was only available for 5-10 seconds before it would reboot again. Eventually made a .bat file to perform the remounting of /system and copying of files.
"Adb wait-for-device" is a handy command to use - it'll pause until it sees a device connect. If it's at the start of a script it'll wait till it sees the device before it runs anything else.
If this still fails you could try googling for a way to manually update? Not sure how lucky you'll be.
If this fails then the only way is to re-flash it. Unfortunately we don't yet have a way of doing this (and won't have until ASUS unlocks the bootloader) so your only option is to wait around hoping it's sooner rather than later, or send it back to ASUS and pay to have it repaired.
Hope you get it fixed.
Click to expand...
Click to collapse
Thank you!
I gotta try this
Could you post your bat file or contents
Sent from my PC36100 using XDA App
Hello, after playing with a tablet I got boot loop so below is solution for this.
This is what I wrote first:
I purchased Chinese tablet called CyberNav, there is link to the website with specs http://www.dracotek.com/cybernav-7-...ps-navigator-ultra-slim-wifi-8gb-gps70yw.html It works great and is worth the money. I received- on request- firmware for it, but it is with .img extension and I have no idea how to get to the files. Attached application PhoenixCard should install it on sd card but it does nothing. So there is my question- can anyone help me with it? Possibly root it? Or update to newer firmware version? I'll post a link to, just need to upload it to my dropbox on my next break at work.
Sek
im pretty sure you need a 3rd party application to flash that firmware, i think you load the .img file into the software on your pc, connect tablet in flash/recovery mode then flash it that way, dont know which software you would need to use though , sorry i cant help further
There is link to rar package http://db.tt/jm7eHfbq
If there is someone who wants to spend some time... Please help.
Bump
Some new infos:
As far I found out tablet is detectable during boot in adb, but it stays in boot loop. I think I've got right usb drivers.
I tried unyaffs the .img file using C:/unyaffs/unyaffs pw08.img but it shows file corrupted (might be wrong method?).
Logcat attached.
Maybe there is someone who will find what it's missing...
I see there is nobody who can help me, so... If some of u have similar problem with chinese tablet- bootloop, can't flash it with LiveSuit our update from sdcard, I found solution which worked for me. Using adb, pulled catalog /dev/data/ to hard disk, then deleted all dalvik cache, installed by me apps and almost every other file from /data on my hard disk. Then typed adb remount, then adb shell rm -r /dev/data/* to delete all data catalog on tablet. Then pushed /data catalog from my hard disk to tablet, and finally adb reboot. And it WORKS! Booting without problems. I wasted 4 days on research how to turn it in flash mode etc. But it was very simple.
Cheers
Sek
Hi, sek111
It was necessary to use the LiveSuite to flash through usb.
Thank you very much, from your post, I found the firmware for my tablet.
An experience with another low cost tablet with Bootloop
I happen to got my tab (Wammy from WickedLeak.org) stuck in BootLoop and was struggling to get a way out for the past 3 days, checking almost all of the posts for this issue!
The tab would stuck on the android loading animation despite running for 2-3 hours and after several hard reboots, it throw-ed following error-
Encryption Unsuccessful
encrytion was interupted and cant complete. as a result the data on your tablet is no longer accessible
to resume using your tablet, you must perform a factory reset. when you set up your tab after the reset, u'll hav an opportunity to restore any data that was backed up to ur google account
Click to expand...
Click to collapse
Despite going for the factory reset, it still didn't workout as the reset activity never completed or proceeded. I happen to be a beginner/noob and was trying my luck with possible solution but was comfortable with ADB stuff and workaround. Well i checked the solution which sek111 offered in this post and it was most closely helped me out. So i would like to Thank him a ton for sharing his solution.
Another method for few others if you don't get through the technical stuff and handling all the flashing tools, i was successful in bringing up the setting window of my tab and chose to do Reset via GUI which worked. Actually my battery got drained out to 7% and a popup message for same displayed while i was on the above error page. I selected the "check battery" option from that pop up and got my way out via factory "Backup and Reset" option under settings.
I hope this might help few people if not all! But the XDA forum is great and everyone will find a solution here. Cheers!!!
So I got this wm8850 chinese generic tablet. The camera is in the front in the middle (wide). It was shipped to me with 4.0.3 in boot loop. I soon found out that it boots into safe mode when I usb to pc. This is the furthest I've gotten with it so far. I can adb into it and have already tried to wipe data. It seems like since its from factory screwed up that a may need to reload the firmware or the os or something. Im kind of a noob because I only have my droid x. I've gotten it out of a boot loop before but I also knew what I had done to cause it so I fixed it. I tried to follow seks adb commands but im too noob to do it I guess. I was able to wipe data and dalvik-cache. Issue still occurs . If anybody can give me some adb commands than can help I would greatly appreciate it. Im fairly sure that I found the firmware elsewhere on xda. I thank you guys for any help at all you can give. I don't wanna send it back without trying everything software related as I can, but ill send it back if I can't fix it or if I brick it
Sent from my DROIDX using xda app-developers app
i have same problem in my china mobile.. dupad k1 ... after in installed new boot screen, device stuck in boot... please help to recover my device in step by step....
I was rooted using ViperMod. I took the JB OTA, thinking rootkeeper would work. Wound up with the partial root issue (some apps worked, i.e. Anti, Network Spoofer, Root Explorer, but root checker and the Linux Installer for Backtrack gave no root errors), so I tried the method here: http://forum.xda-developers.com/showthread.php?t=1911261
I got through step 3. Step 4 gave me a permission denied error, so I used Root Explorer to turn on all permissions for /data/local/tmp. At that point, adb push claimed to have worked through step 6, but I noticed my Prime had frozen. Before I went any further, I decided to hard reboot (hold down power button), to be sure everything was running proper before I started in with shell commands.
Upon reboot, it now sticks at the initial splash screen. I can vol-down & get to the bootloader there, giving me the 4 standard options. Recovery gives me the dead-looking Andy with exclamation mark (I assume because I don't have a backup image, which yes, I know, was stupid not to have. Hindsight.). The OS option says it's starting from a cold boot, but freezes there and does nothing else. I can access fastboot, and at least the reboot command seems to work, but I haven't tried anything else, as I'm not familiar with fastboot, and have no idea where to go from there. I'm hoping against hope I don't have to use the wipe action, as I have a lot of time and data invested in the thing.
I'm also able to vol-up and have APX recognized on my Win7 machine, but I admittedly have no idea what to do with that.
If anyone could help me here, especially if it would include NOT wiping my Prime, I would be forever grateful. Thank you in advance for any advice.
Please, I'm begging the community for help. I have no idea where to go from here. From my view, I don't know what went wrong. I simply changed permissions for one folder and pushed three files.
I don't have anyone else to help with this. This community has always been amazing when someone needed help, and I'm asking, as a man who seems to have screwed himself, for that help for me.
Again, I offer thanks in advance for any advice.
I apologize if this has been asked before, but I have been searching around through dozens of threads over days and don't see much about people in a bootloop without ADB access. Is this an unsolvable problem or is there some way to reconnect to ADB so I can run a fix?
Just for background, I had a fully functioning towel rooted kindle 8.9 HDX which had the Google marketplace, OTC disabled, APEX launcher running, ADB connectivity with all the SDK stuff installed and safestrap. I must have done something wrong with safestrap because my backup didn't take, and when I tried to hide the nav bar I got stuck in a bootloop. I see the grey logo then a lighted black screen, but the kindle no longer connects.
dburns865 said:
I apologize if this has been asked before, but I have been searching around through dozens of threads over days and don't see much about people in a bootloop without ADB access. Is this an unsolvable problem or is there some way to reconnect to ADB so I can run a fix?
Just for background, I had a fully functioning towel rooted kindle 8.9 HDX which had the Google marketplace, OTC disabled, APEX launcher running, ADB connectivity with all the SDK stuff installed and safestrap. I must have done something wrong with safestrap because my backup didn't take, and when I tried to hide the nav bar I got stuck in a bootloop. I see the grey logo then a lighted black screen, but the kindle no longer connects.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2588608 Look a whole thread devoted to your problem .. I would suggest reading the whole thread and understanding as much as possible before you start issuing commands . Good luck ,and by the way this would not have happened if you were using a slot on your safestrap. If you were in fact using a slot. Just hold the power down for over 25 seconds. Then safestrap should boot whatever you do do not do a factory reset in stock recovery
jimyv said:
http://forum.xda-developers.com/showthread.php?t=2588608 Look a whole thread devoted to your problem .. I would suggest reading the whole thread and understanding as much as possible before you start issuing commands . Good luck ,and by the way this would not have happened if you were using a slot on your safestrap. If you were in fact using a slot. Just hold the power down for over 25 seconds. Then safestrap should boot whatever you do do not do a factory reset in stock recovery
Click to expand...
Click to collapse
Maybe I am confused about something, I had already read through that thread a few times and it seems like that assumes you have ADB access or a way to gain it which I do not have. Issuing any of the commands listed in that guide just gets me the same response, Error: Device not found. I saw one guy asking my question and GSLEON said to download the update.bin, but I am not really sure what to do with it and they didn't elaborate. In addition, the advice he gives him about it says the computer should fail to recognize my device but still acknowledge something was plugged in but that doesn't happen with mine. He also suggested trying in linux so that is what I am working on doing now but I have never used Linux so I will see how that goes.
I may just not be understanding something, I'd be in your debt if you'd elaborate on something I am not understanding but in any case sorry if I asked a dumb question. I appreciate you responding, it's good to know what I need is in that thread, I guess I just wasn't able to figure it out yet. I will try harder
So I just soft-bricked my Kindle Fire HDX 7. It does not boot any more but I still have ADB access.
I just tried to follow the steps as described here: http://forum.xda-developers.com/showpost.php?p=60307966&postcount=187
I successfully updated to 3.2.5 and now was about to downgrade to 3.1.0 when I used the .bat from this thread to apply the downgrade: http://forum.xda-developers.com/showpost.php?p=53382929&postcount=1
Even though I tried it several times, I could not downgrade because it said the requested version is lower than the one currently installed.
So le stupid me went on and found out which files the bat was generating/pushing on my HDX, and then manually replaced the /system/build.prop with the one generated by the batch.
I'm not doing this for the first time, so I made a backup of the old build.prop naming it build.prop.backup [afaik].
I then shut down the kindle (to go for a reboot) but apparently it doesn't work and the screen stays black.
Still, it seems like a pretty stupid move afterwards because otherwise it wouldn't cause a brick, right^^ Anyways, I unfortunately have no recovery installed atm.
I rooted the 3.2.5 with towelroot before btw...
However, if I try to copy/replace the build.prop backup it just can't find that file. I tried rebooting/pressing the power button but it doesn't help either.
Can anyone please help me to repair it -.-?
Edit: Turns out that I was accessing my blueStacks emulator with adb, which, even though it wasn't running at the time, caused the commands to not work.
The bluestacks service in windows was responsible for it. Charging the kindle atm and hope to be able to get adb :S
FINAL EDIT: So I messaged amazon Support, told them that it was bricked during an update and got a new kindle without any problems. Didn't mention the downgrade obviously^^
I followed this tutorial and was able to upgrade, downgrade, install TWRP and unlock my bootloader successfully: http://forum.xda-developers.com/showpost.php?p=60186871&postcount=82
For everyone: Just keep in mind that if you are running BlueStacks on your computer you will need to stop all bluestack services in order to make the tools work properly and not end up with a bricked device!
Otherwise some adb commands will fail because it doesn't know which device to use.
Tersus said:
So I just soft-bricked my Kindle Fire HDX 7. It does not boot any more but I still have ADB access.
I just tried to follow the steps as described here: http://forum.xda-developers.com/showpost.php?p=60307966&postcount=187
I successfully updated to 3.2.5 and now was about to downgrade to 3.1.0 when I used the .bat from this thread to apply the downgrade: http://forum.xda-developers.com/showpost.php?p=53382929&postcount=1
Even though I tried it several times, I could not downgrade because it said the requested version is lower than the one currently installed.
So le stupid me went on and found out which files the bat was generating/pushing on my HDX, and then manually replaced the /system/build.prop with the one generated by the batch.
I'm not doing this for the first time, so I made a backup of the old build.prop naming it build.prop.backup [afaik].
I then shut down the kindle (to go for a reboot) but apparently it doesn't work and the screen stays black.
Still, it seems like a pretty stupid move afterwards because otherwise it wouldn't cause a brick, right^^ Anyways, I unfortunately have no recovery installed atm.
I rooted the 3.2.5 with towelroot before btw...
However, if I try to copy/replace the build.prop backup it just can't find that file. I tried rebooting/pressing the power button but it doesn't help either.
Can anyone please help me to repair it -.-?
Edit: I might bricked it completely, because I can not gain w permissions on /system *__*
Click to expand...
Click to collapse
** NEVER MESS WITH BUILD.PROP **
(unless you are an expert and have robust recovery options)
Well, you had the right idea as the modified build.prop never made it to your Kindle which is why you were getting the version mismatch message. It saw 13.1.x was lower than 13.2.5 and bailed. The modified build.prop tricks your Kindle into thinking it is at 13.0.0 so processes the 13.1.x .bin as an upgrade.
None of that really matters as I'm guessing permissions are messed on one or more files that were copied to your device. Options are few if you can not gain write access (obviously bootloader remains locked). You can try a system restore from stock recovery (if working) which can be accessed by pressing the power and volume-up buttons simultaneously from a cold start. I don't hold out much hope that will fix your problem. Fastboot cables are ineffective.
There are several unbrick threads you may want to explore. I have no direct experience with a device in that condition so can't offer much guidance. Perhaps someone will jump in with a better answer ...
I just noticed that if I press power for about 20 secs I get the first boot screen.
But it never reaches the one with the golden kf logo...
I can get to the stock recovery, but a factory reset doesn't change it either.
Any way to get into fastboot from ADB?
Tersus said:
I just noticed that if I press power for about 20 secs I get the first boot screen.
But it never reaches the one with the golden kf logo...
I can get to the stock recovery, but a factory reset doesn't change it either.
Any way to get into fastboot from ADB?
Click to expand...
Click to collapse
After you shutdown your kindle, you can get into fastboot mode by holding "volume -" button while pressing shortly power button (2-3 sec) ... Unfortunately that will not help you, because fastboot mode on HDX tablets is only usable with unlocked bootloader...
I am watching several unbrick threads here over time, some people claims they do not need root for restoring system, some failed because of no root, hard to tell, what will work in your case, but from what you are describing, seems to me, that you are very close to permanent brick, sorry...
But I strongly suggest you, that you at least try this unbrick method or this one, maybe luck will be on your side...
if you somehow lost root access, try this: http://forum.xda-developers.com/showpost.php?p=57659692&postcount=2
Turns out that it was accessing my blueStacks emulator with adb, which, even though it wasn't running at the time, caused the commands to not work.
The bluestacks service in windows was responsible for it. Charging the kindle atm and hope to be able to get adb :S
I will try to get root and restore the build.prop backup, fix permissions and it should reboot... still need adb for it-.-
So I messaged amazon Support, told them that it was bricked during an update and got a new kindle without any problems. Didn't mention the downgrade obviously^^
I followed this tutorial and was able to upgrade, downgrade, install TWRP and unlock my bootloader successfully: http://forum.xda-developers.com/showpost.php?p=60186871&postcount=82
Big thanks to anyone who helped me! You can close this thread...