Database Develop

[HOWTO] Root HKTW 2.3.4 - The easier way

I don't know if I am the only one who realized there's su binary already in the build. Anyway, this is a shorter route to have root working on your phone. This only works with the HKTW 2.3.4 build! And this instruction have only be tested by me. So, do take precautionary measures.
DOWNLOAD: http://dl.dropbox.com/u/6418171/SuperUser.zip
INSTRUCTIONS:
1. Extract the zip to your internal storage (i.e. /sdcard)
2. Get into the phone shell i.e.
adb shell
Click to expand...
Click to collapse
3. Then, type and press enter:
su
Click to expand...
Click to collapse
4. Lastly, copy and paste these whole chunk to your phone shell and press enter:
mount -o remount,rw /dev/block/mmcblk0p12 /system && cp /sdcard/SuperUser/su /system/bin/su && chmod 6755 /system/bin/su && cp /sdcard/SuperUser/SuperUser.apk /system/app/SuperUser.apk && mv /system/xbin/su /system/xbin/dosu
Click to expand...
Click to collapse
If there's no error with the output, you should have root access on your phone now. Tada! Do report of this works for you!

Will try and report if it works or not
Sent from my MB860 using XDA App

Well I know I shouldn't say it here...
But is the HKTW rom blurred or blurless?

Different kind of blur but its still blur
Sent from my MB860 using XDA App

Do you mean Blur 4.5?

I don't know what its called lol
Sent from my MB860 using XDA App

Trying it out now. Will report back.
And this has Blur on it. It's not a custom ROM.

Anyone else experiencing issues getting their phone recognize by adb
Sent from my Atrix 4g Ubl 2.3.4

su is throwing me a permission denied
http://pastebin.com/brXVEYDb

i guess i didn't phrase the instruction clearly. sorry. just edited first post.. reread everything and try again.

had to run it a few times.. but it worked! thx!

Works! 10char

reserved *10chars

su: not found
For some reason USB debugging does not seem to be working properly, even with stay awake checked.
EDIT:
An even easier way.
I decided to run beforeupdate.bat and afterupdate.bat and was able to successfully gain root access on hktw-2.3.4.

jimmer411 said:
su: not found
For some reason USB debugging does not seem to be working properly, even with stay awake checked.
EDIT:
An even easier way.
I decided to run beforeupdate.bat and afterupdate.bat and was able to successfully gain root access on hktw-2.3.4.
Click to expand...
Click to collapse
having the same issue with SU

Are there any other alternatives to root currently?

jimmer411 said:
su: not found
For some reason USB debugging does not seem to be working properly, even with stay awake checked.
EDIT:
An even easier way.
I decided to run beforeupdate.bat and afterupdate.bat and was able to successfully gain root access on hktw-2.3.4.
Click to expand...
Click to collapse
Can you be more specifically on those files? Where to download and how exactly did you go about running those files?

Do I need the SDK for rooting it?

THIS WORKS ON WINDOWS, OSX, AND LINUX
once you type in adb shell then type dosu instead of su and see if that helps

I get an error at the last part when I put it in cmd
Whenever I type in 'su', I get permission denied - and dosu doesn't work either.

[FIX] Phone Bootlooping?

