Related
Someone please help!
I have a LG Optimus L7 P705g, on v10C stock rom, rooted according to http://forum.xda-developers.com/showthread.php?t=1906133
Then I tried to unlock bootloader and install cwm recovery following http://forum.xda-developers.com/showthread.php?t=1664322
I tried both v1 and v2 of the L7CWM archive. But the phone keeps rebooting about 2 minutes after power on.
No matter I boot normally, or boot into cwm recovery, it still restarts about 2 minutes in.
It's driving me crazy. Can somebody give me some pointer in how to resolve this constant reboot situation?
I believe I followed all the instructions provided with the above threads, and tried flashing both v1 and v2 a few times.
Thanks in advance!
ecapella said:
Someone please help!
I have a LG Optimus L7 P705g, on v10C stock rom, rooted according to http://forum.xda-developers.com/showthread.php?t=1906133
Then I tried to unlock bootloader and install cwm recovery following http://forum.xda-developers.com/showthread.php?t=1664322
I tried both v1 and v2 of the L7CWM archive. But the phone keeps rebooting about 2 minutes after power on.
No matter I boot normally, or boot into cwm recovery, it still restarts about 2 minutes in.
It's driving me crazy. Can somebody give me some pointer in how to resolve this constant reboot situation?
I believe I followed all the instructions provided with the above threads, and tried flashing both v1 and v2 a few times.
Thanks in advance!
Click to expand...
Click to collapse
ok, you need to do this.
First, follow this tutorial http://forum.xda-developers.com/showpost.php?p=31828740&postcount=1191 to flash the ROM from this post http://forum.xda-developers.com/showthread.php?t=2176430 this rom is already rooted, and includes CWM and unlocked bootloader, so you shouldn't have any problems to flash any other ROM after that one.
and second, you need to learn to search on the forum, and read more before asking already solved issues.
good luck
vashminted said:
ok, you need to do this.
First, follow this tutorial http://forum.xda-developers.com/showpost.php?p=31828740&postcount=1191 to flash the ROM from this post http://forum.xda-developers.com/showthread.php?t=2176430 this rom is already rooted, and includes CWM and unlocked bootloader, so you shouldn't have any problems to flash any other ROM after that one.
and second, you need to learn to search on the forum, and read more before asking already solved issues.
good luck
Click to expand...
Click to collapse
Thanks for your quick reply! Actually, I'm a little hesitant to use kdz updater, as I've read some posts saying that even after they flash the stock kdz, the phone was in an even worse situation.
Since I can still boot into cwm recovery (I have a 2-minute time frame before the phone restarts itself), should I do a wipe cache or something? Will it help?
Flashing the whole thing is my last resort.
ecapella said:
Thanks for your quick reply! Actually, I'm a little hesitant to use kdz updater, as I've read some posts saying that even after they flash the stock kdz, the phone was in an even worse situation.
Since I can still boot into cwm recovery (I have a 2-minute time frame before the phone restarts itself), should I do a wipe cache or something? Will it help?
Flashing the whole thing is my last resort.
Click to expand...
Click to collapse
yes, I've also read that some people have problems after flashin kdz....but i dont know why, KDZ flashing is usually the best way to make sure your phone is back to a "perfect" working state, since it restores everything to the way it should be, and in most situations is the only way to unbrick the phone.
I can't tell you how many times I had to use KDZ updater to restore my phone after messing with it, im not a developer but i do a lot of experiments with my phone trying to make it work better, and most of the times it end totally bricked, and every time KDZ updater saves my ass. Some time ago i was trying to modify the stock rom myself, and I used to flash via KDZ my phone at least twice a day....so for me is pretty safe to use
vashminted said:
yes, I've also read that some people have problems after flashin kdz....but i dont know why, KDZ flashing is usually the best way to make sure your phone is back to a "perfect" working state, since it restores everything to the way it should be, and in most situations is the only way to unbrick the phone.
I can't tell you how many times I had to use KDZ updater to restore my phone after messing with it, im not a developer but i do a lot of experiments with my phone trying to make it work better, and most of the times it end totally bricked, and every time KDZ updater saves my ass. Some time ago i was trying to modify the stock rom myself, and I used to flash via KDZ my phone at least twice a day....so for me is pretty safe to use
Click to expand...
Click to collapse
I tried to read as many posts as possible about using the L7CWM archive to unlock bootloader and CWM recovery before actually doing it. People with P700 and P705 both reported success. I don't know what I did wrong. I am so frustrated...
The ROM you pointed me to get is for P700, does it matter? (Mine is P705). Or should I use my stock rom kdz to test it out first?
Also the two links that you gave me have different phone mode setting in the KDZ updater, one set as EMERGENCY, the other one set as DIAG. Which one should I use?
Thanks again!
Hope there is an easier way than using the KDZ updater... :fingers-crossed:
ecapella said:
I tried to read as many posts as possible about using the L7CWM archive to unlock bootloader and CWM recovery before actually doing it. People with P700 and P705 both reported success. I don't know what I did wrong. I am so frustrated...
The ROM you pointed me to get is for P700, does it matter? (Mine is P705). Or should I use my stock rom kdz to test it out first?
Also the two links that you gave me have different phone mode setting in the KDZ updater, one set as EMERGENCY, the other one set as DIAG. Which one should I use?
Thanks again!
Hope there is an easier way than using the KDZ updater... :fingers-crossed:
Click to expand...
Click to collapse
yep, it's for P700, but other than NFC, there's no difference...i dont recomend to use that rom for every day because it will drain your battery because of the NFC. but since it comes already rooted and unlocked, its an excelent base to make sure everything is well installed, after that you should be able to enter into recovery without problems, and then you can flash a ROM for P705. Personally I suggest you to try this one http://forum.xda-developers.com/showthread.php?t=2472479 it's working very good for me, and have specific kernel to p705
Of course you can try with stock kdz for p705, but hen you will have to repeat the process with L7CWM and chances are that something goes wrong again.
And I gave you the link that use EMERGENCY because it is the way I use to flash a KDZ, you can try to follow tutorial with DIAG option, but I haven't test it myself, and I would never recommend something I haven't tested before. Also because you said your phone reboots every two minutes, and I think DIAG option needs the phone to be ON while flashing, in EMERGENCY option, the phone will never turn off untill you unplug the cable.
vashminted said:
yep, it's for P700, but other than NFC, there's no difference...i dont recomend to use that rom for every day because it will drain your battery because of the NFC. but since it comes already rooted and unlocked, its an excelent base to make sure everything is well installed, after that you should be able to enter into recovery without problems, and then you can flash a ROM for P705. Personally I suggest you to try this one http://forum.xda-developers.com/showthread.php?t=2472479 it's working very good for me, and have specific kernel to p705
Of course you can try with stock kdz for p705, but hen you will have to repeat the process with L7CWM and chances are that something goes wrong again.
And I gave you the link that use EMERGENCY because it is the way I use to flash a KDZ, you can try to follow tutorial with DIAG option, but I haven't test it myself, and I would never recommend something I haven't tested before. Also because you said your phone reboots every two minutes, and I think DIAG option needs the phone to be ON while flashing, in EMERGENCY option, the phone will never turn off untill you unplug the cable.
Click to expand...
Click to collapse
I read another post about flashing the Homero's v10K rooted KDZ that you mentioned into a North American P705, and that made the phone unbootable.
But fortunately, I managed to get a stock bootloader from a friend's North American P705 and push it into my phone. This did the trick, my phone didn't have the boot loop anymore.
Then, I upgraded the stock firmware to v20A via LG's mobile support tool. At this version (JB as opposed to ICS), I tried to push the cracked bootloader into the phone again. This time, everything was all right, no boot loop! So I flashed the CWM recovery, and everything was good.
I just tested out Szymel's modded stock rom v20E with OC 1305Mhz, seems pretty good!
Now I have a lot of ROM choices to test out. :laugh:
Anyway, thanks so much for your help and suggestions!
HELP
ecapella said:
I read another post about flashing the Homero's v10K rooted KDZ that you mentioned into a North American P705, and that made the phone unbootable.
But fortunately, I managed to get a stock bootloader from a friend's North American P705 and push it into my phone. This did the trick, my phone didn't have the boot loop anymore.
Then, I upgraded the stock firmware to v20A via LG's mobile support tool. At this version (JB as opposed to ICS), I tried to push the cracked bootloader into the phone again. This time, everything was all right, no boot loop! So I flashed the CWM recovery, and everything was good.
I just tested out Szymel's modded stock rom v20E with OC 1305Mhz, seems pretty good!
Now I have a lot of ROM choices to test out. :laugh:
Anyway, thanks so much for your help and suggestions!
Click to expand...
Click to collapse
i have the same problem with my l7 p705 i rooted it and then i installed CWM and then it started restarting every 2 minutes. so i thought maybe unrooting it would help but it didn't. please give me all the steps that you did so i can stop my phone from booting every 2 minutes.!!!
LG P705
My Phones says secure booting error Cause:boot certification verify i`m a newbie help me please ,
Lg Optimus L7 P705 Secure booting Error!
Hello everyone,
I'm from Turkey.
I have LG Optimus L7 P705.
My problem, to take root and Cyanogenmod. But phone is brick.
I have seen the error screen :
-Secure booting Error!
-Cause : boot certification verify
Help me !
Mail Adress 7/24 : [email protected]
I have LG G2 D802 32GB. When I bought it, there was Android 4.4.2 KitKat installed.
Then I rooted it using ioroot25 and installed custom recovery using AutoRec.
I flashed CloudyG3 v1.2 rom by @Cloudyfa using TWRP.
It was working really good except the VOIP calls, thus I wanted to revert back to stock.
I found this guide: http://forum.xda-developers.com/showthread.php?t=2432476
I tried to flash it using some Europe Open KDZ from this page: http://storagecow.eu/index.php?dir=Xda%2FLG+G2%2FStock%2F
The flashing started and stucked at I think 4%. I rebooted the phone and it appeared as qhsusb_dload.
I can't remember if I clicked on Normal or CFE flash. But I think it was normal.
I tried to unbrick it with this guide: http://forum.xda-developers.com/showthread.php?t=2582142
After that I got only LG logo and no recovery, no fastboot, no download mode, no qhsusb_dload mode, no nothing.
Now I got board replacement. The board have rooted Android 4.2.2 Jelly Bean installed.
As I want to have CloudyG3 installed. I tried to do that by installing custom recovery and then flashing the CloudyG3 rom and KitKat baseband. But I think I have a battery drain issue, as Cludyfa already said. I also tried with flashing the Cust and Persist partitions from the KitKat KDZ, but my battery didn't got any better.
The question is, why I bricked my phone with LG flash tool? What should I do to make sure that this won't happen again?
I made backup of entire phone nand (mmcblk0). Should I DD it if I get the bulk mode (qhsusb_dload) again?
Thank you in advance for your answers.
@mss1988 if the phone is stuck at 4% just let it still for some time cause the program could might be bugged or some other error, just leave the phone on dont restart it cause the phone has first removed the stuff and didnt copied the bootloader etc yet.
If you get qhsusb_dload mode then I suggest to use the unbrick guide and also Pick the right files for your phone. You can DD your backup to your phone but using the unbrick guide seems safer to me.
Also check when you can use that qhsusb dload that all files are copied good.
Tip to prevent brick after root and custom recovery: Flash an stock rom through recovery or an stock rom which got modified under the hood.
wulsic said:
@mss1988 if the phone is stuck at 4% just let it still for some time cause the program could might be bugged or some other error, just leave the phone on dont restart it cause the phone has first removed the stuff and didnt copied the bootloader etc yet.
If you get qhsusb_dload mode then I suggest to use the unbrick guide and also Pick the right files for your phone. You can DD your backup to your phone but using the unbrick guide seems safer to me.
Also check when you can use that qhsusb dload that all files are copied good.
Tip to prevent brick after root and custom recovery: Flash an stock rom through recovery or an stock rom which got modified under the hood.
Click to expand...
Click to collapse
When phone stucked there was also some message box on LG Flash Tool. Something like that: ?????? ??? ????????.
Sent from my LG-D802 using XDA Free mobile app
Broken usb cable or port? Problems on pc?
siggey said:
Broken usb cable or port? Problems on pc?
Click to expand...
Click to collapse
As far as I know none of that.
Sent from my LG-D802 using XDA Free mobile app
That something like ????? Was probably in some asian language which your pc couldnt read. Some pc's makes boxes from it some ?. I cant tell you what that ???? Means since they have no meaning without any real symbols from some language of asia (I dont know where the dev comes from)
If it was stuck at 4% you could ask it on the thread of the lg flashtool since the dev of it and or other users may know the problem.
mss1988 said:
What should I do to make sure that this won't happen again?
Click to expand...
Click to collapse
Read the tutorial in detail & HAVE some patience man.
I had a rooted LG G2 D802 on EE with KK update that was working fine until today...
I tried to flash a nice custom rom to it and well, to cut a long story short something went wrong and the next thing i know i have a phone which only shows up as about 10 hdd's in windows, and as QHSUSB_BULK in device manager.
I couldn't get it to go into download mode or anything, so i followed the Unbricking guide here:
http://forum.xda-developers.com/showthread.php?t=2582142
Unfortunately this appeared to do nothing for the phone, so i used the Tung Lee guide and this also did nothing.
After i did the above guide the phone was no longer recognised in windows or Linux, but thanks to this post:
http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
I was able to at least get it back to the state it was in in the first place.
After following all these guides i am now at a loss as to how to sort my phone out,and i'm hoping someone here can point me in the right direction for a fix..
When the phone was working, i put the imei into the firmware engine and it found me the D80220H firmware, i have tried using the bin files from the first guide and from D80220B as well with no luck, so i was wondering if one of the above guides do indeed work, how can i get the .img files i need from a D80220H KDZ?
Its been a long night and i'm now currently without my phone, i'm hoping someone can help and i can get my beloved G2 back to a working state before the weekend.
Thanks in advance, and sorry for the long post.
Tony
Have you simply tried the LG Flash Tool? When it happened to me once, i simply reg
Flashed kdz using this tool and voila!!! Try and report
@Shadowhunta Are you using the twrp IMG from that first guide? That might explain why this isnt working. Extract the kdz using this tool
Flash the aboot, boot and laf then try download mode.
wisefreakz said:
Have you simply tried the LG Flash Tool? When it happened to me once, i simply reg
Flashed kdz using this tool and voila!!! Try and report
Click to expand...
Click to collapse
Gonna try this during my lunchbreak today!
Art Vanderlay said:
@Shadowhunta Are you using the twrp IMG from that first guide? That might explain why this isnt working. Extract the kdz using this tool
Flash the aboot, boot and laf then try download mode.
Click to expand...
Click to collapse
I was using the TWRP from that post, but then i downloaded the latest one and that didn't make any difference, I haven't tried that tool properly yet to get the .img files needed from the KDZ i have for D80220H, but i have flashed the aboot, boot and laf of D80220B and that didn't help either, i couldn't get it into recovery mode, download mode or anything! With the first tutorial i managed to get it into Hard reset mode, but it just hung on processing.
Thanks for the suggestions, i will try them during lunch and get back to you both, thank you so far!
Anyone else had the same problem as me, keep the suggestions coming, all are helpful and appreciated
wisefreakz said:
Have you simply tried the LG Flash Tool? When it happened to me once, i simply reg
Flashed kdz using this tool and voila!!! Try and report
Click to expand...
Click to collapse
Tried this, no dice
Flash tool keeps telling me my phone is disconnected even though its seen as QHSUSB_BULK and as about 10 local disks in disk manager lol
Shadowhunta said:
Tried this, no dice
Flash tool keeps telling me my phone is disconnected even though its seen as QHSUSB_BULK and as about 10 local disks in disk manager lol
Click to expand...
Click to collapse
follow this tutorial... same problem as yours https://www.youtube.com/watch?v=_d5b_osUTug
wisefreakz said:
follow this tutorial... same problem as yours
Click to expand...
Click to collapse
Followed that, still nothing, won't boot into recovery mode, only thing it does is show in windows as a load of local disks, and QHSUSB_BULK in device manager with a yellow exclamation mark
I've followed all the advice so far given and none of it worked, i think i'm screwed :/
Art Vanderlay said:
@Shadowhunta Are you using the twrp IMG from that first guide? That might explain why this isnt working. Extract the kdz using this tool
Flash the aboot, boot and laf then try download mode.
Click to expand...
Click to collapse
Tried this too, nothing, it won't go into download mode.
I have the same problem, please do tell me if any of you find a solution.
I am seriously stuck
What model you guys have?
wisefreakz said:
What model you guys have?
Click to expand...
Click to collapse
I have D802.
Switched999 said:
I have D802.
Click to expand...
Click to collapse
Same, D802.
I phoned LG on saturday and have decided to send it in for repair, i only need it to keep me going till November then i can get the G4.
Well LG have tajen their sweet time, i won't be getting the envelope to send it back in until monday.
Soooo if i can get this fixed before then i would be very happy!
Does anyone else have any ideas please?
Hello,
I have a LG G2 (D802). I was busy flashing the stock KDZ, when I got an error. The progress on my phone stopped, and nothing happened anymore. I wanted to try again, so I turned my phone off. Now, when I boot my phone, it gives the LG logo, and then nothing. When I connect it to my pc, I get a lot of format pop-ups.
I followed this tutorial: http://forum.xda-developers.com/showthread.php?t=2432476
The KDZ I used: Netherlands Open 16GB KitKat D80220D
Furthermore, also while connected to the pc, I only see a folder called "image".
Can someone help me with getting my phone back to stock? It doesn't matter if everything gets wiped, I already backed up everything.
Thanks in advance!
If lots of drives still pop up when you connect your phone to the PC,then follow this guide:https://www.youtube.com/watch?v=hQVTc2m6U-I
I did it,and it fixed my download mode,and I could finally access Download Mode.
If your Download Mode still works,try the TOT method,it worked for me,since the KDZ method would be stuck at 2% every time(in my case).
So,after,or if your download mode works,do try the TOT method.
The Marionette said:
If lots of drives still pop up when you connect your phone to the PC,then follow this guide:https://www.youtube.com/watch?v=hQVTc2m6U-I
I did it,and it fixed my download mode,and I could finally access Download Mode.
If your Download Mode still works,try the TOT method,it worked for me,since the KDZ method would be stuck at 2% every time(in my case).
So,after,or if your download mode works,do try the TOT method.
Click to expand...
Click to collapse
Thanks for your reply, but unfortunately, I even can't get the phone into fastboot mode.
Here are some pictures to show what's inside the "image" folder in the first local disk (= first partition?): 1: http://i.imgur.com/InFoiXA.png 2: http://i.imgur.com/YzjXOmQ.png 3: http://i.imgur.com/JDEnUfa.png
MistaahD said:
Thanks for your reply, but unfortunately, I even can't get the phone into fastboot mode.
Here are some pictures to show what's inside the "image" folder in the first local disk (= first partition?): 1: http://i.imgur.com/InFoiXA.png 2: http://i.imgur.com/YzjXOmQ.png 3: http://i.imgur.com/JDEnUfa.png
Click to expand...
Click to collapse
So you basically cant access the recovery,fastboot nor the Download Mode,right?
Try asking for help on this thread:http://forum.xda-developers.com/showthread.php?t=2432476
People there really know how to help,they helped me there too
Just dont panic,even if your phone is in a "hard brick" state(doubtfully),there is a fix for it too.
I suggest you do not do anything without consulting with other members.
You just have to be patient.
EDIT
Oh,and go to the Device Manager and tell me what name your G2 has when connected to the PC.
The Marionette said:
So you basically cant access the recovery,fastboot nor the Download Mode,right?
Try asking for help on this thread:http://forum.xda-developers.com/showthread.php?t=2432476
People there really know how to help,they helped me there too
Just dont panic,even if your phone is in a "hard brick" state(doubtfully),there is a fix for it too.
I suggest you do not do anything without consulting with other members.
You just have to be patient.
EDIT
Oh,and go to the Device Manager and tell me what name your G2 has when connected to the PC.
Click to expand...
Click to collapse
Indeed, there's really no mode that I can use...
Thanks, I'll ask for help there too! And my phone is being recognized as "QHSUSB_BULK".
MistaahD said:
Indeed, there's really no mode that I can use...
Thanks, I'll ask for help there too! And my phone is being recognized as "QHSUSB_BULK".
Click to expand...
Click to collapse
Hmm,QHSUSB_BULK and no drives popping out?
EDIT
And are you sure you have the LG USB Drivers installed?
EDIT#2
And did you try to install the drivers to another PC and connecting your phone to that PC?
The Marionette said:
Hmm,QHSUSB_BULK and no drives popping out?
EDIT
And are you sure you have the LG USB Drivers installed?
EDIT#2
And did you try to install the drivers to another PC and connecting your phone to that PC?
Click to expand...
Click to collapse
Yep, drivers are installed.
And there are also a lot of drives popping out! See this screenshot: http://i.imgur.com/RcMrAYv.png
Edit: I will try connecting it to another pc now.
MistaahD said:
Yep, drivers are installed.
And there are also a lot of drives popping out! See this screenshot: http://i.imgur.com/RcMrAYv.png
Click to expand...
Click to collapse
Ugh thank god
those drives SHOULD be popping out
Right click on My Computer and select "Manage"
Then,on the left part of that window,you will see the "Disk Management" option. Click it
Then,you should see a certain Disk which is separated into tons of parts.
This part is crucial!
To me,my PCs Hard Drive was "Disk 0",and my fastboot G2 was "Disk 1"
Please tell me which "Disk _" your g2 is.
You can folow this videowithout my help(I could do it by myself in 3 A.M.,so you can do it too! ),I am basically helping you with the same method.
If you want me to proceed with helping you,do tell.
The Marionette said:
Ugh thank god
those drives SHOULD be popping out
Right click on My Computer and select "Manage"
Then,on the left part of that window,you will see the "Disk Management" option. Click it
Then,you should see a certain Disk which is separated into tons of parts.
This part is crucial!
To me,my PCs Hard Drive was "Disk 0",and my fastboot G2 was "Disk 1"
Please tell me which "Disk _" your g2 is.
You can folow this videowithout my help(I could do it by myself in 3 A.M.,so you can do it too! ),I am basically helping you with the same method.
If you want me to proceed with helping you,do tell.
Click to expand...
Click to collapse
My phone is on Disk2. I am now trying to follow this guide, I'll let you know how it worked out.
Edit: wow! I now get the firmware update screen!! What should I do now? What to flash?
MistaahD said:
My phone is on Disk2. I am now trying to follow this guide, I'll let you know how it worked out.
Edit: wow! I now get the firmware update screen!! What should I do now? What to flash?
Click to expand...
Click to collapse
Download the kdz suitable for your model and flash it with LG Flash Tool.
Follow the "Back to stock" guide which you mentioned in the OP.
There will be a link to the KDZ archive for various models,and make sure that you select the kdz for the 32 GB variant if you have a 32 GB variant. Because it will be dangerous if you flash a 16gb variant kdz on a 32 gb phone.
Sent from my LG-D802 using XDA Forums Pro.
EDIT
And if the same thing happens when flashing,fix it again(if it won't access the download mode) and try to flash while using another PC.
Mate, you are the freakin' best!!!! Mah phone works again!!! Now I'm going to install CloudyG2_3.3. What are the steps I need to perform in order to NOT(!!!) brick my phone again?
That'll be my last question, I can't thank you enough!
MistaahD said:
Mate, you are the freakin' best!!!! Mah phone works again!!! Now I'm going to install CloudyG2_3.3. What are the steps I need to perform in order to NOT(!!!) brick my phone again?
That'll be my last question, I can't thank you enough!
Click to expand...
Click to collapse
So the kdz flash worked,and the stock rom boots?
Sent from my LG-D802 using XDA Forums Pro.
Yea it works! I used the stock KK rom though, since Cloudy requires the KK bootloader. I did it right here yes?
MistaahD said:
Yea it works! I used the stock KK rom though, since Cloudy requires the KK bootloader. I did it right here yes?
Click to expand...
Click to collapse
Yes,excellent job.
To root,download "Towelroot" to your phone,install it and press the "Make it rain" button,then install SuperSU,then look for "AutoRec" and make sure you get the version for your variant.
That is just halfway,I will tell you the rest tomorrow,it is 00:26 and I have to get up at 07:00. xD
Sent from my LG-D802 using XDA Forums Pro.
Haha cheers! I think I got it from there, it's just that I don't want to do it in a wrong order haha ;P
And thanks a lot, again! Get your deserved sleep, I should do that too.. Gotta go up at 06:45 hah!! I WIN! xD
Okay,moving on.
Download the BUMPED TWRP from this thread:http://forum.xda-developers.com/lg-g2/development/twrp-twrp-2-8-0-0-kernel-f2fs-tools-t2898705
It is in a flashable zip,so just flash it with the TWRP which was installed by AutoRec.
You must have the bumped version of TWRP!!
After you flashed the BUMP TWRP,reboot recovery.
Here is a bootloader changer,AROMA edition:http://forum.xda-developers.com/lg-g2/general/d802-bootloader-changer-1-1-jb-kk-lp-t3104380
1.Wipe data/factory reset
2.Flash the Bootloader Changer,in AROMA choose the KK bootloader,and install.
3.Flash CloudyG2 3.3
4.Reboot
The Marionette said:
Okay,moving on.
Download the BUMPED TWRP from this thread:http://forum.xda-developers.com/lg-g2/development/twrp-twrp-2-8-0-0-kernel-f2fs-tools-t2898705
It is in a flashable zip,so just flash it with the TWRP which was installed by AutoRec.
You must have the bumped version of TWRP!!
After you flashed the BUMP TWRP,reboot recovery.
Here is a bootloader changer,AROMA edition:http://forum.xda-developers.com/lg-g2/general/d802-bootloader-changer-1-1-jb-kk-lp-t3104380
1.Wipe data/factory reset
2.Flash the Bootloader Changer,in AROMA choose the KK bootloader,and install.
3.Flash CloudyG2 3.3
4.Reboot
Click to expand...
Click to collapse
Hey man,
I noticed that Towelroot doesn't work for LG G2 Lollipop. Any idea how to fix this?
Edit: trying it with another root.
Edit 2: rooted. Going to flash now.
Alright it works, thanks! Can you tell me why I need the bumped version? Just curious
MistaahD said:
Alright it works, thanks! Can you tell me why I need the bumped version? Just curious
Click to expand...
Click to collapse
It is complicated,just do it. XD
I was asking the same thing like you.I ignored others,rushed with roms,didnt use the BUMPED TWRP and my phone was bricked.
Basically the TWRP you get with AutoRec is just capable of flashing partitions for the bootloader,not the system partition(the rom is in the system partition).
The BUMPED TWRP has a certain type of an exploit,and lets us install those system partitions.
Shortly:You can't install roms without the BUMPED TWRP.
Sent from my LG-D802 using XDA Forums Pro.
I'm guessing my phone is refurbished?
I bought a D802 from a third-party, with:
- 32GB ROM
- 4.4.2 D80220b firmware
- 2G, 3G, 4G working
- The csmg.lgmobile.com website said that according to my IMEI, my model is the UAE 32GB D802 and gave me the D80230a firmware for manual flash via LG Flash tool.
I used the phone for a while, rooted it and used Xposed. Never got recovery so no backup(wish I'd seen the SRK tool before). Then I downloaded the firmware from the csmg.lgmobile.com website. I flashed it via the Flash tool and everything seemed fine. Then it booted:
- Touchscreen was erratic. Ghost touches, dead spots, phantom touches, whatever.
- The Baseband Version and IMEI in About Phone both say Unknown
- ROM has converted to a 16GB version
- Download mode is fine along with every other feature of the phone
After that I looked around and found a UAE D80220c firmware and flashed that. It flashed fine but all the above issues remained the same.
I browsed around extensively here and found out:
- Refurbished phones have their back cover and firmware changed to imitate D802's.
- My phone is probably some other G2 model with D802 firmware and an altered IMEI
- The actual model of my device is UNDER the motherboard. Which, apparently, I must get hold of so I can flash the appropriate stock kdz. This gets a bit too hardware-y for me.
So, basically, my phone is no more useful than a brick at the moment. Any expert help would be appreciated but here are the main questions that I'd really like answered:
A. Should I try various flashing the kdz files from different models mentioned in the link I gave up ^there until one clicks and then try to do something about the IMEI?
B. Is there any chance that my phone is beyond repair forever?
C. Should I stop messing around with my mediocre knowledge and take it to a repair shop?
hi
i just flash the Android N Preview it worked normaly then i flash TWRP through Temporary Recovery then i reboot and BAM . Nothing there.
Black display , no bootloader,nothing
just when pluging the device it showed qhsusb_Bulk Driver on Windows
Any Help ?
and if i send it back to google does it cover the Warranty?
Google probably won't do anything for you as you installed it at your own risk
mustafa alzubaidy said:
hi
i just flash the Android N Preview it worked normaly then i flash TWRP through Temporary Recovery then i reboot and BAM . Nothing there.
Black display , no bootloader,nothing
just when pluging the device it showed qhsusb_Bulk Driver on Windows
Any Help ?
and if i send it back to google does it cover the Warranty?
Click to expand...
Click to collapse
No it won't be covered by warranty. What do you mean you flashed TWRP through temporary recovery? Exactly what TWRP did you flash? The filename please.
Good news: your phone is not dead. I've had this issue once with my OnePlus One and I was able to get if fixed.
Bad news: process was a little bit harder than standard flashing, unlocking, etc. stuffs.
Heisenberg said:
No it won't be covered by warranty. What do you mean you flashed TWRP through temporary recovery? Exactly what TWRP did you flash? The filename please.
Click to expand...
Click to collapse
i use the NRT toolKit to flash TWRP (it provide temporary Recovery to flash any zip then it goes back to stock , i did this earlier its not the cause) it boot the recovery and i flashed this file :
twrp-3.0.0.0-s2vep-20160208 (then i realized it is the wrong file in the wrong folder)
after that i reboot the device and got bricked.
anmar21 said:
Good news: your phone is not dead. I've had this issue once with my OnePlus One and I was able to get if fixed.
Bad news: process was a little bit harder than standard flashing, unlocking, etc. stuffs.
Click to expand...
Click to collapse
ok can you give me a link or something ? i am a techy guy and can learn easily.(hopefully)
mustafa alzubaidy said:
i use the NRT toolKit to flash TWRP (it provide temporary Recovery to flash any zip then it goes back to stock , i did this earlier its not the cause) it boot the recovery and i flashed this file :
twrp-3.0.0.0-s2vep-20160208 (then i realized it is the wrong file in the wrong folder)
after that i reboot the device and got bricked.
Click to expand...
Click to collapse
Yeah, wrong recovery, big mistake.
mustafa alzubaidy said:
ok can you give me a link or something ? i am a techy guy and can learn easily.(hopefully)
Click to expand...
Click to collapse
You need special Qualcomm tools to recover, I haven't seen such a tool for this device yet though.
Heisenberg said:
Yeah, wrong recovery, big mistake.
You need special Qualcomm tools to recover, I haven't seen such a tool for this device yet though.
Click to expand...
Click to collapse
i search the net i found that for lG G2 , LG G3
any idea
how much time should i wait if such a tool appears?
thanks for you help
mustafa alzubaidy said:
i search the net i found that for lG G2 , LG G3
any idea
how much time should i wait if such a tool appears?
thanks for you help
Click to expand...
Click to collapse
It's impossible to say if or when it might become available.
@Heisenberg
Flashing the wrong recovery should have corrupted( or affected ) only the recovery partition, shouldn't it. From the description the OP has given it looks like the bootloader is corrupt, which is kind of weird
Have you seen this kind of problem on any other device ( coming from a moto g to n6p I thought the bootloader corruption things were over for me , but after reading this thread I am little terrified )
sjandroiddeveloper said:
@Heisenberg
Flashing the wrong recovery should have corrupted( or affected ) only the recovery partition, shouldn't it. From the description the OP has given it looks like the bootloader is corrupt, which is kind of weird
Have you seen this kind of problem on any other device ( coming from a moto g to n6p I thought the bootloader corruption things were over for me , but after reading this thread I am little terrified )
Click to expand...
Click to collapse
It corrupts the partition table which affects the other partitions.
mustafa alzubaidy said:
ok can you give me a link or something ? i am a techy guy and can learn easily.(hopefully)
Click to expand...
Click to collapse
For my OPO I used a tool and as @Heinsenberg mentioned I've never seen such a tool for the 6P yet. RMA would be the best solution, just say your not able to turn your phone on (which is true) .
sjandroiddeveloper said:
@Heisenberg
Flashing the wrong recovery should have corrupted( or affected ) only the recovery partition, shouldn't it. From the description the OP has given it looks like the bootloader is corrupt, which is kind of weird
Have you seen this kind of problem on any other device ( coming from a moto g to n6p I thought the bootloader corruption things were over for me , but after reading this thread I am little terrified )
Click to expand...
Click to collapse
me too!
i have flashed many rom with many devices , i even flashed a rom by enterning a download rom on a black screen and it worked!
but flashing wrong recovery i dont think it will cause such brick
FYI when i connect it to the PC it is recognized and when i contiously press the power buttuon it re-connected to the pc
If he really sends the device in and Google finds out HOW exactly the phone died, he might face severe consequences. It´s dishonest after all.
If you flash the wrong recovery for a different device, it´s your own bad luck. Now here´s the deal, you can still repair the device if a) Huawei would fix it or b) find a phone shop which could replace the motherboard. Once the Bootloader is bricked, there´s barely anything a regular user could do except for some complicated methods which require the knowledge and the special tools which most people don´t have.
anmar21 said:
For my OPO I used a tool and as @Heinsenberg mentioned I've never seen such a tool for the 6P yet. RMA would be the best solution, just say your not able to turn your phone on (which is true) .
Click to expand...
Click to collapse
mustafa alzubaidy said:
me too!
i have flashed many rom with many devices , i even flashed a rom by enterning a download rom on a black screen and it worked!
but flashing wrong recovery i dont think it will cause such brick
FYI when i connect it to the PC it is recognized and when i contiously press the power buttuon it re-connected to the pc
Click to expand...
Click to collapse
Flashing the wrong recovery can and does cause such a brick, this is what you're experiencing. I've seen it happen on many devices, it borks the partition table.
mustafa alzubaidy said:
but flashing wrong recovery i dont think it will cause such brick
Click to expand...
Click to collapse
You can tell yourself this all day long, but the phone that is in your hands that is now a doorstop, is proof otherwise.
Very crappy situation, but this is why toolkits stink, and why you need to be VERY careful when you mess w the device.