Related
Damn near burst a vessel earlier, doods. I had downloaded the newest darchdroid, and was looking forward to some oc'd, jit-enabled, vanilla goodness. I booted into recovery, wiped everything, and tried to install. Ut oh! Got a bad download. No es bueno. But, imma careful sob, so I have like 4 nandroids sitting on my SD....2 from flipz' latest betas, 1 from the original fresh toast, and one from dc 2.0.8. And it was a damned good thing, too! The backups off the newest would NOT boot. They kept looping. I tried rewiping, nothing. No good. Finally, I tried one of the other nandroids, and It worked first try. Because I'm a curious person, I then immediately booted to recovery and tried my most recent nandroid (the first one that bootlooped). This time it worked like a charm. Consider this evidence that having more than one nandroid in storage is never a bad idea. Anyone with a clue about what might have happened, and why the nandroid wouldn't work...until suddenly it did?
dood, Nandroids are for pansies.
Maybe it has a bad temper, too.
-------------------------------------
Sent from your mom!
@Kcarpenter- Well, paint me pink and stick me in a pot! (i was gonna make a joke about your wife and my root, but in this current climate, it prolly would have gotten me banned for being off topic in my own thread)
@jerry- you're prolly right. I know it has my sense of humor, cause it keeps effing with me when I'm drunk....
Same experience
I tried to make a nand of darch and when it failed I tried to restore my last nand of my last rom and almost "oops_I_crapped_my_pants" when it failed too
Fortunately an older nand worked
So I just had to try darchdroid again and its nanding just fine . I probably wont stick with it fo eva but it is fast as crap after eating liquid dish soap.
btw, did you happen to see the very last stock wallpaper in darchdroid?? HOMINA HOMINA HOMINA. So hot, want to touch the hiney.. awwooooooo
phenicks said:
Same experience
I tried to make a nand of darch and when it failed I tried to restore my last nand of my last rom and almost "oops_I_crapped_my_pants" when it failed too
Fortunately an older nand worked
So I just had to try darchdroid again and its nanding just fine . I probably wont stick with it fo eva but it is fast as crap after eating liquid dish soap.
btw, did you happen to see the very last stock wallpaper in darchdroid?? HOMINA HOMINA HOMINA. So hot, want to touch the hiney.. awwooooooo
Click to expand...
Click to collapse
Na. I had a totally bad download. It never even finished installing. I'll try it again this afternoon, when I'm near a computer.
I am not sure if this will help, but I had a loop problem and I noticed it started when I installed an app. This was in my nandroid back up. If you boot, it will go into loop.
Through adb start removing programs in the /system/app/. I ended up removing the program (apk and/or odex) and it stopped the loop without rebooting. Not sure why it did this.
Once you find the program that may cause this, restore your nandroid and only remove that apk or odex.
Just try it and see if this works.
you should wipe and clear data before nandroiding back. probably why you had a boot loop. With recovery theres no reason why you cant take 5 seconds and wipe everything before nandroid. If you did do a wipe and clear data before hand then my sincere apologies.
Yeah, I rewiped MULTIPLE times (each time I tried to nandroid recover, so, like, 6 times or so). Thanks, though.
I tried to uninstall Voodoo and now when I restart my phone it shows the galaxy
s and verizon animations, then loads up to a black screen and lit up capacitive icons. I can reboot into recovery, but I can't seem to mount the sd card and i keep getting errors when I try to mount any extensions. Please tell me there is something that I can do to fix this.
try wiping?
try instructions from "how to remove voodoo completely" thread. i cwm flashed the file from there when i had the same problem as u.
Take a deep breath. If you can see any thing at all on your screen, it's not bricked.
Just follow the instructions here;
How to remove voodoo
And your phone will be like new.
I would specifically follow the instructions that i give on page three, as adrynalyne's auto removal script still doesn't work 100%.
http://forum.xda-developers.com/showthread.php?t=804784&page=3
i had a similar problem when i tried to remove the old lag fix.
screen turned black on bootup and lights would come on but nothing else...
i had to use odin to restore everything and i had to wipe the cache and data from recovery.
Sometimes pixie dust works...or just listen to them
Sent from my sharks with fricking lazers on their backs
Thank you for the replies. I was able to finally mount the phone after doing a nandroid. It was force closing like crazy, but I kept with it until I was able to mount the phone from the os. Then I put in the voodoo lagfix uninstall folder and wiped and rebooted. Then I was able to nandroid to another backup and wiped, then did a odin restore, wipe and nandroid data restore. Now it's running like new and voodoo is uninstalled. This is an interesting experience coming from the hero and droid. I am a champ at those phones and I have never bricked a phone and I bricked this one twice. Kind of reminds me of the first time I started playing with my hero. It's a way to get the blood pumping.
emplox said:
I would specifically follow the instructions that i give on page three, as adrynalyne's auto removal script still doesn't work 100%.
http://forum.xda-developers.com/showthread.php?t=804784&page=3
Click to expand...
Click to collapse
This. My removal utility is a pain in my ass
I found it works, but then you gotta battery pull and nandroid back. A clean wipe wont cut it.
I disabled voodoo lagfix and the phone would not boot. I tried to use Odin and now all I get is force close when the phone boots up and it will not let me mount the card. any ideas?
Since I initially wrote this thread, I tried Voodoo one more time and when I removed it, this time with an app to see if it was user error, it once again made my phone non-responsive, it seems that it just is a bit unstable when being removed. With that said, I was where you are now and I was able to restore it. I did a factory wipe of my phone and cache through clockwork and then replaced my kernel and put the full stock image on the phone through Odin. Then I went into clockwork and went to my last backup and restored data. The phone loaded up, but it was as if I did a factory reset. I skipped everything, mounted my phone to my cpu and deleted voodoo files manually (the file needed to remove vodoo was just sitting there too). I went back into clockwork and just restored data under the advanced settings and I was back in business. Hopefully this can help you too. It may be overkill, but it worked.
You did NOT brick your phone. Will people please stop saying they bricked their phone when they haven't? Bricked means YOU CAN NOT RECOVER!!!! Stop scaring and confusing people! pretty please.
I'm not sure who that was directed to, but when this first happened,for a while it seemed that no matter what I did, the phone would not become operable. So for all intents and purposes, it is bricked. It doesn't matter if it can be restored, if you can't fix it, then it is bricked. I don't understand why people are so stuck on semantics. If that is the case, then no phone can be truly bricked, because once you send it to Samsung, they can restore it with their proprietary software. If your phone is nonresponsive and you can't fix it, it's bricked. I kept at it and was able to restore my phone, but I've read that there are people on here who couldn't figure it out and gave their phone in for another one. Because restoring the phone is above their skill level, they bricked their phone.
Kamar234 said:
I'm not sure who that was directed to, but when this first happened,for a while it seemed that no matter what I did, the phone would not become operable. So for all intents and purposes, it is bricked. It doesn't matter if it can be restored, if you can't fix it, then it is bricked. I don't understand why people are so stuck on semantics. If that is the case, then no phone can be truly bricked, because once you send it to Samsung, they can restore it with their proprietary software. If your phone is nonresponsive and you can't fix it, it's bricked. I kept at it and was able to restore my phone, but I've read that there are people on here who couldn't figure it out and gave their phone in for another one. Because restoring the phone is above their skill level, they bricked their phone.
Click to expand...
Click to collapse
I believe the preferred term is "soft-bricked"...LOL
Just do a wipe. I used adrenalines uninstaller. Worked like a charm. Voodoo is a pain in my butt
Sent from my SCH-I500-Fascinate using XDA App
Haha, yes, I've seen people use the term soft bricked here. Voodoo's instability is interesting though. I haven't felt this way since I started using smart phones in 03'. Just something I can't seem to get to work. Good thing the payoff isn't that great. To the person who is having trouble with their phone, I hope I, or someone else here, was able to help.
I just removed lagfix and it worked perfectly. Lol my phone never had lag until I installed lag fix. But I do love the kernal And boot animation provided.
Wanted to say I removed voodoo tonight by adding the remove file via adb. Everything worked as planned. Took about 10 minutes to get off step 2 but everything completed and booted up.
Sent from my SCH-I500 using XDA App
I can only offer <3 support... When I tried to remove Voodoo the first time, ugh I went through hell. I was stuck on my loading screen with Samsung just staring me in the face. Followed the complete remove by Adrynalyne, and everything was ok in the end.
Hey guys i know "Help!" threads get annoying (at least in the Fascinate forum they do.) but i could really use some help.
Rooted my friends phone today (root,clockwork,rom manager), and was going to install regular JAC kernal /voodoo w/o color fix.. I made sure the phone had the smaller NAND chip. Installation went fine (phone booted, voice told me it was switching to ext. 4.) and the voice said voodoo was complete. The phone was stuck at the S logo for about an hour and it was then i decided voodoo was botched. From there i rebooted to clockwork and went to restore the nandroid i made when i rooted. The nandroid got stock at one of the Data files for about 30 minutes. (i have a feeling this is around where i messed things up myself) Decided screw it and was going to flash JI6(T959UVJI6) and the stock kernal with ODIN. Now the phone boots past the S logo but the screen stays black and only the backlight menu buttons light up. It wont go past there. Any quick help is appreciated.
You didn't disable the lagfix I'm assuming.
Odin Eugene's Froyo that doesn't brick, then Odin JFD, install ROM of you're choosing.
Did you even try to search for a fix before posting???
~SB
problem0atique said:
Hey guys i know "Help!" threads get annoying (at least in the Fascinate forum they do.) but i could really use some help.
Rooted my friends phone today (root,clockwork,rom manager), and was going to install regular JAC kernal /voodoo w/o color fix.. I made sure the phone had the smaller NAND chip. Installation went fine (phone booted, voice told me it was switching to ext. 4.) and the voice said voodoo was complete. The phone was stuck at the S logo for about an hour and it was then i decided voodoo was botched. From there i rebooted to clockwork and went to restore the nandroid i made when i rooted. The nandroid got stock at one of the Data files for about 30 minutes. (i have a feeling this is around where i messed things up myself) Decided screw it and was going to flash JI6(T959UVJI6) and the stock kernal with ODIN. Now the phone boots past the S logo but the screen stays black and only the backlight menu buttons light up. It wont go past there. Any quick help is appreciated.
Click to expand...
Click to collapse
If you can still boot into clockwork recov. you can save it by pushing the undo voodoo zip file that was mentioned about. Assuming that u have adb access. If not odin froyo that doesnt brick tepartition checked. Turn off. Boot back in download. Odin stock jdf. Ji6 isnt a standalone rom. Its more like a no wipe update. Lucky his vibrant wasnt hardware locked lol. He will have a 90% chance of losing EVERYTHING
Had to odin flash froyo that doesnt brick then jfd and yep he lost all his data but he didnt have much to begin with. Now happily running Fusion. Thanks for the help guys!
So I decided to give Tranquility a test and see how it compares to my currently running ApeX. I followed the usual procedures, data wipe/factory reset.....twice.
then installed TranQ and the TranQ App update.
The phone then boots up and freezes on the animation screen. So i reset it, then it won't boot at all past the Logo screen. Randomly it decides to boot up fine, but then 30 seconds of android and it reboots and freezes up.
So for some reason it won't let me boot into clockwork recovery, so i decide to just do the system only SBF it and be done.
So I've SBF'd it twice now, the first time it did a random restart and froze, and also kept the tranq boot animation. I did the 2nd sbf and it's got rid of the animation screen and back to droid, however the tranq boot logo is there.
I haven't proceeded to reactivate the phone yet, and just leaving it alone it hasn't restarted itself. I'm planning on rerooting and reinstalling clockwork recovery and see if i can get one of my old backups going.
But, any theories to what would have jacked it up so bad? and why the stock moto logo wasn't put back when SBF'ing?
update:
rerooted just fine using Z4, installed clockwork recovery just fine too.
Right now I'm doing a data wipe and reinstalling ApeX 1.3.1 from scratch from clockwork recovery. Then I'm gonna restore one of my backups.
Hopefully all goes well
update:
recovered to my backup just fine. Still didn't get rid of the tranq boot logo, thankfully i had a zip stored away of the stock logo so I installed that.
All is now well in the world.
Lesson from this......if it's working fine, leave yo sht alone!
Logo is stored in different place then a system sbf will update. That's not tranQ 's fault. I still use gummyJar though. Too much blur in TranQ for me
I had the exact same problem when I went from fission to tran q. I literally had to do the. 320 sbf then the. 340 sbf to get tran q to install right. Didn't like it and put fission back on
yea i had to do the same thing comming from fission, and because of it i am just staying on tranquility until Obsidian is more stable, then GOODBYE BLUR :-D
The trick to installing TranQ is to install it over stock. If you try to install it over another custom ROM you will have nothing but problems.
Sent from my DROIDX using XDA App
davidukfl said:
Lesson from this......if it's working fine, leave yo sht alone!
Click to expand...
Click to collapse
I feel your pain, but you shouldn't be discouraged (as long as you Nandroid, Nandroid, Nandroid!).
I also spent a week fiddling with TranQ before giving up due to random reboots. But I went ahead and installed GummyJar. It was worth it!
When you're ready to climb back onto the horse, you should try GummyJar. If you prefer a no-bur ROM, it's probably the best in terms of speed and stability.
well i had tried Gummy before, but it was a little buggy for me. Phone would restart after calls, hardware buttons wouldn't always work and a few other little things.
I actually just switched to Fission and it's pretty brilliant thus far. No problems at all, and the fission manager helps a lot
fmkaiba said:
Logo is stored in different place then a system sbf will update. That's not tranQ 's fault. I still use gummyJar though. Too much blur in TranQ for me
Click to expand...
Click to collapse
IT IS TranQ's fault. It is the only ROM that does this. Before you get rid of Tranq, you have to go in to the tools and set your boot logo back to stock. I have flashed many different ROMs and it is the ONLY ONE that makes sure to "leave its mark," LITERALLY.
had same problem when I went from fission. I had to sbf .32 then sbf .34 then did the tran q and it worked just fine after that. I didn't like it to much so I went back to fission. To get rid of the tran q I just did the same sbf method I did and went back to fission.
z06mike said:
IT IS TranQ's fault. It is the only ROM that does this. Before you get rid of Tranq, you have to go in to the tools and set your boot logo back to stock. I have flashed many different ROMs and it is the ONLY ONE that makes sure to "leave its mark," LITERALLY.
Click to expand...
Click to collapse
You're right on w/this..Its too bad I found out the hard way..
okay so yes...im a noob, or atleast i consider myself one. heres my problem, i jumped into rooting and flashing head first, without researching EVERYTHING, ENTIRELY, so im at fault, i know this guys.
so heres the just of it, i have the mt4g aka htc glacier. i wanted to root, and flash a custom rom. i have a thing for sense 3.0 so i flashed virtuous fusion, now i never checked or learned how to figure out if i have a bad emmc? i through caution to the wind and here i am with no phone.
okay so its installed everythings good no glitches running smooth. my girl downloads mad bull**** into the phone and it starts running SLOW, real slow. i think hmm, factory data reset? earse everything yes i know this is unrevesable. phone goes black. remove battery reinstall, turn on, myotuch 4g then htc sense boot screen, then boot loop, then boot loop, then blakc screen unresponsive until battery pull.
cleared cached partition, wiped dalvik cache tried reinstalling viruous fusion from zip, same problem, not sure where i saved my nadroid backup unable to find it
so basicly guys, without gettin chewed out, am i a total ****ing moron? and is there hope....
also i saw a simalr thread unanswered there was a suggerstion to instal some file with a random jumble of letters and numbers as the name, however idk how to do so without being able to access my sd card with the phone i dont have a spare phone or way to put sd card in laptop please help me someone
SOLVED, not sure how i fixed it but i think its because, i first deleted everything i could form clockwork, then went to advanced deleted cache system and something else reflashed now its working...no complaints, however i read on another forum that virtuous fusion is known for brick devices upon factory data resets
Virtuous Fusion is a very outdated ROM.
Use Virtuous Unity.
joeyydaprofitt said:
okay so yes...im a noob, or atleast i consider myself one. heres my problem, i jumped into rooting and flashing head first, without researching EVERYTHING, ENTIRELY, so im at fault, i know this guys.
so heres the just of it, i have the mt4g aka htc glacier. i wanted to root, and flash a custom rom. i have a thing for sense 3.0 so i flashed virtuous fusion, now i never checked or learned how to figure out if i have a bad emmc? i through caution to the wind and here i am with no phone.
okay so its installed everythings good no glitches running smooth. my girl downloads mad bull**** into the phone and it starts running SLOW, real slow. i think hmm, factory data reset? earse everything yes i know this is unrevesable. phone goes black. remove battery reinstall, turn on, myotuch 4g then htc sense boot screen, then boot loop, then boot loop, then blakc screen unresponsive until battery pull.
cleared cached partition, wiped dalvik cache tried reinstalling viruous fusion from zip, same problem, not sure where i saved my nadroid backup unable to find it
so basicly guys, without gettin chewed out, am i a total ****ing moron? and is there hope....
also i saw a simalr thread unanswered there was a suggerstion to instal some file with a random jumble of letters and numbers as the name, however idk how to do so without being able to access my sd card with the phone i dont have a spare phone or way to put sd card in laptop please help me someone
Click to expand...
Click to collapse
well there's a lesson learned...
never EVER do a factory reset within a ROM... lol
btw, when you went to recovery, did it show any errors?
like "E:/ Can't find ..."?