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
Related
Had my Prime 2 days, got it rooted.
After ICS install and camera update it worked for a while. Then it rebooted and it's stuck in a bootloop. I can't even power it off.
Yes, I've used the reset pinhole.
I've rebooted into Asus recovery but all I get is the "dead droid" screen. I'm assuming it's because I don't have my SD card in.
Any suggestions?
I'm thinking that if I can get my hands on the stock ICS zip direct from Asus I might be able to run that.
I suspect, from this thread that the issue might be that the Launcher has gotten corrupted.
Update:
Ran the battery till the unit shut off and didn't reboot.
Charged the battery for 4+ hours, unplugged it and tried to boot up. Same story, bootloop.
ADB sees my Prime and can issue commands.
Any suggestions? I'm getting desperate here.
Edit again: I can pull a logcat, any suggestions what I'm looking for? I'm not sure what subset of Linux commands are in Android, can I do a kill -9 if I identify a rogue process?
I'm pretty sure top won't work, and a lot of my Linux knowledge is pretty rusty.
Same here
I'm stuck in boot. I rooted it from zedo's instructions (that guy is a whoot!). Afterwards I installed "VM Heap Tool"(by martino), restarted the tab from the VM app and it got stuck in the boot screen.
I'm stuck and don't know what to do. I don't really know codes, so I'm pretty much up a creek without a paddle.
Any help would be MUCH appreciated!
Bumble-Bee has solved this issue for you on IRC but I figured we should post the solution to *your* specific problem here for others. Hopefully it helps them if they run into a simular issue.
With a boot loop try shutting down the tablet by holding power for 30 seconds. If it doesn't shut down then hold power for 30 seconds and after it vibrates hold power and volume down. This should get you into the recovery process.
The first thing to do in trying to resolve this issue (and what solved it for Col_kernel) was to do a data wipe using the recovery menu. Directions on how to perform this can be found here . this will solve the majority of bootloop issues.
The second thing to try to do is to perform a recovery using a signed zip from Asus. the ICS 9.4.2.11.1 is the latest one as of this thread and can be downloaded at the link provided there. Download that and place it on a microsd card. Load the card into your prime and boot into recovery and perform a recovery.
after that, start asking for help
I tried both solutions suggested and they didn't work for me, however I modified the services.jar in systems\framework. Looks like it tries to recover and then goes to an android on his back with an exclamation mark. I can't get adb to recognize my device either. I'm assuming my only options are to send it back to Asus or wait til I can flash at this point?
I should have said that I have already done the reset. Also, I cannot install anything on the tablet, since I cannot even access it. My PC won't even recognize it.
Update: I just spoke with Asus support. They said that if all these options are exhausted, I should return the tablet. That's what I'm going to do today. [good thing I have all my apps backed up. #TiBu!]
I had a dreaded boot loop issue a week or two ago..
I attempted to root the prime using Max Lee's one click using my MBP..
ADB failed to push SU up properly but the script kept running.
After waiting an eternity I bounced the tab to find it in eternal bounce mode and complaining of a corrupted launcher.
Luckily enough I was able to still detect the device and run ADB commands, so I was able to run the same root method (under windows this time) which worked a treat.
Had me really worried for a while, but got the device working again and rooted it (win win)
Anyway, it's interesting that a rogue file or an incomplete binary in the /system/bin folder (which shouldn't have been called by anything) was causing the boot loop!
wells79 said:
I had a dreaded boot loop issue a week or two ago..
I attempted to root the prime using Max Lee's one click using my MBP..
ADB failed to push SU up properly but the script kept running.
After waiting an eternity I bounced the tab to find it in eternal bounce mode and complaining of a corrupted launcher.
Luckily enough I was able to still detect the device and run ADB commands, so I was able to run the same root method (under windows this time) which worked a treat.
Had me really worried for a while, but got the device working again and rooted it (win win)
Anyway, it's interesting that a rogue file or an incomplete binary in the /system/bin folder (which shouldn't have been called by anything) was causing the boot loop!
Click to expand...
Click to collapse
Odd. I had the same issues. I started rooting mine on my mac, then finally moved to my pc. It rooted flawlessly on my pc.
So, I don't know if it was the root with a corrupted file, or the VM Heap Tool that I activated in it that caused it to get stuck in bootloop. But... I didn't restart the tablet until after the VM Heap Tool. In other words, it could have done the same thing without the VM Heap, I just wouldn't have known it, because I didn't restart it right after the root.
Make sense?
I rooted mah Prime (TY Viperboy and contributing dev's!) and finally installed Font Changer. After I selected the font I wanted, obviously I re-booted....and re-booted..and etc. My TFP won't get past the ASUS boot animation, the circle just keeps spinning and spinning. I tried wiping user data and still nothing. Does anyone have a similar experience or advice? I didn't change the density or anything else, just the font.
I also tried the reset button a few times just in case and still the same thing. Android Commander doesn't see it when I connect either, Windows tried to install drivers for it(which i've obviously already installed) and kept getting an error.
98 views...am I the only one who has used Font Changer on the TFP? Do any of you vets on here have an idea how I might be able to boot the device or at least completely revert it to all factory settings/apps? I apologize for having a one sided conversation, but I really would like to use mah Prime again. Thanks!
Sent from my SPH-M900 using XDA App
I use Font Changer and haven't had a problem yet.
Hmm...Well I opted to re-boot from Font Changer after I changed fonts. Did you do the same?
pappasquirrel said:
Hmm...Well I opted to re-boot from Font Changer after I changed fonts. Did you do the same?
Click to expand...
Click to collapse
Yes. I don't know what to tell you.
Anyone know if there is a file I could put on my sd card that the TFP would boot from, like how PG86IMG works w fastboot?
not sure, but i would suggest you to get the newest update from their site, then pop it on a micro sd, (or sd if you have the dock) and try holding power and vol up .... or maybe power vol down, dont remember..
now when you download the zip from asus site, make sure to unextract and copy the zip after you unextract. It's a zip in a zip.
Then try with the zip as its labeled, maybe it'll work or rename to update.zip.... that seems to be the norm on other devices.
good luck, i hope it works so we can have another solution for those that this happens to. Can't wait for unlocker tool, so we can get a recovery on this and if that ever happens we can just do a restore. good luck!
Good idea, thanks! I will give that a go and report back soon. I know I had this problem once or twice on my EVO3D and Moment, I would have to do something similar and try again. I'm hoping for good news to report
keep us updated, I am sort of in the same boat. Mine wont boot up after last firnware update and I have been searching to see if I can make it read the update file from SD
btw, try volume up with power, then hit volume down.... maybe it'll just do a recovery with the image it already has
damn i dont know if its volume up or down.... anyone ever tried this? i dont have my tab with me...to test
Its vol dwn+power for recovery. it will ask to press vol up within 5 sec to enter RCK, I've done that and "andy" just lays there on his back w an exclamation mark coming out of his chest.
If you wait, you get a screen with 10 seconds to select one of two options, User Data Wipe and linex cold boot. I've tried both with no avail. One more thing I found out is since my Prime just stays at the loading screen, everytime I hold power or reset button it would just reboot and hang there again. Aside from letting the battery die the only option I've found to shut down is hold vol up+power till it vibrates, keep em dwn for 2 more seconds and it will shut down.
Sent from my SPH-M900 using XDA App
Font Changer, now TFP won't boot.
My Asus Prime is in the same situation as yours. A rooted it and install Font Changer, after reboot my TFP won't get past the ASUS boot animation. I tryed all the things you do, but Android doesen´t start.
I install APX driver in Windows 7, and when i connect the USB cable, the device is reconized in Windows Device Manager, but a can not acess the tablet.
I don´t know a method the acess the Tablet from microSD, do you know ?
May be BOOTLOADER UNLOCK release from ASUS solve it.
Good luck for us.
Still nada. Windows will reconize that its plugged in, but I get a code 43 or code 10 and can't access the TFP in anyway (that I know of). I asked the same question over on Transformerforums.com and member leeshor has been really helpful. Most of the idea's I was given I had already tried or I could not get to work for my specific problem, but I'm sure that the info will be helpful for a lot of you guys. Here's a link to my thread, check leeshor's sig for some helpful tips. http://www.transformerforums.com/forum/transformer-prime-help/15428-font-changer-now-wont-boot.html
I'm still workin' on it and I'll post if I am able to make any progress, good luck!
Data wipe will definitely not work in this situation as it does nothing to the /System which is where the font's are stored. My best guess is that the font was changed but the permission was not correctly written, had this problem in the early days of my Desire HD.
The only solution that will work, is if you can get into an ADB shell and either put the original fonts back or change the permissions to the correct permissions.
Doktaphex said:
Data wipe will definitely not work in this situation as it does nothing to the /System which is where the font's are stored. My best guess is that the font was changed but the permission was not correctly written, had this problem in the early days of my Desire HD.
The only solution that will work, is if you can get into an ADB shell and either put the original fonts back or change the permissions to the correct permissions.
Click to expand...
Click to collapse
That's what I figured, I just can't get windows to recognize it. When I connect via USB and the device is off, windows sees it as an unknown device(obviously) and that the drivers are fine. After I power it up, windows will either recognize it as an MTP device and when I try to access the tab or re-install the drivers I get a code 10. Or it will still show up as an unknown device with an "!" giving me a code 43. Is there any other way I can gain root access?
It's been awhile (or seems so) and I still haven't had any success. Has anyone else made progress getting back to a usable device??
Ok, so before I send my prime in...do any of you smarty pants know (guess is fine) if this lil problem some of us are having will have a solution when ASUS unlocks the bootloader? Unless there is some kind of boot.zip err something that will load up from stock recovery, I don't think it will change anything. Thoughts? Advice? Bueller?? Thank you in advance
Sent from my SPH-M900 using XDA App
Unlock-bootloader.apk....I guess that answers my question to whether i'd be able to fix permissions from recovery :/ What am I not seeing? There has to be a way to get these Primes w no adb access and a stuck boot screen to fire up...?
Sent from my SPH-M900 using XDA App
Have you tried the blob file from SDcard trick. I believe you rename the update to EP201_SDUPDATE.zip and it should be able to run from the RCK. It has to be on a micro sdcard though otherwise it doesn't work apparently.
As outlined here:
http://forum.xda-developers.com/showpost.php?p=22743057&postcount=119
Ok first of all Im sticking this question in general android Q&A because there in no XDA Forum for this phone. It is a Straight Talk LG Optimus Q 55c, this is my girlfriends phone its basically an optimus p500/v with a sliding keyboard Overclocked too 800mhz. I own a virgin optimus V so I have a lot of experience with this platform but Im stumped maybe im just neglecting to see something, Im hoping "another set of eyes" will help turn on a light and get my girlfriends phone working again as she cant afford another :/!
So here is what Im dealing with. I had rooted the phone for her and installed clockwork mod recovery & fastboot. Since she got the thing its had problems freezing (probably because it stock overclocked), and occasionally pulls a random reset. She asked me If I could install another ROM on it to see if it may help make the phone more stable. I went a searching and found that the Optimus Q community is very small almost nothing and her only real choice was a port of the Area51 Rom. So Installed the rom.... A few days later she had told me her phone was mega slow now and acting up way more, so I told her I would flash back to stock.
I rebooted the phone and found to my surprise CWM and fastboot seemed to be gone... what the h*ll? Im assuming when I flashed AreaRom it installed the stock Recovery and removed fastboot, I cant figure out any reason why the stock recovery would be back on the phone. Anyways I didnt feel like flashing a new recovery at the time. Well 3 days go by and her phone crashes and gets stuck in a boot loop. So she went in to recovery and wiped it. The phone then went through the process of collecting e-mail and password, asking about backing up, then asking whether or not to turn the location services on. Once you hit next Android throws an exception and says setupwizard.apk failed to initialize or something along those line. So after that the launcher does not load only the task bar at the top. When rebooted the phone enters a boot loop againg until wiped.
So heres the deal I can use adb, but when I try to get into an adb shell the prompt says error: closed. I have been able to use adb to push and pull files that is all. I tried to push setupwizard.apk to the system/apps directory but of coures it needs to be remounted to read write and I dont have any shell access to do that. So basically adb sees the phone but the shell doesnt work, when i type adb root it reports adbd is running as root on the phone, so I guess the shell service just never loads.... I do have stock recovery but the problem with that is there is no update.zip files it will except I have tried a myraid of methods to sign an update.zip but every time I try to run the update the stock recovery says verification failed. Of course LG has no official updates for this phone using there signature that I can use.
So basically my phone works recovery works android starts but cant finish setting up and never starts the adb shell service. If anyone knows how I can push setupwizard to /system/app, get adbd to initialize, or sign a 3rd party rom and have the stock recovery use it I would be very gratefull! Maybe there is a way to get fastboot back on there or enabled or something? adb reboot-fastboot just reboots like normal. I am at the point where I going to take the phone apart to find a serial uart connection and pray I can get a shell that way!!
Ive looked into a few programs like kdz update and lgmdp but they dont seem to work with this phone and I cant get into any emergency mode, maybe Im doing it wrong this is the first ive heard of emergeny mode.
Alright. I need some advice one last time, I swear... after this I'm not going to try to do anything.
Phone worked quite well for 2 days. I was enjoying this rom quite a bit. I decided to change the DPI down to 560. I saw that some others in this thread had done so quite easily... so I used this app to change it. Made the change to 560, granted supersu permission and rebooted. Only problem is that... the phone has yet to turn back on. At the moment the only thing I can get it to do is give me a screen that shows a large white empty battery with a cable leading up to it and a hazard exclamation mark in the bottom right when I am trying to put it in download mode. I have tried on multiple computers to restore back to stock following these directions. The best that happens is my computer recognizes an unrecognized device. No luck.
I would love to change the buildprop back or anything, but not even adb recognizes the device.
Otherwise, nothing. I can't get into recovery. I can't get the phone to start at all. All black screen. I can't get any reaction out of it. Any advice would be helpful, I'm on hour two of this. I realize that this is most likely not a problem with the rom, but wanted to see if anyone else had an issue and has advice/let anyone else who's thinking of changing the DPI and shared my troubles reconsider.
Thanks again!
The empty the battery logo is because the phone is dead try charging it for like 30 mins. Also it seems that app you used is 3 years old so it does not support lollipop or even kitkat. After charging it try get it into recovery and restore a backup. If you don't have a backup try wiping your data and cache.
1619415 said:
The empty the battery logo is because the phone is dead try charging it for like 30 mins. Also it seems that app you used is 3 years old so it does not support lollipop or even kitkat. After charging it try get it into recovery and restore a backup. If you don't have a backup try wiping your data and cache.
Click to expand...
Click to collapse
Thanks for the reply!
That emblem only shows up when the battery is removed and I'm trying to put the phone in download mode. So it makes sense. Any other ideas? The battery that I'm using is about 80% full. I still can't find a way to recovery mode.
What other information can I provide to help you out?
Well when your in download mode it does not take any commands can you get the lg powered by android screen? Or just nothing happens? If nothing at all happenes it is most likly bricked. If it boots to the lg screen it is most likly soft bricked.
Bricked- Phone is dead and very very hard to fix if there is a fix
Soft Brick- No OS so you have to reinstall a rom could also be, because of apps.
1619415 said:
Well when your in download mode it does not take any commands can you get the lg powered by android screen? Or just nothing happens? If nothing at all happenes it is most likly bricked. If it boots to the lg screen it is most likly soft bricked.
Bricked- Phone is dead and very very hard to fix if there is a fix
Soft Brick- No OS so you have to reinstall a rom could also be, because of apps.
Click to expand...
Click to collapse
No screen. For anything (other than described).
This is exactly what I was afraid of, but my phone has always been odd. This dead battery screen has always shown up in download mode... even when my phone worked, I've never had the firmware update screen. Which has always been weird to me.
However, the only time my phone shows anything is with the dead battery screen. During such it will show up as an unrecognized device when attached to a computer, again... it's always done this. I was just curious if there was something else or a suggestion that someone more experienced then myself might have.
No that I read it, it sounds like there maybe a very slim chance of getting your device to work. If you mange to get some drivers for the unreconized device driver you maybe able to send adb and fastboot commands. I found this one tool (will limk below) that is call cydia impactor I found in one of rootjunky's toolkit files. I used this one function that was able to make drivers for my sony smartwatch 3 and phone. I will link for the direct download make sure to extract the zip. Inside of the zip you will find another zip called "Impactor_0.9.14.zip" make sure to extract it to it's own folder. If you want you can delete the first folder juat save the impactor folder. Then run the program called "Impactor" can connect your phone to the computer and click on the tab called "USB" then click the button called "Driver Scan". Follow any on screen instructions. It should now generate a driver for your phone if all went well and it will be reconized. Then you should be able to run adb reboot recovery or fastboot reboot-bootloader. The fact that your computer is even seeing the phone tells me that it has so hope of being fixed because your computer see's it. Your device might be in a bootloop of some sort. You may just have no os installed and it may have just glitched.
Download: http://rootjunkysdl.com/getdownload.php?file=Tegra Note 7/ADB root.zip (will immeditly download it)
Worst case scenario, you may try this, or at least read it for general info. I don't think you'll have to go this far though
http://forum.xda-developers.com/showthread.php?t=2582142
[FIX] NO Recovery mode, No download mode, after OTA on rooted LG G2
i changed my dpi once and it bootlooped on me. i was lucky enough to get into recovery and then i restored the data partition from an older nandroid.
i agree with 16. it does sound like the drivers may not be loaded up properly if your computer recognizes a device. have you tried the official lg drivers?
What system are you guys running?
Well, I've found out that for whatever reason... on my phone I have to take out the battery for a period of ~5-10 mins on any change DPI, system rom update, anything. Otherwise, my phone will not turn on. So if someone else find this, give it a try.
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...