Develop Bugs

[Q] Possible hwr problem need advice.

So here's my issue. My phone no longer allows me to flash roms from my external or internal sd card safely. What happens with every rom I flash is twofold. Data connection is always lost, and any reboot causes the phone to boot directly into download mode bypassing the odin flash page. The phone recovers from this with a simple odin back to stock. However, not being able to use non stock roms is no bueno to me.
Does this sound like some internal hwr problem? Is this an SD card issue? Would love some insite.

Which recovery are you using?
Sent from my SPH-L900 using xda premium

Using clockwork recovery current version
Sent from my Nexus 7 using xda app-developers app

Every ROM I flashed had some bugs and they started to multiply. I used Super Wipe and killed EVERYTHING.
I then loaded every zip onto my micro SD via my computer and put it in my phone. Flash and Go.
I went back to stock rooted MA7. The glitches were gone,
So my suggestion is to do a recovery of your first full backup or do what I did.

Okay will try super wipe tonight thanks
Sent from my Nexus 7 using xda app-developers app

Or if that doesn't work use twrp.
Sent from my SPH-L900 using xda premium

Honestly after I Odin it I think Ill try twrp first. I think I've used the superwipe before
Sent from my Nexus 7 using xda app-developers app

rezistrat said:
Honestly after I Odin it I think Ill try twrp first. I think I've used the superwipe before
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Okay, I can't find the thanks button for you guys. THis is the solution. Don't use CWM recovery. TWRP worked wonders, and because I didn't format recovery in cwm so superwipe would probably had helped as well

Glad its working now. I have never used cwm on this phone. But twrp has been smooth sailing.
Sent from my SPH-L900 using xda premium

Use twrp on my s3, and cwm on the wife's note 2. Never had a problem with cwm. Sounds like the problem was not doing a full wipe with cwm (and not a problem with the cwm recovery itself)? But, whatever works for you.
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2

Ive been flashing phones since htc touch pro and ive never had this much problem. Granted I know its me and not the recovery
Sent from my SPH-L900 using xda app-developers app

TW rom issue!

Hi everytime I flash an tw rom on first boot everything works perfectly but as soon as I reboot I get this error phone.android.com has stopped and it keeps doing it so force closing each 15 seconds..
I tried to reflash whit a full wipe various times different tw roms but it still happens??
Also while im at it dont feel like opening another thread I have cwm6 touch the latest and during a nandroid backup it says backup of /data has failed some sort of error ....
I really want to go back to tw tired of aosp any ideas?
Sent from my SGH-T999 using xda app-developers app

Wipe everything and odin flash the root66 firmware. Start over from full stock rooted, but clean.
Run your nandroid again and write down the error. (Save log to sd).
Seems to me there is some corrupted data getting left behind. I'd format the external sd as well. But at least backup and delete the Android folder. (Contains 2 folders inside, data and obb). You can rename to Android-bak if you prefer. Do this before wiping and flashing root66.
Sent from my SGH-T999 using xda premium

Thing is I don't really have access to a laptop anymore and it's really hard I could use mobile odin I guess but this all started since I started using cwm touch might first try to go back to non touch cwm but the process will certainly require a reboot which again will give me force closes...
Sent from my SGH-T999 using xda app-developers app

shahkam said:
Thing is I don't really have access to a laptop anymore and it's really hard I could use mobile odin I guess but this all started since I started using cwm touch might first try to go back to non touch cwm but the process will certainly require a reboot which again will give me force closes...
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
The data error I had too, but on twrp and it's a known thing all over recovery threads for a while now. The error thing happened to me a while back but a root66 fixed that, you should also get the other bug fixed with in the same process.

shahkam said:
Thing is I don't really have access to a laptop anymore and it's really hard I could use mobile odin I guess but this all started since I started using cwm touch might first try to go back to non touch cwm but the process will certainly require a reboot which again will give me force closes...
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Mobile Odin isn't hard to use at all. I highly recommend using it in place of cwm and twrp, except for when a nandroid is needed.
As for the cwm touch, have you considered trting twrp? Personally I prefer it over cwm.
Sent from my SGH-T999 using xda premium

