Database Develop

Moto G xt1072 won't boot at all after installing TWRP+SuperSU

Hello everyone,
I've just tried installing twrp-3.0.2-3-thea.img (md5sum: 35c37561f0c22bfe23cd01b5c388e8b5) and BETA-SuperSU-v2.62-3-20151211162651.zip (md5sum: 7fcb30bcbcd18b5f0b0f5848a096d4ed) on a Moto G LTE 2014 "Thea".
Unfortunately something didn't work. The device first was stuck in the boot animation, then started booting correctly a few times, but now it's completely bricked:
I've been unable to turn the phone on using either pressing power+button down for 10 secs or just pressing the power button for 2 mins while being connected to an usb charger. Obviously it won't connect to adb/fastboot/etc.
I'm really puzzled. Is it even possible to brick a device like this just by trying to root it? Any suggestions?

Alright, found the issue - it seems that for some reason or another flashing TWRP or SuperSu caused fastboot to stop working, hence the hard brick. Now It shows up as "qhsusb_bulk" - unfrotunately there's no way to fix this by myself given that the only fastboot images ( "MBM-CI") available are for Android 4.4.4.

If your bootloader is unlocked you shouldn't have any problems reflashing. You do however have to make sure you are flashing the correct recovery IMG for your phone there are a very large number of ROMS and each is device specific. Try leaving LTE out of your search criteria when searching for images to flash with, rather just Moto G 2nd gen 2014 and you will be on your way to finding the correct IMG. I found a Titan IMG that works with my XT1072 and believe you me that was after the 5th/6th time of reflashing! Another handy tip is that in order to enter into fast boot or recovery mode there's are a few things to consider, namely
The version of fastboot adb you have installed on your PC, some versions behave strangely? Don't ask me I know nothing!
Secondly and very importantly you need to have latest drivers for your make and model of phone installed on your PC.
Thirdly before you connect your phone via its USB cable to PC you must first start up fastboot if you are just using fastboot. I have mine sitting as shortcut on desktop right next to adb shortcut for convenience.
Fourth: hold power button plus vol down for about 3-5 seconds, continue to hold vol- button but let go of power button (this is an important detail that many people on the forum forget to mention) with Motorola specifically!!!! Trust me do it this way and you will almost certainly always boot into recovery/fastboot mode
5th connect your phone to your PC ( not to teach your grama how to suck eggs but don't forget to select USB debugging under dev options on your phone) hopefully you did this??? Otherwise I don't know what the work around is for that, other than factory reset and start over?!
Anyway after connect to PC in the shell terminal run the adb devices command if you are in adb or
run the fastboot devices if you are in fastboot to see if your computer can detect your device? This is a clear indication of whether or not your bootloader is unlocked and/or whether USB Debugging is selected, shouldn't be hard to work out which device is yours as only one device should then show up. There are threads on XDA about how to unlock BL. Aquire root and flash recovery images, obviously, but I couldn't begin to tell you how to do that as each scenario is so different from the next, best of luck!:good:

None of those solutions would obviously work, considering the bootloader/fastboot partition has been altered to the point the device won't boot at all, forget about Drivers or USB Debugging.
By the way, I've just got my device from motorola, after roughly two months since they took it to the repair centre. Their official response has been "We won't fix devices who had been tampered with".
Oh well. When I got it back the clerk could only congratulate me for my really nice new paperweight.

The phone isn't starting at all? It shows something on the screen or acts just like powered off?
Now It shows up as "qhsusb_bulk"
Click to expand...
Click to collapse
You mean the PC isn't recognizing the phone at all and just shows an USB device with that identifier?

LuuchoRocha said:
The phone isn't starting at all? It shows something on the screen or acts just like powered off?
Click to expand...
Click to collapse
Completely blank screen. No response whatsoever.
You mean the PC isn't recognizing the phone at all and just shows an USB device with that identifier?
Click to expand...
Click to collapse
That's right. It's the same error which occurs on some MSM89xx SoCs when the bootloader/blankflash gets steamrolled. But contrary to what happens to some devices like the Galaxy SIII, there are no available bootloader image files available anywhere, and it looks like the SoC used on mot g devices does not provide any failsafe boot mode from sd.
In other words, it's a really nice paper weight until a disgruntled Lenovo employee leaks the required files somewhere. Actually, according to the Motorola tech guy I've spoken to, there's the chance that clearing the bootloader triggers an efuse making it impossible to recover from altogether, but I really hope this is not the case.

SOLVED---OP3T Bricked - stucked at FastbootMode

Hi,
Last Sunday (5) my phone turns off with 25% battery and just don´t turn on.
I was with the stock Oxygen OS.
Now when i turn it on, the oneplus logo appears and the next "screen" that should be the android or any other OS loading, just don´t appear. It just go to black and turn off.
Reading the Threads here about "OP3T Bricked" they all requests to hold volume up, and connect the usb cable.
The problem is when i do it, the driver just pop up at Device Manager List, and few seconds later it disappears.
(Try it using 4 different computers (Desktop win7 , laptop win7, laptop win 10 and desktop winxp) and 2 original OP cables.)
I had read a lot of informations that you share here in forum, but no tips helps to solve this issue.
So i contact the OnePlus support, they give me some links to download 2 encrypted files that looks like the files you guys shares here (One is the driver and the other is some kind of unbrick tool called MSM).
They connect at my computer and as soon they see that my driver just pop up and disappear, they stop the process and said to me to send the device to one support center.
Probably i will do it, but first i want to guarantee that its nothing i can do here.
So I try to reach my phone throw ADB and fastboot commands.
When at the screen of Fastboot I have some information about the phone and the last line said:
DEVICE STATE - LOCKED
using the command adb devices, we don´t find anything.
using fastboot devices, my device is listed by the serial number.
Should be possible to recover it using fastboot commands ?
There is a way to analyze my phone throw fastboot commands? Something like "all hardware is ok", like the memory, battery, etc ?
Best Regards

I have encountered the same issue while I was playing around with a beta oreo rom the name of which I wouldn't not want to mention here. Got my phone bricked and it wouldn't boot to recovery. Only fastboot was accessible so what I did was just flash the blusaprk v45 recovery and after booting I was finally successful in booting my phone into recovery where I wiped system, data, cache and dalvik without internal storage and flashed a nougat rom. Thankfully I was able to revive my phone and that solved my issue.

UPDATE:
I try to use the fastboot commands, but to do it i must use "fastboot oem unlock"
And guess what?! i can´t ...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.023s
Click to expand...
Click to collapse
So a lot of answer for the people who get this fail is to use the MSM tool .....
Any tips ?

Have you read THIS thread? Try to follow exactly those instructions...

jonsat said:
Have you read THIS thread? Try to follow exactly those instructions...
Click to expand...
Click to collapse
Hi Jonsat,
Yes, i tested and as i said, i can´t do it because the driver don´t still at device manager list.
So, the problem was solved, i need to use the OnePlus Support and converge them to use the files like "my method":
The Regular method is:
1) Hold volume +
2) When holding, plug the phone at PC
3) The device should appear at device manager, so you can run tools like MSM
This method does not work for me because my device doesn't still at device manager list, it just pops up and disappears.
So to make it work i need to:
1) Turn off the phone
2) Hold power + Volume +
3) Plug the phone
4) The phone should start with fastboot menu
5) Select recovery mode
6) hold volume +
Now the driver still on device list.
Using this solution, the files that we see here in forum does not work.
Need to use the files from OnePlus Support, MSM3.08 + OnePlus3T_A56(A57, or newer) + Driver Qualcomm signed 24/04/2013.
Thanks you

