Database Users

Checkrom v7

I've always been happy with Checkrom. My previous ROM only lasted 4 hours, so when I saw V7 coming out I immediately flashed it.
After I succesfully flashed it I found out that the kitchenpro app didn't work and later I read that development was stopped. Not even swype which was part of the original samsung.
I now want to flash another ROM, but am afraid to follow the wrong procedure and brick it. It seems I can't even do a factory reset without the risk of bricking it.
I will never flash a checkrom product again.
Can I go into recovery and just flash wanamlite? Does it even work, as it's the standard recovery and not the full CWM?
No (extra) risk of bricking it?
I would appreciate a straightforward answer...

Another checkrom thread..
Sent from My Samsung Galaxy S2 running Paranoidandroid Rom.What else if not?=P

No, a direct question for answer I can't find anywhere.
I've always been helpful in fora on subjects I knew much about. Please, please refrain from answering if you don't know the answer or don't want to give it.

Look at the forum on www.checkrom.com. The instructions of flashing a kernel through Odin and a new rom are written in the V7-section.
Good luck
Sent from my GT-I9100 using xda app-developers app

Simply flash a safe kernel i.e. siyah kernel, reboot in to recovery and flash a rom(might want to do a full wipe beforehand) or restore a backup.
Good luck, this worked out for me.

frater said:
I've always been happy with Checkrom. My previous ROM only lasted 4 hours, so when I saw V7 coming out I immediately flashed it.
After I succesfully flashed it I found out that the kitchenpro app didn't work and later I read that development was stopped. Not even swype which was part of the original samsung.
I now want to flash another ROM, but am afraid to follow the wrong procedure and brick it. It seems I can't even do a factory reset without the risk of bricking it.
I will never flash a checkrom product again.
Can I go into recovery and just flash wanamlite? Does it even work, as it's the standard recovery and not the full CWM?
No (extra) risk of bricking it?
I would appreciate a straightforward answer...
Click to expand...
Click to collapse
First off, wise decision...
With respect to getting out of this, you want to flash a 4.0.3 based ROM. Don't go for a 4.0.4 based one quite yet, regardless of recovery type, if you're after a quick and safe fix.
You want to flash Siyah Kernel first, and then flash the ROM from there.
Siyah Kernel can be flashed via ODIN (flash the TAR as a PDA file).
Then go about your procedure to flash as usual. As above I'll re-iterate, don't flash a 4.0.4 based ROM yet (LQ5 or LQM I believe), as these are not always 100% safe in all scenarios.
You're much better to stick away from these for now.
Again, I have no idea why "developers" are going about releasing ROMs which are based on these kernels, without clear and noticeable warnings about what people are getting into...
Oh well... Hope it goes well, just follow this and you'll be fine.

Use Odin to flash siyah,
then use siyah's recovery to install new rom

zzkonzz said:
Use Odin to flash siyah,
then use siyah's recovery to install new rom
Click to expand...
Click to collapse
Exactly what Pulser has already said. Why repeat it again?
Sent from my GT-I9100 using Tapatalk 2

Thanks all....
Now not on checkrom anymore...

It should be noted that Leo, the main dude, says on Checkrom.com:
"No more ROM development for SGS2.
On that note i am closing the thread."
...and slammed the thread closed here on XDA too!

The last time I used Odin was when I bought my SG2. Since then I flashed all my different ROMs with CWM.
Although I'm glad I'm not using checkrom anymore and never will because of the way they stopped their development I do have to admit it had more than decent battery life (their 4.04 version).
I‘m currently on wanamlite and after 2 hours I'm already on 60% :-(
I used to have cyanogenmod 7 on my HTC HD2?
It might be an idea to try 9 or 10

Check out ParanoidAndroid. I'm getting about 30 hours off of the battery.
Sent from my GT-I9100 using xda app-developers app

Very bad form closing the threads when quite a number of people had flashed the new checkrom with the promise of a fix. They could have at least fixed the kernal issue rather than just abandoning it. Very disappointed. Going to try to flash the kernal via ODIN if I can remember even how!

Nexus 7 kernel issues...

I posted this over at rootz earlier today and didn't get any bites so I figured I'd give it a shot over here.
I may be the only one in the world experiencing this problem. Looked around quite a bit and don't see any sign of others having this issue... Anyway, my N7 doesn't seem to like it when I flash a new kernel. I've tried several different kernels and when ever I flash one my display will not wake up once it times out or if I turn the display off manually. Once the screen goes dark i have to hold the power button down and reboot. I have zero issues with custom kernels as long as they are baked into the rom. I typically wipe cache and dalvic after flashing kernels...
Sent from my Galaxy Nexus using xda app-developers app

