I decided to revive my old tablet so I updated it using the official updater (one by one). The problem is that during the updates, the tablet rebooted by itself... I managed to install every single update and now it's acting weird, it keeps rebooting by itself and I can feel something's wrong.
I installed TWRP, had some trouble cause the guide says i gotta use `adb shell su -c 'command'` but it's not rooted (no su binary anywhere) but the guide says no root required: Fastboot Install Method (No Root Required, Fastboot Cable Required). Anyways, I ended up using the TWRP terminal to manually run the commands, found out a typo in the block device path but in the end I managed to dump the images.
I also noticed that after some seconds (or taps) TWRP touch capability becomes unusable, I have to touch many times for it to work, the buttons get pressed... It's like TWRP (or the tablet) doesn't refresh the display...
Can some with the same model (3rd gen soho) confirm if this is happening to you too, or is my tablet somehow ****ed up?
Thanks in advance!
ChazyTheBest said:
I decided to revive my old tablet so I updated it using the official updater (one by one). The problem is that during the updates, the tablet rebooted by itself... I managed to install every single update and now it's acting weird, it keeps rebooting by itself and I can feel something's wrong.
I installed TWRP, had some trouble cause the guide says i gotta use `adb shell su -c 'command'` but it's not rooted (no su binary anywhere) but the guide says no root required: Fastboot Install Method (No Root Required, Fastboot Cable Required). Anyways, I ended up using the TWRP terminal to manually run the commands, found out a typo in the block device path but in the end I managed to dump the images.
I also noticed that after some seconds (or taps) TWRP touch capability becomes unusable, I have to touch many times for it to work, the buttons get pressed... It's like TWRP (or the tablet) doesn't refresh the display...
Can some with the same model (3rd gen soho) confirm if this is happening to you too, or is my tablet somehow ****ed up?
Thanks in advance!
Click to expand...
Click to collapse
Unfortunately, this forum is for 5th and 7th gen devices; not sure if a dedicated forum exists for 3rd gen soho.
@sd_shadow?
ChazyTheBest said:
I decided to revive my old tablet so I updated it using the official updater (one by one). The problem is that during the updates, the tablet rebooted by itself... I managed to install every single update and now it's acting weird, it keeps rebooting by itself and I can feel something's wrong.
I installed TWRP, had some trouble cause the guide says i gotta use `adb shell su -c 'command'` but it's not rooted (no su binary anywhere) but the guide says no root required: Fastboot Install Method (No Root Required, Fastboot Cable Required). Anyways, I ended up using the TWRP terminal to manually run the commands, found out a typo in the block device path but in the end I managed to dump the images.
I also noticed that after some seconds (or taps) TWRP touch capability becomes unusable, I have to touch many times for it to work, the buttons get pressed... It's like TWRP (or the tablet) doesn't refresh the display...
Can some with the same model (3rd gen soho) confirm if this is happening to you too, or is my tablet somehow ****ed up?
Thanks in advance!
Click to expand...
Click to collapse
see http://forum.xda-developers.com/showthread.php?t=3206681 for relevent info
Davey126 said:
Unfortunately, this forum is for 5th and 7th gen devices; not sure if a dedicated forum exists for 3rd gen soho.
@sd_shadow?
Click to expand...
Click to collapse
sd_shadow said:
see http://forum.xda-developers.com/showthread.php?t=3206681 for relevent info
Click to expand...
Click to collapse
Thanks both of you, I'll copy paste my question there.
Related
HI,
I am sorry to bother the xdadevelopers community but I have tried to root the KIndle Fire HD 7" I offered to my mom for her birthday a week ago and i can't work around a problem :'(
I successfully installed Team Win Recovery Project. But anytime I boot i get into recovey (even when not pressing any button).
I hace searched the web for the last 3 days but any of the solutions have worked so far:
- I have tried to use adb shell "idme bootmode 4000" buti get /sbin/sh: idme not found
- I have tried adb shell nbmode but with the same result
- The rest of the solutions were for linux users.
So the question is ... what to do from here ?
Thank you very very much for any sugestion
Greetings from Bordeaux, France
Aaron Belle
Well, if you can get into recovery, that's a good thing.
I had this problem a couple of days ago. I had tried to revert from Chameleon OS back to the stock OS by flashing Haschode's stock OS zip, which resulted in the issue you described. I fixed it by restoring from a back up of ChaOS o had made, and it got me out of TWRP.
You could try re-flashing Hashcode's stock OS (it comes pre-rooted). It can be found here: http://forum.xda-developers.com/showthread.php?t=2218475
To move it on to your SD card, go to "Advanced" in TWRP and select "ADB Sideload," or something to that effect. Then from your PC, use a command window and enter "adb sideload name\of\zip.zip"
I don't remember if you have to wipe anything or not before you flash it
Hope this helped
>>Sent from my homebuilt TARDIS running Android 4.3... Or maybe it's a rooted Kindle Fire HD running ChameleonOS
Aaron Belle said:
HI,
I am sorry to bother the xdadevelopers community but I have tried to root the KIndle Fire HD 7" I offered to my mom for her birthday a week ago and i can't work around a problem :'(
I successfully installed Team Win Recovery Project. But anytime I boot i get into recovey (even when not pressing any button).
I hace searched the web for the last 3 days but any of the solutions have worked so far:
- I have tried to use adb shell "idme bootmode 4000" buti get /sbin/sh: idme not found
- I have tried adb shell nbmode but with the same result
- The rest of the solutions were for linux users.
So the question is ... what to do from here ?
Thank you very very much for any sugestion
Greetings from Bordeaux, France
Aaron Belle
Click to expand...
Click to collapse
Lol same thing happened to me when I flashed TWRP and 2nd BL. So basically, your in a boot loop. Don't worry you didn't do anything wrong, its just that the stock Kindle OS now hates us because we modified something. So here's what's gonna need to be done. You have TWRP, your all set to flash anything you want! But, you have no custom rom in there correct? My same mistake. Those are all easy fixes, the problem is playing with the KFHD7 drivers on your computer to detect your device 100% while its connected and on TWRP. I can't remember how I got mine to detect it, if I'm not mistaking I unisntalled ALL associated drivers, then reinstalled the ones provided for the rooting process WITH THE DEVICE STILL CONNECTED, then manually updating the driver to those installed drivers in C:/Program Files/Amazon/Kindle Fire. Once its installed, you would need to check by opening a command prompt with ADB, then check for devices by typing "ADB getdevices" if I'm not mistaking and see if some serial numbers show up. Then push the files thru ADB. If you wanna cheat your way thru ADB cause you don't know how to use it properly, do what I used to do. Download the Nexus 7 toolkit, install it, go to the folder where installed and create a shortcut for "tkmain.exe" to your desktop. Then open that and a green text command looking menu is in your view. If serials appear on the top, device is detected thru TWRP. If not keep playing with installing the drivers while in TWRP and refresh the green menu by using option 27 (type 27, then hit enter). Once those serials show up, download the custom ROM you want your mom to have. I recommend CM10.1 as its a small file, stabler than CM10.2, and its basically jellybean. Remember the folder where the Nexus 7 Toolkit was installed, where I first mentioned to make a shortcut for tkmain? Go back to that folder and look for a folder called "put files to push here". Throw the ROM there. Rename the ROM something short and with few or no symbols. When that's done, your ready to push it. Go to the wonderful green menu thingy, type 13 and hit enter. Then it will have two options. Type 2, hit enter. It will ask if your using an insecure bla bla bla. Type yes, hit enter. Then it should show the name of the ROM you threw in the folder, type it out exactly as spelled, hit enter. Push to /sdcard/. Some crap will appear and say "remount failed: Success" ignore that, don't panic, that's good. For a while nothing will show, but afterwards words should appear confirming the push, and Two last questions your gonna type no to. Now your ready to bring moms new device back to life! If you know how to flash a rom, do it. If not, swipe to wipe dalvik cache in Wipe menu, go back, Install > search SD card for your file and flash. Tada! You should see CM logo after the blue Kindle Fire logo and wait til the screen dims more or less, that means your a few seconds away from getting to touch. Remember to start it up, then flash GAPPS so mom can have Google Play, I'm sure she's gonna love Candy Crush Saga as mine does.
Sent from my Amazon Kindle Fire HD using xda app-developers app
May uestnl
Hi,
I have the same problem as AAron Belle, I think:
I followed the
"[REF] Installing Kindle Fire HD 7" 2nd-Bootloader + TWRP Complete Tutorial" till step 3.
I wanted to stop at step3 after installing 2nd bootloader and TWRP, without installing any custom ROMS.
I succeeded in the sense I don't have any red screen and the Kindle Fire HD 7 boots in TWRP (Screen Kindle fire in orange, then in blue, then TWRP).
But I can't find a way to boot anymore in the stock system (amazon).
I try to use a factory cable, but without success.
I would like to keep the 2nd bootloader and TWRP that I just installed, and as a first step use them in the amazon environnment.
Is there something I can do (not too complicated, I'm a noob!) ?
Thank you in advance,
Jeanphi
You can use "adb sideload" or "adb push" from a command prompt while plugged into your kindle in twrp and put a new ROM on it, like stock amazon, kinology, cm 10.1 or 10.2, etc.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
jeanphi506 said:
Hi,
I have the same problem as AAron Belle, I think:
I followed the
"[REF] Installing Kindle Fire HD 7" 2nd-Bootloader + TWRP Complete Tutorial" till step 3.
I wanted to stop at step3 after installing 2nd bootloader and TWRP, without installing any custom ROMS.
I succeeded in the sense I don't have any red screen and the Kindle Fire HD 7 boots in TWRP (Screen Kindle fire in orange, then in blue, then TWRP).
But I can't find a way to boot anymore in the stock system (amazon).
I try to use a factory cable, but without success.
I would like to keep the 2nd bootloader and TWRP that I just installed, and as a first step use them in the amazon environnment.
Is there something I can do (not too complicated, I'm a noob!) ?
Thank you in advance,
Jeanphi
Click to expand...
Click to collapse
Try the solution I mentioned above you. I'm no rocket scientist, or an android expert, just picked up a thing or two from experience. If I can do it you can as well. That's why I mentioned the toolkit I used. It may be for the Nexus 7 but it does the same adb commands used for all androids for you. That way if your not an adb expert you can use that. As I said, your first goal is to get your computer to properly detect the device while in TWRP, your stock kindle OS is just doing what it does best when simple modifications are done.
Lost access to stock amazon
stunts513 said:
You can use "adb sideload" or "adb push" from a command prompt while plugged into your kindle in twrp and put a new ROM on it, like stock amazon, kinology, cm 10.1 or 10.2, etc.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Thank you for the answer.
If I put a new ROM containing stock amazon, will I have still on the Kindle the 2nd bootloader and TWRP ?
Will my Kindle still be rooted ?
Jeanphi
jeanphi506 said:
Thank you for the answer.
If I put a new ROM containing stock amazon, will I have still on the Kindle the 2nd bootloader and TWRP ?
Will my Kindle still be rooted ?
Jeanphi
Click to expand...
Click to collapse
Depends on if the stock ROM is rooted, although usually, the answer is yes since messing around with things like overclocking and so on is always one of the reasons people seek to achieve root. If your going to flash this stock ROM, obviously only possible thru TWRP so yes you'll still have TWRP + 2nd BL. If your going to do the headachey fastboot restore, (not recommended at this point) then no. I've never gotten ADB sideload working, but either way I prefer pushing a rom to the internal SD and just installing.
How to get to the original OS after installing TWRP.
Crossvxm said:
Depends on if the stock ROM is rooted, although usually, the answer is yes since messing around with things like overclocking and so on is always one of the reasons people seek to achieve root. If your going to flash this stock ROM, obviously only possible thru TWRP so yes you'll still have TWRP + 2nd BL. If your going to do the headachey fastboot restore, (not recommended at this point) then no. I've never gotten ADB sideload working, but either way I prefer pushing a rom to the internal SD and just installing.
Click to expand...
Click to collapse
Thank you for answers. I think I will my first attempt to flash a Rom, through TWRP.
I will use this following link from Hashcode
"This flash .zip file contains the Amazon OS 7.4.3 update + root/Superuser.apk and should have OTAs disabled. You can use this to revert back to the Amazon OS should you need to for any reason.
Download Information for OS 7.4.3:
http://goo.im/devs/Hashcode/tate/kfh...n-os-7.4.3.zip
md5sum: 45e687e8e85975348f81f5cbfc8358ac"
Nevertheless, before doing that I might try to understand and use your first answer, as my Amazon 7.4.6 must still be on the system and this is just a question of access to it.
Jeanphi
jeanphi506 said:
Thank you for answers. I think I will my first attempt to flash a Rom, through TWRP.
I will use this following link from Hashcode
"This flash .zip file contains the Amazon OS 7.4.3 update + root/Superuser.apk and should have OTAs disabled. You can use this to revert back to the Amazon OS should you need to for any reason.
Download Information for OS 7.4.3:
http://goo.im/devs/Hashcode/tate/kfh...n-os-7.4.3.zip
md5sum: 45e687e8e85975348f81f5cbfc8358ac"
Nevertheless, before doing that I might try to understand and use your first answer, as my Amazon 7.4.6 must still be on the system and this is just a question of access to it.
Jeanphi
Click to expand...
Click to collapse
Once you flash any, there is no recovering the last stock you had, in this case, 7.4.6. This is lost for all of us. Now I haven't yet researched if there is a way to completely revert back to stock (as in removing the TWRP, 2nd boot loader and any other mods), but if there were, that's the way to go back to 7.4.6. However, no matter what ROM you toss on your device, any objects you may have had saved to your SD are still found as long as you don't delete em thru twrp. Remember before tossing in a rom, in the Wipe section, just swipe to factory reset, then go back and Install the zip from your storage.
Reinstalling stock OS
Crossvxm said:
Once you flash any, there is no recovering the last stock you had, in this case, 7.4.6. This is lost for all of us. Now I haven't yet researched if there is a way to completely revert back to stock (as in removing the TWRP, 2nd boot loader and any other mods), but if there were, that's the way to go back to 7.4.6. However, no matter what ROM you toss on your device, any objects you may have had saved to your SD are still found as long as you don't delete em thru twrp. Remember before tossing in a rom, in the Wipe section, just swipe to factory reset, then go back and Install the zip from your storage.
Click to expand...
Click to collapse
Coming back to give you some news.
I was not able to use the following link, as it was not on my Kindle and I was not able to have the kindle recognized by the computer.
"This flash .zip file contains the Amazon OS 7.4.3 update + root/Superuser.apk and should have OTAs disabled. You can use this to revert back to the Amazon OS should you need to for any reason."
I decided to use he backup I made and I used the following command, with the factory cable:
fastboot -i 0x1949 flash boot stock-boot.img
fastboot -i 0x1949 flash recovery stock-recovery.img
fastboot -i 0x1949 flash system stock-system.img
fastboot -i 0x1949 reboot
It worked and I have a working device, but without TWRP, 2nd boot loader.
I suppose I could have flashed directly the Amazon OS System mentionned earlier, but I was not exactly sure which command to use.
So, I will to try again to install TWRP, 2nd bootloader.
Thank you very much for your help. I will read again your answers to try to use them in the future.
Jeanphi
Completely fixed! Thanks!!
Download the Nexus 7 toolkit said:
I cant tell you how much of a life saver this was....this works 100% !! Just follow his instructions to a tee and this will save a lot of time and effort trying to get our TWRP loop!
Click to expand...
Click to collapse
OK, here's the thing...
I hadn't used my Kindle Fire HD for a few days but when I went to read a book (Yep.. Someone who actually uses their KFHD to read books!) I found, much to my disappointment that Amazon had managed to completely wipe it by doing one of their (in)famous OTA updates!
Being totally hacked off at this, I decided to follow the advice on here and Rooted it, which was surprisingly easy and went without a hitch.
I also decided to follow the advice and prevent further OTA updates by removing the "otacerts.zip" file but, on restart I still got an "Updating..." message.
In the same folder as otacerts.zip there was also an "otacerts" folder, which I also removed and this stopped the "Updating...." message.
Excellent, I thought except when I went to Re-Register the device, I get a "No Network Connection" error message which requests that I connect to a wireless network - except that the device IS connected and I can browse the internet quite happily.
Everything I have tried since then has failed to get rid of this error - even multiple Factory Resets have not cured it - and an hour chatting to one of their Tech Bods couldn't resolve it either.
I have tried downloading the latest update from Amazon but, as it is the same version as on my device, it does nothing.
I thought if I re-instated the otacerts stuff it might cure the problem - except during the many updates it seems to have been dumped as I can no longer find the files on my device.
I guess the bottom line is that I don't have to register with Amazon to get my device working, I have purchased a number of items from them and these will not reinstall if I cannot register the device.
So, here's my question: Can anyone help me please?
If you have a local copy of otacerts.zip that you can let me have (I have scoured Google trying to find a downloadable without success), I can try re-installing that and see if it corrects the error.
Failing that, does anyone know how to force a KFHD to do an "update" to the same software version - or can the software be rolled back and then re-updated?
Any help/advice/suggestions would be gratefully received.
Many thanks in advance.
Just restore a older system image from kindle fire first aid, that should do the trick, it will even put it into fastboot for you so it can do this, though I can't seem to remember if it tries to do it via adb or fastboot itself, so if it doesn't want to boot into fastboot via the default way in the script u have to simply use adb and run: adb shell "su -c 'reboot bootloader'". Sorry if that was a bit of excess info, just covering my bases. You also may need the driver in my signature once its in fastboot, but I'm leaning towards probably not since the USB debugging was previously on so you already have adb drivers installed.
On another note should something bizarre happen and you get stuck in a bootloop from this, you'll need a fastboot cable to get back into fastboot to fix.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Thanks.
stunts513 said:
Just restore a older system image from kindle fire first aid, that should do the trick, it will even put it into fastboot for you so it can do this, though I can't seem to remember if it tries to do it via adb or fastboot itself, so if it doesn't want to boot into fastboot via the default way in the script u have to simply use adb and run: adb shell "su -c 'reboot bootloader'". Sorry if that was a bit of excess info, just covering my bases. You also may need the driver in my signature once its in fastboot, but I'm leaning towards probably not since the USB debugging was previously on so you already have adb drivers installed.
On another note should something bizarre happen and you get stuck in a bootloop from this, you'll need a fastboot cable to get back into fastboot to fix.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Many thanks for the quick reply.
I'll grab KF First Aid and see what I can do.
Any recomms about where to grab older system images?
Ta.
Update - ALL DONE!!
stunts513 said:
Just restore a older system image from kindle fire first aid, that should do the trick, it will even put it into fastboot for you so it can do this, though I can't seem to remember if it tries to do it via adb or fastboot itself, so if it doesn't want to boot into fastboot via the default way in the script u have to simply use adb and run: adb shell "su -c 'reboot bootloader'". Sorry if that was a bit of excess info, just covering my bases. You also may need the driver in my signature once its in fastboot, but I'm leaning towards probably not since the USB debugging was previously on so you already have adb drivers installed.
On another note should something bizarre happen and you get stuck in a bootloop from this, you'll need a fastboot cable to get back into fastboot to fix.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
BIG THANKS!!
It took a while to figure out and work through but I now have a fully rooted, fully working, fully registered KFHD, complete with Google Play and Live Wallpapers!!
Now, all that's left is to re-install all the stuff I lost....
Wish me luck!
Thanks again for your guidance - much appreciated!
Hello,
I've been left with my cousins Kindle Fire HD 7" 16GB (Kindle 7) to fix.
The status bar is permanently missing, including when booting to safe mode.
Other things to note:
Internal storage is accessible via usb
ADB is turned off on the device
Device is stock in every respect
Fastbook boots fine: "product: Tate-PVT-08"
I'm unable to see what firmware version is on the device as I'm unable to view it's settings menu
I have good experience of rooting devices etc. I've put CM11 on multiple phones and also a Kindle Fire 2. Ideally I would like to reset the device to factory defaults to solve the issue, and if not then flash a stock ROM.
If this is possible then please let me know. If you point me to recent tutorials that would be great. Also the ability to re-lock the bootloader, or leave the device in a working stock state would be a huge bonus.
Many thanks!
David
EDIT:
I've done a fastboot wipe but the issue is still present.
Seems like I need to flash a stock image after unlocking the bootloader and installing a recovery. Is this possible without ADB ?
I believe you need ADB to apply the stack override?
Can you enable adb via fastboot or another means?
Cheers
I had the same issue but only after rooting. After I Uninstalled Gmail the problem disappeared And status bar came back as normal
aevans0001 said:
I had the same issue but only after rooting. After I Uninstalled Gmail the problem disappeared And status bar came back as normal
Click to expand...
Click to collapse
I'm afraid in my case the device isn't rooted, and has not had any apps side-loaded etc.
Make a fast boot cable install os again, profit.
Sent from my GT-P3110 using XDA Free mobile app
mrkhigh said:
Make a fast boot cable install os again, profit.
Sent from my GT-P3110 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the reply,
To install the OS again will I not need a second boot-loader? Or does the stock boot-loader allow the installation of a stock OS?
If a 2nd boot-loader is needed, then adb is needed to apply the stack override as part of the second boot-loader installation process.
Since you don't have adb enabled you need to go back to stock to enable it. Luckily there are tools to do this in fast boot. But first you need a fast boot cable and drivers
Here is how to make one, or just buy one on eBay or Amazon
http://forum.xda-developers.com/showthread.php?p=39569189
Now you should have fast boot working (you'll need to install the drivers they are in the 2nd boot loader thread)
This thread will let you flash stock without adb enabled
http://forum.xda-developers.com/showthread.php?p=33156486
Now enable adb in debug settings and install the second boot loader and twrp
http://forum.xda-developers.com/showthread.php?p=37472472
Read at least the first two posts
Sent from my DROID RAZR M using XDA Free mobile app
Looks good. I have a fastboot cable already so should be able to follow the system restore process.
In my circumstances there is no way to identify what version the device is currently running.
Just to clarify, will restoring to (KFHD_SRT_v1.3.5- 7.3.0) be okay regardless of the current version?
I'm not with the device at the moment but may get a chance to recover it in the next two weeks.
Thanks again!
I am unfortunately behind times on the kfhd and most of this is on memory but from when I followed these threads closely, downgrading was an option... Seems like there was some issues with boot loaders not matching causing a red boot screen if you weren't on 7.2.1... If that happens don't freak out, it just means you got something miss matched
Sent from my DROID RAZR M using XDA Free mobile app
mrkhigh said:
I am unfortunately behind times on the kfhd and most of this is on memory but from when I followed these threads closely, downgrading was an option... Seems like there was some issues with boot loaders not matching causing a red boot screen if you weren't on 7.2.1... If that happens don't freak out, it just means you got something miss matched
Click to expand...
Click to collapse
I'm now back with the device and have restored the image successfully.
However now the Wi-Fi will not turn on. I believe this is because the MAC address is not configured correctly, it is displayed as Unavailable on the device.
Using adb shell (as su) I ran the command:
Code:
imde \?
Which outputs:
Code:
Reading idme data ...
Could not find IDME with name = ?
I also attempted to use:
Code:
idme mac F0A22563AAAA
Which outputs:
Code:
Reading idme data ...
Setting mac to F0A22563AAAA
Writing new vars to temp area
You must reboot before new values will take effect
But after a reboot the mac code is not set.
Or, it could be because of version mismatching?
Shall I select the Restore-Factory Recovery option too to ensure this is not the case.
Thanks again!
Normally I do not recommend factory resets but yes, try that. (Keep in mind this turns off adb)
Do you have Bluetooth? Can you register the tablet?
I'm concerned you lost your boot0 block
If you did we may have to get creative.
But first yes try other options..
Sent from my DROID RAZR M using XDA Free mobile app
It's exactly as the title mentions...
Basically I had this tablet for two years, and I love this tablet, we've been through a lot when it came to flashing ROMs and other stuff, the journey so far has been awesome and I don't want it to end here and I won't give up on this tablet!
So here goes... basically I have installed the Magisk Manager app and in the app I chose to install Magisk V14.0 (I chose the recommended option) and once it has finished downloading and installing I then decided to reboot it. Upon rebooting i noticed that the kindle kept rebooting every 3 seconds, so I knew at that point I seriously screwed up!
I'm on the resurrection remix (marshmallow) and when it was installing the Magisk file it said it was updating the boot.img, I think that's the reason why my kindle is acting up. I don't know really know how to fix this issue as I've tried to go into recovery but it simply will not allow me to because it keeps rebooting and doesn't even give me a chance (which is giving me a headache). I looked on similar posts and users have said that a fastboot cable is needed, but I don't have one and I was wondering if using a normal USB cable would do the trick with ADB commands... if possible. If this requires me to purchase (or make) a fastboot cable then I will gladly order (or make) one.
And if ADB method does work, please tell me specific commands to use, and so. Also I have tried getting my laptop (windows 10) to recognise my device, but even when attached and the tablet is on my device isn't showing in device manger, I have downloaded the SDK tools (not manager) and even then I can't use ADB commands in CMD. I typed "ADB shell" (without commas) and even then it won't allow me to access ADB (so please guide me on this area as well).
If you're a user who is interested in helping others and likes to face a challenge, then please step right up and help me as I need all the help at this point! Thank you!
Stone. Cold said:
It's exactly as the title mentions...
Basically I had this tablet for two years, and I love this tablet, we've been through a lot when it came to flashing ROMs and other stuff, the journey so far has been awesome and I don't want it to end here and I won't give up on this tablet!
So here goes... basically I have installed the Magisk Manager app and in the app I chose to install Magisk V14.0 (I chose the recommended option) and once it has finished downloading and installing I then decided to reboot it. Upon rebooting i noticed that the kindle kept rebooting every 3 seconds, so I knew at that point I seriously screwed up!
I'm on the resurrection remix (marshmallow) and when it was installing the Magisk file it said it was updating the boot.img, I think that's the reason why my kindle is acting up. I don't know really know how to fix this issue as I've tried to go into recovery but it simply will not allow me to because it keeps rebooting and doesn't even give me a chance (which is giving me a headache). I looked on similar posts and users have said that a fastboot cable is needed, but I don't have one and I was wondering if using a normal USB cable would do the trick with ADB commands... if possible. If this requires me to purchase (or make) a fastboot cable then I will gladly order (or make) one.
And if ADB method does work, please tell me specific commands to use, and so. Also I have tried getting my laptop (windows 10) to recognise my device, but even when attached and the tablet is on my device isn't showing in device manger, I have downloaded the SDK tools (not manager) and even then I can't use ADB commands in CMD. I typed "ADB shell" (without commas) and even then it won't allow me to access ADB (so please guide me on this area as well).
If you're a user who is interested in helping others and likes to face a challenge, then please step right up and help me as I need all the help at this point! Thank you!
Click to expand...
Click to collapse
Yes, you are going to need a fastboot cable. You can pick one up on Amazon for cheap or you can make your own by using some tutorial online. After you get the fastboot cable, use the Kindle Fire restore tool that I will link down below. Download it (it will take a while) and run it. Please read the directions because I didn't at first and I boot looped my Kindle by installing older recovery and boot image. After this is complete your Kindle will work again. I wouldn't recommend installing Magisk again because it modifies the boot loader. Sorry.
KFHD Restore tool (that tool that I mentioned): https://forum.xda-developers.com/showthread.php?t=1951254
Thank you for this, will. I will follow your instructions once I have received my fastboot cable
Again, thank you. I have left my tablet on my shelf for quite some time now and didn't really have time to fix it due to college work, and so. But I will definitely let you know the results :fingers-crossed:
I made pretty mutch the same error like you and flashed Magisk 12. I used the fastboot cable, entered fastboot and used the recovery tool to restore recovery and stock Rom with supersu and apex launcher. After following exectly the steps in 2. Bootloader and twrp. The problem I am facing is the same I faced before. After flashing linearOS 14 with twrp. I reboot from recovery. At first it showes the orange logo and the the blue. And it stays at blue logo for hours.
I don't know what to do. The strange thing is. I can boot in the recovered Amazonfire OS. But I can't flash any costum Rom.
I have no idea what I made wrong during the process. I followed all steps and repeated the procedure 3 times.
Always ending in blue logo.
Even without flashing any rom. Only following the steps to flash twrp with all the other stuff I am stuck on blue screen.
Please I need advice. Help me
Hi Guys
A friend has given me a table he "bricked" a few months ago. Its a fire 7. I got it to run an old Lineage ROM back in 2017. I think it was on 5.1.1 when I got it.
He tried to flash a different ROM using flashfire and it failed, he says it gave an error about storage space - I am assuming he didn't wipe first.
Now the tablet wont boot. It powers on, shows the amazon splash then reboots, over & over.
I can get to the Amazon recovery holding the vol down button and from there into fastboot - can I recover this unit? I'm wondering if I can use adb to go from fastboot to TWRP then flash a new ROM and it will boot again?
I know a bit but not much about adb etc. Can anyone point me in the right direction?
EDIT: While messing about I have tried the info in this thread: https://forum.xda-developers.com/amazon-fire/orig-development/twrp-recovery-t3242548
I can push the TWRP to the device with fastboot but it fails to boot it with error: (remote: unknown command)
I assume this means its on the locked 5.1.X bootloader and not 5.0.X
Any other options to flash a new bootable ROM to it from the Amazon recovery/fastboot?
Thanks.
cardyology said:
Hi Guys
A friend has given me a table he "bricked" a few months ago. Its a fire 7. I got it to run an old Lineage ROM back in 2017. I think it was on 5.1.1 when I got it.
He tried to flash a different ROM using flashfire and it failed, he says it gave an error about storage space - I am assuming he didn't wipe first.
Now the tablet wont boot. It powers on, shows the amazon splash then reboots, over & over.
I can get to the Amazon recovery holding the vol down button and from there into fastboot - can I recover this unit? I'm wondering if I can use adb to go from fastboot to TWRP then flash a new ROM and it will boot again?
I know a bit but not much about adb etc. Can anyone point me in the right direction?
EDIT: While messing about I have tried the info in this thread: https://forum.xda-developers.com/amazon-fire/orig-development/twrp-recovery-t3242548
I can push the TWRP to the device with fastboot but it fails to boot it with error: (remote: unknown command)
I assume this means its on the locked 5.1.X bootloader and not 5.0.X
Any other options to flash a new bootable ROM to it from the Amazon recovery/fastboot?
Thanks.
Click to expand...
Click to collapse
You'll need to reload FireOS and start over as if it were a new device. If you're certain of the bootloader build reinstall FireOS 5.3.1 to avoid a potential hard brick. You'll then need to root with KingRoot, migrate to SuperSU, find a working build of FlashFire and hope the same thing doesn't happen again. All while making sure the device doesn't take an OTA update from Amazon. In short, a royal PiTA.
Note: there is an evolving hardware hack that may prove easier once it is a bit more mature. Involves cracking open the case (very easy) and shunting a point on the mainboard to ground. At present the exploit needs to run from a Linux based host but I suspect a Windows varient will soon be available. You'll find several threads discussing current progress.
The easiest way to fix this now is to follow the instructions in this thread here. This is the second method mentioned in the above post. This will reinstall the bootloader files and give you a 5.01 bootloader, defeating anti-rollback protection in the process. Afterwards you can load TWRP from fastboot.
As you probably have a 5.1.1 preloader now you should not need to open the case to enter download mode, holding down the left volume button when plugging in the USB cable should be enough.
Davey126 said:
You'll need to reload FireOS and start over as if it were a new device. If you're certain of the bootloader build reinstall FireOS 5.3.1 to avoid a potential hard brick. You'll then need to root with KingRoot, migrate to SuperSU, find a working build of FlashFire and hope the same thing doesn't happen again. All while making sure the device doesn't take an OTA update from Amazon. In short, a royal PiTA.
Note: there is an evolving hardware hack that may prove easier once it is a bit more mature. Involves cracking open the case (very easy) and shunting a point on the mainboard to ground. At present the exploit needs to run from a Linux based host but I suspect a Windows varient will soon be available. You'll find several threads discussing current progress.
Click to expand...
Click to collapse
Thank you for this - I read the hardware hack but also the option to reload fire OS & considered this to be the best option but like a ****, I flashed the tablet with Fire 5.1.2 - I now have an unbootable device. Black screen.
Anything I can do from this point?
MontysEvilTwin said:
The easiest way to fix this now is to follow the instructions in this thread here. This is the second method mentioned in the above post. This will reinstall the bootloader files and give you a 5.01 bootloader, defeating anti-rollback protection in the process. Afterwards you can load TWRP from fastboot.
As you probably have a 5.1.1 preloader now you should not need to open the case to enter download mode, holding down the left volume button when plugging in the USB cable should be enough.
Click to expand...
Click to collapse
As mentioned above, I tried to use the Amazon bootloader to flash FireOS back to the device and start again with it - I flashed 5.1.2 like an idiot and the tablet is now "dead" - I cant seem to even power it on.
Would the method described here recover the brick I now have? : )
Thanks again for the replies guys ! I think I can do the hardware hack if it will help - nothing to lose at this stage really.
cardyology said:
Thank you for this - I read the hardware hack but also the option to reload fire OS & considered this to be the best option but like a ****, I flashed the tablet with Fire 5.1.2 - I now have an unbootable device. Black screen.
Anything I can do from this point?
Click to expand...
Click to collapse
Your device is recoverable - and you may not even have to crack the case. This is the thread you'll want to follow. Still no Windows support but the process as fairly easy once you get past the prerequisites.
cardyology said:
As mentioned above, I tried to use the Amazon bootloader to flash FireOS back to the device and start again with it - I flashed 5.1.2 like an idiot and the tablet is now "dead" - I cant seem to even power it on.
Would the method described here recover the brick I now have? : )
Thanks again for the replies guys ! I think I can do the hardware hack if it will help - nothing to lose at this stage really.
Click to expand...
Click to collapse
The hack I was talking about has evolved a bit now: see here. This will reset anti-rollback protection so should unbrick the tablet. You won't even have to open the case: start with the tablet off and hold down the left volume button and plug in the USB cable as described in the post. You will end up with TWRP installed on the device and fully unlocked fastboot.
MontysEvilTwin said:
The hack I was talking about has evolved a bit now: see here. This will reset anti-rollback protection so should unbrick the tablet. You won't even have to open the case: start with the tablet off and hold down the left volume button and plug in the USB cable as described in the post. You will end up with TWRP installed on the device and fully unlocked fastboot.
Click to expand...
Click to collapse
Nice, I will give that a try now.
Thanks.