Database Info

[q] nexus s 4g cant flash stock plz help!!!!

I can do everything with my phone except for flash stock no matter how many times and ways I try it won't work. Have tried using SW Updater and it gives me the following message:
"Error Occured! Cancel Download!"
I also tried with fastboot and after the phone reboots I get this message:
<waiting for device>
For some reason the phone continues to show these two lines at the bottom of the bootloader screen:
USB Control Init
USB Control Init End
I am really in need of help. Can somebody please help me?

KJOM said:
I can do everything with my phone except for flash stock no matter how many times and ways I try it won't work. Have tried using SW Updater and it gives me the following message:
"Error Occured! Cancel Download!"
I also tried with fastboot and after the phone reboots I get this message:
<waiting for device>
For some reason the phone continues to show these two lines at the bottom of the bootloader screen:
USB Control Init
USB Control Init End
I am really in need of help. Can somebody please help me?
Click to expand...
Click to collapse
Hi,
What are coming from? rooted with what ROM.. what recovery?
And are you trying to flash the newest ICS from stock recovery?
I guess Im just trying to see what you did and what you had before it all happened.
Thanks

Im currently running the [AOSP][4.0.4]Codename Android 2.0.0RC|Fully Open Source+Nightly Builds Rom and I have CWM Recovery and I am trying to flash the OTA ICS Update.

http://forum.xda-developers.com/showthread.php?p=24297394
[OFFICIAL][ROM][CWM] NS4G IMM76D 4.0.4 | Rooted | Zipalign | ETC
This is what u want if ur already rooted
Good luck
Vs Nexus S 4G

I already know how to do everything else, my problem is flashing back to stock because of those messages. I only want to flash back to stock.

I had an issue where fastboot wouldn't recognize my device when I was in bootloader. For whatever reason it worked if I hooked up my phone via usb then rebooted into bootloader.
Anyway you can use this method
http://forum.xda-developers.com/showthread.php?t=1575502
Sent from my Nexus S 4G using Tapatalk 2

Did you install the wrong bootloader by any chance?

KJOM said:
I already know how to do everything else, my problem is flashing back to stock because of those messages. I only want to flash back to stock.
Click to expand...
Click to collapse
That's why I asked for some clarity on ur post.
U want to Unroot and return to stock.
Its a big difference when someone reads and tried to help.
What root method did u use?
Vs Nexus S 4G

@vidaljs, I used the fastboot method to install IMM26D & @psg190, I don't think so.

KJOM said:
@vidaljs, I used the fastboot method to install IMM26D & @psg190, I don't think so.
Click to expand...
Click to collapse
Boot into the bootloader (volume up + power button) and tell me what it says for bootloader version.

It says:
FATBOOT MODE
PRODUCT NAME -HEARING
HW VERSION - D720SPAKE1
BASEBAND VERSION - D720SPALC1
CARRIER INFO - SPR
SERIAL NUMBER - 32************EC
LOCK STATE - UNLOCKED
SELECT - VOL UP or VOL DOWN
EXCUTE - POWER
REBOOT BOOTLOADER
REBOOT
RECOVERY
POWER OFF
USB Control Init
USB Control Init End

KJOM said:
It says:
FATBOOT MODE
PRODUCT NAME -HEARING
HW VERSION - D720SPAKE1
BASEBAND VERSION - D720SPALC1
CARRIER INFO - SPR
SERIAL NUMBER - 32************EC
LOCK STATE - UNLOCKED
SELECT - VOL UP or VOL DOWN
EXCUTE - POWER
REBOOT BOOTLOADER
REBOOT
RECOVERY
POWER OFF
USB Control Init
USB Control Init End
Click to expand...
Click to collapse
Well, that's good that you have the right bootloader. Mine had the same problem, but I accidentally flashed the wrong bootloader. Pretty sure that's why I had no fastboot or USB mount. I had to send mine into Samsung for repairs.

So what's wrong with it?

KJOM said:
So what's wrong with it?
Click to expand...
Click to collapse
With yours? I don't know.
With mine? I don't know.

lol dam

KJOM said:
lol dam
Click to expand...
Click to collapse
Sent my jacked up phone into Samsung. It was unlocked and had TWRP on it (like I said before, no fastboot and none of my computers with any combination of OS/USB cable would recognize the phone). Samsung either repaired or replaced it and it is shipping back to me today.

