Related
I'm having a bit of a trouble with my Desire X and this because for the past month I have been flashing/messing/bricking it.
First of all, I want to return to completely stock. Rom,kernel,boot,recovery etc.And that because I want to update to Jelly Bean and then install a Jellybean ROM
Secondly, after flashing http://forum.xda-developers.com/showthread.php?t=2113587 I was stuck on bootloop for reasons I don't really know (If you are so kind to explain).
Thirdly can I update to Jelly Bean directly from my Custom Rom? Rather than having to go stock and then update.
I can provide any piece of info about ROM/Kernel etc as long as you need them.
Some are here:
Android Version 4.0.4
ROM ShadowDX v2.0
Kernel 3.0.21-g279c1c [email protected] #2 SMP PREEMPT
Current Recovery TWRP v2.6.3.0 (I have also installed neXusPrime for a try,v1.1 I believe)
CID HTC_304
Unlocked Bootloader (HBOOT 1.24.000, what is this)
I don't have a nandroid backup because I didn't know about it when I started messing with my phone (sorry)
Before I forget can someone teach me how to install boot.img, recovery.img and ROMs THE RIGHT WAY
P.S. I'm 16 y/o and kind of a noob but have read alot about everything for my phone.
P.S.2 Anything for 720p playback? (Optional,have read it doesn't support right now,? some say need kernel?)
P.S.3 Not sure about category of thread
A Wild Magikarp said:
I'm having a bit of a trouble with my Desire X and this because for the past month I have been flashing/messing/bricking it.
First of all, I want to return to completely stock. Rom,kernel,boot,recovery etc.And that because I want to update to Jelly Bean and then install a Jellybean ROM
Secondly, after flashing http://forum.xda-developers.com/showthread.php?t=2113587 I was stuck on bootloop for reasons I don't really know (If you are so kind to explain).
Thirdly can I update to Jelly Bean directly from my Custom Rom? Rather than having to go stock and then update.
I can provide any piece of info about ROM/Kernel etc as long as you need them.
Some are here:
Android Version 4.0.4
ROM ShadowDX v2.0
Kernel 3.0.21-g279c1c [email protected] #2 SMP PREEMPT
Current Recovery TWRP v2.6.3.0 (I have also installed neXusPrime for a try,v1.1 I believe)
CID HTC_304
Unlocked Bootloader (HBOOT 1.24.000, what is this)
I don't have a nandroid backup because I didn't know about it when I started messing with my phone (sorry)
Before I forget can someone teach me how to install boot.img, recovery.img and ROMs THE RIGHT WAY
P.S. I'm 16 y/o and kind of a noob but have read alot about everything for my phone.
P.S.2 Anything for 720p playback? (Optional,have read it doesn't support right now,? some say need kernel?)
P.S.3 Not sure about category of thread
Click to expand...
Click to collapse
First I need to know your cid, secondly you are using a recovery that is not for your hboot so thats why that gets a bootloop.
You need to go back to full stock to update to JB and hboot 1.25 there is no other way
HD playback is and will not possible because our phone doesn't support it
Give me your cid and I or someone else will help you further
A Wild Magikarp said:
I'm having a bit of a trouble with my Desire X and this because for the past month I have been flashing/messing/bricking it.
First of all, I want to return to completely stock. Rom,kernel,boot,recovery etc.And that because I want to update to Jelly Bean and then install a Jellybean ROM
Secondly, after flashing http://forum.xda-developers.com/showthread.php?t=2113587 I was stuck on bootloop for reasons I don't really know (If you are so kind to explain).
Thirdly can I update to Jelly Bean directly from my Custom Rom? Rather than having to go stock and then update.
I can provide any piece of info about ROM/Kernel etc as long as you need them.
Some are here:
Android Version 4.0.4
ROM ShadowDX v2.0
Kernel 3.0.21-g279c1c [email protected] #2 SMP PREEMPT
Current Recovery TWRP v2.6.3.0 (I have also installed neXusPrime for a try,v1.1 I believe)
CID HTC_304
Unlocked Bootloader (HBOOT 1.24.000, what is this)
I don't have a nandroid backup because I didn't know about it when I started messing with my phone (sorry)
Before I forget can someone teach me how to install boot.img, recovery.img and ROMs THE RIGHT WAY
P.S. I'm 16 y/o and kind of a noob but have read alot about everything for my phone.
P.S.2 Anything for 720p playback? (Optional,have read it doesn't support right now,? some say need kernel?)
P.S.3 Not sure about category of thread
Click to expand...
Click to collapse
He has mentioned his cid HTC 304 !
GtrCraft said:
First I need to know your cid, secondly you are using a recovery that is not for your hboot so thats why that gets a bootloop.
You need to go back to full stock to update to JB and hboot 1.25 there is no other way
HD playback is and will not possible because our phone doesn't support it
Give me your cid and I or someone else will help you further
Click to expand...
Click to collapse
He has given it to you so clearly.
304
@ OP
i think you can use RUU, if not, there was a NANDROID Collection thread with backups of people having different CID.
Note the steps carefully.
Install a TWRP or CWM recovery (ICS version because 1.24.000 is ICS hboot)
Then download a nandroid backup made with TWRP or CWM as u chose, from the collection thread.
Put the nandroid backup in appropriate folder.
Boot to recovery and restore.
Now use a tool, of fastboot, to flash stock recovery and stock boot. (you can find that in a thread made by ckpv5). Remember you are on the oldest hboot table, so you need two or three updates to go to JB.
When you have flashed above recovery and boot, restart the phone normally. Set it up. You will receive OTA update notification for JB. Let it happen smoothly.
In the end, when you have JB update completed. Then come back here and see a thread to install a custom JB ROM.
Regards
Yasir
neXus PRIME said:
He has given it to you so clearly.
304
@ OP
i think you can use RUU, if not, there was a NANDROID Collection thread with backups of people having different CID.
Note the steps carefully.
Install a TWRP or CWM recovery (ICS version because 1.24.000 is ICS hboot)
Then download a nandroid backup made with TWRP or CWM as u chose, from the collection thread.
Put the nandroid backup in appropriate folder.
Boot to recovery and restore.
Now use a tool, of fastboot, to flash stock recovery and stock boot. (you can find that in a thread made by ckpv5). Remember you are on the oldest hboot table, so you need two or three updates to go to JB.
When you have flashed above recovery and boot, restart the phone normally. Set it up. You will receive OTA update notification for JB. Let it happen smoothly.
In the end, when you have JB update completed. Then come back here and see a thread to install a custom JB ROM.
Regards
Yasir
Click to expand...
Click to collapse
Thanks man, actually used RUU and went back to stock (after a little tut with ckpv5)
So , you took my advice on my first line, and skipped the rest of my speech :'''(
Sent from my HTC Desire X using Tapatalk
I am rooted, TWRP, on 4.3 build 2.22.xx, and I got s-off on firewater even after the newest AT&T update. I installed ViperOne yesterday and thought my phone had froze on the bootscreen, as it just sits on the HTC "This version is for development use only..." screen, for several minutes before the screen just turns off and at that point everything is fine, I just have to unlock it. I went to the Viper IRC to see if anyone could help, but they didn't seem to know what was wrong, seemed to think maybe I was on the wrong hboot version but I've always been on 3.16. So I thought I would ask here to see if anyone had any ideas. Thanks.
Fallen Advocate said:
I am rooted, TWRP, on 4.3 build 2.22.xx, and I got s-off on firewater even after the newest AT&T update. I installed ViperOne yesterday and thought my phone had froze on the bootscreen, as it just sits on the HTC "This version is for development use only..." screen, for several minutes before the screen just turns off and at that point everything is fine, I just have to unlock it. I went to the Viper IRC to see if anyone could help, but they didn't seem to know what was wrong, seemed to think maybe I was on the wrong hboot version but I've always been on 3.16. So I thought I would ask here to see if anyone had any ideas. Thanks.
Click to expand...
Click to collapse
Same for me, i updated my Viper 1.8.0 to 2.1.0 and now booting takes a long time and like described there is no boot animation
Regards,
Thomas
This also happend to me after flashing the latest build of insertcoin.
I thought it was some sort of bug and flashed back to GPE
Don't know about the missing boot animation, but long boot time and hboot 3.16 means you are on 1.XX based firmware. 2.22 based firmware is needed to fix long boot time. For AT&T in particular, 2.22.1540 firmware is recommended.
The firmware issue has been discussed in quite a few threads to this point. But good instructions here:
http://forum.xda-developers.com/showpost.php?p=54408500&postcount=9592
And also, the firmware is packaged with the following ROM, and with great instruction on how to flash (this is the one I used):
http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
redpoint73 said:
Don't know about the missing boot animation, but long boot time and hboot 3.16 means you are on 1.XX based firmware. 2.22 based firmware is needed to fix long boot time. For AT&T in particular, 2.22.1540 firmware is recommended.
The firmware issue has been discussed in quite a few threads to this point. But good instructions here:
http://forum.xda-developers.com/showpost.php?p=54408500&postcount=9592
And also, the firmware is packaged with the following ROM, and with great instruction on how to flash (this is the one I used):
http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
Click to expand...
Click to collapse
I'm on firmware 2.22.401.5 and I still get the ridiculous boot times. Do I need to update the firmware too?
EchelonBarney said:
I'm on firmware 2.22.401.5 and I still get the ridiculous boot times. Do I need to update the firmware too?
Click to expand...
Click to collapse
if you can see this version in Setting - Info - SoftwareInformation then this is wrong. This is not the real firmware version.
I also did an upgrade from Venom 1.8.0 (4.4.2) to Venom 2.1.0 (4.4.3) and Setting - Info - SoftwareInformation showed me 2.22.401.5.
You have to do a manual firmware update or go back to stock rom and let the stock rom do the firmware update.
That means: Wipe in every case!
That solved my problem.
Regards,
Thomas
funfactor71 said:
if you can see this version in Setting - Info - SoftwareInformation then this is wrong. This is not the real firmware version.
I also did an upgrade from Venom 1.8.0 (4.4.2) to Venom 2.1.0 (4.4.3) and Setting - Info - SoftwareInformation showed me 2.22.401.5.
You have to do a manual firmware update or go back to stock rom and let the stock rom do the firmware update.
That means: Wipe in every case!
Click to expand...
Click to collapse
Truth. There is some confusion about "firmware" as the term is a bit vague. In fact "firmware" can mean any software you flash to solid-state type memory; and "firmware" has often been used interchangeably with the ROM.
However, this is not what is being referred to when "updating the firmware package" (or similar recommendation) is discussed in terms of long boot times, broken WiFi, etc. when using a 2.22 based ROM. In fact, these are modules that reside on separate partitions from the ROM, and not touched when a ROM is flashed. These include hboot, radio, media, WiFi, and other modules. And its these software modules that will not play well with a 2.22 based ROM, if the firmware is not up to date.
Looking at software or build number is Settings does not tell you if your firmware is up to date. It simply tells you the software number for the ROM. There is in fact no actual "firmware number" per se; so folks will often refer to the software number that it deployed with (2.22.401, etc.) for lack of a better description/terminology. However, to confirm if the firmware was properly installed, its actually much more useful to look at hboot number and radio baseband. If you are on hboot 3.16, you do not have the updated firmware. The updated firmware will have installed hboot 3.18. The radio will also have been updated, but I'm not personally familiar with all the possible radio numbers associated with the various firmware package (although I suspect the newer firmware packages contain 1.19xxx basebands).
---------- Post added at 10:27 AM ---------- Previous post was at 10:22 AM ----------
EchelonBarney said:
I'm on firmware 2.22.401.5 and I still get the ridiculous boot times. Do I need to update the firmware too?
Click to expand...
Click to collapse
Make sure you firmware is actually updated, per my long-winded comments above.
Also, be aware that 2.22.401 firmware is not recommended for US users, but rather then 2.22.1540:
http://forum.xda-developers.com/showpost.php?p=54408500&postcount=9592
Not sure if this can cause long boot times, but US users have experienced cell connectivity issues using 2.22.401
redpoint73 said:
Don't know about the missing boot animation, but long boot time and hboot 3.16 means you are on 1.XX based firmware. 2.22 based firmware is needed to fix long boot time.
The firmware issue has been discussed in quite a few threads to this point. But good instructions here:
http://forum.xda-developers.com/show...postcount=9592
Click to expand...
Click to collapse
My duhhh. No boot animation is mentioned right in the post I linked:
The issues you will see without the new firmware include long boot times with no boot animations and some users on 9.1 reported wifi and bluetooth issues.
I knew long boot times was an issue, but no boot animation is definitely caused by outdated firmware, also.
redpoint73 said:
...
Not sure if this can cause long boot times, but US users have experienced cell connectivity issues using 2.22.401
Click to expand...
Click to collapse
I am on 2.22.401.4 and I do experience odd 4G issues (phone says it is connected but I get no data.) Switching airplane mode off and on usually fixes the issue. Are you on 2.22.1540? If so, have you experienced any dropouts? I will drop down to that firmware if it could hold a solid connection for my M8. Thanks.
revoltech said:
I am on 2.22.401.4 and I do experience odd 4G issues (phone says it is connected but I get no data.) Switching airplane mode off and on usually fixes the issue. Are you on 2.22.1540? If so, have you experienced any dropouts? I will drop down to that firmware if it could hold a solid connection for my M8. Thanks.
Click to expand...
Click to collapse
I'm on 2.22.1540 and reception is perfect.
Connection issues is a known problem with the "international" firmware 2.22.401, so I highly recommend flashing 2.22.1540.
Some AT&T folks don't even get service on 2.22.401: http://forum.xda-developers.com/att-htc-one-m8/help/service-upgrade-to-firmware-firmware2-t2834076
redpoint73 said:
I'm on 2.22.1540 and reception is perfect.
Connection issues is a known problem with the "international" firmware 2.22.401, so I highly recommend flashing 2.22.1540.
Some AT&T folks don't even get service on 2.22.401: http://forum.xda-developers.com/att-htc-one-m8/help/service-upgrade-to-firmware-firmware2-t2834076
Click to expand...
Click to collapse
Hello again, sorry to threadcrap but I just flash the 2.22.1540 firmware as recommended and all is well. However, I am curious on why the radio version did not downgrade. From the bootloader, the radio list: 1.19.21331147A1.09G which is the same radio version on 2.22.401.4 firmware. Can you please do me a favor and verify your radio version? I have a suspicion that both firmwares carry the same radio version. Thanks!
revoltech said:
Hello again, sorry to threadcrap but I just flash the 2.22.1540 firmware as recommended and all is well. However, I am curious on why the radio version did not downgrade.
Click to expand...
Click to collapse
You may have to flash the firmware twice for everything to install. This is a common issue.
redpoint73 said:
You may have to flash the firmware twice for everything to install. This is a common issue.
Click to expand...
Click to collapse
I installed the 2.22.1540.3 firmware again but it still reports the same radio version, 1.19.21331147A1.09G, and I do see in the CLI output that an radio.img is being flashed onto the device. I downloaded the firmware from mike1986. website. So, does this mean that the 2.22.401.4 firmware and the 2.22.21540.3 share the same radio.img?
This is the stock developer build radio string...compare all number's/letter's... It is possible that radio is unchanged....
revoltech said:
I installed the 2.22.1540.3 firmware again but it still reports the same radio version, 1.19.21331147A1.09G, and I do see in the CLI output that an radio.img is being flashed onto the device. I downloaded the firmware from mike1986. website. So, does this mean that the 2.22.401.4 firmware and the 2.22.21540.3 share the same radio.img?
Click to expand...
Click to collapse
Wonders_Never_Cease said:
This is the stock developer build radio string...compare all number's/letter's... It is possible that radio is unchanged....
Click to expand...
Click to collapse
Thank you for the screenshot. My radio number is identical to the one in the screenshot. There is a possibility that the version number has a slight difference on the 2.22.401.4 which I previously had installed. I appreciate the help :good:
Hey friends, I am very new to the rooting scene. I have a at&t htc m8 and i made the mistake of trying to root the fast and easy way. I followed a guide by a user names Unlocker. I would post the link but am unable to at this current time because i am new here
That has it's readers use hasoon2000's all in one toolkit. Well I think I screwed up in that process. when my phone was off and charging , the screen would briefly flash the TWRP ui with their lock screen. So naturally I freaked out tried my best to unroot the damn thing by following a guide created by the same guy after he got many complaints of issues
Naturally I had problems with this aswell. Now where i'm at, at this current moment is
**tampered** ***unlocked**
I successfully (i think) removed super su and did my best to get back to stock firmware. well I failed at that aswell. I still have TWRP on my phone and managed to get security turned back on.
What I am asking is for any references or maybe even some fresh help on how i can either get my phone back to stock firmware so i can take the OTA updates and be on my merry way or maybe reccomend a custom rom I can use that has the new lolipop software.
Now i was looking to update my TWRP but I am unable to locate an AT&T verison. I see sprint , verizon, and GSM. I feel pretty helpless right now but if i can get some instruction I know I will be able to figure this out.
I'm still really new to this also, but I'll try my best (just take everything I say w/ a grain of salt...):
Krob189 said:
... when my phone was off and charging , the screen would briefly flash the TWRP ui with their lock screen. ...
Click to expand...
Click to collapse
Do you mean that you'd successfully done whatever you were doing and this was happening in normal use? AFAIK it is normal for the the screen to power off during long-running TWRP actions, and power button wakes it up.
Krob189 said:
...
I successfully (i think) removed super su and did my best to get back to stock firmware. well I failed at that aswell. I still have TWRP on my phone and managed to get security turned back on.
Click to expand...
Click to collapse
Which firmware do you have on it now? Do you have ADB installed? If so, it might be helpful if you post the output of the command
Code:
fastboot getvar all
. If not, I think you'll need ADB and fastboot to help recover.
Krob189 said:
...Now i was looking to update my TWRP but I am unable to locate an AT&T verison. I see sprint , verizon, and GSM ...
Click to expand...
Click to collapse
AT&T uses GSM. The GSM version should be correct. Depending on the firmware you have installed, specific versions of twrp may not work. In my case, twrp 2.8.4.0 wouldn't work on AT&T's stock 4.4.2 firmware, but would on the 4.4.4 firmware.
EDIT: Did you make a TWRP backup before attempting these changes? Depending on the state of your firmware, restoring that might be enough to fix things.
AT&T Stock 4.4.4 RUU
This should solve your problem, if you can achieve s-off again:
AT&T Stock 4.4.4 RUU
Krob189 said:
That has it's readers use hasoon2000's all in one toolkit. Well I think I screwed up in that process. when my phone was off and charging , the screen would briefly flash the TWRP ui with their lock screen. So naturally I freaked out tried my best to unroot the damn thing by following a guide created by the same guy after he got many complaints of issues
Click to expand...
Click to collapse
All the panic is for nothing. Its normal for the TWRP screen to appear for a brief moment when the device is powered off, and you connect the charger. At least on older versions of TWPR (and the version installed by Hasoon's toolkit is quite old).
Krob189 said:
Now i was looking to update my TWRP but I am unable to locate an AT&T verison. I see sprint , verizon, and GSM. I feel pretty helpless right now but if i can get some instruction I know I will be able to figure this out.
Click to expand...
Click to collapse
The TWRP version you want is the GSM. All versions of the M8 are essentially the same (and considered "GSM") except for the CDMA (Sprint & Verizon) and dual SIM variants.
---------- Post added at 12:47 PM ---------- Previous post was at 12:46 PM ----------
brasticstack said:
Do you mean that you'd successfully done whatever you were doing and this was happening in normal use? AFAIK it is normal for the the screen to power off during long-running TWRP actions, and power button wakes it up.
Click to expand...
Click to collapse
What the OP is describing was a known bug, and happened when outside of recovery and while the phone was powered off (and while connecting the charger).
Wow thank you for fast responses!
So from my understanding I have a outdated TWRP version. I suppose I need to read up on how to update this and also how to flash a new rom. I only rooted my phone so I could pair up my ps3 controller to my phone so I can play games on it. I regret doing it now to be honest because I have modded my 3ds to play the same games i was using on my phone
I would love to be on the lolipop update that launched yesterday I believe. Should I stick to a rooted rom or just flash a stock version? Can anyone recommend a good lolipop root that has some tweaks for battery life and overall performance?
Krob189 said:
So from my understanding I have a outdated TWRP version. I suppose I need to read up on how to update this and also how to flash a new rom.
Click to expand...
Click to collapse
Just get the latest version of TWRP from their website. As you are asking what version (CDMA vs. GSM) it sounds like you are already getting there.
It sounds like you have the version of TWRP that was installed by the toolkit. That version is many months old. But its a minor bug, anyway. How often do you charge the phone with it powered off, anyway. I also don't think you can do anything in TWRP in this condition (if a security risk is your concern). The TWRP appears for a split second, and that's it.
Krob189 said:
I would love to be on the lolipop update that launched yesterday I believe. Should I stick to a rooted rom or just flash a stock version? Can anyone recommend a good lolipop root that has some tweaks for battery life and overall performance?
Click to expand...
Click to collapse
Lollipop didn't launch for AT&T, its just a long-delayed 4.4.4 update for us. To update to 4.4.4, either return to stock ROM and stock recovery to get the OTA, or relock the bootloader and run the official RUU.
Lollipop (5.0) started to roll out for some Euro CIDs, and has been out for US Dev Edition for a while. But you can't get to Sense Lollipop unless you s-off (or until AT&T releases it).
(FlashKDZ/Root/Recovery/Hiddenmenu/troubleshooting) (noob2noob guide)
Okay, this is my first thread on XDA, the reason I'm making it is there is a lots of problems with progressing to lollipop. All of this is already mentioned in the forum, but this way it is much easier since it is all at one place. If I'm doing something wrong please warn me with explanation how to resolve the issue. If I'm posting in wrong forum section please move my thread where it is supposed to be.
1. Before doing anything check if your phone is ready to get updated:
1.1 Do you have a stock Kitkat rom or at least a rom that is kitkat based, since there can be a problem with partitioning if custom lollipop rom is installed
1.2 Create a backup. Don't be lazy LG backups will not help you since they can't go from kitkat to lollipop, don't try to do it from recovery because you will lose custom recovery. Copy your files from phone including extracted contacts, and back it up online with google or some other backup providers.
1.3 Check if you have a latest touch firmware, because you might have a problems after installing lollipop and it will be hard for you to check for updates since your touch might become useless.
1.3.1 To check it go to hidden service menu by typing 3845#*802# and go under HW Device Test, then Touch Test then touch firmware version and write everything down. After that go to touch firmware upgrade and after 15 seconds compare the touch firmware version values with those you written down.
1.4 In hidden Menu you can also go to wlan test then ota setting to check if it is disabled on your phone. After that check again if there is OTA updates for your phone, and also check if there is PC suite Update.
1.5 Check your phones version if it is D802, D800 or something else, and check which rom you have installed. You can do this in settings about phone or if you are happy about hidden menu found, go there and into settings then version info. This might not be interesting or fun to do, but it will save you the trouble if something goes wrong, because you will know what to ask.
1.6 Last but not the least, before starting to flash fill up your battery, i've read some posts that say there are problems with wrong capacity shown, and a lots of battery drain problems, and only solution till now is to have a full battery on start.
2. You will need LG FlashTool and of course installed drivers for your G2 on your PC.
All of that you can get in the thread by @quangnhut123 .
2.1 Just a bit of precautions, don't forget to always copy a kdz file in to Flashtool folder and then start a tool. All should look the same as in that thread, except you should always use CSE method because with this method you will install kdz from scratch, removing everything from the phone.
2.2 You should find the kdz file which suits for your phone on site . You can check for kdz by typing in imei in check new firmware section or find the one for yourself by searching the site. v30a is lollipop open while v30d is for branded G2's.
(I've read that this site is not allowed by Xda moderators, so if I can't post it please give me info on where should we download kdz's from).
2.3 I think it's all pure logic now but lets say it one more time. You have downloaded kdz file, and put it inside LG Flashtool folder. You should now start Flashtool and get your phone into Download mode. To do this you need to hold volume up button on turned off device and connect usb cable while holding volume up. Now just cse flash.
2/3 This is troubleshooting step, if you have a problem ask and i hope this great community will help you like they did to me, and ofc I will do my best to help.
3. Now we go to rooting.
Here is the thread by @avicohh which worked for my D802.
Just follow his step by step tut and you will have a rooted phone
3.1 The only issue that might happen here is you are stuck with # and adb waiting for your phone. To resolve this just go into download mode manually.
4. Okay rooting done, now let's go to custom recovery install
It's easy as installing an app from google play by @bender_007
4.1 After installing it open the app and follow the on-screen instructions. If it fails for the first time, try it few more times, it will eventually work. (OFC. I didn't install it with only one try).
4.2 To get into custom recovery hold volume down and power button till first LG sign shows up, then release both buttons and quickly press them again. It will ask you do you want to do factory reset, press yes and yes again, and it will get you to custom recovery if you installed it.
4.2.1 If you factory reset your phone that means you didn't install recovery correctly and you will lose your data, but again that should be no problem since you have that backup from the start.
Now optional steps:
5. Install system app remover to remove bloatware from your phone. You can do it manually but this way you will have those apps backed up.
6. Next suggestion is to install a few mods if you need them. In my case I had to have a Plug and pop, since it is lost from Lollipop and I loved that feature. Here is a thread on how to install that mod by @p_a_r_s_a7
//That's all, if you have any questions feel free to ask, since there is no dumb questions, but also try to read carefully before//
Thanks to:
@quangnhut123
@avicohh
@p_a_r_s_a7
@bender_007
A lot of others whose names i can't remember. If anyone else needs to be mentioned PM me and i will add you in this section.
I will add pictures and stuff if needed
Thanks, good all-in-one thread, + easiest methods. Ill recommend it‚to others
This forum is such a mess that a thread like this is like a fresh breath of air. Every advice given on other threads references something that you should already know how it's done, or you should already have done to your phone in the past and have a certain version of it, or non-working tools that are only around for a few months until an update makes them unusable.
No wonder that most of the first-page topics, including pinned ones, have the word "brick" in the title. This should signal the forum moderators that something is wrong around here.
My phone is stock international sim-free G2, never rooted or otherwise modified and yet no one was able to offer a coherent solution of how to update to Lollipop, until your post.
So, thanks for this thread.
Thank you, that is exactly why i made the thread. Every one of those threads has everything explained, but you need to search theough 150 pages to understand how something is done. That's why i wanted to make a thread with all explanations made in a single post and to make it noob friendly since the worst thing that happens in other threads is answer like use a search you have it somewhere.
Hi,
Thanks for the thread. It really helps noobs like me, but I still have a couple of questions...
I was running Paranoid Android L rom with root, twrp and kk bootloader on My D802.
I didn't see this thread before I decided to downgrade back to 4.2.2 stock rom, and now I don't really know what steps to take.(I have kernel version 3..4.0 and build number JDQ39B)
I haven't seen an OTA available, so I was thinking of flashing new Lollipop rom kdz file. But I've been seeing stuff about using LG PC suite to upgrade via OTA so i wasn't sure.
So my main question is that do I do an OTA upgrade on my current 4.2.2 stock rom or do I download an official Lollipop rom? Can you give me a brief idea of the steps to take?
Thanks
seyio said:
Hi,
Thanks for the thread. It really helps noobs like me, but I still have a couple of questions...
I was running Paranoid Android L rom with root, twrp and kk bootloader on My D802.
I didn't see this thread before I decided to downgrade back to 4.2.2 stock rom, and now I don't really know what steps to take.(I have kernel version 3..4.0 and build number JDQ39B)
I haven't seen an OTA available, so I was thinking of flashing new Lollipop rom kdz file. But I've been seeing stuff about using LG PC suite to upgrade via OTA so i wasn't sure.
So my main question is that do I do an OTA upgrade on my current 4.2.2 stock rom or do I download an official Lollipop rom? Can you give me a brief idea of the steps to take?
Thanks
Click to expand...
Click to collapse
Updating through pc suite or ota is the best way if it is available to you. Flashing kdz is the same thing but that is doing it manually while through pc auite nad ota is pretty much automatic. Anyways which ever way you decide to use be sure to fully charge your battery and factory reset acter the update. If you need anything else feel free to ask
[email protected]$o said:
Updating through pc suite or ota is the best way if it is available to you. Flashing kdz is the same thing but that is doing it manually while through pc auite nad ota is pretty much automatic. Anyways which ever way you decide to use be sure to fully charge your battery and factory reset acter the update. If you need anything else feel free to ask
Click to expand...
Click to collapse
Do I flash KK bootloader or root before I update through ota?
seyio said:
Do I flash KK bootloader or root before I update through ota?
Click to expand...
Click to collapse
No need to flash bootloader if you didnt flash it for paranoid android. And definitely no need to root since you can root after update.
Problems with flashing KDZ
I have downloaded Spain Lolipop KDZ file for LG G2 D802.
Have backed up everything usint TWRP> ( Presently on Optimus G3 rom v 1.4.1 with dorimanx kernel and TWRP )
I have copied the KDZ file to the flash tool. When i use CSE flash .. it takes me to the next page .. in which I click on Start which then opens up the LG Mobile support tool.
Then it shows detecting ur phone .. unpacking or extracting file .. after that shows software updating .. reaches 2 % and then shows error .. asks me to retry .
Do you know what I am doing wrong ? or the cause of this prob ?
http://i58.tinypic.com/15rk2eo.png
sankeerth24 said:
I have downloaded Spain Lolipop KDZ file for LG G2 D802.
Have backed up everything usint TWRP> ( Presently on Optimus G3 rom v 1.4.1 with dorimanx kernel and TWRP )
I have copied the KDZ file to the flash tool. When i use CSE flash .. it takes me to the next page .. in which I click on Start which then opens up the LG Mobile support tool.
Then it shows detecting ur phone .. unpacking or extracting file .. after that shows software updating .. reaches 2 % and then shows error .. asks me to retry .
Do you know what I am doing wrong ? or the cause of this prob ?
http://i58.tinypic.com/15rk2eo.png
Click to expand...
Click to collapse
Had the same problem when flashing kitkat kdz. Are you sure that you have pasted kdzfile inside flashtool. If that is not the problem try other kdz. That helped me
Where are you from and more specifically whhere your phone is from so i can maybe help you with finding right kdz. And btw i think you might have a problem when trying to restore that backup so if you still can backup your phone manually or on the cloud.
[email protected]$o said:
Had the same problem when flashing kitkat kdz. Are you sure that you have pasted kdzfile inside flashtool. If that is not the problem try other kdz. That helped me
Where are you from and more specifically whhere your phone is from so i can maybe help you with finding right kdz. And btw i think you might have a problem when trying to restore that backup so if you still can backup your phone manually or on the cloud.
Click to expand...
Click to collapse
I have restored the complete back up using TWRP .... Yes i have already pasted kdz in the same folder of flash tool...still no change .. now downloading D802 20H firmware to flash stock n den again try KDZ
I have seen that some guys who had the same problem resolved it with disconnecting from network
Sent from my LG-D802 using XDA Free mobile app
sankeerth24 said:
I have restored the complete back up using TWRP .... Yes i have already pasted kdz in the same folder of flash tool...still no change .. now downloading D802 20H firmware to flash stock n den again try KDZ
Click to expand...
Click to collapse
http://www.1x1a.com/fixlg-flash-tool-stuck-at-2.html
Or maybe try this. I havent tried it so i cant promise anything but if you want you can try. Hope it helps
[email protected]$o said:
No need to flash bootloader if you didnt flash it for paranoid android. And definitely no need to root since you can root after update.
Click to expand...
Click to collapse
Hi again..
OTA update to Lollipop has failed on my D802, LG PC Suite only upgraded me from Android 4.2.2 to 4.4.2, so can anyone help me out here?
Am I missing something for OTA update? If not, then which lollipop kdz can I download for my phone so that I can flash? I live in UK and i use a 3 UK sim if that helps
but also, In the process of trying to boot into my previously installed TWRP recovery, I discovered that i have been restored to stock recovery. I have rooted the phone, but just wanted to clarify: I flash custom recovery, then bootloader/kernel then lollipop kdz?
Thanks again
seyio said:
Hi again..
OTA update to Lollipop has failed on my D802, LG PC Suite only upgraded me from Android 4.2.2 to 4.4.2, so can anyone help me out here?
Am I missing something for OTA update? If not, then which lollipop kdz can I download for my phone so that I can flash? I live in UK and i use a 3 UK sim if that helps
but also, In the process of trying to boot into my previously installed TWRP recovery, I discovered that i have been restored to stock recovery. I have rooted the phone, but just wanted to clarify: I flash custom recovery, then bootloader/kernel then lollipop kdz?
Thanks again
Click to expand...
Click to collapse
I am not sure but i think that update for the uk didnt come out yet. so you can't update to lollipop yet via pc suite or ota. and you got it all wrong. first you flash lollipop kdz but you will have to try out few of them since official for uk didn't come out yet, after that you root, and then flash custom recovery.
and as previously you will be back to stock recovery after update. you have it all explained step by step in first post. i know it is a bit long but that is the best way, since i didn't want to write stuff like "you should know that" and so on. so just follow the first post and you will be happy, or wait for official uk update over the ota you will be happy too, and i guess it should come out in a month.
[email protected]$o said:
I am not sure but i think that update for the uk didnt come out yet. so you can't update to lollipop yet via pc suite or ota. and you got it all wrong. first you flash lollipop kdz but you will have to try out few of them since official for uk didn't come out yet, after that you root, and then flash custom recovery.
and as previously you will be back to stock recovery after update. you have it all explained step by step in first post. i know it is a bit long but that is the best way, since i didn't want to write stuff like "you should know that" and so on. so just follow the first post and you will be happy, or wait for official uk update over the ota you will be happy too, and i guess it should come out in a month.
Click to expand...
Click to collapse
Thanks for the quick reply.
I'll download all the lollipop kdz's and see which one of them works for me till the UK one comes out then I'll just do a normal flash over it.
But seriously, one month for the UK ota :crying: Right now, I don't even know which is worse: Google that takes forever to release updates with so many bugs, or Apple who generally release better stable updates but make older devices laggy...
Thanks again for all the help.
seyio said:
Thanks for the quick reply.
I'll download all the lollipop kdz's and see which one of them works for me till the UK one comes out then I'll just do a normal flash over it.
But seriously, one month for the UK ota :crying: Right now, I don't even know which is worse: Google that takes forever to release updates with so many bugs, or Apple who generally release better stable updates but make older devices laggy...
Thanks again for all the help.
Click to expand...
Click to collapse
its a good update, not that buggy, and be sure to fully charge your battery before the process. you should try europe open or something like that, but there is no german or uk release yet and some guys suspect it is slowed down because they found out bugs in other versions
After CSE Flashing my d802 with a 30a, it got stock on lg logo screen, then an android screen with "erasing" on bottom, then lg screen. I let it sit for 4 hrs but nothing happened. Im back to stock kitkat atm. A little help please.
fernievidal said:
After CSE Flashing my d802 with a 30a, it got stock on lg logo screen, then an android screen with "erasing" on bottom, then lg screen. I let it sit for 4 hrs but nothing happened. Im back to stock kitkat atm. A little help please.
Click to expand...
Click to collapse
Where from is your phone? Are you sure you flashed right kdz? Did lollipop even turn off? DidCSE flashing finished sucessfully? I would like to help you, but i cant if you dont explainme what is your problem. I am not some pro who faced every error on every phoneso please explain a bit more
And i suppose that erasing screen could have been factory reset on stock recovery
[email protected]$o said:
Where from is your phone? Are you sure you flashed right kdz? Did lollipop even turn off? DidCSE flashing finished sucessfully? I would like to help you, but i cant if you dont explainme what is your problem. I am not some pro who faced every error on every phoneso please explain a bit more
And i suppose that erasing screen could have been factory reset on stock recovery
Click to expand...
Click to collapse
I believe mine is an international version. Where it came from, well, I'm from the Philippines and I got my phone from a local telecom, Globe.
The flash tool said that it was successfully upgraded, but judging from the phone's behavior I think there's something wrong. My phone never started successfully, and I got stuck in the LG logo.
Hello everyone!
I've been very happy with my rooted M9 for the last few months but now a system update message on my screen and I'm trying to figure out what to do about. I seem to recall when I rooted my phone that there could be complications if I install a system update on a rooted phone (like making a Nandroid Backup) but I'm finding scarce information on the topic. Does anyone here have some advice about this?
Rom...
http://forum.xda-developers.com/showthread.php?t=3083799
Firmware...
http://forum.xda-developers.com/showthread.php?t=3073355
Follow the second link above.
You will need to restore the factory system.img using TWRP (exFAT or NTFS for external USB as file is > 4GB).
This puts the modified system (root) back to stock so the update will run successfully.
Flash the original recovery for you system version too.
Then you can accept the OTA and then root the phone again.
Thanks for the responses! I'm still uncertain about a few things so tell me if I have this right.
First I need to restore the factory image. Is that a guy named OJM is talking about on this thread? (http://forum.xda-developers.com/sprint-one-m9/general/rooting-guide-t3073004)
To restore your clean system backup to accept OTAs, you must use fastboot. If you are S-ON, you must be in download mode.
-copy your clean system.emmc.win to your adb/fastboot folder on your pc
-boot into download mode
-use cmd fastboot flash system system.emmc.win
Click to expand...
Click to collapse
In that case, what is a system.emmc.win?
Then I flash the original recovery...what are you refering to when you say "original recovery"?
After that my phone should be locked again and I can go to that second link, download the latest firmware and flash it. And then I can unlock and root my phone again.
Edit: So it looks like someone has made a guide on how to get the OTA updates (if you use the right words in your search). It looks no one done anything with it since May so maybe it still works? http://forum.xda-developers.com/one-m9/general/best-unlocking-bootloader-rooting-guide-t3087354
I would just run the official RUU, it's a one shot process will take care of everything including the radios. Much easier than messing around, just make sure you are S-OFF before you do it. When it's done just flash the latest TWRP and install your rom you will be done.
Sim-X said:
I would just run the official RUU, it's a one shot process will take care of everything including the radios. Much easier than messing around, just make sure you are S-OFF before you do it. When it's done just flash the latest TWRP and install your rom you will be done.
Click to expand...
Click to collapse
That was what I ended up doing. Had few bumps on the way but I managed to get everything working. Thanks for the help everyone!
RUU
Sim-X said:
I would just run the official RUU, it's a one shot process will take care of everything including the radios. Much easier than messing around, just make sure you are S-OFF before you do it. When it's done just flash the latest TWRP and install your rom you will be done.
Click to expand...
Click to collapse
hi sim I have a question the only thing I got to make sure is that the phone is S-OFF and nothing will happen because I read that also the bootlooder had to be lock again so I'm not sure