Database Info

Flashing To 2.1(stock) from Cognition w/vodoo WILL CAUSE BRICK!

Hey everyone, I have desided to create a FYI post to anyone considering flashing back to stock 2.1(Eclair) using Odin if you are currently running Cognition(Froyo) roms. I have attempted flash back to stock on 4 phones(Samsung Captivate) with the same result(failing during the restoing of factoryrfs); causing the imfamous orange dump screen. This is a very serious issue which should be looked at by the devs. I am not trying to start a war or anything but the results from flashing back to 2.1 can almost always be reproduced(a bricked phone)

Atheistnofaith said:
Hey everyone, I have desided to create a FYI post to anyone considering flashing back to stock 2.1(Eclair) using Odin if you are currently running Cognition(Froyo) roms. I have attempted flash back to stock on 4 phones(Samsung Captivate) with the same result(failing during the restoing of factoryrfs); causing the imfamous orange dump screen. This is a very serious issue which should be looked at by the devs. I am not trying to start a war or anything but the results from flashing back to 2.1 can almost always be reproduced(a bricked phone)
Click to expand...
Click to collapse
thats funny. i have run every froyo rom available to us, i9000 w/voodo, ulf, cognition with voodoo, and i have yet to brick my phone. i flash to stock between EVERY new rom.
there is something you are not doing right. did you disable voodoo before attempting to flash stock?