Thats good for u. But I still can't flash stock, other than that, I'm doing great with mine.

RESOLUTION: Assuming you've installed the correct Samsung ADB drivers, you will have had to go to Device Manager, and tell it which driver to use. Good job at getting to to the fastboot screen! You're almost done.
At this point, (on fast boot) open up Device Manager again on your computer. Now your phone is being recognized as something completely different: Android 1.0 was what mine said. Right click on it, 'update driver software', 'browse my computer for...', 'let me select from a list of...", then choose "ADB Interface" from the list. If ADB interface is missing from the list, you haven't installed the drivers.
It will then give you a list of ADB Samsung phone drivers to choose from. I just chose the most updated ones (2012 was at the end of the strand of information about it, as opposed to 2010 which was further down). The second you click next, your phone (assuming you still have the command prompt up on your computer, saying its searching or waiting for your phone) will start to fly through the process of returning you back to stock.
DONE!
Good luck.

Thanks jackharvest. I didn't know Samsung had their own ADB drivers. That was the key! After I configured Windows Device Manager, as you indicated, to use the Samsung driver, all I had to do was run the windows batch file "flash-all.bat" which I had downloaded from google's "Factory Images for Nexus Devices." Unfortunately, their instructions don't tell use about the steps you identified!

Help Please Please with my bricked Alcatel Ot 5020 (Evolve)

This is my first time asking for help directly here, I always find the answers in the other threads solved, but this time I can not find an answer.
I have a alcatel one touch 5020t evolve its a MTK6575 (t-mobile but is used in el salvador), I used to MTKDroidTools to install CWM Revocovery, I did back up with the same program but apparently did not because i look and i cant find anything in the back up folder, only left some files called:
ALCATEL-ONE-TOUCH-5020T_130818__boot_patched_140129-175612.img
ALCATEL-ONE-TOUCH-5020T_130818__recovery_140129-175612.img
in the folder called recovery.
Now the phone on, the startup screen and then turns off, I can enter a menu by pressing on + vol +, where it says enter recovery mode or normal mode, before they tried to install cwm I could go in and delete everything from there, now I get the menu of recovery mode and normal mode but since does not enter recovery mode, got it turns off, like when entering the normal mode.
I tried to flash with sp flash tool but I get an authentication error that is on the img
The pc recognizes my phone, makes the sound when you connect something, now if we go to Device Manager, a device called first appears:
MTK USB Port
After that is disconnected and then a new one appears called :
Media Tek Preloader USB VCOM Port
But there ir a problem, then this becomes a repetitive one disconnects and connects the other, but only when I connect the phone without battery only stays in:
MTK USB Port.
Help what can i do to revive my phone ???????????????

you found any solution i have the same problem ?

:/
harold99 said:
you found any solution i have the same problem ?
Click to expand...
Click to collapse
Sorry, but i could not solve yet, nobody helps me

So were you able to flash cwm to the device? there are several threads requesting a custom recovery for this device and either way could you upload those first two .img files I may be able to use them to try to recover my device
*** Okay so the problem is that the boot loader on this device is locked and for the time being a custom recovery is not possible. I still have access to the recovery on my device so if I could find a way to build an update file from the source code or an official firmware update I could fix mine. Yours may be too far gone. sorry.

any luck with a solution? How close to one have you got to...

ipeedalil said:
*** Okay so the problem is that the boot loader on this device is locked and for the time being a custom recovery is not possible.
Click to expand...
Click to collapse
A friendly warning: Don't just mess around with the Bootloader, that's one delicate piece of software, try to find how to unlock it first, then we can talk of changing the recovery. For rooting purposes I can attest that you can safely root it using the OneClickRoot solutions around the net. I used some chinese root and it worked like a charm.

