Hi i was trying to convert my tmobile n960u 512gb to u1 firmware but system keeps getting stuck on system.img.ext4 for hours no luck. When i try to flash back to stock rom it gets stuck at vendor.img.ext4 no matter what roms i try it doesnt flash all the way. any help guys. Orginally the firmware on the phone was N960USQS2CSGB and i am flashing with patched odin.
Thanks
uzairf said:
Hi i was trying to convert my tmobile n960u 512gb to u1 firmware but system keeps getting stuck on system.img.ext4 for hours no luck. When i try to flash back to stock rom it gets stuck at vendor.img.ext4 no matter what roms i try it doesnt flash all the way. any help guys. Orginally the firmware on the phone was N960USQS2CSGB and i am flashing with patched odin.
Thanks
Click to expand...
Click to collapse
whats the new u1 ure flashing to?
also maybe ure usb cable is at fault. also if ure on win 10 make sure ure on max performance in power settings.
and lastly mabe a bad downlaod. check checksum. maybe use samfirm tool v0.3.6 to dl u1 firmware
I tried All sorts of cables on the laptop. On my desktop odin sees the port but doesnt flash at all just says completed or gets stuck on initializing. The firmware that completes all the way till the end and gets stuck is N960USQU2CSI1_CCT. Also i tried to write the orginal firmware i was on but it gets stuck on vendor.img.ext4 and nothing happens. At the moment im trying to download the latest tmboile CSI1 version to see if it flashes.
uzairf said:
I tried All sorts of cables on the laptop. On my desktop odin sees the port but doesnt flash at all just says completed or gets stuck on initializing. The firmware that completes all the way till the end and gets stuck is N960USQU2CSI1_CCT. Also i tried to write the orginal firmware i was on but it gets stuck on vendor.img.ext4 and nothing happens. At the moment im trying to download the latest tmboile CSI1 version to see if it flashes.
Click to expand...
Click to collapse
what exact version if Odin are you using?
also state the exact files you are loading in each slot in the odin app.
3.13.3b patched version that i got from the forum.
uzairf said:
3.13.3b patched version that i got from the forum.
Click to expand...
Click to collapse
and?
bober10113 said:
also state the exact files you are loading in each slot in the odin app.
Click to expand...
Click to collapse
Bl tab : BL_n960USQUSCSI1
AP TAB: AP_N960USQU2CSI1
CP TAB: N960USQUS2CSI1
CSC TAB: CSC_OMC_OYN_N960UOYN2CSI1
I have 2 more files Home_csc_OMC_OYN
Userdata_TMB_N960USQS2CSGB
i only try to load 4.
Thanks
uzairf said:
Bl tab : BL_n960USQUSCSI1
AP TAB: AP_N960USQU2CSI1
CP TAB: N960USQUS2CSI1
CSC TAB: CSC_OMC_OYN_N960UOYN2CSI1
I have 2 more files Home_csc_OMC_OYN
Userdata_TMB_N960USQS2CSGB
i only try to load 4.
Thanks
Click to expand...
Click to collapse
try adding userdat in the last slot/tab
plus again besure your files arent corrupt.(validate checksum or re downlaod with samfirm tool)
Related
I tried to flash the stock rom via odin but it failed and now i dont have an operating system installed.. Smart switch doesnt work for ATT variants and im just here with a brick.. I can get to download but odin says removed every time..
What Odin version did you use? MUST use Odin v3.10.6
vontokkerths said:
I tried to flash the stock rom via odin but it failed and now i dont have an operating system installed.. Smart switch doesnt work for ATT variants and im just here with a brick.. I can get to download but odin says removed every time..
Click to expand...
Click to collapse
I used Odin 3.10.6 but while flashing odin told me the device got removed (still connected to the PC)
Try it again. Put each of the 4 files in its corresponding spot in odin matching each file with the spot (BL, AP, CP and CSC), put S6 in download mode, connect it to the pc via usb, press start in odin after it recognizes the phone. Use the original usb that came with the S6.
vontokkerths said:
I used Odin 3.10.6 but while flashing odin told me the device got removed (still connected to the PC)
Click to expand...
Click to collapse
I tried to flash it without the auto reboot option and it passed, im gonna see if i have software. Thanks!
If it passed you should have system installed.
vontokkerths said:
I tried to flash it without the auto reboot option and it passed, im gonna see if i have software. Thanks!
Click to expand...
Click to collapse
I rooted my phone and wanted to flash back to stock so I can update with the OTA and re-root, but I downloaded the zip for the AT&T tar files and everything seemed to pass MD5 checks and went okay, but as soon as I hit Start, the program just continues to say NAND Write Start for over 20 minutes, and won't flash, how do I go about re-trying this without bricking my device? It's still plugged in atm in download mode.
What version of Odin are you using? I had this problem because I had v3.10 and the s6 is not compatible with that version, you have to have v3.10.6.
Mine did that, I closed odin, reopened, put each .md5 file in right section (AP in AP, BL in BL, CSC in CSC, ect) and it worked
If Odin is having trouble flashing to your phone. Here is some simply tips and tricks to try.
1. Try flashing everything except for the bootloader .
2. Try running Odin as admin.
3. Try upgrading to the newest Odin available.
4. If all else fails, open Samsung Kies, and go to emergency recovery, put your model # and serial # in, and it will flash your phone to stock for you, then you can try again.
5. Also make sure all of the correct drivers are installed for your phone, sometimes Windows can be bad about that. Try getting drivers from samsung directly.
6. Try a new USB Cable, as crazy as that is, I have had some not work, and others work fine.
7. Try a different USB Port on the PC, or restart the PC.
I hope this helps.
I tried just flashing the ROM and CSC and it flashed just fine, I left out the CP file, what is that? Everything seems fine just flashing the ROM and CSC, but do I need to flash the CP file too, for anything?
CSC is the consumer software customization and is specific to geographical region and carriers. It contains the software packages specific to that region, carrier branding and also APN settings for data connection, MMS etc for your service provider.
I hope this helps
I didnt get it. Do you mean to put each .md5 file in all sections? ? Please help me
_Dennis_ said:
Mine did that, I closed odin, reopened, put each .md5 file in right section (AP in AP, BL in BL, CSC in CSC, ect) and it worked
Click to expand...
Click to collapse
Please help me out. I am having same problem NAND WRITE stuck.
Solved
Thanks everyone for your post. But what I did is, just downloaded the Odin v3.10.6......that worked with S6. And I guess S6 is not compatible to other earlier versions of odin. So better try with Odin v3.10.6.
Nand write start fail solved
I have solved using Odin3 v3.10.7 with firmware VZW-G920VVRU4BOK7-20151211140939 and Windows 7 for Galaxy S6 SM-G920V
NAND stucked
kishor1995 said:
Thanks everyone for your post. But what I did is, just downloaded the Odin v3.10.6......that worked with S6. And I guess S6 is not compatible to other earlier versions of odin. So better try with Odin v3.10.6.
Click to expand...
Click to collapse
can u tell the steps u did? to do it
Help
I am having the same issue and I have done everything suggested here but still is NAND fail. Any ideas
bonniegertz said:
I am having the same issue and I have done everything suggested here but still is NAND fail. Any ideas
Click to expand...
Click to collapse
Were you finally able to get it to work?
Its working!
Zoide_ said:
Were you finally able to get it to work?
Click to expand...
Click to collapse
Yes, I gave up but a friend of mine found a thread that talks about using Kies to bring it back to factory default. You need to know the serial # and IMEI # If you can find this information, you can reset it using Kies.
Had the same problem. Used Odin 3.10.6
But before all this, I connected phone with debugging enabled in windows and authorized it, the problem never resurfaced
Hi everyone i desperately need some help, i had a rooted note 4 gave it to my cousin in greece, he just came back and i told him i would update it, i downloaded tekx"s rom and installed i did a full wipe as usual, after it installed the phone kept on rebooting over and over again, so i thought maybe i had to update the firmware, i tried doing that but i keep getting a fail message i cant update anything. so i rerooted the phone tried updating the firmware again and still getting a fail message. so now i dont have anything on the phone i am only able to go into recovery or down load mode, cant go into any type of settings on the phone incase i forgot to unlock something in there. i've looked everywhere on the net and cant find any type of solution, can someone help me out please? Thank you
panitsos said:
Hi everyone i desperately need some help, i had a rooted note 4 gave it to my cousin in greece, he just came back and i told him i would update it, i downloaded tekx"s rom and installed i did a full wipe as usual, after it installed the phone kept on rebooting over and over again, so i thought maybe i had to update the firmware, i tried doing that but i keep getting a fail message i cant update anything. so i rerooted the phone tried updating the firmware again and still getting a fail message. so now i dont have anything on the phone i am only able to go into recovery or down load mode, cant go into any type of settings on the phone incase i forgot to unlock something in there. i've looked everywhere on the net and cant find any type of solution, can someone help me out please? Thank you
Click to expand...
Click to collapse
Flash latest stock firmware in odin .
Once odin shows PASS go to stock recovery and do factory reset and wait 15 minutes to boot.
Do you have N910T tmobile note 4 ?
Link below for n910t latest firmware.
Extract the file and flash using odin choose AP
https://www.androidfilehost.com/?fid=385035244224408290
Trex888 said:
Flash latest stock firmware in odin .
Once odin shows PASS go to stock recovery and do factory reset and wait 15 minutes to boot.
Do you have N910T tmobile note 4 ?
Link below for n910t latest firmware.
Extract the file and flash using odin choose AP
https://www.androidfilehost.com/?fid=385035244224408290
Click to expand...
Click to collapse
i tried the cog2 the dok firmware nothing it fails all the time. if i try flashing this newer firmware and it works by some chance then i'm worried i wont be able to get a rom to work because from what i've seen most roms are cog2 or doc 6
panitsos said:
i tried the cog2 the dok firmware nothing it fails all the time. if i try flashing this newer firmware and it works by some chance then i'm worried i wont be able to get a rom to work because from what i've seen most roms are cog2 or doc 6
Click to expand...
Click to collapse
yes i have a tmboile note 4
Hello,
Im trying to recover my galaxy s10 for T-Mobile. I flash the correct firmware via Odin, its flashes successfully with no issues, and every time, it gets all the way to the T-Mobile boot screen, freezes, and then starts again at the Samsung screen. When I boot into recovery, I can see at the bottom:
E:[libfs_mgr]Unable to disable quotas on /dev/block/bootdevice/by-name/userdata because /system/bin/tune2fs is missing
I have tried factory resetting from recovery, but it continues to bootloop. Any help would be appreciated, thanks in advance
You used the patched version of Odin right? Reflash the firmware. Use one or 2 version firmwares down from the current if the current firmware doesn't work.
StoneyJSG said:
You used the patched version of Odin right? Reflash the firmware. Use one or 2 version firmwares down from the current if the current firmware doesn't work.
Click to expand...
Click to collapse
I downloaded the newest Odin from SamMobile. Will I be to flash an older firmware, if my bootloader is on the newest?
This error message is normal /system/bin/tune2fs is missing
A full odin Flash should cure it, you may even have to look into the re partition option where you specify the pit file. (extracted from the CSC file).
I've flashed with patched Odin, still same. I'm fairly new to Samsung flashing, how would I go about extracting that file?
OnePlusPat16 said:
I've flashed with patched Odin, still same. I'm fairly new to Samsung flashing, how would I go about extracting that file?
Click to expand...
Click to collapse
try this https://www.youtube.com/watch?v=dfRICZMTPGU
Hi, I need some help flashing my device. Somehow, my device got stuck in a boot loop last night, and I've been having trouble getting it to work again. I think my phone may have reset during an update while in my pocket as I was laying down on the couch last night.
I found my device firmware on sammobile according to the specs listed below. I've downloaded Odin 3.14.4 and have flashed my phone successfully 3 or 4 times at this point, but when it restarts post-flash, it keeps booting into download mode. I can't seem to get it to boot into recovery mode or just turn it off at all anymore. No matter what, it boots straight into download mode.
Does anyone know of a way that I can force it into recovery mode so that I can try restarting it normally? This is my first time flashing a phone, so I have little experience here though I am competent with technology and willing to try further tricks to get it working.
I'm just looking for recommendations and hoping that my phone isn't bricked. I've only owned it for 3 months at this point, so I'm very disappointed.
Thanks in advance for the help, and I'm happy to provide any more information if it helps you come up with any potential solutions.
Specs
Phone: Samsung 21 Ultra
Model: SM-G998U1
PDA: G998U1UES5CVCB
Carrier: XAA
Text on download mode screen:
<!>
partition recovery
Reason avb.slot_verify.c:276: ERROR: recovery: Hash of data does not match digest in descriptor. [2nd]
Calculated Hash of (recovery) : 9C3B9F195F, (VEMETA) : 1C38BF9F7A
Samsung recovery, G998U1UES5CVCB, 50338466R
VBMETA G998U1UES5CVCB, 50341365R
Do you have TWRP installed? Try flushing it. You can also follow Dr. Ketan ROM installation guide, it's very straightforward.
shaharofir said:
Do you have TWRP installed? Try flushing it. You can also follow Dr. Ketan ROM installation guide, it's very straightforward.
Click to expand...
Click to collapse
I don't. I was looking at that post earlier and noticed that it mentioned the G998B/N model. Mine is the G998U1, so I was worried that it wouldn't work or cause more problems. I couldn't find any versions of TWRP that matched my specific model.
your bootloader version is above v1. cannot be unlocked. you need to flash a samsung rom. try redownloading it if you can't boot. and twrp probably won't work either.
you're saying that if you hold the vol up key and power button when the device is off that it won't reboot into recovery at all?
ffuser1 said:
your bootloader version is above v1. cannot be unlocked. you need to flash a samsung rom. try redownloading it if you can't boot. and twrp probably won't work either.
you're saying that if you hold the vol up key and power button when the device is off that it won't reboot into recovery at all?
Click to expand...
Click to collapse
I was actually able to get it to boot into recovery mode this morning. The download mode timed out and the phone shut off which allowed me to finally get into it. I tried redownloading the same rom I got from sammbolie again a few mins ago but still no luck.
Try another firmware with the same BL revision, CVC9 for example
dipotis said:
Hi, I need some help flashing my device. Somehow, my device got stuck in a boot loop last night, and I've been having trouble getting it to work again. I think my phone may have reset during an update while in my pocket as I was laying down on the couch last night.
I found my device firmware on sammobile according to the specs listed below. I've downloaded Odin 3.14.4 and have flashed my phone successfully 3 or 4 times at this point, but when it restarts post-flash, it keeps booting into download mode. I can't seem to get it to boot into recovery mode or just turn it off at all anymore. No matter what, it boots straight into download mode.
Does anyone know of a way that I can force it into recovery mode so that I can try restarting it normally? This is my first time flashing a phone, so I have little experience here though I am competent with technology and willing to try further tricks to get it working.
I'm just looking for recommendations and hoping that my phone isn't bricked. I've only owned it for 3 months at this point, so I'm very disappointed.
Thanks in advance for the help, and I'm happy to provide any more information if it helps you come up with any potential solutions.
Specs
Phone: Samsung 21 Ultra
Model: SM-G998U1
PDA: G998U1UES5CVCB
Carrier: XAA
Text on download mode screen:
<!>
partition recovery
Reason avb.slot_verify.c:276: ERROR: recovery: Hash of data does not match digest in descriptor. [2nd]
Calculated Hash of (recovery) : 9C3B9F195F, (VEMETA) : 1C38BF9F7A
Samsung recovery, G998U1UES5CVCB, 50338466R
VBMETA G998U1UES5CVCB, 50341365R
Click to expand...
Click to collapse
Was your phone carrier branded originally? And you're flashing the u1 firmware so you won't have bloat? Or is it originally an unlocked model? I ask because if it was originally carrier branded and you used the Odin version from the SamMobile site then that may be the reason. U need to use the modded version of Odin that's floating around somewhere. If you need it I can upload it to my drive and let you download that version. I literally just flashed VCB last night and everything worked just fine.
JG96EVO said:
Was your phone carrier branded originally? And you're flashing the u1 firmware so you won't have bloat? Or is it originally an unlocked model? I ask because if it was originally carrier branded and you used the Odin version from the SamMobile site then that may be the reason. U need to use the modded version of Odin that's floating around somewhere. If you need it I can upload it to my drive and let you download that version. I literally just flashed VCB last night and everything worked just fine.
Click to expand...
Click to collapse
No, I bought my phone directly from Samsung, and I bought the unlocked model. I chose the rom from sammobile that looked to be exactly what my phone originally had on it based on the model and PDA/carrier info I found when looking through the recovery logs on the phone when the issue first occurred, before flashing anything onto it. If you think the modded Odin might work, I'd be willing to give it a shot.
I can't tell you the exact differences, but I would flash with the patched odin. it's on xda if you search for it.
No luck so far. I've downloaded the patched Odin software and have tried flashing my device numerous times with the same result. I also tried tried flashing firmware that I found on Frija instead of the firmware I originall downloaded from sammobile to see if anything would be different, and that didn't seem to make a difference.
My best guess (could be wrong) is that it doesn't like the bootloader tied to the firmware I've tried to flash onto the device. I've spent a good while searching firmware that uses the version of the bootloader it wants, but I can't find it anywhere. At this point, I'm all out of ideas, but I appreciate everyone's responses and advice.
So this is what you are saying: You're using patched odin (https://forum.xda-developers.com/attachments/odin3-v3-14-1_3b_patched-zip.5158507/) to flash an official U1 Samsung rom (https://samfw.com/firmware/SM-G998U1/XAA/G998U1UES5CVCB for example) in the AP slot, all other slots are empty, without any odin errors during flash, and are then unable to boot, with partition errors seen in download mode? This is very unusual... flashing in download mode overwrites partitions, including recovery. I would assume if there are no odin errors, then the rom file is not corrupt and the sd card is not damaged. I don't know much about flashing through odin with a locked bootloader, maybe unpatched odin with the above instructions is worth a shot. I'm out of ideas aside from the sd card being damaged or trying unpatched odin if the above instructions with patched odin are resulting in recovery partition errors. I don't think you can access adb in download mode either.
You can extract the CSC file using 7zip. In there you will find the PIT file and you can try flashing it with repartition selected and inserting the PIT file in developers section of Odin.
ffuser1 said:
So this is what you are saying: You're using patched odin (https://forum.xda-developers.com/attachments/odin3-v3-14-1_3b_patched-zip.5158507/) to flash an official U1 Samsung rom (https://samfw.com/firmware/SM-G998U1/XAA/G998U1UES5CVCB for example) in the AP slot, all other slots are empty, without any odin errors during flash, and are then unable to boot, with partition errors seen in download mode? This is very unusual... flashing in download mode overwrites partitions, including recovery. I would assume if there are no odin errors, then the rom file is not corrupt and the sd card is not damaged. I don't know much about flashing through odin with a locked bootloader, maybe unpatched odin with the above instructions is worth a shot. I'm out of ideas aside from the sd card being damaged or trying unpatched odin if the above instructions with patched odin are resulting in recovery partition errors. I don't think you can access adb in download mode either.
Click to expand...
Click to collapse
Interesting. I did not try it with only the AP slot populated. I thought you needed to always flash with the BL, AP, CP, and CSC.
wait, i messed up. if it has all of those files, flash them. my bad. i was thinking about custom roms - sorry about that.
Hey everyone, just wanted to make a final update.
I ended up bringing my phone into ubreakifix after trying just about everything I could, and they were not able to fix it either. They suggested that it might be a hardware issue and recommended sending it to Samsung for repair. I then sent it over to Samsung, and they confirmed that it was an issue with my motherboard. Samsung replaced my motherboard, and the phone is back in action. Since I only had my phone for about 6 months, it was still under warranty.
I appreciate everyone who took their time to provide me with advice. I hope that this post may help someone experiencing a similar issue to mine in the future.