Database Info

[Q] Goes through the root process, but root never occurs

Not sure what is going on but makes me feel stupid. I have the followed the steps to root my kindle fire 8.9, including authorzing other software and the ADB... I can ping 4.2.2.2 and get results. I downloaded the the ADB drivers zip file, expanded to get all the files, ran the runme.bat file, got successful, unlocked the kindle when it asked, but when the process was finished, I was still sitting with kindle fire original software/Rom. Any ideas what I may have missed or what happened? Thanks!

Did yu slct usb debugging mode?it cn b a issue wth that too
Hit thanks rather typing
SENT FROM MY LAVA IRIS 455 using xda developers app

I know nothing about kindle at all but I do know that some android root methods aren't one click, meaning you could very well have root access now. That doesn't mean that anything has changed, you just now have the access needed to change it. you might still need to install Superuser or Supersu app from the play store and maybe a custom recovery.

[rom] [kfsowi 2013] kindle water beta 1!

***DEPRECATED***
THERE ARE FAR MORE FUNCTIONAL ROMS AT THIS POINT!
PLEASE VISIT http://www.kfsowi.com FOR MUCH BETTER ROMS!
I'm going to leave this up just because.
ROM
•°•KINDLE WATER Beta•°•
Beta 2
Based on 11.3.2.1, and I recommend NOT doing this on http://11.3.2.2/11.3.1.0 as I don't know if the kernel has changed to be incompatible. UPDATE: this IS compatible with other versions, there is just an extra step I added below.
Special thanks to Gran PC. Without his help, this wouldn't be possible.
So, what is Kindle Water Beta? Kindle water beta is a far superior firmware to the one that comes stock on our Fire HD's. Why you ask? This is why:
FEATURES:
•No Amazon Garbage
•No Lockscreen Ads.
(They show up again. Turn them off by going to /data/securedstoragelocation/ in a file explorer, select the adunits folder, and remove all permissions)
•No Unwanted Updates
•Wallpaper
•AOSP settings
•Cyanogenmod Gallery App
•Google Play Store & services included & working
•XPOSED Included
•Better navbar using UDN. (Configure in UDN app. Setting it to appear by swiping up from the bottom of your screen is the best way to configure it)
•Gravity box included (Set it to hide Navbar or you will get a double Navbar)
•APEX Launcher
BUGS:
•Not everything is set up perfectly on first boot. You may need to play with Gravity Box, Apex Settings, and UDN to get everything working right. (Specificaly: Set UDN's Trigger to be a swipe from the bottom of the screen, Hide Navbar in Gravity Box, and Turn on tablet ui in Apex if you'd like)
•Some Settings Menus don't work. (Only nonessential ones)
•"Wireless" and "Help" status bar pulldown shortcuts are broken
-------------
CHANGELOG:
•Beta 2- More internal Amazon things have been removed from the ROM.
•Beta 1- First release (Removed)
-------------
INSTALLATION:
(Disclaimer: I take no responsibility for broken devices, but I will try to help you fix it if it does not work)
(Downloads below)
(REPLACE "PATH/TO/DOWNLOADED" WITH THE PATH TO YOUR DOWNLOADED FILE!!!)
•Download Gran PC's minisystem image from his Google Drive page. (Link is posted below)
•Move my system.img (each beta version is in its own named folder in my Google drive, the link is below) to your kindle's SD card.
•Plug powered-off kindle into your computer with fastboot cable.
*•If coming from a version NOT 11.3.2.1, download the boot-prod.img from my Gdrive, (Same link as
Roms down below) Then type "fastboot -i 0x1949 flash boot /path/to/downloaded/boot-prod.img" and hit enter and wait for it to complete.*
•fastboot flash the minisystem image. (fastboot -i 0x1949 flash system /path/to/downloaded/minisystem.img)
•when it finishes, unplug the Kindle and turn it off.
•plug it in with a REGULAR micro-usb cable.
•It will boot up into a very minimal system. (No UI at all I believe)
•type "adb shell" hit enter.
•type "su" hit enter
•type "dd if=/sdcard/system.img of=/dev/block/mmcblk0p9" hit enter.
WAIT FOR IT...
•When it finishes, hard reboot your tablet.
•It should boot up and you're good to go.
•activate ALL xposed modules in the xposed installer app. This will enable wallpaper and block updates. Goto gravitybox's lockscreen area and enable rotation to fix it not rotating.
•lockscreen ads will show again. Turn them off by going to /data/securedstoragelocation/ in a file explorer, select the adunits folder, and remove all permissions).
Thats all.
DOWNLOAD ROM: https://drive.google.com/folderview?id=0B0MtKyW31T-BeGNva05paGJoRVE&usp=sharing
EACH ROM VERSION HAS ITS OWN FOLDER!!!
BOOT-PROD.IMG IS IN THE SAME LINK AS ABOVE! ^^^^ (I take no credit for this file. It is unmodified, Amazon code. Use at your own risk)
Minisystem.img: https://gmf.dabbleam.com/KFSOWI/minisystem.img

