[Q] CM 10.1 Kexec Builds Help - Motorola Droid 4

I've tried to install the Kexec builds of the CM 10.1 nightlies three times now, each time resulting in a blank screen after I hit reboot once I'm done installing it.
Has anybody else had this problem? I've done all the obvious stuff such as wiping properly and what not, yet two different downloads of the same version have yielded the same results. Is the way of installing a kexec build somehow different than the normal builds?
If you've had this problem as well or could shed some light on how to resolve this, I could use the advice.

How long did u wait. It takes a couple minutes at boot
Sent from my XT894 using xda app-developers app

rruleford said:
How long did u wait. It takes a couple minutes at boot
Sent from my XT894 using xda app-developers app
Click to expand...
Click to collapse
Literally about ten minutes each time, without ever even making it to the boot animation.
Edit: Solved. I did two things differently, so actually sure which to attribute the success to. I flashed tonight's nightly, as opposed to the previous nightly, being the first difference. The second one however, was that I placed the ROM on my internal storage when transfering it over from my PC. As opposed to every other ROM, which I slap in a folder on my SD card.

Related

[Q] ANOTHER Boot Loop Problem

Been A long time Lurker here at XDA, so much great info and support!!
Ok so here is my problem I have a 32GB touchpad. I have WebOS running, no problems at all. I have tried many many times installing CM7 and CM7 XRON-ified. Every version and i get into this boot loop....
I have done an ACME Uninstall....reinstalled webos with the Doctor.... fresh installs of everything... full formats of "SD Card"... I am at a loss
After i have done a fresh install i will reboot into CM and it will be working... then just reboot, and start the boot loop...ill stop it on the MBOOT menu and just let it sit then boot back into CM and it will load... then randomly just reboot and go back to the boot loop...
I am at a loss... could it be hardware related... WebOS runs find and diagnostics that i have run in webos come back clean... Any one have any thoughts?.....
If you need any other info please let me know...
Thanks
Cdrshm
Sounds to me like the caches need wiping and another fresh install. But I'm sure you've tried this so I am at a loss.
"A little nonsense, now and then, is relished by the wisest men."
strikerage said:
Sounds to me like the caches need wiping and another fresh install. But I'm sure you've tried this so I am at a loss.
"A little nonsense, now and then, is relished by the wisest men."
Click to expand...
Click to collapse
I have done it more then a dozen times.. hardware issue maybe?
Sent from my Galaxy Nexus using Tapatalk
Bump. Anyone have any thoughts?
Sent from my Galaxy Nexus using Tapatalk
according to the thread, it does that a few times (exact numbers havent been given) because of initial settings.
the 4 TPs ive done all had at least 2 or 3 random reboots that settled out and disappeared .
endlesszeal said:
according to the thread, it does that a few times (exact numbers havent been given) because of initial settings.
the 4 TPs ive done all had at least 2 or 3 random reboots that settled out and disappeared .
Click to expand...
Click to collapse
Yea, but this is actually a boot loop, not just a reboot....many times won't even boot back into cm...
Sent from my Galaxy Nexus using Tapatalk

[NIGHTLY] UNOFFICIAL CM9/ICS For Droid 4 For MotoICS Leak

