Database Users

Problem while attempting to room Galaxy S4 I337 ATT

Phone: Galaxy S4 I337 AT&T with latest update, 4.4.3
What I did before I began the process:
1) Enable debugging mode on the phone
2) Installed latest Samsung Drivers
3) Used original USB Samsung cable
What I did: Download and ran Root and Recovery for ATT-TMO GS4-CASUAL-R527b and in doing so, processed failed.
Here is what looks like now:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Following step, to correct the problem, was I download the firmware that came with the phone, I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar. Zip file in size of 1.59GB and I used different version of Odin, including 1.85, 3.04, 3.05 and 3.07 with no success to fix the problem I caused in the first place.
This is what phone looks like -
This is what Odin looks like when it attempted to process the file above, I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
I would like to get my phone back running again. Can someone please guide me, if it possible to get it back to stock firmware. Please understand that I searched the forum and Google for all possible solutions, as well as YouTube videos. I am clearly not experience in rooting phone and this was my first attempt.
Thank you for all the help.

Remember that the phone has a locked boot loader which prevents stock recovery and kernel from being replaced. Also, the boot loader itself cannot be downgraded.
You were on KitKat which means you had firmware ending with NB1 or NC1. Trying g to flash the MDL files was trying to downgrade boot loader and hence the issue.
http://forum.xda-developers.com/showthread.php?t=2616221
Read the return to stock section of the above thread. Download and flash the NB1 firmware. There are 2 versions of which you can use either.
Method to update to latest NC1 is also given in the thread.
The only working recovery we have is safestrap. All custom ROM flashing happens with this.

Almost..but failed.
So I checked out the post you replayed and I did the following -
1) Downloaded I337UCUFNB1_4.4_Stock_Odin_tar from here
2) Used Odin v3.9.3 and here is the following result:
<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> I337UCUFNB1_TWRootable_Full_Odin.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)
<ID:0/003> Removed!!
<ID:0/003> Added!!
File tar.md5 comes very close to completing and stop; and I get a FAIL!
On the phone I get the following:
START [224, 1440]
BAR [240, 1440]

selchi said:
So I checked out the post you replayed and I did the following -
1) Downloaded I337UCUFNB1_4.4_Stock_Odin_tar from here
2) Used Odin v3.9.3 and here is the following result:
<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> I337UCUFNB1_TWRootable_Full_Odin.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)
<ID:0/003> Removed!!
<ID:0/003> Added!!
File tar.md5 comes very close to completing and stop; and I get a FAIL!
On the phone I get the following:
START [224, 1440]
BAR [240, 1440]
Click to expand...
Click to collapse
just keep trying, that happens from time to time...its usually a faultt usb port or cord, so try differnt ports or buy a new cord, ome time I was stuck with a bad cord and literally kept trying for 2-3 hours before it finally completed the odin flash
Sent from my SAMSUNG-SGH-I337 using Tapatalk

Flashing ROM odin error

Hi,
I;ve posted this issue before but no one answered my previous thread ( T_T )
the issue still hasn't changed.
Trying to flash a Australian ROM on to my N9005.
getting this error in odin
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENE3_N9005VAUENF1_N9005XXUENE3_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> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Size)
<OSM> All threads completed. (succeed 0 / failed 1)
Flashing EU ROM's are fine as I'm currently using the UK 4.4.2 ROM N9005XXUGNG1
Please HELP; as it seems I cant use 4G with this ROM

you cant flash older fw, NG1 is new dont downgrade to older

Both 4.4.2
Thanks for reply!
Yes I'm aware that you can't downgrade.
Both ROM'S are 4.4.2 it just always fail at the same point no matter what.
The only thing that is different is one ROM is branded and one isn't
The one I'm trying to flash is Vodafone.

soulzsium said:
Thanks for reply!
Yes I'm aware that you can't downgrade.
Both ROM'S are 4.4.2 it just always fail at the same point no matter what.
The only thing that is different is one ROM is branded and one isn't
The one I'm trying to flash is Vodafone.
Click to expand...
Click to collapse
Your current version is GNG1 while the rom being flashed is ENE3 (older).
Try to flash the newer one.

vndnguyen said:
Your current version is GNG1 while the rom being flashed is ENE3 (older).
Try to flash the newer one.
Click to expand...
Click to collapse
N9005XXUGNG1 this was released in August
N9005XXUENE3 this was released in July
so I can't flash to a release that was a month old?
I thought that as long as the boot loader was the same version I could flash freely?

soulzsium said:
N9005XXUGNG1 this was released in August
N9005XXUENE3 this was released in July
so I can't flash to a release that was a month old?
I thought that as long as the boot loader was the same version I could flash freely?
Click to expand...
Click to collapse
Not sure if they have the same bootloader version?
You can only check for the bootloader version after install it.

vndnguyen said:
Not sure if they have the same bootloader version?
You can only check for the bootloader version after install it.
Click to expand...
Click to collapse
They are both KitKat 4.4.2 so I'm assuming yes

soulzsium said:
They are both KitKat 4.4.2 so I'm assuming yes
Click to expand...
Click to collapse
I'm not too sure, sorry. You have to check for the bootloader version.
Or you can also flash the modem (baseband) separately.

soulzsium said:
Hi,
I;ve posted this issue before but no one answered my previous thread ( T_T )
the issue still hasn't changed.
Trying to flash a Australian ROM on to my N9005.
getting this error in odin
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENE3_N9005VAUENF1_N9005XXUENE3_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> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Size)
<OSM> All threads completed. (succeed 0 / failed 1)
Flashing EU ROM's are fine as I'm currently using the UK 4.4.2 ROM N9005XXUGNG1
Please HELP; as it seems I cant use 4G with this ROM
Click to expand...
Click to collapse
The problem is your original pit file. As you can see problem is related to hidden partition that is to small for the image from your room that you want to flash(is the place where of in is stopping and give you error). To solve this you need to flash a pit file compatible with the room that you want to flash. What exactly do you want to achieve flashing this room anyway? ..
---------- Post added at 06:56 PM ---------- Previous post was at 06:39 PM ----------
If just LTD is your problem then check this:
<br />
Use ES File explorer or your favorite root explorer and go to data/property and find the persist.radio.lteon.xml file. Open it in Text Editor and if the value that is written is false, change it to true. Save and exit and reboot. Got the options back. Done.<br/>

Need help tab 4 10.1 lte

Hello everyone, I'm new to this tablet and I need help. Sorry for my English
I tried putting a rom with odin and fails at the end of the installation.
My tablet is t-535
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
the text in odin 3.09:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T535XXU1ANH6_T535PHE1ANH1_T535XXU1ANH6_HOME.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> 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> aboot.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> modem.bin
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> FAIL! (Size)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The solution is the pit, please give me

feuer1793 said:
Hello everyone, I'm new to this tablet and I need help. Sorry for my English
I tried putting a rom with odin and fails at the end of the installation.
My tablet is t-535
View attachment 3003086
View attachment 3003087
the text in odin 3.09:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T535XXU1ANH6_T535PHE1ANH1_T535XXU1ANH6_HOME.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> 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> aboot.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> modem.bin
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> FAIL! (Size)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The solution is the pit, please give me
Click to expand...
Click to collapse
Why a pit? I think the pit is still on the tablet but that you arez trying to flash a wrong/corrupted rom.
EDIT: you are flashing a wrong ROM. Probably because of carrier branding. Don't start playing with .pit. You will end up hard bricked after 1 little mistake!!!

Droidphilev said:
Why a pit? I think the pit is still on the tablet but that you arez trying to flash a wrong/corrupted rom.
EDIT: you are flashing a wrong ROM. Probably because of carrier branding. Don't start playing with .pit. You will end up hard bricked after 1 little mistake!!!
Click to expand...
Click to collapse
I download of sammobile 3 roms of spain, england and greece and not worked

