Stuck with flashing custom rom - Galaxy Note 3 Q&A, Help & Troubleshooting

Hello everyone, first of all am a newbie and I am trying to flash my Note3 with custom rom, I installed twrp using Odin, first I faced an error that Everytime Odin will say pass but phone will boot normal, how ever I find the solution by unchecking auto reboot in Odin, after pass I'll unplug the device, pull off battery then restart and it will get me to term recovery and it works fine afterwards. I tried installing few custom ROMs like magma nx, dark lord x etc but after everything done phone get stuck in bootloop. First I did the same and got stuck then I did a stock rom flash and got the phone working again, how ever I tried flashing again with magma nx and it got away from Samsung logo to pyeongchang edition logo and got stuck there, all the roms I tried give me same error. Am using twrp 2.8.7.0. I had also rooted using SuperSU, how can I get past this? Any help will be appreciated.. thank you

What phone model ??
Bootloop read the thousands of bootloop posts use roms SEARCH THREAD box bootloop .
Difficult to know what you are doing wrong without more information .

Model is a Note 3 N9005,
I have gone through most of the threads but I am not finding a solution yet, as I said :-
1) Installed TWRP using Odin
2) Rooted the device
3)Placed few Custom ROMs in SD
4)Flashed using TWRP (followed instructions)
5) Flashing finished successfully
6) Reboot
7) Bootloop
Stuck here, can I provide any other details?

3)Placed few Custom ROMs in SD
As in what rom one only not multiples .
4)Flashed using TWRP (followed instructions)
Right twrp wrong twrp ??
7) Bootloop
What did rom thread say about bootloop ??
Updated bootloader >>when required .
Magma has full instructions and full faqs .
---------- Post added at 02:02 PM ---------- Previous post was at 01:43 PM ----------
mAGMA
SEARCH THREAD Bootloop
https://forum.xda-developers.com/search/thread/3508672?query=bootloop
FAQ
Q: I have bootloop right after I flash the ROM
2. In first boot, when asked to "Consent for Diagnostic Report", you forgot to uncheck it. As written in OP, you have to "uncheck" the Consent for Diagnostic Report.
To solve it:
1. Power off phone
2. Remove sim card
3. Boot to ROM.
4. Go to settings/general management
5. Disable "Report Diagnostic Info"
6. Power off Device.
7. Insert sim card.
8. Boot up phone and continue using it

Managed to make them work already, thanks for the help bro.. appreciate it

I managed to work around the issue of bootloop bro, it had something to do with the kernal , I already flashed to magma and it is working now, how ever I was curious that each time when I restart the phone, it took a bit time to load up, like note 3 logo first, then magma note 8 logo, then after that it says optimizing apps and actually it shows around 240 apps or so, is it normal or is there any workarounds for the same? (How ever, boots up fine but boot up time is around 7-12 min approx)

Related

Cant install a Costum ROM