FLASHING ROMS WILL VOID YOUR WARRANTY AND COULD POTENTIALLY DAMAGE YOUR PHONE -- WHILE I MAKE EVERY ATTEMPT NOT TO LET THIS HAPPEN, IT'S STILL A RISK THAT YOU'RE TAKING. IF SOMETHING BAD SHOULD HAPPEN TO YOUR PHONE, PLEASE DON'T BLAME ME -- HENCE THIS WARNING.
This isn't so much a ROM announcement as it is a direction to find the unofficial nightly builds of CM9 for the Droid 4 (based on Motorola ICS leaks)
Download Here from ROMbot
Download GApps Here (04/29 Goo-Inside GApps Link).
FLASH THE GAPPS.ZIP FILE AFTER YOU FLASH THE ICS.ZIP
WHAT do I need to run this ROM?
- Rooted
- Running a Motorola ICS leak (.206, .208, .211, etc)
- I recommend that you run Safestrap v2.00 to install this. Here's how to use Safestrap
And you can download Safestrap for the Droid 4 (v2.x for ICS-leak users) here:
Safestrap « Hash-of-Codes
WHAT can I expect to work right now?
- 4G and basic phone function
- All sensors
- Camera, Panorama and Face-unlock
- Video Recording
- HD YouTube
- Netflix
Current Known Issues?
- Data connection is a work in progress. It's MUCH better than it used to be in the old ICS builds, however there is always room for improvement. Due to the "global" data connection style of stock Motorola ICS, this problem will probably continue to be worked on. Feedback is always appreciated, but if you see it posted already then there's a good chance I know about specific issues.
- Currently, there is a bug in the rotation display of the phone. What I mean is, that when you take the phone and rotate it, the display will squeeze in on itself and then pop back out. This is a *known* issue and I'm working very hard to fix it.
- The CM9 built-in Wifi Tether won't work. You need to use the "Wifi Tether" app that's bundled into the ROM. Once you open it, hit [menu] and "Settings". Select "Change Device-Profile" to "Generic ICS".
- I'm sure there's more, I'll update this list here in a bit.
WHO works on this?
Myself and @DHacker29 work as a team to build AOSP-based ROMs (and device setups) for several Motorola phones. Typically, I do the coding work in C, C++ or Java while DHacker maintains the blobs, runs merges with CM/AOKP sources, and solves device issues which require less coding.
WHAT is a "nightly"?
It's an automated build ran from a script. It basically: deletes the current set of output files, sync's with github, and then attempts to do a brand new build. It can break at times, in which case we'll fix it (usually this happens when there are framework changes which didn't get merged).
WHY would I want this?
- Since we work on several devices, this is how we decided to start keeping builds up-to-date. Rather than spend several hours a week on builds and uploading. This happens automatically every night around 2am PST.
- It's up to you the community to identify good "stable" builds.
Feel free to follow me on Twitter as I do sometimes make announcements there before I do forum postings:
Hashcode (@Hashcode0f) on Twitter
We maintain all of our code at github:
https://github.com/o...ns/STS-Dev-Team
Screenshots:
[ COMING SOON ]
Reserved for future use
Looking great Hash! Thanks for your work.
my excitement is robust
Just tried installing using safestrap and bootlooped. Had to hard reboot to get back to safestrap recovery and back in to stock ROM. Anyone else tried this yet? Might try again tonight when I get home and let the battery charge up a bit.
Sent from my DROID4 using XDA
kwyrt said:
Just tried installing using safestrap and bootlooped. Had to hard reboot to get back to safestrap recovery and back in to stock ROM. Anyone else tried this yet? Might try again tonight when I get home and let the battery charge up a bit.
Sent from my DROID4 using XDA
Click to expand...
Click to collapse
I was able to get it installed and working just fine under safestrap. Did you wipe data, cache, and dalvick?
jgardner said:
I was able to get it installed and working just fine under safestrap. Did you wipe data, cache, and dalvick?
Click to expand...
Click to collapse
That was it. First time I've used safestrap. I figured since I did not have a previous ROM installed in Safemode that I did not need to wipe. Went back in, wiped data and cache and now I am in business. Looking good Hash!
One question though, I tried to wipe dalvik and it said it could not find sd-ext. Any idea what that is about?
Edit: Feels so good to be flashing ROMs again!!!
kwyrt said:
That was it. First time I've used safestrap. I figured since I did not have a previous ROM installed in Safemode that I did not need to wipe. Went back in, wiped data and cache and now I am in business. Looking good Hash!
One question though, I tried to wipe dalvik and it said it could not find sd-ext. Any idea what that is about?
Edit: Feels so good to be flashing ROMs again!!!
Click to expand...
Click to collapse
I did the exact same thing (not wiping on a fresh safestrap). I believe that message about the sd-ext is normal when wiping dalvik.
kwyrt said:
That was it. First time I've used safestrap. I figured since I did not have a previous ROM installed in Safemode that I did not need to wipe. Went back in, wiped data and cache and now I am in business. Looking good Hash!
One question though, I tried to wipe dalvik and it said it could not find sd-ext. Any idea what that is about?
Edit: Feels so good to be flashing ROMs again!!!
Click to expand...
Click to collapse
I believe the reason behind that message is that the Dalvik cache is not stored on the sd-ext, but rather the sd, which is internal. Since theres technically 2 SD cards on our device, it looks for the dalvik on the first one. A dev would probably have better advice on it though,....I may be wrong.
kwyrt said:
That was it. First time I've used safestrap. I figured since I did not have a previous ROM installed in Safemode that I did not need to wipe. Went back in, wiped data and cache and now I am in business. Looking good Hash!
One question though, I tried to wipe dalvik and it said it could not find sd-ext. Any idea what that is about?
Edit: Feels so good to be flashing ROMs again!!!
Click to expand...
Click to collapse
Safestrap checks for a dalvik cache under a theoretical /sd-ext partition on the external SD. It's almost never there tho. So you can safely ignore that message.
So one thing I have noticed switching between stock and the ICS ROM is the battery level is not consistent. Reads 60% on stock. Reads 26% on ICS. Anybody know what's up with that?
Sent from my DROID4 using XDA
kwyrt said:
So one thing I have noticed switching between stock and the ICS ROM is the battery level is not consistent. Reads 60% on stock. Reads 26% on ICS. Anybody know what's up with that?
Sent from my DROID4 using XDA
Click to expand...
Click to collapse
I havent flashed this one just yet but i know on my droid 3 i let the battery charge all the way up and then wiped battery stats and all was fine after that.
Sent from my DROID4 using XDA
thanks hashcode! you're the man!
Appreciate the Rom.. Runs very nicely on Droid 4. Easy install.
I know HW video is being worked on. Will that fix or update allow Movie Studio to work?
Very interested and excited about Ice Cream Sandwich and future updates to this Rom
Installed and loving it so far.
The one thing I've noticed, the phone gets really hot, and the battery usage is pretty poor. I actually watched my battery percentage drop while doing my installs of all the apps that I had to download.
I lost about 3% during that process, even when plugged into the wall charger.
I'll keep an eye on it, as I'm close to a charger at all times, so bad battery life doesn't affect me too much.
Can't wait for BT to work, as that would be the last piece in a daily driver for me.
EDIT - just discovered I'm having issues with Chrome Beta. I've never used it before, but it won't load any websites. I'll DL Dolphin for the time being, but would love to try out Chrome. Just wondering if anyone else is running into this.
Im fully installed and Chrome Browser works great along with all other functions on my end.
As for battery percentage Im not sure if im having your problem with excess heat....
doubleokneegro said:
Im fully installed and Chrome Browser works great along with all other functions on my end.
As for battery percentage Im not sure if im having your problem with excess heat....
Click to expand...
Click to collapse
Ok found out it was my charger. For some reason it wasn't actually charging and was just causing heat. Plugged it into a different charger and all is well now.
still no love with Chrome though.
kwyrt said:
Just tried installing using safestrap and bootlooped. Had to hard reboot to get back to safestrap recovery and back in to stock ROM. Anyone else tried this yet? Might try again tonight when I get home and let the battery charge up a bit.
Sent from my DROID4 using XDA
Click to expand...
Click to collapse
Im in this same predicament.. Uh.. How do i hard reset? Hold power? That doesnt seem to be working for me....
---------- Post added at 10:16 PM ---------- Previous post was at 10:07 PM ----------
gangrif said:
Im in this same predicament.. Uh.. How do i hard reset? Hold power? That doesnt seem to be working for me....
Click to expand...
Click to collapse
Nevermind, google has solved my despair.
http://www.technipages.com/how-to-reset-frozen-droid-4.html
Thanks.
Absolutely love this ROM!!!!! One request though, what do I need to install to get webtop working? Just got the lapdock 500 a couple hours ago and love this ROM to much to give it up
Sent from my DROID4 on ICS
Everything seems to be working perfectly for me, even the camera is working properly. I haven't tried bluetooth yet, but I'm not too worried about it, I barely use it. Wifi connects and works, no problem there. I noticed a slight lag after installing setCPU but now it seems fine. I'll check tomorrow to see how the battery life is but for now every things pretty smooth. Thanks!

