So I flashed the Alliance Rom for my t-mo Note 4 and all I get is the boot logo.
I've gone through with Odin and the CF auto root junk, used TWRP to wipe and flash this rom.
I got TWRP on there, but I can't seem to put any files onto my phone. Like I select mount, and when I try to drag a file over, windows wont let me.
You see, I've got this error, and it says Kernel is Not SEandroid enforcing. I have looked for a fix, and people say that I need to flash a file called stocK_kernel, which I have.
I can't get this file onto the device it seems. Anyone have any ideas of what is going on?
EDIT: tried flashing another rom using odin and now all i get the t-mobile logo...
and I can't register for sammobile because I can't pass the captcha !! It's frustrating... I can't download what I think I need >_>
Any help would be awesome
I know this is a typical problem, I've been around XDA for a while, but never made an account until I decided to actually root and try to flash my device.
DaltonMplz said:
So I flashed the Alliance Rom for my t-mo Note 4 and all I get is the boot logo.
I've gone through with Odin and the CF auto root junk, used TWRP to wipe and flash this rom.
I got TWRP on there, but I can't seem to put any files onto my phone. Like I select mount, and when I try to drag a file over, windows wont let me.
You see, I've got this error, and it says Kernel is Not SEandroid enforcing. I have looked for a fix, and people say that I need to flash a file called stocK_kernel, which I have.
I can't get this file onto the device it seems. Anyone have any ideas of what is going on?
EDIT: tried flashing another rom using odin and now all i get the t-mobile logo...
and I can't register for sammobile because I can't pass the captcha !! It's frustrating... I can't download what I think I need >_>
Any help would be awesome
I know this is a typical problem, I've been around XDA for a while, but never made an account until I decided to actually root and try to flash my device.
Click to expand...
Click to collapse
A ROM using ODIN? Which one? If it's Lollipop...and you are on the T-Mobile logo screen, how long did you wait? It takes ~10 minutes to boot. But, if you are on the Samsung screen, there is a problem. So, I'm currently thinking you are not waiting long enough?
Try putting your rom in the extsd or internal and flash from there.
I would grab the stock firmware and flash that using Odin. Don't forget to factory reset using stock recovery after flashing stock firmware.
Just start over.
Then root and install twrp, once your back at square one, then put your rom of choice on either of the SD locations and flash using twrp.
A bootloop after flashing a rom is usually, in my experience, a kernel issue. So it couldn't hurt to have an alternate compatible kernel to flash if you need it.
If you have TWRP all is not lost. If you flashed the stock ROM then you probably don't have TWRP anymore. Its just about impossible to wreck this phone by flashing ROMs. I would ODIN to the stock COD6 build. I believe there is a thread with all the files you need in one zip. Follow those instructions and it should get you back to stock rooted and you can go from there with flashing ROMs again.
Sent from my SM-T900 using XDA Free mobile app
No the rom doesn't use Odin. But I imagine the person had to root and flash a custom recovery as well. The rom of course had to be flashed in recovery.
Related
I decided to root my phone and try some ROMS last night on my Captivate. Love it by the way except one problem that I can not seem to figure out.
Before I did any flash I used ROM Manager to take 2 backups of my stock ROM and also used Titanium to backup all user apps and data.
Everytime I try to go back to stock and the phone reboots after recovery mode I get the AT&T logo and it never goes anywhere.
How do I get back to stock?
THANK!
If you are trying to restore stock through nancroid backup that won't work. You need to use odin.
What build is your phone? You can find it under your battery, something between 1006-1012
It is 1012. I thought you could just restore from those backups to get back to stock.
I have never used odin before. How do I go about that?
Thanks!
I can not find a good download for Odin. Could somebody provide please?
Thanks!
With your build you need to be careful what odin you use
You wavy to follow this
http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36
Clockwork does not restore kernel and modem. You are stuck at at&t screen because your system is ext 4 used on roms, and your nandroid is rfs. Long and short it won't work
So.... I am a bit confused now. Is there even a way to get back to stock at this point?
The link I posted
Your stock is jh7, odin One click is jf6. The procedure laid out in the link will get you back to jh7, although it takes a couple steps.
As long as you can get into recovery you can probably reflash any rom you have on your sd
Yikes thats a tall order to get back. Thought it would be more simple. So it is easy getting to a point to flash ROMS... Not so easy going back.
I'm also stuck in the same vicious cycle as we type.
I got 2 different stock rom backups and a cognition backup and can't get nothing to restore factory. I got premium ROM Manager. I can get into 2 different recovery screens. 1 from the Clockwork v2.5.1.3-voodoo lagfix and 1 using the update.zip on my root. Can't restore anything that gets me past the ATT logo.
ChokeD said:
I'm also stuck in the same vicious cycle as we type.
I got 2 different stock rom backups and a cognition backup and can't get nothing to restore factory. I got premium ROM Manager. I can get into 2 different recovery screens. 1 from the Clockwork v2.5.1.3-voodoo lagfix and 1 using the update.zip on my root. Can't restore anything that gets me past the ATT logo.
Click to expand...
Click to collapse
What is your build number, under battery
Between 1006-1012
I don't see a 1006-1012 anything. Where exactly would it be listed under the battery ??? ON the battery ? my phone is 3 days old.
EDIT: oh I think its a 1010 ...I think I found it
Thanks for the help by the way.
Link listed earlier in thread
Yeah it is the same for me.... Sucks!
And I can not download any of the files in that link because I am at work and those hosting sites are blocked for us. :-(
larryroberts said:
Yeah it is the same for me.... Sucks!
And I can not download any of the files in that link because I am at work and those hosting sites are blocked for us. :-(
Click to expand...
Click to collapse
Have you tried this
Phone off
Hold volume up and down and power
Let go when at&t comes up
Should be green recovery
Select install zip from sd
Choose zip
Select rom file that is saved on your sd, any you may of tried
Confirm
If your lucky maybe you can flash the rom
Uhh ??? Somehow from the recovery mode I just re-installed Cognition 3.04 back on my phone by browsing to the ROM.zip an installing it. I have to charge my phone for a few but I'll definitely come back and tell how I did it after a while. I think it was by browsing to cognitionv3.zip from 1 of the recovery menus insead of going to the update.zip. That beats the hell out of going through all the steps of going back to stock.
Thanks for the help.
EDIT:
Yeah somewhat like above post, only I had the Cognition (red) recovery menu and I went to install .zip and browsed to the cognitionv3.zip on my sd and installed it. *BLAM* back to Cognitionv3.04 I'll work with that till I got more time to mess with the other.
mcord11758 said:
Have you tried this
Phone off
Hold volume up and down and power
Let go when at&t comes up
Should be green recovery
Select install zip from sd
Choose zip
Select rom file that is saved on your sd, any you may of tried
Confirm
If your lucky maybe you can flash the rom
Click to expand...
Click to collapse
Yep I have tried that. Or at least I guess....
I go into the recovery screen but the problem is the only zip files I have are my custom ROMS. I did a complete backup with ROM Manager of the stock ROM before flashing however it did not create a zip file, it created a folder which contains everything that was backed up. I have tried to restore from that but when I do and the phone restarts it sticks on the AT&T white logo screen.
I am not saying restore stock, I am saying flash a rom. it may get you a working phone
Oh yeah I have done that just fine. I am using Cognition.
I am just trying to find my path back to stock.
mcord11758 said:
I am not saying restore stock, I am saying flash a rom. it may get you a working phone
Click to expand...
Click to collapse
Exactly, If you flashed a ROM on the phone the ROM is still there. Just use the recovery mode and choose "install a zip from sd" then go to "choose a zip from sd" then it will let you browse the sd for the .zip(rom) you just had. (not stock). It should be successful. Worked for me.
At least you will have a working phone and you can then look into going stock once you've read up a little more on it.
Just trying to help.
EDIT: oh, OK, I myself was in a panic and had just found that possible.
No problem. Thank you for the help!
I was thinking that when I did the backup with ROM Manager that it was creating a ROM version of the stock so I could flash back. Guess not though.
Hi all, I could really really use some help.
Today I decided to try and flash CM9 RC2 and I seem to have messed up big time.
I startred by rooting, using Dr Ketan's guide. That all went smoothly, and root was working.
I put the CM9 zip file on the SD card, turned off my phone, got back into CWM recovery, and most tutorials recommended, selected full data wipe... this is where something seemed to go wrong. While perfoming the data wipe, it seemed to freeze. I let it sit for a while, hoping it would sort itself out, but it didn't, and then it rebooted itself and went into a boot loop.
I can't get back into recovery mode, but I can get into download mode. So I thought the best thing to do would be to flash a stock firmware using odin.
I downloaded the latest german LRG firmware (which I was on before I started) from Sammobile, connected my phone to odin, selected the MD5 file, and pushed start. Again, this is where I got stuck. It just hangs on Nand write start. I've tried this twice now, and it gets stuck at the same stage (about 90% finished)
I have no idea what to do now and really need help. I'm not a total n00b, or at least I thought I wasn't, but I seem to have gotten in way over my head. What should I do?
Edit: see you tried already...
Sent from my GT-N7000 using xda app-developers app
This is classical case of super brick.
You should not hav to wipe on ics. I think u must be on stock kernel. Every corner you may see warning, wiping and reset on ics can brick device, but its unfortunate you didn't notice it.
Anyway check your flash counter is zero and send it to service.centre to claim ur warranty.
If u running out of warranty, fing.a link for 'how to revice bricked note from my signature. And try it.
Edit : i wud like to know, as you said u went to cwm recovery, so at the time of wiping you wr on which kernel?
Sent from my GT-N7000 using xda premium
purple zebra said:
Hi all, I could really really use some help.
Today I decided to try and flash CM9 RC2 and I seem to have messed up big time.
I startred by rooting, using Dr Ketan's guide. That all went smoothly, and root was working.
I put the CM9 zip file on the SD card, turned off my phone, got back into CWM recovery, and most tutorials recommended, selected full data wipe... this is where something seemed to go wrong. While perfoming the data wipe, it seemed to freeze. I let it sit for a while, hoping it would sort itself out, but it didn't, and then it rebooted itself and went into a boot loop.
I can't get back into recovery mode, but I can get into download mode. So I thought the best thing to do would be to flash a stock firmware using odin.
I downloaded the latest german LRG firmware (which I was on before I started) from Sammobile, connected my phone to odin, selected the MD5 file, and pushed start. Again, this is where I got stuck. It just hangs on Nand write start. I've tried this twice now, and it gets stuck at the same stage (about 90% finished)
I have no idea what to do now and really need help. I'm not a total n00b, or at least I thought I wasn't, but I seem to have gotten in way over my head. What should I do?
Click to expand...
Click to collapse
Hi Bud,
From your predicament, first let me tell you what you have done wrong.... You mentioned you're in LRG Rom already and you wanted to flash CM9 after that.... right?
Well, I guess the process you did was totally wrong. You have to download stock GB N7000(from Dr. Ketan's thread) and using that stock GB Rom, that is the time you can install AbysNote kernel to root and install CWM on your phone. Now after that, download mobile ODIN (from google playstore) and flash the CM9 from there.
THAT's the one you should have done before. Remember, there are no easy way of jumping ROMS especially if your already in ICS... IF YOU WANT TO FLASH TO ANOTHER ICS ROM.
My rule of law would be to downgrade first to STOCK GB and from there, ROOT, install CWM and mobile ODIN and that'll be the time you can flash already to the new ICS ROM of your choice.
So here's what your going to do. Since your still able to boot in download mode, Download any stock GB ROM and flash it using PC ODIN. After that, seee if you can bootup your Note already to STOCK GB ROM. If and If you are able to already, then download a clean kernel preferably Abyss Kernel and flash it with your STOCK GB so that you can gain root and have CWM installed. From there, download Mobile Odin pro and flash the CM9 (that you ultimately want to be installed on your Note)
Hope everything's going to be fine and Good luck bud! :fingers-crossed:
Cheers!
Hello, I know its been several days, but I just wanted to update on the situation.
Thank you SO much to Dr.Ketan for pointing me in the right direction. A combination of these 2 guides (http://forum.xda-developers.com/showthread.php?t=1661590&page=2 http://forum.xda-developers.com/showthread.php?t=1667886) has managed to help me repartition my internal memory and get up and running again. I've got a stock gingerbread rom running, and all seems to be well.
I realise I was very stupid to do a wipe on an ICS kernal. I read about the problem for 1 particular Kernal back in may, and hadn't read the updates since, and so didn't realise it effected EVERY ICS kernal since then. It's my own stupid fault for not re-reading the warnings. Let this be a lesson kiddies, a little bit of knowledge is a dangerous thing.
Again, thank you so much for the help, to all involved, you are an asset to the community!
Hi guys, having some serious issues with my Tab. It's the Telstra GT-P7320T.
So I had it rooted and flashed with the glitkis kernel all working fine still on the standard Telstra version of honeycomb. Then when their update for ICS finally came out (after nearly 6 months of knocking it back) I went to update it in the normal manner, not thinking it would have a hissy fit with the root and the custom kernel.
So after it downloaded it did its pre install bit, it rebooted, but then loaded into CWM recovery, and thats where its stayed. I've tried factory resets, clearing and formatting all the caches (davlik, system etc) i've used adb to push a few different roms and kernels etc to the device but nothing ive tried has worked. I flashed arlics ics rom, but it still just boots into recovery. Ive tried flashing the stock kernel and stock recovery but when i try to install zip from sd them they fail "install aborted (bad)"
Anyone got any ideas on what process and files I should try? Ive searched up and down the forum trying different methods for fixing soft brick and returning to stock but to no avail.
Cheers
ragvaror said:
Hi guys, having some serious issues with my Tab. It's the Telstra GT-P7320T.
So I had it rooted and flashed with the glitkis kernel all working fine still on the standard Telstra version of honeycomb. Then when their update for ICS finally came out (after nearly 6 months of knocking it back) I went to update it in the normal manner, not thinking it would have a hissy fit with the root and the custom kernel.
So after it downloaded it did its pre install bit, it rebooted, but then loaded into CWM recovery, and thats where its stayed. I've tried factory resets, clearing and formatting all the caches (davlik, system etc) i've used adb to push a few different roms and kernels etc to the device but nothing ive tried has worked. I flashed arlics ics rom, but it still just boots into recovery. Ive tried flashing the stock kernel and stock recovery but when i try to install zip from sd them they fail "install aborted (bad)"
Anyone got any ideas on what process and files I should try? Ive searched up and down the forum trying different methods for fixing soft brick and returning to stock but to no avail.
Cheers
Click to expand...
Click to collapse
hey mate,
i was just caught out by this last night. all you need to do is re-flash on a stock rom with ether oden of heimdall and youre good to go. im sure there is a oden flashable rom on these forums
take it sleazy!
Cheers mate,
Ive been trying to reflash a stock rom by pushing it to the sd card and installing it, but when i go to install it from recovery it tells me the rom file is bad and aborts, like its corrupt or something, so maybe i need to find some different downloads to try. Thanks, there's hope still at least, lol. I'll find the odin file and try doing it that way.
ragvaror said:
Cheers mate,
Ive been trying to reflash a stock rom by pushing it to the sd card and installing it, but when i go to install it from recovery it tells me the rom file is bad and aborts, like its corrupt or something, so maybe i need to find some different downloads to try. Thanks, there's hope still at least, lol. I'll find the odin file and try doing it that way.
Click to expand...
Click to collapse
yeah, i think its becaute the cwm recovery doesnt know what to do with the update.
you need to have the stock recovery installed. dont take my word for it though.
just look up a tutorial for flashing a rom via oden. its really easy, just make sure the image you are flashing is of .tar.md5 extension.
You can get the stock rom at sammobile.com. down load the zip file then extract the .tar.md5 file out of it using 7-zip.
God promised men that he'd put beautiful women in all corners of the world. Then he laughed and laughed and made the world round
FIXED!! - Cheers Everyone!
OK, so I downloaded the stock telstra rom off the forum here, its at the top of page 3 at present, flashed that with Oden, which fixed the soft brick and allowed me to boot again. I then flashed the stock recovery, rebooted, got into the system and downloaded the ICS update again. Once it rebooted, with the stock recovery it was able to install and successfully boot into ICS!! I was more stoked than I've ever been before, let me tell you, lol.
how ?
ragvaror said:
FIXED!! - Cheers Everyone!
OK, so I downloaded the stock telstra rom off the forum here, its at the top of page 3 at present, flashed that with Oden, which fixed the soft brick and allowed me to boot again. I then flashed the stock recovery, rebooted, got into the system and downloaded the ICS update again. Once it rebooted, with the stock recovery it was able to install and successfully boot into ICS!! I was more stoked than I've ever been before, let me tell you, lol.
Click to expand...
Click to collapse
i currently have the same problem as you did, how did you flash with odin if you're stuck in recovery mode ?
please help, I'm racking my brain trying to figure this out.
Trying to flash my Note 4 (Canadian version - N910W8) with either the AllianceROM 1.1 or TEKXodus 3.6 ROMs. Can't seem to get it done and I'm so incredibly frustrated.
Chronologically-speaking, here's what I did.
1. Rooted with appropriate Auto-Root file with Odin 3.09
2. Used Flashify to flash the latest TWRP files (2.8.7)
Most of the time, I just reboot onto "dm-verity verification failed." I've tried everything I can think of.
Sometimes, I get lucky and boot into TWRP. When I flash using TEKXodus 3.6 ROM, it proceeds to do everything but then, the screen goes black and I can never boot. I've read it can take 15 min for it to boot. I've waited 30 min with nothing. Only thing I could do is boot back into Download mode to reflash it with a stock ROM through Odin.
I don't understand why this doesn't work and I've flashed a bunch of phones before without any issue! Help? Anybody? UGH!
need help
Strat-Mangler said:
Trying to flash my Note 4 (Canadian version - N910W8) with either the AllianceROM 1.1 or TEKXodus 3.6 ROMs. Can't seem to get it done and I'm so incredibly frustrated.
Chronologically-speaking, here's what I did.
1. Rooted with appropriate Auto-Root file with Odin 3.09
2. Used Flashify to flash the latest TWRP files (2.8.7)
Most of the time, I just reboot onto "dm-verity verification failed." I've tried everything I can think of.
Sometimes, I get lucky and boot into TWRP. When I flash using TEKXodus 3.6 ROM, it proceeds to do everything but then, the screen goes black and I can never boot. I've read it can take 15 min for it to boot. I've waited 30 min with nothing. Only thing I could do is boot back into Download mode to reflash it with a stock ROM through Odin.
I don't understand why this doesn't work and I've flashed a bunch of phones before without any issue! Help? Anybody? UGH!
Click to expand...
Click to collapse
i m also having the same problem
did u find any solution
Strat-Mangler said:
Trying to flash my Note 4 (Canadian version - N910W8) with either the AllianceROM 1.1 or TEKXodus 3.6 ROMs. Can't seem to get it done and I'm so incredibly frustrated.
Chronologically-speaking, here's what I did.
1. Rooted with appropriate Auto-Root file with Odin 3.09
2. Used Flashify to flash the latest TWRP files (2.8.7)
Most of the time, I just reboot onto "dm-verity verification failed." I've tried everything I can think of.
Sometimes, I get lucky and boot into TWRP. When I flash using TEKXodus 3.6 ROM, it proceeds to do everything but then, the screen goes black and I can never boot. I've read it can take 15 min for it to boot. I've waited 30 min with nothing. Only thing I could do is boot back into Download mode to reflash it with a stock ROM through Odin.
I don't understand why this doesn't work and I've flashed a bunch of phones before without any issue! Help? Anybody? UGH!
Click to expand...
Click to collapse
So i see your posting about your flashing but what about your wipes..
Nandroid backup ext sd.
Then reboot twrp.
Wipe sys/dal/cache/data..
Include the internal if after what i posted above doesnt work.
Check the md5 sum of your downloaded rom..
Nav to your ext sd were you should have the rom stored..
And flash the rom..
Curious as to why you used flashify to get twrp.. it comes in a tar and flashes easy in odin..
You might wanna try that as well twrp may not be installed 100% corectlly.
Ok..[emoji41] [emoji106]
Last but not least you need to use bishock kern in your flash after the Rom flash, in the same session before reboot.
Or it will never work.
You booting problem more than likely kernel related..
Flashvetrin
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