Database Users

[HELP] Custom Recovery Flashing Failed + Few Other Questions [Noob-User]

Dear XDA Developer Community,
So before I get to the main problem I'd like to let you know that I've been reading a lot of Articles/Threads on Rooting, Flashing Custom Recovery and Custom ROM. Also this is my very first Android phone so please do excuse me, I'm a complete noob at Android, FOR NOW!
My Android Phone Detail ( In case it helps anyone out):
Model Number: SM-N9005 - International Qualcomm Version.
Android Version: 4.4.2 - It originally came with 4.3 Jelly Bean, however I updated it and now regret this decision. However I'm well aware that a downgrade is not possible.
Kernel Version: 3.4.0 - 636608. [email protected]#1
AP: N9005XXUENB7
CP: N9005XXUENB1
CSC: N90050XAENB1
{
"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"
}
Need Help With:
Do I have to be rooted in order to flash custom recovery? I've tried to search for an answer but didn't find anything specific. I do know that I need root access in order to use TWRP Manager. However what about if I wanted to flash TWRP recovery via Odin?
So here's the trouble. I do not have root access nor custom ROM. I tried to flash TWRP using this tutorial, http://true-android.blogspot.co.uk/2014/03/twrp-2700-touch-recovery-for-samsung_8952.html. Go down to the header that says "How To Install TWRP 2.7.0.2 Touch Recovery on Samsung Galaxy Note 3 SM-N9005 Via Odin".
Using that method I tried to flash TRWP. I started Odin, added the img.tar to AP and started the flashing sequence. Everything went well and the box went green meaning it was applied. Getting excited I enter recovery mode only to be disappointed. The recovery was still an stock recovery (or whatever you call it). However it was the first time I went into recovery and was paranoid. When I select "reboot system now" it says "error". Does that mean I messed something up? The images below show what I mean.
I boot into recovery mode:
However it says "No command" with exclamation mark! Is that a bad thing?:
When I select "reboot system now" it shows me this, however it still reboots:
So does this mean something is wrong with the recovery or is it fine? Because I'm completely scared right now and don't want to ruin my brand new Note 3.
Additional Q:
Q1) I think my boot-loader is locked. Since I read Chainfire say that the KK version has locked boot-loaders now. Meaning I cannot flash anything. Is that why the TWRP flash failed? Not really sure. Also you guys know my phone details, could anyone lead my to a thread or anything so I could unlock the boot-loader. I've also read somewhere on XDA that the KitKat bootloader has "install-recovery". Is this true? And is there a way around this currently? Since I really wanted to install TWRP recovery badly.
Q2) Do I need to have ROOT access in order to flash custom recovery and custom ROM? Or could I do it without ROOT access since I've heard some custom ROM's come pre-rooted. I'm thinking to flash BobCat ROM.
Q3) If you look at my device details what method should I use to ROOT my device? "Root de la Vega" seems a bit complicated for me. Since I've only used CMD but don't know about Terminal (though I've heard of it many times). I could use "CF-Auto-Root by Chainfire", however is this safe to use? I do know if I use Chainfire's method my knox counter will trip.
Lastly thanks a lot for the help. I know I'm complete beginner at this and may annoy some users with my questions, so sorry about that. But I had to, because I'm very cautious. I don't go ahead with anything until I know the details and reading a lot on the topic.​

I was also on NB7 a few weeks ago, turn the device off, do the button combo for download mode, and flash this with odin - http://www.techerrata.com/file/twrp2/hlte/openrecovery-twrp-2.7.0.3-hlte-4.4.img.tar
then wait for it to reboot the phone after flashing, and try to go to recovery it should be fine now.
and to root the device, copy this onto the phone http://download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zip and flash that in TWRP and this will add supersu to the system partition of the stock rom. no need for cf-auto-root after this.
I hope this helps!
EDIT:
The first picture shows that knox is 0x0, after flashing twrp like you just did that will be 0x1 now, but this recovery i posted should be fine
also what version of odin are you using? i prefer 1.85 and have never had problems with it.
if you have kies installed or running on your pc kill the processes before starting odin.

celderic said:
I was also on NB7 a few weeks ago, turn the device off, do the button combo for download mode, and flash this with odin - http://www.techerrata.com/file/twrp2/hlte/openrecovery-twrp-2.7.0.3-hlte-4.4.img.tar
then wait for it to reboot the phone after flashing, and try to go to recovery it should be fine now.
and to root the device, copy this onto the phone http://download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zip and flash that in TWRP and this will add supersu to the system partition of the stock rom. no need for cf-auto-root after this.
I hope this helps!
EDIT:
The first picture shows that knox is 0x0, after flashing twrp like you just did that will be 0x1 now, but this recovery i posted should be fine
also what version of odin are you using? i prefer 1.85 and have never had problems with it.
if you have kies installed or running on your pc kill the processes before starting odin.
Click to expand...
Click to collapse
Hi, firstly could you please not quote the while OP because its massive and when you quote it, it ruins the thread. If you could edit that out it would be great, thanks.
Secondly, thanks a lot for the reply. I will try this method soon.
You see I tried to flash TWRP but it didn't work. But now my Current Binary & System Status is "Custom". So I'm shocked to see that, lol. But I'll try your method when I get time .
Also it says "Qualcomm Secureboot: Enable". And I've heard that I cannot flash anything if the bootloader is locked.

jaydeeph said:
Hi, firstly could you please not quote the while OP because its massive and when you quote it, it ruins the thread. If you could edit that out it would be great, thanks.
Secondly, thanks a lot for the reply. I will try this method soon.
You see I tried to flash TWRP but it didn't work. But now my Current Binary & System Status is "Custom". So I'm shocked to see that, lol. But I'll try your method when I get time .
Also it says "Qualcomm Secureboot: Enable". And I've heard that I cannot flash anything if the bootloader is locked.
Click to expand...
Click to collapse
mine also the same Qualcomm Secureboot: Enable , but still can flash recovery. no problem flashing other rom and rooting.

fadhil3536 said:
mine also the same Qualcomm Secureboot: Enable , but still can flash recovery. no problem flashing other rom and rooting.
Click to expand...
Click to collapse
Okay thanks for letting me know. Now I'll try the methods , wish me luck. Hehe.

If you want root flash cf-autoroot from original developement thread. Takes around 10 secs...
Also when flashing a recovery, untick reboot.
Its better to flash, wait for success then boot into recovery as KK has a little script that reverts back to Samsung recovery on 1st boot...
f you boot to recovery after a successful flash, when you then select reboot in the custom recovery it will ask if you wish to disable this little bugger... No more problems with stock recovery re-asserting itself over what you want then...

celderic said:
I was also on NB7 a few weeks ago, turn the device off, do the button combo for download mode, and flash this with odin - http://www.techerrata.com/file/twrp2/hlte/openrecovery-twrp-2.7.0.3-hlte-4.4.img.tar
then wait for it to reboot the phone after flashing, and try to go to recovery it should be fine now.
and to root the device, copy this onto the phone http://download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zip and flash that in TWRP and this will add supersu to the system partition of the stock rom. no need for cf-auto-root after this.
I hope this helps!
EDIT:
The first picture shows that knox is 0x0, after flashing twrp like you just did that will be 0x1 now, but this recovery i posted should be fine
also what version of odin are you using? i prefer 1.85 and have never had problems with it.
if you have kies installed or running on your pc kill the processes before starting odin.
Click to expand...
Click to collapse
fadhil3536 said:
mine also the same Qualcomm Secureboot: Enable , but still can flash recovery. no problem flashing other rom and rooting.
Click to expand...
Click to collapse
ultramag69 said:
If you want root flash cf-autoroot from original developement thread. Takes around 10 secs...
Also when flashing a recovery, untick reboot.
Its better to flash, wait for success then boot into recovery as KK has a little script that reverts back to Samsung recovery on 1st boot...
f you boot to recovery after a successful flash, when you then select reboot in the custom recovery it will ask if you wish to disable this little bugger... No more problems with stock recovery re-asserting itself over what you want then...
Click to expand...
Click to collapse
@celderic &@fadhil3536 thanks for those tips guys but it didn't work, however you're not wrong. Its the script in KitKat as ultramag mentioned. Really appreciate the help guys :good:.
Just as I suspected, what @ultramag said, seems to be the problem here. I did read that somewhere but no one mentioned a way around it.
Thanks a lot, I will try this and let you know of the outcome. In the meanwhile could you help me out here since you're a senior member.
Q1) Does unlocked or locked bootloader matter when ROOTING/Flashing Custom Recovery/Flashing ROM?
I forgot the other questions and some are already answered by me reading the forum threads. If I do remember any, is it okay if I PM you?
Thanks a lot, once again.

