So Here's The Story I Rooted My Phone Installed TWRP and Magisk Here Were I Folded I Forgot To Turn on USB Debugging Or Make A Backup and I tried Flashing a font and it got stuck in a bootloop this all happened while I was smoking weed and for that reason I big panicked and went to TWRP first did a factory reset that didn't work so I said **** it I'll do an advanced clean and flash everything through adb turns out I didn't turn on USB Debugging so now my computer doesn't recognize my phone
go here it will work https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448 if it's not your brand easily can find others but it will work
As long as can get into fastboot just use msntool return it to stock and start again I do it all time when I screw stuff up , lol
Sent from my ONEPLUS A6013 using Tapatalk
Related
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 Guys/girls
I received my nexus 7 today (its lovely!) and then proceeded to attempt to root it so I can change the dpi etc.
I unlocked the bootloader using the Nexus 7 toolkit and that worked fine.
I then went to do the one click to root/flash etc and then got stuck on downloading boot.img.
After leaving it for a few hours I gave up and the nexus booted straight back into the os.
My next attempt was to root using the su binarys via fastboot. This again failed on sending the file. I also noticed that my device is locked at fastboot mode when the usb cable is plugged in, e.g the up/down doesn't work unless I unplug the cable. I have tried different cables and a different PC!
My next step was then to use the toolkit to reset back to factory incase I had screwed something up, so this deleted the bootloader etc as it should and then froze on sending the .img across.
I now have a un responsive fastboot when usb is plugged in and no recovery or bootable tablet, any hints/solutions?
Thanks
herghost said:
Hi Guys/girls
I received my nexus 7 today (its lovely!) and then proceeded to attempt to root it so I can change the dpi etc.
I unlocked the bootloader using the Nexus 7 toolkit and that worked fine.
I then went to do the one click to root/flash etc and then got stuck on downloading boot.img.
After leaving it for a few hours I gave up and the nexus booted straight back into the os.
My next attempt was to root using the su binarys via fastboot. This again failed on sending the file. I also noticed that my device is locked at fastboot mode when the usb cable is plugged in, e.g the up/down doesn't work unless I unplug the cable. I have tried different cables and a different PC!
My next step was then to use the toolkit to reset back to factory incase I had screwed something up, so this deleted the bootloader etc as it should and then froze on sending the .img across.
I now have a un responsive fastboot when usb is plugged in and no recovery or bootable tablet, any hints/solutions?
Thanks
Click to expand...
Click to collapse
yes, actually : D
download this
http://forum.xda-developers.com/showthread.php?t=1809195
if you dont have that one.
pick your device from the list.
install the drivers for your device with device unplugged
make sure the device is fully off
plug in into the computer and hold down the power and volume buttons
windows should pop up saying nexus 7 bootloader driver successfully installed and then you can use the whole fastboot menu thing without a problem and reboot to recovery or whatever.
my suggestion is to install twrp recovery project 2.x.x.x
oh yeah, its a bug with the bootloader that it freezes when you plug the usb cable into the wall or a computer without the proper drivers
jombo2323 said:
yes, actually : D
download this
http://forum.xda-developers.com/showthread.php?t=1809195
if you dont have that one.
pick your device from the list.
install the drivers for your device with device unplugged
make sure the device is fully off
plug in into the computer and hold down the power and volume buttons
windows should pop up saying nexus 7 bootloader driver successfully installed and then you can use the whole fastboot menu thing without a problem and reboot to recovery or whatever.
my suggestion is to install twrp recovery project 2.x.x.x
oh yeah, its a bug with the bootloader that it freezes when you plug the usb cable into the wall or a computer without the proper drivers
Click to expand...
Click to collapse
Thanks for your reply, thats what I did in the first place! Removed and tried again but same issue
herghost said:
Thanks for your reply, thats what I did in the first place! Removed and tried again but same issue
Click to expand...
Click to collapse
you are 100% positive you did EXACTLY what i said?
I have no idea what went wrong
That's the problem with toolkits though. People don't know what they're doing and when something goes wrong you don't know how to fix it!! I understand where toolkits come from, but they are only useful if you know what happens in the background when you click on a button.
Thread Moved
Thread belongs in Q&A. Not the Dev Forum
Post moved.
MD
I mess with several android and other devices on my notebook..
Doing so i install drivers for them and often have the exact same issue as you are having..
Do a search for a program called usbdview.. Install to your pc..
With the nexus unplugged run the program..Delete everything in the list that you do NOT HAVE plugged into your computer..Especially anything that says ADB.. OR ANDROID..
Plug in the nexus 7 refresh the list.. and delete the entries created for it..
Unplug the nexus .. reboot the pc.. Then download or use the tool kit to install the latest Adb drivers for nexus 7 ..
reboot the pc.. then plug in the nexus ..
After doing the above see if you can now use fastboot/ adb...
The above will insure its not a driver issue.Often computers get usb devices confused and causes them to hang ..
Good Luck
erica_renee said:
I mess with several android and other devices on my notebook..
Doing so i install drivers for them and often have the exact same issue as you are having..
Do a search for a program called usbdview.. Install to your pc..
With the nexus unplugged run the program..Delete everything in the list that you do NOT HAVE plugged into your computer..Especially anything that says ADB.. OR ANDROID..
Plug in the nexus 7 refresh the list.. and delete the entries created for it..
Unplug the nexus .. reboot the pc.. Then download or use the tool kit to install the latest Adb drivers for nexus 7 ..
reboot the pc.. then plug in the nexus ..
After doing the above see if you can now use fastboot/ adb...
The above will insure its not a driver issue.Often computers get usb devices confused and causes them to hang ..
Good Luck
Click to expand...
Click to collapse
You Star
Put me on the right track, my PC was basically assuming that it was my S3, in the end I removed everything with samsung in it from the registry, uninstalled all the drivers then tried again, correctly showing as a nexus and not a samsung
Hi all, I dropped and broke the screen of my rooted Nexus 4. I purchased a replacement screen/digitizer, but when I turned on the phone after installing I found it in boot loop. I went into recovery mode and wiped cache partition, dalvik-cache, but that didn’t help. Then I did a factory reset, which didn’t solve the problem either. I must have wiped usb debugging because now I can’t get fastboot or adb commands to work and my computer doesn’t recognize my phone anymore. I can access recovery mode but I am still stuck in boot loop. Any way to get my phone running again, or at least able to get my phone and computer (Mac) to see each other again? Thanks!
Make sure you have latest adb and fastboot SDK files installed. Debugging has no link to fastboot.
Sent from my Nexus 4
I have latest adb and fastboot SDK files installed. I was able to use adb and fastboot commands before I wiped my device, but not anymore
So I ended up getting a new phone -- Zenfone 2 -- and devices wasn't showing up. On a whim, I tried a different USB cable today and it worked! I hooked up my Nexus 4 with this cable and it also worked! Could've been such an easy solution.
I really liked my Nexus 4 and was hoping to eek out another year or so out of it but now I'm out the cost of a digitizer/lcd and another $300 for the Zenfone 2, but I guess it'll become my backup phone. Just wanted give an update and warn others to try switching cables before writing it off like I did.
So as the title says, I recently lost control of my phone and in a panic full wiped everything. I figured this wouldn't be such a big problem as the hardware was fine, however, I'm now realizing that without developer mode and usb debugging enabled I can't do ANYTHING. I've tried to reflash stock via adb but the device isn't recognized, likely for the above reasons. Under normal circumstances I would just plug my phone into my computer and use MTP to move a rom over, however since the default mode is USB charging and I don't have have an OS installed, it seems I can't change that.
I've been told that it's essentially impossible to brick a nexus nowadays, but I feel like I somehow managed and for the silliest reasons. . Someone please help.
Edit: I should mention that I still have access to TWRP somehow.
cri7ica1 said:
So as the title says, I recently lost control of my phone and in a panic full wiped everything. I figured this wouldn't be such a big problem as the hardware was fine, however, I'm now realizing that without developer mode and usb debugging enabled I can't do ANYTHING. I've tried to reflash stock via adb but the device isn't recognized, likely for the above reasons. Under normal circumstances I would just plug my phone into my computer and use MTP to move a rom over, however since the default mode is USB charging and I don't have have an OS installed, it seems I can't change that.
I've been told that it's essentially impossible to brick a nexus nowadays, but I feel like I somehow managed and for the silliest reasons. . Someone please help.
Edit: I should mention that I still have access to TWRP somehow.
Click to expand...
Click to collapse
While in TWRP, use ADB Sideload and install the latest OTA zip from Google:
https://developers.google.com/android/nexus/images?hl=en
Edit: How did you reflash stock? Because you should be able to do the above, ADB push, or drag and drop via TWRP. You may have to mount the file system before doing so.
Sent from my Nexus 5X using Tapatalk
cri7ica1 said:
So as the title says, I recently lost control of my phone and in a panic full wiped everything. I figured this wouldn't be such a big problem as the hardware was fine, however, I'm now realizing that without developer mode and usb debugging enabled I can't do ANYTHING. I've tried to reflash stock via adb but the device isn't recognized, likely for the above reasons. Under normal circumstances I would just plug my phone into my computer and use MTP to move a rom over, however since the default mode is USB charging and I don't have have an OS installed, it seems I can't change that.
I've been told that it's essentially impossible to brick a nexus nowadays, but I feel like I somehow managed and for the silliest reasons. . Someone please help.
Edit: I should mention that I still have access to TWRP somehow.
Click to expand...
Click to collapse
USB OTG pre-populated with a ROM maybe?
DEVICE: OnePlus 6T T-Mobile flashed to International 10.3.8 OOS bluspark kernel, Magisk, TWRP, unlocked boot loader.
CURRENT SITUATION: Currently, lost magisk, twrp, and am factory reset/wiped to stock OOS 10.3.8 have no USB function through OTG, EDL, Fastboot, or ADB. I HAD all of that properly setup and working just days ago. USB only works for charging now. Phone “works” otherwise. Just can’t use USB for DATA, or push recovery, root it now. Which my main reason I bought this phone used was for having root.
HOW: I had everything running and setup how I wanted. But in TWRP recently (not from beginning of owning the device) when I flashed stuff or switch slot A/B in TWRP I would get a warning saying “unable to mount storage” even though the flash file would complete successfully and slot would change. Then when plugging in my USB C OTG drive the phone no longer picked it up. THEN I noticed I couldn’t ADB into the phone. I plugged it into the same cable and USB 2.0 port that had been used fine for a couple weeks. So even though I had everything working fine otherwise I decided to “fix” this problem and try some things which stupidly got me to now a “kinda working” never again to be rooted device. Useless to me. I thought I would reach out here for last ditch effort for any options I missed before trying to sell on eBay for whatever I can for the state it’s in. Can’t post on OnePlus forums for two weeks and OnePlus support sent me template support reply that was no help. Repair would cost more than what I paid for the phone anyway.
I HAVE TRIED: Different cables, different PCs and ports. Full reset from stock recovery option, installing 10.3.8 zip in Local Upgrade to see if it would help anything. I have USB debugging on. No matter what when I plug it into PC I get nothing in Device Manager pop up, no indication from my computer anything has been plugged in. Only thing that happens is the phone starts charging. Doesn’t matter if in OOS, or boot loader. Trying to boot to EDL does nothing. My previously installed Qualcomm driver didn’t indicate anything was plugged in neither does MSM tool. Uninstalled reinstalled drivers. Nada. Think it’s a hardware problem because the phone should pick up in edl or fast boot at least, or the OTG stick. But nothing. Sucks. Hindsight if I had known this was going to be the result I would have never messed with it and left as it was rooted and recovery. Now it’s just a no fun device I’m going to have to part with. Also of note if I have the cable plugged in and try to reboot the phone doesn’t power back on. I have to unplug it then hold volume + PWR to get it to turn back on.
Thanks for reading maybe someone has options but I’m thinking I’m SOL without USB function I can’t get recovery or root back ever.