CONFIRMED WORKING ON LINUX.. waiting to hear for windows, mac...
NOTE: Please keep track of what your doing, because if you DON'T know what you broke, your going to have a hard time fixing it.
I'd recommend NOT wiping DATA/factory restore unless you literally have NO other choice (see post 11)
That being said...
Assuming you know what change(s) you made before your bootloop, you are saying to yourself "If i could only boot up so i can UNDO it" ... this IS for you!
Directions:
Battery Pull
Put Battery Back
Hold M button on keyboard then power
Use vol - button to go to BP TOOLS (don't select yet)
Connect via USB to computer with ADB
In terminal on computer...
Code:
adb wait-for-device shell
On phone use vol + button to select BP Tools.. then wait for your terminal to get you into shell (this will happen while the phone is continuously bootlooping)
according to djrbliss root method...
Code:
mv /data/local/12m /data/local/12m.bak
ln -s /data /data/local/12m
exit
9.
Code:
adb reboot
10. wait for the power off then repeat steps 1-7
11. again thanks to djrbliss...
Code:
rm /data/local/12m
mv /data/local/12m.bak /data/local/12m
mv /data/local.prop /data/local.prop.bak
echo "ro.sys.atvc_allow_netmon_usb=0" > /data/local.prop
echo "ro.sys.atvc_allow_netmon_ih=0" >> /data/local.prop
echo "ro.sys.atvc_allow_res_core=0" >> /data/local.prop
echo "ro.sys.atvc_allow_res_panic=0" >> /data/local.prop
echo "ro.sys.atvc_allow_all_adb=1" >> /data/local.prop
echo "ro.sys.atvc_allow_all_core=0" >> /data/local.prop
echo "ro.sys.atvc_allow_efem=0" >> /data/local.prop
echo "ro.sys.atvc_allow_bp_log=0" >> /data/local.prop
echo "ro.sys.atvc_allow_ap_mot_log=0" >> /data/local.prop
echo "ro.sys.atvc_allow_gki_log=0" >> /data/local.prop
exit
12. then again, repeat steps 1-7
13. You should have root, now go ahead and fix whatever needs fixing and reboot 1 final time
ENJOY
-KrazyKrivda

I followed this exactly but could never get an adb connection. My drivers are good and my adb setup works just fine (I was using it earlier). And idea what I could be doing wrong?
Thank you so much for posting this btw!

one more reason why I choose linux over winblows. Just a personal opinion.

Darksurf said:
one more reason why I choose linux over winblows. Just a personal opinion.
Click to expand...
Click to collapse
I tried both Windows and Linux. Are there any special steps in Linux I may be missing to get adb to work in this mode? I tried my OG Droid to test the adb setup and it worked fine.

you need to be in the android group and have adb properly installed and preferrably the current version. I use a gentoo based linux system so this stuff isn't an issue for me.
Ubuntu and debian based systems are a little different. I really dislike the package management system and Ubuntu separates users from the actual "linux" part of linux. its like linux for n00bs. Not saying its a bad distro, its just not my distro of choice.
But, if you are booting up your device correctly, you should be able to do adb start-server and then do a adb remount (if rooted) then push the files to /system/app/
if you have just ran updates, reboot your computer. If you aren't picking up the device, try using other ports (usb ports can go into a suspend mode to save power and sometimes don't like to wake up, it also happens in windows)

Jonny9797 said:
I followed this exactly but could never get an adb connection. My drivers are good and my adb setup works just fine (I was using it earlier). And idea what I could be doing wrong?
Thank you so much for posting this btw!
Click to expand...
Click to collapse
Join us in IRC and I will try to talk you through it

please help me!
i am having the same problem. i can get into recovery, fastboot, AP, and BP modes, and my device manager sees the ADB interface, but i cannot execute commands. I get this error "C:\Program Files\Android\android-sdk\platform-tools>adb remount error: device not found". i have the latest SDK and moto drivers installed... is there anyway i can install an update.zip from recovery to get me out of the bootloop?

I've updated the OP.. there is no longer a "remount" part... so I'm not sure what you are doing.. again if you can join IRC ( webchat.freenode.com ... #krazyk is the chan ) i'd be more than happy to assist

guys, i need urgent help...
i did some **** by replacing the SystemUI.apk in RootExplorer and it started force closing. i rebooted and i started bootlooping i backed up the apk in a file on my sdcard called 'import'. now i tried BP tools but it wont recognize my device..i had adb working perfectly fine before. what should i do?

Krivda, even in VM ubuntu it still doesn't see my phone... i have jdk, sdk installed... windows and ubuntu both see my xoom but the D3 is not being seen...

if the bootloop is caused due to an issue created in /data then then a factory reset will be fine (if you don't mind losing data).
HOWEVER, if the change it made is in /system.. the factory reset may reset your adb debugging option... which in turn will mean.. you will be stuck in a bootloop without the ability to access adb at all, in which case you are SOL until sbf or a way to run update.zip from recovery.

Yep that's me! I need an sbf lol

royalpunk, let me know if you find a way out... im in the same situation...

yeah, I'm the same as royol and highcee... i guess it just gives us a double incentive to find an sbf

i am also in the same situation ugh

I haven't started to fiddle yet but fear not ill be with yus tomorrow lol
-smc

I know its tempting to foolnaround with files. But no one should be messing with anything till we get an sbf.

suzook said:
I know its tempting to foolnaround with files. But no one should be messing with anything till we get an sbf.
Click to expand...
Click to collapse
SHUTUP lol you're making me feel bad

a little clarification.. OP UPDATED

I wanted to say THANK YOU to krazykrivda.
Because of your how-to I have successfully unbricked my Droid3 )) THANKS

Manually Root w/ Zerg after 893 OTA

I claim no credit for this but after the 893 OTA you wont have root and you will have to go this way to get it back.
Original post I robbed this from [HERE]
You will need adb to do this. You can get the download here depending on your operating system. ADB
Download the follow file: it contains the exploit, su, Superuser
Download exploit -->Exploit.zip
1) Unzip contents of folder to your Desktop
2) open a command terminal and navigate to the folder (cd Desktop/Exploit)
3) type the following commands
---> adb push zerg /data/local
---> adb push su /data/local
---> adb push Superuser.apk /data/local
---> adb shell
---> cd /data/local
---> chmod 777 zerg
---> ./zerg
4) Wait for the root to be gained
5) type the following commands
---> adb shell (only type this if you are no longer in [email protected])
---> mount -o rw,remount /dev/null /system
---> cat /data/local/su > /system/bin/su
---> cat /data/local/Superuser.apk > /system/app/Superuser.apk
---> chmod 4755 /system/bin/su
---> chmod 4755 /system/app/Superuser.apk
---> reboot
This is from P3Droid.
Click to expand...
Click to collapse

Worked like a charm. Thanks!

want to do this for my brother, you just connect the phone to the computer with usb debugging mode enabled right?

Fyi if you correctly root and forever root prior to the ota you will retain root. The update does not remove root if it was forever rooted.
Sent from my DROID BIONIC using XDA App

I used this method on a used Bionic I bought that has 5.7.893. It worked perfectly.

Why do you guys make it so difficult? All you need to do is use R3L3AS3DRoot to restore, root, and forever root your Bionic. And, POW! You will have a rooted Bionic once again, without D/L unnecessary software and typing commands. Props to DHacker.

charlie310 said:
Why do you guys make it so difficult? All you need to do is use R3L3AS3DRoot to restore, root, and forever root your Bionic. And, POW! You will have a rooted Bionic once again, without D/L unnecessary software and typing commands. Props to DHacker.
Click to expand...
Click to collapse
Because R3L3AS3DRoot restores a 886 system and not an 893 system, which is the reason you would "D/L unnecessary software."
So, sure you'll be rooted with an 886 system which isn't current.

you forgot last step....then update and youll still have forever root

I restored and forever rooted my bionic, then did OTA, and still have root. I was on rooted stock previously, but restored because I wasn't able to get or pull the OTA update due to "error try again later".
Sent from my DROID BIONIC using Tapatalk

Terror_1 said:
Because R3L3AS3DRoot restores a 886 system and not an 893 system, which is the reason you would "D/L unnecessary software."
So, sure you'll be rooted with an 886 system which isn't current.
Click to expand...
Click to collapse
Let's think about this logically:
D/L and unzip R3L3AS3DRoot and use 3 clicks to restore/forever root your phone, then D/L the update using a 3 clicks.
Or, D/L and install ADB, D/L and install Java SE, and D/L & unzip the Exploit Zip and type in 15 command lines to root your phone.
It's pretty obvious what is considered easier and requires less unnecessary software.
BTW, if you are flashing a ROM, then option 1 is always the best way to go since you don't have to D/L the OTA update since most ROMs have the update built in (and you already have the updated radio).

getting replacement bionic for radio issues tomorrow hopefully. will i have to use this most likely or will it unrootable? any info would be great thanks!

charlie310 said:
D/L and unzip R3L3AS3DRoot and use 3 clicks to restore/forever root your phone, then D/L the update using a 3 clicks.
It's pretty obvious what is considered easier and requires less unnecessary software.
Click to expand...
Click to collapse
You forget that some of us already have all the prerequisites. I personally can't say if your method works or not. It failed several times for me, so I gave up and zerg worked.
luke1333 said:
getting replacement bionic for radio issues tomorrow hopefully. will i have to use this most likely or will it unrootable? any info would be great thanks!
Click to expand...
Click to collapse
I am partial to doing things manually myself but I guess 43v3r does it too.
I personally had no luck with it.
Sent from my DROID BIONIC using XDA App

what version could you not root?

Does zerg work on 5.9.901 ?

luke1333 said:
what version could you not root?
Click to expand...
Click to collapse
893 43v3r doesn't work on, if you restore the 886 then root you should be fine. Just doing the update then trying to gain root isn't going to work.
kris7778 said:
Does zerg work on 5.9.901 ?
Click to expand...
Click to collapse
I don't know for sure but I am pretty confident that it would.

THANKS!
Flawless victory!
Binarality!

Has anyone rooted a previously unrooted device running version 5.9.901? Who's process?

This method worked for me, but I notice that my 3g service was weak and my 4g was gone. Even if i restarted the phone I couldn't get my 4g to work. This was after the 4g issue with VW braking it. Has anyone else had this problem?

1 click method
is there any 1 click method out there that can be used to do this ,,i used 4ever root a couple of time to restore my phone after screwing it up .. but now even that wont work .. so yeah i have the update but no root ...no matter how i try to do it before or after ..
and i unfortunately do not know how to connect to adb to push anything to my phone .. im not that technical with it ....dont have a clue .ive tried but not easy for me that is thanking you in advance Robb

One question, if I update and then for any reason I can't get root can I go back to stock rom you know the one before ota and start over? ???
Sorry for my english lol
Sent from my DROID BIONIC using XDA App

AIO ZV 8 rooter/CVM NOT WORKING.

I've followed EVERY GAWDAMN suggestion/guide/direction listed, and ZV8 refused to root/CWM for me.
Here's what the AIO says:
Root and Recovery for ZV8
Press any key to continue . . .
* daemon not running. starting it now *
* daemon started successfully *
Device found
Mounting Device
remount failed: Operation not permitted
Pushing Root Permissions
Unable to chmod /system/bin/su: No such file or directory
3720 KB/s (5345280 bytes in 1.403s)
Unable to chmod /system/xbin/busybox: Read-only file system
--install: applet not found
Installing CWM Recovery
/dev/block/mmcblk0p14: cannot open for write: Permission denied
Remove Trash
rm failed for /system/etc/install-recovery.sh, Read-only file system
rm failed for /system/recovery-from-boot.p, Read-only file system
rm failed for /data/local.prop, No such file or directory
CWM Recovery!!!
Just a note for MT. I wish the process were a bit more visible, as I've had to manually push things with adb before on rooting attempts.
I've spent 3 days trying to get this piece of sh!t rooted, and I'm tired of it.
I've followed EVERY DIRECTION/GUIDE/INSTRUCTION to the T, and still nothing, so a hearty STFU if all you can offer is a "Did you follow the directions?"

On the "Regain Root after update" post there is talk of using a terminal emulator to make the root stick on V8. The only thing that worked for me is the post at the top of page 7 (or 8?) that has about 8 steps. If you haven't already tried it.
Sent from my BROKEN OUT VS910

antiwesley said:
I've followed EVERY GAWDAMN suggestion/guide/direction listed, and ZV8 refused to root/CWM for me.
Here's what the AIO says:
Root and Recovery for ZV8
Press any key to continue . . .
* daemon not running. starting it now *
* daemon started successfully *
Device found
Mounting Device
remount failed: Operation not permitted
Pushing Root Permissions
Unable to chmod /system/bin/su: No such file or directory
3720 KB/s (5345280 bytes in 1.403s)
Unable to chmod /system/xbin/busybox: Read-only file system
--install: applet not found
Installing CWM Recovery
/dev/block/mmcblk0p14: cannot open for write: Permission denied
Remove Trash
rm failed for /system/etc/install-recovery.sh, Read-only file system
rm failed for /system/recovery-from-boot.p, Read-only file system
rm failed for /data/local.prop, No such file or directory
CWM Recovery!!!
Just a note for MT. I wish the process were a bit more visible, as I've had to manually push things with adb before on rooting attempts.
I've spent 3 days trying to get this piece of sh!t rooted, and I'm tired of it.
I've followed EVERY DIRECTION/GUIDE/INSTRUCTION to the T, and still nothing, so a hearty STFU if all you can offer is a "Did you follow the directions?"
Click to expand...
Click to collapse
Try booting into CWM the old-fashioned way (hold down button and power). When I went through all the steps, everything looked liked it failed and all I had was an unrooted ZV8. Even Root Checker said I was unrooted. But then I tried to manually boot into CWM, and it worked! I flashed the new rom, and superuser came with it! Might as well give it a try. There's the possibility that you end up wiping data if you don't actually have CWM, but it sounds like you don't really care at this point...

I went through 2 days of hell to get root. There are so many things to try but I think the one thing that worked for me was that after you root the stock V7 is to run titanium backup. When I ran it it said it had to change su access or something and then I rebooted and did this in a terminal program
su<enter>
echo 'ro.kernel.qemu=1' > /data/local.prop<enter>
but also made sure by then doing this:
cat /data/local.prop
if you don't see exactly the ro.kernel.qemu=1 redo it. I was surprised that I had it wrong but for some reason the terminal app missed characters sometimes.
-Keith

What a maroon.
Sent from my VS910 4G using Tapatalk

$ su
su
su: permission denied
$ echo 'ro.kernel.qemu=1' > /data/local.prop
echo 'ro.kernel.qemu=1' > /data/local.prop
cannot create /data/local.prop: permission denied
$

If you are able to have cwm breakout is rooted.
Sent from my Galaxy Nexus using xda premium

