Database Info

NS4G- cm9 froze, pulled bat. stuck at boot, can access CWM Recovery, can't mnt SD

I'm was using CM9 nightly and it froze, I removed the battery and tried to boot but it hangs at Google screen.
I can access bootloader and recovery but, in CWM touch recovery, I can't mount or format system, sdcard, or data but can wipe and mount/unmount cache.
And I can't mount USB in recovery
I can access through fastboot, so what would I need to go about doing to get this thing back up and running?
I don't want to try to many things and screw it up worse or something. It seems to me like the partitions got screwed up or something, but that's just a wild guess. Can anyone help me fix this or point me in the right direction?

jivetrky said:
I'm was using CM9 nightly and it froze, I removed the battery and tried to boot but it hangs at Google screen.
I can access bootloader and recovery but, in CWM touch recovery, I can't mount or format system, sdcard, or data but can wipe and mount/unmount cache.
And I can't mount USB in recovery
I can access through fastboot, so what would I need to go about doing to get this thing back up and running?
I don't want to try to many things and screw it up worse or something. It seems to me like the partitions got screwed up or something, but that's just a wild guess. Can anyone help me fix this or point me in the right direction?
Click to expand...
Click to collapse
sounds like the sd(storage) is gone bad or going bad.

simms22 said:
sounds like the sd(storage) is gone bad or going bad.
Click to expand...
Click to collapse
Any way I could test that theory, through ADB or something?

jivetrky said:
Any way I could test that theory, through ADB or something?
Click to expand...
Click to collapse
maybe a logcat while trying to access the storage? but really, if it isnt accessible, thats all the info you should need.

Wow... internal memory already gone bad? Have you tried fastboot flash the factory images for ns4g?
Sent from my Nexus S 4G using XDA

rasengan82 said:
Wow... internal memory already gone bad? Have you tried fastboot flash the factory images for ns4g?
Sent from my Nexus S 4G using XDA
Click to expand...
Click to collapse
the internal storage going bad is actually a very common problem.

I guess locking bootloader and claiming warranty is the way to go.
Sent from my Nexus S 4G using XDA

rasengan82 said:
I guess locking bootloader and claiming warranty is the way to go.
Sent from my Nexus S 4G using XDA
Click to expand...
Click to collapse
How might I go about doing that?

jivetrky said:
How might I go about doing that?
Click to expand...
Click to collapse
fastboot oem lock
with fastboot while in the bootloader. provided that fastboot sees your device(fastboot devices).

Just a warning... if you oem lock you won't be able to oem unlock again IF you internal memory is indeed corrupted.
Sent from my Nexus S 4G using XDA

rasengan82 said:
Just a warning... if you oem lock you won't be able to oem unlock again IF you internal memory is indeed corrupted.
Sent from my Nexus S 4G using XDA
Click to expand...
Click to collapse
very true. but if youre doing it to send back to samsung for a warranty repair, does it matter?

I don't know the inner workings of Android or this device specifically, but isn't there just a single bit of flash on the phone which is divided/partitioned into SD, system, etc. Is it possible that the partitions have just been corrupted or something like that? I was playing around just seeing what the phone could do and Odin3 will recognize it, but I didn't want to play around and screw anything up even more than it is.
Is it possible to use Odin to try and attempt a fix? I see there is a re-partition option, I was wondering if that could be worth a try?

Well, I guess I've given up and I'll just hope for Samsung to replace/fix it.
Google-foo has not shown me anything as far as trying to repartition just in case it was corrupted or something; couldn't find any images out there with PITs. I'm able to write the bootloaders and recovery so I just used the one-click-stock provided boot and recovery images and flashed them with fastboot then locked it.
Doesn't boot and recovery go on the same flash that is theoretically bad which is stopping SD, system, & data from being mounted?

Just for the sake, what happens now if you do fastboot oem unlock?
Do you get an error? If you don't get an error, unlock it and then download this:
https://dl.google.com/dl/android/aosp/sojus-imm76d-factory-10660f4c.tgz
Unzip everything and put it on a folder (you will find several img files). Now start the phone again in fastboot mode.
fastboot flash bootloader bootloader-crespo4g-d720sprke1.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo4g-d720sprlc1.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot reboot

