Well over in the t mobile side of the gs3 we are thinking of different theories...
We think it has to do with the way recovery was installed
If you installed CM9 and lost IMEI did you flash using a cwm recovery installed via Odin or via Adb or terminal emulator
Same question applies to the people who didn't loose IMEI
State your recovery version and also the way you installed and if you lost IMEI or not. Let's get this started!
Sent from my SGH-T999 using Tapatalk 2
I have my imei. I think we should also include date of device release or maybe even serial numbers.
I have a release day blue 16 GB tmo, no problems. I installed cwm via Odin at first, then flashed the newest non-touch cwm using rom manager. Flashed cm10, no problems. Nandroid back, flashed kernels, etc..
Yea your right we should include date
I got mine you can say a week or so after release day, i did flash aokp and didn't loose IMEI, do you think it would be safe to flash cm9 since I didn't loose IMEI when I flashed aokp?
Sent from my SGH-T999 using Tapatalk 2
Just curious does the imei problem only apply to t-mobile and at&t sgs3's?
Odd.. wonder why my last post didn't appear..
Anyway, isn't the hardware revision number listed on a stamp under the battery, along with the imei and whatnot? Would be useful to track hardware batches along with software.
DarkManX4lf said:
Just curious does the imei problem only apply to t-mobile and at&t sgs3's?
Click to expand...
Click to collapse
I really wouldn't know
Sent from my SGH-T999 using Tapatalk 2
I started a thread here, didn't limit it to CM9 and tried to organize via hardware/recovery, and ROM.
http://forum.xda-developers.com/showthread.php?t=1783990
Post if you see fit...
Markdental said:
I started a thread here, didn't limit it to CM9 and tried to organize via hardware/recovery, and ROM.
http://forum.xda-developers.com/showthread.php?t=1783990
Post if you see fit...
Click to expand...
Click to collapse
Thanks glad to see if got something started! Love this community
Sent from my SGH-T999 using Tapatalk 2
IMEI fine here
I flashed cwm using ODIN, then installed Rom Manager and got latest cwm, flashed Sonic Team FreeGS3 Release 1.5, then installed touch recovery from Rom Manager, flashed FreeGS3 release 3, flashed Adama 003 kernel, did a Nandroid backup, flashed CM9, then restored back to FreeGS3 release 3. Of course, not all of this was done immediately after one another. I wiped data/factory reset, wiped cache & dalvik cache 3 times each in between each flash just to be safe. I also did all flashing from recovery and none from Rom Manager. I have a 16GB Tmo Pebble Blue that I picked up from Walmart on release day.
Hopefully we can get to the bottom of this soon, so I can start flashing again worry free!
You guys didnt see this http://forum.xda-developers.com/showthread.php?p=28883417
This thread has been going on for way over a week
Sent from my SAMSUNG-SGH-I747
sTyLeSz said:
Well over in the t mobile side of the gs3 we are thinking of different theories...
We think it has to do with the way recovery was installed
If you installed CM9 and lost IMEI did you flash using a cwm recovery installed via Odin or via Adb or terminal emulator
Same question applies to the people who didn't loose IMEI
State your recovery version and also the way you installed and if you lost IMEI or not. Let's get this started!
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Installed recovery with the QCOM Toolkit with the allinone package root, insecure boot, Busybox...
rebooted to make sure all was good, flashed FireFox release 3.
Installed Touch CWM 5.8.4.5 VIA Terminal rebooted
nandroid
wiped factory reset/cache/system
flashed AOKP then GAPPS and booted
no IMEI or any issues at all... waiting on CM10 to be more stable too flash.
Have you tried to flash cm9 using cwm touch v5.8.4.5 installed via terminal emulator or adb?
Sent from my SGH-T999 using Tapatalk 2
Related
I have no explanation of what has happened to my n7. It shut off by itself and just bootloops when I try to turn back on. I can get into recovery and I have a nandroid backup of a stock rom. Everytime I restore it restores system and then fails?? I flashed 3 different roms and all r flashed successfully but I get the same bootloops . I was using latest twrp and was get error I/o data / speedtest. Something else but I flashed cwm touch b4 I could jot down the errors . I figured it was twrp bug and didnt realize I wouldnt b able to flash back to twrp do to using gooim to write the image in the first place. I am desperate to find out what happened and I wont b near a pc for a few days. I have an unlocked rooted grouper version . I have read and searched b4 posting
Sent from my SGH-M919 using Xparent Skyblue Tapatalk 2
it could be a hardware failure, maybe the mounted drive (emulated sd card) is corrupted and broken? the boot partition seems to be working
It sux cuz I wont have access to a pc for a few days
Sent from my SGH-M919 using Xparent Skyblue Tapatalk 2
have you tried clearing the whole of /system /data /cache... everything except /sdcard then flash a new rom? maybe that'll clear some things up
Billchen0014 said:
have you tried clearing the whole of /system /data /cache... everything except /sdcard then flash a new rom? maybe that'll clear some things up
Click to expand...
Click to collapse
Yes I wiped system /cache/dalvik/ and factory reset I did them all like 5 times each and flashed a brand new rom. Its so weird
Nothing works. I am always prepared for atuff like this with multiple nandroids cwm/twrp but they both fail to restore
Sent from my SGH-M919 using Xparent Skyblue Tapatalk 2
Back in a few months ago I'm faced with that problem once, tried everything like factory reset, format system/data/cache/sd, install new ROM and also tried to restore by nandroid backup (that used to work fine before that problem occur) but non of these solutions work.
Finally I've to use fastboot to flash it to 4.1.2 (to format and re-partition the device) and flash it back to 4.2.2 and then it work fine again even with many custom rom and kernel installed to my N7 very frequent and today it still work just fine.
why always me said:
Back in a few months ago I'm faced with that problem once, tried everything like factory reset, format system/data/cache/sd, install new ROM and also tried to restore by nandroid backup (that used to work fine before that problem occur) but non of these solutions work.
Finally I've to use fastboot to flash it to 4.1.2 (to format and re-partition the device) and flash it back to 4.2.2 and then it work fine again even with many custom rom and kernel installed to my N7 very frequent and today it still work just fine.
Click to expand...
Click to collapse
Thanks that is what im gonna have to do
Sent from my SGH-M919 using Xparent Skyblue Tapatalk 2
Thanks for the advice i got my pc back today and used wugs toolkit to flash factory image and it booted up thank god .
Sent from my Nexus 7 using Tapatalk 4 Beta
bbobarino said:
Thanks for the advice i got my pc back today and used wugs toolkit to flash factory image and it booted up thank god .
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
In the future, I'd refrain from flashing if you didn't have a computer on hand.
Sent from my Nexus 7 using XDA Premium HD app
peneoark said:
In the future, I'd refrain from flashing if you didn't have a computer on hand.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I couldnt agree more but thats the weird thing I didnt even flash anything for like a week b4 this happened thats why it was so bizzare to me. Still cant explain why it did that
Sent from my SGH-M919 using Tapatalk 4 Beta
bbobarino said:
I couldnt agree more but thats the weird thing I didnt even flash anything for like a week b4 this happened thats why it was so bizzare to me. Still cant explain why it did that
Sent from my SGH-M919 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Electronics can be wacky sometimes
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...
Has anyone tried the 4.3 cm10.2 ROMs found over here (http://androidhosting.org/Devs/Dhacker29/cm-10.2/)? I was going to give it a go last night but for some reason my device got stuck on the "warning your boot loader is unlocked" screen and had to use Matt's utility to give it life... I may give it a try tonight when I'm not expecting any calls...
Sent from my XT907 using xda app-developers app
Yeah, I'm running the latest version of it now. I had the same problem. What worked for me was the following:
1. Wipe everything - system, data and both types of cache.
2. Install CM 10.2 and NOTHING else. Boot the ROM. It should go through now.
3. Once you get to the main screen, reboot into recovery.
4. Install the 4.3 GAPPS version. Reboot, get to the main screen and reboot into recovery.
5. Now flash the 4.3 version of Supersu for CM 10.2
6. Boot one last time into CM 10.2
All the links for everything you need can be found with a Google search. Later I may edit this post to include those links.
Sent from my XT907 using Tapatalk 4
Thank you kindly for the reply... I got it booting finally but couldn't get su permission on TiB and what not... I didn't know about needing the 4.3 su ...I'll flash that now... again thank you kindly
Sent from my XT907 using xda app-developers app
TWRP isn't supported either from what I understand. You need to run CWM.
Any time I install 4.3, it won't reboot. It starts up initially, but I can't get it to get past the Motorola logo upon second boot.
I have tried the normal install method and this method.
Then recovery doesn't see the /data folder so something is wrong with the 4.3 install I presume.
Does it change the location of data?
Yeah I Tried It But It Had No Sound So I Changed Over To 4.2.2 AOKP.
grtechguy said:
TWRP isn't supported either from what I understand. You need to run CWM.
Click to expand...
Click to collapse
I was using CWM on my first attempt... this time around I switched to TWRP...
Sent from my XT907 using xda app-developers app
grtechguy said:
TWRP isn't supported either from what I understand. You need to run CWM.
Click to expand...
Click to collapse
I use TWRP, works ok. Got sound, data, everything working fine. Battery life sucks, but no surprise there.
My 2c
I'm running it right now. I must have missed the part about flashing SuperSu, because I can't do anything as root. I had trouble the first time I flashed with the phone bootlooping, but I flashed again and that fixed it. Battery life is somewhat poor, but I just found the performance page today (Icon was different, silly me!) so we'll see how it goes with a different governor. I've been having issues with Navigation and Bluetooth audio on anything except stock. Bluetooth audio locks the phone and I have to soft-reset it. Navigation crashes if you try to multi-task while using it.
Hi, I was hoping to get some help and insight with the situation I've been dealing with. I'll give as much information as possible so that someone might be able to point me in the right direction.
I have an att galaxy s4 that was purchased and rooted before the mf3 ota that made everything so difficult. I've flashed several roms and decided to go with liquidsmooth 2.37 atm and I'm experiencing a few odd issues (stock mss not working) that no one else seems to have, but for the most part it's running very well. Lately I've wanted to go with a rom using the new 4.4 and I've tried a handful no matter what rom I try I have the same issues. so far I've tried CM 11, Omnirom and Gummy. With all of them everything runs very laggy and glitchy and will frequently freeze until it crashes and reboots. Every single time I've used whatever gapps are linked in the op for every rom and followed flashing instructions to the letter (wipe data/factory reset, wipe cache, wipe dalvik, flash rom , flash gapps, flash super su (if needed) and reboot) and I've even tried different recoveries (both cwm recovery 6.0.4.4 and the latest philz cwm recovery) same results every time. This part shouldn't matter, but I tried flashing these roms while on the original mdl modem and after upgrading to mj9. Let me know any other info you need, but I've tried to be thorough. I appreciate the help.
So what firmware are you on right now?
scott14719 said:
So what firmware are you on right now?
Click to expand...
Click to collapse
I'm guessing mdb
sorry thought i mentioned the firmware is mdl
Rockman195 said:
sorry thought i mentioned the firmware is mdl
Click to expand...
Click to collapse
Looks like you're doing everything right. Have you checked md5's of your downloads?
I don't know how to do that or else I would
Sent from my SGH-I337 using xda app-developers app
Rockman195 said:
I don't know how to do that or else I would
Sent from my SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
http://onlinemd5.com/
Thanks for the link. I'm looking into md5 checking and I downloaded the hash droid app. My only question is when I calculate the md5 of a file what am I supposed to compare it to?
Sent from my SGH-I337 using xda app-developers app
Rockman195 said:
Thanks for the link. I'm looking into md5 checking and I downloaded the hash droid app. My only question is when I calculate the md5 of a file what am I supposed to compare it to?
Sent from my SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
You should compare it to the md5 typically posted where you download the file from
Ok so the dl site like devhost or whatever
Sent from my SGH-I337 using xda app-developers app
Rockman195 said:
Ok so the dl site like devhost or whatever
Sent from my SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Correct. I usually just compare the last 5 or 6 characters. If they match it's very unlikely the others won't too.
tried going back and looking in all the threads that I downloaded roms from, can't find md5s for any of them with one exception and thats an outdated version of a rom I'm not currently trying to flash, so I don't see the point in downloading it just to compare the md5
Downloaded an omnirom build and checked the md5 and everything was good, plus I would be surprised if the md5s were bad on all the roms I've tried. Any other suggestions? Should I try two recovery instead of coming?
Sent from my SGH-I337 using xda app-developers app
Rockman195 said:
Downloaded an omnirom build and checked the md5 and everything was good, plus I would be surprised if the md5s were bad on all the roms I've tried. Any other suggestions? Should I try two recovery instead of coming?
Sent from my SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
I'm running out of ideas try twrp recovery. Here is a zip you can flash in your current recovery http://forum.xda-developers.com/showthread.php?p=45511518
flashed twrp and that royally screwed up the phone. opened recovery using twrp and made a back up then did a system wipe and went to install the rom and when I went to do that, the list of all teh files you have to choose from was blank. I could go through different folder levels but the part where it shows the contents was always emtpy. Sometimes I could touch the area and see I portion highlight like it was making a selection but it wouldnt do anything and there was no file name there. Went to restore the backup I made and there was nothing in the list of backups to restore from. Rebooted the phone and liquid smooth 2.37 loaded like a clean flash with none of my info, files, apps, etc so I downloaded rom manger from the playstore and put the latest cwm touch on there. When I went in recovery none of my cwm backups where there or anything so i went to reboot and it only shows the samsung boot screen. Downloaded a few different roms and gapps on my sd card from y computer and put them on the phone and flashed the roms and gapps and still can't get past the boot screen. I'm really open to suggestions on this one.
If it was me, at this point I'd Odin the stock mdl firmware and start all over again. Something's not right with your phone. But it scares me a little since things aren't flashing correctly and there could be something wrong with your internal memory. If memory is bad it could make things worse.
I think your right. Do you know where I can find the stock firmware and instructions for flashing it? I haven't used Odin in a while.
Sent from my GT-N8013 using xda app-developers app
Rockman195 said:
I think your right. Do you know where I can find the stock firmware and instructions for flashing it? I haven't used Odin in a while.
Sent from my GT-N8013 using xda app-developers app
Click to expand...
Click to collapse
You can get the stock firmware at sammobile.com. it's free but you have to register. You'll download a zip file. Use 7-zip to extract the .tar.md5 file from it and use that in Odin, PDA slot. This is a guide that is not for the s4 but the procedure is the same. It has screen shots in it that help. Don't use any files in it though other than odin. Good luck. http://forum.xda-developers.com/showthread.php?p=26056924
I haven't read the whole thread, so hopefully these haven't already been covered.
1) Make sure your recovery supports 4.4. Not all of them do. Stay the heck away from TWRP because it's done nothing but suck for Galaxy S4, while it was absolute king for the S3. The wrong recovery can still flash a ROM but that ROM may not work very well.
2) Ensure you do a COMPLETE wipe. As in wipe /system and /data. Make sure your internal SD card is formatted. 4.4 may not use some things & folders that 4.2 and 4.3 did, which might cause problems.
3) If you have an external SD, then make sure 4.4 is using the right path for it to access any important files you may have on it, like apps2sd & such.
Well since screwing things up with twrp I'm back to having a working phone again. I didn't have to use Odin but I still might just to go back to stock and then try kit kat. I went into cwm recovery and formatted the system then flashed liquidsmooth 2.37 which is what I was running. Everything works fine with that except when I use the rom manager widget to boot into recovery, it goes to the boot screen with booting recovery at the top but doesn't go further. I have to use the 3 button method to get into recovery. The other odd thing is that mms works for me now.
I tried flashing gummy 4.4 again since everything is fine in jb but I still have the same jittery twitchiness. One thing I noticed is that when I go into the performance settings in 4.4 the current cpu reading will jump from 300 mhz to 1200 to 400 to 1800 etc just at idle. Is that normal. My note 10.1 holds steady when it's just sitting there.
To answer your questions, I'm using cwm 6.0.4.4 which is kit kat approved and I formatted and wiped everything before flashing and it didn't change anything. I appreciate your help so far and look forward to more insight.
Sent from my SGH-I337 using xda app-developers app
Hello Guys,
im facing a problem with my i9505,
I've been using Liquidsmooth Rom for some time,
and yesterday i flashed some roms, and now my sim card isn't recognized anymore, aswell my IMEI and Baseband are missing.
I've had that problem before, so flashed stock rom and restored a TWRP Backup containing only my EFS folder.
This has solved my problems in the past, but now nothing happens.
I have a TWRP backup aswell as a copy of the EFS folder.
Has someone else faced the same problem or knows how to fix it?
Thanks in advance.
No one?
Try to restore efs folder manually with root explorer
Sent from my GT-I9500 using XDA Free mobile app
I'm trying right now, but I am confused because the restore with TWRP doesn't do anything to my EFS folder.
Ok, I copied the EFS folder from my microsd back to the phone but nothing changed :crying:
Have you tried flashing back to stock with Odin? I've heard that can sort out IMEI problems and the sorts.
Even if it doesn't it gives you a clean phone to work with, so you can eliminate any rom problems.
I flashed the stock rom, as well as different modems trough odin, but nothing changed. But I'm wondering why the TWRP restore doesn't show any result.
Sent from my Nexus 7 using Tapatalk
I hope you can recover your phone!
Sent from my GT-I9505 using XDA Free mobile app
kingstark666 said:
I hope you can recover your phone!
Sent from my GT-I9505 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks Mate, I'm still trying. If not, I found a service to repair it for 25 Euros but I hope I will be able to do it myself.
Try to Download another stock rom and before flashing it do a full wipe, including formatting data and cache. Something similar happened to me a few days ago. I've flashed a russian rom and problem solved, but I have the i9500 model.
Sent from my GT-I9500 using XDA Free mobile app
I flashed a 4 Part Rom with full wipe already, but nothing changed.
Sent from my Nexus 7 using Tapatalk
K40S said:
I flashed a 4 Part Rom with full wipe already, but nothing changed.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Not sure if this will work, of it you've tried it already, but have you tried a different version of TWRP?
I did actually, but I'm going to try a older version too and see if it works.
Sent from my Nexus 7 using Tapatalk
Ok, tried restoring with TWRP 2.500 and it shows me failed, contrary to TWRP 2.7.
With TWRP until 2.6.3 it shows me failed, 2.63 and 2.7 show me a succesful message.
LOL it just started working again without me doing anything :highfive::laugh: