So I bougjt an LG G2 (international - D802) and I f***ed it up a bit.... Sadly it can not be fixed for some reason. It is stuck in fast boot mode, and I can not boot into recovery or download mode.... So I bought another LG G2 but this time an verizon. (32gb) And I'm planning on combining the 2 together because the verizon has an cracked screen and an not reacting touchscreen.So I want to replace the verizon's screen with an international one. So is there something I need to know? I just really want my g2 to work again..... It has been broken for about 3 months now....
Please help, because I don't want to break another g2
That isn't so nice that you couldnt use it for 3 months. I dont know what you should watch on since so far as i know only that there are 2 display variants lgd/jdi but there isnt an different digitizer on the phone so far as i know. The only thing that would be maybe is that the verizon logo is missing on the front if the original had one. To be sure that there aren't differences google about it and google the displays and see if you can see a difference on the display's. With that i mean differences with the cables, the parts on the digitizer/display and the pcb(greenish thing most time where the parts are on. I can't really find it out for you since i need to sleep now because its 3:02 AM, I hope that i helped you and that you can fix your problem. If i will remember it then i will make an research on it and i will post it here if you couldnt find if its possible or not. ?
wulsic said:
That isn't so nice that you couldnt use it for 3 months. I dont know what you should watch on since so far as i know only that there are 2 display variants lgd/jdi but there isnt an different digitizer on the phone so far as i know. The only thing that would be maybe is that the verizon logo is missing on the front if the original had one. To be sure that there aren't differences google about it and google the displays and see if you can see a difference on the display's. With that i mean differences with the cables, the parts on the digitizer/display and the pcb(greenish thing most time where the parts are on. I can't really find it out for you since i need to sleep now because its 3:02 AM, I hope that i helped you and that you can fix your problem. If i will remember it then i will make an research on it and i will post it here if you couldnt find if its possible or not. ?
Click to expand...
Click to collapse
Yeah, I had already googled it and I didn't found any weird corners or parts at the display that could be a problem. And I actually don't like the verizon logo at the front haha.
I will keep you posted if it works or not! Hope you had a good night rest =p
FritsPikee said:
Yeah, I had already googled it and I didn't found any weird corners or parts at the display that could be a problem. And I actually don't like the verizon logo at the front haha.
I will keep you posted if it works or not! Hope you had a good night rest =p
Click to expand...
Click to collapse
Ahh alright but i don't think its compatible those two models with the display sorry for late reaction since I can't really see where i replied before easy on desktop and thanks yes i had a good night rest till i woke up...
Compare the 2 Pictures you can also magnify it, the only difference i saw was in the small cable up in the pictures so far as i know that part is for the touchscreen to control the above half i believe. So the only difference between these 2 are the touchscreen i think, you can open and try it but i don't think it will work. Maybe you can describe more about your fastboot problem and we could fix your device?
http://www.etradesupply.com/lg-g2-vs980-lcd-screen-and-digitizer-assembly.html
http://www.etradesupply.com/lg-g2-d802-lcd-screen-and-digitizer-assembly-black-22089.html
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
@FritsPikee try these things to get out of fastboot mode:
The first one which is also suggested by me post #132:http://forum.xda-developers.com/showthread.php?t=2680150&page=14
Btw, Download the stock img files from here if you have d802: http://downloads.codefi.re/autoprime/LG/LG_G2/D802/Stock_Firmware
Just execute all those things but i think that you can use TWRP instead of the original recovery or some other kind of recovery But i am not sure
so do that recovery thing at your own risk :/
or if that doesn't work try this one but its not really well explained.: see fix 4: http://forum.xda-developers.com/showthread.php?t=2694530
If you have some other fastboot mode problem then reply again to this thread or add me on Facebook:Wulsic then i can also help you maybe with it.
wulsic said:
Ahh alright but i don't think its compatible those two models with the display sorry for late reaction since I can't really see where i replied before easy on desktop and thanks yes i had a good night rest till i woke up...
Compare the 2 Pictures you can also magnify it, the only difference i saw was in the small cable up in the pictures so far as i know that part is for the touchscreen to control the above half i believe. So the only difference between these 2 are the touchscreen i think, you can open and try it but i don't think it will work. Maybe you can describe more about your fastboot problem and we could fix your device?
http://www.etradesupply.com/lg-g2-vs980-lcd-screen-and-digitizer-assembly.html
http://www.etradesupply.com/lg-g2-d802-lcd-screen-and-digitizer-assembly-black-22089.html
@FritsPikee try these things to get out of fastboot mode:
The first one which is also suggested by me post #132:http://forum.xda-developers.com/showthread.php?t=2680150&page=14
Btw, Download the stock img files from here if you have d802: http://downloads.codefi.re/autoprime/LG/LG_G2/D802/Stock_Firmware
Just execute all those things but i think that you can use TWRP instead of the original recovery or some other kind of recovery But i am not sure
so do that recovery thing at your own risk :/
or if that doesn't work try this one but its not really well explained.: see fix 4: http://forum.xda-developers.com/showthread.php?t=2694530
If you have some other fastboot mode problem then reply again to this thread or add me on Facebook:Wulsic then i can also help you maybe with it.
Click to expand...
Click to collapse
Sorry for the late reaction, but this is what happend;
I wanted to backup my whole system just in case something would go wrong. So I installed cwm and when I booted my phone in recovery mode it was giving me a 'secure boot error'. But I accidently made a backup with the cwm error (I thought it was still the original recovery but it wasn't) then iI installed twrp 2.7 for lg g2 and that worked just great =). I made my backup. But then there was an software update from android (not google play) so I clicked on the 'install update notification' and my phone turned of and back on. but it booted in twrp instead of the original recovery (duh!) I looked it up on internet and found a command line I had to fill in in the twrp menu (something with 'dd if=/' etc). that fixed the problem but still the update wasn't installed. So I installed my old recovery back (the backup I made but what wasn't the original recovery. I installed the cwm 'secure boot error" recovery back). After I click again on the 'install update notification' my phone went in a bootloop with the 'secure boot error'
then I followed the Instructions in this tread: http://forum.xda-developers.com/showthread.php?t=2582142 And I got it out of the secure boot error thingy, but than it got in the fastboot boot loop =( And that's the whole story ...
i hope you can go something with it! Again, sorry for the late reaction!
You mean lg logo then fastboot? If so then the kernel isnt good. And you gotta replace it :/
wulsic said:
You mean lg logo then fastboot? If so then the kernel isnt good. And you gotta replace it :/
Click to expand...
Click to collapse
Yeah, first the logo and then fastboot, and i tried this tread: http://forum.xda-developers.com/showthread.php?t=2477595
But it didn't worked =( (btw I live in the netherlands to!!)
@FritsPikee ahh okay, maybe its easier if we talk with facebook or something like that my facebook is facebook.com/wulsic1, skype hangouts etc is just wulsic because facebook got bugged when i changed my username.
Because if i will talk dutch to you then it is easier and english is the language you must speak here at xda so yeah. Do you still have custom recovery or is that also gone?
wulsic said:
@FritsPikee ahh okay, maybe its easier if we talk with facebook or something like that my facebook is facebook.com/wulsic1, skype hangouts etc is just wulsic because facebook got bugged when i changed my username.
Because if i will talk dutch to you then it is easier and english is the language you must speak here at xda so yeah. Do you still have custom recovery or is that also gone?
Click to expand...
Click to collapse
I've send you an skype request! But I need to go now, so I'll be back in about 2 hours
@FritsPikee alright i will try to help you then if i dont have to eat then.
Related
Download and Install LG United Mobile Driver
Download and Install LG Mobile Support Tool
Boot your phone into download mode:
Put your G2 into download mode by switching it off, hold the Volume up button and insert the usb cable into the phone; wait for the drivers to finish loading if doing it for the first time.
Start the LG Mobile Support Tool and click on Options -> Upgrade Recovery
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It should now download the firmware (about 2gb) and flash it - this may take some time.
This is needed if you stuck in a bootloop after the flash is done:
Factory reset (this wipe your data and sdcard):
1. Turn the phone off.
2. Press and hold the Power and Volume down button.
3. When the LG logo pops up let go for a second and press the combo again.
4. You'll be prompted to press the Power button 3 times to wipe the device.
I would hate to have to use this, but wow what a good find. Thanks for contributing.
Sent from my LG-D800 using Tapatalk 4
Just got my g2. About to root install twrp etc. This is exactly what I was looking for. Thanks for posting.
Sent from my LG-D801 using XDA Premium 4 mobile app
For anyone putting in dashes with the imei number, dont it wont work with em.
Just wanted to notify that this method made my 32gb D802 a 16 gb one!
karstensson said:
Just wanted to notify that this method made my 32gb D802 a 16 gb one!
Click to expand...
Click to collapse
I used this method last night and it didnt mess with the storage at all. They don't even have a 16gb G2 so who knows. Also are you sure you are not mistaken cause this method doesnt wipe data.
x714x said:
I used this method last night and it didnt mess with the storage at all. They don't even have a 16gb G2 so who knows. Also are you sure you are not mistaken cause this method doesnt wipe data.
Click to expand...
Click to collapse
I know it does'nt wipe data, but it reflashes recovery, and in my case something went wrong. But Lg DO sell D802 as a 16 gb model!
Can anyone using this method please post results. Just wondering if there is more success with this method as opposed to the other method. Thanks.
Saved my bacon today!
karstensson said:
Just wanted to notify that this method made my 32gb D802 a 16 gb one!
Click to expand...
Click to collapse
I don't understand how could this be, you downloaded the specific firmware for your device (using your serial number)...
Can't you just try to flash it again ?
Noam23 said:
I don't understand how could this be, you downloaded the specific firmware for your device (using your serial number)...
Can't you just try to flash it again ?
Click to expand...
Click to collapse
I have reflashed it 5 times The problem was that it asked for some kind of password the first time (not the pin). So I did a factory reset. Now even TWRP says that my storage is 10.66 gb :/
karstensson said:
I have reflashed it 5 times The problem was that it asked for some kind of password the first time (not the pin). So I did a factory reset. Now even TWRP says that my storage is 10.66 gb :/
Click to expand...
Click to collapse
Which password exactly ? when ? in the process of flashing ? the OP mentions no stage in which you need to give password...
What are you going to do now ? your device is not rooted, so you can replace it under warranty, no ?
Noam23 said:
Which password exactly ? when ? in the process of flashing ? the OP mentions no stage in which you need to give password...
What are you going to do now ? your device is not rooted, so you can replace it under warranty, no ?
Click to expand...
Click to collapse
It did not say what the password was for, just asked for it. It came up after the phone had booted, but before i could see the lockscreen. I will wait a couple of weeks, to check if someone else gets the same problem, or if it is fixable. Otherwise i will hand it in on the warranty since there are not traces of root.
karstensson said:
It did not say what the password was for, just asked for it. It came up after the phone had booted, but before i could see the lockscreen. I will wait a couple of weeks, to check if someone else gets the same problem, or if it is fixable. Otherwise i will hand it in on the warranty since there are not traces of root.
Click to expand...
Click to collapse
Why should a password appear at that stage ???
If you went through all of the flash process successfully, booted successfully and only then did a factory reset (when you saw that password), I see no reason to blame the factory reset that you did. This is something to do with the flash process. Maybe this is kind of a punishment that LG unleash on those who use this process ? seriously, why on earth would anyone try to flash his LG2, if it wasn't to get rid of root ? I also don't understand how the password went away after you did hard-reset, since the device was "hard-reset" when you did that flash. You said that you re-flashed about 5 times, did that password appear after each of those 5 times ?
karstensson said:
Just wanted to notify that this method made my 32gb D802 a 16 gb one!
Click to expand...
Click to collapse
Same issue here.
I also got the question after I used the software to enter my encryptionkey. Wich I didnt have.
So I had to hardreset from the recoverymenu (volume down + pwr), then I suddenly had 10.77GB left instead of 26.77GB or something similar.
Annoys me pretty darn much at the time beeing!
I did use my IMEI, not my serialnumber and model. I'll try to use the serial and model this time around, and see if there are any differences at all in doing so.
And yes, it does say 32GB on the back. So we're not mistaken it for a 16GB-model
And it does say that the model is the 32GB when I check the hardware-info on the android itself.
Maybe this has something to do with me using the adbcommand for mounting storage incorrectly?
I thought however it would be reset when I used the LG Mobile Support Tool to hardreset everything though.
Will this work with the AT&T model D800?
Also does this remove all traces of root to the point where you get your warranty back?
what was the solution to this...
Does this work with the TMO versions?
The windows application keeps getting a Windows error and closing shortly after the process begins. Any tips?
I would prob stay away from this if i was anyone else....Because it must be messing people phones up and changing the storage capacity
I've been digging around online and can't find anything that helps me in my case.
Here's my stupidity: I flashed a kernel that was not intended for my phone (meant for Note 2). Reboot and dead screen. Can't get into download mode, recovery, nothing. Removed battery. Didn't help. Plugged into computer. Doesn't pick up anything connected. Odin doesn't see it. Tried RIFF. Can't get it to install the drivers it's supposed to. I saw something about jig dongles that can force it into download mode but I don't know about that.
What really stinks is I had just compiled SheepShaver for android and it took a few hours of work and I really don't want to do that all over again. Also pictures of my father who's just passed away are on there.
Am I screwed? Is there any way at all to get the proper kernel flashed back on this thing without a wipe? If not is there any way I can fix this phone? I have a semi-recent backup (about a month old) on my SD card. I have both Titanium Backup and a full nandroid backup on the SD.
Someone please come to my rescue. I've logged countless hours on this phone and I love it. All this because I couldn't get SELinux to go permissive...
You already know the answer. If you flashed a kernel not for your device and with the symptoms you have, your hard bricked. Jtag is the answer.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
You already know the answer. If you flashed a kernel not for your device and with the symptoms you have, your hard bricked. Jtag is the answer.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Do you know if these guys are the real deal? http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s4-jtag-brick-repair
I don't have the equipment to jtag it myself. Also just to be perfectly clear; An incorrect kernel cannot be fixed with a download mode jig correct?
mascondante said:
Do you know if these guys are the real deal? http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s4-jtag-brick-repair
I don't have the equipment to jtag it myself. Also just to be perfectly clear; An incorrect kernel cannot be fixed with a download mode jig correct?
Click to expand...
Click to collapse
mobiletechvideos.com have gotten high reviews on xda. They're the only ones I'd use.
Edit, I'm not sure they're the same as your link
Edit, edit it looks like they're the same guys
Edit, edit edit I don't know about the jig. It could get you into download mode.
Sent from my Nexus 5 using XDA Free mobile app
mascondante said:
I've been digging around online and can't find anything that helps me in my case.
Here's my stupidity: I flashed a kernel that was not intended for my phone (meant for Note 2). Reboot and dead screen. Can't get into download mode, recovery, nothing. Removed battery. Didn't help. Plugged into computer. Doesn't pick up anything connected. Odin doesn't see it. Tried RIFF. Can't get it to install the drivers it's supposed to. I saw something about jig dongles that can force it into download mode but I don't know about that.
What really stinks is I had just compiled SheepShaver for android and it took a few hours of work and I really don't want to do that all over again. Also pictures of my father who's just passed away are on there.
Am I screwed? Is there any way at all to get the proper kernel flashed back on this thing without a wipe? If not is there any way I can fix this phone? I have a semi-recent backup (about a month old) on my SD card. I have both Titanium Backup and a full nandroid backup on the SD.
Someone please come to my rescue. I've logged countless hours on this phone and I love it. All this because I couldn't get SELinux to go permissive...
Click to expand...
Click to collapse
Install drivers riffbox and use this program, revive your galaxy
https://mega.co.nz/#!LVZSHbSb!jX5wqKImIiT3C_rKXcQvZDlCzH0jJbLe0V8h5JpZmcE
djdedonrg said:
Install drivers riffbox and use this program, revive your galaxy
https://mega.co.nz/#!LVZSHbSb!jX5wqKImIiT3C_rKXcQvZDlCzH0jJbLe0V8h5JpZmcE
Click to expand...
Click to collapse
Thank you. I'm trying. I installed those drivers. Trying to find the forum that explains how to use that tool. I saw that thread but it didn't have the download link anymore for the tool.
Update:
Huston I believe we have a problem:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried installing manually and I get an error about the file's hash doesn't match the cert.
dead s4
mascondante said:
Thank you. I'm trying. I installed those drivers. Trying to find the forum that explains how to use that tool. I saw that thread but it didn't have the download link anymore for the tool.
Update:
Huston I believe we have a problem:
View attachment 2917703View attachment 2917704
I tried installing manually and I get an error about the file's hash doesn't match the cert.
Click to expand...
Click to collapse
which program is that? link is dead.does someone has it?
emplokeas said:
which program is that? link is dead.does someone has it?
Click to expand...
Click to collapse
I think you will need the actual riffbox device. I've long since given up on trying to interface over USB. Riffbox talks directly to the memory chip. Need to be comfortable with soldering. But I do happen to have a link to the latest release of their software. http://www.unlockforum.com/showthread.php/riff-jtag-manager-v1-72-more-new-models-32724.html?
Thats the forum they use. The official site is riffbox.org
Sorry I don't know much else to tell you. If it won't boot it won't listen for a connection on USB. Some devices have a failsafe that activates a sort of programming mode over USB but the Galaxy S4 isn't one of those devices afaik.
So yeah. As the title says I had a rooted VS980 on 4.4.2 with some bloat removed and I accidently hit the wrong button when prompted for the upgrade, I was in a hurry. yes, I'm a moron, and yes, I know this is probably wasting someone's valuable time and I thoroughly apologize for my n00bishness
having said that, I have tried to go through various tuts but none of them seem to be working. yes, it's likely that I am simply doing it wrong, but whatever the case I am stuck with my phone in a bootloop always returning to the TWRP recovery. I believe that means it is soft bricked so I'm hoping this can be fixed fairly easily with the right direction and some patience for my ignorance. I can't seem to get it into download mode with turning it off, holding the volume+ button and plugging it in, it just goes to twrp. :'(
my hope is to get a rooted lollipop. if that is not possible then I would be fine with going back to stock or possibly even a custom rom if it's not too awfully complicated. honestly, I'm at a point where I'm beginning to accept that I probably shouldn't be screwing around with it too much and will likely bite the bullet and just keep my phone stock since there are really only a few minor irritants that make me want to root it.
any help is very much appreciated.
anybody? pretty please? any ideas at all?
Deviouz1 said:
anybody? pretty please? any ideas at all?
Click to expand...
Click to collapse
I have the same problem.. take a look at my post in this section... right under yours... I have links posted to the only method to fix it and also a good question that could help you out as well
a.perkins89 said:
I have the same problem.. take a look at my post in this section... right under yours... I have links posted to the only method to fix it and also a good question that could help you out as well
Click to expand...
Click to collapse
actually, it doesn't look to be the same problem. i dont have download mode, but i do have recovery. it boots to twrp like a champ. what i think i really need is how to get the flash file VS98011A_01.zip on my phone via ADB Sideload, specifically when i cant get the drivers to work.
i've tried the following drivers:
LG_VZW_United_WHQL_v2.14.1.exe
LG_VZW_United_WHQL_v2.20.0.exe
LGUnitedMobileDriver_S50MAN310AP22_ML_WHQL_Ver_3.10.1_3.10.1.0
I may very well be mistaken about what needs to happen, i'm no expert, obviously, but from everything ive read any of those should have worked. i think if i can get the right flash on the phone i should be able to flash it via twrp no?
I"ll help
You need to adb sideload xdabbebs download mode restore and flash back to stock. Here is an excellent guide on adb sideloading, download xdabbeb restore download zip and put it where it tells you to. http://forum.xda-developers.com/showthread.php?t=2559200
Jaqueezzzy said:
You need to adb sideload xdabbebs download mode restore and flash back to stock. Here is an excellent guide on adb sideloading, download xdabbeb restore download zip and put it where it tells you to. http://forum.xda-developers.com/showthread.php?t=2559200
Click to expand...
Click to collapse
awesome,thanks you, i'll try that!
Deviouz1 said:
awesome,thanks you, i'll try that!
Click to expand...
Click to collapse
Just so you know it talks about flashing a ROM, but just use the zip you need insted, because it's the same principal.
Step 9 Fails.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i just happened to have a brand new data cable, tried again with same result so its not media related unless there is an issue with the plug itself, but it's charging and the Device manager shows the correct name ie VS980, it just has a yellow bang on it and i cant find a driver that changes that.
read some more and found others with the same issue apparently which led me to here: http://forum.xda-developers.com/showthread.php?t=2715408
which is where i found the "download mode restore" file you mentioned(i didnt see it in the thread you provided), but without the ability to get adb usb command to work i dont see how i can use it.
any ideas?
Put the zip on usb otg and flash it.
_____________________________________Read more write less and be smart
siggey said:
Put the zip on usb otg and flash it.
_____________________________________Read more write less and be smart
Click to expand...
Click to collapse
awesome, ty sir. i happened to have one of those laying around from when i cracked my screen on my old one and couldnt interact with the screen. took a while to find it buried but i have it and i have successfully been able to access a thumb drive. i think that might be all i need.
will report back though regardless.
ok, now i'm rrrrrEEAALLYY freakin confused...
successfully flashed (via the install section of twrp with usb otg thumbdrive mounted.)
xdabbeb_vs98028a_bootstack.zip
and
xdabbeb_vs982.5_1.1.0.zip
from
http://forum.xda-developers.com/verizon-g2/development/xdabbeb-s-vs982-5-v1-0-0-t2975551
but when i reboot, it goes directly to twrp still.
wat? :'(
ok, installed this:
VS980 39A Firmware
from here:
http://forum.xda-developers.com/verizon-g2/development/vs98039a-stock-fw-t3051560
rebooted, went straight to twrp again.
installed
Restore to 100% stock
from the same page.
rebooted. it went into an upgrade screen that errored and then rebooted before i got a chance to write down the error. but when it came back up, it started "android is upgrading".
so it looks like this may have worked. again, will update the success/failure when i know for sure, but thanks for the help yall. i really do appreciate it.
WOO-FREAKIN-HOOOO!!!
at the setup wizard now.
Deviouz1 said:
ok, installed this:
VS980 39A Firmware
from here:
http://forum.xda-developers.com/verizon-g2/development/vs98039a-stock-fw-t3051560
rebooted, went straight to twrp again.
installed
Restore to 100% stock
from the same page.
rebooted. it went into an upgrade screen that errored and then rebooted before i got a chance to write down the error. but when it came back up, it started "android is upgrading".
so it looks like this may have worked. again, will update the success/failure when i know for sure, but thanks for the help yall. i really do appreciate it.
Click to expand...
Click to collapse
Same problem! stupid Ota grrrrr
Your fix worked for me also. Only used the two files listed above and wiped dalvik after flashing both, one after the other with no reboot in between. Many thanks.
thecadman99 said:
Same problem! stupid Ota grrrrr
Your fix worked for me also. Only used the two files listed above and wiped dalvik after flashing both, one after the other with no reboot in between. Many thanks.
Click to expand...
Click to collapse
sweet, i'm glad someone else found it useful.
Yep, now another problem though. ..no mobile data. .. working on it.
I'd suggest flashing the files in post 12 (I didn't and am having TONS of problems)
So I really didn't get a fix- still working on it.
I have no download mode, and not way to get the serial port to display in device manager, so the LG Mobile support tool won't see my phone....
thecadman99 said:
Yep, now another problem though. ..no mobile data. .. working on it.
I'd suggest flashing the files in post 12 (I didn't and am having TONS of problems)
So I really didn't get a fix- still working on it.
I have no download mode, and not way to get the serial port to display in device manager, so the LG Mobile support tool won't see my phone....
Click to expand...
Click to collapse
Is your baseband recognized by chance?
Deviouz1 said:
Is your baseband recognized by chance?
Click to expand...
Click to collapse
Nope... its UNKNOWN
And I have not download mode
And I have not cdc serial showing up when connected
And TWRP and Root are gone
I'm starting a new thread for help- I've been working on this for 2 days lol.
Thanks for the reply!
Hmm, i was using my Nexus 6p as usual and i don't have any problem with it. One day i woke up because of my alarm rings, i closed the spotify and unplug the headphone. The phone automatically rebooted and does not stop at all until the battery dead. I was thinking about it is bootlooping so i decided to get into recovery and wipe the cache. However, i can't even get into bootloader because when i successful went into bootloader, within 1 second, the device automatically reboot again and start bootlooping. I don't have any chances to boot into recovery. I tried to flash new image but unfortunately does not work.
I asked my friend who is doing phone repair to check whether it is power button stuck or other possible problems to make this thing happen. The results are power button and battery working fine and does not broken or not functioning. I was about to send my Nexus 6p to Huawei Service Center since there is no Google Service Center in my country. Before that, i want to know if anyone has this kind of problem? I would like to fix this myself if possible and if there is any solution for it. Thanks and sorry for my bad english. I have provided a video sample about the situation of my Nexus 6p to show if anyone of you don't know what kind of problem i am facing right now. Please also ignore the sound of my video because of my bad shooting skill.
My Nexus 6p currently on
Android 8.1.0 Beta 1
Some photo sample of how i tried to reflash new image to my Nexus 6p in bootloader below
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Video sample of my Nexus 6p situation (seems like the video cannot be played in the post, i will give the link instead. Sorry about that)
https://www.youtube.com/watch?v=uiy-ToOPrP0&
https://forum.xda-developers.com/nexus-6p/general/guide-tutorial-nexus-6p-bootloop-death-t3716330
Exodusche said:
https://forum.xda-developers.com/nexus-6p/general/guide-tutorial-nexus-6p-bootloop-death-t3716330
Click to expand...
Click to collapse
Thanks for your helping. I have a question about that, the post is trying to said that i should flash the 4core patched boot image file right?
yaohui said:
Thanks for your helping. I have a question about that, the post is trying to said that i should flash the 4core patched boot image file right?
Click to expand...
Click to collapse
Yes you need your bootloader unlocked and then fastboot the 4corefix.img for 8.1. I understand you can't keep your phone on long enough to use fastboot. So you will have to sort that out first. Only thing I remember someone being able to do was heating up the back of the phone with hairdryer. That way it would stay on long enough to preform. There might be more ideas how you will have to read through the article.
Exodusche said:
https://forum.xda-developers.com/nexus-6p/general/guide-tutorial-nexus-6p-bootloop-death-t3716330
Click to expand...
Click to collapse
Exodusche said:
Yes you need your bootloader unlocked and then fastboot the 4corefix.img for 8.1. I understand you can't keep your phone on long enough to use fastboot. So you will have to sort that out first. Only thing I remember someone being able to do was heating up the back of the phone with hairdryer. That way it would stay on long enough to preform. There might be more ideas how you will have to read through the article.
Click to expand...
Click to collapse
Thanks, Appreciated. I will try it.
yaohui said:
Thanks, Appreciated. I will try it.
Click to expand...
Click to collapse
Download the appropriate image on your computer and get fastboot ADB all set up. Then heat the back of your phone with hairdryer (just above the battery) until nice and warm. Then try and boot your phone into bootloader mode and see if it stays. Then quickly unlock bootloader then flash modified 4core boot.img. Make sure you download the one for 8.1 .
Exodusche said:
Download the appropriate image on your computer and get fastboot ADB all set up. Then heat the back of your phone with hairdryer (just above the battery) until nice and warm. Then try and boot your phone into bootloader mode and see if it stays. Then quickly unlock bootloader then flash modified 4core boot.img. Make sure you download the one for 8.1 .
Click to expand...
Click to collapse
My bootloader is unlocked at first actually, so now i'm going to try to flash the modified 4core boot.img.
Exodusche said:
Download the appropriate image on your computer and get fastboot ADB all set up. Then heat the back of your phone with hairdryer (just above the battery) until nice and warm. Then try and boot your phone into bootloader mode and see if it stays. Then quickly unlock bootloader then flash modified 4core boot.img. Make sure you download the one for 8.1 .
Click to expand...
Click to collapse
no luck
am i doing the right thing? I did not heat up my Nexus 6p yet because 2am now here. If really need the hairdryer to warm up, i will try it later.
yaohui said:
no luck
am i doing the right thing? I did not heat up my Nexus 6p yet because 2am now here. If really need the hairdryer to warm up, i will try it later.
Click to expand...
Click to collapse
Ok my bad I didn't read correctly your not on latest 8.1 December your on 8.1 beta 1?
Maybe need a different image. Might be easier to first flash latest stable 8.1 but go though the image list and see if yours is there.
Exodusche said:
Ok my bad I didn't read correctly your not on latest 8.1 December your on 8.1 beta 1?
Maybe need a different image. Might be easier to first flash latest stable 8.1 but go though the image list and see if yours is there.
Click to expand...
Click to collapse
Actually, I did perform flash using all of the modified boot.img and all the result are same. I will try to look into it more.
yaohui said:
Actually, I did perform flash using all of the modified boot.img and all the result are same. I will try to look into it more.
Click to expand...
Click to collapse
See if you can flash the latest 8.1 Stable then go back and flash the first image we tried.
Exodusche said:
See if you can flash the latest 8.1 Stable then go back and flash the first image we tried.
Click to expand...
Click to collapse
it seems like my Nexus 6p remain the same situation after warm up the back of the phone using hairdryer.
yaohui said:
it seems like my Nexus 6p remain the same situation after warm up the back of the phone using hairdryer.
Click to expand...
Click to collapse
Sorry to here that it was a shot in the dark. Are you able to flash stock image through fastboot?
Exodusche said:
Sorry to here that it was a shot in the dark. Are you able to flash stock image through fastboot?
Click to expand...
Click to collapse
I don't think i am able to do that since my Nexus 6p reboot automatically even in bootloader
Besides, i realise one thing that when my phone is on bootlooping, normally you will need to hold power button + volume up + volume down to get into bootloader. but in my case i don't need to. During bootloop, i just need to hold volume down and it will go through bootloader. but the result is still same as previous which is bootlooping still.
yaohui said:
Besides, i realise one thing that when my phone is on bootlooping, normally you will need to hold power button + volume up + volume down to get into bootloader. but in my case i don't need to. During bootloop, i just need to hold volume down and it will go through bootloader. but the result is still same as previous which is bootlooping still.
Click to expand...
Click to collapse
I think your motherboard is fried. The people at repair shop unable to do anything? If you go to the service centre, they'll ask you to replace the motherboard. How old is the phone?
tropical cactus said:
I think your motherboard is fried. The people at repair shop unable to do anything? If you go to the service centre, they'll ask you to replace the motherboard. How old is the phone?
Click to expand...
Click to collapse
Yup, the guy just told me the same thing that i might have to change the motherboard. He asked me to send to the official service centre is the best solution. My phone is around 2 years. I just posted here to see if anyone is facing this kind of problem and looking for solution to fix myself. Since the motherboard is fried, i think i can't do anything for it unless i change the motherboard, so i think i will send to service centre later. Thanks for your reply and @Exodusche your help.
My mobile phone system is the o12c10 version, and then I downloaded the o12c11 version, but I found that the OTA channel is not displayed on the mobile phone, so I directly used fastbootd to brush into the playload. Bin file in FastBoot mode (not FastBoot mode, but FastBoot mode)
After that, I can't start the machine directly, can't enter any mode, and 9008 can't get in
Long press to enter 9008 or any other mode will not respond, and there will be no vibration feedback
When charging, the screen is also black and does not display
The computer interface didn't respond. I've tried line breaks, too
I tried the original cable, lightning cable and USB port
The driver also attempts to uninstall and reinstall the new driver
The computer device manager window still does not show any new devices
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then I got the remote consultation service. The second-line remote service learned about the situation and didn't solve it remotely. It suggested that I send it for repair, but the epidemic situation was blocked and I couldn't send it for repair
How to solve this situation
emergency----------------
English is not my native language; please excuse typing errors.
2023/03/02to update：XDA post-88110375 comments
Solution：How to prevent and remedy the crash caused by wrong XBL
It seems you flashed wrong xbl image, more info here.
Probably motherboard replace is the only solution.
ppajdek said:
It seems you flashed wrong xbl image, more info here.
Probably motherboard replace is the only solution.
Click to expand...
Click to collapse
yeah, it's gone with the wind, motherboard replace is the only solution
nkhater said:
yeah, it's gone with the wind, motherboard replace is the only solution
Click to expand...
Click to collapse
Ok, I have to pay more attention to the next time I swipe the system, so as not to make such a mistake again, thank you
ppajdek said:
It seems you flashed wrong xbl image, more info here.
Probably motherboard replace is the only solution.
Click to expand...
Click to collapse
Thank you for letting me know what's wrong with me. It seems that I should pay more attention to this next time I swipe the system
小忧忧 said:
Ok, I have to pay more attention to the next time I swipe the system, so as not to make such a mistake again, thank you
Click to expand...
Click to collapse
What do you mean will pay more attention, this is catastrophic, there is no room for error, you make a mistake and your investment is gone. This is new to OnePlus, I have been using their phones from day one, never thought this will ever happen.
nkhater said:
What do you mean will pay more attention, this is catastrophic, there is no room for error, you make a mistake and your investment is gone. This is new to OnePlus, I have been using their phones from day one, never thought this will ever happen.
Click to expand...
Click to collapse
Maybe the translation quality of the translator I use is not so perfect.
I prefer to experience other third-party systems without adaptation, so I will brush GSI
Therefore, I will pay more attention to these problems in the process of system brushing in the future
I solved this problem, and the specific solutions for details have been updated to my blog (need to translate, my English level is not good)
link:How to prevent and remedy the crash caused by the wrong XBL
小忧忧 said:
I solved this problem, and the specific solutions for details have been updated to my blog (need to translate, my English level is not good)
link:How to prevent and remedy the crash caused by the wrong XBL
Click to expand...
Click to collapse
My browser wont load the pictures and if im rifht they would show me the "line" to enter.
According to the description above, we can buy an engineering cable to connect to your phone
Then use this line to perform the normal 9008 flashing operation to save your phone
Just to be sure, we can use an Engineering cable to unbrick our devices?
little follow up here, would that work ? i did the same thing years ago with a Lenovo ZUK Z2 Pro, taped aluminium inside the usb connections which i saw from youtube on how to do that, and it reviewed my dead phone into edl from where i could flash stock roms
would this also work on our oneplus 8 pro ?
i hope we can figure stuff out here, threw away my dev-usb cable years ago, would try making a new one
Please tell me if any of you have been able to revive our 8 pro with this cable? or similar
Winstarshl said:
Please tell me if any of you have been able to revive our 8 pro with this cable? or similar
Click to expand...
Click to collapse
Yes it works, read here.
xtcislove said:
My browser wont load the pictures and if im rifht they would show me the "line" to enter.
According to the description above, we can buy an engineering cable to connect to your phone
Then use this line to perform the normal 9008 flashing operation to save your phone
Just to be sure, we can use an Engineering cable to unbrick our devices?
Click to expand...
Click to collapse
ikram.senguen said:
little follow up here, would that work ? i did the same thing years ago with a Lenovo ZUK Z2 Pro, taped aluminium inside the usb connections which i saw from youtube on how to do that, and it reviewed my dead phone into edl from where i could flash stock roms
would this also work on our oneplus 8 pro ?
i hope we can figure stuff out here, threw away my dev-usb cable years ago, would try making a new one
Click to expand...
Click to collapse
Winstarshl said:
Please tell me if any of you have been able to revive our 8 pro with this cable? or similar
ppajdek said:
Yes it works, read here.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Sorry, due to some work and network problems, I can't follow up XDA's posts in time. Besides, my English is not good. I use Google Translate, so some abnormal sentences may appear in the text. Please forgive me
Many people have encountered the same problems as me, which are solved by using the project line mentioned in How to prevent and remediate the crash by wrong XBL
One of my friends couldn't buy a data line because of some factors. He tried to understand the method of data line short circuit, but the test failed to enter 9008. Other group friends also bought the short data line test mentioned in How to recover your device after flashing incorrect DDR xbl images, but failed to enter the final test. (It is also possible that the line used in this article is qualified? But I can't buy it in my region, so I can't test it)
It is worth noting that the 22K resistor is used in the product description of the engineering data line introduced in my article. I think that's the key
I tried to search the platforms you can buy in your country, but I didn't find the data line
However, I found pcb2.0. It has a lot of internal resistance. Its appearance is roughly as shown in the figure below. This may help you