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
Related
Hey guys
I tried the one-click root toolkit for mac from android rootz.
Something apparently has gone wrong during the root and I got some error messages and it didn't proceed. Next thing I know the nexus is stuck on google X logo and that's it. It won't load. I tried to recover through the recovery mode a couple of times but now I get the red warning sign when I go into recovery mode. This is only the second day I've had the nexus for. I feel like crying. Please Help
When the red sign appears press the volup down buttons and power button randomly until you get into recovery then factory reset
My 7 and 10 both did that. Just hold power until it turns off, then boot a recovery, wipe everything except system and reboot. It'll come up ok.
Sent from my Nexus 10 using Tapatalk HD
I'm having the same issue. However, the recovery I have installed is the non-functional CWM. So I can't factory reset. (I managed to once before CWM bombed, but it didn't change anything.)
I've tried several options via the toolkit. After fighting with the app all day it's finally wound up just saying it can't find adb? (I have a growing dislike for this app and have since uninstalled it.) Adb is right where it belongs and seems to run fine from cmd.
I also can't seem to flash anything via fastboot for some reason. The device throws "failinvaild id command" and fastboot immediately crashes on my laptop.
I managed to get it unlocked. However, I'm unable to flash anything to straighten it out...
Any help would be great.
scooterbaga said:
I'm having the same issue. However, the recovery I have installed is the non-functional CWM. So I can't factory reset. (I managed to once before CWM bombed, but it didn't change anything.)
I've tried several options via the toolkit. After fighting with the app all day it's finally wound up just saying it can't find adb? (I have a growing dislike for this app and have since uninstalled it.) Adb is right where it belongs and seems to run fine from cmd.
I also can't seem to flash anything via fastboot for some reason. The device throws "failinvaild id command" and fastboot immediately crashes on my laptop.
I managed to get it unlocked. However, I'm unable to flash anything to straighten it out...
Any help would be great.
Click to expand...
Click to collapse
Watch this video starting at the 6:30 mark.
http://www.youtube.com/watch?v=YtLvlrUDB04
bg1906 said:
Watch this video starting at the 6:30 mark.
http://www.youtube.com/watch?v=YtLvlrUDB04
Click to expand...
Click to collapse
Thanks for the info. My situation wasn't quite the same as my CWM was the real issue, which wouldn't run long enough to allow for the factory reset boot-loop solution. Kept at it and managed to get CWM to finish the individual formats/resets one at a time.
With a now bootable device, I'm off to replace the recovery... Thanks again.
Hey guys
i just wiped all my data and tried to reboot my nexus, but now it's been stuck on the google logo for ages...
trying to flash to stock + unroot with nexus toolkit doesn't work, any way to unbrick it?
please help...
do you have fastboot driver installed?
Step 1: Power down your Nexus 4 (hold the power button until it shuts off) before rebooting into fastboot mode. You can do this by holding down the the Volume Down and Power buttons simultaneously.
Step 2: Connect your device to your computer. Open up a terminal or command prompt, and navigate to the folder containing the fastboot program.
Step 3: Type fastboot devices into the command line, and you should then see your device’s ID, which means fastboot is setup correctly.
now go back to Nexus 4 toolkit. Flash back to stock.
badboy47 said:
do you have fastboot driver installed?
Step 1: Power down your Nexus 4 (hold the power button until it shuts off) before rebooting into fastboot mode. You can do this by holding down the the Volume Down and Power buttons simultaneously.
Step 2: Connect your device to your computer. Open up a terminal or command prompt, and navigate to the folder containing the fastboot program.
Step 3: Type fastboot devices into the command line, and you should then see your device’s ID, which means fastboot is setup correctly.
now go back to Nexus 4 toolkit. Flash back to stock.
Click to expand...
Click to collapse
works
thank you very much
fabian.m said:
works
thank you very much
Click to expand...
Click to collapse
Then, press on his THANKS button. That's the way we have to measure who contributes or not in xda-developers. Please, let's follow rules...
luiseteyo said:
Then, press on his THANKS button. That's the way we have to measure who contributes or not in xda-developers. Please, let's follow rules...
Click to expand...
Click to collapse
well.. technically thanking isn't in the rules.
exb0 said:
well.. technically thanking isn't in the rules.
Click to expand...
Click to collapse
It is in the good behaviour and politeness rules. Not everything is written.
Hi guys i got a similar problem, i flashed a walkman .zip wiped cache and dalvik cache. Then the phone booted into google logo, and it went all black. The display is on but its all black. The problem is i cannot power off the device. Holding all buttons just restarts the phone. What can i do?
I was on latest PA rom
Qbsti said:
Hi guys i got a similar problem, i flashed a walkman .zip wiped cache and dalvik cache. Then the phone booted into google logo, and it went all black. The display is on but its all black. The problem is i cannot power off the device. Holding all buttons just restarts the phone. What can i do?
I was on latest PA rom
Click to expand...
Click to collapse
reflash your rom. reboot your device, hold volune down before it reboots to get into the bootloader then recovery.
simms22 said:
reflash your rom. reboot your device, hold volune down before it reboots to get into the bootloader then recovery.
Click to expand...
Click to collapse
Thanks simms, i managed to get into fast boot between the reboots, and I flashed the rom and gapps.
Damn it scared me even more then the red light issue that happened to me last month.
Qbsti said:
Thanks simms, i managed to get into fast boot between the reboots, and I flashed the rom and gapps.
Damn it scared me even more then the red light issue that happened to me last month.
Click to expand...
Click to collapse
not booting after flashing something or modding something is the easiest of all to fix, just reflash the rom(gapps and kernel too if need be), no need to wipe anything. since i test all the trinity kernels before any get released, and pre-kernels, i get many that dont boot my device or bootloop(among some other funky behaviors), reflashing a good kernel always works
I left my phone for a few minutes, and when I picked it up it was bootlooped again, and i had to use fastboot again. What should I do now? Maybe a factory reset would help me. I don't want more unexpected bootloops. :/
swyped from my nexus 4
Qbsti said:
I left my phone for a few minutes, and when I picked it up it was bootlooped again, and i had to use fastboot again. What should I do now? Maybe a factory reset would help me. I don't want more unexpected bootloops. :/
swyped from my nexus 4
Click to expand...
Click to collapse
Try another rom. You might have downloaded corrupted zips. Also, make sure you flash the things you need first. Eg, flash rom and gapps. Don't restore anything if you're using titanium backup. Try restarting the phone, see if it gets into a bootloop. If it doesn't, then try restoring apps from TB. (if you use TB.)
Hi!
I´ve got a big problem. Today i flashed the new PA version, but it seems that the download had some issue. I could install it but after a while, I wanted to reboot the phone and it got stuck at the Google logo. I can only access fastboot mode and recovery.
So the problem is, i made a full wipe, so i have no rom on the sdcard anymore. Also I am now able to enable the debbuging mode. I tried every toolkit i couzld find, but everyone needs debugging mode enabled. windows doesnt recognize the phone ( it says unkown device). So i tried to install the adb drivers, but nothing happens.
i wanted to try to push a rom with adb on the phone but it says no device found. i am such a noob, i hope some can help me.
thx
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.
Was having issues with my Nexus 7(2013) this morning, rebooted the device and now it gets stuck at the "Google" loading screen.
I can get into the Fastboot loader. I was able to unlock the bootloader.. I have LOCK STATE - unlocked and the unlocked lock showing up on the "Google" boot screen.
I am UNABLE to get into Recovery mode.. either by selecting "Recovery mode" in Fastboot or holding the power and vol up buttons. It just sits on the "Google" boot screen.
I have downloaded and installed the SkipSoft Android Toolkit(mskip).. very nice toolkit BTW. But no matter what I do I'm unable to start the tablet up normally or get into a Recovery mode of any kind.
I have tried to flash TWRP. I have tried to flash the stock ROM. Nothing, still sits at the Google boot screen. Since flashing the stock ROM its been 30 min and still just says "Google".
I'm open to any ideas or anything that you can think of.
Still have TWRP and fastboot access? If so, use the command line fastboot the img using
"fastboot boot <filename>.img"
Reply back; do you get to recovery?
Snuzzo said:
Still have TWRP and fastboot access? If so, use the command line fastboot the img using
"fastboot boot <filename>.img"
Reply back; do you get to recovery?
Click to expand...
Click to collapse
No.. I do not get into recovery of any kind. Stock or TWRP after loading it.. just sits at the Google screen.
Quick question; what were your partition setups like? F2fs? Ext4?
Snuzzo said:
Quick question; what were your partition setups like? F2fs? Ext4?
Click to expand...
Click to collapse
No idea.. it should be whatever it is stock. Before today I never rooted, flashed or did anything to this device.
FDokinawa said:
No idea.. it should be whatever it is stock. Before today I never rooted, flashed or did anything to this device.
Click to expand...
Click to collapse
Answers all of my questions. I know myself I won't be able to help. All I can say is to try relocking and then unlocking again.
Snuzzo said:
Answers all of my questions. I know myself I won't be able to help. All I can say is to try relocking and then unlocking again.
Click to expand...
Click to collapse
Thanks for the help.. will give it a shot.
FDokinawa said:
Thanks for the help.. will give it a shot.
Click to expand...
Click to collapse
What that should do is wipe internal, could have some corruption there. Try doing the command line fastboot of the recovery.img again. Those are the only few things I can think of short from exercising your warranty.
Snuzzo said:
What that should do is wipe internal, could have some corruption there. Try doing the command line fastboot of the recovery.img again. Those are the only few things I can think of short from exercising your warranty.
Click to expand...
Click to collapse
Dont think I can use the warranty.. bought it used(1 hour old) from a friend for $100.. he got it and then decided he didnt like the aspect ratio. His loss, my gain. Until now.. lol
I'll keep hacking at it.. thanks again.
Anytime! You're welcome!
So the original issue I was having was that the screen was not responding to touches. Was unable to slide the unlock button on the screen.
I was able to "Boot to Custom/Stock Recovery without Permanently Flashing it" via SkipSoft Toolkit.. and had TWRP load up. But like before it was not responding to touches.
Starting to think this thing is totally borked.. =/
I'm able to get into TWRP now.. but sits on boot animation screen now. one step forward. Going to try and reload the stock ROM again and see if that helps.
That seemed to work.. at the Welcome screen.
So if anyone else runs into something like this..
Issues:
Flakey touch screen
Stuck on Google bootup screen
Eventually stuck boot loop animation
Get SkipSoft Android Toolkit, donate a couple bucks and keep flashing anything and everything you can. Sorry I can't give you a specific order that works. I would say try the 'ALLINONE'(#8) option first and then download and flash the stock ROM. I did several things in the toolkit a few times over and over. Hopefully I'm good now, if not I will update.
Have you tried reflashing recovery via fastboot?
Exact thing happend to my n4.
Sent from my N⁴ using Android Lollipop by @Sykopompus running Unleased kernel by @DeFcOni
================================
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