Related
Hi All,
New to forum here and to Android *re-engineering* in general. Wife gave me a task: to remove the stock S4 OS and replace it with something better.
These are the steps I followed:
1. In Download mode, used Odin v3.10 to flash TWRP 3.02 recovery
2. Booted to Recovery Mode, it gets to TWRP recovery ROM properly.
3. Recovered to CM13 nightly builds and rebooted to System.
4. Boots to System with the following message:
KERNEL IS NOT SEANDROID ENFORCING
Set Warranty Bit: kernel
Samsung Galaxy S4
GT-I95016
After that it just stays stuck on the screen until I reboot into Download or Recovery Mode.
None of the CM13 OS downloads I used work so far. I've also tried to recover to CM11 after the initial problem, but it doesn't work. Note that there are no releases for this, only nightly builds. Tried for 2 weeks already and I think I probably need some help.
Any ideas?
zdfan said:
Hi All,
New to forum here and to Android *re-engineering* in general. Wife gave me a task: to remove the stock S4 OS and replace it with something better.
These are the steps I followed:
1. In Download mode, used Odin v3.10 to flash TWRP 3.02 recovery
2. Booted to Recovery Mode, it gets to TWRP recovery ROM properly.
3. Recovered to CM13 nightly builds and rebooted to System.
4. Boots to System with the following message:
KERNEL IS NOT SEANDROID ENFORCING
Set Warranty Bit: kernel
Samsung Galaxy S4
GT-I95016
After that it just stays stuck on the screen until I reboot into Download or Recovery Mode.
None of the CM13 OS downloads I used work so far. I've also tried to recover to CM11 after the initial problem, but it doesn't work. Note that there are no releases for this, only nightly builds. Tried for 2 weeks already and I think I probably need some help.
Any ideas?
Click to expand...
Click to collapse
The message during boot is normal if you've modified the Bootloader (in this case, by flashing the recovery).
By "recover" I assume you mean installed/flashed a ROM.
Are you flashing the right ROM for the model?
Did you wipe before flashing?
GDReaper said:
The message during boot is normal if you've modified the Bootloader (in this case, by flashing the recovery).
By "recover" I assume you mean installed/flashed a ROM.
Are you flashing the right ROM for the model?
Did you wipe before flashing?
Click to expand...
Click to collapse
Thanks for replying - ok good to know that message is normal.
1. Yes I flashed the TWRP recovery ROM.
2. In TWRP recovery mode I installed the custom ROM for cyanogenmod 13 for i9506, downloaded from the Builds in this link: __download.cyanogenmod.org/?device=ks01lte___ (copy paste the URL as I cannot post external URL yet)
3. Yes, wiped before flashing.
zdfan said:
Thanks for replying - ok good to know that message is normal.
1. Yes I flashed the TWRP recovery ROM.
2. In TWRP recovery mode I installed the custom ROM for cyanogenmod 13 for i9506, downloaded from the Builds in this link: __download.cyanogenmod.org/?device=ks01lte___ (copy paste the URL as I cannot post external URL yet)
3. Yes, wiped before flashing.
Click to expand...
Click to collapse
How much time did you wait for the phone to boot?
Have you tried other ROMs, from here on the forum?
There is a GT-I9506 section from where you can download various modified ROMs.
GDReaper said:
How much time did you wait for the phone to boot?
Have you tried other ROMs, from here on the forum?
There is a GT-I9506 section from where you can download various modified ROMs.
Click to expand...
Click to collapse
1. Waited up to 1/2 hr, same screen.
2. I've tried CM11 and CM13
3. Could you give an example?
zdfan said:
1. Waited up to 1/2 hr, same screen.
2. I've tried CM11 and CM13
3. Could you give an example?
Click to expand...
Click to collapse
I'm a GT-I9505 user, can't really recommend you anything.
There's AICP, various CM13 builds and others. Just look through the GT-I9506 section (here on the forum) until you find something promising.
Hey guys, first of all sorry about my english, im french.
So my problem is: I tried rooting my Axon 7 A2017U many times, with different guides. I always end up with a softbricked phone, having to restore to stock using MiFlash.
My bootloader is unlocked, i have stock recovery and stock rom for now.
Whenever i flash TWRP, either the signed one (from @tenfar) or unsigned (and up to date) ones, i can't go past the menu saying something like "your phone cant be checked for corruption, please lock your phone [...]" it just freeze. i did read somewhere that i should flash chainfire's root or a special .zip that, i guess, disabled some check that could prevent booting a phone with unsigned stuff/edited system (after flashing TWRP, so it could boot) that didn't work out. i think i found that information in some LineageOS thread here on XDA.
My ultimate goal would be to get a rooted stock nougat 7.1.1, up to date TWRP recovery and to be able to switch to LineageOS to try it out soon.
For what it is worth, i rooted many phones over the years, so while i'm no expert, i should be able to follow most of the steps you give me.
Thanks alot!
What version of TWRP did you flash first?
I have the same root problem i can not install in twrp install in twrp ok but su application displays no root cause i have latest twrp
KwesiJnr said:
What version of TWRP did you flash first?
Click to expand...
Click to collapse
this
https://forum.xda-developers.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715
And @tenfar's signed one
KwesiJnr said:
What version of TWRP did you flash first?
Click to expand...
Click to collapse
this
https://forum.xda-developers.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715
And @tenfar's signed one
Okay. Download and flash this one alone via fastboot and see what happens. This is one the I personally use. It is required for any of the newer versions to work properly.
twrp-3.0.2-2-a2017u.img
You can choose to rename it to just recovery.img, then:
1. fastboot flash recovery recovery.img
or
2.
if you choose to work with the same filename:
fastboot flash recovery twrp-3.0.2-2-a2017u.img
Select reboot to recovery from the bootloader menu now and try again.
Either way, should work fine. I know you mentioned you knew the basics, but just want to be sure.
Also forgot to mention. If TWRP works but you still can't get your phone to boot, you need to follow this guide here
You can start from the part that says:
-----------------------------------------------------
UPDATING FROM B20_Boot / B20 / B27 / B29 / B15(N)
-----------------------------------------------------
Again, that's the ROM I personally use if I want to go back to stock, not the one from the ZTE site.
Gonna try it and give feedback. thanks for taking time to help!
edit: im downloading the rom from the link you shared.
like you said, i can get TWRP to boot but not the phone.
So if i use full stock from ZTE, it can't boot with modified recovery?
edit 2: i don't know what worked, i think it might be the bootstack. or the rom by DrakenFX. now i can boot to the rom with a TWRP recovery installed. It worked, but i soft bricked again trying to flash SuperSU. So now i'm retrying with an updated TWRP.
I haven't tried that yet, but I really suspect that's the reason you're having problems. I rarely use pure stock ROMs. Like you, I'm not an expert in Android Development so I can't tell you why. Just been a flashaholic for years so made a few observations.
Which supersu are you installing? If you're swiping to the right in twrp, you need to install the dm-verity zip or supersu 2.79. There's some issues with newer builds.
Everything is working like a charm! Now im going to finally give lineageOS a try
I used Chainfire's SuperSU 2.79 stable.
Edit : Everything is working flawlessly! I'm running the lastest LineageOS nightly with root (Chainfire's 2.79). Followed their instruction and installation was smooth as butter. I should also point out i flashed the lastest official TWRP which seems more stable than the one @KwesiJnr suggested. The one he suggested was giving me some "can't read X partition" in red text everywhere in the log section, which the official one doesn't do. It was doing his job properly anyway though.
I can't thank @KwesiJnr enough, it helped me find the single mistake i was making.
lololo2 said:
Everything is working like a charm! Now im going to finally give lineageOS a try
I used Chainfire's SuperSU 2.79 stable
Click to expand...
Click to collapse
Glad you're up and running root. :good:
lololo2 said:
Everything is working like a charm! Now im going to finally give lineageOS a try
I used Chainfire's SuperSU 2.79 stable.
Edit : Everything is working flawlessly! I'm running the lastest LineageOS nightly with root (Chainfire's 2.79). Followed their instruction and installation was smooth as butter. I should also point out i flashed the lastest official TWRP which seems more stable than the one @KwesiJnr suggested. The one he suggested was giving me some "can't read X partition" in red text everywhere in the log section, which the official one doesn't do. It was doing his job properly anyway though.
I can't thank @KwesiJnr enough, it helped me find the single mistake i was making.
Click to expand...
Click to collapse
Yeah, like I mentioned before that was the base TWRP you needed to flash first, before any of the newer ones. You weren't intended to use it indefinitely.
There's a lot of Dev love for our device now and support is growing ... exciting new ROMs cropping up. Don't hesitate to try them out.
Hello dear Community!
It is depressing that my first appearance here is to ask for help, but I am going crazy.
So, I tried to Root my phone via Odin + CF Autoroot klte and it seemed to have been a success.
The root checker also said, that my device was rooted so I went on and installed TWRP to be able to install Lineage OS.
After getting Lineage to work I got a few error messages suddenly popping up, telling me that either "Music had stopped" or other android operation were closed because they didn't work properly.
I tried to install Gapps, it seemed to have worked but I was only able to open and enter the store once, afterwards the store never managed to load and then the app closed itself after starting it.
So I checked again with Root Checker, but this time it gave me an error message, too. It said, that my device was not rooted properly.
I guess this is were I made it worse by deciding to just root the phone again. Obviously, it didn't work either.
Afterwards I thought that maybe installing The Original Android OS and then unrooting the phone would be the best solution to be able to start anew.
First I tried to flah Lineage again and that made it impossible for me to boot the phone. The farthest I got was the setup page, were it tells you Hello and were you can choose a Language, but clicking the arrow key didn't do anything at all.
The recovery mode was also not the TWRP one anymore, but the original Android one and that was a huge problem for me.
Then I tried to flash the 6.1 OS for the S5 (I made sure it was the correct version), but now it is stuck at the "Samsung" screen while it boots.
It never boots though.
I don't know what to do anymore.
Please, I beg you, could anyone help me out?
Don't flash the latest Lineage OS ROM
Hello AsylumAlice u shouldn't have flashed the latest Lineage OS ROM because now u will need a new motherboard for your S5 since the ROM corrupts the MMC chip now u will need to get a new MMC chip or a new Motherboard sorry that your s5 is now hard bricked but when u get it fixed flash the DreamUX S8 Rom it works flawless on my S5 SM-G900i
Yours Sincely
Matty Bourke
mattybourke1994 said:
Hello AsylumAlice u shouldn't have flashed the latest Lineage OS ROM because now u will need a new motherboard for your S5 since the ROM corrupts the MMC chip now u will need to get a new MMC chip or a new Motherboard sorry that your s5 is now hard bricked but when u get it fixed flash the DreamUX S8 Rom it works flawless on my S5 SM-G900i
Yours Sincely
Matty Bourke
Click to expand...
Click to collapse
What are the grounds for your claims?
You needn't root via CF-autoroot if your end goal was to flash lineage. CF autoroot was intended to root stock roms with ease and less effort.
Flash The LATEST, official TWRP via odin then do a FULL WIPE. Wipe system, data, cache and dalvik cache.
From here on, you have two options:
1.) Sideload the LineageOS rom via ADB
2.) Transfer it to the phone's storage via MTP and flash it from TWRP.
As for how to accomplish this, the forum search bar and Google has your back. You need only choose one procedure.
If you need the Play Store, flash gapps AFTER flashing LINEAGE AND BEFORE REBOOTING.
Since you were under the idea that utilizing CF-autoroot was a necessity, I suggest that you re-read this post thoroughly before actually putting it into practice.
Kinloch said:
What are the grounds for your claims?
You needn't root via CF-autoroot if your end goal was to flash lineage. CF autoroot was intended to root stock roms with ease and less effort.
Flash The LATEST, official TWRP via odin then do a FULL WIPE. Wipe system, data, cache and dalvik cache.
From here on, you have two options:
1.) Sideload the LineageOS rom via ADB
2.) Transfer it to the phone's storage via MTP and flash it from TWRP.
As for how to accomplish this, the forum search bar and Google has your back. You need only choose one procedure.
If you need the Play Store, flash gapps AFTER flashing LINEAGE AND BEFORE REBOOTING.
Since you were under the idea that utilizing CF-autoroot was a necessity, I suggest that you re-read this post thoroughly before actually putting it into practice.
Click to expand...
Click to collapse
Thank you so much for your fast reply!
-> I flashed the newest Version for klte via Odin, but I can't get into the boot mode.
I only am able to enter the download mode. What can I do now?
Flash TWRP via odin again, untick the Auto-Reset option of Odin first. Then try booting to recovery via long holding the power, home and volume up button simultaneously without releasing any of the buttons until you successfully see the TWRP splash screen.
If that still doesn't work, reboot to recovery via adb from download mode. You need the adb and the usb drivers for your device.
If that still doesn't work, you might have flashed an incompatible version of TWRP.
Kinloch said:
Flash TWRP via odin again, untick the Auto-Reset option of Odin first. Then try booting to recovery via long holding the power, home and volume up button simultaneously without releasing any of the buttons until you successfully see the TWRP splash screen.
If that still doesn't work, reboot to recovery via adb from download mode. You need the adb and the usb drivers for your device.
If that still doesn't work, you might have flashed an incompatible version of TWRP.
Click to expand...
Click to collapse
Thank you so much, it worked perfectly!
I can now start my phone and use it normally.
But the Root Checker still says:
"Sorry! Root access is not properly installed on this device.
Device: SM-G900M
Android version: 7.1.2"
What should I do from now on?
Thank you so much for your help (agaiN).
And as for why I used the auto-root, well I just followed a guide that I found, it only had positive reviews so I assumed it was a correct tutorial.
AsylumAlice said:
Thank you so much, it worked perfectly!
I can now start my phone and use it normally.
But the Root Checker still says:
"Sorry! Root access is not properly installed on this device.
Device: SM-G900M
Android version: 7.1.2"
What should I do from now on?
Thank you so much for your help (agaiN).
And as for why I used the auto-root, well I just followed a guide that I found, it only had positive reviews so I assumed it was a correct tutorial.
Click to expand...
Click to collapse
just flash supersu in twrp
AronFerr said:
just flash supersu in twrp
Click to expand...
Click to collapse
I thought about doing that, but wasn't sure how exactly to proceed and what Version to install.
I downloaded SuperSU v.2.82 and put it on my internal storage.
Just install over TWRP the same way that I Installed Lineage and Gapps I suppose?
I guess if it doesn't work out, I just follow the steps from above again and retry?
Thank you so much. I feel like in idiot in this situation.
AsylumAlice said:
I thought about doing that, but wasn't sure how exactly to proceed and what Version to install.
I downloaded SuperSU v.2.82 and put it on my internal storage.
Just install over TWRP the same way that I Installed Lineage and Gapps I suppose?
I guess if it doesn't work out, I just follow the steps from above again and retry?
Thank you so much. I feel like in idiot in this situation.
Click to expand...
Click to collapse
yes just flash it but no wipes
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)
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.