Glad that you solved! Surely your accurate description of correct procedure will be useful for other people.

jonsat said:
Glad that you solved! Surely your accurate description of correct procedure will be useful for other people.
Click to expand...
Click to collapse
Glad to help

ADB Works, Fastboot still "waiting for any device"

I have been blundering my way though the internet to get my ROG Phone 2 rooted. I have unlocked the bootloader, I have a modified boot image from magisk, I have the ADB connection set up through USB and it works fantastically. I honestly don't know how I got it work, it involved many different driver update attempts and then figuring out I hadn't put the phone into USB debugging, but now fastboot doesn't work.
ADB will list the device, but fastboot cannot see it. I have tried rebooting the phone into the bootloader, but there is no connection on either. Not sure why I thought that would work, but I tried. I really don't understand enough about fastboot to get any farther on my own.
I have the tencent version and I was pretty certain I have the CN android 9.0 on it, but I am no longer certain of that. I am running windows 10.
This is my build number: PKQ1.190414.001.WW_Phone-16.0622.1906.19-0
I honestly don't know, but does that WW mean my tencent phone is running the WW firmware?

RichDoe252 said:
I have been blundering my way though the internet to get my ROG Phone 2 rooted. I have unlocked the bootloader, I have a modified boot image from magisk, I have the ADB connection set up through USB and it works fantastically. I honestly don't know how I got it work, it involved many different driver update attempts and then figuring out I hadn't put the phone into USB debugging, but now fastboot doesn't work.
ADB will list the device, but fastboot cannot see it. I have tried rebooting the phone into the bootloader, but there is no connection on either. Not sure why I thought that would work, but I tried. I really don't understand enough about fastboot to get any farther on my own.
I have the tencent version and I was pretty certain I have the CN android 9.0 on it, but I am no longer certain of that. I am running windows 10.
This is my build number: PKQ1.190414.001.WW_Phone-16.0622.1906.19-0
I honestly don't know, but does that WW mean my tencent phone is running the WW firmware?
Click to expand...
Click to collapse
Fun fact, I just got Fastboot access from my computer by using the side USB port and rebooting into the bootloader from ADB. Still not to sure about the version bit. I think I'm just going to give it whirl and brick my device, maybe.

