Unable to boot TWRP SMN-9005 - Galaxy Note 3 Q&A, Help & Troubleshooting

i tried to flash twrp 3.0 on my smn9005 HLTE but when i try to boot recovery it says
Booting Recovery
Bit Set Warratnyy: Recovery
then black screen apeears mobile vibrate 2 time and then retart as normal my phone is not bricked then i tried twrp 2.8.7.0 it worked fine but i am not able to install any cutom rom it gives error 3004, this rom is for HLTE, HLTEXX etc, what should i do my phone is currently running on stock LP 5.0 and i am 100% sure my phone is HLTE, HLTEXX but new twrp wont work and on older i cannot install any rom even after advance wipe

<i tried twrp 2.8.7.0 it worked fine but i am not able to install any cutom rom
ANY really or just one or two ??
2.8.70 works fine on roms but not for later ports .( see multiple posts)
If you need a later twrp .
Flash 2.8.7.0 then through TWRP flash later TWRP zip.

JJEgan said:
<i tried twrp 2.8.7.0 it worked fine but i am not able to install any cutom rom
ANY really or just one or two ??
2.8.70 works fine on roms but not for later ports .( see multiple posts)
If you need a later twrp .
Flash 2.8.7.0 then through TWRP flash later TWRP zip.
Click to expand...
Click to collapse
thank you for reply, i tried to flash twrp 3.0.zip with twrp 2.8.7.0 but i came up with same issue untill now i have tried
Potato chips(pie), AOSP 9.0 extended all failed to flash in twrp 2.8.7.0 , i cant understand why it is happening now i am flashing repair firmware then i will try it back if it fails then i will downgrade to stock 4.4 again try, i also tried Linegae 14.1 it flashed succesfully but caused bootlops now i am again back to stock

i think i cannot upgrade more from 6.0 now i am downloading TouchWiz MM :crying: :crying:

lastwarning91 said:
thank you for reply, i tried to flash twrp 3.0.zip with twrp 2.8.7.0 but i came up with same issue untill now i have tried
Potato chips(pie), AOSP 9.0 extended all failed to flash in twrp 2.8.7.0 , i cant understand why it is happening now i am flashing repair firmware then i will try it back if it fails then i will downgrade to stock 4.4 again try, i also tried Linegae 14.1 it flashed succesfully but caused bootlops now i am again back to stock
Click to expand...
Click to collapse
When u flash new TWRP first time ,backup your efs (imei,modem).
Second with TWRP 2.8.7.0 u can only flash stock Samsung rom that have aroma support.
Only TWRP 3.2.3.0, this is the latest can flash Oreo ,pie ,nougat roms without issue. But remember u can't flash Samsung roms with this and u have to go back to twrp 2.8.7. Then go back to 3.2 if u wanna flash pie ect roms

Hi all
I can successfully flash twrp-2.8.7.0-hlte-4.4.img.tar and boot into recovery.
But later TWRP,s dont boot.
JJEgan says to flash 2.8.70 and if you need a later twrp flash 2.8.7.0 then through TWRP flash later TWRP.zip.
Question is where can i get a zip of the latest TWRP. The official releases are either img or tar
Thanks

grwalker said:
Hi all
I can successfully flash twrp-2.8.7.0-hlte-4.4.img.tar and boot into recovery.
But later TWRP,s dont boot.
JJEgan says to flash 2.8.70 and if you need a later twrp flash 2.8.7.0 then through TWRP flash later TWRP.zip.
Question is where can i get a zip of the latest TWRP. The official releases are either img or tar
Thanks
Click to expand...
Click to collapse
The Twrp are always .img.tar or .img or even apk from play store https://play.google.com/store/apps/details?id=me.twrp.twrpapp. Anyway, i flashed twrp 3.2.3.0 from 2.8.7.0 ( the same one you had ) using Odin 3.11.1 without a single problem! Mybe the problem is just the Odin's version you used, have a look here too to better understand https://www.theandroidsoul.com/how-to-install-twrp-recovery-using-odin/. I hope you can solve it, good luck.