Soft Bricked 5020T
carlitox2301 said:
This is my first time asking for help directly here, I always find the answers in the other threads solved, but this time I can not find an answer.
I have a alcatel one touch 5020t evolve its a MTK6575 (t-mobile but is used in el salvador), I used to MTKDroidTools to install CWM Revocovery, I did back up with the same program but apparently did not because i look and i cant find anything in the back up folder, only left some files called:
ALCATEL-ONE-TOUCH-5020T_130818__boot_patched_140129-175612.img
ALCATEL-ONE-TOUCH-5020T_130818__recovery_140129-175612.img
in the folder called recovery.
Now the phone on, the startup screen and then turns off, I can enter a menu by pressing on + vol +, where it says enter recovery mode or normal mode, before they tried to install cwm I could go in and delete everything from there, now I get the menu of recovery mode and normal mode but since does not enter recovery mode, got it turns off, like when entering the normal mode.
I tried to flash with sp flash tool but I get an authentication error that is on the img
The pc recognizes my phone, makes the sound when you connect something, now if we go to Device Manager, a device called first appears:
MTK USB Port
After that is disconnected and then a new one appears called :
Media Tek Preloader USB VCOM Port
But there ir a problem, then this becomes a repetitive one disconnects and connects the other, but only when I connect the phone without battery only stays in:
MTK USB Port.
Help what can i do to revive my phone ???????????????
Click to expand...
Click to collapse
I have had a OT-5020T with all the same symptoms as you describe. After much research and diagnosis here is what I have learned and know to be true.
You have soft bricked your phone. For this phone it results in the boot loop you described. At present a Custom Recovery that works is not available for this phone and any attempt to flash an existing one results in a soft brick. There are apps that will flash a Custom Recovery while the phone is one but once you reboot ... !!! Bricked!! This is because ...
a) the memory mapping for this phone is different that other OT-5020 models, so the Custom Recovery placement and indexing is wrong when flashed, causing the boot-loop, and inability for Custom Recovery to load,
and ,
b) the bootloader is locked for the 5020T (different story for other OT 5020 models), and no one has found a way around it yet. Trying to flash back stock firmware for the OT-5020T requires it to be unlocked.
One Touch Update 2.8.0 doesn't seem to want to work one the phone has been altered in this way. SPtools won't work because you need an accurate OT-5020T scatter file (memory map) ,and certification file (bootloader unlocker) to flash any image. In addition to all this the phone doesn't maintain a steady usb connection long enough to allow use of android tools adb and fastboot commands although it does can stay connected in a different mode.
What I have used to restore my phones firmware is a package from Furious Gold that allows the phone to be flashed to factory firmware. I have used it successfully, so I can confirm that the phone wasn't a permanent brick.

Alcatel 5020t T-Mobile plis help flshe file

please am in need of alcatel 5020w firmware, please if someone is having it or having that same phone and want to read the firmware for me my email is [email protected]
thanks

The Unofficial Official Nokia 8 Bootloader Unlock Method

If you try to use the bootloader unlocker apk from Nokia and your Nokia 8 has an android version that's past a certain version, the apk will flat out fail with a "Device not support." error message. And chances are, your Nokia 8 will be at an incompatible android version. So to unlock the bootloader, you will need to downgrade your phone to a legitimate version of android 8.1.0 so the apk will not error out and get you a verification code. This guide will show you how. NOTE THAT THIS METHOD WILL ERASE ALL INTERNAL DATA ON YOUR PHONE.
-
This update zip is what you need for the TA-1004: https://android.googleapis.com/pack.../f9cb380bd9c2bf1b6ddebcab9dcf389843eb2d39.zip
It may be different for the TA-1012, but according to that earlier post, it does not seem to be the case. Nevertheless, just to be safe, here's the zip for the TA-1012: https://android.googleapis.com/pack.../139c94fd08f52fbd3b852ab4ef5c6515fffb784e.zip (I don't have a TA-1012 so I wasn't able to test this particular zip.)
So basically, to make sure there's no problems, make sure in the Developer's options on the phone that OEM unlocking is enabled, then put your SD card into the phone. Plug the phone into your computer. Copy the update zip that you need somewhere onto the SD card. Disconnect the USB cable. Shut down the phone. Then, while holding down the Volume Up button, reconnect the USB cable. You should see a sad android with "No command" displayed. Now release the Volume Up button. Then hold down the power button and then JUST PRESS once on the Volume Up button. You should be at a recovery menu. Using the volume keys, scroll down to the 'Apply update on SD card' option and select it. Select the zip that you copied over to the SD card earlier and then let it install for a while. It will probably pop up with a 'timestamp too old' error, but just ignore this. The update will install anyway. Then once it's done, do a factory reset on the phone and then shut down. MAKE SURE THERE'S NO SIM CARD IN THE PHONE.
Now that's out of the way, boot the phone up again and just click through the first-time setup screens but DO NOT ENABLE WI-FI or any kind of internet connection. We don't want the phone to update itself back to Android 9. Now plug the phone in again. Copy the bootloaderunlocker apk from Nokia's website onto the phone. Install it. Put in the email address you want the unlock key emailed to. Then voila! You'll get the verification code. Put it into the form on Nokia's website and you'll be emailed an unlock.key file. From there, the site will tell you how to proceed.
A HUGE thanks to: THMSP and frankoid
They did all the work. <3

