Flashing LineageOS ROM to Galaxy S4 GT-i9505 - Galaxy S 4 Q&A, Help & Troubleshooting

Hi everyone,
so it's been a while that I'm thinking about flashing the LineageOS 14.1 to my Galaxy S4 i9505
so I've got few questions because I'm still hesitating if I should do it or not.
Are the LineageOS builds stable? I saw "nightly" written in the download page, and I'm not sure if it means if the build's stable or not.
if I'll do it, which ROM build shall I use? (a download link would be great if available)
and are there any risks known to flashing it with a LineageOS ROM?
Thanks

What does stable mean by your definition?

There is always a risk when flashing software to any phone; you just have to be prepared for the possibility of a bricked phone.

Rhoban said:
What does stable mean by your definition?
Click to expand...
Click to collapse
well I mean something with minimum of bugs, that's working just fine with no big or critical know issues, like IMEI problems, o camera or wifi...

audit13 said:
There is always a risk when flashing software to any phone; you just have to be prepared for the possibility of a bricked phone.
Click to expand...
Click to collapse
so is there a build that you eventually, or any other members reading this post have installed on their i9505 and working good?
and in case of bricked phone, is it possible to restore the custom ROM, from the backup that's done with the TWRP recovery?

Sometimes, when a phone is severely bricked, it can only be revived using a separate piece of hardware such as an octopus box.
If you don't have TWRP on the phone, do this:
make sure the phone is running the latest bootloader and ROM;
download laest tar versionTWRP for the i9505 from here: https://dl.twrp.me/jfltexx/
download Odin 3.07 from here: https://www.google.ca/url?sa=t&rct=...ntid=1168421&usg=AOvVaw0aq_x8M8nbsqDFAFe9tFoy
open Odin, put TWRP into the PDA box, uncheck eveything except f reset time;
connect the phone to the computer in download mode and flash the phone;
when you see the word "reset" in Odin's status window, disconnect the USB cable from the phone, remove the battery, replace the battery, boot into recovery using the button combination.
If everything went fine, the phone should be running TWRP.
With TWRP on the phone you can backup your existing ROM, flash custom ROMs, and backup all of the phone's important partitions, including the efs folder.
Things that should not be done:
never flash a custom bootloader;
never flash any ROM or kernel not specficically designed for your phone; and
be prepared for disaster and the possibility you will ruin the phone.
Everyone's needs are different so I suggest flashing different ROMs to get use to the idea of flashing.
Depending on the severity of the brick, TWRP can be used to revive the phone. Odin with a stock ROM would be better IMHO.

audit13 said:
Sometimes, when a phone is severely bricked, it can only be revived using a separate piece of hardware such as an octopus box.
If you don't have TWRP on the phone, do this:
make sure the phone is running the latest bootloader and ROM;
download laest tar versionTWRP for the i9505 from here: https://dl.twrp.me/jfltexx/
download Odin 3.07 from here: https://www.google.ca/url?sa=t&rct=...ntid=1168421&usg=AOvVaw0aq_x8M8nbsqDFAFe9tFoy
open Odin, put TWRP into the PDA box, uncheck eveything except f reset time;
connect the phone to the computer in download mode and flash the phone;
when you see the word "reset" in Odin's status window, disconnect the USB cable from the phone, remove the battery, replace the battery, boot into recovery using the button combination.
If everything went fine, the phone should be running TWRP.
With TWRP on the phone you can backup your existing ROM, flash custom ROMs, and backup all of the phone's important partitions, including the efs folder.
Things that should not be done:
never flash a custom bootloader;
never flash any ROM or kernel not specficically designed for your phone; and
be prepared for disaster and the possibility you will ruin the phone.
Everyone's needs are different so I suggest flashing different ROMs to get use to the idea of flashing.
Depending on the severity of the brick, TWRP can be used to revive the phone. Odin with a stock ROM would be better IMHO.
Click to expand...
Click to collapse
thank you your answer gave me the TWRP recovery install process.
but in my original question, shall I flash a "nightly" build ROM to my phone? I want to upgrade to nougat with LineageOS 14.1 but not sure if it is safe to falsh a nightly build?

Nightlies can be very unstable. The rc releases would be more stable. Regardless of whether it is rc or nightly, they can be stable or unstable depending on how the phone and which apps are used.

Related

Install Recovery and CM on Locked I9500

