Database Info

[Q] Fastboot broke my USB need Help

After trying to unlock my phone and flashing stock rom through CWM I accidently downloaded the rom for the at&t model. I own the sprint model. After flashing the incorrect boot img and radio img the fastboot just spat out errors so closed the CMD and booted up the phone. No longer does the USB work i have tried several computers none detecting it in either bootloader or within the android os. The android os doesnt even ask to mount it it just charges. Any help would really be aprreciated!

kambokid said:
After trying to unlock my phone and flashing stock rom through CWM I accidently downloaded the rom for the at&t model. I own the sprint model. After flashing the incorrect boot img and radio img the fastboot just spat out errors so closed the CMD and booted up the phone. No longer does the USB work i have tried several computers none detecting it in either bootloader or within the android os. The android os doesnt even ask to mount it it just charges. Any help would really be aprreciated!
Click to expand...
Click to collapse
OK firstly never close CMD when it is doing stuff that can cause damage to your PC, device etc. It can cause serious damage
I haven't tried this myself but you could try using a different USB connector. If that still doesn't recognise your device then it is a hardware problem or you have messed up you device.
If it works then download the sprint version and flash.
Hope this helped,
UselessSniper001

Wait what ?
So you wanted to unlock to flash stock ROM with cwm recovery but you used fastboot to flash boot radio etc .img's ?

UselessSniper001 said:
OK firstly never close CMD when it is doing stuff that can cause damage to your PC, device etc. It can cause serious damage
I haven't tried this myself but you could try using a different USB connector. If that still doesn't recognise your device then it is a hardware problem or you have messed up you device.
If it works then download the sprint version and flash.
Hope this helped,
UselessSniper001
Click to expand...
Click to collapse
Ive already tried several different USB cables. Thanks for the suggestion though.
albundy2010 said:
Wait what ?
So you wanted to unlock to flash stock ROM with cwm recovery but you used fastboot to flash boot radio etc .img's ?
Click to expand...
Click to collapse
It was a fastboot image.