DocHoliday77 said:
Mobile Odin isn't hard to use at all. I highly recommend using it in place of cwm and twrp, except for when a nandroid is needed.
As for the cwm touch, have you considered trting twrp? Personally I prefer it over cwm.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Yeah everybody suggests twrp its just that im so familiar whit cwm im sort of affraid of using anything else lol.. but for now im gonna flash non touch cwm first and as of now I've setup my rom and im scared if I flash another recovery I'll have to re setup the rom... ugh...
Sent from my SGH-T999 using xda app-developers app

Have you tried liquidsmooth?
shahkam said:
Hi everytime I flash an tw rom on first boot everything works perfectly but as soon as I reboot I get this error phone.android.com has stopped and it keeps doing it so force closing each 15 seconds..
I tried to reflash whit a full wipe various times different tw roms but it still happens??
Also while im at it dont feel like opening another thread I have cwm6 touch the latest and during a nandroid backup it says backup of /data has failed some sort of error ....
I really want to go back to tw tired of aosp any ideas?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Hey man I have been running Liquidsmooth 4.2.2 for a long time and its the best ROM I know of. You should give it a try!

No doubt its a good rom but was on illusion for like 2months tired of aosp might give miui v5 another spin kinda liked it..
Sent from my SGH-T999 using xda app-developers app

shahkam said:
Yeah everybody suggests twrp its just that im so familiar whit cwm im sort of affraid of using anything else lol.. but for now im gonna flash non touch cwm first and as of now I've setup my rom and im scared if I flash another recovery I'll have to re setup the rom... ugh...
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
There's no reason at all to be nervous about trying a different recovery. Thousands of people have been using it w/o issue. Personally I think they are both really good, I just prefer twrp. Give it a shot, if you don't like it, install cwm.
It shouldn't do anything at all to your current rom. Recovery is on a completely different partition. And you can install w/o flashing. Use goo manager for twrp or rom manager for cwm.
Sent from my SGH-T999 using xda premium

DocHoliday77 said:
There's no reason at all to be nervous about trying a different recovery. Thousands of people have been using it w/o issue. Personally I think they are both really good, I just prefer twrp. Give it a shot, if you don't like it, install cwm.
It shouldn't do anything at all to your current rom. Recovery is on a completely different partition. And you can install w/o flashing. Use goo manager for twrp or rom manager for cwm.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I'll give feedback tomorrow onto that but rebooting the device gives me that android.phone.com has force stopped error so trying to avoid that but will definitely try twrp recovery
Sent from my SGH-T999 using xda app-developers app

[Guide] How to PROPERLY flash a rom

OK guys, lately I've been seeing a little too many people complaining about bootloops and UI crashes, etc when installing/flashing a new rom. This guide includes installing an update of the rom you're currently on that has been re-based as well.
The only reason I'm making this guide is so that users stop filling threads with these issues that are caused by user errors (99% of the time). I haven't bootlooped or had any problems at all when flashing a new rom and I can promise you that I am a huge flashaholic. Here are the steps for a TOUCHWIZ rom:
1. Download rom and calculate md5 checksum (this can be done using ES file explorer from the play store)
2. Reboot into recovery and make a nandroid backup! Can't stress this enough...
3. Do a FULL wipe. This is where I notice the error that most people make. You must do a wipe of data, cache, dalvik cache, preload AND SYSTEM.
- Don't just do a Factory reset, you must manually wipe system as well to prevent any issues. In TWRP this will be under advanced wipe, and in Philz touch recovery this is done by selecting the "Full wipe to install a new rom" option.
4. AFTER wiping all of the above mentioned partitions, then look for the rom in your internal/external SD card and install/flash it.
- if the rom has an aroma installer, sometimes it'll include a full wipe option in there, this doesn't mean that you can skip the full wipe done in step 2 of this guide.
5. Allow the rom to install everything and then choose the reboot option within your chosen recovery.
6. Let the phone reboot, input all of your info in the initial setup and then let the phone sit for a couple minutes. After this I usually reboot the phone again as a habit.
If you follow these steps to the T you shouldn't have any problems. I've yet to bootloop once on this phone with any rom. Now go and flash away!
Other possible issues/fixes:
- if you have a 64gb SD card, your current kernel or the kernel included with the rom you're flashing might not support 64gb SD cards in EXfat format. A fix for this would be to either flash another kernel that has 64gb SD card support or to copy everything from your SD card to a computer, format your EXfat sd card to fat32 format and then retransfer the files back to your sd card.
-some people have reported that moving the zip file from the internal SD to the external SD or vice versa has fixed flashing issues so make sure to try this as well, not sure why this works but it does sometimes.
-if a specific cause can't be diagnosed it's always recommended to restore your phone back to complete stock using Odin to flash stock firmware. Here is a link to the stock firmwares (I take no credit for that thread): http://forum.xda-developers.com/showthread.php?t=2335109
*Will add more info

Just in case.
Sent from my SGH-M919 using XDA Premium 4 mobile app

The twrp has the system wipe option. I don't see that with Cwm, just factory rest/data, and the two caches
Sent from my SGH-M919 using xda app-developers app

shengwang917 said:
The twrp has the system wipe option. I don't see that with Cwm, just factory reset/data, and the two caches
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
-Data wipe/Factory reset. In Philz CWM version when you chose this it stated "Wipe phone for new ROM"

Every recovery as far as I've seen has a system wipe option, just have to look for it. Only mention TWRP because I haven't used the other recoveries in a while.
Sent from my SGH-M919 using XDA Premium 4 mobile app

Question, for restoring nandroid backup : before I first started to flash roms last week. I did the following with Twrp, backup, - wipe data and caches(no system), then I backup again before moving forward with the flash. My question is: can I just restore my second backup with just the system without the data.?
Sent from my SGH-M919 using xda app-developers app

Why do you backup twice? And why would you restore just the system partition? You might as well just reflash the rom so you don't waste space having a system only backup.
Sent from my SGH-M919 using XDA Premium 4 mobile app

shengwang917 said:
Question, for restoring nandroid backup : before I first started to flash roms last week. I did the following with Twrp, backup, - wipe data and caches(no system), then I backup again before moving forward with the flash. My question is: can I just restore my second backup with just the system without the data.?
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
A nandroid will restore your phone exactly how it was when you made the back up.
If I read it correctly, on the 2nd backup, you did a wipe before you did a backup.
So if you restored that 2nd backup, it will have wiped ROM (no data and will need to set up phone again). Hope that make sense.

Yeah that's what I want, I want to go back to that clean clean rom, I don't need my user data
Sent from my SGH-M919 using xda app-developers app

Then don't restore a backup for that. Just reflash the rom.
Sent from my SGH-M919 using XDA Premium 4 mobile app

marcoxx626 said:
Why do you backup twice? And why would you restore just the system partition? You might as well just reflash the rom so you don't waste space having a system only backup.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Cause I'm OCD when comes to things like this, seriously lol. I move all the backups to the external SD and my computer lol. So not too worried about taking up space. I just want to see if everything is working normally with the clean stock rom. I.e. Able to send MMS. Read and write to ext SD properly.
Sent from my SGH-M919 using xda app-developers app

shengwang917 said:
Cause I'm OCD when comes to things like this, seriously lol. I move all the backups to the external SD and my computer lol. So not too worried about taking up space. I just want to see if everything is working normally with the clean stock rom. I.e. Able to send MMS. Read and write to ext SD properly.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
Well if you just want to go back to a fresh clean install there's no point in restoring a backup. Just reflash the rom bro. Any kernel changes or system app changes will still be there if you restore a system backup but won't be there if you reflash the rom (after doing full wipe that is).
Sent from my SGH-M919 using XDA Premium 4 mobile app

