Hard brick after official OTA update from 4.4.4 to 5.1 - Moto G Q&A, Help & Troubleshooting

I was running the Brazillian Retail 4.4.4 stock ROM and decided to update to 5.1 normally OTA. The phone was previously downgraded to 4.4.4 from 5.1 normally. After the software update, the screen was black and my pc recognized it as QHSUSB_BULK. I followed the normal un-hardbrick instructions using the lollipop qboot tool with the blankflash command, and it restarted into fastboot as expected. But now, I cannot flash the partition or motoboot of any version of the stock builds, including 4.4.4, 5.0.2 and 5.1. I really need this phone fixed, so I need some help ASAP if I can. Also, the phone was unlocked before the brick.
Here's a screenshot of the phone on fastboot mode.
{
"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"
}
excuse the poor quality
Moto G XT1033 (Dual SIM)
EDIT: I fixed it by using a ROM from this thread http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795 :good:

Is the phone recognised by PC in fastboot mode ?
Power it on in fastboot mode : Hold Power et Volume- during 3-4 secondes and release.

djibe89 said:
Is the phone recognised by PC in fastboot mode ?
Power it on in fastboot mode : Hold Power et Volume- during 3-4 secondes and release.
Click to expand...
Click to collapse
It is recognized normally by the PC, but I cannot flash a partition table (usually called gpt.bin in stock ROMs) with the error message "version downgraded for primary_gpt".

I just managed to fix it by using a ROM from this thread http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Thanks for the help anyway :good:

foxpersonman said:
I was running the Brazillian Retail 4.4.4 stock ROM and decided to update to 5.1 normally OTA. The phone was previously downgraded to 4.4.4 from 5.1 normally. After the software update, the screen was black and my pc recognized it as QHSUSB_BULK. I followed the normal un-hardbrick instructions using the lollipop qboot tool with the blankflash command, and it restarted into fastboot as expected. But now, I cannot flash the partition or motoboot of any version of the stock builds, including 4.4.4, 5.0.2 and 5.1. I really need this phone fixed, so I need some help ASAP if I can. Also, the phone was unlocked before the brick.
Click to expand...
Click to collapse
I have a moto g (XT1031), which also got hard bricked by the same method (stupid of me....). Unlike OP, my phone is not restarting with the blankflash command. It says, "could not open device" and the screen stays blank. I tried holding down the power button for 2-3 minutes........ Nothing. Any suggestions/help appreciated. Thanks.

greenlantern2014 said:
I have a moto g (XT1031), which also got hard bricked by the same method (stupid of me....). Unlike OP, my phone is not restarting with the blankflash command. It says, "could not open device" and the screen stays blank. I tried holding down the power button for 2-3 minutes........ Nothing. Any suggestions/help appreciated. Thanks.
Click to expand...
Click to collapse
Try using another driver. I don't know how effective that will be, but it could work :fingers-crossed:
I won't share the driver I used because I'm afraid ill end up sharing malware, because the website I got it from was kinda sketchy.
Try googling for the QHSUSB_BULK driver.
Uninstalling the driver is very simple:
Go to the Start menu and type in Device Manager, and open it.
Right click on the "QUALCOMM HS-USB QDLOADER 9008" device (probably under "Ports (COM & LPT)") and click Uninstall.
Tick the "Delete the driver software for this device." checkbox and click OK.
At this point the PC should recognize the device as QHSUSB_BULK again.
Now install the new one

Related

Blue Screen? Wont boot

