I have been reading and have found nothing, is it possible to use adb to flash a backup i created with twrp before my kindle was bricked?
simply NO - you'll have to reinstall twrp
Related
[Q] I put TWRP on my Kindle Fire to make a backup, after completing the backup I transferred it to my computer. How do I remove TWRP from showing up at boot and keep all my stuff on the device?
Thanks,
C. Condon
I assume you are talking about the Yellow Triangle? That is not TWRP... that is FireFireFire... and it is displayed every time you boot.
You don't uninstall it, you leave it.
There are ways to restore the factory boot and recovery partitions but I would have to ask why you would want to do this. If you removed twrp and firefirefire you wouldn't be able to restore your backup if you had a problem.
You can do that. Just flash stock 6.2.1 firmware from amazon site and firefirefire, twrp will be deleted.
Thanks for the help
I did a restore using TWRP, I flashed back to stock root, no rom or anything. Restore went fine, but my device rebooted and started to do an update, I don't know what it was updating but I tried to stop it by turning it off. I shut it off, restarted and it continued to install an update, I got the KF splash screen. It finished and my KF loaded up fine, still have Burrito-Root and SU. But for some reason that Fire logo doesn't come up anymore, so I can't get into TWRP recovery? How did I lose recovery if I just restored a backup?
Do I have TWRP just need to fix something? Or do I have install TWRP all over again? If so, what's the easiest way to do that?
Thanks guys...
I would say using a gscript is probably the easiest way. Check out the dev section.
Sent from my Kindle Fire using xda premium
Sounds like ur backup was not 6.2.2 and it flashed an update after u restored it? Just reinstall fff n twrp (or cwm lol)
Sent from my Kindle Fire using xda premium
I just returned my other fire back to non root by just putting 6.2.2 back onto it. In the process rebooted fff uninstalled and so did twrp. Just reroot reinstall fff and then reinstall twrp.
Sent from my Kindle Fire using Tapatalk
Thanks guys. FireFire was still installed but didnt show. I had to use KindleFireTools and just flashed TWRP again.
Being a total noob, I am happy to report that my KF1 is now running CM10 (Android 4.1.2):
http://forum.xda-developers.com/showthread.php?t=1778010
[ROM] CM10/SGT7 for the Kindle Fire [20121224] [Linaro]
Some problems I ran into:
1) Installed Kindle Fire Utility (KFU) and drivers. KFU could not find Kindle Fire.
SOLUTION: Make sure Kindle Fire is disconnected from computer before installing drivers. If necessary, completely uninstall drivers, restart system, then re-install. Afterwards, you can connect your Kindle and it will should up on KFU.
2) Installed a custom rom using TWRP. Upon reboot, rom was stuck at loading screen.
SOLUTION: I didn't do a factory reset. In the Wipe menu on TWRP, make sure you do a Factory Reset, Cache Wipe, Davlik Cache Wipe, and System Wipe.
3) AOSS Keyboard kept force closing.
SOLUTION: Make sure you're running the correct version of Google Apps (GAPPS). I was installing GAPPS 4.2.x. It should have been 4.1.x for this particular rom.
I also recommend not restoring system data from titanium backup when changing roms. I did that when downgrading from a cm10.1 rom to a cm10 rom and it just got stuck at the cm splash screen until I did a factory reset.
Sent from my Amazon Kindle Fire using Tapatalk HD
Robb Flynn said:
Being a total noob, I am happy to report that my KF1 is now running CM10 (Android 4.1.2):
http://forum.xda-developers.com/showthread.php?t=1778010
[ROM] CM10/SGT7 for the Kindle Fire [20121224] [Linaro]
Some problems I ran into:
1) Installed Kindle Fire Utility (KFU) and drivers. KFU could not find Kindle Fire.
SOLUTION: Make sure Kindle Fire is disconnected from computer before installing drivers. If necessary, completely uninstall drivers, restart system, then re-install. Afterwards, you can connect your Kindle and it will should up on KFU.
2) Installed a custom rom using TWRP. Upon reboot, rom was stuck at loading screen.
SOLUTION: I didn't do a factory reset. In the Wipe menu on TWRP, make sure you do a Factory Reset, Cache Wipe, Davlik Cache Wipe, and System Wipe.
3) AOSS Keyboard kept force closing.
SOLUTION: Make sure you're running the correct version of Google Apps (GAPPS). I was installing GAPPS 4.2.x. It should have been 4.1.x for this particular rom.
Click to expand...
Click to collapse
Good job. Glad it worked out for you.
A note about solution #1:
The problem in this case isn't so much the drivers, as many (including I) had once believed. The problem is the stock bootloader itself. From what I understand, fastboot shouldn't require drivers to work properly anyway. I'm guessing, the stock bootloader (Kindle Fire logo) isn't the same bootloader the device had in it's infancy and this is causing some very confusing problems for a lot of new users.
For one, the command "fastboot devices" will never show a device connected in fastboot mode. And, when you send any other fastboot command, you'll see it hang at "<waiting for device>", indefinitely. * The solution for this, is to send the command with the device shut down completely and then turn the device back on (this is why it worked in your case). Then, as the device boots up again, fastboot will detect the device and continue with whatever process was waiting for the device. KFU uses the same fastboot commands to check if a device is connected (fastboot devices) and install FFF and TWRP (fastboot flash...), therefore the solution is still the same.
That's not to say the bootloader is always the problem. The stock boot animation can easily be confused with the stock bootloader splash screen, but that's another subject altogether.
I hope this helps to clear up some confusion as to what is actually happening when fastboot doesn't seem to be working properly.
Once you've installed your apps and got your KF running smoothly with your new ROM, reboot into TWRP and do a backup. I usually backup Data only. I keep the ROM and the GAPPS on my KF's SDcard so if I ever need to reinstall, I can do a clean wipe (the caches, factory reset, system), install the ROM and GAPPS, and restore my Data from backup.
I also recommend backing up Data regularly and testing your Data backups.
I strongly recommend twa_priv's CM10.1 rom. I use it 2 Kindle Fire's that my kids have.
Today he added hashcode's new Kernal tweaks, and the battery drain in standby (deep sleep) is unbelievable now! My daughter's Fire is getting about -15 drain when sleeping now, it was getting about -35 before todays update, and honestly I thought that was pretty good. Now ita amazing.
(I use battery monitor widget from 3c to check battery drain)
Hello all,
I have a shiny new Sprint LG G2 that I want to flash with CM11. I haven't done anything to it yet; it's currently installing the ZV8 OTA update (and has been for about half an hour, but that's another story).
Before I flash it with anything, I want to make double sure that I can restore it to stock (or to stock post-OTA). Unfortunately, I run Ubuntu, and the only return-to-stock tutorials I have seen are like this one and require hacking up a copy of LG's Windows-only "LG Flash Tool".
I have found a procedure to recover from a few different kinds of soft-bricking, including trying to do an OTA on a non-stock recovery, or having messed up one's boot partitions so the secure boot checks do not pass. It appears that when the phone is in "qhsusb_bulk" mode, Ubuntu will automatically (with no additional drivers) detect it as a 36-partition block device, whereupon you can just dd things to and from all of the various partitions on the phone.
1. If were to get my phone into "qhsusb_bulk" mode, could I just dd all 36 partitions to their own image files from the host PC, and restore them later by doing the reverse?
2. How do I put a Sprint G2 variant (LS980) into "qhsusb_bulk" mode? Do I have to screw up something so that it will fail to boot?
3. Is there any documentation I can read on "qhsusb_bulk" mode? Is it possible to brick the phone so badly by overwriting the wrong partition that I can't get into it to fix it?
4. Is there some other equivalent of the LG Flash Tool process for Linux?
Thanks in advance!
You should just install custom recovery, backup stock ROM, factory reset everything, Install CM11 & GAPPS, and move the stock backup to your laptop or keep on your phone?
That's what I did when i first got my phone, I right away went home backed up stock ROM and flash Paranoid Android. I just went back to stock yesterday from my backup and it's working great
I'm running Ubuntu 13.10 and if anything goes wrong, meaning if you get into a bootloop or recoveryloop, I always adb sideload a ROM and get it up and running again.
xxxrichievxxx said:
You should just install custom recovery, backup stock ROM, factory reset everything, Install CM11 & GAPPS, and move the stock backup to your laptop or keep on your phone?
That's what I did when i first got my phone, I right away went home backed up stock ROM and flash Paranoid Android. I just went back to stock yesterday from my backup and it's working great
I'm running Ubuntu 13.10 and if anything goes wrong, meaning if you get into a bootloop or recoveryloop, I always adb sideload a ROM and get it up and running again.
Click to expand...
Click to collapse
That sounds like it will cover everything but the recovery partition.
How is the stock recovery image backed up in this method, if you overwrite it with the custom recovery as the first step? Is it not backed up? Does the factory reset somehow restore it?
OK, I've done some more experimenting and poking around on IRC, and I have found this (for Sprint models, because that's what I have):
1. ioroot15 can temporarily root the device, without replacing anythig or even instaling su. Just ctrl+c it at the prompt.
2. Once that's done, "adb shell" gives you root, so you can dd the stock recovery (or anything else) from its partition to an .img, and dd TWRP over it like this:
Code:
cd /sdcard
dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=stock-recovery.img
dd if=openrecovery-twrp-2.6.3.2-g2spr.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
3. If you don't even want to make your own backup the Sprint ZV8 stock partition images are all available for download. I can't tell you where they are, because I am apparently not allowed to post links. So if you ever need them you will have to cry and curse the forum admins. They can be flashed back with the temp-root method.
So, you can back up your recovery, flash a custom recovery, backup the rest of your system, and keep both those backups. To return to stock, restore your backup with your custom recovery, then do the temp-root and restore the stock recovery.
I used this method in rooting my device
http://forum.xda-developers.com/android/development/guide-lenovo-a3500-h-t2879208
But now i cant install any sytock update.zip it give me error 7 in cwm and installation abborted
How to restore the stock recovery?