Database Users

[Q] Nexus 10 Bricked :/

Hey,
I need some help with my Nexus 10, it's stuck at the moment.
I ran fastboot oem unlock via the Samsung Google Nexus 10 ToolKit 1.3.0 (updated for 4.2.2) and as soon as it was done it rebooted and was stuck...
Booting normally it gets to the bootlogo and just sits there forever, going round and round and round.
If I try to boot into fastboot it shows that it's unlocked but I can't change change to recovery using the volume rocker it's just a solid static screen, only choice is to start which boots back into the normal boot logo.
I have no way to use adb or fastboot... it's just stuck :/ How do I recover/unbrick this?
Any help would be much appreciated.

Hyflex said:
Hey,
I need some help with my Nexus 10, it's stuck at the moment.
I ran fastboot oem unlock via the Samsung Google Nexus 10 ToolKit 1.3.0 (updated for 4.2.2) and as soon as it was done it rebooted and was stuck...
Booting normally it gets to the bootlogo and just sits there forever, going round and round and round.
If I try to boot into fastboot it shows that it's unlocked but I can't change change to recovery using the volume rocker it's just a solid static screen, only choice is to start which boots back into the normal boot logo.
I have no way to use adb or fastboot... it's just stuck :/ How do I recover/unbrick this?
Any help would be much appreciated.
Click to expand...
Click to collapse
Reboot holding Power and both volume buttons and you should be able to get to recovery