T-mobile Prism II (U8686)
Android 4.1.1 (rooted)
Custom Recovery CWM 6
I just setup swap with swappy2 following this guide.
I just rebooted and now my phone shows the T-Mobile logo and then directly to BLUE SCREEN
Turning on with no buttons pressed / pwr & v+ / pwr v-
{
"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"
}
Turning on with both v+/v- pressed
adb/fastboot wont recognize device
any ideas on what is wrong i hope its not bricked?
Diehardshorty said:
T-mobile Prism II (U8686)
Android 4.1.1 (rooted)
Custom Recovery CWM 6
I just setup swap with swappy2 following this guide.
I just rebooted and now my phone shows the T-Mobile logo and then directly to BLUE SCREEN
adb/fastboot wont recognize device
any ideas on what is wrong i hope its not bricked?
Click to expand...
Click to collapse
Try to again flash, and make sure scatter file is correct according to your device.
I have no access to recovery menu, just getting this blue screen each time it powers up.
Diehardshorty said:
T-mobile Prism II (U8686)
Android 4.1.1 (rooted)
Custom Recovery CWM 6
I just setup swap with swappy2 following this guide.
I just rebooted and now my phone shows the T-Mobile logo and then directly to BLUE SCREEN
adb/fastboot wont recognize device
any ideas on what is wrong i hope its not bricked?
Click to expand...
Click to collapse
To use ADB you also need the device Drivers installed.
christoph.gasser said:
To use ADB you also need the device Drivers installed.
Click to expand...
Click to collapse
Did you even read the thread? Go spam else where
Diehardshorty said:
I know how adb and fastboot work the drivers are installed.
Did you even read the thread?
Click to expand...
Click to collapse
Yes I read your thread.
But you don't only need the ADB drivers you also need the device specified drivers.
For example for my HTC One:
I need: the HTC One drivers
the ADB drivers
I had the same problem some time ago.
christoph.gasser said:
Yes I read your thread.
But you don't only need the ADB drivers you also need the device specified drivers.
For example for my HTC One:
I need: the HTC One drivers
the ADB drivers
I had the same problem some time ago.
Click to expand...
Click to collapse
Well the phone came with an autorun cd that mounted with it when you connected it to the computer. It had adb drivers and the device drivers, i installed them both and used the fastboot and adb to flash CWM recovery before this happened to get it rooted. Was working great before i tried to get swap working with the guide i followed above.
Im thinking its bricked possibly bcause this thread. My devices is doing the same thing he is describing.
Just a few images to show you what is happening
Turning on with no buttons pressed / pwr & v+ / pwr v-
Turning on with both v+/v- pressed
bump
I have the same problem and have not found a solution

Stuck at LG logo

i booted into recovery, made a full backup, wiped everything but internal storage, flashed to lollipop 5.1 but decided to go back to my backup. so rebooted into recovery again and restored the backup. everything seemed to work correctly but after rebooting phoned stuck at lg logo. so i rebooted into recovery by holding "volume - and power" and the factory data reset screen came up and i confirmed that i wanted to reset phone, expecting it to boot into twrp but it went to the the black screen with the android on his side (or something like that), which i assume it did do a factory reset.
so still stuck at lg logo with no custom recovery anymore apparently. among other things, i used srktool to nuke download mode, so phone immediatly goes into fastboot mode. now im trying to use the "fix fastboot mode" but it just sits there saying waiting for device even though i have phone connected to computer in fastboot mode.
is it likely that if/when it did the factory reset, that would disable the usb debugging setting and that's why srktool just shows "waiting for device"?
im betting that your OS got corrupted. You can try to reflash your ROM, or you might be relegated to going into download mode and reflashing the OS back to stock. I have a link for the LG recovery tool and the stock 4.4.2. All youll need from there is towel root and the recovery i have in a separate post
hi i have same problem con you explein how can i do this
hi i have same problem con you explein how can i do this
l.musaj said:
hi i have same problem con you explein how can i do this
Click to expand...
Click to collapse
try this
http://forum.xda-developers.com/att-g2/development/twrp-5-0-d800-g2s-t3247754
youdoofus said:
try this
http://forum.xda-developers.com/att-g2/development/twrp-5-0-d800-g2s-t3247754
Click to expand...
Click to collapse
thank you but my lg d800 dosnt entry in download mode it stuck
{
"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"
}
he stuck here in ports dosnt show nothink but in USB controllers its unknown device
l.musaj said:
thank you but my lg d800 dosnt entry in download mode it stuck
he stuck here in ports dosnt show nothink but in USB controllers its unknown device
Click to expand...
Click to collapse
uninstall the usb driver and let windows find the correct driver for it and follow the stuff in the link i provided after the computer recognizes the device. If that doesnt work do the stuff in the link on another computer or try a different cable. If you can get to download mode, youre likely ok. The issue is either the computer or the cable, not the phone.

Moto One Macro - Bricked Device

