Hello guys,
i need your profressinal help. First of all please excuse my bad englisch. But this forum is my last hope.
I rooted a Samsung A5 (SM-A520F) and everything was fine. But yesterday my girlfriend rebooted this phone it was FAP locked. So i googled a very long time and found a lot of solutions. But i did some misstakes. What i've done:
Phone flashed by combination firmware
Enabled USB Debugging
Flashed the stock OEM (Oreo 8.0) and it bricks on installing hidden.img. Today i now my choose was very badly, but it is happend. I flashed the Stock rom with CSC File and not the Home_CSC which bricked.
I have no possibiliies to flash another ROM... not the combination or a custom Recovery. The Debugging seams to be disabled. The OEM unlock is the same and my bootloader was overflashed by the stock rom.
I didn't know about the new FRP System and created on every mobile phone a junk google account. So i have no choice to enable FRP on the normal way.
Thank you very much
Isn't there any possibilitys to get my phone back?
hello guys,
i'm trying a lot of days to fix my fault. Is anybody there who is able to help me? Is thif phone totally bricked?
Related
Hi all,
I've got the Sony Xperia S and unlocked the bootloader and rooted it once and flashed it with the AOKP, but that didn't work, so I tried the Cyanogenmod 10.0 (Jelly Bean). In summary I think it was the wrong Combination of kernel and custom rom, because it didnt boot anymore and got stuck at the logo.
So I closed the bootloader again and installed the official stock rom from Sony, and all got fine, luckily.
With some more reading into right forums and better knowledge I got the right custom rom and kernel and tried to unlock the bootloader again, but suddenly it didnt work.
Message: Failed (remote: oem unlock 0xF (und noch mehr F) )
I did all with fastboot and the right adb drivers, the phone is installed correctly.
Yesterday I asked for my problem in a shop and the guy said, that the bootloader of any Sony device would close completely, if the (right or wrong) unlock code is used for too many times (like the limit of 10 times).
If he's right, I've got a big problem. But can't I open it with an alternatvie method? Or is there just any mistake?
Thanks for any answer
Chriszo
i dont know, but ive already relocked and unlocked many times without error ,
try to do it again and be sure to input the correct 0xKEY
CM10 contains it's own kernel so could never be a wrong combination of rom and kernel. Did you actually unlock the bootloader or just root the phone? Sounds like your bootloader was locked and you were trying to flash still
Sent from my 4.2.2 Xperia S via Tapatalk
Thanks for the answers.
I don't still know what constellation I really tried to instal the kernel and firmware, but I think it was an advanced stock kernel and then the firmware of the aokp. After that I tried the Cyanogenmod, but the device just didnt boot, there was only the logo.
I remember to have taken the kernel named ics17.elf and the advanced stock kernel with the official 4.0.55 build number.
The the device was rooted and the "sd card" was not wiped, but the data of the apps were deleted.
So the bootloader was open because the kernel can't be flashed with a locked bootloader.
After that I flashed the aokp and then the cyanogen mod.
Because of no booting I relocked the bootloader and installed the official firmware from sony.
Since then I try to unlock the bootloader with this damn error
I try to unlock with another computer. Maybe it work and its a simple solution. To unlock my bootloader i need to use my wife´s laptop.... i try in my compputer many times, install drivers, uninstall, and a lot of tricks but fastboot give me "error" all the times... lol
I just chatted and called with the Sony support (nice to hear great english at the phone ) and again got to hear, that they aren't able or allowed to give any information about the bootloader because of the possibility to loose the warranty of the phone.
I dont know really where my problem is but I think the code is not working any more, although I cant imagine of that
Is there any other way to do that? Or do I just do a stupid mistake ???
Thanks
Chris
Chriszo said:
I just chatted and called with the Sony support (nice to hear great english at the phone ) and again got to hear, that they aren't able or allowed to give any information about the bootloader because of the possibility to loose the warranty of the phone.
I dont know really where my problem is but I think the code is not working any more, although I cant imagine of that
Is there any other way to do that? Or do I just do a stupid mistake ???
Thanks
Chris
Click to expand...
Click to collapse
No no no!
Another guy on xda did it with FlashTool on locked bootloader. I was able to do it until the logo...
Apparently you only can flash roms I think, not?
Anyway Sony supports Open Developer Community as well, they give you info about bootloader here:
unlockbootloader.sonymobile[dot]com
No, I cant flash any rom, therefore I need an unlocked bl. And the stock rom from sony isnt available in the internet, just with the Sony-mobile-update-service.
Well, of course I tried the way Sony dicribes on this webside, as explained below -.-
Got the solution ??
Hey I have the same exact problem and i did the same things as you did ... did get a solution?? please inform me if you did.....
Hi guys,
I've tried everything, but after successful root I can't unlock bootloader and flash recovery mode. Fastboot is also not running. The stock ROM is awfully slow and I wanted to flash a new one... That is what I see when I enter the service menu (see the attachment) :/
Please, help :c
Xperia S LT26i (2012, I think)
Its just not allowed to unlock your bootloader.
Nothing more to say.
Send thanks to Orange, where you device is from.
You may try other ROMs based on stock one, but optimized. As said above you can't do anything about it. I would suggest you to update the phone to a new one with unlocked bootloader, SXS too old nowdays with it's S3 CPU.
Hello
i am new here.
I got a Samsung A3 2017 SM-A320FL which is locked with a pattern. I need the files from the phone(contacts,images,etc...). No one knows the pattern. Is there any way that i can get the files before doing a factory reset. USB debugging is not ON, nor is OEM unlock checked. Cant flash custom recovery because "Custom binary blocked by FRP lock". The phone is working but i cant unlock it and i dont want to factory reset it because i need those files. Anyone got an idea?
Thanks
anyone, anything????
samsungguy123 said:
Hello
i am new here.
I got a Samsung A3 2017 SM-A320FL which is locked with a pattern. I need the files from the phone(contacts,images,etc...). No one knows the pattern. Is there any way that i can get the files before doing a factory reset. USB debugging is not ON, nor is OEM unlock checked. Cant flash custom recovery because "Custom binary blocked by FRP lock". The phone is working but i cant unlock it and i dont want to factory reset it because i need those files. Anyone got an idea?
Thanks
Click to expand...
Click to collapse
Well, don't know if this will help but you can always try! : https://forum.xda-developers.com/galaxy-core/help/guide-removing-frp-protection-samsung-t3275584
https://forum.xda-developers.com/general/general/bypass-frp-lock-samsung-smartphones-z3x-t3725717
Sent from my SM-A520W using XDA Labs
samsungguy123 said:
Hello
i am new here.
I got a Samsung A3 2017 SM-A320FL which is locked with a pattern. I need the files from the phone(contacts,images,etc...). No one knows the pattern. Is there any way that i can get the files before doing a factory reset. USB debugging is not ON, nor is OEM unlock checked. Cant flash custom recovery because "Custom binary blocked by FRP lock". The phone is working but i cant unlock it and i dont want to factory reset it because i need those files. Anyone got an idea?
Thanks
Click to expand...
Click to collapse
login to google dashboard with the google account associated with the device, or you can use the samsung account associated with the phone also.
Cheers
Hello,
I'm in a rather peculiar situation. I bought a Nexus 5X from eBay recently (I know) which was advertised as having the common bootloop issue, of which I saw there seems to be a fix for. After receiving the phone I found that not only does it bootloop, but the bootloader is still locked and the previous owner has set up the phone and used a PIN lock on the lockscreen, leaving me unable to get into the settings to enable Developer settings and unlock the bootloader. Does anyone know of any kind of fix for this? Just to reiterate, I cannot flash any stock rom, and there is no custom recovery on the device. I am not new to unlocking bootloaders and flashing custom firmware, and I have contacted the previous owner to no avail. Any help in this issue would be greatly appreciated.
I have searched the forums but as my situation is compounded of multiple problems (locked BL, no custom recovery and PIN lock) I feel like I have hit a dead end.
I am with ya
I have the exact situation i would love to know if you have figured it out. i have two of them as a package deal from ebay. Both 5x.
advertised as bootloop. wont go past the google screen.. one them i actually got to fire up but then ran into the pin thing...
Can you get in fastboot mode ? If so, you can try flashing a custom recovery
I have a Mi 10T purchased in Italy, and therefore coming factory loaded with a "branded" firmware RJDEUHG. It should be a Windtre modded ROM, please correct me if I'm wrong.
The latest known working ROM was the miui_APOLLOEEAHGGlobal_V12.5.3.0.RJDEUHG_da9e1c75b5_11.0.
Tired of waiting for the slow updates, compared to the unbranded global rooms, I decided to de-brand the phone and upgrade to a stock RJDEUXM.
But none of the XM firmware would load from recovery, therefore I applied and successfully unlocked the bootloader.
With the bootloader unlocked I managed to successfully flash
apollo_eea_global_images_V13.0.2.0.SJDEUXM_20220329.0000.00_12.0_eea_ad6f7ce846
apollo_eea_global_images_V12.5.12.0.RJDEUXM_20220208.0000.00_11.0_eea_664a15ed19
but both got stuck in a bootloop right after flashing.
During one of the many attempts, I used the MiFlash tool and accidentally left the default Flash & Lock option, the flashing was successful and the bootloader was locked.
At the moment I'm on V13.0.2.0.SJDEUXM, and can load onto bootloader and recovery, while, as mentioned before, the system won't load and get stuck in bootloop.
If I try to unlock the bootloader once again, the MiUnlock does not recognize the phone while in fastboot mode, remaining in the "Not connected to the phone" screen.
Any help would be really appreciated.
maybe, this is the solution, seems the same issue
https://c.mi.com/thread-3265050-1-0.html
fastboot devices
fastboot continue
if you have some lucky, boot normally
otherwise follow all the step
bye