rasengan82 said:
Just for the sake, what happens now if you do fastboot oem unlock?
Do you get an error? If you don't get an error, unlock it and then download this:
https://dl.google.com/dl/android/aosp/sojus-imm76d-factory-10660f4c.tgz
Unzip everything and put it on a folder (you will find several img files). Now start the phone again in fastboot mode.
fastboot flash bootloader bootloader-crespo4g-d720sprke1.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo4g-d720sprlc1.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
I can't unlock it now, as the bootloader pops up a screen that says to unlock it you have to wipe/factory reset. But it hangs on that probably because it can't see system/data.
I did try flashing it with fastboot though, before I locked it, and I could flash boot, recovery, and radio but it will just hang forever on flashing system. It never gives an error. I let it sit there for over an hour and it never did anything.
So I guess now that it's locked there really is nothing I can do.

Ok, I think Samsung warranty is the only thing left.

Forgot to update, sent to Samsung and they replaced the PBA, so the flash was apparently bad. Thanks for the advice, everyone!
Was only about a week turn around, just took me a while to actually get the RMA started.
They even send a UPS label to ship it to them then took a week turnaround, overall it was good service.

Xoom 4g Stuck at Red M

My Xoom is a 3g that I sent in to have the 4g upgrade. Ive been running different roms for a couple years, decided to go back to stock the other day. I followed some steps I found at xda about how to do that, It was some version of honeycomb.
Anyways, after a reboot of the xoom It is stuck at the red M. I cannot get into recovery, cannon use adb commands. However, fastboot is working. What can I try next? After spending hours googling it, this doesnt seem real uncommon. But most of the links on how to put on a new bootloader with something called avalance 1.35 seem to be broke. Any ideas?

Your Xoom does not have an OS installed, nor a recovery.
Need to fastboot the stock images.

Mjamocha said:
Your Xoom does not have an OS installed. Flash a custom ROM
Click to expand...
Click to collapse
Correct. However, I cannot get into recovery to flash a rom. I have tried pushing the Motorola default through fastboot. It says it takes it but doesnt do anything.

ArXane said:
Correct. However, I cannot get into recovery to flash a rom. I have tried pushing the Motorola default through fastboot. It says it takes it but doesnt do anything.
Click to expand...
Click to collapse
yeah, i corrected my last comment.
hmmm .... odd

Mjamocha said:
yeah, i corrected my last comment.
hmmm .... odd
Click to expand...
Click to collapse
I have done the following:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
I got the files from the Motorola Support site.
I also used the RSD Lite to try and push factory image.

ArXane said:
I have done the following:
Click to expand...
Click to collapse
you forgot the last command
fastboot oem lock

Mjamocha said:
you forgot the last command
fastboot oem lock
Click to expand...
Click to collapse
Sorry, I have done that one also.

are you using the correct stock images for the 4G version?

Mjamocha said:
are you using the correct stock images for the 4G version?
Click to expand...
Click to collapse
Here are the links I have tried:
http://www.randomphantasmagoria.com/firmware/xoom/trygon4g/
HLK75D
I also tried the motorola image: MZ602_HLK75D that I had to request from Motorola.

It seems that what you have tried is the correct process. I too have the 4G Xoom (USA) and have used that process myself many times. However I used the "MZ600_HRI66" images, to return to stock with no problems. I may suggest to repeat the return to stock process using the HRI66 images.

Mjamocha said:
It seems that what you have tried is the correct process. I too have the 4G Xoom (USA) and have used that process myself many times. However I used the "MZ600_HRI66" images, to return to stock with no problems. I may suggest to repeat the return to stock process using the HRI66 images.
Click to expand...
Click to collapse
WIll try, thank you. Ever heard of everest 1.5 bootloader? It looks like that may be a common fix. All the links I find are broken.

Nope.... flashing HRI66 didnt change anything. Still cannot ADB, still doesnt boot.