Greetings to everyone,
I would be happy if you can help me with a little problem on my Note 4.
For some reason I cant install a costum ROM on my Note 4 (N910F).
As soon as I have installed a ROM like NameLessROM the phone reboots, shows the Samsung logo for about 10 seconds, reboots, shows the logo, reboots, ...
Its the same thing happened to me once whileI tried to boot it with no system partition (wiped it)
I am using the newest TWRP.
Anyone got a solution?
Greetings
Robin
Sorry Robin for "hijacking" your thread but we're in the same boat
I'm having the exact same problem with my SM-N910F.
I've rooted the device using Odin3 and "CF-Auto-Root-trlte-trltexx-smn910f.tar.md5". This thread: http://forum.xda-developers.com/note-4/orig-development/sm-n910-cf-auto-root-t2897428
That went fine and I checked the root privillige afterwords with a terminal app on the phone. I issued the SU command and got at .....root#. Don't know if thats the right/best way to check it!
After rooting the phone I still had the stock recovery tool so again with Odin3 I installed "philz_touch_6.59.0-trlte.tar.md5".
This also went fine and I can now access "PhilZ Touch 6" recovery tool.
From here I've tried installing three different ROM's ("GlamourS6v3_1", "Super.Fast&LolliFamous™[S6+Style+v2][PART.4.0.]_BOC3" and "Super.Fast&LolliFamous_[.PART.6.0.]_BOD2") but keeps ending up with a phone that just keeps rebooting.
When I install the ROM I start with the "Clean to install a new ROM" option and after that install ZIP. The ROM's are located on my SD card.
The installation succed and when I reboot the phone just continues to reboot.
Any good advise?
Regards
John
You have to flash via odin the right modem and bootloader for the ROM that you're trying to install
mone, your a genius! Or maybe you just read the instructions more carefully than I did
I found the exact info and links in the ROM thread and everything is working now.
Thanks!
/John
RDieker201 said:
Greetings to everyone,
I would be happy if you can help me with a little problem on my Note 4.
For some reason I cant install a costum ROM on my Note 4 (N910F).
As soon as I have installed a ROM like NameLessROM the phone reboots, shows the Samsung logo for about 10 seconds, reboots, shows the logo, reboots, ...
Its the same thing happened to me once whileI tried to boot it with no system partition (wiped it)
I am using the newest TWRP.
Anyone got a solution?
Greetings
Robin
Click to expand...
Click to collapse
Okay for Nameless ROM to work on N910F you have to install the SimplKernel and need to update your bootloader and modem accordingly.
imladris said:
Sorry Robin for "hijacking" your thread but we're in the same boat
I'm having the exact same problem with my SM-N910F.
I've rooted the device using Odin3 and "CF-Auto-Root-trlte-trltexx-smn910f.tar.md5". This thread: http://forum.xda-developers.com/note-4/orig-development/sm-n910-cf-auto-root-t2897428
That went fine and I checked the root privillige afterwords with a terminal app on the phone. I issued the SU command and got at .....root#. Don't know if thats the right/best way to check it!
After rooting the phone I still had the stock recovery tool so again with Odin3 I installed "philz_touch_6.59.0-trlte.tar.md5".
This also went fine and I can now access "PhilZ Touch 6" recovery tool.
From here I've tried installing three different ROM's ("GlamourS6v3_1", "Super.Fast&LolliFamous™[S6+Style+v2][PART.4.0.]_BOC3" and "Super.Fast&LolliFamous_[.PART.6.0.]_BOD2") but keeps ending up with a phone that just keeps rebooting.
When I install the ROM I start with the "Clean to install a new ROM" option and after that install ZIP. The ROM's are located on my SD card.
The installation succed and when I reboot the phone just continues to reboot.
Any good advise?
Regards
John
Click to expand...
Click to collapse
If I''m not mistaken your phone model is N910F, if so you are flashing the incorrect ROMs as the ones you listed are for the exynos variant. So please look for ROMs in the correct thread "Galaxy Note 4 Android Development (Snapdragon)" And using PHilztouch recovery is not recommend and so I would advise you to install TWRP,
N910F = Trltexx
N910G = trltedt
Exynos:
N910C = treltexx

3 different custom ROMs won't install/boot, what else?