RichDoe252 said:
I have been blundering my way though the internet to get my ROG Phone 2 rooted. I have unlocked the bootloader, I have a modified boot image from magisk, I have the ADB connection set up through USB and it works fantastically. I honestly don't know how I got it work, it involved many different driver update attempts and then figuring out I hadn't put the phone into USB debugging, but now fastboot doesn't work.
ADB will list the device, but fastboot cannot see it. I have tried rebooting the phone into the bootloader, but there is no connection on either. Not sure why I thought that would work, but I tried. I really don't understand enough about fastboot to get any farther on my own.
I have the tencent version and I was pretty certain I have the CN android 9.0 on it, but I am no longer certain of that. I am running windows 10.
This is my build number: PKQ1.190414.001.WW_Phone-16.0622.1906.19-0
I honestly don't know, but does that WW mean my tencent phone is running the WW firmware?
Click to expand...
Click to collapse
1. You are running a WW rom, but that doesn't necessarily mean your fingerprint is matched. To update you need to have both WW rom and WW fingerprint. You can check if your fingerprint is CN or WW using device info hw from playstore under 'system'
2. In order to root you need to have a matching root boot img for your current rom ie root img for 1906.19, just checking that your know this?
3. Have you managed to get the phone recognised using the cmd 'fastboot devices'? Also are you using the side port?
4.when you say bootloader, have you definitely got the phone in fastboot mode - hold vol up and power button until you see the screen with some options. That screen is fastboot mode, you don't need to select any further options. Once in that mode, connect to pc, open adb and run the fastboot devices cmd. Once your device is recognised, report back here for further steps

superbrick.
reg66 said:
1. You are running a WW rom, but that doesn't necessarily mean your fingerprint is matched. To update you need to have both WW rom and WW fingerprint. You can check if your fingerprint is CN or WW using device info hw from playstore under 'system'
2. In order to root you need to have a matching root boot img for your current rom ie root img for 1906.19, just checking that your know this?
3. Have you managed to get the phone recognised using the cmd 'fastboot devices'? Also are you using the side port?
4.when you say bootloader, have you definitely got the phone in fastboot mode - hold vol up and power button until you see the screen with some options. That screen is fastboot mode, you don't need to select any further options. Once in that mode, connect to pc, open adb and run the fastboot devices cmd. Once your device is recognised, report back here for further steps
Click to expand...
Click to collapse
Thanks for the reply! I did indeed get fastboot to work over USB. Fastboot devices reported back the serial number and everything. I did not know that the build need to match on both the boot and the rom, but that does make sense and I probably should have realized that before I went ahead and copied the rooted boot.img I had over. Then my phone couldn't boot up proper, and got stuck in fastboot. Then I went ahead and copied all of the contents of the same rom over and now it is literally just a black screen. Won't turn on any more. I think I super bricked it.
Sorry I didn't see your post earlier and I know I am not father into the deep end, but is there a way out from where I am.

RichDoe252 said:
Thanks for the reply! I did indeed get fastboot to work over USB. Fastboot devices reported back the serial number and everything. I did not know that the build need to match on both the boot and the rom, but that does make sense and I probably should have realized that before I went ahead and copied the rooted boot.img I had over. Then my phone couldn't boot up proper, and got stuck in fastboot. Then I went ahead and copied all of the contents of the same rom over and now it is literally just a black screen. Won't turn on any more. I think I super bricked it.
Sorry I didn't see your post earlier and I know I am not father into the deep end, but is there a way out from where I am.
Click to expand...
Click to collapse
Oh jeepers dude. So just a black screen... Can you at least boot into fastboot?

reg66 said:
Oh jeepers dude. So just a black screen... Can you at least boot into fastboot?
Click to expand...
Click to collapse
Nope. The only response I can get out of it now is when I plug it into the fastboot port, the computer recognizes that something was plugged in. I don't even get a device on a device manager.

RichDoe252 said:
Nope. The only response I can get out of it now is when I plug it into the fastboot port, the computer recognizes that something was plugged in. I don't even get a device on a device manager.
Click to expand...
Click to collapse
Try holding the power button for around 20 secs until it shuts down. Then try vol up and power together and see if you get back to fastboot. If that doesn't work try vol up vol down and power buttons all together. Then try again to put it in fastboot mode using vol up and power. Let us know what happens /if you can reach fastboot mode

reg66 said:
Try holding the power button for around 20 secs until it shuts down. Then try vol up and power together and see if you get back to fastboot. If that doesn't work try vol up vol down and power buttons all together. Then try again to put it in fastboot mode using vol up and power. Let us know what happens /if you can reach fastboot mode
Click to expand...
Click to collapse
Unfortunately, nothing. Holding power for 20 seconds showed nothing, and like wise for volume up and power. Battery was fully charged too. Had it plugged in for most of today while I was trying to get fastboot to work.

RichDoe252 said:
Unfortunately, nothing. Holding power for 20 seconds showed nothing, and like wise for volume up and power. Battery was fully charged too. Had it plugged in for most of today while I was trying to get fastboot to work.
Click to expand...
Click to collapse
Is there any sort of illumination to the black screen ie do you think the phone is on but the screen is black or do think the phone is completely off?
Holding power button for a while should switch it off after a while. Try holding for longer than 20 secs, then try booting into fastboot mode
---------- Post added at 04:00 AM ---------- Previous post was at 03:44 AM ----------
Well dude, it's 4 am here. Gotta get some sleep dude. Will check here when I wake. Good luck in the mean time

Still trying to get to sleep. How ya getting on? What about vol down and power buttons for 30+secs, can you try that and let us know the results

