Related
Figured this would cut down on threads and questions. I have made a video showing how to manually update to 4.1.2 (WILL ALSO WORK FOR 4.2, just use the correct file that I link to) on your Nexus 7.
http://www.youtube.com/watch?v=PwlXQoAzrBE
Hope this helps.
Thank you =) will try
-Google
I hope people actually watch and learn from this tutorial instead of waiting around for some point and click tool powered by unicorn blood and hamsters. It's an excellent tutorial and gets you in touch with your device by using the exact tools Google provided you to use for this exact thing.. Use them, they are invaluable.
This means we can't use the old method of putting update.zip file in the root folder and let the system upgrades by itself.
Terrific video but for one problem: My N7 doesn't seem to want to go into Recovery.
Using adb reboot recovery gets me into the red triangle screen, but pressing Power+VolUp just gets the Google logo and pressing all three buttons just restarts it. Something is screwy and I've wasted about three hours on messing with it. I never get the screen shown at 3:41.
If I cold start it by pressing Power+VolUp+VolDn, it brings up a screen with an Android on its back with the body open and a big green Start pointing to the Power button and arrows next to the volume buttons. In the lower left in white computer type is:
FASTBOOT MODE
PRODUCT NAME - grouper
VARIANT - not defined yet
HW VERSION - ER3
BOOTLOADER VERSION - 3.34
BASEBAND VERSION - N/A
SERIAL NUMBER - xxxxxxxxxxx
SIGNING - not defined yet
LOCK STATE - LOCKED
Pressing up or down twice brings up Recovery and pressing Power switches to a Google logo and that's the end of the show.
I followed your "How to install the Android SDK, ADB and Fastboot on your PC" video without a hitch (thank you for that one, too) and I have USB debugging turned on (as proven by adb reboot recovery working), so what the heck is going wrong with getting it past the red triangle screen?
EDIT: I'm bone stock, no root.
DirkBelig said:
Terrific video but for one problem: My N7 doesn't seem to want to go into Recovery.
Using adb reboot recovery gets me into the red triangle screen, but pressing Power+VolUp just gets the Google logo and pressing all three buttons just restarts it. Something is screwy and I've wasted about three hours on messing with it. I never get the screen shown at 3:41.
If I cold start it by pressing Power+VolUp+VolDn, it brings up a screen with an Android on its back with the body open and a big green Start pointing to the Power button and arrows next to the volume buttons. In the lower left in white computer type is:
FASTBOOT MODE
PRODUCT NAME - grouper
VARIANT - not defined yet
HW VERSION - ER3
BOOTLOADER VERSION - 3.34
BASEBAND VERSION - N/A
SERIAL NUMBER - xxxxxxxxxxx
SIGNING - not defined yet
LOCK STATE - LOCKED
Pressing up or down twice brings up Recovery and pressing Power switches to a Google logo and that's the end of the show.
I followed your "How to install the Android SDK, ADB and Fastboot on your PC" video without a hitch (thank you for that one, too) and I have USB debugging turned on (as proven by adb reboot recovery working), so what the heck is going wrong with getting it past the red triangle screen?
Click to expand...
Click to collapse
I have the same exact same problem, except my bootloader is unlocked. Tried everything I could think of, and it still doesn't go into android recovery.
Insert your USB cable and make sure it's plugged into a charger or PC.. Recovery won't appear unless you are plugged in. It's an odd bug fixed when you update
I've been plugged in to both a charger and the PC. Come on, if I've fired off adb recovery reboot, doesn't that automatically suggest that I'm connected to the computer? I press Power+Volume Up and it does NOT instantly go to the screen it should, but brings up a Google logo and sits there forever.
styckx said:
Insert your USB cable and make sure it's plugged into a charger or PC.. Recovery won't appear unless you are plugged in. It's an odd bug fixed when you update
Click to expand...
Click to collapse
Doesn't work in either case, it just hangs until the hard reboot kicks in.
DirkBelig said:
Terrific video but for one problem: My N7 doesn't seem to want to go into Recovery.
Using adb reboot recovery gets me into the red triangle screen, but pressing Power+VolUp just gets the Google logo and pressing all three buttons just restarts it. Something is screwy and I've wasted about three hours on messing with it. I never get the screen shown at 3:41.
If I cold start it by pressing Power+VolUp+VolDn, it brings up a screen with an Android on its back with the body open and a big green Start pointing to the Power button and arrows next to the volume buttons. In the lower left in white computer type is:
FASTBOOT MODE
PRODUCT NAME - grouper
VARIANT - not defined yet
HW VERSION - ER3
BOOTLOADER VERSION - 3.34
BASEBAND VERSION - N/A
SERIAL NUMBER - xxxxxxxxxxx
SIGNING - not defined yet
LOCK STATE - LOCKED
Pressing up or down twice brings up Recovery and pressing Power switches to a Google logo and that's the end of the show.
I followed your "How to install the Android SDK, ADB and Fastboot on your PC" video without a hitch (thank you for that one, too) and I have USB debugging turned on (as proven by adb reboot recovery working), so what the heck is going wrong with getting it past the red triangle screen?
EDIT: I'm bone stock, no root.
Click to expand...
Click to collapse
Omega360 said:
I have the same exact same problem, except my bootloader is unlocked. Tried everything I could think of, and it still doesn't go into android recovery.
Click to expand...
Click to collapse
I had the exact same issues. Turns out, I had to hold my volume button directly in the middle while holding power.
ShannonMS81 said:
I had the exact same issues. Turns out, I had to hold my volume button directly in the middle while holding power.
Click to expand...
Click to collapse
THIS WORKED!!!!!!
OMFG!!! I burned the time I was going to watch the making of Prometheus Blu-ray trying to get this stupid thing to work! Where were you hours ago, man?!?!? Thank you!!! Better late than never.
Glad you got it.. BTW.. I did-misread what you said and yes, you would have had a USB cable in. All these posts are running together of people asking for help and having issues. Mah poor brain is getting em all mixed together.
Nexus 7 needs a coffee maker attachment!
qbking77 said:
Figured this would cut down on threads and questions. I have made a video showing how to manually update to 4.1.2 on your Nexus 7.
http://www.youtube.com/watch?v=PwlXQoAzrBE
Hope this helps.
Click to expand...
Click to collapse
Great video! I might just be using this in the near future. I plan on waiting for the factory image (I just like having a full install on my devices when possible) instead of using just the zip file (that is if I dont get the update). Although if the update isnt showing up sometime soon then this is going to work for me just fine.
qbking77 said:
Figured this would cut down on threads and questions. I have made a video showing how to manually update to 4.1.2 on your Nexus 7.
http://www.youtube.com/watch?v=PwlXQoAzrBE
Hope this helps.
Click to expand...
Click to collapse
can't enterthe stock recovery since i instaled CWM. removing it would bring the stock back ?
for some reason its not working for me. im fully stock, no root, locked bootloader. my pc recognizes N7 adb host and goes into recovery, but when i write the command "adb sideload 03a4eaf95f73.signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip" it doesnt send it and just shows me the help info for adb. any suggestions why?
Thanks in advance
Same issue, when I "adb device" it will sometimes show as "device" and other times as something else (don't recall but not device). I can get into recover via "adb reboot recovery" and then into "update via adb" but when I "adb sideload.....(see above)" it just runs through the different commands as if "sideload" is not an option? Followed the video to a "T" and nothing.....thinking about rooting and doing it the old fashion way but this is the first android device I've had that I've not seen a reason to root right away...maybe should just wait for the OTA?
Ram1500 said:
for some reason its not working for me. im fully stock, no root, locked bootloader. my pc recognizes N7 adb host and goes into recovery, but when i write the command "adb sideload 03a4eaf95f73.signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip" it doesnt send it and just shows me the help info for adb. any suggestions why?
Thanks in advance
Click to expand...
Click to collapse
While in stock recovery and in the "apply update from adb" screen, type in the command window "adb devices". It should say:
<your device serial number> sideload
If it does not, check the drivers in device manager. You may need to manually install it. I had to on mine.
Cheers qbking77, worked a treat.
First time I pushed using adb & after following your tut life is good. Thanks again!
Ram1500 said:
for some reason its not working for me. im fully stock, no root, locked bootloader. my pc recognizes N7 adb host and goes into recovery, but when i write the command "adb sideload 03a4eaf95f73.signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip" it doesnt send it and just shows me the help info for adb. any suggestions why?
Thanks in advance
Click to expand...
Click to collapse
You may be using an older version of adb that does not support the sideload command.
Jwoc12 said:
Same issue, when I "adb device" it will sometimes show as "device" and other times as something else (don't recall but not device). I can get into recover via "adb reboot recovery" and then into "update via adb" but when I "adb sideload.....(see above)" it just runs through the different commands as if "sideload" is not an option? Followed the video to a "T" and nothing.....thinking about rooting and doing it the old fashion way but this is the first android device I've had that I've not seen a reason to root right away...maybe should just wait for the OTA?
Click to expand...
Click to collapse
It should say 8sdgfs3JKSDBFkjk3 device or something like that. If it does not, you need to install the the correct driver.
My computer did not recognize my tablet at first. I went to this thread and installed PDAnet which installed the driver.
http://forum.xda-developers.com/showthread.php?t=1809195
I picked up an M7 with a busted power button and want to root it because, reasons.
I'm on KK 4.4.2 with Sense 6 (use Nova Launcher though) and my kernel version is 3.4.10-gb9492d4 [email protected] #1 SMP PREEMPT
I looked through some similar threads about this for Samsung and Nexus devices and found that I can use 'adb' in cmd on Windows to reboot/boot to recovery and such but when further researching I couldn't find "step 1". Any atempts to do it in cmd came back with errors saying I could not do it due to missing something, or in the case of a GUI assisted Windows tray app I found on XDA(can't remember name), saying no device was detected at all.
I also read some business about having to have "fastboot" enabled but without a power button and a having a metal unibody phone I'm still stuck.
Sorry if this has been covered but I Googled extensively and kept coming back to "but where do I start?" I have rooted a Samsung S3 before but obviously it was a different process considering I have all working buttons on the thing.
Thanks for any help!
Zertonshfits said:
I picked up an M7 with a busted power button and want to root it because, reasons.
I'm on KK 4.4.2 with Sense 6 (use Nova Launcher though) and my kernel version is 3.4.10-gb9492d4 [email protected] #1 SMP PREEMPT
I looked through some similar threads about this for Samsung and Nexus devices and found that I can use 'adb' in cmd on Windows to reboot/boot to recovery and such but when further researching I couldn't find "step 1". Any atempts to do it in cmd came back with errors saying I could not do it due to missing something, or in the case of a GUI assisted Windows tray app I found on XDA(can't remember name), saying no device was detected at all.
I also read some business about having to have "fastboot" enabled but without a power button and a having a metal unibody phone I'm still stuck.
Sorry if this has been covered but I Googled extensively and kept coming back to "but where do I start?" I have rooted a Samsung S3 before but obviously it was a different process considering I have all working buttons on the thing.
Thanks for any help!
Click to expand...
Click to collapse
Ok well assumeing you already have adb/fastboot and the drivers for your Device installed you need Fast boot disabled in power settings. And Usb debugging enabled in developer options.
While the phone is booted to the Android OS go to
Settings>Power at the very bottom is the option "Fast boot" make sure this is disabled. Now go to
Settings>Developer Options and enable "Usb debugging"
Now you should be able to boot recovery from the adb command window with
Code:
adb reboot recovery
Or
adb reboot-bootloader
Be very careful flashing roms though. Make sure your recovery is tested and working with the Rom your going to install. If you end up in a bootloop there's very little chance of rescuing it without functional volume keys
Edit :- P.S if you don't see developer options in your settings menu go to
Settings>About>Software Information>More and tap on the Build Number repeatedly untill it says you are now a developer :good:
Danny201281 said:
Ok well assumeing you already have adb/fastboot and ...
Click to expand...
Click to collapse
Ah ha! The 'assume' part is what gets me.
How to I 'get' adb? I assumed that it was a command baked into cmd.
I do have dev options enabled and my drivers installed. Also to clarify my volume buttons are fine, its my power button that is dead.
I woouuuuld like to try some ROMs but untill I get the button actually fixed ill probably stick to xposed and the like to get more out of it, just in case.
Thanks for the quick reply. Once Im able to boot it into different modes should be just the regular process right? (Unlock BLer, custom recov, bing bang boom?)
Zertonshfits said:
Ah ha! The 'assume' part is what gets me.
How to I 'get' adb? I assumed that it was a command baked into cmd.
I do have dev options enabled and my drivers installed. Also to clarify my volume buttons are fine, its my power button that is dead.
I woouuuuld like to try some ROMs but untill I get the button actually fixed ill probably stick to xposed and the like to get more out of it, just in case.
Thanks for the quick reply. Once Im able to boot it into different modes should be just the regular process right? (Unlock BLer, custom recov, bing bang boom?)
Click to expand...
Click to collapse
See this easy installer and guide for adb/fastboot http://forum.xda-developers.com/showthread.php?t=2317790
:good:
Then you can use fastboot to flash a recovery and install a Rom
Woohoo! Ill post my findings when I get a sec to try it!
Hi All,
I have an HTC one M7 unlocked. Two days ago I tried to restart my phone and it is stuck on the Fast boot /bootloader screen. I tried to use the recovery and Reset Factory options, but these are bringing me back to Fastboot screen. Took my phone to a gadget shop and they said OS has gone. Any idea how to proceed? I am a newbie to this forum and any help would be much appreciated
***LOCKED***
M7_U PVT SHIP S-ON RH
HBOOT-1.57.000
OS-6.13.707.107
eMMC-BOOT 2048M
Jan 7 2015,14:50:53.0
FASTBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER>to select item
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
Unlock the bootloader first then install custom recovery
what's up everyone... got a little question and apologise if it's been asked many times before. my wife loves htc (sense UI) so recently i bought a brand new one for her (M7)... the reason im telling this is the fact that I have already drivers and adb installed on my pc (unlocked, rooted and flashed a rom for her on the second day after buying it) but few days ago I bought another M7 at a good price just to use with mhl-vga converter (as a stationary with Bluetooth keyboard and mouse connected so we wouldn't have to connect her m7 or my s5 all the time back and forth) but the thing is, that volume rocker (the one you actually need to enter a fastboot mode, the Volume Down) - dont work, so my question is, - is it possible to enter a fastboot mode through pc using cmd ? I've read that it is possible but yesterday I connected, opened command window, typed ADB devices just to see if pc recognizes the device and nothing, then typed other commands I found googling... commands for reboot, reboot to fastboot... whatever... so I'm asking is it possible? or the only way to get there is to use power and volume down buttons? thanx.
edit : drivers are all good (updated), adb us on my pc. the device was On (booted).
methoddon1 said:
what's up everyone... got a little question and apologise if it's been asked many times before. my wife loves htc (sense UI) so recently i bought a brand new one for her (M7)... the reason im telling this is the fact that I have already drivers and adb installed on my pc (unlocked, rooted and flashed a rom for her on the second day after buying it) but few days ago I bought another M7 at a good price just to use with mhl-vga converter (as a stationary with Bluetooth keyboard and mouse connected so we wouldn't have to connect her m7 or my s5 all the time back and forth) but the thing is, that volume rocker (the one you actually need to enter a fastboot mode, the Volume Down) - dont work, so my question is, - is it possible to enter a fastboot mode through pc using cmd ? I've read that it is possible but yesterday I connected, opened command window, typed ADB devices just to see if pc recognizes the device and nothing, then typed other commands I found googling... commands for reboot, reboot to fastboot... whatever... so I'm asking is it possible? or the only way to get there is to use power and volume down buttons? thanx.
edit : drivers are all good (updated), adb us on my pc. the device was On (booted).
Click to expand...
Click to collapse
You can reboot to the bootloader / fastboot usb mode by using the command "adb reboot bootloader". To use this command, you must have the latest HTC drivers installed on your computer and "USB debugging" option turned on in the developer option menu. If you can't access the developer menu from the settings menu (not in the list), you must active it by going to "settings --> about --> Software info --> more" then start tapping on the "build number" until you see a notification "You are now a developer" telling you that the developer option menu is enabled. Then go back to the settings menu --> Developer option -> USB debug --> ON.
Another important thing when using adb from a booted rom is to make sure that you have unlocked the screen using your PIN (or any other security method). ADB won't work if the screen is locked for obvious security reasons.
Once in the bootloader, if you can't use the volume down key to navigate the options, there is not much you can do except using fastboot commands. If you want to boot in recovery mode for example, since the volume key is broken, you'll need to reboot in the OS and use the "adb reboot recovery" command so you can access the recovery mode. If you want to exit the bootloader, use "fastboot reboot".
I I
alray said:
You can reboot to the bootloader / fastboot usb mode by using the command "adb reboot bootloader". To use this command, you must have the latest HTC drivers installed on your computer and "USB debugging" option turned on in the developer option menu. If you can't access the developer menu from the settings menu (not in the list), you must active it by going to "settings --> about --> Software info --> more" then start tapping on the "build number" until you see a notification "You are now a developer" telling you that the developer option menu is enabled. Then go back to the settings menu --> Developer option -> USB debug --> ON.
Another important thing when using adb from a booted rom is to make sure that you have unlocked the screen using your PIN (or any other security method). ADB won't work if the screen is locked for obvious security reasons.
p. s. with my wife's phone I was done in 15 minutes (including unlocking, rooting, flashing a rom and a boot up). so I'm confused a bit. but since wife's June us new and obviously the volume rocker is functioning, I had no problem getting to bootloader and take it from there.
Once in the bootloader, if you can't use the volume down key to navigate the options, there is not much you can do except using fastboot commands. If you want to boot in recovery mode for example, since the volume key is broken, you'll need to reboot in the OS and use the "adb reboot recovery" command so you can access the recovery mode. If you want to exit the bootloader, use "fastboot reboot".
Click to expand...
Click to collapse
thanx for such detailed info. I'm not" working " a lot with htc, I'm myself a Galaxy Series kinda guy but im familiar with the basics of htc. I'll try again tomorrow. but commands don't do what they were meant to do. after updating the drivers with htc sync and having USB debugging On, and adb installed (everything I used to unlock, root etc my wife's device, this device gives me problems). got to see in manager (on pc) if it's even sees the device. but the command Adb devices didn't show anything connected.
methoddon1 said:
I I
thanx for such detailed info. I'm not" working " a lot with htc, I'm myself a Galaxy Series kinda guy but im familiar with the basics of htc. I'll try again tomorrow. but commands don't do what they were meant to do. after updating the drivers with htc sync and having USB debugging On, and adb installed (everything I used to unlock, root etc my wife's device, this device gives me problems). got to see in manager (on pc) if it's even sees the device. but the command Adb devices didn't show anything connected.
Click to expand...
Click to collapse
Yep and post a screenshot of your devices manager when you'll have time.
alray said:
Yep and post a screenshot of your devices manager when you'll have time.
Click to expand...
Click to collapse
what do you mean? I meant go into pc, open a manager and see if the pc sees it.
methoddon1 said:
what do you mean? I meant go into pc, open a manager and see if the pc sees it.
Click to expand...
Click to collapse
Exactly and if the phone isn't detected or is incorrectly detected (yellow triangle with an exclamation mark) take a screenshot of your windows devices manager and post it here.
I will.
alray said:
Exactly and if the phone isn't detected or is incorrectly detected (yellow triangle with an exclamation mark) take a screenshot of your windows devices manager and post it here.
Click to expand...
Click to collapse
here is the thing, - I was gonna switch my interface to English so it'd be easier for you but don't have it installed and since we just had a major storm, my Internet is down for a minute so here is the thing... in the manager it showd all is good as you see, when you double tap on My HTC, in the little window in General it shows Connected but in time in the same General it'll show "At this moment the device isn't connected (code45). To solve this problem reconnect the device."
p. s. in Drivers tab (just for the hell of it I pressed Update but the drivers are up to date. so does HTC Sync... connected, synced.
oh sh**, I'm finally in after trying and trying... adb devices - Recognised, adb reboot bootloader - rebooted... never mind right now, I'll take it from here. out of time right now but I'll get back to it when my Internet connection fixed. thanx again, but I might be back with another question.
---------- Post added at 09:46 AM ---------- Previous post was at 09:27 AM ----------
maybe it's a coincidence but I deleted folders that I used to work with my wife's htc (in mini-sdk folder was unlock code that I got unlocking her device) and unzipped (still had the zip) again. now I have no problems using adb commands.?
alray said:
Exactly and if the phone isn't detected or is incorrectly detected (yellow triangle with an exclamation mark) take a screenshot of your windows devices manager and post it here.
Click to expand...
Click to collapse
well, I fckd it up... after successfully going through process of unlocking, flashing twrp, restoring apps from Titanium Backup, last thing I had to do was install xposed installer... i installed exactly the same that I did before 4beta but instead of flashing 68 arm 21 zip to install framework I flashed 74 arm 21 zip, wiped dalvik but no boot up. that's it! htc one logo... connected the device to pc, now it sees it but it says it's off line (in cmd). another thing, - as soon as I connect it the Manager shows everything is fine, then I open cmd, go to cd C:\ (everything is still ok in the Manager) but as soon as I type mini-sdk (the adb folder), the Android USB at the top of the Manager stays the same but Removable Devices gers a triangle. any clue??? Jesus, I was there, everything was fine, I've got a backup of stock rom after flashing twrp but now a brick.
here it is
I was using mini-sdk but just now installed 15 seconds ADB program and tried with it... same sh**. it sees it but the status is offline... tested on my Galaxy s5, works just fine. wtf? did I hardbricked my htc?! can it actually see the # but be Offline. still on htc logo.
p. s. on connecting the s5, in the line where htc (pic above) has yellow triangle, it's not there on s5.is there a solution? double pressing on HTC with yellow triangle and in the window popping up in General tab it says, - Impossible to start (code 10).
and another thing... i honestly don't remember if I enabled Debugging when I flashed ARHD Rom... is it On by default in custom roms in htc?
---------- Post added at 03:56 PM ---------- Previous post was at 03:21 PM ----------
alray said:
Exactly and if the phone isn't detected or is incorrectly detected (yellow triangle with an exclamation mark) take a screenshot of your windows devices manager and post it here.
Click to expand...
Click to collapse
look at this... the craziest sh**. look at the commands... on adb reboot - device not found, on adb devices - it shows up but as offline and at that exact moment HTC line on Manager changes to a yellow triangle but not before.
pic
methoddon1 said:
pic
Click to expand...
Click to collapse
You can't use adb if the phone isn't fully booted to the OS or booted in a custom recovery. What version of android or what firmware version is installed on the phone? The Xposed version you need to install depends the android version that is installed on the phone. Bootloop caused by xposed is something easy to fix normally, but you need to get in recovery mode which is a problem without a working volume down key
alray said:
You can't use adb if the phone isn't fully booted to the OS or booted in a custom recovery. What version of android or what firmware version is installed on the phone? The Xposed version you need to install depends the android version that is installed on the phone. Bootloop caused by xposed is something easy to fix normally, but you need to get in recovery mode which is a problem without a working volume down key
Click to expand...
Click to collapse
I know.... (about the volume)... it was on official 5.0... when I was done with it, it was with a latest twrp and ARHD 92.0 Rom installed. everything was fine... i didn't spend much time on it (had to set it all up), so restored everything with Titanium but instead of waiting for my wife to come back from work (I'm sure I didn't even delete the RIGHT xposed zip. it's still on her phone), I've decided to go and f*** it all up by just flashing the wrong one ....
---------- Post added at 04:24 PM ---------- Previous post was at 04:13 PM ----------
so you're saying it's either fixing a volume rocker or throwing it out?! but the thing is, because I was planning on changing the casing anyway, i took off the back cover to have access to the volume down button and I can feel a weak click but it's there (the click) and couldn't enter a fastboot anyway. f*******ck.
methoddon1 said:
I know.... (about the volume)... it was on official 5.0... when I was done with it, it was with a latest twrp and ARHD 92.0 Rom installed. everything was fine... i didn't spend much time on it (had to set it all up), so restored everything with Titanium but instead of waiting for my wife to come back from work (I'm sure I didn't even delete the RIGHT xposed zip. it's still on her phone), I've decided to go and f*** it all up by just flashing the wrong one ....
Click to expand...
Click to collapse
xposed-v74-sdk21-arm.zip should have worked fine on ARHD 92 (android 5.0.2) but flashing xposed can sometimes cause boot problems, even simply enabling a module can cause boot problems. That was a little risky to do it on a that phone since you need adb to reboot in recovery/bootloader because of the broken volume button.
---------- Post added at 09:32 AM ---------- Previous post was at 09:30 AM ----------
methoddon1 said:
so you're saying it's either fixing a volume rocker or throwing it out?! but the thing is, because I was planning on changing the casing anyway, i took off the back cover to have access to the volume down button and I can feel a weak click but it's there (the click) and couldn't enter a fastboot anyway. f*******ck.
Click to expand...
Click to collapse
Unfortunately yes.
Like I said this problem should be easy to fix, but without access to the bootloader or the recovery, there is not much you can do
ok thanx.
I wish youd reminded of that earlier... I've been using Samsung for too long...
deleted
I recently bought this device. I usually root/unlock bootloader on my devices. I haven't attempted anything on this watch yet, but I did try to enter recovery mode. I reset the device and waited for the screen to turn off. Once the screen turned on and showed the LG insignia, I swiped my finger from the top left corner down to the bottom right (as I read on another post). This took me to the bootloader. After that, I selected the recovery option. This caused the classic Android with it's chest open, red triangle, with an exclamation point. My current phone (OnePlus 3) has an unlocked bootloader and root. I doubt it's related, but could that be causing an issue since they're connected? Android Pay works on the watch even though it won't work on the rooted phone.
Is there not a stock recovery on this device, is it locked, or is this a result of the current state of my phone?
The red triangle means a fatal loading error and all processes have ceased. In other words it isn't letting you into the recovery, same if you hold the two buttons you can get to the bootloader but selecting recovery gives you the same result.
Even if you managed to get to the recovery, there is no known way to connect it to the PC, so you cannot unlock the bootloader.
matejdro said:
Even if you managed to get to the recovery, there is no known way to connect it to the PC, so you cannot unlock the bootloader.
Click to expand...
Click to collapse
No known way to connect it while in the bootloader menu? I've been using it with Android Studio to work on watch faces and an instrument tuner. I haven't tried connecting while in the bootloader menu though.
The command is:
adb connect (your watch ip address)
Thinking about it though, I think they both have to be on the same WiFi network. Maybe it's not possible.
This only works with ADB (when watch is fully turned on). It does not work with bootloader.
Works on download mode as well but couldnt get anything to do in there
Grumps said:
Works on download mode as well but couldnt get anything to do in there
Click to expand...
Click to collapse
Do tell more. You can actually connect to the watch when it is in download mode?
matejdro said:
Do tell more. You can actually connect to the watch when it is in download mode?
Click to expand...
Click to collapse
Yes had to setup my home wifi to be open. then reboot in download mode
But as i said once in download i dunno what we can try?
Gets IP adress which is the same ip it gets with adb and can connect with adb on that ip so it is possible to connect to wifi somehwo in that download mode.
Youtube Video : https://youtu.be/IVNmEXj-6Pk
Trying to get lg Flash tool to connect but need dll. it has network option so it should be possible
Can even ping the ip so we should be able to do something?
Wow that is awesome. I assume this could be used to flash custom recovery (and subsequently root the device), if somebody figures out how.
matejdro said:
Wow that is awesome. I assume this could be used to flash custom recovery (and subsequently root the device), if somebody figures out how.
Click to expand...
Click to collapse
Hopefully. Older Samsung phones are rooted via download mode so maybe it will be possible somehow
Well, I plan to try it as well, using your findings (thx!) with this.Wish me luck. Having flashing available is just one step. we don't have twrp or magisk yet
Hello, could you please repost your video? because I am trying to do the same, and I am failing. I set up guest wifi between my laptop and the watches. it is not protected by any password/wpa. watches are pingable, and I am able to adb to it. but after rebooting to bootloader, I am unable to connect. I would like to perform at least oem unlock, but I can't, as I am unable to connect to it.
Could you please provide more detailed howto?
BTW, that red exclamation mark while in Recovery: Press crown button and top button once at the same time. Recovery will open.
From there, we can sideload ZIP. Question is, what zip? I can only assume that it has to be genuine firmware (OTA) and that it has to be downloaded to internal memory prior of rebooting to recovery. So manual update is possible.
Problem I have right now is, that bootloader is locked, and in order to unlock it, we'll need fastboot connection. But the bootloader in the watch does not support so called 'SoftAP' feature. Seems like it will need an update from Google. But when this will happen I don't know. Possibly with Android 9 update? There must be a way, but LG says that they do not share technical specs, ATT gave me unlock code (I assume for SIM unlock, but my watches are already SIM unlocked). Any ideas? There has to be a way to connect to watch once in recovery, download or bootloader (all three modes are fully functional, just without wireless connectivity).
Question
Virnik0 said:
BTW, that red exclamation mark while in Recovery: Press crown button and top button once at the same time. Recovery will open.
.
Click to expand...
Click to collapse
I have a Ticwatch Pro and am trying to get past the exclamation/no command screen when going into recovery. I have tried literally every combination of button presses with the two side buttons and still cannot get any results. Google searches have turned up little in the way of solutions. So, to all the smart folks here on XDA, how can I get this damn watch into recovery!?!?
(background on why - didn't wear the watch for a few weeks, watch battery dies. When charged and rebooted, got a message that my watch was locked with find my device. From there, I have tried all my potential passwords to unlock but nothing worked. I am left to reset outside the OS now so help is GREATLY appreciated)
you need to press in "phone info" long press until you see adb enable bro
I have been blundering my way though the internet to get my ROG Phone 2 rooted. I have unlocked the bootloader, I have a modified boot image from magisk, I have the ADB connection set up through USB and it works fantastically. I honestly don't know how I got it work, it involved many different driver update attempts and then figuring out I hadn't put the phone into USB debugging, but now fastboot doesn't work.
ADB will list the device, but fastboot cannot see it. I have tried rebooting the phone into the bootloader, but there is no connection on either. Not sure why I thought that would work, but I tried. I really don't understand enough about fastboot to get any farther on my own.
I have the tencent version and I was pretty certain I have the CN android 9.0 on it, but I am no longer certain of that. I am running windows 10.
This is my build number: PKQ1.190414.001.WW_Phone-16.0622.1906.19-0
I honestly don't know, but does that WW mean my tencent phone is running the WW firmware?
RichDoe252 said:
I have been blundering my way though the internet to get my ROG Phone 2 rooted. I have unlocked the bootloader, I have a modified boot image from magisk, I have the ADB connection set up through USB and it works fantastically. I honestly don't know how I got it work, it involved many different driver update attempts and then figuring out I hadn't put the phone into USB debugging, but now fastboot doesn't work.
ADB will list the device, but fastboot cannot see it. I have tried rebooting the phone into the bootloader, but there is no connection on either. Not sure why I thought that would work, but I tried. I really don't understand enough about fastboot to get any farther on my own.
I have the tencent version and I was pretty certain I have the CN android 9.0 on it, but I am no longer certain of that. I am running windows 10.
This is my build number: PKQ1.190414.001.WW_Phone-16.0622.1906.19-0
I honestly don't know, but does that WW mean my tencent phone is running the WW firmware?
Click to expand...
Click to collapse
Fun fact, I just got Fastboot access from my computer by using the side USB port and rebooting into the bootloader from ADB. Still not to sure about the version bit. I think I'm just going to give it whirl and brick my device, maybe.
RichDoe252 said:
I have been blundering my way though the internet to get my ROG Phone 2 rooted. I have unlocked the bootloader, I have a modified boot image from magisk, I have the ADB connection set up through USB and it works fantastically. I honestly don't know how I got it work, it involved many different driver update attempts and then figuring out I hadn't put the phone into USB debugging, but now fastboot doesn't work.
ADB will list the device, but fastboot cannot see it. I have tried rebooting the phone into the bootloader, but there is no connection on either. Not sure why I thought that would work, but I tried. I really don't understand enough about fastboot to get any farther on my own.
I have the tencent version and I was pretty certain I have the CN android 9.0 on it, but I am no longer certain of that. I am running windows 10.
This is my build number: PKQ1.190414.001.WW_Phone-16.0622.1906.19-0
I honestly don't know, but does that WW mean my tencent phone is running the WW firmware?
Click to expand...
Click to collapse
1. You are running a WW rom, but that doesn't necessarily mean your fingerprint is matched. To update you need to have both WW rom and WW fingerprint. You can check if your fingerprint is CN or WW using device info hw from playstore under 'system'
2. In order to root you need to have a matching root boot img for your current rom ie root img for 1906.19, just checking that your know this?
3. Have you managed to get the phone recognised using the cmd 'fastboot devices'? Also are you using the side port?
4.when you say bootloader, have you definitely got the phone in fastboot mode - hold vol up and power button until you see the screen with some options. That screen is fastboot mode, you don't need to select any further options. Once in that mode, connect to pc, open adb and run the fastboot devices cmd. Once your device is recognised, report back here for further steps
superbrick.
reg66 said:
1. You are running a WW rom, but that doesn't necessarily mean your fingerprint is matched. To update you need to have both WW rom and WW fingerprint. You can check if your fingerprint is CN or WW using device info hw from playstore under 'system'
2. In order to root you need to have a matching root boot img for your current rom ie root img for 1906.19, just checking that your know this?
3. Have you managed to get the phone recognised using the cmd 'fastboot devices'? Also are you using the side port?
4.when you say bootloader, have you definitely got the phone in fastboot mode - hold vol up and power button until you see the screen with some options. That screen is fastboot mode, you don't need to select any further options. Once in that mode, connect to pc, open adb and run the fastboot devices cmd. Once your device is recognised, report back here for further steps
Click to expand...
Click to collapse
Thanks for the reply! I did indeed get fastboot to work over USB. Fastboot devices reported back the serial number and everything. I did not know that the build need to match on both the boot and the rom, but that does make sense and I probably should have realized that before I went ahead and copied the rooted boot.img I had over. Then my phone couldn't boot up proper, and got stuck in fastboot. Then I went ahead and copied all of the contents of the same rom over and now it is literally just a black screen. Won't turn on any more. I think I super bricked it.
Sorry I didn't see your post earlier and I know I am not father into the deep end, but is there a way out from where I am.
RichDoe252 said:
Thanks for the reply! I did indeed get fastboot to work over USB. Fastboot devices reported back the serial number and everything. I did not know that the build need to match on both the boot and the rom, but that does make sense and I probably should have realized that before I went ahead and copied the rooted boot.img I had over. Then my phone couldn't boot up proper, and got stuck in fastboot. Then I went ahead and copied all of the contents of the same rom over and now it is literally just a black screen. Won't turn on any more. I think I super bricked it.
Sorry I didn't see your post earlier and I know I am not father into the deep end, but is there a way out from where I am.
Click to expand...
Click to collapse
Oh jeepers dude. So just a black screen... Can you at least boot into fastboot?
reg66 said:
Oh jeepers dude. So just a black screen... Can you at least boot into fastboot?
Click to expand...
Click to collapse
Nope. The only response I can get out of it now is when I plug it into the fastboot port, the computer recognizes that something was plugged in. I don't even get a device on a device manager.
RichDoe252 said:
Nope. The only response I can get out of it now is when I plug it into the fastboot port, the computer recognizes that something was plugged in. I don't even get a device on a device manager.
Click to expand...
Click to collapse
Try holding the power button for around 20 secs until it shuts down. Then try vol up and power together and see if you get back to fastboot. If that doesn't work try vol up vol down and power buttons all together. Then try again to put it in fastboot mode using vol up and power. Let us know what happens /if you can reach fastboot mode
reg66 said:
Try holding the power button for around 20 secs until it shuts down. Then try vol up and power together and see if you get back to fastboot. If that doesn't work try vol up vol down and power buttons all together. Then try again to put it in fastboot mode using vol up and power. Let us know what happens /if you can reach fastboot mode
Click to expand...
Click to collapse
Unfortunately, nothing. Holding power for 20 seconds showed nothing, and like wise for volume up and power. Battery was fully charged too. Had it plugged in for most of today while I was trying to get fastboot to work.
RichDoe252 said:
Unfortunately, nothing. Holding power for 20 seconds showed nothing, and like wise for volume up and power. Battery was fully charged too. Had it plugged in for most of today while I was trying to get fastboot to work.
Click to expand...
Click to collapse
Is there any sort of illumination to the black screen ie do you think the phone is on but the screen is black or do think the phone is completely off?
Holding power button for a while should switch it off after a while. Try holding for longer than 20 secs, then try booting into fastboot mode
---------- Post added at 04:00 AM ---------- Previous post was at 03:44 AM ----------
Well dude, it's 4 am here. Gotta get some sleep dude. Will check here when I wake. Good luck in the mean time
Still trying to get to sleep. How ya getting on? What about vol down and power buttons for 30+secs, can you try that and let us know the results
reg66 said:
Still trying to get to sleep. How ya getting on? What about vol down and power buttons for 30+secs, can you try that and let us know the results
Click to expand...
Click to collapse
Bro get to sleep! Such a good Samaritan
TikiThePug said:
Bro get to sleep! Such a good Samaritan
Click to expand...
Click to collapse
LOL! I would if I could, just can't sleep yet. Hopefully soon tho!
RichDoe252 said:
Unfortunately, nothing. Holding power for 20 seconds showed nothing, and like wise for volume up and power. Battery was fully charged too. Had it plugged in for most of today while I was trying to get fastboot to work.
Click to expand...
Click to collapse
Try a USB 2.0 port? Surprisingly this works for some phones even though it's compatible with 3.0.
reg66 said:
Still trying to get to sleep. How ya getting on? What about vol down and power buttons for 30+secs, can you try that and let us know the results
Click to expand...
Click to collapse
Well, It's been untouched for a day now, and it still will not react to input. No response from long hold on the power button. I will try again in the morning. Is it possible that I somehow wrote into the BIOS of the phone? Android does use a BIOS, right?
RichDoe252 said:
Well, It's been untouched for a day now, and it still will not react to input. No response from long hold on the power button. I will try again in the morning. Is it possible that I somehow wrote into the BIOS of the phone? Android does use a BIOS, right?
Click to expand...
Click to collapse
Android itself does not have a BIOS, since Android is an OS and BIOS is more similar to firmware. But yes, the phone does have firmware, and it could be that the mismatch in firmware versions (from which you tried to flash), has caused the bootloader to "not know what to do now" when trying to start the phone up.
One thing which comes with all phones with a Qualcomm chipset is something called Qualcomm Crashdump Mode. You can try to see if you can get your phone in EDL (emergency download) mode and restore the correct firmware in that way:
https://www.the***********.com/rog-phone-2-unbrick-guide (URL gets censored for some reason; it should be "the custom droid" with no spaces)
Also, if you continue to have driver issues with connecting the phone to your PC, are you able to test another PC or even a Mac if you have access to one? I find Windows can be a giant pain for getting ADB and fastboot to work properly at times.
Good luck and let us know how it goes.
reg66 said:
Still trying to get to sleep. How ya getting on? What about vol down and power buttons for 30+secs, can you try that and let us know the results
Click to expand...
Click to collapse
Ok, so here's where I am: I have left the phone unplugged for a long time now. Really had no effect. I just downloaded QPST and I can actually get my computer to see the phone. However, I am still not quite sure how to USE QPST and not make things worse. So this is my plan: I am going to look through the forums here for info on how to use QPST to get my phone working again. Not really sure what that will look like, but fastboot would be a good start. From there, it sounds like I have to get the original firmware back on it, and then go about the process of rooting once again.
Still leaves me with the issue that started me down the path of rooting this phone, but at least it will not longer be bricked.
RichDoe252 said:
Ok, so here's where I am: I have left the phone unplugged for a long time now. Really had no effect. I just downloaded QPST and I can actually get my computer to see the phone. However, I am still not quite sure how to USE QPST and not make things worse. So this is my plan: I am going to look through the forums here for info on how to use QPST to get my phone working again. Not really sure what that will look like, but fastboot would be a good start. From there, it sounds like I have to get the original firmware back on it, and then go about the process of rooting once again.
Still leaves me with the issue that started me down the path of rooting this phone, but at least it will not longer be bricked.
Click to expand...
Click to collapse
You may not HAVE to flash complete firmware, it is quite likely that the boot.img is causing the problem as you flashed an incompatible version. Below you'll flash the correct version which HOPEFULLY will fix your phone, provided you can get into fastboot mode now.
Haven't read back through all the thread so i can't recall all the details of where you're at. As far as i can tell you're still running WW 16.0622.1906.19-0, correct? Can you get the device to now boot into fastboot mode? (from a powered off state, press and hold vol up and power at the same time. You should then be presented with some options, DON'T select any option. With that menu screen open is fastboot mode.
1. Download and install ADB Fastboot from here to C: drive of your pc/laptop.
2. With your phone in fastboot mode (as detailed above) connect it to pc/laptop using the side port of the phone.
3. Navigate to C:\Program Files (x86)\Minimal ADB and Fastboot folder and double click the cmd-here.exe, this will open a cmd window.
4. Type 'fastboot devices' to check that it's recognised, there should be a serial/key shown after entering that cmd.
5. Provided the serial/key is shown in fastboot mode, download the following boot.img (which is for WW 1906.19) from here.
6. Copy that boot img to the same folder you have open for ADB (C:\Program Files (x86)\Minimal ADB and Fastboot)
7. In the cmd window type 'fastboot flash boot boot.img'.
Now, that boot img is the STOCK boot img for your rom version. Don't worry about rooting for now (if i recall correctly, your phone won't boot to system), let's just try to get the phone booting first. Providing there are no errors when flashing the boot img, on the phone fastboot menu, scroll through and choose 'restart'.
Let me know if the device boots to system now... Good luck
I'll pm you my email address so you'll be able to get hold of me if you get stuck at any stage...
EDIT: was forgetting you tried so many times to get into fastboot mode, without success.
---------- Post added at 08:59 PM ---------- Previous post was at 08:17 PM ----------
Dude, is your phone screen still black but switched on? When you tap the screen does it vibrate. I'm thinking you might already be in edl mode (which could be a good thing). Let us know
Check your pm's dude for further info. I can't post links to the site required so have sent via pm
TikiThePug said:
Android itself does not have a BIOS, since Android is an OS and BIOS is more similar to firmware. But yes, the phone does have firmware, and it could be that the mismatch in firmware versions (from which you tried to flash), has caused the bootloader to "not know what to do now" when trying to start the phone up.
One thing which comes with all phones with a Qualcomm chipset is something called Qualcomm Crashdump Mode. You can try to see if you can get your phone in EDL (emergency download) mode and restore the correct firmware in that way:
https://www.the***********.com/rog-phone-2-unbrick-guide (URL gets censored for some reason; it should be "the custom droid" with no spaces)
Also, if you continue to have driver issues with connecting the phone to your PC, are you able to test another PC or even a Mac if you have access to one? I find Windows can be a giant pain for getting ADB and fastboot to work properly at times.
Good luck and let us know how it goes.
Click to expand...
Click to collapse
Just dropping you a quick note to say thanks for thanks! LOL. Yeah, your post earlier seems like the best place to go. Have used Miflash Tool a few times on Xiaomi devices, it's pretty good and straight forward. Should be a LOT easier than using QPST and having to change EMMC to UFS.
Can't remember where i saw it now, but i'm sure i read that if the phone screen is black (but switched on) and vibrates, then it's likely to be in EDL mode already. Which will hopefully be good news for @RichDoe252. Before that (having never been in that situation), i wasn't aware that an all black screen could mean EDL mode is active. Fingers crossed for Rich it'll all work out just fine.
@RichDoe252 If all goes successfully using the QPST file download (and using the Miflash Tool the guide mentions in the pm i sent you) and flashing, DON'T ROOT JUST YET!!!! LOL. Let us know how it goes and then we can look into, and point you in the right direction, for getting you rooted and up to date on latest A9 or A10 whichever you'd prefer
Well I must say Rich, I'm surprised you haven't been back here yet to give any updates on progress!! Sent you a couple of emails through pm... Man, if it was my fairly expensive phone that was in the poo pan, I'd be all over trying to fix it lol
reg66 said:
Well I must say Rich, I'm surprised you haven't been back here yet to give any updates on progress!! Sent you a couple of emails through pm... Man, if it was my fairly expensive phone that was in the poo pan, I'd be all over trying to fix it lol
Click to expand...
Click to collapse
First off, you are a freaking saint. I really do appreciate all the help you have been offering up, and I am sorry I have not been very quick with a response. As my phone currently stands, I get 0% response from anything I do to it. No vibrate, nothing. No indication it even is plugged in. I had it connected to my PC with QPST installed, and it was able to pick up that the phone was there, and then immediately tried to download something to it. Not sure what, not sure why, but that kinda typifiies my interaction with this whole process so far. If you haven't guessed, I'm kinda in over my head.
Back to the problem: QPST started some opperation to download something to it. Wouldn't let me do anything else, said the phone was in "download mode". Either way it stopped at 30% and didn't progress for 30 minutes, so I tried to unplug it and plug it back in. Same interaction. Unable to do anything to the phone, no reaction from the phone what so ever. This was, by the way, plugged into the fastboot side port.
I saw that you PM'ed me, and now I can't find the email notification or the PMs on the site. Forgive me for being unfortunately new at this. I will get back to you bud, and thank you again.