Thanks
When using 2.8.7.0 to flash latest TWRP.img, did you flash to boot or recovery? I get those choices after i select the file to flash. I assume recovery, right?
************ - -UPDATE - -*****************
Flashed img to recovery. All good, said flashing successful . . .but
Tried to reboot to new recovery but got the same boot loop.
Flashed 2.8.7.0 again using ODIN and 2.8.7.0. booted up just fine.
Re flashed 3.2.3.0 from 2.8.7.0. Again the same boot loop
Went back to 2.8.7.0 using ODIN. Booted up.
no idea what to do next
Thanks

I have same issues towards my hlte, twrp ver release later than what you indicated causes recovery boot loops, only 2.8 works. I cant even install custom rom due to unupdated twrp support.

echo-26 said:
I have same issues towards my hlte, twrp ver release later than what you indicated causes recovery boot loops, only 2.8 works. I cant even install custom rom due to unupdated twrp support.
Click to expand...
Click to collapse
You need to read first.
TWRP cannot flash Aroma based roms after 2.8 as per multiple posts .
Later android based roms use later TWRP 3 versions all posted .

Related

Can't Boot into Recovery - Lost Root Access

Hi,
Below is was my setup:
Latest TWRP Recovery
Alucard Kernel
S4 i9505
CM12.1 nightly
XPOSED v75
Viper4Android
Two days ago I decided to flash the sabermod kernel. At first I couldn't install it using the .zip (script error of some sort)
I then flashed the boot.img file as boot.
The phone was working fine for two days (rebooted twice at least).
On every Friday I download the latest nightly and flash it using the dirty flash method.
This is when I ran into trouble...
The TWRP is stuck on the Team Win screen.
I found a way to boot normally and decided to flash the alucard kernel back using Kernel Adiutor (boot.img).
The phone booted but now I have endless process stop errors (com.google.process.gapps) and I have lost root.
I need help...
Regards,
Jat
jdhot2 said:
Hi,
Below is was my setup:
Latest TWRP Recovery
Alucard Kernel
S4 i9505
CM12.1 nightly
XPOSED v75
Viper4Android
Two days ago I decided to flash the sabermod kernel. At first I couldn't install it using the .zip (script error of some sort)
I then flashed the boot.img file as boot.
The phone was working fine for two days (rebooted twice at least).
On every Friday I download the latest nightly and flash it using the dirty flash method.
This is when I ran into trouble...
The TWRP is stuck on the Team Win screen.
I found a way to boot normally and decided to flash the alucard kernel back using Kernel Adiutor (boot.img).
The phone booted but now I have endless process stop errors (com.google.process.gapps) and I have lost root.
I need help...
Regards,
Jat
Click to expand...
Click to collapse
Just reflash TWRP. Uncheck auto-reboot in Odin before flashing.
F2FS Support
I have all partitions formatted in F2FS apart from system which is EXT4. Can I flash TWRP via Odin if it is not . tar?
jdhot2 said:
I have all partitions formatted in F2FS apart from system which is EXT4. Can I flash TWRP via Odin if it is not . tar?
Click to expand...
Click to collapse
Flashing a firmware will fix the issue, both for recovery and rom
Which Firmware?
Which Firmware to flash? Obviously I can only flash via odin. Also what will happen to the F2FS partitions?
jdhot2 said:
Which Firmware to flash? Obviously I can only flash via odin. Also what will happen to the F2FS partitions?
Click to expand...
Click to collapse
Flashing will return you to ext4
Because f2fs needs a special recovery files etc... and it will be replaced.
Test it out you wont lose nothing
Flash latest samsung touchwiz?
Just to confirm you are asking to flash the latest Sammy rom which I believe is 5.0.1. however Cm12.1 is 5.1.1. If you are confident in me trying this I will download the stock rom and flash it via odin and will let you know how I go. Thanks for your help so far.
jdhot2 said:
Just to confirm you are asking to flash the latest Sammy rom which I believe is 5.0.1. however Cm12.1 is 5.1.1. If you are confident in me trying this I will download the stock rom and flash it via odin and will let you know how I go. Thanks for your help so far.
Click to expand...
Click to collapse
Yes flashing sammy, no prob always here to help
Flashing Now
I am now flashing latest Sammy rom with latest Odin.
You're a lifesaver!
Thanks for your help much appreciated.
My phone is up and running again.
Next time if I have any issues with my s4 I'll just flash the latest Sammy rom.

