Related
Hi,
I have a UK Nabi2 which I used Nabilab2 to install TWRP+root+google apps a while back. I needed to do the new two part OTA update, for warranty reasons, so went to install my original backup, but could not find it. I used Nabilab2full and did the stock install, which removed root and returned the device back to stock. (This also changed my nabi to a US version with no serial, FW 2.1.29. which I later found out). & at that point I still had TWRP.
I did the first two of three OTA updates (which worked), the third update crashed during install. I retried the OTA twice more but each time it crashed. The device lost TWRP after this.
Upon entering recovery with ON/Vol+ I now get <3e> recovery. Running the root.zip file from sd card fails (I assume as I am not in the correct mode or have a bad file?). The OTA updates I grabbed from the nabi wiki page (and the thread, see below) also fail.
My device does not show in fastboot. Adb sees it but when using the command, C:\adb reboot recovery, the Nabi reboots and goes to the dead android (pushing -/+ to get into) <3e> recovery, and adb at that point no longer sees the device. The nabi also disconnects once adb shell is executed. I can intsall .apk files via adb command but I still need root access to run TWRP backup manager. I can run the root.zip file via an apk installer, but when running SU it gives a message 'There is no superuser binary installed, and superSU cannot install it. This is a problem!' ...Is there another way can I install root and/or the recovery.img to the Nabi2?
(I have been following the thread here, http://forum.xda-developers.com/showthread.php?t=2041224&page=10, as well as several hours worth of reading various adb, <3e> recovery, lost root etc q&a's in other places but cannot find an answer, or it's assumed that the adb reboot recovery command is working, which mine appears not to be).
Any help or pointers in the right direction would be very appreciated.
Regards,
Smirnofred
Hi,
I have quite a similar issue with this. I flashed custom recovery and forced gapps, but now cannot flash original recovery to perform OTA update. Cannot boot into custom recovery at all.
Done a system restore so now i have lost the gapps that were pushed and cant get into recovery to flash them again :crying:
Thank you for the reply mate, sorry to hear you are in the same situation more or less.
Further reading over at Stack overflow help forums seems to lead me to believe the tablet is bricked. Loss of su/root privileges means no r/w access via adb to put the required files where they need to be, or install or TRWP.
I'm not giving up on this... well not yet. I have a ton of other work related things going on right now that I need to clear down so I can look into this a bit more seriously. I'm away till the 17th April but will check in here when I can. And, if I find a solution I will post it here.
smirnofred ;0)
smirnofred said:
Hi,
I have a UK Nabi2 which I used Nabilab2 to install TWRP+root+google apps a while back. I needed to do the new two part OTA update, for warranty reasons, so went to install my original backup, but could not find it. I used Nabilab2full and did the stock install, which removed root and returned the device back to stock. (This also changed my nabi to a US version with no serial, FW 2.1.29. which I later found out). & at that point I still had TWRP.
I did the first two of three OTA updates (which worked), the third update crashed during install. I retried the OTA twice more but each time it crashed. The device lost TWRP after this.
Upon entering recovery with ON/Vol+ I now get <3e> recovery. Running the root.zip file from sd card fails (I assume as I am not in the correct mode or have a bad file?). The OTA updates I grabbed from the nabi wiki page (and the thread, see below) also fail.
My device does not show in fastboot. Adb sees it but when using the command, C:\adb reboot recovery, the Nabi reboots and goes to the dead android (pushing -/+ to get into) <3e> recovery, and adb at that point no longer sees the device. The nabi also disconnects once adb shell is executed. I can intsall .apk files via adb command but I still need root access to run TWRP backup manager. I can run the root.zip file via an apk installer, but when running SU it gives a message 'There is no superuser binary installed, and superSU cannot install it. This is a problem!' ...Is there another way can I install root and/or the recovery.img to the Nabi2?
(I have been following the thread here, http://forum.xda-developers.com/showthread.php?t=2041224&page=10, as well as several hours worth of reading various adb, <3e> recovery, lost root etc q&a's in other places but cannot find an answer, or it's assumed that the adb reboot recovery command is working, which mine appears not to be).
Any help or pointers in the right direction would be very appreciated.
Regards,
Smirnofred
Click to expand...
Click to collapse
You need to select fastboot protocol in the menu after booting with pwr/vol buttons. Then install fastboot driver, then install TWRP. From that point the thread you linked will work.
scotia_rfc said:
Hi,
I have quite a similar issue with this. I flashed custom recovery and forced gapps, but now cannot flash original recovery to perform OTA update. Cannot boot into custom recovery at all.
Done a system restore so now i have lost the gapps that were pushed and cant get into recovery to flash them again :crying:
Click to expand...
Click to collapse
Doesn't matter if you flash the original recovery, you need to flash the original system. TWRP can do the OTA but it will fail because there are a couple of system files that were changed that fail SHA-1 checks. Don't know what version you are on or if it's a UK or US or Disney/Nick version.
aicjofs,
Thanks for the pointers! ...its most appreciated.
After checking, I do see the nabi in device manager when its in fastboot mode, but its not installed properly (it says 'Android device' but has a 'fastboot' icon with an exclamation mark under it) which would be the root of my issue I would have thought. I was certain the fastboot drivers were installed too, obviously I was wrong.
*EDIT*
Success!
I had java disabled. I also had issues with device manager switching from 'Android device' to 'Unknown device' intermittently.
I started fresh by uninstalling everything nabi/sdk/adb related. Re-installed java, sdk and adb drivers, in that order, which resulted in no conflicts or driver issues! Then when I put the nabi into 'fastboot protocol' the second menu then appeared (which it was not doing previously). I flashed the 2.3.3.0 TWRP recovery image.
Now I have some more reading to do about what image I need to put back onto the nabi.
Thank you.
*EDIT*
Thanks again.
Smirnofed.
smirnofred said:
aicjofs,
Thanks for the pointers! ...its most appreciated.
After checking, I do see the nabi in device manager when its in fastboot mode, but its not installed properly (it says 'Android device' but has a 'fastboot' icon with an exclamation mark under it) which would be the root of my issue I would have thought. I was certain the fastboot drivers were installed too, obviously I was wrong.
*EDIT*
Success!
I had java disabled. I also had issues with device manager switching from 'Android device' to 'Unknown device' intermittently.
I started fresh by uninstalling everything nabi/sdk/adb related. Re-installed java, sdk and adb drivers, in that order, which resulted in no conflicts or driver issues! Then when I put the nabi into 'fastboot protocol' the second menu then appeared (which it was not doing previously). I flashed the 2.3.3.0 TWRP recovery image.
Now I have some more reading to do about what image I need to put back onto the nabi.
Thank you.
*EDIT*
Thanks again.
Smirnofed.
Click to expand...
Click to collapse
Somewhere in that post you linked I put a pretty good procedure for getting a UK Nabi to the latest OS, hopefully you will be up and running in no time.
I'm there, finally. Using the link to the three part install you posted. http://forum.xda-developers.com/showthread.php?t=2041224&page=10 post #98
I'm now @ 2.2.2 (I think), 4.1jb, with 2.6.3.0 twrp recovery. First thing I did was make a full backup (once it was all working 100%).
I had a minor issue with SU trying to install repeatedly once I put the 2.2+ stock image (+modded ota), which sent the nabi back to <3e> recovery. But I just flashed it back to 2.6.3.0 with fastboot.
Many thanks ;0)
smirnofred said:
I'm there, finally. Using the link to the three part install you posted. http://forum.xda-developers.com/showthread.php?t=2041224&page=10 post #98
I'm now @ 2.2.2 (I think), 4.1jb, with 2.6.3.0 twrp recovery. First thing I did was make a full backup (once it was all working 100%).
I had a minor issue with SU trying to install repeatedly once I put the 2.2+ stock image (+modded ota), which sent the nabi back to <3e> recovery. But I just flashed it back to 2.6.3.0 with fastboot.
Many thanks ;0)
Click to expand...
Click to collapse
Hi Smirnofred, I have similiar issues to you, and i'm wondering of you can help. The 2.2 file from dropbox is no longer available, have you still got it? and would you kindly upload it somewhere for me if you have time. It would be much appreciated. :good:
James
Q&A for HDX Stock Images Pre-rooted, Updates Disabled
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
access hdx7 filesystem via pc...without adb enabled on device
ggow said:
Hi All,
Here you can find stock firmware for both thor and apollo devices which are safestrap flashable.
Please note the following:
- These updates do NOT flash a new kernel or recovery - only a new /system image
- Before flashing ensure you know which stock base/kernel/safestrap you have installed and choose the appropriate version for that stock base/kernel.
I will be uploading them as and when I have time.
Thor Images:
13.3.1.0
If you want to re-enable over the air updates then do the following:
- rename /system/etc/security/otacert.old to otacert.zip
- rename /system/app/com.amazon.dcp.old to com.amazon.dcp.apk
Click to expand...
Click to collapse
I've had like a million or so android devices, and successfully hacked them all with 0 bricks to date. i've been pounding on an hdx7 for the past 2 days and i'm stuck.
background:
started off with fw 13.3.2.6
towelrooted/safestrapped/google play etc
been trying to downgrade fw to 13.3.1.0
now i'm in a situation where i flashed the thor fw in the 1st post in the "HDX Stock Images PreRooted, Updates Disabled" thread via safestrap recovery (yes the stock rom...i know i know) and now after safestrap exits to the system, all i get is a black screen. the device is on though. prior to this attempted downgrade, i did a full wipe. i have a nandroid (twrp) stock backup i have successfully reverted to a couple times so far, but this backup is now only on my computer due to the factory reset.
how can i push this file to the device with a black screen, on which adb has not yet been enabled?
i'm also open to other suggestions.
i did create a new rom slot, but it has no os on it either...
thx in advance
andyhax0r said:
I've had like a million or so android devices, and successfully hacked them all with 0 bricks to date. i've been pounding on an hdx7 for the past 2 days and i'm stuck.
background:
started off with fw 13.3.2.6
towelrooted/safestrapped/google play etc
been trying to downgrade fw to 13.3.1.0
now i'm in a situation where i flashed the thor fw in the 1st post in the "HDX Stock Images PreRooted, Updates Disabled" thread via safestrap recovery (yes the stock rom...i know i know) and now after safestrap exits to the system, all i get is a black screen. the device is on though. prior to this attempted downgrade, i did a full wipe. i have a nandroid (twrp) stock backup i have successfully reverted to a couple times so far, but this backup is now only on my computer due to the factory reset.
how can i push this file to the device with a black screen, on which adb has not yet been enabled?
i'm also open to other suggestions.
i did create a new rom slot, but it has no os on it either...
thx in advance
Click to expand...
Click to collapse
Can you get into safestrap?
mr. softbricked
ggow said:
Can you get into safestrap?
Click to expand...
Click to collapse
Yes I can boot into safestrap, I have tried using the ADB sideload feature but when I try issuing ADB commands using ADB in the Android Studio installation directory, it's always 'device not found'.
I tried to use the Terminal Command feature, and it asks me what directory on the HDX I want to start in, and I pretty much called it a night at that point.
Right now I'm thinking I probably have to order a fastboot cable, but I'd be very interested in exploring other options.
Thanks
andyhax0r said:
Yes I can boot into safestrap, I have tried using the ADB sideload feature but when I try issuing ADB commands using ADB in the Android Studio installation directory, it's always 'device not found'.
I tried to use the Terminal Command feature, and it asks me what directory on the HDX I want to start in, and I pretty much called it a night at that point.
Right now I'm thinking I probably have to order a fastboot cable, but I'd be very interested in exploring other options.
Thanks
Click to expand...
Click to collapse
Fastboot cable won't do you any good, don't waste your money
If you are running on windows then install this: http://forum.xda-developers.com/showthread.php?t=2588979
If you are on linux (my preference), be sure you have started adb with admin privileges. ie:
adb kill-server
sudo adb start-server
That may hopefully help your adb woes.
I'll upload a 13.3.2.6.zip file which you can push to your device and flash via safestrap.
sweet
ggow said:
Fastboot cable won't do you any good, don't waste your money
If you are running on windows then install this: http://forum.xda-developers.com/showthread.php?t=2588979
If you are on linux (my preference), be sure you have started adb with admin privileges. ie:
adb kill-server
sudo adb start-server
That may hopefully help your adb woes.
I'll upload a 13.3.2.6.zip file which you can push to your device and flash via safestrap.
Click to expand...
Click to collapse
wow thanks! yes i'm using windows, i will go grab my beautiful brick at lunchtime and try the utility. i do have a 13.3.2.6 bin file from amazon and a 13.3.2.6 zip file i got got from one of the HDX threads here. but if you upload a zip i can try it.
just to be clear, this is what i plan to try (please redirect me if i'm misguided):
on device: start adb sideload safestrap tool. on pc: (cmd prompt-admin) adb start-server, try an adb sideload myfwfile.zip
i really appreciate the assistance, i will definitely post an update once i try the adb utility.
andyhax0r said:
wow thanks! yes i'm using windows, i will go grab my beautiful brick at lunchtime and try the utility. i do have a 13.3.2.6 bin file from amazon and a 13.3.2.6 zip file i got got from one of the HDX threads here. but if you upload a zip i can try it.
just to be clear, this is what i plan to try (please redirect me if i'm misguided):
on device: start adb sideload safestrap tool. on pc: (cmd prompt-admin) adb start-server, try an adb sideload myfwfile.zip
i really appreciate the assistance, i will definitely post an update once i try the adb utility.
Click to expand...
Click to collapse
Forget about the sideload feature of safestrap for this exercise...
For windows the instructions would be this:
1. Download the 13.3.2.6.zip (which is uploading at the moment)
2. Open command prompt
3. cd to the folder where you saved the zip file
4. Connect your kindle if you haven't already.
5. Make sure it shows up as an adb device in the device manager
6. Issue the command <adb devices> and ensure your device is listed in the response.
7. Issue the command <adb push 13.3.2.6.zip /sdcard> - this will take a bit of time complete
8. Then on safestrap select the Install option and find your zip in /sdcard and flash it.
9. Do a factory reset and reboot from safestrap and you should be good to go.
Will let you know when the file is up.
@andyhax0r
13.3.2.6.zip can be found here:
http://forum.xda-developers.com/showpost.php?p=56148362&postcount=1
Softbricked HDX 7 Update
ggow said:
@andyhax0r
13.3.2.6.zip can be found here:
http://forum.xda-developers.com/showpost.php?p=56148362&postcount=1
Click to expand...
Click to collapse
Been working on pushing the recovery file to the device any possible way I can find.
- I downloaded the exe that installs ADB + Fastboot (system-wide)
- I downloaded and have been using the HDX Toolkit + Kindle drivers
- Tried Android Studio's Kindle Fire SDK + drivers installed from official Amazon repo
- Tried on Windows 7 x64
- Tried on Windows 8 x64
- Tried on WIndows 10 x64 Tech Preview
...always the same result:
Shows up only as Kindle FIre HDX with yellow exclamation point under Other Devices in Device Manager, even if I uninstall & delete the drivers & driver directory then reinstall. Whenever I point Device Manager to the C:\Program Files (x86)\Amazon.com\Kindle Fire\Drivers directory to install for the ADB drivers, Device Manager responds with Windows was unable to install your Kindle Fire HDX. Windows could not find the driver software for your device.
Therefore, I can't issue ADB or Fastboot commands because I always get 'error deivce not detected' or 'waiting for device' since driver isn't installed.
It's maddening since I can get into SafeStrap recovery and fastboot on the device, it's in mint condition, and it's completely worthless unless I can somehow get just 1 file to the internal storage. Too bad all the hardware manufacturers 'motivate' consumers to buy a more expensive model with a higher storage capacity by not installing a MicroSD card slot.
I spent numerous hours the past few days researching, installing different versions of Windows, trying to access the device. I really don't know what else to do besides sell it for parts online.
andyhax0r said:
Been working on pushing the recovery file to the device any possible way I can find.
- I downloaded the exe that installs ADB + Fastboot (system-wide)
- I downloaded and have been using the HDX Toolkit + Kindle drivers
- Tried Android Studio's Kindle Fire SDK + drivers installed from official Amazon repo
- Tried on Windows 7 x64
- Tried on Windows 8 x64
- Tried on WIndows 10 x64 Tech Preview
...always the same result:
Shows up only as Kindle FIre HDX with yellow exclamation point under Other Devices in Device Manager, even if I uninstall & delete the drivers & driver directory then reinstall. Whenever I point Device Manager to the C:\Program Files (x86)\Amazon.com\Kindle Fire\Drivers directory to install for the ADB drivers, Device Manager responds with Windows was unable to install your Kindle Fire HDX. Windows could not find the driver software for your device.
Therefore, I can't issue ADB or Fastboot commands because I always get 'error deivce not detected' or 'waiting for device' since driver isn't installed.
It's maddening since I can get into SafeStrap recovery and fastboot on the device, it's in mint condition, and it's completely worthless unless I can somehow get just 1 file to the internal storage. Too bad all the hardware manufacturers 'motivate' consumers to buy a more expensive model with a higher storage capacity by not installing a MicroSD card slot.
I spent numerous hours the past few days researching, installing different versions of Windows, trying to access the device. I really don't know what else to do besides sell it for parts online.
Click to expand...
Click to collapse
1. On device manager Right click on the Kindle HDX device and select Uninstall.
2. Then do a a scan for devices from the device manager.
3. It will now show up as a device requiring a driver.
4. Now right click on it and select properties and press the button 'Update Driver'
5. Then select Browse my computer
6. Look for the Android devices category and select an adb driver to install
7. Windows will then moan that the driver isn't correct for the device - ignore this and select install anyway or whatever the option is to proceed.
8. When installed issue command <adb devices> to confirm it's working.
FINALLY!
ggow said:
1. On device manager Right click on the Kindle HDX device and select Uninstall.
2. Then do a a scan for devices from the device manager.
3. It will now show up as a device requiring a driver.
4. Now right click on it and select properties and press the button 'Update Driver'
5. Then select Browse my computer
6. Look for the Android devices category and select an adb driver to install
7. Windows will then moan that the driver isn't correct for the device - ignore this and select install anyway or whatever the option is to proceed.
8. When installed issue command <adb devices> to confirm it's working.
Click to expand...
Click to collapse
Wanted to give an update with solution:
After trying every possible way I could find to get either a system update file (.bin) or flashable .zip to my softbricked hdx, I was out of options. I had spent numerous hours researching, memorized most adb and fastboot commands, and even installed 3 different versions of Windows trying to get a working environment.
I figured I can revisit the issue later, maybe in 6 months or a year there will be a fix. I boxed up the hdx and put it away. I bought a Nexus 7 2013 to play with, it being my favorite tablet and the one I have found to be most hackable. Got the WugFresh toolkit to unlock and root it, custom Slim rom + mini gapps, Elementalx kernel, and updated Adreno drivers.
I noticed that when I connected the Nexus to my laptop, I couldn't see it in Windows Explorer, no matter what mode put it in (media file transfer, camera, charge, etc). I had already installed the USB driver.
Then it hit me...
The one thing that the hdx and the nexus have in common - the USB cable. Had been using an original Asus Nexus 7 2013 data cable from a Nexus I previously owned.
I immediately changed the cable and got the hdx out, connected it, was able to install the drivers and in adb mode, I pushed both a flashable zip of 13.3.2.6 and a .bin to the /sdcard directory. Booted the hdx, flashed the zip in SafeStrap, and once again I had a working device!
I created a new rom slot, and tried to flash 13.3.1.0 to it, but still got a black screen when it started up. At least I still had my new stock rom to boot to. For some reason, I have been unable to downgrade the firmware on this device. That's okay, because even though I couldn't install the custom rom i wanted to make the hdx into a pure tablet, at least the hdx didn't beat me. I softbricked it, then put in work to come back from it, and learned a lot in the process.
Thanks for all your help!
Hey.
This may be a stupid question, but can I use the pre rooted 13.3.2.6 to update my 13.3.1.0.(rooted) to the latest rootable Version? Or how Do i Do that?
I already disabled ota and installed xposed.
I have a fire hdx Apollo that had been properly up(down)graded and running fine with 2.01. For some reason (and my lack of understanding the correct versions of things) I thought it would be a good idea to install the Apollo update on my stock rom. This of course has now caused boot loops on my stock boot but not my 2.01 boot.
Would love to be able to restore the stock as I do use some of the fire's capabilities from time to time. Sadly I did not do a backup before the update (kicks self furiously).
I DO have a backup from before the upgrade/downgrade so maybe I could restore that then push through the upgrade steps again or something. I'm worried that I will bork my safestrap or do something worse based on my proclivity for damage and chaos.
E.
Cpasjuste said:
Hi @ggow !
I made a flashable zip of the 4.5.2 update for Thor which is compatible with the signing exploit (bootloader/fw flashing removed and modified bootimage with happened dt) as there was some demand.
I'm not sure i should again create a thread for this rom(s) as we may be easily lost. Maybe all our "stock/modified stocks" roms should be in the same thread. What do you think about this ? Here is the link in case : http://android.mydedibox.fr/hdx/update-kindle-13.4.5.2_user_452004120-twrp.zip
Note that i only renamed "otacert.zip" to "otacert.old" on this rom as the "dcp" apk name has changed and i don't remember how i fixed that ... so ota updates may still be enabled isnt it ?
---------- Post added at 03:21 PM ---------- Previous post was at 03:16 PM ----------
I don't know if it's the problem but the appolo recovery is based on an older kernel (3.1.0?) which doesn't have full selinux support. This prevented some zip to be properly flashed (at least on thor) until i use the 4.5.2 kernel sources. Unfortunately we will have to wait for @ggow to receive his new device, in the hope of an exploitable one (but this may be a different problem)
Edit : oups, you are on thor so it's not the problem !
Click to expand...
Click to collapse
Hello,
i found on android-hilfe.de forum which files must be renamed, for disabling ota, link:
/system/app/otaverifier.apk
/system/priv-app/devicesoftwareota.apk
But now i have an other problem, i can't use instant video anymore, i always get a LICENSE_ERROR, any idea, why?
Greets,
Marcel
Gesendet von meinem KFTHWI mit Tapatalk
...
But now i have an other problem, i can't use instant video anymore, i always get a LICENSE_ERROR, any idea, why?
Greets,
Marcel
Gesendet von meinem KFTHWI mit Tapatalk
Click to expand...
Click to collapse
I'm using Cpasjuste's 4.5.2 with those files renamed. I can still play Amazon instant videos without error. At first I renamed those files before the first boot and my kindle was acting weird. I wonder if it's related? May try rename those files back and play a video then immediately rename them again? Be extra careful though. There is a new 4.5.2 OS from Amazon already.
Okaaay, I tested it already and nothing, I can't play videos...
But I have an other thing ? I have a modified gapps zip, that fit for the rom ? I had to remove nearly everything out from it, only the libs, the sync apks and the market left, I will add the file to this post, when I uploaded it later.
Edit: Here is my gapps package:
https://docs.google.com/file/d/0Bw33k6BXtLiYcGdOVGk1VVBEcjg
please report if it works or not ??
Gesendet von meinem KFTHWI mit Tapatalk
Is this flashable from safestrap?I made a flashable zip of the 4.5.2 update for Thor which is compatible with the signing exploit (bootloader/fw flashing removed and modified bootimage with happened dt) as there was some demand.
Rom slot or Stock?
I tried flashing the 4.5.2 stock rom on a rom slot using safestrap and just got a black screen until it finally went back into recovery. I was wondering since it's a stock rom if I needed to flash it onto the stock slot. In that case, do I just flash it over what I have (3.2.8) or do I have to do a wipe? I'm currently using Nexus ROM but I enjoyed the new fire OS before I rolled back to get root back. Help appreciated!
The Rom you mentioned (4.5.2 from Cpasjuste) is for flashing with TWRP and not for safestrap.
TWRP is not working on 3.2.8
Oh for some reason I thought it was for safestrap and not twrp. Does anyone have a ROM like that for safestrap? Or is there a kernel issue or something?
Hello,
Recently I achieved root on my Fire via KingRoot on Fire OS 5.0.1. I disabled the Fire Launcher, and then I stupidly decided to remove KingUser and replace it with SuperSU with SuperSU-Me. Long story short, I rebooted the device when SuperSU finished updating the binaries, and I was greeted with a bricked Fire that would stay on the Fire screen but would not dim and do much else. I can get ADB access, but my Windows PC says that the device is unauthorized and my Linux box says that the device is offline. Any help? I am kind of lost as to what I can do. Thank you in advance
HyperNyan said:
Hello,
Recently I achieved root on my Fire via KingRoot on Fire OS 5.0.1. I disabled the Fire Launcher, and then I stupidly decided to remove KingUser and replace it with SuperSU with SuperSU-Me. Long story short, I rebooted the device when SuperSU finished updating the binaries, and I was greeted with a bricked Fire that would stay on the Fire screen but would not dim and do much else. I can get ADB access, but my Windows PC says that the device is unauthorized and my Linux box says that the device is offline. Any help? I am kind of lost as to what I can do. Thank you in advance
Click to expand...
Click to collapse
Can you get into recovery by holding Power and Volume-Up?
DoLooper said:
Can you get into recovery by holding Power and Volume-Up?
Click to expand...
Click to collapse
Yes, I indeed can get into recovery mode! There might be some hope for my tablet
HyperNyan said:
Yes, I indeed can get into recovery mode! There might be some hope for my tablet
Click to expand...
Click to collapse
Yes, indeed! You can sideload the latest Amazon update. It's 5.1.1. (AFAIK, the November 5.0.1 is not available.) Get the update here: http://kindle-fire-updates.s3.amazo...aZE/update-kindle-20.5.4.1_user_541113320.bin
In recovery, highlight the adb sideload option and press power to get into sideload mode. I don't know linux, but if using Windows install adb drivers. Now, from CMD window, type:
adb sideload <name of the update file>
The update will install and you should be able to boot. You can root with kingroot. After rooting, read/use @bibikalka's guide to reinstall 5.1.1 with SuperSU (to kill Kingroot) and to install Gapps.
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
DoLooper said:
Yes, indeed! You can sideload the latest Amazon update. It's 5.1.1. (AFAIK, the November 5.0.1 is not available.) Get the update here: http://kindle-fire-updates.s3.amazo...aZE/update-kindle-20.5.4.1_user_541113320.bin
In recovery, highlight the adb sideload option and press power to get into sideload mode. I don't know linux, but if using Windows install adb drivers. Now, from CMD window, type:
adb sideload <name of the update file>
The update will install and you should be able to boot. You can root with kingroot. After rooting, read/use @bibikalka's guide to reinstall 5.1.1 with SuperSU (to kill Kingroot) and to install Gapps.
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
Click to expand...
Click to collapse
Thank you! My Fire tablet is now able to boot and can run normally, but with root access this time Thank you for helping me through this issue
Update:
I tried to install TWRP without reading that it would not work on the newer Fire OS bootloader, and now I am stuck with no recovery. Attempting to boot into TWRP results in a black screen after the Amazon logo and then it reboots into the OS. I do have access to Android, but I cannot flash the stock recovery as I am currently without a recovery. Any pointers as to how I can possibly get the stock recovery again so then I can redo the whole process of attempting to install CM11?
You may be able to dd the recovery partition. Someone else will have to help with that.
HyperNyan said:
Update:
I tried to install TWRP without reading that it would not work on the newer Fire OS bootloader, and now I am stuck with no recovery. Attempting to boot into TWRP results in a black screen after the Amazon logo and then it reboots into the OS. I do have access to Android, but I cannot flash the stock recovery as I am currently without a recovery. Any pointers as to how I can possibly get the stock recovery again so then I can redo the whole process of attempting to install CM11?
Click to expand...
Click to collapse
Just do this, run the script provided :
http://forum.xda-developers.com/showpost.php?p=62011272&postcount=2
I'll get you TWRP and 4.5.3 bootloaders. Then flash 5.4.1 stuff from TWRP.
DoLooper said:
Yes, indeed! You can sideload the latest Amazon update. It's 5.1.1. (AFAIK, the November 5.0.1 is not available.) Get the update here: http://kindle-fire-updates.s3.amazo...aZE/update-kindle-20.5.4.1_user_541113320.bin
In recovery, highlight the adb sideload option and press power to get into sideload mode. I don't know linux, but if using Windows install adb drivers. Now, from CMD window, type:
adb sideload <name of the update file>
The update will install and you should be able to boot. You can root with kingroot. After rooting, read/use @bibikalka's guide to reinstall 5.1.1 with SuperSU (to kill Kingroot) and to install Gapps.
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
Click to expand...
Click to collapse
THANK YOU SO EFFING MUCH! I thought my HD6 was done. I was beginning to panic. I went through a LOT of guides to fix it and nothing worked except what you posted.
I know this thread is pretty old, but I haven't fixed the recovery issue yet due to being scared of bricking my tablet. So, just asking, which script do I run? Thanks!
HyperNyan said:
I know this thread is pretty old, but I haven't fixed the recovery issue yet due to being scared of bricking my tablet. So, just asking, which script do I run? Thanks!
Click to expand...
Click to collapse
The recommendations have not changed since the last time you asked Either install stock recovery via Flashify (dig out the recovery image from this zip : 5.2.0_stock_recovery_only.zip , here : http://forum.xda-developers.com/showpost.php?p=62011272 ), or run the script in post #2, and from TWRP, re-install 5.4.1 bootloaders :
http://forum.xda-developers.com/showpost.php?p=62011272&postcount=2
Thank you! My tablet is now working great, TWRP successfully installed. Just about a few minutes ago I had a panic attack when it started boot-looping, but then I shut it off for a while, and booted it into TWRP, and it was fine. Go figure I will now attempt to install cm11! Thank you for all of your help!
A while back, Amazon automatically pushed an update to my kid's Fire HD 6. Since then, the device will boot up and then it just freezes. The screen stays on the device is unresponsive. I am able to get in to recovery on the device, and that all seems to work fine, but booting in to Android is useless because it just locks and you cannot do anything with it.
I have been trying to go through this forum to see what my options are for sideloading another firmware or TWRP or anything like that.. and the posts here are not entirely helpful (for me at least). I'm used to going in to recovery and flashing some zip files to install TWRP, Cyanogenmod or GAPPS or anything like that... but the instructions I see for installing TWRP and the like do not seem to be the traditional methods. From what I think I am seeing, to install TWRP you need shell access to the tablet and then you can use dd to write TWRP to the correct storage space.
What are my options for doing things through recovery with adb? Or can I load an old firmware and then go from there? Any help is appreciated - would really love to get CM12 on this thing in the end if I could.
ganiman said:
A while back, Amazon automatically pushed an update to my kid's Fire HD 6. Since then, the device will boot up and then it just freezes. The screen stays on the device is unresponsive. I am able to get in to recovery on the device, and that all seems to work fine, but booting in to Android is useless because it just locks and you cannot do anything with it.
I have been trying to go through this forum to see what my options are for sideloading another firmware or TWRP or anything like that.. and the posts here are not entirely helpful (for me at least). I'm used to going in to recovery and flashing some zip files to install TWRP, Cyanogenmod or GAPPS or anything like that... but the instructions I see for installing TWRP and the like do not seem to be the traditional methods. From what I think I am seeing, to install TWRP you need shell access to the tablet and then you can use dd to write TWRP to the correct storage space.
What are my options for doing things through recovery with adb? Or can I load an old firmware and then go from there? Any help is appreciated - would really love to get CM12 on this thing in the end if I could.
Click to expand...
Click to collapse
Your understanding of TWRP is right. Basically, we dd the twrp image with OS 4.5.3 bootloaders (the only bootloaders that will boot unsigned recovery) and then before leaving TWRP flash back (almost) current bootloaders and recovery.
You should be able to adb-sideload the OS 5.1.2 update to fix the freeze. Was device rooted before it updated? Do you know what OS it was on? If you have adb access while device is frozen, run these commands for current OS info:
adb shell getprop ro.build.version.fireos
adb shell getprop ro.build.version.number
No CM12 available. Mostly-working CM11 is here: http://forum.xda-developers.com/fire-hd/orig-development/rom-cm-11-kindle-hd6-t3270138
BTW, I assume you tried wiping cache and/or factory reset in recovery. If not, I'd do that first.
Hi guys
I've tried everything, i bought this watch today and i was so hyped about it.
I tried to update it to 6.0.1 using adb on my mac.
The problem is when i do this command "adb reboot recovery" and then "adb devices" it shows no devices! (before entering recovery it actually shows the device in the list!
This is so wierd and there is absolutely no solution that worksfor me... anyone has any ideas?
Edit: The problem more clearly:
Ok guys so the problem was that my LG G Watch (square) for some unknown reason wasn't available in recovery mode through adb, that means when i would use the command "adb devices" in recovery mode, i would see the empty list without any devices, while anywhere outside the recovery (system, fastboot etc) i was able to communicate with the device. (Since i was so frustrated i didn't make it clear enough in the original post ) And my watch was on 4.4! ( :| )
The solution:
Ok, so the problem was the watch, because i tried a OS X (and a windows on the same mac) and 2 windows laptops, all with drivers installed (and done the "update driver..." stuff on all) and the problem still persisted.
This solution is for people whose device is not displayed while in the recovery mode in cmd/terminal.
This is what i did: (i didn't do this in the order because i literally tried every solution on the internet! but this is the order that i was finally able to solve the problem with.)
1. I downloaded this tool from this topic (go to the link, click on LG G Watch > G watch script tool > LG G Watch Restore Tools V9.8.zip)
2. Run this bat (i used a windows but it works on the mac too) 1 LG G Watch Tools for Windows.bat
3. Let it recognize the device
4. When the blue list comes up choose 4 ( you should be in bootloader)[cmd > adb reboot bootloader] when it's done, your device should be on 5.1.1.
5. Download this tool from this topic
6. In cmd/terminal type "adb reboot bootloader" then type "fastboot flash recovery [draggedfile] and drag the downloaded .img to the cmd and press enter.
7. Now you have installed a custom recovery called CWM
8. In cmd type "fastboot reboot" then after reboot "adb reboot recovery"
9. Now inside this tool swip down to "install ..." and swip (to right i guess) and stay here on the watch.
10. Now in cmd type "adb push -p [draggedfile] /sdcard/0/Download" and drag the 6.0.1 OTA update and press enter
11. Now the update is in your device as a zip file in this path : /sdcard/0/Download (it didn't work when i wanted to push it to "/sdcard" folder so i had to go deeper)
12. Now swip on install from sdcard and navigate to the path and choose the zip file.
13. Done! you have successfully updated your device without going into recovery mode!
Thank you very much @lfom for sticking to this topic and helping out in the process!
I just tried it with windows as well and ain't working... im so frustrated...
There's a guide in General section that you may want to read:
http://forum.xda-developers.com/g-watch/general/guide-how-to-fix-6-0-1-adb-bug-t3347122
Thank you very much for your response, but my watch is on 4.4w and i just want to update it because im not able to update it via the sysyem update function... So i guess that guide is no help to me
miladkalbasi said:
Thank you very much for your response, but my watch is on 4.4w and i just want to update it because im not able to update it via the sysyem update function... So i guess that guide is no help to me
Click to expand...
Click to collapse
So you are on 4.4 and want to update? What else? Rooted and custom recovery?
I think there's a tool to flash stock LG ROM, you may want to search for it. This tool may help too:
http://forum.xda-developers.com/g-watch/development/script-lg-g-watch-tool-t2820863
lfom said:
So you are on 4.4 and want to update?
Click to expand...
Click to collapse
Yes, i bought this watch yesterday and it's on 4.4 and i want to update to 6.0.1 (or any newer update)
lfom said:
What else?
Click to expand...
Click to collapse
I have never had developer experience with any android device before so i learned everything in like 6-7 hours, therefore there is a high probability that i might have made mistakes in the way but here's what i have done so far:
1. i tried to update the watch from "About" on the watch itself but kept getting "Something went wrong" error and couldn't fix it.
2. so i moved on to use my mac to do the update which took me 4-5 hours to figure out what SDK platform tools, ADB, OTA updates, bootloader, fastboot etc means.
3. i figured out all this and went on until i reached here: i have to use this commend in the terminal (it's like windows cmd): adb devices
so that i know my device is there and authorized on the companion android device (i see the device in the command shell), i then proceed to this command : adb reboot recovery , as soon as i type this command and press enter, the device reboots and enters recovery mode but it is also vanished from the system, by typing adb devices i no longer see it, i just see an empty list.
4. i also did unlock, wipe, restore back to stock ROMs (5.1.1 ROMS), tried TWRP (i then realized i can't do OTA updates with this tool)
5. i did all of these steps several times and always got the same results!
6. i also tried the windows on my mac and got the exact same results.
7. i tried 3 different windows laptops in the household (2 of which run win 8 and one runs win 7) but was not able to make it through installing the drivers (i couldn't see the android device when i clicked on update drivers...)
lfom said:
Rooted and custom recovery?
Click to expand...
Click to collapse
no i haven't rooted the device
lfom said:
I think there's a tool to flash stock LG ROM, you may want to search for it. This tool may help too:
http://forum.xda-developers.com/g-watch/development/script-lg-g-watch-tool-t2820863
Click to expand...
Click to collapse
Thank you very much for your suggestion, i have already tried that and it doesn't actually give me any more options that i already have.
I've come to the believe that it's either my laptop (which only has 2 USB 3.0 ports and some people say it causes issues) or my watch. I have to try to use a different computer but i don't think i can access more computers or solve the driver problem on the 3 existing ones.
I really wish i could solve this by myself, i live in a country that i can't access warranty and stuff so i either have to fix it myself or get a professional's help.
i found this topic as well, that's exactly my problem.
I can communicate with the watch in bootloader and TWRP but not in the recovery mode (stock)
Well, that thread has a tip about how to access watch in Recovery, it says it will be listed in Windows as an unlisted device, you have to install drivers for that...
It seems that 4.4w is too old so it won't get updated. But I remember reading another thread where the user was able to update it, probably using a full image of system or using TWRP.
If you can get to stock 5.1.1 I remember reading that if you install TWRP you can flash 6.0.1 zip, so maybe it's the best way to go. Also, probably you can force OTA on 5.1.1 (maybe any 5.x) if you do a watch reset while it's in cradle.
lfom said:
Well, that thread has a tip about how to access watch in Recovery, it says it will be listed in Windows as an unlisted device, you have to install drivers for that...
It seems that 4.4w is too old so it won't get updated. But I remember reading another thread where the user was able to update it, probably using a full image of system or using TWRP.
If you can get to stock 5.1.1 I remember reading that if you install TWRP you can flash 6.0.1 zip, so maybe it's the best way to go. Also, probably you can force OTA on 5.1.1 (maybe any 5.x) if you do a watch reset while it's in cradle.
Click to expand...
Click to collapse
Thanks for your response.
Do you mean i use boot, recovery, and system images to get to 5.1.1? i have already done this (through bootloader) and (i guess it's called the ROM?) it's on 5.1.1.
I used TWRP but when i try to use adb sideload and use the 6.0.1 zip file it gives me error saying it failed. (gives me this error on the mac : Total xfer: 0.00x , and "failed" on the watch)
I used CWM right now and it gives me the same results as the stock recovery (not being able to communicate when i enter recovery but when i go back to menu i can communicate with the device again!)
Is flashing the update more complicated that i think it is? i can't find a tutorial for TWRP and flashing an update...
O and about the last part that u added, i don't know how to force anything in that matter...
miladkalbasi said:
Thanks for your response.
Do you mean i use boot, recovery, and system images to get to 5.1.1? i have already done this (through bootloader) and (i guess it's called the ROM?) it's on 5.1.1.
I used TWRP but when i try to use adb sideload and use the 6.0.1 zip file it gives me error saying it failed. (gives me this error on the mac : Total xfer: 0.00x , and "failed" on the watch)
I used CWM right now and it gives me the same results as the stock recovery (not being able to communicate when i enter recovery but when i go back to menu i can communicate with the device again!)
Is flashing the update more complicated that i think it is? i can't find a tutorial for TWRP and flashing an update...
O and about the last part that u added, i don't know how to force anything in that matter...
Click to expand...
Click to collapse
ROM is basically kernel+system, what the device needs to run an operational system, but may include other files like boot and recovery.
As "to force an update", you don't need do to anything else but reset the watch while it's on cradle charging. It's a way to force the system to update to latest firmware, as checking in the About page does not work always if there is an actual update available. It's more like a trick. But I am not sure if it only works if watch is stock (all files from manufacturer's ROM). If I remember correctly, as it's possible to flash 6.0.1 update directly from TWRP then maybe OTA also works with TWRP (I can't verify as my LG G Watch W100 is all stock).
As for adb, probably only custom recovery (TWRP is the most common) supports adb, stock recovery probably not. Anyway, this thread is about rooting with a working TWRP (it says the official one has a bug with 6.0.1) maybe it's what you need:
http://forum.xda-developers.com/g-watch/development/guide-how-to-root-lg-g-watch-6-0-1-t3320512
Oh, and by the way, you can push files to /sdcard before booting to TWRP, it won't be erased unless you factory reset the watch or use recovery to wipe data partition, the same way it works on phone.
lfom said:
ROM is basically kernel+system, what the device needs to run an operational system, but may include other files like boot and recovery.
As "to force an update", you don't need do to anything else but reset the watch while it's on cradle charging. It's a way to force the system to update to latest firmware, as checking in the About page does not work always if there is an actual update available. It's more like a trick. But I am not sure if it only works if watch is stock (all files from manufacturer's ROM). If I remember correctly, as it's possible to flash 6.0.1 update directly from TWRP then maybe OTA also works with TWRP (I can't verify as my LG G Watch W100 is all stock).
As for adb, probably only custom recovery (TWRP is the most common) supports adb, stock recovery probably not. Anyway, this thread is about rooting with a working TWRP (it says the official one has a bug with 6.0.1) maybe it's what you need:
http://forum.xda-developers.com/g-watch/development/guide-how-to-root-lg-g-watch-6-0-1-t3320512
Oh, and by the way, you can push files to /sdcard before booting to TWRP, it won't be erased unless you factory reset the watch or use recovery to wipe data partition, the same way it works on phone.
Click to expand...
Click to collapse
I solved the problem!
Funny thing is i didn’t see your answer and fixed it by myself but you actually proposed exactly what i had to do! Thank you very much for your effort and spending your time on this topic!
For others who might run into the same problem in the future I'm gonna update the first post and say what i did.
Cheers!