Hi. I’ve got a customer with a j5 that I factory reset as she was having problems with it. But now it will only boot to TWRP which must have been installed before she bought it.
I’ve tried sourcing a stock android but with no luck so I tried a few Roms from here today. I can’t get it to work at all! Here’s what Happens.
From twrp I install CM rom and gapps. When I reboot the phone an orange line appears across the screen followed by the Samsung logo. Then the screen starts fading to green. The screen is in full working order when using twrp.
Does anyone have any ideas?!
Thanks
Davidb8 said:
Hi. I’ve got a customer with a j5 that I factory reset as she was having problems with it. But now it will only boot to TWRP which must have been installed before she bought it.
I’ve tried sourcing a stock android but with no luck so I tried a few Roms from here today. I can’t get it to work at all! Here’s what Happens.
From twrp I install CM rom and gapps. When I reboot the phone an orange line appears across the screen followed by the Samsung logo. Then the screen starts fading to green. The screen is in full working order when using twrp.
Does anyone have any ideas?!
Thanks
Click to expand...
Click to collapse
More than likely that version of twrp is outdated get a .IMG file of twrp version 3.2.1 and flash the image in twrp. Use this https://forum.xda-developers.com/galaxy-j5/development/recovery-samsung-galaxy-j5-t3769408/page5
If that isn't the problem and the problem you have persists than you have either flashed the wrong version file as there is several types of galaxy j5 with different hardware,
Or the bootloader you have on the phone is the wrong version ie. it has marshmallow bootloader and your trying to flash a ROM that only supports lollipop or vice versa. Links for both bootloaders are here
https://forum.xda-developers.com/ga...5-1-1-bootloader-modem-j500xx-t3566801/page14
This should fix your issues hope it helped
Related
Hey guys. About a week or three ago I saw nightlies started rolling out for the D802, and decided to try the third nightly that has been released. While flashing itself went fine, I'm having trouble with getting the ROM to boot. After the LG logo the phone enters a blank screen, and won't do anything at all. I can barely notice that the backlight stays on, and I noticed that during this bootloop or whatever this is, Windows Explorer spams over and over I need to format the disk before I can use it when the phone's plugged in. I've read from someone that I should flash the ROM and google apps simultaneously, thus I've added them to a flashing queue and wiped the Davik cache after the flashing.
At first I thought it might've been my recovery being out of date, since I was running TWRP v2.6.x.x before, so I flashed the most recent version I could find which was v.2.8.3.73.
Doing this however made no difference whatsoever, so I gave up at this point and decided to wait for a week or two for the developer to fix a potential issue on the ROMs end.
Now it's fast forward to two weeks later where I'm typing this post after trying to flash the most recent version of cm13 which was available for my phone (the D802).
The problem is I'm starting to run out of ideas to do, so I'm hoping somebody can hold my hand regarding this issue. I really like to try Marshmallow and it's really irritating it doesn't work.
Thanks in advance guys!
i yhink you need to install boostacks when you install boostacks for your varian. dont reboot into system, just go back to main menu. then reboot into recovery from recovery. then copy the rom. flash and gapps ...
i also ecoment blastagator twrp to prevent ecreen dmage
http://forum.xda-developers.com/lg-g2/development/boot-g2-hybrid-bootstacks-t3183219
http://forum.xda-developers.com/lg-g2/development/twrp-twrp-2-8-0-0-kernel-f2fs-tools-t2898705
Thank you!
I was having the same trouble with lineage OS 14.1 on my D802.
I always got a black screen after the logo of LG appeared.
luckily I could get to TWRP and push the alternative bootstack via "adb push (filelocation) /sdcard/"
Thanks a lot!
thc8 said:
Thank you!
I was having the same trouble with lineage OS 14.1 on my D802.
I always got a black screen after the logo of LG appeared.
luckily I could get to TWRP and push the alternative bootstack via "adb push (filelocation) /sdcard/"
Thanks a lot!
Click to expand...
Click to collapse
Newbie here - I'm having the same problem with my D800 after Lineage OS 14 flash via TWRP. Where do I get an 'alternative bootstack'?
Get bootstack from here!
Check this out: https://forum.xda-developers.com/lg-g2/development/lg-g2-bootstacks-t3173715
Hello, i will try to be as elaborate as I can cause I know you guys here are really knowledgeable when it comes to smartphones. So, here are the issues I am currently experiencing with my G900F phone. Just a background, everything in my phone is stock (rom, recovery, kernel) no changes done yet. It currently runs MM with a security patch of February 2017. As of now, I can't boot into the phone.
1. . I was able to successfully root it with CF auto root.
2. I started experiencing random restarts. I tried obtaining the last kmsg however it does not exist.
3. I tried flashing a new ROM thinking maybe there is some rare bug in the stock rom i currently have. I flashed TWRP via Odin, to be able to flash a new ROM. Odin successfully flashed the recovery however when i proceed to install a new ROM through TWRP the phone gets stuck in a bootloop. I do not experience this in the stock recovery
4. I was able to restore the phone through Smart Switch device intialisation. However, with everything stock I still experience the random reboots.
Bottomline: Is there anyway I can fix this on the software side (e.g. flash/update this or that)? And if not, do you think this is a hardware problem? Worth mentioning it's got a yellow screen bug but if i press hard on the back of the phone it disappears. Also, I can boot into stock recovery and download mode without any problems.
Thanks and sorry for the long post really need your insights.
Sorry you are having issues. I apologize if I missed this, but have you tried downloading the official firmware for your device from sammobile or similar sites, then flash that through Odin?
[My phone is already repaired by Samsung under warranty, my internal storage was broken so they replaced the motherboard. There is no need to reply to this thread anymore. Thanks anyway]
Hello everyone, I need help!!!!
Today my Samsung GS6 Edge+ died. (At least, that's what I think)
I own my G928F for 1,5 years now. I rooted it two weeks after that. Several weeks ago I flashed a new ROM called N-Lite Nougat v4.1 which has worked smoothly and without any problems since I've flashed it.
However, today, the 26th of June, my phone turned off all of a sudden while scrolling through Facebook. I haven't flashed, installed nor done, anything that would affect my phone in such a way that it would crash this way. I tried force rebooting with the 3 buttons pressed (Home, Vol+, On/Off) several times. My phone just boots into the ROM and then freezes instantly. Again tried force rebooting for like 5 times, NO luck. Then I tried booting into recovery mode (TWRP 3.1.0.0), cleared Dalvik and cache, factory reset, rebooted, still no luck. Tried several other custom ROM's, still NO luck. Also tried flashing stock Samsung Firmware using ODIN, no luck whatsoever.
I couldn't find any similar problems in the ROM thread, nor anywhere else on the internet. Besides that, I'm starting to think this problem is a defect to the hardware, not the software.
Does anyone know what would be the best thing to do in my situation? Or perhaps anyone who might know what the problem might be and have a possible solution?
Thanks in Advance.
Recovery mode (TWRP 3.1.0.0) is accessible though, but that's all. While trying to install another ROM it just reboots randomly, during flashing progress.
When you say you tried flashing stock rom with ODIN, does it fail or does it succeed but freezes up when you are back in android OS?
kdogguk said:
When you say you tried flashing stock rom with ODIN, does it fail or does it succeed but freezes up when you are back in android OS?
Click to expand...
Click to collapse
It succeeds. But when it's done it just keeps going in a bootloop. It doesn't even boot into Android now. I've used the right settings in Odin. Even tried several different versions of Odin. No success
Larss97 said:
It succeeds. But when it's done it just keeps going in a bootloop. It doesn't even boot into Android now. I've used the right settings in Odin. Even tried several different versions of Odin. No success
Click to expand...
Click to collapse
Out of curiosity, when you flashed the stock Rom was it 6.0.1 or 7.0?
Does it just get stuck on the S6 EDGE + screen for a while? If so you might be to impatient as first boot on almost all roms both custom or stock take a while to boot up. If it shows the Samsung splash screen over and over then yes it's bootlooping.
I can't think of any other reason for it bootlooping, especially if you have flashed a stock Rom, unless maybe you flashed 7.0 rom and still have a 6.0.1 bootloader. But I think that just causes loss of baseband, not a bootloop.
I would suggest another kernel, but that is normally included in the stock rom.
Do you download them from sammobile or another site? If it's another site, is it a reliable site?
kdogguk said:
Out of curiosity, when you flashed the stock Rom was it 6.0.1 or 7.0?
Does it just get stuck on the S6 EDGE + screen for a while? If so you might be to impatient as first boot on almost all roms both custom or stock take a while to boot up. If it shows the Samsung splash screen over and over then yes it's bootlooping.
I can't think of any other reason for it bootlooping, especially if you have flashed a stock Rom, unless maybe you flashed 7.0 rom and still have a 6.0.1 bootloader. But I think that just causes loss of baseband, not a bootloop.
I would suggest another kernel, but that is normally included in the stock rom.
Do you download them from sammobile or another site? If it's another site, is it a reliable site?
Click to expand...
Click to collapse
It was Android 7.0. I downloaded it from Sammobile. I've waited 40 minutes for it to boot up after successful Odin flash. But it just kept doing the same thing. The bootloader that was installed was a 7.0 bootloader. First i get the Samsung Galaxy S6 Edge + screen then the Samsung boot animation and it repeats for hours untill battery runs out haha
Larss97 said:
It was Android 7.0. I downloaded it from Sammobile. I've waited 40 minutes for it to boot up after successful Odin flash. But it just kept doing the same thing. The bootloader that was installed was a 7.0 bootloader. First i get the Samsung Galaxy S6 Edge + screen then the Samsung boot animation and it repeats for hours untill battery runs out haha
Click to expand...
Click to collapse
The last thing I can think of was did you get the right rom for your phone? 928F or 928T etc.
Other than that it might be a trip to the repair centre I'm afraid.
Larss97 said:
It was Android 7.0. I downloaded it from Sammobile. I've waited 40 minutes for it to boot up after successful Odin flash. But it just kept doing the same thing. The bootloader that was installed was a 7.0 bootloader. First i get the Samsung Galaxy S6 Edge + screen then the Samsung boot animation and it repeats for hours untill battery runs out haha
Click to expand...
Click to collapse
Try to do a factory reset in the stock recovery. It might help.
vishnu8058 said:
Try to do a factory reset in the stock recovery. It might help.
Click to expand...
Click to collapse
Done that, no success
kdogguk said:
The last thing I can think of was did you get the right rom for your phone? 928F or 928T etc.
Other than that it might be a trip to the repair centre I'm afraid.
Click to expand...
Click to collapse
Yeah i got the right rom for my phone. I've already sent it to a certified Samsung repair centre, it's still under warranty. Thanks for the help anyway
I upgraded the firmware on my phone to install Bad Boyz Oreo ROM. My phone did not like it. It sent the phone into a constant bootloop.
Since that time, I've tried everything. I'm not a noob to this. I was able to use a Sprint Nougat RUU, which installed successfully with no errors, but it stayed on the HTC green and white screen. No bootloop, just stayed on the screen. I installed TWRP, and flashed an older version of Viper ROM. It's just stuck ont he Venom logo. Not doing anything.
I'm downloading another RUU at the moment. Not sure it's going to do anything.
Can anybody get me to a point where the phone works again? I can't upgrade until July, and I am using my old M8 till I get this fixed.
Thanks!
Mother****er! I just installed Bad Boyz again, using the Magisk and it's booting. What's the issue using the SuperSU optionk
Can U plz provide a link of the same?
Hi there... i am too stuck on a bootloop since i tried updating to Oreo 8.0. Now i have got access only to the download mode. Would appreciate if u can guide how to get rid of the bootloop
Hey everyone,
I have been looking around online for several days now, but haven't been able to find a description of the problem I have with my n910f nor a solution.
When I got the phone it was stuck in bootloops and so I though it was soft bricked.
After I installed the custom rom and the latest version of TWRP via Odin, I thought that the problem was fixed, because the phone booted and I was able to start the configuration of Android (where it asks you for language, time zone etc.)
However, the phone turned itself off during this process. So I wiped everything and tried again, the same thing happened.
I then flashed it with Lineage, but it would turn itself off even before the logo appeared.
Then I flashed it with Ressurrection ROM, but again, the phone turns itself off during booting.
I can access download and recovery mode without any problems, I can flash roms and Odin works like a charm. I also used 2 different batteries.
Does anyone has an idea what I could try? Could it be the version of TWRP I am using (3.0.2.0)? Or is it a hardware issue?
Thank you!!
Hi, I have this exact same issue with my N910T and so far haven't found a solution to this. I really love my Note 4 so I'd like to know if this issue can be solved or not. I event went to a supposed repair shop and they couldn't figure out the problem, guess they weren't that good.
Sorry to hear this.
I have found issues that seemed similar, but not quite the same, and people hinted that it could be a worn out motherboard that is causing this top happen. But before I open up the phone (at the potential risk of breaking at least the screen) I would try everything else.
Or is there a way to test whether the motherboard is defective?
Its the plague of overheated, worn out emmc memories, sadly. Once it happen,the only way is a new/used motherboard,prefferably C model.
eMMC failure, snapdragon models are susceptible to this.
Tüddels said:
Hey everyone,
I have been looking around online for several days now, but haven't been able to find a description of the problem I have with my n910f nor a solution.
When I got the phone it was stuck in bootloops and so I though it was soft bricked.
After I installed the custom rom and the latest version of TWRP via Odin, I thought that the problem was fixed, because the phone booted and I was able to start the configuration of Android (where it asks you for language, time zone etc.)
However, the phone turned itself off during this process. So I wiped everything and tried again, the same thing happened.
I then flashed it with Lineage, but it would turn itself off even before the logo appeared.
Then I flashed it with Ressurrection ROM, but again, the phone turns itself off during booting.
I can access download and recovery mode without any problems, I can flash roms and Odin works like a charm. I also used 2 different batteries.
Does anyone has an idea what I could try? Could it be the version of TWRP I am using (3.0.2.0)? Or is it a hardware issue?
Thank you!!
Click to expand...
Click to collapse
I suggest flashing stock rom with Odin after wiping your whole device in TWRP. I've had the same thing about 2 months ago.
Hey,
thank you for your responses. Yes, I read a lot about it being a motherboard problem.
I got it to work now thanks to this post: https://forum.xda-developers.com/note-4/general/downgrade-official-mm-to-kitkat-t3383885
First nothing happened, but after I flashed Modem and the original Bootloader again (after installing the rom) the phone turned on and I was able to use it for a while (20mins maybe). Then suddenly it turned itself off and stayed on the "Samsung Galaxy" screen for a long time.
Apparently a lot of people are using Wakelock and it seems to be working for some of them, but that seems to defy the point somehow.
KirbyFan64 said:
I suggest flashing stock rom with Odin after wiping your whole device in TWRP. I've had the same thing about 2 months ago.
Click to expand...
Click to collapse
Which Stock Rom did you use exactly? Is your phone working fine?