Related
Hi everyone, I have two kindle fire, I messed with both of them.
I've root them the first one has the problem with the yellow triangle logo stucked. And the other one I've tried to reset it to the factory settings and everything was cool until I hit the TWRP utility and I think I erased everything.
I've see tons of posts regarding rooting and troubleshooting related to rooting and i'm pretty sick of rooting, I think that 3 months is sufficient time, please DON'T POST anything related to rooting.
I'm here asking if anyone knows how to flash all the data ofthe kindle from the pc and been able to install the factory software, firmware (I don't know) from scratch from my pc. Anyone, please?
The first one is probably stuck in fastboot. Try giving it a go with "fastboot oem idme bootmode 4000 && fastboot reboot".
For the second one, "I think I erased everything" is as descriptive as not wanting people to post about your procedure is helpful. What exactly is going on with it? For future reference: http://forum.xda-developers.com/showthread.php?t=1644970
You should also update both FFF and TWRP on both devices once they are working normally.
If i may suggest flashing modaco first after a good wipe everything except your sdcard I believe this will make a smoother transition if you desire to return to stock before returning to stock always do a good wioe to remove remnants of previous roms download the latest stock bin and rename it to update.zip do not place it in any folder just at the root of your sdcard flash in twrp this will also wipe out twrp and fff I really dont recommend doing this lots of people fail at doing the procedure correcty modaco is stock with only the market added try this approach first then you can retain fff and twrp for custom backups.
Ok, so, I've been investigating and what I'm really looking is to erase ABSOLUTELY everything from the kindle sdcard, system, etc, everything. And I'm looking for a method to sideload from the pc the orginal stock ROM of Kindle Fire. Any clues, directions? Any fully functional software?
I really, don't want to try the adb commands (I've tried them before), nor follow any tutorial about root troubleshooting.
I'm really sick of them and of all that mal-functioning software that you have to download(Eg. Not-responding superOneClick, kindleFireUnbrickUtility saying in one line <No device found> <Processing something> <Congrats, your kindle is good to go! (When it's not)>, Eternal loading Android Commander)
With all due respect I DON'T want any more of those, as I said, 3 months is sufficient time, I feel so frustrated.
jRam90 said:
Ok, so, I've been investigating and what I'm really looking is to erase ABSOLUTELY everything from the kindle sdcard, system, etc, everything. And I'm looking for a method to sideload from the pc the orginal stock ROM of Kindle Fire. Any clues, directions? Any fully functional software?
I really, don't want to try the adb commands (I've tried them before), nor follow any tutorial about root troubleshooting.
I'm really sick of them and of all that mal-functioning software that you have to download(Eg. Not-responding superOneClick, kindleFireUnbrickUtility saying in one line <No device found> <Processing something> <Congrats, your kindle is good to go! (When it's not)>, Eternal loading Android Commander)
With all due respect I DON'T want any more of those, as I said, 3 months is sufficient time, I feel so frustrated.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=25730666&postcount=2
Read from "Reverting to stock software". You can manually rename the file and then copy it into the KF instead of using ADB for it, just make sure the extension is .zip and not .zip.bin (Windows hides extensions per default settings).
jRam90 said:
Ok, so, I've been investigating and what I'm really looking is to erase ABSOLUTELY everything from the kindle sdcard, system, etc, everything. And I'm looking for a method to sideload from the pc the orginal stock ROM of Kindle Fire. Any clues, directions? Any fully functional software?
Click to expand...
Click to collapse
To restore back to full factory
1. Download Kindle Fire Software Update Version 6.3.1
2. Rename the file to update.zip
3. Get in to TWRP and mount USB drive
4. Copy update.zip to Kindle Fire
5. Unmount USB drive
6. Do factory reset, then wipe system cache, and dalvik cache
7. Flash the update.zip
8. Let it bootloop about 3 times or so...
If you want FFF and TWRP then flash Stock 6.3.1 Basic from TWRP. This has no root or gapps.
Dasanko said:
http://forum.xda-developers.com/showpost.php?p=25730666&postcount=2
Read from "Reverting to stock software". You can manually rename the file and then copy it into the KF instead of using ADB for it, just make sure the extension is .zip and not .zip.bin (Windows hides extensions per default settings).
Click to expand...
Click to collapse
When trying to execute the adb shell commands all I get is:
- exec 'system/bin/sh' failed: No such file or directory (2) -
I've also tried, fastboot update | flash | boot | flash:raw
This is with one kindle, with the other one, I can't even get the PC to recognized it as a USB
Is there any tool, that really erases everything and take the stock ROM to be installed again? Software, script?
jRam90 said:
When trying to execute the adb shell commands all I get is:
- exec 'system/bin/sh' failed: No such file or directory (2) -
I've also tried, fastboot update | flash | boot | flash:raw
This is with one kindle, with the other one, I can't even get the PC to recognized it as a USB
Is there any tool, that really erases everything and take the stock ROM to be installed again? Software, script?
Click to expand...
Click to collapse
Ahh, that's a bother. It's a pretty annoying error. Could be something messed with your TWRP (I'm assuming you tried the commands from there).
There isn't one, but there's really no need for it... you just rename the ROM to update.zip, wipe cache, dalvik-cache and factory reset, and install update.zip. If you just want to flash stock because you like it better for whatever reason, you could also just look at the MoDaCo custom ROM instead, as it is stock based.
As for the other KF... you can't get it recognized, from where? The ROM? TWRP? Fastboot?
Dasanko said:
Ahh, that's a bother. It's a pretty annoying error. Could be something messed with your TWRP (I'm assuming you tried the commands from there).
There isn't one, but there's really no need for it... you just rename the ROM to update.zip, wipe cache, dalvik-cache and factory reset, and install update.zip. If you just want to flash stock because you like it better for whatever reason, you could also just look at the MoDaCo custom ROM instead, as it is stock based.
As for the other KF... you can't get it recognized, from where? The ROM? TWRP? Fastboot?
Click to expand...
Click to collapse
Both of the kindles, are damaged. I can't access them. I just can access one by USB.
For future reference:
This user's issues have been partially dealt with.
The first KF will require a factory cable to be fixed.
The second KF was soft bricked (there were a few corrupt partitions) after a bad flash attempt of the stock ROM. Luckily, FFF was still installed, but the Windows fastboot drivers weren't. Reinstalled FFF+TWRP from Firekit, and then fixed the partitions, wiped and flashed the stock ROM.
Dasanko said:
For future reference:
This user's issues have been partially dealt with.
The first KF will require a factory cable to be fixed.
The second KF was soft bricked (there were a few corrupt partitions) after a bad flash attempt of the stock ROM. Luckily, FFF was still installed, but the Windows fastboot drivers weren't. Reinstalled FFF+TWRP from Firekit, and then fixed the partitions, wiped and flashed the stock ROM.
Click to expand...
Click to collapse
Thanks a LOT, Dasanko !!!!
jRam90 said:
Thanks a LOT, Dasanko !!!!
Click to expand...
Click to collapse
Ok, So, I have the factory cable. How can I test its Ok?
I have another question, the kindle is pratically empty no system, no sdcard memory, probably corrupted ¿How do I use the factory cable, to format the Kindle and install the Stock ROM again?
With the KF off and unplugged, type "fastboot getvar product" on a shell (KFU/tools).
Then plug in the KF using the factory cable. If you get anything listed or returned, it should be working fine. Otherwise, if you wait a few seconds and still nothing, you'll have to check the drivers to make sure the correct fastboot ones are installed.
To check the partitions, you can just "fastboot boot twrp.img" to load a TWRP into memory, and then "adb shell parted /dev/block/mmcblk0 p" to print all partitions' information.
Dasanko said:
With the KF off and unplugged, type "fastboot getvar product" on a shell (KFU/tools).
Then plug in the KF using the factory cable. If you get anything listed or returned, it should be working fine. Otherwise, if you wait a few seconds and still nothing, you'll have to check the drivers to make sure the correct fastboot ones are installed.
To check the partitions, you can just "fastboot boot twrp.img" to load a TWRP into memory, and then "adb shell parted /dev/block/mmcblk0 p" to print all partitions' information.
Click to expand...
Click to collapse
Well, I'm at my job now. So I will try this at home, but the shell is not working since system/sh (shell) it's not in the Kindle. I was trying to boot it yesterday with "fastboot boot twrp.img" and nothing. I also tried: "fastboot getvar product" and nothing but I only used the console. Anyway, let's see what happens...
Quick question, I've read that the factory cable puts the Kindle straight into bootmode, ¿So the color of the power button, has something to do with it? ¿I mean how do I know the kindle has entered factory mode? ¿The orange light is an indicator? (With a standard USB Cable I only get the green light with the power button, with the factory cable I first get green light, then orange light)
I've also read that if I can see the Kindle fire logo, the bootloader is Ok. Hence my Kindle is OK, but I can't enter fastboot mode. ¿Can anyone confirm this?
It'll get stuck in the bootloader screen, and fastboot commands should work as well, provided the drivers are properly installed and working.
Dasanko said:
It'll get stuck in the bootloader screen, and fastboot commands should work as well, provided the drivers are properly installed and working.
Click to expand...
Click to collapse
OK, I've finally made myself a working factory cable. And in the device manger I can see the kindle listed as "Android phone" and in that root it says "Android ADB Interface". Look like drivers are not working. Where can I download them?
Those are the proper drivers for fastboot you should be able to use kfu to send twrp and fff to the device if that doesn't work you will need to fastboot flash them
All I get is < waiting for device>. Looks like the drivers are not installed.
Simply hold the power button down while connected when it says waiting then power it back on and it should send also try unplug replug when it says waiting
---------- Post added at 03:49 PM ---------- Previous post was at 03:44 PM ----------
If you would like some help I have some time before work but you must finish your thread for the benefit of others
I was told to post this here:
The Problem:
I tried to take the crappy amazon software that only works in the US off this kindle fire, Installed JandyKane and Gapps with no problems (i cleared dalvik cache, regular cache, and factory reset) Also installed Clockwork Recovery (which i read somewhere that might have been the problem).
(note: I used the KF utility)
Now when i turn the device on, it shows the Kindle fire logo for a second or two, then a bunch of triangles float on the screen forever and nothing happens.
Ive tried a few unbrick utilities but it keeps saying it cant find the device. Im having troubles booting into recovery mode. (the utility says device not found)
This isnt even my Kindle Fire and its causing me so many problems >.>
Justos said:
I was told to post this here:
The Problem:
I tried to take the crappy amazon software that only works in the US off this kindle fire, Installed JandyKane and Gapps with no problems (i cleared dalvik cache, regular cache, and factory reset) Also installed Clockwork Recovery (which i read somewhere that might have been the problem).
(note: I used the KF utility)
Now when i turn the device on, it shows the Kindle fire logo for a second or two, then a bunch of triangles float on the screen forever and nothing happens.
Ive tried a few unbrick utilities but it keeps saying it cant find the device. Im having troubles booting into recovery mode. (the utility says device not found)
This isnt even my Kindle Fire and its causing me so many problems >.>
Click to expand...
Click to collapse
Is this what you're refering to when you say you see floating triangles?
http://androidbootanimation.com/wp-content/uploads/2012/08/nexus-7-bootanimation.jpg
If so, That is the jandycane/Jellybean Boot animation. On first boot that could take a few minutes before it finishes. It does, however, sound like you are having other problems... have you tried contacting the kindle using fastboot?
Also, I would highly suggest flashing TWRP (team win recovery project) rather than CWM on the Kindle Fire, on most devices I would recommend CWM but on this one it doesn't work as well and leads to problems >>
I also assume that you flashed firefirefire because you said you saw the kindlefire logo before it went to the triangles so you should be fine on that front.
nschiwy said:
Is this what you're refering to when you say you see floating triangles?
If so, That is the jandycane/Jellybean Boot animation. On first boot that could take a few minutes before it finishes. It does, however, sound like you are having other problems... have you tried contacting the kindle using fastboot?
Click to expand...
Click to collapse
Yes thats it! Im going to leave it on for about 5-15 minutes and see what happens. il let you know
I have tried to boot into fastboot mode with the utility and it says cannot find the file specified.
btw: i dont think i installed firefirefire...
EDIT: Yep, after letting the animation run for 10 minutes still nothing.
Im going to try using TWRP now. Il let you know if it helped.
EDIT2: Nope im getting random errors in the command prompt. Is it 100% necessary to use this program?
Justos said:
Yes thats it! Im going to leave it on for about 5-15 minutes and see what happens. il let you know
I have tried to boot into fastboot mode with the utility and it says cannot find the file specified.
btw: i dont think i installed firefirefire...
EDIT: Yep, after letting the animation run for 10 minutes still nothing.
Im going to try using TWRP now. Il let you know if it helped.
EDIT2: Nope im getting random errors in the command prompt. Is it 100% necessary to use this program?
Click to expand...
Click to collapse
If you're talking about KFU, then no. It is not 100% necessary, It is just designed to make it easier for users so they don't have to use command prompt on their own. I am uploading KindleADB from the burrito root method to help us with what you need to do. I will post a link here when it is finished uploading. Do you know how to use command prompt/adb at all?
KindleADB.zip: http://www.mediafire.com/?1fb30q3wqf95b3i
download this file and unzip and then place it on the root directory of your C:/ Drive (this is not completely necessary, it is just for convenience)
Then try seeing if your device shows up in adb by typing in:
Code:
cd /
cd kindleadb
adb devices
OR
Code:
cd /
cd kindleadb
fastboot getvar product
Either way you want it to show either a series of numbers or say something like amazon kindle or something to that degree, if it is blank or does not leave the <waiting for device> status then we will need to go in another direction. My suggestion for fastboot would be to turn the kindle completely off and then do those commands and then plug in your kindle when it says <waiting for device>... get back to me on your results and we can go from there
Did both of them. On the first part it says
List of Devices attached: (nothing shows up)
second time i did exactly what you said. it was waiting for device before i turned the kindle on, nothing happened.
EDIT: Okay I tried using the utility again, whenever i try to fastboot or boot into recovery it gives me this error
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The kindle has been told to reboot in Fastboot Mode.
Press any key to continue . . .
I'm having the same issue here.
The triangles keep turning and nothing happens.
In the KFU the devices keep showing OFFLINE and Boot Status UNKNOW.
The cd /
cd kindleadb
adb devices
don't show the device and
cd /
cd kindleadb
fastboot getvar product
show waiting for device
Edited:
I dunno what i've done, but im KFU appears Online in normal boot (4000), but the options don't work anymore.
Justos said:
Did both of them. On the first part it says
List of Devices attached: (nothing shows up)
second time i did exactly what you said. it was waiting for device before i turned the kindle on, nothing happened.
EDIT: Okay I tried using the utility again, whenever i try to fastboot or boot into recovery it gives me this error
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The kindle has been told to reboot in Fastboot Mode.
Press any key to continue . . .
Click to expand...
Click to collapse
As long as you have CWM instead of TWRP, you're just wasting your time trying to install Jelly Bean. Install TWRP and try again.
same problem
I have the same exact problem with my fire, it happened two days ago but i hadn't seen anyone else with the problem. I couldn't fix it so i ordered a factory cable on ebay, I'm waiting on that now...
no fff? how about just booting to recovery and flashing a new rom after a full wipe or restoring a backup or have the normal ways of doing things just become obsolete lol I mean so you cant flash isc or jelly bean mount your sd card in recovery transfer one of a few different cm7 roms which will flash right on cwmr and your golden ...
Thepooch said:
no fff? how about just booting to recovery and flashing a new rom after a full wipe or restoring a backup or have the normal ways of doing things just become obsolete lol I mean so you cant flash isc or jelly bean mount your sd card in recovery transfer one of a few different cm7 roms which will flash right on cwmr and your golden ...
Click to expand...
Click to collapse
I'm trying to but, but when I try to enter in recovery mode, i get this:
The system cannot find the drive specified.
Failed to Copy 'files\rcmode' to 'data/local/rcmode' : permission denied
unable do chmode /data/local/rcmode: no such file or directory
/system/bin/sh: data/local/rcmode: not found
recovery?
Reinaque said:
I'm trying to but, but when I try to enter in recovery mode, i get this:
The system cannot find the drive specified.
Failed to Copy 'files\rcmode' to 'data/local/rcmode' : permission denied
unable do chmode /data/local/rcmode: no such file or directory
/system/bin/sh: data/local/rcmode: not found
Click to expand...
Click to collapse
i'm seeing that too when i try to change it to recovery on KFU, but now its actually showing adb online and boot status 4000 as oppposed to when it said offline and unknown for me
What are all the ways to boot into recovery mode? It wont do it with the KFU.
I understand what I need to do now, Factory reset, then install TWRP, then firefirefire, then flash the rom and Gapps?
How am i supposed to do this if i cant get into recovery mode?
Justos said:
What are all the ways to boot into recovery mode? It wont do it with the KFU.
I understand what I need to do now, Factory reset, then install TWRP, then firefirefire, then flash the rom and Gapps?
How am i supposed to do this if i cant get into recovery mode?
Click to expand...
Click to collapse
First I would try using the kindle unbrick utility:
I couldn't find the thread for this so I just have it uploaded to my mediafire account: http://www.mediafire.com/download.php?6kxjs8kbmgn8h3l
I also found this Kindle Fire Unbrick Utility, it might actually be a newer version of the one I provided above with a Graphic UI: http://forum.xda-developers.com/showthread.php?t=1428428
If that doesn't work I would suggest trying a linux environment to contact your device, as Android is linux based and therefore can communicate with a linux machine better than a windows machine. (plus drivers are always a giant mess in windows)
Use this guide to make a portable linux box to try to save your kindle:
http://forum.xda-developers.com/showthread.php?t=1670405
If all else fails, you're probably going to need a factory cable to get your Kindle back up and running:
http://forum.xda-developers.com/showpost.php?p=20380015&postcount=9
Once you have this you can run commands from linux very easily to unbrick your kindle. If you need help with this feel free to PM me.
Hi all,
I tried to install the Jellybean on my One X following instructions step by step from here - the 'guide to installing' link, under the mirrors
http://forum.xda-developers.com/showthread.php?t=1763240
However when booting up it stuck on the flashing crosses for about 20 minutes before I decided it was probably not working. I read the comments and realised the only part I didn't do was a wipe, so I wanted to try again, but before doing a wipe I wanted to make sure I could then re-send the relevant files to my phone via adb, because I assumed a wipe would wipe those files off. However when I do adb devices it doesn't bring up the phone. However if I go into recovery, (CWmod 5.8.4.0) then run adb devices it does bring up my phone on the list. Also when the phone is apparently trying to boot up and stuck on the splash screen loading and I run adb devices it also sees my phone there too. I can send files across. I tried with a recovery img, but the adb message said it was waiting for the device to respond, which it never did.
I had a CWmod backup made before starting, so I ran that, but all that did was change the splash screen it gets stuck on from the colourful crosses to the HTC One logo screen. But it still gets stuck.
Does anyone know what to do from here? I still have access to the bootloader. Do I do a factory reset from the bootloader? Do I do it from CWrecovery? I'm feeling a little bit worried now
Slaxington said:
Hi all,
I tried to install the Jellybean on my One X following instructions step by step from here - the 'guide to installing' link, under the mirrors
http://forum.xda-developers.com/showthread.php?t=1763240
However when booting up it stuck on the flashing crosses for about 20 minutes before I decided it was probably not working. I read the comments and realised the only part I didn't do was a wipe, so I wanted to try again, but before doing a wipe I wanted to make sure I could then re-send the relevant files to my phone via adb, because I assumed a wipe would wipe those files off. However when I do adb devices it doesn't bring up the phone. However if I go into recovery, (CWmod 5.8.4.0) then run adb devices it does bring up my phone on the list. Also when the phone is apparently trying to boot up and stuck on the splash screen loading and I run adb devices it also sees my phone there too. I can send files across. I tried with a recovery img, but the adb message said it was waiting for the device to respond, which it never did.
I had a CWmod backup made before starting, so I ran that, but all that did was change the splash screen it gets stuck on from the colourful crosses to the HTC One logo screen. But it still gets stuck.
Does anyone know what to do from here? I still have access to the bootloader. Do I do a factory reset from the bootloader? Do I do it from CWrecovery? I'm feeling a little bit worried now
Click to expand...
Click to collapse
First of all take a deep breath. Go get yourself a cup of coffee or whatever your favorite drink is. Preferably non-alcoholic.
In CWM, if you go to mounts & storage and mount your sdcard, you will be able to transfer files to your phone's sdcard. One reminder, reboot your phone to bootloader again after file transfer.
You have to install rom's kernel from your PC using fastboot command (even when restoring from your nandroid backup. Copy the boot.img file to your PC from CWM as I described above)
fastboot flash boot boot.img
fastboot erase cache
As for adb commands, CWM supports adb commands not fastboot commands. You have to use fastboot commands when in bootloader in fastboot usb mode such as
fastboot devices
fastboot reboot-bootloader
etc
eyosen said:
First of all take a deep breath. Go get yourself a cup of coffee or whatever your favorite drink is. Preferably non-alcoholic.
In CWM, if you go to mounts & storage and mount your sdcard, you will be able to transfer files to your phone's sdcard. One reminder, reboot your phone to bootloader again after file transfer.
You have to install rom's kernel from your PC using fastboot command (even when restoring from your nandroid backup. Copy the boot.img file to your PC from CWM as I described above)
fastboot flash boot boot.img
fastboot erase cache
As for adb commands, CWM supports adb commands not fastboot commands. You have to use fastboot commands when in bootloader in fastboot usb mode such as
fastboot devices
fastboot reboot-bootloader
etc
Click to expand...
Click to collapse
Hiya, thanks for that. Just a couple points for clarification. Do I do a wipe first? Or Format? Which wiping option should I go for? There's wipe data/factory reset, and wipe cache partition. Also there's the factor reset option on the first bootloaders screen. And if I do wipe it won't that remove the clockworkmod for recovery?
The rom's kernel... would that be, in this jellybeany case, the file tg_endeavoru-ota-33.zip, and the boot.img file?
I realise these are things I should have learned first, but I thought it seemed rather straight forward, now I'm trying to take no risks so just want to make 100% sure I understand everything involved.
Thanks for your help, knowing I'm not doomed has lifted most of the weight
Slaxington said:
Hiya, thanks for that. Just a couple points for clarification. Do I do a wipe first? Or Format? Which wiping option should I go for? There's wipe data/factory reset, and wipe cache partition. Also there's the factor reset option on the first bootloaders screen. And if I do wipe it won't that remove the clockworkmod for recovery?
The rom's kernel... would that be, in this jellybeany case, the file tg_endeavoru-ota-33.zip, and the boot.img file?
I realise these are things I should have learned first, but I thought it seemed rather straight forward, now I'm trying to take no risks so just want to make 100% sure I understand everything involved.
Thanks for your help, knowing I'm not doomed has lifted most of the weight
Click to expand...
Click to collapse
Since you will be coming back from jb, wiping would prevent any future problems. Even if you decide to stay with JB, do a wipe as below
In cwm,
Wipe cache
Under advanced, wipe Dalvik cache
Under mounts and storage, format system
Cwm will remain intact. Also, I think selecting factory reset from bootloader menu will take you to cwm anyways. It's been awhile.
Yes, it is the boot.img file inside the zip. But you must use the full rom and not the ota. Ota only includes updates to some of the already existing files. It's just an upgrade.
Sent from my HTC One X using xda premium
So I'm trying to revive my wifes old kindle fire that's been sitting in the bottom of our cabinent for about 4 months now. I rooted the thing when I bought it (valentines day last year) and put a custom rom on it, but when I powered it on yesterday, it was weird, the boot animation was zoomed in a little and distorted, and it was moved over to the right side of hte screen, so you could only see about half of it. And that's all it did. So i booted into recover (clockwork v5.0.2.7 FULL) to restore or reflash the zip, and there is ABSOLUTELY nothing anywhere, so I mounted the usb storage to the computer, and there is nothing, and i mean nothing on the kindle. So anyways, I donwnloaded a couple roms and put them on the kindle, boot into recovery, flash the rom, and it's the same thing. I reboot after a successful flash the boot image is distorted and out of place, and it just hangs there. Any ideas?
You're doing a full wipe/factory reset first, right?
Sent from my GT-p511x
vballrkc said:
So I'm trying to revive my wifes old kindle fire that's been sitting in the bottom of our cabinent for about 4 months now. I rooted the thing when I bought it (valentines day last year) and put a custom rom on it, but when I powered it on yesterday, it was weird, the boot animation was zoomed in a little and distorted, and it was moved over to the right side of hte screen, so you could only see about half of it. And that's all it did. So i booted into recover (clockwork v5.0.2.7 FULL) to restore or reflash the zip, and there is ABSOLUTELY nothing anywhere, so I mounted the usb storage to the computer, and there is nothing, and i mean nothing on the kindle. So anyways, I donwnloaded a couple roms and put them on the kindle, boot into recovery, flash the rom, and it's the same thing. I reboot after a successful flash the boot image is distorted and out of place, and it just hangs there. Any ideas?
Click to expand...
Click to collapse
The boot animation starting half off the screen is a bug that effects all CM ROMs. Other than it being ugly, it has no effect on the normal usage of the ROM itself. It looks like you received an OTA update from Cyanogenmod and it's possible that may have had some unintended side effects. Reinstalling the ROM, while being sure to factory reset in recovery, should fix the problem...assuming you aren't dealing with something more serious.
The point of that last statement is to highlight the fact that CWM recovery for kindle fires is NOT safe to use. Some versions contain a bug that can create bad blocks which, in effect, renders the device (mostly) useless. If nothing else, you definitely need to install a more current custom recovery for the Kindle Fire. If you like CWM, Cannibal Open Touch Recovery is based off of it and will be very familiar to what you're used to, except significantly safer and more stable. I would say replace your recovery first and then deal with any remaining problematic symptoms.
soupmagnet said:
The boot animation starting half off the screen is a bug that effects all CM ROMs. Other than it being ugly, it has no effect on the normal usage of the ROM itself. It looks like you received an OTA update from Cyanogenmod and it's possible that may have had some unintended side effects. Reinstalling the ROM, while being sure to factory reset in recovery, should fix the problem...assuming you aren't dealing with something more serious.
The point of that last statement is to highlight the fact that CWM recovery for kindle fires is NOT safe to use. Some versions contain a bug that can create bad blocks which, in effect, renders the device (mostly) useless. If nothing else, you definitely need to install a more current custom recovery for the Kindle Fire. If you like CWM, Cannibal Open Touch Recovery is based off of it and will be very familiar to what you're used to, except significantly safer and more stable. I would say replace your recovery first and then deal with any remaining problematic symptoms.
Click to expand...
Click to collapse
Well the only recovery downloads i can find are apk's that need to be installed and then downloaded within the app. As I cannot actually get into any rom (i've tried flashing 3, same thing, weird distorted boot image off to the side) I will need a .zip that i can flash.
vballrkc said:
Well the only recovery downloads i can find are apk's that need to be installed and then downloaded within the app. As I cannot actually get into any rom (i've tried flashing 3, same thing, weird distorted boot image off to the side) I will need a .zip that i can flash.
Click to expand...
Click to collapse
Here, let me Google that for you
http://forum.xda-developers.com/showthread.php?t=2025793
BTW, you can still install a recovery.img in recovery without it being a flashable .zip...
adb push recovery.img /sdcard/
adb shell dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p5
soupmagnet said:
Here, let me Google that for you
http://forum.xda-developers.com/showthread.php?t=2025793
BTW, you can still install a recovery.img in recovery without it being a flashable .zip...
adb push recovery.img /sdcard/
adb shell dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p5
Click to expand...
Click to collapse
I see no download for a .zip file that can be flashed from recovery. All I get is a .img file.
vballrkc said:
I see no download for a .zip file that can be flashed from recovery. All I get is a .img file.
Click to expand...
Click to collapse
Did you happen to read what I wrote, or did you just go straight to the link?
Yes I did. And if you read mine you would know that I asked for a flashable zip. Not a method of flashing a .img from recovery. But thank you for your effort it.is appreciated.
vballrkc said:
Yes I did. And if you read mine you would know that I asked for a flashable zip. Not a method of flashing a .img from recovery. But thank you for your effort it.is appreciated.
Click to expand...
Click to collapse
I did read and I'm well aware of what you're asking for. I even made mention of it in a previous post. The problem here is that Cannibal Open Touch recovery doesn't have a flashable .zip, and there's a strong possibility that installing TWRP will only compound your problems. I'm trying to point you in the right direction, but I'm having trouble understanding your aversion to using the command line, which is essentially faster and more straightforward to begin with.
soupmagnet said:
I did read and I'm well aware of what you're asking for. I even made mention of it in a previous post. The problem here is that Cannibal Open Touch recovery doesn't have a flashable .zip, and there's a strong possibility that installing TWRP will only compound your problems. I'm trying to point you in the right direction, but I'm having trouble understanding your aversion to using the command line, which is essentially faster and more straightforward to begin with.
Click to expand...
Click to collapse
Thank you.
ok, so I'm really trying to avoid using adb or anything, but i may have to before this all said and done. But just for grins I tried flashing an older rom, i believe it was the cm-9 rom, and now it just boot loops. Its not the same issue, just a new one. Any ideas?
vballrkc said:
ok, so I'm really trying to avoid using adb or anything, but i may have to before this all said and done. But just for grins I tried flashing an older rom, i believe it was the cm-9 rom, and now it just boot loops. Its not the same issue, just a new one. Any ideas?
Click to expand...
Click to collapse
I mentioned earlier that using CWM recovery is not safe to use. There's a bug in some versions that can result in the dreaded EMMC superbrick. Don't use it. On top of that, all of the cm9 roms are quite unstable as well, including issues that can prevent the device from charging.
From the looks of it, your bootloop is from flashing CM9 in CWM, which in most cases, the two aren't compatible. So, before you get yourself into any more trouble, I need to ask....
1) Do you have FireFireFire installed? If so, what version (yellow triangle or blue & white KF logo)?
2) Do you still have access to custom recovery?
soupmagnet said:
I mentioned earlier that using CWM recovery is not safe to use. There's a bug in some versions that can result in the dreaded EMMC superbrick. Don't use it. On top of that, all of the cm9 roms are quite unstable as well, including issues that can prevent the device from charging.
From the looks of it, your bootloop is from flashing CM9 in CWM, which in most cases, the two aren't compatible. So, before you get yourself into any more trouble, I need to ask....
1) Do you have FireFireFire installed? If so, what version (yellow triangle or blue & white KF logo)?
2) Do you still have access to custom recovery?
Click to expand...
Click to collapse
you'll have to pardon my lack of knowledge, as it's been at least a year since i've messed with this and I have several android devices, each with their own set of jargen. I know I HAVE installed firefirefire. as to what version, i'm sorry, I don't know. And I do have access to clockwork recovery, but that's it. I can not get into any rom, i've flashed probably 10 different ones.
vballrkc said:
you'll have to pardon my lack of knowledge, as it's been at least a year since i've messed with this and I have several android devices, each with their own set of jargen. I know I HAVE installed firefirefire. as to what version, i'm sorry, I don't know. And I do have access to clockwork recovery, but that's it. I can not get into any rom, i've flashed probably 10 different ones.
Click to expand...
Click to collapse
Okay, don't flash any more ROMs in clockwork recovery. I can't stress that enough.
In order to move forward from here, you need to be able to communicate with the device over ADB, so open a command prompt, change directories (cd) to the one containing adb.exe, and enter 'adb devices' while booted into recovery Does it show that a device is connected?
soupmagnet said:
Okay, don't flash any more ROMs in clockwork recovery. I can't stress that enough.
In order to move forward from here, you need to be able to communicate with the device over ADB, so open a command prompt, change directories (cd) to the one containing adb.exe, and enter 'adb devices' while booted into recovery Does it show that a device is connected?
Click to expand...
Click to collapse
ok hang on, i don't even have adb installed on this computer. been a while since i've used it too. is there a thread in this forum that will help me with that?
vballrkc said:
ok hang on, i don't even have adb installed on this computer. been a while since i've used it too. is there a thread in this forum that will help me with that?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=44446906&postcount=9
That should do the trick
ok, all the threads and "how-to's" i'm finding require that you be able to access the tablets settings to enable ADB. As I cannot do that, i'm not sure what to do now. I mean, is this really that hard? I feel like there is an easy answer out there for me to be able to flash a new recovery....maybe i'm wrong. does ANYONE have an idea on how I can flash a different recovery other then clockwork. Again, I CONNOT do anything on this tablet other then access clockwork recovery andboot loop, that it all.
Very similar similar situation after flashing a rom. Please help me
Hello,
I am running into the a very similar situation. I am running 6.3.2
First I ran KFU 0.9.9, this installed FFF with no problem. KFU downloaded "most recent twrp" and installed it (but does not work, freezes at teamwin logo). and it had trouble installing su.
After looking around for ways to root kindle fire 6.3. without using KFU. I found a tutorial on the following website Eputor.com. (google search eputor how to root kindle fire)
after downloading the recommended files, I ran these comands using cmd
1. adb push fbmode /data/local/fbmode
2. adb shell chmod 755 /data/local/fbmode
3. adb shell /data/local/fbmode
4. adb reboot
after booting into Fastboot mode, I use the following commands
1. fastboot -i 0x1949 flash bootloader u-boot.bin
2. fastboot -i 0x1949 flash recovery twrp.img
3. fastboot -i 0x1949 oem idme bootmode 4000
4. fastboot -i 0x1949 reboot
after booting into recover I use the following commands:
1. adb shell mount system
2. adb push su /system/xbin/su
3. adb shell chown 0.0 /system/xbin/su
4. adb shell chmod 06755 /system/xbin/su
After installing SU and gapps I believe I have accessed root because when I install 3rd party apps SU asks for permission to grant permission.
I have had to manually flash twrp 2.4 because every time I flash a newer twrp and boot into twrp, twrp gets stuck at at the teamwin logo then reboots with no access to recovery, only the teamwin logo. Ive flashed every twrp version from 2.6.3.1 going down the list of twrp downloads provided by the website that (sorry, I would provide the link but can't because I have not have 10 posts yet.) the twrp website provide but the only recovery to actually work on my kindle is twrp 2.4.0.0.
after flashing twrp 2.4, I flashed 3 different roms and have had no luck.
1st rom - I wiped cache, dalvik cache, factory rest and then flashed jb-4.2.2-kfire-hashcode-2013-02-12.
wiped cache again after install was complete, then flashed gapps and after that , wiped cache again.
after rebooting, I get stuck on a the boot animation. It then freezes for a few minutes then it reboots back into FFF then loops back same boot animation loop.
2nd rom - I then proceed to wiped cache, dalvik cache, factory rest and then flash Cm - 10.1 - 20130724 - 1413 - otter-sgt7.zip, wiped cache again after install was complete, then flashed gapps and after that , wiped cache again and reboot.
After rebooting, I get stuck on a the boot animation very similar to the previous rom, it boots up to the boot animation, but the difference is that the boot animation is off centered and cut off. It then freezes for a few minutes then it reboots back into FFF then loops back same boot animation loop.
3rd rom -I do the exact same with Pac_otter_4.3-build.1.RC_20130824- 144117.zip and the exact same thing happens boot loop with off centered boot logo. then reboots into fff and off centered boot logo.
I cant find a rom that will work. I really hope this is enough information, I hope someone out there can help me.
In this thread, it was advised to wipe data. in twrp 2.4.0.0, the wipe options are cache, dalvik cache, factory reset, system, external storage, and android secure. Is it nececary to wipe external storage, system and android secure? I have only wiped cache, dalvik cache, factory reset, system. Please advise.
MasterLarry said:
Hello,
I am running into the a very similar situation. I am running 6.3.2
First I ran KFU 0.9.9, this installed FFF with no problem. KFU downloaded "most recent twrp" and installed it (but does not work, freezes at teamwin logo). and it had trouble installing su.
After looking around for ways to root kindle fire 6.3. without using KFU. I found a tutorial on the following website Eputor.com. (google search eputor how to root kindle fire)
after downloading the recommended files, I ran these comands using cmd
1. adb push fbmode /data/local/fbmode
2. adb shell chmod 755 /data/local/fbmode
3. adb shell /data/local/fbmode
4. adb reboot
after booting into Fastboot mode, I use the following commands
1. fastboot -i 0x1949 flash bootloader u-boot.bin
2. fastboot -i 0x1949 flash recovery twrp.img
3. fastboot -i 0x1949 oem idme bootmode 4000
4. fastboot -i 0x1949 reboot
after booting into recover I use the following commands:
1. adb shell mount system
2. adb push su /system/xbin/su
3. adb shell chown 0.0 /system/xbin/su
4. adb shell chmod 06755 /system/xbin/su
After installing SU and gapps I believe I have accessed root because when I install 3rd party apps SU asks for permission to grant permission.
I have had to manually flash twrp 2.4 because every time I flash a newer twrp and boot into twrp, twrp gets stuck at at the teamwin logo then reboots with no access to recovery, only the teamwin logo. Ive flashed every twrp version from 2.6.3.1 going down the list of twrp downloads provided by the website that (sorry, I would provide the link but can't because I have not have 10 posts yet.) the twrp website provide but the only recovery to actually work on my kindle is twrp 2.4.0.0.
after flashing twrp 2.4, I flashed 3 different roms and have had no luck.
1st rom - I wiped cache, dalvik cache, factory rest and then flashed jb-4.2.2-kfire-hashcode-2013-02-12.
wiped cache again after install was complete, then flashed gapps and after that , wiped cache again.
after rebooting, I get stuck on a the boot animation. It then freezes for a few minutes then it reboots back into FFF then loops back same boot animation loop.
2nd rom - I then proceed to wiped cache, dalvik cache, factory rest and then flash Cm - 10.1 - 20130724 - 1413 - otter-sgt7.zip, wiped cache again after install was complete, then flashed gapps and after that , wiped cache again and reboot.
After rebooting, I get stuck on a the boot animation very similar to the previous rom, it boots up to the boot animation, but the difference is that the boot animation is off centered and cut off. It then freezes for a few minutes then it reboots back into FFF then loops back same boot animation loop.
3rd rom -I do the exact same with Pac_otter_4.3-build.1.RC_20130824- 144117.zip and the exact same thing happens boot loop with off centered boot logo. then reboots into fff and off centered boot logo.
I cant find a rom that will work. I really hope this is enough information, I hope someone out there can help me.
In this thread, it was advised to wipe data. in twrp 2.4.0.0, the wipe options are cache, dalvik cache, factory reset, system, external storage, and android secure. Is it nececary to wipe external storage, system and android secure? I have only wiped cache, dalvik cache, factory reset, system. Please advise.
Click to expand...
Click to collapse
Thanks for taking the time to share your experience. I too hope that someone can help us with this. I'm confident someone will. I've never had a problem that the good folks at XDA couldn't help me fix.
Just putting this out, this is my first time rooting and 'trying to get android' on a device. I recently got a kindle fire 2nd generation but hated the UI and other stuff. My friend suggested me to try rooting it and turn it into an android tablet instead. Following the rooting guide in the forum, I have successfully rooted the device. The next step was installing the 2nd bootloader and TWRP. I followed Hashcode's guide
HTML:
http://forum.xda-developers.com/showthread.php?t=2100963
but got stuck at step 4, flashing the bootloader. I have searched the thread but have not seen anyone solving the issue I'm having. Using cmd, I got the device to boot into fastboot mode and tried to type in 'fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin'. However, it returned an error: cannot load 'otter2-u-boot-prod-10.2.4.bin' : No error. Can someone help me? Your help is much appreciated.
Extra Info:
Amazon Kindle Fire 2 on 10.4.8 (rooted and has SuperSU)
using Windows 7 as workstation
installed KFFirstAide (yes, I have tried option 40 but stuck on <waiting for device>)
Also, I have put the 'otter2-u-boot-prod-10.2.4.bin', 'otter2-twrp-2.6.3.0-recovery.img', and 'otter2-freedom-boot-10.4.6.img' files in the C:\KFFirstAide folder. (I was thinking this might be the reason why it is not working but cannot be sure)
rocketfans14 said:
Just putting this out, this is my first time rooting and 'trying to get android' on a device. I recently got a kindle fire 2nd generation but hated the UI and other stuff. My friend suggested me to try rooting it and turn it into an android tablet instead. Following the rooting guide in the forum, I have successfully rooted the device. The next step was installing the 2nd bootloader and TWRP. I followed Hashcode's guide
HTML:
http://forum.xda-developers.com/showthread.php?t=2100963
but got stuck at step 4, flashing the bootloader. I have searched the thread but have not seen anyone solving the issue I'm having. Using cmd, I got the device to boot into fastboot mode and tried to type in 'fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin'. However, it returned an error: cannot load 'otter2-u-boot-prod-10.2.4.bin' : No error. Can someone help me? Your help is much appreciated.
Extra Info:
Amazon Kindle Fire 2 on 10.4.8 (rooted and has SuperSU)
using Windows 7 as workstation
installed KFFirstAide (yes, I have tried option 40 but stuck on <waiting for device>)
Also, I have put the 'otter2-u-boot-prod-10.2.4.bin', 'otter2-twrp-2.6.3.0-recovery.img', and 'otter2-freedom-boot-10.4.6.img' files in the C:\KFFirstAide folder. (I was thinking this might be the reason why it is not working but cannot be sure)
Click to expand...
Click to collapse
Yea you are kinda right, its because you are running the command from the system32 folder, you need to be cd'd into the folder that the files are in to run that command so "cd c:\kffaide" or w/e first and then run that command. Make sure you check the md5sum of that file before you flash it so you don't end up with a hard brick.
stunts513 said:
Yea you are kinda right, its because you are running the command from the system32 folder, you need to be cd'd into the folder that the files are in to run that command so "cd c:\kffaide" or w/e first and then run that command. Make sure you check the md5sum of that file before you flash it so you don't end up with a hard brick.
Click to expand...
Click to collapse
I have checked the md5sum of the files using a program I found here on xda. I'll try to do the cd from file right now and I'll let you know how that went. Thank you for the quick reply.
Ok, I got it up to the TWRP recovery screen. But how do I continue to flash the stock in step 4 after installing cm10.2 and gapps? Also, I do not have a factory fastboot cable.
EDIT
After installing CM10.2 and gapps, I hit reboot on TWRP and has 'unfortunately, com.android.phone has stop working' message popped up on the screen. Is it because I haven't continue to the section "Flashing back to stock" in step 4?
EDIT2 (I don't think this is related to the bootloader problem but I would like some assistance)
I rebooted again and didn't get the 'unfortunately' messages again. However, when I plug it into my computer, the device doesn't charge when it is active but charges when I put it into sleep mode. Is there any way to fix this issue?
That's because a pc doesn't put out as much amperage as a charger so it doesn't charge unless it is idle. Btw I recommend flashing cm 11, it is more up to date and has has improvements made to it that I think aren't added to cm 10.2.
Sent from my LG-P769 using Tapatalk
stunts513 said:
That's because a pc doesn't put out as much amperage as a charger so it doesn't charge unless it is idle. Btw I recommend flashing cm 11, it is more up to date and has has improvements made to it that I think aren't added to cm 10.2.
Sent from my LG-P769 using Tapatalk
Click to expand...
Click to collapse
I see. Where can I find CM11 and how do I flash it? Is it just:
1.put the file into /sdcard
2.reboot into TWRP recovery
3.uh, wipe memory?
4.install CM11
5.reboot
correct me if I'm wrong. I wasn't sure if these are the correct steps because there are a lot of different guides and most of them don't have the same steps.
P.S. Since the kindle only has 8gb, is there a way to free up more memory on the device other than the needed memory space for the os?
You have to factory reset to goto it. Download latest gapps as well. It should be in the development section for kf2 here on xda. Lemme find a link.
Link found!
http://forum.xda-developers.com/showthread.php?t=2388569
As to freeing up space all I can say is delete stuff you don't need. I don't tend to get low on my hd but the again I have a 16 gb model.
Sent from my LG-P769 using Tapatalk
stunts513 said:
You have to factory reset to goto it. Download latest gapps as well. It should be in the development section for kf2 here on xda. Lemme find a link.
Link found!
http://forum.xda-developers.com/showthread.php?t=2388569
As to freeing up space all I can say is delete stuff you don't need. I don't tend to get low on my hd but the again I have a 16 gb model.
Sent from my LG-P769 using Tapatalk
Click to expand...
Click to collapse
"Factory reset to go to?" Also, I should put CM11 zip and gapp in sdcard right?
Yes, what I meant was you have to factory reset before flashing cm 11. Kinda like how Amazon os caused a few problems if you didn't factory reset first, same applies when going to cm 11 from a previous cm os.
Sent from my LG-P769 using Tapatalk
stunts513 said:
Yes, what I meant was you have to factory reset before flashing cm 11. Kinda like how Amazon os caused a few problems if you didn't factory reset first, same applies when going to cm 11 from a previous cm os.
Sent from my LG-P769 using Tapatalk
Click to expand...
Click to collapse
I'm sorry if this sounds stupid but how do I factory reset my device? I've been working on rooting to installing bootloaders and finally at the point of getting android os on it non stop. Brain cells are dying rapidly...
In twrp hit wipe and choose factory reset.
Sent from my LG-P769 using Tapatalk
stunts513 said:
In twrp hit wipe and choose factory reset.
Sent from my LG-P769 using Tapatalk
Click to expand...
Click to collapse
Thank you so much for all the help. Everything went smoothly after your advises.
Update: It was running well for a while until when it ran out of battery and I recharged it, it won't boot into CM anymore. It just boots into TWRP recovery even if I pressed the option to reboot system and normal boot... What should I do?
Hmm could be a few things, try reflashing then ROM and gapps again, I suspect something with the boot IMG or system image is messed up. If it were the boot IMG I would think it would kick into fastboot though. Feel free to do a wipe of system, cache, and dalvik cache before you flash anything(under wipe>advanced).
Sent from my Amazon Tate using Tapatalk
stunts513 said:
Hmm could be a few things, try reflashing then ROM and gapps again, I suspect something with the boot IMG or system image is messed up. If it were the boot IMG I would think it would kick into fastboot though. Feel free to do a wipe of system, cache, and dalvik cache before you flash anything(under wipe>advanced).
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
I wiped what you said and tried to flash the rom and gapp but when booting, it will still boot into TWRP.
I'll briefly explain what I did prior to the issue.
After everything was all set up, I went to see if there were any updates which there was, the nightlies for CM 11 0518. I hit download and after download was complete, I hit the option "install and reboot". After the orange kindle fire logo came up and briefly after, the blue one, it boot into TWRP. I tried to reboot again but still no changes. So I went ahead and did a factory reset and flashed the two zip files again. The devices still boots into TWRP... I have no idea what to do afterwards and here I am requesting assistance from someone who knows things like these better.
Have you tried wiping internal storage? That's a last resort, maybe somehow your selinux xattribs got messed up. A internal storage wipe would clear them. But it will wipe your sdcard area so backup anything you want to keep over adb first.
Sent from my Amazon Tate using Tapatalk
I haven't tried wiping the internal storage yet. How do I backup over adb? Also,since you said this might be a last resort method, if it fails, is there no other way to fix it? Not even restoring back to its out of the box state and start all over again with rooting and installing bootloaders etc?
PS. I don't know if it is related to what you are talking about at all but when I plug it into my computer, it doesn't recognize my kindle fire.
It should be recognized as an adb device when plugged in while in recovery, in which case your could run
Code:
adb pull /sdcard/ sdcard/
And it should pull it, though that syntax may have been a little off, seems like the syntax when pulling a entire directory isn't quite the same as when pushing one if I remember right but I might be wrong.
You could technically try to restore it with kffa by reflashing to stock, but I don't advise doing that just yet because fastboot is rather limited in comparison to twrp recovery. Twrp gives you access to Linux shell commands over adb whereas fastboot does not and gives you simpler commands.
Sent from my Amazon Tate using Tapatalk
stunts513 said:
It should be recognized as an adb device when plugged in while in recovery, in which case your could run
Code:
adb pull /sdcard/ sdcard/
And it should pull it, though that syntax may have been a little off, seems like the syntax when pulling a entire directory isn't quite the same as when pushing one if I remember right but I might be wrong.
You could technically try to restore it with kffa by reflashing to stock, but I don't advise doing that just yet because fastboot is rather limited in comparison to twrp recovery. Twrp gives you access to Linux shell commands over adb whereas fastboot does not and gives you simpler commands.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
So in short, to backup, I can just use a adb pull command?
After that, I am lost. I don't really understand what you are saying...
Yes just type
Code:
adb pull /sdcard/
and it will pull everything into the directory you are in, which gb be messy if you execute from something like kffa because vBulletin I don't believe it will create a folder called Edward and put the rules there, it will just put all the files right there so it's recommended to specify an empty directory at the end if that command. The rest of the other post was about the comparison if fastboot versus and access. Kindle fire first aid could try to restore it but if something screws up along the way you won't be able to have as much flexibility as you do with twrp to try and fix it. This is hard to explain from my phone...
Sent from my LG-P769 using Tapatalk
stunts513 said:
Yes just type
Code:
adb pull /sdcard/
and it will pull everything into the directory you are in, which gb be messy if you execute from something like kffa because vBulletin I don't believe it will create a folder called Edward and put the rules there, it will just put all the files right there so it's recommended to specify an empty directory at the end if that command. The rest of the other post was about the comparison if fastboot versus and access. Kindle fire first aid could try to restore it but if something screws up along the way you won't be able to have as much flexibility as you do with twrp to try and fix it. This is hard to explain from my phone...
Sent from my LG-P769 using Tapatalk
Click to expand...
Click to collapse
So the steps are something like:
Backup with adb
Wipe internal storage
Flash the rom and gapp?
Alternative solution:
Restore the whole device
Repeat the root process
Installing the 2nd bootloader again
Flash rom and gapp
And the rest is if I were to restore the device, it is more flexible to use kindle fire first aide than to use TWRP?