no custom recovery after flashing UHOJ4 bootloader

Hi,
I had several problems with custom rom, so I went back to stock ROM (latest MOB version) to start everything new.
Now I got the problem that it is not possible to flash CWM or TWRP again (tried different versions to flash with odin). I also tried to get back to UHOL2 bootloader and modem, bootloader is now UHOL2 but also custom recovery not working.
Any ideas how to get TWRP working again?
Thx
Jürgen
Can you root it?
Then you might be able to use flashify to flash the recovery.img
xdajuecat said:
Hi,
I had several problems with custom rom, so I went back to stock ROM (latest MOB version) to start everything new.
Now I got the problem that it is not possible to flash CWM or TWRP again (tried different versions to flash with odin). I also tried to get back to UHOL2 bootloader and modem, bootloader is now UHOL2 but also custom recovery not working.
Any ideas how to get TWRP working again?
Thx
Jürgen
Click to expand...
Click to collapse
Uncheck auto-reboot before flashing TWRP trough Odin.
used CF Auto root - Phone Info says that root is working
which recovery.img should I try - CWM or TWRP doesn't matter for me
TWRP. CWM is outdated.
Uncheck auto-reboot before flashing TWRP trough Odin and removing battery was the solution!
Thx
Selecting auto reboot after flashing twrp causes the stock recovery to overwrite twrp and this is why the phone should be booted into twrp right after flashing.

Stuck in a never-ending bootloop after trying TWRP for SM N9005

