I just need a tester for a small idea i have for installing twrp recovery and 2nd bootloader in a safer manner than usual. The other manners are pretty safe but i figured this seemed really safe because its so simplistic in nature. I don't know whether i will continue this project depending on the results of the test, but basically i thought why not make a 2nd init/bootstrapped twrp that runs a ota update on a zip file that just installs everything for you with a conveniently placed zip file with asserts that it checks for then deletes itself. My first test is just for a 2012 kfhd 7" that either has no 2nd bootloader + twrp and a fastboot cable handy to restore in case this soft bricks it or one with a version of twrp already installed that it higher than 2.6.0.0. I don't wanna post the actual file because i don't want accidental bricks. Chances are based on how this works it will probably brick the first time around because i have not messed with the hijack scripts to mount everything properly yet, but this was taken from another omap based device so if it doesn't work i don't think it will take too much tweaking, but the initial binary it tries to run may cause some havok. I can assure you this should be easy to restore from in twrp by simply renaming a system file, otherwise without a copy of twrp already installed you will have to restore with kffa. I need the kindle that this is being tested on to also be on a rooted amazon os, not another rom. I have no idea if twrp will work with amazon's stock kernel so this should be interesting. post back if you are interested.
If you are wondering why i didn't decide to test this on my own first its simply because i don't feel like having to wipe my entire data partition and restore the data from my pc just to clear selinux xattribs off my data partition so that amazon's kernel will not throw a fit.
So overview for those that don't want to read that big paragraph:
Requirements:
-Running Amazon OS with root
-Have a way to recover from brick (2nd bootloader + twrp or flash back with kffa/srt) - twrp preferred but plz have a never version than 2.6.0.0 installed.
-Have busybox installed
stunts513 said:
I just need a tester for a small idea i have for installing twrp recovery and 2nd bootloader in a safer manner than usual. The other manners are pretty safe but i figured this seemed really safe because its so simplistic in nature. I don't know whether i will continue this project depending on the results of the test, but basically i thought why not make a 2nd init/bootstrapped twrp that runs a ota update on a zip file that just installs everything for you with a conveniently placed zip file with asserts that it checks for then deletes itself. My first test is just for a 2012 kfhd 7" that either has no 2nd bootloader + twrp and a fastboot cable handy to restore in case this soft bricks it or one with a version of twrp already installed that it higher than 2.6.0.0. I don't wanna post the actual file because i don't want accidental bricks. Chances are based on how this works it will probably brick the first time around because i have not messed with the hijack scripts to mount everything properly yet, but this was taken from another omap based device so if it doesn't work i don't think it will take too much tweaking, but the initial binary it tries to run may cause some havok. I can assure you this should be easy to restore from in twrp by simply renaming a system file, otherwise without a copy of twrp already installed you will have to restore with kffa. I need the kindle that this is being tested on to also be on a rooted amazon os, not another rom. I have no idea if twrp will work with amazon's stock kernel so this should be interesting. post back if you are interested.
If you are wondering why i didn't decide to test this on my own first its simply because i don't feel like having to wipe my entire data partition and restore the data from my pc just to clear selinux xattribs off my data partition so that amazon's kernel will not throw a fit.
So overview for those that don't want to read that big paragraph:
Requirements:
-Running Amazon OS with root
-Have a way to recover from brick (2nd bootloader + twrp or flash back with kffa/srt) - twrp preferred but plz have a never version than 2.6.0.0 installed.
-Have busybox installed
Click to expand...
Click to collapse
If I can get my Kindle back up and running, I'll have a go at it for you. But that's a pretty big if right now.
Sent from my iPod touch using Tapatalk, somewhere in the time vortex
Ok thanks, kinda surprised no one has offered before you. This had over 100 views. I guess not too many people are using amazon os that are willing to risk a softbrick. Hopefully this will work I think it is a bit safer than the other methods for beginners that don't want to risk anything.
Tapatalk is annoying me to no end lately... Had to type this message again because quick reply is being glitchy.
Sent from my Amazon Tate using Tapatalk
I could also volunteer. I have an extra Kindle fire 7" Hd. It is rooted and running 7.4.8. I have my trusty fastboot cable and I already have system images for a quick restore.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
The safest method is to "fastboot -i 0x1949 flash bootloader oldbootloader.bin" then "fastboot -i 0x1949 reboot" (assuming you're using the cable and it auto-kicks you into bootloader mode again) "fastboot -i 0x1949 flash recovery twrp.img" and finally "fastboot -i 0x1949 oem recovery"
Edit: This is a more complex version of Hashcode's method, posted on the cm11 installation instructions page.
Sent from my Nexus 7 using Tapatalk
Yea but the thing about that method is sometimes people have bad downloads and don't check for md5sums(not to mention tons of people always having driver issues). If everything is in a signed zip file then if the signature verification fails its about the same as a bad md5sum, not to mention I can add a md5sum comparison in the update-tools script. I was just wanting to make a one click bootloader install option that comes from an apk, kinda like fire flash but simpler.
Sent from my Amazon Tate using Tapatalk
So you're suggesting using an OpenRecoveryScript to flash twrp, the old bootloader, and apply the stack override file to allow for that "2nd boot loader" hack?
Theoretically, that should work, but Amazon might have put restrictions on the recovery to only allow Amazon-signed zip files so that something like this couldn't happen.
Sent from my Nexus 7 using Tapatalk
I thought only Amazon's recovery would have issues with the signature, even if tarp does I can just disable the signature check and use the update-script to check the md5sum before flashing.
Sent from my LG-P769 using Tapatalk
stunts513 said:
I thought only Amazon's recovery would have issues with the signature, even if tarp does I can just disable the signature check and use the update-script to check the md5sum before flashing.
Sent from my LG-P769 using Tapatalk
Click to expand...
Click to collapse
If TWRP is required, doesn't that make this pointless, because you need the 2nd bootloader hack to make twrp work in the first place? Or perhaps I'm just misunderstanding...
EDIT: when I have the time, I'll see if I can manage to recover from my weird semi-brick and if so, I'll revert to stock and help you test.
Sent from my Nexus 7 using Tapatalk
Thanks, and what I,m saying is you run twrp through 2nd init. I have done it on my phone before, has the same hardware as a kf1 with twice as much ram. I have not seen tarp implemented in this manner before though, only cwm, that's another reason I wanted to test this idea.
Sent from my Amazon Tate using Tapatalk
stunts513 said:
Thanks, and what I,m saying is you run twrp through 2nd init. I have done it on my phone before, has the same hardware as a kf1 with twice as much ram. I have not seen tarp implemented in this manner before though, only cwm, that's another reason I wanted to test this idea.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
Oh. You mean a FakeFlash? That's when you flash a zip that actually just overlays a second recovery. Ex. Flashing a TWRP FakeFlash would allow you to use TWRP from the stock recovery without replacing the installed recovery.
Sent from my Nexus 7 using Tapatalk
r3pwn said:
Oh. You mean a FakeFlash? That's when you flash a zip that actually just overlays a second recovery. Ex. Flashing a TWRP FakeFlash would allow you to use TWRP from the stock recovery without replacing the installed recovery.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
That kinda sounds like it, for a more detailed explanation, this is what i'm basing it off of: http://forum.xda-developers.com/showthread.php?t=2095825
I believe thats the right link. Had to search for it so it might not be but i think it is.
stunts513 said:
That kinda sounds like it, for a more detailed explanation, this is what i'm basing it off of: http://forum.xda-developers.com/showthread.php?t=2095825
I believe thats the right link. Had to search for it so it might not be but i think it is.
Click to expand...
Click to collapse
Kindle's back up and running, I'll test it.
>>>Sent from my homebuilt TARDIS running Android 4.4... or maybe it's a Kindle Fire HD running Cyanogenmod 11<<<
Ok I'll upload it tomorrow. I was just checking my notifications. On a side note I left my kindle in the car and woke and woke up and realized it, having to use my phone to check messages because I will cause a domino reaction if I open the front door... it starts with dogs waking up...
Sent from my LG-P769 using Tapatalk
Sorry I haven't uploaded it yet, i will upload it when I have a chance, my weekend has been chaotic because I've been having to prepare for the job I am starting training for tomorrow. I have been meaning to do it but I hit another snag when I finally got some time to myself I told Ubuntu to upgrade to 14.04 and then unity surprised me and now apparently can't set the window buttons to right so I feel like i'm using a mac which I do not like at all so I decided to use mate since its pretty much what mynfavorite Ubuntu distribution had 10.04lts) so I have been spending the better part of the day reconfiguring it so it was more so like Ubuntu 10.04's theme but I modernized it a bit. Still not done with the theme yet but it is much much better. I think I'm going to attempt to add transparency to the theme. Just realized how off topic i went. Anyways I will see about uploading it tomorrow after I get off of work.
Sent from my Amazon Tate using Tapatalk
Related
Just was wondering. I'm more used to what clockworkmod has so I figured it would be easier to install that instead. But I wanted to make sure it was supported before I went ahead and installed it. Anyone know?
Yes. ClockworkMod works just fine on the Kindle Fiya. there is no looking back now.
androidcues said:
Yes. ClockworkMod works just fine on the Kindle Fiya. there is no looking back now.
Click to expand...
Click to collapse
awesome. so i'm ok with installing it straight from rom manager right?
i'm a little paranoid bc a lot of people seem to be posting about bricking their fires.
Unknown. But if you follow the "bricked fire" threads, you'll see that most people find ways to get them back. So I think a lot of folks are at times stuck, but not truly bricked. I think the most common problem, and the one that bit me too - is being stuck in fastboot and therefore having the device not accessible by adb. And they, like me, panic a bit and think they've bricked it. Granted, I'm sure there are ways of truly bricking it, but as long as you're patient, I think KFU and the fastboot command can get you out of most problems.
gadgetman13 said:
Unknown. But if you follow the "bricked fire" threads, you'll see that most people find ways to get them back. So I think a lot of folks are at times stuck, but not truly bricked. I think the most common problem, and the one that bit me too - is being stuck in fastboot and therefore having the device not accessible by adb. And they, like me, panic a bit and think they've bricked it. Granted, I'm sure there are ways of truly bricking it, but as long as you're patient, I think KFU and the fastboot command can get you out of most problems.
Click to expand...
Click to collapse
thanks man, gonna go ahead and do it in a bit. fingers crossed .
Where do you find the CWM files to download?
Sent from my Kindle Fire using Tapatalk
Bmcd37 said:
Where do you find the CWM files to download?
Sent from my Kindle Fire using Tapatalk
Click to expand...
Click to collapse
it installs when you start up rom manager for the first time
EDIT: Woops, just went to install it and it says it's not officially supported yet. Anyone know where to get it?
Looks like there's more to it. Guess I'm gonna be going by this guide to install early CM9:
http://liliputing.com/2011/12/how-to-install-cyanogenmod-7-on-the-amazon-kindle-fire.html
HeliosAI said:
it installs when you start up rom manager for the first time
EDIT: Woops, just went to install it and it says it's not officially supported yet. Anyone know where to get it?
Click to expand...
Click to collapse
I thought CWM required the use of hardware buttons?
HeliosAI said:
Looks like there's more to it. Guess I'm gonna be going by this guide to install early CM9:
http://liliputing.com/2011/12/how-to-install-cyanogenmod-7-on-the-amazon-kindle-fire.html
Click to expand...
Click to collapse
Go to the development section. It says beta but its solid, I did most of the alpha testing for it and doom lord did the port. Is not officially supported by koush. If you know how to use fastboot, you can't fastboot flash recovery.img if u can't figure it out pm me. I'll get u going.
Sent from my Amazon Kindle Fire using xda premium
smirkis said:
Go to the development section. It says beta but its solid, I did most of the alpha testing for it and doom lord did the port. Is not officially supported by koush. If you know how to use fastboot, you can't fastboot flash recovery.img if u can't figure it out pm me. I'll get u going.
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
Agreed. Doomlord's CWM recovery port is awesome. It's touch based and I've tried most every feature and it seems very solid. I installed it in a much easier fashion than most... I just copied it to my SD area and used the dd command to put a copy into the recovery partition. I did this during normal operation of the Kindle.... No fastboot necessary in using that method. Neall.
.
ndoren said:
Agreed. Doomlord's CWM recovery port is awesome. It's touch based and I've tried most every feature and it seems very solid. I installed it in a much easier fashion than most... I just copied it to my SD area and used the dd command to put a copy into the recovery partition. I did this during normal operation of the Kindle.... No fastboot necessary in using that method. Neall.
.
Click to expand...
Click to collapse
That method is sketch. Fastboot is the proper way to flash a recovery. Any other way you risk trouble. Wear your rubbers and use the fastboot binary.
androidcues said:
That method is sketch. Fastboot is the proper way to flash a recovery. Any other way you risk trouble. Wear your rubbers and use the fastboot binary.
Click to expand...
Click to collapse
its not sketch, just no room for error.
put recovery.img on the root of ur SD card, than open mobile terminal, than type these commands.
su (enter)
dd if=/sdcard/recovery.img of=/dev/block/platform/mmci-omap-hs.1/by-name/recovery (enter)
just don't mistype it, all it does is make a copy directly to the /dev folder.
this is how, rom manager actually puts cwm on ur device.
or use this http://forum.xda-developers.com/showthread.php?t=1500935
Sent from my HTC Glacier using xda premium
Ok, I love my stock/unrooted Kindle Fire. I use it every day as is, but I want to try some of the ROMs out there to make it more of a tablet. I Sideload a number of apps not normally available in the Amazon market which seems fine for now so I'm in no realy hurry... Just things like Swype, Gmail, Play/Marketplace... etc would be nice.
However, In order to try this I have to wipe what I have... I have game saves that I don't want to lose (World of Goo, Plants Vs. Zombies, Peggle... etc.) I usually use Titanium Backup to do this on my phones but without rooting the KF I can't use Ti and it seems that I can't Root without wiping out all my data first.
Unfortunately, the Key Words of "Backup" "Stock" and "Unrooted" returns nearly everything within these forums so if you know a thread for doing this please feel free to direct me there since I can't seem to find a way to separate the wheat from the chaff.
OOps, I just realized I wasn't in Q&A when I posted... Go easy on me it was an honest mistake.
u can make a backup first if u want.
fastboot flash a recovery first.
fastboot flash bootloader
get into recpvery n make a backup immediately. then root after
Sent from my MyTouch 4G using xda premium
smirkis said:
u can make a backup first if u want.
fastboot flash a recovery first.
fastboot flash bootloader
get into recpvery n make a backup immediately. then root after
Sent from my MyTouch 4G using xda premium
Click to expand...
Click to collapse
Sounds easy enough... Reason I am leary is that in a lot of the initial device rooting I've dealt with, the initial recovery and bootloader are loaded along with a ROM which overwrites the data to a version which is rootable. If the Recovery and Bootloader images are seperate and won't touch the data then I would be a happy camper.
In digging further It looks like there is also a temporary root method but I can't confirm if the SU and TiBackup will work properly on a stock Fire with temp root. That would be perfection if they do... anyone without data they can't stand the thought of losing willing to verify?
what temp root? if there was, e would rewrite too methods lol.
we root via fastboot just like the nexus 7.
Sent from my Amazon Kindle Fire using xda premium
smirkis said:
what temp root? if there was, e would rewrite too methods lol.
we root via fastboot just like the nexus 7.
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
There was a method posted in the KF forum for using the Amazon Prime videos and still being rooted. I decided to just go full bore and just rooted/flashing TWRP.
Thanks for the help/suggestions! If I blow something up I'll come back a'lookin.
I see a couple of different tools here to unlock and root my Nexus 7. What are the differences between them?
I do not want to flash ROMs; just unlock, root and install cwm recovery.
Nate2 said:
I see a couple of different tools here to unlock and root my Nexus 7. What are the differences between them?
I do not want to flash ROMs; just unlock, root and install cwm recovery.
Click to expand...
Click to collapse
fastboot oem unlock, fastboot flash cmm recovery, flash the su binaries, reboot and profit.
Search for wugfresh nexus root toolkit. Very simple to use.
Sent from my Nexus 7 using xda premium
frozenspark said:
Search for wugfresh nexus root toolkit. Very simple to use.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Don't use tools for rooting with the Nexus devices, it's useless in my opinion. Try to understand the basics behind rooting, recovery and fastboot, do it manually and you will be able to help yourself even if something is not working as expected.
Sent from my Nexus 7 using xda app-developers app
Use this: http://forum.xda-developers.com/showthread.php?t=1809195
This is the best tool for Nexus 7.
AndDiSa said:
Don't use tools for rooting with the Nexus devices, it's useless in my opinion. Try to understand the basics behind rooting, recovery and fastboot, do it manually and you will be able to help yourself even if something is not working as expected.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Even though I know how fastboot, recovery and rooting works, I still use this tool without any of those commands. And it serve the purpose for me quickly. Of course using such tools will not stop you from learning more afterwards.
I wouldn't say its useless.
Sent from my Nexus 7 using xda premium
frozenspark said:
Even though I know how fastboot, recovery and rooting works, I still use this tool without any of those commands. And it serve the purpose for me quickly. Of course using such tools will not stop you from learning more afterwards.
I wouldn't say its useless.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
then you should br helping out all the people that mess up their devices afyer using toolkits and dont know how to fix it. i havent seen you help out, yet you are still recommending toolkits. why is that?
I used the steps outlined at http://rootzwiki.com/topic/28544-guide-nexus-7-bootloadersrecoveriesrootback-to-stock/ to guide me.
I must say it might not be trivial for the non-software-developer types.
I was a Java developer for many years, so I didn't have much problems setting up Java,
Android-sdk, etc.
My N7 was recognized by adb when booted normally, but after I flashed cwm, I could not do 'adb shell' to mount the /system partition and rename the recovery-from-boot.p file to prevent the recovery from getting reset to stock each time.
I ended up installing the ROM Manager app to enable me to boot into cwm recovery.
I have done the obligatory cwm backup. I believe this is the nandroid backup?
Edit:
I used my Linux box to re-flash the bootloader and cwm recovery images to the Nexus 7, and I could 'adb shell' and rename the recovery-from-boot.p file. So I'm all set now.
I just needed to run 'adb start-server' and 'fastboot' using sudo, so it might have been a permissions issue on my Windows box.
Sent from my unrooted DroidX using Tapatalk
I used Wug's Root Toolkit. Both of the toolkits seem good, but that was just the first one I saw. The Wug's Toolkit is an application and the other one is in a CMD.
Sent from my SGH-T989 using xda premium
Linexus said:
Use this: http://forum.xda-developers.com/showthread.php?t=1809195
This is the best tool for Nexus 7.
Click to expand...
Click to collapse
+1
Absolutely brilliant ToolKit, very simple, fast and works like a charm.
I rooted my N7 with this, and had no issues to date.
Only took a couple of minutes.
BRILLIANT!
Looks like I'm not all set, after all Today, right before I plan to take the JB 4.1.2 OTA update, I notice my tablet won't boot into CWM, like it did a couple of days ago. I did rename the one file and things looked normal. What could have happened to my CWM?
Edit:
So there are 2 files that need to be renamed, not 1?
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
And there was a bug in JB 4.1.1 that prevented booting into cwm recovery unless the device was plugged into USB??
Sent from my Nexus 7 using Tapatalk
I re-flashed the same cwm recovery img, reinstalled the same su zip, and I'm back to normal
Gotta watch out for those OTA updates, I tell ya.
Use the fastboot commands
Good to see you alright!
This is like asking "Should I get an automatic or manual car?"
veeman said:
This is like asking "Should I get an automatic or manual car?"
Click to expand...
Click to collapse
In the early days, automatic transmissions were more problematic and much more expensive. Today they are pretty efficient, even though a manual transmission gives you better control over the car, which most people don't really need for everyday driving.
If you frequently get stuck in stop-and-go traffic, you'll wish you had an automatic transmission.
Look at these lazy people..
Beamed from my Grouper.
Nate2 said:
Looks like I'm not all set, after all Today, right before I plan to take the JB 4.1.2 OTA update, I notice my tablet won't boot into CWM, like it did a couple of days ago. I did rename the one file and things looked normal. What could have happened to my CWM?
Edit:
So there are 2 files that need to be renamed, not 1?
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
And there was a bug in JB 4.1.1 that prevented booting into cwm recovery unless the device was plugged into USB??
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Yes there was a bootloader bug on the nexus 7 and most people could not boot into CWM recovery without plugging it into their computer.
I however used TWRP back then [have since switched back to CWM touch, now that the bug is fixed] and had no issues. Now I have no issues with CWM touch, I can boot it directly from fastboot menu, or "reboot -> recovery" when booted.
Nate2 said:
I re-flashed the same cwm recovery img, reinstalled the same su zip, and I'm back to normal
Gotta watch out for those OTA updates, I tell ya.
Click to expand...
Click to collapse
exactly what I would have done! sounds like you're getting the hang of it. and yes, I definitely recommend manual rooting/fastbooting to a toolkit.
Wilks3y said:
+1
Absolutely brilliant ToolKit, very simple, fast and works like a charm.
I rooted my N7 with this, and had no issues to date.
Only took a couple of minutes.
BRILLIANT!
Click to expand...
Click to collapse
Yes that's my favorite too. It does it all and more. It slices, it dices, it'll even cut a can!
Nate2 said:
In the early days, automatic transmissions were more problematic and much more expensive. Today they are pretty efficient, even though a manual transmission gives you better control over the car, which most people don't really need for everyday driving.
If you frequently get stuck in stop-and-go traffic, you'll wish you had an automatic transmission.
Click to expand...
Click to collapse
Yeah, that's what I'm saying. They both have their ups and downs. If you're willing to learn a little about how Android works and learn some adb and fast boot commands then you should definitely do it manually.
If you just want to be a "1337 Haxorz" and aren't willing to learn then just use a toolkit.
OK, just one sub-question on rooting. I see no real reason to root except maybe to get more tablet interface than nexus has. Kinda like when the wifi indicator is at the bottom, since there are those !$#$$ back/home buttons already and a lot of wasted space Anyways, the question.
I bougth N7 16Gb and upgraded via forced OTA to 4.1.2. Do all these root methods work with 4.1.2?
Thanx,
D.
For the first time I did an OTA while rooted. I upgraded to 4.3 and now I've lost the following:
SuperSU dowsn't work
Busybox does't work
Can't run bootloader or recovery
My system still shows as a rooted system upon boot. When I connect to my pc and run wugfresh's toolkit, it fails to find adb. I have verified that the driver is installed correctly and debugging mode is on. I can't unlock, root or even return to stock. I do remember seing a thread about a similar issue quite some time ago but I have been unable to find ut. Any help will be greatly appreciated.
Btw, it has just a plain root, no custom roms installed.
Thanks in advance.
stator said:
For the first time I did an OTA while rooted. I upgraded to 4.3 and now I've lost the following:
SuperSU dowsn't work
Busybox does't work
Can't run bootloader or recovery
My system still shows as a rooted system upon boot. When I connect to my pc and run wugfresh's toolkit, it fails to find adb. I have verified that the driver is installed correctly and debugging mode is on. I can't unlock, root or even return to stock. I do remember seing a thread about a similar issue quite some time ago but I have been unable to find ut. Any help will be greatly appreciated.
Btw, it has just a plain root, no custom roms installed.
Thanks in advance.
Click to expand...
Click to collapse
Hi, stator...
Your post isn't quite clear... does the device boot normally? If so, you should have no problems booting into the bootloader.
But first download the latest UPDATE-SuperSU-v1.51.zip to your Nexus 7.
Shutdown the Nexus as normal. Then press and hold the VOL down button... whilst continuing to hold, press the POWER ON button.
This should boot you into the bootloader (in fastboot mode).
From there, and from your PC, Fastboot flash a custom recovery... (Chainfire recommends TWRP)... with the line...
Code:
fastboot flash recovery recovery.img
Where recovery.img is the name of your custom recovery. I usually just rename it to 'recovery.img' (without quotes) anyway - makes for less typing at the command prompt.
Ensure you get the correct recovery for your device....
TWRP for Nexus 7 Wi-Fi ('Grouper') or TWRP for Nexus 7 3G ('Tilapia')
Although a new version of TWRP is now available (2.6), I had some weird issues with this... particularly when copying Nandroid backups off of my Nexus 7 to my PC. Random 'permission denied' messages would crop up running an ADB PULL command... copying via MTP didn't fair much better either. TWRP 2.5 works without problems though, and it's the version I would recommend.
Anyway... back on topic...
Upon completion of flashing TWRP, boot into that recovery (whilst still in the bootloader)... and select INSTALL... navigate to the folder where you downloaded Chainfires SU root updater (usually, the 'download' folder)... and SWIPE to confirm.
Reboot as normal... you should now be rooted. This can be confirmed by any one of the numerous Root Checker apps available in Playstore.
I haven't experimented with busybox... if you mean this version, I haven't installed it, and nor am I going to... at least not for a while.
My Nexus 7 is still in the process of being rebuilt from the ground up, after having fastboot flashed the factory image, necessitating a full wipe (I was running a custom ROM/Kernel combo before)... so I'm taking this slowly, re-installing apps carefully.
It seems that some apps that worked fine under 4.2.2 are broken under 4.3. MX Player and Adobe Flash Player to name a couple.... but QuickPic and Titanium have now been fixed and work fine under 4.3. I'm under no illusions that Adobe Flash Player will be fixed anytime soon... it's been technically deprecated by Adobe for a while anyway.
Anyway... good luck... and hope you get root sorted.
Rgrds,
Ged.
I am having problems with Busybox as well even though i did not take the OTA. I flashed CleanRom, and Faux kernel.
Just fyi
Sent from my Nexus 7 using xda premium
First and foremost I would like to apologize for taking so long to reply. Real life had me out of town and I didn't have my tablet with me. I tried the advice given but it didn't work at first. It took multiple attempts but I finally got my tablet back to stock. I guess my Nexus 7 didn't agree with the 4.3
OTA while rooted. I can now unlock, root, and even change roms once again. I don't know for sure what was causing the problem but it's all good now. Also, I was always able to use my tablet during my little crisis. I was just unable to unroot or even flash a new rom. Thanks again for all the help.
You could have hit thanks, a guy wrote you a gigantic step-by-step instructions just to help you out
Sent from my LG-P920 using xda app-developers app
shevich said:
You could have hit thanks, a guy wrote you a gigantic step-by-step instructions just to help you out
Sent from my LG-P920 using xda app-developers app
Click to expand...
Click to collapse
I sincerely hope this is a joke. I most definitely said thanks. I even apologized for taking so long to reply. Please try to be constructive or don't bother to post. I've been frequenting this site for quite sometime although I've never posted or even joined until recently. This community has been extremely helpful. The last thing that is needed is another troll. Thank you.
He was talking about using the thanks button.
Sent from my Galaxy Nexus
I was bored and decided to try to build a rom and see what happens, i don't know any c coding so its a bit of it it compiles and works great, if it doesnt work then i'll need a c compiler and both my friends that know c coding dont get online often.
Anyways about the details, i have sucessfully built a 7" and 8.9" Kindle Fire HD version of the rom, soupmaget is going to test the 8.9" rom, but i need a 7" tester prefereably with a fastboot cable incase things go south like the first time where it deleted the second bootloader from the system partition, though i think i fixed that. Anyways if you are interested in testing this pre-alpha build of the rom, plz reply back and il send you a link in a private message to the rom. On another note te tester should also be prepared to do a full backup of their sdcard of their device including the sdcard because i have not ever used this os so i have no idea how it handles the sdcard data, while it shouldnt wipe it i just think it would be a good idea in general.
I can test it.
I have a fastboot cable and the only files that I have are books anyway.
OK sweet I'll pm you the link with instructions.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
I'm your Huckleberry.
---------- Post added at 04:58 PM ---------- Previous post was at 04:54 PM ----------
stunts513 said:
i need a 7" tester
Click to expand...
Click to collapse
I messed up the quote last time. Anywho, link me if you want.
Sweet I'll pm u too.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Sweet I'll pm u too.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
First test:
Downloaded and flashed just fine. After wiping Dalvik/CACHE and rebooting into system it did show the Kindle Fire Animation followed by the TWRP animation and then displayed fastboot. Holding the power button down for 20 seconds powered it off and access to TWRP was still possible. Flashed a nandroid and all is fine. Let me know when the next update is available.
LinearEquation said:
First test:
Downloaded and flashed just fine. After wiping Dalvik/CACHE and rebooting into system it did show the Kindle Fire Animation followed by the TWRP animation and then displayed fastboot. Holding the power button down for 20 seconds powered it off and access to TWRP was still possible. Flashed a nandroid and all is fine. Let me know when the next update is available.
Click to expand...
Click to collapse
So ok im confused it just went into fastboot after trying to boot or something? If thats the case there must be something very wrong with the kernel i think.
stunts513 said:
So ok im confused it just went into fastboot after trying to boot or something? If thats the case there must be something very wrong with the kernel i think.
Click to expand...
Click to collapse
Correct. The flash was successful (in other words it did not fail.) I click reboot into system from TWRP. I saw the Kindle Fire animation followed by the TWRP animation and then, then stead of the ROM animation, it went strait to fastboot. Then I force powered it down, was able to access TWRP, wiped and then flashed my backup nandroid and the Kindle booted with no permanent issues. But yes, something is not right there.
Basically, rather than booting into the system, it booted into the bootloader.
LinearEquation said:
Correct. The flash was successful (in other words it did not fail.) I click reboot into system from TWRP. I saw the Kindle Fire animation followed by the TWRP animation and then, then stead of the ROM animation, it went strait to fastboot. Then I force powered it down, was able to access TWRP, wiped and then flashed my backup nandroid and the Kindle booted with no permanent issues. But yes, something is not right there.
Basically, rather than booting into the system, it booted into the bootloader.
Click to expand...
Click to collapse
*facepalm* i'm going to have to check the kernel image, this whole setup i used is kinda rigged because this os was designed to work with a specific version of jb aosp, and cm 10.2 is close to that revision but not exact so i used aosp as my source and had to modify some of hashcodes file sto get it to compile, but it finally did compile, seeing as there were problems here and there i'm going to take a wild guess the boot.img is using the standard header and not amazons, and thats just a wild guess at best, i don't know what a normal header would do on a kindle, but i will try to decompile the boot.img and see if it errors out like a usual kindle boot.img would if you dont shave off the header with dd.
Man i hate double posting but i thought i'd mention i think what i guessed at was right because it split immediately upon running the splitting script... so now i guess i need to ask hashcode wtf is going on and how to fix it since it's not compiling the boot.img with the correct header.
Sounds like a plan.
Sent from my Amazon Kindle Fire HD running CM 10.2 using xda app-developers
Well I talked to hashcode, I'm trying to get it fixed, but I'm a bit confused, makefile coding isn't my specialty, I am going to ask other RC's and see what I can dig up.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
hi!!
stunts513 said:
I was bored and decided to try to build a rom and see what happens, i don't know any c coding so its a bit of it it compiles and works great, if it doesnt work then i'll need a c compiler and both my friends that know c coding dont get online often.
Anyways about the details, i have sucessfully built a 7" and 8.9" Kindle Fire HD version of the rom, soupmaget is going to test the 8.9" rom, but i need a 7" tester prefereably with a fastboot cable incase things go south like the first time where it deleted the second bootloader from the system partition, though i think i fixed that. Anyways if you are interested in testing this pre-alpha build of the rom, plz reply back and il send you a link in a private message to the rom. On another note te tester should also be prepared to do a full backup of their sdcard of their device including the sdcard because i have not ever used this os so i have no idea how it handles the sdcard data, while it shouldnt wipe it i just think it would be a good idea in general.
Click to expand...
Click to collapse
send me instructions for the test
I will next time I make a build after fixing this boot.IMG issue I have, I haven't seen hashcode in the IRC since Wednesday and I haven't been able to fix the makefile issue yet, I have to transfer some of the code from cm's /build/core/Makefile to mine, specifically the parts that let's board_custom_booting_mk work to generate the booting correctly. You would think there would be a patch for aosp that does this, but I guess most devices don't need a custom bootimg?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Test
stunts513 said:
I will next time I make a build after fixing this boot.IMG issue I have, I haven't seen hashcode in the IRC since Wednesday and I haven't been able to fix the makefile issue yet, I have to transfer some of the code from cm's /build/core/Makefile to mine, specifically the parts that let's board_custom_booting_mk work to generate the booting correctly. You would think there would be a patch for aosp that does this, but I guess most devices don't need a custom bootimg?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I have understood that the boot.img should go hand in hand with the system you build,
so a custom boot.img should be mandatory
excuse my bad English, I use google translator
Any chance of a build compatible with the kf2?
I'm too broke to buy the newest fire hdx that's on sale for $180 today,so I'm holding on to my 2012 non-hd fire.
Sent from my Amazon Kindle Fire2 using XDA Premium HD app
agentfusion said:
Any chance of a build compatible with the kf2?
I'm too broke to buy the newest fire hdx that's on sale for $180 today,so I'm holding on to my 2012 non-hd fire.
Sent from my Amazon Kindle Fire2 using XDA Premium HD app
Click to expand...
Click to collapse
Keep an eye on Swappa. People are dumping their older models for cash for the newer models.
Sent from my Amazon Kindle Fire HD running CM 11 KitKat 4.4 using xda app-developers
I plan on building it for all supported kf's, right now I'm working out the build kinks and seeing if it will even boot. Just fixed the makefile issue but I may have introduced another issue by using a certain patch to disable recovery a while back, so I may need to grab a fresh copy of the make file and repatch it, I'll pm when it's more ready to test which will be soon.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Send me a PM once you get the boot.img thing fixed. I have a fastboot cable, too.
Sent from my Amazon Kindle Fire HD using xda app-developers app
Hi,
Just for understanding right. Is this for the Kindle Fire HD KFSOWI (3rd gen)?
If yes then I absolutely want to try your Rom.
Thanks in advance.