Related
Hi guys,
I have bricked my tablet, when i try to "Nand Erase All" it keeps failing, can someone explain the problem
Odin Log:
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1005)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Erase...
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
---------------------------------------------------------------------
Status:
-Device: Galaxy Note 10.1 N8000, not rooted, Debugging mode disabled so no ADB:crying:
-Bootloop, No recovery mode, Can access Download mode:good:
----------------------------------------------------------------------
What I have tried so Far
- Removed the battery ( didn't work)
- Flashed bootloader --> (Flashed Successfully but didn't work)
- Flashed CWM recovery -->(Flashed Successfully, battery off then on, but didn't work, still cant access recovery mode)
- Flashed Stock firmware -->(Flashed Successfully but didn't work)
-Flashed (Stock/custom recovery) with Pit file re-partition checked --> (Repartitioned and Flashed Successfully but didn't work)
-I read about that I need to check "Nand Erase ALL" ( with Pit file on) to erase cache and every corrupted file
so I tried but I kept failing giving the error mentioned above, So any explanation why "Nand Erase All" fails, and any other suggestions for my current situation
Thanks in advance
scorpiohyena said:
Hi guys,
I have bricked my tablet, when i try to "Nand Erase All" it keeps failing, can someone explain the problem
Odin Log:
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1005)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Erase...
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
---------------------------------------------------------------------
Status:
-Device: Galaxy Note 10.1 N8000, not rooted, Debugging mode disabled so no ADB:crying:
-Bootloop, No recovery mode, Can access Download mode:good:
----------------------------------------------------------------------
What I have tried so Far
- Removed the battery ( didn't work)
- Flashed bootloader --> (Flashed Successfully but didn't work)
- Flashed CWM recovery -->(Flashed Successfully, battery off then on, but didn't work, still cant access recovery mode)
- Flashed Stock firmware -->(Flashed Successfully but didn't work)
-Flashed (Stock/custom recovery) with Pit file re-partition checked --> (Repartitioned and Flashed Successfully but didn't work)
-I read about that I need to check "Nand Erase ALL" ( with Pit file on) to erase cache and every corrupted file
so I tried but I kept failing giving the error mentioned above, So any explanation why "Nand Erase All" fails, and any other suggestions for my current situation
Thanks in advance
Click to expand...
Click to collapse
Update:
currently I am using heimdall, Trying to create a Custom Pit to skip bad sectors in recovery and boot partitions, any experience in that would be helpfull.
I am trying to figure out the pit files parameter to create a custom working file
scorpiohyena said:
Update:
currently I am using heimdall, Trying to create a Custom Pit to skip bad sectors in recovery and boot partitions, any experience in that would be helpfull.
I am trying to figure out the pit files parameter to create a custom working file
Click to expand...
Click to collapse
Hi there did you had any success trying to unbrick your tablet ??, I'm experiencing the same issues as you.
I've a rooted Note 10.1 N8013 running on stock firmware.
I've tried everything, all left for me is trying "Nand erase all" . but it fails everytime
Thank you !!
hi gays
can you tell me if the problem of nand eras all fail was solved ?
I was on DRL6 and Pie, and tried to do the CRK1 to DRL6 through Odin 3.13 Patched version, went into Odin mode on the phone. Added BL + AP + CP + HOME_CSC like the tutorial stated, Odin said (success 0 / failed 2), so I assumed I didn't have Samsung drivers installed, closed out of Odin and installed the drivers, rebooted Odin it seemed like it was going to work because it went further than the other tries but then it failed at "Complete(Write) operation failed."
I tried different cords, USB ports, turned off Firewall.
So, I figured I'd leave it alone, restarted my phone and it noticed it wouldn't reboot. I unplugged it, and held down the power button which booted up:
[UPLOAD MODE]
Unkown Error
----------------------
DDR Vendor: Samsung
SOC_HW_REVISION: 2.1
skip print_summary_to_lcd..
Generating summary...
>> General Info
>> DDR Info
>> RPM
>> TrustZone
>> Hypervisor
Done!
[To PC] Connect a USB cable or
[To SD] Press VOL_UP + VOL_DOWN
Click to expand...
Click to collapse
Tried Odin while in the mode and now this is what I'm getting:
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> skip file list for home binary
<ID:0/003> apdp.mbn
<ID:0/003> msadp.mbn
<ID:0/003> persist.img.ext4
<ID:0/003> dqmdbg.img.ext4
<ID:0/003> Home Binary Download
<ID:0/003> Total Binary size: 4907 M
<ID:0/003> SetupConnection..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Edit: Got it into Download Mode, this is what I'm getting now.
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 4920 M
<ID:0/004> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Edit 2: Did some Googling, and seen that my cache could've been corrupted. So, I went back into Download mode, flashed just CSC in Odin, and my phone worked again. So, being stubborn, I flashed BL + AP + CP without CSC and my phone is now Optimizing App, then reboots and continues the cycle. I'm now back in Upload Mode and stuck, phone won't turn off or anything.
[UPLOAD MODE]
Unkown Error
DDR Vendor: Samsung
SOC_HW_REVISION: 2.1
RAM dump by hard reset
lastSns: 0x5a
Generating summary...
General Info
DDR Info
DCVS Info
Recovered from an exception
Done.
[To PC] Connect a USB cable or
[To SD] Press VOL_UP + VOL_DOWN
Synchronous Exceoption
lr: 0x0000000085e37228
sp: 0x000000001407bba0
pc: 0x0000000085e37288
Click to expand...
Click to collapse
Edit 3: Back to Optimizing and rebooting again. It goes to completion but then reboots back to the Samsung logo.
What phone do you have? I had a similar problem that is almost exactly as you described. I have an N950U1 but I flashed the T-Mobile firmware to mine a few months ago. I believe that was my problem but I could be wrong. I posted in another thread about this. https://forum.xda-developers.com/at...in-flash-to-note-8-specific-computer-t3883398 . I think I could have flashed the unlocked firmware, but I haven't tried to see if that is the solution.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
* [B][U]Your warranty is now void.[/U][/B]
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
Odin
- Odin3 v3.13.3
Heimdall
- Glass Echidna
TWRP for Samsung Galaxy Note 4 (Qualcomm)
How to flash a bootloader and/or modem1. If your tablet is turned on normally, turn on Advanced reboot in Developer options and select "Download" from the Restart menu,
2. In Odin, import either the bootloader.tar or bootloader_modem.tar file, depending on your variant, with the "AP" button.
How to flash TWRP with Odin1. If your tablet is turned on normally, turn on Advanced reboot in Developer options and select "Download" from the Restart menu. Alternatively, power it off and press the Power, Volume Down, and Home buttons simultaneously. When the blue screen appears, release all 3 buttons and press Volume Up.
2. In Odin, import the appropriate twrp.tar file for your variant with the "AP" and press the "Start" button.
3. Pull the battery as soon as your phone vibrates.
4. You can then boot directly into TWRP by pressing the Power, Volume Up, and Home buttons simultaneously. Release all three buttons as soon as you see the boot screen ("Samsung Galaxy Note 4").
How to flash TWRP within a previous version of TWRP1. If your tablet is turned on normally, turn on Advanced reboot in Developer options and select "Recovery" from the Restart menu. Alternatively, power it off and press the Power, Volume Up, and Home buttons simultaneously. Release all 3 buttons when the boot screen appears ("Samsung Galaxy Note 4").
2. In TWRP, tap "Install" then "Install Image".
3. Navigate in the folder structure to the location of the appropriate twrp.img file for your variant and tap it.
4. Select the "Recovery" radio button.
5. Move the slider to the right to flash the TWRP image.
6. Tap "Reboot System" or, alternatively, tap the back arrow 3 times to return to the main menu, then tap "Reboot" and "Recovery" to reboot into the TWRP image you have just flashed.
Changelog
- See post #2.
Bugs
E:recv error on uevent
- This warning appears during the process of making a nandroid backup. I assure you that it's perfectly innocence: your backup should complete successfully and it should restore successfully without any reference to this warning. This is a known bug that affects other Exynos devices as well, such as the Samsung Galaxy S7 Edge (hero2lte).
- Technical explanation from bigbiff himself: "I think it must be a bug, probably shouldn't print the log out if we aren't using ueventd to pull in partition information on a target device. I am not sure what devices we are supporting using ueventd however. Looks like it only runs from the process_fstab function. It's harmless, but I wonder if it should be put in an ifdef guard."
Credits
- Inspiration in motivating me to learn how to build TWRP: _mone
- Kernel work and device trees for related devices: cvxda
- micky387 and every other open source developer and user who contributes directly or indirectly to the TWRP community in the development of and in providing feedback for the tblte, trlte, and trlteduos.
Sources
- apq8084 kernel repository
- tblte repository
- trlte repository
- trlteduos repository
- TWRP repository
XDA:DevDB Information
TWRP 3.5.2_9-0, ROM for the Samsung Galaxy Note 4
Contributors
ripee, _mone, cvxda, micky387
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Version Information
Status: Stable
Current Stable Version: 3.5.2_9-0
Stable Release Date: 2021-04-06
Created 2019-05-24
Last Updated 2022-12-09
Reserved
Reserved
Hello,
First of all, thank you for you continuous work and courage to keep our devices up to date, by you I mean the whole awesome team !
Updated of TWRP 3.3.1-0 was successfully done within TWRP 3.3.0-0 - flash image - recovery.
Update of Bootloader_Modem file was a bit longer :
- with the provided Odin3 v3.13.1 - the ID:COM was going crazy connecting/disconnected no matter what USB port (2.0 and 3.0) I was using and I was using OEM cable.
<ID:0/005> Added!!
<ID:0/005> Removed!!
<ID:0/005> Added!!
<ID:0/005> Removed!!
...
Updating Samsung Mobile Phone Driver didn't help (but just in case, link = https://forum.xda-developers.com/showpost.php?p=78823944&postcount=623 )
Even after a restart of Windows 10 OS.
Luckily I had kept a zip of Odin3_v3.10.7 close by me (this was the version I used for my previous BL/CP update) and using this version was fine, my n910f is correctly on DRI2_DQL1.
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1100)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> modem.bin
<ID:0/005> NON-HLOS.bin
<ID:0/005> rpm.mbn
<ID:0/005> sbl1.mbn
<ID:0/005> sdi.mbn
<ID:0/005> tz.mbn
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
I'll report if anything good or bad is noticed within the next few days.
Thank you again,
Updated to 3.3.1-0 and for some reason it refuses to remember the correct date and time. Every time I boot in it defaults to something like 1971-01-20 with a completely wrong time for my time zone. Some other basic setting like reversed navbar would not stick every time.
Reverted to 3.2.3-0 and everything's back to normal. Any ideas? I though maybe my phone was somehow causing it but once I reverted the problem disappeared.
Apex Predator said:
Updated to 3.3.1-0 and for some reason it refuses to remember the correct date and time. Every time I boot in it defaults to something like 1971-01-20 with a completely wrong time for my time zone. Some other basic setting like reversed navbar would not stick every time.
Reverted to 3.2.3-0 and everything's back to normal. Any ideas? I though maybe my phone was somehow causing it but once I reverted the problem disappeared.
Click to expand...
Click to collapse
@ripee
Has the issue been resolved yet ?
It only happens to me when I do a full complete wipe for a clean flash.
It doesn't seem to affect a roms integrity when restoring a backup.
Once a rom has been run for a length of time the TWRP clock updates ok.
All these backups are less than 3 days old.
All are the latest builds of each respective rom.
The oldest backup is Xenon
mangojack01 said:
@ripee
Has the issue been resolved yet ?
It only happens to me when I do a full complete wipe for a clean flash.
It doesn't seem to affect a roms integrity when restoring a backup.
Once a rom has been run for a length of time the TWRP clock updates ok.
All these backups are less than 3 days old.
All are the latest builds of each respective rom.
The oldest backup is Xenon
Click to expand...
Click to collapse
The easiest way to resolve this is to wipe your phone, flash stock, then start again with twrp and your rom. TWRP gets its time and date from the system clock, which is set by the rom, which is set by your mobile company.
I had the same thing happen on my wifi-only tablet, and reflashing stock is the only thing that worked. No idea why this happened in the first place, perhaps some twrp or rom update went screwy, and some file or folder permission isn't allowing it to be set properly.
I'm still using 3.2.3 so this might be irrelevant info, or just wrong info, but it looks like that .twrps file on the internal sdcard is where the settings are stored. I had never updated my time in twrp so it had been on mountain time (-7) and the file at /storage/emulated/0/TWRP/.twrps reflected that but I just changed to it to my correct time, eastern standard (-5) (it's still daylight savings so its EDT instead EST for the moment). Now that hidden file has been updated with EST and EDT references.
I guess if you're formatting the internal sdcard there's no way to protect it, but perhaps users could copy it and then replace it after a full wipe assuming TWRP is not being updated. If updating TWRP it might just be safer to redo the settings or, like I apparently have, just not pay it any attention.
Since there's a variety of file explorer apps out there I thought I would add that some file managers may use the symlink path of /sdcard/TWRP/.twrps or mnt/sdcard/TWRP/.twrps but for those that are curious the actual path is /storage/emulated/0/TWRP/.twrps
kevintm78 said:
I'm still using 3.2.3 so this might be irrelevant info, or just wrong info, but it looks like that .twrps file on the internal sdcard is where the settings are stored. I had never updated my time in twrp so it had been on mountain time (-7) and the file at /storage/emulated/0/TWRP/.twrps reflected that but I just changed to it to my correct time, eastern standard (-5) (it's still daylight savings so its EDT instead EST for the moment). Now that hidden file has been updated with EST and EDT references.
I guess if you're formatting the internal sdcard there's no way to protect it, but perhaps users could copy it and then replace it after a full wipe assuming TWRP is not being updated. If updating TWRP it might just be safer to redo the settings or, like I apparently have, just not pay it any attention.
Since there's a variety of file explorer apps out there I thought I would add that some file managers may use the symlink path of /sdcard/TWRP/.twrps or mnt/sdcard/TWRP/.twrps but for those that are curious the actual path is /storage/emulated/0/TWRP/.twrps
Click to expand...
Click to collapse
I agree, it's more of an annoyance than anything else, especially to a grumpy, slightly aspie, 69yo pedant.
I run trwp v 3.3.1
I've tried cut n paste .twrp after formating internal sd many times in many ways via twrp file manager.
eg, wipe everything internal, reboot recovery, setup recovery, replace/ overwrite or edit new .twrp file, reboot recovery, but without success.
cest la vie
Thanks for your feedback, I'm sure others also may find it enlightening.
Hi, Ripee
I got two 910V I bought it off one has bad efs partition and one has bad speaker/mic I was thinking to copy bad speaker/mic efs partition to another one, but copying over efs partition didn't do anything. I thought it will copy over IMEI stuff to this second phone?
zfk110 said:
Hi, Ripee
I got two 910V I bought it off one has bad efs partition and one has bad speaker/mic I was thinking to copy bad speaker/mic efs partition to another one, but copying over efs partition didn't do anything. I thought it will copy over IMEI stuff to this second phone?
Click to expand...
Click to collapse
You have an interesting challenge. .
Have you tried a restore sd card ?
Check the emmc brickbug if you can.
I believe the hack to get root for the Verizon note 4 writes to the efs partition to clone it into a developer edition. Which every with a hacked Verizon phone like mine has the exact same IMEI 1000000000000 or something like that
Hi
how to flash N910FXXU1DRI2_N910FXXU1DQL1.tar (bootloader_modem.tar) with Heimdall ? I understand I have to untar and flash files separately, but there are not only two files in this .tar, there are 7 files !
Can you guide me please ?
Thanks
louisJJ said:
Hi
how to flash N910FXXU1DRI2_N910FXXU1DQL1.tar (bootloader_modem.tar) with Heimdall ? I understand I have to untar and flash files separately, but there are not only two files in this .tar, there are 7 files !
Can you guide me please ?
Thanks
Click to expand...
Click to collapse
Incase you haven't solved it yet.
This worked for me on manjaro-linux with heimdall installed as well as on debian-sid with heimdall-flash.
As root:
Code:
heimdall detect
To make sure your device is detected
Code:
heimdall flash --APNHLOS /tmp/e/NON-HLOS.bin --ABOOT /tmp/e/aboot.mbn --MODEM /tmp/e/modem.bin --RPM /tmp/e/rpm.mbn --SBL1 /tmp/e/sbl1.mbn --DBI /tmp/e/sdi.mbn --TZ /tmp/e/tz.mbn --no-reboot
Where for example /tmp/e/ is your path to files to flash.
When process finished successfully pull battery and reboot to recovery.
Thanks a lot!
Hi,
I am having troubles with the modem that is listed in this thread...N910FXXU1DQL1....I have poor reception.
Can someone point me to a full list of modems I can test ? I am installing LineageOS 16 from this tuto.
Thanks
louisJJ said:
Hi,
I am having troubles with the modem that is listed in this thread...N910FXXU1DQL1....I have poor reception.
Can someone point me to a full list of modems I can test ? I am installing LineageOS 16 from this tuto.
Thanks
Click to expand...
Click to collapse
Just adding this here in case anyone else is looking for it
N910FXXU1DRI2_N910FXXU1DRI1.tar.md5
Caution: backups made with older versions than v3.4.0 seem to be not compatible. I wanted to restore a backup I made with v3.2.1 with v3.4.0 but the system couldn't boot. Verified this two times. Had to go back to v3.21 to perform a successful restore.
It's better using TWRP 3.3.1 for all flashing operations.
I think we have the same odin
PasSlert said:
Hello,
First of all, thank you for you continuous work and courage to keep our devices up to date, by you I mean the whole awesome team !
Updated of TWRP 3.3.1-0 was successfully done within TWRP 3.3.0-0 - flash image - recovery.
Update of Bootloader_Modem file was a bit longer :
- with the provided Odin3 v3.13.1 - the ID:COM was going crazy connecting/disconnected no matter what USB port (2.0 and 3.0) I was using and I was using OEM cable.
<ID:0/005> Added!!
<ID:0/005> Removed!!
<ID:0/005> Added!!
<ID:0/005> Removed!!
...
Updating Samsung Mobile Phone Driver didn't help (but just in case, link = https://forum.xda-developers.com/showpost.php?p=78823944&postcount=623 )
Even after a restart of Windows 10 OS.
Luckily I had kept a zip of Odin3_v3.10.7 close by me (this was the version I used for my previous BL/CP update) and using this version was fine, my n910f is correctly on DRI2_DQL1.
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1100)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> modem.bin
<ID:0/005> NON-HLOS.bin
<ID:0/005> rpm.mbn
<ID:0/005> sbl1.mbn
<ID:0/005> sdi.mbn
<ID:0/005> tz.mbn
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
I'll report if anything good or bad is noticed within the next few days.
Thank you again i think we have the same version of odin, how did you downgrade it,or you have 2 version of odin installed on you computer which you can switch to any version you want to use
Click to expand...
Click to collapse
Odin doesn't have to be installed.
Just to doubleclick any of the different .exe starts the appropriate version.
I have a Galaxy S8+ (SM-G955U).
After a few days it was working just fine, then suddenly after I let it die out of charge, it did not turn on. During this state, the phone was rooted.
First, the Issue was loading into Download mode (still happening), it loads but the screen is black. I use Odin so it tells me when the Pc recognize it, and it does. I tried flashing stock ROM with Odin but it stays on setup and if not it stays on Initializing forever, now the problem is a bit easier to solve because it just stays stuck on the Samsung Logo. Odin Recognizes my device but doesn't flash anything. It says on analysis forever and if it continues to setup connection it stays there for 15-20 minutes . It fails. <OSM> All threads completed ( succeed 0 / failed 1).
I can only boot to Download Mode nothing else. Not even Recovery Mode.
Not sure if this matters but this is my full model
SM-G955UZKATMB ( Tried finding this exact firmware but no luck.
I don't have a recovery mode for some reason it won't boot to this mode only Download mode.
Not sure if this matter but it doesn't charge either, it stays on the charging state, a blank circle with a thunderbolt symbol inside.
IF anyone has any idea or hint of what I can do, please comment.
Thanks again.
<ID:0/009> Odin engine v(ID:3.1203)..
<ID:0/009> File analysis.. (TAKES A WHILE)
<ID:0/009> skip file list for home binary
<ID:0/009> apdp.mbn
<ID:0/009> msadp.mbn
<ID:0/009> persist.img.ext4
<ID:0/009> Home Binary Download
<ID:0/009> SetupConnection.. (TAKES DOUBLE THE WHILE)
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Maybe more expertise is available here: https://forum.xda-developers.com/galaxy-s8+
zen2o1 said:
I have a Galaxy S8+ (SM-G955U).
After a few days it was working just fine, then suddenly after I let it die out of charge, it did not turn on. During this state, the phone was rooted.
First, the Issue was loading into Download mode (still happening), it loads but the screen is black. I use Odin so it tells me when the Pc recognize it, and it does. I tried flashing stock ROM with Odin but it stays on setup and if not it stays on Initializing forever, now the problem is a bit easier to solve because it just stays stuck on the Samsung Logo. Odin Recognizes my device but doesn't flash anything. It says on analysis forever and if it continues to setup connection it stays there for 15-20 minutes . It fails. <OSM> All threads completed ( succeed 0 / failed 1).
I can only boot to Download Mode nothing else. Not even Recovery Mode.
Not sure if this matters but this is my full model
SM-G955UZKATMB ( Tried finding this exact firmware but no luck.
I don't have a recovery mode for some reason it won't boot to this mode only Download mode.
Not sure if this matter but it doesn't charge either, it stays on the charging state, a blank circle with a thunderbolt symbol inside.
IF anyone has any idea or hint of what I can do, please comment.
Thanks again.
<ID:0/009> Odin engine v(ID:3.1203)..
<ID:0/009> File analysis.. (TAKES A WHILE)
<ID:0/009> skip file list for home binary
<ID:0/009> apdp.mbn
<ID:0/009> msadp.mbn
<ID:0/009> persist.img.ext4
<ID:0/009> Home Binary Download
<ID:0/009> SetupConnection.. (TAKES DOUBLE THE WHILE)
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
You need to use latest firmware for example this one :
https://samfrew.com/download/Galaxy__S8+__/hsjp/TMB/G955USQU5DSD3/G955UOYN5DSD3/
Use slow download and IDM manager ...
After that extract firmware and flash with Odin ...
Hi,
I did a lot of trying to get twrp installed.
After a while I followed a hint and it worked but I lost Magisk.
After installing Magisk I got a bootloop. Magiskuninstaller didn't work and all other methods I know also didn't help.
Now I have only twrp working and maybe that's the only possibility to install anything, because in ODIN I always get failures
e.g.
Trying to install bootloader:
<ID:0/007> abl.elf
<ID:0/007> xbl.elf
<ID:0/007> xbl_config.elf
<ID:0/007> FAIL! (Auth)
and
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007>
<ID:0/007> Re-Partition operation failed.
or, when I tick Re-Partition in options
<ID:0/007> Can't open the specified file. (Line: 2006)
any help would be appreciated
Firstly, and please forgive me for nitpicking in your time of dread, if your device can power on it is not bricked, despite what so many uninformed folks say; "bricked" means there is no way to get it to even power on. And since I'm in 'education mode' there is no such thing as "soft brick"; it's like saying something is "kinda dead", and there is no such things as zombies irl.
Anyways, have you tried resetting the tab in recovery mode? Good instructions here:
https://www.hardreset.info/devices/samsung/samsung-galaxy-tab-s6/recovery-mode/
TiTiB said:
Anyways, have you tried resetting the tab in recovery mode? Good instructions here:
https://www.hardreset.info/devices/samsung/samsung-galaxy-tab-s6/recovery-mode/
Click to expand...
Click to collapse
First: Thanks for your support
But: I'm in twrp recovery not in stock
and I cannot enter safe mode
any solution for this?
Tronje said:
First: Thanks for your support
But: I'm in twrp recovery not in stock
and I cannot enter safe mode
any solution for this?
Click to expand...
Click to collapse
I don't think I've had to use button combos while in TWRP, but their purpose is to *force* your device in to a certain state (in this case Recovery), no matter what state they are currently in. Usually in such cases where it looks like critical files or operations are messed up, common, and sound, advice is to get back to stock and then do, whatever.
Other than that, I'll have to defer to what others have to say. Good Luck!
or is there a way to do it via sideload?
it's totally crazy, nothing seemes to work
I was able to install stock boot image and stock recovery that I extracted from firmware that I downloaded from samfrew hopefully I could solve the problems with odin - but failed
I'm even not able to shut down the tablet when connected to powercable - there is a permanent bootloop
I was able to take some photos. Maybe someone will realize what else I could try to do. The large photo shows, what happened when I tried to sideload several versions of the downloaded firmware
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tronje said:
or is there a way to do it via sideload?
it's totally crazy, nothing seemes to work
I was able to install stock boot image and stock recovery that I extracted from firmware that I downloaded from samfrew hopefully I could solve the problems with odin - but failed
I'm even not able to shut down the tablet when connected to powercable - there is a permanent bootloop
I was able to take some photos. Maybe someone will realize what else I could try to do. The large photo shows, what happened when I tried to sideload several versions of the downloaded firmware
View attachment 4988349
View attachment 4988351
View attachment 4988353
View attachment 4988355
Click to expand...
Click to collapse
I'm not an expert here by any means, but I think if you can get to fastboot/bootloader you can use ODIN to do a full restore. I would think you can also use fastboot to just restore the recovery partition as well.
ChrisDos said:
I'm not an expert here by any means, but I think if you can get to fastboot/bootloader you can use ODIN to do a full restore. I would think you can also use fastboot to just restore the recovery partition as well.
Click to expand...
Click to collapse
Dear,
did you really read my post?
I need real, detailled help because I'm always getting errors in Odin.
I think Odin is no longer an option.
Mostly it ends with an FAIL! (Auth)
or Re-Partition operation failed
or, when I tick Re-Partition in options: <ID:0/007> Can't open the specified file. (Line: 2006)
I was so desperate that I was looking for a PIT-file, who knows wherefore, but no success.
I ticked and unticked I think every possible options in Odin, tried several releases of firmware with several releases of Odin-Software and also different twrp releases.
My last hope was my old notebook, as I read, that sometimes there are differences in behaviour between some PC, but failed again.
Maybe a detailed instruction how and what to sideload or another PIT-File (I found only this one: GTS6L_EUR_OPEN.pit)
Maybe that's the problem: I'm using German firmware with European PIT? But I couldn't find European firmware oder German PIT
Tronje said:
Dear,
did you really read my post?
I need real, detailled help because I'm always getting errors in Odin.
I think Odin is no longer an option.
Mostly it ends with an FAIL! (Auth)
or Re-Partition operation failed
or, when I tick Re-Partition in options: <ID:0/007> Can't open the specified file. (Line: 2006)
Click to expand...
Click to collapse
Might want to use Frija to download the firmware. If ODIN is no longer an option, then all is lost. I highly doubt that is though. I've had issues with specific USB cables not working or a bad USB port. I wouldn't panic yet as TiTiB said. As long as you can get it to turn on and get to the bootloader, there should be a way to recover it.
Looks at the Tab 5Se, S10, note 10, etc threads on recoveries. The Tab S6 forums don't seem to be nearly as prolific as other forums.
I know you are at your wits end, but hang end there. Try using Frija to get the proper firmware. You might even try going back to the original or second release in August of last year. You key is going to be getting ODIN to do the work though. I also fine it ludicrous that the Samsung devices have so many different boot options using the keys. Evening the timing of pressing the buttons in a certain order is critical.
ChrisDos said:
Might want to use Frija to download the firmware.
Click to expand...
Click to collapse
ok, I did, downloaded, flashed with the same disappointing result
ChrisDos said:
If ODIN is no longer an option, then all is lost. I highly doubt that is though. I've had issues with specific USB cables not working or a bad USB port. I wouldn't panic yet as TiTiB said. As long as you can get it to turn on
Click to expand...
Click to collapse
I even cannot shut it down. That's what make me think, it's lost.
ChrisDos said:
and get to the bootloader, there should be a way to recover it.
Click to expand...
Click to collapse
I didn't find any. In bootloader there should be a warning message first before entering, but there is none. And later some characters (a status message or something like that) on the top of the screen, but there is none.
ChrisDos said:
Looks at the Tab 5Se, S10, note 10, etc threads on recoveries. The Tab S6 forums don't seem to be nearly as prolific as other forums.
Click to expand...
Click to collapse
that's my very last hope
Tronje said:
I even cannot shut it down. That's what make me think, it's lost.
Click to expand...
Click to collapse
All is not lost - If it powers on, it isn't bricked - Simply software malfunctioning. Would assume you've corrupted the system with Magisk, which means just flashing stock should fix it. No idea why Odin isn't working though, since you've already flashed back to stock recovery - Are you sure you have the correct Firmware? Your bootloader is probably locked again, so you won't be able to flash anything but stock.
bartleby999 said:
All is not lost - If it powers on, it isn't bricked - Simply software malfunctioning. Would assume you've corrupted the system with Magisk, which means just flashing stock should fix it. No idea why Odin isn't working though, since you've already flashed back to stock recovery - Are you sure you have the correct Firmware? Your bootloader is probably locked again, so you won't be able to flash anything but stock.
Click to expand...
Click to collapse
I tried all available firmware versions with different odin releases. It's always the same:
<ID:0/010> Initialzation..
<ID:0/010>Set PIT file..
<ID:0/010> DO NOT TURN OFF TARGET!!
<ID:0/010> FAIL! (Auth)
<ID:0/010>
<ID:0/010> Re-Partition operation failed.
Trying to flash twrp recovery:
<ID:0/007> NAND Write Start!!
<ID:0/007> SingleDownload.
<ID:0/007> recovery.img
<ID:0/007> vbmeta.img
<ID:0/007> FAIL! (Auth)
<ID:0/007>
I really really would like to know where this FAIL! (Auth) comes from. But all google search brought solutions not fitting to my situation.
Few minutes ago it just let me flash TWRP_T865_3.3.1-9.tar without grumbling - but there is no twrp recovery, only stock
<ID:0/007> Odin engine v(ID:3.1301)..
<ID:0/007> File analysis..
<ID:0/007> Total Binary size: 0 M
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> NAND Write Start!!
<ID:0/007> SingleDownload.
<ID:0/007> RQT_CLOSE !!
<ID:0/007> RES OK !!
<ID:0/007> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
with TWRP_T865_3.3.1-10L.tar I'm getting error message again
Tronje said:
I tried all available firmware versions with different odin releases. It's always the same:
...
Click to expand...
Click to collapse
I just posted a solution here: https://forum.xda-developers.com/showpost.php?p=82229527&postcount=7
Moe5508 said:
I just posted a solution here: https://forum.xda-developers.com/showpost.php?p=82229527&postcount=7
Click to expand...
Click to collapse
That's great news. Now I got one step further.
For the first time there are some characters on the screen. (see attached file)
... but FAIL! (Auth)
persists
when I tried flashing BL-File
That's great indeed.
Now we get down to the firmware issues...it appears you might have upgraded to a higher BL one which may not allow you to downgrade BL)...might I suggest you try a different firmware?
And you are also already OEM Unlocked, right?
Was this round one of flashing BL, or round two, as per my guide? Please PM me and lets troubleshoot that way rather...
Moe5508 said:
That's great indeed.
Now we get down to the firmware issues...it appears you might have upgraded to a higher BL one which may not allow you to downgrade BL)...might I suggest you try a different firmware?
And you are also already OEM Unlocked, right?
Was this round one of flashing BL, or round two, as per my guide? Please PM me and lets troubleshoot that way rather...
Click to expand...
Click to collapse
display shows
FRP LOCK : OFF
OEM LOCK : OFF (U)
so I think I'm unlocked
I tried all German 4 firmware releases and I always failed in step 1
I got my device in november with october release and upgraded to december release
Here's the full log of Odin, it always shows the same result:
<ID:0/010> Added!!
<ID:0/010> Odin engine v(ID:3.1301)..
<ID:0/010> File analysis..
<ID:0/010> Total Binary size: 152 M
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> NAND Write Start!!
<ID:0/010> SingleDownload.
<ID:0/010> abl.elf
<ID:0/010> xbl.elf
<ID:0/010> FAIL! (Auth)
<ID:0/010>
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I could try to lock the device, but probably no good idea?
what is strange:
when I try to install twrp recovery I'm getting message
<ID:0/007> Added!!
<ID:0/007> Odin engine v(ID:3.1401)..
<ID:0/007> File analysis..
<ID:0/007> Total Binary size: 0 M
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> NAND Write Start!!
<ID:0/007> SingleDownload.
<ID:0/007> RQT_CLOSE !!
<ID:0/007> RES OK !!
<ID:0/007> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/007> Removed!!
but when I boot, there is no twrp recovery , only stock, nothing changed
Tronje said:
what is strange:
...
but when I boot, there is no twrp recovery , only stock, nothing changed
Click to expand...
Click to collapse
I think this is a TWRP issue then, and you can ask in the thread there...as far as I can recall with flashing TWRP, you must be quick again at first boot to NOT let the device boot fully...you need to boot directly into TWRP else the custom recovery won't stick...
Moe5508 said:
I think this is a TWRP issue then, and you can ask in the thread there...as far as I can recall with flashing TWRP, you must be quick again at first boot to NOT let the device boot fully...you need to boot directly into TWRP else the custom recovery won't stick...
Click to expand...
Click to collapse
Yes, I know. But I don't know what to do with twrp?
There seemes to be no operating system on the tab and there is no possibility to flash one from twrp. I flashed it just to see what would happen. It couldn't get worse.
What I need is a methode flashing by odin or something else with available firmware.
I only know odin. Is there something similar?
Tronje said:
I tried all available firmware versions with different odin releases. It's always the same:
<ID:0/010> Initialzation..
<ID:0/010>Set PIT file..
<ID:0/010> DO NOT TURN OFF TARGET!!
<ID:0/010> FAIL! (Auth)
<ID:0/010>
<ID:0/010> Re-Partition operation failed.
Trying to flash twrp recovery:
<ID:0/007> NAND Write Start!!
<ID:0/007> SingleDownload.
<ID:0/007> recovery.img
<ID:0/007> vbmeta.img
<ID:0/007> FAIL! (Auth)
<ID:0/007>
I really really would like to know where this FAIL! (Auth) comes from. But all google search brought solutions not fitting to my situation.
Few minutes ago it just let me flash TWRP_T865_3.3.1-9.tar without grumbling - but there is no twrp recovery, only stock
<ID:0/007> Odin engine v(ID:3.1301)..
<ID:0/007> File analysis..
<ID:0/007> Total Binary size: 0 M
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> NAND Write Start!!
<ID:0/007> SingleDownload.
<ID:0/007> RQT_CLOSE !!
<ID:0/007> RES OK !!
<ID:0/007> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
with TWRP_T865_3.3.1-10L.tar I'm getting error message again
Click to expand...
Click to collapse
Sorry but I have to ask, why are you repartitioning anything? The only option you should touch in Odin from the options available on the left side of the screen is automatic reboot as far as I'm aware.
I would slow down and reread from the beginning.
1. Get all the correct firmware, double checking model and version numbers (is it SM-T860 or SM-T860N for example).
2. Prioritize your tasks and do them 1 at a time (get recovery working correctly, then install stock firmware, then if desired install TWRP OR root, one or the other, don't attempt to speed things up and try flashing 2 operations at once).
3. Reread what you are about to attempt before you start the process.
4. Don't try and improve on the instructions you are following, follow them exactly.
If you do the above I really can't see how you can go wrong.
Feel free to PM me any questions and if I can help I will.
Good luck brother
Sent from my [device_name] using XDA-Developers Legacy app