Related
Hi,
Sorry if this seems like a dumb question - A bit confused from reading up all the info on upgrading to ICS on the p990.
Im running a volk custom kernel, and CM 7.2 - OS Version 2.3.7.
Whats the "best" way to upgrade to the new ICS? I tried running the LG software update but it doesnt go too well, fails after it tries to detect phone - even though it detects it initially.
Can I get the release that LG released with my setup?
Please advise.
Thanks!
Same situation here. I'm on official cm7.2 and would like to upgrade to ics. But don't think that useing official lg update tool is so good idea - it might brick your phone. It won't update to ics because you aren't running the official GB rom so lg update tool won't upgrade (correct me if i'm wrong).
Maybe the AIO tool would do the trick.
Anyways, people we need your advice!
LOL, use NVflash ICS rom like TG.
for me the best way is using the toolkit to install new partition, new bootloader and recovery
than boot into recovery and flash the room as usual
Thanks Wakata.
Much appreciated. I have tried downloading the toolkit but its always corrupt.. ill download the 7 zip format.
I take it that I will need to back everything up and wipe everything, install new partition, boot loadder and recovery(CWM??), then flash with the new rom and kernel?
I've also used the All-In-One P990-Toolkit to upgrade to ICS.
You can use 1. to backup your internal SD in case you need it later.
Then hit 4. to change the partition layout and after that 8. to flash the new unlocked bootloader. That's all.
Thanks again
Slight problem - I downloaded the 7z file, and extracted them, but cant seem to run the .cmd file? What am i doing wrong here?
scratch that last question.. for some reason the files are corrupt when i download them.. grrrr.
So I followed the instructions, and suprise suprise, I get an error -
Nvflash started
nvflash configuration file error: file not found
An error occured. Read above lines for details
Help please
Nevermind, I had a fiddle and flashed ics 6.0.xxx.. lets see how it goes. Hopefully I havent bricked it lol
Sorry, problem.
I first tried option 1, then 4, then 8.. after its all done, no errors - I boot the phone, and its stuck on the red LG logo.. I've left it there for around 10-15 mins with no luck? Help!
Haha, actually I figured it out. I did realise I didnt have a ROM! Doh! lol rookie mistake.
I downloaded this rom and kernel(1.4ghz OC) and its running pretty well, no bugs so far(touch wood)
Want to downgrade Android version using the RAZR i? Be careful, there are many bricks and things you should know before you do this. Bricked means that the phone is not working or responding to official manufacture software or resetting, essentially a 'hard brick' phone is normally not able to be repaired by the user without exchanging parts inside the phone.
Avoiding Bricked Phones
1. One of the most important rules after you have downgraded/unlocked bootloader is do not accept an Over the Air (OTA) update! Users are reporting that it bricks phones!
2. Do not downgrade from Jelly Bean to Ice Cream Sandwich using RSD Lite, this defnitely results in a hard-bricked phone that cannot be recovered with software. Downgrading using a fastboot can be done yet it is still risky - there are a lot of bricked phones.
Downgrading Jelly Bean to Ice Cream Sandwich
Some users are able to do this while avoiding bricks. There is a huge amount of bricks related to this though. Really know the phone and recovery methods before you try to do it.
Recovering Over The Air brick
If you have unlocked your bootloader and then receive a message notification on your phone or computer saying that there is an update, don't update! This is resulting in a 'soft brick'. If you have a soft brick, download RSD lite (linked below) and flash a ROM.
The Most Common Type of RAZR i Brick
What does the screen say? "Service Required, Code Corrupt"
How? I get about 10 messages per day with this, it's becoming easier to see how the bricks are happening. 1. Using a homemade fastboot or RSD to downgrade from Jelly Bean to Ice Cream Sandwich. Next, the user accepts a Motorola update (called Over The Air). This creates a brick. Then users are trying a popular "unbrick" method which unbricks, then hard bricks. I think the modifcations and downgrade procedures are somehow incompatible, they don't work well together, it is producing the worst kind of brick and it happens here *every day*.
Here I will add links to bricked phones because of the downgrade, there are many more RAZR i threads for bricking from modifications and root in addition to these:
http://forum.xda-developers.com/showthread.php?t=2185954
http://forum.xda-developers.com/showthread.php?t=2126440
http://forum.xda-developers.com/showthread.php?t=2197005
http://forum.xda-developers.com/showthread.php?t=2180972
http://forum.xda-developers.com/showthread.php?t=2191234
http://forum.xda-developers.com/showthread.php?t=2189185
http://forum.xda-developers.com/showthread.php?t=2184877
http://forum.xda-developers.com/showthread.php?t=2157162
http://forum.xda-developers.com/showthread.php?t=2146350
http://forum.xda-developers.com/showthread.php?t=2123324
http://forum.xda-developers.com/showthread.php?t=2173614
http://forum.xda-developers.com/showthread.php?t=2162505
http://forum.xda-developers.com/showthread.php?t=2018998
http://forum.xda-developers.com/showthread.php?t=1945176
http://forum.xda-developers.com/showthread.php?t=2150770
http://forum.xda-developers.com/showthread.php?t=2147442
http://forum.xda-developers.com/showthread.php?t=2095661
http://forum.xda-developers.com/showthread.php?t=2089559
http://forum.xda-developers.com/showthread.php?t=2140305
http://forum.xda-developers.com/showthread.php?t=2138640
http://forum.xda-developers.com/showthread.php?t=2136962
http://forum.xda-developers.com/showthread.php?t=2131564
http://forum.xda-developers.com/showthread.php?t=2127864
http://forum.xda-developers.com/showthread.php?t=2134391
http://forum.xda-developers.com/showthread.php?t=2130903
http://forum.xda-developers.com/showthread.php?t=2121392
http://forum.xda-developers.com/showthread.php?t=2119961
Still want to downgrade? Make sure you have ready enough about recovery etc. and note the huge number of bricks after downgrading Jelly Bean to Ice Cream Sandwich.
Flashing an Original ROM with Motorola's RSD Lite Flash Tool
Use this tool entirely at your own risk. If you modify your phone using this tool, it is your responsibility. This tool is intended to be used by those that have read about ROMs/flashing, including the XDA University guides on this. This should not be used unless you are familiar with these processes. There are many, many new users with bricked phones so don't take this casually! Using this tool to flash wipes all user data. This method of flashing is not known to fix "service required, code corrupt".
The source of this guide is the official Motorola document on this in addition to my own usage.
1. You need to make sure you have the Motorola drivers for the phone installed. You can get them here.
2. You need RSD Lite. You can download that here.
3. You need to download the original ROM that you want to flash. You can download one from here.
4. Your phone should be charged to at least 50%, but I recommend a full charge.
5. Start RSD Lite. Now put the phone in fastboot mode. Connect the phone to the computer.
6. Press the 'browse' button and select the ROM to flash. Your phone should be visible in the lower box on the screen. The ROM information should be visible in the top box to the right.
7. Click the start button. You select the ROM you want and de-compress the ROM. Now flash. When it is finished, it should say that it has completed or failed.
-----Reserved-----
Bricked Moto? Fastboot not responding so can't use RSD lite? Problems switching between Android versions, accepted Over The Air update with unlocked bootloader?
SharpnShiny said:
OK I may be able to help, I've found something.
Bricked Moto? Fastboot not responding so can't use RSD lite? Problems switching between Android versions, accepted Over The Air update with unlocked bootloader? Private Message me!
Click to expand...
Click to collapse
Can you post it here?
Check your mail. :good:
hi
SharpnShiny said:
Check your mail. :good:
Click to expand...
Click to collapse
please post it here .
I have a problem when it begins to vibrate and then turn off. Gets the green light but nothing appears. Can anyone help me?
iMillerp said:
I have a problem when it begins to vibrate and then turn off. Gets the green light but nothing appears. Can anyone help me?
Click to expand...
Click to collapse
Didi you try this solution?
St.Noigel said:
Didi you try this solution?
Click to expand...
Click to collapse
Yes, I tried, but now the message "Service Required Code Corrupt"
When people use that unbrick solution for a 'soft brick', it seems to be 'hard bricking the device' entirely. Personally, I wouldn't use that method for anyone who hasn't used it before.
Hard Brick!! Help
I have the same problem. I tried a few times the unbrick jb to ics method and it works fine, but now after i charged up my battery and would to restart it doesn't load the the software. still having the bootloader logo. i shut it down and unbricked it like this: http://forum.xda-developers.com/showthread.php?t=2184877. After that it reboots, but it says "Service Required Code Corrupt".
Please Help Me!!!!!!
@op
when you used an ota your BOotloader will get a update too thats the problem!
if your bootloader is for jb and you flash ics you will brick. for sure!
if you ever flashed fastboots and never an ota you still have the ics bootloader(i can post later a vers. number of mine ics Bootloader) i think when u downgrade with the correct bootloader you wont get a brick.
but iam not 100% sure. so better dont downgrade!!!
regards
Some users reported that some lines of code in jb fastboots trigger the lock too. But either way, I agree, this phone is quite risky to downgrade!
Nice tuto guy!
but you can add information to unbrick to your tuto...
Excuse my ignorance, but what reason would someone have to downgrade from a "stock" JB to ICS?
I want to know because I'm getting the notification from my carrier that the OTA update is available and I want to know if there's any reason I should not. Currently I'm looking for ways to keep my root(ICS) going into JB and I'm reading about otarootkeep as an option, but I'm wondering if after I upgrade and it doesn't work(lets hope it does), if there's an alternative to root JB without unlocking the bootloader(the same as I have it right now).
Thanks for any replies.
r1c47 said:
Excuse my ignorance, but what reason would someone have to downgrade from a "stock" JB to ICS?
I want to know because I'm getting the notification from my carrier that the OTA update is available and I want to know if there's any reason I should not. Currently I'm looking for ways to keep my root(ICS) going into JB and I'm reading about otarootkeep as an option, but I'm wondering if after I upgrade and it doesn't work(lets hope it does), if there's an alternative to root JB without unlocking the bootloader(the same as I have it right now).
Thanks for any replies.
Click to expand...
Click to collapse
Hi. Well, one of the major reasons that people listed was battery problems. I have to admit, with ICS, my battery lasted 2-3 days. With JB, it last about 1 day. Many people said it was Google Now in JB. I always kept that off, and yet my battery was just 1 day. I did all of the usual things, formatting SD, wiping everything, factory reset, and a lot more, and still just 1 day. There are threads about that, a lot of people not happy with JB battery performance. I know other people had other issues, but just one I had in common with most people was battery.
OK I know there are a few threads on this, I found one about ICS/JB performance that you may be interested in reading: http://forum.xda-developers.com/showthread.php?t=1943058&page=3
Personally, I don't think there's a 'wrong' option, but do know that downgrading from JB to ICS on this phone is creating a LOT of bricked phones. So it would be safer to choose one OS or the other! Good luck!
matheusgallo said:
Nice tuto guy!
but you can add information to unbrick to your tuto...
Click to expand...
Click to collapse
No problem! I know for a fact that OTA bricks can be solved with RSD Lite, so that's one positive note! I'll update as soon as I can.
Dear sir,
I am using JB GB (Unlock & root) flash over RSD , then i Omar rom & now Pillama0.8 , can i use mattgroff homemade fastboot to JB (91.2.26001.Retail.en.EU.zip) and then mattgroff homemade fastboot to ICS (81.5.39001.Retail.en.GB.zip - NOTE:must i use mattgroff JB ADB&FASTBOOT file?)
Switching between 2 anytime without any OTA update is ok right?
Thks
Also using Galaxy tab & used to jump among this 3 from GB to ICS & JB with no problem cause each switch (flash or CWM) will flash alterbridge86 developer GB-Stock-Safe-v5.zip which clean & repartition. Hope some can do that for us too.Thks
Bootloader Stucks
HI all, I really need your help:
I've unlocked bootloader through procedure on Motorola website: bootloader has been locked and phone worked well.
after few days I tried to root my phone using Razr_i_root tool.
message on screen reported that root was complete but phone is keeping rebooting itself.
I've tried to make a Factory recovery but with no success.
Also tried to reflash original ROM with RSD lite but installation was aborted at "gpt installation"
I really don't know how proceed...
PLease HELP MEEE!!!
I have not seen those messages before, I cannot figure out how you got them.
Did you install any modifications at all in the few days after your unlocked the bootloader? If you only unlocked the bootloader and rooted, there should be no problem. Since there is a bootloop problem, there must be a conflict. If you have made any more modifications it will likely be them. I would have said try RSD Lite but if that didn't do anything...p.s. do you have a nandroid backup? Did you flash a recovery? Can you get into recovery?
Hello guys,
I'm hoping to get some help here, since I've lost 2 days trying to flash my phone with a custom ROM.
The phone was running Official Android 4.0.4 Ice Cream Sandwich V30A, and I did the following in order to flash it:
After unsuccessful rooting attempts with SuperOneClick (stuck at step 7) I found another way, using nvflash, following these instructions. Somehow I thought I need to unlock the bootloader first, in order to root the phone, so I did that first. After that, I rooted my phone with SuperSU Root as described in this tutorial, and also installed CWM.
I thought that I was ready for the flashing part, and downloaded a custom ROM along with the right GAPPS, and followed the instructions carefully.
First few attempts I got stuck at the beginning of rom flashing process, than I found a solution, where I needed to delete the first line in the META-INF\com\google\updater-script file, then the flashing came trough, but somehow to quick I thought.
After everything was wiped/cleaned/flashed I click on “reboot system now” after which the phone should reboot into the new rom, but nothing happens, the phone acts "dead", it won't turn on, or boot into recovery mod. I was sure that I've bricked my phone, but luckily I was able to get it back on using the APX method with nvflash and boot flash.
But then the phone starts with the official ICS 4.0.4, as if nothing was flashed.
After another day of searching for a solution, I've found out that there are different partitions for different rom's, than I realized that I was trying to flash
Android 4.2.2 Jelly Bean on LG Optimus 2X via Avatar Custom ROM
LG Optimus 2X P990 to Android 4.2.1 CM10.1 Jelly Bean Nightly
Jelly Bean on a ICS device wich logicaly should run on a different partition, so I downloaded a ICS based ROM EAGLESBLOOD™ ICS "AOSP" 4.0.4_r2.1 and got the same issue when flashing, where I had to delete the first line in META-INF\com\google\updater-script, but than the flashing process went trough and seemed more genuine than before as it took longer to finish, so I was happy for a moment, and rebooted the device, and voila nothing...he's deaaaad again.
Can someone please help me to find out where the problem lies.
Thanks for any help, I hope someone takes the time to read this.
No one here to help...
Finally I've managed to install TWRP over CWM with AIO Tollkit, to see if the problem was with CWM.
The flashing process/time seemed similar, but the phone actually booted this time, but not into the new "flashed" custom ROM, but into the old stock one which should be wiped/deleted...
Dont worry too much....
Just use the All In One Tool Kit by spyrosk.....just wipe everything....as I suspect that all your partitions have been disturbed.....for the link for this tool, check my signature
Flash the one from JellyCream.... (it is new bootloader ROM on the dev section) or if you want the 4.3 based CM ROM, then find the one from tonyp....
You will loose the data on the Internal SD card....if you have a backup on the external, then restore form it....
Edit: Eaglesblood ROM is not supported by the developers as far as I know....
Finally
Thank you for replying/helping :good:
As it seems, it was a bootloader issue (ord/new). My phone has the new one, and I thought that the ROMs I've downloaded
Android 4.2.2 Jelly Bean on LG Optimus 2X via Avatar Custom ROM
LG Optimus 2X P990 to Android 4.2.1 CM10.1 Jelly Bean Nightly
EAGLESBLOOD™ ICS "AOSP" 4.0.4_r2.1
would run with the newBL, since they ware recently updated or made, and there was no clear info about the boot loader version.
Now after 3-4 Days of struggling, I've tried a ROM which is made and clearly stated for the newBL,ParanoidAndroid v2.6 "p990-2.6-14-newbl-tonyp.zip" and flashed it without any problems. I didn't have to wipe the whole internal storage with AIO Toolkit, I've followed the usual flashing procedure.:victory::laugh::good: the new rom looks awesome. I hope that I won't have any lock screen or random reboot issues, like before.
Now I'm gonna help a guy, who has the same problem.
Hi there!
First of all, yes, I'm completely new to modding Android phones. Not so new to modding in general though, which makes me question why I made such a nooby mistake... but alas, I now have to ask what many might think to be a nooby question in order to fix said mistake.
Just as the title said, I accidentally installed CWM before flashing my phone, and am now unable to launch into Recovery Mode. I know that there's a way to get it revert it to stock recovery, but as far as I've been able to tell, there's no way to do that without going into the Recovery menu in the first place. Does anybody have an idea what I can do?
My phone can still launch to the firmware (stock firmware, but am planning on installing Cyanogenmod 11), so for now I'm alright but considering the OTHER problems I'm having with the stock firmware, I'd really like a way to get back to my installation ASAP. If I can't, I'll get to my problems with the stock FW later...
-Coover55
Coover55 said:
Hi there!
First of all, yes, I'm completely new to modding Android phones. Not so new to modding in general though, which makes me question why I made such a nooby mistake... but alas, I now have to ask what many might think to be a nooby question in order to fix said mistake.
Just as the title said, I accidentally installed CWM before flashing my phone, and am now unable to launch into Recovery Mode. I know that there's a way to get it revert it to stock recovery, but as far as I've been able to tell, there's no way to do that without going into the Recovery menu in the first place. Does anybody have an idea what I can do?
My phone can still launch to the firmware (stock firmware, but am planning on installing Cyanogenmod 11), so for now I'm alright but considering the OTHER problems I'm having with the stock firmware, I'd really like a way to get back to my installation ASAP. If I can't, I'll get to my problems with the stock FW later...
-Coover55
Click to expand...
Click to collapse
We continue in the other thread
NOTE: This was posted in the past, but I messed up the wording... probably why I didn't get help. I said that I had forgot to flash, but what I forgot to do was to Root my phone. Here's a copy-paste of my previous post, but with fixed wording.
Hi there!
First of all, yes, I'm completely new to modding Android phones. Not so new to modding in general though, which makes me question why I made such a nooby mistake... but alas, I now have to ask what many might think to be a nooby question in order to fix said mistake.
Just as the title said, I accidentally installed CWM before rooting my phone, and am now unable to launch into Recovery Mode. I know that there's a way to get it revert it to stock recovery, but as far as I've been able to tell, there's no way to do that without going into the Recovery menu in the first place. Does anybody have an idea what I can do?
My phone can still launch to the firmware (stock firmware, but am planning on installing Cyanogenmod 11), so for now I'm alright but considering the OTHER problems I'm having with the stock firmware, I'd really like a way to get back to my installation ASAP. If I can't, I'll get to my problems with the stock FW later...
-Coover55
If u remove & insert battery, & then try entering recovery mode(Home+Power keys)...u surely have accessed recovery by now
Coover55 said:
NOTE: This was posted in the past, but I messed up the wording... probably why I didn't get help. I said that I had forgot to flash, but what I forgot to do was to Root my phone. Here's a copy-paste of my previous post, but with fixed wording.
Hi there!
First of all, yes, I'm completely new to modding Android phones. Not so new to modding in general though, which makes me question why I made such a nooby mistake... but alas, I now have to ask what many might think to be a nooby question in order to fix said mistake.
Just as the title said, I accidentally installed CWM before rooting my phone, and am now unable to launch into Recovery Mode. I know that there's a way to get it revert it to stock recovery, but as far as I've been able to tell, there's no way to do that without going into the Recovery menu in the first place. Does anybody have an idea what I can do?
My phone can still launch to the firmware (stock firmware, but am planning on installing Cyanogenmod 11), so for now I'm alright but considering the OTHER problems I'm having with the stock firmware, I'd really like a way to get back to my installation ASAP. If I can't, I'll get to my problems with the stock FW later...
-Coover55
Click to expand...
Click to collapse
Which CWM version did you use? Are you running a Stock rom?