Database Develop

[RESOLVED]Did I just brick my phone? Any help at all is appreciated

So in preparation for the kitkat update, I did the following steps:
unrooted within superuser app
flash stock recovery
flash stock boot.img
flash stock system.img
Once I rebooted I downloaded the OTA and tried to install. Now, after that, I wasnt really sure what happened on the phone, as I passed the time by watching a youtube video on my computer. However, I looked back down, and it was inside the bootloader, giving a partition failure of some sort. And when I tried to flash anything, it gave a remote failure error. It won't boot into anything, and it says the device is locked. Can't do mfastboot oem get_unlock_data either, literally nothing but fastboot reboot works
do i have a $650 paper weight on my hands?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Fixed it! See the post at the very bottom of this page for the solution!

i would use RSD lite to get back to the latest 4.2.2

mj0528 said:
i would use RSD lite to get back to the latest 4.2.2
Click to expand...
Click to collapse
it won't boot at all

Well fastboot starts at least. If you try to reload stock firmware (4.2.2) using rsdlite(not fastboot from a command line) which error do you get?

Steve-x said:
Well fastboot starts at least. If you try to reload stock firmware (4.2.2) using rsdlite(not fastboot from a command line) which error do you get?
Click to expand...
Click to collapse
My device isn't showing up under rsdlite 6.1.4 at all

Sadly then I'm leaning towards it being a pretty looking brick. I've had many flash failures while experimenting with my XT1058s but I have never tried any custom recoveries so they were always recoverable with fastboot and rsdlite.
Hopefully someone else has some suggestions for you to try.

I flashed system.img, recovery.img, and boot.img from the original sbf file. not from the first OTA. and then the phone seems to have locked itself

alex94kumar said:
I flashed system.img, recovery.img, and boot.img from the original sbf file. not from the first OTA. and then the phone seems to have locked itself
Click to expand...
Click to collapse
Had you taken the first OTA already? If you had done that, you should have flashed these files from the new SBF file....
So, when you are in fastboot mode, your device is no longer getting recognized from fasboot command line? What does fastboot devices show?

tejaskary said:
Had you taken the first OTA already? If you had done that, you should have flashed these files from the new SBF file....
So, when you are in fastboot mode, your device is no longer getting recognized?
Click to expand...
Click to collapse
Ah. there's my problem. I flashed the files from the factory moto X.
And the device is recognized in fastboot, I can send it commands, it's just that none of them except fastboot reboot actually work

alex94kumar said:
Ah. there's my problem. I flashed the files from the factory moto X.
And the device is recognized in fastboot, I can send it commands, it's just that none of them except fastboot reboot actually work
Click to expand...
Click to collapse
Can you try these commands and see if anything changes?
fastboot oem fb_mode_clear
fastboot reboot-bootloader
After that can you try any of the fastboot flash commands using the new SBF file?

It worked!!! Oh my god thank you so much! You are a life saver!!

delete

alex94kumar said:
It worked!!! Oh my god thank you so much! You are a life saver!!
Click to expand...
Click to collapse
Glad it worked for you !! Enjoy with 4.4...

bricked, broke, something

