Database Users

[Q] Phone wont boot after attempting Voodoo Lag Fix

and I am not a happy camper right now. My phone is not bricked but I have tried everything imaginable to get it to boot up but no dice.
After I flashed the fix I couldnt boot past recovery and I couldnt but up into clockwork because I hate replace the update.zip with the the lag fix. So I used Odin to try to reflash back to stock without removing the lag fix (there was no way for me to).When Odin rebooted my phone and tried to wipe my data I realized it failed for some reason and then rebooted again. But it only got past the swirly S animation screen but the screen goes black after that. Cant get farther then that no matter what I do... Tried Odin multiple times but its the same result. Tried wiping data and cache manually through recovery but still not working.
Any suggestions?? Some quick facts that could help...
-I can get into recovery
-I can get into download mode
-I can use Odin
-Vibrant drivers are installed on my computer
-I have ADB installed

Ok I see theres a repartition option in Odin if I do that Im pretty sure ill be set if I check that since it will remove the lag fix but Ill end up losing all of my data. Is there any way for me to to copy the files in my internal sd card to my computer in the current state my phone is in??
Ok... tried mount USB storage but my computer isnt recognizing is it.

Nope, sorry. We don't really have a way to communicate with the file system unless the OS is booted and the proper drivers are loaded.
I guess if anything good comes of this it's that you know to back up often now though! You have to flash the "Eugene's Froyo that doesn't brick" rom, then flash back to stock JFD or JI6, but you sound pretty informed so you probably already knew that.

I see thats to bad, the Amon's recovery for the G1 allowed you to view files in it. But no I never knew that you should flash Eugene before going back to stock. I've flashed back to stock from Axura before with no problems before. Still this gives me some hope because Im sure the problem is the lagfix I tried and maybe it will play nicely with Eugene's ROM.
EDIT: And it worked!! Thanks bud just goes to show any little bit of info could make a difference Lost all my files though but oh well, lesson learned.

help(resolved)

Hey I just seriously screwed my self over bassicly I tried to get miui to boot from the samsung fascinate however when I installed it in cmr it spassed out then powered of then went to the bootloader and I get a red error message saying can't mount data or something so then I tried to reinstall Eco 3 Odin using Odin and it worked it booted but it says I have zero data on my phone and I can't install anything. I also tried the oneclick soft unbricker but it fails saying adb divers are not installed when they are. I'm doing this on my phones browser witch is the only thing that seems to be working right now I also tried a band restore but I got the same data error message.

Have you tried restoring to DL17 and then re-upgrading to 2.2?

And how about a good old odin flash?
In worst case, I would ask imnuts for the full odin package, or use a fascinate full odin package to get you off your feet, then reflash the modem, and recovery, then wipe In recovery cyan cwm... Then flash ec03
Sent from my SCH-I400 using XDA Premium App

wait wait, is this on a Continuum or Fascinate?

Nuckin said:
wait wait, is this on a Continuum or Fascinate?
Click to expand...
Click to collapse
He is on a Continuum, but you can use a fascinate Odin package to reformat partitions if they get messed up, then just reflash recovery and start fresh if you can get in then... That wasn't a really good thing though to suggest to a newcomer necessarily, so thank you for pointing that out

