Related
Im sorry if this is being repeated, but I'm relatively new to flashing custom ROMs and up until now haven't really had any issues.
I recently flashed the latest PACman rom 4.3 and I'm not sure what went wrong. I'm coming from 4.2. I did everything the same as usual, wiped cache and dalvik, installed the zip. As soon as the phone rebooted, I started getting error messages. "Acore has stopped working, blame tyler", same thing for the system UI. So I decided to do a wipe and restore. Well now my restore wont work. I've had to go back to a PAC version from back in February because none of my other restore files will work. I'm not sure what to do. Even on this restore file, I'm getting "insufficient storage" messages when I havent even uploaded all my apps yet.
Please help!
justxan said:
Im sorry if this is being repeated, but I'm relatively new to flashing custom ROMs and up until now haven't really had any issues.
I recently flashed the latest PACman rom 4.3 and I'm not sure what went wrong. I'm coming from 4.2. I did everything the same as usual, wiped cache and dalvik, installed the zip. As soon as the phone rebooted, I started getting error messages. "Acore has stopped working, blame tyler", same thing for the system UI. So I decided to do a wipe and restore. Well now my restore wont work. I've had to go back to a PAC version from back in February because none of my other restore files will work. I'm not sure what to do. Even on this restore file, I'm getting "insufficient storage" messages when I havent even uploaded all my apps yet.
Please help!
Click to expand...
Click to collapse
I had similar problems going to 4.3 as well. Mine kept getting frozen at the boot screen, and wouldn't restore any of my backups. I tried flashing back to previous versions of android and nothing was really making any difference. Finally I ended up flashing the whole phone back to stock. From there I flashed the new 4.3 stuff on top of that and now everything is working flawlessly like it should again. I still have no idea what caused the issues, it's gotta be something in the new 4.3 stuff that's trickling in.
Here's what I did:
Download the most recent complete firmware file (which is UCDLK3 for d2att)
Download the pit file for my phone
Flash stock image and pit file with repartition through ODIN
Flash custom recovery back through ODIN (CWM, TWRP, etc)
Download and flash latest UCDMG2 bootloader (for d2att)
Download and flash your choice of ROM, kernel & gapps
and optionally -
Update modem to latest UCDMG2
Now you should be back to a fresh install of 4.3 which works the way it should! Hopefully you had your apps backed up with titanium or something similar which can be restored now as well.
exodus454 said:
I had similar problems going to 4.3 as well. Mine kept getting frozen at the boot screen, and wouldn't restore any of my backups. I tried flashing back to previous versions of android and nothing was really making any difference. Finally I ended up flashing the whole phone back to stock. From there I flashed the new 4.3 stuff on top of that and now everything is working flawlessly like it should again. I still have no idea what caused the issues, it's gotta be something in the new 4.3 stuff that's trickling in.
Here's what I did:
Download the most recent complete firmware file (which is UCDLK3 for d2att)
Download the pit file for my phone
Flash stock image and pit file with repartition through ODIN
Flash custom recovery back through ODIN (CWM, TWRP, etc)
Download and flash latest UCDMG2 bootloader (for d2att)
Download and flash your choice of ROM, kernel & gapps
and optionally -
Update modem to latest UCDMG2
Now you should be back to a fresh install of 4.3 which works the way it should! Hopefully you had your apps backed up with titanium or something similar which can be restored now as well.
Click to expand...
Click to collapse
Thank you for responding and providing details. I guess I'm not understanding where to find these files. I have the firmware downloaded. The pit file, I can't seem to find no matter what I search for. I can find help on creating my own, but I'm afraid I'll screw something up if I start messing with things. The stock image, bootloader and modem...no idea where to find those either. I've never had to do any of this before. Are these files within the rom I'm trying to flash??
Alright so I'm new at this and haven't managed to brick my phone yet so that's a good sign.
As far as I've learned the process is Root>Recovery>Rom Flash, at least generally.
I rooted it successfully, but when I try to install recovery with ROM Manager it lists only one S3 with a bracketed cell phone provider I don't think I have. So I ditched CWM and went to Goo Manager but when I try to install that, it just hangs on some download page telling me its about to start.
So I'm going to assume the recovery thing is pretty easy to sort out and move on to my next question.
My S3 is unlocked, but I am under Koodo, which is an extension of Telus. My phone model is a I747M, not an I747. As far as I can see they are identical in hardware and software, but I'm really wondering what ROMs I can install. I've researched but didn't find much, and I don't want to blindly flash a i747 rom onto a potentially different phone, and risk anything.
Oh and PS any ROM with the vanilla android (like on the google phones) will do.
Thanks.
Czaran said:
Alright so I'm new at this and haven't managed to brick my phone yet so that's a good sign.
As far as I've learned the process is Root>Recovery>Rom Flash, at least generally.
I rooted it successfully, but when I try to install recovery with ROM Manager it lists only one S3 with a bracketed cell phone provider I don't think I have. So I ditched CWM and went to Goo Manager but when I try to install that, it just hangs on some download page telling me its about to start.
So I'm going to assume the recovery thing is pretty easy to sort out and move on to my next question.
My S3 is unlocked, but I am under Koodo, which is an extension of Telus. My phone model is a I747M, not an I747. As far as I can see they are identical in hardware and software, but I'm really wondering what ROMs I can install. I've researched but didn't find much, and I don't want to blindly flash a i747 rom onto a potentially different phone, and risk anything.
Oh and PS any ROM with the vanilla android (like on the google phones) will do.
Thanks.
Click to expand...
Click to collapse
Hello Noob (I mean that kindly, I used to be one)
I'll help you with what ever you need. I'm Canadian and on Bell i747M. Feel free to ask me any questions and I'll reply as soon as I can. Hopefully I wont be too confusing. I'll just try to break down all your questions in a point form.
First, i747 and i747M are almost identical. With the latest 4.3 ROMS there are differences in the bootloader that will make data not work on your phone. For now, stay away from any stock 4.3 ROM. AOSP ROMs (CM10, Task650) are fine.
Recovery: Through Rom Manager you will want to download the recovery titled "Samsung Galaxy S3 (ATT) " The AT&T version of the S3 is commonly shown as D2ATT(i747). This recovery will work for you. I have had a problem with TWRP myself recently being stuck on the download page. There is another way to install TWRP, but it is a bit more difficult. Try CWM first and if you like I will give you instructions for TWRP.
ROMs: If you want the most common and most stable Vanilla ROMs for your phone you are gonna want Cyanogenmod or Task's ROM. They are very similar with a few different features. Beware, if you ask questions in Task's thread you will be told it is an ATT ROM only. It does work on the i747M though.
Latest Cyanogen: http://download.cyanogenmod.org/?device=d2att
Latest Task : http://forum.xda-developers.com/showthread.php?t=1766684
You will of course lose Touchwiz on these ROMs.
Touchwiz Roms:
STAY AWAY FROM 4.3 ROMS!!!!!!
These ones will do as is. Watch that they are still 4.1.2
http://forum.xda-developers.com/showthread.php?t=1766684 This one has a white theme and is my favorite.
http://forum.xda-developers.com/showthread.php?t=2176793 This one has tons of options.
As always be sure to read the OP in every thread. You will learn lots there. If you want any more info reply and I will try and help.
BCSC said:
Hello Noob (I mean that kindly, I used to be one)
I'll help you with what ever you need. I'm Canadian and on Bell i747M. Feel free to ask me any questions and I'll reply as soon as I can. Hopefully I wont be too confusing. I'll just try to break down all your questions in a point form.
First, i747 and i747M are almost identical. With the latest 4.3 ROMS there are differences in the bootloader that will make data not work on your phone. For now, stay away from any stock 4.3 ROM. AOSP ROMs (CM10, Task650) are fine.
Recovery: Through Rom Manager you will want to download the recovery titled "Samsung Galaxy S3 (ATT) " The AT&T version of the S3 is commonly shown as D2ATT(i747). This recovery will work for you. I have had a problem with TWRP myself recently being stuck on the download page. There is another way to install TWRP, but it is a bit more difficult. Try CWM first and if you like I will give you instructions for TWRP.
ROMs: If you want the most common and most stable Vanilla ROMs for your phone you are gonna want Cyanogenmod or Task's ROM. They are very similar with a few different features. Beware, if you ask questions in Task's thread you will be told it is an ATT ROM only. It does work on the i747M though.
Latest Cyanogen: http://download.cyanogenmod.org/?device=d2att
Latest Task : http://forum.xda-developers.com/showthread.php?t=1766684
You will of course lose Touchwiz on these ROMs.
Touchwiz Roms:
STAY AWAY FROM 4.3 ROMS!!!!!!
These ones will do as is. Watch that they are still 4.1.2
http://forum.xda-developers.com/showthread.php?t=1766684 This one has a white theme and is my favorite.
http://forum.xda-developers.com/showthread.php?t=2176793 This one has tons of options.
As always be sure to read the OP in every thread. You will learn lots there. If you want any more info reply and I will try and help.
Click to expand...
Click to collapse
Awesome, I appreciate the writeup. So I flashed recovery successfully (ROM Manager doesn't seem to have d2att anymore so I used ODIN).
I'll probably go for Cyanogen mod tommorow, I'll post again if I have any questions.
Thanks.
Czaran said:
Awesome, I appreciate the writeup. So I flashed recovery successfully (ROM Manager doesn't seem to have d2att anymore so I used ODIN).
I'll probably go for Cyanogen mod tommorow, I'll post again if I have any questions.
Thanks.
Click to expand...
Click to collapse
CM is a good ROM. There should soon be Kitkat versions available. You will be seeing nightly updates when it does come around. Before you start flashing, you should learn what a 'Nandroid' is. You can take a Nandroid backup in CWM or TWRP. Always save these to an External SD card. If anything ever goes wrong with your ROM, you can just re flash the Nandroid backup and be back to where you were the day you did the backup. The farther you get into flashing the more likely you will need these. Before doing your first Flash, do an Nandroid and copy your photops and stuff off of the phone. When jumping between Stock and AOSP roms, you will need to do a full wipe and will lose what you have not backed up. Be sure to sync contacts to Google....this is the one that has screwed me the most.
BCSC said:
CM is a good ROM. There should soon be Kitkat versions available. You will be seeing nightly updates when it does come around. Before you start flashing, you should learn what a 'Nandroid' is. You can take a Nandroid backup in CWM or TWRP. Always save these to an External SD card. If anything ever goes wrong with your ROM, you can just re flash the Nandroid backup and be back to where you were the day you did the backup. The farther you get into flashing the more likely you will need these. Before doing your first Flash, do an Nandroid and copy your photops and stuff off of the phone. When jumping between Stock and AOSP roms, you will need to do a full wipe and will lose what you have not backed up. Be sure to sync contacts to Google....this is the one that has screwed me the most.
Click to expand...
Click to collapse
Alright, so I have CWM v5.5.0.4, which from what I understand is pretty outdated. It was probably just me following an outdated guide and forgot to look up an updated version. Will I need to update of will it cause any problems? I already backed up my phone on 5.5.0.4 with Nandroid.
Also I feel like I'm misunderstanding the procedure of flashing a new rom. So I downloaded a cm-10.1.3 zip which is is the latest stable build on android 4.2.2. This has an .img inside so this is the rom. I use CWM to flash this onto my phone correct? (Once I figure out if I need to update CWM)
Lastly whats the deal with Gapps? I downloaded the CM Gapps for 10.1 from their wiki. Is this the only way to get Gmail, Maps, and the Google Play Store onto the phone?
From what I understand I think I can just use odin to flash, correct? If so I'd probably prefer that because its the most familiar and noob friendly.
Czaran said:
Alright, so I have CWM v5.5.0.4, which from what I understand is pretty outdated. It was probably just me following an outdated guide and forgot to look up an updated version. Will I need to update of will it cause any problems? I already backed up my phone on 5.5.0.4 with Nandroid.
Also I feel like I'm misunderstanding the procedure of flashing a new rom. So I downloaded a cm-10.1.3 zip which is is the latest stable build on android 4.2.2. This has an .img inside so this is the rom. I use CWM to flash this onto my phone correct? (Once I figure out if I need to update CWM)
Lastly whats the deal with Gapps? I downloaded the CM Gapps for 10.1 from their wiki. Is this the only way to get Gmail, Maps, and the Google Play Store onto the phone?
From what I understand I think I can just use odin to flash, correct? If so I'd probably prefer that because its the most familiar and noob friendly.
Click to expand...
Click to collapse
I wouldn't use Odin. It really will only become necessary if you want to flash back to complete stock.
You do want the latest version of CWM installed or you will run into problems flashing. You can get this 2 ways.
1: through Rom Manager. You will find your specific CWM with these steps. a-Recovery Setup b-ClockworkMod Recovery c-Hit menu button to left of home and pick 'Show All Devices' d- Here scroll until you get 'Samsung Galaxy S3 (AT&T)' D2ATT. e- Click Flash ClockworkMod Recovery. Allow permissions for root. Ignore the touch option unless you want to pay for it. I can teach you the free way.
You will now have the latest CWM
You can download the latest CM-10.2, it is in release candidate stage and is extremely stable. They have been working on it for months. It will give you 4.3 (The good kind, not the one I warned against). After downloading a ROM, you leave it zipped exactly like it is. Do not extract it, just move it to your SD card. You will also want Gapps. Gapps is necessary because it is Google's own software that is legally not allowed to be built into ROMs. It must be installed separately. You can find those here. They help you know which to use with chart depending on which Cyanogen you use http://wiki.cyanogenmod.org/w/Gapps. Again just move the zip over to your internal.
With these 2 zips transferred to your phone you are ready to start. Before you do, make sure you have transferred all your pics and stuff off of the phone. Also be sure to save your contacts. You can now boot into recovery. You should notice recovery version 6.0.4.3. Volume button scrolls menu, Power button selects. You will want to do a Nandroid backup in case anything goes wrong. I know you did one with CWM 5.5 but should do another just to be sure it is with current CWM. You can delete the other one later.
Goto - backup and restore
Goto - backup to external or /storage/sdcard1 (i put both because im already on 4.4 and may have different menu than you.
Let this work and when done continue to flashing ROM
Go to 'choose zip from /sdcard'
Select CM-10-xxxxxxx.zip
After this completes you will do the same with Gapps.zip
After completion of both files you will need to factory reset your phone. Flashing AOSP over Stock will cause boot loops if you do not.
Go back to CWM main menu and select wipe data/factore reset
After completing this go to wipe cache partition and select this.
Finally you want to wipe Dalvik cache. you will find this in CWM under main menu /advanced/wipe dalvik cache.
Upon completion of this you should have CM10 4.3 running. Just exit CWM reboot phone and when booted follow setup instructions.
Let me know if you get stuck somewhere.
BCSC said:
Upon completion of this you should have CM10 4.3 running. Just exit CWM reboot phone and when booted follow setup instructions.
Let me know if you get stuck somewhere.
Click to expand...
Click to collapse
Alright cool. So through Mod Manager, there was not d2att, there was only S3(Metro PCS) which I thought was a bit odd. I found a way to flash an updated recovery via terminal emulator so that went well.
And your steps were very well written and concise. I'm now running CM without a problem.
Thanks for your help!
Czaran said:
Alright cool. So through Mod Manager, there was not d2att, there was only S3(Metro PCS) which I thought was a bit odd. I found a way to flash an updated recovery via terminal emulator so that went well.
And your steps were very well written and concise. I'm now running CM without a problem.
Thanks for your help!
Click to expand...
Click to collapse
Cool terminal emulator was that other way to do it. Hope all is well for you with this. Welcome to flashing. As another tip, if you are going to flash a lot, there is an app called Titanium backup that is well worth the $5 it costs. It saves all your apps and data and after a clean wipe you can just reinstall all your apps in one step. For example after a wipe you will not lose your Angry Birds levels if you restore your titanium data. It's worth a look.
so i recently dove into rooting my s4 after first spending a lot of time reading this great board, thought i had a handle on it, thought things were going very well, but i've hit a snag, which came while attempting my first restore - i'm hopeful someone will give me a little help,
a little background:
1. before rooting i backed up my phone with titanium, also backed it up by copying all of its contents to my pc.
2. i followed the excellent "[SGH-M919] CF-Auto-Root" instructions and it worked without a hitch, it was a quick and easy process, no surprises.
3. confirmed that i was rooted using "root checker", all systems were go.
4. once the root was done i made another backup using titanium and sms backup. i also made a full system backup using online nandroid pro and, to be extra safe, i also backed up efs using efs backup tool.
5. i then moved some folders and files to my external card and once again backed up my phone as before, including to my pc.
6. feeling confident that i could now restore my system to its rooted stock state if things went south, i decided to flash my first rom with cwm, i went with cm11 m7 4.4.3 - i saved the cm11 and gapps zips to my external card using rom tool box pro, rebooted into cwm recovery, selected the two files, and flashed. i also did a data and cache wipe before doing so.
6. needless to say i was thrilled when cm11 loaded perfectly, it worked great, and it was just what i was hoping for.
7. having been bitten by the apparent ease of flashing roms, i decided to restore my system to it's pre cm11 state, to it's rooted stock rom state, and try another rom, rather than just flash another rom from cm11 - i wanted to make sure that returning to my rooted stock rom state would be a simple matter.
and that's where i've run into problems.
1. as i mentioned i made two system backups of my stock rom before flashing cm11, one right after i rooted my phone, and one after moving some folders and files to the external card.
2. after doing a wipe, i chose to restore the second backup, the one i made after moving files and folders, and it didn't quite work out - everything appeared to restore perfectly, but my device was immediately inundated with pop up warnings about stopped apps, i also got a persistent warning that the system had stopped responding as well, prompting me to choose between "wait" or "stop it". not only was the restored backup mired in popup screens, but it was impossibly slow, impossibly "laggy".
3. so i decided to restore the other stock backup, the one i made before i moved folders and files, and the results were the same, pop screens for apps not working, system warnings, severe lags, etc., identical to the first backup.
then i panicked.
1. i decided to flash my phone with the "[SGH-M919] CF-Auto-Root" file again, again with odin, hoping that it would put me where i started - i didn't stop to think that my phone was already rooted, that the file was was for unrooted phones.
2. not only did the reflash not work (my phone just booted as normal, as if the flash didn't get a chance to finish), but cwm recovery in boot mode was gone, replaced by what appears to be the andorid stock recovery screen, a screen with an animated dying/collapsing robot, - the screen was titled: "android system recovery <3e> and asked for an "update" from the external storage or cache.
3. not knowing what "update" it was looking for, i selected a backed system files (the first rooted stock rom backup i made, the second rooted stock backup i made, and even the cm11 file) - none worked.
4. i then downloaded a clean stock rom from cwm's website, converted it from zip to tar, and tried to flash it using odin with my device in upload mode, it didn't work either.
so how badly did i mess up my phone? any help would be greatly appreciated.
aeneas1 said:
so i recently dove into rooting my s4 after first spending a lot of time reading this great board, thought i had a handle on it, thought things were going very well, but i've hit a snag, which came while attempting my first restore - i'm hopeful someone will give me a little help,
a little background:
1. before rooting i backed up my phone with titanium, also backed it up by copying all of its contents to my pc.
2. i followed the excellent "[SGH-M919] CF-Auto-Root" instructions and it worked without a hitch, it was a quick and easy process, no surprises.
3. confirmed that i was rooted using "root checker", all systems were go.
4. once the root was done i made another backup using titanium and sms backup. i also made a full system backup using online nandroid pro and, to be extra safe, i also backed up efs using efs backup tool.
5. i then moved some folders and files to my external card and once again backed up my phone as before, including to my pc.
6. feeling confident that i could now restore my system to its rooted stock state if things went south, i decided to flash my first rom with cwm, i went with cm11 m7 4.4.3 - i saved the cm11 and gapps zips to my external card using rom tool box pro, rebooted into cwm recovery, selected the two files, and flashed. i also did a data and cache wipe before doing so.
6. needless to say i was thrilled when cm11 loaded perfectly, it worked great, and it was just what i was hoping for.
7. having been bitten by the apparent ease of flashing roms, i decided to restore my system to it's pre cm11 state, to it's rooted stock rom state, and try another rom, rather than just flash another rom from cm11 - i wanted to make sure that returning to my rooted stock rom state would be a simple matter.
and that's where i've run into problems.
1. as i mentioned i made two system backups of my stock rom before flashing cm11, one right after i rooted my phone, and one after moving some folders and files to the external card.
2. after doing a wipe, i chose to restore the second backup, the one i made after moving files and folders, and it didn't quite work out - everything appeared to restore perfectly, but my device was immediately inundated with pop up warnings about stopped apps, i also got a persistent warning that the system had stopped responding as well, prompting me to choose between "wait" or "stop it". not only was the restored backup mired in popup screens, but it was impossibly slow, impossibly "laggy".
3. so i decided to restore the other stock backup, the one i made before i moved folders and files, and the results were the same, pop screens for apps not working, system warnings, severe lags, etc., identical to the first backup.
then i panicked.
1. i decided to flash my phone with the "[SGH-M919] CF-Auto-Root" file again, again with odin, hoping that it would put me where i started - i didn't stop to think that my phone was already rooted, that the file was was for unrooted phones.
2. not only did the reflash not work (my phone just booted as normal, as if the flash didn't get a chance to finish), but cwm recovery in boot mode was gone, replaced by what appears to be the andorid stock recovery screen, a screen with an animated dying/collapsing robot, - the screen was titled: "android system recovery <3e> and asked for an "update" from the external storage or cache.
3. not knowing what "update" it was looking for, i selected a backed system files (the first rooted stock rom backup i made, the second rooted stock backup i made, and even the cm11 file) - none worked.
4. i then downloaded a clean stock rom from cwm's website, converted it from zip to tar, and tried to flash it using odin with my device in upload mode, it didn't work either.
so how badly did i mess up my phone? any help would be greatly appreciated.
Click to expand...
Click to collapse
If it boots at all you didn't kill it.
Not sure what rom you got from the CWM site. They do recoveries, not roms. The ROM manager app does allow you to download roms, but you can't just convert those from zip to tar. That doesn't make them flashable in Odin.
Here's what you do. Get the stock ROM from either here on XDA (use the search feature to find it) or from Sammobile.com.
Flash that in Odin.
Then you can start over.
---OR---
If you want to try to fix what you've got now, download CWM or TWRP RECOVERY (nor ROM) and flash that in Odin. Boot to recovery, wipe data and system, and flash any other rom you want. That will start you over with a fresh rom of your choice.
Skipjacks said:
f it boots at all you didn't kill it.
Click to expand...
Click to collapse
hallelujah!
Skipjacks said:
Not sure what rom you got from the CWM site. They do recoveries, not roms.
Click to expand...
Click to collapse
my apologies, i meant that i downloaded recovery files from the cwm website, not a rom files - i got them from https://www.clockworkmod.com/rommanager - i downloaded both (touch & non-touch) s4 t-mobile versions (6.0.4.7). i'm assumed those were recovery files?
Skipjack" said:
The ROM manager app does allow you to download roms, but you can't just convert those from zip to tar. That doesn't make them flashable in Odin.
Click to expand...
Click to collapse
again, my apologies - i meant that i downloaded *.img files, not zips, and converted them to tars for odin use. i used a batch file to convert them from img to tar, found at xda, here: http://forum.xda-developers.com/showthread.php?t=2281287 - it seemed to do the job, odin ran and reported success. wrong files? wrong conversion?
Skipjack said:
Here's what you do. Get the stock ROM from either here on XDA (use the search feature to find it) or from Sammobile.com.
Flash that in Odin.
Then you can start over.
---OR---
If you want to try to fix what you've got now, download CWM or TWRP RECOVERY (nor ROM) and flash that in Odin. Boot to recovery, wipe data and system, and flash any other rom you want. That will start you over with a fresh rom of your choice.
Click to expand...
Click to collapse
given a choice, i'd like to do what's bolded in red - but that's what i thought i was doing by flashing the cwm file i downloaded from the cwm website - but after the flash attempt it wouldn't boot into cwm, it would just boot into (i'm assuming") the stock rom i restored, which was a mess. i also unchecked auto-boot to see if that helped - but when i manually booted it didn't boot into cwm, it booted into the stock recovery, with the animated android.
i'll try downloading cwm from the sources you provided, and see if that does the trick. btw, why do you think i was able to flash the cm11 rom with (seemingly) perfect success, but wasn't able to restore either one of the full system (android) backups i made after i rooted my phone?
anyway Skipjack, thanks a ton for your assistance and i'll report back after i give your sources a try. fwiw, it sure is a great charge when a newbie like me sees a custom rom load for the first time, displaying a new ui as it boots, fun stuff.
Just download the ready yo flash tar files. Cwm has them. Twrp has them.
success Skipjack thanks to your generous time and assistance!
i ended up downloading the latest odin zip i could find and philz_touch_6.08.9-jfltetmo.tar.md5... my first try didn't take, with auto-reboot checked, my phone simply rebooted into the same problematic rom i had restored. i then tried it with auto-boot unchecked and manually booted when odin reported pass/success, and it worked. what struck me as odd was how long it took to flash, to report pass/success, around 3-5 minutes if i had to guess, a big difference compared to when i first used odin to root my phone with the["SGH-M919] CF-Auto-Root *.tar.md5 file - i'm guessing that's why it didn't work with auto-boot checked, just took too long?
anyway once i booted into philz_touch recovery i executed the wipe data/factory reset > clean to install a new rom command and then flashed the cm11 m7 (snapshot) rom, which i had flashed once before, right before i attempted to restore the stock rom it had replaced. and as was the case the first time around, it installed without a hitch and is running smooth and fast.
however now when i boot the phone, as soon as the cyanogen logo appears, very tiny text appears in the upper left hand corner which reads (i had to use a magnifying glass!) - it doesn't seem to effect the performance of he device but i'd like to get to the bottom of it, i've already searched and it appears to be a rather common issue.
kernel is not seandroid enforcing
set warranty bit: kernel
btw, i forgot to mention, when i purchased my sgh-m99 it already had 4.3 installed - when i flashed my first rom (cm11 m7) it included kitkat 4.4.2... could this be what caused my problems? did trying to go back to (restore) a 4.3 rom after flashing a 4.4.2 rom screw things up? can this even be done successfully?
and finally, at the risk of bugging the heck out of you, what roms do you prefer for your s4, assuming you have an s4? do you like aosp roms or touchwiz? does one type have a better reputation of being more stable? the primary reason i wanted to rot my phone was to get rid of a bunch of t-mobile / samsung bloatware, which i thought i could do by installing a lean custom rom. any suggestions, which are your favorites? thanks again Skipkack.
ouhned after
re the two lines of text i now get in the upper left hand corner of the screen whenever i boot, the kernel message:
kernel is not seandroid enforcing
set warranty bit: kernel
well after a lot of searching and reading, including coming across dozens of "fixes" and "solutions" that didn't seem to work for many folks, these two responses seemed to make some sense, what do you think?
eclpsues said:
I'm not an expert in Android OS but I think this is not an error. It is more of a notification that the STOCK KERNEL has been change to a CUSTOM one.
Click to expand...
Click to collapse
Joku1981 said:
You are right.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2594483
aeneas1 said:
re the two lines of text i now get in the upper left hand corner of the screen whenever i boot, the kernel message:
kernel is not seandroid enforcing
set warranty bit: kernel
well after a lot of searching and reading, including coming across dozens of "fixes" and "solutions" that didn't seem to work for many folks, these two responses seemed to make some sense, what do you think?
http://forum.xda-developers.com/showthread.php?t=2594483
Click to expand...
Click to collapse
The tiny text on the boot screen is basically telling you that Knox has been tripped. You are right. It does not affect the performance of the phone.
Skipjacks said:
The tiny text on the boot screen is basically telling you that Knox has been tripped. You are right. It does not affect the performance of the phone.
Click to expand...
Click to collapse
thanks skipjack... btw i'm really liking the cm11 m7 rom but, via the learning curve process, i've discovered it does not support wifi calling, something that apparently all aosp rom lack, guess i'll have to go with a touchwiz rom even tho the selection seems to be few and far between. also, is it possible to revert back to 4.3 once 4.4.2 has been flashed? seems like there's a lot of mixed opinions on this, altho in terms of those opinions it's hard for me tell who the pros are that should believed, and who the other guys are that really don't know. thanks again.
aeneas1 said:
thanks skipjack... btw i'm really liking the cm11 m7 rom but, via the learning curve process, i've discovered it does not support wifi calling, something that apparently all aosp rom lack, guess i'll have to go with a touchwiz rom even tho the selection seems to be few and far between. also, is it possible to revert back to 4.3 once 4.4.2 has been flashed? seems like there's a lot of mixed opinions on this, altho in terms of those opinions it's hard for me tell who the pros are that should believed, and who the other guys are that really don't know. thanks again.
Click to expand...
Click to collapse
Once you are rooted you can flash any custom ROM 4.3, 4.4, 4.2, etc. and then go back to stock 4.3. And only TW ROMs allow wifi calling
Sent from my SGH-M919 using XDA Premium 4 mobile app
Kriptik210 said:
Once you are rooted you can flash any custom ROM 4.3, 4.4, 4.2, etc. and then go back to stock 4.3. And only TW ROMs allow wifi calling.
Click to expand...
Click to collapse
very interesting... i guess i misunderstood the posts i read on the subject, maybe they were discussing whether or not you could revert to 4.3 from 4.4.2 on non-rooted phones, which i'm guessing isn't possible. anyway, as i mentioned previously, i fist rooted my 4.3 phone, did a full system backup (using online nandroid), flashed a 4.4.2 rom which worked perfectly, then tried to restore my 4.3 backup only to encounter a bunch of problems, thought going from 4.4.2 back to 4.3 may have caused the problems but i guess not?
so if i'm using a 4.4.2 custom rom and want to restore a 4.3 backup i should be able to boot into recovery and restore from there? or would i need to do a 4.3 flash first, before restoring a 4.3 backup?
aeneas1 said:
very interesting... i guess i misunderstood the posts i read on the subject, maybe they were discussing whether or not you could revert to 4.3 from 4.4.2 on non-rooted phones, which i'm guessing isn't possible. anyway, as i mentioned previously, i fist rooted my 4.3 phone, did a full system backup (using online nandroid), flashed a 4.4.2 rom which worked perfectly, then tried to restore my 4.3 backup only to encounter a bunch of problems, thought going from 4.4.2 back to 4.3 may have caused the problems but i guess not?
Click to expand...
Click to collapse
Did you wipe before you restored? And do not misunderstand this, you cannot downgrade firmwares once you go 4.3 and up, but you can downgrade the system, which is what you did with your backup
serio22 said:
Did you wipe before you restored? And do not misunderstand this, you cannot downgrade firmwares once you go 4.3 and up, but you can downgrade the system, which is what you did with your backup
Click to expand...
Click to collapse
thanks very much for the clarification, i was under the impression that firmware and system were somewhat synonymous in this context, i.e. if you upgraded firmware you were in effect upgrading the system, but i see that's not the case, again thanks. and yes i did do a full wipe before trying to restore the backup, was i not supposed to?
aeneas1 said:
thanks very much for the clarification, i was under the impression that firmware and system were somewhat synonymous in this context, i.e. if you upgraded firmware you were in effect upgrading the system, but i see that's not the case, again thanks. and yes i did do a full wipe before trying to restore the backup, was i not supposed to?
Click to expand...
Click to collapse
Updating firmware does update the system. Based on your previous comment the only thing you did was update the system by flashing a ROM which only contains the system, data, and kernel, so you can still flash the 4.3 firmware. Firmware consists of bootloader, recovery, modem, and system, what you cannot downgrade is the bootloader, the flash will fail every time because it will try to downgrade it. And you should not experience any issues restoring your back up. What were this problems?
btw serio22, do you have a favorite tw rom?
Yea serio22, what is your favorite TW ROM?
Sent from my SGH-M919 using XDA Premium 4 mobile app
serio22 said:
Based on your previous comment the only thing you did was update the system by flashing a ROM which only contains the system, data, and kernel, so you can still flash the 4.3 firmware.
Click to expand...
Click to collapse
but the cm11 rom zip i flashed included 4.4.2, before flashing i was using 4.3 - so didn't i update (or change) both the system and firmware?
btw, fwiw, - now that i'm up and running thanks to skipjacks help, i decided to try restoring my 4.3 backup again. when i tried this in the past it would restore to the same state as it was before but it was virtually unusable because of severe lags and multiple app not working popups that made navigating almost impossible. well now when i try to restore it fails and i get the following message:
checking md summs...
md5 mismatch
serio22 said:
Based on your previous comment the only thing you did was update the system by flashing a ROM which only contains the system, data, and kernel, so you can still flash the 4.3 firmware.
Click to expand...
Click to collapse
but the cm11 rom zip i flashed included 4.4.2, before flashing i was using 4.3 - so didn't i update (or change) both the system and firmware?
btw, fwiw, - now that i'm up and running thanks to skipjacks help, i decided to try restoring my 4.3 backup again. as i mentioned, when i tried this in the past it would restore to the same state as it was before but it was virtually unusable because of severe lags and multiple "app not working" popups that made navigating almost impossible. but now when i try to restore the 4.3 backup it fails and i get the following message:
checking md summs...
md5 mismatch
update:
well it looks like the *.md5 file was pointing to my internal drive rather than external which is where i had moved the 4.3 backup (and apparently the *.md5 file didn't update or account for the move), anyway i copied the backup to my internal drive and, viola, no more md5 mismatch errors. more importantly, it restored the 4.3 backup perfectly, in the exact same state as before, without all of lagging and pop up issues i was having before, so i'm one happy camper! not sure what i did the first time around, but all is good now, for he time being, sure wish i knew what i mucked up to cause the problems in the first place, i really have no idea, other than being a newbie at this. also, fwiw, the tiny text in the upper left hand corner that appears during boot (kernal message) no longer appears now that i have restored the 4.3 system backup... fwiw2, i'm liking the philz_touch_recovery but it sure has taken some getting used to, the commands are so close together and the thing is so sensitive, very easy to accidentally select the wrong option, and some of the wrong options aren't too friendly if it wasn't what you had intended to select.
aeneas1 said:
but the cm11 rom zip i flashed included 4.4.2, before flashing i was using 4.3 - so didn't i update (or change) both the system and firmware?
Click to expand...
Click to collapse
Read my previous post more closely below. Good to see you up and running though! And no I don't have a favorite tw Rom
serio22 said:
Updating firmware does update the system. Based on your previous comment the only thing you did was update the system by flashing a ROM which only contains the system, data, and kernel, so you can still flash the 4.3 firmware. Firmware consists of bootloader, recovery, modem, and system, what you cannot downgrade is the bootloader, the flash will fail every time because it will try to downgrade it.
Click to expand...
Click to collapse
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
I've been running CM11 nightlies for a while now, but recently decided to switch back to the dreaded touchwiz, as some apps weren't operating correctly. I used CWMR to restore the backup I had made previous to installing CWM. Booting up revealed many processes failing during the setup process, as well as the absence of the keyboard. Being a bit noobish, I installed a stock rom/recovery, hoping that would fix the issues. It did not. It stalls at "Just a sec..." before Setup Wizard quits and it loops indefinitely. Problem is I now can't flash a new rom or restore. I've tried installing cwm with no luck since, but take this with a grain of salt as I was admittedly a bit panicky during. Any help is greatly appreciated.
So are you still looking to restore or find any method to have your device boot up again...?
Spark91 said:
So are you still looking to restore or find any method to have your device boot up again...?
Click to expand...
Click to collapse
Yes. I've had no luck the past few days with it. Might give up on it if I can't get it working.
Head to rwilco12's website and under downloads for the Galaxy S II Sprint SPH-D710, Download the Odin OneClick of the stock rooted GB27, You can choose between deodexed or odexed, pick your poison, note that choosing Full Restore wipes internal and No_Data preserves internal storage.
Put device in download mode and restore.
Once you've fully restored, Download AGAT's gb27 source recovery and flash via recovery flasher on device or Odin on PC. Start up into recovery and try restoring your GB27 ROM again. I remember there being a guide when flashing back and forth from cm to tw and there was a specific way you had to restore it, I've lost the thread but still looking for it for you.
But until then, try the Odin one click method and see where it flies there