Database Users

HEIMDALL one-click The safest way to upgrade.

Hi,
We would like to make a idiot proof ROM upgrade method.
Too many people are, for example, accidentally upgrading P9000 ROM onto I9000.
That will brick a phone.
My suggesting is this.
Set phone to usb debugging mode.
Have a single tool that automatically does the following (unfortunately, only possible on a rooted phone):
1) Uses adb to backup the bml1 and bml3 boot loaders. (Might as well backup efs also and check the user has root. If a user cannot get root, they really should not be flashing their ROM in the first place. Some method to automatically check if the phone is "network locked" might help. Can you do things like *#06# from the adb command line?)
2) Do a checksum on the bml1 and bml3 backups to identify which boot loader is actually on the device, and therefore identify the device. I.e. I9000 or P9000.
3) Check the USB ID of the phone is correct.
4) Double checks that the boot loader files provided by the user are compatible.
5) Automatically use adb to switch the phone into download mode
6) Flash only a compatible bootloader.
If a new ROM is published with a new boot loader, prevent the user from using it, until developers upgrade HEIMDALL one-click to recognize the new boot loader.
Have another tool, that does similar, but that will never flash the bootloader. Instead it uses the files provided by the user to flash only the rest of the phone, and never the bootloaders.
So long as the boot loaders are not touched, even if boot loaders are in the user provided file, the user can always recover using the 301K JIG.
Another thing to consider is the PIT. Have the tool implement a feature to read the PIT from the phone and if the PIT provided by the user is the same, automatically do not re-partition.
If the PIT needs changing, only flash the PIT and with the bootloader tool (described above).
This will ensure the user can still reach Download mode, even though the user will have to flash an ROM to be able to boot the phone into Android after that. But the important bit is that the phone will not become a Brick.
Of the current PIT files, I don't think any of them wipe the BML1 and BML3 boot partitions.
They only modify the size of the system and data partitions.
The main way to make all this "safe" is to separate the "repartitioning and installing boot loaders" from the "ROM install".
"ROM install without PIT and bootloaders" is 100% safe, installing boot loaders and PIT is the risky bit, so provide a tool that does it safely.
Maybe include a good boot.bin and Sbl.bin with the safe bootloader tool.
What do people think?

I'm working with Benjamin Dobell, the developer of Heimdall. There will be several features in the first release..
The specs on the .9A release planned features are:
Open source - everyone can contribute
Java app- Cross platform, One download handles all major platforms
One Click Packaging-Developer can add in their PIT, PBL, SBL, Kernel, Modem and FactoryFS(ROM) by dropping files into the zip
Heimdall included-installed automatically for the platform the user is running
User Awareness-User must check "flash bootloader" and they must be "sure they want to do this" which will make it a 3 click operation
The 1.0 release will include more features. I'll make sure to point Benjamin to this thread.

it would be awesome to see this fly

It's good to hear that...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I cannot wait to see this! I am an Ubuntu user with Windows 7 only for Odin. Would love to have a reason not to use Windows.....ever.
Sent from my SAMSUNG-SGH-I897 using XDA App

As somewhat of a trial run, I branched this project into "One-Click UnBrick". This installs heimdall and will execute the close-pc-screen command. I am still working on it. The main problem is Win7 drivers. Distributing them in a one-click manner is tough. I've already worked around win7 UAC, registry, filesystem issues, and VC++ issues. The last problem is to figure out how to get the drivers to install for a Gadget device.

[A70B/IT2 HC][3.2.81 update] Enabling SDE and rooted firmware package