okay heres what happened firts i wanted to see if i could get the miui rom for the samsung fascinate to boot on the continuum there pretty much the same phone minus the ticker and screen size so i went into clockwork mod and wiped everything then went to install zip from sd card and clicked on the miui rom witch was the process we always used on the hero. then after i clicked on it, it started to install then my screen started shacking and my phone turned off. when i turned it back on it when to the bootloader and a red error message poped up saying
e:cant mount /dev/blockstill(invalid argument
and when i go to recovery it says the same thing when i try to wipe/restore nand it says the same thing. so at that point i powered off and went to download mode and reinstalled eco3 odin using pda mode on odin and it worked then it rebooted and i got to the set up screen and i got 2 force closes daily brefeing and something else i went ahead and skipped all that stuff and it loaded fine after that. however now for some reason it says i have zero system memory so i cant install any apps or save data however it does recognize my sd card but i cant install to sd card. so bassicly the phone functions just no internal memory. at this point i honestly dont know what to do everything on the hero was simple and straight forward and we never ran into these kind of problems. ive also tried to restore my nands and reinstall clockwork mod but still no dice. what i need to do now i guess is get the necessary files to go completely stock and see if that helps. and if someone could point me in the direction to those files i would really aprechiate it. oh and i tried the one click unbricker it sayed success but didnt really do anything.
oh and i know trying to install miui was stupid but i was just wanting to see if it would boot lol.

Download the PIT file in the Development forum, as well as the DL17 Odin package from the FAQ of the EC03 post I made. Flash the DL17 in PDA, with the PIT, and re-partition selected. After that, you should be back on DL17, and can do whatever you want from there.

huzzza!!!
thank god that worked thank yall so much i still cant believe that just happened but restoring the stock odin image worked and all is well. so i guess tommorow i can reroot and restore my nand.
once again thank yall for the help.

I survived the Encryption Unsuccessful error unscathed?!

I've been a stalker on here for a long time, as I've been interested in custom ROMs but I never pulled the trigger, until last night. My Vibrant has served me well for a many years, I bought it shortly after they came out. All I'd ever done to it was network unlock it so I could keep using it after I moved to the UK.
I've been toying with getting a new phone for a few months now so I decided why not try and flash a custom ROM and get ICS on my Vibrant, if I got the EU error and bricked it, oh well, I'd get a new phone. So I after much reading and research, studying the tutorials on here I went for it. I am vary tech and computer savvy. I build my own computers from scratch, I've flashed my routers and set up networks so I was pretty confident I could do this with the help of the forums here.
I've read every thread I can find on the EU on here and I know that the community needs as much info as possible to try and solve this bug, so I will try and be as specific as possible and list everything I did. But bear in mind, I'm new to this and this was my first time doing much of this so some things may be muddled as I was up til quite late messing with all this.
To start my phone was running 2.2 which was updated using Kies Mini. The only thing I'd ever done to it was network unlock, and for that all I did was find the file on the phone with the code and then enter it to unlock.
I decided to follow Woodrube's guide (http://forum.xda-developers.com/showthread.php?t=1464423)
I followed the guide to the "T".
1. Used Odin to flash back to stock 2.1, worked fine, phone booted back up and everything worked. Phone Data showed I was on 2.1.
2. I put Clockwork Recovery downloaded from Woodrube's sig block on my internal sdcard labeled as Update.zip
3. Created a folder called ICS on my internal sdcard. Found and downloaded CM7 from the forums here and dropped it into the ICS folder. Found and downloaded the ICS Passion ROM from the forums and dropped it into the ICS folder
4. Booted to recovery mode and did Reinstall Packages. It ran but brought me back to the blue recovery screen. so per Woodrube's guide I did it again and the second time it brought me to the green CWR recovery screen
5. I did wipe data/ factory reset
6. I did wipe cache
7. I went to advanced and did wipe dalvik cache
8. I went to mounts and storage and did format system
9. I went to install from sdcard and found the ICS folder I made and ran the CM7 fille I dropped there. It worked the first time and booted right up, I let it sit for about 5 mins waiting for the request to install my google password as Woodrube mentions, but it never appeared, so I moved on after 5-6 min of waiting.
10. I then booted back into recovery mode using the extended power button menu
11. I went to install from sdcard again and this time ran the ICS Passion file. It ran some text lines showed on the screen as id did somethings and then I sw a Random Offset error and a small hex string but then it said successfully installed but didn't leave the recovery screen. So i scrolled up to reboot system.
12. The phone rebooted, showed me the Passion splash screens and a progress bar which filled and completed, then showed a few other splash screens and then it booted up showing my signal strength bar and notifications bar. I thought YES! I did it and it worked. then the screen flashed, it showed a single multi-colored line horizontally across the middle of the screen and then flashed again and I was looking at the Encryption Unsuccessful screen.
13. I DID NOT PUSH THE RESET BUTTON, I set the phone aside and followed Woodrube's link to the Captivate Forums and read up on the error, read all of it, then searched the forums for more threads on the error and read all of those, then I Googled the error and read everything else I could find.
14. First i tried just shutting the phone down with the power button and then restarting it. I did this about 5-6 times. Every time it rebooted it showed me the Passion splash screens then boots up shows my notification bar and signal strength meter and the EU screen. That didn't work. I next tried rebooting 5 times without my external sd card installed. Same results
15. Next I decided to see if I had lost access to my internal sdcard as I had read about. I wasn't sure if I had because I had never pushed the EU screen reset button. So I booted into recovery mode, went to install from sdcard and my sdcard list popped up. I still had access to my internal sdcard.
At this point I was torn... do I stop playing with fire and just got back to stock, update with Kies Mini and go back to using the phone as I had always been and forget all this or do I try and figure this out? Well my stubborn side hating to be stumped had encountered a problem and so wanted to move forward... on i went.
16. I decided, ok, I can still see my internal sdcard so why not try reflashing the ISC Passion and see if maybe it will take this time with no EU. I ran it and exactly the same thing happened as the first time.. right down to the flash with the horizontal line and all. (I did not wipe data, cache or anything, just reflashed. Not sure if I should have or not)
17. Back to recovery mode and check... yes still see my internal sdcard. hmmm
18. Decide ok, how about it I do Woodrube's guide all over again from the start? Maybe that will work. I followed the guide again using all the same files and wound up right back at the EU screen again.
19. Hmmm, how about a different ICS ROM? Went and found ICZen and downloaded it. Hmm, how do I get this unto my internal sdcard if the phone won't boot all the way? Booted it back to the EU screen and just plugged the phone into the usb on my computer, windows recognized it, made the device plugged in noise, and both my internal and external sdcards on the phone showed up as drives. Navigated to the ICS folder in the internal sdcard and dropped the ICZen file into it.
20. Rebooted the phone into recovery mode using the power button menu
21. Used install from sdcard and flashed the ICZen. (Again, I didn't wipe anything before hand. Again not sure if I was supposed to)
22. The ROM installed and got stuck in a boot loop. I pulled the battery and rebooted to recovery and reflashed the ICZen again with no wipes. This time it worked and the phone rebooted and I got the ICZen splash screens, then the notification bar and signal strength meter showed up.. and AGAIN the weird flash with the horizontal bar and then the EU screen. SIGH
23. Booted back to recovery mode and checked if I still had access to internal sdcard. yes it was still there.
24. Shut down and booted to download mode and ran Odin and flashed back to stock 2.1
This is where I am now, It was too late to try anything else and my wife was glaring at me to go to bed so shut off the phone and went to bed.
I tried to put everything I did down with as much detail as I could. I'm sure some of you pros out there might be wincing at stuff I did, but again this is all new stuff for me and I'm slowly learning.
If you have any questions or need clarification just ask and I will try and help/explain better.
Hopefully this might help in the quest to solve this bug or it may just be a waste of time to read, dunno.

I got to:
"To start my phone was running 2.2 which was updated using Kies Mini."
and stopped there
Come back to Froyo - always welcome here

Moped_Ryder said:
I got to:
"To start my phone was running 2.2 which was updated using Kies Mini."
and stopped there
Come back to Froyo - always welcome here
Click to expand...
Click to collapse
LOL, yea I know, but up until this adventure last night, I just used the phone with the Samsung updates as it was, didn't really have a need to do otherwise.

I think that you should flash one of Moped's ROMs and make sure that it will boot up and run ok and that you did, in fact get out of the EU bug safely.
Couple of things:
I did get your PM and I thank you for the info. This post is far more detailed, which is a ton better.
You say that you were unlocked. There was a theory not too long ago about a corrupted EFS file, but AdamOutler uploaded his and someone else replaced theirs with it and it didn't work. But I am thinking that there might be a link here bc I have seen several posts over the last few months that ICS ROMs have been out where someone's data has been borked or their IMIE was gone. Wonder if there is a correlation to that? I'll have to ask some people onver in the Captivate thread and if anyone in the Vibrant thread can chime in too(?).
If you want to flash another ROM, just follw my ICS guide but where it says to install CM7, just install your shiny, new 2.2 instead and there you are.
Great Job dodging that bullet and hope that you no longer lurk, but be a part of the community at large. If your intelligence is reflected in your post, you are welcome here anytime.

Thanks Woodrube,
I was thinking the same thing about loading a 2.2 ROM and be sure I'm all good.
I know the 2.1 I loaded last thing last night seemed to work fine. But I will try a 2.2 once I get home and will update on here after I do.
Funny thing about all this is that my wife now won't let me near her Captivate ROFL.

Can you blame her ?
For the sake of the thread i can chime in on the unlock part. I'm still untouched by the EU bug "touching wood(rube)" . I'm using the i896 version of the Captivate from Rogers and there was never codes inside of it so most app were unsuccesfull at pulling them. I had to use the free SGS Unlock website where you upload your nv_data.bin and it returns you a unlocked version. I also never encountered any efs/imei issue.

hi.
I saw you have not wiped when installing the ROMs. I think maybe you should try and do the wipe before installing the ICS ROM.
Wipe system, data, cache.
Good luck

romitkin said:
hi.
I saw you have not wiped when installing the ROMs. I think maybe you should try and do the wipe before installing the ICS ROM.
Wipe system, data, cache.
Good luck
Click to expand...
Click to collapse
BINGO!
So I followed Woodrube's guide again.. started from scratch... only change I made was I wiped data factory reset, wiped cache, wiped Dalvik cache, and under mounts and storage I format system BEFORE flashing the ICS Passion.
Logged into Google Account and set up phone and now I'm rockin' ICS
Not sure how or why this worked but it did.
Thoughts?

Trying to Reload Stock Backup. Something's Not Right.

I installed CM10.1.3 using Odin and TWRP. Well, I didn't have my contacts so I'm trying to restore it to the backup I made so I can save those to the SD card and reload CM. Therein lies the problem. I cleared the caches, restored the backup and all went well until I tried to reboot. My phone has been stuck on the Sprint screen for over half an hour and won't boot. I know the first boot takes longer but not 30+ minutes right?! What's going on?

JL-KA said:
I installed CM10.1.3 using Odin and TWRP. Well, I didn't have my contacts so I'm trying to restore it to the backup I made so I can save those to the SD card and reload CM. Therein lies the problem. I cleared the caches, restored the backup and all went well until I tried to reboot. My phone has been stuck on the Sprint screen for over half an hour and won't boot. I know the first boot takes longer but not 30+ minutes right?! What's going on?
Click to expand...
Click to collapse
Try a battery pull and start from scratch.

El Shaddai's Wrath said:
Try a battery pull and start from scratch.
Click to expand...
Click to collapse
Start from scratch as in reload the backup? Or just try to power on?

Trying both. Pulled battery and tried to turn it on with the same result. Stuck on the Sprint screen. I'll try restoring the backup again and report back.

Not looking good. Restored the backup again and clicked Reboot. 10+ minutes on the Sprint screen so far.

Didn't work. Gonna try reinstalling cyanomod. Hopefully I can end up with at least something that will fully boot.

Nothing is working. I can't even figure out how to get cyanogenmod back on the divice. Last time I downloaded that from the phone.

JL-KA said:
Nothing is working. I can't even figure out how to get cyanogenmod back on the divice. Last time I downloaded that from the phone.
Click to expand...
Click to collapse
Which build are you on? MDC, MDL,MF9, MJA? Just curious?
GS4 Stock Rooted MJA 4.3,Philz Touch CWM,HotSpot Mod,Transparent Weather Widget,8SMS(Stock Messaging,KitKat)

Simply try a factory reset in your recovery.

I would also recommend a factory reset, either through recovery or from ODIN. Worth noting that, if you back your contacts up to your Google account, you can import them from there when you reload, without having to reflash, export to SD, flash again. This could also work for you in the unfortunate incident that you have to factory reset without a functioning backup (like now).
Also, Titanium will of course back up contacts and MMS/SMS, for future use once you get through the soft brick.

Hey Bud, just got your PM. One thing I Noticed with the S4 is that restoring nandroids can be a real pain. I struggled with mine for hours before I came up with a way to get it done AND get root back, which was my problem.
Granted, I'm on US Cellular, but it should work the same way
The first thing you need to do is make sure you're using Odin 3.07 As Administrator
Get into D/L mode (Power + Vol Down, then hit Vol up when the screen appears - works better if you're not connected to your computer yet)
Connect your phone and open up Odin, then check Reboot, PDA and flash the stock ROM for your phone.
I THINK the .tar file is in THIS Thread
Click start, once it loads into Odin, which could take a minute so don't freak if you get Odin (Not Responding)
If it boots back up into stock, you're golden. Then you can try and re-root as normal.
Now, the problem I had, was getting Root back. It just wouldn't take, even though it showed Success, using CF Auto-Root, Klingo, etc. All of them. SU got installed, but binaries would not install, SO, here's the procedure to get Root back.
You'll need the Chainfire SuperSU Update on your SDCard and you'll need the .Tar file for either CWM (I recommend) or TWRP for the Sprint S4. Not sure where to find those but someone will know on here
Put the SU Update on your sdcard
Boot to Recovery (Power +Volume Up)
Do a Factory Reset then reboot. Skip over the setup
Power down then reboot to Download Mode
In Odin, Use PDA to browse to the CWM.tar and run it - Now you have Custom Recovery
After Phone boots up, power down and reboot to recovery.
Flash the Chainfire SU Update
Done! Just like that.
Power up and check root
Hope this helps, neighbor

All good guys. Thanks for the help.

N910C stuck in frustrating bootloop

Hey wassup. So yesterday I rooted my phone and tried to install CM13 on it. Took a few tries since the rom I got was corrupted but I got it to work. Then I noticed it was guzzling the battery like lemonade (this EXACT same thing happened on my previous S4 too) so I gave up on it and decided to revert back to the stock rom. Everything went well... NOT. I downloaded the stock firmware (3gigs... zzz) and I flashed it with Odin and the phone restarted. The little android robot from the default unrooted recovery popped up and it had below it this: "Installing system update..." and then out of the blue it said "Erasing" and it's gear started rotating backwards. THEN, when it finished the normal Samsung Galaxy Note 4 logo popped up, went away and then CAME BACK AGAIN FOR LIKE 500 TIMES AND COUNTING. AOSP roms work just fine, it's just that touchwiz ones won't work whatsoever (even tried sixperience, no luck)... What should I do? I already lost my S4 due to this...

install TWRP custom recovery, boot up in recovery format system dalvik cache and internal storage then try flashing stock with odin hopefully it will work.

Try to remove battery first.from tsoch recovery wipe data cache and see if it works

dork997 said:
install TWRP custom recovery, boot up in recovery format system dalvik cache and internal storage then try flashing stock with odin hopefully it will work.
Click to expand...
Click to collapse
Been there, done that. Nope, still refuses to work :/

bumpity bump bump

Did you backup your efs partition before you flashed cm13? If not you corrupted your efs and your phone is a wifi tablet now because you cant use your modem.

travis82 said:
Did you backup your efs partition before you flashed cm13? If not you corrupted your efs and your phone is a wifi tablet now because you cant use your modem.
Click to expand...
Click to collapse
this never happened to me with my old s2 or s4
why is it happening now ?

Didn't backup. Now it just won't even work with odin. Whenever I try to just flash anything with it goes off and says 0 successes and 0 fails. What I did notice though was that whenever I installed a stock rom it starts this "Installing system update" with the android robot twingling it's antennaes and then out of nowhere it's blue bar goes away and it says "Erasing" then... bootloop. Now odin won't even work (explained above). Should I just give up and send it in for repairing? Or can ANYONE send me the twrp restore file, please...

Peontikos_Desmos said:
Didn't backup. Now it just won't even work with odin. Whenever I try to just flash anything with it goes off and says 0 successes and 0 fails. What I did notice though was that whenever I installed a stock rom it starts this "Installing system update" with the android robot twingling it's antennaes and then out of nowhere it's blue bar goes away and it says "Erasing" then... bootloop. Now odin won't even work (explained above). Should I just give up and send it in for repairing? Or can ANYONE send me the twrp restore file, please...
Click to expand...
Click to collapse
Hi
Same problem
Any ideas !!!

Hey,
I have the same problem it turns out after flashing, i cant remember, maybe dytto note 4 rom, it got stuck in continous bootloops and the only way it is working for me is when its charging. I know it sounds crazy but its the only way for me, ive tried installing stock different countries firmware and bunch of custom rom with no luck. I sent it to the place where i bought the phone and made myself look dumb asking why it is like that and i told them i had not do anything. After only a week they phoned me and said it was rooted (i did get the root out when i gave it but they somehow knew it was... later i understood that it is all about that stupid Know thing) and refused to cover my warranty. They said that the only way i can get it to work is to pay 300$ for new chip :,(

senon said:
Hey,
I have the same problem it turns out after flashing, i cant remember, maybe dytto note 4 rom, it got stuck in continous bootloops and the only way it is working for me is when its charging. I know it sounds crazy but its the only way for me, ive tried installing stock different countries firmware and bunch of custom rom with no luck. I sent it to the place where i bought the phone and made myself look dumb asking why it is like that and i told them i had not do anything. After only a week they phoned me and said it was rooted (i did get the root out when i gave it but they somehow knew it was... later i understood that it is all about that stupid Know thing) and refused to cover my warranty. They said that the only way i can get it to work is to pay 300$ for new chip :,(
Click to expand...
Click to collapse
ffs i'm not paying another phone's worth in a ****ing motherboard. I tried:
-Flashing the stock bootloader, fails at sboot.img:NAND Write start fail
-Flashing the PIT file, just... wont flash. Successes 0/Fails 0
-Flashing the stock AP file, bootloop
-Flashing the CP and the CSC stock files, serial(com) port cannot be opened.
****ing garbage. For some reason my phone's the only exception to the rule that phones able to boot into download mode are salvageable. It's going in for a repair and if it's more than $50 I'm not rooting again even at gunpoint.

Quick update:
I found a toolkit that has a flash stock boot image option. Had to recover to my cm13 backup to enable usb debugging. Will post results

Nothing of course...

try this step by step,
1. Download stock firmware THE LATEST ONE (n910c v5.1.1) from sammobile.com
2. Download newest Odin and Samsung USB; installed Samsung USB
3. I am assuming you have installed twrp recovery. Boot to twrp recovery and do a full wipe; wipe all!
4. Boot to downloading mode and install stock via odin. That is it.
Ps.... in case of failure, make sure you have installed Samsung USB! Or just reconnect usb cable with other usb ports untill it is working.

Never flach cm if doesn'T HAVE a efs backup if not you will stuck with cm

Oliva.raiders said:
1. Download stock firmware THE LATEST ONE (n910c v5.1.1) from sammobile.com
2. Download newest Odin and Samsung USB; installed Samsung USB
3. I am assuming you have installed twrp recovery. Boot to twrp recovery and do a full wipe; wipe all!
4. Boot to downloading mode and install stock via odin. That is it.
Ps.... in case of failure, make sure you have installed Samsung USB! Or just reconnect usb cable with other usb ports untill it is working.
Click to expand...
Click to collapse
Well, crap I already sent it in for repairing but if the fuqing robbers decide to change the motherboard instead of doing anything to it and charge me 500$ to do so I'm getting it back and I'm trying this one. Already did but it wouldn't hurt retrying... BTW FOR THE LOVE OF GOD DOES SOMEONE HAVE A TWRP BACKUP FILE ON STOCK TOUCHWIZ? JESUS

radium56ad said:
Never flach cm if doesn'T HAVE a efs backup if not you will stuck with cm
Click to expand...
Click to collapse
Is there absolutely NO workaround?

i had the same issue, this is how i solved this (you won't like it):
-deleted efs partition
-restored 5.1.1 coj5 via odin
-then took it to a samsung repair center to restore the imei
paid them like 50 bucks...that sucks. after this im backing up efs folder before flashing a rom.

radium56ad said:
Never flach cm if doesn'T HAVE a efs backup if not you will stuck with cm
Click to expand...
Click to collapse
JuanWilliman said:
i had the same issue, this is how i solved this (you won't like it):
-deleted efs partition
-restored 5.1.1 coj5 via odin
-then took it to a samsung repair center to restore the imei
paid them like 50 bucks...that sucks. after this im backing up efs folder before flashing a rom.
Click to expand...
Click to collapse
Oh that's nothing man. The fuqing scammers told me the whole freaking board had to be replaced...

There's one thing I've noticed though that's PROBABLY gotta be the culprit. Whenever I install a touchwiz rom, the phone boots up fine for once, shows the robot with the "Installing system update" and then it goes off with "Erasing" followed by the bootloop. Could anyone please elaborate on this? I have a feeling this is what's causing this ****fest