On my TF700T I'm currently running CyanogenMod version 11-20140805-SNAPSHOT-M9-tf700t. I currently have CWM Recovery 6.0.4.4
I want to return to a stock Asus ROM from their website.
I've tried flashing WW_epad-user-10.6.1.14.10.zip with CWM but get an error...
assert failed: write_raw_image("/tmp/blob", "staging")
E:Error in /storage/sdcard1/WW_epad-user-10.6.1.14.10.zip
(Status 7)
Installation aborted.
What is it I'm doing wrong?
No thoughts?
I just tried commands from this thread, and I get error: cannot open 'blob' - yes the blob files was in the same folder as fastboot.
What cant I get this to work???
Bad download maybe?
sbdags said:
Bad download maybe?
Click to expand...
Click to collapse
I've downloaded the update 4-5 times... How big a deal is the different models? WW, TW, US??? I think it's WW, it was purchased in Australia.
Thanks for replying
When you tried to flash the zip from cwm did you unzip it first? I.e., flash the zip in the zip?
Other than that check the output of fastboot devices first.
sbdags said:
When you tried to flash the zip from cwm did you unzip it first? I.e., flash the zip in the zip?
Other than that check the output of fastboot devices first.
Click to expand...
Click to collapse
Yup I unzipped the download.
I'm running a Mac book pro, but running boot camp or OSX I still get 015d262e98340004 fastboot
typing fastboot reboot did reboot the tablet so fastboot and adb are working correctly.
FL00DY said:
I currently have CWM Recovery 6.0.4.4
assert failed: write_raw_image("/tmp/blob", "staging")
E:Error in /storage/sdcard1/WW_epad-user-10.6.1.14.10.zip
Click to expand...
Click to collapse
IIRC the "staging" target doesn't work in CWM - don't remember about TWRP. But you can edit the updater-script and replace "staging" with "/dev/block/mmcblk0p4", that should work.
FL00DY said:
I get error: cannot open 'blob' - yes the blob files was in the same folder as fastboot.
Click to expand...
Click to collapse
That's a common mistake in many of the guides - the file must be in your *current* directory.
FL00DY said:
Yup I unzipped the download.
I'm running a Mac book pro, but running boot camp or OSX I still get 015d262e98340004 fastboot
typing fastboot reboot did reboot the tablet so fastboot and adb are working correctly.
Click to expand...
Click to collapse
Hmm I've never used a mac in my life so I can't help you any further. On a windows machine or linux the last thing to check is that the blob file is in the same folder but you already said that.
Can you run an md5sum on the zip file (I know you dl'ed it 5 times) just to confirm it is not getting corrupted....
Other than that I'm out of ideas - sorry.
_that said:
IIRC the "staging" target doesn't work in CWM - don't remember about TWRP. But you can edit the updater-script and replace "staging" with "/dev/block/mmcblk0p4", that should work.
That's a common mistake in many of the guides - the file must be in your *current* directory.
Click to expand...
Click to collapse
The stock updater-script looks like this
Code:
assert(package_extract_file("blob", "/tmp/blob"), write_raw_image("/tmp/blob",
"staging"),delete("/tmp/blob"));
When you say replace "staging" - what should the bottom line look like?
This post says the blob must be in the same folder as the fastboot.exe - what do you mean when you say the file must be in your "current" directory?
sbdags said:
Hmm I've never used a mac in my life so I can't help you any further. On a windows machine or linux the last thing to check is that the blob file is in the same folder but you already said that.
Can you run an md5sum on the zip file (I know you dl'ed it 5 times) just to confirm it is not getting corrupted....
Other than that I'm out of ideas - sorry.
Click to expand...
Click to collapse
I've setup adb and fastboot to work the same way in Windows & OS X. I used to be a PC guy til I moved to graphic design... Thanks everyone for the help :good:
FL00DY said:
When you say replace "staging" - what should the bottom line look like?
Click to expand...
Click to collapse
If you don't know how to do a simple text substitution, I'd recommend you use the fastboot method.
FL00DY said:
This post says the blob must be in the same folder as the fastboot.exe - what do you mean when you say the file must be in your "current" directory?
Click to expand...
Click to collapse
That post is wrong as I already said. Files whose name you specify on a command line must be in your current working directory (of your shell), unless you specify them with a path. So you either have to use "cd" to the directory containing the blob file, or you have to specify the (relative or absolute) path to the blob file on the fastboot command line.
_that said:
If you don't know how to do a simple text substitution, I'd recommend you use the fastboot method.
Click to expand...
Click to collapse
Well I just wasn't sure if I was only replacing Staging ...
Meaning should the line look like this ...
Code:
"/dev/block/mmcblk0p4"),delete("/tmp/blob"));
That post is wrong as I already said. Files whose name you specify on a command line must be in your current working directory (of your shell), unless you specify them with a path. So you either have to use "cd" to the directory containing the blob file, or you have to specify the (relative or absolute) path to the blob file on the fastboot command line.
Click to expand...
Click to collapse
OK sure that makes sense, I just didnt want you meant by current. Thanks very much :good:
It all worked on Friday, thanks so much @_that life saver ... oh and I wasn't trying to steal your thunder in the other thread :good:
Related
Having seen this thread http://forum.xda-developers.com/showthread.php?t=512319
I thought that also linux users could need a script like that, so I wrote this simple script in python that automates the fastboot restore process.
Requirements:
File attached that contains fastboot for linux and the script
Fastboot working (you must have drivers for fastboot working)
Python installed
Procedure:
Create a folder
put script, fastboot and img files you want to restore in the folder
open a terminal
run: "cd /folderYouCreated
run "python nandrest_linux.py"
Follow on-screen instructions
For any problem use this thread
Good idea.
Could your script be tweaked so that it could be put into the 'restore' image by JF or the Dude? It would be great to be able to do a restore from the restore mode, just as one can now do the Nandroid backup.
I don't know, because it is written in python.. Maybe if someone translate it in bash script language..
well the bigger problem is, blackgin's script is doing exactly what the windows batch file is doing - calling fastboot. I just wonder why we can't use flash_image in recovery?
billc.cn said:
well the bigger problem is, blackgin's script is doing exactly what the windows batch file is doing - calling fastboot. I just wonder why we can't use flash_image in recovery?
Click to expand...
Click to collapse
Not sure why you keep saying you can't use flash_image in recovery as I stated on the other thread you CAN use flash_image. I have done it several times
korndub said:
Not sure why you keep saying you can't use flash_image in recovery as I stated on the other thread you CAN use flash_image. I have done it several times
Click to expand...
Click to collapse
I have been able to get it to work also in Recovery Mode
Well ok, but then im wondering, why JF didn't add that function, if it is so simple..
Markazeh said:
Well ok, but then im wondering, why JF didn't add that function, if it is so simple..
Click to expand...
Click to collapse
he added the console to his recovery image thus providing that ability to do this....
Blackgin, your script is so easy for noobs like me to use!
Now that I've corrected my foolish folly, its now on to installing Cyanogen's 4.1.999 ROM!
Hi all :
I try open all CGs for see the files, but i only know to open CG39 and some more..
sudo mount -o loop CG.39.smg CG39
But the others ¿¿
Some one have the answer ¿?¿?¿?
There is a Perl script which can unpack boot and recovery (CG35 & CG47) in this thread: http://forum.xda-developers.com/showthread.php?t=443994
Filipitripi said:
Hi all :
I try open all CGs for see the files, but i only know to open CG39 and some more..
sudo mount -o loop CG.39.smg CG39
But the others ¿¿
Some one have the answer ¿?¿?¿?
Click to expand...
Click to collapse
CG64.smg & CG65.smg: partition tables that you can open using fdisk/sfdisk
CG33.smg is a CDROM ISO file!
iirc one or two of them are the splash image (not 100% sure now)
Filipitripi said:
Hi all :
I try open all CGs for see the files, but i only know to open CG39 and some more..
sudo mount -o loop CG.39.smg CG39
But the others ¿¿
Some one have the answer ¿?¿?¿?
Click to expand...
Click to collapse
how to repack cg39.smg
if you have any details on windows 7 how to open repack do send me.
rachit2588 said:
how to repack cg39.smg
if you have any details on windows 7 how to open repack do send me.
Click to expand...
Click to collapse
http://sourceforge.net/projects/ext... 2.2 (Latest)/ext2explore-2.2.71.zip/download
It will allow you opening ext3 images inside Windows
^very good idea
danimagrin said:
http://sourceforge.net/projects/ext... 2.2 (Latest)/ext2explore-2.2.71.zip/download
It will allow you opening ext3 images inside Windows
Click to expand...
Click to collapse
so now i can see files on cg39.smg using ext2reader but the thing is now how to get system image from cg39.smg to system.img ??
rachit2588 said:
so now i can see files on cg39.smg using ext2reader but the thing is now how to get system image from cg39.smg to system.img ??
Click to expand...
Click to collapse
System.img to be restored with Nandroid? If yes you have to extract all files with ext2reader then use mkyaffs2image to build system.img.
danimagrin said:
System.img to be restored with Nandroid? If yes you have to extract all files with ext2reader then use mkyaffs2image to build system.img.
Click to expand...
Click to collapse
with mkyaffs2image its jus showing me a cmd windows for some less thn 1 sec and its jus goes away...please upload the version you are using...also let me know if it needs any prerequisite software to be installed.
It's because mkyaffs2image is a command line app, just like in the DOS days... To use it you should open a cmd window (type cmd at Windows menu and press enter), go to the directory right before the one you extracted files (you use cd "dirname" to enter in a directory and "cd .." to leave it. So when you are in the directory right before the one in which you've extracted files type "mkyaffs2image CG39extracteddir system.img"
danimagrin said:
It's because mkyaffs2image is a command line app, just like in the DOS days... To use it you should open a cmd window (type cmd at Windows menu and press enter), go to the directory right before the one you extracted files (you use cd "dirname" to enter in a directory and "cd .." to leave it. So when you are in the directory right before the one in which you've extracted files type "mkyaffs2image CG39extracteddir system.img"
Click to expand...
Click to collapse
oh , ok.. its working..thanks
danimagrin said:
It's because mkyaffs2image is a command line app, just like in the DOS days... To use it you should open a cmd window (type cmd at Windows menu and press enter), go to the directory right before the one you extracted files (you use cd "dirname" to enter in a directory and "cd .." to leave it. So when you are in the directory right before the one in which you've extracted files type "mkyaffs2image CG39extracteddir system.img"
Click to expand...
Click to collapse
ok last doubt...after creating system.img can it be restored via custom recovery..??
how to add md5 check sums for that so that custom recovery can identify as proper nandorid..!!??
rachit2588 said:
oh , ok.. its working..thanks
Click to expand...
Click to collapse
You welcome!
Sure you can use it with nandroid, you must download md5sum.exe, place it together with mkyaffs2image, after you used mkyaffs2image then type "md5sum system.img" and it will generate checksum. Create a file called "nandroid.md5" and paste what md5sum returned. You can open a nandroid.md5 file of another backup and you'll understand better how it's done..
excellent..i got it
@danimagrin help me how to add root files if our cg39 image is unrooted..??
ie how to manually add root files from some rooted cg39 image to some non rooted original image..which files and folders are required to add/replace..?? ne thoughts..
rachit2588 said:
@danimagrin help me how to add root files if our cg39 image is unrooted..??
ie how to manually add root files from some rooted cg39 image to some non rooted original image..which files and folders are required to add/replace..?? ne thoughts..
Click to expand...
Click to collapse
I know how to do it on Linux, because you've to run chmod and chown to set su and Superuser.apk permissions. I'll see if it's possible to do it inside Windows and I'll answer you asap.
Where did you get mkyaffs2image for Windows? Are you running it with -f flag or not? Have you already made an image and restored it and did it really work? I'm afraid if will not work because of the same problem above...
danimagrin said:
I know how to do it on Linux, because you've to run chmod and chown to set su and Superuser.apk permissions. I'll see if it's possible to do it inside Windows and I'll answer you asap.
Where did you get mkyaffs2image for Windows? Are you running it with -f flag or not? Have you already made an image and restored it and did it really work? I'm afraid if will not work because of the same problem above...
Click to expand...
Click to collapse
yes i have made an system.img with md5 nandroid check sum...but still not restored with CWM Recovery...yeah mkyaffs2image works on windows...find out in the attached IMG depacker
rachit2588 said:
yes i have made an system.img with md5 nandroid check sum...but still not restored with CWM Recovery...yeah mkyaffs2image works on windows...find out in the attached IMG depacker
Click to expand...
Click to collapse
I'll test it as soon as I get home and then I tell you!
So I just rooted via Pete's instructions, I'm on CWM 3.1.0.1 or something but I see some people are on 4.x.x.x what should I be on? Rom manager only lists the 3.1.0.1 thanks in advance.
DigitalDementia said:
So I just rooted via Pete's instructions, I'm on CWM 3.1.0.1 or something but I see some people are on 4.x.x.x what should I be on? Rom manager only lists the 3.1.0.1 thanks in advance.
Click to expand...
Click to collapse
you should upgrade to the latest, 4.x.x.x.
Im not really finding a link to that CWM version, if I flash one of the kernels will it give me the newest recovery? I know that's how people did it on the fascinate.
Going into the nexus s developement thread and look for cwm 4.x.x.x section posted by j_r0dd. The latest should be 4.0.1.4. Grab that .img file and put it into your C:\AndroidSDK\tools folder or wherever you have it located.
1. Open cmd,
cd C:\whateveryounamedit\tools
2. Boot into bootloader
3. Plug in usb and type: fastboot devices, your devices # should pop up, sometimes if its blank its still connected.
4. Type: fastboot flash recovery nameofrecovery.img
I would give a link, but im on the app.
Sorry.
EDIT: oh and be sure you grab the one for ns4g devices.
Wow thanks for being so helpful! I'll do that ASAP.
Your welcome.
kijp15 said:
Going into the nexus s developement thread and look for cwm 4.x.x.x section posted by j_r0dd. The latest should be 4.0.1.4. Grab that .img file and put it into your C:\AndroidSDK\tools folder or wherever you have it located.
1. Open cmd,
cd C:\whateveryounamedit\tools
2. Boot into bootloader
3. Plug in usb and type: fastboot devices, your devices # should pop up, sometimes if its blank its still connected.
4. Type: fastboot flash recovery nameofrecovery.img
I would give a link, but im on the app.
Sorry.
EDIT: oh and be sure you grab the one for ns4g devices.
Click to expand...
Click to collapse
adb doesn't seem to recognize fastboot as a command? I'm in the bootloader though.
Anyone have a zip of the cwm 4.x.x.x recovery?
Did you install android sdk on your computer? If not, you should do that before you proceed.
EDIT: or did you put adb to your path on your computer
I'm on W7 so I just went to platform-tools and typed cmd in the address bar. However fastboot isn't in platform-tools?
So I went to tools but got another error trying to flash.
Sorry for all the questions I've never had to use fastboot.
Or just put the .img file on the root of your sdcard.
Open terminal
type flash_image recovery /sdcard/nameofrecovery.img
Download android terminal
su
flash_image recovery /sdcard/nameofrecovery.img
Hit enter, it should now read the .img file
After that type reboot recovery to check it. Hope this helps.
kijp15 said:
Download android terminal
su
flash_image recovery /sdcard/nameofrecovery.img
Click to expand...
Click to collapse
If it says no image found?
DigitalDementia said:
If it says no image found?
Click to expand...
Click to collapse
Are you doing correctly?
I've done it a tons of time and it never gave me that msg.
When downloaded it, did it say .txt at the end, if it did change it from
.txt to .img.
And try again.
Positive. I renamed it cwm4.img for ease of use and I type:
su
flash_image recovery /sdcard/cwm4.img
Then it says flash_image: not found
kijp15 said:
When downloaded it, did it say .txt at the end, if it did change it from
.txt to .img.
And try again.
Click to expand...
Click to collapse
Still an image file.
Is your img file in any folders?
If it is your doing something wrong that I don't know about. Ha. If it is take out and out it on the root of your sdcard.
I've just flashed a img wit this same exact process and it went threw.
kijp15 said:
Is your img file in any folders?
If it is your doing something wrong that I don't know about. Ha. If it is take out and out it on the root of your sdcard.
I've just flashed a img wit this same exact process and it went threw.
Click to expand...
Click to collapse
Ugh... frustrating! It's not in a folder, it's right on the root mocking me. Okay just so I know I'm doing it right I do it like this:
su
flash_image recovery /sdcard/cwm4.img
Right? With the spaces between recovery and /sdcard/ ?
Hmmm... that is right.. is your terminal a black or blue background?
If its black your have the wrong terminal.
This guide is to root Remix OS for PC
You will need Ubuntu for Rooting (You can download and run it in live CD)
If you are experienced with linux systems don't read whats written in bracket
1. Download and Extract RemixRoot.zip
2. Copy system.img from your pendrive or hdd wherever you have installed Remix Os to this folder (ie RemixRoot folder it should be alongside Readme.txt)
3. Open Terminal (Ctrl+Alt+T)
4. Type
Code:
sudo -i
5. Enter your password (If you are running in live cd then no password)
6. Change directory to RootRemix folder (Goto tmp folder, right click and goto properties and copy location, this is your <dir> replace it in command below )
Code:
cd <dir>
7. If you did it right next line of terminal will end with RemixRoot# followed by blinking cursor
8. Now run rootx.sh script by typing
Code:
sh rootx.sh
9. If everything goes right there wont be any error message and you will get a root.img in your RemixRoot folder
10. Rename it to system.img and copy to your pendrive/hdd replacing previous system.img
11. Reboot and go to RemixOS and update SuperSU binaries
12. That's it! you are now rooted
Thanks to Chainfire & hackarchive
I tried it but i got no system.img, i got r/w access to system (choosen by install) so i tried to symlink it to my system directory and commented out all image mounted related things from script and then tried it.
but after that i cannot boot android anymore, i think the problem is app_process linking to daemonsu, since i set back to original it boots like normal but no superuser access. SuperSU said theres is no superuser installed.
Any suggestion?
Silly question but will I lose root access if I update to the newest version by flashing the new image over the top?
Yes a silly question.... Deserves a silly answer. It will still be underneath, but good luck trying to retrace it!
any other method for rooting, without using ubuntu?
#tested with ubuntu live, and it works like a charms. Thank you..
Sent from my C46G using XDA Premium 4 mobile app
ninharp said:
I tried it but i got no system.img, i got r/w access to system (choosen by install) so i tried to symlink it to my system directory and commented out all image mounted related things from script and then tried it.
but after that i cannot boot android anymore, i think the problem is app_process linking to daemonsu, since i set back to original it boots like normal but no superuser access. SuperSU said theres is no superuser installed.
Any suggestion?
Click to expand...
Click to collapse
same problem here.
Hope same other method can solved
I modified the original script to work with the system folder installation and i removed all app_processX dependend things from script (dunno if it affects the root in any way, cannot find any issue by now) Read the Readme.txt for further installation instructions. The link you find on the reddit sub that GoPal has posted! I cannot post links right now.
Try this
kretex said:
Hope same other method can solved
Click to expand...
Click to collapse
ninharp said:
I tried it but i got no system.img, i got r/w access to system (choosen by install) so i tried to symlink it to my system directory and commented out all image mounted related things from script and then tried it.
but after that i cannot boot android anymore, i think the problem is app_process linking to daemonsu, since i set back to original it boots like normal but no superuser access. SuperSU said theres is no superuser installed.
Any suggestion?
Click to expand...
Click to collapse
You will get root.img file you will have to rename it to system.img
masdeco said:
same problem here.
Click to expand...
Click to collapse
Me too [emoji25]
Envoyé de mon E5333 en utilisant Tapatalk
I've just installed RemixOS 2.0 onto a partition on my Lenovo X200T. I followed the instructions and all was good until I tried to run SuperSU. When it tried to update via the normal method the install failed and asked for a reboot. Any suggestions.
ninharp said:
I modified the original script to work with the system folder installation and i removed all app_processX dependend things from script (dunno if it affects the root in any way, cannot find any issue by now) Read the Readme.txt for further installation instructions. The link you find on the reddit sub that GoPal has posted! I cannot post links right now.
Try this
Click to expand...
Click to collapse
the answer is replace the system folder. this is my methode :
1. copy the system img from the extracted remix iso to somewhere
2. then run the script
3. unpack the system img that already rooted and copy all the content to the system folder of the remix (replace)
4. done. Remix os rooted.
Guys, I installed Remix to ext4 partition (in order to use all free space), so there's no "system.img" on it (but there's "system" folder). How to modify the script or to root Remix other way?
masdeco, thanks for the idea! How do you unpack img file, btw?
4ezahernya said:
Guys, I installed Remix to ext4 partition (in order to use all free space), so there's no "system.img" on it (but there's "system" folder). How to modify the script or to root Remix other way?
masdeco, thanks for the idea! How do you unpack img file, btw?
Click to expand...
Click to collapse
after root the system img then mount it, copy all the content to the system folder of your remix.
since I am a linux user so I use this command :
mount -o loop system.img tmp
this is so cool cool
Works Lenovo Yoga 2 11
Installed to a partition on my HD:
Downloaded RemixOS iso
extracted contents of iso
created temp, data and system folders
ran this tool to root the system.img (now root.img)
renamed root.img back to system.img
mounted system.img to temp folder
copied contents of temp folder to system folder
added entry in grub
now I am triple booting Windows, Linux and RemixOS 2.0 Android with ROOT
Thank You!!!
here is a xdelta3 for patching system.img for those using Remix OS 2 from a USB stick and run windows
GizmoTheGreen said:
here is a xdelta3 for patching system.img for those using Remix OS 2 from a USB stick and run windows
Click to expand...
Click to collapse
can you please explain its usage?
the_poolee said:
can you please explain its usage?
Click to expand...
Click to collapse
me too!
Please
the_poolee said:
can you please explain its usage?
Click to expand...
Click to collapse
dariett said:
me too!
Please
Click to expand...
Click to collapse
it shouldn't be too hard to figure out, put the files in your folder of choice with the system.img from your usb stick, run the batfile. it should create a file named rooted system image, now just replace system.img on your usb stick with that and run...
ofcourse I am assuming your system.img is identical to the one I had, which it should be if it was the 2.0 dev preview which is the only thing you can get today, right?
I try to flash a patched boot.img and it says can't load boot.img did something change?
Virus1x said:
I try to flash a patched boot.img and it says can't load boot.img did something change?
Click to expand...
Click to collapse
What is the exact syntax of your command, and the exact error message? Cut/paste or screenshot would be the best way for you to provide the accurate info.
Usually, the error message that fastboot can't load a file, means the boot.img file is simply not in the right place on your computer (needs to be in the same folder where fastboot.exe is located); or you may have just typed the name of the file wrong (so again, it is looking for a file that is technically not there). But I'd like to see the exact input/output to get a better indication of what went wrong.