Database Info

[Q] can't umount offical system.img in ubuntu?

Hello,
I want to modify system.img and repack it from ruu "Saga_HKCSL_CHT_1.31.832.3"
My operation system is Ubuntu 11.04, I have used command : " mount system.img ./tmp/ -o loop " , it auto mount as ext4 format.
It looks like no problem, but when I umount the image, the command "umount ./tmp/" can't return, and the kernel log has a message " EXT4-fs error (device loop2): ext4_init_inode_table:1282: comm ext4lazyinit: Something is wrong with group 0 "
I guess the Desire S's ext4 format is not the normal ext4 format, I try to use " simg2img " and got a error message " bad magic ".
Can anyone help me? thanks!

If I understand, you want to extract system.img, modify it, and put it back in the RUU file ?

Igl0 said:
If I understand, you want to extract system.img, modify it, and put it back in the RUU file ?
Click to expand...
Click to collapse
I use hboot to write the system.img back, because my phone is S-Off, so i can put the PG88IMG.zip on the SD card to flash my phone.

I meet same problem,someone can help me

[Resolved] [Q] How to install stock rom from RUU on Wildfire using linux only?

Hi!
I have an HTC Wildfire, have it rooted, clockwork and cyanogenmod installed. Now, I need to send it back for repair an therefor restore everything as it was. This thread is great help: http://forum.xda-developers.com/showthread.php?t=1160251
I have a problem though: I don't have Windows except for Virtualbox and RUU won't work there. So I need to install the data from RUU*.exe using linux tools only.
So far I have extracted the rom.zip file using wine and
Code:
find .wine/drive_c/ -name 'rom.zip' -exec cp -v {} ./update.zip \;
Inside this rom.zip I have the following:
Code:
android-info.txt radio.img recovery.img system.img userdata.img boot.img hboot_7225_1.01.0001_101117.nb0 rcdata.img splash1.nb0
So I boot into the recovery and try to flash rom.zip which I have renamed to update.zip and copied to /sdcard/. I needed to turn signature checkings off to get past signature checking error, now I get following:
Code:
E:Can't open /sdcard/update.zip
(bad)
Installation aborted
I assume that it is possible to install all the *.img and *.nb0 files, but in what order do I have to install them and how exactly? I have linux, fastboot and adb at my disposal. HTCFlasher doesn't work with wildfire. So, how do I get my stock rom back? Does anybody have an idea?

Found out myself (sort of).
Ok, I bit the bullet, cleaned the cache and did as follows from a folder with all the rom images:
Code:
fastboot flash boot boot.img
fastboot flash radio radio.img
fastboot flash rcdata rcdata.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot reboot
Now I have HTC stock firmware with HTC Sense on top of it. Probably no root, but I need it to send my wildfire back for repair anyway.
Last thing to do: install hboot with
Code:
fastboot oem mb 9C068490 1 30
fastboot flash hboot hboot_7225_1.01.0001_101117.nb0
Let's hope it'll work.
EDIT: It did work indeed!
Code:
BUZZ PVT SHIP S-ON
HBOOT-1.01.0001
Does anybody know what "fastboot oem mb 9C068490 1 30" exactly does? Except that it is an OEM command of course?

Soft Brick

