How do i fix this? I'm using stock 20c as my primary and have installed all the necessary files as well as a hexec comp. kernel (optimus prime 2.7) . I tried booting up slimbean 4.3 with iodak v8 but the phone shuts down instead of booting. Also tried slimbean 4.22 with no luck using the patched cm kernel in the multirom thread, iodak, and optimus prime 2.7 cm version but the phone still shuts down after hitting the boot option. Have also tried deleting and reinstalling but no luck. YES, I'VE SEARCHED FOR MY PROBLEM AND LOOKED AT EVERY SINGLE POST IN THAT THREAD AT LEAST TWICE and none of the posts help with my issue, I've seen my problem mentioned a couple of times but the authors somehow fix it without posting why or have a completely different issue. Is there anyway to fix my problem?
juanacevedo said:
How do i fix this? I'm using stock 20c as my primary and have installed all the necessary files as well as a hexec comp. kernel (optimus prime 2.7) . I tried booting up slimbean 4.3 with iodak v8 but the phone shuts down instead of booting. Also tried slimbean 4.22 with no luck using the patched cm kernel in the multirom thread, iodak, and optimus prime 2.7 cm version but the phone still shuts down after hitting the boot option. Have also tried deleting and reinstalling but no luck. YES, I'VE SEARCHED FOR MY PROBLEM AND LOOKED AT EVERY SINGLE POST IN THAT THREAD AT LEAST TWICE and none of the posts help with my issue, I've seen my problem mentioned a couple of times but the authors somehow fix it without posting why or have a completely different issue. Is there anyway to fix my problem?
Click to expand...
Click to collapse
Honestly man I do not think that you really search because I answered this question twice ...
Anyway to boot your second 4.3 ROM, you need either to put your phone on charge and then select Slim OR just after having selected Slim, wait one second and then hold the power button as if you wanted to turn on your phone. These two methods will boot your second ROM.
The last method is easier but longer in time : you need to backup your two ROMs and then invert their position ... I don't think I'm really clear ... In your case you need to have Slim as first ROM and Stock as second.
All your ROMs will then boot normally without any trick
Sent from my LG-P880 using xda premium
juanacevedo said:
How do i fix this? I'm using stock 20c as my primary and have installed all the necessary files as well as a hexec comp. kernel (optimus prime 2.7) . I tried booting up slimbean 4.3 with iodak v8 but the phone shuts down instead of booting. Also tried slimbean 4.22 with no luck using the patched cm kernel in the multirom thread, iodak, and optimus prime 2.7 cm version but the phone still shuts down after hitting the boot option. Have also tried deleting and reinstalling but no luck. YES, I'VE SEARCHED FOR MY PROBLEM AND LOOKED AT EVERY SINGLE POST IN THAT THREAD AT LEAST TWICE and none of the posts help with my issue, I've seen my problem mentioned a couple of times but the authors somehow fix it without posting why or have a completely different issue. Is there anyway to fix my problem?
Click to expand...
Click to collapse
I Got same Problem, but With offial stock 4.1.2 AS secundary. When i Boot it it "shuts down", but i can't Start anything after it. I need To remove akku To get it up again...press power button after multrom Boot works for me...is that normal ? :/
Sent from my LG-P880 using xda app-developers app
The "ectoplasma22" solution worked, I thanked him with the button, but I do it publicly, thank you!
This is my first message, I have yet another 9 to be able to write in the multirom development section, to report this bug, the solution is not elegant, and this problem must be seriously considered.
PS. Of course, respecting the times of the developers and their dedications. Thanks everyone!
Related
Hello, I'm not particularly new to Android, nor am I new to the prospect of flashing roms. However, I recently flashed an upgrade of cm10.1 to my Nook HD via recovery and I'm now stuck at "Loading (SD)..." in the bootloader. Is there a specific way that CM10.1 has to be upgraded or did something just go wrong during the flash? With my other devices, you can just flash the upgrade zip from the recovery menu. Thanks in advance for the help!
and finglha
bradleyrogers89 said:
Hello, I'm not particularly new to Android, nor am I new to the prospect of flashing roms. However, I recently flashed an upgrade of cm10.1 to my Nook HD via recovery and I'm now stuck at "Loading (SD)..." in the bootloader. Is there a specific way that CM10.1 has to be upgraded or did something just go wrong during the flash? With my other devices, you can just flash the upgrade zip from the recovery menu. Thanks in advance for the help!
Click to expand...
Click to collapse
Up until the most recent .zip, I have done just what you described. Couple times my HD god hung up during that same process... I just powered down and restarted and it booted fine.
lossofsilence said:
Up until the most recent .zip, I have done just what you described. Couple times my HD god hung up during that same process... I just powered down and restarted and it booted fine.
Click to expand...
Click to collapse
Yea it has happened to me too, I just powered off with a long press on the 'N' and power button. Restarted and it worked fine.
Actually i'm on 10.1 too.
This thing happens sometime. This is normal for early alfa soft.
On first clean install test i had 3 or more times stop on Cyanogen logo. But it started work on fourth time. Same happened with second clean install too (messed Adnroid to death with my hard tests and modifications ). Power OFF/On have sometime magical power.
Well, I was able to restart the nook and flashed the zip again. It worked! However, I can't change the brightness. To be honest, I can't remember if I even tried before. So, is this just a bug or is it common? Thanks for the help guys
bradleyrogers89 said:
Well, I was able to restart the nook and flashed the zip again. It worked! However, I can't change the brightness. To be honest, I can't remember if I even tried before. So, is this just a bug or is it common? Thanks for the help guys
Click to expand...
Click to collapse
I have no problem adjusting brightness on 1/28
codya321 said:
I have no problem adjusting brightness on 1/28
Click to expand...
Click to collapse
It's weird. I couldn't get it to work without using the Tablet UI. Once I switched, it started working. Oh well, it's working fine now. Thanks for the help, you guys are the best.
CM 10.1 needs some time for settle. Then it works wthout lag
Sent from my GT-I9100 using Tapatalk 2
Hey there,
I went from stock to CM10.1 and everything works correctly, except that I get bluescreens and now random reboots. I update nightlies hoping that the problem disappears.
Is there anyone that can help me with that issue. It happens randomly, even when it just sits there doing "nothing".
Please help, I don't want to go back to T-Mobile stock (that's where it last worked)!
ami2510 said:
Hey there,
I went from stock to CM10.1 and everything works correctly, except that I get bluescreens and now random reboots. I update nightlies hoping that the problem disappears.
Is there anyone that can help me with that issue. It happens randomly, even when it just sits there doing "nothing".
Please help, I don't want to go back to T-Mobile stock (that's where it last worked)!
Click to expand...
Click to collapse
You could always use the stable version of CM10. It's still Jellybean, just 4.1.2 instead of 4.2.2. My biggest problems with CM10.1 are bluetooth and connecting it to the PC as a Mass Storage Device. With CM10, I have never had issues.
Go up and read the threads in the general forum. The last really stable cyanogenmod releases were the M3 "snapshot". Anything after that is what you get, random reboots, graphical problems etc. Try that one.
fraughtsigewulf said:
You could always use the stable version of CM10. It's still Jellybean, just 4.1.2 instead of 4.2.2. My biggest problems with CM10.1 are bluetooth and connecting it to the PC as a Mass Storage Device. With CM10, I have never had issues.
Click to expand...
Click to collapse
srpanadero said:
Go up and read the threads in the general forum. The last really stable cyanogenmod releases were the M3 "snapshot". Anything after that is what you get, random reboots, graphical problems etc. Try that one.
Click to expand...
Click to collapse
Ok i will try the M3, and not do the nightlies.
I ll report back if that solved my problem.
Fixed. read post above.
Thank you so much for your help!!
I see problem fixed sorry to hijack but what version of clockword mod are u running. I have 5.5. Orsomething like that but can download and roms? Error 7 keeps popping up. And if i upgrade cwm where and how would that be. Sorry once again
parmakr said:
I see problem fixed sorry to hijack but what version of clockword mod are u running. I have 5.5. Orsomething like that but can download and roms? Error 7 keeps popping up. And if i upgrade cwm where and how would that be. Sorry once again
Click to expand...
Click to collapse
That has nothing to do with the problem. But it is because you are using an old recovery, either update CWM or use goo manager to install TWRP, which is touchscreen anyways. Then you wont have the Error 7 anymore.
Hi guys!
I'm a newbie here at XDA. Long time ago, I have formatted my Optimus 2X from GB to ICS using smart flash tool. I have done that successfully. After few months, I felt like my phone is slow to respond. Then I decided to repartition and install fresh ICS copy again. I was not 100% sure what I was doing at that time. I have used AIO tool for this. Selected option no. 4 and have selected CWM v6.0.2.5 as recovery.
Then I tried to install the new ROM using smart flash and I did not succeed. After I have messed up with this problem, I contacted "spyrosk" (the OP of AIO tool thread) and he told me to install stock ROM on this thread. Then I have downloaded the V30A ROM and copied out to the phone memory, and installed using cwm by selecting install zip from sdcard option. I have succeeded.
But now I want get my phone back to the situation where I installed ICS in first time (GB to ICS using smartflash). Because my camera isn't working, OS freezes pretty much, etc. So I tried several times using Smart flash (in AIO tool) tool as I did as same as when I update from GB to ICS. But, I'm getting an error. Time out reached, after few minutes.
Should I remove CWM before install the fresh stock ICS rom using smart flash? Please guide me through this as I am a newbie for these kind of things. All I want to do is, bring back my phone to the same situation where I upgrade from GB to ICS, as I told you at the beginning of this thread.
Please don't ignore this thread by thinking I am an epic noob at this. Guide me and I'll do exactly as you guys say. Thanks a lot for reading. A reply would be greatly appreciated. :angel:
Anyone? Please.
BUMP. Can someone please give me an advice? I'm kinda disappointed right now.
androidpradeep said:
BUMP. Can someone please give me an advice? I'm kinda disappointed right now.
Click to expand...
Click to collapse
There is nothing to worry about, just keep trying using smartflash. After each try remove the cable then connect it back, if it still not works restart teh phone to S/W screen. If it still not works try it on an other usb port, and do everithing from the begining. If it still fails use another cable or try it on an other computer.
It usually start work for the 6th or the 7th time of trying.
No need to remove cwm or anything like that.
bitdomo said:
There is nothing to worry about, just keep trying using smartflash. After each try remove the cable then connect it back, if it still not works restart teh phone to S/W screen. If it still not works try it on an other usb port, and do everithing from the begining. If it still fails use another cable or try it on an other computer.
It usually start work for the 6th or the 7th time of trying.
No need to remove cwm or anything like that.
Click to expand...
Click to collapse
Thank you very much for replying this thread BitDomo. I will try some more times then. Apart from that, I have seen a way to uninstall CWM by installing some files to the device. But I did not try that since that method is for CWM v3.x.x.
I'm kinda noob at savvy android thingies for now. I will learn some more about these thingies from the start of next month. Until then, I just want to bring my phone to official ICS 4.0.3 stock ROM and use the phone as I did earlier.
Thanks again for your kind reply to this thread bro. Really appreciate. I'll try some more times and will post the results. Dear android experts, any other solutions for this? Please make a post if you have a suggestion. Peace.. :highfive:
Please help
Guys I have tried over 10 times to flash to ICS 4.0.4 using Smartflash. But everytime I end up with same error. Then I tried Nvflash. But my device showed me a black screen after the process completed. Everything working correctly but I couldn't see anything on my LCD, its just a black screen with the light. So, I used full brick repair for P990 here at xda.
Now I have CWM v6.0.2.5 as recovery and CyanogenMod 10-20131105-UNOFFICIAL-p990 in my phone. Can someone please explain me how to bring this phone back to official ICS 4.0.4? I tried smartflash right now and device shows a black LCD screen. Smartflash picks up the device but process stops in few seconds. I have searched for revert back to stock ICS from CM, but I did not get a descriptive enough information for this. Please write atleast a brief reply if you know the procedure. Thank you very much. :good:
androidpradeep said:
Guys I have tried over 10 times to flash to ICS 4.0.4 using Smartflash. But everytime I end up with same error. Then I tried Nvflash. But my device showed me a black screen after the process completed. Everything working correctly but I couldn't see anything on my LCD, its just a black screen with the light. So, I used full brick repair for P990 here at xda.
Now I have CWM v6.0.2.5 as recovery and CyanogenMod 10-20131105-UNOFFICIAL-p990 in my phone. Can someone please explain me how to bring this phone back to official ICS 4.0.4? I tried smartflash right now and device shows a black LCD screen. Smartflash picks up the device but process stops in few seconds. I have searched for revert back to stock ICS from CM, but I did not get a descriptive enough information for this. Please write atleast a brief reply if you know the procedure. Thank you very much. :good:
Click to expand...
Click to collapse
Problem solved. The thing we learnt today is that the battery have to be inserted when you use smartflash.
Sent from my LG-P990 using xda app-developers app
bitdomo said:
Problem solved. The thing we learnt today is that the battery have to be inserted when you use smartflash.
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
This dude is a genius. This tip fixed my phone instantly. If any of you had the same problem, remember NOT to remove the battery when you do a smartflash. So its time to close the thread.
i said it many times on forum
Hi,
I have a problem wit the CM11 nighly builds. Since the Kernel was updated (begin of Feb.) I must insert my PIN number of the simcard more than one times a day.
Often I must insert my pin 2-4 times at one day.
I have also clean the caches, but the problem is still there.
Also the usage of the idoak Kernel does not fix this Problem.
Have someone the same trouble. How can I fix this problem?
I'm quite sure you didn't flash the ROM in a proper clean way.
I think it's ROM related and not kernel related. Try a full wipe with cache cleaning as well as formatting system under mounts and storage in cwm.
Then flash your ROM + Gapps and maybe your kernel.
Backup your current ROM just to be sure, you can restore /data after clean install with advanced restore to get your apps etc back.
Sent from my LG-P880 using XDA Premium 4 mobile app
I had the same issue. I resolved it with newer nightly and clean install.
Cheers
Ur loosing connection to network, probably due to ril problems. Check my sig for possible solution
I have done yesterday the following.
1. Backup current ROM
1. Clean /system
2. Clean Dalvik
3. Clean cache
4. Wipe All
5. Install CM11 Nighly
6. Reboot (phone comes up)
7. restore /data from backup
But now before 30 Minutes I must insert my Pin number again.
It seems that the problem came when the phone wakeup from deep sleep.
It might also be caused by a faulty or not properly inserted Sim card.
Sent from my LG-P880 using xda app-developers app
Yes maybe, but I have this problem not before update.
I have also fixed the sim card with a tape in my phone.
Problem still there
Hi,
the problem is still there.
I have now make a complete clean installation with cleaning of /system too.
But sometimes I must insert the PIN again.
Currently I have installed the nightly build 11-20140308-NIGHTLY-p880 with the default kernel.
I have enabled debugging and logged the reason. The log file is attached in this post.
Can anyone please look at the logfile.
For me it looks like that the phone disables or lost the radio.
I hope you can now help me.
Works with another ROM
I have installed last saturday the ROM NAMELESS and the SIM problem is not there, all works fine.
So there must be a problem in the orginal CyanogenMod 11 version.
I think the developers from the CM11 should search the problem.
By the way, the NAMELESS ROM has much better battery usage.
heliflieger9 said:
I have installed last saturday the ROM NAMELESS and the SIM problem is not there, all works fine.
So there must be a problem in the orginal CyanogenMod 11 version.
I think the developers from the CM11 should search the problem.
Click to expand...
Click to collapse
Same on my phone (ril bug/sim-pin-bug).. with Original LG Firmware no problem at all.. with CM11 several times a day I have to enter the pin.
heliflieger9 said:
I have installed last saturday the ROM NAMELESS and the SIM problem is not there, all works fine.
So there must be a problem in the orginal CyanogenMod 11 version.
I think the developers from the CM11 should search the problem.
By the way, the NAMELESS ROM has much better battery usage.
Click to expand...
Click to collapse
Although your problem seems to be solved, I wanted to be sure that the hint from Flying_Bear was understood.
What is important in @Flying_Bear signature is not the process of flashing, but his method of patching the RIL, which is described here http://direct.xda-developers.com/showpost.php?p=46751745 .
I tried it, and believe it makes a huge difference.
Did you try that?
Ottonet said:
Although your problem seems to be solved, I wanted to be sure that the hint from Flying_Bear was understood.
What is important in @Flying_Bear signature is not the process of flashing, but his method of patching the RIL, which is described here http://direct.xda-developers.com/showpost.php?p=46751745 .
I tried it, and believe it makes a huge difference.
Did you try that?
Click to expand...
Click to collapse
No, I did not try that, because I won't change this every time I install a new nightly. I think this is so, is it?
I see, that the RIL in other ROMs like Nameless ROM work, why did the CM developers not change it?
heliflieger9 said:
No, I did not try that, because I won't change this every time I install a new nightly. I think this is so, is it?
I see, that the RIL in other ROMs like Nameless ROM work, why did the CM developers not change it?
Click to expand...
Click to collapse
Yes, that is understandable, When I had that problem I considered the opportunity of tweaking the RIL every time I updated a Rom, then since many, many nightlies and with iodak 9.95 kernel I did not see baseband wakeock appearing again, so I almost forgotten the matter.
Though I believe that it is not necessary to replicate the process described by Flying_Bear from the beginning to the end. All you have to do is getting a modified "telephony-common.jar" then, after each upgrade, copy that file into /system/framework, give it the correct permissions/owners and reboot.
Mind that I did not try this method, and don't know if it makes sense at all, maybe @Flying_Bear can give us a confirmation. If it worked, it would be no much hassle.
Inviato dal mio GT-P3110 utilizzando Tapatalk
Unfortunately, telephony-common.jar is usually incompatible from nightly to nightly (usually). With practice, the process takes only a few mins. Try upgrading weekly instead of nightly
I have now tested the RIL changes from @Flying_Bear for two days.
It works and I must not insert my SIM-Card pin again.
I see in official CM thread that some people have currently also RIL problems. Did the CM developer know about this problems?
heliflieger9 said:
I have now tested the RIL changes from @Flying_Bear for two days.
It works and I must not insert my SIM-Card pin again.
I see in official CM thread that some people have currently also RIL problems. Did the CM developer know about this problems?
Click to expand...
Click to collapse
not sure if they know there are specific problems, but the solution was presented to them back for cm10, and arcee rejected it due to many mentions of eternityproject inside the code itself (which normal users don't care about, as they care about stable RIL, and don't care who contributed)
Check this
http://forum.xda-developers.com/optimus-4x-hd/orig-development/ril-baseband-fix-t3134167
First and foremost, let me say that I messed up.
Now that that's out of the way, let me begin;
I have a VS980 (obviously) with Cyanogenmod 11 running the latest nightly (6-26 I believe, running 4.4.4), and as many know the Verizon version has had issues with any rom with rotation issues. So I decided to search around and try and find a fix for this, and the most likely fix seemed to be flashing a KK baseband. I know before that my device was 12B or whatnot.
Well, now I'm in a bootloop, and have no clue what to do next.
Ive tried restoring from a nandroid backup and straight up reflashing the ROM.
I have TWRP 2.7.0.0 installed, but my United drivers wont recognize my G2 when in recovery (even though the computer sees it as "VS980" in devices), and I just downloaded and started up the SDK, but haven't downloaded anything other than that.
What I think might work is pushing the correct baseband to the phone, but I have no idea how to do so. I know basic ADB from a past experience, but very very basic.
I need some direction as what to do is what I'm saying. Any and all help is much appreciated, thank you so much!
Chirzu said:
First and foremost, let me say that I messed up.
Now that that's out of the way, let me begin;
I have a VS980 (obviously) with Cyanogenmod 11 running the latest nightly (6-26 I believe, running 4.4.4), and as many know the Verizon version has had issues with any rom with rotation issues. So I decided to search around and try and find a fix for this, and the most likely fix seemed to be flashing a KK baseband. I know before that my device was 12B or whatnot.
Well, now I'm in a bootloop, and have no clue what to do next.
Ive tried restoring from a nandroid backup and straight up reflashing the ROM.
I have TWRP 2.7.0.0 installed, but my United drivers wont recognize my G2 when in recovery (even though the computer sees it as "VS980" in devices), and I just downloaded and started up the SDK, but haven't downloaded anything other than that.
What I think might work is pushing the correct baseband to the phone, but I have no idea how to do so. I know basic ADB from a past experience, but very very basic.
I need some direction as what to do is what I'm saying. Any and all help is much appreciated, thank you so much!
Click to expand...
Click to collapse
If you can get it in download mode, restore it back to stock using the guide in the General section..
Doesnt download mode require it to actually boot? Im bootlooping.
Sent from my SCH-I510 using XDA Free mobile app
Chirzu said:
Doesnt download mode require it to actually boot? Im bootlooping.
Sent from my SCH-I510 using XDA Free mobile app
Click to expand...
Click to collapse
You should still be able to get into recovery, it's just getting the timing right. Recovery has it's own kernel.
Try holding down power for 15 or so seconds til it restarts, immediately hit the volume down and power, let go when the LG splash screen comes up and hit them both again.
You'll get the factory hard reset screen, keep hitting power til it gets you to Recovery.
CM11 nightlies are still based on JB kernel source, so you need the 12B radio for it to boot. That's why you're bootlooping. So if you have a 12B radio on your SD, you can flash that. Then clean flash your current build of CM11. Should boot up then. If I was you I'd think about updating to 24A, and use one of the ROMs that use KK kernel source. There's a CM11 for 24A build out. Not in nightlies but pretty frequent builds.
mjones73 said:
You should still be able to get into recovery, it's just getting the timing right. Recovery has it's own kernel.
Try holding down power for 15 or so seconds til it restarts, immediately hit the volume down and power, let go when the LG splash screen comes up and hit them both again.
You'll get the factory hard reset screen, keep hitting power til it gets you to Recovery.
Click to expand...
Click to collapse
Its not Recovery that I have an issue getting into, its download mode. I have no problem getting into there, however, I have no idea about anything regarding download mode.
JRJ442 said:
CM11 nightlies are still based on JB kernel source, so you need the 12B radio for it to boot. That's why you're bootlooping. So if you have a 12B radio on your SD, you can flash that. Then clean flash your current build of CM11. Should boot up then. If I was you I'd think about updating to 24A, and use one of the ROMs that use KK kernel source. There's a CM11 for 24A build out. Not in nightlies but pretty frequent builds.
Click to expand...
Click to collapse
I dont think I do, but do you know how I can get my drivers to work or where I can pull drivers from for my laptop to recognized my phone so I can push a radio to it?
Will definitely think about KK in the future, thank you.
Sent from my SCH-I510 using XDA Free mobile app
http://forum.xda-developers.com/showthread.php?t=2448960 I got mine from this thread. I've had issues too some. Sometimes I've actually had to install them a couple times with the phone plugged into my laptop to get them to work
Thanks man, Ill definitely try that out when I get to my computer.
Sent from my SCH-I510 using XDA Free mobile app
JRJ442 said:
http://forum.xda-developers.com/showthread.php?t=2448960 I got mine from this thread. I've had issues too some. Sometimes I've actually had to install them a couple times with the phone plugged into my laptop to get them to work
Click to expand...
Click to collapse
Update: The drivers honestly didn't matter in the end I think, as I tried it with 3/4 of them successfully installing (The CDC one never installed correctly) and everything went perfectly!
Thank you so much for pointing me in the right direction.
Sent from my kickass VS980