Hi,
I flash unnoficial twrp into my doogee s88 pro using this command
Code:
fastboot flash recovery twrpname.img
Then I dind't flash Vbmeta and now my doogee is in infinite loop (is restarting all the time) and I can't acces to recovery mode pressing volume up + power either volume down + power.
I tried to connect to PC to send fastboot commands but doogee is in automatic reboot all the time and I can't send any command.
In the screen appears:
Orange state
Your device has been unlocked and can't be trusted
Your device will boot in 5 seconds
With SP Flash Tool I can format whole flash and now I'm try installing a ROM stock with SP Flash Tool.
I can format whole flash connecting USB cable in power on exact moment, and SP Flash Tool has been able to format flash.
Now I have problem with Download the stock firmware. I download from differents websites but in all situations SP Flash Tool have an error 50005 (firmware not comtabile) and 10001 (DA or Auth virification failed)
I keep trying to revive the doogee
My S88pro is also in infinity loop. I didn't do nothing. From one day to another it loops. Does anyone has a solution. Need to access a wallet. Can't find my private keys.
bambo1543 said:
My S88pro is also in infinity loop. I didn't do nothing. From one day to another it loops. Does anyone has a solution. Need to access a wallet. Can't find my private keys.
Click to expand...
Click to collapse
The first task that you don't have to do is FORMAT with SP Flash.
Although mobile are in infinete loop you can flash original firnware with SP Flash tool, but you lost everithing.
With SP Flash you can read all flash memory and separate the different partitons, but I try many times unsuccessfully.
What is the type of nand memory you have? Emmc or ufs?
Related
After Lollipop Update of my phone (Lava iris icon), I had to root in again and while trying to root it from custom recovery, I bricked it ( may be the recovery is not compatible). So,it stuck in the bootloop and by pressing Power and volume buttons, I am only able to access Fastboot mode. I downloaded the stock rom of device and tried to flash recovery , boot etc. with fastboot commands, but it is still in bootloop. I also tried to flash cwm recovery (though it is not available for device, I chose the nearest one), but in vain.
When I try to flash system partition, it gives error while erasing system <unknown command> (may be due to fact that phone is not rooted as of now). Also, SP flash tools are not recognizing the device and I cant use adb commands also. So, I am stuck with only fastboot in hand and I have stock rom as well as lollipop update, but i am unable to use these due to errors. Can anyone help? I will be very thankful for an advice. Thanks in advance.
rishab951 said:
After Lollipop Update of my phone (Lava iris icon), I had to root in again and while trying to root it from custom recovery, I bricked it ( may be the recovery is not compatible). So,it stuck in the bootloop and by pressing Power and volume buttons, I am only able to access Fastboot mode. I downloaded the stock rom of device and tried to flash recovery , boot etc. with fastboot commands, but it is still in bootloop. I also tried to flash cwm recovery (though it is not available for device, I chose the nearest one), but in vain.
When I try to flash system partition, it gives error while erasing system <unknown command> (may be due to fact that phone is not rooted as of now). Also, SP flash tools are not recognizing the device and I cant use adb commands also. So, I am stuck with only fastboot in hand and I have stock rom as well as lollipop update, but i am unable to use these due to errors. Can anyone help? I will be very thankful for an advice. Thanks in advance.
Click to expand...
Click to collapse
is there a partition file with the stock rom you downloaded?
if so, try to flash that first with fastboot.
Hello,
I tried to flash my Alcatel ideal 4060a with custom rom following by the instructions in Thread. I got Install successful screen
but it is still booting in to TWRP recovery. when i try to reboot with bootloader option it is hanging at logo only for 30+ minutes. can anyone please help me out in this ? Thanks in advance
[email protected] said:
Hello,
I tried to flash my Alcatel ideal 4060a with custom rom following by the instructions in Thread. I got Install successful screen
but it is still booting in to TWRP recovery. when i try to reboot with bootloader option it is hanging at logo only for 30+ minutes. can anyone please help me out in this ? Thanks in advance
Click to expand...
Click to collapse
I realize this is a very old post, but in hopes that the information will be helpful to any current device owners, I'll address the question:
The AT&T Alcatel IDEAL (4060a) ships with a fully.unlocked bootloader. As such, installing TWRP custom recovery is simple to do once root of the stock OS is attained. NOTE: fastboot mode has been disabled on the 4060a by Alcatel (TCL). Trying to boot to bootloader mode from recovery or using the command
adb reboot recovery
from a terminal or command prompt will only reboot the device. Without fastboot mode, recovering a bricked device is very problematic unless the device will boot into TWRP recovery mode. From TWRP, a stock Android 5.1.1 ROM can be installed which will recover your device to its stock factory state. In the unfortunate event your device is hard bricked (unable to boot into either the OS or TWRP recovery mode), your only option is to push stock firmware to the device using a firehose programmer via Qualcomm HS-USB QDLoader (9008 mode), also known as Emergency Download Mode (EDL).
Please !!!, where do I find the "firehose programmer file" for the AT & T ALCATEL 406
AeonFlux1603 said:
I realize this is a very old post, but in hopes that the information will be helpful to any current device owners, I'll address the question:
The AT&T Alcatel IDEAL (4060a) ships with a fully.unlocked bootloader. As such, installing TWRP custom recovery is simple to do once root of the stock OS is attained. NOTE: fastboot mode has been disabled on the 4060a by Alcatel (TCL). Trying to boot to bootloader mode from recovery or using the command
adb reboot recovery
from a terminal or command prompt will only reboot the device. Without fastboot mode, recovering a bricked device is very problematic unless the device will boot into TWRP recovery mode. From TWRP, a stock Android 5.1.1 ROM can be installed which will recover your device to its stock factory state. In the unfortunate event your device is hard bricked (unable to boot into either the OS or TWRP recovery mode), your only option is to push stock firmware to the device using a firehose programmer via Qualcomm HS-USB QDLoader (9008 mode), also known as Emergency Download Mode (EDL).
Click to expand...
Click to collapse
Please !!!, where do I find the "firehose programmer file" for the AT&T ALCATEL 4060a? My Phone is hard Bricked.
Hi All,
I had my Redmi 9A flashed and was using the original stock rom unlocked and rooted. Since I ran into some issue with applications failing to start I decided to reflash with the OTA update zip. Now that I did that the phone keeps rebooting anc connecting it to a PC with all the drivers available including MTK, QUALCOM the system won't detect the phone and the phone will never boot into bootloader, or recovery or EDL mode.
I have tried various ADB and Fastboot commands but they would work only when the system detects thd phone and the phone does not reboot.
Has anyone come across such issues ?
MiUnlock tool failed
MiFlash tool failed
Sp flash tool failed
All other flash tools failed too
hola ya encontraste alguna solución estoy en el mismo caso
have you tried holding power button + vol down button till fastboot shows up?
Answer to the first post
when you have rooted your phone, it modifies the boot.img file, and the original MIUi ROM detects that, and bootloops
The fix its to flash vbmeta.img via fastboot, using the keys (power + vol down )
yes and neither fastboot with volume down nor recovery with volume up appears ... please have any suggestions or it will be that this device has no remedy
Hi,
I think I have the same issue: I tried to root and corrupted/incompatible vbmeta security, and device will continuously self-reset, will not enter fastboot, and no recovery.
I must remove battery to stop it from draining due to bootloop.
From what I searched, my guess, there is only one hope: to use the hardware test-pins to force EDL mode.
I found some info on EDL pins for many other devices (9c 9T... ) but not for 9A.
So please, if anyone knows, has the PCB layout, please post a picture and explain how to force enter EDL mode.
After that, I guess SP flasher can be used.
kukudro said:
Hi,
I think I have the same issue: I tried to root and corrupted/incompatible vbmeta security, and device will continuously self-reset, will not enter fastboot, and no recovery.
I must remove battery to stop it from draining due to bootloop.
From what I searched, my guess, there is only one hope: to use the hardware test-pins to force EDL mode.
I found some info on EDL pins for many other devices (9c 9T... ) but not for 9A.
So please, if anyone knows, has the PCB layout, please post a picture and explain how to force enter EDL mode.
After that, I guess SP flasher can be used.
Click to expand...
Click to collapse
I was able to revive it by downloading the correct image with sp flash tools, it turns out that my device after investigating a little was from a Russian region, and with that image it was like new, what a scare
MaykoDiaz7 said:
I was able to revive it by downloading the correct image with sp flash tools, it turns out that my device after investigating a little was from a Russian region, and with that image it was like new, what a scare
Click to expand...
Click to collapse
and you used EDL test-pins to force EDL mode? or you entered from fastboot reboot EDL ?
for me is auto resetting continuu, so can't enter fastboot..
Good morning!
While attempting to flash a stock MIUI 10 ROM into my Xiaomi Redmi Note 7, to downgrade back to Android 9.0 due to some app compatilibty issue, I messed up big time and my phone is now stuck in a loop where the screen turns on, nothing shows up, then it restarts, going off for a few seconds and turning on again.
Power Button + Volume UP successfully brings me to the stock recovery 3.0 from xiaomi.
Power Button + Volume DOWN fails to bring me to the fastboot mode.
If I select the Connect with MIAssistant in the recovery the phone will show up as "sideloaded" after using the command adb devices, but the MIPCSuite app does not see it and the command adb restart bootloader also fails to bring up the fastboot mode, it just gets stuck in the loop again.
More context on what went wrong and caused this: I followed an online tutorial to flash a rom using the MIFlash app, so I unlocked the bootloader and tried to flash the rom usin xiaomi's tool. I got a failed to check sparse crc error code and it went downhill from there when I tried to fix things reading multiple threads on the issue. I tried deleting some lines from the flash_all.bat file and tried to flash it again but then the flashing process went seemingly forever so I aborted the operation and now this loop happens. I tried a few more times but with no success.
The first time I tried to use the tool I used the clean all and lock option so I'm not certain if the miflash tool locked the bootloader regardless of the outcome of the flashing attempt.
Is there hope? Can I fix this phone if I only have access to stock recovery and nothing else (although it shows up in adb devices but can't get into fastbootmode) ?
Thanks a lot to anyone who took the time to read and possibly help.
Both ADB and Fastboot are Android-side launched by device's bootloader. If you can't enter Fastboot mode then my guess is there is something is wrong with curently installed Android.
BTW: If you lock device's bootloader then bootloader attempts to load device's Stock ROM.
jwoegerbauer said:
Both ADB and Fastboot are Android-side launched by device's bootloader. If you can't enter Fastboot mode then my guess is there is something is wrong with curently installed Android.
BTW: If you lock device's bootloader then bootloader attempts to load device's Stock ROM.
Click to expand...
Click to collapse
I see.
What can I do to try to fix this issue?
I finally managed to fix it through the Emergency Download Mode (EDL). It requires Xiaomi Authentication which I bypassed using this guide: https://www.droidwin.com/fix-mi-account-authorization-unbrick-xiaomi-edl-mode/
With that setup I flashed a stock rom using the MiFlash tool.
I tried installing the pixel experience rom and after I flashed the aex recovery before side loading the ROM, it went into bootloop and ended up with the stock recovery and ROM. I tried to flash TWRP recovery and go a message that the the boot/recovery image is destroyed so I tried to flash the stock boot image back and since then I am not able to get it out of fastboot mode.
I tried everything, flashing the recovery again, both stock and TWRP and also tried using the flash-all to flash the stock ROM back but nothing seems to be working.
When using the flash-all, I get 'partitions not found' and 'flashing is not allowed in critical partitions' error.
I even tried msmtool but I am not able to get my phone into edl mode for the tool to detect it.
Tried holding the vol+/vol- and connecting the usb cable but to no vain, the tool does not seem to detect it.
I even tried using the all-in-one tool but my phone is not getting detected when it is turned off but it gets detected when it's in flashboot mode from where I cannot enter edl.
Let me know if there is anything I can do to fix it? Or if taking the phone to the official service center help?
Can you reboot from fastboot to edl by entering fastboot reboot-edl? Or similar, don't know exactly anymore
Alternatively see if this can help you getting into edl: https://forum.xda-developers.com/t/guide-how-to-reboot-to-edl-from-fastboot.3394292/