Hello guys,
I have tried flashing an image in Odin, it connects but odin immediately crashes.
Using the androidSDK ADB, it connects, wipes a few things in a fraction of a second, then takes forever to try to push Boot.img which is only 5mb! this never completes.
I have tried wugfresh nexus root toolkit, and starts working perfectly, sends bootloader, boot, cache, recovery, but then at system it says FAILED (data transfer failure (unknown error)) rebooting into bootloader...
and it never reboots.
EDITED:
I tried wugfresh nexus toolkit for the 8th time, and SOMEHOW it got through the whole lot and I managed to boot.
For the record, (not that these things may have made a difference) had powered the tablet off before, on several occasions, and this time, I had also booted to bootloader from the tablet in a powered off state. I had read elsewhere that this had made a difference for someone.
No idea why it worked now... but relieved.
Related
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.
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
Nexus 7 2012 32GB wifi, Stock, Unlocked, Rooted, TWRP.
I am new to adb, but have used Wug's toolkit in the past. I attempted to sideload the Lollipop OTA zip through through Wug's toolkit. Everything was going well, but for some reason I got an error that stated that there was not enough room to install the update. I figured that was the end of that, but when I tried to reboot, it went straight to the stock recovery, and will not boot past that. Did some poking around in the toolkit, and found I didn't have fastboot anymore. (Also, I did not make a backup, stupid stupid, because I had recently wiped everything, and have the factory images downloaded). So, with the toolkit not getting me anywhere, I decided to try getting back to running through ADB. Read some tutorials, downloaded SDK, get that all set up so I can see where I am at. Command window, Type "adb devices", get "serial # sideload. Tried "adb reboot recovery", got no devices.
Probably should have just stopped but, since I knew I had USB debugging on, and all the newest drivers installed (just ran the toolkit) I figured why not try to sideload from here? Not enough Space again. Tried sideloading OTA 4.4.4(KTU84P) which is what I was running up to this point, and get unexpected contents error in "system/app/basicdreams.apk" "status 7".
Top of screen says:
Android system recovery (3e)
KTU84P
Long story short; Stuck in stock recovery, No Fastboot, Apply update from ADB works, but haven't anything to finish installing.
Thanks for any help, you guys are awesome, and give me way too much info for my own good, obviously.
Got back to working at this. WUG's toolkit fixed it. Just like every answer, in every thread with similar problems said it would. Using the flash stock +unroot and the soft brick/bootloop option. Since i was on Bootloader version 4.23, I flashed 5.0. Not sure what was different this time, as I tried the same process last night.
Anyway, anyone having the same troubles should give that a try.
Hopefully someone can help me here.
I have the N10 and it is rooted. I flashed the stock recovery and flashed the stock kernel.
So I should have been pretty much stock cause I had the 4.4.4 factory image on it except it was unlocked.
So then I let it do the OTA for lollipop.
When it rebooted into recovery it got about 1/3 and then hit an error (just said error).
Now I can only get it to the recovery screen and the reboot Mode Flag is 'Recovery'
The only thing I can do at that point is hit the power button and it reboots to recovery with a "No Command" error.
Help please!
EDIT: The thing finally booted up on it's own. Should I leave it alone or try to take the OTA update again?
sl2222 said:
Hopefully someone can help me here.
I have the N10 and it is rooted. I flashed the stock recovery and flashed the stock kernel.
So I should have been pretty much stock cause I had the 4.4.4 factory image on it except it was unlocked.
So then I let it do the OTA for lollipop.
When it rebooted into recovery it got about 1/3 and then hit an error (just said error).
Now I can only get it to the recovery screen and the reboot Mode Flag is 'Recovery'
The only thing I can do at that point is hit the power button and it reboots to recovery with a "No Command" error.
Help please!
EDIT: The thing finally booted up on it's own. Should I leave it alone or try to take the OTA update again?
Click to expand...
Click to collapse
Same for me. I'm trying to even manually flash the factory image, but it will not detect fastboot. I'm trying to research this now. The device just keeps restarting itself over and over into No Command.
IT Rider said:
Same for me. I'm trying to even manually flash the factory image, but it will not detect fastboot. I'm trying to research this now. The device just keeps restarting itself over and over into No Command.
Click to expand...
Click to collapse
Hi, I have exactly the same problem after installing Android 5.0 OTA. Please post a solution here if you find it. Thanks!
I didn't try the OTA again. I installed Lollipopalooza from this thread...
http://forum.xda-developers.com/showthread.php?t=1998585
No problem with it so far
sl2222 said:
I didn't try the OTA again. I installed Lollipopalooza from this thread...
http://forum.xda-developers.com/showthread.php?t=1998585
No problem with it so far
Click to expand...
Click to collapse
But I cannot flash any rom as none of ADB commands can be run (device is not connected, though I connected it with OEM cable). I tried factory reset but it didn't help.
Just wanted to share what worked for me after the OTA update failed and flashing stock images didn't work. Put the tablet in fastboot. Installed stock image, tablet wouldn't boot. Restarted went into recovery got the android on its back with the red x coming out of it (did not say bad command at thia point). I presses volume up and power at the same time on this screen. Cleared cache and rebooted then the tablet booted up.
I cannot believe companies still get away with this inadequate device "killing" type of software. Did no-one at the company do any testing before release?????
Rant over, onto solution - for me anyway.
The issue I had was that I could not get ADB to be of any use so switched to fastboot. Should have used fastboot from the getgo. Hohum.
So, into recovery with android on it's back with red triangle and reboot into fastboot.
Connect N10 to PC with USB cable.
Downloaded "Minimal ADB and Fastboot"(MAF)
Downloaded Lollipop for Nexus 10 - image-mantaray-lrx21p.zip and saved to c: drive (this saves loads of typing at command prompt)
File path for update is c:\image-mantaray-lrx21p.zip
Open MAF and ensure folder path points to your MAF install folder..
At command prompt type fastboot update c:\image-mantaray-lrx21p.zip
If you want to wipe device prior to update then type fastboot -w update c:\image-mantaray-lrx21p.zip
This may take a while so go make a drink - or something.
If all goes well, mine did, you should eventually be presented with the lollipop opening screen and a working device.
Just finally got it working!
ROM updates from ADB Sideload or Fastboot failed every time for different reasons.
What I had to do is to flash custom recovery (latest TWRP) with "fastboot flash recovery <recovery.img>" command.
From TWRP flashing the official ROMs also failed. But flashing Lollipopalooza as sl2222 suggested finally succeeded.
Thanks for all the help!
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...