Thanks!
Thanks Antiwesley!
I had tried a few different times to get this working, your post below finally got it for me:
"LGNPST to ZV7.
Using AIO 1 LG Revo AIO, Root ZV7 ONLY.
Install "Rom Manager" (thanks to slimzim for this one)
Manually create local.prop as seen elsewhere in a few other versions of this kind of thing.
LGNPST to ZV8.
In a command prompt, 'adb remount'
'adb push su /system/bin/su'
'adb push superuser.apk /system/bin/superuser.apk'
'adb push busybox /system/bin/busybox'
Use AIO 2 to install CWM. It will error on a couple of things, don't panic. (one is an applet failure in the rooting process and the other are rm failures.) DO NOT USE OPTION #1! Only use Option #2!
Reboot.
Use Rom Manager's "Reboot Recovery" option and it boots straight into CWM.
(I had zero success using the hardware (power/down button) to boot into CWM.
Apply Broken Out 1.1
Back up while you're in CWM.
Reboot.
Enjoy ZV8."
The only thing I did differently was OTA to ZV8 rather than LGNPST. Also when I ran option two of AIO 2 I didn't get any errors.
The whole process took right around an hour.
Thanks again!
FYI I would have posted this in the dev section in the Regain Root thread but am lacking the posts to do so.

stinkyjak said:
$ su
su
su: permission denied
$ echo 'ro.kernel.qemu=1' > /data/local.prop
echo 'ro.kernel.qemu=1' > /data/local.prop
cannot create /data/local.prop: permission denied
$
Click to expand...
Click to collapse
koda1789 said:
Thanks Antiwesley!
I had tried a few different times to get this working, your post below finally got it for me:
"LGNPST to ZV7.
Using AIO 1 LG Revo AIO, Root ZV7 ONLY.
Install "Rom Manager" (thanks to slimzim for this one)
Manually create local.prop as seen elsewhere in a few other versions of this kind of thing.
LGNPST to ZV8.
In a command prompt, 'adb remount'
'adb push su /system/bin/su'
'adb push superuser.apk /system/bin/superuser.apk'
'adb push busybox /system/bin/busybox'
Use AIO 2 to install CWM. It will error on a couple of things, don't panic. (one is an applet failure in the rooting process and the other are rm failures.) DO NOT USE OPTION #1! Only use Option #2!
Reboot.
Use Rom Manager's "Reboot Recovery" option and it boots straight into CWM.
(I had zero success using the hardware (power/down button) to boot into CWM.
Apply Broken Out 1.1
Back up while you're in CWM.
Reboot.
Enjoy ZV8."
The only thing I did differently was OTA to ZV8 rather than LGNPST. Also when I ran option two of AIO 2 I didn't get any errors.
The whole process took right around an hour.
Thanks again!
FYI I would have posted this in the dev section in the Regain Root thread but am lacking the posts to do so.
Click to expand...
Click to collapse
I am having the problem Stinkjak is having. No matter how I try and copy the .prop into the /data folder. I get a message that says java.io.filenotfoundexception:/data/local.prop (permission denied). Can anyone crack this error?

Plumbert said:
I am having the problem Stinkjak is having. No matter how I try and copy the .prop into the /data folder. I get a message that says java.io.filenotfoundexception:/data/local.prop (permission denied). Can anyone crack this error?
Click to expand...
Click to collapse
Are you already on stock ZV7 and rooted? Use Root Explorer and go to /data and create new file, name it local.prop. Open in text editor, enter ro.kernel.qemu=1 then save it. If you can't do that in Root Explorer then you aren't rooted.

Root/Android JB Kindle fire 10.2.3

So for the last 7 hours i've been researching how to root/ install JB or another rom onto this brand new kindle i have running 10.2.3.
I've got ADB running and i've tried Sparkym3 and a few other root methods and i keep getting permission denied when i go to write fbmode or su
SO i'm at a loss, i'd really like to get this installed and working for my handicapped father's new kindle, its his xmas gift, and i know i'd prefer he be able to use google play and stuff.
Any help would be fantastic, this is really rattling my brain.

Unfortunately, you're out of luck with a custom ROM/Jelly Bean, but you can gain access to the play store and lose the ads with root. I tried the automated method in the link below with no success. The qemu tool just quit after step two.
Is this the method you tried?
http://forum.xda-developers.com/showthread.php?t=1893838
I just followed this video to the letter, and I was golden. HOWEVER, I was on 10.2.1. I don't know if it will work with .3. Keep me posted because my other daughter's KF2 received the update before I attempted root, and I haven't attempted root on it yet . I renamed the otacert.zip file to prevent the update on the alreay-rooted tablet.
http://forum.xda-developers.com/showthread.php?t=1891939

scubamike said:
Unfortunately, you're out of luck with a custom ROM/Jelly Bean, but you can gain access to the play store and lose the ads with root. I tried the automated method in the link below with no success. The qemu tool just quit after step two.
Is this the method you tried?
http://forum.xda-developers.com/showthread.php?t=1893838
I just followed this video to the letter, and I was golden. HOWEVER, I was on 10.2.1. I don't know if it will work with .3. Keep me posted because my other daughter's KF2 received the update before I attempted root, and I haven't attempted root on it yet . I renamed the otacert.zip file to prevent the update on the alreay-rooted tablet.
http://forum.xda-developers.com/showthread.php?t=1891939
Click to expand...
Click to collapse
The commands:
adb shell
rm -r /data/local/tmp
ln -s /data/ /data/local/tmp
exit
adb reboot
adb shell
echo 'ro.kernel.qemu=1' > /data/local.prop
exit
abd reboot
adb shell mount -o remount,rw /system
adb push su /system/xbin/su
adb shell
chown 0.0 /system/xbin/su
chmod 06755 /system/xbin/su
rm /data/local.prop
exit
adb reboot
adb install Superuser.apk
^^^ Method i tried, and failed, wont allow remount, gives me permission denied, i didnt try Qemu at all.
If i could get access to play store i'd be fine keeping it on stock, i just want my dad to be able to use this thing with standard apps.
I think this method is strictly for the kindle fire HD and i'm trying to do it on a standard Kindle Fire.

Hi there,
I,ve got the same issue with my brand new KF Gen2 FW 10.2.3. During the 1st run everythings seems fine (all commands were accepted),
but in the end I was not able to get root access by the superuser-app.
After that I decided to reset the device to factory defaults, but now I'm not able to create any file under /data (echo 'ro.kernel.qemu=1' > /data/local.prop).
Has anyone a good idea which way we have to choose to get root access on the KF2 (FW10.2.3)?
Thanks yanzz

yanzz said:
Hi there,
I,ve got the same issue with my brand new KF Gen2 FW 10.2.3. During the 1st run everythings seems fine (all commands were accepted),
but in the end I was not able to get root access by the superuser-app.
After that I decided to reset the device to factory defaults, but now I'm not able to create any file under /data (echo 'ro.kernel.qemu=1' > /data/local.prop).
Has anyone a good idea which way we have to choose to get root access on the KF2 (FW10.2.3)?
Thanks yanzz
Click to expand...
Click to collapse
My device lets me punch in the echo command but once i hit mount or push i'll get permission denied so i'm at a loss myself. I hope one of these higher end techies can help us make this happen before Christmas time or my dads kindle stays stock :crying:

I actually was able to root my 10.2.1 yesterday, but overnight it appears to have upgraded itself to 10.2.3, and now it's unrooted again.
The original technique to root fails on this step:
<code>
[email protected]:/ $ echo 'ro.kernel.qemu=1' > /data/local.prop
echo 'ro.kernel.qemu=1' > /data/local.prop
/system/bin/sh: cannot create /data/local.prop: Permission denied
</code>
Anyone have any luck?
I'd love any ideas to override the bootloader on thing, since I'm about sick and done with the stock rom.

arcymag said:
I actually was able to root my 10.2.1 yesterday, but overnight it appears to have upgraded itself to 10.2.3, and now it's unrooted again.
The original technique to root fails on this step:
<code>
[email protected]:/ $ echo 'ro.kernel.qemu=1' > /data/local.prop
echo 'ro.kernel.qemu=1' > /data/local.prop
/system/bin/sh: cannot create /data/local.prop: Permission denied
</code>
Anyone have any luck?
I'd love any ideas to override the bootloader on thing, since I'm about sick and done with the stock rom.
Click to expand...
Click to collapse
If you put the 10.2.1 rom back in the kindleupdates folder on the SDCard and go the setting to update the kindle I wonder if it will reset back to 10.2.1. Atleast you could re-root and then try to block the OTA so it wont go back to 10.2.3.

bodi524 said:
If you put the 10.2.1 rom back in the kindleupdates folder on the SDCard and go the setting to update the kindle I wonder if it will reset back to 10.2.1. Atleast you could re-root and then try to block the OTA so it wont go back to 10.2.3.
Click to expand...
Click to collapse
I tried that last night, but it didn't work for me. Does anyone know if the .bin files from Amazon are flashable through fastboot... It would definitely be worth building/buying a factory cable if we could fastboot flash back to 10.2.1, root, and block ota updates.

Not to beat a dead horse but I am having the same trouble with Kindle Fire 2. Lost Root access last night when Amazon pushed 10.2.3. I tried to down-date to 10.2.1 but the .bin file keeps getting deleted from the kindleupdates folder after I press the update button in "settings-device-about". Unfortunately I learned about disabling automatic updates a little too late. Thank you in advance for helping us out. We are not worthy.

arcymag said:
I actually was able to root my 10.2.1 yesterday, but overnight it appears to have upgraded itself to 10.2.3, and now it's unrooted again.
The original technique to root fails on this step:
<code>
[email protected]:/ $ echo 'ro.kernel.qemu=1' > /data/local.prop
echo 'ro.kernel.qemu=1' > /data/local.prop
/system/bin/sh: cannot create /data/local.prop: Permission denied
</code>
Anyone have any luck?
I'd love any ideas to override the bootloader on thing, since I'm about sick and done with the stock rom.
Click to expand...
Click to collapse
Thats exactly where it fails for me :/
Oh kindle hacking gods have mercy on us.

xiastro1ix said:
Thats exactly where it fails for me :/
Oh kindle hacking gods have mercy on us.
Click to expand...
Click to collapse
I am willing to try the hack posted for the 8.9" bootloader.
However I want to know the restore process works first.
If someone will pull the partitions to restore, zip them and post them I will try the backup on my KindleFire2.
See Here:
http://forum.xda-developers.com/showthread.php?t=2032822
Mine is bricked as of now so trying to restore it won't harm it anymore that it already is.
Once we having a working restore I will try the bootloader crack....and in an exchange with
Hashcode he said he thinks the Original KF roms will then work (WITH SOME KERNEL CHANGES)
for the KindleFire2.

this thread
http://forum.xda-developers.com/showthread.php?t=2033297
claims that they've got root working on the current version, but I tried and it doesn't even recognize my device is plugged in. Several confirmations in that thread that people have it working though.

confrmed root access on 10.2.3
http://forum.xda-developers.com/showthread.php?t=2033297
Just completed hooray!
Now to replace ROM
well it claims its rooted and it has super user installed, but i still cant get past permission denied messages when trying to go ahead and get a new rom on it.
Not sure what to do here, i want to get google aps on it and i'll be fine, but i don't know what file explorer would be good for the stock rom that i can get through the amazon store :\
I'm actually not sure if it is rooted, the first method installed SU onto the phone, but i don't actually see the second portion processing the exploit, its getting permission denied aswell, the kindle has superuser on it, but now i'm completely lost, i still cant get it to do anything....
Edit- ALL DONE YAY
Got googleplay and 1mobile installed, just had to purchase ES file explorer and play around a bit

Any idea why I can't seem to get past these root methods even seeing my kindle is plugged in? I KNOW one of the methods came bundled with some kinda drivers ... I'm just at a loss for what I'm doing wrong because I've tried all sorts of stuff from various posts and instructions...
Running Win7 x64 if that helps any.

Trendy Ideology said:
Any idea why I can't seem to get past these root methods even seeing my kindle is plugged in? I KNOW one of the methods came bundled with some kinda drivers ... I'm just at a loss for what I'm doing wrong because I've tried all sorts of stuff from various posts and instructions...
Running Win7 x64 if that helps any.
Click to expand...
Click to collapse
Step one is getting ADB hooked up and installed on your computer
if youre telling me your computer is seeing "kindle" then youre already doing it wrong. In order for these methods to work upon plugging in your kindle, device manager should say Android- ADB composite device, or something along those lines,

xiastro1ix said:
Step one is getting ADB hooked up and installed on your computer
if youre telling me your computer is seeing "kindle" then youre already doing it wrong. In order for these methods to work upon plugging in your kindle, device manager should say Android- ADB composite device, or something along those lines,
Click to expand...
Click to collapse
I was trying to use the ADB drivers found here,
http://forum.xda-developers.com/showthread.php?t=1893838
but when installed they didn't say anything like that in the final step that showed me what was installed, it said amazon kindle somethingorother.
Device manager went from showing
Portable devices
|
_ Kindle
To now
Kindle Fire
|
_ Kindle
Installing the driver manually gets me something that looks like ADB Kindle Fire but now it doesn't show up in My Computer at all, and the root with restore
http://forum.xda-developers.com/showthread.php?t=1886460
doesn't "see" my kindle...
I'm rather lost.
Here's a log of as far as I've gotten so far:
======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
= Idea for Tablet S from Fi01_IS01 =
= (22.11.2012) v17 =
======================================================================
Device type:
1) Normal
2) Special (for example: Sony Tablet S, Medion Lifetab)
x) Unroot
Make a choice: 1
Checking if i should run in Normal Mode or special Sony Mode
Please connect your device with USB-Debugging enabled now
remote object '/system/app/Backup-Restore.apk' does not exist
remote object '/system/bin/ric' does not exist
.
.
Normal Mode enabled!
.
Pushing busybox....
failed to copy 'stuff/busybox' to '/data/local/tmp/./busybox': Permission denied
Pushing su binary ....
failed to copy 'stuff/su' to '/data/local/tmp/./su': Permission denied
Pushing Superuser app
failed to copy 'stuff/Superuser.apk' to '/data/local/tmp/./Superuser.apk': Permi
ssion denied
Making busybox runable ...
Unable to chmod /data/local/tmp/busybox: No such file or directory
.
Please look at your device and click RESTORE!
If all is successful i will tell you, if not this shell will run forever.
Running ...
Successful, going to reboot your device in 10 seconds!
error: device not found
Waiting for device to show up again....
Going to copy files to it's place
/system/bin/sh: /data/local/tmp/busybox: not found
You can close all open command-prompts now!
After reboot all is done! Have fun!
Bin4ry
Press any key to continue . . .
It's only "Seeing" my kindle if I power it down, plug in the USB, and then it seems to "catch" it while it's booting up. And it remains caught until the tool lets go of it and then it goes to the lock screen as normal.
on this step
Please look at your device and click RESTORE!
If all is successful i will tell you, if not this shell will run forever.
I get no restore option, probably because my kindle is in a booting state when this is all happening.