[Q] Do I have an un-android-able Touchpad?

Hello All,
I'm not that new to the XDA scene as I've been rooting for a couple of years now (HTC Aria, HTC One XL), however I am completely stumped as to why my HP Touchpad keeps randomly rebooting while in android. Here's the TL;DR
1. Installed moboot 0.3.5, CWM 1012, and CM9 20121212 Nightly using ACMEInstaller2.
2. Everything installed fine, except device randomly reboots within 5 min of starting up, sometimes immediately (before I can even unlock the display), sometimes even while loading the cyanogenmod splash screen.
3. I have read everything on the XDA's about this problem and scoured Google for hours to no avail. Tried clearing cache, Dalvik cache, then fix permissions. Still randomly reboots. Tried turning off beats audio in webOS. Still randomly reboots. Used ACMEUninstaller, erased webOS completely, re-rooted using ACMEInstaller3, moboot 0.3.5, CWM 1012, and CM9 20121212 Nightly. Still Randomly Reboots.
I am at the end of my ropes here, about to give up and just accept that my device is not compatible with android, even though countless others are running android with little problem. I'm just not understanding what I am doing wrong, if anything. Any comments / advice would be very much appreciated.
Peace and Love
That's odd. Maybe try a different ROM?
bananagranola said:
That's odd. Maybe try a different ROM?
Click to expand...
Click to collapse
I've tried CM7 Alpha 3.5, CM9 Nightlys, and CM9 Fat and Creamy by SGA. CM7 was the most stable, but still I had many FC's and random reboots, though not as many as CM9.
leetpcguy said:
I've tried CM7 Alpha 3.5, CM9 Nightlys, and CM9 Fat and Creamy by SGA. CM7 was the most stable, but still I had many FC's and random reboots, though not as many as CM9.
Click to expand...
Click to collapse
I would try wiping cache and dalvik-cache. Aside from that, I'm out of ideas.
bananagranola said:
I would try wiping cache and dalvik-cache. Aside from that, I'm out of ideas.
Click to expand...
Click to collapse
Just tried that and it rebooted before I could even navigate to No-Frills CPU Control :/ I appreciate the input though.
It seems that once it boots, if i don't touch anything, it will not reboot while at the lock screen. I've had it charging for the past 4 hours or so while booted in CM9 and haven't ventured past the lock screen and it hasn't rebooted yet.
When you unlock it, see if you can find out what the min cpu speed. If it's @ 192, try 384 or even 432 and see if that makes a difference
Sent from my ThunderBolt using xda premium
rrrrrrredbelly said:
When you unlock it, see if you can find out what the min cpu speed. If it's @ 192, try 384 or even 432 and see if that makes a difference
Sent from my ThunderBolt using xda premium
Click to expand...
Click to collapse
I have tried both of those as well as setting both the min and max frequency to 1.2 GHz. It still reboots; seems to be independent of CPU clock speed.
I've also tried disabling all haptic feedback as well as turning the sound all the way down and turning off the keypress sounds. Still reboots.
i had the same issue. i used acmeuninstaller and removed android completely. downloaded the latest CM9 nightly and CWM and such. used acmeinstaller to install CWM, then I installed CM9 and gapps manually via CWM. check out jscullins latest CWM build. it may help.
Are you using the right Gapps zip? If you flash CM9 and are using Jelly Bean Gapps, it may have problems trying to run the Google setup at start since its meant for Jelly Bean. Just a thought.
It may be a block of bad Nand memory. Similar problems have been seen / noted in some of the other tablet forums (I hang out a lot in the Advent Vega forum) and this is not totally unknown, although not that common. It may just be an area that hasn't been used or is avoided by Webos, but comes into play with Android and the extra partitions.
Only suggestion from me would be to try AcmeInstaller3 if you haven't already as that sets different partitions to AcmeInstaller2 to allow for the space needed for CM10, but will work fine with CM9.
slicetwo said:
i had the same issue. i used acmeuninstaller and removed android completely. downloaded the latest CM9 nightly and CWM and such. used acmeinstaller to install CWM, then I installed CM9 and gapps manually via CWM. check out jscullins latest CWM build. it may help.
Click to expand...
Click to collapse
The only thing I did different than what you suggested here is let the ACMEInstaller3 install CM9 for me. I have not tried jscullins build of CWM though, I will give that a shot and also try installing the ROM manually after ACME has installed CWM.
jsgraphicart said:
Are you using the right Gapps zip? If you flash CM9 and are using Jelly Bean Gapps, it may have problems trying to run the Google setup at start since its meant for Jelly Bean. Just a thought.
Click to expand...
Click to collapse
I'm 99% sure I was using the right apps, and usually I can make it through the setup portion of the initial boot without a restart. Doesn't last too much longer than that though...
dmarchant said:
It may be a block of bad Nand memory. Similar problems have been seen / noted in some of the other tablet forums (I hang out a lot in the Advent Vega forum) and this is not totally unknown, although not that common. It may just be an area that hasn't been used or is avoided by Webos, but comes into play with Android and the extra partitions.
Only suggestion from me would be to try AcmeInstaller3 if you haven't already as that sets different partitions to AcmeInstaller2 to allow for the space needed for CM10, but will work fine with CM9.
Click to expand...
Click to collapse
I've used ACMEInstaller3 the last two times I reverted everything to stock, erased and reset webOS, and started over. Still had the same problems as when I used ACMEInstaller2.
youre doing something wrong,, probly something simple..
have you looked @ youtube?
roland has some good vids.
so does reverendkjr