Atheistnofaith said:
Hey everyone, I have desided to create a FYI post to anyone considering flashing back to stock 2.1(Eclair) using Odin if you are currently running Cognition(Froyo) roms. I have attempted flash back to stock on 4 phones(Samsung Captivate) with the same result(failing during the restoing of factoryrfs); causing the imfamous orange dump screen. This is a very serious issue which should be looked at by the devs. I am not trying to start a war or anything but the results from flashing back to 2.1 can almost always be reproduced(a bricked phone)
Click to expand...
Click to collapse
I always flash back to JF6 via Odin 1 click before going to any new rom. It does not matter for whether voodoo is disabled or not because Odin 1 click repartitions everything to RFS. Also, the orange screen is not that big a deal. Reflashing JF6 via Odin once more is the solution.
If you continually have these problems when flashing to JF6:
1. Try re-downloading Odin 1 click.
2. Follow correct procedure for Odin flashing (Read OP's)
3. Try other USB ports
4. Uninstall and install fresh drivers that match your operating system (eg. 32bit/64bit)
Further, this post is not for the development section, but belongs in General or Q&A.

I think even without voodoo disabled, flashing back to stock will break voodoo and it wont be functional anymore. I personally never disable voodoo when flashing back to stock. You need to Master Clear after flashing back to stock.
Never bricked my phone flashing all the time.

I do it all the time! Never bricked my phone... EVER! The closest I came was when I tried flashing to another rom with CVM with voodoo still enabled. got stuck in loop, but to rectify the situation I "flashed back to stock with one click ODIN" and all was well.

i9000 is not the captivate argh different kernel

Odin gave me Blue, Light Blue, Orange, White and Black Screens of Death, no matters if i had Voodoo or not..
I think it sometimes hangs without any reason, but the drivers/program itself..
Thanks God my phone doesn't have the Bootloader's 3 Button issue..

Atheistnofaith said:
i9000 is not the captivate argh different kernel
Click to expand...
Click to collapse
I believe he was referring to i9000 roms. I have never had any issues flashing back to stock from any rom. It has to be something you are doing. Might be the answer you want but probably going to be the most common answer you will get. Check your steps.

Atheistnofaith said:
i9000 is not the captivate argh different kernel
Click to expand...
Click to collapse
i never said i am running an i9000 HARDWARE, i said ROMS
like everyone else has said. its something YOU are doing wrong. please dont spread FUD

This thread needs to be deleted. It's patently false.
Sent from my Captivate.

Sometimes its not the arrow....
its the Indian. The majority of the people who flash follow the same procedure with no issues. While its nice of you to try to caution folks, maybe you need to look at what you're doing instead of jumping to conclusions.

MikeyMike01 said:
This thread needs to be deleted. It's patently false.
Sent from my Captivate.
Click to expand...
Click to collapse
Agreed 10char

MikeyMike01 said:
This thread needs to be deleted. It's patently false.
Sent from my Captivate.
Click to expand...
Click to collapse
AGREED!
one person has problems with multiple devices=look for the common denominator.

if not deleted then at least OP change the title because its misleading.

i wouldn't be so fast to poopoo the post. I had similar issues with two of my previous captivates. Both times Odin froze on factory and bricked me to an unrecognizable state and both times I had some kind of lagfix I didn't disable. Right now I just write it off as coincidence as both times i didn't necessarily do things in the right order but there may be some legs to flashing some phones to stock with lagfixes. It's possible but the best thing to do is before flashing to stock remove and disable any lagfixes and you'll never have the problem
and is this a general thread or dev?

Atheistnofaith said:
Hey everyone, I have desided to create a FYI post to anyone considering flashing back to stock 2.1(Eclair) using Odin if you are currently running Cognition(Froyo) roms. I have attempted flash back to stock on 4 phones(Samsung Captivate) with the same result(failing during the restoing of factoryrfs); causing the imfamous orange dump screen. This is a very serious issue which should be looked at by the devs. I am not trying to start a war or anything but the results from flashing back to 2.1 can almost always be reproduced(a bricked phone)
Click to expand...
Click to collapse
I have flashed i9000 roms, kernels, modems, themes, and anyting else imaginable, with and without voodoo, with and without master clear, and have NEVER gotten the orange death screen before, during, or after Odin flashing back to stock. I've flashed just about every iteration of the Cognition FroYo roms and have never had an issue.
Re-download odin, maybe? But it's not an issue with Cognition.

Belaflek said:
i wouldn't be so fast to poopoo the post. I had similar issues with two of my previous captivates. Both times Odin froze on factory and bricked me to an unrecognizable state and both times I had some kind of lagfix I didn't disable. Right now I just write it off as coincidence as both times i didn't necessarily do things in the right order but there may be some legs to flashing some phones to stock with lagfixes. It's possible but the best thing to do is before flashing to stock remove and disable any lagfixes and you'll never have the problem
and is this a general thread or dev?
Click to expand...
Click to collapse
Yo only need to disable voodoo when you are upgrading from one version to another but when you are flashing back to stock it will repartition everything for you back to RFS.

I've run all the Froyo kernels, ROMs, even i9000 Froyo ROMs on the Froyo reoriented kernel, with or without voodoo, it doesn't matter, and I flash back to stock all the time. Odin wipes everything out, it doesn't matter what you are running.

the "factoryfs.rfs" screen-o-death is a well known problem. fortunately, factoryfs.rfs doesn't really matter (it's only the /system partition), your phone just won't boot. Likely you'll hit the phone--!--PC screen, but as long as you have 3 button recovery working, you're safe.
this issue crops up when you have a bad USB connection to your phone. I'm willing to bet 90% of the people with this problem are running outdated hardware (made before 2006 or so) that can't keep up with ODIN's pace or are using a desktop and not plugging the USB into a port connected to the motherboard (you should be using one on the back of the tower)

MikeyMike01 said:
This thread needs to be deleted. It's patently false.
Sent from my Captivate.
Click to expand...
Click to collapse
posts like this... littering the dev forum

Galaxy Mini Disaster!!

Hi All,
Iv had a disaster with me 3 month old Galaxy Mini, I got the latest Android magazine which talked about installing custom ROM's so I downloaded ROM Manager which the recommended, and tried to perform a ROM Backup firstly it asked for my phone model which it didn't say anything about, anyway I accidently hit the wrong phone model, it then asked for a backup name which, I OK'd it, the phone should reboot into recovery mode and perform the backup, mine shutdown and now I cant turn it on. It was plugged in when I did all this, and I left it plugged in when it shutdown. I dont even get the charging icon when its off.
have I bricked my phone?
PLEASE HELP?

Oh boy, looks like you got a problem...
You'll get more help here: http://forum.xda-developers.com/forumdisplay.php?f=1311
In all probability, you will have to go to samsung service centre, and they will replace the processor...

bugs78 said:
Hi All,
Iv had a disaster with me 3 month old Galaxy Mini, I got the latest Android magazine which talked about installing custom ROM's so I downloaded ROM Manager which the recommended, and tried to perform a ROM Backup firstly it asked for my phone model which it didn't say anything about, anyway I accidently hit the wrong phone model, it then asked for a backup name which, I OK'd it, the phone should reboot into recovery mode and perform the backup, mine shutdown and now I cant turn it on. It was plugged in when I did all this, and I left it plugged in when it shutdown. I dont even get the charging icon when its off.
have I bricked my phone?
PLEASE HELP?
Click to expand...
Click to collapse
A lot of reading is neede when trying to flash custom roms on any phone.
I think you better had done everything by yourself in recovery (step by step), so no mistake can be made that way.
Maybe you can get some help in Galaxy Mini section.
I guess you cant even power it in download mode?

Alpha120 said:
A lot of reading is neede when trying to flash custom roms on any phone.
I think you better had done everything by yourself in recovery (step by step), so no mistake can be made that way.
Maybe you can get some help in Galaxy Mini section.
I guess you cant even power it in download mode?
Click to expand...
Click to collapse
I honestly don't think he was rooted, or had a custom recovery.

You must flash the tass.ops file via odin ( computer program ) and then download and install ( again via odin ) the stock or a custom rom.
WARNING: To successfully unbrick your galaxy mini, you must have the odin for samsung galaxy mini GT-S5570. Odin for other devices will probably destroy your device at all.
If you want links and more instructions, you can sent me a pm.
If I helped you, don't forget to press the Thanks button.
Sent from my GT-S5570 using xda premium

Thanks, so will samsung need to replace the processor as stated earlier, or can this be repaired by a decent phone repair shop?
Sgmaster said:
You must flash the tass.ops file via odin ( computer program ) and then download and install ( again via odin ) the stock or a custom rom.
WARNING: To successfully unbrick your galaxy mini, you must have the odin for samsung galaxy mini GT-S5570. Odin for other devices will probably destroy your device at all.
If you want links and more instructions, you can sent me a pm.
If I helped you, don't forget to press the Thanks button.
Sent from my GT-S5570 using xda premium
Click to expand...
Click to collapse

Have you even read Sgmaster's post??
You need to flash a stock rom using ODIN, no need to take it to any service if it boots into download mode.

Alpha120 said:
Have you even read Sgmaster's post??
You need to flash a stock rom using ODIN, no need to take it to any service if it boots into download mode.
Click to expand...
Click to collapse
Sgmaster said:
You must flash the tass.ops file via odin ( computer program ) and then download and install ( again via odin ) the stock or a custom rom.
Click to expand...
Click to collapse
I don't know how is he going to flash tass.ops with odin, and then separately flash a stock rom...
Last I checked, you couldn't flash an odin partition script by itself, since that script is for odin's use on the phone and not for the phone itself...
Is it different for mini?
Typed using a small touchscreen

I think Sgmaster meant to load .ops file and then, flash the stock rom.
For SGS+ is ariesve.ops, I flashed with odin a few times...

Right this. First load the tass.ops file via odin and then flash a rom throught odin or clockworkmod recovery mode.
If I helped be sure to press THANKS button.
Sent from my GT-S5570 using xda premium.

Always read the threads first if not a vid is even better

*sigh*
This is why articles shouldn't say, "IT'S SO EASY, ANYONE CAN DO IT!"
No, it's not. It's easy to f*ck up and brick your phone is what it is. Don't even bother joining XDA if you don't have the patience to read. Nowadays all we get are people who join after messing up their phones, begging us to perform some over-the-internet sorcery to fix it. We're not magicians. We're people. We don't exist to serve you. We have lives.
This isn't pointed directly at the OP.

