Alright, I am having some trouble with the Nexus and hopefully someone can help me with this. Then Nexus was unlocked and rooted but I was still rocking the stock rom on there. The tablet used to be recognized by the computer and everything was fine. I used a car charger today to charge the tablet, came home, and the tablet would no longer show MTP when connected to the computer but rather would only charge.
I thought it was an issue with the rom so I downloaded a new rom, made a backup and went to flash it. Something happened when I was flashing the rom which forced the tablet to reboot and all it would get to is the Google screen. It won't go past that. I can get into the bootloader but can't boot into recovery or the system. Its not being recognized in fastboot mode either so I have no way to flash a recovery onto it...
Any suggestions?
have you tried force rebooting it a few times to try to get it ti boot up?
simms22 said:
have you tried force rebooting it a few times to try to get it ti boot up?
Click to expand...
Click to collapse
Multiple times. I have also used several different USB cables and ports on the computer. Still nothing
Any other thoughts?? I'm really in a bind
rmerchant786 said:
Any other thoughts?? I'm really in a bind
Click to expand...
Click to collapse
Can I take a look at it for you? Send me a PM and we will chat on google talk. I have some ideas though, we can connect remotely with teamviewer and I'll see if I can tell what's going on.
Any luck? I'm having the same problem.
The device is not recognized by the computer at all and the bootloader freezes then I connect it to the computer or the charger.
Engstrom said:
Any luck? I'm having the same problem.
The device is not recognized by the computer at all and the bootloader freezes then I connect it to the computer or the charger.
Click to expand...
Click to collapse
change your wire it maybe faulty or try it again on another pc
ngoralph said:
change your wire it maybe faulty or try it again on another pc
Click to expand...
Click to collapse
I've tried three usb cables on three computers (with W7, W8, Ubuntu and OS X). Makes no difference.
It does however indicate charging then it's off.
Engstrom said:
I've tried three usb cables on three computers (with W7, W8, Ubuntu and OS X). Makes no difference.
It does however indicate charging then it's off.
Click to expand...
Click to collapse
out of ideas but i used the wire given on the box and it worked but when i used different plug it didn't work
I have the same problem too after i meet flashing error in TWRP ~
I'm trying to flash Paranoid ROM update in TWRP, somehow the recovery show error when flashing so i decided to reboot system.
After that it stuck at Google logo and when I try to plug in the usb to computer, the fastboot freeze...
What to do man? Please help me
Please anyone help help ???
Are you two able to get an adb connection? If so, and you can get into fastboot, you can download and flash the Google factory ROM.
If you are not familiar with adb, try the Nexus 7 Toolkit from Skipsoft.net to flash the OEM ROM.
I'm not the lowest of the low, but I am the slowest of the slow.
I had similar issue
When I first unlocked and rooted my N7 .... and then tried to flash AOKP, I had a very similar issue as it would not boot into OS or CWM! SO i left it for some time and then crossed my fingers and tried to boot into bootloader 1 day later and then CWM ..... and it worked!
I think this is quite good advice for u to try out!
exglynco said:
Are you two able to get an adb connection? If so, and you can get into fastboot, you can download and flash the Google factory ROM.
If you are not familiar with adb, try the Nexus 7 Toolkit from Skipsoft.net to flash the OEM ROM.
I'm not the lowest of the low, but I am the slowest of the slow.
Click to expand...
Click to collapse
exglynco said:
Are you two able to get an adb connection? If so, and you can get into fastboot, you can download and flash the Google factory ROM.
If you are not familiar with adb, try the Nexus 7 Toolkit from Skipsoft.net to flash the OEM ROM.
I'm not the lowest of the low, but I am the slowest of the slow.
Click to expand...
Click to collapse
Thanks for the reply mate
I can get into fastboot but once I connect the usb, it freeze and the toolkit I used (GNEX TOOLKIT) couldn't get my device :crying:
And sorry to ask, what is adb connection?
I only know fastboot, now my N7 only can boot in fastboot without usb plug in :silly:
But I will try to use the toolkit you recommend me, hope it works :fingers-crossed:
Thanks a lot
---------- Post added at 12:48 AM ---------- Previous post was at 12:45 AM ----------
exglynco said:
Are you two able to get an adb connection? If so, and you can get into fastboot, you can download and flash the Google factory ROM.
If you are not familiar with adb, try the Nexus 7 Toolkit from Skipsoft.net to flash the OEM ROM.
I'm not the lowest of the low, but I am the slowest of the slow.
Click to expand...
Click to collapse
wtgserpant said:
When I first unlocked and rooted my N7 .... and then tried to flash AOKP, I had a very similar issue as it would not boot into OS or CWM! SO i left it for some time and then crossed my fingers and tried to boot into bootloader 1 day later and then CWM ..... and it worked!
I think this is quite good advice for u to try out!
Click to expand...
Click to collapse
Haha...so what I have to do is wait for a few day and try again
Thanks for the advice
Google Fasfboot and ADB. Between the two of them, you can flash recovery, push & flash ROMs, etc. The Nexus 7 Toolkit makes Fasfboot & ADB commands pushbutton choices.
I'm not the lowest of the low, but I am the slowest of the slow.
Related
Hey guys,
I've been noticing something unusual with my tablet. The stock hard-reset recovery(as well as CWM) only works with USB plugged in. When it is not plugged on the computer, it hangs on the black screen with the Google logo(when it is oem locked, there's a lock on the bottom). I am also a Galaxy S2 user so I know that I didn't need the USB plugged in, in order to enter the recovery mode.
Is this normal for the N7 tablet? or is there something wrong with it?
Thank you
kaywoo said:
Hey guys,
I've been noticing something unusual with my tablet. The stock hard-reset recovery(as well as CWM) only works with USB plugged in. When it is not plugged on the computer, it hangs on the black screen with the Google logo(when it is oem locked, there's a lock on the bottom). I am also a Galaxy S2 user so I know that I didn't need the USB plugged in, in order to enter the recovery mode.
Is this normal for the N7 tablet? or is there something wrong with it?
Thank you
Click to expand...
Click to collapse
I have the same issue, and I always thought it was just me. Going to try a different recovery when I'm back home.
cheami said:
I have the same issue, and I always thought it was just me. Going to try a different recovery when I'm back home.
Click to expand...
Click to collapse
Yeah it's weird. Even after coming back to stock, unrooted, the hard-reset via stock recovery doesn't work unless USB is plugged in. Maybe some files are missing
Wow, I'm glad I stumbled on this thread, I was going nuts trying to figure out why I couldn't boot back into CWM after going back to the stock image and applying the OTA .zips.
Confirmed, I can get it to boot into CWM from fastboot only if I have the USB cable plugged in. Otherwise it just hangs on the Google splash screen.
Weird.
I've been able to boot into recovery using the app "quickboot" which had an option to reboot into recovery. My usb cable isn't plugged in.
Sent from my Galaxy Nexus using Tapatalk 2
This sounds a bit like my Nexus S i9020. It will only go into bootloader without the usb, and only go into download mode with USB attached (although it doesn't have to be powering it). This is the same on both handsets I've used. Maybe not a 'flaw' and more a nod to using fast boot/adb?
Sent from my Nexus S using xda app-developers app
I am currently having the same problem. Did anybody come up with a fix for this?
I'm having the same issue with the nexus 7. I've found out that you can boot into recovery if you have ROM Manager installed and select reboot into recovery.
Does anyone know if this is an OS issue or recovery issue?
Interesting. Was wondering why I couldn't get into Recovery from the Bootloader.
Another bug for me is that if I boot into Bootloader with the USB connected, I cannot make any selection using the volume keys. Only works if I boot in first without USB connected, then connect once I'm booted.
Its a bug, guys learn to search in the Development threads, I'm sure its being worked on,personally I've been able to get into recovery without have to connect via USB, if all else fails you can enter recovery via USB and ADB, by issuing the command adb reboot recovery in terminal/cmd
I had the same issue last week. Not sure what changed but now I'm able to get into recovery using the reboot menu or good mngr/rom mgr. No need for usb. I'm on modaco rom and used both clockwork and twrp.
Sent from my PG86100 using xda app-developers app
I have one more problem...
When I connect USB, the keys don't work in bootloader so can't try recovery with USB cable on.
Any solution for this?
cheami said:
I have the same issue, and I always thought it was just me. Going to try a different recovery when I'm back home.
Click to expand...
Click to collapse
I have the same problem.
LTE Galaxy Nexus
Nexus 7 (16gb)
Miracle.vl63 said:
I have one more problem...
When I connect USB, the keys don't work in bootloader so can't try recovery with USB cable on.
Any solution for this?
Click to expand...
Click to collapse
There are two different versions of CWM- one uses the power and vol-up/down buttons for keys- the other used the tablets touchscreen for button press functions.
You may have installed the touch(screen) version of CWM- try using the touchscreen for controls.
Same issue here. I can get to recover either connected or via rom manager.
Sent from my MIUI Motorola Star Tac
omegajester said:
Same issue here. I can get to recover either connected or via rom manager.
Sent from my MIUI Motorola Star Tac
Click to expand...
Click to collapse
I too can get into recovery via ROM Manager. I read somewhere that pulling the battery might help. I know that's a bit of a pain on the Nexus 7, but I'm going to try that when I get home later to see if that helps.
LTE Galaxy Nexus
Nexus 7 (16gb)
Trikkenut said:
I too can get into recovery via ROM Manager. I read somewhere that pulling the battery might help. I know that's a bit of a pain on the Nexus 7, but I'm going to try that when I get home later to see if that helps.
LTE Galaxy Nexus
Nexus 7 (16gb)
Click to expand...
Click to collapse
Nope, disconnecting the battery didn't change anything. Wug Fresh (Nexus Root Toolkit developer) informed me on Google + that it's a Google issue and it should be fixed in a future update. For now i'll be either plugging in USB to computer or ROM Manager.
I can't even get into the boot loader with my usb plugged into a charger not a computer
askho said:
I can't even get into the boot loader with my usb plugged into a charger not a computer
Click to expand...
Click to collapse
Try Quick Boot
Free, easy to use, will boot to bootloader, recovery, reboot etc... requires root of course, you already have that.
i dont't have root because it was screwed up right fromt he get go
The problem is I can't unbrick and restore my nexus to stock rom.
I can't boot the device and I'm only able to boot to bootloader. However, my computer doesn't recognize the nexus. It keeps saying Window cannot recognize it whenever I plug my tablet to the computer in bootloader. I tried uninstall and reinstall driver several times, but none of them seems to work . ----> That means I can't even use adb to restore the phone simply because my tablet is not recognized in window.
Is there anyway to fix this problem? I really need your helps as soon as possible.
Thank you for reading !
Get to bootloader. Then use Wugs toolkit, open advanced options. On the very left is something like "temp boot to recovery". Once that boots it to recovery, ADB should work. It did for me. I was in some trouble last night and got out by this. If you know how to use adb/fastboot commands, you should be good. And I uninstalled my drivers and when I plugged it in the device automagically reloaded the drivers. But you have to do it a few times. Had to do it in bootloader, recovery, and another point. Anytime it asks to load drivers/etc do it.
I can't boot to recovery through Wug Tool Kit. It keeps saying Fastboot device was not found >"<
By the way, whenever I connnected my device to computer, the bootloader freezes :|
What were you doing before you go into this situation?
I was on Glazed Jelly Bean rom and wanted to go back to stock rom. I used nexus 7 toolkit to do all the work for me. However, there was something wrong like the toolkit didnt extract the stock img right or something like that, my tablet got bootloop, and what happened next was what i had been telling you guys.
Best bet is if somehow you could get into recovery or get adb working. Might want to uninstall drivers and install again and reboot computer. I would suggest using this thread and flash things manually back to stock. http://forum.xda-developers.com/showthread.php?t=1907796 but you would need adb working.
When you power off device and use volume and power can you get it to go into boot loader then plugged into computer try to get to recovery or adb.
Consider deleting the drivers from Windows after uninstalling them otherwise Windows may try to be "clever" and reinstall the bad driver when you plug the device in. The Nexus 7 drivers from Asus can be downloaded here and Google's USB drivers are here
Travisdroidx2 said:
Best bet is if somehow you could get into recovery or get adb working. Might want to uninstall drivers and install again and reboot computer. I would suggest using this thread and flash things manually back to stock. http://forum.xda-developers.com/showthread.php?t=1907796 but you would need adb working.
When you power off device and use volume and power can you get it to go into boot loader then plugged into computer try to get to recovery or adb.
Click to expand...
Click to collapse
What if I couldn't get adb working?
I tried everything and windows still doesn't recognize my device in fastboot
Have you tried Nexus Root Toolkit v .1.5.4?
kiddo94 said:
I tried everything and windows still doesn't recognize my device in fastboot
Click to expand...
Click to collapse
try connecting to the usb port at the back of your computer
Paranoid flashed with the bricked kernel did this to me once right after the move to 4.1.2. Even with a full wipe and all the usual safety precautions it just stuck on bootloop forever and wouldn't let me in. I chalked it up as that's what I get for being the guy that's never satisfied with stock. I was unable to get my nexus7 fixed. I sent you a suggestion on pm though.
Never mind everyone. Thank you so much for your help.
I tried install the nexus 7's driver on another computer and it recognized my device in bootloader mode, and restore everything back to stock now. Thank you so much!!!!
Mine did that to the first time I tried. After I got it to work, the permissions were all messed up and I could not get it to download anything off the web and I was getting a playstore error 90% of the time as well. I finally just wiped everything on my tablet, installed the stock rom via N7 toolkit, then reflashed smooth rom, and all is working now. It may have been a bug with the older version of N7 toolkit, as I updated it before I reran everything.
Hi!, I have a bricked Oneplus 2 so heres how it happened
My device was running oxygen os 3.0 with TWRP 3.0 and I decided to flash the resurrection remix ROM on my phone through twrp, and when I did flash it I think it gave me some error code, and then I rebooted my phone and now its stuck in a bootloop with no OS installed.
I tried going to TWRP and adb was not working and adb side load was not working, I went to fastboot and my computer wont detect my device through fastboot. I tried first aid kit and my phone was not being detected. I did try this with using 2 other computers running windows 10 and I tried it with a computer running Linux Mint. How ever when I check in Device Manager It shows "communications port (COM1) I tried updating that driver with the Oneplus 2 Qualcom drivers and it gave me a error code 10 and I tried installing an ADB interface driver to that to and I got the same error code 10. I also tried this method below with no luck.
"https://forums.oneplus.net/threads/updated-29-03-2016-mega-unbrick-guide-for-a-hard-bricked-oneplus-2.347607/"
Please help me and the community facing this problem, Thanks!
I have a same problem. so any advice how to fix this is more than welcome. Except Firstaid kit gave back Recovery (twrp) which Oxygen 3.0 Beta removed etc, Now i have TWRP 2.8.7.0 and thats it. PC just dont find device so that i could transfer nesessary files
E: Does it matter is this Oneplus 2 recovery tool for A2001 or A2003? i just noticed that the one i downloaded, folder name is A2001_save_brick_mini
SirMika said:
I have a same problem. so any advice how to fix this is more than welcome. Except Firstaid kit gave back Recovery (twrp) which Oxygen 3.0 Beta removed etc, Now i have TWRP 2.8.7.0 and thats it. PC just dont find device so that i could transfer nesessary files
E: Does it matter is this Oneplus 2 recovery tool for A2001 or A2003? i just noticed that the one i downloaded, folder name is A2001_save_brick_mini
Click to expand...
Click to collapse
I caint do any thing in twrp to, but I heard that there was a problem with twrp 3.0 that you caint transfer any files to pc, I think you might fix the problem by getting a usb type c usb otg and flashing the stock rom from there possibly. but I doint want to pay the price for it right now, but hopefully I will find a solution
SirMika said:
I have a same problem. so any advice how to fix this is more than welcome. Except Firstaid kit gave back Recovery (twrp) which Oxygen 3.0 Beta removed etc, Now i have TWRP 2.8.7.0 and thats it. PC just dont find device so that i could transfer nesessary files
E: Does it matter is this Oneplus 2 recovery tool for A2001 or A2003? i just noticed that the one i downloaded, folder name is A2001_save_brick_mini
Click to expand...
Click to collapse
And does your phone get recognized by fast boot? because you were saying that you used first aid to get recovery, and first aid uses fastboot, because you will beable to fix your phone through fastboot
yes, i just run fastboot commands and its unlocked etc but PC dont find OPT
---------- Post added at 10:27 AM ---------- Previous post was at 10:23 AM ----------
i just cant figure out how i transfer flashable zips in device to get oxygen or some decent rom
SirMika said:
yes, i just run fastboot commands and its unlocked etc but PC dont find OPT
---------- Post added at 10:27 AM ---------- Previous post was at 10:23 AM ----------
i just cant figure out how i transfer flashable zips in device to get oxygen or some decent rom
Click to expand...
Click to collapse
This might help you if your phone can be detected in fastboot:
http://www.androidsage.com/2016/03/12/restore-oneplus-2-full-stock-firmware/
It is a stock rom that you flash through fastboot
fahad999 said:
This might help you if your phone can be detected in fastboot:
http://www.androidsage.com/2016/03/12/restore-oneplus-2-full-stock-firmware/
It is a stock rom that you flash through fastboot
Click to expand...
Click to collapse
Sure i can try but i dont expect to get this work anymore..at leat awhile. earlier i tried to sideload stock OxygenOS but it failed because it says i need adb v 1.0.32 or newer, and surprise surprise it dont work properly in Windows 10.
SirMika said:
Sure i can try but i dont expect to get this work anymore..at leat awhile. earlier i tried to sideload stock OxygenOS but it failed because it says i need adb v 1.0.32 or newer, and surprise surprise it dont work properly in Windows 10.
Click to expand...
Click to collapse
It should work if your phone is recognized by fastboot, you have to download stock rom fastboot file and extract it, then connect your phone to fastboot to pc, then in the stockrom file click the run-all.bat and your phone should work but the problem with my phone is that my phone is not being recognized by fastboot
fahad999 said:
It should work if your phone is recognized by fastboot, you have to download stock rom fastboot file and extract it, then connect your phone to fastboot to pc, then in the stockrom file click the run-all.bat and your phone should work but the problem with my phone is that my phone is not being recognized by fastboot
Click to expand...
Click to collapse
not sure but i did similar procedure yesterday. see second post http://forum.xda-developers.com/oneplus-2/general/rom-mirrors-official-oxygen-os-roms-ota-t3209863 but i had no idea what i suppose to do..all i had was stock recovery..
in adb, running command fastboot device it shows my phone
Guys I am stuck too, form oxygen os 3.0 I decided to restore my all old backup from twrp, and now my device is fried, recovery is not working too. I tried ton of ways, it can boot into fastboot, but my pc cannot detect it for some reason. In pc no fastboot devices. Nothing in ports. that 10second trick is also not working. Someone plz help
Getsuga Tenshou said:
Guys I am stuck too, form oxygen os 3.0 I decided to restore my all old backup from twrp, and now my device is fried, recovery is not working too. I tried ton of ways, it can boot into fastboot, but my pc cannot detect it for some reason. In pc no fastboot devices. Nothing in ports. that 10second trick is also not working. Someone plz help
Click to expand...
Click to collapse
it seems there is no way to fix it..my skills and knoledge aint high, but i´v done all by the book and nothing. it also goes in fastboot and twrp but thats it. i wish i could help you but were in a same boat
Getsuga Tenshou said:
Guys I am stuck too, form oxygen os 3.0 I decided to restore my all old backup from twrp, and now my device is fried, recovery is not working too. I tried ton of ways, it can boot into fastboot, but my pc cannot detect it for some reason. In pc no fastboot devices. Nothing in ports. that 10second trick is also not working. Someone plz help
Click to expand...
Click to collapse
Danm, that sucks. Later I may try using a virtual machine of Linux Mint on my computer and see if it will detect my phone in fastboot. And the sad thing is that this oneplus 2 is my only phone
Getsuga Tenshou said:
Guys I am stuck too, form oxygen os 3.0 I decided to restore my all old backup from twrp, and now my device is fried, recovery is not working too. I tried ton of ways, it can boot into fastboot, but my pc cannot detect it for some reason. In pc no fastboot devices. Nothing in ports. that 10second trick is also not working. Someone plz help
Click to expand...
Click to collapse
Just to refresh, the problem that we are looking at is that your PC does not recognize our phone (Driver Problem)
So together we have to find a solution to this driver problem, so this is the main problem. I myself am running Windows 10
fahad999 said:
Just to refresh, the problem that we are looking at is that your PC does not recognize our phone (Driver Problem)
So together we have to find a solution to this driver problem, so this is the main problem. I myself am running Windows 10
Click to expand...
Click to collapse
I think i need to get in my hands PC with Win7. i also came that conclusion the problem is Windows.
Oneplus drivers (/D) just keep pop-upping asking what todo, when selected nothing happens
EDIT: is it possible install proper softwares via USBstorage?
Guys, I am running a dual boot machine (windows 7 and 10) and on both there is not even a sign of detection. Same is happening on another laptop which runs on windows 7 too. Only phone boots to bootloader on connected (like a charger and nothing else).
Just before my fp stopped working. Last time it did, my usb type c cable also died. This time I don't know since I directly restored from twrp and did not connect it to my pc. There is a slight chance that our usb type c cables have malfunctioned (which is better than permanent brick). If you have any access/ friend with that cable please try it. If it works we might be in luck.
Note: SirMika, For you usb is working, you do not need to try this, did you try flashing revert files
Getsuga Tenshou said:
Guys, I am running a dual boot machine (windows 7 and 10) and on both there is not even a sign of detection. Same is happening on another laptop which runs on windows 7 too. Only phone boots to bootloader on connected (like a charger and nothing else).
Just before my fp stopped working. Last time it did, my usb type c cable also died. This time I don't know since I directly restored from twrp and did not connect it to my pc. There is a slight chance that our usb type c cables have malfunctioned (which is better than permanent brick). If you have any access/ friend with that cable please try it. If it works we might be in luck.
Note: SirMika, For you usb is working, you do not need to try this, did you try flashing revert files
Click to expand...
Click to collapse
I just got a Linux Mint virtual machine and still the phone is not being detected via ADB and Fastboot in Linux Mint, I think the only possible solution that we have is purchasing a USB Type C USB OTG and Side-loading a ROM on their and flashing it through recovery. But this possible solution is for people who still have access to their recovery and luckily I do.
Oxygen OS 3.0 Flashable ZIP: http://downloads.oneplus.net/2016-03-30/op2/OnePlus_2_OxygenOS_3.0_Beta/
USB TYPE C OTG: http://www.amazon.com/Adapter-RAVPo...qid=1463938874&sr=8-1&keywords=usb+type+c+otg
fahad999 said:
I just got a Linux Mint virtual machine and still the phone is not being detected via ADB and Fastboot in Linux Mint, I think the only possible solution that we have is purchasing a USB Type C USB OTG and Side-loading a ROM on their and flashing it through recovery. But this possible solution is for people who still have access to their recovery and luckily I do.
Oxygen OS 3.0 Flashable ZIP: http://downloads.oneplus.net/2016-03-30/op2/OnePlus_2_OxygenOS_3.0_Beta/
USB TYPE C OTG: http://www.amazon.com/Adapter-RAVPo...qid=1463938874&sr=8-1&keywords=usb+type+c+otg
Click to expand...
Click to collapse
Update! I know why our phones are bricked! when we installed custom roms you wiped the phone right. I was reading that there was a new feature in android in which you wipe the phone with a password, the bootloader gets locked. So I believe that our devices now have a locked bootloader
fahad999 said:
I caint do any thing in twrp to, but I heard that there was a problem with twrp 3.0 that you caint transfer any files to pc, I think you might fix the problem by getting a usb type c usb otg and flashing the stock rom from there possibly. but I doint want to pay the price for it right now, but hopefully I will find a solution
Click to expand...
Click to collapse
in twrp press format data (i mean format data no wipe data)...then yes...reboot and now your phone is well partitioned
after that (in orange twrp flash a oxygen oos 3.0 or h2os) or if you want to return to oos 2.x or any other custom rom use the LP steps in this forum....http://forum.xda-developers.com/oneplus-2/general/guide-helper-zips-to-switch-oos-3-0-oos-t3351253
---------- Post added at 10:26 PM ---------- Previous post was at 10:15 PM ----------
Getsuga Tenshou said:
Guys I am stuck too, form oxygen os 3.0 I decided to restore my all old backup from twrp, and now my device is fried, recovery is not working too. I tried ton of ways, it can boot into fastboot, but my pc cannot detect it for some reason. In pc no fastboot devices. Nothing in ports. that 10second trick is also not working. Someone plz help
Click to expand...
Click to collapse
see in connected devices that there is one that has no name or isnt recogniced the press update driver and choose update from a list drivers not update from online then choose android device and then try every (google or clockworkmod driver i think that the one who work is android adb interface...then your computer should detect your phone if not search one the internet because every computer is different in terms of drivers i am telling you the way that i solve alway in mine (you can allways use that chinese program to restore your phone to oos 2.1.1)
Guihardrock said:
in twrp press format data (i mean format data no wipe data)...then yes...reboot and now your phone is well partitioned
after that (in orange twrp flash a oxygen oos 3.0 or h2os) or if you want to return to oos 2.x or any other custom rom use the LP steps in this forum....http://forum.xda-developers.com/oneplus-2/general/guide-helper-zips-to-switch-oos-3-0-oos-t3351253
---------- Post added at 10:26 PM ---------- Previous post was at 10:15 PM ----------
see in connected devices that there is one that has no name or isnt recogniced the press update driver and choose update from a list drivers not update from online then choose android device and then try every (google or clockworkmod driver i think that the one who work is android adb interface...then your computer should detect your phone if not search one the internet because every computer is different in terms of drivers i am telling you the way that i solve alway in mine (you can allways use that chinese program to restore your phone to oos 2.1.1)
Click to expand...
Click to collapse
Sorry to say that this is not working for me and I have no OS installed, I formatted data in twrp and typed yes and still I got no luck. My device is not being recognized by pc in twrp, I installed many drivers (Oneplus Drivers, Google USB Drivers, 15 Sec ADB & Fastboot Drivers, Universal ADB Drivers) Still I got no luck, and nothing shows up in device manager, I tried this in 2 Computers awwell.
i have unlocked bootloader, latest TWRP but no OS. instead zip fils it should be image. adb cant find phone but fast boot does
Please help! I am somewhat a noob and I have a bricked Moto X pure. My phone bricked when i was installing supersu from the twrp. Now it can get into bootloader but all the data on my phone is deleted including twrp. For me this would be an easy fix but of course, my phone does not sense the usb cord. I have tried a couple usb cords to connect to my pc but none of them will work. Am i stuck into a paradox if i dont find a way to get my usb cord to work? Pleaser Help!!!
enochthegreat said:
Please help! I am somewhat a noob and I have a bricked Moto X pure. My phone bricked when i was installing supersu from the twrp. Now it can get into bootloader but all the data on my phone is deleted including twrp. For me this would be an easy fix but of course, my phone does not sense the usb cord. I have tried a couple usb cords to connect to my pc but none of them will work. Am i stuck into a paradox if i dont find a way to get my usb cord to work? Pleaser Help!!!
Click to expand...
Click to collapse
Honestly, if your phone can't talk to your computer with fastboot in the bootloader, your pretty much screwed.
How did you root? What specific version and steps did you take?
I used the hiensberg guide https://forum.xda-developers.com/moto-x-style/general/guides-how-to-guides-beginners-t3200808
What do you think is the best option from here?
Are you trying to get into fastboot with it connected to computer?
Iceburn1 said:
Are you trying to get into fastboot with it connected to computer?
Click to expand...
Click to collapse
No im already in fastboot mode. Im just trying to restore my devioe so that it works. When i power on my phone it displays the unlocked bootloader warning then goes into fastboot mode. The screen reads-
"Start up failed: Your device didnt start up succesfully. Use the software repair assistant on computer to repair your device. Connect your device to your computer to get the software repair assistant. AP Fastboot Flash Mode (Secure) Error: failed to load kernel! Fastboot reason: fall-through from normal boot mode"
On top of this my device will not connect to my computer through usb and all my data is deleted included twrp. I really dont know what to do
acejavelin said:
Honestly, if your phone can't talk to your computer with fastboot in the bootloader, your pretty much screwed.
How did you root? What specific version and steps did you take?
Click to expand...
Click to collapse
I was thinking of downloading the whole operating system on a micro sd card then connecting it to my phone.
Would that work?
enochthegreat said:
I was thinking of downloading the whole operating system on a micro sd card then connecting it to my phone.
Would that work?
Click to expand...
Click to collapse
No... Factory images and custom recovery can only be loaded with fastboot.
So if you connect you phone in the Bootloader to your PC and do "fastboot devices" what is the response? And what OS?
acejavelin said:
No... Factory images and custom recovery can only be loaded with fastboot.
So if you connect you phone in the Bootloader to your PC and do "fastboot devices" what is the response? And what OS?
Click to expand...
Click to collapse
The response is no devices attached. I am android 6.0
enochthegreat said:
The response is no devices attached. I am android 6.0
Click to expand...
Click to collapse
I meant your PC's operating system... I assume Windows? Which means it is likely a driver issue, does it show up in device manager?
enochthegreat said:
The response is no devices attached. I am android 6.0
Click to expand...
Click to collapse
Have you tried rsd lite it might recognize your device?
acejavelin said:
I meant your PC's operating system... I assume Windows? Which means it is likely a driver issue, does it show up in device manager?
Click to expand...
Click to collapse
My pc operating system is windows vista and my device used to show up on device manager. I used to be able to plug the usb and be able to look at my phone saying device connected
enochthegreat said:
"Start up failed: Your device didnt start up succesfully. Use the software repair assistant on computer to repair your device. Connect your device to your computer to get the software repair assistant. AP Fastboot Flash Mode (Secure) Error: failed to load kernel! Fastboot reason: fall-through from normal boot mode"
Click to expand...
Click to collapse
Do you have this when you boot into bootloader/fastboot mode?
Power off, vol - & power?
I think you can't repair it in home.
It looks like you flashed something wrong or something in wrong place.
F.e.: twrp into boot partition.
jonomods said:
Have you tried rsd lite it might recognize your device?
Click to expand...
Click to collapse
Hmm i just tried that and no device showed up. I think after this im just gonna buy a fresh usb cord and if that does work i am scarping this phone. I overall had a very bad experience with this phone anyways. Ill get back to you once i try.
But you had unlocked and flashed TWRP, right? So fastboot worked at one time and you understand how to use it, generally at least?
acejavelin said:
But you had unlocked and flashed TWRP, right? So fastboot worked at one time and you understand how to use it, generally at least?
Click to expand...
Click to collapse
Yes fastboot worked at one time and so did twrp. I had reached the last stage of rooting which was installing supersu when the whole thing crashed. After my phone stopped working i went into recovery mode and used twrp to format my data and delete everything. Since then i havent been able to plug in a usb or go into recovery mode
enochthegreat said:
Yes fastboot worked at one time and so did twrp. I had reached the last stage of rooting which was installing supersu when the whole thing crashed. After my phone stopped working i went into recovery mode and used twrp to format my data and delete everything. Since then i havent been able to plug in a usb or go into recovery mode
Click to expand...
Click to collapse
Hmm... Sounds like bad luck, hopefully a new, quality cable will take care of it for you
Looks like it was all bad luck. A day after I bricked my phone my charger port broke
Hello
I tried a Nougat rom for the Nexus 4 which was available as a full update package (including system bootloader rom etc) and installed it with the update command from adb instead of from custom rom.
now my phone is bricked and I cant seem to get it fixed.
It either gets stuck in a bootloop, or i can force switch it to bootloader mode. From there I can go to recovery but the stock recovery is useless.
Problem is when i connect this to my windows 10 pc, it shows no sign of being detected. I installed drivers over and over including the universal ADB and fastboot drivers available here on XDA. it doesnt show up under adb devices command and even the Nexus 4 rootkit doesnt detect it as a phone.
I wanna make this phone working again. I'm guessing the way is to go back to stock image and then re-root and re-flash custom recovery and ROM. but even for this, it should be detected by the PC and adb command and rootkit right? Is there something I'm overlooking here?
This is the ROM I tried
https://forum.xda-developers.com/nexus-4/development/fake-nexus-rom-nexus-4-t3230268
The way to install it is also mentioned there and that is exactly what I did.
Did you try this adb installer: https://forum.xda-developers.com/showthread.php?t=2588979
In that thread, I read the people are able to use adb on Windows 10. If that doesn't work, find a Windows 7 PC or boot to ubuntu using bootable pendrive and flash the factory images using fastboot.
Nitin
nitin.chobhe said:
Did you try this adb installer: https://forum.xda-developers.com/showthread.php?t=2588979
In that thread, I read the people are able to use adb on Windows 10. If that doesn't work, find a Windows 7 PC or boot to ubuntu using bootable pendrive and flash the factory images using fastboot.
Nitin
Click to expand...
Click to collapse
So are you saying this is definitely a problem of Windows 10? I hadnt even considered that...
BluTheCool said:
So are you saying this is definitely a problem of Windows 10? I hadnt even considered that...
Click to expand...
Click to collapse
I read many users complaining about that. You can try that installer; as I mentioned - users have reported that they were able to use adb on Windows 10 after installing adb using that installer. If that doesn't work try the second suggestion (Ubuntu/ Linux)
Nitin
nitin.chobhe said:
I read many users complaining about that. You can try that installer; as I mentioned - users have reported that they were able to use abd on Windows 10 after installing adb using that installer. If that doesn't work try the second suggestion (Ubuntu/ Linux)
Nitin
Click to expand...
Click to collapse
i tried the installer but it made no difference. i tried it my win 7 partition as well but it didnt show up in the device manager.. i think usb debugging must have been disabled with my new rom flash. but even then i dont get why it wont show up as anything in devman...
any command i try ends with waiting for device and since i cant find the device in devman I cant even update the driver manually. I guess I could give linux a shot
Hey I finally figured out the problem. Its unbelievable. The usb port of the device was slightly bent in such a way that every cable I tried never really connected with the phone. I twisted it up a little and now its being detected as fastboot. The drivers you provided work like a charm now. Thanks for all the help !
BluTheCool said:
Hey I finally figured out the problem. Its unbelievable. The usb port of the device was slightly bent in such a way that every cable I tried never really connected with the phone. I twisted it up a little and now its being detected as fastboot. The drivers you provided work like a charm now. Thanks for all the help !
Click to expand...
Click to collapse
Glad that it helped, hope you get it revived soon :fingers-crossed:
Nitin
BluTheCool said:
Hey I finally figured out the problem. It's unbelievable. The USB port of the device was slightly bent in such a way that every cable I tried never really connected with the phone. I twisted it up a little and now it's being detected as fast boot. The drivers you provided work like a charm now. Thanks for all the help!
Click to expand...
Click to collapse
It seems I have the same prob, as my N4 too doesn't get detected. But my ph can charge with USB when I connect to PC.
How you twisted USB port? I mean it has very less room to insert any tool.
sandy7874 said:
It seems I have the same prob, as my N4 too doesn't get detected. But my ph can charge with USB when I connect to PC.
How you twisted USB port? I mean it has very less room to insert any tool.
Click to expand...
Click to collapse
Tell me one thing - can you boot to fastboot mode?
Nitin
nitin.chobhe said:
Tell me one thing - can you boot to fastboot mode?
Nitin
Click to expand...
Click to collapse
Yes I m able to boot to Fastboot mode.
sandy7874 said:
Yes I m able to boot to Fastboot mode.
Click to expand...
Click to collapse
Ping me on hangouts. My email ID is in my signature.
Nitin