Kindle Fire 6.3 root - Kindle Fire Android Development

Warning
Below be dragons, please gather armor and basic computing knowledge before preceding </ubergeek>. Working adb AND fastboot are requires, support for adb and fastboot are NOT offered by me. If you question is related to OSX or Linux I may be able to help. If it is windows related, don't get pissed when I tell you "I have no idea", it is the truth.
This is at your own risk! Do not blame me if something goes wrong!
For 6.2, 6.2.1 and 6.2.2 please see BurritoRoot3 -> http://rootzwiki.com/topic/13027-rootbootloader-burritoroot3-kindle-fire-root-easy-root-edition/
While I have another root exploit, Amazon neglected pokey's far more beautiful one this update, and we have no good reason to blow another root for this update, so isntead here is a guide using fbmode.
Full credits for this goes to pokey9000 (see http://forum.xda-developers.com/showthread.php?t=1414832). This guide requires you to have adb and fastboot working FOR THE KINDLE FIRE, on whatever os you are on.
Required files:
fbmode.zip - http://forum.xda-developers.com/showthread.php?t=1414832
twrp2 - http://teamw.in/project/twrp2/79
su - http://dl.dropbox.com/u/8699733/kindlefire/su
firefirefirefire http://forum.xda-developers.com/showthread.php?t=1369405
fastboot + adb for your OS of choice.
unzip fbmode.zip
adb push fbmode /data/local/fbmode
adb shell chmod 755 /data/local/fbmode
adb shell /data/local/fbmode
adb reboot
Your kindle will "get stuck" on the kindle fire screen, but really it's just in fastboot mode.
fastboot -i 0x1949 flash bootloader <name of firefirefire image here>
fastboot -i 0x1949 flash recovery <name of recovery image here>
Your device will now boot into twrp recovery, and flash the firefirefire bootlaoder. When done it will prompt you to reboot. Upon reboot you will get stuck on the "yellow triangle" screen of firefire fire.
fastboot oem idme bootmode 5002
fastboot reboot
Once in recovery
adb shell mount system
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
Lets disable the root check before rebooting
adb shell mv /system/bin/check_rooted /system/bin/check_rooted.bak
adb shell idme bootmode 4000
adb reboot
Once booted into Android, install superuser
adb install Superuser.apk

So this is strictly to add root for someone who is running stock 6.3, correct?
Thanks for the write up.

Once again! You rule.

Your fast! I was gonna suggest pokeys bootmodes before tossing an exploit but u went straight for it lol. Great work jcase
Sent from my Kindle Fire using xda premium

kernelsandirs said:
Once again! You rule.
Click to expand...
Click to collapse
It's pokey's not mine, I just posted up a guide to stop ppl from asking me

smirkis said:
Your fast! I was gonna suggest pokeys bootmodes before tossing an exploit but u went straight for it lol. Great work jcase
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
I flashed back to stock and updated. My "secondary" exploit still exists, but after getting root I decided to check and see if fbmode would still work, and it does.
So we should be good for the next one as well.

Quick question you wonderful people,
Does this work with kinfauns 1.3 firefirefire?
It's basically just pokey9000's with some quirks and a different boot menu but figured I would ask the "big guys" first before I turn into one of those "I bricked my fire" folks. Cheers.

Laquox said:
Quick question you wonderful people,
Does this work with kinfauns 1.3 firefirefire?
It's basically just pokey9000's with some quirks and a different boot menu but figured I would ask the "big guys" first before I turn into one of those "I bricked my fire" folks. Cheers.
Click to expand...
Click to collapse
should work with anything

Wow, it didn't take them long to implement a root check at all. I guess more people are rooting their devices than had previously expected. They're selling them at a loss in the hopes that they will make it up in app store and prime sales. Woops. Oh well, I'm just glad I switched rooms when I did. It won't be long before they make them either unrootable (less likely) or stop selling them altogether (more likely).
Sent from my Amazon Kindle Fire using xda premium

soupmagnet said:
Wow, it didn't take them long to implement a root check at all. I guess more people are rooting their devices than had previously expected. They're selling them at a loss in the hopes that they will make it up in app store and prime sales. Woops. Oh well, I'm just glad I switched rooms when I did. It won't be long before they make them either unrootable (less likely) or stop selling them altogether (more likely).
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
no, every update has "broke" root. amazon does this so that their updates wont brick rooted devices. they haven't done anything to prevent people from rooting.

Worked fine, maybe I misread it or maybe you left out sticking superuser.apk in the adb/fastboot folder? Anywhoo I got root on 6.3 with this method, thanks

jcase said:
should work with anything
Click to expand...
Click to collapse
Indeed it does and I even re-added FFF 1.3 working like a charm. Thank you and pokey9000 for all the hard work!

Another fantastic job! Thanks so much!!

raiderep said:
Worked fine, maybe I misread it or maybe you left out sticking superuser.apk in the adb/fastboot folder? Anywhoo I got root on 6.3 with this method, thanks
Click to expand...
Click to collapse
No, I assume people setup their paths correctly during adb installation, negating the need for that.

BigFuzzyArchon said:
no, every update has "broke" root. amazon does this so that their updates wont brick rooted devices. they haven't done anything to prevent people from rooting.
Click to expand...
Click to collapse
Actually, this is the first time they have implemented something like this, its a separate service that checks for root, they run it at boot.

jcase said:
Actually, this is the first time they have implemented something like this, its a separate service that checks for root, they run it at boot.
Click to expand...
Click to collapse
they run it at boot and do what ?
would be interesting ...

Perhaps a stupid question, but where do I get the "Superuser.apk" used at the end of the instructions under 'adb install Superuser.apk'? Because It wasn't one of the files listed under needed files section. Thanks

daggy1985 said:
Perhaps a stupid question, but where do I get the "Superuser.apk" used at the end of the instructions under 'adb install Superuser.apk'? Because It wasn't one of the files listed under needed files section. Thanks
Click to expand...
Click to collapse
just google for "superuser.apk download" ...

daggy1985 said:
Perhaps a stupid question, but where do I get the "Superuser.apk" used at the end of the instructions under 'adb install Superuser.apk'? Because It wasn't one of the files listed under needed files section. Thanks
Click to expand...
Click to collapse
It's in the OP, just abbreviated as "su."
http://dl.dropbox.com/u/8699733/kindlefire/su

Droidanian said:
It's in the OP, just abbreviated as "su."
http://dl.dropbox.com/u/8699733/kindlefire/su
Click to expand...
Click to collapse
the su command and the superuser.apk are different things
the superuser.apk is a wrapper to su command

Related

[Tool] Downgrade VivoW with hboot 0.98

Windows: Disable or remove all phone, PDA, MP3 sync softwares, including HTC Sync, itunes, and all Antivirus software and suspend all unnecessary processes.
Windows: Install HTC USB Drivers on your PC. http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
64 bit Linux Users: Android tools in the kit are 32 bit. You will need to install ia32-libs (Debian) or equivelent if they are not already installed. Debian/Ubuntu: sudo apt-get install ia32-libs
Get adb and fastboot working on your PC
Start with phone in Charge Only mode, sdcard mounted by phone, not PC, and USB debugging enabled
A kit with everything needed (including adb and fastboot) including scripts. vwhk-12102011-c.zip MD5: 26a2dbcb96d82153add7edaccd157996
IMPORTANT: Run the Linux script as ROOT, run the Windows script as Admin.
Run Revolutionary for S-OFF & CWM if desired after downgrade. http://revolutionary.io/
Notes:
No goldcard needed for Verizon DINC2. If you ask this, you'll get nothing but hate.
Yes, this wipes data and downgrades the ROM completely.
Code:
adb shell rm -r /data/local/tmp/*
adb push zergRush /data/local/tmp/zergRush
adb push misc_version /data/local/tmp/misc_version
adb shell chmod 777 /data/local/tmp/zergRush
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/zergRush
adb shell /data/local/tmp/sh -c '/data/local/tmp/misc_version -s 2.18.605.3'
adb reboot bootloader
fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Radio_1.09.01.0622_NV_VZW1.92_release_199487_signed.zip
fastboot reboot
Thanks to:
Revolutionary - for everything they do
Ch4lky - zergRush
Guhl - misc_version
Trying now
EDIT: I don't want this post to confuse anyone... I missed a step but this worked perfect for me.
loudaccord said:
Trying now
Dumb question... then I can run the regular revolutionary PRE4 to get s-off and install cwm recovery?
stuck on adb shell /data/local/tmp/sh -c '/data/local/tmp/misc_version -s 2.18.605.3'
C:\android-win-tools>adb shell /data/local/tmp/sh -c '/data/local/tmp/misc_versi
on -s 2.18.605.3'
--set_version set. VERSION will be changed to: 2.18.605.3
Patching and backing up partition 17...
Error opening backup file.
C:\android-win-tools>fastboot oem rebootRUU
< waiting for device >
Can't get past there.
Click to expand...
Click to collapse
what happened when you tried to get temproot with zergrush?
was the phone in charge only mode? It needs be to write a backup file to the sdcard.
the < waiting for device > error is because the fastboot driver is not installed or there is contention with some program.
i missed a step; updated code above:
prerequisite: adb and fastboot fully working.
attn1 said:
what happened when you tried to get temproot with zergrush?
was the phone in charge only mode? It needs be to write a backup file to the sdcard.
the < waiting for device > error is because the fastboot driver is not installed or there is contention with some program.
prerequisite: adb and fastboot fully working.
Click to expand...
Click to collapse
Temproot with zergrush said that it was successful, phone is on charge only mode.
looks like fastboot doesn't seem to be working, I have it installed but I'll have to get to the bottom of this.
Any way for me to test if fastboot is working easily?
loudaccord said:
Temproot with zergrush said that it was successful, phone is on charge only mode.
looks like fastboot doesn't seem to be working, I have it installed but I'll have to get to the bottom of this.
Any way for me to test if fastboot is working easily?
Click to expand...
Click to collapse
I missed the adb reboot step. check the code above for where that line goes.
attn1 said:
I missed the adb reboot step. check the code above for where that line goes.
Click to expand...
Click to collapse
cool, trying again
edit... that worked... sending zip now.
edit2: ran through all the commands... going to try to get s-off now. Thanks!
edit3: Success
loudaccord said:
edit3: Success
Click to expand...
Click to collapse
Groovy. Have fun.
Does this mean alpharevx isnt working on a 2.3.4 root? Is this the only way or just a way if you dont want to wait?
Sent from my ADR6350 using xda premium
Bob-o said:
Does this mean alpharevx isnt working on a 2.3.4 root? Is this the only way or just a way if you dont want to wait?
Sent from my ADR6350 using xda premium
Click to expand...
Click to collapse
It means its not working on any hboot other than 0.97
I saw the tool tweeted by AlpharevX. I wasn't sure if it would work for Inc2. I am already rooted, but thank you for writing a guide for us!!!!
subscribing.
so this is a legitimate way to root the .98 dinc2?? is it restore able to stock or is it permanent? thanks
lddrew said:
subscribing.
so this is a legitimate way to root the .98 dinc2?? thanks
Click to expand...
Click to collapse
Yes.
lddrew said:
is it restore able to stock or is it permanent?
Click to expand...
Click to collapse
is question able to muster or is it nonsensical?
disregard that last question, sorry i had read that if rooting it with something other than AlphaRevX that restoring it to stock may be more complicated. sorry about that.
thank you for the info
I know im prolly get flamed for askin this noob question, but how do i get adb and fastboot up on my laptop? I have rooted my fascinate and was good with odin, but im still learnin htc stuff. Thanks in advance.
Bob
Sent from my ADR6350 using xda premium
Bob-o said:
I know im prolly get flamed for askin this noob question, but how do i get adb and fastboot up on my laptop? I have rooted my fascinate and was good with odin, but im still learnin htc stuff. Thanks in advance.
Bob
Sent from my ADR6350 using xda premium
Click to expand...
Click to collapse
Google it..it has step by step instructions on the website
Sent from my Incredible 2 using xda premium
Bob-o said:
I know im prolly get flamed for askin this noob question, but how do i get adb and fastboot up on my laptop? I have rooted my fascinate and was good with odin, but im still learnin htc stuff. Thanks in advance.
Bob
Sent from my ADR6350 using xda premium
Click to expand...
Click to collapse
thats a fair question, but really, the answers are everywhere. I'll make it easy for you. Check back on post 1. I'll update it.
attn1:
You, Sir, are Incredible squared!!(No pun intended ) Do you realize how many searches and web pages I went through in vain before coming to this workaround. Awesome, to say the least. Thanks ever so much for this write up, it is greatly appreciated, and a beer or two (donation) will be coming your way Friday.
I had to get a replacement for my rooted DINC2, and wouldn't you know it, they sent me out one with the 0.98 bootloader. I thought all hope was lost, well, at least until revolutionary found an exploit for the 0.98. This has helped tremendously.
Thanks again ever so much,
Chris
attn1 said:
thats a fair question, but really, the answers are everywhere. I'll make it easy for you. Check back on post 1. I'll update it.
Click to expand...
Click to collapse
Thank you very much.
Sent from my ADR6350 using xda premium
okay i have the folder extracted in my downloads folder, it keeps saying the script location can't be found. i am confused. can you elaborate on the bits about where to put the files and whatnot before you execute the script??
lddrew said:
okay i have the folder extracted in my downloads folder, it keeps saying the script location can't be found. i am confused. can you elaborate on the bits about where to put the files and whatnot before you execute the script??
Click to expand...
Click to collapse
really? open a cmd prompt as admin and run hack-vivow.cmd

[HOWTO] Root Your Stock Galaxy Nexus

This post is now deprecated there are new ways of rooting more easily here is the link to one of those
http://forum.xda-developers.com/showthread.php?t=1392310
just kept for reference
link no longer works as it is a very old boot img, if you wanna go this way use latest superboot
Rooting your Galaxy Nexus
Download this file contains necessary files and also lastest samsung drivers in case you dont have them, probably you need android sdk drivers for fastboot
Download
credit to @peteralfonso for the insecure boot.img which allows this to remount system and this way install su binary and Superuser.apk
This are the instructions for Galaxy Nexus
they require basic knowledge of fastboot adb and using command prompt/terminal
works same way on linux and windows
Be sure to have fastboot and adb ready and working
extract somewhere and you will get 4 files su, Superuser.apk , boot.img and drivers
turn off the phone
Boot into bootloader mode (Vol UP+ Vol Down + Power) then execute this command, be sure to have fastboot and boot.img on same folder or be ready to type a long path pointing to your boot.img
REMINDER: by doing fastboot oem unlock you will completely wipe your device so be sure to backup anything important
execute this command
Code:
fastboot oem unlock
fastboot boot boot.img
edit: thanks chirality forgot the oem unlock
the device will reboot and start in unsafe mode where you can enable adb as root usually on production devices this is not posible
Be sure to enable adb debugging on menu
back to command prompt
Code:
adb root
adb remount
adb push su /system/bin
adb push Superuser.apk /system/app
adb shell chmod 06755 /system/bin/su
adb shell chmod 06755 /system/app/Superuser.apk
adb reboot
and you are done and youve got your Galaxy Nexus rooted
This process does not involve flashing another boot.img, it just boots once with it and after that returns to original boot.img
As usual
YOU ARE PERFORMING THIS AT YOUR OWN RISK! I AM NOT RESPOSIBLE FOR ANY BRICKS OR PROBLEMS!
Which wont happen we are just pushing 2 files to our phone
edit2: sorry for the bad paths of adb was too late and didnt notice my error
Don't you have to do "fastboot oem unlock" first before being able to boot off the insecure image? I thought they fixed that with the Nexus S already.
Thanks for the post - apparently people are having problems with the Superboot method, so I'll give this a go when mine arrives today.
I guess this comes with all the usual "at your own risk" and "will void your warranty" warnings?
(sorry if that's a stupid question - this is my first Nexus, so I'm not sure where I stand on rooting, unlocking bootloaders, and the warranty etc.)
Great - worked without issue for me and I can now use the Entree VPN client for connecting into work. (the HD screen is great for remote desktop work)
Minor typo in the permissions lines though - should read:
adb shell chmod 06755 /system/bin/su
adb shell chmod 06755 /system/app/Superuser.apk
Thanks very much,
Chris.
Thanks for this davioxx for putting together the guide, chriscole for the fixes and @peteralfonso for the insecure boot.img.
I'm now succesfully rooted.
It seems Root Explorer needs an update for the GN though. Only opens in the bottom left corner of the screen for me, and is comprised of static.
Sorry for the newbee question, been quite a while since rooting my nexus one...
Do i need to enable adb debugging on phone menu before executing the fastboot oem unlock code and then enable it again after it reboots and starts in safe mode?
w00t!
Thank you
You may want to change the path names on the chmod part, I blindly followed the instructions and the files were in diffrent places from where I pushed them to
But thanks \o/
I haz root!
Tnx, easy like all nexus devices, now need some you tube for that!
Sent Via My HTC Desire HD
looks pretty simple ... hopefully it will be the same process for us in the States
Not 100% sure what's going on here. I haven't rooted since I got the Nexus One.
When my phone is on and connected, command prompt shows my phone as an attached device. But when I boot into bootloader, it isn't attached anymore and command prompt just tells me that the commands are unrecognized? How come?
majikdragoon said:
Not 100% sure what's going on here. I haven't rooted since I got the Nexus One.
When my phone is on and connected, command prompt shows my phone as an attached device. But when I boot into bootloader, it isn't attached anymore and command prompt just tells me that the commands are unrecognized? How come?
Click to expand...
Click to collapse
Are you doing it via adb or fastboot?
Not sure. I restarted the phone into bootloader and tried to follow the instructions
Hahaha... I was trying to sideload N64oid as it's been removed from the market. I ended up using Android Centrals Sideloader instead.
majikdragoon said:
Not sure. I restarted the phone into bootloader and tried to follow the instructions
Hahaha... I was trying to sideload N64oid as it's been removed from the market. I ended up using Android Centrals Sideloader instead.
Click to expand...
Click to collapse
Hi probably you dont have the bootloader driver installed, that has to be done manually at least for my win 64 machine, check this thread about that
Set Up ADB, fastboot and drivers Nexus S it is practically the same for your Galaxy Nexus
Oh ok! I'll look at that now. Thanks fellas
Why couldn't you just....
Fastboot OEM unlock
Fastboot flash recovery
Flash su zip in recovery
(obviously, I'm omitting some steps here like after Fastboot flashing recovery, booting into recovery...ect)
Unless there isn't a custom recovery available yet...
That's how I rooted BOTH the N1 and NS....
Sent from my HTC Sensation 4G using xda premium until I can get the Galaxy Nexus on T-Mobile
there isnt a custom recovery yet and stock recovery needs signed recoveries
actually not hard you take 3 mins in all process
Babydoll25 said:
Why couldn't you just....
Fastboot OEM unlock
Fastboot flash recovery
Flash su zip in recovery
(obviously, I'm omitting some steps here like after Fastboot flashing recovery, booting into recovery...ect)
Unless there isn't a custom recovery available yet...
That's how I rooted BOTH the N1 and NS....
Sent from my HTC Sensation 4G using xda premium until I can get the Galaxy Nexus on T-Mobile
Click to expand...
Click to collapse
Babydoll25 said:
Unless there isn't a custom recovery available yet...
Click to expand...
Click to collapse
Ding ding ding.
Also some people don't want to flash a custom recovery anyway.
Sent from my Nexus S using XDA App
Drivers
Does anyone know where else to get the drivers from? installed the ones attached but when i go into device manager, i am seeing android.1 and when type "fastboot devices" nothing comes up
coleburns said:
Does anyone know where else to get the drivers from? installed the ones attached but when i go into device manager, i am seeing android.1 and when type "fastboot devices" nothing comes up
Click to expand...
Click to collapse
How I got fastboot working was to install pdanet, one of the steps is to install all the drivers. It doesn't matter if it fails after that step, I didn't want pdanet anyways
The ones attached seem to only be for adb mode.
Sent from my Galaxy Nexus using xda premium
el3ctrik said:
How I got fastboot working was to install pdanet, one of the steps is to install all the drivers. It doesn't matter if it fails after that step, I didn't want pdanet anyways
The ones attached seem to only be for adb mode.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
thanks for that, managed to get it working with pdanet.
however when i try to run the adb commands, i get the adbt cannot run as root in production builds
how did you get rooted?
thanks

[Q] Kindle Fire with 6.3 Help with Rooting Please

Hi,
I am a total noob. I don't even know the proper expressions for this whole thing.
So this is my case:
I am outside the US and bought the Kindle Fire with a 6.3 firmware, couple of days ago.
Being curious about what it all can do, created a fake account with a test credit card as I read somewhere in the net.
Then downloaded the KFU 0.9.5 and rooted the device, everything went according to the plan, so I thought.
Then I discovered I had to use something called Market Opener to install other apps. But this Market Opener never worked.
So I found out that I had to change permissions. But this cannot happen as I get that message that adb services can not run in production builds etc. whatever that may mean.
So I downloaded Android SDK, followed the instructions installed it but I still cannot get into the root and change folder permissions. Sometimes it recognizes the device, sometimes not and when it does it tells me the same thing as above.
Then I would need some .apk to do the thing on the device but I cannot install those as I don't have the Market Opener or the Google Play and I cannot get those if I don't have superuser permissions to change things in Folders.
Basically I have been spending the last 3 days in searching the net for answers but to no avail.
So, can someone help me please? What I need to do is being able to install some apps including Market Opener / Google Play and being able to watch Amazon VOD. Is this possible?
Please bear in mind that I have no clue of the specific language, i.e. I don't know what flash is and how to do it nor I know how to do a backup and restore or how to reset everything in the original state.
SO if some of you have the patience to help, please advice me with some noob language so that I can understand.
Thanks in advance for the help that will come
Are you looking to put a custom rom on it or just root? If you're looking to keep Amazon services, you can put MoDaCo's rom on it, which is just like your kindle out of the box with a few extra bells and whistles. There are alot of guides floating around on how to get ADB working. There's an excellent beginners guide in the General section that I highly advise checking out.
Noob terms: if you want to keep the Amazon experience, I reccomend MoDaCo. Look for it in the development fourms.
brainchow said:
Are you looking to put a custom rom on it or just root? If you're looking to keep Amazon services, you can put MoDaCo's rom on it, which is just like your kindle out of the box with a few extra bells and whistles. There are alot of guides floating around on how to get ADB working. There's an excellent beginners guide in the General section that I highly advise checking out.
Noob terms: if you want to keep the Amazon experience, I reccomend MoDaCo. Look for it in the development fourms.
Click to expand...
Click to collapse
Thanks for ur answer.
I have read a lot of guides out there but I seem not to be able to get the ADB working as I always get the message I gave in the original post plus the fact that sometimes it recognizes the device and sometimes not.
I have read the beginners guide which was excellent but without the ADB working there is little I can do I suppose.
As I wrote, I want to play with the device to see what it is able to do and want to use the Amazon VOD if possible. I.e. I would like to be able to use Google Play to get apps on will and still keep the Amazon services. Would that be possible with the MoDaCo staff?
Ok. I downloaded the MoDaCo staff.
Must I reset the kindle to the factory settings before I install that? If yes, how?
And how do I flash it?
Make sure you are in fact rooted.
You seem like you know enough about adb to try the following commands.
adb shell
ls /system/xbin
Look for a file called "su" in the list
Then...
ls /system/app
Look for a file called "Superuser.apk"
A lack of either of these means you're not rooted and may be the source of your problems
If you are trying to change system file permissions through adb...
adb root
adb remount
adb shell chmod blah /blah/blah/yadayada
Just don't literally type "blah /blah/blah/yadayada"
Sent from my Amazon Kindle Fire using xda premium
a factory reset won't really help you because you're basically replacing the operating system. pretty sure all amazon services are working with modaco. to install it, look around for a guide on how to install something called firefirefire (FFF) and TWRP. pretty sure that can all be done with kfu in a couple clicks. then copy the modaco zip onto your kindle, go into the wipe menu and clear out system, cache, dalvik cache, and data (factory reset), then go into install and choose the modaco zip. reboot and you should be set.
soupmagnet said:
Make sure you are in fact rooted.
You seem like you know enough about adb to try the following commands.
adb shell
ls /system/xbin
Look for a file called "su" in the list
Then...
ls /system/app
Look for a file called "Superuser.apk"
A lack of either of these means you're not rooted and may be the source of your problems
If you are trying to change system file permissions through adb...
adb root
adb remount
adb shell chmod blah /blah/blah/yadayada
Just don't literally type "blah /blah/blah/yadayada"
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
Thank you for your answer.
I would gladly follow your advice but the adb does not find my device. I don't know whether this is normal and if I must reboot my PC.
The kfu also gives me an offline status...
brainchow said:
a factory reset won't really help you because you're basically replacing the operating system. pretty sure all amazon services are working with modaco. to install it, look around for a guide on how to install something called firefirefire (FFF) and TWRP. pretty sure that can all be done with kfu in a couple clicks. then copy the modaco zip onto your kindle, go into the wipe menu and clear out system, cache, dalvik cache, and data (factory reset), then go into install and choose the modaco zip. reboot and you should be set.
Click to expand...
Click to collapse
Thanks again for the fast answer. I am impressed!
Doesn't the FFF and the TWRP get installed automatically with the kfu?
its most likely your computer. a reboot might help. if not, how did you install the drivers? are you using a mac or pc? try installing the drivers that came bundled with KFU.
if you're using a PC, go into device manager and see if something about android ADB pops up. if not, it's your drivers.
---------- Post added at 07:53 PM ---------- Previous post was at 07:51 PM ----------
GreekCY said:
Thanks again for the fast answer. I am impressed!
Doesn't the FFF and the TWRP get installed automatically with the kfu?
Click to expand...
Click to collapse
haha, no problem .
if FFF was installed, you should see a picture of fire in a caution sign or an android logo over the kindle fire logo when you boot it up. if all you see is kindle fire, then you don't have fff. im pretty sure you need fff to get into twrp. if fff is installed, you should be able to hop into fastboot and install twrp if it's not installed yet.
brainchow said:
its most likely your computer. a reboot might help. if not, how did you install the drivers? are you using a mac or pc? try installing the drivers that came bundled with KFU.
if you're using a PC, go into device manager and see if something about android ADB pops up. if not, it's your drivers.
Click to expand...
Click to collapse
I am using a PC ( a netbook, don't laugh, I'm on vacation!!)
I installed the drivers using the install_bat from the kfu.
In device manager I see Android Phone and underneath Android Composite ADB Interface...
interesting. check my previous post and see if you have FFF installed. adb should be working fine if device manager can find it. if you can, run adb devices into cmd and see if it picks up your kindle. not sure if the stock rom has a development switch in the settings.. if there's an option to enable usb debugging, make sure that is on. if not, just try moving usb ports and running adb devices.
If adb has trouble recognizing your device, it means it's a driver issue. Either Windows, KFU or a combination of the two causes the drivers to fail for some reason.
Uninstall/delete your current drivers in device manager (may require reboot)
Turn your Kindle off
Reinstall drivers
Turn your Kindle on
Retry adb commands
Sent from my Amazon Kindle Fire using xda premium
brainchow said:
interesting. check my previous post and see if you have FFF installed. adb should be working fine if device manager can find it. if you can, run adb devices into cmd and see if it picks up your kindle. not sure if the stock rom has a development switch in the settings.. if there's an option to enable usb debugging, make sure that is on. if not, just try moving usb ports and running adb devices.
Click to expand...
Click to collapse
I have FFF as I see the fire in a caution sign (yellow triangle thing right?)
ADB still doesn't pick my kindle after a PC restart.
No usb debugging available in the stock rom.
I will uninstall and reinstall the drivers from device manager.
Thanks again for your prompt help. I am oblidged!
GreekCY said:
I have FFF as I see the fire in a caution sign (yellow triangle thing right?)
ADB still doesn't pick my kindle after a PC restart.
No usb debugging available in the stock rom.
I will uninstall and reinstall the drivers from device manager.
Thanks again for your prompt help. I am oblidged!
Click to expand...
Click to collapse
that's fantastic... if you have FFF, try pressing the power button a couple times as it turns on and see if you can get into recovery. you shouldn't need adb now. if you can get into recovery, just wipe and flash the new rom. if you don't, you can use fastboot to install it.
brainchow said:
that's fantastic... if you have FFF, try pressing the power button a couple times as it turns on and see if you can get into recovery. you shouldn't need adb now. if you can get into recovery, just wipe and flash the new rom. if you don't, you can use fastboot to install it.
Click to expand...
Click to collapse
Ok...I reinstalled the drivers
now ADB gets the kindle
I do adb shell
then ls / system /xbin
no such file or directrory
the same goes with the
ls / system / app
But if I give su I get
su
#
Now what?
And in which directory should I transfer the MoDaCo Rom?
GreekCY said:
Ok...I reinstalled the drivers
now ADB gets the kindle
I do adb shell
then ls / system /xbin
no such file or directrory
the same goes with the
ls / system / app
But if I give su I get
su
#
Now what?
Click to expand...
Click to collapse
SU (substitute user) in shell is different from the su binary
Make sure you are typing "L"s, not "i"s then /system/xbin
Sent from my Amazon Kindle Fire using xda premium
soupmagnet said:
SU (substitute user) in shell is different from the su binary
Make sure you are typing "L"s, not "i"s then /system/xbin
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
I really do type "L"...still ls/system/xbin: not found
modaco can go anywhere in the kindle.. just copy it somewhere. then press the power button a couple times when FFF comes up and see if you can get into twrp.
brainchow said:
modaco can go anywhere in the kindle.. just copy it somewhere. then press the power button a couple times when FFF comes up and see if you can get into twrp.
Click to expand...
Click to collapse
Guys? I just installed ModaCo and it seems it works fine. Google Play seems to work and all my data are still there (I mean the books I uploaded). If this is right then.... THANKS TO ALL OF YOU SO MUCH!!!!
Drinks are on me! Now I go to sleep! Will keep you informed!!!
Thanks again!!!!
GreekCY said:
I really do type "L"...still ls/system/xbin: not found
Click to expand...
Click to collapse
Space between ls and /system/xbin and no other spaces
It IS there, your Kindle wouldn't work otherwise
Sent from my Amazon Kindle Fire using xda premium
GreekCY said:
I really do type "L"...still ls/system/xbin: not found
Click to expand...
Click to collapse
if you want to use adb, should be ls /system/xbin. make sure you put the space after the ls. i would still recommend flashing modaco nevertheless... that shouldn't need adb. just maybe fastboot if your recovery isnt installed.
---------- Post added at 08:59 PM ---------- Previous post was at 08:57 PM ----------
GreekCY said:
Guys? I just installed ModaCo and it seems it works fine. Google Play seems to work and all my data are still there (I mean the books I uploaded). If this is right then.... THANKS TO ALL OF YOU SO MUCH!!!!
Drinks are on me! Now I go to sleep! Will keep you informed!!!
Thanks again!!!!
Click to expand...
Click to collapse
no problem... enjoy
i would still recommend wiping data and the two caches to ensure that it's bug free. but if everything works fine, so be it.
have fun

can't get into settings after root

Hi, I rooted with KFF and now i can't swip from the top of the screen and i have no back arrow or home button. i was trying to remove root with KFF and bin4ry but no luck. Can somebody give me some instructions? Thanks
Rooting alone will not cause the type of problems you are describing. Have you installed a custom ROM, custom launcher, or any other alterations to /system that would require root privileges?
No 2nd bootloader. just root and i can't enable adb
Adb was required for root, it should still be enabled if you never were able to get into settings after root. Weird... If worst comes to worst u might have to reflash the system image, which on the bright side is prerooted. But I just don't see how rooting it could cause such a weird error, sounds like something got messed up with the systemui apk, and root doesn't modify that.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
cubiche said:
No 2nd bootloader. just root and i can't enable adb
Click to expand...
Click to collapse
To remove "root", simply enter the following commands in a terminal emulator:
Code:
su
mount -o remount,rw /system
rm /system/app/Superuser.apk
rm /system/xbin/su
mount -o remount,ro /system
exit
But, be warned. If having "root" is not the source of your problem, as I suspect, and you have some additional changes to your /system directory that you've failed to mention, you will not only be stuck with the problem you had to begin with, but you will also not have root permissions or the adb connection you would need to fix your device.
He should be able to get it in fastboot though with the fastboot getvar product command if he plugs in his kindle when off after running it since a 8.9" model right? That would be useful even if adb is disabled.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
I can get into fastboot with kff, but I don't know where go from there.
You can restore a saved system.img, but it will still be rooted when it's finished.
I have a saved image from another kindle HD 8.9. I think it was 8.3.0. Will that work? Can someone will me through the process?
cubiche said:
I have a saved image from another kindle HD 8.9. I think it was 8.3.0. Will that work? Can someone will me through the process?
Click to expand...
Click to collapse
Code:
fastboot -i 0x1949 flash system system.img
Hey soupmagnet, thanks for the help. Is there a risk of bricking the tablet?
The risk is considerably lower than installing the 2nd bootloader.
How do I enter that line. From adb?
ok, i'm done but i'm stuck on the kindle fire screen.
Where did you get your system.img?
[Edit:] Nevermind. I forgot you already told us. Is it safe to assume you have a boot.img as well?
it was saved on my computer from a different hd 8.9. i saved it before frashing 2nd bootloader and twrp. should i also flash the recovery and boot?
yes i have boot and recovery.img
fastboot -i 0x1949 flash boot boot.img
That should fix it.
i flashed recovery, boot and system and still don't have the navigation buttons. system is still rooted, i assume because i flash a rooted system.img. i also have the stock-system, recovery and boot. do you think that will fix it?
I guess I assumed that's what you meant when you said you had saved images.
Unless you unpack, unroot and repack your system.img, it's going to be rooted either way because you have to have root permissions to save your system.img. But it seems beyond all logic and reasoning to think that having "root", which consists of two files that are completely independent of the systemui.apk and framework-res.apk, would have any effect on the navbar at all.
By all means, restore your stock images. I'm very interested to see if it has any effect.

Couldn't write bp1, panic! Fbmode issue?

Hello, I have recently downloaded fbmode, and after following the steps prior to execuion, the execution fails, only giving me the error: couldn't write bp1, panic! After 4 hours of trying other software and searching for a solution, I made this post. I am using sustem v6.3.3, which is, from what I have read, 2nd generation. Any help would be much appreciated. I am also on a Arch Linux Box right now. Thanks.
-Hydrochloricacid
see my [2014][Pre-Rooted][Stock]System Version 6.3.3-Original Kindle Fire Only
---------- Post added at 05:23 PM ---------- Previous post was at 05:21 PM ----------
short answer is you need a Fastboot/Factory cable to start the process.
MikiBest said:
Mobile shell doesn't support the seconds hand for analog clocks. They sell the Spb Time to enhance the clock features.
Click to expand...
Click to collapse
Had the same issue. I was pushing fbmode to /data/local/fbmode from a different thread and getting that error 'couldn't write bp1'.
Changed to push to /data/local/tmp and all worked without factory cable.
Sent from my LG-P930 using Tapatalk 2
More clarification please...
nightlimits said:
Had the same issue. I was pushing fbmode to /data/local/fbmode from a different thread and getting that error 'couldn't write bp1'.
Changed to push to /data/local/tmp and all worked without factory cable.
Sent from my LG-P930 using Tapatalk 2
Click to expand...
Click to collapse
Can you clarify what you did... I'm having the same problem.
Did you change, "adb push fbmode /data/local/fbmode" to "adb push fbmode /data/local/tmp" or did you change something else?
(sorry I'm a bit of a beginner and do not have a factory Kindle cable)
ajax_borges said:
Can you clarify what you did... I'm having the same problem.
Did you change, "adb push fbmode /data/local/fbmode" to "adb push fbmode /data/local/tmp" or did you change something else?
(sorry I'm a bit of a beginner and do not have a factory Kindle cable)
Click to expand...
Click to collapse
[6.3.3] Flashing FFF and TWRP without Fastboot Cable
sd_shadow said:
[6.3.3] Flashing FFF and TWRP without Fastboot Cable
Click to expand...
Click to collapse
You can also use an Android phone cable
Oh C'mon, is it even worth it?
I must apologize for my rant in advance, and is not directed at this group, but the task at hand: IMO all this is absolute Bull$h1t. I simply wanted to root my old Kindle (I've done this several times before without incident), and I go around and around downloading 5 gig SDK software, additional rooting programs, drivers, then being told I need a legacy this, and ADB that, and yet another different driver here, and so forth and so on, and then "oh no it dont work with windows 8.1" so I start this nonsense over on my XP box, and then 4 more hours later I read maybe its cause its the wrong cable, or whatever the "fix" is this hour!!!
Well. I did it my way.
Maphoo said:
I must apologize for my rant in advance, and is not directed at this group, but the task at hand: IMO all this is absolute Bull$h1t. I simply wanted to root my old Kindle (I've done this several times before without incident), and I go around and around downloading 5 gig SDK software, additional rooting programs, drivers, then being told I need a legacy this, and ADB that, and yet another different driver here, and so forth and so on, and then "oh no it dont work with windows 8.1" so I start this nonsense over on my XP box, and then 4 more hours later I read maybe its cause its the wrong cable, or whatever the "fix" is this hour!!!
Well. I did it my way.
Click to expand...
Click to collapse
[How To][Root] Kindle Fire 1 update 6.3.4 [2014]
Sent from my XT907 using Tapatalk
I don't know if this is what EVERYONE is seeing with this problem, but in MY case, the problem was that various scripts were attempting to run fbmode as non-root user.
The most simplistic way of dealing with this is to start an adb shell, su to root, then execute /data/local/tmp/fbmode:
c:\ adb shell
$ su
# /data/local/tmp/fbmode
# exit
$ exit
c:\ adb reboot
The kindle should then reboot in fastboot mode.
---------- Post added at 09:45 PM ---------- Previous post was at 09:27 PM ----------
pestaub said:
I don't know if this is what EVERYONE is seeing with this problem, but in MY case, the problem was that various scripts were attempting to run fbmode as non-root user.
The most simplistic way of dealing with this is to start an adb shell, su to root, then execute /data/local/tmp/fbmode:
c:\ adb shell
$ su
# /data/local/tmp/fbmode
# exit
$ exit
c:\ adb reboot
The kindle should then reboot in fastboot mode.
Click to expand...
Click to collapse
After thinking about this some more, I'm guessing that the 'run as root' solution is not the root (no pun intended) cause of the problem. I don't know where/what 'bp1' is, but I'd be willing to bet that some of the other messing around that I've done has caused it to become unwriteable. Wish I knew what that was.

Categories

Resources