Database Info

[Q] Did I buy a bricked Nexus S

I bought a Nexus S from craigslist last night and it was out of juice. The seller was like oh bring it back if it doesnt work and I fell for it! I have the box/manuals/charger and everything so the phone was not stolen. When I put it on charge and turned it on this morning all that comes on the screen is google and a unlocked padlock on it. I thought that I can restore it. Went to the recovery mode by pressing volume up an power switch and tried reboot/recover and power off and they all lead to the same screen. volume down and power leads to nothing. So I called the seller and his phone keeps saying its disconnected. I realize I should have been more careful.
Now I am wondering if there is a way to restore the phone as I think that the seller messed up trying to mod the phone and there is no OS on the phone. Does anyone know how to fix this problem? I tried installing various recoveries and nothing seems to work since I cannot get super user to load nor can I boot up the phone to the OS. Please help a noob!

What is that "same screen" you are talking about? If it's the Droid with a "!" then you have to press vol up + power again to activate stock recovery.
Since you can access fastboot you should be able to flash a new recovery with adb.
Download the cwm recovery image, put it in /tools folder, run adb in cmd prompt, command is "fastboot flash recovery <recoveryimagename>.img", after that you can mount the internal storage via cwm recovery, copy any rom you like onto it, then "install from zip". I'd also format all parts of the phone once (mount and storage) and wipe dalvik cache (wipe) before you flash the new rom.
If it all doesn't help put the phone into download mode (vol up + vol down and then plug in usb cable while holding those two buttons), samfirmware.com has files (Odin) for the i9020 and i9023 (not NS4G yet).
In case your pc/laptop misses USB drivers you can find a guide on how to install adb and the drivers on unlockr.com.

even easier then that, just download the one click root (the gsm version for gsm or the ns4g one for cdma). turn the phone off then boot it back up by holding volume up and power. this will get you into fastboot, from there run the one clicks until it starts to do stuff to your phone, you may need to boot into fastboot mode again at some point. but it will get you a custom recovery loaded up from there you can download a custom rom and flash it in recovery and have a fully working phone
sounds liek the guy tried to root it and messed up something so he sold it privatly seeing as he couldnt figure it out. his loss is now your gain
the phone as you describe it is fully recoverable (dont use odin as its rather risky if you dont know what to do with it, not when you have things like fastboot or recovery mode)

mitrals said:
So I called the seller and his phone keeps saying its disconnected. I realize I should have been more careful.
Click to expand...
Click to collapse
If you were interested in getting in touch with the seller, try calling that number from another phone. You have been Google Voice blocked.
However, your issue is easily fixed I think and this shouldn't be needed.

rentaric: It keeps going back to the screen that says Google and has a unlocked padlock at the bottom center. I tried doing the recovery by the following link: http://forum.xda-developers.com/showthread.php?t=1007782 (The phone is unlocked as it states in Lock State-Unlocked). I was able to finish part 3 as well. In part 4 I get stuck at step #8, where pressing recovery gets me back to Google and unlocked padlock screen. I repeated the procedure multiple times and always get stuck at part 4 step 8. I am trying to get samfirmware going after I try one click root. Will post results.
shabbypenguin: I will download one click root and see where that takes me. I also think there might be some water damage to the phone as the strip on the phone is red and at times buttons dont work.
t1n0m3n: I called the seller from 5 different numbers (US and Canada numbers) and it says the line is disconnected for all numbers. I think he disconnected his phone.
Other notes: Phone looks in great condition so if I can get it running it would be awesome. I paid $250 for it thinking its a great price if the phone worked. Attached is the picture of what the phone does on start up.

are you sure you were able to flash the recovery correctly? does the md5 match? maybe try re-downloading the file?
fastboot flash recovery recovery.img
make sure you are using the recovery specific to your device (NS, NS4G)

Where do I find the MD5?
Here is what the phone says on the bootloader mode:
FASTBOOT MODE
PRODUCT NAME - HERRING
HW VERSION - REV 16
BOOTLOADER VERSION - I9020XXKA3
BASEBAND VERSION - I9020UCKD1
CARRIER INFO - ATT
SERIAL NUMBER - 31310A98550B00EC
LOCK STATE - UNLOCKED
And the rest..
Please let me know if anyone can help! Thank you