Transfer a stockish ROM (can be deodexed & rooted, doesn't really matter) via WiFi and flash in CWM.

polobunny said:
Transfer a stockish ROM (can be deodexed & rooted, doesn't really matter) via WiFi and flash in CWM.
Click to expand...
Click to collapse
CWM Is no longer there after i restored it I was able to flash a stock ICS through normal recovery but the usb is still not working.

From a powered off state, if you hold VOL down and then press POWER, can you access download mode?
If yes, and you connect it to your computer (I'm going to assume you are using a windows computer), can you hear the device connected sound? It should get detected.

I messed up with Huawei Mate 9. Please Help.

Guys i have a really really big problem with mate 9 (MHA-L29). I broke both twrp and system same time (please don't ask why.)
Now, my phone don't open, just fastboot&rescue mode, useless huawei recovery (which can't format data neither install stock rom). Besides, i can't install stock rom because i tried once, and i downloaded wrong system file, and i can't format the phone now. Because of that, stock rom that i download sd card not working too. Because there is a dload file in phone.
worst of all, i can't install twrp again, because my fastboot screen tell me that: "Phone Unloced" (with red) "FRP Lock" (with green). When i try to install twrp, adb says "Failed, remote command not allowed"
Now, if can install the twrp, all my problems will be solve. There is 1 custom rom (RomAur) and 1 system backup.
How can i install twrp with this situation?

Please someone help me i spend 2 days and still nothing! How can i open this phone? Stock rom, with/without root, custom rom whatever, just tell me how can i open this phone

up

You get that command when trying to flash the wrong recovery partition, was your room nougat or Oreo based?? If nougat it's fastboot flash recovery recovery.img and Oreo fastboot flash recovery_ramdisk recovery.img I think you are trying to flash the wrong partition

shae23 said:
You get that command when trying to flash the wrong recovery partition, was your room nougat or Oreo based?? If nougat it's fastboot flash recovery recovery.img and Oreo fastboot flash recovery_ramdisk recovery.img I think you are trying to flash the wrong partition
Click to expand...
Click to collapse
No, my twrp is not wrong, i installed before, and i used long time, till broken. I installed wrong twrp recovery over correct recovery (i was trying to chance recovery because project treble). Thats why my twrp broken. Now i try to correct one, but adb says "not allowed". My custom rom nougat based.

cannurkars said:
No, my twrp is not wrong, i installed before, and i used long time, till broken. I installed wrong twrp recovery over correct recovery (i was trying to chance recovery because project treble). Thats why my twrp broken. Now i try to correct one, but adb says "not allowed". My custom rom nougat based.
Click to expand...
Click to collapse
With FRP lock you'll have to use DC-Phoenix.
But it costs €19 (For 3 days usage).
Simply put you can bypass FRP with it by force closing DC-Phoenix when it has activated the backdoor, after this you can flash anything from fastboot (until you reboot).
So you could use it to flash back TWRP.
Or you can use it to install stock firmware

ante0 said:
With FRP lock you'll have to use DC-Phoenix.
But it costs €19 (For 3 days usage).
Simply put you can bypass FRP with it by force closing DC-Phoenix when it has activated the backdoor, after this you can flash anything from fastboot (until you reboot).
So you could use it to flash back TWRP.
Or you can use it to install stock firmware
Click to expand...
Click to collapse
I will try it. Thank you very much.

cannurkars said:
Guys i have a really really big problem with mate 9 (MHA-L29). I broke both twrp and system same time (please don't ask why.)
Now, my phone don't open, just fastboot&rescue mode, useless huawei recovery (which can't format data neither install stock rom). Besides, i can't install stock rom because i tried once, and i downloaded wrong system file, and i can't format the phone now. Because of that, stock rom that i download sd card not working too. Because there is a dload file in phone.
worst of all, i can't install twrp again, because my fastboot screen tell me that: "Phone Unloced" (with red) "FRP Lock" (with green). When i try to install twrp, adb says "Failed, remote command not allowed"
Now, if can install the twrp, all my problems will be solve. There is 1 custom rom (RomAur) and 1 system backup.
How can i install twrp with this situation?
Click to expand...
Click to collapse
During startup the menu there is a option to go in Huawei e-recovery, when you are at the start up menu hold volume up for about 5 second.

ConnerZhao929 said:
During startup the menu there is a option to go in Huawei e-recovery, when you are at the start up menu hold volume up for about 5 second.
Click to expand...
Click to collapse
No it wasn't work for me. But thank for your attention. I'm glad to find a good person to help me and my problem solved about 1-2 hour ago.

Special Request
Hey ante . Is it possible to help me ? I rooted my phone 2 days back and messed it up while downloading a framework app which ended me up in a bootloop. I have been reading and following your posts of you helping others. I don't really get the steps what I should follow.
My phone is unlocked. FRP shows Unlock.
Rooted on oreo and I tried e-recovery and fastboot steps you mentioned in other threads using kernel and ramdisk etc. ( After this I have lost access to TWRP and I am simply getting EMUI Screen with options for Factory Data Reset and Wipe Cache Partition. I don't know where it is going to lead me next :-/.
Also downloaded Huawei Extractor and tried to extracted specific files but the firmware file I have doesn't have CUST.img file.
Also the site link you mentioned for download firmware is in some other language and I am unable to search for my firmware.
I also tried the placing update file in the dload on my sd card but fails at 5%. The file was correct and I am sure I did'n download the wrong firmware.
Currently it shows this on the fastboot screen.
Andorid reboot reason
: AP_S_ABNORMAL 32
NA
Just don't know what I should be doing ? PLEASE HELP BRO?
ante0 said:
With FRP lock you'll have to use DC-Phoenix.
But it costs €19 (For 3 days usage).
Simply put you can bypass FRP with it by force closing DC-Phoenix when it has activated the backdoor, after this you can flash anything from fastboot (until you reboot).
So you could use it to flash back TWRP.
Or you can use it to install stock firmware
Click to expand...
Click to collapse

AniMaL92 said:
Hey ante . Is it possible to help me ? I rooted my phone 2 days back and messed it up while downloading a framework app which ended me up in a bootloop. I have been reading and following your posts of you helping others. I don't really get the steps what I should follow.
My phone is unlocked. FRP shows Unlock.
Rooted on oreo and I tried e-recovery and fastboot steps you mentioned in other threads using kernel and ramdisk etc. ( After this I have lost access to TWRP and I am simply getting EMUI Screen with options for Factory Data Reset and Wipe Cache Partition. I don't know where it is going to lead me next :-/.
Also downloaded Huawei Extractor and tried to extracted specific files but the firmware file I have doesn't have CUST.img file.
Also the site link you mentioned for download firmware is in some other language and I am unable to search for my firmware.
I also tried the placing update file in the dload on my sd card but fails at 5%. The file was correct and I am sure I did'n download the wrong firmware.
Currently it shows this on the fastboot screen.
Andorid reboot reason
: AP_S_ABNORMAL 32
NA
Just don't know what I should be doing ? PLEASE HELP BRO?
Click to expand...
Click to collapse
What's your firmware now?
You can get that info in Fastboot using
Code:
fastboot oem get-product-model
fastboot oem get-build-number
Since your recovery and fastboot still functions you probably will only need to use HWOTA to get back to stock.
It can be found here: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-oreo-update-package-t3699522
But post your cust/build before proceeding.
Also cust.img is found in UPDATE.APP in the hw data zip.

Problem Solved - Somewhat
Hey ante. Thanks for the promt reply. I got it solved by using CHIMERA tool.
Would like to suggest others also stuck with same issue to use CHIMERA.
Note - It is a paid tool and 100% legit and it can help with all problems related to FRP, Bootloader Lock / Unlock & also flashes back to factory firmware.
However what I am facing now I have flashed another version of firmware which isn't my region and some features of my phone like fingerprint scanner and other things are not working but phone is back to live. So Im glad and looking forward to searching for clean Oreo Firmware for my region to flash using CHIMERA Again.
Also, the sick and stupid part of it. I went to the service center and a person non-technical told me straight that you lost your device and it's of no use now. We cannot fix such issues 99% but I'll still ask my team and let you know after 3 days.
Thank God I didn give them and wasted my time and money.
As soon as I returned, I followed up to things and got it done myself. :good:
Anybody can possibly suggest a official firmware Oreo EMUI for Middle East Region!? If not which one can be flashed instead and where to download from?

Device needs old Google account after factory reset

I can't use my phone, it needs the older Google account in order to keep using it, but I don't remember the details. Is there a way to bypass this?! It's really stupid. iPhones has this sort of protection but Apple keeps track of its users so it makes sense... Now if you do a mistake here your phone is useless?! Or, there's a fix for it
Thanks

You can try to unlock bootloader and see if that works. Someone did data wipe on official firmware, with root and recovery if never asks

FreiKhost said:
I can't use my phone, it needs the older Google account in order to keep using it, but I don't remember the details. Is there a way to bypass this?! It's really stupid. iPhones has this sort of protection but Apple keeps track of its users so it makes sense... Now if you do a mistake here your phone is useless?! Or, there's a fix for it
Thanks
Click to expand...
Click to collapse
If you have twrp you can easily fix it. If not then there is a way to flash persist partition to fix it.

djhulk2 said:
You can try to unlock bootloader and see if that works. Someone did data wipe on official firmware, with root and recovery if never asks
Click to expand...
Click to collapse
But how? I can't enable developer options
superac11 said:
If you have twrp you can easily fix it. If not then there is a way to flash persist partition to fix it.
Click to expand...
Click to collapse
If I install TWRP, can I then install back original recovery? I want the phone to look as new after

EDIT: I just realised I can't install TWRP because I can't transfer files to my phone! because on FRP the computer does not recognise the device, and I also can't use ADB push because I can't turn on developer settings. Also, recovery mode does not work. but Fastboot does..

Through fastboot you can root, install twrp, wipe phone completely. You unlock boatloader in fastboot mode. May give you error saying locked...but you sure can still wipe the phone. There isn't a Samsung counter when you root, and you can lock back to official

djhulk2 said:
Through fastboot you can root, install twrp, wipe phone completely. You unlock boatloader in fastboot mode. May give you error saying locked...but you sure can still wipe the phone. There isn't a Samsung counter when you root, and you can lock back to official
Click to expand...
Click to collapse
I did it! In another way without fastboot. But just to know: How can I install TWRP via fastboot, if I can't transfer the zip file to the phone?

Tool all in one, once in fastboot mode it'll show you connected. Recovery and flasher option, you can install twrp and magisk. Works on official rom and custom

You have no chance to access the phone without the code. Its the google FRP lock.

Yess i have solution inbox me ..

This is Factory Reset Protection (FRP) which is a built-in security feature of Android 5.1 and later.

[Guide] TWRP and ROOT for A20e (A202f) [Updated]

My way of installing TWRP and ROOT on A20e (only tested on a202f).
Everything is working both on TWRP and MAGISK.
Versions:
-Magisk (v26.1)
-MagiskManager (v26.1)
-TWRP (3.6.1_9.0)
_________________________________________________
Download attached files:
-TWRP and ROOT(magisk) Odin is included!
_________________________________________________
#Factory reset is recommended!
#Make sure BOOTLOADER is unlocked!
#If you don't need MAGISK stop at step 6 and reboot to system
[TWRP Installation]
1. Extract required files, open ODIN (as Administrator) click on the "AP" button and choose TWRP-3.6.1_9.0.tar file.
2. In the "Options" menu untick "Auto-Reboot" .
3. On your phone boot into the "Download Mode" then in ODIN you can press the START button. (make sure you are connected to PC)
4. If everything is fine there should be green "PASS!" text in ODIN.
[ If your flashing failed make sure the bootloader is unlocked and check if cable is properly connected ]
[Don't let the phone boot into system because it will replace TWRP with stock recovery.img]
6. Boot into TWRP and FORMAT DATA (Wipe/Format Data) to remove encryption.
# If you don't need MAGISK you can reboot to system. Otherwise continue reading the guide.
[MAGISK Installation]
7. From TWRP reboot into RECOVERY again.
8. Connect your phone to PC or if you moved Magisk-v26.1.zip and Magisk-v26.1.apk to SD card then use SD card.
9. Flash the Magisk-v26.1.zip file and reboot to system.
10. When you boot into system install the Magisk apk.
11. Open it and finish the installation process.
12. Reboot
ENJOY!

[UPDATE]
-Updated versions of both TWRP and MAGISK
# TWRP 3.5.2_9-0 --> TWRP 3.6.1_9-0
# Magisk v23 --> Magisk v24.3
-Remodifed VBMETA
For ANY help contact me on Telegram: https://t.me/SerbianGeek

does encryp work on this ? dont need to backup just hide data part if fone is stole

This one flashes and boots the first time, but after a reboot there is the infamous error "only official released binaries are allowed to be flashed"

/dev/null/ said:
This one flashes and boots the first time, but after a reboot there is the infamous error "only official released binaries are allowed to be flashed"
Click to expand...
Click to collapse
No problems on my end, pal.

SerbianGeekster said:
No problems on my end, pal.
Click to expand...
Click to collapse
this phone is really a PITA. every time i try to do something it's 1 step forward and 2 steps back. never suffered so much. i flashed it like 20 times. all i want is a working twrp on stock rom and pass safetynet

/dev/null/ said:
This one flashes and boots the first time, but after a reboot there is the infamous error "only official released binaries are allowed to be flashed"
Click to expand...
Click to collapse
to bypass this error:
1. connect to wifi
2. change the date to 2 august 2019
3. boot into download mode
4. flash twrp

Thank you! It worked! No problems got me.
I kinda feel like idiot that I couldn't install it with that ease before

OH **** IT WORKED !!!
I've been at this for hours, thank you so much !!!

Hello,
I have a Samsung A20e running with the a202fxxu4cvk1 firmware (a11 version). I would like to install twrp and then to root it. I tried several tutorials (Odin, OEM unblocked, USB debugging, time change) but twrp installation fails with message 'custom recovery blocked by frp'.
Can anyone help me?

I duckduckgoed, and found this XDA thread, where the second post says the following :
Nemirtingas said:
FRP: https://www.samsung.com/us/support/frp/
FRP Just locks your phone if you alter the boot or recovery image and you had a google account registered. To unlock it you have to wipe data (factory reset) and reflash stock boot.img and recovery.img before using it again. If your cousin wants to flash my ROM (lineageos-13.0) he'd better not, its not stable and he will encouter random reboots and codecs bugs. The best thing to do is to remove FRP from his phone and flash Magisk (a root manager like SuperSU) and debloat it.
For more information, find the Grandprimevelte group on Telegram.
Click to expand...
Click to collapse
The rest of the posts mention the need for a modified boot.img, else your phone would brick after adding a Google account, but I don't know about that... I have MicroG on mine with a Google account and no problems.
Anyway, frp seems to be a related to having a Google account on your phone.

fjunk said:
Hello,
I have a Samsung A20e running with the a202fxxu4cvk1 firmware (a11 version) /.../ Custom recovery blocked by frp'.
Can anyone help me?
Click to expand...
Click to collapse
Hello..I was wrong. My issue is not related to frp but OEM. OEM is unlocked according to developper menu but is not effective. Not able to upload any custom rom or bootloader.
I read that there was issue (use of a volume up button in download mode).
Any idea?

fjunk said:
Hello..I was wrong. My issue is not related to frp but OEM. OEM is unlocked according to developper menu but is not effective. Not able to upload any custom rom or bootloader.
I read that there was issue (use of a volume up button in download mode).
Any idea?
Click to expand...
Click to collapse
Indeed, my issue is that in download mode I can only do a volume down button and power button to reboot in system mode. No option to unlock bootloader.

I think you only need to do that once, afterwards, download mode doesn't warn you.
What error message do you get exactly when trying to flash TWRP, at what point, and what gives it (phone, odin) ?

lPolarisl said:
I think you only need to do that once, afterwards, download mode doesn't warn you.
What error message do you get exactly when trying to flash TWRP, at what point, and what gives it (phone, od
Click to expand...
Click to collapse
Many thanks for your update. Attached are pictures of the mobile and the Odin result. The error is an OEM issue (red text on the top of the mobile screen). In other forums, I can see that the download mode has an option to unlock OEM bootloader. I can't see it on my phone.

Putting the camera so that it covers the error message, what an amazing idea xD
I have never encountered this error, so let's start from the beginning.
Have you enabled the developer options, and activated "allow USB debugging" on the phone ? Also, if there is an option "allow OEM unlock", activate that as well (not all Samsung phones have it).
Have you installed the proper ADB and Samsung drivers ? Which version of Odin are you using ?

lPolarisl said:
Putting the camera so that it covers the error message, what an amazing idea xD
I have never encountered this error, so let's start from the beginning.
Have you enabled the developer options, and activated "allow USB debugging" on the phone ? Also, if there is an option "allow OEM unlock", activate that as well (not all Samsung phones have it).
Have you installed the proper ADB and Samsung drivers ? Which version of Odin are you using ?
Click to expand...
Click to collapse
Thanks for your reply.
That's sure that it doesn't really help to hide the error message. Usb debugging is enabled (I am able to run adb commands) and OEM is unlocked on the preference setting. I did the test with Odin 3.13 but same results with newer version. I installed an A11 firmware (a202fxxu4cvk1).
Don't t know how to go ahead. It seems that I don't have the possibility to unlock OEM in the download mode interface....

Wait, what is that about the firmware ? What did you flash, how and why ?
also, try a patched version of Odin from this post (I have 3.13.1_3B)

lPolarisl said:
Wait, what is that about the firmware ? What did you flash, how and why ?
also, try a patched version of Odin from this post (I have 3.13.1_3B)
Click to expand...
Click to collapse
I bought a refurbished mobile phone (blackmarket). It came with a 9.0 version. I tried to update to a custom rom without success so I installed the latest 'official' version
Download Samsung Galaxy A20e SM-A202F XEF France A202FXXU4CVK1 firmware
Fast download latest Samsung Galaxy A20e firmware SM-A202F from France with A202FXXU4CVK1 and Android version 11
www.sammobile.com
I uploaded this version using Odin. I also tried the patched Odin version. I read that the patched version only works with a10 version.

Huh...
I have no idea how that behaves, but I hardly see why it would cause a problem.
What else could you try... Restore factory settings maybe ?
Pressing volume up when starting in download mode ? (Note, this supposedly relocks the bootloader if it has been unlocked, if that happens and your phone isn't 100% on stock, it will brick.)

help nedeed cant do anything

bootloader locked usb debugging off cant make command through adb sorry for bad English
cant do anything cant flash firmware tried everything

Use Rescue Mode. Enter bootloader by holding down Power + Vol Down while it was turned off, then use your volume keys to navigate to Rescue Mode. Then, go to https://pixelrepair.withgoogle.com/ and continue from there.

thanku for reply sean .. i tried rescue mode but when i choose nd to click rescue mode it atomatic comes only fastboot mode nd i cant flash or boot any img file or zip file

rubail said:
thanku for reply sean .. i tried rescue mode but when i choose nd to click rescue mode it atomatic comes only fastboot mode nd i cant flash or boot any img file or zip file
Click to expand...
Click to collapse
The point of Rescue Mode is to update the existing Android installation to a newer version. In this case of yours, your phone does not detect any valid OS, which is now pretty impossible if you want to install a fresh Android installation. Can you at least try to boot into Recovery mode?

thankss sean.. and no recovery mode opening only fastboot
only when i try to chose any other option for recovery rescue or any other it not opening only fastboot and barcode is opening this happened when i flash custom rom on both slot and flash stock rom on one slot and relocked bootloader my biggest mistake was this after all this my phone is not booting

The only last resort for you now is to contact Google Support, or go to a nearby Google Store for assistance. Since you custom'ed' ROM it, your warranty is now voided. If you still want to try fix it yourself, ask ChatGPT or Google for help :-(

ok iam going to give it to a shop or ill return my phone it has 1 years of waranty

rubail said:
ok iam going to give it to a shop or ill return my phone it has 1 years of waranty
Click to expand...
Click to collapse
if you can get into fastboot mode, I might try PixelRepair tool from Google, but there's a chance it'll format/wipe data...so be aware of that...
nevermind...didn't read fully...overlooked that you relocked bootloader...this is a time old tale of hard bricking device when relocking bootloader -- for next time (and for anyone considering it), the best way to do it is to use Google's official Android Flash Tool as it is from Google so you know it follows proper protocol to not hardbrick your device when relocking bootloader...

i can access fastboot mode but nothing help because of bootloader locked nd debugging is also disabled :'(

rubail said:
i can access fastboot mode but nothing help because of bootloader locked nd debugging is also disabled :'(
Click to expand...
Click to collapse
Your last chance is sideloading an OTA -- you don't need usb debugging or unlocked bootloader to do that. But it's a stretch as you locked the bootloader without flashing factory images on both slots which usually results in hard-bricks.