Database Develop

[Q] Unable to flash Lollipop. Can't install this package on top of incompatible data.

Here's the backstory. Skip to the next paragraph if you don't want to bother reading it. (Phone is GT-I8190N)
Originally, all was well with custom cyanogenmod kitkat from novafusion. I got a USB dac which didn't work with the kitkat I had. Phone freezes upon plugging in. So I decided to go to lollipop.
So I flashed cm12.1_golden.nova.20150627 into the phone with 2.8.0.0 teamwin recovery. (Couldn't update to 2.8.3.0 for some reason. Used Odin. Said PASS! But version stays the same in phone.)
Everything went well, I got lollipop running. I decided to do a reset in android through the settings menu.
Phone restarted and this happened (teamwin splash screen flashes): /watch?v=Wr-dlk7q06A (Newcomer can't post link... This isn't spam but if I really can't put links I'll remove it)
I admit I panicked and did some things I'm pretty sure screwed myself even further so here goes:
Went back to Odin and tried to flash a stock rom onto it. (I8190XXAMJ2_I8190ORGAMJ1_HOME) Unfortunately. I was dumb and didn't realize my phone was GT-I8190N and not GT-I8190. So I got the wrong stock rom.
Odin FAIL! with error stuck on "complete(write) operation failed."
The second time I tried it the error was "There is no PIT partition."
So I did Re-Partition with goldenxx + the stock rom. It errored at "nand write start modem.bin fail complete(write) operation failed"
I did finally realize I got the wrong stock rom. That flashed properly and stock rom is working. Not sure if the PIT thing blew something up. Anyhow, onto the next paragraph where the current situation lies.
So now it's in stock ROM.
I got Odin to flash CWM 6.0.2.7 then I tried to use that to flash the same lollipop I used before. It got the error status 7. Can't install this package on top of incompatible data. No file context detected.
I tried the delete assert line trick. Now CWM gives no error. I don't remember what it exactly said. I think it said Updating. Then installation failed. No specific error.
So I flashed TWRP 2.8.0.0 and tried to flash lollipop again. Again error. Can't install this package on top of incompatible data. Error executing updater in zip.
And that's about it. I have absolutely no clue how to continue this. All help is appreciated! Thank you for your time!

Have you tried flashing a different rom, lp or kk? Also rooting & doing full wipes, maybe jump from stock to lp is too big, I'm not too sure
Sent from my GT-I8190 using XDA Free mobile app

Softbricked AT&T Galaxy S5

I purchased a soft bricked sm-g900a phone off of Ebay with the idea of using Odin to reflash and recover the phone. Since the phone was purchased soft bricked I do not have a history on what firmware was running on the phone or what the previous owner flashed that may have caused the phone not to boot to the OS or into recovery. I am assuming the previous owner was on 5.0 and tried to downgrade and ran into problems.
Short description of the current state of the phone:
1. Phone will boot into Odin Mode and can be flashed using Odin.
2. Phone will start to boot to recovery but sticks at "Recovery Booting. . . ." and reboots after about 30 seconds
3. Phone boots to Samsung logo and reboots after about 30 seconds.
What works:
Using Odin I can flash the following without errors: After flashing the phone exhibits the behavior above.
G900A_OC4_Stock_Kernel.tar.md5,
G900A_OA1_Stock_Kernel.tar.md5
G900A_OC4_Stock_Modem.tar.md5,
G900A_OC4_Stock_Partitions.tar.md5
G900AUCU3BOC4_OneClick..exe - reboots to recovery and "Recovery Booting. . . ."
I can flash SM-G900A_pit.pit with Odin 3.07 but not 3.09 or 3.10.
What does not work.
Tried flashing G900A_Downgrade_to_NCE.tar.md5 - Odin reports error
<ID:0/005> system.img.ext4
<ID:0/005> FAIL! (Auth)
Phone reports errors
SYS REV CHECK FAIL :Refer 2> Binary 1
SECURE CHECK FAIL : System
Tried flashing SM-G900A 4.4.2 G900AUCU1ANCE Firmware - AP_G900AUCU1ANCE_964333_REV00_user_low_ship_MULTI_CERT.tar.md5 in AP slot
Same errors as above .
Tried to use Kies to recover the phone. It goes through the process of recovering with 4.4.2 and crashes about the same place flashing wit Odin does.
I assume if I could get into recovery to do a factory wipe I would be able to get the phone to boot. I have read multiple forum posts and blogs on getting the bricked phone to work where most recommend flashing G900A_Downgrade_to_NCE.tar.md5 and then if you can't get into recovery to flash either G900A_OC4_Stock_Kernel.tar.md5 or G900A_OA1_Stock_Kernel.tar.md5 and then you should be able to get into recovery. This of course has not worked for me.
Does anyone have any idea how I might go about getting this phone to boot into recovery? Also is it possible to have the local AT&T store re flash 5.0 on the phone.
I know it is a risk buying soft bricked phones but I sure would not like to have an expensive paper weight.

Bogiemaker said:
I purchased a soft bricked sm-g900a phone off of Ebay with the idea of using Odin to reflash and recover the phone. Since the phone was purchased soft bricked I do not have a history on what firmware was running on the phone or what the previous owner flashed that may have caused the phone not to boot to the OS or into recovery. I am assuming the previous owner was on 5.0 and tried to downgrade and ran into problems.
Short description of the current state of the phone:
1. Phone will boot into Odin Mode and can be flashed using Odin.
2. Phone will start to boot to recovery but sticks at "Recovery Booting. . . ." and reboots after about 30 seconds
3. Phone boots to Samsung logo and reboots after about 30 seconds.
What works:
Using Odin I can flash the following without errors: After flashing the phone exhibits the behavior above.
G900A_OC4_Stock_Kernel.tar.md5,
G900A_OA1_Stock_Kernel.tar.md5
G900A_OC4_Stock_Modem.tar.md5,
G900A_OC4_Stock_Partitions.tar.md5
G900AUCU3BOC4_OneClick..exe - reboots to recovery and "Recovery Booting. . . ."
I can flash SM-G900A_pit.pit with Odin 3.07 but not 3.09 or 3.10.
What does not work.
Tried flashing G900A_Downgrade_to_NCE.tar.md5 - Odin reports error
<ID:0/005> system.img.ext4
<ID:0/005> FAIL! (Auth)
Phone reports errors
SYS REV CHECK FAIL :Refer 2> Binary 1
SECURE CHECK FAIL : System
Tried flashing SM-G900A 4.4.2 G900AUCU1ANCE Firmware - AP_G900AUCU1ANCE_964333_REV00_user_low_ship_MULTI_CERT.tar.md5 in AP slot
Same errors as above .
Tried to use Kies to recover the phone. It goes through the process of recovering with 4.4.2 and crashes about the same place flashing wit Odin does.
I assume if I could get into recovery to do a factory wipe I would be able to get the phone to boot. I have read multiple forum posts and blogs on getting the bricked phone to work where most recommend flashing G900A_Downgrade_to_NCE.tar.md5 and then if you can't get into recovery to flash either G900A_OC4_Stock_Kernel.tar.md5 or G900A_OA1_Stock_Kernel.tar.md5 and then you should be able to get into recovery. This of course has not worked for me.
Does anyone have any idea how I might go about getting this phone to boot into recovery? Also is it possible to have the local AT&T store re flash 5.0 on the phone.
I know it is a risk buying soft bricked phones but I sure would not like to have an expensive paper weight.
Click to expand...
Click to collapse
Its hard to tell what version it was on previously since recovery wont even boot, but from how its acting i'd say it was on LP and bricked for a KK flash, so you flashing NCE(Kitkat) is doing zilch. Seeing as there is no option for you to root, and im assuming you arent interested in that anyway, i would just take it to bestbuy or the att store and get them to reflash it, just say you got it off ebay and it was like that.
Sent from my Tw5ted SM-G900A using Tapatalk

I took the phone to BestBuy and the guy there flashed it with 5.0.1 with the same results. Boots to the Recovery Booting. . . . screen for about 30 seconds and then reboots. My daughter is taking it to an AT&T repair center to see if they have any better luck.

Have you tried flashing the boot image?
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app

Boot image. Not sure which file you are talking about.
Could you give me a little more information or a link to the file?

Re: Softbricked AT&T Galaxy S5
If you have the oc4 update zip, in the zip should be a boot image, create an md5 tar file from it then flash in AP. If that doesn't work, you flashed a bad kernel and may have to use jtag to fully recover. Or bring it to a repair facility to have them do it.

My daughter took the phone to an AT&T repair center and they also could not successfully flash the phone. The only OC4 update i have found is the G900AUCU3BOC4_OneClick..exe update and I do not believe I can extract the boot image from that update. Is there another source of the OC4 update available where I could obtain the boot image.
Thanks for the help everyone.

I'll look for the DL link. But if they tried flashing it, and it didn't work. You may be SOL.

Bogiemaker said:
I purchased a soft bricked sm-g900a phone off of Ebay with the idea of using Odin to reflash and recover the phone. Since the phone was purchased soft bricked I do not have a history on what firmware was running on the phone or what the previous owner flashed that may have caused the phone not to boot to the OS or into recovery. I am assuming the previous owner was on 5.0 and tried to downgrade and ran into problems.
Short description of the current state of the phone:
1. Phone will boot into Odin Mode and can be flashed using Odin.
2. Phone will start to boot to recovery but sticks at "Recovery Booting. . . ." and reboots after about 30 seconds
3. Phone boots to Samsung logo and reboots after about 30 seconds.
What works:
Using Odin I can flash the following without errors: After flashing the phone exhibits the behavior above.
G900A_OC4_Stock_Kernel.tar.md5,
G900A_OA1_Stock_Kernel.tar.md5
G900A_OC4_Stock_Modem.tar.md5,
G900A_OC4_Stock_Partitions.tar.md5
G900AUCU3BOC4_OneClick..exe - reboots to recovery and "Recovery Booting. . . ."
I can flash SM-G900A_pit.pit with Odin 3.07 but not 3.09 or 3.10.
What does not work.
Tried flashing G900A_Downgrade_to_NCE.tar.md5 - Odin reports error
<ID:0/005> system.img.ext4
<ID:0/005> FAIL! (Auth)
Phone reports errors
SYS REV CHECK FAIL :Refer 2> Binary 1
SECURE CHECK FAIL : System
Tried flashing SM-G900A 4.4.2 G900AUCU1ANCE Firmware - AP_G900AUCU1ANCE_964333_REV00_user_low_ship_MULTI_CERT.tar.md5 in AP slot
Same errors as above .
Tried to use Kies to recover the phone. It goes through the process of recovering with 4.4.2 and crashes about the same place flashing wit Odin does.
I assume if I could get into recovery to do a factory wipe I would be able to get the phone to boot. I have read multiple forum posts and blogs on getting the bricked phone to work where most recommend flashing G900A_Downgrade_to_NCE.tar.md5 and then if you can't get into recovery to flash either G900A_OC4_Stock_Kernel.tar.md5 or G900A_OA1_Stock_Kernel.tar.md5 and then you should be able to get into recovery. This of course has not worked for me.
Does anyone have any idea how I might go about getting this phone to boot into recovery? Also is it possible to have the local AT&T store re flash 5.0 on the phone.
I know it is a risk buying soft bricked phones but I sure would not like to have an expensive paper weight.
Click to expand...
Click to collapse
Hello! OP...are you still around?
Did you ever recover this phone?
I was in the same situation...maybe worse...and I was finally able to recover it.
Please let me know what happened with yours?
THANKS!

jebep said:
Hello! OP...are you still around?
Did you ever recover this phone?
I was in the same situation...maybe worse...and I was finally able to recover it.
Please let me know what happened with yours?
THANKS!
Click to expand...
Click to collapse
How did you recover yours?

[REQ-DEV HELP] Experienced user and flasher stuck on DOK2 mounting partitions problem

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?

"No OS installed" T-Mobile Note 4

Hey everyone,
I hope I posted this in the proper area. I've run into a problem with my Note 4. I wiped it and now if I try to reboot from TWRP, it says theres no OS installed. If I do reboot, it gets stuck on the samsung Note 4 screen.
I need to get this up and running asap. Could someone please help?
I have TWRP 2.8.7.0 installed and I have Odin 3.09 on my desktop. I would really appreciate detailed instructions and download links to anything else I may need so that I can get my Note 4 up and running again.
Thank you.

krieger119 said:
Hey everyone,
I hope I posted this in the proper area. I've run into a problem with my Note 4. I wiped it and now if I try to reboot from TWRP, it says theres no OS installed. If I do reboot, it gets stuck on the samsung Note 4 screen.
I need to get this up and running asap. Could someone please help?
I have TWRP 2.8.7.0 installed and I have Odin 3.09 on my desktop. I would really appreciate detailed instructions and download links to anything else I may need so that I can get my Note 4 up and running again.
Thank you.
Click to expand...
Click to collapse
Very simple dude just download any rom for n910t and flash it from twrp or download stock firmware from sammobiles and flash in odin.

Trex888 said:
Very simple dude just download any rom for n910t and flash it from twrp or download stock firmware from sammobiles and flash in odin.
Click to expand...
Click to collapse
That's my problem. I haven't been able to find any rom for Note 4. Last I remember, there wasn't anything on sammobiles for Note 4. Would love a stock firmware right now so I can flash it.

UPDATE: I found a stock firmware from this thread https://forum.xda-developers.com/no...uide-odin-to-stock-unrooted-firmware-t2957156
just tried to flash it and I got a fail. I followed the instructions exactly but it failed.
Any idea why? Or what I should do?
Odin v.3 engine (ID:3)..
File analysis...
SetupConnection...
Initialization...
Get PIT for mapping...
Firmware update start...
SingleDownload.
Aboot.mbn
NAND Write Start!!
sbl1.mbn
rpm.mbn
FAIL! (Auth)
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)

