Database Info

[Q] NS4G is possesed

I have a strange situation going on with my phone and I could use some advice.
My issues started after loading the "official" IMM76D ROM, the rooted and odexed version. Phone would shut off like it was dead after charging all night. Wont boot back up without a battery pull. It would freeze up while the screen was on forcing a battery pull. Basically unusable for more than 10 minutes.
Here is where I might have messed things up. I tried to wipe the phone completely, including the SD card. Factory Reset multiple times, wiped everything multiple times. I even did a repartition of the SD card thinking it would format it further.
Where I'm at now. The phone still boots into the 4.0.4 ROM and I still have CM recovery. But now no matter what I do, factory reset, format/wipe EVERYTHING including the SD card, use fastboot to load a whole new setup, THE PHONE BOOTS RIGHT BACK INTO THE ROM AND SD CARD STILL HAS EVERYTHING. I dont get it.
I have ODIN 1.87 downloaded but it wont see my phone in download mode. I have all the correct drivers loaded including PDAnet, and my phone is correctly detected as Android ADB Device. Interesting side note: fastboot detects the phone, ADB does not. dont know if that means anything.
Sorry for the long winded post but I have been at this for 4 days now and I really need my phone back! Any ideas??

Maybe flash stock rom or CWM recovery from fastboot would solve the partitions issue. I remember when i had my old HTC magic i would sometimes change the partition layout and to reverse it i would have to reflash my recovery.
But as i said, this is all theory and can work or not.

[Q] Random Reboot and Reset

So i saw a lot of random reboot threads, but none like my problem. I'm running Embryo 6.11. I was using my phone today to take pictures and then the phone rebooted itself, but would not get past the Samsung glow logo. I waited about a minute and nothing, so I pulled the battery, waited about 5 minutes for the phone to cool down, just in case it was an overheating issue. Then I tried to reboot and the same thing happened, it got stuck at the glow logo. So i rebooted again, this time I got to my home screen, as soon as I tried to open an app, the phone rebooted and then it wouldn't get past the glow logo again. I pulled the battery, then put it back in and just charged the phone up while off, just in case i had to do a lot of stuff to it. So after i charged it up, I tried booting up again, no luck. So i booted into recovery, tried flashing the ROM over the current installation, in hopes that that would just fix the broken areas causing it not to boot, but it didn't, so i went back into recovery and did a full wipe and now i'm starting from scratch again. This happened a week ago today (the 15th) and it also happened on the 1st. I don't know what is going on, do I have a bad partition from doing the Sean 3x wipes in the past when i used skyICS (I don't do that anymore, just one wipe now), or maybe from using Darkside superwipe in the past?

fishlipsboy said:
So i saw a lot of random reboot threads, but none like my problem. I'm running Embryo 6.11. I was using my phone today to take pictures and then the phone rebooted itself, but would not get past the Samsung glow logo. I waited about a minute and nothing, so I pulled the battery, waited about 5 minutes for the phone to cool down, just in case it was an overheating issue. Then I tried to reboot and the same thing happened, it got stuck at the glow logo. So i rebooted again, this time I got to my home screen, as soon as I tried to open an app, the phone rebooted and then it wouldn't get past the glow logo again. I pulled the battery, then put it back in and just charged the phone up while off, just in case i had to do a lot of stuff to it. So after i charged it up, I tried booting up again, no luck. So i booted into recovery, tried flashing the ROM over the current installation, in hopes that that would just fix the broken areas causing it not to boot, but it didn't, so i went back into recovery and did a full wipe and now i'm starting from scratch again. This happened a week ago today (the 15th) and it also happened on the 1st. I don't know what is going on, do I have a bad partition from doing the Sean 3x wipes in the past when i used skyICS (I don't do that anymore, just one wipe now), or maybe from using Darkside superwipe in the past?
Click to expand...
Click to collapse
I had a similar issue on Embryo 7... ROM installed fine, worked fine for about a week then reboot and not going past the Samsung logo. What I found out was that the data and system partition were bad... running an e2fsck from adb shell while in recovery turned out a lot of logical errors (most of them were about inodes allocated to more files if I remember correctly but not only those). I found out while working on it that wiping these partitions from recovery is not fixing these errors.
What I did was I wiped everything (cache, data, system), ran e2fsck on each individual partition to fix the errors until no more were showing up then started from scratch (install ROM, restore apps, etc). So far, no more issues.

How do I run e2fsck? I'm not familiar with adb shell. I am a flasher and slight modder, but not a dev.

fishlipsboy said:
How do I run e2fsck? I'm not familiar with adb shell. I am a flasher and slight modder, but not a dev.
Click to expand...
Click to collapse
Reboot phone in recovery since you need those partitions unmounted. Connect phone to PC with USB then connect from PC with adb (run "adb shell"). If partitions (data, system, cache) are mounted you can unmount them from recovery.
Once you are in adb shell then you can run "e2fsck -fnv /dev/block/mmcblk0p24" to scan system partition. Repeat for data partition (mmcblk0p25), efs (mmcblk0p21), cache (mmcblk0p26), preload (mmcblk0p27). That will tell you only if you have errors; it will not fix them.
To fix them, run "e2fsck -fcyv /dev/block/<part name as above>".
You can also run "e2fsck" (with no parameters) to see the help and what each parameter means.
Also, see this great thread regarding the list of partitions in Skyrocket... http://forum.xda-developers.com/showthread.php?t=1629508
Hope this helps you. Let me know if you need more detailed instructions.
---------- Post added at 11:31 PM ---------- Previous post was at 11:27 PM ----------
fishlipsboy said:
How do I run e2fsck? I'm not familiar with adb shell. I am a flasher and slight modder, but not a dev.
Click to expand...
Click to collapse
BTW, if you find errors on your data and/or system partitions and choose to fix them, it does not mean that you phone will boot fine right away. Depending on how bad it is, you might need to reinstall the ROM.
Also, fixing the errors takes space (as *nix saves the recovered files under "lost+found" folder) so in my case, I chose to wipe the partitions from recovery first, then fix the errors and then re-install the ROM.

Brand new Nexus 5 DOA

The the device came in today and when I turn it on The Google logo comes, turns off and restarts for a boot loop. I even did a full restore using the recovery toolkit like swoggers and even then no luck. I was able to install twrp with no issue. Anyone have the same issue ?
Thanks

Anyone?

saadkhan07 said:
Anyone?
Click to expand...
Click to collapse
I had problems AFTER I installed TWRP, but before that it booted just fine.
My problems started after unlocking the bootloader and installing TWRP. Try wiping as much as possible (except System) with TWRP. I read somewhere it's a problem with the cache partition. I also went into "Mount" in TWRP (I think that's what it's called) and mounted System. I'm telling you all this from memory, not sure exactly how I fixed it, but eventually I was able to turn the phone on.
Hopefully this is the reason you're having problems. It'd be frustrating to have to try and get another one from the Goog.

[Q] Cannot wipe or flash anything, stuck in decryption screen.

I am stuck on the Decyption screen where it says "To start Android, enter your password". I have seen a few threads about this issue but they managed to solve the issue by reflashing or re-unlocking the bootloader. However, I am unable to do any of these things.
I have been on ViperOneM8 for quite a long time now and everything was working fine. I unlock my screen by swiping up on the screen while the screen is off. Felt the vibration to unlock but the screen stays blank. Had to force reboot it to make it work again. A few days later, this exact same issue happened again, but before I was able to reboot the device, it rebooted on its own and went into the said decryption screen. I enter a random word for password and it says, password is correct but data is corrupted; must factory reset to use phone.
Alright, so I have factory reseted, nothing happened. It wiped my data and sd card, same decryption screen.
I've used the bootloader to flash a stock android, I remember it succeeded but restarted to the same screen.
I've used twrp to re-flash multiple roms, all succeeded, restarted to same thing.
I've wiped data, full wipe, you name it, restarted to same thing. Once it reboots it would show the ViperOne boot, so something isn't wiping.
I even went into the phone's data and manually deleted everything in internal storage with my pc, restarted the phone, same thing. Checked the internal storage again, everything that was there got restored.
I've used adb and fastboot to push data, same thing. I've used the dottat .exe installer, goes through the entire process, reboots... same thing.
I've tried reflashing another recovery, success, but it boots into the same recovery.
I've tried doing the SuperCID and going through htcdev to unlock the device again, but it fails when pushing the key. SuperCID also resets whenever I restart the device. I've tried locking the bootloader with fastboot but that fails.
One thing I couldn't do is boot into the RUU mode. 'fastboot oem rebootRUU' doesn't seem to work for me. It reboots the device but boots up and goes into the decryption screen.
When I try the 0P6BIMG with bootloader, it seems to restart before completing the installation now. But I remember it went through successfully before, but still boots into the decryption screen.
It seems like no matter what I do, the phone restores itself to the previous state that it's in. That or nothing is actually affecting the data.
I am at a lost of what to do. I feel like maybe it's a damaged hardware but at the same time I am unsure. Anybody have any suggestions at all?

kyuuku said:
I am stuck on the Decyption screen where it says "To start Android, enter your password". I have seen a few threads about this issue but they managed to solve the issue by reflashing or re-unlocking the bootloader. However, I am unable to do any of these things.
I have been on ViperOneM8 for quite a long time now and everything was working fine. I unlock my screen by swiping up on the screen while the screen is off. Felt the vibration to unlock but the screen stays blank. Had to force reboot it to make it work again. A few days later, this exact same issue happened again, but before I was able to reboot the device, it rebooted on its own and went into the said decryption screen. I enter a random word for password and it says, password is correct but data is corrupted; must factory reset to use phone.
Alright, so I have factory reseted, nothing happened. It wiped my data and sd card, same decryption screen.
I've used the bootloader to flash a stock android, I remember it succeeded but restarted to the same screen.
I've used twrp to re-flash multiple roms, all succeeded, restarted to same thing.
I've wiped data, full wipe, you name it, restarted to same thing. Once it reboots it would show the ViperOne boot, so something isn't wiping.
I even went into the phone's data and manually deleted everything in internal storage with my pc, restarted the phone, same thing. Checked the internal storage again, everything that was there got restored.
I've used adb and fastboot to push data, same thing. I've used the dottat .exe installer, goes through the entire process, reboots... same thing.
I've tried reflashing another recovery, success, but it boots into the same recovery.
I've tried doing the SuperCID and going through htcdev to unlock the device again, but it fails when pushing the key. SuperCID also resets whenever I restart the device. I've tried locking the bootloader with fastboot but that fails.
One thing I couldn't do is boot into the RUU mode. 'fastboot oem rebootRUU' doesn't seem to work for me. It reboots the device but boots up and goes into the decryption screen.
When I try the 0P6BIMG with bootloader, it seems to restart before completing the installation now. But I remember it went through successfully before, but still boots into the decryption screen.
It seems like no matter what I do, the phone restores itself to the previous state that it's in. That or nothing is actually affecting the data.
I am at a lost of what to do. I feel like maybe it's a damaged hardware but at the same time I am unsure. Anybody have any suggestions at all?
Click to expand...
Click to collapse
Sounds like you have one of the few that have been popping up where the entire phone becomes write protected.
Before running the ruu run the following fastboot commands.
Fastboot oem task 28
Fastboot oem task 29
If any errors re-run the command.
Then run ruu.

dottat said:
Sounds like you have one of the few that have been popping up where the entire phone becomes write protected.
Before running the ruu run the following fastboot commands.
Fastboot oem task 28
Fastboot oem task 29
If any errors re-run the command.
Then run ruu.
Click to expand...
Click to collapse
I tried those commands and it looks successful, but once I rebootRUU it would just reboot and load to the decryption screen again.
I also tried the 0P6BIMG method after those commands, no luck.

kyuuku said:
I tried those commands and it looks successful, but once I rebootRUU it would just reboot and load to the decryption screen again.
I also tried the 0P6BIMG method after those commands, no luck.
Click to expand...
Click to collapse
Sounds like your phone did end up write protected. You need a new motherboard.
The ones I have seen like this don't even allow you to lock the boot loader or turn s back on either.

dottat said:
Sounds like your phone did end up write protected. You need a new motherboard.
The ones I have seen like this don't even allow you to lock the boot loader or turn s back on either.
Click to expand...
Click to collapse
Ahh that's too bad. It was what I expected though.
Thank you anyway for the help!

Nexus 5 not starting

