Related
HELP!
Tried using the method to unlock and root and when I used the boot img now I am in a bootloop, sits at Google and just keeps going. Can anyone point me to the factory LTE boot.img? PLEASE?
Thank you in advance.
Would this help? http://rootzwiki.com/topic/11459-updatedvzw-g-nexus-full-nandroid/
I am having the same issue. The root tool included boot.img gets the phone stuck on the Google logo when the 'fastboot boot boot.img' command is used
Are you guys on verizon? And if so, did you download and install the ota before doing superboot thing? Need to know because I was about to do it myself, and I did the ota this morning after I got my GN.
Sent from my Galaxy Nexus using XDA App
im in the same boat. used superboot r3 ....
---------- Post added at 01:25 PM ---------- Previous post was at 01:25 PM ----------
wilshyre said:
Are you guys on verizon? And if so, did you download and install the ota before doing superboot thing? Need to know because I was about to do it myself, and I did the ota this morning after I got my GN.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
i did the OTA then superboot
---------- Post added at 01:27 PM ---------- Previous post was at 01:25 PM ----------
hmm, i managed to get into recovery. i did factory reset... looked like the phone froze for a while but i believe i pressed power and volume (cant remember if i was both or just one. but i was able to boot up just fine.
Factory Images for CDMA/LTE Verizon Galaxy Nexus: https://dl.google.com/android/aosp/mysid-itl41d-factory-516b56c2.tgz
Source: http://groups.google.com/group/android-building/msg/f6002e27c9b41a5d?pli=1
jbqueru Jean-Baptiste Queru
Factory images for Verizon Galaxy Nexus at goo.gl/SOSa6 - more goodness will follow.
14 minutes ago Favorite Retweet Reply
Click to expand...
Click to collapse
looks like superuser was installed as well...
wilshyre said:
Are you guys on verizon? And if so, did you download and install the ota before doing superboot thing? Need to know because I was about to do it myself, and I did the ota this morning after I got my GN.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
I tried superboot and the manual method, no dice. Stuck on the Google logo for both
I had to wait at least five minutes before it finally rebooted again after fast booting the boot.img. I was sure that I wasn't booting but it turns out it was just taking a long time
Sent from my Galaxy Nexus using xda premium
Are you sure it's in a bootloop?
If your following this guide, step 4 rooting, give it some time. I thought mine was froze at that step as well, but I waited and it booted up. Probably took about 2 minutes or so (though it felt like 20).
Edit: Ha, swm beat me to the punch
Nevermind... apparently it worked and gave me SU without getting past the Google logo. Did a battery pull and superuser worked. Very strange.
Natolx said:
Nevermind... apparently it worked and gave me SU without getting past the Google logo. Did a battery pull and superuser worked. Very strange.
Click to expand...
Click to collapse
people here http://forum.xda-developers.com/showthread.php?t=1352413&page=12
are saying it takes about 5 minutes, not actually a boot loop...
I found the LTE img here , I actually loaded odin and wiped data and it solved my bootloop, wasnt stuck on the animation it was stuck at the actual Google, then it would vibrate and reset Google just keep doing it. Apparently that old img works fine with 4.0.1 but 4.0.2 sends you in the loop
There's also this tarball recently issued direct from google:
http://groups.google.com/group/andr...hread/9a944a4dbc8d23c5/f6002e27c9b41a5d?pli=1
It's not 4.0.2 though, that puts you back on 4.0.1.
Can someone list the steps that are needed to actually flash the stock image on a windows computer. I am stuck at the google logo and bootlooping as well.
Thanks in advance!
Wngman200 said:
Can someone list the steps that are needed to actually flash the stock image on a windows computer. I am stuck at the google logo and bootlooping as well.
Thanks in advance!
Click to expand...
Click to collapse
Same. I downloaded the tgz file from Googles site but I dont know how to flash it on my phone. Odin im assuming could work but Ive never used it.
Wngman200 said:
Can someone list the steps that are needed to actually flash the stock image on a windows computer. I am stuck at the google logo and bootlooping as well.
Thanks in advance!
Click to expand...
Click to collapse
Johnpg said:
Same. I downloaded the tgz file from Googles site but I dont know how to flash it on my phone. Odin im assuming could work but Ive never used it.
Click to expand...
Click to collapse
Do you guys have fastboot set up and do you have 7zip or something comparable to unzip the tgz?
Sent from my Galaxy Nexus using xda premium
davehasninjas said:
Do you guys have fastboot set up and do you have 7zip or something comparable to unzip the tgz?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Yeah my computer finds the serial number. I tried to use ODIN but ODIN wont find my phone(where it shows up with the ID and yellow) I also have something to unzip it. Still havnt figured out how to flash the stock image
How to flash the stock image file for those of you having issues:
http://forum.xda-developers.com/showpost.php?p=20344760&postcount=2
Johnpg said:
Yeah my computer finds the serial number. I tried to use ODIN but ODIN wont find my phone(where it shows up with the ID and yellow) I also have something to unzip it. Still havnt figured out how to flash the stock image
Click to expand...
Click to collapse
ok, when you unzip it, go to the image-mysid-itl41d.zip folder, and move system.img and boot.img to the same directory as fastboot.
Now once you have fastboot up in a terminal and your device is in fastboot mode the commands are:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot
Unless you're going the method from the noob thread, in which case thebfastboot commands should be (correct me if I'm wrong):
fastboot-windows.exe flash system system.img
fastboot-windows.exe flash boot boot.img
fastboot-windows.exe reboot
And that should have you booting back to stock.
I ran into this issue myself since I was on 4.0.2. Once I was back on 4.0.1 I used super boot straight from [email protected]'s thread and it worked fine. Upgraded back to 4.0.2 afterwards and still kept root.
Let me know if this helps.
Sent from my Galaxy Nexus using xda premium
Would somone mind posting the ICS version of flash_image? I can't find it anywhere.
Alternatively, would someone mind compiling it please: https://github.com/CyanogenMod/android_bootable_recovery/blob/ics/flashutils/flash_image.c
Why do u specifically need flash_image?
What r you trying to do?
Sent from Galaxy Nexus (GSM)
nxt said:
Why do u specifically need flash_image?
What r you trying to do?
Sent from Galaxy Nexus (GSM)
Click to expand...
Click to collapse
I want to flash images on my device. It looks like the version of the file that has been out for years is not ICS compatible.
Sent from my Galaxy Nexus using Tapatalk
Just do it via clockwork recovery, or fastboot... unless
You want to do it from the phone itself using terminal?
Sent from Galaxy Nexus (GSM)
I flashed the ICS image from Google code just fine. Via fastboot.
I'm not sure what flash_image is supposed to be or why you need it. I'm pretty sure you don't need it if all you want to do is flash the ICS-images found on Google code.
If I'm a noob and don't get what this is all about... Sorry, I guess. I'll STFU
nxt said:
Just do it via clockwork recovery, or fastboot... unless
You want to do it from the phone itself using terminal?
Sent from Galaxy Nexus (GSM)
Click to expand...
Click to collapse
Exactly.
josteink said:
I flashed the ICS image from Google code just fine. Via fastboot.
I'm not sure what flash_image is supposed to be or why you need it. I'm pretty sure you don't need it if all you want to do is flash the ICS-images found on Google code.
If I'm a noob and don't get what this is all about... Sorry, I guess. I'll STFU
Click to expand...
Click to collapse
flash_image is a utilty that will allow you to flash images to partitions on your device using a terminal emulater on your device or via adb. There is no need to have an unlocked bootloader, and no need to plug your device into a computer.
CWM uses this utility to flash images. It looks like Koush made some changes to it to make it work on ICS, as the original version no longers works properly on ICS (worked fine on Gingerbread and earlier).
I'd really appreciate it if someone would quickly compile it for me. I don't have access to a linux box at the moment. Thanks.
efrant said:
I'd really appreciate it if someone would quickly compile it for me. I don't have access to a linux box at the moment. Thanks.
Click to expand...
Click to collapse
If nobody has helped you out by Sunday, pm me and I can see what I can get done. Unfortunately no time now.
Sent from my Galaxy Nexus using Tapatalk
josteink said:
If nobody has helped you out by Sunday, pm me and I can see what I can get done. Unfortunately no time now.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Thanks very much. I'll pm you if no one helps out.
Sent from my Galaxy Nexus using Tapatalk
efrant said:
Would somone mind posting the ICS version of flash_image? I can't find it anywhere.
Alternatively, would someone mind compiling it please: https://github.com/CyanogenMod/android_bootable_recovery/blob/ics/flashutils/flash_image.c
Click to expand...
Click to collapse
Anyone?... Bueller?... Anyone?...
efrant said:
Would somone mind posting the ICS version of flash_image? I can't find it anywhere.
Alternatively, would someone mind compiling it please: https://github.com/CyanogenMod/android_bootable_recovery/blob/ics/flashutils/flash_image.c
Click to expand...
Click to collapse
This one comes from building ICS complete and something I had lying around from my december build.
Can't get Koush's recovery to build at all and since I am a complete noob when it comes to gcc basics and cross-compiling especially, I can't get you that one without instructions.
Anyone care to offer some educational insight... In the name of science ofcourse!
josteink said:
This one comes from building ICS complete and something I had lying around from my december build.
Can't get Koush's recovery to build at all and since I am a complete noob when it comes to gcc basics and cross-compiling especially, I can't get you that one without instructions.
Anyone care to offer some educational insight... In the name of science ofcourse!
Click to expand...
Click to collapse
Thanks for spending time on this, but, unfortunately it does not work on ICS. If it was from a build pre-December 18, it likely won't have the modifications in it.
I'm a noob as well, and I probably know less than you, so I don't think I'd be able to write a good step-by-step...
Hopefully someone will be able to help out. Thanks again.
josteink said:
This one comes from building ICS complete and something I had lying around from my december build.
Can't get Koush's recovery to build at all and since I am a complete noob when it comes to gcc basics and cross-compiling especially, I can't get you that one without instructions.
Anyone care to offer some educational insight... In the name of science ofcourse!
Click to expand...
Click to collapse
Correction.
Using some cyanogen magic perl scripts, I managed to unpack the official 5.5.0.2 recovery (which works fine on my ICS gnex) and from that one I could extract KOush's build of flash_image, which you will find attached to this post.
It is significantly larger than the plain ICS flash_image, which I guess means it is statically built/linked and probably supports more devices, but I can't really say anything for sure.
Have a good one.
Now... I'm still looking into building fastboot FOR arm (so that I can run it from my asus transformer).
Anyone care to help me out getting gcc to build stuff for me?
Hmmm. I can't figure this out. None of the versions of flash_image seem to work in a terminal, yet CWM and ROM Manager obviously work using it.
If anyone can help shed some light on this, it would be more than welcome.
On older devices, you could use flash_image to flash radios, bootloaders, and recoveries, either through a terminal emulator on your device, or though an adb shell on your computer.
The syntax was: flash_image partition path-to-image-file.img
Trying to use this on my Galaxy Nexus produces an error:
can't find recovery partitionfailed with error: -1
Not sure what the problem is. It would be nice to get this working, as it would give users another on-device option to flash radios, bootloaders, and recoveries, without using ROM Manager.
Hey efrant, did u ever get anywhere with this?
danger-rat said:
Hey efrant, did u ever get anywhere with this?
Click to expand...
Click to collapse
Unfortunately not. There must be a different syntax for the ICS version, but I didn't get around to trying to figure it out. I suppose someone could ask one of the guys that make apps for flashing recoveries (rom manager, CWM touch installer), i.e., koush et al., as they must obviously use flash_image.
Sent from my Galaxy Nexus using Tapatalk
Trying flash_image from ROM Manager 5.0.0.1
efrant said:
Unfortunately not. There must be a different syntax for the ICS version, but I didn't get around to trying to figure it out. I suppose someone could ask one of the guys that make apps for flashing recoveries (rom manager, CWM touch installer), i.e., koush et al., as they must obviously use flash_image.
Click to expand...
Click to collapse
The apk for ROM Manager from ClockworkMod (Koush) contains a flash_image file in the assets folder. For ROM Manager 5.0.0.1, the file is 70.66K and has a MD5 checksum of a7291696dd4fc4208e397e31aa84bc9e.
I'm going to try copying it to /system/bin, setting ownership to root.root, and setting permissions to 750. I'll then see if it works on my Galaxy Nexus (LTE/CDMA) like the old CyanogenMod flash_image used to work.
I'll post back here once I'm done.
---------- Post added at 03:22 PM ---------- Previous post was at 03:16 PM ----------
chriv said:
I'll post back here once I'm done.
Click to expand...
Click to collapse
No luck. I used the flash_image that was in ROM Manager 5.0.0.1, and I had the same problem:
Code:
[email protected]:/mnt/sdcard/Download # flash_image recovery recovery.img
flash_image recovery recovery.img
can't find recovery partitionfailed with error: -1
255|[email protected]:/mnt/sdcard/Download #
---------- Post added at 03:27 PM ---------- Previous post was at 03:22 PM ----------
I also tried:
Code:
[email protected]:/mnt/sdcard/Download # flash_image --help
flash_image --help
usage: flash_image partition file.img
2|[email protected]:/mnt/sdcard/Download #
So the usage of the flash_image file is supposedly still the same. Maybe it's expecting a different name for the recovery partition (other than "recovery")?
chriv said:
[snip]
So the usage of the flash_image file is supposedly still the same. Maybe it's expecting a different name for the recovery partition (other than "recovery")?
Click to expand...
Click to collapse
I think the quote above is right. We prob have to use:
flash_image /dev/block/platform/omap/omap_hsmmc.0/by-name/recovery CWM.img
But I haven't had the chance to work through it yes.
Sent from my Galaxy Nexus using Tapatalk
flash_image not the solution
efrant said:
I think the quote above is right. We prob have to use:
flash_image /dev/block/platform/omap/omap_hsmmc.0/by-name/recovery CWM.img
Click to expand...
Click to collapse
I tried that. The error is the same. I also checked out the android source. The source for flash_image is bootable/recovery/mtdutils/flash_image.c .
flash_image enumerates all of the mtd partitions on the device from /proc/mtd, and compares their names with the first argument passed to it. If it doesn't find a match, it bails with the error "can't find %s partition" where %s is the first argument passed to flash_image.
You can enumerate the mtd partitions yourself. I did, and this is what I got:
Code:
[email protected]:/ $ cat /proc/mtd
cat /proc/mtd
dev: size erasesize name
mtd0: 00100000 00001000 "w25q80"
[email protected]:/ $
As you can see, the only mtd partition on my Samsung Galaxy Nexus is w25q80. I could use flash_image with it, but I'm not that brave. For all I know, I could be overwriting the system partition, or the userdata partition.
The bottom line:
It is not likely that flash_image is being used by ROM Manager on the Galaxy Nexus, as flash_image is only capable of writing to the w25q80 mtd partition, and I don't know what it is! Koush must be using some other way to flash the recovery from the phone.
I'd be interested to know if other Galaxy Nexus users have something different for /proc/mtd.
I'd contact Koush and ask him how he writes the recovery on the Galaxy Nexus, but he never responds to my tweets! ;-)
I hope this helps some users, even if it just prevents other users from going on a wild goose chase with flash_image.
@chriv I get the same as you when I list the partitions.
Sent from my Galaxy Nexus using Tapatalk
Sorry to bump an old thread, but I found an alternative way to flash recovery images to my CDMA Galaxy Nexus without using flash_image (and without unlocking the bootloader/using fastboot). I found a post over on RootzWiki and the command is:
Code:
cat name-of-the-recovery.img > /dev/block/platform/omap/omap_hsmmc.0/by-name/recovery
I did this and successfully reflashed the stock Google recovery image. I currently have a CM9 nightly running on the phone, the bootloader relocked and the stock recovery loaded (since leaving ClockworkMod Recovery installed would allow a thief to extract data via adb).
There are other things in the /by-name directory such as boot and radio so I'm guessing that it'd be possible to write those images as well (although I haven't tried it myself).
The only weird bug I've encountered is that ROM Manager still says that ClockworkMod Recovery is still installed for some reason (but it's not).
Hey everyone. I am a fresh new owner of the Kindle Fire 2(and generation), running 10.4.6 firmware, and its definitely a nifty little thing. I got it solely for the purpose of rooting it and turning into some half-ass Nexus 7, haha. I've been reading up as much as I can, and from what I've been seeing, this device is a finnicky SOB. Things can go either really smoothly, or really badly at random. So before I take the plunge, I just wanna post the steps I'm gonna do in hopes that someone who is rooted and running a custom ROM can solidly confirm these steps are correct.
I'm going to use this guide here to for 10.4.6: http://forum.xda-developers.com/showthread.php?p=44577053
Then I'm going to use this guide for root: http://forum.xda-developers.com/showthread.php?t=2075959
Downgrade bootloader(not software firmware) to 10.2.4, flash TWRP using fastboot on PC, then load in the FMKilo-2.apk and CM and gapps on tablet, run Tweezermod, reboot into TWRP and do a full system wipe (I'll wipe 3x just to be safe), then flash CM and gapps.
From my understanding, I don't necessarily need a fastboot cable to root and flash ROMs, but I will need it incase things go haywire, which there is a moderate possibility of. Is all of this correct? I'm sorry if this is a redundant and pointless post, but I just want some solid answers before I dive in. I'm not new to Android or flashing, but this device is just a little intimidating, so I just wanna be safe. And who knows, maybe this post can help others with 10.4.6
Cheers, guys. :beer:
Sent from my LG-LS970 using xda app-developers app
I suggest putting the ROM and gapps onto the kindle before flashing twrp and 2nd bootloader, because the latest os detects if the boot loader isn't the same version as the os, if it doesn't match it boot loops into recovery and its slightly more complicated than drag and dropping the ROM once that happens.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
I suggest putting the ROM and gapps onto the kindle before flashing twrp and 2nd bootloader, because the latest os detects if the boot loader isn't the same version as the os, if it doesn't match it boot loops into recovery and its slightly more complicated than drag and dropping the ROM once that happens.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
So right after flashing TWRP, immediately flash CM and gapps? And how's my steps looking? Am I good to go without needing a fastboot cable?
Sent from my LG-LS970 using xda app-developers app
It seems like you left out the step for installing 2nd boot loader, I'm more familiar with the HD models so I'll have to check up on the details for flashing on kf2, but I think you can just use fire flash to flash twrp, but I'd better check before you start messing with the boot loader. And yea pretty much you have to flash a new ROM or a older amazon os from twrp after flashing.
Edit: I don't see any mention of fire flash being compatible with kf2's, best to avoid it. There's a thread that tells how to put second boot loader and twrp on in the android dev section if u haven't seen it. Here it is! http://forum.xda-developers.com/showthread.php?t=2100963
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
It seems like you left out the step for installing 2nd boot loader, I'm more familiar with the HD models so I'll have to check up on the details for flashing on kf2, but I think you can just use fire flash to flash twrp, but I'd better check before you start messing with the boot loader. And yea pretty much you have to flash a new ROM or a older amazon os from twrp after flashing.
Edit: I don't see any mention of fire flash being compatible with kf2's, best to avoid it. There's a thread that tells how to put second boot loader and twrp on in the android dev section if u haven't seen it. Here it is! http://forum.xda-developers.com/showthread.php?t=2100963
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Sweet, thank you so much man! And I can do all of this WITHOUT the fastboot cable, right? I only need that if SHTF, correct? And one more thing, I put the 2nd bootloader on AFTER I downgrade to 10.2.4?
Once again, I apologize for all the questions. Just wanna be safe rather than sorry.
Sent from my LG-LS970 using xda app-developers app
Yes you downgrade the bootloader first or you will be needing a fastboot cable, hehe.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Yes you downgrade the bootloader first or you will be needing a fastboot cable, hehe.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Well, didn't get very far at all I couldn't get adb to recognize my device. I updated android SDK, install Google USB Drivers, installed new Kindle driver fixes in the reference thread in the development section, rebooted both device and computer. Adb just refused to recognize the device. Maybe I'll try a different computer?
Sent from my LG-LS970 using xda app-developers app
Make sure your drivers are installed, also remember adb doesn't work with fastboot mode, just thought I'd mention that. If you don't have the drivers installed use the ones in my signature.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Make sure your drivers are installed, also remember adb doesn't work with fastboot mode, just thought I'd mention that. If you don't have the drivers installed use the ones in my signature.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Well, for some reason I can't even get other computers to recognize my device using ADB. These same computers I've been using for root for quite sometime now, are all of the sudden not listing any devices through ADB, not even my phone. Should I try reinstalling adb drivers? And how would I go about using the USB drivers posted in your signature?
Sent from my LG-LS970 using xda app-developers app
You just find then device in the device manager with a yellow triangle next to it usually, right click it, hit update driver, and point it to the directory that u extracted that zip file to. If you happen to need a newer version of adb/fastboot, download the attachment on this post.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
You just find then device in the device manager with a yellow triangle next to it usually, right click it, hit update driver, and point it to the directory that u extracted that zip file to. If you happen to need a newer version of adb/fastboot, download the attachment on this post.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Hey man, just wanted to say thanks for the ADB drivers and USB drivers! My device is now successfully rooted
However, I've ran into another problem. When continuing through the bootloader process, when I'm supposed to downgrade to 10.2.4, I'm supposed to enter the fastboot command to flash the bootloader, command prompt just hangs at <waiting for device>...
I've read through the thread about this message, but I couldn't find a clear answer, as it seems some people have succeed with AND without a fastboot cable for this part :/
Any suggestions?
Sent from my LG-LS970 using xda app-developers app
iamterence said:
Hey man, just wanted to say thanks for the ADB drivers and USB drivers! My device is now successfully rooted
However, I've ran into another problem. When continuing through the bootloader process, when I'm supposed to downgrade to 10.2.4, I'm supposed to enter the fastboot command to flash the bootloader, command prompt just hangs at <waiting for device>...
I've read through the thread about this message, but I couldn't find a clear answer, as it seems some people have succeed with AND without a fastboot cable for this part :/
Any suggestions?
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
You can still do everything through the ADB shell. Using fastboot isn't really necessary, but you'll have to be really careful.
soupmagnet said:
You can still do everything through the ADB shell. Using fastboot isn't really necessary, but you'll have to be really careful.
Click to expand...
Click to collapse
Thank you for the response. Is there a guide somewhere I can use that explains how to issue the adb commands instead of going through fastboot?
*EDIT*
Dug around for a bit and stumbled across this. Would these be the correct commands for going through adb?
" Put them in the same directory as adb and open up cmd
cd to the directory with adb and issue the commands:
adb push otter2-freedom-boot.img /sdcard/
adb push otter2-twrp-2.4.4.0-recovery.img /sdcard/
adb shell
su
dd if=/sdcard/otter2-freedom-boot.img of=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot
dd if=/sdcard/otter2-twrp-2.4.4.0-recovery.img of=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery
reboot"
Sent from my LG-LS970 using xda app-developers app
iamterence said:
Thank you for the response. Is there a guide somewhere I can use that explains how to issue the adb commands instead of going through fastboot?
*EDIT*
Dug around for a bit and stumbled across this. Would these be the correct commands for going through adb?
" Put them in the same directory as adb and open up cmd
cd to the directory with adb and issue the commands:
adb push otter2-freedom-boot.img /sdcard/
adb push otter2-twrp-2.4.4.0-recovery.img /sdcard/
adb shell
su
dd if=/sdcard/otter2-freedom-boot.img of=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot
dd if=/sdcard/otter2-twrp-2.4.4.0-recovery.img of=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery
reboot"
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
Close. Asuming your device is already rooted, you created your backups, AND flashed the stack override, you still need to downgrade the bootloader.
Code:
adb push otter2-u-boot-prod-10.2.4.bin /sdcard/
adb push otter2-freedom-boot.img /sdcard/
adb push otter2-twrp-2.4.4.0-recovery.img /sdcard/
adb shell
su
dd if=/sdcard/otter2-u-boot-prod-10.2.4.bin of=/dev/block/platform/omap/omap_hsmmc.1/by-name/bootloader
dd if=/sdcard/otter2-freedom-boot.img of=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot
dd if=/sdcard/otter2-twrp-2.4.4.0-recovery.img of=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery
reboot
Be sure do check the md5s of all downloads before flashing though
soupmagnet said:
Close. Asuming your device is already rooted, you created your backups, AND flashed the stack override, you still need to downgrade the bootloader.
Code:
adb push otter2-u-boot-prod-10.2.4.bin /sdcard/
adb push otter2-freedom-boot.img /sdcard/
adb push otter2-twrp-2.4.4.0-recovery.img /sdcard/
adb shell
su
dd if=/sdcard/otter2-u-boot-prod-10.2.4.bin of=/dev/block/platform/omap/omap_hsmmc.1/by-name/bootloader
dd if=/sdcard/otter2-freedom-boot.img of=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot
dd if=/sdcard/otter2-twrp-2.4.4.0-recovery.img of=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery
reboot
Be sure do check the md5s of all downloads before flashing though
Click to expand...
Click to collapse
Thank you, will try a little bit later in the day. One more question, do I no longer need the FMKilo apk? I've been seeing in other threads that the apk has been bricking devices, but v4 may or may not work. And its not mentioned in the 2nd bootloader thread, so I'm just a bit confused. Should I still download and run v4 after downgrading bootloader and installing TWRP, or should I just downgrade, install TWRP, and immediately flash CM + gapps from there? Wanna get all the clear information I can.
Sent from my LG-LS970 using xda app-developers app
Bump. Waiting for an answer before I continue with this.
Sent from my LG-LS970 using xda app-developers app
*UPDATE*
HOT DAMN! I AM RUNNING CM10.1!!!
So what I did was download all the needed files, and used the fixed commands posted above by Soup to adb push them to the device, then proceeded with did commands to flash them to the device. I made damn sure that the file names matched that of those in the commands, inputted them one by one, rebooted and was greeted by the blue Kindle Fire logo, where I was able to cycle through the options to get to recovery. Immediately wiped everything in TWRP, and flashed CM and gapps. Up and running! This tablet is soooooo much better with AOSP running on it. Thank you, Stunts and Soup for helping me out.
And this was all done WITHOUT a fastboot cable. It was extremely dangerous and risky, but I made it through unharmed.
Sent from my Amazon Kindle Fire2 using xda app-developers app
soupmagnet said:
Close. Asuming your device is already rooted, you created your backups, AND flashed the stack override, you still need to downgrade the bootloader.
Code:
adb push otter2-u-boot-prod-10.2.4.bin /sdcard/
adb push otter2-freedom-boot.img /sdcard/
adb push otter2-twrp-2.4.4.0-recovery.img /sdcard/
adb shell
su
dd if=/sdcard/otter2-u-boot-prod-10.2.4.bin of=/dev/block/platform/omap/omap_hsmmc.1/by-name/bootloader
dd if=/sdcard/otter2-freedom-boot.img of=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot
dd if=/sdcard/otter2-twrp-2.4.4.0-recovery.img of=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery
reboot
Be sure do check the md5s of all downloads before flashing though
Click to expand...
Click to collapse
Please tell me, what if I use this image otter2-twrp-2.6.3.0-recovery.img instead of this otter2-twrp-2.4.4.0-recovery.img?
I use the zip-otter2-twrp-2.6.3.0-recovery.zip here. Just make sure your file shows the name you used.
Sent from my Amazon Kindle Fire2 using xda app-developers app
not 6.3.2
kindle fire utility boot status unknown
adb is online..how to looting?
Use Kindle Fire Utility to root.
Sent from my XT894 using Tapatalk
sd_shadow said:
Use Kindle Fire Utility to root.
Sent from my XT894 using Tapatalk
Click to expand...
Click to collapse
I've been trying last night and today, and it won't work. The version is 6.3.3. Drivers are fine, shows up as Android Composite ADB Interface in device manager on windows 7. I can access the Kindle as a drive on my PC. When I run Kindle Fire Utility 0.9.9, it reports
ADB Status: Online
Boot Status: Unknown.
If I try to either manually set fastboot with option 1 Bootmode Menu, or try to "Install Permanent Root with Superuser" option 2, it has
Installing Permanent Root
Activating Fastboot (4002)
5090 KB/s (510876 bytes in 0.09x) then this:
couldn't write bp1, panic!
finds twrp.img, and downloads fff.bin. Then the kindle reboots, KFU says "Installing FFF..." and <waiting for device>.
But then does nothing, even after I swipe the lock and go back into file transfer mode on the kindle.
Anything I try to do reports "couldn't write bp1, panic!" on KFU. I have another kindle that rooted fine, this one just refuses to.
Any ideas?
AviatorDave said:
I've been trying last night and today, and it won't work. The version is 6.3.3. Drivers are fine, shows up as Android Composite ADB Interface in device manager on windows 7. I can access the Kindle as a drive on my PC. When I run Kindle Fire Utility 0.9.9, it reports
ADB Status: Online
Boot Status: Unknown.
If I try to either manually set fastboot with option 1 Bootmode Menu, or try to "Install Permanent Root with Superuser" option 2, it has
Installing Permanent Root
Activating Fastboot (4002)
5090 KB/s (510876 bytes in 0.09x) then this:
couldn't write bp1, panic!
finds twrp.img, and downloads fff.bin. Then the kindle reboots, KFU says "Installing FFF..." and <waiting for device>.
But then does nothing, even after I swipe the lock and go back into file transfer mode on the kindle.
Anything I try to do reports "couldn't write bp1, panic!" on KFU. I have another kindle that rooted fine, this one just refuses to.
Any ideas?
Click to expand...
Click to collapse
You have another kindle that has 6.3.3 that rooted with no issues? Just curious. Planning on rooting mine as well and looking for any insight as I don't want to brick my device since it updated to 6.3.3 on me.
nathan.stanford said:
You have another kindle that has 6.3.3 that rooted with no issues? Just curious. Planning on rooting mine as well and looking for any insight as I don't want to brick my device since it updated to 6.3.3 on me.
Click to expand...
Click to collapse
Yes, I actually had 2 of them that rooted fine. They are all KF HD 7" First Generation. This one just won't. I'm now working with the KF First Aide tool kit, and I now get SU: ACCESS DENIED or something like that. Communication with ADB is fine, there's a permission issue somewhere I can't figure out.
Towelroot.com
Sent from my SCH-I545 using Tapatalk
joshuabg said:
Http://Towelroot.com
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2783157
Sent from my XT894 using Tapatalk
---------- Post added at 01:34 PM ---------- Previous post was at 01:33 PM ----------
Think your link has an extra http://
Sent from my XT894 using Tapatalk
sd_shadow said:
http://forum.xda-developers.com/showthread.php?t=2783157
Sent from my XT894 using Tapatalk
---------- Post added at 01:34 PM ---------- Previous post was at 01:33 PM ----------
Think your link has an extra http://
Sent from my XT894 using Tapatalk
Click to expand...
Click to collapse
Hmmm. Downloaded it, installed it. The "make it rain" button that says it will reboot my device does not.
Rooting Kindle running 6.3.3
so you have successfully rooted a kindle fire hd running 6.3.3? I have spent all day trying to figure out how to root mine and install a version of jelly bean. Could you point me in the direction of what versions of jellybean/kindle fire utility to use? i have tried using kf utility 0.9.9 and i have the same issue as you where it says the device is online but the boot status is unknown. Thx for the help.
Rob251 said:
so you have successfully rooted a kindle fire hd running 6.3.3? I have spent all day trying to figure out how to root mine and install a version of jelly bean. Could you point me in the direction of what versions of jellybean/kindle fire utility to use? i have tried using kf utility 0.9.9 and i have the same issue as you where it says the device is online but the boot status is unknown. Thx for the help.
Click to expand...
Click to collapse
Awww crapola. Nevermind. All I knew was that both of them were on 6.3.3, so I thought that was what they've always been on. Bzzzzt. The one that was working still has the adw launcher installed, but it doesn't have root any more. So THAT'S why KFU doesn't work on this new one.
They are my girlfriend's kids' kindles, and I told her not to ever update them, but I guess this one was pushed out.
So.... how long until theres a root kit for 6.3.3?
AviatorDave said:
Awww crapola. Nevermind. All I knew was that both of them were on 6.3.3, so I thought that was what they've always been on. Bzzzzt. The one that was working still has the adw launcher installed, but it doesn't have root any more. So THAT'S why KFU doesn't work on this new one.
They are my girlfriend's kids' kindles, and I told her not to ever update them, but I guess this one was pushed out.
So.... how long until theres a root kit for 6.3.3?
Click to expand...
Click to collapse
Hopefully soon, i heard towelroot this new program/website that roots a bunch of devices may work. have you heard anything about it? i dont want to brick my kindle.
Rob251 said:
Hopefully soon, i heard towelroot this new program/website that roots a bunch of devices may work. have you heard anything about it? i dont want to brick my kindle.
Click to expand...
Click to collapse
Didn't brick it, but didn't work either. The apk installs just fine, but when I click the "make it rain" button that says the device will reboot, nothing happens. The device does not reboot, and is not rooted. I tried rebooting the kindle and trying again with the same result. I guess I now fit the definition of insanity.
AviatorDave said:
Didn't brick it, but didn't work either. The apk installs just fine, but when I click the "make it rain" button that says the device will reboot, nothing happens. The device does not reboot, and is not rooted. I tried rebooting the kindle and trying again with the same result. I guess I now fit the definition of insanity.
Click to expand...
Click to collapse
And... tried V2 of towelroot this morning. Still no worky-worky.
Somebody get a straitjacket.
Old rooting methods not working yah...
What I have done -
1. fastboot using factory cable
2. install TWRP+FFF with KFU
3.flash modified pre-rooted ROM
If Amazon continues updating 1st gen, not sure there are lots of enthusiasts, who would continue rooting it. Thus decided to switch to alternative ROM. Well, stock is better for battery etc... etc... but as I do also have HDX and most of time use it, having stock ROM on 1st gen is not as crucial for me.
According to this post (and the post above^^), if you have a factory cable (special cable used to power on in bootloader mode), you can revert to a custom recovery and bootloader and then flash a 6.3.2 ROM. Problem then is avoiding another OTA.
http://forum.xda-developers.com/showpost.php?p=53532982&postcount=2
my fff said:
in cmd driver number showing.but in kfu boot status unknown...adb driver composit installed..
why that? kfu trouble?kindle version 6.3.3 is 6.3.2 same thing?
Click to expand...
Click to collapse
see firmware 6.3.3 -=Post your rooting progress here=-
---------- Post added at 08:37 AM ---------- Previous post was at 08:36 AM ----------
Please don't just start a new thread, when you don't get the answer you want.
my fff said:
Not Kfu. In cmd kindle fire tooting
Click to expand...
Click to collapse
no toot for 6.3.3, cmd other otherwise
To root new update 6.3.3, you need a fastboot/factory cable, adb/ fastboot.exe files, FFF bootloader.bin, twrp.img, and my prerooted 6.3.3 zip
Kindle Fire Utility does not work with 6.3.3 update
Sent from my XT894 using Tapatalk
Sorry if this is a repost but I couldn't find anything on the subject.
I just got my Kindle Fire (1st gen) today and was toying around with it. It was connected to my wifi and then without prompting me shut off and began updating. I knew that there was no root for it so I turned the kindle off by holding the power button while it was updating. Is there any way for me to disable the update without powering it on the whole way?
It currently has 6.3.2 and I don't want to update to 6.3.3
I am aware that you can root 6.3.3 but from my understanding it requires a factory cable which I currently do not have.
Thank you
Update: I did some more digging and saw that it could be rooted but could not install a custom recovery without a factory cable. My apologies.
iAlec said:
Sorry if this is a repost but I couldn't find anything on the subject.
I just got my Kindle Fire (1st gen) today and was toying around with it. It was connected to my wifi and then without prompting me shut off and began updating. I knew that there was no root for it so I turned the kindle off by holding the power button while it was updating. Is there any way for me to disable the update without powering it on the whole way?
It currently has 6.3.2 and I don't want to update to 6.3.3
I am aware that you can root 6.3.3 but from my understanding it requires a factory cable which I currently do not have.
Thank you
Update: I did some more digging and saw that it could be rooted but could not install a custom recovery without a factory cable. My apologies.
Click to expand...
Click to collapse
I would never shut off any operating system in the middle of an update. It is trouble. I wish you the best, but I think you should be purchasing a factory cable.
Not sure what will happen when you power back on.
Could download kindle fire utility, start run.bat
Connect kindle, to PC, it should power on when connected.
See what happens.
Bad idea to power off in the middle of installing firmware.
Sent from my DROIDX using Tapatalk
---------- Post added at 08:48 PM ---------- Previous post was at 08:47 PM ----------
And yes saferoot will root 6.3.3, but still need fastboot cable for fff/twrp/roms
Sent from my DROIDX using Tapatalk
sd_shadow said:
Not sure what will happen when you power back on.
Could download kindle fire utility, start run.bat
Connect kindle, to PC, it should power on when connected.
See what happens.
Bad idea to power off in the middle of installing firmware.
Sent from my DROIDX using Tapatalk
---------- Post added at 08:48 PM ---------- Previous post was at 08:47 PM ----------
And yes saferoot will root 6.3.3, but still need fastboot cable for fff/twrp/roms
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
Unless someone overhauls Smirkit http://forum.xda-developers.com/showthread.php?t=1500935 .
Thepooch said:
Unless someone overhauls Smirkit http://forum.xda-developers.com/showthread.php?t=1500935 .
Click to expand...
Click to collapse
I hope so haha. I just got my Kindle Fire and do not have the ability to get a factory cable at this time
Check this out:
http://forum.xda-developers.com/showthread.php?t=2817362
Sent from my Amazon OtterX using XDA Free mobile app
Ixthusdan said:
Check this out:
http://forum.xda-developers.com/showthread.php?t=2817362
Sent from my Amazon OtterX using XDA Free mobile app
Click to expand...
Click to collapse
Maybe you could push fbmode can't test it my device is so far from stock never going back My point about smirkit is fastboot is not needed it writes bootloader and recovery from a running system. The only prerequisites are superuser or supersu, busybox with .sh working, terminal emulator and smirkit of course.
Neither fbmode nor smirkit work with 6.3.3
Sent from my DROIDX using Tapatalk
sd_shadow said:
Neither fbmode nor smirkit work with 6.3.3
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
So it won't work? That's too bad I got really excited for a minute haha
iAlec said:
So it won't work? That's too bad I got really excited for a minute haha
Click to expand...
Click to collapse
maybe someone can edit files or method, but I did not get any positive results.
sd_shadow said:
maybe someone can edit files or method, but I did not get any positive results.
Click to expand...
Click to collapse
I just tried it. I got it into fastboot mode but I couldn't install FFF (got stuck after step 4 in the second half of the post)
iAlec said:
I just tried it. I got it into fastboot mode but I couldn't install FFF (got stuck after step 4 in the second half of the post)
Click to expand...
Click to collapse
You sure kindle did not just reboot?
Sent from my DROIDX using Tapatalk
sd_shadow said:
You sure kindle did not just reboot?
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
It hung there for ~15 minutes. I'll try again tomorrow but didn't seem to get anywhere tonight.
iAlec said:
It hung there for ~15 minutes. I'll try again tomorrow but didn't seem to get anywhere tonight.
Click to expand...
Click to collapse
If it is fastboot kindle fire utility may work
Sent from my DROIDX using Tapatalk
sd_shadow said:
If it is fastboot kindle fire utility may work
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
Yeah I got it out using KFU so I'll just try again tomorrow. Thanks
iAlec said:
I just tried it. I got it into fastboot mode but I couldn't install FFF (got stuck after step 4 in the second half of the post)
Click to expand...
Click to collapse
You sure kindle updated to 6.3.3, checked system version?
Sent from my DROIDX using Tapatalk
Positive. And I don't have a factory cable.
Sent from my Note 3 using Tapatalk
iAlec said:
Positive. And I don't have a factory cable.
Sent from my Note 3 using Tapatalk
Click to expand...
Click to collapse
Yep it works I just need different commands
my steps
I just did
Step 1: Root the kindle fire
Step 2: Download fbmode
Step 3: Install fbmode by using adb push fbmode /data/local/tmp
Step 4: Set fbmode permissions by using: adb shell chmod 755 /data/local/tmp/fbmode
Step 5: Run these commands here:
Code:
adb shell
su
cd /data/local/tmp
./fbmode
exit
exit
Kindle reboots to fastboot mode
6. downloaded openrecovery-twrp-2.2.2.1-blaze.img and fff-u-boot_v1.5.bin
7. placed in adb folder
8. ran these command in command prompt
Code:
fastboot -i 0x1949 flash recovery openrecovery-twrp-2.2.2.1-blaze.img
fastboot -i 0x1949 flash bootloader fff-u-boot_v1.5.bin
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
9.done
Awesome I'll give this a try. Can you explain how you put those files from step 6 into the adb folder? I'm new to Android so I'm a little confused.
Sent from my Note 3 using Tapatalk
iAlec said:
Awesome I'll give this a try. Can you explain how you put those files from step 6 into the adb folder? I'm new to Android.
Sent from my Note 3 using Tapatalk
Click to expand...
Click to collapse
I just use these files adb-fastboot.zip mirrors unzip and move (AdbWinUsbApi.dll, AdbWinApi.dll, adb.exe, fastboot.exe) to a folder in c drive named adb.
Also move fbmode, FFF, and TWRP. Be sure to verify md5 checksums for FFF and TWRP flashing a corrupt Bootloader is bad.