Related
After installing my ROM and the GApps, cache was wiped and wiped successfully but then TWM froze, I can't get back into recovery because it freezes on the TeamWin splash screen and I also can't boot into the ROM because it looks like it didn't go through successfully. Any ideas on how to resolve this issue?
Actually resolved the recovery mode issue, but for some reason no matter what I cannot get the ROM to boot any longer. Gets to the loading screen, freezes for a sec after a minute and reboots.
Xoured said:
Actually resolved the recovery mode issue, but for some reason no matter what I cannot get the ROM to boot any longer. Gets to the loading screen, freezes for a sec after a minute and reboots.
Click to expand...
Click to collapse
Restore a nandroid to get your phone running again. Then try to flash the rom. I assume your on mdl firmware.
This didn't work for some reason so not really sure where to go hah.
Xoured said:
This didn't work for some reason so not really sure where to go hah.
Click to expand...
Click to collapse
If you're on mdl firmware, I'd probably Odin the stock firmware and start over again.
Do you happen to have a link to the thread for S4 odin stock on hand? Can look otherwise
Xoured said:
Do you happen to have a link to the thread for S4 odin stock on hand? Can look otherwise
Click to expand...
Click to collapse
I don't. But I get stock firmware from sammobile.com
Hi,
I flashed the google edition rom a few weeks ago, all was working fine. This morning, I decided to flash a stock rom from sammobile (was this a bad idea)? I used CF autoroot and twerp custom recovery. It failed. So wiped everything, reflashed the google edition rom, but when I reboot the phone it gets stuck showing "Samsung galaxy s4" white text.
To boot it again i have to wipe data, cache and dalvik, then reflash the ROM, then qipe cache and dalvik, then it reboots. But when I turn it off then on again the whole process starts again.
Can anybody tell me what I'm doing wrong? This is the same ROM that worked faultlessly for weeks...
Thanks
Did u wait long enough, first reboot after flashing a new rom can take a while.
Sent from my GT-I9505 using XDA Premium HD app
richard2311 said:
Did u wait long enough, first reboot after flashing a new rom can take a while.
Sent from my GT-I9505 using XDA Premium HD app
Click to expand...
Click to collapse
Yeah, I gave it 5 minutes, but it's not even getting to the boot animation.
When I tried to flash the stock rom could that have messed something up? It said failed, then for ages after that, it kept saying "error-failed to open \data\data .... I/O error" in twrp.
To avoid that I have to wipe data seperately, reboot recovery, then flash the ROM again from scratch. Every time I reboot the phone I have to do a full wipe and flash the rom before it even boots..
dickson123 said:
Yeah, I gave it 5 minutes, but it's not even getting to the boot animation.
When I tried to flash the stock rom could that have messed something up? It said failed, then for ages after that, it kept saying "error-failed to open \data\data .... I/O error" in twrp.
To avoid that I have to wipe data seperately, reboot recovery, then flash the ROM again from scratch. Every time I reboot the phone I have to do a full wipe and flash the rom before it even boots..
Click to expand...
Click to collapse
Have a read if this great guide: http://forum.xda-developers.com/showpost.php?p=43340522&postcount=3297
mobileguynz said:
Have a read if this great guide: http://forum.xda-developers.com/showpost.php?p=43340522&postcount=3297
Click to expand...
Click to collapse
Ok, thanks, I'll give it a go later. I'm at work and was hoping for a solution that didn't require ODIN (work PC too locked-down )
dickson123 said:
Ok, thanks, I'll give it a go later. I'm at work and was hoping for a solution that didn't require ODIN (work PC too locked-down )
Click to expand...
Click to collapse
Well depending on which stock ROM you flashed you maybe affected by the enabled SElinux issue see https://plus.google.com/app/basic/stream/z13xxnmzvyeihn00w23wcdp55terwvove
mobileguynz said:
Well depending on which stock ROM you flashed you maybe affected by the enabled SElinux issue see https://plus.google.com/app/basic/stream/z13xxnmzvyeihn00w23wcdp55terwvove
Click to expand...
Click to collapse
I don't understand what the issue is though. I'm not doing anything different than I did 3 weeks ago, and yet this time it doesn't work.
It's now gotten to the stage where it won't boot at all, just sits at the white text, no boot animation.
Is it possible that flashing a stock un-rooted ROM has messed it up somehow? Technically it never flashed because it just failed immediately.
dickson123 said:
I don't understand what the issue is though. I'm not doing anything different than I did 3 weeks ago, and yet this time it doesn't work.
It's now gotten to the stage where it won't boot at all, just sits at the white text, no boot animation.
Is it possible that flashing a stock un-rooted ROM has messed it up somehow? Technically it never flashed because it just failed immediately.
Click to expand...
Click to collapse
If you flashed the latest stock ROM it maybe be one with Knox and that has a secure boot loader and kernel secure Selinux Knox stops you from modifying and installing.
Try using ausdims v16 kernel or wadams Adam kernel for stock roms. Note when I flashed the last ROM waited 10 minutes and had do a wipe and reset for it to boot see last pages for discussion http://forum.xda-developers.com/showthread.php?t=2250824
http://forum.xda-developers.com/showthread.php?t=2250824
So i have the I337m, canadian model S4 on Bell Mobility network, and I"m running SlimRoms with 2.5.0.2 twrp recovery.
Every other reboot, the phone gets stuck on the splash screen, I have no problem to go into recovery mode or anything, this is simply a problem when rebooting and gets stuck on the "Galaxy S4" screen. Here's what I've tried, tried both with TWRP and CWM and TWRP seems better, I don't get stuck on the splash screen as often as CWM. I've reverted back to the "stock ROM" and rerooted and loaded the TWRP recovery, and while it seems better at first, it slowly gets stuck more and more at the splash screen.
I'm running out of ideas, no knowing what do to to improve this problem...
Anyone else having this problem? I'm positive this is not a "ROM" related problem but a recovery problem, yet maybe it's just my phone that's being the problem.
JP
I'll also add that I've never formated data on TWRP... since I've read it gives that problem.
jproy12 said:
I'll also add that I've never formated data on TWRP... since I've read it gives that problem.
Click to expand...
Click to collapse
You have to do a factory reset, wipe data, or you will get a boot loop. Do that and I'm sure you'll get past the boot loop. If you're concerned about the version of twrp you're on, update it.
http://forum.xda-developers.com/showthread.php?p=41010145
jd1639 said:
You have to do a factory reset, wipe data, or you will get a boot loop. Do that and I'm sure you'll get past the boot loop. If you're concerned about the version of twrp you're on, update it.
http://forum.xda-developers.com/showthread.php?p=41010145
Click to expand...
Click to collapse
I'm not getting boot loops actually, I get stuck on the "splash screen" and when I hold the "power" button for +/-10sec it reboots and most of the time it's fine.
When I install any roms, I always do a factory reset... So I doubt it's that
i had the same issue. im running the same s4 on koodo/telus. how i got it to work took a while but it fixed the problem. full back up through recovery but i wasnt gona use it..i only had it for safety. used titanium to back up all the apks. then grabbed a stock rom from the Canadian stock roms page and used odin to flash it. rooted and added recovery (twrp). downloaded my rom to the sd, wiped everything and installed the rom. once done then used titanium to restore the apks. im still learning the basics to all this so in no way am i an expert and theres probably a better way around all this but this is what worked for me. maybe it helps who who knows
h_khan said:
i had the same issue. im running the same s4 on koodo/telus. how i got it to work took a while but it fixed the problem. full back up through recovery but i wasnt gona use it..i only had it for safety. used titanium to back up all the apks. then grabbed a stock rom from the Canadian stock roms page and used odin to flash it. rooted and added recovery (twrp). downloaded my rom to the sd, wiped everything and installed the rom. once done then used titanium to restore the apks. im still learning the basics to all this so in no way am i an expert and theres probably a better way around all this but this is what worked for me. maybe it helps who who knows
Click to expand...
Click to collapse
Yea, I had done this before, but I'm giving it another shot tonight to see if it'll fix my problem for good...
Still having the same problem... Running out of ideas
jproy12 said:
Still having the same problem... Running out of ideas
Click to expand...
Click to collapse
I was having a similar problem to your's. I found the cause of my issue. It was TWRP 2.6.0.0. More specifically, it was using TWRP 2.6 to format my /data partition. After doing some trouble shooting, I found that my /data partition was the cause of my S4 hanging at the S4 splash screen. Like you, I was able to get into Android on the first boot, but if I tried to reboot, I was get stuck at the splash screen. So, long story short (solution), I restored one of my nandroid backups, got into Google Play, downloaded ROM Manager and installed CWM. I used CWM to format my /data partition and ONLY my /data partition. Once I did this, I rebooted my phone. Android loaded, I had to go through the initial setup process since I formatted the /data partition, but after this, I was able to reboot my phone 5 times in a row without issue and shut down twice with no problems booting back up.
Here is my thread: http://forum.xda-developers.com/showthread.php?p=45448596#post45448596
There's a bit of reading. Hope this helps.
So my issue was caused by TWRP 2.6.0.0 and using it to format my /data partition.
jproy12 said:
Still having the same problem... Running out of ideas
Click to expand...
Click to collapse
i think the rom is the cause of this issue. i myself am running goldeneye rom which is the best rom ive used so far...perfectly balanced performance and battery life. id definitely recommend it.
Talabis said:
I was having a similar problem to your's. I found the cause of my issue. It was TWRP 2.6.0.0. More specifically, it was using TWRP 2.6 to format my /data partition. After doing some trouble shooting, I found that my /data partition was the cause of my S4 hanging at the S4 splash screen. Like you, I was able to get into Android on the first boot, but if I tried to reboot, I was get stuck at the splash screen. So, long story short (solution), I restored one of my nandroid backups, got into Google Play, downloaded ROM Manager and installed CWM. I used CWM to format my /data partition and ONLY my /data partition. Once I did this, I rebooted my phone. Android loaded, I had to go through the initial setup process since I formatted the /data partition, but after this, I was able to reboot my phone 5 times in a row without issue and shut down twice with no problems booting back up.
Here is my thread: http://forum.xda-developers.com/showthread.php?p=45448596#post45448596
There's a bit of reading. Hope this helps.
So my issue was caused by TWRP 2.6.0.0 and using it to format my /data partition.
Click to expand...
Click to collapse
Thanks, I'll give that a try, but it seems like this is/was my problem, is your problem fixed for good now? No getting stuck on the "boot screen"?
h_khan said:
i think the rom is the cause of this issue. i myself am running goldeneye rom which is the best rom ive used so far...perfectly balanced performance and battery life. id definitely recommend it.
Click to expand...
Click to collapse
I've been running Slim for a year now, and won't go back to anything else, it's stable and fast, I doubt it's a ROM problem, but a recovery problem.
i think you're right. a problem with the recovery makes more sense.
jproy12 said:
Thanks, I'll give that a try, but it seems like this is/was my problem, is your problem fixed for good now? No getting stuck on the "boot screen"?
Click to expand...
Click to collapse
So it seems like this wasn't exactly my problem... I've reverted back to stock and I'm doing a couple shutdowns and reboot and see if I still get stuck at the splash screen.
I've been doing reboots and shutdowns on the "stock" rom and "stock" recovery, and all is good, so I can rule out the fact that it's the phone and it's hardware issues...
Now, just need to figure out the actual problem
jproy12 said:
Thanks, I'll give that a try, but it seems like this is/was my problem, is your problem fixed for good now? No getting stuck on the "booscreen"?
Click to expand...
Click to collapse
So far so good. I rebooted many times since I made the post in this thread. Haven't got stuck on the splash screen yet.
I'm still having the problem, being on either the TWRP, CWM or Philz recovery, so I'm really not sure what it could be. I'm on the latest modem and still have the problem, is none else having these issues?
I'm getting annoyed and really want to get this fixed.
I think any ROM built on AOSP or CyanogenMod have this issue. It's already a known issue to CM.
Use CWM and you'll have to deal with it less.
emckai said:
I think any ROM built on AOSP or CyanogenMod have this issue. It's already a known issue to CM.
Use CWM and you'll have to deal with it less.
Click to expand...
Click to collapse
I've never seen anyone really mentionning this for the Galaxy S4 from my numerous searches...
jproy12 said:
I've never seen anyone really mentionning this for the Galaxy S4...
Click to expand...
Click to collapse
If you look in the cyanogenmod thread, it's located in the known bug (post #2)
Any custom roms built on top of CM10 will probably have this issue.
emckai said:
If you look in the cyanogenmod thread, it's located in the known bug (post #2)
Any custom roms built on top of CM10 will probably have this issue.
Click to expand...
Click to collapse
You are right! I guess it's one of those bugs, just never noticed anyone really mentioning anything about it
jproy12 said:
You are right! I guess it's one of those bugs, just never noticed anyone really mentioning anything about it
Click to expand...
Click to collapse
Yeah, but I don't think its a big deal anyway. How many times do you turn off your phone and turn it back on in a day?
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.
Hello,
Like the title says, I have a Samsung J5, I rooted it as soon as I got it maybe a year or so ago.
I never had any issues with it. This morning, however I made a (now in hindsight) bad decision by factory resetting, dont even ask me why I thought I needed to factory reset it, I already did it.
Anyways, I did the factory reset from the phone and it instantly rebooted into TWRP, and here's where I got lost. I don't know what to do from here.
I assumed the phone would just reset itself, but it always reboots in recovery mode.
I thought maybe I had to flash a ROM again (I flashed a custom one and then stock back when I first rooted it, but my memory is terrible and I just have faint memories of it), I looked that up and found I needed Odin, the stock rom I wanted to flash and to reboot into download mode. So I got all I required and I don't think Odin is finding my phone.
My phone just has the blue screen saying downloading... and do not turn off target. Nothing else. and Odin doesn't show anything (I think it's supposed to show the device somewhere? Anyways, I'm super lost and I have no idea what to do.
I mostly just need someone to point me in the right direction, maybe some instructions I can follow or something, I'm not super experienced as you can tell but I can follow basic instructions when I'm not being dumb.
TL;DR: Did factory reset on rooted J5, now it only boots into TWRP, no idea where to go from here, stock rom flash?
4tson said:
Hello,
Like the title says, I have a Samsung J5, I rooted it as soon as I got it maybe a year or so ago.
I never had any issues with it. This morning, however I made a (now in hindsight) bad decision by factory resetting, dont even ask me why I thought I needed to factory reset it, I already did it.
Anyways, I did the factory reset from the phone and it instantly rebooted into TWRP, and here's where I got lost. I don't know what to do from here.
I assumed the phone would just reset itself, but it always reboots in recovery mode.
I thought maybe I had to flash a ROM again (I flashed a custom one and then stock back when I first rooted it, but my memory is terrible and I just have faint memories of it), I looked that up and found I needed Odin, the stock rom I wanted to flash and to reboot into download mode. So I got all I required and I don't think Odin is finding my phone.
My phone just has the blue screen saying downloading... and do not turn off target. Nothing else. and Odin doesn't show anything (I think it's supposed to show the device somewhere? Anyways, I'm super lost and I have no idea what to do.
I mostly just need someone to point me in the right direction, maybe some instructions I can follow or something, I'm not super experienced as you can tell but I can follow basic instructions when I'm not being dumb.
TL;DR: Did factory reset on rooted J5, now it only boots into TWRP, no idea where to go from here, stock rom flash?
Click to expand...
Click to collapse
Try factory reset in TWRP under "wipe" and try rebooting then.
If that doesn't work download a rom from xda for your device onto an sd card. Then put the sd card into the phone, Reboot into twrp and flash the ROM.
The reason odin isn't picking up your device is more than likely USB debugging isn't enabled which you can only do from inside the phones settings. Enable it once you flash the new rom and then flash your old firmware using odin afterwards if you wish.
Do you know what model it is?
Or even what year model it is? 2015?/16?/17?
If you can boot into twrp you have nothing to worry about as it can be easily resolved
garylawwd said:
Try factory reset in TWRP under "wipe" and try rebooting then.
If that doesn't work download a rom from xda for your device onto an sd card. Then put the sd card into the phone, Reboot into twrp and flash the ROM.
The reason odin isn't picking up your device is more than likely USB debugging isn't enabled which you can only do from inside the phones settings. Enable it once you flash the new rom and then flash your old firmware using odin afterwards if you wish.
Do you know what model it is?
Or even what year model it is? 2015?/16?/17?
If you can boot into twrp you have nothing to worry about as it can be easily resolved
Click to expand...
Click to collapse
Hey
I have already tried doing the factory reset from TWRP, but when I reboot after that it goes back into recovery mode, if I try to reboot from recovery mode into system it just goes back to recovery mode as well.
I'll try downloading another rom, I got the stock one in there but it doesn't flash it from TWRP, which I'm pretty sure is expected behaviour anyways.
The model is SM-J510MN 2016, I'll start looking for a rom.
Thanks
4tson said:
Hey
I have already tried doing the factory reset from TWRP, but when I reboot after that it goes back into recovery mode, if I try to reboot from recovery mode into system it just goes back to recovery mode as well.
I'll try downloading another rom, I got the stock one in there but it doesn't flash it from TWRP, which I'm pretty sure is expected behaviour anyways.
The model is SM-J510MN 2016, I'll start looking for a rom.
Thanks
Click to expand...
Click to collapse
You can't flash the stock rom in TWRP because it is a .zip.tar file and twrp can only flash .zip files or .img files
garylawwd said:
You can't flash the stock rom in TWRP because it is a .zip.tar file and twrp can only flash .zip files or .img files
Click to expand...
Click to collapse
Yeah, I may or may not have already tried hehe.
You wouldn't happen to have a rom that's not being hosted on Mega would you? I exceeded my limit when I was 95% done downloading one of them.
I think I found one, whoops.
4tson said:
Hello,
Like the title says, I have a Samsung J5, I rooted it as soon as I got it maybe a year or so ago.
I never had any issues with it. This morning, however I made a (now in hindsight) bad decision by factory resetting, dont even ask me why I thought I needed to factory reset it, I already did it.
Anyways, I did the factory reset from the phone and it instantly rebooted into TWRP, and here's where I got lost. I don't know what to do from here.
I assumed the phone would just reset itself, but it always reboots in recovery mode.
I thought maybe I had to flash a ROM again (I flashed a custom one and then stock back when I first rooted it, but my memory is terrible and I just have faint memories of it), I looked that up and found I needed Odin, the stock rom I wanted to flash and to reboot into download mode. So I got all I required and I don't think Odin is finding my phone.
My phone just has the blue screen saying downloading... and do not turn off target. Nothing else. and Odin doesn't show anything (I think it's supposed to show the device somewhere? Anyways, I'm super lost and I have no idea what to do.
I mostly just need someone to point me in the right direction, maybe some instructions I can follow or something, I'm not super experienced as you can tell but I can follow basic instructions when I'm not being dumb.
TL;DR: Did factory reset on rooted J5, now it only boots into TWRP, no idea where to go from here, stock rom flash?
Click to expand...
Click to collapse
maybe install usb drivers and try this: disconnect device, hold power, home and vol up key, connect device and then press volume up to enter download mode
Dyeide said:
maybe install usb drivers and try this: disconnect device, hold power, home and vol up key, connect device and then press volume up to enter download mode
Click to expand...
Click to collapse
Yep, I tried that, although I'm not sure the USB drivers I downloaded were correct, since the official page isn't working at least for me. So I downloaded what the websites claimed were the correct drivers, I went into download mode that way, which has some debug info on the top left stating it's in Odin mode, but Odin still didn't recognize it.
I'm pretty sure usb debug options were turned on before this, but I'm not sure if the factory reset could've messed with that, thought I'm assuming it could be part of it.
I'm currently trying to download some custom roms to follow garylawwd's advice, I'll reply once I've got results.
garylawwd said:
You can't flash the stock rom in TWRP because it is a .zip.tar file and twrp can only flash .zip files or .img files
Click to expand...
Click to collapse
So I downloaded one, wiped everything, installed it via twrp, it apparently installed it correctly, rebooted the system and it went straight into recovery mode again. It's not letting me reboot into anything that isn't download or recovery. Any other ideas? Am I doing something wrong?
4tson said:
So I downloaded one, wiped everything, installed it via twrp, it apparently installed it correctly, rebooted the system and it went straight into recovery mode again. It's not letting me reboot into anything that isn't download or recovery. Any other ideas? Am I doing something wrong?
Click to expand...
Click to collapse
Uhm, so after doing that I flashed the latest twrp version (I had 3.0.2 or something), rebooted after flashing the image, did a wipe from there, rebooted and it now didn't boot into recovery mode but instead I'm now on a white screen with the samsung logo in the middle looping from light grey to black. I'll look into that I guess...
4tson said:
Uhm, so after doing that I flashed the latest twrp version (I had 3.0.2 or something), rebooted after flashing the image, did a wipe from there, rebooted and it now didn't boot into recovery mode but instead I'm now on a white screen with the samsung logo in the middle looping from light grey to black. I'll look into that I guess...
Click to expand...
Click to collapse
After it got stuck on the samsung logo I rebooted into recovery mode, flashed the custom rom once again, rebooted and it's still stuck on the samsung logo. Lost once more.
4tson said:
After it got stuck on the samsung logo I rebooted into recovery mode, flashed the custom rom once again, rebooted and it's still stuck on the samsung logo. Lost once more.
Click to expand...
Click to collapse
Go into twrp and go to wipe. Click advanced wipe and wipe system, internal, data, dalvik cache.
Then flash the ROM again and reboot
garylawwd said:
Go into twrp and go to wipe. Click advanced wipe and wipe system, internal, data, dalvik cache.
Then flash the ROM again and reboot
Click to expand...
Click to collapse
Tried this just now, it rebooted twice and on the second reboot it got stuck on the logo once again.
I think I'm done trying to mess around with it, I'll take it to a repair place :/
Thanks for looking out though, definitely appreciate your tips even if they didn't end up working out. :good:
4tson said:
After it got stuck on the samsung logo I rebooted into recovery mode, flashed the custom rom once again, rebooted and it's still stuck on the samsung logo. Lost once more.
Click to expand...
Click to collapse
https://forum.xda-developers.com/ga...nt/recovery-twrp-3-1-2-blue-dogerino-t3768707 Try flashing this recovery it's a newer version.Just download the .img file and install it through twrp as recovery when prompted.
4tson said:
So I downloaded one, wiped everything, installed it via twrp, it apparently installed it correctly, rebooted the system and it went straight into recovery mode again. It's not letting me reboot into anything that isn't download or recovery. Any other ideas? Am I doing something wrong?
Click to expand...
Click to collapse
Why would you try a ROM which has not been updated for months,get a recent one like Lineage OS just to try if it works,its also small in size.
DontTouchMaPhone said:
Why would you try a ROM which has not been updated for months,get a recent one like Lineage OS just to try if it works,its also small in size.
Click to expand...
Click to collapse
He wants to just enable USB debugging in devoloper options because he wants the stock firmware and his pc isn't recognising his phone because this option isn't enabled.
He has twrp so flashing any rom will do just to get into the phone and enable USB debugging so he can flash the stock firmware through odin
garylawwd said:
He wants to just enable USB debugging in devoloper options because he wants the stock firmware and his pc isn't recognising his phone because this option isn't enabled.
He has twrp so flashing any rom will do just to get into the phone and enable USB debugging so he can flash the stock firmware through odin
Click to expand...
Click to collapse
I understand why he is using a custom rom,I mean why did he try one that has not been updated for ages because maybe its the rom causing bootloop
DontTouchMaPhone said:
I understand why he is using a custom rom,I mean why did he try one that has not been updated for ages because maybe its the rom causing bootloop
Click to expand...
Click to collapse
Hey, so yeah, I was just looking for any rom, didn't really look for anything in particular, just got the first one I found in order to just get into the phone.
I ended up just taking it to a repair place after not having much luck myself, I don't know what exactly they did, but I now have that ROM flashed and I have access to the phone, I'm not sure if I want to try flashing either a different custom rom now, stock, or just sticking to this, since I'm sorta scared it will get messed up again and I'll have to go back to that repair place.
4tson said:
Hey, so yeah, I was just looking for any rom, didn't really look for anything in particular, just got the first one I found in order to just get into the phone.
I ended up just taking it to a repair place after not having much luck myself, I don't know what exactly they did, but I now have that ROM flashed and I have access to the phone, I'm not sure if I want to try flashing either a different custom rom now, stock, or just sticking to this, since I'm sorta scared it will get messed up again and I'll have to go back to that repair place.
Click to expand...
Click to collapse
Are you on stock now?
DontTouchMaPhone said:
Are you on stock now?
Click to expand...
Click to collapse
Nope, I'm on Extreme ux 8.0, which is what I downloaded to try to get into the phone to turn on the usb debugging option, the guy that repaired it must've noticed it was already on my SD card and flashed it without telling me.
Like I said, I kind of want to go back to stock but I'm sort of scared of touching it and having it get stuck again, I've kinda got used to this rom's little issues by now though I suppose.
4tson said:
Nope, I'm on Extreme ux 8.0, which is what I downloaded to try to get into the phone to turn on the usb debugging option, the guy that repaired it must've noticed it was already on my SD card and flashed it without telling me.
Like I said, I kind of want to go back to stock but I'm sort of scared of touching it and having it get stuck again, I've kinda got used to this rom's little issues by now though I suppose.
Click to expand...
Click to collapse
Wait,so you paid for the repair right?And he flashed you a custom rom?Looks pretty scammy to me..Anyways do you have twrp or stock recovery?