marcoxx626 said:
Well if you just want to go back to a fresh clean install there's no point in restoring a backup. Just reflash the rom bro. Any kernel changes or system app changes will still be there if you restore a system backup but won't be there if you reflash the rom (after doing full wipe that is).
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This is it right ? http://forum.xda-developers.com/showthread.php?t=2267895 , I think there is a Odin back to stock thread on here too
Sent from my SGH-M919 using xda app-developers app

shengwang917 said:
This is it right ? http://forum.xda-developers.com/showthread.php?t=2267895 , I think there is a Odin back to stock thread on here too
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
Ok, now you lost me. What is your ultimate goal in this? Back to complete stock like out of the box?
Sent from my SGH-M919 using XDA Premium 4 mobile app

marcoxx626 said:
Ok, now you lost me. What is your ultimate goal in this? Back to complete stock like out of the box?
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sorry lol, yeah i want to go back to right out of the box stock.
Sent from my SGH-M919 using xda app-developers app

Yeah follow that thread. Please hit thanks if I helped at all.
Sent from my SGH-M919 using XDA Premium 4 mobile app

After I flash unwizzed rom in aroma after it installs everything it says assert failed : package_extract_file("boot.img","/temp/boot.img") ?? It boots the Samsung Galaxy S4 screen then turns off then back on then back into recovery.. been doing this for alot of ROMs i try to flash

shengwang917 said:
The twrp has the system wipe option. I don't see that with Cwm, just factory rest/data, and the two caches
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
For cwm:
Mounts/Storage - Mount/System.
Sent from my SGH-M919 using Tapatalk 4

Robdizz said:
After I flash unwizzed rom in aroma after it installs everything it says assert failed : package_extract_file("boot.img","/temp/boot.img") ?? It boots the Samsung Galaxy S4 screen then turns off then back on then back into recovery.. been doing this for alot of ROMs i try to flash
Click to expand...
Click to collapse
Not sure what that could be. Did you check the md5?
Sent from my SGH-M919 using XDA Premium 4 mobile app

I've been asking everyone it does this on alot of roms i flash the only one that worked was Alpha 5.0 but tried to go to 7.0 and did same thing. How do u check the Md5?

[Q] flashing a rom without bricking?

I cant flash a rom and have it work. I have tried several ROMS like aokp, jedi, smooth, jellybeans, etc and they almost always brick. Jedi worked but google services crashed back to back to back to the point where i couldnt even use the phone. does anyone know of a 4.3 rom that works on att sgh-i317?? i basically went down the list on galaxynote2root.com and tried them all but no success.
I have root, have TWRP installed and flash the rom and it bricks. i factory reset first, then install and nothing.
any ideas?

All of the roms on this forum work.. What are your exact steps?
Sent from my SAMSUNG-SGH-I317 using xda app-developers app

Kreateablaze said:
All of the roms on this forum work.. What are your exact steps?
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
Have they been tried on sgh-i317?
I did these exact steps:
Rooted phone and installed TWRP recovery
put AOKP Rom on SD card and booted into recovery mode
Wiped/Factory reset through recovery
rebooted into recovery
installed AOKP ROM
booted and bricked- hangs at "X" aokp bootup screen

Have you installed gapps after flashing an aosp rom? I am running carbon rom right now... Earlier today I was on aokp. I have used them all and I have a I317. An att note 2
Sent from my SAMSUNG-SGH-I317 using xda app-developers app

Kreateablaze said:
Have you installed gapps after flashing an aosp rom? I am running carbon rom right now... Earlier today I was on aokp. I have used them all and I have a I317. An att note 2
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
does not having the gapps installed prevent the phone from booting? ive booted a rom before without gapps and it booted.
was there something wrong with my steps? did you use the aokp milestone or nightlies? where did you get the carbon rom? its all good?

I used the latest aokp nightly. And right now I'm running the newest carbon nightly. I got it from the op of the carbon thread.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app

