Related
i've been using CWM recovery and CM nightlies. they've been just fine. today i restored a two day old backup, as i didn't care for the current nightly.
now the phone black screens after the samsung splash.
i've tried:
factory reset
wipe dalvick/cache
restoring other backups
flashing other nightlies
and the phone will boot for the first time, but if i select 'reboot' or 'power down' on the next boot it's only a samsung splash, then black screen (no cm splash, no response from buttons input), and will not boot again.
what's the problem ?
ohgood said:
i've been using CWM recovery and CM nightlies. they've been just fine. today i restored a two day old backup, as i didn't care for the current nightly.
now the phone black screens after the samsung splash.
i've tried:
factory reset
wipe dalvick/cache
restoring other backups
flashing other nightlies
and the phone will boot for the first time, but if i select 'reboot' or 'power down' on the next boot it's only a samsung splash, then black screen (no cm splash, no response from buttons input), and will not boot again.
what's the problem ?
Click to expand...
Click to collapse
Happens once in a while when you flash over a back up.
Try making a clean flash.
Sent from my Carbonized SAMSUNG-SGH-T769 using Tapatalk Pro
Somcom3X said:
Happens once in a while when you flash over a back up.
Try making a clean flash.
Sent from my Carbonized SAMSUNG-SGH-T769 using Tapatalk Pro
Click to expand...
Click to collapse
i've done that. right now, i've wiped everything, and then flashed a nightly, and it will not reboot !
it will only boot the -one- time directly after flashing a new rom. any reboot attempts after that means it freezes, or fails, with a black screen directly after the samsung splash.
what have i missed ?
ohgood said:
i've done that. right now, i've wiped everything, and then flashed a nightly, and it will not reboot !
it will only boot the -one- time directly after flashing a new rom. any reboot attempts after that means it freezes, or fails, with a black screen directly after the samsung splash.
what have i missed ?
Click to expand...
Click to collapse
Try installing Samsung firmware via Odin. Root it and try again. Wouldn't hurt to try.
Sent from my Carbonized SAMSUNG-SGH-T769 using Tapatalk Pro
Somcom3X said:
Try installing Samsung firmware via Odin. Root it and try again. Wouldn't hurt to try.
Sent from my Carbonized SAMSUNG-SGH-T769 using Tapatalk Pro
Click to expand...
Click to collapse
could you point me to a specific samsung firmware, or is there only one ?
ohgood said:
could you point me to a specific samsung firmware, or is there only one ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=24660137
Make sure repartition is always unchecked in Odin
Sent from my Carbonized SAMSUNG-SGH-T769 using Tapatalk Pro
ohgood said:
could you point me to a specific samsung firmware, or is there only one ?
Click to expand...
Click to collapse
Check out this post from the brick fix thread.
http://forum.xda-developers.com/showpost.php?p=44626072&postcount=117
The full fix thread
http://forum.xda-developers.com/showthread.php?t=1591601
Sniped lol
i've wiped everything. flashed back to stock via odin, rooted, just like always.
i've even wiped in between.
after the FIRST clean boot, there is no rebooting. all it does is continue to hang after the samsung splash. no cyanogenmod, no stock rom, no nothing, nothing will boot the SECOND TIME.
i really don't understand this.
i'm using CWM recovery 5.5.0.4, cm-nightly 10-05, and it just don't think it's going to work properly again. it's a real shame, cause i really like the size, weight, and speed of this phone. but if it won't boot, i can't use it.
if anyone has any tips, i'll try them. at this point i really don't mind destroying it, and it might make me feel better to do so.
i meant to add, it doesn't matter if i use a backup, flash a fresh new rom, or use stock. the first boot works fine, but all boots after that wether from powering down or selecting 'reboot' fail.
maybe this part will help -
if i wipe the phone completely, it will boot. let's call this boot 1.
i can setup the phone, or change nothing in settings, doesn't appear to matter, and choose 'power down' or 'reboot'. let's call this reboot 1.
the next time i power on the phone, black screen. no CM splash, nothing. i guess we'll call this hang 1 ?
ideas ?
ohgood said:
i've wiped everything. flashed back to stock via odin, rooted, just like always.
i've even wiped in between.
after the FIRST clean boot, there is no rebooting. all it does is continue to hang after the samsung splash. no cyanogenmod, no stock rom, no nothing, nothing will boot the SECOND TIME.
i really don't understand this.
i'm using CWM recovery 5.5.0.4, cm-nightly 10-05, and it just don't think it's going to work properly again. it's a real shame, cause i really like the size, weight, and speed of this phone. but if it won't boot, i can't use it.
if anyone has any tips, i'll try them. at this point i really don't mind destroying it, and it might make me feel better to do so.
.
i meant to add, it doesn't matter if i use a backup, flash a fresh new rom, or use stock. the first boot works fine, but all boots after that wether from powering down or selecting 'reboot' fail.
Click to expand...
Click to collapse
The October nightlies are cm10.2 right? Your using the old recovery, that's the issue. And there are newer nightlies.
New recoveries
http://forum.xda-developers.com/showthread.php?t=2475802
Cm thread
http://forum.xda-developers.com/showthread.php?t=2459198
Romman0 said:
The October nightlies are cm10.2 right? Your using the old recovery, that's the issue. And there are newer nightlies.
New recoveries
http://forum.xda-developers.com/showthread.php?t=2475802
Cm thread
http://forum.xda-developers.com/showthread.php?t=2459198
Click to expand...
Click to collapse
yes, they're fairly recent nightlies. i skipped back to the 10-5 nightly as i thought that might ahve been part of the problem. since you're pointing to my recovery being an older version, i'll update it. thanks for the clue stick !
Romman0 said:
The October nightlies are cm10.2 right? Your using the old recovery, that's the issue. And there are newer nightlies.
New recoveries
http://forum.xda-developers.com/showthread.php?t=2475802
Cm thread
http://forum.xda-developers.com/showthread.php?t=2459198
Click to expand...
Click to collapse
hey thank you for that. i've removed the old cwm recovery, flashed new, lots of other flashes, and it finally works again. now to dig up a non-corrupted backup and hopefully be back to working.
thanks button was used
well, after all of that i'm going to roll with cm-10.0, cwm 6.xomething, so i can have a working compass on oruxmaps.
i won't be updating until 10.x begins to support compass functions again.
see yall then !
ohgood said:
well, after all of that i'm going to roll with cm-10.0, cwm 6.xomething, so i can have a working compass on oruxmaps.
i won't be updating until 10.x begins to support compass functions again.
see yall then !
Click to expand...
Click to collapse
Make sure you use the latest cm10 nightly, as the old stable one is a lot less "stable" than the name suggests, and is lacking features
Romman0 said:
Make sure you use the latest cm10 nightly, as the old stable one is a lot less "stable" than the name suggests, and is lacking features
Click to expand...
Click to collapse
thanks for the tip !
i finally got all the corrupted files (or whatever was causing problems) rm'd from both the phone and sdcard.
as of yesterday i had CM-10.o + CWM 6.0.3.8 and gapps 2012-8 (i think) working nicely on the phone. backed up a nandroid of all of it two times, and restored them to make sure restores were working. yes, everything fine.
as of today, i have CM-10.2 (latest nightly) + CMW 6.0.3.8 and gapps (current) working nicely on the phone. backed CURRENT up nandroid on sdcard, and restored a few times to make sure. yes, working fine.
seems it was
A) corrupted files/filessystems
and/or
B) too old a clockworkmod recovery
C) unstable CM version( s )
but now all is fine. thanks to all that helped !
Ok, so I probably know the answer to this already :crying:
Brief story - stock rooted ROM with custom kernel. Made backup with TWRP. Flashed stock boot,img and system.img in fastboot, flashed downloaded update from 4.4 -> 4.4.2 in recovery. Wiped cache and dalvik - started but recovery locked up. Had to hold power to reboot phone. Booted fine but no network, no IMEI, no baseband.
And no I don't have and EFS backup
I take it the phone is now buggered.
Is there anything I can do to fix this??
Appreciate anything that might help this.
Cheesy Wotsit said:
Ok, so I probably know the answer to this already :crying:
Brief story - stock rooted ROM with custom kernel. Made backup with TWRP. Flashed stock boot,img and system.img in fastboot, flashed downloaded update from 4.4 -> 4.4.2 in recovery. Wiped cache and dalvik - started but recovery locked up. Had to hold power to reboot phone. Booted fine but no network, no IMEI, no baseband.
And no I don't have and EFS backup
I take it the phone is now buggered.
Is there anything I can do to fix this??
Appreciate anything that might help this.
Click to expand...
Click to collapse
The same thing happened to me. Flash the latest version of TWRP, wipe your cache again, and your phone will be back to normal.
not true for all you may end up having to RMA I had my efs backup it still didn't fix it sorry to be the bearer of bad news but they make it sound like bringing it back is 100% but in some cases that's not true
Sent from my Nexus 4 using xda app-developers app
ddloco said:
not true for all you may end up having to RMA I had my efs backup it still didn't fix it sorry to be the bearer of bad news but they make it sound like bringing it back is 100% but in some cases that's not true
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
In his case, if he just does what I said to do he'll be fine. He didn't lose his EFS, he rebooted in the middle of a cache wipe and his partitions got messed up. Updating TWRP and wiping the cache again will set everything straight. This is a fairly common issue with older versions of TWRP.
_MetalHead_ said:
In his case, if he just does what I said to do he'll be fine. He didn't lose his EFS, he rebooted in the middle of a cache wipe and his partitions got messed up. Updating TWRP and wiping the cache again will set everything straight. This is a fairly common issue with older versions of TWRP.
Click to expand...
Click to collapse
I'm just saying the same thing happens to me and nothing that's suggested fixed it that's why I say its not 100% me and another guy both had the same problem and the only way was to RMA I also had my efs but even after doing everything from going back to stock updateubg twrp and reflashing my esf backup my phone would not correct its self so I'm not saying that this method doesn't work for some people but for me and another used it was a no go
So why are you guys still using twrp if it is causing issues?
Just use cwm instead!
Sent from my Nexus 5 using Tapatalk
Elisha said:
So why are you guys still using twrp if it is causing issues?
Just use cwm instead!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
because the majority dont have any problems.
and people, take precautionary measures and back up your efs partition, its the first thing i did as soon as i had a custom recovery. it takes 2 seconds. and store it somewhere OTHER then your phones internal storage, like on a comp or dropbox
TheAtheistOtaku said:
because the majority dont have any problems.
and people, take precautionary measures and back up your efs partition, its the first thing i did as soon as i had a custom recovery. it takes 2 seconds. and store it somewhere OTHER then your phones internal storage, like on a comp or dropbox
Click to expand...
Click to collapse
This is not an EFS issues. Simple matter of twrp messing up partitions.
Sent from my Nexus 5 using Tapatalk
Elisha said:
This is not an EFS issues. Simple matter of twrp messing up partitions.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
i know, still doesnt hurt to be caution though
ddloco said:
I'm just saying the same thing happens to me and nothing that's suggested fixed it that's why I say its not 100% me and another guy both had the same problem and the only way was to RMA I also had my efs but even after doing everything from going back to stock updateubg twrp and reflashing my esf backup my phone would not correct its self so I'm not saying that this method doesn't work for some people but for me and another used it was a no go
Click to expand...
Click to collapse
Yeah but did it happen to you the way it happened to OP? So far every single person that I have come across who was in this boat due to a bad cache wipe in TWRP was able to fix it by updating TWRP and re-wiping the cache. It's a well known issue.
_MetalHead_ said:
Yeah but did it happen to you the way it happened to OP? So far every single person that I have come across who was in this boat due to a bad cache wipe in TWRP was able to fix it by updating TWRP and re-wiping the cache. It's a well known issue.
Click to expand...
Click to collapse
Thanks for the help guys. Got it up and running again more by accident than anything. Seems like MetalHead was correct, the partition was fine but just not readable. Unfortunately in order to get up and running again I flashed all the stock images in flasboot and did a full factory reset in the stock recovery which fixed the problem. Sounds like I could have done without the full wipe after all but at least it's all fixed now.
As for backing up the EFS, lesson learned. I had the 1st official TWRP on the phone which had no option for EFS backup like the current one. Guess what I'll be doing right now??
Anyway, happy man again and thanks to all that replied :good:
I must apologize for saying its not 100% but the truth is I had the exact same thing happen and no stock or fast boot cache fixed it I'm living proof that it works for the masses but under rare circumstances this just doesn't solve it oh man how I wish this would've fixed mine I been using a inspire 4g its killing me I feel like I jumped out of a beemer and landed in a pinto lol
Sent from my Nexus 4 using xda app-developers app
Glad that the OP got the issue resolved !
on a side note , can anyone tell me what is the safest version of TWRP there ? i.e without this cache wipse issue ( taking too long to wipe ? )
ddloco said:
I must apologize for saying its not 100% but the truth is I had the exact same thing happen and no stock or fast boot cache fixed it I'm living proof that it works for the masses but under rare circumstances this just doesn't solve it oh man how I wish this would've fixed mine I been using a inspire 4g its killing me I feel like I jumped out of a beemer and landed in a pinto lol
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Thats a bummer man. What kind of phone are you using now?
Lowresolution said:
Glad that the OP got the issue resolved !
on a side note , can anyone tell me what is the safest version of TWRP there ? i.e without this cache wipse issue ( taking too long to wipe ? )
Click to expand...
Click to collapse
I believe 2.6.3.4 is the latest version. That's the one I'm on, works just fine.
Sent from my Nexus 5 using XDA Premium 4 mobile app
_MetalHead_ said:
Thats a bummer man. What kind of phone are you using now?
I believe 2.6.3.4 is the latest version. That's the one I'm on, works just fine.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Got it , thanks mate Just upgraded my version of TWRP .
the nexus 4 is my phone I gave to my wife now that its hers I'm lucky to pick it up just to hop on xda but when its her Facebook time she hurrie up and kick me off lol the phone I'm using is an HTC inspire 4g it sucks
Sent from my Nexus 4 using xda app-developers app
Guys, I'm running Purity room with Franco kernel and PA GAPPS. I've had this problem recently, where my room is running perfectly. But when ever I do a factory reset through CWM 6.0.4.5 and reboot, the error "phone had stopped" pops up and all I can do is long press the power button to reboot into recovery and restore a backup.
Any ideas guys?
Sent from my Nexus 5 using XDA Premium 4 mobile app
I would suggest redownloading purity and Gapps and franco kernel (You just never know). Flash them individually and boot into the phone and see which one is causing you problems; after a factory reset with wiping cache/ dalvik. If this does not work try a different ROM (I always keep a stock rooted/deodexed on my phone), if it still persist I would do a full wipe start over from scratch.
mistahseller said:
I would suggest redownloading purity and Gapps and franco kernel (You just never know). Flash them individually and boot into the phone and see which one is causing you problems; after a factory reset with wiping cache/ dalvik. If this does not work try a different ROM (I always keep a stock rooted/deodexed on my phone), if it still persist I would do a full wipe start over from scratch.
Click to expand...
Click to collapse
Thanks for the reply, however, Ive already done the following:
1- Wipe Data/Factory reset > Reboot: "Phone has stopped" Error
2- Wipe Data/Factory reset > Install Purity (with/without GAPPS) > Reboot: "Phone has stopped" Error
3- Wipe Data/Factory reset > Install Puroty (with/without Franco kernel) > Reboot: "Phone has stopped" Error
4- Wipe Data/Factory reset > Installed other ROM> Reboot: "Phone has stopped" Error
5- Wipe Dialler/SIM toolkit > Wipe Data/Factory reset > Reboot: "Phone has stopped" Error
Cache/Dalvik Cache cleared every time.
The old backup still works, I even dirty flashed the new Purity version over it and works ok. The problem only arises after Wipe Data/Factory Reset.
Couldn't find any other solutions, any other suggestions?
Well I would say that if it works after your backup and then dirtyflashing a newer version of purity then leave it go, this is probably not the best option but if it works.... My other option in my previous post was to completely wipe the phone and start over as in back to stock and start over.
Something could've corrupted, who knows, maybe something went wrong with your installation of a bootloader. You said you are running CWM 6.x.x.x, try flashing the stock bootloader and then reflashing a different bootloader I suggest TWRP but there are other options. I used CWM on my nexus and it did it's purpose but when I flashed TWRP onto my nexus 5 it was just more clean and it had touch, go figure.
I'd try using Titanum Backup and clearing the data of the phone, dialer storage, etc after the reset. Had a similar situation the other day that doing that resolved. Hope that helps. Problems like this can be annoying.
Just thought of this: Could be your recovery. Might not be wiping things correctly. If what I suggested doesn't help, then try TWRP. I've found very few things that TWRP is not better at vs CWM (on officially supported phones).
OK try to install cyanogen mode and let me know what happened
Sent from my Opal 800 using xda app-developers app
mistahseller said:
Well I would say that if it works after your backup and then dirtyflashing a newer version of purity then leave it go, this is probably not the best option but if it works.... My other option in my previous post was to completely wipe the phone and start over as in back to stock and start over.
Something could've corrupted, who knows, maybe something went wrong with your installation of a bootloader. You said you are running CWM 6.x.x.x, try flashing the stock bootloader and then reflashing a different bootloader I suggest TWRP but there are other options. I used CWM on my nexus and it did it's purpose but when I flashed TWRP onto my nexus 5 it was just more clean and it had touch, go figure.
Click to expand...
Click to collapse
Will try resetting and well then install twrp ... let's see. Can't let it be coz I need to be able to test other roms and stuff.
Sent from my Nexus 5 using XDA Premium 4 mobile app
es0tericcha0s said:
I'd try using Titanum Backup and clearing the data of the phone, dialer storage, etc after the reset. Had a similar situation the other day that doing that resolved. Hope that helps. Problems like this can be annoying.
Just thought of this: Could be your recovery. Might not be wiping things correctly. If what I suggested doesn't help, then try TWRP. I've found very few things that TWRP is not better at vs CWM (on officially supported phones).
Click to expand...
Click to collapse
Yeah that would be an easier option to try before resetting... Will try twrp as well.
Sent from my Nexus 5 using XDA Premium 4 mobile app
You can install any ROM it does not have to be cyanogen mod.
why is that the goto for everyone?.....
---------- Post added at 12:18 PM ---------- Previous post was at 12:18 PM ----------
es0tericcha0s said:
I'd try using Titanum Backup and clearing the data of the phone, dialer storage, etc after the reset. Had a similar situation the other day that doing that resolved. Hope that helps. Problems like this can be annoying.
Just thought of this: Could be your recovery. Might not be wiping things correctly. If what I suggested doesn't help, then try TWRP. I've found very few things that TWRP is not better at vs CWM (on officially supported phones).
Click to expand...
Click to collapse
What does TWRP not do that CWM does?
mistahseller said:
You can install any ROM it does not have to be cyanogen mod.
why is that the goto for everyone?.....
---------- Post added at 12:18 PM ---------- Previous post was at 12:18 PM ----------
What does TWRP not do that CWM does?
Click to expand...
Click to collapse
CM is usually the go to to try something else because A) It's usually the most stable of aftermarket Roms due to the larger community and user support B) been around the longest / out for the most phones so is more well known C) it's different than AOSP so if you have issues with AOSP AND CM then you know something is really going on. That being said, CM is boring and plain to me. I appreciate that they are a good base to work off of but just by itself - yawn.
There have been a time or 2 that something would not flash through TWRP or CWM is recommended by the dev, though this is few and far between on this phone. I mod phones all the time (have done over 100 different ones) and sometimes things just work better on one than the other for various reasons.
es0tericcha0s said:
CM is usually the go to to try something else because A) It's usually the most stable of aftermarket Roms due to the larger community and user support B) been around the longest / out for the most phones so is more well known C) it's different than AOSP so if you have issues with AOSP AND CM then you know something is really going on. That being said, CM is boring and plain to me. I appreciate that they are a good base to work off of but just by itself - yawn.
There have been a time or 2 that something would not flash through TWRP or CWM is recommended by the dev, though this is few and far between on this phone. I mod phones all the time (have done over 100 different ones) and sometimes things just work better on one than the other for various reasons.
Click to expand...
Click to collapse
The problem im facing doesnt seem to be related to stability .... can try twrp though to make sure there isnt a problem with flashing or resetting through CWM.... Should I directly install TWRP over CWM or should I first reset my phone with stock and then root again before installing TWRP?
Ad.Shk2 said:
The problem im facing doesnt seem to be related to stability .... can try twrp though to make sure there isnt a problem with flashing or resetting through CWM.... Should I directly install TWRP over CWM or should I first reset my phone with stock and then root again before installing TWRP?
Click to expand...
Click to collapse
The stability idea was referring to the other poster's confusion over why someone suggested trying CM in the first place.
You can install TWRP over CWM with no issues. I typically just fastboot the recovery image, though if you aren't comfortable with that, then install the app GooManager and installing the OpenRecovery script in there will do the trick for you. No reason to go all the way back to stock at all for that. If I had a $1 for every time I had issues because of some file / recovery /formatting incompatibility, then I'd probably be able to take my wife out to a fancy dinner. Heh (I work on a lot of phones, it's my job. ) If you need help with either method, feel free to hit me up on Hangouts or make sure to post quote me because otherwise I'll forget to check back on the thread. Good luck.
es0tericcha0s said:
The stability idea was referring to the other poster's confusion over why someone suggested trying CM in the first place.
You can install TWRP over CWM with no issues. I typically just fastboot the recovery image, though if you aren't comfortable with that, then install the app GooManager and installing the OpenRecovery script in there will do the trick for you. No reason to go all the way back to stock at all for that. If I had a $1 for every time I had issues because of some file / recovery /formatting incompatibility, then I'd probably be able to take my wife out to a fancy dinner. Heh (I work on a lot of phones, it's my job. ) If you need help with either method, feel free to hit me up on Hangouts or make sure to post quote me because otherwise I'll forget to check back on the thread. Good luck.
Click to expand...
Click to collapse
Thanks a lot for the help bro. I just flashed TWRP (fastboot method) and wiped my phone, the problem "unfortunately, phone has stopped" persists..... Any ideas?
Ad.Shk2 said:
Thanks a lot for the help bro. I just flashed TWRP (fastboot method) and wiped my phone, the problem "unfortunately, phone has stopped" persists..... Any ideas?
Click to expand...
Click to collapse
Ah, that sucks man. Ok, well, next things to try include:
Wipe cache + dalvik
Go to Advanced / Fix Permissions
Reboot
Do you have a PIN on your SIM card? I was reading through the Purity thread and some were saying they had your problem and disabling that resolved.
es0tericcha0s said:
Ah, that sucks man. Ok, well, next things to try include:
Wipe cache + dalvik
Go to Advanced / Fix Permissions
Reboot
Do you have a PIN on your SIM card? I was reading through the Purity thread and some were saying they had your problem and disabling that resolved.
Click to expand...
Click to collapse
Nope no pin.... Will try the permissions thing and shall let you know.
Sent from my Nexus 5 using XDA Premium 4 mobile app
es0tericcha0s said:
Ah, that sucks man. Ok, well, next things to try include:
Wipe cache + dalvik
Go to Advanced / Fix Permissions
Reboot
Do you have a PIN on your SIM card? I was reading through the Purity thread and some were saying they had your problem and disabling that resolved.
Click to expand...
Click to collapse
No luck my friend, I'm back on cwm... antyother ideas?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Ad.Shk2 said:
No luck my friend, I'm back on cwm... antyother ideas?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It looks like at this point, it's time to try another rom or update the Purity one. That, or maybe try this: http://forum.xda-developers.com/showthread.php?t=2526844
Dw about it. Fixed it. Apparently there was a problem with the com.android.phone/telephony. UnInstalled them, and then factory reset my phone. Then installed the Rom again. All well thanks for you help bro.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Ad.Shk2 said:
Dw about it. Fixed it. Apparently there was a problem with the com.android.phone/telephony. UnInstalled them, and then factory reset my phone. Then installed the Rom again. All well thanks for you help bro.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You're welcome. Glad all is well again.
I had the same problem. But i did not make a backup..
How can I unninstall phone apk from recovery?
Hi,
I have a rooted VZW S3 and have been running Jelly Beans build 20 for a while now. Wanting to give a 4.3 rom a try I loaded up MOAR 7.1. Wiped everything, I possibly could without wiping my SD card. Flashed the rom, no problems. Booted it up, no problems. Then if I do a reboot, even after it has sat for a while without me doing anything to it, I get stuck on the Samsung SIII screen. I can do a battery pull and go to TWRP then wipe and get back to my Jelly Beans, but I'd like to give MOAR 7.1 a try. Any help would be appreciated.
Thanks.
powerkatwedel said:
Hi,
I have a rooted VZW S3 and have been running Jelly Beans build 20 for a while now. Wanting to give a 4.3 rom a try I loaded up MOAR 7.1. Wiped everything, I possibly could without wiping my SD card. Flashed the rom, no problems. Booted it up, no problems. Then if I do a reboot, even after it has sat for a while without me doing anything to it, I get stuck on the Samsung SIII screen. I can do a battery pull and go to TWRP then wipe and get back to my Jelly Beans, but I'd like to give MOAR 7.1 a try. Any help would be appreciated.
Thanks.
Click to expand...
Click to collapse
Make sure to use the latest TWRP and did you install ML1 modem like instructed so?
buhohitr said:
Make sure to use the latest TWRP and did you install ML1 modem like instructed so?
Click to expand...
Click to collapse
Yeah I have the latest build if twrp and I think I already has the correct Mode from a prior rom. I didn't even check to verify guess I got too excited. I'll check and report back. Thanks.
buhohitr said:
Make sure to use the latest TWRP and did you install ML1 modem like instructed so?
Click to expand...
Click to collapse
Well I didn't have the ML1 modem so I wiped everything clean, installed the modem, then the rom. Got the same result.
powerkatwedel said:
Well I didn't have the ML1 modem so I wiped everything clean, installed the modem, then the rom. Got the same result.
Click to expand...
Click to collapse
Any other ideas that may be causing this?
powerkatwedel said:
Any other ideas that may be causing this?
Click to expand...
Click to collapse
Here is another user solved the issue, take from the thread:
"What I did was upgrade my recovery with Goo, I removed the SD card, I wiped the internal memory (not sure if this is necessary but what the hell), factory wiped, installed 7.1, once the phone booted up I logged in to gmail, let it sync, didn't install anything else and rebooted just to make sure it reboots fine, and it worked. Then I installed all my apps with TB without data, just the apps. That is what I did. I had the same problem as you for two days and was frustrated but then I read that if you upgrade your recovery it would work fine. I am assuming you are trying to wipe cache and it is telling you that it can't be mounted, that is another problem I was having, so I am assuming that by wiping the internal memory it cleared that problem up. I hope this helps you out. Hopefully someone here can either back up what I am saying or call me crazy and help you out. Good luck."
What kernel are you installing? I had similar problem trying to install with LK. But that is just my phone not playing nice with it unfortunately (nothing wrong with LK) try DKP or KT.
Sent from my SCH-I535 using xda app-developers app
Lehocki said:
What kernel are you installing? I had similar problem trying to install with LK. But that is just my phone not playing nice with it unfortunately (nothing wrong with LK) try DKP or KT.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I have tried LK and the Stock and was still getting it. I was able to get it to install last night finally and work, but now my WiFi isn't working.
powerkatwedel said:
I have tried LK and the Stock and was still getting it. I was able to get it to install last night finally and work, but now my WiFi isn't working.
Click to expand...
Click to collapse
I was never able to get the WiFi to work, so I switched roms and was able to get everything working on Wicked. Thanks for all the help.
I have had my phone a month and its been working flawlessly. I've installed a few custom roms on it and I'm comfortable with all the technical side from years of doing this.
What happened is my phone had a random shutdown and on reboot there was a com.androidsystemui error. No problem I thought, so I wiped the phone and restored a backup of the same rom (latest Heisenberg which has been very stable for me) same issue. OK maybe its rom related. So I did a clean install of Slimkat which I have found v stable. Instant reboot on setup. After trying this a few times I took the nuclear option and wiped by entire phone including storage and went through all this again using otg. Same problems.
I can only think its recovery or sim card related? any ideas?
btw I have tried fixing permissions and repairing file system in recovery. Thanks in advance!
parmafran said:
I have had my phone a month and its been working flawlessly. I've installed a few custom roms on it and I'm comfortable with all the technical side from years of doing this.
What happened is my phone had a random shutdown and on reboot there was a com.androidsystemui error. No problem I thought, so I wiped the phone and restored a backup of the same rom (latest Heisenberg which has been very stable for me) same issue. OK maybe its rom related. So I did a clean install of Slimkat which I have found v stable. Instant reboot on setup. After trying this a few times I took the nuclear option and wiped by entire phone including storage and went through all this again using otg. Same problems.
I can only think its recovery or sim card related? any ideas?
Click to expand...
Click to collapse
What recovery are you using? I would consider trying out Philz touch recovery, not sure it will fix it, but its worth a shot anyways.
I have exactly the same bug, with my one (the one with these problems is for a friend) i once had this too, i thougt flashing every image file from stock image has fixed it ill try it in some hours.
BTW i use TWRP v 2.7.1.1 or 2.8.0.1 but this lsat one dont works with multirom for now
I managed to fix it! I used this guide: http://forum.xda-developers.com/one...fs-corrupt-t2879061/post55531560#post55531560
parmafran said:
I managed to fix it! I used this guide: http://forum.xda-developers.com/one...fs-corrupt-t2879061/post55531560#post55531560
Click to expand...
Click to collapse
Thank you very much
Read the full thread. Possibly a latest twrp issue.