jaydeeph said:
@celderic &@fadhil3536 thanks for those tips guys but it didn't work, however you're not wrong. Its the script in KitKat as ultramag mentioned. Really appreciate the help guys :good:.
Just as I suspected, what @ultramag said, seems to be the problem here. I did read that somewhere but no one mentioned a way around it.
Thanks a lot, I will try this and let you know of the outcome. In the meanwhile could you help me out here since you're a senior member.
Q1) Does unlocked or locked bootloader matter when ROOTING/Flashing Custom Recovery/Flashing ROM?
I forgot the other questions and some are already answered by me reading the forum threads. If I do remember any, is it okay if I PM you?
Thanks a lot, once again.
Click to expand...
Click to collapse
You untick reboot in Odin. This will leave your phone in download mode after the flash. When it says "success" you then turn off phone and boot to recovery.
Depends what you mean wigh locked or unlocked bootloaders.
If youre talking about the n9005 bootloader that wont let you downgrade, I have that. Wont matter. If you mean like the US carriers that lock & do bad stuff you might need to check out that particular forum.
Im a shift worker so getting back can be spotty but I have no problem with you pming me.

ultramag69 said:
You untick reboot in Odin. This will leave your phone in download mode after the flash. When it says "success" you then turn off phone and boot to recovery.
Depends what you mean wigh locked or unlocked bootloaders.
If youre talking about the n9005 bootloader that wont let you downgrade, I have that. Wont matter. If you mean like the US carriers that lock & do bad stuff you might need to check out that particular forum.
Im a shift worker so getting back can be spotty but I have no problem with you pming me.
Click to expand...
Click to collapse
Woop, I did it last night bro & then went to sleep straight away. But yeah I did exactly what you told me in the first post you made and it worked like a charm! Once flashed I shut it down and boot it up into recovery mode and TWRP was there . It didn't ask me to disable the KitKat script thingy but I think it automatically did that because I booted into recovery 3 more times just to triple check it, I'm very cautious.
And yes I have the SM-N9005 International Version, since I'm in the right forum . Ohh okay I guess I'll just have to wait for someone to figure out how to downgrade . But will it be okay if I flash a Custom ROM without ROOT? Or would I need to ROOT then flash Custom ROM? Or is it the opposite way around? Unless the Custom ROM comes with ROOT then I know I can just flash the ROM.
Thanks bro, I'll PM you if anything is urgent; and take all the time in the world dude, I know people always get busy .

jaydeeph said:
Woop, I did it last night bro & then went to sleep straight away. But yeah I did exactly what you told me in the first post you made and it worked like a charm! Once flashed I shut it down and boot it up into recovery mode and TWRP was there . It didn't ask me to disable the KitKat script thingy but I think it automatically did that because I booted into recovery 3 more times just to triple check it, I'm very cautious.
And yes I have the SM-N9005 International Version, since I'm in the right forum . Ohh okay I guess I'll just have to wait for someone to figure out how to downgrade . But will it be okay if I flash a Custom ROM without ROOT? Or would I need to ROOT then flash Custom ROM? Or is it the opposite way around? Unless the Custom ROM comes with ROOT then I know I can just flash the ROM.
Thanks bro, I'll PM you if anything is urgent; and take all the time in the world dude, I know people always get busy .
Click to expand...
Click to collapse
I tend to root with new recovery, cuts down on problems later.... Is the fact you have no root connected to the fact it wasn't rooted or because the rom wasn't rooted right?
I use cf-autoroot, about 10 secs to flash and that includes opening odin, selecting file, putting phone in download mode and hitting start.... Heck, in the time it took me to type this I could've rooted 2 phones....:silly:

ultramag69 said:
I tend to root with new recovery, cuts down on problems later.... Is the fact you have no root connected to the fact it wasn't rooted or because the rom wasn't rooted right?
I use cf-autoroot, about 10 secs to flash and that includes opening odin, selecting file, putting phone in download mode and hitting start.... Heck, in the time it took me to type this I could've rooted 2 phones....:silly:
Click to expand...
Click to collapse
I did not get anything you said here: "Is the fact you have no root connected to the fact it wasn't rooted or because the rom wasn't rooted right?"
Haha, But I think I understand after reading 10 times xD. I don't have ROOT nor any Custom ROM. But wanted to know do I need to have ROOT in order to flash Custom ROM?
Also in the recovery mode, TWRP asks me to install SuperSU or something like that. Should I allow it? Would it be safe?