Shouldn't you be making backups before flashing.

Maromi said:
Shouldn't you be making backups before flashing.
Click to expand...
Click to collapse
Yeah, but I think that's a given.
Sent from my KFSOWI Running The Kindle-Water Beta 1 ROM

Will surely try this later on tonight.
The link to the minisystem img file is a 404

Flashing a ROM with no disaster recovery or at least a backup is risky. @Mineturtle33 do you have a source code for this? It's a nice start though. That tablet may get a full makeover yet.
Edit: If there is a source code available.
Sent From Kindle Fire HD 7 running CM 11 4.4.2

The 2013 has a method to recover to stock, making backups its useless though because the system image is too big for fastboot's buffer, hence we have a weird recovery procedure. This is interesting, I'll have to check how big the system.img is out of curiosity.
Sent from my Amazon Kindle Fire HD using Tapatalk

stunts513 said:
The 2013 has a method to recover to stock, making backups its useless though because the system image is too big for fastboot's buffer, hence we have a weird recovery procedure. This is interesting, I'll have to check how big the system.img is out of curiosity.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
The image is 1.22 GB
Sent from my KFSOWI Running The Kindle-Water Beta 1 ROM

LinearEquation said:
Flashing a ROM with no disaster recovery or at least a backup is risky. @Mineturtle33 do you have a source code for this? It's a nice start though. That tablet may get a full makeover yet.
Edit: If there is a source code available.
Sent From Kindle Fire HD 7 running CM 11 4.4.2
Click to expand...
Click to collapse
No source for the ROM, but I believe there is for the minisystem.img. Feel free to modify/redistribute this as much as you'd like.
Sent from my KFSOWI Running The Kindle-Water Beta 1 ROM

juanfers said:
Will surely try this later on tonight.
The link to the minisystem img file is a 404
Click to expand...
Click to collapse
Fixed the 404 error. Sorry about that.
Sent from my KFSOWI Running The Kindle-Water Beta 1 ROM

LinearEquation said:
Flashing a ROM with no disaster recovery or at least a backup is risky. @Mineturtle33 do you have a source code for this? It's a nice start though. That tablet may get a full makeover yet.
Edit: If there is a source code available.
Sent From Kindle Fire HD 7 running CM 11 4.4.2
Click to expand...
Click to collapse
We have a recovery method.
Sent from my KFSOWI Running The Kindle-Water Beta 1 ROM

stunts513 said:
The 2013 has a method to recover to stock, making backups its useless though because the system image is too big for fastboot's buffer, hence we have a weird recovery procedure. This is interesting, I'll have to check how big the system.img is out of curiosity.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Well,not quite. Gran PC found something called "fastboot multiflash" which allows you to flash ridiculously large system images. I don't know how it really works. You can check it out in his Google Plus post.
Sent from a piece of KitKat

The reason I use the minisystem to dd the system.img to /system instead of fastboot flashing is because the img file can't fit in the fastboot buffer. @Anonymous.123
Sent from my KFSOWI Running The Kindle-Water Beta 1 ROM

Hi,
I've try to upgrade my kindle, but when I connect it with fastboot cable the system (Win7 32bit) configure it like Adb Android but the command adv devices not recognize any.
I also try with on Ubuntu 13.10 and also here the adb devices not recognize any.
Can you send me the driver you have used to install ?
Thanks a lot.

First of all. Make sure adb is on in settings. Secondly. You don't need adb until you install minisystem with fastboot. Use Ubuntu. I do not give drivers support for windows. @slim_s200
Sent from my KFSOWI Running The Kindle-Water Beta 1 ROM

Anonymous.123 said:
Well,not quite. Gran PC found something called "fastboot multiflash" which allows you to flash ridiculously large system images. I don't know how it really works. You can check it out in his Google Plus post.
Sent from a piece of KitKat
Click to expand...
Click to collapse
o.0 this is interesting i looked it up on google, very interesting way to implement that, if what i read is that same, then fastboot on the pc would split it up into several segments and then send them in multiple flashes. Thats pretty cool.

slim_s200 said:
Hi,
I've try to upgrade my kindle, but when I connect it with fastboot cable the system (Win7 32bit) configure it like Adb Android but the command adv devices not recognize any.
I also try with on Ubuntu 13.10 and also here the adb devices not recognize any.
Can you send me the driver you have used to install ?
Thanks a lot.
Click to expand...
Click to collapse
When you plug it in with a fastboot cable, you don't need adb commands, and adb won't see it. You need to use fastboot commands.
Sent from my Galaxy Nexus using Tapatalk

This is great!
Would you mind posting some screenshots of the AOSP settings and status/nav bars?

Forgive my ignorance, but what is the advantage does this have over CM11?
Sent from my GT-I9300 using XDA Premium 4 mobile app

bryanchapman9999 said:
Forgive my ignorance, but what is the advantage does this have over CM11?
Sent from my GT-I9300 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well,none. But at least it is better than the stock Amazon OS. And by better I mean REALLY good? .
Sent from a piece of KitKat

Mineturtle33 said:
When you plug it in with a fastboot cable, you don't need adb commands, and adb won't see it. You need to use fastboot commands.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Thanks for your reply, but, I've ask fot the drivers because when I've try to type the fastboot command it returned the error "File minisystem,bin" not found!
I've check the path, but this is ok, /storage/sdcard0/FILE.bin and also try /sdcard/FILE.bin nothing change, any ideas?
Thanks.

(Q) How to root Mediapad X2?

I used lots of methods trying to root Huawei Mediapd X2 but got no lucks.
Anybody gets successful?