why another topic ?!

foxbatul said:
why another topic ?!
Click to expand...
Click to collapse
Because I don't expect people to dig around in all the Nokia 8 Guide threads to find the exact and, to my knowledge, only way to unlock the bootloader. Furthermore, I found this solution in a sort of unrelated thread, which would make the solution even harder to find for the average user.

S5Guy said:
Because I don't expect people to dig around in all the Nokia 8 Guide threads to find the exact and, to my knowledge, only way to unlock the bootloader. Furthermore, I found this solution in a sort of unrelated thread, which would make the solution even harder to find for the average user.
Click to expand...
Click to collapse
I understant but not.
Here it's not the place for lazy ones. Or for apple boys.
Unlock, modding, ROMs are for people with other approach. So this kind of topics make more noise instead to help.
Just my 2 cents.
BTW - thank you posting "downgrade to oreo" procedure.
it s the offline one ( my choice was to use "register to beta" and" unregister").
no need SD card or something, just a good wifi connection and patience.

Thanks for this. I just noticed that the "OEM unlocking" is disabled and greyed out on my TA-1012 device. Will it still work?

I cant get into the Phone without establishing an Internet connection, any tips?

Thank you so much OP this method worked perfectly I finally was able to unlock the bootloader

There seems no way for me to get past the Wifi selection page, how did all of you got into the system?

Ok solved this one, had to Update to P remove the Google Account linked to the Device and downgrade again.
It's Part of the Factory Reset Protection that you cant skip the Wifi and Update Screens.

Thank you for posting this guide, it got me to unlocking the bootloader on my TA-1004 after I received the described "Device not support" error.
I enabled "OEM unlocking" before downgrading my firmware and the option was grayed out for me afterwards. However the bootloader unlock still worked correctly other than being forced to us a Mac as none of my windows machines would show the device in fastboot mode.

ma401 said:
Thank you for posting this guide, it got me to unlocking the bootloader on my TA-1004 after I received the described "Device not support" error.
I enabled "OEM unlocking" before downgrading my firmware and the option was grayed out for me afterwards. However the bootloader unlock still worked correctly other than being forced to us a Mac as none of my windows machines would show the device in fastboot mode.
Click to expand...
Click to collapse
If only Nokia 8 had support for custom roms. Im stuck on the december security patch of Pie because it has a prerooted boot img posted somewhere on this forum. Ot would be fun to play around with a google-free custom rom like lineageOS. But sadly devs dont seem to give a damn about the phone

MDV106 said:
If only Nokia 8 had support for custom roms. Im stuck on the december security patch of Pie because it has a prerooted boot img posted somewhere on this forum. Ot would be fun to play around with a google-free custom rom like lineageOS. But sadly devs dont seem to give a damn about the phone
Click to expand...
Click to collapse
I think we can thank HMD for that by making unlocking the bootloader so difficult. I only ended up buying the Nokia 8 because I got it for such a good deal ($220 CAD) and needed a temporary phone to tide me over until I can get something better. I feel sorry for anyone who paid full price for this phone and I don't blame developers for moving to something more accessible.

