Dear readers,
I’ve rooted my Samsung J 710gn with CF-Auto-Root. The rooting process looked successful and my phone booted after the process. Rootchecker said the root was successful and I was able to install rooted apps. When I rebooted the phone, it didn’t boot again. It just kept on vibrating. The thing is, I rooted a Samsung neo s5 before it, and it behaved exactly the same; all seemed good until i restarted and then it just vibrated. I thought that the problem was with this phone, because of the state it was in.
However my perfect functioning j7 2016 did the same which showed me, probably I did something wrong. But I just can’t figure out what it was. I read a lot about rooting and followed a tutorial. Thereby I am not able to fix the boot loop.
I hope there is someone who can help me..
Thank you in advance.
Related
Hello fellow XDA members! I am a Noob.
So I believe I have a Bricked Galaxy Note 10.1. Model GT-N8013
I Rooted Stock ROM, and flashed Collective Edition 5 Dark Side.
So heres what happened, everything seemed fine, until I made a mistake, I was Pimping my ROM with the PimpMyRom app. Every change seemed fine and my note worked, but when i saw the double boot screen slide in the app, i did what it said, i have the imf support or something like that. Then after i had the ''support'' needed, i clicked install button on the double boot slide, it seemed to do something and requested nothing, so i went ahead chose a second clip, and clicked set as second boot screen. It said it wont take effect until the 3rd boot, so i rebooted 3x, but at the third time, it was stuck at the boot screen with the galaxy note 10.1 logo ! It did not start or did anything, over time it would turn off and automatically reboot, but it would get stuck again !.
To attempt to fix it, I Booted into recovery (CWM) and did everything i could. I wiped nearly all cache, factory reseted, then out of fear, i flashed the stock firmware ROM from Sammobile website, with ODIN, and to my knowledge, it got worse!! It booted, seemed to do something then in the logo screen it got stuck once again!! Stock recovery says unable to mount /efs, i don't believe EFS is completely corrupted, I left it stuck for awhile and it shut down in like an hour. Help, what can i do to fix this!?!?!?!
Device cannot boot up.
I could boot into recovery and download mode only.
I thought that I too had bricked my 8013 the past weekend. Trying to do something that I shouldn't. It took me a bit of work and a lot of worry (my wife gave me my 8013 for Xmas and if I had to tell her that it was now a doorstop, she would have killed me). I used this method to get back to stock and then was able to work my way back to the ROM I use. I disremember in which order I Odin'd things, but in the end was able to un-brick. All I can say is give it a shot.
jusliloleme said:
I thought that I too had bricked my 8013 the past weekend. Trying to do something that I shouldn't. It took me a bit of work and a lot of worry (my wife gave me my 8013 for Xmas and if I had to tell her that it was now a doorstop, she would have killed me). I used this method to get back to stock and then was able to work my way back to the ROM I use. I disremember in which order I Odin'd things, but in the end was able to un-brick. All I can say is give it a shot.
Click to expand...
Click to collapse
i did what u said...but all i got is i able to get through the logo but without seeing anything only able to hear the sound. any other tip? i got the same problem as above.
So recently, I update my SGH-I337 via OTA and i started having call issues where I would keep having to restart the phone in order to make the phone calls work again. I then decided to root my phone in order to get the calls to work again and they did. I then decided that since my phone was now rooted, I would completely get rid of KNOX using Root Explorer. Doing this soft bricked my phone after a reboot. After some research, I found this post http://forum.xda-developers.com/showthread.php?t=2663545 and i got my phone working again using steps 1-7. I then took it a step further and used Odin3 v1.85 and flashed the JFLTE_USA_ATT_16G.pit file with ALL_ATT_I337UCUFNB1_I337ATTFNB1_505595_REV06_user_low_ship_MULTI_CERT.tar.md5 file and that in term bricked my phone again. So I repeated steps 1-7 again but wound up with a bootloop at the AT&T logo and now have no clue what to do. I have been at this for 3 days now so any assistance would be wonderful. Thanks.
EDIT: Got it fixed....removed battery and rebooted into recovery and performed a factory reset. it stayed at the AT&T logo screen for a couple minutes before it booted up.
Glad you were able to fix it on your own. Great job!
Thread closed
Ok so, I've been researching for about 2 days now. Trying to figure out a way to fix my soft bricked phone, now the problem with the phone is that, before it was bricked I had rooted it with this program called Kongo Root, after it ended and what not, it seemed like the phone was rooted successfully, so I went on and went to the play store and decided to download Superuser(even though I already had one from the Kongo Root program) anyhow I installed this superuser, and it asked for root permission, I allowed it, and after it asked me to go to the recovery install, I said yes, and my phone restarted, now it is stuck in the screen where it is supposed to download something or update idk, but it just shows an android with the sphere or whatever it is on its stomach, and there's a percentage bar at the bottom, and it just shows a 0% and it does not go any further than that, I cannot access bootloader, and it seems like my PC won't recognise the phone either. Help please. Sorry if my explanation is not good enough, I typed this really fast, im just really desperate.
I have a T-Mobile Galaxy S5, stock and rooted. Today, I used Kies to update to the latest G900TUVS1FOJ4 patch. That worked fine with no issue, but it did clear my root. No problem. So then I used the tutorial on this site:
http://nasirtech.blogspot.com/2015/02/root-g900tuvu1dob1-android-50-stock.html
to try to re-obtain root. (This was the tutorial I used previously and it worked fine.) However, this time, at the end, after Odin said "PASS" and the phone rebooted, it got stuck on the Samsung logo screen, and it will not go past it. I have gone into recovery and cleared the cache and done a factory wipe/reset, but it still gets stuck on the logo screen.
[Edit:] I am adding that after a long time of showing the Samsung logo screen (not sure how long), it does switch over to the white T-Mobile logo screen. Then that screen stays for a long time. I gave up and pulled battery to start over, but now it's doing it all over again.
[Edit 2:] I also want to add that the Samsung logo screen it is stuck on is not the colorful one, but the static black&white one, with "Powered by Android" at the bottom. In case that matters.
I can't figure out what to do next. I'm wary of following a tutorial on the web now, for fear it will be incorrect and do more damage.
What I want is to get past this, and end up with my phone on the new G900TUVS1FOJ4 patch, stock, and rooted.
Thank you,
Chris
Ok, I was able to flash stock G900TUVS1FOJ4, so my phone is no longer stuck, and I'm on the latest stock, but unrooted.
Now I am having trouble finding how to safely root it without doing the same thing again.
Any instructions out there for safely rooting this version?
Hi,
Thanks for writing to us at XDA Assist.
You can post your question in your device forum help section to get further help:
T-Mobile Galaxy S 5 Q&A, Help & Troubleshooting
Good luck!
Hello, this is my first post in this forum. So I have a galaxy a51 and a few days ago I woke up and I realized it was stuck at the Samsung Galaxy A51 Secured by Knox part. It's no longer under warranty and I know Odin exists. I've tried flashing with the latest firmware that I could find and it was a success on Odin. Yet, it is still stuck at this part of the boot.
Is there something I missed?
I downloaded official firmware from Frija by the way. Will try to get to recovery mode tomorrow and clear cache. If that doesn't work then I don't know what else. All tutorials and information in regards to this problem just leaves it at that. The day before yesterday I managed to get to the lock screen where I enter pin, but it crashed the second I typed in my first number. And before that I had this issue, but managed to get my phone booted and running for a few hours. I'm new to modifying phones, but I've flashed and modified video game consoles. So while it is a bit different, I do have some kind of experience and am not a complete noob.