i know this is probably a stupid question, but how do i boot into TWRP? does it have to be through a computer or is there a way to do it straight from the device?
Sent from my Kindle Fire using xda premium
install firefirefire
Have you actually installed twrp? If not, google it.
If you did, then reboot your device and when you see the yellow triangle on boot, hold the power button for 2 seconds until your power button turns from green to orange, then release it and wait a bit until the twrp screen appears.
Quick question....can I have TWRP 2.0 & FireFireFire bootloader installed with the stock Kindle splash screen?
I have both the bootloader (mmcblk0p2) and recovery (mmcblk0p5) backed up on my computer. I can boot from the TWRP backup without installing it (fastboot -i 0x1949 boot mmcblk0p5.img), but can I just dd the bootloader and recovery backups to their respective partitions (/dev/block/mmcblk0p2 and /dev/block/mmcblk0p5) and keep the Kindle splash screen?
The triangle is FFF.... if you don't want that, you would have to replace the graphic it uses. It is doable, but you would have to recompile FFF with the new graphic in it.
So basic answer... no.
Thanks for your input.
Well as it turns out, the "splash" partition isn't the splash screen partition I thought it was. It actually contains some log files which are probably used for troubleshooting.
Related
Yesterday, I have rooted mu Kindle Fire with BuritoRoot3, installed CWM and after putting it to recovery mode with Kindle Setup Utility, before flashing Energy ROM, I forgot to clean/wipe/factory default and i stuck in boot loop. Although the device was not booting up, it was responsive to ADB, but I stuggled to put it back to recovery mode to wipe it flash it again. I discovered, that the command "idme" that Setup Utility is using, does not exist in Energy ROM files (it should be located in /system/bin). So quick workaround was to extract this file from KF stock update image (a .bin file, which is actually a .zip and can be opened if renamed to .zip) and push it to /system/bin. Setup Utility will be able to get it to recovery mode again then.
what? reboot and hold the power button during startup
Sent from my HTC Glacier using xda premium
it did not help, it was going to the splash screen right on and loop again
Rom: Stock
Rooted with KFU 0.9.5
TWRP 2.1
fff 1.4a
The problem I'm having is that when I boot my KF up it goes to fff. I get 3 options to boot from (this is whenever I power down the KF). When I choose to boot to recovery, the power light turns orange for two secs and then it boots; but back to the fff screen. I did this about four times in a row and it still boots back to the ffa screen.
If I choose ~normal boot~, It boots up fine. When I try to use KFU to boot to recovery or fast boot, it says that it is waiting for device. I tried this several times but no luck.
I want to get into recovery. That's my goal. I'm guessing that the KF is not booting in fastboot for it to go into recovery. I tried to reinstall TWRP 2.1 with KFU and it gets to the point where it's waiting for the device and nothing happens.
I'm not very advanced in this stuff. Please be patient with me. Thank you for all your help.
what command are you using to install recovery?
ok
download twrp 2.1.1.img onto pc
turn off kindle (20 second hold) with the usb cable unplugged from the kindle
open terminal where you have fastboot located.
type the following:
fastboot flash recovery </enter/path/to/recovery.img/here>
press enter
you should see waiting for device
then plug in your usb to kindle
this should power up the kindle and fastboot flash a new recovery.
then type
fastboot reboot
note:
(there is a space between recovery & /
i also find it easier to put a space after "recovery" then drag & drop recovery.img into terminal)
ok...
I did everything you said and the cmd console was still <waiting for device> after I plugged in the KF.
I checked in device manager and that's ok for the adb (it says: android composite adb interface).
Still looking to get into twrp recovery.
IndianaBond said:
I want to get into recovery. That's my goal. I'm guessing that the KF is not booting in fastboot for it to go into recovery. I tried to reinstall TWRP 2.1 with KFU and it gets to the point where it's waiting for the device and nothing happens.
Click to expand...
Click to collapse
There's probably something wrong in KFU's process. Could you at least show us its log or a screenshot?
reflash twrp using smirkit. than try to get into recovery again
Sent from my Galaxy Nexus using xda premium
if its waiting for device your pc is issuing fastboot command. so as you say its your kindle.
one of the above methods should work.
imho smikis's smirkit is nice to use
edit: can you copy and paste your commands after you try to flash new recovery
Today I tried booting up to recovery (power+vol down), after choosing Recovery Mode from the menu and hitting Power button, it gets to a screen with the green Android guy with a red triangle and just stays there.
So I rebooted the phone. Launch Nexus Root Toolkit, I tried to install CWM or TWRP, neither works. It gets to the same recovery mode and gets stuck there, only this time, it gets stuck on the Google logo instead of the Android guy with red triangle. I even try to flash stock recovery, and it also doesn't work.
Why can't I get into CWM or TWRP nor can I flash them?
Thanks for any help.
bebopblues said:
Today I tried booting up to recovery (power+vol down), after choosing Recovery Mode from the menu and hitting Power button, it gets to a screen with the green Android guy with a red triangle and just stays there.
So I rebooted the phone. Launch Nexus Root Toolkit, I tried to install CWM or TWRP, neither works. It gets to the same recovery mode and gets stuck there, only this time, it gets stuck on the Google logo instead of the Android guy with red triangle. I even try to flash stock recovery, and it also doesn't work.
Why can't I get into CWM or TWRP nor can I flash them?
Thanks for any help.
Click to expand...
Click to collapse
Be sure u are bootloader unlocked.
Android guy is normal... Is a safety step before entering on stock recovery, to pass that: hold power and hit once volume +
Probably u cant flash images cuz fastboot isnt working(old fastboot.exe file), wrong recovery file,...
sent from my NEXUS 4 tasting a revamped cooking recipe of Jellybeans (stock 4.3).
C4SCA said:
Be sure u are bootloader unlocked.
Android guy is normal... Is a safety step before entering on stock recovery, to pass that: hold power and hit once volume +
Probably u cant flash images cuz fastboot isnt working(old fastboot.exe file), wrong recovery file,...
sent from my NEXUS 4 tasting a revamped cooking recipe of Jellybeans (stock 4.3).
Click to expand...
Click to collapse
Bootloader was unlocked. I launched the CMD Prompt from Nexus Root Toolkit and ran the fastboot command to manually flash the downloaded CWM and it worked.
Code:
adb reboot bootloader
fastboot flash recovery recovery-clockwork-x.x.x.x-mako.img
So maybe something's odd about the simple one-click utilities in Nexus Root Toolkit that is not working.
Thanks for the help nonetheless. :good:
bebopblues said:
Bootloader was unlocked. I launched the CMD Prompt from Nexus Root Toolkit and ran the fastboot command to manually flash the downloaded CWM and it worked.
Code:
adb reboot bootloader
fastboot flash recovery recovery-clockwork-x.x.x.x-mako.img
So maybe something's odd about the simple one-click utilities in Nexus Root Toolkit that is not working.
Thanks for the help nonetheless. :good:
Click to expand...
Click to collapse
well ui never used tollkits... i like to know what im doing, and IMO doing it urself is better wich turned out to be true in ur case
im glad u got it working
Hey Guys,
So I was trying to downgrade to 4.3 on my Nexus 7, and I was dumb enough to disconnect it before it was complete. I believe it was in the process of deleting user data. Now I have a screen that says "booting failed" on the left, the google logo in the middle, an unlock symbol on the bottom, and a start banner on the top left, but every time I try to hit start, it just stays on the same screen saying booting failed. Same results when I try to boot into recovery. Is there any hope?
You should investigate whether or not you can communicate with it using fastboot. You might need to get it to the bootloader screen (rather than the "failed boot" screen). [REF] Nexus 7 Button Combinations
If you can, then there is all sorts of hope (from what you describe, it sounds like the bootloader is unlocked). All you need to do is do a little reading about fastboot - for instance in the "return to stock" thread here on XDA.
fastboot is the gateway to all things root with the N7.
There might be hope
I can get to fastboot. The hang comes when I run the fastboot erase userdata. It just gets stuck there.
bmoney83 said:
I can get to fastboot. The hang comes when I run the fastboot erase userdata. It just gets stuck there.
Click to expand...
Click to collapse
I've done exactly the same thing. Any update please?
Thank you
bmoney83 said:
I can get to fastboot. The hang comes when I run the fastboot erase userdata. It just gets stuck there.
Click to expand...
Click to collapse
Stuck as in no messages, no output, prompt never returns?
Have you tried soft-booting a recovery to see what happens? e.g.
e.g. TWRP
Code:
fastboot boot openrecovery-twrp-2.4.1.0-grouper.img
e.g. CWM
Code:
fastboot boot recovery-clockwork-touch-6.0.2.3-grouper.img
-OR- (non-touch version)
fastboot boot recovery-clockwork-6.0.2.3-grouper.img
(The above are just examples, I'm not recommending a particular version of either custom recovery)
That might be a start. By communicating with a soft-booted recovery (adb shell blah-blah-blah), you can look at the kernel log (e.g. "adb shell dmesg") and see if it is complaining about partitions, filesystems, etc. The only rub with this is that because of the N7's use of an "internal" pseudo-SD card, the custom recoveries try and mount the userdata partition as soon as they start up, so if there is something wrong with that filesystem, the recovery itself might get wedged. I think I saw this with TWRP for instance - the touch interface wouldn't come up when I had a effed-up userdata partition. So, either an older recovery or a non-touch interface recovery might be adviseable here if you have troubles.
good luck
Solved!
Alright, two things helped me out here.
1. I used a different computer and reinstalled everything.
2. When you unzip the stock rom, it still leaves one zipped file in there that also needs to be unzipped into the platform-tools folder.
And now I'm in business!
Using the 2017 Shield I am not able to fastboot boot twrp.img, when attempting to do so (using 3.0.2, 3.1.1, 3.2) it results in a momentary Nivida logo, then the display output stops, requiring a hard reboot.
I am able to fastboot flash recovery and boot into TWRP but once I've done this it causes a boot freeze, displaying the Nivida logo indefinitely.
I feel certain there is something I've missed, I've had this same experience on two Shield units so far.
w0rdie said:
Using the 2017 Shield I am not able to fastboot boot twrp.img, when attempting to do so (using 3.0.2, 3.1.1, 3.2) it results in a momentary Nivida logo, then the display output stops, requiring a hard reboot.
I am able to fastboot flash recovery and boot into TWRP but once I've done this it causes a boot freeze, displaying the Nivida logo indefinitely.
I feel certain there is something I've missed, I've had this same experience on two Shield units so far.
Click to expand...
Click to collapse
are you on a 4k tv, if so that is your problem twrp for the shield will not show on 4k
jionny said:
are you on a 4k tv, if so that is your problem twrp for the shield will not show on 4k
Click to expand...
Click to collapse
I had the same issues, tried different monitors (non 4K), gave up and used magisk for root. I use flashfire for backups and flashing zips. Installed xposed through magisk. I don't think i have a need for TWRP after all the bootloops and issues. I had to reflash the stock image everytime to get it to boot. I am running version 7.0.2.
Did you make sure to install the Nvidia Family Drivers for ADB. I had to uninstall ADB Composite Device and also delete driver files. I then rescanned after plugging back into PC, it was listed as ADB Composite under USB devices. Updated the driver with the Nvidia Family Driver. Haven't had an issue since.
Michajin said:
I had the same issues, tried different monitors (non 4K), gave up and used magisk for root. I use flashfire for backups and flashing zips. Installed xposed through magisk. I don't think i have a need for TWRP after all the bootloops and issues. I had to reflash the stock image everytime to get it to boot. I am running version 7.0.2.
Click to expand...
Click to collapse
I'll have to look into flashfire, as I've seen the same suggestion pop up elsewhere. Any tips on how to install Magisk on the Shield? I've attempted several times with as many methods I could find through several threads, and they've all failed in one way or another. Did you have to use a specific version of Magisk?
Also, I currently have TWRP flashed on my Shield. I've been reading that the new Oreo doesn't play nicely with TWRP and may be prone to bricking and bootloops. I eventually want to upgrade mostly to prevent the nag screen. Is there a way to install the stock bootloader without wiping the device and flashing the stock image?
thekwijibo said:
I'll have to look into flashfire, as I've seen the same suggestion pop up elsewhere. Any tips on how to install Magisk on the Shield? I've attempted several times with as many methods I could find through several threads, and they've all failed in one way or another. Did you have to use a specific version of Magisk?
Also, I currently have TWRP flashed on my Shield. I've been reading that the new Oreo doesn't play nicely with TWRP and may be prone to bricking and bootloops. I eventually want to upgrade mostly to prevent the nag screen. Is there a way to install the stock bootloader without wiping the device and flashing the stock image?
Click to expand...
Click to collapse
If i am understanding you, you are on Nougat and want to go on to Oreo? I have Magisk on Oreo.
I am on Oreo but i couldn't get TWRP to work. You could flash back to stock recovery; (download stock image from NVidia whatever version you are on)
fastboot flash recovery recovery.img
Use the recovery.img from the stock image that matches your current OS
I took the boot.img from the stock OS image put it in a location on my sheild i could access from file manager then patched it with magisk (latest version), then flashed it from fastboot
fastboot flash boot boot.img
"boot.img" being the one you patched with magisk.
None of this should wipe anything unless you unlock/lock the bootloader.
Michajin said:
If i am understanding you, you are on Nougat and want to go on to Oreo? I have Magisk on Oreo.
I am on Oreo but i couldn't get TWRP to work. You could flash back to stock recovery; (download stock image from NVidia whatever version you are on)
fastboot flash recovery recovery.img
Use the recovery.img from the stock image that matches your current OS
I took the boot.img from the stock OS image put it in a location on my sheild i could access from file manager then patched it with magisk (latest version), then flashed it from fastboot
fastboot flash boot boot.img
"boot.img" being the one you patched with magisk.
None of this should wipe anything unless you unlock/lock the bootloader.
Click to expand...
Click to collapse
Awesome. Thanks for the clarification. It worked, I flashed the recovery.img and I was able to install the OTA update.
I was able to use Magisk to patch the boot.img, however when I used fastboot to flash it to the shield, it didn't seem to do anything. I tried again with no improved results. I tried flashing the super.su zip that had worked for me before, and I ran into some bootloops, but was able to get things somewhat working again. I decided to scrap it, and try to flash the whole enchilada from the Nvidia image.
fastboot flash staging blob
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot reboot
and..... brick. oops.
I was able to pull the power, plug in a keyboard, hold down A&B and managed to get into fastboot. Yay!
I suspected I might have skipped a step in there or rebooted prematurely, so I tried the process again.
This time I got the yellow bootloader warning, followed by the red system corrupt warning. I thought I had screwed it up, but after a few moments it finished booting. So, it "works", but takes a bit longer to boot due to the additional red warning screen.
Any suggestions on where I should go from here? I feel like I'm walking on thin ice with this additional red warning screen on boot.
thekwijibo said:
Awesome. Thanks for the clarification. It worked, I flashed the recovery.img and I was able to install the OTA update.
I was able to use Magisk to patch the boot.img, however when I used fastboot to flash it to the shield, it didn't seem to do anything. I tried again with no improved results. I tried flashing the super.su zip that had worked for me before, and I ran into some bootloops, but was able to get things somewhat working again. I decided to scrap it, and try to flash the whole enchilada from the Nvidia image.
fastboot flash staging blob
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot reboot
and..... brick. oops.
I was able to pull the power, plug in a keyboard, hold down A&B and managed to get into fastboot. Yay!
I suspected I might have skipped a step in there or rebooted prematurely, so I tried the process again.
This time I got the yellow bootloader warning, followed by the red system corrupt warning. I thought I had screwed it up, but after a few moments it finished booting. So, it "works", but takes a bit longer to boot due to the additional red warning screen.
Any suggestions on where I should go from here? I feel like I'm walking on thin ice with this additional red warning screen on boot.
Click to expand...
Click to collapse
From magisk check root at that point, i didn't notice any difference until i open magisk and install the manager. I used the developer image from NVidia, flashed the 7.0.2 version then did the boot.img for magisk. The red warning screen? that the bootloader unlocked warning? If always used the flash-all.bat file so i didn't have to go line by line. I thought it would work either way, but maybe there is something more to the developers image i missed.
After I booted the magisk patched boot.img, the magisk application wouldn't load. It would just go to the splash screen with the logo image, and remain there indefinitely. I waited about 10 minutes, then FC it. Thereafter I couldn't even open the app until I rebooted, in which it would hang on the splash screen yet again. I tried to use apps that require root, and all apps indicated that I didn't have root. Oh well. I've had nothing but trouble with magisk on my shield, but it works flawlessly on all my other android devices. I'll have to keep futzing with it, because several people out there have successfully done so, and I must be totally missing some critical step along the way.
As for the warning screens, when I boot there's first the yellow bootloader unlocked warning, which I'm used to. After that goes away, just a black screen, then a few moments later a red warning screen pops up saying:
"Your device is corrupt. It can't be trusted and may not work properly".... yadda yadda yadda.
This stays on for a while, and at first I might have prematurely assumed I bricked my device, but it eventually boots. It takes about twice as long to boot now, but it eventually does.
I downloaded and flashed the developer's image from the Nvidia site as well, and followed the flashing instructions exactly as the attached documented steps indicated. Perhaps I ought to try the stock image next? If that doesn't work, I'm assuming I'll have to completely wipe and factory reset the device, then flash as stock image. The red warning corruption warning has me slightly worried, but mostly irritated that it takes my shield twice as long to boot now. (ok, maybe not twice as long, but at about 30 seconds longer)
I'm curious, where did you find the flash-all.bat? I'm wondering if there is some secret squirrel command that I neglected that wound me up in this situation. Or maybe the dual warning screens is "normal" for those using the developer image?