Hello,
I am a noob trying to install a rom with aroma installer. But now it has been stuck at the page where it says: The installation wizard has successfully installed *********. Press next to exit.
What do i do? Power off?
Is it definitely stuck? Aroma doesn't always recognise touch events very accurately, and I usually have to tap the "next" button a few times before it registers. Failing that, if it's finished installing whatever you flashed, you should be fine to reboot manually anyway.
Yes,i have tried to push the next button many times but nothing happens. It has been like this for 30 minutes now. The successfully installed text appeared very fast, a second or two maybe after the previous screen. So if it has installed the rom, it was def a fast install.
Anyway, is it safe to try to reboot, even if it was in the middle of the install? Rebot to recovery and try again?
Well, there certainly isn't anything else to be done besides rebooting. I don't know what you were trying to install - if it was a several-hundred-MB ROM, as most things that use Aroma are, you would expect it to take a while. Smaller things can be flashed very quickly. If it _did_ go wrong somewhere, there are a few things:
1. What recovery, and what version thereof, are you using?
2. Did you wipe data before using the installer?
3. Most of all, what were you trying to install? There might be some known issue with certain configurations.
I wouldn't necessarily expect a working OS when you reboot, depending on what you were trying to install and how badly things went wrong, but you should be able to get back into recovery easily enough.
Thank you for your quick reply.
1. I use the CWM recovery in this http://forum.xda-developers.com/showthread.php?t=1914394 thread, not the newest, but 5.5 something i believe.
2. Yes, wiped all data + dalvik.
3. I was trying to install rXTREME on my SGS III lte i9305.
I've rebooted now, and everything works perfect as the phone was before i tried to do the install. No brick. I also tried to flash it one more time, but stuck at the same place again. Rebooted fine at stock rom again. Maybe i should take this as a hint that someone else should be put at the steering wheel.. :laugh:
EDIT: forgot link above
Found out what the problem was.
In Aroma Installer i selected EFS backup both times. The third time i tried i did not do this. And everything went fine. Runs smooth.
my galaxy s3 international version got stuck at 30% of formatting\data partition while trying to flash s4 revolution 4.1 rom
what should i do?
jehad.drarjeh said:
my galaxy s3 international version got stuck at 30% of formatting\data partition while trying to flash s4 revolution 4.1 rom
what should i do?
Click to expand...
Click to collapse
This is I9305 forum is this your phone ??
This thread is about Aroma installer is that your problem ???
Suggest you read the basic faqs and guides first looks like from your post you are either flashing wrong rom to your phone or have hijacked a thread in the wrong forum ./
jje
Related
2 nights ago I thought I would have a go at installing ULTIMATE ROM 3.0. I have flashed many Roms on my Galaxy S before and not had a problem yet. I have ClockworkMod Recovery 2.5.1.0 installed.
However, this time- something went wrong. I don't think the installation completed properly. When I tried to reboot the system (to go back into my previous ROM) I wasn't able to. The Samsung logo appeared before the phone booted back into Recovery mode.
I tried to re-flash my previous working update.zip but had problems. I wasn't able to properly re-flash as the Installation would abort for various reasons. After doing cache clearing and data/factory reset I still had no luck. I resorted to reformatting the sdcard. Still didn't solve the flashing problem.
Throughout the whole time I was able to adb into the phone, browse the file system and I could push files on to it and take files off. But Kies wouldn't recognise the phone and Odin isn't able to complete a transfer to the phone (not sure why).
Today, I am able to successfully flash update.zip files (at least, that's what it looks like) but the phone ALWAYS boots into ClockwordMod recovery.
I am fast running out of ideas. Does anyone have any suggestion?
How can I tell if my ROMs are really 'there' but I can't access them because ClockworkMod is preventing them from booting?
hmmm... me too.. stuck in a loop, that keeps going back to the CWM recovery menu, and no matter what i do, keeps going back to it... cant even get to the download screen to flash (again).... here i was thinking no matter what happens when installing custom roms, i can always flash to my stable secure rom, but not this time... need some software that can perform surgical operations, any suggestions?
bradels said:
2 nights ago I thought I would have a go at installing ULTIMATE ROM 3.0. I have flashed many Roms on my Galaxy S before and not had a problem yet. I have ClockworkMod Recovery 2.5.1.0 installed.
However, this time- something went wrong. I don't think the installation completed properly. When I tried to reboot the system (to go back into my previous ROM) I wasn't able to. The Samsung logo appeared before the phone booted back into Recovery mode.
I tried to re-flash my previous working update.zip but had problems. I wasn't able to properly re-flash as the Installation would abort for various reasons. After doing cache clearing and data/factory reset I still had no luck. I resorted to reformatting the sdcard. Still didn't solve the flashing problem.
Throughout the whole time I was able to adb into the phone, browse the file system and I could push files on to it and take files off. But Kies wouldn't recognise the phone and Odin isn't able to complete a transfer to the phone (not sure why).
Today, I am able to successfully flash update.zip files (at least, that's what it looks like) but the phone ALWAYS boots into ClockwordMod recovery.
I am fast running out of ideas. Does anyone have any suggestion?
How can I tell if my ROMs are really 'there' but I can't access them because ClockworkMod is preventing them from booting?
Click to expand...
Click to collapse
myrobelle said:
hmmm... me too.. stuck in a loop, that keeps going back to the CWM recovery menu, and no matter what i do, keeps going back to it... cant even get to the download screen to flash (again).... here i was thinking no matter what happens when installing custom roms, i can always flash to my stable secure rom, but not this time... need some software that can perform surgical operations, any suggestions?
Click to expand...
Click to collapse
Thats too bad guys,and i m sorry to hear that news.I would like to havean answer but i dont...
The fact is that since most people in this forum use some custom roms,and all of us think the same,that we can always go back,so it would be great if you give some more details about what happened to you,and mybe why it went wrong,and it would be even better if one of the BIG guys would give some explanation about this...
I already thinking of not updating my rom anymore,dot want to end up in looping too,so lets see if someone will find something.Good luck guys..
By the way,i didnt get it right,CWM recovery cannot load your backup????
I just got an idea,but not sure if or how it would work or not.
Since you can push file with ADB,if soeone made a clean backup with his CWM (o e mail,contacts,setting saved) and send it to you,so that you log in with CWM recovery and flash that ???
Just an idea..maybe stupid dont know...
Its not very clear if youve tried this already but cant you just boot into recovery through adb? or does that not work either?
[SOLVED -- Read my last post]
Posting on forum was my last resource, but I've tried literately almost everything I can possible find.
I already bricked my phone and had to unbrick, do everything (update firmware etc) all over again.
I am at a point where I am afraid to do something new to my phone now without knowing what they are...
Please bare with me, I am not familiar with exactly what flashing is or whatnot, I just followed the instructions and got where I am....
K, recently I decided to wipe my phone CLEAN and update to new CyanogenMod 9 from factory mode.
So, I have Captivate, I897. It was ECLARE with 2.1 firmware.
I have updated to 2.3.5 (Gingerbread [I897UCKJ2]), Rooted.
I had to Flash BACK to KK4_stock_kernel.tar for me to use WIFI again because I had issue after Rooting my phone, I couldnt access the WIFI.
I installed Clockwork mod (Free version).
My goal is to install CyanogenMod 9, and part of the process requires me to enter the CMW Recovery Mod.
I dont even know what this looks like, but all I know is whenever I boot my phone, after the AT&T logo animation it seems to go into this "messed up" screen, where as if my phone is broken. Stays there for 3 seconds and then continues to boot back to its OS.
In ROM manager, it says Flash ClockworkMod Recovery (You must have the clockworkmod recovery installed to flash and restore ROMs!)
Another option within ROM manager is, Reboot into Recovery (Boot into Recovery mode for manual management.), which if I do access it, it takes me back to that AT&T logo animation and that "messed up" screen again, but this time it stays there. Where all kinds of colored pixels are on my screen as if my screen is broken. It will only continue to boot back to my OS if I press power button or some sort.
Im guessing that's my Recovery Mod, which my phone for some reason cannot see?
So I tried "Download ROM (Upgrade to ROM Manager (premium) to access the full list of ROMs!", hoping this may cure that messed up screen effect, which I think is the Recovery Mod for all I know... When I click to install, it gives me Confirm Phone Models. None are my phone model for me to install.. (It only gives me Google Nexus S / Google Nexus S 4G / Samsung Epic4G / Samsung GalaxyS i9000).
Earlier, I was looking at this, http://forum.xda-developers.com/showthread.php?t=1127578
which is a way to fix recovery mod(?) But I have NO idea how to even install those files... Maybe not the .tar file but the other one.
Please help? Am I the only one experiencing this kind of problem? Couldnt find anywhere else on youtube / google / forum..
Thank you VERY much in advance, really appreciate it..
-Dan.
danroh said:
I had to Flash BACK to KK4_stock_kernel.tar for me to use WIFI again because I had issue after Rooting my phone, I couldnt access the WIFI.
-Dan.
Click to expand...
Click to collapse
This is your likely problem right here. The Kernel that is installed during the rooting process and typically when you install custom roms is what is responsible for installing and therefor you being able to access the CWM recovery. Flashing back to the stock kernel likely messed things up for you.
http://forum.xda-developers.com/showthread.php?t=1300843
Now if you follow that link it will take you to several one click options for flashing your phone to stock gingerbread but with a kernel containing CWM. Also keep in mind that it is possible you could have wifi issues if you've had them in the past, but if your goal is to get to CM9 just ignore the wifi for the time it shouldn't be an isuse in the end.
Hey OP,
See this.... TRusselo's Flashing Guide
Sent from my SAMSUNG-SGH-I897 using xda premium
You need Gingerbread bootloaders.
Thanks guys! I figured out the problem and solved it!
Like you guys said, I didnt have the bootloader. The gingerbread I installed was the no bootloader version. After reinstalling to the one with bootloader, I was able to access the recovery mod and that "rainbow screen" glitch was no more.
Thank you!
Hello everyone,
I've been literally 12 hours searching for possible answers on how to repair my Galaxy Note N7000 which from what I've concluded, has a problem that can be easily repaired but I've found nothing but limitations when I have a go at it. It doesn't seem to be bricked as I can still access recovery mode, download mode and it effectively boots, it's only giving me errors.
Here's what happened:
1) I tried rooting it using UnlockRoot PRO. Paid the PRO version, detected the device. Later I find it says the N7000 with 4.1.2 is not compatible so the rooting process was never completed, so I rooted it using Root_SuperSU.0.95.Only-signed and it worked just fine.
2) Everything worked fine, downloaded Andromizer to customize the phone.
3) Changed the DPI size to test it, then went to Developer Options and changed the Animation scales to 0.5 to make it all run faster.
4) Rebooted the device. Once I did, I got nothing but "SystemUI has stopped working" together with "TouchWiz home has stopped working errors".
I checked around the web and so far, what I've found (and tried) is this:
1) There seems to be a bug related to TouchWiz and the Animation Scale option (or perhaps the DPI size option in Andromizer). So I tried to do a wipe data / factory reset through recovery mode.
2) When trying the wipe data / factory reset through recovery mode, I rebooted the phone, only to find the SAME errors after I registered everything.
3) First option that came to mind was to wipe everything and immediatly reinstall the Official JellyBean 4.1.2 firmware (at this point I want to pretty much unroot the device as I didn't know it was going to give me so much trouble). When I tried that, I realized that SUDDENLY, Odin (nor Heimdall) are NOT detecting the phone in download mode. I'm guessing it's because USB Debugging is turned off but, I can't access the phone settings. It's my only logical conclusion, although it should be turned on given I could install PhilZ Custom Recovery later.
4) I search around the web and it says it's a driver problem. So I uninstall everything, run CCleaner, USBDeview to uninstall everything related to the Samsung Galaxy. Reboot. Install drivers again. Reboot. Plug booted phone and let Windows detect the device, installed successfully. Reboot in download mode. Let windows detect the device, installed successfully. Run Odin: DEVICE NOT DETECTED. (It does detect it while it's booted though, only it doesn't work for **** obviously).
I've literally tried everything. I've tried checking for a way to install the firmware via Recovery Mode instead of Download Mode. I've tried checking for a way to remotely access the device and mod the settings from there using ADB, and I get the same problem in ADB, doesn't detect the device.
Also tried to reset settings to normal via PhilZ Custom Recovery which I managed to install later.
Isn't there just a way to reset all settings to normal? Shouldn't a factory reset do this? How can I get SOMETHING to work and try to recover the phone? Any Aroma Recovery Script? Any way to mess with the system folder and modify settings manually via notepad or something since due to the SystemUI / TouchWiz home errors I can't access the phone settings?
I'm barely awake at this point. Can't believe I've stressed myself this much. Please help. This is beyond retarded.
Thank you,
Z
i had the same exact problem just few hours ago.....first of all you should boot into recovery mood by pressing vol up+ home button+lock button until samsung logo shows and then wipe all data/factory reset and wipe all cache partitions..........if that didnt fix it you should try rerooting it againg after re wiping
I read the post but it seems you have done a lot of things and nothing worked. So what is the situation right now? You can boot as normal but cannot get any icons or settings as sysUI and TW crashes?
Try installing GB ROM then wipe/cache first. If good, root GB ROM then do full wipe. Then test ROM for crashing.
If good then install JB rom and test. Let us know.
unable to enter phone setting ？ then just simply look for a secsetting.apk for ur version then replace it n set the permission rw-r--r--
You could use adb to modify your build.prop
Sent from my SGNote
Makrilli said:
You could use adb to modify your build.prop
Sent from my SGNote
Click to expand...
Click to collapse
Bwahahah, now I see why you guys enjoy calling newcomers "noobs".
It was a computer problem. I just reinstalled JB 4.1.2 from my netbook and it worked.
Weird as hell though, given that I updated my GT-N7000 to JB 4.1.2 through Odin in this computer and it never gave me any problems.
I AM going to learn some ADB / Android SDK though. I'd rather learn everything before something like this happens to me again.
I appreciate everyone's concern, and thank you all for it.
nice to hear that you had this one fixed
Glad to hear its working now.
n7000 touchwiz home stopped
Zardonic said:
Bwahahah, now I see why you guys enjoy calling newcomers "noobs".
It was a computer problem. I just reinstalled JB 4.1.2 from my netbook and it worked.
Weird as hell though, given that I updated my GT-N7000 to JB 4.1.2 through Odin in this computer and it never gave me any problems.
I AM going to learn some ADB / Android SDK though. I'd rather learn everything before something like this happens to me again.
I appreciate everyone's concern, and thank you all for it.
Click to expand...
Click to collapse
hi.... im having the same problem as yours. i dont know what to do
lulu2050 said:
i had the same exact problem just few hours ago.....first of all you should boot into recovery mood by pressing vol up+ home button+lock button until samsung logo shows and then wipe all data/factory reset and wipe all cache partitions..........if that didnt fix it you should try rerooting it againg after re wiping
Click to expand...
Click to collapse
I have tried to upgrade my touchwiz to the new one, but got the danger message, would clearing the cache help?
Sent from my SM-N910C using Tapatalk
Hello.
I just successfully flashed CM9 Build 6 on my Galaxy S Plus. It was terrifying.
My problem lies in the fact that i can't seem to get Gapps working. I tried multiple versions, from the latest one to 20120429, which is currently the last one flashed on my phone. The apps don't appear, and trying to use a downloaded Google Play app from the web makes it start, but it just flashes a 'Loading' screen for a split second and then boots me back to the app menu.
Any ideas on what I could do next to fix this?
Have you tried wiping your entire phone and then reinstalling CM9 + gapps (the version provided by arco68)?
It's what I did the first time. Should I flash it again?
You should definitely give it a shot, maybe something went wrong while flashing.
What recovery are you using?
Apparently I had the stock one, that must of been the problem. Didn't document well enough.
I've just flashed 6.0.1.2 and I'll flash everything again once I download all the files.
Yep that was it. It runs as it should now. Thank you for your help.
Good to hear!
Slightly related, please note what's going on in the dev section (here). Certain combinations of recovery software and hardware may brick your phone if you try to wipe data. Playing with your new recovery could be dangerous right now, be careful!
Im currently using a S3 Mini I8190L with Carbon latest ROM. It was all fine and great until I tried to improve a little bit by using swapper2 through this method:
http://forum.xda-developers.com/showthread.php?t=1659231&page=1
Since the ROM documentation said it provided support for swap, I went straight for the swapper2 apk configuration, set it all, HIT ok. After that part, i got 2 fail msgs, the phone froze and i had to restart it.
But it would go straight to a white pixelated screen and never boot into KK or TWRP. All it does is Download mode (btw, battery doesn't recharge, need to use a 2nd device to charge it)
I tried to reflash the ROM but got a "THERES NO PIT PARTITION" error, went on to solving that with i8190l.pit but after flashing it, nothing changes. Still cant flash ROMs, boot to KK or TWRP.
For reference, the "STOCK" firmware is this one: http://www.sammobile.com/firmwares/confirm/22769/I8190LUBAMK1_I8190LZTMAMK1_ZTM/
What should I do ?
Sir,
Please wait until mods will move this thread to the device specific forum for more relevant answers.
Stand by
Good luck