jaydeeph said:
I did not get anything you said here: "Is the fact you have no root connected to the fact it wasn't rooted or because the rom wasn't rooted right?"
Haha, But I think I understand after reading 10 times xD. I don't have ROOT nor any Custom ROM. But wanted to know do I need to have ROOT in order to flash Custom ROM?
Also in the recovery mode, TWRP asks me to install SuperSU or something like that. Should I allow it? Would it be safe?
Click to expand...
Click to collapse
Sorry long day with little sleep. If TWRP is asking to install Super SU then it will root for you, let it...

ultramag69 said:
Sorry long day with little sleep. If TWRP is asking to install Super SU then it will root for you, let it...
Click to expand...
Click to collapse
Okay thanks bro. And hey, don't need to say sorry . Make sure you rest :good:.

jaydeeph said:
Okay thanks bro. And hey, don't need to say sorry . Make sure you rest :good:.
Click to expand...
Click to collapse
Mate, I didn't even get any of the Easter holidays off and am working ANZAC day... Good pay, lousy hours and no social life....:silly:

ultramag69 said:
Mate, I didn't even get any of the Easter holidays off and am working ANZAC day... Good pay, lousy hours and no social life....:silly:
Click to expand...
Click to collapse
Wow, that sucks. I'm sure you have rights for Easter Holidays though, and bank holidays?

[GUIDE] UPDATED Lenovo Vibe P1 A42/C72/C58 Root

This thread is for Lenovo Vibe P1 and NOT for P1m
Code:
*I am not responsible for bricked devices, dead SD cards, thermonuclear war.
First of all im just a user, who want to help others, i am NOT the maker/creator of these files.
Root and first TWRP recovery:
This method will work if your phone is on latest rom / S288 / maybe its work on older rom, BUT i dont test it.
1. You need download Lenovo driver and install it.
2. Get the QFIL/QPST and install it too.
3. Download the P1a42_S288... zip and unzip to your desktop.
4.Go in your Developer options /Tap 7 times build number/ and allow OEM unlock and USB debugging.
{
"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"
}
Click to expand...
Click to collapse
5. You need download Supersu and put it in your INTERNAL storage root folder.
6.Shut down your device / phone/, press Volume + and connect to the pc via USB
7. Your windows give sounds for a new device, u go in Device manager /and in QFIL too/ and u will see the qualcomm hs-usb qdloader 9008.
Click to expand...
Click to collapse
8.Open your QFIL and press the first BROWSE and choose prog_emmc_firehose_8936.mbn from the unzipped folder.
Click to expand...
Click to collapse
9. Choose Load xml and choose rawprogram0_aboot+twpr and then patch0.
Click to expand...
Click to collapse
10. Press the blue Download button and it will start.
Click to expand...
Click to collapse
11. That is not all!!! Your phone will reboot BUT u need to press 3/ i mean volume + , - and power / button for 10 second if it start reboot, or your phone will reboot in Android, and u will get again stock recovery.
12.A If you havent TWRP u need start it again from step 6.
12.B If you have TWRP swipe the trigger to right and confirm the first ask.
13. Go to install and search your Supersu and flash it.
14. Wipe your dalvick cache and normal cache and reboot your phone.
15. The first reboot will take a long time / 10 minute was for me / dont restart, let it work.
16. If you do everything good, have now a ROOTED phone.
P1C72/C58 root method if u are on vibeUI rom.
You have to do the same like the top one, but u have to download this one
And use rawprogram-flashj_rec instead of rawprogram0_aboot+twpr
If it work for you, please hit the Thanks button or send me a beer via paypal.

Very good English not bad at all, anyway when you do the first part does that mean TWRP is only temporary ? and the second part makes TWRP permanent what is the third part for ?

karlzberg said:
Very good English not bad at all, anyway when you do the first part does that mean TWRP is only temporary ? and the second part makes TWRP permanent what is the third part for ?
Click to expand...
Click to collapse
1. make a permanent twrp, u can root your phone with this twrp / and supersu/ for use stock rooted rom.
2. and 3. is for custom roms, with the 1. twrp u cant flash custom roms, thats why u need this twrps, one is a chinese twrp and one is kyo's recovery what i use every time.

. I already have done part one from the other thread but this is good to know thank you.

@suryavamsi6

I have a P1 c72, if I flash P1a42_S288... zip , will NFC work? I have a sensor for glucose, freestyle libre, working with NFC so this is an important point for me. Regards

MOBUTU90 said:
I have a P1 c72, if I flash P1a42_S288... zip , will NFC work? I have a sensor for glucose, freestyle libre, working with NFC so this is an important point for me. Regards
Click to expand...
Click to collapse
If i know it right, yes thats work perfectly for my friend.

I have a p1c58 (2gb ram 16 gb storage) bought from China. Is this procedure suitable for p1c58 too? Thanks

coolman7 said:
I have a p1c58 (2gb ram 16 gb storage) bought from China. Is this procedure suitable for p1c58 too? Thanks
Click to expand...
Click to collapse
Didnt tried, but the cpu and something are same, so u can try it.

Starchm said:
Didnt tried, but the cpu and something are same, so u can try it.
Click to expand...
Click to collapse
Is there any risk to damage or brick the phone?
Thanks

coolman7 said:
Is there any risk to damage or brick the phone?
Thanks
Click to expand...
Click to collapse
Yes it can, but on forums u csn search some backup rom

