You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi all...
would you please help me...as I`m very frustrated about flashing my new Galaxy Tab2 P5110..
After installing Heimdall on my Linux Ubuntu 12.4.; I dowloaded stock Rom for Tab 2 from samfirmware...unpacked it and got several files.
At terminal I tried to type following:
sudo heimdall flash - - cache cache.img - - recovery recovery.img - - param param.lfs - - hidden hidden.img - - secondary-boot Sbl.img - - etc.etc.
BUT what is correct:
boot.img --> kernel boot.img or primary-bootloader boot.img ????
system.img --> system system.img or factoryfs system.img ???
And more...after unpacking the stock firmware a got a "MLO"-file? how to handle MLO-files???
PLEASE would you support & explain.
Thanks a lot in advance.
Rgds,
Micha
The text was updated successfully, but these errors were encountered:
Github issues are not for customer support; they are for bug reports and feature requests. If you need help in future please use the contact form on the Glass Echidna website.
Nonetheless, you're after:
heimdall print-pit
Which will print a list of filenames and corresponding partition names. You can then flash using partition names directly. i.e. "--SBL" instead of "--secondary-bootloader".
Hi all...
would you please help me...as I`m very frustrated about flashing my new Galaxy Tab2 P5110..
After installing Heimdall on my Linux Ubuntu 12.4.; I dowloaded stock Rom for Tab 2 from samfirmware...unpacked it and got several files.
At terminal I tried to type following:
sudo heimdall flash - - cache cache.img - - recovery recovery.img - - param param.lfs - - hidden hidden.img - - secondary-boot Sbl.img - - etc.etc.
BUT what is correct:
boot.img --> kernel boot.img or primary-bootloader boot.img ????
system.img --> system system.img or factoryfs system.img ???
And more...after unpacking the stock firmware a got a "MLO"-file? how to handle MLO-files???
PLEASE would you support & explain.
Thanks a lot in advance.
Rgds,
Micha
The text was updated successfully, but these errors were encountered: