I am using the Note 10.1 N8000 and i have just rooted earlier today and installed the latest CWM 6.0.3.6 Touch version. I can access it fine and cleared the cache and dalvik cache as instructed in the ROM thread. But when installing the ROM itself, there is freezing when i've reached the 3rd or sometimes the 4th step. I can't keep using the volume keys (as i've read that sometimes using the touch in CWM can cause freezing issues) in the Aroma menu, as i can't see which button is being selected (no highlighted buttons, so i can't differentiate which button is selected).
Just to see if this isn't a bug with the ARHD 9.0 or its bundled Aroma, i've also tested the Omega ROM and there is again freezing in the Aroma menu, after a few steps, sometimes at the very last step.
I would really appreciate some help if someone could figure out why i can't go through the Aroma installer without freezing. Basically, i'm now stuck wth my stock 4.1.2 Touchwiz ROM.
Some times Aroma freeze with official CWM for me too, try using a diferent recovery
Try:
PhilZ Touch [CWM Advanced Edition] - http://forum.xda-developers.com/showthread.php?t=2202714
Or
TWRP Touch Recovery - http://forum.xda-developers.com/showthread.php?t=1851548
Hope it helps
Sent from my GT-N8013 using XDA Premium HD app
Well known problem just run install again.
I find sometimes doing the basic no add on installs followed by whatever you want install works .
Related
So, I tried to root this phone and I used SuperOneClick and successfuly rooted it.
Afterwards, I downloaded ROM Manager and installed the nightly 53 from Cyanogenmod 7.
I checked Wipe Data & Cache, Wipe Dalvik Cache;
Afterwards, it went to the clockwork recovery; (the orange screen) installed it successfully from the SD card;
Afterwards, Cyanogenmod didn't boot correctly and got looped so i had to pull the battery; then restarted;
it loaded correctly but welcomed me with a series of force closes;
THE PROBLEM:
1. wi-fi doesnt work; when it restarts, it resets all the accounts and settings i've worked on;
2. the orange clockwork recovery mode won't start; instead, it goes to android system recovery <3e>; at that; there are four options that i can go up and down to wipe data/factory reset and all those options
but cannot click on the option; the power button doesn't do anything; the home button makes it disappear;
3. when i go to the terminal; su doesn't work; it goes permission denied;
rom manager won't restart into flash recovery to install new nightly;
so what have i done? what do i do?
I would just like to go back to stock;
Why don't you try posting this in the nightly thread or read a little. Your posting in the wrong place.
Sent from my Nexus S using Tapatalk
I'm guessing you won't be able to, but try turning on the phone by holding the power button and volume down. There's a chance this will take you to recovery, at which point you can wipe and re-flash.
Technically, rom manager only does a "fake" flash of cwm, so that's why it probably will not.
Otherwise, you can probably use adb somehow, but that's outside of my knowledge.
Had the same issues, but you shouldn't use nigh builds as your main rom. if you do use build 105
cm 7 gone wrong
Did you do nandroid backup? If so boot into cwm recovery and restore it ,if you didn't go here http://forum.xda-developers.com/showthread.php?t=1048274 follow the directions if you still have issues you can pm me.
If you can access ROM manager try flashing recovery
If I helped in anyway feel free to thank me
Did you install cwm using nvFlash or rom manager? If you didn't install cwm using nvFlash you will need to do that first. Using rom manager is only a "fake flash" for our phone and the recovery is only temporarily installed.
Sent from my LG-P999 using XDA Premium App
Read the nightly thread from around when 53 came out. Several people had this issue, myself included.
Solution is to just flash a different nightly on top of 53.
Sent from my LG-P999 using XDA Premium App
dnichols4 said:
Read the nightly thread from around when 53 came out. Several people had this issue, myself included.
Solution is to just flash a different nightly on top of 53.
Sent from my LG-P999 using XDA Premium App
Click to expand...
Click to collapse
But first u MUST install cwm with nvFlash
Sent from my LG-P999 using XDA Premium App
Got to use NV flash that will fix your problem
Sent from my LG-P999 using XDA Premium App
yuppp that nvflash is the first step, never use rom manager to flash cwm, im my opinion rom manager is garbageeee, i never use it
Thread moved to proper forum.
I just flashed MIUI (latest version) and my DS is restarting repeatedly.I was at stock ROM before and i had factory reset it before I flash MIUI.
Anyone knows what happened?
EDIT: sorry for spamming...i got to CWM and i format again and it worked
ps. greate job with the ROM
are you using clockwork recovery?
barkermichaelj said:
are you using clockwork recovery?
Click to expand...
Click to collapse
would recommend that you install EXT4 recovery rather than CWM
simply download file onto SD
boot into CWM
and flash ZIP file
CWM works just fine, you just need to make sure you wipe everything before flashing new ROM, ie data, cache, dalvik cache, etc, then all is good
Just wanted to add that I to ended up in a bootloop, and I've had miui 1.8.5 installed since it came. It stopped after about 10 reboots. Dunno know what's up, had a lot of FC's as well these last few days.
Looking forward to tomorrow for am update! Cheers!
Sent from my HTC Desire S using XDA App
I also had some problems with 1.8.5 version (random reboots). I am still using the 1.7.29 version that is working great. Only theme chooser FC's.
all aroma roms brick my samsung infuse . android lays down with red triangle . what does this mean ?
What cwm recovery do you have? And on what rom are you currently?
Sent from my sweet & buttery Infuse
Take your battery out and put it back in. Then do the 3 finger back to cwm and you can flash a ROM that doesn't require aroma.
jb cwm 6. im able to flash any rom (zip) just not aroma i was using miui until aroma . it fails to change permissions
at end of install . so for now in usng cyber rom
I had the red triangle too. Thought I had a paperweight. Had to do several wipes then I started back at Stock with Heimdall and moved back up to JB. Seemed one or two of the Aroma zip were not compatible with JB. Now unless the Aroma has JB in its name, I don't touch it.
Sent from my SGH-i997 using xda premium
I tried to flash CNA today and had that issue.
Not sure if it had to do with selecting report error, show log or rebooting into recovery (something tells me it may have been the reboot).
I wiped everything manually, then went through the installer, selected full wipe and install went through.
Sent from my sweet & buttery Infuse
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
I succesfully added clockwork recovery, and installed the cyanogen mod 10.1 (4.2.2) to my phone, however when I click reboot, it gets stuck on the Samsung Logo
I then took the battery out and did a dalvic cache clear but the same issue occured... My install was succesfull, its just that it gets stuck on the Samsung Logo...
what have I done wrong?? Should I try install a different mod?? Or have I bricked my phone?? Or is there a foolproof way of installing a mod using Odin??
PS: (additional info)
I renamed the mod file before installing if that helps
I have no backup files
the only thing I can access on the phone atm is the Recovery Mode and Download Mode...
You would have backed up your previous rom..try fixing permissions....if not check cynogenmod is for your device or not.... If not download your device os reflash it by installing stock recovery.
Sent from my Micromax A110Q using xda app-developers app
I dont want to hijack this thread, but I have basically the same problem. I rooted my GT-I9300 phone and all was well, until I ran "NoBloat" to remove unwanted apps. Thereafter it runs up to the Samsung logo, then I get the following messages in succession: "Unfortunately messaging has stopped", "Unfortunately the process com.android has stopped", "smartcard service has failed" and "unfortunately the phone has stopped". I removed the battery, tried to flash the ROM again using the standard Samsung.tar file to restore to factory settings, but it made no difference. I am able to read the S3 files when linked to my Desktop and I can get it into download mode. I have run out of ideas and need help from the clever members.
If you get force closes fix permissions
Hit thanks if I helped
Sent from my Xperia Live with Walkman using xda app-developers app
Firstly, cwm doesn't work. Its garbage. I've semi bricked my phone well over 10 times trying to flash cm on it with cwm. Install goomanager and install TWRP to flash.
Secondly, once into TWRP recovery. Go to wipe>advance wipe> and select delvik cache, data, cahce, storage. Then go back to TWRP home and install the cm 10.1 and also the gapps package.
Sent from my SPH-L710 using xda app-developers app
Jeanrick said:
I dont want to hijack this thread, but I have basically the same problem. I rooted my GT-I9300 phone and all was well, until I ran "NoBloat" to remove unwanted apps. Thereafter it runs up to the Samsung logo, then I get the following messages in succession: "Unfortunately messaging has stopped", "Unfortunately the process com.android has stopped", "smartcard service has failed" and "unfortunately the phone has stopped". I removed the battery, tried to flash the ROM again using the standard Samsung.tar file to restore to factory settings, but it made no difference. I am able to read the S3 files when linked to my Desktop and I can get it into download mode. I have run out of ideas and need help from the clever members.
Click to expand...
Click to collapse
I think that bloatware app has taken away crucial files needed to keep the stability of an app up...
I don't know what I would do to fix that...
PS: please message me the samsung.tar file
dalton912 said:
Firstly, cwm doesn't work. Its garbage. I've semi bricked my phone well over 10 times trying to flash cm on it with cwm. Install goomanager and install TWRP to flash.
Secondly, once into TWRP recovery. Go to wipe>advance wipe> and select delvik cache, data, cahce, storage. Then go back to TWRP home and install the cm 10.1 and also the gapps package.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
if you dont like cyangenmod why did you brick your phone 10 times, why did you even go on after the second brick?
I love cm. I dislike cwm. I wanted the 4.3 jb on my phone.
Sent from my SPH-L710 using xda app-developers app