Hello folks, please help me ASAP, as I have no other devices in me and both my private and work related things are associated with my phone so...
I was doing this and since im noob I was going step by step so i dont mess something and yet that happened. you can read from there what I was doing and what happened.
Basically I tried to flash firmware by executing line by line of commands and now my phone is dark (nothing can be done with physically clicking the buttons). Its connected with the PC so sometimes i can hear that USB sounds you know.. Anyway, can you please assist me how to proceed and go back to normal ?
Open device manager and look for Qualcomm
if you see that your Device is in EDL Mode.
Try this tool
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
sd_shadow
Nope, nothing with qualcomm in my device manager.
And after running "bank-flash" my device now rebooted to fastboot.
KomitaMKD said:
sd_shadow
Nope, nothing with qualcomm in my device manager.
And after running "bank-flash" my device now rebooted to fastboot.
Click to expand...
Click to collapse
ok, I'm not sure what the flashing problem is.
rerun
Code:
fastboot getvar all
sd_shadow said:
ok, I'm not sure what the flashing problem is.
rerun
Code:
fastboot getvar all
Click to expand...
Click to collapse
I pressed the button to start the mobile and now its stuck/taking too long on the motorola logo.
running the bank flash file in this state gives me this now
Code:
working path= C:\Users\trajk\Downloads\rescuetool_JimnyPlus_64
Loading Da...
Loading Da OK!
Loading Scatter file...
ChecksumLevel = 2!
Loading Scatter file success!
Loading AuthFile...
Loading Auth OK!
Waiting for com port cable insert...
Please insert comport...
KomitaMKD said:
I pressed the button to start the mobile and now its stuck/taking too long on the motorola logo.
running the bank flash file in this state gives me this now
Code:
working path= C:\Users\trajk\Downloads\rescuetool_JimnyPlus_64
Loading Da...
Loading Da OK!
Loading Scatter file...
ChecksumLevel = 2!
Loading Scatter file success!
Loading AuthFile...
Loading Auth OK!
Waiting for com port cable insert...
Please insert comport...
Click to expand...
Click to collapse
Blankflash only works with EDL Mode (black screen)
10 minutes later im still stuck on the Motorola - Powered by Android logo
So, how do I proceed now?
Try this guide, my friend: https://forum.xda-developers.com/t/...your-bricked-motorola-moto-one-macro.4145191/
VD171 said:
Try this guide, my friend: https://forum.xda-developers.com/t/...your-bricked-motorola-moto-one-macro.4145191/
Click to expand...
Click to collapse
Im not sure how to use this
Official Stock Rom by LOLINET: https://mirrors.lolinet.com/firmware/moto/lima/official
{
"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"
}
KomitaMKD said:
So, how do I proceed now?
Click to expand...
Click to collapse
You need to reboot to fastboot mode, unplug USB, and hold the volume button and power, till you see the fastboot screen.
You have
Code:
ro.carrier: reteu
sd_shadow said:
You have
Code:
ro.carrier: reteu
Click to expand...
Click to collapse
Okay that did the work now my phone is off - black after i pressed the buttons...
Now which one should i download? Should i use the Android 10 one or the 9 one you mentoined previously (if its the same). btw before i do anything i had android 9 running with the november patch
I tried that Android 10 and this is what i did.
Extracted Mediatek and the firmware in same folder, did the cmd thing from the xml through the spanish web site, ran the bat file and nothing happened.
Now ill be trying with the android 9 version
Okay guys im not able to successfully run the flashfile.bat
I tried with the (Optional) Automatic BAT file made by Eufracio López and it did the trick!!! I was able to flash Android 10!
KomitaMKD said:
I tried with the (Optional) Automatic BAT file made by Eufracio López and it did the trick!!! I was able to flash Android 10!
Click to expand...
Click to collapse
Nice job, my friend.
I would like to thank you all who spared some of your
VD171 said:
Nice job, my friend.
Click to expand...
Click to collapse
Thanks to you and @sd_shadow , I really appreciate your quick assistance
KomitaMKD said:
Hello folks, please help me ASAP, as I have no other devices in me and both my private and work related things are associated with my phone so...
I was doing this and since im noob I was going step by step so i dont mess something and yet that happened. you can read from there what I was doing and what happened.
Basically I tried to flash firmware by executing line by line of commands and now my phone is dark (nothing can be done with physically clicking the buttons). Its connected with the PC so sometimes i can hear that USB sounds you know.. Anyway, can you please assist me how to proceed and go back to normal ?
Click to expand...
Click to collapse
Hi @KomitaMKD this is vignesh , i am also using Moto One Macro device , Lastweek i have thought to flash my mobile due to some reason first time my device became brick... I am not ble to do anything its come startup failure ! Message .... I felt really bad ... Then almost i tried 8 hrs continuously for recovering my phone.. finally i found it. I recovered my mobile. Below i will give a link just go through it , that will help your mobile to become normal.
[RECOVER][UNBRICK][BLANKFLASH] How unbrick your bricked Motorola Moto One Macro
This script was made by Eufracio López (yehison). Thank you very much ! 1. First, you have to download required contents: Minimal ADB and Fastboot Tool: https://androidmtk.com/download-minimal-adb-and-fastboot-tool Motorola Device Manager...
forum.xda-developers.com