brees75 said:
Reboot holding Power and both volume buttons and you should be able to get to recovery
Click to expand...
Click to collapse
I'm on the xda-devs irc at the moment and we've got so far... but still its messed up.
- Recovery is dead (can't get into it atm, orange triangle guy every time)
- Flashed stock via fastboot and unrooted, but on reboot I get the triangle guy.
- I can boot into unsecure roms (temporary)
- I can boot into temporary recoverys, clearing cache works but davlik cache and factory reset doesn't work both say "failed"
I'm currently awaiting the guy whos been helping me get back from the shops.

From what I remember you need to either install something or run a command after "oem unlock" for security reasons. Android wont let you boot back into the OS until you have wiped all the data after the unlock.

The orange guy means it's working. There's a button combo to hit at that screen to get the recovery to boot. Once there do a factory reset and your done.
That's why toolkits sick, they teach you nothing and when they break your stuck
Sent from my Nexus 10 using Tapatalk HD

Can you flash a factory image to it via fastboot?
Rock Chalk Jayhawk!

altimax98 said:
The orange guy means it's working. There's a button combo to hit at that screen to get the recovery to boot. Once there do a factory reset and your done.
That's why toolkits sick, they teach you nothing and when they break your stuck
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
The pressing 3 buttons at once; cycling to recovery... method wasnt working because there was no recovery accessable what so ever and temporary recoveries weren't working.
That's what a few guys in IRC said too about the toolkits haha
Thankfully some guy by the name of YellowGTO spent some time helping me out and we finally got there in the end, he's awesome and extremely patient
jlvlawrence said:
Can you flash a factory image to it via fastboot?
Rock Chalk Jayhawk!
Click to expand...
Click to collapse
Okay, updates for everyone just incase someone else gets the problem.
- Factory Images via fastboot flashed fine but never stuck, just kept returning me to triangle dude.
- Fix permissions, did nothing
- Restoring stock recovery did nothing, I still couldn't get to a recovery.
- Temporary recoveries only had limited functionality.
I decided to unlock an already unlocked phone again
I flashed stock, Ran file permissions
Used the temporary recovery to clear the cache/davlik (previously didn't work)
I re-rooted, Installed TWRP 2.4.4.0, this finally stuck.
I double checked that it had stuck by booting the system, rebooting into recovery, powering device of and powering it on to Android. It was all working perfectly.
I then made my backup and put a custom rom and kernel on, it's working lovely now.
It seems that somewhere during the oem unlock it messed up some partitions or something resulting in recoveries and flashing not to work/stick.

Good to hear it's working for you. The issue is that the stock N10 bootloader does not wipe the data partitions correctly as it should. So after an unlock you need to go into the stock recovery and wipe it. Boot once, then go and flash all your flasheys
Sent from my Nexus 10 using Tapatalk HD

altimax98 said:
Good to hear it's working for you. The issue is that the stock N10 bootloader does not wipe the data partitions correctly as it should. So after an unlock you need to go into the stock recovery and wipe it. Boot once, then go and flash all your flasheys
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
That's the thing, the recovery wasn't available in any way shape or form and temporary recoveries wouldn't wipe the cache... the oem unlock went wrong somehow even though it had full power, wasn't interrupted or anything.
I'm glad it's all working now, I thought the device was completely dead at one stage.

I think you had the problem almost everyone runs into:
As you can see in the video, you just have to try for a bit to actually get the recovery menu to open - My heart dropped a little before I knew that as well

anazei said:
I think you had the problem almost everyone runs into:
As you can see in the video, you just have to try for a bit to actually get the recovery menu to open - My heart dropped a little before I knew that as well
Click to expand...
Click to collapse
I think you are right and that was his problem..... The toolkit actually told him how to handle this ... but who reads all the that text anyway

[Q] Stock Nexus 4 bad install of 4.3 OTA

Hello, I tried searching for this but came up empty. I have a completely stock Nexus 4, received the OTA push for 4.3. Phone has never been rooted. After going through the install process it showed the android on it's back with a red triangle and said error. After a restart the phone just sits at the Google screen!!! I'm I boned or is there a fix for this? Any info would be greatly appreciated! Thank you!

Jesmuris said:
Hello, I tried searching for this but came up empty. I have a completely stock Nexus 4, received the OTA push for 4.3. Phone has never been rooted. After going through the install process it showed the android on it's back with a red triangle and said error. After a restart the phone just sits at the Google screen!!! I'm I boned or is there a fix for this? Any info would be greatly appreciated! Thank you!
Click to expand...
Click to collapse
Try going into fastboot and flashing the stock rom from google.

gmaxpwnage said:
Try going into fastboot and flashing the stock rom from google.
Click to expand...
Click to collapse
Not sure what mode I entered, Held vlm down + power. Says Fastboot Mode in red with a big green Start at the top. Options it gives me is Start, restart bootloader, recovery mode, and power off. If I try to enter Recovery mode it says no command. Don't see anything that allows me to reinstall

Jesmuris said:
Not sure what mode I entered, Held vlm down + power. Says Fastboot Mode in red with a big green Start at the top. Options it gives me is Start, restart bootloader, recovery mode, and power off. If I try to enter Recovery mode it says no command. Don't see anything that allows me to reinstall
Click to expand...
Click to collapse
Ok, found out on the no command screen I can hold power and hit vlm up and it brings me to system recovery with these options. Reboot system, apply update from ADB, wipe data/factory reset, wipe cache partition.
Not sure what to do sadly

Try following step:
1. Press Vol up and down and powerbutton same time to get to the fastboot mode as you mention.
2. Choice Recovery Mode and press power button. If you got luck you will see an android guy with red mark on the screen.
3. Press Vol Up and Power button same time for while don't let go it will pop up a list of option clean the cache and do factory reset, then reboot system.
If this method not working. Then hard method is flash your Nexus 4 with fastboot. Search the forum there few people already post how to flash 4.3 ROM with fastboot

Johnsonyc said:
Try following step:
1. Press Vol up and down and powerbutton same time to get to the fastboot mode as you mention.
2. Choice Recovery Mode and press power button. If you got luck you will see an android guy with red mark on the screen.
3. Press Vol Up and Power button same time for while don't let go it will pop up a list of option clean the cache and do factory reset, then reboot system.
If this method not working. Then hard method is flash your Nexus 4 with fastboot. Search the forum there few people already post how to flash 4.3 ROM with fastboot
Click to expand...
Click to collapse
Ok thank you, trying this now will update:good:

Didn't work Will try other method

Jesmuris said:
Didn't work Will try other method
Click to expand...
Click to collapse
Sorry to hear this bad news Hope the other method work for you!

Well, first try, couldn't get my PC to recognize fastboot in adb. Was getting frustrated beyond hell and had to walk away for a bit. Came back about an hour later and for some reason it finally recognized it... Back to the start screen like when I first bought the phone. So far working ok, except for being able to log into my google account... 2-step verification giving me issues now lol. Thank you again for your assistance. Very much appreciated!!:good::good:

Jesmuris said:
Well, first try, couldn't get my PC to recognize fastboot in adb. Was getting frustrated beyond hell and had to walk away for a bit. Came back about an hour later and for some reason it finally recognized it... Back to the start screen like when I first bought the phone. So far working ok, except for being able to log into my google account... 2-step verification giving me issues now lol. Thank you again for your assistance. Very much appreciated!!:good::good:
Click to expand...
Click to collapse
I had a similar experience (kind of). I had issues side-loading 4.2.2 -> 4.3 on my N4. After it finished update and rebooted I got a black screen and nothing more. I ran through it and tried to update to 4.3 again, and then it worked.
Even though it worked I've been noticing issues with it. For example, I now can no longer uninstall anything. When I attempt to uninstall any app, the phone reboots. I'm backing up now with Titanium and am about to flash. I was hoping there would be a quick fix here, but such is life. Viva la impatience.

I have same problem my stock 4.2.2 stuck x boot load , did vol up+dwn +power now stuck in "Download Mode" do not unplug the device until the process is complete .

oneguy77 said:
I have same problem my stock 4.2.2 stuck x boot load , did vol up+dwn +power now stuck in "Download Mode" do not unplug the device until the process is complete .
Click to expand...
Click to collapse
This is what I eventually followed to get mine working. I just did scenario 2 and that worked perfectly for me, so far no issues, just having to get things back to where I had them before. The second link is actually more detailed. Just make sure you follow step by step. I guess i could have not done step D10 but wanted to make sure this route worked for me. Thank you again for those who pointed me in the right direction
http://www.androidpolice.com/2013/0...-to-android-4-3-jwr66v-and-root-it-right-now/
http://forum.xda-developers.com/showpost.php?p=34552123&postcount=1

Jesmuris said:
Well, first try, couldn't get my PC to recognize fastboot in adb. Was getting frustrated beyond hell and had to walk away for a bit. Came back about an hour later and for some reason it finally recognized it... Back to the start screen like when I first bought the phone. So far working ok, except for being able to log into my google account... 2-step verification giving me issues now lol. Thank you again for your assistance. Very much appreciated!!:good::good:
Click to expand...
Click to collapse
I have the exact same problem but not sure how to get my PC to recognize fastboot in adb mode...

FYI if you flash to stock android 4.3 and you have the 16 GB Nexus 4, make sure that after you re-flash you have the full 16 GB and not 8 GB (unless you want to re-setup your phone twice like me). If you get this problem you can wipe cache and data from recovery and voila, all of your free space is back.
---------- Post added at 10:52 PM ---------- Previous post was at 10:44 PM ----------
zpilot said:
I have the exact same problem but not sure how to get my PC to recognize fastboot in adb mode...
Click to expand...
Click to collapse
If this is what I think it is, I was having the same problem. If I went into Control Panel on my PC and it would say that the driver is failing to load. To fix this I uninstalled the driver, rebooted, reinstalled Google USB Driver from the Android SDK Manager, restarted, and all was well after that.
I really have no explanation for why this fixed it, or it didn't work before, because other than fastboot, everything was working flawlessly with getting my phone to communicate with my PC.

[q] lg g2 major problem help

HI ALL
MY phone has a major problem. I rooted the phone and also installed twrp 2.6.3.3 onit and installed custom rom, Now everything has gone after reboot.
I ONLY CAN TURN ON PHONE AND GOES STRAIGHT INTO BLACK FASTBOOT SCREEN , THERE IS NO TWRP RECOVERY AND CAN GET INTO FIRMWARE UPDTAE BY USB PLUS VOL +. BUT WILL NOT INSTALL ANYTHING , ON FIRMWARE SCREEN STATES ROOTED, BUT I ONLY HAVE FASTBOOT SCREEN OR FIRMWARE UPDATE,
ANYIDEA HOW I CAN FIX THIS ISSUE .

adb
Lord Kelly said:
HI ALL
MY phone has a major problem. I rooted the phone and also installed twrp 2.6.3.3 onit and installed custom rom, Now everything has gone after reboot.
I ONLY CAN TURN ON PHONE AND GOES STRAIGHT INTO BLACK FASTBOOT SCREEN , THERE IS NO TWRP RECOVERY AND CAN GET INTO FIRMWARE UPDTAE BY USB PLUS VOL +. BUT WILL NOT INSTALL ANYTHING , ON FIRMWARE SCREEN STATES ROOTED, BUT I ONLY HAVE FASTBOOT SCREEN OR FIRMWARE UPDATE,
ANYIDEA HOW I CAN FIX THIS ISSUE .
Click to expand...
Click to collapse
I had the same issue. I believe it was a bad MD5. Although I know you can adb command from a PC, I had just recently deleted all of my drivers to get into a couple of nexus 7's.keep trying the volume down and power key the correlation seems to be if you can hit it right as it boots. I made it back to the factory data reset screen hit power through and dropped into TWRP.
I'm not sure how much you know or if you've ever had to boot through the factory reset screen but it does NOT actually reset your device rather is the push to your recovery.
Good luck,

Mikkey81 said:
I had the same issue. I believe it was a bad MD5. Although I know you can adb command from a PC, I had just recently deleted all of my drivers to get into a couple of nexus 7's.keep trying the volume down and power key the correlation seems to be if you can hit it right as it boots. I made it back to the factory data reset screen hit power through and dropped into TWRP.
I'm not sure how much you know or if you've ever had to boot through the factory reset screen but it does NOT actually reset your device rather is the push to your recovery.
Good luck,
Click to expand...
Click to collapse
I have done that sevral times now before it did go into that recovery twrp but not when I do it it goes into fastboot everytime , its like it has wiped twrp off the phone and no recovery , even used fastboot on pc to boot into it and it wont just goes back to fast bootscreen

you should be able to still get recovery -switch off phone,press vol down and power button at the same time as soon as you see the lg logo press the same combination again and hopefully it will go to a white screen with factory reset press the button I think 3 times and it will take you thru to twrp it may take a few tries but if u get the combo right it will work -if not you may have to go to the thread in xda g2 forum and im afraid learn how to restore your phone to factory state again which is a pain in the a**e but make sure you have all the necessary drivers installed as that will not work properly either-hopefully you can get back into recovery and restore your back up-good luck!

Bootloop?

My Nexus 10 has been acting up recently...the battery seemed to be draining A LOT quicker then it normally would.....the tablet would just shutdown in the middle of doing something. Fast forward a week or two, now when I turn it on it vibrates for a second, shows the "GOOGLE" logo and starts the boot animation for 4.4, vibrates and repeats the same. I manually formatted and flashed 4.4 (fastboot flash boot ...etc...) and still am getting the same issues...Any suggestions on what to try next?

Flash the newest factory image automatically via fastboot.
Sent from my Galaxy Nexus using XDA Free mobile app

Just did that to no avail....same issue as before...Anything else to try?
It almost seems like it is not charging but I would assume I could still get it to boot up while connected to the charger....correct?

Update....I flashed CWM and sideloaded gapps and a ROM...and tried that...still the result..."GOOGLE" logo comes up and then a vibration...then it goes back to "charging" (the white battery with the lightning bolt through it)

Nobody has anything? Damn...lol

cirenj said:
Nobody has anything? Damn...lol
Click to expand...
Click to collapse
Sounds like it may be a hardware issue, since flashing the factory image didn't even help. I would say trying flashing the factory image using the flash-all method, and wiping data/factory reset right after. Couldn't hurt.

cirenj said:
Nobody has anything? Damn...lol
Click to expand...
Click to collapse
You said you installed cwm -- I assume you mean the recovery rom... If I'm wrong ignore the rest.
I too have had this issue and it was not hardware. To fix this I booted into cwm (the recovery rom I use on my N10) and reinstalled a stock factory boot rom. Just for those that don't know to boot into the recovery rom, power off the tablet, then press and hold the power, volume up AND volume down simultaneously --- finally, use the volume button to scroll to the recovery menu.
uDude

texascwby1836 said:
You said you installed cwm -- I assume you mean the recovery rom... If I'm wrong ignore the rest.
I too have had this issue and it was not hardware. To fix this I booted into cwm (the recovery rom I use on my N10) and reinstalled a stock factory boot rom. Just for those that don't know to boot into the recovery rom, power off the tablet, then press and hold the power, volume up AND volume down simultaneously --- finally, use the volume button to scroll to the recovery menu.
uDude
Click to expand...
Click to collapse
I have tried that as well...I am thinking it is a hardware issue as previously stated....amazing...spend $500 for a piece of hardware only to have it die a little over 12 months later....talk about pissed off....

cirenj said:
I have tried that as well...I am thinking it is a hardware issue as previously stated....amazing...spend $500 for a piece of hardware only to have it die a little over 12 months later....talk about pissed off....
Click to expand...
Click to collapse
No shoot me a PM ..
Lets see if we can get you up and running again ..
If we do we can post what we did back here from all XDA users ..
Thx Josh

I am having the same exact issues. I too force flashed stock 4.4.4 and it still does not boot up. Any ideas on how to remedy this would be greatly appreciated.
Thank you!

Hoping to hear something as well...but doesn't look good...

Can you access adb? To check logcat while it's booting (and possibly find out why it's bootlooping)?
What did you use to format the partitions?
Sent from my Nexus 10 using Tapatalk

I can access adb on my laptop...and I used the "fastboot format" and "fastboot flash"
How would I check the logcat file?

http://forum.xda-developers.com/showthread.php?t=2274119

beekay201 said:
Can you access adb? To check logcat while it's booting (and possibly find out why it's bootlooping)?
What did you use to format the partitions?
Sent from my Nexus 10 using Tapatalk
Click to expand...
Click to collapse
I am unable to get my Nexus to show up in command prompt when I run "adb devices". Not sure what to do.

