Hi, my BQ Aquaris U2 Lite won't boot, I unlocked its bootloader and when I restart it, it is stuck at the next screen:
Your device software can't be checked for corruption. Please lock the bootloader.
If no key pressed:
Your device will boot in 5 seconds
But nothing happens, it stays there.
Help please, thank you.
@help38
The first time that an Android device boots up, the bootloader ( the Android counterpart to Windows BIOS/UEFI ) starts running. It is basically a software program that contains a list of OS instructions to ensure the smooth functioning of the device. Once this bootloader is unlocked, the user can manually change what ROM image was set as default by the OEM, and customize the device according to its liking.
Simply unlocking the bootloader does NOTHING than the Android OS now is waiting for instruction what ROM to load and run
jwoegerbauer said:
@help38
The first time that an Android device boots up, the bootloader ( the Android counterpart to Windows BIOS/UEFI ) starts running. It is basically a software program that contains a list of OS instructions to ensure the smooth functioning of the device. Once this bootloader is unlocked, the user can manually change what ROM image was set as default by the OEM, and customize the device according to its liking.
Simply unlocking the bootloader does NOTHING than the Android OS now is waiting for instruction what ROM to load and run
Click to expand...
Click to collapse
Hi, thank you, but my phone is stuck at that screen and nothing happens, I can't boot Android, do you know what is happening?
I unlocked the bootloader with BQ Firmware Flash Tool, because the phone only loaded Android Recovery, and didn't boot up the OS.
I only want to recover my files and photos
Thank you again.
@help38
I think you've to flash a Custom ROM. Note that's only possible if USB debugging got enabled on phone before unlocking the bootloader took place.
jwoegerbauer said:
@help38
I think you've to flash a Custom ROM. Note that's only possible if USB debugging got enabled on phone before unlocking the bootloader took place.
Click to expand...
Click to collapse
How can I do that?
I didn't have USB debugging enabled, aren't there any other ways to recover my files?
Thank you.
help38 said:
How can I do that?
I didn't have USB debugging enabled, aren't there any other ways to recover my files?
Thank you.
Click to expand...
Click to collapse
No other methods, AFAIK
Even doing a Factory Reset doesn't relock the bootloader.
BTW: The 1st thing of all things an Android user should do is to enable USB debugging on his phone: that makes it all easier.
jwoegerbauer said:
No other methods, AFAIK
Even doing a Factory Reset doesn't relock the bootloader.
BTW: The 1st thing of all things an Android user should do is to enable USB debugging on his phone: that makes it all easier.
Click to expand...
Click to collapse
, thank you, but, do you know if there is someone who could recover the files by paying him?
I really want those files
help38 said:
, thank you, but, do you know if there is someone who could recover the files by paying him?
I really want those files
Click to expand...
Click to collapse
Repair service?
jwoegerbauer said:
Repair service?
Click to expand...
Click to collapse
I don't think they could, but I will try, thanks.
jwoegerbauer said:
Repair service?
Click to expand...
Click to collapse
They told me that they can't...
Do you know any other place to recover my photos?
Thank you again.
At least is there a way to unbrick the phone?
Thanks.
Help please
Related
Hello Guys~i really need some help~please~I'm using Sony Ericsson X10~
I do the bootloader unlock sim~all fine...~downgrade...with flash tool~
After that~downgrade success lol~and i open the qsd8250_semc to unlock sim~
The system will just start if you press any key but after i do that~
i forgot to close my flashtool~damm~==~
and i close my qsd8250_semc.cmd 1st then i close flashtool~i think it crash already~
after that the phone automatic start up~i don care about it and i take out the battery and put in again~then start from the step qsd8250_semc.
i open the qsd8250_semc and all success killing...etc~
but when i need to upgrade back the karnel~i got a big problem~
the flash tool say "USB debugging"are off and wan to start up the phone and go to enable it~
but i cannot start my phone~just stack at the loading screen with the word~(Sony Ericsson)~i waiting about 1hours also cannot get in~i tried to wait it~and i try to do the upgrade karnel process again~
the flash tool is run about 80%~i think it success but it say again need to on the "USB debugging"and aborted~
Damm~now when i start up my phone~after the word (Sony Ericsson)come out~and then it will display a green background and got a big (!) symbol~
Someone can help me to fix this problem please~thx alot~Guys~
Some One Please Help~
waikhin520 said:
Some One Please Help~
Click to expand...
Click to collapse
Lol. Ok, what you've manage to do was successfully brick you phone. No worries, this is an easy fix.
1. Download a stock 2.3.3 SE ROM.
2. Put .ftf file into the firmware folder of the flashtool (make sure its the latest version flashtool.)
3. Follow the flashtool's instructions.
4. After successfully flashing the stock ROM, Keep the flashtool open. Unplug the device and boot the device. Enable debugging and unknown sources.
5.Plug in phone (phone should still be on), flashtool will recognize the device seconds after. Then root.
6. After successfully rooting the device, repeat unlocking methods.
PS: The wonderful thing about our devices (x10) is that you can never break your phone by flashing too many times or bricking the device. Never. The only absolute way to break your phone is to damage the USB port. So be gentle with that part of the phone.
Mr.Quipster said:
Lol. Ok, what you've manage to do was successfully brick you phone. No worries, this is an easy fix.
1. Download a stock 2.3.3 SE ROM.
2. Put .ftf file into the firmware folder of the flashtool (make sure its the latest version flashtool.)
3. Follow the flashtool's instructions.
4. After successfully flashing the stock ROM, Keep the flashtool open. Unplug the device and boot the device. Enable debugging and unknown sources.
5.Plug in phone (phone should still be on), flashtool will recognize the device seconds after. Then root.
6. After successfully rooting the device, repeat unlocking methods.
PS: The wonderful thing about our devices (x10) is that you can never break your phone by flashing too many times or bricking the device. Never. The only absolute way to break your phone is to damage the USB port. So be gentle with that part of the phone.
Click to expand...
Click to collapse
It's not true that you can't brick it. Once you have unlocked the bootloader there's a chance to brick it (One or two devs have done it before).
aR_ChRiS said:
It's not true that you can't brick it. Once you have unlocked the bootloader there's a chance to brick it (One or two devs have done it before).
Click to expand...
Click to collapse
If you're talking about "bricking" the device then of course there is always a chance of bricking. Whether it be on a locked or unlocked bootloader. I was talking about permanently breaking the device, meaning it is unable to fix or repair.
Mr.Quipster said:
If you're talking about "bricking" the device then of course there is always a chance of bricking. Whether it be on a locked or unlocked bootloader. I was talking about permanently breaking the device, meaning it is unable to fix or repair.
Click to expand...
Click to collapse
You misunderstand
Bricking means to permantly break it.
With a locked bootloader you can not do that because you can always do a software repair with SEUS/PCCompanion.
With an unlocked bootloader you can do that and the only potential way of savng it is with JTAG.
But here is the point, You cannot brick your phone with a locked bootloader!!!
It may lock on you, you may not be able to boot, but thats does not mean its bricked
gregbradley said:
You misunderstand
Bricking means to permantly break it.
With a locked bootloader you can not do that because you can always do a software repair with SEUS/PCCompanion.
With an unlocked bootloader you can do that and the only potential way of savng it is with JTAG.
But here is the point, You cannot brick your phone with a locked bootloader!!!
It may lock on you, you may not be able to boot, but thats does not mean its bricked
Click to expand...
Click to collapse
Thank you for clearing that up. Now I know...
Guys Thx alot~can you give me a link of the 2.3.3 SE ROM~
?
waikhin520 said:
Guys Thx alot~can you give me a link of the 2.3.3 SE ROM~
?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=936733
can i ask~download which one~><~me damm foolish~
waikhin520 said:
Guys Thx alot~can you give me a link of the 2.3.3 SE ROM~
?
Click to expand...
Click to collapse
Use PCCompanion to install stock 2.3.3 rom...
Just click on update and/or repair
I noe already~thx~downloading~hope it work~^^~alive~
Thx a lot~Man~^^~Love u guys~
HELLO ,my english is bad ......
my HTC DNA was Not start, Black screen ,When connected to the computer ,Display QDloader ........
who can help me ? thank you
Atlas.F said:
HELLO ,my english is bad ......
my HTC DNA was Not start, Black screen ,When connected to the computer ,Display QDloader ........
who can help me ? thank you
Click to expand...
Click to collapse
Is the phone like it was when new or have you rooted it and loaded some custom rom? Hard to help without some additional clues.
Atlas.F said:
HELLO ,my english is bad ......
my HTC DNA was Not start, Black screen ,When connected to the computer ,Display QDloader ........
who can help me ? thank you
Click to expand...
Click to collapse
Help me out to better understand the situation I need to know a few things...
1) What have you done to the device (is the bootloader locked or unlocked? has it been rooted? did you flash any files, if so what files? did you attempt s-off?)
2) What were you doing before this happened?
3) Can you access recovery or bootloader?
.torrented said:
Help me out to better understand the situation I need to know a few things...
1) What have you done to the device (is the bootloader locked or unlocked? has it been rooted? did you flash any files, if so what files? did you attempt s-off?)
2) What were you doing before this happened?
3) Can you access recovery or bootloader?
Click to expand...
Click to collapse
1,unlocked,
2, I was looking for root s-off .
3, can't into recovery and bootloader......:crying:
Atlas.F said:
1,unlocked,
2, I was looking for root s-off .
3, can't into recovery and bootloader......:crying:
Click to expand...
Click to collapse
After you Unlocked it, did you flash anything else?
Can you give me as much detail as to what you were doing before this happened? Like any/all files you flashed? the order you tried doing all of it? To me it sounds like a soft-brick but im not certain because ive never experience anything like this?
Try just powering off the device then hold Power and Volume Down at the same time and see what happens?
Try just turning on the phone and go into command prompt/terminal and do either an
Code:
adb devices
fastboot devices
and see if either can recognize the phone
A few days ago my watch restarted on it's own and never got past the startup..which isn't that unusual, it'd happened a few times. No big deal just reset it with the button on the back. I tried that and again an endless loop. I tried searching for any help in this situation and the only lead I found was to reset and power it down through the boot menu and let it sit for a few minutes...but didn't matter. I've wiped and reset from the boot menu, hoping it might do something to get it past the startup, but no luck yet. I didn't open up the developer options and unlock anything...so I don't believe I could try anything from the computer right? Is there any other recourse to take or am I completely hosed?
JRSly said:
A few days ago my watch restarted on it's own and never got past the startup..which isn't that unusual, it'd happened a few times. No big deal just reset it with the button on the back. I tried that and again an endless loop. I tried searching for any help in this situation and the only lead I found was to reset and power it down through the boot menu and let it sit for a few minutes...but didn't matter. I've wiped and reset from the boot menu, hoping it might do something to get it past the startup, but no luck yet. I didn't open up the developer options and unlock anything...so I don't believe I could try anything from the computer right? Is there any other recourse to take or am I completely hosed?
Click to expand...
Click to collapse
You don't need developer options to do "fun" things from the boot menu. Just an unlocked bootloader.
I have a TWRP backup somewhere, so if you have a borked system, you can always flash (or better yet, boot) TWRP (make a backup of your broken), push the backup file folder to your watch (without overwriting the broken backup), and then restore mine.
Last thing to do is a factory reset to clean up any left over garbage. Hope this helps.
But isn't Developer Options necessary to allow that? It lets you turn on ADB Debugging which would then let you get on the computer and unlock the bootloader?
Or is there an alternate way to go about things...can I unlock the bootloader from the boot menu? I've only rooted a couple phones, with a lot of careful reading and reviewing of these forums...I'm not very knowledgeable.
JRSly said:
But isn't Developer Options necessary to allow that? It lets you turn on ADB Debugging which would then let you get on the computer and unlock the bootloader?
Or is there an alternate way to go about things...can I unlock the bootloader from the boot menu? I've only rooted a couple phones, with a lot of careful reading and reviewing of these forums...I'm not very knowledgeable.
Click to expand...
Click to collapse
Fastboot is independent of ADB, so you can unlock the bootloader from the boot menu. That is the way to unlock bootloader 90+% of the time.
Just need to issue these commands (like you would ADB) :
fastboot devices
fastboot oem unlock
...and then complete the on-screen (watch) confirmation. Hope this helps.
Sent from my ASUS_Z00AD
OfficerJimLahey said:
Fastboot is independent of ADB, so you can unlock the bootloader from the boot menu. That is the way to unlock bootloader 90+% of the time.
Just need to issue these commands (like you would ADB) :
fastboot devices
fastboot oem unlock
...and then complete the on-screen (watch) confirmation. Hope this helps.
Sent from my ASUS_Z00AD
Click to expand...
Click to collapse
All right, my new problem is that the computer doesn't recognize the watch. When I plug it in it only appears as an unknown device and there's an error about the device having malfunctioned. Trying to install drivers despite the error leads nowhere, Windows says that the drivers present on the computer are up-to-date. So with it being an unknown device, I can't communicate with the watch from the command prompt.
Remove the drivers from Device Manager (check delete driver), connect your device again to the computer then reinstall the drivers.
MihaiSG said:
Remove the drivers from Device Manager (check delete driver), connect your device again to the computer then reinstall the drivers.
Click to expand...
Click to collapse
No luck, I'd tried that a couple times before...just no progress, still sees it as an unknown device and trying to force install the drivers does nothing. It says the existing drivers are up to date.
I'm getting more and more discouraged. I can't seem to make any progress. I'm looking into sending it away for repair even though, of course, it's about two months out of the warranty.
You are not removing the drivers correctly, make sure that you have this option checked and try again:
http://www.sevenforums.com/tutorials/77614-device-manager-hidden-devices.html
MihaiSG said:
You are not removing the drivers correctly, make sure that you have this option checked and try again:
http://www.sevenforums.com/tutorials/77614-device-manager-hidden-devices.html
Click to expand...
Click to collapse
Anything more I should be doing? Everything mentioning Android or ADB is removed. I'd never plugged the watch in before and installed drivers, so there's nothing from the watch to delete. But still the same thing, Windows only sees it as a Unknwon Device under USB controllers and sees no need to update drivers when I try, since it doesn't seem to see it as a watch or Android device of any sort.
Are you sure that you have installed the correct drivers? What is the hardware id?
MihaiSG said:
You are not removing the drivers correctly, make sure that you have this option checked and try again:
http://www.sevenforums.com/tutorials/77614-device-manager-hidden-devices.html
Click to expand...
Click to collapse
MihaiSG said:
Are you sure that you have installed the correct drivers? What is the hardware id?
Click to expand...
Click to collapse
I think so? I'm far from an expert but I've messed with a handful of phones and tablets in the last five years and never had issues with drivers I didn't sort out fairly easily. I downloaded the official Google USB driver, I tried the LG Watch Tool which installs the Universal ADB driver.The LG Watch then finds no devices.
I'm a bit ignorant, what hardware ID do you refer to? Of the driver?
Of the device.
Here is a guide:
http://www.makeuseof.com/tag/how-to-find-unknown-device-drivers-by-their-vendor-device-id/
Can you post some screenshots from device manager?
MihaiSG said:
Of the device.
Here is a guide:
http://www.makeuseof.com/tag/how-to-find-unknown-device-drivers-by-their-vendor-device-id/
Can you post some screenshots from device manager?
Click to expand...
Click to collapse
Device Manager wasn't much help for finding the IDs, but I tried using USBDeview and it's reporting something as Android Bootloader Interface, which I'll have to assume is the watch. The vendor ID is 18D1 and the product ID is 4EE0. And here is a screen cap of the entry in the Device Manager that I've been seeing. If there's anything more specific in the device's properties that could be insightful, let me know.
Your device is seen as an unknown device. My only advice is to try on another PC your last working drivers and maybe it will work.
Hi fellow developers.
So,my story is quite weird and expected indeed.
Being the noob I am at flashing custom roms and recoveries,I flashed orange fox recovery on my device,even flashed a custom rom and managed to use it for about 3/4 hours.
Then I thought that my device was ready, all my changes work,and it is a good idea to relock my bootloader.So,without flashing the stock recovery back,I relocked my bootloader.
After reboot,my device is stuck on "Red state" and keeps on rebooting after every 5 secs. I can't even boot to fastboot mode,nor can I completely shut down my device.
So any ideas what can I do? Do I need to go to the service center? If yes,what would they do and how much would they charge?
Thank you!.
Kaybee2611 said:
Hi fellow developers.
So,my story is quite weird and expected indeed.
Being the noob I am at flashing custom roms and recoveries,I flashed orange fox recovery on my device,even flashed a custom rom and managed to use it for about 3/4 hours.
Then I thought that my device was ready, all my changes work,and it is a good idea to relock my bootloader.So,without flashing the stock recovery back,I relocked my bootloader.
After reboot,my device is stuck on "Red state" and keeps on rebooting after every 5 secs. I can't even boot to fastboot mode,nor can I completely shut down my device.
So any ideas what can I do? Do I need to go to the service center? If yes,what would they do and how much would they charge?
Thank you!.
Click to expand...
Click to collapse
Not that only you should have the stock recovery to relock bootloader, you should need to return completely to stock to can relock it safely.
Follow this guide carefully https://forum.xda-developers.com/t/repair-dead-hard-bricked-realme-3-3i-tutorial.4224255/ replace all the files needed when it comes to your specific model.
Kaybee2611 said:
Hi fellow developers.
So,my story is quite weird and expected indeed.
Being the noob I am at flashing custom roms and recoveries,I flashed orange fox recovery on my device,even flashed a custom rom and managed to use it for about 3/4 hours.
Then I thought that my device was ready, all my changes work,and it is a good idea to relock my bootloader.So,without flashing the stock recovery back,I relocked my bootloader.
After reboot,my device is stuck on "Red state" and keeps on rebooting after every 5 secs. I can't even boot to fastboot mode,nor can I completely shut down my device.
So any ideas what can I do? Do I need to go to the service center? If yes,what would they do and how much would they charge?
Thank you!.
Click to expand...
Click to collapse
For future reference, NEVER re-lock the bootloader when your phone isn't 100% stock. The guide SubwayChamp linked above should work.
SubwayChamp said:
Not that only you should have the stock recovery to relock bootloader, you should need to return completely to stock to can relock it safely.
Follow this guide carefully https://forum.xda-developers.com/t/repair-dead-hard-bricked-realme-3-3i-tutorial.4224255/ replace all the files needed when it comes to your specific model.
Click to expand...
Click to collapse
Hey @SubwayChamp
I did try the method you recommended. But,my phone is not recognised as a mediatek device.They show all the connected devices as usb.
Kaybee2611 said:
Hey @SubwayChamp
I did try the method you recommended. But,my phone is not recognised as a mediatek device.They show all the connected devices as usb.
Click to expand...
Click to collapse
[GUIDE] REALME 7 RMX2155 GLOBAL BOOTLOADER UNLOCK
WELCOME, ALL. After a very tiring process of swapping between ROMs and changing regions, APKs, et cetera, we have finally been able to perfect the method for unlocking the bootloader of the RMX2155! This is a detailed guide aimed to give you an...
forum.xda-developers.com
Try following step one to eight inclusive. Should then recognize your device.
Kaybee2611 said:
Hey @SubwayChamp
I did try the method you recommended. But,my phone is not recognised as a mediatek device.They show all the connected devices as usb.
Click to expand...
Click to collapse
how much will service center charge for repairing it??
Hey for me same problem now in my narzo 30a.... can u fix that problem ? @Kaybee2611
daitama said:
how much will service center charge for repairing it??
Click to expand...
Click to collapse
I didn't bring it to the repair center, in my country no one knows about. IDK which the price could be, maybe 40 buckets.
I am not responsible for bricked devices, dead SD cards, etc!
I have not tested the global unlock, Global version unlock thread.
Make sure you make backups before unlocking the bootloader, as this operation will wipe all user data and apps.
Make sure your system version is the official and latest one.
Requirements
- 60% charge on the phone
- PC and usb data cable
- Installed fastboot and proper drivers on your PC
1. Install Deep Testing Apk attached in this post.
2. Click on the Apply Now button in order to get approval for bootloader unlock.
3. Check the status after apply using the Query Approval Status.
4. If you get an error, force stop the application, change your device language to Chinese and try again (if someone can post screenshot of what to tap, I would update this post)
5. Once the approval is done, tap Start Testing button, this will reboot your device in the bootloader.
6. Last chance, make backups at this point otherwise your data is gone.
7. Run command
Code:
fastboot flashing unlock
8. Done, you can now reboot into system normally
If I missed anything, kindly comment and I'll update OP.
myogui said:
I am not responsible for bricked devices, dead SD cards, etc!
Make sure you make backups before unlocking the bootloader, as this operation will wipe all user data and apps.
1. Install Deep Testing Apk attached in this post.
2. Click on the Apply Now button in order to get approval for bootloader unlock.
3. Check the status after apply using the Query Approval Status.
4. If you get an error, force stop the application, change your device language to Chinese and try again (if someone can post screenshot of what to tap, I would update this post)
5. Once the approval is done, tap Start Testing button, this will reboot your device in the bootloader.
6. Last chance, make backups at this point otherwise your data is gone.
7. Run command
Code:
fastboot flashing unlock
8. Done, you can now reboot into system normally
If I missed anything, kindly comment and I'll update OP.
Click to expand...
Click to collapse
Hi myogui
Do you have the firmware for RMX3300_11_A.19?
Do I run that command from the phone? When I start deep testing and phone reboots I only have the options to start, power off, recovery, and restart bootloader.
I can't get this to work on A19 firmware no matter what I do. Says not supported on this model even though I have the correct RMX3300 so I am going to upgrade to A20 and see if it works
Nope upgrading to A20 doesn't work either. Always get failed to submit in either english or chinese.
wildlime said:
Nope upgrading to A20 doesn't work either. Always get failed to submit in either english or chinese.
Click to expand...
Click to collapse
It did take a couple of tries to get it to work but still that was done in like 10-15 minutes. You could try to factory reset the phone first but if it's still doesn't work for you you'll be stuck re-installing everything on your phone.
wildlime said:
Nope upgrading to A20 doesn't work either. Always get failed to submit in either english or chinese.
Click to expand...
Click to collapse
Same problem. It work for me trying all Chinese languages (simple and another two). It seems stuck for like 30 minutes, then idk why I've exit and re enter the app and it worked.
i cant get my computer to recogize the phone when in bootloader. Anyone else run into this? i ran the fastboot command with the phone plugged in but its still waiting for a device to connect
Bnblare said:
i cant get my computer to recogize the phone when in bootloader. Anyone else run into this? i ran the fastboot command with the phone plugged in but its still waiting for a device to connect
Click to expand...
Click to collapse
Try another USB cable and make sure you are in the folder where fastboot program is.
Bnblare said:
i cant get my computer to recogize the phone when in bootloader. Anyone else run into this? i ran the fastboot command with the phone plugged in but its still waiting for a device to connect
Click to expand...
Click to collapse
Download the attached file, then install manually the driver, select the android_winusb.inf file.
myogui said:
Try another USB cable and make sure you are in the folder where fastboot program is.
Click to expand...
Click to collapse
hacls said:
Download the attached file, then install manually the driver, select the android_winusb.inf file.
Click to expand...
Click to collapse
Thanks! This is definitely a driver issues.
I have an RMX 3300 Chinese model. Build number is RMX3300_11_A.20. When I run the deeptesting_RMX3300.apk it says "Failed to submit application. This phone model does not support deep testing. "
robert3892 said:
I have an RMX 3300 Chinese model. Build number is RMX3300_11_A.20. When I run the deeptesting_RMX3300.apk it says "Failed to submit application. This phone model does not support deep testing. "
Click to expand...
Click to collapse
I finally managed to get past this point. But when I go to step 7 it says waiting for device. I'm using the same USB cable that works for ADB. Might try another cable tomorrow and/or another usb port.
Tried different cables and usb ports. Still stuck on 'waiting for device'
robert3892 said:
I finally managed to get past this point. But when I go to step 7 it says waiting for device. I'm using the same USB cable that works for ADB. Might try another cable tomorrow and/or another usb port.
Click to expand...
Click to collapse
Is a secret how you managed that?
criszz said:
Is a secret how you managed that?
Click to expand...
Click to collapse
I believe that the servers which grant permission for the deep testing app are busy at different times of the day. I simply retried the app during different times of the day until it worked. I still am working on a complete solution
robert3892 said:
Tried different cables and usb ports. Still stuck on 'waiting for device'
Click to expand...
Click to collapse
Fixed this issue finally by installing the android bootloader usb drivers
OK I have this working. I believe I will now need to relock the bootloader
robert3892 said:
OK I have this working. I believe I will now need to relock the bootloader
Click to expand...
Click to collapse
Don't relock the bootloader using the ADB lock command. This will brick your device!
Everithing ok, thanks man.