First:
Warning! This is only for A70B/A70IT2 Honeycomb model, It won't work on Froyo model!
Here is a package that enables unofficially SDE menu in recovery and install a rooted stock firmware with busybox and SuperUser.Apk
Pre-Requisite:
- Adb must be enabled on tablet and PC driver+adb command must be working. You can test on pc with "adb shell", it should give you a '$' prompt. If you don't have this, first make it work. There are multiple links around to help if needed.
Instructions:
- Unzip files on your pc in adb.exe directory.
- Launch enable_sde.bat on your pc. It's better to do it in a cmd.exe window, you'll be able to copy-paste log here if anything goes wrong.
- Follow instructions in the cmd window. Basically, script reboots tablet multiple times, you have to press enter when tablet is completely booted each time.
- Congratulation, your device is sde enabled and has a rooted sde firmware. Please read below for more information.
Upgrades:
If you already installed a first version and enabled sde already, here is how to install new rooted firmware:
- Optional: flash updated stock firmware. I always recommend to match stock firmware, it avoids dalvik-cache rebuilds and bootloaders may have been updated in new firmwares.
- Boot rooted firmware. You should be running rooted firmware if you want upgrade script to work. To be sure of that, you should see SuperUser app in your apps menu.
- Unzip files on your pc in adb.exe directory
- Launch upgrade.bat (or upgrade.sh for linux)
- Tablet reboots at the end to rooted firmware and should be upgraded to new version.
SDE information:
1) What is SDE?
SDE (Special Developer Edition) is basically a dual boot mechanism. It allows us to dual boot Archos stock firmware and our custom ones.
2) How does it work ?
I won't give much details on how to use it, I should do a separate topic about this one someday. Until then, here is some basic information:
- At the end of this script, you are booted with sde firmware, superuser should be in your start menu and you should be root with adb or any root app.
- If you reboot or boot, press volume up while booting, it will display the dual boot menu. Select "Developer Edition", it will start the rooted build (check here point 9 to see how it looks).
- If you missed volume key or don't do anything during reboot, you will go back to unrooted stock firmware. You have to press the volume up key during boot to get the boot menu.
- Warning: booting stock firmware is harmless except that you will loose your SuperUser.apk preferences. As it's not part of stock firmware, Android clears it.
- You can boot straight to rooted firmware by deleting the stock firmware kernel in recovery. Check here, do point 4,5, and on screen 6, select "Remove Android Kernel". Make sure that you have properly working SDE firmware before doing that. If you want to re-enable back stock firmware, just flash it from recovery again.
Downloads:
3.2.80 can be downloaded here: Mirror 1 (Mediafire), Mirror 2 (Sendspace).
3.2.81 can be downloaded here: Mirror 1 (SendSpace) (bat fixed)
Sorry, Mediafire no longer let me upload without signup, if you know one good upload location without registration and allowing more than 200 MB, let me know.

*reserved*

Registered just to say thank you!
Worked like a charm, and no problems using the shell script (I run Arch Linux)
Keep up the good work!

Thanks
I mean real thanks
Sent from my ARCHOS 70it2 using xda premium
EDIT:
Beautiful man, beautiful. Works splendidly
Thanks again

LeTama
Have a beer or two on me, 84G89322WT2139701.
Thanks again for your Rom.

Hi mrew42,
Thanks a lot! Much appreciated!

Tomorrow, my 70b return at home
I testing that !
but my 70bit2 is with 3.2.81

Letama, can you may be make the same for 3.2.81?

Yes, it will come soon...

3.2.81 is up and instructions on first post updated if you upgrade.

Great
http://www.jbmm.fr/?p=27601
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

cajl said:
Great
Click to expand...
Click to collapse
Nice job! Thanks for the article on jbmm!

Thanks, will try it out soon.

Thanks letama, this is just what I wanted. Awsome work!
I think there is an error in upgrade.bat and enable_sde.bat for 3.2.81.
The line that reads:
adb push android_32.ext4.update /media/
should read:
adb push android_32.ext4.update /data/media/
Also, upgrade.bat is missing the line that says:
adb shell rm /data/local.prop
Keep up the good work and thanks again.

ColinTaylor said:
I think there is an error in upgrade.bat and enable_sde.bat for 3.2.81.
The line that reads:
adb push android_32.ext4.update /media/
should read:
adb push android_32.ext4.update /data/media/
Click to expand...
Click to collapse
Ah! Right! Thanks for pointing it, I'll fix that and re-upload when I find time to do it.
Also, upgrade.bat is missing the line that says:
adb shell rm /data/local.prop
Click to expand...
Click to collapse
Yes, this is normal, this one is only needed when enabling sde first time. local.prop is coming from temp root and won't be there anymore.

I finally had time to try it out tonight, all seemed to be installed fine, but I don't see the Superuser in the apps list... I can boot into developers fw menu though. Did I miss something or should I just try to reinstall the SDE again by running that bat file again?

No, as ColinTaylor said, there is a typo in script, you just need to push the ext4.update at root of storage.
Just type this command in the directory you unzipped the files:
Code:
adb push android_32.ext4.update /data/media/
then boot sde.

Hello
As i have read your post about how to root 3.2.81, the instructions seems to confuse me, but what do you mean by adb? im sorry im kinda new at this ,please let me know thanks!

hello, first of all thanks for your work.
I am having some problems with the upgrade file.
it says that it cannot stat 'zImage':no such file or directory
and secondly it cannot open the kernel file (no such file or directory) mkf lashimage failed.
could you please provide some help with this?
thanks!

lozano.markp said:
Hello
As i have read your post about how to root 3.2.81, the instructions seems to confuse me, but what do you mean by adb? im sorry im kinda new at this ,please let me know thanks!
Click to expand...
Click to collapse
adb is a developer tool from android sdk that let you execute commands on your tablet from your PC. You have to install android sdk to get it, you need to enable it on the tablet and have a proper driver.

[UTILITY][RUU IMITATE]Easy Installer - Install your rom's like an RUU[HTC only]

Easy Installer​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What is Easy Installer?
Easy installer is a windows RUU imitate that helps you as user to install your Rom's with only 2 clicks. Fully automated!
For devs Easy installer helps to provide Rom's alternate to the recovery zip archive.
Click to expand...
Click to collapse
How does Easy installer work?
Thats easy. The developer create a system img file of his rom and configure Easy installer easily with one config file. The package can provide like a normal rom.
The user run a little exe-file and the RUU installs the rom fully automated! If something runs false, the RUU gives the user an error and a explanation what he can to do now.
Click to expand...
Click to collapse
What i need for Easy installer
For now, Easy Installer works only with image files, so you need your Rom as a image file. You can create a image file of your rom easily with mkyaffs.arm (find in attachements).
The config file is easy to understand. An example here (found in package too):
Code:
;The config file is neccessary for the RUU. Here you define all file namens.
[functions]
;imgfile specify, if you want to flash a image or a zip file (0=zip-file, 1=img-file). For now, only img files working, sry :(
imgfile=1
;waitbl set the time the RUU wait for the bootloader (fastboot). Some devices take a while to reboot to bootloader. Set the time here, in generally the time 10 is enough
waitbl=10
;the img-name specify the name of the image file without the file extension!
img-name=system
;zip-name is for one of the next versions, when it is possible to flash zip files. If you want, you can delete this
zip-name=HC_MIUI3.2
;boot-name specify the name of the boot.img without extension.
boot-name=boot
;set the name of the clockworkmod recovery file for your device here.
cwm-name=cwm
;rec-name is the original recovery of HTC that must be inserted for img-files. Put the name here without extension
rec-name=recovery
[labels]
;specify the shown rom-name in the RUU
rom-name=.sense
;the device name is the full name of the device the rom is for
device-name=Wildfire S
;some devices has more versions (marvel, marvelc, marvelct e.g.). Specify for what device your rom is.
device-code=marvel
The picture in the RUU is namend "PHONE.bmp" in package, you can replace with your own.
Click to expand...
Click to collapse
How to create the system.img?
Well, thats is easy
1. Install your Rom you want to use in Easy Installer at your phone via the Recovery (don't start the Rom!!!)
2. Go to recovery, connect your phone via USB-Cable to computer
3. Download the mkfs.arm.zip (see attachements)
4. Create a new directory in your SD-Card (example: "build")
5. Copy the extracted file "mkfs" of the downloaded archive into the folder "build"
6. Insert the SD-Card into the phone
7. In recovery go to: "mounts&storage->mound /sdcard" or run following adb-command: adb mound /sdcard
8. run the following commands in adb one after one:
adb shell
cd /sdcard/build
./mkfs /system /sdcard/build/system.img
9. Wait for the "Build OK."-message
10. Exit the adb shell via exit command and turn off the phone
11. Take the SD-Card of the phone and insert it into your PC
12. in the SD-Card's folder /build you will find a "system.img". Use this file for the easy installer
Click to expand...
Click to collapse
Changelog
v0.0.1
- first version, basic install function
Click to expand...
Click to collapse
Download
See the attachements (WSWizard.zip)
Click to expand...
Click to collapse

Will this work for all devices?
Any chances of bricking? Because many of users of Micromax A70 bricked their phone by a chinese flashing tool.
Burned from my laser torch using pencil cells

Sorry, i see now, that i posted this in false section. In genarally it works only for HTC devices which are unlocked or S-OFF, not for others!

How can I use the mkfs.arm?

it works only on ARM-based devices, like the HTC phones.
You must copy the file onto your sd-card e.g.:
adb push mkfs.arm /sdcard/build
After this you install your Rom on the device or copy the /system-files to the sd-card. Now you run following command:
adb shell
cd /sdcard/build
./mkfs.arm /system /sdcard/system.img
ODER
./mkfs.arm /sdcard/build/system /sdcard/system.img
Then the file will build a system.img and copy it onto the sdcard for next use

Would like to know if this would work to ONelll123
Wipe everything
Flash Rom
Make Nandroid
Use Nandroid as ROM's Images
It seems much easier to me than having to go to shell and all Not meant to be an insult, just a recommendation/question

Hmm, it ia qn idea, but idk in what filesystem the backups are saved. If it is yaffs2 it can be that this works.
But you must do shell commands too. Its for secruity reasons and that this method used works.
Sent from my HTC Wildfire S A510e using XDA

ONeill123 said:
it works only on ARM-based devices, like the HTC phones.
You must copy the file onto your sd-card e.g.:
adb push mkfs.arm /sdcard/build
After this you install your Rom on the device or copy the /system-files to the sd-card. Now you run following command:
adb shell
cd /sdcard/build
./mkfs.arm /system /sdcard/system.img
ODER
./mkfs.arm /sdcard/build/system /sdcard/system.img
Then the file will build a system.img and copy it onto the sdcard for next use
Click to expand...
Click to collapse
Thanks I will be try this when htc one x gets adb working recovery

[AT&T] Return to stock w/o computer with Mobile ODIN

Chainfire is a well-known developer on XDA. He has released numerous apps that are extremely useful. One of particular interest is Mobile ODIN. As the name of the app suggests, it flashes Samsung firmware onto your device. This is extremely helpful as it is often annoying to have to rely on your computer to flash back to stock. Furthermore, some of you may experience problems due to the USB port on your computer or phone. Also, this will not trip your flash counter.
USE WITH CAUTION. I AM NOT RESPONSIBLE IF YOU BRICK YOUR DEVICE OR YOUR CAT GOES ON FIRE
This will not flash/re-partition PIT, IBL/PBL, SBL & EFS. (No need to anyways...)
To flash via Moile ODIN, you must have ROOT
As a safety precaution, you must have 80% battery power!
1. Go to Chainfire's thread for Mobile ODIN (here) and download the following files:
MobileODINLite-v3.00.apk
MobileODIN_FlashKernel_I747-v2.0.apk
[OPTIONAL] If you're feeling generous, then go do Chainfire (he deserves it!) and yourself a favor and download the paid app via the Play Market. Pro can inject root in the stock firmware prior to flashing!
Note: If you downloaded Mobile ODIN Pro, you wont need to install MobileODIN_FlashKernel_I747-v2.0.apk as it will automatically download the corresponding apk for your device.
2. Once you've downloaded and installed the two apps, go download AT&T stock firmware. As this is a huge file, download it on strong WiFi connection.
(MD5: 66c6dfae34fd06c098f07537d19943c2) <- MD5Sum of the zip file
3. Extract zip and place tar.md5 in the root of your internal sdcard.
4. Open Mobile Odin > select Open File... > I747UCALEM_I747ATTALEM_I747UCALEM_HOME.tar.md5
It will not flash the following files in tar:
aboot.mbn
sbl2.mbn
sbl3.mbn
rpm.mbn
tz.mbn
5. Check wipe data and cache & dalvik cache* and flash (select Check for MD5 sum).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Note*: While it is not necessary to wipe data and cache & dalvik cache in the app, it is suggested as to prevent boot loops.

nice guide

Pardon my ignorance, but when you say "It will not flash the following files in tar:"... are those files not needed at all or do we need to add them manually?

I don't think so as you don't need to flash boot loaders. Also, repartition is not necessary as were not using hellraised roms (yet).I am not 100% sure tho.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

tamanaco said:
Pardon my ignorance, but when you say "It will not flash the following files in tar:"... are those files not needed at all or do we need to add them manually?
Click to expand...
Click to collapse
I believe it's a "safety" feature that the dev built in, because unless absolutely necessary, you generally don't want to mess with bootloaders, as those are the few items that can seriously f up (aka "Hard" brick) a phone if it goes bad. Also, it was found that some of the latest leaks from Samsung on various devices contained some shady bootloaders that noobs were indiscriminately flashing, so again, this helps save them from themselves

[TOOL][LINUX]COPERFIELD ROM MAKER create system.img for some devices

[TOOL][LINUX] COPERFIELD ROM MAKER v.0.0.2
DOWNLOAD TOOL
Suport:
Samsung Galaxy S
Samsung Galaxy Tab 7.0
Samsung Galaxy SII I9100
Samsung Galaxy SIII I9300
Samsung Galaxy NoteI N7000
Samsung Galaxy Tab 7.7 P6800
Google Nexus 7
1. Required LINUX and Root access on the device ...
2. Enable debug mode on the device and connect the USB to the PC.
3. Extract the file from the archive with the tool to check just in case the right of scripts and binaries folder /tools - all must be executed ...
4. From the root folder of the tool to run in a terminal script menu:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5. Configure the tool to claim 1 (necessary only once after the start of the tool):
6. Select the appropriate device, the program will create the device image of the system partition, download to PC and convert it to an image suitable for flashing Odin and put it in the out.
7. Select the package in the image archive .tar.md5 for flashing via Odin or fast boot (if necessary, may be placed in a folder out the rest of the ROM - the tool will pack them with the system image), enter the name new firmware and press Enter, the tool will create the firmware and display a report:
8. May be further packed in zip with maximum compression, to achieve the smallest size ...
9. The ability to create cache.img
10. Cache.img empty images in the folder empty (before flashing renamed cache.img)

the s2 and s3 system.img will be ext4 format ?

globula_neagra said:
the s2 and s3 system.img will be ext4 format ?
Click to expand...
Click to collapse
Of cause, kernels don't support different file systems...

Lol...I just started making script...here.But you finished it here perfectly with many devices supported .Good to see it.Let me see If I can anything better
---------- Post added at 10:13 AM ---------- Previous post was at 09:15 AM ----------
Just a little idea for you...If you make an empty data partition too,You can make sure that the rom does a factory reset while its been flashing

vijai2011 said:
Lol...I just started making script...here.But you finished it here perfectly with many devices supported .Good to see it.Let me see If I can anything better
Click to expand...
Click to collapse
Yes, I do not mind
Just a little idea for you...If you make an empty data partition too,You can make sure that the rom does a factory reset while its been flashing
Click to expand...
Click to collapse
I do not quite understand what you mean, but in order to reset a user's data is sufficient to add to the cache.img command wipe data...

as i9000 said:
Yes, I do not mind
I do not quite understand what you mean, but in order to reset a user's data is sufficient to add to the cache.img command wipe data...
Click to expand...
Click to collapse
I will pm you shortly with what I meant along with commands for you to understand it better
Sent from my GT-N7000 using xda app-developers app

Please can you help a noob - ROM seems extremely small
Hi I have been hunting for a tool to do a "complete" backup of my S3 so I can restore it in one go after playing with other ROMS and get back to Stock easily. So seeing this looked fantastic. I have run steps 1 , 4 and 10 .
The ROM i get is only 27,161 KB , and as the stock rom I flashed was over 1 gb I wonder if I have done something wrong and I am afraid to try flashing this with Odin . Especially when I did a NANDROID Backup from S3 Toolkit and this is 1.6gb .
Any advice would be well received .

plug_it_in said:
Hi I have been hunting for a tool to do a "complete" backup of my S3 so I can restore it in one go after playing with other ROMS and get back to Stock easily. So seeing this looked fantastic. I have run steps 1 , 4 and 10 .
The ROM i get is only 27,161 KB , and as the stock rom I flashed was over 1 gb I wonder if I have done something wrong and I am afraid to try flashing this with Odin . Especially when I did a NANDROID Backup from S3 Toolkit and this is 1.6gb .
Any advice would be well received .
Click to expand...
Click to collapse
You forgot step 5! configure tool, compile and install zlib and compile ext4_utils, and got empty image system.img...

is there a chance of a port to cygwin?

I like how the title says it supports any device and then the first post says it supports less than 10 devices.

Creating .tar.md5 will create images that increase binary counter ?
Edit:
Only with custom recovery

gianptune said:
I like how the title says it supports any device and then the first post says it supports less than 10 devices.
Click to expand...
Click to collapse
Sorry, it all my bad english, of cose isn't any but some...
I did chang it...

Is there any apps like this for W8??
Sent from my E16i using xda premium

Hi and thx for a great tool
1. Any chance when I run 6. that it stops when it is mounted and I can edit/add content in the output.img before it creates a system.img?
Would be nice to be able to edit before system.img
2. Possible to edit a factory system.img that I have on pc?
Thx for your time