Any ideas? I've tried reflashing stock images and still have the same problems..

michaelearth said:
Any ideas? I've tried reflashing stock images and still have the same problems..
Click to expand...
Click to collapse
Can you give more details about your issue? If its still about not connecting PC and tablet see this guide for help
http://forum.xda-developers.com/showthread.php?t=2277112

demkantor said:
Can you give more details about your issue? If its still about not connecting PC and tablet see this guide for help
http://forum.xda-developers.com/showthread.php?t=2277112
Click to expand...
Click to collapse
The problem is that my tablet will reboot constantly and it shows my battery being fully drained even after charging it overnight. I'm able to force flash stock images to my tablet and this has not fixed the issue. So at the moment my nexus 10 is an expensive paperweight.

What happens when booted to bootloader or recovery? Does it act normal or loop?

demkantor said:
What happens when booted to bootloader or recovery? Does it act normal or loop?
Click to expand...
Click to collapse
When I boot into the bootloader it acts normal.

[SOLVED] Bootloop. No recovery. Bootloader locked.

================================
Solution: http://forum.xda-developers.com/one...bootloader-locked-t3212187/page2#post63494201
================================
Hello,
This afternoon, I was preparing to flash Oxygen OS 2.1 through twrp but I wanted to make a backup first. Attempting to load up twrp by holding Vol- and Power, my OPT flashed the starting frame of the boot animation for half a second before turning off. This repeated every 5 seconds. I could still boot OOS normally at this stage.
I decided to reflash twrp so as to make the backups, but on attempting to flash it, I saw that my bootloader was locked. So into fastboot mode I went, but trying to unlock it, it did the same as trying to get into recovery. As soon as I sent the command, "fastboot oem unlock", the screen went dark, flashed the starting frame for the boot animation, and promptly when dark again.
I now can't boot up normally, nor can I enter recovery. I can access fastboot mode, but I can't seem to make any changes.
I've attempted to use this solution as well as several other similar ones with no success.
I've had my OPT since 17th of August with absolutely no signs of trouble until this afternoon.
To me, it seems like it could be a hardware issue, but I'd hope it would last more than 40 days.
Any suggestions?
Thanks.
----
x-post: whirlpool, reddit

