Related
Greetings, all. I'm a big fan of using Xposed modules for my phone, especially YouTube Adaway but since I upgraded via kdz to 5.0.2 this evening I can't get Xposed to run even after reboot using the apk found in the Xposed lollipop thread. I tried to check the log files to be able to post the output here but it won't read those either. Has anyone been able to get this to work and if so, how? Any help is greatly appreciated as the main reasons I root is for ad blocking and titanium backup
lerner17 said:
Greetings, all. I'm a big fan of using Xposed modules for my phone, especially YouTube Adaway but since I upgraded via kdz to 5.0.2 this evening I can't get Xposed to run even after reboot using the apk found in the Xposed lollipop thread. I tried to check the log files to be able to post the output here but it won't read those either. Has anyone been able to get this to work and if so, how? Any help is greatly appreciated as the main reasons I root is for ad blocking and titanium backup
Click to expand...
Click to collapse
Did you flash the zip on the thread also?
I did not
krchi said:
Did you flash the zip on the thread also?
Click to expand...
Click to collapse
My bootloader is still locked so to my knowledge there's not a way to flash a zip without a custom recovery (TWRP, CWM and the like). Maybe I read the thread wrong and you had to both flash the zip and install the apk
Edit: Yes, that is correct, I read it wrong. The zip must be flashed for the framework to install. Is there a way to flash a zip without a custom recovery? This is the first phone I've had with a locked bootloader, all the other ones I just installed a recovery from here and ran/modded it
lerner17 said:
My bootloader is still locked so to my knowledge there's not a way to flash a zip without a custom recovery (TWRP, CWM and the like). Maybe I read the thread wrong and you had to both flash the zip and install the apk
Edit: Yes, that is correct, I read it wrong. The zip must be flashed for the framework to install. Is there a way to flash a zip without a custom recovery? This is the first phone I've had with a locked bootloader, all the other ones I just installed a recovery from here and ran/modded it
Click to expand...
Click to collapse
The L90 of D415 has a unlocked bootloader by deafult, I never unlocked mines and flashed recovery, Just flash this http://forum.xda-developers.com/lg-l90/development/recovery-twrp2-7-1-0lgl90w7xxshoxx-t2826150 using Flashify, download the img and open Flashify and select flash recovery then select that image and in that app you should be able to reboot to recovery to flash the xposed zip. Since I've never tried it I dont know how well xposed runs on stock lollipop remember to backup.
krchi said:
The L90 of D415 has a unlocked bootloader by deafult, I never unlocked mines and flashed recovery
Click to expand...
Click to collapse
Thank the gods for that then! I am leaving tomorrow on a trip and need my phone fully functional for the duration (hooray GPS) so just to be safe I'm going to hold off on flashing the custom recovery until I get back on Monday and will also flash the Xposed framework then as well and report back. Thanks for the help! I will update this thread after flashing just in case others are looking for this to say whether or not it worked.
Hello,
I was able to get xposed running well on 5.0.2. However i didnt flash stock kdz, I flashed a modified stock ROM found in the development section (see http://forum.xda-developers.com/lg-l90/development/rom-l90-d415-lollipop-xtreme-v1-0-4-25-t3092813)
After flashing the ROM as described in the link above, i rebooted to recovery. I then flashed the xposed zip file. After that, I wiped cache and dalvik cache (VERY IMPORTANT to avoid any storage errors). Finally I did a normal boot, and it installed perfectly. Hope this helps! Best of luck my friend
Sorry for late response
Turns out my boot loader was in fact unlocked. TWRP through Flashify and then install the zip through there, then install the apk and reboot again. Thank you both so much for the information!
Correction
lerner17 said:
Turns out my boot loader was in fact unlocked. TWRP through Flashify and then install the zip through there, then install the apk and reboot again. Thank you both so much for the information!
Click to expand...
Click to collapse
While Xposed installed and worked it also soft bricked my phone in that I kept getting "unfortunately com.android.phone stopped working". Not sure if it's the program itself or the fix memory leak module I installed. Thankfully I had a backup right before I flashed that zip and it appears my phone is working again. Not sure if I will try to install it again without the memory leak patch or not. Thoughts?
lerner17 said:
While Xposed installed and worked it also soft bricked my phone in that I kept getting "unfortunately com.android.phone stopped working". Not sure if it's the program itself or the fix memory leak module I installed. Thankfully I had a backup right before I flashed that zip and it appears my phone is working again. Not sure if I will try to install it again without the memory leak patch or not. Thoughts?
Click to expand...
Click to collapse
Sadly, this also led me to restore my stock, modded KK backup. What I found to be a temporary fix is to wipe cache/data for the phone apk as well as the SIM Toolkit, then reboot. It appears fixed for some time, but then reappears. This problem seems to arise whenever you use wifi or mobile data, and goes away when you switch them off (at least that was my experience).
I think that the main culprit is the Xposed framework itself. I was told by others it's not fully compatible on stock LP for the L90, but still tried it either way. I got too many mods I like to not use Xposed, so I rolled back to kk. If you can live w/o Xposed then try LP with no framework and see what happens. Best of luck!
jbonilla51 said:
I think that the main culprit is the Xposed framework itself. I was told by others it's not fully compatible on stock LP for the L90, but still tried it either way. I got too many mods I like to not use Xposed, so I rolled back to kk. If you can live w/o Xposed then try LP with no framework and see what happens. Best of luck!
Click to expand...
Click to collapse
How sad I will continue to monitor the Xposed threads then to see if/when it's fully functional with stock Lollipop.
I was in panic mode with my phone yesterday not working because it happened right when my car decided to also quit working so I saw those possible fixes as well and neither worked. Thankfully I backed up through TWRP right before I flashed the Xposed zip so that save my butt,
Hi guys Recently Samsung released 5.1.1 for our devices! So I decided to make a easy tutorial on how to install TWRP on our devices (unfortunately without root).
1. Download newest odin from Here!
2. Reboot to download mode.
3. Download this file TWRP RECOVERY
4.Flash it with AP option.
5. Done! Now You should be able to boot into TWRP Recovery.
Info
Can I restore my previous custom rom now?
Yes and no. I tried restoring two roms. AOSP and TW, aosp had a bootloop then successfully booted, and TW didn't seem to boot at all.
Does it root my device/Can I root my device now?
Nope, not yet. I tried to make a custom rom with root built in but it was stuck in a bootloop.
Why would I need this?
Well. Now You can restore Your rom, and flash other roms(Some may fail due to a newer bootloader).
Any bugs?
Sometimes first boot after flashing this recovery might bootloop, but just remove Your battery and turn on Your phone again.(Happened only once to me)
Click to expand...
Click to collapse
Yes... I did manage to restore the backup image of 5.1 as I ended up in bootloop while trying for the root access. So far OK with at least TWRP is working.
I have a question, If I'm on 5.1.1 and I've installed this TWRP, By using this TWRP RECOVERY, can I install 5.0.1 custom rom via zip file?
I do not mean to restore my backup rom. I mean I do a fresh installation
vodanhdaisu said:
I have a question, If I'm on 5.1.1 and I've installed this TWRP, By using this TWRP RECOVERY, can I install 5.0.1 custom rom via zip file?
I do not mean to restore my backup rom. I mean I do a fresh installation
Click to expand...
Click to collapse
Some people have reported issues flashing a 5.01 rom without using odin to downgrade first
Sent from my SM-N910C using Tapatalk
vodanhdaisu said:
I have a question, If I'm on 5.1.1 and I've installed this TWRP, By using this TWRP RECOVERY, can I install 5.0.1 custom rom via zip file?
I do not mean to restore my backup rom. I mean I do a fresh installation
Click to expand...
Click to collapse
It seems to bootloop roms that need 5.0 bootloader. But AOSP rom that runs on 5.1.1 boots up without any problems. Just during boot You might see message "kernel is not seandroid enforcing" and then the rom should boot up.
I flashed twrp via odin and it says pass then reboot after that when i try to enter recovery it get me to stock recovery any clue why is that and how to solve this ? v.v
Thanks a ton bro.
thank u so much guys
Not working
Hi there
I have tried it several times but didn´t work. It always come back to stock recovery. My N910C is on 5.1.1 non rooted.
Any hint ?
jefflryb said:
Hi there
I have tried it several times but didn´t work. It always come back to stock recovery. My N910C is on 5.1.1 non rooted.
Any hint ?
Click to expand...
Click to collapse
Just after installation goes into recovery mod before starting.. Do not let the phone boot
Thanks
Recovery & Kernel not seandroid reinforcing
Hi after i installed the custom recovery whenever i boot up and see the boot screen a red text shows up the top left corner of the screen that says recovery or kernel not seandroid reinforcing. Please help.
Which version of twrp is this?
after installing via of in twrp it fails to come up all I get is the standard recover
Hi I could really use some help here my phone had some trouble so I had to wipe it out and reinstall the 5.1.1 lollipop when I did so however I lost the recovery partition I was using TW RP I have since tried to reinstall it and Odin says that it is successful yet when I try to boot into the recovery partition I get to default recovery partition that comes with the phone I've also tried using the CWM recovery image and it does the same thing says its successful but I can't boot into it because it boots into the default one any idea what is going on and what I can do. I should also note that I've tried reinstalling the 5.0.1 version of lollipop and that has failed in Odin any ideas would be greatly appreciated because at the moment I have no way to root my phone I can't flash the custom kernel that's needed for 5.1.1 or anything else for that matter please help thank you
jereny.taylor6969 said:
Hi I could really use some help here my phone had some trouble so I had to wipe it out and reinstall the 5.1.1 lollipop when I did so however I lost the recovery partition I was using TW RP I have since tried to reinstall it and Odin says that it is successful yet when I try to boot into the recovery partition I get to default recovery partition that comes with the phone I've also tried using the CWM recovery image and it does the same thing says its successful but I can't boot into it because it boots into the default one any idea what is going on and what I can do. I should also note that I've tried reinstalling the 5.0.1 version of lollipop and that has failed in Odin any ideas would be greatly appreciated because at the moment I have no way to root my phone I can't flash the custom kernel that's needed for 5.1.1 or anything else for that matter please help thank you
Click to expand...
Click to collapse
Easiest way on odin is make sure auto reboot is unchecked. When its done unplug the cable pull the battery put it back in boot into twrp Let me know how it works out for you.
azizski said:
I flashed twrp via odin and it says pass then reboot after that when i try to enter recovery it get me to stock recovery any clue why is that and how to solve this ? v.v
Click to expand...
Click to collapse
keep pressing vol up + home + power as soon as u press start button............in odin
Should this be in any conflict with the kernel with http://forum.xda-developers.com/note-4/development/n910c-kernel-5-1-1-stock-tw-permissive-t3206548 ? When I try to use both, i end up in a bootloop
Backup please help
Guys do you have a Back-Up?a backup of lollipop 5.1.1 a backup from twrp can i have back up or any just a backup from recovery mode because my firmware 5.1.1 wont work the only that i know that works is a backup from recovery mode can someone give me a backup pleaseee thank you . sorry for my bad english :3
aejaz_ally said:
keep pressing vol up + home + power as soon as u press start button............in odin
Click to expand...
Click to collapse
This one worked. Thanks!
So last time my phone was stuck on the device name and model number screen. I solved that issue by flashing TWRP using Odin.
but now the phone would not go past the boot screen no matter what I do. I re-flashed CM11 4 times now, factory reseted and wipe cache and dalvik cache. What should I do?
1. change your thread title please. Need help is not really helpful or directs to your issue.
2. what version of TWRP are you using? The official TWRP 2.8.7.0 does not work. Too long to explain why's that. To fix this issue there are some solutions if you flashed the faulty recovery:
- flash Stock ROM again and stay on TWRP 2.8.5.0
- some users fixed this issue by just flashing another recovery or just flashing a stock based custom rom to get their phone working. You still need to change recovery.
In my case I had to flash stock again and flash my preferred recovery again to get my phone working.
maultasche said:
1. change your thread title please. Need help is not really helpful or directs to your issue.
2. what version of TWRP are you using? The official TWRP 2.8.7.0 does not work. Too long to explain why's that. To fix this issue there are some solutions if you flashed the faulty recovery:
- flash Stock ROM again and stay on TWRP 2.8.5.0
- some users fixed this issue by just flashing another recovery or just flashing a stock based custom rom to get their phone working. You still need to change recovery.
In my case I had to flash stock again and flash my preferred recovery again to get my phone working.
Click to expand...
Click to collapse
So I should flash TWRP 2.8.5.0 and flash CM11 again? (because I don't have stock rom for S3 LTE)
Where can I get stock rom fro S3 LTE I can't seem to find it all, I find is firmwares.
Also, a few questions
1) If I give it into my phone carrier (Optus) would they know that it is rooted?
2) If they know it is rooted and with a custom rom and don't fix it for free is it possible to get it fixed by paying money??
The firmware provided by Samsung is the stock ROM I'm talking about
No, since you tried to flash a ROM through the faulty recovery you need to flash either official firmware from Samsung or a custom ROM based on Samsung stock like AMCHA or N4 Elite. I'd recommend to go with official Samsung firmware. After that go to stock recovery (it will come when you flash official firmware), do a factory reset and let the phone boot once. After that you can flash TWRP 2.8.5.0 and flash any ROM you want.
The new recovery from TWRP is too big for the S3. The S3 recovery is a little over 8MB, the new one needs more and messes up partitions etc. You won't be able to mount /system, /data and the recovery can't read your internal partitions as it should. Go with the way I provided. It seems like a lot of work but it's done in a few minutes.
For your two questions: yes and yes. But you can fix that on your own and don't need your operator or Samsung to get your phone fixed.
Thanks a lot for helping. I was scared to death cause if something happened I would've had to start using a old brick Nokia phones
Is it possible that after I flash the stock firmware, my phone still doesn't boot up?
I am basically a level above newbie, so I don't get what is happening. I see tutorials and do what they tell me to do. sometime I get what I am doing sometime I don't
as i said, after flashing stock, go into the recovery and do a factory reset. The phone will boot then
maultasche said:
as i said, after flashing stock, go into the recovery and do a factory reset. The phone will boot then
Click to expand...
Click to collapse
Ok sorry for doubting you! My phone is working now, thanks a lot for your help
Glad it's working now, you're welcome
I have rooted my s3 via odin and now i wont to flash twrp via flashify. Now i have a bootloop on my s3. How can i recover the phone. i am a noob on s3 and i don*t know how i could go into fastbootmode. Please help me.
what S3 do you have? Which recovery did you flash?
maultasche said:
2. what version of TWRP are you using? The official TWRP 2.8.7.0 does not work. Too long to explain why's that. To fix this issue there are some solutions if you flashed the faulty recovery:
- flash Stock ROM again and stay on TWRP 2.8.5.0
- some users fixed this issue by just flashing another recovery or just flashing a stock based custom rom to get their phone working. You still need to change recovery.
In my case I had to flash stock again and flash my preferred recovery again to get my phone working.
Click to expand...
Click to collapse
I had this problem too! Flashed stock rom, then flashed TWRP 2.8.5.0 (I was using 2.8.7.0) and then flashed cyanogenmod 12 and boom it booted and worked!
Thank you very much!
Hello guardians of the Android Phones. I ran into a major issue while updating from 5.1.1 custom ROM to 6.0.1 that I found on this thread : http://forum.xda-developers.com/tmo...20t-android-6-0-1-marshmallow-update-t3356838
Steps I took:
1) Upgraded TWRP to 3.0.2.0 (3.0.2.1 doesn't work properly on my device. it flashes the TWRP 3 logo and then goes black) ... So I ended up re-installing TWRP 2.8.7.2 and then flashed TWRP 3.0.2.0
2) Copied the ROMS of choice to the SDCARD
3) Using Odin 3.10.7 I flashed using Twisted Sixx Custom ROM (which didn't work correctly due to the bootloader not being Marshmallow 6.0.1 compatible) from my understanding of what i've read through these threads.
4) Flashed the AP using G920TUVU3EPD1_G920TTMB3EPD1_G920TUVU3EPD1_HOME.tar.md5
Now i'm 100% locked out from downgrading Stock or Custom ROMS. TWRP can no longer be installed.
Having a feeling I used a Bear Trap ROM.
What do I do? Feeling like throwing this out the window. *sigh*.
Thanks ahead of time... anything to point me in the right direction would be greatly appreciated.
I am not a dev... but I tried smartswitch, perhaps it can help you. Hopefully you didn't do factory reset.
Try that and then if it doesn't work, again, wait for the experts.
What is SmartSwitch? Do you have a URL or THREAD with information and download links?
Thanks for the tip.
britchel said:
I am not a dev... but I tried smartswitch, perhaps it can help you. Hopefully you didn't do factory reset.
Try that and then if it doesn't work, again, wait for the experts.
Click to expand...
Click to collapse
I did an Odin flash of EPF1 and didn't lose the ability to flash recovery. I have not yet tried downgrading. I would take a deep breath, drink a beer or two, and go back through things step by step. At this point I would suggest using Odin to flash a complete image, perhaps of a different version, and go from there.
ninjadroids said:
What is SmartSwitch? Do you have a URL or THREAD with information and download links?
Thanks for the tip.
Click to expand...
Click to collapse
http://www.samsung.com/us/smart-switch/assets/downloads/Smart_Switch-PC_setup.exe
Hey can u reboot to recovery and to download mode?
You need to be in download mode to use smart-switch
Here's another tread alike to yours....
http://forum.xda-developers.com/tmo...rick-wont-boot-successful-odin-flash-t3435751
Smiles on the beer or two!
Are you using the G920T also? Which image did you Odin flash with? Do you have the direct link? I do like your idea of flashing with a different 6.x image variant as opposed to downgrading.
socal87 said:
I did an Odin flash of EPF1 and didn't lose the ability to flash recovery. I have not yet tried downgrading. I would take a deep breath, drink a beer or two, and go back through things step by step. At this point I would suggest using Odin to flash a complete image, perhaps of a different version, and go from there.
Click to expand...
Click to collapse
Yes I can reboot into recovery and to download mode. Thank you for the link.
britchel said:
http://www.samsung.com/us/smart-switch/assets/downloads/Smart_Switch-PC_setup.exe
Hey can u reboot to recovery and to download mode?
You need to be in download mode to use smart-switch
Here's another tread alike to yours....
http://forum.xda-developers.com/tmo...rick-wont-boot-successful-odin-flash-t3435751
Click to expand...
Click to collapse
ninjadroids said:
Smiles on the beer or two!
Are you using the G920T also? Which image did you Odin flash with? Do you have the direct link? I do like your idea of flashing with a different 6.x image variant as opposed to downgrading.
Click to expand...
Click to collapse
I don't unfortunately - Google is your friend. Some firmwares that come to mind are DOJ7, DOJC, and COF6.
But first: Is your bootloader locked? If you have not yet unlocked it, that may be a problem. I unlocked mine as soon as I got my phone (and yes I'm on a G920T). A locked bootloader may prevent downgrading although it should not prevent a rescue Odin of the same or newer firmware.
Yes it's locked.
Is there a way to unlock it while maintaining my current image?
All those firmware are 5.x
I'm stuck on unlocked Marshmallow 6.0.1
And according to Smart Switch. I'm one version down from latest with it prompting to upgrade.
I'm going to hold off on that for the moment...
If you flashed edp1, you are far from latest.
Lemme know if i am wrong at anything
If you can access download and recovery, that means the phone is in a bootloop when booting up..
Since you flashed the edp1 firmware, your bootloader must have been updated so now you can only use mm roms.
As for recovery, is it stock or twrp?
Also when in download modex whats your system status - stock or custom?
Well if EDP1 is far from latest, then that is great news. I can boot into my firmware. It's for sure stock as far as I can tell.
Download mode output:
RED: ODIN MODE
PRODUCT NAME: SM-G920T
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
FAP LOCK: OFF
BLUE: Secure Download: Enabled
Knox Warranty Void: 1 (I tripped it when rooting it in 5.x)
AP SWREV: B:3 K:2 S:2
It won't let me get into TWRP after flashing it... when I try it says the following:
RED: "RECOVERY IS NOT SEANDROID ENFORCING"
It doesn't matter which version of TWRP I attempt to flash with.
Thanks!
danveer said:
If you flashed edp1, you are far from latest.
Lemme know if i am wrong at anything
If you can access download and recovery, that means the phone is in a bootloop when booting up..
Since you flashed the edp1 firmware, your bootloader must have been updated so now you can only use mm roms.
As for recovery, is it stock or twrp?
Also when in download modex whats your system status - stock or custom?
Click to expand...
Click to collapse
Did you flashed root or anything after you tried to flash recovery via odin?
Also when you flashed edp1, phone still didnt boot?
Edp1 is about the march or april update i think
The next main update is epf1 because it restricts going back futher
Then there came a update 5 days ago.. just a security update... havent flashed that coz i am rooted..
Anyways lets concentrate on edp1
Since its a mm rom, going back to 5.1 roms means a bootloop, so ill suggest not doing that
Also after flashing the mm rom, if you flash anything over it, you wont be able to boot a system because a new dm verity check mm has introduced.. to bypass it, you either need to flash a mm root file or a kernel that can disable the check.
I was stuck at the same thing since i Flashed recovery and that failed the checks so was getting bootloops..
I was able to go in recovery and download mode but not boot up..
Since you have a custom status, it can be a reason for bootloops
http://forum.xda-developers.com/gal...y-official-twrp-galaxy-s6-edge-t3354508/page8
The phone boots. I just cannot get root. I guess I don't understand the terminology regarding "bootloops" or "MM" ... I attempted a APK root... which failed. And still using my previous kernel unless flashing the custom ROM overwrote that.
So I can login to the phone and connect it to USB and sideload APK files, no problem. I just cannot TWRP flash properly and enter it using the UP recovery mode. And when I tried flashing other ROMS in Download recovery mode either ODIN crashes or it gives me a NAND WRITE error.
Which root and / or kernel files would you suggest to me to flash in ODIN to break this protection that's preventing a full root on this image? Or would it be preferable in my situation to find a different ROM and resolving the ODIN crash problem to achieve a full 6.x marshmallow root?
Thanks again! Greatly appreciated Sir.
danveer said:
Did you flashed root or anything after you tried to flash recovery via odin?
Also when you flashed edp1, phone still didnt boot?
Edp1 is about the march or april update i think
The next main update is epf1 because it restricts going back futher
Then there came a update 5 days ago.. just a security update... havent flashed that coz i am rooted..
Anyways lets concentrate on edp1
Since its a mm rom, going back to 5.1 roms means a bootloop, so ill suggest not doing that
Also after flashing the mm rom, if you flash anything over it, you wont be able to boot a system because a new dm verity check mm has introduced.. to bypass it, you either need to flash a mm root file or a kernel that can disable the check.
I was stuck at the same thing since i Flashed recovery and that failed the checks so was getting bootloops..
I was able to go in recovery and download mode but not boot up..
Since you have a custom status, it can be a reason for bootloops
http://forum.xda-developers.com/gal...y-official-twrp-galaxy-s6-edge-t3354508/page8
Click to expand...
Click to collapse
ninjadroids said:
The phone boots. I just cannot get root. I guess I don't understand the terminology regarding "bootloops" or "MM" ... I attempted a APK root... which failed. And still using my previous kernel unless flashing the custom ROM overwrote that.
So I can login to the phone and connect it to USB and sideload APK files, no problem. I just cannot TWRP flash properly and enter it using the UP recovery mode. And when I tried flashing other ROMS in Download recovery mode either ODIN crashes or it gives me a NAND WRITE error.
Which root and / or kernel files would you suggest to me to flash in ODIN to break this protection that's preventing a full root on this image? Or would it be preferable in my situation to find a different ROM and resolving the ODIN crash problem to achieve a full 6.x marshmallow root?
Thanks again! Greatly appreciated Sir.
Click to expand...
Click to collapse
Which odin are you using?
Try 3.10.7 because using older odin on mm gives that nand write error...
That could explain a lot of things
I'm using 3.10.7 latest.
danveer said:
Which odin are you using?
Try 3.10.7 because using older odin on mm gives that nand write error...
That could explain a lot of things
Click to expand...
Click to collapse
http://forum.xda-developers.com/che...rite-start-fail-odin-soluction-t2851096/page5
Try this thread..
It has solutions when nand write fails...
Also trying a different verion pf odin might work like 3.10.6 or another maybe
ninjadroids said:
Yes it's locked.
Is there a way to unlock it while maintaining my current image?
All those firmware are 5.x
I'm stuck on unlocked Marshmallow 6.0.1
And according to Smart Switch. I'm one version down from latest with it prompting to upgrade.
I'm going to hold off on that for the moment...
Click to expand...
Click to collapse
EPD1 and EPF1 are 6.0.1 Marshmallow.
@ninjadroids:
Take this as you will but reading back through this thread gives me the impression that you lack the necessary know-how to customize your phone. I highly suggest you leave it stock for the time being until you know EXACTLY what you are doing.
My reasons for saying this:
-In your first post you state that "using Odin 3.10.7 I flashed using Twisted Sixx Custom ROM". To my knowledge there are NO custom ROMs designed to be flashed via Odin. They are in .zip files, to be installed via recovery ONLY.
-This is actually my mistake - the G920T bootloader does not have a lock function; flashing a custom recovery will simply trip the e-fuse and render it Knox 0x1 warranty void.
-You are not familiar with what Odin images are for the G920T, or what version they are. You should NEVER flash ANYTHING via Odin unless you are absolutely sure it is intended for your specific device.
-In the 9th post you state your bootloader is unlocked (again I apologize for the confusion) but in the 3rd line you say you're on unlocked Marshmallow. I'm going to assume you have limited knowledge of what the bootloader, the recovery, download mode, and system are.
-You mention seeing the red "RECOVERY IS NOT SE ANDROID ENFORCING". This is an error message generated by the bootloader saying the recovery is custom and did not pass the security check...but it is also completely normal. I get it every single time I go into TWRP...which works just fine.
-You do not understand what "MM" means when all of us including you are talking about Marshmallow.
-You do not understand what a "bootloop" is. For the sake of education, a bootloop is exactly what it sounds like - your device gets stuck in a loop while booting. This is generally mentioned when it is persistent - the device does not complete the boot process, coming to a stable useable Android interface. This is indicative of several possible problems; most likely you did something incorrectly, causing the boot process to halt, in which case the phone restarts itself to attempt to boot again, hence the loop.
-You do seem to understand sideloading via ADB and I'll give you credit for that. But when using the button combo (Vol Up+Home+Pwr) to boot into recovery, you WILL boot into recovery...whether that is stock recovery or TWRP. Some reboots may prevent this; if in doubt, hold Vol Down+Home+PWR until the screen shuts off; immediately go to Vol UP while still holding Home and Power.
-In the 13th post you ask about flashing kernels via Odin. Firstly: custom ROM .zips contain the kernel intended to work with that ROM. There is no need to flash anything separately. I am a little fuzzy on how root is accomplished on stock Marshmallow; it used to be we could flash SuperSu via recovery, but now there is talk about systemless...Anyway, I will reiterate what I was saying about Odin: DO NOT USE IT unless you know EXACTLY what you are doing. You have the potential to turn your phone into an expensive paperweight.
I am not trying to put you on blast or criticize you; I'm trying to help you avoid bricking your phone. There are a lot of things that could go wrong; you shouldn't be messing with something you don't understand, especially if you don't know how to fix it if something goes wrong.
For now even i am confused as to what is causing error.
Its probably that his storage is not curropt causing namd write fail..
I would recommend doing a backup. since you can turn on a phone, connect it to pc and move the important files and contacts to it.
Then download stock rom via sam mobile and do a clean install..
Ill prefer pf1 because, if memory serves right, edp1 had that notorious auto brightness bug.. If odin is not helping then try smart switch.
Boot up system, see if everything is working..it should be fresh as new.
After that follow the instructions as to flash twrp from the link i gave in one of my previous posts.. twrp should now flash...( i dont see any reason it shouldnt )
Flash root via recovery, or a custom rom you wanna flash but make sure its a 6.0.1 one ( xtre sto lite or alexis recommended )
That should root your phone too...
P.s. mm -> short for MarshMallow
Bootloop, when all you see is samsung logo which comes during boot... it wont go past that.. you never reach your lock screen or are able to unlock your phone... as mentioned in detail by -> socal
Flashing any rom overwrites kernel so if you flashed edp1, you are now on stock kernel...
P.p.s when you said sideload apk.. was it via adb shell or simply installing apk from internal memory of phone?
You answered a lot of my questions in that last post. Thank you kindly.
socal87 said:
EPD1 and EPF1 are 6.0.1 Marshmallow.
@ninjadroids:
Take this as you will but reading back through this thread gives me the impression that you lack the necessary know-how to customize your phone. I highly suggest you leave it stock for the time being until you know EXACTLY what you are doing.
My reasons for saying this:
-In your first post you state that "using Odin 3.10.7 I flashed using Twisted Sixx Custom ROM". To my knowledge there are NO custom ROMs designed to be flashed via Odin. They are in .zip files, to be installed via recovery ONLY.
-This is actually my mistake - the G920T bootloader does not have a lock function; flashing a custom recovery will simply trip the e-fuse and render it Knox 0x1 warranty void.
-You are not familiar with what Odin images are for the G920T, or what version they are. You should NEVER flash ANYTHING via Odin unless you are absolutely sure it is intended for your specific device.
-In the 9th post you state your bootloader is unlocked (again I apologize for the confusion) but in the 3rd line you say you're on unlocked Marshmallow. I'm going to assume you have limited knowledge of what the bootloader, the recovery, download mode, and system are.
-You mention seeing the red "RECOVERY IS NOT SE ANDROID ENFORCING". This is an error message generated by the bootloader saying the recovery is custom and did not pass the security check...but it is also completely normal. I get it every single time I go into TWRP...which works just fine.
-You do not understand what "MM" means when all of us including you are talking about Marshmallow.
-You do not understand what a "bootloop" is. For the sake of education, a bootloop is exactly what it sounds like - your device gets stuck in a loop while booting. This is generally mentioned when it is persistent - the device does not complete the boot process, coming to a stable useable Android interface. This is indicative of several possible problems; most likely you did something incorrectly, causing the boot process to halt, in which case the phone restarts itself to attempt to boot again, hence the loop.
-You do seem to understand sideloading via ADB and I'll give you credit for that. But when using the button combo (Vol Up+Home+Pwr) to boot into recovery, you WILL boot into recovery...whether that is stock recovery or TWRP. Some reboots may prevent this; if in doubt, hold Vol Down+Home+PWR until the screen shuts off; immediately go to Vol UP while still holding Home and Power.
-In the 13th post you ask about flashing kernels via Odin. Firstly: custom ROM .zips contain the kernel intended to work with that ROM. There is no need to flash anything separately. I am a little fuzzy on how root is accomplished on stock Marshmallow; it used to be we could flash SuperSu via recovery, but now there is talk about systemless...Anyway, I will reiterate what I was saying about Odin: DO NOT USE IT unless you know EXACTLY what you are doing. You have the potential to turn your phone into an expensive paperweight.
I am not trying to put you on blast or criticize you; I'm trying to help you avoid bricking your phone. There are a lot of things that could go wrong; you shouldn't be messing with something you don't understand, especially if you don't know how to fix it if something goes wrong.
Click to expand...
Click to collapse
Wonderful. Thanks man. I will be attempting a Stock ROM Odin flash and go from there. I will update my progress. Thank you all very much for the answered questions and pointing me in the right direction. Hopefully this thread will prove useful for anyone who is attempting to deal with a G920-T and attaining root the proper way for Marshmallow 6.x
danveer said:
For now even i am confused as to what is causing error.
Its probably that his storage is not curropt causing namd write fail..
I would recommend doing a backup since you can turn on a phone
Then downloading stock rom via sam mobile and do a clean install...if odin is not helping doing that then try smart switch.
Boot up system, see if everything is working..
After that follow the instructions as to flash twrp from the link i gave in one of my previous posts.. twrp should now flash...( i dont see any reason it shouldnt )
Flash root via recovery, or a custom rom you wanna flash vut make sure its a 6.0.1 one ( xtre sto lite or alexis recommended )
That should root your phone too...
Click to expand...
Click to collapse
So I tried installing Xposed Framework by flashing it's ROM, but after I did it, I rebooted my phone, but every time I do it, it always boots into TWRP recovery. I tried fixing it by looking in the setting and I used a backup I made before doing all this crap and I restored, but my phone still boots only into TWRP recovery mode. I would really appreciate it if anyone could help me. Thanks.
PS. My phone is rooted and it has TWRP
TribalPaint said:
So I tried installing Xposed Framework by flashing it's ROM, but after I did it, I rebooted my phone, but every time I do it, it always boots into TWRP recovery. I tried fixing it by looking in the setting and I used a backup I made before doing all this crap and I restored, but my phone still boots only into TWRP recovery mode. I would really appreciate it if anyone could help me. Thanks.
PS. My phone is rooted and it has TWRP
Click to expand...
Click to collapse
Is it possible that you used the wrong Xposed for your device or SDK version? I can't imagine that restoring a backup didn't fix it. Did you try wiping system in TWRP first?
Things you can try:
- Flash the "Xposed Uninstaller" zip file in TWRP, which should always be on your device when you are flashing new versions of Xposed.
- Reflash TWRP in Odin. This should fix a recovery loop.
- Wipe system, data, dalvik, cache in TWRP, then try restoring your backup.
- As a last resort, you can download the latest stock firmware for your device from the sammobile site, flash it in Odin, let it boot once, reflash TWRP, wipe in TWRP and restore your backup (if you were running a custom rom you liked or something), then flash the correct Xposed for your device & android version.
Hope this helps!
Sent from my SM-N920T using Tapatalk
bogarty said:
Is it possible that you used the wrong Xposed for your device or SDK version? I can't imagine that restoring a backup didn't fix it. Did you try wiping system in TWRP first?
Things you can try:
- Flash the "Xposed Uninstaller" zip file in TWRP, which should always be on your device when you are flashing new versions of Xposed.
- Reflash TWRP in Odin. This should fix a recovery loop.
- Wipe system, data, dalvik, cache in TWRP, then try restoring your backup.
- As a last resort, you can download the latest stock firmware for your device from the sammobile site, flash it in Odin, let it boot once, reflash TWRP, wipe in TWRP and restore your backup (if you were running a custom rom you liked or something), then flash the correct Xposed for your device & android version.
Hope this helps!
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
Hello. I already tried zipping the uninstaller for xposed but it did nothing, I also tried wiping dalvik cache and all, but no luck. I also think that my backups are just not functional. Now I'm left to just reflashing TWRP and if that doesn't work I'll have to flash the original stock firmware for my phone. I have spent already 2 days with constant searching for ways to fix my phone and not being able to do other things because this has been taking up my time and my patience, so I really appreciate every bit of fixing my phone that I get. Since I am new to all this I would be very grateful if you could send me the links to the correct files for my device and also give me a tutorial on what to do. As I appreciate any support, so I'm thankful for you helping me But until then my device is still not able to boot regulary but rather boots to TWRP
TribalPaint said:
Hello. I already tried zipping the uninstaller for xposed but it did nothing, I also tried wiping dalvik cache and all, but no luck. I also think that my backups are just not functional. Now I'm left to just reflashing TWRP and if that doesn't work I'll have to flash the original stock firmware for my phone. I have spent already 2 days with constant searching for ways to fix my phone and not being able to do other things because this has been taking up my time and my patience, so I really appreciate every bit of fixing my phone that I get. Since I am new to all this I would be very grateful if you could send me the links to the correct files for my device and also give me a tutorial on what to do. As I appreciate any support, so I'm thankful for you helping me But until then my device is still not able to boot regulary but rather boots to TWRP
Click to expand...
Click to collapse
Also, if I try to reflash TWRP, do I have to reflash the original firmware first, or I can just go straight ahead and just reflash TWRP?
TribalPaint said:
Also, if I try to reflash TWRP, do I have to reflash the original firmware first, or I can just go straight ahead and just reflash TWRP?
Click to expand...
Click to collapse
Update:
I fixed my phone, and here's what I did, so if anyone is new here with the same issue I had, I hope this can help you. So first of all as I said I kept booting to TWRP, later I tried reflashing TWRP, but I remembered that I missed something in ODIN, so I just pulled the cord and my screen after rebooting just said something along the lines of "An unexpected error occurred while updating software, please recover using Samsung Smart Switch." after that, I tried Samsung Smart Switch, but it was no luck for me, so then I used the last resort. I went on sammobile.com, I searched stock firmware for the exact model I had and then I checked the stock firmware that was available. Since I'm from Latvia, I picked the Baltic region, then I downloaded the latest stock firmware. After a long time, I downloaded the file, and I checked the instructions on how to flash it, I flashed the stock firmware, and then my problem was fixed, my phone was working again and now I have Android 7.1.1 as I used to have Android 6.0.1 and I had ZERO file loss However as you flash the stock firmware, TWRP get "flashed" out and same with root if you have it, and in that case if you want TWRP and root again, I highly suggest Meziani's YoutTube channel, because he gives simple and working tutorials on how to do it I'm glad if this helped anyone.