Database Info

My G2x seems to be dead

I'm here, requesting help, i've read (i think) almost everything. Try everything and i'm not able to recover my G2x.
I'm from mexico, and my english it's no so good, i hope that everyone can understand what i'm trying to say U_U
I brought a used T-Mobile G2x from ebay. I was SOOO happy with the phone, a good one, a kickass and it was about $250 dlls for me. I think that was a good deal. The phone was on a average/good condition.
So, i rooted it, then after, moved the rom from stock to CM7 stable.
I changed then to eaglesblood ICS, then another eaglesblood, and then again CM7.
The phone was working very good. Then, a issue appeared.
Some day, the phone was a little slow, then i rebooted it. And then started the pain...
The screen showed the LG Logo, white brilliant. And after a seconds, power off. What!?
I tried to power on again. Nothing. I did the battery pull and then worked fine. I thought that was a simple bug or something.
Later, the phone ran out of energy. I pluged on the wall charger but nothing happened. I left it for an hour and tried to turn it on. Nothing...
Then charged the battery with a multicharger and the same problem. LG Logo, nothing. Checked on the CWM Recovery and did a cleanup of battery stats, nothing. I was desperate, so i've flashed my phone with Eaglesblood again. Vuala, the phone worked... 'till froze and i had to pull the battery... Again, LG Logo... nothing.
The phone boot up by himself after leaving it for an hour or more. But i had another problem... Battery at 999% Or battery stuck at 32% and suddenly dies...
I've checked with the battery app and saw that the battery said 0 mV
I have 2 batteries, and the both with the same problem. One LG, one chinese.
So, i went with a friend of mine, i took borrowed a battery of his LGO3D, and... nothing
The phone works with APX, powers on on the recovery, i even sometimes reads ok the battery and the phone comes alive, 'till i have to reboot it because the phone is so slow after 2 or 3 weeks without a reboot... but it's so rare and random...
I even updated the phone with the 21y baseband and the new stock rom, but keeps doing the same thing...
I'm just at the point that i want to throw the phone to the wall...
There are something that i can do?
Change some piece?
I must say that when the phone read the battery and it's ok, i can charge it normally, works perfectly, usb ok, everything it's like nothing was bad. But the problem is if the phone shut's down...

Get adb working with USB and if using a windows pc open Command Prompt and run
HTML:
adb devices
....Make sure your device is found, an ID number will appear if successful....
HTML:
adb reboot
....Let the phone start rebooting. When "adb devices" works and shows the phone ID again proceed...
HTML:
adb shell
$ su
# dmesg > /sdcard/dmesg.txt
# logcat -v time -d > /sdcard/logcat.txt
# exit
$ exit
adb pull /sdcard/logcat.txt %USERPROFILE%\Desktop\logcat.txt
adb pull /sdcard/dmesg.txt %USERPROFILE%\Desktop\dmesg.txt
exit
If you get a complaint with those last 2 commands; change %USERPROFILE% = whatever your username is where your Desktop is located. (i.e. C:\Users\me\Desktop\dmesg.txt)
Then either email them to me or post them on www.pastebin.com and post links to both files.

I'm a little lost...
First of All! Thanks for the help
And i dont know... The phone must be ON to do that?
The phone right now doesn't power on, just the LG Logo, at this point, when i attach to a computer via USB Cable, the computer doesn't detect anything...
I can enter the CWM Recovery, it's enough??
And a funny thing: The phone NEVER powers ON (Not even the LG LOGO) when usb or charger it's connected.
EDIT:
Good news, i've got adb working, but i don't have su, i'm downloading it thanks
EDIT AGAIN
The last time that i've flashed to stock rom the g2x forgot to root the phone
i've already tried with adb commands, but i got errors when i try...
I guess that i need usb debugging On, and i doesn't have it...
I'm on a dead end??

Go to the ROM for recovery thread in development section, follow it step by step and your phone will be 100% alive and kicking on GB 2.3.4.
Sent from my SPH-D710 using xda premium

supertaco said:
First of All! Thanks for the help
And i dont know... The phone must be ON to do that?
The phone right now doesn't power on, just the LG Logo, at this point, when i attach to a computer via USB Cable, the computer doesn't detect anything...
I can enter the CWM Recovery, it's enough??
And a funny thing: The phone NEVER powers ON (Not even the LG LOGO) when usb or charger it's connected.
EDIT:
Good news, i've got adb working, but i don't have su, i'm downloading it thanks
EDIT AGAIN
The last time that i've flashed to stock rom the g2x forgot to root the phone
i've already tried with adb commands, but i got errors when i try...
I guess that i need usb debugging On, and i doesn't have it...
I'm on a dead end??
Click to expand...
Click to collapse
If I recall you were the one who emailed me and I sent you links to NVFlash correct? Did that work for you? I'm just trying to see what your question really is. It sounded from you OP that the hardware perhaps keeps failing and no matter which ROM you flash, you eventually get stuck in bootloop like you are now. Are you just trying to get out of bootloop or is this a reocurring problem? If your stuck in bootloop then your only solution is to NVFlash a recovery and push a rom. If its reocurring then we gotta figure out why... thats where my instructions come in. So you need to tell us exactly what you're trying to do.
As for adb yes you can adb from recovery. You gotta go to Mounts and storage > Mount /system though or else the device wont show.

oOo B0XeR oOo said:
If I recall you were the one who emailed me and I sent you links to NVFlash correct? Did that work for you? I'm just trying to see what your question really is. It sounded from you OP that the hardware perhaps keeps failing and no matter which ROM you flash, you eventually get stuck in bootloop like you are now. Are you just trying to get out of bootloop or is this a reocurring problem? If your stuck in bootloop then your only solution is to NVFlash a recovery and push a rom. If its reocurring then we gotta figure out why... thats where my instructions come in. So you need to tell us exactly what you're trying to do.
As for adb yes you can adb from recovery. You gotta go to Mounts and storage > Mount /system though or else the device wont show.
Click to expand...
Click to collapse
Ok... my first problem: Language. I don't have problem with the reading, but writing... i'll try to put my words on the right place
I don't remember, when i first flashed my G2x i did it with the Rom Manager App... the result came on a bootloop. Then i used NVFlash and flashed a correct ClockworkMod Recovery. Installed CM7 and everything was fine. Then i wanted to try ICS and flashed it again. No problem. I normally follow the guides step by step, and the phone was right. Then, one day the phone froze and was the first time that i had the bootloop with the LG Bright Logo, then dim, and then power off.
The problem not was while i was flashing a rom. Because while i was on the problem, i flashed with NVFlash the original bootloader and then restore the original firmware, and the problem still there. Right now the phone has the stock rom, updated by the LG utility, and the problem persists.
I think that is what you say. The phone doesn't pass the LG Logo screen no matter which rom i flash... What i don't understand is that the phone seems to be ok. When it powers (a week ago) it worked just fine...
I don't think that is a bootloop caused by a bad flashing... i think that is a recurring problem...
I have this 2 folders with tools for the NVFlash, i think that the both of them are right...
One-Click-G2x-recovery-flasher-04-28-12 [Folder]
One-Click-G2x-recovery-flasher-09-23 [Folder]
They have the APX drivers and NVFlash and the One-click-G2xr-recovery-flasher app...
I'll mount the /system in recovery and i will try to get that log. With the /system mounted then i think that i can root the phone...
I'm gonna try... let's see what happen...
Thanks
EDIT: I noticed (when the problem first came) that the sticker of water damage was ripped off... is not there... But i don't know if the phone was really damaged by water, because i'm not the first owner... The phone was working fine for about 6 months and now it's just like i'm explaining...

