seeing as i cant post to this thread (http://forum.xda-developers.com/showthread.php?t=996073) yet i'll ask here...so im in the process of flashing the new blackhole resurrection rom and im stuck at the loading screen that says 'android' i've been on it for about 15-20 minutes and the little lady hasn't spoken to me since i got to this screen... also the phone keeps vibrating randomly...did i do something wrong or is this just part of the process? if i have to restore via cwm and try again that's fine i did a full backup yesterday, i just want to know if it's broken or just taking forever
still not working
just did a restore and it is still stuck at the boot animation and keeps vibrating randomly... am i going to have to do a full odin restore?
If you are getting 3 vibrations after 1, then something is forceclosing. It would be best to do a odin restore.
yeah that's what was happening...i did an odin restore from this thread:http://forum.xda-developers.com/showthread.php?t=977493...then i did a restore from a backup i had everything is working now except for boot animations custom or otherwise... i thought EB01 supported custom boot anis
so i flashed the voodoo version of EB01 and my custom boot anis work now
i have the same issue with Blackhole. during boot animation constantly haptics. once booted up force closes everything.
i'm using cmm 2.5 w/ voodoo disabled to flash it like the Blackhole 4.3 post recommended. but no luck. anyone know how to get Blackhole on correctly? thanks
Related
Recently I got a Samsung Vibrant, I decided to root it and put a custom ROM Image on it. Bionix. I Didn't like Bionix and tried to restore from a Nandroidb backup.
Thats where everything went crazy.
After restoring back to my stock ROM all my apps kept crashing and asking to force close. So I ran nandroid again and tried to restore from a different back up, and it said Restore failed. This is where sweat began to drip off my face as the Vibrant Only boots up to the Samsung Vibrant splash screen and goes black.
So I used ODIN 1.3 With stock vibrant roms to restore it, and it's saying it's PASSED, It mounts and everything, but it still keeps going black after the Samsung boot screen.
I've tried this 6 times with the same results all with different stock Vibrant roms with the same results. I can still boot into clockwork mod recovery. How do I fix this problem?
I DONT KNOW WHAT TO DO OH GOD SOME ONE PLEASE HELP Thank you in advance
Try taking your battery and sim card out. Put them back in start up odin, make sure you have the correct 32 or 64 bit drivers installed. Go into download mode plug into odin.
I used a couple of different stock rom sources and found this one to run the smoothest.
http://forum.xda-developers.com/showthread.php?t=739091
ps. nandroid sucks always odin, I have no problems with odin v1.0
So i decided to make the jump from nv to voodoo and I was excited, but before I knew it i messed up my phone. I upgraded to the new cwm 3.0.0.8 and cleared and wiped everything then flashed sc 2.7v now when I boot up it just sits at the samsung logo. If I battery pull I can still get into cmw, but when I try and flash anything else I have on my sd card it wont let me because of the new version of cwm. I tried to do a restore because I made a back up right before I flash 2.7v but then I get stuck on the honeycomb animation screen. I figure if worse comes to worst I can flash it with odin when I get home. Just wondering if any one else ran into this or has any suggestions because I would like to try voodoo again when I get this fixed.
Thanks in advance
Jake
If you check the thread where you got the rom you will see that 2.7 has been taken offline untill further notice. you should reflash 2.6 and than try to restore that nandroid.
good day.
I was under the impression that the 2.7nv was the one not working. Well be that as it may I was going to just flash back to 2.6 but the new cwm dosent support it anymore now that it is orange. Thank you for the fast response none the less.
Fixed this......put my sd card into an mp3 player that is also a usb drive and re downloaded an old cwm (the green one) and that let me get at my sc2.6nv. Yay.
Sent from my SCH-I500 using XDA App
Hi all,
I tried to install this voodoo lagfix on my phone yesterday through the update.zip method and my phone wouldn't get past the loading screen and kept reverting back to recovery mode. To make a long story short, I used odin to flash eclair, then I used "Samsung Kies Mini" to update me to the official froyo update. Everything worked fine, So I tried to install the lagfix again (horrible move) and now my phone just shows the Flashing S Boot then turns black (Everytime). I don't know what to do. I tired using odin to flash eclair which works, but still it goes to the flashing s boot and turns black. Please Help!
mgrisan1 said:
Hi all,
I tried to install this voodoo lagfix on my phone yesterday through the update.zip method and my phone wouldn't get past the loading screen and kept reverting back to recovery mode. To make a long story short, I used odin to flash eclair, then I used "Samsung Kies Mini" to update me to the official froyo update. Everything worked fine, So I tried to install the lagfix again (horrible move) and now my phone just shows the Flashing S Boot then turns black (Everytime). I don't know what to do. I tired using odin to flash eclair which works, but still it goes to the flashing s boot and turns black. Please Help!
Click to expand...
Click to collapse
someone else had this issue i think, il have a look
http://forum.xda-developers.com/showthread.php?t=1194845
everyone already knows that and thats what you said you did but it fixed it for them
hi all,
hope someone can help with this.. i have some sort of CWM bug that is messing up the entire flashing system for me.
ill try not to be too long winded.
was on MIUI 1.10.14 with JT "stock" kernel and all was fine..although this had the "no boot to recovery" issue, so i couldnt get to CWM by the menu. i decided to try glitch kernel again. so on tuesday i downloaded glitch V12 ML from the thread and flashed it by using ROM MANAGER and selected "install from sd card" ..i noticed immediately that something was sketchy, since when it booted to CWM via RM, i got version 4.1.xxx ? not 5.0.xxx like glitch is supposed to show.. i flashed anyway and it flashed and everything peachy. figured rom manager knew what it was doing..
so today rolls around..and since RickS put out the fixed MIUI 1.10.21 i again used Rom manager to get to recovery, and now its a totally diffrerent color 4.0.xx something.. i figured "it'll work like last time" .. uhhh no..
boot loop hell..
so i come home and ODIN it back to ED05, and install the CWM 4.0 Fixed for CM7.tar that i have used before...so now, i go to flash and at the splash screen on boot (no matter what i flash, ive tried older miui, and CM7.1) at the kernel splash screen it will hang for a second, flip over to what looks like a CWM script running very quickly (have seen blue and yellow so far for colors) then will go to boot screen and boot loop on either the blue CM logo (if CM7.1) or on the MIUI "globe"..
what the heck did i do and how do i fix it? i have ODIN'd back to EDO5 and it still will not rid it of the "problem"
Ideas?
mrjake1970 said:
hi all,
hope someone can help with this.. i have some sort of CWM bug that is messing up the entire flashing system for me.
ill try not to be too long winded.
was on MIUI 1.10.14 with JT "stock" kernel and all was fine..although this had the "no boot to recovery" issue, so i couldnt get to CWM by the menu. i decided to try glitch kernel again. so on tuesday i downloaded glitch V12 ML from the thread and flashed it by using ROM MANAGER and selected "install from sd card" ..i noticed immediately that something was sketchy, since when it booted to CWM via RM, i got version 4.1.xxx ? not 5.0.xxx like glitch is supposed to show.. i flashed anyway and it flashed and everything peachy. figured rom manager knew what it was doing..
so today rolls around..and since RickS put out the fixed MIUI 1.10.21 i again used Rom manager to get to recovery, and now its a totally diffrerent color 4.0.xx something.. i figured "it'll work like last time" .. uhhh no..
boot loop hell..
so i come home and ODIN it back to ED05, and install the CWM 4.0 Fixed for CM7.tar that i have used before...so now, i go to flash and at the splash screen on boot (no matter what i flash, ive tried older miui, and CM7.1) at the kernel splash screen it will hang for a second, flip over to what looks like a CWM script running very quickly (have seen blue and yellow so far for colors) then will go to boot screen and boot loop on either the blue CM logo (if CM7.1) or on the MIUI "globe"..
what the heck did i do and how do i fix it? i have ODIN'd back to EDO5 and it still will not rid it of the "problem"
Ideas?
Click to expand...
Click to collapse
odin back to dl09 eclair, that should fix it. I had the same problem. You can find the files in my guide.
+1
your solution worked and got rid of the mess... thanks!
I've been trying different ROMS and I used SlimROM for awhile until I realized GPS didn't work and my cell connection sucked comapred to TW-based ROMS. Then I tried Hyperdrive which worked at first but every time I would reboot after the first power on after the install, it would stay stuck on the Samsung screen. I reinstalled it time after time (like 6 times) and it would never REboot after the first boot. Every other ROM I've tried installing (Illusion, Synergy, CleanROM) just gets stuck right after the install and they never boot.
I've also noticed that when I try to do a factory wipe after installing anything but SlimROM, I get "error mounting /data" and "error mounting /sdcard/.android_secure".
I've tested installing all of these with the newest verison of TWRP and CWM v6.0.3.2
any ideas?
Factory reset Last option
snowman4839 said:
I've been trying different ROMS and I used SlimROM for awhile until I realized GPS didn't work and my cell connection sucked comapred to TW-based ROMS. Then I tried Hyperdrive which worked at first but every time I would reboot after the first power on after the install, it would stay stuck on the Samsung screen. I reinstalled it time after time (like 6 times) and it would never REboot after the first boot. Every other ROM I've tried installing (Illusion, Synergy, CleanROM) just gets stuck right after the install and they never boot.
I've also noticed that when I try to do a factory wipe after installing anything but SlimROM, I get "error mounting /data" and "error mounting /sdcard/.android_secure".
I've tested installing all of these with the newest verison of TWRP and CWM v6.0.3.2
any ideas?
Click to expand...
Click to collapse
if nothing works, factory-reset but last option.
yeah I just started downloading the stock rom to flash with ODIN in the morning. I just wanted some reason why this would happen so I won't always have have this problem and to know why it only works with some roms over others.
Please read forum rules before posting
Questions and help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Im having the same problem. I've done a complete ODIN restore to stock like 10 times, while trying Hyperdrive downloaded from 2 sources all with a matching MD5.
I'm on rooted stock right now until someone can figure this out.
I followed the rooting procedure... tried TWRP and Clockwork recoveries... Followed all instructions to the T...
Not sure what else to try... Or what I could be doing wrong... All I can think of now is restoring someones nandroid backup...
Being stuck at the Samsung Galaxy S4 screen sucks...
Zothar said:
Im having the same problem. I've done a complete ODIN restore to stock like 10 times, while trying Hyperdrive downloaded from 2 sources all with a matching MD5.
I'm on rooted stock right now until someone can figure this out.
I followed the rooting procedure... tried TWRP and Clockwork recoveries... Followed all instructions to the T...
Not sure what else to try... Or what I could be doing wrong... All I can think of now is restoring someones nandroid backup...
Being stuck at the Samsung Galaxy S4 screen sucks...
Click to expand...
Click to collapse
I restored to stock using these files http://www.sxtpdevelopers.com/showthread.php?t=237 to flash through ODIN. Rerooted by flashing the older kernel, rooting, installing superSU, then reflashing the newer kernel (normal root procedure). Then I insatlled ROM Manager and gave it root to install CWM recovery. Then I flashed to my same Hyperdrive ROM I was using before and now everything works beautifully. Nothing gets stuck anywhere an no more "cannot mount /data"
Just use that site and restore to stock and everything should work fine.
I'd like to add some confirmation to this. I had similar problems after flashing my first ROM- phone wouldn't reboot a second time, and when I attempted to make nandroids the files would be ridiculously large (~1 TB). I restored to the stock Touchwiz, rerooted normally, and reflashed normally. The strange thing is that I did the rooting and the flashing with the same files I had used the first time, implying something went wrong during the first rooting/flashing process.