Develop Bugs

Can't seem to install custom ROMs

Sorry for the somewhat long post, but I've tried a lot to solve this problem. So the other day, I tried installing the Paradox II Love ROM from Juggernaut 5.0 and followed its instructions exactly. I used both the Super Wipe and Kernel Cleanser and the steps that followed. After my phone rebooted, it would load the new kernel and then immediately reboot into recovery mode.
So after failing to work a few more times, I decided to try Darkside Digital Warfare. Again, the kernel would load, but then this time, it would just get stuck on the kernel logo. I waited over 20 minutes, and it did nothing. In the thread for the ROM, apparently a few people have had the same issue. A possible solution was installing a different kernel. I tried several, and it continued to have the same problem.
So I decided to use my nandroid backup, which didn't work. Something about an md5 mismatch I think. So I decided to try and reflash Juggernaut 5, and that ROM now wouldn't load. So I try GBaxeEX which I was using before Juggernaut and that just reboots to recovery.
So far, all that works are stock ROMs or ROMs that are close to stock. Right now, I'm using a debloated ROM and have no problems. I've found I can load custom kernels, so I'm using Darkside Xv1.
I've tried using Odin to go back to stock before flashing new custom ROMs, I've tried manually wiping system data in recovery before flashing, I've tried not using the Super Wipe, and I've tried redownloading the ROMs in case of an error or incomplete download. I've also tried initiating the install from ROM Manager. My phone just refuses to accept custom ROMs anymore.
Any advice is appreciated. I've been flashing ROMs since the Vibrant first came out and have never had a problem like this.

Try running tdj super wipe. Then flash your rom of choice. I highly recommend darkside rom!
Sent from my SGH-T989 using xda premium

GreggoryD502 said:
Try running tdj super wipe. Then flash your rom of choice. I highly recommend darkside rom!
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Like I said in my original post, I did try the Super Wipe and have tried it multiple times since. I've also tried using the Super Wipe and formatting system data in recovery.

segata said:
Like I said in my original post, I did try the Super Wipe and have tried it multiple times since. I've also tried using the Super Wipe and formatting system data in recovery.
Click to expand...
Click to collapse
You may have to ODIN back to stock then re-root. After that get CWM and start flashing again. This should work.
What I learned from my Vibrant days. If everything else fails, Odin Stock and start all over again.
BTW. Small hint. Use ROM Manager to create a .zip for CWM, rename it update.zip. Doing this will allow you to go directly from Stock recovery (volume +/- and power) to flashing without Rooting the device. Just load stock recovery and install the created update.zip by selecting Install Update. First flash of update.zip will go back to Stock recovery, second will load CWM.

Raistline said:
You may have to ODIN back to stock then re-root. After that get CWM and start flashing again. This should work.
What I learned from my Vibrant days. If everything else fails, Odin Stock and start all over again.
BTW. Small hint. Use ROM Manager to create a .zip for CWM, rename it update.zip. Doing this will allow you to go directly from Stock recovery (volume +/- and power) to flashing without Rooting the device. Just load stock recovery and install the created update.zip by selecting Install Update. First flash of update.zip will go back to Stock recovery, second will load CWM.
Click to expand...
Click to collapse
Again, this was something I tried multiple times and was mentioned in my original post. I was able to fix the md5 mismatch error thanks to a few other XDA threads, so I've restored a previous backup for my Juggernaut 5.0 setup.

Update: Since restoring a previous backup, I've successfully flashed Darkside Digital Warfare. However, Paradox II still refuses to install.

[Q] Need Help Small Problem

So, been a couple weeks been trying to flash CM10 ROMs, Paranoid, AOKP and CYANO, Everytime i flash I wipe everything as instructed and when it reboots it just hangs on the cyanogem boot image with the wheel spinning and does nothing. Not even a boot loop?! I let it sit for up to a half hour before and still nothing. But I can go and restore my old rom (not CM!) and works great..and if I flash a a new TW rom it flashes correctly.
Any ideas. I am on CWM when I flash. I also tried to flash TWRP and that would not take as well and had to go back to CWM.

