Can anyone help me how to make .tar file with only stock recovery.img inside flashable through odin. Im planning to install custom recovery and I want a backup procedure to revert it back to stock recovery instead of flashing the full stock rom.
Anyone please enlighten my confuse brain cells. I read some procedure for doing that stuff but I want the procedure which really came from galaxy note 4 forums. I was thinking different devices have own specific way of doing that.
macoX13 said:
Can anyone help me how to make .tar file with only stock recovery.img inside flashable through odin. Im planning to install custom recovery and I want a backup procedure to revert it back to stock recovery instead of flashing the full stock rom.
Anyone please enlighten my confuse brain cells. I read some procedure for doing that stuff but I want the procedure which really came from galaxy note 4 forums. I was thinking different devices have own specific way of doing that.
Click to expand...
Click to collapse
Its the same procedure for all devices
Rajada said:
Its the same procedure for all devices
Click to expand...
Click to collapse
thanks. can you link a particular thread or site for doing the that.
macoX13 said:
thanks. can you link a particular thread or site for doing the that.
Click to expand...
Click to collapse
if you are in linux, do this command in terminal:
tar -H ustar -c recovery.img > recovery.tar
if wou want a md5 file:
md5sum -t recovey.tar >> recovery.tar
mv recovery.tar recovery.tar.md5
if you are in windows install tar for windows
Rajada said:
if you are in linux, do this command in terminal:
tar -H ustar -c recovery.img > recovery.tar
if wou want a md5 file:
md5sum -t recovey.tar >> recovery.tar
mv recovery.tar recovery.tar.md5
if you are in windows install tar for windows
Click to expand...
Click to collapse
im in windows. is there a thread for doing that so i can follow the procedure.
Related
Does anybody have a link to original firmware for Samsung Mesmerize for odin? I made a booboo and I need those files to make my phone work again, sorry I wrote on fascinate forum, but theres no Mesmerize section yet AFAIK
Bump. I too, need some help.
This may or may not be what you are looking for. It won't let me post links but if you go to google and type Mesmerize_sys_dump.zip it is on Multiupload.com. I could not get ClockworkMod to work with my Mesmerize doing a system dump. I get "E: failed to verify whole-file signature AND E: signature verification failed". Can I use this Odin program to dump and restore?
frozn00 said:
This may or may not be what you are looking for. It won't let me post links but if you go to google and type Mesmerize_sys_dump.zip it is on Multiupload.com. I could not get ClockworkMod to work with my Mesmerize doing a system dump. I get "E: failed to verify whole-file signature AND E: signature verification failed". Can I use this Odin program to dump and restore?
Click to expand...
Click to collapse
That dump is not a ROM. Someone copied all the files from /system to their desktop and zipped them.
That is all this is.
It could very easily be *made* into a ROM as far as I understand it, but it does not contain kernel or recovery if that is what you are looking for.
If all you need are the apks/odexs, then downloading it and extracting it to your disk should allow you to push them to /system/apps via adb.
how to make recovery.bin odin file (assuming you have a stock recovery on your phone)
adb shell cat /dev/block/bml8 > /sdcard/recovery.bin
adb pull /sdcard/recovery.bin .
tar --format=ustar -cf recovery.tar recovery.bin
done
jt1134 said:
how to make recovery.bin odin file (assuming you have a stock recovery on your phone)
adb shell cat /dev/block/bml8 > /sdcard/recovery.bin
adb pull /sdcard/recovery.bin .
tar --format=ustar -cf recovery.tar recovery.bin
done
Click to expand...
Click to collapse
Help im a Captivate user, and not quite a neewb but i got a samsung MESMIRIZE and used ODIN 3 for captivate by mistake. its a natural thing to do when you have done so many captivates. now the mesmirize wont even come on! is there any hope at all?
scuubee said:
Help im a Captivate user, and not quite a neewb but i got a samsung MESMIRIZE and used ODIN 3 for captivate by mistake. its a natural thing to do when you have done so many captivates. now the mesmirize wont even come on! is there any hope at all?
Click to expand...
Click to collapse
Yes there is hope as long as you can find the mesmerize stock files for odin. Give this a try: http://forum.xda-developers.com/showthread.php?t=997359
i trying to install custom kernal on y but cant install is there any solution..plz help.me
solution is follow the instruction on the op of the kernel thread you are trying to install and always mount system before you flash anything
mangeshbhosale said:
i trying to install custom kernal on y but cant install is there any solution..plz help.me
Click to expand...
Click to collapse
you can try flashing the boot.img vie odin if that didn't do it then i don't know what will
the X Machine said:
you can try flashing the boot.img vie odin if that didn't do it then i don't know what will
Click to expand...
Click to collapse
you dont flash the boot.img via odin
you flash tar files via odin (which contain the boot.img) but it has to be an odin flashable tar file
if you only have the boot.img file you can flash it via cwm with the boot image installer zip file
All instructions on how to flash each kernel will be on the op of each kernel thread
marcussmith2626 said:
you dont flash the boot.img via odin
you flash tar files via odin (which contain the boot.img) but it has to be an odin flashable tar file
if you only have the boot.img file you can flash it via cwm with the boot image installer zip file
All instructions on how to flash each kernel will be on the op of each kernel thread
Click to expand...
Click to collapse
man anyone who uses odin will know that no need for this post
the X Machine said:
man anyone who uses odin will know that no need for this post
Click to expand...
Click to collapse
please remember not all people who read your posts will have used odin or have understanding of what boot.img is
marcussmith2626 said:
please remember not all people who read your posts will have used odin or have understanding of what boot.img is
Click to expand...
Click to collapse
yah i guess that not all people understand this i will try and explain things in the future any way thx you for explaining my answer for him :fingers-crossed:
If Help You!!
you can flash using this:
Download Kernel Update.zip
put the boot.img in sdcard
go reboot recovery (use cwm)
mount all system, data, cache,etc
go to 'install zip form sdcard'
select Kernel Update.zip
it finish installation go advance and reboot recovery is done!!
thnks guys for ur awesome reply..problem are solve now
[ Read the How To at the second post ]
Heya guys,
I just got yesterday my new Galaxy S5. I'm actually someone who is switching from the iPhone world to Galaxy.
I had a Note 2 in the past for some time and I'm sys admin so I'm a bit familiar with flashing and technical stuff.
Phone Information:
Model: SM-G900FD (or SM-G900MD?) (DuoS)
Country of Origin: United Arab Emirates
The phone came with stock rom 4.4.2. On the About Phone screen it shown SM-G900FD as model, directly from unboxing.
But when entering the Odin Mode it shows as product name SM-G900MD (which would fit the origin of course).
The first I did was downloading G900FDXXU1BNL9 (Android 5.0 SER (Russia)) and flash it with Odin. It works like a charm.
Then I tried dozen of different rooting methods, and failed every time, I spent I believe 10 hours on it already and flashed the phone about 30 times.
When flashing the stock rom, either the new G900FDXXU1BNL9 (5.0) or old G900FDXXU1ANF6 (4.4.2) it works like a charm.
The phone comes to life, Android is working fine.
As soon as I try to flash *any* other image, CWM, CF-Auto-Root or anything, it starts with "NAND Write Start!" and then in some seconds stops with "Complete(Write) operation failed." and the system ends up in a soft brick (Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.). I tried from every piece of software I could find many different versions. Different Odin versions. I tried Heimdall (Mac) and fastboot (Windows & Mac) without success. These two don't work at all with the phone. Heimdall can't correctly connect to the phone and download the PIT, I was reading its a bug with the newest bootloader of Samsung. And fastboot/adb can't see the phone, at all. While heimdall or odin can see the phone, so its not a driver issue that the OS can't recognize the phone.
I tried also different versions of CWM, CF-Auto-Root, either for SM-G900FD or SM-G900MD. No luck.
What I tried then was using towelroot, but it doesn't work with the newest Android. So I found a thread that stated to flash a old Kernel, which will give errors during booting but you can then root the phone with towelroot, and then flash the newest kernel back to the phone. I tried that, taking out the boot.img files from old and new firmware out and use a script to package them into .tar.md5 files and try to flash them with Odin. Even there, Odin reports FAIL! With the boot.img files from the stock images, which work fine flashing if I flash the entire stock image.
I tried also installing a old stock rom and try rooting it there with CWM/CF-Auto-Root. Same stuff, FAIL! flashing.
I'm a bit out of ideas right now. Does anyone ever encountered this? Or does have a hint on what could cause this problems?
Some threads I was reading (its a way more, but the list would be too long, I just add the most recent ones) and following:
[How to] Root for 4.4.2 and Flash rooted Stock Android 5.0 with KNOX 0x0?
http://forum.xda-developers.com/showpost.php?p=54745709&postcount=13
Galaxy S5 G900FD
http://forum.xda-developers.com/showpost.php?p=55994495&postcount=102
[Script][Tool] how to create a tar.md5 file from img For Odin
http://forum.xda-developers.com/showthread.php?t=2446269
Click to expand...
Click to collapse
Thank you very much for any assistance. I hope there is a possibility to root this phone
Cheers,
Sven
PS: My KNOX Warranty Void is already increased, so the warranty is killed already.
[HowTo]
Heya everyone again,
I just wanted to say that the last hope I had to try did work finally.
As every flashing of single partitions (eg. recovery.img, cache.img.ext4 or boot.img) failed, I did the following:
1. Take the image you want to have, in my case it is Android 5.0 SER (G900FDXXU1BNL9) stock image, and unpack it
2. Take the CWM, I used philz_touch_6.26.2-klte.tar.md5, and unpack it
3. Move the recovery.img file from the CWM to the image you want to flash and replace the original recovery.img
4. Package all together into one image.tar.md5 file, in my case it would be the stock image with the replaced CWM recovery.img
5. Flash it with Odin, it worked at me!
6. Proceed with the default rooting procedure of CWM (copy SuperSU, boot recovery, install ZIP)
You are done!
Steps to package the image.tar.md5 file (I used Mac OS X Yosmite):
$ COPYFILE_DISABLE=1 gtar -H ustar -c NON-HLOS.bin aboot.mbn boot.img cache.img.ext4 hidden.img.ext4 modem.bin recovery.img rpm.mbn sbl1.mbn sdi.mbn system.img.ext4 tz.mbn > image.tar
$ gmd5sum -t image.tar >> image.tar
$ mv image.tar image.tar.md5
Click to expand...
Click to collapse
The OS X tools (tar and md5) are NOT suitable! You should use brew install coreutils and use the gnu tar and md5sum commands. The OS X tar will produce a unusable tar file and Odin will crash, the OS X md5 produces a different output than md5sum (even when using md5 -r) and the verification will fail. When using Linux/Windows tar/md5sum tools all should be fine. If odin crashes when trying to flash it doesn't like how tar packaged up your file. Try a different tar version (better: operating different system).
I hope this helps people that encountered the same issue as me and they can now enjoy Android 5.0 with root on their SM-G900FD.
Cheers,
Sven
Well done!!
af2k said:
Heya everyone again,
I just wanted to say that the last hope I had to try did work finally.
As every flashing of single partitions (eg. recovery.img, cache.img.ext4 or boot.img) failed, I did the following:
1. Take the image you want to have, in my case it is Android 5.0 SER (G900FDXXU1BNL9) stock image, and unpack it
2. Take the CWM, I used philz_touch_6.26.2-klte.tar.md5, and unpack it
3. Move the recovery.img file from the CWM to the image you want to flash and replace the original recovery.img
4. Package all together into one image.tar.md5 file, in my case it would be the stock image with the replaced CWM recovery.img
5. Flash it with Odin, it worked at me!
6. Proceed with the default rooting procedure of CWM (copy SuperSU, boot recovery, install ZIP)
You are done!
Steps to package the image.tar.md5 file (I used Mac OS X Yosmite):
The OS X tools (tar and md5) are NOT suitable! You should use brew install coreutils and use the gnu tar and md5sum commands. The OS X tar will produce a unusable tar file and Odin will crash, the OS X md5 produces a different output than md5sum (even when using md5 -r) and the verification will fail. When using Linux/Windows tar/md5sum tools all should be fine. If odin crashes when trying to flash it doesn't like how tar packaged up your file. Try a different tar version (better: operating different system).
I hope this helps people that encountered the same issue as me and they can now enjoy Android 5.0 with root on their SM-G900FD.
Cheers,
Sven
Click to expand...
Click to collapse
Well done !!
i was looking for this root for my phone M-G900FD
until i read your thread ,so please upload the ready made file to root my phone as i am not experienced in this matter
waiting for your feed back
thanks
I had the same problem. I couldn't flash any other image whatever I did. And what I did was disabling reactivation lock within the settings. Worked since then.
free007 said:
please upload the ready made file
Click to expand...
Click to collapse
I will look into this tomorrow and provide a ready image for this.
AlwaysAndroid said:
what I did was disabling reactivation lock within the settings. Worked since then.
Click to expand...
Click to collapse
It didn't work out of the box at me. I checked right now within the settings and the reactivation lock is disabled already.
So we seem to face different problems. I still don't understand why flashing anything but an entire firmware is failing.
Well done indeed, would love to get my hands on your modded ROM, as in Dubai with new Duos just purchased today.
Any problems with Wifi passwords not being stored on re-boot?
af2k said:
Heya everyone again,
I just wanted to say that the last hope I had to try did work finally.
As every flashing of single partitions (eg. recovery.img, cache.img.ext4 or boot.img) failed, I did the following:
1. Take the image you want to have, in my case it is Android 5.0 SER (G900FDXXU1BNL9) stock image, and unpack it
2. Take the CWM, I used philz_touch_6.26.2-klte.tar.md5, and unpack it
3. Move the recovery.img file from the CWM to the image you want to flash and replace the original recovery.img
4. Package all together into one image.tar.md5 file, in my case it would be the stock image with the replaced CWM recovery.img
5. Flash it with Odin, it worked at me!
6. Proceed with the default rooting procedure of CWM (copy SuperSU, boot recovery, install ZIP)
You are done!
Steps to package the image.tar.md5 file (I used Mac OS X Yosmite):
The OS X tools (tar and md5) are NOT suitable! You should use brew install coreutils and use the gnu tar and md5sum commands. The OS X tar will produce a unusable tar file and Odin will crash, the OS X md5 produces a different output than md5sum (even when using md5 -r) and the verification will fail. When using Linux/Windows tar/md5sum tools all should be fine. If odin crashes when trying to flash it doesn't like how tar packaged up your file. Try a different tar version (better: operating different system).
I hope this helps people that encountered the same issue as me and they can now enjoy Android 5.0 with root on their SM-G900FD.
Cheers,
Sven
Click to expand...
Click to collapse
Looks like gtar needs to be installed separately.
$ brew install gnu-tar
This is what I was looking for...
I am not on OSX. Is there a possibility to get access to the modified image?
Hello guys
I hope you help me please
I want the official recovery. Img file
Located in the official rom file for samsung galaxy tab 4.7 wifi (smt230) kitkat 4.4.2
because yesterday i install root in my tablet
and the recovery its changed to openrecovery-twrp-2.8.0.1-degas
but i want to restore the original stock recovery
please help me guys
and i cant download the official rom (kitkat 4.4.2) because my internet is very slow
thanks for all of you
m
enough with the :crying: already !
okay @thisisapoorusernamechoice
has the stock recovery for the sm-t230nu posted, i'm thinking it might pass the smell test for the sm-t230
T230NUstockRecovery.zip
https://www.androidfilehost.com/?fid=95916177934553754
you will need to extract the recovery.img from the archive and tar the recovery.img for odin flashing
in terminal
tar -H ustar -c recovery.img > recovery.tar
m
thx bro its working
Hello, want to download this ROM, but I'm a bit confused because I always flash the new roms manually using a cwm recovery only. I'm not an expert in these tar md5 files.. Anyways im running a stock lollipop N9005XXUENC2 and my question is can I flash AryaMod using the cwm only and without downloading the 2 tar files the developer mentioned in the main thread? If not, can you tell me exactly what I should do using Odin? Thanks..
here you go!
MohamedBmb said:
Hello, want to download this ROM, but I'm a bit confused because I always flash the new roms manually using a cwm recovery only. I'm not an expert in these tar md5 files.. Anyways im running a stock lollipop N9005XXUENC2 and my question is can I flash AryaMod using the cwm only and without downloading the 2 tar files the developer mentioned in the main thread? If not, can you tell me exactly what I should do using Odin? Thanks..
Click to expand...
Click to collapse
the thing is,
1. Make all necessary backups, install ODIN and Samsung drivers in PC, also download the necessary files (BL, CP and ROM).
2. remove battery and insert after 10 secs.
3. Directly boot into Download Mode via key combo (after getting into Download Mode, Open ODIN and also connect phone to PC).
[download both files, select "BL tar file" in BL and "CP tar file" in CP in ODIN]
4. Flash the BL and CP from OP via ODIN (after selecting two files, click Start, it will automatically restart and it will show Success)
5. Now after the phone is ON (Success message), disconnect from PC and enter Recovery Mode and flash ROM.zip
6. Select your Options in Aroma and enjoy.
The Dev recommended to use TWRP and also I had TWRP from start. You can check in the ROM thread whether anyone is doing this via CWM.
Good luck.