Hi,
I followed this article -> phandroid DOT com/2014/11/05/how-to-root-nexus-9/ (Sorry, new account, can't link) to the letter, and everything seemed to go well, until the last step where I ran "fastboot reboot" which returned "error: device not found" I thought nothing of this as there was a reboot option on the devices screen, so I rebooted, I get the google logo, followed by the four orbs, then it says "Optimising app x of 99" once this is done, its back to the orbs again and it just repeats.
I tried restoring to factory defaults from the recovery menu, that did nothing, then sometime after I noticed I actually cant turn the device off any more, if I hold the power button it turns off, but reboots instantly. I tried going through the steps again, but no luck, the only change was that I didn't have the error at the end, and the first Optimising dialogue said 104 apps, not 99, but all the rest afterwards have said 99.
I'm not sure what do do from here, any advice?
Here's my cmd output:
Code:
## First attempt ##
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb
reboot bootloader
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fas
tboot oem unlock
...
(bootloader) ability is 1
(bootloader) RUU_frame_buffer_enable_flag=0
(bootloader) Start Verify: 0
(bootloader) [hboot query] query 24 is not implemented
(bootloader) [hboot query] query 24 is not implemented
(bootloader) Start Verify: 0
(bootloader) [hboot query] query 24 is not implemented
(bootloader) [hboot query] query 24 is not implemented
(bootloader) Unlock device successfully!
OKAY [ 23.489s]
finished. total time: 23.489s
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fas
tboot boot inject.img
cannot load 'inject.img': No such file or directory
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fas
tboot boot nexus9\inject.img
downloading 'boot.img'...
OKAY [ 0.783s]
booting...
OKAY [ 0.156s]
finished. total time: 0.939s
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fas
tboot flash boot nexus9\patched.img
target reported max download size of 518205818 bytes
sending 'boot' (7830 KB)...
OKAY [ 0.541s]
writing 'boot'...
(bootloader) Device State : Unlocked
OKAY [ 0.798s]
finished. total time: 1.339s
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb
reboot
error: device not found
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb
reboot
error: device not found
## Second attempt ##
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fas
tboot oem unlock
< waiting for device >
...
(bootloader) ability is 1
(bootloader) Device stete is unlock already
OKAY [ 0.141s]
finished. total time: 0.141s
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fas
tboot boot inject.img
cannot load 'inject.img': No such file or directory
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fas
tboot boot inject.img
downloading 'boot.img'...
OKAY [ 0.749s]
booting...
OKAY [ 0.158s]
finished. total time: 0.908s
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fas
tboot flash boot patched.img
target reported max download size of 518205818 bytes
sending 'boot' (7830 KB)...
OKAY [ 0.539s]
writing 'boot'...
(bootloader) Device State : Unlocked
OKAY [ 0.787s]
finished. total time: 1.326s
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fas
tboot reboot
rebooting...
finished. total time: 0.066s
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>
Try returning to stock and trying again. See method 2 of this, http://forum.xda-developers.com/showthread.php?p=58956577
Sent from my Nexus 9 using XDA Free mobile app
That root method is for the old 5.0 Android; it doesn't work anymore with 5.1.1. Go back to stock using jd1639's link, then run Chainfire's Auto-root and you should be good to go. Link is here: https://download.chainfire.eu/595/CF-Root/CF-Auto-Root/CF-Auto-Root-flounder-volantis-nexus9.zip. There's supposedly an update coming in the next week or so to fix the stagefright vulnerability, make sure you do NOT take it in case it does weird things that could cause you to lose root.
(I know it says Volantis and not flounder but the Nexus 9 is known by both names, just to keep things confusing)
Thanks guys, root is now all working
Had a strange way of getting there though, I went back to stock, then tried the auto root as mentioned, but I had the same problem again, so I re-flashed just the boot.img file from stock, powered up, and lo and behold, root working fine
TheShryke said:
Thanks guys, root is now all working
Had a strange way of getting there though, I went back to stock, then tried the auto root as mentioned, but I had the same problem again, so I re-flashed just the boot.img file from stock, powered up, and lo and behold, root working fine
Click to expand...
Click to collapse
Your better off doing the bootloader unlock, then flashing TWRP recovery, then flashing supersu. IMO using autoroot methods make no sense. You now have no recovery and if anything goes wrong you have to flash all of the factory images again. And what if you want to use a custom rom? I would highly recommend getting TWRP at http://twrp.me and flashing it. Then you can actually make full backups in case of disaster. Good luck!
bynarie said:
Your better off doing the bootloader unlock, then flashing TWRP recovery, then flashing supersu. IMO using autoroot methods make no sense. You now have no recovery and if anything goes wrong you have to flash all of the factory images again. And what if you want to use a custom rom? I would highly recommend getting TWRP at http://twrp.me and flashing it. Then you can actually make full backups in case of disaster. Good luck!
Click to expand...
Click to collapse
i'll try your TWRP method once i get my LTE version 32gb
link to bootloader unlock method? thx
which version do i use here?
https://dl.twrp.me/flounder/
cobyman7035 said:
i'll try your TWRP method once i get my LTE version 32gb
link to bootloader unlock method? thx
which version do i use here?
https://dl.twrp.me/flounder/
Click to expand...
Click to collapse
Hey, to unlock bootloader you enable developer settings in android, check the "enable oem unlock" switch, boot the device into fastboot mode "adb reboot fastboot" and issue "fastboot oem unlock". This is assuming you have adb and fastboot in your path/working folder. Then, download the lastest twrp - flounder-2.8.7.0.img - and "fastboot flash recovery flounder-2.8.7.0.img". The flounder version of twrp works for both LTE and WIFI variants. If you need any more assistance just let me know.
cobyman7035 said:
i'll try your TWRP method once i get my LTE version 32gb
link to bootloader unlock method? thx
which version do i use here?
https://dl.twrp.me/flounder/
Click to expand...
Click to collapse
bynarie said:
Hey, to unlock bootloader you enable developer settings in android, check the "enable oem unlock" switch, boot the device into fastboot mode "adb reboot fastboot" and issue "fastboot oem unlock". This is assuming you have adb and fastboot in your path/working folder. Then, download the lastest twrp - flounder-2.8.7.0.img - and "fastboot flash recovery flounder-2.8.7.0.img". The flounder version of twrp works for both LTE and WIFI variants. If you need any more assistance just let me know.
Click to expand...
Click to collapse
Just take notice that this will wipe everything on your device, so make a backup first.
dictionary said:
Just take notice that this will wipe everything on your device, so make a backup first.
Click to expand...
Click to collapse
cobyman7035 said:
...
Click to expand...
Click to collapse
Yes, my apologies... I forgot to mention this. You will definitely want to pull any pictures or other files you might want to keep from the /sdcard partition. Or anything else because ALL DATA WILL BE WIPED.
thx. where do i dload the latest SU chainfire? after i flash twrp, then flash SU? do i need to wipe dalvik or cache?
im installing that huge android SDK studio setup into my laptop for prep
cobyman7035 said:
thx. where do i dload the latest SU chainfire? after i flash twrp, then flash SU?
Click to expand...
Click to collapse
Here > https://download.chainfire.eu/740/SuperSU/BETA-SuperSU-v2.49.zip
ok i just unlocked my bootloader....so i rebooted in android again...i have to go back and enable usb debugging and developers again?
---------- Post added at 10:16 AM ---------- Previous post was at 10:01 AM ----------
when i typ adb reboot fastboot. ...my n9 reboots into the android o.s and NOT into fastboot?
---------- Post added at 10:23 AM ---------- Previous post was at 10:16 AM ----------
nm i installed and flash twrp and SU! i didn't do a dalvik cache wipe...is that ok? booting in android o/s again to setup!
my next step is to go unencrypted... don't wanna setup too many apps cuz its just gonna be all deleted again
I am trying to flash twrp or any custom recovery image so that I could root my LGv10, I am running Android 6.0.
When I boot my phone into fastboot mode I dont get the fastboot options just the options to exit or restart. However I still can run commands through adb, I try running the command to flash the custom image and I keep getting this.
Code:
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (5158 KB)...
OKAY [ 0.160s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.185s
If I try to start up in recovery mode I get an android with a red error triangle, preventing me from rooting. Is there anyway I can fix this? any help will be appreciated as I've looked already and cannot seem to find a fix to this problem.
Hi, which model of the V10 do you own?
Please note that bootloader unlock and installation of a custom recovery is only officially supported on the T-Mobile Version of the V10 and the European V10 with the model number H960A. On the H960A you need to unlock your bootloader first. Otherwise flasing recovery fails.
cyvr1 said:
Hi, which model of the V10 do you own?
Please note that bootloader unlock and installation of a custom recovery is only officially supported on the T-Mobile Version of the V10 and the European V10 with the model number H960A. On the H960A you need to unlock your bootloader first. Otherwise flasing recovery fails.
Click to expand...
Click to collapse
Thanks for the reply!
My LGv10 is the T-Mobile version, model number LG-H901. I'm running Marshmallow 6.0, My bootloader is unlocked I'm still getting the same problem.
Not sure what to try anymore
Same exact issue I have. Don't know what else to do.
I was getting that yesterday, though I found another method that seems to have worked, only issue with that one is that whenever I try I flash a ROM, it fails with error 7.
https://dottech.org/198032/how-to-root-lg-v10-t-mobile-h901-on-android-6-0-marshmallow/
This was the method I used, though I didn't do it properly since I couldn't figure out what to do with the kdz file. But I do have TWRP recovery installed to my phone now.
Hi all,
Today I tried to root my LG G5 H830 but with an older method for Marshmallow(in the video i was watching the version wasn't even specified so I was unaware and I believed that the version of the phone did not really matter). I proceeded to follow this man's instructions @: "How to Root T-Mobile LG G5!" by "Max Lee" on Youtube(as a new user i cannot post links ) I unlocked my bootloader, got drivers and followed his instructions up onto an error on LGUP. Basically the error's purpose was to tell me that Nougat is not supported. So I had no choice but to reboot my phone and go through the android initializing setup.
After realizing the error of my ways I then found this post here via Google Search: "Install TWRP Recovery and Root LG G5 on Android Nougat | DroidViews" to install TWRP. Now my bootloader is unlocked and I have no root. The only problem here is that whenever I go into developer options and try to toggle 'OEM unlock' on it won't let me. The OEM unlock setting is grey-ed out and I am unable to toggle it!! This is what I need help with! Although my bootloader is very much infact unlocked I think some error occurred to where now I cant toggle my OEM unlock thus I am unable to flash a TWRP recovery via fastboot!
If I reboot into my bootloader and run the command "fastboot flash recovery recovery.img" i get this:
Code:
target reported max download size of 536870912 bytes
sending 'recovery' (18668 KB)...
OKAY [ 0.419s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.435s
I even ignored the error and tried to boot into recovery manually and i just get the stock recovery.
Please help me guys
What about locking the bootloader again and unlocking it after that with the newer video you used?
MAGNVM said:
Hi all,
Today I tried to root my LG G5 H830 but with an older method for Marshmallow(in the video i was watching the version wasn't even specified so I was unaware and I believed that the version of the phone did not really matter). I proceeded to follow this man's instructions @: "How to Root T-Mobile LG G5!" by "Max Lee" on Youtube(as a new user i cannot post links ) I unlocked my bootloader, got drivers and followed his instructions up onto an error on LGUP. Basically the error's purpose was to tell me that Nougat is not supported. So I had no choice but to reboot my phone and go through the android initializing setup.
After realizing the error of my ways I then found this post here via Google Search: "Install TWRP Recovery and Root LG G5 on Android Nougat | DroidViews" to install TWRP. Now my bootloader is unlocked and I have no root. The only problem here is that whenever I go into developer options and try to toggle 'OEM unlock' on it won't let me. The OEM unlock setting is grey-ed out and I am unable to toggle it!! This is what I need help with! Although my bootloader is very much infact unlocked I think some error occurred to where now I cant toggle my OEM unlock thus I am unable to flash a TWRP recovery via fastboot!
If I reboot into my bootloader and run the command "fastboot flash recovery recovery.img" i get this:
Code:
target reported max download size of 536870912 bytes
sending 'recovery' (18668 KB)...
OKAY [ 0.419s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.435s
I even ignored the error and tried to boot into recovery manually and i just get the stock recovery.
Please help me guys
Click to expand...
Click to collapse
Did you try to run the terminal/cmd as an administrator/root?
Sent from my LG-H840 using Tapatalk
Hi all,
Today I tried to root my LG G5 H830 but with an older method for Marshmallow(in the video i was watching the version wasn't even specified so I was unaware and I believed that the version of the phone did not really matter). I proceeded to follow this man's instructions @: "How to Root T-Mobile LG G5!" by "Max Lee" on Youtube(as a new user i cannot post links ) I unlocked my bootloader, got drivers and followed his instructions up onto an error on LGUP. Basically the error's purpose was to tell me that Nougat is not supported. So I had no choice but to reboot my phone and go through the android initializing setup.
After realizing the error of my ways I then found this post here via Google Search: "Install TWRP Recovery and Root LG G5 on Android Nougat | DroidViews" to install TWRP. Now my bootloader is unlocked and I have no root. The only problem here is that whenever I go into developer options and try to toggle 'OEM unlock' on it won't let me. The OEM unlock setting is grey-ed out and I am unable to toggle it!! This is what I need help with! Although my bootloader is very much infact unlocked I think some error occurred to where now I cant toggle my OEM unlock thus I am unable to flash a TWRP recovery via fastboot!
If I reboot into my bootloader and run the command "fastboot flash recovery recovery.img" i get this:
Code:
target reported max download size of 536870912 bytes
sending 'recovery' (18668 KB)...
OKAY [ 0.419s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.435s
I even ignored the error and tried to boot into recovery manually and i just get the stock recovery.
Please help me guys
duplicate thread >>> original here https://forum.xda-developers.com/lg-g5/help/help-please-t3601192
thread closed
I am trying to get back to EMUI but so far everythig i tried has failed, so turning to you guys for advice.
this is for a Honor 9 (not lite)
I unlocked bootloader after paying 5 credits to DC unlocker
I flashed RR custom ROM from openKirin
I now want to get back to stock but all methods are failing
Tried dload method but getting error "update failed"
Tried recovery and downloading the firmware with firmware finder and messing with the DNS settings
Tried ADB method but getting the following error
(bootloader) Necessary to unlock FRP!
(bootloader) Navigate to Developer options, and enable "OEM unlock"!
FAILED (remote: 'Command not allowed')
Finished. Total time: 0.024s
my frp in bootloader is showing as locked and my OEM lock status is unlocked
Any help would be grately appreciated.
Have you tried installing the factory recovery rom B368 .. instructions are in the zip file
http://androidhost.ru/6er