Things I would check:
Verify MD5 tags of the roms your flashing when you download
Try wiping cache/dalvik/system and doing a factory reset after you have a successful flash
Question I have for you...
Have you tried unrooting and rooting again?
TWRP and CWM should both work, but have you ran the darkside scripts if using CWM? > http://forum.xda-developers.com/showthread.php?t=1477955
Lastly - I have heard people needing to reflash several times before it "takes" which it sounds like maybe you've tried & I realize these may be very basic things for you but you never know hopefully someone can help the more info you provide.

ldd_recoil said:
Things I would check:
Verify MD5 tags of the roms your flashing when you download
Try wiping cache/dalvik/system and doing a factory reset after you have a successful flash
Question I have for you...
Have you ever successfully loaded a custom rom on this particular phone?.... because you may have improperly rooted
TWRP and CWM should both work, but have you ran the darkside scripts if using CWM? > http://forum.xda-developers.com/showthread.php?t=1477955
Click to expand...
Click to collapse
I am on a custom rom now and everything is fine..but when I try to flash anything other than a Touchwhiz rom it seems to fail. I had paranoid running for a little while but I could not access my external sd so went back to my Jedi Mind Trick rom and everything was fine...so I decided to try a different paranoid thinking the issue was with this specific rom and it would not boot..went back to JMT and then tried aosp cm10 rom thinking and it wouldn't boot.
i have tried everything you have suggested except for the Factory Reset after the flash. Never really check the MD5 though. Might give it a try later on when I get bored with this rom again.
Thanks,
T

Sorry, reread your post now that I have the right context... Try unrooting and rerooting if you continue to have new rom flash issues.

toreone said:
So, been a couple weeks been trying to flash CM10 ROMs, Paranoid, AOKP and CYANO, Everytime i flash I wipe everything as instructed and when it reboots it just hangs on the cyanogem boot image with the wheel spinning and does nothing. Not even a boot loop?! I let it sit for up to a half hour before and still nothing. But I can go and restore my old rom (not CM!) and works great..and if I flash a a new TW rom it flashes correctly.
Any ideas. I am on CWM when I flash. I also tried to flash TWRP and that would not take as well and had to go back to CWM.
Click to expand...
Click to collapse
Solution is Simple.... When it hang in the cyanogenmod boot image with the wheel spinning just switch off -> Go to recovery -> install the DarkSide Cache Wipe.Zip then see the magic.... :good:

srikanth.t989 said:
Solution is Simple.... When it hang in the cyanogenmod boot image with the wheel spinning just switch off -> Go to recovery -> install the DarkSide Cache Wipe.Zip then see the magic.... :good:
Click to expand...
Click to collapse
Thanks, i will give this a try next time i flash...and i'll report back. This happened with a few different roms...this should fix those too!? also, I am pretty sure I ran the Darkside before I did first boot...should I have waited?
EDIT::: THIS WORKED...IT WAS HUNG UP ON BOOT IMAGE..FOLLOWED INSTRUCTIONS ON TOP AND BINGO!!!! I SAW THE MAGIC

toreone said:
Thanks, i will give this a try next time i flash...and i'll report back. This happened with a few different roms...this should fix those too!? also, I am pretty sure I ran the Darkside before I did first boot...should I have waited?
Click to expand...
Click to collapse
I was running into this same issue until I switched from CWM to the most recent TWRP, it's super easy just install Goomanager app and hit menu button >install OpenRecoverScript. After switching I haven't needed the Darkside script and I've yet to get a single hang at boot. Hopefully it helps!

cluckkillerb said:
I was running into this same issue until I switched from CWM to the most recent TWRP, it's super easy just install Goomanager app and hit menu button >install OpenRecoverScript. After switching I haven't needed the Darkside script and I've yet to get a single hang at boot. Hopefully it helps!
Click to expand...
Click to collapse
I actually tried this yesterday and it went through the motions and when I restarted into recovery it was just like a blue background with the Team Win on it but never made it past that...so I had to flash back to CWM through Odin to get it to be able to flash again..

