Related
Phone stuck on "Samsung - Custom" screen after creating TWRP backup. Help please?
I have an ATT S4, that has had CM 10.1 on it running flawlessly pretty much since nightlies started to get released. Decided to try going back to some TW based ROMs. Running the latest nightly, loaded up TWRP, created a backup, as I usually do before swapping roms. Created the backup fine, now it won't boot, it just sits at the Samsung screen with the lock and Custom message. Wiped cache\dalvic, even tried restoring from the backup I just created. Nothing. Tried it with the phone plugged into the computer and without being plugged in (I think I recall it being plugged into USB could cause issues in the past), and still nada. Tried pulling the battery and rebooting about 10 times. Can get into recovery and odin mode perfectly fine still. Any suggestions or ideas? Thanks
Simonzi said:
I have an ATT S4, that has had CM 10.1 on it running flawlessly pretty much since nightlies started to get released. Decided to try going back to some TW based ROMs. Running the latest nightly, loaded up TWRP, created a backup, as I usually do before swapping roms. Created the backup fine, now it won't boot, it just sits at the Samsung screen with the lock and Custom message. Wiped cache\dalvic, even tried restoring from the backup I just created. Nothing. Tried it with the phone plugged into the computer and without being plugged in (I think I recall it being plugged into USB could cause issues in the past), and still nada. Tried pulling the battery and rebooting about 10 times. Can get into recovery and odin mode perfectly fine still. Any suggestions or ideas? Thanks
Click to expand...
Click to collapse
There are no less than a dozen similar threads about similar problems already. Have you looked at those threads for a possible solution yet? You can find them by using the search function or better yet just doing a visual search of the first few pages of the "General" and "Q&A" sections. Good luck.
Sounds like a ROM and kernel issue. Try flashing a ROM with a loki'd kernel.
Tylorw1
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Tylorw1 said:
Sounds like a ROM and kernel issue. Try flashing a ROM with a loki'd kernel.
Tylorw1
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
I don't see how that could be the case. I didn't flash anything. I just loaded TWRP, created a backup, and rebooted my phone. No ROM\kernel change. Nothing more than creating a backup in TWRP.
scott14719 said:
There are no less than a dozen similar threads about similar problems already. Have you looked at those threads for a possible solution yet? You can find them by using the search function or better yet just doing a visual search of the first few pages of the "General" and "Q&A" sections. Good luck.
Click to expand...
Click to collapse
I tried searching, the closest one I could find on the first few pages was this one. I just didn't see any specific to my situation because nothing was flashed. Like my response to Tylorw1, all I did was boot into recovery, create a backup, and reboot my phone. Didn't flash a ROM, change a kernel, format anything, etc...
I has this same problem... It happened after every single reboot after flashing various ROMs or anything.. I gave up and went back to CWM and haven't had the problem since :good:
Sent from my SGH-I337 using xda app-developers app
Simonzi said:
I have an ATT S4, that has had CM 10.1 on it running flawlessly pretty much since nightlies started to get released. Decided to try going back to some TW based ROMs. Running the latest nightly, loaded up TWRP, created a backup, as I usually do before swapping roms. Created the backup fine, now it won't boot, it just sits at the Samsung screen with the lock and Custom message. Wiped cache\dalvic, even tried restoring from the backup I just created. Nothing. Tried it with the phone plugged into the computer and without being plugged in (I think I recall it being plugged into USB could cause issues in the past), and still nada. Tried pulling the battery and rebooting about 10 times. Can get into recovery and odin mode perfectly fine still. Any suggestions or ideas? Thanks
Click to expand...
Click to collapse
what version of twrp? if it is 2.6.?.? then get off of it, also, what I did was pull battery for 3min, it booted fine....go back to early version of twrp...
STVERDI said:
I has this same problem... It happened after every single reboot after flashing various ROMs or anything.. I gave up and went back to CWM and haven't had the problem since :good:
Sent from my SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
I've wanted to go back to CWM. That's what I had on my S3. Only thing stopping me, is all my nandroid backups for my S4 are done with TWRP, and I don't want to run into a situation where I need them, and them not being compatible
TheAxman said:
what version of twrp? if it is 2.6.?.? then get off of it, also, what I did was pull battery for 3min, it booted fine....go back to early version of twrp...
Click to expand...
Click to collapse
Nope, still on 2.5.0.2. Finally, after a third complete wipe/format and restore from the back I had created (the one that started the whole issue), it works fine. Such a huge pain in the ass.
a user had to boot back into twrp and wipe data/factory reset yesterday to fix this issue.
Simonzi said:
I've wanted to go back to CWM. That's what I had on my S3. Only thing stopping me, is all my nandroid backups for my S4 are done with TWRP, and I don't want to run into a situation where I need them, and them not being compatible
Nope, still on 2.5.0.2. Finally, after a third complete wipe/format and restore from the back I had created (the one that started the whole issue), it works fine. Such a huge pain in the ass.
Click to expand...
Click to collapse
And you have to be ****ing kidding me. I rebooted into recovery while typing my initial response, just to verify I was still on the 2.5.x.x TWRP. Booted up TWRP, verified that, choose "Reboot System", and same thing. Back to sitting at the Samsung screen. Nandroid backups or not, ditching TWRP as soon as I get it able to boot back up.
Even worse off now than when I started. After my last post, where my phone was doing the same "stuck on Samsung logo" thing, just from booting into TWRP, I decided to swap to a different recovery. Searched for "switch from TWRP to CWM", and found my own post I had made a few months ago, but never went through.
Following those instructions now, I decided on the PhilZ CWM. Head over to that thread, grab the loki'd zip, load up TWRP, and flash the zip. Now I can't even boot into recovery!! It just freezes on the Samsung screen with the blue "recovery booting" text.
Can still get into download mode, so I tried using ODIN to flash PhilZ jflteatt.tar.md5 file, and it fails.
At this point, waiting for the stock 1.6 firmware package to download, so I can just ODIN that.
If anyone has any other suggestions though, they'd be great. Have an hour to try while waiting for that to download
somebody had mentioned this...
http://forum.xda-developers.com/showpost.php?p=44629460&postcount=8
make sure you have the correct firmware and proceed as you are. likely your best bet.
Simonzi said:
Even worse off now than when I started. After my last post, where my phone was doing the same "stuck on Samsung logo" thing, just from booting into TWRP, I decided to swap to a different recovery. Searched for "switch from TWRP to CWM", and found my own post I had made a few months ago, but never went through.
Following those instructions now, I decided on the PhilZ CWM. Head over to that thread, grab the loki'd zip, load up TWRP, and flash the zip. Now I can't even boot into recovery!! It just freezes on the Samsung screen with the blue "recovery booting" text.
Can still get into download mode, so I tried using ODIN to flash PhilZ jflteatt.tar.md5 file, and it fails.
At this point, waiting for the stock 1.6 firmware package to download, so I can just ODIN that.
If anyone has any other suggestions though, they'd be great. Have an hour to try while waiting for that to download
Click to expand...
Click to collapse
Stock 1.6 firmware package?
Make sure you get the correct firmware? Go to SamMobile and get the stock firmware from there or go to Adam Outlers "Stock firmware ODIN" thread in the General section (the AMDL firmware link is in that thread you just have to look for it).
scott14719 said:
Stock 1.6 firmware package?
Make sure you get the correct firmware? Go to SamMobile and get the stock firmware from there or go to Adam Outlers "Stock firmware ODIN" thread in the General section (the AMDL firmware link is in that thread you just have to look for it).
Click to expand...
Click to collapse
Yeah, I meant 1.6gb firmware package. Just forgot the "gb". That's what I'm currently downloading, but trying to recover it with Kies while waiting.
I would like to report I had the same problem.
After changing roms and making a nandroid, and then deciding to switch roms again, I ran into the stuck at Samsung Custom with a lock boot screen. Most roms would boot up once, but a restart or power down would lead to being stuck. I was flashing through TWRP.
I went into TWRP and flashed OUDHS recovery which overrode TWRP and wiped/flashed through OUDHS a new rom.
Problem solved.
S3 at&t stuck in TWRP booting screen.
xBeerdroiDx said:
a user had to boot back into twrp and wipe data/factory reset yesterday to fix this issue.
Click to expand...
Click to collapse
Im new to custom roms, I pressed ok for an update on my phone, after the update was complete my phone shut off and booted into TWRP and now I can't get back to my android screen nor make calls etc. HELPPPPPPPP PLEASSSSSEE I have been trying to fix my phone since july and I have been using this cheap phone that don't even get internet. I have an S3 1747 at&t
Lnjames said:
Im new to custom roms, I pressed ok for an update on my phone, after the update was complete my phone shut off and booted into TWRP and now I can't get back to my android screen nor make calls etc. HELPPPPPPPP PLEASSSSSEE I have been trying to fix my phone since july and I have been using this cheap phone that don't even get internet. I have an S3 1747 at&t
Click to expand...
Click to collapse
Wrong forum. Please go to the s3 section with your question.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Had this problem just now, solved it by fixing permissions.
I am running an MDL based S4, and screwed the pooch. I was going to wipe the internal storage and made the mistake of doing it through TWRP 2.5. Now, I have the same problem of being stuck on the custom boot screen. I have tried to change from TWRP to OUDHS Recovery, but still boot loops to Custom screen. I have tried fresh installs of 4.2 ROMs and 4.4.2 Google Editions. Do I need to flash via ODIN?
Flame away....I know better than this!!!!
Help would be greatly appreciated.
Sent from my GT-N8013 using Tapatalk 4
So I'm pretty desperate and I apologize if similar info was posted somewhere else. I've been researching several hours but couldn't find anything.
I originally installed CM11 and decided to experiment with a different rom TriForce ROM [TouchWiz]. I put the zip file on my SD card and booted into clockworkmod it gave an error of bad zip. I tried different usb port to transfer the zip, downloaded it multiple times with no result. So I decided to try a different rom Stock_Rooted_Deodexed_MF9_Rom.zip. The installation finished but the phone would not boot.
Recently I flashed the stock rom from odin, it finished successfully but still not boot, Galaxy sreen lights up quickly and that's it.
rmngorelov said:
So I'm pretty desperate and I apologize if similar info was posted somewhere else. I've been researching several hours but couldn't find anything.
I originally installed CM11 and decided to experiment with a different rom TriForce ROM [TouchWiz]. I put the zip file on my SD card and booted into clockworkmod it gave an error of bad zip. I tried different usb port to transfer the zip, downloaded it multiple times with no result. So I decided to try a different rom Stock_Rooted_Deodexed_MF9_Rom.zip. The installation finished but the phone would not boot.
Recently I flashed the stock rom from odin, it finished successfully but still not boot, Galaxy sreen lights up quickly and that's it.
Click to expand...
Click to collapse
Restore from nandroid backup. I hope you made one. Try going into recovery do a factory reset and wipe all cache and data and what not and then install a ROM from Odin.
rmngorelov said:
So I'm pretty desperate and I apologize if similar info was posted somewhere else. I've been researching several hours but couldn't find anything.
I originally installed CM11 and decided to experiment with a different rom TriForce ROM [TouchWiz]. I put the zip file on my SD card and booted into clockworkmod it gave an error of bad zip. I tried different usb port to transfer the zip, downloaded it multiple times with no result. So I decided to try a different rom Stock_Rooted_Deodexed_MF9_Rom.zip. The installation finished but the phone would not boot.
Recently I flashed the stock rom from odin, it finished successfully but still not boot, Galaxy sreen lights up quickly and that's it.
Click to expand...
Click to collapse
Make sure you're using roms for your version of your phone. the MF9 bootloader is really old and probably wont install anymore. My phone did this before and I thought I bricked it, but I kid you not I took the battery out and removed the SIM card and rebooted and it booted up just fine. May not work for you, but I suggest you go back to update stock firmware then try again. If you're using the triband model, there's a post around here somewhere with confirmed roms that wont brick your device. I'm currently using the Google Play Edition Stock ROM and it's working GREAT.
Link for new firmware (NG5 Firmware): https://mega.co.nz/#F!0JdRkIZR!AqqKdbvba_Hpg5VrCmrbPw
i7vSa7vi7y said:
Restore from nandroid backup. I hope you made one. Try going into recovery do a factory reset and wipe all cache and data and what not and then install a ROM from Odin.
Click to expand...
Click to collapse
I restored to this stock ROM before and everything worked well. Currently I can't boot into recovery, Samsung flashes once and that's it, that's why I'm desperate the only thing I can do is boot in to download mode for odin.
silentdeath631 said:
Make sure you're using roms for your version of your phone. the MF9 bootloader is really old and probably wont install anymore. My phone did this before and I thought I bricked it, but I kid you not I took the battery out and removed the SIM card and rebooted and it booted up just fine. May not work for you, but I suggest you go back to update stock firmware then try again. If you're using the triband model, there's a post around here somewhere with confirmed roms that wont brick your device. I'm currently using the Google Play Edition Stock ROM and it's working GREAT.
Link for new firmware (NG5 Firmware):
Click to expand...
Click to collapse
Does it matter that I can't get into recovery to clear the cache first before trying new roms?
silentdeath631 said:
Make sure you're using roms for your version of your phone. the MF9 bootloader is really old and probably wont install anymore. My phone did this before and I thought I bricked it, but I kid you not I took the battery out and removed the SIM card and rebooted and it booted up just fine. May not work for you, but I suggest you go back to update stock firmware then try again. If you're using the triband model, there's a post around here somewhere with confirmed roms that wont brick your device. I'm currently using the Google Play Edition Stock ROM and it's working GREAT.
Link for new firmware (NG5 Firmware):
Click to expand...
Click to collapse
Maybe I'm doing something foolish but every time I try to download files from the link you gave I get a decryption error so I can't download them zip or original.
rmngorelov said:
I restored to this stock ROM before and everything worked well. Currently I can't boot into recovery, Samsung flashes once and that's it, that's why I'm desperate the only thing I can do is boot in to download mode for odin.
Click to expand...
Click to collapse
Just hold home power and volume up. Right when you see text at the top left let go. You have to have the right timing
i7vSa7vi7y said:
Just hold home power and volume up. Right when you see text at the top left let go. You have to have the right timing
Click to expand...
Click to collapse
After almost eight hours of troubleshooting I finally got it to work.
I've tried flashing clockworkmod several times to see if I could get into recovery with no result so I gave up on that and I flashed the newest stock rom I could find L720VPUFNG2_L720SPTFNG2_SPR and it was still not booting. Than I thought maybe twerp would make a difference and god almighty it finally booted! I felt as if I gave birth to a child after eight hours of labor!
Now I'm extremely paranoid about touching anything because it took me forever to do this. Does anyone know why flashing twerp would make such a difference? I know this sort of stuff can get extremely complicated but I'd like to try to understand.
I hope my foolish agony contributed to this community if not in any other way except by the comedic relief caused by my ignorance.
rmngorelov said:
After almost eight hours of troubleshooting I finally got it to work.
I've tried flashing clockworkmod several times to see if I could get into recovery with no result so I gave up on that and I flashed the newest stock rom I could find L720VPUFNG2_L720SPTFNG2_SPR and it was still not booting. Than I thought maybe twerp would make a difference and god almighty it finally booted! I felt as if I gave birth to a child after eight hours of labor!
Now I'm extremely paranoid about touching anything because it took me forever to do this. Does anyone know why flashing twerp would make such a difference? I know this sort of stuff can get extremely complicated but I'd like to try to understand.
I hope my foolish agony contributed to this community if not in any other way except by the comedic relief caused by my ignorance.
Click to expand...
Click to collapse
Depends what recovery you had and what version. I personally like Philz touch recovery but TWRP is good. Now wipe and flash a ROM my friend or restore a backup
rmngorelov said:
After almost eight hours of troubleshooting I finally got it to work.
I've tried flashing clockworkmod several times to see if I could get into recovery with no result so I gave up on that and I flashed the newest stock rom I could find L720VPUFNG2_L720SPTFNG2_SPR and it was still not booting. Than I thought maybe twerp would make a difference and god almighty it finally booted! I felt as if I gave birth to a child after eight hours of labor!
Now I'm extremely paranoid about touching anything because it took me forever to do this. Does anyone know why flashing twerp would make such a difference? I know this sort of stuff can get extremely complicated but I'd like to try to understand.
I hope my foolish agony contributed to this community if not in any other way except by the comedic relief caused by my ignorance.
Click to expand...
Click to collapse
im having similar issues. which version of TWRP worked for you?
thank you
fearthemarchx said:
im having similar issues. which version of TWRP worked for you?
thank you
Click to expand...
Click to collapse
I recommend flashing the newest one here using odin
http://teamw.in/project/twrp2
Then once you are able to boot into recovery go to wipe and perform both factory reset and format data. Then install whatever rom you like, I used Sprint Galaxy S4 SPH-L720 VPUFNAE (Androdi 4.4.2) found here
http://galaxys4root.com/galaxy-s4-stock-firmware/ (or maybe find a newer stock rom if this one gives you errors)
Just copy the zip file to the phone, boot into twrp, do wipe factory reset again, select install then select the zip in whatever directory and you should be good to go. Make sure you do a back up in twrp once you get the phone to boot so you can always revert to stock.
I hope I was thorough enough that some of the information was useful. Let me know if you need any more help.
only certain recoveries will stick. ive tried the most recent twrp, with no luck. only a few versions of philztouch work.
Sent from my LGL34C using XDA Free mobile app
fearthemarchx said:
only certain recoveries will stick. ive tried the most recent twrp, with no luck. only a few versions of philztouch work.
Sent from my LGL34C using XDA Free mobile app
Click to expand...
Click to collapse
Format with philztouch that works then try flashing a new stock rom with odin. That should bring everything back to stock including the recovery.
ive tried. when i flash rom via odin i only get a blue "recovery booting" at the top of boot screen. even when i only power on, not into recovery. im going to attempt to flash rom provided in previous post via philz.
Sent from my LGL34C using XDA Free mobile app
fearthemarchx said:
ive tried. when i flash rom via odin i only get a blue "recovery booting" at the top of boot screen. even when i only power on, not into recovery. im going to attempt to flash rom provided in previous post via philz.
Sent from my LGL34C using XDA Free mobile app
Click to expand...
Click to collapse
You're in download mode when you flash from odin right? If you your getting an error flashing, try a different stock rom after reformating/resetting to factory (it's crucial to clear the cache before trying a different rom). I had to try a few roms before I found one that worked.
Hey wassup. So yesterday I rooted my phone and tried to install CM13 on it. Took a few tries since the rom I got was corrupted but I got it to work. Then I noticed it was guzzling the battery like lemonade (this EXACT same thing happened on my previous S4 too) so I gave up on it and decided to revert back to the stock rom. Everything went well... NOT. I downloaded the stock firmware (3gigs... zzz) and I flashed it with Odin and the phone restarted. The little android robot from the default unrooted recovery popped up and it had below it this: "Installing system update..." and then out of the blue it said "Erasing" and it's gear started rotating backwards. THEN, when it finished the normal Samsung Galaxy Note 4 logo popped up, went away and then CAME BACK AGAIN FOR LIKE 500 TIMES AND COUNTING. AOSP roms work just fine, it's just that touchwiz ones won't work whatsoever (even tried sixperience, no luck)... What should I do? I already lost my S4 due to this...
install TWRP custom recovery, boot up in recovery format system dalvik cache and internal storage then try flashing stock with odin hopefully it will work.
Try to remove battery first.from tsoch recovery wipe data cache and see if it works
dork997 said:
install TWRP custom recovery, boot up in recovery format system dalvik cache and internal storage then try flashing stock with odin hopefully it will work.
Click to expand...
Click to collapse
Been there, done that. Nope, still refuses to work :/
bumpity bump bump
Did you backup your efs partition before you flashed cm13? If not you corrupted your efs and your phone is a wifi tablet now because you cant use your modem.
travis82 said:
Did you backup your efs partition before you flashed cm13? If not you corrupted your efs and your phone is a wifi tablet now because you cant use your modem.
Click to expand...
Click to collapse
this never happened to me with my old s2 or s4
why is it happening now ?
Didn't backup. Now it just won't even work with odin. Whenever I try to just flash anything with it goes off and says 0 successes and 0 fails. What I did notice though was that whenever I installed a stock rom it starts this "Installing system update" with the android robot twingling it's antennaes and then out of nowhere it's blue bar goes away and it says "Erasing" then... bootloop. Now odin won't even work (explained above). Should I just give up and send it in for repairing? Or can ANYONE send me the twrp restore file, please...
Peontikos_Desmos said:
Didn't backup. Now it just won't even work with odin. Whenever I try to just flash anything with it goes off and says 0 successes and 0 fails. What I did notice though was that whenever I installed a stock rom it starts this "Installing system update" with the android robot twingling it's antennaes and then out of nowhere it's blue bar goes away and it says "Erasing" then... bootloop. Now odin won't even work (explained above). Should I just give up and send it in for repairing? Or can ANYONE send me the twrp restore file, please...
Click to expand...
Click to collapse
Hi
Same problem
Any ideas !!!
Hey,
I have the same problem it turns out after flashing, i cant remember, maybe dytto note 4 rom, it got stuck in continous bootloops and the only way it is working for me is when its charging. I know it sounds crazy but its the only way for me, ive tried installing stock different countries firmware and bunch of custom rom with no luck. I sent it to the place where i bought the phone and made myself look dumb asking why it is like that and i told them i had not do anything. After only a week they phoned me and said it was rooted (i did get the root out when i gave it but they somehow knew it was... later i understood that it is all about that stupid Know thing) and refused to cover my warranty. They said that the only way i can get it to work is to pay 300$ for new chip :,(
senon said:
Hey,
I have the same problem it turns out after flashing, i cant remember, maybe dytto note 4 rom, it got stuck in continous bootloops and the only way it is working for me is when its charging. I know it sounds crazy but its the only way for me, ive tried installing stock different countries firmware and bunch of custom rom with no luck. I sent it to the place where i bought the phone and made myself look dumb asking why it is like that and i told them i had not do anything. After only a week they phoned me and said it was rooted (i did get the root out when i gave it but they somehow knew it was... later i understood that it is all about that stupid Know thing) and refused to cover my warranty. They said that the only way i can get it to work is to pay 300$ for new chip :,(
Click to expand...
Click to collapse
ffs i'm not paying another phone's worth in a ****ing motherboard. I tried:
-Flashing the stock bootloader, fails at sboot.img:NAND Write start fail
-Flashing the PIT file, just... wont flash. Successes 0/Fails 0
-Flashing the stock AP file, bootloop
-Flashing the CP and the CSC stock files, serial(com) port cannot be opened.
****ing garbage. For some reason my phone's the only exception to the rule that phones able to boot into download mode are salvageable. It's going in for a repair and if it's more than $50 I'm not rooting again even at gunpoint.
Quick update:
I found a toolkit that has a flash stock boot image option. Had to recover to my cm13 backup to enable usb debugging. Will post results
Nothing of course...
try this step by step,
1. Download stock firmware THE LATEST ONE (n910c v5.1.1) from sammobile.com
2. Download newest Odin and Samsung USB; installed Samsung USB
3. I am assuming you have installed twrp recovery. Boot to twrp recovery and do a full wipe; wipe all!
4. Boot to downloading mode and install stock via odin. That is it.
Ps.... in case of failure, make sure you have installed Samsung USB! Or just reconnect usb cable with other usb ports untill it is working.
Never flach cm if doesn'T HAVE a efs backup if not you will stuck with cm
Oliva.raiders said:
1. Download stock firmware THE LATEST ONE (n910c v5.1.1) from sammobile.com
2. Download newest Odin and Samsung USB; installed Samsung USB
3. I am assuming you have installed twrp recovery. Boot to twrp recovery and do a full wipe; wipe all!
4. Boot to downloading mode and install stock via odin. That is it.
Ps.... in case of failure, make sure you have installed Samsung USB! Or just reconnect usb cable with other usb ports untill it is working.
Click to expand...
Click to collapse
Well, crap I already sent it in for repairing but if the fuqing robbers decide to change the motherboard instead of doing anything to it and charge me 500$ to do so I'm getting it back and I'm trying this one. Already did but it wouldn't hurt retrying... BTW FOR THE LOVE OF GOD DOES SOMEONE HAVE A TWRP BACKUP FILE ON STOCK TOUCHWIZ? JESUS
radium56ad said:
Never flach cm if doesn'T HAVE a efs backup if not you will stuck with cm
Click to expand...
Click to collapse
Is there absolutely NO workaround?
i had the same issue, this is how i solved this (you won't like it):
-deleted efs partition
-restored 5.1.1 coj5 via odin
-then took it to a samsung repair center to restore the imei
paid them like 50 bucks...that sucks. after this im backing up efs folder before flashing a rom.
radium56ad said:
Never flach cm if doesn'T HAVE a efs backup if not you will stuck with cm
Click to expand...
Click to collapse
JuanWilliman said:
i had the same issue, this is how i solved this (you won't like it):
-deleted efs partition
-restored 5.1.1 coj5 via odin
-then took it to a samsung repair center to restore the imei
paid them like 50 bucks...that sucks. after this im backing up efs folder before flashing a rom.
Click to expand...
Click to collapse
Oh that's nothing man. The fuqing scammers told me the whole freaking board had to be replaced...
There's one thing I've noticed though that's PROBABLY gotta be the culprit. Whenever I install a touchwiz rom, the phone boots up fine for once, shows the robot with the "Installing system update" and then it goes off with "Erasing" followed by the bootloop. Could anyone please elaborate on this? I have a feeling this is what's causing this ****fest
I installed the twrp app on my rooted samsung s7 edge, it downloaded and installed the image, now when rebooting all i have is a red screen? someone please help
thanks
nevermind all sorted now phew
stephenuk said:
nevermind all sorted now phew
Click to expand...
Click to collapse
How did you sort it out?
Flame_Beard said:
How did you sort it out?
Click to expand...
Click to collapse
Reinstall twtp agaim that worked for me
Sent from my SM-G935F using XDA-Developers mobile app
Flame_Beard said:
How did you sort it out?
Click to expand...
Click to collapse
Used an older version through odin
This ended up being sorted for me, as it just booted after about a half hour. But how, if you hit this red screen can you reflash? You aren't getting to dowload mode or recovery with that perma-red screen
lol, I spoke too soon again, was reflashing twrp after going back to a stock rom, this happened again for me only its not budging from red screen now. I can't get into download mode as I mentioned above too
hey guys I have the same
the phone dont even switch off
how did you fix it?
edit SOLUTION : I managed to reboot the phone with adb
add reboot
then I flashed the version 3.0.0.0 of TWRP and it worked !
Help!
stephenuk said:
I installed the twrp app on my rooted samsung s7 edge, it downloaded and installed the image, now when rebooting all i have is a red screen? someone please help
thanks
Click to expand...
Click to collapse
I rooted my phone, had twrp recovery successfully. then i tried to install xposed and it was probably the wrong version. tried to use odin to get the stock rom, but the screen is only red, and i can hear the volume sounds... any help?
sammobile.com/firmwares/database/SM-G935F/TEN/ i used the newest version
adrianbjorvatn said:
I rooted my phone, had twrp recovery successfully. then i tried to install xposed and it was probably the wrong version. tried to use odin to get the stock rom, but the screen is only red, and i can hear the volume sounds... any help?
sammobile.com/firmwares/database/SM-G935F/TEN/ i used the newest version
Click to expand...
Click to collapse
I am having the same problem. Odin is stuck in "Setup Connection"
Do you have any ideas?
Thanks
You have probably flashed a wrong kernel.
The solution is to flash the right kernel for your device.
I was flashing S7 root on S7Edge
Flame_Beard said:
How did you sort it out?
Click to expand...
Click to collapse
i just used an earlier version
julien32 said:
how did you fix it?
edit SOLUTION : I managed to reboot the phone with adb
add reboot
then I flashed the version 3.0.0.0 of TWRP and it worked !
Click to expand...
Click to collapse
Thank you very much, worked for me!:good:
i tryed the posted solutions, but won´t work for me.
I found a another version an flash it, so that the red sceen is gone, but this was the wrong version.. so i tried to flash the right twrp image, but odin freezes everytime...
what can i try?
Hi Guys,
I flashed everything stock after having some issues with encrypton and a custom ROM.
After flashing twrp-3.1.1-0-herolte.img with Odin 3.17 I only get a red screen when booting into recovery and the phone won't even boot the OS.
Any idea how to get TWRP working so I can get back to a custom ROM?
Thanks,
Nicolas
Edit: Hero2lte worked
flashed ****ty rom /** THE GALAXY PROJECT **/ with twrp + themes and hard bricked my phone
my usb doesnt work, just for charging, i was told something gone on my mobo of s7 edge.
i can boot into download mode but nothing to do without pc...
Nikouy said:
Hi Guys,
I flashed everything stock after having some issues with encrypton and a custom ROM.
After flashing twrp-3.1.1-0-herolte.img with Odin 3.17 I only get a red screen when booting into recovery and the phone won't even boot the OS.
Any idea how to get TWRP working so I can get back to a custom ROM?
Thanks,
Nicolas
Edit: Hero2lte worked
Click to expand...
Click to collapse
you are a live saver!!i love you!!!
juda iskariotsky said:
flashed ****ty rom /** THE GALAXY PROJECT **/ with twrp + themes and hard bricked my phone
my usb doesnt work, just for charging, i was told something gone on my mobo of s7 edge.
i can boot into download mode but nothing to do without pc...
Click to expand...
Click to collapse
Lol. I have the very same problem: Flashed The Galaxy Project ROM and hit "update bootloader etc...." and now all I have is this red screen..... - Though the ROM worked for a couple of hours, but when I tried to enter the recovery I stock with this red screen. Cant even go into download mode...
Any help? How did you solved this issue?
I didn't, ****ty Rom just bricked it.
Just reflash the recovery or flash stock. I can't, my pc doesn't recognize my s7 anymore.
He doesn't even bother to mention that bug...
NandorHUN said:
Lol. I have the very same problem: Flashed The Galaxy Project ROM and hit "update bootloader etc...." and now all I have is this red screen..... - Though the ROM worked for a couple of hours, but when I tried to enter the recovery I stock with this red screen. Cant even go into download mode...
Any help? How did you solved this issue?
Click to expand...
Click to collapse
Same here. Only in my case I use this ROOM for weeks
I jumped in to this without making a backup, I have successfully rooted plenty of phones but was careless. This phone has a problem with the battery so it died while I was flashing the phone. I've tried using Odin to put Stock Tar but it fails, also have tried a few other Rom's but it fails. When in recovery trying to flash from SD i get a fail so now i have no backup no os is there any hope? In CWM i got it to load N910PVPS4DPK1 deodexed rom but upon reboot it stays in bootloop. Any and all help is welcome Thank you in advance.
dj trek said:
I jumped in to this without making a backup, I have successfully rooted plenty of phones but was careless. This phone has a problem with the battery so it died while I was flashing the phone. I've tried using Odin to put Stock Tar but it fails, also have tried a few other Rom's but it fails. When in recovery trying to flash from SD i get a fail so now i have no backup no os is there any hope? In CWM i got it to load N910PVPS4DPK1 deodexed rom but upon reboot it stays in bootloop. Any and all help is welcome Thank you in advance.
Click to expand...
Click to collapse
Did you try with a new battery ?
srajx786 said:
Did you try with a new battery ?
Click to expand...
Click to collapse
A new battery was in the mail before i started this project for a friend still waiting. Do you think that would cause this issue?
dj trek said:
A new battery was in the mail before i started this project for a friend still waiting. Do you think that would cause this issue?
Click to expand...
Click to collapse
Tried with a new battery now i can't even get into recovery mode
dj trek said:
Tried with a new battery now i can't even get into recovery mode
Click to expand...
Click to collapse
Back into recovery but reminder is i have no os file system is erased cant get it to accept any rom in odin or through sd card fails all all except one but is still caught in a bootloop once restart begins obviously not able to flash rom any clue as to what is preventing rom to flash?
Well finally some success! Here's what i did.....
dj trek said:
I jumped in to this without making a backup, I have successfully rooted plenty of phones but was careless. This phone has a problem with the battery so it died while I was flashing the phone. I've tried using Odin to put Stock Tar but it fails, also have tried a few other Rom's but it fails. When in recovery trying to flash from SD i get a fail so now i have no backup no os is there any hope? In CWM i got it to load N910PVPS4DPK1 deodexed rom but upon reboot it stays in bootloop. Any and all help is welcome Thank you in advance.
Click to expand...
Click to collapse
https://forum.xda-developers.com/no...basebandsbootloaders-marshmallow-pe2-t3395644
Thanks to Freeza
I flashed the software from here and waited while it rebooted countless times id say about 10-20 times each time getting further and further until finally booted up. Be patient if i had stopped the process i wouldnt have a working rooted SGNE. The first thing i noticed different from other times iv flashed was it went straight into boot up and starting uprgrading android apps,then rebooted and started where it left off got a little further then rebooted again and so on and so forth until it was complete.I immediately made a backup and now have a working rooted SGNE.