Okay. Some history to start with...
I got Chinese version of Galaxy Note which runs i9220 ROM and been trying to flash with HK/EU ROM last several days but out of luck so far. (And whenever failed, I re-loaded stock ROM found from Samsung-updates.com site for i9220. It then worked fine but still with original problem unsolved.
I then tried one last method that I saw someone succeed flashing Chinese ROM via use of PIT file came from one of the other downloads.. yeah, I didn't check the source PIT came from before try... which is my bad.
Without confirming it, I instantly located "u1_02_20110310_emmc_EXT4.pit" that's packaged with odin 1.85 and carelessly gave a try.
And now... my precious GalaxyNote became the most expense brick in my house and am looking for professional help from you guys.
Steps I did before bricking and tried:
1. Load GalaxyNote in Download mode (volume down + home + power)
2. Launch Odin 1.85 and no change to default setting. (Check mark on #Auto Reboot & #F.Reset Time, uncheck on #Re-Partition & #Flash Lock)
3. Set PIT to "u1_02_20110310_emmc_EXT4.pit"
4. Set PDA to "N7000XXKL7_N7000OXAKL7_N7000XXKL7_HOME"
5. Click #Start
Soon after around 5%, it failed.
I then attempted to restore factory ROM via usual way - doing same as above except no PIT this time and choosing original stock ROM for i9220.
It failed! OMG...
I then tried again (#1 ~ 5 above) but this time, check on #Re-partition for luck. Still no luck!
I then downloaded Heimdall1.3.1 and tried to extract PIT file but the tool fails as well and gives "ERROR: Failed to access device. libusb error: -12".
At all times, GalaxyNote screen shows android icon with 'Downloading... Do not turn off target!!'. And the device can also be seen from odin.
Soon as turn off galaxynote and disconnect from computer, it shows 'Software Update Fail' message.
How I can restore to original factory setting? And if possible, how I can restore to EU or Hong Kong ROM?
My Chinese friend has the same device as mine. In this case, will Heimdall tool help extracting PLT from it and help restoring my device via odin?
Your professional help is sincerely appreciated!!!!
Resolved
Using "Q1_20110914_16GB.pit" and re-partition check from odin while flashing to original stock rom has resolved an issue.
Referred from following thread.
http://forum.xda-developers.com/showthread.php?t=1533214
Never use pit and do not tick repartion when flashing.
bootloader?
U are fine. It is a recovery issue and not a bootloader. Install custom recovery and flash stock firmware w odin. Oh yea, and profit.
Toolmighty said:
U are fine. It is a recovery issue and not a bootloader. Install custom recovery and flash stock firmware w odin. Oh yea, and profit.
Click to expand...
Click to collapse
Why do you revive an old thread? The user has resolved it the day after his problem.
Hello everybody,
I've been following some posts around the forum for some time now.
So I decided to flash my Samsung Galaxy S + with the newest stock firmware.
I first tried Odin, but that was no succes because VirtualBox couldn't handle it and just crashed when it started to upload the roms into my phone.
So it was bricked first, but got it back up and running.
I'm using linux as my OS, so of course I found Heimdall.
This seemed a nice tool, but I found out that the package format needs to be else then how the stock roms are delivered.
At last I tried to flas using the dd method.
I did the command dd if=...img of=dev/block/mmcblk0p.. bs=4096 for all partition images.
I managed to start the flashed roms. Only I found out that after installing some apps and after a few reboots the system starts to get faulty.
All of a sudden Play Store doesn't install apps anymore "Package Invalid" error, and for some reason also after each reboot more apps start to dissappear (get replaced by sd-card icon but unable to open or reïnstall).
Also I did a factory reset after dd'd the images into my phone, cause that's what everybody recommends.
The roms I've tried so far were XXKQB and XXKP1, both with the same issues.
The original firmware which came with my phone is: XXKPG.
Hopefully somebody can point me in the right direction in getting a newer rom onto my pda.
Greetings PsychoGame
I suggest you use a PC, im sure you will find one somewhere, friend/neighbour/relative. Then use Odin to flash.
Odin firmwares
Sammobile.com You should find I9001 firmware here
http://forum.xda-developers.com/showthread.php?t=1102881 Not sure if compatible with I9001
Or if your persistent have you tried here. **Check if compatible** If its an older firmware, connect to Kies and it should update to the latest.
JUST NOTICED THE I9001 CHECK THAT THE FIRMWARE IS COMPATIBLE
I agree with Talon, use ODIN on a windows-based machine... In any case you can always install windows on a different partition, but it's not worth it. For me the whole flashing process only lasted for 4 minutes, so just grab a PC somewhere and install it...
I also recommend KQE insted of KQB as the wifi is fixed
I rooted my note 5 the other day using Odin which was successful , decided I wanted to unroot since I have an sm-920T and keep the getting a pop up message due to a t-mobile app and being rooted. I deleted the t-mobile app but kept getting the pop up message associated with it.
I downloaded some stock roms and tried flashing with Odin but it kept failing to write and the process of flashing only worked in twrp which I did. I had issues with my phone randomly restarting and often too. I did some googling and figured I had a corrupted pit file. I download firmware boh6 and the associated pit file and followed the directions to the letter and I keep coming up with a write fail in odin. Any ideas on how to fix this or solve the issue?
Bobby45512 said:
I rooted my note 5 the other day using Odin which was successful , decided I wanted to unroot since I have an sm-920T and keep the getting a pop up message due to a t-mobile app and being rooted. I deleted the t-mobile app but kept getting the pop up message associated with it.
I downloaded some stock roms and tried flashing with Odin but it kept failing to write and the process of flashing only worked in twrp which I did. I had issues with my phone randomly restarting and often too. I did some googling and figured I had a corrupted pit file. I download firmware boh6 and the associated pit file and followed the directions to the letter and I keep coming up with a write fail in odin. Any ideas on how to fix this or solve the issue?
Click to expand...
Click to collapse
Install Smart Switch (Kies for newer models) on a computer, and use the option Emergency software recovery and initialization.
Hello,
I have been trying to fix a friends t-mobile phone (note 5), he got it from ebaya, dumb i know. It seems like it was rooted because it wouldn't make calls and had super user. I loaded the official latest software via odin and only made it worse, wont even load to OS now.
I have loaded several SWs to try and restore (using odin)
these are the SWs i tried
N920TUVU1AOGE_N920TTMB1AOGE_N920TUVU1AOGE_HOME.tar (.CM fail) original note 5 tmobile sw.
N920TUVU1BOH4_N920TTMB1BOH4_N920TUVU1BOH4_HOME.tar (.CM fail) revision, still official.
N920TUVU2DPD1_N920TTMB2DPD1_N920TUVU2DPD1_HOME.tar (pass) latest official
Odin gives me a consistent pass with official N920TUVU2DPD1_N920TTMB2DPD1_N920TUVU2DPD1_HOME software
It keeps rebooting into recovery mode,
Tried doing a wipe from recovery mode. Error - (Failed to mount /preload (no such file or directory)
Every time the device loads into recovery mode it shows error...
"dm-verity verification failed...
need to check drk first..."
I dont know what to do, knox shows 0x0
used different PCs
different cords
different odins
i must have installed it a dozen times, i even removed the cache file and re packaged the .tar any help would be fantastic.
westsidekino said:
Hello,
I have been trying to fix a friends t-mobile phone (note 5), he got it from ebaya, dumb i know. It seems like it was rooted because it wouldn't make calls and had super user. I loaded the official latest software via odin and only made it worse, wont even load to OS now.
I have loaded several SWs to try and restore (using odin)
these are the SWs i tried
N920TUVU1AOGE_N920TTMB1AOGE_N920TUVU1AOGE_HOME.tar (.CM fail) original note 5 tmobile sw.
N920TUVU1BOH4_N920TTMB1BOH4_N920TUVU1BOH4_HOME.tar (.CM fail) revision, still official.
N920TUVU2DPD1_N920TTMB2DPD1_N920TUVU2DPD1_HOME.tar (pass) latest official
Odin gives me a consistent pass with official N920TUVU2DPD1_N920TTMB2DPD1_N920TUVU2DPD1_HOME software
It keeps rebooting into recovery mode,
Tried doing a wipe from recovery mode. Error - (Failed to mount /preload (no such file or directory)
Every time the device loads into recovery mode it shows error...
"dm-verity verification failed...
need to check drk first..."
I dont know what to do, knox shows 0x0
used different PCs
different cords
different odins
i must have installed it a dozen times, i even removed the cache file and re packaged the .tar any help would be fantastic.
Click to expand...
Click to collapse
Maybe try using the PIT file to do repartitioning of the partitions? Which recovery is on it?
MrMike2182 said:
Maybe try using the PIT file to do repartitioning of the partitions? Which recovery is on it?
Click to expand...
Click to collapse
I can try that, can you recommend a tutorial on how to do it for the note 5?
westsidekino said:
I can try that, can you recommend a tutorial on how to do it for the note 5?
Click to expand...
Click to collapse
Since you said it was already rooted, why don't you go to the T-Mobile thread download and flash one of the Roms and kernels they have instead of trying to flash stock?
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.