Ok, guys. I tried every option on every forum and none of them worked so here I am.
I unlocked and rooted my nexus 4 using the Wugfresh toolkit v 1.9.3. Everything worked perfectly until I tried to flash Cyanhacker ROM and kernel at the same time. I factory reset my phone before doing that (wiped dalvik/cache etc.). In TWRP, it said everything was successful, however I got stuck in a bootloop and when I tried to factory reset again, I accidently wiped my OS as well (i know... i am a retard:cyclops. Now I can only go in fastboot and TWRP.Now, I tried to use Wugfresh toolkit to Flash Stock + Unroot while being in fastboot, but it states that "Fastboot device was not found". Suggestions?
Thanks in advance.
First of all check you have fastboot driver install for your Nexus 4.
After that, you can try to reboot again in bootloader and from fastboot command line write "fastboot devices".
If your device appear you can reimage your stock image.
If you could load TRWP recovery, from it you can use install from sideload to "reinstall" again the original or modify custom rom.
That's the problem, when I connect my phone to my PC, nothing happens. When i try to open device manager I dont see my phone or the Android ADB Interface.
it happened to me last week, use usbdeview (easily googled) to uninstall all your android related driver from it, don't forget to check the driver properties to delete the inf file also.
restart your pc and search then install universaladb driver (do some googley again) then try again. though last week my side here had to reinstall my xp from scratch to get mine working but i hope you aren't.
Related
Earlier today I flashed Kaos Droid to try it out, but it put my Nexus in a state where it would not go past the screen that says Google and has the lock at the bottom. Since I have TWRP, Reboot to recovery from boot loader didn't work. I tried fixing the problem in not Windows and Ubuntu, but Windows kept on ending up as unknown device and no matter what drivers I tried to make it use it would not take, and in Linux it didn't show up in adb devices. I got lucky and it rebooted into TWRP after my fifth try of selecting recovery from the boot loader. I restored from backup, but I don't want this to happen again, if that ever happens. What should I do to get it in adb devices? Thanks.
Sent from an 8-core device from 2015
usb debugging
Try
Code:
adb kill-server
adb start-server
Can't remember if you need superuser permissions or not.
thebobp said:
Try
Code:
adb kill-server
adb start-server
Can't remember if you need superuser permissions or not.
Click to expand...
Click to collapse
I tried that, didn't work.
sonikot said:
usb debugging
Click to expand...
Click to collapse
How could I turn that on from bootloader? It was and is on before flashing the ROM and after restore.
Should have been able to run fastboot commands, either to try to reboot into the existing recovery, reboot into a recovery image, or flash a new recovery.
Sent from my Nexus 7 using xda premium
jcracken said:
Earlier today I flashed Kaos Droid to try it out, but it put my Nexus in a state where it would not go past the screen that says Google and has the lock at the bottom. Since I have TWRP, Reboot to recovery from boot loader didn't work. I tried fixing the problem in not Windows and Ubuntu, but Windows kept on ending up as unknown device and no matter what drivers I tried to make it use it would not take, and in Linux it didn't show up in adb devices. I got lucky and it rebooted into TWRP after my fifth try of selecting recovery from the boot loader. I restored from backup, but I don't want this to happen again, if that ever happens. What should I do to get it in adb devices? Thanks.
Sent from an 8-core device from 2015
Click to expand...
Click to collapse
Have a look at the Device Manager in Windows with your tablet plugged in. If there's that yellow triangle, just right click and choose update driver. Then you just browse and point Windows to where you have your N7 drivers.
akbar26 said:
Have a look at the Device Manager in Windows with your tablet plugged in. If there's that yellow triangle, just right click and choose update driver. Then you just browse and point Windows to where you have your N7 drivers.
Click to expand...
Click to collapse
That's the thing, I pointed it to official N7 drivers, Google USB Drivers, SuperOneClick drivers, and a bunch of other ones. It would never take--saying either that the best drivers are already installed (even though none were installed) or no suitable drivers exist in that directory.
I'm having a similar issue here, except I can get to the "X" boot animation.
jcracken said:
That's the thing, I pointed it to official N7 drivers, Google USB Drivers, SuperOneClick drivers, and a bunch of other ones. It would never take--saying either that the best drivers are already installed (even though none were installed) or no suitable drivers exist in that directory.
Click to expand...
Click to collapse
same problem here ... did u ever solve it ?
sonikot said:
usb debugging
Click to expand...
Click to collapse
Sometimes it seems to me that, even though USB debugging is "on", it really isn't.
Several times I have had to un-check and re-check "USB debugging" before adb would recognize the device.
Just my experience. Your milage may vary.
i'm in the same boat !
,
Any ?
Are you on 4.2.2? There now should be a security dialog upon executing an ADB command on the device, it will prompt you to allow the command to be executed.
If tou aren't on 4.2.2 - then it seems to be either a driver or a ROM issue
Yes I'm on 4.2.
I had this problem too and reinstalling the SDK tools fixed it for me for some reason.
Sent from my Paranoid 3.0 Nexus7 running M-Kernel mr1
I reinstall sdk without sucess
Maybe try using wugfresh toolkit. I've seen people say they couldn't use adb or fastboot but the toolkit worked. Doesn't really make sense to me since the toolkit just sends the commands for you but hey, worth a shot. It will walk you through uninstalling current drivers and doing a fresh driver install also.
Sent from my Paranoid 3.0 Nexus7 running M-Kernel mr1
travisjustin said:
Maybe try using wugfresh toolkit. I've seen people say they couldn't use adb or fastboot but the toolkit worked. Doesn't really make sense to me since the toolkit just sends the commands for you but hey, worth a shot. It will walk you through uninstalling current drivers and doing a fresh driver install also.
Sent from my Paranoid 3.0 Nexus7 running M-Kernel mr1
Click to expand...
Click to collapse
I use this kit. Remove all drivers. Then install the driver again. The drivers has been install in fastboot mode and recovery mode. The nexcus is recognized in these mode by the wugfresh toolkit.
Unfortunately in normal mode, when i active usb debug mode, i get a unkown device on windows 7 32 with any possibility to update the drivers.
I get error unkow device, device is stop error 43
Cable is stock and also try another one.
I get same message error on another computer with windows 8
I confirm that my usb issue is solved.
After a factory reset, i reinstall the last release Usb ROM and USB comes back to life on my nexus.
The nexus is no more recognized as unkown device by my computer and i can install the adb driver.
During this story, i try also to get acces via wifi but was unable to connect even with adb over wifi enable on the nexus.
That why Timur recommands me to made a full factory reset.
My problem seems to be due to corrupt data that block every connections between the computer and the nexus (adb wifi and usb) based on last 4.2.2 new safety features.
So far i recommand full wipe between two rom install to avoid such trouble.
Thank a lot to timur for his support during the week end.
If your nexus is rooted, go in recovery mode and install a new rom from zip.
How to ?
Download rom of your choice via wifi
You can download a rom directly from your nexus to sd.
Check here for download (example)
http://mehrvarz.github.com/nexus-7-usbrom/
Download Google applications on your nexus via wifi
Download from here : http://donandroid.com/gapps
Before installing new rom make a save using titanium backup.
https://play.google.com/store/apps/details?id=com.keramidas.TitaniumBackup&hl=fr
Save all your application and data in batch mode.
Create titanium.zip on your nexus 7 sd.
Then from recovery mode make a full wipe but without erasing sd data.
Follow these instructions :
Unless you format the system partition and system caches, you aint wiped nothing, there is only one way to carry out a proper full wipe, and thats the full wipe the correct way.
1. Boot into recovery
2. Wipe the cache partition
3. Go to advanced and wipe dalvik and batt stats.
4. Go back to mounts and storage and format system, then data, then cache.
5. Go back and install the rom zip file from the sd card.
6. Reboot.
No need to wipe data/factory reset, the contents of your internal and external sd cards are untouched.
From Recovery mode
- install titanium.zip.
- install gapps.zip
Reboot
Go to titanium backup and recover all your data.
Et voila...
I'm using Wug's Nexus Root Toolkit v1.7.9 to root and flash a recovery but it never completes. It hangs when trying to run TWRP
Nexus 10
4.4, build KRT16S, bone stock
unlocked
- In NRT choose Root (with or without custom recovery)
- It reboots into fastboot OK
- it boots the temporary boot OK
- it pushes the root files OK
- it reboots into fastboot OK
- when it trys to temporary boot into TWRP fastboot says
"FASTBOOT STATUS - DATA007bf800" and hangs
NRT hanges and I have to force quit it.
I can reboot the Nexus by holding PWR for 5seconds. It's not rooted (of course). I can reboot to stock recovery just fine. The tablet otherwise works fine.
The problem seems to be when NRT tries to run TWRP.
Interestingly, even if I set NRT options to use CWM, it still tries to boot into TWRP.
Any ideas?
mageus said:
I'm using Wug's Nexus Root Toolkit v1.7.9 to root and flash a recovery but it never completes. It hangs when trying to run TWRP
Nexus 10
4.4, build KRT16S, bone stock
unlocked
- In NRT choose Root (with or without custom recovery)
- It reboots into fastboot OK
- it boots the temporary boot OK
- it pushes the root files OK
- it reboots into fastboot OK
- when it trys to temporary boot into TWRP fastboot says
"FASTBOOT STATUS - DATA007bf800" and hangs
NRT hanges and I have to force quit it.
I can reboot the Nexus by holding PWR for 5seconds. It's not rooted (of course). I can reboot to stock recovery just fine. The tablet otherwise works fine.
The problem seems to be when NRT tries to run TWRP.
Interestingly, even if I set NRT options to use CWM, it still tries to boot into TWRP.
Any ideas?
Click to expand...
Click to collapse
I did exactly as you only a couple of days ago. I plugged into a different USB port and it worked the 2nd time.
IT still though got into a bootloop (the graphics on the startup never stop) so pressed all 3 buttons many times then did a factory reset then was golden thereafter.
Good luck.
nigelhealy said:
I did exactly as you only a couple of days ago. I plugged into a different USB port and it worked the 2nd time.
Click to expand...
Click to collapse
Did you have the "FASTBOOT STATUS - DATAXXXX" error?
I've seen tons of posts about "FASTBOOT STATUS - FAIL INVALID" messages, but that's not what's happening here. It sounds like a memory error, either a bad file read, or physical RAM error. I verified the hash on NRTs copy of TWRP, so that's not the problem.
I tried 3 different USB cables and 2 different USB ports. No help.
I'll try to manually sideload TWRP via Fastboot today, but am not hopeful.
mageus said:
Did you have the "FASTBOOT STATUS - DATAXXXX" error?
I've seen tons of posts about "FASTBOOT STATUS - FAIL INVALID" messages, but that's not what's happening here. It sounds like a memory error, either a bad file read, or physical RAM error. I verified the hash on NRTs copy of TWRP, so that's not the problem.
I tried 3 different USB cables and 2 different USB ports. No help.
I'll try to manually sideload TWRP via Fastboot today, but am not hopeful.
Click to expand...
Click to collapse
So I've been doing for my 3 Android devices (N4, N7, N10), doing stock install of 4.2.2, 4.3, 4.4 and doing some benchmarks, so I've been doing loads of stock flash, root, some with / without custom recovery.
One combination, I can't recall which, which sounds most similar to yours, what I did was NOT have any custom recovery installed, a pure simply stock install, and then simple rooted it with NO custom recovery, then I could get past the problem similar to yours, I installed ROM Manager and let it install a customer recovery.
I have got the impression from the 3-4 stock installs I done last 4 days on my N10, that WUGS TWRP+N10 is not as stable as WUGS TWRP+N7 or WUGS TWRP+N4. It seems better either WUGS + N10 + no custom recovery, or that other one (Koush?). You can add custom recovery post setup so long as you're rooted, ROM Manager is what I used.
FYI having tried 4.2.2, 4.3, 4.4, then back to 4.3, i've settled on 4.4, and on all my 3 Android devices, each though with a different kernel - N10 doesn't have Franco but it also has USB driver issues (thanks Samsung and Google) but found a kernel which put them back in.
I sideloaded TWRP 2.6.3.1 via fastboot. Piece of cake. TWRP even asked to install SuperSU, which I did.
Nigel, I think you're right. There may be issues with NRT, TWRP 2631, and the Nexus 10.
nigelhealy said:
I plugged into a different USB port and it worked the 2nd time.
Click to expand...
Click to collapse
HOLY COW.....I've flashed CWM, TWRP, and CWM Touch multiple times...nothing.
I changed USB ports and get it the first time.
I tried installing CM with CM Installer for MAC ... until it got stuck in bootloop.
Using adb I pushed image, still bootloop.
Reset to factory, cleared partition, flushed dalvik cache, all the same.
adb commands seem to work since I can make the phone reset and so forth.
details:
mako 16 GB
HW version - rev_11
bootloader version MAKOZ30d
baseband M9615A-CEFWMAZM02.0.1701.02
signing - production
secure boot - enabled
lock state - unlocked
recovery mode is CWM v6.0.4.7 (assuming it got installed by the CM installer for MAC)
tried by hand to resuscitate with cm-11-20141008-SNAPSHOT-M11-mako.zip and cm-11-20141107-NIGHTLY-mako.zip using sideload to no avail - still bootloops despite numerous factory resets and cache partition wipes.
any ideas please?
thanks
This is what i use: http://forum.xda-developers.com/nex...olkit-wugs-nexus-root-toolkit-v1-8-2-t2015469
Has multiple options for going back to stock, rooting, and lots of other things.
TreatnHerRight said:
This is what i use: http://forum.xda-developers.com/nex...olkit-wugs-nexus-root-toolkit-v1-8-2-t2015469
Has multiple options for going back to stock, rooting, and lots of other things.
Click to expand...
Click to collapse
That looks great ... and uses Windows only
I can boot Windows under VMWare Fusion on my MAC however not 100% sure if that would work within that environment as I need to do some USB passthrough.
Thanks for the pointer though.
ilmoomino said:
I tried installing CM with CM Installer for MAC ... until it got stuck in bootloop.
Using adb I pushed image, still bootloop.
Reset to factory, cleared partition, flushed dalvik cache, all the same.
adb commands seem to work since I can make the phone reset and so forth.
details:
mako 16 GB
HW version - rev_11
bootloader version MAKOZ30d
baseband M9615A-CEFWMAZM02.0.1701.02
signing - production
secure boot - enabled
lock state - unlocked
recovery mode is CWM v6.0.4.7 (assuming it got installed by the CM installer for MAC)
tried by hand to resuscitate with cm-11-20141008-SNAPSHOT-M11-mako.zip and cm-11-20141107-NIGHTLY-mako.zip using sideload to no avail - still bootloops despite numerous factory resets and cache partition wipes.
any ideas please?
thanks
Click to expand...
Click to collapse
Honestly, when I get into these situations I just flash the stock images and use that as a starting point. (I'm guessing your recovery is still working fine, given what you've said, so you can pull that out of the zip it sends so it doesn't write over it)
My approach, however, is usually, "damn, I messed up, let's go back to a known good point and try again" though, so keep that in mind if you decide to follow this path.
nic0lette said:
Honestly, when I get into these situations I just flash the stock images and use that as a starting point. (I'm guessing your recovery is still working fine, given what you've said, so you can pull that out of the zip it sends so it doesn't write over it)
My approach, however, is usually, "damn, I messed up, let's go back to a known good point and try again" though, so keep that in mind if you decide to follow this path.
Click to expand...
Click to collapse
That didn't work either (the restore to stock).
The USB passthrough on VMWare fusion works like a charm, ADB sees the device, passing commands on from the Windows application, rebooting and so forth.
However once it goes through the repair process at some point I get some strange cyan screen with white and lilac blinking lines and the program keeps saying "waiting for your device (or phone, or whatever" ...
Losing the will to live.
ilmoomino said:
That didn't work either (the restore to stock).
The USB passthrough on VMWare fusion works like a charm, ADB sees the device, passing commands on from the Windows application, rebooting and so forth.
However once it goes through the repair process at some point I get some strange cyan screen with white and lilac blinking lines and the program keeps saying "waiting for your device (or phone, or whatever" ...
Losing the will to live.
Click to expand...
Click to collapse
Why are you using VMWare? You should be able to download the tools you need for WIndows, Mac, or Linux.
Go and grab the Android SDK and install the "Android SDK Platoform-tools" and download 4.4.4 image from Google.
Once you have those two things, unzip the factory image and do "adb reboot bootloader" and then run "sh flash-all.sh" from a command prompt. This will use fastboot to write an img file to the partitions on the device, so if you can't run the SDK tools, for whatever reason, use fastboot to run the commands in the file. (That is, don't use recovery and adb sideload, do it through fastboot)
The -w option will wipe your data, so if you want you can try and run the last line (fastboot -w update image-occam-ktu84p.zip) without the "-w", but if it doesn't work then I'd try it again with it.
If you can boot into the bootloader and recovery then your device isn't dead. Worst case you have to go to a friend's place and flash it there.
nic0lette said:
Why are you using VMWare? You should be able to download the tools you need for WIndows, Mac, or Linux.
Go and grab the Android SDK and install the "Android SDK Platoform-tools" and download 4.4.4 image from Google.
Once you have those two things, unzip the factory image and do "adb reboot bootloader" and then run "sh flash-all.sh" from a command prompt. This will use fastboot to write an img file to the partitions on the device, so if you can't run the SDK tools, for whatever reason, use fastboot to run the commands in the file. (That is, don't use recovery and adb sideload, do it through fastboot)
The -w option will wipe your data, so if you want you can try and run the last line (fastboot -w update image-occam-ktu84p.zip) without the "-w", but if it doesn't work then I'd try it again with it.
If you can boot into the bootloader and recovery then your device isn't dead. Worst case you have to go to a friend's place and flash it there.
Click to expand...
Click to collapse
I am using VMWare Fusion since my Windows work laptop is dead (courtesy of lost charger).
So I must use my Mac (which used the CM installer where things went sour).
Doubt it is a problem since I can get ADB to work.
I have already dowloaded the Android SDK Platoform-tools and stock 4.4.4.
I used ADB on MAC, but after I copy the ROM the phone does some scroll-bar progress, then I clear partitions/factory erase/cache ... and boot loop again.
I will follow your advice and use the described process.
You are right - as long as I have bootloader I am safe.
Might go and buy Moto X+1 or Sony X3 ... as I want to go 4G but thought might use the N4 for another few months.
thanks
following instructions from nic0lette I have now my phone back to normal ...
will try CM using the same instructions ... well, using the flash-all.sh as a base script
thanks (and "thanked")
I am having trouble using WUG Nexus Root ToolKit.
Windows 7 (64 bit)
Run as Administrator
----------------------------------------
I open the toolkit see the first window where you are prompted to select your device. I do along with the correct version. Next the popup comes up asking me to put the device in dubugging mode, I am unable to do so with me not being able to boot.
--------------
I am stuck in a bootloop and have been for about three days.
I manually flashed ClockWork Recovery touch with Fastboot.
Tried flashing stock images manually from Fastboot
Tried Flashing Ubuntu from Ubuntu PC (received errors "Cache formatting not successful - flash may fail")
--------------
The Toolkit is stuck in the system tray and I am unable to do anything
Wug_Updater_Nexus.exe is in the system tray sometimes as well. I cannot see the toolkit or right click on the system tray icon. I did some Google searching and have not had any finds on this specific problem.
Am I just an idiot?
-----------------------------------------
EVERY TIME I try to reboot my device via ClockWork or TWRP it always prompts me to root my device, however it does not work. Still in BootLoop.
Just a note, I just replaced the screen and found a similar post
http://forum.xda-developers.com/nexus-4/help/nexus-4-endless-bootloop-help-t3087736
Nexus 4 Stuck at boot screen after replacing the LCD/Digitizer
Tried reseating/replacing all connections still no luck :crying: :crying:
Reverted from CM 10.2 to stock 4.4, Stuck in a bootloop
I wish we could change the title of this post or make a new sticky post about the proximity sensor not working after screen install
Downgrade the Radio to the original version and that will allow you to boot.
radio-mako-m9615a-cefwmazm-2.0.1700.48.img
After manually flashing each partition, are you running the fastboot commands to "fasboot erase userdata" and to "fastboot flash userdata userdata.img" before booting for the first time?
so i feel like Ive tried everything.
tried to flash a rom and gapps in twrp and phone booted to warning screen with the yellow triangle.
passes that and then goes to google splash screen with unlock icon. and then repeats to the cycle.
i have tried multiple 6.x.x builds using skipsoft toolkit with no change.
i have installed twrp and tried to flash 6.x.x rom and 7.0.0 rom.
i have tried to flash stock NBD90X 7.0.0 using nexus root toolkit.
i have tried going into stock recovery and wipe data/factory reset
i have tried minimal ABD fastboot and running the commands manually.
All have failed to change the boot looping i experience.
my phone is unlocked.
computer can see it as fastboot devices
computer CANNOT see it under abd devices
i am able to install and get into TWRP using skipsoft tookkit.
i feel like i am running out of things to flash onto the device haha
any help is appreciated.
barrackOBAMA said:
i have tried multiple 6.x.x builds using skipsoft toolkit with no change.
i have installed twrp and tried to flash 6.x.x rom and 7.0.0 rom.
i have tried to flash stock NBD90X 7.0.0 using nexus root toolkit.
i have tried going into stock recovery and wipe data/factory reset
i have tried minimal ABD fastboot and running the commands manually.
All have failed to change the boot looping i experience.
Click to expand...
Click to collapse
First, I'd recommend staying away from Toolkits, as you can't really see what's happening and diagnose issues. Since you've used fastboot/ADB commands, you know they are faster anyway. When you say your PC can't recognize your device in ADB, was your device in recovery? Make sure you're in recovery and you're ready to receive ADB commands. If you CAN see your phone with fastboot that means you're in the bootloader, whereas you have to boot into recovery to see your device via ADB.
Also, you didn't outline anything else you may have done. Did you restore from a nandroid with a buggy version of TWRP? Your issue sounds like the TWRP EFS restore bug (3.0.2-2). It effectively bricks your device, but there is a thread here that discusses it. Effectively you need to be recovery ADB mode and run a couple commands to delete your EFS partition and that will fix the issue.
More info here: http://forum.xda-developers.com/nexus-6p/help/im-stuck-google-logo-stop-reboots-twrp-t3452842
Make sure you've also installed the updated 3.0.2-3 TWRP as it will work with encrypted data and doesn't have the EFS bug.