EDIT: solution here
Hi all,
My HTC OX+ died, and I bought a Motorola Moto G (Falcon) to see me through to the end of my contract. Aside from the price, the big draw was CM support.
I've unlocked by bootloader and installed TWRP without trouble (when I was screwing with my HOX+, I read that CWM doesn't support sideloading. Since - correct me if I'm wrong - the 'cleanest' way to install a ROM is to format the SDcard completely, then install the ROM, sideloading support is vital).
I've tested and confirmed root access (initially, I thought not having the SU binary installed was an issue, although I did have TWRP installed fine). However, I'm stuck with adb - in recovery, adb does not recognise what I do. I've tried installing, uninstalling and reinstalling drivers from various sources (first the ones offered my Motorola during the unlocking process, then the ones from Windows Update, and last but not least ones from here: http://d-h.st/5j0 - following advice of a thread I found on here). I've tried doing this both automatically and manually using Device Manager.
Usually, precisely because of these problems, I hate using Windoze for this kind of thing. However, I don't have a Linux distro open to me atm - other than in VirtualBox, in which case adb still doesn't pick up the phone (presumably because its reliant on the host Windows drivers). I'm tearing my hair out trying to get it fixed.
Not that they can be conclusively relied upon, but as confirmation it is a drivers issue (despite Device Manager finding no problem), when the phone is connected in recovery (TWRP), Windows plays an odd sound - three tones instead of the usual two.
Any help would be appreciated. My Windows is Windows 7 Ultimate x64. Also, I've no problems at all when the stock OS is booted - or at least 'adb devices' detects the device and displays it correctly.
Thanks!
CWM does work with sideloading (that's the way i installed CM the first time ) [make sure to use the one linked in CM11 thread!]
if i understand correctly:
fastboot works fine (since you could unlock the BL)
adb works when the device is booted
adb fails when in recovery
make sure you are using the latest adb :
Code:
[email protected] ~ $ adb version
Android Debug Bridge version 1.0.31
if your version is lower than 1.0.31, then update it (in that case your adb is outdated regarding the 4.4 bootloader) ==> update your Android SDK manager or your adb binary
matmutant said:
CWM does work with sideloading (that's the way i installed CM the first time ) [make sure to use the one linked in CM11 thread!]
if i understand correctly:
fastboot works fine (since you could unlock the BL)
adb works when the device is booted
adb fails when in recovery
make sure you are using the latest adb :
Code:
[email protected] ~ $ adb version
Android Debug Bridge version 1.0.31
if your version is lower than 1.0.31, then update it (in that case your adb is outdated regarding the 4.4 bootloader) ==> update your Android SDK manager or your adb binary
Click to expand...
Click to collapse
Do you think CWM is preferred to TWRP? If sideloading is supported, it's not like you spend much time in recovery anyway, so if you think it'll help, flashing CWM is definitely something I can do...
AFAIK...
- have only used fastboot briefly to install recovery, but this went without a hitch.
- ADB does indeed work when the stock OS is booted
- As above. Fails in recovery, I suspect because of a driver issue (weird Windows sound when connected, no Autoplay popup etc). You can kind of understand this...writing a driver for the device in recovery is hardly a key issue for the devs (though I confess, why it can interact with the same hardware with one set of programs loaded (i.e. stock OS) and not another (i.e. TWRP) I've no idea)
Just issued the command, and (as expected since I downloaded the bundle only yesterday from Google) I am running 1.0.31.
ArminasAnarchy said:
Do you think CWM is preferred to TWRP? If sideloading is supported, it's not like you spend much time in recovery anyway, so if you think it'll help, flashing CWM is definitely something I can do...
AFAIK...
- have only used fastboot briefly to install recovery, but this went without a hitch.
- ADB does indeed work when the stock OS is booted
- As above. Fails in recovery, I suspect because of a driver issue (weird Windows sound when connected, no Autoplay popup etc). You can kind of understand this...writing a driver for the device in recovery is hardly a key issue for the devs (though I confess, why it can interact with the same hardware with one set of programs loaded (i.e. stock OS) and not another (i.e. TWRP) I've no idea)
Just issued the command, and (as expected since I downloaded the bundle only yesterday from Google) I am running 1.0.31.
Click to expand...
Click to collapse
In fact i never tried TWRP : i have always been happy with CWM so i didn't feel the need to change (so you can give a try but i don't think it would change anything)
Try to run ADB as administrator it may help (i think you can open cmd as admin with windows but don't remember how :-\)
I don't know how USB drivers work : there's a long time i didn't use Windows
matmutant said:
In fact i never tried TWRP : i have always been happy with CWM so i didn't feel the need to change (so you can give a try but i don't think it would change anything)
Try to run ADB as administrator it may help (i think you can open cmd as admin with windows but don't remember how :-\)
I don't know how USB drivers work : there's a long time i didn't use Windows
Click to expand...
Click to collapse
I think I can figure this out - I'll double check it was running as admin, and try flashing CWM.
As with flashing ROMs, do I need to wipe anything first? Or can I just use the same command I used for flashing TWRP in the firs place?
If it's still not working, (re) installing Linux seems an idea to try (I assume you're not on OSX?). What distro do you use and/or do you know others have had no problems with? (Usually if I was installing Linux, I'd take Ubuntu's minimal iso and stick as little as possible on top of it - since the drivers are likely to be something cut out of that though, installing a 'normal'/'full' .iso seems sensible)
Cheers for your help, man
ArminasAnarchy said:
I think I can figure this out - I'll double check it was running as admin, and try flashing CWM.
As with flashing ROMs, do I need to wipe anything first? Or can I just use the same command I used for flashing TWRP in the firs place?
If it's still not working, (re) installing Linux seems an idea to try (I assume you're not on OSX?). What distro do you use and/or do you know others have had no problems with? (Usually if I was installing Linux, I'd take Ubuntu's minimal iso and stick as little as possible on top of it - since the drivers are likely to be something cut out of that though, installing a 'normal'/'full' .iso seems sensible)
Cheers for your help, man
Click to expand...
Click to collapse
The latest TWRP has in its wipe menu a setting to wipe to install a new rom I use this and with the Gapps & rom Zips on the phone choose install from sd card.
You only need fastboot to flash recovery or stock roms.
Adb is not needed at all but can still be used if you prefer!
ArminasAnarchy said:
I think I can figure this out - I'll double check it was running as admin, and try flashing CWM.
As with flashing ROMs, do I need to wipe anything first? Or can I just use the same command I used for flashing TWRP in the firs place?
If it's still not working, (re) installing Linux seems an idea to try (I assume you're not on OSX?). What distro do you use and/or do you know others have had no problems with? (Usually if I was installing Linux, I'd take Ubuntu's minimal iso and stick as little as possible on top of it - since the drivers are likely to be something cut out of that though, installing a 'normal'/'full' .iso seems sensible)
Cheers for your help, man
Click to expand...
Click to collapse
To install CWM :same as for TWRP, no wipe required
________
Linux :
I'm using Mint (Cinnamon and Xfce) since a while [ubuntu based distro] and Manjaro since a few days [Arch based]
If you want yo install linux without touching your HDD you can do the following :
Burn an iso (Xubuntu could be nice)
Take a blank 16GB USB key and unplug your HDD to void issues
Boot on live CD
Install linux to that USB device
And now each time you want linux : just force boot your computer to USB (no grub / no modifications on HDD)
To use ADB you'll need the Android SDK Manager (to stay up-to-date) and set up your udev rules following this
matmutant said:
To install CWM :same as for TWRP, no wipe required
________
Linux :
I'm using Mint (Cinnamon and Xfce) since a while [ubuntu based distro] and Manjaro since a few days [Arch based]
If you want yo install linux without touching your HDD you can do the following :
Burn an iso (Xubuntu could be nice)
Take a blank 16GB USB key and unplug your HDD to void issues
Boot on live CD
Install linux to that USB device
And now each time you want linux : just force boot your computer to USB (no grub / no modifications on HDD)
To use ADB you'll need the Android SDK Manager (to stay up-to-date) and set up your udev rules following this
Click to expand...
Click to collapse
Is the android-tools-abd and android-tools-fastboot package in the Ubuntu repos not maintained to be the latest? I've no idea about Arch package names, but again, it'd surprise me if they didn't maintain their repo with the latest package (especially since they pride themselves on being on the bleeding edge).
ArminasAnarchy said:
Is the android-tools-abd and android-tools-fastboot package in the Ubuntu repos not maintained to be the latest? I've no idea about Arch package names, but again, it'd surprise me if they didn't maintain their repo with the latest package (especially since they pride themselves on being on the bleeding edge).
Click to expand...
Click to collapse
It is up-to-date on arch/Manjaro (I don't remember the package name either)
On Ubuntu it wasn't when I needed (February), so I installed SDK package :-/
matmutant said:
It is up-to-date on arch/Manjaro (I don't remember the package name either)
On Ubuntu it wasn't when I needed (February), so I installed SDK package :-/
Click to expand...
Click to collapse
Right, well...we'll see how it goes. It might be the repo package does the job.
I've installed CWM and can conclusively confirm I prefer TWRP (the interface is hardly touch-friendly and even though I'm using the touch build, it's easier to use the volume rocker in case of accidental presses) but little else. Windows seems completely ****ed up - when CWM is booted, it plays the disconnect sound, when the cable is unplugged and plugged back in it goes back to playing the 'unknown' tone. Currently torrenting Xubuntu - going to see if a live install has any more luck.
Full solution
matmutant said:
It is up-to-date on arch/Manjaro (I don't remember the package name either)
On Ubuntu it wasn't when I needed (February), so I installed SDK package :-/
Click to expand...
Click to collapse
Right, I'm running TWRP with CM11. There are a couple of issues bothering me, but that's another thread...
Solution:
- From stock, booted into recovery, then replaced TWRP with CWM. Rebooted into CWM.
- Tested sideload from CWM. Still non-functional. Made sure cmd.exe was running with administator privileges, still no difference. Time for _buntu!
- Installed Xubuntu. Connected to wifi, downloaded
Code:
android-tools-adb
and
Code:
android-tools-fastboot
. Plugged in phone. Checked
Code:
adb version
(it is the latest, 14.04 was released in April after you checked in Feb, and the new release must have updated the package...seems strange no one backported it though).
- Sideloaded and did a dirty flash of CM11 (didn't want to wipe without first confirming I could flash and everything was functional). Issues (as expected) such as slow loading but able to boot up.
- Decide it's time to push my luck and flash TWRP - this goes without a hitch.
- Test sideload. Still working, so perform full wipe and factory reset. Then sideload CM11 + GApps.
- Reboot into CM11. Still some issues so flashed the CM11 kernel using fastboot (not sure if TWRP does this automatically, but since the boot up improved a bit, I'd guess not).
- Now have a fully functional phone, albeit some of the changes from CM10.x to CM11 have disorientated me a bit...
Thanks for your help man. As with a lot of things this turned out to be a dopey Windoze issue than a problem with the phone or adb etc!
TWRP
TWRP has sideload ability.
Boot into recovery and got to the "Advanced" button then the "ADB Sideload" button is at the bottom. I am on TWRP v2.7.0.0 and I used it the other day so I know for sure it works.
ArminasAnarchy said:
Right, I'm running TWRP with CM11. There are a couple of issues bothering me, but that's another thread...
Solution:
- From stock, booted into recovery, then replaced TWRP with CWM. Rebooted into CWM.
- Tested sideload from CWM. Still non-functional. Made sure cmd.exe was running with administator privileges, still no difference. Time for _buntu!
- Installed Xubuntu. Connected to wifi, downloaded
Code:
android-tools-adb
and
Code:
android-tools-fastboot
. Plugged in phone. Checked
Code:
adb version
(it is the latest, 14.04 was released in April after you checked in Feb, and the new release must have updated the package...seems strange no one backported it though).
- Sideloaded and did a dirty flash of CM11 (didn't want to wipe without first confirming I could flash and everything was functional). Issues (as expected) such as slow loading but able to boot up.
- Decide it's time to push my luck and flash TWRP - this goes without a hitch.
- Test sideload. Still working, so perform full wipe and factory reset. Then sideload CM11 + GApps.
- Reboot into CM11. Still some issues so flashed the CM11 kernel using fastboot (not sure if TWRP does this automatically, but since the boot up improved a bit, I'd guess not).
- Now have a fully functional phone, albeit some of the changes from CM10.x to CM11 have disorientated me a bit...
Thanks for your help man. As with a lot of things this turned out to be a dopey Windoze issue than a problem with the phone or adb etc!
Click to expand...
Click to collapse
I'm happy it worked fine finally !
And thank you for providing the way you did it, that could help some other people having similar issue.
highspeedfelon said:
TWRP has sideload ability.
Boot into recovery and got to the "Advanced" button then the "ADB Sideload" button is at the bottom. I am on TWRP v2.7.0.0 and I used it the other day so I know for sure it works.
Click to expand...
Click to collapse
I think you mis-read somewhere. I know TWRP has sideload, I used it on my HOX+. It was CWM I was unsure of...
matmutant said:
I'm happy it worked fine finally !
And thank you for providing the way you did it, that could help some other people having similar issue.
Click to expand...
Click to collapse
That was the idea, yeah .
I love the way the moral of the story is "Don't expect Windows to do the job properly. EVER. (Or at least not without several hours of screwing with it first)."
ArminasAnarchy said:
I love the way the moral of the story is "Don't expect Windows to do the job properly. EVER. (Or at least not without several hours of screwing with it first)."
Click to expand...
Click to collapse
And during that time i succeeded to break both my Mint and Manjaro installs (user-related fails) and bring them back to life XD
Related
Here I am again...
This time I have written a shell script (linux only) and made a live-cd (for all windows/linux users) to automatically root the stock firmware on the TF101. Every stock firmware.
Today in Europe Asus rolled out the 3.2 upgrade. If you are on stock and you have alredy upgraded then download attached tar file and do as follows:
NOTE: Unfortunately, this script won't work with the latest revision of TF101 (3G version, B80 and some B70)
NOTE2: As someone pointed out (thank you Pieter) you need to be root on your linux box in order to make it work.
Code:
tar -xvf universal.tar
cd universal
./universal.sh
In Ubuntu the last command would be:
Code:
sudo ./universal.sh
Follow the instructions and you're done.
If you have a stock US/DE/TW/JP/TB firmware you can do the same.
If you are running an older version of Honeycomb the process is the same.
When ASUS will pull out another upgrade... same commands as above.
So this probably is the closest thing to one-click-root for the Transformer.
This won't install custom rom/CWM/strange other things (V2 version added the support for CWM); it's only root.
I've tested this morning after the 3.2 upgrade and it worked like a charm.
However this is in testing stage so, as always, if you brick/ruin/burn/crash something don't blame on me.
This package includes the Bootunpack tool, courtesy of Rayman84
LIVE CD INSTRUCTIONS
It's based on slitaz (http://www.slitaz.org/).
Burn the image into a cd or if you want it on a thumb usb drive follow this (http://doc.slitaz.org/en:guides:liveusb).
Put the cd/usb in your pc and reboot.
Follow the indication on screen (for setting locale and keymap).
When the desktop shows up, double click on "Universal Root for ASUS TF101".
Again follow the indication and you'll be ok.
For a guide on how to boot from cd/usb try this: http://www.passwordunlocker.com/knowledge/change-bios-settings.html
or search with google.
The option to install a stock boot/recovery (added on V3) is working even if not fully tested.
The program has correctly rebuilt a stock recovery on my WW version.
From version V4 root checker correctly says that the rom is not rooted after you do an unroot.
If you like the work i did take a look at that funny button under my name with the "donate to me" caption
Seriously, I appreciate even only a "Thanks".
FAQ
[Q] I'm running on Windows, how can I burn the live-cd?
[A] Try with cdburnerxp (it's the easiest way).
You can download one installer frome here:
http://cdburnerxp.se/en/download
or the portable package if you don't want to install other software:
http://download.cdburnerxp.se/portable/CDBurnerXP-4.3.8.2568.zip
Start the program (for the portable version the file is cdbxpp.exe) and click on "Burn iso image". Then select the .iso file you have downloaded and click "burn disk". All Done.
[Q] How can I reboot in APX/recovery mode?
[A] Do as follows:
VOL UP + POWER BUTTON for ~5sec = boot in APX mode. The screen will stay black as if it is turned off. This mode is used only when you use nvflash to flash boot/recovery/data partition (this is the first step in my script).
VOL DOWN + POWER BUTTON ~5sec = will appear a screen where it says to press vol down again to wipe all data (obviously you don't want to do it now), or press up to enter RCK (recovery mode). If you installed CWM you will see the main menu navigable with vol up / vol down / power button.
If you have the stock recovery you will see a green android with a esclamation mark on a yellow triangle.
[Q] Help! I can't reboot in recovery mode!
[A] I think the main problem here is that it is a bit tricky to get into CWM recovery, once you see the small text come up don't try to read anything, just hit volume up.
Hold volume down plus power until the text in upper left shows,if you let go too early it just boots up and you never see the text. If you wait too long you don't get the option to boot into recovery. Hope that helps..
Thx to ckuke4 for this answer http://forum.xda-developers.com/showpost.php?p=16306342&postcount=60
[Q] The live-cd gave me this error: "connection failed NvError 0x8" what is it?
[A] This means that either you are not in APX mode (read above), or that you have one of the latest revision of the tf101 (B7O) which have an unknown (for now) sbk.
For what i know, there's no knew method for rooting your device.
Maybe someone will find a way, but for now you have to be patient.
[Q] I'm running your scripts from my linux box, but it keep me saying "Permission Denied". Why?
[A] You need the root privileges on your local machine.
If you are running Ubuntu:
Code:
sudo ./universal.sh
[I](it will asks for your password)[/I]
If you are running another linux distro:
Code:
su
[I](it will asks for your password)[/I]
./universal.sh
[Q] I have rooted my tablet with this method, but I can't find the superuser app and Titanium Backup says that I am not rooted.
[A] The root script will asks you to reboot your tablet, make sure that usb debugging is turned on and then press any key.
You have to wait until you see a little bee on the bottom right of your tablet's screen, near the clock. Then press any key.
[Q] I've installed CWM but every time i try to do a backup, it says it can't find sdcard. But my microsd card work fine with root explorer!
[A] Don't get me wrong but, are you sure?
In root explorer you see a sdcard folder but it's not your microsd, it's the internal memory (it's weird, i know). In root explorer the microsd card is mounted under the "/removable/microsd" folder. You should also see a little sd card icon in the bottom right, near the clock.
Also you need to make sure the card is formatted correctly. Try reformat it with this: https://www.sdcard.org/consumers/formatter_3/
Thanks to skeeterpro for the link (http://forum.xda-developers.com/showpost.php?p=16385872&postcount=6)
[Q] The live cd stops at the command prompt, I can't see the desktop.
[A]The live cd doesn't include every driver for every video card, mouse, keyboard, etc.. (keep in mind that the original slitaz livecd is only 30MB).
You can do all the process in the text console, it's not much more difficult.
If it asks for a login insert "tux" (without quotes).
At the command line enter the following:
Code:
cd
cd universal
./universal.sh
Then the magic will start. The unroot script is called ./unroot.sh
CHANGELOG:
V4:
- Corrected some text
- Added a link on the Desktop to this thread
- Added stock ramdisk for all SKU (though JP, CN and DE are not the latest versions) (thanks to kovla for the latest TB recovery)
- Added a script on the Desktop to increase the font size on the fly for those who are using a very high dpi monitor/tv.
- Changed compression algoritm. Now the iso is ~10MB smaller.
- Maybe I have found the way to make everyone read the faq...
V3:
- [BETA] added a second script to come back to stock.
V2:
- added the option to install CWM (thanks Roach!)
- more error check
V1:
First version
=====> DOWNLOAD LIVE-CD V4 - (Mirror)<=====
DOWNLOAD LIVE-CD V3 (previous version)
DOWNLOAD LIVE-CD V2
As always, keep your eyes open and
Have Fun!
Hey, how about an equivalent windows script for those who prefer msft's os. Ok?
awesome -one root to rule them all!
ondoy1943 said:
Hey, how about an equivalent windows script for those who prefer msft's os. Ok?
Click to expand...
Click to collapse
In linux there's no need for drivers to work with tf101.
Windows seems to be problematic with driver (for someone seems to be way too difficult install the right ones).
As i stated above, adding this to a live linux cd will be the final one-click-root (put a live cd/usb-memory on your computer, reboot, follow the easy instructions and you're rooted).
Sincerely I don't know how to modify a livecd to add these scripts and programs.
If anyone wants to try, he is welcome.
Anyway I don't plan to do a windows port of this.
Disappointed! No windows support!
Will probably be trying this method from my PCLOS partition, if I can hold off the OTA update which has just begun pestering me.
Got to find out whether the modded adhoc wpa_supplicant works with 3.2 first, thanks for the effort HF
Excellent, glad to avoid having to dig out my old Windows box to root the TF Would advise people to drop it, new Mint/Ubuntu is much nicer visually than Win7 and my startup times are fantastic, not to mention the slick media support.
Does you script give also install CWM?
Will give this a go later and see how it works.
belrik said:
Excellent, glad to avoid having to dig out my old Windows box to root the TF Would advise people to drop it, new Mint/Ubuntu is much nicer visually than Win7 and my startup times are fantastic, not to mention the slick media support.
Does you script give also install CWM?
Will give this a go later and see how it works.
Click to expand...
Click to collapse
I was thinking on it, but perhaps it's better no.
Installing cwm means no more ota, since the update relies on the stock recovery.
This script was meant to leave all as stock as possible.
For all the windows folks:
I have added to the first post a live-cd with all the necessary tools.
Just run it and you'll be fine. (anyway, you are always in time to switch to linux)
Hallo and thanks!!!
what about mac's Users?
Can you explain a bit about what it does? So we can all learn.
Thank you,
Hi !
Will it work under wmware or virtual pc ?
Sorry if this is a dumb questions, but would this work in Terminal in OS X?
RayYung said:
Can you explain a bit about what it does? So we can all learn.
Thank you,
Click to expand...
Click to collapse
So you wanna learn? Good!
First i learned how to root the stock firmware from here: http://forum.xda-developers.com/showthread.php?t=1125714 .
Essentially the steps are:
1 - download a modified boot image into the tablet
2 - install the su and superuser packages.
My scripts do these 2 steps. I wrote a small howto that explains how to modify a boot image (http://forum.xda-developers.com/showthread.php?t=1193737)
Caramel said:
Hi !
Will it work under wmware or virtual pc ?
Click to expand...
Click to collapse
scirio said:
Sorry if this is a dumb questions, but would this work in Terminal in OS X?
Click to expand...
Click to collapse
I really would like to have an answer to these questions...
The Mac should have a layer of compatibility with linux (can't tell you more), but i really don't know the mac world.
*Maybe* the live cd will work under virtual machine; there should be some options to enable the usb feature. In Virtual Box there's an option to enable the usb controller and an option to filter what device will be accessible to the guest os; don't know vmware and virtual pc.
I don't know if an Intel based Macintosh is able to boot from a x86 live-cd, you could try.
I'm sorry i can't help you much more.
scirio said:
Sorry if this is a dumb questions, but would this work in Terminal in OS X?
Click to expand...
Click to collapse
Oops- no- there is no Nvflash for Mac. Sorry.
Created a live usb, booted via windows, and voila i am looking at a linux desktop, which i have not seen for a long time. Started going to its paces to root my tf, but did not push thru to the end, in as much as my tf is already rooted beforehand. But i can sense that barring any unforeseen miscues by the |op|, this almost one-click rooting procedure should produce its desired result. Highly recommended; good job |op|.
Looks like this calls for an "unrooting" routine to complement the rooting process. How about it?
Nice script! I just completed one of my own for unrooting the TF
One thing: why not just use adb reboot recovery instead of telling them how to do it manually?
brando56894 said:
Nice script! I just completed one of my own for unrooting the TF
One thing: why not just use adb reboot recovery instead of telling them how to do it manually?
Click to expand...
Click to collapse
I have already tried this, but seems it doesn't work.
if i write "adb reboot recovery" or "adb reboot bootloader" my tablet reboot in normal mode.
It's more reliable do it manually.
how can install ClockworkMod recovery
i rooted my transformer with your one click tool from live cd.
if i want install ClockworkMod recovery how can do ?
zulu99 said:
i rooted my transformer with your one click tool from live cd.
if i want install ClockworkMod recovery how can do ?
Click to expand...
Click to collapse
For now if you are running on windows, you can use one of these methods:
http://forum.xda-developers.com/showthread.php?t=1125714
http://forum.xda-developers.com/showthread.php?t=1185104
you are already rooted, so just need the cwm.
Since i had many requests on adding cwm, i am going to update the scripts and live-cd for adding this feature.
I'll keep you updated.
hi! my apologies but i searched and read alot of post already on how to solve this.
i flashed Roach latest CMW how ever being so stupid i forgot to put a ROM on internal memory. did full wipe already and i have no ROM to flash as it reads internal memory only.
ive read alot of post regarding the concern, i want to try to push a ROM on internal drive using ADB but when i run "adb devices" nothing is found.
any suggestions or any links to posts that i might get help or tutorial. im not an expert on using ADB so keep instructions simple, im a noob i admit it but i just need help. thanks!
read through posts "[Troubleshooting/Solved] ClockworkMod recovery 5.5.0.4 from Koush" "Used roach's new CWM recovery, now can't intall rom" "
im on recovery and when i run adb devices it just blank. any walk through is much appreciated!
Do yo have USB debugging on?
I dont know because i was about to flash a new rom so i did a full wipe already
Did you ever get ADB working before all this? USB debugging usually have to be turn on by the user. In Settings>Developer options.
i havent with my tablet but with my htc desire hd i used adb. and when ever i flash a ROM on my tf i usually turn on usb debugging always. right now in on recovery roach r2. my ROM is on my external memory. also tried to do a nvflash how ever whenever i run the download.bat cmd opens then closes 3 secs maybe
i also got a new sdk from this forum " [GUIDE] Getting ADB Setup; An Idiots' proof guide on getting ADB working for Rooting!" as ave said above when i type "adb devices" its just blank and does not list any device.
I had exactly the same problem - I'm not sure about tablet version that I own, but I've flashed Wipe Lite and new Recovery. I also have HTC phone that I've been using on the same PC .
I've spent an hour trying to get my TF back on feet and I managed it.
I would recommend uninstalling all HTC and ASUS software and drivers, rebooting PC and installing just ASUS PC Suite. It worked in my case - suddenly Device ID showed up for a few seconds before ADB reported "no device" again.
So I've pushed Rogue XM Recovery to data/media:
adb push roguexm data/media
Of course use name of zip file instead "roguexm" in command above.
After that zip file showed up on sdcard and I could flash it - it doesn't support AROMA but it works quite fine otherwise.
Hope it'll work in your case. Good luck!
Hope it will help
I once were in your case, did full wipe and forgot to put a Rom in internal memory. But in my case I just rebooted the transformer and all of a supprise, my tablet reverted to the stock Rom! I dont know how this happend but may be Asus did something to keep stock Rom persistent whatever you have flashed roms or CWMs.
So i hope this also happened in your case, just give it a try. Good luck!
If he did "Full Wipe - factory reset" then he should be able to boot HC/ICS and from that copy files onto internal /sdcard.
But if he used Android Revolution Super Wipe script either Lite or Full then he has nothing to boot into, no system at all - I've done that Only thing that left was recovery without external sdcard support, so I had nothing to install...
ASUS and HTC drivers have some issues and make everything harder than it should be, that's why I recommend to uninstall all HTC and ASUS software, rebooting PC and installing ASUS PC Suite only, to have "clean" drivers on PC.
I've tried different drivers and none of them worked, until I've done that.
Ok, I'll try to write it simple, I'm not sure if I can post links so just in case I'll give thread names. If it will be too simple don't get mad - ok?
1. Uninstall ASUS and HTC software, reinstall ASUS software like mentioned above.
2. Create folder on your C: drive called CWM
3. Go to post "Eee Pad Transformer Android Development\[Recovery] Rogue XM Recovery v1.3.0 (CWM-based Recovery v5.0.2.7" thread - http://forum.xda-developers.com/showthread.php?t=1446019
and "save as..." cwm_recovery-5027_rogue_rburrow-tf101-r1.zip to C:\CWM
4. Highlight/select command below:
adb push cwm_recovery-5027_rogue_rburrow-tf101-r1.zip data/media
then right click on it and select "copy" - it will save you typing it later.
5. Boot Recovery on your Transformer and connect it to PC, let system install device drivers
6. Click START, "Run...", type: cmd
7. It should show you path to your profile folder - C:\Users\yourname>
8. Type: cd /CWM
it will change folder to C:\CWM>
9. type: adb devices
(it should give you your device ID, if it still will give "no device id" then there I can't help you - I'm sorry)
10. right click on black background and select "paste" (you'll see command that you've copied from number 4), then press enter
11. It should copy recovery onto your internal sdcard - you will be able to select it from tablet
12. type adb kill-server and disconnect tablet, install new recovery and from that one you will be able to select external or internal sdcard
Notes:
I don't know why but I was able to send only small file from CWM-adb connection, it kept disconnecting quite quickly that is why I recommend sending Rogue XM Recovery instead of whole new ROM.
Other thing - it may depend on what windows system you have - I'm on Win 7 x64 (don't remember how it worked on other versions) and I can paste onto cmd (black) window without problems from right click menu. If you won't be able to paste there or you'll get some rubbish, try to right click on top bar and select "Edit" and then "Paste".
Ok, that's all. Hope it will work.
thanks for all inputs. i did a full wipe but not as scripts. i wiped manually. i did try to reboot but stuck as eepad screen. will try to re-install asus drivers and uninstall htc ones. hopefully i get it done today. i will update later...
still no luck. device not found. im going to try to install new sdk... i hope it works. ive already removed htc sync and drivers. also re-installed asus sync and updated drivers. on device manager detects on other devices transformer but drivers are not installed.
yahoo! got it working now. i had to enable adb usb Drivers for Nvidia Tegra based Android Tablets and re-install SDK download android usb and learn What Is ADB And How To Install It With Android SDK.
finally got my tablet working again and my first thing to do is have a copy of a ROM and CWM in both storages!
thanks alot for the input and for helping!
thanks Kraliz
monespeso said:
yahoo! got it working now. i had to enable adb usb Drivers for Nvidia Tegra based Android Tablets and re-install SDK download android usb and learn What Is ADB And How To Install It With Android SDK.
finally got my tablet working again and my first thing to do is have a copy of a ROM and CWM in both storages!
thanks alot for the input and for helping!
thanks Kraliz
Click to expand...
Click to collapse
Could you tell me how to do that? Because I have the exact same problem.
Hi all,
I had a nice, long, detailed post typed out but then my browser at work crashed, so here is the revised edition:
I recently (three days ago) bought a TF300T tablet. Absolutely love it. As any android fan does, I immediately wanted to root it to get the full benefit of the device. I followed the step-by-step guide on the cyanogenmod wiki and have been successful (after a few hours of figuring things out) in unlocking the device. I am aware at this point that my device is unlocked and my Asus warranty is voided. I am also aware I may have to follow different steps to root it, and am willing to do so accordingly.
I'm not set on using cyanogenmod, but that seems to be the most popular and well-known one so I'd like to use one that is established.
So, up until now I have followed that guide but I am having an issue with flashboot. When I go to do the 'fastboot devices' command, I get nothing. It just jumps to the next line, as if I sent a blank command. When I type 'adb devices' it works fine and shows some letters&numbers so I know my device is recognized.
With all that being said, can anyone advise me on which step I'm doing wrong, if any?
Also, I'm -really- cautious about potentially bricking this thing. I still have 30 days at Best Buy but I'm also an employee there and my co-workers know I'm trying to root so if I brick it, it may not be as easy to return it as with a normal customer. I also have the Accidental Damage & Handling plan so if I DO brick it, I can smash it and get a new one without too much incident, if it comes down to it (which obviously is a LAST resort)
My device is as following:
Asus Transformer Pad TF300T unlocked, firmware .29.
I' have about 15 tabs open in Google Chrome right now after SEARCHing the forums, specifically the TF300 forum, and I'm filtering through all the posts right now. If I find a solution I will post asking for this thread to be deleted.
I'm very tech-savvy, but completely new to android. I don't own a smartphone, and this is my first android device, so this is an incredible learning experience. If anyone feels so kind, could you please explain the different terminiologies used in the rooting scene? I hear stuff about blobs, .build files, DE, WW, US stuff. What's what? And what does it all mean?
Thanks so much, and here's to hoping my computer doesn't crash as soon as I press "post"!!
-Opethfan89
*edit* Forgot to add that when I use the command
fastboot flash recovery recovery-clockwork-5.5.0.4-tf300t.img
Click to expand...
Click to collapse
the command prompt just stays stuck on "waiting for device", while my device is stuck on "Starting fastboot USB download protocol"
Slight resolution
So I am just posting with a slight update to what I've been trying to get this working. I uninstalled the ADK, all drivers, and started over from scratch. I installed ADB using the method listed on the CyanogenMod wiki, and it works fine (I can use all ADB commands from command prompt and it lists my device when I use the 'adb devices' command.
So I'm continuing to follow the steps on the CyanogenMod wiki page and I get back to the part about Fastboot. I boot into fastboot mode, plug the device in, and the new development is that my computer DOES recognize fastboot only in device manager. I do have a yellow exclamation mark near it meaning I don't have the proper driver installed.
So now my newest question is, how do I install the driver for -just- fastboot, or where can I find the .inf file so I'm able to install it myself?
I'm SO close to rooting this device I can just taste it!! Any device is very much appreciated
Thanks!
Opethfan89
Are you following this guide?
http://forum.xda-developers.com/showthread.php?t=1668173
Pretty easy to follow and the easiest way to install recovery and root device.
Yes I have followed that guide and like I said I get to the step where fastboot SHOULD be recognized by my computer but it isn't. It shows up in my device manager with a yellow exclamation point so I literally just need the driver to make things work and I should be rooted.
This thread has the drivers you need: http://forum.xda-developers.com/showthread.php?t=1661653
There are no special fast boot drivers. Just install the Asus drivers, and you'll be good to go.
Also, I know this is off-topic, and I mean no offense to you, but every time I see a thread about driver problems in Windows, I feel a thousand times better about using Linux. No drivers to install. It just works.
Have you tried to see the index on tf300t development?
Hope you have all you need and all process.
For Fastboot : [GUIDE] Help for flash more faster when you use Fastboot Line Command
And for Drivers:
ASUS Android USB Drivers.zip - 2012/04/13 - MD5 Sum: 43af8f39ed421caabecd6c4a2de17212 - Size: 8.28 MB (8687221 bytes)
ASUS Pad PC Suite (PC version V1.0.41) - MD5 Sum: 02d7661affefeb0ae05f577b6b24b37a - Size: 145.09 KB (148570 bytes)
ASUS Sync V1.0.82 - MD5 Sum: a7d229ee2f2678819e6a99711d1f572d - Size: 62.18 MB (65195236 bytes)
You will find all you need for your TF300t in this index
As long as you have the android sdk installed and the asus pad suite driver installed it should work no problem
vel0city said:
As long as you have the android sdk installed and the asus pad suite driver installed it should work no problem
Click to expand...
Click to collapse
You don't need to use android sdk except if you to use commands line.
Use the guide about [URL "http://forum.xda-developers.com/showpost.php?p 27218675&postcount 20"][GUIDE] Help for flash more faster when you use Fastboot Line Command[/URL] and you will see than it's easy and faster to push something
I haven't use android sdk though it's installed on my laptop
philos64 said:
You don't need to use android sdk except if you to use commands line.
Use the guide about [URL "http://forum.xda-developers.com/showpost.php?p 27218675&postcount 20"][GUIDE] Help for flash more faster when you use Fastboot Line Command[/URL] and you will see than it's easy and faster to push something
I haven't use android sdk though it's installed on my laptop
Click to expand...
Click to collapse
I think you do need to install android sdk because of the fastboot files are in there and need it to use fastboot that could be the reason why his computer does not recognize the tablet when he is in fastboot mode. If you look at your android manager you will see a file under android tools that fastboot files are installed.
you need to specify device id
fastboot -i 0x0b05 flash recovery recovery-clockwork-5.5.0.4-tf300t.img
Click to expand...
Click to collapse
try that op
IT WORKED!!!!
EndlessDissent said:
This thread has the drivers you need: http://forum.xda-developers.com/showthread.php?t=1661653
There are no special fast boot drivers. Just install the Asus drivers, and you'll be good to go.
Also, I know this is off-topic, and I mean no offense to you, but every time I see a thread about driver problems in Windows, I feel a thousand times better about using Linux. No drivers to install. It just works.
Click to expand...
Click to collapse
See, I think that's where I messed up. None of the guides say to download ASUS' drivers, and in my anxiousness to root I must have overlooked that step. I will try this today and post my results accordingly!! Also, no offense taken by the linux comment, and I've used linux in the past, but I've had quite a few times where it doesn't "just work" (Like using a broadcom wireless card on my old laptop. I had to learn how to use ndiswrapper and whatnot, not a pleasant experience for a linux newb at that time!!)
I recently removed my Linux partition (was using ubuntu 10.10 because I hate unity!!) and can re-install it if it will make my rooting process easier?
vel0city said:
As long as you have the android sdk installed and the asus pad suite driver installed it should work no problem
Click to expand...
Click to collapse
Yea I didn't download the asus pad suite drivers, and I think that is what is causing my issue. I wish I could post links to the guides I am following but none of them specify that. They just say to download the android SDK and all drivers are included.
FlyingPoo said:
you need to specify device id
try that op
Click to expand...
Click to collapse
I did do that, flyingpoo. At one point my cmd line showed "Sending file recovery.img (5***kb)" but the tablet never picked it up, so I know there is just some miscommunication between the tablet and the PC. When I typed adb devices in cmd line, I see the device listed, but when I type fastboot devices in cmd line, it just goes to a blank line.
I will try the above listed solutions and hope that something works. Thank you all so much for your help!
*edit* This guy, right here? Yea, he's freakin ecstatic! I installed the drivers from EndlessDissents' post, and it worked!! As soon as I booted into fastboot mode, my computer recognized the device. I then used the command that FlyingPoo used (which I tried in the past), and it showed:
Code:
c:\recovery1>fastboot -i 0x0b05 flash recovery recovery.img
sending 'recovery' <5306 KB>...
OKAY [2.417s]
writing 'recovery'...
OKAY [2.053s]
finished. total time: 4.473s
So now I'm following the next few steps to root it. I've backed up my apps using Astro as well as the ASUS backup suite, and I'm using CWM for a backup of my entire system at the moment.
Thank you again to everyone who responded. I always get hung up on the simplest step, but once that is overcome everything else is a smooth ride downhill
One last noobish question to ask, and then I think I'll be done:
I've downloaded the root-signed.zip file, as well as the latest CyanogenMod file I could find (The official wiki didn't have one listed for any asus products, for some reason?) as well as a google apps for cyanogenmod. I put the files on my SD card but nothing on there is detected within CWM. So the noobish question is which directory do I need to put the files in for CWM to detect it?
That being said, I'm also wanting to backup my system to my external SD card and I selected the option in CWM to backup but it said no sd\ext was detected. Any thoughts?
Thanks again everyone for your responses.
*EDIT* For anyone following this thread, I did figure it out. Another guide I referenced specifies that you copy the files to the INTERNAL SD card (which is kind of confusing, as SD card explicitly refers to an external memory card) and then choose it from CWM. So for me, I downloaded the files on my computer, copied them to my SD card, put the SD card in my tablet, and copied the files to the root directory of the internal storage on my tablet.
Thanks again everyone, I now have root (at least, I'm pretty sure I do?)
Mod, please feel free to close this thread as necessary.
Hey everyone. Long time lurker, first time poster, and always grateful.
Okay, so I took a good look at some related threads. They all seem to have been resolved by using tools specific to their particular device. I have not had luck following their lines. So, here's what's up with me:
Asus Transformer Tf700 US edition
Had Cyanogen Mod. Wanted to sell my tablet, so I decided to wipe and go back to factory. Unfortunately, while fooling around in TWRP, I managed to putz it up and wipe the system and data. So no more OS, and apparently no more super user (whoops), although I may be wrong about that.
I can reboot the device into TWRP, but I can't mount the microsd card. When I plug my microsd card into my device, I just get an error that says cannot mount external sd card. So, since that isn't working, I've tried to sideload via adb.
I have the SDK but can't run ADB sideload because ADB on my computer does not recognize my device. I have tried to install updated drivers, though the drivers that I did find, when I point windows to the folder with them, it doesn't see a driver. SO maybe I'm doing that wrong.
I'm completely at my wit's end here. Can someone give me a little help?
Thanks everyone for your help in advance.
Specifics please????
CM, TWRP, Windows, drivers: What version?
You may want to try this, it installs the drivers for you: http://forum.xda-developers.com/showthread.php?t=2588979
berndblb said:
Specifics please????
CM, TWRP, Windows, drivers: What version?
You may want to try this, it installs the drivers for you: http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
Hey there, thanks so much for replying!
I'm using TWRP v2.6.0.0.
Windows 7 x64 SP1
The CM version that I had, I actually don't recall now. I had flashed it back to stock though, before this, by using TWRP recovery. I noticed after that that I had not flashed my saved files properly. That's when I pooched it, hah.
I removed the existing USB drivers via device manager, restarted, used the installer that you linked to, restarted, and plugged in my device. It said installing drivers, and then failed to install drivers. ADB does not recognize a connected device. Merp.
I still haven't had any luck. Does anyone have any ideas?
You have to get the Windows drivers working to get ADB and fastboot access to your tablet and that can be tricky. Any chance you can get your hands on a Linux machine?
If the ADB tool I linked to didn't work (and I don't understand why - I used it on Win7 32 bit without a hitch) try to install the Google Universal Naked Drivers (google the term and should find them easily).
Actually - do you have the Asus device drivers installed? What happens if you connect the USB cable? Does Windows recognize the device at all? If not try to download Asus Sync, install it and try again. Once Windows recognizes the tablet as a MTP device, run the adb tool again and then try "adb devices" when you are booted into Android and "fastboot devices" when the tablet is in fastboot mode.
http://forum.xda-developers.com/showthread.php?t=2646279
berndblb said:
You have to get the Windows drivers working to get ADB and fastboot access to your tablet and that can be tricky. Any chance you can get your hands on a Linux machine?
If the ADB tool I linked to didn't work (and I don't understand why - I used it on Win7 32 bit without a hitch) try to install the Google Universal Naked Drivers (google the term and should find them easily).
Actually - do you have the Asus device drivers installed? What happens if you connect the USB cable? Does Windows recognize the device at all? If not try to download Asus Sync, install it and try again. Once Windows recognizes the tablet as a MTP device, run the adb tool again and then try "adb devices" when you are booted into Android and "fastboot devices" when the tablet is in fastboot mode.
Click to expand...
Click to collapse
Hey, thanks for the reply. When I plug in the device, it tries to install drivers and almost immediately fails. It then shows in the device manager as shown in the attached file. When I right click, select update driver, and point it to the folder with the google naked drivers (or the asus drivers), it says that "Windows cannot find drivers for this device." This seems strange to me. It has no idea what the transformer is when it is plugged in. Is there a different manual method of installing drivers, or cuing windows to recognize that these are the correct drivers?
I had Asus Sync installed, and that didn't seem to do anything for me. Windows would not do anything differently than it had already done. Grrr. This hurts.
sbdags said:
http://forum.xda-developers.com/show....php?t=2646279
Click to expand...
Click to collapse
This method looks promising, but it requires one to go into Android and turn on USB debugging mode. Problem is: I have no OS to log in to in order to do so
Whoops, forgot screen shot
Jeez - this is frustrating. I'm running out of ideas how to get Windows to work...
You are running Windows with administrator rights - yes?
Consider installing Linux as a dual boot on your Windows machine. I did that just to get rid of these ADB/fastboot driver problems....
berndblb said:
Jeez - this is frustrating. I'm running out of ideas how to get Windows to work...
You are running Windows with administrator rights - yes?
Consider installing Linux as a dual boot on your Windows machine. I did that just to get rid of these ADB/fastboot driver problems....
Click to expand...
Click to collapse
I'm running shy on space on my OS SSD, but would it potentially work running off of a boot disk? I have Fedora lying around here somewhere. Would the process be especially different? I have so very little experience working in Linux.
Also, I wonder if this is important. When I tell TWRP to reboot the machine, it informs me that super user isn't installed, and offers to root my device for me, but when I select that option, the screen just goes blank and it appears to hang, and I have to reboot it with the volume and power keys.
hardshank said:
I'm running shy on space on my OS SSD, but would it potentially work running off of a boot disk? I have Fedora lying around here somewhere. Would the process be especially different? I have so very little experience working in Linux.
Also, I wonder if this is important. When I tell TWRP to reboot the machine, it informs me that super user isn't installed, and offers to root my device for me, but when I select that option, the screen just goes blank and it appears to hang, and I have to reboot it with the volume and power keys.
Click to expand...
Click to collapse
I have no idea if you can run adb or fastboot if you boot Linux off a boot disc - but what the heck? Why not try it at this point?
I do not understand your driver problems at all. I helped someone today with a lot of the same problems: The tablet only booted into recovery, TWRP would not mount the microSD, didn't see any files on the internal... The ADB tool I linked to earlier allowed him to adb reboot to the bootloader - the rest was a breeze... Something in your Windows setup is just effed up... Sorry - wish I had that magic wand...
berndblb said:
I have no idea if you can run adb or fastboot if you boot Linux off a boot disc - but what the heck? Why not try it at this point?
Click to expand...
Click to collapse
Sure, if you have compatible adb and fastboot binaries it should work. Linux doesn't care where it was booted from.
_that said:
Sure, if you have compatible adb and fastboot binaries it should work. Linux doesn't care where it was booted from.
Click to expand...
Click to collapse
I had to install the adb and fastboot binaries on my distro. You can't do that on Linux running off a disc - can you? You would have to find a distro that comes with them?
berndblb said:
I had to install the adb and fastboot binaries on my distro. You can't do that on Linux running off a disc - can you? You would have to find a distro that comes with them?
Click to expand...
Click to collapse
On some live distros you can install additional software to a ramdisk. For adb and fastboot, any live distro with 32 bit libraries should have the required libs so that you can just copy/download the binaries and run them.
So here is an interesting development: I am now able to see my micro SD card when it is plugged into my device. Why? I haven't the foggiest. However, I still can't see any of its contents. Curious....
hardshank said:
So here is an interesting development: I am now able to see my micro SD card when it is plugged into my device. Why? I haven't the foggiest. However, I still can't see any of its contents. Curious....
Click to expand...
Click to collapse
Okay. I can't believe this worked, but I'm back in action. Here's how it went down:
- I tried doing a Linux USB drive, but was having difficulties getting it to boot, and my knowledge of Linux is so limited, I basically gave up hope.
- Today, I picked up my tablet (which has remained plugged in for power all of this time), and rebooted it. At the opening screen, which allows me to choose to go into TWRP, boot into (I think) Linux, or wipe data, I had never selected Wipe Data. Why? Because accidentally wiping the wrong partition is what got me in this mess to begin with.
- SO then I think, what the hell. It seems to have actually done something (though I don't know what), so I grab my micro SD with stock Android loaded on it, and pop it in. Voilà! It is recognized (as above).
- For some reason, no contents of card are visible
- Restarted device: card contents visible!
- Selected "Install" in TWRP menu, and selected my stock ROM
So. This has been a weird month. Thank you to EVERYONE who helped out on this. I'll be sure to hit the Thanks buttons!
hardshank said:
Okay. I can't believe this worked, but I'm back in action. Here's how it went down:
- I tried doing a Linux USB drive, but was having difficulties getting it to boot, and my knowledge of Linux is so limited, I basically gave up hope.
- Today, I picked up my tablet (which has remained plugged in for power all of this time), and rebooted it. At the opening screen, which allows me to choose to go into TWRP, boot into (I think) Linux, or wipe data, I had never selected Wipe Data. Why? Because accidentally wiping the wrong partition is what got me in this mess to begin with.
- SO then I think, what the hell. It seems to have actually done something (though I don't know what), so I grab my micro SD with stock Android loaded on it, and pop it in. Voilà! It is recognized (as above).
- For some reason, no contents of card are visible
- Restarted device: card contents visible!
- Selected "Install" in TWRP menu, and selected my stock ROM
So. This has been a weird month. Thank you to EVERYONE who helped out on this. I'll be sure to hit the Thanks buttons!
Click to expand...
Click to collapse
Glad you got it working!
Out of curiosity: Was your tablet booted or completely off until you picked it up today? Did you reboot into the bootloader or did it do that by itself?
Sent from my ASUS Transformer Pad TF700T using Tapatalk
Read this whole guide before starting.
This is for the 8th gen Fire HD8 (karnak).
Current version: amonet-karnak-v3.0.1.zip
This is based on @xyz`s original work, but adds some features such as reboot to hacked BL.
It also intends to simplify the installation process.
If you are already unlocked you can simply update by flashing the ZIP-file in TWRP.
NOTE: If you are on a firmware lower than 6.3.1.2 this process does not require you to open your device, but should something go horribly wrong, be prepared to do so.
What you need:
A Linux installation or live-system
A micro-USB cable
Install python3, PySerial, adb, fastboot dos2unix. For Debian/Ubuntu something like this should work:
Code:
sudo apt update
sudo add-apt-repository universe
sudo apt install python3 python3-serial adb fastboot dos2unix
1. Extract the attached zip-file "amonet-karnak-v3.0.1.zip" and open a terminal in that directory.
NOTE: If you are already rooted, continue with the next step, otherwise get mtk-su by @diplomatic from here and place (the unpacked binary) into amonet/bin folder
2. Enable ADB in Developer Settings
3. Start the script:
Code:
sudo ./fireos-step.sh
NOTE: If you are on a firmware newer than 6.3.0.1, a downgrade is necessary, this requires bricking the device temporarily. (The screen won't come on at all)
WARNING: There have been numerous reports that would indicate a hardware-change that doesn't allow access to the bootrom.
When bricking these devices there is currently no known way to unbrick.
This makes the hardware-method currently the safest option.
To brick firmware 6.3.1.2 use the attached brick-karnak.zip, boot into fastboot
Code:
adb reboot bootloader
and run
Code:
./brick-6312.sh
Make sure ModemManager is disabled or uninstalled:
Code:
sudo systemctl stop ModemManager
sudo systemctl disable ModemManager
After you have confirmed the bricking by typing "YES", you will need disconnect the device and run
Code:
sudo ./bootrom-step.sh
Then plug the device back in.
The device will reboot into TWRP.
You can now install Magisk from there.
Going back to stock
Extract the attached zip-file "amonet-karnak-return-to-stock.zip" into the same folder where you extracted "amonet-karnak-v3.0.1.zip" and open a terminal in that directory.
Then run:
Code:
sudo ./return-to-stock.sh
Your device should reboot into Amazon Recovery. Use adb sideload to install stock image from there. (Make sure to use FireOS 6.3.0.0 or newer, otherwise you may brick your device)
Important information
Don't flash boot/recovery images from FireOS (FlashFire, MagiskManager etc.)
TWRP will prevent updates from overwriting LK/Preloader/TZ, so generally installing an update should work without issues (only full updates, incremental updates won't work).
For ROM developers there is still an option to overwrite these, which should only be done after thorough testing and if needed (LK should never be updated).
It is still advised to disable OTA.
Very special thanks to @xyz` for making all this possible and putting up with the countless questions I have asked, helping me finish this.
Special thanks also to @diplomatic for his wonderfull mtk-su, allowing you to unlock without opening the device.
Thanks to @Kaijones23 for testing.
Unbricking / Unlocking with Firmware 6.3.1.2+
If Recovery OR FireOS are still accessible (or your firmware is below 6.3.1.2) there are other means of recovery, don't continue.
If your device shows one of the following symptoms:
It doesn't show any life (screen stays dark)
You see the white amazon logo, but cannot access Recovery or FireOS.
If you have a Type 1 brick, you may not have to open the device, if your device comes up in bootrom-mode (See Checking USB connection below).
Make sure the device is powered off, by holding the power-button for 20+ seconds
Start bootrom-step.sh
Plug in USB
In all other cases you will have to open the device.
Make sure ModemManager is disabled or uninstalled:
Code:
sudo systemctl stop ModemManager
sudo systemctl disable ModemManager
NOTE: If you have issues running the scripts, you might have to run them using sudo.
Also try using different USB-ports (preferably USB-2.0-ports)
Open the device and short the pin marked in the attached photo to ground while plugging in.
1. Extract the attached zip-file "amonet-karnak-v3.0.zip" and open a terminal in that directory.
2. start the script:
Code:
sudo ./bootrom-step.sh
It should now say Waiting for bootrom.
3. Short the device according to the attached photo and plug it in.
4. When the script asks you to remove the short, remove the short and press enter.
5. Wait for the script to finish.
If it stalls at some point, stop it and restart the process from step 2.
6. Your device should now reboot into unlocked fastboot state.
7. Run
Code:
sudo ./fastboot-step.sh
8. Wait for the device to reboot into TWRP.
9. Use TWRP to flash custom ROM, Magisk or SuperSU
Checking USB connection
In lsusb the boot-rom shows up as:
Code:
Bus 002 Device 013: ID [b]0e8d:0003[/b] MediaTek Inc. MT6227 phone
If it shows up as:
Code:
Bus 002 Device 014: ID [b]0e8d:2000[/b] MediaTek Inc. MT65xx Preloader
instead, you are in preloader-mode, try again.
dmesg lists the correct device as:
Code:
[ 6383.962057] usb 2-2: New USB device found, idVendor=[b]0e8d[/b], idProduct=[b]0003[/b], bcdDevice= 1.00
Reserved #2
Reserved #3
This is very cool @k4y0z!
Now we can use boot-recovery.sh & boot-fastboot no?
Regards!
Rortiz2 said:
This is very cool @k4y0z!
Now we can use boot-recovery.sh & boot-fastboot no?
Regards!
Click to expand...
Click to collapse
Yes, that is also supported.
k4y0z said:
NOTE: If you are on a firmware lower than 6.3.1.2 this process does not require you to open your device, but should something go horribly wrong, be prepared to do so.
NOTE: If you are on a firmware newer than 6.3.0.1, a downgrade is necessary, this requires bricking the device temporarily. (The screen won't come on at all)[/COLOR]
Click to expand...
Click to collapse
So do you need to open the case to run this exploit on the newest firmware, or can you just brick to install older lk/preloader, and go from there?
Kctucka said:
So do you need to open the case to run this exploit on the newest firmware, or can you just brick to install older lk/preloader, and go from there?
Click to expand...
Click to collapse
On 6.3.1.2 mtk-su has been fixed, so unless you already have root (or another way to get temp-root is found), bricking isn't an option and you will have to open the case.
If you do have root the script will do the bricking for you.
@k4y0z For people who already used the steps in xyz's thread and are running your TWRP and LineageOS, is there anything here that we're missing? Or is this just a new method to arrive at the same results?
jibgilmon said:
@k4y0z For people who already used the steps in xyz's thread and are running your TWRP and LineageOS, is there anything here that we're missing? Or is this just a new method to arrive at the same results?
Click to expand...
Click to collapse
k4y0z said:
This is based on @xyz`s original work, but adds some features such as reboot to hacked BL.
It also intends to simplify the installation process.
If you are already unlocked you can simply update by flashing the ZIP-file in TWRP.
Click to expand...
Click to collapse
Additionally it adds support for the boot-recovery and boot-fastboot scripts.
And a script to enable UART output for the kernel.
So nothing essential if you are already using the updated TWRP.
Ran this pup on a unit that I was keeping unrooted (aside from occational temp root via mtk-su) as a control but was becoming painful to use/maintain. Also missed TWRP. Worked like a champ with zero issues ... aside from stumbling over my own stupidity. Used Lubuntu live 18.04 and Magisk 19.3/7.3.2. Staying on FireOS 6.3.0.1 (w/hijacks) for now until a fully vetted custom ROM becomes available.
Thanks for the great tool and accompanying guidance.
I have added unbricking/bootrom instructions in Post #2
@k4y0z
If I flash your zip, can I then flash Amazon update as is? Will your TWRP manage the bootloaders/etc when flashing the stock ROM?
bibikalka said:
@k4y0z
If I flash your zip, can I then flash Amazon update as is? Will your TWRP manage the bootloaders/etc when flashing the stock ROM?
Click to expand...
Click to collapse
I think yeah:
TWRP will prevent updates from overwriting LK/Preloader/TZ, so generally installing an update should work without issues (only full updates, incremental updates won't work).
Click to expand...
Click to collapse
So I got a HD8 2018 today and it came with OS version that forced me to connect to WiFi and update itself. I was pretty pissed but I used this guide to get root easily.
I had Arch based linux installed which gave problems while running script, so I made bootable Ubuntu usb and that worked fine. Thank you everyone involved in developing this hack.
madman said:
So I got a HD8 2018 today and it came with OS version that forced me to connect to WiFi and update itself. I was pretty pissed but I used this guide to get root easily.
I had Arch based linux installed which gave problems while running script, so I made bootable Ubuntu usb and that worked fine. Thank you everyone involved in developing this hack.
Click to expand...
Click to collapse
For future reference you can avoid the presumed forced WiFi connect by putting in a bogus password; once authentication fails a 'skip' option will appear.
bibikalka said:
@k4y0z
If I flash your zip, can I then flash Amazon update as is? Will your TWRP manage the bootloaders/etc when flashing the stock ROM?
Click to expand...
Click to collapse
Rortiz2 said:
I think yeah:
Click to expand...
Click to collapse
Yes, exactly.
Rortiz2 said:
I think yeah:
Click to expand...
Click to collapse
k4y0z said:
Quote:
TWRP will prevent updates from overwriting LK/Preloader/TZ, so generally installing an update should work without issues (only full updates, incremental updates won't work).
Yes, exactly.
Click to expand...
Click to collapse
OK - tried to upgrade to the latest update-kindle-Fire_HD8_8th_Gen-NS6312_user_1852_0002517056644.bin using the suggestions above, and got a hardcore Amazon logo bootloop.
My actions. I had the old unlock, so I flashed the zip in this thread first. New TWRP showed up - so far so good. Then I flashed the Amazon update zip as is, thinking the updated TWRP would do its magic. Flashed Magisk, tried to reboot. No go - Amazon logo bootloop. No recovery either. So it feels that I lost the unlock, and, perhaps LK & preloader & TZ got overwritten with the new versions from the Amazon update zip.
Any recovery here other than opening the case?
bibikalka said:
OK - tried to upgrade to the latest update-kindle-Fire_HD8_8th_Gen-NS6312_user_1852_0002517056644.bin using the suggestions above, and got a hardcore Amazon logo bootloop.
My actions. I had the old unlock, so I flashed the zip in this thread first. New TWRP showed up - so far so good. Then I flashed the Amazon update zip as is, thinking the updated TWRP would do its magic. Flashed Magisk, tried to reboot. No go - Amazon logo bootloop. No recovery either. So it feels that I lost the unlock, and, perhaps LK & preloader & TZ got overwritten with the new versions from the Amazon update zip.
Any recovery here other than opening the case?
Click to expand...
Click to collapse
That is strange, I've had no issues installing that firmware unmodified through TWRP.
So you can't boot neither normal or recovery?
Does it say something in the corner when trying to boot recovery?
You can try the boot-fastboot.sh script to get into hacked fastboot.
k4y0z said:
That is strange, I've had no issues installing that firmware unmodified through TWRP.
So you can't boot neither normal or recovery?
Does it say something in the corner when trying to boot recovery?
You can try the boot-fastboot.sh script to get into hacked fastboot.
Click to expand...
Click to collapse
Cannot boot anywhere - no message about booting recovery either. When you tried installing unmodified firmware, was that on HD8 2018, or some other tablet? I wonder if perhaps there are some differences with HD8 2018 given that it's Nougat.
I will try the hacked fastboot, but most likely - will have to open the case.