Hello
I am not able to flash system.img , i get the cannot load system.img error in cmd prompt. All other .img flash fine
i flashed twrp and tried repair , did not help.
i have also fastboot erased cache , system , bootloader but it didnt help in clearing the system and flashing the stock one on top
Also i can flash a custom rom in TWRP and boot but the storage is then stuck at around 12 GB.
Any pointers guys ?
Are you flashing the files one by one or using the script?
A factory reset from stock recovery should bring you back to 32. After a good flash of course.
this happened to me once
heres how i fixed it on my windows vista machine
1- Make sure you run CMD as admin
2- Make sure you close all other applications before sending system.img (on my case it was chrome holding RAM even tho i have 3GB of RAM and plenty was available)
Solved
Thanks for the replies guys.
I fixed it by editing the command used to flash the system.img
fastboot flash -S 512M system system.img
It was for sure the RAM being used a lot on the current machine although i had 4 GB of RAM.
likonvampire said:
Thanks for the replies guys.
I fixed it by editing the command used to flash the system.img
fastboot flash -S 512M system system.img
It was for sure the RAM being used a lot on the current machine although i had 4 GB of RAM.
Click to expand...
Click to collapse
Wow thank you so much for this! I was running into this error on Windows 8.1 with 10GB of RAM and plenty free!!!! I guess this command sends it out and writes it in chunks? Can we figure out why this is happening?
Could it be instead related to using up inodes? And not RAM?
likonvampire said:
Thanks for the replies guys.
I fixed it by editing the command used to flash the system.img
fastboot flash -S 512M system system.img
It was for sure the RAM being used a lot on the current machine although i had 4 GB of RAM.
Click to expand...
Click to collapse
Thank you so much for this. My rig has 16 Gigs or ram, could it be something else causing this issue?
HELP!
on my side is showing me waiting for device what should i do?
Related
Hey, and thank you all here on the forums for all the guides and helpful information.
I am completely new at android rooting, flashing and all that comes with this, though I've read up quite a bit.
Now, my tablet is running the 4.2.1 build "JOP40D.WW_epad-10.6.1.14.10-20130801" which i've found can not be rooted in certain ways, so I went for the fastboot.
I've made sure everything was as should be, far as I can tell from what I've read here:
Tablet prepared:unlocked, usb debugging checked
adb and fastboot ready
correct drivers
latest twrp blow(openrecovery-twrp-2.6.3.2-tf700t.blob)
Then, as I put in the final command "fastboot -i 0x0B05 flash recovery twrp.blob" I get the message "error: out of memory" and the fastboot.exe crashed.
What could be causing this? Don't really want to try over again since I have no idea what I might be doing wrong and I really don't want to end up with the hassle of a bricked tablet.
Could it be an issue with the twrp version, and its compatibility with the tablet?
There is no lack of available memory on my computer, and there shouldn't be problems with the tablet's ROM or RAM, as it runs fine except for the obvious problem this tablet has. Previous to unlocking it was wiped and reset to stock 4.2.1 Jelly Bean with the .10 build.
The CMD window looks like this:
"
C:\users\Hbryne.Hbryne-PC>fastboot devices
015d2d431f240415 fastboot
C:\users\Hbryne.Hbryne-PC>cd c:\android-adb
c:\android-adb>fastboot -i 0x0B05 flash recovery twrp.blob
error: out of memory
"
Thanks in advance for any helpful reply!
HBMoe said:
Hey, and thank you all here on the forums for all the guides and helpful information.
I am completely new at android rooting, flashing and all that comes with this, though I've read up quite a bit.
Now, my tablet is running the 4.2.1 build "JOP40D.WW_epad-10.6.1.14.10-20130801" which i've found can not be rooted in certain ways, so I went for the fastboot.
I've made sure everything was as should be, far as I can tell from what I've read here:
Tablet prepared:unlocked, usb debugging checked
adb and fastboot ready
correct drivers
latest twrp blow(openrecovery-twrp-2.6.3.2-tf700t.blob)
Then, as I put in the final command "fastboot -i 0x0B05 flash recovery twrp.blob" I get the message "error: out of memory" and the fastboot.exe crashed.
What could be causing this? Don't really want to try over again since I have no idea what I might be doing wrong and I really don't want to end up with the hassle of a bricked tablet.
Could it be an issue with the twrp version, and its compatibility with the tablet?
There is no lack of available memory on my computer, and there shouldn't be problems with the tablet's ROM or RAM, as it runs fine except for the obvious problem this tablet has. Previous to unlocking it was wiped and reset to stock 4.2.1 Jelly Bean with the .10 build.
The CMD window looks like this:
"
C:\users\Hbryne.Hbryne-PC>fastboot devices
015d2d431f240415 fastboot
C:\users\Hbryne.Hbryne-PC>cd c:\android-adb
c:\android-adb>fastboot -i 0x0B05 flash recovery twrp.blob
error: out of memory
"
Thanks in advance for any helpful reply!
Click to expand...
Click to collapse
It looks as if you ran the 'fastboot devices' command from a different directory than 'fastboot -i 0x0B05....'
You cd'd into c:\android-adb
You have to run the fastboot cmd out of the same directory your fastboot.exe is in. And twrp.blob has to be in that directory (or folder) too.
berndblb said:
It looks as if you ran the 'fastboot devices' command from a different directory than 'fastboot -i 0x0B05....'
You cd'd into c:\android-adb
You have to run the fastboot cmd out of the same directory your fastboot.exe is in. And twrp.blob has to be in that directory (or folder) too.
Click to expand...
Click to collapse
Ah, could that have caused it? Figured the connection check could be done from anywhere - maybe that's what triggered the error. Tried again - although now without the check since I know it's connected and recognized - and it worked :laugh:
Thanks!
berndblb said:
You have to run the fastboot cmd out of the same directory your fastboot.exe is in. And twrp.blob has to be in that directory (or folder) too.
Click to expand...
Click to collapse
Not true if fastboot is properly installed in a directory that is in the PATH.
_that said:
Not true if fastboot is properly installed in a directory that is in the PATH.
Click to expand...
Click to collapse
True - but very few do...
Sent from my XT894 using Tapatalk
need help
hi im new here
i have alot of problems need help guys
first i was in build ww6.5.0 and was in root yesterday asus push new update in ota i download it and when my device restart to start setup it stop
and get erorr when it bootup gave me this (your device is recoverd to the original configuration) then i delete root (frome super user) and download the update again
same prob
sec idownload the raw image frome asus offcial site ww6.5.0 and my device freez after boot to setup the image and i force it to shutdown after that i can't make factory reset
saying to me E:unable to write /cashe/recovery/command file
and i have no root now
today i downoade the new image UL-K00E-WW-6.6.1.0-user.zip it start fine and copy fiels but got errors too
:Eunable to rename file /cashe/update.zip: cross-device linkE:unable to write file
E:unable to write file: /cashe/update.zip
E:update flash failed
flash failed
fail(flash_cmds error!)
Hi everyone,
I was on 4.4.2 and wanted to update to 4.4.3. Since I installed Xposed and the OTA package wouldn't install even after I uninstalled the framework, I opted for the factory image. I used the flash_all script that came with the image file and now my phone is stuck at the dancing colors.
Now I think I can probably get the phone to work again is I do a factory reset but I don't want to lose the file on the internal sdcard.
Is there anyway to backup the files on the internal storage?
I've tried ADB but it doesn't list my device either in bootloader or with the phone off or stuck at the dancing colors.
ADB does list my device in recovery mode with the "apply update from ADB" option, but I can't do a adb pull from there. It says:
error: closed.
Any idea?
OR a method to solve the soft-brick situation without wipe the files on /sdcard would work as well.
Thank you.
lgm said:
Hi everyone,
I was on 4.4.2 and wanted to update to 4.4.3. Since I installed Xposed and the OTA package wouldn't install even after I uninstalled the framework, I opted for the factory image. I used the flash_all script that came with the image file and now my phone is stuck at the dancing colors.
Now I think I can probably get the phone to work again is I do a factory reset but I don't want to lose the file on the internal sdcard.
Is there anyway to backup the files on the internal storage?
I've tried ADB but it doesn't list my device either in bootloader or with the phone off or stuck at the dancing colors.
ADB does list my device in recovery mode with the "apply update from ADB" option, but I can't do a adb pull from there. It says:
error: closed.
Any idea?
Click to expand...
Click to collapse
You have lost your internal data after using the factory images...
Primokorn said:
You have lost your internal data after using the factory images...
Click to expand...
Click to collapse
I did? The command in the flash script is
Code:
fastboot.exe -w update image-hammerhead-ktu84m.zip
and from what i can tell from the output it didn't flash userdata.img
Would that mean my files on the internal /sdcard is still in tact?
lgm said:
I did? The command in the flash script is
Code:
fastboot.exe -w update image-hammerhead-ktu84m.zip
and from what i can tell from the output it didn't flash userdata.img
Would that mean my files on the internal /sdcard is still in tact?
Click to expand...
Click to collapse
You need to remove "-w" if you didn't want it to flash your data. Everything's gone now dude..
fxdil said:
You need to remove "-w" if you didn't want it to flash your data. Everything's gone now dude..
Click to expand...
Click to collapse
I see. That solves the problem too, I guess. Thank you for clarifying.
:crying::crying:
Hi all.
I have searched the forum for solution to my problem but can't seem to find it.
When trying to flash 5.1 I get an error
After,I try to flash all .img files manually. All flash normal except system.img
I searched forums, used Wugs tool, tried on different PC's (Windows 8.1 & Windows 7) tried with different fastboot versions but no result.
Older versions flash normal(5.0.1, 4.4.4, etc..)
Any suggestions?
How much ram the PCs have?
One has 8gb ram installed,another one has 16gb
arsen4oo said:
One has 8gb ram installed,another one has 16gb
Click to expand...
Click to collapse
Strange...
Can you pack the adbs and fastboots to a zip or rar and upload it to somewhere or give me a link which adb and fastboot you use. I am going to try flash 5.1 in 30 minutes.
Here they are.
I am downloading ubuntu to try flashing from there.
*Update.
Succeed flashing on Ubuntu. Don't understand what's wrong with Windows.
arsen4oo said:
Here they are.
I am downloading ubuntu to try flashing from there.
*Update.
Succeed flashing on Ubuntu. Don't understand what's wrong with Windows.
Click to expand...
Click to collapse
Using your binaries it flashed fine, I got no errors.
My specs: Windows 8.1 Pro 8GB ram.
What is different with my setup about ram management is that since I have an SSD as drive C I moved the pagefile.sys to my HDD.
I also have Microsoft Visual C++ 2008, 2010, 2012 redistributables installed. I have no idea if that counts
I don't think problem is caused by pagefile.
But seems many people have this issue when flashing 5.1
Flashing from ubuntu is an alternative solution..
I have no idea what the issue is but here is how I got round exactly the same error message on my Windows 7 machine.
Create a new local user (with admin rights) and then reboot your machine. Log in with that user and close any applications that try to auto-start. Then try the batch file and it should now work.
I think it must be related to memory/open applications. I have loads of stuff open in the background, i.e. in the systray, with my standard login. This new user had nothing. Using this user after a reboot seems to do the trick!
Try to download the nexus image again. It might be corrupted or extract it again using 7zip. Just flashed mine a while ago using "minimal adb and fastboot" on windows 7 x64 with 2gb of RAM. Machines doesn't have anything to do with adb flashing. It's the file itself or the adb drivers.
Edit: I see you've already sorted this out via ubunta machine. Good for you.
I had the same issue last night too. I downloaded the latest nexus USB drivers and the flash completed successfully.
Had the same issue. Spent all night unbricking my phone. One of the partitions didn't flash right and i left my phone over night and it still didn't boot up. got 2 hours of sleep.
Kitkat flashed fine though.
So what i did. im using minimal adb fastboot
1) flash 4.4.4 images
2) extract ALL 5.1 image files (boot, system, etc) into the minimal adb fastboot folder C:\\program files etc etc
3) flash each item manuall
-fastboot flash bootloader bootloadername.img
-fastboot flash radio radioname.img
-then do the same with boot, radio, system, userdata, cache. (fastboot flash "partition" "name".img) so if youre flashing boot, then boot boot.img
this should boot up just fine. 2-5 minutes tops.
Manual flashing fixes it
Thanks a lot russian392! Your instructions resolved the issue for me on Windows 7 Home Premium laptop with only 4GB RAM.
So in addition to the standard flashing instructions I did the following:
1. Unzip image-hammerhead-lmy47d.zip
2. In flash-all.bat change the following line:
Code:
fastboot -w update image-hammerhead-lmy47d.zip
to:
Code:
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash system system.img
BorgKing said:
Thanks a lot russian392! Your instructions resolved the issue for me on Windows 7 Home Premium laptop with only 4GB RAM.
So in addition to the standard flashing instructions I did the following:
1. Unzip image-hammerhead-lmy47d.zip
2. In flash-all.bat change the following line:
Code:
fastboot -w update image-hammerhead-lmy47d.zip
to:
Code:
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash system system.img
Click to expand...
Click to collapse
yep you got it right :good:
I'm sure your issue will be solved if you do exactly what said in this video
Those videos helped me to flash 5.1 successfully
Sanjay Varma said:
I'm sure your issue will be solved if you do exactly what said in this video
Those videos helped me to flash 5.1 successfully
Click to expand...
Click to collapse
lol i got the idea from the same vid. Just ive flashed partitions manually before.
russian392 said:
lol i got the idea from the same vid. Just ive flashed partitions manually before.
Click to expand...
Click to collapse
lolz - though he is explaining well, I did mistakes as the commands and file names identically followed by each other
Hello good people of xda,
I recently like less then 2 weeks bought my first tablet, the NVidia shield k1 and I loved it. great gaming experience, support for my 64gb card, smooth work, good battery life but... since I updated to 6.0 all of that is gone.
My sd card can no longer by used to move apps too, formatting it to internal storage cause the tablet to "corrupt" my card.
Battery is dyeing like there is no tomorrow, tablet feel much less responsive, the list can go on and on.
Hence I'm looking for help and advice. I want to go back to 5.1 lollipop OS:
- is there anyway to make a rollback officially?
- what tools I would need (would I need to root my device or not??
- will rolling back void my warranty ?
I would appreciate the help on this matter, as since the update my tablet became a 200 dollars tray to carry drink around, and that is not cool at all (shame on you nvdia!!)
many thanks
Get your firmware version here :
https://developer.nvidia.com/shield-open-source
Then fallow this thread :
http://forum.xda-developers.com/showthread.php?t=2399737
Unlock bootloader
And instal your firmware by those commands :
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot reboot
Done!
I just rollback on K1 from 6.0 update to 5.1.1
Riddo said:
Hello good people of xda,
I recently like less then 2 weeks bought my first tablet, the NVidia shield k1 and I loved it. great gaming experience, support for my 64gb card, smooth work, good battery life but... since I updated to 6.0 all of that is gone.
My sd card can no longer by used to move apps too, formatting it to internal storage cause the tablet to "corrupt" my card.
Battery is dyeing like there is no tomorrow, tablet feel much less responsive, the list can go on and on.
Hence I'm looking for help and advice. I want to go back to 5.1 lollipop OS:
- is there anyway to make a rollback officially?
- what tools I would need (would I need to root my device or not??
- will rolling back void my warranty ?
I would appreciate the help on this matter, as since the update my tablet became a 200 dollars tray to carry drink around, and that is not cool at all (shame on you nvdia!!)
many thanks
Click to expand...
Click to collapse
You should try a factory reset first. Whatever method you use to go back to 5.1, you have to do a clean install, so, why no try a factory reset first?
Doing a factory restore doesn't reset the android version is just resets it back to fresh with android 6.0
What firmaware are you using. For k1 there is only extract-nv-recovery-image-shield-tablet-sb_na_wf-37154_590.0364
It`s correct?
perun said:
What firmaware are you using. For k1 there is only extract-nv-recovery-image-shield-tablet-sb_na_wf-37154_590.0364
It`s correct?
Click to expand...
Click to collapse
extract-nv-recovery-image-shield-tablet-sb_na_wf-37154_590.0364.sh
and what about next ??
I did a factory reset after the upgrade and it's been really smooth for me
Sent from my LG-H901 using Tapatalk
You need cygwin to unpack this fule using command bash ./name.sh
There's no userdata.img in the file and there's a blob file
OmenHTX said:
You need cygwin to unpack this fule using command bash ./name.sh
Click to expand...
Click to collapse
I have also have the nvidia k1 tablet since recently, but im not satisfied with the quality of marshmallow compared to lollipop.
I just download this file (extract-nv-recovery-image-shield-tablet-sb_na_wf-37154_590.0364.zip) after i Unpacked i got a folder with a SH file extension. I am stuck cuz nvidia says that i need to do something with comand line on ther website but I dont understand.
could you please tel me step by step if its not too mutch
abati said:
I have also have the nvidia k1 tablet since recently, but im not satisfied with the quality of marshmallow compared to lollipop.
I just download this file (extract-nv-recovery-image-shield-tablet-sb_na_wf-37154_590.0364.zip) after i Unpacked i got a folder with a SH file extension. I am stuck cuz nvidia says that i need to do something with comand line on ther website but I dont understand.
could you please tel me step by step if its not too mutch
Click to expand...
Click to collapse
Very simple way to roll back from 6.0
1) Get the software here :
https://developer.nvidia.com/shield-open-source
2) Unzip it and you will get a file_name.sh
2)Unlock your device using this guide :
http://forum.xda-developers.com/show....php?t=2399737
Unlock bootloader
3) Install cygwin to unpack the firmware you downloaded from 1)
use thiscommand bash ./File_name.sh
4) Add ADB and Fastboot path to your windows system path
5) where you unpacked the file_name.sh there should be a flash-all.bat
run it wait for it to finish and you should have a shield k1 back to factory with 5.1.1 installed
If you face any problem on the steps above you can always have a look at this tutorial for rooting your device because they differ very little from install a custom ROM.
http://nvidiashieldzone.com/index.p...tablet-root/root-shield-tablet-v2-1-lollipop/
I found with any ROM, if I factory reset than got to recovery, than default wipe, than load new ROM but start fresh with Google apps 1 at a time. Sometimes reboot after each app especially if it is a new rom or updated rom in this case being marshmallow. This has usually solved issues for me.
eraizel said:
Very simple way to roll back from 6.0
1) Get the software here :
https://developer.nvidia.com/shield-open-source
2) Unzip it and you will get a file_name.sh
2)Unlock your device using this guide :
http://forum.xda-developers.com/show....php?t=2399737
Unlock bootloader
3) Install cygwin to unpack the firmware you downloaded from 1)
use thiscommand bash ./File_name.sh
4) Add ADB and Fastboot path to your windows system path
5) where you unpacked the file_name.sh there should be a flash-all.bat
run it wait for it to finish and you should have a shield k1 back to factory with 5.1.1 installed
If you face any problem on the steps above you can always have a look at this tutorial for rooting your device because they differ very little from install a custom ROM.
http://nvidiashieldzone.com/index.p...tablet-root/root-shield-tablet-v2-1-lollipop/
Click to expand...
Click to collapse
thnx bro, I just watched someone unpacking the sh file on youtube via Linux, So thankfully i succeeded in unpacking the sh file on my kubuntu. At the moment I have a folder with 8 files that i unpacked from the original SH file.
I already installed ADB and Fastboot via the Minimal ADB/Fastboot programme, so after I unlock the bootloader via ADB/fastboot programme, do I only need to go to the folder where I exctracted the SH files and press on the flash-all.bat file ?
---------- Post added at 11:35 PM ---------- Previous post was at 10:37 PM ----------
abati said:
thnx bro, I just watched someone unpacking the sh file on youtube via Linux, So thankfully i succeeded in unpacking the sh file on my kubuntu. At the moment I have a folder with 8 files that i unpacked from the original SH file.
I already installed ADB and Fastboot via the Minimal ADB/Fastboot programme, so after I unlock the bootloader via ADB/fastboot programme, do I only need to go to the folder where I exctracted the SH files and press on the flash-all.bat file ?
Click to expand...
Click to collapse
nvm ma8 !
I managed to succesfully flash the official stock 5.1.1 as you just guided me, Your amazing big thanks !!!
abati said:
I have also have the nvidia k1 tablet since recently, but im not satisfied with the quality of marshmallow compared to lollipop.
I just download this file (extract-nv-recovery-image-shield-tablet-sb_na_wf-37154_590.0364.zip) after i Unpacked i got a folder with a SH file extension. I am stuck cuz nvidia says that i need to do something with comand line on ther website but I dont understand.
could you please tel me step by step if its not too mutch
Click to expand...
Click to collapse
right click on flash-all.bat and click on "edit" you can find those lines with fastboot then started on order. After that reboot it. It will take 15' or longer to go to instructions screen.
Sent from my SHIELD Tablet K1 using Tapatalk
Cygwin
where did you actually learn to unpack the sh file. I have cygwin installed but i have not a clue on how to use it to unpack that file. I am trying to get back to Lollipop.
abati said:
thnx bro, I just watched someone , So thankfully i succeeded in unpacking the sh file on my kubuntu. At the moment I have a folder with 8 files that i unpacked from the original SH file.
I already installed ADB and Fastboot via the Minimal ADB/Fastboot programme, so after I unlock the bootloader via ADB/fastboot programme, do I only need to go to the folder where I exctracted the SH files and press on the flash-all.bat file ?
---------- Post added at 11:35 PM ---------- Previous post was at 10:37 PM ----------
nvm ma8 !
I managed to succesfully flash the official stock 5.1.1 as you just guided me, Your amazing big thanks !!!
Click to expand...
Click to collapse
fairley said:
where did you actually learn to unpack the sh file. I have cygwin installed but i have not a clue on how to use it to unpack that file. I am trying to get back to Lollipop.
Click to expand...
Click to collapse
Try this tutorial, it helped me aswell: Sorry I cannot paste links so just google "how to geek how to use linux commands in windows with cygwin"
Guys, I followed every step in the forementioned guides and how-tos but I get always stuck with the NVIDIA/Android bootscreen (the logo). I downloaded and extracted the Linux folder and executed the flash-all.bat
Did this process several times now. Often after the flash if I go to recovery it is saying "cannot mount cache". Read something it has to do with the KitKat -> Lollipop upgrade and a cache.img is needed?
I just don't get why everybody else just don't have this problem though I did exactly the same steps... btw, this is an European / German device... but I don't think this is the problem?
Thanks
thanks for the links, but it still does not tell you how to unpack the file. Are their any other links you can give me?
Groohmsch said:
Try this tutorial, it helped me aswell: Sorry I cannot paste links so just google "how to geek how to use linux commands in windows with cygwin"
Guys, I followed every step in the forementioned guides and how-tos but I get always stuck with the NVIDIA/Android bootscreen (the logo). I downloaded and extracted the Linux folder and executed the flash-all.bat
Did this process several times now. Often after the flash if I go to recovery it is saying "cannot mount cache". Read something it has to do with the KitKat -> Lollipop upgrade and a cache.img is needed?
I just don't get why everybody else just don't have this problem though I did exactly the same steps... btw, this is an European / German device... but I don't think this is the problem?
Click to expand...
Click to collapse
I've managed to compile 5.1.1 aosp,
here is my problem, fastboot doesn't seem to recognize the command i'm typing in '-S 256M' as stated on the sony site.
If i try and flash them the normal way, for example "fastboot flash system system.img"
it doesn't flash like this, i have tried on linux and windows.
I've attached screenshots to show my problem.
Edit- I should of said first, I can flash boot, recovery and userdata the normal way, but system.img hangs. Fastboot won't let me use the command listed on the sony site when flashing any of the partitions.
My compiled system.img seems fine and I can view and extract the files so I don't think it's corrupted.
issue '-S 265M' after 'flash'..!!!
SO it should be 'fastboot flash -S 265M system system.img'
And you need to specify memory breakdown for the system image only, as it has a massive size, for the rest skip using '-S 265M'
P.S.: You certainly seem to be new at Android compilation.. I would advice you to try checking other forums first... checking out what works and what doesn't before experimenting! Just saying!
Cheers