Long time ago (almost one year), I there was an OTA update, so I decided to update. Result: No booting anymore.
I try to push the bottom for 1 to 5 seconds and nothing. The watch only shows up the Amazfit triangle logo when I push the button for 10 seconds, and after 3 seconds, it dissapears.
I am able to access via adb and boot it into fastboot mode. It is unlocked, and I followed the Unbrick tutorial, and tried to update the system, but no luck.
Any clue about what can I do? I would appreciate any help on this. I bought this watch to Banggood june last year, and I manipulated it, so I don't expect a return if I send it.
This is the best guide you can follow, as it will flash everything again even if you have a null SN:
https://forum.xda-developers.com/smartwatch/amazfit/guide-restore-null-sn-locked-t3775998
If you have a valid SN and everything seems OK in fastboot mode, then just skip the misc.img part.
It seems that many watches have a damaged internal storage, that's what cause problems like the one you have. You have to try to flash other firmwares and erase the data partition (as explained in step 9 of the tutorial) until you can boot, and hope it stays working after that. Unfortunately there isn't much you can do besides that.
Related
Hello,
I'm a little bit at a dead end after trying so much things.
My phone already was in repair for three times. The first time the replaced the mainboard because of a defective earspeaker. Before sending it in I was on the latest available Stock OTA update for my ROM (2.3.4, Retail DACH).
After I got it back after the first repair, I started to get trouble with GPS. Then also the touchscreen started to get a dead area and I send it in for repair the second time. I mentioned the GPS problems aswell, but they just changed the screen.
Then I send it in for the third time and now I have the third mainboard in my phone.
Unfortunately GPS still didn't work. Shows satelites, even sometimes gets a fix for some seconds, but the GPS Test App never reported a value for Accuracy.
Since I didn't want to send it in a again I started to search and found that this seems to be related to libnmea.so.
So I rooted the phone, exchanged the file, checked the permissions and tested it after reboot. Phone showed satelites, but the values for the satelites never went above 30 and it didn't get a GPS-fix within the 20 minutes I was testing it outside in the cold
So I followed another advice to flash a newer radio (N_01.77.36P) just to see if that helps. This required me to unlock the bootloader and install CWM Recovery, since this Radio I found was a fruit cake.
GPS isn't still much better now though... I drove a distance of 350 km (from work back to my home office) with always getting some satelites (approx. max. 7 at a time) displayed but only on the last 40 km I got my first fix, which then also displayed accuracy, so it might have helped a bit, I thought, but GPS fix only worked until I rebooted the phone the next time, since then it seems I didn't drive far enough to get a fix again...
Then I discovered the next problem...
Since unlocking killed my settings I had to make them again. My Exchange ActiveSync at work requires DeviceEncryption, and when the phone rebooted to enable encryption CWM Recovery came up with an error, that it doesn't recognize the parameter, and the phone didn't get encrypted and so I was without my contacts, calender and mails...
I couldn't find a way in the forums to restore the stock recovery, so I decided to reflash the stock-image with SBF.
Followed the guidance to delete cache, davlik cache and factory reset via cwm, and to erase different partitions using fastboot before using RSD Lite.
RSD Lite was 5.7 and the Motodrivers are 5.5.0, running on Win8 64bit.
RSD Lite flashed until 99% and then failed when trying to restart the phone in BP Bypass mode (0x70BE), and the phone was stuck with Error "Failed to boot 1".
I tried the ROM 1FF-olympus_emara-user-2.3.4-4.5.2A-74_OLE-31-release-keys-signed-rtdach.sbf
Then I found hints, that others were in the same boat and were able to recover from this error flashing this image
1FF-olympus_emara-user-2.3.4-4.5.2A-74_OLE-31.1-release-keys-signed-NonEFIGSRetail-EU.sbf
But this didn't help me either, even after more retries. I also tried flashing on three computers and even tried to flash under linux using a Knoppix Live CD. Flash was always performed until the end, but after the last reboot I had the failed to boot 1 again.
Since I didn't find any more usefull guidance of things I could try, I thought "give it another try with the bootloader from the unlock (intl-fix-try1.sbf), can't get really worser now" and so did I and voila device is back and running.
Tried it again to flash a full sbf and came back to the same error, flashed the bootloader.sbf and it's working again...
After that I rooted it again and replaced the libnmea.so file again. But didn't have chance to test it yet, if this helped in any way...
I don't have much hope and think, that I 'll need to send it back to repair again, so again my question, is there any way, to get rid of the "Unlocked" of the bootscreen?
I can think of two possibilities, maybe there is a patched version of this intl-fix-try1.sbf available, that doesn't display this word or there is a way to really get back to the stock bootloader...
Best Regards
Mario
Exactly whats ur problem?????can u be more specific !!!
Sent from my MB860 using Tapatalk
Currently my problem is having the word "unlocked" during boot. Guess they'll refuse or charge for service, when they see it, when I send it in for repair once again...
GPS is still not working as it used to before the first repair. It sees some satelites (max. observed signal strength in GPS Test app yesterday was 23), but doesn't get a fix, even after 30 minutes.
Mario1976 said:
Currently my problem is having the word "unlocked" during boot. Guess they'll refuse or charge for service, when they see it, when I send it in for repair once again...
GPS is still not working as it used to before the first repair. It sees some satelites (max. observed signal strength in GPS Test app yesterday was 23), but doesn't get a fix, even after 30 minutes.
Click to expand...
Click to collapse
Mario1976,
I am encountering a similar problem with my AT&T Atrix 4G running Fruit Cake 4.5.141 with BL unlocked.
I cannot get the Data Encryption to work with CWM Recovery 5.8.1.8.
I'm beginning to think that I'll need to restore the stock Android Recovery to be able to get the Data Encrytion to work.
So far, my previous attempts at flashing the stock 4.5.141 SBF using RSDLite has met with the sec_exception: febe, 35, 35 error.
I also tried to use another set of instruction for restoring stock recovery onto another device on my Atrix but to no avail:adb push install-recovery.sh /data/local
adb shell
su
mount -o rw,remount /system
cat /data/local/install-recovery.sh > /system/etc/install-recovery.sh
dd if=/system/recovery-from-boot.p of=/dev/block/mmcblk0p1Konker
Update:
I finally figured out that the sec_exception: febe, 35, 35 error meant that the SBF was not intended for the device. That led me to suspect that the system board is not an original AT&T US board. I gave an Asian stock SBF a try & viola! The phone was successfully restored to factory stock ROM with stock bootloader & the Unlocked words removed from the boot screen. Device encryption is also working without any issues.
Here's the full story: a few months ago I unlocked the bootloader of my Huawei Y300-0100, rooted it and installed TWRP. Some days ago I wanted to try a custom ROM but I made the mistake of wiping system and cust along with the caches and data, I didn't really notice it as I did it too fast (without reading) and attempted to install the ROM, but the phone froze while doing so.
I turned the phone off and turned it back in to find a green screen with two rectangles, one red and one blue.
After many days of searching on the internet I found that the only way to fix my phone is to flash the stock ROM by copying dload/UPDATE.APP to the root of the SD card, and turning on the phone while pressing vol+-, but the update stops at the second step.
Taking a look at the update log I see that the error is related to CRC, which means the UPDATE.APP has somehow been modified, but that's not true as I have tried both the stock ROM that came with the phone and the official update from Huawei, as well as many other updates, and they all give me the same CRC update.
If I attempt the update without an SD card the phone goes into a pink/purple-ish screen, connecting the phone to the PC, Ubuntu recognizes it as a GSM device, but there's something strange, when I type lsusb in the terminal I see this:
Code:
Bus 001 Device 021: ID 12d1:1035 Huawei Technologies Co., Ltd. U8120
Which is completely incorrect as this phone is not an U8120.
I have tried many different methods, such as doing the procedure without a battery or using more than 5 different SD cards and now I have no idea what to do next, can anyone help me out here?
Hi hello
So here’s a head scratcher I hope someone can help me with that won’t involve replacing my main board.
Got myself the p20 lite (ANE-LX1 C432) - Single Sim.
I unlocked the bootloader with Huawei just before they stopped handing out the codes. All was good and happy with the world.
Rooted with Magisk and Was busy messing around With Termux, Linux deploy, Mobile Terminal and some pretty basic stuff. I’ve been out of the android scene for a while so was getting reacquainted with the scene.
Anyway. I was messing around in the terminal in a root shell just fixing basic permissions after messing up my termux environment as root. Phone randomly rebooted (I must’ve messed with the wrong folder -no idea which) came back on and my IMEI and baseband were gone.
No worries, I thought. Happened tonnes of times with my previous Devices (looking at you Samsung) just a quick restore or flash and all will be happy again.
Yeah, not quite.
Note that up until this point I hadn’t touched the system partition (probably besides the mobile terminal mishap -no idea)
So over the last week or so I have tried everything. Restore from Twrp backup. Flashed stock through fastboot, through erecovery. Those flashed ok but didn’t fix it.
Putting numerous different update.app FULL & OTA updates in dload folder on SD and internal all failed. Only used my builds version of course and only ones firmware finder deemed compatible/available
Then I got desperate (read: stupid) Decided to take the unpacked firmware files and flash whichever ones twrp would let me. First tried just the modem files. Didn’t help. Then just went through the list and flashed all I could.
I think the kicker came in when I installed the Trustfirmware.img because once I did that I rebooted and now I was stuck in an endless boot loop. No way to get into recovery. Not with their ton combo nor adb/fastboot.
I still had access to fastboot at this point at least and started doing every single thing suggested all over the net just trying to get back to stock.
Tried the unbrick option on The Huawei Multi-Tool. Flashed ok. Phone still wouldn’t boot. Did it a few times with 3 approved versions. Nothing. Only access to fastboot otherwise I was in a boot loop with error mode error no 15 and the verification failure (Attached below)
Last thing I tried after reading online was to relock my boot loader and flash stock. So I locked it with Huawei Multi-Tool. Reboot......
Now I don’t even have access to fastboot. My PC’s (windows and Linux) don’t even acknowledge it and holding volume down in all the weird and wonderful ways and times does nothing. All I get is startup Huawei Logo, Error Mode as per pic Below and then reboot. That’s it.
I’m assuming it’s trying to do a factory reset after relocking the bootloader (if it even locked properly, can’t check) but it can’t get into recovery/erecovery. I dunno ?
That’s my essay of where I’m at. Warranty is already void so not an option and I don’t want to buy a new mainboard (may as well buy a new phone).
So here I am. Is this my life now or does anyone have any magic tricks to possibly suggest?
Pyrolectic13 said:
Hi hello
So here’s a head scratcher I hope someone can help me with that won’t involve replacing my main board.
Got myself the p20 lite (ANE-LX1 C432) - Single Sim.
I unlocked the bootloader with Huawei just before they stopped handing out the codes. All was good and happy with the world.
Rooted with Magisk and Was busy messing around With Termux, Linux deploy, Mobile Terminal and some pretty basic stuff. I’ve been out of the android scene for a while so was getting reacquainted with the scene.
Anyway. I was messing around in the terminal in a root shell just fixing basic permissions after messing up my termux environment as root. Phone randomly rebooted (I must’ve messed with the wrong folder -no idea which) came back on and my IMEI and baseband were gone.
No worries, I thought. Happened tonnes of times with my previous Devices (looking at you Samsung) just a quick restore or flash and all will be happy again.
Yeah, not quite.
Note that up until this point I hadn’t touched the system partition (probably besides the mobile terminal mishap -no idea)
So over the last week or so I have tried everything. Restore from Twrp backup. Flashed stock through fastboot, through erecovery. Those flashed ok but didn’t fix it.
Putting numerous different update.app FULL & OTA updates in dload folder on SD and internal all failed. Only used my builds version of course and only ones firmware finder deemed compatible/available
Then I got desperate (read: stupid) Decided to take the unpacked firmware files and flash whichever ones twrp would let me. First tried just the modem files. Didn’t help. Then just went through the list and flashed all I could.
I think the kicker came in when I installed the Trustfirmware.img because once I did that I rebooted and now I was stuck in an endless boot loop. No way to get into recovery. Not with their ton combo nor adb/fastboot.
I still had access to fastboot at this point at least and started doing every single thing suggested all over the net just trying to get back to stock.
Tried the unbrick option on The Huawei Multi-Tool. Flashed ok. Phone still wouldn’t boot. Did it a few times with 3 approved versions. Nothing. Only access to fastboot otherwise I was in a boot loop with error mode error no 15 and the verification failure (Attached below)
Last thing I tried after reading online was to relock my boot loader and flash stock. So I locked it with Huawei Multi-Tool. Reboot......
Now I don’t even have access to fastboot. My PC’s (windows and Linux) don’t even acknowledge it and holding volume down in all the weird and wonderful ways and times does nothing. All I get is startup Huawei Logo, Error Mode as per pic Below and then reboot. That’s it.
I’m assuming it’s trying to do a factory reset after relocking the bootloader (if it even locked properly, can’t check) but it can’t get into recovery/erecovery. I dunno ?
That’s my essay of where I’m at. Warranty is already void so not an option and I don’t want to buy a new mainboard (may as well buy a new phone).
So here I am. Is this my life now or does anyone have any magic tricks to possibly suggest?
Click to expand...
Click to collapse
Check the second post in this thread:
https://forum.xda-developers.com/honor-7x/help/help-stuck-error-mode-screen-t3735067
kilroystyx said:
Check the second post in this thread:
https://forum.xda-developers.com/honor-7x/help/help-stuck-error-mode-screen-t3735067
Click to expand...
Click to collapse
Thanks for this.
The battery discharged fully about two days ago.
I haven’t tried plugging it in and out as/if it turns on immediately (though even though it shows dead without charger it still comes on immediately).
I’m gonna get a weaker lower amp charger and see if that maybe helps. Fml ?
***UPDATE***
Been at it for hours. Battery is completely flat. But h second I plug it in the the Black Huawei logo comes up ten a few seconds later it’s on the same error screen for a little longer then boot loops like that constantly.
The error isn’t the same as the post in that link though. And I am FRP unlocked.
Eh.
Pyrolectic13 said:
Thanks for this.
The battery discharged fully about two days ago.
I haven’t tried plugging it in and out as/if it turns on immediately (though even though it shows dead without charger it still comes on immediately).
I’m gonna get a weaker lower amp charger and see if that maybe helps. Fml ?
***UPDATE***
Been at it for hours. Battery is completely flat. But h second I plug it in the the Black Huawei logo comes up ten a few seconds later it’s on the same error screen for a little longer then boot loops like that constantly.
The error isn’t the same as the post in that link though. And I am FRP unlocked.
Eh.
Click to expand...
Click to collapse
I guess your previous error was related to ramdisk...
Now what is your current situation?
-What error is showed in the Error mode?
-Can you reach FASTBOOT&RESCUE MODE menu?
-What is your current recovery?
kilroystyx said:
I guess your previous error was related to ramdisk...
Now what is your current situation?
-What error is showed in the Error mode?
-Can you reach FASTBOOT&RESCUE MODE menu?
-What is your current recovery?
Click to expand...
Click to collapse
As it stands I cannot enter fastboot or recovery mode. Update from SD also doesn’t do anything. Battery is completely discharged. And if I leave it on the charger it doesn’t charge, only boot loops.
So with all that the ONLY thing this phone does now is:
- Starts up Showing Huawei logo
- Error Mode Screen with Func No: 15 (bl31 image) & Error No: 1 (security verify failed)
- Reboots
Ths happens whether it’s plugged into the pc’s usb or the charger. Tried all combinations of buttons too.
It has stock recovery as I flashed that back when trying to revert back to stock.
I lost access to fastboot after I locked the bootlaoder again using the Huawei Multi Tool. It’s like it trying to do the factory wipe that it usually would after locking/unlocking the bootloader but is unable to due to the error mode screen.
Sent from my iPhone using Tapatalk
Pyrolectic13 said:
As it stands I cannot enter fastboot or recovery mode. Update from SD also doesn’t do anything. Battery is completely discharged. And if I leave it on the charger it doesn’t charge, only boot loops.
So with all that the ONLY thing this phone does now is:
- Starts up Showing Huawei logo
- Error Mode Screen with Func No: 15 (bl31 image) & Error No: 1 (security verify failed)
- Reboots
Ths happens whether it’s plugged into the pc’s usb or the charger. Tried all combinations of buttons too.
It has stock recovery as I flashed that back when trying to revert back to stock.
I lost access to fastboot after I locked the bootlaoder again using the Huawei Multi Tool. It’s like it trying to do the factory wipe that it usually would after locking/unlocking the bootloader but is unable to due to the error mode screen.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
I see, it is really bad
My last hope is to be able to do a forced Firmware upgrade. Press power button and VOL + and VOL- simultaneously. Do you see the same as the attached image?
kilroystyx said:
I see, it is really bad
My last hope is to be able to do a forced Firmware upgrade. Press power button and VOL + and VOL- simultaneously. Do you see the same as the attached image?
Click to expand...
Click to collapse
Ah man, I wish it would even do that. It makes no attempt to even pretend to see the sd card update. If I hold all the buttons in it still only comes up with the error mode and reboots.
I popped it open and connected a charger up battery to see if that would help but it doesn’t.
Do you maybe know the pin layout on the inside or know where I could get schematics? Been looking everywhere.
I’m almost done building my own Jtag box and am hoping to bring it back to life by writing straight to the damn thing.
Sent from my iPhone using Tapatalk
Pyrolectic13 said:
Ah man, I wish it would even do that. It makes no attempt to even pretend to see the sd card update. If I hold all the buttons in it still only comes up with the error mode and reboots.
I popped it open and connected a charger up battery to see if that would help but it doesn’t.
Do you maybe know the pin layout on the inside or know where I could get schematics? Been looking everywhere.
I’m almost done building my own Jtag box and am hoping to bring it back to life by writing straight to the damn thing.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
That is sad!!!
With JTAG and schematics stuff I cannot help you.
What I found recently and it was new for me (I didn't tested yet) is a possibility to install firmware via "dload" folder, but to start installation the stock recovery have to be full functional.
If I found something interesting for you I'll post here.
kilroystyx said:
That is sad!!!
With JTAG and schematics stuff I cannot help you.
What I found recently and it was new for me (I didn't tested yet) is a possibility to install firmware via "dload" folder, but to start installation the stock recovery have to be full functional.
If I found something interesting for you I'll post here.
Click to expand...
Click to collapse
To my knowledge the recovery is installed. Well erecovery. It was working up until I locked the bootloader again and it went into a boot loop instead of doing the factory reset.
Is there any other way to force sd update other than with the dload folder?
Thanks for tying to help, I appreciate it.
Pyrolectic13 said:
To my knowledge the recovery is installed. Well erecovery. It was working up until I locked the bootloader again and it went into a boot loop instead of doing the factory reset.
Is there any other way to force sd update other than with the dload folder?
Thanks for tying to help, I appreciate it.
Click to expand...
Click to collapse
You can check the official documentation about that.
Please let us know how you solved this problem.
kumarsid7 said:
Please let us know how you solved this problem.
Click to expand...
Click to collapse
Still unsolved as of yet.
I’ve finished building my own version of the Riff/Octoplus box as well as a makeshift Jtag. I’m still trying to find and piece together some firmware files and other board software I think I need.
Also, if anyone has any idea where the test point is on this board I’d really appreciate you pointing it out. I cannot find the schematics or any solid documentation anywhere.
I will attach the pics I have of both sides of the board as soon as I get home.
Sent from my iPhone using Tapatalk
in first picture youle see many circles golden 2 smallest is testpoint good luck
Pyrolectic13 said:
Still unsolved as of yet.
I’ve finished building my own version of the Riff/Octoplus box as well as a makeshift Jtag. I’m still trying to find and piece together some firmware files and other board software I think I need.
Also, if anyone has any idea where the test point is on this board I’d really appreciate you pointing it out. I cannot find the schematics or any solid documentation anywhere.
I will attach the pics I have of both sides of the board as soon as I get home.
View attachment 4579956
View attachment 4579957
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
in first picture youle see many circles golden 2 smallest is testpoint good luck
well, try to restore your device using dload method. It needs you to copy the UPDATE.APP in dload folder of an external sd card(formated in NTFS format) and then just press both vol up+down along with power button for a few seconds. It will auto launch huawei e-recovery and will try to flash the UPDATE.APP you stored in ext sd card. This should definitely work.
Dload method doesn't need you to unlock your device or bootloader.
Maybe?
I know it’s a long shot but I still have this phone. If anyone maybe knows if there’s been a way to fix this as of yet please let me know. ?
Lol. Still got this damn thing. Been searching around and seen a few people reporting similar errors. Never find out if they ever solve it though.
So. Anyone maybe have any knowledge to share? Anything at all.
I don't know if you still have your device, but I had the exact same issue with a P10 (VTR-L09)
I was able to fix fastboot using https://github.com/mashed-potatoes/PotatoNV
That tool was designed to unlock the bootloader, but I noticed that It actually flashes a slightly modified version of fastboot.
PotatoNV can also unlock P20 lite bootloader, so you should give it a shot.
Good luck!
If it works, you should be able to flash stock recovery image and then restore the system using the dload folder.
you can Repair it with Software Testpoint and Full Bootloader Unlock ,and then flash a Board Software via Software Testpoint, that helps 100%!!!
use this Firmware Download ANE-LX1
use the Software with logins and you have all what you need.
you must start the Software Testpoint so!!
VIDEO : how to start Software Testpoint P20 Lite
than in Software Testpoint you flash the included Board Software with DC-Phoenix and after that use the included dload update via sdcard and eRecovery mode and your Phone is running!!!
I would unlock the bootloader via Software Testpoint with DC-Phoenix, then the FBLock is unlocked and you can flash as you wish!!!! And the great thing about it is that you don't need an UnlockKey either, you can then read this with HCU client software, the only thing that's stupid is that you need a time-based license for the two programs, which you have to buy.
HCU client download
https://hcu-client.com
DC Phoenix download
https://forum.dc-unlocker.com/forum/modems-and-phones/huawei/155916-dc-phoenix
Since I accidentally bought a 3-day license twice and my P20 Lite is now completely rooted on Lineage 19.1, I can give away 2 access data, which are still valid for 2 days.
you can edit your smartphone with it.
username : bl26457
password : kKncnkMj
username : bl26390
password : JDAZqnkN
Then I wish you a lot of fun with it, hope it helps you if someone else is active in this thread.
Good morning, everyone.
I have been frequenting this forum since the days when I had my trusty and beautiful HTC m8.
I find myself writing this post today looking for help: my uncle received from his friend a Doodgee x93 phone that was locked and whose unlock code he couldn't remember.
So I thought it would be simple, flash the ROM again so as to erase all the old data and reset the phone.
However, I found myself unable to do so.
After installing several versions of the drivers, in the various attempts, I used "SP_Flash_Tool_v5.1924_Win" with the only two firmwares available (any site always links to the exact same downloads) "Doogee_X93_MT6580_EEA_210902_10.zipper" and "DOOGEE-X93-Android10.0-20210902_user_20210902_R16.zipper".
The process stops at 2% without any error description.
In addition, the phone remains unusable, the screen does not turn on, and I cannot start recovery.
I then tried installing each file individually, and they all work except "super.img", which I assume are the android files given the weight of the 1.8Gb file.
Here I was able to turn it on, it did the boot android logo, then went to ">start fast boot.." but it never booted, surely because it couldn't find the rest of the files.
From the "MT6580_Android_scatter.txt" file, I tried editing the following.
"boundary_check: false" to true, but always to no avail.
I attach a screenshot and ask for your help, because I don't know how to proceed anymore, and all the online guides are the same copy/paste that don't work.
Thank you in advance
so you got a working phone and you bricked without doing research how to factory reset + reset FRP
Error: 3154 (S_DA_SDMMC_WRITE_FAILED) indicates flash storage wear-out.
you can however try another tool. do a full backup of all partitions first (especially partitions not included in stock ROM)
https://github.com/bkerler/mtkclient
I thank you for responding, I have downloaded and set up everything, as soon as I have a moment I will try to use the software you linked.
The phone worked, but it was locked as the owner, a friend of my uncle who gave it to him, had changed it long ago and could not remember the code to unlock it.
It was not a problem to reset it as he had already taken out his things before changing it.
However, I actually looked at several guides and followed every step, I didn't make anything up.
It had been several years since I had last done it, it seemed very similar to when using odin, and I went easy.
I can see in your screenshot you haven't unticked checkbox preloader. therefore I doubt you found the right tutorial. All it needs is formatting userdata and erase metadata + frp partitions.
https://www.hovatek.com/forum/thread-21638.html
some more information about Secure Boot Download Agents and why one must not flash in Format all + Download mode
https://www.hovatek.com/blog/so-whats-all-this-talk-about-meditek-secure-boot-and-da-files
similar thread
https://forum.xda-developers.com/t/frp-protection-on-doogee-s96-pro-who-has-tips.4418737
In the next few days I will have time to put in and try.
I have read the documentation, but I have a doubt: should I flash all *.img files, or just "super.img" which I failed with "SP Flash Tool"?
Or is there a command I haven't seen that automatically uses the "Android_scatter" file?
mtkclient don't use scatter file, it reads partition table on device. you can flash only super.img based on partition label.
Code:
python3 mtk w super super.img
Thanks for all the reply!
Im gonna watch all your link and in the next days let you know if it works! Meanwhile i wish you a good evening
I've been getting help on this over at Hovatek, but it's extremely slow going; I first posted there on December 11 and it's still not resolved. This phone is a former Lifeline phone, and I've been trying to get it rooted so that I can use the Tello SIM I obtained. The problem the phone was having is that it refused to do any updates, so Tello's troubleshooting as to why it wasn't detecting the SIM was completely halted.
I did finally get to the point of rooting it. The major problem I have now is that it will only boot to fastboot mode. I can get it into recovery mode, but I get the dead android with "no connection" under it, and I've tried everything the internet has suggested to get past that, and it won't. Additionally, any fastboot command (apart from "fastboot devices") I try in ADB returns "FAILED (remote: 'unknown command'). I don't know how to get it into EDL mode from fastboot. I've tried every button combo possible, and the only one that does anything different is power + volume up, which changes it to a bright white screen. At this point I just want to do a hard reset so I can take another go at the rooting process, but the phone doesn't seem to want to allow me to. I would appreciate any help with this; I don't have a working phone at the moment because of these issues.
https://forum.xda-developers.com/t/trouble-rooting-umx-u683cl.4518007
Yes, that's my original post from back in November. That post is no longer my problem, though I will set your response there aside for when I hopefully get the phone to do anything besides fastboot.
it's clearly same topic, you must not open new thread. add your second post to previous one so mods can delete this thread.
It's clearly not. It's the same phone, but a different problem. The old post was seeking help with rooting it (and got no action, you may note), this one is about getting it out of fastboot mode so I can reset the damn thing and try again.
you bricked that device as a result of trouble with rooting. all info belongs to the previous thread, so others can read the history that caused this situation. I am not arguing any further here. answer in other thread and close this one.
somnomania said:
I've been getting help on this over at Hovatek, but it's extremely slow going; I first posted there on December 11 and it's still not resolved. This phone is a former Lifeline phone, and I've been trying to get it rooted so that I can use the Tello SIM I obtained. The problem the phone was having is that it refused to do any updates, so Tello's troubleshooting as to why it wasn't detecting the SIM was completely halted.
I did finally get to the point of rooting it. The major problem I have now is that it will only boot to fastboot mode. I can get it into recovery mode, but I get the dead android with "no connection" under it, and I've tried everything the internet has suggested to get past that, and it won't. Additionally, any fastboot command (apart from "fastboot devices") I try in ADB returns "FAILED (remote: 'unknown command'). I don't know how to get it into EDL mode from fastboot. I've tried every button combo possible, and the only one that does anything different is power + volume up, which changes it to a bright white screen. At this point I just want to do a hard reset so I can take another go at the rooting process, but the phone doesn't seem to want to allow me to. I would appreciate any help with this; I don't have a working phone at the moment because of these issues.
Click to expand...
Click to collapse
Here is the full firmware for the U683CL. Be sure to wipe the userdata and cache because I dumped the firmware from the same phone from a guy for $5 and it still has the guy's data and it contains pretty weird things...
BE SURE TO USE EDL CLIENT!
EDL CLIENT IS ONLY SUPPORTED ON LINUX SO MAKE A VIRTUAL MACHINE!
EDL CLIENT DOES NOT REQUIRE ANY RAWPROGRAM0.XML OR PATCH0.XML FILE!!
Link (I will make sure this link is never taken down and if it is, I'm reuploading the link no matter what): https://www.mediafire.com/file/js8ynkg8uum9ql0/u683cl_february_patch.zip/file