reg66 said:
Still trying to get to sleep. How ya getting on? What about vol down and power buttons for 30+secs, can you try that and let us know the results
Click to expand...
Click to collapse
Bro get to sleep! Such a good Samaritan

TikiThePug said:
Bro get to sleep! Such a good Samaritan
Click to expand...
Click to collapse
LOL! I would if I could, just can't sleep yet. Hopefully soon tho!

RichDoe252 said:
Unfortunately, nothing. Holding power for 20 seconds showed nothing, and like wise for volume up and power. Battery was fully charged too. Had it plugged in for most of today while I was trying to get fastboot to work.
Click to expand...
Click to collapse
Try a USB 2.0 port? Surprisingly this works for some phones even though it's compatible with 3.0.

reg66 said:
Still trying to get to sleep. How ya getting on? What about vol down and power buttons for 30+secs, can you try that and let us know the results
Click to expand...
Click to collapse
Well, It's been untouched for a day now, and it still will not react to input. No response from long hold on the power button. I will try again in the morning. Is it possible that I somehow wrote into the BIOS of the phone? Android does use a BIOS, right?

RichDoe252 said:
Well, It's been untouched for a day now, and it still will not react to input. No response from long hold on the power button. I will try again in the morning. Is it possible that I somehow wrote into the BIOS of the phone? Android does use a BIOS, right?
Click to expand...
Click to collapse
Android itself does not have a BIOS, since Android is an OS and BIOS is more similar to firmware. But yes, the phone does have firmware, and it could be that the mismatch in firmware versions (from which you tried to flash), has caused the bootloader to "not know what to do now" when trying to start the phone up.
One thing which comes with all phones with a Qualcomm chipset is something called Qualcomm Crashdump Mode. You can try to see if you can get your phone in EDL (emergency download) mode and restore the correct firmware in that way:
https://www.the***********.com/rog-phone-2-unbrick-guide (URL gets censored for some reason; it should be "the custom droid" with no spaces)
Also, if you continue to have driver issues with connecting the phone to your PC, are you able to test another PC or even a Mac if you have access to one? I find Windows can be a giant pain for getting ADB and fastboot to work properly at times.
Good luck and let us know how it goes.

reg66 said:
Still trying to get to sleep. How ya getting on? What about vol down and power buttons for 30+secs, can you try that and let us know the results
Click to expand...
Click to collapse
Ok, so here's where I am: I have left the phone unplugged for a long time now. Really had no effect. I just downloaded QPST and I can actually get my computer to see the phone. However, I am still not quite sure how to USE QPST and not make things worse. So this is my plan: I am going to look through the forums here for info on how to use QPST to get my phone working again. Not really sure what that will look like, but fastboot would be a good start. From there, it sounds like I have to get the original firmware back on it, and then go about the process of rooting once again.
Still leaves me with the issue that started me down the path of rooting this phone, but at least it will not longer be bricked.

RichDoe252 said:
Ok, so here's where I am: I have left the phone unplugged for a long time now. Really had no effect. I just downloaded QPST and I can actually get my computer to see the phone. However, I am still not quite sure how to USE QPST and not make things worse. So this is my plan: I am going to look through the forums here for info on how to use QPST to get my phone working again. Not really sure what that will look like, but fastboot would be a good start. From there, it sounds like I have to get the original firmware back on it, and then go about the process of rooting once again.
Still leaves me with the issue that started me down the path of rooting this phone, but at least it will not longer be bricked.
Click to expand...
Click to collapse
You may not HAVE to flash complete firmware, it is quite likely that the boot.img is causing the problem as you flashed an incompatible version. Below you'll flash the correct version which HOPEFULLY will fix your phone, provided you can get into fastboot mode now.
Haven't read back through all the thread so i can't recall all the details of where you're at. As far as i can tell you're still running WW 16.0622.1906.19-0, correct? Can you get the device to now boot into fastboot mode? (from a powered off state, press and hold vol up and power at the same time. You should then be presented with some options, DON'T select any option. With that menu screen open is fastboot mode.
1. Download and install ADB Fastboot from here to C: drive of your pc/laptop.
2. With your phone in fastboot mode (as detailed above) connect it to pc/laptop using the side port of the phone.
3. Navigate to C:\Program Files (x86)\Minimal ADB and Fastboot folder and double click the cmd-here.exe, this will open a cmd window.
4. Type 'fastboot devices' to check that it's recognised, there should be a serial/key shown after entering that cmd.
5. Provided the serial/key is shown in fastboot mode, download the following boot.img (which is for WW 1906.19) from here.
6. Copy that boot img to the same folder you have open for ADB (C:\Program Files (x86)\Minimal ADB and Fastboot)
7. In the cmd window type 'fastboot flash boot boot.img'.
Now, that boot img is the STOCK boot img for your rom version. Don't worry about rooting for now (if i recall correctly, your phone won't boot to system), let's just try to get the phone booting first. Providing there are no errors when flashing the boot img, on the phone fastboot menu, scroll through and choose 'restart'.
Let me know if the device boots to system now... Good luck
I'll pm you my email address so you'll be able to get hold of me if you get stuck at any stage...
EDIT: was forgetting you tried so many times to get into fastboot mode, without success.
---------- Post added at 08:59 PM ---------- Previous post was at 08:17 PM ----------
Dude, is your phone screen still black but switched on? When you tap the screen does it vibrate. I'm thinking you might already be in edl mode (which could be a good thing). Let us know
Check your pm's dude for further info. I can't post links to the site required so have sent via pm

