I have my cousin's phone right here - just yesterday he tried to update to Lollipop. He was on stock TouchWiz, no root or anything of the sort and installed the update.
Now, if I try to turn on the phone, all I get is this screen and it just stays there forever:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If I try to boot into the bootloader, all I get is this: https://goo.gl/photos/WBSAcHhALQ9Jmz2n9
I really don't know what I would do here - can you do anything once your bootloader is f*ed up?
If it helps, the phone's model is SM-N7505
Yes, the same issue happened with me today on Note3 Neo. I rebooted the phone and it stuck on the same place. Checked in local phone repairing shop unable to make hard reset. They are suspecting of hardware issue. What could be the coz of this?
vadsvads said:
I have my cousin's phone right here - just yesterday he tried to update to Lollipop. He was on stock TouchWiz, no root or anything of the sort and installed the update.
Now, if I try to turn on the phone, all I get is this screen and it just stays there forever:
If I try to boot into the bootloader, all I get is this: https://goo.gl/photos/WBSAcHhALQ9Jmz2n9
I really don't know what I would do here - can you do anything once your bootloader is f*ed up?
If it helps, the phone's model is SM-N7505
Click to expand...
Click to collapse
Try flashing the rom using odin
ismaadu78 said:
Try flashing the rom using odin
Click to expand...
Click to collapse
How would I do that without being able to access the bootloader? I haven't done much with Samsung devices yet, only with my HTC phones. I've heard of the name ODIN though... Are there any tutorials you can recommend?
You don't need bootloader to flash stock rom via Odin, you only need to access Download mode (vol. down+home+lock). You can look up tutorials on YT. Just type "How to flash stock Samsung rom using Odin". Hope that helps somehow
Related
Like my title says I have a i317 Note II on AT&T. It was bricked a while back I tried factory reset which sent it into a boot loop until the battery drained now it is just a brick and wont start but past the Samsung logo.
I ran Odin v3.09 with a Pass but the phone is still doing the same thing. Not sure where to go after this. Do I need to run a new bootloader file? Any help would be great.
These are the files I ran with it:
i317.pit
I317-UCUBMK6.tar.md5
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
verapakill said:
Like my title says I have a i317 Note II on AT&T. It was bricked a while back I tried factory reset which sent it into a boot loop until the battery drained now it is just a brick and wont start but past the Samsung logo.
I ran Odin v3.09 with a Pass but the phone is still doing the same thing. Not sure where to go after this. Do I need to run a new bootloader file? Any help would be great.
These are the files I ran with it:
i317.pit
I317-UCUBMK6.tar.md5
View attachment 3062723
Click to expand...
Click to collapse
Is the phone still turning on? If so maybe try booting into recovery first and wiping all data before flashing stock rom again with odin?
I tried that. I have been able to get the phone to boot but as soon as it restarts it goes right back into a bootloop. Try wiping again and restarting with the same results. Stuck in a boot loop on the first Samsung screen.
So I decided to flash a new kernel and it worked fine and was an improvement. Developed connection issues thru Bluetooth so I decided to go back to stock. When following the directions to flash back to stock my watch just boots to logo then goes to a picture of
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So I'm a bit lost on what to do now. I tried flashing again following the same process. Am I screwed here or is there anything I can do?
I can still boot into fastboot and use adb/fastboot etc but that's about it. Maybe I need to flash a different image? if anyone has one backed up that I can install.
Thanks!
You sure you are using the revised process? And that you are fastboot booting the recovery and not fastboot flashing it?
I was able to flash my return back to stock and relock with bootloader using the revised instructions from skin1980 and his posted files.
brizey said:
You sure you are using the revised process? And that you are fastboot booting the recovery and not fastboot flashing it?
I was able to flash my return back to stock and relock with bootloader using the revised instructions from skin1980 and his posted files.
Click to expand...
Click to collapse
Yes! it's weird though haha. But worse case I can have the store replace it so not that big of a deal just wanted to see if I could work around the process and get it booted up.
Njzkrish said:
Yes! it's weird though haha. But worse case I can have the store replace it so not that big of a deal just wanted to see if I could work around the process and get it booted up.
Click to expand...
Click to collapse
PM me with your hangouts
Hello, I tried rooting my phone following this tutorial from a youtuber named Max Lee. since I am a noob. Everything was going fine until I flashed the SuperSU (As shown in the vid). I rebooted it and it got stuck in a bootloop. I tried multiple methods to get out, but I ended up relocking the bootloader and now I can't get into recovery. Since I hit rock bottom (which is why I am making this thread lol), I just need to know if there is anyway I can resolve this issue, or I need to know if my phone is just hard bricked.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
BarackObama1889 said:
Hello, I tried rooting my phone following this tutorial from a youtuber named Max Lee. since I am a noob. Everything was going fine until I flashed the SuperSU (As shown in the vid). I rebooted it and it got stuck in a bootloop. I tried multiple methods to get out, but I ended up relocking the bootloader and now I can't get into recovery. Since I hit rock bottom (which is why I am making this thread lol), I just need to know if there is anyway I can resolve this issue, or I need to know if my phone is just hard bricked.
Click to expand...
Click to collapse
@zedomax! His tutorials are good. He also has a website for that at htconeroot.com
But here's the problem, that tutorial is over two years old, so the TWRP recovery and SuperSU app linked there are outdated and won't work with the newer firmware.
Here's what to do:
Unlock your bootloader again.
Flash the latest TWRP in fastboot that you can download from here
From there you can either flash a ROM (almost all of them come pre-rooted with SU already installed), or flash the latest stable SuperSU.zip in recovery that you can download from here.
The easiest is to just flash TWRP, then a custom ROM.
Good luck!
Has anyone seen this on the Pixel?
I get this, when I turn off the phone and press volume up (only) then plug in the cable and get to this Download Mode that I has never seen on a Pixel. I always use bootloader to flash.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What is it for?
What firmware use ?
Is this new? ( I've seen this on a LG phone before )
P.S. I'm on Android Q beta Qpp2 (not rooted)
valderdark said:
Has anyone seen this on the Pixel?
I get this, when I turn off the phone and press volume up (only) then plug in the cable and get to this Download Mode that I has never seen on a Pixel. I always use bootloader to flash.
What is it for?
What firmware use ?
Is this new? ( I've seen this on a LG phone before )
P.S. I'm on Android Q beta Qpp2 (not rooted)
Click to expand...
Click to collapse
Yeah, it's been noted a while back. Unfortunately it is of no use to us unless you could get factory signed firmware from google, and then have the proper interface with which to install it. Some folks were messing with it in late 2017 to see if a root exploit could be found for the Verizon variant by installing it, however, it never came to fruition.
Badger50 said:
Yeah, it's been noted a while back. Unfortunately it is of no use to us unless you could get factory signed firmware from google, and then have the proper interface with which to install it. Some folks were messing with it in late 2017 to see if a root exploit could be found for the Verizon variant by installing it, however, it never came to fruition.
Click to expand...
Click to collapse
Thought that I would mess around with it.
It would be nice to have a different way to flash a firmware just in case the other method doesn't work.
Thanks
So, I really wanted to get the phone rooted, and I couldn't do it without a recovery, because I can't find the firmware for it no matter what, there is only firmware for 5059d, so when I flashed TWRP for 5059d, it was asking for a password, but I didn't have one. I made one, but TWRP didn't let me mount internal storage. I tried factory reset and it made it even worse, it showed me this image
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried factory reset but didn't help, then I tried to flash 5059d stock recovery, it worked, but now it does not even want to boot into system, I have tried Wipe data/Factory reset, didn't help. I am stuck now. I did try to flash stock firmware for 5059d, but I can't do it for some reason, SP flashtool throws me some ERROR : STATUS_BROM_CMD_FAIL /0xC0060005) error. I really don't know what to do now, if someone knows to help me, it would be preety cool . This is not my main phone, but I really want to get it fixed. Screw rooting now.
Where did you get the ROM?
DerivativeOfLog7 said:
Where did you get the ROM?
Click to expand...
Click to collapse
First Google search, phone is completely gone though so not worth investigating
BokeeXD said:
First Google search, phone is completely gone though so not worth investigating
Click to expand...
Click to collapse
Look at this: https://forum.xda-developers.com/t/...rom-a-5059d-to-unbrick.4598953/#post-88676529
May be worth a shot. If I were you I'd first try normally just plugging the usb cable in while the phone is off, and if it doesn't work, take it apart, unplug the battery, and then plug it in