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
So I dropped my phone and shattered the screen a few days ago. Just today a section of the screen failed that prevented me from unlocking the device with my pattern. Like an idiot, I kept trying to obtain the pattern unlock, but ultimately failed and now the phone is forcing me to unlock it by signing into the Google account associated with the phone. Unfortunately that only works if you have a Wifi or data connection, which I DON'T have because I had it in Airplane mode when the digitizer died.
So what are my options here? The phone DOES have an unlocked bootloader, as I loaded the Mexican ROM a while back to replace the stock U.S. one. When I boot up to Fastboot mode, it says unlocked status 3, and I can successfully see the device by using the "fastmode devices" mode. However, I cannot access the device via ADB because I didn't have USB debugging turned on.
I'm not all that familiar with Android recovery options and would just like to see if I can get into my device without having to wipe it. Ideally all I want to do is either:
A.) Somehow turn on Wifi so I can unlock the device by signing into google (I can connect a keyboard up to the phone to type in my credentials)
B.) Somehow turn on USB debugging so I can use ADB to then clear the password or turn on wifi, etc
Help!
Farfolomew said:
So I dropped my phone and shattered the screen a few days ago. Just today a section of the screen failed that prevented me from unlocking the device with my pattern. Like an idiot, I kept trying to obtain the pattern unlock, but ultimately failed and now the phone is forcing me to unlock it by signing into the Google account associated with the phone. Unfortunately that only works if you have a Wifi or data connection, which I DON'T have because I had it in Airplane mode when the digitizer died.
So what are my options here? The phone DOES have an unlocked bootloader, as I loaded the Mexican ROM a while back to replace the stock U.S. one. When I boot up to Fastboot mode, it says unlocked status 3, and I can successfully see the device by using the "fastmode devices" mode. However, I cannot access the device via ADB because I didn't have USB debugging turned on.
I'm not all that familiar with Android recovery options and would just like to see if I can get into my device without having to wipe it. Ideally all I want to do is either:
A.) Somehow turn on Wifi so I can unlock the device by signing into google (I can connect a keyboard up to the phone to type in my credentials)
B.) Somehow turn on USB debugging so I can use ADB to then clear the password or turn on wifi, etc
Help!
Click to expand...
Click to collapse
When you hold down the power button at the lockscreen, isn't there an option to turn on/off airplane mode?
TheCrazyDirectioner said:
When you hold down the power button at the lockscreen, isn't there an option to turn on/off airplane mode?
Click to expand...
Click to collapse
Huh I can't believe I didn't see that option. Unfortunately, I also had my data connection turned off as well, so simply turning off airplane mode is not sufficient.
I tried to load CWM recovery using the fastmode flash recovery cmd, thinking it would give me some sort of ADB access, but it errored out with a "remote failure" error. I'm not even sure that recovery would have let me disable the pattern lock anyways.
Thanks for the help!
Farfolomew said:
So I dropped my phone and shattered the screen a few days ago. Just today a section of the screen failed that prevented me from unlocking the device with my pattern. Like an idiot, I kept trying to obtain the pattern unlock, but ultimately failed and now the phone is forcing me to unlock it by signing into the Google account associated with the phone. Unfortunately that only works if you have a Wifi or data connection, which I DON'T have because I had it in Airplane mode when the digitizer died.
So what are my options here? The phone DOES have an unlocked bootloader, as I loaded the Mexican ROM a while back to replace the stock U.S. one. When I boot up to Fastboot mode, it says unlocked status 3, and I can successfully see the device by using the "fastmode devices" mode. However, I cannot access the device via ADB because I didn't have USB debugging turned on.
I'm not all that familiar with Android recovery options and would just like to see if I can get into my device without having to wipe it. Ideally all I want to do is either:
A.) Somehow turn on Wifi so I can unlock the device by signing into google (I can connect a keyboard up to the phone to type in my credentials)
B.) Somehow turn on USB debugging so I can use ADB to then clear the password or turn on wifi, etc
Help!
Click to expand...
Click to collapse
http://forum.xda-developers.com/sho...mctr=(not provided)&__utmv=-&__utmk=201566226
That link doesn't help me at all, since I can't unlock the phone to turn on USB debugging, nor would I even be able to unlock it even if I could control it remotely.
But anyways, great news to report! I was able to eventually load the Clockwork mod (CWM) as the recovery partition in fastboot mode. The problem earlier trying to flash CWM was that the phone's battery was too low and it threw a vague "remote failure" error. After charging it up to 100% the flash worked fine. After that, I rebooted into CWM and then flashed the Aroma file manager zip (using method VII on this page: http :// en. miui. com /thread-5684-1-1 . html) , and managed to delete the password and gesture key files, and voila! after restarting my phone I was in! Wooo!
So obviously I was only able to do this because my phone was previously rooted with bootloader unlocked. If that weren't the case (ie, default from the factory), then the only option would have been to wipe the device.
Farfolomew said:
That link doesn't help me at all, since I can't unlock the phone to turn on USB debugging, nor would I even be able to unlock it even if I could control it remotely.
But anyways, great news to report! I was able to eventually load the Clockwork mod (CWM) as the recovery partition in fastboot mode. The problem earlier trying to flash CWM was that the phone's battery was too low and it threw a vague "remote failure" error. After charging it up to 100% the flash worked fine. After that, I rebooted into CWM and then flashed the Aroma file manager zip (using method VII on this page: http :// en. miui. com /thread-5684-1-1 . html) , and managed to delete the password and gesture key files, and voila! after restarting my phone I was in! Wooo!
So obviously I was only able to do this because my phone was previously rooted with bootloader unlocked. If that weren't the case (ie, default from the factory), then the only option would have been to wipe the device.
Click to expand...
Click to collapse
why dont you take an HDMI cable then connect it to a TV or screen then you can see everything
Mine screen was broken some moths ago and I did this to use phone before new screen replacement came. Maybe it can help you.
devilsking said:
why dont you take an HDMI cable then connect it to a TV or screen then you can see everything
Mine screen was broken some moths ago and I did this to use phone before new screen replacement came. Maybe it can help you.
Click to expand...
Click to collapse
Yes, I should have immediately stopped trying to pattern-unlock it with the broke screen and waited until I could have hooked up my mouse. I didn't know it would lock me out of the pattern-unlock method after so many tries and force me to unlock using google signin. Also, with the google sign in, I assumed it used cached credentials, but it does not. It requires an active data or wifi connection to verify. Neither of those were turned on, nor could I turn them on. The only option I had was to get in there using a Recovery ROM and remove the password key files. I guess the moral of this story is don't be an idiot and absolutely try to get into your phone right away, when there are plenty of other ways to get in even if hte screen is completely broke (like you said with HDMI cable, keyboard, mouse, etc)
Also, I had a "fun" little issue after that where I tried to edit the build.props file to enable home screen rotation, but that ended up crashing the OS and I had to use fastboot to flash just the system.img that was from the stock Mexican 4.1.2 ROM. So now, I just downloaded an app that allows me to rotate my device, and thus allow me to avoid the dead part of the digitizer when I need to.
So sadly the 2nd gen Moto X is not that strong. A 2.5' drop and the screen is completely shattered and only about the left 1/4" is readable. I need some help trying to back up my files before replacing it. I can boot into fastboot mode and my computer recognizes it, but I can't get any farther than that. The only options I see on the menu are "N, R, (what looks like a B, R or F), B, B, Q". I figured out that the "N" is "Normal" and I think the "R" is recovery. If I can get to an ADB enabled session i should be able to do most of what i need to do, but without seeing a screen it's hard to do. Additionally, I have a PIN lock (but luckily not encrypted) to work around.
Does anyone have any ideas on how I could get this working? I heard that some of it could be done via recovery, but i'm flying blind so either need some fastboot commands with an image file, or someone willing to post screenshots/menu options to help get me far enough. I found some tutorials for removing the passcode lock (luckily I have a rooted, unlocked phone) but I can't post the links here.
Anyone have any suggestions/help?
Thanks!
Jeffe
Well, I manged to figure out how to get into the recovery mode, but when selecting "Apply update from ADB" my computer doesn't seem to recognize the device even though I've previously installed the USB drivers before. Trying to see if there's a different set of drivers i'm missing.
Hi all,
A few years ago (well when the devices has pretty much just come out), I ran a mod which i found on the XDA website that allowed me to root my partners Xperia T (LT30P),
Everything has been fine until recently, where I've wanted to upgrade the ROM on the phone, but this is where i'm having some major problems.!
Essentially I cant get the phone to boot into either Flash mode (green LED) or Fastboot mode (Blue LED). I've tried the volume down and then connecting the USB cable to my PC (on which the correct drivers are installed via Flashtool). and also the volume up for Fastboot. Neither work. Unsure if the phone has an unlocked bootloader or if that matters (im a Samsung man and used to working with that, so all the Xperia modding is totally new to me... :/
So far ive tried the following:
-Volume down key and plugging into USB port - Result: Phone remains switched off.
-Volume up key pressed in and then plugging into USB port. - Result: Phone remains switched off
-Enabled USB debugging and attempted to boot the phone into flash mode via ADB (Flashtool option). Phone simply reboots.
-Attempted inbuilt software update - Update downloads, but fails at 25% approx when it reboots and attempts the install.
-PC companion equally unsuccessful on my PC, as cant enable flash mode.
I'm totally at a loss at how to flash a fresh complete build (using a ftf file) to the phone without access to flash mode or fastboot mode. Anyone got any idea or know of any tools that might allow me to to completely rebuild the phone so all partitions are present and correct?
One idea i had was to flash a recovery to the phone using FlashR or alike, but cant seem to get it to work either. Flashr looks to install the twrp recovery, but when i attempt to reboot into recovery via Flashr or Rom Manager (another tool i use but not sure if useable on xperia phones?), the phone simply reboots. SOunds like a damaged or wiped partition perhaps?
Anyhoo , any ideas would be welcome guys! Too good a phone to just leave in the drawer
Cheers
Craig.
Cant you flash a boot.img (maybe from cm11 or something) with inbuilt recovery? You can use this for flashing
Ok, I've started writing this reply and lost everything near the end, started freaking out, calmed down and decided to do it again, cause I know what it's like to have a phone that's not behaving as it should. So here goes the shorter-ish version cause I really can't type everything again...
Make sure your volume buttons are working at all (I mean when the phone is booted). They work? good, procced. They don't? we can bypass that, but you, should get them fixed.
Got to this thread and download the latest build of the ROM http://forum.xda-developers.com/xperia-t-v/orig-development/rom-cyanogenmod-12-neo-s-homebuilds-t2984988
Extract the boot.img file from the zip and copy it to the root of your external micro sdcard, NOT IN A FOLDER. If you don't have an sdcard, put in on the internal storage, again, not in a folder.
Root your phone if you haven't. There are plenty of threads on that here on xda
Download an app called Terminal Emulator from the Play Store
Open the app and type su into the prompt.
Grant the app superuser/root access
The following step is the dangerous one where you can seriously break your phone forever. I'm not responsible for anything you mess up. You alone chose to do this
Run the following command in the terminal (be sure that the $ at the end of the line changed to a # (That means you're in root shell, but it's not important))
If you don't have an external sdcard type sdcard0 instead of sdcard1
Code:
dd if=/storage/sdcard1/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/Kernel
Connect the phone to a PC with fastboot drivers installed
Next execute this command and your phone should now boot into fastboot
Code:
reboot bootloader
If a blue LED lights up, you can happily continue flashing kernels and ROMs, if not report back and I'll see if I can help you
Cheers gents. Going to give this a shot tonight. I read last night that some builds out there where you cannot unlock the bootloader (which you can check via service menu)? Is that now bypassable?
crstephenson said:
Cheers gents. Going to give this a shot tonight. I read last night that some builds out there where you cannot unlock the bootloader (which you can check via service menu)? Is that now bypassable?
Click to expand...
Click to collapse
No and it probably never will be. It's hardcoded on the chip. If your phone is bought with a contract binding or it's limited to a single provider, then chances are that you will never be able to unlock the bootloader and flash kernels. It could be that you not being able to get into fastboot is because it's restricted on the device itself [citation needed]. In that case you're screwed and can pretty much forget the whole custom kernel thing. Only ROMs for locked bootloaders
I have ADB and Fastboot installed on my computer. Nothing lists/shows up when the watch is connected and I run "adb devices" in terminal (as I thought would happened) .
In the recovery, there's a choice for "apply update from sd card". How does that work or does it even work, on this watch?
I haven't used the watch in some time (silver 1st gen); I guess I gave up on it a while ago. It used to be stuck on the 4 spinning circles but not anymore. When I put it on the charger, it's just stuck on the LG boot screen. I think it showed the empty battery icon and thunderbolt but can't remember seeing it today. Search for some threads on being stuck on the LG screen, not charging and stock image recovery.
So trying to troubeshoot it, I tried to charge it (w/stock charger) and all I got was stuck on the LG screen and it got warm to the touch after about 20 mins. I worried about screen burns so, I shut it down. I'm able to get into the fastboot and recovery menus. In the recovery menu, I tried a reset but nothing changed after a reboot.
In thinking it may need a restoring with the stock image, I've read that ADB Debugging on the device must be enabled (or am I incorrect about that?) Question: How can I do that if I can't get into the settings of the watch?
I'm on Linux Mint. I have SDKManager on it but not quite sure how to use it. Not a power user by any means. A little help is greatly appreciated. The only other device I've used XDA before was on a Galaxy Note (1). That was a long time ago (what we're on Note 9 now!)
Well after thinking about it, I figured I'd try the option "apply update from ADB" in the recovery mode on the watch. The watch prompted for the package I wanted to apply to the device. I opened a terminal window on my computer and ran "adb devices" and lo and behold, it came up with the watch's serial number and the text "sideload" next to it. So does this mean I could sideload a stock (or custom) ROM back on to it?
here's some specifics of the watch:
Fastboot menu
Product name - bass
Variant - bass 4GB
HW version - rev_10
Bootloader version - BASSZ12b
Singing - Production
Secured Boot - enabled
Lock State - locked
Android Recovery menu
lge/bass/bass
7.1.1/NWS2.170620.003/4125898
Any help would be appreciated for this noob.