any jellybean rom i use if i reboot or turn it off then back on it softbricks being stuck at the google logo. i can access fastboot and recovery and flash a stock image but someone inform me why it does this. i love jellybean but cant factory restore everytime i need to boot the phone up
I too am having this issue.
Wipe cache and dalvik cache. Then flash the ROM again. Boot it up.
Sent from my Galaxy Nexus using xda app-developers app
When installing a new ROM you have to do a full wipe, oh and stay away from the franco kernel a lot of people are having problems with it
Mars196 said:
When installing a new ROM you have to do a full wipe, oh and stay away from the franco kernel a lot of people are having problems with it
Click to expand...
Click to collapse
? I don't have any problems with it as many other people are using Franco Kernel on JB and ICS based ROMs... please don't make false comments without any proof.
Related
i have googled this and tried multiple ways of installing it but i always get a boot loop. Whats going on?
Hey if you just want to get your phone back again, just flash another firmware from the one you used. Should start up just fine.
have done already but i actually want to install cyn mod. I managed to get as far as the main screen buit then immediately reboots. I cant find wifi modules for latest doom kernel either they arent in his thread.
FLASH KERNEL FIRST (from cyanogenMOD or doomkernel for CM7 etc)
Than flash cyanogenMOD
any other way will make your phone bootloop.
I think you have to unlock BL via SE in order to flash CM..
of course you would likely broke your warranty.
this based on my experience (I'm a newbie too in the android's world). this is what I've done :
1. unlock BL via SE (not all carriers allowed this!)..
2. flash .42 fw
3. follow the instructions given on CM thread by fxp.
it's worked for me.
goodluck.
I've had this problem before. Did you wipe the delvic cache, wipe data/factory reset and wipe cache partition in CWM before you flashed the update.zip?
It would seem it was a specific version of cm that was making it bootloop the one from dooms thread 7.2.0 works fine and also the one before the latest stable release also worked fine. I however found a problem with the spacebar on the keyboard when using the phone in landscape so am now going to try arconium and doom kernel its a shame really because cm from what i used of it looked really nice.
Try 7.1.0.1.
I got bootloop too with 7.1.0.2
Kuroyukii said:
Try 7.1.0.1.
I got bootloop too with 7.1.0.2
Click to expand...
Click to collapse
Aye thats the one i used but ended up having a problem with the spacebar not working in landscape so am on acronium now which is all good but superuser keeps crashing meh always something eh.
at first im also having the same problem,just follow the instruction by FXP : flash bb56,flash fw.42,flash FXP kernel via fastboot,flash update via recovery,wipe dalvik cache,reboot..
Sent from my LT18i using Tapatalk
I have this exact same problem
I've done everything I was supposed to, I think, and still doesn't work. It boots, shows me the little Android "Welcome!" screen, and before I have time to press anything or begin setting up my device, it reboots into the Cyanogenmod loading screen. I've tried different kernels, different basebands, every time wiping Dalvik cache, etc. and it REFUSES to work. I'm pretty desperate by now because I really wanted to use this ROM so any help is greatly appreciated.
I also followed precisely rashid.fairus' instructions and it still does the exact same thing.
You need to Wipe Data, Cache and Dalvik ----- BEFORE AND AFTER FLASH
I do this here, and positive feedback
Velcis Ribeiro said:
You need to Wipe Data, Cache and Dalvik ----- BEFORE AND AFTER FLASH
I do this here, and positive feedback
Click to expand...
Click to collapse
Sometimes you DON'T WIPE ANYTHING AT ALL. Just flash CM and Google.
Works for me on Xperia Acro S.
gabantarung said:
Sometimes you DON'T WIPE ANYTHING AT ALL. Just flash CM and Google.
Works for me on Xperia Acro S.
Click to expand...
Click to collapse
Only when you upgrade to a later version of the same ROM.
Sent from my Xperia Arc S using xda premium
Velcis Ribeiro said:
You need to Wipe Data, Cache and Dalvik ----- BEFORE AND AFTER FLASH
I do this here, and positive feedback
Click to expand...
Click to collapse
Wipe dalvik and cache when upgrading to later version, wiping data will reset phone to factory settings and you lose all personal data.
僕のLT18iから送られてきた
I was running Paranoid Android 2.99.
Okay, heres what I have done. May be the worst mistake I could do, I chose /system to format in recovery after installing the custom kernel packed in the zip of Paranoid Android by extracting it separately. And now, what I get is a phone stuck in bootloop.
After this I tried the following:
Restoring a NanDroid backup of my HTC Sense, and I know it won't work because I was using Titanium KISS kernel. Now, when I want to flash a new kernel through HTC All in one toolkit, I get a <unknown error>. The kernel of Titanium required for sense is not flashing in my phone. In fact, no kernels are flashing in the phone through the toolkit.
The phone is not bricked, because the LED glows, I can go into Recovery and Bootloader mode.
Please help me, what should I do??
First of all: Are you GSM or CDMA?
Second of all (if you are GSM) YOU SHOULD NOT FLASH THE KERNEL THAT WAS PACKED INTO THE ROM! you should download the Hellboy kernel, the latest (i think it is 20121215) and flash that.
Yes, I made that mistake. I flashed the boot.img, and now I am dead! X(
I am on GSM. Any fix? Please!
techie.anish said:
Yes, I made that mistake. I flashed the boot.img, and now I am dead! X(
I am on GSM. Any fix? Please!
Click to expand...
Click to collapse
Bootloops are nothing
Just flash the kernel and u are good to go
Sent from my One V using xda premium
techie.anish said:
I was running Paranoid Android 2.99.
Okay, heres what I have done. May be the worst mistake I could do, I chose /system to format in recovery after installing the custom kernel/QUOTE]
well.. you missed a lot of things here
like:
boot into recovery and do:
factory reset
wipe cache
wipe dalvik cache
and then wipe system
after that, flash the rom ( you didn't stated this either).
then boot into bootloader and flash the kernel hellboy.
reboot
if this doesn't help, do the followings:
go to bootloader
flash the kernel again
go to recovery
do:
factory reset
wipe cache
wipe dalvik cache
wipe system
install rom again.
reboot
one of these two should work just fine. your phone is not bricked or unfunctional. don't worry!
Click to expand...
Click to collapse
Flashing the kernel gives a sort in the cmd "Malformed 1 byte"
Now
Sent from my MT11i using xda app-developers app
techie.anish said:
Flashing the kernel gives a sort in the cmd "Malformed 1 byte"
Now
Sent from my MT11i using xda app-developers app
Click to expand...
Click to collapse
redownload the kernel once more
oh sorry, my stupid mistake!
i was flashing it in HBOOT mode... lol!
sorry, once again :embarassed:
cybervibin said:
Bootloops are nothing
Just flash the kernel and u are good to go
one of these two should work just fine. your phone is not bricked or unfunctional. don't worry!
Click to expand...
Click to collapse
neither of them are working for me.. dont know what to do
Hey guys so this is weird... every time I flash an AOSP 4.1.2 ROM (CM10, paranoid 2.55, slimbean) it ALWAYS ends up in a bootloop. Like the bootloop isnt like I had it on sgs i9000. It gives a short, weak vibration while on boot animation screen. It doesn't bootloop if I upgrade to AOSP 4.2.1 but bootloops when doing 4.1.2... yes I did wipe data, (not /data/media) wiped system, cache, dalvik before flashing the rom.... please help
Sent from my SGH-I747M
Helloworld294 said:
Hey guys so this is weird... every time I flash an AOSP 4.1.2 ROM (CM10, paranoid 2.55, slimbean) it ALWAYS ends up in a bootloop. Like the bootloop isnt like I had it on sgs i9000. It gives a short, weak vibration while on boot animation screen. It doesn't bootloop if I upgrade to AOSP 4.2.1 but bootloops when doing 4.1.2... yes I did wipe data, (not /data/media) wiped system, cache, dalvik before flashing the rom.... please help
Sent from my SGH-I747M
Click to expand...
Click to collapse
Maybe something wrong with how you rooted your device?
laserlight959 said:
Maybe something wrong with how you rooted your device?
Click to expand...
Click to collapse
Nope, because I was running rooted stock before flashing cm10. Right now I'm running rooted stock with ktoonz kernel.
Sent from my SGH-I747M
dear all,
please am facing a very bad problem and i need urgent help.
every time i wanted to flash a custom rom, to flash a stock rom, re-root the phone.
i mean that if i was in a custum rom and want to change the rom i stuck on the sony logo which force me to re-do all the first process (flash a stock rom, re-root the phone),
well my problem and the main question is... what am doing wrong?!?! please heeeeeelp.
When you install a custom rom install the kernel provided with that rom and read the instruction on that specific rom how to install
Sent from my LT26i using xda premium
oache said:
When you install a custom rom install the kernel provided with that rom and read the instruction on that specific rom how to install
Sent from my LT26i using xda premium
Click to expand...
Click to collapse
am doing all the steps mentioned, and am still on locked boot loader.
thats your problem you cant have custom roms on locked bootloaders.
when you install other custom roms you should follow those steps
factory reset
cache partition wipe
wipe davlik cache (cwm>advanced)
(i also format system but its optional)
install rom zip
reboot... i do this and i have never stuck on sony's logo
soldiers33 said:
thats your problem you cant have custom roms on locked bootloaders.
Click to expand...
Click to collapse
Yes you can but only stock based roms. Which are you trying to flash?
Sent from my 4.2.2 Xperia S via Tapatalk
devilakos said:
when you install other custom roms you should follow those steps
factory reset
cache partition wipe
wipe davlik cache (cwm>advanced)
(i also format system but its optional)
install rom zip
reboot... i do this and i have never stuck on sony's logo
Click to expand...
Click to collapse
wow thanks it worked after factory reset, i never format my phone before installing a custom rom, i thought while installing the custom rom it writes formatting system, wiping cahe.. etc... though i thought i do automatic
really thanks for helping
Ben36 said:
Yes you can but only stock based roms. Which are you trying to flash?
Sent from my 4.2.2 Xperia S via Tapatalk
Click to expand...
Click to collapse
am flashing XZXperience v2 rom, well as i noticed and a friend before your post figured it out, i must factory rest.. i really worked and didnt stuck on sony logo
thanks all for helping and replying me
this forum rooooooocks
I have tried every method I can think of to get 4.3 to play nice with my phone. I have used Odin to flash stock and twrp, tried cwm recovery, tried beanstalk, hellybean, cm, and aokp. I changed twrp settings and infamous wipe. Everything I do always results with my phone getting stuck on the boot animation. Even if I clear caches, it will boot and get to the upgrading apps screen and then freeze and reboot and again stuck on the boot animation.
4.1.2 gets stuck on the kernel boot for me, 4.2.2 doesn't work with BT correctly. So frustrating.
Any suggestions are welcome.
4.3
dkrcubsfan said:
I have tried every method I can think of to get 4.3 to play nice with my phone. I have used Odin to flash stock and twrp, tried cwm recovery, tried beanstalk, hellybean, cm, and aokp. I changed twrp settings and infamous wipe. Everything I do always results with my phone getting stuck on the boot animation. Even if I clear caches, it will boot and get to the upgrading apps screen and then freeze and reboot and again stuck on the boot animation.
4.1.2 gets stuck on the kernel boot for me, 4.2.2 doesn't work with BT correctly. So frustrating.
Any suggestions are welcome.
Click to expand...
Click to collapse
Twrp 2.6.10 is the minimum. I am using 2.6.30. 2.6.00 will not work. Also wipe everything but SD. That includes android secure and preload.
stormannorman said:
Twrp 2.6.10 is the minimum. I am using 2.6.30. 2.6.00 will not work. Also wipe everything but SD. That includes android secure and preload.
Click to expand...
Click to collapse
Thanks, but I've tried all that.
Sent from my SGH-T989 using Tapatalk 4
dkrcubsfan said:
Thanks, but I've tried all that.
Sent from my SGH-T989 using Tapatalk 4
Click to expand...
Click to collapse
Twrp version 2.6.3.0 has bugs and is causing issues for a lot of people.
Make sure you use 2.6.1.0 and see how it goes.
Sent from my cellular telephone
kj2112 said:
Twrp version 2.6.3.0 has bugs and is causing issues for a lot of people.
Make sure you use 2.6.1.0 and see how it goes.
Sent from my cellular telephone
Click to expand...
Click to collapse
I have had Zero issues with 4.1 or 4.2 never bricked my phone---- until 4.3 I will tell you how i solved my problems - I have no boots, to 4.3 working but issues with data corruption and gapps crashing random apps crashing, finally after reading and reading i solved it.
1. Flash TWRP 2.6.1 (NOT 2.6.0, not 2.6.0.4 and especially NOT 2.6.3) any other recovery will not work properly - yes for some it may but some people seem to have some of the same problems.
2. Wipe data, Davlik, Cache and the prior rom. it has to be a clean wipe/flash
3. Flash Rom of choice (Black Liquid smooth is awesome)
4. Flash Standard gapps 08/13 (dont get fancy yet and flash slim gapps or inverted, just use the tried and true basic to get it working)
5. let the damn phone rest and settle 10 min minimum.
6. reboot to recovery, wipe Davlik and cache for good measure and fix permissions, reboot and enjoy.
dkrcubsfan said:
I have tried every method I can think of to get 4.3 to play nice with my phone. I have used Odin to flash stock and twrp, tried cwm recovery, tried beanstalk, hellybean, cm, and aokp. I changed twrp settings and infamous wipe. Everything I do always results with my phone getting stuck on the boot animation. Even if I clear caches, it will boot and get to the upgrading apps screen and then freeze and reboot and again stuck on the boot animation.
4.1.2 gets stuck on the kernel boot for me, 4.2.2 doesn't work with BT correctly. So frustrating.
Any suggestions are welcome.
Click to expand...
Click to collapse
if twrp keeps giving you problems like these maybe try doing it from cmw. ive read it gives way less problems than twrp:good:
Decimus Meridius said:
I have had Zero issues with 4.1 or 4.2 never bricked my phone---- until 4.3 I will tell you how i solved my problems - I have no boots, to 4.3 working but issues with data corruption and gapps crashing random apps crashing, finally after reading and reading i solved it.
1. Flash TWRP 2.6.1 (NOT 2.6.0, not 2.6.0.4 and especially NOT 2.6.3) any other recovery will not work properly - yes for some it may but some people seem to have some of the same problems.
2. Wipe data, Davlik, Cache and the prior rom. it has to be a clean wipe/flash
3. Flash Rom of choice (Black Liquid smooth is awesome)
4. Flash Standard gapps 08/13 (dont get fancy yet and flash slim gapps or inverted, just use the tried and true basic to get it working)
5. let the damn phone rest and settle 10 min minimum.
6. reboot to recovery, wipe Davlik and cache for good measure and fix permissions, reboot and enjoy.
Click to expand...
Click to collapse
This. 2.6.1.0 twrp.
Sent from my cellular telephone