S5Guy said:
If you try to use the bootloader unlocker apk from Nokia and your Nokia 8 has an android version that's past a certain version, the apk will flat out fail with a "Device not support." error message. And chances are, your Nokia 8 will be at an incompatible android version. So to unlock the bootloader, you will need to downgrade your phone to a legitimate version of android 8.1.0 so the apk will not error out and get you a verification code. This guide will show you how. NOTE THAT THIS METHOD WILL ERASE ALL INTERNAL DATA ON YOUR PHONE.
-
This update zip is what you need for the TA-1004: https://android.googleapis.com/pack.../f9cb380bd9c2bf1b6ddebcab9dcf389843eb2d39.zip
It may be different for the TA-1012, but according to that earlier post, it does not seem to be the case. Nevertheless, just to be safe, here's the zip for the TA-1012: https://android.googleapis.com/pack.../139c94fd08f52fbd3b852ab4ef5c6515fffb784e.zip (I don't have a TA-1012 so I wasn't able to test this particular zip.)
So basically, to make sure there's no problems, make sure in the Developer's options on the phone that OEM unlocking is enabled, then put your SD card into the phone. Plug the phone into your computer. Copy the update zip that you need somewhere onto the SD card. Disconnect the USB cable. Shut down the phone. Then, while holding down the Volume Up button, reconnect the USB cable. You should see a sad android with "No command" displayed. Now release the Volume Up button. Then hold down the power button and then JUST PRESS once on the Volume Up button. You should be at a recovery menu. Using the volume keys, scroll down to the 'Apply update on SD card' option and select it. Select the zip that you copied over to the SD card earlier and then let it install for a while. It will probably pop up with a 'timestamp too old' error, but just ignore this. The update will install anyway. Then once it's done, do a factory reset on the phone and then shut down. MAKE SURE THERE'S NO SIM CARD IN THE PHONE.
Now that's out of the way, boot the phone up again and just click through the first-time setup screens but DO NOT ENABLE WI-FI or any kind of internet connection. We don't want the phone to update itself back to Android 9. Now plug the phone in again. Copy the bootloaderunlocker apk from Nokia's website onto the phone. Install it. Put in the email address you want the unlock key emailed to. Then voila! You'll get the verification code. Put it into the form on Nokia's website and you'll be emailed an unlock.key file. From there, the site will tell you how to proceed.
A HUGE thanks to: THMSP and frankoid
They did all the work. <3
Click to expand...
Click to collapse
Hello i too tried unlocking my nokia 8 but the laptop doesnt recognise my phone in fastboot Mode.i need help i installed all drivers but the same problem arises

shivaji namburu said:
Hello i too tried unlocking my nokia 8 but the laptop doesnt recognise my phone in fastboot Mode.i need help i installed all drivers but the same problem arises
Click to expand...
Click to collapse
try fastboot -i 0x2e04 [Your_Command]

sumitinhome said:
try fastboot -i 0x2e04 [Your_Command]
Click to expand...
Click to collapse
Actually even pc doesnt detect the device and it doesn't show in my pc section
---------- Post added at 04:57 PM ---------- Previous post was at 04:55 PM ----------
sumitinhome said:
try fastboot -i 0x2e04 [Your_Command]
Click to expand...
Click to collapse
What is that i didn't get it will it work.....?
If possible put the command clearly ....to understand

shivaji namburu said:
Actually even pc doesnt detect the device and it doesn't show in my pc section
---------- Post added at 04:57 PM ---------- Previous post was at 04:55 PM ----------
What is that i didn't get it will it work.....?
If possible put the command clearly ....to understand
Click to expand...
Click to collapse
If pc is not detecting the phone the its driver problem. try to install proper drivers.

sumitinhome said:
If pc is not detecting the phone the its driver problem. try to install proper drivers.
Click to expand...
Click to collapse
I mean it detects when the phone is in nornal mode but when mobile is booted into fastboot mode it doesn't detect

shivaji namburu said:
I mean it detects when the phone is in nornal mode but when mobile is booted into fastboot mode it doesn't detect
Click to expand...
Click to collapse
Yes i understood, make sure you are using latest adb drivers.
More on it. Make sure you have USB debugging on from Developers options. Also make sure oem unlocking option is on.
1 - Connect your phone to pc while powered on.
2 - From adb folder open command prompt and type adb devices (If your device is detected in adb mode while powered on)
2.1 - if not detected in adb devices.. then go to developer settings and revoke USB debugging authorizations. then again repeat the above process in point no. 2.
3 - if detected now then type adb reboot bootloader, let it reboot in download mode.
4. then type 'fastboot flash unlock [your unlock key]' if this doesnt work then try 'fastboot -i 0x2e04 flash unlock [unlock key]'
5. after that either 'fastboot oem unlock' or 'fastboot -i 0x2e04 oem unlock'
See if this works.