Are you rebooting the phone after installing the custom recovery (part 3, step 5)?
If yes, skip the rebooting part and go directly into recovery from bootloader screen. In case it works you can continue to mount the usb storage, copy a ROM on your sdcard, unmount, then go back to "Install from zip" after doing all 3 wipes available in "wipe" menu.
If no, then I have no further ideas then using Odin.

Same issue for me, maybe this phone got the NAND Flash problem. Warm it up then try to turn on your Nexus, it worked for me but I sent my Nexus last week to Samsung for repair.
There is a thread in Google Mobile Help Forum (google.com) in Help forum > Google Mobile > Android Devices > Android Applications (not listed above)
Sorry but i can't post the link.
Regards.

I am having the same exact problem with my phone. The only difference is that my Nexus is a sprint phone. Were you able to get your phone working and how did you do it?
---------- Post added at 05:27 PM ---------- Previous post was at 05:15 PM ----------
Im having the same problem with my phone. I have a nexus s and I think I need to flash [RECOVERY] clockwork because it says "fastboot mode - No boot or recovery img." Im using a mac but I cant seem to get it working. Can someone help me. I cant seem to figure out what to do and where to start.

[Completed] brick problem, noob here, plz help

my problem is kind of abnormal. i couldnt find solution anywhere so i came here. my device was zenfone 5(t00f)/lollipop.
so i wanted to root my phone. i followed this guide >>
HTML:
http://forum.xda-developers.com/zenfone-5/general/zenfonetoolkit3-24-40-87-t3406557
the tool i used is called ZenfoneToolkit_20160719, downloaded from here
HTML:
https://drive.google.com/drive/folders/0B0AFmAAcGS5xbWpTQzBQVTN3b1k
. its a bundle of .exe, .dll, .img, .bin files. but no need to work on them seperately, there is a simple cli tool from which you can choose what you want to do and it executes that file for you. below is the list what you can do.
1. Wipe Cache
2. Factory Reset
3. Flash Boot
4. Flash Recovery
5. Flash Fastboot
6. Flash Stock ROM
7. Root
8. Unroot
9. Unlock Bootloader
10. Relock Bootloader
11. Zenfone Rescue aka Debrick
12. Fixing Generic IMEI 004999010640000
13. Backup MicroSD
14. Flash Boretz Kernel Lollipop
so wiped cache[1] first then i tried to root[7]. sadly it didnt work, when i turned the phone on it took me to fastboot screen, there i had only a few options like, normal boot(doesnt happen), recovery mode, restart. when i turned it off and pressed power and volume up together it would go to recovery where none of the options works. i though that was what called brick, so followed this guide to make my life better
HTML:
http://zenfone-blog.blogspot.com/2015/06/guide-how-to-unbrick-asus-zenfone-4-5-6.html
.
my phone by default came with kitkat. so when i downloaded the firmware i wanted to get a kitkat. but i couldnt find a matching recovery img and firmware for kitkat on asus official page. so i downloaded jellybean. ASUS ZenFone 5(T00F/T00J) software Image: V1.18.40.9 ww for firmware from here
HTML:
https://www.asus.com/support/Download/39/1/0/2/96nqlxHp1VKV4Rdz/32/
. and recovery img is 1.18.40.9_ww_recovery.img from here
HTML:
https://www.asuswebstorage.com/navigate/s/644D9E0A19714899974C75FC4B6C87EDY
. i dont know what "ww" means in those name but i saw it in my software version before so i went with it.
All the steps went smoothly, by the end of it i guessed my phone charge would be low so i put it in charge and turned it on. first time it turn on without a problem. i checked out a few things and leave it for charge. after a while i came back and battery was 0%. i thought i would be wise to plug out and in charging port again. as soon as i pull out the pin, screen instantly turned black and the phone went dead after a looooong ass vibration.
now when i try to charge the orenge light at top lights up but the animation that shows battery always show its empty. if i try to turn it on while plugged, it shows asus logo/intel logo and goes dead again. if i try to turn it on without being plugged, it shows a battery logo with a question mark, which i think means the phone cannot find battery.
i am stuck here.... plz someone be my savior.

http://forum.xda-developers.com/zenfone-5/help/debrick-asus-zenfoen-5-fastboot-t3377455
solved here

nooblett said:
http://forum.xda-developers.com/zenfone-5/help/debrick-asus-zenfoen-5-fastboot-t3377455
solved here
Click to expand...
Click to collapse
Great that the problem was solved
Thread closed

Boot loop s6 g920f

Hi guys,
so here is the thing...my sister gave me s6 to fix it which i thought it would be pretty easy but...she got the phone from her friend who doesnt know much and i assume he went for rooting it but fail...at first, it was all stock and problem was on booting. It was an update screen followed by no command error(same screen after firmware installation - which that guy probably did)..Anyways, i wanted to enter recovery, do the reset and thats it, but i couldnt scroll up and down although volume up and down is working...so i installed twrp via odin and i can access it now... I have done the reset but nothing...it just randomly restarts after samsung logo and keeps going like that. Also very importamt thing you need to know is that all of thi cant be done without charger. Without charger phone is dead..So guys ,do you think it is hardware, or do i need to install proper firmware or something else.. Thank you and sorry for bad english

svetp said:
Hi guys,
so here is the thing...my sister gave me s6 to fix it which i thought it would be pretty easy but...she got the phone from her friend who doesnt know much and i assume he went for rooting it but fail...at first, it was all stock and problem was on booting. It was an update screen followed by no command error(same screen after firmware installation - which that guy probably did)..Anyways, i wanted to enter recovery, do the reset and thats it, but i couldnt scroll up and down although volume up and down is working...so i installed twrp via odin and i can access it now... I have done the reset but nothing...it just randomly restarts after samsung logo and keeps going like that. Also very importamt thing you need to know is that all of thi cant be done without charger. Without charger phone is dead..So guys ,do you think it is hardware, or do i need to install proper firmware or something else.. Thank you and sorry for bad english
Click to expand...
Click to collapse
Hi svetp,
I had the same problem. Whenever I tried to flash the Stock ROM things got worse, until in the end I had the same problem as you. Then I read that AOKP image cures almost always such problems - and it worked ! Don't do this if phon is still under warranty as it triggers the knox counter !
If you can still access download mode try the following:
download the latest TWRP file for your S6 model
download AOKP image for your S6 model
download GAPPS for your S6 model
enter download mode
flash TWRP with Odin, but un-tick "Auto-Reboot" in Odin
when completed go to recovery at once (don't let the phone try to boot normally, just "kill" phone and hold the buttons for download mode)
when in recovery (TWRP) start ADB software (if you don't know how google samsung galaxy S6 ADB for advice)
transfer the downloaded AOKP image and GAPPS to your phone (/sdcard is a nice place) via ADB
wipe cache in TWRP
install image and GAPPS
wipe cache and reboot your phone
everything should be normal by then
Good luck !
Peter

Nexus 5 bootloop, stuck in Rom intro - Don't know how to connect it to my pc

First of all, I'm pretty noob this days on Android so I'm very sorry guys, also english is not my first language.
My nexus was working great until today. I ended a Whatsapp Call and get a black screen, phone looks frozen (happened before). Reboot it and works fine for 5-10 minutes, after that it started to reboot itself the whole time in bootlop, stuck in the rom intro, after the Google text. My rom is one of the very first roms from Slim Roms, I'm sorry I don't remember the Android Version, but is "old".
I can access to the recovery mode tho. I tried to wipe dalvik cache and the TWRP failed, wipe and factory reset, fail as well... I don't know what else to do. I don't have any image to install in the sd, or any backup. Windows 10 recognize an "android" but can't access to it so I can't copy any file to it.
Is my phone dead or can I do something? I love this phone :crying:

Any help please? I tried using ADB and get to copy some files into the phone but still every time I try to do a wipe cache, factory reset or what ever I get a Unable to mount Data / Cache / Storage... every time the same error.
I google it and found that some people could fix that error by repairing the file system and select ext4. But I can't do that, my TWRP build is quite old (v2.6.3.4) and doesn't have that option here. Any suggestions?
Thanks btw

Me again
I've been reading forums for more than 7 hours today and trying different solutions, and nothing. But found this guy here https://androidforums.com/threads/is-my-nexus-5-dead.1099076/
He basically had the same issue as me few years ago, exactly the same, He didn't find any luck apparently.
How is it possible that a phone that can get access to TWRP or copy/flash files via ADB/Fastboot can't be saved? Theoretically in this case this is not a hard bricked, right? So? This is so so weird

It's possible that portions of the internal memory are damaged.
The only thing left to try is flash a stock ROM using ADB commands. I recommend trying a KK ROM.

No OS but twrp working
Hello friend.
If I have understood your problem correctly then you have twrp working but no os.
I found that there is an option in twrp to enable MTP. once you do that you will be able to access it. While the phone is in recovery mode connect it to the computer and it will get recognized and you can transfer zip file to it and then flash a new os.
Cheers!

audit13 said:
It's possible that portions of the internal memory are damaged.
The only thing left to try is flash a stock ROM using ADB commands. I recommend trying a KK ROM.
Click to expand...
Click to collapse
I tried that already, it does the installation thing but always fail in the end
mevrik_007 said:
Hello friend.
If I have understood your problem correctly then you have twrp working but no os.
I found that there is an option in twrp to enable MTP. once you do that you will be able to access it. While the phone is in recovery mode connect it to the computer and it will get recognized and you can transfer zip file to it and then flash a new os.
Cheers!
Click to expand...
Click to collapse
Also tried that: new rom+ gapps via usb adb and the TWRP says Failed...
I mean I still have OS because every single time I try to turn on my phone the animation screen of the Slim Rom goes in. The problem is I can't install anything new, no new rom, no factory image, no new version of TWRP, I can't wipe data or cache or do a factory reset because I get a big red Failed always. Feelsbad

ekeixdurden said:
I tried that already, it does the installation thing but always fail in the end
Also tried that: new rom+ gapps via usb adb and the TWRP says Failed...
I mean I still have OS because every single time I try to turn on my phone the animation screen of the Slim Rom goes in. The problem is I can't install anything new, no new rom, no factory image, no new version of TWRP, I can't wipe data or cache or do a factory reset because I get a big red Failed always. Feelsbad
Click to expand...
Click to collapse
Try this: lock the bootloader and reboot back into the bootloader. If the bootloader remains locked, that's a good sign. If the bootloader is unlocked, that is a bad sign.

audit13 said:
Try this: lock the bootloader and reboot back into the bootloader. If the bootloader remains locked, that's a good sign. If the bootloader is unlocked, that is a bad sign.
Click to expand...
Click to collapse
I tried that with the Nexus root tool kit and the bootloader still is unlocked

ekeixdurden said:
I tried that with the Nexus root tool kit and the bootloader still is unlocked
Click to expand...
Click to collapse
Tells me that the memory chip is defective and needs to be replaced.
Indicates to me that the chip had lost its write capability.

audit13 said:
Tells me that the memory chip is defective and needs to be replaced.
Indicates to me that the chip had lost its write capability.
Click to expand...
Click to collapse
Shieeeet... So nothing to do I guess? I already ordered a new phone but if I can save this beauty would be great

It would be great to fix it but the simplest solution may be to buy a nexus 5 with a smashed screen and working motherboard. I've done this before and it's worked out well because the nexus 5 is pretty old by today's phone standards so I got it cheap.

hmm not a bad idea at all. Thank you!

Root newbie

Hello,
Please help me. My samsung a8 updated to android 9 and the call recording is disabled. I need to root the phone, but help me please in the following questions:
1. Do i need custom rom?
2. Do i need custom kernel?
3. Will the android self update as now?
So what is the most importnt steps just to root the device?
In my whole life i paid for one software (callrecorder) which is not working now.

Unfortuently there is no clear tutorial to root this phone but you car read here: [GUIDE][17.06.2019] RMM/KG bypass - Root/Install TWRP on Exynos Samsung after 2018

Snypie said:
Hello,
Please help me. My samsung a8 updated to android 9 and the call recording is disabled. I need to root the phone, but help me please in the following questions:
1. Do i need custom rom?
2. Do i need custom kernel?
3. Will the android self update as now?
So what is the most importnt steps just to root the device?
In my whole life i paid for one software (callrecorder) which is not working now.
Click to expand...
Click to collapse
1. Do i need custom rom?
no
2. Do i need custom kernel?
no
3. Will the android self update as now?
if you flashed TWRP, no

1. Do i need custom rom? No
2. Do i need custom kernel? No
3. Will the android self update as now? depend on your settings
1-to root it the first thing is to have OEM Unlock available and enabled in Dev Options
if not keep the device fully on and with data on dont restart, power off or reset for at least 7 days continuously (or a bit more) and you should have it
if it's not shown dot bother with the rest
2-to have Dev Menu available go to settings >> about phone >> software information >> on build number tape multiple times 10 times i guess, you will have a pop up confirmation
once back at settings menu you will find a new choice at the very bottom "Develper Options"
3-next step with to plug ur phone with PC with usb cable
after installing SAMSUNG DRIVERS & ODIN and downloading TWRP (custom recovery)
in ODIN 2nd tab, untick "AUTO REBOOT" VERY VERY IMPORTANT
chose the TWRP file using AP button/option in ODIN
put your phone in download MOD power off completely >> power back on while holding vol+ and vol- at the same time
flash the file using ODIN to your phone
4- now here is the tricky part
after fklashing TWRP if you reboot normaly you will be locked again and you wont have that OEM Unlock option i talked about and you will be stuck
so, after flashing TWRP, press vol- + power button to reboot the phone
AT THE VERY PRECISE MOMENT WHEN PHONE TURN OFF BEFORE POWERING BACK ON WHEN IT BLINK
RELEAS POWER BUTTON AND VOL+ and PRESS POWER BUTTON + VOL+ AGAIN VERY VERY QUICKLY
if successful you should boot into TWRP directly
5-once you are in TWRP wipe everything then format the device (ALL DATA WILL BE LOST)
of course you need to have the needed files already copied in the SD CARD
from twrp after the wipe and formatiing
go to install and flash in that order RMM_Bypass_v3_corsicanu or RMM-State_Bypass_Mesa_v2
then no-verity-opt-encrypt-6.0
then at the end flash Magisk-v19.3
once its done reboot the phone normally, you will have your phone working as normal
once you are in, install Magisk APK MagiskManager-v7.3.2
reboot again
and voilaaa, you should have root and everything shoul be functional for you
allthow of course I will not be responsible for any kind of software or hardware damage, and certainly not ressponsible for any data loss
as it is completely you responsibility
I would like to attach all the files mentioned above, to help better but dnt sems to find how
so you will have to download and gather them from previous posts

Thank you very much, but i have a question. You wrote this:
"4- now here is the tricky part
after fklashing TWRP if you reboot normaly you will be locked again and you wont have that OEM Unlock option i talked about and you will be stuck
so"
I this will happen what csn i do?
The most afraiding thing is to me about rooting if i get a brick.

Snypie said:
Thank you very much, but i have a question. You wrote this:
"4- now here is the tricky part
after fklashing TWRP if you reboot normaly you will be locked again and you wont have that OEM Unlock option i talked about and you will be stuck
so"
I this will happen what csn i do?
The most afraiding thing is to me about rooting if i get a brick.
Click to expand...
Click to collapse
its virtually impossible to brick samsung devices these days. Well, perma-brick that is. I have spent entire evenings after work bricking phones just so i could figure out what caused the brick and then fix it. the worst thing that would happen if the FRP lock gets enabled again is that youd have to go re-disable it.
i guess i didnt really explain that clearly after re-reading it. So, when he says "stuck" he means with TWRP installed and no method of rooting. The phone will boot normally in the situation described in point #4