Epinter's CM10 on ICS + JB (Lateral Flash from RAZRHD ROM)

I was simply curious and discovered that this RAZR HD ROM works (almost perfectly!) on my AHD running ICS. I assume this should fully work for JB, because it's made for that kernel. So if you're on JB, please try it and let us know.
>> Use Safestrap SLOT-1 to flash Epinter's rom: http://www.linuxmobile.org/razrhd/cm10
If your WIFI won't turn on, replace the drivers with the correct files from here: http://forum.xda-developers.com/showthread.php?t=2107662
Developers/Coders: How do we get the sensors working on ICS?? I've tried like mad to replace with stock-ics drivers, but I really don't know what I'm doing
Enjoy the pull-down toggles & customizable soft-keys!!
[edit: attached my screenshots; everything seems to work on ICS except the sensors & gps]
no go on JB 4.1.1, stuck in boot animation for 10mins twice.
progrockguy said:
I was simply curious and discovered that this RAZR HD ROM works (almost perfectly!) on my AHD running ICS. I assume this should fully work for JB, because it's made for that kernel. So if you're on JB, please try it and let us know.
Click to expand...
Click to collapse
What do you mean by almost perfectly... what was and was not working? Im still running on ICS and would love to get cm10 on my device.
JB 4.1.1 it boots for me but I get Encryption Unsuccessful. No go.
Sent from my MB886 using xda app-developers app
I can get the JB rom to boot, but i get a message about phone not successfully encrypted and requires a reset, wiping data now to see if it will work.
(installing to rom slot using safestrap)
coldfear00 said:
no go on JB 4.1.1, stuck in boot animation for 10mins twice.
Click to expand...
Click to collapse
Can you try deleting slot1 from Boot Options and creating a new one from scratch, wipe, then re-flash (and cross your fingers).
EcHoFiiVe said:
JB 4.1.1 it boots for me but I get Encryption Unsuccessful. No go.
Click to expand...
Click to collapse
Oneofonex1 said:
I can get the JB rom to boot, but i get a message about phone not successfully encrypted and requires a reset, wiping data now to see if it will work.
Click to expand...
Click to collapse
Is this the error message you guys are talking about? Also are you flashing to a freshly wiped (cache, dalvik, sys, factory data) slot or over an existing rom (i.e. dirty and not recommended)?
forum.xda-developers.com/showthread.php?t=1580902
If that's the bug then there is a fix for it, but I didn't encounter that at all on ics.
Clean flash. I have already seen that guide but we don't have partitioning in SS.
Sent from my MB886 using xda app-developers app
Damn this encryption bug. I did not see that coming due to simply being on JB.
I saw another thread say that removing the microsd and rebooting a couple of times might get you past the error message. This isn't ideal and reinserting would probably bring it back, but if it works we could then determine if all the sensors work on JB.
Nothing works on my side either I tried reboots w/o SD and tried booting off another ROM and then installing no-go
Sent from my MB886 using xda app-developers app
progrockguy said:
Is this the error message you guys are talking about? Also are you flashing to a freshly wiped (cache, dalvik, sys, factory data) slot or over an existing rom (i.e. dirty and not recommended)?
forum.xda-developers.com/showthread.php?t=1580902
If that's the bug then there is a fix for it, but I didn't encounter that at all on ics.
Click to expand...
Click to collapse
yes, exact error message but, will the fix from work on our phones (i'm a bit skeptical and cant be the 1st to jump and find out).
Oneofonex1 said:
yes, exact error message but, will the fix from work on our phones (i'm a bit skeptical and cant be the 1st to jump and find out).
Click to expand...
Click to collapse
Yeah that solution seems impractical. I think a simpler solution would be to work around the internal "sdcard." I'd remove anything that involves mounting/reading that area (/data/media) and see if it boots up then. I took a look at Batakang's init files and I noticed that his omit the /storage lines that this CM10 includes.
But my first priorities are these two cpa exams on the 14th and 28th. I've been wasting too much time on this new phone :/
progrockguy said:
Yeah that solution seems impractical. I think a simpler solution would be to work around the internal "sdcard." I'd remove anything that involves mounting/reading that area (/data/media) and see if it boots up then. I took a look at Batakang's init files and I noticed that his omit the /storage lines that this CM10 includes.
But my first priorities are these two cpa exams on the 14th and 28th. I've been wasting too much time on this new phone :/
Click to expand...
Click to collapse
tried removing everything (except twrp folder and safestrap) from external sd, still get encryption error. I appreciate your time, i hope your exams go well. good luck
Just a question how is everything going so far guys? Keep up the good work
ATRIX HD running BATAKANG 1.10
This ROM won't boot because were using SS and not CWM or TWRP
Sent from my MB886 using xda app-developers app
What if we use whirley eyes bootmanager like the atrix 2
Sent from my MB886 using xda app-developers app
EcHoFiiVe said:
This ROM won't boot because were using SS and not CWM or TWRP
Click to expand...
Click to collapse
This boots up just fine. The ROM creator himself says it can be flashed with Safestrap: http://forum.xda-developers.com/showthread.php?t=1993888
The issue is getting past the "Encryption Unsuccessful" message for those on JB. From what I've read it's because the internal sdcard cannot fully read. (Maybe a factory reset & SD wipe via stock would help by erasing any encrypted data?)
progrockguy said:
This boots up just fine. The ROM creator himself says it can be flashed with Safestrap: http://forum.xda-developers.com/showthread.php?t=1993888
The issue is getting past the "Encryption Unsuccessful" message for those on JB. From what I've read it's because the internal sdcard cannot fully read. (Maybe a factory reset & SD wipe via stock would help by erasing any encrypted data?)
Click to expand...
Click to collapse
No. Its because we use a bootstrap recovery. I don't think its SS compatible because the Encryption Unsuccessful error only happens because of the incompatibility.
Sent from my MB886 using xda app-developers app

Phone shuts down after reboot

I have been experiencing this for a while: after rebooting my phone, the exact momment it finishes booting up, it starts shutting down, no matter what custom ROM I have flashed, so it makes me believe it's not ROM related, but related to the bootloader or something like that. after banging my head against the wall for so long I couldn't find any solution, so I'd like to know what's your opinion about it.
Edit: forgot to mention I've tried all the routine methods, cleaning dalvik/cache, wiping system, data and even internal storage without any success, that's why I believe it is bootloader related, but I'm no expert so... If this issue has been addressed here please show me where as I've become empty handed
Sent from my LG-P880 using XDA Premium HD app
tristaoeast said:
I have been experiencing this for a while: after rebooting my phone, the exact momment it finishes booting up, it starts shutting down, no matter what custom ROM I have flashed, so it makes me believe it's not ROM related, but related to the bootloader or something like that. after banging my head against the wall for so long I couldn't find any solution, so I'd like to know what's your opinion about it.
Edit: forgot to mention I've tried all the routine methods, cleaning dalvik/cache, wiping system, data and even internal storage without any success, that's why I believe it is bootloader related, but I'm no expert so... If this issue has been addressed here please show me where as I've become empty handed
Sent from my LG-P880 using XDA Premium HD app
Click to expand...
Click to collapse
i have seen this happening only when the custom kernel is not compatible with the rom installed. the bootloader has nothing to do. we just unlock it to install a different recovery image that help us install any kernel and any rom
I'm using the CM10.1.3 right now with its stock kernel and it still happens... It annoys me so freaking much
Sent from my LG-P880 using XDA Premium HD app
tristaoeast said:
I'm using the CM10.1.3 right now with its stock kernel and it still happens... It annoys me so freaking much
Sent from my LG-P880 using XDA Premium HD app
Click to expand...
Click to collapse
Maybe you should reflash the .kdz file to be completely stock. If this problem still occurs, it's definitely nor ROM related.
Dexxon said:
Maybe you should reflash the .kdz file to be completely stock. If this problem still occurs, it's definitely nor ROM related.
Click to expand...
Click to collapse
....... the .kdz is used to flash stock LG's rom. when he sais stock kernel with cm 10.1.3 , he means , the cyanogenmod 10.1.3 as it is.
kessaras said:
....... the .kdz is used to flash stock LG's rom. when he sais stock kernel with cm 10.1.3 , he means , the cyanogenmod 10.1.3 as it is.
Click to expand...
Click to collapse
exactly.. It is annoying me for real not being able to find what's causing this... Not being able to properly reboot is a real pain in the a**

Categories

Resources