So I managed to successfully soft brick my one xl with rogers after I tried the Debranding method explained by JSLEnterprises, while we wait for a CWM recovery that might help me I need some help getting my phone working. So far fastboot is useless (on a mac) when I try to fastboot update to JSLEnterprises's rogers ruu.zip I get all this
Whoops: didn't find expected signature
read_central_directory_entry failed
error: failed to access zipdata in '??K?WY-??/?>?*{??
??#/????mGFb?-=?f?qxg??|*??)???y?ftm???>?66?-#???????$???:̇+_??????????Z?~???>??fe?o?/?`?O?B??A??xa_?&???+{]?W???G
??Άֽ???0??)
??
?K???ڷ[?v-i
XrOW??7 ?l????ր?z??9'?'??R??y???-?:?????W|???>??
??????? ?_?)?VC?--???B?o???<Xa??Z8 ????_x??vo????????ԟ6p???
c{~?~??j???Js?a???0????????`??
??>?[.씄C쿨덻
?',`?~??o??ѱ3?x??P?6v?
?:???!?X?,"K???S??=x?\??M
;sO#L~?Eh?p????/??f?²}?آ?u?!??
I have also tried extracting the system.img boot_signed.img and recovery (just for kicks) and tried flashing those individually. The system.img just wouldn't flash,
sending 'system' (1048572 KB)... FAILED (remote: data length is too large)
boot and recovery send and write just fine.
I tried extracting the contents of my zip with the only program I could find that could open said zip, (all others would say it was invalid) and then rezipped it, when I try to flash that I get it telling me that no boot.img was found, thats fair cuz its named boot_signed, I open the zip, rename all the *_signed.img to just *.img and it goes fine with the exeptions that no .sig files are there and system.img is too large.
Whenever I go to my recovery and try to factory reset, I get errors at first about how it cant mount /data/data/recovery/log, but the factory reset gives me
Formatting /data
cant't mount /data
and then cant' mount all sorts of locations in the /cache
then formatting /cache
wipe complete
trying to apply and update from either internal, external or cache seems to fail and make my phone reboot
I have also tried the windows at&t ruu, every one out there the 1.52, 1.68 even 1.44 but no luck. I did JSLEnterprises trick of replacing rom.zip with the rogers.zip but I get error 155 and my phone gets stuck at a black screen with chrome htc letters until i reboot it. Is there anything else you guys could suggest that would help since I contacted the fellow who is working on a CWM port and he informed me that mounting the "sdcard" wont be possible right away.
Somebody help!

Help - unbrick using fastboot and files from update.zip?

I have bricked my kyobo ereader (gingerbread 2.3.5) but still have fastboot and limited adb (no shell commands since there is no valid system) access on the device.
I have various update.zips for the device but unfortunately these are installable only on a working system (via settings->privacy->updates) and I know of no way of installing the update.zip since there does not appear to be any custom recovery for this ebook reader and booting into recovery does not install the update.zip on the sdcard.
The update.zip for the Kyobo ereader contains boot.img, recovery.img and a system folder containing files and directories for the system partition (an example of an official update.zip is available from m.kyobobook.co.kr/mirasol/update.zip )
I have extracted the system folder on a ubuntu system and need to prepare a system.img file which may be flashed using fastboot. I have also changed owner of the extracted files to root:root and chmod 777 on all the executables in the extracted system folders. A complication is that I only have the windows qualcomm hsusb drivers for fastboot or adb to connect to a pc, so I must use a windows 7 notebook to flash the device (possibly precluding pushing the system folder files to the device since they don't have permission and owner settings in windows)
I have tried various tools to make a system.img including the native linux mkcramfs and tools suggested by various google searches such as mkfs.yaffs2.x86 and make_ext4fs. All these tools could prepare a system.img but unfortunately they have different sizes and I am not sure which img is the correct one. I have tried to flash the various system.img using both fastboot flash system system.img and also by adding the system.img to the update.zip (together with placeholders for the required android-info.txt but in all cases they do not any files onto the sytem partition (although fastboot does send the system.img successfully to the device and writes the 120~180MB img files in about 50-70seconds. I have tried using both the official boot.img and the rooted boot.img. I noticed that the device reboots twice after such flashing which may be because there is some protection from the official recovery.img which checks the system partition an erases it if it does not match.
My first 2 questions are general and the third is specific to my situation:
1. What is the correct tool to generate an android system.img file from the extracted update.zip's system folder on a linux system?
2. Any suggestions on how to flash an update.zip using fastboot or adb?
3. Are there any generic recovery.img which I could try to flash over the official recovery partition on the kyobo mirasol ereader?
Any suggestions anyone?

[Q] TF300T TWRP bootloop. Return to stock?

Any help would be greatly appreciated. I recently flashed the new TRWP using fastboot. Went fine. I then tried to wipe and flash the newest version of KatKiss. I thought it also went fine but after reboot, it bootloops TWRP. I can tell the tablet to boot Android, but it just hangs. Then when I try to boot back into TWRP, it starts the bootloop all over again. Here is what it's doing during bootloop.
Running OpenRecoveryScript
E:Could not mount /data and unable to find crypto footer.
E:Unable to mount '/data'
E:Unable to recreate /data/media folder.
Updating partition details...
E:Unable to mount '/data'
...done
E:Unable to mount storage.
E:Unable to mount /data/media during GUI startup.
Full SELinux support is present.
E:Unable to mount /data/media/TWRP/.twrps when trying to read settings file.
Processing AOSP recovery commands...
E:Unable to mount '/data'
-- Wiping DATA Partition...
Formatting Cache using make_ext4fs function.
After about 1 minute it will follow with...
E:Unable to mount '/data'
-- Data Partition Wipe Complete!
Done processing script file
It will then reboot within 3 seconds after displaying the last line, and begin it all over again.
I'm hoping someone can tell me what options I have at this point. Would I be able to return to stock using fastboot and ASUS's blob from their website? Again, any help is greatly appreciated!

Solved.
I had already figured on buying a new tablet regardless, so I figured I'd go ahead and try to recover using fastboot. It did work. I noticed this post had a few views, and on the chance there were other people having the same issue, I'll post how I did it. I recommend using Windows 7 for this.
Download the appropriate firmware from ASUS's website. (WW, US, CN, JP etc...) Unzip the file twice until you have the META-INF folder and blob file. I placed both of these into a folder named "TF300t" directly on the C drive.
Install your device drivers, I used the Google SDK drivers.
Boot into fastboot.
Run these commands...
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\TF300t\blob (Again, this is where I saved my blob file.)
You should see something along these lines, when flashing your system...
C:\>fastboot -i 0x0B05 flash system c:\TF300t\blob
erasing 'system'...
OKAY [ 1.665s]
sending 'system' (800931 KB)...
OKAY [142.128s]
writing 'system'...
OKAY [155.462s]
finished. total time: 299.255s
When it's finished, run the last command...
fastboot -i 0x0B05 reboot
From this point, you should be booted back into stock.

Recreate the partition
anim0sity said:
I had already figured on buying a new tablet regardless, so I figured I'd go ahead and try to recover using fastboot. It did work. I noticed this post had a few views, and on the chance there were other people having the same issue, I'll post how I did it. I recommend using Windows 7 for this.
Download the appropriate firmware from ASUS's website. (WW, US, CN, JP etc...) Unzip the file twice until you have the META-INF folder and blob file. I placed both of these into a folder named "TF300t" directly on the C drive.
Install your device drivers, I used the Google SDK drivers.
Boot into fastboot.
Run these commands...
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\TF300t\blob (Again, this is where I saved my blob file.)
You should see something along these lines, when flashing your system...
C:\>fastboot -i 0x0B05 flash system c:\TF300t\blob
erasing 'system'...
OKAY [ 1.665s]
sending 'system' (800931 KB)...
OKAY [142.128s]
writing 'system'...
OKAY [155.462s]
finished. total time: 299.255s
When it's finished, run the last command...
fastboot -i 0x0B05 reboot
From this point, you should be booted back into stock.
Click to expand...
Click to collapse
anim0sity
What happened if you dont have the blob???
I had a tab, i complete erase all the partition and i cannot install any app, always had error 963
How i can recreate all the partition of my tablet?
It running android 5 lollipop
Regards,

Shouldn't be any reason you don't have the blob file. You can download it straight from ASUS's website. When you download it, it comes in a zip file. You have to extract it twice. So unzip the original zip file downloaded, then unzip the file you get from unzipping the original. From there, you should have the blob file needed to flash your tablet back to stock using fast boot / sdk tools.
Sent from my SAMSUNG-SGH-I317 using XDA Free mobile app

anim0sity said:
Shouldn't be any reason you don't have the blob file. You can download it straight from ASUS's website. When you download it, it comes in a zip file. You have to extract it twice. So unzip the original zip file downloaded, then unzip the file you get from unzipping the original. From there, you should have the blob file needed to flash your tablet back to stock using fast boot / sdk tools.
Sent from my SAMSUNG-SGH-I317 using XDA Free mobile app
Click to expand...
Click to collapse
Hi Anim0sity
I downloaded the package and starting doit the process
H:\android-sdk\platform-tools>fastboot devices
015d15b4fc481208 fastboot
H:\android-sdk\platform-tools>fastboot erase system
_
Now is hanging here what i can do it??
Thanks

successful
Hi
After many tries and plug the usb cable in the back of my tower i successful install the firmware
Regards,

HI to rstore to stock using twrp, is it as simple as downloading the file to the tablet, unziping once then flashing the resulting file, or is it a bit more difficult than that?