Kreateablaze said:
I used the latest aokp nightly. And right now I'm running the newest carbon nightly. I got it from the op of the carbon thread.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
What were your steps? what recovery were you using? im just so confused why my phone bricks every time

I'm using the latest version of twrp recovery. Try updating it?
Sent from my SAMSUNG-SGH-I317 using xda app-developers app

Download your rom and gapps again using a PC...
Then place the files to your SD using a card adapter if no USB connection is possible...
Then fully wipe the device again from within the latest version of TWRP recovery and flash the new downloads ...
You may have a bad flash ...and you are not bricked...g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

gregsarg said:
Download your rom and gapps again using a PC...
Then place the files to your SD using a card adapter if no USB connection is possible...
Then fully wipe the device again from within the latest version of TWRP recovery and flash the new downloads ...
You may have a bad flash ...and you are not bricked...g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I did those exact steps and it did not work. i tried flashing pac man rom the last time and it got stuck in a boot loop too. I think there are some files that are corrupt or some temp files somewhere that are preventing a successful flash. my binary flash count was 9. and that was just on this run, ive tried flashing several times before. each time the only way to recover it is hooking the phone up to a pc and using kies to flash back to stock firmware. this sucks.

What version of twrp are you using? I have never had this issue you are having and I have flashed every rom on this forum for our device.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app

igotta67bug said:
I did those exact steps and it did not work. i tried flashing pac man rom the last time and it got stuck in a boot loop too. I think there are some files that are corrupt or some temp files somewhere that are preventing a successful flash. my binary flash count was 9. and that was just on this run, ive tried flashing several times before. each time the only way to recover it is hooking the phone up to a pc and using kies to flash back to stock firmware. this sucks.
Click to expand...
Click to collapse
9 counts ??
Uh....yeh...not right ...
Have you messed with device partitions in ODIN ??
If so...something is definitely wrong ...
At this point ...you may want to consider a full return to stock and allow the PIT to properly restore your partitions..
Just follow the return to stock guide (sticky )...in the general section ..
Once restored to stock with a corrected flash counter you can begin again using CF auto root as your root method..
It sounds as if you have root issues and possible partition damage...
One other step you can try first is to boot into download mode and re-root using CF...
That may help....but certainly won't hurt anything...then attempt a clean flash again..
If it fails ...then the return to stock and rooting again seems prudent ...g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

Ok ill try that. When I do the sticky method is that different than using kies to flash to stock? Kies is supposed to wipe everything and reload stock firmware. I agree the partitions are corrupt somewhere
Sent from my SAMSUNG-SGH-I317 using xda app-developers app

igotta67bug said:
Ok ill try that. When I do the sticky method is that different than using kies to flash to stock? Kies is supposed to wipe everything and reload stock firmware. I agree the partitions are corrupt somewhere
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
Are u wiping data and system as well in recovery. If you're running TW and u switch to AOSP without wiping everything.....the results most likely wouldn't b pretty
Sent from my SAMSUNG-SGH-I317 using Xparent Skyblue Tapatalk 2

I'm doing a factory reset--> "swipe to wipe". Do I need to do something else?
Sent from my SAMSUNG-SGH-I317 using xda app-developers app

Kies is not the method I use in returning to stock...as I don't trust it..
Odin is my first choice ...
Using Odin to flash a factory rom will wipe everything as well ...and is far more reliable ...IMHO...g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

gregsarg said:
9 counts ??
Uh....yeh...not right ...
Have you messed with device partitions in ODIN ??
If so...something is definitely wrong ...
At this point ...you may want to consider a full return to stock and allow the PIT to properly restore your partitions..
Just follow the return to stock guide (sticky )...in the general section ..
Once restored to stock with a corrected flash counter you can begin again using CF auto root as your root method..
It sounds as if you have root issues and possible partition damage...
One other step you can try first is to boot into download mode and re-root using CF...
That may help....but certainly won't hurt anything...then attempt a clean flash again..
If it fails ...then the return to stock and rooting again seems prudent ...g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
OK, so i followed these steps perfectly and it did not work. GOt Stuck in a boot loop again. something is corrupt. i used the latest version of clockwork mod and tried to install the latest AOKP nightlies. :crying:

