Hi
I used my Xiaomi Redmi Note 3, 3GB RAM, 32GB new phone first day yesterday.
When I went to sleep it was 92% charged and when I woke up it was stuck on the Xiaomi loading screen. I let it on that screen for about 3 hours before I restarted it.
It's unable to boot into normal mode, and when I try to get into recovery mode it just shows a screen to connect a cable.
When I connect the cable to the computer it shows that the cable is connected but nothing happens after this.
If I boot the phone in fastboot and use Mi PC Suite to try to flash it, it just tells me to reboot in normal mode and try again.
If I hold all 3 buttons I have managed to get into some test mode, but from there I can't do anything.
How can I reset or get into my phone again? Is this normal behaviour after just one day use?
Johanna12221 said:
Hi
I used my Xiaomi Redmi Note 3, 3GB RAM, 32GB new phone first day yesterday.
When I went to sleep it was 92% charged and when I woke up it was stuck on the Xiaomi loading screen. I let it on that screen for about 3 hours before I restarted it.
It's unable to boot into normal mode, and when I try to get into recovery mode it just shows a screen to connect a cable.
When I connect the cable to the computer it shows that the cable is connected but nothing happens after this.
If I boot the phone in fastboot and use Mi PC Suite to try to flash it, it just tells me to reboot in normal mode and try again.
If I hold all 3 buttons I have managed to get into some test mode, but from there I can't do anything.
How can I reset or get into my phone again? Is this normal behaviour after just one day use?
Click to expand...
Click to collapse
Flash aboot it will ok..
Hi and thanks for your reply!
By running fastboot getvar product I found out that I have the "special edition" model, kate.
I have now downloaded this:
kate_global_images_6.9.8_20160805.0000.29_6.0_global_042c784ac4
After unpacking and trying to flash I get this:
Code:
fastboot flash tz C:\kate\kate\images\tz.mbn
target reported max download size of 536870912 bytes
sending 'tz' (637 KB)...
OKAY [ 0.023s]
writing 'tz'...
FAILED [B](remote: Critical partition flashing is not allowed)[/B]
finished. total time: 0.032s
"Flash tz error"
Johanna12221 said:
Hi and thanks for your reply!
By running fastboot getvar product I found out that I have the "special edition" model, kate.
I have now downloaded this:
kate_global_images_6.9.8_20160805.0000.29_6.0_global_042c784ac4
After unpacking and trying to flash I get this:
Code:
fastboot flash tz C:\kate\kate\images\tz.mbn
target reported max download size of 536870912 bytes
sending 'tz' (637 KB)...
OKAY [ 0.023s]
writing 'tz'...
FAILED [B](remote: Critical partition flashing is not allowed)[/B]
finished. total time: 0.032s
"Flash tz error"
Click to expand...
Click to collapse
By looks of it, you have a locked bootloader and hence, are unable to flash fastboot files. The only way for you to make your device usable again is to somehow boot into the 'edl' mode and use MiFlash to falsh the fastboot ROM from there.
Hi! Thanks for your reply.
I didn't do anything to the bootloader, so yeah it should be locked.
I will contact the store I bought it from and try to get it returned.
So sad to have made this purchase. I hope I can find another phone, perhaps one that is not as cheap as this.
Hi again!
I have kept trying to solve this issue further. I'm able to get into edl mode using the modified fastboot that I found here on the forums with "fastboot reboot-edl".
I managed to run MiFlash 2016.04.01 (important, newer version didn't work!)
But it still seems to be stuck in just an endless Android loading screen. Anything else I can try?
Johanna12221 said:
Hi again!
I have kept trying to solve this issue further. I'm able to get into edl mode using the modified fastboot that I found here on the forums with "fastboot reboot-edl".
I managed to run MiFlash 2016.04.01 (important, newer version didn't work!)
But it still seems to be stuck in just an endless Android loading screen. Anything else I can try?
Click to expand...
Click to collapse
I can help you. Talk me in PM.
Hi!
Thanks for offering your help, andersonaragao.
I finally got it to work by doing a "Flash all" of the MIUI 8 package.
So the steps so solve was just this easy:
Boot in fastboot (Volume down + power)
Make sure you have kenzo or kate (fastboot getvar product)
Get correct fastboot rom, depending on kenzo/kate: (http://en.miui.com/a-234.html)
Boot in edl (Fastboot_edl-v2: fastboot reboot-edl)
MiFlash 2016.04.01 (Flash all)
Related
My almost two-year-old Hero froze this morning, so I had to take out the battery, but after this I've been unable to boot, it's stuck on the HeRO screen. I can't start recovery either, the only thing working is hboot / fastboot. Erasing user data using fastboot doesn't do anything.
Also, plugging the phone into charger doesn't signalize charging – the LED doesn't light up, and the PC doesn't recognize the phone either. Only fastboot does connect the phone to the PC, but adb doesn't work and all attempts to flash a new recovery or do anything else via fastboot end with "FAILED (remote: not allowed)":
Code:
c:\adb>fastboot devices
HT97JL903267 fastboot
c:\adb>fastboot boot recovery-RA-hero-v1.7.0.1.img
downloading 'boot.img'... FAILED (remote: not allow)
c:\adb>fastboot flash boot recovery-RA-hero-v1.7.0.1.img
sending 'boot' (3972 KB)... FAILED (remote: not allow)
I tried installing the official RUU updates (2.73.405.66, 2.73.405.5 and 1.76.405.1 too) but none of them could connect to the phone, Error [170]: USB Connection error.
I was using Elelinux-Hero-2.1-update1-Reloaded with radio 63.18.55.06SU_6.35.17.03 and recovery was Amon RA 1.6.2 I guess.
The phone did a similar thing 3 weeks ago but I was able to boot into recovery and erase data and cache and it worked fine afterwards. Now only fastboot is accessible.
Is there anything else I can do at this point or is the phone dead for good?
Disregard my previous post.
I left the phone booting for 30 minutes, the battery got uncomfortably hot, but the phone booted up eventually. Then I managed to install the official RUU from here.
It didn't solve anything though – it still takes around 20 minutes to boot, the touch screen doesn't work and I get an "android.process.acore" error all the time – but since the phone seems untouched (thanks to the RUU install) I can lodge a claim and get a replacement phone hopefully.
You could try putting HEROIMG.NBH on the sdcard and booting into hboot. If you go into fastboot and press vol-down it quickly scans for files on the SD, of which heroimg is one, and if it finds them, installs them.
Can't really help more than that. My phone did that last year, took it to the shop and ended up getting a new motherboard, cause the ROM chip was knackered.
One thing I would recommend though when you get it fixed is to flash an engineering bootloader, do if it breaks again you've got none of this "remote not allow" rubbish.
Of all the times to say disregard my last post.........
Sorry about that, thanks a lot though!
I suppose some hardware is broken in my Hero as well, I will take it back to the shop tomorrow.
Thanks again!
Hi guys,
after flashing original recovery from Rashr, I have a hard bricked Meizu M1 Note. I can only boot into fastboot or VCOM (for SP Tool), no recovery, not normal boot.
Hope you can help me,
Thank you
Same story, even worse! I wanted to downgrade from LP to KK. I followed step by step guide posted in other forum. Everything works, but after 2 or 3 days, phone started to act very strange. Volume keys did not react properly (cant switch in recovery and made an screen shot for example), phone started to loose network coverage . I tried to reset it, but unfortunately no fastboot and recovery modes were present. The only way to switch in recovery was rashr tool. I decided to reflash recovery again and everything went wrong! The result was permanent restart, no recovery and fastboot modes. Maybe this method should be avoided. I know that everything I made is at my own risk, dont blame me.
Need advice to unbrick it. I was thinking to disassemble it and disconnect battery and try to resurrect it with adb?! The bad thing is that it wont turn into fastboot...pfuu.
Have some progress - phone can go into fastboot mode, but when I try to flash stock recovery, it reports error:
C:\adb>fastboot flash recovery recovery.img
sending 'recovery' (16384 KB)
OKAY [ 0.616s]
writing 'recovery'...
FAILED (remote:
Security deny - Err:0x2017 because it is locked
)
finished. total time: 0.665s
Click to expand...
Click to collapse
Will appreciate any help. Thanks!
Any help?
Help
I have the same problem. Could anyone help us?
any help?
I have more or less the same problem but my cellular conects disconects preloader usb driver and don't see nothing in the screen, not logo, not recovery, not fastboot mode, any help?
Hello there!
Long story short:
I'm was successfully running on twrp-3.0.2-0-onyx-20161020-085152.img and cm-13 on my beloved OPX for serveral months now. Got it running, following this guides:
http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
https://wiki.cyanogenmod.org/w/Install_CM_for_onyx
Also, happily updating the nightly builds since then.
But last update went wrong. I OTA updated my device on the go, not paying to much attention that the update will be cm13->cm14. After TWRP installed the update i got stuck on reboot with the OnePlus logo.
I restarted the phone (Powerbutton off/on), 'cause my guts told me that something went wrong. I hoped to reboot to recovery an rollback the update to previous CM version.
But, it won't boot.
This is what happens:
Powerbutton down (Trun on): -> Vibrates -> flashes OP Logo + powerd by Android -> Vibrates -> flashes OP Logo + powerd by Android ->...
I can reach fastboot mode by VolumeUp (w/o pressing powerbutton) but i cannot reach TWRP recovery.
So normally i could totally live with fastboot, flashing reflashing unlocking etc. BUT here my first WTF experience took place:
I can not
Code:
fastboot oem unlock
because oem unlock is locked! I know how to unlock it via DevMode -> unlock oem unlock yadda yadda (who had this "great" idea anyway?!). But since i cannot boot the OS, i cannot enter devmode....
So before going through all the (Mega)unbrick guides, I'm curious:
Is there some way around this dilemma?
What we've got: No OS, no recovery, only fastboot
Code:
$: fastboot devices
...
25bf1e07 fastboot
$ fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.006s]
finished. total time: 0.006s
$: fastboot oem unlock
...
FAILED (remote: oem unlock is disabled)
finished. total time: 0.003s
$: fastboot format userdata
Creating filesystem with parameters:
Size: 12611891200
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3079075
Block groups: 94
Reserved block group size: 751
Created filesystem with 11/770048 inodes and 88617/3079075 blocks
target reported max download size of 536870912 bytes
erasing 'userdata'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.000s
Code:
fastboot continue
ends up in same loop.
I cannot adb.
Device is encrypted.
I've no problem to completely wipe or factory reset or stock reset my device, hence i love tinkering with it and have backups of important data.
I sincerely ask for some pointers, links, opinions on how to go on from here? Is there a chance to get my phone back running? Should I stop searching and just follow the unbrick guides?
Are there unbrick guides for Linux users? (Just nice to have! )
Is there some exploit, backdoor, trick, magic to circumvent a disabled 'oem unlock'? (again: who had this 'great' idea anyways? )
Unbrick guide(s):
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-x.417648/
Thank you very much in advance! Have your (virtual) coffee on me!
sem
Hi,
I do have the very same issue.
I can enter fastboot but that's about it. Would be curious to get it running again without the "mega unbrick" stuff...
I found a way to get back.
After i have flashed to CM 14.1 Nightly update it was stuck at the oneplus logo, and i felt the same that something went wrong had no other choice just rebooted the phone and then it started acting wired (Phone vibrates and it shows oneplus logo for every second) and not able to access TWRP. Only i can access is Fast boot but here is the twist the oem was locked and we cannot unlock it any way.
Spent lot of time (2hrs+) searching for the solution and finally found it :angel:
Check this Link
forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-x.417648/
It took me around 4hrs to get back to my Custom Rom
Cheers
i'm suffering the same problem now...today morning tried to update the cm nightly 14 and soft bricked my oneplus X
is the mega unbrick guide really working..? for me device is not recognized when i connect the phone to the pc pressing v up key for 10 secs..
prasannazx said:
i'm suffering the same problem now...today morning tried to update the cm nightly 14 and soft bricked my oneplus X
is the mega unbrick guide really working..? for me device is not recognized when i connect the phone to the pc pressing v up key for 10 secs..
Click to expand...
Click to collapse
Which driver you are using and which windows version 64bit or 32bit?
prasannazx said:
i'm suffering the same problem now...today morning tried to update the cm nightly 14 and soft bricked my oneplus X
is the mega unbrick guide really working..? for me device is not recognized when i connect the phone to the pc pressing v up key for 10 secs..
Click to expand...
Click to collapse
Just flash Arsenic Kernel for Android N. Cyanogen 14 has kernel problem. Flashing custom kernel will fix your bugged boot
Caraparbor said:
Just flash Arsenic Kernel for Android N. Cyanogen 14 has kernel problem. Flashing custom kernel will fix your bugged boot
Click to expand...
Click to collapse
Thnx man!! It helped me not to waste my time doing this mega unbrick process...
Caraparbor said:
Just flash Arsenic Kernel for Android N. Cyanogen 14 has kernel problem. Flashing custom kernel will fix your bugged boot
Click to expand...
Click to collapse
Thank you...? ?
does the clock app and settings for gboard work ????
does the clock app and settings for gboard work ????
Caraparbor said:
Just flash Arsenic Kernel for Android N. Cyanogen 14 has kernel problem. Flashing custom kernel will fix your bugged boot
Click to expand...
Click to collapse
But is flashing a kernel possible w/o oem unlock?
prasannazx said:
i'm suffering the same problem now...today morning tried to update the cm nightly 14 and soft bricked my oneplus X
is the mega unbrick guide really working..? for me device is not recognized when i connect the phone to the pc pressing v up key for 10 secs..
Click to expand...
Click to collapse
Press VolUp until you see something in Devicemanager! It took more than 10s for me too until it showed up in Devicemanager.
Or if you have a Linux at hand, look at dmesg. You should see something like this:
Code:
[ +0,004635] usbcore: registered new interface driver qcserial
[ +0,000049] usbserial: USB Serial support registered for Qualcomm USB modem
[ +0,000103] qcserial 1-4:1.0: Qualcomm USB modem converter detected
[ +0,000325] usb 1-4: Qualcomm USB modem converter now attached to ttyUSB0
[Dec24 02:39] usb 1-4: USB disconnect, device number 6
[ +0,000343] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0
Ashok6086 said:
After i have flashed to CM 14.1 Nightly update it was stuck at the oneplus logo, and i felt the same that something went wrong had no other choice just rebooted the phone and then it started acting wired (Phone vibrates and it shows oneplus logo for every second) and not able to access TWRP. Only i can access is Fast boot but here is the twist the oem was locked and we cannot unlock it any way.
Spent lot of time (2hrs+) searching for the solution and finally found it :angel:
Check this Link
forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-x.417648/
It took me around 4hrs to get back to my Custom Rom
Cheers
Click to expand...
Click to collapse
I was stuck on OnePlus logo too, but I solved the situation pushing a different recovery throgh fastboot commands, then I've installed a different ROM. It took me only 5 minutes!
When you restart your bricked device (pressing for 12 seconds the power btn) keep pressed the Volume UP BTn to enter the Fastboot Mode, the follow the procedure to flash a different recovery.
I'm using BlueSpark TWRP Recovery. As ROM, for now, I'm using XperienceRom with Android 7.1 and no bug found.
I tried that too, but no use. it says OEM Locked and we cannot unlock the phone that means we cannot load anything.
Ashok6086 said:
I tried that too, but no use. it says OEM Locked and we cannot unlock the phone that means we cannot load anything.
Click to expand...
Click to collapse
Use megha unbrick guide
http://forum.xda-developers.com/one...ga-unbrick-guide-hard-bricked-t3272108/page20
I had the same problem. Solved it by first flashing latest cm and right after that I flash arsenic kernel and then reboot. I had to do that every time I flash a new nightly build but it works. Hope it helps
Hello.
I've had the exact same problem as semph0re.
Did the Mega Unbrick Guide thing, somehow I got a "Sahara communication failed" during the process, but it still managed to flash the stock recovery (and the old bootloader i guess).
From there I'm able to install and successfully boot OOS 2.3 (or older), old versions of CM13.0 (those based on the old bootloader), and TWRP-3.0.2-0 recovery and therefore unlock the bootloader.
So basically anything compatible with the old bootloader.
And trying to install anything based on the new bootloader, either a stock rom, the OPX_MM_recovery from Oneplus, any custom rom, with or without custom kernel or a custom recovery leave me with a fixed Oneplus logo (and the powered by android disappearing almost immediately)
But I can't manage to update the bootloader.
Either by trying to install OOS3.1.x from OOS 2.x
Nor by following matwaking guidehttps://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Does anyone have face the same issue ? Any idea what could the cause of the problem ?
The only thing I could think of but didn't try is to go through the Mega Unbrick guide again. But I'm on Ubuntu and do not have a Windows machine anywhere near me at the moment.
@GARGZUL you have to use stock recovery from 2.X.X not mm stock.
Exodusche said:
@GARGZUL you have to use stock recovery from 2.X.X not mm stock.
Click to expand...
Click to collapse
@Exodusche
That's what I tried many times.
Trying to install OOS3.x from OOS2.x with either (old)stock recovery or TWRP-3.0.2-0 leave me with a beautiful stuck Oneplus logo when booting system.
And those are the only recovery I can boot on. Any more recent recovery won't boot (fixed Oneplus logo again or 'dtb not found' error when boot from fastboot command) since they require the new BL.
It's like when trying to install OOS3.x or flashing matwaking's BLUpdater.zip the old bootloader is not deleted, effectively preventing any new BL based rom or recovery to boot.
@GARGZUL Use latest twrp and you want to use 2.2.3 before flashing 3.X.X .
Exodusche said:
@GARGZUL your using the wrong twrp use 3.0.3
Click to expand...
Click to collapse
@Exodusche
I would if I could. But when flashing TWRP 3.0.3-0 (either with flashboot or via TWRP 3.0.2-0) my phone won't boot to recovery (Vol down+poweer gives me a stuck oneplus logo, and 'fastboot boot twrp-3.0.3-0-onyx.img' gives me a "dtb not found" error).
Any other idea ?
Hi,
I'm new here, so please excuse me if I am posting in the wrong category.
So I tried to root my Doogee F7 (not the pro version) using fastboot and TWRP, and it resulted in a sort of bootloop where it says:
Code:
Orange State
Your device has been unlocked and can't be trusted
Your device will boot in 5 seconds
And then it restarts and gives the same message again. This loop has been going on for some time and I can't stop it because the phone has a non-removable battery and I have tried every possible combination of buttons (i.e. Power + Volume Down + Volume Up).
The process I used in my attempt to root was as following:
1. I used
Code:
adb reboot bootloader
to go into fastboot. (I already set up everything like USB debugging and OEM unlocking in the developer options)
2. I then used
Code:
fastboot oem unlock
and pressed Volume Up to unlock the bootloader. All was successful.
3. I then tried to flash TWRP to recovery and I believe this is where everything went wrong. I flashed it using
Code:
fastboot flash recovery recovery.img
and it was successful, according to the command prompt:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery "C:\Users\momen\Downloads\recovery (1).img"
target reported max download size of 134217728 bytes
sending 'recovery' (12832 KB)...
OKAY [ 0.562s]
writing 'recovery'...
OKAY [ 0.213s]
finished. total time: 0.779s
4. After it finished I used
Code:
fastboot reboot
to reboot the phone and that's when it got stuck.
At the moment I am just letting my battery run out, as I have no other way of turning off the phone, and neither adb nor fastboot is working.
I don't really know if my device was even supported, but I followed the instructions on various websites stating that I should first unlock my bootloader, then flash TWRP, then flash superSU onto it, and my phone would be rooted. I used the latest TWRP image, and I think that was where I went wrong. Is there anything I can do to get my phone to work again?
Hey! i´m sorry for your phone, can you tell me any updates, is it fixed now? what happened? i am about to do the same process to root my Doogee F7 and i´m very worried that my phone gets bricked, so please, i need your recommendations.
I hope everything is alright with your phone.
solartediego said:
Hey! i´m sorry for your phone, can you tell me any updates, is it fixed now? what happened? i am about to do the same process to root my Doogee F7 and i´m very worried that my phone gets bricked, so please, i need your recommendations.
I hope everything is alright with your phone.
Click to expand...
Click to collapse
Ah yes, sorry for not updating. I managed to connect my phone to my PC again using the flash tool and then I could flash the original ROM back onto it. I found the ROM by Googling for a bit tho I dont have a link. Be aware that if you do this, it basically factory resets your phone, locking your bootloader again and all. If you do manage to root your phone please contact me as I still have not managed to do so.
Edit: This process of flashing back your ROM always works as long as your phone powers on, so don't worry too much about bricking your phone. I think I've bricked my phone over 20 times trying to root it, and it worked every single time.
Hello there. I suggest that you use "fastboot boot recovery.img" than using "fastboot flash" if you are not sure if the custom recovery works (or if you just want to test/try it). In this way, you'll just boot the custom recovery temporarily (and your stock recovery is still in tacked).
For rooting your device, first you'll need a working custom recovery for your device (you used TWRP, very first if it works or compatible with your device).
Insyder28 said:
Ah yes, sorry for not updating. I managed to connect my phone to my PC again using the flash tool and then I could flash the original ROM back onto it. I found the ROM by Googling for a bit tho I dont have a link. Be aware that if you do this, it basically factory resets your phone, locking your bootloader again and all. If you do manage to root your phone please contact me as I still have not managed to do so.
Edit: This process of flashing back your ROM always works as long as your phone powers on, so don't worry too much about bricking your phone. I think I've bricked my phone over 20 times trying to root it, and it worked every single time.
Click to expand...
Click to collapse
Hi.How you actually managed to connect your phone to PC using flash tool if you were in a bootloop and had no access to fastboot mode or recovery?
ciubsy2004 said:
Hi.How you actually managed to connect your phone to PC using flash tool if you were in a bootloop and had no access to fastboot mode or recovery?
Click to expand...
Click to collapse
Im interested too in your process to flash TWRP again, as i am in the same boot loop than you with a Doogee S60. I´ve waited till the battery ended, but now flash tool doesn´t recognize my phone. If i charge the battery, i get a boot loop again..
TheBidan said:
Im interested too in your process to flash TWRP again, as i am in the same boot loop than you with a Doogee S60. I´ve waited till the battery ended, but now flash tool doesn´t recognize my phone. If i charge the battery, i get a boot loop again..
Click to expand...
Click to collapse
I have managed to get the flash tool recognizing my phone.Had to keep pressed volume up,if i recall properly(or try volume down) before connecting usb cable to phone with flash tool opened and . It was a while ago though and i can't remember exactly which key was for sure. Hope this helps
Hello guys,
I've recently got my hands on a not-working P20 Lite, which was stuck on boot with the well-known "your device has failed verification and may not work properly" error message. Since I got stuck on a HUAWEI logo when trying to enter the recovery, ended up in a bootloop trying to enter the download mode, the only way to get the phone working was fastboot. And since I am writing this post, yeah, y'all guessing correctly, it has not been successful. (Error message 'Command not allowed')
After giving up on it and leaving it stuck on the HUAWEI logo for a while, I have noticed that it has turned off. After turning on the device, it shows a green screen with 2, red and blue squares (see attached image), still not being able to boot in recovery mode, however fastboot still somehow manages to fire up.
Any suggestions? Is this phone dead (which I honestly believe), or is there something that would possibly be able to change its state?
Thanks!
EnterPaulini said:
your device has failed verification and may not work properly"
Click to expand...
Click to collapse
EnterPaulini said:
it shows a green screen with 2, red and blue squares
Click to expand...
Click to collapse
Wrong region (oeminfo).
EnterPaulini said:
Is this phone dead?
Click to expand...
Click to collapse
No, not dead yet
Need more information about your phone . Install on your PC "Minimal ADB and fastboot" tool .
In fastboot mode run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
fastboot oem battery_present_check
and post the results please.
(First try to charge the phone).
(bootloader) :ANE-LX1 9.1.0.372(C432E7R1P7)
(bootloader) ANE-LX1
vendorcountry: hw/eu
(bootloader) :ANE-LX1-CUST 9.1.0.7(C432)
(bootloader) :ANE-LX1 9.1.0.132(C432E5R1P7)
(bootloader) 3426mv
Thanks!
Okay, try this way out...
1. in fastboot mode run command
fastboot erase userdata
and try restart the device.
2. download and use a Service ROM
https://androidhost.ru/2AVi
with an sd/card or an USB-OTG flashdrive in dload mode. Unpack .zip archive , find dload file in "Software" folder, and simply transfer it to the SD card, without unpacking it! (instruction can be found in ReleaseDoc folder).
Turn off your phone and flash FW using three button combo .(Power+Vol.Up+VolDown).
-Alf- said:
Okay, try this way out...
Click to expand...
Click to collapse
Still hanging in there! Entering the dload mode does not work, I always land on the same green screen and it shuts down.
EDIT:
Back to the "Your device has failed verification and may not work properly" screen. It actually shows the HUAWEI logo again and shows that the device is charging, when turned off. Trying to enter the dload mode results in a bootloop.
EDIT2:
After few times of trying to enter the dload mode I am stuck with the green screen again. From what I have observed, the green screen does not come up when I am connected with the USB cable. When not, everything except fastboot leads to the green screen with a small LED diode blinking red (not so familiar with this phone, no idea what's this for, it's located on the notch). On the other hand, everything except fastboot with cable connected leads to a bootloop. But at least I can see the HUAWEI logo, eh?
Paid service
But if it's a hardware problem (e.g. dead memory), it won't help you.
-Alf- said:
Paid service
But if it's a hardware problem (e.g. dead memory), it won't help you.
Click to expand...
Click to collapse
And if I tried this solution @kikson112 suggested? Doing something with that test point, could this end up working?
I can't help you, that's Greek to me... I have never used this method, nor dc-phoenix (thank goodness).
This happened to my ANE-LX1 a while ago, bootloader never unlocked and device was fully stock...
Device was still under warranty and huawei repaired it for free
Probably a hardware issue
Hey! I have the same problem now. From todays morning it has been stuck on the loading Huawei logo. I haven't got any messages about that warning, you have got, but I have tried to enter the recovery mode and sometimes, it just flashes that green screen with the two squares. Now I think is without power. Have you somehow started the phone?
AmaliaRepova said:
Hey! I have the same problem now. From todays morning it has been stuck on the loading Huawei logo. I haven't got any messages about that warning, you have got, but I have tried to enter the recovery mode and sometimes, it just flashes that green screen with the two squares. Now I think is without power. Have you somehow started the phone?
Click to expand...
Click to collapse
Hello,
some related links:
https://forum.xda-developers.com/t/...-blue-red-flag-fastboot.4339931/post-85697163