I have been all over every droid forum trying to find an answer or a solution and have, so far, been unsuccessful in finding one. When I got the phone, I installed the CWM recovery and the Voodoo lagfix. Here is what happened:
Yesterday (2/25), my phone wouldn't connect to my PC. After I rebooted the phone, it would hang during while the Media Scanner was going. So, I decided to flash the phone. I didn't have the stock ROM, but I did have a copy of the DL30 leak so I booted into CWM recovery and installed the DL30.zip file. As soon as it finished and restarted, I was getting all sorts of force closes. Reading into the problem a little, I realized that I should have disabled Voodoo before flashing. So, I tried flashing back to DL09 and I started getting this message at startup:
-- Wiping data...
Formatting FOTA...
FOTA wipe failed.
Formatting Data...
Data wipe failed.
Formatting CACHE...
Cached wipe failed.
Formatting DB_Data...
Dbdata wipe failed.
wipe_data failed.
So, I started looking on xda-forums. I found a thread about recovering from this using something called "Eugene's does not brick" ROM and some "T959UVJFD True Stock Firmware" file. But, stupid me, I didn't realize these were for a Samsung Vibrant, not a Fascinate. I flashed the ROM and firmware (with re-partition) successfully with ODIN, but then I started getting a different boot screen for an IT-9000. So, after much more searching and downloading I found Adrenalyne's DI01 package. I also found a flash program called Heimdall, and with the DI01 package, was able to get back to the Fascinate ROM stuff (the boot screen stopped showing the IT-9000 info). However, the phone still shows the wipe data failures, but with some extra text:
--Movi_Check Start..!!
checksum confirmation need_checksum[0]
Not need checksum confirmation
-- Movi_check already executed..!!
-- movi_checking done..!!
So now I am trying to follow the instructions that I should have followed yesterday. However, when I try to flash the DI01 package via ODIN, I get the following error:
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.bin
<ID:0/004> cache.rfs
<ID:0/004> dbdata.rfs
<ID:0/004> factoryfs.rfs
<ID:0/004> modem.bin
<ID:0/004> movinand.bin
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have the DJ09 and DJ05 ROMs, but when I try the ODIN flash I get the following error:
<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> cache.rfs
<ID:0/004> dbdata.rfs
<ID:0/004> factoryfs.rfs
<ID:0/004> modem.bin
<ID:0/004> recovery.bin
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
My only theory is that the phone isn't booting into the correct recovery because I flashed the Vibrant software w/ repartition. So I tried flashing the CWM recovery via ODIN, but get the same failure at the recovery.bin part. I read somewhere that I need to restore the MBR (because of the Voodoo lagfix), but I can't because I can't get into the CWM recovery to restore it. So now I am stuck and can't figure anything else to do. Please please please help.
Related
after flashing the repencis v2.6pro it got stuck in boot screen and it wont go to recovery and i am not able to flash it with odin v1.85 it comes like this
<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> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
i did it with the dokey's kies broken frimware specified in his thread
plz help
vllskumar said:
after flashing the repencis v2.6pro it got stuck in boot screen and it wont go to recovery and i am not able to flash it with odin v1.85 it comes like this
<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> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
i did it with the dokey's kies broken frimware specified in his thread
plz help
Click to expand...
Click to collapse
Try another version. Make sure your phone is in download mode using Vol down+Home key+Power key. Flash it when the COM box is lit up after selecting PDA, Phone and CSC. Try Odin v1.84 if v1.85 fails.
raolemo said:
Try another version. Make sure your phone is in download mode using Vol down+Home key+Power key. Flash it when the COM box is lit up after selecting PDA, Phone and CSC. Try Odin v1.84 if v1.85 fails.
Click to expand...
Click to collapse
Try pressing Ctrl+Alt+Delete and go to "Processes" and search for the following process :"KiesTrayAgent.exe","Kies.exe","adb.exe"
If you seen that all in the processes of your PC/Laptop , Make sure to end that all process before proceeding up with Mr.Odin
Because mine i've flashed my DXLA1 Firmware because i always encountering SD Card issues so i ended up downgrading my DXLA1 to my Factory Firmware DXKK4
In this way , Mr.Odin helped me
vllskumar said:
after flashing the repencis v2.6pro it got stuck in boot screen and it wont go to recovery and i am not able to flash it with odin v1.85 it comes like this
<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> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
i did it with the dokey's kies broken frimware specified in his thread
plz help
Click to expand...
Click to collapse
install some other version... kill kies / adb processes... make sure ur cable is fine
got it right
there was some problem with the kies splitted files so downloaded the firmware from from another source n now got it working thx guyz
So I've been screwing around now for somewhere around 7 hours trying to figure out how to root the s4. I've tried both the motochopper and odin methods on pc and mac and every time i end up with the same errors. I've followed the instructions word for word and tried again with after wiping the phone of all its data. heres the log for 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> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
Then motochopper seems to run smooth, but then says:
Rooting phone...
This may take a few minutes.
Failure.
Cleaning up...
Exploit complete. Press enter to reboot and exit.
Press any key to continue...
Any ideas? I have the SGH-M919 T-Mobile version.
did you do the ota update before you tried to root? I did, and had to oden back to the stock m919uvuamdb version, then motochop, then flash a recovery of your choice, then you can flash any of the roms, custom or stock+root. thru recovery. I think maybe now there is an updated stock with root avail,
and make sure you follow directions for unzipping and placing the .tar in the right place (pda) and uncheck all but reboot
If you've updated then you are UVUAMDL, follow this
http://forum.xda-developers.com/showthread.php?t=2268880
Also, there is a a problem flashing CWM or TWRP. Just be sure to read the first 4 pages of that thread
Alternate method which I did on MDL:
1) Odin OUDHS Recovery, download SuperSU cwm zip from link in thread: http://forum.xda-developers.com/showthread.php?t=2260031
2) Then cwm rebuilt kernel with root restriction removed: http://forum.xda-developers.com/showthread.php?t=2271976
3) In the same session cwm the SuperSU zip mentioned in #1.
Can you log into a root shell?
Sent from Spaceball One.
Solution
You need to flash t Mobil kernel to get root and root thrue cwm method
Hi
My GT-I9195 S4mini recently starting acting strangely recently, then suddenly 2 days ago would not boot up completely, there is the constant boot loop with the Samsung logo, then the blank screen and vibration.
As i had CWM recovery 6.0.3.3 (also fully rooted), I booted into recovery and tried to wipe date/reset, it attempted to do this errored with the failed to mount /data! and attempting to mount data or the external_sd via the advanced menu also failed to mount /data!.
I tried to install CM10 custom rom and i got a Status 7 error, edited the update scripts in the .zip file and the same thing happened
Tried to reinstall firmware with ODIN, tried the original H3G firmware (I'm on 3UK) and it failed to update, however eventhough the CHE firmware was successful, on rebooting the CWM 6.0.3.3 recovery was still there (its doesnt seem to allow me to update the recovery) and the same problems with boot loop and failed mounts.... Any further suggestions I would surely appreciate.
Try updating to the latest CWM, and also try with Odin 3.09 in case it was 3.07 you tried with.
i have tried that it seems successful on Odin, however when the device reboots, its still says 6.0.3.3, just redownloading the latest CWM
Odin error log for H3G firmware
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> tz.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> persist.img.ext4
<ID:0/004> NON-HLOS.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Ext4)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Odin Logs for CHE Firmware
<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> SingleDownload.
<ID:0/004> tz.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> NON-HLOS.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
after the update, the CWM Recovery is still present which seems quite odd
flashing ROMs does not remove cwm and thus its obvious that cwm is still present. (Though when flashing to stock ROM you can get the following message in cwm "Rebooting will change to stock recovery" or something along those lines.
Can be ignored by pressing NO when closing cwm.)
Try updating cwm with the new version (6.0.3.7) through Odin 3.9. And if you still have bootloop try to reflash your device.
Hope this works out for you.
Sent from my GT-I9195 CM10.1-Nightlies using xda app-developers app
JMailuhu said:
flashing ROMs does not remove cwm and thus its obvious that cwm is still present. (Though when flashing to stock ROM you can get the following message in cwm "Rebooting will change to stock recovery" or something along those lines.
Can be ignored by pressing NO when closing cwm.)
Try updating cwm with the new version (6.0.3.7) through Odin 3.9. And if you still have bootloop try to reflash your device.
Hope this works out for you.
Sent from my GT-I9195 CM10.1-Nightlies using xda app-developers app
Click to expand...
Click to collapse
Hi Mate
Thanks for the advice, I have flashed firmwares not roms, hence the recovery should have changed unless I'm mistaken....anyway, I am unable to flash roms as I am unable to mount /data, so all attempts to install a rom through CWM have failed. wipe data has failed as the /data isnt mounting. I have flashed 3 firmwares via ODIN 3.09, the CHE and another have been successful but the boot loop continues, however the H3G which is my phones model has been unsuccessfully flashed for some strange reason.
I will try the latest CWM, howwever my challenge has been that I have a very slow net connection at present hence my inability to access firmwares easily.
I was on resurrection remix rom and I wanted to go back to the stock rom.So I downloaded the firmware for my region from stockroms.net and tried flashing it in ODIN.The problem is that odin gives a fail error when it reaches the end of the system.img file.I don't know what to do here,please help.Here is the progress report from 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> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Try using an older version of odin like 1.85 and also make sure the downloaded rom is ok.
I did that.I used like 3 different versions of odin and 2 stock roms with different regions.No effect.I have flashed TWRP back again so atleast some functionality is restored
Ok seems lik a partition issue. Try using an appropriate pit file.
gambitflash said:
I was on resurrection remix rom and I wanted to go back to the stock rom.So I downloaded the firmware for my region from stockroms.net and tried flashing it in ODIN.The problem is that odin gives a fail error when it reaches the end of the system.img file.I don't know what to do here,please help.Here is the progress report from 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> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
After Flashing The Stock Firmware Through Odin And Recieve Error MEssage Take Of the battery and put it back
Now go to download mode
Connect your phone
open odin
flash cwm or twrp using odin
when flashing is completed your phone is restart at this point Press Vup+Home+Power
Now Recovery is open
dont do anything except restart
it may ask for rooot then install it
now again go to recovery mode and flash custom rom using recovery
hope it works
Hi maybe someone has any ide what I do wrong here.
I am trying to install TWRP (latest available for SM-T525 - 10.1 inches LTE), but after tryin all Odin versions available and at least two versions of TWRP I'm stuck.
This is the output from odin (tried to run as admin/non admin) at least 2 invocations. MD5 sum verified - ok.
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1401)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 10 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> twrp-3.0.2-0-picassoltexx.img
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Additionally on the tablet screen I get newline in red :
Unsupport dev_type
The blue progress bar is few pixels wide but it gets stuck as well and I have to restart the tablet to get back to the system or to the recovery.
Any ideas are really highly appreciated.
Thanks in advance.
P.S. This is annoying when the device is getting more and more unusable because of the software (now youtube is not working anymore on this old kitkat 4.4.2) while the hardware is doing well.
FIXED:
I had to rename the image file to recovery.img - it helped.
ryzior said:
....
FIXED:
I had to rename the image file to recovery.img - it helped.
Click to expand...
Click to collapse
That's amazing as I always thought that Odin is only capable of flashing .tar or .tar.md5 files.
Perhaps this is only valid for older versions.
How did you managed to flash that recovery? I have also softbricked my T525 - reboots only to fastboot (Odin mode), but Odin can't even recognize it (not even PC sound of plugged device etc.). Stuck on Lineage bootloop and rebooting twrp (wrong version probably.