Add language
I test samsung s2 i9100
Extract I9100XXLPQ.tar.md5 --> factoryfs.img (sgs2toext4.jar) --> factoryfs.ext4.img
Ubuntu
...
mkdir /mnt/system
mount factoryfs.ext4.img /mnt/system
cp framework/*.apk /mnt/system/framework/ <---Language change here
cp app/*.apk /mnt/system/app/ <---Language change here
tar cvf factoryfs.img /mnt/system <---suspect here (!)
e2fsck factoryfs.img <--- can abort
umount /mnt/system
step1:
tar cvpf factoryfs.tar factoryfs.img
md5sum -t factoryfs.tar >> factoryfs.tar
mv factoryfs.tar factoryfs.tar.md5
factoryfs.tar.md5 flash with odin failed
step2:
tar -H ustar -c boot.bin cache.img factoryfs.img hidden.img modem.bin param.lfs Sbl.bin zImage > your_odin_package.tar
md5sum -t your_odin_package.tar >> your_odin_package.tar
mv your_odin_package.tar your_odin_package.tar.md5
your_odin_package.tar.md5 flash with odin
boot.bin ok
cache.img ok
factoryfs.img <--- failed here
....stop here.....
please, help me!
Thanks!
thanhlapvn said:
Add language
I test samsung s2 i9100
Extract I9100XXLPQ.tar.md5 --> factoryfs.img (sgs2toext4.jar) --> factoryfs.ext4.img
Ubuntu
...
mkdir /mnt/system
mount factoryfs.ext4.img /mnt/system
cp framework/*.apk /mnt/system/framework/ <---Language change here
cp app/*.apk /mnt/system/app/ <---Language change here
tar cvf factoryfs.img /mnt/system <---suspect here (!)
e2fsck factoryfs.img <--- can abort
umount /mnt/system
step1:
tar cvpf factoryfs.tar factoryfs.img
md5sum -t factoryfs.tar >> factoryfs.tar
mv factoryfs.tar factoryfs.tar.md5
factoryfs.tar.md5 flash with odin failed
step2:
tar -H ustar -c boot.bin cache.img factoryfs.img hidden.img modem.bin param.lfs Sbl.bin zImage > your_odin_package.tar
md5sum -t your_odin_package.tar >> your_odin_package.tar
mv your_odin_package.tar your_odin_package.tar.md5
your_odin_package.tar.md5 flash with odin
boot.bin ok
cache.img ok
factoryfs.img <--- failed here
....stop here.....
please, help me!
Thanks!
Click to expand...
Click to collapse
I think tar cvf factoryfs.image is basically just a tar file not a repacked ext4.image file so i think you should use the command or a tool to repack the image file and that you should continue step 1 or 2 with the repacked file, so what I am suggesting is you dont need these two lines
tar cvf factoryfs.img /mnt/system <---suspect here (!)
e2fsck factoryfs.img <--- can abort
after unmount, repack it in whatever way you like ,then proceed with step 1 or 2 with the repacked file.
Edit:And by repacking I dont mean compressing into a tar again, there maybe tools available for repacking.
Hmm I been meaning to ask you but did you try pushing both apk via a signed zip file through the stock recovery?
Sent from my GT-I9100 using xda app-developers app
king_below_my_lord said:
Hmm I been meaning to ask you but did you try pushing both apk via a signed zip file through the stock recovery?
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
I create update zip (cwm) change language ok but i like build md5 flash via odin (no need recovery, no need root, no need update ver same ver pack update...)
thanhlapvn said:
I create update zip (cwm) change language ok but i like build md5 flash via odin (no need recovery, no need root, no need update ver same ver pack update...)
Click to expand...
Click to collapse
Lol, yeah to each his own preferences. But I always prefer the shortest way, where minimal action is needed, and with root I can make most changes from inside the OS, but I am intrigued which language did you insert?
Edit :Since the matter is over add Solved in title.
Sent from my GT-I9100 using xda app-developers app
Hey everybody, I spent the last two days reading up and down the forum and simply cant find an solution to recover my soft bricked SCH-545.
I was on a MK2 firmware. I rooted my phone using the saferootmethod which worked fine. Than I wanted to flash Hiperdrive RLS 15 on my device using safestrap. Here the flash ran all the way through but my phone simply wouldnt boot anymore (boot freeze). At this point I still could go into safestrap recovery mode. So I decided to select another rom. Unfortunatelly I dont know anymore which one. Stupid me! The end of the story, it didnt work "Firmware upgrade encountred an issue. Please select recovery mode in Kies and try again". I cant go into recovery mode anymore and Kies wont detect the device. I only can go into download mode. This works still fine.
So I decided to follow this threat (http://forum.xda-developers.com/showthread.php?t=2578209) in order to recover the device. I tried both, full-wipe and no-wipe / with and without pit file. I also tried different USB cable (original samsung and other) and different USB hubs. But I always get following error:
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_I545VRUEMK2_I545VZWEMK2_1937946_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> persdata.img.ext4
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The next end last attempt was to download the stock firmware from sammobile.com (I545VRUEMJ7, I545VRUEMK2, I545VRUFNC5). But also the same error. I know now that you cannot downgrade but I still gave it a shot thinking that I might was mistaken with the built number MK2. But when I bought the phone it came with 4.2.2 and I know that I upgraded it to 4.3 at some point later.
Also, In the downloading mode, in the top left corner it says:
Write protection: enabled
eMMC Burst Mode: enabled
Now I simply dont know what I can do anymore. Is there somebody else you experiences / experienced similar issues or somebody who could point me in the right direction. Any help would be greatly appreciated. Thanks a thousand times!!!
BabelDev said:
Hey everybody, I spent the last two days reading up and down the forum and simply cant find an solution to recover my soft bricked SCH-545.
I was on a MK2 firmware. I rooted my phone using the saferootmethod which worked fine. Than I wanted to flash Hiperdrive RLS 15 on my device using safestrap. Here the flash ran all the way through but my phone simply wouldnt boot anymore (boot freeze). At this point I still could go into safestrap recovery mode. So I decided to select another rom. Unfortunatelly I dont know anymore which one. Stupid me! The end of the story, it didnt work "Firmware upgrade encountred an issue. Please select recovery mode in Kies and try again". I cant go into recovery mode anymore and Kies wont detect the device. I only can go into download mode. This works still fine.
So I decided to follow this threat (http://forum.xda-developers.com/showthread.php?t=2578209) in order to recover the device. I tried both, full-wipe and no-wipe / with and without pit file. I also tried different USB cable (original samsung and other) and different USB hubs. But I always get following error:
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_I545VRUEMK2_I545VZWEMK2_1937946_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> persdata.img.ext4
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The next end last attempt was to download the stock firmware from sammobile.com (I545VRUEMJ7, I545VRUEMK2, I545VRUFNC5). But also the same error. I know now that you cannot downgrade but I still gave it a shot thinking that I might was mistaken with the built number MK2. But when I bought the phone it came with 4.2.2 and I know that I upgraded it to 4.3 at some point later.
Also, In the downloading mode, in the top left corner it says:
Write protection: enabled
eMMC Burst Mode: enabled
Now I simply dont know what I can do anymore. Is there somebody else you experiences / experienced similar issues or somebody who could point me in the right direction. Any help would be greatly appreciated. Thanks a thousand times!!!
Click to expand...
Click to collapse
Well, this is different. Normally, the "Complete (Write) operation failed." has some info displayed on the phone that says why it failed.
I'd start with installing Samsung Kies and trying to recover using that.
k1mu said:
Well, this is different. Normally, the "Complete (Write) operation failed." has some info displayed on the phone that says why it failed.
I'd start with installing Samsung Kies and trying to recover using that.
Click to expand...
Click to collapse
Hi thank for your quick response. I get this message on Odin. In the screen of the device you only see a progress bar that stops. Thats It.
I also tried installing / reinstalling Kies and the samsung driver but it wont detect my device. So it seems that this is not an option either.
BabelDev said:
Hi thank for your quick response. I get this message on Odin. In the screen of the device you only see a progress bar that stops. Thats It.
I also tried installing / reinstalling Kies and the samsung driver but it wont detect my device. So it seems that this is not an option either.
Click to expand...
Click to collapse
PS: Odin detects the device but Kies does not.
BabelDev said:
Hey everybody, I spent the last two days reading up and down the forum and simply cant find an solution to recover my soft bricked SCH-545.
I was on a MK2 firmware. I rooted my phone using the saferootmethod which worked fine. Than I wanted to flash Hiperdrive RLS 15 on my device using safestrap. Here the flash ran all the way through but my phone simply wouldnt boot anymore (boot freeze). At this point I still could go into safestrap recovery mode. So I decided to select another rom. Unfortunatelly I dont know anymore which one. Stupid me! The end of the story, it didnt work "Firmware upgrade encountred an issue. Please select recovery mode in Kies and try again". I cant go into recovery mode anymore and Kies wont detect the device. I only can go into download mode. This works still fine.
So I decided to follow this threat (http://forum.xda-developers.com/showthread.php?t=2578209) in order to recover the device. I tried both, full-wipe and no-wipe / with and without pit file. I also tried different USB cable (original samsung and other) and different USB hubs. But I always get following error:
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_I545VRUEMK2_I545VZWEMK2_1937946_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> persdata.img.ext4
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The next end last attempt was to download the stock firmware from sammobile.com (I545VRUEMJ7, I545VRUEMK2, I545VRUFNC5). But also the same error. I know now that you cannot downgrade but I still gave it a shot thinking that I might was mistaken with the built number MK2. But when I bought the phone it came with 4.2.2 and I know that I upgraded it to 4.3 at some point later.
Also, In the downloading mode, in the top left corner it says:
Write protection: enabled
eMMC Burst Mode: enabled
Now I simply dont know what I can do anymore. Is there somebody else you experiences / experienced similar issues or somebody who could point me in the right direction. Any help would be greatly appreciated. Thanks a thousand times!!!
Click to expand...
Click to collapse
This is what you should do;
1. First boot in to linux (google "dual-boot linux and windows 7" or "boot linux live cd" if you dont know how to get linux)
2. Download this file and this file
3. Next, open terminal emulator (google "how to open terminal emulator in linux" if you dont know how to open terminal emulator.) and then copy and paste the following into terminal:
Code:
find . -name "Heimdall1.4c2debian.sh" -exec cp {} ~/ \;
find ~/ -name "Heimdall1.4c2debian.sh" -type f -exec chmod 755 {} \;
sh ~/Heimdall1.4c2debian.sh
4. Type in your password (dont worry if it looks like no characters are being entered when you type your password, this is normal hit enter after your done typing your password) if all went well heimdall-frontend should open up.
5. In the "flash" tab under "PIT" select browse and find the pit file i had you download in step 2.
6. Under "Partitions (Files)" select add then change the Partition type to SYSTEM and choose the system.img.ext4 file that you can get from the ALL_I545VRUEMK2_I545VZWEMK2_1937946_REV06_user_low_ship_MULTI_CERT.tar.md5 you downloaded earlier (rename the end of the file from tar.md5 to .tar then extract it) then click "Add" and then "Remove"
7. Go over to the "Utilities" tab and select "detect" then go back to the flash tab and select "start". If all goes well this should recover your device.
Sorry about telling you to google this or that, but if I had to type out the whole process I think I would've just given up typing a response at all.
Code:
find . -name "Heimdall1.4c2debian.sh" -exec cp {} ~/ \;
find ~/ -name "Heimdall1.4c2debian.sh" -type f -exec chmod 755 {} \;
sh ~/Heimdall1.4c2debian.sh
Hey and thank you. I am installing Ubuntu right now. Just for clarity, you want me to copy and paste the exact code including ";" or do I need to modify it in any way?
I will keep the forum updated on my "progress".
Thank you guys a thousand times.
So I installed Ubuntu via VMware on my OSX, copied all the files on my virtual machine and opened the terminal. So far, so good.
But when I entered the commands I get following error "missing argument to `-exec'" (see screenshot).
Help would be greatly appreciated. Thank you!
BabelDev said:
So I installed Ubuntu via VMware on my OSX, copied all the files on my virtual machine and opened the terminal. So far, so good.
But when I entered the commands I get following error "missing argument to `-exec'" (see screenshot).
Help would be greatly appreciated. Thank you!
Click to expand...
Click to collapse
you removed both semi-colons. Literally copy and paste what I typed.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Surge1223 said:
you removed both semi-colons. Literally copy and paste what I typed.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I did that to but receive an "Syntax error: redirection unexpected"
Thanks for you quick response!!
BabelDev said:
I did that to but receive an "Syntax error: redirection unexpected"
Thanks for you quick response!!
Click to expand...
Click to collapse
try typing this in terminal:
Code:
bash ~/Heimdall1.4c2debian.sh
and if that doesnt work try:
Code:
cd ~/
chmod 777 Heimdall1.4c2debian.sh
./Heimdall1.4c2debian.sh
Sent from my SCH-I545 using XDA Premium 4 mobile app
Surge1223 said:
try typing this in terminal:
Code:
bash ~/Heimdall1.4c2debian.sh
and if that doesnt work try:
Code:
cd ~/
chmod 777 Heimdall1.4c2debian.sh
./Heimdall1.4c2debian.sh
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried both commands now and both seem to work. I type in the passwords and it runs. Than it asks me a second time for the pass and than I get an "Authentication failure". Tried it multiple times with both commands, always the same (see screenshot)
If it doesnt work with ubuntu, do you think I just should tried it with the OSX version of Heimdall?
Thank you!
BabelDev said:
I tried both commands now and both seem to work. I type in the passwords and it runs. Than it asks me a second time for the pass and than I get an "Authentication failure". Tried it multiple times with both commands, always the same (see screenshot)
If it doesnt work with ubuntu, do you think I just should tried it with the OSX version of Heimdall?
Thank you!
Click to expand...
Click to collapse
ok open terminal and type this in, when it asks for the password just hit enter, dont actually type a password.
Code:
sudo su
then finally copy and paste the below:
Code:
find . -name "Heimdall1.4c2debian.sh" -exec cp {} ~/ \;
find ~/ -name "Heimdall1.4c2debian.sh" -type f -exec chmod 755 {} \;
bash ~/Heimdall1.4c2debian.sh
you can replace the last line with the below if it the above doesnt work.
Code:
cd ~/
chmod 777 Heimdall1.4c2debian.sh
./Heimdall1.4c2debian.sh
Thanks again surge1223. This time Heimdall fronted started but after following your instructions I get a "Failed to begin session!". I attached again a screenshot. Any leads on went wrong? Thank you.
PS: Here the full status description from Heimdall:
Heimdall v1.4.1
Copyright (c) 2010-2014 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
ERROR: Failed to begin session!
Releasing device interface...
Re-attaching kernel driver...
BabelDev said:
Thanks again surge1223. This time Heimdall fronted started but after following your instructions I get a "Failed to begin session!". I attached again a screenshot. Any leads on went wrong? Thank you.
Click to expand...
Click to collapse
connect the phone to a different usb port, then type this in terminal hit enter when it asks for pass
Code:
sudo su
then:
Code:
sudo apt-get update && sudo apt-get upgrade
if you're not using a live cd then I would recommend rebooting here but if you are using a live cd dont reboot then in the same terminal window type the following (if you didnt reboot)
Code:
heimdall-frontend
and try again
Sent from my SCH-I545 using XDA Premium 4 mobile app
Surge1223 said:
connect the phone to a different usb port, then type this in terminal hit enter when it asks for pass
Code:
sudo su
then:
Code:
sudo apt-get update && sudo apt-get upgrade
if you're not using a live cd then I would recommend rebooting here but if you are using a live cd dont reboot then in the same terminal window type the following (if you didnt reboot)
Code:
heimdall-frontend
and try again
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I followed your instructions and rebooted ubuntu. Afterwards I started heimdall-fronted again and followed the your initial instructions. I made sure that my S4 is in download mode.
Now I receive follwoing error however:
Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: -3
BabelDev said:
Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: -3
Click to expand...
Click to collapse
I meanwhile installed libusb on ubuntu using following commands:
sudo apt-get install libusb-dev
sudo bash -c "apt-get update && apt-get upgrade"
After rebooting I still get the same error on Heimdall as before
Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: -3
Any leads on whats going on? Thanks!
BabelDev said:
I followed your instructions and rebooted ubuntu. Afterwards I started heimdall-fronted again and followed the your initial instructions. I made sure that my S4 is in download mode.
Now I receive follwoing error however:
Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: -3
Click to expand...
Click to collapse
ok now in terminal, type the following and hit enter when it asks for pass
Code:
sudo su
Then copy and paste all of the below into terminal and reboot once they're done installing and try again (we're almost there!)
Code:
sudo apt-get update && sudo apt-get upgrade && sudo dpkg --configure -a && sudo dpkg --add-architecture i386 ; sudo apt-get update ; sudo apt-get --yes --force-yes install build-essential pkg-config zlib1g-dev libusb-dev libqt4-dev qt4-qmake autoconf libtool libusb-1.0-0-dev debhelper libusb-1.0-0 libgcc1 libc-bin tzdata libc-bin libdb1-compat initscripts libdb1-compat locales psmisc git-core ia32-libs libusb-ocaml libhpmud0 libdevice-usb-perl libusb-0.1-4 libusb-1.0-0-dev libusb-dev libusb-1.0-0 libusb++0.1-4c2 libusbprog-dev libusb++-dev libusbtc08-1 libusbmuxd-dev libusbmuxd1 libusbprog0
Sent from my SCH-I545 using XDA Premium 4 mobile app
Surge1223 said:
ok now in terminal, type the following and hit enter when it asks for pass
Code:
sudo su
Then copy and paste all of the below into terminal and reboot once they're done installing and try again (we're almost there!)
Code:
sudo apt-get update && sudo apt-get upgrade && sudo dpkg --configure -a && sudo dpkg --add-architecture i386 ; sudo apt-get update ; sudo apt-get --yes --force-yes install build-essential pkg-config zlib1g-dev libusb-dev libqt4-dev qt4-qmake autoconf libtool libusb-1.0-0-dev debhelper libusb-1.0-0 libgcc1 libc-bin tzdata libc-bin libdb1-compat initscripts libdb1-compat locales psmisc git-core ia32-libs libusb-ocaml libhpmud0 libdevice-usb-perl libusb-0.1-4 libusb-1.0-0-dev libusb-dev libusb-1.0-0 libusb++0.1-4c2 libusbprog-dev libusb++-dev libusbtc08-1 libusbmuxd-dev libusbmuxd1 libusbprog0
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you. I followed your instruction but it seems that the "package is missing, has been obsoleted, or is only available from another source". I also attached a screenshot.
I tried to flash using heimdall again anyway but received the same libusb error.
Thanks once again. I followed your last instructions but received following notice "package is missing, has been obsoleted, or is only available from another source". I rebooted and tried the to flash using heimdall again but received the same libusb error. I also attached a screenshot.
Greetings
I have been trying to modify a stock image, and here is what I have done so far:
I found this link, and followed it in this manner: @ubuntu:~/expermental_stock$ umkbootimg boot.img
unmkbootimg version 1.2 - Mikael Q Kuisma <[email protected]>
Kernel size 8262680
Kernel address 0x8000
Ramdisk size 1064985
Ramdisk address 0x2000000
Secondary size 0
Secondary address 0xf00000
Kernel tags address 0x1e00000
Flash page size 2048
Board name is ""
Command line "console=null androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 ehci-hcd.park=3"
*** WARNING ****
This image is built using NON-standard mkbootimg!
OFF_KERNEL_ADDR is 0xFE208100
OFF_RAMDISK_ADDR is 0x00200100
OFF_SECOND_ADDR is 0xFF100100
Please modify mkbootimg.c using the above values to build your image.
****************
Extracting kernel to file zImage ...
Extracting root filesystem to file initramfs.cpio.gz ...
All done.
---------------
To recompile this image, use:
mkbootimg --kernel zImage --ramdisk initramfs.cpio.gz --base 0x1dfff00 --cmdline 'console=null androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 ehci-hcd.park=3' -o new_boot.img
---------------
I copied the original zImage to a backup file:
I copied the original zImage to a backup file: @ubuntu:~/expermental_stock$ cp zImage backup_zImage
I moved my new zImage over: @ubuntu:~/expermental_stock$ cp ~/androidkernel3/arch/arm/boot/zImage .
@ubuntu:~/expermental_stock$ ls
aboot.mbn cache.img.ext4 modem.bin NON-HLOS.bin sbl1.mbn system.img.ext4
backup_zImage info N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_HOME.tar.md5 recovery.img sdi.mbn tz.mbn
boot.img initramfs.cpio.gz N900PVPUCNC5_N900PSPTCNC5_SPR.zip rpm.mbn SS_DL.dll zImage
ran the command again to "recompile" I assume this uses the new zImage @ubuntu:~/expermental_stock$ mkbootimg --kernel zImage --ramdisk initramfs.cpio.gz --base 0x1dfff00 --cmdline 'console=null androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 ehci-hcd.park=3' -o new_boot.img
[email protected]:~/expermental_stock$ ls
aboot.mbn cache.img.ext4 modem.bin new_boot.img rpm.mbn SS_DL.dll zImage
backup_zImage info N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_HOME.tar.md5 NON-HLOS.bin sbl1.mbn system.img.ext4
boot.img initramfs.cpio.gz N900PVPUCNC5_N900PSPTCNC5_SPR.zip recovery.img sdi.mbn tz.mbn @ubuntu:~/expermental_stock$ rm N900PVPUCNC5_N900PSPTCNC5_SPR.zip @ubuntu:~/expermental_stock$ mv backup_zImage /tmp/ @ubuntu:~/expermental_stock$ ls
aboot.mbn info N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_HOME.tar.md5 recovery.img sdi.mbn tz.mbn
boot.img initramfs.cpio.gz new_boot.img rpm.mbn SS_DL.dll zImage
cache.img.ext4 modem.bin NON-HLOS.bin sbl1.mbn system.img.ext4 @ubuntu:~/expermental_stock$ mv boot.img /tmp/
Renamed the new_boot.img to original name @ubuntu:~/expermental_stock$ mv new_boot.img boot.img @ubuntu:~/expermental_stock$
Oh I also moved the original files to /tmp @ubuntu:~/expermental_stock$ mv backup_zImage /tmp/ @ubuntu:~/expermental_stock$ mv boot.img /tmp/
[email protected]:~/expermental_stock$ ls
aboot.mbn info N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_HOME.tar.md5 rpm.mbn SS_DL.dll zImage
boot.img initramfs.cpio.gz NON-HLOS.bin sbl1.mbn system.img.ext4
cache.img.ext4 modem.bin recovery.img sdi.mbn tz.mbn
moved the original tar file to another directory
[email protected]:~/expermental_stock$ mv N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_HOME.tar.md5 /tmp/ @ubuntu:~/expermental_stock$
Then I used this link to create a tar.md5 file, and I ziped the whole thing again : @ubuntu:~/expermental_stock$ tar -H ustar -c * > N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_HOME.tar @ubuntu:~/expermental_stock$ md5sum -t N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_HOME.tar >> N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_HOME.tar @ubuntu:~/expermental_stock$ mv N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_HOME.tar N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_HOME.tar.md5 @ubuntu:~/expermental_stock$zip -r N900PVPUCNC5_N900PSPTCNC5_SPR *
I moved the zip file to a location I have used to to flash other images before. I get the unable to mount error, which I got before and was able to flash before. I have twrp on my phone. I also get the error "unable to open zip file".
Do you see anything wrong with what I have done?
I've tried multiple methods, but I can't seem to get the pre-rooted ROM to flash properly, however, the completely stock ROM flashes just fine, so I'm wondering what in the heck I'm doing wrong.
Here's what I've done after I add the su binaries and deodexed:
-- make_ext4fs WITH -s
-- make_ext4fs WITHOUT -s
-- make_ext4fs WITHOUT -s THEN img2simg
-- This method
After those, I tried these:
-- tar -H ustar -c sboot.bin cm.bin boot.img recovery.img system.img cache.img modem.bin >> Flash.tar
-- tar cfx Flash.tar sboot.bin cm.bin boot.img recovery.img system.img cache.img modem.bin
-- Using 7zip to add the file to a pre-existing tar
-- Renaming system.img to system.img.ext4 (Didn't fail, but it just hanged at recovery at the top and system.img.ext4 as the last log entry)
However, every time it gets to the system.img, it fails, saying "Complete(Write) operation failed."
Is there any fix to this? Or is my phone not accepting a custom system.img?
I've used both Odin3 v3.10.7 and v1.85
Thanks in advance!
I cant Flash or using odin, any help?
The log odin
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
I want try this but dont work, i can't make work then adb....
Go to recovery, (If PhilZ, turn the screen off by swiping to the left - to prevent burn-ins.. )
Open adb shell,
umount /data
umount /cache
umount /system
umount /preload
dd if=/dev/zero of=/dev/block/mmcblk0p8 bs=16M
dd if=/dev/zero of=/dev/block/mmcblk0p9 bs=16M
dd if=/dev/zero of=/dev/block/mmcblk0p10 bs=16M
dd if=/dev/zero of=/dev/block/mmcblk0p12 bs=16M
sync
And reboot to download mode from the reboot menu, use ODIN to flash stock firmware.
After flashing stock firmware, it'll automatically enter recovery to apply CSC.
After recovery exits, be quick and enter recovery manually yourself.
It'll complain it can't mount /cache and /data. Ignore and do a factory reset, and reboot.
Don't flash anything custom until you get stock firmware running perfectly.
0p8 = cache
0p9 = system
0p10 = preload
0p12 = data (will take tens of minutes)
At the end of each dd command, it will complain that no more space is available. That's normal, however if you got some another error, that means your nand is hardwarelically corrupted..
Are you trying to flash the latest stock ROM from sammobile.com, updato.com, or samsung-firmware.org?
Tried using the original Samsung USB cable?
The phone is in stock recovery mode so you can only sideload, which is useless.
You need to be in download mode to flash but you get pit errors so can't flash anything, you need to have twrp to have full adb.
I'm afraid your phone is F00ked.
As a last resort, try flashing the stock recovery on its own via odin & download mode. If it doesn't take then the phone is good for keeping your shelf dust free..