My Nexus 10 was on Android 4.3 rooted and unlocked. Upgrade to 4.4 via OTA would not work.
I used WugFresh Nexus Rootkit 1.79, and was about to upgrade from Android 4.3 to 4.4, but first ran Flash Stock and unroot so I would be able to accept OTA updates. Unfortunately, the program halted when it completed the requested action, and I am left in fastboot. The tablet is stuck in fastboot mode, and no matter which option I try it always comes back to fastboot mode. Also I have tried to initiate custom recovery, via power and Volume up, but again to no avail.
USB debugging was active, and I had CWM recovery and root.
When I go to 'Restart Bootloader', (or 'Recovery Mode' or 'Start') the tablet immediately reboots back to 'Start'. Thankfully the 'Power Off' button does actually stop the tablet.
I have tried to see if I could get to Stock Recovery from fastboot, but that gives no response beyond going to the next tab.
Is anyone able to provide assistance in recovering from this dilemma?
First make sure bootloader is unlocked, if not
fastboot oem unlock
Then fastboot wipe
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
Now grab latest twrp or clockwork image
fastboot flash recovery nameofrecovery.img
Then boot to new recovery
For fun format all partitions available to in there
Now go to advanced, adb sideload
adb sideload romofchoice.zip
Then probably need gapps
adb sideload gapps.zip
Now reboot
This will get you up and running, if you absolutely want stock and non rooted let me know and I'll help you get there, but I will advise not to bother with toolkits as most every "help me fix xxxxxx" is from a toolkit user
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
First make sure bootloader is unlocked, if not
fastboot oem unlock
Then fastboot wipe
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
Now grab latest twrp or clockwork image
fastboot flash recovery nameofrecovery.img
Then boot to new recovery
For fun format all partitions available to in there
Now go to advanced, adb sideload
adb sideload romofchoice.zip
Then probably need gapps
adb sideload gapps.zip
Now reboot
This will get you up and running, if you absolutely want stock and non rooted let me know and I'll help you get there, but I will advise not to bother with toolkits as most every "help me fix xxxxxx" is from a toolkit user
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Many thanks for your response demkantor.
Although I tried to clearly describe the status of the tablet and the problem, I did not intend that I should come across as one who is familiar with the complexities of programming of either the tablet, or rooting around in the registry of a PC.
I can however follow clear instructions.
Your message appears to give a list of what to do, and presumably in the tablet from within fastboot. But I am lost after that.
By the way, the bootloader is unlocked.
Since the fastboot is currently inoperable, how do I initiate fastboot wipe, and then the following 3 commands 'erase system-w, boot & recovery'?
If you can spare the time and expand on your listing, I would certainly appreciate it.
http://forum.xda-developers.com/showthread.php?t=2277112
Sent from my Nexus 4 using XDA Premium 4 mobile app
Wow demkantor many thanks! The link you provided will take a bit of reading after I get back from the gym. A full afternoon ahead I suspect! I'll let you know how I go.
Just let me know if you get stuck
Sent from my Nexus 4 using XDA Premium 4 mobile app
Hi demkantor,
All done and dusted. Many thanks for your help, My tablet is now running on KitKat 4.4.2.
Your contributions to XDA University are very well arranged and written, and logically guide us through the maze. I for one did not know XDA University existed, and it is a shame that you as the person who pulled your contributions together have to also point us to it!
Many thanks for your efforts!
Edit - I read somewhere that the [Q] at the start of the thread should be changed to something else when the problem is resolved. It certainly is! Can the moderator correct this for me please?
Demkantor, I think I may have screwed up big time. I am unlocked and rooted, running stock 4.4. I woke up yesterday and had a notification that a system update had been downloaded. I did a temporary unroot and took the update. Which failed. I went into twrp and wiped everything. Still no go.Then, like a dummy I rebooted after it gave me a warning about not having an os installed. It wont do anything now except go into bootloader. I must have wiped twrp, because it wont boot into that or stock recovery. When I plug it up to my computer,I get this message( fastboot status-failInvalid command). I've just about every option in wugs toolkit. I keep getting adb and fastbooterrors. Have I completely hardbricked my nexus 10? I would appreciate it if you could point me in the right direction or let me know if I'm just wasting my time. I've been messing with this thing since around midnight and I'm about ready to start pullnig hair out of my head. Thanks in advance my friend.
@63t061
Thanks for the kind words, ive been busy lately (finals and all) so normally i would helped more personally but im glad you were able to get it all working on your own through research, which is the best way as im sure you have learned much and will be able to share with the next! Great job! As for editing the thread title, just edit it in your first post @moejoe88
Can you post all input output from cmd/terminal as its easier to see the issue. And try not use tool kits
Start with
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash recovery recovery.img
Sent from my SGH-T699 using XDA Premium 4 mobile app
Thanks for replying so quickly. I've had to walk away from it for a little while and get some sleep. I'll get some rest and make a fresh start of it. Again, thanks for the quick reply.
I've tried running terminal and the computer wont even recognize the tablet. I believe the battery is drained because I can get it to the bootloader, but it shuts back off after a few minutes. I'm trying to charge for a while and I'll give it another shot. Thanks again.
Related
Last night I was using my Nexus 4 and it wouldn't connect to any web pages so I thought I'd reboot to see if that fixed it. I powered off then back on and it won't get past the Nexus logo on the start up screen.
I'm unlocked and rooted but haven't installed any Roms ever. I used Wug's toolkit to root.
the only thing I can think of is that I was copying fonts from the system folder and maybe I moved a font instead of copying it, but I really don't think moved anything without replacing. Either way, i really don't think that moving a font would cause the phone to not boot up.
The phone booted up just fine an hour or so before this happened, so the font thing is the only thing I can come up with. I tried to use Wug's toolkit to push the font file to the N4 but the script gets stuck when trying to reboot.
Please help!! any suggestions?
------
addt'l info:
CWM not installed, phone does not bootloop, just gets stuck at X
nvillamob said:
Last night I was using my Nexus 4 and it wouldn't connect to any web pages so I thought I'd reboot to see if that fixed it. I powered off then back on and it won't get past the Nexus logo on the start up screen.
I'm unlocked and rooted but haven't installed any Roms ever. I used Wug's toolkit to root.
the only thing I can think of is that I was copying fonts from the system folder and maybe I moved a font instead of copying it, but I really don't think moved anything without replacing. Either way, i really don't think that moving a font would cause the phone to not boot up.
The phone booted up just fine an hour or so before this happened, so the font thing is the only thing I can come up with. I tried to use Wug's toolkit to push the font file to the N4 but the script gets stuck when trying to reboot.
Please help!! any suggestions?
------
addt'l info:
CWM not installed, phone does not bootloop, just gets stuck at X
Click to expand...
Click to collapse
do a factory reset via recovery
by copying system fonts which are not made for jb, your system could be damaged and thats the reason why you are in a bootloop..
What font did you push and how?
Sent from my HTC6435LVW using Tapatalk 2
pa.pn2 said:
do a factory reset via recovery
by copying system fonts which are not made for jb, your system could be damaged and thats the reason why you are in a bootloop..
Click to expand...
Click to collapse
I'd really like to avoid doing a factory reset if possible, but that may be inevitable.
What I did was copy (move?) fonts from the system folder to a folder on the sd card so the fonts would be accessible to something I was making in UCCW.
When I boot into recovery all I see is the Android laying on its back with a red triangle and beneath that it says "No command."
And this is why you don't use a toolkit. It gives you ability to do things when you didn't know how to get there.
You should just factory reset and get your phone booting. I don't think you're in a position to be trying to save your data because you did things without know what was going to happen. Don't ever touch things in system unless you truly know what you're doing. Especially not without a nandroid backup.
Sent from my Nexus 4 using xda premium
I'm in over my head now, but I knew what I was doing at the time. I *think* I moved a ttf file instead of copying it. A brain fart led to all this. Live and learn and hopefully the community can help me out.
I do have a nandroid from a couple weeks ago that I'd be happy to flash but I'm not familiar with adb but I'm willing to give it a shot if anyone could help. Google hasn't brought me much luck.
nvillamob said:
I'm in over my head now, but I knew what I was doing at the time. I *think* I moved a ttf file instead of copying it. A brain fart led to all this. Live and learn and hopefully the community can help me out.
I do have a nandroid from a couple weeks ago that I'd be happy to flash but I'm not familiar with adb but I'm willing to give it a shot if anyone could help. Google hasn't brought me much luck.
Click to expand...
Click to collapse
Best thing I can say is to fastboot flash back to stock. Google on how to do it, there's a guide on XDA on how to restore factory stock images.
Start all over as if you just got your phone and don't do the same mistakes again. Spend the 25-30 minutes and read how to use fastboot, and don't do things without asking or thinking beforehand. If you don't know what you're going to be modifying or whatever, don't do it.
You don't flash a nandroid. You restore it via recovery in recovery mode.
So I booted into recovery, chose wipe data/factory reset.
After that runs, I reboot the phone and I'm still stuck on the X.
I've got the factory image tgz file but I don't know how to flash it
nvillamob said:
So I booted into recovery, chose wipe data/factory reset.
After that runs, I reboot the phone and I'm still stuck on the X.
I've got the factory image tgz file but I don't know how to flash it
Click to expand...
Click to collapse
Use search + read stickies in the future.
Here is the thread you're looking for, http://forum.xda-developers.com/showthread.php?t=2010312
D. Type in the commands into the command prompt
1) Make sure your computer recognizes your device by typing: fastboot devices
2) Unlock your bootloader (if you have not already done so): fastboot oem unlock
3) You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept. Note: you use the volume keys to change the option and the power button to accept. You cannot use the touch screen.
4) Reboot by typing: fastboot reboot-bootloader
5) Flash the bootloader: fastboot flash bootloader bootloader-mako-makoz10l.img (or whatever the name of the bootloader image that you downloaded).
6) Reboot: fastboot reboot-bootloader
7) Flash the radio: fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.33.img (or whatever the name is of the radio image that you downloaded).
8) Reboot: fastboot reboot-bootloader
9) Flash the system partition: fastboot flash system system.img
10) Optional (NOT optional for n00bs) -- Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked. See note 2 below.
11) Flash the kernel/ramdisk: fastboot flash boot boot.img
12) Optional (NOT optional for n00bs) -- Flash the recovery partition: fastboot flash recovery recovery.img
13) Erase the cache partition: fastboot erase cache
14) Reboot: fastboot reboot
15) Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the Dalvik cache.
Click to expand...
Click to collapse
the files within the tgz will contain those imgs that you need. you may skip on fastboot flashing the radio, recovery, bootloader
do flash the system and boot flash for sure.
thanks again. I must be awful at searching because I can never find what I'm looking for.
In the mean time, I figured out how to use the toolkit to flash the stock image and I'm back in business. i sincerely appreciate the help.
nvillamob said:
thanks again. I must be awful at searching because I can never find what I'm looking for.
In the mean time, I figured out how to use the toolkit to flash the stock image and I'm back in business. i sincerely appreciate the help.
Click to expand...
Click to collapse
It's all good, I mainly use Google and type random tags on google like "how do i restore nexus 4 back to stock" or something between those lines and something would pop up. In general, Q&A there are stickied threads that has an index with a link to all the other pages that you're looking for.
It all comes with experience.
Errrrrrrr. Um.... you kinda killed me when you said toolkit. Don't use them it's what got you in this situation in the first place. Learn from your mistakes. The toolkit didn't necessarily bring you to this situation but you're not familiar with what the toolkit is actually doing and you're doing changes to the system because you aren't aware of what's going on in your surroundings.
http://forum.xda-developers.com/showthread.php?t=1469909 is a good thread on why you don't use toolkits. How do you think I know all this knowledge? Certainly not by using a toolkit. You have to know how to do these things, otherwise the next problem you'll have you'll ask questions some more. Please just take the time and read it and figure it out how to do it. It's not difficult by any means.
Good luck and glad I can help. I hope I could change your mind on the dangers of using toolkits and do it the traditional way with backgrounds of why you're doing this and that. If everyone used a toolkit then no one would be in Q&A forums could help others, like myself. If i used a toolkit, i wouldn't know how to fix your situation either. Thanks.
The title may sound strange but it's true.
I have this phone for just one week and haven't used it to call (reason: moving from T-Mobile to Tele2, this takes time. Date: 25e).
Rooting will allow me to do some stuff like a different boot animation which caught my attention. What I just don't want to happen is that I brick my phone to the point that it doesn't work anymore. Secondly I void my warranty which is something I don't feel so good about seeing I just got the phone.
I don't know this yet but if I root is. Can I back up everything from the phone? Contacts, Apps, settings etc etc? So when something goes wrong I can install a image of my back up?
Sadly I am pretty dark now. It's all new and while I would like to give it a shot, some things don't feel right for me just yet as stuff is unclear to me on how do it it.
Can XDA help me maybe? Also what are some really cool ROM's? I wanted to get Touchwiz but there is no (lol) and Cyanogenmod is like Stock Android so it seems ...pointless?
Best regards,
Robert Oortwijn
ZyreHD said:
The title may sound strange but it's true.
I have this phone for just one week and haven't used it to call (reason: moving from T-Mobile to Tele2, this takes time. Date: 25e).
Rooting will allow me to do some stuff like a different boot animation which caught my attention. What I just don't want to happen is that I brick my phone to the point that it doesn't work anymore. Secondly I void my warranty which is something I don't feel so good about seeing I just got the phone.
I don't know this yet but if I root is. Can I back up everything from the phone? Contacts, Apps, settings etc etc? So when something goes wrong I can install a image of my back up?
Sadly I am pretty dark now. It's all new and while I would like to give it a shot, some things don't feel right for me just yet as stuff is unclear to me on how do it it.
Can XDA help me maybe? Also what are some really cool ROM's? I wanted to get Touchwiz but there is no (lol) and Cyanogenmod is like Stock Android so it seems ...pointless?
Best regards,
Robert Oortwijn
Click to expand...
Click to collapse
setup adb and learn how to flash back to stock in fastboot. you will never brick your device beyond repair as long as you are capable of following directions for flashing and rooting and such
Here's the sticky from the other forum.
That is very useful and they talk in layman's terms. When I first got my N4, I followed this and got custom everything following the instruction posted there.
I'm no expert, but I rooted my N4 in the first week very easily, and as long as you follow all the instructions in the XDA thread then you won't go wrong. If you are really worried then you can use a toolkit as that will automate everything, but I'd never recommend that as you aren't really learning.
As for backing everything up, you can back up some things like your contacts, WiFi passwords and so on to your Google account. Apps is a lot harder if you want the data, but I believe an ABD backup will work - again, look at the appropriate thread (or use the toolkit for backing up).
And Roms, most of them have a stock feel with more features such as extra customization, but if you want a different look you can use themes - you can get touchwiz themes on the play store for ROMs like CM.
Sent from my Nexus 4 using xda premium
you dont need root to flash roms or kernels, you need a custom recovery(and an unlocked bootloader). you need root to run root apps and to mess around with the root file system.
I agree with tom about the toolkits. There is a large correlation between people who use toolkits and people who break their phone and have no idea what they are doing. Learning fastboot will save you from huge headaches and regret in the future.
username8611 said:
I agree with tom about the toolkits. There is a large correlation between people who use toolkits and people who break their phone and have no idea what they are doing. Learning fastboot will save you from huge headaches and regret in the future.
Click to expand...
Click to collapse
Finally got it rooted and installing CM10.1 went easy!
What I only want to know now is:
How do I relock the phone from rooted to unrooted again? Same for bootloader.
Removal of Clockwork.
And remove CM10.1 and get stock android back.
Thats all!
ZyreHD said:
Finally got it rooted and installing CM10.1 went easy!
What I only want to know now is:
How do I relock the phone from rooted to unrooted again? Same for bootloader.
Removal of Clockwork.
And remove CM10.1 and get stock android back.
Thats all!
Click to expand...
Click to collapse
Read this thread http://forum.xda-developers.com/showthread.php?t=2010312 well, it will show you exactly how to get back to stock if need be.
We were all scared and nervous too when we first rooted an android device. Lol. When you get it done you soon realize how easy it was. :thumbup:
Sent from my Nexus 4 using Tapatalk 2
Can someone help? So I have Cyanogenmod installed on the phone and got USB debug on. When i unplug and go into the bootloader and then plug the micro-usb in my PC doesn't detect the phone. I do have the drivers installed.
It did work, now it doesn't meaning I can't perform the stuff needed.
ps: If your wondering if I use the SDK to put everything to stock well sorry but I can't get the SDK to work. Java issues and errors. Pain in the ass so I stop with that.
In the bootloader and then recovery I get a Android logo with a red /!\ ?
Edit 1: I tried a reboot and now it doesn't hang. The X logo is moving but nothing yet.
Edit 2: 5min later and still at the X logo. It does move but nothing. Is my phone dead?
ZyreHD said:
In the bootloader and then recovery I get a Android logo with a red /!\ ?
Edit 1: I tried a reboot and now it doesn't hang. The X logo is moving but nothing yet.
Click to expand...
Click to collapse
if you are getting and android with a red "!", it sounds like you didnt flash a custom recovery. you need to be on either cwm, or twrp.
edit: it sounds like something got jacked and you need to start over again. it sounds like you are going back to stock, right?
start from the bootloader with fastboot. format/erase all the partitions and reflash everything and you should be golden
im not sure if i reading it right, but from what i can gather, you flashed cm10.1, then found out adb doesnt work right so you are ditching it and going back to stock? i wouldnt worry about it too much. as long as you can still use fastboot in the bootloader, thats all you need to do anything to save yourself from certain death. adb is more helpful for gathering up data if you cant lose it before flashing back to stock
username8611 said:
if you are getting and android with a red "!", it sounds like you didnt flash a custom recovery. you need to be on either cwm, or twrp.
edit: it sounds like something got jacked and you need to start over again. it sounds like you are going back to stock, right?
start from the bootloader with fastboot. format/erase all the partitions and reflash everything and you should be golden
Click to expand...
Click to collapse
For some reason. I pressed the buttons to get into the bootloader I get this:
Download Mode. Do not unplug?
Edit: I'm back in the bootloader. I didn't press the combination right sending me into Download Mode.
Edit 2:
So what I did was this. I followed these instruction on how to install custom ROMS: http://www.androidrootz.com/2013/02/how-to-install-custom-roms-on-nexus-4.html I also followed them in the procedure of rooting your phone.
I tried it out and now wanted to go back to stock. So I found a article also by them and did that: http://www.androidrootz.com/2012/12/how-to-unroot-nexus-4-to-stock-42-jelly.html
When I was at the point where the cmd said: erasing use rdata the article said: 5min, but it took longer so I unplugged the USB.
Now I'm here where I can't boot the OS anymore. Bootloader does work but recovery doesn't as I get the /!\
Edit 3:
Retrying in the meantime. Now at writing system (done)
Edit 4:
Now I'm at the point where it's erasing userdata....
Edit 5: couple of minutes later and still going.
ZyreHD said:
For some reason. I pressed the buttons to get into the bootloader I get this:
Download Mode. Do not unplug?
Click to expand...
Click to collapse
unplug anything that is plugged into your phone. make sure it is completely turned off. hold volume down and power until it vibrates. it should take you straight to the bootloader
---------- Post added at 02:21 PM ---------- Previous post was at 02:16 PM ----------
yeah something is amiss, hold on let me type this up real quick
go here and download OCCAM factory image. open up the file you downloaded and you should see userdata.img, system.img, etc.... take all the files that end in img and move them to your directory for fastboot aka: /platform-tools, or whatever you use for fastboot.
boot your phone to the bootloader. type this in fastboot, pressing enter after each line:
fastboot format userdata
fastboot format system
fastboot format cache
fastboot erase boot
fastboot erase recovery
fastboot reboot-bootloader
now for the flashing,
fastboot flash recovery recovery.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
fastboot flash userdata userdata.img
OPTIONAL... if you think your radio is messed up -----> fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.48.img
fastboot reboot
voila
username8611 said:
unplug anything that is plugged into your phone. make sure it is completely turned off. hold volume down and power until it vibrates. it should take you straight to the bootloader
---------- Post added at 02:21 PM ---------- Previous post was at 02:16 PM ----------
yeah something is amiss, hold on let me type this up real quick
go here and download OCCAM factory image. open up the file you downloaded and you should see userdata.img, system.img, etc.... take all the files that end in img and move them to your directory for fastboot aka: /platform-tools, or whatever you use for fastboot.
boot your phone to fastboot. type this, pressing enter after each line:
fastboot format userdata
fastboot format system
fastboot format cache
fastboot erase boot
fastboot erase recovery
fastboot reboot-bootloader
now for the flashing,
fastboot flash recovery recovery.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
fastboot flash userdata userdata.img
OPTIONAL... if you think your radio is messed up -----> fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.48.img
fastboot reboot
voila
Click to expand...
Click to collapse
I got a different option now. format userdata and I get options. Flash all, erase, update filename etc.
ZyreHD said:
For some reason. I pressed the buttons to get into the bootloader I get this:
Download Mode. Do not unplug?
Edit: I'm back in the bootloader. I didn't press the combination right sending me into Download Mode.
Edit 2:
So what I did was this. I followed these instruction on how to install custom ROMS: http://www.androidrootz.com/2013/02/how-to-install-custom-roms-on-nexus-4.html I also followed them in the procedure of rooting your phone.
I tried it out and now wanted to go back to stock. So I found a article also by them and did that: http://www.androidrootz.com/2012/12/how-to-unroot-nexus-4-to-stock-42-jelly.html
When I was at the point where the cmd said: erasing use rdata the article said: 5min, but it took longer so I unplugged the USB.
Now I'm here where I can't boot the OS anymore. Bootloader does work but recovery doesn't as I get the /!\
Click to expand...
Click to collapse
When you see the android laying down that is stock recovery. Press volume up and power to open the menu. Then you can factory reset.
Sent from my Nexus 7 using xda premium
El Daddy said:
When you see the android laying down that is stock recovery. Press volume up and power to open the menu. Then you can factory reset.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I only have 4 options there.
Reboot system now
apply update from ADB
wipe data/factory reset....
Oh I got it. It formatted and I rebooted. For now it only shows the X logo. Will go downstairs in the meantime to get something to drink. It might take some time maybe?
THANKS YOU SO MUCH!!!
Just as I wanted to go it booted!!!!!!!!!!!!!!!!! 2 hours of hard search and it was this small thing to do? I was really afraid that I had wiped the factory reset of the phone!!!!
Thank you again, all of those who helped!!!!:laugh::laugh::good::highfive:
nevermind, you were talking about the options in recovery
ZyreHD said:
THANKS YOU SO MUCH!!!
Just as I wanted to go it booted!!!!!!!!!!!!!!!!! 2 hours of hard search and it was this small thing to do? I was really afraid that I had wiped the factory reset of the phone!!!!
Thank you again, all of those who helped!!!!:laugh::laugh::good::highfive:
Click to expand...
Click to collapse
Congrats. That's why I wrote what I did in your other thread. Read, read, read. Its better to know how to fix things before they happen then frantically trying to find out how fix them while they happen.
Sent from my Nexus 7 using xda premium
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
Well, i tried to install stock Bootloader, stock recovery and stockrom with wugfresh tool under "Back to Stock", and so thats the problem:
When i try to send the bootloader, it stucks and the tablet posts under the infos on the bootloader screen: FASTBOOT STATUS - DATA00140000.
And thats it. I waited 2 hour, it still stucks on sending bootloader. So i downloaded the Unified Android Toolkit, install the fastboot driver and tick the option to install a new recovery... It still stucks on sending bootloader. In Youtube Videos, i saw, that the sending finished about 0,2 s. Thats 1280kb! Why doesnt work it on my tablet. I had root, but i didnt tick the usb debugging. So when i switch on my tablet, it comes to the bootloader, and its the activated bootloader( i can switch to recovery, reboot bootloader, power off, reboot system,..) and its unlocked. If i reboot into the recovery, it also comes to the activated bootloader. Its also when i tick the reboot system. So what can i do? Is it hardware bricked? Or whats the problem? I have the bootloader version MANTAMF01 and the H/W Version 8. Can anyone helps me?
And yes, i am the Admin on my PC
The problem is the toolkit, just use fastboot
fastboot flash bootloader nameofbootloader.img
And your done
But after doing so you effectively wipe a few of your partitions so then flash recovery and ROM as well, the method on doing so slightly varies depending if your going back to stock or what something custom
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
The problem is the toolkit, just use fastboot
fastboot flash bootloader nameofbootloader.img
And your done
But after doing so you effectively wipe a few of your partitions so then flash recovery and ROM as well, the method on doing so slightly varies depending if your going back to stock or what something custom
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I am having the same exact problem, and I tried doing as you said with fastboot, but I still can't receive any files. Any other suggestions? Any help would be greatly appreciated.
funkym0nkee said:
I am having the same exact problem, and I tried doing as you said with fastboot, but I still can't receive any files. Any other suggestions? Any help would be greatly appreciated.
Click to expand...
Click to collapse
Are you trying to return to stock? Download the appropriate factory image (just Google android factory image) extract all and flash with fastboot.
If you want more detailed explanation boot to bootloader and write down all info on that screen, pet me know the os of your PC, and the explain a little more what's wrong, I'm not sure what can't receive any files means. It is often helpful to copy and paste all input/output from cmd/terminal
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Are you trying to return to stock? Download the appropriate factory image (just Google android factory image) extract all and flash with fastboot.
If you want more detailed explanation boot to bootloader and write down all info on that screen, pet me know the os of your PC, and the explain a little more what's wrong, I'm not sure what can't receive any files means. It is often helpful to copy and paste all input/output from cmd/terminal
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I just resolved this issue on my own about a minute before your response lol. The problem was that I wasn't using the stock USB cord. Holy cheese and rice, I've been sitting here for the past 5 hours at wits end trying to figure out the problem. My problem was exactly like MrCreeper's, it was just stuck on "sending 'bootloader'" with no progress whatsoever on either PC or tablet. Who woulda thunk the problem was simply that I was using the incorrect USB cord -_- *sigh*
Anyway, thank you for your prompt reply. I did use a few of your tips from your other posts when I ran into other problems trying to flash stock image, so cheers for that!
First of all, I know that there are many people asking same thing. I have checked those threads and I guess I am just a little bit more clueless. Last time I was able to use my Nexus 10 was 3 months ago. Since then I tried to solve it many times, but no luck so far. I will try to explain some of the issues I'm experiencing, but I'm afraid I'm not too good with all the expressions people are using on this forum.
1. ADB vs Fastboot
I see this mentioned often and I don't know what exactly it means. It's amazing to me that I can't google it, I'm usually good with googling. I can see that my N10 is sometimes listed under ADB and sometimes under Fastboot devices but I have no idea what I did to change that. I do know that whatever I try to do at certain point, it's always in "wrong" mode, waiting for adb etc. So if someone can point me to a thorough explanation, a wiki or something, that would be very nice.
2. The Loop
I managed to get ClockworkMod v6.0.4.3 installed and it's this loop that device is now inside. I've tried pretty much all possible combinations, wiped both caches, did factory reset, rebooted to system/bootloader/recovery... nothing. Always ends up on same CM menu.
3. Android Toolkit
I have installed this on my computer and tried so many things that I forgot about all details. I tried flashing the big 400 MB stock image to the device, but haven't been successful (says waiting for ADB, even if the device WAS listed as ADB device before I started the procedure). I am also expecting to see the N10 as another "drive" from my desktop, if you know what I mean, so that I could copy files to it. However I don't see it that way, I only see it registered as a Nexus 10 device, like a mouse or any other non-drive device. Is this normal?
So what to do? Can anyone tell me in a simple way, because I am obviously stupid enough to find threads I've seen so far not clear enough. And I would actually think that my computer literacy level is rather high, I think that this Nexus 10 is the only thing that brought me to my knees in last 20 years of working with computers.
And when I say "simple wiki style" I'm thinking of something like this:
Ok. no links allowed, great. It's a redmondpie article named
/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
This is easy enough for me... but do I assume correctly that all this has already been done with me installing Android Toolkit? If so, it uses a different path structure and I don't see all those folders...
So u do have cmw installed, when u try to flash a ROM it just boots to recovery?
Sent from my Nexus 10 using Tapatalk
newellj79 said:
So u do have cmw installed, when u try to flash a ROM it just boots to recovery?
Click to expand...
Click to collapse
You mean flashing ROM only with CWM, not through android toolkit? Through CWM menu I have tried (many times):
- wipe data / factory reset
- wipe cache partition
- wipe dalwik cache
I don't see way to do anything with:
- install zip
- backup and restore
- mounts and storage
Rebooting menu items do following:
- Reboot system --> reboots to same CWM recovery menu
- Reboot to bootloader --> reboots to the stock bootloader "menu" where I can choose between Start, Power Off, Recovery mode (picking this will reboot to CWM recovery menu) and Restart bootloader (picking this will reboot to this same menu)
- Reboot recovery --> reboots to same CWM recovery menu
1 adb works only in os and recovery, fastboot works only in bootloader
2 it looks like your recovery is screwed up, flash this with fastboot
http://techerrata.com/file/twrp2/manta/openrecovery-twrp-2.6.3.1-manta.img
fastboot erase recovery
fastboot flash recovery nameofrecovery.img
3try not to use toolkits, you have a nexus, toolkits are more complicated than manual methods and you won't learn anything from it
Once you have recovery
Wipe all, then you will will need to use adb sideload to flash ROM as you have no ROM on emulated sdcard
Go to advanced menu
adb sideload
adb sideload nameofROM.zip
adb sideload gapps.zip
For more info on fastboot
http://forum.xda-developers.com/showthread.php?t=2277112
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
1 adb works only in os and recovery, fastboot works only in bootloader
2 it looks like your recovery is screwed up, flash this with fastboot
http://techerrata.com/file/twrp2/manta/openrecovery-twrp-2.6.3.1-manta.img
fastboot erase recovery
fastboot flash recovery nameofrecovery.img
3try not to use toolkits, you have a nexus, toolkits are more complicated than manual methods and you won't learn anything from it
Once you have recovery
Wipe all, then you will will need to use adb sideload to flash ROM as you have no ROM on emulated sdcard
Go to advanced menu
adb sideload
adb sideload nameofROM.zip
adb sideload gapps.zip
For more info on fastboot
http://forum.xda-developers.com/showthread.php?t=2277112
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The first part worked ok. The second part doesn't.
ADB sideload - I went there in the Nexus menu
adb sideload kitkat2501.zip
returns this:
* failed to write data 'protocol fault (no status)' *
If I do it without starting adb sideload on nexus, then it just says "error: closed", so it does recognize the change.
I downloaded the latest sdk tool, 64-bit, and the stock nexus 10 rom from 25th Janaury.
Let's do this, grab the latest stock for manta from here
https://developers.google.com/android/nexus/images
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
And extract and run the flashall.bat
This should bring you to the latest official software/firmware. Then with you up and running we can root and give you custom recovery,ROM,whatever
If you have an issues at all please copy and paste all input/output from cmd/terminal here
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
Let's do this, grab the latest stock for manta from here
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
And extract and run the flashall.bat
This should bring you to the latest official software/firmware. Then with you up and running we can root and give you custom recovery,ROM,whatever
If you have an issues at all please copy and paste all input/output from cmd/terminal here
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You are a wizard. I got it all ok now and I added CWM to it, it was easy to root it from there.