Database Info

[Q] Nexus S keep's restarting itself.

Good day all, I recently got a Nexus S for free from my brother becuase it keep's restarting its self. The phone was rooted with Cyanogen rom, and from what he told me has been dropped a couple of times. With this all being said, he went ahead and flashed a fresh rom on there (unk which one) and wiped everything etc.. Anyone exp this type of problem before and if so what can be done to fix it?

King350z said:
Good day all, I recently got a Nexus S for free from my brother becuase it keep's restarting its self. The phone was rooted with Cyanogen rom, and from what he told me has been dropped a couple of times. With this all being said, he went ahead and flashed a fresh rom on there (unk which one) and wiped everything etc.. Anyone exp this type of problem before and if so what can be done to fix it?
Click to expand...
Click to collapse
Lol I think you over clocked it on the minimum ... try the minimum at 800m ... or if anything flash a new rom.. its probably the rom itself
Sent From In between Your Moms Boobies

Try another (stable) rom? (no development rom)
Wipe everything.
And yes, probably its underclocked/overclocked too high.

I would like to flash a rom but once I turn it on it keeps force closing everything and I am unable to do anything on the phone, It boots into recovery mode just fine though
Sent from my HTC Vision using XDA App

King350z said:
I would like to flash a rom but once I turn it on it keeps force closing everything and I am unable to do anything on the phone, It boots into recovery mode just fine though
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Good news, you flash your ROM from recovery. Download the package, boot into recovery. Mount the SD card and push or push using adb push. Flash the zip from CWM.

my friend purchased the phone yesterday and he is on the latest Official version (2.3.6) and the phone keeps rebooting!!!
is this normal?? there must a problem!

3mar84 said:
my friend purchased the phone yesterday and he is on the latest Official version (2.3.6) and the phone keeps rebooting!!!
is this normal?? there must a problem!
Click to expand...
Click to collapse
Wipe data/factory reset from recovery if it's a used phone.

If he just bought it return it... thats easy
If he rooted it and changed the rom -- put it back to stock or put a new rom on it
I personally found that most of my restarts were due to me trying to pull the stock launcher into an unfamiliar rom. Make sure (if you are using Titanium backup) to only load apps not system *unless you are trying to go back to the same rom*
good luck

First check if he overclocked too much or underclocked too much. Put it to normal.
Alternatively you can just flash another rom. Before flashing remember to wipe everything
Goodluck!

GRRR! Tbolt won't boot with any roms I try to install

My wife's phone is rooted and has been running BAMF for a long time. Well, it's slow as nuts right now and she asked me to redo it. I've been using Jellyblur on my phone, she liked it, and asked that i install that. Well, i can't for the life of me get the phone to boot with a new rom. Multiple downloads, and even downloaded about 3 different roms and it won't get past the white HTC screen.
I can reload my backup I made and it will start up just fine, but it just DOES NOT want to boot with a new rom.
I'm doing full wipes and I even copied the file I installed on my phone to her phone and tried installing that. No go.
Any ideas?
Thanks!
damon

SubliminalME said:
My wife's phone is rooted and has been running BAMF for a long time. Well, it's slow as nuts right now and she asked me to redo it. I've been using Jellyblur on my phone, she liked it, and asked that i install that. Well, i can't for the life of me get the phone to boot with a new rom. Multiple downloads, and even downloaded about 3 different roms and it won't get past the white HTC screen.
I can reload my backup I made and it will start up just fine, but it just DOES NOT want to boot with a new rom.
I'm doing full wipes and I even copied the file I installed on my phone to her phone and tried installing that. No go.
Any ideas?
Thanks!
damon
Click to expand...
Click to collapse
You likely need to update the Recovery.
I'm guessing it has some older form of Clockwork Mod Recovery on it.
You should update to 4ext.
That link is the app that you use as an interface for while in Android OS and it also installs the Recovery.
Install it while in Bamf, load the app and install recovery for HTC Thunderbolt.
Then try updating the rom, good luck!
If you end up liking it, support the dev and buy the full version of the controller app.
The recovery is free and so is the app I linked you however...