The same just happened to me, wtf

Makrilli said:
The same just happened to me, wtf
Click to expand...
Click to collapse
What were you doing before it occurred? Perhaps we can work out the cause.

GusGold said:
What were you doing before it occurred? Perhaps we can work out the cause.
Click to expand...
Click to collapse
I'm not sure what I was doing, I was going to flash different ak kernel as my wifi didn't work.
HOWEVER
I read someone suggesting if you still have bootloop after trying the qualcomm recovery tool, try booting to fastboot and use: fastboot continue
my opt booted nicely to hydrogen os and after I shut it down it no longer bootlooped and I was able to get to recovery.
I'll post this to your reddit thread too, maybe it might help somebody one day, hopefully this works for you too

Makrilli said:
use: fastboot continue
Click to expand...
Click to collapse
Mate! that worked for me too!
However... It only seems to skip the bootloop for that power on. After power off, it returns to the boot loop. I also still can't unlock the bootloader and can't access recovery.
But at least it can boot into OS with fastboot continue!
Thank you.

Weird, after the first successful boot I rebooted and a chinese menu prompted me if I wanted to unlock the bootloader, and I did.
Maybe you should try different recovery packages.
But I'm glad to hear you at least got past the boot loop

Makrilli said:
Maybe you should try different recovery packages.
Click to expand...
Click to collapse
Can't flash a new one since the bootloader won't unlock :/
I guess the phone is in working order at the moment, I just can't let it get turned off without my computer next to me...

