My friend's J2 Prime (SM-G532G/DS) happened to be stucked at Security Error (blue screen), no idea how it get there. Tried to flash stock firmware. But after flashing, the phone booted back into the same blue screen, now with a line of red text at the top saying, "Custom binary blocked by FRP. (recovery. img)". Tried many different stock firmware (with 4 files) but none of them solved the problem. Can't boot into recovery, only download mode. Can someone give me detailed step by step on how to fixed this.
If it help, I'm from Malaysia. So maybe the firmware might need to be from this region. Not sure about the origin of the phone though. Also, what could be the reason for this to happen? I'm assuming root. Could it even happen on its own, I mean without rooting or flashing?
also G532G/DS - ARH1 bootloader
i've been going thru lots of ROMs (including testing Lineages), this have never happened to me before.
Flashing stock firmware thru Odin though, require OEM Unlocking ON in Developer Settings.
^ I mean, did you/your friend turn it on before flashing? if not, it actually succeeded?
Only solution might be possible:
Go to stock recovery (POWER + HOME + VOL-UP), wait for it to load, then factory reset from there.
I suppose some images might help!
I'm pretty sure the OEM if off because he know nothing about this thing. When I got it, it already like this. Can't get into recovery, after the first Samsung logo appear, it went straight into the error screen. Same thing happened after flashing.
I don't know how to post images here...
JEDAlive said:
I'm pretty sure the OEM if off because he know nothing about this thing. When I got it, it already like this. Can't get into recovery, after the first Samsung logo appear, it went straight into the error screen. Same thing happened after flashing.
I don't know how to post images here...
Click to expand...
Click to collapse
+ OEM Unlock: if disabled, Odin should've failed straight away and no reboot stuff going.
+ Can't get into recovery:
Is it true that you cannot get into recovery? If left stock, It should be an Android with spinning stuff, text is "installing update" then no command for a while ~2min, and it will go to normal recovery.
I mean, it is supposed to do "recovery" :v
+ Images: post it on Imgur (or any online image service). Copy link here, add space between "https://" and all the stuff there. Wont be considered URL i guess (havent tried)
Related
I need help, When I turn on my Nexus the screen stays stuck on the Google start up screen. My phone is rooted with JellyBean. I have the Verizon version of the phone. I was also wondering how can I unroot my phone back to stock ICS?
http://forum.xda-developers.com/showthread.php?t=1626895
Follow that to return to stock.
biscuitownz said:
http://forum.xda-developers.com/showthread.php?t=1626895
Follow that to return to stock.
Click to expand...
Click to collapse
Thanks.
Right now I'm still stuck at the google start-up screen which still won't load up. I don't know if I messed up my phone.
I'm not really tech savvy with the entire flashing and fixing, but I'll help you best as I can.
You're not in trouble even if the phone hangs on the google logo upon a boot up. If you can hold the volume up and then the power, you should have access to bootloader. You can boot cwm to install stock rom, which I believe will remove root (superuser) and return to stock ics or jelly bean depending on which stock rom you install. If you've unlocked the phone (which I assume you did), you can lock it again by using the command "fastboot oem lock," which will lock the device back to factory settings.
I've basically surmised the linked thread above. If you're still confused, look at this thread here. Cheers!
biscuitownz said:
http://forum.xda-developers.com/showthread.php?t=1626895
Follow that to return to stock.
Click to expand...
Click to collapse
My phone is facing same problem, but with a twist and need help.
I did not unlock, root, or install any bootloader before, no CWM.
But my phone is now in bootloop, after a hang for unknown reasons.
I tried recovery, reboot, even fectory reset, but it just goes into a continous loop of google word logo, flashing trapezoids, and then a glitchy stop, then loop.
Sometimes it will just loop at the google word logo.
So I thought my original ROM must be damaged, and wanted to flash a new rom, hoping to fix things.
Problem is, I managed to unlock, but cant get through to rooting as whenever I try to root, it will attempt to run, but will end up saying :
FAILED <status read failed<too many links>>
Also i did not have USB debug before my phone went into bootloop. So now during rooting and attempts to install CWM, there is supposed to be a reboot and a change of USB debug setting required, which can't happen in my case as it couldn't even reboot to stock android.
So I am stuck with a bricked phone currently, when I didn't do anything in the first place...
details of my phone when in fastboot mode:
Product name - tuna
Variant - maguro
HW Version - 9
BOOTLOADER VERSION - PRIMEKK15
BASEBAND VERSION - I9250XXLA2
CARRIER INFO - NONE
SERIAL NUMBER - sorry not disclosed
SIGNING - production
Please let me know what i should do next... Hope to recover my phone
Thanks.
Make sure before you start, you have the correct drivers for your phone. Use this for your driver, and put the phone on bootloader. Make sure when you type fastboot devices, it shows the device. You can then unlock, boot cwm, flash either stock or other roms from there.
I have been using the i747z ROMs for quite some time and after trying a bunch of other ROMs I always reverted back to theirs. So when their 3.0 version came out with Android 4.3 I installed it, using ClockWorkMod recovery. Right after it installed, CWM displayed a message about the boot loader and to fix it. So I went ahead and did that (Don't really remember what the message was) What I know is that I lost root. Also the phone could not connect to the mobile network, only on Wifi. So this morning, I factory reset the phone again, and attempted to root the phone with Odin with CF-Auto-Root-d2att-d2uc-samsungsghi747 (which I had used when I first rooted the phone). Now the phone doesn't boot past the 2nd samsung logo, it starts out with the Samsung logo with the blue circle around it, then the AT&T Rethink Possible and then the plain white Samsung logo. Also, the LED has a slow blue flicker.
I can get the phone into download mode and I have used Odin to attempt to load the stock firmware and the stock bootloader. But after restarting the phone I can't get past the same screen described above.
I am pretty sure this is not related to the i747z v3.0 ROM but rather something a miss with the order in which things need to start in Android. I have done some reading on that but I am not sure what I need to do to correct this soft brick situation. ( I have googled "soft brick" as well)
Any thoughts would be greatly appreciated!
mozphoto said:
I have been using the i747z ROMs for quite some time and after trying a bunch of other ROMs I always reverted back to theirs. So when their 3.0 version came out with Android 4.3 I installed it, using ClockWorkMod recovery. Right after it installed, CWM displayed a message about the boot loader and to fix it. So I went ahead and did that (Don't really remember what the message was) What I know is that I lost root. Also the phone could not connect to the mobile network, only on Wifi. So this morning, I factory reset the phone again, and attempted to root the phone with Odin with CF-Auto-Root-d2att-d2uc-samsungsghi747 (which I had used when I first rooted the phone). Now the phone doesn't boot past the 2nd samsung logo, it starts out with the Samsung logo with the blue circle around it, then the AT&T Rethink Possible and then the plain white Samsung logo. Also, the LED has a slow blue flicker.
I can get the phone into download mode and I have used Odin to attempt to load the stock firmware and the stock bootloader. But after restarting the phone I can't get past the same screen described above.
I am pretty sure this is not related to the i747z v3.0 ROM but rather something a miss with the order in which things need to start in Android. I have done some reading on that but I am not sure what I need to do to correct this soft brick situation. ( I have googled "soft brick" as well)
Any thoughts would be greatly appreciated!
Click to expand...
Click to collapse
After flashing through odin did you format data?If not try it.
Go into recovery and wipe data.
**SOLVED**
Thanks xXFl4sh, I had tried that.
Solved!
Alright where do I start? How about RTFM Some how I had missed the part about flashing a bootloader and a modem after the ROM. Not recalling having to do that before, I skipped right over it. Once the recovery CWM 6.0.3.1 was finally loaded, getting the flashing the ROM, the bootloader and the modem was easy as usual.
The key was having to use Odin to install a recovery in .tar or .tar.md5 format since I could not access a Recovery Mode on the GS3, as well as a rooted stock image (I used root66_ATT_I747UCDLK3.tar.md5 which is a rooted Android 4.1.1 for AT&T) For the recovery, I couldnt' find a .tar or .tar.md5 for ClockWorkMod (did find a utility to convert it, but didn't want to introduce another variable into the mix) so I used one from Team Win Recovery (v2.6.3.0) and with that I loaded the CWM recovery. Once all of that was in place, I proceed to factory reset, clear data, cache, system and then flash the new ROM, bootloader and modem.
In all of this I learned quite a bit about the whole process and how to narrow down possible resolutions. I still see the "Rom may flash stock recovery on boot" message after flashing either a ROM, bootloader or modem, but just backing out without answering Yes or No seems to work. Also (and this may be related, I don't see the option to restart in recovery from shutdown menu). Don't really know what that's all about for now, and honestly don't want to mess around (at least for a while)
I know the steps are general, but I hope this can help some else if they get their devices in a soft brick situation. As for the i747z v3 ROM with 4.3, I really like it, everything works (Wifi,Blutooth,tethering) and the battery seems good as well.
Thanks!
I don't know what happened but all of a sudden my gs4 stopped working and I could only get it up to the logo before it rebooted again. I am a total noob so I don't have any developer apps or firmware or whatever. I tried using Kies but I get stuck on the serial number part as I have entered everything on the box and behind the battery with none of them working. Now I am trying to use Odin but I think I messed up my phone even more. On the box it says M919NUVUEMK5 so I downloaded the firmware with that same code but originally I had downloaded the NUVUFOK one and used that. So I followed the guide and used that NUVUFOK file, and it seemd to be working as the download bar on my phone was almost done, but then all of a sudden it failed. I figured that was the wrong firmware so I went back and got the MK5 one, but now when I try to do the same thing with this firmware the bar only loads a tiny bit and then stops. Also the phone won't start up properly after I tried this, now it says there is an issue with the firmware upgrade and I need to use recovery mode in Kies. I have no idea what to do or what I am even doing, all I want to do is get my phone working again.
If you live in the US, you can take it to Best Buy an they will use there software to get it working again. Its hell of a lot less work.
Reformat
Operation Ivy said:
I don't know what happened but all of a sudden my gs4 stopped working and I could only get it up to the logo before it rebooted again. I am a total noob so I don't have any developer apps or firmware or whatever. I tried using Kies but I get stuck on the serial number part as I have entered everything on the box and behind the battery with none of them working. Now I am trying to use Odin but I think I messed up my phone even more. On the box it says M919NUVUEMK5 so I downloaded the firmware with that same code but originally I had downloaded the NUVUFOK one and used that. So I followed the guide and used that NUVUFOK file, and it seemd to be working as the download bar on my phone was almost done, but then all of a sudden it failed. I figured that was the wrong firmware so I went back and got the MK5 one, but now when I try to do the same thing with this firmware the bar only loads a tiny bit and then stops. Also the phone won't start up properly after I tried this, now it says there is an issue with the firmware upgrade and I need to use recovery mode in Kies. I have no idea what to do or what I am even doing, all I want to do is get my phone working again.
Click to expand...
Click to collapse
Hello. You will need to reformat your device so odin can recognize it. This can be done by using odin to flash a custom recovery like TWRP. The download link for that custom recovery is: https://dl.twrp.me/jfltetmo
Once you have that downloaded open odin and select AP option. Browse to where you saved TWRP and select it. Now proceed with flashing like normal. after its done flashing turn off the device.
After it is completely off hold the power button and volume up button simultaneously until you see the blue words on the top right corner of the boot logo screen.
Now you are in the twrp custom recovery menu. Go to Wipe > Advanced Wipe then select everything except for external sd, USB, and internal storage.
Once it is complete formatting turn the phone off again and boot back into download mode. Now you can reflash the correct firmware for your phone. I recommend using this firmware instead since it is a whole image rather than an incremental update. After flashing this your phone will reboot, give you the loading android logo and then the phone will start up once again! Good luck
The phone is giving the firmware error message because you tried to flash an older firmware to the phone.
Download the latest firmware for your phone and reflash it using Odin and the original Samsung USB cable.
AndroidInitiate said:
Hello. You will need to reformat your device so odin can recognize it. This can be done by using odin to flash a custom recovery like TWRP. The download link for that custom recovery is:
Once you have that downloaded open odin and select AP option. Browse to where you saved TWRP and select it. Now proceed with flashing like normal. after its done flashing turn off the device.
After it is completely off hold the power button and volume up button simultaneously until you see the blue words on the top right corner of the boot logo screen.
Now you are in the twrp custom recovery menu. Go to Wipe > Advanced Wipe then select everything except for external sd, USB, and internal storage.
Once it is complete formatting turn the phone off again and boot back into download mode. Now you can reflash the correct firmware for your phone. I recommend using this firmware instead since it is a whole image rather than an incremental update. After flashing this your phone will reboot, give you the loading android logo and then the phone will start up once again! Good luck
Click to expand...
Click to collapse
I downloaded it and it worked but now can't get past the "blue words" part. When trying to go into recovery it gives me either of two screens, one says "system software not authorized by samsung has been found on your phone." with red words "secure fail: kernel" or the blue words show up followed by red words that say "recovery is not seandroid enforcing" and then yellow words "set warranty bit: recovery". the phone is still resetting and freezing randomly.
Operation Ivy said:
I downloaded it and it worked but now can't get past the "blue words" part. When trying to go into recovery it gives me either of two screens, one says "system software not authorized by samsung has been found on your phone." with red words "secure fail: kernel" or the blue words show up followed by red words that say "recovery is not seandroid enforcing" and then yellow words "set warranty bit: recovery". the phone is still resetting and freezing randomly.
Click to expand...
Click to collapse
you are using the T-Mobile Samsung Galaxy S4 right?
AndroidInitiate said:
you are using the T-Mobile Samsung Galaxy S4 right?
Click to expand...
Click to collapse
Yes it is the SGH-M919N model.
Operation Ivy said:
Yes it is the SGH-M919N model.
Click to expand...
Click to collapse
You need to boot into recovery holding volume up and power button simultaneously. Once your in recovery mode format it. then you can reflash stock firmware.
I'm trying to prevent having to use the warranty if I don't have to as this was just a mistake on my part.
I've tried going completely back to stock removing TWRP and everything and I'm in the stock recovery right now with the error that says:
"Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory reset and erase all user data stored on this device."
Which I've done twice now (since going back to stock bootloader) and nothing happens.
These are the steps I took-
downloaded factory ota image.
flashed flash-all.bat
moved boot.img to adb directory and flashed boot image on both a & b slots
ran flash-all.bat again (just in case)
start up & get the loading G screen that either never stops loading or refreshes to this screen with the error above.
I tried locking the bootloader and that just caused a "no os" error. So I unlocked it, re-ran flash-all.bat and now I'm back with this error. I mean at least I can get into the bootloader & recovery?
I'm going to try pressing the 'try again' about 20 times in a row. I saw something online that said pressing try again that many times it randomly worked. I'm still searching and trying to figure this out but that is going to be my next step while I search.
I posted this on reddit about an hour ago but still no responses so I wanted to reach out here as well.
Just for more information: I am able to get into stock recovery & bootloader just fine. It is just the OS that doesn't want to load. I have factory reset this thing more times than I can count. I've tried flashing the images google has up. I did the very first one and the 8.1.0.
Neither are working & I don't understand why. The ones that are listed here.
Just for kicks here is a screenshot of the whole window and what happens during the flashing in the flash-all.bat. Here they are.
HELP?
While I was doing those screenshots I fixed it! I downloaded 8.1.0 (OPM1.171019.011, Dec 2017) just for the heck of it since the others weren't working. Figured it wouldn't hurt anything, would just cause the same error to appear and it took longer to install, which I figured was good, AND NOW I WAS ABLE TO GET INTO THE STARTUP SCREEN! WOO!
DudeThatsErin said:
I'm trying to prevent having to use the warranty if I don't have to as this was just a mistake on my part.
I've tried going completely back to stock removing TWRP and everything and I'm in the stock recovery right now with the error that says:
"Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory reset and erase all user data stored on this device."
Which I've done twice now (since going back to stock bootloader) and nothing happens.
These are the steps I took-
downloaded factory ota image.
flashed flash-all.bat
moved boot.img to adb directory and flashed boot image on both a & b slots
ran flash-all.bat again (just in case)
start up & get the loading G screen that either never stops loading or refreshes to this screen with the error above.
I tried locking the bootloader and that just caused a "no os" error. So I unlocked it, re-ran flash-all.bat and now I'm back with this error. I mean at least I can get into the bootloader & recovery?
I'm going to try pressing the 'try again' about 20 times in a row. I saw something online that said pressing try again that many times it randomly worked. I'm still searching and trying to figure this out but that is going to be my next step while I search.
I posted this on reddit about an hour ago but still no responses so I wanted to reach out here as well.
Just for more information: I am able to get into stock recovery & bootloader just fine. It is just the OS that doesn't want to load. I have factory reset this thing more times than I can count. I've tried flashing the images google has up. I did the very first one and the 8.1.0.
Neither are working & I don't understand why. The ones that are listed here.
Just for kicks here is a screenshot of the whole window and what happens during the flashing in the flash-all.bat. Here they are.
HELP?
While I was doing those screenshots I fixed it! I downloaded 8.1.0 (OPM1.171019.011, Dec 2017) just for the heck of it since the others weren't working. Figured it wouldn't hurt anything, would just cause the same error to appear and it took longer to install, which I figured was good, AND NOW I WAS ABLE TO GET INTO THE STARTUP SCREEN! WOO!
Click to expand...
Click to collapse
You tried fastbooting the "factory OTA image" Well, that mistake number one. Just use the stock factory image, not the OTA.
Never mind.?
Congrats on fixing it.
For future reference, and if you ever reset your phone again, you should perform: fastboot flashing unlock_critical <--this will wipe your phone!
As you can see in your screenshots, that failed, each time. This was the cause of your failure(s): FAILED (remote: Flashing is not allowed for Critical Partitions)
The last one worked because it flashed the proper bootloader (TMZ12a). Had you not used that image, it still would have failed.
What was your fix?
@DudeThatsErin -As mentioned by uicnren, you still need to unlock_critical or your phone will not upgrade properly, and you won't be able to flash full factory images. When you unlocked your bootloader, there were two steps but you only completed the first one. See the sticky by Nathan for step-by-step instructions. Unlocking critical will wipe the phone again, but then you will be set.
Hi there,
first of all, sorry for my bad english.
I want to remove the Stock ROM from my Tablet (Samsung Galaxy Tab S4 | SM-T830) and install something else (https://www.getdroidtips.com/android-12samsung-galaxy-tab-s4/).
For some Reason Samsung forced me to do a factory reset to unlock the bootloader (maybe I did it wrong, but now it happened, so it is how it is). Now the OEM Unlock Options says "Bootloader is already unlocked", but when I go into Download mode, I have multiple Problems:
1.: When I enter download mode by Booting into Recovery (adb reboot recovery) and choose "reboot to bootloader", OR by entering it directly using "adb reboot bootloader", I dont get the Warning Screen so I get into download mode directly.
2.: When entering Dowload mode as descibed in problem 1, I also dont get the informations at the Top left, I only see the Download Icon on a blue background but when restarting the tablet and holding Volume Up and Volume Down simuntainuasly, it will show the warning (in the correct cyan colors) and in the next step it shows me those status informations at the top left.
3.: However, regardless to how I get into download mode, the colors of the download mode screen will change to a blue filter version after one second. but I did never activate any blue filter on the device, and on any other device, the colors are displayed correctly.
4.: Any instalation with Odin3 failed on the device, regardless to how i got into download mode
In any online article I read, noone has any problems with installing something when in download mode.
Also, the KG-Status is displayed as "checking, I dont know if this is good or not.
What am I doing wrong, why can't I install anything on the device?
what is wrong with download mode? post a picture.
drivers installed correctly? check in windows device manager.
what does not work with Odin? what error message?
First of all, thank you for your reply!
1.: The Picture shows that the is something wrong with the Download mode of the Tab S4, because the Colors are not being displayed correctly (as you can see, the colors of the other devices are much more cyan), and I would not have mentioned that if the device would just be unable to show colors correctly, but in the Warning before the Download mode, the Colors are displayed as they are on the other devices, so the eventually the device wants to tell me something, but I dont know what.
2.: Well, I am pretty sure that the drivers are installed Correctly, because Flashing a Galaxy Tab S2, Galaxy S8 and Galaxy S5 worked perfectly with the same driver.
3.: I'l attach a Screenshot of Odin.
ALso, what does "KG STatus: Checking" mean? Is it the reason for the problem, or is it good? On the Web I could only find "Kg Status: Locked" and "KG Status: Unlocked". should I unlock it? If yes, how?
you say any installation with Odin3 failed. you are trying to flash TWRP.
try to flash something different.
https://topjohnwu.github.io/Magisk/install.html#instructions
not sure about the display, though.
Well, I have a porblem with the Program that is mentioned in the Guide you linked, Frija asks for a CSC, and I dont know what I have to enter there, I only know that the device is a SM-T830/gts4lwifi.
CSC is region code
Rooting, ODIN, Firmware, CSC Information And Myths Debunked / Noob's Guide To Samsung Devices
Since a lot of people will have their Galaxy S22 Ultra soon and I myself am thinking about either getting an S21 Ultra or S22 Ultra, I wanted to summarise a lot of information I found out during researching as Samsung devices are quite different...
forum.xda-developers.com
Okay, maybe I am an Idiot or so, but it does not work, Frija does not find any Firmware for the SM-T830, flashing a custom build of TWRP also does not work, folowing other Guides to install Magisk doesn't work, and using Odin to Flash a System Imagge (in the Guide I saw this was how they did it) also does not work.
Also "adb sideload" does not work using the Stock Recovery, so I really need TWRP to do so.
When searching for the KG Status, I found out that Samsung devices are checking themselves for a Week or so before accepting any Unofficial images, since I factory reseted the Tablet two days ago, the device may check itself. So should I eventually wait a Week before trying it again?
I dont know what I could do, so that seems logical for me, do you think that might solve the Problem?
Well, if RMM/KG state is prenormal you would see message "Only official released binaries are allowed to be flashed"
Anyway, try to flash official ROM and wait for KG state while device is connected to internet.
you can download according to your region from https://samfw.com/firmware/SM-T830
T830Guy said:
Okay, maybe I am an Idiot or so, but it does not work, Frija does not find any Firmware for the SM-T830, flashing a custom build of TWRP also does not work, folowing other Guides to install Magisk doesn't work, and using Odin to Flash a System Imagge (in the Guide I saw this was how they did it) also does not work.
Also "adb sideload" does not work using the Stock Recovery, so I really need TWRP to do so.
When searching for the KG Status, I found out that Samsung devices are checking themselves for a Week or so before accepting any Unofficial images, since I factory reseted the Tablet two days ago, the device may check itself. So should I eventually wait a Week before trying it again?
I dont know what I could do, so that seems logical for me, do you think that might solve the Problem?
Click to expand...
Click to collapse
Setting the 7 days back works
T830Guy said:
Okay, maybe I am an Idiot or so, but it does not work, Frija does not find any Firmware for the SM-T830, flashing a custom build of TWRP also does not work, folowing other Guides to install Magisk doesn't work, and using Odin to Flash a System Imagge (in the Guide I saw this was how they did it) also does not work.
Also "adb sideload" does not work using the Stock Recovery, so I really need TWRP to do so.
When searching for the KG Status, I found out that Samsung devices are checking themselves for a Week or so before accepting any Unofficial images, since I factory reseted the Tablet two days ago, the device may check itself. So should I eventually wait a Week before trying it again?
I dont know what I could do, so that seems logical for me, do you think that might solve the Problem?
Click to expand...
Click to collapse
try this: https://forum.xda-developers.com/t/...-twrp-and-magisk.4059227/page-2#post-88134465