Struck on Nokia Logo
S5Guy said:
If you try to use the bootloader unlocker apk from Nokia and your Nokia 8 has an android version that's past a certain version, the apk will flat out fail with a "Device not support." error message. And chances are, your Nokia 8 will be at an incompatible android version. So to unlock the bootloader, you will need to downgrade your phone to a legitimate version of android 8.1.0 so the apk will not error out and get you a verification code. This guide will show you how. NOTE THAT THIS METHOD WILL ERASE ALL INTERNAL DATA ON YOUR PHONE.
-
This update zip is what you need for the TA-1004: https://android.googleapis.com/pack.../f9cb380bd9c2bf1b6ddebcab9dcf389843eb2d39.zip
It may be different for the TA-1012, but according to that earlier post, it does not seem to be the case. Nevertheless, just to be safe, here's the zip for the TA-1012: https://android.googleapis.com/pack.../139c94fd08f52fbd3b852ab4ef5c6515fffb784e.zip (I don't have a TA-1012 so I wasn't able to test this particular zip.)
So basically, to make sure there's no problems, make sure in the Developer's options on the phone that OEM unlocking is enabled, then put your SD card into the phone. Plug the phone into your computer. Copy the update zip that you need somewhere onto the SD card. Disconnect the USB cable. Shut down the phone. Then, while holding down the Volume Up button, reconnect the USB cable. You should see a sad android with "No command" displayed. Now release the Volume Up button. Then hold down the power button and then JUST PRESS once on the Volume Up button. You should be at a recovery menu. Using the volume keys, scroll down to the 'Apply update on SD card' option and select it. Select the zip that you copied over to the SD card earlier and then let it install for a while. It will probably pop up with a 'timestamp too old' error, but just ignore this. The update will install anyway. Then once it's done, do a factory reset on the phone and then shut down. MAKE SURE THERE'S NO SIM CARD IN THE PHONE.
Now that's out of the way, boot the phone up again and just click through the first-time setup screens but DO NOT ENABLE WI-FI or any kind of internet connection. We don't want the phone to update itself back to Android 9. Now plug the phone in again. Copy the bootloaderunlocker apk from Nokia's website onto the phone. Install it. Put in the email address you want the unlock key emailed to. Then voila! You'll get the verification code. Put it into the form on Nokia's website and you'll be emailed an unlock.key file. From there, the site will tell you how to proceed.
A HUGE thanks to: THMSP and frankoid
They did all the work. <3
Click to expand...
Click to collapse
after this my phone struck on nokia logo, please help,,,,
i'm training to recovery mode \ download mode but not working both

gvreddy said:
after this my phone struck on nokia logo, please help,,,,
i'm training to recovery mode \ download mode but not working both
Click to expand...
Click to collapse
Factory reset by wiping cache and data via recovery. Start over and try again.

"Your device is corrupt, It can't be trusted and will not boot" - 7 Pro 5G (GM1920)

"Your device is corrupt, It can't be trusted and will not boot" - 7 Pro 5G (GM1920)
Tried to relock my bootloader and nwo im stuck on "Your device is corrupt, It can't be trusted and will not boot" is there any tool out there that will help to unbrick the 5G version for EU? (GM1920) the MSMTool doesnt seem to support this version or does anyone know how to get out of it?!
Thanks

exxpired said:
Tried to relock my bootloader and nwo im stuck on "Your device is corrupt, It can't be trusted and will not boot" is there any tool out there that will help to unbrick the 5G version for EU? (GM1920) the MSMTool doesnt seem to support this version or does anyone know how to get out of it?!
Thanks
Click to expand...
Click to collapse
You never relock your device until you know it's stock and bootable. Can you get into fastboot?

exxpired said:
Tried to relock my bootloader and nwo im stuck on "Your device is corrupt, It can't be trusted and will not boot" is there any tool out there that will help to unbrick the 5G version for EU? (GM1920) the MSMTool doesnt seem to support this version or does anyone know how to get out of it?!
Thanks
Click to expand...
Click to collapse
We are trying to get an msmtool, but your situation could help us prioritize getting it from OnePlus, pm me

Whoareyou said:
We are trying to get an msmtool, but your situation could help us prioritize getting it from OnePlus, pm me
Click to expand...
Click to collapse
I actually managed to boot to fastboot, change the bootslot and luckily 10.0.0.3 was released which allowed me to install and wipe out TWRP (which I didnt realise got installed, I thought I set it to only boot to it not install it) im guessing this is why it went into the corrupt state.

Hi everyone
I have same problem could you help me pls