cluckkillerb said:
I was running into this same issue until I switched from CWM to the most recent TWRP, it's super easy just install Goomanager app and hit menu button >install OpenRecoverScript. After switching I haven't needed the Darkside script and I've yet to get a single hang at boot. Hopefully it helps!
Click to expand...
Click to collapse
After doing this try downloading quickboot to boot into twrp recovery, if that doesn't help you might need to flash back to stock/re-root and start from square one =/

[Q] CM10 Stable - Completely Unstable and Broken

Hi there, I'm new to the forum but have been rooting for about a year. Here is my problem...
I was running stock firmware on my SGS3 and went through the standard cm10 root/rom install process. I flashed CMW with Odin, booted to recovery, installed cm10, jb gapps, cleared cache and delvik cache and rebooted. All the above processes worked fine and once it boots into JB, nothing seems to work. My home button does nothing, the top status bar is blank, no wifi, no keyboard (the process just crashes when I attempt to type).
I know this isn't an issue with CM10 on the SGS3 as this works for most people but does anyone have any ideas on how to remedy this? This may be a unique issue as I can't seem to find anyone else experiencing this.

Also...
I should also mention that I've tried a restore in recovery, reinstalled cm10, blah blah blah, and same results. I've also tried the cm10.m2 roms with the identical results. After reboot I don't even get the welcome wizard. It just boots right into the blank, default JB home screen and starts popping up process failure errors. I can navigate around (though the home button doesn't work) but can't use the keyboard etc.
Am I missing something? Is there a way for me to do a clean restore and try again?
Some technical info:
ClockworkMod Recovery v5.8.4.7
cm-10.0.0-d2att.zip
gapps-JB-20121130-signed.zip

Did you do a complete wipe? Data, cache, Davlik , System and then install cm10.
Coming from stock you need to fully wipe.
Sent from my SAMSUNG-SGH-I747 using xda premium

Machoscrawn said:
I should also mention that I've tried a restore in recovery, reinstalled cm10, blah blah blah, and same results. I've also tried the cm10.m2 roms with the identical results. After reboot I don't even get the welcome wizard. It just boots right into the blank, default JB home screen and starts popping up process failure errors. I can navigate around (though the home button doesn't work) but can't use the keyboard etc.
Am I missing something? Is there a way for me to do a clean restore and try again?
Some technical info:
ClockworkMod Recovery v5.8.4.7
cm-10.0.0-d2att.zip
gapps-JB-20121130-signed.zip
Click to expand...
Click to collapse
Your clockworkMod is out of date to run CM10 & the gapps. Upgrade to the latest clockwork mod, then the latest CM then the latest Gapps and you should be good to go.

dynamiclynk said:
Did you do a complete wipe? Data, cache, Davlik , System and then install cm10.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Thanks for the reply. This is what I did...
(Main cwm menu) -wipe cache partition
(Advanced) -wipe dalvik cache
+++go back+++
-reboot system now
Is there something additional I should clear?

Kweli87 said:
Your clockworkMod is out of date to run CM10 & the gapps. Upgrade to the latest clockwork mod, then the latest CM then the latest Gapps and you should be good to go.
Click to expand...
Click to collapse
Thanks for the reply,
How do i update to the latest clockworkMod? Do you happen to have a URL? I think I found the latest 6.something, but they all seem to be in .iso format.

You can't go from stock rom to CM10 without clearing factory reset thing in CWM.. I don't know the exact text string it uses but it should be right on top of clearing cache.. It looks like you only cleared cache and flashed a new rom.

i386W7 said:
You can't go from stock rom to CM10 without clearing factory reset thing in CWM.. I don't know the exact text string it uses but it should be right on top of clearing cache.. It looks like you only cleared cache and flashed a new rom.
Click to expand...
Click to collapse
Sorry I may have missed mentioning that. The first thing I did was the -factory restore/reset

If updating CWM doesn't help, I'd recommend re-downloading the CM10 zip and verifying the MD5 hash. It could be that the download got corrupted somehow...

