I recently followed the steps on this tutorial All steps were followed in order and the OS boots perfectly as does the included 2.6 TWRP. However, when trying to use TWRP flash some CM10 roms I am never able to. Reading on various forums I discovered that this can usually be fixed by downgrading TWRP to 2.3 or 22.
Problem is that after I flash them onto the Kindle with fastboot (which states that the write was succesful) and reboot through fastboot I can't actually get to the recovery. I turn on the Kindle, hold vol+, the Kindle logo goes from orange to blue but then it always just shows fastboot logo. This is when the fastboot cable isn't even plugged in. I can flash the 2.6 TWRP that was linked from the tutorial back on and IT works fine. But it seems to be the only TWRP img that will work. I'm lost here. Any help or ideas would be appreciated.
(I get the older TWRP files from here. The site says too use FireFireFire for 2.2 but it's my understanding that doing so can brick newer KFHD models.)
qreg66 said:
I recently followed the steps on this tutorial All steps were followed in order and the OS boots perfectly as does the included 2.6 TWRP. However, when trying to use TWRP flash some CM10 roms I am never able to. Reading on various forums I discovered that this can usually be fixed by downgrading TWRP to 2.3 or 22.
Problem is that after I flash them onto the Kindle with fastboot (which states that the write was succesful) and reboot through fastboot I can't actually get to the recovery. I turn on the Kindle, hold vol+, the Kindle logo goes from orange to blue but then it always just shows fastboot logo. This is when the fastboot cable isn't even plugged in. I can flash the 2.6 TWRP that was linked from the tutorial back on and IT works fine. But it seems to be the only TWRP img that will work. I'm lost here. Any help or ideas would be appreciated.
(I get the older TWRP files from here. The site says too use FireFireFire for 2.2 but it's my understanding that doing so can brick newer KFHD models.)
Click to expand...
Click to collapse
First of all, you have to use the TWRP made for your device. Since you are posting in the KFHD forum, I have to assume that is what you have, so here's is the link for it's corresponding TWRP recovery, posted by Hashcode...
http://forum.xda-developers.com/showthread.php?t=2218796
Thanks for the link but I actually do have the working version of TWRP for KFHD7. The problem is it is the only version that will work. I've downloaded older versions of TWRP (2.3.3.0) specifically but none work. For some reason 2.6 is the only one that boots to recovery correctly. However, judging from comments on the web it IS possible to downgrade to older TWRP versions. That is what I need to do but can't.
I have a Kindle Fire HD 1st Gen and I've been trying all day just to get rid of TWRP and get back to stock Amazon ROM. I tried flashing TWRP 2.2.2.1 zip, but apparently anything I flash there's an error and says couldn't find /sdcard/kindleupdate/whatever. I've downloaded KFU 0.9.6 and I have Java and SDK/ADB installed. When I try and install the drivers I get an error with an "X" next to Google (WinUSB). When I hit run.bat it says I'm online, but the device is unknown. My device won't go into fastboot anymore, it will just say on the prompt "kindle fire has been told to boot in fastboot mode" and then after that the kindle reboots and I get stuck with the light blue twrp "kindle fire hd" boot logo. I heard that TWRP 2.6.0.0 sucks because it won't flash the Amazon stock rom and that TWRP 2.2.2.1 can flash the stock rom. So I started searching on how to downgrade from TWRP 2.6.0.0 to 2.2.2.1, but everything involves kindle fire utility and root and all this other stuff that doesn't seem to work. I'm just really frustrated and fed up at this point. Why is it so difficult to get Kindle Fire Utility to install my drivers correctly and get into fastboot?
My main objective is to remove TWRP and just get back to Amazon stock OS so I can sell the darn thing.
Yes, I've searched on youtube and on xda on how to fix the driver issues/fastboot all day, but nothing has worked.
I'd really appreciate it if someone could give me some detailed steps on how to fix all of this. I wish I hadn't installed TWRP at all if I'd known it was this difficult to flash a rom.
jacobjapan said:
I have a Kindle Fire HD 1st Gen and I've been trying all day just to get rid of TWRP and get back to stock Amazon ROM. I tried flashing TWRP 2.2.2.1 zip, but apparently anything I flash there's an error and says couldn't find /sdcard/kindleupdate/whatever. I've downloaded KFU 0.9.6 and I have Java and SDK/ADB installed. When I try and install the drivers I get an error with an "X" next to Google (WinUSB). When I hit run.bat it says I'm online, but the device is unknown. My device won't go into fastboot anymore, it will just say on the prompt "kindle fire has been told to boot in fastboot mode" and then after that the kindle reboots and I get stuck with the light blue twrp "kindle fire hd" boot logo. I heard that TWRP 2.6.0.0 sucks because it won't flash the Amazon stock rom and that TWRP 2.2.2.1 can flash the stock rom. So I started searching on how to downgrade from TWRP 2.6.0.0 to 2.2.2.1, but everything involves kindle fire utility and root and all this other stuff that doesn't seem to work. I'm just really frustrated and fed up at this point. Why is it so difficult to get Kindle Fire Utility to install my drivers correctly and get into fastboot?
My main objective is to remove TWRP and just get back to Amazon stock OS so I can sell the darn thing.
Yes, I've searched on youtube and on xda on how to fix the driver issues/fastboot all day, but nothing has worked.
I'd really appreciate it if someone could give me some detailed steps on how to fix all of this. I wish I hadn't installed TWRP at all if I'd known it was this difficult to flash a rom.
Click to expand...
Click to collapse
HD and 1st gen are different devices, which do you have?
Sent from my DROIDX using Tapatalk
jacobjapan said:
I have a Kindle Fire HD 1st Gen and I've been trying all day just to get rid of TWRP and get back to stock Amazon ROM. I tried flashing TWRP 2.2.2.1 zip, but apparently anything I flash there's an error and says couldn't find /sdcard/kindleupdate/whatever. I've downloaded KFU 0.9.6 and I have Java and SDK/ADB installed. When I try and install the drivers I get an error with an "X" next to Google (WinUSB). When I hit run.bat it says I'm online, but the device is unknown. My device won't go into fastboot anymore, it will just say on the prompt "kindle fire has been told to boot in fastboot mode" and then after that the kindle reboots and I get stuck with the light blue twrp "kindle fire hd" boot logo. I heard that TWRP 2.6.0.0 sucks because it won't flash the Amazon stock rom and that TWRP 2.2.2.1 can flash the stock rom. So I started searching on how to downgrade from TWRP 2.6.0.0 to 2.2.2.1, but everything involves kindle fire utility and root and all this other stuff that doesn't seem to work. I'm just really frustrated and fed up at this point. Why is it so difficult to get Kindle Fire Utility to install my drivers correctly and get into fastboot?
My main objective is to remove TWRP and just get back to Amazon stock OS so I can sell the darn thing.
Yes, I've searched on youtube and on xda on how to fix the driver issues/fastboot all day, but nothing has worked.
I'd really appreciate it if someone could give me some detailed steps on how to fix all of this. I wish I hadn't installed TWRP at all if I'd known it was this difficult to flash a rom.
Click to expand...
Click to collapse
What firmware are you running? This matters because in order to get rid of TWRP, you will have to flash an Amazon image via fastboot to get rid of the second bootloader. This will put you back to stock. Knowing your firmware is imperative or you can flash yourself into a hard brick.
I just got my motorola yesterday. I did quite a few things like unlocking it and rooting it..After my first initial root it worked fine but earlier today i decided to install lollipop. I was using the twrp version 2.7 to install the rom but i realised it wasnt working till i tried a few more time and it finally it. I tried back up my stock 4.4.4 room before i installed my new rom but it failed several times because i think the recovery was faulty to say the least. Anyways my lollipop worked very fine but i notice anytime i restarted the phone it took a long freaking time to restart but it was working normal as usual until i restarted my phone another time and realised i couldn't go past the bootanimation.It takes forever but i never get past it. I then decided to flash the twrp 2.8.0.1. After flashing i realised I could do a backup but it was too late. I tried a few tricks I've always used to get past the bootanimation like mounting the storage but it never shows up on my pc. I also tried side loading the rom using the adb sideload command but it never workedd.it always shows up saying "error: device not found" but when i go back to the bootloader and use the fastbootdevices command it shows up my device. IS there any recovery that will allow me to sucessfully mount my storage or sideload my rom without all this hussle?
rom:TitanPrimeROMv1.3-XT1068-69_RC1
XT1068
Rooted
TWRP 2.0.8.1
Window 8.1 64bit
I already have my mini sdk files
Can you fastboot flash the factory images?
If you can confirm you can get into either bootloader where ADB works or TWRP
i will make you a either a TWRP backup of a clean 4.4.4 GB UK xt1068 restore (boot.img + system folder)
or i will make a ADB mfastboot flashable (in bootloader) of the 4.4.4 GB UK ROM
LMK which you need/prefere?
Hi everyone
i have a motorola x 2nd gen xt1093 us cellular which i believe is in a state of coma cuz there is no OS only access to bootloader and recovery...
heres where it started
1. 5.1 was running perfectly fine but i wanted to convert to pure edition and get os 6.0
2. I unlocked the bootloader and rooted it with kingo
3. I installed twrp 3 and made a backup, it was normal
4. I restored with backup and kept getting stuck at "android is starting, starting apps"
5. I stupidly wiped everything essensially deleting the OS
here is what i have tried so far
1. flashed stock recovery and did factory reset but still cannot go beyond Bootloader Unlocked Warning
2. flashed twrp recovery again, when i enter twrp my devices shows up as media device on computer, tried copying the stock firmware zip file to device but it was too big, adb pushed the stock firmware as update.zip to device, tried installing with twrp but i get the md5 error, is there something wrong with what i downloaded? i downloaded the last one from http://motorolastockrom.blogspot.com/2016/05/moto-g-2nd-gen-stock-firmware-download_32.html does md5 error mean the download is bad? cuz i had resume several times while downloading...
3. sideload option with twrp just keeps trying to start but doesn't
4. flashed philz touch cm recovery, from there tried to sideload but it also failed
5. tried the auto flasher tool by jamesjerss from http://forum.gsmhosting.com/vbb/f78...to-flasher-root-script-v3-1-firmware-1965102/ which actually does seem to install the os from the folder but again i dont go beyond bootloader ulocked warning screen
6. tried RSD lite but it doesnt detect the device even after reinstalling the motorola device manager
please help this stupid
would greatly appreciate
i kept looking around and got the right solution
anyone with a similar experience just to go to http://forum.xda-developers.com/moto-x-2014/help/os-boot-t3384786
that solved my 36hr long misery
Hello guys!
Yesterday I tried to flash the newest Lineage-built to my new G7+ (XT1965-3, bought in Germany via Amazon), but something went wrong and now I'm afraid, I bricked my phone.
It's not my first flash of Lineage, as I did this in the past already on some older Phones (SII, SIII, S5), but it's the first time, that I have a major issue.
So I followed all the steps on the Lineage-Wiki (on Win10).
After flashing the recovery (the lineage-recovery, not TWRP) I wasn't able to enter the recovery-mode, so the phone booted to StockRom. And probably this was the problem: As it didn't react to VolumeDown+Power, I reflashed the recovery a second time. After that the touch-screen is not working any more.
I am able to enter the recovery-mode and I can boot to Stock-Rom, but in both modes the phone does not react to touch, so I can only use the Volume- and Power-Buttons.
Probably I made more mistakes after that: I thought, that a factory-reset would help, but It didn't. I also relocked the bootloader, but as I saw, that it also did not bring any solution, I unlocked it a second time.
Conclusion: I have a brand new phone, with lineage-recovery, an unlocked bootloader but without touch working.
I also tried to flash Lineage, but the sideload got stuck at 47%. So Lineage is not installed and it boots into Stock, where I can not get any further without touch.
Has anyone any idea, what could be the issue and how I can fix it? I would like to start from scratch, but I don't know, what is the exact problem and if i can for example return to stock recovery.
Thank you!
---- EDIT ----
If it helps: I am able to boot TWRP via "fastboot boot twrp-xxx.img". And in TWRP the touch works!
I could flash lineage directly via TWRP from external sd-card, but i am afraid that after that I won't be able to return if something goes wron.
probably your best bet is to go right back to stock using the LMSA tool and starting fresh. I've seen others encounter similar issues on different devices and always the cleaneast solution was just to role back everything and start over.
Thank you so much. With LMSA I managed to restore everything to stock and touch is working!
So I'm going to start from scratch and finally install Lineage.
Is is indicated to use the Lineage-Recovery, as the Lineage-Wiki says, or would it better to use TWRP?
TWRP gives me the option to flash from sd-card, which seems to me better than via sideload.
joglxv said:
Thank you so much. With LMSA I managed to restore everything to stock and touch is working!
So I'm going to start from scratch and finally install Lineage.
Is is indicated to use the Lineage-Recovery, as the Lineage-Wiki says, or would it better to use TWRP?
TWRP gives me the option to flash from sd-card, which seems to me better than via sideload.
Click to expand...
Click to collapse
Glad your back up and running. Take a look in the lineage thread, but it does appear most people lean towards using twrp, shouldnt have an issue with either however.
digitaljeff said:
Glad your back up and running. Take a look in the lineage thread, but it does appear most people lean towards using twrp, shouldnt have an issue with either however.
Click to expand...
Click to collapse
I'm having a similar problem. At first touch was fubar but I was able to return to stock using LMSA and now touch works. I can load TWRP with fastboot and even install a custom ROM and TWRP, but installing any custom ROM results in a boot loop during the finding and installing updates part of the phone setup during first boot. I'm tried Evolution X which I was running previously(for about a month, and then a boot loop started yesterday), PixelOS 10, and AncientOS, but all result in the boot loop on first boot after connecting to wifi.
Fixed
I fixed this somehow by manually flashing the latest stock firmware to slot a, and then extracting the evolution x Rom and manually extracting the IMG files inside and manually fastboot flashing those to slot b. I then set b as the active slot and booted up, patched the boot image with magisk, flashed that, and everything works. Not sure why twrp wouldn't do the trick.
Finally had the time to install Lineage. Now everything works.
I followed the instructions someone posted in the [ROM][OFFICIAL] LineageOS 17.1 [nightlies]-thread and the instructions of the lineage-wiki:
1. fastboot boot TWRP
2. sideload the copy-partitions.zip from lineage-wiki
3. factory reset via TWRP (wipe cache, dalvik and data)
4. sideload lineage
5. reboot bootloader
6. fastboot boot TWRP
7. sideload magisk
8. reboot system
Had a little bootloop the first time rebooting the system, but that was because I forgot to wipe data-partition in step 3. Wiping data and rebooting did it for me.
So I have a working Lineage17.1 with root via Magisk.
Thank you for the help!
I had exactly the same problem like you had. Bought a brand new moto g7 plus and after recovery flash, Touchscreen was not working anymore. I could manage to go back to the bootloader, sideloaded TWRP, but side loading lineage worked for me then. It seemed to be stuck on 47 percent, but this seems to be a normal issue, the file was there and after installing, touchscreen worked normally.