I'm trying to disable encryption and my usual method of typing this into adb in recovery isn't working. Is it possible?
Code:
adb shell recovery --wipe_data --set_filesystem_encryption=off
Related
How to I flash an imagine in superuser through adb
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?
Hello friends,
I have Kindle Fire HD 8.9. I installed CM 11 on it six months ago using this method http://forum.xda-developers.com/showthread.php?t=2128175 and have been using it without any major problem since then. But I feel sluggishness in its performance so I want to switch back to stock Amazon OS. I had made a backup of stock OS using the method described in above mention thread, i.e.
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
Now I have those four files (bootblock.img, stock-boot.img, stock-recovery.img and stock-system.img) on my HDD.
If I want to go back to stock OS, I would do following steps, and I want to know if that is the proper way to proceed. and is there something I must do during the whole process in order to succeed or must be mindful of?
Plug in your fastboot cable and reboot so that you see the fastboot screen and enter the following commands:
Code:
fastboot -i 0x1949 flash boot boot.img
fastboot -i 0x1949 flash recovery recovery.img
fastboot -i 0x1949 flash system system.img # This one will take a few minutes
fastboot -i 0x1949 reboot
or should I follow instructions given here http://forum.xda-developers.com/showthread.php?t=2011126
some suggestions or instructions would be of great help. Thank you.
Both serve.
If you use your files you will return to the version that originally had in the tablet. If you use the link, you will return to the above versions (8.1.4, 8.1.3 or 8.1.2).
I do not recommend re-stock. CM11 is faster than any stock.
Yes, I did find CM11 much productive than stock Amazon OS but over time I witnessed deterioration in performance. I am in no way trying to say that it is because of CM,it could have been low hardware of Kindle.
Anyway, I used the backup made by TWRP and restored Kindle to its initial state(i.e. rooted and Google Play installed). At this moment I am on version 8.4.9. I have two questions, what if I install latest OTA? Would I loose TWRP and Root? and eventually ability to install a new ROM again? Or TWRP would be still there after OTA?
After latest OTA 8.5.1, TWRP and root permission is gone and Kindle is back to its original condition.
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!
Hello,
i recently installed magisk rooted my phone using TWRP. Then I debloated it and deleted the MI cloud services. Now when I start my phone it reboots into TWRP and shows:
“Android Rescue Party trigger! Wipe data and caches and/or clean-flash you ROM!"
Is there a method to reinstall these apps from TWRP?
Depends on how you debloated. either copy these files back to device and wipe dalvik-cache
Code:
/system/app/CloudService/CloudService.apk
/system/app/CloudService/oat/arm64/CloudService.vdex
/system/app/CloudService/oat/arm64/CloudService.odex
or re-enable the package in package-restrictions.xml
Code:
adb pull /data/system/users/0/package-restrictions.xml
delete the enabled flag with Notepad++
<pkg name="com.miui.cloudservice" ceDataInode="300224" e̶n̶a̶b̶l̶e̶d̶=̶"̶3̶"̶ ̶e̶n̶a̶b̶l̶e̶d̶C̶a̶l̶l̶e̶r̶=̶"̶s̶h̶e̶l̶l̶:̶1̶0̶0̶0̶"̶ ̶i̶n̶s̶t̶a̶l̶l̶-̶r̶e̶a̶s̶o̶n̶=̶"̶4̶"̶/>
push the modified file back and write its content into existing file
Code:
adb push package-restrictions.xml /tmp
adb shell cat /tmp/package-restrictions.xml > /data/system/users/0/package-restrictions.xml
/system/app/CloudService/CloudService.apk /system/app/CloudService/oat/arm64/CloudService.vdex /system/app/CloudService/oat/arm64/CloudService
adb pull /data/system/users/0/package-restrictions.xml
adb push package-restrictions.xml /tmp
adb shell cat /tmp/package-restrictions.xml
you need platform-tools for this and type commands on your PC in cmd.exe