Hello all
Trying to figure out some issues with my nexus 7.
I was loading up a game, and hit back. The device froze, and I attempted to reboot. Would freeze at "google" screen.
I've tried to do a factory reset via recovery mode, and it simply returns that it cannot mount the partitions, with the "invalid argument" as the reason.
I've attempted to manually wipe the directories via fastboot, but it always fails with the same error. Invalid argument.
It would appear my file structure is gone, and I cannot load the stock because when I attempt to unlock my fastboot it freezes on removing "userdata"
I've tried 3 PCs, all different cables, usb 1,2 and 3. I've used the Asus USB drivers, and the universal. I've tried Wugs methods, which simply render the same error, just quicker.
adb sideloading also fails. It just seems I cannot get anything to write on the sdcc.
fastboot oem ? - fails
fastboot oem h - fails
Only thing that works, is the listing of the device in adb/fastboot - It will prompt for the unlock, but once hitting yes it freeze. Sat for 2 hours, nothing.
Any ideas?
Wrong forum try the nexus 7 2013 forum. If fastboot OEM unlock fails and adb sideloading fails then its most likely a corrupted nand partition has made the internal memory unwritable that would mean RMA or a new motherboard
Sent from my C5303 using xda app-developers app
Related
Hello,
I was attempting to update from 4.3 SlimBean to 4.4 SlimKat Weekly.
I booted into CWM Recovery, wiped system, cache, dalvik cache etc, and went to flash the rom.
The rom must have been corrupt or something, as I was unable to and received an error.
I rebooted and was stuck in fastboot.
From here, I've tried both Wug's Nexus Root toolkit, and the Skip Root toolkit.
Running the return to stock and unroot whilst in fastboot in either of them caused a crash of fastboot.exe and the Skip Root equivalent.
After a reboot Wug's allowed me to atleast run the program, but I received link errors, so tried again. This time it couldn't find it, unplug, replug. Link errors, cant find it and this repeated.
Skip also allowed me to after reboot, but gave the exact same faults.
That's as far as I've really got. I occasionaly get it to run, and it seems to work only for it to get part way in, sometimes after sending the bootloader, or on the bootloader and it can not find any devices.
For some extra info, this is Running Windows 8.1, using a USB 3.0 Front panel header and tried using default cable, samsung and kindle ones too.
I'm looking for any ideas? Worst case scenario is I can try when I'm back home at the weekend and there I have a PC with XP that I have used previously to fix this style of boot error.
Cheers,
WiiManic
Stop using toolkits, issues love to pop up for those who do
Make sure bootloader is still unlocked
If not
fastboot oem unlock
Flash latest twrp or cwm or whatever, just download the image and open cmd in this location
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash recovery nameofrecovery.img
Now boot to new recovery
Go to advanced
Adb sideload
On PC go to ROM of choice, maybe slimbean
adb sideload nameofrom.zip
When complete
adb sideload nameofgappsoranythingelseneeded.zip
Reboot
Sent from my Nexus 4 using XDA Premium 4 mobile app
Hello,
Tried to update to lollipop like the rest of the world..well, i should have waited
At first i just ran the flash-all.bat (edited so it didn't include erase userdata and the -w option)
fastboot threw all sorts of errors, too many links, invalid argument
then i tried to run manually the commands, same thing. Not all of them "worked" at once.
Unfortunately I don't have a log.
So now i have a N7 that won't boot past the Google screen
I can get to bootloader but it shows on device manager as Unknown USB device, Device Descriptor Request Failed, so fastboot doesnt help.
I can also get to stock recovery and use adb just fine.
Is there anyway to fix this? sideloading anything?
So I followed the XDA guide on rooting. After getting back to the setup screen, I constantly got:
Unfortunately, the process com.google.process.gapps has stopped.
It was literally constant to the point where I could only type one letter at a time. Okay, so I tried factory reset via TWRP. No good. So I downloaded a factory image and tried to flash it, and now my phone sits at the Google/padlock screen forever.
What do I do? I still have fastboot and TWRP access. I'm not sure the images are completely copying to the Nexus when I try to put them directly on the phone. Using Google's image and flash-all command ends in:
writing 'system'...
FAILED (remote: unknown command)
I don't understand this. Please help me. I can't use my phone at all.
Are you unlocked? Can you fastboot flash?
I can, yes. I figured out at least part of my problem - the USB 3 port on my laptop is misbehaving somehow. The USB 2 port works. I was able to fastboot flash. It remains to be seen why I had the gapps issue originally...
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?
Ok, I'm going to start by explaining everything I did up to this point to eliminate any troubleshooting sugggestions i may have already done.
I rooted and installed recovery the same way everyone else did. After a couple of days, I tried to install a ROM but im assuming i was encrypted because i was stuck in a loop that would only boot me into TWRP. Did my research and took the necessary steps to get around that and decrypt and boot into the new ROM.. FINALLY!!! Only one problem, this rom doesn't have Super SU installed, Alright... so i download the proper Super SU build and put it on my Micro SD card and try to boot into TWRP to flash....
This is where the problem begins. I never get the prompt to authorize my PC from my phone to allow anything, and i never did each time i reset. I'm almost certain the adb on this rom is messed up, i've wiped about 4-5 times to re-enable usb debugging from scratch in order to adb or fastboot into recovery via command prompt, however when i try adb, i get that unauthorized error an there's no option on the LG V20 to revoke under developer settings. Fastboot i just get the same "waiting for device" message. Also keep in mind that i set it to photo mode, every mode that was available and nothing. Tried different USB Cords and did this on both my laptop and my PC at work
I've tried uninstalling and reinstalling all of the drivers, re-installed the latest version of adb and fastboot to my PC, that didn't work either. Tried deleting the adbkeys file in the .android folder and still nothing.
When i try to boot in recovery manually, i just get the wipe data option and when i click yes to everything, it actually wipes my data. I'm unable to reflash TWRP because I can't access ADB or Fastboot due to the unauthorized error.
Someone, PLEASE HELP!!!!
any luck?
ahq1216 said:
Ok, I'm going to start by explaining everything I did up to this point to eliminate any troubleshooting sugggestions i may have already done.
I rooted and installed recovery the same way everyone else did. After a couple of days, I tried to install a ROM but im assuming i was encrypted because i was stuck in a loop that would only boot me into TWRP. Did my research and took the necessary steps to get around that and decrypt and boot into the new ROM.. FINALLY!!! Only one problem, this rom doesn't have Super SU installed, Alright... so i download the proper Super SU build and put it on my Micro SD card and try to boot into TWRP to flash....
This is where the problem begins. I never get the prompt to authorize my PC from my phone to allow anything, and i never did each time i reset. I'm almost certain the adb on this rom is messed up, i've wiped about 4-5 times to re-enable usb debugging from scratch in order to adb or fastboot into recovery via command prompt, however when i try adb, i get that unauthorized error an there's no option on the LG V20 to revoke under developer settings. Fastboot i just get the same "waiting for device" message. Also keep in mind that i set it to photo mode, every mode that was available and nothing. Tried different USB Cords and did this on both my laptop and my PC at work
I've tried uninstalling and reinstalling all of the drivers, re-installed the latest version of adb and fastboot to my PC, that didn't work either. Tried deleting the adbkeys file in the .android folder and still nothing.
When i try to boot in recovery manually, i just get the wipe data option and when i click yes to everything, it actually wipes my data. I'm unable to reflash TWRP because I can't access ADB or Fastboot due to the unauthorized error.
Someone, PLEASE HELP!!!!
Click to expand...
Click to collapse
different route but im in the same boat. any luck?
I fixed this shortly after. Wanted to avoid returning to stock as. The only option was you and I was on 10d. I had to go back to stock but luckily the recovery method still works.