I've tried several sense and aosp roms. I use twrp 2.1.0. It flashes and then when I reboot it just hangs on the boot screen.
Obviously I wipe everything. And after my first mishap I tried wiping everything twice with no avail. Is or has anyone had/have the same issue? And a possible fix?
sent from my HP Touchpad. Dual-booting Android 4.0.4 and WebOS 3.0.5
Twrp is known for issues with sense. Try cwm and see if you get further
Sent from my PG06100 using Tapatalk 2
hamagc said:
Twrp is known for issues with sense. Try cwm and see if you get further
Sent from my PG06100 using Tapatalk 2
Click to expand...
Click to collapse
I did try cwm. Because I thought my recovery partition might be messed up. But same thing. And I have downloaded the rooms several times to make sure it wasn't a issue with corrupted download.
sent from my HP Touchpad. Dual-booting Android 4.0.4 and WebOS 3.0.5
Can you get back to stock?
Sent from my PG06100 using Tapatalk 2
blmvxer said:
I did try cwm. Because I thought my recovery partition might be messed up. But same thing. And I have downloaded the rooms several times to make sure it wasn't a issue with corrupted download.
sent from my HP Touchpad. Dual-booting Android 4.0.4 and WebOS 3.0.5
Click to expand...
Click to collapse
Did you fully root your phone? Meaning you have "s-off" in the bootloader and not "s-on"?
Sent from my HTC Evo Shift using xda premium
blmvxer said:
I did try cwm. Because I thought my recovery partition might be messed up. But same thing. And I have downloaded the rooms several times to make sure it wasn't a issue with corrupted download.
sent from my HP Touchpad. Dual-booting Android 4.0.4 and WebOS 3.0.5
Click to expand...
Click to collapse
Did you check the MD5 checksum, or just re-download the Rom. Did you make sure and download over WiFi , or Hardline? As a rule of thumb never DL Roms, or Themes over the Network. Any stop in Data transfer will usually cause issues. Have you tried reformatting your SD Card. Are you certain your on the latest CWM Recovery? Also +1 to what hamagc said about TWRP.
prboy1969 said:
Did you check the MD5 checksum, or just re-download the Rom. Did you make sure and download over WiFi , or Hardline? As a rule of thumb never DL Roms, or Themes over the Network. Any stop in Data transfer will usually cause issues. Have you tried reformatting your SD Card. Are you certain your on the latest CWM Recovery? Also +1 to what hamagc said about TWRP.
Click to expand...
Click to collapse
Yeah first recovery I ever tried on my Nexus 7 was twrp. Almost soft bricked my tablet When I booted after flashing it a lot of things started force closing. Now I won't be flashing that again.
sparksco said:
Did you fully root your phone? Meaning you have "s-off" in the bootloader and not "s-on"?
Sent from my HTC Evo Shift using xda premium
Click to expand...
Click to collapse
He sounds like an s-on user. Maybe a tutorial on how to flash ROMs for the s-on users would be a good thing to have floating around.
Sent from my HTC MyTouch 4G Slide running MikXE
My backup is of the latest cm9 unofficial. I have re downloaded those roms several times and have checked the md5. I have tried different recoveries. So as of now I am at a loss. It literally doesn't make sense. The last rom I successfully installed which was last night was The jellybean preview 2. And then I recovered back to CM9 when I didn't like talking through the speaker phone. I tried installing a few sense rooms today to update my prl and here I am.
sent from my HP Touchpad. Dual-booting Android 4.0.4 and WebOS 3.0.5
At this point I would flash back to complete stock and start fresh. If at stock you still have issues, you know its a phone problem (and hopefully you have tep).
Sent from my PG06100 using Tapatalk 2
Also I can recover my ICS, I just think its a phone issue. And I'm to lazy to go back to stock and such I use my phone constantly and every time I switch roms I have to tell like 10 people to wait about 5 minutes before I text them or call them.
sent from my HP Touchpad. Dual-booting Android 4.0.4 and WebOS 3.0.5
blmvxer said:
Also I can recover my ICS, I just think its a phone issue. And I'm to lazy to go back to stock and such I use my phone constantly and every time I switch roms I have to tell like 10 people to wait about 5 minutes before I text them or call them.
sent from my HP Touchpad. Dual-booting Android 4.0.4 and WebOS 3.0.5
Click to expand...
Click to collapse
If your already Fully Rooted ( which I would hope you already are ) :silly: . Then doing an RUU back to 2.2 , and then Re-rooting can be accomplished in no time at all.
Related
I updated to EI22, stock w/OTA update. I then rooted and things were working great. Then about 1 week ago, I did a CWM backup and when I restarted the phone just kept automatically rebooting approx. every 3 -4 minutes. I could not stop it no matter what I did. Then I restored the backup and it worked fine. A few days later, I turned the power off to put in a my extra battery, and when I turned it on, the same thing happened. I had to restore twice fir it to stop this time. Then this morning, I did a reboot to see what would happen, and again it happened. Mind you it was working flawless before I restarted it. I have tried everything from removing programs, turning off the wifi, leaving the battery out for a half hour, but nothing. Sometimes after it reboots, I leave it alone for 15 minutes and then when I hit the power button, it just restarts.
Any ideas before I put back froyo??
Sounds like a bad flash. I would Odin all the way to Stock EC05 then root then flash a Gingerbread ROM. Your error is either in the kernel or recovery to happen immediately after boot. It could even be a flaky partition table.
Sent from my SPH-D700 using XDA App
OK. Funny, I flashed backed to a stock EC05 and did the OTA update so as to possible avoid any problems like this.
mszach said:
OK. Funny, I flashed backed to a stock EC05 and did the OTA update so as to possible avoid any problems like this.
Click to expand...
Click to collapse
I figured that but the problem may lie in the rooting which required you to flash a kernel or in your recovery module.
Sent from my SPH-D700 using XDA App
mszach said:
Any ideas before I put back froyo??
Click to expand...
Click to collapse
Your not alone on this issue. I am also considering going back to froyo
ADW was nice enough to bring up a crash report that I emailed myself. In the stack trace I see that android Package manager has died as a cause of the exception. I am not a java programmer so am at a loss here to what's happening.
See also this related post
So I flashed to the ACS ICS rom and so far no problems. What a great ROM!! Many thanks to Marcusant and ACS.
Sent from my SPH-D700 using XDA App
don't use the OTA.
just root ec05, flash CWM 5, flash modem update ec05 to EI22, flash a rom of your choosing. it's that simple. i don't see why people go the OTA route. it just causes problems with the recovery.
EDIT: also if you want Rom manager, check the kernel(or rom) for compatibility.
Why use ROM MANAGER at all? All the same tasks can be done from Clockwork Mod directly?
Sent from my SAMSUNG-SGH-I777 using xda premium
robmoney215 said:
Why use ROM MANAGER at all? All the same tasks can be done from Clockwork Mod directly?
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
I'm lazy sometimes and like to use a GUI...
Sent from my SPH-D700 using XDA App
robmoney215 said:
Why use ROM MANAGER at all? All the same tasks can be done from Clockwork Mod directly?
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
It was not supported for the Epic before but with the new CWM5 it is. It is much faster to boot into recovery from ROM Manager rather than powering down and 3 fingering into it. Plus ROM Manager supports renaming your backups when you are doing them. Also ROM Manager will continuously update your CWM if new versions come out. There is also OTA updates available if the developer supports it on their ROM.
I had encounter ICS, which was great, but isn't ready to be a daily rom, so I use koush's app to reboot into recovery.
then I got stuck at the boot animation, so I decided to open up the stock recovery, and wiped data/factory reset like an idiot. So now all i have is stuck at the M logo, or stock recovery.
Am I going to have to use an official update.zip to flash, then root my phone again?
You are going to have to sbf.
Sent from my DROID2 using xda premium
okay, so I sbf'd back to stock froyo (only GB sbf I can find around the net is a megaupload link, which is obviously not very helpful nowadays) and let it do an OTA update to GB.
I then root, just like i have before, using the motorola one click root program on my computer.
I get root, install koush's bootstrap, and reboot into recovery. I then try to install libertyv3 2.0, which seems to go well...
until i reboot. once i reboot my phone, I'm stuck back at the bootloader, and can't do anything except SBF all over again.
seriously, what's going on? maybe this liberty .zip is broken or something? (i had to find a mirror, because A team gummy's site seems to be down, and B the only other official mirror is megaupload)
I'm going to try another rom, probably encounter ICS because i already have it on my SD card.
this time, I actually read the instructions and tried to install Liberty with clockwork recovery instead of koush.
still. effing. happening.
I reboot after flashing the zip and I can't get past the bootloader screen.
Code:
Bootloader
D2.37
Err:A5,69,35,00,23
Battery OK
OK to Program
Connect USB
Data Cable
I'm seriously at wit's end here. I just got this phone but a couple days ago after I lost my original. it's an insurance replacement. I rooted with the moto one click root, and used koush to install encounter ICS. after not knowing about encounter's wonky way of activation the custom bootloader, I mistakenly wiped the phone with the stock bootloader. I SBf'd back to stock froyo, then OTA updated to gingerbread.
That is my entire history with this phone. what the hell could possibly be wrong with it?
Do you wipe data/cache/dalvic once before you flash and twice after? Liberty is dead use ICS.
Sent from my DROID2 ICS using xda premium
Albinoman said:
Do you wipe data/cache/dalvic once before you flash and twice after? Liberty is dead use ICS.
Sent from my DROID2 ICS using xda premium
Click to expand...
Click to collapse
I did certainly wipe before flashing, but have never not once heard of wiping twice after flashing. wouldn't that undo the flash? what's the point of that? And like I said, I would use encounter ICS, but it's nowhere near stable enough for daily use.
When you wipe after its just to make sure everything is stock. As long as you don't wipe /system the rom will still be there. Actually if you can live without a camera EncounterICS is an amazing daily driver. Also never use bootstrap unless you're on stock gb.
Sent from my DROID2 ICS using xda premium
I can live without a camera, but google music barely works, which is something I can't live without. I'm thinking about going back to Apex until encounter gets really good (had apex for months up until i lost my original phone)
Google music is working fine for me. Good idea apex is great.
Sent from my DROID2 using xda premium
I just flashed Paranoid Android on my N7 running 4.1.2, and it's stuck in the boot animation. I've been on this for about 10 minutes now. What should I do?
Go back to recovery, factory reset, wipe caches and reflash
Sent from my Nexus 7 using xda app-developers app
Try long pressing the power button to turn it off and try booting again. Sometimes it hangs on boot after flashing. Especially with certain kernels.
Wow, I'm in the same spot here after flashing PA. Can't get to recovery, PC isn't seeing it either. Been searching all day. Can anyone point us in the right direction? It will be much appreciated.
SpazticWonder said:
I just flashed Paranoid Android on my N7 running 4.1.2, and it's stuck in the boot animation. I've been on this for about 10 minutes now. What should I do?
Click to expand...
Click to collapse
chivo559 said:
Wow, I'm in the same spot here after flashing PA. Can't get to recovery, PC isn't seeing it either. Been searching all day. Can anyone point us in the right direction? It will be much appreciated.
Click to expand...
Click to collapse
Did you guys update the bootloader?
Sent from my SAMSUNG-SGH-I747 using xda premium
Apocalypse487 said:
Did you guys update the bootloader?
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Nope! I'm slapping myself as with one hand as I type with the other. Is there any method of salvation? *Please note: I rely on toolkits most of the time. Any help is appreciated, as always.
***Got it! I forgot to carry the one!
chivo559 said:
Nope! I'm slapping myself as with one hand as I type with the other. Is there any method of salvation? *Please note: I rely on toolkits most of the time. Any help is appreciated, as always.
***Got it! I forgot to carry the one!
Click to expand...
Click to collapse
So you fixed it? I updated the bootloader before updating PA to any newer versions. I haven't had bootloops. I followed the DROIDMODDERX video on YouTube when I was on 4.1.1. In the tool kit thread it tells you how to update.
Sent from my SAMSUNG-SGH-I747 using xda premium
Reboot error related to paths?
I flashed my N7 a few weeks back (using goomanager) with 4.2 JB which worked fine. I then put on gapps and got an endless loop of error messages about trying to configure them. At this point I rebooted to recovery and put back on rooted stock 4.1.1.
I thought I would try PA again this week and the ROM flashes OK, but when I reboot the N7 "hangs" at the boot screen and goes no further. The same thing happens if I try SmoothROM. I can go back to rooted stock OK though.
I notice the paths have been updated as per 4.2 but otherwise things appear the same as before.
Any idea why PA now won't boot?
Thanks
mik
On AOKP 4.2.1 the phone app crashes when I receive a call. I've reflashed a fresh downloaded GAPPS on here and it does the same thing. When coming to this ROM I wiped all data and factory reset everything. I've tried that again and it's still doing this. Starting to get on my nerves. Anyone have this problem?
MERKJONES said:
On AOKP 4.2.1 the phone app crashes when I receive a call. I've reflashed a fresh downloaded GAPPS on here and it does the same thing. When coming to this ROM I wiped all data and factory reset everything. I've tried that again and it's still doing this. Starting to get on my nerves. Anyone have this problem?
Click to expand...
Click to collapse
try a different rom. you can also try to delete the data for the phone app(then wipe dalvik after).
simms22 said:
try a different rom. you can also try to delete the data for the phone app(then wipe dalvik after).
Click to expand...
Click to collapse
I tried clearing the data from the phone app. I can reboot and clear dalvik again. I also flashed http://forum.xda-developers.com/showthread.php?t=2127498 and it's still acting up.
are you using any mods or themes?
simms22 said:
are you using any mods or themes?
Click to expand...
Click to collapse
Nope.
MERKJONES said:
Nope.
Click to expand...
Click to collapse
did you dirty flash your rom or did you make a clean install? also, after you installed aokp, did you restore system apps with titanium backup? and, have you tried a third party phone app?
simms22 said:
did you dirty flash your rom or did you make a clean install? also, after you installed aokp, did you restore system apps with titanium backup? and, have you tried a third party phone app?
Click to expand...
Click to collapse
I did a clean install and manually installed all of my apps again. I managed to fix it by dirty flashing the 4.2 version of AOKP. However; my phone still has that random reboot issue. The thing that's odd is, when it comes back online it loses it's settings. So I'll have to setup Google Wallet and Google Voice again. My keyboard goes back to the default AOSP one.
I think I might just RMA this phone and start over. I do love it, and the negatives don't outweigh the positives.
rma? dont.
wipe that thing clean with a factory reset. all your problems will be gone. then, if you like, start trying out roms again.
but bugging lg and nexus because you trashed your phone, thats not so cool. i can kinda understand samsung tries hard to lock their bootloaders sometimes.
links here: https://dl.google.com/dl/android/aosp/occam-jop40d-factory-ca7602f0.tgz
theres a batch file inside, make sure fastboot is around and click it (you must be in fastboot mode aswell). in a couple of seconds youre back to stock.
molesarecoming said:
rma? dont.
wipe that thing clean with a factory reset. all your problems will be gone. then, if you like, start trying out roms again.
but bugging lg and nexus because you trashed your phone, thats not so cool. i can kinda understand samsung tries hard to lock their bootloaders sometimes.
links here: https://dl.google.com/dl/android/aosp/occam-jop40d-factory-ca7602f0.tgz
theres a batch file inside, make sure fastboot is around and click it (you must be in fastboot mode aswell). in a couple of seconds youre back to stock.
Click to expand...
Click to collapse
Um... I had the problem on stock 4.2 as well, factory from Google themselves. It rebooted at random for no reason. I have wiped everything... multiple times. It's still doing it.
same thing happened to me this whole week. I have been flashing custom ROM custom this whole week. People have been texting saying my phone dont work. I called in to re-fresh with TMobile network and still the same thing. I also got a new micro sim card still the same. i have to revert back to stock with root in order for the phone calls to work. i have been searching for a fix.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
toanau said:
same thing happened to me this whole week. I have been flashing custom ROM custom this whole week. People have been texting saying my phone dont work. I called in to re-fresh with TMobile network and still the same thing. I also got a new micro sim card still the same. i have to revert back to stock with root in order for the phone calls to work. i have been searching for a fix.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
I thought it was the MicroSIM too - I got a brand new one with them, but nope - it's been all strange. Do you have 4.2 Stock rooted anywhere? I can only seem to find 4.2.1. I just wiped everything, restored factory etc etc and threw stock 4.2.1 on here, got the reboot issue. Phone has been working lately finally. I had to dirty flash AOKP 4.2.1 build-1 over build-2.
MERKJONES said:
I thought it was the MicroSIM too - I got a brand new one with them, but nope - it's been all strange. Do you have 4.2 Stock rooted anywhere? I can only seem to find 4.2.1. I just wiped everything, restored factory etc etc and threw stock 4.2.1 on here, got the reboot issue. Phone has been working lately finally. I had to dirty flash AOKP 4.2.1 build-1 over build-2.
Click to expand...
Click to collapse
i just used the stock 4.2.1 ROM and kernel. I am using the backup I made for my phone when i first rooted my phone. I don't a copy of the that. try using WUG rooting kit. u should be able to load it in that way. good luck. i missing flashing custom ROM, but I need my phone call to work. and by the way my last custom ROM was AOKP.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
You can always follow efrants guide to go fully back to stock.
Sent from my Nexus 4 using xda premium
Did you make any changes to the dpi in the build.prop? I remember messing with that on my nexus s on ics, and the phone app would crash.
Sent from my Galaxy Nexus using xda app-developers app
tokuzumi said:
Did you make any changes to the dpi in the build.prop? I remember messing with that on my nexus s on ics, and the phone app would crash.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
No. And even on stock 4.2 I'm now having the sound disappearing problem. Where it'll just stop for no reason.
i am trying download a new gapp and see if that fix the problem. stock is very boring
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
toanau said:
i am trying download a new gapp and see if that fix the problem. stock is very boring
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
I tried to get a new gapps in case the download was bad. I'm just going to RMA it. I'm on 4.2.0 stock, unrooted with default everything and it's still acting up. Phone.apk works now; which is lovely, but it reboots at random and Music stops working after 3 minutes.
MERKJONES said:
I tried to get a new gapps in case the download was bad. I'm just going to RMA it. I'm on 4.2.0 stock, unrooted with default everything and it's still acting up. Phone.apk works now; which is lovely, but it reboots at random and Music stops working after 3 minutes.
Click to expand...
Click to collapse
Everything is good now. Just flash new AOPK mr1 build 3 with newly doiwnload gapp. So far so good. Make sure you download the gapp from 12/12/2012
Sent from my Nexus 7 using xda app-developers app
No matter what I do... no matter what ROM I flash to, and I have tried 4 different ROMs, I keep getting the UI Stops Working error and then my phone is virtually non-functional. The notifications, navigation, and launcher bars go away and I cannot do anything. The only thing that I can do is boot into recovery and then flash a new ROM, BUT I have been doing this a couple times a day.
I even formatted my entire phone, internal storage and all, started completely over AND YET I still get the issue. What can I do???
System UI errors
alwaysbelieve1 said:
No matter what I do... no matter what ROM I flash to, and I have tried 4 different ROMs, I keep getting the UI Stops Working error and then my phone is virtually non-functional. The notifications, navigation, and launcher bars go away and I cannot do anything. The only thing that I can do is boot into recovery and then flash a new ROM, BUT I have been doing this a couple times a day.
I even formatted my entire phone, internal storage and all, started completely over AND YET I still get the issue. What can I do???
Click to expand...
Click to collapse
Did you freeze any of your system apps?
mcapozzi said:
Did you freeze any of your system apps?
Click to expand...
Click to collapse
The only ones that I can think of are the live wallpaper ones, Email Exchange since I don't need it, and face unlock. I also froze the NFC. I wouldn't think that would cause it. I was reading on the internet that the Facebook app can cause it so I deleted the app and we will see.
---
Sent using my Droid Razor M- THE BEST SMARTPHONE ON THE PLANET!
Heard about Kettlebells... learn more: http://synergykettlebell.com
Launcher
alwaysbelieve1 said:
The only ones that I can think of are the live wallpaper ones, Email Exchange since I don't need it, and face unlock. I also froze the NFC. I wouldn't think that would cause it. I was reading on the internet that the Facebook app can cause it so I deleted the app and we will see.
---
Sent using my Droid Razor M- THE BEST SMARTPHONE ON THE PLANET!
Heard about Kettlebells... learn more: http://synergykettlebell.com
Click to expand...
Click to collapse
What launcher are you using?
-Mike
mcapozzi said:
What launcher are you using?
-Mike
Click to expand...
Click to collapse
Nova Prime
alwaysbelieve1 said:
Nova Prime
Click to expand...
Click to collapse
You didn't by chance accidentally freeze the stock launcher?
-Mike
mcapozzi said:
You didn't by chance accidentally freeze the stock launcher?
-Mike
Click to expand...
Click to collapse
No
Here is a thread regarding the issue, but none of the "fixes" worked for me: http://forums.androidcentral.com/sa...0371-unfortunately-system-ui-has-stopped.html
I deleted Facebook so we shall see if that does the trick.
When this happened to me I used Matt's utility option 1... rooted it updated it n made a TiB of everything... now when I tinker n it gets wonky I restore the systemui.apk n reboot... I know you said that you started over does that mean you used rsd and flashed stock... or did you go through a recovery to do the wiping formatting n what not?
Sent from my XT907 using xda app-developers app
Had this happen the other day and this is what I did. I rebooted the phone WHILE HOLDING THE VOLUME DOWN KEY. it boots into safe mode. While in there make a TiBu of your apps. Then boot into recovery and factory data/reset like 3 times, flash back to a ROM and restore your apps. This way you don't lose your stuff.
Sent from my XT907 using Tapatalk 4
ezknives said:
When this happened to me I used Matt's utility option 1... rooted it updated it n made a TiB of everything... now when I tinker n it gets wonky I restore the systemui.apk n reboot... I know you said that you started over does that mean you used rsd and flashed stock... or did you go through a recovery to do the wiping formatting n what not?
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
When I meant started over I was yes referring to the booting to recovery and then wiping/formatting everything, then reflashing a ROM. That works, but I just am nervous now because the issue persists no matter the ROM. Sometimes it takes a day or two or sometimes it happens even quicker than that. I think it might be Facebook so I am not installing that app again. Why FB works on my Nexus 7 tablet and my wife's phone just fine is beyond me.
I didn't know I can make a backup of systemui.apk and restore it to make it work. I wish we could find the main issue to begin with so we can resolve this once-and-for-all.
evastonian said:
Had this happen the other day and this is what I did. I rebooted the phone WHILE HOLDING THE VOLUME DOWN KEY. it boots into safe mode. While in there make a TiBu of your apps. Then boot into recovery and factory data/reset like 3 times, flash back to a ROM and restore your apps. This way you don't lose your stuff.
Sent from my XT907 using Tapatalk 4
Click to expand...
Click to collapse
Yes that is exactly what I do every time. Today I started completely fresh and installed everything manually so I can better narrow down any issues.
alwaysbelieve1 said:
When I meant started over I was yes referring to the booting to recovery and then wiping/formatting everything, then reflashing a ROM. That works, but I just am nervous now because the issue persists no matter the ROM. Sometimes it takes a day or two or sometimes it happens even quicker than that. I think it might be Facebook so I am not installing that app again. Why FB works on my Nexus 7 tablet and my wife's phone just fine is beyond me.
I didn't know I can make a backup of systemui.apk and restore it to make it work. I wish we could find the main issue to begin with so we can resolve this once-and-for-all.
Click to expand...
Click to collapse
Yea I backup everything on my external hard drive (that after I back anything up I bubble wrap and put in my fire safe< a bit paranoid) every week, so that if anything happens I can just wipe it clean and start fresh (I have never used rsd lite but I'm guessing its somewhat like option one of Matt's utility) that restores your phone to a moto flashed like state... ready to be sold as a certified like new device (as Verizon would call it)...
Sent from my XT907 using xda app-developers app
Are you mounting system in TWRP, before you wipe data? For some reason, I stopped doing this when I updated to the newer TWRP. There was a thread on here where someone said they mounted prior to wiping and it solved their 4.3 issues. I tried it and it worked for me. I would suggest you try the same.
RikRong said:
Are you mounting system in TWRP, before you wipe data? For some reason, I stopped doing this when I updated to the newer TWRP. There was a thread on here where someone said they mounted prior to wiping and it solved their 4.3 issues. I tried it and it worked for me. I would suggest you try the same.
Click to expand...
Click to collapse
Don't even know how to do this or what this means exactly...