goodtimes50 said:
If updating CWM doesn't help, I'd recommend re-downloading the CM10 zip and verifying the MD5 hash. It could be that the download got corrupted somehow...
Click to expand...
Click to collapse
Two questions:
1) What is the best way for me to update cwm?
2) I've seen this MD5 hash recommendation here and there. I have no idea what that means. How would I "verify the MD5 hash".

Machoscrawn said:
Two questions:
1) What is the best way for me to update cwm?
2) I've seen this MD5 hash recommendation here and there. I have no idea what that means. How would I "verify the MD5 hash".
Click to expand...
Click to collapse
Flash one of the rooted stock ROMs. Preferably an ICS one since you are on an older cwm. Wipe data, cache, dalvik. Download ROM manager from the play store. Update your recovery to the latest through that. Than flash back to cm10.

BAM1789 said:
Flash one of the rooted stock ROMs. Preferably an ICS one since you are on an older cwm. Wipe data, cache, dalvik. Download ROM manager from the play store. Update your recovery to the latest through that. Than flash back to cm10.
Click to expand...
Click to collapse
Ok thanks! I'm going to give that a shot and see how it goes.

Machoscrawn said:
Ok thanks! I'm going to give that a shot and see how it goes.
Click to expand...
Click to collapse
Ok so I tried flashing a stock rooted ICS ROM and now I'm stuck on the Samsung logo boot screen. Here is the method I tried, using Odin. http://forum.xda-developers.com/showthread.php?t=1739426
I used the "Bell Image (This works with Canadian Virgin Mobile SGH-I747M) - Old Image I747MVLALH1 (ICS 4.0.4)"
After flashing I booted into the stock recovery and cleared the cache partition then rebooted. Still stuck on the Samsung boot screen.
UPDATE: I just let it sit on the Samsung logo boot screen and it eventually loaded into ICS.

Machoscrawn said:
Two questions:
1) What is the best way for me to update cwm?
2) I've seen this MD5 hash recommendation here and there. I have no idea what that means. How would I "verify the MD5 hash".
Click to expand...
Click to collapse
1) I believe Rom Manager (from the Play Store) can do this.
2) Basically an MD5 value is generated when the file is created and is usually listed on the download page (on get.cm look for "md5sum" right under the download link for each build). There are apps that create an MD5 value from the file that you download and compare against the original to ensure that it's intact. If the values don't match, something's wrong with the file. Check out FastSum (there are lots of others out there too).

goodtimes50 said:
1) I believe Rom Manager (from the Play Store) can do this.
2) Basically an MD5 value is generated when the file is created and is usually listed on the download page (on get.cm look for "md5sum" right under the download link for each build). There are apps that create an MD5 value from the file that you download and compare against the original to ensure that it's intact. If the values don't match, something's wrong with the file. Check out FastSum (there are lots of others out there too).
Click to expand...
Click to collapse
Ok cool. Well i have downloaded ROM Manager but when I try to flash the latest recovery and it gives me a list of devices, mine isn't there. The only S3 listed is "Galaxy S3 (MetroPCS)". The list itself looks incomplete, maybe only 20 devices listed. I've rebooted the phone since installing ROM Manager but the list still only shows the one SGS3.

Machoscrawn said:
Ok cool. Well i have downloaded ROM Manager but when I try to flash the latest recovery and it gives me a list of devices, mine isn't there. The only S3 listed is "Galaxy S3 (MetroPCS)". The list itself looks incomplete, maybe only 20 devices listed. I've rebooted the phone since installing ROM Manager but the list still only shows the one SGS3.
Click to expand...
Click to collapse
Try to download GooManager and select the Flash Roms option, it will prompt you, select *Find one for me* reboot into recovery try to wipe/reset and reinstall the ROM and gapps and see if it works

wally3614 said:
Try to download GooManager and select the Flash Roms option, it will prompt you, select *Find one for me* reboot into recovery try to wipe/reset and reinstall the ROM and gapps and see if it works
Click to expand...
Click to collapse
Ok I tried the Goomanager route. When I'm in recovery doing the install of the rom, I get a FAILED error right after it tries updating partition... I've tried installing from internal and external sd with the same results...
I've attached a screenshot. Well I attempted to with my webcam, hopefully it's semi-readable.

Machoscrawn said:
Ok I tried the Goomanager route. When I'm in recovery doing the install of the rom, I get a FAILED error right after it tries updating partition... I've tried installing from internal and external sd with the same results...
I've attached a screenshot. Well I attempted to with my webcam, hopefully it's semi-readable.
Click to expand...
Click to collapse
Well at least you have the proper twrp definitely try and re download the ROM, carefully make sure it is absolutely the correct ROM(I rushed once, thought I was sure n dl'd the wrong one and bricked my older s3) if u have the slightest break during DL this can happen. I KNOW it is frustrating but worth it in the end

wally3614 said:
Well at least you have the proper twrp definitely try and re download the ROM, carefully make sure it is absolutely the correct ROM(I rushed once, thought I was sure n dl'd the wrong one and bricked my older s3) if u have the slightest break during DL this can happen. I KNOW it is frustrating but worth it in the end
Click to expand...
Click to collapse
Alright, I downloaded the latest stable (the only one) build of CM 10 from get.cm. Removed the current version from my internal sd and tried the process again. Same error...
So again, I'm now using GooManager, TeamWin Rocovery v2.3.1.0, CM10 Stable. Doing a factory reset, then wiping system, then install cm10, this is where it fails.
Any way that I can restore everything on my phone completely to stock and start from scratch? Anything else you/anyone can recommend?

Machoscrawn said:
Alright, I downloaded the latest stable (the only one) build of CM 10 from get.cm. Removed the current version from my internal sd and tried the process again. Same error...
So again, I'm now using GooManager, TeamWin Rocovery v2.3.1.0, CM10 Stable. Doing a factory reset, then wiping system, then install cm10, this is where it fails.
Any way that I can restore everything on my phone completely to stock and start from scratch? Anything else you/anyone can recommend?
Click to expand...
Click to collapse
If youre looking to completely start over. Just grab an unrooted stock .tar from one of the links somewhere around here, put your phone in download mode and let it flash. Clean slate.

[Q] MIUI for V One Help! (What in hells name am I doing wrong?!)

Hey there;
Firstly, thanks for your great efforts on the ports of your roms and consistent, useful forum help.
I appreciate that you probably get a load of these threads but I could really use some help with the installation of the ROM, as I've had a load of problems trying to install it.
I am attempting to install the MIUI rom (http://forum.xda-developers.com/showthread.php?t=1797515), and I am coming from the original software that comes with the device.
I have an unrooted One V, coming from the base OS and kernel. Currently, I can't get past the Jellybean Android screen (getting stuck on starting apps), and usually I can't even get past the MIUI screen at all. Here are the steps I've taken;
- I downloaded this kernel: boot-TK-USB-201302150054 from this thread: http://forum.xda-developers.com/show....php?t=1765687 and flashed it in fastboot, twice.
- Then launch into recovery, follow the instructions on your thread (format all apart from SD), and go ahead and install the .zip.
- Clear Delvik, clear Battery and Fix permissions, then proceed to reboot in an attempt to get in. At this point it hangs on MIUI screen for up to 5 minutes.
- I then try re-flashing the kernel in fastboot again. Still no help.
- I then try and reinstall the .zip from the SD card, and still no improvement.
I imagine I'm doing something very wrong, but I can't work out what it is and it's driving me crazy.
Can you help?!
Thanks in advance, Reasoner.

you are installing an older rom version which has no support..and is old

paarthdesai said:
you are installing an older rom version which has no support..and is old
Click to expand...
Click to collapse
Any chance you good point me in the right direction for an newer version?
Also, am I doing all the steps right?

paarthdesai said:
you are installing an older rom version which has no support..and is old
Click to expand...
Click to collapse
Okay, I have now attempted to install YOUR version of MIUI, and I'm still not having any luck.
I have;
- Flashed the boot.img using the one you suggest on your thread (twice)
- Booted into Recovery, cleared all caches excluding SD
- installed from .zip in CWM Recovery
- Cleared Delvik
On reboot I still get stuck on the MIUI screen.

Reasoner said:
Okay, I have now attempted to install YOUR version of MIUI, and I'm still not having any luck.
I have;
- Flashed the boot.img using the one you suggest on your thread (twice)
- Booted into Recovery, cleared all caches excluding SD
- installed from .zip in CWM Recovery
- Cleared Delvik
On reboot I still get stuck on the MIUI screen.
Click to expand...
Click to collapse
Ignore this, tried again and got through! Thanks a bunch!

Bootloop? Please help this soooper noober!

Sorry for my total noobness. I've just recently started this whole root awesomeness and I've hit a snag...... I'm sure there are many threads about my problem but I can't find one. I had CM 10.2 on my AT&T galaxy s3 and things were smooth and stable. Decided to try the "Collective" 4.3 ROM and SixShooter kernel. I put the zips in the phone (used the same gapps zip that was in there because I believe the Collective ROM is based off of the CM 10 ROM). Did a backup, then wiped chache, dalvick cache, system, and data (using TWRP recovery). Then did a multiple install of all three files in one action because TWRP lets you. so why not do it?
Rebooted, and I get the samsung logo, then sixshooter, then blank screen, vibration, pause, another vibration, then it starts all over. I can go into odin mode, or pull the battery to get it to stop.
Tried using odin to flash the .tar file, but it says PASS! and then the phone just automatically starts the loop again.
Was installing all 3 files (ROM, KERNEL, and Gapps zip files) at the same time a bad move?
I tried going back into recovery and it gives me the CWM recovery. Do I have TWRP AND CWM at the same time? Wierd. Tried wiping cache, and dalvik cache again and then rebooting, it still loops.
I'm at a a loss. I've watched a ton of videos and they all pretty much just say to find the right .tar and use odin to get back to stock. Like I said I've tried this and it just starts the loop again. Please help!! (I don't know a thing about ADB/terminal commands so if thats the fix I'll need my hand held) If theres a link to a thread that tells me how to get out of this I'd sure appreciate it. I greatly appreciate anyone who can take the time to explain to me what to do......

I would suggest booting into recovery and do the full wipe. Then just flash the ROM and gapps. If you're still bootlooping it could be a bad download of the ROM so if youve still got cm10.2 sitting around flash it instead. If that works I would look at downloading collective again. If not well maybe someone else has some input.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Ok, I just read the op again, and isn't the sixx shooter kernel packaged with the ROM? Also it states to factory data reset, wipe dalvik, install ROM, and the phone should reboot by itself do to a script, let phone settle, THEN boot back into recovery, flash gapps, wipe cache, reboot, enjoy! Maybe u shouldn't have flashed everything at once?

Yep, I'm a total tool. I installed everything in one action. ROM, gapps, kernel. Guessing I didn't need the kernel. And I should have read more closely the collective thread as it says to do the ROM. let it reboot, settle, etc. So the install all of them in one step is where I forked it up. I got it though. Pulled my head out and got the newest TWRP .img file and updated my recovery with odin. ROM is loaded and sweet as all get out!!
Crisis averted. Don't know what I would have done at work tomorrow without my podcasts and pandora! Thx for the help though. Love this forum.

Hmm. Okay, guess I don't have it completely sorted. I have gotten it to boot into the OS, let it sit a few. turned it off and tried to boot into recovery with vol+/home/power but it just starts it back up to the OS? Does the collective ROM change the way you get into recovery?

LilHoov said:
Hmm. Okay, guess I don't have it completely sorted. I have gotten it to boot into the OS, let it sit a few. turned it off and tried to boot into recovery with vol+/home/power but it just starts it back up to the OS? Does the collective ROM change the way you get into recovery?
Click to expand...
Click to collapse
Should have the four way reboot in the power menu. Long press the power button, while the phone is on, select reboot recovery. See if that helps...

Nevermind, I got it. lol
Gotta let go of that power button after vibration......man it's late