I happened to see there is an article published recently on this an some comments say they succeeded. I didn't try it myself, as I am not sure the Super-Root.apk used in the article is safe or not.
(Please replace the <dot> to . in the URL as I don't have permission to put links.. Sorry for the inconvenience..)
www<dot>how-to-root<dot>club/2015/04/huawei-mediapad-x2-7075.html
vuhongduong said:
I used lots of methods trying to root Huawei Mediapd X2 but got no lucks.
Anybody gets successful?
Click to expand...
Click to collapse
---------- Post added at 04:21 PM ---------- Previous post was at 04:06 PM ----------
I did some more search and found the file Super-Root.apk is actually Framaroot version 1.4.1 (you can tell that from the MD5 checksum.) There is new version available and you can try it from
forum<dot>xda-developers<dot>com/apps/framaroot/root-framaroot-one-click-apk-to-root-t2130276
tozhangkai said:
I happened to see there is an article published recently on this an some comments say they succeeded. I didn't try it myself, as I am not sure the Super-Root.apk used in the article is safe or not.
(Please replace the <dot> to . in the URL as I don't have permission to put links.. Sorry for the inconvenience..)
www<dot>how-to-root<dot>club/2015/04/huawei-mediapad-x2-7075.html
Click to expand...
Click to collapse

tozhangkai...the first link just goes to an endless circle of surveys (have seen that before for other files...i do not know if people really are able to get files from that link..but appears you have)
Framaroot...1.4.1 is an old one from October last year..the latest is 1.93 and that does not even run anyway (immediately has a message saying basically that this exploit does not work for the system)..anyway both do not work
EDIT
i also tried srs one click root..went through several reboots,,,and said at the end the rooting was a success and that superuser apk was installed..but it wasn't
may have a go at it again later..(it came up with a message to accept and i missed it and it timed out on me)
http://www.srsroot.com

mac231us said:
tozhangkai...the first link just goes to an endless circle of surveys (have seen that before for other files...i do not know if people really are able to get files from that link..but appears you have)
Framaroot...1.4.1 is an old one from October last year..the latest is 1.93 and that does not even run anyway (immediately has a message saying basically that this exploit does not work for the system)..anyway both do not work
EDIT
i also tried srs one click root..went through several reboots,,,and said at the end the rooting was a success and that superuser apk was installed..but it wasn't
may have a go at it again later..(it came up with a message to accept and i missed it and it timed out on me)
http://www.srsroot.com
Click to expand...
Click to collapse
I tried this with no success. It says root complete, but nothing doing. I also tried kingoroot, more of the same.
Sent from my GEM-703L using XDA Free mobile app

That is why I am looking at rooting it through the system image itself (see my other posts on this and where I posted the link for complete firmware..on the mediapad x2 announced thread) but will flash only if highly confident as doing this for the first time for any phone (that is, rooting myself through system image)..need someone with the skills here to step in
Sent from my GEM-703L using XDA Free mobile app

mac231us said:
That is why I am looking at rooting it through the system image itself (see my other posts on this and where I posted the link for complete firmware..on the mediapad x2 announced thread) but will flash only if highly confident as doing this for the first time for any phone (that is, rooting myself through system image)..need someone with the skills here to step in
Sent from my GEM-703L using XDA Free mobile app
Click to expand...
Click to collapse
I wish I could help you. Thanks for your work so far.
Sent from my GEM-703L

Hehehe... Looking for the same thing here and i can see it's not easy ! Just got the tablet a week ago and so far, i'm impressed. I guess we will have to wait a bit until more people start hacking that new tablet away..
Homer J. Fong said:
I wish I could help you. Thanks for your work so far.
Sent from my GEM-703L
Click to expand...
Click to collapse

miroul said:
Hehehe... Looking for the same thing here and i can see it's not easy ! Just got the tablet a week ago and so far, i'm impressed. I guess we will have to wait a bit until more people start hacking that new tablet away..
Click to expand...
Click to collapse
Yeah, patience is not a virtue I possess in my normal life, but because of the people giving of their free time and effort I've never found it hard to wait for this stuff.
Sent from my trltetmo

Unlock is required before trying any root method.

use below URL to apply for unlock code:
http://www.emui.com/plugin.php?id=unlock&mod=unlock&action=apply
It's a Chinese web page, but easy to guess.
If the web page doesn't work, take a snapshot of the phone box with IMEI and SN number, send to [email protected] requesting for unlock code.
They'll reply in 2~4 weeks, too slow. An email with 16 number unlock code.
Use fastboot unlock OEM to unlock the bootloader.
Root and 3rd party recovery is only possible after the unlock.

For now, you cannot unlock even if you get the code

I unlocked bootloader , but the root can not be done any program .

I did unlock and someone showed that the root genius can root the phone via adb command.
The bad news is that I can't install the adb driver somehow

Root genius can not handle it . I can not install any CWM recovery. Maybe someone has any advice ?

citybobby said:
For now, you cannot unlock even if you get the code
Click to expand...
Click to collapse
Can you elaborate more on this? I keep getting FAILED (remote: password wrong)
I verified the code, and even mailed Huawei and they responded with the same code.
Thanx

Let me know if u have flashed philz touch recovery for ur device.it has an inuilt rooting system which can ropt ur device easily.
Or u can try vroot.apk or kingo root both can root almost every device.
Sent from my A0001 using XDA Free mobile app
---------- Post added at 02:35 AM ---------- Previous post was at 02:31 AM ----------
Or u can try this one it will work for 100%.
1. Download Super-Root.apk for How To Root Huawei Mediapad X2 [Tutorial] from this link :
http://filesrightnow.com/file/05JRK
2. Connect your device to your PC using the USB cable.
3. Copy the Super-Root.apk over to the root of your SD card.
4. Once it’s been copied, disconnect your device from your PC.
5. Head to Menu>>Settings>>Security on your device and enable the Unknown sources option.
6. Open the File Manager app on your device and install the app you copied earlier to your device.
7. Once the app’s been installed, launch it from your App Drawer.
8. Select Install SuperSU from the first dropdown menu.
9. Select exploit, tap on it in the app.
10. The app should begin rooting your device, shouldn’t take too long to finish.
11. Reboot your device once it’s been rooted.
12. You’re all done! Excellent! You’ve successfully How To Root Huawei Mediapad X2 [Tutorial] rooted your Android device using the Super-Root.apk app and you should now be able to see the SuperSU app in your App Drawer!
Sent from my A0001 using XDA Free mobile app

Cyanandroid said:
Let me know if u have flashed philz touch recovery for ur device.it has an inuilt rooting system which can ropt ur device easily.
Or u can try vroot.apk or kingo root both can root almost every device.
Sent from my A0001 using XDA Free mobile app
---------- Post added at 02:35 AM ---------- Previous post was at 02:31 AM ----------
Or u can try this one it will work for 100%.
1. Download Super-Root.apk for How To Root Huawei Mediapad X2 [Tutorial] from this link :
http://filesrightnow.com/file/05JRK
2. Connect your device to your PC using the USB cable.
3. Copy the Super-Root.apk over to the root of your SD card.
4. Once it’s been copied, disconnect your device from your PC.
5. Head to Menu>>Settings>>Security on your device and enable the Unknown sources option.
6. Open the File Manager app on your device and install the app you copied earlier to your device.
7. Once the app’s been installed, launch it from your App Drawer.
8. Select Install SuperSU from the first dropdown menu.
9. Select exploit, tap on it in the app.
10. The app should begin rooting your device, shouldn’t take too long to finish.
11. Reboot your device once it’s been rooted.
12. You’re all done! Excellent! You’ve successfully How To Root Huawei Mediapad X2 [Tutorial] rooted your Android device using the Super-Root.apk app and you should now be able to see the SuperSU app in your App Drawer!
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Haven't tried flashing anything yet (can't unlock bootloader) but I wanted to point out that KingoRoot, VRoot (a.k.a iRoot) and Super-Root all do NOT work. They all fail (with varying behavior and/or error messages). Running the B013 OTA update.

Did the B013 ota update worked for u?
Sent from my A0001 using XDA Free mobile app

Cyanandroid said:
Did the B013 ota update worked for u?
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Not sure what you mean but I'm on build number GEM-703LV100R001C233B013
Now If only I can root

shassouneh said:
Not sure what you mean but I'm on build number GEM-703LV100R001C233B013
Now If only I can root
Click to expand...
Click to collapse
Just send Huawei an Email with your IMEI #, Model Number, Serial Number and Product Number telling them you keep getting an error when trying to unlock your phone from their website. That's what I did. Of course you need to be unlocked before you can do any of the following.
-Make sure you have the drivers installed for the phone
-Plug the USB cable into the computer and into the phone
-Turn phone off and while turning it back on hold volume down and phone will enter download mode
-Download Android Platform tools from my Dropbox I made it easier for everyone. (The super_bootb013.apk file is included)
https://www.dropbox.com/sh/7dgdl6r2nftz5mt/AABvdjdt4a4zRNAsSE1QR2Oaa?dl=0
-Right click on the Android Platform Tools folder while holding in Shift and select Open Command Window Here
-When the command prompt opens type in fastboot flash boot super_boot.b013.img
-After it finishes, type in fastboot reboot. The phone will boot normally.
-Then you have two options. Download SuperSU from the Google Play Store, install it, open up and update the binary if it prompts you.
or
-Included in my Android Platform Tools folder is the Superuser.apk file. Just install that manually, then open it and update the binaries. When you reboot you will be rooted. This works on B013 only.
-I also installed the Chinese TWRP and even though I can't read Chinese, I have no problems getting around in it.

Possible root method?

I just came across this possible root method while searching for one on the Fire 8. It's dated for April 4 so it's recent. Though it's for 5.3.2.1, if it does work, maybe can be modified for 5.3.3.0?
https://www.quora.com/How-do-I-root-Kindle-Fire-HD-8-6th-Gen-2016
I'm on my tablet so can't copy and paste the steps. If someone else could?

DragonFire1024 said:
I just came across this possible root method while searching for one on the Fire 8. It's dated for April 4 so it's recent. Though it's for 5.3.2.1, if it does work, maybe can be modified for 5.3.3.0?
https://www.quora.com/How-do-I-root-Kindle-Fire-HD-8-6th-Gen-2016
I'm on my tablet so can't copy and paste the steps. If someone else could?
Click to expand...
Click to collapse
How interesting. I wonder if it will work on the earlier firmware versions too like 5.3.1.0 and 5.3.1.1. That way, don't have to mess with Kingoroot and anything that was put in there that will help the Chinese cyber-attack capability..lol. I'm on 5.1.1, but I'm too lazy to wipe it and try it..maybe later. Unless someone else wants to give it a go?
As far as I know, no root exists for 5.3.3.0. Alexa is a whore.

smokejumper76 said:
How interesting. I wonder if it will work on the earlier firmware versions too like 5.3.1.0 and 5.3.1.1. That way, don't have to mess with Kingoroot and anything that was put in there that will help the Chinese cyber-attack capability..lol. I'm on 5.1.1, but I'm too lazy to wipe it and try it..maybe later. Unless someone else wants to give it a go?
As far as I know, no root exists for 5.3.3.0. Alexa is a whore.
Click to expand...
Click to collapse
I may give it a go. I don't stand to lose anything really. I'm working on a project at the moment regarding Wireless Display (Miracast) though and I don't want to lose any of that so I have to make a back up. No root is supposed to exist for 5.3.2.1 either

DragonFire1024 said:
I may give it a go. I don't stand to lose anything really. I'm working on a project at the moment regarding Wireless Display (Miracast) though and I don't want to lose any of that so I have to make a back up. No root is supposed to exist for 5.3.2.1 either
Click to expand...
Click to collapse
Note there have been reports 5.3.3.0 can be rolled back to 5.3.2.1 on the 5th gen Fire. Not sure if this also applies to 6th gen HD 8. Typically a failed/invalid rollback results in a non-recoverable brick; not something to mess around with lightly.
---------- Post added at 08:40 PM ---------- Previous post was at 08:33 PM ----------
DragonFire1024 said:
I just came across this possible root method while searching for one on the Fire 8. It's dated for April 4 so it's recent. Though it's for 5.3.2.1, if it does work, maybe can be modified for 5.3.3.0?
https://www.quora.com/How-do-I-root-Kindle-Fire-HD-8-6th-Gen-2016
I'm on my tablet so can't copy and paste the steps. If someone else could?
Click to expand...
Click to collapse
Don't get your hopes up. This is a generic tool that lacks favorable references (recent or otherwise) in trusted Android communities. Good luck.

Davey126 said:
Note there have been reports 5.3.3.0 can be rolled back to 5.3.2.1 on the 5th gen Fire. Not sure if this also applies to 6th gen HD 8. Typically a failed/invalid rollback results in a non-recoverable brick; not something to mess around with lightly.
---------- Post added at 08:40 PM ---------- Previous post was at 08:33 PM ----------
Don't get your hopes up. This is a generic tool that lacks favorable references (recent or otherwise) in trusted Android communities. Good luck.
Click to expand...
Click to collapse
I won't give up hope. I'm pretty convinced we'll eventually get root or the bootloader's unlocked. Something tells me Amazon's stock wasn't soaring because of these things or for that matter their so called FireOS. It's only a matter of time.
Just an observation when bricking my XT907 a few days ago (being flashed as we speak...drum roll) I noticed more than one recovery mode. Two for sure, maybe three. There is the generic black screen and white font...you can choose reboot, recovery, wipe partition and fastboot or what not. Well there's also an Android 'Droid Master Reset.' Would that reset to factory or to stock prior to Motorola customization? I've always done it through the first screen. I'm just wondering in case there might be something to exploit in those options. Does a real total Master Reset exist at all for these tablets? Prior to FireOS?

DragonFire1024 said:
I won't give up hope. I'm pretty convinced we'll eventually get root or the bootloader's unlocked. Something tells me Amazon's stock wasn't soaring because of these things or for that matter their so called FireOS. It's only a matter of time.
Click to expand...
Click to collapse
Much has happened over the past 12-15 months to bolster Android security some of which undoubtedly has made it to FireOS. Past techniques used to secure root will be far less effective moving forward.
DragonFire1024 said:
Just an observation when bricking my XT907 a few days ago (being flashed as we speak...drum roll) I noticed more than one recovery mode. Two for sure, maybe three. There is the generic black screen and white font...you can choose reboot, recovery, wipe partition and fastboot or what not. Well there's also an Android 'Droid Master Reset.' Would that reset to factory or to stock prior to Motorola customization? I've always done it through the first screen. I'm just wondering in case there might be something to exploit in those options. Does a real total Master Reset exist at all for these tablets? Prior to FireOS?
Click to expand...
Click to collapse
Never heard of or seen a low level "Master Reset" function in an Amazon device (dating back to 2nd gen Fire HD) or any Android device for that matter.

DragonFire1024 said:
I may give it a go. I don't stand to lose anything really. I'm working on a project at the moment regarding Wireless Display (Miracast) though and I don't want to lose any of that so I have to make a back up. No root is supposed to exist for 5.3.2.1 either
Click to expand...
Click to collapse
Wishing for your success! Really hoping to have new root for this. :fingers-crossed:

Where is the download for this? When I do a search for "SuperOneClick" I get a tool for Gingerbread or older.

ShapeShifter499 said:
Where is the download for this? When I do a search for "SuperOneClick" I get a tool for Gingerbread or older.
Click to expand...
Click to collapse
Here's their site http://www.superoneclickdownload.com/
I've seen the method before in other forums ranging from a few months to a few years. I don't recall which ones or if they worked.
If anyone does try, I recommend following the steps here: http://www.pcworld.com/article/244303/how_to_root_your_kindle_fire.html At least the source is a little bit more 'legit' for lack of better terms.

Is it available for all firmwares??
I've been waiting on 5.3.2.1 for a root strategy on Kingroot and Kingoroot, but after about one year, They can't root my device.
And what is the advantage of using this method? Is it better than Kingroot?

Someone tried this method? It works? Thanks in advance for your responses.

behrad said:
Is it available for all firmwares??
I've been waiting on 5.3.2.1 for a root strategy on Kingroot and Kingoroot, but after about one year, They can't root my device.
And what is the advantage of using this method? Is it better than Kingroot?
Click to expand...
Click to collapse
Didn't work for me but I may not have done it right.

The Steps Are As Follows:
"
Step 1: Turn on your Kindle Fire and tap the top bar, near the battery and Wi-Fi icons; press More... from the drop-down menu, then Device, and tap Allow Installation of Applications to On.
Step 2: Download the Android SDK from the Android Developer site. Get the version with an installer app (installer_r15-windows.exe).
Step 3: Download the Java Development Kit (version 7, at the time of this writing). Make sure to download the appropriate version of the Java Development Kit for your PC--I'm on a 32-bit Windows 7 PC, so I downloaded the Windows x86 version.
Step 4: Install the Java Development Kit. Make sure you do this before you install the Android SDK. All you need to do is to open the installer file you downloaded (mine was called jdk-7u1-windows-i586.exe) and click through the installer wizard.
Step 5: Install the Android SDK. Simply open installer_r15-windows.exe and follow the instructions. Once the Android SDK is finished installing, the SDK Manager app will automatically open with a list of software packages you can download. Go ahead and install all the prechecked packages, but make sure that the Google USB Driver package (listed under Extras) is checked. You'll need this file to let your PC communicate with the Kindle Fire. Wait for SDK Manager to download install and all the packages, and don't panic if it asks you for permission to kill a server or process. Just click OK until it's all done with the install process.
Step 6: Now that you have the SDK installed, you'll have to make two quick modifications to it before you can root the Kindle Fire. First, open up your User Account folder in Windows (C:\Users\(Your Account Name), find the new ".android" directory, and find a file called adb_usb.ini. Open it up in Notepad, add a new line at the bottom of the document, and type 0x1949. Make sure that string is on its own line in the document, save it, and close it. Next, go to wherever you installed the Android SDK itself (probably C:\Program Files\Android\android-sdk), and navigate to the \extra\google\usb_driver\ directory. Find the file called android_winusb.inf and open it in Notepad. There, you'll want to take the following lines and paste them immediately underneath the [Google.NTx86] and [GoogleNTamd64] headings in the document:
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
Save the file and exit Notepad. If Notepad doesn't let you overwrite android_winusb.inf when you're saving it, save the edited version to your desktop, and then drag the edited version over to the usb_driver directory to replace the old version with your edited version. Windows may ask you for Administrator permission to replace android_winusb.inf--don't worry, it's fine.
Step 7: Plug your Kindle into your PC. You'll need a micro-USB cable to do this, which the Fire doesn't ship with, so you'll have to buy that cable if you don't already have one that you use with your phone or camera. Windows will probably automatically attempt to install a driver for it, fail, and then mount it as a normal storage device. That's fine, though we may have to change something there later.
Step 8: Now that your PC and Kindle are connected, we're going to open up the Android SDK to make sure it recognizes the Kindle. Open up Command Prompt in Windows (Start Menu, All Programs, Accessories, Command Prompt) and navigate to wherever you installed the Android SDK.
Don't remember your DOS commands? That's okay--just open up the Command Prompt and type cd followed by the file path to the platform-tools directory (for example: cd C:\Program Files\Android\android-sdk\platform-tools\). Once you're there, type adb kill-server, press Enter, type adb devices, and then press Enter again. You should see the Command Prompt return with "List of devices attached" and a string of numbers followed by "device"--that means the Android SDK recognizes the Kindle is attached, and you're ready to proceed to the next step.
However, if you don't have any devices listed, it probably means that Windows isn't using your Android SDK USB driver to communicate with your Kindle Fire. Go to Control Panel in Windows, open Device Manager, and scroll down the list of devices until you find your Kindle listed. Right-click the listing and select Update, then click Browse my computer for driver software, Browse, and navigate to the directory that holds the file you edited earlier called android_winusb.inf--probably C:\Program Files\Android\android-sdk\extras\google\usb_driver. Click Next; Windows should now switch over to the Android SDK USB driver for your Kindle. Go back to the Command Prompt; type adb kill-server, press Enter, then type adb devices, and press Enter again. You should see something show up under the list of attached devices.
Step 9: Now you're ready to root your Kindle. All you have to do is download SuperOneClick (and Microsoft's NET 2.0 Framework, if you don't already have it installed), install both apps, open up SuperOneClick, and click Root.
Let SuperOneClick do its thing--the entire process takes a few minutes--and when it's done, go back to the Command Prompt, type adb kill-server, and press Enter. Then, just to be sure, click on the Safely Remove Hardware and Eject Media icon in the Windows Notification Area (usually a picture of a plug with a green checkmark on it), eject the Kindle, and unplug it. Congratulations--you have root access!
" - Qoura, Anya General
---------- Post added at 01:00 PM ---------- Previous post was at 12:54 PM ----------
DragonFire1024 said:
Just an observation when bricking my XT907 a few days ago (being flashed as we speak...drum roll) I noticed more than one recovery mode. Two for sure, maybe three. There is the generic black screen and white font...you can choose reboot, recovery, wipe partition and fastboot or what not. Well there's also an Android 'Droid Master Reset.' Would that reset to factory or to stock prior to Motorola customization? I've always done it through the first screen. I'm just wondering in case there might be something to exploit in those options. Does a real total Master Reset exist at all for these tablets? Prior to FireOS?
Click to expand...
Click to collapse
So you mean to find a way to factory reset the kindle to before it had fire OS, when it still had an unmodified android os(or whatever they came with first)?
If so, that sounds like a possible exploit, though I think Amazon has probably made sure that it was impossible without a brick.

So this giant post is simply and advert for SuperOneClick which is an old rooting method that hasn't worked for years.

Davey126 said:
So this giant post is simply and advert for SuperOneClick which is an old rooting method that hasn't worked for years.
Click to expand...
Click to collapse
Not to mention a lot of links I found in the near past, redirect to Kingroot who I suspect either bought OneClick or put them out of business.

Pre-Installing APKs on Nexus Player Oreo stock rom

This really should be asked in the dev forum, But my post count is not high enough or worthy!
I have several Nexus Players I plan on selling with the oreo update pre installed, There are 2 addl non playstore apps I need to include as part of the package.
I'm trying to avoid "profiling" the devices to add the 2 extra apps. I have flashed the oreo upgrade to all 8 of them.
I cannot push the apks without profiling to enable adb nor can I seem to find a good zip template to make use the bootloader recovery adb function.
I have tested a few and they all fail with footer and signature failures? I'm only left with a few ideas. Please comment if you can help with any of the options below or suggest a better one..
1. Find a proper update.zip template that works with nexus player..Oreo 8.0 or can bypass the check..
2. Can apps installed in a profiled device be preserved thru a reset method that would allow the device to startup with the first run screens re-instated? Remote setup, WiFi, User account.. Out of the box experience?
3. Can an APK or ZIP be copied to a location on the Nexus Player that would allow it to be installed on first run? (I seem to think Youtube does this)
4. Least popular... Modify the Oreo upgrade img to have the 2 apps pre installed? <--This option looks messy..
Any suggestions appreciated!! Thanks

I suppose #2 is possible if you install as a system app.
Sent from my KFFOWI using Tapatalk

rufy93 said:
I suppose #2 is possible if you install as a system app.
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
After careful examination, #2 and #4 are really the same thing. Without root, I would have to mount the oreo system.img file in linux and add the 2 apks to root/system/app then repack the img file to re-burn the rom. Not exactly sure if that would be enough, I assume there is some checksum or signing in the image file to prevent guys like me from modifying it. Also what would happen after google hits it with an update? would these apps survive? Finding the answer to why the stock Oreo bootloader recovery adb fails to accept the typical update zip format will end up being the right solution.

If you wish to flash using the stock recovery, the update zip must be properly signed. This usually means by the oem private keys.
I haven't been following the modding scene for a long time, but I'm sure these are still inaccessible.
Sent from my KFFOWI using Tapatalk