Hi guys,
Sorry if this is in the wrong forum. I've searched around but can't find anyone with quite the same issue as myself.
I returned to my desk at work to find that my nexus 7 2013, latest stock Android OS installed, was stuck on the Google logo screen. It was switched on previously and charging via my work PC at the time.
A few points about what is happening with the Nexus:
I can get to the bootloader but it says "E: failed to mount /cache (invalid arguement), E: can't mount /cache recovery log, E: can't open /cache recovery/log..." you get the idea
The third line from the end says "e: failed closing /dev/block/platform/msm_sdcc.1/by-name/misc (i/o error), e: failed to mount cache (invalid arguement).
if I select wipe cache from the bootloader I see the same error
I selected wipe data and this seems to work, before giving me the above error again
I've seen about the Wugfresh and Unified toolkit and I have tried them. But the big problem seems to be that neither my work PC or home laptop detects that my Nexus is plugged into them via USB. If I could solve that I think I'd be able to restore, right?
I'm also really intrigued as to how this happened. I've never rooted this Nexus. The most advanced thing I've done with it is to install Nova Launcher and that was over 6 months ago. Weird how it can just suddenly go wrong.
Any help would be greatly appreciated.
Just to add, with the Wug/Nexus Toolkit I've been through the driver installation program and whilst I can get the ADB Interface driver to install, when I'm in the bootloader the Nexus doesn't show in Device Manager and using the "Soft-bricked" option and then "Flash Stock + Unroot" I get an error that no fastboot device could be found.
Have you checked your control panel inside device manager? Your nexus 7 could be listed as a unknown device under other devices, or listed as a nexus 7.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If so. it's a matter of just installing the right drivers, you can install the official Google drivers and choose the bootloader driver when installing.
http://developer.android.com/sdk/win-usb.html
If you get some compatibility error while installing the drivers, just ignore it and continue.
edit: just noticed your 2nd post. nevermind.
Maverick-DBZ- said:
Have you checked your control panel inside device manager? Your nexus 7 could be listed as a unknown device under other devices, or listed as a nexus 7.
If so. it's a matter of just installing the right drivers, you can install the official Google drivers and choose the bootloader driver when installing.
If you get some compatibility error while installing the drivers, just ignore it and continue.
edit: just noticed your 2nd post. nevermind.
Click to expand...
Click to collapse
Thanks for trying! Yep, nothing shows up if I'm in bootloader mode.
I've installed the adb interface driver and if I reboot the Nexus and leave it for a while *sometimes* an "Android Device" will display in Device Manager.
All the instructions say enable USB debugging, disable MTP but I can't do that because it won't turn on! I am pretty much saying this - "I installed the drivers but it still says ADB/Fastboot device not found! What should I do?" which is a page on wugfresh, but I'm new and can't post links- but even this doesn't cover if the device won't boot at all.
teamcooperuk said:
Thanks for trying! Yep, nothing shows up if I'm in bootloader mode.
I've installed the adb interface driver and if I reboot the Nexus and leave it for a while *sometimes* an "Android Device" will display in Device Manager.
All the instructions say enable USB debugging, disable MTP but I can't do that because it won't turn on! I am pretty much saying this - "I installed the drivers but it still says ADB/Fastboot device not found! What should I do?" which is a page on wugfresh, but I'm new and can't post links- but even this doesn't cover if the device won't boot at all.
Click to expand...
Click to collapse
Ok, I was being dumb.
I was starting up using power+volume up. Realised power+volume down gets me to bootloader and that I was in recovery mode before.
So I used the Wugfresh "Flash Stock and Unroot" option. This seemed to be going well except I get told my bootloader is locked.
The I tried to use the Unlocker tool in Wugfresh. This tells me it can't detect an ADB device, but when I hit cancel the unlock bootloader screen opens. And then hangs when I select unlock!
What can I try next?!
Do you know how to use ADB manually with a dos prompt? Kits are nice and they help a lot, but sometimes they don't work right and get in the way.
Code:
fastboot oem unlock
The above command is what you need to unlock your bootloader. If you see a little lock below the Google logo at startup, you've unlocked your bootloader. You're on a Nexus 7 2013 Wi-Fi right?
If it still freezes when unlocking, you could try opening the tablet and disconnecting the battery for a little bit, and then putting everything back together again. For some reason it seems to work for some people.
Maverick-DBZ- said:
Do you know how to use ADB manually with a dos prompt? Kits are nice and they help a lot, but sometimes they don't work right and get in the way.
Code:
fastboot oem unlock
The above command is what you need to unlock your bootloader. If you see a little lock below the Google logo at startup, you've unlocked your bootloader. You're on a Nexus 7 2013 Wi-Fi right?
If it still freezes when unlocking, you could try opening the tablet and disconnecting the battery for a little bit, and then putting everything back together again. For some reason it seems to work for some people.
Click to expand...
Click to collapse
I don't - do I just open a cmd prompt window, navigate to where fastboot is and run that command with the Nexus connected via USB and in the bootloader?
I tried an alternative toolkit, the unified one. The UI of that is a cmd prompt window. That shows me that it hangs during the unlock bootloader process where it is "erasing user data", I left it for 8 hours overnight and it was still hanging.
Does it sound totally bricked?
teamcooperuk said:
I don't - do I just open a cmd prompt window, navigate to where fastboot is and run that command with the Nexus connected via USB and in the bootloader?
I tried an alternative toolkit, the unified one. The UI of that is a cmd prompt window. That shows me that it hangs during the unlock bootloader process where it is "erasing user data", I left it for 8 hours overnight and it was still hanging.
Does it sound totally bricked?
Click to expand...
Click to collapse
Yes, correct.
As a possible solution, run the below fastboot command. Must be in bootloader menu for this to work. See image below.
Code:
fastboot format cache
Then boot to recovery and do a factory reset.
If it still hangs, try downgrading to a lower android version, 4.3 is a good start. If the process fails, post on what step it failed.
Maverick-DBZ- said:
Yes, correct.
As a possible solution, run the below fastboot command. Must be in bootloader menu for this to work. See image below.
Code:
fastboot format cache
Then boot to recovery and do a factory reset.
If it still hangs, try downgrading to a lower android version, 4.3 is a good start. If the process fails, post on what step it failed.
Click to expand...
Click to collapse
I'm getting an error when I try to run these commands. It complains that ADBwinAPI.dll isn't installed. Tryed using regsvr32 to do so but that also gives me an error.
Trying to use Eclipse to run these commands now but it looks like this could be a wormhole of settings beyond my technical ability!
Just to add, I tried to format the cache using the power+volume up screens. I just get the cache errors listed in the original post.
Maverick-DBZ- said:
Yes, correct.
As a possible solution, run the below fastboot command. Must be in bootloader menu for this to work. See image below.
Code:
fastboot format cache
Then boot to recovery and do a factory reset.
If it still hangs, try downgrading to a lower android version, 4.3 is a good start. If the process fails, post on what step it failed.
Click to expand...
Click to collapse
teamcooperuk said:
I'm getting an error when I try to run these commands. It complains that ADBwinAPI.dll isn't installed. Tryed using regsvr32 to do so but that also gives me an error.
Trying to use Eclipse to run these commands now but it looks like this could be a wormhole of settings beyond my technical ability!
Just to add, I tried to format the cache using the power+volume up screens. I just get the cache errors listed in the original post.
Click to expand...
Click to collapse
Ok, found the adb client in the platform-tools sdk directory. Running the unlock I get the same problem, the hang on erasing userdata:
Code:
C:\Users\xxxxxxxx\Documents\Google_Drivers\adt-bundle-windows-x86_64-20140702\sdk\pl
atform-tools>fastboot oem unlock
...
(bootloader) Unlocking bootloader...
(bootloader) erasing userdata...
Just kicked off the erasing cache command...looks like that's hanging too after 30 seconds....should finsih pretty quickly, right?
Off to Asus I go I think!
No need to run the bootloader command. If it still hangs after the below command and nothing else, then it's time to call Asus and RMA it. :crying:
Code:
fastboot format cache
Part of your NAND is likely toast and why the cache partition won't erase.
Related
So today I had a problem with an app not opening correctly so I rebooted the device. The device was stuck in the kit kat boot sequence. I turned it off and charged it. Tried booting to no avail. So I go into stock recovery mode and wiped cache and then proceeded to wipe/factory reset. It then got stuck on factory reset. I let it sit there on the charger for awhile and it was still stuck on factory reset. So i rebooted to attempt again. Now it won't even go into recovery mode. It'll boot to the fastboot screen but when trying to go into recovery it gets stuck on the white Google logo. Is there anything I can do or do I need to send it back? I bought it in July-ish so it should still be on warranty.
It should be easy to restore the stock ROM. Do you have the device drivers installed and a copy of fastboot?
http://developer.android.com/sdk/win-usb.html
http://www.xda-developers.com/andro...ng-fast-adb-fastboot-and-driver-installation/
Boot your Nexus 7 to the fastboot screen, then connect it to your PC. Open a command prompt window with administrator privileges, cd to the fastboot directory (let me know if you need help here), then type the following commands:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
This will wipe everything on your Nexus 7, preparing it for a full flash of the stock recovery and ROM. You can download the stock ROM from here, and there's a "flash-all.bat" file inside that will restore recovery and the ROM all by itself.
https://developers.google.com/android/nexus/images#razor
Pandae said:
It should be easy to restore the stock ROM. Do you have the device drivers installed and a copy of fastboot?
http://developer.android.com/sdk/win-usb.html
http://www.xda-developers.com/andro...ng-fast-adb-fastboot-and-driver-installation/
Boot your Nexus 7 to the fastboot screen, then connect it to your PC. Open a command prompt window with administrator privileges, cd to the fastboot directory (let me know if you need help here), then type the following commands:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
This will wipe everything on your Nexus 7, preparing it for a full flash of the stock recovery and ROM. You can download the stock ROM from here, and there's a "flash-all.bat" file inside that will restore recovery and the ROM all by itself.
https://developers.google.com/android/nexus/images#razor
Click to expand...
Click to collapse
when trying any commands in adb it says waiting for device and hangs on that.
Use adb if your tablet is booted into Android, and use fastboot if you're only at the bootloader.
Do you have the drivers installed? At a command prompt (again must be administrator permissions), type "fastboot devices" and see if it gives a response.
Pandae said:
Use adb if your tablet is booted into Android, and use fastboot if you're only at the bootloader.
Do you have the drivers installed? At a command prompt (again must be administrator permissions), type "fastboot devices" and see if it gives a response.
Click to expand...
Click to collapse
fastboot devices does nothing. I am in the fastboot directory. I thought I had the drivers installed, but in device manager it shows up as Android with an exclamation mark
OK, that explains it. Delete the driver by hitting Del, and just to be safe, click "View" at the top, then select to show hidden devices. Delete anything else that might be for any Android devices. Then install the drivers I linked to. They're generic drivers that work with either Nexus 7 generation, plus other Nexus devices.
Pandae said:
OK, that explains it. Delete the driver by hitting Del, and just to be safe, click "View" at the top, then select to show hidden devices. Delete anything else that might be for any Android devices. Then install the drivers I linked to. They're generic drivers that work with either Nexus 7 generation, plus other Nexus devices.
Click to expand...
Click to collapse
ok done now fastboot devices shows something, typed in fastboot erase boot and it says erasing boot...seems like it is stuck on this command
wildside84 said:
ok done now fastboot devices shows something, typed in fastboot erase boot and it says erasing boot...seems like it is stuck on this command
Click to expand...
Click to collapse
Couldn't you just try to boot a recovery IMG?
fastboot boot recovery path/to/recovery.img
That will let you run recovery without flashing it
Sent from my Nexus 7 using Tapatalk 4 Pro
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Erasing boot shouldn't take too long. Hopefully the partition isn't damaged.
SwoRNLeaDejZ, I believe he couldn't get into recovery. For problems like this, I like to erase recovery and everything else anyway, especially since flash-all.bat will restore stock recovery as part of the process.
Pandae said:
Erasing boot shouldn't take too long. Hopefully the partition isn't damaged.
SwoRNLeaDejZ, I believe he couldn't get into recovery. For problems like this, I like to erase recovery and everything else anyway, especially since flash-all.bat will restore stock recovery as part of the process.
Click to expand...
Click to collapse
no commands work. on erase recovery command it says failed command write failed invalid argument
edit: fastboot boot recovery fails also "command write failed unknown error"
edit: i get a lot of fastboot.exe has stopped working errors on windows. redownloaded platform tools and still happens. I'm at a loss I guess I have to get Google to replace it entirely
I may have taken something for granted. Did you unlock the bootloader?
fastboot oem unlock
Pandae said:
I may have taken something for granted. Did you unlock the bootloader?
fastboot oem unlock
Click to expand...
Click to collapse
no and whats funny is I just got done trying that before i read your message. i restarted the device and my computer and just decided to see if it would dirty flash the flash-all.bat and it was actually going through not giving the write errors but did say bootloader is locked. so i typed fastboot oem unlock and the screen popped up on the device to say yes or no. i selected yes and it, again, got stuck for 10-15 minutes on erasing data...rebooted the device, unlock appears to have failed. argh
If you power down and reboot back into the bootloader, it still says unlocked? What if you try unlocking again?
Pandae said:
If you power down and reboot back into the bootloader, it still says unlocked? What if you try unlocking again?
Click to expand...
Click to collapse
it says the bootloader is locked. i am trying again right now. i get to the yes no screen, select yes and on the command prompt it is stuck on erasing userdata
I've never seen it take very long. Let it sit for a while, maybe plug it in and just wait?
Pandae said:
I've never seen it take very long. Let it sit for a while, maybe plug it in and just wait?
Click to expand...
Click to collapse
ill let it sit, but i think there is something wrong with the device. i had a similar prob with a gs2 and it wouldnt erase or write anything to partition. would usb debugging have to have already been enabled? i cant remember if that was checked or not. or does that matter?
USB debugging is necessary for connecting once the tablet has booted into Android, but it isn't needed for fastboot and the bootloader level. At this point I fear there's more corruption than can be fixed, but let's wait a little while and see.
Pandae said:
USB debugging is necessary for connecting once the tablet has booted into Android, but it isn't needed for fastboot and the bootloader level. At this point I fear there's more corruption than can be fixed, but let's wait a little while and see.
Click to expand...
Click to collapse
Just received an email from Google support. They are unwilling to help because I purchased the device from Best Buy rather than Google Play...WTH? Best Buy won't help either I won't even bother. At this point I'll have to hope Asus will take it in for repair. That kind of bummed me out about Google. Not sure if I want to buy another nexus device again now.
wildside84 said:
no commands work. on erase recovery command it says failed command write failed invalid argument
edit: fastboot boot recovery fails also "command write failed unknown error"
edit: i get a lot of fastboot.exe has stopped working errors on windows. redownloaded platform tools and still happens. I'm at a loss I guess I have to get Google to replace it entirely
Click to expand...
Click to collapse
use usb jig and flash via odin nice work :good:
wildside84 said:
Just received an email from Google support. They are unwilling to help because I purchased the device from Best Buy rather than Google Play...WTH? Best Buy won't help either I won't even bother. At this point I'll have to hope Asus will take it in for repair. That kind of bummed me out about Google. Not sure if I want to buy another nexus device again now.
Click to expand...
Click to collapse
Is Google writing the book "How Not to Stand Behind Your Product"? Sheesh!
Sorry I couldn't be of more help. Good luck and speedy repairs to you. I must admit that with the touchscreen problems, and that it took someone who isn't a Google employee to fix it for a lot of people, all while Google is still silent, I myself don't care to buy another product by Google and/or Asus.
---------- Post added at 12:24 AM ---------- Previous post was at 12:18 AM ----------
VerlyAnanda said:
use usb jig and flash via odin nice work :good:
Click to expand...
Click to collapse
Odin is for Samsung devices, unless something's happened I didn't hear about.
I am such a noob and suck at rooting.I got problem during rooting my kindle fire,here's the stories.I try to search all the way in the forum. But,all of it not working. Could you guys help me ?
1) follow root instruction and downloaded KFU
2) successfully installed superuser and go launcher
3) TWRP or CWR or FFF doesn't appear when i reboot back my device to flash custom rom.
4) I tried to run install_driver and run it again and select bootmode menu
5) I choose 3 for recovery.and its brick.luckily i could switch off my kindle.but when i wanna turned it on,its doesnt return to home menu.its stuck at the stock bootloader.
I'm hoping you guys could help me and suggest me the way how to solve it.
I also attach some screen shot of the kindle and my notebooks when i plugged in usb cable in.
Cheers.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
it seems to be in fastboot mode - you have to fix your windows driver for fastboot mode, then you can continue with kfu.
driver (under android phone):
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface
detailed explanation here: http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
b63 said:
it seems to be in fastboot mode - you have to fix your windows driver for fastboot mode, then you can continue with kfu.
driver (under android phone):
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface
detailed explanation here: http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
Click to expand...
Click to collapse
thanks for the advice.I will try it after this and inform you back. Btw, do i need kindle usb cable? for fastboot, since i purchased used kindle so the seller didnt gimme those cable. im currently using sony micro usb cable.
no - every micro usb cable will work
b63 said:
no - every micro usb cable will work
Click to expand...
Click to collapse
i will try to read all of it, try to understand it.and get you know once i already figure it out okay?:cyclops:
i already update my driver.and why in KFU,my device is offline.
21th century apes said:
i already update my driver.and why in KFU,my device is offline.
Click to expand...
Click to collapse
your device seems to be in fastboot mode - you have selected the wrong driver.
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface
normal boot -> adb commands YES -> fastboot commands NO
fastboot -> adb commands NO -> fastboot commands YES
recovery -> adb commands YES -> fastboot commands NO
if the device is in fastboot mode "adb status" is allways "offline".
if you have installed the right driver you can check manually
with "fastboot devices" and "fastboot getvar product".
if you get response to this commands you are good to go.
i finally able to install bootloader and twrp.i thought i never make a mistakes.but unfortunately,during time im backing up stock rom,(nandbackup).i check all the boxes (for the left side) and for right side nothing.its running,when completed.its show huge amount of data (around 780 mb).i really think dat tis is normal for backup.in twrp,and video by tom gt,time for backup for 10 minutes.but me,already 5 hour still stuck in twrp.cant go anywhere.
b63 said:
your device seems to be in fastboot mode - you have selected the wrong driver.
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface
normal boot -> adb commands YES -> fastboot commands NO
fastboot -> adb commands NO -> fastboot commands YES
recovery -> adb commands YES -> fastboot commands NO
if the device is in fastboot mode "adb status" is allways "offline".
if you have installed the right driver you can check manually
with "fastboot devices" and "fastboot getvar product".
if you get response to this commands you are good to go.
Click to expand...
Click to collapse
bro i hope you can help me solve tiz things off.during backup nand.for the first time.its stuck and as i mention previously its stuck 5 hours but for almost 2 days.its still not finish.am i brick my fire?am i miss out something?later i'll attach picture for your preferences.i think when i already booted up kindle fire,its consider no such big issues.maybe for me that not familiar.
21th century apes said:
bro i hope you can help me solve tiz things off.during backup nand.for the first time.its stuck and as i mention previously its stuck 5 hours but for almost 2 days.its still not finish.am i brick my fire?am i miss out something?later i'll attach picture for your preferences.i think when i already booted up kindle fire,its consider no such big issues.maybe for me that not familiar.
Click to expand...
Click to collapse
if you managed to install bootloader and twrp then you are good to go.
you tried to make a backup of the stock firmware and now the twrp is stuck.
i don't know what options you checked, but this should be no problem.
just hold the power button for ~20sec till it turns off and try again.
check only options which exist on your device then the backup should be done in ~10min.
b63 said:
if you managed to install bootloader and twrp then you are good to go.
you tried to make a backup of the stock firmware and now the twrp is stuck.
i don't know what options you checked, but this should be no problem.
just hold the power button for ~20sec till it turns off and try again.
check only options which exist on your device then the backup should be done in ~10min.
Click to expand...
Click to collapse
Thank you dude.Finally im able to use custom rom.oh,yeah .Btw,i got one last question.Why i cant connect my kindle with computer.instead its show my kindle,its only charging.coz i need to backup all my stuff inside my kindle to computer.
21th century apes said:
Thank you dude.Finally im able to use custom rom.oh,yeah .Btw,i got one last question.Why i cant connect my kindle with computer.instead its show my kindle,its only charging.coz i need to backup all my stuff inside my kindle to computer.
Click to expand...
Click to collapse
that depends on the rom you used. some have a option to enable this function.
the best advise would be to search or ask in the section of the rom you used.
great that it's working now - much fun with your kf
hey dude.im already killed my kindle fire and now its dead.here the stories :
i try to backup all my stuff to my computer.as what you told me before,i try to follow.pick ROM that have usb debugging option for transfering data.okay done.but when i transferring my data from kindle to pc.(i dunno what happen) accidentally my kindle fire hang and i disconnect all the cable hoping that my kindle fire will be okay.but thats the end of my kindle fire.its failed to boot.just plain black screen.when i plugged in the cable.led light blinking.like normal.red and yellow.but there's nothing i can do.i open up device manager on my pc,instead of android phone appeared during time im connecting my phone with pc,its appeared usb mass storage (code 10).device cant start and load.hope you could guide me.anybody.
all guide will be kindly appreaciated.thanks.
For days now I have been trying to root this HTC Wildfire (NOT Wildfire S) that my dad gave to me (so I take it that this phone is very old), because I need to install Android 2.3 on it to be able to download Skype (the phone is stuck on Android 2.2). However after trying many guides, on this website AND others, I am simply unable to do it, so that is why I am writing this forum post.
This is the HBOOT screen:
(As a new user I can not post any images or links for some reason so I just typed this
*** LOCKED (OOW) ***
BUZZ PVT SHIP S-ON
HBOOT-1.02.0000
MICROP-0622
TOUCH PANEL-ATMEL224_20aa
RADIO-3.35.20.10
Dec 13 2011, 12:08:54
HBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
I have tried so many different things, especially posts on this website, and have so far been unsuccessful, but that may be mainly because I am new to this type of thing.
Any help is appreciated, it seems to me that there is almost no solution, half the links to files I need for this process has turned out to be so old that it is no longer even there.
NurusS said:
I have tried so many different things, especially posts on this website, and have so far been unsuccessful, but that may be mainly because I am new to this type of thing.
Any help is appreciated, it seems to me that there is almost no solution, half the links to files I need for this process has turned out to be so old that it is no longer even there.
Click to expand...
Click to collapse
Hi there, welcome to the forum
Have you tried using my guide to root hboot 1.02.0000? What have you tried already? (Links please ) also what are you getting stuck on/at?
lastly what version of windows are you on?
Sent from my Desire S using Tapatalk
heavy_metal_man said:
Hi there, welcome to the forum
Have you tried using my guide to root hboot 1.02.0000? What have you tried already? (Links please ) also what are you getting stuck on/at?
lastly what version of windows are you on?
Sent from my Desire S using Tapatalk
Click to expand...
Click to collapse
Yes, I have. I spent a lot of time trying to use your method but it simply didn't work
http://forum.xda-developers.com/showthread.php?t=2262345 I take it you mean this post?
I have problems at step 3. When I use the htcdev instructions, when I'm on the RUU it says ERROR[191]: ROM IS NOT SUPPORTED
And after that there is nothing that I can do to continue with your instructions. I am on Windows 8.
NurusS said:
Yes, I have. I spent a lot of time trying to use your method but it simply didn't work
http://forum.xda-developers.com/showthread.php?t=2262345 I take it you mean this post?
I have problems at step 3. When I use the htcdev instructions, when I'm on the RUU it says ERROR[191]: ROM IS NOT SUPPORTED
And after that there is nothing that I can do to continue with your instructions. I am on Windows 8.
Click to expand...
Click to collapse
Okay, windows 8 can have some issues with android development but we "should" ( ) be able to get around them.
to your main issue you do not need to flash the ruu, as you already have the upgraded hboot, so skip that part and move onto getting your unlock token via fastboot.( should it say that you need to download the ruu just to move the web page along then do so, but you dont need that file.) View here for a how to on getting fastboot set up with windows 8 and view here for commonly ran into issues with windows 8. Should you get stuck or need more advice just ask pal
heavy_metal_man said:
Okay, windows 8 can have some issues with android development but we "should" ( ) be able to get around them.
to your main issue you do not need to flash the ruu, as you already have the upgraded hboot, so skip that part and move onto getting your unlock token via fastboot.( should it say that you need to download the ruu just to move the web page along then do so, but you dont need that file.) View here for a how to on getting fastboot set up with windows 8 and view here for commonly ran into issues with windows 8. Should you get stuck or need more advice just ask pal
Click to expand...
Click to collapse
Are you sure? it says S-ON, LOCKED and I'm not sure what you mean by the adb folder (where we put the BUZZ-recovery file), but it seems to work where I put it and is stuck forever at < waiting for device >
What is the problem here?
NurusS said:
Are you sure? it says S-ON, LOCKED and I'm not sure what you mean by the adb folder (where we put the BUZZ-recovery file), but it seems to work where I put it and is stuck forever at < waiting for device >
What is the problem here?
Click to expand...
Click to collapse
Yeah im positive pal. the old hboot never used to say locked. if its sits at waiting for device it means that the device is not connected okay. can you run the command
Code:
adb devices
for me and see if it detects the phone.
Do you have usb debugging enabled?
Did you download the zip file from the forum page?
heavy_metal_man said:
Yeah im positive pal. the old hboot never used to say locked. if its sits at waiting for device it means that the device is not connected okay. can you run the command
Code:
adb devices
for me and see if it detects the phone.
Do you have usb debugging enabled?
Did you download the zip file from the forum page?
Click to expand...
Click to collapse
I ran the command an got this back:
C:\Users\Nurus>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
SH14RPY08821 device
I have USB debugging enabled on my phone.
What zip files are you referring to?
NurusS said:
I ran the command an got this back:
C:\Users\Nurus>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
SH14RPY08821 device
I have USB debugging enabled on my phone.
What zip files are you referring to?
Click to expand...
Click to collapse
Sorry for my delay pal, you seem to have download the correct zip file from the op. Try these commands
Adb reboot bootloader
(The device should reboot into fastboot, highlighted in red at the top, Followed by.)
fastboot oem get_identifier_token
Then highlight the code using right click/mark/ then select it all and right click it again. Post that into the htcdev website.
Sent from my nexus 7 using Tapatalk
heavy_metal_man said:
Sorry for my delay pal, you seem to have download the correct zip file from the op. Try these commands
Adb reboot bootloader
(The device should reboot into fastboot, highlighted in red at the top, Followed by.)
fastboot oem get_identifier_token
Then highlight the code using right click/mark/ then select it all and right click it again. Post that into the htcdev website.
Sent from my nexus 7 using Tapatalk
Click to expand...
Click to collapse
I did what you said, I got <waiting for device> again.
NurusS said:
I did what you said, I got again.
Click to expand...
Click to collapse
When the command prompt states waiting for the device,and you have booted into hboot using the command fastboot reboot boot loader, does the phone say fastboot in red at the top, with options like fastboot reboot and other options in red? Or is it the standard black/blue writing? If its not all red then with the fastboot option highlighted press power once. I will upload pictures of what o mean as soon as I get to my laptop.
heavy_metal_man said:
When the command prompt states waiting for the device,and you have booted into hboot using the command fastboot reboot boot loader, does the phone say fastboot in red at the top, with options like fastboot reboot and other options in red? Or is it the standard black/blue writing? If its not all red then with the fastboot option highlighted press power once. I will upload pictures of what o mean as soon as I get to my laptop.
Click to expand...
Click to collapse
Fastboot is highlighted in red.
NurusS said:
Fastboot is highlighted in red.
Click to expand...
Click to collapse
Sorry for my very delayed response pal, life got in the way.
ok so your hboot looks like this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
yeah like this except yours will say locked and not unlocked at this stage.
So from here open your command prompt from within the adb folder
Then enter this command, copy and pastif prefered.
Code:
fastboot oem get_identifier_token
this should return a large code in the command prompt.
You will then need to Rght click, mark, and then highlight all the code like the htcdev website states.
post that info into the website and they will email you your unlock token.bin
post back on how you get on.
heavy_metal_man said:
Sorry for my very delayed response pal, life got in the way.
ok so your hboot looks like this?
yeah like this except yours will say locked and not unlocked at this stage.
So from here open your command prompt from within the adb folder
Then enter this command, copy and pastif prefered.
Code:
fastboot oem get_identifier_token
this should return a large code in the command prompt.
You will then need to Rght click, mark, and then highlight all the code like the htcdev website states.
post that info into the website and they will email you your unlock token.bin
post back on how you get on.
Click to expand...
Click to collapse
Once again, I just get <waiting for device>
NurusS said:
Once again, I just get <waiting for device>
Click to expand...
Click to collapse
Okay, then your issue is with your fastboot driver. Do you have another computer you can use?
Just install android SDK and jdk and then try to install your drivers as heavy metal man said. I hope this could work..or try to use this
http://forum.xda-developers.com/showthread.php?t=2317790
Sent from my Moto G using XDA Free mobile app
Q&A for [GUIDE][ROOT] Smartwatch 3 KNX01V
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [GUIDE][ROOT] Smartwatch 3 KNX01V. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
HELP!?
XorZone said:
You have been warned!
Links:
Sony PC Companion
SWR50-rootboot.img@ mega.nz, md5 summ: e2c34b07faa415a6cbb95943649c7eba
Step 1:
Code:
[URL="source.android.com/source/building-devices.html#unlocking-the-bootloader"]Unlocked bootloader[/URL]
1. Enable adb debug
2. adb reboot bootloader
3. fastboot oem unlock (twice if requested)
4. fastboot format cache
5. fastboot format userdata
6. fastboot getvar all (and verify that it is)
7. fastboot reboot
Step 2:
Code:
Updated to the latest KNX01V
[URL="http://www.sonymobile.com/us/tools/pc-companion/"]Install Sony PC Companion[/URL] and use Supports Zone -> Accessories software update -> Smartwatch 3
Step 3:
Code:
Have Flashboot (Sony s1 flash) drivers installed just in case (Install Sony PC Companion and do update as indicated in previous step)
Step 4:
Code:
[COLOR="red"]BOOT [/COLOR][COLOR="Red"](DO NOT EVER FLASH IT!!!)[/COLOR] rooting boot.img
1. Download rooting kernel image (SWR50-rootboot.img)
2. Reboot into bootloader (adb reboot bootloader)
3. fastboot boot SWR50-rootboot.img
4. Wait till device reboots or sits in black screen for a while (1 min+ then reboot it by holding power 10+sec)
Step 5:
Code:
Verify by:
1. adb shell
2. su
3. you should see [email protected]:/ #
Step 6:
Code:
1. Let me know!
2. Use it, dive into GPS investigation or customizations, etc.....
Special thanks:
1. Justin Case for LG G Watch rooting method using LGGW-rootboot.img
2. osm0sis for Android Image Kitchen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
I've been following directions from here and from the lggw tutorial with no success. I get fast boot running on the watch but after typing "Fastboot oem unlock" the command terminal stays on "waiting for device". Could you help me please?
13noninja said:
I've been following directions from here and from the lggw tutorial with no success. I get fast boot running on the watch but after typing "Fastboot oem unlock" the command terminal stays on "waiting for device". Could you help me please?
Click to expand...
Click to collapse
Sounds like your'e missing the right drivers. I'm sorry I don't have a link right now but it should be somewhere on the OP.
13noninja said:
I've been following directions from here and from the lggw tutorial with no success. I get fast boot running on the watch but after typing "Fastboot oem unlock" the command terminal stays on "waiting for device". Could you help me please?
Click to expand...
Click to collapse
1. Download and install google usb driver: http://developer.android.com/sdk/win-usb.html
2. Check if you have adb driver in place: adb devices, if not - go into Device Manager and force missing driver to be "Android Composite ADB Interface".
To force it "Update Driver" -> "Browse My Computer" -> "Let me pick from a list ..." -> Select "Google, Inc." on left and "Android Composite ADB Interface" on the right.
Verify that you have adb access, by typing "adb devices", if needed confirm connection on the phone
3. Reboot to bootloader by typing "adb reboot bootloader", you should see "Running Fastboot" on watch screen.
4 Check "fastboot devices", you should see device id followed by fastboot word.
If not - go into Device Manager and force missing driver to be "Android Bootloader Interface" by followinf instructions for adb, but make sure to pick "Google, Inc." on left and "Android Bootloader Interface" on the right.
5. Verify fastboot working by executing fastboot devices.
6. Follow guide.
Got It
Thx XorZone and nobunnysapro, i found the missing drivers and got everything running smoothly.
I can not get my device to show up in adb devices and its driving me crazy. Tried windows 7/8/server 2012R2 ..lol
Now I have done my fair share of custom roms and bootloaders.
OG Droid
Nexus
Nexus 10
Asus Memo Pad (came from alarm company, and could only load one app...now its a full running tablet)
I am sure its a silly thing I have done or am missing...
Thoughts....ideas?..need more info?
Oh and ADB Debugging is on
I can't seem to get it working..
I have the drivers and ADB works fine, i can sideload stuff to watch and install apk and everything.
But when I write "adb reboot boatloader" it does just normal reboot. Can't get into fastboot mode.
Orvils said:
I can't seem to get it working..
I have the drivers and ADB works fine, i can sideload stuff to watch and install apk and everything.
But when I write "adb reboot boatloader" it does just normal reboot. Can't get into fastboot mode.
Click to expand...
Click to collapse
boatloader? I do not think sony included boat on board... JK
correct one is
Code:
adb reboot bo[B]o[/B]tloader
XorZone said:
boatloader? I do not think sony included boat on board... JK
correct one is
Code:
adb reboot bo[B]o[/B]tloader
Click to expand...
Click to collapse
Sorry, misspelled. But in terminal I am writing everything correctly. Not sure why it doesn't go into fastboot.
Sent from my SM-N910F using Tapatalk
Orvils said:
Sorry, misspelled. But in terminal I am writing everything correctly. Not sure why it doesn't go into fastboot.
Sent from my SM-N910F using Tapatalk
Click to expand...
Click to collapse
1. Are you doing it through USB connection and not over bluetooth?
2. What is your current build number/version in about menu?
Yes I'm doing everything with USB connection.
Build number is KNX01V
Sent from my SM-N910F using Tapatalk
Orvils said:
Sorry, misspelled. But in terminal I am writing everything correctly. Not sure why it doesn't go into fastboot.
Click to expand...
Click to collapse
Always check if adb in general works (may be driver probs in Win):
Code:
adb devices -l
(That's a lowercase L)
A guide for relocking the boot loader? I'm looking to go to lollipop for wear so I'd like to know how to go back to stock.
Fastboot OEM lock, and better reflash using Sony companion before.
I plan to try to get ota as is, then if it'll not work reflash using companion and then if it is still not upgrades I'll relock as last resort.
I have reinstalled Google USB drives over and over again manually and through SDK... When I try to manually point it to the right drivers I don't even get offered the right drivers.. I have google inc. Selected on the left but I dont see android composite or android bootloader interface...help would be much appreciated
Hello, any idea to make it work on lollipop? Thanks!
I have Sony Smartwatch 3 and want to install normal APK via Sideload and USB/PC (do not want to root my smartphone).
Is this possible and which SW i need to install on Windows PC?
Step by step guide (for noobs) would be great. Thanks
Gesendet von meinem SM-T310 mit Tapatalk
/Users/sekhon/Desktop/Brick Phone.jpg
Hi,
My HTC M8 (which i have not used for a year) seems to have been cricked to what ever extent !
I put it on charge and the following shows up
________________________________________
*** Software status: Modified ***
*** Locked ***
M8_UL PVT Ship S-ON
(few other lines)
FastBOOT AC
<vol up. to previous item>
<vol down> to next item>
<power> to select item
HBOOT
RAMDUMP
REBOOT
REBOOT FASTBOOT
POWER DOWN
no matter what i do it just ends up here and doesn't really startup,
I had aSD Card in the phone and removed it and tried to restart but no luck!
Any help would be highly appreciated !
saint4mbuddapest said:
no matter what i do it just ends up here and doesn't really startup,
Click to expand...
Click to collapse
So what did you try to do? The above doesn't tell us anything you tried or didn't try (aside from removing the SD card).
Don't want to waste the time and effort, to advise you to do things you may have already tried.
Hello,
Thanks for the reply!
I tried to connect it to my mac via usb to flash a rom or twrp etc but my computer doesn't show the phone.
I tried selecting the recovery mode from the menus and nothing happens.
It just restarts and goes back to the same mode.
So honestly i havnt tried much as i do not know where to begin.. Apart from going into all of the menus on the screen and that's it.
I think i the phone is missing the recovery and the rom? Not sure.... Help!
saint4mbuddapest said:
I tried to connect it to my mac via usb to flash a rom or twrp etc but my computer doesn't show the phone.
Click to expand...
Click to collapse
The mac will only be able to connect via fastboot, in the current condition. Do you have fastboot/adb setup on your mac? I'm not a mac user, so I won't be able to advise much on that.
saint4mbuddapest said:
I think i the phone is missing the recovery and the rom? Not sure.... Help!
Click to expand...
Click to collapse
Since the phone will only boot to bootloader, you are correct in that it appears the ROM is damaged or corrupt. Since I don't think the Rogers version has RUU to recover, you are right in the approach of flashing TWRP and ROM to the phone.
However, you will also need to unlock the bootloader, in order to flash TWRP. And you will need working fastboot connection to mac/PC in order to unlock bootloader and flash TWRP. So you really need to troubleshoot the connection issue, first.
You might also read through the following thread for more recovery options or info: https://forum.xda-developers.com/showthread.php?t=2694297
redpoint73 said:
Since I don't think the Rogers version has RUU to recover
Click to expand...
Click to collapse
On post #1 OP wrote (few other lines) which is important to be highlighted. Without OS info no way to help.
Or as usual need fastboot getvar all result. If it is Lollipop RUU 4.20.631.3 is available for free.
Also I remember Marshmallow RUU is available too on AFH but can't confirm it now as I maybe wrong ..need to search for it
Edit : here is Marshmallow RUU - http://gsm-firmware.com/index.php?a=browse&b=file-info&id=14070
Leave it to you to guide OP.
Maybe need to flash 6.13.631.7 firmware first before RUU
Thanks!
I just tried the add fast boot connection went through all the steps ok, HOWEVER when i type in ./adb devices it does not show the phone. So far all posts and videos i have found explain about trouble shooting when the phone OS is still running but none for my situation.
There is a red highlights text which says "FASTBOOT"
and it turns to "FASTBOOT USB" when i plug in with my MAC
Also i have tried 2 different USB cables same result, tried clicking on the "REBOOT FASTBOOT" as well same result.
Anything else i can do to have a working connection ?
redpoint73 said:
The mac will only be able to connect via fastboot, in the current condition. Do you have fastboot/adb setup on your mac? I'm not a mac user, so I won't be able to advise much on that.
Since the phone will only boot to bootloader, you are correct in that it appears the ROM is damaged or corrupt. Since I don't think the Rogers version has RUU to recover, you are right in the approach of flashing TWRP and ROM to the phone.
However, you will also need to unlock the bootloader, in order to flash TWRP. And you will need working fastboot connection to mac/PC in order to unlock bootloader and flash TWRP. So you really need to troubleshoot the connection issue, first.
You might also read through the following thread for more recovery options or info: https://forum.xda-developers.com/showthread.php?t=2694297
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/IMG]
http://i65.tinypic.com/254x8g0.jpg
<img src="http://i65.tinypic.com/254x8g0.jpg" border="0" alt="Image and video hosting by TinyPic">
saint4mbuddapest said:
Thanks!
I just tried the add fast boot connection went through all the steps ok, HOWEVER when i type in ./adb devices it does not show the phone. So far all posts and videos i have found explain about trouble shooting when the phone OS is still running but none for my situation.
There is a red highlights text which says "FASTBOOT"
and it turns to "FASTBOOT USB" when i plug in with my MAC
Also i have tried 2 different USB cables same result, tried clicking on the "REBOOT FASTBOOT" as well same result.
Anything else i can do to have a working connection ?
Click to expand...
Click to collapse
Have you installed the HTC drivers to your computer?
If not, install HTC Sync Manager (you can get the MAC version here). During the installation of Sync Manager the drivers will be installed. After they are, Uninstall Sync Manager (it doesn't play nice with ADB/fastboot) and the drivers will remain
xunholyx said:
Have you installed the HTC drivers to your computer?
If not, install HTC Sync Manager (you can get the MAC version here). During the installation of Sync Manager the drivers will be installed. After they are, Uninstall Sync Manager (it doesn't play nice with ADB/fastboot) and the drivers will remain
Click to expand...
Click to collapse
Just tried that as well, no improvement
saint4mbuddapest said:
I just tried the add fast boot connection went through all the steps ok, HOWEVER when i type in ./adb devices it does not show the phone.
Anything else i can do to have a working connection ?
Click to expand...
Click to collapse
When on fastboot, correct command is fastboot devices or ./fastboot devices
Based on your bootloader screenshot, you can try the above linked RUU to fix your phone
saint4mbuddapest said:
I just tried the add fast boot connection went through all the steps ok, HOWEVER when i type in ./adb devices it does not show the phone. So far all posts and videos i have found explain about trouble shooting when the phone OS is still running but none for my situation.
There is a red highlights text which says "FASTBOOT"
and it turns to "FASTBOOT USB" when i plug in with my MAC
Click to expand...
Click to collapse
This is working normally, and as intended.
adb and fastboot are related, but different conditions, usage and requirements.
adb: Only works in OS, or alternately TWRP. Needs debugging enabled in phone settings. Will not work in fastboot mode.
fastboot: Only works in fastboot mode. Does not require debugging enabled in phone settings.
Stuck in fastboot mode, you should get a response (phone's ID) to: fastboot devices
Otherwise, there may be a driver or USB connectivity issue.
However, since ckpv5 linked an RUU for you to use, the mac won't help you. RUU is probably the easiest way to get the phone back up and running. But you'll need access to a PC for the RUU to work. RUU won't work properly with mac, even emulating a PC.
redpoint73 said:
However, since ckpv5 linked an RUU for you to use, the mac won't help you. RUU is probably the easiest way to get the phone back up and running. But you'll need access to a PC for the RUU to work. RUU won't work properly with mac, even emulating a PC.
Click to expand...
Click to collapse
It's zip format, can use microsd method
ckpv5 said:
It's zip format, can use microsd method
Click to expand...
Click to collapse
Nice. :good: Obviously, I missed that detail. Should have figures, since most M8 versions without "official" released RUUs seem to get them leaked as zip format.