Hi All,
I'm not sure if this is the right place to post this as I'm relatively new to posting on XDA. My girlfriend has a Galaxy S4 (I337) that I quickly and easily installed Cyanogenmod on. It's awesome and significantly better than TouchWiz. So, I bought an S4 off Ebay assuming it would be similar enough. It turns out this new S4 is an I9500 and before shipping it was updated to 4.3, which appears to lock the bootloader and prevent downgrading. I've tried Odin, Heimdall, ADB, Philz, Chainfire, Cofface, stock ROMs, etc with no luck. Today I did manage to root the phone and confirm root with TowelRoot. I'm wondering/hoping someone might have some resources to get CM on this thing. While I'd prefer not to brick it I am willing to take risks as I have a Razr (soft-bricked and unbricked) running CM and am relatively comfortable with computers/Linux.
I've been Googling and trying things for a month now and can't even find that much information on the locked bootloader. Any help would be greatly appreciated, thanks.
--
SL
The I9500 doesn't have a locked bootloader. You just can't downgrade from 4.3 to 4.2.2 with official roms. Same applies when you are running 4.4, then you also can't downgrade officially.
Just flash a custom recovery true Odin and flash away.
Why would you even want to downgrade? Are you sure you are picking the right files? You cant flash the files for the I337 on the I9500. So just go to the section for the I9500 roms and flash away.
Hi Lennyz1988,
Thanks for the quick reply. I don't specifically want to downgrade but that's the last option I've tried. Ultimately the goal is to put Cyanogenmod on the phone. When I attempt to upload any file via Odin I get "secure magiccode check fail : boot" (or fail : recovery) depending on what I'm flashing. All the reading I've done says that when these phones are updated to 4.3 a fix has been applied that stops Odin from working. Thus, I my last resort is/was to try and downgrade. As I said, I've been Googling for the last month and while few people have posted about this I have not found any solutions.
Hoping someone might have a solution or anything new to try that I haven't tried already, thanks again,
--
SL
Download the latest TWRP recovery:
http://techerrata.com/browse/twrp2/i9500
Fire it up in Odin under PDA. You need the .tar (DON'T EXTRACT IT).
If it fails:
- Different usb port
- Different cable
- Different pc
- Reinstall drivers
- Make sure Kies is not running the background.
Or you can use heimdall to flash it. Use the command line though:
heimdall flash --recovery nameoftherecovery.img (you need the .img instead of the .tar)
No luck there, Odin still fails with the same message. I have tried Heimdall on 2 different computers (4 different usb cables) and always get the libusb 12 error.
Since I have root access I figured I might be able to wipe the recovery partition from a terminal emulator. I copied recovery.img from the I9500 CWM to the internal sd card. I then went to /dev/block/msm_sdcc.1/by-name to figure out what partition is recovery, turns out its 21. I then did “dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p21”. I then booted into recovery and it just hung up. I had previously found a stock recovery partition so I flashed that via Odin (the only file I have found that works flashing via Odin). I could then boot back into the normal recovery. I then tried flashing both recovery and cache with the CF Auto files (cache is partition 18). Same result, it just hangs when trying to boot into recovery. At one point I did manage to flash a recovery that then came up with a warning about “software installed that is not supported by AT&T” and I couldn’t get past that so had to flash the stock recovery again.
On a side note, I accidentally wiped the EFS partition in this process (if found a tutorial that shows the S3 had recovery in partition 10, which is EFS on the S4). As a result 1.) the menu didn’t pop up when I hit the power button and 2.) wifi didn’t work. So, I made an .img of the EFS partition on my GT-I337 and moved it to the I9500 and that worked restoring both. In case anyone makes the same mistake.
I have now also used CWM ROM Manager and GooManger and tried installing recovery that way with no luck.
Just check if the internal memory partitioning is correct ( number, size and format) (use fdisk or parsed).
ODIN will install according to the PIT file and if drivers and cables are OK it is no other explanation than that.
PS: do not trust heimdall data because it just read the PIT file and do not give the true info from the memory part.!
Uhm on the TWRP website they say that the I9500 has it on partition 10.....
This would be the proper partition based on their website:
mmcblk0p10
Are you absolutely sure you have an i9500? Because my guess is that you don't.....
Boot into download mode. What does it say your model is?
Because on the AT&T it's partition 21.... So my guess is that you are messing up....
Thanks everyone for the input/feedback,
Something I think I had forgotten to mention previously, when the initial root/recovery attempts didn't work I downloaded an app to verify it is a genuine Samsung as I have heard of very good knock-offs. It is genuine according to the app.
Good point/catch regarding the location of the recovery partition. Under About Phone it shows as an I9500 and always has. When in download mode it currently shows as I337 but I wasn't sure if that was simply a result of all my attempts so I figured best to go with the one I am certain has been the same since I bought the phone. I had been hesitant to try wiping the recovery with for the I337 as that is how I soft-bricked my RazrHD (ultimately un-bricked it).
Tonight I will try the I337 files and see if Odin is successful. Thanks again.
Damn! Turns out my phone is an I337. The hardward (under the battery) says I9500 and when I plug it into a computer it shows up as I9500. On the weekend I thought I read that there is now the ability to flash recovery and install CyanogenMod on I337 if its updated to 4.4.2. So, I donwloaded the firmware and flashed with Odin. It flashed successfully but now I realize I am mistaken and 1.) cannot flash recovery, and 2.) cannot downgrade. For the time being I have installed Nova Launcher and removed as much of TouchWiz as possible. It's not perfect but at least usable. I'd like to start researching what it would take to flash recovery on this phone but I suspect I'm too busy at this moment.
Thanks everyone for the help,

