So after having my phone being stuck in a boot loop (just restarted one day and has been in a boot loop since) , I figured the thing to do was to flash TWRP 2.8.7.0 (I had a solution that had rooted my phone without a custom recovery). After a successful flash, I go to recovery (up volume + Power) and it says recovery on the Samsung screen.
And then, it goes back into the boot loop.
Suggests as usual flashed wrong file for model .
See multiple identical posts .
But if it was a prexisting boot loop then go back to your other posts .
Sent from my SM-N930F using XDA-Developers Legacy app
JJEgan said:
Suggests as usual flashed wrong file for model .
See multiple identical posts .
But if it was a prexisting boot loop then go back to your other posts .
Sent from my SM-N930F using XDA-Developers Legacy app
Click to expand...
Click to collapse
Flashed twrp-2.6.3.1-hltetmo.tar successfully.
While its connected into my PC, it gets stuck at the T-mobile sign at full brightness.
When I unplug it, it goes back to a boot loop.
You want the TMobile forum not this one .
Sent from my SM-N930F using XDA-Developers Legacy app
Confirm the model # in download mode before flashing anything else.
Has there been solution for this one? I got n9005 and i can't get other than twrp 2.8.7.0 working, have tried different bootloaders but without luck. Only stock images what works are N9005XXUGNG1_N9005NEEGNG1_NEE(cant update to lollipop, stucks on bootloop) and N9005XXUGBOK6_N9005XEOGBOJ1_XEO. Also had luck with some unofficial cm13 rom.
I'am not that familiar with this samsung style of using odin instead of fastboot and adb so i'am litlle bit lost and just don't know what else anymore can i do to get working new twrp so i can install nougat.
What rom are you going to install.
Sent from my SM-N930F using XDA-Developers Legacy app
i tried official lineageos 14 hlte, it looks like installation goes fine with twrp 2.8.7.0 but phone wont boot. currently i have nordic bootloader and modem BL_N9005XXSGBQD1 and CP_N9005XXUGPQB1 and twrp 2.8.7.0 just tried to upgrade newer twrp from image file but same old bootloop again.
Could there be something wrong in filesystem? Is there some pit-file that i can try with my phone without risk of bricking it?
---------- Post added at 22:22 ---------- Previous post was at 22:06 ----------
btw, where does that charging icon come when phone is power off? my phone is just boot looping when powered off and i put charger on it.
Bootloop thats often wrong TWRP used .
Flash latest TWRP through TWRP or try Philz Recovery .
tried to install 3.1.1.0 from twrp 2.8.7.0. Install went fine without any errors but still not booting to recovery. found philz 6.13.0 after browsing, it also boots to recovery, installing lineageos went to boot loop just as it has done before.
I would start at step one.
Boot to download mode .
Note model and flash stock rom via Odin.
Sent from my SM-N930F using XDA-Developers Legacy app
i have tried both stock 4.4 and 5.0 roms, both boot and works fine but i still can't make twrp higher than 2.8.7.0 to work.
Okay. Now i have restored stock N9005XXUGBNL8, root and installed twrp app and used it to flash twrp 3.1.1.0 Flashing went fine as usually, phone boots as normally but still when i try to boot recovery phone reboots after 10-15sec. Also did try to flash multiple versions of twrp and no newer than 2.8.7.0 works.
Try one of the custom non ASOP roms see if that boots .
Sent from my SM-N930F using XDA-Developers Legacy app
Anyone found a solution?
I have the same problem,twrp above 2.8.7.0 dont work(bootloops) and new 7.1.2 roms do the same thing.
I manage to install an old 7.1.1 cyanogen 14 rom from 2016 december 10 minutes ago and it's working for now.
Next thing i tried to update the rom to a new build from january 2017 but i got bootloops...it's very strage.
Managed to install crdroid 7.1.2 from twrp 2.8.7.0, aokp unofficial also worked but still no luck with lineageos and newer twrp.
@stepi1 - Did you manage to find a solution to this problem? You are certainly not alone. I have exactly the same problem, and so do others! Nothing newer than TWRP 2.8.7 works on my N9005. Read the last few pages of this thread and you will see that I have the exact same issue. Seems there is either a bug or something different in the device tree for TWRP versions 3 and above which is not allowing the phones to boot these newer versions - https://forum.xda-developers.com/galaxy-note-3/development/recovery-twrp-3-2-1-1-t3746760
Chris
Sorry but no, i didn't find any solution used old twrp and crdroid for a while before giving up with that phone.
stepi1 said:
Sorry but no, i didn't find any solution used old twrp and crdroid for a while before giving up with that phone.
Click to expand...
Click to collapse
Thanks for confirming that.
Chris
fanilas said:
Anyone found a solution?
I have the same problem,twrp above 2.8.7.0 dont work(bootloops) and new 7.1.2 roms do the same thing.
I manage to install an old 7.1.1 cyanogen 14 rom from 2016 december 10 minutes ago and it's working for now.
Next thing i tried to update the rom to a new build from january 2017 but i got bootloops...it's very strage.
Click to expand...
Click to collapse
This is a known problem with some hlte devices, including mine. It has something to do with the way the newer TWRP versions (>v3) are built. There are devs working on it, but as of yet, the problem has not yet been resolved.
Chris
Related
Hi!
First I tell you how I recently messed up my LG G2 D802.
I hadn't had a custom rom for ages and now I wanted to have one (This wasn't the first time. I've done this a lot earlier). I had always had root access, but not custom recovery. So the first thing was to install one and I chose to download Rom Manager from Google Play, and then install ClockWorkMod. So, when I was installing the custom recovery I came up with a problem: something went wrong during the installation (I have no idea why). When I booted the device, white letters and numbers appeared on the top left of the screen, saying something like: "boot certification error" and numbers like "[780] [800]" and so on. The screen went black and the phone didn't load the OS. So I was shocked of course because I had never had such a problem.
So, desperate for trying everything to find the solution, I tried tens of ways to try to fix the problem. Finally I read about thing called SRKTool. So I used it and ended up having TWRP on my device, and no OS at all. I tried to flash CM12 and CM12.1 (downloaded from the official site) but nothing works out. TWRP says that flashing the ROM is succesful but when rebooting the system it doesn't load the OS but it comes back to TWRP Recovery mode - WHATEVER I DO. I can't enter the Download -mode at all. I tried hard reseting (Power + Vol - keys), but once again it boots to the TWRP. I can't understand why the TWRP fails to flash the ROM even though it's saying the process was successful. Or maybe this problem is much more internal - and permanent.
After tens of XDA developers' threads I'm writing this here because I'm in need of help. I want to bring my G2 to back in life. I'm out of ideas. Can you help me? I tried to flash the stock firmware but guess what happened? The installation failed, and the device booted back to TWRP. So all I'm able to do is to use the TWRP Recovery. I appreciate your help. Thank you.
(Ps. I'm sorry if I break the rules by writing a new thread. My problem just seems to be so unique that I couldn't find help anywhere.)
If you have access to twrp than you can do what ever is needed
what twrp version douy you have?
enabel MTP, so you can copy from PC
Spumpkin said:
Hi!
First I tell you how I recently messed up my LG G2 D802.
I hadn't had a custom rom for ages and now I wanted to have one (This wasn't the first time. I've done this a lot earlier). I had always had root access, but not custom recovery. So the first thing was to install one and I chose to download Rom Manager from Google Play, and then install ClockWorkMod. So, when I was installing the custom recovery I came up with a problem: something went wrong during the installation (I have no idea why). When I booted the device, white letters and numbers appeared on the top left of the screen, saying something like: "boot certification error" and numbers like "[780] [800]" and so on. The screen went black and the phone didn't load the OS. So I was shocked of course because I had never had such a problem.
So, desperate for trying everything to find the solution, I tried tens of ways to try to fix the problem. Finally I read about thing called SRKTool. So I used it and ended up having TWRP on my device, and no OS at all. I tried to flash CM12 and CM12.1 (downloaded from the official site) but nothing works out. TWRP says that flashing the ROM is succesful but when rebooting the system it doesn't load the OS but it comes back to TWRP Recovery mode - WHATEVER I DO. I can't enter the Download -mode at all. I tried hard reseting (Power + Vol - keys), but once again it boots to the TWRP. I can't understand why the TWRP fails to flash the ROM even though it's saying the process was successful. Or maybe this problem is much more internal - and permanent.
After tens of XDA developers' threads I'm writing this here because I'm in need of help. I want to bring my G2 to back in life. I'm out of ideas. Can you help me? I tried to flash the stock firmware but guess what happened? The installation failed, and the device booted back to TWRP. So all I'm able to do is to use the TWRP Recovery. I appreciate your help. Thank you.
(Ps. I'm sorry if I break the rules by writing a new thread. My problem just seems to be so unique that I couldn't find help anywhere.)
Click to expand...
Click to collapse
The solution is easy. Download the stock rom for your model and install it with otg cable. The reason cm12 is not booted is because you need jb bootloader or caf bootstacks.
Enviado desde mi LG-D802 mediante Tapatalk
renzo090513 said:
The solution is easy. Download the stock rom for your model and install it with otg cable. The reason cm12 is not booted is because you need jb bootloader or caf bootstacks.
Enviado desde mi LG-D802 mediante Tapatalk
Click to expand...
Click to collapse
cm11 => jb bootloader
cm12, cm12.1 and cm13 => kk bootloader
klemenSLO said:
If you have access to twrp than you can do what ever is needed
what twrp version douy you have?
enabel MTP, so you can copy from PC
Click to expand...
Click to collapse
The current version is 2.8.7.3. Should I try other versions?
Did you solve the issue? Or is it still not allowing you to get into your F/W?
staylecrate said:
Did you solve the issue? Or is it still not allowing you to get into your F/W?
Click to expand...
Click to collapse
Hi!
I tried to install TWRP version 2.6.6.3, but it fails to flash it so I'm stuck with the version 2.8.7.3. All I'm able to enter is just the recovery mode. I can't enter the download mode so I can't flash the stock firmware.
Currently I'm out of ideas. I can't flash any OS, the TWRP fails everytime and creates errors.
Try flash bumped kernel like lp dorimanx then flash bumped bootstak then lp rom like cloudy or stock. Or google this: lg g2 unbrickable now xda ...that work for me
I may be doing something stupid, but I've tried various options...
I had an original 5.1.1 build that I let OTA to 6.0. Everything was working fine. I wanted to root, so I installed TWRP... and then the machine wouldn't reboot; it stuck at the "powered by Android" screen and never went into the standard animation screens. I could reboot into TWRP recovery easily enough and using that I could see the filesystem data, but the OS wouldn't boot.
So I reflashed back to 5.1.1 (using http://www.andromods.com/download-files/xt1575-stock-firmware-moto-x-2015-pure-edition.html ), let that OTA to 6.0, installed TWRP... same result.
Third attempt; started at 5.1.1 then installed TWRP (which worked) and then did OTA to 6.0... but this went into a reboot loop.
(Of course during all this I've lost my configs, but I can rebuild that)
Has anyone been able to install TWRP onto an X-Pure 2015 that's running 6.0 ?
What TWRP version are you installing? Make sure it's 2.8.7.1 https://dl.twrp.me/clark/
Sent from my XT1575 using Tapatalk
Sorry, yes, I should have mentioned that; twrp-2.8.7.1-clark.img
Did you install TWRP as read only? I did this and now system recovery is overwriting TWRP and I have no idea how to get out of it.
I had the same problem a couple days ago and posted about it in the 'Android 6.0 Update rolling out! Pure Edition' thread:
"I keep running into a problem after doing the MM update when I flash TWRP (either 2.8.7.0 or 2.8.7.1) where it won't boot into system, just sits there where the animation part should start. Booted/rebooted fine a few times after finishing the MM update, even after flashing the unlocked bootloader logo fix, but as soon as I flash recovery it won't boot system. "
Tried it several times with both TWRP 2.8.7.0 and 2.8.7.1 with no success. Also tried sideloading the OTA per the manual steps in this thread but still couldn't boot to system. Only by already having TWRP installed on 5.1.1 am I able to flash a custom 6.0 ROM successfully. Haven't seen a really clear statement yet that someone has flashed TWRP on fully stock MM with no problem..
EVR_PR said:
Did you install TWRP as read only? I did this and now system recovery is overwriting TWRP and I have no idea how to get out of it.
Click to expand...
Click to collapse
First time I let /system be read-write and second time I let /system be RO. However this likely isn't related to recovery overwriting TWRP; it's documented that on first boot the OS may rewrite the recovery data meaning you'd need to install TWRP again.
Dahenjo said:
I had the same problem a couple days ago and posted about it in the 'Android 6.0 Update rolling out! Pure Edition' thread
...
Haven't seen a really clear statement yet that someone has flashed TWRP on fully stock MM with no problem..
Click to expand...
Click to collapse
Thanks; at least I know it's not me being stupid then (or if I am, then I'm not alone ).
sweh said:
First time I let /system be read-write and second time I let /system be RO. However this likely isn't related to recovery overwriting TWRP; it's documented that on first boot the OS may rewrite the recovery data meaning you'd need to install TWRP again.
Click to expand...
Click to collapse
I have flashed TWRP twice and even rebooted to recovery from recovery and system recovery still overwrites TWRP after booting to system.
Only way I can access TWRP is either flashing it or booting into from the fastboot folder using the fastboot boot command.
Doesn't matter what I do, the option for changing TWRP from read-write to read only doesn't show up anymore.
sweh said:
Thanks; at least I know it's not me being stupid then (or if I am, then I'm not alone ).
Click to expand...
Click to collapse
Well, at age 65 I do put my socks on backwards sometimes..... :silly:
Read on a fairly-detailed post that using adb to flash recovery and rebooting into it should actually work fine!
Could anyone confirm? Is it even possible?
P.S. I'm on XT1572 Indian stock 6.0, and very eager for twrp
I had the exact same problem. I used adb. Stuck on loading screen and then suddenly black. Not able to boot the phone. I'd like to make a nandroid and after that I'd like to use systemless root. If I'm correct, I'll still receive ota's while using systemless root.
Same for me. Returned to stock EU 5.1.1, got update, installed it. Later unlocked bootloader and installed latest TWRP. And now I am stuck on booting up image.
So stock Marshmallow cant be used with TWRP?
BooBzi said:
Same for me. Returned to stock EU 5.1.1, got update, installed it. Later unlocked bootloader and installed latest TWRP. And now I am stuck on booting up image.
So stock Marshmallow cant be used with TWRP?
Click to expand...
Click to collapse
That seems to be the case since I have yet to hear of anyone freshly setting up TWRP for clark/MXPE on purely stock MM without it failing to boot to system afterwards. If you already have TWRP on 5.1.1 you can install a custom MM ROM and then TWRP works normally (ie boots to system), but so far that's the only way I'm aware of to get it functional on MM.
I see you started another thread on this, which may help it get noticed, but maybe also post in the TWRP thread. I posted there on this issue over a week ago but have had zero response from OP, but if others keep doing so maybe that will help.
IMVHO, TWRP for MXPE isn't being supported well - this problem, the version being incorrect for several weeks causing confusion w/dozens of unnecessary posts (this alone could likely be fixed in 2 minutes), as well as the 'SD as internal storage' issue(s) which may be more involved but are still the type of thing those maintaining it are supposed to address. Even some acknowledgement that the issues are recognized and being worked on would be nice, but thus far not even that.
Dahenjo said:
That seems to be the case since I have yet to hear of anyone freshly setting up TWRP for clark/MXPE on purely stock MM without it failing to boot to system afterwards. If you already have TWRP on 5.1.1 you can install a custom MM ROM and then TWRP works normally (ie boots to system), but so far that's the only way I'm aware of to get it functional on MM.
I see you started another thread on this, which may help it get noticed, but maybe also post in the TWRP thread. I posted there on this issue over a week ago but have had zero response from OP, but if others keep doing so maybe that will help.
IMVHO, TWRP for MXPE isn't being supported well - this problem, the version being incorrect for several weeks causing confusion w/dozens of unnecessary posts (this alone could likely be fixed in 2 minutes), as well as the 'SD as internal storage' issue(s) which may be more involved but are still the type of thing those maintaining it are supposed to address. Even some acknowledgement that the issues are recognized and being worked on would be nice, but thus far not even that.
Click to expand...
Click to collapse
Thanks for reply, I did listen to you and post on TWRP thread.
Dahenjo said:
That seems to be the case since I have yet to hear of anyone freshly setting up TWRP for clark/MXPE on purely stock MM without it failing to boot to system afterwards. If you already have TWRP on 5.1.1 you can install a custom MM ROM and then TWRP works normally (ie boots to system), but so far that's the only way I'm aware of to get it functional on MM.
I see you started another thread on this, which may help it get noticed, but maybe also post in the TWRP thread. I posted there on this issue over a week ago but have had zero response from OP, but if others keep doing so maybe that will help.
IMVHO, TWRP for MXPE isn't being supported well - this problem, the version being incorrect for several weeks causing confusion w/dozens of unnecessary posts (this alone could likely be fixed in 2 minutes), as well as the 'SD as internal storage' issue(s) which may be more involved but are still the type of thing those maintaining it are supposed to address. Even some acknowledgement that the issues are recognized and being worked on would be nice, but thus far not even that.
Click to expand...
Click to collapse
I was on pure stock mm and sideloaded twrp without any issues. I use the twrp app (requires root) to reboot into recovery without any problems.
ccic2491 said:
I was on pure stock mm and sideloaded twrp without any issues. I use the twrp app (requires root) to reboot into recovery without any problems.
Click to expand...
Click to collapse
Hello, is it possible to get step by step tutorial?
Later will try on Style with stock MM.
Thanks!
ccic2491 said:
I was on pure stock mm and sideloaded twrp without any issues. I use the twrp app (requires root) to reboot into recovery without any problems.
Click to expand...
Click to collapse
Did you not use the Fastboot Install Method on the TWRP site? We are unable to reboot back into system after using this on stock MM, which always worked fine on stock LP. If you used a different method that worked could you please share what that was?
I am using twrp 2.8.7.1 on my Moto X Style XT1572 Asia retail without any trouble for past two weeks.
I normally flashed it using the fastboot and never ran into trouble.
gulshanstrider said:
I am using twrp 2.8.7.1 on my Moto X Style XT1572 Asia retail without any trouble for past two weeks.
I normally flashed it using the fastboot and never ran into trouble.
Click to expand...
Click to collapse
Just to confirm - when you flashed TWRP you were completely stock after installing the 6.0 OTA (not still on 5.1.1 before taking the OTA), correct?
Dahenjo said:
Just to confirm - when you flashed TWRP you were completely stock after installing the 6.0 OTA (not still on 5.1.1 before taking the OTA), correct?
Click to expand...
Click to collapse
Here is what I did:-
1) I was in Stock 5.1.1 (had unlocked bootloader)
2) I took the OTA.
3) Flashed the twrp 2.8.7.1 using fastboot
So yes I was completely stock 6.0 when I flashed the TWRP for MM
Hello all, maybe you can help...
After finally getting a stable TWRP from @ashyx that finally booted, I attempted to flash roms and Gapps on my SM-T350. This should be simple enough, but every rom I flash either doesn't boot or boots with only sound and no display!!!!
Yes, I'm running TWRP 3.2.3-1 courtesy of @ashyx
Yes, I've wiped several times.... wiped internal storage sometimes too
I'm running the latest official 7.1.1 release from Samsung.... I cannot get anything else to boot!
Please offer some support, I need some help y'all!
-------------------------------------------
EDIT: THIS ISSUE HAS BEEN SOLVED
Check the latest comments for more info
I'm having the exact same issues, never experienced this before with any device. Hope someone can help or we can find a fix.
Same - SM-T350
I was able to install Jazzrom but none of the other SM-T350 roms. I can hear sound when I press the power button, but no display when trying Lineage 15 or 16. Jazzrom runs slow, that is why I'm not sticking with it. I have tried several versions of TWRP as well. 3.2.3-1 seems to be the only one that got Jazzrom installed. Thanks in advance for your time. Same issue with crDroid rom ver 5.2
my suggestion would be to use odin to reflash to stock, and reinstall twrp. i've never encountered that specific issue with the device
elginsk8r said:
my suggestion would be to use odin to reflash to stock, and reinstall twrp. i've never encountered that specific issue with the device
Click to expand...
Click to collapse
Tried that.... no luck. Everyone else who reported a problem is having the same exact issue as me.... it's strange.
Here is what I posted in the crDroid area:
I might be posting a little soon but finally on the road to success after only getting a blank screen after boot. Downgraded the stock 7.1.1 to marshmallow T350XXU1BPK1 using the BL, AP and CSC files in Odin. Used TWRP TWRP-3.2.1-lineage-15.1_j1_20180418_gt58wifi. Versions of TWRP that worked before didn't work after the downgrade. Installed April 9th crDroid ROM and gapps pico. I am now at the sign in screen.
heymanster said:
Here is what I posted in the crDroid area:
I might be posting a little soon but finally on the road to success after only getting a blank screen after boot. Downgraded the stock 7.1.1 to marshmallow T350XXU1BPK1 using the BL, AP and CSC files in Odin. Used TWRP TWRP-3.2.1-lineage-15.1_j1_20180418_gt58wifi. Versions of TWRP that worked before didn't work after the downgrade. Installed April 9th crDroid ROM and gapps pico. I am now at the sign in screen.
Click to expand...
Click to collapse
Hmm..... I will check this out. Thanks for the lead! I will let u know what happens
heymanster said:
Here is what I posted in the crDroid area:
I might be posting a little soon but finally on the road to success after only getting a blank screen after boot. Downgraded the stock 7.1.1 to marshmallow T350XXU1BPK1 using the BL, AP and CSC files in Odin. Used TWRP TWRP-3.2.1-lineage-15.1_j1_20180418_gt58wifi. Versions of TWRP that worked before didn't work after the downgrade. Installed April 9th crDroid ROM and gapps pico. I am now at the sign in screen.
Click to expand...
Click to collapse
This solved it!!! Finally!!! For clarification, anyone who is having this issue must downgrade to stock Marshamallow (BPK1) and flash twrp 3.2.1. It must have something to do with the newer oreo bootloader, so just downgrade and Viola! Success! :good:
Hello!
I try to install the latest version of lineage on my note 3 and followed the tutorial on the lineage website.
However, I got some issues getting the latest version of TWRP on the phone. Beside the method via heimdall I've also tried Odin and update via old TWRP install and sd card. I also installed the stock rom again and retried flashing but nothing worked.
Basically I can flash old TWRP and get into the TWRP recovery mode - twrp-2.8.7.0-hlte-4.4.img works perfectly fine. But when I try twrp-3.4.0-0-hlte or trwp-3x though the flash is confirmed I cannot get into recoverymode and will end up in a bootloop.
I've tried twrp-3.2.2-0-hlte, twrp-3.1.1-0-hlte, twrp-3.4.0-0-hlte all with same result (bootloop). Only version that works is twrp-2.8.7.0-hlte-4.4
Any idea where this issue may come from?
Any other recovery tool I could use to get lineage on my note3?
update:
hmm why would the recovery system care for the os?
fwiw I updated the firmware to the latest official version (android 5.0) and then retried.
same result: with TWRP 2.8.7.0 I can flash and get into recovery mode. TWRP 3.x I can flash and they will bootloop
TWRP 2.8.7.0 I get the message
"Recovery booting...
recovery is not seandroid enforcing
Set warranty bit: recovery"
=> TWRP recovery mode
TWRP 3.x
"Recovery booting...
Set warranty bit: recovery"
=> bootloop
What model ??
Known issue for some re TWRP 3 failing , well posted on here .
Read answers to your other posts .
JJEgan said:
What model ??
Known issue for some re TWRP 3 failing , well posted on here .
Read answers to your other posts .
Click to expand...
Click to collapse
sm n9005
I found a possible reason in the TWRP thread: LCD and Digitizer may have been replaced and hardware change could case this. I am not sure though
[/COLOR]
ashyx said:
If you've got one of those finicky devices which seems to have slightly different hardware then you may find this build works:
https://androidfilehost.com/?fid=6006931924117938350
However be aware it's also likely you will not be able to boot any recent android version on your device if this is the case.
Click to expand...
Click to collapse
this worked for me finally! And it looks like linageOS can be installed too... I will update
-------
lineageOS and google apps could be installed without issues. I was stuck on the bootsequence quite a bit but now I am in the OS
smuffiy said:
sm n9005
I found a possible reason in the TWRP thread: LCD and Digitizer may have been replaced and hardware change could case this. I am not sure though
[/COLOR]
this worked for me finally! And it looks like linageOS can be installed too... I will update
-------
lineageOS and google apps could be installed without issues. I was stuck on the bootsequence quite a bit but now I am in the OS
Click to expand...
Click to collapse
Hi smuffy,
May I know what lineage version are u flashing?
I'm facing same problem also, can you please guide me how to solve this issue?
Thanks
I do not remember exactly but I think the latest by that time.
However I was unable to make lineage detect my SIM card after that. I tried some other workarounds but it never worked and I finally gave up.
smuffiy said:
I do not remember exactly but I think the latest by that time.
However I was unable to make lineage detect my SIM card after that. I tried some other workarounds but it never worked and I finally gave up.
Click to expand...
Click to collapse
My phone cannot flash lineageOS 17.1 version and above.
My phone is new, just rooted, tried custom rom android 9 worked!
LineageOS 16 - ok
LineageOS 18.1 - x (After flash, cannot see any file inside the phone memory)
Havoc 2.9 - ok
Havoc 3.7 - x (After flash, cannot see any file inside the phone memory)
Are you facing same problem also?
*Remarks*
My phone keep in bootloop, cannot initialize...
Thanks.
Which TWRP are you using? I had the custom "twrp 3311 ashyx".
I just checked, 17.1+ also does not work for me. Just as you stuck in bootloop.
With this (ashyx) https://www.alebalweb.com/note3/note3-sm-n9005--twrp--work-on-my-note3.zip los 17 work until 02 jan 2021... Then bootloop...
I can't update after 02 jan 2021 (Galaxy Note 3 SM-N9005)
I can't update after 02 jan 2021 on my Galaxy Note 3 SM-N9005, all work good but when the phone restart... an infinite reboot... I make a video to show what happen If I reinstall the 02 jan 2021 update the phone work perfectly... Ideas?
forum.xda-developers.com
I've recently received a k53a48 phone that had system branded by vendor with many trash apps.
I wanted to quickly change the ROM to something else.
I didn't do anything like that in a while, so I tried to follow the instructions closely.
I've managed to flash TWRP 3.4.0-0 via fastboot.
The big mistake I made was than wiping the phone without backing it up first.
I've tried flashing multiple different ROMs from this page that were either marked as karatep or k53.
Each time it failes with e1001 and Error 7. Currently I don't have any installed system and did not find any I would be able to install succesfuly.
Do I do something wrong? What else should I try?
I've seen some instructions on how to override Error 7 but first wanted to make sure if that's something I should do. After all, it might mean something important and overriding it might further damage my phone.
Quite similar problem in mine K33a48 - I managed to install TWRP for Karate,
I'm unable to install any ROM - TWRP shows success [1] but after reboot phone goes directly to fasboot mode..
Did you install TWRP as recovery or boot image?
Reinstall TWRP as recovery and you should be able to install applicable ROM.
Are you sure that TWRP 3.4. is for karatep k53a48??
Sent from my [device_name] using XDA-Developers Legacy app