I've had my phone for about two months now without any issues. I have it rooted with the stock rom. Today I was getting a red wifi calling notification. When I finally went to check it, it was error that said cannot start so I turned it off and back on to see if that would resolve anything. Since then my phone has been constantly rebooting. It comes on and stays on for about two minutes before rebooting again. I've been able to reach the settings and turn wifi calling off but that hasn't helped. I want to try to maybe disable the app or whatever runs it and try clearing it's data, so my question finally is does anyone know which app I would be looking for under all apps so I could give that a try.
ghettovirtuoso said:
I've had my phone for about two months now without any issues. I have it rooted with the stock rom. Today I was getting a red wifi calling notification. When I finally went to check it, it was error that said cannot start so I turned it off and back on to see if that would resolve anything. Since then my phone has been constantly rebooting. It comes on and stays on for about two minutes before rebooting again. I've been able to reach the settings and turn wifi calling off but that hasn't helped. I want to try to maybe disable the app or whatever runs it and try clearing it's data, so my question finally is does anyone know which app I would be looking for under all apps so I could give that a try.
Click to expand...
Click to collapse
I'm having a very similar issue. Stock M8 running latest T-mobile firmware. Rooted. Flashed PhilzCWMtouch and now the phone reboots every 1-3 minutes. I flashed the original recovery via fastboot and it is still rebooting. Going to redownload the stock recovery and try flashing it again before I do a full restore. I really want to avoid that if possible.
cheasfridge said:
I'm having a very similar issue. Stock M8 running latest T-mobile firmware. Rooted. Flashed PhilzCWMtouch and now the phone reboots every 1-3 minutes. I flashed the original recovery via fastboot and it is still rebooting. Going to redownload the stock recovery and try flashing it again before I do a full restore. I really want to avoid that if possible.
Click to expand...
Click to collapse
Thanks for the reply, but I gave up last night trying to fix it from the current state. I restored a nandroid from the previous week and used titanium to infuse data into already installed apps and restore missing apps. I do hope you find success in getting your issue to stop. I haven't had problem using TWRP on this phone, maybe give that a try
ghettovirtuoso said:
Thanks for the reply, but I gave up last night trying to fix it from the current state. I restored a nandroid from the previous week and used titanium to infuse data into already installed apps and restore missing apps. I do hope you find success in getting your issue to stop. I haven't had problem using TWRP on this phone, maybe give that a try
Click to expand...
Click to collapse
I finally was able to fix it after flashing twrp and then doing a wipe from there. then updated superSU and everything seems fine now. sorry about the different accounts. I need to delete that other one.
Sent from my HTC One_M8 using Tapatalk
ghettovirtuoso said:
I've had my phone for about two months now without any issues. I have it rooted with the stock rom. Today I was getting a red wifi calling notification. When I finally went to check it, it was error that said cannot start so I turned it off and back on to see if that would resolve anything. Since then my phone has been constantly rebooting. It comes on and stays on for about two minutes before rebooting again. I've been able to reach the settings and turn wifi calling off but that hasn't helped. I want to try to maybe disable the app or whatever runs it and try clearing it's data, so my question finally is does anyone know which app I would be looking for under all apps so I could give that a try.
Click to expand...
Click to collapse
Lemme ask you......... did you root your phone BEFORE or AFTER receiving any OTAs?
I have T-Mobile and the M8 too. I rooted my phone AFTER getting the OTA, and I'm pretty sure that's what caused all hell to break loose. My phone wasn't like yours at first, for weeks it would randomly go into Recovery mode............ but then this past week it started doing that: constantly rebooting. I didn't have a backup that was pre-root, only post-root (rookie mistake lol), so having to replace it now. Using the post-root is just a temporary fix as it can still go back to non-stop reboot at anytime, but the new phone comes in Tuesday.
Please let me know.
Good luck! (Not sure if that's you in the other post that said it's been fixed).
Thank You,
RockStar2005
RockStar2005 said:
Lemme ask you......... did you root your phone BEFORE or AFTER receiving any OTAs?
I have T-Mobile and the M8 too. I rooted my phone AFTER getting the OTA, and I'm pretty sure that's what caused all hell to break loose. My phone wasn't like yours at first, for weeks it would randomly go into Recovery mode............ but then this past week it started doing that: constantly rebooting. I didn't have a backup that was pre-root, only post-root (rookie mistake lol), so having to replace it now. Using the post-root is just a temporary fix as it can still go back to non-stop reboot at anytime, but the new phone comes in Tuesday.
Please let me know.
Good luck! (Not sure if that's you in the other post that said it's been fixed).
Thank You,
RockStar2005
Click to expand...
Click to collapse
I rooted preOTAs. Pretty much as soon I got the phone. I have been unsuccessful in stopping the problem as of yet but am going to RUU in a few minutes. Prior to this I've only tried factory resets from within the OS and from the bootloader wiping everything including data and external sd. Hope this RUU provides me some peace.
ghettovirtuoso said:
I rooted preOTAs. Pretty much as soon I got the phone. I have been unsuccessful in stopping the problem as of yet but am going to RUU in a few minutes. Prior to this I've only tried factory resets from within the OS and from the bootloader wiping everything including data and external sd. Hope this RUU provides me some peace.
Click to expand...
Click to collapse
It almost seems like this (my) phone hates to be rooted. As soon as I restore to pre-root backup, it's fine. I hate not being rooted.
Software No: 1.57.531.7
It did the constant reboot (after about 1 minute of being loaded) with both stock, rooted and with Skydragon 2.3 rom. Very irritating. It seems to happen when I unplug it from the charger or pc, while rebooting.
chattguy said:
It almost seems like this (my) phone hates to be rooted. As soon as I restore to pre-root backup, it's fine. I hate not being rooted.
Software No: 1.57.531.7
It did the constant reboot (after about 1 minute of being loaded) with both stock, rooted and with Skydragon 2.3 rom. Very irritating. It seems to happen when I unplug it from the charger or pc, while rebooting.
Click to expand...
Click to collapse
I was having the same problems. I'm getting my replacement phone today. My current one is only working (for now) b/c I did a restore, but not far back enough for it to be working 100% right. I'm working with someone who might have a plan, so we'll see. He said he did everything, including root and S-OFF, and got Harman/Kardon sound too (on his non-Sprint phone). I'll post again here when I get more info. First gotta get my replacement phone. lol I had H/K but I think rooting it after the OTA messed it up, but we'll see. H/K did improve the sound, so I really want it back.
RockStar2005
chattguy said:
It almost seems like this (my) phone hates to be rooted. As soon as I restore to pre-root backup, it's fine. I hate not being rooted.
Software No: 1.57.531.7
It did the constant reboot (after about 1 minute of being loaded) with both stock, rooted and with Skydragon 2.3 rom. Very irritating. It seems to happen when I unplug it from the charger or pc, while rebooting.
Click to expand...
Click to collapse
Mine too. I RUU'd back to stock and unlocked bootloader. Before anything else I made a backup. Rooted and the problem presented itself again. Restored backup but chose not to root and my phone has been fine thus far. Never used an android without root so this should be interesting.
ghettovirtuoso said:
Mine too. I RUU'd back to stock and unlocked bootloader. Before anything else I made a backup. Rooted and the problem presented itself again. Restored backup but chose not to root and my phone has been fine thus far. Never used an android without root so this should be interesting.
Click to expand...
Click to collapse
Yeah man, I hope they come up with a fix for it, I don't want to be unrooted forever.
ghettovirtuoso said:
Mine too. I RUU'd back to stock and unlocked bootloader. Before anything else I made a backup. Rooted and the problem presented itself again. Restored backup but chose not to root and my phone has been fine thus far. Never used an android without root so this should be interesting.
Click to expand...
Click to collapse
He's working to help me out. Maybe he can fix your issue too? Still waiting for him to write me a guide for my specific issues, so can't verify anything, but sounds like he's helped a lot of ppl on here already. Check him out:
http://forum.xda-developers.com/showthread.php?t=2718130
Good luck!
RockStar2005
---------- Post added at 03:01 PM ---------- Previous post was at 03:00 PM ----------
chattguy said:
Yeah man, I hope they come up with a fix for it, I don't want to be unrooted forever.
Click to expand...
Click to collapse
He's working to help me out. Maybe he can fix your issue too? Still waiting for him to write me a guide for my specific issues, so can't verify anything, but sounds like he's helped a lot of ppl on here already. Check him out:
http://forum.xda-developers.com/showthread.php?t=2718130
Good luck!
RockStar2005
Related
I was restoring a Nandroid on my Note 3 tonight- when I rebooted, I got an error message saying Process System isn't responding - do you want to stop it or wait - no matter which option I chose, the phone would reboot - I tried to restore other nandroids and got the same error,
I tried to Odin back to stock and on reboot - I got the same message.
Not sure what to do ?
It's kind of like the old "death loops' but I don't recall ever seeing that particular error message -
Any suggestions? RIght now I can't do anything with this phone - ???
same problem here..... i get no signal and bootloops
Wtf. Im getting the same thing here. Driving me crazy. Im out of solutions
this worked like a charm for me. Im back up. I even used the same exact backup which was looping after without efs of course.
http://forum.xda-developers.com/showthread.php?t=2471421
1. Reboot to recovery
2. Hit "Advanced" Select "Terminal Command"
3. Hit "Select" (lower right corner)..Do not select any specific folder, just hit select..
4. keyboard will open, type in the following commands, make sure you put the spaces and / where they need to be, it needs to look exactly as outlined..
mke2fs /dev/block/mmcblk0p12
Hit Go - The command will run.
Clear the box, type the following command
mkdir /efs
Hit Go - The command will run.
Clear the box, type the following command
mount -t ext4 /dev/block/mmcblk0p12 /efs
Hit Go - The command will run.
thanks dreisus but i tried your fix many times but no luck still bootloop
trezegol said:
thanks dreisus but i tried your fix many times but no luck still bootloop
Click to expand...
Click to collapse
Well if you get the fix let me know. Im always interested in different solutions. How did bootloops start. Mine started with sinmply trying to install a theme through twrp .
i just did a efs backup after that install recovery boot into recovery didnt flash anything i just restart to system and bootloop started ... ill let you know if i get it fix im willing to try anything even if it hardbrick my phone r doesnt work so if anyone whants me to try something let me know
me also !!!!.. WTF is happening?
I flash it stock firmware 3 times... still same
This problem happen to me yesterday... I just rebooted my phone and it started happening. I get the Process System isnt Responding error message along with an infinite bootloop. I have no signal and my baseband said unknown when I finally got in and then it went to bootlooping again. I don't know WTF is going on lol. I didn't do anything to my device. It was perfect until yesterday. Can else anyone chime in on what the problem may be?
Edit: I performed the "Fix" with wiping the efs but I have to perform it every couple of reboots because after I reboot 2-3 times, it starts happening again.
lm that guy said:
This problem happen to me yesterday... I just rebooted my phone and it started happening. I get the Process System isnt Responding error message along with an infinite bootloop. I have no signal and my baseband said unknown when I finally got in and then it went to bootlooping again. I don't know WTF is going on lol. I didn't do anything to my device. It was perfect until yesterday. Can else anyone chime in on what the problem may be?
Edit: I performed the "Fix" with wiping the efs but I have to perform it every couple of reboots because after I reboot 2-3 times, it starts happening again.
Click to expand...
Click to collapse
Happens to me as well on all roms except jedi elite. I don't know if it's the phone or something I'm doing but I've just accepted jedi for now my buddy can only flash wicked and it happens on all others for him
Jedi Elite Powered T-Mobile Note 3
I just had this happen after a reboot on me today. I rebooted the phone again and it was fine. Stock rooted. Only time it has ever done it.
str8killinya said:
Happens to me as well on all roms except jedi elite. I don't know if it's the phone or something I'm doing but I've just accepted jedi for now my buddy can only flash wicked and it happens on all others for him
Jedi Elite Powered T-Mobile Note 3
Click to expand...
Click to collapse
krelvinaz said:
I just had this happen after a reboot on me today. I rebooted the phone again and it was fine. Stock rooted. Only time it has ever done it.
Click to expand...
Click to collapse
This is so weird. Before, I could flash any ROMS I wanted to with no problems. It started when I was using the ROA ROM but like I said I flashed that ROM many times and was using it for 3 days solid.
But anyways, I sadly had to get rid of mine. No matter what ROM im using results in a instant reboot even on the stock firmware. I just hope I get a new device with knox 0x0 because im staying on stock for a bit.
lm that guy said:
This is so weird. Before, I could flash any ROMS I wanted to with no problems. It started when I was using the ROA ROM but like I said I flashed that ROM many times and was using it for 3 days solid.
But anyways, I sadly had to get rid of mine. No matter what ROM im using results in a instant reboot even on the stock firmware. I just hope I get a new device with knox 0x0 because im staying on stock for a bit.
Click to expand...
Click to collapse
I think I must have wiped my EFS or something got corrupted - I followed Steps posed by Steve Lazarus - in this thread and it worked fine - (I also later found a flashable fix that does the same thing on the N9005 Thread...so if it happens again, that is what I will use.
I do know that the NOTE 3 Seems much more prone to getting soft bricked than just about any other phone I have ever used..
mocsab said:
I think I must have wiped my EFS or something got corrupted - I followed Steps posed by Steve Lazarus - in this thread and it worked fine - (I also later found a flashable fix that does the same thing on the N9005 Thread...so if it happens again, that is what I will use.
I do know that the NOTE 3 Seems much more prone to getting soft bricked than just about any other phone I have ever used..
Click to expand...
Click to collapse
Yeah, im 100% sure it has something to do with the EFS. It somehow got corrupted. Because when I finally get into the system, I check my baseband and it said unknown.
But the thing is, I never touched my EFS at all. I just rebooted one day and it was happening. Also I'd like to mention, that whenever I restored my EFS with the latest TWRP, everything started working again!!! BUT... i would have to perform this every 2-3 reboots because the problem would continue to arrive. So I had 2 choices... Perform an EFS restore every time I boot my phone or just return it.
lm that guy said:
Yeah, im 100% sure it has something to do with the EFS. It somehow got corrupted. Because when I finally get into the system, I check my baseband and it said unknown.
But the thing is, I never touched my EFS at all. I just rebooted one day and it was happening. Also I'd like to mention, that whenever I restored my EFS with the latest TWRP, everything started working again!!! BUT... i would have to perform this every 2-3 reboots because the problem would continue to arrive. So I had 2 choices... Perform an EFS restore every time I boot my phone or just exchange it. I chose the latter.
Click to expand...
Click to collapse
I never touched my EFS either - but somehow when I made a back up on a rom I was using, when I rebooted afterwards I got those nasty reboots. then nothing would work - no other backups - I tried using ODIN To go to stock - nada - but following the instructions from Lazarus - I was able to get it going again.
mocsab said:
I never touched my EFS either - but somehow when I made a back up on a rom I was using, when I rebooted afterwards I got those nasty reboots. then nothing would work - no other backups - I tried using ODIN To go to stock - nada - but following the instructions from Lazarus - I was able to get it going again.
Click to expand...
Click to collapse
If you are referring to wiping the EFS using TWRP I tried that and it worked. But the problem would come back every couple of reboots. And I wasn't about to perform this every time I reboot lol. Now that I think about it, have you ever experienced that followup random reboot when you boot your phone? Maybe that was a warning sign that this was coming
lm that guy said:
If you are referring to wiping the EFS using TWRP I tried that and it worked. But the problem would come back every couple of reboots. And I wasn't about to perform this every time I reboot lol. Now that I think about it, have you ever experienced that followup random reboot when you boot your phone? Maybe that was a warning sign that this was coming
Click to expand...
Click to collapse
I have noticed that occasionally the phone will boot up - look like is almost ready and then reboot - usually only happens once and then the phone boots fine. I have always thought it was the finickyness of the NOTE 3 - and the newness of custom recovery's for the NOTE 3 - I honestly don't know why it does it - the most recent version of TWRP seems more stable - but who knows....?
+Jason Ren https://db.tt/QQfxFQlo this fixed boot my loops. flash in recovery. keep it on your sdcard for future use.
Sent from my SM-N900T using Tapatalk
Hello everyone thanks for checking out my post for assistance.
I was running the OpTimuS 2.2 yesterday when my phone jumped into a boot-loop. The phone will be on for about 20-40 seconds then reboot. During that time I have no service and when I update the profile I get a message that I don't have any service. I can get into recovery and Download mode. I tried to just wipe and install the rom again. That process resulted in the same boot loop. I have a back up but that was done before the "spark" update and I didn't want to restore that because I know there will be an issue with the radio. I downloaded the stock rooted rom but the phone will not stay on long enough to transfer the file and when I try and load via recovery it will not allow me to transfer the file. (never shows up on computer I might be doing that wrong) I then attempted to bring the phone back to stock following this process http://www.rwilco12.com/forum/showthread.php?tid=96 but when I get down to step 13 the program will not respond anymore. I am going a friends house to try on a different computer but I wanted to get this out there just in case that has the same result.
Thanks again for any info that you could provide.
usvi525 said:
Hello everyone thanks for checking out my post for assistance.
I was running the OpTimuS 2.2 yesterday when my phone jumped into a boot-loop. The phone will be on for about 20-40 seconds then reboot. During that time I have no service and when I update the profile I get a message that I don't have any service. I can get into recovery and Download mode. I tried to just wipe and install the rom again. That process resulted in the same boot loop. I have a back up but that was done before the "spark" update and I didn't want to restore that because I know there will be an issue with the radio. I downloaded the stock rooted rom but the phone will not stay on long enough to transfer the file and when I try and load via recovery it will not allow me to transfer the file. (never shows up on computer I might be doing that wrong) I then attempted to bring the phone back to stock following this process http://www.rwilco12.com/forum/showthread.php?tid=96 but when I get down to step 13 the program will not respond anymore. I am going a friends house to try on a different computer but I wanted to get this out there just in case that has the same result.
Thanks again for any info that you could provide.
Click to expand...
Click to collapse
Flashing back to stock won't work, I had the same thing happened.......it's the EFS Partition (http://forum.xda-developers.com/showthread.php?t=2451390) If you made a EFS Partition Backup, then flashing that will be your best hope.....I didn't make a backup so I went to sprint cuz I have insurance and they are ordering me a new phone
Shadow_God said:
Flashing back to stock won't work, I had the same thing happened.......it's the EFS Partition (http://forum.xda-developers.com/showthread.php?t=2451390) If you made a EFS Partition Backup, then flashing that will be your best hope.....I didn't make a backup so I went to sprint cuz I have insurance and they are ordering me a new phone
Click to expand...
Click to collapse
They replaced it even though your phone was rooted?
Try installing an updated modem for your variant from this thread. It's worth a try.
http://forum.xda-developers.com/showthread.php?t=2451426
If you get it working, definitely make an EFS backup right away.
usvi525 said:
They replaced it even though your phone was rooted?
Click to expand...
Click to collapse
I used the LGFlashTool to bring it back to stock unrooted.......but my phone had no sevice and rebooted every couple minutes, plus the touchscreen wasn't working either.....I told them I took the Spark update and thats when it happened, he said they had alot of issue with touchscreen stopped working and rebooting issue with the spark update......so they didn't look at it long...lol
I have tried back to stock numbers of times....installing modems....restoring my backups....nothing would get it to work, so I gave up and went to sprint...lol
On the rom you were using, have you tried enabling airplane mode to prevent reboots? You could try to get a stock-based flashable zip on the device if possible.
alone-together said:
Try installing an updated modem for your variant from this thread. It's worth a try.
http://forum.xda-developers.com/showthread.php?t=2451426
If you get it working, definitely make an EFS backup right away.
Click to expand...
Click to collapse
Thanks for the option. I was able to install the radio but the issue remains.
usvi525 said:
Thanks for the option. I was able to install the radio but the issue remains.
Click to expand...
Click to collapse
Have we ruled out the possibility to flash a stock ROM in TWRP? If by any chance you have a USB OTG cable, you could try to connect a flash drive with another ROM.
This is my last ditch effort. Small back story: I somehow wiped EVERYTHING on my G2. EFS partition, ESN, data, SIM info., everything with dialer codes. All of my network information reads "unknown". I tried many methods from here on the forums to get this data back and it turns out I have lost my EFS partition- DNA for the network? I sent it to LG to get it fixed, having done a hard reset and leaving no trace of root. They sent it back without even asking and did no repairs. The note said "board bent". WTF?? How does the user bend the main board, especially when I never opened it? They voided my warranty and ripped off my IMEI/MEID sticker from the back of the phone.
Anyways, I am here with a brick. No network still. Here is what I have done:
1) .tot method to ZVC. Several more times... once to ZV7 where I lost touch capability. Luckily saved my arse with a micro->usb cable and a mouse.
2) attempted to root with ioroot25. Failed because the phone WILL NOT find recovery mode. adb, voldown+pwr then again from power off, and apps are unable to force the phone into recovery mode. I assume it is possible that my recovery mode is deleted?
3) Would have tried all of these "rewrite your efs/imei/etc" things but I can't do any without root. Can't root without recovery, can I?
4) Spent the last two weeks scouring the internet for a fix and going back to my Epic 4G temporarily.
Please help me, has anyone seen this before? Can anyone help me fix it? I am to the point where I would pay to have it fixed. Any experts out there? XDA has yet to let me down... I just need to know if I can fix it or if it is a brick so I can go searching for an old Sprint GS3.
Thanks all,
baublitz
Ok, so I am not to sure exactley what I did. I accidental hit unroot in CWM. I have a recent titanium backup, but i suppose that will do me no good. I lost superuser permission to operate Titanium anyway. Also CMW as the app is useless to me now. I can boot into it using the volume down, home power option, but i can not get to anything there to restore it.
Do i need to re-root, or what direction should I be going in? All I am looking for is someone to point me in the proper direction, I feel horrible asking this here, as I normally know what I am doing.
Thanks for your help.
I am back to stock. Not rooted or anything, so there is one problem solved. I would like to OTA update, but it is saying i am up to date, and i am pretty sure 4.1.2 is not up to date. Oh well, im half way there.... i think...
sully42 said:
I am back to stock. Not rooted or anything, so there is one problem solved. I would like to OTA update, but it is saying i am up to date, and i am pretty sure 4.1.2 is not up to date. Oh well, im half way there.... i think...
Click to expand...
Click to collapse
You have options, OTA to 4.3 (just advance time/date 24 hours or whatever time it says to check again) You will have a locked bootloader and Knox *****ing at you if you install root.
Or you can flash this through ODIN or CWM, You get root and 4.3
http://forum.xda-developers.com/showthread.php?t=2589891
dicksteele said:
You have options, OTA to 4.3 (just advance time/date 24 hours or whatever time it says to check again) You will have a locked bootloader and Knox *****ing at you if you install root.
Or you can flash this through ODIN or CWM, You get root and 4.3
http://forum.xda-developers.com/showthread.php?t=2589891
Click to expand...
Click to collapse
Thanks! I got it to OTA to 4.3,I did not think about changing the clock, I ended up booting to CWM and factory resetting, then rebooted and it poped up with in 30 seconds that there was a software update.
I think I will flash that threw oden later. I was mostly freaking out because my phone was stuck between rooted, and not rooted. All sorts of apps where tweeking out on me. 4.3 is nice, but way to much junk installed by ATT.
cell carriers are the worst kind of people.
sully42 said:
Thanks! I got it to OTA to 4.3,I did not think about changing the clock, I ended up booting to CWM and factory resetting, then rebooted and it poped up with in 30 seconds that there was a software update.
I think I will flash that threw oden later. I was mostly freaking out because my phone was stuck between rooted, and not rooted. All sorts of apps where tweeking out on me. 4.3 is nice, but way to much junk installed by ATT.
cell carriers are the worst kind of people.
Click to expand...
Click to collapse
No worries. This just came out yesterday.
http://forum.xda-developers.com/showthread.php?t=2659569
A little of the crap removed. I'm running it, pretty smooth.
Moderators, please forgive me in not in the right place...
Came home from a glorious week of camping and decided to check out some 4.4.4 ROM's on my phone...
Already running older version of C-ROM, so backed up and flashed the KK 4.4.4 version. That's where it the wheels came off my bus..
Phone booted so damn slow, then there were hundred's of FC's, rendering the phone unuseable. Rebooted, cleared Dalvik and Cache but same difference. The phone died, the battery would NOT charge! No matter what! Try as I may...NO GO!!! For hours! Feared it was that issue wherein the S3 motherboard dies and the phone has to be replaced by Samsung. Kept trying...finally get the phone to boot into TWRP. Whew!!! Still the phone kept complaining that the battery was dead. WTF?!
Restored the back up I had made...accidentally grabbed another backup from december of last year (Cyanogenmod), so had to recover my C-ROM back instead...RESTORE FAILS! Tried a few times but still failed. Tried to re-flash the latest C-ROM, but STILL fails...everything I'm trying fails.
I read the output and see an error, "Unable to wipe /system" ...found a thread where a user, using TWRP, had the same error with their ROM they were trying to flash. Eventually, the fix was to delete the make_4fs (or whatever it's called) from /sbin directory. Did so and was able to flash my Cyanogen, but could not restore my C-ROM backup. That STILL fails, however, no error in the live output while it's restoring. Just ends up Failing at the end of the restore process. The live logs indicate that it's using the 2fs (or whatever it's called), which was successful in flashing my Cyanogen ROM...why will it not restore my C-ROM back? :crying:
Any help would be greatly appreciated.
kojam said:
Moderators, please forgive me in not in the right place...
Came home from a glorious week of camping and decided to check out some 4.4.4 ROM's on my phone...
Already running older version of C-ROM, so backed up and flashed the KK 4.4.4 version. That's where it the wheels came off my bus..
Phone booted so damn slow, then there were hundred's of FC's, rendering the phone unuseable. Rebooted, cleared Dalvik and Cache but same difference. The phone died, the battery would NOT charge! No matter what! Try as I may...NO GO!!! For hours! Feared it was that issue wherein the S3 motherboard dies and the phone has to be replaced by Samsung. Kept trying...finally get the phone to boot into TWRP. Whew!!! Still the phone kept complaining that the battery was dead. WTF?!
Restored the back up I had made...accidentally grabbed another backup from december of last year (Cyanogenmod), so had to recover my C-ROM back instead...RESTORE FAILS! Tried a few times but still failed. Tried to re-flash the latest C-ROM, but STILL fails...everything I'm trying fails.
I read the output and see an error, "Unable to wipe /system" ...found a thread where a user, using TWRP, had the same error with their ROM they were trying to flash. Eventually, the fix was to delete the make_4fs (or whatever it's called) from /sbin directory. Did so and was able to flash my Cyanogen, but could not restore my C-ROM backup. That STILL fails, however, no error in the live output while it's restoring. Just ends up Failing at the end of the restore process. The live logs indicate that it's using the 2fs (or whatever it's called), which was successful in flashing my Cyanogen ROM...why will it not restore my C-ROM back? :crying:
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Have you tried using ODIN to restore back to stock? If you can get the phone up and running, you may be able to restore from your old backups.
Bass_Man25 said:
Have you tried using ODIN to restore back to stock? If you can get the phone up and running, you may be able to restore from your old backups.
Click to expand...
Click to collapse
Thanks bud.
Oh, I got the phone up and running on the Cyanogen dated dec/2013.
ODIN? Never thought of it. Been such a long time. I do need to get stock on here so I can all the latest official radios etc, then put custom ROMs.
Been such a loooooong time since used ODIN though. Shouldn't be hard to get back on the horse.
Thanks for the suggestion!!!
any idea why this happened? anyone?
as an fyi, I tried to put the lastest SlimROM on but same difference. (i'm really pressed for time always. so I decided this is the quickest thing to try). seems the only thing that will flash is my Cyanogen from December. Strange...
Will have to give ODIN a try if I can ever get the time some day..
Odin shouldn't be a much longer process. Start flash, walk away. When you return 10 minutes to a few hours later, it'll be sitting there waiting for you, all nice and stock!
Anyway, one thing I dont recall seeing you tried is a factory reset. Chances are, that's what caused all your FC. Roms will always take a while on first boot. But all those FC were likely due to incompatible data. Then you may have encountered more data corruption as the system worked overtime trying to resolve all those conflicts.
Its purely a theory, but there's a good chance you will never be able to find exactly what caused all of your issues. Dont lose sleep over it is my best advice! A couple of tips though....
Never wipe/format system! Had you been able to successfully do so, and then nothing would still flash, there would no longer be an o/s to boot into! All roms will format your system partition as the first step in the flash, so there's just no need to do this manually. Most flash failures occur before the flash actually starts, meaning if there's a problem, most times you'll still be able to reboot normally.
Update your firmware. If its been a while since taking an ota or updating via Odin, you're probably on an older firmware build which is known to cause problems with many more recent roms. Most simply will not flash if not updated.
Also, by flashing your up to date firmware in Odin, you will likely fix any corruption which may have occurred on some of those partitions. Good chance you'll be able to flash whatever you want after an Odin firmware update and factory reset.
Hope that helps! Good luck!
DocHoliday77 said:
Odin shouldn't be a much longer process. Start flash, walk away. When you return 10 minutes to a few hours later, it'll be sitting there waiting for you, all nice and stock!
Anyway, one thing I dont recall seeing you tried is a factory reset. Chances are, that's what caused all your FC. Roms will always take a while on first boot. But all those FC were likely due to incompatible data. Then you may have encountered more data corruption as the system worked overtime trying to resolve all those conflicts.
Its purely a theory, but there's a good chance you will never be able to find exactly what caused all of your issues. Dont lose sleep over it is my best advice! A couple of tips though....
Never wipe/format system! Had you been able to successfully do so, and then nothing would still flash, there would no longer be an o/s to boot into! All roms will format your system partition as the first step in the flash, so there's just no need to do this manually. Most flash failures occur before the flash actually starts, meaning if there's a problem, most times you'll still be able to reboot normally.
Update your firmware. If its been a while since taking an ota or updating via Odin, you're probably on an older firmware build which is known to cause problems with many more recent roms. Most simply will not flash if not updated.
Also, by flashing your up to date firmware in Odin, you will likely fix any corruption which may have occurred on some of those partitions. Good chance you'll be able to flash whatever you want after an Odin firmware update and factory reset.
Hope that helps! Good luck!
Click to expand...
Click to collapse
What's up, Doc? Sorry for that...
I downloaded Odin this morning. I should have gotten the link from XDA. The site i got it from looked official, however, tons of endless pop-ups after I installed it. Freak!!!
Then found the xda links. Not sure which version to get because i didn't see which one handles the S3. The latest version (3.09) should, no?
As well, where do i get the stock ROM from? Forgive me for all these questions. Been extremely busy with work these past few months. No time to play around with my phone everything. I'm forgetting more than I know.
A full wipe was done. In TWRP, system was check (it's always checked) automatically when wiping to flash a new ROM.
Thanks again!
Everything you need is in my sig. Go to the firmware thread and the stock or root66 firmware listed there us what you flash in odin. Version 3.09 is fine btw.
DocHoliday77 said:
Everything you need is in my sig. Go to the firmware thread and the stock or root66 firmware listed there us what you flash in odin. Version 3.09 is fine btw.
Click to expand...
Click to collapse
Thanks!
S.O.S!!!
kojam said:
Thanks!
Click to expand...
Click to collapse
Downloaded the rooted firmware from your link and the ODIN (3.09)...
Flashed the firmware (making sure to get the correct one for WIND)...ODIN did it's thing...got a green pass...the phone rebooted...got the Samsung symbol, little swoosh animation, and the accompanying sound effect that goes with the swoosh-thing...THE PHONE NEVER BOOTED UP AN O/S!
Did it at about 11:30 last night, left it, got up this morn, and phone STILL in same status!
Found out that site where I downloaded the firmware had an issue last night. They posted this morn, apologizing to people about a D.O.D attack that may have caused dropped downloads. I downloaded the firmware again this morn, flashed with ODIN, got a pass....SAME THING!!! Phone
Had to quickly pack up my laptop to bring with me to the office. Will try the official, non-rooted firmware to see if I can get it to go.
Problems' that my team went from 12 to 2 people...my partner's off today...and I got a LOUD MOUTH across from me who WILL NOT leave me alone, no matter what I say or do. LOL.
Any suggestions?
In the words of George Costanza:
"I'm BACK, babyyyyyyy!!!!!"
The official firmware worked!
Phone's back online. Thanks for all your help. Will have to see about rooting later...as well, want to see how the battery operates on stock firmware. I've tried EVERYTHING under the sun to preserve batt life and NOTHING worked!!!
Tried EVERY KERNEL noted to be good on battery life, tried TONS of apps that were supposed to help, turned off as much as I could, etc....
batt still not good. I give up. Every diagnostic app says batt is very good. I dunno...
Earplugs! Lol! I definitely feel for you about your work status! Been there!
About the firmware though, if the download had been corrupted, it would've failed the initial check done by Odin. You are probably ok. Dont worry just yet!
If it is hanging up at the Samsung screen, you probably just need to factory reset. Almost always fixes this. (It happens due to incompatible data left from your previous rom)
This will wipe internal sdcard though, so if you haven't backed up yet, the next thing to fo is flash TWRP via Odin. You can then use its built in file manager to copy whst you need first. Or you can then flash an insecure kernel and use adb if you're familiar with that.
The Doc is in!
if the download had been corrupted, it would've failed the initial check done by Odin
Click to expand...
Click to collapse
That's EXACTLY my thought too. That was really perplexing...
I am up again...
Facotry Reset? How do I do that if stuck at the Samsung splash though?
Now that i know the official firmware works, maybe i'll, try again with the rooted firmware, try to factory reset when stuck, and continue to flash TWRP as you described above. Don't mind factory resetting. I've taken everything I need.
Oh!!!!
I noticed that all the apps I had before flashing the firmware are STILL on my phone. I would have thought that they would have been wiped out completely when lord ODIN was doing her thing.
....and battery life is STILL pretty bad...
Phone's been charging...became fully charged...unplugged it..it was down to 84% after only about 30/mins.
Will see how it goes after doing the factory wipe.
Again, how do i do a factory wipe if stuck at the Samsung swoosh after I re-flash the rooted firmware ?
Maybe your battery is dying. it happens. That would explain a big drop from the start.
To factory reset if you're stuck at boot up, turn the phone off, then boot up into recovery. Hold volume up, home and power. After it vibrates, release power only, continue holding the other two until you see recovery booting up.
If stock recovery is installed, choose factory reset.
In TWRP (probably similar in cwm) go to Wipe and choose factory reset there. In TWRP and CWM, factory resetting does not wipe your internal sdcard. Stock recovery will.
And as for Odin, it doesn't actually touch the user data partition, so all your apps and data are preserved. This is great when just upgrading from one build to the next, but is the reason a factory reset is required if coming from a non touchwiz rom.
---------- Post added at 03:59 PM ---------- Previous post was at 03:53 PM ----------
How old is your battery? The S3 is at the age where people who bought it when it was first released will start to notice the battery is beginning to degrade.
You can also get an app called Better Battery Stats here on xda (paid version in the play store). Its the goto utility for investigating problems with battery drain. Run it for a day after a full charge and then check its logs for persistent wakelocks. The app thread should explain its use better than I can, but if you are having trouble you can always post your bbs log here for one of us to look over. (This isnt my strongest area, but there are a few others around that may also be able to help. )
Just did the ota update. Have since rebooted phone twice. Update and phone don't like each other! Chrome keeps auto-closing. And phone is lagging/freezing continuously. Phone was rooted years ago, and never any issues, even upgrading to Kitkat. This one I'm not to sure about!!!!!
Oh, and booting takes about twice looking too!
Keeps getting better...can't download anything from the play store. Says it's downloading, but never goes anywhere.
andygold said:
Just did the ota update. Have since rebooted phone twice. Update and phone don't like each other! Chrome keeps auto-closing. And phone is lagging/freezing continuously. Phone was rooted years ago, and never any issues, even upgrading to Kitkat. This one I'm not to sure about!!!!!
Oh, and booting takes about twice looking too!
Keeps getting better...can't download anything from the play store. Says it's downloading, but never goes anywhere.
Click to expand...
Click to collapse
Were you rooted? The last OTA update tried to take away root and it was really hard getting it back. It's acted strangely ever since.
wildbean98 said:
Were you rooted? The last OTA update tried to take away root and it was really hard getting it back. It's acted strangely ever since.
Click to expand...
Click to collapse
I took the update against my better judgement and sure enough soft bricked and now phone wont go into DL mode...grrrr
Major issues here as well. My SD card is now blank and doesn't want to mount. Big slowdowns as well. Any way to remove this update ?
Sent from my SHIELD Tablet using Tapatalk
Was finally able to DL apps, but at a crawl. I cleared the cache including dalvik, and everything is back to normal. And I'm still rooted!
I used Cache Cleaner NG from the play store
Soft bricked
I have bricked my phone after accidentally accepting it. Got back the phone again with lg flash tool. Once restarted the phone, rooted it, used titanium backup apk to freeze the software updater.
I don't think that it is wise to do a software update while rooted, it usually denies the process anyways.
Actually guys, its most likely that malware piece that was making its way around. Didnt anyone else read about it a few days ago? Let me hunt it down and see if i can post a link here. Standby....
Update: hold the phone, i may have been mistaken. Standby...
Now im soo broke i cant even pay attention!
ThaHawk said:
I don't think that it is wise to do a software update while rooted, it usually denies the process anyways.
Click to expand...
Click to collapse
Hi, rooting a phone does not stop the update anyway since you can unroot very easily, if it is supersu apk. But if a person installed custom recovery, it can brick the phone since the update tries to use the stock recovery. I learnt it in the hard way.
sdivk said:
Hi, rooting a phone does not stop the update anyway since you can unroot very easily, if it is supersu apk. But if a person installed custom recovery, it can brick the phone since the update tries to use the stock recovery. I learnt it in the hard way.
Click to expand...
Click to collapse
I stand corrected, your absolutely right!
ThaHawk said:
I stand corrected, your absolutely right!
Click to expand...
Click to collapse
Thanks. If you have a rooted lg e980 without custom recovery, you can use quickboot apk to enter stock recovery, which has limited features.
The problem with unlocking bootloader and use custom recovery is, if there is an update, there is no way to relock the bootloader and flash stock recovery. If sombody can shed the light on this matter, i really appreciate it.
I am looking for a way to relock the bootloader and install stock recovery without using lg flash tool.
Not that i am expecting an update from AT&T anytime soon.
+1
its better its included on CM based ROMs also