guys need help
i flashed twrp and after successful attempts to go to recovery from download mode directly, it finally went into recovery but before recovery could boot up i saw this at the top "recovery is not seandroid enforcing"
anyways twrp came online and i wiped the data, but now i cant push the dm verity file from pc via both mtp or adb
tried all usb ports, different wire, different pc.
i can create and delete folders but cant send file and without that, my phone stays in bootloop.
i can go into recovery and go into download mode
what should i do?
please reply. my hands are shaking badly
danveer said:
guys need help
i flashed twrp and after successful attempts to go to recovery from download mode directly, it finally went into recovery but before recovery could boot up i saw this at the top "recovery is not seandroid enforcing"
anyways twrp came online and i wiped the data, but now i cant push the dm verity file from pc via both mtp or adb
tried all usb ports, different wire, different pc.
i can create and delete folders but cant send file and without that, my phone stays in bootloop.
i can go into recovery and go into download mode
what should i do?
please reply. my hands are shaking badly
Click to expand...
Click to collapse
That message is fine. Been on mine since day one....
You need to go back into download mode a Odin back to stock.
EDIT: Why are you wanting to mess with dm verity ?
The Sickness said:
That message is fine. Been on mine since day one....
You need to go back into download mode a Odin back to stock.
EDIT: Why are you wanting to mess with dm verity ?
Click to expand...
Click to collapse
I flashed twrp and after that system wasnt booting up
I read in a recovery form ( http://forum.xda-developers.com/gal...y-official-twrp-galaxy-s6-edge-t3354508/page8 that mm introduced verity checks so it can only be disabled if i flash something that disables it..and hence get out of bootloops...
I was making a mistake using adb sideload.. once i corrected the command, everything works...
P.s. its great to see a reply from a dev like you...
"RECOVERY IS NOT SEANDROID ENFORCING" is a normal message when you have a custom recovery installed. Ignore it. It simply means the recovery image did not pass the bootloader's security check; this does not affect your ability to flash ROMs or use your phone.
socal87 said:
"RECOVERY IS NOT SEANDROID ENFORCING" is a normal message when you have a custom recovery installed. Ignore it. It simply means the recovery image did not pass the bootloader's security check; this does not affect your ability to flash ROMs or use your phone.
Click to expand...
Click to collapse
CAn you please be more specific? my phone is showing "RECOVERY IS NOT SEANDROID ENFORCING" do I have to flash a stock rom first or I can flash another custom rom through odin?
Thank you
tuffmek said:
CAn you please be more specific? my phone is showing "RECOVERY IS NOT SEANDROID ENFORCING" do I have to flash a stock rom first or I can flash another custom rom through odin?
Thank you
Click to expand...
Click to collapse
Ignore it...it affects nothing
The Sickness said:
Ignore it...it affects nothing
Click to expand...
Click to collapse
sorry for asking again but i see kernel is not seandroid enforcer on the samsung screen when the phone turns on, it happened after I fleshed a custom rom. should I just wait until it loads or what do you mean it effects nothing?
thank you
tuffmek said:
sorry for asking again but i see kernel is not seandroid enforcer on the samsung screen when the phone turns on, it happened after I fleshed a custom rom. should I just wait until it loads or what do you mean it effects nothing?
thank you
Click to expand...
Click to collapse
Some kernels like stock will have that message in red. My kernels do not.
It affects nothing is pretty straight forward. Did your phone boot? Notice any issues?
It's easy to remove the warning when it goes to recovery. But that means it must be complied with that change.
The Sickness said:
Some kernels like stock will have that message in red. My kernels do not.
It affects nothing is pretty straight forward. Did your phone boot? Notice any issues?
It's easy to remove the warning when it goes to recovery. But that means it must be complied with that change.
Click to expand...
Click to collapse
My phone does not boot, it just stays at the screen galaxy s6 edge when you just turn on the phone
I also tried to falsh a stock rom but Odin says fail.
tuffmek said:
My phone does not boot, it just stays at the screen galaxy s6 edge when you just turn on the phone
I also tried to falsh a stock rom but Odin says fail.
Click to expand...
Click to collapse
Are you flashing the correct firmware?
The Sickness said:
Are you flashing the correct firmware?
Click to expand...
Click to collapse
Hmm, that is a good quesation, I got it from this link
http://forum.xda-developers.com/galaxy-s6-edge/general/sm-g925f-s6-firmware-thread-t3078841
There are two downloads for T-Mobile SM-G925T Galaxy S6 Edge Stock Firmware so I will download the second one and give it a try.
tuffmek said:
Hmm, that is a good quesation, I got it from this link
http://forum.xda-developers.com/galaxy-s6-edge/general/sm-g925f-s6-firmware-thread-t3078841
There are two downloads for T-Mobile SM-G925T Galaxy S6 Edge Stock Firmware so I will download the second one and give it a try.
Click to expand...
Click to collapse
Those are 5.1.......
Where you on 6.0.1? Because that is the firmware you need. Get it from Sammobile.com
The Sickness said:
Those are 5.1.......
Where you on 6.0.1? Because that is the firmware you need. Get it from Sammobile.com
Click to expand...
Click to collapse
Thanks so much dude, it worked.
tuffmek said:
Thanks so much dude, it worked.
Click to expand...
Click to collapse
Good to hear
@tuffmek:
Why did you continue to ask questions when you were told not to worry about it? The SEANDROID ENFORCING error message is inconsequential. If you install a custom recovery such as TWRP, you WILL see the "RECOVERY IS NOT SEANDROID ENFORCING" message, because custom recoveries do not pass the security check. It is NOT an issue. If you install a custom kernel, you will see a similar message. Once again it is not an issue.
I seem to be saying this a lot: If you don't know what you're doing and don't know how to fix it if something goes wrong, you should NOT be doing it in the first place. Questions like this are rather elementary and honestly should not be asked.
Related
Hi guys,
I have a few problems with my Motorola Milestone.
1. I can't get in to recovery. I only get an black screen (backlight is on)
2. I don't get any video in the bootloader. but RSD lite does recognizes it, and is able to flash it. When it's flashing I do get video only stating that there is software update busy.
3. When I boot up my phone I don’t get, a Motorola logo, but just a black screen (back light on) followed by the Android logo after a few minutes.
4. If I try to wake up the phone, the screen remains black, but the hardware keys to light up, I have to press the lock button multiple times to activate the screen. - Note when the screen remains black, it is responsive and I can unlock the phone, but it still remains black. And sometimes the colors are inverted, but when i make a screen of it with Screen Grabber (shoot me) it's in normal colors.
That kind of sums it up.
I have tried a few things to fix it. I have:
1. Cleared caches, and personal data
2. Flashed a different SBF en recovery
And since I can’t get in to recovery, I had to get Root via Z4 Root method and it works fine.
Afterwards I downloaden Rom-manger, and installed the ClockWork recovery, and tried to boot in Recovery via clockwork, but that didn’t work either. I also can’t get in to Recovery via a cold boot
I think the problems started when I was using CyanogenMod 7 RC4. It worked just fine, but after I installed it I couldn't get in to recovery.
Can I try something else to fix it? or should I flash it back to original state and RMA it?
Edit some additional information:
Frimware: 2.2.1
Frimware configuration: GAS_EMEA_UCAMS1FRYOQWRTEU_P005
Baseband version: 3GSMPU91A_U_91.09.00I
Baseband configuratuin version:UCALHLSMR2EMEAB1B806E.0R
Kernel Versuin: 2.6.32.9-ge635aa4 [email protected]#1
Build Number: SHOLS_U2_05.06.0
And is it possible to restore the orginal boot animation, without recovery?
TL.DR: Motorola Milestone --> CyanogenMod 7 RC4 --> no recovery & no video @ bootloader, plus additinal video problems --> back to orginal --> same problems.
BUMP: is there anyone with a possible soulution?
ClockWork recovery doesn't work on milestone.
So CM7 does boot up?
zeppelinrox said:
ClockWork recovery doesn't work on milestone.
So CM7 does boot up?
Click to expand...
Click to collapse
CM7 doesn't anymore as I removed it, and flashed a different SBF and recovery.
CyanogenMod 7 RC4 worked fine but I had a few video problems, and I could get in to recovery.
I will flash a different recovery tonight and try it out.
Only use androidiani open recovery
Sent from my Milestone using Tapatalk
zeppelinrox said:
Only use androidiani open recovery
Sent from my Milestone using Tapatalk
Click to expand...
Click to collapse
Flashed a different .sbf and placed the androidiani open recovery files on the Sd card root, but i still can't get in to recovery. I won't even get the /!\ screen. The phone does turn on, but will only get a black screen.
Which sbf?
Sent from my Milestone using Tapatalk
UK SHOLS_U2_02.36.0
I think I bricked it, I'm going to try to restore it or buy a new phone... >.<
BloemBlaster said:
UK SHOLS_U2_02.36.0
I think I bricked it, I'm going to try to restore it or buy a new phone... >.<
Click to expand...
Click to collapse
I don't think you bricked it... but damaged it in some way.
Could also be some hardware related stuff in the end.
Anyway try to wipe everything, that could be wiped.
Start into bootloader and try to install G.O.T. 2.2.1 using RSD again.
This one got the vulnerable recovery already integrated.
Then try to use the specific G.O.T. OpenRecovery on your sdcard to check system integrity.
Please try to take care of every single step and check out what happens....
If your hardware is doing fine, i'm pretty sure that you will get a working phone again.
P.S.: How about your bootloader version?
Good luck,
scholbert
scholbert said:
I don't think you bricked it... but damaged it in some way.
Could also be some hardware related stuff in the end.
Anyway try to wipe everything, that could be wiped.
Start into bootloader and try to install G.O.T. 2.2.1 using RSD again.
This one got the vulnerable recovery already integrated.
Then try to use the specific G.O.T. OpenRecovery on your sdcard to check system integrity.
Please try to take care of every single step and check out what happens....
If your hardware is doing fine, i'm pretty sure that you will get a working phone again.
P.S.: How about your bootloader version?
Good luck,
scholbert
Click to expand...
Click to collapse
I think my boatloader is 90.47 I'm not sure as I won't get any video in the boatloader.
I flashed the G.O.T 2.2.1but I can't get in to recovery, there is still no video only a blackscreen.
Is it posible the may have deleted the files for the logo?
BloemBlaster said:
I think my boatloader is 90.47 I'm not sure as I won't get any video in the boatloader.
I flashed the G.O.T 2.2.1but I can't get in to recovery, there is still no video only a blackscreen.
Is it posible the may have deleted the files for the logo?
Click to expand...
Click to collapse
You can try upgrading your bootloader to 90.78 from here.
Then try flashing GOT 2.2.1, then see if AOR boots up.
sileshn said:
You can try upgrading your bootloader to 90.78 from here.
Then try flashing GOT 2.2.1, then see if AOR boots up.
Click to expand...
Click to collapse
I flashed 90.78, and then reflashed GOT 2.2.1, but is still can't get into te recovery. I getting the same result, no motorola logo and a black screen with no /!\ logo
If your phone is recognised in adb, then you can use the link below to get into AOR directly. Just make sure you have AOR extracted to your sdcard.
http://forum.xda-developers.com/showthread.php?t=625950
Check the commands in the last post and enter them in order.
I was just looking at QtADB for somebody else's problem but it looks like you can use QtADB to boot recovery if the phone is recognized.
http://qtadb.wordpress.com/features/
Hi guys,
sorry for the late reply, but I'm also moving at the moment.
I have tired numerous things.
If I flash the 2.2.1 Firmware SHOLS_U2_05.26, I can get to the recovery selection screen, with the /!\ screen.
But if apply update.zip I will get an error message, stating "EOCD marker occurs after start of EOCD E:signature verification failed", something like that, I don't know the specific message out of my head
And if I flash a vurnable recovery only sbf, with the SHOLS_U2_05.26 I can't get the recovery screen, only a black screen.
zeppelinrox said:
I was just looking at QtADB for somebody else's problem but it looks like you can use QtADB to boot recovery if the phone is recognized.
http://qtadb.wordpress.com/features/
Click to expand...
Click to collapse
I will try thiss when I get home.
sileshn said:
If your phone is recognised in adb, then you can use the link below to get into AOR directly. Just make sure you have AOR extracted to your sdcard.
http://forum.xda-developers.com/showthread.php?t=625950
Check the commands in the last post and enter them in order.
Click to expand...
Click to collapse
I will try this if zepplelinrox method fails becaus I don't have any experince with adb. But the phone is recognised.
...........strange....
BloemBlaster said:
If I flash the 2.2.1 Firmware SHOLS_U2_05.26, I can get to the recovery selection screen, with the /!\ screen.
But if apply update.zip I will get an error message, stating "EOCD marker occurs after start of EOCD E:signature verification failed", something like that, I don't know the specific message out of my head
Click to expand...
Click to collapse
This is standard error, if vulnerable recovery is not installed and you try to start OpenRecovery.
BloemBlaster said:
And if I flash a vurnable recovery only sbf, with the SHOLS_U2_05.26 I can't get the recovery screen, only a black screen.
Click to expand...
Click to collapse
This is strange behaviour...
My last guess is, that something might be wrong with your vulnerable recovery sbf file (file corruption ???). There should have been some errors during flash...
Anyway, you might grab it here and try again:
http://gitorious.org/droid/openrecovery/blobs/master/zips/SHOLS/vulnerable_recovery.sbf
Good luck!
scholbert
sileshn said:
If your phone is recognised in adb, then you can use the link below to get into AOR directly. Just make sure you have AOR extracted to your sdcard.
http://forum.xda-developers.com/showthread.php?t=625950
Check the commands in the last post and enter them in order.
Click to expand...
Click to collapse
Still trying this, no luck yet. ADB isn't my strongest point
zeppelinrox said:
I was just looking at QtADB for somebody else's problem but it looks like you can use QtADB to boot recovery if the phone is recognized.
http://qtadb.wordpress.com/features/
Click to expand...
Click to collapse
The same goes for you, no luck yet. QtADB, work and it recognise my phone, but i can't any (re)boot commands.
scholbert said:
This is standard error, if vulnerable recovery is not installed and you try to start OpenRecovery.
This is strange behaviour...
My last guess is, that something might be wrong with your vulnerable recovery sbf file (file corruption ???). There should have been some errors during flash...
Anyway, you might grab it here and try again:
http://gitorious.org/droid/openrecovery/blobs/master/zips/SHOLS/vulnerable_recovery.sbf
Good luck!
scholbert
Click to expand...
Click to collapse
I actually have no idea how to download the sbf, form the site you have provided.
nevermind, I found it out . but now if my phone to connect to windows it doesn't recognizes it :S
BloemBlaster said:
but now if my phone to connect to windows it doesn't recognizes it :S
Click to expand...
Click to collapse
Before or after flashing the vulnerable recovery again?
Confusing...
scholbert
scholbert said:
Before or after flashing the vulnerable recovery again?
Confusing...
scholbert
Click to expand...
Click to collapse
Sorry for being confusing, it was after flashing vulnerable recovery, but my I'm flashing with a different system now and it working just fine.
If I try the .sbf you provided RSD gives a error "Failed flashing process. failed flashing process (0x17100);phone connected"
BloemBlaster said:
Sorry for being confusing, it was after flashing vulnerable recovery, but my I'm flashing with a different system now and it working just fine.
Click to expand...
Click to collapse
No problem...
BloemBlaster said:
If I try the .sbf you provided RSD gives a error "Failed flashing process. failed flashing process (0x17100);phone connected"
Click to expand...
Click to collapse
O.K. seems that something went wrong during download grab it here:
http://forum.xda-developers.com/showpost.php?p=13039348&postcount=17
BTW the link points to the OpenRecovery developers git rep... so this file is absolutely save.
Cheers,
scholbert
I can get it into download mode + recovery mode, but keeps rebooting at logo. tried factory wipe. completely stock.
here's a picture
]http://dl-1.va.us.xda-developers.com/2/9/2/8/2/6/9/10668416_829527553754164_1709046890_n.jpg?key=2NJxF1hr-LOFooxPNFDfCA&ts=1410111073
anybody got any idea?
just put it through odin, flashed cf root and everything ok but still just boots to samsung logo and repeats. what should i do
UrbanDesigns said:
I can get it into download mode + recovery mode, but keeps rebooting at logo. tried factory wipe. completely stock.
here's a picture
]http://dl-1.va.us.xda-developers.com/2/9/2/8/2/6/9/10668416_829527553754164_1709046890_n.jpg?key=2NJxF1hr-LOFooxPNFDfCA&ts=1410111073
anybody got any idea?
just put it through odin, flashed cf root and everything ok but still just boots to samsung logo and repeats. what should i do
Click to expand...
Click to collapse
Do any error messages appear on the stock recovery screen?
ArkThompson said:
Do any error messages appear on the stock recovery screen?
Click to expand...
Click to collapse
nope but it shows the android bot open with a red !
UrbanDesigns said:
nope but it shows the android bot open with a red !
Click to expand...
Click to collapse
Have you tried flashing stock firmware through Odin? You can find it at http://www.sammobile.com/firmwares/
ArkThompson said:
Have you tried flashing stock firmware through Odin? You can find it at http://www.sammobile.com/firmwares/
Click to expand...
Click to collapse
nope but I tried the basic root firmware, wouldn't really make a difference would it?
i know it's not a power switch issue as well because the phone only boots up when i press the button, not on its own
UrbanDesigns said:
nope but I tried the basic root firmware, wouldn't really make a difference would it?
i know it's not a power switch issue as well because the phone only boots up when i press the button, not on its own
Click to expand...
Click to collapse
What? CF-Auto-Root is just something that roots your phone. Flashing stock firmware is completely different.
Try plugging your phone into a PC and use Kies to restore your firmware to defaults.
SM-T815
I have try to root with odin and cf autoroot and all work fine, then I have installed twrp for 815 5.0.2 version. After the installation the tablet restart on recovery mode, I try to make a backup and twrp works good but at the restart the tablet is in bootloop.
I can’t shut down. I can only access download mode and not recovery mode.
I have flashed the original firmware with odin and odin says PASS but at the restart it is bootloop again. I try to flash twrp again and odin says PASS, after this I can read on the start screen (the only one I can see) “recovery is not nandroid enforced”. I tried different firmware but nothing work.
Someone can help me?
Grazie 1000
Boot into recovery POWER +HOME +VOL DOWN then as soon as the screen goes blank immediately change to VOL UP whilst still holding the other buttons.
Wipe data. If that doesn't work then factory reset.
Thanks for the answer. I try more than 100 time but it don't go in recovery mode. I tried to complete discharging and then recharging with the buttons pushed. Nothing. Every time it's stuck in the start screen and i can't shut down.
ashyx said:
Boot into recovery POWER +HOME +VOL DOWN then as soon as the screen goes blank immediately change to VOL UP whilst still holding the other buttons.
Wipe data. If that doesn't work then factory reset.
Click to expand...
Click to collapse
sorry to bother you,
do you think it is possible to force recovery mode from odin? i can't do it with buttons
ctlx said:
sorry to bother you,
do you think it is possible to force recovery mode from odin? i can't do it with buttons
Click to expand...
Click to collapse
Not possible.
Try booting to Download mode then hit CANCEL then immediately hold HOME + VOL DOWN + POWER make sure you hold the buttons in that order and you must be quick.
[email protected] said:
I don't have much idea but I had read somewhere that u can flash ROMs through Odin too.
P.S. I m not sure about it.
Sent from my GT-S7390 using XDA Forums
Click to expand...
Click to collapse
Please read the OP again.
ashyx said:
Not possible.
Try booting to Download mode then hit CANCEL then immediately hold HOME + VOL DOWN + POWER make sure you hold the buttons in that order and you must be quick.
Click to expand...
Click to collapse
no way. i flash the stock firmware with kies3, all work good but bootloop again. impossible to boot in recovery, i try more then 100 times your way but only download mode
ctlx said:
no way. i flash the stock firmware with kies3, all work good but bootloop again. impossible to boot in recovery, i try more then 100 times your way but only download mode
Click to expand...
Click to collapse
please don't let me go to samsung asking for help
ctlx said:
please don't let me go to samsung asking for help
Click to expand...
Click to collapse
Still not able to boot to recovery? I will build you a boot image that will boot you directly to recovery.
ashyx said:
Still not able to boot to recovery? I will build you a boot image that will boot you directly to recovery.
Click to expand...
Click to collapse
it will be great!
yes i'm still on bootloop
same trouble here lase help
Hi All!
I would like to share with you how I fix the preblem after root of my T815.
After long night and reading whole net I found the solution.
As you I also wants to root my device because of availible only one user. I wanted to have multiusers. So folowing the instructions downloading all software and after root I got bootloop. Trying everithing but no success. I wasn't able to flash even some of the stock ROMs.
Solution:
I found in Sammobile what is my current ROM and downloaded it. Then flash - no any problems. Went smooth. Then I root the device... and now I have rooted device with multiuser support.
It seems that after fresh flash everithing is OK. It seems that after you playing with your device for a while you enabled some options thats make your device to loop after root.
I wish you Happy New Year!
Nikog
Whoops sorry, I completely forgot to come back to you about this!
Glad you got it sorted.
Nikog said:
Hi All!
I would like to share with you how I fix the preblem after root of my T815.
After long night and reading whole net I found the solution.
As you I also wants to root my device because of availible only one user. I wanted to have multiusers. So folowing the instructions downloading all software and after root I got bootloop. Trying everithing but now success. I wasn't able to flash even some of the stock ROMs.
Solution:
I found in Sammobile what is my current ROM and downloaded it. Then flash - no any problems. Went smooth. Then I root the device... and now I have rooted device with multiuser support.
It seems that after fresh flash everithing is OK. It seems that after you playing with your device for a while you enabled some options thats make your device to loop after root.
I wish you Happy New Year!
Nikog
Click to expand...
Click to collapse
thanks, I will try and let you know if it works for me.
at this time I have tried to flash different stock rooms but not one works, even if odin says it is all ok
ashyx said:
Whoops sorry, I completely forgot to come back to you about this!
Glad you got it sorted.
Click to expand...
Click to collapse
i don't find a solution.
if you can help me it will be great
ctlx said:
i don't find a solution.
if you can help me it will be great
Click to expand...
Click to collapse
Still not able to boot to recovery?
ashyx said:
Still not able to boot to recovery?
Click to expand...
Click to collapse
yes still on the same condition, only download mode
ctlx said:
yes still on the same condition, only download mode
Click to expand...
Click to collapse
OK, hopefully I can come back to you later with a boot.img to boot directly to recovery.
ashyx said:
OK, hopefully I can come back to you later with a boot.img to boot directly to recovery.
Click to expand...
Click to collapse
thanks a lot
ctlx said:
thanks a lot
Click to expand...
Click to collapse
It was a late night for me last night and working late again tonight.
If I get the opportunity after work I'll get something up, but if not it may be tomorrow on my day off.
This will be for the SM-G935D/SC-02H Japanese variant of the s7 edge.
Stock ODIN firmware: https://www.androidfilehost.com/?fid=817550096634767393 (SC02HOMU1BQC5 Nougat)
TWRP 3.1.1: https://www.androidfilehost.com/?fid=673791459329056265
HKROM V2: https://www.androidfilehost.com/?fid=817550096634771123
HKernel for hero2qltedcm V2 (June):https://www.androidfilehost.com/?fid=961840155545571333
Kernel includes:
CVE updated
Permissive
F2FS support
Ramdisk changes the same as hero2qltechn variant. (All changes are the same)
Kernel Change-log:
https://github.com/travismills82/android_kernel_samsung_msm8996/commits/test-tw-7.0
TWRP Unofficial:
F2FS Support
More partitions supported for backup and restore compared to official version
How to root this device: https://forum.xda-developers.com/s7-edge/how-to/guide-sm-g9350-s7-edge-qualcomm-sd820-t3410969
Really amazing developer I've met!
Thank you so much @travis82
after i flash this i can't even access download mode and recovery mode. my phone keeps restarting with message "Recovery Booting (Blue text color) and "Set Warranty Bit: Recovery" (Yellow Text Color) please help me.
gAracUh said:
after i flash this i can't even access download mode and recovery mode. my phone keeps restarting with message "Recovery Booting (Blue text color) and "Set Warranty Bit: Recovery" (Yellow Text Color) please help me.
Click to expand...
Click to collapse
twrp 3.0.3 https://www.androidfilehost.com/?fid=817550096634747128
This recovery working for you? Others stated the one in the op works just fine, but since I do not have this device to test personally I can only go off of what users say.
it's working for me, after i flash the ROM i think my phone got bootloop that's why i boot again to download mode but when i tried to flash stock rom it gives a fail. now my phone stuck on led blue light and "Recovery Booting (Blue text color) and "Set Warranty Bit: Recovery" (Yellow Text Color). i need to wait to drain the battery and try if i can boot to download mode again.. i'm afraid if i can't access download mode again or recovery.
You guys are remembering to format data on a new twrp install or a new os version install? 6-7,7-8 get it? These roms or recoverys will not brick the devices I made them for kinda impossible.
You do know a brick right? Brick = no power nothing just a pricey paperweight.
how about my problem "Recovery Booting (Blue text color) and "Set Warranty Bit: Recovery" (Yellow Text Color) and it keeps restarting i can't access recovery either download mode
gAracUh said:
how about my problem "Recovery Booting (Blue text color) and "Set Warranty Bit: Recovery" (Yellow Text Color) and it keeps restarting i can't access recovery either download mode
Click to expand...
Click to collapse
did u unlock your bootloader? sounds like you did not.
it won't my phone to unlock bootloader everytime i run CROM it closes automatically. until now i can't believe my phone was bricked and i don't have any idea to fix this without download mode. even if i bring this to service center i think they will not to accept my phone because my warranty is already void.
hy i recently bought this(sc02h) model from Japan but currently using it in Australia. everythng is fine except for the rom.....there is lots of bloatware apps in japanese which i dont realy need and the starting animation of docomo is bothering me too. So is there anyway i can use a global firmware with no bloatware in this model?? i dont want any root or custom rom . only want to flash with odin
Thanks for ur help in advance
ch0c0lateb0yctg said:
hy i recently bought this(sc02h) model from Japan but currently using it in Australia. everythng is fine except for the rom.....there is lots of bloatware apps in japanese which i dont realy need and the starting animation of docomo is bothering me too. So is there anyway i can use a global firmware with no bloatware in this model?? i dont want any root or custom rom . only want to flash with odin
Thanks for ur help in advance
Click to expand...
Click to collapse
no global firmware only jap firmware. You got what you got and are stuck with it. Enjoy your phone.
travis82 said:
no global firmware only jap firmware. You got what you got and are stuck with it. Enjoy your phone.
Click to expand...
Click to collapse
shame....i was starting to like this blue coral version...still happy though...been using s7 black for a while now.
Kernel updated to V2 with June cve patches etc.. check changelogs in 1st post.
Hello! first of all thank you for this thread. I've been reading since the first thread that sir Travis has created.
I just can't unlock my bootloader, I think it is the reason why I am having bootloops after installing the rom , and even I install the rom in this thread I am still having the bloated one after installing.
I tried installing different CROM Services from every other sources that I found, but still no luck. CROM service has stopped -error I get when opening after installing it on my phone.
I also tried factory resetting my phone then install CROM but still same error occurs.
I hope you can help me guys. Thank you in advance!
mavin11 said:
Hello! first of all thank you for this thread. I've been reading since the first thread that sir Travis has created.
I just can't unlock my bootloader, I think it is the reason why I am having bootloops after installing the rom , and even I install the rom in this thread I am still having the bloated one after installing.
I tried installing different CROM Services from every other sources that I found, but still no luck. CROM service has stopped -error I get when opening after installing it on my phone.
I also tried factory resetting my phone then install CROM but still same error occurs.
I hope you can help me guys. Thank you in advance!
Click to expand...
Click to collapse
SC-02H/SCV33 doesn't need to unlock bootloader. Because they aren't been locked bootloader.
So there's no need to do that.
baobeatmaker said:
SC-02H/SCV33 doesn't need to unlock bootloader. Because they aren't been locked bootloader.
So there's no need to do that.
Click to expand...
Click to collapse
oh.. didnt know that. thank you bro. then I dunno what I did wrong in the process that gives me a bootloop everytime I install the ROM from this thread..
but I will try to do it again at this moment, and will be back for the result. thanks again!
mavin11 said:
oh.. didnt know that. thank you bro. then I dunno what I did wrong in the process that gives me a bootloop everytime I install the ROM from this thread..
but I will try to do it again at this moment, and will be back for the result. thanks again!
Click to expand...
Click to collapse
I tried installing ROM again, but Im still stuck at the Galaxy logo which is blinking a little fast I think with blue led light that is not blinking even a little.
mavin11 said:
I tried installing ROM again, but Im still stuck at the Galaxy logo which is blinking a little fast I think with blue led light that is not blinking even a little.
Click to expand...
Click to collapse
You need to let the phone boot about 15-20mins bro.
You just need more patient.
mavin11 said:
oh.. didnt know that. thank you bro. then I dunno what I did wrong in the process that gives me a bootloop everytime I install the ROM from this thread..
but I will try to do it again at this moment, and will be back for the result. thanks again!
Click to expand...
Click to collapse
baobeatmaker said:
You need to let the phone boot about 15-20mins bro.
You just need more patient.
Click to expand...
Click to collapse
I tried it again, I've waited for almost 1 hour, and nothing happens. I wonder, before booting, something shows at the top with yellow font color says "Set Warranty Bit : kernel", is it normal for that to show? or is it mean that Im having a corrupted boot data?
mavin11 said:
I tried it again, I've waited for almost 1 hour, and nothing happens. I wonder, before booting, something shows at the top with yellow font color says "Set Warranty Bit : kernel", is it normal for that to show? or is it mean that Im having a corrupted boot data?
Click to expand...
Click to collapse
it's really normal. Mine shown that too.
Full AT&T official FIRMWARE G935AUCS4BRA1 to restore //G935A\\ with January security
G935AUCS4BRA1
Latest ODIN 3.12.10
Enjoy !!!!
norbarb said:
G935AUCS4BRA1
Latest ODIN 3.12.10
Enjoy !!!!
Click to expand...
Click to collapse
As always, thanks so much.
New BIT 5 version is released ... link needed
aamszia said:
New BIT 5 version is released ... link needed
Click to expand...
Click to collapse
There is no full firmware with Bootloader 5, there not even any of G935 was OTA updated to Bootloader 5 as of yet. . There are only combination files witch you should not flash unless you need to fix your phone. So i'm sorry but you stuck on it.
Can't seem to get it to download... through computer or phone
Edit: I got it.... thanks
norbarb said:
G935AUCS4BRA1
Latest ODIN 3.12.10
Enjoy !!!!
Click to expand...
Click to collapse
Thank you ! Quick question, I currently have 935A with May security firmware fully stock, can I just flash this directly to get latest update ? (I believe this will wipe my phone too)
bestjsg said:
Thank you ! Quick question, I currently have 935A with May security firmware fully stock, can I just flash this directly to get latest update ? (I believe this will wipe my phone too)
Click to expand...
Click to collapse
Yes. You can flash directly and this will wipe data in your phone.
Sent from my SM-N950U using XDA Premium HD app
Stock ATT firmware
Thanks tons, now stuck in a boot loop cannot even turn off. I have tried various ways to get the U version and if I get this back to stock, think I will sell it and buy a U version. Hate carrier proprietary garbage.:good:
nomad247 said:
Thanks tons, now stuck in a boot loop cannot even turn off. I have tried various ways to get the U version and if I get this back to stock, think I will sell it and buy a U version. Hate carrier proprietary garbage.:good:
Click to expand...
Click to collapse
You need to get to recovery and clean cache
Sent from my SM-N950U using XDA Premium HD app
Bootloop
You need to get to recovery and clean cache
Have a ask a really dumb question, How do I get to "clear cache" in recovery? And of course, googled it, just have to charge some. I did achieve root earlier, just trying to get the "U" mod installed. Thanks tons
edit: Did the steps so now I have a blinking message saying recovery booting...
nomad247 said:
You need to get to recovery and clean cache
Have a ask a really dumb question, How do I get to "clear cache" in recovery? And of course, googled it, just have to charge some. I did achieve root earlier, just trying to get the "U" mod installed. Thanks tons
Click to expand...
Click to collapse
Press and hold power, home and volume button up anthill Samsung splash screen. Then let go and for recovery menu to popup.
Sent from my SM-N950U using XDA Premium HD app
Boot loop and maybe bricked
I still cannot get to the cache to clear it.
Here what I have right now.
hold power button, screens goes black then have the first screen of start, S7 edge, it goes off and comes back on
i can get into down load mode, tried reloading the stock firmware but get a write error, model miss-match
if arrow down goes to start up boot loop, if arrow up does into downlaod
power off (does not really shut off)
Vol up + home + power, gets the recovery booting loop
Odin sees the phone, but any writes all seem to fail. Sometimes have to use Odin Prince sometimes 3.12.7
In 12/.6 tried to load the S7 edge qual com image file from rooting, and that said fail in red.
Tried to flash back stock but like I said earlier, says product code miss match
I had tried to use odin to do that update and that probably is what screwed the pooch.
Any ideas?
eror 404 not found broken link very nice...
error 404
can you upload the file again ?
@norbarb you need to take all your links down if you're not going to reupload them.
Boot loop and recovery boot loop
You need to get to recovery and clean cache
ok so, is there a way to fix this with boot lop and recovery in boot loop?
Odin comsy sees the phone but ADB does not... Hoping to get this fixed and working again. Had to buy a phone so using a SM-G930V. At least no more ATT for me....
Anyone???
Here you go guys enjoy.
https://drive.google.com/drive/folders/1aal95ObUmnxdNu33bac0GXosOSRLXD0i
Q: why are the files doble the size of the other updates??
bsharp8 said:
Here you go guys enjoy.
Click to expand...
Click to collapse
Disregard - sorry, didn't see the new link.
Edit: Thanks for the updated files! I'm not sure why it failed the first time, but it worked the second time.