EDIT: Reposted to a more appropriate forum.
I tried installing several different ROMs onto my cursedAT&T phone (Note 3 N900A). I managed to downgrade to Android 4.4.2 and root the phone (from the current OEM-supplied OC3). I had different results for each ROM I tried:
cm-13-20151101-UNOFFICIAL-hlte.zip - Immediately produces a "failed" message trying to install from SafeStrap 3.75 hlteatt, because my phone is hlteatt and not hlte.
MagMa_NX_UX10_Ultimate_XDA.zip - Trying to install from Safestrap: progress bar freezes at 0% done.
RR-N-v5.8.2-20170309-hlte.zip - Installs successfully, but won't boot. First try reboot just stops on a black screen. 2nd reboot gives me the menu seen when booting with Vol Up + Home held down. (Is this the AT&T's firmware "bootloader?")
I used Safestrap to perform a Wipe of everything except my MicroSD card in the ROM Slot (#1) I was using before each ROM installation attempt. Any suggestions on getting any of these working? From reading other's experiences, it appears that some are successfully using some custom ROMs with this model phone.
In this forum its not normal to use Safestrap .
Custom roms are flashed as per the roms instructions generally via TWRP .
You should ask in the forum for your model .
Thanks. I reposted there and edited the original post here to say so.
u cant flash roms on safetrap, its only for flashing custpm recovery and then u flash custom rom
You may need to wipe the data partition to let roms boot properly on first boot

rr 7.1.2 without gapps/ recovery mode not possible

Hello xda developers this is my second thread sorry for the first one that i made yesterday, I am having a problem with my lenovo k4 note a7010a48
after rooting successfully I proceed to flash rr 7.1.2 but did not flash the gapps now my problem is how to go back on recovery mode to start over again
I already used the power button followed by the volume up down buttons but it is not working like before it is nougat. I only need to get to recovery mode. Please help and thankyou in advance. More power
Does u have root access now and which version of rr u flashed
yes the phone is rooted already and flashed with rr 7.1.2 only need to open recovery mode which is I have no idea
Contact in telegram app 9032015333 I will tell u
i dont know that or how to do that can you teach me please thank you
I have the same issue. Can't enter into recovery and the phone is unable to start.
Same Issue || Don't Know How To Fix
Hi,
I am searching for a possible solution from a day. But could not find a working solution.
After successfully flashing RR-N-5.8.5 (Android N)
Unable to go into recovery.
PROBLEM DESCRIPTION:
1. When Press Vol Up + Vol Down + Power Up
2. Recovery is not loading up
3. Instead it goes in boot loop
4. Normal boot mode and fast boot mode are working perfectly fine
SOLUTIONS TRIED:
1. Flashing recovery again using fastboot mode
2. Flashing different recovery, i.e updated version of recovery
As all recoveries which were available were for marshmallow version. I am not sure but have doubt as android version is updated so the kernel so do recovery also become obsolete in this case ?
Any help is welcome and appreciated
Thanks
---------- Post added at 05:18 PM ---------- Previous post was at 05:12 PM ----------
jaineshjain said:
Contact in telegram app 9032015333 I will tell u
Click to expand...
Click to collapse
Whole concept of this platform is sharing your knowledge
Don't you think it would be better if you discuss here itself ?
jaineshjain said:
Contact in telegram app 9032015333 I will tell u
Click to expand...
Click to collapse
Whole concept of this platform is sharing your knowledge
Don't you think it would be better if you discuss here itself ?
for fastboot mode and for recovery mode yes i tried it also but thats the problem no recovery mode. I will wait for the solution when it comes i will just store my phone for a while.
Hi Developers,
Is it possible to reset the phone at hardware level? I can't even connect the phone to PC as it keeps on rebooting.
Please note: upgraded to Nougat and wanted to do the second recovery as suggested by mohancm in the post. When the phone rebooted (before flashing the second recovery), the problem started.
Please let me know if any one has a fix/workaround for the issue.
Thanks,
Srihari
1.Download TWRP recovery unzip files.
https://drive.google.com/file/d/0B1CKVcdcbHFPUzFCODVMN0ZfTW8/view
2.Now in folder TWRP\img\ there is the file recovery.img.
3.Download the second recovery for nougat recovery-Nougat.img and put in the TWRP\img folder.
https://androidfilehost.com/?fid=673368273298981920
4.Rename it as the original, recovery.img and replace it.
5.Then connect your phone to usb and select the 3th option from usb debugging message
"Transfer photos(ptp)"
6.run TWRP_Install.bat from TWRP folder
And you are done, had the same problem and I figure this solution, hope it will help.
I cannot locate the transfer photos(ptp)
ok I already done the part I am now on the recovery mode thanks. new problem of mine is after flashing the rom gapps and recovery after reboot it goes back to recovery mode did I miss something on flashing?
ok so i already passed this problem thanks for the help xda community thank you very much but I have this bootloop problem maybe I did a mistake flashing before rebooting sorry i am a noob in this kind of upgrade specially in mobile phones. I will be careful next time after I passed this problem I hope you will help me once again, my phone in bootloop is killing me.
I have same issue... I flashed gapps and my phone is working smoothly... The issue is i can't go into recovery mode... I tried some one tap reboot to recovery apps but all whats happening is phone restarting normally.
For those who can't access recovery mode. You were supposed to flash updated recovery image after flashing rrn rom.
Enter into fastboot mode by using adb shell.
Flash the updated recovery image
Now try rebooting into recovery.
Should work.
Worst case, restore by flashing stock rom using SP flash tools. And then start all over again.
If you face any issues ping me. Even I had faced this issue and fixed it after a lot of struggle. I can try to help you.
Or you could download Official Twrp App directly from play store, then find A3000 (Air Row) in 'select device' and flash that to recovery, (if your phone is rooted) then you are good to go, go to recovery mode and thats all, your twrp is now has been flashed.
Thank me later??
MisledMew said:
Enter into fastboot mode by using adb shell.
Flash the updated recovery image
Now try rebooting into recovery.
Click to expand...
Click to collapse
This really worked for me. Many thanks man.
Well it got me some time to find the right recovery image for my ROM so I decided to give you link for anyone going through the same.
My configuration at that time was: DotOS 1.2 and TWRP 3.1.1 (or so).
On the DotOS thread was enclosed link to wrong recovery image file (or its version was changed as of 28.12.2018) but after small investigation I found this file recovery-mohan-N.img.
Note: This recovery worked for TWRP and Android Nougat and I'm not an expert to suggest this will work for your case either.
Thank you again and have a nice time
firelmnt said:
This really worked for me. Many thanks man.
Well it got me some time to find the right recovery image for my ROM so I decided to give you link for anyone going through the same.
My configuration at that time was: DotOS 1.2 and TWRP 3.1.1 (or so).
On the DotOS thread was enclosed link to wrong recovery image file (or its version was changed as of 28.12.2018) but after small investigation I found this file recovery-mohan-N.img.
Note: This recovery worked for TWRP and Android Nougat and I'm not an expert to suggest this will work for your case either.
Thank you again and have a nice time
Click to expand...
Click to collapse
Glad it helped

[Bootloop] N9005 not booting after frame (display) replacement

Hi,
as the title says, my phone is not booting anymore, after I transplanted the motherboard from a frame with a broken screen into a new frame (from china).
Abbreviations used:
RR => Resurrection Remix 5.8.5
CWM => ClockWorkMod Recovery 6.0.4.6-kitkat
TWRP => TeamWinRecoveryProject 3.2.1-1
I was using RR from the Rock Stable Setup on it before and it worked beautifully.
What happened:
I performed the mainboard-transplantation according to the iFixit guide
I held the power button to boot the phone:
It vibrated
It showed this screen for a couple of seconds
It vibrated
Back to step 1
And that until I removed power.
Then I tried to boot into recovery mode by holding the key combination on boot:
Same as above, but with this bootscreen
Then I tried to boot into download mode by holding the key combination on boot:
The warning to confirm download mode poped up and I got to see this screen.
I connected it to my PC and opened odin 3.09 and it recognized the device.
I tried to get adb and fastboot to see the device, but nothing worked. (In the old frame and before I broke the screen, it would be recognized at this stage)
I flashed TWRP with odin, odin showed the green "PASS!", but booting to recovery still failed.
I proceeded to flash a stock ROM, which had worked when I had issues with RR.
It worked, I went through the Android 5 setup process, enabled debug and connected adb.
adb saw the phone.
I rebooted to recovery and stock recovery booted correctly.
Sideloading anything with adb failed due to signature verification.
I then went back to download mode and flashed CWM successfully.
It now boots into recovery, but whenever I try to flash anything with CWM, it fails showing this screen
Or something similar (the photo comes from flashing RR 5.8.5)
I have both linux and windows properly setup and used both with adb, fastboot and odin (only windows)/heimdal (only linux).
I checked drivers and usb cables.
I opened the phone back up and checked all connections.
But I can't get any version of RR, CyanogenMod or LineageOS on there.
I've searched the internet, but people that have these kinds of problems after replacing parts of their phones, seem to only have driver issues or skipped steps in the manuals of custom ROM installations.
If you have any idea on what I could try or what I'm doing wrong or not doing, please leave an answer.
I'll keep this post updated below here:
(no updates, yet)
Thanks so much in advance
Simon
Your picture shows stock recovery not CWM .
Try flashing TWRP recovery through Odin .
I did flash TWRP and afterwards there was no recovery anymore.
When I flash CWM, I get the recovery shown in the photo.
The stock recovery has a black background and no touch controls for me.
What you saw must have been CWM.
Update: I can flash twrp-2.8.7.0-hlte-4.4.img.tar and it works. It's the only image that works, but I still can't boot into or flash any custom OS.
The only working OS I have at the moment is a stock android 5.0, which is not all that useful...
If anyone has an idea, why I can't or how I can find out what is causing it, please say so.
I can flash twrp-2.8.7.0-hlte-4.4.img.tar and it works. It's the only image that works, but I still can't boot into or flash any custom OS. )
What do you mean by ANY ??
Well, exactly that.
Regardless of what zip I flash, I end up with a bootloop.
If I flash a recovery zip, the recovery bootloops, but the OS still boots.
If I flash a custom ROM, I can still boot into recovery fine, but booting normally results in a bootloop.
The only way to get software onto my phone has been via odin and only an old CWM, Philz Touch, TWRP (Version 2.8.7.0 and below) and STOCK Android (Versions 4.3, 4.4.2, 5).
Anything else I have tried so far did not result in an error, but I couldn't boot into it either.
If you have ideas for software I can try flashing, please tell. I really have no idea how to get the damn thing to work again...
What happens when you flash correct stock rom via Odin ??
I mean that I can boot into it after flashing it via Odin.
But its terribly slow and bloated compared to ROMs like ResurectionRemix, so I don't want to use it.
AnyTimeTraveler said:
I mean that I can boot into it after flashing it via Odin.
But its terribly slow and bloated compared to ROMs like ResurectionRemix, so I don't want to use it.
Click to expand...
Click to collapse
In that case phone is OK .
Usual is that user is failing to follow instructions .
Not sure what you mean by fastboot on a N9005 .sounds like not a N9005 .
Personally with TWRP 2.8.70 i would be flashing something like .
https://forum.xda-developers.com/galaxy-note-3/development/rom-magma-nx-rom-t3508672
as its correct TWRP .
I am able to follow instructions.
Thank you very much.
I followed exactly the same procedure that has worked many times when switching between custom ROMs.
Also, the phone has a perfectly working version of Ressurection Remix installed at the time my frame broke and it did get stuck in the same bootloop after replacing the frame, even thogh the software was exactly the same.
I am looking for help analyzing the boot process and some way of capturing the kernel log when booting to determine where the error occures that traps the phone in a bootloop.
AnyTimeTraveler said:
I am able to follow instructions.
Thank you very much.
I followed exactly the same procedure that has worked many times when switching between custom ROMs.
Also, the phone has a perfectly working version of Ressurection Remix installed at the time my frame broke and it did get stuck in the same bootloop after replacing the frame, even thogh the software was exactly the same.
I am looking for help analyzing the boot process and some way of capturing the kernel log when booting to determine where the error occures that traps the phone in a bootloop.
Click to expand...
Click to collapse
Dear Mate..
Have you solved your problem? I have same problem after transplating N900 frame.
Sorry, I gave up, since I dearly needed a working phone and bought a OnePlus 3 cheaply from ebay second hand. It's been working like a charm and I threw the note into my museum after I softbricked it for the n-th time and couldn't get it out of a bootloop that didn't leave me time to go into Fastboot.
Sorry friend, but I can't help with this.
after reading a lot of similar threads, seems like the hardware is the cause of us not able to update to higher versions of twrp(& custom roms)

