Develop Bugs

Boot loop on miui

well i am a little lost... i tried to update the kernel to the newest version of savaged zen. But got stuck on the white screen, so i went back and wiped both catches again, then i got to the boot animation and now thats looping.. okay so i made a backup before starting but now after wiping everything and restoring the backup is boot looping too. Any suggestions?

Try another kernel. I am using the BCblend kernel from november, it's awesome and very stable. Once you get it booted, go into your advanced wifi settings and set your sleep policy to never.

well... my backup boot loops too... wouldnt the backup have the old kernel?

It's possible your phone doesn't like that kernel either, mine didn't. How long were you running it before flashing the new kernel? I would try at least a couple more kernels and if you still can't get it booted then wipe and start over. What version of MIUI are you running?

In my opinion...if you have a good working kernel do not change it. From what ive seen every custom rom is based off a stock rom that comes with a kernel. Usually only custom kernels that match the rom version work well. So it could be the rom and the kernel dont work well together. One thing is nobody seems to list which kernel version is from which rom. So its hard to tell. Also I think your pri version will mess with compatability also. Basically newest rom versions should work with newest kernels. But if your on an older rom...the older kernels will probably work better. And usually kernels come out (it seems) before rom versions. Like new miui kernel supports 4g, but the rom does not support it yet. Also nandroid? backups should have the kernel also. Not sure bout miui backup. But wiping and installing it fresh usually works well. If not you know the deal..wipe everything..then flash the rom..and start over So.....find a good one...keep it=no issues
Evo - Myn 2.2 RLS 3 - Clockwork - HBoot .76

flash gone wrong? twrp to cwm?

Hey everyone, I had just flashed cyanogen 10 kang with twrp and everything was fine until I decided to try and get the nexus s 4g modem which I had failed at every time before that. I would flash the rom, then gapps, Then the nexus modem patch before the shadow kernel. This time I flashed the shadow kernel before the nexus modem patch and it had apparentally powered itself off (I had left the room) so I tried to boot back into twrp, but it popped up with cwm 5.0 something instead. And the only backups I have are for twrp. . After I looked around in it for a little I tried flashing the rom and gapps again, booted up fine except I don't believe I had any signal. At all.
I tried to find something that would put twrp back onto my phone but haven't had any luck. And for some reason when I booted back into recovery it had changed to cwm 6.0 something. I don't know what to make of any of it. Right now I'm on cm9 snapshot beta 4 i think. I thought it was the one with twrp already in it so I thought I could try and restore my stuff.
Anyone have a remedy for this? I'd really appreciate it. Thank you in advance for your time.

swiftstrike763 said:
Hey everyone, I had just flashed cyanogen 10 kang with twrp and everything was fine until I decided to try and get the nexus s 4g modem which I had failed at every time before that. I would flash the rom, then gapps, Then the nexus modem patch before the shadow kernel. This time I flashed the shadow kernel before the nexus modem patch and it had apparentally powered itself off (I had left the room) so I tried to boot back into twrp, but it popped up with cwm 5.0 something instead. And the only backups I have are for twrp. . After I looked around in it for a little I tried flashing the rom and gapps again, booted up fine except I don't believe I had any signal. At all.
I tried to find something that would put twrp back onto my phone but haven't had any luck. And for some reason when I booted back into recovery it had changed to cwm 6.0 something. I don't know what to make of any of it. Right now I'm on cm9 snapshot beta 4 i think. I thought it was the one with twrp already in it so I thought I could try and restore my stuff.
Anyone have a remedy for this? I'd really appreciate it. Thank you in advance for your time.
Click to expand...
Click to collapse
You have to flash nyankernel or just the twrp zip. And next time when you flash from twrp, you need to pick inject twrp if you don't want cwm.
Sent from my SPH-D700 using Tapatalk 2