Product F(RED) said:
*sigh*
This is why articles shouldn't say, "IT'S SO EASY, ANYONE CAN DO IT!"
No, it's not. It's easy to f*ck up and brick your phone is what it is. Don't even bother joining XDA if you don't have the patience to read. Nowadays all we get are people who join after messing up their phones, begging us to perform some over-the-internet sorcery to fix it. We're not magicians. We're people. We don't exist to serve you. We have lives.
This isn't pointed directly at the OP.
Click to expand...
Click to collapse
Thats why no matter what, Im still on Stock Froyo.

I'm not saying don't root. It's not hard to root, but it is easy to brick your phone. By brick, I mean permanently. As long as you have recovery mode or download mode, you're good. But my point is read, read, read before you even download a ROM.

I did successfully root my fine no problems, and read about ROM's but, think I should have read more before attempting.
I`m guilty of getting misty eyed over the thought of something new and flashy not seen before.
I have been on here a while reading, not posting and i think i`ll check out here before attempting again.
anyway I wimped out and sent it back to Samsung to be repaired under its warranty, I know I could probably fix it with the help of you guys, but if I dont need to have the hassle.
But, if I was to recover myself I know you have said use odin I have downloaded it and had a look. Would I load the software then attempt to turn it on with the Home, down volume, and on buttons it should then boot into recovery mode. Is that correct?
Thanks All for your time

My tab is in danger of brickbug HELP please

GT- P6210
So i used Chainfires apk to check to see if i'm in danger of the hard brick bug.
And it has said I'm at risk!, so i have ICS on my tab but am too scared to use it!
What are my options?
Should i just keep on using it and keep my fingers crossed?
My Noob guess is to go back to Honeycombe?
(download honeycomb rom tar, and flash via Odin?)

@riverboat2001
please check this thread. thanks.
http://forum.xda-developers.com/showthread.php?t=1818638
and also this link.
http://forum.xda-developers.com/showthread.php?p=27074278

aperture said:
@riverboat2001
please check this thread. thanks.
http://forum.xda-developers.com/showthread.php?t=1818638
and also this link.
http://forum.xda-developers.com/showthread.php?p=27074278
Click to expand...
Click to collapse
Hi, thanks for replying, i had already read that first post, but it doesn't seem to have an outcome.
As for the second one is it still relevant information if it's for the N7000?
The guy is saying avoid Samsung ROM's completely, what rom should i be using then?
Lastly do you know if it's safe to do a wipe/reset from within CWM ?
Cheers

