So Sorry to post this if it's already been answered, but to be honest, I am completely lost.
I had the G1 phone for awhile and loved it. I was very familiar with rooting, flashing, etc. For some reason, I cannot get my MyTouch 3G to work.
I got the Google ION which was given out at the Google Conference in SF. My question is, how do I flash the recovery image and get the Hero Rom? From the other post, I heard that you need to flash the recovery image first and then apply the Hero Rom without rooting. How do I do this? Any step by step tutorial? Don't I need to root my phone?
Please help, thank you in advance. Any help will be greatly appreciated.
you get fastboot from htc.com and the recovery image from Smartphone France.
then, you ought to be able to do this with your phone plugged in:
Code:
fastboot flash recovery recovery.img
put the ROM you want on the sdcard as update.zip (use adb push or just drag-n-drop in Finder/Explorer). restart the phone while holding the home key, and use the trackball to navigate the recovery menu.
Thanks for your help...just a quick question, how would I enter this code "fastboot flash recovery recovery.img"? Would I have to use adb from my computer?
I rather use Amon_RA's recovery image. So I need to type "$fastboot boot recovery-RAv1.1.1G.img" instead. Would I have to use adb?
That command is correct, except you don't use ADB. ADB is the Android Debug Bridge, it only works when the phone is booted, it is used to give commands and access the Android filesystem on your desktop/laptop. Fastboot is when you enter fastboot mode so you can flash .img files from your PC or .nbh files from your SD.
So you wouldn't type ADB in the command prompt but you would type Fastboot?
My wife got an ION.
What I did was follow the "root my htc magic" wiki from android-dls.com
http://android-dls.com/wiki/index.php?title=Magic_Rooting
This allowed me to install a new recovery image.
I then installed the ion rv2 rom from haykuro, but the wifi wouldn't work for me. eventually, i installed the ion-r2-sapphire rom (look in xda, or PM me). Or haykuro's google code page.
If you have the developer edition you dont have to do anything, just put the rom as update.zip into your memory stick, go into recovery i think it was home plus power and update it thats it.
Related
Guys i rooted the build GRH78C so i know how to root
i put the new build GRI40 that removes the root access by restoring it from rom manager.
but i was so stupid thinking that superboot for the build GRH78C can also root the new build GRI40. I did then it rebooted but stuck on google logo.
is there any solution?
if i tried the superboot for the new build when it comes out will it work?
does that mean my nexus s will not work forever?
please help
boot into recovery mode
then load another ROM
as a last resort you can use the Odin method, if you are unable to use fastboot methods
after flashing GRI40 by restoring from rom manager i got stuck 2.3.3 unrooted!
if i boot into recovery mode it only recognizes update.zip and passing.zip
i thought of moving update.zip into the internal memory so recovery can recognize it but i cant the phone doesn't have a sd card.
please help
I manage to try this and have the same fate.
To fixit ,is easy. Follow the following.
Fastboot write the original boot.img from GRH78C to the phone,
Boot into recovery, re-apply update.zip
Once done, you are back in business.
SWEETTOOTH said:
after flashing GRI40 by restoring from rom manager i got stuck 2.3.3 unrooted!
if i boot into recovery mode it only recognizes update.zip and passing.zip
i thought of moving update.zip into the internal memory so recovery can recognize it but i cant the phone doesn't have a sd card.
please help
Click to expand...
Click to collapse
qwerp_ said:
I manage to try this and have the same fate.
To fixit ,is easy. Follow the following.
Fastboot write the original boot.img from GRH78C to the phone,
Boot into recovery, re-apply update.zip
Once done, you are back in business.
Click to expand...
Click to collapse
Alternatively you can do the following:
1) Download the newest version of CWM from here (Google Nexus S, near the bottom of the list)
2) Boot your phone to the bootloader
3) Type
Code:
fastboot boot recovery-clockwork-3.0.0.5-crespo.img
4) Go to mounts and storage and mount USB storage
5) Download a different ROM like CM and place it on the root of your SDcard
6) Flash it
7) Golden!
kenvan19 said:
Alternatively you can do the following:
1) Download the newest version of CWM from here (Google Nexus S, near the bottom of the list)
2) Boot your phone to the bootloader
3) Type
Code:
fastboot boot recovery-clockwork-3.0.0.5-crespo.img
4) Go to mounts and storage and mount USB storage
5) Download a different ROM like CM and place it on the root of your SDcard
6) Flash it
7) Golden!
Click to expand...
Click to collapse
thanks i tried it but it says Permission denied
what i do
first i write cd the drag the tool floder to the terminal
hit enter
drag the recovery image into terminal (space) then paste fastboot boot recovery-clockwork-3.0.0.5-crespo.img
hit enter
it says
Permission denied
by the way
i have above only fastboot mode . there is no fastboot mode usb
in the bottom standard_set_configuration
does the fastboot sees my device?
is that right?
qwerp_ said:
I manage to try this and have the same fate.
To fixit ,is easy. Follow the following.
Fastboot write the original boot.img from GRH78C to the phone,
Boot into recovery, re-apply update.zip
Once done, you are back in business.
Click to expand...
Click to collapse
please do you have the file of the original boot.img?
then how to push update.zip with terminal?
Odin is GOD..
SWEETTOOTH said:
Guys i rooted the build GRH78C so i know how to root
i put the new build GRI40 that removes the root access by restoring it from rom manager.
but i was so stupid thinking that superboot for the build GRH78C can also root the new build GRI40. I did then it rebooted but stuck on google logo.
is there any solution?
if i tried the superboot for the new build when it comes out will it work?
does that mean my nexus s will not work forever?
please help
Click to expand...
Click to collapse
Hi SWEETTOOTH, if your still stuck on the Google screen can I suggest Odin as a way forward (http://forum.xda-developers.com/showthread.php?t=947950) , it wll flash you back to stock 2.3.1, but it will you keep the latest baseband that ships with 2.3.3 (I9020XXKB1). I have used it twice with no problems.
You can then re root and proceed down another path?
guys please help i bought it last week now it doesnt work at all.
how to push update.zip with adb?
how to solve Permission denied problem?
help
SWEETTOOTH said:
thanks i tried it but it says Permission denied
what i do
first i write cd the drag the tool floder to the terminal
hit enter
drag the recovery image into terminal (space) then paste fastboot boot recovery-clockwork-3.0.0.5-crespo.img
hit enter
it says
Permission denied
by the way
i have above only fastboot mode . there is no fastboot mode usb
in the bottom standard_set_configuration
does the fastboot sees my device?
is that right?
Click to expand...
Click to collapse
Okay, if you want to test to see if fastboot sees your device do this:
Code:
fastboot devices
If you get an output on that, it sees your phone. Now assuming that works and assuming I understand what is happening to you correctly do exactly as I say:
1) Download and unzip this file and place on your desktop and place the recovery image into that folder.
2) Boot your phone into the bootloader
3) Type or copy the following into your terminal exactly
Code:
~/Desktop/adb-fastboot/fastboot boot recovery-clockwork-3.0.0.5-crespo.img
that *should* work to get you into the custom recovery. From there do this:
1) Go to mounts and storage and chose mount USB storage.
2) Go to this thread and download either of them (one of them is rooted one of them is not. If you want to be rooted, download the rooted one if not download the unrooted).
3) Unzip the file to the root of your SDcard (it should be a folder called clockworkmod).
4) Eject the drive from your computer and select unmount on your phone.
5) Go to backup and restore and select restore and select the one named GRI40-2.3.3 or something like that (can't remember exactly what its named).
6) Reboot your phone. Follow the other instructions about how to prevent the stock recovery from overwriting CWM and how to flash CWM etc.
Did it work?
it says
/Desktop/adb-fastboot/fastboot boot recovery-clockwork-3.0.0.5-crespo.img
cannot load 'recovery-clockwork-3.0.0.5-crespo.img'
i feel like giving up all i need is to install the recovery but there's something wrong
fastboot cant see my device
Did you install the Android ask and the Nexis s drivers?
Sent from my MattedBlues CM7 Google Nexus S!
yes i have the sdk , and i have mac do i need drivers to install?
SWEETTOOTH said:
yes i have the sdk , and i have mac do i need drivers to install?
Click to expand...
Click to collapse
No, no need to install drivers on a mac...Man I'm baffled...I'll send distortedloop a PM and ask him to check this out because I'm out of ideas...sorry man!
Thanks man for all the initiatives
SWEETTOOTH said:
Thanks man for all the initiatives
Click to expand...
Click to collapse
Its no problem man, everyone should be able to use their phones however they like and rooting isn't easy. Sometimes people need a little help I know I did at first! hehe
Sweet, I have one last idea actually... try this:
Download this SDK http://www.box.net/shared/ljhg8t5sjh it should have everything including an older version of CWM which should still work (again unzip it to your desktop) and try using this command:
Code:
~/Desktop/androidsdk/tools/fastboot flash recovery ~/Desktop/androidsdk/tools/recovery-clockwork-3.0.0.0-crespo.img
If it works you can flash the newest version of CWM through rom manager later.
Sweettooth, is your bootloader unlocked? Do you gave the unlocked padlock icon on the bottom of the screen when you first turn on phone and have Google logo?
If your bootloader got updated to gri40 you can't fastboot boot or fastboot flash if youre locked.
Try the fastboot oem unlock command from Mac Terminal, you can always say no to the warning that pops up if you dont want to go further. Be aware that oem unlock will wipe all data off the phone including sdcard photos and stuff.
SWEETTOOTH said:
fastboot cant see my device
Click to expand...
Click to collapse
Sorry if you answered this already, but when you type in fastboot devices on the Mac Terminal what is the response you get?
I recently rooted my phone (T-Mobile US Nexus S) and installed the 4.0.3 OTA update from this thread, but now I cannot access any Google apps or get root access on any of the apps that require it.
SounderBruce said:
I recently rooted my phone (T-Mobile US Nexus S) and installed the 4.0.3 OTA update from this thread, but now I cannot access any Google apps or get root access on any of the apps that require it.
Click to expand...
Click to collapse
Ok! first download : http://www.4shared.com/zip/XG506hyV/icsroot-fastboot-recovey.html
just unpack, connect your device and click run.bat.....Good luck!
I ran the .bat, but I get an error saying "Device already rooted", but it is still not recognized as rooted by SuperUser.
Alternatively, is it possible to completely wipe the phone of everything (including root) so I can start over with a fresh phone?
Of course you can, and might be the best idea if you don't mind doing it.
Make sure you have the latest CWM recovery on your phone, download the FULL ROM from this thread (i'm not american so i don't know exactly, but from what i know yours is the I9020T, so get that ROM) and copy it to the SDCard. Now go into recovery, wipe system/data and dalvik cache, then flash the ROM.
Do make sure you have the right ROM though. This will get you 100% fresh and untouched 4.0.3. You can probably clear out any non-personal folders on the sdcard too, but that shouldn't do any harm anyway.
After this, use the attached file from this thread to root, and feel free to update root/superuser.
Actually, that's what I did...I can't use CWM recovery because its displaying an error of no root. So how do I wipe this or fix CWM?
Is your boot loader unlocked? And are you trying to flash cwm through fastboot?
Note to backup your sdcard if unlocking the bootloader.
Harbb said:
Is your boot loader unlocked? And are you trying to flash cwm through fastboot?
Note to backup your sdcard if unlocking the bootloader.
Click to expand...
Click to collapse
My bootloader is apparently unlocked and I'm trying to flash through fastboot.
Are you sure the following is satisfied:
-open padlock and google logo on boot
-fastboot (on phone) says "bootloader status: unlocked" or something of the like
-you are using: "fastboot flash recovery "C:\path\to\recovery.img""
-you are using the above command while connected to the PC via USB (with working drivers) and that you are in fastboot mode on the phone (turn off phone --> hold Vol. Up then hold Power TOGETHER for about 2 seconds, should give you reboot and recovery options)
It is necessary to be in the bootloader/fastboot interface on the phone when you run the command. Hopefully it was something simple that i said above, otherwise i'm completely lost.
1. Yes
2. Yes
3. I didn't use that method to root...
4. I'll try that.
3 is just flashing recovery, that is the code u type into cmd/terminal to reflash the recovery img. It isn't rooting the phone. 4 is how to get into the mode on the phone to use the command.
Its a bit confusing at first but makes much more sense once you do it one or two times.
Where do I go to get the recovery image?
The latest ClockWorkMod Recovery can be found on this page. Just scroll down to Nexus S and download 5.0.2.0 crespo .img. Then just direct fastboot to the folder you have it saved in while using the "fastboot flash recovery C:\path\to\recovery.img" command.
Ok. I've tried this, but in command prompt, I get the following error:
C:\Users\Bruce>fastboot flash recovery C:\Users\Bruce\Downloads\recovery.img
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
Check out this rooting guide, however only go up to step 5 (and do NOT type "fastboot oem unlock", do everything up until that point). This will setup fastboot for you, and setup drivers for your computer. Once this is done, do what you did above and it should work successfully.
Remember to cd (change directory) in cmd to where you unzipped that folder.
There isn't a link...
Sorry, stuffed that up. I fixed the link in my previous post pointing to NexusSHacks - How to Root Nexus S.
It's worked, but when I try to go to the recovery menu, the Google/unlocked padlock screen freezes or it displays an Android with its chest compartment open and a red triangular ! symbol.
I just had a really long reply and managed to lose it by closing the page..
That's the stock bootloader you see there, it probably didnt flash or you rebooted your phone. And make sure that you are flashing the latest CWM you downloaded before.
I flashed the latest CWM, but when I try to go to recovery, my phone freezes at the Google logo with the unlocked padlock.
Have you tried flashing it again, or maybe redownloading the file? And of course making sure it is the NEXUS S version which you are downloading.
Alternatively, try just "fastboot boot recovery.img", replacing recovery.img with the full name and path of cwm.
edit: btw, i'll be gone for an hour or two Bruce so i can answer any more questions/issues when i get back
Hello everyone!
I've used ROM manager to flash clockwork mod recovery and it worked great until I realised that this clockwork doesn't see my SD card! I just wanted to know is there a solution to this without going back to stock etc?
Sent from my Xoom using XDA Premium HD app
Never fear! Fastboot is here!
Fastboot flash recovery recovery.img from the command line of your computer (you must have motorola drivers installed plus adb/fastboot tools)
I recommend Rogue Recovery, it's over in the android development section. Others prefer TWRP and EOS recovery. Take your pick. All support the internal SD card.
Thanks for your reply!
I thought about it initially, wanted to repeat steps used to flash it when original recovery was on. But first command re-booted xoom and took me to clockwork (no s..t, Sherlock? ) and then I thought I better stop before I end up with a brick.
So just to be clear, connect my xoom, go to the right folder on my pc and type:
fastboot flash recovery file-name.img
is that correct? do I need to be in recovery?
xywojtek said:
Thanks for your reply!
I thought about it initially, wanted to repeat steps used to flash it when original recovery was on. But first command re-booted xoom and took me to clockwork (no s..t, Sherlock? ) and then I thought I better stop before I end up with a brick.
So just to be clear, connect my xoom, go to the right folder on my pc and type:
fastboot flash recovery file-name.img
is that correct? do I need to be in recovery?
Click to expand...
Click to collapse
So you need to be in bootloader mode, not recovery. You can either turn the xoom on then press the down button about 2 seconds after you see the splash screen or use 'adb reboot bootloader'. I think it says 'starting fastboot protocol', can't quite remember from memory. then as you said, go to the right folder type fastboot flash recovery file-name.img
then fastboot reboot
then you'll be able to get into your custom recovery
love you man!
Hello,
again i need help I have unlocked the bootloader on my Xoom, the i have flashed TWRP and downloaded a Rom and the Gapps. I copied the gapps onto the device and followed instructions which came with the rom. I was instructed to wipe "system" too which i did.
Of course that deleted the downloaded rom and gapps too. Now i have TWRP and was excited to mount USB storage and just copy over again the rom and gapps but unfortunately there is no mount as USB option.
What and how is the smartest way to go about it? I wanted to sideload over ADB but the device is not found. I have really tried everythin in my knowledge, hope someone can help
cheers
Come on guys, really need help here. My kids are killing me for the damn thing
I have same problem.......it's an issue of twrp !
Have you tried a micro sd card? (copy the rom and gapps there from a pc then put it in the Xoom, etc...)
Worst case, you should be able to grab the stock images http://forum.xda-developers.com/wiki/Motorola_Xoom and fastboot flash the device back to stock.
Have the same problem
dosada, could you solve the problem?
airesch, I tried to mount sd card but it is impossible. How can I return to stock without ADB because computer is not recognized?
hbtwender said:
dosada, could you solve the problem?
airesch, I tried to mount sd card but it is impossible. How can I return to stock without ADB because computer is not recognized?
Click to expand...
Click to collapse
Stock flash doesnt require adb, just fastboot mode. You may need to still install a driver, but if you can boot into recovery then the xoom should also be able to boot into fastboot mode and be recognized by a pc. If the instructions on the link I gave arent enough, I will see if I cant find something tomorrow when I am on a pc.
Sent from my GT-N8013 using XDA Premium 4 mobile app
hbtwender said:
dosada, could you solve the problem?
airesch, I tried to mount sd card but it is impossible. How can I return to stock without ADB because computer is not recognized?
Click to expand...
Click to collapse
NOTE: This WILL erase everything remaining on the device. In the case of the above, I don't know that you have much choice, just be forewarned.
Lord AIO toolkit has all the tools you need (look at the second post if you need the Windows driver.) Extract both the stock image zip and the toolkit (unless you have the sdk, in which case as long as you can find fastboot.exe you should be fine,) to somewhere convenient. Install the windows driver if you never have before and reboot your pc.
1. Boot your Xoom in fastboot mode: Power+Vol+ until it says: Starting Fastboot protocol support (you may need to tap the Vol+ instead of holding it the whole time, my Xoom has always been a bit picky about the buttons.)
2. Connect the usb to the pc
3. In a Command prompt window, go into the extracted version of the toolkit above (or if you have the sdk, just go to where you have fastboot.exe from it)
4. Run the following commands (replacing the files at the end with the full extract path from your stock image zip extract)
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
"fastboot reboot" if you want to stay unlocked or "fastboot oem lock" if you want to re-lock and follow the prompts. The Xoom will get OTA updates even if it's unlocked, so there should be no reason to re-lock unless you need to send it in for service.
The driver isn't what I used to use, but it *should* work, and the instructions should be correct as far as I can remember. As long as you don't flash the wrong image to the wrong place/run out of power during flashing/disconnect during a flash then none of this should permanently damage the hardware and should get you a working device again. It's just that it's been so long since I have personally done any of this that I have forgotten more than I ever knew .
Solved
airesch said:
NOTE: This WILL erase everything remaining on the device. In the case of the above, I don't know that you have much choice, just be forewarned.
Lord AIO toolkit has all the tools you need (look at the second post if you need the Windows driver.) Extract both the stock image zip and the toolkit (unless you have the sdk, in which case as long as you can find fastboot.exe you should be fine,) to somewhere convenient. Install the windows driver if you never have before and reboot your pc.
1. Boot your Xoom in fastboot mode: Power+Vol+ until it says: Starting Fastboot protocol support (you may need to tap the Vol+ instead of holding it the whole time, my Xoom has always been a bit picky about the buttons.)
2. Connect the usb to the pc
3. In a Command prompt window, go into the extracted version of the toolkit above (or if you have the sdk, just go to where you have fastboot.exe from it)
4. Run the following commands (replacing the files at the end with the full extract path from your stock image zip extract)
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
"fastboot reboot" if you want to stay unlocked or "fastboot oem lock" if you want to re-lock and follow the prompts. The Xoom will get OTA updates even if it's unlocked, so there should be no reason to re-lock unless you need to send it in for service.
The driver isn't what I used to use, but it *should* work, and the instructions should be correct as far as I can remember. As long as you don't flash the wrong image to the wrong place/run out of power during flashing/disconnect during a flash then none of this should permanently damage the hardware and should get you a working device again. It's just that it's been so long since I have personally done any of this that I have forgotten more than I ever knew .
Click to expand...
Click to collapse
Hey airesch, thank you for your support. I couldn´t follow yours suggestion because my xoom was not recognizing the PC or MAC. However I discovered that my sdcard was broken. When I´ve tried a new one with ZIP files inside it works perfectcly and I could return to my old room doing flah in the recovery mode of TWRP2.2.
It is important to note that my Xoom did not find .IMG files inside the card but only ZIP ones. Any way it worked perfectly and I hope this solution will serve to other in solving his/her problems.
Many thanks
Well, that works too, and that was closer to what I originally suggested (tho I didn't expect you had a bad sd card.)
And yes, recoveries generally don't support IMG files directly, you need to have a specially crafted zip to flash those in. IMG files directly are for fastboot/pc tool flashing.
Congrats on fixing it.
First I'll give credit where it is due. From two threads on this site is where I got help with this issue:
I followed THIS guys steps for manually erasing and got the recovery images and lots of other useful information from HERE. Thank you guys very much!
OK, so, hopefully I can help someone with my little story as well. I was having issues with apps and programs crashing on me with lollipop and the new marshmallow update. The tablet just wasn't working properly and moving slow. I even had the SD card holding all my apps and larger files so I didn't overload the internal storage. So, I decided I wanted to flash back to factory/stock recovery and go from there. I did this using THIS method. I flashed via the "flash-all.bat" file (the command in fastboot is the same as the file name). I should note that there was one instance that failed during the install (I did try it again and got the same failure). Said something about “did you mean you wanted to flash this partition” or something, then showed it failed. After flashing I hit continue on the bootloader screen of the tablet and it said it was "cold booting." After about 5 minutes or so it started to boot but never made it past the NVidia screen. I tried wiping the phone with factory reset, wiping the cache, etc. and then re-flashing the recovery (again with the .bat file). I tried flashing TWRP but it didn't install apparently, because it still went to factory recovery. I even re-locked and then unlocked my bootloader to see if that would set everything straight. Nothing seemed to work. I knew I would eventually find a solution though so I kept looking. Stumbled on some other people that had the same issues but no solution (hope those people got it figured out). So here's what I did after some more research:
First, if you're in this situation and you did factory reset to try and resolve the problem, you may feel like you can no longer communicate with the device via fastboot/adb, but as long as you have the usb drive and your SDK tools installed (I used CodeWorks for Android all-in-one program) that shouldn't be a problem. You'll just have to be in the bootloader on the tablet.
-If for some reason you deleted or uninstalled your drivers and tools you'll have to download them again and then, the computer should still be able to communicate with the tablet. In the device manager under portable devices it will still show up as Module something or other. So the computer still sees the device but doesn't fully recognize it yet. Don't worry, this should still work! Just make sure you that fastboot is seeing the device by inputting "fastboot devices" in the command window and a 14 digit serial number should pop up. If it just says "list of devices" or there's nothing then you wont be communicating with the tablet.
Your device should be connected to your computer and started in bootloader mode. On your computer you should have the command prompt for adb/fastboot open. I just go to the folder where the .exe files are located and hold shift and right click in the white space of the folder, then select "open command window here."
From here follow the erase steps: stolen from manigault! :highfive:
fastboot erase system
fastboot erase userdata
fastboot erase boot
fastboot erase recovery
fastboot erase cache
Then flash your recovery MANUALLY:
fastboot flash recovery {dir}/recovery.img
fastboot flash boot {dir}/boot.img
fastboot flash system {dir}/system.img
fastboot flash userdata {dir}/userdata.img
fastboot flash staging {dir}/blob
fastboot flash dtb {dir}/tegra124-tn8-p1761-1270-a04-e-battery.dtb
You can download whatever recovery version you wish. I downloaded 2.2.2 because that's what my device came with out of the box on Christmas 2014. It will more then likely be a .zip file. To make this whole process a little easier simply extract the files in the .zip file where the adb.exe and fastboot.exe files are located (folder should be named platform-tools) and you can completely eliminate typing the whole directory before the file name. ***After your done flashing everything you can go back and delete those files if you want. Just double check that you're deleting the right files by looking at the original zip file. Not sure if it makes a difference but I deleted them anyway.
For example the commands in fastboot will look like this exactly :
(after extracting recovery files into platform-tools folder)
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
fastboot flash dtb tegra124-tn8-p1761-1270-a04-e-battery.dtb
Note: Do NOT use the flash-all.bat command as this doesn't seem to work for this situation. Do it manually like shown above. And let each individual process complete before attempting to input another command.
After this step I didn't select continue on the bootloader. You can either select reboot or simply input "fastboot reboot" into the command window. It may take about 5 minutes to start installing everything but just be patient, it should start. Sometimes with these things you have to do things twice before it works. If for some reason it doesn't work the first time then start from the beginning and try it again. It took two times for me, but that's because I installed system.img twice and was getting double screen. Newb error... and I was a bit inebriated last night when I did this.
Hope this helps someone!
Thanks again to manigault and MidgetMob!
NVIDIA download files HERE!
i think i done the same thing
but the problem i now have is i cnt get tablet into fastboot on pc. i can load fastboot on tablet with power and volume down , but the tablet only shows as MTP device in device manager. i have downloaded drivers from nvidia and no matter what i try i cant install them i have been through all instructions but scince it went to mtp device i cant get device showing in adb. The only way i can get device showing in adb on pc ist to select apply update from adb ! but none of these commands listed in your post will work because its in sideload. is there anyway i cn reset , flash custom rom ect bu using commands while device is in adb sideload.
all i get is now send the package you want to apply to the device with "adb sideload <filename>".....
if you could shed any light on this it would be much appreciated , thanks , lester
did you update official android 6.0 before? then, not working stock recovery, stock boot...
If you can enter bootloader mode, download unofficial twrp 3.0.0.0 (here http://forum.xda-developers.com/shield-tablet/development/wip-twrp-2-8-0-1-unofficial-t2877117) and flash it.
i have a working boot.img file on marshmallow if you want.. please reply.
Sorry for the late response! I have no clue how you got into sideload??? Are you talking about through the recovery on your device? You're not able to get adb/ fastboot to recognize the device, right? It doesn't matter how you get the tablet into the bootloader. Whenever you have the phone in the bootloader then you'll use the fastboot command to "talk to" the device; i.e. "fastboot devices" without the quotes. That command should show your device if it shows as an MTP device whenever you open your "device manager" in windows. That's the same exact situation I was in. Download the codeworks from nvidia like I linked above. Hopefully then you should be able to recognize your device through the bootloader. If not DM me and I'll try to help you.
I'm having the exact problem as Lester. Tablet boots into bootloader but won't connect to computer. So I go into recovery mode and nothing works except apply update from adb. Which brings up the side load message that Lester quoted. And bootloader is showing "device=locked". I am attempting to fix this tablet for a friend that messed it up trying to flash a custom rom. Problem is he had no idea what he was doing and I'm not exactly sure what he did. I do however have a lot of experience with rooted android devices and flashing so any help would be GREATLY APPRECIATED!
---------- Post added at 05:59 PM ---------- Previous post was at 05:55 PM ----------
Also, I've already tried flashing stock rom back onto the tablet by applying update from sd card function in the recovery but when I try to do that the tablet for some reason can't mount the sd card.
rom fiend said:
Tablet boots into bootloader but won't connect to computer.
Click to expand...
Click to collapse
If you've got the device in bootloader then you need to use fastboot, not adb. Try the command 'fastboot devices' and see if the device id is listed. If so then grab a factory image, unzip it and use fastboot to flash the .img files using the commands 'fastboot flash system system.img'. Just make sure to match the partition names to the files.
Hello i have similar issue except when i try flash something i get this error ''remote: file write failed''
and i have to reboot into fastboot to get it flashing fully
but even though i managed to flash everything by rebooting when i boot system nothing shows up, i can just see the back light coming on and turning off after a while
Please help