Hi guys! Happy New Year!!
I have a problem, I run MiNCO v6 ROM and till yesterday it worked properly, but i found the volume a little bitt low, so i installed Vomer's patch audiov5, available in his modding thread and designed for MiNCO ROMs, which didn't gave me any problem with past MiNCO ROM versions live v5 or v4.
So I went to recovery, installed mod from .zip and rebooted; after 5 minutes the device was still blocked on a screen saying: "Android Upgrade, Application starting..." or something like that; so i decided to remove battery, and put it back again. From this moment the phone is stuck in boot loop, if i turn it on it block on MINCO logo.
I can access recovery using fastboot mode so i tried to restore from a Nandroid i had on the device but recovery said there were no files, i don't know why.
SO what can i do?? I have original ROM zip saved on the memory of the device, maybe i could wipe cache and flash fresh ROM?? Do i need to wipe also data and dalvik?? Other solutions??
Thanks.
Wipe data. Flash a known good rom. I don't see why you needed to make a thread when you could get to recovery.
063_XOBX said:
Wipe data. Flash a known good rom. I don't see why you needed to make a thread when you could get to recovery.
Click to expand...
Click to collapse
Sry if I just wanted to be shure of what I'm doing.
Related
I have had Cyanogenmod 7 for some time now, but ever since yesterday it is stuck on the Cyanogenmod boot screen and does nothing. I can get into Clockworkmod Recovery, but I am scared to do anything past that for fear of messing something up. Do you all know something I could try to get my phone back working (It is an HTC Inspire on AT&T)
Thanks
Ellimistopher said:
I have had Cyanogenmod 7 for some time now, but ever since yesterday it is stuck on the Cyanogenmod boot screen and does nothing. I can get into Clockworkmod Recovery, but I am scared to do anything past that for fear of messing something up. Do you all know something I could try to get my phone back working (It is an HTC Inspire on AT&T)
Thanks
Click to expand...
Click to collapse
Do you remember anything that happened/changed between when it was working and when it wasn't? S-ON or S-OFF?
Since you can get into CWM, I would just flash a new ROM. In fact, I would first dirty flash the same ROM over the one you've got first to see if that fixes it. If that doesn't work, clean flash a different ROM.
bananagranola said:
Do you remember anything that happened/changed between when it was working and when it wasn't? S-ON or S-OFF?
Since you can get into CWM, I would just flash a new ROM. In fact, I would first dirty flash the same ROM over the one you've got first to see if that fixes it. If that doesn't work, clean flash a different ROM.
Click to expand...
Click to collapse
What's the easiest way of going about this, I haven't ever done anything past the initial root and flash
Just put the ROM to be flashed on the SD card, it's a zip - and then choose to "install from zip" and navigate to it in Recovery. You could find a superwipe .zip file - which cleans all caches etc - on this forum, and that will give you the assurance that your phone is squeaky clean for when you flash the ROM zip file.
Just make sure your phone is - preferably - fully charged. The only thing that can go wrong is the battery running out while flashing .
If for whatever reason it still doesn't get past the bootloop, re-flash or try flashing a different ROM.
There are plenty of really good ROMs for the HD in the ROM sub-forum, for a rock-solid alternative, look at the Android Revolution ROMs.
Ellimistopher said:
What's the easiest way of going about this, I haven't ever done anything past the initial root and flash
Click to expand...
Click to collapse
Download the ROM (make sure it's the exact same version as the one you first flashed) onto your computer. Get the ROM onto your phone, either by using an sdcard adapter or by booting into CWM and mounting the sdcard on the computer. In CWM, wipe cache and dalvik, then install the ROM zip. Reboot. (If you're S-ON, say so; there are a couple extra steps.)
If that doesn't work, do it again with a different ROM. Also, instead of wiping only cache and dalvik, also wipe system and data. You will lose all your installed apps and saved data.
Sorry, but I can't give exact step-by-step CWM instructions because I don't use CWM.
So all I did was reflash the exact same file that I already had on my SD card, and that worked. Cleared the data/caches and I'm back online. Thanks for the help.
i i tried innstalling the Cyanogenmod 10 from the rom manager
and when it was time to reboot it was stuck on the cyanogenmod logo then i formatted the phone system and everything thinking it would solve my problem..now im stuck on the boot screen saying "Samsung Galaxy Siii"
any solutions please ?
I would say reboot to recovery and install the nandroid you should have made before installing a custom rom... If ya dont have a backup its time to learn some odin and adb. Or try flashing a different rom, either way learning adb and odin is not a bad idea.
Do a factory reset. Wipe cache/dalvik.
misterarby said:
i i tried innstalling the Cyanogenmod 10 from the rom manager
and when it was time to reboot it was stuck on the cyanogenmod logo then i formatted the phone system and everything thinking it would solve my problem..now im stuck on the boot screen saying "Samsung Galaxy Siii"
any solutions please ?
Click to expand...
Click to collapse
If you followed the directions to install CM then you wiped your dalvik cache, when you do this it takes the phone quite a bit longer to boot than normal. It is possible that it was just rebuilding the cache, or also possible something didnt flash correctly and it was actually stuck, just thought you should be aware of the delay in startup. Your second step of formatting system effectively deleted whatever OS was there so its no wonder you didnt get past the boot logo at this point, there was nothing left to get to. Reflashing the ROM should fix you up assuming it was a good download to begin with. I would say forget about using rom manager to install roms (and probably not be alone in saying this), flash it from a .zip in the recovery manually. If not you are probably looking at flashing back to rooted stock with odin as smokin suggested. Another alternative would be if you have an external sd and some way to copy to it you could just redownload CM and flash it from the external storage. Also as smokin mentioned you should have a backup, if not bet you will next time .
You checked "yes this is a question"
Guess where it belongs?
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thanks
FNM
After trying to flash a new rom after being on AOKP M1 for a little while (http://forum.xda-developers.com/showthread.php?t=1875923) the phone got stuck at the Black and white Samsung Galaxy SIII screen and didn't boot upon hitting reboot system now on cwm. Tried again, tried reflashing and the whole 9 yards wouldn't boot at all. So I turned to odin and went to the prerooted latest JB build (http://forum.xda-developers.com/showthread.php?t=1949687) and then reflashed touch cwm and tried to reflash the rom. Same problem. So, I odin'd back to the non rooted UVDLJA. Rerooted and reflashed cwm and blahblahblah. I said hmm maybe it's the rom, I then tried to flash this rom (http://forum.xda-developers.com/showthread.php?t=1993934) and when I tried to reboot system now after the process; again the phone got stuck at the black and white Samsung Galaxy SIII screen and did not boot. The phone works fine when I odin it to stock builds but refuses to boot custom roms. Can someone help me here? I haven't been able to find a solution for days. :crying:
PS I'm a noob, don't kill me lol
edit: forgot to include I have the Tmobile variant
Did you wipe data and cache when you flashed the new rom?
nyyankees1237 said:
After trying to flash a new rom after being on AOKP M1 for a little while (http://forum.xda-developers.com/showthread.php?t=1875923) the phone got stuck at the Black and white Samsung Galaxy SIII screen and didn't boot upon hitting reboot system now on cwm. Tried again, tried reflashing and the whole 9 yards wouldn't boot at all. So I turned to odin and went to the prerooted latest JB build (http://forum.xda-developers.com/showthread.php?t=1949687) and then reflashed touch cwm and tried to reflash the rom. Same problem. So, I odin'd back to the non rooted UVDLJA. Rerooted and reflashed cwm and blahblahblah. I said hmm maybe it's the rom, I then tried to flash this rom (http://forum.xda-developers.com/showthread.php?t=1993934) and when I tried to reboot system now after the process; again the phone got stuck at the black and white Samsung Galaxy SIII screen and did not boot. The phone works fine when I odin it to stock builds but refuses to boot custom roms. Can someone help me here? I haven't been able to find a solution for days. :crying:
PS I'm a noob, don't kill me lol
edit: forgot to include I have the Tmobile variant
Click to expand...
Click to collapse
a few questions:
and i can verify the issue is something on your end, because the ROM you tried was mine, and nobody has had that issue (not booting it)
do this...
1. make sure you have the latest version of clockwordmod, don't use twrp
2. re-download my ROM (just for sake of not adding any other variables to your issue, because mine should boot)
3. put ROM on external SD card
before continuing... take a quick look at my thread here in QA titled "flashing ROMs correctly every time" .... so you can get some instruction on verifying MD5 of the download... don't worry, the thread will explain that you...
now proceed
4. boot to recovery
5. do a factory reset - 3 times do this, just to be thorough. people will say you don't need to, but like i said, just for the sake of removing variables
6. go to mounts and storage, format system 3 times - (yes, through recovery as well)
7. flash ROM, and reboot
EDIT*** i will say this, ALWAYS format system when flashing a new ROM
cobraboy85 said:
a few questions:
and i can verify the issue is something on your end, because the ROM you tried was mine, and nobody has had that issue (not booting it)
do this...
1. make sure you have the latest version of clockwordmod, don't use twrp
2. re-download my ROM (just for sake of not adding any other variables to your issue, because mine should boot)
3. put ROM on external SD card
before continuing... take a quick look at my thread here in QA titled "flashing ROMs correctly every time" .... so you can get some instruction on verifying MD5 of the download... don't worry, the thread will explain that you...
now proceed
4. boot to recovery
5. do a factory reset - 3 times do this, just to be thorough. people will say you don't need to, but like i said, just for the sake of removing variables
6. go to mounts and storage, format system 3 times - (yes, through recovery as well)
7. flash ROM, and reboot
EDIT*** i will say this, ALWAYS format system when flashing a new ROM
Click to expand...
Click to collapse
thanks for the info, will try this all out soon. I've been flashing roms for years now and have never run into anything like this, and as previously stated, this didn't occur solely with your rom which has me thinking something has happened to the phone itself. will get back to you soon and once again thank you
chucktdriscoll said:
Did you wipe data and cache when you flashed the new rom?
Click to expand...
Click to collapse
of course, wiped data, cache, & delvik
nyyankees1237 said:
of course, wiped data, cache, & delvik
Click to expand...
Click to collapse
my point is...
coming from a cm based ROM, or aokp, whatever you said... you would want to format system as well.
nyyankees1237 said:
After trying to flash a new rom after being on AOKP M1 for a little while (http://forum.xda-developers.com/showthread.php?t=1875923) the phone got stuck at the Black and white Samsung Galaxy SIII screen and didn't boot upon hitting reboot system now on cwm. Tried again, tried reflashing and the whole 9 yards wouldn't boot at all. So I turned to odin and went to the prerooted latest JB build (http://forum.xda-developers.com/showthread.php?t=1949687) and then reflashed touch cwm and tried to reflash the rom. Same problem. So, I odin'd back to the non rooted UVDLJA. Rerooted and reflashed cwm and blahblahblah. I said hmm maybe it's the rom, I then tried to flash this rom (http://forum.xda-developers.com/showthread.php?t=1993934) and when I tried to reboot system now after the process; again the phone got stuck at the black and white Samsung Galaxy SIII screen and did not boot. The phone works fine when I odin it to stock builds but refuses to boot custom roms. Can someone help me here? I haven't been able to find a solution for days. :crying:
PS I'm a noob, don't kill me lol
edit: forgot to include I have the Tmobile variant
Click to expand...
Click to collapse
I was having some of the same issues. I downloaded XquiziT's Superwipe and ran it by installing from external sd card. I ran it three times to clear everything out, then I wiped data, cache and the rest three times.
No probs for me after that.
Will definitely give that a try as well! Thank you! Will post my results when the holiday is over.
Happy thanksgiving
Sent from my SGH-T999 using xda app-developers app
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!
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