I've been using the following MIUI for a few versions, and the most recent one breaks wifi calling for me. When I first flashed the rom, it did an endless reboot until I booted the rom in safemode. Then it would actually load correctly but wifi calling force closes every time.
Has this happened for anyone else? Any ideas?
http://forum.xda-developers.com/showthread.php?t=1060415
jamtown85 said:
I've been using the following MIUI for a few versions, and the most recent one breaks wifi calling for me. When I first flashed the rom, it did an endless reboot until I booted the rom in safemode. Then it would actually load correctly but wifi calling force closes every time.
Has this happened for anyone else? Any ideas?
http://forum.xda-developers.com/showthread.php?t=1060415
Click to expand...
Click to collapse
I understand you don't have enough post to do so in the Dev section. But that is where this really belongs. You'll get more reply and it'll bring more attention because the dev will read that thread looking for issues.
jamtown85 said:
I've been using the following MIUI for a few versions, and the most recent one breaks wifi calling for me. When I first flashed the rom, it did an endless reboot until I booted the rom in safemode. Then it would actually load correctly but wifi calling force closes every time.
Has this happened for anyone else? Any ideas?
http://forum.xda-developers.com/showthread.php?t=1060415
Click to expand...
Click to collapse
Wifi calling is working and fully functional... I would suggest to wipe /data and reflash... report back or pm me
sent from my demonSPEED_EXT4 Glacier using XDA Premium App
Yeah I know it should have been in the dev section, but as you stated, I can't post there yet. Hopefully can after this post!
thederekjay, thanks for the response! I reflashed the rom twice with the same response both times. I then redownloaded the rom, checked the md5 and verified that it was the same as the previous download and it was, but still had the same issue. When I first flash the rom and it boots into it, it endlessly reboots, never getting passed the gingerbread MIUI screen, until I hold menu and let it boot into safe mode. I then reboot the phone, and it will boot normally but wifi will FC immediately and every time I run it after. Everything else seems to work flawlessly though. WIFI calling is a big deal to me though because I get poor reception in my apartment so I've relied on it in the past. I did notice that no one else reported this issue though. Weird that I'm the only one having it. I'll try to reflash with the new update you posted the other day to fix the MMS issue and see if that works better.
BTW, love the rom! Thanks for the work you put into it!
I believe that it's clockwork not wiping correctly regardless of reflashing the recovery.
Mount/data
Mount/cache
Mount/system
Format/data
Format/cache
Format/system
Then go back wipe/data factory reset
Wipe cache
Wipe dalvik.
Install the rom.
Sent from my demonSPEED Glacier using XDA Premium App
I'll try this as soon as I get home!
also, I noticed that your signature, thederekjay, says that you are using ext4. A friend of mine mentioned that on his galaxy S captivate that he switched to ext4 and it ran much faster. Do I need to do something special for that, and is it advantageous to do so?
jamtown85 said:
also, I noticed that your signature, thederekjay, says that you are using ext4. A friend of mine mentioned that on his galaxy S captivate that he switched to ext4 and it ran much faster. Do I need to do something special for that, and is it advantageous to do so?
Click to expand...
Click to collapse
It would be added into the rom Friday. Ext4 has significant speed boost over ext3. The system is initially faster on start up. The overall os. Probably the reason Google choose to make gingerbread ext 4. Overall optimization by using it. Not all roms are full ext 4 usually ext3 mounted as ext4. The reason Samsung galaxy phones first ones were so slow were due to rfs really outdated. That's why when your friend used ext 4 it was a dramatic increase. This is pretty much the differences ext3 vs ext4.http://en.m.wikipedia.org/wiki/Ext4
Sent from my demonSPEED Glacier using XDA Premium App
Killbynature said:
I believe that it's clockwork not wiping correctly regardless of reflashing the recovery.
Mount/data
Mount/cache
Mount/system
Format/data
Format/cache
Format/system
Then go back wipe/data factory reset
Wipe cache
Wipe dalvik.
Install the rom.
Sent from my demonSPEED Glacier using XDA Premium App
Click to expand...
Click to collapse
That seemed to have fixed it! Thanks! I don't understand why that made a difference but it certainly did. Is there a bug in clockwork or something?
jamtown85 said:
That seemed to have fixed it! Thanks! I don't understand why that made a difference but it certainly did. Is there a bug in clockwork or something?
Click to expand...
Click to collapse
That's what I believe I don't know why it's doing that though. I thinking the standard wipe isn't actually mounting properly.
Sent from my demonSPEED Glacier using XDA Premium App
Related
Ok here's the deal you know how we always wipe out data cache and dalvik....well I was wondering is there anyway we can reformat the phone itself just to get all the ****(extra data )from all different roms being flashed out of it. I don't know if this exists but it might be a good idea to help with speed. The reason I think this is possible is because when flashing viper rom 3.0.2 it says lag fix is already installed when I tryto install and when I try to repair or remove it says its working fine but the quadrant isn't affected and lagfix is still red in the viper app. Must be stuck in memory somewhere....is this possible?
Sent from my SPH-D700 using XDA App
Cam3ron1 said:
Ok here's the deal you know how we always wipe out data cache and dalvik....well I was wondering is there anyway we can reformat the phone itself just to get all the ****(extra data )from all different roms being flashed out of it. I don't know if this exists but it might be a good idea to help with speed. The reason I think this is possible is because when flashing viper rom 3.0.2 it says lag fix is already installed when I tryto install and when I try to repair or remove it says its working fine but the quadrant isn't affected and lagfix is still red in the viper app. Must be stuck in memory somewhere....is this possible?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
nah i probably had a file in there that shouldn't have been in there... did you flash the a2sd files as well?
Nope just the rom
Sent from my SPH-D700 using XDA App
Wiped and installed like 3 times still laggy so im back on bonsai is there anyway to ise viper lagfix on other roms?? And theres no way for files to pile up in the flash mem of the phone at all
Sent from my SPH-D700 using XDA App
Please post questions in General section.
So I rooted and switched ROM's many times on my MT3g, and now that i'm trying it on my MT4g, I'm having hella trouble.
So I got to S=off and its perarooted now, with ClockworkMod Recovery image: 3.0.2.4. I tried to update the Kernel to KB-Kernel-2.4.8-108-CFS-SV... put my phone with the stock ROM into a boot loop, so i restored it. Tried to update the Kernel then immediately install CM-7.0.0... again put it into a boot loop, and had to restore. What am i missing here? Should be partitioning like with my MT3g? Should i be wiping? Is there something else I should be installing?
Some_Biker said:
Tried to update the Kernel then immediately install CM-7.0.0... again put it into a boot loop, and had to restore.
Click to expand...
Click to collapse
That's your problem. You can't flash a kernel before the ROM, because the ROM's standard kernel immediately overwrites it. Try wiping all 3 items in the recovery menu, flash CM7, and then let it boot. Once CM7 is stable, try flashing your kernel. Just make sure it is compatible.
Sweet, thanks. Hopefully it works.
Sent from my HTC Glacier using XDA App
Some_Biker said:
So I rooted and switched ROM's many times on my MT3g, and now that i'm trying it on my MT4g, I'm having hella trouble.
So I got to S=off and its perarooted now, with ClockworkMod Recovery image: 3.0.2.4. I tried to update the Kernel to KB-Kernel-2.4.8-108-CFS-SV... put my phone with the stock ROM into a boot loop, so i restored it. Tried to update the Kernel then immediately install CM-7.0.0... again put it into a boot loop, and had to restore. What am i missing here? Should be partitioning like with my MT3g? Should i be wiping? Is there something else I should be installing?
Click to expand...
Click to collapse
Yes wipe, thats the issue not what tj said even though his information is correct
Sent from my HTC Glacier using XDA Premium App
Some_Biker said:
Sweet, thanks. Hopefully it works.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
It will work.
1. Flash Rom
2. Wait 5 mins so everything loads
3. Reboot into recovery
4. Wipe cache then in advanced...wipe davlik cache
5. Select zip from sd card and flash new kernel
Follow this and you will be good to go everytime! Happy flashing!
Lakeshow423 said:
It will work.
1. Flash Rom
2. Wait 5 mins so everything loads
3. Reboot into recovery
4. Wipe cache then in advanced...wipe davlik cache
5. Select zip from sd card and flash new kernel
Follow this and you will be good to go everytime! Happy flashing!
Click to expand...
Click to collapse
Wipe before u flash tho
Sent from my HTC Glacier using XDA Premium App
mark manning said:
Yes wipe, thats the issue not what tj said even though his information is correct
Click to expand...
Click to collapse
But I did mention wiping, and that was my main thought as to why it's not booting.
TeeJay3800 said:
But I did mention wiping, and that was my main thought as to why it's not booting.
Click to expand...
Click to collapse
My bad read to fast
Sent from my HTC Glacier using XDA Premium App
Arrg... Maybe I'm just impatient... Or maybe I'm wiping the wrong 3... How long should I expect to wait and what 3 should I wipe?
Sent from my HTC Glacier using XDA App
Some_Biker said:
Arrg... Maybe I'm just impatient... Or maybe I'm wiping the wrong 3... How long should I expect to wait and what 3 should I wipe?
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Wipe factory data
Wipe catche
Then go into advanced wipe dalvik
Should take 30 secs max to wipe, 5 mins max to install and reboot
Then flash your Rom and reboot. Once its rebooted then try flashing the kernel. There is no reason that won't work assuming you do have s-off
Sent from my HTC Glacier using XDA Premium App
If what Mark said doesn't work, I'd look to a corrupt recovery image, or more likely a bad download or SD card.
Aww... I'd be hella sad if I had a bad sdcard. My problem was that I wasn't wiping the correct things, but now thanks to you great people I finally can flash again! Thanks!
Sent from my HTC Glacier using XDA App
Glad you got it working. If Mark or I have helped you, maybe you could hit the thanks button.
Make sure when you do a kernel you wipe cache and than davlvik and than flash the first time kernel and than repeat the process and than flash your desired kernel.
Sent from my HTC Glacier using XDA Premium App
I have a quick question. When switching ROMs should I also in addition to factory reset, also perform a system/wipe to wipe the already installed custom ROM? Thanks.
It is generally unnecessary, but not a bad idea to do so. Most devs have their updater script format /system, but you'll find the occasional one that omits that one line.
Sent from my Nexus 7 using Tapatalk HD
Alright. So I shouldn't worry about performing system wipe?
Sent from my Nexus 7 using xda app-developers app
tsmith9191 said:
Alright. So I shouldn't worry about performing system wipe?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I think it's better to wipe the system. As I've faced many kind of froblem because of a dirty flash. And I've seen many bug reports on several ROM thread and it just came out that it's not the ROM but the dirty flash is causing the problem. It will probably take 1-2hr to get back to the previous position so what's the big didfference??
____________________________________________
Please press the thanks button if you find this helpful.
ashik992 said:
I think it's better to wipe the system. As I've faced many kind of froblem because of a dirty flash. And I've seen many bug reports on several ROM thread and it just came out that it's not the ROM but the dirty flash is causing the problem. It will probably take 1-2hr to get back to the previous position so what's the big didfference??
____________________________________________
Please press the thanks button if you find this helpful.
Click to expand...
Click to collapse
OK. So when switching ROMs I should perform factory restore, wipe all caches, as well as system/wipe to erase the ROM currently installed. I have done it that way before but I always get nervous when I wipe system, cause now it has no ROM installed at all and I don't want anything to happen in that case. But thanks for the quick reply
Sent from my Nexus 7 using xda app-developers app
tsmith9191 said:
OK. So when switching ROMs I should perform factory restore, wipe all caches, as well as system/wipe to erase the ROM currently installed. I have done it that way before but I always get nervous when I wipe system, cause now it has no ROM installed at all and I don't want anything to happen in that case. But thanks for the quick reply
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
What could happen?? Hardbrick?? A little chance..... Here's what I think when I do something risky. Just Think like I don't have any device if I can get this device back it's bonus for me.
You can always flash a rom whatever it has one or not untill your device can be booted into fastboot. So don't be afraid if something bad(!?) happens and you can boot into fastboot mode. Once I even had no boot just the fastboot it took less than 5 min to get a system on it.
And dirty flash is always an option. I myself had and seen many people having problems with it.
_________________________________________
Don't just say thank, there is a button for thnking.
Clean is always the best! But always make a backup before the wipe process!
Wipe:
/system
/userdata
/.android-secure
/dalvik-cache
/cache
Okay, so I was listening to a YouTube video via Popup Browser BETA. When the song finished, I tried closing the window, but it wouldn't let me interact with the window. Not sure why. I just figured since the app was in beta it was just confused, so I went to the settings->running applications->I force closed the app. But for some reason, the little window still wouldn't go away. So I decided to reboot my device. Bad idea, apparently...
Now whenever I boot up my phone it'll vibrate, display the Google logo for a few seconds, and then... it goes to a blank black screen. Not a clue why. I've tried:
- Leaving it to charge and rebooting
- Leaving it in the blank black screen
- Booting into recovery, then trying to reboot the device from there
- Clearing cache partition
Nothing works. I still can't boot up my phone again.
I'm running Slimbean 4.2.1 (not the latest version). There really isn't anything that might have triggered this. I can still charge my phone (the charging animation still occurs) and I can still go into CWM Recovery. I'd really rather not have to install a new ROM or anything... but if I have to, is there a way to extract the data I have on my phone now while in recovery or something?
Any suggestions?
EDIT: This has been FIXED. Moderators, if you see this, you can close this thread. If anyone else has this problem, try reflashing your current version of your ROM, that's how I fixed mine. I'm not responsible for damage to your device.
Why haven't you tried reflashing your rom without wiping data?
Sent from my iPad 4
mitchdickson said:
Why haven't you tried reflashing your rom without wiping data?
Sent from my iPad 4
Click to expand...
Click to collapse
I could try that.. but isn't there a chance it'll corrupt the data for certain apps or no? I'd just really rather not loose all of that.
Surpass said:
I could try that.. but isn't there a chance it'll corrupt the data for certain apps or no? I'd just really rather not loose all of that.
Click to expand...
Click to collapse
It's not going to hurt anything. Make a CWM backup of your data if you want.
Sent from my iPad 4
Surpass said:
I could try that.. but isn't there a chance it'll corrupt the data for certain apps or no? I'd just really rather not loose all of that.
Click to expand...
Click to collapse
No way of corrupting your data, as long as you don't select to wipe data partition or data is already corrupted. But this is strange that your phone gone crazy like this. Try to reflash your rom without wiping data and see if your phone will boot up
Sent from my Nexus 4 using xda app-developers app
mitchdickson said:
It's not going to hurt anything. Make a CWM backup of your data if you want.
Sent from my iPad 4
Click to expand...
Click to collapse
I've not got enough free space on my phone I don't think (it's only 16GB, I got about 2GB free).
Unless I'm mistaken the backup will take more than that, yes? Considering I've got a few games apps that probably equate to about 4GB.
gallardo5 said:
No way of corrupting your data, as long as you don't select to wipe data partition or data is already corrupted. But this is strange that your phone gone crazy like this. Try to reflash your rom without wiping data and see if your phone will boot up
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Should I reflash with a newer version of the ROM or should I reflash the old one that I'm running?
EDIT: Woops sorry about double post.
Surpass said:
Should I reflash with a newer version of the ROM or should I reflash the old one that I'm running?
EDIT: Woops sorry about double post.
Click to expand...
Click to collapse
Reflash the same version you were running before this accident, as the newest version requires clean flash. If you want to run the latest version and have your data back, reflash the same version you were running before, then backup your data, wipe phone, flash the latest version and restore your data
Sent from my Nexus 4 using xda app-developers app
gallardo5 said:
Reflash the same version you were running before this accident, as the newest version requires clean flash. If you want to run the latest version and have your data back, reflash the same version you were running before, then backup your data, wipe phone, flash the latest version and restore your data
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Okay I'll give that a go, thanks for the help and I'll report back my results. :good:
EDIT: Tried downloading the Zip from their site and now it's saying I've got to log in, but no place to register... grr. I might be a bit longer..
Surpass said:
Okay I'll give that a go, thanks for the help and I'll report back my results. :good:
Click to expand...
Click to collapse
Good luck then and if you will have any problem, just write here and don't forget to quote my post so I will get an email notification
Sent from my Nexus 4 using xda app-developers app
gallardo5 said:
Good luck then and if you will have any problem, just write here and don't forget to quote my post so I will get an email notification
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
WOO! Thanks a lot! Booted up perfectly, and no loss of data or anything like that. Only odd things is it seems to have changed my DPI... but I can change that easily so it's not really a bother. It also made me have to update the Virus Definitions on Avast!, not sure why either.
I shall now proceed to thank all of your posts.
Surpass said:
WOO! Thanks a lot! Booted up perfectly, and no loss of data or anything like that. Only odd things is it seems to have changed my DPI... but I can change that easily so it's not really a bother. It also made me have to update the Virus Definitions on Avast!, not sure why either.
I shall now proceed to thank all of your posts.
Click to expand...
Click to collapse
Great to hear it worked for you now comes the best part, flashing the latest rom
Sent from my Nexus 4 using xda app-developers app
gallardo5 said:
Great to hear it worked for you now comes the best part, flashing the latest rom
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yes either that or perhaps switch to a new one, I've been with semi-stock Android for quite a while now I'm really liking the port of MIUI V5...
Hey, I could really use some guidance here. I'll present the information as simply as I can:
I bought a Galaxy s4 AT&T a few days ago. I've been interested in rooting and flashing different roms, but I think I may have done a bit too much.
I rooted using the motochopper method - great, worked like a charm.
I made a backup of my original rom using CWM. I even took that backup and saved a copy of it on my Mac - perfect.
I thought I'd try Cyanogenmod 10.1, so I downloaded the latest nightly build and flashed it using CWM - so far so good.
Everything was working fine, but my LTE (or any data) was not working at all. I could use Wifi, but once I turned wifi off, I had no data, no gps, no 3g, no 4g, no LTE. I tried the *#*#4636*#*# method, the LTEOnOff app, and changing my APN based on the recommendations provided in this thread - I just couldn't get it to work.
I thought I'd try restoring my original backup, but when I went into CWM to do so, it said that my backup could not be found...(I still have a backup on my computer, just in case)
I needed my phone to work, and badly needed LTE to do so. So, I downloaded this rom: [ROM] CleanROM 1.0 -★| Clean and Smooth! | The Way Nature Intended! |★-
So far, this rom was working fine - it's just a debloated version of TouchWiz - which I like. But, here's my problem now - If my phone reboots, it stays frozen on the Samsung logo (with unlocked lock logo underneath), and I can't get past it. I'd have to go BACK into recovery, and flash the CleanROM all over again, and set my phone up as new with all data wiped.
I really need my phone to work again, and I don't know where to go from here. What options do I have left? What can I do to get out of that frozen Samsung loading screen? Can't I just reset my phone to the way it was? Can't the CM10.1 rom work with LTE?
Your help will be greatly appreciated.
Your best option is to flash the stock MDB firmware via odin . After you get the PASS on Odin go ahead and manually boot into stock recovery and wipe data factory reset again then reboot. You will have to re root and reinstall recovery but this will take care of any issues you had from a bad flash.
http://forum.xda-developers.com/showthread.php?t=2261573
Sent from my GT-I9505G using Tapatalk 2
mavverick said:
Hey, I could really use some guidance here. I'll present the information as simply as I can:
I bought a Galaxy s4 AT&T a few days ago. I've been interested in rooting and flashing different roms, but I think I may have done a bit too much.
I rooted using the motochopper method - great, worked like a charm.
I made a backup of my original rom using CWM. I even took that backup and saved a copy of it on my Mac - perfect.
I thought I'd try Cyanogenmod 10.1, so I downloaded the latest nightly build and flashed it using CWM - so far so good.
Everything was working fine, but my LTE (or any data) was not working at all. I could use Wifi, but once I turned wifi off, I had no data, no gps, no 3g, no 4g, no LTE. I tried the *#*#4636*#*# method, the LTEOnOff app, and changing my APN based on the recommendations provided in this thread - I just couldn't get it to work.
I thought I'd try restoring my original backup, but when I went into CWM to do so, it said that my backup could not be found...(I still have a backup on my computer, just in case)
I needed my phone to work, and badly needed LTE to do so. So, I downloaded this rom: [ROM] CleanROM 1.0 -★| Clean and Smooth! | The Way Nature Intended! |★-
So far, this rom was working fine - it's just a debloated version of TouchWiz - which I like. But, here's my problem now - If my phone reboots, it stays frozen on the Samsung logo (with unlocked lock logo underneath), and I can't get past it. I'd have to go BACK into recovery, and flash the CleanROM all over again, and set my phone up as new with all data wiped.
I really need my phone to work again, and I don't know where to go from here. What options do I have left? What can I do to get out of that frozen Samsung loading screen? Can't I just reset my phone to the way it was? Can't the CM10.1 rom work with LTE?
Your help will be greatly appreciated.
Click to expand...
Click to collapse
Factory Reset
Wipe Cache
Wipe Dalvik
Format /system
Flash ROM or ROM and gapps if AOSP
Reboot
KingKongDingDong said:
Factory Reset
Wipe Cache
Wipe Dalvik
Format /system
Flash ROM or ROM and gapps if AOSP
Reboot
Click to expand...
Click to collapse
Having the same issue so I figured I'd give these steps a shot. Followed them exactly and phone (AT&T S4, TWRP) would won't even reboot the first time into CleanROM. I'm stuck on the Samsung screen with the lock.
edit: I've noticed that now, when I reboot into TWRP, it prompts me for a password. Hitting cancel takes me to the regular home screen, but I had not been getting the password prompt before attempting to install CleanROM. A permissions issue, perhaps?
edit 2:
I've just spent some time trying a bunch of things with bits of good luck surrounded with tons of bad. Below are the steps I've taken to try to get CleanROM to boot (and reboot) without any issues. Hopefully they help figure out the issues we're having.
Wipe Cache
Wipe Dalvik
Wipe /system
Flash CleanROM
Reboot
---- Failed
Reboot into Recovery
Prompted for password, hit cancel
Fix permissions
---- Failed
Reboot to recovery
Prompted for password, hit cancel
Format data (type yes)
Reboot
---- Successfully booted to CleanROM
Ran through phone / account setup
Saw home screen
Powered off and then back on (not using reboot)
---- Failed
Reboot to Recovery
No longer prompted for password
Factory Reset
Attempt to Fix Permissions: failed
Restore default settings
Reboot system
---- Failed
Reboot to Recovery
Prompted for Password, hit cancel
Format Data (type yes)
Reboot System
--- Successfully booted to CleanROM
Ran through phone / account setup
Saw home screen
Reboot (using reboot, not power off / on)
---- Failed
Reboot to Recovery
Prompted for password, hit cancel
Factory Reset: failed
Restore Default settings
Prompted for password, hit cancel
Factory Reset: failed
* Internal Storage showing 0MB (as if it's not reading it correctly)
Fix Permissions
Prompted for password, hit cancel
Nothing has changed, my phone is currently chilling in TWRP
MJHawaii said:
Your best option is to flash the stock MDB firmware via odin . After you get the PASS on Odin go ahead and manually boot into stock recovery and wipe data factory reset again then reboot. You will have to re root and reinstall recovery but this will take care of any issues you had from a bad flash.
http://forum.xda-developers.com/showthread.php?t=2261573
Sent from my GT-I9505G using Tapatalk 2
Click to expand...
Click to collapse
This. You decided to ignore this post for some reason.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
cuffed zhesea
Cataligh said:
This. You decided to ignore this post for some reason.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
I can't speak for OP, but I was hoping there was another way to rectify what has already been done without flashing stock seeing as how I'm on OSX. If that's the only option, then so be it.
Hey. Thanks for the feedback in this thread. I flashed factory through Odin, and everything is working fine. I then factory reset my phone through factory recovery. I'm back to standard touchwiz with all the bloat lol.
I'm going to wait until there a more stable release of cm10.1 - that was a good rom.
Appreciate all the help people!
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Your best bet is do what "cataligh" mentioned... flash back to stock via odin...
Sent from my SAMSUNG-SGH-I337 using xda premium
When you flashed cm10 it probably wipe the internal sdcard, you should ALWAYS do you backups to the extsdcard...period.
TheAxman said:
When you flashed cm10 it probably wipe the internal sdcard, you should ALWAYS do you backups to the extsdcard...period.
Click to expand...
Click to collapse
Yeah, absolutely! I always backed up and flashed roms from my external SD.
mavverick said:
I'm going to wait until there a more stable release of cm10.1 - that was a good rom.
Click to expand...
Click to collapse
waiting is for simpletons. get aokp and transcend...
jaboles said:
I can't speak for OP, but I was hoping there was another way to rectify what has already been done without flashing stock seeing as how I'm on OSX. If that's the only option, then so be it.
Click to expand...
Click to collapse
As I mentioned before starting over is always the Best and Safe way to go. Shortcuts will only cause you headaches and possibly get you a brick that is why you see Odin stock threads. Do yourself a favor and start over I know it sucks but when your modifying your phones its gonna happen once in awhile.
Sent from my GT-I9505G using Tapatalk 2
MJHawaii said:
As I mentioned before starting over is always the Best and Safe way to go. Shortcuts will only cause you headaches and possibly get you a brick that is why you see Odin stock threads. Do yourself a favor and start over I know it sucks but when your modifying your phones its gonna happen once in awhile.
Sent from my GT-I9505G using Tapatalk 2
Click to expand...
Click to collapse
Wise words. Took your advice, installed Windows with boot camp, and got back to stock via odin.
I am going to say something about this thread, we are all giving advice on how to do this and that, and not once is it mentioned anywhere....in the OP
WHAT DEVICE WE ARE TALKING ABOUT! PLEASE STATE THE DEVICE WHEN NEEDING HELP!
The Ax says, I apologize if I missed what device.
TheAxman said:
I am going to say something about this thread, we are all giving advice on how to do this and that, and not once is it mentioned anywhere....in the OP
WHAT DEVICE WE ARE TALKING ABOUT! PLEASE STATE THE DEVICE WHEN NEEDING HELP!
The Ax says, I apologize if I missed what device.
Click to expand...
Click to collapse
My original question was for the AT&T version of the Galaxy S4 - i337.
xBeerdroiDx said:
waiting is for simpletons. get aokp and transcend...
Click to expand...
Click to collapse
Welllllll I just tried installing AOKP as well (Task650). Buttttttt, same issue with the LTE stuff. I tried reviewing all the APN settings, but didnt get any data connection on my phone except for wifi.
mavverick said:
Welllllll I just tried installing AOKP as well (Task650). Buttttttt, same issue with the LTE stuff. I tried reviewing all the APN settings, but didnt get any data connection on my phone except for wifi.
Click to expand...
Click to collapse
What APN settings were you using?
Sent from my SAMSUNG-SGH-I337 using xda premium
doktor buknasty said:
What APN settings were you using?
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
Yeah, data was enabled - and I was using ATT LTE apn settings that I found on these forums. I made sure to use the right now. Plus, when I rebooted my phone, it got stuck on the Samsung lock screen again...
Juuuuust ODINed back to factory right now for the second time :crying:
Was it these settings:
Sent from my SAMSUNG-SGH-I337 using xda premium
doktor buknasty said:
Was it these settings:
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
Yes, those were the exact settings that I used. Is it possible that I could have a defective phone or sim card?
Right now, I am on factory touchwiz with root enabled, and my phone is working perfectly fine. I can reboot, use LTE, everything. The problem starts when I load any CM or AOKP rom...