Hello everyone!
I have a ulefone armor x5 pro (MT6762). I tried to install twrp without success, as the port available in the forum is for the MT6763 chip variant. Before further experimenting (my phone entered in a bootlop that i resolved reflashing recovery.img), After that experience, I decided to make a backup of my own stock rom as the available on the ulefone official site seems not to be the right one (armor X5 not pro). Using SP_Flashtools, I tried to do a full reading of my device, and the power supply was cut off in the process. At this point, the device was dead. Then I was able to flash the rom provided by the manufacturer. The process was completed successfully. However, the phone did not turn on again. I disassembled it to disconnect the battery and sp flashtools recognizes it, but it remains stuck in "downloading DA 100" and does not advance any further. Try reinstalling drivers, changing laptops, different versions of the program, and SP_MDT but the same thing always happens. Downloading DA 100% (red bar at the bottom) and nothing else. At this point I don't know what else to do. My phone does not turn on at all. Any suggestion will be highly appreciated.
Thankyou!
EDIT: PROBLEM SOLVED. The problem was the firmware that i tried to download. The manufacturer has many variants of the same device name. Now the phone has back to life.
Hi, I have the Ulefone Armor X5 2020 version (android 10)with the mt6762 mediatek processor ( description of the seller, the ticket on the box and Ulefone description) this is very confuse why the stock rom for this device is for mt6765 and I read mt6765 with sp flash software.
My problem is what this was bricked from factory, its work unstable and rebooting ramdomly.
I try many things like factory reset, wipe the cache, (when wipe the cache the display show E: Fota installation aborted, E:: No such file or diretory) reflash the stock firmware, reflash preloader and recovery separately, but the problem persist.
And one of the first messages i read was system corrupted.
{
"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"
}
Please Help!!!
Related
Hello,
I used Sp Flash Tool to get my ZTE Blade L3 back to Stock (after a self ported rom failed -.-').
Because I was a little sleepy, I didn't unchek all boxes and everything got flashed.
(Preloader, MBR, EBR1, BOOTMG, Recovery, SEC_RO, LOGO, Android (/System))
Afterwars I wanted to restart the phone, but the display stayed black....
As it seems, my L3 only starts the bootloader, but doesn't realy boot ( Device-Manager doesn't detect the phone).
After many tries, I wasn't able to acomplish something.
Tried:
-reflash everything
-only flash bootloader, MBR, EBR1, BOOT, LOGO & SEC_RO
-flash bootloader & format flash
-(wasn't able to get meta-mode http://forum.xda-developers.com/showthread.php?t=1943442)
Sometimes the phone loopes the bootloader and changes between Mediatek Preloader & Mediatek USB Port (strangely the COMs switch between 6 and 7).
SP Flashtool Memory Test also says:
Error: NAND Flash not detected!
Error: UFS not detected!
{
"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"
}
Click to expand...
Click to collapse
I don't know what I can do anymore, I hope that someone can help me.
Just for someone else who comes here the ROM (at least the stock ROM)... Go to 4PDA. I went 6 days trying to learn how to fix the phone without knowing anything about any of this, and luckly I found 4PDA... It has ROMs of the phone. Stock ROMs (which was what I wanted) and modified ROMs. Nowhere else I found stock ROMs for it... I REALLY recommend that website for ANYONE who mods the phone... At least if it's not that known, like Blade L3. It's in russian, but if you need, use Google Translate or any other translator and it will work well enough. This phone can't be bricked. I've done many stupid things to it. It's ALWAYS recoverable. I can do whatever I want. It will never be bricked. As long as a phone with a MediaTek chipset has a scatter file and correct files to flash, it can't be bricked. At least from my experience... Cheers!
using SPFlash you need to click on download or if not working click on firmware upgrade, not on format and download!
Hello,
i'm new in the forum, i have problem with Meizu M6 Note M721H because i have installed twrp recovery with app crack (3.2.1) and next i have deleted SO (flyme firmware) and i have cleaned the phone, after i have updated twrp to 3.2.2-0 version and after reboot, after 1-2 seconds of meizu logo the screen becomes black and the twrp doesn't start....and i haven't firmware installed...fastboot mode working but i haven't permissions because bootloader is locked and secured. I can't use well QFIL.exe and after after I Have entered the files in the program and start download, i have the issue: "Download Fail: Switch to EDL FailFailed to Switch to Emergency Download mode". I tried everything, could you help me?
{
"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"
}
Maybe this can help you to fix that error.
https://geekofia.wordpress.com/2017/10/12/download-failswitch-to-edl-failfirehose-fail-fixed/
MatteoGhost07 said:
Hello,
i'm new in the forum, i have problem with Meizu M6 Note M721H because i have installed twrp recovery with app crack (3.2.1) and next i have deleted SO (flyme firmware) and i have cleaned the phone, after i have updated twrp to 3.2.2-0 version and after reboot, after 1-2 seconds of meizu logo the screen becomes black and the twrp doesn't start....and i haven't firmware installed...fastboot mode working but i haven't permissions because bootloader is locked and secured. I can't use well QFIL.exe and after after I Have entered the files in the program and start download, i have the issue: "Download Fail: Switch to EDL FailFailed to Switch to Emergency Download mode". I tried everything, could you help me?
Click to expand...
Click to collapse
what do you mean you deleted "SO"?
if i understand correctly you replaced stock recovery with twrp but it can not load because your bootloader is locked.
i am not very well familiar with qfill but you are having wrong port open "900E" . you need to enable "9008".
try if this trick works https://www.youtube.com/watch?v=fOpZsUQwOrY
fortunately i have the same problem, same phone, unfortunately you need to open it up, as i understand there are some circuits you need to shortcircuit to load the fastboot, looking into this now, will post updates
And how did someone solve a black screen problem after TWRP botting? I have the same problem and I can not deal with it; /
master2007 said:
And how did someone solve a black screen problem after TWRP botting? I have the same problem and I can not deal with it; /
Click to expand...
Click to collapse
hold down the power button for 20 seconds?
Assuming you still have an the Android OS installed.
Unbrick Meizu M6 note
Hello, why don't you try to flash it with qfil rom?
Recently I have found in my drawer an old Yarvik Noble 97ic+ (Tab09-410) tablet, I got around 2014. Unfortunately it had a broken DC charging connector and the microUSB wasn't enough to kickstart it back to life. So I decided to disassemble the tablet and after some time I managed to charge it and actually turn it on. It booted up and everything. I left it to charge a bit more, but after coming back I found that the tablet no longer boots and all I can get is the "YARVIK" logo stuck on the screen. I have found another customer with exactly the same problem - He charged the tablet for a bit too long and bricked it.
What I can do with the tablet is get it to show with the "adb devices" and I can get it to STOCK recovery, which unfortunately only allows to flash images verified by the manufacturer. I tried all the options in recovery - wiping the cache, data/factory reset and recovery system from backup.
The Yarvik brand, which was a small company in the Netherlands went bankrupt a while ago and there isn't any support or stock firmware images on the web. I only found some dead links on the site arctablet.com, where I also found some users that successfuly flashed a newer android - a rom for Odys Iron CM12.1 lp 5.1.1 (stock is 4.2.2)
When I reboot it into bootloader the screen is completely dark and "lsusb" command shows only the usb port without any device name.
When I tried the "adb reboot-bootloader" command in the console, the device is no longer recognized (with fastboot devices). I assumed it might be because of missing windows drivers, so after trying a whole bunch of them I connected the device to linux with same results. When I reboot it into bootloader the screen is completely dark and "lsusb" command shows only the usb port without any device name. Therefore I cannot install any custom recovery like CWM or TWRP which would allow to flash another than the original Yarvik image.
Is there anyone that could provide the original Yarvik "Tab09-410.img"? Any help is widely appreciated. Thank you for your precious time.
{
"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"
}
Bump. Anyone?
search for odys-iron-jb4.4.2-V1.04
willem
Hi there,
I'd really be grateful for any help anyone can give. Yesterday, my Honor 7C got stuck in a boot loop, restarting at the blue Honor screen continually until the battery runs out. It's impossible to boot it into recovery mode using any combination of key presses. It just keeps restarting.
Can someone please help? I don't really mind losing the phone, but ideally I would like to save some of the data on it, as it had been a while since I backed up.
I understand that the way to do this might be to flash the stock ROM, root the phone and then run a data recovery program like EaseUs. Is this correct?
Also, I have tried to flash the stock ROM but really have no idea how to do it. I got half way through using SP Flash Tool before I realised that the Honor 7C is not a Mediatek phone.
Also, I can't find the stock ROM (LND-L29) anywhere except on pretty dodgy looking websites. Is there a reliable source for stock ROMs anywhere?
Any help would be really gratefully received. Thanks!
B7C
@Bricky7C
Your Honor 7C has a Qualcomm chip-set hence you might use free-of-charge QPST ( read: Qualcomm Product Support Tool ) to re-flash device's Stock ROM.
{
"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"
}
Turns out my bootloop was caused by a hardware problem after all - ripping open the side of the phone solved it.
However, for anyone who stumbles across this thread with a similar problem, jwoegerbauer's suggestion of QPST was very helpful, but the tool on the site would not install for me on Windows 10. I kept getting an "installation was interrupted error". However, I found a working version of the tool at:
androidmtk dot com fslash download-qpst-flash-tool
[I'm a new user so XDA won't allow me to post a URL]
I scanned for viruses and the installation didn't cause me any issue, though I never ended up having to use it in the end.
Hi everyone, I have the Ulefone Armor X5 2020 version (android 10)with the mt6762 mediatek processor ( description of the seller, the ticket on the box and Ulefone description) this is very confuse why the stock rom for this device is for mt6765 and I read mt6765 with sp flash software.
My problem is what this was bricked from factory, its work unstable and rebooting ramdomly.
I try many things like factory reset, wipe the cache, (when wipe the cache the display show E: Fota installation aborted, E:: No such file or diretory) reflash the stock firmware, reflash preloader and recovery separately, but the problem persist.
And one of the first messages i read was system corrupted.
{
"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"
}
Help me please!!!
Aha! Same fone as mine... Now here's your problem, same as mine, quite simply, android 9 says mt6762, but an upgrade to android 10_q shows mt6765, I now have mine on 10 pro, and it shows mt6762. Now to get out of where you are, you need to grab the firmware for your fone, have adb/fastboot setup, and get ready to restore fone, the fact you can see recovery means it aint that bad... did you fix it?
Pachacouti said:
Aha! Same fone as mine... Now here's your problem, same as mine, quite simply, android 9 says mt6762, but an upgrade to android 10_q shows mt6765, I now have mine on 10 pro, and it shows mt6762. Now to get out of where you are, you need to grab the firmware for your fone, have adb/fastboot setup, and get ready to restore fone, the fact you can see recovery means it aint that bad... did you fix it?
Click to expand...
Click to collapse
Hello, thanks for answering, could you tell me the download link of the firmware that you used to be able to test and see if my phone revives please.