Hello. I own a kindle fire HDX 7 (Thor) with a bootloader installed, but can't install the new rom. I wipe first, then install the rom, and finally gapps. After resetting and pressing continue to skip the recovery, the screen just stays black until it fails and I reset my device back into recovery.
Anyone know what I may be missing?
Thanks!
Edit: the recovery installed is Safestrap 4.01 (TWRP v2.7.1.0). I'm kind of confused as to whether this is safestrap or trwp.
Safestrap isnt the same as TWRP, if you have Safetrap ,you are limited to bootloader locked ROM's like FireNexus KK, you need unlock the bootloader to get full TWRP recovery
Every single ROM needs a minimum recovery build installed to get flashed properly, if my memory dont fail, Marshmallow and Nougat ROM's, needs TWRP version 3.0 or newer ,otherwise thats why you cant install it.
If you have TWRP, you can upgrade using Flashify,start the system, downaload Flashify from Google Play, open it, and use recovery option to replace old TWRP, just grab the new TWRP (search in the forums the links) replace it and reboot, and its done
But check first first which recovery are you install, replace Safetrap with TWRP without unlocked bootloader , will brick your device
This is a TWRP recover screen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And this is Safestrap
Yousucks2 said:
Safestrap isnt the same as TWRP, if you have Safetrap ,you are limited to bootloader locked ROM's like FireNexus KK, you need unlock the bootloader to get full TWRP recovery
If the ROM have Marshmallow or Nougat core, you need a newer version of TWRP, version 3.0 or newer ,otherwise thats why you cant install it.
If you have TWRP you can upgrade using Flashify,start the system, downaload Flashify, open it, and open recovery option, just grab the new TWRP (search in the forums the links) replace it and reboot, and its done
But check first first which recovery are you install, replace Safetrap with TWRP without unlocked bootloader , will brick your device
Click to expand...
Click to collapse
Excellent response!
@leeismyname - I happen to be helping another member through unlocking the bootloader (here). Feel free to tag along. Just be sure to use the "Thor" (7" HDX) vs "Apollo" (8.9" HDX) files when installing the vulnerable aboot (bootloader) and TWRP. Ask questions in that thread as needed.
Thank you both for your timely and informative responses! From the pictures, I know I have safestrap. Time to piggy back off Davey's other thread!
Related
I followed guides (this guide) on this site to convert my HTC One Dev Edition --> Google Play Edition with OTAs.
This is what I did:
- The phone was already unlocked.
- I got S-OFF.
- I verified that my MID was correct and changed my CID to match the Google Play Edition phone.
- I installed TWRP Recovery and used it to wipe the phone.
- I flashed the "Pre Rooted 4.3 RUU Zip"
The phone is running well with 4.3 now.
What I need help with:
I don't plan on flashing ROMS in the future, I just want it to be a GPE with OTA updates.
My understanding is that flashing the RUU also installs the GPE stock recovery (overwriting TWRP), and the stock recovery has to be there in order to get OTAs. Is this right?
When I enter the bootloader and choose recovery, I see this screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is this normal?
Does it mean that the correct stock recovery is in place?
ggabriele3 said:
I followed guides (this guide) on this site to convert my HTC One Dev Edition --> Google Play Edition with OTAs.
This is what I did:
- The phone was already unlocked.
- I got S-OFF.
- I verified that my MID was correct and changed my CID to match the Google Play Edition phone.
- I installed TWRP Recovery and used it to wipe the phone.
- I flashed the "Pre Rooted 4.3 RUU Zip"
The phone is running well with 4.3 now.
What I need help with:
I don't plan on flashing ROMS in the future, I just want it to be a GPE with OTA updates.
My understanding is that flashing the RUU also installs the GPE stock recovery (overwriting TWRP), and the stock recovery has to be there in order to get OTAs. Is this right?
When I enter the bootloader and choose recovery, I see this screen:
Is this normal?
Does it mean that the correct stock recovery is in place?
Click to expand...
Click to collapse
Yes, that is absolutely normal, when you boot stock recovery, it's looking automatically in your file structure for something to flash. When it doesn't find anything, you get this screen. To get to recovery options just hold volume up and hit power, the screen will go grey and you'll see the recovery options.
Hope this helps.
hi i managed to update my tab to the latest firmware 4.0.4 . Previously it was already rooted and TWRP installed. I was thinking of rooting and backing up this build so from romtoolbox i boot into recovery mode (thinking that i will be seeing TWRP) But when boot i was shown the folllowing picture
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
since all of my buttons are not working (hence the reason installing TWRP ) i was ok fine lets reboot it via adb. therefore i run adb reboot and yet it still boots back to the same screen . Thinking i need to reverting all of the changes via odin i tried reboot download also does not work. reboot-bootloader also does not work. apprently i am stuck at this screen.
Right now i only have access to adb and is there any way i can recover from this?
many thanks again
I'm assuming you were running some kind of custom rom with TWRP as your recovery before going to stock ICS. Essentially, flashing stock ICS overwrote the old TWRP.
To fix it, flash in TWRP again (its somewhere in the development section) via Odin.
EDIT: If you can't access download mode... Try push the TWRP .tar file via ADB
Sent from my GT-P7510
Soryuu said:
I'm assuming you were running some kind of custom rom with TWRP as your recovery before going to stock ICS. Essentially, flashing stock ICS overwrote the old TWRP.
To fix it, flash in TWRP again (its somewhere in the development section) via Odin.
EDIT: If you can't access download mode... Try push the TWRP .tar file via ADB
Sent from my GT-P7510
Click to expand...
Click to collapse
the thing is i only root and installed twrp for the sake of backing up since my daughter loves to install application. I've read about pushing / Installing application but that would requires root right? this is my command console like
Right now is there a way to force it to boot into download because thats the only way i see i can fix it (without using physical buttons)
Again many thanks for replying.
So long story short: Finally got CWM installed on the MS769 from Metro by using some chinese root program to get root, installed busybox, then used the L9 Recovery installer from artas to get CWM on there. So then I try to install bobzhome's P769 CM ROM and met with undesirable results.
Here is CWM installed by the L9 Recovery Installer v1.5:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The rom I'm trying to install:
The "This package is for "p769,p760,u2" devices; this is a "p940" error
This most certainly not a p940! So I suspect CWM is a bit outdated. But how can I get the most up to date CWM when I've already used the most up-to-date L9 Recovery Installer? I've tried other flashing programs like flashr and CWM's official rom manager on Google Play but I get met with the dead android picture when trying to boot into the new recovery I flashed.
I also tried opening up the CM ROM and finding the script that does this check and disabled it. But then shortly I get this error regarding setting recursive metadata. I googled "setting recursive metadata" error and folks just say to update CWM. So I guess I gotta really get CWM updated.
Is this a dead end for me? Should I just toss this phone in a pit of lava?
Have you unlocked the bootloader? If not, you can't install CM.
The CWM you've installed is a 2nd-init recovery. You need to unlock the bootloader to install a) a proper recovery, and b) to install ROMs that aren't based on stock
Darren
Sent from my Bell Mobility Samsung Galaxy S6 SM-G920W8 using Tapatalk
DarryDoo said:
Have you unlocked the bootloader? If not, you can't install CM.
The CWM you've installed is a 2nd-init recovery. You need to unlock the bootloader to install a) a proper recovery, and b) to install ROMs that aren't based on stock
Darren
Sent from my Bell Mobility Samsung Galaxy S6 SM-G920W8 using Tapatalk
Click to expand...
Click to collapse
Thanks for the response. Alas, I feared the worst. I had that feeling since there were several people saying there's absolutely no way to unlock the bootloader, and that there was even a petition to unlock it.
It can be unlocked, using a 910k cable and plenty of patience.
Until then, you can only run stock ROMs, or modified stock ROMs such as Kumakan or UltraROM. Try them out, they may suit your needs if you don't want to go through the BL unlock process.
Cheera
Darren
Sent from my Bell Mobility Samsung Galaxy S6 SM-G920W8 using Tapatalk
I'm currently on CM 13.0-20160809-NIGHTLY-onyx and I've tried to flash three different Roms on my phone (Two different versions of cm14 and OOS3) with TWRP. But every time I get the error message attached in the screenshot.
Now, I've seen a few people online having similar problems, but it was mostly for cm12 and the suggested fixes are not really helpful for my situation.
I've somehow lost my stock backup so I'm kinda lost right here.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In general Error 7 usually means you're using the wrong version of TWRP. I'm still using Blu_Sparks version for the new bootloader.
quoakkaflocka said:
I'm currently on CM 13.0-20160809-NIGHTLY-onyx and I've tried to flash three different Roms on my phone (Two different versions of cm14 and OOS3) with TWRP. But every time I get the error message attached in the screenshot.
Now, I've seen a few people online having similar problems, but it was mostly for cm12 and the suggested fixes are not really helpful for my situation.
I've somehow lost my stock backup so I'm kinda lost right here.
Click to expand...
Click to collapse
You need to upgrade your bootloader and TWRP.you are using very old CM and now everything is changed so upgrade your boot loader and recovery.
I already use TWRP 3.0.2-0 which is the newest version according to TWRP Manager.
How do I upgrade my bootloader?
Edit: So I found this way to do it :Link
The thing is: it says the bootloader must be unlocked, but if I type "fastboot devices" I get nothing back. "adb devices works. I'm pretty sure that my bootloader is unlocked since I have a custom rom and my device is rooted but I'm not sure if I have activated the CM recovery option in the developer settings ever since.
I really don't wanna brick my phone so I'm not sure if I should blindly follow the steps in the link above.
quoakkaflocka said:
I already use TWRP 3.0.2-0 which is the newest version according to TWRP Manager.
How do I upgrade my bootloader?
Edit: So I found this way to do it :Link
The thing is: it says the bootloader must be unlocked, but if I type "fastboot devices" I get nothing back. "adb devices works. I'm pretty sure that my bootloader is unlocked since I have a custom rom and my device is rooted but I'm not sure if I have activated the CM recovery option in the developer settings ever since.
I really don't wanna brick my phone so I'm not sure if I should blindly follow the steps in the link above.
Click to expand...
Click to collapse
"fastboot devices" doesn't work unless you are in the bootloader
I would like to install LineageOS 14.1 on my S4 but I can't get TWRP to install. I'm running the new VRSGPL1 build and have it rooted. Also tried to install TRWP on rooted OF1 but couldn't make it work. I started with a completely reset and wiped phone each time. I used Wondershare to root, unlock the bootloader, and install SuperSU. I then try to use the official TWRP app to install. It says it succeeded but after reboot, I get the message that the phone didn't start correctly and that i need to use the Verizon tool to repair. I've tried MANY different methods to make it work so i'm at the end of my rope. I'm hoping one of you Gurus out there can help. Thanks.
mikeymoman said:
I would like to install LineageOS 14.1 on my S4 but I can't get TWRP to install. I'm running the new VRSGPL1 build and have it rooted. Also tried to install TRWP on rooted OF1 but couldn't make it work. I started with a completely reset and wiped phone each time. I used Wondershare to root, unlock the bootloader, and install SuperSU. I then try to use the official TWRP app to install. It says it succeeded but after reboot, I get the message that the phone didn't start correctly and that i need to use the Verizon tool to repair. I've tried MANY different methods to make it work so i'm at the end of my rope. I'm hoping one of you Gurus out there can help. Thanks.
Click to expand...
Click to collapse
You can only use Flashfire (v.53 or lower with this device) with a locked bootloader. You can't install TWRP or any other custom recovery. Don't keep trying because you will brick your phone.
PS- Wondershare nor any other tool (available now at least) will unlock your bootloader on this device.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Doesn't it mean the bootloader is unlocked if i get the screen with Samsung and an unlocked lock on boot?
mikeymoman said:
Doesn't it mean the bootloader is unlocked if i get the screen with Samsung and an unlocked lock on boot?
Click to expand...
Click to collapse
No that means you're rooted
Ok. Thanks for clearing that up for me. I installed Flashfire. I tried v .52 first and it wouldn't start up so i uninstalled and installed v .53. It starts up and lets me choose my zip files to flash. I click on flash and it starts the process giving me the screen loading files then goes blank. I've tried changing different settings but i still get the blank screen. Any ideas?
mikeymoman said:
Ok. Thanks for clearing that up for me. I installed Flashfire. I tried v .52 first and it wouldn't start up so i uninstalled and installed v .53. It starts up and lets me choose my zip files to flash. I click on flash and it starts the process giving me the screen loading files then goes blank. I've tried changing different settings but i still get the blank screen. Any ideas?
Click to expand...
Click to collapse
Sent you a pm