Hello everyone !
I bought a Samsumg Galaxy S6 Edge + ( G928G ) , however did not like the OS of Samsumg and decided to install a custom ROM .
I root with the help of Arter97 and finally installed TWRP to facilitate the time to use the Recovery Mode .
Managed to install the Rom smoothly, did not show any eror log or anything , the problem appeared in connecting to my S6 , appears Boot Screen of Samsumg ( Written Samsumg Galaxay S6 Edge + ), then it changes to the Boot Screen of custom ROM , then that happens the problem, the image will be still there and nothing happens , the image does not freeze , but also does not change screen.
So I tried to go back to Rom Original Samsumg , however the problem persisted, appears Boot Screen of Samsmung and the image will be still there.
If anyone can help me I will be very grateful , because I need my phone for work .
raitos said:
Hello everyone !
I bought a Samsumg Galaxy S6 Edge + ( G928G ) , however did not like the OS of Samsumg and decided to install a custom ROM .
I root with the help of Arter97 and finally installed TWRP to facilitate the time to use the Recovery Mode .
Managed to install the Rom smoothly, did not show any eror log or anything , the problem appeared in connecting to my S6 , appears Boot Screen of Samsumg ( Written Samsumg Galaxay S6 Edge + ), then it changes to the Boot Screen of custom ROM , then that happens the problem, the image will be still there and nothing happens , the image does not freeze , but also does not change screen.
So I tried to go back to Rom Original Samsumg , however the problem persisted, appears Boot Screen of Samsmung and the image will be still there.
If anyone can help me I will be very grateful , because I need my phone for work .
Click to expand...
Click to collapse
I sent you a PM. Check it..
Konsstantine34 said:
I sent you a PM. Check it..
Click to expand...
Click to collapse
Why not share here so others can get help?
/CK
Café King said:
Why not share here so others can get help?
/CK
Click to expand...
Click to collapse
Hey man. I was thinking about that. I made some custom splash screen which has other countries flags and else. Just asked for a credit to dev of script for use his zip. I mean i wanted to use his zip to flash my custom splash screens(u can see a sample in my profile album), but he didnt reply or care that. I cant post under that situation.
Ed.: Here you go see them. They arent professional work, I was just having rest and got an idea like that. There are more flags and etc. No need to post without credit. Im using for myself and send some friends.
Related
Hy there...
I just got my brand new sgs today and am already starting to learn things about it...
I wanted to install the Android Lockscreen instead of the Samsung one , and after flashing my phone kept freezing at the boot logo.
Here is a solution based on the file that bricked it in the first place, and what's great , if it works for you , you won't have to reflash it.
Just connect the phone frozen at boot logo via USB.
from the dir , hit repairme.bat and follow the onscreen instructions.
*Worked on JM1 ORO phone.
Hope this helps someone else.
BR
@Admin , if this doesn't work for other phones eg.android.policy is version dependent ... please delete this post
@All i got in this mess in the first place , cause i didn't read that this lockscreen remover wasn't for my phone version.
PLZ help me on this guys , im going mad on this
HOW TO SOLVE THE " DM-VERITY VERIFICATION FAILED NEED TO CHECK DRK FIRST " or when i install a stock rom this one first appears bUt not in reCovery " DEVICE DOESNT HAVE DRK , INSTALL DRK " ????????
it all happened after i deleted my imei then succesfully restored it with backup when downgrading from that god forsaken CM13 made by raymanFX (it was build 8 i think) , now OTAs and Security patches all face this issue in recovery when installing after being downloaded , now im in middle of nowwhere with no backup and ive tried everything but none works and im not a hacker nor an information thief just a member waiting for HELP... (SM-N910H)
:crying::crying::crying::crying::crying::crying:
! THERE IS NO OFFICIAL SAM CUSTOMER SERVICE IN MY CITY AND mobile merchants are not TRUSTWORTHY !
Someone told me that i need to find a cert file for my Phone and i found it , how is it related to DRK and what should i do with it??
Whatever happens to the phone, if the phone turns on, doesnt have any hardware issue it can be revived.
The universal method is flashing stock firmware through odin
Download your country's note 4 firmware from sammobile and flash it through odin
Works most of the time
For any more help pm m!
yeah. try flashing samsung stock firmware with odin. have you done it
Sent from my SM-N920G using Tapatalk
YEP Odin flash is most of the time a good fix.
ankahuja said:
Whatever happens to the phone, if the phone turns on, doesnt have any hardware issue it can be revived.
The universal method is flashing stock firmware through odin
Download your country's note 4 firmware from sammobile and flash it through odin
Works most of the time
For any more help pm m!
Click to expand...
Click to collapse
well . odin was the first thing to try i have gone even far far away from odin and non works . but a video on youtube got my attention , a guy with a s6 edge had this problem and fixed with some sort of software (i attached it) , a friend of mine says that its sth called BOX and i dont understand him !https://www.youtube.com/watch?v=HlMQQPpqELI
ArmanFGT said:
well . odin was the first thing to try i have gone even far far away from odin and non works . but a video on youtube got my attention , a guy with a s6 edge had this problem and fixed with some sort of software (i attached it) , a friend of mine says that its sth called BOX and i dont understand him !https://www.youtube.com/watch?v=HlMQQPpqELI
Click to expand...
Click to collapse
See here: http://forum.xda-developers.com/note-4/help/dm-verity-verification-failed-recovery-t2945531
Use google and search for
Note 4 DM-VERITY VERIFICATION FAILED
You get a 100 hits.
The same occurred for my LG G3 D855 which has erased its IMEI just for trying 'restore upgrade errors' in the LG mobile support tool. From that onwards I have firmly decided not to flash manually in any way except when official upgrades / uupdates are released via KIES or via OTA update.
Please do not flash by your own as it is always risky. It is not a PC where you can take out the affected hard disk and fix it in a working PC and backup the data.
To all manual flashing persons :
If your phone succeeds in manual flashing, donnot brain wash others to do the same. Not all persons always do R & D in android like you.
sudhakar35 said:
The same occurred for my LG G3 D855 which has erased its IMEI just for trying 'restore upgrade errors' in the LG mobile support tool. From that onwards I have firmly decided not to flash manually in any way except when official upgrades / uupdates are released via KIES or via OTA update.
Please do not flash by your own as it is always risky. It is not a PC where you can take out the affected hard disk and fix it in a working PC and backup the data.
To all manual flashing persons :
If your phone succeeds in manual flashing, donnot brain wash others to do the same. Not all persons always do R & D in android like you.
Click to expand...
Click to collapse
Thanks for the reply but the main problem is that any OTA that comes to note 4 i download them and the device says to restart to recovery to install the Update and i say yes but when it goes to recovery the recovery wont function well since it shows dm-verity error and supported API : 3 the update process fails to complete . My imei is as cool as always i havent had a problem with IMEI since i bought the phone
at least 10000 people have note 4 and none has had the problem ???? REALLY ?
seems like im pretty f***ed up
chappatti said:
See here: http://forum.xda-developers.com/note-4/help/dm-verity-verification-failed-recovery-t2945531
Use google and search for
Note 4 DM-VERITY VERIFICATION FAILED
You get a 100 hits.
Click to expand...
Click to collapse
dear chappati , according to that video i need a physical thing which is called a BOX and a software called GC PRO because that guy had my problem and fixed it with a clicking , but im reasearching for 5 months and nothing comes out . i need information PLZ
Hi, i used to had that problem too, when i first flash a custom rom to my N910G i back up my stock rom.. everthing including EFS.. after that then i wipe everything like normal procedure when u flash a rom. till then 1 day i wanna go back to stock rom i accidentally ticked EFS while i wanna restore that stock rom back up and then i thought it was nothing serious until i flash stock rom with odin and when i boot into stock recovery that dm-verity message was shown, did so much research but no luck. my n910G was on a Singapore firmware, that time it had a update i just try my luck by downloading the latest SG firmware and then that message was gone! m now already on MM no problems like that anymore
Deleted
Hi, I need your help guys, this is the problem:
I have a Samsung Galaxy S6 EDGE+ with Android 6.0.1 Marshmallow and the model is SM-G928F. No problem here.
So I decided to flash twrp with Odin, all correctly, version, compatibility, etc.
I plugged the phone in download mode, and flashed the twrp. All seems to be fine.
BUT just after that, when the phone is rebooting, it appears a message in red: "recovery is not seandroid enforcing" and i can't pass to recovery mode. The only way to fix it is flashing the stock firmware. So I can't install any custom recovery and I don't know how to fix that problem and I need the custom recovery as soon as possible. If anyone know the solution, please ask me. Thanks :fingers-crossed:
That is a common problem.The cause is that you dont have an mm compatible twrp.Use this http://forum.xda-developers.com/s6-...ecovery-official-twrp-galaxy-s6-edge-t3354492 Also dont forget that the first thing you must do is flash a kernel
@ÆROMIND - It's possible @Rainbow_Dash is correct, but if you did as you said and had checked version, compatibility etc, try this first:
After installing TWRP, as soon as the screen goes dark when rebooting - and you have to be quick - hit the volume up/power/home buttons simultaneously and keep them pressed. You should reboot into recovery.
I had the same problem, this worked. The "recovery is not seandroid enforcing" is normal btw.
B3311 said:
@ÆROMIND - It's possible @Rainbow_Dash is correct, but if you did as you said and had checked version, compatibility etc, try this first:
After installing TWRP, as soon as the screen goes dark when rebooting - and you have to be quick - hit the volume up/power/home buttons simultaneously and keep them pressed. You should reboot into recovery.
I had the same problem, this worked. The "recovery is not seandroid enforcing" is normal btw.
Click to expand...
Click to collapse
Thanks very much for the support, I will try it.
I'll let you know if it's work, thanks!
ÆROMIND said:
Thanks very much for the support, I will try it.
I'll let you know if it's work, thanks!
Click to expand...
Click to collapse
But just a question:
@Rainbow_Dash Said to me that I need to flash a custom kernel, maybe he have reason because I'm using the Marshmallow stock firmware, and it have more security. Perhaps that's is the problem. In that case, will I need to flash a kernel? Anyway, I don't want it, because customs kernel usually have problems with battery and a few more like wi-fi spontaneous disconnections.
ÆROMIND said:
But just a question:
@Rainbow_Dash Said to me that I need to flash a custom kernel, maybe he have reason because I'm using the Marshmallow stock firmware, and it have more security. Perhaps that's is the problem. In that case, will I need to flash a kernel? Anyway, I don't want it, because customs kernel usually have problems with battery and a few more like wi-fi spontaneous disconnections.
Click to expand...
Click to collapse
I wont lie on 100% stock roms costum kernels are often a terrible idea resulting in what you mentioned.But if you use a good costum rom (like audax plus my tw favourite) that will not be a problem and many times resulting in a better experience and battery life etc
@ÆROMIND - did you solve it?
Why can't I just flash one with Odin? As other mobile holders could do. What's the problem with the Samsung Galaxy s6 Edge + ? I mean I tried everything what's in this post but it is hanging on RECOVERY IS NOT SEANDROID ENFORCING. I've just flashed the stock rom with Odin. But I got an enormous battery drain caused by Android OS and everyone is saying the only solution is rooting your phone. I got a Samsung Galaxy s6 Edge + (928F PDA G928FXXS2BPE2
CSC G928FPHN2BPB6)
S6EdgePlus928FUser said:
Why can't I just flash one with Odin? As other mobile holders could do. What's the problem with the Samsung Galaxy s6 Edge + ? I mean I tried everything what's in this post but it is hanging on RECOVERY IS NOT SEANDROID ENFORCING. I've just flashed the stock rom with Odin. But I got an enormous battery drain caused by Android OS and everyone is saying the only solution is rooting your phone. I got a Samsung Galaxy s6 Edge + (928F PDA G928FXXS2BPE2
CSC G928FPHN2BPB6)
Click to expand...
Click to collapse
Because you can try every twrp if you want even if its listed working for edge plus.If it is not compatible with mm bootloader it wil hang at seandroid enforcing which is why you must get the one i linked up there.If you have lolipop flash whatever you want.
S6EdgePlus928FUser said:
Why can't I just flash one with Odin? As other mobile holders could do. What's the problem with the Samsung Galaxy s6 Edge + ? I mean I tried everything what's in this post but it is hanging on RECOVERY IS NOT SEANDROID ENFORCING. I've just flashed the stock rom with Odin. But I got an enormous battery drain caused by Android OS and everyone is saying the only solution is rooting your phone. I got a Samsung Galaxy s6 Edge + (928F PDA G928FXXS2BPE2
CSC G928FPHN2BPB6)
Click to expand...
Click to collapse
Alot of people (including me) have had the same problem. Strange thing is 3.0.0 worked just fine. The probs started when I updated to 3.0.2. After that I haven't been able to install ANY of the previous versions. Then I saw that someone was using the version for note 5 noblelte. So I tried and it worked like clockwork.. I'm on G928F with the latest bootloader from Sammy.
B3311 said:
@ÆROMIND - did you solve it?
Click to expand...
Click to collapse
I didn't, basically because i was waiting for a reply, but nothing. The reason that i didn't try to solve the problem, it's because i don't really know what will happen to my S6 (and this was so annoying cause i flashed stock firmware to fix the ''recovery is not seandroid enforcing'' like 6 times, and as you can understand , I didn't want to do it again), and probably nothing good would come out.
Anyways, i will not leave this thread, so keep leaving comments to solve this problem in community. Thanks to all
ÆROMIND said:
I didn't, basically because i was waiting for a reply, but nothing. The reason that i didn't try to solve the problem, it's because i don't really know what will happen to my S6 (and this was so annoying cause i flashed stock firmware to fix the ''recovery is not seandroid enforcing'' like 6 times, and as you can understand , I didn't want to do it again), and probably nothing good would come out.
Anyways, i will not leave this thread, so keep leaving comments to solve this problem in community. Thanks to all
Click to expand...
Click to collapse
I (as many others) had your problems. Me (and others) solved it by installing 3.0.2-1 for note 5 noblelte. Works perfect.
I'm on a G928F Latest firmware.
thools60 said:
I (as many others) had your problems. Me (and others) solved it by installing 3.0.2-1 for note 5 noblelte. Works perfect.
I'm on a G928F Latest firmware.
Click to expand...
Click to collapse
Are you sure? Okey, as you say it works, I'm going to try it, if that solve the problem, you will helped me so much!!
B3311 said:
@ÆROMIND - It's possible @Rainbow_Dash is correct, but if you did as you said and had checked version, compatibility etc, try this first:
After installing TWRP, as soon as the screen goes dark when rebooting - and you have to be quick - hit the volume up/power/home buttons simultaneously and keep them pressed. You should reboot into recovery.
I had the same problem, this worked. The "recovery is not seandroid enforcing" is normal btw.
Click to expand...
Click to collapse
Awesome! I was having problem into going into twrp on a Galaxy s6 and this fixed it! =D
Hello
My phone suddenly faced a bootloop, i was on cyanogen 13. just looping the Lenovo logo. Not able to get into recocery.. But QFIL detecting phone, and i even flashed the kitkat version of stock.. The process shows success but still im stuck at bootloop, even tried various method.. Your valuable help appreciated here
any help ?
mjtirur said:
any help ?
Click to expand...
Click to collapse
I think it's some hardware problem. The phone when first came to market has one of the best specifications. Other players had significantly higher prices of their phones providing same hardware. So, I think that Lenovo compromised on the hardware components to provide the SD410 and 2gigs of RAM for this price. I many times had problems with proximity and light sensor. Also the battery sometimes awkwardly dies giving very bad backup and only when you decide to replace it, it automatically starts working fine, for some time atleast. Then same thing happens again.
So, I think its problem with some hardware component. Otherwise, flashing from QFIL successfully, would have unbricked the phone.
Im facing the exact same problem as of now...
Managed to boot into recovery somehow and flashed a ROM but then again it went back to bootloop while unlocking the lockscreen
i have solution.
First off all remove battery then insert it again , after this press vol. Up + vol. Down + power on button by doing this your device completely boot recovery which one is now installed with software.
You said previously that your device is on only showning logo , its mean you have 60℅ chance to get your device in working condition.
Bro if you flashed stock kikat firmware then without flashing any software again just simply flash kitkat twrp recovery through adb . After this flash any kitkat rom ( recommended cm 11 by ed300 ) , huree you get your device live.
OR
If you recently flashed stock lolipop then without flashing any software again just simply flash lolipop twrp recovery through adb . After this flash any lolipop based or marshmallow based or naughat based rom , after that any rom from these android version will work , hurreee you got your phone alive but remember dont again directly flash kitkat rom over any lollipop , marshmallow, naughat rom otherwise you will again got bootloop . But you can directly only flash stock kitkat over stock lolipop or stock lolipop over stock kitkat only . I hope you understand what to do :good:
If you have any problem you can simply tell me via my WhatsApp no. - +91 9205097520 (indian no.) Or simply reply me on xda or simply mail me - [email protected] . I have other tricky solution steps ,which were really used and tested by me. Bye friends.......... And Don't forget to tell me about your device problem .
sasukay said:
I think it's some hardware problem. The phone when first came to market has one of the best specifications. Other players had significantly higher prices of their phones providing same hardware. So, I think that Lenovo compromised on the hardware components to provide the SD410 and 2gigs of RAM for this price. I many times had problems with proximity and light sensor. Also the battery sometimes awkwardly dies giving very bad backup and only when you decide to replace it, it automatically starts working fine, for some time atleast. Then same thing happens again.
So, I think its problem with some hardware component. Otherwise, flashing from QFIL successfully, would have unbricked the phone.
Click to expand...
Click to collapse
Okey Bro
nk41319 said:
First off all remove battery then insert it again , after this press vol. Up + vol. Down + power on button by doing this your device completely boot recovery which one is now installed with software.
You said previously that your device is on only showning logo , its mean you have 60℅ chance to get your device in working condition.
Bro if you flashed stock kikat firmware then without flashing any software again just simply flash kitkat twrp recovery through adb . After this flash any kitkat rom ( recommended cm 11 by ed300 ) , huree you get your device live.
OR
If you recently flashed stock lolipop then without flashing any software again just simply flash lolipop twrp recovery through adb . After this flash any lolipop based or marshmallow based or naughat based rom , after that any rom from these android version will work , hurreee you got your phone alive but remember dont again directly flash kitkat rom over any lollipop , marshmallow, naughat rom otherwise you will again got bootloop . But you can directly only flash stock kitkat over stock lolipop or stock lolipop over stock kitkat only . I hope you understand what to do :good:
Click to expand...
Click to collapse
Thanks bro... i will try this and let you know !!!
AmythD said:
Im facing the exact same problem as of now...
Managed to boot into recovery somehow and flashed a ROM but then again it went back to bootloop while unlocking the lockscreen
Click to expand...
Click to collapse
yes man gonna try the above solution.. lets c
Hi guys, today I made a big mistake by thinking that it would be so easy to root on my S5 +, I was wrong, because it appear that I had the bootloop problem, i resolved it by mistake i was so lucky, I tried to put a BootLoader on Odin on AP section, an error occured on my phone, It reset it and it did come back to life Yeah WTF right ? So now that i've got my phone back ! I'm happy but still, I'm worry about my sim and I want to know if someone is listening to me (because strange things happened lately), that's why I did some research and It appear that an app does exist to prevent such thing ! it's called Snoopsnitch, Amazing isn't it ?
I've got hope that you might be able to help me to root my phone properly this time and avoiding the loopboot issue. If you can led me to do it, it would be amazing.
There is my config. I wish you a good day, night or whatever you are doing on this planet. Kiss. :victory:
https:// ibb.co/FqssRkM
https:// ibb.co/5BPrc7p
Sorry i'm new and i'm not allowed to share my image link so I had to trick the system ><
Thanks for your time and your answers guys. :highfive:
Oh hi, im having the boot loop / logo problem too.
could you explain more clearly what you did to resolve that and is it still good to this day?
ive already used odin3 v3.11 and put the latest stock firmware successfully but the phone still boot loops or if lucky it will get passed the carrier screen (O2) but then as soon as i restart the phone it will boot loop again. (or boot loop randomly, if i dont restart it myself, eventually).
I havent tried TWRP or PIT as im a basic user and just wanted the stock rom.
Any updated advice? ...im worried its the memory/emmc/hardware prob
thanks