Related
I bricked it. I had TWRP installed, and running a debloated Odexed version of Stock. I attempted to flash Slim Bean 6.5 Weekly with Aroma addons. The Aroma ended up borking my recovery. It bootloops pre-recovery mode. I can get into Download mode and Odin'd back to Stock, but it's still won't go into recovery and vibrate loops with a black screen.
Anyone know how to fix this? Damn locked bootloader!!!
Did you try and reflash recovery ? Does the phone boot up once you restore via Odin ?
Have you tried flashing twrp via Odin?
I have not tried flashing TWRP with Odin... is there a Odin version of TWRP?
It did not boot after flashing stock. I'd like to Odin TWRP if it's available.
I found an Odin TWRP.tar for SGS3, but nothing for S4, yet. Need a little more help.
Did you try rooting and flashing twrp via goomanager? I had something similar happen to me on my skyrocket and that's how I fixed it.
Aroma does not work on the GS4 yet. At least that is what I have been reading.
Sent from my SAMSUNG-SGH-I337 using xda premium
TheAxman said:
Aroma does not work on the GS4 yet. At least that is what I have been reading.
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
This version of CWM claims to work with Aroma on the S4...
http://forum.xda-developers.com/showthread.php?t=2322682
scott14719 said:
This version of CWM claims to work with Aroma on the S4...
well lets take a look see...shall we. thanks
Click to expand...
Click to collapse
came across this thread: http://forum.xda-developers.com/showthread.php?t=2281287
it converts an img to an odin-flashable tar.
i went ahead and converted the latest twrp img for the at&t S4 and have attached it. i have not tested it as i am not near my device at the moment. if you decide to try it, unzip the tar.md5 and flash at your own risk as i have not tested this method by @cabloomi.
False aroma works fine with twrp on a gs4.
Sent from my SGH-I337 using Tapatalk 4 Beta
This happened to me. Use odin to put TWRP back on. You'll be fine.
Sent from my SGH-I337 using Tapatalk 2
Yeah I had this a couple different times trying to get rid of the custom/lock icon boot up. Flash fresh stock rom, root it and install recovery with "Root and Recovery for ATT-TMO GS4-CASUAL-R527b" --> http://forum.xda-developers.com/showthread.php?t=2297900 then flash the recovery you want etc, and restore Nandroid of backed up rom. Worked for me!
Everyone keeps saying to Odin TWRP like it's a common thing. I have yet to find a Odin version of TWRP that's loki'd for the S4. If you have done this, and it worked, please supply a link to the correct file. In this case an Odin version of TWRP. Thank you
JJ5150 said:
I bricked it. I had TWRP installed, and running a debloated Odexed version of Stock. I attempted to flash Slim Bean 6.5 Weekly with Aroma addons. The Aroma ended up borking my recovery. It bootloops pre-recovery mode. I can get into Download mode and Odin'd back to Stock, but it's still won't go into recovery and vibrate loops with a black screen.
Anyone know how to fix this? Damn locked bootloader!!!
Click to expand...
Click to collapse
I had a similar issue. When you hold the key combination to boot into recovery, do it for more than one cycle. Sometime for some reason it doesn't take the first time so keep holding the buttons. After getting into android recovery, clear cache and reset the phone.
JJ5150 said:
Everyone keeps saying to Odin TWRP like it's a common thing. I have yet to find a Odin version of TWRP that's loki'd for the S4. If you have done this, and it worked, please supply a link to the correct file. In this case an Odin version of TWRP. Thank you
Click to expand...
Click to collapse
When I had the problem is sounds like your having I Odined the Stock image back to the phone and then cleared the dalvik and cache with the stock recovery menu, then I was able to boot, I then rooted and used the debloater program found here on the forums and then just downloaded goomanager and installed TWRP, the one it pushes is LOKIed for you.
This is also the only .img file I can find for the our version of TWRP. IIRC you can use Odin to flash it
EDIT: Like trublu said, you may have to do it several times (clearing the caches in the stock recovery after ODIN)
JJ5150 said:
Everyone keeps saying to Odin TWRP like it's a common thing.
Click to expand...
Click to collapse
you are correct in that twrp has not posted tars on their website yet for download. they have, however, posted imgs. find a way or find someone to convert that img to an odin-flashable tar and you'll be all set.
JJ5150 said:
I have yet to find a Odin version of TWRP that's loki'd for the S4.
Click to expand...
Click to collapse
i believe that all s4 recoveries are "loki'd", if you will.
xBeerdroiDx said:
you are correct in that twrp has not posted tars on their website yet for download. they have, however, posted imgs. find a way or find someone to convert that img to an odin-flashable tar and you'll be all set.
i believe that all s4 recoveries are "loki'd", if you will.
Click to expand...
Click to collapse
The Tmo and Sprint variants do not require Loki'd recoveries, as their bootloaders are not locked.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
After trying many options available to me such as, Flashing Stock with Odin and trying to access recovery via the three finger method, and trying to convert a TWRP.img file to a .tar file... which I managed to successfully flash, but to no avail. I'm stuck at the vibrating boot loop dead screen, soft brick scenario.
I found these guys in a similar thread http://mobiletechvideos.com/
I called them and they were really nice and professional. I shipped out my phone for Brick Repair today. I believe I'll be happy with the results from these guys from they way they conduct themselves in their videos.
I'll report back when I have my fixed, unbricked S4 back in my hands
JJ5150 said:
After trying many options available to me such as, Flashing Stock with Odin and trying to access recovery via the three finger method, and trying to convert a TWRP.img file to a .tar file... which I managed to successfully flash, but to no avail. I'm stuck at the vibrating boot loop dead screen, soft brick scenario.
I found these guys in a similar thread http://mobiletechvideos.com/
I called them and they were really nice and professional. I shipped out my phone for Brick Repair today. I believe I'll be happy with the results from these guys from they way they conduct themselves in their videos.
I'll report back when I have my fixed, unbricked S4 back in my hands
Click to expand...
Click to collapse
They do great work..used them 2 years ago. With a mytouch..ouch..
Sent from my SAMSUNG-SGH-I337 using xda premium
JJ5150 said:
After trying many options available to me such as, Flashing Stock with Odin and trying to access recovery via the three finger method, and trying to convert a TWRP.img file to a .tar file... which I managed to successfully flash, but to no avail. I'm stuck at the vibrating boot loop dead screen, soft brick scenario.
I found these guys in a similar thread http://mobiletechvideos.com/
I called them and they were really nice and professional. I shipped out my phone for Brick Repair today. I believe I'll be happy with the results from these guys from they way they conduct themselves in their videos.
I'll report back when I have my fixed, unbricked S4 back in my hands
Click to expand...
Click to collapse
It's called Jtag repair. And the guys you mentioned have saved many a ass with it. I've seen several good results. Unless something else is found, it is the only way I know of to fix a truly bricked phone. Some people (those who flash a lot and Dev a lot) have their own Jtag boxes.
BTW, which tool / method did you use to convert the .img to a TAR? I've seen a couple of methods and a tool or two but I was wondering if you used something I don't know about? TIA.
RESOLVED:
- Flashed a stock firmwire image from Sammobile using Odin. (AMDL)
- Did a factory reset in the stock recovery TWICE to get it to finally boot.
- Rooted with motochopper
- Installed TWRP
- Back to Task650.
Okay, so I'm a bit stuck. I was running the newest Task650 rom and KT's 9/17 kernel.
I updated to the 10/20 kernel as soon as it was released and it bugged my phone. Blew up everything, glitched my DPI and colors. It was unusable, however the weirdest part is that my custom recovery was removed so I can't seem to flash the old kernel to get my device back to normal.
I tried using odin but it just keeps failing, so I really am unsure what to do now. If I could get the previous kernel back onto it, it would be fine.
Any help? I can't seem to find a .tar.md5 file for TWRP or clockworkmod to flash a new recovery in Odin. I tried Philz .tar.md5 files but it fails as well.
Click to expand...
Click to collapse
As long as your not MF3
try goo manager for TWRP
or
Try ROM manager just to flash CWM
Note: do not use ROM manager for nothing else if you didn't already know.
Sent from my GT-I9505G using xda premium
jball said:
As long as your not MF3
try goo manager for TWRP
or
Try ROM manager just to flash CWM
Note: do not use ROM manager for nothing else if you didn't already know.
Sent from my GT-I9505G using xda premium
Click to expand...
Click to collapse
I cannot use the Google Playstore.. my entire screen is over scaled and impossible to navigate.
So no use of DPI settings.can you use ADB or terminal emulator
Sent from my SAMSUNG-SGH-I337 using xda premium
when you say you tried odin, are you saying you tried flashing the stock rom (MDL), tried flashing a custom recovery tar, or both? what error is it giving?
unfortunately i think kt accidentally uploaded a 4.2.2 kernel and thats what you downloaded. check out his thread and see what anyone else in your situation may have done already to remedy this. good luck
Can you reroot by flashing an autorooter through download mode? Doing so might enable you to flash kernels again.
Is factory reset an option?
xBeerdroiDx said:
when you say you tried odin, are you saying you tried flashing the stock rom (MDL), tried flashing a custom recovery tar, or both? what error is it giving?
unfortunately i think kt accidentally uploaded a 4.2.2 kernel and thats what you downloaded. check out his thread and see what anyone else in your situation may have done already to remedy this. good luck
Click to expand...
Click to collapse
I managed to get the latest stock firmwire (AMDL 4.2.2) off of Sammobile. I did successfully flash the stock .tar.md5 image through Odin, using the PDA slot. Phone seemed to restart and boot right up, but now gets stuck at the AT&T logo. It makes the boot sound and than BAM; frozen.
Now I am truly stuck. Seems flashing the stock image didn't work.. unless I did it wrong through Odin but I doubt it. These are the steps I took,
- Start Odin
- Connect phone in downloaded mode
- Click PDA (select the I337UCUAMDL_I337ATTAMDL_ATT.tar.md5 file)
- Wait for it to confirm the firm, than hit start.
- After waiting about 5 minutes it's successful.
Am I doing ANYTHING wrong?
Te3k said:
Can you reroot by flashing an autorooter through download mode? Doing so might enable you to flash kernels again.
Is factory reset an option?
Click to expand...
Click to collapse
Do a factory reset in the stock recovery after you flash with Odin. It'll get you past the boot loop.
jd1639 said:
Do a factory reset in the stock recovery after you flash with Odin. It'll get you past the boot loop.
Click to expand...
Click to collapse
Did a Factory reset in the stock recovery, wiped all data etc. Still gets stuck at the AT&T logo.
EDIT: Did it twice and it worked!
Br4nd3n said:
Did a Factory reset in the stock recovery, wiped all data etc. Still gets stuck at the AT&T logo.
EDIT: Did it twice and it worked!
Click to expand...
Click to collapse
How long have you given the boot? The first boot can take a long time. 5 minutes or more isn't unheard of.
jd1639 said:
How long have you given the boot? The first boot can take a long time. 5 minutes or more isn't unheard of.
Click to expand...
Click to collapse
Gave it about 2 hours the first time.. knew it was stuck. However I did the factory reset twice in a row, and it finally booted. Just did a quick root through Motochopper, installed TWRP and now I'm back and running on Task650 :good:
Good deal
Sent from my GT-I9505 using xda premium
Br4nd3n said:
Gave it about 2 hours the first time.. knew it was stuck. However I did the factory reset twice in a row, and it finally booted. Just did a quick root through Motochopper, installed TWRP and now I'm back and running on Task650 :good:
Click to expand...
Click to collapse
:good:
Let me preface this by saying I have searched here and other websites and have tried the methods I have found and cannot get the issue fixed. ANY help is greatly appreciated.
I have a sprint s4 l720. I rooted it and installed a custom rom and twrp a few months ago. I recently saw that 4.4 came out and wanted to try a new rom. I first booted into recovery and tried to restore my system back to the original stock rom that I had backed up when I first installed the new one. I was able to restart it and it loaded fine but if I pull the battery or do a restart it gets stuck at the samsung splash screen. I have tried advanced wipe, format data, wipe dalvik and cache and even installing other roms and it still gives me the same behavior. I have tried other methods to re-install the stock rom and I keep encountering issues. I downloaded the most recent ODIN and the samsung USB drivers and "jflterspr16gb.pit" and sprints .tar.md5 file. It loads into odin fine and shows the added on the dialogue box and I load the respective files into odin and it keeps failing. I am at a lost.
All I want is to be able to add either the stock rom or preferably the custom 4.4 rom and work as it used to. Restart when needed and not get stuck at the boot screen. ANY help is much appreciated. any ideas on what I am doing wrong? Thanks guys!
Anything 4.4 at this point is custom. Just boot into recovery, wipe and flash the 4.4 ROM.
Sent from my SPH-L720 using Tapatalk
if your at ota MJA then trying to odin md5 will not work. Did you take the MJA update?
frostedunit said:
Anything 4.4 at this point is custom. Just boot into recovery, wipe and flash the 4.4 ROM.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
I have tried that. I boot into twrp and have tried formatting all data and just wipe data and then I restart and load gummy 4.4 and the gapps for it and then wipe the dalvik and cache. It will boot into the gummy rom fine and give me no issues, but it is if I try to restart it or power it down and power it back on is where it gets stuck at the samsung splash screen.
rheller219 said:
if your at ota MJA then trying to odin md5 will not work. Did you take the MJA update?
Click to expand...
Click to collapse
I am not for sure what the MJA is. Could you pleaes elaborate to me? Thanks.
pgrim85 said:
I have tried that. I boot into twrp and have tried formatting all data and just wipe data and then I restart and load gummy 4.4 and the gapps for it and then wipe the dalvik and cache. It will boot into the gummy rom fine and give me no issues, but it is if I try to restart it or power it down and power it back on is where it gets stuck at the samsung splash screen.
I am not for sure what the MJA is. Could you pleaes elaborate to me? Thanks.
Click to expand...
Click to collapse
Where does it stop on the odin error? And dont use the pit file. Try again without the pit file.
Sent from my SPH-L720 using xda app-developers app
You should always be on a stock ROM of the latest version prior to flashing an unofficial, newer Android ROM.
For example:
If you're trying to flash 4.4, you should be on stock 4.3 such as this: http://forum.xda-developers.com/showthread.php?t=2505025
MJA is the latest official 4.3 build for the Sprint S4.
If you're on 4.2, you should update to 4.3 stock, then flash 4.4. This generally prevents any unexpected results.
Furthermore, always ensure you are flashing from a trusted recovery such as TWRP and CWM.
Occasionally, one recovery will not run the install script properly.
If you are certain you are doing the install right, you can try from another recovery.
Additionally: If you are having trouble with Odin on Windows 8, ensure your computer does not report a driver malfunction when you plug your device in after entering download mode.
This can possibly be fixed by running Odin as administrator. Or, you can attempt to manually install the USB drivers by downloading them, disconnecting from the Internet, uninstalling previous drivers, then manually installing the USB package you downloaded.
Sent from my SPH-L720 using xda app-developers app
R0CKSTAR3N3RGY said:
You should always be on a stock ROM of the latest version prior to flashing an unofficial, newer Android ROM.
For example:
If you're trying to flash 4.4, you should be on stock 4.3 such as this: http://forum.xda-developers.com/showthread.php?t=2505025
MJA is the latest official 4.3 build for the Sprint S4.
If you're on 4.2, you should update to 4.3 stock, then flash 4.4. This generally prevents any unexpected results.
Furthermore, always ensure you are flashing from a trusted recovery such as TWRP and CWM.
Occasionally, one recovery will not run the install script properly.
If you are certain you are doing the install right, you can try from another recovery.
Additionally: If you are having trouble with Odin on Windows 8, ensure your computer does not report a driver malfunction when you plug your device in after entering download mode.
This can possibly be fixed by running Odin as administrator. Or, you can attempt to manually install the USB drivers by downloading them, disconnecting from the Internet, uninstalling previous drivers, then manually installing the USB package you downloaded.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
Is there a way I can fresh restart my phone? I do not have any recovery files since I wiped my phone in its entirety and I had no backed it up on the SD card, rookie mistake, I know. I don't necessarily need 4.4, but what I do need is my phone to boot up properly whenever I choose and not have to boot into recovery, wipe the phone and then when I turn it on have to go through the setup process.
ROMANTiC KiD said:
Where does it stop on the odin error? And dont use the pit file. Try again without the pit file.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
I will have to look where it stops again tonight. but it does connect by showing the "pass" on the odin box on the left. could it be that I have the wrong odin? I noticed the top of odin it shows epic 4g when I have a galaxy s4, is this ok or is there a way I can change that? I dl the odin from a forum that was specifically a tutorial on how to flash the galaxy s4, sprint specifically, so I figured it would be the correct one. Also, I did try again without the pit file and it still failed.
Thanks for the help so far guys
Some of the Odin packages have multiple versions thrown together. Make sure to use the highest version number (3.07?) And that you are putting the .tar in the PDA slot. If all else fails, try deleting the .md5 off the end of the file before you load it in Odin. Used to work on OG Epic sometimes.
Sent from my SPH-L720 using Tapatalk
Was testing kn0x0ut on our device when I ended up flashing an empty system image. I was on MK2 and attempted to use the MJ6-MJ9 method of flashing just enough files to pass the OTA checks. They didn't flash, and now it says my PIT is broken. I have recovery, and the data partition is in place as on a normal boot it loads to black screen with a blue LED. I can use adb, but there is no root so I can't restore my system. Any suggestions? I'm busy today so I won't be able to reply much, but I can gladly give more information.
EDIT: The system apparently isn't empty. The partition got flashed at some point and appears to have MF3 files.
However, there is still no root and it boots up to nothing but a black screen with blue LED still. I can't get the small update from cache that the MJ6-MJ9 thread mentions. Also, attempting a recovery boot results in the Secure Fail: Kernel screen. Recovery is fixed with the MJ6 recovery file.
FIXED: I was able to get it working following the instructions again. Not sure what the exact issue was with the first time i tried, but flashing the MJ6 recovery makes recovery boot again. I had to flash the two emergency tars, flash the recovery tar again, and then boot into recovery. It then applied the update from cache and on next reboot i went back in and used the sideload.
Have you tried ADB sideloading the update through the recovery?
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Supreme Dynamite said:
Have you tried ADB sideloading the update through the recovery?
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It doesn't go through since it fails the file check.
Possible help
Hey there, I Gorked my i337 at&t version on Thanksgiving day! I was able to go to this thread and just used Odin to flash the two .tar files and then was able to sideload the mk2 update. Boom phone was back to 4.3
http://forum.xda-developers.com/showthread.php?t=2526964&page=19
joshzdad2013 said:
Hey there, I Gorked my i337 at&t version on Thanksgiving day! I was able to go to this thread and just used Odin to flash the two .tar files and then was able to sideload the mk2 update. Boom phone was back to 4.3
http://forum.xda-developers.com/showthread.php?t=2526964&page=19
Click to expand...
Click to collapse
That's what i've been trying to no avail. The first small update from cache never happened and now it's broken even more.
EDIT: Recovery is booting after flashing the MJ6 recovery, surprisingly. Will attempt instructions one more time and report back.
I beleive i just said screw it since I knew I was boned! I then just flashed recovery-mj6.tar.md5 not even sure if it worked. Then flashed the mf3-emergency-part-1.tar.md5 then the mf3-emergency-part-2.tar.md5 and finally I beleive I tried the side load of my mk2 full update file and it worked.
joshzdad2013 said:
I beleive i just said screw it since I knew I was boned! I then just flashed recovery-mj6.tar.md5 not even sure if it worked. Then flashed the mf3-emergency-part-1.tar.md5 then the mf3-emergency-part-2.tar.md5 and finally I beleive I tried the side load of my mk2 full update file and it worked.
Click to expand...
Click to collapse
Good job man you had me on the seat of my pants reading this.
ROOTED ATT MK2 using Tapatalk
Hello.First post here.
I currently have been using CM11 for a few months now but miss some features on stock. (multiwindow, air view) so I installed Sacs ROM.
Everything was working great today except a known problem is wifi will not work due to radio opbstructions (i believe). So i attempted to change the baseband to MF9.
At first, Odin started then immidately it failed. The error read 'Fused 4 Binary 1'
So i assumed it was a connection error. I loaded back into download mode and tried again. Failed.
At this point i thought screw it, and took the battery out. tried to reboot and stuck at the soft brick "Firmware upgrade encountered and issue. Please select recovery mode in Kies and try again"
I installed Kies. Plugged in my phone. Drivers installed but Kies will not connect. Try to do 'Firmware Upgrade and Initialization'
However Kies will NOT accpet my S/N number. i tried everything. writing it all out or with a space every 3 numbers or with 'DEC' at the front. nothing worked.
I even called sprint to double check S/N (ESN/DEC)
so basically I'm soft bricked and Kies is screwing me over. Any ideas?
Have you tried to odin back to stock?
Sent from my SPH-L720 using XDA Premium 4 mobile app
ROMANTiC KiD said:
Have you tried to odin back to stock?
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
thats the one thing i want to avoid.
by reverting to stock wont i lose root access? i have a backup of my old CM ROM from before i flashed sacs. should i revert to stock then restore to CM then reinstall Sacs?
whatthe_fuzz said:
thats the one thing i want to avoid.
by reverting to stock wont i lose root access? i have a backup of my old CM ROM from before i flashed sacs. should i revert to stock then restore to CM then reinstall Sacs?
Click to expand...
Click to collapse
Yes but it takes all but about 30 seconds to root again
You could go straight to sacs after rooting.
Sent from my SPH-L720 using Tapatalk
daniel4653 said:
Yes but it takes all but about 30 seconds to root again
You could go straight to sacs after rooting.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
ok that might leave me with a cleaner install also.
wheres the stock file i can flash on Odin?
also how should i update the radio if it didnt work the first time?
Thank you for the help
whatthe_fuzz said:
ok that might leave me with a cleaner install also.
wheres the stock file i can flash on Odin?
also how should i update the radio if it didnt work the first time?
Thank you for the help
Click to expand...
Click to collapse
If you flash a full stock tar you won't have to flash radio.
Do a search please for the tar.
Sent from my SPH-L720 using XDA Premium 4 mobile app
leaderbuilder said:
If you flash a full stock tar you won't have to flash radio.
Do a search please for the tar.
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i searched around and eventually found a working .md5 file. its apparently is stock. got my phone to start booting but it got stuck at the yellow sprint screen. im going to try to boot into safe mode. any ideas how to access my recovery file? i have one form CWM and one from Ti Backup
which tar did you flash through Odin? MF9, MK2 or NAE?
IF you were on MF9 and flashed the full MF9 tar you can try and flash again. Just power off phone completely, go to download mode, attach and run Odin. (same for MK2 or NAE) BUT if you tried flashing MJA/MK2 or NAE you cannot go back to MF9. Things you should have read about already.
If it hangs on boot after flashing, power off completely, boot to stock recovery and do a factory reset and then let it restart first reboot can take 5 to 10 earth minutes.
You can then root via CF-Autoroot or Saferoot, install goomanager to grab a custom recovery (CWM or TWRP) OR Odin said recoveries (Philz, TWRP etc.)
leaderbuilder said:
which tar did you flash through Odin? MF9, MK2 or NAE?
IF you were on MF9 and flashed the full MF9 tar you can try and flash again. Just power off phone completely, go to download mode, attach and run Odin. (same for MK2 or NAE) BUT if you tried flashing MJA/MK2 or NAE you cannot go back to MF9. Things you should have read about already.
If it hangs on boot after flashing, power off completely, boot to stock recovery and do a factory reset and then let it restart first reboot can take 5 to 10 earth minutes.
You can then root via CF-Autoroot or Saferoot, install goomanager to grab a custom recovery (CWM or TWRP) OR Odin said recoveries (Philz, TWRP etc.)
Click to expand...
Click to collapse
I think i fixed it.
Problems resolved.
The issue was i had Sacs v4 which didnt support wifi and i read that it needed MF9 firmware.
i had a lapse in judgement and without thinking tried to go back from MJA. didnt catch it until now.
I eventually found the correct stock file. eventually got into the phone. rerooted and in the process of install the proper sacs ROM (v5.6)
this was a simple error that i shouldve caught thanks guys!
hopefully this ROM will work with wifi...
BTW, all my backups were wiped
Your backups weren't on your external sd? Ooo, that sucks. Glad you got it.
Sent from my SPH-L720 using XDA Premium 4 mobile app