TikiThePug said:
Android itself does not have a BIOS, since Android is an OS and BIOS is more similar to firmware. But yes, the phone does have firmware, and it could be that the mismatch in firmware versions (from which you tried to flash), has caused the bootloader to "not know what to do now" when trying to start the phone up.
One thing which comes with all phones with a Qualcomm chipset is something called Qualcomm Crashdump Mode. You can try to see if you can get your phone in EDL (emergency download) mode and restore the correct firmware in that way:
https://www.the***********.com/rog-phone-2-unbrick-guide (URL gets censored for some reason; it should be "the custom droid" with no spaces)
Also, if you continue to have driver issues with connecting the phone to your PC, are you able to test another PC or even a Mac if you have access to one? I find Windows can be a giant pain for getting ADB and fastboot to work properly at times.
Good luck and let us know how it goes.
Click to expand...
Click to collapse
Just dropping you a quick note to say thanks for thanks! LOL. Yeah, your post earlier seems like the best place to go. Have used Miflash Tool a few times on Xiaomi devices, it's pretty good and straight forward. Should be a LOT easier than using QPST and having to change EMMC to UFS.
Can't remember where i saw it now, but i'm sure i read that if the phone screen is black (but switched on) and vibrates, then it's likely to be in EDL mode already. Which will hopefully be good news for @RichDoe252. Before that (having never been in that situation), i wasn't aware that an all black screen could mean EDL mode is active. Fingers crossed for Rich it'll all work out just fine.
@RichDoe252 If all goes successfully using the QPST file download (and using the Miflash Tool the guide mentions in the pm i sent you) and flashing, DON'T ROOT JUST YET!!!! LOL. Let us know how it goes and then we can look into, and point you in the right direction, for getting you rooted and up to date on latest A9 or A10 whichever you'd prefer

Well I must say Rich, I'm surprised you haven't been back here yet to give any updates on progress!! Sent you a couple of emails through pm... Man, if it was my fairly expensive phone that was in the poo pan, I'd be all over trying to fix it lol

reg66 said:
Well I must say Rich, I'm surprised you haven't been back here yet to give any updates on progress!! Sent you a couple of emails through pm... Man, if it was my fairly expensive phone that was in the poo pan, I'd be all over trying to fix it lol
Click to expand...
Click to collapse
First off, you are a freaking saint. I really do appreciate all the help you have been offering up, and I am sorry I have not been very quick with a response. As my phone currently stands, I get 0% response from anything I do to it. No vibrate, nothing. No indication it even is plugged in. I had it connected to my PC with QPST installed, and it was able to pick up that the phone was there, and then immediately tried to download something to it. Not sure what, not sure why, but that kinda typifiies my interaction with this whole process so far. If you haven't guessed, I'm kinda in over my head.
Back to the problem: QPST started some opperation to download something to it. Wouldn't let me do anything else, said the phone was in "download mode". Either way it stopped at 30% and didn't progress for 30 minutes, so I tried to unplug it and plug it back in. Same interaction. Unable to do anything to the phone, no reaction from the phone what so ever. This was, by the way, plugged into the fastboot side port.
I saw that you PM'ed me, and now I can't find the email notification or the PMs on the site. Forgive me for being unfortunately new at this. I will get back to you bud, and thank you again.

Alcatel 1C suddenly says "can't load Android system"