Maybe I can transfer a backup to my memory card and restore off of that? I would just need a backup... Anyone?

krieger119 said:
Maybe I can transfer a backup to my memory card and restore off of that? I would just need a backup... Anyone?
Click to expand...
Click to collapse
did you try: https://forum.xda-developers.com/no...om-n910t3uvu3epj2-stock-rooted-odex-t3501592?
Also, I would update to latest TWRP (3.0.2, i think)

I would just Odin back to stock firmware if you dont have a backup. you probably wiped the wrong partition or something, I've seen this message before too and that's how I got my phone working again
T-Mobile Note 4
N910T trltetmo
Resurrection Remix 5.8.2
Android 7.1.1

Dolemaine said:
did you try: https://forum.xda-developers.com/no...om-n910t3uvu3epj2-stock-rooted-odex-t3501592?
Also, I would update to latest TWRP (3.0.2, i think)
Click to expand...
Click to collapse
Nothing unfortunately. Just to be sure I did it right ... I downloaded the kernel zip file in that thread. Transferred it to my sd card, loaded it back onto my phone, went into twrp, hit install, found the zip file and installed it. a few seconds later, it was done. I rebooted. It went to the logo screen again and then it back to TWRP. IDK what to do anymore
highonthc said:
I would just Odin back to stock firmware if you dont have a backup. you probably wiped the wrong partition or something, I've seen this message before too and that's how I got my phone working again
Click to expand...
Click to collapse
That's what I'm trying to do, but Odin keeps failing.

i have these saved on my android file host account. see if it helps.
COD6
https://www.androidfilehost.com/?fid=23991606952595589
md5: 305ce514b95b9213c09b1a430d894e31
ANK4
https://www.androidfilehost.com/?fid=95897840722645896
md5: 8aa74f2a7183d8e0ef1cc4559d99c377

moabizzi said:
i have these saved on my android file host account. see if it helps.
COD6
https://www.androidfilehost.com/?fid=23991606952595589
md5: 305ce514b95b9213c09b1a430d894e31
ANK4
https://www.androidfilehost.com/?fid=95897840722645896
md5: 8aa74f2a7183d8e0ef1cc4559d99c377
Click to expand...
Click to collapse
So, the COD6 seems to be damaged or something. I couldn't use it. And the ANK4 I already had and still getting a fail.
It's been a long time since this occurred. IDK if this helps but when the phone was still up and running. For some unknown reason, I went to my app drawer and uninstalled/deleted Superuser. Could that be a reason why I'm having an issue flashing my Note 4 back to stock?

Could someone possible send me a backup file from a Note 4 so that I could restore my phone and then factory reset? Maybe that'll get my phone up and running.

YES!!! I fixed it!!! Why didn't anyone tell me that I couldn't flash a stock (kitkat) rom if I had previously updated to Lollipop or Marshmallow? Fortunately, while searching "write fail: aboot" a thread came up and someone mentioned it so I downloaded a marshmallow rom and that was it. I'm up and running now.

Trying to flash stock firmware, bootloop, /system/bin/tune2fs is missing

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