[Q] How to remove TWRP completely - Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot

Hi Guys,
after a lot of struggle I managed to get FireOS Stock back on my HDX 7" 2013.
The speakers on my device don't work anymore and I want to use the warranty on amazon.
Therefore I should remove TWRP I guess...
I got Safestrap 3.75 (TWRP v2.7.1.0) on my device and already tried the following threads for removing TWRP and having Stock FireOS on the device:
http://forum.xda-developers.com/showthread.php?t=1638452 (2nd Post starting with "Reverting to stock software")
-> still being able to access TWRP
http://forum.xda-developers.com/showthread.php?t=2409435
-> still being able to access TWRP
Also I read this: "If you Kindle Fire is booting directly into TWRP, without you doing it manually, then your device is stuck in fastboot mode.
You can issue the following commands through adb on your computer:
adb shell su -c "idme bootmode 4000"
adb reboot"
-> I am only able to use adb commands when I am booted into a ROM and not from TWRP. Is that normal? When I issue the command (booted into FireOS) I get: "C:\adb-tools>adb shell su -c "idme bootmode 4000"
/system/bin/sh: su: not found"
And when trying "adb shell idme bootmode 4000" I get: "Could not open /dev/block/mmcblk0boot0!
Can't read the idme."
Although I believe these bootmode changes won't remove TWRP... My idea was just to use this so Amazon Support won't notice the changes made to the device...
Can anyone tell me how I remove TWRP and stay with my currently working FireOS (with broken speakers...)
Thanks a lot!
~finchson

If you have Safestrap you do NOT have the "real" TWRP!
Safestrap should be removed by un-installing it's app via Safestrap itself. Be sure to remove secondary slots before un-installation, if you created any.

Cl4ncy said:
If you have Safestrap you do NOT have the "real" TWRP!
Safestrap should be removed by un-installing it's app via Safestrap itself.
Click to expand...
Click to collapse
But I don't have Safestrap (the App) installed anymore. Currently there is only FireOS Stock ROM active and I don't even know if that one is rooted...
{
"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 Safestrap I used seems to be unavailable and the links are not working anymore: http://forum.xda-developers.com/showthread.php?t=2556677 and http://blog.hash-of-codes.com/downloads/safestrap/
I was lucky enough to find the apk here: http://www.mechno.com/goog/
But I no longer got Root on the Stock ROM and therefore cant remove Safestrap.
Luckily towelroot worked just fine so my Stock ROM was rooted and I could remove Safestrap.
I now rebooted the device and everything seems to be ok.
My warranty device already is on it's way.
Thanks for the tip Cl4ncy

Related

[Q] Stuck in first white screen

I am stuck with my HTC Hero and I need help to find my way out of the maze.
I was having trouble with my RCMix v2.2 WWE instalation. I decided to flash a new ROM.
What I did:
I tried to boot into recovery but it didn't work. I believe recovery was damaged. I went to installed Rom Manager and tried to reinstall RA Recovery. When it was rebooting, phone got stuck in the first white screen.
Now that's where I am stuck:
Even though I try all the rebooting shortcuts, it doesn't load regular ROM and doesn't load recovery. It keeps showing the white screen with HTC logo and "quietly brilliant" slogan. And it starts it over and over.
If I try to go into recovery with power+home button it freezes in HTC logo on white screen, without looping and without showing "quietly brilliant" slogan.
My two options were:
1) Flash a recovery using ADB. It didn't work. I think that's because phone doesn't really goes to the point where the desktop software can reach it through debug mode. Doesn't know where to go from here. I go to Windows CMD line, in ADB folder and try to run "adb shelll". It shows me "Error: device not found".
2) Install a stock/shipped ROM. My hope was to start from a shipper rom and go from there all the way to rooting and flashing a custom ROM. The installation of a shipped ROM worked until the point where it checks the ID. Since I don't have a goldkey (and there is not way I can create one) it doesn't allow me to finish shipped ROM instalation. Is there an universal shipped ROM file which doesn't demand a specific ID or goldkey?
So... What do I do? Any one can give me a clue?
Thanks!
I've been trying to use ADB + Fastboot to install RA Recovery, as described here:
http://forum.xda-developers.com/showthread.php?t=561124
The problem is that the instructions below don't work:
via fastboot + adb -> In case you don't have a custom recovery, so when you get signature fail errors
Code:
adb shell reboot bootloader
fastboot boot recovery-RA-hero-v1.7.0.1.img
adb shell mount /sdcard
adb push recovery-RA-hero-v1.7.0.1.img /sdcard/recovery-RA-hero-v1.7.0.1.img
adb shell flash_image recovery /sdcard/recovery-RA-hero-v1.7.0.1.img
adb shell reboot
Click to expand...
Click to collapse
As you can see 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"
}
What am I doing wrong? (I wish I could have asked in the related thread, but I was not allowed).

