Here's a dump of clean 8105 (official O2 2.1) firmware:
Streak_8105_img.zip
You may use it as a base for mods.
Dump as in nandroid, or you extracted the. Pkg
If the second then how?
fards said:
Dump as in nandroid, or you extracted the. Pkg
Click to expand...
Click to collapse
I manually dumped (cat /dev/mtd/mtd0 > /sdcard/boot.img) boot and recovery after rooting the device. Then reflashed pkg and clockwork, and dumped system and userdata.
damn i was hoping you'd worked out how to get into the .pkg
just thinking if we can unyaffs the recovery from a stock, we may be able to work out how they extract it..
brb
EDIT
Damn recovery is an binary standalone executable..
no joy with that one then
fards said:
damn i was hoping you'd worked out how to get into the .pkg
Click to expand...
Click to collapse
Is update.pkg something specific to Dell Streak?
Googling "update.pkg" gives references related to Streak only...
Thread temporarily stuck.
yeah it's an odd file system,
OSx and PS3 also use ,pkg files, but neither seem to have any relation to the update.pkg that we're getting from Dell.
I agree with you that it probably is a binary that takes over the device and puts things in correct places.
If you observe the update process it does a lot of things.
The binary approach gives a lot of flexibility and you do not have to relay on features built into the firmware.
Maybe this can help.... This is not a dump but the update.zip extracted from the update.pkg. You will see that it is the usual format of an update under android. There is also the baseband update in the zip.
http://www.megaupload.com/?d=9A1QI7PM
geek78 said:
Maybe this can help.... This is not a dump but the update.zip extracted from the update.pkg.
Click to expand...
Click to collapse
We are more interested in the extraction procedure.
Ah ok. You have to try to update a device with the wrong device type build. When you have the message "bat Fota ..." take out the battery. In the SD card you will have a file update.pkg.dec. This is a zip of a "standard" pkg file (under OSX you can expand this pkg file extracted). Credit to Clus3R
LOL. Neat trick ;-)
Reminds me how I extracted .msi packages from .exe ;-)
geek78 said:
Ah ok. You have to try to update a device with the wrong device type build. When you have the message "bat Fota ..." take out the battery. In the SD card you will have a file update.pkg.dec. This is a zip of a "standard" pkg file (under OSX you can expand this pkg file extracted). Credit to Clus3R
Click to expand...
Click to collapse
AWESOME!!!
hi - ive literally just got my Streak out of the box (standard Dell unlocked version)
Can i use this on mine?
And if so is there any special procedure??
Applying the .img with fastboot in usual way like the recoverys?
edit:
I think, this should work:
Code:
fastboot-windows.exe -i 0x413c flash recovery recovery.img
fastboot-windows.exe -i 0x413c flash userdata userdata.img
fastboot-windows.exe -i 0x413c flash system system.img
fastboot-windows.exe -i 0x413c flash boot boot.img
fastboot-windows.exe -i 0x413c reboot
edit2: hmm: userdata failed. Any ideas?
Related
Credits to geek78.
I take no responsibility if your brick you device!!!
This worked for me and i am now on Stock 1.6 6601 with the original baseband.
Please do not ask me to support any issues.
1. You need to downgrade back to O2 stock 4399.
Download the official update 4399 from here : http://loadbalancing.modaco.com/download.p...104_4399_21.pkg
Copy this update to the root of your sdcard and rename it update.pkg
Download this zip http://hotfile.com/dl/62324940/5dea6fd/recovery.rar.html
Unzip it on your desktop
Put your streak in fastboot mode
Go to the directory where are the files from recovery rar and execute the right cmd for your situation :
fastboot-yourOS -i 0x413c flash recovery recovery.stock.new.img
push the the 2 volume buttons and at the same time execute the right cmd for your situtation :
fastboot-yourOS -i 0x413c reboot
Choose update from sd card …. And after the process you have now a 4399 21 build
Root your streak and install a browser like root explorer and a terminal from de market
2. Change the system so it will accept the 6601 pkg file when trying to restore.
Download the official 6601 build from HERE and place the file at the root of your SDCARD.
Download THIS FILE, unzip it and place it at the root of your SDCARD (the name of the file should show up as boot.img)
Download THIS FILE and unzip it where your want on your sdcard.
Then mount your / as rw and copy all the files unziped at the same place on the streak (etc to /etc, system to /system ...) do NOT overwrite entire folders, just copy the 3 files inside those folders to their respective folders under /system, /bin and /etc)
From terminal on your streak with su rights execute this
flash_image boot /sdcard/boot.img
Reboot your streak in normal mode
Reboot your streak in recovery mode and apply the update from sdcard
Once booted you should be on 6601 1.6 at&t firmware and baseband.
Thanks for the post.
I am planning to return to 1.6
This would help me.
wow, very cool, will downgrade later. thanks!
When we mount / as rw, I'm assuming you want us to but the contents of etc to /system/etc, bin to /system/bin and then the recovery-from-boot.p to /system, correct?
Also, do you happen to have the fastboot-windows? It's not a big deal if you don't.
downgrade and baseband restore worked great. thanks a bunch. this is especially helpful now with the kernel released and I want to play with some custom roms, can always revert back to stock.
the first link does not work, just goes to the Modaco home page
Are you downgrading from 8105 2.1 or the earlier version? Since I updated to 8105 i have been unable to get to 4399.
Sent from my Dell Streak using XDA App
ok i found the stock O2 4399 elsewhere, but the zip file does not have a fastboot-windows, just mac and linux. do i just move my fastboot.exe file to the recovery folder that has the recovery.stock.new?
Yes just use the fastboot.exe and rename the file if you want to follow the instructions exactly.
Sent from my Dell Streak using XDA App
ok i just got
E:No signature (972 files)
E:Verification failed
joeclark said:
ok i found the stock O2 4399 elsewhere...
Click to expand...
Click to collapse
Where is a reliable location? The 4399's I've found indicate they may have been customized. I am looking for plain vanilla stock 4399. TIA.
GenghisKhent said:
Where is a reliable location? The 4399's I've found indicate they may have been customized. I am looking for plain vanilla stock 4399. TIA.
Click to expand...
Click to collapse
hxxp://loadbalancing.modaco.com/download.php?url=paul/streak/Streak_104_4399_21.pkg
ok that one is installing thanks for the full address
JaysFreaky said:
hxxp://loadbalancing.modaco.com/download.php?url=paul/streak/Streak_104_4399_21.pkg
Click to expand...
Click to collapse
After changing hxxp to http, I get a redirect to hxxp://www.modaco.com/; no pkg file.
joeclark said:
ok that one is installing thanks for the full address
Click to expand...
Click to collapse
No problem!
GenghisKhent said:
I get a redirect no pkg file.
Click to expand...
Click to collapse
Really? That's strange. I downloaded it and it seems joeclark was able to as well.
EDIT: I just tried it myself, and it's not working anymore, either.
Go to this page, and skip the zip (they're pre-rooted) and go to the pkg.
hxxp://android.modaco.com/content/dell-streak-streak-modaco-com/310618/19-aug-streak-1-6-downloads-how-tos-rom-superboot-recovery/
ok now i am getting fota mismatch
i got the 4399 installed and am trying to get to the 6601, i put all the files where they belong pretty sure i did the flash_image correctly
and then i went to do the recovery from the update.pkg and i get the error
trying the 2nd part again crossing fingers
FOTA model name mismatch. System restart in 30 seconds.
any ideas?
oh yeah and i have flashing lights now too.
joeclark said:
ok now i am getting fota mismatch
i got the 4399 installed and am trying to get to the 6601, i put all the files where they belong pretty sure i did the flash_image correctly
and then i went to do the recovery from the update.pkg and i get the error
Click to expand...
Click to collapse
Clubtech said in the other thread to remove your battery and send him the .dec file that is on the sdcard. Maybe he can help you with that.
joeclark said:
trying the 2nd part again crossing fingers
FOTA model name mismatch. System restart in 30 seconds.
any ideas?
oh yeah and i have flashing lights now too.
Click to expand...
Click to collapse
fota error and flashing lights so you have still :
recovery from 4399
boot from 6601
So you have made a mistake during the copy of the files to the right location. .. try again....
I wonder if this is working for both 6941 and 8105?
Hi everyone,
I tried using a script which automated the install for the the custom recovery, but I started to get messages that it ran out of disk space (I can't link to the file due to my noob status). I probably should have come here first before using that script, but such as life..
I have no important data on the phone, if I lose it all that's ok.
It rebooted and my p500 waits with the following
"Fastboot mode started"
"udc_start()"
It also gives some info when USB is connected ie.
"- suspend -"
"- reset -"
Do I have a paperweight?
thanks and sorry for the newb post ..
edit: so I found this : http://forum.xda-developers.com/showthread.php?t=1003790 and
http://forum.xda-developers.com/showthread.php?t=875881
and have gotten it to the yellow emergency mode, not sure how to flash it from here though.
edit2: dling the stock firmware from http://forum.xda-developers.com/showthread.php?t=1073827
edit3: there's this as well.. http://forum.xda-developers.com/showthread.php?t=1088046 If I try this method, will it screw up again from too little free disk space?
I'm to drunk to guide our give you the link to fix it but I will tell you, you can fix it just hold on we will help you ; ) and we don't by the time I wake up I will help you its ok ))
Sent from my LG-P500 using XDA Premium App
dislplin01 said:
I'm to drunk to guide our give you the link to fix it but I will tell you, you can fix it just hold on we will help you ; ) and we don't by the time I wake up I will help you its ok ))
Sent from my LG-P500 using XDA Premium App
Click to expand...
Click to collapse
thank you very much, I appreciate it haha
Your phone has booted in fastboot mode. Go to development section and read a tutorial how to recover from fastboot.
Sent from my LG-P500 using XDA Premium App
setTopbox said:
thank you very much, I appreciate it haha
Click to expand...
Click to collapse
Then did u unbricked now
Mahesh
go here....
http://forum.xda-developers.com/showthread.php?t=1088046
or here
http://forum.xda-developers.com/showthread.php?p=13813493
How to install Android SDK /ADB
http://lgoptimusonep500.blogspot.com/2011/01/how-to-install-android-sdk-adb.html
dislplin01 said:
I'm to drunk to guide our give you the link to fix it but I will tell you, you can fix it just hold on we will help you ; ) and we don't by the time I wake up I will help you its ok ))
Sent from my LG-P500 using XDA Premium App
Click to expand...
Click to collapse
Most honest post I've seen on the entire forum.
Sent from my Kyocera Echo.
mvgadagi said:
Then did u unbricked now
Mahesh
Click to expand...
Click to collapse
I got the phone working again - thanks! I guess it's not a great idea to install the custom recovery
with low disk space?
setTopbox said:
I got the phone working again - thanks! I guess it's not a great idea to install the custom recovery
with low disk space?
Click to expand...
Click to collapse
Hmmm. Well, should not matter? /recovery uses a separate partition. Perhaps you flashed a corrupt (incomplete) image?
well if u ever wish to install recovery just download rom manger from market (latest) and install recovery from rom manger option make sure u hav eusb debugging enabled. it works easy
shhbz said:
well if u ever wish to install recovery just download rom manger from market (latest) and install recovery from rom manger option make sure u hav eusb debugging enabled. it works easy
Click to expand...
Click to collapse
Erm... reading all the posts about fastboot after using ROM Manager for this, I guess I would rather stick with the custom script using flash_image.
doktornotor said:
Hmmm. Well, should not matter? /recovery uses a separate partition. Perhaps you flashed a corrupt (incomplete) image?
Click to expand...
Click to collapse
hmm, I'm not sure (when I dl'd the file I did compare the hash as per instructions). I used the following instructions:
manast.com/2011/05/07/how-to-install-custom-recovery-on-lg-optimus-one-p500
I then went into a terminal emulator, and ran "sh /sdcard/rf.sh". At that point the output of the script started to say "disk full" (and then it reboot into the fastboot prompt).
setTopbox said:
I then went into a terminal emulator, and ran "sh /sdcard/rf.sh". At that point the output of the script started to say "disk full" (and then it reboot into the fastboot prompt).
Click to expand...
Click to collapse
No idea about that script. Using flash_image and never had any issue with "disk full", frankly the message does not make sense. All you need is to copy the recovery image to SD and run as root:
Code:
# flash_image recovery /sdcard/recovery.img
Done.
doktornotor said:
No idea about that script. Using flash_image and never had any issue with "disk full", frankly the message does not make sense. All you need is to copy the recovery image to SD and run as root:
Code:
# flash_image recovery /sdcard/recovery.img
Done.
Click to expand...
Click to collapse
I'm getting permission denied when trying to use flash_image. Gingerbreak says the device is rooted, and the terminal does ask for superuser permission when i open it (su works in the terminal). I also tried chmod 755 flash_image but that didn't work either.
the permissions for flash_image are r-xr-x any thoughts ?
edit: apparently the sdcard is mounted with -noexecute ? So I tried copying flash_image to / but it's read only. Is there somewhere where I can execute this?
This rf.sh script seems most notorious, I too went into fastboot after that. Doktornotor's method worked (in fact I think he/she was the one who bailed me out back then as well).
If you got into fastboot, most probably you have a rooted phone.
To use flash_image you need to get the flash_image.sh on the root of your sd card. Search the forum for Amon-Ra custom recovery, and you shall find this file in that thread (it is required for Amon ra setup). Log in to your adb console, and use fastboot to push the new image in the recovery partition.
Unless your recovery.img or flash_image.sh is corrupted, it will work for sure.
Keep in mind, fastboot is a very powerfull tool, if you can access it, you're safe.
Cheers,
Alex
did you get out??
just flash stock firmware with kdz worked for me bro
Buddy,
You do not need to flash anything with KDZ. The ROM is fine nothing happened to it. All your issue is with the recovery being flashed wrongly for some reason.
I had the same issue just yesterday and I managed to flash the recovery through fastboot.
What you need to do is:
1. Install android SDK from Google.
2. Connect the phone while it is on fastboot.
3. If your windows does not find the fastboot drivers online, use the drivers in this link:
http://www.megaupload.com/?d=39ZR16W1
4. extract the .zip file that you copied to your SD. The one that contains the recovery.
5. Copy the recover.img (or whatever the name of the .img file in the .zip file) to the folder inside the android sdk where fastboot.exe is located (I think its the tools folder)
6. Copy the adbwinapi.dll file from the android SDK\platform-tools\ to the folder containing fastboot.
7. issue the command (and replace recovery.img with the .img file name you have):
fastboot flash recovery recovery.img
fastboot reboot
Dr.Alani said:
Buddy,
You do not need to flash anything with KDZ. The ROM is fine nothing happened to it. All your issue is with the recovery being flashed wrongly for some reason.
I had the same issue just yesterday and I managed to flash the recovery through fastboot.
What you need to do is:
1. Install android SDK from Google.
2. Connect the phone while it is on fastboot.
3. If your windows does not find the fastboot drivers online, use the drivers in this link:
http://www.megaupload.com/?d=39ZR16W1
4. extract the .zip file that you copied to your SD. The one that contains the recovery.
5. Copy the recover.img (or whatever the name of the .img file in the .zip file) to the folder inside the android sdk where fastboot.exe is located (I think its the tools folder)
6. Copy the adbwinapi.dll file from the android SDK\platform-tools\ to the folder containing fastboot.
7. issue the command (and replace recovery.img with the .img file name you have):
fastboot flash recovery recovery.img
fastboot reboot
Click to expand...
Click to collapse
I appreciate the information. When I'm in adb, su won't allow me to gain root access on the phone. The phone itself is rooted using gingerbreak though.
setTopbox said:
I appreciate the information. When I'm in adb, su won't allow me to gain root access on the phone. The phone itself is rooted using gingerbreak though.
Click to expand...
Click to collapse
I do not see how you need to use adb.
Sent from my LG-P500 using XDA App
I downloaded roms from samfirmware, after I unrar it, these are the file list
boot.img bootloader.bin cache.img hidden.img modem.bin recovery.img system.img
So How can I extract some files from system.img? I've tried unyaffs, but it segfaulted.
another stupid question is , how I can flash these files using odin? just select *.img in
pda and start?
yo
hi darren.hoo, i faced the same problem as yours and i realised that we should actually boot our tab to the downloading mode before we launch Odin3,pda.Turn on the usb debugging too(i dont know if this is necessary or not).Anyway happy flashing!
*Odin can only read .tar / .md5 extension ,you dont have to extract everything.
Kruel
Hi Darren.hoo,
To read the image files - It depends.
boot.img and recovery.img requires potentially a script to seperate the ramdisk and also the kernel. There are many good article on many wikis that explains which hex point is the seperator between the two.
system.img - I haven't really played with this too much as I don't usually create ROMS or anything - have you tried to mount it normally on a linux system? as if the system.img is just a ISO? (e.g. mount -o loop system.img /mnt). To rebuild this to become "flashable" is a different story (i believe you need the unayffs2 tools).
bootloader.bin - you'll need a hexeditor of some sort. This is as is a bin file (data file)
Not sure about the others. (cache - i'd assume you can recreate anyway and the modem i guess is another binary that requires a hexeditor.)
In terms of flashing the IMG - you need to tar up the *.img files, then do something like md5sum -t #name of tar# >> #name of tar#. Basically, it just appends the hash in md5 format to the tar. rename the file to something like *.tar.md5, and use that to flash as PDA.
Hope this helps.
Really great tips!
frankus0512 said:
system.img - I haven't really played with this too much as I don't usually create ROMS or anything - have you tried to mount it normally on a linux system? as if the system.img is just a ISO? (e.g. mount -o loop system.img /mnt). To rebuild this to become "flashable" is a different story (i believe you need the unayffs2 tools).
Click to expand...
Click to collapse
no luck with this:
debian:/home/darren/gtab/rom/EUR/P7500XWKG9# mount -oloop system.img /mnt
mount: you must specify the filesystem type
But from what I've got from searching xda a lot, maybe it's RFS filesystem?
frankus0512 said:
In terms of flashing the IMG - you need to tar up the *.img files, then do something like md5sum -t #name of tar# >> #name of tar#. Basically, it just appends the hash in md5 format to the tar. rename the file to something like *.tar.md5, and use that to flash as PDA.
Click to expand...
Click to collapse
this tip just really solved my problem.
I've got a tar.md5 file with three files in it: boot.img, system.img, recovery.img, but I don't
want to flash recovery.img coz I've already flashed CWM, yesterday I tried delete recovery.img from the tar ball and then flash it, then ODIN tells me that the files is invalid by
md5sum. I didn't know earlier that it records md5 checksum at the end of the tarball file.
It seems the OP got his answer but I'm having problems figuring out what to do.
I also have a system.img that i unzipped from a tar.md5 package by first editing the file extension to only say tar and then untarring it. When I try to mount the system.img with:
sudo mount -o loop system.img /media/systemimg
I get the filesystem type error:
mount: you must specify the filesystem type
Could someone who knows this please comment on how to mount the system.img to gain access to the files so I can explore system, that would be awesome.
span_01 said:
It seems the OP got his answer but I'm having problems figuring out what to do.
I also have a system.img that i unzipped from a tar.md5 package by first editing the file extension to only say tar and then untarring it. When I try to mount the system.img with:
sudo mount -o loop system.img /media/systemimg
I get the filesystem type error:
mount: you must specify the filesystem type
Could someone who knows this please comment on how to mount the system.img to gain access to the files so I can explore system, that would be awesome.
Click to expand...
Click to collapse
samsung firmwares should have -t rfs but you have to have a linux kernel on your dev machine that has a rfs modules
http://forum.xda-developers.com/showthread.php?t=1081239
darren.hoo said:
I downloaded roms from samfirmware, after I unrar it, these are the file list
boot.img bootloader.bin cache.img hidden.img modem.bin recovery.img system.img
So How can I extract some files from system.img? I've tried unyaffs, but it segfaulted.
another stupid question is , how I can flash these files using odin? just select *.img in
pda and start?[/QUOTE,
........................................
hello,
you can extract system.img by android kitchen but it is long process to setup kitchen.
you make it .tar file to flash as pda in odin.
if you want to extract system.img, contact me by email, [email protected]
I will tell you .
Click to expand...
Click to collapse
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
ZV6 is out!! And NO this is not Lollipop... it's still Android KitKat 4.4.2
Thanks to an anonymous donor we now have the ZV6 TOT. I have broken down the TOT and also uploaded the individual partitions which can be flashed if rooted. Speaking of root... ZV6 blocks Stump Root. If you wish to use ZV6 and have root you must install Bump'd TWRP while on ZV4 then manually flash the ZV6 boot/modem/system partitions... OR you may be able to root on ZV4 then take the official ZV6 OTA update and keep root -- the OTA has NOT been pushed yet so it is too early to say for sure. Remember to NEVER take an OTA if you have modified your SYSTEM partition at all (xposed/tethermod/etc) OR if you have TWRP installed.
Changelog:
Google Security Patches
Qualcomm Security Patch
International Voice over WI-FI
Improve unlock algorithm when phone is in the pocket
Enhancements to the LG Home (Sluggish UI fix)
Enhancement to the compass application
Enhancement to the Auxiliary cable recognition.
Mobilize Device Content Caching - An application caches HTTP web and app data on the device (not the Network), making the retrieval of data faster and saving bandwidth on the network
--TOT (*.zip) can be downloaded *HERE*
Flash this TOT using the same method as ZV4. You will need to select "Board DL" in LG Flash, otherwise you will get stuck. After the TOT flashes it will reboot your phone into the "MiniOS".. unplug the USB cable and press and hold the power button on the phone then press on the "Normal Boot" option on your phones screen. You are now on stock ZV6. Remember... there is no root for ZV6 so do not flash ZV6 TOT unless you don't mind being without root.
--Individual ZV6 partitions to flash manually can be downloaded *HERE*
I am removing the system.img from Codefire but thanks to @budeone system.img has been mirrored HERE. Feel free to make more mirrors of system...
The bootloader does NOT need to be updated in order to use the ZV6 boot/modem/system images. It's completely optional to flash the bootloader files (aboot, sbl1, dbi, laf, factory, tz, rpm). To flash the boot, modem and system partitions manually someone can make some new flashable *.zips containing the partitions... OR you can use my "flash2" *.zips which can be found under the How-To Manually Flash/Update Device w/ System.img, Boot.img and Modem.img section in my *[PSA] NO OTAs!! | Keep Root/Unlock | How-To: Block OTA, DL SW/FW, Update Manually* thread. You simply stick any loose system.img and/or boot.img and/or modem.img on your internal sdcard and flash my premade flashable zips in TWRP to install them.
--ZV4-to-ZV6 OTA Update Zip can be downloaded *HERE*
You must have a stock recovery and stock system partition for this to work. Being rooted may be OK but if you've edited or removed apks or other files or edited the build.prop then OTA zip may fail the integrity check. Root may not stick thru OTA.. until someone confirms one way or the othe the risk is yours.
Directions:
1. Remove USB cable from phone.
2. Power phone off.
3. Press and hold volume down + power until you boot into stock recovery.
4. Select "update with adb"
Rename zip file into update.zip
Code:
adb sideload update.zip
Alternate Directions to skip using ADB (needs microSD card):
1. Format microSD card as EXT4.
2. Rename zip to update.zip
3. Move update.zip onto external SD card. EZ way would be to stick SD card in phone then connect phone to PC and use MTP.
4. Power off and boot into stock recovery (vol down + power)
5. Select the Update from SDCARD option.
Alternate Directions to skip using ADB (must have root):
1. Stick OTA zip file in the /cache directory
2. Power off and boot into stock recovery (vol down + power)
3. Select the Update from cache option... then select the update zip you placed in /cache
As mentioned above.. ZV6 blocks Stump Root. Bump is not blocked.. so as long as you have root with ZV4 you can manually update to ZV6 and keep Bump'd TWRP or flash any Bump'd kernel or rom. No anti-rollback has been added to this update either.. so downgrading to ZV4 works!
Click to expand...
Click to collapse
Autoprime. Thank you for your work. +1
I've tried using the flash2 with system, boot and modem imgs being in flash2 folder on the internal storage. But It says it successfully flashed them but reboot and nothing.
Nada. I don't believe its really flashing them since it goes really quick.
Well, took me a bit to get back up and running... but yeah, not seeing much of a difference in this versus ZV4. (Well, except losing root since I'm impatient and flashed the TOT.)
Interesting any major changes or is it a security update
autoprime said:
ZV6 is out!! And NO this is not Lollipop... it's still Android KitKat 4.4.2
Click to expand...
Click to collapse
I'll mirror when I get home from work today. Thanks man!
@autoprime I read all the above, but do you know if we take zv6, can we revert by .tot to zv4? I know there's been issues with that in the past.
Warboy said:
I've tried using the flash2 with system, boot and modem imgs being in flash2 folder on the internal storage. But It says it successfully flashed them but reboot and nothing.
Nada. I don't believe its really flashing them since it goes really quick.
Click to expand...
Click to collapse
the flash2 files have a check in them to make sure the proper file is in its proper place before anything else.. this way it doesnt erase your partition if its not actually going to flash a new file. Perhaps the folder is named Flash2 with a capital F? If the folder is named "flash2" with lowercase f and is located at /sdcard/flash2/ on your phone.... and the files are named system.img modem.img and boot.img with all lowercase letters.. it should work. They have been confirmed working by many users across all G3 models.
If there is still an issue.. please provide a recovery.log if possible.
engine95 said:
@autoprime I read all the above, but do you know if we take zv6, can we revert by .tot to zv4? I know there's been issues with that in the past.
Click to expand...
Click to collapse
No issues downgrading. There'd be giant red letters everywhere otherwise. But I have now added a mention in the OP that specifies downgrading is still an option. :good:
ZV6 upgrade went just fine, as you stated. No problems using flash2 stuff and let TWRP save the root. It seems to upgrade the Home launcher as well as the contacts database. It also upgrades the Sprint data-sharing activity. In other words, ZVF6 works fine, but is not a big update.
Flashable zip should be up tonight. Tomorrow at latest.
http://forum.xda-developers.com/showthread.php?p=56937777
I have a working compass!
I flashed the modem.img first with no apparent change, then the system.img... Shazammm! After calibration, the compass seems to be accurate. This was the big flaw for me on an otherwise lovely device and now it seems to be working. Now I can look forward to a Lollipop update.
I pray it fixes the bluetooth. I have a Chrysler U Connect system and my G3 or a G3 Vigor for my girlfriend will not stay paired to the unit.
After unzipping the system.img zip, it's named "14-system.img".
I plan on using the "flash2" process of upgrading.
Do I need to rename "14-system.img" to just "system.img" for the flash2 procedure to work?
Thank you
EDIT: I went back and re-read Auto's manual update procedure and can confirm, yes, I do need to rename "14-system.img" to "system.img"
autoprime said:
the flash2 files have a check in them to make sure the proper file is in its proper place before anything else.. this way it doesnt erase your partition if its not actually going to flash a new file. Perhaps the folder is named Flash2 with a capital F? If the folder is named "flash2" with lowercase f and is located at /sdcard/flash2/ on your phone.... and the files are named system.img modem.img and boot.img with all lowercase letters.. it should work. They have been confirmed working by many users across all G3 models.
If there is still an issue.. please provide a recovery.log if possible.
Click to expand...
Click to collapse
The files are in the internal SDcard under "/sdcard/flash2/*.img" * being there respected names
here is the link to the recovery.log
http://pastebin.com/AE7y7KAH
Warboy said:
The files are in the internal SDcard under "/sdcard/flash2/*.img" * being there respected names
here is the link to the recovery.log
http://pastebin.com/AE7y7KAH
Click to expand...
Click to collapse
thanks for log. odd, the only error in the log is that it doesn't see the system.img file and then aborts.
for whatever reason it's checking /sdcard/flash2/ and not finding the file. Not sure where to go from here. Logs would suggest that the file name is incorrect or folder name is wrong. But you've said they are correct.. so.. idk.
To debug this further.. can you connect to adb shell while in TWRP? And paste the output from the following commands?
Code:
adb shell
cd /sdcard/flash2/
ls
autoprime said:
thanks for log. odd, the only error in the log is that it doesn't see the system.img file and then aborts.
for whatever reason it's checking /sdcard/flash2/ and not finding the file. Not sure where to go from here. Logs would suggest that the file name is incorrect or folder name is wrong. But you've said they are correct.. so.. idk.
To debug this further.. can you connect to adb shell while in TWRP? And paste the output from the following commands?
Code:
adb shell
cd /sdcard/flash2/
ls
Click to expand...
Click to collapse
http://imgur.com/J5FkM9V
http://imgur.com/RGnDXyZ
Warboy said:
http://imgur.com/J5FkM9V
http://imgur.com/RGnDXyZ
Click to expand...
Click to collapse
I'm officially stumped
everything looks right. just not meant to be on your device I guess.
I'm reaching here.. but maybe there's some issue if you used MTP? Versus using ADB push to put the image on your phone?
Have you noticed if the modem or boot image has updated (those would be fast flashes) and just system is not working? or all 3 not working? You'd have to check the software settings under About Phone to see if baseband(modem) or kernel changed.
you could always use the dd command to try and flash the image while in TWRP..
Code:
adb shell
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/system
dd if=/sdcard/flash2/system.img of=/dev/block/platform/msm_sdcc.1/by-name/system
The 2 dd commands should take a minute or three to complete.
Or just wait for engine95's stock rooted ZV6 rom.
autoprime said:
I'm officially stumped
everything looks right. just not meant to be on your device I guess.
I'm reaching here.. but maybe there's some issue if you used MTP? Versus using ADB push to put the image on your phone?
Have you noticed if the modem or boot image has updated (those would be fast flashes) and just system is not working? or all 3 not working? You'd have to check the software settings under About Phone to see if baseband(modem) or kernel changed.
you could always use the dd command to try and flash the image while in TWRP..
Code:
adb shell
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/system
dd if=/sdcard/flash2/system.img of=/dev/block/platform/msm_sdcc.1/by-name/system
The 2 dd commands should take a minute or three to complete.
Or just wait for engine95's stock rooted ZV6 rom.
Click to expand...
Click to collapse
Should it be Flash2 not flash2
thznutz87 said:
Should it be Flash2 not flash2
Click to expand...
Click to collapse
I tried having a capital F and that didn't change anything.
system.7z
https://mega.co.nz/#!G0onwR5T!QV-NZ2hpAIllAX9tKCNBDkGLyE7AWD241Stws-c6y18