Related
I flashed to cm-10.1-20130403-NIGHTLY-d2spr and everything was working fine. I was able to make phone calls, apps worked, no errors etc. I was using Titanium backup to bring back some of the apps and accidently chose one of my batch restores that had system data in it. I noticed it shortly into the backup and stopped it. It caused some media process errors and I thought I would just clear cache etc and reflash with the ROM again.
The rom loaded and now it tells me to activate my phone. I hit activate and obviously its not activating my phone. I don't have a restore in nandroid or in titanium based on this rom I can use. My last titanium backup was from the rooted jelly bean 4.1.2. This version of 10.1 is android 4.2.2. I have googled and read for hours but not 100% sure what to do. If I go into the Status of the Phone within CyanogenMod 10.1 I can see that it says mobile network disconnected, my phone number 000-000-4327,
I can connect to the apps and wifi but can't get to the mobile network.
What are my options?
Do I unroot and reload stock ROM from sprint? Then call an activate and reset counter?
Do I try this http://forum.xda-developers.com/showthread.php?p=25470797?
Do I call sprint and try a manual activation?
Can I got to another ROM and get cell service back?
First, remove all the #s in your post but prl. Could cause you problems with people stealing your info. Second, reflash your rom and see if that fixes it, if not, flash a stock rom and force reactivation through the dialer (there's a ## code to do it)
Thanks
CNexus said:
First, remove all the #s in your post but prl. Could cause you problems with people stealing your info. Second, reflash your rom and see if that fixes it, if not, flash a stock rom and force reactivation through the dialer (there's a ## code to do it)
Click to expand...
Click to collapse
Thanks for your help. Can I flash the stock rom with still being rooted? or Do I need to unroot and then reflash?
turboenterprise said:
Thanks for your help. Can I flash the stock rom with still being rooted? or Do I need to unroot and then reflash?
Click to expand...
Click to collapse
Go to freezas thread and download the "mb1 stock rooted" rom. Then flash it and see if you have mobile, if not look up the ## code to reactivate (you need to be on wifi though)
I've had this and solved
Posted steps, will find link. Meanwhile you will need msl and stock or tw ROM.
Give me a few and I'll find link.
http://forum.xda-developers.com/showthread.php?p=38122125#post38122125
You will have to contact sprint if you dont have your msl, and min.
Shouldnt give you any issues, i even admitted i had screwed it up.
Thanks
There are quite a few threads. Sorry I need a little hand holding. Don't want to do the wrong one. Then I just move the zip to the phone in the sdcard. Boot into CWM then install zip and restart?
http://forum.xda-developers.com/showthread.php?t=1743923
[ROM]9/20/12 LI3 Sprint Samsung Galaxy S 3 OTA (Stock/ROOTED/Odex/DeOdex/Firmware!
http://forum.xda-developers.com/showthread.php?t=1910947 -
[ROM|Stock Rooted] 3/3/13 Sprint Touchwiz Jelly Bean 4.1.2 (L710VPBMB1) Odex/DeOdex
http://forum.xda-developers.com/showthread.php?t=1745865
[ROM|MB1]3/7/13 Galaxy S fre3 2.41 (HybridOdex/Speed/+BatteryLife/Tweaks/Options
THis ONE?
Download (full ROM):
Galaxy S fre3 2.41 | Mirror
Galaxy S fre3 2.41 MD5: EB682E234137F2B8EAC763DE7EE15342
I used the middle one you posted. Just put on SD and flash.
The one that says "firmware" is not a rom, its the radio/modem for that build. You can flash any of the others, if it ever has "odex" or "deodex" on it, then its a rom
CNexus said:
The one that says "firmware" is not a rom, its the radio/modem for that build. You can flash any of the others, if it ever has "odex" or "deodex" on it, then its a rom
Click to expand...
Click to collapse
All right, I will try to flash this one:
Filename: MB1_update_FULL_Odex.zip
MD5sum: a89894f653099d158c8c459f2b7f656e
turboenterprise said:
All right, I will try to flash this one:
Filename: MB1_update_FULL_Odex.zip
MD5sum: a89894f653099d158c8c459f2b7f656e
Click to expand...
Click to collapse
Yup, that's fine, try the steps listed in the thread linked above
Also, you don't need to call sprint to get your msl, there's a guide in the General subforum for how to get it if you'd rather them not know what you're doing with your phone
EDIT
Here's how to activate (you have to be on wifi)
jazz995756 said:
Be sure your on a touch wiz ROM and do hands free activation. To do that simply dial ##72786# and wait for your phone to reboot. Upon boot unlock your screen and DONT touch your phone it will do an activation and do your latest prl and profile and your phone will reboot again. Let it finish booting and unlock your phone again and wait for a screen to say activation has been successfull and that should fix it.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
My 10+ hour ordeal is over. Thank you so much for your help. I flashed the one I mentioned above and I followed the normal setup and restored the PRL etc and I can make phone calls... It is just so hard to find information with all the different carriers,different versions, different ROMS, etc... Much appreciated. Didn't have to call sprint or anything.
Now I got to figure out how to get rid of the 5 - 0 folders Cyanogenmod created with all the same stuff on the internal card
So, first off, just wanna say that I have a RIDICULOUS amount of experience with flashing roms. Literally over 100 different devices and 1000s of different flashes of my own devices on top of it. Quite familiar with this S2 as well and have customized them to all sorts of extents, but this one has me baffled. This phone refuses to run 4.2.2/4.3/4.4.x roms. Using the most up to date radio and the suggested TWRP (2.6.1.0) as well as CWM 6.0.44 and the newer TWRP: 2.6.3.0. Every time the phone will get to the set up screen, refreeze and boot. No issues running stock or stock based 4.1.2 roms. I've tried changing recoveries, wiping everything (/system, /data, /caches) repeatedly, Odin back to stock and redoing everything, switching kernels, wiping caches before rebooting and leaving it be, changing batteries, etc but nothing has worked. So far I've tried BlackLiquid 2.92 (4.2.2 stable), Awesome Audio rom (4.3), official CM11 (whatever the last build up was last night), and BeanStalk 4.4.2 (12/16) and all behave exactly the same - freeze on start up and reboot. This doesn't seem to be much of a widespread issue obviously, so just baffled and getting a bit frustrated as this should have been a 20 minute process that has turned into a few hours already. Since USB Debugging isn't on by default on newer roms, how would I even do a logcat to see if there is anything meaningful there? Any ideas?
Update: I have another S2. Performed same steps, same TWRP, same radio and rom, on same external SD card and that one booted right up like normal confirming that it is the phone itself, but what causes that?? Corrupted partitions?
I have the same problem, just format your internal and external sd card with just ROM file on your storage then try to install, than please inform me
Sent from my SGH-T989 using XDA Premium 4 mobile app
iamdofus said:
I have the same problem, just format your internal and external sd card with just ROM file on your storage then try to install, than please inform me
Sent from my SGH-T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Nope. No luck there (only tried Beanstalk so far, but exact same issue). Thanks for the suggestion though! Only using internal storage, no SD card, though thinking I might try that next...
Edit: Just to be thorough, I formatted internal storage via TWRP and my computer then readded the files and just tried to boot rom only and freezes before I can do anything.
Do you by chance have a refurbished s2?
The screen has been replaced by a friend of mine and he managed to mess up the soft keys with it, but everything else functions. That's actually why he sent it to me, so I could hook him up with Pie and all that kind of thing so the soft keys aren't an issue. What's your thoughts on the refurb side of it?
es0tericcha0s said:
The screen has been replaced by a friend of mine and he managed to mess up the soft keys with it, but everything else functions. That's actually why he sent it to me, so I could hook him up with Pie and all that kind of thing so the soft keys aren't an issue. What's your thoughts on the refurb side of it?
Click to expand...
Click to collapse
OK thanks for reply, I have one more solution give me. Some time I will give try that it worked for me.
Sent from my SGH-T989 using XDA Premium 4 mobile app
es0tericcha0s said:
Nope. No luck there (only tried Beanstalk so far, but exact same issue). Thanks for the suggestion though! Only using internal storage, no SD card, though thinking I might try that next...
Edit: Just to be thorough, I formatted internal storage via TWRP and my computer then readded the files and just tried to boot rom only and freezes before I can do anything.
Click to expand...
Click to collapse
ok lets stat it with this
1) download both the scripts of infamous wipe cache and infamous super wipe.
2) format your both SD card with PC (FAT32)
2) put both these wipe files and and your rom file ( i prefer try slimbean rom first)
3) Now in twrp 2.6.0.0- follow the steps
i) format your phone with twrp options
ii) again format your phone with infamous super file. (by going in to INSTALL ZIP file option in TWRP)
iii) than format with infamouse cache file (by going in to INSTALL ZIP file option in TWRP)
iv) install your rom and compatiable GAPPS zip file.
v) after installing or somewhere between procedure if twrp says something about supersu birnaries are not correct than click on DO . NOT FIX
vi) again format infamouse cache wipe.
vii) now FINALLY reboot the rom.
it should work, and it worked for me. if u sucessfully run the rom than you can eailsy run all the AOSP roms in this forum. Again If you try this please do tell me what happend.
Followed to a "T" and still in the same boat - freezes after bootup. I used those same steps before with another darkside wipe script (maybe older?) but yea, have already been down that road. I did downgrade to 2.6.0.0 and used Slim 4.3 because 4.4 is supposed to use the newer TWRP, just to be certain, but GRRR. I guess we're just gonna have to settle for a 4.1.2 rom and call it a day. :/
So here are the log output from the wipes:
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.SUPER.WIPE_recovery.log
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.CACHE.WIPE_recovery.log
I see some stuff at the bottom of those that might indicate something weird, but I am not adept at interpreting these, so just wondering if someone could point me to the right direction about the repair checks and what not listed on these. Thanks!
Edit 2: I did get a AOSP based 4.1.2 rom to boot with no problems! wtf... LoL
Last Edit:
Problem solved! I used basically the same steps I had been doing but once the AOSP 4.1.2 rom booted then now everything works like it should again. Have loaded a 4.3 and 4.4 rom successfully. Thanks for the help!
es0tericcha0s said:
So, first off, just wanna say that I have a RIDICULOUS amount of experience with flashing roms. Literally over 100 different devices and 1000s of different flashes of my own devices on top of it. Quite familiar with this S2 as well and have customized them to all sorts of extents, but this one has me baffled. This phone refuses to run 4.2.2/4.3/4.4.x roms. Using the most up to date radio and the suggested TWRP (2.6.1.0) as well as CWM 6.0.44 and the newer TWRP: 2.6.3.0. Every time the phone will get to the set up screen, refreeze and boot. No issues running stock or stock based 4.1.2 roms. I've tried changing recoveries, wiping everything (/system, /data, /caches) repeatedly, Odin back to stock and redoing everything, switching kernels, wiping caches before rebooting and leaving it be, changing batteries, etc but nothing has worked. So far I've tried BlackLiquid 2.92 (4.2.2 stable), Awesome Audio rom (4.3), official CM11 (whatever the last build up was last night), and BeanStalk 4.4.2 (12/16) and all behave exactly the same - freeze on start up and reboot. This doesn't seem to be much of a widespread issue obviously, so just baffled and getting a bit frustrated as this should have been a 20 minute process that has turned into a few hours already. Since USB Debugging isn't on by default on newer roms, how would I even do a logcat to see if there is anything meaningful there? Any ideas?
Update: I have another S2. Performed same steps, same TWRP, same radio and rom, on same external SD card and that one booted right up like normal confirming that it is the phone itself, but what causes that?? Corrupted partitions?
Click to expand...
Click to collapse
Interesting, so you're saying it's phone specific?
That begs to ask other questions now:
1. Where did this phone come from? is it a Tmobile version (SGH-T989) or AT&T (i-1900)?
2. You mentioned you got it from a friend; did it come rooted? unlocked? Or did you have to do that process yourself?
UltimaniumX said:
Interesting, so you're saying it's phone specific?
That begs to ask other questions now:
1. Where did this phone come from? is it a Tmobile version (SGH-T989) or AT&T (i-1900)?
2. You mentioned you got it from a friend; did it come rooted? unlocked? Or did you have to do that process yourself?
Click to expand...
Click to collapse
Yep, very much phone specific. Used same recovery, same rom zip and gapps off the same external SD card, to be certain. That one updated just like every other S2 I've done. And it's the Tmo version. The At&t models are i777 S2 or i727 S2 Skyrocket. The i9100 is international and has a physical home button. But the phone was not modified at all. No root, custom recovery, etc. I was only able to resolve it by first starting with an AOSP 4.1.2 rom and working my way up to 4.4. One of the weirder issues I've come across.
es0tericcha0s said:
Followed to a "T" and still in the same boat - freezes after bootup. I used those same steps before with another darkside wipe script (maybe older?) but yea, have already been down that road. I did downgrade to 2.6.0.0 and used Slim 4.3 because 4.4 is supposed to use the newer TWRP, just to be certain, but GRRR. I guess we're just gonna have to settle for a 4.1.2 rom and call it a day. :/
So here are the log output from the wipes:
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.SUPER.WIPE_recovery.log
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.CACHE.WIPE_recovery.log
I see some stuff at the bottom of those that might indicate something weird, but I am not adept at interpreting these, so just wondering if someone could point me to the right direction about the repair checks and what not listed on these. Thanks!
Edit 2: I did get a AOSP based 4.1.2 rom to boot with no problems! wtf... LoL
Last Edit:
Problem solved! I used basically the same steps I had been doing but once the AOSP 4.1.2 rom booted then now everything works like it should again. Have loaded a 4.3 and 4.4 rom successfully. Thanks for the help!
Click to expand...
Click to collapse
What did you exactly do? I flashed a 4.1.2 and then flashed a 4.3 based ROM and it didn't work. What recovery version did you use to flash the 4.3 ROM?
tpag02 said:
What did you exactly do? I flashed a 4.1.2 and then flashed a 4.3 based ROM and it didn't work. What recovery version did you use to flash the 4.3 ROM?
Click to expand...
Click to collapse
Sorry, I don't pay attention to the notifications on XDA very often. I don't usually browse the S2 forums unless needed because I have an N5, but anyway... The 4.1.2 rom you used, was it TW or AOSP type? I used 2.6.0 to wipe everything, then used cache and superwipe zips then 4.1.2 AOSP type rom then cache wipe zip again then after that booted, I was able to go back to 2.6.1 and flash a 4.3 via wiping, wipe zips, installing rom then cache wipe again. After that, repeated with a KK rom and now it loads roms just like it should. If you want more precise help, feel free to hit me up on Hangouts with my username: es0tericcha0s. Good luck! I know how frustrating it can be when it gets a little out of whack like this...
I'm in the same boat
Same here. I just bought a galaxy s2 from my friend (tmobile version) and I too get stuck in a bootloop no matter what rom I use. It boots up freezes then reboots 7 keeps doing that endelessly. I've even wiped using twrp & darkside then reflashed the stock rom in odin, but no luck. strangely it only happens on the cellular network, otherwise it works fine on wifi. But when I turn off the wifi and go to the cellular network I can't even turn on the wifi anymore and still stuck in this boot loop It's wierd and frustrating.
DennyTek said:
Same here. I just bought a galaxy s2 from my friend (tmobile version) and I too get stuck in a bootloop no matter what rom I use. It boots up freezes then reboots 7 keeps doing that endelessly. I've even wiped using twrp & darkside then reflashed the stock rom in odin, but no luck. strangely it only happens on the cellular network, otherwise it works fine on wifi. But when I turn off the wifi and go to the cellular network I can't even turn on the wifi anymore and still stuck in this boot loop It's wierd and frustrating.
Click to expand...
Click to collapse
Hmm. That's interesting... This is happening on the stock rom - where you turn on cellular data and it reboots? Definitely a different issue than the one I was having. Which stock rom were you flashing via Odin? Have you tried other versions of the stock rom and had the same problem?
TMO 4.1.2
es0tericcha0s said:
Hmm. That's interesting... This is happening on the stock rom - where you turn on cellular data and it reboots? Definitely a different issue than the one I was having. Which stock rom were you flashing via Odin? Have you tried other versions of the stock rom and had the same problem?
Click to expand...
Click to collapse
This was happening on any rom I used (Cm 10.2 stable, Cm 11 nightly, AOKP & Super Nexus 3.0 which is Android 4.3) I can't really speak for the stock rom (tmo 4.1.2) since I've never used it for more that 5 minutes, sigh but I'll try it and see if it gives me the same problem :/
Are you guys flashing gapps if the ROM you're installing doesn't have it?
Sent from my SGH-T989 using Tapatalk
yep
wikitiki said:
Are you guys flashing gapps if the ROM you're installing doesn't have it?
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
ya, well at least I am anyways
wikitiki said:
Are you guys flashing gapps if the ROM you're installing doesn't have it?
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
I had tried with and without and did not make any difference.
DennyTek said:
This was happening on any rom I used (Cm 10.2 stable, Cm 11 nightly, AOKP & Super Nexus 3.0 which is Android 4.3) I can't really speak for the stock rom (tmo 4.1.2) since I've never used it for more that 5 minutes, sigh but I'll try it and see if it gives me the same problem :/
Click to expand...
Click to collapse
I just started working on a VZW S3 on T-Mobile service that has this issue. Happens on stock VZW 4.1.2, stock T-Mobile 4.1.2 rom, custom 4.1.2 T-Mobile rom, and stable CM 10.2. Weirdest thing... full wipes including /system inbetween each flash. Changed the modem too. Nothing helps. Pretty sure it's a bad board at this stage.
Cool beans, 0! Having this exact problem, will try your method for my s2, btw which aosp 4.1.2 did u use? Can I get a link? Thanks been having the problem for a few months now and just gave up haha, been super thirsty for that beanstalk kk build
One last thing can u also provide a link to the 4.3 that u used? I really want it to work and want to follow what u did to the , megabyte
Wow, what a ride I had with this phone.
Starting with the fact that the model of the phone was SGH-I747 with AT&T branding I then tried to flash a custom ROM for this model, of course everything went bad, we'll not everything, but I couldn't make any calls, see IMEI nubmer and so on.
Thanks to a very helping member of SGH-I747 board, audit13, I found out that my phone is in fact T-Mobile's SHG-T999. I was lucky enough and was able to restore stock ROM of this model.
Now everything works, but since I'm located in Europe I would like to flash stock ROM without all the T-Mobile useless (since I don't have this carrier in my country) apps.
I found this ROM, which seems to be the one best used to get as close to stock android as possible - http://forum.xda-developers.com/showthread.php?t=2501303
And I just wanted to make sure that I don't miss anything important.
Phone Data
Model: SGH-T999
Bootloader version: T999UVUENC2
Android Version: 4.3
I've rooted the phone using this guide - http://forum.xda-developers.com/showthread.php?t=1771687 and using March 2014 - 4.3 JellyBean.
Could someone please explain difference between -StockMOD Custom ROM- and -StockMOD ROM-? I understand that -StockMOD ROM- is completely based on Stock ROM, little to no changes. But how little are these changes, will I have all the T-Mobile apps?
Steps I'm planning to make
1. Backing up efs folder by copying it with Root Browser to SD card and then on my PC.
2. Installing Clockwork MOD and Flashing ClockworkMod Recovery option
3. Creating backup of current ROM with ClockworkMod
4. Downloading StockMOD Custom ROM 4.3 RLS2.1.zip from the thread mentioned above (I'm a bit worried that file name in the thread is different - StockMOD Custom ROM T999 4.3 RLS2.1.zip)
5. Unfortunately I don't see link to T999UVUEMJC modem anywhere.
6. Copying of ROM file and Modem file to SD card (Is it ok if my SD card is only 2GB? ROM is a bit over 1GB).
7. Rebooting into recovery from ClockworkMod
8. Selecting Wipe data/factory reset
9. Selecting Wipe Cache partition
10. Going to advanced and selecting Wipe davlink cache
11. Selecting Mounts and Storage and format /system
12. Installing modem zip (If I can find it)
13. Installing StockMOD Custom ROM 4.3 RLS2.1.zip (is it ok to have spaces in file name?)
14. Praying to God everythings works
You could follow this thread to backup your efs folder: http://forum.xda-developers.com/showthread.php?t=1804117
I suggest flashing CWM directly from Odin in download mode. I would not install it using an App from the play store. This is just my personal preference.
All of the other steps look fine.
viltnieks said:
....Now everything works, but since I'm located in Europe I would like to flash stock ROM without all the T-Mobile useless (since I don't have this carrier in my country) apps.
I found this ROM, which seems to be the one best used to get as close to stock android as possible - http://forum.xda-developers.com/showthread.php?t=2501303
....
Could someone please explain difference between -StockMOD Custom ROM- and -StockMOD ROM-? I understand that -StockMOD ROM- is completely based on Stock ROM, little to no changes. But how little are these changes, will I have all the T-Mobile apps?
Click to expand...
Click to collapse
StockMOD Custom has much (if not all) of the carrier branding removed. It has added some customization tweaks to the ROM; mainly XPosed App and Wanam XPosed Module. It also has a few other custom apps and features from newer Galaxy devices replacing the stock apps. It is themed to look like a Galaxy S5 instead of an S3.
The StockMOD ROM has very little removed; KNOX, Syscope, CarrierIQ, and maybe something else. Other than that it will look almost identical to what you now have, including all of the T-Mobile stuff. This one would match the filename in the thread title. It was created first and the StockMOD Custom was added to the thread afterwards, is my guess.
Steps I'm planning to make
1. Backing up efs folder by copying it with Root Browser to SD card and then on my PC.
2. Installing Clockwork MOD and Flashing ClockworkMod Recovery option
3. Creating backup of current ROM with ClockworkMod
4. Downloading StockMOD Custom ROM 4.3 RLS2.1.zip from the thread mentioned above (I'm a bit worried that file name in the thread is different - StockMOD Custom ROM T999 4.3 RLS2.1.zip)
5. Unfortunately I don't see link to T999UVUEMJC modem anywhere.
6. Copying of ROM file and Modem file to SD card (Is it ok if my SD card is only 2GB? ROM is a bit over 1GB).
7. Rebooting into recovery from ClockworkMod
8. Selecting Wipe data/factory reset
9. Selecting Wipe Cache partition
10. Going to advanced and selecting Wipe davlink cache
11. Selecting Mounts and Storage and format /system
12. Installing modem zip (If I can find it)
13. Installing StockMOD Custom ROM 4.3 RLS2.1.zip (is it ok to have spaces in file name?)
14. Praying to God everythings works
Click to expand...
Click to collapse
I would also suggest this post for backing up imei and other nvdata. Specifically the reboot nvbackup instructions.
Since you are on NC2 bootloader and modem(baseband) do not mess with changing your modem to MJC (step 12). You can confirm that it will work on NC2 in the second line of the changelog of StockMOD Custom thread (post #2)
Another thing: I see StockMOD Custom has an Aroma Installer. I have not used a ROM with this option. Aroma Installer will give you choices during the ROM installation, I can only guess what they are without installing the ROM. The choices probably entail choosing between the stock apps and the later Galaxy device apps; Note 3, S4, and S5.
Thank you, I'm feeling a lot more confident now.
I will definitely check those links on backing up efs folders/IMEI.
viltnieks said:
Thank you, I'm feeling a lot more confident now.
I will definitely check those links on backing up efs folders/IMEI.
Click to expand...
Click to collapse
You're most welcome. I personally have used several of these methods, redundancy causes no harm.
dawgdoc said:
You're most welcome. I personally have used several of these methods, redundancy causes no harm.
Click to expand...
Click to collapse
I had hoped that everything would go smoothly from this point, it is nothing serious, but I have encountered a small problem.
I followed instruction in the link you provided Part B, point 4, I booted into recovery mode in order to install Synergy Backup. Installation starts, then I get this:
Preparing device...
Setting up 7z
Backing up EFS if unlocked
***Not unclocked Skipping Backup***
Install from sdcard complete.
What is really strange is that after going back and selecting reboot system I get this option in CWM:
Root access possibly lost. Fix?
-No
-Yes - Fix Root (/system/xbin/su)
I verified with titanium backup and root checker that I have root access.
viltnieks said:
I had hoped that everything would go smoothly from this point, it is nothing serious, but I have encountered a small problem.
I followed instruction in the link you provided Part B, point 4, I booted into recovery mode in order to install Synergy Backup. Installation starts, then I get this:
Preparing device...
Setting up 7z
Backing up EFS if unlocked
***Not unclocked Skipping Backup***
Install from sdcard complete.
What is really strange is that after going back and selecting reboot system I get this option in CWM:
Root access possibly lost. Fix?
-No
-Yes - Fix Root (/system/xbin/su)
I verified with titanium backup and root checker that I have root access.
Click to expand...
Click to collapse
Good news is that it caused no harm.
Confusing news is that that message was not caused by Part B, Point 4. I have seen that message before on my SGS3 but not my Captivate. On the SGS3 my custom recovery is TWRP not CWM. Also, I only did Part A, Point 2 on both devices. (The Captivate does have CWM as its recovery.) Fact is I have seen the message more than once, most of the time I selected the option to Fix. On the last time I selected No. I retained root on all occasions. I have seen others report seeing that message and I think it was from some action other than nvbackup. All this leaves me with no idea why it is happening.
dawgdoc said:
Good news is that it caused no harm.
Confusing news is that that message was not caused by Part B, Point 4. I have seen that message before on my SGS3 but not my Captivate. On the SGS3 my custom recovery is TWRP not CWM. Also, I only did Part A, Point 2 on both devices. (The Captivate does have CWM as its recovery.) Fact is I have seen the message more than once, most of the time I selected the option to Fix. On the last time I selected No. I retained root on all occasions. I have seen others report seeing that message and I think it was from some action other than nvbackup. All this leaves me with no idea why it is happening.
Click to expand...
Click to collapse
Coould it be related to the fact that I have data_1, data_2, data_3 folder in my root?
Also when I enter /storage/ I have a lot of folders like:
emulate
extSdCard
sdcard0
UsbDruveA
UsbDruveB
UsbDruveC
UsbDruveD
UsbDruveE
UsbDruveF
I guess this just isn't my lucky week.
I followed the steps mentioned above and install was successful, but I get no OS installed error.
Glad I made those backups...
EDIT:
For some reason the problem was with first file I downloaded in #2nd post StockMOD ROM named StockMOD Custom ROM T999 4.3 RLS2.1.zip
I then downloaded file from #3rd post StockMOD ROM named StockMOD ROM T999 4.3 v4.zip and was able to finish installation successfully. But as you said there is almost no change over the ROM I had before.
viltnieks said:
I guess this just isn't my lucky week.
I followed the steps mentioned above and install was successful, but I get no OS installed error.
Glad I made those backups...
EDIT:
For some reason the problem was with first file I downloaded in #2nd post StockMOD ROM named StockMOD Custom ROM T999 4.3 RLS2.1.zip
I then downloaded file from #3rd post StockMOD ROM named StockMOD ROM T999 4.3 v4.zip and was able to finish installation successfully. But as you said there is almost no change over the ROM I had before.
Click to expand...
Click to collapse
It's possible you had a bad download of the StockMOD Custom ROM. Did you verify the checksum after the download, assuming one was provided in post #2 or the download site? You could always download it again, without verifying, and see if it works correctly the second time.
I just checked my file system and /storage has all of the folders you named with an additional folder, /container. All of the /UsbDrive folders and /container are empty folders on my device. I do not have any idea where they came from.
dawgdoc said:
It's possible you had a bad download of the StockMOD Custom ROM. Did you verify the checksum after the download, assuming one was provided in post #2 or the download site? You could always download it again, without verifying, and see if it works correctly the second time.
I just checked my file system and /storage has all of the folders you named with an additional folder, /container. All of the /UsbDrive folders and /container are empty folders on my device. I do not have any idea where they came from.
Click to expand...
Click to collapse
As it turns out I needed to install StockMOD ROM T999 4.3 v4.zip which is the custom ROM and then update it with StockMOD Custom ROM T999 4.3 RLS2.1.zip
At least that's what I did, now everything works.
Thank you very much for sticking with me during this
There is one last thing that bothers me, during these last few days, I have installed, uninstalled apps, flashed roms, created backups, etc. There probably is a lot of "junk" on the phone at the moment. Is there a way to erase everything and just flash that custom ROM? Like when you reinstall Windows, you format disk and just install a fresh version of windows.
viltnieks said:
As it turns out I needed to install StockMOD ROM T999 4.3 v4.zip which is the custom ROM and then update it with StockMOD Custom ROM T999 4.3 RLS2.1.zip
At least that's what I did, now everything works.
Thank you very much for sticking with me during this
There is one last thing that bothers me, during these last few days, I have installed, uninstalled apps, flashed roms, created backups, etc. There probably is a lot of "junk" on the phone at the moment. Is there a way to erase everything and just flash that custom ROM? Like when you reinstall Windows, you format disk and just install a fresh version of windows.
Click to expand...
Click to collapse
Glad to hear you have been able to get the ROM you want loaded.
The way to clear out all of the detritus would be accomplished while in your custom recovery. In addition to wiping /cache and /dalvik-cache you would also format /data and /system before flashing the ROM. Before doing that, make sure you save anything you wish to reuse to your computer, or at least to an external micro SDcard. Stuff to be saved off the internal SDcard would include your backups, rom zips, and any app apks you may have a hard time finding again; not just music and pictures.
dawgdoc said:
Glad to hear you have been able to get the ROM you want loaded.
The way to clear out all of the detritus would be accomplished while in your custom recovery. In addition to wiping /cache and /dalvik-cache you would also format /data and /system before flashing the ROM. Before doing that, make sure you save anything you wish to reuse to your computer, or at least to an external micro SDcard. Stuff to be saved off the internal SDcard would include your backups, rom zips, and any app apks you may have a hard time finding again; not just music and pictures.
Click to expand...
Click to collapse
Thank you very much!
For the past 3 days i've gone through hell and back with this phone.
To start off I rooted the phone, and that was working fine, my buddy was downloading something (idek what it is and I have no way to get ahold of him to ask him) and after that it busted. Then I somehow deleted my whole operating system.
Since then I have downloaded a 4.3 stock rom (os?) and I have successfully unbricked my phone. Now I have no service, and i'm 99% sure it's because all of my IMEI things are unknown. Now I figure that is an easy fix by downloading a modem?
Before I look into fixing my IMEI problems I would like to get back to 4.4.2 (Kit-Kat I think it was?)
I've downloaded countless ROMs, IMG files (converted to tar.md5), and many versions of Odin.
I've messed with Samsung Kies but I can just tell that this is a garbage program, and I have no clue what i'm doing.
What i'm asking here is help to getting me back to stock 4.4.2 (WITHOUT A ROOT) and possibly fix my IMEI problem and the problem I can't get 3g/mobile data working (snapchat/instagram did not work) (APN maybe?) (I haven't looked into these problems yet, could be super hard, could be fairly easy)
Samsung Galaxy S3 AT&T SGH-i747 is the phone i'm currently working with.
The last thing I tried to do is flash with a boot.tar.md5 and system.tar.md5, it did NOT work, as I was not sure where to put those files at in odin. Boot = Bootloader and System = AP/PDA?
Sorry if I come off as a complete noob, this is literally last resort for me (I've been doing this for 3 days....) as I can probably suspect you guys are very tired of all of these help requests.
Thank you to everybody who reads this, and am looking forward to having a normal phone again.
Edit: First post here
Does the phone boot into download mode? Sounds like it does since you can use Odin.
To get the phone running, copy the latest cm11 or cm 12 to an sd card, copy cm11 Gapps or cm12 Gapps (download the version that matches the ROM you intend to flash), flash a custom recovery (I prefer CWM for the d2lte or Philz Touch for the d2lte), boot into recovery, do a full wipe, flash cm, flash Gapps, boot the phone.
audit13 said:
Does the phone boot into download mode? Sounds like it does since you can use Odin.
To get the phone running, copy the latest cm11 or cm 12 to an sd card, copy cm11 Gapps or cm12 Gapps (download the version that matches the ROM you intend to flash), flash a custom recovery (I prefer CWM for the d2lte or Philz Touch for the d2lte), boot into recovery, do a full wipe, flash cm, flash Gapps, boot the phone.
Click to expand...
Click to collapse
sick thanks for the response homie.
i'm not exactly sure which CM to download, I went to the d2ltes since that's the closest thing to my device I found in that list.
I also went to cwm rom managers and downloaded the recovery setup, i'm guessing I convert that and flash it using odin and voila, I have cwm?
and for the cm11 gapps I went to this website and downloaded the zip file, going to just put that on my sd card with the CM (when I figure out which one to download)
am I headed in the right direction?
edit: okay I got cwm recovery on my phone... thats good
edit 2: alright downloading cm12 and alreayd have cmgapps in a zip ready to be put in my sd card. i'll let you know how installing it with cwm goes. thank you for your help man I really appreciate it.
edit 3: how would I go about installing it via owm? everytime I install from sd card it resets my phone, just go back into recovery and install the second zip? or is there a way I can install both at once?
Boot into cwm, wipe cache, wipe data, wipe dalvik, install cm1 from sd card, install gapps, reboot.
The i747 is also known as the d2lte so anything designed for the d2lte is good.
audit13 said:
Boot into cwm, wipe cache, wipe data, wipe dalvik, install cm1 from sd card, install gapps, reboot.
The i747 is also known as the d2lte so anything designed for the d2lte is good.
Click to expand...
Click to collapse
alright! couldn't thank you enough. like I said i'll keep you updated!
edit: i'm in the cwm recovery or w.e and there is a different keyboard as i'm doing this, does this transfer over to be my real keyboard after the cwm recovery stuff? if not, how do I get this keyboard?
edit 2: wow this is totally different, sick.. let me play around with it, i'm sure i'll have some questions.
alright, phone number is still not available, imei and imei sv is still not available, same with everything in the SIM status.
going to try and find a modem for my model.
no luck so far, if someone could help search for a MODEM for SGH-i747 AT&T s3 that would be great..
sorry for being so needy.. thanks for hanging in here and helping me out.
edit: I found this link but it's for 4.4.2... it says do not use it if you're on 4.3.... is it okay if i'm at like 5.1.1 cwm?
well, I cannot post the link and I do not want to find a way around to post the link incase a mod shuts this thread down. if you want the link you may PM me..
edit 2: okay so google play services does NOT work, and I need that in order to open skype.. so that's on another thing on the list of **** to fix. However I just downloaded an apk and I need to put it in system/apps but i'm not sure where to find that... i'll probably end up downloading it on the phone and dropping it in with a file manager.
edit 3: none of this worked, I still need google play services to get installed..
Does the phone boot to the desktop? Which rom did his try? Try the latest cm10.2 for the d2lte.
Are you able to install a terminal app or Samsung phone info app?
Try and find the apk version of the app and just install it from the file browser.
audit13 said:
Does the phone boot to the desktop? Which rom did his try? Try the latest cm10.2 for the d2lte.
Are you able to install a terminal app or Samsung phone info app?
Try and find the apk version of the app and just install it from the file browser.
Click to expand...
Click to collapse
It tells me "It cannot be installed". I will find 10.2 for d2lte... assuming I find the corresponding GApps.
I also could have ran all of the other google apps... "google +, playstore, youtube, etc"
edit: I cannot find cm 10.2, lowest I can find for d2lte is 11. should I try that instead?
These are all the zips i'm installing with cwm when I wipe/reset my phone totally:
Calkulin's Google Play Service modded (so google play services works)
cm-11
gapps-kk-20140606
and I am currently messing with modem files to get my service back, i'm about to try my second one.. wish me luck!
edit: I can't get my baseband model to show, nor my imei numbers to come, they all stay unknown.. if someone would like to do some sort of 1 on 1 that would be awesome.
You could also try the cm for the d2att.
audit13 said:
You could also try the cm for the d2att.
Click to expand...
Click to collapse
trying it now! should I use a specific gapps? maybe for 5.1.1? cause 12.1 uses 5.1.1 if i'm not mistaken.
There are separate gapps for cm10.2, cm11, and cm12.
It sounds to me like there is a problem with the modem and bootloader combination on the phone.
What specific bootloader version is on the phone?
audit13 said:
There are separate gapps for cm10.2, cm11, and cm12.
It sounds to me like there is a problem with the modem and bootloader combination on the phone.
What specific bootloader is on the phone?
Click to expand...
Click to collapse
so after I download cm12.1 and cm12gapps, I should look further into the bootloader/modem problem?
i've tried a few modems for i747 and i've had no luck so far unfortunately, if someone else reading this has had experience or knows someone who has experiences null baseband / imei numbers let me know!
edit: oops, my mistake.. just saw the last part of your post now. i'm not sure how to find out my bootloader.
Use the terminal app and type getprop ro.bootloader.
audit13 said:
use the terminal app and type getprop ro.bootloader.
Click to expand...
Click to collapse
i747ucufnj1
i'm certain the only problem I have now is the IMEI (no sim service) besides that everything is good now!
farkas3 said:
i747ucufnj1
i'm certain the only problem I have now is the IMEI (no sim service) besides that everything is good now!
Click to expand...
Click to collapse
Alright I've now figured out that I do NOT have ANY efs files for samsung galaxy I747UCUFNJ1.
I have the imei number from the back of my phone.
I tried the EFS pro method and when I click "backup" an error pops up and says "Block device does NOT exist"
I'm so confused and I need help lol
wow, I fixed it! I installed the correct modem corresponding to my baseband / bootloader something like that.. wow. most stressful 4 days of my life
ty so much
Glad you got it working. This is why I kept asking about the modem and suggesting that the modem doesn't match the bootloader.
Hello! This is my first contribution to the community and thought some might find it useful.
Here's my Stock OH3 ROM for the Sprint Samsung Galaxy Note II SPH-L900. You'll find a list of changes that I've made in the differences section of this post. If anything minor changes, they will be listed on posts #2, #3 and #4.
Description:
OH3 is referred to as the Stagefright update. When it was released on August 31, 2015, all known issues at the time were patched.
Since then three more vulnerabilities were discovered. As of October 8, 2015, CVE-2015-6602 and possibly CVE-2015-3875 remain unpatched.
If Samsung and Sprint releases another patch, I'll update this package to reflect the changes.
Information:
Software version: L900VPUCOH3
Android version: 4.4.2
Kernel version: 3.0.31-3084104 [email protected] #1 Mon Aug 24 17:13:18 KST 2015
Build number: KOT49H.L900VPUCOH3
Differences:
Root access via SuperSU v2.46.
Removed KNOX.
Completely deodexed.
BusyBox added.
Enabled write permissions for external SD Card.
Hotspot / Tethering:
Download and install Xposed framework.
Download and install Wanam Xposed.
Open Wanam Xposed and under System, select disable tethering provisioning.
Wi-Fi Hotspot, Bluetooth & USB Tethering will now be enabled.
OH3 Modem:
I have attached the OH3 modem to this post just in case you need it. Unzip the file and flash it with Mobile Odin.
If you don't have the pro version of Mobile Odin, you can find a lite version at the thread below.
http://forum.xda-developers.com/showthread.php?t=1347899
Extra Toggles:
Want an extra row of quick toggles such as the ones listed below?
Mobile Data, Airplane Mode, Wi-Fi Hotspot, S Beam, NFC.
Download the extra toggles file located in the files section of this post to your external SD Card. Once you finish installing the ROM and completed the initial setup, boot into recovery and flash the file.
Issues:
None.
Instructions:
*** BACKUP YOUR CURRENT ROM & INTERNAL SDCARD TO THE EXTERNAL SD CARD BEFORE PROCEEDING. ***
1. Place the ROM on your external SD Card.
2. Boot into Philz Touch Recovery 6.07.9.
3. Select: Wipe Data/Factory Reset & Clean to Install a New ROM.
4. Select: Mounts and Storage & format /data and /data/media (/sdcard).
5. Select: Install Zip & Choose zip from /storage/sdcard1.
6. Pick the ROM to flash from external SD Card and wait until the process is finished.
7. Reboot and enjoy!
Files:
Stock OH3 (Rooted/Deknoxed/Deodexed) [10-08-15]: https://www.androidfilehost.com/?fid=24052804347832689
Philz Touch Recovery 6.07.9: https://www.androidfilehost.com/?fid=24052804347832997
OH3 Modem: https://www.androidfilehost.com/?fid=24052804347833013
Extra Toggles: https://www.androidfilehost.com/?fid=24052804347846974
WiFi Fix (PRE NE2 ONLY)
This fix is only devices that didn't ship with NE2 or never flashed a Stock NE2 Odin package.
Instructions:
1. Load the attached file in the PDA / AP slot in Odin on your PC.
2. Start the flashing process.
3. WiFi should be operation now.
File:
WiFi Fix (PRE NE2 ONLY): https://www.androidfilehost.com/?fid=24052804347841079
Keyboard Update for Stock OH3
This update for the predictive text double space bug that's present in the keyboard that shipped with OH3.
Instructions:
1. Place the update on your external sdcard.
2. Boot into Philz Touch Recovery 6.07.9.
3. Select: Install Zip & Choose zip from /storage/sdcard1.
4. Pick the update to flash from external sdcard and wait until the process is finished.
5. Reboot and enjoy!
File:
Keyboard Update for Stock OH3: https://www.androidfilehost.com/?fid=24052804347842574
EOL
Unfortunately, I won't be able to provide any further updates. My device completely died due to motherboard failure on the morning of Wednesday, November 16, 2016.
Thanks to all who found this ROM useful for their devices!
Note II R.I.P. (2012 - 2016)
Do I have to take any other updated before this ROM or can I just flash it? Im coming from CM 12.1 and before that I was running a TW 5.01 ROM (I think)
EDIT: I flashed it and skipped the TW Setup because WiFi wasnt working. Flashed the modem through MOdin and still no WiFi.
spotopolis said:
Do I have to take any other updated before this ROM or can I just flash it? Im coming from CM 12.1 and before that I was running a TW 5.01 ROM (I think)
EDIT: I flashed it and skipped the TW Setup because WiFi wasnt working. Flashed the modem through MOdin and still no WiFi.
Click to expand...
Click to collapse
I've flashed this on devices that either had NE2, NK2 or OH3. What was the last stock rom version you were running on your device?
Installed this on my wife's new Note 2 inherited from her son. No issues. Nicely done and thanks.
spotopolis said:
Do I have to take any other updated before this ROM or can I just flash it? Im coming from CM 12.1 and before that I was running a TW 5.01 ROM (I think)
EDIT: I flashed it and skipped the TW Setup because WiFi wasnt working. Flashed the modem through MOdin and still no WiFi.
Click to expand...
Click to collapse
I had the same problem coming from CM12.1, this is how I fixed it. YMMV.
Nevermind it failed
spotopolis said:
Do I have to take any other updated before this ROM or can I just flash it? Im coming from CM 12.1 and before that I was running a TW 5.01 ROM (I think)
EDIT: I flashed it and skipped the TW Setup because WiFi wasnt working. Flashed the modem through MOdin and still no WiFi.
Click to expand...
Click to collapse
k3v0 said:
I had the same problem coming from CM12.1, this is how I fixed it. YMMV.
Nevermind it failed
Click to expand...
Click to collapse
Please see post #2.
Update for keyboard available on post #3.
Coming from NE2 based rooted stock ROM. Modem zip will not flash through Philz. Am I to understand correct the only way the OH3 modem can be flashed is specifically with Mobile Odin?
Installed from zip. After install:
SW version = NE2
Baseband version = NE2
Build # = OH3
Suggestions?
lennykravitz2004 said:
Coming from NE2 based rooted stock ROM. Modem zip will not flash through Philz. Am I to understand correct the only way the OH3 modem can be flashed is specifically with Mobile Odin?
Installed from zip. After install:
SW version = NE2
Baseband version = NE2
Build # = OH3
Suggestions?
Click to expand...
Click to collapse
Yes, that's correct. The lite version is available at the thread below.
http://forum.xda-developers.com/showthread.php?t=1347899
jsnzns said:
Yes, that's correct. The lite version is available at the thread below.
http://forum.xda-developers.com/showthread.php?t=1347899
Click to expand...
Click to collapse
Mobile Odin Pro is required for Zip install. Zip file not recognized at all by Lite version.
Any plans for an md5 to flash?
lennykravitz2004 said:
Mobile Odin Pro is required for Zip install. Zip file not recognized at all by Lite version.
Any plans for an md5 to flash?
Click to expand...
Click to collapse
Unzip the file and flash the file named modem.bin inside the archive.
jsnzns said:
Unzip the file and flash the file named modem.bin inside the archive.
Click to expand...
Click to collapse
Thank you very much for:
your work
your time
your patience
I hope some good karma comes your way sooner than AND later.
:good:
is the hotspot fix a mod or a fix. just curious as I am not a subscriber. had the fix for earlier roms but flashed this a hour ago and seems to be good. curious about the hotspot fix
EDIT... found a working hotspot mod/fix.. cant give credits cause all I have is the link. tested, connected to note with my galaxy 10 tab.
thanx to creator of this fix... installed using philz recovery.
http://forum.xda-developers.com/attachment.php?attachmentid=2710344&d=1398532292
barelynotlegal said:
is the hotspot fix a mod or a fix. just curious as I am not a subscriber. had the fix for earlier roms but flashed this a hour ago and seems to be good. curious about the hotspot fix
EDIT... found a working hotspot mod/fix.. cant give credits cause all I have is the link. tested, connected to note with my galaxy 10 tab.
thanx to creator of this fix... installed using philz recovery.
http://forum.xda-developers.com/attachment.php?attachmentid=2710344&d=1398532292
Click to expand...
Click to collapse
I opted to use Wanam Xposed to handle the hotspot/tethering changes. Everything works and stays working. When I was putting this rom together, I noticed that certain modifications that had to do with hotspot/tethering were reset on reboot.
wanam didnt work for me. tried several attempts and rebooting of course. tried above and is still working after several reboots
barelynotlegal said:
wanam didnt work for me. tried several attempts and rebooting of course. tried above and is still working after several reboots
Click to expand...
Click to collapse
Okay, thank you for reporting it and the included fix. I'm going to tweak it a bit because it adds quick toggles that our devices don't use.
Optional extra toggles available on post #1.