Database Info

Cant flash Cyanogen, recovery faulty & weird crashes in stock on refurbished Nexus 5

Cant flash Cyanogen, recovery faulty & weird crashes in stock on refurbished Nexus 5
Hey guys,
so I recently got a "refurbished" replacement for my Nexus 5 and I decided since im starting out fresh (can't access the data on the old one), I'll try out Cyanogen mod.
I can assure you that I followed all the instructions exactly. At some point I checked every download for his checksums and all were ok.
Each time I started the process by flashing a factory image (flash-all.bat), to have a clean start.
I also tried to wipe cache/dalvik cache/data afterwards, but not always. This didn't change the behavior.
These things happened to me while trying to accomplish the task, and working around the issues as they arised:
Flashing TWRP: High (3 of 4) chance that TWRP wouldn't even start up, the phone would hang and just flash the TWRP background picture on screen.
When I did get through to TWRP, applying the Cyanogenmod .zip got stuck at "patching system image unconditionally". Let it go on for hours.
I figured that TWRP was broken and tried Clockworkmod instead. CWM at least always started after flashing it. But same as TWRP, it failed in installing the Cyanogenmod .zip. I tried putting it onto the phone by going into the stock android and then through adb push command, but also through sideloading directly into CWM.
What I noticed when going into the stock ROM was, that a lot of Google processes were failing during the initial setup (where it wants to know ur WiFi, date, Google acc, etc), like Maps, Settings, Play Services, and some others. Sometimes they were failing so hard it was impossible to type in the WiFi passphrase because the notifications of different "xxx has stopped working" were coming to fast, sometimes not a single one was failing. I could not find any pattern to this. When they were failing so hard I couldn't get through the initial setup I would just flash the stock again, until I got only some of them failing, or none at all.
Back to CWM and installing the Cyanogenmod .zip:
It failed with different errors. I got status 0, status 1, I think I once got status 6 or 7, but half of the time it hanged exactly where TWRP was hanging. The errors were random. After getting status X, I would sideload it right again, to get other status Y, sideload again, to get the hang. Could not recognize a pattern.
During this I switched USB ports, and cables, and even tried using my laptop instead of the desktop. One of the cables was faulty, it didn't even allow a connection, but any other setup showed the same behaviour.
Is there anything else I can/should try? Is it my fault, or is the phone bad?
Assuming the phone is bad, I suppose I still could get a stock running without the crashes, so it would _feel_ like the phone is alright (which is what Google probably did before sending it out again as "refurbished"), but I think there would be errors in the future, also I don't want a phone with such an uncertainty. Would they swap it? Also, it is a LG-D820, which means it might have issues with european LTE, haven't gotten to trying that out since I don't use LTE right now, nor will I in the near future.
Best regards,
napster

napstr said:
Hey guys,
so I recently got a "refurbished" replacement for my Nexus 5 and I decided since im starting out fresh (can't access the data on the old one), I'll try out Cyanogen mod.
I can assure you that I followed all the instructions exactly. At some point I checked every download for his checksums and all were ok.
Each time I started the process by flashing a factory image (flash-all.bat), to have a clean start.
I also tried to wipe cache/dalvik cache/data afterwards, but not always. This didn't change the behavior.
These things happened to me while trying to accomplish the task, and working around the issues as they arised:
Flashing TWRP: High (3 of 4) chance that TWRP wouldn't even start up, the phone would hang and just flash the TWRP background picture on screen.
When I did get through to TWRP, applying the Cyanogenmod .zip got stuck at "patching system image unconditionally". Let it go on for hours.
I figured that TWRP was broken and tried Clockworkmod instead. CWM at least always started after flashing it. But same as TWRP, it failed in installing the Cyanogenmod .zip. I tried putting it onto the phone by going into the stock android and then through adb push command, but also through sideloading directly into CWM.
What I noticed when going into the stock ROM was, that a lot of Google processes were failing during the initial setup (where it wants to know ur WiFi, date, Google acc, etc), like Maps, Settings, Play Services, and some others. Sometimes they were failing so hard it was impossible to type in the WiFi passphrase because the notifications of different "xxx has stopped working" were coming to fast, sometimes not a single one was failing. I could not find any pattern to this. When they were failing so hard I couldn't get through the initial setup I would just flash the stock again, until I got only some of them failing, or none at all.
Back to CWM and installing the Cyanogenmod .zip:
It failed with different errors. I got status 0, status 1, I think I once got status 6 or 7, but half of the time it hanged exactly where TWRP was hanging. The errors were random. After getting status X, I would sideload it right again, to get other status Y, sideload again, to get the hang. Could not recognize a pattern.
During this I switched USB ports, and cables, and even tried using my laptop instead of the desktop. One of the cables was faulty, it didn't even allow a connection, but any other setup showed the same behaviour.
Is there anything else I can/should try? Is it my fault, or is the phone bad?
Assuming the phone is bad, I suppose I still could get a stock running without the crashes, so it would _feel_ like the phone is alright (which is what Google probably did before sending it out again as "refurbished"), but I think there would be errors in the future, also I don't want a phone with such an uncertainty. Would they swap it? Also, it is a LG-D820, which means it might have issues with european LTE, haven't gotten to trying that out since I don't use LTE right now, nor will I in the near future.
Best regards,
napster
Click to expand...
Click to collapse
Hi.
According to what you say, it seems an hardware problem of you phone. Don't know if it may help but you can try installing an older factory image (for example kitkat) and seeing if the "force closing" problems are still there. If your phone is ok it should be able to run a factory image at least.

Download the nexus root toolkit, create a nandroid backup, then when either in CWM or TWRP wipe everything off the phone then try to flash a ASOP rom like Cataclysm if nothing else works then I don't know how to help sorry-.-

So I tried to get the stock ROM up and running again, and it seems even that is not possible. Several processes keep crashing during various tasks, even when idling. After having a short chat with Google Support about the issues I got an RMA offered, so things are cool. I locked the phone again, set the tamper-bit to false and wiped everything.

Galaxy S6 - freezing and rebooting 50+ times a day

I've got a Vodafone UK version SM-G920F that has recently started to freeze, crash and reboot constantly.
I managed to back up my data and perform a factory reset from the Setting page, but it crashed 10+ times during the install process (would freeze at various different stages, either rebooting on its own, or requiring a Vol Down+Power reset)
I'm now on a fresh install, but it's still rebooting constantly. I managed to use it like normal for an hour today, but right now it's just rebooted 3 times and won't even get past the Samsung loading screen without several Vol Down+Power resets.
What other options do I have? And is anyone aware of a known hardware issue that could cause this?
I was considering flashing a different ROM, but I'm scared it would reboot during the process and corrupt something...

robjg said:
I've got a Vodafone UK version SM-G920F that has recently started to freeze, crash and reboot constantly.
I managed to back up my data and perform a factory reset from the Setting page, but it crashed 10+ times during the install process (would freeze at various different stages, either rebooting on its own, or requiring a Vol Down+Power reset)
I'm now on a fresh install, but it's still rebooting constantly. I managed to use it like normal for an hour today, but right now it's just rebooted 3 times and won't even get past the Samsung loading screen without several Vol Down+Power resets.
What other options do I have? And is anyone aware of a known hardware issue that could cause this?
I was considering flashing a different ROM, but I'm scared it would reboot during the process and corrupt something...
Click to expand...
Click to collapse
Maybe a battery issue?

a friend just gave me his very same model phone with the very same issues.. if I find out anything I'll tell you here, or if you solve it first please write down what you did.

Thanks Vibbuz.
I've been trying to download a stock firmware to flash via Odin, but download speeds from Updato are really bad.

So I managed to flash a firmware after installing Odin on a Windows laptop (painful trying to get it to work on my Mac)
Firmware installed OK, but after boot I was getting a constant "com.sec.epdg" pop-up box that wouldn't let me use the phone at all. Not sure if that's due to the tsar3000 firmware?
Wiped the cache and did a factory reset after booting into recovery, and now it's stuck in a boot-loop again (95% of the time it hangs at the Samsung logo animation)

Just tried using SamFirm v0.3.6 to find the correct file. Downloaded a 4gb file, but several attempts to extract only gives BL, CP, CSC files but no AP (throws up an Unknown Error during process).
So still stumped!

Yet another update. Left Updato running overnight and downloaded a firmware.
Flashed it with Odin, claims to have succeeded but phone then reboots and hangs at "Erasing" stage (Android logo is spinning, then stops)
I'm starting to think it's pretty broken...

I've been having this exact same issue since June. If your phone happens to boot try activating power saving mode (to reduce cpu speed) as soon as possible.
It seems that doing that diminished the frequency in which my phone rebooted. If it also helps you it might be a faulty battery that can't provide enough voltage. (I'm not 100% sure on this part though, just thought of it because of the apple batteries drama)
Please post your results! Looks like a lot of people are affected by this and it would be great if we could find the cause of the problem.

I just read your thread actually! Sounds very similar to mine.
I've got nowhere. I don't think it's hard-bricked as I can still access Odin mode on the phone, and sometimes boots to Recovery, but it freezes and various different points and is currently unusable (either freezes at Samsung logo, "Erasing" part after installing firmware, or once it started to run though new device setup then froze).
Went ahead and bought an S8, but still want to fix the S6!

robjg said:
I've got a Vodafone UK version SM-G920F that has recently started to freeze, crash and reboot constantly.
I managed to back up my data and perform a factory reset from the Setting page, but it crashed 10+ times during the install process (would freeze at various different stages, either rebooting on its own, or requiring a Vol Down+Power reset)
I'm now on a fresh install, but it's still rebooting constantly. I managed to use it like normal for an hour today, but right now it's just rebooted 3 times and won't even get past the Samsung loading screen without several Vol Down+Power resets.
What other options do I have? And is anyone aware of a known hardware issue that could cause this?
I was considering flashing a different ROM, but I'm scared it would reboot during the process and corrupt something...
Click to expand...
Click to collapse
Does it have twrp? Try a non stock ROM and kernel

So did anyone manage to find an issue in this rebooting. I am having the same issue.

damir_nis said:
So did anyone manage to find an issue in this rebooting. I am having the same issue.
Click to expand...
Click to collapse
Hi I have same Problem I send the my s6 for repairmen that Saied me this problem related to mobile Hard drive.
I didn't believe it and try some official rom and a rom from Philippine GLB solve my problem for 3 M/o but now developed as same problem whitout any successful rom installation.
I think this problem from incompatibility google play store version to my rom. please flash a custom rom without google apps and immediately after installation turned off data and Wi-Fi internet after 2 day whit sim card whit out any change in setting can use it.

Hello,
anyone found some kind of solution? Happened to me also - freezing, restarts and then my S6 stopped working.. Sometimes I can boot to recovery menu, sometimes it boots up to android (and then freezes again), but the chances are almost non existing. Service man told me the same thing as @ghasemzm - eMMC failure. Yes, it is completely possible, but i don't wanna believe it, because they only tried to reflash the rom. I've made some "google research" and found that there were some issues in power IC on S6/S6E. Could this be related to it?

ghasemzm said:
Hi I have same Problem I send the my s6 for repairmen that Saied me this problem related to mobile Hard drive.
I didn't believe it and try some official rom and a rom from Philippine GLB solve my problem for 3 M/o but now developed as same problem whitout any successful rom installation.
I think this problem from incompatibility google play store version to my rom. please flash a custom rom without google apps and immediately after installation turned off data and Wi-Fi internet after 2 day whit sim card whit out any change in setting can use it.
Click to expand...
Click to collapse
Will test the theory and let the group know.

So i have installed philipines latest update 6.0.1 i think with PIT file provided on Sammobile.
I have tested it for a day with normal ussage like i set up every other phone and it still continued restarting.
Figured out let me test with no google account signed in and the phone is working perfectly. For a full day.
So i dont know what the problem is but i will try again with google account tomorrow for a day see what happens.
After that will install 7.0.1 uk update with PIT file for it and test with that.

I have the same problem and I am quite sure that it is the mobile hard drive.
I tried to use F2FS but didn't find a working rom for that.
Samsung refused repair because of root.... Never Samsung again!

same issues here - any solutions found? My best guess is hardware fault...

Debugging J7 Prime Restart issue

Pardon for a long story but someone gave this Samsung J7 Prime(SM-G610F) to me with an issue "An Error Has Occurred While Updating The Device Software". So I gave Samsung Smart Switch a try sadly they removed the Initialize option and old version don't seam to do what it suppose to do so I wen to a traditional Odin flashing. I then look for a stock rom for the phone that I think is the right one. Started with android 6 MM region pakistan and flashing went well. I was able to use it for a good hour or two until I notice it restarted by it self, then it keeps doing it 10-20 seconds after booting up. I though its the firmware I'm using so I went and look for Oreo version this time I region india (I don't know if region matters). So I flashed it again and tested the device again. I'm still able to use it for a good while till it restarted again. I then keep testing it to see what may be causing the problem. I notice that when the WIFI is on it just crash the phone to reboot so as soon as the phone reboots I turned the wifi off and it didn't crash anymore. I then factory reset the phone cleared everything, wipe cache then installed benchmark tools first. Thing I notice is it crashes when Google Play store is trying to install or download something. I tested it a couple of times to see when it crash and it does crash when downloading or installing something. I was still able to install 3Dmark and run it with wifi off. It completed the test without crashing so it couldn't the processor issue. I then look for another rom and tried flashing it. This time I had issue with it failing at system.img even if I use recent rom that worked. I then keep trying till flashing TWRP worked and flashing the rest of the rom is fine again.
What bothers me is why doesn't it crash during the first couple of hours. I've search similar issues and they say it may have been and app issue. I've already disabled bunch of app but nothing changed. Run the phone in safe mode but this time instead of crashing and rebooting right away it freezes for a few seconds. I suspect if google play or something being an issue since I've tried disabling it and it didn't crash for a couple of hours. Looked for allot of related thread but none of them seam to solve my problem.
I suspect either its the rom that I'm using and it can only be fixed by using the original rom, or its having a memory issue but don't know how to pin point it. Anyone can suggest on how I can debug this? I'm used to debugging things in real time and my knowledge with android is a quite slim but as a programming understanding the errors won't be a problem. I hope.
Edit: Hmm. Does copying kernel log with TWRP work or the kernel logs get overwritten every time the phone reboots? Because I see the kernet logs but don't see anything failing except for something saying SHUTDOWN but I don't think thats it. :S

Still no reply. :S I think its /system dismounting it self while doing a write operation. but it doesn't trigger until a certain amount of time after the phone is flashed or factory reset. I have to go to recovery and mount system back but that only happens on marshmallow. over version it remounts it self after the random reboot. After factory reset I'm able to install COD mobile and play a couple of match. after a long while it just decides to reboot.
I also tried z3x and after reading PIT from phone OK. the phone just reboots and flashing completes without it doing any flashing.

Hoping someone can help rescue my phone.( Moto G5)

Hi everyone last night i decided to root my ohone. I have had it for a while but for some reason hadn't got round to doing it.
I followed all the instructions firstly unlocking bootloader, TWRP then installing no verity and magisk etc and every looked to be good phone starts up with the the your device has been unlocked message and something about bad id key but then would start like normal and set about installing all my apps etc again for the phone to be back to how it was just rooted.
However tonight i restarted my phone and when it's went to start up it throws me into the fast loader screen wtih your device didnt stat up successfully use the software repair assistant on computer to repair your device.
I had only been installing my usual apps/ new luancher etc... however the only thing i think that could have caused an issue was i checked for an android version update and it found i already had the most up to date one so nothing was downloaded but possibly just checking has caused an issue ?
Any help with this would be appreciated.
I can still boot into team win recovery mode but was hoping as i've now installed everything a new... i could resolve this without another fresh install if possible ?
Thanks

fendertele said:
Hi everyone last night i decided to root my ohone. I have had it for a while but for some reason hadn't got round to doing it.
I followed all the instructions firstly unlocking bootloader, TWRP then installing no verity and magisk etc and every looked to be good phone starts up with the the your device has been unlocked message and something about bad id key but then would start like normal and set about installing all my apps etc again for the phone to be back to how it was just rooted.
However tonight i restarted my phone and when it's went to start up it throws me into the fast loader screen wtih your device didnt stat up successfully use the software repair assistant on computer to repair your device.
I had only been installing my usual apps/ new luancher etc... however the only thing i think that could have caused an issue was i checked for an android version update and it found i already had the most up to date one so nothing was downloaded but possibly just checking has caused an issue ?
Any help with this would be appreciated.
I can still boot into team win recovery mode but was hoping as i've now installed everything a new... i could resolve this without another fresh install if possible ?
Thanks
Click to expand...
Click to collapse
You could try reflashing the boot.img
What does getvar all say?
Code:
fastboot getvar all

Question Stucked in bootloop

Hey,
I have got Xiaomi POCO X3 PRO NFC 8/256GB, most probably have android 11 MIUI 12.5.5 global, in EU. Been using automatic updatese. Please note, that I haven't flashed any custom software. Have been using vanilla OS since release and been updating it with automatic updates.
Suddenly my phone has entered bootloop state and I am not able to take it out of it since.
Latest action I have taken just before the problem started is that I connected my phone to charger during the game ( PGR) , while it was at around 40% charge. After short moment it has frozen and restarted the phone. Since then it has been constantly bootlooping with POCO icon and resetting again, turning off the screen and back to POCO icon - it has been for over 2 hours already. It doesn't feel that my power button is stuck.
Still can operate power + vol buttons reliably. I can access Fastboot and MIUI Recovery Menu 5.0, where I have 4 options:
1. Reboot - back to bootloop
2. Wipe data - haven't tried it yet
3. Connect to MIAssistant - TIL it is supposedly dead service?
4. Safemode - it brings me back to bootloop again
Tried to take out SIM and microsd, to no avail. Haven't tried to wipe out data until I try other solutions, to restore it, as I have some 2FA on it, which would be a pain to recover.
I haven't learned before around flashing and recovery for the last few years (only I have done it around android 4, 5 and 6). I would like request assistance - how to approach resolving this problem?
Currently I am reading on fastboot, which I believe might help me here, by connecting it to PC.
EDIT: Got around this https://xiaomiflashtool.com/tutorial/use-xiaomi-flash-tool and stock rom https://xiaomistockrom.com/xiaomi-poco-x3-pro , I believe it might work
EDIT #2: At 20.11.2022. At around end of october this issue started repeating out of nowhere. And then suddenly stop,
Then the phone bricked. Sent for warranty and just got it back.
Turns out that motherboard died and was the cause.

gol_galad said:
Hey,
I have got Xiaomi POCO X3 PRO NFC 8/256GB, most probably have android 11 MIUI 12.5.5 global, in EU. Been using automatic updatese. Please note, that I haven't flashed any custom software. Have been using vanilla OS since release and been updating it with automatic updates.
Suddenly my phone has entered bootloop state and I am not able to take it out of it since.
Latest action I have taken just before the problem started is that I connected my phone to charger during the game ( PGR) , while it was at around 40% charge. After short moment it has frozen and restarted the phone. Since then it has been constantly bootlooping with POCO icon and resetting again, turning off the screen and back to POCO icon - it has been for over 2 hours already. It doesn't feel that my power button is stuck.
Still can operate power + vol buttons reliably. I can access Fastboot and MIUI Recovery Menu 5.0, where I have 4 options:
1. Reboot - back to bootloop
2. Wipe data - haven't tried it yet
3. Connect to MIAssistant - TIL it is supposedly dead service?
4. Safemode - it brings me back to bootloop again
Tried to take out SIM and microsd, to no avail. Haven't tried to wipe out data until I try other solutions, to restore it, as I have some 2FA on it, which would be a pain to recover.
I haven't learned before around flashing and recovery for the last few years (only I have done it around android 4, 5 and 6). I would like request assistance - how to approach resolving this problem?
Currently I am reading on fastboot, which I believe might help me here, by connecting it to PC.
EDIT: Got around this https://xiaomiflashtool.com/tutorial/use-xiaomi-flash-tool and stock rom https://xiaomistockrom.com/xiaomi-poco-x3-pro , I believe it might work
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/

NOSS8 said:
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
Click to expand...
Click to collapse
Thanks, will follow this to make back up and in case it occurs again.
Managed to resolve this problem by draining up my battery due to constant restarts(obviously can't pull out battery). After that happened, connected my phone to normal charger, juiced it up to 10% and phone started just fine.
I have tried to recreate this problem, however it didn't occur again.