[Q&A] [HOWTO][TAR][OUDHS] THE ODIN THREAD :: Return to stock, fix soft brick :: 5/7/
Q&A for [HOWTO][TAR][OUDHS] THE ODIN THREAD :: Return to stock, fix soft brick :: 5/7/13 MDL
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [HOWTO][TAR][OUDHS] THE ODIN THREAD :: Return to stock, fix soft brick :: 5/7/13 MDL. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
i did all this to my s4 but now when i boot it, says Kernel Is Not Seandroid Enforcing, Set Warranty Bit
also when i booted the phone the wifi does not work. could you help with this problem?
Samsung Galaxy S4
Is This ''UVUAMDL Official TAR'' for Samsung Galaxy S4?
Ayaz Gill said:
Is This ''UVUAMDL Official TAR'' for Samsung Galaxy S4?
Click to expand...
Click to collapse
Yes
UPDATE: I fixed the issue while posting this, the solution is included. I am hoping by posting this it may help someone having the same problem, because I spent hours and days trying to solve the issue. Sorry the post is so long.
This is my first post.. I am in desperate need of help!
I have searched everywhere, and cannot find any answers really.
I rooted my M919 at one point, and I could not receive OTA updates.
I do not know if it was rooted when I tried to update it with Odin though.
I was in a hurry (I know BIG mistake) and I never wiped my phone or anything before trying to flash the phone.
I think the phone may not be working because I may have not used triangle away before, but I am not sure if I ever used it. I did the root a long time ago.
I have tried changing USB cords, computers, drivers, md5 files, different Odin versions, flashing PIT file, you name it, I have probably tried it
When I boot the phone the currupt recovery screen shows up. Kies will not recognize the phone.
In the left corner it says:
ODIN MODE
...SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURST MODE enabled
I can still access "downloading" mode, and it says the same as above.
Odin gives me different errors depending on the file I am attempting to flash
The reason I tried flashing the PIT file is because it would sometimes say
I am not completely sure what update I was using before this all happened, but I think it may have been this one, unrooted?:
CF-Auto-Root-jfltetmo-jfltetmo-sghm919.tar.md5
Error codes are as follows:
While flashing 4.4.4 (Odin 3.10)
M919UVUFNH7_M919TMBFNH7_M919UVUFNH7_HOME.tar.md5
JFLTE_USA_TMO_16G.pit
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUFNH7_M919TMBFNH7_M919UVUFNH7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
Recovery File I found (Odin 3.09)
JFLTE_USA_TMO_16G.pit
openrecovery-twrp-2.8.0.1-jfltetmo.tar
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
Recovery File I found (Odin 3.09)
JFLTE_USA_TMO_16G.pit
openrecovery-twrp-2.8.0.1-jfltetmo.tar
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
One time I tried using this and it passed!!!
This ONLY works on 3.07 to my knowledge though. It fails on every other Odin
Recovery File I found (Odin 3.07)
JFLTE_USA_TMO_16G.pit
openrecovery-twrp-2.8.0.1-jfltetmo.tar
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
The screen is now frozen on the "Samsung Galaxy S4" screen and just shuts off if trying to boot into recovery mode.
If plugged into USB while trying to boot into recovery it launches the recovery file I just flashed!
I went back into download mode, and plugged the phone back in.
I opened Odin 3.07 again, since I had success with the recovery file.
I tried flashing 4.4.4 again M919UVUFNH7_M919TMBFNH7_M919UVUFNH7_HOME.tar.md5
and it failed while only having Auto Reboot checked. I tried launching it with Auto Reboot AND F Reset Time, and it worked!! Hope this helps someone!!
Hi DarkMenace - would it be possible for you to send me signed M919 PIT file as well? Thanks
shaqto said:
Hi DarkMenace - would it be possible for you to send me signed M919 PIT file as well? Thanks
Click to expand...
Click to collapse
Replied to your email. Not sure if I still have it but I may be able to find it if you say it's not there.
alright i did a no no... I tried flashing back to stock odin when my phone was encrypted .. now its softbricked.
everytime i try to flash the stock odin, it always fails at system.img ext4. Need some help guys, its been softbricked for a week. I flashed philz touch twrp on it so I do recovery on it. any ideas?
doesnt work
Bricked my s4/but i had twrp installed to fix it
I'm getting a Fail message in Odin over and over. I've downloaded the .zip twice so I don't think it's an issue with a corrupt file... The .dll is in my Odin folder and everything. Pretty confused and today is my last day to send my phone back into T-Mobile before they charge me.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> sbl2.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> aboot.mbn
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
asmth00 said:
I'm getting a Fail message in Odin over and over. I've downloaded the .zip twice so I don't think it's an issue with a corrupt file... The .dll is in my Odin folder and everything. Pretty confused and today is my last day to send my phone back into T-Mobile before they charge me.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> sbl2.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> aboot.mbn
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
What version Bootloader/Modems do you have now on the phone? If the version you have now has Knox, then you can't downgrade to MDL.
If you are not sure, you can use this free app: https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo&hl=en
If the version is MK2 or newer, you can't downgrade to MDL.
You can find newer firmwares either on the SamMobile.com site, or on this thread: http://forum.xda-developers.com/galaxy-s4-tmobile/general/firmwares-official-mdl-mk2-nb4-t2816508
Rob
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
In odin, it says 0:[COM4] on the top left
You have 0:[COM3] in your screenshot
Is there a problem or something?Or is it fine?
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SGH-M919-UVUAMDB-k0nane.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
I get this when i click start
i have a gt-1905 softbricked
please help me
AziNoapte said:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SGH-M919-UVUAMDB-k0nane.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
I get this when i click start
i have a gt-1905 softbricked
please help me
Click to expand...
Click to collapse
If you have a GT-1905 (which I can't find), you shouldn't be trying to flash FIRMWARE for a T-Mobile phone (SGH-M919). That will brick your phone.
If it is an S4, you should be able to take off the back and look under the battery for the model number.
You can flash ROMs, but not firmware between different S4 models. Try finding the FIRMWARE for your phone, and flash that. Also, verify your model, because GT-1905 isn't a Samsung model number.
You can find firmwares here: http://www.sammobile.com/firmwares/
Rob
rlichtefeld said:
If you have a GT-1905 (which I can't find), you shouldn't be trying to flash FIRMWARE for a T-Mobile phone (SGH-M919). That will brick your phone.
If it is an S4, you should be able to take off the back and look under the battery for the model number.
You can flash ROMs, but not firmware between different S4 models. Try finding the FIRMWARE for your phone, and flash that. Also, verify your model, because GT-1905 isn't a Samsung model number.
You can find firmwares here: ------------To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links--------------
Rob
Click to expand...
Click to collapse
i messed up the writing cuz i was scared
I have 19505
I managed to get to 4.2.2 with konane`s guide,got the stock tar but wifi doesnt work on my S4
Can you help me fix it?
Or if it is impossible, can i upgrade to KitKat?
AziNoapte said:
i messed up the writing cuz i was scared
I have 19505
I managed to get to 4.2.2 with konane`s guide,got the stock tar but wifi doesnt work on my S4
Can you help me fix it?
Or if it is impossible, can i upgrade to KitKat?
Click to expand...
Click to collapse
Since this forum is for the T-Mobile variant of the S4, and I'm not familiar with the GT-I9505, I would suggest you try the forum for that model:
http://forum.xda-developers.com/galaxy-s4
If you flashed a T-Mobile tar to your I9505, it is probably because of the radio/modem which was designed for the T-Mo model. There should be links in that forum about no WiFi, etc.
Rob
Hello gang. Got a new circuit board installed two weeks ago. Got the phone back, started setting it up, and after about an hour the touchscreen quit working. >8\
I emailed the shop and they said "could be because you're rooted."
Smelled like bull**** to me, but giving them the benefit of the doubt I figured I'd try to flash back to stock. (Which I WAS actually stock, I had the 4.4.4 OTA update, and then rooted and de-bloated.)
Anyway, I downloaded the "Stock firmware" (SGH-M919-UVUAMDB-k0nane.tar.md5) from post 1 in the title thread and flashed it with Odin.
SEEMS to be working, but oddly enough I have a M919UVUFNH7 baseband and bootloader, but Android 4.4.2, which based on my reading, should be impossible?
Also, like several other posters, I have no wifi.
In any event, I am currently downloading the NH7 firmware from sammobile. Says 2 hours to go.
Will try to flash that with Odin and we'll see what happens. Anyone have suggestions in the meantime?
OK - follow-up. I downloaded M919UVUFNK2_M919TMBFNK2_M919UVUFNK2_HOME.tar and flashed it with Odin. Even though Odin said "Boot" and "Modem" in the flashing process, I still seem to have NH7 bootloaders and baseband.
Help?
Well, never mind. I don't care anymore. Tried to replace my glass and cracked the digitizer. Dunno if I'm down to drop another $120 on this thing now.
$300 purchase price
$100 circuit board replacement
$12 glass
Now $120 for a display? I might just call knock it off with this thing.
Related
I was installing cyanogenmod but something soft-briked it so I went back and did the unrooting process but this time installed 4.4.2 instead of the older rom. After trying to root I learned that the stock rom I was on patched rooting away. Now I'm stuck and even trying to downgrade I get the following error in odin. All my searching I haven't found anything on how to fix this. Can someone help, all the guides on the forum do not work.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sbl2.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl3.mbn
<ID:0/006> rpm.mbn
<ID:0/006> aboot.mbn
<ID:0/006> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
Guess I didn't need to do that, still was able to flash custom rom, thought i lost that ability. Now I only have to worry about the whole flag for warranty
.
Try getting another stock file, what I mean by another I mean find it from xdas s4 thread and a new version of Odin, preferably a older version
Sent from my SGH-M919 using XDA Premium 4 mobile app
This was originally posted in the wrong forum. My apologies.
So after following this link: http://www.cnet.com/how-to/how-to-ro...ung-galaxy-s3/ I have a bricked device.
No matter what I do, Odin seems to fail. This is what I think caused the problem in the first place. Also there is the possibility that the guide is way out of date.
So I was wondering if anyone had any advice on how to proceed? The device isnt mine and this isnt my first time rooting a device. I just have never bricked anything before.
Here is the log from ODIN from recreating the process in the link above
Code:
<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> cache.img
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Here is the Log from ODIN from my latest attempt to flash something at it.
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_ATT_I747UCDLK3.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Tried flashing a full image, but it gives this error
Code:
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Tried flashing the "stock" image.
Going to try a different PC tomorrow and hope that I get a different result.
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Do you have an i747 or u747m? Do not flash any more ROMs without knowing the bootloader version installed on your phone. If you phone has a 4.3 or newer bootloader and you try to downgrade it, it will brick your phone.
I recommend that you install the latest version of Philz and flash cm10.2 for the d2att to at least get your phone running so you can determine the bootloader.
audit13 said:
Do you have an i747 or u747m? Do not flash any more ROMs without knowing the bootloader version installed on your phone. If you phone has a 4.3 or newer bootloader and you try to downgrade it, it will brick your phone.
I recommend that you install the latest version of Philz and flash cm10.2 for the d2att to at least get your phone running so you can determine the bootloader.
Click to expand...
Click to collapse
SGH-i747
And the issue I am encountering is a bit bigger than that, I cant install anything. I cant even flash the stock .tar file I found. I cant get ODIN to do anything except fail? I never even got CWM installed.
Can you get into download mode and stay in download mode?
There is not stock tar.md5 ROM you can flash from sammobile because AT&T never made a stock ROM available after 4.1.1.
Did you try to flash Philz Touch for the d2lte in Odin 3.07 using his tar.md5 recovery file? What about TWRP?
No TWRP either?
Can you provide me a link to that MD5
After digging up the MD5 I have got the phone booting again.
Thank you so much for all your help!
Boot loop after factory reset on GT-N5110
I tried to reset the device using Settings>Back up and reset>Factory data reset>Delete all.
Rebooted into a black screen with an Android with a hatch open and a blue spinning thing. It's been stuck in a endless loop of the startup screen with the name and model, which then goes to the Android with open hatch.
I pried the rear cover off and discovered that I don't have any screwdrivers small enough to remove the battery. So I'm wondering if there is any software based fix that I can try.
Holding down Power+Volume Down interrupts the loop and brings up this screen - blogyourearth.com/wp-content/uploads/2012/02/Samsung-Galaxy-S2-Warning-Custom-rom-installation.jpg
I've had the tablet for 2 years, so the warranty is long gone. I'd be open to flashing a Custom Rom/Kernel, as long as I'm able to go back to the default TouchWiz 4.1.2.
Bump/Update
Update/bump.
Tried flashing the stock 4.1.2. firmware from sammobile.com with Odin v3.07. - Doesn't seem to work, here are the status messages from Odin:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N5110XXBMC9_N5110XACBMC9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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 -----Status was frozen on boot.img for 3 hours.
<ID:0/004> __Xmit Write fail
<ID:0/004> XmitData Fail..
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Anyone have any idea what's wrong? Should I try a different version of Odin, different firmware or what?
emc_2 said:
Update/bump.
Tried flashing the stock 4.1.2. firmware from sammobile.com with Odin v3.07. - Doesn't seem to work, here are the status messages from Odin:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N5110XXBMC9_N5110XACBMC9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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 -----Status was frozen on boot.img for 3 hours.
<ID:0/004> __Xmit Write fail
<ID:0/004> XmitData Fail..
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Anyone have any idea what's wrong? Should I try a different version of Odin, different firmware or what?
Click to expand...
Click to collapse
Are you able to enter download mode without issues?
pvsgh said:
Are you able to enter download mode without issues?
Click to expand...
Click to collapse
Yes, no issues at all.
emc_2 said:
Yes, no issues at all.
Click to expand...
Click to collapse
Try flashing TWRP recovery, take a backup of your current ROM, and then try installing one of custom ROM .
pvsgh said:
Try flashing TWRP recovery, take a backup of your current ROM, and then try installing one of custom ROM .
Click to expand...
Click to collapse
Have no idea on how to do any of the above, but I'm googling now. Are there any guides/articles on how to do this, that You could point me in the direction of? Since I'm soft-bricked, is there any point in trying to back-up my presumably borked ROM? I've already downloaded my country specific, stock 4.1.2. ROM.
Many thanks for taking the time to help me and I apologize for the noob questions. I know my way around Windows, but when it comes to Android - I'm hopeless
I flashed TWRP successfully, I think...
Stumbled across the ODIN troubleshooting thread and one of the steps was to try different cables. The 10 foot cable I've been using for the past 8 months would only end up with a failure, stock cable... didn't even register. 8 inch cable I bought for my external battery had a successful flash in 10 seconds!
<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)
i.imgur.com/HPziH0E.png
emc_2 said:
I flashed TWRP successfully, I think...
Stumbled across the ODIN troubleshooting thread and one of the steps was to try different cables. The 10 foot cable I've been using for the past 8 months would only end up with a failure, stock cable... didn't even register. 8 inch cable I bought for my external battery had a successful flash in 10 seconds!
<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)
i.imgur.com/HPziH0E.png
Click to expand...
Click to collapse
OK so now you have a working TWRP recoveryand you also know what was causing ODIN to fail.
Next step would be to install a custom ROM, check the development section.
if you prefer stock then you ODIN your stock tar file which you downloaded.
Using TWRP, I backed up; EFS, Boot, Cache, System and Data. After the backup completed I followed the prompt to reboot and it booted into Android *happy dance*.
looks like all the user preferences are gone. No more password or background pictures and all apps have been removed from their folders. Basically looks like all the apps that I installed are there and any data associated. But all my preferences and set options are gone.
Going through the apps, I remembered that I had rooted using Framaroot. Do you think that may have been the cause for the soft-brick? Should I un-root and then try the factory reset again or just flash the stock ROM that I downloaded?
EDIT: didn't see your reply when I started typing this out. Since TWRP is flashed. Does that mean it has replaced whatever recovery Samsung had in place? If so; does having it installed/flashed increase the chance of a fairly stress free recovery in case of future problems?
So, it turns out pvsgh is pretty awesome!
It worked! Thank you so much. You rock!
Had to use another cable though. I think I need a new USB/Charge port
After flashing the stock ROM I had quite a bit of left over data like app folders and pictures/screenshots. Went into the stock recovery and did a factory reset from there, which wiped the internal storage back to factory state.
Should I flash TWRP again and use it to backup everything, now that everything seems to be working normal. Or just leave it as is?
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N5110XXBMC9_N5110XACBMC9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> cache.img
<ID:0/004> hidden.img
<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!!
i.imgur.com/j9neU0B.png
emc_2 said:
It worked! Thank you so much. You rock!
Had to use another cable though. I think I need a new USB/Charge port
After flashing the stock ROM I had quite a bit of left over data like app folders and pictures/screenshots. Went into the stock recovery and did a factory reset from there, which wiped the internal storage back to factory state.
Should I flash TWRP again and use it to backup everything, now that everything seems to be working normal. Or just leave it as is?
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
N5110XXBMC9_N5110XACBMC9_HOME.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Added!!
Odin v.3 engine (ID:4)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
boot.img
NAND Write Start!!
recovery.img
system.img
cache.img
hidden.img
RQT_CLOSE !!
RES OK !!
Removed!!
Remain Port .... 0
All threads completed. (succeed 1 / failed 0)
Added!!
Removed!!
i.imgur.com/j9neU0B.png
Click to expand...
Click to collapse
You can take a backup that you can use to restore your tablet if you ever get issues again.
Or just follow the same procedure again.
Taking backup is completely a user choice whether he want it or not.
So I rooted my s4 mini i9195 and flashed aicp ver 10 and now I have no wifi, no mobile, no lte, the haptic feedback buttons don't work, no led, and my computer doesn't recognize the s4 mini unless I go into download mode. When I start up the phone it says something about something being wrong with the internal hardware of my phone but it's a brand new phone and I didn't have these problems before flashing this rom. I tried using odin to go back to stock and it fails at nand-write start. I tried loading a new pit and that fails too. I'm completely stuck now. I have no idea what to do. Can someone please help me?
How you flashed aicp?
I used cwm.
Here's what comes up on odin when I try to flash back to stock:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9195XXUCOD3_I9195BTUCOD1_I9195XXUCOD3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<ID:0/006> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Can you enter in recovery mode?
yeah, I can. I tried clearing caches and data and flashing aicp over again, it didn't work-in fact, for whatever reason the aicp rom isn't in my sd card anymore.
Try to flash a stock deodexed rom from here http://forum.xda-developers.com/showthread.php?t=2552363 using your custom recovery
the problem with that is I can't get anything from my computer to my phone because the phone doesn't pop up on My Computer and the phone doesn't give me any options when it's plugged in. It's only recognized when in download mode and trying to do anything in download mode doesn't seem to work.
Download direct to you phone and then move to sdcard or download to pc and than just using a card reader move rom to your sdcard and then try to flash
I can't download directly to my phone, I have no connection whatsoever on my phone.
Use a computer and a card reader ))
I'm going to get an sd reader later today. I tried flashing the modem and this is what I got:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MODEM_I9195XXUCOC2.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NON-HLOS.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> Transmission Complete..
<ID:0/006> Now Writing.. Please wait about 2 minutes
<ID:0/006>
<ID:0/006> Receive Response from boot-loader
<ID:0/006> Complete(Write) operation failed.
<ID:0/006> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
What firmware did you have before flashing aicp?
It was android 4.4.2 touchwiz I believe but I don't know the details. The phone was up-to-date and it's I9195
Whatever try to restore to a stock rom by flashing a deodexed rom
so the rom flashed properly but I still didn't have mobile data or wifi or haptic feedback. I'm not really worried about the haptic keys because I can just use softkeys if necessary but the mobile data and wifi are an issue. LED worked when I shut the phone down to put it into download mode to flash the modem. Flashing the modem was unsuccessful:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MODEM_I9195XXUCOC2.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NON-HLOS.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> Transmission Complete..
<ID:0/005> Now Writing.. Please wait about 2 minutes
<ID:0/005>
<ID:0/005> Receive Response from boot-loader
<ID:0/005> Complete(Write) operation failed.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
And the phone came up with red lettered "Secure Check Fail Modem"
Try to call *#06# And tell what you get
At least look here http://forum.xda-developers.com/gal...rom-aicp-6-0-kk-4-4-4-9195-919015-10-t2907258
IMEI 990004400585315 / 01
I looked on that thread but nothing about my issue is coming up.
<ID:0/005> Receive Response from boot-loader
<ID:0/005> Complete(Write) operation failed.
Does this mean that I should flash a new bootloader? I never unlocked knox because beyond voiding the warranty, I didn't think it would have any effect on flashing but I may be wrong?
Your phone is definitely a "i9195" and not a "i9195L"? Was your phone locked to a network?
I found this http://forums.androidcentral.com/sa...ot-flash-really-really-stuck-please-help.html try to do how is described in the last thread but remember that you have a 9195 not a s3
Hi there!
I recently bought a N3N (N7505) :good: for mobile drawing. Since I bought it used, I found KNOX at 0x1 and the 4.4.2 it came with was already annoyingly buggy (lags everywhere, packed RAM & phone app FCs). I did manage to root it through CF-Autoroot (I think?) and even put a custom recovery (TWRP touch v2.8.7.0)
The problem is, everytime I download a ROM from Sammobile (md5 checks confirm undamaged downloads), it fails to flash via ODIN (flashes ALL THE WAY till the end and says FAILED - phone reboots perfectly to previous OS like nothing happened) and I'm wondering if I downloaded the wrong ODIN files, or is there something I'm missing?
So, i'm currently on N7505XXUCNL1 and wondering how I can reflash it (or a similar one) to refresh the phone anew :angel:
ROMz, Y U NO FLASH???
Any advice on what ROM would best suit me to refresh my N3N with???
:victory::victory::victory:Thanks in advance!!:victory::victory::victory:
UPDATE:
When i'm in Download mode, this is the information displayed
ODIN MODE
PRODUCT NAME: SM-N7505
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
Secure Download : Enabled
KNOX WARRANTY VOID: 1
AP SWREV: (2)
The ODIN log for when I try to flash N7505XXUCNL1_N7505OXXCNL1_TPH is here:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1100)..
<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> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> modem.bin
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The ODIN log for N7505XXUCOE1_N7505SWCCOF1_SWC is here:
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1100)..
<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> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> modem.bin
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Now I'm stuck on the Firmware update encountered an issue. Please select recovery mode in Kies and try again
can you provide us the log?
damadikaz said:
can you provide us the log?
Click to expand...
Click to collapse
The ODIN failed flash log??
Where do I find that?
damadikaz said:
can you provide us the log?
Click to expand...
Click to collapse
Greetings damadikaz,
I have posted my ODIN logs as an UPDATE on the main post for two separate flashes that both failed.
Any help is greatly appreciated:highfive::highfive::highfive:
Try flashing the latest stock ROM from here: http://www.sammobile.com/firmwares/database/SM-N7505/
Looks to me like the flash is failing because the bootloader currently on the phone is newer than the bootloader in the ROM you are flashing.
audit13 said:
Try flashing the latest stock ROM from here: http://www.sammobile.com/firmwares/database/SM-N7505/
Looks to me like the flash is failing because the bootloader currently on the phone is newer than the bootloader in the ROM you are flashing.
Click to expand...
Click to collapse
Oh WOW!!! It could be!
Thank you very much:laugh:
Going to download tonight and flash :good::good::good:
Will return with feedback!
Thanks again good sir! :highfive::highfive::highfive: