Hi,
I'm very unsure where to put this thread as my device has no forum of its own. I have a ViewSonic ViewPad 7 tablet, but I guess this is not even a device specific question, which is why I ended up posting it here.
I have an image of the stock ROM on my tablet (system.img + boot.img), but I'm unable to extract or flash the system.img directly, which is why I need your help. I've been reading some topics regarding this and tried out different methods, but either I am doing something wrong or the image is not complete. It was created using the cat command in the shell.
If any of you should be able to extract the system.img from this zip file I would be forever grateful, as I really need to get my stock ROM back so that I'm able to have Danish locale as well as text messages.
Thank you very much in advance!
http://www.multiupload.com/6C6M83LR7P
Bump it up
Related
Dear Fellas,
After reading a bit through the pages of this Q&A forum I realized that there is no thread describing a proper method to flash a stock firmware into our "stock" tablets, I mean, without any customization or root.
Anyone please, could share his knowledge and enrich us into this subject? Yes, anyone knows how to proceed to flash a stock firmware through microSD?
Just to make things clear as possible, my wondering extends to which files add into microSD, the correct format, the correct structure to flash.
Really appreciate ideas and directions.
Cheers
Erick
Get the firmware you want from the asus webpage, extract it, find in the extracted path another zip archive and rename it to EP101_SDUPDATE Make sure you leave it a zip dont change the extension AND make sure it is on the root of the card... boot by pressing the VOL DOWN + POWER button... as soon as you see some text press within 5 sec the UP button....and wait
Hello, I'm very new to this forum so plz forgive me if I post this in the wrong place.
I recently bought a asus tf300 and flash the cmw recovery img. Since I'm unlock the bootloader, I no longer get update from ASUS website. My question is how am I manually update the blob file that I download from ASUS support website.
I have look alot threads about this issue, and I find out there are mainly three methods that can update the blob.
1. Using Asus Manual upload:
According to Asus website, they said just put the zip file in the micro sd card and the system will pop up an notification that will help u upload.
2. Using CMW to upload:
upload the blob with CMW recovery. There are some thread that tells me it will brick the device. But some people said it is ok to use CMW to upload the blob, therefore I'm a little bit confused about this method.
3. Wolf's way:
http://forum.xda-developers.com/showthread.php?t=1622628
The following is my questions:
1. what is the difference between these three method?
2. if the CMW is okay can someone tells me the right way to upload the blob. Such as using the original build.prop something like that?
3. is it ok to use the wolf's way to update the blob?
Sorry for so many questions and my poor English.
I'd use the ADB / Terminal emulator method (Wolf's way mostly)
Place on transformer, then flash the 'blob' file through the staging partition.
You'll need to reinstall CWM and reroot everytime you do this, unless you manually extract the SOS partition out of the blob file ASUS gives you with blobtools then repack it.
I have spent several weeks working on this (reading thread after thread) on modifying stock firmware and im running into a problem. I more or less want to know if what i want to do is actually possible. I have downloaded the original .tar.md5 firmware image, opened with 7zip and "extracted" the .tar file (more or less just removed the hash) and then extracted the .img files from the .tar file. I have unpacked/mounted/modified/repacked using several methods (dsixda kitchen -which havent been able to work around adding the java path since after i add the path cygwin thinks im missing clean app until i remove the path in which case i get an error saying it cant find java/ i have tried mounting using ext4_utils in ubuntu) my issue arises when i take my modified and repacked system.img file i cant get it to work either by 1. zipping it in a .tar with the other .img files and flashing with odin, 2. zipping system.img alone into a .tar and flashing with odin, 3. installing cwm/root and flashing the system.img)
More or less my question is
1. is it possible to modify the stock firmware and load it onto the tablet without rooting
2. can system.img be flashed by itself or does it need the other .img files in the same .tar
3. does the tar file require being signed before flashing even with CWM recovery and root already on the tablet?
I have used these forums for a while to find answers, but i am new to posting, i havent needed to post a question until now since i spend as much time researching as i can before bothering people with a question (i like to figure stuff out and hate to admit defeat) Thanks in advance for the help despite my noobishness
Hey everyone,
I have been looking all over for the files needed to make my TF700 brick proof. I basically need the ebtblob.bin file for my device so I can flash it via fastboot. The main site that says to get it from their download section does not appear to actually have it (http://androidroot.mobi/download/). Does anyone have the files they can send me? Just to be clear I am not asking for anyone elses device specific backups, rather the file I need to flash via fastboot to create them in the first place.
Thanks!
http://androidroot.mobi/t3_nvflash/ - scroll down to the downloads section.
Thread Closed at OP's request.
Hi folks.
I have an unusual smartphone from a Brazilian manufacturer, CCE, who have been bought for Lenovo.
This manufacturer are not exactly knowed for their support our product quality and I'm prety sure my device will not be updated or suported for any longer.
It's the SK504 and I want to try to customize the rom, build tunning apps (battery consumption sucks) and things like that. I have a good programming backgroung but not for mobile devices so I'm stepping on eggs for now.
The first thing I tried to do was get a backup from my actual rom so if I mess with something I shouldn't I would be able to come back to a working version through fastboot.
long story short, I managed to obtain through romdump 5 files; checksum.md5, config.gz, system.info.gz and system.tar
but, in the posts I been reading, it gives me the idea that I should get a boot.img, a recovery.img and a system.tar.gz
And with this I would be able to generate my own system.img through a different process.
Since I'm not being able to find what I did wrong, can anyone tell me if there are a different way to get those boot.img and recovery.img?
I tried the "adb backup -f boot.img boot" but it generates a 1kb .img file and I don't believe this is a valid boot.img.
rhodesbauer said:
Hi folks.
I have an unusual smartphone from a Brazilian manufacturer, CCE, who have been bought for Lenovo.
This manufacturer are not exactly knowed for their support our product quality and I'm prety sure my device will not be updated or suported for any longer.
It's the SK504 and I want to try to customize the rom, build tunning apps (battery consumption sucks) and things like that. I have a good programming backgroung but not for mobile devices so I'm stepping on eggs for now.
The first thing I tried to do was get a backup from my actual rom so if I mess with something I shouldn't I would be able to come back to a working version through fastboot.
long story short, I managed to obtain through romdump 5 files; checksum.md5, config.gz, system.info.gz and system.tar
but, in the posts I been reading, it gives me the idea that I should get a boot.img, a recovery.img and a system.tar.gz
And with this I would be able to generate my own system.img through a different process.
Since I'm not being able to find what I did wrong, can anyone tell me if there are a different way to get those boot.img and recovery.img?
I tried the "adb backup -f boot.img boot" but it generates a 1kb .img file and I don't believe this is a valid boot.img.
Click to expand...
Click to collapse
Instead of making a backup, have you tried to find original restore image? Usually it is a an .IMG file.
qwertyu123 said:
Instead of making a backup, have you tried to find original restore image? Usually it is a an .IMG file.
Click to expand...
Click to collapse
I used Root Explorer to look for both, recovery.img and *.img.
No result.
try this http://forum.xda-developers.com/showthread.php?t=2450045