[Driver] PureDriver STS R5A ADB Recovery Custom Driver

While in the Sony Tablet Bootloader Discussion I have created a R5A ADB Recovery Driver.
This will overwrite your Sony Tablet S ADB driver.
This does support x86 and x64.
Please note that the recovery is going to disallow most if not some adb commands, I created this so people can access the recovery with the new recovery address via ADB, hopefully someone would be able to bypass and hack the recovery using this.
This uses the ADB from the system so it is ok to install.
EDIT: I was really suppose to use adb install to install an application.
EDIT 2: Sideload just throws back an error, I have not tested ADB install and I doubt that would work.
Screeny of the commands that would work if I had a flashable zip file and also if the recovery allowed such thing:
{
"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"
}
Download and Installation instructions here: http://caftp.pcsat.tv/drivers/puredriver_sts_r5a_adb
andyabc said:
While in the Sony Tablet Bootloader Discussion I have created a R5A ADB Recovery Driver.
This will overwrite your Sony Tablet S ADB driver.
This does support x86 and x64.
Please note that the recovery is going to disallow most if not some adb commands, I created this so people can access the recovery with the new recovery address via ADB, hopefully someone would be able to bypass and hack the recovery using this.
This uses the ADB from the system so it is ok to install.
EDIT: I was really suppose to use adb install to install an application.
EDIT 2: Sideload just throws back an error, I have not tested ADB install and I doubt that would work.
Screeny of the commands that would work if I had a flashable zip file and also if the recovery allowed such thing:
Download and Installation instructions here: http://caftp.3owl.com/Drivers/PureDriver_STS_R5A_ADB/
Click to expand...
Click to collapse
says install method not supported for this type of file. I was hoping to use this to allow flashing on my soft brick tab that I just can't seem to get going again.
jamminjon82 said:
says install method not supported for this type of file. I was hoping to use this to allow flashing on my soft brick tab that I just can't seem to get going again.
Click to expand...
Click to collapse
Yeah the install command is just for installing applications...
Sent from my Nexus 4 using Tapatalk 4
Can we run adb shell and “ dump_image boot /sdcard/boot.img “ to port CWM
Plays2 said:
Can we run adb shell and “ dump_image boot /sdcard/boot.img “ to port CWM
Click to expand...
Click to collapse
Nope, unfortunately Sony did block most of the ADB commands and I assume it is blocked with either ADB unlock code or some file which is required to unlock the commands.
Sent from my Nexus 4 using Tapatalk 4

[Q] Help. Stuck in Android system recovery<3e>

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.

New AOSP-Ex Rom won't load, please help

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!

Custom binary blocked by FRP lock (Samsung S7 SM-G930F) adb shows no device

hey guys,
hope you are doing fine so far.
a few days ago I rebooted my phone bc I thought this would be a good idea. I do not do that very often.
then this message appeared on the screen:
CUSTOM BINARY BLOCKED BY FRP LOCK and now it is stuck in here:
red: ODIN MODE, DOWNLOAD SPEED FAST
{
"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"
}
I would like to backup some directories via adb shell before I reinstall my rom. Best way would be to not lose any data and bring it back to life as it was.
BUT: adb does not show any deivce no matter what I do.
what I did:
Windows: I installed the drivers, adb (also tried 2 tools from xda), created adb_usb.ini in %user%\.android (for correct vendor ID)
Linux(latest Ubuntu LTS):
1. installed adb
2. lsusb shows: Bus 001 Device 008: ID 04e8:685d Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II] (Download mode)
what is a bit confusing, bc I got a S7 as mentioned before.
3. defined usb rules: SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", ATTR{idProduct}=="685d", MODE=="0666", GROUP=="plugdev"
in /etc/udev/rules.d/51-android.rules (I had to create the file).
4. changed vendor file: /home/user/.android/adb_user.ini
0x04e8 (same as in Windows).
5. reloaded adb rules, restarted udev and adb service and until now I restarted the computer a few times.
still no devices shown via "adb devices".
I cannot change any preferences within my rom bc it won't start. recovery mode does not work, too.
ROM: Project Alice 2.0 (2017-09)
Recovery: TWRP (I do not remember exactly which version, but must be latest 2017-09, probably twrp-3.1.1-0-herolte)
SU: SR3-SuperSU v2.82
is there someone out who can help me with this mess? I would appreciate that much!!! nearly crying here...
PS: atm I have to use an iphone... so please be aware that I am really (!) desperate to get my phone back
Solution
no answers so far ^^
BUT in case s.o. needs help at this point, I found a solution that helped me.
found a gem on Youtube. I am not allowed to post links thus I am too new here...
Just search for "Flash official Android 8.0 Oreo Firmware on S7/S7 edge (WITHOUT FACTORY RESET??✔)"
--> flash a new ROM via Odin with the HOME_CSC file.
that got my phone back to life without wiping my data.
hlppp
no work..

Categories

Resources