Little bump here... 130 views and not a peep... :-/

scram99 said:
Little bump here... 130 views and not a peep... :-/
Click to expand...
Click to collapse
youre experiencing "sod", which is a fairly common problem with android 4.2.1 source code(not as common on the n7 as the gnex, but common enough). do you flash the kernel with the rom or do you flash the kernel separately?

This happens after switching out the kernel on any ROM I've used. Have not flashed a different kernel at the same time I flashed a ROM. I don't think that will make a difference. I can however flash kernels over my stock rooted backup... I don't know. Just weird and bums me out being limited like this...

scram99 said:
This happens after switching out the kernel on any ROM I've used. Have not flashed a different kernel at the same time I flashed a ROM. I don't think that will make a difference. I can however flash kernels over my stock rooted backup... I don't know. Just weird and bums me out being limited like this...
Click to expand...
Click to collapse
I would just factory reset and start from scratch. Do you have any settings set like UV??
Sent from my Nexus 7 using xda premium

I have tried flashing back to stock, relocking and starting from scratch. I do not undervolt...
A few good folks in the android community had experienced similar happenings and suggested lean kernel... Flashed it earlier this evening and working like a charm.

[Q] Need some help, not sure where to find these answers.

I'll start off by giving some background information. I ordered my Nexus 4 back in March and ran stock up until about July/June. Prior to the Nexus I had the HTC G2. I don't know how to root and and use custom ROMs and I have looked at the root guide for the Nexus but it's a huge barrage of information and some terms that I don't know what they are. However, this question doesn't involve rooting. I gave my Nexus 4 to a friend, who also has the Nexus, to root for me and use a custom ROM. In this process however, he did something that he told me to never do (I really don't know why..) and he ended up soft bricking my phone. He did that because my phone was stuck on the "Google" start up screen for over 40 minutes. Basically, he wiped the entire phone, I think. Due to some issues, we are no longer on speaking terms and he was the only person I knew who knows how to deal with rooting and custom ROMs.
Now I don't have the original back up of the stock. My question is, if I ever needed to send my phone back to Google for repairs or anything else, would I be able to somehow get the phone back to it's stock state?
Also, where could I find some resources that aren't a barrage of information? When I go to those threads like the Nexus rooting guide, it's just so much information and I get lost (I don't even quite know what a ROM is, my current interpretation is an operating system). Currently, I think I know how to update the ROM, I'm currently using Paranoid Android.
I apologize if this issue of mine can easily be solved with a search. I have googled this issue numerous times and I could not really find a solid answer.

Fubs261 said:
I'll start off by giving some background information. I ordered my Nexus 4 back in March and ran stock up until about July/June. Prior to the Nexus I had the HTC G2. I don't know how to root and and use custom ROMs and I have looked at the root guide for the Nexus but it's a huge barrage of information and some terms that I don't know what they are. However, this question doesn't involve rooting. I gave my Nexus 4 to a friend, who also has the Nexus, to root for me and use a custom ROM. In this process however, he did something that he told me to never do (I really don't know why..) and he ended up soft bricking my phone. He did that because my phone was stuck on the "Google" start up screen for over 40 minutes. Basically, he wiped the entire phone, I think. Due to some issues, we are no longer on speaking terms and he was the only person I knew who knows how to deal with rooting and custom ROMs.
Now I don't have the original back up of the stock. My question is, if I ever needed to send my phone back to Google for repairs or anything else, would I be able to somehow get the phone back to it's stock state?
Also, where could I find some resources that aren't a barrage of information? When I go to those threads like the Nexus rooting guide, it's just so much information and I get lost (I don't even quite know what a ROM is, my current interpretation is an operating system). Currently, I think I know how to update the ROM, I'm currently using Paranoid Android.
I apologize if this issue of mine can easily be solved with a search. I have googled this issue numerous times and I could not really find a solid answer.
Click to expand...
Click to collapse
Is the phone booting into PA? If not try holding the power button and the volume down at the same time. It should boot into recovery. If it does all you need to do is flash a rom "install a os".
Sent from my Nexus 4 using xda app-developers app

Tunderpimp said:
Is the phone booting into PA? If not try holding the power button and the volume down at the same time. It should boot into recovery. If it does all you need to do is flash a rom "install a os".
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Ohh yes, I should clarify. Currently the phone is working and I have it up to date on Paranoid Android. The only issue I had when updating Paranoid Android was that I could not use the kernel my friend had supplied me with (I think it was the Franco kernel). When I would flash the kernel, it would get stuck on the Google logo screen. I would have to get out of that by re-flashing Paranoid Android again and I've been unsuccessful in flashing any kernels. The main reason I wanted to root my phone was a custom kernel, to help with battery life.
My main question is that I wanted to know if I could ever get it back to stock (as to not void a warranty) if I were to ever need to for any reason.

Fubs261 said:
Ohh yes, I should clarify. Currently the phone is working and I have it up to date on Paranoid Android. The only issue I had when updating Paranoid Android was that I could not use the kernel my friend had supplied me with (I think it was the Franco kernel). When I would flash the kernel, it would get stuck on the Google logo screen. I would have to get out of that by re-flashing Paranoid Android again and I've been unsuccessful in flashing any kernels. The main reason I wanted to root my phone was a custom kernel, to help with battery life.
My main question is that I wanted to know if I could ever get it back to stock (as to not void a warranty) if I were to ever need to for any reason.
Click to expand...
Click to collapse
which franco kernel, was it compatibke with your rom? i mean are you on android 4.3 and the kernel 4.2.2(or vice versa)? when you flashed the kernel, did you flash with the rom then boot up, or did you just flash the kernel alone? did you try redownloading the kernel, maybe a bad download? was it a jss kernel or a jwr kernel?

Fubs261 said:
My main question is that I wanted to know if I could ever get it back to stock (as to not void a warranty) if I were to ever need to for any reason.
Click to expand...
Click to collapse
Yes you can.
Read the guides as slowly as you need to...stopping to research anything you don't understand...
Or just use those no brainer toolkits that teach you nothing.
And stick to stock until you know what's going on within your device when you do these things.

simms22 said:
which franco kernel, was it compatibke with your rom? i mean are you on android 4.3 and the kernel 4.2.2(or vice versa)? when you flashed the kernel, did you flash with the rom then boot up, or did you just flash the kernel alone? did you try redownloading the kernel, maybe a bad download? was it a jss kernel or a jwr kernel?
Click to expand...
Click to collapse
I'm not sure what version it was, I guess that might have been the issue. Would that have caused it to stay on the Google logo screen? I'll make sure to double check for that next time I try to do something.
studacris said:
Yes you can.
Read the guides as slowly as you need to...stopping to research anything you don't understand...
Or just use those no brainer toolkits that teach you nothing.
And stick to stock until you know what's going on within your device when you do these things.
Click to expand...
Click to collapse
Thank you for answering. Could you link a good starter thread for me? I was hesitant to use a custom ROM or even to root my phone. What compelled me to do it was the kernels extending battery life. Because I was so lost and felt overwhelmed, I had my friend help me but now we are no longer on talking terms so I'm lost.
Again, I wish to apologize, I know I should just look this up myself, but with the possibility of bricking/soft-bricking my phone, I want to get as much help as possible. Whatever small nudge, I will take.

Your questions can be answered by reading the stickies thread in the general section. Just follow the instructions to flash back to factory stock:
http://forum.xda-developers.com/showthread.php?t=2010312
If you flash a kernel and the phone won't boot, that kernel or version of the kernel isn't compatible with that rom or particular version of Android.
sent from xda premium app
---------- Post added at 06:09 AM ---------- Previous post was at 06:06 AM ----------
Fubs261 said:
Because I was so lost and felt overwhelmed, I had my friend help me but now we are no longer on talking terms so I'm lost.
Click to expand...
Click to collapse
I hope it's not because he messed up your phone, it's not his fault that you trusted him to do it in the first place. If not, well nevermind.
sent from xda premium app

It's very simple to get it back to stock. You'd just need to find a copy of the stock Rom (which I can assure you is probably on this very website floating around somewhere) and flash it in recovery like you would any other Rom.
Sent from my 16GB Blue Verizon Galaxy S3 running MIUI v5 with KT kernel
---------- Post added at 03:14 AM ---------- Previous post was at 03:12 AM ----------
Also keep in mind, custom roms usually come with custom kernels. So you shouldn't even have to worry about kernel flashing. If you want to preserve battery you should focus more on under clocking and thermal throttling...
You can find guides on here somewhere for that too...
Sent from my 16GB Blue Verizon Galaxy S3 running MIUI v5 with KT kernel

How to replace custom kernel?

Hello, using Purity ROM + Semaphore kernel and I want to try another kernel. Maybe matr1x. What are steps? I need to flash stock kernel, than custom or I can flash custom kernel without stock?
Thank you

You don't have to flash stock first.

Just flash custom over custom...no need to flash stock

DrFredPhD said:
You don't have to flash stock first.
Click to expand...
Click to collapse
Mashed_Potatoes said:
Just flash custom over custom...no need to flash stock
Click to expand...
Click to collapse
Use caution. There are cases where flashing one kernel over another has proven to cause stability issues. Whilst for the majority of cases it's not necessary to flash stock kernel first, be prepared to do so. In other words, have a stock kernel downloaded as a back up in case you do have issues with the phone after the kernel exchange.

Mr_JMM said:
Use caution. There are cases where flashing one kernel over another has proven to cause stability issues. Whilst for the majority of cases it's not necessary to flash stock kernel first, be prepared to do so. In other words, have a stock kernel downloaded as a back up in case you do have issues with the phone after the kernel exchange.
Click to expand...
Click to collapse
I've been flashing custom over custom on my ex-Note II and everything was fine. And of course, always wipe cache

Mashed_Potatoes said:
I've been flashing custom over custom on my ex-Note II and everything was fine. And of course, always wipe cache
Click to expand...
Click to collapse
Good for you. Still doesn't mean the best advice we can give someone here is to "don't worry about it, just do it, it'll be fine". You don't know what ROM / Kernel people are coming from / going to and you certainly don't know how future ROMs / Kernels will behave. Again, there ARE examples on this forum where some kernels don't like being flashed over other non-stock kernels, problems have arisen and the only option was to flash a stock kernel first.
The best advice we can give someone on this forum is to be prepared for something to not go 100%. Like you I've never had a bad flash be-it ROM, radio or kernel but I still make sure I have a nandroid of the previous working state, stock ROM, radio and Kernel downloaded and know how to flash them before I do anything. That way, should it go wrong I'm covered.
I can not stress enough how wrong it is to just say "yeah, nothing will go wrong". It DOES go wrong and it goes wrong every day. For someone.

Mr_JMM said:
Good for you. Still doesn't mean the best advice we can give someone here is to "don't worry about it, just do it, it'll be fine". You don't know what ROM / Kernel people are coming from / going to and you certainly don't know how future ROMs / Kernels will behave. Again, there ARE examples on this forum where some kernels don't like being flashed over other non-stock kernels, problems have arisen and the only option was to flash a stock kernel first.
The best advice we can give someone on this forum is to be prepared for something to not go 100%. Like you I've never had a bad flash be-it ROM, radio or kernel but I still make sure I have a nandroid of the previous working state, stock ROM, radio and Kernel downloaded and know how to flash them before I do anything. That way, should it go wrong I'm covered.
I can not stress enough how wrong it is to just say "yeah, nothing will go wrong". It DOES go wrong and it goes wrong every day. For someone.
Click to expand...
Click to collapse
Umm, a recovery backup is something everyone should have. A backup of everything, including EFS for the clumsy ones that lose their IMEI's.
If you have a full backup of your system, it is okay to say "don't worry everything will be alright". If something goes wrong, you just do a system restore.
But that's just me, i can't be bothered with flashing stock kernels and roms all the time.

[Q&A] [AOSPA 4.4.4 KTU84P] ParanoidAndroid 4.4+ G2 [06/28]

Q&A for [AOSPA 4.4.4 KTU84P] ParanoidAndroid 4.4+ G2 [06/28]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:

One simple question.
The builds from aospa are 4.4 sources or 4.2?
Thanks in advance.

NEO2598 said:
One simple question.
The builds from aospa are 4.4 sources or 4.2?
Thanks in advance.
Click to expand...
Click to collapse
@houstonn was originally developing but stopped in June due to computer failures which is being resolved soon. His last build of 6/29 was on 4.4 sources and required the modem of stock 4.4.
The current builds supplied by @ayysir and now @jakew02 are on 4.2 sources which would require that specific modem.
Which ones exactly not sure as I am not familiar with every carrier version only sprint.
Sent from my LG-LS980 using Tapatalk

MeestaAytch said:
@houstonn was originally developing but stopped in June due to computer failures which is being resolved soon. His last build of 6/29 was on 4.4 sources and required the modem of stock 4.4.
The current builds supplied by @ayysir and now @jakew02 are on 4.2 sources which would require that specific modem.
Which ones exactly not sure as I am not familiar with every carrier version only sprint.
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
It has been stated in the ROM thread multiple times that you must use a 4.2 STOCK JB MODEM for best compatibility. Any other modems you guys use is solely at YOUR OWN DISCRETION. @MeestaAytch they should know what to use at this point but thanks for clarifying again for those who don't want to search before posting :highfive:

@jakew02 no problem. I know it's tiring repeating the same information but from what I've seen in my time using XDA.... It'll never change.
I'm glad you devs still continue doing what you're doing for us though knowing this nonsense goes on.
Sent from my LG-LS980 using Tapatalk

A few bugs
Hi,
The thread is too big for me to go thru it post by post so I'll just make a few questions and hopefully I'll get some answers. I flashed this ROM and it was working flawlessly. I only found very few bugs like not being able to set up multiple recurrent alarms because the app would freeze and there was another bug but I can't remember. The problem I find frustrating is with the text messages or SMSs. At first I was not receiving SMSs. Then I was receiving them but I couldn't send any. I returned back to stock VS98024a and I'm still having the same problem but at least I'm getting a pop-up when "General problems: cause code 96". I have googled this several times in several ways and can't seem to find a solution, not even on the Verizon site or help app on the phone. I need help with this please.

How to keep the back home task manager buttor on the screen?

battery life? i want to install on lg d800 and its beta only..

dori kernel
Hi,
From where you get Dorimanx kernel for AOSP ROMs ?

My phone says it can't connect to the camera, and the torch. Does anyone know how to solve this?
Sent from my LG-LS980 using XDA Free mobile app

LG G2 D802 SIM not recognized
ok, so im quite familiar with flashing roms etc, ive had cyanogenmod and cloudy g3 installed on my d802 without any problems however when i flashed paranoid android 4.4 (i used the appropriate one for my model) i am left with no service, it seems that my sim is not recognised . ive tried reflashing several times and even reflashed my old rom which worked (calls, texts data) please could someone help me as i love the look and feel but cant use my phone without radio.
im using twrp recpvery aswell
Alex

a13xch1 said:
ok, so im quite familiar with flashing roms etc, ive had cyanogenmod and cloudy g3 installed on my d802 without any problems however when i flashed paranoid android 4.4 (i used the appropriate one for my model) i am left with no service, it seems that my sim is not recognised . ive tried reflashing several times and even reflashed my old rom which worked (calls, texts data) please could someone help me as i love the look and feel but cant use my phone without radio.
im using twrp recpvery aswell
Alex
Click to expand...
Click to collapse
Please state exact filename and order of wipe/flash.

Just tried the test build for D802. Booted at LG logo for a while then screen turned black with 2 red lines and one green vertical line. I was so sure I was gonna get the permanent black lines but then again I read that the damaged screens are caused by already faulty hardware under high heat.
Anyways, I panicked and then I restarted the phone by pressing power + down. Then I got the weird boot sequence like everyone above describes and it boots into the OS. Thank God I got no black lines! However it wasn't stable for me as the phone rebooted itself twice within the span of 20 minutes. I'm going back to 13/10 build for now.

Any d802 users flashing latest twitter released rom can you please report here if jdi or lgd and whether or not weird logo appeared?
I'm on jdi and had weird logo appeared after clean flash. I did not let the rom boot and reflashed previous version without further problems

FYI, houston's latest works great so far on the VS980. Clean flash, using RenderKernel R24.

So i have the vs980 and i currently have xdabbebs rom on my phone, but i want to try PA. Can someone explain how to flash a rom over another rom, or is there something else i should do. i tried it once by flashing with twrp and it just hung on the lg sreen. luckily i had a back up

jclemens23 said:
So i have the vs980 and i currently have xdabbebs rom on my phone, but i want to try PA. Can someone explain how to flash a rom over another rom, or is there something else i should do. i tried it once by flashing with twrp and it just hung on the lg sreen. luckily i had a back up
Click to expand...
Click to collapse
Migrating from one ROM to another is for me like this:
1. Nandroid backup
2. Wipe all except sdcard (yes, wipe system)
3. Flash new ROM
Be sure to always have a Nandroid backup!
And always check what baseband (aka radios or modem) your new ROM is requiring.
-___-
If you are UPDATING your current ROM, I.e. flashing a new build of let's say paranoid android, you can flash the updated file right on top of your old system. That is called DIRTY FLASHING and it's actually risky, so please, always do Nandroid backups!
-____-
Peace

Thank you for the reply. I tried doing it the way you suggested again and i get the same results. I wipe everything that is necessary and when i try to install the zip it immediately says failed

jclemens23 said:
Thank you for the reply. I tried doing it the way you suggested again and i get the same results. I wipe everything that is necessary and when i try to install the zip it immediately says failed
Click to expand...
Click to collapse
Ok
I would;
Update my custom recovery to the latest
Download recommended baseband, to be on the safe side
Redownload the ROM
Check the md5-checksum
Retry to install it
Flash the recommended baseband, better safe than sorry
Never give up
Peace

Hi guys i just flashed the newest build and out of all the roms i have flashed i have never seen this problem. After i flashed i have no sim service at all. Done a clean install still no good.