Related
So, basically I am at a loss. I ususally spend enough time on problems like this until I solve them myself, but now I really need the help of others.
I rooted my Xperia X10i, installed some custom ROMs, everything went fine. The phone was still a bit buggy though, so I decided to go a step further.
So I unlocked the bootloader (using some threads from this forum), and had no issues with that either.
Then I installed the custom DoomKernel from here (the failsafe one!):
http://forum.xda-developers.com/showthread.php?t=1253853
It booted just fine, but I noticed I had no Wifi and my SIM card wasn't recognized. So I installed the Wifi modules that can be found in the same thread. I'm not sure which ROM I had on the phone at this point, since I tried many different ones.
The problem is now, that when trying to get the Wifi working, some time after a reboot the phone would ask my pin-code, and after that just gives a blue screen, instead of the usual home screen. I can slide my status bar down, and from there I can access some things, but not much. Basically I can only see that the phone does't seem to recognize my SIM card (even though it asked for the code?) and my wifi doesnt work either. Without a home screen I can't open my apps or anything.
I have since tried to install different ROMs. Again only the status bar works after a boot, besides that all I see is the standard background. Some ROMs can let me turn Flight Mode on from the status bar, and when I click it everyhting works again (except for any wifi or service, of course).
I have also tried to flash different kernels since, but nothing changed. So I used the SE PC Companion to get back to all the official SE 2.3.3 stuff. Still only the status bar works. I can still flash kernels and ROMs and boot into them succesfully, but I will always get a blank screen with just the status bar after tying my PIN code.
So... does anyone have a clue how to solve this issue? Any way to COMPLETELY restore all the phone's software, since updating or repairing using the PC Companion leaves the real problem untouched? Many thanks in advance!
Ok, resolved the issue. Apparently something went wrong while unlocking the bootloader. Restore it by clicking on "Restore" in the newest S1Tool (older versions don't have that button) and everything is solved. Just note that if you have a kernel running that requires an unlocked bootloader at the moment you restore the bootloader, obviously your device won't boot any more. Don't worry, just flash another kernel in that case.
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.
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...
Hello everyone, I have lots of issues with this tablet since I bought it. It works painfully slow, yet resetting it doesn't change anything, still the same problem. I also tried to root it via Kingroot and it werk, however it took me lot of time due to the system being unresponsive / unstable and almost useless. It comes with android 4.0.3 and I also tried looking up for any possibilites to reinstall the firmware since I'm extremely sure it could be caused from the firmware it also got installed from the factory. I also tried searching for custom roms and other ways around for TWRP or any custom recovery, but no result. I also tried up with the Flashify app to try extracting / backing up / dumping the recovery and the kernel but the app freezes up. I also tried a possibility to update the firmware from their official page, hence it failed to do so since it gives an error in their flashing software that dosen't tell me nor it logs it what it could be caused up from the connecting part.
primux.es/producto/tablets/tablet-primux-siroco-2-101/189
(not sure if anyone understands spanish thought but I can translate if needed)
This is the page from where I tried to download and install their software and their firmware down below on the page. primuxcomputers.es/primux/siroco2upgrade.pdf
There are the instructions where I tried to follow but at the "Imagen 9: Icono" part got me stuck in there. It requests me to insert the cable in the tablet holding the "Home" button and while holding it, plugging in the USB cable throught PC, and tap quickly the "Power" button 3 times. However it gives me a red X icon and yet nothing shows up in the devices: No ID, no other kind of detection no logs no nothing. After it showed up the X on the status, it disconnects itself and it changes to ready / green icon and plugs itself in again but nothing really happens to detect it again thought.
I also tried to boot in recovery mode but nothing happens menawhile Flashify keeps on the rebooting in recovery mode in loop doing nothing else... I'm seriously in pain with this tablet. And if you ask me to return it, not gonna even bother doing that..
I seriously hope any answer very soon and don't get dissapointed by the ignorance of this topic..
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.