GusGold said:
Can't flash a new one since the bootloader won't unlock :/
I guess the phone is in working order at the moment, I just can't let it get turned off without my computer next to me...
Click to expand...
Click to collapse
Nono I mean different qualcomm recovery packages, the ones with MSM8994DownloadTool, I also replaced the stock recovery in the qualcomm package with twrp just in case if that matters

Makrilli said:
Nono I mean different qualcomm recovery packages, the ones with MSM8994DownloadTool, I also replaced the stock recovery in the qualcomm package with twrp just in case if that matters
Click to expand...
Click to collapse
Ahh, do you mind linking me to the one you used?

I think I used this: https://mega.nz/#!EsNQHKab!ifATzg4rxxBniPad0iyxANqlN8cZpUx2MVWaZgEhrD4
but it might have also been this: https://drive.google.com/file/d/0B14IjYN3PtxcSlJ5aGQxX3JERHM/view?usp=sharing
It's also worth mentioning I flashed both a few times before I tried the fastboot continue command so try both a few times and see if that helps, also I replaced the stock recovery with twrp in both recovery packages before flashing.
Edit: And best of luck, I'm rather confident your OPT is going to work properly again.

Boot Loop
I got the same problem.
Phone is rooted and i can't unlock it in cmd, just reboot itself when i try it.
The only way for me to even start the OPT is to (volume+ and power), to get to fastboot mode, then run "fastboot continue" twice in cmd.
If i reboot the phone it get cought in a boot loop where i can see the logo, reboots about every 2 sec.
Is there a solution for this? I've been searching 2 for two days now.
I don't care if i have to reset the entire phone.