Alright ...
Do you mean that you returned to stock ??
And have rooted again ...??
If yes ..we can dig deeper ...and if not ...proceed with full unroot...g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

I used the sticky on turning your phone back to stock which used odin. I followed that list perfectly which said to flash stock using odin, root using cf then using triangle away, then super user to fully unroot. Then I installed clockword mod recovery, booted to recovery mode, cleared all cache and davlik and factory reset again, then installed the aokp and it got stuck in a boot loop
Sent from my SAMSUNG-SGH-I317 using xda app-developers app

Here's what I do with twrp when flashing a rom.
Go to wipe menu and then advanced wipe and select dalvik, cache, data, system and internal(optional). I do it three times to make sure. then flash your rom with gapps (if aosp)

Cannot complete reboot after flashing Rom

Good day fine community.
My Galaxy S3 i747M(Rogers) stays stuck @ Galaxy S3 screen after flashing this ROM S3Rx 3.0 TouchWiz 4.3 MJB (1-27-14) Full AROMA.
1. First succesfully flashed 4.3 bootloader and MK5 modem from within a 4.1 ROM
2. Then used TRWP, full wipe, formatted internal sd, flashed ROM and loaded well.
3. Then attempted a Nandroid, which for some reason stayed almost an hour in the "backing up system data", so I cancelled it when the "cannot finish" message appeared.
4. Then rebooted, and now stays stuck in Galaxy S3 screen.
I redid 1, 2 and 4, and still stuck, even if I let the phone rest for more than 10 minutes.
For the life of me, it seems to be a bootloader issue, but I am unsure.
Anyone has any idea what I did wrong?
Thank you.

Try wipe of /system and all other wipes that you can apply. These are under the advanced section of your recovery
This will wipe your whole phone. Then try and reboot
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Reboot into what? Everything's wiped.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app

Builtnoob, did that. My sd card was fully wiped, as well as cache and dalvik. Thanks for the input.
Sent from my SGH-I747M using XDA Premium 4 mobile app

Shortydogg, once i flashed and was in the launcher, and alk was working fine, I rebooted in to recovery to do nand. Even if the nand was uncuccessfull, i should still be able to boot into the rom, since it was already running. That is my question: how come it stays stuck at boot. Thx for looking into it.
Sent from my SGH-I747M using XDA Premium 4 mobile app

Usually first boot takes a good half hour at times. Give it some time. However this could be due to a faulty flash. Or some corruption of data. Use twrp to mount your internal memory. Then redownload the ROM and reflash .
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Did you format the internal SD or did you format the system, data, and cache from recovery?

audit13, I formatted everything but my ext sd card. Tonight I will try again, this time with fresh download and wiping cache and dalvik after flashing, before booting, and will report back. Thanks guys.
Sent from my SGH-I747M using XDA Premium 4 mobile app

Me said:
audit13, I formatted everything but my ext sd card. Tonight I will try again, this time with fresh download and wiping cache and dalvik after flashing, before booting, and will report back. Thanks guys.
Sent from my SGH-I747M using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Don't forget the /system wipe as a lot of the stock ROMs do need it
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

buildnoob, 10-4.
Sent from my SGH-I747M using XDA Premium 4 mobile app

An easier fix may be to just flash a pre-rooted 4.3 ROM that is made for the Bell, Telus or Rogers version of your phone. Then, load a custom recovery to flash custom ROMs.
http://forum.xda-developers.com/showthread.php?t=1739426

Buildnoob, thanks for the info. I did fresh install and wiped cache and dalvik after flash and now all is well.
Thanks guys for the help.

DroidArt said:
buildnoob, 10-4.
Sent from my SGH-I747M using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Test reply