Urgent help reqd
randomly my nexus 5 restarted
google came on screen and now only those four animated circles are showing up and the phone doesnt go further
went in bootloader but cant wipe cache, cant format, or anything else from there.
usb debuggng must be off as far as i remember
trying to flash through sdk manager. have downloaded image. but stops at "waiting for device" in cmd and it doesnt go any further than that. even tried doing it manually through cmd.
when the phone is connected it is showing the drivers but it isnt installng and can see the yellow exclamation.
manually downloaded the drivers and tried installing manually but shows drivers are up to date.
uninstalled driver and reinstalled but same issue. it is connected to usb 2.0.
now how do i get it to work?
I have tried all the options i could search for on this forum but none of them solved my issue.

Is the bootloader unlocked?

How do i check that?

Ok got it
It is locked
How do i unlock?

I checked some unlocking bootloader threads but they all require usb debugging to be on.
My phone is not starting at all so i cannot do that
How do i go about it now

Tried nexus root toolkit. It isnt detecting the device.

Unlocking will wipe you device.
Google themselves have a guide on how to flash, not sure why you are using toolkits.
Also, you will wipe your device, if you haven't already. Make sure you have the right drivers, make sure you get the device to come up under "fastboot devices"

Already tried all methods mentioned by google or xda.
If you read my initial post my phone is not getting detected as well but shows installing drivers when connected but the installation fails.

Manually install the correct drivers.

Tried that but i get the error that you already have latest drivers. But its not detecting the phone

Try removing the drivers and reinstalling
Also, try different USB ports and cables.

Did all of that a number of times. Still no luck

Other phones are getting connected and detected just fine.

useruser12 said:
Urgent help reqd
randomly my nexus 5 restarted
google came on screen and now only those four animated circles are showing up and the phone doesnt go further
.
Click to expand...
Click to collapse
Hi all, i have a similar problem
this morning my n5 boots into "optimizing apps", but stops when reach around 15/20 apps and reboot (3 or 4 times)...
Now, only keeps in android animation like useruser12.
I can see my data in TWRP, battery 95%...
I wipe cache/dalvik... nothing
I reflash the kernel (ElementalX 6.17), still nothing
Any ideas?
PS: latest news. After make a backup, I made a factory reset and restore a system-boot-cache partition from old backup. Now the phone boots but i hate lose all my data xD. I want try to solve my problem using my "corrupted" backup for avoid losing data. If that fails, I can always restore this functional backup. Any ideas again?

Used the nexus root toolkit.managed to unlock bootloader but immediately the device reboots and goes into the bootloop again.
Tried the flash stock + unroot function as well which detected my factory image and everything went smooth till it came back to unlocking the bootloader and rebooting the device after that and again went into the bootloop
Though i have installed the drivers, on reboot windows 7 automatically starts installing the mtp usb device driver but fails. Manually downloaded the drivers and installed as well.
Still its not worked and whatever i do it comes back and get stuck at the bootloop.
Any expert can give a solution? Thanks

After unlocking the bootloader, does the bootloader relock when the phone is rebooted? If it does, the memory chip is defective.

Phone doesnt reboot completely.goes into a loop after the google logo and doesnt go further.
If i switch off the phone midway here without it booting up and then restart the bootloader then its locked again.
But what i read was that the process of complete reboot needs to finish and i need to turn on usb debugging. So is it because of that the bootloader locks again?
Anyways, this what im facing

Dalamar666 said:
Hi all, i have a similar problem
this morning my n5 boots into "optimizing apps", but stops when reach around 15/20 apps and reboot (3 or 4 times)...
Now, only keeps in android animation like useruser12.
I can see my data in TWRP, battery 95%...
I wipe cache/dalvik... nothing
I reflash the kernel (ElementalX 6.17), still nothing
Any ideas?
PS: latest news. After make a backup, I made a factory reset and restore a system-boot-cache partition from old backup. Now the phone boots but i hate lose all my data xD. I want try to solve my problem using my "corrupted" backup for avoid losing data. If that fails, I can always restore this functional backup. Any ideas again?
Click to expand...
Click to collapse
Lucky that you could do a factory reset. I wasnt even able to do that from the bootloader.

useruser12 said:
Lucky that you could do a factory reset. I wasnt even able to do that from the bootloader.
Click to expand...
Click to collapse
Sorry, i did it via TWRP.

If the bootloader relocks itself upon reboot, it's the memory chip that is damaged.