***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.
Related
I found less detailed guide on rootzwiki created by birdman, but i decided to repost it here in more detail.
* Disclaimer: I do not take any responsibility for anything you do to your phone, whether be brick, break, or somehow mess it up.
Requirements
1. You must have the sdk installed and you are able to access, and use adb and fastboot.
2. You must have debugging enabled on your Nexus 7.
3. Download Su here (Chainfire's thread for supersu) (Thanks Eric_Eric_Eric)
4. Download CWM here. Scroll down to Nexus 7 and choose whether touch or regular.
Pre-Steps
To make this easier, you should put the su zip on the sdcard for later.
1. In terminal, cd to the directory you have your sdk in. Then cd into platform-tools.
2. Type adb push path-to-zip/JB-SuperSU.zip /sdcard
Unlocking Your Nexus 7
To unlock your device
1. cd to platform-tools
2. Reboot to the bootloader - adb reboot bootloader
3. Unlock your device* -
fastboot oem unlock *You will have to accept and erase all the user data on the tablet.
*You must run this as sudo in Linux
Flash Clockwork Mod Recovery
(You're still inside the bootloader)
4. Flash CWM -
fastboot flash recovery path-to-img/CWM-grouper-recovery.img5. Make CWM Permanent -
1. Boot into recovery2. Go to Mounts and Storage3. Mount /System4. Type in Terminal*adb shell
cd /system
mv recovery-from-boot.p recovery-from-boot.bak
If your having trouble gaining shell, try "adb kill-server" then "abd start-server". Couple of my friends had this problem, and this should hopefully fix it.
* For some people, it has been reported that you don't have to replace recovery-from-boot.bak. The flash is enough to make the recovery stick.
Flash Su
1. Go back by pressing power button2. Install the zip in the sdcard
Reboot and your device is now rooted!!
For anybody having trouble trying to use fastboot and come up with a no-permissions error or adb ????????? problem, I created a guide to fix the problem here: [GUIDE]Fix Fastboot and USB
Any ugly splash screens indicating it has been unlocked?
No SD Card!
Not to be a jackass or anything, but this tablet has no SD Card slot...might that require slightly different steps than what you outlined?
jorge_culv said:
Not to be a jackass or anything, but this tablet has no SD Card slot...might that require slightly different steps than what you outlined?
Click to expand...
Click to collapse
I'm sure he meant internal storage.
Is there a way to do this without adb? I'm sort of new to adb....any help would be greatly appreciated. Ty
Sent from my SAMSUNG-SGH-T989 using xda premium
jorge_culv said:
Not to be a jackass or anything, but this tablet has no SD Card slot...might that require slightly different steps than what you outlined?
Click to expand...
Click to collapse
What he wrote about pushing SU to /sdcard is correct. I have a Transformer Prime and ASUS called the internal storage /sdcard, which is a little counter intuitive. I presume the same situation exists with the Nexus 7.
paddycr said:
What he wrote about pushing SU to /sdcard is correct. I have a Transformer Prime and ASUS called the internal storage /sdcard, which is a little counter intuitive. I presume the same situation exists with the Nexus 7.
Click to expand...
Click to collapse
This is correct. There is no emmc internal storage. Its just called sdcard
Sent from my Galaxy Nexus using xda app-developers app
movieaddict said:
Is there a way to do this without adb? I'm sort of new to adb....any help would be greatly appreciated. Ty
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Umm, this no way to do this without adb. I'm working on a one click script which i will be posting later. I am currently in IO Sessions and should have it in the next couple of days.
But an answer, again, no, there isn't. You need to download the sdk, and install the tools. then just cd to platform-tools, and use adb like i said. If your in windows, use adb.exe then the arguments, but if your in linux, just use ./adb. Same thing with fastboot.
khaytsus said:
Any ugly splash screens indicating it has been unlocked?
Click to expand...
Click to collapse
Ya, there is, its the Google logo with the unlocked sign at the bottom, just like the galaxy nexus.
FadedLite said:
Umm, this no way to do this without adb. I'm working on a one click script which i will be posting later. I am currently in IO Sessions and should have it in the next couple of days.
But an answer, again, no, there isn't. You need to download the sdk, and install the tools. then just cd to platform-tools, and use adb like i said. If your in windows, use adb.exe then the arguments, but if your in linux, just use ./adb. Same thing with fastboot.
Click to expand...
Click to collapse
TY very much faded, looking forward to ur one click script!
what exactly does he fastboot OEM unlock do? just curious
Sent from my Amazon Kindle Fire using xda premium
smirkis said:
what exactly does he fastboot OEM unlock do? just curious
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
It tells fastboot to oem unlock the device.
Sent from my GT-P3113 using xda app-developers app
FadedLite said:
This is correct. There is no emmc internal storage. Its just called sdcard
Click to expand...
Click to collapse
I stand corrected, thanks and +1 for setting me straight!
stickmount?
Can someone rooted please test if stickmount works.
Thanks
Guide* and just wait there will be a one click root for this device
Sent from my HTC Vision using xda app-developers app
mintaeroboy said:
Guide* and just wait there will be a one click root for this device
Sent from my HTC Vision using xda app-developers app
Click to expand...
Click to collapse
Ya, that's me trying to write it while trying to take notes during a seminar at IO haha
But ya, I'm working on it right now.
I'm new to the tablet, so this maybe a silly question, but is it possible to use 4ext for recovery instead of CWM? I like the 4ext a lot more for my HTC Glacier.
what would unlocking do? isnt that for phones so you can put other simcards??
r0mmel said:
what would unlocking do? isnt that for phones so you can put other simcards??
Click to expand...
Click to collapse
It is technically "unlocking the boot loader" but unlocking was short and sweet for the title.
Sent from my Galaxy Nexus using xda app-developers app
[GUIDE]
Sent from my Xoom using xda premium
Thread closed.
Now also tested on ICS and JB...
Op thx will try that soon
Sent from my A7/A7+ using xda app-developers app
shreyans4020 said:
Op thx will try that soon
Sent from my A7/A7+ using xda app-developers app
Click to expand...
Click to collapse
You know, it would be great if many people test this. As I have only an x10 mini pro, it's rather hard for me to test this on other devices .
work on i9300 stock Rom
Thanks! you've saved a phone!
Working the linux command on i9300 stock rom 4.1.2 JZO54K ELLA with root and busybox installed
Thanks a lot!!!!
desmolab said:
Thanks! you've saved a phone!
Working the linux command on i9300 stock rom 4.1.2 JZO54K ELLA with root and busybox installed
Thanks a lot!!!!
Click to expand...
Click to collapse
No problem, bro, that's what I made this thread for. Anyway, thanks for reporting back!
I couldn't remember my unlock pattern. Tried flashing the .zip on my HTC Evo 4G LTE running Dirty Unicorn (based off Paranoid Android) but it didn't work (I'm Rooted, unlocked, S-Off with TWRP installed).
I was able to get in using my Google account after all though. The "forgot password" button didn't show before but it did after I rebooted and tried the pattern unsuccessfully 5 times. It showed up then (maybe the button stops showing AFTER 5 unsuccessful attempts until you reboot?).
SMS Bypass
Check out this app I made based on this principle.
http://forum.xda-developers.com/showthread.php?p=43146798
Kilroy. said:
Hey folks!
Assuming you forgot the Pattern/Password that you use to secure your phone. Of course,
you could get in using your Gmail account Password...
But what if you don have an account or you forgot the password to that, too???
Here are two possibilities:
.
.
.
B. For everyone without a recovery version installed:
What you need:
-A computer running a Linux distro (Ubuntu, Mint, etc.) NOTE: This Guide was written for MINT 14, but it should work on other distros, too.
-a USB cable to connect your phone to the PC
-adb installed (look at quick tutorial below)
INSTRUCTIONS:
1. Connect you (turned on) Phone to the Computer via USB.
2. Open a terminal window.
3. Type
Code:
adb devices
adb shell
cd data/system
rm *.key
4. Done!
Now you just have to reboot.
NOTE: The Pattern lock will probably still show up, but you can type in anything you want, as it will accept anything!
Please test this on every Android OS, as I have only tested it on GB so far, but, theoretically, it should work on any Android Version & ROM.
I know there are similar threads on xda, but this is the first that offers a tutorial for getting past almost all locks (Password, PIN, Pattern) instead of only he Pattern, and, of course, the first to offer a flashable zip.
Click to expand...
Click to collapse
Kilroy. said:
You know, it would be great if many people test this. As I have only an x10 mini pro, it's rather hard for me to test this on other devices .
Click to expand...
Click to collapse
I can confirm that i've tested this (Method B), using ADB in Windows and it worked on my Xperia T (Jellybean, firmware 9.1.A.1.141). Couple of points 'USB debugging' has to be enabled on the phone, had to add a 'su' command before the deletion line.
Code:
adb devices
adb shell
cd data/system
[B]su[/B]
rm *.key
Great
Sent from my GT-S5570 using xda app-developers app
WoW I was looking for this thing and here I am got this one ...
Thankz OP
Tried on Canvas A116, didn't work.
So say I had a att gs4, no root, no recovery. Just stock, would this work?
S-OFF
Boot Unlock (TAKE THAT AT&T!)
TWRP 2.6.3.0
Running something that'll probably change in a few days
for option B the manual is incomplete, missing add that you need to have previously active USB debugging option, if you had not activated, it will not work.
cesargdmi said:
for option B the manual is incomplete, missing add that you need to have previously active USB debugging option, if you had not activated, it will not work.
Click to expand...
Click to collapse
Tried even after activating USB debugging option still not working, I guess not for CHD.
Sent from my Micromax A116 using XDA Premium HD app
The zip did not work for me on a KitKat 4.4, BUT... I was able to delete the password files in /data/system with "fastboot boot openreco.img"... Luckly I had an unlocked phone. It has a file browser in advanced, came in handy.
Thanks Mate!
Even working on ages old Xperia X10 mini!
jodhaniohm97 said:
Thanks Mate!
Even working on ages old Xperia X10 mini!
Click to expand...
Click to collapse
NP
Sent from my Nexus 7 using xda app-developers app
Didn't work in KitKat(any ROM ) brother... But I thank u for ur efforts..
Sent from my GT-I9082 using Tapatalk
Works great on KitKat with TWRP (I didn't try your flashable zip, I just used the terminal built into twrp to run "rm *.key" in /data/system).
Update 1-21-14: Root for 5-0-11 available - go to pg 17 for details, pg 20 for new and improved method. Having said this, there are no real benefits to Android 4.3 over 4.2, so I recommend staying with 4-7-3.
Yes, folks after two days of trial and error I finally was able to build a system image file (from the US OTA update files) that you install via fastboot.
Install Instructions:
First, BACKUP! Use ASUS App Backup for installed Apps (and their data) and I also use My Backup to backup personal and system settings info. Once rooted, use My Backup Root (or keep using ASUS App Backup for Apps and My Backup (non-root) for everything else. Always Backup to your External SDcard as a Factory Reset (should you need to do one) or if you have to or accidently run 'fastboot erase userdata' will erase your internal SDcard.
Second, Charge your Battery - make sure you do any flashing with a good charge, battery going low during this process can do 'bad things'...
Linux Users Note: I'm using Ubuntu and fastboot will not recognize the MemoPad. Still trying to resolve this, the latest Windoze version of fastboot works.
Download ME302C-US-Root.img.gz from MediaFire (see below)
Install the Minimal ADB-Fastboot into a folder (google this you're on your own)
Install the ASUS USB Drivers (google this you're on your own)
Place the image file in the adb/fastboot folder (do not decompress, install as is)
Run these fastboot commands:
fastboot devices (make sure your MemoPad is connected)
fastboot erase cache
fastboot erase system
fastboot flash system ME302C-US-Root.img.gz
Reboot from MemoPad recovery menu
Install from Market:
SuperSU v1.86 Chainfire (required for all other apps to work)
Root Checker (run it to confirm you have root)
You are now rooted
Note: this install follows the ASUS update script that links various binaries in /system/bin to 'toolbox' so you may want to enhance that by installing BusyBox from the Market and use Safe Install method to add new links to the ones already set for toolbox (explained in busybox).
Enjoy your Rooted MemoPad!
Download the image file from here:
http://support.mediafire.com/download/avhe9zizn7z0t5w/ME302C-US-Root.img.gz
If the flash fails or doesn't root, you can just go back to the original OTA update by downloading it from ASUS and running:
fastboot erase cache
fastboot erase system
fastboot flash update US_ME302C-V4.7.3-0-ota-user.zip
Don't post questions about installing/using fastboot or USB drivers, it's been covered ad-nauseum here and other places - google is your friend. If you have the LTE model (ME302KL), that has a locked bootloader and requires the unlock utility available on the ASUS website before you run fastboot.
Thanks goes out to djsven for getting this idea started, then getting it done himself in Germany using the German distro from ASUS. I ended up having to extract the su binary he had as the three I tried from different downloads didn't work. Not sure where he got it but it's a winner!
gbkelley said:
Yes, folks after two days of trial and error I finally was able to build a system image file from the US OTA update that you install via fastboot. All I need to do now is find a free file upload site to host the file for you to download.
Install Instructions:
Download ME302C-US-Root.img.gz from (wherever)
Install the Minimal ADB-Fastboot into a folder (google this)
Install the ASUS USB Drivers (google this)
Place the image file in the folder
Run these fastboot commands:
fastboot devices (make sure your MemoPad is connected)
fastboot erase cache
fastboot erase system
fastboot flash system ME302C-US-Root.img.gz
Reboot from MemoPad recovery menu
Install from Market:
Root Checker (run it to confirm you have root)
SuperSU
Some app requiring root and run it - you should get a notification from SuperSU to grant su for app
You are now rooted
Note: this install follows the ASUS update script that links various binaries in /system/bin to 'toolbox' so you may want to replace that by installing BusyBox from the Market.
Enjoy your Rooted MemoPad!
I'll update this post when I have a download url for you.
Click to expand...
Click to collapse
Where can I find ME302C-US-Root.img.gz ???? Searches are finding nothing.
Turbojugend said:
Where can I find ME302C-US-Root.img.gz ???? Searches are finding nothing.
Click to expand...
Click to collapse
+1
Why not use Mega? Seems to always work and have great speed.
It is rooted...thank you.
Sent from my ME302C using Tapatalk 4
Turbojugend said:
Why not use Mega? Seems to always work and have great speed.
Click to expand...
Click to collapse
I tried RapidShare and it was crap. MediaFire was next on my list and that worked so I used it. May try Mega if there are problems with folks getting the file from MediaFire, we'll see...
Worked for me. Updated to 4.7.3 and is rooted.
Tried in Linux and could not get fastboot to recognize device.
Tried in Windows Server 2012 with this driver:
http://software.intel.com/en-us/articles/intel-usb-driver-for-android-devices
Ran setup file as Administrator with compatibility mode set to XP SP3. Required a restart before "fastboot devices" worked. If anyone can post a way to make fastboot work in Linux for this tablet, it would be appreciated.
-notten
notten said:
Worked for me. Updated to 4.7.3 and is rooted.
Tried in Linux and could not get fastboot to recognize device.
Tried in Windows Server 2012 with this driver:
http://software.intel.com/en-us/articles/intel-usb-driver-for-android-devices
Ran setup file as Administrator with compatibility mode set to XP SP3. Required a restart before "fastboot devices" worked. If anyone can post a way to make fastboot work in Linux for this tablet, it would be appreciated.
-notten
Click to expand...
Click to collapse
Try this:
http://forum.xda-developers.com/showthread.php?t=537508
or this...
http://bernaerts.dyndns.org/linux/74-ubuntu/245-ubuntu-precise-install-android-sdk
gbkelley said:
Try this:
http://forum.xda-developers.com/showthread.php?t=537508
or this...
http://bernaerts.dyndns.org/linux/74-ubuntu/245-ubuntu-precise-install-android-sdk
Click to expand...
Click to collapse
Hey, thanks, but neither of those has anything I haven't tried. I'm using the latest SDK and running fastboot as root so it's not the perms. I read on some Intel forum that someone else is having trouble getting it to work in Linux also.
Any luck with iptables? I don't think the kernel for this tablet comes with iptables enabled. I tried a few methods of getting it installed (DroidWall, iptables (beta) from marketplace). If I screw up the kernel on this, will flashing over it with the system image you upped revert it?
-notten
Thanks a lot for all of this gbkelley. Cheers!!
notten said:
. If I screw up the kernel on this, will flashing over it with the system image you upped revert it?
-notten
Click to expand...
Click to collapse
No my image is the /system folder only. Kernel is in boot.ini. The OTA update zip should fix it though as it has boot.ini
Xposed framework works great. Gravity box and app settings work great. Thanks for root.
Sent from my ME302C using Tapatalk 4
Links if you don't want to google it
Minimal ADB and Fastboot
How to install USB drivers
tdamocles said:
Xposed framework works great. Gravity box and app settings work great. Thanks for root.
Sent from my ME302C using Tapatalk 4
Click to expand...
Click to collapse
Hide battery work for you?
Got Root, Thanks so much.
gbkelley, this tablet has been out for a pretty long time, what do you think is the reason for the lack of ROM's and dev for it?
Turbojugend said:
gbkelley, this tablet has been out for a pretty long time, what do you think is the reason for the lack of ROM's and dev for it?
Click to expand...
Click to collapse
I would think that until a few days ago we didn't have a recovery image to which we could revert. I don't know precisely what's required to build a custom kernel for this tablet, but I'm guessing it's slightly more difficult since we don't know the exact kernel config. I don't think there are any source distributions of this kernel, and I somehow doubt we're lucky enough to have had ASUS build the kernel with CONFIG_IKCONFIG. Then there's probably custom patching that they've done to the code that they probably just won't release. But assuming we had a kernel config we can start building some nice ROMs or even updating the OS to kitkat, etc. As far as default apps/themes/whatever, I guess you could extract the recovery image, repackage it with your favorite APKs, themes, etc., and now you have a new ROM. I'll participate in ROM building for this tablet once we get a kernel config.
-notten
EDIT: Looks like kernel config was found a week ago by ze Germans: http://www.draisberghof.de/usb_mode...sid=c87b172460e22c6f0021f69c3bd5a601&start=15
Looks like it's time to start building custom ROMs for this tablet. I'll have to look into it sometime this week.
notten said:
I would think that until a few days ago we didn't have a recovery image to which we could revert. I don't know precisely what's required to build a custom kernel for this tablet, but I'm guessing it's slightly more difficult since we don't know the exact kernel config. I don't think there are any source distributions of this kernel, and I somehow doubt we're lucky enough to have had ASUS build the kernel with CONFIG_IKCONFIG. Then there's probably custom patching that they've done to the code that they probably just won't release. But assuming we had a kernel config we can start building some nice ROMs or even updating the OS to kitkat, etc. As far as default apps/themes/whatever, I guess you could extract the recovery image, repackage it with your favorite APKs, themes, etc., and now you have a new ROM. I'll participate in ROM building for this tablet once we get a kernel config.
-notten
EDIT: Looks like kernel config was found a week ago by ze Germans: http://www.draisberghof.de/usb_mode...sid=c87b172460e22c6f0021f69c3bd5a601&start=15
Looks like it's time to start building custom ROMs for this tablet. I'll have to look into it sometime this week.
Click to expand...
Click to collapse
Maybe I am getting my versions mixed up. Is this version of the tablet brand new, not the same that has been out for months? Mine is the ME302C version
Turbojugend said:
Maybe I am getting my versions mixed up. Is this version of the tablet brand new, not the same that has been out for months? Mine is the ME302C version
Click to expand...
Click to collapse
I believe you're right in saying that this tablet has been out for some time. I suppose there has been enough interest that things are now starting to take off. I mean, I bought it a couple weeks ago and I assumed I'd have to use the WW SKU root and try go beg ASUS for kernel configs. Seems like most of that has been taken care of in the last week. I'm actually really glad. It's a good time to be an ASUS MeMO Pad 10 FHD owner.
notten said:
I believe you're right in saying that this tablet has been out for some time. I suppose there has been enough interest that things are now starting to take off. I mean, I bought it a couple weeks ago and I assumed I'd have to use the WW SKU root and try go beg ASUS for kernel configs. Seems like most of that has been taken care of in the last week. I'm actually really glad. It's a good time to be an ASUS MeMO Pad 10 FHD owner.
Click to expand...
Click to collapse
Ok cool, I just don't want to be stuck with something that will have nothing going for it. I really like the tablet, but if it was going to be dead on XDA I would exchange it for the Sony Xperia Z Tablet. Both fit my needs for what I use it for.
Which one are you getting? Amazon Fire (7"), Fire HD 8 and Fire HD 10
5th Generation(2015) kindle fires
Just a list of Options, Hidden Features (from the Fire 7in thread)
Post what you have found, here.
Allow Apps from Unknown Sources
Settings>Security>tap toggle>Ok
Enable Developer Options
Settings>Device Options>Tap on Serial Numbers several times>You are now Developer
Enable USB Debugging
Setttings>Device Options>Developer Options>Enable ADB>tap on toggle>Enable
USB Drivers
see Fire thread
Fastboot Mode
Power Off>Hold Volume Down Up button (closest to power button)>Power On
Exit Fastboot Mode: Hold Power Button for ~20secs
Codename: ?
Code:
fastboot -i 0x1949 getvar product
product:
Google Play without root
Installing Google Framework/Playstore without Root by sd_shadow
Root (tried on my Fire 7in)
Failed: NewKingrootV4.52_C127_B227_xda_release_2015_09_28_105243.apk
Failed: KingRoot-4.1.0.249-release-nolog-201505211812_105241.apk
Im eyeing the 10.1inch... At 230 bucks it's a good price.. So thin.. So Sexy...
Sent from my HTC6600LVW using Tapatalk
Preordered the 888: KF HD 8, 8", 8Gb
Thanks for the referral from the Fire General thread, sd-shadow! I also have the HD 8 w/ 8gb.
Changed title to: Got mine/ Tips and Tricks thread
Installing Play services
I just want to say that the method that was pointed out in the Fire forum didn't work on mine( FIre HD 8 8gb). I had to install the google services framework as well and also didn't have to do any of the adb stuff either. Everything appears to be working as of right now. I managed to get Clash of Clans working.
bharadwajm07 said:
I just want to say that the method that was pointed out in the Fire forum didn't work on mine( FIre HD 8 8gb). I had to install the google services framework as well and also didn't have to do any of the adb stuff either. Everything appears to be working as of right now. I managed to get Clash of Clans working.
Click to expand...
Click to collapse
think you only need adb command if you want to use goggle settings app
Sent from my KFFOWI using Tapatalk
sd_shadow said:
think you only need adb command if you want to use goggle settings app
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
Ok got it. Btw any chance you got writing to ext SD working on yours? I still havent been able to get it to work.
bharadwajm07 said:
Ok got it. Btw any chance you got writing to ext SD working on yours? I still havent been able to get it to work.
Click to expand...
Click to collapse
I think we need root.
Sent from my KFFOWI using Tapatalk
So, I understand correctly that the root methods for previous Fire Tablets do not work for the Fire HD 10 (5th generation)?
revengineer said:
So, I understand correctly that the root methods for previous Fire Tablets do not work for the Fire HD 10 (5th generation)?
Click to expand...
Click to collapse
As of yet, no one has posted root success, for any of the 5th Gen tablets.
Sent from my KFFOWI using Tapatalk
Thank you for the confirmation. I know it's still early, just wanted to make sure I did not miss anything.
Hey, I got ADB working after some difficulties, but the one click batch installer for all the Google services doesn't work-- it complains that the APKs are incompatible. This is on a Fire HD 8 btw. Which are the correct ones to use?
MrTroika said:
Hey, I got ADB working after some difficulties, but the one click batch installer for all the Google services doesn't work-- it complains that the APKs are incompatible. This is on a Fire HD 8 btw. Which are the correct ones to use?
Click to expand...
Click to collapse
I'm surprised the batch didn't work.
had you tried installing apps before using the batch file?
Sent from my KFFOWI using Tapatalk
I got it working eventually-- just needed to go find the right versions of the various APKs.
MrTroika said:
I got it working eventually-- just needed to go find the right versions of the various APKs.
Click to expand...
Click to collapse
Great, could you post the right versions? Thanks
Looking for Testers for a Possible Root method
Using the same method of creating a Boot.img that makes the /system rw for the 2015 7 in Fire.
@csolanol and @diegocr have created a batch file, with a modified boot.img for the HD 8/10.
There is some risk that this method will not work, Amazon may have done something different in the 8 and 10 models.
If the boot.img does not work, the tester may have to re install the firmware via adb sideload, or this could brick the device, although that is unlikely.
just post here, if you are willing to test, the batch file is already uploaded to dropbox.
Sd card access fixed
my kindle auto updated to 5.1.1 and amazon seems to have fixed writing to SD card. The update also doesn't break play installation as far as i can tell.
Just got the Play store and Google Services installed using the method for the 7 inch 2015 model. Haven't have any luck with disabling lock screen ads. I presume this is because my HD 8 is running 5.1.1.
On another note I found the product codename for the HD8. THEBES
Also messed around with the recovery a bit. Everything seems to be the same as the 7 inch as well.
Edit: I should also mention that unlike the 7inch fastboot mode does not display anything on the screen. The only indication is when Fastboot is displayed after the "adb devices" is executed.
I received a 10 for Christmas (thanks missus).
At first I couldn't read my fishing magazine on it but then I found this thread.
I didn't try the batch file but installed the APKs one by one from an SD card via ES file manager.
Everything is now good, I have Google play and can install what I want.
I plugged in an old HSUPA USB Stick (1&1) and it was recognised!
Just need to find out how to get it to work.
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