hi.sorry for my language. En Not Native language.I have problem with formatting a BCT partition for my tablet viewsonic viewpad 10s.please help me.
I have a question : can do forrmat BCT drive with program Bab sector from Xda developers????
thanks a lot
:crying::crying::crying::crying::crying:
error download link
alivaiper said:
hi.sorry for my language. En Not Native language.I have problem with formatting a BCT partition for my tablet viewsonic viewpad 10s.please help me.
I have a question : can do forrmat BCT drive with program Bab sector from Xda developers????
thanks a lot
:crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
error download link : alivaiper.persiangig.com/Untitled.jpg
Are you using the correct .bct, flash.cfg and nvflash for your tablet?
rajeevvp said:
Are you using the correct .bct, flash.cfg and nvflash for your tablet?
Click to expand...
Click to collapse
nvflash = yes
correct.bct & flash.cfg =no
what is correct.bct & flash.cfg ?
alivaiper said:
what is correct.bct & flash.cfg ?
Click to expand...
Click to collapse
No idea--sorry. Try:
1. Looking inside the Stock ROM files (update or install) for the correct files.
2. Get those files from a user with a working viewpad 10s using the ``nvflash --read'' command.
3. Also make sure that you use the correct bootloader.bin and other image files for your tablet. Don't use the gTablet images with nvflash.
rajeevvp said:
No idea--sorry. Try:
1. Looking inside the stock ROM files (update or install) for the correct files.
2. Get those files from a user with a working viewpad 10s using the ``nvflash --read'' command.
3. Also make sure that you use the correct bootloader.bin and other image files for your tablet. Don't use the gTablet images with nvflash.
Click to expand...
Click to collapse
first time i tried to install this Rom : ViewPad_10s_v1.09_firmware_update
But that error came up! : Formatting Partition 2 BCT Please Wait .... FAILED
after that i tried every roms i could install on viewpad 10s and every single time i end up with the same error!
i dont now what to do?!
how can i erase and format the Nand flash? and if i do this, my viewpad will full break?
alivaiper said:
first time i tried to install this Rom : ViewPad_10s_v1.09_firmware_update
But that error came up! : Formatting Partition 2 BCT Please Wait .... FAILED
Click to expand...
Click to collapse
Upload that firmware update file somewhere, then post a link to it so that I can inspect it.
rajeevvp said:
Upload that firmware update file somewhere, then post a link to it so that I can inspect it.
Click to expand...
Click to collapse
www
.
mediafire
.
com
/?pst6qq8zufcyb7f
tnx.
sorry
i cannot post a link so i split it
alivaiper said:
www.mediafire.com/?pst6qq8zufcyb7f
i cannot post a link so i split it
Click to expand...
Click to collapse
1. Is that the official viewpad 10s firmware update from ViewSonic?
2. I don't have a Windows system, so a .exe file is no use to me. Run the .exe file if it's a self-extracting executable, then upload the files extracted somewhere.
rajeevvp said:
1. Is that the official viewpad 10s firmware update from ViewSonic?
2. I don't have a Windows system, so a .exe file is no use to me. Run the .exe file if it's a self-extracting executable, then upload the files extracted somewhere.
Click to expand...
Click to collapse
1- yes, this is a official firmware for viewsonic 10s
2- my internet speed is very low! (32 KB per sec!!!!) so it will be a long time until i uplode thease files!!!
i extract the exe file with winrar and thease files extracted :
Name Size
system.img 133 MB
recovery.img 4.33 MB
boot.img 4.11 MB
userdata.img 1.45 MB
bootloader.bin 919 KB
nvflash.exe 151 KB
nvhost.exe 97.5 KB
libnvtestio.dll 94.5 KB
libnvos.dll 92.0 KB
libnvapputil.dll 78.5 KB
libnvflash.dll 76.0 KB
buildbct.exe 67.0 KB
libnv3p.dll 50.5 KB
libnvaes_ref.dll 44.0 KB
libnvdioconverter.dll 44.0 KB
libnvusbhost.dll 43.5 KB
libnvboothost.dll 42.5 KB
flash.bct 3.98 KB
flash.cfg 2.03 KB
lvds.bat 183 bytes
H5PS1G83EFR-S6C_V24_0625.bct 3.98 KB
is this what u need?
Try the latest firmware update from this page:
http://ap.viewsonic.com/in/kbase/article.php?id=478
Follow the installation instructions in the pdf file on the same page.
Related
Can anyone help me where can I download S5830XWKPN full package file?
On samfirmware site they only provide one-package file.
Thanks alot!
that one package already include every files needed to fully flash your ace.
if you/re not sure, open that one package tar file using winrar, or 7zip. if you see 9 files total, then you're good
setya5785 said:
that one package already include every files needed to fully flash your ace.
if you/re not sure, open that one package tar file using winrar, or 7zip. if you see 9 files total, then you're good
Click to expand...
Click to collapse
I already did that, but I noticed those files are different compare to usual full package file like in KPH.
those are the individual file.
if you extract all 4 full package files using winrar, you'll get the same 9 individual files
setya5785 said:
those are the individual file.
if you extract all 4 full package files using winrar, you'll get the same 9 individual files
Click to expand...
Click to collapse
I'm confused. for full package, extension file names are ".md5".
But on a one package file some files don't have extension name.
What could be wrong?
those full package are also tar archieve. the same 9 files archieved seperately.
lol, you ectract onepackage, pack into 4 seperate archive and vise-versa
it doesn't matter as long as you have all 9 files needed. ODIN will extract all files and flash individual files.
for those who flash onepackage and failed, mostly due to incomplete onepackage.
You sure it'll work all right? You won't be able to flash the KPN 1 package from say 2.2 right?
setya5785 said:
those full package are also tar archieve. the same 9 files archieved seperately.
lol, you ectract onepackage, pack into 4 seperate archive and vise-versa
it doesn't matter as long as you have all 9 files needed. ODIN will extract all files and flash individual files.
for those who flash onepackage and failed, mostly due to incomplete onepackage.
Click to expand...
Click to collapse
Define an incomplete onepackage and a complete onepackage .
consegregate said:
You sure it'll work all right? You won't be able to flash the KPN 1 package from say 2.2 right?
Click to expand...
Click to collapse
as long as you use a full one package file. it's work.
all you need is this files :
amss
arm11boot
boot.img
data.rfs (optional)
csc.rfs
mibib
oemsbl
qcsbl
recovery.img
system.rfs
either you get it from a single archive (onepackage), or 4 archieves (seperated into appboot, code, csc and modem). it doesn't matter.
whatever you give ODIN, it will unpack the archieve to get all those files before actually flashing it into the device.
if you get 4 archieve version -like i said, you can actually extract a full onepackage, and pack it again into 4 archieve-
APBOOT tar.md5 should include :
arm11boot
mibib
oemsbl
qcsbl
CODE tar.md5 should include :
boot.img
data.rfs (optional)
recovery.img
system.rfs
CSC tar.md5 should include :
csc.rfs
MODEM tar.md5 should include :
amss
and yea, i did flash my stock froyo (2.2.1 DXKC1) directly into XWKPN.
EmoBoiix3 said:
Define an incomplete onepackage and a complete onepackage .
Click to expand...
Click to collapse
see above
setya5785 said:
as long as you use a full one package file. it's work.
all you need is this files :
amss
arm11boot
boot.img
data.rfs (optional)
csc.rfs
mibib
oemsbl
qcsbl
recovery.img
system.rfs
either you get it from a single archive (onepackage), or 4 archieves (seperated into appboot, code, csc and modem). it doesn't matter.
whatever you give ODIN, it will unpack the archieve to get all those files before actually flashing it into the device.
if you get 4 archieve version -like i said, you can actually extract a full onepackage, and pack it again into 4 archieve-
APBOOT tar.md5 should include :
arm11boot
mibib
oemsbl
qcsbl
CODE tar.md5 should include :
boot.img
data.rfs (optional)
recovery.img
system.rfs
CSC tar.md5 should include :
csc.rfs
MODEM tar.md5 should include :
amss
and yea, i did flash my stock froyo (2.2.1 DXKC1) directly into XWKPN.
see above
Click to expand...
Click to collapse
I see.....you win .
setya5785 said:
as long as you use a full one package file. it's work.
all you need is this files :
amss
arm11boot
boot.img
data.rfs (optional)
csc.rfs
mibib
oemsbl
qcsbl
recovery.img
system.rfs
either you get it from a single archive (onepackage), or 4 archieves (seperated into appboot, code, csc and modem). it doesn't matter.
whatever you give ODIN, it will unpack the archieve to get all those files before actually flashing it into the device.
if you get 4 archieve version -like i said, you can actually extract a full onepackage, and pack it again into 4 archieve-
APBOOT tar.md5 should include :
arm11boot
mibib
oemsbl
qcsbl
CODE tar.md5 should include :
boot.img
data.rfs (optional)
recovery.img
system.rfs
CSC tar.md5 should include :
csc.rfs
MODEM tar.md5 should include :
amss
and yea, i did flash my stock froyo (2.2.1 DXKC1) directly into XWKPN.
see above
Click to expand...
Click to collapse
Hello setya5785. nice explanation!
Just a few questions.
1. Some other mods here said that you can't directly flash stock froyo (2.2.1 DXKC1) to KPN using one package file. they said, you must flash with any 2.3.3 with full package before flash KPN with one package file. is this true??
2. What do you recommend more, flash KPN with one package file? or extract files first and archive them with tar.md5 then flash??
Hope to here from you, thanks!
EmoBoiix3 said:
I see.....you win .
Click to expand...
Click to collapse
LOL, there's no win or lose
droidtwoseven said:
Hello setya5785. nice explanation!
Just a few questions.
1. Some other mods here said that you can't directly flash stock froyo (2.2.1 DXKC1) to KPN using one package file. they said, you must flash with any 2.3.3 with full package before flash KPN with one package file. is this true??
2. What do you recommend more, flash KPN with one package file? or extract files first and archive them with tar.md5 then flash??
Hope to here from you, thanks!
Click to expand...
Click to collapse
1. it depends. if you can get a complete onepackage, it'll be safe. i flash from DXKC1 directly to XWKPN using onepackage file that include all files (well minus data.rfs, but not that it matter, as long as you wipe before flashing).
so basicly, check your file or where you get your file from.
i use this onepackage - http://www.multiupload.com/Y643XGWMMN (password: sampro.pl)
most mod advice againts onepackage probably because, some uploader / site only give backup files from PDA files like system.rfs, boot.img, and some other (you can only get this from your phone using normal backup).
when flashing only ginger's PDA files into froyo. you'll get stuck at boot. this is because froyo's bootloader can't boot ginger (and vide versa)
so check your files first.
4 speerate archieve can be easier to identify. but onepackgae file, you need to extract or open teh archieve in some archieving app (like winrar or 8zip)
2. if you already got onepackage file with all needed files. just use it.
setya5785 said:
as long as you use a full one package file. it's work.
all you need is this files :
amss
arm11boot
boot.img
data.rfs (optional)
csc.rfs
mibib
oemsbl
qcsbl
recovery.img
system.rfs
either you get it from a single archive (onepackage), or 4 archieves (seperated into appboot, code, csc and modem). it doesn't matter.
whatever you give ODIN, it will unpack the archieve to get all those files before actually flashing it into the device.
if you get 4 archieve version -like i said, you can actually extract a full onepackage, and pack it again into 4 archieve-
APBOOT tar.md5 should include :
arm11boot
mibib
oemsbl
qcsbl
CODE tar.md5 should include :
boot.img
data.rfs (optional)
recovery.img
system.rfs
CSC tar.md5 should include :
csc.rfs
MODEM tar.md5 should include :
amss
and yea, i did flash my stock froyo (2.2.1 DXKC1) directly into XWKPN.
see above
Click to expand...
Click to collapse
Hello setya5785. Nice explanation.
Just a few more questions.
1. Some mods and threads here said the you can't directly flash stock froyo (2.2.1 DXKC1) to KPN using one package file. They said that you must first flash with any 2.3.3 using full package file before you can flash KPN using one package file. Is this true??
2. About flashing froyo 2.2.1 DXKC1 to KPN what do you recommend more, flashing with one package file? or extracting one package file then archive certain files to .tar.md5 then flash??
Hope to hear form you! Thanks!
double post ? see reply above
Excellent explanation. Mind making a thread to include these details? Will clear up the many questions about flashing Samsung firmwares.
setya5785 said:
double post ? see reply above
Click to expand...
Click to collapse
Sorry for the double post. I thought I didn't post it at first. Thanks for the explanation men. I think I'm now ready to update my Ace.
Anyway, can you tell me more about this "when flashing only ginger's PDA files into froyo. you'll get stuck at boot. this is because froyo's bootloader can't boot ginger (and vide versa)". You said I will stock on boot? What will I do when I encounter this?
i could, but it'll just be a copy and paste and redundant from this one.
might as well refer to this post/thread
droidtwoseven said:
Sorry for the double post. I thought I didn't post it at first. Thanks for the explanation men. I think I'm now ready to update my Ace.
Anyway, can you tell me more about this "when flashing only ginger's PDA files into froyo. you'll get stuck at boot. this is because froyo's bootloader can't boot ginger (and vide versa)". You said I will stock on boot? What will I do when I encounter this?
Click to expand...
Click to collapse
you'll mostly gonna get stuck at galaxy ace GT-5830 samsung boot screen.
when you do encounter this. just turn off your phone.
enter download mode, and flash another rom (back to froyo stock) or another ginger using another source.
setya5785 said:
you'll mostly gonna get stuck at galaxy ace GT-5830 samsung boot screen.
when you do encounter this. just turn off your phone.
enter download mode, and flash another rom (back to froyo stock) or another ginger using another source.
Click to expand...
Click to collapse
What could be the reason for this? The file/s??
You just said you successfully flash your stock froyo to KPN using one package file, can I ask you the files you used?
I can't download the file from the link you'd given
droidtwoseven said:
What could be the reason for this? The file/s??
You just said you successfully flash your stock froyo to KPN using one package file, can I ask you the files you used?
I can't download the file from the link you'd given
Click to expand...
Click to collapse
most incomplete (or should i say update/version) or onepackage only include pds files backup. there's no bootloader, modem/phone/baseband.
so if you flash this ginger's update into froyo, your phone still using froyo's bootloader and baseband. this bootloader can't load ginger's system.
this is why most will advice to flash any full package ginger, to get the bootloader.
but if you already have the full onepackage, it's good to go.
i use XWKPN from the on i linked at post #12
there's 9 mirror from that multiupload link.
Hai all i am working on a working ics rom for the Veolo player and clones.
Now i downloaded a rom from Himedia Q5 and wanted to extract the system.img logo.img and boot.img files to see whats inside
I tried all tools available on this forum (Unjaffs2 etc.) but no luck so far
The firmware is available here https://mega.co.nz/#!KMkHVTCR!XSLG0gNa-z20jDqYNQbNMy89qQZC1WIQpy5SmUGAcbk
Can some one try to extract this img files for me and explain to me how they did it ?
I can,t run it n the veolo beause the veolo has 512mb system memory and the himedia q5 1gb.So i can't make a system dump.
I want to modify the rom to be used on a veolo thats the idea.
I thing these files are packed some how ???
Hope you can help me guys thnx
system.img is an yaffs2 file system: 4K 24bits/1K and contains root filesystem as well.
boot.img is NOT an Android boot image, but an uImage kernel.
bootargs.img contains kernel boot arguments in text.
Quite not-the-way-we-do-it-in-Android, but manageable.
yeah i know the bootimg contains the kernel etc and the system.img is a yaffs2 file system i also know
Buit still the problem is that i can't extract the root file system etc in it all tools i could find gave a error ?
Any idea how i can extract it ? since the common tools seems not to work ?
Thx for the info btw
Anyone who can help me unpack the system.img and the userdata.img ???????????????????
Unpack system.img Q5 and MMB-422 or Veolo aka Godbox
kraakie256 said:
Anyone who can help me unpack the system.img and the userdata.img ???????????????????
Click to expand...
Click to collapse
Yeah, no problem. I own a MMB-422, a Veolo look-a-like. I have an ICS firmware for it, so it should also work on your Veolo. The problem is that you need an RS232 <-> UART or USB <-> UART converter to modify the systems partition and upload the new ICS firmware. I build one myself. I posted the howto on meteorit.wikia.com/wiki/MMB-422.HDTV/Software-Updates
I managed to decompile the system.img and userdata.img from the Q5 with yaffs2utils. I believe I used the following command ./unyaffs2 -p 4096 -s 200
To unpack the MMB-422 firmware (8K chunks and 366B spare) I also use unyaffs2 but with -p 8094 and -s 366
But then......I can pack the system dir again to an system.img with mkyaffs2img but it generates an image with a complete different layout and it cannot be used with our "Godbox".
Maybe we can coöperate? Do you live in The Netherlands? I do......Do you have C++ skills?
bobbes said:
Yeah, no problem. I own a MMB-422, a Veolo look-a-like. I have an ICS firmware for it, so it should also work on your Veolo. The problem is that you need an RS232 <-> UART or USB <-> UART converter to modify the systems partition and upload the new ICS firmware. I build one myself. I posted the howto on meteorit.wikia.com/wiki/MMB-422.HDTV/Software-Updates
I managed to decompile the system.img and userdata.img from the Q5 with yaffs2utils. I believe I used the following command ./unyaffs2 -p 4096 -s 200
To unpack the MMB-422 firmware (8K chunks and 366B spare) I also use unyaffs2 but with -p 8094 and -s 366
But then......I can pack the system dir again to an system.img with mkyaffs2img but it generates an image with a complete different layout and it cannot be used with our "Godbox".
Maybe we can coöperate? Do you live in The Netherlands? I do......Do you have C++ skills?
Click to expand...
Click to collapse
Well i managed to unpack it etc but my Veolo died Flash mem full of bad blocks grrrr
I amw aiting for a replacement
Btw The firmwares MMB-422 choose -p8192 -s368
And for the Himedia -p4096 -s200 and you can repack it with -p8192 -s368 but it seems that somehow the fw crashes when you flaash it
I think it's a library in the lib folder who causes the crash
Can't continue at the moment since my veolo died
And no i dont have C++ Skills i understand it a bit
Btw The firmwares MMB-422 choose -p8192 -s368
Click to expand...
Click to collapse
That's true. I made an mistake.
And for the Himedia -p4096 -s200 and you can repack it with -p8192 -s368 but it seems that somehow the fw crashes when you flaash it
Click to expand...
Click to collapse
The (re)compiled image has a complete different structure so the mkyaffs2img program has to be rewritten to suite our needs. It wont flash it in bootloader (u_boot aka fastboot) mode.
To bad that your Veolo's NAND has died! Are you sure? Did you try a complete erase of the whole NAND and then repartition the NAND again? Do you use UART?
bobbes said:
That's true. I made an mistake.
The (re)compiled image has a complete different structure so the mkyaffs2img program has to be rewritten to suite our needs. It wont flash it in bootloader (u_boot aka fastboot) mode.
To bad that your Veolo's NAND has died! Are you sure? Did you try a complete erase of the whole NAND and then repartition the NAND again? Do you use UART?
Click to expand...
Click to collapse
yeah it's dead i used a uart\
When you recomplile remove the first part of the header with a hexeditor
Look for Yffsv10 or something like that
And remove all crap before that. other wise fastboot won't regonize it as a yaffs2 image
I Backup-ed my Acer tab b1-A71 using android system recovery - Just like CWM.
The file name ends with .Backup, and i wanted to extract some files from it..
How to Extract data from .Backup file ? - Created with android system recovery
looking for the same
reena0307 said:
I Backup-ed my Acer tab b1-A71 using android system recovery - Just like CWM.
The file name ends with .Backup, and i wanted to extract some files from it..
How to Extract data from .Backup file ? - Created with android system recovery
Click to expand...
Click to collapse
me too looking for the same thing ..how to extract from or decompile .backup file which we get thru recovery.
hi loverboyritesh :: i and you are in same position.. but some advaaanced users are here that we are telling rumors and lies.. dont worry bro.. even i'm trying to get solution.. will tel you after geeing one.. Still no one can tell me hoe to extract .BACKUP file..
same
i am looking for how to reinstall .backup myself so i can have my original rom install.
but i have notice my .backup is 700+mb while custom rom is 200+mb
do you know how to?
reena0307 said:
I Backup-ed my Acer tab b1-A71 using android system recovery - Just like CWM.
The file name ends with .Backup, and i wanted to extract some files from it..
How to Extract data from .Backup file ? - Created with android system recovery
Click to expand...
Click to collapse
same here. dunno how to open and extract the files from a .backup file. hoping you know already
siiingkeeet said:
same here. dunno how to open and extract the files from a .backup file. hoping you know already
Click to expand...
Click to collapse
Nope.. Still i'm having that file but no one knew
reena0307 said:
Nope.. Still i'm having that file but no one knew
Click to expand...
Click to collapse
been searching for 5 days now :<
not a single answer found on google and forums
cant even post a new thread yet. just joined
hope someone will drop by this thread
still no solution?
got same problem here
Got a bootloop issue with an ASUS MeMo Pad 7 HD and I've booted in recovery <3e> to make a backup.
I've got a userdata_YYYYMMDD_HHMMSS.backup. I tried opening it with a bunch of tools like unyaffs, abe (Android backup extractor), going live on the file using linux tools (open as 7zip, zip, rar, tar, tar.gz, gz, bz2 , mount as iso, ext4 and so on....)
Still no luck :-/
Only clue is that the file seems compressed. During the backup under recovery, it told me 3600MB to backup and the file userdata_xxxxxxxx_xxxxxx.backup show only 2.61GB
I did this backup 3 time to ensure there were no corruption during the write process from the pad and did again the same "tests" to open the file...Not better.
If any dev' have any clue of the file format, I'd be glad to help
It doesn't seem to be a valid unix img file. Tried mounting it to no avail. When it's restored by the recovery it also extracts the individual files because i fails on one in my case and stops the entire restore... I tried unzipping it, changed extension to ,jar, .tar, .zip, etc., none of them are recognised...amazing for a standard android feature to find so little info about it
Any solution?
I called Alcatel's technical service today and they told me that you can use the backup file only from the phone. Mine gives me the following error when I try to restore it: Error Magic header
If anyone knows how to unpack the backup file I would be more than grateful.
It's a 512 byte header in front of a "tar.gz"
hexdump -C userdata_xxxxxxxx_yyyyyy.backup | lessshowed the magical zip header "1f8b0800 00000000" at offset 0x200
So, skipping 512 bytes, the rest can be gunzip | tar
dd if=userdata_xxxxxxxx_yyyyyy.backup bs=512 skip=1 | gunzip -c | tar xv
Sir ektoric what d u mean on ur post?
Sorry cant understand it..
Can u please d a step by step procedure? Please...pls...plss
Thanks in advance...
Steps?
@ektoric sir im a noob in this... Can u show a step by step procedure?
@killen00 sorry, I assume you have a linux machine (or have access to one). The command is actually all there is to it.
Code:
dd if=userdata_xxxxxxxx_yyyyyy.backup bs=512 skip=1 | gunzip -c | tar xv
If you don't have a linux machine available, might I suggest one of the many distros of your choice, most of which have LiveCDs which you can run without installing.
script for gunzip method
maybe on xda it is common sense, but for me it was necessary to know, that these stock android recovery extracted files can be restored with nandroid custom recovery, if you simply repack them into tar archive.
i put this two command lines in a dirty shell script (extract + repack as tar).
thanks to ektoric figuring out his gunzip method!
edit: notamamasboy's mount method added (but not tested yet). if script not works come back few days later, download again and check version, maybe it has changed meanwhile.
with this you're able to transfer data of non-rooted phone to (rooted) similar one.
this is useful in case touchscreen is broken, you haven't custom recovery installed, usb-debugging is disabled and connecting usb-otg-mouse doesn't work.
tested on my Archos 50 b Oxygen (Mediatek MT6582).
it works for me, feel free to improve, port to busybox and publish. no support. use at own risk.
edit: bckp2cwm.sh is deprecated it is FOR JELLY BEAN ONLY (no selinux support)
a newer (selinux) version bckp2win.sh for TWRP you can find here:
http://forum.xda-developers.com/showthread.php?t=3775129
How did you go about determining the magic number found at 0x200? My hexdump output does not have that magic number (1f 8b) in any instance. Leads me to believe my backup is not a tar file. Any suggestions then?
@notamamasboy, you are unfortunately correct.
Someone else also mentioned that their
Code:
userdata_xxxxxxxx_yyyyyy.backup
file was not of the same format I tried some "known magic headers", and could not find anything tell-tale. In which case, without some clues, you are back at square one.
ektoric said:
@notamamasboy, you are unfortunately correct.
Someone else also mentioned that their
Code:
userdata_xxxxxxxx_yyyyyy.backup
file was not of the same format I tried some "known magic headers", and could not find anything tell-tale. In which case, without some clues, you are back at square one.
Click to expand...
Click to collapse
Even more peculiarly, two backups were created a .backup and a .backup2, I wonder if combining with cat I can get somewhere...
The situation:
System partition has been wiped, would like to restore it using OTA.zip available from OEM
What I have
Access to fastboot and adb sideload in stock recovery
OTA zip package from OEM
What I have tried and my background
I have been on the client side of mods\recoveries\dev for android platforms on various devices for 4-5 years. I'm capable with Linux, and self teach quickly, I know just enough to get myself into trouble at the moment(hence the trouble I'm in).
1. I have tried to convert the system data in the OEM package to a yaffs etx4 style .img and send via fastboot, but I get "Invalid sparse file format at header magi" this led down a road to a tool called sparse converter that compressed the img into smaller parts, but then I get a more generic error "FAILED (remote: flash_cmds error!) For giggles , even know I know this would have been useless even if it had worked I tried it with the stock SDK 4.4.2 system.img just to see if I could fastboot any system files, same result.
2. So then I thought perhaps I could go the ADB side-load approach, first I tried just sending over the provided OTA zip package, but I get an error on the device after if finishes transferring "end of footer from /tmp/update.zip not 0xffff (file exists)" and "Signature verification failed" this led me to using a tool called "UpdatezipCreator" to generate a zip with the system files and sign the package, this also was a dead end.
So i'm turning to the wisdom and experience of XDA for some guidance, I'm willing to put in the leg work, I just need some direction.
TF103C Update
A couple of things. Im having the same issues with creating a yaffs ext4 .img and have the same error when i got to flash the image. Intel actually has a repo some place for bay trail (with bay lake included) device setup (https://01.org/android-ia). I did the same thing you did with AOSP and as expected it tries to boot but fails and boot loops.
I have however been able to flash the update.zip that is on the Asus website through recovery. First question did you unzip the the first zip file? The zip that is the link contains another zip which is the one you upload and update (sideload worked for me).
Im wondering if you can help me out too. I got an OTA about a day ago and hit the back button but it decided to update anyway. The tablet rebooted and just flashed a red bar at me then turned off. I can get to the droidboot to load images but I cant boot into recovery and im not sure why. Ive tried using the zenRoot recoveries that were used for rooting, but no luck. Booting to system or recovery produces a red bar and turns off. Do you by chance have a recovery I could try? Thanks.
Hope that was helpful.
Eclipse00 said:
The situation:
System partition has been wiped, would like to restore it using OTA.zip available from OEM
What I have
Access to fastboot and adb sideload in stock recovery
OTA zip package from OEM
What I have tried and my background
I have been on the client side of mods\recoveries\dev for android platforms on various devices for 4-5 years. I'm capable with Linux, and self teach quickly, I know just enough to get myself into trouble at the moment(hence the trouble I'm in).
1. I have tried to convert the system data in the OEM package to a yaffs etx4 style .img and send via fastboot, but I get "Invalid sparse file format at header magi" this led down a road to a tool called sparse converter that compressed the img into smaller parts, but then I get a more generic error "FAILED (remote: flash_cmds error!) For giggles , even know I know this would have been useless even if it had worked I tried it with the stock SDK 4.4.2 system.img just to see if I could fastboot any system files, same result.
2. So then I thought perhaps I could go the ADB side-load approach, first I tried just sending over the provided OTA zip package, but I get an error on the device after if finishes transferring "end of footer from /tmp/update.zip not 0xffff (file exists)" and "Signature verification failed" this led me to using a tool called "UpdatezipCreator" to generate a zip with the system files and sign the package, this also was a dead end.
So i'm turning to the wisdom and experience of XDA for some guidance, I'm willing to put in the leg work, I just need some direction.
Click to expand...
Click to collapse
I have the same problem, keysersoza42. I did a "fastboot wipe system" and now I only have access to fastboot. Just need to find a way to put system back
keysersoza42 said:
I have however been able to flash the update.zip that is on the Asus website through recovery. First question did you unzip the the first zip file? The zip that is the link contains another zip which is the one you upload and update (sideload worked for me).
Click to expand...
Click to collapse
Can you please tell me the exact steps you used to get sideload to work? I have the same problem as Eclipse00 : "after if finishes transferring "end of footer from /tmp/update.zip not 0xffff (file exists)" and "Signature verification failed""
Asus TF103C update.zip
UPDATE: Link to system.img
goo.gl/Oz2X7o
Honestly all i did was follow the normal steps to do a side load. One thing to make sure of is that you have the correct version of the firmware; BBY, WW, etc. When you first download it it is a Zip file in a zip file so the second one is the one you need to side load. To step this out:
1) Download from Asus the correct update. If you dont know which version you have you can boot into the bootloader and one of the versions will say BBY, WW, etc...
2) Unzip the contents of the download from Asus. This should be another zip file.
3) Boot into recovery. If you get the 'dead android' press and hold vol down for about 5 seconds then press vol up.
4) In recovery enter sideload mode
5) adb sideload innerUpdate.zip file (the zip file you unzipped from the downloaded file).
6) works???
This is what worked for me. The other option is to fastboot a system.img. This is hard b\c Asus doesnt release them and when i dd'ed a system image off of the partition it wouldn't load. I did however find a way to get a system image on there through fastboot. If it comes down to this let me know and ill post more on it. Good luck!
RaVe-N said:
Can you please tell me the exact steps you used to get sideload to work? I have the same problem as Eclipse00 : "after if finishes transferring "end of footer from /tmp/update.zip not 0xffff (file exists)" and "Signature verification failed""
Click to expand...
Click to collapse
---------- Post added at 08:55 PM ---------- Previous post was at 08:36 PM ----------
Sorry this is old, but just a couple of weeks ago i got the fastboot system.img to load. Here are the steps I did to produce this.
Some times its helpful to unpack a system image and/or repack to be flashed to an android device. For example the Asus tf103c required special compressing for parsing.
Tools you will need:
simg2img
make_ext4fs
Windows
SparseConverter_1.0.0.exe
Note: There were system.img files that were pulled directly from a rooted device using dd. These images would always give an error (flash_cmds_error!) while trying to write the image even if it had been compressed. The only way I got around this was to mount and unpack an image known to flash correctly (in my case the Intel BayTrail image from the intel android repo). The replace the contents with what every you wish to be in there (in my case the system folder from the Asus update.zip). The limitation here is you are limited to the size of the original flashable .img. Usually you can remove odex files to get around this and push those later if needed.
For the Asus images the NFC was removed from the list of features b\c it didnt have NFC which resulted in the settings app to crash during onCreate. These files were removed from the system directory.
/system/etc/permission/*.nfc*
Step-by-step guide
Steps 1-6 may be done in linux but step 7 and 11-15 must be done in windows.
In your workspace create a dir. mkdir sys
./simg2img system.img sys.raw
If you get : "Invalid sparse file format at header magi Failed to read sparse file"
You must decompress the image first with SparseConverter.
go to step 9 except replace 14 with this: SparseConverter.exe /decompress [.img to decompress] [.img to write to] then return to this step and continue.
SparseConverter.exe /decompress E:\system.img_sparsechunk1 D:\system.img
sudo mount -t ext4 -o loop sys.raw sys/
sudo ./make_ext4fs -s -l 1638M -a system new.img sys/
Note: The size needs to change depending on how big of an im age it is.
You may try to push the image as is, but if you get a "Invalid Sparse File Format At Header Magi" you have a compression error in the system image and can not be separated properly.
In windows open a command prompt window
Navigate to the SparseConverter_1.0.0.exe
SparseConverter.exe /compress [.img to compress] [.img to write to] [size in MB]
SparseConverter.exe /compress D:\system.img E:\ 256MB
Good Luck!
AndroidDestoryer said:
I have the same problem, keysersoza42. I did a "fastboot wipe system" and now I only have access to fastboot. Just need to find a way to put system back
Click to expand...
Click to collapse
Thanks.
I think the reason sideload isn't working is that my OTA update version is higher than the version downloadable as a zip...
Those are the steps I followed but it just doesn't work.
What exactly is the system image file you have linked to? Has it already gone through all the steps mentioned below? Is it plain old AOSP?
Thanks for all the help.
keysersoza42 said:
UPDATE: Link to system.img
goo.gl/Oz2X7o
Honestly all i did was follow the normal steps to do a side load. One thing to make sure of is that you have the correct version of the firmware; BBY, WW, etc. When you first download it it is a Zip file in a zip file so the second one is the one you need to side load. To step this out:
1) Download from Asus the correct update. If you dont know which version you have you can boot into the bootloader and one of the versions will say BBY, WW, etc...
2) Unzip the contents of the download from Asus. This should be another zip file.
3) Boot into recovery. If you get the 'dead android' press and hold vol down for about 5 seconds then press vol up.
4) In recovery enter sideload mode
5) adb sideload innerUpdate.zip file (the zip file you unzipped from the downloaded file).
6) works???
This is what worked for me. The other option is to fastboot a system.img. This is hard b\c Asus doesnt release them and when i dd'ed a system image off of the partition it wouldn't load. I did however find a way to get a system image on there through fastboot. If it comes down to this let me know and ill post more on it. Good luck!
---------- Post added at 08:55 PM ---------- Previous post was at 08:36 PM ----------
Sorry this is old, but just a couple of weeks ago i got the fastboot system.img to load. Here are the steps I did to produce this.
Some times its helpful to unpack a system image and/or repack to be flashed to an android device. For example the Asus tf103c required special compressing for parsing.
Tools you will need:
simg2img
make_ext4fs
Windows
SparseConverter_1.0.0.exe
Note: There were system.img files that were pulled directly from a rooted device using dd. These images would always give an error (flash_cmds_error!) while trying to write the image even if it had been compressed. The only way I got around this was to mount and unpack an image known to flash correctly (in my case the Intel BayTrail image from the intel android repo). The replace the contents with what every you wish to be in there (in my case the system folder from the Asus update.zip). The limitation here is you are limited to the size of the original flashable .img. Usually you can remove odex files to get around this and push those later if needed.
For the Asus images the NFC was removed from the list of features b\c it didnt have NFC which resulted in the settings app to crash during onCreate. These files were removed from the system directory.
/system/etc/permission/*.nfc*
Step-by-step guide
Steps 1-6 may be done in linux but step 7 and 11-15 must be done in windows.
In your workspace create a dir. mkdir sys
./simg2img system.img sys.raw
If you get : "Invalid sparse file format at header magi Failed to read sparse file"
You must decompress the image first with SparseConverter.
go to step 9 except replace 14 with this: SparseConverter.exe /decompress [.img to decompress] [.img to write to] then return to this step and continue.
SparseConverter.exe /decompress E:\system.img_sparsechunk1 D:\system.img
sudo mount -t ext4 -o loop sys.raw sys/
sudo ./make_ext4fs -s -l 1638M -a system new.img sys/
Note: The size needs to change depending on how big of an im age it is.
You may try to push the image as is, but if you get a "Invalid Sparse File Format At Header Magi" you have a compression error in the system image and can not be separated properly.
In windows open a command prompt window
Navigate to the SparseConverter_1.0.0.exe
SparseConverter.exe /compress [.img to compress] [.img to write to] [size in MB]
SparseConverter.exe /compress D:\system.img E:\ 256MB
Good Luck!
Click to expand...
Click to collapse
Versions and system.img
Oh yeah i forgot about that. If you are ahead of the update then it will reject the load. Last i checked there was an "2.0.33.80" and a "2.0.33.101" on the asus website. I think 101 is 4.4.4, but not 100% sure on that.
The system.img is a stock image of the ASUS TF103C. It has no NFC b\c the device does not have NFC and if you leave some of the files in there the settings app will crash b\c it thinks its a feature it should find. The version should be "80" or 4.4.2. This will load regardless of the version that is currently loaded since you are loading it through the bootloader. I have tried this on both the WW and BBY versions and it worked. It has already gone through the steps i listed below.
RaVe-N said:
Thanks.
I think the reason sideload isn't working is that my OTA update version is higher than the version downloadable as a zip...
Those are the steps I followed but it just doesn't work.
What exactly is the system image file you have linked to? Has it already gone through all the steps mentioned below? Is it plain old AOSP?
Thanks for all the help.
Click to expand...
Click to collapse
Thanks mate.
I'll give it a whirl tonight and see how it goes. I should just be able to use "fastboot flash system system.img" correct?
keysersoza42 said:
Oh yeah i forgot about that. If you are ahead of the update then it will reject the load. Last i checked there was an "2.0.33.80" and a "2.0.33.101" on the asus website. I think 101 is 4.4.4, but not 100% sure on that.
The system.img is a stock image of the ASUS TF103C. It has no NFC b\c the device does not have NFC and if you leave some of the files in there the settings app will crash b\c it thinks its a feature it should find. The version should be "80" or 4.4.2. This will load regardless of the version that is currently loaded since you are loading it through the bootloader. I have tried this on both the WW and BBY versions and it worked. It has already gone through the steps i listed below.
Click to expand...
Click to collapse
fastboot
Yes that is correct and in the bootloader.
Did you give this a try? Did it work?
RaVe-N said:
Thanks mate.
I'll give it a whirl tonight and see how it goes. I should just be able to use "fastboot flash system system.img" correct?
Click to expand...
Click to collapse
keysersoza42 said:
Yes that is correct and in the bootloader.
Did you give this a try? Did it work?
Click to expand...
Click to collapse
YES! Thanks so much! had to fastboot erase cache and data as well but it works!
Cheers!
keysersoza42 said:
Yes that is correct and in the bootloader.
Did you give this a try? Did it work?
Click to expand...
Click to collapse
Hi again.
So after a couple of days usage I've noticed a few things...
There appears to be no camera driver. The camera app just complains that you need to have a camera to use it...
Also some things that used to work don't anymore: So far I've noticed the Google Inbox app doesn't work, and any dosbox app doesn't work. They just FC.
Should I retry again, maybe redo the factory reset. Maybe wipe the data partition from fastboot?
Camera and other crashes
Ill have to take a look at it. I hadnt used any of those so ill have to checkout it out. Ill try to get some time this week.
RaVe-N said:
Hi again.
So after a couple of days usage I've noticed a few things...
There appears to be no camera driver. The camera app just complains that you need to have a camera to use it...
Also some things that used to work don't anymore: So far I've noticed the Google Inbox app doesn't work, and any dosbox app doesn't work. They just FC.
Should I retry again, maybe redo the factory reset. Maybe wipe the data partition from fastboot?
Click to expand...
Click to collapse
Same issue
Hi guys,
Just noticed this thread, and gave the uploaded system.img a try using fastboot command.
It gives me the error that the system img cannot exceed a certain amount of bytes (500 mb'ish)
any tips?
Brick3d said:
Hi guys,
Just noticed this thread, and gave the uploaded system.img a try using fastboot command.
It gives me the error that the system img cannot exceed a certain amount of bytes (500 mb'ish)
any tips?
Click to expand...
Click to collapse
Try this: http://forum.xda-developers.com/showpost.php?p=60638910&postcount=78
RaVe-N said:
Try this: http://forum.xda-developers.com/showpost.php?p=60638910&postcount=78
Click to expand...
Click to collapse
If you need to unbrick your tablet, have a look at my simple guide here!
http://forum.xda-developers.com/android/help/comprehensive-guide-unbricking-asus-t3106719
keysersoza42 said:
Asus TF103C update.zip
UPDATE: Link to system.img
goo.gl/Oz2X7o
Honestly all i did was follow the normal steps to do a side load. One thing to make sure of is that you have the correct version of the firmware; BBY, WW, etc. When you first download it it is a Zip file in a zip file so the second one is the one you need to side load. To step this out:
1) Download from Asus the correct update. If you dont know which version you have you can boot into the bootloader and one of the versions will say BBY, WW, etc...
2) Unzip the contents of the download from Asus. This should be another zip file.
3) Boot into recovery. If you get the 'dead android' press and hold vol down for about 5 seconds then press vol up.
4) In recovery enter sideload mode
5) adb sideload innerUpdate.zip file (the zip file you unzipped from the downloaded file).
6) works???
This is what worked for me. The other option is to fastboot a system.img. This is hard b\c Asus doesnt release them and when i dd'ed a system image off of the partition it wouldn't load. I did however find a way to get a system image on there through fastboot. If it comes down to this let me know and ill post more on it. Good luck!
---------- Post added at 08:55 PM ---------- Previous post was at 08:36 PM ----------
Sorry this is old, but just a couple of weeks ago i got the fastboot system.img to load. Here are the steps I did to produce this.
Some times its helpful to unpack a system image and/or repack to be flashed to an android device. For example the Asus tf103c required special compressing for parsing.
Tools you will need:
simg2img
make_ext4fs
Windows
SparseConverter_1.0.0.exe
Note: There were system.img files that were pulled directly from a rooted device using dd. These images would always give an error (flash_cmds_error!) while trying to write the image even if it had been compressed. The only way I got around this was to mount and unpack an image known to flash correctly (in my case the Intel BayTrail image from the intel android repo). The replace the contents with what every you wish to be in there (in my case the system folder from the Asus update.zip). The limitation here is you are limited to the size of the original flashable .img. Usually you can remove odex files to get around this and push those later if needed.
For the Asus images the NFC was removed from the list of features b\c it didnt have NFC which resulted in the settings app to crash during onCreate. These files were removed from the system directory.
/system/etc/permission/*.nfc*
Step-by-step guide
Steps 1-6 may be done in linux but step 7 and 11-15 must be done in windows.
In your workspace create a dir. mkdir sys
./simg2img system.img sys.raw
If you get : "Invalid sparse file format at header magi Failed to read sparse file"
You must decompress the image first with SparseConverter.
go to step 9 except replace 14 with this: SparseConverter.exe /decompress [.img to decompress] [.img to write to] then return to this step and continue.
SparseConverter.exe /decompress E:\system.img_sparsechunk1 D:\system.img
sudo mount -t ext4 -o loop sys.raw sys/
sudo ./make_ext4fs -s -l 1638M -a system new.img sys/
Note: The size needs to change depending on how big of an im age it is.
You may try to push the image as is, but if you get a "Invalid Sparse File Format At Header Magi" you have a compression error in the system image and can not be separated properly.
In windows open a command prompt window
Navigate to the SparseConverter_1.0.0.exe
SparseConverter.exe /compress [.img to compress] [.img to write to] [size in MB]
SparseConverter.exe /compress D:\system.img E:\ 256MB
Good Luck!
Click to expand...
Click to collapse
the link to system.img is not working
Got some problem when I tried to flash the stock ROMs on acer A3-A40 tablet.
I have got the files from ACER support web sites, the zip file contains these dir/files :
--
META-INF/
boot.img
file_contexts.bin
lk.bin
preloader_neostra8167_tb_n.bin
scatter.txt
system.new.dat
system.patch.dat
system.transfer.list
type.txt
tz.img
I can boot into Recovery now but from the Recovery menu, it always said "package file not exist" (or not found) when I select "Apply update from SD card".
Should I rename the xxx.zip file to something like 'update.zip' ??
BTW, these are the files I have downloaded now:
--
- OS_Acer_AV0M0.RV03RC04.WW.GEN1_A60M_A.zip
- OS_Acer_RV09RC01.WW.GEN1_A60M_A.zip
- SD_ACer_AV0M0_A3-A40_RV07RC01_WW_GEN1.zip
none of them works for me......
Any advice here?
yes.
Koumeles.
Can someone send me RV07 rom?
RV07RC01
I can't download it anywhere. Everyone saying to download ti from ftp, but I cannot access it.
have about the same problem, during the update the power was turned off and after charging the battery the tablet hung on the Acer screensaver.
1. archives do not need to be unpacked when writing to a memory card.
2.Could you send me an archive - SD_ACer_AV0M0_A3-A40_RV07RC01_WW_GEN1.zip
The service center said that it could not access the FTP site to download this archive.
Look here if you can help firmwarefile_com/acer-iconia-one-10