Galaxy S4 (GT-i9500) Major problem

Hello everyone. I used Albe95 N5+S6 Port rom for my GT-i9500 and it worked flawlessly. I had TWRP recovery. After a lot of using I thought to re-flash the rom and start using it new, so I reinstalled the Rom file on my external SD card and flashed the rom using TWRP recovery and it was a success, but then I noticed I accidentally backed up some things which I didn't wanted to I re-flashed the Rom again, but this time when I (in recovery mode) wiped the data, I chose "Advanced Wipe" or "Advanced Reset" (It was something like that I don't exactly remember. So after that I reflashed the rom and when I had to press "Reboot" a message appeared above saying "Looks like super user is not installed in your phone. Do you wish to install it?" I said Yes and the screen went blank. I tried to reboot but It didn't. I removed the battery and then put it back again and tried to get into recovvery but recovery seemed to be lost and I ended up in Samsung's own factory mode where we have options like reboot, flash using external sd card, flash using adb, enable cp logging and etc. I tried to flash back everything but nothing works. Tried Odin and tried flashing custom firmware but it fails. If I reboot Samsung Galaxy S4 GT-i9500 comes on screen and then it goes blank no boot animation or anything like that. Please help me, Your help will be highly appreciated
I used advanced wipe many times before, I'm pretty sure something else caused your dilema.
And most Odin fail messages are caused by the USB cable, PC USB ports (back ports are recommended) and Windows version.
So what should I do now?
If the problems are caused by the above mentioned, you should obviously try to change things up.
It appears that your phone is in soft-brick.
Also, you lost your TWRP.
Check your bootloader version and install the stock firmware via odin. (If you still fail in odin, As GDreaper pointed out, odin fail could cause by usb cable, port and windows version so you need to keep changing until it works)
Root the phone. Reinstall the TWRP.
Then flash the custom rom again. When you install the custom rom please follow the cooker (custom rom maker) instructions on wiping.
Thanks for your comment. I'm kind of a noob, how do I check bootloader version? and how will I know after checking my bootloader version which stock firmware to install?
Bootloader has nothing to do with it.
If you flash a stock firmware, the Bootloader will also be updated to whatever Bootloader the download firmware has.
The only situation where the Bootloader would matter is if you try to go from lollipop to kitkat, in which case it will fail.
Thank you. My device is back now.
I am glad to hear that your problem is solved.
When I was on kit-kat, I did not check my bootloader version and flash the stock firmware with older version of bootloader which tripped the knox counter on my i 9500. That was why I said to check the bootloader version before installing the stock firmware. You can use app like phone info to see the bootloader info. Then install the firmware with the same or newer bootloader.
I recomend to Update drivers, Windows, Bootloader install Samsung Kies and Install TWRP again, After stock

Really old modem and bootloader, what are my options from here?

