Hello All, I flashed the V2 version of the JB Rom on my CDMA GNex and it was working great until I rebooted my phone. Now It is bootlooping.
I can boot into recovery
This is what I have done:
Battery/Sim Card Pull
Catch Wipe/Factory data reset
Tried to Nanodroid back to an older rom
Tried to install AOKP back
All lead to bootlooping
I am sorry if this is has been addressed but any help would be greatly appreciated.
I got it to boot. After many tries it just turned on. Go figure.
How did you exactly get it to work. You said after many tries it just worked. What kind of "tries" did you do because I'm having the same issue? I tried nandroid restore, full system wipe, reinstall of AOKP build40, etc. It keeps bootlooping. Help
If all else fails, Nexus Factory Images will always be available.
Its been so long since I done the fastboot and stock 4.0.4. I'm afraid I have forgotten. I looked at that page and downloaded the stock image but I'm not sure how to use the fastboot and adb commands anymore.
elusiveaura said:
Its been so long since I done the fastboot and stock 4.0.4. I'm afraid I have forgotten. I looked at that page and downloaded the stock image but I'm not sure how to use the fastboot and adb commands anymore.
Click to expand...
Click to collapse
Well, if you have ADB and fastboot installed, that's a good start. All you need to do is unzip the file and place it where your terminal will recognize it. Then turn on USB debugging on in developer settings, then boot into your boot loader (Power + Volume Up + Volume Down) and type in "sh flash-all.sh" or you can do it manually, "fastboot flash recovery recovery.img, fastboot flash bootloader bootloader.img" etc... This will wipe all your data, including your SD card.
Trying to go to 100% back to stock for resale. I downloaded the 6.3.1 bin file and renamed to update.zip and installed with TWRP. Everything seemed to go fine but after rebooting I get a constant android.process.acore force close and it just keeps rebooting every 15 seconds. It wont stay up long enough to get through the menus to do a factory reset and KFU shows its ONLINE with a 4000 boot status but every time I try to install permanent root or install TWRP or any other recovery it says failed to copy permission denied...
Not sure what to do here. Every time I try to do anything with KFU it tells me the "directory data/local.fbmode: not found". I also have the problem that I have 2 more Kindle Fires I need to restore to stock but I don't really dare try anything after this for fear the same thing might happen. Any friendly advice out there?
Help?
GrandMasterB; said:
data/local.fbmode
Click to expand...
Click to collapse
Is that a typo or is that how you're entering the command? Also, did you make sure to push fbmode to /data/local before trying to execute?
That's using Kindle Fire Utility. I'm not entering any commands myself, just menu selections. So is that in relation to the" permission denied" error I'm getting first? Is that not allowing it to push the fbmode file? Why would I get a permission denied all the sudden? It has always worked fine on all 3 of our Fires.
GrandMasterB said:
That's using Kindle Fire Utility. I'm not entering any commands myself, just menu selections. So is that in relation to the" permission denied" error I'm getting first? Is that not allowing it to push the fbmode file? Why would I get a permission denied all the sudden? It has always worked fine on all 3 of our Fires.
Click to expand...
Click to collapse
I should have known...silly me.
No. What I'm saying is, in your previous message, the string of text that you posted: "directory data/local.fbmode: not found" is incorrect...Did you copy and paste that exactly as is or did you type it? The answer could mean a completely different solution.
Sorry, that's a typo on my part. I'll copy and paste exactly what i am seeing below.
***********************************************
* Recovery Installer *
***********************************************
***********************************************
* WARNING *
***********************************************
Make sure to read each screen carefully!
Make sure to follow instructions given to you!
twrp.img has been found.
***********************************************
* NOTICE *
***********************************************
Installing TWRP...
If we get stuck here for awhile, power the kindle on and off a few times.
You should also check device manager for "kindle" If so, rerun the driver
installer that came packaged with KFU.
***********************************************
* Activating Fastboot (4002) *
***********************************************
failed to copy 'files\fbmode' to '/data/local/fbmode': Permission denied
Unable to chmod /data/local/fbmode: No such file or directory
/data/local/fbmode: not found
The kindle has been told to reboot in Fastboot Mode.
< waiting for device >
You're actually very lucky because you are able to connect to the kindle using adb, which when I had this problem was completely out of the question. I would try to send the commands manually using command prompt. You may not be able to do that unless you're in fastboot mode though which can be done by (I don't have a windows PC with me at the moment to check this but I believe that is) option 1 in KFU for bootmodes and then option 2 for fastboot. You're going to need to download KindleADB which I just so happen to have available on my mediafire account: http://www.mediafire.com/download.php?1fb30q3wqf95b3i
I would also recommend downloading this TWRP.img which is TWRP 2.1.1 rather than the most recent 2.2.0 which has seemed to cause some issues recently during flashing.: http://www.mediafire.com/download.php?f3sr33214229pr2 and place that in your KindleADB folder after you have downloaded and extracted it. and this is the file for fff v.1.4a which is the current version as far as I know. http://www.mediafire.com/?el5lxqvoasa8uer also place that file into your KindleADB folder and rename it to fff.bin (not fff.bin.bin).
For convenience, place the KindleADB folder on the root of your C: Drive (not in any folders or anything)
To flash TWRP use these commands one line at a time:
Code:
cd /
cd KindleADB
fastboot flash recovery twrp.img
To flash fff you should already be in the KindleADB directory so you can just enter these commands:
Code:
fastboot flash bootloader fff.bin
fastboot reboot
Please understand though that even though I have a lot of experience with android and Kindle Fire and I am fairly confident that this should get you in the right direction I would really appreciate if someone else could confirm that this would work before you try it. (I'm actually more worried about getting you stuck in fastboot than anything else). If this doesn't work you're probably going to need to get a factory cable
After you have TWRP and FFF reflashed to your device, you want to place the update.zip on your SD if it isn't still there and make sure you do a factory reset and wipe EVERYTHING (DATA, CACHE, SYSTEM, DALVIK) before you flash it, that is how you wound up in this situation to begin with. With your other devices which already have twrp and fff installed, that is all you will have to do.
nschiwy said:
You're actually very lucky because you are able to connect to the kindle using adb, which when I had this problem was completely out of the question. I would try to send the commands manually using command prompt. You may not be able to do that unless you're in fastboot mode though which can be done by (I don't have a windows PC with me at the moment to check this but I believe that is) option 1 in KFU for bootmodes and then option 2 for fastboot. You're going to need to download KindleADB which I just so happen to have available on my mediafire account: http://www.mediafire.com/download.php?1fb30q3wqf95b3i
I would also recommend downloading this TWRP.img which is TWRP 2.1.1 rather than the most recent 2.2.0 which has seemed to cause some issues recently during flashing.: http://www.mediafire.com/download.php?f3sr33214229pr2 and place that in your KindleADB folder after you have downloaded and extracted it. and this is the file for fff v.1.4a which is the current version as far as I know. http://www.mediafire.com/?el5lxqvoasa8uer also place that file into your KindleADB folder and rename it to fff.bin (not fff.bin.bin).
For convenience, place the KindleADB folder on the root of your C: Drive (not in any folders or anything)
To flash TWRP use these commands one line at a time:
Code:
cd /
cd KindleADB
fastboot flash recovery twrp.img
To flash fff you should already be in the KindleADB directory so you can just enter these commands:
Code:
fastboot flash bootloader fff.bin
fastboot reboot
Please understand though that even though I have a lot of experience with android and Kindle Fire and I am fairly confident that this should get you in the right direction I would really appreciate if someone else could confirm that this would work before you try it. (I'm actually more worried about getting you stuck in fastboot than anything else). If this doesn't work you're probably going to need to get a factory cable
After you have TWRP and FFF reflashed to your device, you want to place the update.zip on your SD if it isn't still there and make sure you do a factory reset and wipe EVERYTHING (DATA, CACHE, SYSTEM, DALVIK) before you flash it, that is how you wound up in this situation to begin with. With your other devices which already have twrp and fff installed, that is all you will have to do.
Click to expand...
Click to collapse
Thank you. This is exactly what I was looking for. BUT right before you posted this I was finally able to get through the menu and initiate a factory reset that was able to finish and reboot itself before it rebooted unexpectedly again. Every time I tried it before I would get a reboot before it was finished with the factory reset.
Anyways, its back up and running fine now. Connected to my wifi and downloading some apps now. I do have a question though, I did a factory reset and wiped dalvic/cache before installing the update.zip and I wiped dalvic/cache after the install before rebooting and I had this problem. I did not wipe SYSTEM because the guide I followed for back to stock didn't say to wipe system and also because many months ago I was switching ROMs and I wiped everything including stystem (like I do on my Galaxy Nexus) before the install and it wouldn't boot past the FIRE logo. Luckily at that time I still had TWRP installed and was able to easily fix it. But you are saying that I SHOULD wipe system on the other 2 Kindle Fires before I install the update.zip? Just want to make sure I don't have to go through this 2 more times today...
Thanks again for the helps guy. I am extremely thankful.
GrandMasterB said:
Thank you. This is exactly what I was looking for. BUT right before you posted this I was finally able to get through the menu and initiate a factory reset that was able to finish and reboot itself before it rebooted unexpectedly again. Every time I tried it before I would get a reboot before it was finished with the factory reset.
Anyways, its back up and running fine now. Connected to my wifi and downloading some apps now. I do have a question though, I did a factory reset and wiped dalvic/cache before installing the update.zip and I wiped dalvic/cache after the install before rebooting and I had this problem. I did not wipe SYSTEM because the guide I followed for back to stock didn't say to wipe system and also because many months ago I was switching ROMs and I wiped everything including stystem (like I do on my Galaxy Nexus) before the install and it wouldn't boot past the FIRE logo. Luckily at that time I still had TWRP installed and was able to easily fix it. But you are saying that I SHOULD wipe system on the other 2 Kindle Fires before I install the update.zip? Just want to make sure I don't have to go through this 2 more times today...
Thanks again for the helps guy. I am extremely thankful.
Click to expand...
Click to collapse
All you need to do is run the factory reset from TWRP... I know people suggest you wipe the cache and dalvik cache as well, but if you pay attention to the output from doing a factory reset, you'll see it's all inclusive. A factory reset will reformat /data and /cache. Wiping the cache reformats /cache. Wiping the dalvik cache erases /data/dalvik-cache and /cache/dalvik-cache. If redundancy matters to you, it won't hurt to do it all, but you absolutely must perform a factory reset.
I'm not calling you a liar, but despite your claims, I suspect you missed the factory reset part and the /data partition wasn't wiped clean. This is backed up by the fact that the factory reset from the stock system software fixed things for you. The two are pretty much the same, but the stock software will also wipe the /sdcard clean.
As for wiping the system, you don't need to do that before returning to stock. Essentially all ROM/stock zips include a line like this in their updater-script...
format("ext4", "EMMC", "/dev/block/platform/mmci-omap-hs.1/by-name/system");
The above is from the 6.3.1 update zip archive. That takes care of making sure the system is clear of any files before anything else gets written to it. Again... it's not going to hurt if you take that extra step, but it's unnecessary.
That concludes my lecture on everything you never cared to know about factory reset and wiping the system.
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.
Hi there,
I stupidly downloaded the latest SlimKat .zip onto my nexus 7, but with the file for my i9300, so obviously it does not boot.
Now, I haven't done this in a while apart from a toolkit, but is there a way to push the file via adb? I can boot into twrp and go Advanced, Adb sideload, but then it doesn't seem to 'complete', and I can't find the device from my computer, despite it showing in fastboot when I am in that mode; it does not in adb.
I know I can wipe to factory image, will that COMPLETELY wipe my device? As in, all my downloaded files, titanium backup etc.? Or just /data? I'd like to backup my internal sdcard if at all possible.
To sum up, wiped /system, but no .zip currently on device. Can I remedy this without losing pictures/titanium backup?
Thank you,
Habylab
habylab said:
Hi there,
I stupidly downloaded the latest SlimKat .zip onto my nexus 7, but with the file for my i9300, so obviously it does not boot.
Now, I haven't done this in a while apart from a toolkit, but is there a way to push the file via adb? I can boot into twrp and go Advanced, Adb sideload, but then it doesn't seem to 'complete', and I can't find the device from my computer, despite it showing in fastboot when I am in that mode; it does not in adb.
I know I can wipe to factory image, will that COMPLETELY wipe my device? As in, all my downloaded files, titanium backup etc.? Or just /data? I'd like to backup my internal sdcard if at all possible.
To sum up, wiped /system, but no .zip currently on device. Can I remedy this without losing pictures/titanium backup?
Thank you,
Habylab
Click to expand...
Click to collapse
A factory reset wipes the data and cache, any changes made to the system will still be there after a factory reset. Flashing the complete factory image will also wipe everything. The userdata.img inside the factory image is what wipes everything. You could flash all the images inside the factory image separately except for the userdata image and your data will stay intact.
If you can see it in fastboot just fastboot flash the system.img and the boot.img. Get the "correct" system.img and boot.img (you have to extract the images from a factory image) and put them inside the platform-tools folder of the sdk, manually put your device in fastboot, plug it in to the computer, shift-right click from inside the platform-tools folder, choose "Open command window here," type fastboot devices and you should see your device, type fastboot flash boot boot.img, hit enter then fastboot flash system system.img hit enter. Type fastboot reboot hit enter and your device should reboot normally! All of your data will still be intact. This might be useful 15 seconds ADB Installer v1.3, I personally have the full sdk installed but I did try the ADB installer on my brother's laptop a few months ago.
I have a Redmi note 5 pro, I was using a custom rom, but was experiencing some bugs so I decided to put another ROM in it, I already did this lots and lots of times and I always followed this procedure:
Reboot into recovery(TWRP), Transfer the ROM, GAPPS and MAGISK to the phone > wipe Cache, Dalvik Cache and System. > Install ROM, GAPPS > WIPE DATA > FLASH MAGISK > WIPE INTERNAL STORAGE > DONE.
Never had a problem, but this time idiot me was doing this at 5am, dying to go to sleep, and I started by wiping everything, without moving the files to the phone beforehand.
Well, apparently once you wipe the system the phone internal storage doesn't show up in the computer anymore, I didn't know that. I always thought that since TWRP was MTP compatible, it would always be a thing, welp.
I then thought of 2 solutions to this: I remember ADB sideload was a thing, and I also could buy a memory card, put the files there, and just load into the phone, bam.
Since it was 5am the memory card would have to wait, and I couldn't get ADB sideload to work, it would't recognize my device for some reason.
I then remembered fastboot existed, and weirdly enough my phone was recognized as a fastboot device on my pc. So I went, downloaded the correct fastboot rom from xiaomi website and tried flashing it using a official tool that they provide, and then tried again using a third party tool that also does something similar.
I was getting a few errors, and then in one of my restarts the phone just stopped showing stuff. It would still turn on, but it's just a black screen, no icons, no recovery, no fastboot, nothing. The battery icon when I put the charge in is the only thing that still shows up.
I already know the answer to this, but hope is the last thing to die, so, is it irreparably ****ed up ? Is there anything I can do? Is it even worth it sending it to repair services? (It wouldn't be Xiaomi, they don't have stores here in my country)
EDL
i´m pretty sure that at least EDL Method works, many tutorials on youtube. Search for "redmi note 5 edl method"
Try to find something about edl mode as mentioned above. It might be your last chance to revive this phone, but you need to take the back cover to be able to find the edl pins and short them. There are many guides on the internet as well as on youtube. But before you try to do that, first try to enter the fastboot mode somehow, you may succeed, so tinker with it for couple of minutes.
As you are able to boot it into Fastboot mode,
1. boot into fastboot mode
2. boot into recovery using "fastboot boot twrp-name.img"
You should be able to see your device in PC after booting in TWRP
3. format data.
(If you are not able to see Internal storage of your RN5 in PC then,
1.boot in fastboot from twrp.
2. boot in twrp again using command above)
4. then copy your files and flash them.
5. wipe cache/dalvik
6. reboot
rasik107 said:
As you are able to boot it into Fastboot mode,
1. boot into fastboot mode
2. boot into recovery using "fastboot boot twrp-name.img"
You should be able to see your device in PC after booting in TWRP
3. format data.
(If you are not able to see Internal storage of your RN5 in PC then,
1.boot in fastboot from twrp.
2. boot in twrp again using command above)
4. then copy your files and flash them.
5. wipe cache/dalvik
6. reboot
Click to expand...
Click to collapse
As I said in the post
and then in one of my restarts the phone just stopped showing stuff. It would still turn on, but it's just a black screen, no icons, no recovery, no fastboot, nothing.
Click to expand...
Click to collapse
I can't boot into fastboot. Right now my only chance seem to be EDL mode, I'll give it a try as soon as I can.
Vitorvlv said:
As I said in the post
I can't boot into fastboot. Right now my only chance seem to be EDL mode, I'll give it a try as soon as I can.
Click to expand...
Click to collapse
And then dont forget to post what happened..
Whether you fixed your phone or not..
Is she dead or not... :angel:
I cant handle the suspense, you are holding...
Sreehul R said:
And then dont forget to post what happened..
Whether you fixed your phone or not..
Is she dead or not... :angel:
I cant handle the suspense, you are holding...
Click to expand...
Click to collapse
she or he posted as soon as she / he can do.