hey, I have the same issue and I don't know how to solve it.
phone run out of battery, I connected to charge it and when I started it up, I am getting the message "Your device is corrupt. It can't be trusted and will not boot". This error is looped, phone reboots every few seconds and immediately goes to this message.
I bought the phone in Europe and used it as is... (no mods, no ROM flashing, no fiddling with the Bootloader or the OS.
Now, what is interesting is that I can get into fastboot (by pressing power + vol up + vol down) but I have no idea what to do next. Tried all the options in the menu (recovery mode, restart bootloader, start, power off) and all of them lead to the same message above (your device is corrupt).
if while in fastboot I connect the phone to a PC, and run fastboot.exe devices in command line it does recognize the phone (I can see the serial number).
Any ideas what I should do next?

Fastboot, Samsung Galaxy A51

Hello, i wanted to ask how to fix the fastboot mode.
Everytime when i try to access it, it just says "Entering Fastboot..."and thats all.
I dont want to close it, thats not my problem, i just wanna flash a recovery.img, and the fastboot seems not working. Any ideas?

M3DUS4 said:
Hello, i wanted to ask how to fix the fastboot mode.
Everytime when i try to access it, it just says "Entering Fastboot..."and thats all.
I dont want to close it, thats not my problem, i just wanna flash a recovery.img, and the fastboot seems not working. Any ideas?
Click to expand...
Click to collapse
this could be because the galaxy A51 wasnt built with fastboot, and the code to launch this option was just reused from a different device, or because something isnt connecting properly.

Hello, I have the same ... Android 11 (and currently 12) (from Frija). So it is not the fault of incorrect configuration or with connecting. Only something is wrong with this phone ...

I have this device and this solved it for me:
Enable OEM unlocking in developer settings
Shut down the phone
Hold volume up and volume down
Plug in a USB cable connected to a computer (the computer being turned on)
Keep holding
You're in download mode!
Side note: This might not work in USA or Canada, I am from europe and it works here. I have no idea if it works in another region. Also, you can't just flash a recovery.img on Samsung since there is no real "fastboot", you have to use download mode and Odin.

But I know how to enter download mode... Problem is Fastboot mode...

There is no fastboot mode on a modern Samsung device. If there is, it's fake and you cannot flash anything with it. As you can see even from Wikipedia, Odin is the Samsung replacement of fastboot.
So no fastboot, only download mode.
If a guide is saying to use fastboot, it is not compatible with Samsung.
If you would tell me why you specifically need fastboot, I'll be happy to tell you how you can do it with Odin, if possible.

Because I have Samsung Galaxy A51 5G (A516B) with new Android 12 and I can't do a root! Because I can't upload TWRP (custom recovery) because I haven't OEM unlock option in Deveoper Option. I tried trick with set back date by 7days but not succes. Everything I;ve metioned here - I did at my phone with Android 11.
And... I have read that I can turn this fu**ing OEM option by comend at ADB: fastboot oem unlock.
Phew ...
So this fastboot method is the last method to do a root with my phone.

Upload TWRP by Odin in download mode -ends red warning - of corse...
Have you any ideas?
I would be grateful for help...

I have read this fastboot method at:
How to Unlock Bootloader On Samsung Galaxy Phones [EASY GUIDE]
Are you looking for a Complete tutorial on How To Unlock Bootloader on Samsung Galaxy Phones? If yes, then you have come to the right place.
www.guidetoroot.com

Yeah, that guide is not relevant on any modern Samsung device. Besides, even if it was, which it isn't, you would first need to enable OEM unlocking from the Developer Settings.
But the fact that you don't have an option for OEM unlock is weird, since I have the exact same device model and it is there for me.
May I ask what is your region and is your phone locked to a telephone carrier?

My region is PLS - Poland. And not - phone is not locked. Have you the newest system Android 12?

Yes, I do. It's weird that there isn't even an option for you.
I'll try to come up with some new ideas if I have time...

I'll be glad for it...

Hej, do you have any idea?

stanwin said:
Hej, do you have any idea?
Click to expand...
Click to collapse
Have you tried everything listed here?

BloodyFruitDestroyer said:
Have you tried everything listed here?
Click to expand...
Click to collapse
Yes, I did. Evething exept the last one...

You could try it. It might be risky, but it's the only option I personally can come up with right now.

I've tried this option but Odin stuck on "files verification". Any help?

have any of you encountered this problem?
And how did you solve it?

You can also try searching for combination firmware for your device online