no never heard of it. are you on everest?
adb wont work unless usb debugging is enabled, and you can't get into
USB debugging because you can't get into the system.
try this to place a recovery;
fastboot oem unlock
fastboot reboot
Get back into fastboot then grab a recovery image;
fastboot flash recovery (your recovery.img here)
if all else fails - go here - http://forum.xda-developers.com/showthread.php?t=1468298

Mjamocha said:
no never heard of it. are you on everest?
adb wont work unless usb debugging is enabled, and you can't get into
USB debugging because you can't get into the system.
try this to place a recovery;
fastboot oem unlock
fastboot reboot
Get back into fastboot then grab a recovery image;
fastboot flash recovery (your recovery.img here)
if all else fails - go here - http://forum.xda-developers.com/showthread.php?t=1468298
Click to expand...
Click to collapse
Tried flashing recovery with the stpes agove, same deal, cannot get into recovery. WIll try the LORD tool and will let you know.

[Q] Stuck in boot loop after recovery attempt

I'm trying to recover to stock after having a custom ROM for a few days (Cyanogenmod, nothing too fancy).
I was using this guide over on the Nexus dev forum:
http://forum.xda-developers.com/showthread.php?t=2513701
Everything went smoothly until after I flashed the bootunlocker zip to revert the tampered flag back to normal. Then the reboot loop happened.
I've flashed multiple times using both methods to no avail. I also updated the driver on Windows 7.

dabockster said:
I'm trying to recover to stock after having a custom ROM for a few days (Cyanogenmod, nothing too fancy).
I was using this guide over on the Nexus dev forum:
http://forum.xda-developers.com/showthread.php?t=2513701
Everything went smoothly until after I flashed the bootunlocker zip to revert the tampered flag back to normal. Then the reboot loop happened.
I've flashed multiple times using both methods to no avail. I also updated the driver on Windows 7.
Click to expand...
Click to collapse
Try to get into recovery and clear the caches and do a data factory reset. Just hold power down and power at the same time and select recovery.

gee2012 said:
Try to get into recovery and clear the caches and do a data factory reset. Just hold power down and power at the same time and select recovery.
Click to expand...
Click to collapse
This works, and it gets me working again. But I would like to reset that flag if possible. It all breaks when I flash the zip found here:
http://forum.xda-developers.com/showthread.php?t=2239421
The NexusBootUnlocker script is what is being referenced in the restoration guide.

dabockster said:
This works, and it gets me working again. But I would like to reset that flag if possible. It all breaks when I flash the zip found here:
http://forum.xda-developers.com/showthread.php?t=2239421
The NexusBootUnlocker script is what is being referenced in the restoration guide.
Click to expand...
Click to collapse
Did you boot into TWRP to flash the Bootlocker.zip? In cmd type `fastboot boot twrp.img` (or the name you have given it) and reboot?

dabockster said:
This works, and it gets me working again. But I would like to reset that flag if possible. It all breaks when I flash the zip found here:
http://forum.xda-developers.com/showthread.php?t=2239421
The NexusBootUnlocker script is what is being referenced in the restoration guide.
Click to expand...
Click to collapse
You can use that script with twrp by booting it as mentiomed above or if u r rooted then u can also use nexus bootunlocker from play store.

gee2012 said:
Did you boot into TWRP to flash the Bootlocker.zip? In cmd type `fastboot boot twrp.img` (or the name you have given it) and reboot?
Click to expand...
Click to collapse
Yep. I have done the guide to the letter and followed the video. Nothing.
And it might be worth noting that I am doing this on a red Nexus 5 (the new color). Maybe Google changed something?

dabockster said:
Yep. I have done the guide to the letter and followed the video. Nothing.
And it might be worth noting that I am doing this on a red Nexus 5 (the new color). Maybe Google changed something?
Click to expand...
Click to collapse
No, that doesn`t make a difference. What do you see when you type in cmd: `fastboot oem device-info` with the phone in bootloader?

gee2012 said:
No, that doesn`t make a difference. What do you see when you type in cmd: `fastboot oem device-info` with the phone in bootloader?
Click to expand...
Click to collapse
It shows that the bootloader is locked and the tampering flag is false, just like the tutorial said. However, normal boot results in a loop.

