Develop Bugs

[URGENT] Stuck on "Firmware Upgrade Encountered an Issue"

Hello XDA, haven't been on these forums for a while.
I have a slight issue with a Galaxy SIII I just picked up off a friend.
The S3 goes to this screen every time I try to boot it with the power button:
{
"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"
}
And I AM able to get to the download mode screen:
I've tried to flash a Stock Rooted Firmware onto the phone using Odin 3.07, and all it does is say it failed.
Another thing to note is that I CAN'T boot into recovery, and that I do not have Clockworkmod installed.
Also, I am not sure if my device is rooted as it was given to me by someone else..
Any help on trying to solve this issue will be much appreciated!! Thank you! ��
EDIT: if you can't see the images for some reason, it is just a photo of the "Firmware Upgrade Encountered an Issue" screen and a photo of the download mode screen.
More info:
ODIN MODE
PRODUCT NAME: SGH-T999
CUSTOM BINARY DOWNLOAD: Yes (4 counts)
CURRENT BINARY: custom
SYSTEM STATUS: official
QUALCOMM SECURE BOOT ENABLE

When you try to flash with Odin, what does it say in the message box after it fails?
Also, what firmware are you trying to flash?

DocHoliday77 said:
When you try to flash with Odin, what does it say in the message box after it fails?
Also, what firmware are you trying to flash?
Click to expand...
Click to collapse
This is the firmware I am trying to flash: root66_TMO_T999UVDLJA.tar.md5
It's basically a rooted stock ROM for the SIII T-Mobile.
And this is the message I receive when trying to flash:
Please note I have tried to flash other firmwares as well, getting the same message.
One thing that DID work was flashing a custom recovery through odin.
Thanks for the reply!

UPDATE:
I've now gotten the phone to get stuck at the Samsung boot logo (the one where it glows blue) instead of giving me the firmware issue message.
I did this by flashing CWM through odin. In Odin, it said the flash was successful but when I boot into recovery on my phone, it just goes to the stock Samsung recovery.
One thing I did notice was that when I try to factory reset the phone, it gives me a BUNCH of errors in red text.. doesn't seem normal.
Thanks again!

Yeah. Im afraid that doesn't sound good. But before getting too negative, try flashing the firmware again, but this time use the PIT file as well. In case the local one on your device is corrupted, use one from our thread in the General section.
http://forum.xda-developers.com/showthread.php?t=1848267
Download the correct one for your device. If the link in the op isn't working check my last few posts for a mirror.
Now in Odin do exactly as before, but also click the PIT button and select the file you just downloaded. Then make sure that re-partition is checked. Click start.
If something corrupted your partition layout, theres a chance this will fix it. If it doesn't work, theres a good possibility the memory is going bad....

DocHoliday77 said:
Yeah. Im afraid that doesn't sound good. But before getting too negative, try flashing the firmware again, but this time use the PIT file as well. In case the local one on your device is corrupted, use one from our thread in the General section.
http://forum.xda-developers.com/showthread.php?t=1848267
Download the correct one for your device. If the link in the op isn't working check my last few posts for a mirror.
Now in Odin do exactly as before, but also click the PIT button and select the file you just downloaded. Then make sure that re-partition is checked. Click start.
If something corrupted your partition layout, theres a chance this will fix it. If it doesn't work, theres a good possibility the memory is going bad....
Click to expand...
Click to collapse
Same thing happens this time, same error message. It seemed like the PIT file did not make a difference at all..
BUT! Now, I went into the stock recovery and tried to do a factory reset. NO ERRORS!
And when it began to boot, it made the little ringtone "jingle" and FINALLY BOOTED UP TO THE SETUP SCREEN!!
YOU, MY FRIEND, ARE AMAZING. THANK YOU SO MUCH!!
So for all future references: the PIT file may seem to do nothing at all, but once you do a factory reset it will work like a charm.
Once again, thanks! Bought the phone for $20, now I can sell it for around $100, lol.

Glad i could help!