riverboat2001 said:
Hi, thanks for replying, i had already read that first post, but it doesn't seem to have an outcome.
As for the second one is it still relevant information if it's for the N7000?
The guy is saying avoid Samsung ROM's completely, what rom should i be using then?
Lastly do you know if it's safe to do a wipe/reset from within CWM ?
Cheers
Click to expand...
Click to collapse
As long as you are using cm, I don't think it will be a problem. I will never go back to official. The problem stems from an issue with the stock recovery from Samsung. So in short, the devs are aware of the issue, but Samsung doesn't seem to care. As long as you are running the current cwm, and the dev isn't an idiot, you shouldn't have a problem. (No offense aorth and locerra, I know you're aware)
Sent from my Galaxy Tab 7 Plus

riverboat2001 said:
GT- P6210
So i used Chainfires apk to check to see if i'm in danger of the hard brick bug.
And it has said I'm at risk!, so i have ICS on my tab but am too scared to use it!
What are my options?
Should i just keep on using it and keep my fingers crossed?
My Noob guess is to go back to Honeycombe?
(download honeycomb rom tar, and flash via Odin?)
Click to expand...
Click to collapse
the thing is, if you go into recovery mode (hold power and volume up during boot) and then you see something like "recovery 3e" on the screen. THEN you have a problem.. it means you are on stock ICS with the stock Recovery and IF you do the "factory reset/wipe" in that recovery mode. your TAB is a goner..
then you get a linux system, get heimdall go to this thread
http://forum.xda-developers.com/showthread.php?t=1785862
and follow all instructions untill you have a non-stock (no 3e) recovery on your tab.
then your tab (*as far as other people say) is safe. then you can wipe/flash/backup and do whatever you want with a relatively (lower) risk than before..

wingie6200 said:
the thing is, if you go into recovery mode (hold power and volume up during boot) and then you see something like "recovery 3e" on the screen. THEN you have a problem.. it means you are on stock ICS with the stock Recovery and IF you do the "factory reset/wipe" in that recovery mode. your TAB is a goner..
then you get a linux system, get heimdall go to this thread
http://forum.xda-developers.com/showthread.php?t=1785862
and follow all instructions untill you have a non-stock (no 3e) recovery on your tab.
then your tab (*as far as other people say) is safe. then you can wipe/flash/backup and do whatever you want with a relatively (lower) risk than before..
Click to expand...
Click to collapse
Wow, thanks so much for taking the time to offer your advice.
I only have myself to blame for getting into this pickle! After Flashing so many different ROM's on loads of devices i just got a bit blaiz'e
Last night i did a wipe and factory reset through CWM and it all went well, so my question is, giving that i know i'm at risk, i can see three options,which is the "safest"
1/ Put tab away and don't use it until Samsung release a fix we can use
2/ Keep using the tab, but have that worrying niggle in the back of my mind
3/ Follow the post above and carry out the suggested procedure outlined above? (is it 1000% safe?
Can i assume that if i go as far as recovery mode via the ICS version to see the "recovery 3e" but don't wipe/factory reset i'm safe?
And consequently if i DON'T see that i would be safe to go ahead?
I do feel as if I'm sitting on a time-bomb here
(years ago i would have spent weeks messing around with this sort of thing, but as a middle aged housewife thats always on the go, i don't have the time, I just like to get my stuff working fast and bloatware free and i'm happy!)
Once again thanks for your input.

lol cant guarantee the 1000% safe part (since the offending code is in part coming from samsung) but people are aware of it / working to fix it and all non stock stuff is most probably safe. the CWM 6.0.1.0 definitely is, just used it myself.
and these things are kinda random (if all posts are to be believed) so i would just use the tab normally and worry about it much.. reports also say that samsung does repair these bricked tabs under warranty in case the unthinkable does happen.
and its not a time bomb :laugh:! (although there would probably be an app for that somewhere..)

I think the issue is only with the ics 3e recovery, not the hc one. Clockwork is fine, at least the newest one, not sure about the one Gary posted
Sent from my myTouch 4g via Tapatalk

ringnutz said:
I think the issue is only with the ics 3e recovery, not the hc one. Clockwork is fine, at least the newest one, not sure about the one Gary posted
Sent from my myTouch 4g via Tapatalk
Click to expand...
Click to collapse
What exactly trigger the brick bug? I already use the ICS stock recovery to do a wipe/factory reset your for my tab a couple of times and all was fine. I just was lucky? I have the second ICS update for the GT-P6210. Is this model affected? I mean, is someone with this model already trigger the brick bug?
Sorry for so many questions, thanks.

Kuniokun said:
What exactly trigger the brick bug? I already use the ICS stock recovery to do a wipe/factory reset your for my tab a couple of times and all was fine. I just was lucky? I have the second ICS update for the GT-P6210. Is this model affected? I mean, is someone with this model already trigger the brick bug?
Sorry for so many questions, thanks.
Click to expand...
Click to collapse
Yeah, I did.. happened the first time
Sent from my myTouch 4g via Tapatalk

Brickbug is caused by ****ty flashing firmware on some of our devices.
No danger with cwm 6.0.1.0 from aorth. We r safe!
Sent from my GT-P6200 using xda app-developers app

[Q] Was rooted - took OTA - hanging at white Verizon logo screen

I was rooted and made the mistake of accepting the latest OTA update, which I assume was the new and devious 4.3. The update process seemed to work fine, but on reboot, phone is now freezing at the white Verizon logo screen.
My boot sequence looks like this: "SAMSUNG ([lock pic] Custom)" -> "SAMSUNG GALAXY S III" on black -> Swirly SAMSUNG logo on black -> Verizon animation on white -> HANG at indefinitely repeating few-frame loop animation of shining Verizon logo on white background.
I can get to Download mode - it looks like this:
ODIN MODE
PRODUCT NAME: SCH-I535
CUSTOM BINARY DOWNLOAD: Yes (2 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
*NO* mention of Warranty Bit.
Does this mean I am still on 4.1.2 and not dreaded 4.3 Knox? I don't want to screw up and accidentally brick this thing.
Unfortunately I have crappy notes from my original rooting, so I don't know if I had a simple root or custom ROM or custom bootloader or what. I know I have CF-Auto-Root-d2vzw-d2vzw-schi535.tar.md5, VRBMB1_Bootchain.tar.md5, and VRALEC.bootchain.tar.md5 in my work folder, and I was only rooting so I could use SGS3 Easy UMS so I likely did whatever method was needed for that.
How can I get back to functional? Stock or custom, I don't care, but with all the bricking dangers I'm reading about after this new OTA update I just want to proceed extra carefully. Also I'd really like to not have to wipe the phone with a factory reset or anything like that.
Thanks for your help!

scrowdid said:
I was rooted and made the mistake of accepting the latest OTA update, which I assume was the new and devious 4.3. The update process seemed to work fine, but on reboot, phone is now freezing at the white Verizon logo screen.
My boot sequence looks like this: "SAMSUNG ([lock pic] Custom)" -> "SAMSUNG GALAXY S III" on black -> Swirly SAMSUNG logo on black -> Verizon animation on white -> HANG at indefinitely repeating few-frame loop animation of shining Verizon logo on white background.
I can get to Download mode - it looks like this:
ODIN MODE
PRODUCT NAME: SCH-I535
CUSTOM BINARY DOWNLOAD: Yes (2 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
*NO* mention of Warranty Bit.
Does this mean I am still on 4.1.2 and not dreaded 4.3 Knox? I don't want to screw up and accidentally brick this thing.
Unfortunately I have crappy notes from my original rooting, so I don't know if I had a simple root or custom ROM or custom bootloader or what. I know I have CF-Auto-Root-d2vzw-d2vzw-schi535.tar.md5, VRBMB1_Bootchain.tar.md5, and VRALEC.bootchain.tar.md5 in my work folder, and I was only rooting so I could use SGS3 Easy UMS so I likely did whatever method was needed for that.
How can I get back to functional? Stock or custom, I don't care, but with all the bricking dangers I'm reading about after this new OTA update I just want to proceed extra carefully. Also I'd really like to not have to wipe the phone with a factory reset or anything like that.
Thanks for your help!
Click to expand...
Click to collapse
You got lucky. For some reason your boot chain didn't flash so it's still unlockable.
You need to flash this file in Odin:
http://www.androidfilehost.com/?fid=23134718111254196
Using section 5 of this guide:
http://forum.xda-developers.com/showthread.php?t=1762709
Then root and unlock with casual:
http://forum.xda-developers.com/showthread.php?t=2332825
Then download ez unlock 1.2 and verify it's unlocked.
Then you're good to go again. Install a custom rom and never accept an Ota again.
As far as wiping your phone goes, you can't really do much about that, this is pretty much a last resort.
Sent from my SCH-I535 using Tapatalk 2

It's a nice write up Badusername..:good:
I just want to add that if you want to keep stock rooted, just make sure you disabled OTA. Like Badusername mentioned if you decided to flash custom rom then you don't have to worry about OTA.

If that's everything in download mode, then you are still on 4.1.2. If you want to try retaining your /sdcard data, then you could try Odin flashing the no-wipe VRBMB1 image.
If you would like to start clean and wipe away /sdcard, then Odin flash this VRBMF1 4.1.2 stock image. You would need to root and unlock in both cases. DO NOT accept the 4.3 OTA in either case.
Edit: ninja'd lmao...badly

Thanks! I am operational again with the No-Wipe flash. Whew!
Unfortunately, it looks like I lost all my text messages though. That was one of the main things I had been hoping to preserve, to keep a record of some conversations. Unless there's something I'm missing and they might still be lurking somewhere?
My photos survived and it looks like apart from a few settings it's mostly unwiped. Cool! Glad I didn't ruin it. Now I can try a custom 4.3 or something else if I want, but for now I'm just glad to have it working again.

This happened to me after flashing VZW-I535VRUCML1-20131220083128 instentionally to return back to stock.
after flashing with odin in PDA mode, the samsung 'custom' screen came on then the loop on the white logo.

blueblur said:
This happened to me after flashing VZW-I535VRUCML1-20131220083128 instentionally to return back to stock.
after flashing with odin in PDA mode, the samsung 'custom' screen came on then the loop on the white logo.
Click to expand...
Click to collapse
Did you boot into recovery and do a factory reset?
Sent from my SCH-I535 using Tapatalk 4

SlimSnoopOS said:
Did you boot into recovery and do a factory reset?
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
When? Before flashing stock? No. After? No, but if I can get into recovery, I will.
edit:::
went into recovery after flashing odin image, that did the trick. thank you.
still showing 'custom' when starting up

blueblur said:
When? Before flashing stock? No. After? No, but if I can get into recovery, I will.
edit:::
went into recovery after flashing odin image, that did the trick. thank you.
still showing 'custom' when starting up
Click to expand...
Click to collapse
No problem. Idk why custom would be there unless you tried flashing something pre-4.3 in Odin beforehand? Odin flashing the VRUCML1 tar would wipe everything else off the phone in terms of rom and root. It doesn't affect anything unless you plan on doing a warranty replacement.

SlimSnoopOS said:
No problem. Idk why custom would be there unless you tried flashing something pre-4.3 in Odin beforehand? Odin flashing the VRUCML1 tar would wipe everything else off the phone in terms of rom and root. It doesn't affect anything unless you plan on doing a warranty replacement.
Click to expand...
Click to collapse
I was trading it in to verizon for the note 3. i'm good to go now. thanks for your help!

scrowdid said:
Thanks! I am operational again with the No-Wipe flash. Whew!
Unfortunately, it looks like I lost all my text messages though. That was one of the main things I had been hoping to preserve, to keep a record of some conversations. Unless there's something I'm missing and they might still be lurking somewhere?
My photos survived and it looks like apart from a few settings it's mostly unwiped. Cool! Glad I didn't ruin it. Now I can try a custom 4.3 or something else if I want, but for now I'm just glad to have it working again.
Click to expand...
Click to collapse
Just a suggestion. I use an app in the play store called sms backup plus. It backs up your texts to your email.
https://play.google.com/store/apps/details?id=com.zegoggles.smssync
Sent from my SCH-I535 using Xparent ICS Tapatalk 2

Revert to stock

Phone:
Galaxy s4 (gti9505)
Network: Three.
Right. So I rooted my phone and flashed cyanogen mod 11. On 2 occasions I nearly had heart failure because I thought I'd bricked my phone. However I didn't and am successfully running the ROM no problems. The thing is I don't really like it and wish to go bk to stock. It goes without saying I did a nandroid back up but I kept getting an error while trying to restor using the nandroid backup and have been stuck with this ROM I don't like for a good month. I've read that I can revert to stock using Odin but am scared to do so as it was scary enough flashing this ROM yet alone undoing it.
Does anybody know of anywhere or anyone that could do this for me. I live in the uk, manchester.
Any help seriously apprexiayed.
Thanks guys.

Big Drew said:
Phone:
Galaxy s4 (gti9505)
Network: Three.
Right. So I rooted my phone and flashed cyanogen mod 11. On 2 occasions I nearly had heart failure because I thought I'd bricked my phone. However I didn't and am successfully running the ROM no problems. The thing is I don't really like it and wish to go bk to stock. It goes without saying I did a nandroid back up but I kept getting an error while trying to restor using the nandroid backup and have been stuck with this ROM I don't like for a good month. I've read that I can revert to stock using Odin but am scared to do so as it was scary enough flashing this ROM yet alone undoing it.
Does anybody know of anywhere or anyone that could do this for me. I live in the uk, manchester.
Any help seriously apprexiayed.
Thanks guys.
Click to expand...
Click to collapse
Yes you are right you need odin to flash stock firmware.....just download it from sammobile.com and flash it via odin and you are good to go......but you will lose root after flashing stock?
Hit thanks if it helped?
Sent from my GT-I9500 using Tapatalk