running RUU on rooted phone gives me failure to connect thru usb. fastboot oem lock relocked my device and RUU tells me i need to be above 30% to flash, and i'm at 70%
fastboot................unlock token fails
device starts at splash screen with red text and wont continue past
restoring last rom successful, but wont boot past red text
push rom to device fastboot flash zip rom.zip just hangs (i have done this many times in past, it will say failed, too big of file and then ends up working any way.
fastboot oem rebootRUU works, but stil wont flash RUU says battery is dead and it's not
tried usb 2.0 and 3.0 with no luck been running rom that is no longer suported and the updated version that worked best has been deleted from server, so i want to go back to stock. i've tried other roms and was not happy so i just want stock back.
current, relocked boot loader, still have TWRP recovery, s-off, custom firmware, and all that works even though i'm (again) relocked boot loader, and i can't unlock it says faild when trying to flash unlock token

jpwhre said:
running RUU on rooted phone gives me failure to connect thru usb. fastboot oem lock relocked my device and RUU tells me i need to be above 30% to flash, and i'm at 70%
fastboot................unlock token fails
device starts at splash screen with red text and wont continue past
restoring last rom successful, but wont boot past red text
push rom to device fastboot flash zip rom.zip just hangs (i have done this many times in past, it will say failed, too big of file and then ends up working any way.
fastboot oem rebootRUU works, but stil wont flash RUU says battery is dead and it's not
tried usb 2.0 and 3.0 with no luck been running rom that is no longer suported and the updated version that worked best has been deleted from server, so i want to go back to stock. i've tried other roms and was not happy so i just want stock back.
current, relocked boot loader, still have TWRP recovery, s-off, custom firmware, and all that works even though i'm (again) relocked boot loader, and i can't unlock it says faild when trying to flash unlock token
Click to expand...
Click to collapse
Backup all of your data to your PC, HTC Backup or Google, then do a factory reset. Now, try to flash the stock firmware first then the RUU from this site.

majmoz said:
Backup all of your data to your PC, HTC Backup or Google, then do a factory reset. Now, try to flash the stock firmware first then the RUU from this site.
Click to expand...
Click to collapse
i can't, bootloader show locked, and splash screen shows unlocked and it doesn't go past splash screen.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
all fast boot commands work and when phone was running all adb commands worked, problem is i have a locked bootloader ( image above ) and un unlocked bootloader ( image below ) at same time

jpwhre said:
i can't, bootloader show locked, and splash screen shows unlocked and it doesn't go past splash screen.
all fast boot commands work and when phone was running all adb commands worked, problem is i have a locked bootloader ( image above ) and un unlocked bootloader ( image below ) at same time
Click to expand...
Click to collapse
The splash screen has the warning because you have a custom recovery installed not because the bootloader is unlocked. Try to flash the stock firmware with the instructions in the OP. When it flashes, the red warning will go away. Since you are in the bootloader, try to get to factory reset. It may help clear up some of your issues and allow you flash the RUU.

majmoz said:
The splash screen has the warning because you have a custom recovery installed not because the bootloader is unlocked. Try to flash the stock firmware with the instructions in the OP. When it flashes, the red warning will go away. Since you are in the bootloader, try to get to factory reset. It may help clear up some of your issues and allow you flash the RUU.
Click to expand...
Click to collapse
Nothing, i tried flashing TWRP official instead of modified one i've been running from here, i tried flashing 4.3 firmware, i tried flashing 5 firmware ( on modified version of that from OMJ ) and nothing worked
Final attempt was to bypass the htc driver installer i have and install htc sync. Phone started right up after that. Now to restore to stock ( attempt again )

Need Help Mate S Bootloop and Can't Update Any Rom

Hi friends,
i have a mate s L09 and i had 5.1.1 Lollipop on it CRR-L09C432B161 or something like that.i think it was a rom for Turkey.
i wanted to root it and installed carrera 2.8 twrp with fastboot mode but nothing changed.i could not get twrp.so i could not install supersu and i wanted to install CRR-L09C432B145 rom and my device get bootloop.
So i tried to install other roms via fastboot but nothing changed.
Then i gooogled all the net and did everything but i could't get device back.
i wanted to install twrp rtecovery but i think there is a problem and no rom or recovery got installed.
Now:
1-i don't know which rom was installed on it.CRR-L09C432B161 or something else.
2-i can not install any rom or recovery.(i did many times to extract with Huawei extract tool cust,boot,recovery,system and installed with fastboot but nothing)
3-My device's bootloader is unlocked but i don't know FRP is locked or unlocked(the pic is under)
4-Maybe FRP is locked and i can not install anything becouse of it,i do not know
5-My compuer can't load the device,all the adb drivers installed,no problem.i changed cable and sd card but same problem.
Please help me.i can not use my device.
The pics:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
]

The Fastboot picture is to small. Can´t read what´s written there but i guess your device is FRP locked since there are two red texts/lines on the bottom side.
The only thing you could try is placing the right Update.App on an SD card and do an forceupdate via Vol+/- and Power. Since you don´t know the original Build, you have to try different files until one works.

Tuerkay said:
The Fastboot picture is to small. Can´t read what´s written there but i guess your device is FRP locked since there are two red texts/lines on the bottom side.
The only thing you could try is placing the right Update.App on an SD card and do an forceupdate via Vol+/- and Power. Since you don´t know the original Build, you have to try different files until one works.
Click to expand...
Click to collapse
Hi,thanks for your reply,
i tried many times that solution.when i do volume+/ and power device get Huawei's erocovery and i press the "update with internet" it says "no wireless found".the other alternatives are "power off" and "reset".
PS:Yes,you're right in the second image,it says:
PHONE Unlocked
FRP Unlock
with red color.

If there is "PHONE Unlocked" and "FRP Unlocked" written on the Fastboot screen, you can flash a new system. Extract System.img Recovery.img boot.img and cust.img from an Update.App and flash via fastboot. To be able to do that, you should search for "Minimal ADB and Fastboot Driver" in the XDA Forum and instal that.

Tuerkay said:
If there is "PHONE Unlocked" and "FRP Unlocked" written on the Fastboot screen, you can flash a new system. Extract System.img Recovery.img boot.img and cust.img from an Update.App and flash via fastboot. To be able to do that, you should search for "Minimal ADB and Fastboot Driver" in the XDA Forum and instal that.
Click to expand...
Click to collapse
ADB drivers all installed.Phone unlocked but it says "FRP Unlock".Not FRP unlocked.i flashed many times new system. Extracted System.img Recovery.img boot.img and cust.img from an Update bu nothing changed.i think they can not installed.
i tried many different roms..B145,B321,B114.And i tried to install twrp recovery but nothing changed again.
i tried all adb command to erase local stroge but isays the command are false.
and i forget to say:my computer can not see the device.it says "device not found".i uninstall the adb drivers and install again the last driver but nothing changed.
Any other way to install rom?
Or if i have to unlock FRP can i install rom?i don't know muck more about the Huawei system.
i upload images again.

You have to use fastboot commands in fastboot Mode. ADB commands wont work. Plug in your Phone. Open device Manager on your pc. Look for "android device". Remove Driver. Unplug Phone. Install "minimal adb and fastboot". Reboot pc. Plug j. Phone. Pc should find Phone now.

Minimal Adb and fastboot drivers also installed.My device shown like this at the device manager.
And i wrote wrong i tries always fastboot commands,sorry.

altanis said:
Minimal Adb and fastboot drivers also installed.My device shown like this at the device manager.
And i wrote wrong i tries always fastboot commands,sorry.
Click to expand...
Click to collapse
contact me, i can solve your problem

mutahharbashir said:
contact me, i can solve your problem
Click to expand...
Click to collapse
Thank you for your reply @mutahharbashir,
but i did not solve the problem and sold my phone.

Unbrick Xiaomi Mi A2 [jasemine]

Hello,
i have bought a new Xiaomi Mi A2 and thought it would be a really nice idea to flash magisk on it. First everything was alright. I unlocked my bootloader in fastboot with "fastboot oem unlock" and flashed twrp on the b partition. Unfortunately my device broke (don't know why... maybe the unofficial twrp with some bugs or...). So now i have a really big problem, because my twrp recovery is missing as well as the stock recovery. When i try to switch on the mobile i am stuck in bootloop (with the mi logo). Not even the bootloader warning is shown.
Fastboot mode is working but not really nice. Not even the mitu appears, no the display is black (or doesn't show anything.. The device's display is on).
My Mi A2 is recognized by the computer so I considered to flash the stock rom with fastboot.
I thought it would work, but in the mi flash programm i got the erorr: flash devcfg_a error.
Now i can't switch my mobile off, because when I'm holding the power button, it restarts and restarts and restarts...
I know i am stupid and maybe have done something wrong, but i would be soooo happy to get some help
Thank you so much!

Fastboot flashing unlock_critical
(It will wipe /data)
then flash with mi flash
But before doing that, try just flashing stock boot
Fastboot flash boot_a boot.img
Or boot_b if that's your active slot

Nebrassy said:
Fastboot flashing unlock_critical
(It will wipe /data)
then flash with mi flash
But before doing that, try just flashing stock boot
Fastboot flash boot_a boot.img
Or boot_b if that's your active slot
Click to expand...
Click to collapse
Thank you very much for your answer.
Unfortunately i have wiped everything in twrp before (when it worked) so there's nothing stored on the device.
When i type in critical unlock only a big list of commands appears which can be used.... ?

MardukPVP said:
Thank you very much for your answer.
Unfortunately i have wiped everything in twrp before (when it worked) so there's nothing stored on the device.
When i type in critical unlock only a big list of commands appears which can be used.... ?
Click to expand...
Click to collapse
what's the exact command you used?

Nebrassy said:
what's the exact command you used?
Click to expand...
Click to collapse
In minimal ADB and Fastboot I used: fastboot flashing unlock_critical
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

MardukPVP said:
In minimal ADB and Fastboot I used: fastboot flashing unlock_critical
Click to expand...
Click to collapse
Don't use minimal adb, use this https://developer.android.com/studio/releases/platform-tools

Okay, i've got no words. You saved my life. It worked. Thank you sooo much !!!

Not receiving updates
I need help i recently flashed fastboot rom on mi A2 Oct patch firmware.I can't receive any Ota Updates,How to get in phone on original state? With working online updates in settings PLEASE HELP!!:crying::crying:

jdivya524 said:
I need help i recently flashed fastboot rom on mi A2 Oct patch firmware.I can't receive any Ota Updates,How to get in phone on original state? With working online updates in settings PLEASE HELP!!:crying::crying:
Click to expand...
Click to collapse
So you have flashed this rom https://en.miui.com/download-353.html ?

Nebrassy said:
Fastboot flashing unlock_critical
(It will wipe /data)
then flash with mi flash
But before doing that, try just flashing stock boot
Fastboot flash boot_a boot.img
I promised I would create an account here just to thank you if your method worked!
After doing something dumb (I typed some wrong commands I think) my A2 got into the infinite reboot, never got out of the android logo, I tried everything and literally thought I lost my phone for good ;n;
I downloaded "jasmine_global_images_V10.0.2.0.PDIMIFJ_20181206.0000.00_9.0_02b8deeb6d.tar" and flashed that on miflash and watched my phone come back from the dead like frankestein or something. He's doing great and is in top shape, thanks to your advice! THANK YOU VERY MUCH! Hope you have a wonderful 2019!
Click to expand...
Click to collapse

MardukPVP said:
Okay, i've got no words. You saved my life. It worked. Thank you sooo much !!!
Click to expand...
Click to collapse
Hey Did Your smartphone works fine I mean did you get every Updates from Stock

error
Nebrassy said:
Fastboot flashing unlock_critical
(It will wipe /data)
then flash with mi flash
But before doing that, try just flashing stock boot
Fastboot flash boot_a boot.img
Or boot_b if that's your active slot
Click to expand...
Click to collapse
When i try it shows the error remote error flashing partition , how to solve that help please my email is [email protected] , replay there if possible thank you

[email protected] said:
When i try it shows the error remote error flashing partition , how to solve that help please my email is [email protected] , replay there if possible thank you
Click to expand...
Click to collapse
Try flashing through edl mode

I think I bricked my mi a2 please help me.
MardukPVP said:
Thank you very much for your answer.
Unfortunately i have wiped everything in twrp before (when it worked) so there's nothing stored on the device.
When i type in critical unlock only a big list of commands appears which can be used....
Click to expand...
Click to collapse
I have a mi a2 and it's stuck on Android logo screen. It has an unlocked bootloader and maybe it's rooted too. While I thought I rooted it.. It went into bootlooping.. Only fastboot and android logo can be accessed. I tried flashing it with stock rom but mi flash tool goes like 3500+ sec. Please tell how to fix this.

same issu
okay i hav the same problem, can't fix it
whenever i try to use any command in cmd during the device is in fastboot mode, my phone screen go to the black, and it says in a liitle, "press any key to shutdown"
is there any solution? it will me life saving.

anikapproe said:
...whenever i try to use any command in cmd during the device is in fastboot mode, my phone screen go to the black, and it says in a liitle, "press any key to shutdown" is there any solution?
Click to expand...
Click to collapse
I have the same issue in PC I'm writing this from (in USB3.1 Gen2 and Gen 1 ports, and even in USB 2.0 ports), but have no problems in 2 other PCs I currently have access to.
For non-universal solution with my current PC please see more info in my answer in neighbouring thread: https://forum.xda-developers.com/showpost.php?p=81693759&postcount=28.

Question Stuck in FastBoot Mode loop , recovery and rescue mode give boot failure, bricked?

Hi!
I got this new Pixel 7 2 weeks ago, yesterday the battery went completly discharged and now the phone starts into Fastboot mode, with the Enter Reason being boot failure. Recovery mode and rescue mode both fail to load, and just send me back to the Fastboot Mode. I alredy tried a bunch of stuff to fix it, but the phone its still OEM lock so flashing via the Google flash tool its imposible, does anyone has any idea of what can i do to save it?

Did you try this too?
https://pixelrepair.withgoogle.com/carrier_selection

t-ryder said:
Did you try this too?
https://pixelrepair.withgoogle.com/carrier_selection
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
yes, Rescue Mode fails to load, so it gives me Unable to connect the Phone

There's fastboot mode and fastbootD I guess. You can enter fastbootD from fastboot. Maybe I confuse stuff tho, since lately I got a lot of chaos in my head. DYOR.
Have you tried Pixel Flasher?
https://github.com/badabing2005/PixelFlasher/releases

t-ryder said:
There's fastboot mode and fastbootD I guess. You can enter fastbootD from fastboot. Maybe I confuse stuff tho, since lately I got a lot of chaos in my head. DYOR.
Have you tried Pixel Flasher?
https://github.com/badabing2005/PixelFlasher/releases
Click to expand...
Click to collapse
No, i am going to give it a go and update on results

t-ryder said:
There's fastboot mode and fastbootD I guess. You can enter fastbootD from fastboot. Maybe I confuse stuff tho, since lately I got a lot of chaos in my head. DYOR.
Have you tried Pixel Flasher?
https://github.com/badabing2005/PixelFlasher/releases
Click to expand...
Click to collapse
It failed, it gives me "Bootloader is locked, can't flash." and trying to unluck the bootloader with the fastboot commands gives me FAILED (remote: 'flashing unlock is not allowed')

And get into fastbootd and sideload a full OTA somehow?
https://developers.google.com/android/ota?hl=en
Or is adb disabled?

t-ryder said:
And get into fastbootd and sideload a full OTA somehow?
https://developers.google.com/android/ota?hl=en
Or is adb disabled?
Click to expand...
Click to collapse
adb its disabled and entering recovery mode also fails, the phone its pretty much new, so i didn't have time do much with it.

I've seen this before where people's phones have "died" when letting the battery run out. I haven't seen any successful methods to recover (not to say there isn't).
Since you're bootloader is locked and you don't have OEM Unlocking enabled you won't be able to flash anything via fastboot. If OEM Unlocking were enabled you would be able to use Android Flash Tool as that will unlock your bootloader during the process as long as you have OEM Unlocking enabled.
Maybe try to see if Pixel Flasher can get you into recovery mode to see if you can sideload an OTA, although given the circumstances I'm doubtful it will. By the way, you don't need USB Debugging enabled to sideload an OTA. Being in sideload mode enables a very limited set of ADB commands on Pixels, including adb sideload <imagename>.zip.
Good luck...

Lughnasadh said:
I've seen this before where people's phones have "died" when letting the battery run out. I haven't seen any successful methods to recover (not to say there isn't).
Since you're bootloader is locked and you don't have OEM Unlocking enabled you won't be able to flash anything via fastboot. If OEM Unlocking were enabled you would be able to use Android Flash Tool as that will unlock your bootloader during the process as long as you have OEM Unlocking enabled.
Maybe try to see if Pixel Flasher can get you into recovery mode to see if you can sideload an OTA, although given the circumstances I'm doubtful it will. By the way, you don't need USB Debugging enabled to sideload an OTA. Being in sideload mode enables a very limited set of ADB commands on Pixels, including adb sideload <imagename>.zip.
Good luck...
Click to expand...
Click to collapse
Even trying to get into recovery mode with Pixel Flasher fails.. looks like my only option its asking for warranty and i wanted to avoid that.

Have you tried issuing the command fastboot getvar all to see what slot you're on and what the status of your slots are? Maybe switching slots could get you a boot.

41rw4lk said:
Have you tried issuing the command fastboot getvar all to see what slot you're on and what the status of your slots are? Maybe switching slots could get you a boot.
Click to expand...
Click to collapse
Unfortunately their bootloader is locked so they won't be able to switch slots via fastboot commands. Even if they were able to switch slots they would then have to flash the OS to that slot before being able to boot into that slot since you can only boot into the slot where the OS was last flashed in this circumstance.

I can't get over the fact that you can't just flash an official image on a locked bootloader. I used to be a Moto fan and that was always the good thing about them, as long as it was officially signed, locked or not you could flash the same or updated firmware. Plus if it was qualcomm, when you bricked it would go into edl mode and you could blankflash your way back.
Yet a Google device, who also develops android, you're up a creek unless you unlock your bootloader.