Related
So I'm getting tired of waiting for Sprint to roll out the damn ICS OTA...and even when they do, the Touchwiz leaks I've seen don't look terribly interesting. So I'm considering going to CM9 Alpha 2, having already experienced it on my HP Touchpad and loved it.
My original thought process was: backup all apps and settings, use QBking's guide to install CWM, do an additional nandroid backup and move that onto my PC, and install CM9 A2.
My problem is that I'm currently on completely stock Gingerbread EL29. No root. So I can't use Titanium Backup in case I have to go back to GB. I guess theoretically then I could go: Stock -> Stock Root -> Titanium Backup -> CM9A2...but I'm aware that you install CWM as part of the CM9 installation, so trying to shove TB into the mix might be redundant.
My questions are the following:
1. Is a nandroid backup sufficient for this kind of move, or should I be looking to fit Titanium into the mix as well? My understanding is that Titanium would be more or less required to actually get those apps to cross the GB-ICS threshold, short of downloading them all again. But it seems like more work.
2. QBking has videos on how to go from stock GB to CM9A2. But what do I do if I want to go back to EL29 GB, on the offchance I decide to go for Sprint's OTA?
3. Assuming I do go back, can the nandroid backup I made before installing CM9 be used to restore my stock GB settings (after I reinstall the EL29 kernel), or will that brick my phone?
Thanks in advance.
Aganar said:
So I'm getting tired of waiting for Sprint to roll out the damn ICS OTA...and even when they do, the Touchwiz leaks I've seen don't look terribly interesting. So I'm considering going to CM9 Alpha 2, having already experienced it on my HP Touchpad and loved it.
My original thought process was: backup all apps and settings, use QBking's guide to install CWM, do an additional nandroid backup and move that onto my PC, and install CM9 A2.
My problem is that I'm currently on completely stock Gingerbread EL29. No root. So I can't use Titanium Backup in case I have to go back to GB. I guess theoretically then I could go: Stock -> Stock Root -> Titanium Backup -> CM9A2...but I'm aware that you install CWM as part of the CM9 installation, so trying to shove TB into the mix might be redundant.
My questions are the following:
1. Is a nandroid backup sufficient for this kind of move, or should I be looking to fit Titanium into the mix as well? My understanding is that Titanium would be more or less required to actually get those apps to cross the GB-ICS threshold, short of downloading them all again. But it seems like more work.
2. QBking has videos on how to go from stock GB to CM9A2. But what do I do if I want to go back to EL29 GB, on the offchance I decide to go for Sprint's OTA?
3. Assuming I do go back, can the nandroid backup I made before installing CM9 be used to restore my stock GB settings (after I reinstall the EL29 kernel), or will that brick my phone?
Thanks in advance.
Click to expand...
Click to collapse
Hello! Welcome to the AOSP club.
1. Restoring data is usually a no-no for these ROMs because they might cause force closes and slow downs etc. Ultimately, your mileage will vary, but I wouldn't try because
AOSP roms automatically install all the apps you have installed from the market! It's an awesome feature. If some apps aren't automatically installed, then you can find them in data/app or system/app of your nandroid and push it through root explorer or manually install them
2. I would head over the dev section and look for sfhub's oneclick el 29 root. Whenever I want to flash an ICS rom and I'm on ICS, I first use sfhub's oneclick to go back to stock rooted gingerbread, then I go about and install stock el26 cwm and flash etc etc. I don't know if stock root can accept OTA, but I'm sure you'll find a way to back to stock stock in that thread, or in the sticky of dev section that says Auto Root package.
3. It will brick your phone. As a general rule of thumb, don't do anything in the recoveries provided by ICS Roms, as over the past month the E4GT community have seen a high rise in bricks due to them. It will hopefully be resolved once samsung released ICS Source for epic 4g touch, and we can get a real kernel to mess with.
Good luck and have fun! Remember, once you go AOSP, you can never go back.
Why cm9 rather than a leaked version of ics? Im not trying to be an ass or concince you otherwise just curious. From my viewpoint the leaks are stable and some are in odin so its baaically a 1 click install after rooted? Everything about an alpha version makes me nervous and cm9 doesnt seem ready to me so i wonder if im missing something.
Sent from my SPH-D710 using Tapatalk
cm9
someguyatx said:
Why cm9 rather than a leaked version of ics? Im not trying to be an ass or concince you otherwise just curious. From my viewpoint the leaks are stable and some are in odin so its baaically a 1 click install after rooted? Everything about an alpha version makes me nervous and cm9 doesnt seem ready to me so i wonder if im missing something.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
u must not have used a2 because there is less wrong with it than any tw leak there has been ....
just because its a alpha doesnt mean anything its a daily for alot of people almost everything works ....even stuff you will never get on tw like naitive tether and blue tooth controllers like ps3 wii etc
Well I went ahead and did it. No issues to report just yet.
A few post-CM9 install questions though:
1. How do I set speed dials on my phone contacts? I've been searching around and can't quite find it.
2. After ODIN'ing the phone but before installing CM9, I was able to boot to CWM recovery by turning the phone off then holding vol-up + power. But now when I do that it boots into Android recovery. How do I boot to CWM recovery again?
Aganar said:
2. After ODIN'ing the phone but before installing CM9, I was able to boot to CWM recovery by turning the phone off then holding vol-up + power. But now when I do that it boots into Android recovery. How do I boot to CWM recovery again?
Click to expand...
Click to collapse
This is my first Samsung. I have been on HTC until now. I have been wondering the same thing about recovery. I also tried to reinstall CWM from the included Rom Manager it just freezes. Also, I had a problem this morning where I had to use ODIN to put CWM back on and I wiped cache and dalvik and then it would no longer boot. I tried to restore my back up and the same thing. Just froze at boot screen. I had to start over. Luckily I had a pretty current Titanium backup to quickly put my programs back on it.
So, I have the same question as you about CWM and also wiping cache/delvik and restoring the backup.
caseyatbt said:
This is my first Samsung. I have been on HTC until now. I have been wondering the same thing about recovery. I also tried to reinstall CWM from the included Rom Manager it just freezes. Also, I had a problem this morning where I had to use ODIN to put CWM back on and I wiped cache and dalvik and then it would no longer boot. I tried to restore my back up and the same thing. Just froze at boot screen. I had to start over. Luckily I had a pretty current Titanium backup to quickly put my programs back on it.
So, I have the same question as you about CWM and also wiping cache/delvik and restoring the backup.
Click to expand...
Click to collapse
Never touch rom manager for this phone as of now it is not compatible and could brick you. To answer both of your questions about recovery, I do not recommend flashing a different kernel with CM9 the dev did this for your own safety to prevent bricks, and they're really is no need for it on CM9 until you need to update it. Play safe and save your phone, try to save time and you'll brick it
O...k...
That poses problems for my next question. Namely, my signal seems to have taken a nose-dive since installing ICS. I don't know if the signal has actually degraded, since I'm no longer on a Touchwiz-based ROM, or if it only seems like it's degraded, because perhaps the ICS signal detector is more accurate than the GB one and my signal indicator was incorrect before. But I just had a few calls earlier today and there was more static than I'm used to.
So, how do I go about getting another PRL? The workaround I saw for that involved "flashing" a version of the stock kernel onto the SD card long enough to get another one. But if I can't get into CWM...
Can any one answer why I can't restore a CWM backup or even reboot after performing cache or dalvik wipe? I really like this phone, but it sure seems like rooting/recovery/roms work the same as it did on my HTC phone.
Aganar said:
So, how do I go about getting another PRL? The workaround I saw for that involved "flashing" a version of the stock kernel onto the SD card long enough to get another one. But if I can't get into CWM...
Click to expand...
Click to collapse
caseyatbt said:
Can any one answer why I can't restore a CWM backup or even reboot after performing cache or dalvik wipe? I really like this phone, but it sure seems like rooting/recovery/roms work the same as it did on my HTC phone.
Click to expand...
Click to collapse
Here's a link to an FC22 CWM Recovery. ODIN this guy into your phone - http://forum.xda-developers.com/showthread.php?t=1563547&highlight=fc22
@Aganar - The way I've been getting the whole PRL / Profile thing is ---- Get all setup in CM9 the way you like it, fast backup everything via your preferred user land method (titanium, smsbackup, call log backup, etc). Roll back to a Stock GB ROM (calkulin EL29). Update PRL / Profile. Immediately upgrade to ICS but dont wipe the cache. Restore apps & logs from backups. Havent had a single issue...
takes about 10 min round trip.
I guess my concern is, if the flash from GB to ICS is what caused the signal degradation in the first place, why would flashing back to GB in order to update the PRL have any benefit, if I have to flash back to ICS again?
You won't lose the PRL update after you reflash.
---------- Post added at 08:35 PM ---------- Previous post was at 08:35 PM ----------
CyberMacGyver said:
Here's a link to an FC22 CWM Recovery. ODIN this guy into your phone - http://forum.xda-developers.com/showthread.php?t=1563547&highlight=fc22
Click to expand...
Click to collapse
Are you sure? There are all sorts of warnings about that recovery and ICS.
Ok so I have kind of a strange problem and i dont think its with cwm. I always make nandroid backups before flashing new roms as a precaution but in this case it did no good I recently installed Paranoid Android on my phone to try out Jelly Bean. It is pretty awesome But it is a little buggy with a few of the apps i like to run (rom toolbox and dropbox being the major ones). After restoring all my apps i decided to restore my messaging data. That caused the rom to not boot past the google screen. So I decided to go back to Black Ice AOKP with my backup. Didnt work, gave me the "error while restoring /data!". I also just recently updated to CWM Touch 6.0.0.5. I also tried an earlier backup with the same problem. I decided to use fastboot to flash a different CWM (5.8.*.* touch and regular) and basically has the same issue just a different response (could not find data.img, cache.img, and boot.img). Because i use Titanium backup anyway i decided to just wipe and flash Black Ice but when i do it boots for about 30 seconds and then the phone restarts. I tried this multiple times doing multiple formats to no avail. Just for sh*ts i decided to try to wipe and reinstall Paranoid Android. IT BOOTED!! But the weird thing is is that all my apps were still there including my messaging data that borked the install to begin with :/ Anyway to make a long story short, my phone is now working but im afraid that i can't restore my backup or even install a new rom without issues. It seems that CWM will not properly wipe my phone anymore. I am wondering what this new rom could have installed that would cause these issues? I didnt flash any new radios or bootloaders so i dont think that is an issue. Please help!! lol I would like to go back until this rom gets further development or AOKP goes to JB. Any help is appreciated. Thank you for your time
-Erik
I really don't think the ROM caused your recovery to not work correctly. Have you tried a different recovery, like TWRP?
Oh, and any problems you're having with apps on Paranoid can be easily fixed by changing what mode they display in via Paranoid Settings.
shode, ndomeopu
Thanks For The Quick Replies! My Swype Has Decided Too Capitalize Every Word And I'm Not Going Too Fix It Lol.. Anyway I've Tried Changing Modes With Rom ToolboxAnd It Made No Difference. i Will Try With Drop Box. It Seems Like Maybe This New Rom Messed With The Permissions And That's Why i Can't Properly Format? The Thing Is Is That CWM Worked Fine Before Booting This Rom. And i definitely Understand That My Conclusions Don't Make Sense But Neither Does The Problem Lol. i Guess What My Question Is Is Why Do The Previous Versions Off cwm That Worked Before Not Work Now? i Will Give The Other Recovery a Shot And Let You Know But i Prefer cwm Just Because It's What i Know And Had Always Worked... Until Now Of Course. Also i Don't Consider Myself anewbie At Thus Stuff But i Am Definitely No dev Lol. Any Suggestion Is Welcome. Thanks!
jesusice said:
Oh, and any problems you're having with apps on Paranoid can be easily fixed by changing what mode they display in via Paranoid Settings.
Click to expand...
Click to collapse
Silly Me For Not Thinking Of Changing The Settings. dropBox Now Works But My Swype Is Still Messed Up
Swype works fine for me at 320 dpi and phone mode. Which is the Gnex's default settings so if an app gives you issues try those settings. I'm not too sure about CWM, it's been a while since I've used it. If you want to try TWRP the easiest way is to just install Goo Manager and go to Flash ROMs and in the additional options select Flash Open Recovery Script.
well swype in general worked.. maybe its just my browser. Anyway I installed TWRP, makes me wonder why I wanted to keep CWM It worked.. im back to the old rom. Quick question.. does it save the backups to /sdcard like CWM? I thought it said it backed up to /data/media which means if i completely wipe /data ill lose my backups. Also does this mean I dont have as much space for backups? Thanks for your help.
Gimmemabrewski said:
well swype in general worked.. maybe its just my browser. Anyway I installed TWRP, makes me wonder why I wanted to keep CWM It worked.. im back to the old rom. Quick question.. does it save the backups to /sdcard like CWM? I thought it said it backed up to /data/media which means if i completely wipe /data ill lose my backups. Also does this mean I dont have as much space for backups? Thanks for your help.
Click to expand...
Click to collapse
/sdcard and /data/media are the same thing. I'm sure there's a better technical explanation but I think it's symlinked or something. So wiping data or factory reset in recovery will not wipe your SD contents. From within the ROM it might.
I've flashed 3-4 ROMs on my Dinc2. (Magnolia, IC Tazz, Skyraider, ViperINC). I've done the wipe cache/davlik/format before each flash. After testing each ROM, I decided on Magnolia, and did a full superduperwipe via Chillybean's AntiVenom. With each ROM flash I've noticed things being different and outright missing. For example, YouTube may or may not be there after flash.
Is this normal? I've tried formatting with ext3 and ext4, noticing no speed or function different... but could this have something to do with it?
I'm still sorta new at this flashing thing. If there's something I'm missing or doing wrong, I'm open to ALL suggestions.
My phone is a Verizon Dinc2, radio is 320, and my recovery is 4EXT.
Rumblur said:
I've flashed 3-4 ROMs on my Dinc2. (Magnolia, IC Tazz, Skyraider, ViperINC). I've done the wipe cache/davlik/format before each flash. After testing each ROM, I decided on Magnolia, and did a full superduperwipe via Chillybean's AntiVenom. With each ROM flash I've noticed things being different and outright missing. For example, YouTube may or may not be there after flash.
Is this normal? I've tried formatting with ext3 and ext4, noticing no speed or function different... but could this have something to do with it?
I'm still sorta new at this flashing thing. If there's something I'm missing or doing wrong, I'm open to ALL suggestions.
My phone is a Verizon Dinc2, radio is 320, and my recovery is 4EXT.
Click to expand...
Click to collapse
Some Deva just won't put it in their Roms. Most the apps just need to be redowbliaded from the market.
Sent from a phone HTC forgot. Right now its running Chilly powered PAC n a lil NOS jus for fun.
Thanks but that's not what I'm saying. I'm saying I can load the same ROM from the same file and there be different apps or features each time I flash it.
Rumblur said:
Thanks but that's not what I'm saying. I'm saying I can load the same ROM from the same file and there be different apps or features each time I flash it.
Click to expand...
Click to collapse
Then you probably aren't doing a full wipe, assuming the rom isn't an aroma installed rom and you choose different features.
yes, they are Aroma installed, using EXT4 as my recovery. I'm talking about (specifically) Magnolia and ViperINC. I've noticed different apps being loaded with each flash. I use Chilly's AntiVenom wiper, then let the ROM do another wipe of it's own choosing. It's just weird, I thought I'd ask if anyone else ever had the same experience.
...
*facepalm
Rumblur said:
I've flashed 3-4 ROMs on my Dinc2. (Magnolia, IC Tazz, Skyraider, ViperINC). I've done the wipe cache/davlik/format before each flash. After testing each ROM, I decided on Magnolia, and did a full superduperwipe via Chillybean's AntiVenom. With each ROM flash I've noticed things being different and outright missing. For example, YouTube may or may not be there after flash.
Is this normal? I've tried formatting with ext3 and ext4, noticing no speed or function different... but could this have something to do with it?
I'm still sorta new at this flashing thing. If there's something I'm missing or doing wrong, I'm open to ALL suggestions.
My phone is a Verizon Dinc2, radio is 320, and my recovery is 4EXT.
Click to expand...
Click to collapse
Hi Friend,
Best way to overcome this is to install Titanium Backup from play store and take a full backup of your apps+data and you can restore the same after flashing new rom.
Regarding youtube you can flash GAPPS from this link goo.im/gapps (install according to your android version)
denny007 said:
Hi Friend,
Best way to overcome this is to install Titanium Backup from play store and take a full backup of your apps+data and you can restore the same after flashing new rom.
Regarding youtube you can flash GAPPS from this link goo.im/gapps (install according to your android version)
Click to expand...
Click to collapse
Um, if you're flashing sense roms, don't flash gapps... Those are specifically for aosp, cm base and aokp roms.
Sent from my Nexus 7 using xda premium
hey guys... i have 2 att s3's... the one is running CM11 M12, and the other is fully stock...
my wife found out the hard way today that her GPS does not work (CM11/M12 snapshot on NE4 baseband). i have been reading all this about going back to stock for the dial pad menu options and doing the nvram fix and etc etc.... my question is, since i have a stock s3 with the latest NJ1 bootloader and baseband... can't i make a complete backup of that and restore it to her s3 running CM11/M12, get the menu options, do the fix, and restore back to CM11/M12? or will that change the baseband and bootloader back to NE4??
wow... nothin from no one?
A nandroid won't touch bootloader or modem. I don't think an nj1 stock nandroid will boot on ne4 firmware unless you flash a custom kernel too. I would not try it.
It would be easier to just flash an ne4 based touchwiz ROM on her phone. You need a stock dialer to run the ussd code to get into the maintenance menu and do the nvrebuild thing it sounds like you've read up on.
You can find a rooted stock ne4 ROM in the forums here. Talking monkeys and s3rx are both tw and ne4 based so they should work fine too. Just read up and flash carefully.
jason2678 said:
A nandroid won't touch bootloader or modem. I don't think an nj1 stock nandroid will boot on ne4 firmware unless you flash a custom kernel too. I would not try it.
It would be easier to just flash an ne4 based touchwiz ROM on her phone. You need a stock dialer to run the ussd code to get into the maintenance menu and do the nvrebuild thing it sounds like you've read up on.
You can find a rooted stock ne4 ROM in the forums here. Talking monkeys and s3rx are both tw and ne4 based so they should work fine too. Just read up and flash carefully.
Click to expand...
Click to collapse
well, that's kinda half what i am saying... if i restore to the backup i made of the original, i can get the ota update and go from there...
DigiManTX said:
well, that's kinda half what i am saying... if i restore to the backup i made of the original, i can get the ota update and go from there...
Click to expand...
Click to collapse
Restoring an NJ1 nandroid on NE4 firmware might work, it might not, I'm not really sure. I've never tried it and no one has posted any horror stories on here about it that I've seen. If it does actually boot, I think there's a good chance wifi or data (and maybe some other things) won't work right with an NJ1 stock rom on NE4 firmware without flashing a custom kernel too, not that you care too much about that if you're just using it for the GPS fix. It is probably too Frankenphone for an OTA to work, and since it is an up to date NJ1 rom it might not even trigger an OTA. If you try this, make sure you have a nandroid of your CM11, or a CM rom zip readily available for a bail out plan in case this just bootloops. I wouldn't recommend this. I'm just not sure it will work. I doubt it will hard brick, but why tempt fate? AT&T S3's have been really finicky about firmware since Knox was forced on them from MJB onward.
To fix GPS all you really need is a stock dialer. Step 3 in this thread has recovery flashable, near stock AT&T NE4 roms. If flashed properly, I am sure this will work.
You have a higher probability of success if you do this. Make a nandroid backup of CM11 on her phone. Clean flash one of the NE4 roms from the thread above. A full format of the internal storage is recommended when switching from AOSP to TW (sometimes the TW rom just won't boot if you don't), but if you do a full format make sure your CM11 nandroid and the stock rom you're going to flash are stored on an external microSD or you've verified that you can adb push or copy files over usb using mtp when in custom recovery. Otherwise you'll be left with a totally blank phone and no rom to install or backups available. A little microSD preloaded with the files is the most reliable way to go.
Once you're up and running in the stock rom, skip all the setup stuff as best you can and get to a dialer. Open your stock dialer and enter *#197328640#
That should open a menu. Now navigate Mainmenu -> UMTS -> Common -> NVREBUILD -> NVREBUILD
Don't exit or hit home after telling it to rebuild the NVRAM. Let it sit for 30+ seconds, then long press power and pick restart.
Once your phone boots back up open up Google maps and see if location locks, it should now. At this point you can boot into your custom recovery, restore the CM11 backup you made, and enjoy your custom ROM with working location service. It might not be necessary, but I always do all the wipes for a clean flash and format the internal storage again before restoring the nandroid. This takes about an extra 30 seconds and keeps any TW files from getting left over in your AOSP setup.
I've had to do this twice to fix GPS on my phone and it works.
jason2678 said:
Restoring an NJ1 nandroid on NE4 firmware might work, it might not, I'm not really sure. I've never tried it and no one has posted any horror stories on here about it that I've seen. If it does actually boot, I think there's a good chance wifi or data (and maybe some other things) won't work right with an NJ1 stock rom on NE4 firmware without flashing a custom kernel too, not that you care too much about that if you're just using it for the GPS fix. It is probably too Frankenphone for an OTA to work, and since it is an up to date NJ1 rom it might not even trigger an OTA. If you try this, make sure you have a nandroid of your CM11, or a CM rom zip readily available for a bail out plan in case this just bootloops. I wouldn't recommend this. I'm just not sure it will work. I doubt it will hard brick, but why tempt fate? AT&T S3's have been really finicky about firmware since Knox was forced on them from MJB onward.
To fix GPS all you really need is a stock dialer. Step 3 in this thread has recovery flashable, near stock AT&T NE4 roms. If flashed properly, I am sure this will work.
You have a higher probability of success if you do this. Make a nandroid backup of CM11 on her phone. Clean flash one of the NE4 roms from the thread above. A full format of the internal storage is recommended when switching from AOSP to TW (sometimes the TW rom just won't boot if you don't), but if you do a full format make sure your CM11 nandroid and the stock rom you're going to flash are stored on an external microSD or you've verified that you can adb push or copy files over usb using mtp when in custom recovery. Otherwise you'll be left with a totally blank phone and no rom to install or backups available. A little microSD preloaded with the files is the most reliable way to go.
Once you're up and running in the stock rom, skip all the setup stuff as best you can and get to a dialer. Open your stock dialer and enter *#197328640#
That should open a menu. Now navigate Mainmenu -> UMTS -> Common -> NVREBUILD -> NVREBUILD
Don't exit or hit home after telling it to rebuild the NVRAM. Let it sit for 30+ seconds, then long press power and pick restart.
Once your phone boots back up open up Google maps and see if location locks, it should now. At this point you can boot into your custom recovery, restore the CM11 backup you made, and enjoy your custom ROM with working location service. It might not be necessary, but I always do all the wipes for a clean flash and format the internal storage again before restoring the nandroid. This takes about an extra 30 seconds and keeps any TW files from getting left over in your AOSP setup.
I've had to do this twice to fix GPS on my phone and it works.
Click to expand...
Click to collapse
ok... awesome... makes sense at what ur saying. thank you. so you didn't bother with updating the band and just left it on ne4? and yes, i would plan on making a full backup of her cm11 and throw it on the ext SD as well...
DigiManTX said:
ok... awesome... makes sense at what ur saying. thank you. so you didn't bother with updating the band and just left it on ne4? and yes, i would plan on making a full backup of her cm11 and throw it on the ext SD as well...
Click to expand...
Click to collapse
There should be no need to update your bootloader and modem from NE4 to NJ1. I think NE4 is still working just fine even on the latest lollipop alphas available for this phone.
If you feel the need, there is a recovery flashable bootloader/modem update to NJ1 here. I flashed this to get my phone up to NJ1. You can trust anything enewman posts.
On the newer AT&T firmware be sure to always have a matching bootloader/modem (seems to go for MJB, NE4, and NJ1 - everything post Knox). That's why it makes sense to package them together, like has been done in that zip. Always read carefully and upgrade incrementally if you choose to. I don't know if it is some sort of security "feature" thinking something nefarious is going on if bootloader and modem don't match or what, but some hard bricks have been reported if you try to run AT&T S3's without matched bootloader/modem on these firmware revisions.
jason2678 said:
There should be no need to update your bootloader and modem from NE4 to NJ1. I think NE4 is still working just fine even on the latest lollipop alphas available for this phone.
If you feel the need, there is a recovery flashable bootloader/modem update to NJ1 here. I flashed this to get my phone up to NJ1. You can trust anything enewman posts.
On the newer AT&T firmware be sure to always have a matching bootloader/modem (seems to go for MJB, NE4, and NJ1 - everything post Knox). That's why it makes sense to package them together, like has been done in that zip. Always read carefully and upgrade incrementally if you choose to. I don't know if it is some sort of security "feature" thinking something nefarious is going on if bootloader and modem don't match or what, but some hard bricks have been reported if you try to run AT&T S3's without matched bootloader/modem on the these firmware revisions.
Click to expand...
Click to collapse
right on... thank you again! if ne4 is good, then so be it... i just rather not have a shoe thrown at me over this GPS not working thing... lol
DigiManTX said:
right on... thank you again! if ne4 is good, then so be it... i just rather not have a shoe thrown at me over this GPS not working thing... lol
Click to expand...
Click to collapse
Happy wife, happy life
NE4 and NJ1
I've posted questions about the boot-loader "update" over in the other forum and from what I have read , updating from NE4 to NJ1 is basically to return to stock unrooted, some people have reported that the signal drops and GPS was better when going to NJ1, but I've been told that If you are not experiencing issues then there's no need to update.
you have GOT to be kidding me... i finally had the opportunity to do this and it's failing on the restore of the backup i made right beforehand... made a complete backup of everything i had to choose. over 2 gigs... flash the stock rooted, did the nvram rebuild, got the gps lock... all was golden... now trying to restore the cm11 backup and it fails... she is going to kill me now... it was nice knowing you guys...
***edit... and now even going back to cm11 or slimkat, i still don't have gps again... grrrrrr...
DigiManTX said:
you have GOT to be kidding me... i finally had the opportunity to do this and it's failing on the restore of the backup i made right beforehand... made a complete backup of everything i had to choose. over 2 gigs... flash the stock rooted, did the nvram rebuild, got the gps lock... all was golden... now trying to restore the cm11 backup and it fails... she is going to kill me now... it was nice knowing you guys...
***edit... and now even going back to cm11 or slimkat, i still don't have gps again... grrrrrr...
Click to expand...
Click to collapse
That stinks. Did you enable compression on the backup? Did you format internal SD before trying to restore the backup? I don't think the format thing is an absolute must, but it is good practice. If you don't do it you will find some touchwiz files that survive the restore in your AOSP based system. Make sure your backup is stored on an external SD before you do an internal format!
If you can't get the backup to restore after formatting internal storage or you just don't want to try formatting internal storage, here are a couple other things you can try to salvage it.
Titanium Backup has an extract from nandroid backup feature. This could be a Pro feature, I'm not sure. Going pro supports some great developers and unlocks some of the best features, like being able to make a flashable zip of your backups. I find it to be worth the money. This has a chance of being able to get you your apps and app data back, if the backup isn't somehow corrupted beyond being useful.
If it is user data like pictures and such you're worried about, you should be able to copy the nandroid backup to a PC, then extract data.ext4.win archive and explore the files. If the built-in Windows zip utility won't handle it, try 7zip. If the data archive is split (you find a data.ext4.win000, data.ext4.win001, etc) you have to concatenate the files into a usable tar. Combining split archives is fairly simple if you're running Linux, but I'm not sure how to manage it if your PC is running Windows. At the size you mentioned I don't think you'll encounter a split data archive, but I'm not certain. This also assumes that the nandroid isn't corrupted beyond the point of being useful.
As for the GPS thing, if you flash enough roms it happens. I've had to do it twice. Once was after just a few flashes. The second time was after probably dozens. After the second time I keep a nandroid backup of a stock rom on my external SD just so I can quickly revert to stock, rebuild nvram, the revert back to Slimkat.
jason2678 said:
That stinks. Did you enable compression on the backup? Did you format internal SD before trying to restore the backup? I don't think the format thing is an absolute must, but it is good practice. If you don't do it you will find some touchwiz files that survive the restore in your AOSP based system. Make sure your backup is stored on an external SD before you do an internal format!
If you can't get the backup to restore after formatting internal storage or you just don't want to try formatting internal storage, here are a couple other things you can try to salvage it.
Titanium Backup has an extract from nandroid backup feature. This could be a Pro feature, I'm not sure. Going pro supports some great developers and unlocks some of the best features, like being able to make a flashable zip of your backups. I find it to be worth the money. This has a chance of being able to get you your apps and app data back, if the backup isn't somehow corrupted beyond being useful.
If it is user data like pictures and such you're worried about, you should be able to copy the nandroid backup to a PC, then extract data.ext4.win archive and explore the files. If the built-in Windows zip utility won't handle it, try 7zip. If the data archive is split (you find a data.ext4.win000, data.ext4.win001, etc) you have to concatenate the files into a usable tar. Combining split archives is fairly simple if you're running Linux, but I'm not sure how to manage it if your PC is running Windows. At the size you mentioned I don't think you'll encounter a split data archive, but I'm not certain. This also assumes that the nandroid isn't corrupted beyond the point of being useful.
As for the GPS thing, if you flash enough roms it happens. I've had to do it twice. Once was after just a few flashes. The second time was after probably dozens. After the second time I keep a nandroid backup of a stock rom on my external SD just so I can quickly revert to stock, rebuild nvram, the revert back to Slimkat.
Click to expand...
Click to collapse
i just gave up on restoring the backup... somehow some way it magically got deleted off my sd card anyways... i just got to my wits end after that... she didn't kill me and kinda had that "whatever" face...
as far as the GPS working goes... idk what i am doing wrong here. i used the stock rooted rom that i downloaded from the option 3 link. not sure of the differences between the odex and the de-odexed, but i just went with the 1st... in TWRP, i did advance wipe (checked dalvik, system, data, internal, and cache... left micro sd and usb-otg alone), then went back and chose format data, then another advanced wipe with aforementioned options chosen... then rebooted straight into recovery. flashed the stock rooted rom, rebooted again and stock rom came up... went thru all the bs prompts and bypassed what i could. got to the dialer, did the nvram rebuild, waited a min, rebooted, tried maps and also download gps status app... got fixes, saw sats, etc... rebooted and flashed to cm11, pico gapps (since restore didn't work) and started fresh... got maps and gps status app downloaded... no GPS lock, no sats listing in gps status app... tried flashing to slimkat, same deal... and this is where i be now... about to make a smoothie in my vitamix out of these 2 s3's... OH! and this is on both of them... the one running ne4 AND nj1... same procedures done on both...
ok, i just did the same procedure but this time just went with slimkat from fresh and GPS is good... must be a "me" problem or a CM problem... idk... but at least i can work with slimkat... i kinda dig this rom
At a bit of a loss here. I have here a d2att/I747 that was working up until today on PAC-Rom, then I decided to wipe it clean and install a Touchwiz ROM. I tried S3RX, I tried a supposed Note V port, hell, I'm trying stock. None of them will finish booting. S3RX and the Note V port give me a perpetual boot logo, stock gets past the Samsung logo, plays the sound, then gets stuck at the AT&T logo. I've given each one at least an hour to do something, and they're apparently not going anywhere.
I've tried everything I know how to do; I've wiped EVERYTHING (system, data, internal storage, formatted data, the whole shebang) and nothing seems to make a difference. It's on NJ2 and I even just tried reflashing the NJ2 bootloader/modem, but that doesn't seem to have done anything either. Totally at a loss here. What could be causing this? I mean, it boots into download/recovery fine and always -starts- booting the roms, but never finishes. Could I have a corrupted partition or something?
EDIT: Oh, so I put PAC back on it and it boots again. So yeah, this seems specific to TW roms. I don't get it.
which recovery/version do you have ?
are the touchwiz roms the same android version as the pac-rom version ?
checked the touchwiz md5 to make sure has not been bad downloads ? (i know , far-fetched for them all to be bad DLs. just a thought).
"err on the side of kindness"
First off when you went from CM/AOSP based ROM to TW did you wipe everything but external storage? When going from CM/AOSP to TW & vice versa you MUST wipe internal storage. If you do this & it still fails to boot you'll need to flash the stock recovery wipe with it & install stock. Then Odin TWRP & you're good to go.
You can get the stock recovery from enewman17's NE4 thread.
Just be sure to do your research. d2att is the easiest of all d2's to hard brick thanks to At&t not releasing full firmwares.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Flashable AT&T Galaxy S3 NJ2 Stock Recovery Zip (Pulled last fall) Google Drive Links
https://drive.google.com/file/d/0B0lfMZeSyJnYT2xFbUxKVUR0RGM/view?usp=drivesdk
Chuckles5150 said:
Flashable AT&T Galaxy S3 NJ2 Stock Recovery Zip (Pulled last fall) Google Drive Links
https://drive.google.com/file/d/0B0lfMZeSyJnYT2xFbUxKVUR0RGM/view?usp=drivesdk
Click to expand...
Click to collapse
Nice!
? d2att Oct-M KrAkEn Kernel ?
Jaitsu said:
At a bit of a loss here. I have here a d2att/I747 that was working up until today on PAC-Rom, then I decided to wipe it clean and install a Touchwiz ROM. I tried S3RX, I tried a supposed Note V port, hell, I'm trying stock. None of them will finish booting. S3RX and the Note V port give me a perpetual boot logo, stock gets past the Samsung logo, plays the sound, then gets stuck at the AT&T logo. I've given each one at least an hour to do something, and they're apparently not going anywhere.
I've tried everything I know how to do; I've wiped EVERYTHING (system, data, internal storage, formatted data, the whole shebang) and nothing seems to make a difference. It's on NJ2 and I even just tried reflashing the NJ2 bootloader/modem, but that doesn't seem to have done anything either. Totally at a loss here. What could be causing this? I mean, it boots into download/recovery fine and always -starts- booting the roms, but never finishes. Could I have a corrupted partition or something?
EDIT: Oh, so I put PAC back on it and it boots again. So yeah, this seems specific to TW roms. I don't get it.
Click to expand...
Click to collapse
Flash slimkat ROM and then flash TW ROM. It will work I had same problem
Oh wow, I didn't mean to abandon this thread. I haven't been getting email notifications 'til today for some reason. Anyway, yeah, I've wiped *everything* including internal storage; I'm flashing from an external SD. Nada. I was really hoping there was some NJ2 Odin-able package I could use that'd guarantee I wasn't screwing anything up, but oh well. Anyhow, I don't have the device on hand anymore (doing this for a family member), but perhaps I'll get it back and try that slimkat idea...? To answer mrrocketdog's question, no, actually. PAC is 5.1, every TW ROM I've found is 4.4. Shouldn't matter if I'm wiping every partition I can first, though, no?
Jaitsu said:
Oh wow, I didn't mean to abandon this thread. I haven't been getting email notifications 'til today for some reason. Anyway, yeah, I've wiped *everything* including internal storage; I'm flashing from an external SD. Nada. I was really hoping there was some NJ2 Odin-able package I could use that'd guarantee I wasn't screwing anything up, but oh well. Anyhow, I don't have the device on hand anymore (doing this for a family member), but perhaps I'll get it back and try that slimkat idea...? To answer mrrocketdog's question, no, actually. PAC is 5.1, every TW ROM I've found is 4.4. Shouldn't matter if I'm wiping every partition I can first, though, no?
Click to expand...
Click to collapse
Definitely try flashing the slimkat ROM. I had the same prob as you and read someone's reply about it. It fixed the issue for the touchwiz ROMs. After flashing slimkat go back to a touhwiz ROM. Do this before messing with the phone. I have a slimkat ROM on my SD card ready to be flashed at any moment for whenever I want to go back to touchwiz haha
Sent from my SAMSUNG-SGH-I747 using XDA-Developers mobile app
BakedOnSomeSour said:
Definitely try flashing the slimkat ROM. I had the same prob as you and read someone's reply about it. It fixed the issue for the touchwiz ROMs. After flashing slimkat go back to a touhwiz ROM. Do this before messing with the phone. I have a slimkat ROM on my SD card ready to be flashed at any moment for whenever I want to go back to touchwiz haha
Sent from my SAMSUNG-SGH-I747 using XDA-Developers mobile app
Click to expand...
Click to collapse
So do I have to flash Slimkat and then dirty flash TW? Seems like that'd have to be the case, otherwise anything it adds would get wiped away, unless it messes with partitions or something... I need to read up on this ****. That's weird.