Database Develop

[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

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.

[Q] Can 10.2.1 on KF2 be rooted?

I got an OTA update to 10.2.1 on my Kindle Fire 2 (not HD) before I had a chance to try to root while on 10.1.3. Have any of you KF2 owners tried to root on the new ROM version?
Thanks,
KindofBlues71

yup
Got it to root but I can't get my Holo Launcher HD to work. Does anyone have a fix for this?

strat6 said:
Got it to root but I can't get my Holo Launcher HD to work. Does anyone have a fix for this?
Click to expand...
Click to collapse
just rooted my kindle fire 2 and wanted to know if there is a possibility to prevent it from auto-updating in the future?!

strat6 said:
Got it to root but I can't get my Holo Launcher HD to work. Does anyone have a fix for this?
Click to expand...
Click to collapse
How did you get it to root? I followed the instructions given in
'[VIDEO] How to Root the Amazon Kindle Fire HD Tablet'
http://forum.xda-developers.com/showthread.php?t=1891939
-----
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
-----
I typed in the directions as shown. On the step,
'adb install Superuser.apk'
I got an error that said the file was already there. I suspect that it didn't install. All other steps seemed to complete properly. I also tried the 'rootQemu.Bat' file way shown in,
http://forum.xda-developers.com/showthread.php?p=31759763&postcount=10
But it didn't complete.
Any help?
Patrick
---------- Post added at 05:47 PM ---------- Previous post was at 05:32 PM ----------
PMcHargue said:
How did you get it to root? I followed the instructions given in
'[VIDEO] How to Root the Amazon Kindle Fire HD Tablet'
http://forum.xda-developers.com/showthread.php?t=1891939
-----
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
-----
I typed in the directions as shown. On the step,
'adb install Superuser.apk'
I got an error that said the file was already there. I suspect that it didn't install. All other steps seemed to complete properly. I also tried the 'rootQemu.Bat' file way shown in,
http://forum.xda-developers.com/showthread.php?p=31759763&postcount=10
But it didn't complete.
Any help?
Patrick
Click to expand...
Click to collapse
Well, managed to get root again by folowing the above using copy/paste. Had to unplug/plug in the KF each time. What a pain. Amazon sucks for doing this to a good piece of HW.

That's what worked for me. Also reinstalled the Holo HD launcher and its working again. I saw people in other forums trying to remove the navigation bar in the go launcher, Holo gives you an option to hide it(It still pops up occasionally though). You can also add a home button to the screens so when you're looking at all your apps there's a touchscreen home button.
They definitely made this tablet time consuming to customize but with root and a custom launcher I still think this things a steal at $159.

lost root, adds are back
I recieved the ota update10.2.1 and lost root. Was able to gain root again and since then lost root and adds are back. Didn't loose launcher though. I'm going to try to Root again and try to block the ota this time.

Root problem kindle fire 10.2.1
strat6 said:
I recieved the ota update10.2.1 and lost root. Was able to gain root again and since then lost root and adds are back. Didn't loose launcher though. I'm going to try to Root again and try to block the ota this time.
Click to expand...
Click to collapse
Hi, I have the kindle fire 2 10.2.1, but I have trouble making the root.
Which method I can use to do this?
Must be the same as the kindle fire HD?
thanks

Describing the kind of trouble are you having would be a good place to start...
"That's a special kind of stupid. The kind that makes me laugh"

soupmagnet said:
Describing the kind of trouble are you having would be a good place to start...
"That's a special kind of stupid. The kind that makes me laugh"
Click to expand...
Click to collapse
I used "Qemu automated root" and it said it was successful and I see the SU App. I am not able to go to root explorer in ES file explorer (SU permissions denied) and the Root Explorer paid APP, I am not able to change permissions of any files/folders from Read only to R/W
I guess this means I am not rooted or there a step I missed? I did end up doing it manually by copy and pasting the code into cmd window but same results...

[Q] Can i Cancel updating?

I did something stupid, which involved not staying up to date with the news on my kindle hd 7 inch since i got comfortable with my setup and hadn't really done anything much to it lately that needed me going to the forums. Anyways, my kindle decided to download the ota update, which was like a slap in the face because 3/27 was my birthday and I was in the middle of reading manga and it rebooted then tried to update so I naturally held the power button down. Is there anyway to cancel the update via adb? I typically leave adb on as a precaution to any problem I might have. I thought maybe I could run a shell and tell it to remove the update file which I'm assuming is still in /sdcard/kindleupdates (I think thats the folder name), and maybe push the 7.2.3 update as a precaution in case it started to flash already and I didn't notice. I don't want to turn it back on until I know that I can connect to it with adb because I don't want it to update, I planned on flashing cm10 to it whenever it became stable, and I heard the latest update will break the ability for me to put a bootloader on it. Any help would be appreciated.

stunts513 said:
I did something stupid, which involved not staying up to date with the news on my kindle hd 7 inch since i got comfortable with my setup and hadn't really done anything much to it lately that needed me going to the forums. Anyways, my kindle decided to download the ota update, which was like a slap in the face because 3/27 was my birthday and I was in the middle of reading manga and it rebooted then tried to update so I naturally held the power button down. Is there anyway to cancel the update via adb? I typically leave adb on as a precaution to any problem I might have. I thought maybe I could run a shell and tell it to remove the update file which I'm assuming is still in /sdcard/kindleupdates (I think thats the folder name), and maybe push the 7.2.3 update as a precaution in case it started to flash already and I didn't notice. I don't want to turn it back on until I know that I can connect to it with adb because I don't want it to update, I planned on flashing cm10 to it whenever it became stable, and I heard the latest update will break the ability for me to put a bootloader on it. Any help would be appreciated.
Click to expand...
Click to collapse
You can find here instructions on how to disable OTA services:
Code:
adb shell su -c "busybox mount -o remount,rw /system"
adb shell su -c "mount -o rw,remount /dev/block/mmcblk0p1 /system"
adb shell su -c "pm disable 'com.amazon.dcp/.ota.OTAUpdateMessageHandler'"
adb shell su -c "pm disable 'com.amazon.dcp/.ota.InventoryUploadService'"
adb shell su -c "pm disable 'com.amazon.dcp/.ota.UpdatesLookupService'"
adb shell su -c "pm disable 'com.amazon.dcp/.ota.OTAService'"
adb shell su -c "pm disable 'com.amazon.dcp/.ota.AppStateMonitorService'"
adb shell su -c "pm disable 'com.amazon.dcp/.ota.CheckForOTAUpdatesService'"
adb shell su -c "pm disable 'com.amazon.dcp/.ota.ViewUpdateActivity'"
adb shell su -c "pm disable 'com.amazon.dcp/.ota.OTAStatusActivity'"
adb shell su -c "pm disable 'com.amazon.dcp/.ota.ResetOTAMessageHandler'"
adb shell su -c "pm disable 'com.amazon.dcp/.ota.InventoryUploadService$InventoryUploadReceiver'"
adb shell su -c "pm disable 'com.amazon.dcp/.ota.UpdatesLookupService$MountStatusChangedReceiver'"
adb shell su -c "pm disable 'com.amazon.dcp/.ota.OTAService$OTAWakeupReceiver'"
adb shell su -c "pm disable 'com.amazon.dcp/.ota.OTAService$OTADedupeReceiver'"
adb shell su -c "pm disable 'com.amazon.dcp/.ota.OTAService$OTAInstallNowReceiver'"
adb shell su -c "busybox mount -o remount,ro /system"
adb shell su -c "mount -o ro,remount /dev/block/mmcblk0p1 /system"
adb reboot
adb wait-for-device
The question is how to get access to ADB. If you boot your device normally then I guess it will be too late. Kindle OS will proceed with the update. Perhaps, you can get into recovery (if you have it) and run these commands.
Anyway, it is better if you hear a second opinion from somebody more experienced.

thanks for that, i found that script when i was browsing earlier in a sh script, and was going to ask if it worked until i noticed that the script was linked back to the xda forums, wish i had sen it before my kindle started updating, and i don't have a custom recovery installed, thats why i wanted to not install this update i had been waiting around for one to come out and i kinda forgot about it and never checked back to see that it was out. I hope someone can still help me out, or atleast tell me if i will just have to boot up and I'm assuming wait for a new root exploit, since i think they usually patch the previous one when they update. Hope to hear a reply soon because i hate reading manga on my ipod... its got a small screen compared to my kindle... (I NEED MY MANGA FIX xD) and yes i know i could read it on my pc bu ti cant lay in my bed while i do it... love the quickmanga app.

stunts513 said:
thanks for that, i found that script when i was browsing earlier in a sh script, and was going to ask if it worked until i noticed that the script was linked back to the xda forums, wish i had sen it before my kindle started updating, and i don't have a custom recovery installed, thats why i wanted to not install this update i had been waiting around for one to come out and i kinda forgot about it and never checked back to see that it was out. I hope someone can still help me out, or atleast tell me if i will just have to boot up and I'm assuming wait for a new root exploit, since i think they usually patch the previous one when they update. Hope to hear a reply soon because i hate reading manga on my ipod... its got a small screen compared to my kindle... (I NEED MY MANGA FIX xD) and yes i know i could read it on my pc bu ti cant lay in my bed while i do it... love the quickmanga app.
Click to expand...
Click to collapse
When kindle is updated to 7.3.0 you lose your root and some applications will stop working or get deleted. You can still re-root your Kindle 7.3.0 using exactly the same procedure as for 7.2.3. I just re-rooted my device yesterday. it worked without any problem. I had to reinstall Google Play and custom launcher after root.

ok well thanks, I guess I have no choice but to let it finish updating, well maybe unless they find a new bug to let us put custom recovery on it, that other project will get more attention, can't remember the name of it because I haven't been browsing around in the community much for atleast a month. Funny thing is I have to remember how I rooted my kindle... I left all my rooting utilities and scripts in a folder, but my mom has a kindle fire 1st gen that i rooted as well so the stuff is also in the folder, shouldn't be a problem though I'm a pc tech so i can sort this stuff out easily.

Unpossible ROOT please help!

Well I have Kindle Fire 7 at home and I wanted to install android on,so first I have to root it but I can not describe you how many times and solutions I have tried,Binary root,Qemu root, KF First Aide.So first two works like a charm and after "Root" is done I try to test it with ES file explorer and root is not applied.I really don't know what I can do more.
I am at version 11.3.2.5
What can I do?

duvnjak said:
Well I have Kindle Fire 7 at home and I wanted to install android on,so first I have to root it but I can not describe you how many times and solutions I have tried,Binary root,Qemu root, KF First Aide.So first two works like a charm and after "Root" is done I try to test it with ES file explorer and root is not applied.I really don't know what I can do more.
I am at version 11.3.2.5
What can I do?
Click to expand...
Click to collapse
My kindle is this model: kindle fire p48wvb4

duvnjak said:
My kindle is this model: kindle fire p48wvb4
Click to expand...
Click to collapse
BUMP Please help me

duvnjak said:
bump please help me
Click to expand...
Click to collapse
**** you everyone **** youuuuu!

mine just updated to 11.3.2.6 yesterday w/o my knowledge
ugh, I'll never get to root this guy

duvnjak said:
**** you everyone **** youuuuu!
Click to expand...
Click to collapse
No need to flame. We all saw your request.
Head over to kfsowi.com which will porbably redirect you to another site where you can find a rooting guide.

Root for "11.3.2.6_user_326002520"
It´s still possible to root 11.3.2.6 with KindleSuite with a small tweak:
1.) Get an actual version from KindleSuite: https://github.com/secretdevwork/KindleSuite/wiki
2.) Extract the archive and search in folder "/resources/tools" for the file "11325.bat" and make a backup of this file
3.) open "11325.bat" in a text editor
4.) search for the code line
Code:
adb shell chmod 755 /data/local/tmp/*
replace this line with the following code lines:
Code:
adb shell chmod 755 /data/local/tmp/su
adb shell chmod 755 /data/local/tmp/exploit
adb shell chmod 755 /data/local/tmp/rootme.sh
5.) save the edited file
6.) start KindleSuite, go to Root section and select the "11.3.2.5" entry (which leads to the edited Batch skript)
7.) start the rooting procedure as described by KindleSuite
8.) profit
This is just a small tweak to fix the chmod permission problems with the original script but I think KindleSuite will be updated in a few days.
P.S.: the KindleSuite root procedure does restore 11325-boot.img but nevermind it is binary the same as in the original 11.3.2.6_user_326002520 image included.

Calibaan said:
It´s still possible to root 11.3.2.6 with KindleSuite with a small tweak:
1.) Get an actual version from KindleSuite:
2.) Extract the archive and search in folder "/resources/tools" for the file "11325.bat" and make a backup of this file
3.) open "11325.bat" in a text editor
4.) search for the code line
Code:
adb shell chmod 755 /data/local/tmp/*
replace this line with the following code lines:
Code:
adb shell chmod 755 /data/local/tmp/su
adb shell chmod 755 /data/local/tmp/exploit
adb shell chmod 755 /data/local/tmp/rootme.sh
5.) save the edited file
6.) start KindleSuite, go to Root section and select the "11.3.2.5" entry (which leads to the edited Batch skript)
7.) start the rooting procedure as described by KindleSuite
8.) profit
This is just a small tweak to fix the chmod permission problems with the original script but I think KindleSuite will be updated in a few days.
P.S.: the KindleSuite root procedure does restore 11325-boot.img but nevermind it is binary the same as in the original 11.3.2.6_user_326002520 image included.
Click to expand...
Click to collapse
Just says waiting for device after i select 11.3.2.5

Of course you still need an ADB connection and a fastboot cable for rooting the 7" Kindle and according to the "Waiting for device..." ADB connection is not established.