My phone is a Samsung Note 3 SM-9005, currently it's stuck in an infinite bootloop even after removing the battery for an hour.
I get this message:
RECOVERY BOOTING ...
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit : recovery
... along with the Samsung SM-N9005 logo, a couple of beeps/buzzes and then it repeats ad infinitum.
Here's what I did over the last day to get to this sorry state of affairs:
1. Upgraded from Android 4.3 (the original operating system) to 5.0 using the Samsung N9005XXUGBOA5 ROM with Odin 3.12. This worked fine but the phone lost root.
2. I rooted the phone again using Odin and Chainfire Auto-Root. All good so far.
3. I installed TWRP (the official TWRP App 1.5, going by my records)
4. I flashed the latest custom recovery which would have been 3.0.x and this seemed to be fine. So far no problems.
5. I then got ideas above my lowly station, apparently. I wanted to flash one of the newer ROMs: [Rom][N7 Port][12.12.2016] [Multi-DPI] Phronesis Rom N7 v4.1 Feature Rich & Smooth
https://forum.xda-developers.com/ga...m-phronesis-mm-rom-v1-0-feature-rich-t3463244
6. In the instructions, it said to use TWRP recovery version 2.8.7. I found that and flashed it. (Yes, it was for the Samsung SM N9005).
7. I rebooted into recovery mode to make a backup with that 2.8.7 version.
8. Now I'm stuck in boot loop hell with ...
RECOVERY BOOTING ...
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit : recovery
... with the Samsung SM-N9005 logo, a couple of beeps/buzzes and so on (as stated above).
I've tried leaving the battery out for an extended period and this hasn't worked. The phone never gets to the stage where I can talk to it with Odin or get any kind of menu. Is the phone truly bricked now?
If so, was it a critical error to go from the 3.0.x TWRP recovery back to 2.8.7 for the purposes of this custom ROM upgrade?
If not, what can be done to regain control of the phone?
This is obviously an older phone as I've had it for about 3 years now, but I'd love to get it working again if possible. I really loved it and was planning to use it for a couple more years (hence the upgrade path I've explained above).
Can you boot into download mode? I suspect you flash the 4.3 version of twrp, you need a 4.4 version. This one https://dl.twrp.me/hlte/twrp-2.8.7.0-hlte-4.4.img.tar.html
Boot into download mode and flash it with odin.
I suggest flashing the latest stock ROM, flash the latest tar version of twrp with Odin, root with supersu.zip in twrp.
Stonedead, you were right on the money. I did what you suggested (Download mode) and that different TWRP file, and it worked.
Thanks so much.
Thanks audit13 also, although I didn't need to go that far to undo my mistake.
I got the same problem with my note 3. Thank you for the solution. Now how do I exactly get TWRP working on my phone. It is already rooted.
See TWRP thread.
Basics flash twrp tar through odin
Root is not needed to install the tar version of TWRP with Odin.
Thanks. Managed to get twrp working now. Also installed the note 8 Rom
Hi ok im having the same problem kinda follow the installation as posted,so i have note 3 sm-n9005 stock rom,root and replaced twrp 4.3 for 4.4 to install phronesis n7 v7 for note 3 followed all instructed then rebooted went to samsung boot then booted to twrp recovery ive been on it all day thinking what da hell ive done wrong?can someone instruct me of what i did or didnt do or have i completely mess stuff up?cheers anyone.
instructions .
Boot into recovery (say TWRP 2.8.7.0)
JJEgan said:
instructions .
Boot into recovery (say TWRP 2.8.7.0)
Click to expand...
Click to collapse
Sorry jjegan not following?it already reboots into twrp recovery after the galaxy note 3 logo appears for 20 seconds?I have read and followed threads that have same or similar problems but no avail im am totally lost and from reading this rom it sounds great if I can get there that is,so please simple instructions would be very helpful as I'm still learning very sorry for being dumb.
This rom
phronesis n7 v7 for note 3
all Aroma roms require TWRP 2.8.7 and not newer versions .As posted multiple times in the thread .
Search results for query: TWRP
forum.xda-developers.com
JJEgan said:
This rom
phronesis n7 v7 for note 3
all Aroma roms require TWRP 2.8.7 and not newer versions .As posted multiple times in the thread .
Search results for query: TWRP
forum.xda-developers.com
Click to expand...
Click to collapse
Hi JJEgan,thank you for the reply back much appreciated for your time so far,so do you mean twrp-2.8.7.0-hlte-eu.tar file?and not twrp 2.8.7.0-hlte-4.4 img.tar file?that's the one I am using to flash the rom with and having problems with.
Hi there again ok im so confused not sure which one,there are so many of the 2.8.7.0 versions with 4.3 or 4.4-img.tar im not sure if im downloading 4.4 or 4.3 as im still a noob and love tech,I have read threads upon this rom problems still can't get the grasp of the simple twrp version I have lte au version android 5,and when I read 2.8.7.0 im think is it 4.4 4.3 or just 2.8.7.0 tar file?I'm following the installation up into the problem of not booting up in stays In galaxy note 3 boot and I have removed the battery 5mi z replaced then recovery and factory reset then it does the same again and I have tried 3 times waited longer each time im thinking maybe go back to stock I don't think my phone is agreeing with me,jjEgan thanks for the info amd time im sorry if annoy you with a simple installation to you,still I have read and grasp the concept of twrp installer version yeah??
Only use 2.8.70 as said later versions wont flash that rom.
2.8.7.0 TAR flashed through Odin .
JJEgan said:
Only use 2.8.70 as said later versions wont flash that rom.
2.8.7.0 TAR flashed through Odin .
Click to expand...
Click to collapse
Thanks for the reply JJEgan,no I have finally fix the problem solution start over fresh instalments installed stock,flash twrp 4.4, flashd supersu threw twrp,wiped 3x install,instead of rebooting threw Aroma rebooted system threw twrp it loaded first go,thanks for the threads I took bits n pieces frm each threaded problems,cheers JJEgan love the version rom,one more thing what kernel would be better or what would your choice be cheers

Bricked SM-J500FN (After flashing TRWP)

So I rooted my Samsung Galaxy J5 (SM-J500FN) by flashing CF-Autoroot with ODIN, and then I wanted to flash TRWP so I could install XPosed Framework.
After flashing TRWP with no errors on ODIN, if I try to reboot normally or in recovery the screen slowly turns green?
I managed to get into Download mode and connected to ODIN, but I cannot flash a new ROM as you cannot flash .zip files. (I have a LineageOS rom and my Stock ROM with build number J500FNXXU1BQA4)
up2 said:
So I rooted my Samsung Galaxy J5 (SM-J500FN) by flashing CF-Autoroot with ODIN, and then I wanted to flash TRWP so I could install XPosed Framework.
After flashing TRWP with no errors on ODIN, if I try to reboot normally or in recovery the screen slowly turns green?
I managed to get into Download mode and connected to ODIN, but I cannot flash a new ROM as you cannot flash .zip files. (I have a LineageOS rom and my Stock ROM with build number J500FNXXU1BQA4)
Click to expand...
Click to collapse
The screen turns green when you flash the wrong TWRP (not corresponding to your Android version) or when you flash Lollipop roms over Marshmallow and vice versa (except MM/N cm/aosp roms which must be flashed on LP).
You can flash only stock rom (.tar format file) with Odin.
TWRP for lollipop 5.1.1: https://forum.xda-developers.com/galaxy-j5/development/recovery-samsung-galaxy-j5-t3468844 .
TWRP for Marshmallow 6.0.1: https://forum.xda-developers.com/galaxy-j5/development/recovery-samsung-galaxy-j500f-t3416960 .
Flash the correct TWRP according to your Android version. I believe you must reflash stock rom with Odin first since you're screen is turning on, but try to flash the correct TWRP first and see if you get rid of your problem. If not, then reflash stock rom and then flash TWRP again.
#Henkate said:
The screen turns green when you flash the wrong TWRP (not corresponding to your Android version) or when you flash Lollipop roms over Marshmallow and vice versa (except MM/N cm/aosp roms which must be flashed on LP).
You can flash only stock rom (.tar format file) with Odin.
TWRP for lollipop 5.1.1: https://forum.xda-developers.com/galaxy-j5/development/recovery-samsung-galaxy-j5-t3468844 .
TWRP for Marshmallow 6.0.1: https://forum.xda-developers.com/galaxy-j5/development/recovery-samsung-galaxy-j500f-t3416960 .
Flash the correct TWRP according to your Android version. I believe you must reflash stock rom with Odin first since you're screen is turning on, but try to flash the correct TWRP first and see if you get rid of your problem. If not, then reflash stock rom and then flash TWRP again.
Click to expand...
Click to collapse
Wow, thanks a lot.
The thread where I got the TWRP from didn't show that it was for 5.1.1, I flashed TRWP for 6.0.1 and my phone worked again and the TWRP works!
Thanks!!

SM-9005 could not do normal boot when flashing TWRP 2.8.7.0

Hello. I have SM-9005 and by mistake I flashed the latest TWRP (3.2.3.0) when it should be flashed the 2.8.7.0. Successfully I reverted to recovery and firmware stock, but when when I tried to flash again to use the TWRP 2.8.7.0 the phone enters in Odin mode and says it could not do normal boot. However, I always succeed in flashing the 3.2.3.0 version. From the file list my TWRP 2.8.7.0 is the hltexx version and still can't flash it.
Without that TWRP I can't instal the MAGMA roms. I tried installing older versions of TWRP but with no success. Any thoughts? Thanks.
P.S: already found the solution. Wrong TWRP

Categories

Resources