dabockster said:
It shows that the bootloader is locked and the tampering flag is false, just like the tutorial said. However, normal boot results in a loop.
Click to expand...
Click to collapse
So it worked, now go into recovery and wipe the caches and do a data factory reset and then it should boot normaly.

Don't use the zip then. Unlock the bootloader, root the phone and download bootunlocker app.
Then, reset tamper and lock from the app. Unroot using supersu
Sent from my Nexus 5 using Tapatalk

gee2012 said:
So it worked, now go into recovery and wipe the caches and do a data factory reset and then it should boot normally.
Click to expand...
Click to collapse
Nope, won't boot to recovery. All I have is the adb at the bootloader.
EDIT: Tried unplugging the USB while it was booting. This fixed everything! Thanks for the help!

dabockster said:
Nope, won't boot to recovery. All I have is the adb at the bootloader.
Click to expand...
Click to collapse
What happens when you type in cmd: fastboot reboot recovery ?

dabockster said:
Nope, won't boot to recovery. All I have is the adb at the bootloader.
Click to expand...
Click to collapse
When you say it won't boot into recovery do you get the dead android with the red exclamation mark? That is recovery just hit vol up
Sent from my Nexus 5

dabockster said:
Nope, won't boot to recovery. All I have is the adb at the bootloader.
Click to expand...
Click to collapse
You can't use adb at the bootloader
Only fastboot works
Sent from my Nexus 5 using Tapatalk

So I just tried booting it while unplugged from my computer and it worked flawlessly. This bit should be added to future unroot guides.
Thanks for the help!

[Q] Bricked one

os deleted and just stuck on one+ logo can boot in to twrp or fast boot what can i do?

brooklynchildxbc said:
os deleted and just stuck on one+ logo can boot in to twrp or fast boot what can i do?
Click to expand...
Click to collapse
Push a custom rom via adb and flash in recovery or flash stock images via fastboot

acuicultor said:
Push a custom rom via adb and flash in recovery or flash stock images via fastboot
Click to expand...
Click to collapse
i tried adb won't work and fastboot not doing anything i keeping getting a error saying that bootloader locked or can't erase
what really pisses me off i didn't even brick it a dumbass friend of mine did thinking he knew what he was doing.

brooklynchildxbc said:
i tried adb won't work and fastboot not doing anything i keeping getting a error saying that bootloader locked or can't erase
what really pisses me off i didn't even brick it a dumbass friend of mine did thinking he knew what he was doing.
Click to expand...
Click to collapse
Is fastboot working? Unlock bootloader and push custom recovery there. Go to adb sideload and that should work eventually. I had an issue with HTC One M7 - someone deleted sytem, and cyanogenmod installer helped, because it pushed CWM recovery, maybe try that one as well?

boober78 said:
Is fastboot working? Unlock bootloader and push custom recovery there. Go to adb sideload and that should work eventually. I had an issue with HTC One M7 - someone deleted sytem, and cyanogenmod installer helped, because it pushed CWM recovery, maybe try that one as well?
Click to expand...
Click to collapse
thank you so much i gave up then tried what you said then all of a sudden adb connected and i sideloaded the update file and got it back

brooklynchildxbc said:
thank you so much i gave up then tried what you said then all of a sudden adb connected and i sideloaded the update file and got it back
Click to expand...
Click to collapse
No problem. I'm glad I could help
Sent from my One using Tapatalk

brooklynchildxbc said:
thank you so much i gave up then tried what you said then all of a sudden adb connected and i sideloaded the update file and got it back
Click to expand...
Click to collapse
Don't give up.... I was in the same position like you for a couple days....and now is fix by my self..... If you unlock your bootloader try to lock back (fastboot oem lock) now try to flash via fastboot Philz Recovery ( try until is rebooting himself into recovery) .... After that put on a memory stick the new system .... You may need to mount the USB flash drive ..... That's exactly what I have done....Good Luck ...

