Related
Warning:
Installing this bin will allow any UID to reboot your device.
After a few people complained about making bad system mods, or permissions on /system/app and not being able to get root or back into recovery after that, I made a little tool to help.
http://dl.dropbox.com/u/8699733/kindlefire/rbfb
Installation
Use my BurritoRoot app to get root:
adb root
adb remount
adb push rbfb /system/xbin/
adb shell chown 0.0 /system/xbin/rbfb
adb shell chmod 06755 /system/xbin/rbfb
adb reboot
To use:
So if your stuck in a bootloop, and you can only get to adb, you can use this took to reboot to fastboot or recovery.
adb shell /system/xbin/rbfb <parameter>
4000 : boot normal
4002 : boot fastboot
5001 : boot recovery
Any or no parameter will reboot.
##########################
Help fund my device fund, so we can bring BurritoRoot to other devices
https://market.android.com/details?id=net.andirc.jcasedonate
##########################
so rebooting into a particular mode depends on a single binary only?
kfu is failed install twrp...how to bootloader uninstall or unlock in cmd?i want root......
icolt said:
kfu is failed install twrp...how to bootloader uninstall or unlock in cmd?i want root......
Click to expand...
Click to collapse
I can help you. Please follow below step.
install TWRP:
1.Package You need：
a.Kindle Fire 6.2.2 image file
b.TWRP package
2.after install driver，you can input below command under CMD:
fastboot -i 0x1949 flash recovery openrecovery-twrp-blaze-2.1.1.img
3.Root Step:
If you want to root your KF,You must use the 6.2.2 firmware.
root command:
adb push root/su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
adb remount
adb install root/Superuser.apk
adb reboot
attachment is the root file you need.
2012androidfans said:
I can help you. Please follow below step.
install TWRP:
1.Package You need：
a.Kindle Fire 6.2.2 image file
b.TWRP package
2.after install driver，you can input below command under CMD:
fastboot -i 0x1949 flash recovery openrecovery-twrp-blaze-2.1.1.img
3.Root Step:
If you want to root your KF,You must use the 6.2.2 firmware.
root command:
adb push root/su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
adb remount
adb install root/Superuser.apk
adb reboot
attachment is the root file you need.
Click to expand...
Click to collapse
in 6.3version?????
icolt said:
in 6.3version?????
Click to expand...
Click to collapse
NO, ONLY FOR 6.2.2 or 6.2.1.
Hi guyz! With this small guide I hope i'll explain to you how to flash a recovery without bootloader. C'mon!
1) Download the recovery
2) Extract the recovery image in the zip (normally the folder is named "pg76img.zip" and the recovery "recovery.img")
4) Download terminal emulator
5) Open Terminal Emulator
6) Write su and accept superuser request
7) write flash_image recovery /sdcard/recovery.img
8) if you'd like to try if recovery work write reboot recovery
9) enjoy!
-EDIT-
This script doesn't work with stock rom (sense roms)
Sent from my Wildfire S using xda app-developers app
This method won't work on Sense ROMs unless you install the flash_image script (Else you'll get not found or something similar).
Assuming you've already downloaded and installed Android SDK and that stuff, we can start:
1. Extract the script. Let's say you extracted it to your Desktop.
2. Connect your WFS with android debugging on.
3. Type the following:
Code:
adb root (enter)
adb remount (enter)
adb push Desktop\flash_image /system/bin (enter)
adb shell chmod 0755 /system/bin/flash_image (enter)
4. Flash your recovery. (In this case, your recovery.img is on /sdcard/)
Code:
adb shell flash_image recovery /sdcard/recovery.img
That's all. And there's no need to do this on CM-based ROMs as they already have this command script.
ScardracS said:
Hi guyz! With this small guide I hope i'll explain to you how to flash a recovery without bootloader. C'mon!
1) Download the recovery
2) Extract the recovery image in the zip (normally the folder is named "pg76img.zip" and the recovery "recovery.img")
4) Download terminal emulator
5) Open Terminal Emulator
6) Write su and accept superuser request
7) write flash_image recovery /sdcard/recovery.img
8) if you'd like to try if recovery work write reboot recovery
9) enjoy!
Sent from my Wildfire S using xda app-developers app
Click to expand...
Click to collapse
this won't work on stock roms....as stock doesn't have flash_image script....so mention in OP only for cm based roms....& ofcourse for stock based roms djoliver has already posted a tut
With Android 4.2.x I was able to install SuperSU binary right after flashing the factory image using fastboot, without flashing any custom recovery. I simply boot CWM recovery:
Code:
fastboot boot recovery-clockwork-6.0.3.5-maguro.img
... mounting /system and pushing the su executable with the right permissions:
Code:
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
With Andoird 4.3, after installing the su executable (taken from the .zip file, latest version) SuperSU Pro complains about no SU binary installed :crying:
How can I fix this? Thank you.
Just flash the zip and be happy. Remind you'll need the version 1.45 minimun
Sent from my Galaxy Nexus using xda app-developers app
"no SU binary installed" means mobile is not rooted,try to root your device with latest version of SuperSu with TWRP Recovery,you can find alot of tutorials if you search
By Hashcode, Senior Recognized Developer on 1st February 2013, 10:57 AM over 5 years ago
STEP 1. Backup your stock partitions to your own HD for later if you need disaster recovery:
Code:
adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot of=/sdcard/stock-boot.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery of=/sdcard/stock-recovery.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/system of=/sdcard/stock-system.img" # This will take a few minutes
adb pull /sdcard/boot0block.img
adb pull /sdcard/stock-boot.img
adb pull /sdcard/stock-recovery.img
adb pull /sdcard/stock-system.img # This will take a few minutes
with that being said here is what happens, i can see adb is working
C:\adb>adb devices
List of devices attached
B0CC060324930545 device
C:\adb>adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
/system/bin/sh: su: not found
C:\adb>
I could go on on but, that would be more gibberish.
So, what is wrong? Did the commands change? Is my path set wrong on my pc? Is there a updated thread i just have not come across yet? Anyone?
I'll thank you now for any help
Nothing changed. If you get the device to show up with the adb devices command, then everything's theoretically set up. The only reason you're getting an error with su not being found is that you aren't rooted. Here's a quick way to get root (like actually super simple, considering you already have ADB working):
1) download the attached 8.1.4 bootloader file (this is ripped straight from my Kindle before I "upgraded" to 8.5.1 to test this out). you may consider placing it in the same folder as the adb program. Also download SuperSU and the latest TWRP build for this device.
2) shut down the kindle and make sure it's plugged in.
3) run fastboot -i 0x1949 getvar product, then power the kindle on. when you see "fastboot mode" on the kindle, you should see something in the command prompt that begins with "Jem". if you do, then it's working.
4) type fastboot -i 0x1949 flash bootloader jem_8-1-4_bootloader.img to flash the 8.1.4 bootloader. this is ESSENTIAL because the kindle won't boot custom (unsigned) images otherwise. more explanation below...
5) next, type fastboot -i 0x1949 flash recovery twrp.img, where twrp.img is the file name of the TWRP image you downloaded earlier.
6) type fastboot -i 0x1949 oem recovery to kick the Kindle into recovery mode. if all goes well, you should see "TWRP" on your device after a few moments.
7) copy the SuperSU zip you downloaded to the kindle's internal storage. then on the kindle, tap Install. Next, on the side menu to the left, swipe up from the bottom and tap "sdcard" (referring to the internal storage that you see on the computer when the kindle's plugged in). Tap the SuperSU .zip, and then swipe where indicated. Feel free to reboot the system, and then voila, you're rooted. You should be able to run those backup commands. As a bonus, you won't have to download TWRP or the bootloader image from that virus-laden d-h.st site - avoid it like the plague.
8) Because TWRP's already flashed, you can type adb reboot recovery from the stock OS to begin flashing a new ROM right away.
A couple side notes...
1) Because you've flashed TWRP, a custom recovery, there is no need whatsoever to run the stock recovery backup command. It's already been overwritten, and if you really need it (which, again, is highly doubted because it only lets you run a factory reset), you can actually extract the recovery image from the system partition. Just run adb pull /system/recovery-prod.img stock-recovery.img instead of the adb shell su... stock-recovery.img one.
2) You have to flash the 8.1.4 bootloader because the one you currently have is more than likely a newer version. Custom ROMs (and even recoveries like TWRP) rely on an exploit in the 8.1.4 bootloader in order to trick the device into running the image (and newer bootloaders have this exploit patched already). So technically, because the exploit has to be run every time, the bootloader is never "unlocked" - merely tricked. Without the older bootloader in place, you get what is referred to as the "red screen of death". It's not pretty, but it's not permanent either. (Just power off the kindle, and then run the fastboot command involving "getvar product" to get it to the bootloader so you can flash the 8.1.4 bootloader and go forward.)
Hope this helps!