supertaco said:
Ok... my first problem: Language. I don't have problem with the reading, but writing... i'll try to put my words on the right place
I don't remember, when i first flashed my G2x i did it with the Rom Manager App... the result came on a bootloop. Then i used NVFlash and flashed a correct ClockworkMod Recovery. Installed CM7 and everything was fine. Then i wanted to try ICS and flashed it again. No problem. I normally follow the guides step by step, and the phone was right. Then, one day the phone froze and was the first time that i had the bootloop with the LG Bright Logo, then dim, and then power off.
The problem not was while i was flashing a rom. Because while i was on the problem, i flashed with NVFlash the original bootloader and then restore the original firmware, and the problem still there. Right now the phone has the stock rom, updated by the LG utility, and the problem persists.
I think that is what you say. The phone doesn't pass the LG Logo screen no matter which rom i flash... What i don't understand is that the phone seems to be ok. When it powers (a week ago) it worked just fine...
I don't think that is a bootloop caused by a bad flashing... i think that is a recurring problem...
I have this 2 folders with tools for the NVFlash, i think that the both of them are right...
One-Click-G2x-recovery-flasher-04-28-12 [Folder]
One-Click-G2x-recovery-flasher-09-23 [Folder]
They have the APX drivers and NVFlash and the One-click-G2xr-recovery-flasher app...
I'll mount the /system in recovery and i will try to get that log. With the /system mounted then i think that i can root the phone...
I'm gonna try... let's see what happen...
Thanks
EDIT: I noticed (when the problem first came) that the sticker of water damage was ripped off... is not there... But i don't know if the phone was really damaged by water, because i'm not the first owner... The phone was working fine for about 6 months and now it's just like i'm explaining...
Click to expand...
Click to collapse
Ok, I bet your partition tables are messed up. If you can get that dmesg and logcat file it would be ideal but if you cant then we just gotta move forward.
First copy all your stuff from SDcard and internal memory into a folder on a PC. Make a backup using clockwork or whatever and also copy that onto a PC just to be safe.
Then you need to search the G2x forum for this batch utility called something like "auto-formatter partition repair tool" or something similar. If you cant find it message me.
Youll want to run that first, its going to completely wipe all of your stuff and reformat the blocks sizes. Once done youll need to NVFlash a CWM recovery again. Then push a ROM over to the phone and install with CWM. (Dont push a stock rom or anything Gingerbread. Ideally push EaglesBlood ICS since I know it works and can help you troubleshoot.
So i would do that first because i bet your upgrade when u said you attempted to install ICS corrupted the file system, which can happen if you dont format /system prior.
Get the utility, backup everything , format the partitions, NVflash CWM recovery, push ICS rom, install, install GAPPS, come back here and tell me it worked

oOo B0XeR oOo said:
Ok, I bet your partition tables are messed up. If you can get that dmesg and logcat file it would be ideal but if you cant then we just gotta move forward.
First copy all your stuff from SDcard and internal memory into a folder on a PC. Make a backup using clockwork or whatever and also copy that onto a PC just to be safe.
Then you need to search the G2x forum for this batch utility called something like "auto-formatter partition repair tool" or something similar. If you cant find it message me.
Youll want to run that first, its going to completely wipe all of your stuff and reformat the blocks sizes. Once done youll need to NVFlash a CWM recovery again. Then push a ROM over to the phone and install with CWM. (Dont push a stock rom or anything Gingerbread. Ideally push EaglesBlood ICS since I know it works and can help you troubleshoot.
So i would do that first because i bet your upgrade when u said you attempted to install ICS corrupted the file system, which can happen if you dont format /system prior.
Get the utility, backup everything , format the partitions, NVflash CWM recovery, push ICS rom, install, install GAPPS, come back here and tell me it worked
Click to expand...
Click to collapse
It's a shame that i cannot get that logcat... :/
Well... i have nothing to lose (data, or something), so i searched over the forums and i found this utility:
Code:
[URL="http://forum.xda-developers.com/showthread.php?t=1590523"]http://forum.xda-developers.com/showthread.php?t=1590523[/URL]
I think thats the right one, or at least, one of many...
That utility flashes a CWM Touch, then, i installed Eaglesblood Gingerbread (because the utility said that if i don't, the sdcard will not be recognized) and the gaaps...
Turned off the phone...
Turned On...
But then again, i have the LG logo bright, then dim, then power off :/
Do you think that could be a charger flex problem? Motherboard? I should burn it?? :/

Use the batch cleanup tool, then flash stock rooted ROM. That way you cab make sure something works, and stock is going to be the safest flash. If that works, then you can go on to custom Roms
Sent from my LG-P999 using xda premium

supertaco said:
It's a shame that i cannot get that logcat... :/
Well... i have nothing to lose (data, or something), so i searched over the forums and i found this utility:
Code:
[URL="http://forum.xda-developers.com/showthread.php?t=1590523"]http://forum.xda-developers.com/showthread.php?t=1590523[/URL]
I think thats the right one, or at least, one of many...
That utility flashes a CWM Touch, then, i installed Eaglesblood Gingerbread (because the utility said that if i don't, the sdcard will not be recognized) and the gaaps...
Turned off the phone...
Turned On...
But then again, i have the LG logo bright, then dim, then power off :/
Do you think that could be a charger flex problem? Motherboard? I should burn it?? :/
Click to expand...
Click to collapse
Yes thats the utility, and the post above by "rtotheichie" is correct too.
You cant flash a Gingerbread ROM. You need to either push a stock/rooted build, or an ICS build. It's that gingerbread -to- ICS thats causing the partition problem (if it even is that). So what you're doing is fixing it then messing it up again.
--> There could be any number of things going on and we can guess at anything but what good is that gonna do? ... You NEED to get that #dmesg log. I would focus on doing whatever you can to get ADB working because thats going to tell us exactly what is failing at boot time. Can you get into Recovery? I wouldn't even worry about starting the ROM, you should focus on getting into Recovery first. If you cant get into Recovery then you didn't flash it correctly with NVFlash. If you can get in, then go to Mounts & Storage > mount /system ...then get that ADB going using my 1st post above. Thats your only hope if you cant get it on your own.

oOo B0XeR oOo said:
Yes thats the utility, and the post above by "rtotheichie" is correct too.
You cant flash a Gingerbread ROM. You need to either push a stock/rooted build, or an ICS build. It's that gingerbread -to- ICS thats causing the partition problem (if it even is that). So what you're doing is fixing it then messing it up again.
--> There could be any number of things going on and we can guess at anything but what good is that gonna do? ... You NEED to get that #dmesg log. I would focus on doing whatever you can to get ADB working because thats going to tell us exactly what is failing at boot time. Can you get into Recovery? I wouldn't even worry about starting the ROM, you should focus on getting into Recovery first. If you cant get into Recovery then you didn't flash it correctly with NVFlash. If you can get in, then go to Mounts & Storage > mount /system ...then get that ADB going using my 1st post above. Thats your only hope if you cant get it on your own.
Click to expand...
Click to collapse
Well, i have no problems with recovery. Never had IT. But the last time i tried to use the commands failed... I'll post a video, maybe that will be more self explaining... I really appreciate that you take a time for helping me thanks

supertaco said:
Well, i have no problems with recovery. Never had IT. But the last time i tried to use the commands failed... I'll post a video, maybe that will be more self explaining... I really appreciate that you take a time for helping me thanks
Click to expand...
Click to collapse
No problem.
Well if you can get into recovery and if you have ADB and the drivers for the phone setup on your PC you should have no problems connecting. Try using a Windows PC if you can, it's funny but ADB is probably the only thing that is easier to get going the 1st time in Windows rather than Linux (Ubuntu).
Just keep trying and run
HTML:
$ adb devices
each time until a device ID shows up.
I've noticed you've posted this same question on like every single Android website that exists; but I'm telling you what the correct answer is and the only way you're going to be able to figure out what is going on is to get to a log file. No one has a magic trick that will automagically fix this from afar. Anything else is just guessing and checking.
In recovery, try going to Advanced > Show log ...what does that say? Also it won't hurt to try going to Advanced > Fix permissions. I doubt that will do anything for you but it won't hurt to try at this point.

oOo B0XeR oOo said:
No problem.
Well if you can get into recovery and if you have ADB and the drivers for the phone setup on your PC you should have no problems connecting. Try using a Windows PC if you can, it's funny but ADB is probably the only thing that is easier to get going the 1st time in Windows rather than Linux (Ubuntu).
Just keep trying and run
HTML:
$ adb devices
each time until a device ID shows up.
I've noticed you've posted this same question on like every single Android website that exists; but I'm telling you what the correct answer is and the only way you're going to be able to figure out what is going on is to get to a log file. No one has a magic trick that will automagically fix this from afar. Anything else is just guessing and checking.
In recovery, try going to Advanced > Show log ...what does that say? Also it won't hurt to try going to Advanced > Fix permissions. I doubt that will do anything for you but it won't hurt to try at this point.
Click to expand...
Click to collapse
I'll try that, today
And i know that aint no magic trick that fix my phone... I'll try everything to resolve the problem.
Thanks...
And another thing. I've checked my PM's, and saw that i've never send a PM to you. And no, i'm not flooding the entire www with my question. But i think that i should have used a diferent question to describe my problem. This is the first time that i ask for help, after reading and reading on the web, and almost everyone says: "send it back to t-mobile", but that's not an option for me. And my first choice (and olny) for asking help of course it's xda.
I remember that once clicked "show log" and an error pop out, but i didn't try the fix permissions options.
This is the video. Sorry for my bad english.
Video

supertaco said:
I'll try that, today
And i know that aint no magic trick that fix my phone... I'll try everything to resolve the problem.
Thanks...
And another thing. I've checked my PM's, and saw that i've never send a PM to you. And no, i'm not flooding the entire www with my question. But i think that i should have used a diferent question to describe my problem. This is the first time that i ask for help, after reading and reading on the web, and almost everyone says: "send it back to t-mobile", but that's not an option for me. And my first choice (and olny) for asking help of course it's xda.
I remember that once clicked "show log" and an error pop out, but i didn't try the fix permissions options.
This is the video. Sorry for my bad english.
Video
Click to expand...
Click to collapse
I saw the video.
Take out the battery > then put it back in.
Press and hold BOTH the [Power] and [Volume Down-] at the same time and keep holding them.
Keep them both pressed while the "LG logo" appears; shortly after you should see the white logo change to a BLUE logo... once you see that you can let go.
Does that work and get you into Recovery? ...let me know.
One other thing to try...
Plug your USB cable into the Computer ONLY ---Not the phone.
Take out the battery, do NOT put it back in.
Now (with the battery still removed), Press and Hold [Volume Up+] and [Volume Down-] together. Do not press the Power button.
While still holding both Volume buttons together, insert the USB cable into the phone.
Now wait a second or two, does the phone Power On into a "Download mode screen"?
If not, let go of the Volume buttons and unplug the USB from the phone.
Now plug the USB back into the phone. Press and hold the [POWER] Button for several seconds (still with NO battery in, just the USB).
Does that turn the phone on?
P.S. - This might be good to have as well:
User manual (Spanish): http://www.lg.com/us/products/documents/LG-G2x-UserGuide_ES.pdf
Service Repair Manual (English): http://www.mediafire.com/view/?cscdjc6p08t2omq

oOo B0XeR oOo said:
I saw the video.
Take out the battery > then put it back in.
Press and hold BOTH the [Power] and [Volume Down-] at the same time and keep holding them.
Keep them both pressed while the "LG logo" appears; shortly after you should see the white logo change to a BLUE logo... once you see that you can let go.
Does that work and get you into Recovery? ...let me know.
One other thing to try...
Plug your USB cable into the Computer ONLY ---Not the phone.
Take out the battery, do NOT put it back in.
Now (with the battery still removed), Press and Hold [Volume Up+] and [Volume Down-] together. Do not press the Power button.
While still holding both Volume buttons together, insert the USB cable into the phone.
Now wait a second or two, does the phone Power On into a "Download mode screen"?
If not, let go of the Volume buttons and unplug the USB from the phone.
Now plug the USB back into the phone. Press and hold the [POWER] Button for several seconds (still with NO battery in, just the USB).
Does that turn the phone on?
P.S. - This might be good to have as well:
User manual (Spanish): http://www.lg.com/us/products/documents/LG-G2x-UserGuide_ES.pdf
Service Repair Manual (English): http://www.mediafire.com/view/?cscdjc6p08t2omq
Click to expand...
Click to collapse
I'm currently downloading the service manual and the user manual.
Ok, i tried the first thing. The phone gets on recovery mode. All good.
On the second thing to try:
-I followed the steps just as you said: vol+ and vol- and connect usb cable. It makes a sound of connected device, checked and windows detects a NVIDIA USB Boot-recovery driver for Mobile devices, but the phone screen never powers up or show a download mode screen. When i flash anything with NVFlash it shows the Download mode screen...
-I plugged the phone without battery, and pushed the power button. The phone does not power on. Not even the LG logo or anything.
I'm still trying to get that logcat. But everytime that i want to type "su" on the adb shell says that cannot found su...
Now i'm on recovery.
Advanced> fix permissions: Done.
Show log:
Init.svc.adbd=running
I: Checking for extendedcommand...
I: Skipping execution of extendedcommand, file not found...
W: Failed to mount /dev/block/mmcblk0p1 (invalid argument)
W: Failed to mount /dev/block/mmcblk0p7 (invalid argument)
Fixing permissions...
/sbin/fix_permissions 2.04 started at 01-01-2007 00:00:36
cat: can't open '/data/system/packages.xml' : no such file or directory
cat: can't open '/data/system/packages.xml' : no such file or directory
/sbin/fix_permissions 2.04 ended at 01-01-2007 00:00:36 (runtime: 0m0s)
Done!

Whats the status on this are you still dead? Looks like you need to do that partition formatter script now... appears your partitions are messed up. What ROM is on there now?

oOo B0XeR oOo said:
Whats the status on this are you still dead? Looks like you need to do that partition formatter script now... appears your partitions are messed up. What ROM is on there now?
Click to expand...
Click to collapse
Sorry, i didn't get the mail of new post...
Yeah, it's still dead...
Today, i put the battery on the phone and it started right away. Battery status ok, everything working fine. But i didn't put a sim card, so i turned off the phone and it's dead again.
I don't know if i'm getting a GOOD partition formatter. But i've already used one... and the result it's the same...
And even tried a crazy method of one guy that put the phone on the fridge for 10 mins and then NVFlashed-it to a stock gb...
And nothing U_U
Power up, show a bright LG logo, then a less bright one... power off...
Thanks for your help...
EDIT:
Today i opened the phone, extracted the logic board and watched everything. A VERY SMALL bga chip (i don´t know wich) had a little crack on it, i cleaned with a soft brush and a little piece came off... Now the phone doesn't boot at all, not even the LG logo... i think that's the end...
If someone can indicate me where i can buy a new mainboard it would be very appreciated. Thanks.
END

LG
eBay
Stuff wanted/selling here
Find a person selling a great phone but like the screen is broken or something. Look at the repair manual i posted previously above.

lg mytouch c800 bricked?

hi im pretty new here a friend of mine gave me her lg c800 mytouch to try and fix it for her.. not sure what she did she said she rooted the phone and the root was successful but i have a good idea that she doesnt know what she was doing..i will post a pic of the error screen im getting. but it says
E:Cant find misc
E:cant find misc
Finding update package...
E:unknown volume for path [sd:/download/adb_fastboot_and_other_tools.Zip]
E:Cant mount SDCARD:/download/adb_fastboot_and_other_tools.zip
Installation aborted
facory reset failed
restart factory reset..
now im far from a pro at this i know a lil more about computers and Ios devices..but ive rooted a few phones and to me it looks like she unzipped adb fastboot on her phone from her sd card??
ive tried holding F..A..vol down..and power..Nothing..
ive tried volume up .volume down and power still nothing..
BUT if i hold E..vol UP and power it brings me to a white screen that says S/W update
the big problem is the phone wont stay on long enough to do anything on the computer it stays on 3 sec. then reboots to same screen (computer says phone is unplugged) then phone just keeps restarting.
but the phone WILL stay on when i put it on the S/W update screen..but computer wont recognize the phone at all on that screen
ive tried the adb and fastboot commands but the phone wont stay recognized..it will recognize the phone and say thats its in recovery mode but when phone restarts it dont see phone no more..
well thanks ahead of time if anyone has any input or solution
and hopefully all this will make sense to someone lol
i think this pic will work.. if not ill try again

any ideas please?? or am i completely out of luck?

When you say:
delilah25 said:
it will recognize the phone and say thats its in recovery mode but when phone restarts it dont see phone no more..
Click to expand...
Click to collapse
...do you mean that you can successfully communicate with the phone over USB, but you only have 3 seconds? What way is the phone recognized? Is it visible to adb/fastboot?

post-mortem said:
When you say:
...do you mean that you can successfully communicate with the phone over USB, but you only have 3 seconds? What way is the phone recognized? Is it visible to adb/fastboot?
Click to expand...
Click to collapse
Yes In Adb device list it shows the phone and then says recovery..but after that I don't have enough time to type any other commands ..the phone is also recognized in "my computer" as removable device then when the phone restarts seconds later it says device unplugged ..and just keeps restarting on its own till I remove the battery...I just read on the forum in a post that Adb will recognize the phone if it's off but I remove the battery and put it back in and plug in USB and phone turns on and keeps restarting won't even let me turn it off!! I'm losing patience with this thing lol
But I don't get why the error mentions fastboot? Not my phone so if it's not fixable I don't really care but I'm just the stuborn type when it comes to fixing electronics ..again thanks ahead of time to anyone that helps cuz I'm completely lost on this one

Have you tried timing it to send a quick "adb reboot recovery"? If you can use fastboot, you can tell it to boot off a new, custom recovery img, without actually flashing it.

i have the same problem
post-mortem said:
Have you tried timing it to send a quick "adb reboot recovery"? If you can use fastboot, you can tell it to boot off a new, custom recovery img, without actually flashing it.
Click to expand...
Click to collapse
i used an app on the market to remove bloatware. i removed slacker and the app stated that after two reboots that everything would be fine and the app would be gone. after one reboot the phone has the same screen this gentlemans lady friend has. it looks like the app its looking for is no longer zip aligned properly. someone told me to rename a recovery image the error message to trick the bootloader into thinking the missing app is there. hes an app dev so i figured he knows whats what. ive tried everything the gentleman in this post said and more. hell i have two of these phones and rooted the other and made a backup of that phone and dragged the backup to an sd card and rebooted to see if any of the backed up system apks would trigger a successful reboot but to no avail. i have all the drivers i need and adb commands but nothing works because the phone doesnt stay connected to my pc long enough for anything. please reply with some knowledge. ive been scouring the web for at least a month. i was so happy when i came across this. i actually became a member just to post about this erroer (look up diabolus ae in the forum search field. my post is about 3 days old with a better pic of the screen message. i bought a galaxy s II but i want to give the lg to my son. please help or respond:cyclops:

diabolus ae said:
i used an app on the market to remove bloatware. i removed slacker and the app stated that after two reboots that everything would be fine and the app would be gone. after one reboot the phone has the same screen this gentlemans lady friend has. it looks like the app its looking for is no longer zip aligned properly. someone told me to rename a recovery image the error message to trick the bootloader into thinking the missing app is there. hes an app dev so i figured he knows whats what. ive tried everything the gentleman in this post said and more. hell i have two of these phones and rooted the other and made a backup of that phone and dragged the backup to an sd card and rebooted to see if any of the backed up system apks would trigger a successful reboot but to no avail. i have all the drivers i need and adb commands but nothing works because the phone doesnt stay connected to my pc long enough for anything. please reply with some knowledge. ive been scouring the web for at least a month. i was so happy when i came across this. i actually became a member just to post about this erroer (look up diabolus ae in the forum search field. my post is about 3 days old with a better pic of the screen message. i bought a galaxy s II but i want to give the lg to my son. please help or respond:cyclops:
Click to expand...
Click to collapse
Normally, if you want to flash a custom recovery through fastboot, people will tell you to run 2 commands:
fastboot flash recovery nameofimagefile.img
fastboot reboot recovery
Since you don't have time to execute those 2 commands, you can tell it to just boot from the .img file, without flashing over your current recovery. (This is actually proper form, as you can test if the .img file works properly without damaging your existing recovery.) The way you do that is to 1st copy a recovery .img file to the root of your SD card, then execute the following 1 command:
fastboot boot nameofimagefile.img
Since you only have ~3 seconds, type the command in, and wait for the right instant to hit enter on the keyboard. If the command is successfully sent to the phone, it will reboot into that .img.
See if that works for you. Good luck.

[Q] Dead touchscreen

Hello,
I am trying to fix my girlfriends HTC One S, she accidentally dropped it into the bathtub full of water, she picked it up fast, put it to rice so it sucks out the water and applied heat, the phone worked, but the touchscreen is totally unresponsive, is there any way how I could determine if the touchscreen is damaged, or the motherboard? I dont have anyone else around me who would give up their warranty and let me open theirs phone so I could test it. I already disassembled the phone, tried unplugging the connectors, checking if there is any visible water damage, but i got nothing, so either the panel or the motherboard must be damaged, I need some way to determine which one is it.
I will also add a conversation with Awesome, he was trying to help me at first and there are some more information.
The wet phone? I did reply. Is the phone rooted? If its not boot into the boot loader holding the volume down and power and click factory reset see if you get the touchscreen working again. If it doesn't work then you short circuit something but if it works and goes away then its your screen.
If your phone is rooted its gonna be hard to do factory reset.
Sent from my HTC One S using Tapatalk 2
Then I probably did not figure out the answer was for me
Well, the problem with that is, that there are some valuable photos inside and a factory reset would definitely remove them,
I was looking for a solution for backing them up, I got to a software, that can control the phone from PC without the need of being
installed in the phone, there was a slight problem since it required USB debugging to be turned on and it wasn't. So I was browsing
the internet to find out if it is possible to turn on USB debugging from PC, or perhaps somehow, until here on XDA in some thread
someone said it is impossible, so I gave up backing up the data and went straight for the repair, that is why I need somehow to find out
if either motherboard is damaged or digitizer, I have the phone totally disassembled. I am guessing that some touch controller on board is
damaged, since I cant see any visible damage to digitizer, but I am not sure and I do not want to buy wrong part.
Also the phone is not rooted and is using stock ROM.
Thank you
Yes without USB Debuggin its impossible to extract those files, and without u doing a factory reset I really can't think of doing or trying anything else to figure out what may be the problem. Since its water damage you really won't see if its short circuited. I'm more than sure you got a short circuit rather than needing a digitizer. Other than that feel free to open a new thread in the general section of the one s and asking there maybe other users will have other options for you.
Thank you for help.

Sapphire18 said:
Hello,
I am trying to fix my girlfriends HTC One S, she accidentally dropped it into the bathtub full of water, she picked it up fast, put it to rice so it sucks out the water and applied heat, the phone worked, but the touchscreen is totally unresponsive, is there any way how I could determine if the touchscreen is damaged, or the motherboard? I dont have anyone else around me who would give up their warranty and let me open theirs phone so I could test it. I already disassembled the phone, tried unplugging the connectors, checking if there is any visible water damage, but i got nothing, so either the panel or the motherboard must be damaged, I need some way to determine which one is it.
I will also add a conversation with Awesome, he was trying to help me at first and there are some more information.
The wet phone? I did reply. Is the phone rooted? If its not boot into the boot loader holding the volume down and power and click factory reset see if you get the touchscreen working again. If it doesn't work then you short circuit something but if it works and goes away then its your screen.
If your phone is rooted its gonna be hard to do factory reset.
Sent from my HTC One S using Tapatalk 2
Then I probably did not figure out the answer was for me
Well, the problem with that is, that there are some valuable photos inside and a factory reset would definitely remove them,
I was looking for a solution for backing them up, I got to a software, that can control the phone from PC without the need of being
installed in the phone, there was a slight problem since it required USB debugging to be turned on and it wasn't. So I was browsing
the internet to find out if it is possible to turn on USB debugging from PC, or perhaps somehow, until here on XDA in some thread
someone said it is impossible, so I gave up backing up the data and went straight for the repair, that is why I need somehow to find out
if either motherboard is damaged or digitizer, I have the phone totally disassembled. I am guessing that some touch controller on board is
damaged, since I cant see any visible damage to digitizer, but I am not sure and I do not want to buy wrong part.
Also the phone is not rooted and is using stock ROM.
Thank you
Yes without USB Debuggin its impossible to extract those files, and without u doing a factory reset I really can't think of doing or trying anything else to figure out what may be the problem. Since its water damage you really won't see if its short circuited. I'm more than sure you got a short circuit rather than needing a digitizer. Other than that feel free to open a new thread in the general section of the one s and asking there maybe other users will have other options for you.
Thank you for help.
Click to expand...
Click to collapse
Em so is the bootloader unlocked? you could try to see if adb is working in fastboot or if it is unlocked I think TWRP lets you use adb.

Well, its all in stock, so I guess the bootloader is locked, and without USB debugging turned on ADB doesn't recognize the phone.

Sapphire18 said:
Well, its all in stock, so I guess the bootloader is locked, and without USB debugging turned on ADB doesn't recognize the phone.
Click to expand...
Click to collapse
Ok but have you tried adb in fastboot?

adb in fastboot should work, regardless of the setting in the rom.
What android version is it running? If its running 4.1 you could use an OTG cable and hook up a mouse to control the device.

Goatshocker said:
adb in fastboot should work, regardless of the setting in the rom.
What android version is it running? If its running 4.1 you could use an OTG cable and hook up a mouse to control the device.
Click to expand...
Click to collapse
Omg so forgot you can use a mouse so going to do that now for no reason lol.

Darknites said:
Omg so forgot you can use a mouse so going to do that now for no reason lol.
Click to expand...
Click to collapse
Theres also an app that can share your kb/mouse to your android device, the device will see the kb/mouse as hardware plugged in.
ShareKM its called, works damn good on both my S and TF.

Goatshocker said:
Theres also an app that can share your kb/mouse to your android device, the device will see the kb/mouse as hardware plugged in.
ShareKM its called, works damn good on both my S and TF.
Click to expand...
Click to collapse
Cool think I have a play later.

Okay, here is what I got, the OTG cable is not working, that means the phone doesn't have Android 4.1.
The ShareKM application requires installation into the phone, meaning it is out of question too.
I am experimenting with this ADB in fastboot, but I am not really sure how that fastboot command works when I run ADB.exe trough command prompt and list devices, it show me only my other phone in USB debugging, when I run the fastboot.exe and type adb devices it says "waiting for the device", I do not really know how to work with this with a little guide, it shows me some commands there, i tried the one with rebooting into bootloader, but it still says only "waiting for device".
Could you give me a little guide perhaps link to guide what exactly I am supposed to do to run ADB in fastboot?
I am pretty technical type, dont need noobish explanation.
Thank you

Okay, I managed to get into fastboot, I always thought it is something with the fastboot.exe in SDK Platform-tools, well, anyway, I am inside, it says Fastboot USB, but adb still isnt showing the device in the list.
Also there is a big pink ***LOCKED***, that means that bootloader is locked I guess.
Any other ideas how I could backup the files? or any other suggestions?
Thank you

Moving slowly forward, I was being stupid and I was using the ADB command instead fastboot command, when I am in fastboot mode now, well, trough fastboot command now the PC recognizes the phone, altho what is the next step now?
Thanks again

Yeah, the ShareKM app was never really ment for you, it was more of a suggestion to dark sorry if it confused you.
I ran some quick tests, and yeah Im afraid adb is, in fact, not working in bootloader.
What happens if you boot into recovery? Maybe it works there?
What kind of things do you need to save? Is it just like pictures and stuff from the sdcard?
In that case, you could unlock the bootloader (this will wipe the device data, like applications etc) and install TWRP. Im 100% sure ADB works in TWRP without you needing to use the screen.

Just tried booting into recovery, the only thing I am receiving is big red exclamation mark, not sure what it means, I did some digging and it usually appears when someone is trying to do OTA update from custom ROM, strangely, this is original stock ROM.
One S doesn't posses SD card, it has 16Gb internal storage, but is probably divided into some system partition and data partition, if that is what you meant. Yes, it is only some photos and videos.
You said TWRP, as I did some background search, it says touch recovery, that kinda sounds it uses touch, and that is the one thing I can't use.
Or am I mistaken?

Sapphire18 said:
Just tried booting into recovery, the only thing I am receiving is big red exclamation mark, not sure what it means, I did some digging and it usually appears when someone is trying to do OTA update from custom ROM, strangely, this is original stock ROM.
One S doesn't posses SD card, it has 16Gb internal storage, but is probably divided into some system partition and data partition, if that is what you meant. Yes, it is only some photos and videos.
You said TWRP, as I did some background search, it says touch recovery, that kinda sounds it uses touch, and that is the one thing I can't use.
Or am I mistaken?
Click to expand...
Click to collapse
Right you say adb is see your phone now, download Quick ADB Pusher load it and see if you find the sd card if it does just copy over everything you want, it will need to be in pull mode for this.

Darknites said:
Right you say adb is see your phone now, download Quick ADB Pusher load it and see if you find the sd card if it does just copy over everything you want, it will need to be in pull mode for this.
Click to expand...
Click to collapse
It did not work, but I am going to describe everything I did: I started the phone, got into Bootloader, switched into fastboot and connected USB cable, then I started the Quick ADB pusher, switched into pull mode, opened ADB Explorer, but there I dont see anything, only "error: device not found".
Did I do anything wrong, or is it that the Quick ADB pusher doesn't work in fastboot?

Sapphire18 said:
It did not work, but I am going to describe everything I did: I started the phone, got into Bootloader, switched into fastboot and connected USB cable, then I started the Quick ADB pusher, switched into pull mode, opened ADB Explorer, but there I dont see anything, only "error: device not found".
Did I do anything wrong, or is it that the Quick ADB pusher doesn't work in fastboot?
Click to expand...
Click to collapse
Em did you try scan under select device?

Darknites said:
Em did you try scan under select device?
Click to expand...
Click to collapse
It shows me the phone there, under name SH27NW401121, but when I open the ADB explorer, there is only a folder named
"error: device not found" to me it looks like that Quick ADB pusher doesnt work in fastboot mode.

Sapphire18 said:
It shows me the phone there, under name SH27NW401121, but when I open the ADB explorer, there is only a folder named
"error: device not found" to me it looks like that Quick ADB pusher doesnt work in fastboot mode.
Click to expand...
Click to collapse
Then I'm out of ideas because unlocking the Bootloader will wipe the sd.

Indeed, Quick ADB is just a GUI front-end for adb commands. If adb doesnt work in a command line, Quick ADB wont work either.
Theres nothing I can do about that, its not like I can magically force your device into accepting adb commands.
Unlocking the bootloader wont wipe the SD... At least, it didnt for me (just the /Android/ folder).
Things like pictures taken and custom ringtones were still present after the unlocking.
So, ADB doesnt work when youre in recovery either? (the big red exclamation mark)

Goatshocker said:
Indeed, Quick ADB is just a GUI front-end for adb commands. If adb doesnt work in a command line, Quick ADB wont work either.
Theres nothing I can do about that, its not like I can magically force your device into accepting adb commands.
Unlocking the bootloader wont wipe the SD... At least, it didnt for me (just the /Android/ folder).
Things like pictures taken and custom ringtones were still present after the unlocking.
So, ADB doesnt work when youre in recovery either? (the big red exclamation mark)
Click to expand...
Click to collapse
And I am not throwing any blame either, I am just open to every solution
How would unlocking the bootloader help me? so I could put that TWRP inside and do some magic with it?
For the recovery part, I am not really sure how it is supposed to work, but every picture I googled shows some text
along with the exclamation mark, but the only thing I am getting is exclamation mark, and after a while the phone reboots.
I am guessing the recovery either wont load up, or something is wrong, should I try running ADB while that exclamation mark is shown?

Softbricked my nexus 5? Any help?

So i'm not super competent in adb and what not, but just competent to use wuggs toolkit. I went to google's website to download lollipop 5.0 for my nexus 5. Then i set the phone back to stock, flash 5.0 and its running well. Then i go back in to settings, developer options, and to root my nexus 5 and install TWRP on it through wuggs. Now it has twrp, but will not boot up past the google name with the unlock. I only have the fastboot page and TWRP. The big kicker here is that my pc says does not recognize device and it flickers back and forth with connection every two seconds to my PC. When i go into device manager it shows android device though. So well hey i figure since i have a softbricked nexus i'll just click the button for it and reset. Well it wont do it, it pulls up fastboot.exe goes through a few commands, some saying it failed then it stops and windows tells me to close fastboot.exe
Any help from the very respected XDA?

oh, gawd.. fastbooting a factory img would have been so much faster. sorry, toolkit, i cant help you with it.

hayden55 said:
So i'm not super competent in adb
Click to expand...
Click to collapse
There's your answer right there. That's how ppl like Op brick their devices everyday

Do some research, read read and lastly Read
If you can adb the factory image you can adb a recovery. Google how to. Its literally one comand line.
Stop tossing the word bricked around, a brick is a phone that doesn't turn on and don't blame other things if you don't know how to use them.
Google is your best friend. No one is going to hold your hand.

jayRokk said:
Do some research, read read and lastly Read
If you can adb the factory image you can adb a recovery. Google how to. Its literally one comand line.
Stop tossing the word bricked around, a brick is a phone that doesn't turn on and don't blame other things if you don't know how to use them.
Google is your best friend. No one is going to hold your hand.
Click to expand...
Click to collapse
aww but i really wanted a hand hold.

hayden55 said:
aww but i really wanted a hand hold.
Click to expand...
Click to collapse
here is an extra long :highfive: for your hand holding

chapelfreak said:
here is an extra long :highfive: for your hand holding
Click to expand...
Click to collapse
Hey thanks bud! Problem was it couldnt connect to the computer for more than 5 seconds...
SOO.... i messed with mounting an OTG jump drive and it had my old TWRP back with android 4.4.4. IT Worked!
p.s. i tried just mounting system data etc... the turn on mtp connection button and it Would show up better than just plugging in but couldnt download anything big. and no adb connection

dicecuber said:
There's your answer right there. That's how ppl like Op brick their devices everyday
Click to expand...
Click to collapse
i do not need your input if you aren't going to contribute to the problem just antagonize the op

Current problem at hand: phone now will only connect to pc for 5 seconds at a time. What could do this and how do I reflash to normal?

Still using toolkits?

hayden55 said:
i do not need your input if you aren't going to contribute to the problem just antagonize the op
Click to expand...
Click to collapse
It's a suggestion

Disclaimer: I use OS X/Terminal to fix these things normally and honestly found that after the initial learning curve, it's easier than using Windows or Wugfresh. I'm not a developer, just a hobbyist user.
Make sure you're using an OEM cable to connect to the computer if you're getting dropouts. Also, attempt to uninstall and reinstall OEM drivers (I believe Wugfresh has instructions on how to do this) for Windows.
If you have confirmed that you have TWRP 2.8.1.0 installed, try to boot to TWRP --> ADB Sideload. Connect phone to computer, open Terminal/Console and type the command 'adb devices' (without the apostrophes. I haven't used Windows since I stop using Wugfresh, so the command probably differs). If the device can be seen through this, you should be able to return to the bootloader and start issuing fastboot commands to flash the image.
Let me know how I can help!

OP7 Pro Fastboot Bootloop! [HELP]

This may be a simple solution, but I am completely puzzled on how to fix this.
SO i recently rooted my phone & used the twrp "twrp-3.3.1-4-guacamole". Installed magisk via that twrp and continued with my day.
I accidentally got a virus by trying to get a full free vpn, me being a terrible pirate, i accidentally got a virus! Silly me.
It was annoying me and I decided to factory reset my phone... not via twrp. I remembered after I clicked "Reset all" on oxygenos that it's not the way how to do it with a root device, and well.. it didn't exactly work.
Every time I power/reboot the phone it just brings me to the fastboot menu of "START", "POWER OFF", "RECOVERY MODE", & "RESTART BOOT LOADER". I thought since TWP is recovery mode I try to access that... no luck, it just brings me back to that fastboot menu. I tried going on CMD via adb by saying "fastboot flash boot twrp-3.3.1-4-guacamole.img". It will say it's finished and successful, but when i reboot and try to access recovery mode it just does not work.
TL;DR: Think I bricked my phone, there is no OS installed and I can only access the fastboot.
Any help? Much appreciated

https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691

trapcoder666 said:
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
Click to expand...
Click to collapse
Thank you for the guap recovery as i didn't know it existed. However, what are the steps? when i go on the MSM download tool it doesn't detect my phone.
that being said, i can't access any of my files through my pc using fast boot. on MSM it's just saying "waiting for device" even when plugged in so thats annoying.

trapcoder666 said:
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
Click to expand...
Click to collapse
I downloaded the one you sent, and after a while as my internet is bad. It still does not work.
Whenever I try to install the qualcomm drivers it never shows up, and when i try and boot it up so the gual recover detects my phone it never works. It's still saying "waiting for device".
Does anyone know how to fix this? it's doing my head in that it's not as easy as it should be.

MOweenSalah said:
I downloaded the one you sent, and after a while as my internet is bad. It still does not work.
Whenever I try to install the qualcomm drivers it never shows up, and when i try and boot it up so the gual recover detects my phone it never works. It's still saying "waiting for device".
Does anyone know how to fix this? it's doing my head in that it's not as easy as it should be.
Click to expand...
Click to collapse
Pretty sure that your phone will not be accessible via adb/fastboot during the msm process. Did you follow the directions in the link above to a T?
A few things to note:
- Works perfectly fine for unbricking GM1917 modeled OnePlus 7 Pros.
- Use the original cable and try to plug it into a USB 2.0 port. I've found that this is the most ideal condition.
- Make sure your device is charged up. If you can't see how much charge it has, leave it charged via the 30W warp charger for 40 minutes and that should be good enough.
- In the L2 drivers folder found in the archive, navigate to the 32 or 64 folder depending on your system's architecture, and click on the file that ends in the extension ".cat". Then, click "view signature", then "View certificate", then "Install." This is IMPORTANT.
- Then, make sure your device is powered OFF, then, plug in the USB-A side of the cable (big head) into your computer and do NOT connect the USB-C (small head) into your phone yet.
- Hold down Volume up AND volume down for five seconds, and while you're continuing to hold, plug the USB-C side into your phone. The drivers should automatically download, and you should see a "Qualcomm QD loader" device in Device Manager. If you see an exclamation mark or you don't see this, you are doing it wrong and you need to repeat the above steps.
- Open up MSMTool.exe as an administrator and click 'start' only. Should take a few minutes, but you will have a good-as-new OnePlus 7 Pro.
Click to expand...
Click to collapse

Krsmqn said:
Pretty sure that your phone will not be accessible via adb/fastboot during the msm process. Did you follow the directions in the link above to a T?
Click to expand...
Click to collapse
I did yes, i pressed all buttons and the power button for 5 seconds and plugged my charger in. Then after that went on the MSM tool and it went straight to the fastboot. I really don't know but it loves this fastboot tool haha

Krsmqn said:
Pretty sure that your phone will not be accessible via adb/fastboot during the msm process. Did you follow the directions in the link above to a T?
Click to expand...
Click to collapse
Add: I made a video showing what I mean with the fastboot. Basically if i do anything with the phone fastboot it will just go back to the menu (sorry for bad quality)
https://www.youtube.com/watch?v=jU8a6kDXNNs&feature=youtu.be

MOweenSalah said:
Add: I made a video showing what I mean with the fastboot. Basically if i do anything with the phone fastboot it will just go back to the menu (sorry for bad quality)
&feature=youtu.be
Click to expand...
Click to collapse
It's one of those things where if someone was there with you, it'd likely get figured out. I've seen this kind of situation hundreds of times on XDA, and with all due respect, the problem is most always at the hands of the user. These phones are cookie cutter made, so there's nothing different (besides individual variants) that would make thee tools not function correctly, unless it's operator error. But that's not set in stone. Just don't give up. Try setting up your camera for an overhead view. I couldn't tell if you were plugging in your cord. And it seemed to reboot, instead of power off. Repeat the steps carefully, and see if you can achieve better results.
Don't give up! We're here for you ?

Make sure phone is powered off before plugging it in. Launch msm tool, Press the vol up and down key for a few seconds then plug in.
Edit : make sure your drivers are up to date too.

I don't know about msm tools never tried it but I know your situation.
Don't do fastboot flash boot twrp-3.3.1-4-guacamole.img
Remove the word flash. You are supposed to boot into twrp then flash the zip file to the phone.
look at this

Command in Fastboot mode is:
Fastboot boot "name of the recovery".img. Phone should boot to twrp. Then flash twrp.zip
or try Fastboot roms:
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Choose the one for youre phone (region)
MSM tool it's the last option.

Can't you just switch slots from fastboot or did you mess up both?

trapcoder666 said:
Make sure phone is powered off before plugging it in. Launch msm tool, Press the vol up and down key for a few seconds then plug in.
Edit : make sure your drivers are up to date too.
Click to expand...
Click to collapse
Firstly I'm terribly sorry for no response (same goes to everyone else looking into this matter for me. THANK YOU!)
However, I have done this multiple times in the past and it instantly goes back to boot menu. it sucks :/

IronSingh said:
I don't know about msm tools never tried it but I know your situation.
Don't do fastboot flash boot twrp-3.3.1-4-guacamole.img
Remove the word flash. You are supposed to boot into twrp then flash the zip file to the phone.
look at this
Click to expand...
Click to collapse
Okay. I shall go and look into this situation when I receive my phone back (going to explain that in a later quote)

larsdennert said:
Can't you just switch slots from fastboot or did you mess up both?
Click to expand...
Click to collapse
If i'm honest with you.. i'm not sure in the slightest. My only assumption is no because the only thing I can access is only the fastboot. if i attempt to go into recovery mode it will go back to fastboot. when I flash twrp it will flash but it won't boot into it. It's confusing as hell.
Just to add to this whole situation:
Since I have no idea and just wanted it fixed in the day; i was willingly to give money for this phone to be fixed, but thanks to the person, he just made it a slower process by doing things i've already done.. going to pick the phone back up in an hour of this message.
I haven't used the fastboot boot twrp cmd yet, but from how everything else has been so far i feel like that won't work, but i will update everyone on that situation.
Just to add additional things that I may have not mentioned in the past will be below:
- Whenever i type in "ADB Devices" in cmd, it will not show up with anything. However, when I type in "fastboot devices" it shows it's serial and in "fastboot". It will only show as fastboot and i can't access the phone via file explorer in windows.
When i say "ADB Devices" it says *devices attached* and will show none of my phones details, but when i say fastboot devices it will then show the devices.
^ what i said above means I can't use the guap recover, or anything which means the phone has to be detected in windows, because other than fastboot, it won't work at all.
- So far I can't access twrp as a whole, so if anyone knows how to give me a guide on how to install it from where I am at, that would be amazing (if not, i'll try and reiterate what to do with the one given from a previous comment, so thank you )
- There was one time I was allowed in TWRP but i completely forgot how i entered it (so i can't explain), So i feel like there is hope in that aspect. I feel like i entered something via cmd so maybe there's a way?
In terms of hardware my phone is completely fine, there's not a single problem other than the software being a pain in the ***!!
if anyone can just spew out a bunch of help in different explanations it means the world because so far all I can see is that I wasted about £600 on an amazing phone because of dumb *** haha.
Thank you to everyone who has helped, and is helping

From your comments, you are not familiar with how Android functions. Not knowing the difference between adb and fastboot is an indicator that you should just endeavour to have a stock phone until you understand whats going one. It's also hard for people to help as no one has hands on and can see what is broken. Everyone here will be working blind like trying to fix your car for you from across the country.
Start the phone into fastboot and connect it to a pc. From a pc command prompt in your fastboot directory enter the command:
fastboot getvar current-slot
If the current slot is A then:
fastboot --set_active=b
or vice versa
fastboot --set_active=a
then fastboot reboot and see if you boot into the other slot.
Not knowing what phone you have makes it even tougher but I suspect you will have to reflash a clean complete rom via fastboot.
https://forum.xda-developers.com/on...fastboot-roms-oneplus-7-pro-t3931424#poststop

larsdennert said:
From your comments, you are not familiar with how Android functions. Not knowing the difference between adb and fastboot is an indicator that you should just endeavour to have a stock phone until you understand whats going one. It's also hard for people to help as no one has hands on and can see what is broken. Everyone here will be working blind like trying to fix your car for you from across the country.
Start the phone into fastboot and connect it to a pc. From a pc command prompt in your fastboot directory enter the command:
fastboot getvar current-slot
If the current slot is A then:
fastboot --set_active=b
or vice versa
fastboot --set_active=a
then fastboot reboot and see if you boot into the other slot.
Not knowing what phone you have makes it even tougher but I suspect you will have to reflash a clean complete rom via fastboot.
https://forum.xda-developers.com/on...fastboot-roms-oneplus-7-pro-t3931424#poststop
Click to expand...
Click to collapse
I do appreciate the help. If i'm honest with you the only reason I did this is to increase my data speeds (which from look of things is outdated now), and a longer battery life. I don't know much about rooting/jailbreaking but believe me that I have been in the scene for years, but not even knowing everything haha!
that being said.. i'm in twrp! thank you so much mate, i'll try and go and install the rom now. thank you!

Now install the zip twrp

Thankfully.. IT'S FIXED!
I didn't have to install twrp again or any of that. I simply changed the slot from A to B and pressed all buttons when it was showing the "! Your decide is unlocked" orange/black screen.
I had msm tools up and it detected and instantly installed the OS to the latest one and boom. It works again!
I got to thank everyone for helping me because without you people I wouldn't of been able to fix it. I looked everywhere and no help anywhere as I feel like it's pretty dumb to do what I did haha!
Thank you again people!

Oh you gave up on root?
You are supposed to read the instructions and follow them to the letter. When I read your post I realized you tried to install twrp like you would pre Oreo but it changed you have to boot into twrp then install it via zip file.
Anyways just remember that for next time.