[ROM][7.1.1]Android Ice Cold Project 12.1
Hey Guys, I have got a big problem here. I had installed the latest release dated 28th Jan (link given by one of the developers). I had upgraded my TWRP to 3.0.2-0 then i installed the rom zip and the gapps zip. At first time it booted up normally without any bugs and all. However after next boot onwards i started getting many background app crashes so i decided to revert back to the TWRP backup which i had made on newly upgraded TWRP just before installing this rom. I had taken backup and then wiped everything to install.
After i restored with no errors i am stuck in boot loop. I mobile restarts and then holds on the boot animation and the vibrates and restarts again. This happens endlessly. I tried to re-wipe everything and restore but it didn't help. I tried to wipe everything and reinstall this rom again but now mobile turns up upto aicp boot animation and the screen turns off and only blue led indication comes on.
I have tried almost everything in laslt 24 hours but no way did anything. Am still stuck at endless bootloop.
This is all that i tried.
1. I tried to flash ROM S288 using QFIL : bootloop
2. I tried to flash ROM S285 using QFIL: bootloop
3. I tried to change partition from ext4 to fat and then back to ext4 for system and data and then restore twrp backup : Bootloop
4. I tried to change partition from ext4 to fat and then back to ext4 for system and data and then install aicp installable zip with gapps :stuck after boot animation with screen off and blue led on.
5. I erased all the partitions and formated all internal partitions as signle ext4 file system (29GB size) and then download stock rom with stock recovery using QFIL. : Bootloop.
There is only way i can stop bootloop and that is i force it to boot in recovery mode (stock/twrp). In either of the recovery mode it boots up and works normally. But irreespective of any rom i try to install it always ends up in bootloop. There is something that it is looking for just after boot animation which it is not able to find after boot animation and hence it boots again. I am not sure what it is looking for so i tried to erase every partition and restore that by downloading stock rom using qfil both lolipop and marshmallow version but still no use.
Please guys tell me what can be done now. its been over 24 hrs am struggling and i guess i already did everything i knew. Now i need your help.

Hey guys a new query here. Your expert opinion is required.
Check this attached screenshot.
I have range of both the networks. IMEI is also my original IMEI. But baseband is unknown. I remember baseband had some value. Why is it unknown now. Any idea?
Is there anything abnormal to worry or shall I ignore it?

Can anyone get me downloaded this p1c72 Vibe UI rom file from chinese website https://pan.baidu.com/s/1qXyzyX2. Please if anyone can please reply.

mity_dev said:
Can anyone get me downloaded this p1c72 Vibe UI rom file from chinese website https://pan.baidu.com/s/1qXyzyX2. Please if anyone can please reply.
Click to expand...
Click to collapse
http://4pda.ru/forum/index.php?showtopic
Translate this Russian language and look for vibe ui. What you are looking for is there.

Hey Guys
Today i have intentionally hard bricked my own Lenovo Vibe P1 (P1a42) just to demonstrate you all how to recover the dead (hard bricked) qualcomm devices.
This process is more or less same for all the qualcomm devices. In some devices other steps may be needed where you will have to wipe entire ROM space and make a single partition of ExFAT format.
https://youtu.be/ZU1vu5diGsE
Well i have tried to make the video in such a way that i include more or less everything possible. Please bare with me.
Further Readings and reference:
http://www.droidsavvy.com/unbrick-qualcomm-mobiles/
https://www.leakite.com/2016/06/revised-how-to-unbrick-qualcomm-android.html

can u please tell me which zip i have to download for putting in QFIL the link provided is having 7 downloads

[email protected] said:
can u please tell me which zip i have to download for putting in QFIL the link provided is having 7 downloads
Click to expand...
Click to collapse
P1a42_S288_160721_ROW_RAW_QFIL

Starchm said:
P1a42_S288_160721_ROW_RAW_QFIL
Click to expand...
Click to collapse
thanks , i have another problem i cant understand the steps after 11 can anybody explain them to me better .
11. That is not all!!! Your phone will reboot BUT u need to press 3/ i mean volume + , - and power / button for 10 second if it start reboot, or your phone will reboot in Android, and u will get again stock recovery.
12.A If you havent TWRP u need start it again from step 6.
12.B If you have TWRP swipe the trigger to right and confirm the first ask.
13. Go to install and search your Supersu and flash it.
14. Wipe your dalvick cache and normal cache and reboot your phone.
15. The first reboot will take a long time / 10 minute was for me / dont restart, let it work.
16. If you do everything good, have now a ROOTED phone.
Click to expand...
Click to collapse

lenovo vibe p1a42 with s288 row root device on ubuntu
Please anybody help in rooting my device lenovo vibe p1a42 with s288 row on ubuntu os
Thanks,
Sampath

Galaxy S4 Play Edition (GT-I9505G) and Lineage OS 15.1

