Why can't sgs2toext4.jar convert system.img to ext4 image of ACE 2 Jelly Bean firmwares?
I first thought it was okay but mounting the image with DiskInternals LinuxReader gives files in wrong size.
I even checked the md5 hash with Odin and it's successful, with both NEE and DBT firmware.
The same process works for other devices firmware.
I tried both 7zip and WinRAR to unpack system.img from the tar archive.
The process gets in a loop
HELLO
..........
AM ISAAC VYSIONS HERE TO HELP
EMAIL: [email protected]
..........
.....................................................................................
TO GET STARTED DOWNLOAD FLASH FIRMWARE----> drdevs.com/devs/FXZ-files/XT907%20%28Droid%20RAZR%20M%29/VZW_XT907_4.4.2-KDA20.62-10.1_CFC_1FF.xml.zip (COPY TO URL)
AND FOLLOW ME CAREFULLY....
I HAVE TWO WAYS OF SHOWING YOU HOW TO FIX THIS.. A & B
I PREFER OPTION B MOST
............
OPTION A
.............
...............................................................................................
1. Extract the zip file contents to a temporary location on your PC where fastboot
command works and with CMD (command promt)
2. Kindly put ur device in Fastboot mode by pressing power and down volume key..
3... when successfull in Fastboot Mode
connect ur device to PC and Type this
In a terminal command prompt, browse to where the extracted files are located
OR
*Put Extrated file in where fastboot files is located(easy)
Then type the following commands (one at a time)
...................................................................
fastboot -w
fastboot flash partition gpt.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl2 sbl2.mbn
fastboot flash sbl3 sbl3.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot erase tombstones
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot continue
DONE... :good:
..................................................
IF U GET ERROR ----> target reported maximum download size OR Data size exceed download buffer
FIX WITH Option B
.............................
OPTION B
..............................
DOWNLOAD THIS FILE FROM MY GOOGLE DRIVE.------> drive.google.com/file/d/0B9aFpZeQTZh-VVEtaDdnUDZXYjg/view?usp=sharing (COPY TO URL)
And replace it with the one in the extracted firmware folder
then download RSD LITE ----->.rsdlite.com (COPY TO URL)
1. INSTALL IT ON UR PC AND PUT UR DEVICE IN FASTBOOT MODE ..
2. MAKE SURE IT SHOWS UP IN THE RSD SOFTWARE AS FASTBOOT DEVICE
3. CLICK THE BROWSE FOLDER BUTTON AND BROWSE INTO THE EXTRACTED FIMWARE FOLDER
4. THEN SECLECT THE FILE NAMED .......: VZW_XT907_4.1.2-9.8.1Q-66_1FF.xml
5. CLICK THE START BUTTON
It keeps a little bt longer when it get to flash system so be patient
AND
WAIT TILL IT FINISH THEN VOALA .....:crying:
LIKE MAGIC
NB: EMAIL ME OR POST IF U DONT UDERSTAND ANY THING..
IT WORKS PERFECTLY
ALSO WORKS WITH
VALIDATION FAIL
STUCK AT BOOT
STUCK AT FASTBOOT
STUCK AT MOTO EYE
DIM SCREEN CANT TURN ON..
Hi guys
My Find7 using LVM and Paranoid ROM had rebooting issues (long time issues). I tried to 'fix file system' and it threw an 'encryption failed ' screen on ROM boot. That happened a few tims so I went into TWRP and attempted NANDROID restore.
That failed with error 225. I cannot after removing LVM install ColorOS 1.2.1i or 1.2.7.i . TWRP says it cannot mount '/data'. ColorOS stock recovery fails too.
Now I can't reflash through Fastboot TWRP
I think I recall fixing this by flashing Clockwork but I can't find a version for the Find 7.
Any help?
Thanks so much!
okay as soon as I published, I had moved through mass mounting coloros 1.2.7i using coloros stock recovery
I flashed and it worked.
Hours of failure prior to this.
Thanks, myself.
For anyone who can't flash recovery and is stuck do this
install fastboot. Google it.
download colorOS 1.2.7i and extract the zip to say the folder FIX
download this oppo find7 stock recovery to FIX http://s000.tinyupload.com/index.php?file_id=00219433653419942379 or use TWRP in its place (change the recovery.img name to whatever your twrp file is called.)
hold shift + right click (windows) in FIX and click open command prompt here
copy each line below and right click and paste line by line
Fastboot oem unlock
flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash aboot emmc_appsboot.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash oppostanvbk static_nvbk.bin
fastboot flash LOGO logo.bin
fastboot flash reserve4 reserve4.img
Hi,
I am currently running Cyanogen OS 13.0 and I have not managed to update via OTA and TWRP. After TWRP-Update the system just hangs on boot. OTA just does not do the update after reboot. I just keeps downloading the OTA-Update again and again which eats my data plan, unless I notice and stop it. I am looking for a clear instruction on how to flash the newest version directly via cable. I could not find one. Alternatively I would be happy if someone could show me a way to stop the repeating downloads of the latest OTA-version.
Thanks!
basically you unzip the flashtool zip and do
Code:
fastboot flash splash splash.img
fastboot flash modem NON-HLOS.bin
fastboot flash aboot emmc_appsboot.mbn
fastboot flash hyp hyp.mbn
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash tz tz.mbn
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash system system.img
if you want to keep data skip userdata (but clear dalvik cache in twrp)
if you want to keep twrp do not flash recovery
Dior DNA said:
basically you unzip the flashtool zip and do
Code:
fastboot flash splash splash.img[/QUOTE]
It worked thanks. Unfortunately I am back to bootloops after flashing supersu.v2.46 via twrpThis worked with previous versions.
Any idea how to do this correctly?
Click to expand...
Click to collapse
sambahb said:
It worked thanks. Unfortunately I am back to bootloops after flashing supersu.v2.46 via twrp. This worked with previous versions.
Any idea how to do this correctly?
Click to expand...
Click to collapse
You need to root MM with system less SuperSU ZIP version, I believe v2.65 onwards (v2.76 may be latest, you need to check). And each time you flash kernel (aka boot.img) again you need to root.
Dior DNA said:
You need to root MM with system less SuperSU ZIP version, I believe v2.65 onwards (v2.76 may be latest, you need to check). And each time you flash kernel (aka boot.img) again you need to root.
Click to expand...
Click to collapse
Its better to use super su 2.76 because it has boot image patcher.
Sent from my Wileyfox Swift using XDA-Developers mobile app
Hi, here my current situation:
- I have a SM-G960F
- OEM is locked
- I'm in a bootloop
- I downloaded G960FXXSBETH2_G960FODXBETG8_DTM.zip from sammobile
- in this zip, there are boot.img, system.img, recovery.img, ...
- I am able to flash all of them except for system.img via, e.g., heimdall flash --BOOT boot.img
- for heimdall flash --SYSTEM system.img I get "Custom Binary(SYSTEM) Blocked by OEM Lock"
My history:
- I had lineageos 15.?? installed and backed it up via TWRP
- I wanted to install lineageos for microg 17.?? via dirty install (with signature faking)
- The migration.zip from the lineage.microg.org worked
- The actual build from them did not work because of wrong vendor binaries
- I guess, the migration.zip enabled OEM and that's where I am
Do you have any idea why the system.img cannot be flashed while the others can? It should be the original samsung firmware. Do I need an older firmware, e.g., Android 8?
Can you link a good explanation of the versioning issues with bootloaders? Am I able to restore my backup of 15.?? if I successfully install a 17.?? version?
I appreciate any help to unbrick my phone
Best, Phil
Hi,
in Sammobile, there are three German versions of the firmware:
- Germany (DBT)
- Germany T-Mobile (DTM)
- Germany Vodafone (VD2)
How do I find out which version I need and how much does it matter?
Thanks in advance,
Phil
I got it working with the help of hainguyenthao.
During all these installation steps I made some notes for myself to remember if I have to re-do this in some months or years... Don't expect too much of them as they were only intended for usage of my own. However, maybe you get some useful information out of it. (solving the original issue can be found as the last section)
# Installing custom roms
## Modes
- download-mode or Odin-mode or bootloader: Power + Bixby + VolDown * 7s
- recovery: Power + Bixby + VolUp * 7s
## Locks
- OEM lock means that only samsung-signed firmware can be installed
- FRP lock is similar to this
- RMM lock is hard (introduced in Samsung, Android 10)
- symptoms: "RMM state = Prenormal", "Only official released binaries are allowed to be flashed", OEM unlock not available
- reason: sim card with wrong country
- solution: wait for 7 days
- after unlocked again: install bypass zip (after each time flashing a custom rom!)
- see this post: https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
- dm-verity seems to be another lock
## Odin vs Heimdall
- Odin only works on Windows (thouhg also in a VM)
- Heimdall works on Linux
- Probably with quite some work, heimdall can be installed on MacOS
- Odin usage recommended a lot!!!
- Alternatively unpack the matryoshka until you have the .img's and install them in one go (not individually!!!)
- sudo heimdall flash --BOOT boot.img --CACHE cache.img --CM cm.bin --DQMDBG dqmdbg.img --HIDDEN hidden.img --KEYSTORAGE keystorage.bin --RADIO modem.bin --CP_DEBUG modem_debug.bin --ODM odm.img --OMR omr.img --PARAM param.bin --RECOVERY recovery.img --BOOTLOADER sboot.bin --SYSTEM system.img --UP_PARAM up_param.bin --USERDATA userdata.img --VENDOR vendor.img
## Installing a custom ROM
- unlock OEM in developer options (if not available, see RMM lock)
- heimdall flash --RECOVERY twrp-3.4.0-0-starlte.img --no-reboot
- then directly boot to recovery (`Power` + Bixby + VolUP * 7s) after ending download-mode (`Power` + VolDown * 7s)
- lineage-17.1-20201019-recovery-starlte.img can be used as well but twrp is more convenient
- install zips adb sideload in the following order:
- lineage-17.1-20201016-microG-starlte.zip
- no-verity-opt-encrypt-6.1.zip (against dm-verity)
- RMM-State_Bypass_Mesa_v2.zip (against RMM lock)
- maybe try flashing magisk zip (but not tested)
## Installing Samsung stock firmware
- download with samsungfirmware.net, sammobile.com (needs login)
- install Odin on Windows
- unpack to get .tar.md5 files
- drag them into Odin
- go to download mode (`Power` + Bixby + VolDown * 7s)
- press start in Odin
## Root
- supersu does not work (invalid zip; probably deprecated)
- addonsu does not work from lineageos17.1 onwards (https://www.xda-developers.com/lineageos-17-1-android-10-officially-available/)
- Magisk has to be used (https://topjohnwu.github.io/Magisk/install.html)
- patching AP did only work at second time
- instructions use stock Android, not sure how lineageos works...
- consider the warnings below the Samsung instructions
## File endings
- .tar.md5 files can be installed directly by odin; alternatively rename, and unpack twice until one can flash the files individually heimdall flash --RECOVERY recovery.img --...
- .tar files work with odin as well
- .img files are usually recovery; flash with heimdall (they are inside the odin tar-packages)
- .zip are files to install with twrp or lineage recovery (e.g., lineageos, RMM, no-verity, ...)
## How to disable OEM during a bootloop
- help by Michael Samy via Discord
- use Odin in Windows (if not available, use VM)
- flash a combination image (e.g., from samsungfirmware.net, combinationfirmware.com)
- in this combination image, enable OEM
- then one can flash the newest samsung version again
Phil9876 said:
I got it working with the help of hainguyenthao.
During all these installation steps I made some notes for myself to remember if I have to re-do this in some months or years... Don't expect too much of them as they were only intended for usage of my own. However, maybe you get some useful information out of it. (solving the original issue can be found as the last section)
# Installing custom roms
## Modes
- download-mode or Odin-mode or bootloader: Power + Bixby + VolDown * 7s
- recovery: Power + Bixby + VolUp * 7s
## Locks
- OEM lock means that only samsung-signed firmware can be installed
- FRP lock is similar to this
- RMM lock is hard (introduced in Samsung, Android 10)
- symptoms: "RMM state = Prenormal", "Only official released binaries are allowed to be flashed", OEM unlock not available
- reason: sim card with wrong country
- solution: wait for 7 days
- after unlocked again: install bypass zip (after each time flashing a custom rom!)
- see this post: https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
- dm-verity seems to be another lock
## Odin vs Heimdall
- Odin only works on Windows (thouhg also in a VM)
- Heimdall works on Linux
- Probably with quite some work, heimdall can be installed on MacOS
- Odin usage recommended a lot!!!
- Alternatively unpack the matryoshka until you have the .img's and install them in one go (not individually!!!)
- sudo heimdall flash --BOOT boot.img --CACHE cache.img --CM cm.bin --DQMDBG dqmdbg.img --HIDDEN hidden.img --KEYSTORAGE keystorage.bin --RADIO modem.bin --CP_DEBUG modem_debug.bin --ODM odm.img --OMR omr.img --PARAM param.bin --RECOVERY recovery.img --BOOTLOADER sboot.bin --SYSTEM system.img --UP_PARAM up_param.bin --USERDATA userdata.img --VENDOR vendor.img
## Installing a custom ROM
- unlock OEM in developer options (if not available, see RMM lock)
- heimdall flash --RECOVERY twrp-3.4.0-0-starlte.img --no-reboot
- then directly boot to recovery (`Power` + Bixby + VolUP * 7s) after ending download-mode (`Power` + VolDown * 7s)
- lineage-17.1-20201019-recovery-starlte.img can be used as well but twrp is more convenient
- install zips adb sideload in the following order:
- lineage-17.1-20201016-microG-starlte.zip
- no-verity-opt-encrypt-6.1.zip (against dm-verity)
- RMM-State_Bypass_Mesa_v2.zip (against RMM lock)
- maybe try flashing magisk zip (but not tested)
## Installing Samsung stock firmware
- download with samsungfirmware.net, sammobile.com (needs login)
- install Odin on Windows
- unpack to get .tar.md5 files
- drag them into Odin
- go to download mode (`Power` + Bixby + VolDown * 7s)
- press start in Odin
## Root
- supersu does not work (invalid zip; probably deprecated)
- addonsu does not work from lineageos17.1 onwards (https://www.xda-developers.com/lineageos-17-1-android-10-officially-available/)
- Magisk has to be used (https://topjohnwu.github.io/Magisk/install.html)
- patching AP did only work at second time
- instructions use stock Android, not sure how lineageos works...
- consider the warnings below the Samsung instructions
## File endings
- .tar.md5 files can be installed directly by odin; alternatively rename, and unpack twice until one can flash the files individually heimdall flash --RECOVERY recovery.img --...
- .tar files work with odin as well
- .img files are usually recovery; flash with heimdall (they are inside the odin tar-packages)
- .zip are files to install with twrp or lineage recovery (e.g., lineageos, RMM, no-verity, ...)
## How to disable OEM during a bootloop
- help by Michael Samy via Discord
- use Odin in Windows (if not available, use VM)
- flash a combination image (e.g., from samsungfirmware.net, combinationfirmware.com)
- in this combination image, enable OEM
- then one can flash the newest samsung version again
Click to expand...
Click to collapse
thx for your effort