Hey guys
The volume rocker on my HD2 is broken, and I have cLK flashed on my device. My problem is that I can only boot into cLK and fastboot mode as recovery is useless to me because I cant navigate through the options using the volume rocker.
I am looking for a rom (android/winmo) that is a .img file so that I can flash through fastboot, or if any of you know any other possible way I can flash a rom through fastboot so I can get my phone working again. Right now I dont mind which rom I flash, as long as I get my phone in working order again.
All help is GREATLY appreciated....!!!
If anyone also knows how I can compile a rom into a .img file so I can flash through fastboot, that is also welcomed help!
Any ROM you download that is for cLK has a. img file in it. you will have to extract the file from the. zip hou download to find it. Read my post here it will give youthe details on how to flash your ROM.
T-Macgnolia said:
Any ROM you download that is for cLK has a. img file in it. you will have to extract the file from the. zip hou download to find it. Read my post here it will give youthe details on how to flash your ROM.
Click to expand...
Click to collapse
Hey bud, thanks for the reply, but my question still remains... what about the other 2 folders in the rom folder (META-INF and SYSTEM) what happens with those? lol....
atsavlis said:
Hey bud, thanks for the reply, but my question still remains... what about the other 2 folders in the rom folder (META-INF and SYSTEM) what happens with those? lol....
Click to expand...
Click to collapse
Sorry for the late response but those two files do get used, the img file oules the information from them as it is flashing. To put it simply when you initiate the flash the img does the rest of the work. The img file is sort of like a cab file for Windows Mobile only it is not all self contained and has more functions than just to install the software. Note I said sort of not exactly like, that is just a comparison to help you understand. When you flash a Android ROM via CWM it essentialy just activates the img file to flash the ROM.
Daf roms come as a system.img
or
if you have access to another hd2, flash the target rom to it and then use mkyaffs2img command in the terminal to dump the system folder to a system.img file.
Benefit of this would be you can tweak the rom(reduce size for example, by removing unwanted apps) before you dump to system.img
samsamuel said:
Daf roms come as a system.img
or
if you have access to another hd2, flash the target rom to it and then use mkyaffs2img command in the terminal to dump the system folder to a system.img file.
Benefit of this would be you can tweak the rom(reduce size for example, by removing unwanted apps) before you dump to system.img
Click to expand...
Click to collapse
Thanks for getting back to me buddy! Unfortunately I dont have a second HD2, and I dont know anyone willing to help me out in Greece, lol... Would you be willing to dump your system folder for me and upload it so I can use yours?? I would GREATLY appreciate the help... sitting with my HD2 "semi" bricked... lol
Also, if I use the .img file from the DAF roms, can I flash it using fastboot??? You have any suggestions on how I can flash it considering I cant use the volume rocker on my mobile?
Well id like to say yes but it's Easter weekend and my sons 1st birthday tomorrow, so the likelihood of getting near a PC are slim for a few days.
You could always learn how to use the android emulator,, build the image on a virtual hd2
As for flashing,,, no idea, no clue what fastboot does, magldr for me, but in your OP you implied you could use it to write img files to partitions.
You ever got a solution for this? I'm in the exact same situation right now.
Related
Hi,
I was wondering if there was a way to convert .zip files of ROMs/themes into system.img files so that they can be booted up via the android sdk emulator?
I've seen that it's possible to launch system.img files in the sdk emulator, but after searching for quite some time I wasn't able to pinpoint a method for creating system.img from update-cm-4.2.12.2-signed.zip (for example).
Thanks.
DT
i made a post about those system.img files earlier here: http://forum.xda-developers.com/showthread.php?t=609090
in theory it's possible using the mkfs.yaffs2 tool, but i'm not sure whether the emulator supports danger SPL roms, because the system image file size is limited in the emulator as well...
http://www.dotphone.org/attachment.php?aid=6
it's the mkfs.yaffs2 tool
see usage here:
http://www.dotphone.org/viewthread.php?tid=32
Hi,
Thanks for the link, but I'm quite a newbie in these things, so could someone please walk me through process? I've downloaded the archive in the link.
How many times do I unzip it (I can unzip it up to three times and then I get 5 files numbered 1 through 5)? Where do I paste it? How do I use it? The explanation in the other thread was slightly too complicated for me sorry
Thanks
DT
/push
Anyone willing to help out a newbie?
bump
I am looking to do the same thing
Get someone to Nandroid backup the ROM.
It creates a system.img, recovery.img, data.img, cache.img and boot.img.
Not the easiest method but it works
I've compiled and installed a modded kernel. I'm trying to figure out how to load AOSP compiled binaries. I've tried using adb flash_image system /sdcard/system.img, but I get "failed with error: 6." Does anyone know what this means or how to load system.img on a Galaxy Tab from VZW? I'm working on reactivating the phone dialer...
the galaxy tab has nothing like fastboot, so its pretty hard to flash it! but u can try to overwrite a stock factory.rfs with the files from ur system.img and flash via odin!
That sounds like a great idea. However, I'm trying to figure out how to put the vendor specific drivers in the system.img, which is mountable and editable. If I could get my hands on an original stock system.img, that'd be awesome.
Sent from my SCH-I800 using XDA App
As far as I know, the Tab doesn't use mtd file system, so I don't think it uses .img extensions.
Not positive though. Somebody correct me if I'm wrong.
I know for a fact that img files are created as the output of an Android system build. This img can be broken apart with standard Linux tools. I've already done this. I've also mounted factoryfs.rfs to a local directory, which allows me to move apps to and from the file system.
Sent from my SCH-I800 using XDA App
If you have a md5 of it too, you should be able to flash it via an advanced restore in CWM recovery. That is if it is only the data that is flashed to /system. otherwise I would suggest converting it to a .fs or .tar and flash via heimdall or Odin (respectively).
What PC tools can I use to open .img files in a nandroid/CWM backup set?
Must I set up an Android ROM cooking kitchen using Virtual Box + Ubuntu, or is there another way?
zyborg said:
What PC tools can I use to open .img files in a nandroid/CWM backup set?
Must I set up an Android ROM cooking kitchen using Virtual Box + Ubuntu, or is there another way?
Click to expand...
Click to collapse
use the attached unyaffs.exe to extract a system.img! simply drag the created system.img onto unyaffs.exe and it will extract alle the files in the same directory!
to rebuild, i think it might be able to create a image file in magic disk maker but im not sure
zyborg said:
What PC tools can I use to open .img files in a nandroid/CWM backup set?
Must I set up an Android ROM cooking kitchen using Virtual Box + Ubuntu, or is there another way?
Click to expand...
Click to collapse
http://android-dls.com/wiki/index.p...cking.2C_Editing.2C_and_Re-Packing_the_images
Landroid said:
use the attached unyaffs.exe to extract a system.img! simply drag the created system.img onto unyaffs.exe and it will extract alle the files in the same directory!
to rebuild, i think it might be able to create a image file in magic disk maker but im not sure
Click to expand...
Click to collapse
thanks! this was very easy to use
Hi Guys,
I have created this video trying to explain myself what was going on with my phone. Please someone help me to fix this.
just add youtube dot com/ (with the back slash) before the following link. Sorry since I'm new here it won't allow me to post any links.
watch?v=x8kIBi8NVsE
Problems are:
1. Not booting to Android Cyanogen
2. Stuck on MAGLDR Screen
3. Recovery (Vol down + Power button ) don't work.
4. Not connecting to activesync (Windows 7)
Thank you. Please let me know if you have any questions.
Same problem, the only thing i get to work is WP7.
I want to install Android and there is no colored Bootloader and the USB-Flasher in MAGLDR isnt helpful for flashing something except WP7.
And when im using the toolkit the drivers (can be downloaded through the Toolkit) arent woking.
Thanks in advance ;-)
shankar10 said:
Hi Guys,
I have created this video trying to explain myself what was going on with my phone. Please someone help me to fix this.
just add youtube dot com/ (with the back slash) before the following link. Sorry since I'm new here it won't allow me to post any links.
watch?v=x8kIBi8NVsE
Problems are:
1. Not booting to Android Cyanogen
2. Stuck on MAGLDR Screen
3. Recovery (Vol down + Power button ) don't work.
4. Not connecting to activesync (Windows 7)
Thank you. Please let me know if you have any questions.
Click to expand...
Click to collapse
Hi,
It's worth trying to download an official ROM from T-Mobile and
Change the .exe to .zip and
Extract with winrar or 7z the RUU_Leo_HTC_****************************_Ship.zip
find the larger *.nbh file and rename it to leoimg.nbh and place this file on an sd card that is 4gb or less.
Then try to boot that from 2. Boot AD SD in magldr.
malybru said:
Hi,
It's worth trying to download an official ROM from T-Mobile and
Change the .exe to .zip and
Extract with winrar or 7z the RUU_Leo_HTC_****************************_Ship.zip
find the larger *.nbh file and rename it to leoimg.nbh and place this file on an sd card that is 4gb or less.
Then try to boot that from 2. Boot AD SD in magldr.
Click to expand...
Click to collapse
Thanks. I'll try that.
malybru said:
Hi,
It's worth trying to download an official ROM from T-Mobile and
Change the .exe to .zip and
Extract with winrar or 7z the RUU_Leo_HTC_****************************_Ship.zip
find the larger *.nbh file and rename it to leoimg.nbh and place this file on an sd card that is 4gb or less.
Then try to boot that from 2. Boot AD SD in magldr.
Click to expand...
Click to collapse
Okay I've done as you told and didn't work. It's saying SD kernal open failed. Do I have delete whatever I have in the SD card and just place only this file?
This wont work because the phone seeks an android-install not a winmo 6.5 stock-rom,
Sorry mate
Im seeking for solution for this problem 3 days now and the only thing that could work is an winmo installation on sd
Sent from SGS2 (VillainROM 1.4)
Sturmfest said:
This wont work because the phone seeks an android-install not a winmo 6.5 stock-rom,
Sorry mate
Im seeking for solution for this problem 3 days now and the only thing that could work is an winmo installation on sd
Sent from SGS2 (VillainROM 1.4)
Click to expand...
Click to collapse
Did you try that yourself? Do you know how to do it?
shankar10 said:
Did you try that yourself? Do you know how to do it?
Click to expand...
Click to collapse
The problem is that theire working on it but i dont know if it comes or when it comes to our phones, at the moment there is no solution to fix this,
by the way i have experienced that most of dft-roms and tools are working with usb-flasher mode in magldr, so we have to find someone who could modify a winmo rom to flash with daw.exe
Sent from SGS2 (VillainROM 1.4)
same problem guys !
Try this
http://forum.xda-developers.com/showthread.php?t=893618&page=260
Hi guys!
Ok. so I'm (really) not a developer, I'm just trying to make a flashable ZIP (+ custom recovery and root) from the latest D80230f_00.kdz (told you, not a dev', but, yeah, everyone should starts with something right?). and I got some difficulties at the end of the process: when trying to flash the zip file, I got a big red error (ok, just red) in TWRP: "E: failed to sysMapFIle /sdcard/rom_name.zip".
Have you ever met this error?
Furthermore, I got a question about the update-binary file (maybe it's link to the error?): I've downloaded @somboons KK_template_new.zip, but their was already an update-binary file in it. I've unziped the archive, write everything I need in the updater-script, and re-zip all (see attachments), I don't do anything except ziped all: should I do something else such as sign the archive or thing like this? 'cause I don't find anything accurate about update-binary file: I don't know if we have to take it from other archive, or if it's create during signing the archive.
Oh, yeah, the recovery.img is TWRP 2.8.7.1.
Anyway, all kind of help will be very appreciate.
Thanks in advance guys !
@casual_kikoo
I would ask a mod to move your post to the Q&A where it belongs
I'm not sure if they move them or delete threads when they're not in the right sub forums.
Lawlrus said:
@casual_kikoo
I would ask a mod to move your post to the Q&A where it belongs
I'm not sure if they move them or delete threads when they're not in the right sub forums.
Click to expand...
Click to collapse
Oh ok so I post in wrong place... I was..sure :crying: ...
Thanks!
casual_kikoo said:
Hi guys!
Ok. so I'm (really) not a developer, I'm just trying to make a flashable ZIP (+ custom recovery and root) from the latest D80230f_00.kdz (told you, not a dev', but, yeah, everyone should starts with something right?). and I got some difficulties at the end of the process: when trying to flash the zip file, I got a big red error (ok, just red) in TWRP: "E: failed to sysMapFIle /sdcard/rom_name.zip".
Have you ever met this error?
Furthermore, I got a question about the update-binary file (maybe it's link to the error?): I've downloaded @somboons KK_template_new.zip, but their was already an update-binary file in it. I've unziped the archive, write everything I need in the updater-script, and re-zip all (see attachments), I don't do anything except ziped all: should I do something else such as sign the archive or thing like this? 'cause I don't find anything accurate about update-binary file: I don't know if we have to take it from other archive, or if it's create during signing the archive.
Oh, yeah, the recovery.img is TWRP 2.8.7.1.
Anyway, all kind of help will be very appreciate.
Thanks in advance guys !
Click to expand...
Click to collapse
Whenever u flash a zip for it needs to be signed, I would check or Ayysir's Android Kitchen, that's where I started my development from, I started just like u, only modifying touchwiz roms and repackaging them in flushable zoos format with android kitchen, if u need help let me know
P.S., Windows is NOT the platform to start development on lol, if I were u I'd start dual booting whatever machine ur using with a Linux OS of ur choice, for someone new like urself, I'd go with Ubuntu
Sent from my Nexus 6 using Tapatalk
soupysoup said:
Whenever u flash a zip for it needs to be signed, I would check or Ayysir's Android Kitchen, that's where I started my development from, I started just like u, only modifying touchwiz roms and repackaging them in flushable zoos format with android kitchen, if u need help let me know
P.S., Windows is NOT the platform to start development on lol, if I were u I'd start dual booting whatever machine ur using with a Linux OS of ur choice, for someone new like urself, I'd go with Ubuntu
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
First of all, thanks you so much for your fast answer. Yeah, I know Windows isn't the easiest platform to start development. Well, I've already have Ubuntu installed on VMWare, I just took screenshots on Windows .
Ok, so if I understood well, update-binary file is created during the signing step? That's why it doesn't work right now, 'cause I don't signed my ZIP.... Yeah ok I start to understand !
I'm gonna download Android Kitchen (this one right?) and start cooking !
Again, thanks you so much dude you make me more and more enthusiast about creating ROMs on Android.
I had 50pc japan version of s5(sc-04f), installed rom 'G900F.STOCK.FOR.SCL23.FULL.MINHQUAN'. The downside of this rom is that its pre-rooted. I managed to unroot it by goin in supersu & click 'full-unroot'. But i had multiple devices to flash, so is there a way for me to re-pack this firmware again after i unroot it? So that i could flash it to my other devices without root.
wee2000 said:
I had 50pc japan version of s5(sc-04f), installed rom 'G900F.STOCK.FOR.SCL23.FULL.MINHQUAN'. The downside of this rom is that its pre-rooted. I managed to unroot it by goin in supersu & click 'full-unroot'. But i had multiple devices to flash, so is there a way for me to re-pack this firmware again after i unroot it? So that i could flash it to my other devices without root.
Click to expand...
Click to collapse
Your best bet is to post this question within the following Q&A thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=2700073
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
ok done, thx 4 the info
just in case if i missed the reply there, hope someone could reply me here?
when i extract the ZIP file, i got
METE-INF folder
boot.img
system.img
just in case if i missed the reply there, hope someone could reply me here?
when i extract the ZIP file, i got
METE-INF folder
boot.img
system.img
wee2000 said:
just in case if i missed the reply there, hope someone could reply me here?
when i extract the ZIP file, i got
METE-INF folder
boot.img
system.img
Click to expand...
Click to collapse
Should we search for this firmware or you can provide a link to its thread?
the link is here : https://choimobile.vn/threads/6-0-1-scl23-stock-rom-g900f-full-port-v3-by-huaminhquan93.37412/
wee2000 said:
the link is here : https://choimobile.vn/threads/6-0-1-scl23-stock-rom-g900f-full-port-v3-by-huaminhquan93.37412/
Click to expand...
Click to collapse
Generally, if it's 6.0.1 and rooted systemlessly, you need to replace boot.img with a stock one and remove SuperSU app from system.img.
This ROM intended to be flashed from TWRP, so it's an ext4 image.
You can mount it to a linux system on your PC and remove anything you want.
I havent done anything like this before. Could u give me some links or guides? My PC is running Windows 10.
wee2000 said:
I havent done anything like this before. Could u give me some links or guides? My PC is running Windows 10.
Click to expand...
Click to collapse
Ok, here' a simpler way:
1. Make changes on one phone.
2. Make a TWRP backup of boot and system partitions.
3. Restore this backup on other phones. They must have TWRP installed, a 6.0.1 bootloader and modem.
You'll have to rename backup's folder path and to wipe cache/data/system before restore.
can i use winrar to extract & compile the rom, without linux? So that i will have a much faster flashing process for all other units..
wee2000 said:
can i use winrar to extract & compile the rom, without linux? So that i will have a much faster flashing process for all other units..
Click to expand...
Click to collapse
Ok, I've managed to download that ROM at last.
The things look even simpler.
To prepare an "unrooted" ROM:
1. Download the zip form this post and unpack updater-script somewhere.
2. Make a copy of V3.G900F.STOCK.FOR.SCL23.FULL.MINHQUAN.zip, open it with Windows Explorer and replace V3.G900F.STOCK.FOR.SCL23.FULL.MINHQUAN.zip\META-INF\com\google\android\updater-script with the file you've unpacked from the attachment.
3. Try to flash ans see if it's what you need.
thx so much, already passed all units to the buyer. ill try that on next batch restock, may iknow if there's a way to get the service menu shortcode *#0*# to work again? This rom doesn't has the service menu.
bbsc said:
Ok, I've managed to download that ROM at last.
The things look even simpler.
To prepare an "unrooted" ROM:
1. Download the zip form this post and unpack updater-script somewhere.
2. Make a copy of V3.G900F.STOCK.FOR.SCL23.FULL.MINHQUAN.zip, open it with Windows Explorer and replace V3.G900F.STOCK.FOR.SCL23.FULL.MINHQUAN.zip\META-INF\com\google\android\updater-script with the file you've unpacked from the attachment.
3. Try to flash ans see if it's what you need.
Click to expand...
Click to collapse
I've replaced the updater-script in the zip file, but supersu is still there