It is damn near IMPOSSIBLE to actualy, truly "brick" these devices. There are way too many safeguards in place.
Be careful before announcing that you are "bricked". Bootlooping (which is what your device was doing) is not "bricked". As long as you have fastboot, you can always reflash recovery, and then use recovery to reflash your custom ROM (or you can bypass all of that and reflash the factory images from fastboot).
Don't panic, you know more than you think you know. Just don't get freaked out, and read. You'll be fine.

Help Me Unbrick?

Tried rooting my pixel 3 with XDA instructions. Phone bootlooped and went into recovery. Tried restarting, same issue. Tried factory reset, same issue.
I can still boot to fastboot, recovery, barcodes etc.
When the pixel 3 is in bootloader the device is not recognized by adb on mac or pc. Can someone help? Prefer to solve the issue through mac if possible but if PC is the only option I'll greatly appreciate your help too.

Solved
Figured it out. If anyone is in a similar situation here is how i got my phone working again on a mac.
1) ./adb kill-server
2) ./adb start-server
3) ./fastboot devices (to make sure your device is seen)
4) ./fastboot flash radio <radio.img> (probably didn't have to do this but made me feel safer for whatever reason)
5) ./fastboot reboot bootloader
6) ./fastboot -w update <image.img>
My phone then booted to my recovery which said that my OS was corrupt. After having a panic attack, I simply selected retry and BOOM my phone is back to working condition.

I'm love you??????
suhaybh said:
Figured it out. If anyone is in a similar situation here is how i got my phone working again on a mac.
1) ./adb kill-server
2) ./adb start-server
3) ./fastboot devices (to make sure your device is seen)
4) ./fastboot flash radio <radio.img> (probably didn't have to do this but made me feel safer for whatever reason)
5) ./fastboot reboot bootloader
6) ./fastboot -w update <image.img>
My phone then booted to my recovery which said that my OS was corrupt. After having a panic attack, I simply selected retry and BOOM my phone is back to working condition.
Click to expand...
Click to collapse
Thank you thank you thank you. The last part still got me confused, because I actually pulled from the zipped image file I had. I had an image file on hand, but it just wouldn't work. And I had no idea about the radio, so I just skipped since it didn't seem all that pertinent. This is the second time I've had to get it back to stock, but I couldn't remember for the LIFE of me how I did it. Even though it was literally two hours before this time. Hey! I just don't know when to quit!

suhaybh said:
Figured it out. If anyone is in a similar situation here is how i got my phone working again on a mac.
1) ./adb kill-server
2) ./adb start-server
3) ./fastboot devices (to make sure your device is seen)
4) ./fastboot flash radio <radio.img> (probably didn't have to do this but made me feel safer for whatever reason)
5) ./fastboot reboot bootloader
6) ./fastboot -w update <image.img>
My phone then booted to my recovery which said that my OS was corrupt. After having a panic attack, I simply selected retry and BOOM my phone is back to working condition.
Click to expand...
Click to collapse
Hello, I cannot unlock fastboot in a Pixel 3 XL and If I press the Button Recovery in Fastboot, the phone ia turning off. Any ideas? Thank you

robertoancini51 said:
Hello, I cannot unlock fastboot in a Pixel 3 XL and If I press the Button Recovery in Fastboot, the phone ia turning off. Any ideas? Thank you
Click to expand...
Click to collapse
Have you tried to flash the factory image? Also, did you do anything to the device, flash something, to get it to the point where it will only boot to the bootloader and won't boot into recovery?
Sent from my [device_name] using XDA-Developers Legacy app

jd1639 said:
Have you tried to flash the factory image? Also, did you do anything to the device, flash something, to get it to the point where it will only boot to the bootloader and won't boot into recovery?
Click to expand...
Click to collapse
If i cannot unlock the bootloader, is there any posibility to flash factory image? I didn't do anything to it, that's how I bought it.

