Hey guys, I'm new here.Soon my new Nexus4 will arrive and i have some questions about installing cyanogenmod.
1.Can I install cyanogenmod with the new cm installer on this device??
2.If this is possible and i install cyanogenmod, how do i update the version if a newer one is released ??
3.I red that the cm intaller install a custom recovery too, if i dont like the cyanogen mod can i install other roms or i must do something before ??
4.If i use this cm installer i know that i will lose my warranty, am i right ?? And if yes, is there any posiblity to restore the phone to original state (i mean lock back the bootloader and others) ?
Thanks
On the same page of this forum is a Cyanogenmod Q & A thread, I would start there and READ.
Sent from my Nexus 4 using Tapatalk
I prefer installing ROMs through a custom recovery because you can unlock the bootloader and install a custom recovery without disturbing the phone's existing ROM.
AndyTimE said:
Hey guys, I'm new here.Soon my new Nexus4 will arrive and i have some questions about installing cyanogenmod.
1.Can I install cyanogenmod with the new cm installer on this device??
2.If this is possible and i install cyanogenmod, how do i update the version if a newer one is released ??
3.I red that the cm intaller install a custom recovery too, if i dont like the cyanogen mod can i install other roms or i must do something before ??
4.If i use this cm installer i know that i will lose my warranty, am i right ?? And if yes, is there any posiblity to restore the phone to original state (i mean lock back the bootloader and others) ?
Thanks
Click to expand...
Click to collapse
1) Yes
2) In Settings there will be an update option, you can also flash ZIP by downloading them from (http://download.cyanogenmod.org/?device=mako)
3) Yes, you can install other ROMS and gapps from recovery.
4) Yes, you can use google's stock images to restore your phone to original state.
whitemolecule said:
1) Yes
2) In Settings there will be an update option, you can also flash ZIP by downloading them from (http://download.cyanogenmod.org/?device=mako)
3) Yes, you can install other ROMS and gapps from recovery.
4) Yes, you can use google's stock images to restore your phone to original state.
Click to expand...
Click to collapse
Thanks a lot man. So about restoring at point the 4th question. Just flash in cwm a the stock rom and that's it?
AndyTimE said:
Thanks a lot man. So about restoring at point the 4th question. Just flash in cwm a the stock rom and that's it?
Click to expand...
Click to collapse
Not actually, you need to flash it via fastboot after installing device drivers from your computer. Which is a small tool that comes with Android SDK. (You can find it everywhere)
But I am sure there are flashable recovery ZIPs for stock ROMs on this forum.
AndyTimE said:
Thanks a lot man. So about restoring at point the 4th question. Just flash in cwm a the stock rom and that's it?
Click to expand...
Click to collapse
Here's a link to WUG's toolkit that can help with your Nexus 4: http://www.wugfresh.com/nrt/
Being that you're a noob (just like me) you may want to try flashing things with the android SDK instead of a toolkit (not saying it's bad, I've actually never used it). I just started messing with my nexus 4 using the SDK and some of the write ups here and found them really helpful and I learned a lot. Then again, if you consider yourself computer illiterate (not saying you are, your choice) you may WANT to use the toolkit. Just my .02.
Sent from my Nexus 7 using xda app-developers app
whitemolecule said:
Not actually, you need to flash it via fastboot after installing device drivers from your computer. Which is a small tool that comes with Android SDK. (You can find it everywhere)
But I am sure there are flashable recovery ZIPs for stock ROMs on this forum.
Click to expand...
Click to collapse
By using that CM installer to unlock bootloadder and install cwm and cyanogenmod, is there any change to brick the device or any incompatiblities ?? Just take the phone out of box install that CM app on the phone and on the pc and start ??
Edit: The app is no more in playstore, from where can i take that official app ??
You can take it from get.cm
Sent from my Nexus 4 using xda app-developers app
AndyTimE said:
By using that CM installer to unlock bootloadder and install cwm and cyanogenmod, is there any change to brick the device or any incompatiblities ?? Just take the phone out of box install that CM app on the phone and on the pc and start ??
Edit: The app is no more in playstore, from where can i take that official app ??
Click to expand...
Click to collapse
You can download app as an apk file from their site: http://beta.download.cyanogenmod.org/install
It is a Nexus device, so it is hard to brick it.
I have been using custom ROMS from first day I bought the device and I haven't got a problem. As I said you can revert back to stock ROM or just try another ROM.
No one can warrant you that everything will work and there is always a chance of brick, but not too much if you do everything right.
so just update to latest official version of kitkat and then i use that cm installer without anything to do before like root or unlock bootloader ?
Related
Hey Guys,
i downloaded the nexus 4 toolkit. the latest build (4.2.2) isn´t shown there.
i dunno which version is included in the stock n4. i will get it in a few hours and i just wanted to ask, if my plan is gonna work xD
1. update to the latest version
2. unlock bootloader
3. customrecovery
4. flash rom
the only problem i am facing now, is that i don´t know if the toolkit can unlock the latest bootloader, because "JDQ39" isn´t shown as listed device. or should i unlock the bootloader on a previous version, the stock delivered (i don´t think it will come with 4.2.2) and then install the stock image? as i know from my galaxy nexus the bootloader will be unlocked after that. but i´m not sure how it is with the nexus4.
i hope someone can help me. it might be a noobquestion. i just want to make sure that everything works fast, because this nexus4 is a present for my sister and she´s waiting for it
L-ViZ said:
Hey Guys,
i downloaded the nexus 4 toolkit. the latest build (4.2.2) isn´t shown there.
i dunno which version is included in the stock n4. i will get it in a few hours and i just wanted to ask, if my plan is gonna work xD
1. update to the latest version
2. unlock bootloader
3. customrecovery
4. flash rom
the only problem i am facing now, is that i don´t know if the toolkit can unlock the latest bootloader, because "JDQ39" isn´t shown as listed device. or should i unlock the bootloader on a previous version, the stock delivered (i don´t think it will come with 4.2.2) and then install the stock image? as i know from my galaxy nexus the bootloader will be unlocked after that. but i´m not sure how it is with the nexus4.
i hope someone can help me. it might be a noobquestion. i just want to make sure that everything works fast, because this nexus4 is a present for my sister and she´s waiting for it
Click to expand...
Click to collapse
Normaly it should work, allthough it is not the exact firmware the procedure stays the same. So you should be good.
But between item 3 and 4 comes flashing the superSU zip with CWM/TWRP from here http://download.chainfire.eu/315/SuperSU/UPDATE-SuperSU-v1.25.zip. After reboot you also have to install Busybox from Google play, after that make a nandroid backup in recovery and then flash the rom.
mmh don´t need root in my case, if the recovery will be installed by toolkit, root will be included in the rom anyways
L-ViZ said:
mmh don´t need root in my case, if the recovery will be installed by toolkit, root will be included in the rom anyways
Click to expand...
Click to collapse
Root is not achieved by flashing a ROM.
UberSlackr said:
Root is not achieved by flashing a ROM.
Click to expand...
Click to collapse
It can indeed be achieved that way. If you have an unlocked bootloader and custom recovery then you still might not have root, but you could just flash a pre-rooted custom ROM.
Sent from my Nexus 4
steviewevie said:
It can indeed be achieved that way. If you have an unlocked bootloader and custom recovery then you still might not have root, but you could just flash a pre-rooted custom ROM.
Sent from my Nexus 4
Click to expand...
Click to collapse
that´s it
Don't use the toolkit, it's easy to do manually. That way you will learn more about the steps involved, which will come in very handy if you have a problem with the phone in the future.
Sent from my Nexus 4
Will I get updates from Google. if I root my Nexus 7 and i'm on a custom ROM?
abhilashbaishya said:
Will I get updates from Google. if I root my Nexus 7 and i'm on a custom ROM?
Click to expand...
Click to collapse
On a custom rom No. Rooted running stock you will get updates dont make the same mistake i did when running stock and delte custom apps just freez them
Next time pal post in the q&a for subjects like this and have a search
Sent from my HTC One X using xda premium dont forget to hit the thanks button if i helped you
You will successfully get an OTA if...
You're using the stock kernel
You have not renamed/deleted/mangled files in /system
You have not installed garbage like Beats etc which modify libraries
You have not screwed with your framework to bling it
ie: YOUR ROM IS STOCK
You STILL get, and apply an OTA, if you have..
Unlocked your bootloader
Rooted your device
You're using a modern CWM or TWRP
khaytsus said:
You STILL get, and apply an OTA, if you have..
Unlocked your bootloader
Rooted your device
You're using a modern CWM or TWRP
Click to expand...
Click to collapse
If you install a custom recovery you won't be able install the update naturally. You'll have to download the update and install from recovery manually.
Visa Declined said:
If you install a custom recovery you won't be able install the update naturally. You'll have to download the update and install from recovery manually.
Click to expand...
Click to collapse
Good point, but it will install just fine. But yes, you have to boot into recovery and flash the OTA zip file.
So, i was in a hurry and i downloaded the wrong kernel. I wanted to download the linaro franco kernel for android 4.4, but instead i downloaded this one "franco.Kernel-nightly-r14-linaro.zip". this is an old version.
So now, my device does not boot and i cant install the correct kernel file.
What should I do?
Use a toolkit like wug and install through it the stock or any custom kernel you want.
Unleashed by my Nexus 4
But...
But, there is a way to only replace the kernel or i have to re-install the ROM?
Re-install only the kernel may affected something?
Thanks a lot.
Marcelo Diniz said:
But, there is a way to only replace the kernel or i have to re-install the ROM?
Re-install only the kernel may affected something?
Thanks a lot.
Click to expand...
Click to collapse
Didn't make a nandroid before you flashed it?
Start fresh... In the future make a nandroid and make dam sure you have correct files before you flash
Sent from my Nexus 4 using XDA Premium HD app
fastboot flash boot kernel.img
OK
I flashed the stok room again using WugFresh toolkit.
Totaly woks.
Thaks for help.
Hey everyone, sorry if this question has been answered already. I have sifted through pages and pages in this forum and haven't found a solution for my D800.
My G2 is rooted, with TWRP installed. I was successful in flashing Paranoid Android v4 beta 4, and 5. The problem arises when I try to flash LG Stock based ROMS. After TWRP says flashing was successful and I try to reboot, the screen shows LG logo for a second and turns blank!! That's it just a clear black screen, and the ROM doesn't boot at all.
The ROMs I tried and failed to boot:
1. Aeon
2. Korean stock based rom
3. Scott's CleanROM
4. Rayglobe 3.2
5. Rayglobe Flex ROM v4
Now, I know that sometime ROMs take time to boot on the first run, so I even tried leaving it at the blank screen for 15-20 mins with no result. Since it has been the same result for multiple ROMs, it definitely isn't a bad install or a bad ROM download either. I hope not
Is there anything I am missing in the steps? All ROMs were installed after factory resetting through TWRP (no dirty flash). I am baffled with this, please let me know if I need to revert to software version "d" for these ROMs to work?
TIA
vish9 said:
Hey everyone, sorry if this question has been answered already. I have sifted through pages and pages in this forum and haven't found a solution for my D800.
My G2 is rooted, with TWRP installed. I was successful in flashing Paranoid Android v4 beta 4, and 5. The problem arises when I try to flash LG Stock based ROMS. After TWRP says flashing was successful and I try to reboot, the screen shows LG logo for a second and turns blank!! That's it just a clear black screen, and the ROM doesn't boot at all.
The ROMs I tried and failed to boot:
1. Aeon
2. Korean stock based rom
3. Scott's CleanROM
4. Rayglobe 3.2
5. Rayglobe Flex ROM v4
Now, I know that sometime ROMs take time to boot on the first run, so I even tried leaving it at the blank screen for 15-20 mins with no result. Since it has been the same result for multiple ROMs, it definitely isn't a bad install or a bad ROM download either. I hope not
Is there anything I am missing in the steps? All ROMs were installed after factory resetting through TWRP (no dirty flash). I am baffled with this, please let me know if I need to revert to software version "d" for these ROMs to work?
TIA
Click to expand...
Click to collapse
Did you factory reset after as well? If I recall correctly Paranoid Android is AOSP. What kernel are you running?
sounds like you are onn the 10o update. You will need to flash back to stock 10d with lg flash tool and then root and install recovery again. Then you should be good to go on flashing roms. I know that some of the newest versions of TWRP and Philz have issues flashing some roms too so that may also be the cause. If you downgrade the recovery you have to the version right before it may fix your issue also
joebob296 said:
Did you factory reset after as well? If I recall correctly Paranoid Android is AOSP. What kernel are you running?
Click to expand...
Click to collapse
Exactly, AOSP ROMs are booting up fine but not the Stock based ones.. I am not flashing any kernels, just the ROM, so I'm assuming it will run on either the stock kernel or the kernel included in the ROM zip?
Have you been successful in installing such ROMs? Am I missing something in the wiping part? Only been doing the factory reset in TWRP before installing any ROM.
Check m
And make sure that you are running the stock kernel. Are you on the 10o update?
Sent from my LG-D801 using Tapatalk
rquiett said:
sounds like you are onn the 10o update. You will need to flash back to stock 10d with lg flash tool and then root and install recovery again. Then you should be good to go on flashing roms. I know that some of the newest versions of TWRP and Philz have issues flashing some roms too so that may also be the cause. If you downgrade the recovery you have to the version right before it may fix your issue also
Click to expand...
Click to collapse
Oh, I hadn't thought about anything being wrong with the recovery.. Always assumed it gets the work done
How do I find previous versions of TWRP compatible with D800?
joebob296 said:
Check m
And make sure that you are running the stock kernel. Are you on the 10o update?
Sent from my LG-D801 using Tapatalk
Click to expand...
Click to collapse
Yes I am on 10o.. Does it have issues with installing other Stock ROMs? If yes, I'll try to follow the thread on using LGFlash tools, I've never done that before. Hopefully its not much difficult to follow the instructions.
That is one of the easiest guides to follow. Be sure to follow the correct set of instructions(depends on carrier) and download the the 10d version.
Sent from my LG-D801 using Tapatalk
joebob296 said:
That is one of the easiest guides to follow. Me sure to follow the correct set of instructions(depends on carrier) and download the the 10d version.
Sent from my LG-D801 using Tapatalk
Click to expand...
Click to collapse
Thanks.. I'll try to do it tonight and post my results here.
joebob296 said:
Be sure to follow the correct set of instructions(depends on carrier) and download the the 10d version.
Sent from my LG-D801 using Tapatalk
Click to expand...
Click to collapse
I'm stuck in the process! Can't change the com port number to 41. The guide is pretty easy to understand. But when I put my phone is download mode and try to change the com port number, it says I don't have the write privileges for this device's setting. I've tried it on both Win 7 and Win 8 laptops, with LG mobility drivers installed.
Is there something in the phone settings I need to enable so that I get the write privileges to change com port number?
Do you have administrator privileges?
Sent from my LG-D801 using Tapatalk
SOLVED!
joebob296 said:
Do you have administrator privileges?
Sent from my LG-D801 using Tapatalk
Click to expand...
Click to collapse
Yay!!! Finally did it!
Issue 1: If faced with write privileges for com port (tried successfully in Win 8)
Solution: After going in to com port properties, click "change settings" and there is the option to change com port number.
Issue 2: Once the port number was changed to 41, rest of the instructions are easy to follow on this thread http://forum.xda-developers.com/showthread.php?t=2633150
Once on D80010d, I rooted with ioroot22, and installed recovery using FreeGee. Just installed Rayglobe 3.2 minutes ago, and it finally booted up!!!
So, the bottomline is that go back to D80010d if you wanna play with Stock based ROMs! I flashed with TWRP 2.6.3.3, so the fault is not with the recovery. That much I can confirm
Thanks for the suggestions guys. Thread solved I guess.
Great. Glad to hear it.
Sent from my LG-D801 using Tapatalk
rquiett said:
sounds like you are onn the 10o update. You will need to flash back to stock 10d with lg flash tool and then root and install recovery again. Then you should be good to go on flashing roms. I know that some of the newest versions of TWRP and Philz have issues flashing some roms too so that may also be the cause. If you downgrade the recovery you have to the version right before it may fix your issue also
Click to expand...
Click to collapse
Thanks for the input. Before I flashed back to D80010d today, I installed older versions of Philz and TWRP but neither helped. So downgrading was sort of a compulsion, in my case at least.
and the moral of the story is, unless you are getting an android version upgrade in the update, do not take the update.
hi all , sorry but my english is so bad
i just bought a galaxy s4 att secondhand , this had bassband UCUAMDL . and i checked the lastest version of it is 4.2.2
can i upgrade my phone up to 4.4 ?
and i dont know terminology about "MF3 - MK2 ............."
could you tell me ?
thanks so much :victory::victory::victory:
Root. Install TWRP recovery. Flash a rom 4.4.4 or try some lollipop love!! You are lucky enough to have an unlocked bootloader..
HORiZUN said:
Root. Install TWRP recovery. Flash a rom 4.4.4 or try some lollipop love!! You are lucky enough to have an unlocked bootloader..
Click to expand...
Click to collapse
thanks so much ,
can you get me links :crying:
but MF3 - MK2 ............. what is it ?
when i flash rom , what i have to notice ?
I hope you don't have MF3. If that's the case, I'm pretty sure that SafeStrap is your only recovery option.
HORiZUN said:
I hope you don't have MF3. If that's the case, I'm pretty sure that SafeStrap is your only recovery option.
Click to expand...
Click to collapse
but i dont know MF3 >"<
what is it ?
how check it on my phone ?
HORiZUN said:
I hope you don't have MF3. If that's the case, I'm pretty sure that SafeStrap is your only recovery option.
Click to expand...
Click to collapse
i am in 4.2.2
sonluyen94 said:
but i dont know MF3 >"<
what is it ?
how check it on my phone ?
Click to expand...
Click to collapse
I have the same question. hopefully someone will be able to explain it to us.
MF3 would be the last three digits of your system software version
HORiZUN said:
MF3 would be the last three digits of your system software version
Click to expand...
Click to collapse
my baseband : I337UCUAMDL
kernel version : 3.4.0-453947 - [email protected] #1
android version : 4.2.2
build number : JDQ39.I337UCUAMDL
it is my phone >"<
You don't have MF3, and that's a good thing. You can install a custom recovery. You need to root, install a custom recovery, and then you can start flashing roms.
sonluyen94 said:
my baseband : I337UCUAMDL
kernel version : 3.4.0-453947 - [email protected] #1
android version : 4.2.2
build number : JDQ39.I337UCUAMDL
it is my phone >"<
Click to expand...
Click to collapse
nogods said:
I have the same question. hopefully someone will be able to explain it to us.
Click to expand...
Click to collapse
Ok, use TowelRoot.com to root the phone, and use TWRP manager to install TWRP on your device. After that check out the development section of this very forum and flash any ROM you wish. 4.2.2 or 4.4.4 or 5.0 or anywhere in between (Just read the thread and instructions first!!!). Whatever you do, never update using the OTA updater on the stock ROM! Also, dotn ever flash an image in Odin that isn't MDL, because if you go higher than MDL, you lose the ability to have a custom recovery. You are one of the lucky ones, cherish the ability, and read through threads before flashing, stuff. Good Luck!
Also, you don't have to worry if the ROM says safestrap compatible, because you don't have to use Safestrap, you can have TWRP instead (which is better), because all Safestrap ROMS are TWRP compatible, but not vice-versa.
npjohnson said:
Ok, use TowelRoot.com to root the phone, and use TWRP manager to install TWRP on your device. After that check out the development section of this very forum and flash any ROM you wish. 4.2.2 or 4.4.4 or 5.0 or anywhere in between (Just read the thread and instructions first!!!). Whatever you do, never update using the OTA updater on the stock ROM! Also, dotn ever flash an image in Odin that isn't MDL, because if you go higher than MDL, you lose the ability to have a custom recovery. You are one of the lucky ones, cherish the ability, and read through threads before flashing, stuff. Good Luck!
Also, you don't have to worry if the ROM says safestrap compatible, because you don't have to use Safestrap, you can have TWRP instead (which is better), because all Safestrap ROMS are TWRP compatible, but not vice-versa.
Click to expand...
Click to collapse
thanks so much :fingers-crossed:
but can you talk to me what rom is good about battery ?
sonluyen94 said:
thanks so much :fingers-crossed:
but can you talk to me what rom is good about battery ?
Click to expand...
Click to collapse
Most if not all. They're all built from either GPE or CM.
All good advice. Plus when you root and get Twrp recovery installed do a backup thru Twrp (Nandroid) and keep on phone and put a copy on pc. That way you have something to restore if you get in trouble. Also, your bootloader is not unlocked. No Att i337s are. Instead devs use an exploit called Loki-Doki to bypass Sammy's security checks to allow custom roms/kernels etc to flash. You can google Loki Doki and read up on it. If the rom or kernel is not loki'd you will have to flash the zip thru recovery to allow the rom or kernel to flash. You will come across this when flashing International roms and kernels. I don't have link any more so maybe someone else can link it. Keep it on SD card. Like noted read OP carefully and last 20 pages of rom thread. Builds newer than MDL are blocked by Att from using Loki and require SafeStrap. Which you don't need to worry about. Although you can read up on it. Good Luck. [emoji1]
Sent from my iPhone 6 Plus using Tapatalk
I hope you won't mind me jumping in your thread.,
I've recently had to odin my mdl phone back to stock. I haven't done that in a long time. I have root, and supersu, and busybox. The TWRP Manager app is malfunctioning and I cannot use it to install recovery. They list the crash I am experiencing in the play store as a known problem, and they say it will take time to fix. I have a good loki'd copy of twrp but the stock recovery doesn't want to install it. I even changed the name to "update.zip" and it fails. So my problem is I need a recovery. I am considering installing Clockworkmod's ROM Manager to install their recovery, and then using their recovery to install the good loki'd twrp that I want. Does this sound like a good plan? I have been away from this hobby for a while.
plasticglock said:
I hope you won't mind me jumping in your thread.,
I've recently had to odin my mdl phone back to stock. I haven't done that in a long time. I have root, and supersu, and busybox. The TWRP Manager app is malfunctioning and I cannot use it to install recovery. They list the crash I am experiencing in the play store as a known problem, and they say it will take time to fix. I have a good loki'd copy of twrp but the stock recovery doesn't want to install it. I even changed the name to "update.zip" and it fails. So my problem is I need a recovery. I am considering installing Clockworkmod's ROM Manager to install their recovery, and then using their recovery to install the good loki'd twrp that I want. Does this sound like a good plan? I have been away from this hobby for a while.
Click to expand...
Click to collapse
You can flash a recovery zip in a custom recovery. So if you have the loki'd twrp in a zip file, flashing cwm first will work
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
You can flash a recovery zip in a custom recovery. So if you have the loki'd twrp in a zip file, flashing cwm first will work
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks man, that's exactly what I was planning. I remember avoiding CWM last year due to some issue on this device so I just wanted to make sure it wasn't going to do more harm than good. :good:
plasticglock said:
Thanks man, that's exactly what I was planning. I remember avoiding CWM last year due to some issue on this device so I just wanted to make sure it wasn't going to do more harm than good. :good:
Click to expand...
Click to collapse
ROM manager didn't work. It said it installed cwm recovery but it didn't. I was able to install the latest TWRP with this ROM Installer and it worked like a charm! I then installed my custom TWRP from there, rebooted recovery, and installed Danvh's Google edition. I'm setting it up right now. I'm so happy to get my phone back. I just hope the odin flash fixed my problems.
To the OP try ROM installer to get your custom recovery going. Also if you like simple and fast AOSP check out Danvh's google edition rom, but stick to 4.4.4 for now. 5.0 is out but its buggy. Here's a link to the custom version of twrp that I use. https://www.dropbox.com/l/iDQQqlzNbyiFbQrMF4XcRc It's already loki'd so you can flash it if you have any problems with the latest build.