Earlier, I tried installing ViperXL 2.1.0 ROM, wiped the cache, system, and factory restored in TWRP.
When I was installing the ROM, it got stuck at 90%, so I just gave up. This is my first android phone in two years, so I am just
starting to get use to ROMs again.
visualizeit said:
Earlier, I tried installing ViperXL 2.1.0 ROM, wiped the cache, system, and factory restored in TWRP.
When I was installing the ROM, it got stuck at 90%, so I just gave up. This is my first android phone in two years, so I am just
starting to get use to ROMs again.
Click to expand...
Click to collapse
Do it again. I had that happen to me once.
Reboot into recovery, Wipe System/Factory reset and reflash.
If you rooted from 2.20 flash the boot.img first
Could also be a corrupt zip. Chrome used to do that to me.
Sent from my One X using xda premium
Just flashed again and this time it was successful.
Unchecked the exchange mail mod because that is what it froze at earlier.
Vioe does that to ne often. It hangs at 90%. Then I simply reboot to twrp and flash again and it works without modifying anything.. it's weird
sent from my venom injected, blazingly fast as f#&k OneXL via xda premium
The problem is either related to TWRP or Aroma. I'm pretty sure all ROMs that use Aroma experience this, although I don't think I've had it happen to me since installing TWRP 2.3.1.0 (at least, from what I remember)
Rebooting back into recovery and reflashing usually works, no matter what the selection is.
Related
I just updated to bean 10. from synergy. As per instructions, I did the data reset and then wipe. Previous I had ez unlooker for the boot unlocker. Selected the unlocked version. Coudnt get it to load the first time secons time it went to the animation, but i pulled the battery. I rewiped and clean the cache again, but this time, I booted the phone, skiped all the sign up and update stuff and got the ez unlocker installed, unlocked the bootloader rebooted into recovery, (clockwork touch) and did my install. Now no issues at all, great battery life, on small thing, i got a volume booster app because the phone seems quieter. Oh, got the v.6 kernel too.
My question, I guess its a question. If you do a factory reset and data wipe ect ect as per instructions, arent you locking the bootlaoder? When I reinstalled the ex unlocker on the factory wipe, and loaded it, it gave me a bootlader status "unknown"
Nah a factory reset in custom recovery doesn't relock the bootloader. If it did we wouldn't be able to flash any of these ROMs because we wipe before flashing.
Mine says unknown as well. But I flashed imos new kernel an it worked despite saying unknown.
Sent from my SCH-I535 using xda app-developers app
Hi, this is my first post ever on XDA so sorry if im doing it wrong or if its in the wrong spot . anyways i am running stock and am on rooted & unlocked vzw gs3 . I downloaded and installed Scotty's Clean Rom 2.5 which was released just last week. I wiped/factory reset/ formatted everything and the rom seems to install fine, but then when i reboot it stays on the sgs3 boot screen forever? I dont know why it is not working. Ive tried about three times. Thanks.
slegger04 said:
Hi, this is my first post ever on XDA so sorry if im doing it wrong or if its in the wrong spot . anyways i am running stock and am on rooted & unlocked vzw gs3 . I downloaded and installed Scotty's Clean Rom 2.5 which was released just last week. I wiped/factory reset/ formatted everything and the rom seems to install fine, but then when i reboot it stays on the sgs3 boot screen forever? I dont know why it is not working. Ive tried about three times. Thanks.
Click to expand...
Click to collapse
I had the same problem with 2.1 and 2.5 on my phone. For some reason, the flash does not work on my phone the first time. both times I had to pull the battery when I got stuck on the boot screen then boot into recovery, re-wipe, fix permissions and reinstall. It always worked for me on the second try.
Good luck.
slegger04 said:
Hi, this is my first post ever on XDA so sorry if im doing it wrong or if its in the wrong spot . anyways i am running stock and am on rooted & unlocked vzw gs3 . I downloaded and installed Scotty's Clean Rom 2.5 which was released just last week. I wiped/factory reset/ formatted everything and the rom seems to install fine, but then when i reboot it stays on the sgs3 boot screen forever? I dont know why it is not working. Ive tried about three times. Thanks.
Click to expand...
Click to collapse
This happened to me once. Try to re-root the phone again then flash it.
Did you do a dalvick cache wipe too? Also were you flashing a kernel with 2.5? Are you coming from stock or a custom rom too? And if you are coming from a custom rom does it use a custom kernel? You should also check the md5 of the rom and verify it didnt get corrupt on download/transfer.
Sent from my SCH-I535 using xda app-developers app
RE
x714x said:
Did you do a dalvick cache wipe too? Also were you flashing a kernel with 2.5? Are you coming from stock or a custom rom too? And if you are coming from a custom rom does it use a custom kernel? You should also check the md5 of the rom and verify it didnt get corrupt on download/transfer.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Yes i wiped the dalvick, fixed permissions, formatted just about everything and factory reset, when that did not work I formatted and wiped everything before and after the flash. still no luck. I was not flashing a kernel, (to be honest im not even sure how to do that) and im coming from a stock rooted rom that i got when i first rooted with odin. I checked the md5 and everything matched up too.
How!?
rpuleo said:
This happened to me once. Try to re-root the phone again then flash it.
Click to expand...
Click to collapse
How do you re root? would i have to use odin to flash the rooted rom again?
The process of how you flashed sounds right.
When you say it's stuck forever, how much time did you give the phone to reboot. Sometimes with a new rom, it may take 5 min or longer for reboot to finish. If you haven't already, just walk away for 5-10 min before checking it.
Sent from a SYNERGIZED GalaxySIII
Clean rom wouldn't install for me on my phone... Weird stuff happened on the screen during boot animation and then would vibrate like crazy and go into boot loop... I came to realize that it was the kernel and I flashed lean kernel and it worked perfectly... I think these roms act differently on everyone's phones and sometimes there's no rhyme or reason to why things work for some people and not others... Just my. 02 cents
Sent from my SCH-I535 using xda app-developers app
Hey guys, i am trying to flash the synergy rom. I originally tried in TWRP but my phone would reboot when in the aroma insaller. After odin flashing CWM because i couldnt get back into TWRP, i tried again. Same problem, reboots out of aroma. I would go ahead and call the .zip faulty but i tested further. I chose backup in CWM and when it got to data it rebooted. Then i tried to format data and it rebooted again. Anyone know what to do to get synergy installed?
VinBertinelli said:
Hey guys, i am trying to flash the synergy rom. I originally tried in TWRP but my phone would reboot when in the aroma insaller. After odin flashing CWM because i couldnt get back into TWRP, i tried again. Same problem, reboots out of aroma. I would go ahead and call the .zip faulty but i tested further. I chose backup in CWM and when it got to data it rebooted. Then i tried to format data and it rebooted again. Anyone know what to do to get synergy installed?
Click to expand...
Click to collapse
Try flashing a rom without aroma, it has always cause problems for me but when I say something about it no one feels like it the problem
Sent from my SCH-I535 using xda premium
More and more people are having this problem. I did too. Phone would not stay in recovery or download mode long enough to do anything.
Background details. I have TWRP 2.4.4.0 installed, rooted, S-OFF. I had Viper XL installed, but wanted to try a stock JB rom. I downloaded CleanROM, booted into recovery. From here:
-wiped cache
-wiped dalvik cache
-System reset
-wiped system
From here, I go to install CleanROM. It runs aroma installer, I choose my options, and follow on screen prompts. It seems to flash too quickly (like it's not installing). It says successful, and gives me the option to go home, wipe cache/dalvik, or reboot. If I click reboot, it says No OS installed, are you sure you want to reboot?
I tried rebooting, and it stops in the white bootup screen. Not sure what step I am missing here. I didn't think that I needed to flash boot.img since I have S-OFF, but is that the case? Any help would be great - THANKS!
opto_isolator said:
Background details. I have TWRP 2.4.4.0 installed, rooted, S-OFF. I had Viper XL installed, but wanted to try a stock JB rom. I downloaded CleanROM, booted into recovery. From here:
-wiped cache
-wiped dalvik cache
-System reset
-wiped system
From here, I go to install CleanROM. It runs aroma installer, I choose my options, and follow on screen prompts. It seems to flash too quickly (like it's not installing). It says successful, and gives me the option to go home, wipe cache/dalvik, or reboot. If I click reboot, it says No OS installed, are you sure you want to reboot?
I tried rebooting, and it stops in the white bootup screen. Not sure what step I am missing here. I didn't think that I needed to flash boot.img since I have S-OFF, but is that the case? Any help would be great - THANKS!
Click to expand...
Click to collapse
Flash twrp 2.3.3.1 and reflash rom. Also verify md5 of Rom download. And if you want a great jb Rom give magio Rom a run. It's my daily driver and is amazing
Sent from my HTC One XL using xda premium
THANKS! That seemed to work. Why do some roms work with newer versions of TWRP, and some do not? That's odd. I installed Viper XL with 2.4.
opto_isolator said:
THANKS! That seemed to work. Why do some roms work with newer versions of TWRP, and some do not? That's odd. I installed Viper XL with 2.4.
Click to expand...
Click to collapse
All versions of twrp past 2.3.3.1 have issues. Be it wiping or flashing on the evita.
And if it helped just hit the thanks button
Sent from my HTC One XL using xda premium
31ken31 said:
All versions of twrp past 2.3.3.1 have issues. Be it wiping or flashing on the evita.
And if it helped just hit the thanks button
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
This.... Reflash 2.3.3.1 or previous. Had ypur issue months back, drove me balls crazy for a few weeks.
Sent from my HTC One XL using xda premium
Has anyone figured out a way to prevent boot loops when rebooting CM10.2 that doesn't involve wiping the device and reinstalling CM10.2 and GAPPS (if you're lucky to even get this to work)?
Went from stock 4.1.2 (unlocked and rooted, before the most recent patch)
Wiped data/cache/dalvik
Installed Skrilax 8/5 nightly and 7/29 GAPPS
Wiped data/cache/dalvik again
Booted up system, installed apps and messed around, then turned phone off. Now the phone sticks at the M logo (or unlocked bootloader, whatever you have showing).
uncgecongrad07 said:
Has anyone figured out a way to prevent boot loops when rebooting CM10.2 that doesn't involve wiping the device and reinstalling CM10.2 and GAPPS (if you're lucky to even get this to work)?
Went from stock 4.1.2 (unlocked and rooted, before the most recent patch)
Wiped data/cache/dalvik
Installed Skrilax 8/5 nightly and 7/29 GAPPS
Wiped data/cache/dalvik again
Booted up system, installed apps and messed around, then turned phone off. Now the phone sticks at the M logo (or unlocked bootloader, whatever you have showing).
Click to expand...
Click to collapse
Sounds like you didn't initially wipe your system. You're going to have to start over
sent from my xt926 RAZR maxx hd
Wiping was the first thing I did after doing a backup, before I installed the ROM. I assume if I hadn't wiped to start I wouldn't have been able to boot CM to begin with, which I was able to do.
I recall this being a known issue, but was just curious if anyone had come up with an answer and hadn't posted yet.
Sent from my DROID RAZR HD using xda app-developers app
I didn't have this issue when I ran CM10.2.
Sent from my DROID RAZR HD using Tapatalk 4
mentose457 said:
I didn't have this issue when I ran CM10.2.
Sent from my DROID RAZR HD using Tapatalk 4
Click to expand...
Click to collapse
I'm only running CM10.1, but I did notice on my first boot it seemed to hang on the CM loading screen for a long time (a few minutes). This was because like a noob I accidentally wiped modem. I had to use the Droid Utility's factory restore, then restart the wipe & flash process.
What did work:
I used CWM's format options to mount then wipe system/data/cache (in that order), and remount them. Then went back to the main CWM and ran the Factory Reset and Wipe Cache options, verified that system/data/cache were still mounted, then flashed from external SD the CM nightly and GApps.