Develop Bugs

[ROOTED]Bell v20f .img files

Here is a link to the .img files. You can flash them using adb, but you will lose CWM. I am posting these in the hope that it will help someone who knows a little bit more about bootloader security and whatnot to make a CWM-compatible version.
The stock files are Here
Extract files to root of SD card, enable USB debugging and PC Software mode (if on LG rom)
Run the following from windows command prompt:
adb shell
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p13
dd if=/sdcard/firmware.img of=/dev/block/mmcblk0p1
dd if=/sdcard/baseband.img of=/dev/block/mmcblk0p14
dd if=/sdcard/system.img of=/dev/block/mmcblk0p27
Restart,
Congrats, you've got the latest Bell release for the P930.
Got it rooted using this guide: http://forum.xda-developers.com/showthread.php?t=1835946
Used Rom Manager to install CWM.
Whenever I try to boot into CWM, i get the following error:
-------------------------------------------
Secure Booting Error
Cause : boot certification verify
-------------------------------------------
---------------------------------------------------
Enter the fastboot...
Enter the fastboot...
Long time no see!
---------------------------------------------------
Click to expand...
Click to collapse
The ROM boots though, and has root access. Superuser works, and I am currently using titanium backup to delete the massive amounts of bloatware present in the rom.
I have attempted to flash recovery.img with CWM on it, but the error persists.
Anyone have any ideas as to how we can get around this error?
Click to expand...
Click to collapse

hereric said:
Anyone have any ideas as to how we can get around this error?
Click to expand...
Click to collapse
You must downgrade to GB before you can install CWM properly.

I just wonder if it works if you just load boot.img and system.img with adb.

abc001 said:
I just wonder if it works if you just load boot.img and system.img with adb.
Click to expand...
Click to collapse
You're welcome to try. I am too busy today, and I have started getting random reboots, so I'm switching back to Liquid Nitro.

How to get back to 100% stock unrooted?

Hi, all I've done since getting the 8.9 was boot into FastBoot, and use the KFID System.Img to flash the rooted system.img (option 3 I think).. I'm wanting to return now to 100% unrooted stock, what are the steps I need to take? I don't have a 2nd bootloader installde or anything like that.

Haloman800 said:
Hi, all I've done since getting the 8.9 was boot into FastBoot, and use the KFID System.Img to flash the rooted system.img (option 3 I think).. I'm wanting to return now to 100% unrooted stock, what are the steps I need to take? I don't have a 2nd bootloader installde or anything like that.
Click to expand...
Click to collapse
Code:
adb shell su -c "rm /system/app/Superuser.apk"
Code:
adb shell su -c "rm /system/xbin/su"
Then factory reset it.

Thepooch said:
Code:
adb shell su -c "rm /system/app/Superuser.apk"
Code:
adb shell su -c "rm /system/xbin/su"
Then factory reset it.
Click to expand...
Click to collapse
I was able to do it by downloading official firmware update from amazon and used their instructions for upgrading removed root.
Thank you!
Sent from my SCH-I605 using Tapatalk 2

T^T
Sent from my GT-S5300 using xda app-developers app

[Q] Need help to go back to stock OS

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.

XT1635-03 Power On Straight Away Go To Bootloader Mode

Hi, I have a XT1635-03 and have an issue of power on button go to bootloader mode instead of go to system. Phone is unlocked and on modified logo.bin. Any idea how to fix this symptom?
Thank you.

Hi,
First boot to twrp recovery menu and connect your phone via usb. And in your computer open the adb fastboot command And type the following:
adb shell dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
#but do a backup before! (just in case)
adb pull /dev/block/platform/msm_sdcc.1/by-name/misc misc.img
Sent from my VTR-L29 using Tapatalk

pocko said:
Hi,
First boot to twrp recovery menu and connect your phone via usb. And in your computer open the adb fastboot command And type the following:
adb shell dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
#but do a backup before! (just in case)
adb pull /dev/block/platform/msm_sdcc.1/by-name/misc misc.img
Sent from my VTR-L29 using Tapatalk
Click to expand...
Click to collapse
Thank you, but I'm currently on stock ROM (retcn).
So I have to flash TWRP, perform the 'dd' command and flash back the stock ROM and the issue will be gone?
Update: Flashed the TWRP and tried the 'dd', it returned error of no such file or directory.
dd: can't open '/dev/block/platform/msm_sdcc.1/by-name/misc': No such file or directory
Cheers.

ADB help

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!