http://forum.xda-developers.com/tab-4/general/guide-how-to-pit-file-qualcomm-device-t2932088

[q] need help install stock rom

I am not an expert at installing ROMs on Android devices. I hope someone can help.
I have a Sprint Galaxy S4, SPH-L720. I have installed CM12 but now I would like to return to a stock ROM. I downloaded several from Sammobile. Now, I cannot install them.
I have tried several versions of ODIN. Attached is the message I get when trying to flash with ODIN 3.09. I have also tried to install from an SD card using CWM and TWRP with similar failure.
Any help will be greatly appreciated.
Code:
<ID:0/005> Added!!
<ID:0/005> Removed!!
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUFNG2_L720SPTFNG2_L720VPUFNG2_HOME.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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!

laserman2431 said:
I am not an expert at installing ROMs on Android devices. I hope someone can help.
I have a Sprint Galaxy S4, SPH-L720. I have installed CM12 but now I would like to return to a stock ROM. I downloaded several from Sammobile. Now, I cannot install them.
I have tried several versions of ODIN. Attached is the message I get when trying to flash with ODIN 3.09. I have also tried to install from an SD card using CWM and TWRP with similar failure.
Any help will be greatly appreciated.
Code:
<ID:0/005> Added!!
<ID:0/005> Removed!!
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUFNG2_L720SPTFNG2_L720VPUFNG2_HOME.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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
Click to expand...
Click to collapse
You have a bad download
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Thanks for your response. I tried 5 different ROMs from Sammobile, all with the same results. I guess they could all be bad. Does anyone know of a good source for download?

laserman2431 said:
Thanks for your response. I tried 5 different ROMs from Sammobile, all with the same results. I guess they could all be bad. Does anyone know of a good source for download?
Click to expand...
Click to collapse
I've tried to install many different stock packages with pretty much the same results. Also, an image of my current settings attached. Is it a problem that I have 5.0.2 but MDL modem? Do I need to wipe everything before I run ODIN?
The only way that I can restore the phone is to ODIN install the recovery image shown below, then reinstall the CM12 ROM from the SD. When I try to install other zip packages through recovery/SD, they always fail. When I try to install other packages through ODIN, they always fail.
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.08.9-jfltespr.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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)

laserman2431 said:
I've tried to install many different stock packages with pretty much the same results. Also, an image of my current settings attached. Is it a problem that I have 5.0.2 but MDL modem? Do I need to wipe everything before I run ODIN?
The only way that I can restore the phone is to ODIN install the recovery image shown below, then reinstall the CM12 ROM from the SD. When I try to install other zip packages through recovery/SD, they always fail. When I try to install other packages through ODIN, they always fail.
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.08.9-jfltespr.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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
Since you installed Lollipop you need to wipe the internal sd. Also the stock images are here on XDA and have a much better download speed. Just look for Odin or TAR in the title. I recommend NG2. That's the latest one.

Solved.
Well. This is embarrassing. It turns out the problem was either with my USB port or my drivers. I had installed drivers and tried the other port already. Maybe it was just a bad combination.
I hope this might be helpful to other people having the same problem.
Thanks for the help!

laserman2431 said:
Well. This is embarrassing. It turns out the problem was either with my USB port or my drivers. I had installed drivers and tried the other port already. Maybe it was just a bad combination.
I hope this might be helpful to other people having the same problem.
Thanks for the help!
Click to expand...
Click to collapse
it's actually the most common problem with Odin.

Hi guy's i have a sprint s4 . While I was using custom rom it deleted my imei and now it show 00000000 how do I write it
---------- Post added at 02:54 AM ---------- Previous post was at 02:54 AM ----------
Need help
---------- Post added at 02:55 AM ---------- Previous post was at 02:54 AM ----------
I was trying to root phone and install custom rom

