Hello I am on Check Rom v3 w/ Abyss Kernal v3 and I'm trying to change my system sounds, like unlock and lock.
I tried changing them, but my phone went into a boot loop. How do I fix this situation? I tried setting the correct permissions.
Any ideas? I eventually had to completely reflash rom, which wipes everything.
Ok an update on the situation, after I installed checkromv3 again and it wiped everything, I tried it again and know it works. So weird. I think it had something to do with the cache or something, which I tried to clear.
ok back to boot loops again after i did a nandroid backup. could anyone help?
Related
Hey guys i need some serious help
Im coming from cm5.0.8.1,froyo radio, pershoots kernel. I tried to go to jand-o-rama. final 9.
So i did a nandroid back + clockworkmod backup. Now i wiped evrything,dalvik-cache, cache, restore/factory settings and battery. When i was flashing kand-o-rama everything went well except the last part were i think it was flashing the kernel. It said error(couldn't remember the code). So i did another full wipe and tried to restore to my previous version but when i did its just stuck on the colored X with the unlock sign. I tried several full wipe/restore with no luck. I also tried to full wipe/restore factory settings then reboot but still wouldn't go past the bootloader.
Also tried to reinstall fastboot but still the same.
Im not good with ADB so pls if you can help me with my dilemma.
Pls pls..
Thanks!
I downloaded and installed Rodriguezstyle MiUi rom yesterday, following all the install procedures(the double wipes and what not). But when I go to use it, it sometimes worked and it sometimes would crash and reboot. It was very weird because instead of just rebooting to the os, it would give the Nexus X then, after going no further, reboot again giving the Nexus X and reboot again and so on. This happened with every MiUi rom I installed, but not with the Evil Desire rom I have now. I really like MiUi, do you guys have any fix?
Specs - Nexus One w/ 5.12 Korean Radio
Trying Rods 1.6.6
Have you overclocked it with setcpu? You might want to turn that off and see what happens. I assume you did a complete wipe first btw?
I did wipe and my rom crashes before I can install setcpu
MIUI 0.11.5 + English Pack
I am using MIUI 0.11.5 Deodexed + English Pack. No issues so far. Its perfect.
Why are you making multiple useless threads about this?
@ inferus
could you post the site you got it from. And I have also tired the bundle, which did not work either
MIUI stock
Here you go
http://forum.xda-developers.com/showthread.php?t=789566
I tried all three of those and on every one my phone gets stuck in the boot loop. I have tried everything, factory wiping, cache wiping, dalvik wiping, battery wiping, and clear storage. is there any way I can completely delete the operating system off my phone so I can freshly install the new rom of MiUi. This is bootloop also happens to me when I flash micromod and cyanogen. THIS IS SO FRUSTRATING! does anyone have the same problem too
this static X bootloop also happened a lot on KoR. its based on CM6.0 but maybe this solution will also fix your problem:
http://forum.xda-developers.com/showpost.php?p=8023620&postcount=4383
@pseudoheld
You are the freaken man, however, is this a permanent fix or only temporary?
I spoke too soon, when I do HBoot in the boot loader, sometimes it skips going to the recovery and goes into the boot loop. Is there any way to update the bootloader
paintmandoo3993 said:
I tried all three of those and on every one my phone gets stuck in the boot loop. I have tried everything, factory wiping, cache wiping, dalvik wiping, battery wiping, and clear storage. is there any way I can completely delete the operating system off my phone so I can freshly install the new rom of MiUi. This is bootloop also happens to me when I flash micromod and cyanogen. THIS IS SO FRUSTRATING! does anyone have the same problem too
Click to expand...
Click to collapse
I was not referring to the other links on that post. I installed the stock hosted directly on that post. Also provided a link below for your convenience
http://djmcnz.batteryboss.org/MIUI/deodexed/miui-n1-0.11.5-deodexed-signed-PROPER.zip
And the English pack.
http://forums.miui-dev.com/viewtopic.php?f=5&t=39
i will keep you posted, again
and same problem. Bootloop and whenever I go to the HBoot and try to boot into recovery I get the boot loop again and it wont even enter recovery, I gotta pop the battery
what recovery did you use
Hi, I have installed seeARMS ROM and followed his instuction. I have kept the JL2 modem and speedmod kernell (I was already on speedmod). I have tried 2 methods to install. The seeARMS.UGJL2.v0.4.zip with the seearms file and the CWM.
Both install went OK and I even had a congratulations screen. The problem is when the phone reboot it stays on the boot animation and get stuck there. I have tried 2 different boot animation and the same happen.
I have no problem to restore my data since I had backup but I would like to have the seearms ROM. Any idea?
Also a side question, can we get the new CK1 modem with seearms?
Richard
Have you been wiping your phone before flashing the rom? I have been having issues like you describe only when i flashed a rom w/o wiping.
(In CWM Recovery: wipe data/factory reset, wipe cache and advanced -> wipe dalvik cache)
No. I did not wipe. I am not interested in the new ROM if it mean wiping. I made a test by downloading a boot animation app. I trying 2 different boot animation and had the same result. The boot animation play with no sound but I have a vibration during boot and then nothing. Eventually it go back to the animation, vibrate and this repeat until I restore the backup.
I am wondering if tehre is something special about the Bell Canada boot animation?
Can I use the seearms without any boot animation folder?
I don't think it's a problem about the boot ani in particular.
I am not very familiar with the rom, since i have another device. In the seearms rom thread the dev mentioned two versions of the rom, one that requires wiping and one that does not.
So i guess it could be working out to flash the latter w/o wiping. But in my expirience those things rarely work out that way.
There might be incompabilities with the config data left behind by the rom installed before, or other possible issues.
Only way to be sure that those things aren't blocking anything is to wipe the phone and do a clean flash.
Personally i always do it that way. And if i like the rom, and choose to use it, it is always possible to get back all the apps and settings back with titanium backup and/or syncing them back.
But as always before wiping, if you choose to do so, please be sure to have a full nandroid backup, in case you want to go back, or something goes wrong.
I will try the wipe version
What rom were u on before seearms
Sent from my GT-I9000 using XDA Premium App
I was still on stock (froyo 2.2). Actually still on it today
You were right. The wipe version worked fine. I have now to decide to keep it or not...lol
ROM is awasome was worth well the trouble.
Glad it worked out for you - have fun with the rom
Sent from my Desire Z
Hey,
so I just tried to reinstall Doc's Master ICS V12. Wiped Cache, Data and Dalvik. I was already running V12, and so I had all the prior requirements to flash it. I wanted a clean install as it was starting to lag though. However, this time, I made the mistake of formatting the system AFTER I flashed, and now it's bootlooping. It flashes the Samsung logo, then the Icy Glitch (kernel) logo, then shows a brief script in CWM and then keeps repeating this pattern. I tried to three button combo to boot back to recovery, but it's not working (I recall it working way back). Is there any other way that I can get back to recovery?
[Edit] Got it to work, delete please!
So I've been attempting to install a rom, ANY rom on my phone and the results always seem to be the same. I boot into TWRP, wipe then install the rom. On reboot, the phone loads up the initial (black) samsung screen. Then buzzes twice and reboots. It will do this infinitely. It happens with any rom I've tried flashing. It has to be something I am missing or doing wrong. Does anyone have an idea what it is? I've even gone as far as completely wiping, odin in a stock image and then adding TWRP again. I just can't seem to figure it out.
re: bootloops
Tharkys said:
So I've been attempting to install a rom, ANY rom on my phone and the results always seem to be the same. I boot into TWRP, wipe then install the rom. On reboot, the phone loads up the initial (black) samsung screen. Then buzzes twice and reboots. It will do this infinitely. It happens with any rom I've tried flashing. It has to be something I am missing or doing wrong. Does anyone have an idea what it is? I've even gone as far as completely wiping, odin in a stock image and then adding TWRP again. I just can't seem to figure it out.
Click to expand...
Click to collapse
You need to ODIN flash the stock original official COG2
firmware & odin flash cf-autoroot and the twrp recovery
before flashing the zip file rom.
Once that's done you can flash any N910T zip file rom in
twrp recovery without any issues.
Make sure to do a full wipe in twrp before you flash any
zip file rom to avoid bootloops and or getting stuck on
the samsung boot logo screen and be sure to do a full
and complete wipe which includes:
"System, Data, Cache, Dalvik Cache and last but not
least do a factory reset.
Good luck,
Have a great day!
Tharkys said:
So I've been attempting to install a rom, ANY rom on my phone and the results always seem to be the same. I boot into TWRP, wipe then install the rom. On reboot, the phone loads up the initial (black) samsung screen. Then buzzes twice and reboots. It will do this infinitely. It happens with any rom I've tried flashing. It has to be something I am missing or doing wrong. Does anyone have an idea what it is? I've even gone as far as completely wiping, odin in a stock image and then adding TWRP again. I just can't seem to figure it out.
Click to expand...
Click to collapse
i dont know if we are having the same problem but try installing the original firmware via odin and see if that works. if it does not then we have the same problem and i dont know how to fix it, now i am stuck with my S4 wait for help from someone to help me fix my note 4