Related
Edit: Problem solved.
To preface all of this, I understood the risks I was taking. I may have accidentally messed something up due to my own error and I understand this. The end.
I have the SM-T810 model. First I flashed the Permissive Lollipop 5.1.1 kernel through Odin along with the TWRP recovery. All went well. I made a backup through TWRP. Tablet worked perfectly upon reboot.
Then I went to flash the Optimal Rom according to the directions:
"1. Download ROMzip to your SD Card
2. BACKUP YOUR CURRENT ROM - I cannot stress this enough. Don't ask why, just do it.
3. You will need to flash the firmware package in ODIN that matches the base of the current ROM, located in post 3 here
4. Flash ROMzip in recovery
5. Reboot"
So Before flashing the ROMzip in recovery, I flashed the provided firmware package in ODIN, "810_oh7_fw_BigBot96.tar.md5" This is where Odin failed and things got messed up.
After restarting the tab it gets stuck at the "Galaxy Tab S2" logo screen. At the top in red letters it reads "Kernel is not seandroid enforcing."
I am still able to get into recovery, which I factory resetted, wiped, formatted, the whole nine yards in a million different combinations. Afterwards I would restore the backup I created earlier (which always appears to be successful), however when I go to reboot from recovery TWRP tells me there is no OS installed and goes back to being frozen at the boot logo. Weird.
Whenever I try to flash stock from Odin, the images provided on these forums, it fails
"<ID:0/005> NAND Write Start!!
<ID:0/005> boot.img
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)"
Where did I go wrong? I may have accidentally forgot to run odin as administrator, maybe that was it? If anyone has any questions I'll be glad to answer and I appreciate any help that I can get. Thanks.
I would guess that the stock ROM you try to flash has an older bootloader version than the ROM you had flashed before. The bootloader is not downgradeable.
So look for a 5.1.1 stock ROM with a "2B" in the version number ( a canadian and some other version is available). Then Odin should flash it just fine.
hasenbein196601 said:
I would guess that the stock ROM you try to flash has an older bootloader version than the ROM you had flashed before. The bootloader is not downgradeable.
So look for a 5.1.1 stock ROM with a "2B" in the version number ( a canadian and some other version is available). Then Odin should flash it just fine.
Click to expand...
Click to collapse
I have a feeling you are right, since I am able to flash other things through odin on the tab (like the custom kernel), just not the stock rom. Also, I just recently bought the tablet and stupidly updated it immediately upon unboxing, so I probably do have a newer bootloader. If anyone knows where I can get a newer stock ROM I would be very grateful.
bullhound said:
I have a feeling you are right, since I am able to flash other things through odin on the tab (like the custom kernel), just not the stock rom. Also, I just recently bought the tablet and stupidly updated it immediately upon unboxing, so I probably do have a newer bootloader. If anyone knows where I can get a newer stock ROM I would be very grateful.
Click to expand...
Click to collapse
It should be available on SamMobile. Also when flashing your twrp backup make sure you are restoring system.
Lastly you don't need to flash the firmware package just the rom as you are already updated by the looks of things.
So just find the latest stock firmware then flash that then the rom.
ashyx said:
It should be available on SamMobile. Also when flashing your twrp backup make sure you are restoring system.
Lastly you don't need to flash the firmware package just the rom as you are already updated by the looks of things.
So just find the latest stock firmware then flash that then the rom.
Click to expand...
Click to collapse
Thanks for the tips. Would a newer 5.0.2 ROM possibly have the newer bootloader, or would I need to find a 5.1.1 ROM which is what I had previously installed? Having trouble finding a 5.1.1 ROM
Wow that was stupid of me. I never tried flashing the Optimal ROM itself because I initially freaked out after flashing the firmware. My tablet is back in action with Optimal ROM
bullhound said:
Wow that was stupid of me. I never tried flashing the Optimal ROM itself because I initially freaked out after flashing the firmware. My tablet is back in action with Optimal ROM
Click to expand...
Click to collapse
No worries, thanks button is above. ?
Hello XDA members and devs. I have stumbled upon an issue that seems to be close to un-fixable. I have the SM-N910T obviously. I am on DOK2, every rom Touch Wiz and Cyanogenmod flashed correctly a couple of months ago. Now the only things I can flash are DOK2 stock firmware via ODIN, and then I can successfully flash TWRP 2.8.7.0, the only ROM I can flash is Maximum Overdrive 4.0.1 +(all upper updates.) I got a hold of Max OD dev and he said it's because of the 3 mount lines he added to the top of his updater-script. So I added those lines to updater-scripts of other roms and none worked. Some other roms have many other mount points and important lines of code in the updater-script that should not be removed or edited. I want to go back to Cyanogenmod, and others either 12.1 nightlies, or the new CM Remix 13.0 which worked before all the others stopped working at the same time.
Yes I also tried this.
Quote:
Originally Posted by sudoBacon
I tried before. Doesnt work onlky DOK2 or maximum ods 4.0.1 + no other roms
After you flash D0K2 firmware - Use the stock Recovery and Factory Reset - That will get you out of the bootloop - Just remember that your internal storage will be wiped!
I also get the same issue after attempting to downgrade which always fails. Used to be able to downgrade and upgrade firmware's as well, now I cant. I got the dev of Max OD rom to pull a DOK2 pit file even flashing that does not fix my issue. I also posted on Reddit, so I will copy and paste this post.
Reddit Post.
I have a T-Mobile Note 4 was working fine for a long time flashed many ROM's multiple times over and over again never had a problem until I flashed DOK2 I assume. With ODIN. I did flash to stock from COD6 to DOK2 can't seem to downgrade back to COD6 with ODIN get error cant downgrade note 4 SW REV CHECK FAIL : [aboot]Fused2 > Binary 1 [1] eMMC write fail : ABOOT , that appears on Download mode. Then every time I install TWRP I try to install a ROM from OTG usb or ext sd and nothing flashes, rom files work used them before. I can only seem to install DOK2 and can't downgrade or flash other roms. I need help so I can flash other roms. Yes I tried flash stock DOK2 and boot stock recovery then clearing cache and factory reset, to downgrade to COD6 still failing and can't install other roms. every time i try to flash version lower then DOK2 using odin get this error ; SW REV CHECK FAIL : [aboot]Fused2 > Binary 1 [1] eMMC write fail : ABOOT
At one point I installed CWM trlltexx or something like that through TWRP, and did format and all of that. But after that went back to stock flashed TWRP 2.8.7.0 because couldn't flash roms with CWM because the roms thought I was on trltexx. Formatted all partitions with CWM. Anyways tried to get back to Cyanogenmod and or Tekxodus and other roms all fail. Minus Maximum Overdrives 4.0.1.
The first 3 lines that Overdrive mentioned that must make my roms flash able are.
HTML:
run_program("/sbin/busybox", "mount", "/system");
run_program("/sbin/busybox", "mount", "/cache");
run_program("/sbin/busybox", "mount", "/data");
Anyways please contact me on Google+ Hangouts or respond here if you know how to fix my issue also have Skype but PM me for that info. Add Bacon Seeds first and last name to Google + Hangouts that G+ Hangouts email is [email protected] . I am experienced in compiling roms extracting, de compiling as well. Life on my Note 4 without some Cyanogenmod had been technologically heartbreaking. I like flashing multiple roms and swapping back and forth. Now I cant even test others stuck on Max OD which is a good and awesome rom but sometimes get tired of Touch Wiz.
I would install the ROM you can, then dirty flash an aosp ROM, then try to flash the ROM you want.
therealjwkware said:
I would install the ROM you can, then dirty flash an aosp ROM, then try to flash the ROM you want.
Click to expand...
Click to collapse
I'll give this a shot but I seriously doubt this will work if other methods didn't.
sudoBacon said:
I'll give this a shot but I seriously doubt this will work if other methods didn't.
Click to expand...
Click to collapse
Use Kies to recover your phone. It should be able to fit any issues with partitions etc.
Odd how using the PIT file does not fix this issue. It's literally setting up your phone's partition table all over again and it isn't working. Also, on DOK2's bootloader, it is impossible to rollback bootloader. I tried going from DOK2 -> ANIH (Kitkat original) and it didn't work. You can still run older ROMs, just not the older bootloader. That's why you're getting the 'Binary 2 > Fused 1' message.
-
By the way, you should be using ODIN3.10.7. It is the latest version. Load up the full stock DOK2 firmware (I suggest downloading using SamFirm -- make sure to check Binary Nature for a full firmware), follow this guide:
http://forum.xda-developers.com/showthread.php?t=2610757
They used a PIT and Stock to fully wipe, with the exception in this case being that this is 5.1.1 and not 4.4.4
ShrekOpher said:
Use Kies to recover your phone. It should be able to fit any issues with partitions etc.
Click to expand...
Click to collapse
I tried that and now after doing factory reset in the stock firmware I can not even flash Maximum OD only DOK2 via odin.
sudoBacon said:
I tried that and now after doing factory reset in the stock firmware I can not even flash Maximum OD only DOK2 via odin.
Click to expand...
Click to collapse
do you have a working DOK2 stock firmware running on your phone. Once you upgrade to DOK2 you can only flash ROMs based on 5.1.1 or ROMs that include a kernel. If you want to flash a ROM based on 5.0.1 you will need to flash either the Emotion Kernel or the Beast mode kernel as well before you reboot the device.
If you have Stock TW firmware running and you have TWRP installed your phone should be fixed. As long as you use compatible ROMs with it.
ShrekOpher said:
do you have a working DOK2 stock firmware running on your phone. Once you upgrade to DOK2 you can only flash ROMs based on 5.1.1 or ROMs that include a kernel. If you want to flash a ROM based on 5.0.1 you will need to flash either the Emotion Kernel or the Beast mode kernel as well before you reboot the device.
If you have Stock TW firmware running and you have TWRP installed your phone should be fixed. As long as you use compatible ROMs with it.
Click to expand...
Click to collapse
Still didn't work.
Edit : Now i cant seem to install any rom nor Max OD. only DOK2 via odin. TWRP log says
E:Mount: Unable to find partition for path /sdcard
E:UnMount: Unable to find partition for path /sdcard
E:Mount: Unable to find partition for path /sdcard
sudoBacon said:
Still didn't work.
Edit : Now i cant seem to install any rom nor Max OD. only DOK2 via odin. TWRP log says
E:Mount: Unable to find partition for path /sdcard
E:UnMount: Unable to find partition for path /sdcard
E:Mount: Unable to find partition for path /sdcard
Click to expand...
Click to collapse
Looks like you corrupted your partitions. You might need to flash the pit file to fix it. I think there is a thread related to that somewhere.
Request thread closed, resolved!
Steps taken not in any order.
Find a legit us TRLTE pit file. Message me for the TRLTE pit file or I'll make a separate thread for it.
Flash DOK2 stock firmware + proper pit file and have re-partition checked, along with flash BL and EFS clear.
Format ext SD card.
Downloaded the roms onto the formatted SD card.
Flash the latest TWRP recovery
Wipe all not including system x3 times.
Go to Wipe and then Format, check system format system type Yes
Go to install select your ROM.
Then select your GApps and custom kernel whatever else you want.
You might have to do the stock flashing and wiping and formatting several times before this works along with the re-partitioning.
Note a legit TRLTETMO pit file can be found : http://www.sammobile.com/forum/showthread.php?t=29568
The legit pit file name for TRLTETMO should be labeled: TRLTE_USA_TMO.pit
sudoBacon said:
Request thread closed, resolved!
Steps taken not in any order.
Find a legit us TRLTE pit file. Message me for the TRLTE pit file or I'll make a separate thread for it.
Flash DOK2 stock firmware + proper pit file and have re-partition checked, along with flash BL and EFS clear.
Format ext SD card.
Downloaded the roms onto the formatted SD card.
Flash the latest TWRP recovery
Wipe all not including system x3 times.
Go to Wipe and then Format, check system format system type Yes
Go to install select your ROM.
Then select your GApps and custom kernel whatever else you want.
You might have to do the stock flashing and wiping and formatting several times before this works along with the re-partitioning.
Note a legit TRLTETMO pit file can be found : http://www.sammobile.com/forum/showthread.php?t=29568
The legit pit file name for TRLTETMO should be labeled: TRLTE_USA_TMO.pit
Click to expand...
Click to collapse
Congrats!
Hey bacon. I'm glad you figured it out. But in was wondering if you think me doing the pit file would work for my situation. Currently my phone is on a loop every time I flash dok2. And twrp will not flash any huge files. I can get kernels too flash but not roms. Any insight would be greatly appreciated. I can't even get the firmware too boot up. Thanks in advance
Jamonguyen said:
Hey bacon. I'm glad you figured it out. But in was wondering if you think me doing the pit file would work for my situation. Currently my phone is on a loop every time I flash dok2. And twrp will not flash any huge files. I can get kernels too flash but not roms. Any insight would be greatly appreciated. I can't even get the firmware too boot up. Thanks in advance
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=24369303960684492
Here's a pit for the N910T, grabbed from the latest DOK2.
eduardog131 said:
https://www.androidfilehost.com/?fid=24369303960684492
Here's a pit for the N910T, grabbed from the latest DOK2.
Click to expand...
Click to collapse
I'm trying to get stock to boot without success. I would really appreciate any help.
Longshark said:
I'm trying to get stock to boot without success. I would really appreciate any help.
Click to expand...
Click to collapse
Have you flashed the full ODIN package? Try erasing NAND and Re-Partition (with .pit in ODIN package)
I will usually just go about it that way when I go to stock to start off fresh.
eduardog131 said:
Have you flashed the full ODIN package? Try erasing NAND and Re-Partition (with .pit in ODIN package)
I will usually just go about it that way when I go to stock to start off fresh.
Click to expand...
Click to collapse
So I'm flashing the full ODIN package. PDA for stock, PIT from the link you posted, Checked boxes are Auto Reboot. Re-Partition, F. Reset Time and NAND Erase All. This is with ODIN 3.07.
What do I do when it finishes?
---------- Post added at 10:45 PM ---------- Previous post was at 10:43 PM ----------
eduardog131 said:
Have you flashed the full ODIN package? Try erasing NAND and Re-Partition (with .pit in ODIN package)
I will usually just go about it that way when I go to stock to start off fresh.
Click to expand...
Click to collapse
It's done but boot looping with RECOVERY BOOTING... screen. Do I flash TWRP now? I have 2.8.7. Is that sufficient?
Thanks
Longshark said:
So I'm flashing the full ODIN package. PDA for stock, PIT from the link you posted, Checked boxes are Auto Reboot. Re-Partition, F. Reset Time and NAND Erase All. This is with ODIN 3.07.
What do I do when it finishes?
---------- Post added at 10:45 PM ---------- Previous post was at 10:43 PM ----------
It's done but boot looping with RECOVERY BOOTING... screen. Do I flash TWRP now? I have 2.8.7. Is that sufficient?
Thanks
Click to expand...
Click to collapse
It shouldn't be bootlooping, in fact it has to reboot into recovery right after ODIN flashes the stock package, it needs to erase + verify / flash CSC contents. It should pretty much boot up into stock. If you really want to flash TWRP (to flash a custom ROM), flash it. Right after you flash it, make sure you take the battery out and you reboot into recovery manually. Stock system prevents recovery from being overwritten.
eduardog131 said:
It shouldn't be bootlooping, in fact it has to reboot into recovery right after ODIN flashes the stock package, it needs to erase + verify / flash CSC contents. It should pretty much boot up into stock. If you really want to flash TWRP (to flash a custom ROM), flash it. Right after you flash it, make sure you take the battery out and you reboot into recovery manually. Stock system prevents recovery from being overwritten.
Click to expand...
Click to collapse
Sorry I'm fairly new to this. So it did boot into custom recovery. I just want the phone back to stock without TWRP or any bells or whistles.
Its on the stock recovery interface. Should I wipe data/factory reset? Or reboot system now?
Longshark said:
Sorry I'm fairly new to this. So it did boot into custom recovery. I just want the phone back to stock without TWRP or any bells or whistles.
Its on the stock recovery interface. Should I wipe data/factory reset? Or reboot system now?
Click to expand...
Click to collapse
Once it's done with verification of CSC, just reboot system. It should take a few minutes to set itself up, then will throw you into the setup wizard. Once you're there you're good to go.
eduardog131 said:
It shouldn't be bootlooping, in fact it has to reboot into recovery right after ODIN flashes the stock package, it needs to erase + verify / flash CSC contents. It should pretty much boot up into stock. If you really want to flash TWRP (to flash a custom ROM), flash it. Right after you flash it, make sure you take the battery out and you reboot into recovery manually. Stock system prevents recovery from being overwritten.
Click to expand...
Click to collapse
Also does it matter the dm-verity verification failed is showing at the bottom?
Recently, I ran into the same problem and decided to check the interwebs for a solution which turns out to be pretty simple.
To solve the issue;
1. Download official firmware for your device from sammobile
2. Extract your firmware files from the TAR. (delete ext .md5 from file name, then open with 7zip/winrar. unzip)
3. Repack your firmware AFTER deleting cache.img. Instructions
4. Flash the repackaged firmware via ODIN
That's it!
Muthumbi said:
Recently, I ran into the same problem and decided to check the interwebs for a solution which turns out to be pretty simple.
To solve the issue;
1. Download official firmware for your device from sammobile
2. Extract your firmware files from the TAR. (delete ext .md5 from file name, then open with 7zip/winrar. unzip)
3. Repack your firmware AFTER deleting cache.img. Instructions
4. Flash the repackaged firmware via ODIN
That's it!
Click to expand...
Click to collapse
I tried this it failed frp lock
Muthumbi said:
Recently, I ran into the same problem and decided to check the interwebs for a solution which turns out to be pretty simple.
To solve the issue;
1. Download official firmware for your device from sammobile
2. Extract your firmware files from the TAR. (delete ext .md5 from file name, then open with 7zip/winrar. unzip)
3. Repack your firmware AFTER deleting cache.img. Instructions
4. Flash the repackaged firmware via ODIN
That's it!
Click to expand...
Click to collapse
Muthumbi: thank you so much, you are a genius. My n9208 was stuck at Samsung logo forever, no matter what I did, what stock firmware I flash through odin or through Kies, it just couldn't boot, I almost lost my hope. When entered recovery, only thing I noticed was the dm-verity failure, and I tried your way to solve the dm-verity problem only in the dim hope to change something........guess what, it booted, and booted very quickly!!!!, you saved my note 5!, massive thank you:good::good::good:
Now only one problem: rebooted into system, then entered stock recovery and did factory reset, dm-verity failure happened again. Any definitive solution other than re-flash stock firmware without cache.img? Much appreciated.
Normmo said:
Muthumbi: thank you so much, you are a genius. My n9208 was stuck at Samsung logo forever, no matter what I did, what stock firmware I flash through odin or through Kies, it just couldn't boot, I almost lost my hope. When entered recovery, only thing I noticed was the dm-verity failure, and I tried your way to solve the dm-verity problem only in the dim hope to change something........guess what, it booted, and booted very quickly!!!!, you saved my note 5!, massive thank you:good::good::good:
Click to expand...
Click to collapse
Download this file and flash it via odin after fleshing any stock ROM. Tell me how it goes
HoodPhonez said:
I tried this it failed frp lock
Click to expand...
Click to collapse
Does your phone boot up?
Muthumbi said:
Does your phone boot up?
Click to expand...
Click to collapse
No just stay on samsung logo.
HoodPhonez said:
No just stay on samsung logo.
Click to expand...
Click to collapse
yes it did boot up, but the recovery still shows Dm-verity failure after factory reset. thanks Muthumbi.
HoodPhonez said:
No just stay on samsung logo.
Click to expand...
Click to collapse
You might have to look for a way to undo FAP lock
Normmo said:
yes it did boot up, but the recovery still shows Dm-verity failure after factory reset. thanks Muthumbi.
Click to expand...
Click to collapse
Kindly send me a private message with exact details. I will get back to you in a while
HoodPhonez said:
No just stay on samsung logo.
Click to expand...
Click to collapse
You'll need to undo FRP lock first
How? I searched can't find a way
Muthumbi said:
Recently, I ran into the same problem and decided to check the interwebs for a solution which turns out to be pretty simple.
To solve the issue;
1. Download official firmware for your device from sammobile
2. Extract your firmware files from the TAR. (delete ext .md5 from file name, then open with 7zip/winrar. unzip)
3. Repack your firmware AFTER deleting cache.img. Instructions
4. Flash the repackaged firmware via ODIN
That's it!
Click to expand...
Click to collapse
Please do video I cant do it :good: , I'm a few days without Cell Phones
yyyyyyyyyyyyyyyyyes man it work thnks:laugh:
my problem solved with this file:
Code:
https://www.androidfilehost.com/?fid=24052804347784115
G920f
G928C...boots to wifi turning on, gets stuck there for a bit then reboots. If i do factory reset, it gets stuck at the boot logo permanently. if i get into recovery again, i get the dm-verity error. any ideas. cant root coz the FRP lock is on.
I had this problem and solved it by flashing Galaxy S6 marshmallow Kernel (check if it's compatible with your device e.g. I have a G920F). Then do a erase data/clear cache/reboot.
Your DRK is damaged. If you will extract the boot.img and system.img from the stock firmware then convert them each to .tar.md5 and flash the system.img then the boot.img it will boot like normal. If you ever update or reset the device it will stick back on the Samsung splash screen until you flash them again. I can repair your DRK as a permanent fix, but it can only be repaired via UART cable which means it cannot be redirected and repaired remotely. You are more than welcome to ship your phone to my business and I will repair the DRK and return it to you, but you must pay return shipping.
"furious99, you were right, though i hadn't seen your message, i noticed the marshmallow update for iraq for the G928C had been released, downloaded it and flashed the phone. It has been working since. I did a factory reset and it was still fine. so that is the solution.
Muthumbi said:
Recently, I ran into the same problem and decided to check the interwebs for a solution which turns out to be pretty simple.
To solve the issue;
1. Download official firmware for your device from sammobile
2. Extract your firmware files from the TAR. (delete ext .md5 from file name, then open with 7zip/winrar. unzip)
3. Repack your firmware AFTER deleting cache.img. Instructions
4. Flash the repackaged firmware via ODIN
That's it!
Click to expand...
Click to collapse
This is only a temporary solution. If you update the firmware or factory reset the phone it will go back to being stuck on the Samsung logo. It can only be permanently fixed via a hardware solution atm.
Was in the process of IMEI repair. (Just for reference.)
My phone use to be rooted and on a custom rom. It was previously reverted back to stock DOK2 5.1.1. My phone cannot be flashed anymore for some reason. I cant even flash the DOK2 file that goes in AP. I tried flashing the trlte pit file and now my phone doesn't boot past the T-Mobile logo. I think im missing some files to do a full ODIN flash.
U need to flash trltetmo pit file. Trlte is for N910F I believe and I think it's 16gb internal sd. U need to flash 100% stock dok2 with the pit file and make sure repartition is checked. If it fails....try renaming the .tar.md5 to just .tar (remove md5) for some reason I can't flash stock any other way
Karina Kapri said:
Was in the process of IMEI repair. (Just for reference.)
My phone use to be rooted and on a custom rom. It was previously reverted back to stock DOK2 5.1.1. My phone cannot be flashed anymore for some reason. I cant even flash the DOK2 file that goes in AP. I tried flashing the trlte pit file and now my phone doesn't boot past the T-Mobile logo. I think im missing some files to do a full ODIN flash.
Click to expand...
Click to collapse
I don't have a specific answer to your problem, but make sure you try and wipe the cache as well. I remember having a situation where I was trying to flash my device back to stock and it was bootlooping. The problem ended up being that I hadn't properly wiped everything from the custom ROM I had been on.
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.