not trying to "thread-jack" - but I have a really similar problem (minus the twrp - which i'm not familiar with). Throughout my update to the crespo modem, during the mtd/bml check the phone would reboot into cwm - and I noticed that just like OP, the cwm would change to some 5.0version (not the usual 6 version)....
Here's what I have:
I was on CM Kang 7/30 with shadow kernel
I updated to CM Kang 8/08 (no problems)
I flashed the http://darkierawr.com/Android/Users/...atchcm7AIO.zip and I kept on getting Status 7 errors... I downloaded it a few times with the same result.
Then I saw someone say they flashed the kernel first and then the modem update... so I flashed the http://dl.dropbox.com/u/820341/Shadow-2_CM10_MdmCrp.zip (successful) and then tried flashing the modem update. Got stuck in a boot loop - so I did a battery pull.
Did a cold boot (pressing power) and now the phone "doesn't have a modem" no radio, no signal etc...
Tried it all over again - mounted system - formatted system - flashed 8/08 kang, gapps, then the modem update, and kernel.
my phone boots but no signal. is there a odin version of the modem that I can flash? or does anyone have any ideas?!?!?!
thanks!!

altimuh said:
not trying to "thread-jack" - but I have a really similar problem (minus the twrp - which i'm not familiar with). Throughout my update to the crespo modem, during the mtd/bml check the phone would reboot into cwm - and I noticed that just like OP, the cwm would change to some 5.0version (not the usual 6 version)....
Here's what I have:
I was on CM Kang 7/30 with shadow kernel
I updated to CM Kang 8/08 (no problems)
I flashed the http://darkierawr.com/Android/Users/...atchcm7AIO.zip and I kept on getting Status 7 errors... I downloaded it a few times with the same result.
Then I saw someone say they flashed the kernel first and then the modem update... so I flashed the http://dl.dropbox.com/u/820341/Shadow-2_CM10_MdmCrp.zip (successful) and then tried flashing the modem update. Got stuck in a boot loop - so I did a battery pull.
Did a cold boot (pressing power) and now the phone "doesn't have a modem" no radio, no signal etc...
Tried it all over again - mounted system - formatted system - flashed 8/08 kang, gapps, then the modem update, and kernel.
my phone boots but no signal. is there a odin version of the modem that I can flash? or does anyone have any ideas?!?!?!
thanks!!
Click to expand...
Click to collapse
Try http://marcusant.com/android/epic/modem.bin
Sent from my SPH-D700 using Tapatalk 2

No Signal AOSP, IMEI Zero'd Out. Please Help!

Hello, normally I do lots of research and searching in order to figure out problems for myself, but this one I have been stuck on for weeks.
I am on SGH-T999v, here is my issue.
I am trying to use either the latest 1.5 Spirit Rom, or M4 gummy Rom in combination with KTOONSEZ Kernel from here.
If I try to flash the kernel with latest versions of those roms, my baseband says "UNKNOWN" and my IMEI gets zero'd out.
Also it tells me that I have no sim card inserted. I have tried formatting dalvic/cache before and after installation of kernel as well as fixing permissions.
Both Spirit 1.5 and Gummy M4 work no problem without the custom kernel installed.
Also, on only 1.1 Spirit and M3 gummy, am I able to use the custom KT kernel and still have my signal.
Okay now here is the strange part of the problem.
Currently I am using the custom recovery TWRP that lets me use multiboot from here
And after successfully creating a multiboot rom, I go ahead and install Gummy M4 + Gapps + KT Kernel and boot it up, to find out that it actually works perfectly fine.
My baseband shows up, and my signal connects.
Also the version im using of the recovery menu is V2.11
I am just wondering why is it that the rom + custom kernel doesn't work with a regular flash, and that it only seems to work when I multiboot it?
What I want is to not have to create a multiboot rom in order to use this, I want to actually flash these to my phone.
Please help me, anyone who has any idea of what I am talking about..Sorry if I have not been clear enough. Thank you/.
Edit: I also forgot to mention that I have tried flashing the stock modem after the kernel + rom installation through odin, that did nothing.

[Q] Galaxy Note 3 (n900t) Boot Loop after flashing cyangenmod 11

Hi, new to flashing roms and this might be a noobie question, however, I can't find an answer online. Over this week I have tried to flash cyanogenmod to note 3 the tmobile variant. I have it rooted (thanks to CF-Auto-Root) and it has twrp 2.8 the newest version. I downloaded the newest cyanogenmod rom and gapps into my flash drive and used an adaptar when I tried to flash it to my phone. It successfully flashed and I was excited for the new rom. However, when my phone rebooted into the Samsung Galaxy note 3 boot up screen; the top left of the screen showed Kernel is not seandroid enforcing set warranty bit: kernel. And it just starts bootlooping. I've tried waiting for 30 minutes and that just kept happening. So i decided to boot into recovery and and restore my original rom with twrp. That went fine and now I have all my data back. However, how do I end the bootloop? I watch youtube videos and they all work fine, however, they dont get the bootloop. They even have the same phone with the same carrier. I know its not the bootloader because tmobile doesnt have locked boot loaders. Right now I'm running on 4.4.2 Kit Kat on my note 3. Also I have already went back into twrp after flashing the rom and wiping dalvik and cache. It still didnt work. After I went back in and formated system memory and it still didnt work, so I gave up and did a little research. However, I cant anything relavant online to help me.
Links that I already read: http://forum.xda-developers.com/showthread.php?t=2470599
http://forum.xda-developers.com/showthread.php?t=2609767
http://forum.xda-developers.com/showthread.php?t=2614787

Hi,
I will have your thread moved to your device section.
Good luck!

Superbia Thema said:
Hi, new to flashing roms and this might be a noobie question, however, I can't find an answer online. Over this week I have tried to flash cyanogenmod to note 3 the tmobile variant. I have it rooted (thanks to CF-Auto-Root) and it has twrp 2.8 the newest version. I downloaded the newest cyanogenmod rom and gapps into my flash drive and used an adaptar when I tried to flash it to my phone. It successfully flashed and I was excited for the new rom. However, when my phone rebooted into the Samsung Galaxy note 3 boot up screen; the top left of the screen showed Kernel is not seandroid enforcing set warranty bit: kernel. And it just starts bootlooping. I've tried waiting for 30 minutes and that just kept happening. So i decided to boot into recovery and and restore my original rom with twrp. That went fine and now I have all my data back. However, how do I end the bootloop? I watch youtube videos and they all work fine, however, they dont get the bootloop. They even have the same phone with the same carrier. I know its not the bootloader because tmobile doesnt have locked boot loaders. Right now I'm running on 4.4.2 Kit Kat on my note 3. Also I have already went back into twrp after flashing the rom and wiping dalvik and cache. It still didnt work. After I went back in and formated system memory and it still didnt work, so I gave up and did a little research. However, I cant anything relavant online to help me.
Links that I already read: http://forum.xda-developers.com/showthread.php?t=2470599
http://forum.xda-developers.com/showthread.php?t=2609767
http://forum.xda-developers.com/showthread.php?t=2614787
Click to expand...
Click to collapse
Make sure your getting the ROM from here: http://download.cyanogenmod.org/?device=hlte
Latest TWRP recovery is 2.8.4: http://www.techerrata.com/browse/twrp2/hlte
Gapps: http://wiki.cyanogenmod.org/w/Google_Apps
When in recovery do a factory reset as step 1. Then go into Advanced Wipe, and only leave SD card unchecked. Wipe everything else. Then Format the system. After all that Flash the ROM, then Gapps, and them reboot. If you want you can try CM12. It's been very stable even as a new nightly.
http://forum.xda-developers.com/note-3-tmobile/general/official-cm12-released-t2995099
Seeing: Kernel is not seandroid enforcing set warranty bit: kernel is normal for CM. Don't worry about that.
Hope it works for ya. Enjoy.

I downloaded cyanogenmod and gapps from those websites, but I'll flash twrp again to give it another try. Yea I was goanna install android lollipop but the bootloop gets me every time...
Sent from my SM-N900T using XDA Free mobile app

bobbyphoenix said:
Make sure your getting the ROM from here: http://download.cyanogenmod.org/?device=hlte
Latest TWRP recovery is 2.8.4: http://www.techerrata.com/browse/twrp2/hlte
Gapps: http://wiki.cyanogenmod.org/w/Google_Apps
When in recovery do a factory reset as step 1. Then go into Advanced Wipe, and only leave SD card unchecked. Wipe everything else. Then Format the system. After all that Flash the ROM, then Gapps, and them reboot. If you want you can try CM12. It's been very stable even as a new nightly.
http://forum.xda-developers.com/note-3-tmobile/general/official-cm12-released-t2995099
Seeing: Kernel is not seandroid enforcing set warranty bit: kernel is normal for CM. Don't worry about that.
Hope it works for ya. Enjoy.
Click to expand...
Click to collapse
Welp I went ahead and flash another rom and it worked so I'm guessing I either have the wrong files or something is wrong with my phone. However, dompop works amazingly to thanks for the help!!!

wicked rom will not install.

I've been trying for over a month to get wicked rom installed on my n3 n900t . I'm rooted bootloader unlocked with twrp installed. I've had no issue installing any other rom on this phone I'm currently running alliance 5.0 and resurrection remix 6.0.1 and they work great but I would like to see what wicked is like. ( what it does when trying to install ) OK I have the wicked rom saved to my SD card with 4.4.2 gapps I'll restore my phone to alliance rom which is 4.4.2 and is says in the install it needs to be a 4.4.2 bootloader to install wicked, I'll go into twrp do a full wipe data, delvic,system, wipe it out then install the ROM and gapps package and it'll start to do its thing then get to where it says aramullz xda ( something? ) the progress bar will stop and it'll self boot itself out of twrp and go back to alliance rom and which will be messed up due to doing a full wipe. I like to figure things out on my own that's the fun part but this one's got me. Thanks for any advice.

Did you use terminal or Samsung Phone Info app to verify the bootloader in the phone?

I installed compullsion kernel 4.4.2 before and that failed, tried installing it while flashing the rom and gapps that failed, tried the other older versions of wicked v5 and v4 and v1 they all act exactly the same. I even wiped the whole phone completely cause I got Pissed due to failure ( lol ) flashed a fresh AP in Odin and tried everything again and still failed. I'm in the process of trying to convert the zip file to a tar md5 but having issues that Odin won't except the files cause the ( tar archived ) and I did flash the 4.4.2 bootloader as well. I'm beginning to think wicked doesn't like me.

My bootloader info should be 4.4.2

fastjohnson said:
this the info now which is useless because I'm on alliance 5.0 rom so it originally came from 4.4.2 chainfire zip.
Click to expand...
Click to collapse

Yes, looks like the phone is on 4.4.2 bootloader. Were you able to install the ROM?

audit13 said:
Yes, looks like the phone is on 4.4.2 bootloader. Were you able to install the ROM?
Click to expand...
Click to collapse
No still nothing I've tried everything I even wiped the entire phone installed the B4 Odin files AP and BL and CSC then flash chain fires autoroot file and twrp. The phone was basically stock 4.4.2. I tried all 3 wicked zips V1 V4 V5 and they all reacted the same way. And I already grabbed these files from different locations to make sure I didn't possibly get a bad batch. I've got every rom to flash on this no problem. Pacman, RR, alliance, slimroms, any cyan rom, I've come to terms no wicked for me. Lol

Lol, finally got wicked installed via flashfire. Twrp wouldn't do it. Super happy really fast rom.

What versions of twrp did you try? Just curious.

Using the newest 3.0.2 I think. Btw wicked rom so far is the most stable coolest rom I've experienced so far. I forsee it as my daily.

I have seen reports of some people having issues with 3.0 and higher so I stick with 2.87 for my devices.

No I actually didn't catch that. Besides that it refusing to install the wicked rom I haven't seen very many other issues. Well sometimes when im restoring a rom in twrp when it boots itll sometimes not in stall a lot of Google Play stuff and the UI will crash and I'll have to restore it again. I actually like the look and the button placement better in the version your using.