robertoancini51 said:
If i cannot unlock the bootloader, is there any posibility to flash factory image? I didn't do anything to it, that's how I bought it.
Click to expand...
Click to collapse
Try flashing the factory image. The official firmware should flash. But make sure you have the latest sdk tools platform, r28.
Sent from my [device_name] using XDA-Developers Legacy app

jd1639 said:
Try flashing the factory image. The official firmware should flash. But make sure you have the latest sdk tools platform, r28.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I'm not sure what the rules are on cross posting but here's his OP https://forum.xda-developers.com/pixel-3-xl/help/google-pixel-3xl-fastboot-locked-t3885967
Can you flash a factory image with a locked bl? I thought not. Either a factory reset, perhaps sideload the OTA but that's about it IIRC. I'm also wondering where he got it from since it's not really clear.

bobby janow said:
I'm not sure what the rules are on cross posting but here's his OP https://forum.xda-developers.com/pixel-3-xl/help/google-pixel-3xl-fastboot-locked-t3885967
Can you flash a factory image with a locked bl? I thought not. Either a factory reset, perhaps sideload the OTA but that's about it IIRC. I'm also wondering where he got it from since it's not really clear.
Click to expand...
Click to collapse
I'm not sure if it will flash with the locked bootloader, but it's worth a try. He can't get into recovery so the ota, which would be my first suggestion, isn't an option. But if the device is new and came that way RMA of the best choice.
Sent from my [device_name] using XDA-Developers Legacy app

jd1639 said:
I'm not sure if it will flash with the locked bootloader, but it's worth a try. He can't get into recovery so the ota, which would be my first suggestion, isn't an option. But if the device is new and came that way RMA of the best choice.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I don't think he knows how to get into recovery and I also don't think this is a new device. He needs to read up on some things first. From entering recovery to platform tools to adb and fastboot commands. It's all out there he just needs to search a little.

bobby janow said:
I don't think he knows how to get into recovery and I also don't think this is a new device. He needs to read up on some things first. From entering recovery to platform tools to adb and fastboot commands. It's all out there he just needs to search a little.
Click to expand...
Click to collapse
You're probably right on recovery. It seems a lot of people don't know what to do once you get the "no command".
Sent from my [device_name] using XDA-Developers Legacy app

jd1639 said:
You're probably right on recovery. It seems a lot of people don't know what to do once you get the "no command".
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I was included in that first time I saw it. lol. Slight panic but the Google helped me out of it. Even knowing what to do it can be a little finicky.

jd1639 said:
Have you tried to flash the factory image? Also, did you do anything to the device, flash something, to get it to the point where it will only boot to the bootloader and won't boot into recovery?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
This is me right now. I can only boot into bootloader. I can't power off, start, or enter recovery mode. It just takes me back to bootloader. I have a mac. Any help would be appreciated!
Thanks!

abhinavkonagala said:
This is me right now. I can only boot into bootloader. I can't power off, start, or enter recovery mode. It just takes me back to bootloader. I have a mac. Any help would be appreciated!
Thanks!
Click to expand...
Click to collapse
Is your bootloader unlocked? Have you tried flashing the factory image?

abhinavkonagala said:
This is me right now. I can only boot into bootloader. I can't power off, start, or enter recovery mode. It just takes me back to bootloader. I have a mac. Any help would be appreciated!
Thanks!
Click to expand...
Click to collapse
For me the same here (bootloader is unlocked)
Device was rooted, and I only wanted to flash the march factory image...
Any help would be great! Thanks

LGFr.... said:
For me the same here (bootloader is unlocked)
Device was rooted, and I only wanted to flash the march factory image...
Any help would be great! Thanks
Click to expand...
Click to collapse
What happened exactly? If your bootloader unlocked, and have fastboot access, then you should be able to fastboot the factory image.

LGFr.... said:
For me the same here (bootloader is unlocked)
Device was rooted, and I only wanted to flash the march factory image...
Any help would be great! Thanks
Click to expand...
Click to collapse
You using sudo for fastboot and adb commands?
How'd you install platform tools? I know for me the only thing that worked on Mac was using Homebrew . All other methods were finicky at best