jaybhatia999 said:
Hi guy's i have a sprint s4 . While I was using custom rom it deleted my imei and now it show 00000000 how do I write it
---------- Post added at 02:54 AM ---------- Previous post was at 02:54 AM ----------
Need help
---------- Post added at 02:55 AM ---------- Previous post was at 02:54 AM ----------
I was trying to root phone and install custom rom
Click to expand...
Click to collapse
Just Odin stock ROM. That is the easiest way to get out back. This will restore you're phone to the state in which you received it.

But it will lock my phone back to sprint.. It's unlocked now

jaybhatia999 said:
But it will lock my phone back to sprint.. It's unlocked now
Click to expand...
Click to collapse
Sorry, I have no experience with that. But you definitely should have started with that bit of information.

Buongiorno sperando che qualcuno qui parli italiano volevo delle informazioni nel mio asus trasformers pad tf700t è stata cambiata la rom e vorrei portarla come era in origine per poi resettare il tablet

jaybhatia999 said:
But it will lock my phone back to sprint.. It's unlocked now
Click to expand...
Click to collapse
When did you install a ROM stock to an unlocked phone, the phone keeps it
I did the upgrade, MDC NG2 and kep it

I think I rooted too much?

I have a Note 4 SM-N910G that used to run on 5.1.1.
It kept bugging me for an update through OTA but couldn't cuz It was rooted
so I skimmed over the procedure and used TWRP and flashed my phone to CM13. Which ended up worse than before.
Sooo I flashed the stock rom for 6.1.1 using Odin aaand it was still laggy and now shuts down on its own.
Long story short, I re-rooted a couple of times. 30-ish. Aaaand now anything I flash my phone with keeps failing.
I know. I know. I'm an idiot.
It can still boot with VOL Down + Power button + Home though.
When I do the volume up procedure I get a "firmware upgrade encountered an issue".
Am I screwed or is there still hope?

Don't give up mate, Your phone is just laggy, not hard bricked. There is no 6.1.1 stock rom for note 4, we just got 6.0.1!!! I have flashed (rom, mods, recovery, etc) thousands of times in my note 4 and your issue may not have caused because of rooting or flashing. As u have already tried mm stock, Try to flash 5.1.1 unmodified stock rom with odin. Check the battery too, Once my friend's Note 2 had boot loop just because of the faulty battery, in live power(battery removed after samsung logo with charger plugged) it booted without a issue.

I'm having exactly the same issue, nothing I flash be it stock or rom is stable any more. Lags, then shuts off. Sometimes reboots on it's own, other times it needs the battery pulling. Nothing I have tried works

scorpienez said:
Don't give up mate, Your phone is just laggy, not hard bricked. There is no 6.1.1 stock rom for note 4, we just got 6.0.1!!! I have flashed (rom, mods, recovery, etc) thousands of times in my note 4 and your issue may not have caused because of rooting or flashing. As u have already tried mm stock, Try to flash 5.1.1 unmodified stock rom with odin. Check the battery too, Once my friend's Note 2 had boot loop just because of the faulty battery, in live power(battery removed after samsung logo with charger plugged) it booted without a issue.
Click to expand...
Click to collapse
So I left it without the battery on for a couple of hours and tried to flash the stock rom and it failed again. But halfway through though!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910GDTU1COL3_N910GVAU1COL3_N910GDTU1COL3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> FAIL! (Write)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

akeemcab26 said:
So I left it without the battery on for a couple of hours and tried to flash the stock rom and it failed again. But halfway through though!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910GDTU1COL3_N910GVAU1COL3_N910GDTU1COL3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> FAIL! (Write)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Use Kies to recover your phone. Choose firmware upgrade & initialisation and enter your full model number (for example SM-N910F) & serial number.

akeemcab26 said:
So I left it without the battery on for a couple of hours and tried to flash the stock rom and it failed again. But halfway through though!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910GDTU1COL3_N910GVAU1COL3_N910GDTU1COL3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> FAIL! (Write)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
See if you have checked repartition. uncheck it if it is checked(Uncheck this just before you are about to click on start) and flash again.

sanjaydev said:
See if you have checked repartition. uncheck it if it is checked(Uncheck this just before you are about to click on start) and flash again.
Click to expand...
Click to collapse
It's always unchecked though. Still the same result. Messes up at system.img.ext4