I've ran into the following problem:
came home and try to open my phone, code doesn't work to unlock screen. Unless I'm going insane was sure the code was correct twice.
Restart phone, stuck on enjoy.now for a long time, goes to alcatel logo, then goes into an Android Recovery message saying "can't load Android system. Your data may be corrupt."
Then 2 options: try again or Factory data reset.
I've managed to find the following possible solution: https://glebovdev.medium.com/how-to-fix-cant-load-android-system-issue-8a5b0ead5a15
..but I can't even get to recovery screen with more than 2 options. It would be a huge pain if I have to factory reset.. should it be possible to get to recovery mode on my phone as well?
Is there any possible way to get the data off the phone (mainly Google Authenticator to which I'm not sure I have the codes anymore)?
Thanks

BrickAlcatel said:
I've ran into the following problem:
came home and try to open my phone, code doesn't work to unlock screen. Unless I'm going insane was sure the code was correct twice.
Restart phone, stuck on enjoy.now for a long time, goes to alcatel logo, then goes into an Android Recovery message saying "can't load Android system. Your data may be corrupt."
Then 2 options: try again or Factory data reset.
I've managed to find the following possible solution: https://glebovdev.medium.com/how-to-fix-cant-load-android-system-issue-8a5b0ead5a15
..but I can't even get to recovery screen with more than 2 options. It would be a huge pain if I have to factory reset.. should it be possible to get to recovery mode on my phone as well?
Is there any possible way to get the data off the phone (mainly Google Authenticator to which I'm not sure I have the codes anymore)?
Thanks
Click to expand...
Click to collapse
It could be that your device is trying to boot to the inactive slot, verify in fastboot mode which slot is marked as active and try to boot either in A and/or in B slot.

Idk if I'm doing something wrong but holding volume up or down as it restarts, the only boot screen I get is:
Android Recovery
TCL/5003d_EEEA/Curie
8.1.0/OPM2.171019.012/5003d_ALWE_EEA_V3
user/release-keys
(aforementioned error)
Try again
Factory data reset
fastboot mode should show other options right?

BrickAlcatel said:
Idk if I'm doing something wrong but holding volume up or down as it restarts, the only boot screen I get is:
Android Recovery
TCL/5003d_EEEA/Curie
8.1.0/OPM2.171019.012/5003d_ALWE_EEA_V3
user/release-keys
(aforementioned error)
Try again
Factory data reset
fastboot mode should show other options right?
Click to expand...
Click to collapse
Well, fastboot is to interact through fastboot commands and you can check from there the slot that is active with
Code:
fastboot getvar all
and you see something like slot_active xx

When I run adb devices in powershell it does not show any devices connected (although the device does show as connected in Windows device management).
In device management it does show as "MTP USB device".
Is this likely to be a driver issue?

BrickAlcatel said:
When I run adb devices in powershell it does not show any devices connected (although the device does show as connected in Windows device management).
In device management it does show as "MTP USB device".
Is this likely to be a driver issue?
Click to expand...
Click to collapse
Device has to be power on to respond to adb commands and from what you were telling your device is bricked..

It's technically powered on but yes still does nothing but bootloop and try again/factory reset screen. There's no possible other way to get to Android recovery mode when the volume down+power option doesn't seem to be working?

BrickAlcatel said:
It's technically powered on but yes still does nothing but bootloop and try again/factory reset screen. There's no possible other way to get to Android recovery mode when the volume down+power option doesn't seem to be working?
Click to expand...
Click to collapse
Device has to be strongly and consistently on so adb commands can work, they can't work while in bootloop so forget it this way.
What you can try is tipically pwr + vol. up and pwr + vol. dwn, one of them will take you to fastboot mode where you can give it a try to what I pointed out in previous outputs.

OK some progress.. apparently you have to let go of power button and volume up right as the alcatel logo appears, the timing seems to matter. I'm now able to see Android recovery with more options at least so will try from there.
Thanks again for taking time to reply.

I've tried
Code:
fastboot getvar all
this results in <waiting for any device>
adb devices still shows no list of devices even though in Device Manager it shows as "Fastboot gadget" under other devices
I've downloaded drivers from Alcatel website in case it's a driver issue but on the list of model numbers during setup mine (5003D_EEA according to recovery screen) doesn't show.
I do see a bunch of websites allegedly offering these specific drivers but assume it's risky to download from anywhere other than Alcatel official site.

BrickAlcatel said:
I've tried
Code:
fastboot getvar all
this results in <waiting for any device>
adb devices still shows no list of devices even though in Device Manager it shows as "Fastboot gadget" under other devices
I've downloaded drivers from Alcatel website in case it's a driver issue but on the list of model numbers during setup mine (5003D_EEA according to recovery screen) doesn't show.
I do see a bunch of websites allegedly offering these specific drivers but assume it's risky to download from anywhere other than Alcatel official site.
Click to expand...
Click to collapse
It seems to be a reliable site https://www.androidusbdrivers.com/alcatel-1-usb-drivers/ it offers the 4 different drivers needed covering all the modes that your device can enter to.
I would recommend mainly two things:
- Uninstall/remove firstly all the drivers that you don't use, it could be something for an old android/tablet that you don't use anymore.
- Don't swap the cable data from/for other device, any of them have its own type of connection, use the same proper cable data for only one device.
From there the typical first step in fastboot is just typing
Code:
fastboot devices
], if the message is "waiting for device" then it's not working.

hi im having the exact same problem, but cant get out of this. Could somebody maybe help me? How did you eventually fixed it? kindregards

Question [SOLVED] RN10 5G Hard-bricked after installing GSI

Hello fellas,
The other night I got frustrated over some bugs on MIUI 13 on my RN10 5G and decided to install MIUI 12.5. I did everything right and the FW downloaded from miuirom.com. It's EU, It's the correct, but it wouldn't boot.
Decided to flash PE, because I've used it and it was cool and all, but when it finished, I did the usual - Recovery-Wipe Data-Reboot.
Here's the problem - it took more than 15s on the Redmi boot screen (before it took less than 10s) and after that it restarted. OK, maybe something went wrong. After restarting it boots to a black screen, stays on it for about 3-5s and restarts again. Cool, it's in boot loop. But it doesn't display the boot screen, can't access recovery and holding for recovery immediately halts the phone and it turns off.
My question - other than getting a new phone, is there a way to... like, un-brick the phone?
Something a bit useful might be, that I've used a VNDKLite version of PE, and if I understood right, it partitions the phone in some weird way, to keep the vendor's data and the OS separately. Maybe this is causing it? I don't know.
P.S. If there is something with solidering, like changing the Flash Memory chip, I'm out...

Here are some steps you can take to try to fix your phone:
Try to enter recovery mode: Depending on your phone model, you can try to enter recovery mode by holding down a combination of buttons. Once in recovery mode, you may be able to reset your phone to factory settings, which can help fix the issue.
Contact the manufacturer: If your phone is still under warranty, contact the manufacturer for support. They may be able to provide a solution or offer a repair or replacement
Seek help from the developer community: If you installed PixelExperience through a custom ROM, try seeking help from the developer community on forums or social media. They may have experience with similar issues and be able to provide assistance.
Consider professional repair: If none of the above options work, you may need to take your phone to a professional repair service. They may be able to diagnose and fix the issue, but be aware that this can be expensive.
In any case, it's important to be cautious when installing custom ROMs on your phone, as they can potentially cause issues if not installed correctly. Make sure to research thoroughly and follow instructions carefully to minimize the risk of bricking your phone.

@timjohnson2584 Thanks for the help! That's also a quick update.
So, the first one, I literally cant enter recovery nor fastboot. Acidentally I've entered a secret menu, that gave me the option between Recovery, Fastboot and normal. VolUp to change choice and VolDown for confirm. I wasn't able to access it again, but it doesn't matter, because when I was in it, i chose fastboot and it restarted into the same boot loop. Second - the phone is unlocked, re-flashed with, i dont even know what anymore, and I've disassemble it to change the screen, so the warranty is no no. The 3rd - nothing personal, but "...that's why I'm here". Fourth - I don't really have the finances for a technician and just want to repair it @ home, sooo...
Thanks anyways

Again, a quick update!
I found out that the menu i have accessed may have been the weirdass BROM menu, because after some search I've found out how to enter it. When the screen lights up, hold PWR and VolUp, till the screen turns off, and then immediately hold VolUp and VolDown. When screen lights up, no matter what it enters the mode. Sadly, just hanging there doesn't give me access trough adb nor fastboot and if i choose fastboot it restarts. But if it's normal or recovery, it vibrates, freezes, disappear and halts.

Hey guys, another quick update that might frustrate some people. I've left it for the night to boot-loop reboot and stuff and today when I tried powering it up, it wouldn't show signs of life. When connected to this PC, from which I'm sending this, and hold any combination of buttons, it shows in the Comp Mgmt for a brief second as COM3 Serial Port. That's cool, at least its recognizing it, but if before there was at least backlight on the screen, this time it's fully blank - no picture, no backlight, no sh*t. If someone asks, the weirdass way Xiaomi did it is the phone's daughterboard for charging is connected to the screen, AND THEN it all connects to the mainboard. If it chargin', then it ain't disconnected - that's how I look at the situation. :/
P.S. Also, I don't think it's a problem, but I've disconnected the speaker and vibrator motor, so I can sleep peacefully.

someone here has had a similiar issue with you but differently recovered without using brom
anyways, i took a glance at your issue, seems like you are still in brom right?
install MiFlashPro, you will need it to fill the Download-Agent in sp tool (see what the spaces means below)
then, download any miui rom from any website (my favorite is mifirm.net, it downloads faster)
extract the rom folder. now open sp tool.
now you will need to fill out 3 spaces:
download-agent (DA for short), scatter-loading file & authentication file.
DA is to have access to the devices internal storage, scatter-loading shows you the mapping of the partitions it will flash on the mtk & authentication is just MTK protection for newer mtk devices that you need to be able to flash (its also used to successfully flash, but you still need to bypass it somehow, as you require a Mi Account able to do BROM flashing, see below as you follow the thread)
to find the DA, it is always in the MiFlashPro installation location, so ...\MiFlashPro\. Access that folder, open up "\SP_Flash_Tool_V5" folder, and you will find a file named "MTK_AllInOne_DA.bin", use it as the DA.
to find the authentication file, its located in the same path of the DA, so ...\MiFlashPro\SP_Flash_Tool_V5\, and you will find a file named "auth_sv5.auth", use it as the authentication file.
finally, to find the scatter-loading file, it is in the rom folder you extracted, so ...\camellian_xx_xxxx_images_VXX.X.X.X.xxxxx_XXXXXXXX.XXXX.XX_XX.X_xxxxxl\ (the X's represent your MIUI version you downloaded). the scatter-loading file is always located in the folder "images", so \camellian...\images\, and you will find a text file named "MT6833_Android_scatter.txt", use it as the scatter-loading file.
Now, you need to edit the "MT6833_Android_scatter.txt", or else when you use to flash you will get this error:
{
"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"
}
Open it (located at your MIUI ROM folder at \images), then use the locate tool to find "combo_partsize_check: true". You will probably find a few lines set as true, just replace every one with false (if it doesnt find it, just put "combo_partsize_check", but you will waste more time finding those that are set to true)
Alright, we finished our sp tool settings. now we have to bypass MTK Auth protection.
(Dont close sp tool yet!)
Ive annexed the tool below (mtkauthbypass.zip), download it and extract it.
It looks like this:
After you are ready, press the "Disable Auth" button, get your hands on the phone and press at the same time the VOL+, VOL- & POWER button, till you see prompts appearing in the blank (i dont have a screenshot to show how it looks like, sorry)
After it is finished and was successful, now go back to sp tool, and click "Download" asap.
Now wait for it to flash, maybe 5-15 minutes, and some time to boot, and done, your phone is alive again.
if anything didnt work post about it asap so i can help
(ps: if you get this, its a easy procedure to repair your bricked mtk, and you will get used to it quickly)

OK, thanks, I'll try that. But just to ask, do I have to stay in this BROM mode with options on blank screen while doing this, or select fastboot, recovery, normal first?

bg0169 said:
OK, thanks, I'll try that. But just to ask, do I have to stay in this BROM mode with options on blank screen while doing this, or select fastboot, recovery, normal first?
Click to expand...
Click to collapse
well, not necessarily. only when you get to the bypassing, because brom will automatically restart if theres no command taken in a few seconds

OK, now I have a problem. All my programs are ready, the phone is in BROM mode, but the PC is not recognizing it. It's not from the cable and it doesn't appear in Device Manager.

bg0169 said:
OK, now I have a problem. All my programs are ready, the phone is in BROM mode, but the PC is not recognizing it. It's not from the cable and it doesn't appear in Device Manager.
Click to expand...
Click to collapse
Wait a few moments, i think i have the mtk brom drivers for it, sorry for the wait

No problem, have your time

bg0169 said:
No problem, have your time
Click to expand...
Click to collapse
There you go its attached, try them. Should work

OK, update again, again, again... Now I even have a picture on my phone in BROM mode and what's happening even with the drivers from above:
Down there is the phone and on the screen is SP flash ready in the background and the MTK bypass tool. Also, PLEASE don't question the webcam, I know

Also here is what the Dev Mgmt sees. It's not showing even as serial port (the COM3 port from which it showed during the bootloop)

bg0169 said:
OK, update again, again, again... Now I even have a picture on my phone in BROM mode and what's happening even with the drivers from above:
View attachment 5860261
Down there is the phone and on the screen is SP flash ready in the background and the MTK bypass tool. Also, PLEASE don't question the webcam, I know
Click to expand...
Click to collapse
BROM mode is not that!
BROM is accessed by pressing down VOL+, VOL- & POWER all at the same time when device is turned off or rebooting, while connecting it to the pc, and BROM does not display anything, not even the LCD lights up, you just got to know whenever it is in BROM by your computer
Let the device reboot (select any mode from the list), and right as it reboots, press down all of the buttons, and connect the phone simultaneously.

OK, so when I plug the phone into my laptop and start holding all the buttons for eternity, it just connects and disconnects in 1sec.
I managed to capture it while doing it and:
, yeeaaahhhh, no,
I think it's entering BROM mode from what you've said, but that's what is happening. It recognizes it, but doesn't stay in. If i let go on the buttons, the phone just starts restarting again.

bg0169 said:
OK, so when I plug the phone into my laptop and start holding all the buttons for eternity, it just connects and disconnects in 1sec.
I managed to capture it while doing it and:
View attachment 5860273, yeeaaahhhh, no,
I think it's entering BROM mode from what you've said, but that's what is happening. It recognizes it, but doesn't stay in. If i let go on the buttons, the phone just starts restarting again.
Click to expand...
Click to collapse
press the "disable auth" button, and then connect it into BROM again, then it will bypass normally
it restarts because its not receiving any command, its normal

OK, I'll try it out in a moment... Thanks!

OK, even if u want, I have a screen capture. I open the tool, click bypass, connect the phone, and hold all the buttons. BUUUT it just keeps connecting and disconnecting. Always! Even with the drivers! Restarted my PC, same s**t! Now I'm pissed off a lot! Are you sure this is the only way, am I doing something wrong? I saw your "How to Guide" thread and followed everything and it's the same.

bg0169 said:
OK, even if u want, I have a screen capture. I open the tool, click bypass, connect the phone, and hold all the buttons. BUUUT it just keeps connecting and disconnecting. Always! Even with the drivers! Restarted my PC, same s**t! Now I'm pissed off a lot! Are you sure this is the only way, am I doing something wrong? I saw your "How to Guide" thread and followed everything and it's the same.
Click to expand...
Click to collapse
i see the problem
its the driver. well, not exactly the driver
it seems like its a issue from the phone's side. but its normal! it also happens to me every time i try to bypass it
bg0169 said:
OK, so when I plug the phone into my laptop and start holding all the buttons for eternity, it just connects and disconnects in 1sec.
I managed to capture it while doing it and:
View attachment 5860273, yeeaaahhhh, no,
I think it's entering BROM mode from what you've said, but that's what is happening. It recognizes it, but doesn't stay in. If i let go on the buttons, the phone just starts restarting again.
Click to expand...
Click to collapse
just like you show here, the port is not working (error symbol), so clearly it cant detect the phone to be able to do any commands
i tried bypassing to see just now, and yes, it also shows the same problem as you, the error symbol, however if you have the patience to retry lots of times, trying to bypass it, then its the solution for it.
what you can try is just keep bypassing lots of times till you get it.. thats it, i hope