Why is my device bootlooping after installing TWRP?

So the first thing I did after getting my new Flo was to use the standard OTA update to bring it up to 4.4.4, then unlock the bootloader, and flash TWRP 2.8.0.1. The recovery flashed fine, but take a look at the TWRP log every time I boot into it:
{
"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 going wrong? If I try to boot back to the stock ROM it just bootloops. Any help is greatly appreciated.
Thanks!

Anyone? I just realized something else that seems odd. When I reboot into recovery (holding down the power button and the volume down button) it doesn't boot into recovery, it boots into fastboot mode. Is this something unique to the N7 or is it part of the device being screwed up?
Thanks.

It's normal that Power/Vol- will bring you to the bootloader first, and from there you can choose to go into recovery.
Something probably happened with the OTA update. Try downloading the factory image (ROM plus recovery) and flashing that. Then you can try flashing a custom recovery again.
https://developers.google.com/android/nexus/images
Just to make sure, you got TWRP from here, right?
http://techerrata.com/browse/twrp2/flo

Pandae said:
It's normal that Power/Vol- will bring you to the bootloader first, and from there you can choose to go into recovery.
Something probably happened with the OTA update. Try downloading the factory image (ROM plus recovery) and flashing that. Then you can try flashing a custom recovery again.
https://developers.google.com/android/nexus/images
Just to make sure, you got TWRP from here, right?
http://techerrata.com/browse/twrp2/flo
Click to expand...
Click to collapse
Thanks for the tip, and even more for linking me straight to it. I really appreciate it.
And yeah I got the recovery straight from TWRP's site, and tried flashing a few different versions numerous times.
I'll try this as soon as I get off work and report back; thanks again.

Pandae said:
It's normal that Power/Vol- will bring you to the bootloader first, and from there you can choose to go into recovery.
Something probably happened with the OTA update. Try downloading the factory image (ROM plus recovery) and flashing that. Then you can try flashing a custom recovery again.
https://developers.google.com/android/nexus/images
Just to make sure, you got TWRP from here, right?
http://techerrata.com/browse/twrp2/flo
Click to expand...
Click to collapse
You're the man! Working perfectly now; re-installed TWRP and rooted no problem. Must have had some sort of issue with the OTA update as you mentioned. Thanks a ton.

Excellent, I'm glad to hear! :good: I had such bad luck upgrading a long time ago to 4.2.2 (soft-bricked my original N7), and since then I don't do any more Android upgrades, only full flashes.

Need help to UN-brick my phone due to frp lock... Please!

I rooted my phone last week and was surprised by the new OEM lock, A.K.A. FRP... At any rate, I rooted it and last night it froze up and when it restarted, it said Custom binary blocked by FRP and then just reboots. I have tried to flash everything and Odin will not work for anything. I can only get it to go into the download mode and then it fails. Any help?

PharQrazyR said:
I rooted my phone last week and was surprised by the new OEM lock, A.K.A. FRP... At any rate, I rooted it and last night it froze up and when it restarted, it said Custom binary blocked by FRP and then just reboots. I have tried to flash everything and Odin will not work for anything. I can only get it to go into the download mode and then it fails. Any help?
Click to expand...
Click to collapse
You must use odin version 3.10.7 only.
Here is odin v3.10.7 in case you need it:
https://www.androidfilehost.com/?fid=24052804347842132
Then odin flash the official Samsung firmware.
After the phone fully boots make sure that the oem unlock is enabled.
Never disable it.
Good luck
Have a nice evening.
Sent from my SM-G928T using Tapatalk

Misterjunky said:
You must use odin version 3.10.7 only.
Here is odin v3.10.7 in case you need it:
https://www.androidfilehost.com/?fid=24052804347842132
Then odin flash the official Samsung firmware.
After the phone fully boots make sure that the oem unlock is enabled.
Never disable it.
Good luck
Have a nice evening.
Sent from my SM-G928T using Tapatalk
Click to expand...
Click to collapse
i rooted my phone, (forgot to enable oem unlocking), was working fine but now have the same issue as above. flashed stock firmware but phone stays on "samsung" screen...

kc720 said:
i rooted my phone, (forgot to enable oem unlocking), was working fine but now have the same issue as above. flashed stock firmware but phone stays on "samsung" screen...
Click to expand...
Click to collapse
Go into recovery mode and do a factory reset.
Reboot and it should boot normally.
Good luck.
Sent from my SM-G928T using Tapatalk

Misterjunky said:
Go into recovery mode and do a factory reset.
Reboot and it should boot normally.
Good luck.
Sent from my SM-G928T using Tapatalk
Click to expand...
Click to collapse
Thank you for reply. I did do a reset and erase cache. Still stuck on samsung screen. Pm shows the phone in device manager but this is all I have. More than 15 minutes...
{
"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"
}

Did you flash a custom kernel? That was the only way I could get past this to obtain root.

Accidentally flashed Note 4 Edge recovery image to Note 4 Official app, need help..

Hi, so today I rooted my Note 4 and installed the official TWRP app, I made the mistake of flashing the Note 4 Edge recovery firmware directly from the TWRP app and when I rebooted my phone updated and now the touch screen heavily distorts where I touch the screen in order to compensate for the edge that is not there. My phone is basically unusable but with some effort I can get into TWRP to try to restore to the back up I made before doing this but it doesn't fix the problem. The phone will also not boot into any sort of recovery mode and is not recognized by odin anymore. I don't know what to do here.. if anyone has any tips for me I'd be very appreciative. Thank you so much.

slothandtorpor said:
Hi, so today I rooted my Note 4 and installed the official TWRP app, I made the mistake of flashing the Note 4 Edge recovery firmware directly from the TWRP app and when I rebooted my phone updated and now the touch screen heavily distorts where I touch the screen in order to compensate for the edge that is not there. My phone is basically unusable but with some effort I can get into TWRP to try to restore to the back up I made before doing this but it doesn't fix the problem. The phone will also not boot into any sort of recovery mode and is not recognized by odin anymore. I don't know what to do here.. if anyone has any tips for me I'd be very appreciative. Thank you so much.
Click to expand...
Click to collapse
Try pulling the battery at least one minute, reinstall battery and boot directly to recovery or download mode. But if you can boot to system, you could install the Official TWRP Manager from Google Play and download the right TWRP image and flash it with the same app.
In the app, search "Samsung Galaxy Note 4" and scroll to bottom and select "...Qualcomm -- trlte", then "...Americas...". The file you need is twrp-3.1.1-0-trlte.img to flash with TWRP or the the recovery flash option in the app.
I've read many posters have flashed wrong recovery (Note Edge) but not corrupted partitions. But you may need to flash the stock tar if getting right TWRP recovery flashed, boot and opening dialer and dialing *#2663# and pressing the top left update button doesn't work.
{
"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"
}
Alternately, you can download this app and use the left tab to select secret codes and select code 2663 (if the dialer code doesn't work).
http://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
The 2663 secret code is to correct the touch screen calibration. You need to use your S-pen to open dialer or navigate until touch is restored.
Sent from my SM-N920P using Tapatalk

Thank you so much man I had done everything up to entering that last secret code and that did it for me. It's a damn shame I already have a new phone coming in the mail but thank you so so much.

wow, spoke a little too soon on this one. Now normal booting is failing and it goes straight to recovery, that and I can't get my computer to detect it in Odin

slothandtorpor said:
wow, spoke a little too soon on this one. Now normal booting is failing and it goes straight to recovery, that and I can't get my computer to detect it in Odin
Click to expand...
Click to collapse
When boot fails, do you see eMMC read or write failure (component failure)? If you see that, Samsung Support may offer to repair it for $75 USD and a week or more turnaround. Unless you have a warranty...
Your phone not detecting on PC could be a bad Samsung USB driver. Try reinstalling it; download it from Samsung Support for your model number. But give Odin and PC time if you're trying to install stock tar; it takes a minute or longer to verify the md5, then it may add your phone in COM tab on Odin as highlighted. You may see a comment in Odin log (view log while running), like please wait during this verification. Don't try to proceed without md5 verification and COM added.
Sent from my SM-N920P using Tapatalk

Tried again today and after a few restarts I got my phone to read in odin and wrote a stock tar.gz to it. I'm still updating as we speak but it looks like it's gonna work out thanks a bunch man.
samep said:
When boot fails, do you see eMMC read or write failure (component failure)? If you see that, Samsung Support may offer to repair it for $75 USD and a week or more turnaround. Unless you have a warranty...
Your phone not detecting on PC could be a bad Samsung USB driver. Try reinstalling it; download it from Samsung Support for your model number. But give Odin and PC time if you're trying to install stock tar; it takes a minute or longer to verify the md5, then it may add your phone in COM tab on Odin as highlighted. You may see a comment in Odin log (view log while running), like please wait during this verification. Don't try to proceed without md5 verification and COM added.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse

[HELP] SM-A520 stuck in Bootloader after trying to unbrick by installing Stock Rom

Hey guys, my Phone is stuck in the Bootloader after trying to install the Stock Rom with Odin.
I had to try to unbrick it because I wanted to unlock FRP and at least everything I tried has failed.
The last method I tried, bricked the Phone and now it's stuck in the Bootloader despite flashing the Stock Rom with Odin.
{
"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"
}
Please help, I don't now what to do anymore...

Hifty said:
Hey guys, my Phone is stuck in the Bootloader after trying to install the Stock Rom with Odin.
I had to try to unbrick it because I wanted to unlock FRP and at least everything I tried has failed.
The last method I tried, bricked the Phone and now it's stuck in the Bootloader despite flashing the Stock Rom with Odin.
Please help, I don't now what to do anymore...
Click to expand...
Click to collapse
Does Odin say the operation succeded? I think you just need to restart the phone lol

Baseminge said:
Does Odin say the operation succeded? I think you just need to restart the phone lol
Click to expand...
Click to collapse
Yes, the process got no problem, Odin said succeded.
I already tried restarting the phone multiple times... for example the phone stays in Bootloader for over an hour at the moment.

Hifty said:
Yes, the process got no problem, Odin said succeded.
I already tried restarting the phone multiple times... for example the phone stays in Bootloader for over an hour at the moment.
Click to expand...
Click to collapse
For "bootloader" you mean download mode or what? Cause I cannot see anything in your "this my screen now". Try to resent pic

Baseminge said:
For "bootloader" you mean download mode or what? Cause I cannot see anything in your "this my screen now". Try to resent pic
Click to expand...
Click to collapse
I mean the pre-boot screen, where the where model name, powered by android and so on stands.
https://imgur.com/a/eDI8PNr

Hifty said:
I mean the pre-boot screen, where the where model name, powered by android and so on stands.
https://imgur.com/a/eDI8PNr
Click to expand...
Click to collapse
Ok, It's download mode. I think you just need to press and hold vol- and power button simultaneously and when screen come black, waiting for the boot.
If won't work:
-Check you downloaded the correct firmware for your phone
-It's recommended to use Odin v3.13.1 and UNTICK auto-reboot
-Try to restart first in recovery and boot phone by recovery

Baseminge said:
Ok, It's download mode. I think you just need to press and hold vol- and power button simultaneously and when screen come black, waiting for the boot.
If won't work:
-Check you downloaded the correct firmware for your phone
-It's recommended to use Odin v3.13.1 and UNTICK auto-reboot
-Try to restart first in recovery and boot phone by recovery
Click to expand...
Click to collapse
Well, at first I took the newest Firmware Update, could it help to install an older version?
And how do I restart the Phone safely after installing the stock rom?

Hifty said:
Well, at first I took the newest Firmware Update, could it help to install an older version?
And how do I restart the Phone safely after installing the stock rom?
Click to expand...
Click to collapse
Now it seems to be stuck in Bootscreen...