Realme 5i phone dead but can be detected in Windows 10

So i was trying to install twrp and it failed and the phone displayed this "the current image(boot/recovery) have been destroyed" and keeps turning on and off. Later it restarts and got stuck in the logo "Realme with powered by Android". I don't know what happened. I can't press volume up and power button. So I waited till it drains its battery. So I tried charging it back and it shows charging red. Then when it reaches to a point where it can turn on, It got stuck in the charging white logo thingy and it wont let me do anything.
But after a few tries it finally wont turn on.
I tried connecting it to the computer and somehow it shows an unknown driver.
QUSB_BULK_CID:0411_SN:B3336417
{
"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"
}
I have no idea what that is but I know that "B3336417" is the ID of the phone.
Can anyone help me how to fix this phone?
Assuming you've correctly installed ADB driver on Windows 10 then if USB Debugging didn't get enabled on phone you'll NOT see the phone in Windows' Device Manager under Portable Devices - where it should be shown.
Try installing MTK Drivers, it should fix the problem
EDIT: Then flash Stock ROM using SP Flash Tool V5
jwoegerbauer said:
Assuming you've correctly installed ADB driver on Windows 10 then if USB Debugging didn't get enabled on phone you'll NOT see the phone in Windows' Device Manager under Portable Devices - where it should be shown.
Click to expand...
Click to collapse
I pressed volume up + volume down + power button and it takes me to fastboot mode. Do you know how to restore back the phone? where can I find the stock rom for realme 5i?
NoveNoki said:
Try installing MTK Drivers, it should fix the problem
EDIT: Then flash Stock ROM using SP Flash Tool V5
Click to expand...
Click to collapse
I pressed volume up + volume down + power button and it takes me to fastboot mode. Do you know how to restore back the phone? where can I find the stock rom for realme 5i?
Grim Face said:
I pressed volume up + volume down + power button and it takes me to fastboot mode. Do you know how to restore back the phone? where can I find the stock rom for realme 5i?
Click to expand...
Click to collapse
Here are official ROM files from all Realme phones: https://www.realme.com/eu/support/software-update just search for your phone and you should find it, tho you will need a computer so you can flash the files
EDIT: Do you know if your device uses MediaTek chip?
NoveNoki said:
Here are official ROM files from all Realme phones: https://www.realme.com/eu/support/software-update just search for your phone and you should find it, tho you will need a computer so you can flash the files
EDIT: Do you know if your device uses MediaTek chip?
Click to expand...
Click to collapse
My phone uses Snapdragon but I finally have OrangeFox recovery
NoveNoki said:
Here are official ROM files from all Realme phones: https://www.realme.com/eu/support/software-update just search for your phone and you should find it, tho you will need a computer so you can flash the files
EDIT: Do you know if your device uses MediaTek chip?
Click to expand...
Click to collapse
Can I flash my rom to the Orange Fox Recovery mode? It seems that my OS is gone.
Grim Face said:
Can I flash my rom to the Orange Fox Recovery mode? It seems that my OS is gone.
Click to expand...
Click to collapse
I think you should be able to, i am not too sure. But i whould recommend you to flash it manually using the fastboot mode, tho if you can try flashing it from the recovery

Nokia 1.4 TA-1322 Help

