Related
To this point I have managed to root and unlock my Captivate with great success. I have also managed to run various ROM's, Cognition, Serendipity, Paragon, etc.
I was using Serendipity 5.3 and the Steam kernel, I tried adding afterburner features and have now gotten stuck. The phone continues to reboot into steam recovery and I can navigate, but always receive "Partition /res/.fake/gingerbread/system could not be mounted! What should I do?"
I can get into download mode very easily by pulling the battery, putting battery back in, holding vol up and down then plugging phone into usb cable. From that point it just hangs plugged in or not, no communication with the pc, I can see the device as an Android UMS composite drive but can't write to the drive. I have tinkered in the console mode from Steam recovery and some of the usual commands will work such df -h to see drives and size, ls shows all the contents on the phone.
I run Linux on both my desktop and laptop, I have Xp in a VM with USB support, it shows as a Nexus device but Odin will not communicate with the device either. I have tried Heimdall, but receive the following.
Claiming interface... Success
Setting up interface... Failed!
I originally used Heimdall when flashing the first time then moved to CWM and never had an issue until I began fooling around with the kernel.
I'm hoping this is a repairable situation, maybe using the console in steam recovery? Just not sure what the commands might be or I may be barking up the wrong tree altogether.
Thanks in advance for any help offered.
I was in rogue recovery and was partitioning an old sdcard i messed up a while back it finished partitioning then my figure hit the power button by mistake..wich shouldnt have hurt anything since it was fished doing what it was doing any way.
I think reboot recovery was hilighted when i hit the power button. It went black and never turned back on. Ive tried the volume+power and adb wont work unless its powered on so im screwed. When i plug into comp nothing happens but when i plug in the charger i get the white charging light.
Ive looked around at other brick threads but they were all stuck at moto logo and stuff but i cant even get that.
ericman77 said:
I was in rogue recovery and was partitioning an old sdcard i messed up a while back it finished partitioning then my figure hit the power button by mistake..wich shouldnt have hurt anything since it was fished doing what it was doing any way.
I think reboot recovery was hilighted when i hit the power button. It went black and never turned back on. Ive tried the volume+power and adb wont work unless its powered on so im screwed. When i plug into comp nothing happens but when i plug in the charger i get the white charging light.
Ive looked around at other brick threads but they were all stuck at moto logo and stuff but i cant even get that.
Click to expand...
Click to collapse
I'm not really familiar with the Rogue recovery for the Xoom (what it actually partitions when you choose "partition sdcard") but are you sure you were partitioning your external sdcard? in the Xoom, the internal storage is also called sdcard. IF you did the internal sdcard, you would be in trouble. I can't imagine that the recovery would let you do that though...
Yeah surly it wouldn't have an option to partition the internal sdcard. Ive used this option several times in clockwork recovery to fix cards. I never even seen any option to choose ether internal or external sdcard. It just said partition sdcard in the advanced. I'm looking at instructions to build a moto programing cord to force it to boot into fastboot.
I made the program cable. I plugged it in it started installing drivers then failed to install. Went to the next usb port then the same thing and the same on the third.
I went to moto.com got the usb drivers now when i plug it in the pc just makes the sound that it does when you plug something in and nothing happens. I checked adb devices in cmd and theres nothing. anybody have any ideas?
The same prob here
ericman77 said:
I made the program cable. I plugged it in it started installing drivers then failed to install. Went to the next usb port then the same thing and the same on the third.
I went to moto.com got the usb drivers now when i plug it in the pc just makes the sound that it does when you plug something in and nothing happens. I checked adb devices in cmd and theres nothing. anybody have any ideas?
Click to expand...
Click to collapse
Hi mates,
I have the same prob like ericman77. When I plug the usb to PC I can heard the sound when a USB is plugged in a PC, but when I am typping "adb devices", CMD says "List of devices attached" without any device. (RDS2 or RDS3 prob¿?¿?¿)
I found some interesting links that are talking about made a "service cable", solding en micro-usb's 5 pin a cable from red cable. I did it one, but nothing changed it.
Today, I will try to do another service cable, and crossing my fingers for found a solution.
I've installed SDK from Android (adb...) and downloaded moto drivers before. I am working on Win7 64 bits.
Any idea?
Thanks in advance.
Xavi.
Solved!
xfernandezs said:
Hi mates,
I have the same prob like ericman77. When I plug the usb to PC I can heard the sound when a USB is plugged in a PC, but when I am typping "adb devices", CMD says "List of devices attached" without any device. (RDS2 or RDS3 prob¿?¿?¿)
I found some interesting links that are talking about made a "service cable", solding en micro-usb's 5 pin a cable from red cable. I did it one, but nothing changed it.
Today, I will try to do another service cable, and crossing my fingers for found a solution.
I've installed SDK from Android (adb...) and downloaded moto drivers before. I am working on Win7 64 bits.
Any idea?
Thanks in advance.
Xavi.
Click to expand...
Click to collapse
Hi folks,
at least a ssolution come to my home.
I had RSD 3 error, so what does it means? My pc recognise Xoom. So, here there are the steps:
First of all, all drivers and SDK on your computer.
Plug USB and the to Xoom. The PC will recognise with the special sound.
Go to this site htt*://developer.motorola.com/products/software/ (register need) and download the files from your xoom model.
Type this:
adb reboot bootloader
fastboot flash boot <dir from boot.img>
fastboot flash system <dir from system.img>
fastboot flash recovery <dir from recovery.img>
fastboot flash userdata <dir from userdata.img>
fastboot erase cache
fastboot reboot
In "dir from" you have to paste all the files that you doanloaded before.
And at least, I have my Xoom alive again.
Thanks mates.
Good luck.
Xavi.
Good job!
Glad you bring xoom back to life!
...I think these threat will help others as well!
I'm thinking I'm just screwe. Adb reboot bootloader gives me error device not found.
Motorola Xoom screen Freezes
Hi,
I am very new and am a novice to software in general. I have a xoom, I followed the steps as described here
http://forum.xda-developers.com/showthread.php?t=1242241
and was able to
a) Set up ADB
b) Get the required drivers
c) Unlock the bootloader
d) Get CWM to work
e) was able to do In cwm, go into "install zip from sdcard" -> "Choose zip from sdcard", then select the Xoom-Universal-Root.zip file you downloaded.
f) I did not have this file in my micro sd card, so I accessed the computer as an USB through CWM and pasted the file into SD card
g) Then it showed in SD card
h) Then I chose it from SD card
i) The message I got is SU is installed
j) Then there was a reboot, however it freezes at the Motorola screen
I am able to get into CWM, but can not get the device to go beyond the Motorola screen.
My objective when I started this was to install a new ROM
Please help and thanks for all help.
Update - 1 and Help request
Since I could access the CWM through the device keys, I thought may be I can install another rom and it would work, so the steps I follwed
a) Connect device to Desktop
b) Device not detected, the adb devices returned nothing
c) other commands returned "waiting for device"
d) any way I connected the device to desktop using a blackberry USB cable
e) Entered Recovery mode
f) Mounted USB storage and accessed the SD card through desktop
g) Saved the file "Eos-umts_everest-2.0.0.zip" into the SD card by accessing this through the Desktop
h) used the CWM to install this zip
i) Installed the google aps as mentioned by team EOS
Result - No more Freezed Motorola screen, and there was a Team EOS screen after that there is an animation which is still going on. I am assuming this is ok and intend to let it run as long as possible. Now it's on charge and then I will take it off charge and let it run till the battery drains itself. Do let me know if I am doing anything wrong.
gaganpattanayak said:
Since I could access the CWM through the device keys, I thought may be I can install another rom and it would work, so the steps I follwed
a) Connect device to Desktop
b) Device not detected, the adb devices returned nothing
c) other commands returned "waiting for device"
d) any way I connected the device to desktop using a blackberry USB cable
e) Entered Recovery mode
f) Mounted USB storage and accessed the SD card through desktop
g) Saved the file "Eos-umts_everest-2.0.0.zip" into the SD card by accessing this through the Desktop
h) used the CWM to install this zip
i) Installed the google aps as mentioned by team EOS
Result - No more Freezed Motorola screen, and there was a Team EOS screen after that there is an animation which is still going on. I am assuming this is ok and intend to let it run as long as possible. Now it's on charge and then I will take it off charge and let it run till the battery drains itself. Do let me know if I am doing anything wrong.
Click to expand...
Click to collapse
The first boot-up can be quite long, but if it goes past, say 20 minutes, get the Xoom back into recovery and you should wipe cache partition, go to advanced and wipe dalvik cache, go back and re-flash the ROM and the Gapps files and then reboot. You might also want to re-download the ROM zip file, just in case the download was corrupt.
Good luck!
I'm thinking what ever I did when I formatted that sdcard must have completely whipped my hole xoom. Good thing I had a 3 year square trade warranty.
ericman77 said:
I'm thinking what ever I did when I formatted that sdcard must have completely whipped my hole xoom. Good thing I had a 3 year square trade warranty.
Click to expand...
Click to collapse
That's what I said in my first comment...it formatted the partitions of your internal "sdcard"...your "hard drive" in essence. That's why I stay away from that operation completely.
Update - 2 and Help request
Please see quote below,
I have mentioned that I was able to root and then upgrade to Teameos ROM. However I tried various options in Goo Manager and when I tried to flash other roms, I got a message that I need an open recovery enabled script. The goo manager offered to find and install one for me, I tried that however the same message that I need an open recovery enabled script when ever I tried to flash nightlies. Hence I decided to go back to the stock rom
a) Downloaded the relevant files from Motorola websites
b) Followed the instructions and was able to downgrade and followed the instructions for OTA updates after flashing the stock rom
c) Now this has replaced the Clockwork mod recovery.
d) Now I want to reinstall Clockwork mod
e) Hence, unlocked the bootloader, got confirmation on Xoom that it is unlocked and the device rebooted automatically, I did not have to type the reboot command in ADB
f) I flashed the clockworkmod recovery image as I have done it earlier
g) The device says flashing is successful
h) However when I reboot there is no CWM
I started surfing and realized that this is has something do with the OTA updates.
So I again flashed the Motorola stock and did the CWM without the OTA, even then I am not able to get the CWM
Please just link me to proper post so I can learn, thanks for all the help
gaganpattanayak said:
Since I could access the CWM through the device keys, I thought may be I can install another rom and it would work, so the steps I follwed
a) Connect device to Desktop
b) Device not detected, the adb devices returned nothing
c) other commands returned "waiting for device"
d) any way I connected the device to desktop using a blackberry USB cable
e) Entered Recovery mode
f) Mounted USB storage and accessed the SD card through desktop
g) Saved the file "Eos-umts_everest-2.0.0.zip" into the SD card by accessing this through the Desktop
h) used the CWM to install this zip
i) Installed the google aps as mentioned by team EOS
Result - No more Freezed Motorola screen, and there was a Team EOS screen after that there is an animation which is still going on. I am assuming this is ok and intend to let it run as long as possible. Now it's on charge and then I will take it off charge and let it run till the battery drains itself. Do let me know if I am doing anything wrong.
Click to expand...
Click to collapse
I was able to sort it out. Had to install the Gapps package.
However I was mot able to install this through goo manager. Had to download it to the SD card and install it via CWM
Regards and Thank you for all help
gaganpattanayak said:
I was able to sort it out. Had to install the Gapps package.
However I was mot able to install this through goo manager. Had to download it to the SD card and install it via CWM
Regards and Thank you for all help
Click to expand...
Click to collapse
Goomanager is great and it is also still a work in process. I'm glad you figured it out.
anyone have solutions for not powering on after flashing?
05/30/2012 14:26:08 [WARNING] Machine: stingray
05/30/2012 14:26:08 [INFORMATION] stingray_panel_init: setting pll_c to 598000000 Hz plck to 66400000 Hz
05/30/2012 14:26:09 [INFORMATION] print_constraints: stingray_panel_reg: 5000 mV
05/30/2012 14:26:12 [INFORMATION] GPIO Input Driver: Start gpio inputs for stingray-keypad in interrupt mode
05/30/2012 14:26:12 [INFORMATION] input: stingray-keypad as /devices/virtual/input/input7
05/30/2012 14:26:12 [INFORMATION] using input dev stingray-keypad for key reset
05/30/2012 14:26:13 [INFORMATION] keychord: using input dev stingray-keypad for fevent
05/30/2012 14:26:14 [INFORMATION] stingray_gps_reset_gpio: setting GPS Reset GPIO to 0
05/30/2012 14:26:14 [INFORMATION] stingray_gps_standby_gpio: setting GPS standby GPIO to 0
05/30/2012 14:26:14 [INFORMATION] stingray_gps_reset_gpio: setting GPS Reset GPIO to 1
05/30/2012 14:26:14 [INFORMATION] stingray_gps_standby_gpio: setting GPS standby GPIO to 1
05/30/2012 14:26:32 [INFORMATION] stingray_gps_standby_gpio: setting GPS standby GPIO to 0
I used android-os-monitor to get this, my xoom is mz601, i am curious why the machine identifies it as stingray.
does it mean i can flash roms for stingray
Sent from my MZ601 using xda premium
gaganpattanayak said:
05/30/2012 14:26:08 [WARNING] Machine: stingray
05/30/2012 14:26:08 [INFORMATION] stingray_panel_init: setting pll_c to 598000000 Hz plck to 66400000 Hz
05/30/2012 14:26:09 [INFORMATION] print_constraints: stingray_panel_reg: 5000 mV
05/30/2012 14:26:12 [INFORMATION] GPIO Input Driver: Start gpio inputs for stingray-keypad in interrupt mode
05/30/2012 14:26:12 [INFORMATION] input: stingray-keypad as /devices/virtual/input/input7
05/30/2012 14:26:12 [INFORMATION] using input dev stingray-keypad for key reset
05/30/2012 14:26:13 [INFORMATION] keychord: using input dev stingray-keypad for fevent
05/30/2012 14:26:14 [INFORMATION] stingray_gps_reset_gpio: setting GPS Reset GPIO to 0
05/30/2012 14:26:14 [INFORMATION] stingray_gps_standby_gpio: setting GPS standby GPIO to 0
05/30/2012 14:26:14 [INFORMATION] stingray_gps_reset_gpio: setting GPS Reset GPIO to 1
05/30/2012 14:26:14 [INFORMATION] stingray_gps_standby_gpio: setting GPS standby GPIO to 1
05/30/2012 14:26:32 [INFORMATION] stingray_gps_standby_gpio: setting GPS standby GPIO to 0
I used android-os-monitor to get this, my xoom is mz601, i am curious why the machine identifies it as stingray.
does it mean i can flash roms for stingray
Sent from my MZ601 using xda premium
Click to expand...
Click to collapse
Stingray is for CDMA/LTE (and GSM???), wingray is wifi, only.
Is your Xoom for CDMA/LTE (US version usually) or is it GSM?
My xoom is MZ601, this would me umts evesrest its a gsm/wifi handset, however this is presenting itself as stingray, so can i install nightlies for stingray or not
Sent from my MZ601 using xda premium
Oh I am hoping someone here can help me out here. I just got this tablet, and tried to do the Froyo update, only to find out (too late) that this model is different and not up-gradable to the 2.2. After screwing around a bit with it, not sure what happened, but now the entire system is gone.
It boots to the Cruz logo, and sits there. ADB recognizes it, but I have no shell access, and when I do a ADB ls /system it lists only 2 files, with random numbers.
ADB remount - FAILS
ADB reboot fastboot - FAILS (just reboots it)
ADB reboot recovery - gets to recovery (in ADB devices) but tablet is blank, but no sh access
Vol + & power do nothing.
Vol - & power do nothing
While attached to my PC (Win7-64) and hit the reset and Vol -, it shows up as JZ4760 USB Boot, but Windows REFUSES to let me install any drivers for it. (Got the USBToolKit, but even after turning off driver signing, it still says they're not signed and refuses to load them)
I got the 2.0 firmware (default) so now what I need it a way to push the img files to the tab (hopefully)
Any ideas, or is this thing really a neat little brick now?
Thanks
No one?? Come on guys...I've been on this site for a long time, and have seen some of you pull out a brick and make a phone out of it again. LOL
I'm thinking if I can just get fastboot to load somehow on the tablet, I could issue commands from my PC to "push" the image files back over.
Question is: how do I get fastboot to get onto the tablet to load into???
I would like a copy of your firmware if still available for the cruz of course impossible to find as site is no longer hosted
Hi.
It's been some time since i tried fixing my Asus Transformer...
The problem is : If it has battery life. It boot's and gets stuck on the first screen.
With the logo "eee pad" .
If i turn it off, it automaticly reboots and gets stuck in the same screen.
If i try to get into recovery mode.
Vol down, Powerup... and the vol up , i can see the few line's of code , saying it will boot into recovery mode.
but while trying to start recovery mode the icon changes to a fallen android and an "! triangle above it
I've been looking around forums evrywhere but i cant find a solution for my exact problem.
can anyone help?
Quickly, with the info you provided, I would think your firmware or storage may be damaged.
Can you access ADB? Sometimes you can while it boots, even if it doesn't fully boot. That would allow you to check logs and back up data.
Can you access APX? It has nothing to do with Android, it's a part of the device made by Asus to allow you to "inject" a firmware inside the device while it's in "brick" state.
If you can access ADB, you can "pull" the files you want from the device to your computer. You can see information on ADB here. Basically you install the package from google and connect the device to your computer, then run a set of commands.
If you can access APX (chances are you can unless there's hardware damage), then EasyFlasher can push a stock firmware back to the device. This will wipe your device 100% back to stock and you will lose all your files.
Lethe6 said:
Quickly, with the info you provided, I would think your firmware or storage may be damaged.
Can you access ADB? Sometimes you can while it boots, even if it doesn't fully boot. That would allow you to check logs and back up data.
Can you access APX? It has nothing to do with Android, it's a part of the device made by Asus to allow you to "inject" a firmware inside the device while it's in "brick" state.
If you can access ADB, you can "pull" the files you want from the device to your computer. You can see information on ADB here. Basically you install the package from google and connect the device to your computer, then run a set of commands.
If you can access APX (chances are you can unless there's hardware damage), then EasyFlasher can push a stock firmware back to the device. This will wipe your device 100% back to stock and you will lose all your files.
Click to expand...
Click to collapse
With my Ubuntu, if i do the command ./adb device
Then i can see a number. So the device is connected i think.
I am not sure if i can access APX, i do not yet how to test tis yet.
Is there an easy way to see / test this in ubuntu ?
DarkCloud98 said:
With my Ubuntu, if i do the command ./adb device
Then i can see a number. So the device is connected i think.
I am not sure if i can access APX, i do not yet how to test tis yet.
Is there an easy way to see / test this in ubuntu ?
Click to expand...
Click to collapse
APX mode is just a black screen, but your PC will install drivers and see the device when you enter that mode
Hold Volume up & Power until the USB connect sound appears, now you are in APX mode - there will be nothing on the screen of the transformer until you are flashing a new ROM maybe
What serial number is your TF ?
NVFlash is the quickest way to get back to 100% working stock
http://www.xdafileserver.nl/Files/A...OMS/ICS .27/NVFLASH_ICS_9.2.1.27_WW_NOROOT.7z
*Detection* said:
APX mode is just a black screen, but your PC will install drivers and see the device when you enter that mode
Hold Volume up & Power until the USB connect sound appears, now you are in APX mode - there will be nothing on the screen of the transformer until you are flashing a new ROM maybe
What serial number is your TF ?
NVFlash is the quickest way to get back to 100% working stock
Click to expand...
Click to collapse
I tried the "hold volume up & power" when connected to my Windows PC.
I did see the "usb connection" and heard the sound.
But it says the installation failed.
my serial number of my TF is B60KAS032926
DarkCloud98 said:
I tried the "hold volume up & power" when connected to my Windows PC.
I did see the "usb connection" and heard the sound.
But it says the installation failed.
my serial number of my TF is B60KAS032926
Click to expand...
Click to collapse
NVFlash is supported for your serial number, make sure you are running the download.bat as Administrator (Right click > Run as Admin)
Remove any other USB devices from the PC (apart from your keyboard and mouse)
Connect the TF to the PC > Power off the TF > Hold Vol up and Power until USB connects, run download.bat as Admin
*Detection* said:
NVFlash is supported for your serial number, make sure you are running the download.bat as Administrator (Right click > Run as Admin)
Remove any other USB devices from the PC (apart from your keyboard and mouse)
Click to expand...
Click to collapse
Ok, i'l try that right now.
The APX driver is installed now.
i'l try NVFlash
DarkCloud98 said:
Ok, i'l try that right now.
The APX driver is installed now.
i'l try NVFlash
Click to expand...
Click to collapse
I edited my post with quick instructions
Connect the TF to the PC > Power off the TF > Hold Vol up and Power until USB connects, run download.bat as Admin
*Detection* said:
NVFlash is supported for your serial number, make sure you are running the download.bat as Administrator (Right click > Run as Admin)
Remove any other USB devices from the PC (apart from your keyboard and mouse)
Connect the TF to the PC > Power off the TF > Hold Vol up and Power until USB connects, run download.bat as Admin
Click to expand...
Click to collapse
When do i know if it's done. And is there any other thing required?
I used the NVFLASH_ICS_9.2.1.27_WW_NOROOT
and running download.bat with admin its starts a terminal.
after this is done, i see 2 lines of information on my Asus transformer. only chip Uid and Nv3P server
DarkCloud98 said:
When do i know if it's done. And is there any other thing required?
I used the NVFLASH_ICS_9.2.1.27_WW_NOROOT
and running download.bat with admin its starts a terminal.
after this is done, i see 2 lines of information on my Asus transformer. only chip Uid and Nv3P server
Click to expand...
Click to collapse
That's good, its working, you can watch command prompt I think if it stays open to watch the progress as it sends the files across, can't remember exactly, but the TF should reboot on its own when its done
It can take 10mins or more iirc so just leave it to do its thing, then it shoot boot up
The only thing I remember having to do, was once it had booted, and I manually reboot the TF, it would hang on a black screen (Only that first reboot though) holding power for around 30 seconds, then powering on normally fixed it and it never does it again, just that first boot
Might not even happen on yours, could be a fault on my TF
*Detection* said:
That's good, its working, you can watch command prompt I think if it stays open to watch the progress as it sends the files across, can't remember exactly, but the TF should reboot on its own when its done
It can take 10mins or more iirc so just leave it to do its thing, then it shoot boot up
The only thing I remember having to do, was once it had booted, and I manually reboot the TF, it would hang on a black screen (Only that first reboot though) holding power for around 30 seconds, then powering on normally fixed it and it never does it again, just that first boot
Might not even happen on yours, could be a fault on my TF
Click to expand...
Click to collapse
ok sweet, thx !
i hope it'l boot soon
after that...i'l need to root it again i think. ...but thats for later.
Now it would be awsome to let it work again.
thx again for the help
DarkCloud98 said:
ok sweet, thx !
i hope it'l boot soon
after that...i'l need to root it again i think. ...but thats for later.
Now it would be awsome to let it work again.
thx again for the help
Click to expand...
Click to collapse
You could flash the pre-rooted versions too although I think it's easy enough to root yourself these days
This is the XDA Fileserver for different ROMs if you need them
http://www.xdafileserver.nl/index.php?dir=Asus/Asus+Transformer+(TF101)
I was just reading someone else who had the same display stuck on their TF while trying to use NVFlash and they said re-downloading the ROM and trying it again fixed it
So if this fails for some reason, try another NVFlash ROM from the XDA Server
*Detection* said:
That's good, its working, you can watch command prompt I think if it stays open to watch the progress as it sends the files across, can't remember exactly, but the TF should reboot on its own when its done
It can take 10mins or more iirc so just leave it to do its thing, then it shoot boot up
The only thing I remember having to do, was once it had booted, and I manually reboot the TF, it would hang on a black screen (Only that first reboot though) holding power for around 30 seconds, then powering on normally fixed it and it never does it again, just that first boot
Might not even happen on yours, could be a fault on my TF
Click to expand...
Click to collapse
seems to still do nothing more.
sure i'm not missing the something i should add to the NVFLASH ?
DarkCloud98 said:
seems to still do nothing more.
sure i'm not missing the something i should add to the NVFLASH ?
Click to expand...
Click to collapse
NVFlash contains everything you need, ROM and NVFlash tools to install it to the TF, I've used that exact same download on mine so it should be working
Did you have any progress showing in command prompt ?
It should say something like
Deleting partition
1
2
3
4
5 etc
Then creating partiton
1
2
3
4
5etc
Then sending boot.img
sending system.img <<<<< This one takes a while
Try it a few times until you start seeing progress in CMD, if you don't see it after a few minute, cancel it again try again
There is also a Linux version of NVFlash you could try
http://forum.xda-developers.com/showthread.php?t=1123429
*Detection* said:
NVFlash contains everything you need, ROM and NVFlash tools to install it to the TF, I've used that exact same download on mine so it should be working
Did you have any progress showing in command prompt ?
It should say something like
Deleting partition
1
2
3
4
5 etc
Then creating partiton
1
2
3
4
5etc
Then sending boot.img
sending system.img <<<<< This one takes a while
Try it a few times until you start seeing progress in CMD, if you don't see it after a few minute, cancel it again try again
There is also a Linux version of NVFlash you could try
Click to expand...
Click to collapse
i see =
sending file: transformer.bct
- 4080/4080 bytes sent
transformer.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: blob.EBT
/ 786432/1454712 bytes sent
and when it's done , the cmd closes and thats about it.
so'l best try it a few times?
DarkCloud98 said:
i see =
sending file: transformer.bct
- 4080/4080 bytes sent
transformer.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: blob.EBT
/ 786432/1454712 bytes sent
and when it's done , the cmd closes and thats about it.
so'l best try it a few times?
Click to expand...
Click to collapse
Did the TF not reboot on its own ?
Have you tried booting it manually by holding power for 30 seconds then powering on normally ?
That all looks like its working fine, sending the files across
EDIT - I`ll upload an older version that I have saved, it has a different file structure and uses .img instead of .blob
EDIT - Try this NVFlash
http://www.portableandroid.co.uk/androidDL/new Windows.zip
*Detection* said:
Did the TF not reboot on its own ?
Have you tried booting it manually by holding power for 30 seconds then powering on normally ?
That all looks like its working fine, sending the files across
EDIT - I`ll upload an older version that I have saved, it has a different file structure and uses .img instead of .blob
EDIT - Try this NVFlash
Click to expand...
Click to collapse
I Just Tried the linux NvFlash.
and the boodloader sending = send succesfully
but the next step it says : "File not found: recovery.img"
Failed executing command .... NvError 0x4
Command failure: create failed.
I'm nog going to try the last NVversion you linked with my Windows PC
EDIT: And the other NvFlash version you linked me, does the same...after it being sent, the CMD closes and thats it
DarkCloud98 said:
I Just Tried the linux NvFlash.
and the boodloader sending = send succesfully
but the next step it says : "File not found: recovery.img"
Failed executing command .... NvError 0x4
Command failure: create failed.
I'm nog going to try the last NVversion you linked with my Windows PC
Click to expand...
Click to collapse
I think maybe the linux version is the older .img version, and the files are .blob so it can't find anything
The one I linked you is the .img windows version, hopefully you'll have more luck with that
If not, put all the .img files into the linux folder and try it that way
*Detection* said:
I think maybe the linux version is the older .img version, and the files are .blob so it can't find anything
The one I linked you is the .img windows version, hopefully you'll have more luck with that
If not, put all the .img files into the linux folder and try it that way
Click to expand...
Click to collapse
It worked !!!
By using the linux download.sh but by adding all the files in the from the windows folder that were missing.
Thank you very much !!!
DarkCloud98 said:
It worked !!!
By using the linux download.sh but by adding all the files in the from the windows folder that were missing.
Thank you very much !!!
Click to expand...
Click to collapse
Great news! Linux vs Linux did the trick
How long have you been without your TF until now? It'll be like having a new toy again I would imagine
(first, If im on the wrong thread can you help with asking a moderator to move it to the correct place, or how ever that would work? Thanks!!)
Im on Linux Mint 18 Sarah Cinnamon 64 bit
I'm trying to root my Nvidia K1 shield tablet. no idea what im doing and the more I research this the more confusing it gets. Seems like If you ran windows theres "Clear Cut & Right to the Point" instructions about how to do this on about 14 hundred pages of great info including great you tube videos which heavily explain it, in great easy to understand detail.
What Ive done so far.
installed ADB and BootLoader (but ive no idea how to actually use these programs yet, still figuring that one out)
I have sucessfully Unlocked the Device
Now im trying to flash the .img I hit this command (from terminal) and get this result
$ fastboot flash recovery recovery.img
target reported max download size of 100663296 bytes
sending 'recovery' (16384 KB)...
OKAY [ 0.658s]
writing 'recovery'...
OKAY [ 0.651s]
finished. total time: 1.309s
Now following these steps at this website http://developer.download.nvidia.co.../0_0_0_Factory/HowTo-Flash-Recovery-Image.txt
im on the:
$ fastboot flash boot boot.img
error: cannot load 'boot.img'
Now ive no idea what to do, how to fix this ,or even if im following the right directions. what I need is (im going to throw a nice Trump statement here)
Can someone explain how you root a Nvidia shield K1 tablet, start to finish, ON LINUX, and every step simplified along the way explained, PERIOD!!!!
Everyone starts to tell you how to do this, then they jump on a windows PC throwing me all off...
now my .img file is from this website https://www.androidfilehost.com/?fid=24269982087005399
its in my downloads folder if that matters??? Not sure but i think it does. If i need to move this .img file somewhere please explain how to do it, don't just say "oh your problem is you need to move it to /usb/local/ or something," and just leave it there. remember i need help, so if I need to move things and use commands please help me with that. thank you
You know I got my MCSE, MCSA, A+ SERVER+ NET+ NOVEL and I can write python Programs and im getting into Julia. I know DOS, & I feel im a power User on Andriod, and ive been using personal computers since the 1970's. But when it comes to linux, I cant even google my way out of anything, even if the problem is very minor and simple, still, I cant google my way out of anything on linux its crazy. I keep having to write on forums on threads to find the answer. Someone with my Creds, granted most were aquired in 2002, shouldnt struggle like I do with linux, the support is terrible, and I dont mean updates for software and hardware, im sure thats fine. But when it comes to user support and the documentation for instruction, you get pages of results that have more links then answers on the page to other peoples help pages, that link more to other pages. You cant just goto 1 page, get the answer, done finished your allset, NOPE LINUX does not work that way and its to bad, I see why most of the world doesn't use it.
Good analogy right here, if someone in your neighborhood is giving out free gold to anyone, you know ya whole villiage or town is going to be there getting free gold, ya well, if Linux was that good, the whole world would be using it, and there not, and its free just like the gold. So does that tell you anything?
settled that, smashed the tablet, going to mount it on my wall as a reminder for tech not to mess with me. and yes linux sucks balls!!!!
Maverick617 said:
settled that, smashed the tablet, going to mount it on my wall as a reminder for tech not to mess with me. and yes linux sucks balls!!!!
Click to expand...
Click to collapse
I suggest anger management and growing some sort of ability to wait periods of time before going all hulk smash... You waited all of 2 hours for someone to tell you you had already finished all you needed a pc for... After flashing the twrp recovery over adb all you needed to do was boot into it. you could have done so by shutting it off then holding vol down and power to get you to the fastboot menu then use the volume rockers to go to recovery the power button will be enter in this case and it should boot the recovery you just loaded.
From there you flash the super su binary you already downloaded and when you boot into the tablet after that you can load a apk from the google play store supersu is what i use then you are rooted...
mirrin said:
I suggest anger management and growing some sort of ability to wait periods of time before going all hulk smash... You waited all of 2 hours for someone to tell you you had already finished all you needed a pc for... After flashing the twrp recovery over adb all you needed to do was boot into it. you could have done so by shutting it off then holding vol down and power to get you to the fastboot menu then use the volume rockers to go to recovery the power button will be enter in this case and it should boot the recovery you just loaded.
From there you flash the super su binary you already downloaded and when you boot into the tablet after that you can load a apk from the google play store supersu is what i use then you are rooted...
Click to expand...
Click to collapse
Also just going to add the process is the same in mint/ubuntu as it is in windows. Getting fastboot/adb is the only difference, and it basically tells you how to do if you try using fastboot without it installed. Also make sure you are in the right directory and type the correct name or you get the cant load message.
Additionally as someone who had to learn linux cli on Red hat i would have to say vs ms dos about the same... if the op thinks mint is bad i have some old yellow dog and mandrake 7.0 disk i can send him. He does not know the pain of trying to find the drivers on repositories and such just to get the sound and Ethernet working... Had the issue of my realtek 10/100 card not working under linux but my 3com card would if i had preloaded the drivers...
I have tried unbuntu and mint both gave a very similar experience to installing windows. With the exception unlike windows i did not need to patch 1000 things before using it and everything just worked.
Also Android is linux...
SHIELD TABLET K1 RECOVERY IMAGE FLASHING INSTRUCTIONS
To follow the instructions in this guide, you will need adb and fastboot.
These tools are provided as part of the Android SDK:
http://developer.android.com/sdk/index.html
Before flashing this recovery image to your SHIELD TABLET, connect your SHIELD TABLET
via USB to the PC where you downloaded this recovery image.
Next, put your SHIELD TABLET into fastboot mode using one of the following methods:
SW method:
- Boot to android home screen
- Connect the device to linux/windows system
- Open terminal (on linux); command prompt (on windows).
- Type "adb reboot bootloader" in terminal/command prompt
HW method: (If you had done this after the part you loaded what ever recovery nvidia tried pushing on you it should have worked)
- Turn off the device
- Press "Volume Down" -> "Power", hold "Volume Down" and leave Power buttons till device boots
(I dont even know what this from nvidia is talking about)http://forum.xda-developers.com/shi...recovery-twrp-2-8-7-0-touch-recovery-t3257172 <--go to the xda first next time...
To flash this recovery image to your SHIELD TABLET, run the following commands from
the directory where you extracted the recovery image package. If this is the
first time you have done this procedure, you must unlock the bootloader (see
below):
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase userdata
fastboot flash staging blob
(Better instructions that i found on this place)
https://twrp.me/devices/nvidiahshieldtablet.html
adb reboot bootloader
(https://dl.twrp.me/shieldtablet/) Download latest here rename the .img file twrp.img maesure the file is in the adb folder...
fastboot flash recovery twrp.img
fastboot reboot
After boot you can issue this command
adb rebooot recovery
or
shut off the tablet
hold vol down then hold power
then press vol down until recovery is highlighted then push power button...
Unlocking the Bootloader<you needed to do this first>
Your SHIELD TABLET may have shipped with a locked bootloader. To update the device,
you must unlock the bootloader using the following:
- fastboot oem unlock
- Press the "Volume Down" button to select "Unlock bootloader" option on device
- Press the "Power" button to confirm the unlock. Your device's bootloader is now unlocked.
Click to expand...
Click to collapse