Hello folks,
I have Galaxy S4, Play Edition, GT-I9505G, currently running SlimROM 7.1.2 build 1.17 (dated 20180115) and baseband version I9505GUEUDNL3.
Last stock I had on this phone was Android 5.0. If there was any OTA after that, I didn't install it.
(Sam Mobile does not list this device, hence no way of knowing firmwares, but https://forum.xda-developers.com/wiki/Samsung_Galaxy_S_4/GT-I9505G lists mine as the last firmware.)
I have been trying to install Lineage 15/Oreo ROMs and with every ROM I am getting Error 7, which is supposedly Recovery error but every time I have used the recovery recommended by the ROM administrator. So its definitely not a recovery issue in my case.
I was wondering, those with same device, managed to install Oreo ROM, what is your baseband version? Most likely, this is the culprit, but to be sure, I would like to know at least one person with same device and different baseband version that managed to install Oreo ROM.
This page (https://forum.xda-developers.com/galaxy-s4/i9505g-develop/odin-images-i9505g-t3271624) list a lot of stock ROMs. Mine is half way through. Hence, I would like to see someone with newer baseband running Oreo ROM.
Many thanks in advance.

Did you check the updater script to ensure the phone's model # is included?

audit13 said:
Did you check the updater script to ensure the phone's model # is included?
Click to expand...
Click to collapse
Yes. All the ROMs I tried were for I-9505 of which I-9505G is a variant. I also removed that part of the script, just in case, but the same error occurred.

fuzzychicken said:
Yes. All the ROMs I tried were for I-9505 of which I-9505G is a variant. I also removed that part of the script, just in case, but the same error occurred.
Click to expand...
Click to collapse
Maybe you need to add the gt-i9505g to the list rather than removing it.

audit13 said:
Maybe you need to add the gt-i9505g to the list rather than removing it.
Click to expand...
Click to collapse
It was already there, so the ROMs were compatible but I removed just in case, thought if it is not working with the model number in it, maybe I can try without it, as recommended on some other blog posts on the web.

I guess the only other thing would be to try different versions of TWRP.

audit13 said:
I guess the only other thing would be to try different versions of TWRP.
Click to expand...
Click to collapse
I am sorry, thats what I said in the OP. I have tried every possible version of TWRP that was recommended for those ROMs and the error keep showing up. That indicates that its not recovery that is causing the problem.

Only thing left I can think of would be to flash the latest stock ROM, factory wipe, flash twrp, then wipe, and then flash the custom ROM.

audit13 said:
Only thing left I can think of would be to flash the latest stock ROM, factory wipe, flash twrp, then wipe, and then flash the custom ROM.
Click to expand...
Click to collapse
That is what I am thinking but I am not too sure which is the latest stock ROM.
https://forum.xda-developers.com/galaxy-s4/i9505g-develop/odin-images-i9505g-t3271624 On this page, there are loads of stocks. Mine is half way through. Its I9505GUEUDNL3_FULL. Assuming that the list goes down as newer stocks, esp looking at the last 3 alpha-numerics, should I be flashing I9505GUEUDPF1_FULL?
If I flash, I9505GUEUDPF1_FULL will it write new bootloader and baseband? If yes, do I have to go through whole unlock bootloader thing? or just flash twrp via Odin and go ahead with newer ROM? This is the most sticky part as I don't remember how I did it in the past. I just don't touch something I am not very clear understanding on, but this time I would like to update to Oreo, primarily for security purpose and the cash is tight so if I brick this, I wouldn't be very happy to buy another device. Hence trying to dot all i's and cross all t's.
Thanks for all help in advance.

Flashing a stock ROM with Odin will update the bootloader and modem.
The bootloader is not locked and has never been locked on the gt-i9505.

audit13 said:
Flashing a stock ROM with Odin will update the bootloader and modem.
The bootloader is not locked and has never been locked on the gt-i9505.
Click to expand...
Click to collapse
Thank you.
Let me put it in steps, pls correct me if I am wrong.
1. Flash I9505GUEUDPF1_FULL using Odin. Once rebooted, confirm if newer baseband is present. Check if the calls and data works.
2. Flash TWRP recovery using Odin (it will revert to stock recovery, right?) If not, alls good as it is.
3. Install ROM of choice.
There is no data on the phone, I reflashed SlimROM after all attempts of Oreo failed.
Anything tricky stuff in between?
Thanks in advance.

To prevent the stock recovery from overwriting twrp, uncheck everything in Odin except for reset time, flash twrp, when you see the word "reset" in the status window, remove the usb cable from phone, remove the battery, replace the battery, boot into twrp.

audit13 said:
To prevent the stock recovery from overwriting twrp, uncheck everything in Odin except for reset time, flash twrp, when you see the word "reset" in the status window, remove the usb cable from phone, remove the battery, replace the battery, boot into twrp.
Click to expand...
Click to collapse
I am very sorry to be a PITA, mate, but I really need help here.
As per the suggestions, I tried flashing various images. In every image I flashed, the calling and wifi worked but cell data didn't work in any of those versions. Still I tried flashing Oreo with them but the error persisted. So probably, its something beyond I can do it with my little knowledge.
So finally, to give up I tried going to back to where I was before all this, to baseband version, I9505GUEUDNL3. I flashed NL3 image linked in the post https://forum.xda-developers.com/galaxy-s4/i9505g-develop/odin-images-i9505g-t3271624 through Odin. While the OS shown in about phone is 5.0, the baseband version is stuck at OJ1, where the data does not work.
Any idea how I can go back to NL3 where data worked flawlessly?
Many thanks in advance.
Edit: I flashed NL3 modem from https://forum.xda-developers.com/showthread.php?t=2452034 but still the issue persists. I have nandroid backups from the very first time when I flashed another ROM. If I use that to restore, will it restore all the issues?

The bootloader and modem should be flashed in tandem to maintain compatibility with each other. Data may not be working due to a mismatch.
Flash the latest stock ROM from sammobile.com, updato.com, or samsung-firmware.org.

audit13 said:
The bootloader and modem should be flashed in tandem to maintain compatibility with each other. Data may not be working due to a mismatch.
Flash the latest stock ROM from sammobile.com, updato.com, or samsung-firmware.org.
Click to expand...
Click to collapse
Thank you.
Can you pls take a look at this thread? https://forum.xda-developers.com/galaxy-s4/i9505g-develop/odin-images-i9505g-t3271624 Supposedly, these are factory images. I tried these images and my best guess is, they have right bootloader and modem. None of the sites you suggested carry stock images for GT-I9505G (Play Edition). They have GT-I9505 though.
What I tried so far.
- Flashed images linked above. Didn't work
(at one point, I even got OTA, when I was on OE1 baseband, it updated to OJ1. So in theory, in this OTA, it should fix this mismatch bootloader and modem, right?) When things didn't change after this update. I tried to flash NL3 image.
- Flashed NL3 image which I had. The baseband remained at OJ1. This was odd to me. So flashed NL3 modem. The issue persisted.
- I had taken nandroid backup before I started flashing custom ROMs. I tried to restore that back up through a custom recovery, TWRP. No help.
Screenshot of that backup, if it tells you anything
{
"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"
}
- I have EFS Backups, but I don't quite remember how I took that backup.
Screenshot attached. Any idea if this can be used to restore everything in one shot. I don't know if EFS contains bootloader as well.
You mentioned I should flash stock ROM. Assuming that ROM images linked on the XDA thread above are untouched, shouldn't that fix the issue? If not, is there any possibility one can find bootloader images (if such thing exists) because modem images are available in another thread. One can pick and choose a combination to flash. I am just speculating. I have no idea if such a thing can be done.
Thank you so much. Really appreciate you sticking around to share the ideas.
P.S. - Is there any option where you can delete both bootloader and modem just before flashing the stock ROM via Odin or TWRP?

There is no need to deal with the EFS at this moment as long as the phone is showing the correct IMEI and MAC address.
Yes, those look like factory images and you should try the latest ROM which is PF1. It's possible that the phone was running a newer bootloader than the one found in the NL3 ROM. Some boot loaders cannot be downgraded.
You cannot delete the bootloader from the phone. Without a bootloader, the phone would function. It's similar to the BIOS of a PC.

It is not TWRP that's the problem - it's the size of your system / user partitions on the 9505g.
@side said he would have a fix in version 4 OptLos for this.
His solution is not something I will be implementing in Resurrection Remix however.

audit13 said:
There is no need to deal with the EFS at this moment as long as the phone is showing the correct IMEI and MAC address.
Yes, those look like factory images and you should try the latest ROM which is PF1. It's possible that the phone was running a newer bootloader than the one found in the NL3 ROM. Some boot loaders cannot be downgraded.
You cannot delete the bootloader from the phone. Without a bootloader, the phone would function. It's similar to the BIOS of a PC.
Click to expand...
Click to collapse
So I flashed PF1 stock ROM, both bootloaders and modems are PF1. Made sure over the full day yesterday, there is no update and the problem persists. Can't flash Oreo and no cell phone data. Now, my interest in Oreo has pretty much died and only hoping to find a tweak to fix cell phone data. Fixed APN, made a factory reset just to be sure that its not the issue, tried SIM card in the different phone and other SIM in my phone that its not the SIM or the network thats the cause. So far I have not managed to find out what made the phone lose cell phone data.
Buff99 said:
It is not TWRP that's the problem - it's the size of your system / user partitions on the 9505g.
@side said he would have a fix in version 4 OptLos for this.
His solution is not something I will be implementing in Resurrection Remix however.
Click to expand...
Click to collapse
Dang man, your comment came a little late after I managed to fcuk up my phone very well trying to install Oreo. It will be great if you folks can make this comment in OP of the respective ROMs so that next I9505G user won't mess it up royally the way I did. If I remember correctly, I read both the threads start to the end and I didn't find any comment on this issue of I9505G.
Thanks both of you for chiming in and trying to help. If there is any idea to fix the loss of cell phone data, that will be of great help.

No possible way of getting into download mode. Please help. LG V20 H918 T-Mobile

I was able to root my phone and use it for a while but then it started reboot for no reason. It is currently running Oreo, H91820h.
I tried to restore to different earlier back up but same issue and a whole bunch of apps complain and terminate itself. Tried to flash Lineage OS and same problem.
So I tried to use LGUP to restore it to stock image but cannot get the phone into download mode.
When I hold the volume down button and plug in the USB cable, I get the fastboot screen.
{
"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"
}
When I hold the volume up button and plug in the USB cable, I get the "Download Mode" icon for about 2 second and then it switches to TWRP screen.
I remember when I first tried to install TWRP, it was version 3.2.1-3. Then I tried to flash twrp version 3.3.1-0 but for some reason, sometime it boots up with version 3.3.1-0 and sometime it boots up with version 3.2.1-3.
I cannot flash anything in fastboot or adb since it always come back with "FAILED (remote: 'unknown command')".
I have tried for over a week, read everything I could on the internet and tried everything but without success in getting into download mode to reload the stock image with LGUP.
Could anybody provide any suggestion or an alternate way of restoring the stock image without requiring going to download mode? May be re-flash with a different twrp version or remove twrp completely so it doesn't show up when I press volume up and plug in the USB cable.
Please, I am desperate. I can even send you the phone if you think you can fix it.
Thanks.

bqbase said:
I was able to root my phone and use it for a while but then it started reboot for no reason. It is currently running Oreo, H91820h.
I tried to restore to different earlier back up but same issue and a whole bunch of apps complain and terminate itself. Tried to flash Lineage OS and same problem.
So I tried to use LGUP to restore it to stock image but cannot get the phone into download mode.
When I hold the volume down button and plug in the USB cable, I get the fastboot screen.
When I hold the volume up button and plug in the USB cable, I get the "Download Mode" icon for about 2 second and then it switches to TWRP screen.
I remember when I first tried to install TWRP, it was version 3.2.1-3. Then I tried to flash twrp version 3.3.1-0 but for some reason, sometime it boots up with version 3.3.1-0 and sometime it boots up with version 3.2.1-3.
I cannot flash anything in fastboot or adb since it always come back with "FAILED (remote: 'unknown command')".
I have tried for over a week, read everything I could on the internet and tried everything but without success in getting into download mode to reload the stock image with LGUP.
Could anybody provide any suggestion or an alternate way of restoring the stock image without requiring going to download mode? May be re-flash with a different twrp version or remove twrp completely so it doesn't show up when I press volume up and plug in the USB cable.
Please, I am desperate. I can even send you the phone if you think you can fix it.
Thanks.
Click to expand...
Click to collapse
I'm not that familiar with the 918 ( I have 2 H910 )
But from the symptoms you described
I would guess that your MB is shot.
Even if you do manage to get into download mode you'll likely have errors flashing anything. I can look at the phone but it sounds like you need a replacement MB.
Sent from my Mi MIX 2S using Tapatalk

clsA said:
I'm not that familiar with the 918 ( I have 2 H910 )
But from the symptoms you described
I would guess that your MB is shot.
Even if you do manage to get into download mode you'll likely have errors flashing anything. I can look at the phone but it sounds like you need a replacement MB.
Sent from my Mi MIX 2S using Tapatalk
Click to expand...
Click to collapse
Not sure what you mean by "MB". I don't think it means "motherboard" so my best guess is "master boot".
Where can I get a replacement MB and how to replace it?

bqbase said:
Not sure what you mean by "MB". I don't think it means "motherboard" so my best guess is "master boot".
Where can I get a replacement MB and how to replace it?
Click to expand...
Click to collapse
Yes you need a motherboard
Or another phone
Sent from my Mi MIX 2S using Tapatalk

clsA said:
I'm not that familiar with the 918 ( I have 2 H910 )
But from the symptoms you described
I would guess that your MB is shot.
Even if you do manage to get into download mode you'll likely have errors flashing anything. I can look at the phone but it sounds like you need a replacement MB.
Sent from my Mi MIX 2S using Tapatalk
Click to expand...
Click to collapse
bqbase said:
Not sure what you mean by "MB". I don't think it means "motherboard" so my best guess is "master boot".
Where can I get a replacement MB and how to replace it?
Click to expand...
Click to collapse
Hold the phone here, the H918 can NEVER use fastboot to flash, thats why the lafsploit is used to replace download mode with a copy of twrp, leading many H918 users to have two different twrp installs.
To get download mode back flash this from the original lafsploit thread.
Rebooting for no reason is a bad sign (maybe see about replacing your battery if its the original one). Everything else (fastboot not working, download mode replaced by twrp)? Normal.

Phoenix591 said:
Hold the phone here, the H918 can NEVER use fastboot to flash, thats why the lafsploit is used to replace download mode with a copy of twrp, leading many H918 users to have two different twrp installs.
To get download mode back flash this from the original lafsploit thread.
Rebooting for no reason is a bad sign (maybe see about replacing your battery if its the original one). Everything else (fastboot not working, download mode replaced by twrp)? Normal.
Click to expand...
Click to collapse
OMG, OMG, OMG, I got my download mode back. I am so appreciate your help. I wish I can send you a beer.
I must have gone through this lafsploit thread a hundred times but never paid attention to this "OPTIONAL" note and I wasted sooo much time refusing to post a question on this forum thinking I can find the answer just buy combing through the internet.
I believe you are dead on with reboot issue too. I got more than a few times with the phone complaining that wrong battery was inserted and need to shutdown. But I thought my un-experienced flashing of all the junks I did on the phone are causing it.
"OPTIONAL
If you would like to restore download mode onto your laf partition AFTER you have installed TWRP onto recovery:
Boot to TWRP that is on recovery
Flash this zip: laf_restore.zip
This can be done at any time after you are rooted. About the only reason you would want to flash laf back is if you use LG Backup.
TWRP has the ability to backup your phone, so I am not sure why someone would want this (maybe you are more comfortable with it?).
Also, flashing back to 100% unrooted stock can be accomplished by flashing a zip in TWRP, you don't NEED to flash a KDZ, but again, maybe you are more comfortable doing it that way.
The bottom line is TWRP on both laf and recovery is FAR FAR more useful than flashing laf back. You can test new versions of TWRP while keeping your old known working version (for example)."

clsA said:
I'm not that familiar with the 918 ( I have 2 H910 )
But from the symptoms you described
I would guess that your MB is shot.
Even if you do manage to get into download mode you'll likely have errors flashing anything. I can look at the phone but it sounds like you need a replacement MB.
Sent from my Mi MIX 2S using Tapatalk
Click to expand...
Click to collapse
I just want to say thank you to clsA and Phoenix591 for the help. I found the answer and was able to successfully restore my phone to 100% stock. I know it's hard to pinpoint the issue while trying to understand all the craps that people post on their question. Hit or miss, right or wrong, work or not, I really appreciate all the effort that you did to help me figure out the solution.

bqbase said:
I just want to say thank you to clsA and Phoenix591 for the help. I found the answer and was able to successfully restore my phone to 100% stock. I know it's hard to pinpoint the issue while trying to understand all the craps that people post on their question. Hit or miss, right or wrong, work or not, I really appreciate all the effort that you did to help me figure out the solution.
Click to expand...
Click to collapse
Guess I missed it on this one
V20 does have a lot of motherboard issue over the years. Apps crashing and phone rebooting randomly are 2 of them.
Glad you got it sorted and back to stock
Sent from my Mi MIX 2S using Tapatalk

Phoenix591 said:
Hold the phone here, the H918 can NEVER use fastboot to flash, thats why the lafsploit is used to replace download mode with a copy of twrp, leading many H918 users to have two different twrp installs.
To get download mode back flash this from the original lafsploit thread.
Rebooting for no reason is a bad sign (maybe see about replacing your battery if its the original one). Everything else (fastboot not working, download mode replaced by twrp)? Normal.
Click to expand...
Click to collapse
Thank you very much, i can Relock and unroot my device with this, thank you so much

Phoenix591 said:
Hold the phone here, the H918 can NEVER use fastboot to flash, thats why the lafsploit is used to replace download mode with a copy of twrp, leading many H918 users to have two different twrp installs.
To get download mode back flash this from the original lafsploit thread.
Rebooting for no reason is a bad sign (maybe see about replacing your battery if its the original one). Everything else (fastboot not working, download mode replaced by twrp)? Normal.
Click to expand...
Click to collapse
Hi I've happened to run into the same mistake however the link is broken. If you still have the file I would really appreciate the help.
I'm usually very careful when it comes to flashing but I made the mistake of trusting someone to unlock my V20 for global use, vendor told me they didn't know if they could do it since it was rooted and their unlocking software detected the root. He needed to remove the root and charge me extra. I trusted him into removing the root and pushed back the agreed upon date like three times. He kept saying he could not remove twrp. Long story short he told me he wasn't able to do it and gave me a discount, he said he was able to unlock it but was not able to power it on as it was bootlooping. I assume it was because he locked the bootloader and once I unlocked it again when I try to go into download mode to restore into LGUP it boots me into twrp instantly. Thanks in advance

Cannot boot to latest version of TWRP on SM-N910G

Hello!
I bought an SM-N910G on ebay recently. The stock rom is a little bit slow and I would like to flash lineage or something else.
When i try to flash the latest version of twrp with odin it passes and shows the splash screen with the logo and version (all normal) but doesnt load and reboots to Android.
Does anyone have any ideas? ive tried most things that i found online but nothing works. the first available version on the twrp website does flash and work but wont flash latest lineage.

del32 said:
Hello!
I bought an SM-N910G on ebay recently. The stock rom is a little bit slow and I would like to flash lineage or something else.
When i try to flash the latest version of twrp with odin it passes and shows the splash screen with the logo and version (all normal) but doesnt load and reboots to Android.
Does anyone have any ideas? ive tried most things that i found online but nothing works. the first available version on the twrp website does flash and work but wont flash latest lineage.
Click to expand...
Click to collapse
Which bootloader is active?
So 3.6.2-9-0 doesn't start?
Tried flashing that .img using old TWRP as well or only .tar with Odin?
What did 3.1.0-0 say when flashing LOS fails?

bmwdroid said:
Which bootloader is active?
So 3.6.2-9-0 doesn't start?
Tried flashing that .img using old TWRP as well or only .tar with Odin?
What did 3.1.0-0 say when flashing LOS fails?
Click to expand...
Click to collapse
sorry i am not sure what you mean by which bootloader is active, is there a way to check this?
Nope, it just loads on the splash screen for a while then boots back to android
I have tried old twrp to flash and odin tar
It said an error about this rom is for *phone* you are using blank or something along those lines.
Afaik 3.5(?) is the only one that can install past oreo roms

del32 said:
sorry i am not sure what you mean by which bootloader is active,
is there a way to check this?
Click to expand...
Click to collapse
That's the one from the stock firmware you came from.
Should be the latest stock possible.
Did you check or can you tell?
del32 said:
Nope, it just loads on the splash screen for a while then boots back to android
I have tried old twrp to flash and odin tar
It said an error about this rom is for *phone* you are using blank or something along those lines.
Click to expand...
Click to collapse
Can you provide a screenshot?
del32 said:
Afaik 3.5(?) is the only one that can install past oreo roms
Click to expand...
Click to collapse
Well mine is on 3.6.1_9-0 and currently on Havoc 4.16 I got from the telegram group.
Has of course the battery drain problem (like all A11 custom versions for this device) when shut down.
With that TWRP I've installed A11 versions of LOS, crDroid and Havoc mulitple times.

bmwdroid said:
That's the one from the stock firmware you came from.
Should be the latest stock possible.
Did you check or can you tell?
Can you provide a screenshot?
Well mine is on 3.6.1_9-0 and currently on Havoc 4.16 I got from the telegram group.
Has of course the battery drain problem (like all A11 custom versions for this device) when shut down.
With that TWRP I've installed A11 versions of LOS, crDroid and Havoc mulitple times.
Click to expand...
Click to collapse
im using the latest 6.0.1 australia optus firmware (im australian and on optus)
there were bootloader files there available there for download but i dont think they worked for me. and also gave me no service in android
I am currently at school, so i will be able to provide a screenshot later
should i try a different stock firmware version/ different country carrier when i get home?

del32 said:
im using the latest 6.0.1 australia optus firmware (im australian and on optus)
Click to expand...
Click to collapse
So that should be ok.
del32 said:
...
should i try a different stock firmware version/ different country carrier when i get home?
Click to expand...
Click to collapse
No idea if that wil do any good or even harm your device.
I know that on some that works but idk about yours.
Perhaps it will help to start from scratch flashing the latest stock if available via samfirm_reborn_3.6.3 (gets it directly from Samsungs servers).

bmwdroid said:
So that should be ok.
No idea if that wil do any good or even harm your device.
I know that on some that works but idk about yours.
Perhaps it will help to start from scratch flashing the latest stock if available via samfirm_reborn_3.6.3 (gets it directly from Samsungs servers).
Click to expand...
Click to collapse
I'll try samfirm_reborn_3.6.3
currently installing the files it needs
{
"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"
}

@del32 which files?
Didn't need any additional ones on my W11 system.
SamFirm_Reborn itself starts directly without installation.
Took it from here:
GitHub - ivanmeler/SamFirm_Reborn
Contribute to ivanmeler/SamFirm_Reborn development by creating an account on GitHub.
github.com

bmwdroid said:
@del32 which files?
Didn't need any additional ones on my W11 system.
SamFirm_Reborn itself starts directly without installation.
Took it from here:
GitHub - ivanmeler/SamFirm_Reborn
Contribute to ivanmeler/SamFirm_Reborn development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
not sure what it needed but i just installed anyways and it all worked
used the same github link
also now in twrp, getting error 1 got a screenshot

del32 said:
not sure what it needed but i just installed anyways and it all worked
used the same github link
also now in twrp, getting error 1 got a screenshot
Click to expand...
Click to collapse
Well your device is trltedt so ROM should fit.
Which TWRP right now?
Did updaing it work?
You did "Format data" after wiping?
Tried with 2nd download of that ROM?
Tried crDroid or Havoc?
Once when I had flashing problems I changed filesystem of several partitions to and fro which helped.
If that all doesn't help I'ld start from scratch.

bmwdroid said:
Well your device is trltedt so ROM should fit.
Which TWRP right now?
Did updaing it work?
You did "Format data" after wiping?
Tried with 2nd download of that ROM?
Tried crDroid or Havoc?
Once when I had flashing problems I changed filesystem of several partitions to and fro which helped.
If that all doesn't help I'ld start from scratch.
Click to expand...
Click to collapse
I am using 3.1.0
I tried a later version and still didnt work, 3.2.2 does not even work!!!
Yes, format data after wiping.
I have tried to redownload
will try havoc right now

@bmwdroid
same issue with havoc, error one and your device is blank
not sure what happened with it

del32 said:
@bmwdroid
same issue with havoc, error one and your device is blank
not sure what happened with it
Click to expand...
Click to collapse
I suppose you definitely need a higher TWRP version but don't understand why you can't flash it.
What does TWRP say when you flash a higher version?

@del32 regarding higher TWRP.
As I understood you you're either flashing 3.5 or higher using Odin and it then TWRP doesn't start afterwards.
Correct?
What happens when you flash high TWRP...img using the older 3.1. TWRP and reboot after that into recovery from TWRP menu?

bmwdroid said:
@del32 regarding higher TWRP.
As I understood you you're either flashing 3.5 or higher using Odin and it then TWRP doesn't start afterwards.
Correct?
What happens when you flash high TWRP...img using the older 3.1. TWRP and reboot after that into recovery from TWRP menu?
Click to expand...
Click to collapse
I just got it to work!!! TWRP 3.5.2 and Havoc are running!!!
i was recording a video to show what i did and how it failed and it just worked
as long as i dont screw around with twrp i should be fine, thank you for your help.
if it wasnt for your response i was just going to give up and not bother.
Your browser is not able to display this video.

@del32 glad I could somewhat help.
May I quote from the film "Galaxy Quest":
Never give up, never surrender
Additional advices: I saw you rebooting after flashing but it's recommended to wipe Cache/Dalvik before the reboot.
It's useful to activate "advanced reboot" so that you can directly reboot to TWRP from the system without button combo.
When you want to get a higher TWRP you can flash it directly within the old one using a .img file.
Worked always for me so it should for you as well.
And you could mark the thread as solved so that others have no need to answer.

bmwdroid said:
@del32 glad I could somewhat help.
May I quote from the film "Galaxy Quest":
Never give up, never surrender
Additional advices: I saw you rebooting after flashing but it's recommended to wipe Cache/Dalvik before the reboot.
It's useful to activate "advanced reboot" so that you can directly reboot to TWRP from the system without button combo.
When you want to get a higher TWRP you can flash it directly within the old one using a .img file.
Worked always for me so it should for you as well.
And you could mark the thread as solved so that others have no need to answer.
Click to expand...
Click to collapse
Thank you very much, also ive never had issue with not wiping after flash but ill keep it in mind and try to remember for later on
I also had advanced reboot on but i didnt have an os on the phone at time of recording
once again, many thanks!!!!!!!
so excited to have Havoc on my phone

del32 said:
Thank you very much, also ive never had issue with not wiping after flash but ill keep it in mind and try to remember for later on
I also had advanced reboot on but i didnt have an os on the phone at time of recording
once again, many thanks!!!!!!!
so excited to have Havoc on my phone
Click to expand...
Click to collapse
Which Havoc version btw?

bmwdroid said:
Which Havoc version btw?
Click to expand...
Click to collapse
4.6, working nicely on android 11
faster than i thought it would be!

@del32 here you find much newer ones: