Related
My Galaxy Gio is broken, SUGGESTIONS WHAT TO DO PLEASE ༼ つ X_X ༽つ <<<<<<<<<<<<
Hello fellow members of this forum,
My phone was running AOKP, and today I wanted to try another ROM, so I figured I could update my CWM aswell with this nice touch edition (http://forum.xda-developers.com/showthread.php?t=2691050)
After following the instructions for the installation, I ended up with a phone who just booted - showed the samsung logo - booted again (I guess that's what you call a bootloop?)
It won't boot to recovery aswell, only Download mode
Now here comes the problem:
My Gio won't connect to Odin or Kies (usb not recognized by windows)
Things I've been trying to do:
- Boot into recovery (gets me back into the bootloop)
- Installed USB drivers and Kies (usb not recognized in download mode, however in ramdump mode Kies says it's "Connecting...", but anything wont happen) (maybe wrong USB drivers, can someone who knows they work link their drivers?)
- Tried different USB cables + ports
One thing that came up my mind is that I'm using windows 10, do you think that's the problem?
I will try previous versions of Windows tomorrow
Does anyone know how to solve this?
Thanks for reading!
Few qcom chipsets were affected by a bug in Windows 8.1 USB stack which made them not recognize in Download Mode (or fastboot mode). Drivers aren't an issue, it's the windows itself that's buggy (Actually, it's not a bug but a security feature... but is unfortunately breaking our and few other devices) here. I'm pretty much sure that windows 10 also has this issue.
Solutions:
-> Downgrade your PC to windows 8 (not 8.1) or below and Odin will work.
-> Try some dirty solutions available over the web.
And what steps did you follow to install the recovery? Flashing a recovery by the way mentioned in that thread will not make any harm to your device. Worst it can do was a 'bad recovery install' i.e. your phone won't be able to boot recovery but it will be able to boot on normal android system. Please clearly mention the steps you followed.
Bhargav97 said:
Few qcom chipsets were affected by a bug in Windows 8.1 USB stack which made them not recognize in Download Mode (or fastboot mode). Drivers aren't an issue, it's the windows itself that's buggy (Actually, it's not a bug but a security feature... but is unfortunately breaking our and few other devices) here. I'm pretty much sure that windows 10 also has this issue.
Solutions:
-> Downgrade your PC to windows 8 (not 8.1) or below and Odin will work.
-> Try some dirty solutions available over the web.
And what steps did you follow to install the recovery? Flashing a recovery by the way mentioned in that thread will not make any harm to your device. Worst it can do was a 'bad recovery install' i.e. your phone won't be able to boot recovery but it will be able to boot on normal android system. Please clearly mention the steps you followed.
Click to expand...
Click to collapse
Thanks for reply!
I'm downloading windows 8 and 7 right now to try it out, should I use the kies program to install drivers or this driver package (http://forum.xda-developers.com/showthread.php?t=961956) ?
Am I able to flash the recovery.img via Odin aswell?
Here's what I did:
- I downloaded the recovery.img and put it on the sd card
- Booted and went to terminal emulator, wrote:
su
flash_image recoveryonly /sdcard/recovery.img
- I did a reboot (not to recovery thou), and the phone became like this
Update:
Odin worked with windows 7, FINALLY GOT A PHONE AGAIN WOOHOOO :victory:
Thou I can't seem to install the touch recovery without the same happening again, but I made it work with another recovery + the rom i wanted (http://forum.xda-developers.com/showthread.php?t=2396690)
Update2:
I did some research and it turned out the recovery probably does not support RFS file system
Can I make a switch to ext somehow?
ANYWAY THANK YOU!
lemon1337 said:
Update:
Odin worked with windows 7, FINALLY GOT A PHONE AGAIN WOOHOOO :victory:
Thou I can't seem to install the touch recovery without the same happening again, but I made it work with another recovery + the rom i wanted (http://forum.xda-developers.com/showthread.php?t=2396690)
Update2:
I did some research and it turned out the recovery probably does not support RFS file system
Can I make a switch to ext somehow?
ANYWAY THANK YOU!
Click to expand...
Click to collapse
Using a CyanogenMod ROM (or ROMs based on the same) is a good option for you. They are ext4.
Frankly speaking, The steps you wrote should not break your device booting the android system. Even if it's RFS. Moreover, Recovery has no relation with android system (or its fstype).
Bhargav97 said:
Using a CyanogenMod ROM (or ROMs based on the same) is a good option for you. They are ext4.
Frankly speaking, The steps you wrote should not break your device booting the android system. Even if it's RFS. Moreover, Recovery has no relation with android system (or its fstype).
Click to expand...
Click to collapse
Yeah that's what I thought aswell, so this came as a big question mark for me, I still get the same error with the touch recovery. (nothing works when I install it).
Is it possible for you to make it flashable via .ZIP file(for use in recovery) or Odin file?
Guys: I need your understanding, experience, patience and HEEELP!!!
The history:
2 months ago, I bought a new HUAWEI GR3 (TANGO) TAG-L23. Processor = MT6753T
I tried to root it using KingoRoot. I Messed it up... Got a soft-brick: splash screen boot loop. At that moment, I still had access to Fastboot and Recovery mode (stock recovery).
After tons of days googling, found a TWRP recovery that someone claimed that worked in GR3.
I decided to flash it using fastboot commands from my PC. Result = OK. Flashed and worked like a charm.
Tired of searching a stock/custom firmware for GR3 TAG-L23, I decided to download and flash a GR3 TAG-L22 rom using TWRP.
Result = Messed it up again... this time worst... Hard-bricked I think: the phone didn't show any light, couldn't boot it again in any mode... Dead...
The only hope I had is that it is detected by Windows for about 10 seconds as MEDIATEK USB PORT (COMxx) where xx changes when I connect it from one USB port to another.
Since then, I tried almost every tutorial/video/solution/forum/website over the internet, tried almost every SP Flash tool version from v3.1224 to v5.1628, downloaded every scatter.txt for MT6753 processor, tried changing with/without battery option in SPFT, pressing every phone buttons combos, with no luck...
I always get the same error: S_FT_ENABLE_DRAM_FAIL (0xFC0)
Downloaded and installed almost every driver I found on internet: not overwritting them... I created a Virtual Machine, and test them separately using snapshots. Result = Same DRAM_FAIL error.
last week, got another HUAWEI GR3 TAG-L23, untouched, brand new...
I did the following with the new one:
Flashed TWRP recovery using fastboot commands = OK
Rooted it using SuperSU = OK
executed tons of ADB commands that found over the internet, to dump the partition table and stock rom using dd command = OK (I think... what I got is a bunch of files - system, lk, boot, logo, cache, frp, userdata, secro, recovery, nvdata, protect1 and 2, tee1 and 2, and so on).
Using the partition table information, edited one scatter.txt file for MT6753 and, one by one, adjusted the partition info (start and lenght). I did it because when using any downloaded scatter file, and selecting the files that I got from dd commands, SPFT showed error messages saying them were wrong. After editing it and loading the files that I got from the second phone, SPFT recognized them as good ones.
But.... I'm still getting the d...mn S_FT_ENABLE_DRAM_FAIL (0xFC0) error
Also tried to get a rom backup and scatter file from the second phone using MTK DROID ROOT & TOOLS v2.5.3 with no luck: it shows all phone information (except IMEIs), a green rectangle shows up, but... a weird message appears at right: "ERROR: TotalBytesPerChunk Not Found. Set Default Page/Spare=2048/64 !!!". Then I click on "BLOCKS MAP" button, a new window appears showing the partition info (that already got using adb command prompt) and "create scatter file" button is grayed out... And if I try to perform the backup, it starts fine, but ends with error, and no file is backed up...
Let me mention that I already read and googled the totalbytesperchunk error and the grayed out button stuff and tried all alternatives too, and nothing worked.
My work environment:
PC = Laptop With 8 GB RAM / Windows 10 pro x64
Virtual Machines: Windows 7 pro 32 bits, Windows XP 32 bits, Ubuntu 32 and 64 bits...
What else can I do?
How can I use the second, rooted and working phone to get a rom/firmware working dump? it is possible?
If someone decides to help me, let me know what do you need (dumped files, downloaded scatter.txt files, screenshots, whatever you need...)
COM## is a COM port. You can use a terminal program to directly interact with the device.
You are not completely bricked yet.
I do not have any further details to help you, but I can tell you there is still hope.
Connect the dead device to PC, load up a terminal app (if on windows, just load up the app named Terminal)
See where you can get with that.
good luck
Please Help cesarr4: my TAG-L23 bricked - Need your TWRP
I have a bricked GR3 after using Kingo Root. You mention in the post:
"After tons of days googling, found a TWRP recovery that someone claimed that worked in GR3. I decided to flash it using fastboot commands from my PC. Result = OK. Flashed and worked like a charm."
Please share this TWRP recovery, please.
antonioroa said:
I have a bricked GR3 after using Kingo Root. You mention in the post:
"After tons of days googling, found a TWRP recovery that someone claimed that worked in GR3. I decided to flash it using fastboot commands from my PC. Result = OK. Flashed and worked like a charm."
Please share this TWRP recovery, please.
Click to expand...
Click to collapse
I attached the recovery I'm currently using in the second GR3. I'm still looking forward the stock rom and a way to recover the first one... have u found a way to unbrick it?
Here you can find the recovery too: http://forum.xda-developers.com/android/development/recovery-twrp-3-0-2-0-huawei-tag-l01-p8-t3433520
I have the same problem with kingroot, and cannot find TAG-L23 rom.
I sent my phone to huawei support and they said it's a board problem and need to replace, the cost is near to the phone's original price.... No way!
In clangsm web page there's a stock rom but you need to pay for vip membership.
Please help with this issue.
I'm still trying to get a working rom image from the 2nd GR3 that I bought... No luck yet... I'm plenty sure that there is no need to do hardware replacement... can anyone point me to a tool/step-by-step guide to readback and save a flashable rom image from GR3 phone, and a SP tools that works with GR3 chipset/PCB?
Hi, i have a TAG-L01 and i got the same problem, i've tried a lot with no lucky, it seems sp flash tool don't support our device(or is huawei that don't want).
If you have some ideas please tell me, i will help(our devices are exactly the same, all TAG-Lxx are the same)
Hello
I have a TAG-L23. I was able to install the TRWP recovery mentioned in previous posts. But I do need the Stock ROM, since I am not able to start the phone. It is allways rebooting. any idea where to find the ROM? maybe cesarr4 can do a backup on TWRP from his second phone and we can load it. just make a backup in the recovery and Zip it, then you may share it.
srgg01 said:
Hello
I have a TAG-L23. I was able to install the TRWP recovery mentioned in previous posts. But I do need the Stock ROM, since I am not able to start the phone. It is allways rebooting. any idea where to find the ROM? maybe cesarr4 can do a backup on TWRP from his second phone and we can load it. just make a backup in the recovery and Zip it, then you may share it.
Click to expand...
Click to collapse
Done. Where can I share it for you?
cesarr4 said:
Done. Where can I share it for you?
Click to expand...
Click to collapse
please share your ROM in google drive. i've got same problem here.
Any link to the TAG-L23 ROM? please share as I believe mine is corrupted.
This thread is a tip for Googlers who don't know what to do to fix their Note 5 AT&T phone with the following message:
"An error has occurred while updating the device software. Use the emergency recovery function in the Smart Switch PC Software"
<This screen is Odin Download Mode>
The above error screen is secretly "Download Mode", you do not have to get into Odin Download Mode in order to flash your firmware. If you can't get smart switch to work and you don't know your base band version, like me, then trying all the firmwares until one succeeds might be a solution for you.
Where? <I added links to available firmwares and backups I made>
YOU CAN'T DOWNGRADE FIRMWARE Upgrading reduces the chances you will be able to get rid of AT&T apps + Samsung bloatware someday
Root is not available and the locked bootloader is still locked from release so I wouldn't hold my breath
Warning warning warning you should ask for help from your carrier not me!! Proceed foolishly at your own risk
Edit: Feb 11th, 2017
All of these firmwares are available from XDA Members. PLEASE THANK THEM FOR MAKING THEM!
Samsung/AT&T do not provide these to use!!! NOTICE: I made backup copies for these firmwares but you should get them directly and thank the person who provided them!
(DON'T UPGRADE UNLESS YOU MEAN IT!!!! There's no downgrading from Android 6.01 PHA or higher that I'm aware of, and I'm fairly aware.
OJ1 was taken from XDA Member: JUSMEJOSE on this: THREAD
BACKUP OF: N920AATT2AOJ1_Recovery
OGG was taken from XDA Member: Rolland_K on this: THREAD
N920AUCU1AOGG
PB2 was taken from XDA Member: meraz900 on this: THREAD
N920AUCU2APB2_User_Binary
(I am unsure where I got the backup version of PE6)
PE6 was taken from XDA Member: smxwang on this: THREAD
N920AUCU2BPE6
N920AUCU2BPE6 backup
PK1 was taken from XDA Member: smxwang from this: THREAD
N920AUCS4CPK1
Odin version:
I have used Odin 3.10.6 and 3.12.5 to flash the 6.01 ending in PK1 from the above screen. Either of those odin versions obtained via XDA-developers forum will work.
If you need to retry to flash your firmware with Odin after an error you must reboot. VOLUME DOWN BUTTON + POWER BUTTON + HOME BUTTON. keep holding them, you don't have to unplug it will reboot shortly
Added 02-26-2016 --- PJ1 firmware have a corrupted BL combination file from all known online resources! I recovered param.bin from the damage BL and took the remaining files from PJ1 small ota file
Please give thanks to norbarb for sharing this file when no one could find it and get it direct from norbarb! I couldn't find this file anywhere else and I really needed it for testing, thanks norbarb.
https://forum.xda-developers.com/showpost.php?p=69354814&postcount=8
N920AUCS3CPJ1 firmware (BL file is not Odin flashable if anyone needs me to repack it I might take the time to do that.)
Here's the UP file (found from this forum somewhere this is not my work)
SS-N920AUCU3CPHA-to-S3CPJ1-UP
How to flash unpacked boot.img, recovery.img, sboot.bin and etc:
Unpacked .img, .bin files can be flashed directly using "heimdall flash tool for Linux": https://github.com/Benjamin-Dobell/Heimdall
-- To flash sboon.bin, boot.img, recovery.img and other unpacked firmware files use --> Ubuntu 16.10 with heimdall flash tool for Linux from github. Google how to install dependencies
-- Issues these commands before heimdall. sudo apt-get update, sudo apt-get upgrade, sudo apt-get install build-essential (then read appendix for heimdall readme)
-- Use the frontend for heimdall flash tool for Linux --> sudo apt-get install heimdall-frontend
-- Uncheck auto-reboot, don't boot until all files flashed. I'm uncertain what can happen mixing firmware versions in all cases. download mode is fairly safe, recovery mode sounds risky for data
****** I am collecting all firmware for the AT&T Note 5 up to baseband N920AUCS4CPK1. If you have firmware or update files please list them or I can host send me a pm. ******
I need firmware to create removal tools for customers planning to switch carriers on varying versions. My collection so far is efficient but when I find a way to beat the bootloader I would like my tool to be one step regardless of baseband. While I am still trying to find a competent way to forcibly remove the locked bootloader I am confident I will get there especially with the availability of twrp for almost every other variant along with many great kernels for Android 6.01.
Note: I have no idea how to remove the bootloader without access to dirtycow and I haven't confirmed my fix on baseband beyond N920AUCS4CPK1. I would need help from someone very confident with android to test scope beyond baseband N920AUCS4CPK1
I never considered someone could reach this screen without knowing what Odin is and I really meant this post to help those learning Odin. I am sorry that I have no idea what options are available from AT&T / Samsung, using smartswitch or kies. Generally if you see this screen you achieved doing so using a flashing tool such as, but certainly not limited to, Odin for Windows or Heimdal for Linux/Mac.
It is my opinion you shouldn't flash firmware to your phone unless you know what you're doing. Odin has great protections against corrupt files but you need to obtain legitimate copies of the correct firmware. If you flash a rooting firmware especially from the wrong phone it is a real fight to get back into download mode and then you probably shouldn't screw up twice.
Thanks for your collecting.Now I have PL1 package, I will upload it soon. In fact I have a way to download all Frimware end to the latest QB2.......But it is not for free, each package cost about 2.5USD and only get security path.Now I'm waiting the Nougat firmware, I will upload them when it was released....
droidvoider said:
This thread is a tip for Googlers who don't know what to do to fix their Note 5 AT&T phone with the following message:
"An error has occurred while updating the device software. Use the emergency recovery function in the Smart Switch PC Software"
<This screen is Odin Download Mode>
The above error screen is secretly "Download Mode", you do not have to get into Odin Download Mode in order to flash your firmware. If you can't get smart switch to work and you don't know your base band version, like me, then trying all the firmwares until one succeeds might be a solution for you.
Where? <I added links to available firmwares and backups I made>
YOU CAN'T DOWNGRADE FIRMWARE Upgrading reduces the chances you will be able to get rid of AT&T apps + Samsung bloatware someday
Root is not available and the locked bootloader is still locked from release so I wouldn't hold my breath
Warning warning warning you should ask for help from your carrier not me!! Proceed foolishly at your own risk
Edit: Feb 11th, 2017
All of these firmwares are available from XDA Members. PLEASE THANK THEM FOR MAKING THEM!
Samsung/AT&T do not provide these to use!!! NOTICE: I made backup copies for these firmwares but you should get them directly and thank the person who provided them!
(DON'T UPGRADE UNLESS YOU MEAN IT!!!! There's no downgrading from Android 6.01 PHA or higher that I'm aware of, and I'm fairly aware.
OJ1 was taken from XDA Member: JUSMEJOSE on this: THREAD
BACKUP OF: N920AATT2AOJ1_Recovery
OGG was taken from XDA Member: Rolland_K on this: THREAD
N920AUCU1AOGG
PB2 was taken from XDA Member: meraz900 on this: THREAD
N920AUCU2APB2_User_Binary
(I am unsure where I got the backup version of PE6)
PE6 was taken from XDA Member: smxwang on this: THREAD
N920AUCU2BPE6
N920AUCU2BPE6 backup
PK1 was taken from XDA Member: smxwang from this: THREAD
N920AUCS4CPK1
Odin version:
I have used Odin 3.10.6 and 3.12.5 to flash the 6.01 ending in PK1 from the above screen. Either of those odin versions obtained via XDA-developers forum will work.
If you need to retry to flash your firmware with Odin after an error you must reboot. VOLUME DOWN BUTTON + POWER BUTTON + HOME BUTTON. keep holding them, you don't have to unplug it will reboot shortly
Added 02-26-2016 --- PJ1 firmware have a corrupted BL combination file from all known online resources! I recovered param.bin from the damage BL and took the remaining files from PJ1 small ota file
Please give thanks to norbarb for sharing this file when no one could find it and get it direct from norbarb! I couldn't find this file anywhere else and I really needed it for testing, thanks norbarb.
https://forum.xda-developers.com/showpost.php?p=69354814&postcount=8
N920AUCS3CPJ1 firmware (BL file is not Odin flashable if anyone needs me to repack it I might take the time to do that.)
Here's the UP file (found from this forum somewhere this is not my work)
SS-N920AUCU3CPHA-to-S3CPJ1-UP
How to flash unpacked boot.img, recovery.img, sboot.bin and etc:
Unpacked .img, .bin files can be flashed directly using "heimdall flash tool for Linux": https://github.com/Benjamin-Dobell/Heimdall
-- To flash sboon.bin, boot.img, recovery.img and other unpacked firmware files use --> Ubuntu 16.10 with heimdall flash tool for Linux from github. Google how to install dependencies
-- Issues these commands before heimdall. sudo apt-get update, sudo apt-get upgrade, sudo apt-get install build-essential (then read appendix for heimdall readme)
-- Use the frontend for heimdall flash tool for Linux --> sudo apt-get install heimdall-frontend
-- Uncheck auto-reboot, don't boot until all files flashed. I'm uncertain what can happen mixing firmware versions in all cases. download mode is fairly safe, recovery mode sounds risky for data
****** I am collecting all firmware for the AT&T Note 5 up to baseband N920AUCS4CPK1. If you have firmware or update files please list them or I can host send me a pm. ******
I need firmware to create removal tools for customers planning to switch carriers on varying versions. My collection so far is efficient but when I find a way to beat the bootloader I would like my tool to be one step regardless of baseband. While I am still trying to find a competent way to forcibly remove the locked bootloader I am confident I will get there especially with the availability of twrp for almost every other variant along with many great kernels for Android 6.01.
Note: I have no idea how to remove the bootloader without access to dirtycow and I haven't confirmed my fix on baseband beyond N920AUCS4CPK1. I would need help from someone very confident with android to test scope beyond baseband N920AUCS4CPK1
Click to expand...
Click to collapse
hi all,
could anyone help me,i flashed my samsung note5 n920A with other rom,but failed.now my note5 become like this,i have no idea to solve it.
iam confused....
Jorlu said:
hi all,
could anyone help me,i flashed my samsung note5 n920A with other rom,but failed.now my note5 become like this,i have no idea to solve it.
iam confused....
Click to expand...
Click to collapse
You're not the first person I've help who couldn't connect smart switch, or the other program they have, and it wasn't a problem with the device.. Before we start you should know that AT&T official store can repair your device in a few minutes at their official store. You will be updated to the latest version but there is even some chance they can save your data!!! If you want to do this yourself for one of the many obvious reasons, such as you don't have AT&T store. Don't worry it's not a huge problem because that error screen is Odin Download mode.
1. First thing you should know is that if you upgrade you can't downgrade. If you don't know which version you were on, and that's important to you, then you should download the lowest firmware version first then try the next versions one by one. (SW REV. CHECK FAIL) <--- that means you tried to downgrade
subnote: if you don't care which version and you don't care about root? download the latest firmware PK1 and save yourself the headache.
2. Next you should understand the buttons fully.
POWER + VOL. DOWN for 8 seconds == REBOOT
when screen goes blank release and then press these to enter download mode: POWER + VOL. DOWN + HOME
3. But again I want to remind you that you DON'T need to enter Odin Download Mode, that error screen IS download mode. But you have to reboot before trying. So press Power + Vol. Down and then just let it reboot to that error screen.
4. Download the lowest version firmware linked here. Uncompress the firmware file until it is 4 files.
BL "" "" "" .tar.mdg
AP "" "" "" .tar.mdg
CP "" "" "" .tar.mdg
CSC "" "" "" .tar.mdg
5. You have a NEWER device so you load all 4 slots with those files ( the slots are labeled)
6. If you get SW REV. CHECK FAIL then download the next version of firmware and try again. If you get to the latest one I linked above but you still have that sw rev check fail message then reply back here to let me know and I will look for a later one for you.
Note: You can flash these and get your phone to turn off if you get tired and want a break
You can flash ANY boot.img and recovery.img to your phone and eliminate that error message almost 100% of the time.. This isn't a repair method unless by some crazy chance you have PJ1 firmware and your boot.img was the problem, I think your system.img is the problem tho.
1. Download these files.
https://drive.google.com/open?id=0B-fnF5v-xg6OR1VWRTItWFVOTVE
2. Flash them with Odin as I described above.. (don't forget to reboot to that error screen again, sounds stupid but it's necessary to reboot to the error screen fresh)
3. Reboot your phone POWER + Vol. Down for 8 seconds or so.. When the screen goes blank quickly release then hold Vol. UP + Power + Home
4. If it didn't show a little green android then enter recovery mode you missed.. repeat step 2..
5. Select power off (don't wipe, that would nuts) but power off is safe even using the wrong firmware version
Here's Odin if anyone needs it. For Note 5 I recommend versions 3.10.7 or 3.12.3
https://mega.nz/#F!5NckmKyL!bUwBEFnadbVcrYeKdm76Tg
--stay clear of 3.12.5 it is possible it changes imei related things, i had to reset mine through at&t website
droidvoider said:
You're not the first person I've help who couldn't connect smart switch, or the other program they have, and it wasn't a problem with the device.. Before we start you should know that AT&T official store can repair your device in a few minutes at their official store. You will be updated to the latest version but there is even some chance they can save your data!!! If you want to do this yourself for one of the many obvious reasons, such as you don't have AT&T store. Don't worry it's not a huge problem because that error screen is Odin Download mode.
1. First thing you should know is that if you upgrade you can't downgrade. If you don't know which version you were on, and that's important to you, then you should download the lowest firmware version first then try the next versions one by one. (SW REV. CHECK FAIL) <--- that means you tried to downgrade
subnote: if you don't care which version and you don't care about root? download the latest firmware PK1 and save yourself the headache.
2. Next you should understand the buttons fully.
POWER + VOL. DOWN for 8 seconds == REBOOT
when screen goes blank release and then press these to enter download mode: POWER + VOL. DOWN + HOME
3. But again I want to remind you that you DON'T need to enter Odin Download Mode, that error screen IS download mode. But you have to reboot before trying. So press Power + Vol. Down and then just let it reboot to that error screen.
4. Download the lowest version firmware linked here. Uncompress the firmware file until it is 4 files.
BL "" "" "" .tar.mdg
AP "" "" "" .tar.mdg
CP "" "" "" .tar.mdg
CSC "" "" "" .tar.mdg
5. You have a NEWER device so you load all 4 slots with those files ( the slots are labeled)
6. If you get SW REV. CHECK FAIL then download the next version of firmware and try again. If you get to the latest one I linked above but you still have that sw rev check fail message then reply back here to let me know and I will look for a later one for you.
Note: You can flash these and get your phone to turn off if you get tired and want a break
You can flash ANY boot.img and recovery.img to your phone and eliminate that error message almost 100% of the time.. This isn't a repair method unless by some crazy chance you have PJ1 firmware and your boot.img was the problem, I think your system.img is the problem tho.
1. Download these files.
https://drive.google.com/open?id=0B-fnF5v-xg6OR1VWRTItWFVOTVE
2. Flash them with Odin as I described above.. (don't forget to reboot to that error screen again, sounds stupid but it's necessary to reboot to the error screen fresh)
3. Reboot your phone POWER + Vol. Down for 8 seconds or so.. When the screen goes blank quickly release then hold Vol. UP + Power + Home
4. If it didn't show a little green android then enter recovery mode you missed.. repeat step 2..
5. Select power off (don't wipe, that would nuts) but power off is safe even using the wrong firmware version
Click to expand...
Click to collapse
thank alot ,my note5 already work after i flash N920AUCS4CPK1.
thank you,,,thank you...
may i ask you is it possible my note 5 can flash others rom?
iam from indonesia, i gonna give this phone to my mom, but i need to flash the rom with indonesian language,
is there any international rom(within indonesian language) i can use?
Jorlu said:
thank alot ,my note5 already work after i flash N920AUCS4CPK1.
thank you,,,thank you...
may i ask you is it possible my note 5 can flash others rom?
iam from indonesia, i gonna give this phone to my mom, but i need to flash the rom with indonesian language,
is there any international rom(within indonesian language) i can use?
Click to expand...
Click to collapse
Is Indonesian listed as a language in settings? check
SETTINGS | SYSTEM | Language and Input <--- if not here I don't know how to solve, i will keep my eyes open for a solution for her.
That version that you're on is within scope of my current work to allow custom roms, but currently I'm still developing the method. (this bootloader is locked I will get around it eventually).. If you upgrade beyond that version I don't know if I can get root again. Best thing to do is give me a couple months to see if I can conquer the bootloader, I think I will win. Don't pass that firmware version that you are on PK1
thank you,hope soon i will win it.
---------- Post added at 08:24 PM ---------- Previous post was at 08:23 PM ----------
there is no indonesian language in the list
after flash my note5 n920a hotspot cant be active,
is there any way can solve it
My first guess is that a package it needs is disabled or damaged. But also you should know that sometimes I have to flash twice in a row with Samsung devices after a crashed out install to get it right again. Also... Did you check logcat to see what the problem is? There is a lot of information coming through logcat and while a couple errors isn't uncommon we always want to watch it after a customization to see what fails.
I am just getting back after several days away if you're still not able to solve this in the next couple days I will test it on mine, to check dependencies and etc.
cool tools:
adb logcat
Android Studio has a tool called 'monitor' search how to open it for Windows/Linux
adb shell pm list packages -e <---- list enabled packages only
adb shell pm list packages -d <---- list disabled packages only
droidvoider said:
This thread is a tip for Googlers who don't know what to do to fix their Note 5 AT&T phone with the following message:
"An error has occurred while updating the device software. Use the emergency recovery function in the Smart Switch PC Software"
<This screen is Odin Download Mode>
The above error screen is secretly "Download Mode", you do not have to get into Odin Download Mode in order to flash your firmware. If you can't get smart switch to work and you don't know your base band version, like me, then trying all the firmwares until one succeeds might be a solution for you.
Where? <I added links to available firmwares and backups I made>
YOU CAN'T DOWNGRADE FIRMWARE Upgrading reduces the chances you will be able to get rid of AT&T apps + Samsung bloatware someday
Root is not available and the locked bootloader is still locked from release so I wouldn't hold my breath
Warning warning warning you should ask for help from your carrier not me!! Proceed foolishly at your own risk
Edit: Feb 11th, 2017
All of these firmwares are available from XDA Members. PLEASE THANK THEM FOR MAKING THEM!
Samsung/AT&T do not provide these to use!!! NOTICE: I made backup copies for these firmwares but you should get them directly and thank the person who provided them!
(DON'T UPGRADE UNLESS YOU MEAN IT!!!! There's no downgrading from Android 6.01 PHA or higher that I'm aware of, and I'm fairly aware.
OJ1 was taken from XDA Member: JUSMEJOSE on this: THREAD
BACKUP OF: N920AATT2AOJ1_Recovery
OGG was taken from XDA Member: Rolland_K on this: THREAD
N920AUCU1AOGG
PB2 was taken from XDA Member: meraz900 on this: THREAD
N920AUCU2APB2_User_Binary
(I am unsure where I got the backup version of PE6)
PE6 was taken from XDA Member: smxwang on this: THREAD
N920AUCU2BPE6
N920AUCU2BPE6 backup
PK1 was taken from XDA Member: smxwang from this: THREAD
N920AUCS4CPK1
Odin version:
I have used Odin 3.10.6 and 3.12.5 to flash the 6.01 ending in PK1 from the above screen. Either of those odin versions obtained via XDA-developers forum will work.
If you need to retry to flash your firmware with Odin after an error you must reboot. VOLUME DOWN BUTTON + POWER BUTTON + HOME BUTTON. keep holding them, you don't have to unplug it will reboot shortly
Added 02-26-2016 --- PJ1 firmware have a corrupted BL combination file from all known online resources! I recovered param.bin from the damage BL and took the remaining files from PJ1 small ota file
Please give thanks to norbarb for sharing this file when no one could find it and get it direct from norbarb! I couldn't find this file anywhere else and I really needed it for testing, thanks norbarb.
https://forum.xda-developers.com/showpost.php?p=69354814&postcount=8
N920AUCS3CPJ1 firmware (BL file is not Odin flashable if anyone needs me to repack it I might take the time to do that.)
Here's the UP file (found from this forum somewhere this is not my work)
SS-N920AUCU3CPHA-to-S3CPJ1-UP
How to flash unpacked boot.img, recovery.img, sboot.bin and etc:
Unpacked .img, .bin files can be flashed directly using "heimdall flash tool for Linux": https://github.com/Benjamin-Dobell/Heimdall
-- To flash sboon.bin, boot.img, recovery.img and other unpacked firmware files use --> Ubuntu 16.10 with heimdall flash tool for Linux from github. Google how to install dependencies
-- Issues these commands before heimdall. sudo apt-get update, sudo apt-get upgrade, sudo apt-get install build-essential (then read appendix for heimdall readme)
-- Use the frontend for heimdall flash tool for Linux --> sudo apt-get install heimdall-frontend
-- Uncheck auto-reboot, don't boot until all files flashed. I'm uncertain what can happen mixing firmware versions in all cases. download mode is fairly safe, recovery mode sounds risky for data
****** I am collecting all firmware for the AT&T Note 5 up to baseband N920AUCS4CPK1. If you have firmware or update files please list them or I can host send me a pm. ******
I need firmware to create removal tools for customers planning to switch carriers on varying versions. My collection so far is efficient but when I find a way to beat the bootloader I would like my tool to be one step regardless of baseband. While I am still trying to find a competent way to forcibly remove the locked bootloader I am confident I will get there especially with the availability of twrp for almost every other variant along with many great kernels for Android 6.01.
Note: I have no idea how to remove the bootloader without access to dirtycow and I haven't confirmed my fix on baseband beyond N920AUCS4CPK1. I would need help from someone very confident with android to test scope beyond baseband N920AUCS4CPK1
Click to expand...
Click to collapse
thank you for this, just what i was needing, but if its not too much trouble, i wouldnt mind a packed up version of the BL file so that it is odin flashable.
thank you
Hello!
I bought a GT-I9195I - 8 GB via Ebay. The former owner tried to flash an update but the battery drained leaving the phone unable to boot.
What I did so far:
normal booting - only showed the model number, not even Samsung boot logo
reovery mode - booted, but showed some Errors (sorry, don't remember them exactly), some partitions could not be mounted
factory reset from stock recovery - failed (some partitions could not be formatted)
wipe cache - failed
Then I got the TWRP for the phone as described in
https://forum.xda-developers.com/ga.../rom-cyanogenmod-14-0-s4-mini-3g-lte-t3471761
and tried to flash it with heimdall flash --RECOVERY recovery.img --no-reboot (running linux on the Desktop, so I can't use ODIN).
This seemed to be successful, but the stock recovery was still there, showing the same errors.
So I tried again, getting the following messages:
Code:
[email protected]:~/Downloads/SamsungS4mini$ sudo heimdall flash --RECOVERY recovery.img --no-reboot
Heimdall v1.4.1
Copyright (c) 2010-2014 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
100%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: RECOVERY upload failed!
Ending session...
Releasing device interface...
The phone showed: "Flash write failure".
Trying to boot ends up in the black screen "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again".
Same result in several tries with TWRP and CWM.
I flashed the TWRP file already this way on another I9195, so I am sure, I've got the correct recovery for this model. Only download-mode is still accessible.
I read some similar threads now, but didn't find something that seemed to match this case.
Is there anything I can do?
I hope that someone can help me.
Regards, Stefan
Hi have you tried to flash stock rom
bzpbavarian said:
Hi have you tried to flash stock rom
Click to expand...
Click to collapse
I thought, I tried. But yesterday found out, this phone is an GT-I9195 LTE (search at imeipro.info). So I had the wrong stock rom. Sammobile is down for normal Downloads until tomorrow. Then I'll fetch the (hopefully) right files and try again.
Someone here has a link to a suiting debrick.img? All the links I found by searching the forum seem to be down.
Okay, I'm giving up now. The phone refuses to flash the original rom and recovery.
Starting with a debrick.img (https://forum.xda-developers.com/showthread.php?t=2473783 was my guide) doesn't change anything.
Maybe the chip is broken? I installed custom recovery and lineage on two other phones this weekend, so I know how to do it.
Thanks for reading and for all the helpful things I found in this forum!
I am unable to unlock OEM on my Samsung Galaxy 10.1 (2014 edition) SM-P605 Tablet and I am looking for help.
Details:
This old Samsung Galaxy 10.1 2014 Tablet (European SM-P605) has the stock 5.1.1 Android (Android security patch level 2017-04-01). I would like to replace the old android with LineageOS, but first I need to unlock the bootloader, which requires me to unlock the OEM.
However I have failed to unlock the OEM, despite following various internet guides (ie putting tablet into developer mode, and if OEM unlock doesn't show up try various Date/Time changes (to the past) + Auto Software update disable, plus trying this many times if it fails to work the first time). OEM unlock never shows up.
wrt seeing the Tablet from my PC, I have tried over a dozen USB cables between PC and Tablet where a few cables will let me see the tablet on my PC (ie I obtain a USB notification and adb can see the Tablet).
As noted, I have adb installed on my GNU/Linux PC and when Samsung Galaxy 10.1 2014 Tablet is running nominally with the cables that work connected between Tablet/PC, in a bash shell on my PC I can see:
Code:
corei7:/home/user # ./adb -d devices
List of devices attached
6fa80ec0 offline
However fastboot, of course, can not see the Tablet as the Tablet is not in download/odin mode.
But when I hold power and volume-down button to successfull reboot to odin mode from that point and on, I can no longer see the Tablet with adb nor can I see it with fastboot (in the bash shell on my PC - the Tablet is also no longer a detected USB device).
Regardless, I do not believe/speclate this to be a PC issue (ie not a Linux nor MS-Windows issue) but rather I think/speculate this issue of fastboot (and adb) not seeing the Tablet in downoad/boot mode is because OEM is still locked. But I can't unlock OEM.
Is there an app I can install to unlock the OEM ?? ... because following the recommended developer/date-time/software-update/reboot sequences on the Tablet all fail (in all orders of combinations), despite many dozens of attempts.
Further to the above, I also tried clearing the cache, and tried a Factory reset, then repeating the advised (from internet searches) recommended developer/date-time/software-update/reboot sequences on the Tablet, which all also still fail (in all orders of combinations), despite various attempts. The OEM lock still does not show up under ' general > developer options '.
Researching this I learned finding the OEM unlock is nominally simple with a Eyxnos CPU in this Tablet, but purportedly difficult (not possible? < unsure > ) with a Snapdragon CPU. My Tablet has a Snapdragon 800 (2.27 GHz) which may be part of the reason I havent solved this.
oldcpu said:
Researching this I learned finding the OEM unlock is nominally simple with a Eyxnos CPU in this Tablet, but purportedly difficult (not possible? < unsure > ) with a Snapdragon CPU. My Tablet has a Snapdragon 800 (2.27 GHz) which may be part of the reason I havent solved this.
Click to expand...
Click to collapse
afaik this old device (same as mine) has no OEM unlocking option.
I just flashed TWRP and carried on.
bmwdroid said:
afaik this old device (same as mine) has no OEM unlocking option.
I just flashed TWRP and carried on.
Click to expand...
Click to collapse
Interesting. Thanks for the note on your experience.
Its old and unused, so I guess I do have nothing to lose. I am currently charging it up, and once its fully charged I will give it a try.
Hello,
I was looking for the same information as you for my Galaxy Note 10.1 SM-P600 and I also think that there is simply no OEM unlock.
However, I can't flash TWRP via Odin, I get a "FAIL" message every time I try. I have to reflash the official firmware to reboot the tablet otherwise I get an error telling me to connect it to Kies....
Can anyone know where my error comes from? (the tablet is not rooted)
Mkj76000 said:
... However, I can't flash TWRP via Odin, I get a "FAIL" message every time I try. I have to reflash the official firmware to reboot the tablet otherwise I get an error telling me to connect it to Kies....
Can anyone know where my error comes from? (the tablet is not rooted)
Click to expand...
Click to collapse
Gotta provide more info.
Which Odin version?
Complete! TWRP filename?
I read it's recommended not to have KIES installed when using Odin but standard Samsung phone drivers only.
Sorry. I have Odin 3.14.4 It looks like this :
{
"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"
}
As for TWRP, this is the latest version that I have downloaded here : https://eu.dl.twrp.me/lt03wifiue/
The file is twrp-3.6.0_9-0-lt03wifiue.img.tar
I haven't installed Kies, I was just quoting the error message displayed on the tablet. I restored it via Odin with the latest version of 5.1 from February 2019 (XEF France)
I did manage to install CWM touch from this link (latest version) via Odin. I then tried to install TWRP from CWM via a zip file (also found on the TWRP site link above but it's version 2.8.7). I was able to boot into TWRP but the touchscreen doesn't work so it's unusable.
I am out of ideas, thanks in advance for your help.
Mkj76000 said:
Sorry. I have Odin 3.14.4 It looks like this : View attachment 5531771
As for TWRP, this is the latest version that I have downloaded here : https://eu.dl.twrp.me/lt03wifiue/
The file is twrp-3.6.0_9-0-lt03wifiue.img.tar
I haven't installed Kies, I was just quoting the error message displayed on the tablet. I restored it via Odin with the latest version of 5.1 from February 2019 (XEF France)
I did manage to install CWM touch from this link (latest version) via Odin. I then tried to install TWRP from CWM via a zip file (also found on the TWRP site link above but it's version 2.8.7). I was able to boot into TWRP but the touchscreen doesn't work so it's unusable.
I am out of ideas, thanks in advance for your help.
Click to expand...
Click to collapse
Did you reinstall stock as one(if available at all) or multiple part file?
I always use multiple parts after having trouble with a one part file.
You've put twrp in Odin AP didn't you?
Never worked with philz-touch so idk if it can replace itself with/by flashed TWRP...zip.
Tested older TWRP...tars as well?
Btw: On these old devices I always use Odin 3.09 which always worked.
I was only able to download a rom in one file. If you have a site where I can find a rom with several files I can try.
I also tried to flash an old version of TWRP (2.8) via Odin but it doesn't work.
I have just tried again with Odin 3.09, same error.
Every time I use the AP box
Mkj76000 said:
..... If you have a site where I can find a rom with several files ......
Click to expand...
Click to collapse
Using samfirm_reborn_0.3.6.3 checking "binary nature" and "automatic decryption" will give you a zip file containing the 4 files.
bmwdroid said:
afaik this old device (same as mine) has no OEM unlocking option.
I just flashed TWRP and carried on.
Click to expand...
Click to collapse
Thanks again. After following your advice I finally managed to install LineageOS. I stayed with the older LineageOS v.14.1 with android 7.1.1 as I wanted the tablet's camera to work.
Because I am only a GNU/Linux user (I don't do Windows ) I strugged a bit with various guides as almost all are for MS-Windows users to install TWRP.
Installing TWRP from Google Play store, without Tablet rooted did not give sufficient permissions for me to Flash that was consistent with various guides I read. I could not get Magisk (a program that is supposed to give root permissions) to give me full root permissions for TWRP. And for a while it seemed like I was stuck in a 'chicken before the egg' situation (as some guides suggested installing Magisk from TWRP).
Connecting my PC to the Tablet, I also tried adb and fastboot from GNU/Linux - where adb worked but fastboot did not. In the end I installed heimdall and that worked for me under GNU/Linux. To get to this point I had to try various USB cables and use a USB-2.0 port (instead of a USB-3.0 port) on my GNU/Linux PC.
Trying to flash with " --RECOVERY" specified in heimdall did not work for me, but after downloading from Tablet to PC, and looking at the Tablet's PIT contents, I noted 'RECOVERY' (with recovery.img) in "Entry-14" on my specific tablet. Armed with that information, when instead I specified "14" in heimdall (instead of "RECOVERY") I was pleasantly suprised to discover on a Tablet reboot that TWRP installed in the Tablet's boot loader.
Once TWRP was installed it was simple to then flash with TWRP the files for lineage-14.1-20210320-UNOFFICIAL-lt03lte and open_gapps-arm-7.1-stock-20220122 (clearing cache ... etc ... as appropriate per various web instructions). I prevously had placed those ZIP files on the Tablet's storage.
It was quite the adventure and took some time, however eventually success.
If it had not been for your recommendation / observation that there was no OEM unlocking option I would still be stuck there. Many thanks for your help !!
For the record (in case anyone with same Tablet is curious) this is what I did to install TWRP and LineageOS on my Samsung Galaxy 10.1 (2014) SM_P605 (Snapdragon 800) tablet (after obtain helping on this forum not to worry about OEM mode).
I used openSUSE LEAP-15.2 GNU/Linux to flash TWRP-3.2.3-0 on to the tablet. Once TWRP was installed I booted the Tablet to TWRP and used TWRP to flash lineage-14.1-20210320-UNOFFICIAL-lt03lte and open_gapps-arm-7.1-stock-20220122.
Details:
On openSUSE-LEAP-15.2 GNU/Linux I installed android-tools ( https://software.opensuse.org/package/android-tools ) and heimdall ( https://software.opensuse.org/package/heimdall ).
I pre-installed in the Samsung tablet storage (root location) the files: lineage-14.1-20210320-UNOFFICIAL-lt03lte.zip and open_gapps-arm-7.1-stock-20220122.zip . In hindsight I should also have pre-installed a TWRP.zip version, but I failed to do so.
I spent some time checking my various USB cables to pick the best one wrt reliability for copying data/charging devices, and I used a USB-2 port, and not a USB-3 port for connecting my GNU/Linux PC to the Tablet. I previously read that could make the difference in ensuring a successful effort.
I note this was the previous Tablet state when booting to ODIN mode:
Code:
ODIN MODE
PRODUCT NAME: SM-P605
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
KNOX WARRANTY VOID: 0X0
QUALCOMM SECUREBOOT: ENBALE (CSB)
RP SWREV: S2, T2, R2, A2, P2
SECURE DOWNLOAD : ENABLE
UDC START
As near as I could determine, there was no custom bootloader (boot loader may even have been locked ?? ) and the tablet was not rooted.
With the Tablet running I plugged the USB cable into the Tablet. I noted a popup in KDE desktop on my GNU/Linux detecting the Tablet.
I prepositioned in my GNU/Linux PC, in a directory (in which I was to open a bash shell) the TWRP file: twrp-3.2.3-0-lt03lte_20180923.img
On my GNU/Linux PC I opened a bash shell and I typed:
Code:
sudo adb reboot bootloader
That rebooted the Tablet to "Download" (I think also refered to as "FastBoot mode" ). There was no KDE popup this time. However typing :
sudo heimdall detect
gave me an indication that the Tablet was detected by heimdall.
In that same bash shell I then typed:
sudo heimdall print-pit
I scolled through the resultant "pit" output and I found an entry with "RECOVERY" and "recovey.img" (Entry-14). ie
Code:
--- Entry #14 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 15
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 268288
Partition Block Count: 26624
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RECOVERY
Flash Filename: recovery.img
FOTA Filename:
Seeing 'Recovery' in 'Entry-14', in that same bash shell I then typed:
Code:
sudo heimdall flash --14 twrp-3.2.3-0-lt03lte_20180923.img --no-reboot
The Tablet seemed to hang there with a blue line indicating flashing ? I waited a few minutes and there was no further indication on the Tablet display. I thought the flash failed, so I held down the power off to shut down and restart the tablet.
The Tablet to my surprise, rebooted to TWRP. I don't know precisely what caused that (as I described what I did above with a power-off to restart), but I decided to immediately take advantage of the tablet booting to TWRP.
At that point I followed the regular instructions on the Internet for flashing LineageOS on the Tablet from TWRP ... ie using TWRP, to WIPE data, clear CACHE, and flashed lineage-14.1-20210320-UNOFFICIAL-lt03lte.zip with NO reboot specified. I cleared CACHE again (possibly not needed) and then flashed open_gapps-arm-7.1-stock-20220122.zip . Unfortunately I did not have a "TWRP.ZIP" prepositioned on the Tablet, so I was not able to flash that next. I suspect this was a mistake on my part, and if I wish to update again, I will again need to go through the above to put TWRP on the table.
I then rebooted the tablet (disconnecting from PC) and it booted to LineagOS-14.1 (with android-7.1.2).
I am pleased the Tablet camera functions with v.14.1.
I believe with the current flash that TWRP is no longer installed. I have not checked the Tablet's updated PIT output.
I do note the ODIN mode on the table is almost the same, except for Knox warranty void entry which reads "KNOX WARRANTY VOID: 0X1 (1)"
Hopefully the above may help someone - although no guarantees as it could brick your device for all I know. Fortunately it did not brick mine.
==== =====
Prior to the above, what did not work for me with stock Samsung Android 5.1.1:
- fastboot, that came with Android tools, would not work for me when the Tablet was in 'Download'/'ODIN mode'. That is why I switched to using heimdall.
- I tried to root the Tablet prior to installation with Magisk (downloading from the web) but that rooting failed. I tried installing (from Google playstore) TWRP on the Tablet, but it kept saying no root permissions and would not give me flash capable options. I was unable to install Magisk with TWRP (from Google playstore) as I had no root permissions on the tablet. I did not want to use other 3rd party root apps as I was concerned about possible maleware. That is why I ended up using a PC to flash TWRP.
- I tried to flash TWRP with
Code:
sudo heimdall flash --RECOVERY twrp-3.2.3-0-lt03lte_20180923.img
and also with
Code:
sudo heimdall flash --RECOVERY twrp-3.2.3-0-lt03lte_20180923.img --no-reboot
and neither worked.
The first gave an indication that the PIT file was successfully downloaded and that RECOVERY upload was successful, but in fact if failed, as the Tablet would not go to TWRP during a reboot.
In the case of the second heimdall, the tablet just hung for over 10 minutes with a blue bar, so I simply restarted the tablet.
Only by specifying the "14" (from Entry-14) was I able to get heimdall to work for me (having previously determined the RECOVERY was in entry-14).
Hello,
I finally managed to get around my problem.
I managed to install TWRP 3.4.0 via the official TWRP application after flashing CWM with Odin...
I haven't tried to update TWRP to 3.6.0, it's an old tablet that will be replaced soon so I'm not going to procrastinate on it.
So I finally managed to install Lineage OS 17 without any problem (and Magisk). Laborious but functional.
Mkj76000 said:
Hello,
I finally managed to get around my problem.
I managed to install TWRP 3.4.0 via the official TWRP application after flashing CWM with Odin...
I haven't tried to update TWRP to 3.6.0, it's an old tablet that will be replaced soon so I'm not going to procrastinate on it.
So I finally managed to install Lineage OS 17 without any problem (and Magisk). Laborious but functional.
Click to expand...
Click to collapse
Is your version the Verizon? I've been trying to flash a rom for years now