Bootloop after uninstalling Xposed + Firmware upgrade encountered issue

Hello,
I'm really desperate right now and would highly appreciate your help.
The background is the following:
several months ago I've flashed Cyanogenmod 13 on my Note 3 (N9005) using TWRP (via Odin). The system has been working perfectly. In addition, I was using Xposed (Version 89) without any problems. However I decided to uninstall Xposed today using its uninstaller, but I only got a error message ( I don't remember its content, it was saying something like ' can't rename... /lib'.
Well, I then tried uninstalling via recovery which resulted in a bootloop.
I watched some YT-videos explaining how to bypass Xposed in TWRP, so I went to download mode and tried installing the TWRP with stock_kernel_twrp_1120-signed-for_Odin (the file I used the first time). This step failed. After restarting my phone it's saying: 'Firmware upgrade encountered issue. Please select recovery mode in Kies & try again'.
I don't know what to do now. I simply want to install a working TWRP to save all my files and recover from the bootloop. What matters the most to me is to recover all data on the phone (videos, pictures, files etc. which unfortunately I haven't backed up).
I'm able to access download mode (home/power/volume down) but I don't know what to do to get a recovery/TWRP.
I'm not doing anything right to avoid further harm and wait for your advice. I'd be most grateful if you could help me.
Thanks in advance!
Exupery
exupery09 said:
Hello,
I'm really desperate right now and would highly appreciate your help.
The background is the following:
several months ago I've flashed Cyanogenmod 13 on my Note 3 (N9005) using TWRP (via Odin). The system has been working perfectly. In addition, I was using Xposed (Version 89) without any problems. However I decided to uninstall Xposed today using its uninstaller, but I only got a error message ( I don't remember its content, it was saying something like ' can't rename... /lib'.
Well, I then tried uninstalling via recovery which resulted in a bootloop.
I watched some YT-videos explaining how to bypass Xposed in TWRP, so I went to download mode and tried installing the TWRP with stock_kernel_twrp_1120-signed-for_Odin (the file I used the first time). This step failed. After restarting my phone it's saying: 'Firmware upgrade encountered issue. Please select recovery mode in Kies & try again'.
I don't know what to do now. I simply want to install a working TWRP to save all my files and recover from the bootloop. What matters the most to me is to recover all data on the phone (videos, pictures, files etc. which unfortunately I haven't backed up).
I'm able to access download mode (home/power/volume down) but I don't know what to do to get a recovery/TWRP.
I'm not doing anything right to avoid further harm and wait for your advice. I'd be most grateful if you could help me.
Thanks in advance!
Exupery
Click to expand...
Click to collapse
Flash TWRP 2.8.7.0 via ODIN.
if this works, then backup everything from recovery immediately.
here is the link (if you need).
https://forum.xda-developers.com/ga...ecovery-twrp-materialized-dark-light-t3153589
Now Flash a new kernel. look over here at xda for your need.
then reboot and check. pls have patience if it took long while first boot.
and pls tell if it works.
dark_phoenix said:
Flash TWRP 2.8.7.0 via ODIN.
if this works, then backup everything from recovery immediately.
here is the link (if you need).
https://forum.xda-developers.com/ga...ecovery-twrp-materialized-dark-light-t3153589
Now Flash a new kernel. look over here at xda for your need.
then reboot and check. pls have patience if it took long while first boot.
and pls tell if it works.
Click to expand...
Click to collapse
Thank you very much for your help.
I've just flashed twrp-2.8.7.0-hlte-4.4.img.tar successfully, but when trying to access recovery (volume up/home/power) it's stuck in the Samsung logo saying:
'RECOVERY BOOTING....
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery"
What to do now?
I've found different kernels:
https://forum.xda-developers.com/ga...nt/kernel-idlekernel-leankernel-fork-t3241582
and
https://forum.xda-developers.com/galaxy-note-3/development/temasek-kernel-t3395437
Which should I choose for N9005/Cyanogenmod 13? I have no idea due to lacking knowledge.
[Hlte][Purify][25.02.17][CM13.0]. sounds appropriate to me? Could you please give me an advice? Thank you!
Ok, flashing both twrp-2.8.7.0-ha3g.tar and then twrp-2.8.7.0-hlte-4.4.img.tar resulted in the herein before mentioned problem (stuck on Samsung logo).
I now flashed successfully n9005-cwm-recovery-6.0.4.4 and it's backed up everything.
I then tried uninstalling xposed via recovery with the uninstaller.zip on sdcard, but got this error message:
mv: can't rename '/system/lib/libart.so.o
rig': No such file or directory
E: Error in /data/media/0/Android/data/de.robv.android.xposed.installer/cache/downloads/framework/xposed-uninstaller-20180117-arm.zip
Any ideas how to fix it? Or do you recommend wiping everything and flashing a new ROM (e.g. MagMa NX ROM)?
exupery09 said:
Ok, flashing both twrp-2.8.7.0-ha3g.tar and then twrp-2.8.7.0-hlte-4.4.img.tar resulted in the herein before mentioned problem (stuck on Samsung logo).
I now flashed successfully n9005-cwm-recovery-6.0.4.4 and it's backed up everything.
I then tried uninstalling xposed via recovery with the uninstaller.zip on sdcard, but got this error message:
mv: can't rename '/system/lib/libart.so.o
rig': No such file or directory
E: Error in /data/media/0/Android/data/de.robv.android.xposed.installer/cache/downloads/framework/xposed-uninstaller-20180117-arm.zip
Any ideas how to fix it? Or do you recommend wiping everything and flashing a new ROM (e.g. MagMa NX ROM)?
Click to expand...
Click to collapse
ok.
you backed up your necessary data ?
if YES then go ahead and wipe everything and flash a new rom, which ever you want.
you know what. i am a huge fan of this dev.
here is this his work. awesome rom. give it a go.
https://forum.xda-developers.com/galaxy-note-3/development/rom-aspireteam-c9-pro-v2-0-t3610152
or this one if you don't want touchwiz .
https://forum.xda-developers.com/ga...-resurrection-remix-n-v5-8-3-vanilla-t3615227
---------- Post added at 10:43 AM ---------- Previous post was at 10:27 AM ----------
exupery09 said:
Thank you very much for your help.
I've just flashed twrp-2.8.7.0-hlte-4.4.img.tar successfully, but when trying to access recovery (volume up/home/power) it's stuck in the Samsung logo saying:
'RECOVERY BOOTING....
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery"
What to do now?
I've found different kernels:
https://forum.xda-developers.com/ga...nt/kernel-idlekernel-leankernel-fork-t3241582
and
https://forum.xda-developers.com/galaxy-note-3/development/temasek-kernel-t3395437
Which should I choose for N9005/Cyanogenmod 13? I have no idea due to lacking knowledge.
[Hlte][Purify][25.02.17][CM13.0]. sounds appropriate to me? Could you please give me an advice? Thank you!
Click to expand...
Click to collapse
FOR THIS ONE ....
i think you need to pull battery out just after successfully flashing TWRP 2.8.7.0
when ODIN flashes recovery and says passed. pull out battery immediately. don't let the phone boot/start. wait 10-20 seconds. re-insert battery and try now booting in TWRP.

Categories

Resources