Recovery was indeed out of date. Thanks a million ..wouldn't have thought of that!
Sent from my Nexus 7 using Tapatalk 2

SubliminalME said:
Recovery was indeed out of date. Thanks a million ..wouldn't have thought of that!
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
No problem.
Glad you got it resolved.

baseband unknown :((

So i must have messed up my phone while using the all in one root unlocker and so on. Im not sure what i did, but i finally got my phone to boot, and now i get no service. Im on tmobile and it says i have no sim card. When i go into about phone it shows baseband unknown.
I really have no idea what to do. Ive never been stuck in this situation. Maybe someone more experienced can point me in the right direction?
any help would be appreciated!

aamzalag said:
So i must have messed up my phone while using the all in one root unlocker and so on. Im not sure what i did, but i finally got my phone to boot, and now i get no service. Im on tmobile and it says i have no sim card. When i go into about phone it shows baseband unknown.
I really have no idea what to do. Ive never been stuck in this situation. Maybe someone more experienced can point me in the right direction?
any help would be appreciated!
Click to expand...
Click to collapse
so furthermore, it looks like i have no data partition anymore, i can go on my chromebrowser on the phone and browse the web but when i try to install anything it says no sdcard. I also cant move anything to the phone via windows, it just freezes even tho i can see the phone and go into the internal storage.
Im really screwed here. Ive also used the fastboot files to flash back to google stock, but for some reason continue to find everything borked.
HELP PLZ!!! ahah

Also, finding that i cant mount any partition, cache, data, anything liek that. It seems like my partitions have been messed up . Not sure how to resolve that

Well it looks like your the first one to brick the nexus 5. If your imei is missing your screwed.
P.S.A DON'T USE TOOLKITS
Sent from my NEXUS 5

Might be helpful to others to explain exactly what you did to your phone.

lafester said:
Might be helpful to others to explain exactly what you did to your phone.
Click to expand...
Click to collapse
He used a tool kit. Who knows what it did to his phone
Sent from my NEXUS 5

I realize that maybe using the toolkit may not have been a good choice but considering im already here. Constructive advice might be a little more helpful... I know that with my old verizon GS3 if i lost my imei/ similar info, i could nv flash myself and get it back in certain cases. Does a similar thing not exist for the nexus 5? Id imagine that a truly unlocked device like this one should have a method to get back from anything?

aamzalag said:
I realize that maybe using the toolkit may not have been a good choice but considering im already here. Constructive advice might be a little more helpful... I know that with my old verizon GS3 if i lost my imei/ similar info, i could nv flash myself and get it back in certain cases. Does a similar thing not exist for the nexus 5? Id imagine that a truly unlocked device like this one should have a method to get back from anything?
Click to expand...
Click to collapse
If you've flashed the stick images and it hasn't fixed it then you might be out of luck. With the n4 there is a thread on how to restore the phone with LG nv flash in download mode. I don't think the tools or files are available yet for the n5 tho
Sent from my NEXUS 5

i dont know what i did, but i restored the factory image one more time, then booted to stock recovery and wiped all partitions. The phone booted and my imei and baseband are back. Working 100% now. Gonna sit out the rooting and so on for now. time to relax for a bit

So you can't fastboot flash anything? Can you fast boot flash twrp recovery from the android SDK on a PC?
Sent from my Nexus 7

aamzalag said:
i dont know what i did, but i restored the factory image one more time, then booted to stock recovery and wiped all partitions. The phone booted and my imei and baseband are back. Working 100% now. Gonna sit out the rooting and so on for now. time to relax for a bit
Click to expand...
Click to collapse
That's how I fixed my N4. I flashed the factory images 3 times.

Glad it's working finally
Sent from my Nexus 7

Ya, fastboot continued to work, and iw as able to flash the factory images.At first those werent fixing anything. the final time i flashed it right before it worked again, i let the phone sit and run the boot screen for about 30 minutes before i went to stock recovery and wiped. Then it booted perfectly.
The previous times i had flashed twrp and wiped which i believe was the cause in the first place.
Thanks all its working perfect now. The device is amazing,!

aamzalag said:
The previous times i had flashed twrp and wiped which i believe was the cause in the first place.,!
Click to expand...
Click to collapse
Sames just happened to me, but I didnt use a toolkit, i did it all manually.
Quick flash of the factory image sorted it. :victory:
UPDATE: Flashed TWRP again....All ok this time.

You guys unlocked the bootloader first right?
Sent from my SGH-I747

This has just happened to me. I have installed the stock images 2 times now.
Is there anything you guys did differently to make it work?

My N5 decided to wipe the baseband and IMEI when I went to wipe the cache through recovery. Tried to reflash factory images 5 times and each time, when the phone boots up, hangouts, camera and gallery apps force close and I still have no network signal or IMEI/baseband.
Worst bit is all I did was wipe the cache partition, done that a million times and never had this problem
Anyone know what i can do?
I've relocked the bootloader for now but I can't call Google because my only phone is the Nexus 5 so that's out of the question.
Edit:
Managed to fix it by using a slightly different set of fastboot commands.
Here's what I did:
adb reboot bootloader
fastboot flash bootloader bootloader-hammerhead-HHZ11d.img
fastboot reboot-bootloader
fastboot flash radio radio-hammerhead-M8974A-1.0.25.0.17.img
fastboot reboot-bootloader
fastboot -w update image-hammerhead-krt16m.zip
fastboot reboot-bootloader
That worked for me

WRAITH07 said:
My N5 decided to wipe the baseband and IMEI when I went to wipe the cache through recovery. Tried to reflash factory images 5 times and each time, when the phone boots up, hangouts, camera and gallery apps force close and I still have no network signal or IMEI/baseband.
Worst bit is all I did was wipe the cache partition, done that a million times and never had this problem
Anyone know what i can do?
I've relocked the bootloader for now but I can't call Google because my only phone is the Nexus 5 so that's out of the question.
Click to expand...
Click to collapse
After you flash the factory image, boot into recovery and do a factory reset.

You mentioned a cache wipe. Was this in CWM or TWRP? My N5 hung trying to do a cache wipe in CWM. After rebooting the sdcard was inaccessible. The solution was to flash TWRP from fastboot, and do an advanced wipe of only the cache, and give it TIME. Like 5-10 minutes. After another reboot I had the sdcard and radio back, but some write permission issues. One more reboot and everything was ok again.
Sent from my Nexus 5 using Tapatalk

cmstlist said:
You mentioned a cache wipe. Was this in CWM or TWRP? My N5 hung trying to do a cache wipe in CWM. After rebooting the sdcard was inaccessible. The solution was to flash TWRP from fastboot, and do an advanced wipe of only the cache, and give it TIME. Like 5-10 minutes. After another reboot I had the sdcard and radio back, but some write permission issues. One more reboot and everything was ok again.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I had this issue while wiping cache in TWRP 2.6.3.0
Sent from my Nexus 5 using Tapatalk

[Q] Buying the phone today and rooting?

If I buy the S3 from a verizon store today brand new, will I be able to root it and unlock the boot loader still or will it come with a firmware too new?
Sorry if this was answered before. Tried searching but couldn't find results. If they are out there then I blame iOS 7 and my iPhone that needs replacing

I'm not sure what, if any, updates they've had in the last few months but I just got my s3 in August. I did take an update on it and had no issues with using casual to root & unlock. Perhaps someone may have a more recent experience.
Sent from my Slim GS3

Yes you will still be able to root, our 4.3 update hasn't happens yet
Sent from my SCH-I535 using xda app-developers app

Rooting is a great idea- I'm loving 4.4 on the s3.

clembrowning said:
Yes you will still be able to root, our 4.3 update hasn't happens yet
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
That's great to know. I take it I can use custom recovery, and replace the ROM entirely? I don't want to deal with an OTA removing root on me.
Thanks

fbiryujin said:
That's great to know. I take it I can use custom recovery, and replace the ROM entirely? I don't want to deal with an OTA removing root on me.
Thanks
Click to expand...
Click to collapse
You should have absolutely ZERO issues with rooting/using a custom recovery, etc... Casual couldn't be any easier.

MisterSprinkles said:
You should have absolutely ZERO issues with rooting/using a custom recovery, etc... Casual couldn't be any easier.
Click to expand...
Click to collapse
Not necessarily. If he gets a phone that was manufactured after ~July 2013, he'll have problems. There was apparently a silent change to the firmware/hardware/boot process that prevents any of the currently-available custom recovery packages from working. (Not clear on what the change was other than they apparently back-ported it from the GS4 and it requires a change to the recovery's kernel before anything will mount.) I've been fighting to get my brand new GS3 rooted and a custom ROM on it for almost two weeks now.
Trying to do so with Casual caused an endless boot-into-recovery loop because the recovery couldn't clear the cache and reset the 'boot into recovery' flag that ADB set; I was forced to flash back to stock recovery to fix that.
I did manage to get both TWRP and CWM loaded via ODIN, but every version I tried (dozens in all) refused to mount any partitions - it couldn't mount/read from /system or /data or /sdcard or /cache, so there's no way to flash anything. The closest I've come is by using the hacked-up versions of TWRP and CWM from this thread, but they're built for to Sprint phones, so now when booted into Recovery my phone thinks it's a Sprint and won't flash the VZW versions of anything.
So far, every person who's having this problem appears to have gotten their phone in the second half of this year, so I strongly suspect that buying one now will have the same result.

KutuluMike said:
Not necessarily. If he gets a phone that was manufactured after ~July 2013, he'll have problems. There was apparently a silent change to the firmware/hardware/boot process that prevents any of the currently-available custom recovery packages from working. (Not clear on what the change was other than they apparently back-ported it from the GS4 and it requires a change to the recovery's kernel before anything will mount.) I've been fighting to get my brand new GS3 rooted and a custom ROM on it for almost two weeks now.
Trying to do so with Casual caused an endless boot-into-recovery loop because the recovery couldn't clear the cache and reset the 'boot into recovery' flag that ADB set; I was forced to flash back to stock recovery to fix that.
I did manage to get both TWRP and CWM loaded via ODIN, but every version I tried (dozens in all) refused to mount any partitions - it couldn't mount/read from /system or /data or /sdcard or /cache, so there's no way to flash anything. The closest I've come is by using the hacked-up versions of TWRP and CWM from this thread, but they're built for to Sprint phones, so now when booted into Recovery my phone thinks it's a Sprint and won't flash the VZW versions of anything.
So far, every person who's having this problem appears to have gotten their phone in the second half of this year, so I strongly suspect that buying one now will have the same result.
Click to expand...
Click to collapse
Ah crap. Thanks for the warning. I decided to order a Verizon Moto X Dev Edition. Can't wait for that to arrive.
Thanks to everyone for the info/advice.

KutuluMike said:
Not necessarily. If he gets a phone that was manufactured after ~July 2013, he'll have problems. There was apparently a silent change to the firmware/hardware/boot process that prevents any of the currently-available custom recovery packages from working. (Not clear on what the change was other than they apparently back-ported it from the GS4 and it requires a change to the recovery's kernel before anything will mount.) I've been fighting to get my brand new GS3 rooted and a custom ROM on it for almost two weeks now.
Trying to do so with Casual caused an endless boot-into-recovery loop because the recovery couldn't clear the cache and reset the 'boot into recovery' flag that ADB set; I was forced to flash back to stock recovery to fix that.
I did manage to get both TWRP and CWM loaded via ODIN, but every version I tried (dozens in all) refused to mount any partitions - it couldn't mount/read from /system or /data or /sdcard or /cache, so there's no way to flash anything. The closest I've come is by using the hacked-up versions of TWRP and CWM from this thread, but they're built for to Sprint phones, so now when booted into Recovery my phone thinks it's a Sprint and won't flash the VZW versions of anything.
So far, every person who's having this problem appears to have gotten their phone in the second half of this year, so I strongly suspect that buying one now will have the same result.
Click to expand...
Click to collapse
Not necessarily true on that... I got mine last month... I did have issues with using the latest casual Root method, but the all-in-one casual Root works perfectly! But I would suggest downloading rom manager and letting that app install recovery for you (TWRP and cwm touch both caused issues for me). If you need a step by step, pm me and I'll write it up for you...
Sent from my SCH-I535 using xda premium

Macrodroid said:
Not necessarily true on that... I got mine last month... I did have issues with using the latest casual Root method, but the all-in-one casual Root works perfectly! But I would suggest downloading rom manager and letting that app install recovery for you (TWRP and cwm touch both caused issues for me). If you need a step by step, pm me and I'll write it up for you...
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I have no problem getting the recovery installed. The custom recoveries are just *non-functional* because they can't mount any partitions. The error logs' are pretty clear, and every custom recovery I've tried behaves exactly the same.

[Q] random shutdown and bootloop

Hello First post here so hopefully in the right place! I've got a nexus 5, UK model purchased around January time. I had rooted, running stock with SuperSU installed and a few apps installed with xposed mod.
It was running perfectly fine, until a few days back where I was required to reboot, it then got stuck at the Google screen and wouldn't go past that, I turned the phone off for a while and eventually could get into it.. Great, until it happened again.. I spoke to a friend who said perhaps it was the xposed which was causing it, so I flashed back to factory, ran it for a while and it was fine, so went back to root and tested it, was stable so I reinstalled xposed.. It then got stuck in the bootloop again, so flashed to factory certain that it was xposed causing issues. I'm now running factory, however the phone will still get stuck in bootloop but will also randomly reboot itself now.. Has anyone experienced this? After scanning the forums I can't find anything so hopefully someone can help!! My boot loader is still unlocked.
Thank you, Jordan.