houstie said:
Use Kies to recover your phone. Choose firmware upgrade & initialisation and enter your full model number (for example SM-N910F) & serial number.
Click to expand...
Click to collapse
Kies 1? 2? or 3?
I'm using 3 btw.
Whenever I choose firmware upgrade & initialization it hangs when I search for my phone's model.

Ooookay. It said I needed a PIT File. I got one scouring the internet and did a flash.
I got this.
<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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> FAIL! (Write)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
Now I read somewhere that I need to enable something in my android to make the system.img.ext4 not fail.
But how can I enable that option if I can't even finish flashing? :|
If I boot it normally, I get firmware upgrade encountered and issue.

Rafa5e5t6yf said:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
all I'm seeing are broken links :\

akeemcab26 said:
Kies 1? 2? or 3?
I'm using 3 btw.
Whenever I choose firmware upgrade & initialization it hangs when I search for my phone's model.
Click to expand...
Click to collapse
Kies 3. Make sure you use capital letters when entering your phone model.

houstie said:
Kies 3. Make sure you use capital letters when entering your phone model.
Click to expand...
Click to collapse
I enter the phone model, SM-N910G, click ok, and says do not remove usb connection.
after the preparation for the update finishes Kies 3 just turns black and nothing in it can be clicked.
My phone's firmware is now 6.0.1
The errors I get are
system.img.ext4 fail
rpm.mbn fail
firmware encountered an issue
mmc read failed to boot normal
either of the 4 show up after flashing.
tried flashing with the PIT file + the stock firmware, PIT file only, firmware only,
system.img.ext4 fails. Always does. But last night I tried it again and it went halfway through! But still failed.

Here You go,
1. Use Odin v3.10, go to PIT tab and select your device specific pit file first.
2. Click AP on the right side and select the latest firmware .tar.md5 file.
3. Go to options tab and select Auto-reboot, clear nand partition, re-partition, F.reset time & bootloader update as you need to format emmc (nand).
4. Flash the device, wait for it to complete and give it 5 mins to boot.
5. Once rebooted you may get stuck at samsung logo, dont worry, just go to stock recovery by pulling battery and holding down volup+home+power and perform a factory reset and clear cache.
6. Might take upto 5mins, but works like a charm.

akeemcab26 said:
I tried flashing with the PIT file + the stock firmware, PIT file only, firmware only,
system.img.ext4 fails. Always does. But last night I tried it again and it went halfway through! But still failed.
Click to expand...
Click to collapse
Use this PIT file I extracted from latest 6.0.1 binary stock rom.

vighneshpillai90 said:
Here You go,
1. Use Odin v3.10, go to PIT tab and select your device specific pit file first.
2. Click AP on the right side and select the latest firmware .tar.md5 file.
3. Go to options tab and select Auto-reboot, clear nand partition, re-partition, F.reset time & bootloader update as you need to format emmc (nand).
4. Flash the device, wait for it to complete and give it 5 mins to boot.
5. Once rebooted you may get stuck at samsung logo, dont worry, just go to stock recovery by pulling battery and holding down volup+home+power and perform a factory reset and clear cache.
6. Might take upto 5mins, but works like a charm.
Click to expand...
Click to collapse
Thanks for the reply!
I used the PIT file you gave me and used
N910GDTU1DPD4_N910GODD1DPB5_N910GDDU1DPB4_HOME.tar and
N910GDTU1DPD4_N910GODD1DPB5_N910GDDU1DPB4_HOME.tar
but both still gave me the system.img.ext4 fail
I checked
auto reboot,
repartition,
f. reset time,
nand erase all
and phone bootloader update on the third try
but still failed and gave me a new error written in blue or grey not sure but it was something like
odin failed to write.
edit: I can now boot to android recovery!
but at the very bottom it says
supported api: 3
dm-verity verification failed...
E: failed to mount /system (invalid argument)

Still hoping someone could help me!