p3wb said:
I got the same problem.
Phone is rooted and i can't unlock it in cmd, just reboot itself when i try it.
The only way for me to even start the OPT is to (volume+ and power), to get to fastboot mode, then run "fastboot continue" twice in cmd.
If i reboot the phone it get cought in a boot loop where i can see the logo, reboots about every 2 sec.
Is there a solution for this? I've been searching 2 for two days now.
I don't care if i have to reset the entire phone.
Click to expand...
Click to collapse
And I'm guessing you have tried the qualcomm recovery tool?

And I'm guessing you have tried the qualcomm recovery tool?[/QUOTE]
I got TWRP installed but its unreachable, volume- and power ends in boot loop.
I can´t install anything when the phone is locked.
I even tried a Factory reset, boot loop and no change when i got it up again.

p3wb said:
And I'm guessing you have tried the qualcomm recovery tool?
Click to expand...
Click to collapse
I got TWRP installed but its unreachable, volume- and power ends in boot loop.
I can´t install anything when the phone is locked.
I even tried a Factory reset, boot loop and no change when i got it up again.[/QUOTE]
Yeah but the qualcomm recovery tool that we discussed on the first page?
Sent from my OPT

Makrilli said:
I got TWRP installed but its unreachable, volume- and power ends in boot loop.
I can´t install anything when the phone is locked.
I even tried a Factory reset, boot loop and no change when i got it up again.
Click to expand...
Click to collapse
Yeah but the qualcomm recovery tool that we discussed on the first page?
Sent from my OPT[/QUOTE]
I finally got my OPT working again, tried Qualcomm recovery tool, wasn't able to complete the "MSM8994DownloadTool"
So i downloaded "A2001_14_A.03_150805" in a guide from technobuzz.net/unbrick-oneplus-2/
A similar but it does a entire wipe of the phone, nothing left at all. WARNING!
But i was okey with it.
Well the phone was in Chinese when it was all done but to change language was no problem.

I finally managed to solve it on mine. I had been cautious over the past weeks to not let it run out of battery or get turned off while away from my computer as
Code:
fastboot continue
was the only way I could get past the boot loop.
My core issue to solve was that I couldn't get it recognised as the USB Diagnostic 9006 under Ports in Device Manager. I installed the driver from here manually by right clicking the /qcser/x64/qcser.inf file and selecting install from the context menu. Then, I powered off my OP2. While only holding Vol+ (not power or Vol-), I plugged in my OP2 to the computer and it was finally recognised as the 9006. Then using the recovery tool from the prior link, it installed and rebooted my OP2. The moment of truth was when it rebooted and didn't enter a boot loop!
Then with the Chinese recovery prompt, I selected the top/first option and it brought me to the welcome/first setup screen of OOS.
It wiped the internal memory, and installed OSS 2.0.2 (don't know if coincidence or not as that was my prior OS as well). Now to install twrp and update to the latest OOS hopefully without a hitch.
Happy to finally know it wasn't a hardware issue like a failed eeprom or a dud nand controller as my prior phone (Samsung Note 10.1) died to a failed nand controller as well.
Will update with news of twrp and OOS, but I feel that should go smoothly now. Thanks to the others that helped in this thread too!

Yeap, all good!
Flashed official twrp through fastboot and batch installed OOS2 through 2.1.1 patches and SuperSU. Everything working like new!
Phew.

hi can one of you guys help me out? on teamviewer? mine is stock in the bootloop and i can only get it to boot up via fastboot continue. and i cant figure out how to get it to work. i would like to go back to complete stock and no root
best Martin

gamdiiii said:
hi can one of you guys help me out? on teamviewer? mine is stock in the bootloop and i can only get it to boot up via fastboot continue. and i cant figure out how to get it to work. i would like to go back to complete stock and no root
best Martin
Click to expand...
Click to collapse
Is it recognised as a USB Diagnostic 9006 in your device manager?

Hi GusGold No its 9008