I was able to root my Kindle Fire 2 on 10.2.3 doing a combination of:
http://forum.xda-developers.com/showthread.php?t=1891939
and
http://forum.xda-developers.com/showthread.php?t=1894717
adb shell
rm -r /data/local/tmp
ln -s /data/ /data/local/tmp
exit
adb reboot
This step in red no longer works!
adb shell
echo 'ro.kernel.qemu=1' > /data/local.prop
exit
Instead do...
4) Restore the fake "backup": adb restore fakebackup.ab Note: do not click restore on your device. Just enter the command into the command prompt on your PC and press the enter key.
5) Run the "exploit": adb shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done" Note: when you enter this command, you should see your adb window flooded with errors -- this is what is supposed to happen.
6) Now that the "exploit" is running, click restore on your device.
7) Once it finishes, reboot your device: adb reboot Note: Do not try and use your device when it reboots. Running this exploit will reboot your device into emulator mode, so it will be laggy and the screen will flicker -- this is normal.
adb shell mount -o remount,rw /system
adb push su /system/xbin/su
adb shell
chown 0.0 /system/xbin/su
chmod 06755 /system/xbin/su
rm /data/local.prop
exit
adb reboot
adb install Superuser.apk

Deflection said:
I was able to root my Kindle Fire 2 on 10.2.3 doing a combination of:
http://forum.xda-developers.com/showthread.php?t=1891939
and
http://forum.xda-developers.com/showthread.php?t=1894717
adb shell
rm -r /data/local/tmp
ln -s /data/ /data/local/tmp
exit
adb reboot
This step in red no longer works!
adb shell
echo 'ro.kernel.qemu=1' > /data/local.prop
exit
Instead do...
4) Restore the fake "backup": adb restore fakebackup.ab Note: do not click restore on your device. Just enter the command into the command prompt on your PC and press the enter key.
5) Run the "exploit": adb shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done" Note: when you enter this command, you should see your adb window flooded with errors -- this is what is supposed to happen.
6) Now that the "exploit" is running, click restore on your device.
7) Once it finishes, reboot your device: adb reboot Note: Do not try and use your device when it reboots. Running this exploit will reboot your device into emulator mode, so it will be laggy and the screen will flicker -- this is normal.
adb shell mount -o remount,rw /system
adb push su /system/xbin/su
adb shell
chown 0.0 /system/xbin/su
chmod 06755 /system/xbin/su
rm /data/local.prop
exit
adb reboot
adb install Superuser.apk
Click to expand...
Click to collapse
I have a new Kindle Fire (1st gen) and all your steps were perfect until I tried to install the SuperUser.apk where it says I dont have permissions to copy to /data/tmp... ans fails to install superuser.
Any ideas? Maybe chmod of /data getting in emulator mode?
Thanks

reyvaj said:
I have a new Kindle Fire (1st gen) and all your steps were perfect until I tried to install the SuperUser.apk where it says I dont have permissions to copy to /data/tmp... ans fails to install superuser.
Any ideas? Maybe chmod of /data getting in emulator mode?
Thanks
Click to expand...
Click to collapse
There is a whole forum for kf1. Kf1 runs 6.something not 10.2...

Hi, i need help, i want root my kindle fire first generation 7 on 10.2.3_user_2313820 sw version, many thanks