Hello everyone, I need some help.
On november 2021 I purchased Nokia 1.4 and that day when alarm was ringing my phone screen frozen/stopped. Screen sensor and the buttons stopped was not responding. I googled immediately and found the way to turn off forzen Nokia 1.4 by pressing Wolume up + Power off buttons same time (Source: https://www.nokia.com/phones/en_int...-reboot-my-smartphone-when-its-not-responding ).
When my phone turned on again I was happy till the next restarting of my phone. My nokia get Stucked in a Reboot Loop.
Screen lights and when Android GO Logo appears it turns off again and again.
I tried to flash my phone using QFIL Tool but there was unsolved issue of Android ADB Interface driver. The QFIL Tool couldn't detected my device. Mybe it needed different keys combination when connectiong it to PC to boot.
QFIL Tool source: https://androidmtk.com/download-qualcomm-flash-image-loader-qfil
Than I unlocked bootloader using this command:
Code:
fastboot oem unlock-go
I thought it was boot or recovery fail and by the reason I downloaded the firmware from alien9firmware
Source: https://alien9firmware.com/index.php?a=downloads&b=file&id=1325
Because QFIL Tool did not work I flashed boot and recovery via ADB. I moved these two .img files to disk C and ran the following commands
Code:
fastboot devices
fastboot reboot bootloader
fastboot flash recovery c:\recovery.img
fastboot flash boot c:\boot.img
fastboot reboot bootloader
fastboot erase cache
fastboot reboot
Disconnect device
You guess what do you think guys happen
My nokia was still stucked in reboot Loop.
Than I googled smartphones with same Core Qualcome QM 215 and downloaded Nokia 8 and Nokia 6.2 TWRPs from twrp official website.
Source: https://twrp.me/Devices/Nokia/
ADB thrown me an error when I tried to flash Nokia 8 TWRP. "The file is too large and blablabla..."
Then I tried to flashed twrp-3.6.0_9-0-SLD_sprout(nokia6.2) with no errors.
I have never seen anything like that. When I press to "Power button + Volume down" buttons my phone shows the stock recovery again which has no matter.
Then I gooled so many times I and I made a decision that every smartphone with Qualcomm QM215 core has absolutely same bugs.
There are smartphones with this terrible Processor:
Smartphones with Qualcomm Snapdragon 215 processor
List of smartphones that works with Qualcomm Snapdragon 215 processor inside.
www.kimovil.com
Than I found this video. In this video he used dryer and it worked. Unfortunately I have not dryer and... It may works on our devices too, Who knows...
Than someone told me to use MiFlash tool to boot my device. I faced another problem the firmware backup was missing the boot_lock.bat file. I had to download Xiaomi Kenzo global firmware to copy and modify the .bat files to my firmware backup. That trying became my night mare. I accidently erased Bootloader.
Today I was searching how connect How to a connect phone with erased bootloader to pc and I found this:
[guide] repair hard bricked devices with deleted bootloader (sboot)
I'm writing this in android development section because this is only section for both models, i hope this is not a problem. Also i want to say thanks to sataccount from gsmhosting, he found working map at the end. This guide is for hard bricked...
forum.xda-developers.com
Than I connected my phone to pc via usb and opened Device manager. There appeared QHSUSB_BULK device missing driver.
Then I found the driver here: https://fixfirmware.com/qhsusb-bulk-driver/
At least I managed to connect my device to pc again. And now QFIL Tool detects my phone.
Problems never ends. I downloaded 5 firmwares from different websites and the emmc filefouse prog_emmc_firehose *** ddr.mbn and Rawprogram .xml files missing in all of them.
Do someone know where can I fount the emmc Firehose and Rawprogram .xml files?
Oleg69 said:
Problems never ends. I downloaded 5 firmwares from different websites and the emmc filefouse prog_emmc_firehose *** ddr.mbn and Rawprogram .xml files missing in all of them.
Do someone know where can I fount the emmc Firehose and Rawprogram .xml files?
Click to expand...
Click to collapse
Try it
optimusodd said:
Try it
Click to expand...
Click to collapse
I have downloaded the firmware but there is not prog_emmc_firehose.mbn in the archive
{
"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"
}
Oleg69 said:
On november 2021 I purchased Nokia 1.4 and that day when alarm was ringing my phone screen frozen/stopped. Screen sensor and the buttons stopped was not responding. I googled immediately and found the way to turn off forzen Nokia 1.4 by pressing Wolume up + Power off buttons same time
Click to expand...
Click to collapse
When it's still under warranty ,why didn't you claim it ?
optimusodd said:
When it's still under warranty ,why didn't you claim it ?
Click to expand...
Click to collapse
It was gifted to me from abroad. You know...
S
Oleg69 said:
It was gifted to me from abroad. You know...O
Click to expand...
Click to collapse
So what was your end result because I'm currently in bootloop with an unlocked bootloader as well but not having much luck with many of the same avenues you spoke of.. anyone?
Absolutely no luck, you gotta take your phone to the service center or buy a new one as I did (another brand)
Absolutely not.. I refuse. If it's an android, there's a way. Thank God this is simply one of 8 phones I've currently got
Does unlocking the bootloader of this device put the device in boot loop. I want to unlock the bootloader coz I want to install custom ROM. Anyone tell me how to unlock the bootloader of this device without putting the device in boot loop.

Categories

Resources