arsenaljordan said:
Hello First post here so hopefully in the right place! I've got a nexus 5, UK model purchased around January time. I had rooted, running stock with SuperSU installed and a few apps installed with xposed mod.
It was running perfectly fine, until a few days back where I was required to reboot, it then got stuck at the Google screen and wouldn't go past that, I turned the phone off for a while and eventually could get into it.. Great, until it happened again.. I spoke to a friend who said perhaps it was the xposed which was causing it, so I flashed back to factory, ran it for a while and it was fine, so went back to root and tested it, was stable so I reinstalled xposed.. It then got stuck in the bootloop again, so flashed to factory certain that it was xposed causing issues. I'm now running factory, however the phone will still get stuck in bootloop but will also randomly reboot itself now.. Has anyone experienced this? After scanning the forums I can't find anything so hopefully someone can help!! My boot loader is still unlocked.
Thank you, Jordan.
Click to expand...
Click to collapse
Are you able to flash a custom recovery? like TWRP, PHILZ, CWM? try it.
if successful, flash a custom Rom. just to discard the possibility of emmc failure.

GUGUITOMTG4 said:
Are you able to flash a custom recovery? like TWRP, PHILZ, CWM? try it.
if successful, flash a custom Rom. just to discard the possibility of emmc failure.
Click to expand...
Click to collapse
I am able to flash a custom recovery and so forth, so wouldn't think it to be emmc failure.

arsenaljordan said:
I am able to flash a custom recovery and so forth, so wouldn't think it to be emmc failure.
Click to expand...
Click to collapse
It doesn't really exonerates emmc from being bad yet. now, wipe and flash a Rom, a stock/aosp based one

GUGUITOMTG4 said:
It doesn't really exonerates emmc from being bad yet. now, wipe and flash a Rom, a stock/aosp based one
Click to expand...
Click to collapse
I have already flashed the stock recovery and ROM back to the device