Related
I tried a search but didn't find much of any relevance to my Arc's problem.
My Arc was getting quite laggy so I decided to wipe and put a custom ROM on. I rooted, then unlocked the bootloader and managed to put on CWM using DoomLord's kernel. Everything fine up until here.
Then, mistakenly, I tried to put stable CM7 on without updating the stock ROM. I was still on 3.0 (2.3.3) something. Well, after that it got stuck in a boot loop with the SE and CM7 logos just coming up and restarting.
I then tried the Flashtool with a stock uptodate 4.0 something firmware. It flashed successfully, but it still was stuck in the loop, albeit now without the CM7 logo. I then tried the FTA unbricking tool for repairing the trim area but it still stayed in the boot loop.
What else can I do? Maybe there is a driver problem and that is why even after using Flashtool it still doesn't boot?
I would be very grateful if someone could help me on this.
You have to flash FXP's kernel and not DooMKernel.
But I also tried to flash a stock rom and that didn't work also.
EDIT: I flashed stock ROM again, still didn't boot. Installed DoomLord kernel and then arconium and it still doesn't boot.
EDIT 2: In CWM Recovery if I try to wipe data, it says this:
"E:format_volume: no MTD partition "userdata"
Has anyone got a fix for this?
It would be much appreciated.
can you charge your phone now?
Yep, I can charge the phone.
it means your kernel is still working....
then have it fully charged, then try to flashing again.
some tips:
1. always have latest flashtools
2. always have your phone fully charged b4 flashing.
3. proceed flashing carefully. if u miss one thing, then trouble come.
4. have cache and dalvik cache cleaned after flashing a kernel or Rom.
good luck mate...
gogo415 said:
it means your kernel is still working....
then have it fully charged, then try to flashing again.
some tips:
1. always have latest flashtools
2. always have your phone fully charged b4 flashing.
3. proceed flashing carefully. if u miss one thing, then trouble come.
4. have cache and dalvik cache cleaned after flashing a kernel or Rom.
good luck mate...
Click to expand...
Click to collapse
No luck with previous firmwares so I'll try to flash the latest .62 stock ROM and then see.
I'll let you know how I get on. Thanks!
Well lads, I managed to get it working by flashing the LT18i firmware (4.0.2.A.0.42_CE). Now I just need to go back to the drawing board and try to get CM7 on there.
Thanks for all the help! I'll update this thread with any experiences.
I've managed to do it. Installed latest .62 firmware, flashed CM7 kernel, flashed 7.2 ROM and then GAPPS.
I don't know why it took me two days to bring the phone back from the dead.
ZAnwar said:
I've managed to do it. Installed latest .62 firmware, flashed CM7 kernel, flashed 7.2 ROM and then GAPPS.
I don't know why it took me two days to bring the phone back from the dead.
Click to expand...
Click to collapse
hi, i came up with the same question:
E:format_volume: no MTD partition "userdata"
and my device is moto xt502
could you be so kind to give some details how you fix it
thank you very much
I am having the same problem too..please help! i flashed cm7 kernel n followed the instructions very carefully
ilamaan said:
I am having the same problem too..please help! i flashed cm7 kernel n followed the instructions very carefully
Click to expand...
Click to collapse
I followed the instructions too, though they are not so much noob-friendly (and neither are the people on the forums, it seems...). FXP is not responding (actually, they rarely respond to anything, they usually just post when new release is out), other people either don't know how to fix it, because they haven't experienced such issues, or they are just hostile because you're "a an annoying noob". Anyway... first time after trying to flash 64 baseband on 107 or 106 release, I got stuck on logo, then flashed back to .42 and it worked. Now, while updating to 108, I tried to flash the 64 libraries and patch, but it didn't work. Got back to .42, but this time nothing happened. Still stuck on logo. And when I try to restore data, it says:
E:format_volume: no MTD partition "userdata"
Error while formatting /data!
I think I'll go back to stock... love CM, but hate the poor/no help of the developers...
try these
flash new firmware using flashtool.
after flash.turn on your device.
enable uknown source n usb debug
then turn off your fon
flash baseband 64
then turn on your fon
put fxp108 updated-kang,gaps,baseband 64 libs on your memory card,
then turn off your fon
flash fxp kernel fastboot flash boot boot.img
after flash turn on your fon..go to recovery
formated factory reset,wipe cache,clear dalvik cache,wipe betry stats..
flash update cm7.update.zip,gaps.zip,baseband64libs.zip
reboot your fon..wait 2 or 3 mint..done
My thanks goes to you. I was hoping to avoid full wipe, but I don't care anymore, since I brought my phone back to life. I skipped these steps, though:
beranchoi said:
flash baseband 64
flash baseband64libs.zip
Click to expand...
Click to collapse
...because I went to check which baseband my phone was after flashing Global .62, and it said I was on -64, so it was no more necessary. For all of you having trouble with booting, follow the instructions given.
And now back to restoring all those apps
hey guys, can you post the link to that stock firmware, baseband and libs? maybe I've downloaded something wrong :/
btw. is there still that bug with a dark screen after locking phone?
lemon66 said:
hey guys, can you post the link to that stock firmware, baseband and libs? maybe I've downloaded something wrong :/
btw. is there still that bug with a dark screen after locking phone?
Click to expand...
Click to collapse
This is the link to the stock 4.0.2.A.0.42.. flash it using flashtool.. http://www.multiupload.com/W3B7BOKUXQ
Everything you need for flashing FXP is on his signature, including bb .64 (to be flashed with flashtool - doesn't erase a thing).. then download FXP (latest is 108) and inside the zip file you'll see boot.img, which contains the special kernel (to be flashed using fastboot, not flashtool).
Also there's no dark screen bug in the latest releases, certainly not in FXP 107 and 108, which I'm using now.
Please help!
beranchoi said:
try these
flash new firmware using flashtool.
after flash.turn on your device.
enable uknown source n usb debug
then turn off your fon
flash baseband 64
then turn on your fon
put fxp108 updated-kang,gaps,baseband 64 libs on your memory card,
then turn off your fon
flash fxp kernel fastboot flash boot boot.img
after flash turn on your fon..go to recovery
formated factory reset,wipe cache,clear dalvik cache,wipe betry stats..
flash update cm7.update.zip,gaps.zip,baseband64libs.zip
reboot your fon..wait 2 or 3 mint..done
Click to expand...
Click to collapse
Hey, this is my first post on here. I am new to android and just got an arc a few days ago. Even before i got it i was trying to figure out how to mod it. I am reasonably good at computers but a lot of the stuff i read on these forums is beyond me.
I have done my best to root and install CM7 on my arc but i have failed yet again.
I finally got it rooted and was all happy until when i tried to install CM7, all i can get to is the boot screen, but although the little android on the skateboard is very cool, i wish i could get it going!
So because I dont really understand the list of instructions you posted in this quote, i was hoping you could kind of translate into noob-speak. I still dont feel like i completely understand 'flashing'. In your instructions you say to "flash baseband 64" and that is the main point where I am stuck i think. Do you use a certain program (flashtool?) for this? or do it through a terminal window on the PC.
Also links to all the files mentioned would be awesome, its hard to find proper links with multiupload down and that kind of thing. Also with the rate this kind of tech evolves, things get outdated to quickly.
Please help! At the moment i have (i think) successfully returned my arc to the stock firmware using flashtool. Although i did this twice because i re-tried flashing CM7 and failed again. And the second time i couldnt seem to select LTI5i as the device to flash too, but LTI8i is what i used and it appears to have worked. So any help with that little conundrum would also be appreciated!
Cheers for any help given, I am so desperate to get this mod going as i have spent a solid 10+ hours trying already.
your bootloader unlock?right?
which kernel u use right now?
@tehknowitallnoob, I can lead you through the whole flashing process, if you want to, but only on Friday after around 9 pm GMT +1, since I don't have the time to do it earlier.
Sent from my LT15i (Xperia arc) on CM7
Try this:
Reflash back to stock ROM with a flashtool.
Then again flash the cm7 or try cm9
-cheers
So after seeing a Jelly Bean rom on here, I decided to download it and flash it. I did a nandroid backup first and then flashed the rom. Wouldn't boot. Basically it would vibrate with the Google screen then reboot over and over again. Tried to do a nandroid RESTORE and it gave me an error about restoring /data. Tried other backups and they gave me the same error. Tried to flash a completely different ROM and bootlooped on the Google screen. I saw that people were having errors with the TOUCH CWM so I reflashed the nontouch Recovery Image and I am getting the same results. I think I ****ed my phone. I have no other ideas so I am turning to the communty for help with this. I'm out of ideas. PLEASE HELP! Thanks!
Might be a stupid question but did you do the wipe/factory reset, wipe cache, wipe dalvik prior to the flash? Just asking...
drew_grant said:
So after seeing a Jelly Bean rom on here, I decided to download it and flash it. I did a nandroid backup first and then flashed the rom. Wouldn't boot. Basically it would vibrate with the Google screen then reboot over and over again. Tried to do a nandroid RESTORE and it gave me an error about restoring /data. Tried other backups and they gave me the same error. Tried to flash a completely different ROM and bootlooped on the Google screen. I saw that people were having errors with the TOUCH CWM so I reflashed the nontouch Recovery Image and I am getting the same results. I think I ****ed my phone. I have no other ideas so I am turning to the communty for help with this. I'm out of ideas. PLEASE HELP! Thanks!
Click to expand...
Click to collapse
I'm guessing you flashed the Vicious Version? Same thing happened to me today except it booted for like an hour then shut itself down and never booted all the back up. I had to flash a factory image through GNex Toolkit. I tried all kinds of things; restore a nandroid of cm9, Aokp, Stock, reflashing, nothing. So I hate to say it but looks like your going to be spending some time with fastboot tonight...
I really hope someone can prove me wrong though, cuz factory img wipes everything including SD.
Mikef3j said:
Might be a stupid question but did you do the wipe/factory reset, wipe cache, wipe dalvik prior to the flash? Just asking...
Click to expand...
Click to collapse
First thing I did.
xIC-MACIx said:
I'm guessing you flashed the Vicious Version? Same thing happened to me today except it booted for like an hour then shut itself down and never booted all the back up. I had to flash a factory image through GNex Toolkit. I tried all kinds of things; restore a nandroid of cm9, Aokp, Stock, reflashing, nothing. So I hate to say it but looks like your going to be spending some time with fastboot tonight...
I really hope someone can prove me wrong though, cuz factory img wipes everything including SD.
Click to expand...
Click to collapse
I'm all out of ideas. I've been spending 2 hours on this. This looks like my only option. Even worse for me, I can't access the GNEX Toolkit because I have a Mac. Do you have the file or the link to the file you flashed?
drew_grant said:
I'm all out of ideas. I've been spending 2 hours on this. This looks like my only option. Even worse for me, I can't access the GNEX Toolkit because I have a Mac. Do you have the file or the link to the file you flashed?
Click to expand...
Click to collapse
Use fastboot.
Sent from my Xoom using xda premium
Has anyone determined why this is happening with the new JB roms? I got stuck in this situation last night and would love to try again if I could just figure out where I went wrong the first go around.
This is srsly the last time I'm posting this.
Code:
adb pull /data/media/ /SDBACKUP/
To get your SD contents back.
Then fastboot flash back to stock.
JB changes the directory that your data resides in...which seems to be why many are having problems.
I, however, have swapped back to an AOKP nandroid just fine.
After trying to flash a new rom after being on AOKP M1 for a little while (http://forum.xda-developers.com/showthread.php?t=1875923) the phone got stuck at the Black and white Samsung Galaxy SIII screen and didn't boot upon hitting reboot system now on cwm. Tried again, tried reflashing and the whole 9 yards wouldn't boot at all. So I turned to odin and went to the prerooted latest JB build (http://forum.xda-developers.com/showthread.php?t=1949687) and then reflashed touch cwm and tried to reflash the rom. Same problem. So, I odin'd back to the non rooted UVDLJA. Rerooted and reflashed cwm and blahblahblah. I said hmm maybe it's the rom, I then tried to flash this rom (http://forum.xda-developers.com/showthread.php?t=1993934) and when I tried to reboot system now after the process; again the phone got stuck at the black and white Samsung Galaxy SIII screen and did not boot. The phone works fine when I odin it to stock builds but refuses to boot custom roms. Can someone help me here? I haven't been able to find a solution for days. :crying:
PS I'm a noob, don't kill me lol
edit: forgot to include I have the Tmobile variant
Did you wipe data and cache when you flashed the new rom?
nyyankees1237 said:
After trying to flash a new rom after being on AOKP M1 for a little while (http://forum.xda-developers.com/showthread.php?t=1875923) the phone got stuck at the Black and white Samsung Galaxy SIII screen and didn't boot upon hitting reboot system now on cwm. Tried again, tried reflashing and the whole 9 yards wouldn't boot at all. So I turned to odin and went to the prerooted latest JB build (http://forum.xda-developers.com/showthread.php?t=1949687) and then reflashed touch cwm and tried to reflash the rom. Same problem. So, I odin'd back to the non rooted UVDLJA. Rerooted and reflashed cwm and blahblahblah. I said hmm maybe it's the rom, I then tried to flash this rom (http://forum.xda-developers.com/showthread.php?t=1993934) and when I tried to reboot system now after the process; again the phone got stuck at the black and white Samsung Galaxy SIII screen and did not boot. The phone works fine when I odin it to stock builds but refuses to boot custom roms. Can someone help me here? I haven't been able to find a solution for days. :crying:
PS I'm a noob, don't kill me lol
edit: forgot to include I have the Tmobile variant
Click to expand...
Click to collapse
a few questions:
and i can verify the issue is something on your end, because the ROM you tried was mine, and nobody has had that issue (not booting it)
do this...
1. make sure you have the latest version of clockwordmod, don't use twrp
2. re-download my ROM (just for sake of not adding any other variables to your issue, because mine should boot)
3. put ROM on external SD card
before continuing... take a quick look at my thread here in QA titled "flashing ROMs correctly every time" .... so you can get some instruction on verifying MD5 of the download... don't worry, the thread will explain that you...
now proceed
4. boot to recovery
5. do a factory reset - 3 times do this, just to be thorough. people will say you don't need to, but like i said, just for the sake of removing variables
6. go to mounts and storage, format system 3 times - (yes, through recovery as well)
7. flash ROM, and reboot
EDIT*** i will say this, ALWAYS format system when flashing a new ROM
cobraboy85 said:
a few questions:
and i can verify the issue is something on your end, because the ROM you tried was mine, and nobody has had that issue (not booting it)
do this...
1. make sure you have the latest version of clockwordmod, don't use twrp
2. re-download my ROM (just for sake of not adding any other variables to your issue, because mine should boot)
3. put ROM on external SD card
before continuing... take a quick look at my thread here in QA titled "flashing ROMs correctly every time" .... so you can get some instruction on verifying MD5 of the download... don't worry, the thread will explain that you...
now proceed
4. boot to recovery
5. do a factory reset - 3 times do this, just to be thorough. people will say you don't need to, but like i said, just for the sake of removing variables
6. go to mounts and storage, format system 3 times - (yes, through recovery as well)
7. flash ROM, and reboot
EDIT*** i will say this, ALWAYS format system when flashing a new ROM
Click to expand...
Click to collapse
thanks for the info, will try this all out soon. I've been flashing roms for years now and have never run into anything like this, and as previously stated, this didn't occur solely with your rom which has me thinking something has happened to the phone itself. will get back to you soon and once again thank you
chucktdriscoll said:
Did you wipe data and cache when you flashed the new rom?
Click to expand...
Click to collapse
of course, wiped data, cache, & delvik
nyyankees1237 said:
of course, wiped data, cache, & delvik
Click to expand...
Click to collapse
my point is...
coming from a cm based ROM, or aokp, whatever you said... you would want to format system as well.
nyyankees1237 said:
After trying to flash a new rom after being on AOKP M1 for a little while (http://forum.xda-developers.com/showthread.php?t=1875923) the phone got stuck at the Black and white Samsung Galaxy SIII screen and didn't boot upon hitting reboot system now on cwm. Tried again, tried reflashing and the whole 9 yards wouldn't boot at all. So I turned to odin and went to the prerooted latest JB build (http://forum.xda-developers.com/showthread.php?t=1949687) and then reflashed touch cwm and tried to reflash the rom. Same problem. So, I odin'd back to the non rooted UVDLJA. Rerooted and reflashed cwm and blahblahblah. I said hmm maybe it's the rom, I then tried to flash this rom (http://forum.xda-developers.com/showthread.php?t=1993934) and when I tried to reboot system now after the process; again the phone got stuck at the black and white Samsung Galaxy SIII screen and did not boot. The phone works fine when I odin it to stock builds but refuses to boot custom roms. Can someone help me here? I haven't been able to find a solution for days. :crying:
PS I'm a noob, don't kill me lol
edit: forgot to include I have the Tmobile variant
Click to expand...
Click to collapse
I was having some of the same issues. I downloaded XquiziT's Superwipe and ran it by installing from external sd card. I ran it three times to clear everything out, then I wiped data, cache and the rest three times.
No probs for me after that.
Will definitely give that a try as well! Thank you! Will post my results when the holiday is over.
Happy thanksgiving
Sent from my SGH-T999 using xda app-developers app
Placed an item in the original topic already, decided to make a seperate one for more attention:
I'm running FXP151 on my Xperia S, with a NovaKernel flashed on top of it. Now I want to update FXP to 201, but the last times I tried flashing a newer version straight on top of the current setup, it will always halt with an error. Which in turn makes the phone unusable until I flash the original boot.img, wipe all data and restore a backup.
What should I do in order to update FXP properly? I've got the feeling that the NovaKernel shouldn't be there when I do, but I'll leave it to the experts.
Thanks in advance!
----
What I do to prevent this from happening again, is flash the FreeXperia Recovery by Bin4ry via fastboot before I update. That recovery seems to work out of the box. After doing the update, I flash Nova back and it boots without issues.
rc_enzo said:
Placed an item in the original topic already, decided to make a seperate one for more attention:
I'm running FXP151 on my Xperia S, with a NovaKernel flashed on top of it. Now I want to update FXP to 201, but the last times I tried flashing a newer version straight on top of the current setup, it will always halt with an error. Which in turn makes the phone unusable until I flash the original boot.img, wipe all data and restore a backup.
What should I do in order to update FXP properly? I've got the feeling that the NovaKernel shouldn't be there when I do, but I'll leave it to the experts.
Thanks in advance!
Click to expand...
Click to collapse
I don't know about any one else but I always had problems flashing zips from nova kernel so just extract fxp kernel from the Rom and install with fxp kernel, then just flash the Rom with out any wipes
Sent from my LT26i using xda premium
Try flashing the update, boot it, wait a bit, then reboot and install the kernel. Wipe dalvik.
Sent from my LT26i using Tapatalk
Tried flashing 202 over 201 today. Immediately got a "some symlinks failed"-notice and was forced to do a restore onceagain. Without any changed kernels. Gives me an 'error while formatting cache' when restoring, seen that before. It is starting to get on my nerves.
I'm keeping up Titanium backups from now on...
Update: did a dalvik wipe, fixed permissions, tried rebooting and erasing cache multiple times (to no avail), but it managed to boot to the launcher somehow. Can't see why, because the cache is crappy.
I have an I747 on T-Mobile.
I recently installed SlimBean 4.3 on it, and it started up and worked fine. But when I went to restart it, it hung on the "SlimBean" screen. Never got to the bootanimation.
I read online that there's issues when coming from another 4.3 rom, and I had previously been running CyanogenMod 10.2, although it was a nightly and it crashed, corrupting my data. I decided not to try that again.
So after that experience with SlimBean, I tried to flash BeanStalk from the T-Mobile GS3 forum. This is also a 4.3 rom, and it ran fine on my I747, except when I went to reboot. It too hung on the logo.
And yes, I have wiped internal storage, and I'm running the latest version of TWRP. I even tried to flash Samsung's stock firmware with Odin, and it worked, but it wouldn't boot (or maybe I'm overestimating how quickly TouchWiz can boot). It overrode my recovery, like I was expecting, so I flashed TWRP with Odin and then proceeded to flash SlimBean 4.3 again. Same problem.
Does anyone have a solution to this? It's been driving me crazy. I will try some other 4.3 roms and see if they're all doing this.
danielhep said:
I have an I747 on T-Mobile.
I recently installed SlimBean 4.3 on it, and it started up and worked fine. But when I went to restart it, it hung on the "SlimBean" screen. Never got to the bootanimation.
I read online that there's issues when coming from another 4.3 rom, and I had previously been running CyanogenMod 10.2, although it was a nightly and it crashed, corrupting my data. I decided not to try that again.
So after that experience with SlimBean, I tried to flash BeanStalk from the T-Mobile GS3 forum. This is also a 4.3 rom, and it ran fine on my I747, except when I went to reboot. It too hung on the logo.
And yes, I have wiped internal storage, and I'm running the latest version of TWRP. I even tried to flash Samsung's stock firmware with Odin, and it worked, but it wouldn't boot (or maybe I'm overestimating how quickly TouchWiz can boot). It overrode my recovery, like I was expecting, so I flashed TWRP with Odin and then proceeded to flash SlimBean 4.3 again. Same problem.
Does anyone have a solution to this? It's been driving me crazy. I will try some other 4.3 roms and see if they're all doing this.
Click to expand...
Click to collapse
p
I had something that sounds similar when I was trying to update from task's 4.2.2 to 4.3. Kept stopping at the kernel screen ( after the usual wiping of caches and system). Finally, someone recommended that, in addition to wiping data, that I format data as well. This basically wipes everything (i was using twrp 2.3.3.1). After doing this, I reinstalled the ROM and gapps and it works now.
Not sure this is what you experienced but it sounded similar. Before doing anything else, be sure that you have a back up and that you have removed any external sd card, should you have to go back. Good luck.
captican said:
p
I had something that sounds similar when I was trying to update from task's 4.2.2 to 4.3. Kept stopping at the kernel screen ( after the usual wiping of caches and system). Finally, someone recommended that, in addition to wiping data, that I format data as well. This basically wipes everything (i was using twrp 2.3.3.1). After doing this, I reinstalled the ROM and gapps and it works now.
Not sure this is what you experienced but it sounded similar. Before doing anything else, be sure that you have a back up and that you have removed any external sd card, should you have to go back. Good luck.
Click to expand...
Click to collapse
Yeah, I did that. I wiped everything I could and formatted data. Maybe I should try installing a different kernel?
With your issue, was it stopping on the first boot or did you get it running once then it stopped?
danielhep said:
I have an I747 on T-Mobile.
I recently installed SlimBean 4.3 on it, and it started up and worked fine. But when I went to restart it, it hung on the "SlimBean" screen. Never got to the bootanimation.
I read online that there's issues when coming from another 4.3 rom, and I had previously been running CyanogenMod 10.2, although it was a nightly and it crashed, corrupting my data. I decided not to try that again.
So after that experience with SlimBean, I tried to flash BeanStalk from the T-Mobile GS3 forum. This is also a 4.3 rom, and it ran fine on my I747, except when I went to reboot. It too hung on the logo.
And yes, I have wiped internal storage, and I'm running the latest version of TWRP. I even tried to flash Samsung's stock firmware with Odin, and it worked, but it wouldn't boot (or maybe I'm overestimating how quickly TouchWiz can boot). It overrode my recovery, like I was expecting, so I flashed TWRP with Odin and then proceeded to flash SlimBean 4.3 again. Same problem.
Does anyone have a solution to this? It's been driving me crazy. I will try some other 4.3 roms and see if they're all doing this.
Click to expand...
Click to collapse
I had the same problem since 4.3 came out. It has to do with partition tables... What i've done to correct the problem:
- Odin back to stock
- Format entire phone. (Complete wipe) + Dalvik and cache
- Odin stock with root
- Replaced TWRP recovery for CWM
- Flashed 4.3 ROM and VOILA
- I have tried every 4.3 rom ever since with no problems
Don't (Complete wipe) with Twrp recovery, it seems to mess up the partitions.
Hope this works for you
Cheers
danielhep said:
Yeah, I did that. I wiped everything I could and formatted data. Maybe I should try installing a different kernel?
With your issue, was it stopping on the first boot or did you get it running once then it stopped?
Click to expand...
Click to collapse
It loaded the first time and then rebooted, freezing on the kernel screen. I could get into recovery, and restore a previous ROM but it would hang up on 4.3. I described the steps I had taken when someone suggested reformatting data. I tried again and it is working now.
The method described in the other post may also solve your problem. I say that because I cannot update twrp to 2.6.1, at least via goo manager. I have not tried using Odin to update (yet).
I have this same as problem. It's annoying. I reflashed the rom 15 times yesterday. I'm gonna try and see if Deathstrings idea works.
Sent from my SGH-I747 using XDA Premium 4 mobile app
I managed to load a stock rom back to the phone but again, it hung on the SAMSUNG screen. Took it to "a guy" and he did a
key sequence and got it to boot. Woulnd't tell me what it was........
ANy one know???
Apocalypse487 said:
I have this same as problem. It's annoying. I reflashed the rom 15 times yesterday. I'm gonna try and see if Deathstrings idea works.
Sent from my SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This happened to me after I flashed back but formatting data got it to work (but I have had more problems with apps not installing properly but I learned how to deal with that...still cannot update TWRP via goo manager; waiting on trying it with Odin).