Hi,
I got my Nexus 9 around launch date and used Wugs toolkit to unlock bootloader, root and install teamwin recovery.
I kept gettting OTA updates for 5.0.2 but they wouldn't install. After months of ignoring I thought I'd update.
It wouldn't update so I tried to use Wugs toolkit to 'Flash stock + unroot to latest version'.
This failed saying something about no fastboot device, although the device went to the white screen and seemed to be displaying hboot/fastboot as options...
I got frustrated and used TWRP to wipe everything, including the OS!
I'm used to Samsung so expected an Odin type program to flash over my mess... I can't seem to do anything now.
HELP! (Please!)
A reason I don't like tool kits. If they don't work as expected you have no idea what to do next. Follow the long method of this, http://forum.xda-developers.com/showthread.php?p=58956577
Sent from my Nexus 9 using XDA Free mobile app
Appreciate the reply but I can't enable anything within the device as there is no OS installed...
I have used vol down and power to select fastboot.... Is this "Boot your device into the bootloader" in your guide?
All I get is waiting for device in the cmd window
thanks
jotan said:
Appreciate the reply but I can't enable anything within the device as there is no OS installed...
I have used vol down and power to select fastboot.... Is this "Boot your device into the bootloader" in your guide?
All I get is waiting for device in the cmd window
thanks
Click to expand...
Click to collapse
Vol down and power does bring you into the bootloader. Do you have usb drivers setup? Go into device manager on your pc with the device connected. Do you have an icon with a yellow exclamation mark? If so right click on it and go to where you can choose a driver from a list on your computer. Choose Android adb composite interface.
Sent from my Nexus 9 using XDA Free mobile app
Sorry about the late reply, been on my honeymoon! For some reason it just wouldn't work on my PC, so I used my laptop and all was well.
Thanks.
Thread closed!
Related
I'm having trouble getting this POS rooted. Got it unlocked with little problem, but now that it comes to rooting, it's extremely confusing to follow the tutorials. Is there any working one-click methods? I'm no stranger to Android OS, I had my Dinc2 rooted in about 5 minutes after unboxing. But this abomination is really working my nerves. Help please?
There is no "One-Click Root"
But rooting using the given instructions is not difficult at all.
Its as simple as downloading a few files, and typing a few codes.
what have you tried so far? and what firmware are you running?
Since you unlocked your bootloader,here is how you get Root
http://forum.xda-developers.com/sho...m.xda-developers.com/showthread.php?t=1130639
download the .img ,put it in your fastboot folder
download the rootxperia.zip to your SD card
Turn phone off,plug into your PC/Laptop and hold search button ( might take some tries) ,you should get BLUE LED
SHIFT+RIGHTCLICK on fastboot folder and open in command window (assuming your usiing vista/win7) and type
fastboot boot recoveryPLAY.img
wait 2 minutes,it takes time.
Apply zip from SDcard and you are rooted
Cat_On_Droid said:
Since you unlocked your bootloader,here is how you get Root
http://forum.xda-developers.com/sho...m.xda-developers.com/showthread.php?t=1130639
download the .img ,put it in your fastboot folder
download the rootxperia.zip to your SD card
Turn phone off,plug into your PC/Laptop and hold search button ( might take some tries) ,you should get BLUE LED
SHIFT+RIGHTCLICK on fastboot folder and open in command window (assuming your usiing vista/win7) and type
fastboot boot recoveryPLAY.img
wait 2 minutes,it takes time.
Apply zip from SDcard and you are rooted
Click to expand...
Click to collapse
the wait for recovery to load is HORRIBLE!! lol. push the menu button once in a while if you are unsure. i did. it makes the wait (for me) less painful but installing the .zip and rebooting successfully with a rooted phone is AWESOME!!
Thanks for simplifying it for me Cat. I'm sitting here with my blue LED, my blank screen and my command window that now says "waiting for device" so that's what I'm doing. Waiting. Smoke break time.
chattguy said:
Thanks for simplifying it for me Cat. I'm sitting here with my blue LED, my blank screen and my command window that now says "waiting for device" so that's what I'm doing. Waiting. Smoke break time.
Click to expand...
Click to collapse
God this is painful. It's doing nothing. Should I unplug and try it again? it's been over 10 minutes.
chattguy said:
God this is painful. It's doing nothing. Should I unplug and try it again? it's been over 10 minutes.
Click to expand...
Click to collapse
are you sure that you installed the "S1Boot Fastboot" driver completely ?
cause i had some problem like yours ... just go to my computer=> right clik => manage=> devicce manager
and check if it's already install or not (( other devices ))
mehdi.moha said:
are you sure that you installed the "S1Boot Fastboot" driver completely ?
cause i had some problem like yours ... just go to my computer=> right clik => manage=> devicce manager
and check if it's already install or not (( other devices ))
Click to expand...
Click to collapse
Sony Ericsson sa0102 is installed, but I'm not seeing anything in my device manager about S1 Fastboot. Hmm...how would one go about installing it? I have the fastboot folder on my desktop. It has two subfolders, Fastboot and USB_drivers .
chattguy said:
God this is painful. It's doing nothing. Should I unplug and try it again? it's been over 10 minutes.
Click to expand...
Click to collapse
In this case if it's either still 'waiting for device' or trying to boot recoveryPLAY.img, then you're safe to try again since nothing is being flashed
When connected next time, in fastboot mode, before booting the .img, type this:
fastboot devices 'enter'
It will show a list of devices attached.
It might be that your missing some drivers so fastboot is not working correctly and won't detect your device. Have you pc companion installed? I don't remember if there came any drivers with the fastboot download but check that, there might be some drivers you didn't install.
Regards Dousan...
This is what happens. I just get another prompt. Here's a screenshot of that, along with the drivers folder.
chattguy said:
This is what happens. I just get another prompt. Here's a screenshot of that, along with the drivers folder.
Click to expand...
Click to collapse
That means no device is connected. Unlike ADB, fastboot does not return the usuall "list of attached devices" line. Have you installed fastboot drivers?
Sent from my R800i using Tapatalk
AndroHero said:
That means no device is connected. Unlike ADB, fastboot does not return the usuall "list of attached devices" line. Have you installed fastboot drivers?
Sent from my R800i using Tapatalk
Click to expand...
Click to collapse
I don't know, I just installed what the guy told me to when he did the remote bootloader unlock. Fastboot IS in my device manager, however, it says there are no drivers installed. I've got the blasted things on my desktop with some DPInst.exe installer, but it says I need the 64-bit version, which I can't find. Microsoft tried to have me download some silly .ISO file but I really think there must be an easier way than to burn some DVD installation disk.
chattguy said:
I don't know, I just installed what the guy told me to when he did the remote bootloader unlock. Fastboot IS in my device manager, however, it says there are no drivers installed. I've got the blasted things on my desktop with some DPInst.exe installer, but it says I need the 64-bit version, which I can't find. Microsoft tried to have me download some silly .ISO file but I really think there must be an easier way than to burn some DVD installation disk.
Click to expand...
Click to collapse
Ok these are the x32/x64 fastboot drivers.
http://www.multiupload.com/0XZV1LXRVA
Download them and unpack them. Connect your device in fastboot mode. Then navigate to device manager on windows, Find the S1 Fastboot thats not installed correctly. go to update driver and navigate to the driver package you just unpacked. Done
AndroHero said:
Ok these are the x32/x64 fastboot drivers.
http://www.multiupload.com/0XZV1LXRVA
Download them and unpack them. Connect your device in fastboot mode. Then navigate to device manager on windows, Find the S1 Fastboot thats not installed correctly. go to update driver and navigate to the driver package you just unpacked. Done
Click to expand...
Click to collapse
Mother. Of. God.
I did it. No, f**k that, you did it. All of you, thank you so much. You guys really helped me out bigtime, without berating me and calling me a noob lol. I sincerely appreciate it.
Also a special thanks to Alejandrissimo for unlocking the bootloader. Without you, this wouldn't have even been possible. Yay this blasted phone is finally rooted...
...and nobody had to die in the process.
That's what we are all here for. Learning about things through each other. We were all without knowledge at one point
Sent from my R800i using XDA App
I need some serious help... I think I bricked my Nextbook Premium 7. I compiled a custom ROM and forgot to included a launcher. Didn't realize it until after I flashed it. My tablet is stuck in a bootloop and only way to shut it down is with the reset [pin hole] button. Power button does nothing except start it up. I have already tried to put the stock update.img on an external SD hoping it would boot from there, but it did not. I am not sure what to do next, I have looked all over google and xda. Please help!
Thank you in advance!
Do you have a custom recovery installed? Did you try installing it threw fastboot files and cmd prompt on computer?
Please hit the thank you button if i helped!
techno-update said:
Do you have a custom recovery installed? Did you try installing it threw fastboot files and cmd prompt on computer?
Please hit the thank you button if i helped!
Click to expand...
Click to collapse
There ins't a custom recovery installed, this device flashes by detecting an update.img and askes to install it. It doesn't get past what would be considered the kernel screen. This tablet doesn't work like a standard android phone. There are no hard buttons except the power button, so attempting to get into any recovery is not possible. It also doen't boot enough to add any files to it.
Sounds like your screwed. Sorry.....
Please hit the thank you button if i helped!
check out this link
http://forum.xda-developers.com/showthread.php?t=1410862&page=9
Ok, just bricked my Nextbook 7
Here is how I flashed a firmware without access to recovery:
If you are in a bootloop, Connect USB and Power.
Press and hold pin on back until you hear windows try to detect a device but the screen is off.
Download this: http://arctablet.com/assets/tools/Fi..._Tool_v1.4.zip
Install the driver from the drivers folder.
3. Installing the drivers on the computer
Following the tablet entering in recovery mode, the computer should now show it has found a new USB device and prompt for a device driver. Select the appropriate driver in the driver directory from the Rockchip Flash Tool 1.4 package.
It will then install the driver for RK29 Device
4. Sending the firmware to the tablet
The flashing tool should display a green square around the number 1 in the lower left area of the Windows application.
Select the firmware file to flash using the button in the top right area of the application. Select the update.img file from here:
http://www.multiupload.com/NQHSNZJSO2
Then push the Upgrade button to transfer the selected firmware to the tablet.
The firmware will be copied to the tablet, a progression counter will go from 0% to 100% on this step, followed by a verification.
You are done, let the tablet reboot and update itself. It should take a few minutes for the flash process to finish.
This procedure has been successfully tested on Windows XP 32 bits for flashing a bricked NextBook 7 Premium YF1011 (but should work on others)
Help !!
Please help, got the tablet yesterday NEXT7P12 YF091211085 by flashing the official site was a brick, the tablet will not turn on, the computer does not see it.
screen moved after installing rom
Hi, i don't know if I'm on the right place but if anyone can help me, please I haw the Nextbook 7 premium and have instaled costum rom on it, but after rebooting my screen position has moved from right to left 2 cm and from up to down 1 cm , so my screen is moved I don't know why I have try to install 3 other rom and factory firmware but the screen is still moved or should I say cut. Any ideas? please I have try to google it but no luck...
I no longer have my np7 but I did try just about every ROM for it. Never have I had or seen an issue like this, and in truth I can't think of what the issue may be.
There are different np7 variants and some don't play nice with custom ROMs (built sept 2012 and older lose WiFi) so you might have a model that can only use one software due to hardware/firmware change.
There never was much development for the np7 here, I think finlessbob and others are still working on it at freaktab.com maybe see if they can help
Sent from my Nexus 4 using xda premium
d33dvb said:
Ok, just bricked my Nextbook 7
Here is how I flashed a firmware without access to recovery:
If you are in a bootloop, Connect USB and Power.
Press and hold pin on back until you hear windows try to detect a device but the screen is off.
Download this: http://arctablet.com/assets/tools/Fi..._Tool_v1.4.zip
Install the driver from the drivers folder.
3. Installing the drivers on the computer
Following the tablet entering in recovery mode, the computer should now show it has found a new USB device and prompt for a device driver. Select the appropriate driver in the driver directory from the Rockchip Flash Tool 1.4 package.
It will then install the driver for RK29 Device
4. Sending the firmware to the tablet
The flashing tool should display a green square around the number 1 in the lower left area of the Windows application.
Select the firmware file to flash using the button in the top right area of the application. Select the update.img file from here:
http://www.multiupload.com/NQHSNZJSO2
Then push the Upgrade button to transfer the selected firmware to the tablet.
The firmware will be copied to the tablet, a progression counter will go from 0% to 100% on this step, followed by a verification.
You are done, let the tablet reboot and update itself. It should take a few minutes for the flash process to finish.
This procedure has been successfully tested on Windows XP 32 bits for flashing a bricked NextBook 7 Premium YF1011 (but should work on others)
Click to expand...
Click to collapse
Your link not working? Send alternative link please!
I've tried to also find the tbauto root downloads but my browsers never find the page no matter who's link i try I'm a massive noob but i have rooted my nexus s 4g and last night i put ics onto my friend touch pad so I thought i was able to follow directions but i guess not.
steps i took:
downloaded all files needed to run revolutionary
downgraded
ran revolutionary
got correct code from serial number
reboots into bootloader (on phone ) says waiting for fastboot on revolutionary
help out a noob!
screen shot
View attachment 928832
loook
colbatronbmw said:
I've tried to also find the tbauto root downloads but my browsers never find the page no matter who's link i try I'm a massive noob but i have rooted my nexus s 4g and last night i put ics onto my friend touch pad so I thought i was able to follow directions but i guess not.
steps i took:
downloaded all files needed to run revolutionary
downgraded
ran revolutionary
got correct code from serial number
reboots into bootloader (on phone ) says waiting for fastboot on revolutionary
help out a noob!
Click to expand...
Click to collapse
once the phone boots into the bootloader you have to press the power button to select fastboot from the menu (vol +/- are used to scroll). this will put the phone in fastboot. if your usb connection is detected it should display "fastboot usb" on your phone after a few seconds.
what software version do you have? If it is 2.11.605.9 then there are extra steps need to get it.
---------- Post added at 02:36 PM ---------- Previous post was at 02:32 PM ----------
If you are on the system version stated above use this http://www.cd-net.net/dev/Joomla/index.php/projects/htc-thunderbolt-hacking to root.
Thanks I'll try it
Sent from my Nexus S 4G using Tapatalk
Another option disconnect the phone from the USB and reconnect it after a few seconds. Might have to power cycle the phone also.
Solution to "waiting for fastboot"
I just ran into this same problem, nothing I could find would work. I was using the thunderbolt all-in-one solution to root my phone and was stuck on the revolutionary step. If I power cycled and booted into recovery and selected fastboot, the phone would say "fastboot usb" for a moment, but then it would just say "fastboot". Finally, I found a solution. With Revolutionary stuck at "waiting for fastboot...." I did the following:
* uninstalled the HTC drivers
* reinstalled the drivers
* power cycle phone and boot into recovery
* select fastboot
again it said "fastboot usb", then toggled to "fastboot", but then windows gave me a message telling me that a device driver was installed, and it togged back to "fastboot usb". revolutionary was then able to find my phone and go to the next step which was... booting into fast boot (once moar). again it hung here, and I had to repeat all of the above steps.
after this I was able to install CWM successfully, and use the all-in-one tool to install the super user program.
What version of windows are u on?
Sent from my Liquidsmooth Rezound using xda app-developers app
tburns said:
What version of windows are u on?
Sent from my Liquidsmooth Rezound using xda app-developers app
Click to expand...
Click to collapse
I am on Windows 7
Try running the tool on administrator. Also when you connect the device before you start the process and you get the prompt to run HTC sync don't touch it. Don't close or allow the dialog just leave it be until the tool is run.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
Try running the tool on administrator. Also when you connect the device before you start the process and you get the prompt to run HTC sync don't touch it. Don't close or allow the dialog just leave it be until the tool is run.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Great idea, thanks. If I root another tbolt I'll try this out.
Hi,
the last days, I read a lot about flashing custom ROMs and wanted to do so with my HTC Legend. I'm not really new to flashing ROMs in general.I already flashed several other devices, but I'm stuck with unlocking the bootloader. My problem is, that the CMD is either reacting with "CommandError" or "waiting for device". I'm not able to get the token for unlocking the bootloader. Another problem is, that the SDK Manager won't start for me. So I just grabbed the 3 files out of the filesystem and tried it with them. Using HTCs recommended fastboot.exe doesn't change anything. I hope you can help me with a few details:
1. Do I have to install something else than HTC Sync? (I think, it already installed the driver, too)
2. Which connection mode should i choose, when connecting the legend? (recharging/hdd/htc sync/tethering)
3. Which version of the SDK should I use? Is it possible, that someone just gives me a zip with those 3 files?
I'm looking forward to your answers!
Regards
OdlG
SOLUTION:
The solution was a too old version. My phone had version 3.15.405.3.
First I updated to version 3.15.405.6 (found via google here at xda-dev).
Then I patched the new ROM I downloaded from htc-dev (step 0 at unlocking; must connect phone for that hint!) 3.30.0.0.
Then I could receive the token via CMD at a Windows 7 PC (Win8 PC still said "waiting for device", obviously because the driver wasn't installed correctly so the phone wasn't recognised in fastboot mode).
I followed the last steps rom htc-dev and now unlocked the bootloader
Click to expand...
Click to collapse
(pardon my english, it's not my mothertongue)
AW: Difficulties with unlocking the Bootloader
You should use charging mode and you have to activate usb debugging in settings
Sent from my HTC One using xda app-developers app
Thanks for the reply!
I already enbled USB Debugging, and now tried it in charging mode. I created a BAT-File with the following command:
cd C:\Android\
fastboot oem get_identifier_token
But it still says "waiting for device" Any suggestions?
Did you follow these instructions? especcially selecting "fastboot"?
http://www.htcdev.com/bootloader/unlock-instructions
if yes and it still didn't work i've no idea at the moment
I tried it once more:
I connected the phone, "fastboot usb" is written there. the cmd still writes "waiting for device". after a few seconds, the pc reports, that the usb device could not be recognised. then there is written "fastboot" instead of "fastboot usb", though the cable is still connected.
a few hours ago i also got a guide at htc dev, that i should install da RUU (what does it mean btw?). i downloaded the german vodafone version and tried to install it. I will try that once more, hopefully the unlock will be successful afterwards!
thanks for your advice!
EDIT:I'm using the following software btw.
Android SDK (adt-bundle-windows-x86_64-20130219)
Java RE 7 Update 17
HTC Sync (3.3.X or something like that)
The RUU installer is starting the setup without problems. It's rebooting the phone o install version 3.30 (hboot1.02). But when the Phone starts in the bootloader mode and displays "RUU", the PC is unable to detect the USB device and the setup fails caused by missing usb connection
Can I somehow influence the detection of the phone in fastboot/bootloader mode?
Normally it should be enough to install the HTC USB Drivers...
You can grab the newest for example from this thread: http://forum.xda-developers.com/showthread.php?t=2191279
The second what you need is an actual adb.exe, fastboot.exe, AdbWinApi.dll & AdbWinUsbApi.dll... grab it for example from here: http://d-h.st/RvD (Thanx to torxx (http://forum.xda-developers.com/member.php?u=3828647))
After u've installed the drivers and extracted the adb file do the folowing
Turn off your phone completly
Push Vol down & Power ...device will start
Navigate with vol+- to fastboot press power
connect with usb-cable (possible that windows will install drivers...wait till its complete)
now "fastboot usb" should be read in the display of your phone
open a shell (cmd)
navigate to your fastboot.exe
type: "fastboot oem get_identifier_token"
it seems, that my htc firmware is far too old (3.15.405.3). i installed all the stuff on my win7 laptop instead of win8 desktop pc and could install the RUU... at least untill the notification, that i needed to update the firmware first, and update hboot1.02 (3.30.0.0) afterwards. the big update is also 150MB, the small one only 5MB. i'll give it a try and report back here, if i am able to manage all the stuff^^
btw autoupdating via options doesn't work ("phone is up to date"). do i have to sign in via google to get a better result?
I managed to unlock the bootloader!
The solution was a too old version. My phone had version 3.15.405.3.
First I updated to version 3.15.405.6 (found via google here at xda-dev).
Then I patched the new ROM I downloaded from htc-dev (step 0 at unlocking; must connect phone for that hint!) 3.30.0.0.
Then I could receive the token via CMD at a Windows 7 PC (Win8 PC still said "waiting for device", obviously because the driver wasn't installed correctly so the phone wasn't recognised in fastboot mode).
I followed the last steps rom htc-dev and now unlocked the bootloader
now i will try the rest Thanks for the helpful hints!
AW: [solved] Difficulties with unlocking the Bootloader
Okay nice to hear that it now works:thumbup:
I would say... Have fun while flashing and trying new roms
Sent from my HTC One using xda app-developers app
esco27 said:
Okay nice to hear that it now works:thumbup:
I would say... Have fun while flashing and trying new roms
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Already flashed CM10.1 It's not as smooth as on my Ainol Aurora 2 Tablet, but the Legend hasn't got the power by far. But if you have a look at the specs, it is amazing, how good it runs on the legend
Thanks for all the help! That was definately worth it^^ I only have minor problems with my SIM-card up to now.
Hey guys, i'm new to the nexus world, i've had a Nexus 7 but I never rooted it.
I just got an LTE Nexus 9 and want to root it and flash TWRP. I'm using WinDroid. The problem is, i never get prompted to accept ADB permissions. Coming from a Samsung phone, when i check USB debugging, I automatically get a popup menu on my phone asking me with I want to give this PC permissions to use ADB. On my nexus 9, nothing happens. I see in Device manager that my nexus is connected under Android ADB Interface, and I know my drivers are installed, but WinDroid doesnt see my device, it's always offline.
Anybody know what could be the issue?
polish_pat said:
Hey guys, i'm new to the nexus world, i've had a Nexus 7 but I never rooted it.
I just got an LTE Nexus 9 and want to root it and flash TWRP. I'm using WinDroid. The problem is, i never get prompted to accept ADB permissions. Coming from a Samsung phone, when i check USB debugging, I automatically get a popup menu on my phone asking me with I want to give this PC permissions to use ADB. On my nexus 9, nothing happens. I see in Device manager that my nexus is connected under Android ADB Interface, and I know my drivers are installed, but WinDroid doesnt see my device, it's always offline.
Anybody know what could be the issue?
Click to expand...
Click to collapse
What is windroid? To root do this:
1. Enable developer options.
2. In developer options enable oem unlock
3. If you don't have fastboot set up on your pc Google 15 second adb install xda
4. Unlock your bootloader if it isn't already, fastboot oem unlock
5. Flash twrp onto your device, fastboot flash recovery twrp.img
6. Flash supersu in twrp
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
What is windroid? To root do this:
1. Enable developer options.
2. In developer options enable oem unlock
3. If you don't have fastboot set up on your pc Google 15 second adb install xda
4. Unlock your bootloader if it isn't already, fastboot oem unlock
5. Flash twrp onto your device, fastboot flash recovery twrp.img
6. Flash supersu in twrp
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Windroid is an easy to use universal toolkit. it basically automates the Unlock/root/recovery process. You can find more details here: http://forum.xda-developers.com/nexus-9/development/tool-windroid-universal-android-toolkit-t2984544
As for my issue, i have solved it checking in other threads, i have to set tablet to Camera USB mode, then it asks for RSA authentification right away. Thanks for your help anyways,
polish_pat said:
Windroid is an easy to use universal toolkit. it basically automates the Unlock/root/recovery process. You can find more details here: http://forum.xda-developers.com/nexus-9/development/tool-windroid-universal-android-toolkit-t2984544
As for my issue, i have solved it checking in other threads, i have to set tablet to Camera USB mode, then it asks for RSA authentification right away. Thanks for your help anyways,
Click to expand...
Click to collapse
Nah, I prefer to use fastboot. I can do it faster and I know what it's doing. Glad you got your device working though.
Sent from my Nexus 9 using XDA Free mobile app
My tool worked well for unlocking bootloader but it failed to install recovery and root, I think this might be because Platform Tools was not installed. I ended up doing it manually via command line. Worked perfect. Thanks for your input