My son brought me his Nexus S 4g and told me that it doesn't work anymore. He says that he didn't do anything and that it just started doing this on its own. Any help would be greatly appreciated.
When powered on, it quickly goes to the screen with the Google icon and a lock icon. It sits here for about 30 seconds, then reboots to the same thing. If I pull the battery and hold Vol Up and Power when inserting the battery I can get into Fastboot, but when I select Recovery or Reboot, I get the same Google screen.
When I gave him the phone, it was rooted with CWM recovery loaded and a ICS ROM running.
Any help would be greatly appreciated as I have been reading through threads all night long without finding much.
Sounds to me like you need to begin the rooting process again at the "fastboot oem unlock" part. Since you probably don't have anything on your SD card, you might have to push a new recovery via fastboot as well.
Look to this thread:
http://forum.xda-developers.com/showthread.php?t=1078213
for inspiration.
Once you get into the recovery loaded via fastboot, you can get whatever rom that you want onto the SD card by navigating to:
Mounts and Storage > Mount USB Storage
and leave it on that screen while you load the rom onto the SD card.
After that flash the new rom via CWM as normal.
Thanks for the reply. Since I was already unlocked, I followed the steps to return the phone to stock, including flashing boot, system, userdata, recovery and erasing cache. Now when I reboot, it just loops to the Google screen and reboots after 30 seconds. The only difference is that I don't see the lock icon at the bottom or the Google screen.
When I select Recovery, it just goes into the same Google loop. I am going to try to go through the root steps and see what happens. :-(
I was able to unlock the phone, but it will not boot into Recovery. I can get to Fastboot, but I am back to where I started.
When I gave the phone to my son, I had installed SetCPU and configured a profile to throttle the processor down when the screen was off to conserve battery. I am now wondering if he tried to overclock the processor and clicked "set at boot".
Any more suggestions? (please)
Did you successfully flash a recovery.img? Immediately after this you should hit Recovery, then mount the storage, copy a ROM over, do a Full Wipe and flash the ROM.
If all goes well, you'll boot fine. If not, it may be a hardware problem. Try to wipe most of it and lock the bootloader if you need to send it to samsung.
It looks like I successfully flashed a recovery image. I have tried version 5.x and version 3.x. Below is the result of the 5.x command. However when I select Recovery from Fastboot, I go to the Google screen loop.
C:\Program Files\Android\android-sdk\tools>fastboot flash recovery recovery-cloc
kwork-5.0.2.0-crespo4g.img
sending 'recovery' (4136 KB)... OKAY
writing 'recovery'... OKAY
C:\Program Files\Android\android-sdk\tools>
OK, go to http://wonderly.com/bb/CRESPO4G/OEM/GRJ22IMAGES.zip
That will download the GRJ22 stock images of your phone. Unzip them in your PC. Next, use fastboot like this.
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
After it finishes you can reboot your phone with "fastboot reboot". This will installed Stock GB 2.3.4 for NS4G. Setup your phone and you will get OTA to 2.3.5. After that you will get OTA again to 2.3.7. Good luck.
By the way, you must let it OTA all the way up to 2.3.7 to get the latest Radio and bootloader version.
Giving it a shot now. I'll let you know shortly how it goes.
Update: Same result. All commands completed successfully, but I end up in the Google logo boot loop. Is there a kernel .img file that I should flash, in case my son tried to flash an unsupported kernel?
C:\Program Files\Android\android-sdk\tools>fastboot flash bootloader bootloader
img
sending 'bootloader' (1536 KB)... OKAY
writing 'bootloader'... OKAY
C:\Program Files\Android\android-sdk\tools>fastboot reboot-bootloader
rebooting into bootloader... OKAY
C:\Program Files\Android\android-sdk\tools>fastboot flash radio radio.img
sending 'radio' (15232 KB)... OKAY
writing 'radio'... OKAY
C:\Program Files\Android\android-sdk\tools>fastboot reboot-bootloader
rebooting into bootloader... OKAY
C:\Program Files\Android\android-sdk\tools>fastboot flash system system.img
sending 'system' (174451 KB)... OKAY
writing 'system'... OKAY
C:\Program Files\Android\android-sdk\tools>fastboot flash userdata userdata.img
sending 'userdata' (18796 KB)... OKAY
writing 'userdata'... OKAY
C:\Program Files\Android\android-sdk\tools>fastboot flash boot boot.img
sending 'boot' (2904 KB)... OKAY
writing 'boot'... OKAY
C:\Program Files\Android\android-sdk\tools>fastboot flash recovery recovery.img
sending 'recovery' (3144 KB)... OKAY
writing 'recovery'... OKAY
C:\Program Files\Android\android-sdk\tools>fastboot erase cache
erasing 'cache'... OKAY
C:\Program Files\Android\android-sdk\tools>fastboot reboot
rebooting...
C:\Program Files\Android\android-sdk\tools>
That included stock kernel.
Man you might just want to fastboot oem lock and send the phone. Those were factory images... if they don't work it means hw issues.
Sent from my Nexus S 4G using XDA
rasengan82 said:
That included stock kernel.
Man you might just want to fastboot oem lock and send the phone. Those were factory images... if they don't work it means hw issues.
Sent from my Nexus S 4G using XDA
Click to expand...
Click to collapse
I agree. If this does not work, send the phone back to Sprint.
I really appreciate y'all trying to help. I will see if Sprint will be kind enough to exchange it. Thanks again.
Everytime I install TWRP and boot into it. It shows Zero internal storage and when I reboot it outlines there isnt an OS installed.
The system OS isnt wiped (although I thought that the first 50 times). When I enter fastboot again TWRP inst installed.
No idea what going on... tried latest and previous TWRP files.
thanks in advance
Heres the Log
-------------
Z:\NewNexus7Root\platform-tools>adb reboot bootloader
Z:\NewNexus7Root\platform-tools>fastboot flash recovery twrp-2.8.7.0-flo.img
sending 'recovery' (8956 KB)...
OKAY [ 0.291s]
writing 'recovery'...
OKAY [ 0.271s]
finished. total time: 0.564s
Z:\NewNexus7Root\platform-tools>adb reboot recovery
error: device not found
error: device not found
Got it working after I found the MultiRom fix on this site.
Seems I had one of those unique "locked down" Nexus's 2013; mines from Amazon.
I originally did a boot unlock, a fash of twrp-2.8.7.2-angler.img, and when I could not get the pattern on twrp recovery to function, I did a sideload of the twrp.img instead of an install.
This failed in a boot loop.
SO I did a flash back to stock with angler-mdb08m-factory-dbc17940.tgz (after unpacking this).
Then I restored all my apk, etc.
BUT now when I do:
fastboot flash recovery twrp-2.8.7.2-angler.img, I SEE:
target reported max download size of 494927872 bytes
sending 'recovery' (16880 KB)...
OKAY [ 0.561s]
writing 'recovery'...
OKAY [ 0.247s]
finished. total time: 0.809s
---- all looks fine, but the device itself does not seem to react and when I reboot, and select recovery, it just goes into Google recovery.
Has anyone else seen this, and do you know how to get past this?
I already tried to unlock again and it tells me error, already unlocked.
So my next step would be to do a lock and then an unlock again, but that would probably cause me to take several hours restoring after another flash to stock, and I fear that I will be back where I am now??? any thoughts??
SOLVED!
It seems that somehow, I just hadn't waited long enough. I was able to now reboot into recovery.
Thanks to any that looked at this issue.
So i have been trying to flash TWRP 3.0.0.1 onto my phone using the guide, http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928, and at first when i got to step 2 and tried to flash TWRP file, it would say "error: cannot load twrp.img"
and that went away and i was finally able to flash it after installing universal adb driver.
When i flash it i get this:
C:\SDK\android-sdk-windows\platform-tools>fastboot flash recovery twrp.img
target reported max download size of 494927872 bytes
sending 'recovery' (16904 KB)...
OKAY [ 0.415s]
writing 'recovery'...
OKAY [ 0.244s]
finished. total time: 0.665s
and when i try to reboot to the bootloader, it shows up the standard stock recovery. What am i doing wrong?
please help
Also, when i do adb devices, it wont show my device. But i saw on the forum that adb doesnt even matter.
NEVERMIND i got it to work. But now im having trouble flashing the lastest march update. It says error 7 and something about my SD card.
LifeOfNexus said:
So i have been trying to flash TWRP 3.0.0.1 onto my phone using the guide, http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928, and at first when i got to step 2 and tried to flash TWRP file, it would say "error: cannot load twrp.img"
and that went away and i was finally able to flash it after installing universal adb driver.
When i flash it i get this:
C:\SDK\android-sdk-windows\platform-tools>fastboot flash recovery twrp.img
target reported max download size of 494927872 bytes
sending 'recovery' (16904 KB)...
OKAY [ 0.415s]
writing 'recovery'...
OKAY [ 0.244s]
finished. total time: 0.665s
and when i try to reboot to the bootloader, it shows up the standard stock recovery. What am i doing wrong?
please help
Also, when i do adb devices, it wont show my device. But i saw on the forum that adb doesnt even matter.
NEVERMIND i got it to work. But now im having trouble flashing the lastest march update. It says error 7 and something about my SD card.
Click to expand...
Click to collapse
I flashed twrp 5 times.. before it "stick" and shows up twrp recovery.
I will update my unbricking process with every attempt
Attempt 1:
Tried to flash grossoshop fastboot rom 17s by manually erasing boot, system, userdata, cache and recovery. Phone doesn't wake up with any. Still responds to ADB and Fastboot commands with no errors
If browsed through adb, system partition only shows two directories lib and lib64
Attempt 2:
Trying to manually flash mbn files present in the official 20s rom of x720. QPST is not recognizing my phone. I have to somehow put the phone into 9008 mode rather than 9025 mode (which is diagnostic)
There are no QPST compatible files around for Le Pro 3. Guess I finally put my 240$ to the trashcan....
Attempt 3:
I tried to flash the mbn, elf and bin files to their corresponding partitions via fastboot, everything went okay with the flashing. Then I flashed the boot.img, stock recovery and splash..... Went okay.
Rebooted my phone into recovery and its still dead. I can only see ADB interface in device manager and device is recognized correctly in adb.
If I power off my phone by pressing both volume buttons + power and then just insert USB cable, I end up in QDLoader 9008 mode. There is still hope if LeEco ever releases service rom for Le Pro 3 just like it released earlier for Le1, Le2, Le Max 2 etc. Leeco.re has all the firmwares except Le Pro 3.
Flagship my ass, LeEco ripped us off with its amazing chinese U-turn yet again. There is no hope in unbricking the phone unless I get QFill factory service rom meant to be compatible with QPST flasher.
Attempt 4:
Finally found the unbrick service rom which is to be flashed with FlashOne program but turns out the file is incomplete.
Ref Thread: http://www.leeco.re/topic/1906-helpx720-bricked/#comment-33155
I charged my x720 last night (just 10 hrs ago), drove to office with battery last known at 87% just 30 minutes ago.
I took it out of my pocket, sent a couple of text msgs, put it on my office table. Now all of a sudden phone is black, no display, no sign of life except short two vibrations everytime I try to turn it on. I have no idea what has just happened. Still got 6 hrs to stay at office then to home where I might try to charge/put phone to PC and check....
I literally have no idea what just happened.
I'm on CM13 by Team Superluminal and never had any problems like this in the past....
I'll update what was the problem once I get home and thoroughly check my phone :/
Click to expand...
Click to collapse
leave power button and vol down pressed for some time........ it's not the normal waiting time....... just leave it pressed until you get into download mode......
it happened to me with a past custom rom.......... your boot-loader may be locked again......
TURBO
TURBO2012 said:
leave power button and vol down pressed for some time........ it's not the normal waiting time....... just leave it pressed until you get into download mode......
it happened to me with a past custom rom.......... your boot-loader may be locked again......
TURBO
Click to expand...
Click to collapse
Phone vibrates very momentarily after about 10 seconds of holding power button and then vibrates like that every 10 seconds if I keep power button pressed.
I connected it to my Computer and it shows up as QUSB_BULK in device manager. Looks like my device is bricked until LeEco releases QFIL files for Le Pro3. I already have installed Qualcomm QDLoader 9008 drivers.
I am leaving this phone on charger overnight and will check if Battery really was depleted this fast in-case phone lives up. Otherwise its a sad story until LeEco releases QFIL files.
Update # 2
I managed to connect my phone stable with Computer without any stupid black rebooting.
I'm able to see my device in ADB under recovery, and ADB under composite interface and even I can issue ADB Reboot Bootloader command to take it to fastboot.
If I just flash TWRP, it flashes successfully but stays black. Even if I boot recovery image, it reboots into composite interface instead.
Next stop: Grossoshop fastboot rom. Im downloading it right now from https://mega.nz/#!VEM1QIYL!HwT9hk7-GA6KZBTRMv0IQ9kleYaG-el63UF21S6P0us
I REALLY REALLY REALLY HOPE IT WORKS. Phone died on me while on nearly full battery so if it stayed on during whole day it still would have half the juice left to be flashed in fastboot. I don't know if the phone is recharging on adapter or not.
Code:
D:\ADB>adb devices
List of devices attached
50a2127e recovery
D:\ADB>adb reboot bootloader
D:\ADB>adb devices
List of devices attached
D:\ADB>fastboot devices
50a2127e fastboot
D:\ADB>fastboot flash recovery lepro3_twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (47052 KB)...
OKAY [ 1.313s]
writing 'recovery'...
OKAY [ 0.328s]
finished. total time: 1.641s
D:\ADB>fastboot boot lepro3_twrp.img
downloading 'boot.img'...
OKAY [ 1.331s]
booting...
OKAY [ 0.344s]
finished. total time: 1.675s
D:\ADB>adb reboot -p
D:\ADB>adb devices
List of devices attached
50a2127e device
D:\ADB>adb reboot recovery
D:\ADB>adb reboot bootloader
D:\ADB>fastboot devices
50a2127e fastboot
D:\ADB>fastboot oem device-info
...
(bootloader) Device product name: [le_zl1_whole_netcom]
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Serial console enabled: false
(bootloader) Serial hw output enabled: false
(bootloader) Display panel:
OKAY [ 0.078s]
finished. total time: 0.078s
D:\ADB>
Update # 3 Phone is still in coma after flashing Grossoshop 17s rom via fastboot
Incomplete log since the batch file window can't be maximized or scrolled
Code:
*****
**********************************************************************
***** FLASH SYSTEM *****
**********************************************************************
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 0.000s]
sending sparse 'system' (487311 KB)...
OKAY [ 14.516s]
writing 'system'...
OKAY [ 9.544s]
sending sparse 'system' (518775 KB)...
OKAY [ 14.934s]
writing 'system'...
OKAY [ 7.324s]
sending sparse 'system' (524287 KB)...
OKAY [ 15.657s]
writing 'system'...
OKAY [ 5.031s]
sending sparse 'system' (524284 KB)...
OKAY [ 15.755s]
writing 'system'...
OKAY [ 4.486s]
sending sparse 'system' (500922 KB)...
OKAY [ 15.109s]
writing 'system'...
OKAY [ 7.818s]
sending sparse 'system' (484095 KB)...
OKAY [ 14.501s]
writing 'system'...
OKAY [ 89.072s]
finished. total time: 213.780s
**********************************************************************
***** FLASH KERNEL *****
**********************************************************************
target reported max download size of 536870912 bytes
sending 'boot' (35764 KB)...
OKAY [ 1.016s]
writing 'boot'...
OKAY [ 0.234s]
finished. total time: 1.266s
**********************************************************************
***** FLASH TWRP *****
**********************************************************************
target reported max download size of 536870912 bytes
sending 'recovery' (48272 KB)...
OKAY [ 1.344s]
writing 'recovery'...
OKAY [ 0.344s]
finished. total time: 1.687s
**********************************************************************
***** REBOOT RECOVERY *****
**********************************************************************
-- If process was OKAY.....
-- Press any Key to start Recovery then.....
1. Wipe DATA, CACHE and DALVIK CACHE for new rom installation.....
2. Wipe CACHE and DALVIK CACHE if you are updating BB72 rom.....
3. Restart at the end of the process.....
-- First boot takes long.....
D:\ADB\GSLEPRO3\18S>
Update # 4:
Phone is still dead, only recognizeable through ADB, Fastboot, QDLoader 9008. Screen never comes alive, only the vibrator gives the sign of life if not for the device Manager.
I managed to flash the mbn, elf and bin files to corresponding parittions with no errors, then I flashed official boot.img, splash.img and stock recovery but upon reboot, phone is still dead.
Dang it man. I in the same boat. I can get to the fastboot and that is it. If i try to boot recovery it flashes the recovery screen and then goes back... im so dumb for even trying to unlock and flash a rom on this thing...
Same here - qdload 9008 mode and no qfil compatible rom pack from LeEco. Relying blindly on them releasing the files sometime in the future seems like a lost cause to me.
coolmaster121 said:
Dang it man. I in the same boat. I can get to the fastboot and that is it. If i try to boot recovery it flashes the recovery screen and then goes back... im so dumb for even trying to unlock and flash a rom on this thing...
Click to expand...
Click to collapse
I am out and have OmniRom installed atm. Thank your XDA!
In case this helps you guys fix it:
https://forum.xda-developers.com/showpost.php?p=71704244&postcount=595
coolmaster121 said:
I am out and have OmniRom installed atm. Thank your XDA!
In case this helps you guys fix it:
https://forum.xda-developers.com/showpost.php?p=71704244&postcount=595
Click to expand...
Click to collapse
Your case was different. At least ur phone showed signs of life by momentarily showing u the recovery screen. My phone doesn't live up at all not even. LED notification light or screen. Just fastboot or ADB or QDLoader.....
Had a similar effect yet from different reason. I dropped my phone in salty water (I thought it would survive as it did in fresh water for a minute LoL) and it won't turn off but just in a boot loop to Recovery.
Then the screen died, won't turn on at all, phone vibrates once or twice every restart infinitely. The battery drained out and I put the phone in a bucket of rice for a day and voila it turned on again. I was able to relock the bootloader and sent it back for repair (with fingers crossed hoping they won't dismantle the phone and find water traces inside =D). They replaced it with new one and so I am happy camper again. =D
Joms_US said:
Had a similar effect yet from different reason. I dropped my phone in salty water (I thought it would survive as it did in fresh water for a minute LoL) and it won't turn off but just in a boot loop to Recovery.
Then the screen died, won't turn on at all, phone vibrates once or twice every restart infinitely. The battery drained out and I put the phone in a bucket of rice for a day and voila it turned on again. I was able to relock the bootloader and sent it back for repair (with fingers crossed hoping they won't dismantle the phone and find water traces inside =D). They replaced it with new one and so I am happy camper again. =D
Click to expand...
Click to collapse
I just happened to buy the phone and get it shipped to wrong country where Leeco support doesn't exist neigther the country supports such repair correspondance. Customs here will charge me around 150$ when I will recieve my phone after repair, moreover my Leeco warranty isnt covered because I didnt buy from their official store (rather a chinese store through a friend and get it shipped to me). So Im left out in the dark waiting for the on-shelf recovery measures.
Man, sucks when we break it this much, huh? I just tried to remove the encryption (was asking for password) after having gotten encrypted from flashing TARS 21s on my 727. Now I can fastboot and see recovery but I can't push any files because adb says it's "unauthorized".... I can't authorise because I have no OS!!! No files either obviously, I just wiped the storage entirely to remove that encryption. Anybody have any ideas on this one? Going to have use a Walmart burner for a little while until I can get a usb-c OTG drive. That's the only thing I can think of since I CAN enter recovery/fastboot flash things
benjmiester said:
Man, sucks when we break it this much, huh? I just tried to remove the encryption (was asking for password) after having gotten encrypted from flashing TARS 21s on my 727. Now I can fastboot and see recovery but I can't push any files because adb says it's "unauthorized".... I can't authorise because I have no OS!!! No files either obviously, I just wiped the storage entirely to remove that encryption. Anybody have any ideas on this one? Going to have use a Walmart burner for a little while until I can get a usb-c OTG drive. That's the only thing I can think of since I CAN enter recovery/fastboot flash things
Click to expand...
Click to collapse
Do you have twrp installed? And an OTG?
benjmiester said:
Man, sucks when we break it this much, huh? I just tried to remove the encryption (was asking for password) after having gotten encrypted from flashing TARS 21s on my 727. Now I can fastboot and see recovery but I can't push any files because adb says it's "unauthorized".... I can't authorise because I have no OS!!! No files either obviously, I just wiped the storage entirely to remove that encryption. Anybody have any ideas on this one? Going to have use a Walmart burner for a little while until I can get a usb-c OTG drive. That's the only thing I can think of since I CAN enter recovery/fastboot flash things
Click to expand...
Click to collapse
You can try "adb sideload" in twrp usually it bypasses "unauthorized" status and flashes away directly.
ivangotoy said:
You can try "adb sideload" in twrp usually it bypasses "unauthorized" status and flashes away directly.
Click to expand...
Click to collapse
That actually did the trick, thanks! I'd be really screwed without TWRP booting.
We, in the qh-usb boat, are rly screwed right now
benjmiester said:
That actually did the trick, thanks! I'd be really screwed without TWRP booting.
Click to expand...
Click to collapse
I am screwed. Can yu explain how this adb sideload worked?
zman123 said:
I am screwed. Can yu explain how this adb sideload worked?
Click to expand...
Click to collapse
Sorry I didn't see this earlier. I was lucky in that my phone would still work in fastboot mode with my computer even though adb push would not so I couldn't push files to flash.
If you can get to twrp, or fastboot (volume DOWN + power, hold until it boots to fastboot screen) then you can open fastboot command window on PC, type fastboot devices and make sure it shows a device is attached and recognized. If so, flash twrp with command fastboot flash boot twrp.zip (or whatever you name it). Once in twrp, you can go to sideload option, have to toggle it on in twrp and it will say ready (waiting to accept zip over adb). Then have rom zip and gapps zip in adb/fastboot folder on pc.
Use command adb sideload rom.zip then same for gapps.zip. It will show progress on the phone if working.
benjmiester said:
Sorry I didn't see this earlier. I was lucky in that my phone would still work in fastboot mode with my computer even though adb push would not so I couldn't push files to flash.
If you can get to twrp, or fastboot (volume DOWN + power, hold until it boots to fastboot screen) then you can open fastboot command window on PC, type fastboot devices and make sure it shows a device is attached and recognized. If so, flash twrp with command fastboot flash boot twrp.zip (or whatever you name it). Once in twrp, you can go to sideload option, have to toggle it on in twrp and it will say ready (waiting to accept zip over adb). Then have rom zip and gapps zip in adb/fastboot folder on pc.
Use command adb sideload rom.zip then same for gapps.zip. It will show progress on the phone if working.
Click to expand...
Click to collapse
Thank you! I was finally able to get sideload to work. I was using Darkobas recovery and that caused issues. Flashing normal TWRP worked. I was able to get back to stock via recovery so know I am trying to fix the prolem that started this mess... Google play store wont work on cellular..... most annoying problem in the world!