I could really use some help on this one. I rooted my phone back in the summer of 2017 and used the Pure Nexus rom. I have not had any problems and did not do any updates since then.
Out of nowhere my phone shuts off. When I try to boot it, the screen flashes between being static (like a TV without reception) and the google screen that is off center (instead of google being in the middle, it only briefly displays "oogle" to the left side of the screen). I can access my bootloader, which is still unlocked, but I can no longer get into my recovery.
Any help is greatly appreciated. I do not remember which version of firmware I had but i do not think I ever updated it from the original firmware the phone came with.
Thanks in advance
Update: I think it is only fastboot I can get into, not the bootloader. i think I am on 7.1.2. It is the google store phone. I tried using the SkipSoft android toolkit to both install and sideload the factory stock image and it would not work, It just says, FAILED (remote: verify bootloader image failed on production device)"
I'm really stuck on this one
Try doing the update manually. Download the latest factory image file, and double-check the checksum value. Unzip the file and open a command prompt or terminal window in that directory. Separately, open the flash-all.bat or flash-all.sh file in a text editor. Run each of the flash commands yourself, and see where the errors show up. Copy/paste or screenshot any errors, and let us know what happens.
Related
Currently my phone is unusable. It displays the green screen with the myTouch logo for a minute or so then goes black and starts over. I can get to recovery mode, and I tried flashing the only copy of CM I have avaliable from there, which is 4.2.3, but it got stuck at the step "Deleting files..." Here's how I got to this point:
I wanted to get Navigation, but every time I tried to install it from market it said something along the lines of "The package is not signed correctly." I got the attached zip from this wave (You need a Google Wave account to view. Currently invite only.) Here's some relevant bits from the wave:
Here. I'll attach the zip file. Just install it like you would a build. If you don't see it afterwards, I hear you have to install Google Voice to make it work.
So i just go into recovery and install any zip for that?
Yup, exactly. Only downside is... with every update to Cyanogen's mod, you need to reupload the navigation.
Click to expand...
Click to collapse
I was on the latest CM at the time (which I think is still the latest) and this was posted before Nav was in the Market. I installed this zip and I had Nav, but there was an even newer version of Maps in Market, and I installed that and it worked this time. Only thing was, this zip somehow changed my version number of CM, and CM Updater said I was three updates behind again. I figured I'd go ahead and try running the latest CM zip and see if Maps still worked, and it did. But after a while, it randomly rebooted on me. This kept happening for a while, but it was only every couple days, so I figured I'd see if it was still doing it after the next CM update and if so I'd post about it then.
Just today a new version of Google Maps was in Market, and I downloaded it and installed it and played with it for a bit. Then later the system rebooted and I am where I am now. Just keeps rebooting after the myTouch screen.
My recovery image is just the normal Android one, I think. (It says Android system recovery <2> at the top and Build: CyanogenMod v1.4 + JF at the bottom, but it's always said that even before Nav and working fine on 4.2.7.)
Other stuff that ran/might have ran in background: Google Voice, Google Listen, Wifi power widget... There's probably more that I'm not thinking of right now. Will add later if I do.
My recovery image doesn't let me mount my card and I don't have an SDHC reader, but obviously I can get one, since it will probably be needed to fix this.
Only reason I'm not completely freaked out right now is anti-anxiety meds. Please tell me it's not a brick, because I'm not supposed to take any more today.
It's not bricked. Do you know how to fastboot? Download Amon_RA's recovery 1.5.1G and from there fastboot it and replace your current G1 recovery. This rom allows you to mount your SD card, and from there you can put in a new rom on your phone and flash it again.
I did some searching on fastboot, and I got to the fastboot screen on my phone, but I don't understand what to do on my computer's side. I'm running XP SP3. Edit: I also have another partition running OpenSUSE, but I haven't used it in forever and I'm not very good with it. XP options are preferable.
Okay, I wanna make sure I got this right before I continue. I got the Android SDK from Google, and I got the file recovery-RA-sapphire-v1.5.1G.img from this thread. So from a command prompt in the tools directory of the SDK, I should run "fastboot update recovery-RA-sapphire-v1.5.1G.img"?
Edit: Nevermind, I want the flash command like it says in the thread I linked to. Duh.
Edit: So I did fastboot flash recovery recovery-RA-sapphire-v1.5.1G.img and it just said < waiting for device > even when I clicked Fastboot USB on the phone. I keep getting the add hardware wizard and ignoring it. Am I supposed to install a driver for this or something?
Sorry to repost with nothing new to say, but I've searched and looked through other threads and I just can't figure this out. I really need my phone to work.
I hold back and push power on the phone, a white screen comes up with Sapphire pvt 32B... Fastboot. I plug it in to my USB cable and it changes to Fastboot USB. I get a found new hardware wizard and just hit esc.
I type "fastboot flash recovery recovery-RA-sapphire-v1.5.1G.img" in command prompt and it just says "< waiting for device >" forever.
I can push the trackball and the screen goes black for a second and then comes back with the exact same thing. I get the wizard again.
What am I missing?
Edit: Okay, I found the driver and now I get "sending 'recovery' (4050 KB)... FAILED (remote: not allow)"
jomasecu said:
Sorry to repost with nothing new to say, but I've searched and looked through other threads and I just can't figure this out. I really need my phone to work.
I hold back and push power on the phone, a white screen comes up with Sapphire pvt 32B... Fastboot. I plug it in to my USB cable and it changes to Fastboot USB. I get a found new hardware wizard and just hit esc.
I type "fastboot flash recovery recovery-RA-sapphire-v1.5.1G.img" in command prompt and it just says "< waiting for device >" forever.
I can push the trackball and the screen goes black for a second and then comes back with the exact same thing. I get the wizard again.
What am I missing?
Edit: Okay, I found the driver and now I get "sending 'recovery' (4050 KB)... FAILED (remote: not allow)"
Click to expand...
Click to collapse
what spl do you have? does it allow fastboot?
I don't know.
A long time ago I rooted my phone and put CM9 on it. I decided I wanted to go back and try Jelly Bean (from factory then go outwards).
I had a difficult time with the CM flash and found one that worked, and thought I was good to go.
My phone: gt-i9020a nexus s
Product name: Herring
HW version 16
boot loader: i 9020xxkl
carrier att
fastboot enabled
unlocked state.
I can launch the official 2.3.6 (Build GRK39F), from google
then the OTA updated kicks in and the phone is stuck at 'boot' Google logo on the screen.
I have done the information below and the same keeps happening...
link: http://forum.xda-developers.com/showthread.php?t=1586845
first of all, the VQ8PQk is a patch file, not a full rom. So flashing that on something else than 2.3.6 will never work. Get into clockworkmod recovery wipe wverything from the mounts and storage menu, and then flash this file : http://android.clients.google.com/pa...o/ZD3PyN0t.zip and THEN this : http://android.clients.google.com/pa...o/hR7QFEtn.zip
and other steps I could try to work around, none of them seem to work.
Am I missing anything?
Thanks!
Use the full factory rom images (sojuaxxxx) from Google.
https://developers.google.com/android/nexus/images#sojua
Follow the instruction on that page (scroll up). If using Windows, use 7zip (or similar util) to expand the .tgz file, open content of "flashall.sh" and execute the commands one at a time.
Code:
fastboot flash bootloader bootloader-crespo-i9020xxlc2.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo-i9020uckj1.img
fastboot reboot-bootloader
fastboot -w update image-sojua-jro03e.zip
The last command will wipe all data and install new 4.1.1 rom.
Edit: install CYGWIN to have linux-like commands (works with tar, adb, fastboot) in windows.
Do you have a backup (preferrably CWM backup) that you have prior to trying to get JB working? If so keep that handy, and preferrably store it on the PC. Titanium backup can ease migrating apps after a wipe and is highly recommended, so do one of these too if you havn't already.
After you make sure you have a solid backup with the information that you want/need on the phone, i would just start fresh. The best way to do this is to do a factory image flash (note: you want sojua if you have the 850MHz variant which is from AT&T). Flashing these will wipe all user data and the /system partition, the sdcard won't be touched. Basically you download it, extract it, then hook up your phone in fastboot mode and do the commands as written in the text file (or run it as a script if you know how). I've described it in more detail elsewhere as have others, doing a search should give results pretty quickly
This will become a factory install of android as given by google, in your chosen version. I'd go straight ot JB and then you can see how much you like it. CWM backup data can be extracted if you lost some crucial information in the flashing and all your apps and their data can be easily restored with titanium backup.
morning update
_android_ said:
Use the full factory rom images (sojuaxxxx) from Google.
Follow the instruction on that page (scroll up). If using Windows, use 7zip (or similar util) to expand the .tgz file, open content of "flashall.sh" and execute the commands one at a time.
Code:
fastboot flash bootloader bootloader-crespo-i9020xxlc2.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo-i9020uckj1.img
fastboot reboot-bootloader
fastboot -w update image-sojua-jro03e.zip
The last command will wipe all data and install new 4.1.1 rom.
Click to expand...
Click to collapse
running linux, no cygwin needed
did this again this morning..and i'm stuck on the google boot screen with the unlocked padlock on the bottom.
how long should this run (20 minutes now)
I have tried the roms from that page, the 2.3.6 is the only rom that I was able to get working..
lost_man said:
running linux, no cygwin needed
did this again this morning..and i'm stuck on the google boot screen with the unlocked padlock on the bottom.
how long should this run (20 minutes now)
I have tried the roms from that page, the 2.3.6 is the only rom that I was able to get working..
Click to expand...
Click to collapse
Make sure you use the sojua versions.
Do you mean you finish all the steps and upon reboot, it's stuck on Google boot screen?
What do you mean by you can only get 2.3.6 working? It went past Google boot screen?
** ran 'flash-all.sh" see if that changes anything, nothing like a script to rule out human error.***
**** that was a mistake...now phone is not turning on, the screen is dead...when i plug in USB chord, nothing is detected no state change on the phone. When I press buttons no state change nothing changes on the screen. I actually think my phone is a true brick, not a software glitch that is fixable....any suggestions now? ****
lost_man said:
** ran 'flash-all.sh" see if that changes anything, nothing like a script to rule out human error.***
**** that was a mistake...now phone is not turning on, the screen is dead...when i plug in USB chord, nothing is detected no state change on the phone. When I press buttons no state change nothing changes on the screen. I actually think my phone is a true brick, not a software glitch that is fixable....any suggestions now? ****
Click to expand...
Click to collapse
Some (quite a few) Nexus S seemed to be vulnerable to Jelly Bean/CM10 update in that the mainboard is toast. I think the only option is to send back for warranty repair. There are some threads on rigging some kind of adapter cable but that will definitely void your warranty (physical mod).
Doesn't sound good, there have been instances where the flash storage has given up and ends up needing a new SoC (the whole mainboard) and similar issues. Some more information would be good to diagnose this better though.
-Take the battery out for 5 minutes, place back in, can you get into fastboot?
-Can you flash recovery and radio? Can you enter recovery?
-After the "fastboot -w update ...." command, what messages do you see on the phone (at the bottom)?
If you can't get the phone to turn on at all after a good 5 minutes without the battery inserted, give AdamOutlers resurrector a shot. A nice phone call to samsung might be a good idea if you're still within 12 months of purchasing. Hopefully it all turns out okay.
-Take the battery out for 5 minutes, place back in, can you get into fastboot?
-Can you flash recovery and radio? Can you enter recovery?
-After the "fastboot -w update ...." command, what messages do you see on the phone (at the bottom)?
If you can't get the phone to turn on at all after a good 5 minutes without the battery inserted, give AdamOutlers resurrector a shot. A nice phone call to samsung might be a good idea if you're still within 12 months of purchasing. Hopefully it all turns out okay.
Click to expand...
Click to collapse
Did all of the above, nothing. adamoutliers does not see a device connected.
lsusb shows nothing
dmesg shows my device disconnect, after the failed boot, no reconnect.
I'm headed out for a few hours, I will leave battery out, and phone disconnected but i'm thinking it's toast. Att will send an RMA phone to me, they gave me a choice of samsung focus (I asked how a windows phone was similar to an android?) or a samsung galaxcy II skyrocket...I'll try samsung next..
Thanks for all the help!
lost_man said:
Did all of the above, nothing. adamoutliers does not see a device connected.
lsusb shows nothing
dmesg shows my device disconnect, after the failed boot, no reconnect.
I'm headed out for a few hours, I will leave battery out, and phone disconnected but i'm thinking it's toast. Att will send an RMA phone to me, they gave me a choice of samsung focus (I asked how a windows phone was similar to an android?) or a samsung galaxcy II skyrocket...I'll try samsung next..
Thanks for all the help!
Click to expand...
Click to collapse
How do i close this thread? It's done, the phone is dead...rma...
My question is regarding flash stock + unroot using the Nexus Root Toolkit v 1.6.3
I have already unlocked and rooted my phone using the tool.
I am now trying to flash stock + unroot using the Nexus Root Toolkit.
I downloaded the build from Google's Factory Image Download page.
I get passed Which Factory Image? by clicking Other/Browse
Choice: I downloaded a factory image myself that I would like to use instead.
Choose a google facotry image: mysidspr-ga02-factory.tar
Analyzing factory image; please be patient
Hascheck Verification
Enter the md5 has given for: mysidspr-ga02-factory.tar
I enter: c93156606b39a6b61d371ef935a6a6ba from googles website.
Message pops up: Your file is good to extract and flash! Press OK to continue.
Please be patient...Checking ADB Status
Device Connected Rebooting your device into bootloader mode
Chekcing Fastboot Status
Device Connected
Checking Fastboot Status
Device Connected
CMD window opens
Booting up your freshly flashed stock device
Wait for your device to finish booting up...
- It will appear to be boot looping; just wait...
-It could take 5-10 minutes; please be patient...
When its finally booted back up, please remember to re-enable USB debugging if you plan on using the toolkit to perform other operations
Press any key to exit...
My phone remains on the Bootloader screen with the robot laying down with its hatch open.
Bootloader is on Start
below robot:
FASTBOOT MODE
PRODUCT NAME - tuna
VARIANT - toro 32GB
HW VERSION - 14
BOOTLOADER VERSION - PRIMELC03
BASEBAND VERSION - L700, FC12 COMA - L700, FC12
CARRIER INFOR - NONE
SERIAL NUMBER - 0A3C2C620401C009
SIGNING - production
LOCK STATE - UNLOCKED.
I have gone through this over and over and have waited anywhere from 15 minutes to 3 hours. Nothing else occurs.
So I click Press any key to exit from the command window and restart my phone and it is still on Android 4.1.1
Any suggestions/help would be greatly appreciated.
Hi, I noticed that if you choose the option where you have already downloaded the image (from google) it wont work. You have to select the option where the program downloads the image from that site goo.xxx.
Google's stock image is .tar and the image downloaded from the other site is .tgz ( supposedly the same thing, but the toolkit would only extract the second) To be honest, I would have rather use the image downloaded from google's...
Doesn't work for me too..
tessorodesoto said:
Hi, I noticed that if you choose the option where you have already downloaded the image (from google) it wont work. You have to select the option where the program downloads the image from that site goo.xxx.
Google's stock image is .tar and the image downloaded from the other site is .tgz ( supposedly the same thing, but the toolkit would only extract the second) To be honest, I would have rather use the image downloaded from google's...
Click to expand...
Click to collapse
I tried to do both ways but it doesn't work for me either..
I have Galaxy Nexus with Android 4.2.1. I have managed to unlock and root my phone easily using Nexus Root Toolkit 1.7.1. However when it comes to flash rom+unroot process, it is not working.. I tried to flash Android 4.2.2 and Android 4.3 by choosing both options but the process always stopped in the beginnig of CMD prompt window..
same problem
I rooted my newly aquaried nex which was a fully stock 4.1 in anticipation of flashing to boost and custom roms and all that fun stuff. NOW I cant flash I CANT change os. I CANT FACTORY RESTORE I CANT DO CRAP I HAVE A FREAKING PAPER WEIGHTT because I don't want sprint and there is no way ill put this back on ebay and give the head ache to someone else. HAS ANYONE FIGURED ANYTHING OUT YET? I can really use a hand. Ive spent over 15 hours researching downloading flashing fast booting etc. and I've gotten nowhere ANY HELP would be GREATLY APPRECIATED.
So I was trying to flash the correct factory firmware onto my phone, using this guide. The sparsechunks all failed, but I still continued. Now my phone only halfway has the bootloader working. As I said in the title, it connects to my PC as a device but I can't use the cmd commands that the guide showed anymore. In the bootloader, only half the commands show properly. Power off, Recovery mode, Start and Qcom. I can also look at my phone information (IMEI, serial number, etc.) Any option (excluding info) besides power off makes my screen flash for a second every couple seconds. Also, plugging my phone into a computer instantly turns it on (to the flashing screens). Any help to factory reset my Moto G 2015?
If your Moto G is in the bootloader (fastboot mode) and you plug it in to your PC, can you type fastboot devices and see your device? If so, you should be fine. You need to go through the process that you tried earlier. I'm not sure why your sparse chunks failed because you gave no error message. Did you grab the correct factory images? If you go through it again and get an error message at any point, just stop and ask here... You are leaving too much information out of your post for anybody to really help you. What model of Moto G do you have? XT??? What factory images did you download? Please give the error messages when something fails.
lease give more info:
but if you can acces fastboot modus and you still getting the same error, just boot or flash twrp recovery and flash cyanogenmod
that's the best option
I fixed it with RSDlite and the .xml file, but I'll put more info in case someone else has the problem. I have an Xt1540 and I had the correct newer version images. The error was simply, "Invalid Sparse Image." After continuing and trying a reboot, I couldn't see my device when I checked adb devices. But, some commands would still go through. None of the flashing worked, but erasing did. The bootloader was obviously quite bugged-out, but I could still see the log. That gave me hope that I could still edit my phone's insides! The reboot command failed here, but atleast it didn't go back to the annoying screen flashes. So I figured I would try something besides the CMD which didn't recognize my phone. So I just clicked around on RSDlite and it worked! I suppose it auto found my device, because I didn't do anything but browse for the .XML file and double click it. Thanks for the help!
*hangs head in shame*
Ok, I'm stumped and I need help.
Last time I rooted a phone, it was our old HTC Thunderbolts... Things have changed significantly since then, or so it would appear.
Trying to fix my wife's phone after a Verizon OTA update seems to have jumped her phone from Android 10 to 11, and in the process nerfed the hotspot (which we need, as we're rural with no landline broadband available)
I'm working on a Moto G Power (sofia XT2041-4), bought late last year off the shelf from Best Buy.
Home PC is a Windows 10 box. I do not have a linux environment available to me.
I am \ was trying to put LinageOS on it, but honestly don't care what OS it is as long as we can turn the hotspot on ourselves, regardless of what Verizon wants. Over a decade ago, I rooted our phones with ICS image, so I have some outdated experience here. CalyxOS looks nice but I don't think it'll work on Moto G Power.
So, here's where I'm at in the last 48 hours.
I have gone in and gotten the unlock key from motorola, and successfully undone the OEM Lock. (I know this is the case because it tells me I'm an idiot and I should lock it, every time it boots up now). This also managed to wipe the phone, which, oops, read to the end of the paragraph BEFORE unlocking and deleting pictures of the grandkids which came in since the last backup.
Somehow last night, I managed to get it to be a brick, but used LMSA to unbrick it, but that version is still the OTA updated Android 11, so same problem with the hotspot.
I have installed the Android SDK, newest motorola drivers, and also the standalone 'Minimal ADB and Fastboot' on my PC
I've managed to get TWRP installed in the recovery portion of the phone. (note: may have been wiped now, but I can get it back on I believe)
Following this video, I managed to bring TWRP up, wiped the device, then copied the Lineage OS image to the microSD card, as well as Open GApps. The only thing I couldn't get to work, other than, you know, the new OS, is I didn't see a place to enable advanced boot options, so I have to get back to the bootloader via Volume Down and Power from a full shutdown state.
When I try to install the LinageOS (17.1), it looks like it's installing, goes through steps 1 and 2, then a slew of error messages in the log.
I've got the 4 image files I pulled out of one of the LineageOS zip files (Boot, Product, System, VBMeta) in the 'Minimal ADB and Fastboot' directory.
I can run 'fastboot flash boot boot.img' from the 'Minimal ADB and Fastboot' directory and it succeeds.
When I try to run Product, System or VBMeta in the same way (cmdline = fastboot flash product product.img), all of them fail the Preflash Validation and it comes back with 'FAILED (remote failure)'
During this process, somehow I bricked my wife's phone AGAIN, but just got it reset with LMSA for the second time. So, I may have wiped out everything I've done previously on the phone, which may or may not be a good thing. But, I believe everything I've done up to this point is repeatable (which is somewhat why I wrote all of the above details out)
Edit: Progress is Made! - Ok, now that I've got FASTBOOTD figured out, I was able to flash the Boot, Product, System and VBMeta into active partition A. But when I use the command 'flashboot reboot' it just keeps coming back to the fastboot flashload screen with the green android with it's access panel open. I tried to get back into TWRP via entering 'Recovery Mode' at the loader, but apparently it got wiped. I'm guessing I should flash it back into the recovery slot ("fastboot flash recovery twrp-3.4.0-0-sofia-test9") and then maybe try to recover from Partition A via TWRP?
Things I'm not sure about
First, I'm pretty sure I'm not in FastbootD. I don't see a big red FASTBOOTD at the top, and according to this thread, means I'm not in it.
Update: Ok, I realized I didn't have the 'platform tools', which I have now downloaded, and once I was back in fastboot, I was able to run 'Flashboot reboot flashboot' and now I know I'm in FlashbootD. Not sure what I'm supposed to do in here at this point, but hey, I've now got the correct interface.
I think FASTBOOTD should be something I'm interacting with on the Moto G Power, but for the life of me, I can't figure out how to get to it.
Update on this, see above.
I feel like I've got to be CLOSE to getting this thing working, but damned if I can seem to cross the finish line.
Help?
Further Edit: So, I tried another OS, ResurrectionOS, just to see if it was an issue with the image.
Started with another reset with LMSA (I love that tool... It zeroes out all the stupid things I'm doing on the Moto G Power during this process)
Rebooted into FastBootD mode (with the nice red at the top)
Flashed all four of the images. No errors noted during the process
Wiped the Data
Rebooted... And right back to the bootloader. Cannot seem to get out of the boot loader to get the new OS to initialize.
Again, Help?
Did you ever solve this riddle?