It's been a while since I've flashed anything; at least a year, though more likely two. Whatever I have now I'm guessing is a rom called stock(ish)v06, since that's what is listed in my bootloader. I guess the modem (baseband?) is NAE, and I'm still using a very old version of TWRP (2.6.3 according to my signature, haven't checked).
Obviously, the development that still exists for this device has moved well past me. But given how temperamental my device has been lately, I want to give flashing something newer a shot before buying a new device.
Trouble is, I'm not sure how to go about flashing roms and finding the right modem/firmware when everything I have is so out of date.
Suggestions?
beerindex said:
It's been a while since I've flashed anything; at least a year, though more likely two. Whatever I have now I'm guessing is a rom called stock(ish)v06, since that's what is listed in my bootloader. I guess the modem (baseband?) is NAE, and I'm still using a very old version of TWRP (2.6.3 according to my signature, haven't checked).
Obviously, the development that still exists for this device has moved well past me. But given how temperamental my device has been lately, I want to give flashing something newer a shot before buying a new device.
Trouble is, I'm not sure how to go about flashing roms and finding the right modem/firmware when everything I have is so out of date.
Suggestions?
Click to expand...
Click to collapse
Download latest fully stock firmware so you will have latest bootloader and modem from http://www.sammobile.com
which is Lollipop, then flash latest TWRP. If you like stock, there is a stock deodex ROM, there is the awesome Wicked X (heavily modified Lollipop stock), or if stock is not your thing you can get CM12(Lollipop) or CM13 official(Marshmallow)
Sent from my SCH-R220
mattzeller said:
Download latest fully stock firmware so you will have latest bootloader and modem from http://www.sammobile.com
which is Lollipop, then flash latest TWRP. If you like stock, there is a stock deodex ROM, there is the awesome Wicked X (heavily modified Lollipop stock), or if stock is not your thing you can get CM12(Lollipop) or CM13 official(Marshmallow)
Sent from my SCH-R220
Click to expand...
Click to collapse
I want to make sure I understand what you're telling me to do, so a few clarifying questions:
1) I am meant to be updating TWRP first, then using it to flash stock firmware to update the bootloader and modem, and then flashing a rom of my choosing?
2) Why is that method preferable to using Odin to update the modem?
3) If I flash this newer official firmware, am I going to lose root?
4) In flashing the newer firmware, won't my bootloader lock, making it not possible to flash a new rom?
beerindex said:
I want to make sure I understand what you're telling me to do, so a few clarifying questions:
1) I am meant to be updating TWRP first, then using it to flash stock firmware to update the bootloader and modem, and then flashing a rom of my choosing?
2) Why is that method preferable to using Odin to update the modem?
3) If I flash this newer official firmware, am I going to lose root?
4) In flashing the newer firmware, won't my bootloader lock, making it not possible to flash a new rom?
Click to expand...
Click to collapse
1) No, use Odin to flash full stock that you downloaded from sammobile.com, you cannot flash full stock from recovery.
2) Because some if not most newer ROMs require you to be on Lollipop bootloader.
3) Yes you will lose root, but this flashing of stock firmware is to update your bootloader and modem so you can flash the newest ROMs. The lack of root doesn't matter since you will be flashing latest TWRP via Odin and modified ROMs soon after.
4) if you have Sprint L720 the bootloader isn't locked. Check I'm 'about phone' to make sure you have an L720 and not another variant of S4
Make sure Samsung drivers are installed on your computer.
So your flashing steps go as follows:
1) Download everything you need first:
a) Full stock from http://www.sammobile.com to your computer
b) Latest TWRP tar file to your computer
c) The custom ROM of your choice (and correct gapps if AOSP or CM based) saved on external SD card on your phone since it will be flashed via recovery.
2) Turn phone off completely. I pull the battery then put it back in then boot directly to download mode: power + volume down. (Rebooting to download mode doesn't always allow a proper flashing)
3) Start Odin (uncheck reboot and reset time) and then plug phone into computer.
4) If COM lights up green in Odin click AP and select the file you downloaded from sammobile (it will be PDA instead of AP if you are using an older version of Odin) and click OK or start (I don't remember which it has)
5) If it flashes successfully pull the battery and then put it back in and turn the phone on normally. It will take a while to boot, like 15-20 minutes possibly. Flashing stock myself I have seen it say it was successful and it wasn't and the fix for me was to leave reset checked and let it do it's thing.
6) Once you have booted into your newly flashed stock OK3, do step 2 and 3 again, so you can flash TWRP.
7) When you go to flash TWRP in Odin uncheck reset time and DEFINITELY have reset unchecked (if Odin reboots your phone TWRP doesn't stick). Do step 4 again except this time select the TWRP tar file. Once it flashes successfully pull battery put it back in and boot directly to recovery (power + volume up) from there do a backup if you want, if not you can flash the custom ROM and gapps if necessary that you downloaded earlier.
Sent from my SCH-R220
mattzeller said:
1) No, use Odin to flash full stock that you downloaded from sammobile.com, you cannot flash full stock from recovery.
2) Because some if not most newer ROMs require you to be on Lollipop bootloader.
3) Yes you will lose root, but this flashing of stock firmware is to update your bootloader and modem so you can flash the newest ROMs. The lack of root doesn't matter since you will be flashing latest TWRP via Odin and modified ROMs soon after.
4) if you have Sprint L720 the bootloader isn't locked. Check I'm 'about phone' to make sure you have an L720 and not another variant of S4
Make sure Samsung drivers are installed on your computer.
So your flashing steps go as follows:
1) Download everything you need first:
a) Full stock from http://www.sammobile.com to your computer
b) Latest TWRP tar file to your computer
c) The custom ROM of your choice (and correct gapps if AOSP or CM based) saved on external SD card on your phone since it will be flashed via recovery.
2) Turn phone off completely. I pull the battery then put it back in then boot directly to download mode: power + volume down. (Rebooting to download mode doesn't always allow a proper flashing)
3) Start Odin (uncheck reboot and reset time) and then plug phone into computer.
4) If COM lights up green in Odin click AP and select the file you downloaded from sammobile (it will be PDA instead of AP if you are using an older version of Odin) and click OK or start (I don't remember which it has)
5) If it flashes successfully pull the battery and then put it back in and turn the phone on normally. It will take a while to boot, like 15-20 minutes possibly. Flashing stock myself I have seen it say it was successful and it wasn't and the fix for me was to leave reset checked and let it do it's thing.
6) Once you have booted into your newly flashed stock OK3, do step 2 and 3 again, so you can flash TWRP.
7) When you go to flash TWRP in Odin uncheck reset time and DEFINITELY have reset unchecked (if Odin reboots your phone TWRP doesn't stick). Do step 4 again except this time select the TWRP tar file. Once it flashes successfully pull battery put it back in and boot directly to recovery (power + volume up) from there do a backup if you want, if not you can flash the custom ROM and gapps if necessary that you downloaded earlier.
Sent from my SCH-R220
Click to expand...
Click to collapse
Thanks for the very detailed response. This totally clears up my questions. I'll charge my phone this evening and give it a shot in the morning when my battery is at 100%. :good:
beerindex said:
Thanks for the very detailed response. This totally clears up my questions. I'll charge my phone this evening and give it a shot in the morning when my battery is at 100%. :good:
Click to expand...
Click to collapse
Feel free to post back here or PM me if you have any more questions or problems, it wouldn't be the first time walking someone through the process via pm here or other methods
Sent from my SCH-R220

Might have Bricked S7 Edge SM-935FD. Need Help to recover

Hello guys
My phone is Galaxy S7 Edge Duos- SM935FD. I seem to have bricked the device.
Below are the actions I have performed.
1. Flashed TWRP using ODIN as described on https://www.the***********.com/root-samsung-galaxy-s7-edge/
2. Booted successfully into the OS. Found superuser app installed.
3. When I went to back to Flash ROM i erased multiple things such as internal storage/dalvik/cache/system after which device got stuck in bootloop. Showing NO OS.
4. I tried flasing Custom ROM Zip files through OTG. The process failed showing package corrupt and still stuck in bootloop.
I can enter recovery/download mode however cant seem to get the device booted. How can I get the device to work either Custom or stock ROM.
I will be going through some threads in the meantime, your guidance is very much appreciated.
Flash stock rom with Odin: This shouldnt be posted on Development Forum but rayher questions and Answers.
Find what your Stock Firmware for your phone is using Sammobile and flash stock then re do rooting and TWRP Process
zzThrain is right -- I wouldn't risk flashing custom ROMs at this stage, especially because many contain new bootloaders or other stuff that might make this even worse for you. Just pick up the relevant Samsung stock ROM file (from, for example, SamMobile) and see if it boots normally again. Once it does, re-do the process *after checking all MD5s of the files you used* -- I, too, have had it happen before that a download went corrupted and I flashed it. If all is well, get into Download Mode and let Odin rip.
rixon.d9 said:
Hello guys
My phone is Galaxy S7 Edge Duos- SM935FD. I seem to have bricked the device.
Below are the actions I have performed.
1. Flashed TWRP using ODIN as described on https://www.the***********.com/root-samsung-galaxy-s7-edge/
2. Booted successfully into the OS. Found superuser app installed.
3. When I went to back to Flash ROM i erased multiple things such as internal storage/dalvik/cache/system after which device got stuck in bootloop. Showing NO OS.
4. I tried flasing Custom ROM Zip files through OTG. The process failed showing package corrupt and still stuck in bootloop.
I can enter recovery/download mode however cant seem to get the device booted. How can I get the device to work either Custom or stock ROM.
I will be going through some threads in the meantime, your guidance is very much appreciated.
Click to expand...
Click to collapse
Go to recovery mode & transfer rom to phone using pc. wipe cache, delvikcache, data only. No need to wipe internal sd. Install rom & reboot.
if you phone goes to recovery or download mode, no need to worry. If it doesn't go to neither recovery nor download mode, them your phone might have probably bricked.
It's my pleasure to help you if you still facing this problem
zzThrain said:
Flash stock rom with Odin: This shouldnt be posted on Development Forum but rayher questions and Answers.
Find what your Stock Firmware for your phone is using Sammobile and flash stock then re do rooting and TWRP Process
Click to expand...
Click to collapse
Hi
I tried flashing stock rom from sammobile. I could find for SM-935FD hence downloaded SM-935F.
It got stuck at 90% showing System in ODIN.
From the ZIP file which is the file that needs to be flashed among below ? I tried AP.
AP_G935FXXU2DRB6_CL12365438_QB16944063_REV00_user_low_ship_meta.tar
BL_G935FXXU2DRB6_CL12365438_QB16944063_REV00_user_low_ship.tar
CP_G935FXXU2DRAG_CL648265_QB8691891_SIGNED.tar
CSC_OJV_G935FOJV2DRAG_CL12785220_QB16560277_REV00_user_low_ship.tar
HOME_CSC_OJV_G935FOJV2DRAG_CL12785220_QB16560277_REV00_user_low_ship.tar
Now when I try again it immediately shows FAIL. Am i Flashing the right stock rom ?
It Worked. Thanks to all who helped.
I wasn't running ODIN as Admin and also was using an slightly older version V3.10.7.

Samsung Galaxy Note 3 (SM-N900T) not booting into recovery

Hello there,
So I was trying to update the android version on my Note 3, because android 5.0 is outdated and vastly unsupported. I rooted my phone correctly, and flash TWRP onto it with Odin v3.10.6. But every time I try to boot into recovery, it simply goes into the Odin flash screen. I'm not able to access the recovery, and not able to install the rom (Lineage OS).
I have tried re-flashing the rom.
If there is any solution to this, please let me know.
Thank you.
Search your question answered many times .
Usual is you are flashing a TWRP for the wrong model .
Try an older TWRP and then upgrade TWRP .
There is no need to root the phone before flashing TWRP.
WARNING: there is always a risk of bricking a phone whenever flashing files with Odin. Be prepared to deal with a possibly bricked phone.
This method has worked for several of my Samsung phones:
Download Odin 3.07: https://forum.xda-developers.com/attachment.php?attachmentid=1168421
Download the tar version of TWRP 2.8.5.0 from here: https://twrp.me/samsung/samsunggalaxynote3qualcomm.html
Open Odin, do not check anything except for f reset time. Place TWRP in the PDA slot, flash TWRP. When you see the word "reset" in the status window, remove USB cable from phone, remove battery, replace battery, use buttons to boot into recovery.
The T-Mobile Note 3 forum is here: https://forum.xda-developers.com/note-3-tmobile
Thanks!
Thanks So Much!
I was able to bot into the recovery and install lineage OS!
:good::good:
Glad it worked for you
I need some help anyone. My hlte has been on lollipop for a long time. But decided to try some new roms, haven't flashed in a few years. Anyway I was using the newest twrp and tried flashing a few ROMs but they were unsuccessful. I know from experience that formatting the system deleted all personal data in twrp, so I flashed Philz touch recovery to clean my system for a clean rom install. After that I flashed the last zip file for hlte from the twrp website. And now recovery doesn't boot, but download mode will boot. But I think someone was in my settings before the flash, and disabled USB debugging possibly, because my computer will not detect it. Tried several cables, and other computers, but still will not recognize my note 3. Maybe it's in charging only mode? Because it charges. Is there any hope? Please help if you can. Thanks
TWRP usual is user is using wrong TWRP for the rom .
USB debugging is not needed .
Install Samsung USB drivers to PC . Flash stock rom via Odin .
USB contacts for charging are separate from the USB contacts for data.
It's possible that the USB port on the phone is defective.
root

Categories

Resources