Yes, many would say running CyanogenMod 12.1 and having the latest CM Recovery would be great, I did too, and i soft bricked my beloved KFHD7 (tate) :crying: . Now, I will be looking into this, but I don't think CanogenMod makes the recoveries custom for our device :crying: . in either case, only trust CWM, TWRP, or Philz for our device. (I personally use TWRP "all day, every day") Just a warning to crack flashers like myself who flash anything and everything available on there device (I've flashed every rom on this forum except for a few recent 5.1.1 roms) :laugh: .
I have to agree. Wish you had posted this before I flashed it to mine now I'm waiting on a fastboot cable so I can get mine back up and running lol. I think on the one I flashed it didn't even have the option to restore from a backup
Sent from my HTC One_M8 using XDA Free mobile app
twfs said:
I have to agree. Wish you had posted this before I flashed it to mine now I'm waiting on a fastboot cable so I can get mine back up and running lol. I think on the one I flashed it didn't even have the option to restore from a backup
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah, I just got a 8.9 kindle, (already bricked :'( ) but it was a real bummer when it just kept rebooting into CM recovery. My advice: keep a flash able TWRP zip handy, just in case you get there again, also, I don't think you need a cable, the "reboot to boot loader" option lets you boot into fast boot. And I think a normal cable works once your in it (so long as you have to right drivers).
Sent from my iPhone using Tapatalk
MeowDude said:
Yeah, I just got a 8.9 kindle, (already bricked :'( ) but it was a real bummer when it just kept rebooting into CM recovery. My advice: keep a flash able TWRP zip handy, just in case you get there again, also, I don't think you need a cable, the "reboot to boot loader" option lets you boot into fast boot. And I think a normal cable works once your in it (so long as you have to right drivers).
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Try running fastboot oem idme bootmode 4000 while the kindle initially powers up (add in -i 0x1949 if needed) to reset the boot mode. After that, it shouldn't stick to booting into recovery.
monster1612 said:
Try running fastboot oem idme bootmode 4000 while the kindle initially powers up (add in -i 0x1949 if needed) to reset the boot mode. After that, it shouldn't stick to booting into recovery.
Click to expand...
Click to collapse
I will when I get the chance, thanks.
Sent from my iPhone using Tapatalk
Related
I finally managed to unbrick my KF and reroot it a few weeks ago only for amazon to come out with 6.2.3 or whatever the new version is and of course it unrooted it.
I have a MacBook Pro so I decided to use BreakDroid to reroot my KF.
Well in the process of doing so it installed CWM which has turned into a total monster.
Now my KF will only load to either the Yellow Triangle screen or the CWM-based Recovery menu screen. I keep trying to boot it out of that mode by using
cd /Users/macuser/android-sdk-macosx/tools
./fastboot-mac -i 0x1949 oem idme bootmode 5002
but that just seems to take me to the red CWM menu screen.
Does anybody know how I can get CWM off of my KF for GOOD?
I swear if I see that red menu or that yellow triangle again I'm going to throw it across the room.
Help a girl out?
To change to normal boot, use 4000 or use the following fast boot commands:
fastboot -i 0x1949 oem idme bootmode 4000
or
fastboot oem idme bootmode 4000
then fastboot reboot
Sent from my Amazon Kindle Fire using Tapatalk
Didn't Work
I tried that...it didn't work either. It just brought me back to that stupid yellow triangle.
Since you have cwm, restore your backup or flash your desirable ROM.
Sent from my Amazon Kindle Fire using Tapatalk
=D
You know I actually decided to do that on my own before I read your post and it totally worked! Thank you for giving me the advice though.
I am glad you got your KF working
Sent from my Amazon Kindle Fire using Tapatalk
I tried this but it didn't seem to work for me.
One problem is when I renamed the update to "update.zip" it doesnt show up as a file I can install in TWRP. However, when I actually .zip the update then it shows up.
I used install and it says "installing" with a progress bar, but when I reboot it goes right back into TWRP recovery mode.
My kindle is fully accessible through Kindle Fire Utility, but it will only stay in recovery mode, If I try to put it back into normal mode it gives a message "The system cannot find the drive specified".
I think at some point I deleted the system files using TWRP assuming I could just flash them back. I'm guessing I was wrong at this point.
Any help would be appreciated.
all u had to do, was tap reboot system on cwm. its not twrp, it ain't broken. no adb boot mode changes. just reboot lol
Sent from my HTC Glacier using xda premium
Hi I'm new here but lately I'e been reading a lot of the posts about rooting and installing roms on a kindle fire since I recently got one. I got cyanogen 9 on it (I think anyways) and used twrp for it. All went well but when I tried to go back to twrp, it loaded CW. Could anyone point me in the right direction to get twrp back on since I felt more comfortable with that?
Thanks for any help I can get
Get your command prompt ready and make sure both TWRP and fastboot are in your present working directory.
You can use CWM to reboot into fastboot mode or do it manually, then...
fastboot -i 0x1949 boot twrp.img
Where "twrp" would be the exact name of the recovery.img you want to flash.
After it's installed...
fastboot -i 0x1949 oem idme bootmode 4000
...to get out of fastboot. Then reboot.
Sent from my Amazon Kindle Fire using xda premium
Just follow the direction in the following thread to install TWRP 2.0 or 2.1. Please note you need to select the KF as a device to download the correct version
http://forum.xda-developers.com/showthread.php?p=24687315
Sent from my Amazon Kindle Fire using Tapatalk 2
ammubarak said:
Just follow the direction in the following thread to install TWRP 2.0 or 2.1. Please note you need to select the KF as a device to download the correct version
http://forum.xda-developers.com/showthread.php?p=24687315
Sent from my Amazon Kindle Fire using Tapatalk 2
Click to expand...
Click to collapse
I did that but when i rebooted it went to CW again...
@soupmagnet: am i supposed to copy/paste that stuff in my cmd?
LVMickey said:
I did that but when i rebooted it went to CW again...
@soupmagnet: am i supposed to copy/paste that stuff in my cmd?
Click to expand...
Click to collapse
Or type it, but yes. You need to be in fastboot mode first (stuck at boot screen). CWM has an option to reboot into fastboot.
[Edit:] Not to insult your intelligence, but make sure your device is plugged into the computer first
Sent from my Amazon Kindle Fire using xda premium
http://forum.xda-developers.com/showpost.php?p=24691872&postcount=4
http://forum.xda-developers.com/showpost.php?p=24720976&postcount=11
http://forum.xda-developers.com/showpost.php?p=24732291&postcount=1298
http://forum.xda-developers.com/showpost.php?p=24748001&postcount=1317
LVMickey said:
I did that but when i rebooted it went to CW again...
@soupmagnet: am i supposed to copy/paste that stuff in my cmd?
Click to expand...
Click to collapse
After you download the image file, do the following
[ how to flash/install ]
reboot into fastboot mode and enter the command:
fastboot flash recovery filename.img
Then you need to change the mode to normal boot. I think that you did fastboot boot filename.img . You need to flash the file into recovery. Good luck
Sent from my Amazon Kindle Fire using Tapatalk 2
Hi, when android 4.3 launched, i went back to 4.2 complete stock with no custom recovery and locked the bootloader to receive the update OTA.
Now I have 4.3 with Z20i bootloader and when i flash cwm, phone gets stuck on the GOOGLE splashscreen and after 1/2 hour moves to the X screen and gets stuck there. Recovery does not works. I had to flash stock recovery and wipe all data to make it work. when trying
Code:
fastboot boot recovery.img (recovery-clockworkmod-6.0.3.6-mako.img)
, it shows a black screen after google and then reboots in safemode whenever any button is pushed.
RohMish said:
Hi, when android 4.3 launched, i went back to 4.2 complete stock with no custom recovery and locked the bootloader to receive the update OTA.
Now I have 4.3 with Z20i bootloader and when i flash cwm, phone gets stuck on the GOOGLE splashscreen and after 1/2 hour moves to the X screen and gets stuck there. Recovery does not works. I had to flash stock recovery and wipe all data to make it work. when trying
Code:
fastboot boot recovery.img (recovery-clockworkmod-6.0.3.6-mako.img)
, it shows a black screen after google and then reboots in safemode whenever any button is pushed.
Click to expand...
Click to collapse
Normally you have to execute
Code:
fastboot flash recovery recovery.img
Try it with the latest cwm image
Sent from my Nexus 4 running Android 4.2.2
mihahn said:
Normally you have to execute
Code:
fastboot flash recovery recovery.img
Try it with the latest cwm image
Sent from my Nexus 4 running Android 4.2.2
Click to expand...
Click to collapse
flash installs the recovery but nothing works. i have to do a wipe and install the stock recovery to boot it. i wrote it on top
Put your device on the bootloader menu and use this: https://developers.google.com/android/nexus/images#occamjwr66v
Always use the stock bootloader like pretty much everyone who owns the Nexus 4.
Sent from my Nexus 4 using Tapatalk 4
andyabc said:
Put your device on the bootloader menu and use this: https://developers.google.com/android/nexus/images#occamjwr66v
Always use the stock bootloader like pretty much everyone who owns the Nexus 4.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
It is on the stock bootloader that comes with the nexus 4. The problem is after 4.3 update, i am not able to install cwm on my phone. using fastboot boot command gives black screen while fastboot flash boots a recovery whose none of functions work as it is unable to mount any partition, etc. and i have to install factory image of recovery and do a factory reset to boot the device again to android.
RohMish said:
It is on the stock bootloader that comes with the nexus 4. The problem is after 4.3 update, i am not able to install cwm on my phone. using fastboot boot command gives black screen while fastboot flash boots a recovery whose none of functions work as it is unable to mount any partition, etc. and i have to install factory image of recovery and do a factory reset to boot the device again to android.
Click to expand...
Click to collapse
Oh, I thought that was some custom bootloader, apologies.
Em yeah you will have to install the factory image.
Sent from my Nexus 4 using Tapatalk 4
andyabc said:
Oh, I thought that was some custom bootloader, apologies.
Em yeah you will have to install the factory image.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
Did that. it has made me more mad as it took 3 hours to download and when your phone is not working, even ever minute is like an day.
RohMish said:
Did that. it has made me more mad as it took 3 hours to download and when your phone is not working, even ever minute is like an day.
Click to expand...
Click to collapse
Did you try installing an other recovery like either the latest version of CWM or TWRP?
Sent from my Nexus 4 using Tapatalk 4
andyabc said:
Did you try installing an other recovery like either the latest version of CWM or TWRP?
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
tried an older version of cwm, touch, everything. but all are having same issues
RohMish said:
tried an older version of cwm, touch, everything. but all are having same issues
Click to expand...
Click to collapse
Older is worse!
Try TWRP 2.6.0.0.
Sent from my Nexus 4 using Tapatalk 4
andyabc said:
Older is worse!
Try TWRP 2.6.0.0.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
trying it now.
any ways i can switch to cwm after that as i prefer cwm any day of week. will fastboot boot command word as i dont want to sit flashing the factory image and let the apps and all download again
UPDATE: Tried twrp via fastboot boot command. nothing. just a blank screen after the reboot from bootloader (and after google boot screen) for a few seconds, andd then shuts down.
RohMish said:
trying it now.
any ways i can switch to cwm after that as i prefer cwm any day of week. will fastboot boot command word as i dont want to sit flashing the factory image and let the apps and all download again
Click to expand...
Click to collapse
The issue is that fastboot boot recovery doesn't work on 4.3. The new command if fastboot - c lge.kcal=0|0|0|x boot recovery.img
BLACKED OUT LTE N4
spaceman860 said:
The issue is that fastboot boot recovery doesn't work on 4.3. The new command if fastboot - c lge.kcal=0|0|0|x boot recovery.img
BLACKED OUT LTE N4
Click to expand...
Click to collapse
not working. says 0 is a not a command. this is as | works as a batch separator in windows
Update: as i remembered modifier <"> will prevent | from kicking into next line, i tried that, and it works!
fastboot -c "lge.kcal=0|0|0|x" boot recoverycwm.img. but still no action. tried a backup, it starts to backup but files are corrupted. and nothing else work.
This is from efrant guide
Open a command prompt in the directory mentioned above and type: fastboot boot customrecovery.img Note: If you are running the latest bootloader (z20i), the command would be: fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img Thanks hwti & el_charlie
BLACKED OUT LTE N4
spaceman860 said:
This is from efrant guide
Open a command prompt in the directory mentioned above and type: fastboot boot customrecovery.img Note: If you are running the latest bootloader (z20i), the command would be: fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img Thanks hwti & el_charlie
BLACKED OUT LTE N4
Click to expand...
Click to collapse
i loads up but is kind of broken.
any way i can copy the files to my pc to do some analysis. currently the folder which used to save the files has nothing. adb pull /mnt/shell/emulated/clockworkmod/backup/ /android/adbbackupfiles/nexus4 is yielding nothing.
OK. so now i tried using the touch version, and this time there are some files(Still copying). but those are very different than what it was on my older phones and my initial backup. Sorry, I had got away with this due to studies. now the files are .a and.b and the orignal file which is 0KB
So, one of my family members was mucking around on their tablet. I was sure that I has locked down the appropriate areas, but as of right now, I think I'm looking at a hard-brick. I'm not sure what kind of fastboot capabilities I have, turning it off, and on again boots to what looks like fastboot, but I have a Google splash screen. Using the vol up/down/pwr button does boot into fastboot, but I'm not sure what I have at my disposal for flashing. Any suggestions? I've just never seen anything like this before.
If you can boot into fastboot, it isn't a hard brick. A brick doesn't turn on.
Just try fastboot flashing the stock image on it from Google.
Sent from my Nexus 5
Another alternative would be to boot into recovery, if you can.
I assume you had twrp or cwm? If so, you could reflash the rom you're using. If not, you could install twrp from fastboot and then sideload a rom of your choice.
Pirateghost said:
If you can boot into fastboot, it isn't a hard brick. A brick doesn't turn on.
Just try fastboot flashing the stock image on it from Google.
Sent from my Nexus 5
Click to expand...
Click to collapse
bsquare said:
Another alternative would be to boot into recovery, if you can.
I assume you had twrp or cwm? If so, you could reflash the rom you're using. If not, you could install twrp from fastboot and then sideload a rom of your choice.
Click to expand...
Click to collapse
ADB push wasn't accepting anything. What I ended up doing, was using the Wug toolkit to force-flash a stock image. Still not sure what the hell happened, I'm just happy it works now.
Thanks for your help!
Verfassergeist said:
ADB push wasn't accepting anything. What I ended up doing, was using the Wug toolkit to force-flash a stock image. Still not sure what the hell happened, I'm just happy it works now.
Thanks for your help!
Click to expand...
Click to collapse
Fastboot and adb are not interchangeable.
Adb doesn't work in fastboot mode
Sent from my Nexus 5
Pirateghost said:
Fastboot and adb are not interchangeable.
Adb doesn't work in fastboot mode
Sent from my Nexus 5
Click to expand...
Click to collapse
I....*facepalm*
I'm trying to install TWRP recovery on my essential phone. this is the guide i am using, though pretty much every guide i found follows the same commands:
https://android.gadgethacks.com/how-to/install-twrp-recovery-essential-ph-1-0187660/
The command to determine my current slot returned that i am on slot_b, and when i try to flash the twrp img to slot_a, it sits trying to write. it never crashes but doesn't get anywhere. nothing is happening either in the command prompt window or on the phone screen.
I'm not sure what the issue is. I've updated the android sdk to the newest version and confirmed that I'm using that version of fastboot. I've also updated essential's windows drivers for the device, and rebooted the bootloader several times.
EDIT: I have noticed that on the phone screen when in the bootloader, it says "SECURE BOOT - yes". i don't know if this is important, but when i ran "fastboot oem device-info" it said true for unlocked and unlocked-critical.
Ricx94 said:
I'm trying to install TWRP recovery on my essential phone. this is the guide i am using, though pretty much every guide i found follows the same commands:
https://android.gadgethacks.com/how-to/install-twrp-recovery-essential-ph-1-0187660/
The command to determine my current slot returned that i am on slot_b, and when i try to flash the twrp img to slot_a, it sits trying to write. it never crashes but doesn't get anywhere. nothing is happening either in the command prompt window or on the phone screen.
I'm not sure what the issue is. I've updated the android sdk to the newest version and confirmed that I'm using that version of fastboot. I've also updated essential's windows drivers for the device, and rebooted the bootloader several times.
EDIT: I have noticed that on the phone screen when in the bootloader, it says "SECURE BOOT - yes". i don't know if this is important, but when i ran "fastboot oem device-info" it said true for unlocked and unlocked-critical.
Click to expand...
Click to collapse
Have you the latest twrp.img from the twrp.me site?
Do you have a type c to USB connector thing? Bluetooth keyboard?
If yes, fastboot flash boot twrp.img.
You might need the Bluetooth keyboard in case of not having touch response.
dirtyreturn said:
Have you the latest twrp.img from the twrp.me site?
Do you have a type c to USB connector thing? Bluetooth keyboard?
If yes, fastboot flash boot twrp.img.
You might need the Bluetooth keyboard in case of not having touch response.
Click to expand...
Click to collapse
i do have the newest file. i even tried redownloading it thinking the file might have been corrupted.
i haven't gotten to the part where i would need a usb otg keyboard yet, though i have one for when i make it that far.
I would check out the PH1 Development Telegram Channel as if your on stock they have boot images with TWRP and root already added and then all you have to do is fastboot flash the patched image and you will have TWRP with working touch and root as well. Here is the link to the channel if your interested https://t.me/EssentialPH1DEV
dirtyreturn said:
Have you the latest twrp.img from the twrp.me site?
Do you have a type c to USB connector thing? Bluetooth keyboard?
If yes, fastboot flash boot twrp.img.
You might need the Bluetooth keyboard in case of not having touch response.
Click to expand...
Click to collapse
robertbarber said:
I would check out the PH1 Development Telegram Channel as if your on stock they have boot images with TWRP and root already added and then all you have to do is fastboot flash the patched image and you will have TWRP with working touch and root as well. Here is the link to the channel if your interested https://t.me/EssentialPH1DEV
Click to expand...
Click to collapse
I'm not having issues with touch yet. haven't even made it far enough to know if I'm having an issue with touch in twrp...
I can't flash anything for some reason.
I'm stuck at "Sending 'boot_b' (48712 KB)" and nothing happens. every post I've seen says this should take less than 2 seconds but I've waited up to 10 minutes some tries and nothing happens. i need to restart the bootloader after trying this each time before it will let me try again.
Ricx94 said:
I'm not having issues with touch yet. haven't even made it far enough to know if I'm having an issue with touch in twrp...
I can't flash anything for some reason.
I'm stuck at "Sending 'boot_b' (48712 KB)" and nothing happens. every post I've seen says this should take less than 2 seconds but I've waited up to 10 minutes some tries and nothing happens. i need to restart the bootloader after trying this each time before it will let me try again.
Click to expand...
Click to collapse
Did you do the two unlock commands via fastboot? Firstly.?(not intending to dumb you down or anything)
Did you try with just - fastboot flash boot twrp.img ?
P.S. !! Definitely check out the posted telegram channel! Super helpful group of people.
dirtyreturn said:
Did you do the two unlock commands via fastboot? Firstly.?(not intending to dumb you down or anything)
Did you try with just - fastboot flash boot twrp.img ?
P.S. !! Definitely check out the posted telegram channel! Super helpful group of people.
Click to expand...
Click to collapse
I did fastboot flashing unlock and unlock_critical. Those seemed to work it shows up as being unlocked and factory reset.
To try to flash twrp I ran fastboot flash boot_a (also tried boot_b and boot) twrp.img and it tried to send but just sits trying and isn't getting anywhere.
Ricx94 said:
I did fastboot flashing unlock and unlock_critical. Those seemed to work it shows up as being unlocked and factory reset.
To try to flash twrp I ran fastboot flash boot_a (also tried boot_b and boot) twrp.img and it tried to send but just sits trying and isn't getting anywhere.
Click to expand...
Click to collapse
https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976
Ricx94 said:
I did fastboot flashing unlock and unlock_critical. Those seemed to work it shows up as being unlocked and factory reset.
To try to flash twrp I ran fastboot flash boot_a (also tried boot_b and boot) twrp.img and it tried to send but just sits trying and isn't getting anywhere.
Click to expand...
Click to collapse
Are you using cmd or power shell for Windows. What ports are you using,2.0 or 3.0 and which type of cord. A-c or c-c
Sent from my PH-1 using Tapatalk
dazeone said:
Are you using cmd or power shell for Windows. What ports are you using,2.0 or 3.0 and which type of cord. A-c or c-c
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
I've tried both CMD and Powershell
my computer only has USB 3.0 and 3.1 ports, all type A, so I'm using USB A-C cables. the cables are both only USB 2.0.
so I'm not sure why i tried this but it seemed to work...
I sent the flash command and when it got to the part it normally freezes at, i restarted the bootloader using volume and power keys on the phone. then while it was restarting i sent the command again, and as soon as it got to the bootloader the command activated and worked instantly. now I'm toying around with this newfound knowledge and i think i have twrp working. just wiped phone again and installed AOSIP so here we go
Ricx94 said:
so I'm not sure why i tried this but it seemed to work...
I sent the flash command and when it got to the part it normally freezes at, i restarted the bootloader using volume and power keys on the phone. then while it was restarting i sent the command again, and as soon as it got to the bootloader the command activated and worked instantly. now I'm toying around with this newfound knowledge and i think i have twrp working. just wiped phone again and installed AOSIP so here we go
Click to expand...
Click to collapse
Sorry... I didn't read...
When you are stuck at waiting for device .. if you unplug... Run the command... And then plug in... It will sometimes take...
Why... I don't know
Sent from my PH-1 using Tapatalk
Ricx94 said:
so I'm not sure why i tried this but it seemed to work...
I sent the flash command and when it got to the part it normally freezes at, i restarted the bootloader using volume and power keys on the phone. then while it was restarting i sent the command again, and as soon as it got to the bootloader the command activated and worked instantly. now I'm toying around with this newfound knowledge and i think i have twrp working. just wiped phone again and installed AOSIP so here we go
Click to expand...
Click to collapse
Nice to hear! Be sure to have the twrpinstaller.zip handy to flash after the ROM!! This preserves twrp.
rignfool said:
Sorry... I didn't read...
When you are stuck at waiting for device .. if you unplug... Run the command... And then plug in... It will sometimes take...
Why... I don't know
Click to expand...
Click to collapse
I need to send the command while the bootloader is restarting. It works consistently for me. Unplugging and repluging won't do it; only restarting bootloader. I honestly can't explain it but it's working great.
Ricx94 said:
I need to send the command while the bootloader is restarting. It works consistently for me. Unplugging and repluging won't do it; only restarting bootloader. I honestly can't explain it but it's working great.
Click to expand...
Click to collapse
HOLY CRAP THANK YOU
I've been going insane and this worked for whatever reason. You are awesome!
Zach Alt said:
HOLY CRAP THANK YOU
I've been going insane and this worked for whatever reason. You are awesome!
Click to expand...
Click to collapse
Glad i could be of service