Related
Hi there !
I just switched from a Windows Phone to a Huawei P9 Lite (VNS-L31), my first Android phone (never too late, I guess?).
I was following the instructions provided in this toolkit (https://forum.xda-developers.com/hu...nt/europe-vns-l31-toolkit-bootloader-t3432873) to unlock the dual SIM support, as this phone is from Orange and locked to single SIM.
I successfully unlocked the bootloader, installed TWRP and rooted the phone. I got to the stage when updating the phone from the SD card is requested. Stock firmware was L31C109B120, new firmware is L31C432B130.
The update seemed to progress well, but actually no, as the phone is now bricked (black screen, screen will not power on, does not display anything).
Powering the phone with any combination of Vol+, Vol- and Power depressed results in nothing at all.
So I installed adb + fastboot and at least the phone is recognized in fastboot. I successfully unlocked the bootloader (again?) within fastboot with my unlock code.
Now I am able to manually flash the boot, recovery and system partitions from the B130 firmware. Unfortunately, this results in nothing, the phone will still not boot to anything else than fastboot mode.
I have limited knowledge/experience with Android phones, so I am kind of stuck now. I have read several topics and fastboot definitely seems to be the way to go, but there must be something that I am doing wrong.
I was wondering whether someone would be willing to give me some insight, please?
Any help would be highly appreciated!
Many thanks in advance,
Regards,
Eric.
[Edit]: I was able to flash the stock VNS-L31C432B130 firmware but not with fastboot... I had to use DC-Phoenix and pay 15€ to do so. Is there a free equivalent to DC-Phoenix yet?
Hello
I think you should disconnect the cable and press on volume + and power erevovery wipe factory, cache. Restart
If it does not work, start again.
With the toolkit, bootloader code, installs twrp,
Go download c432oeminfo double sim.zip Badwolf
Fashe c432oeminfo.zip.
switch off.
Doad b130.
Yes, this solution saved my phone... And u can try flash with fastboot any partition (recovery, system....)
Odoslané z VNS-L21 pomocou Tapatalku
Thank you for your help, guys!
Yet, nothing happens when I disconnect the cable and try to reboot the phone while holding Vol+ and Power. Vol- and power or Vol+, Vol- and Power do not deal any better result unfortunately. The screen remains off.
I believe I should delete/flash something through fastboot, but I do not know what! I believe I have tried everything I could think of, and I am running out of ideas...
Yet the phone is accessible through fastboot, so all hope is not lost, right?
Well, I have good news: I managed to reflash my phone by following this thread: https://forum.xda-developers.com/hua...green-t3485836
You have to download and use DC-Phoenix to flash a stock firmware to the phone.
The bad part is that it is a paid service that will cost you 15€... but for me it was worth it in comparison with having a dead phone.
I wonder why no one has come up with a free equivalent to DC-Phoenix yet?
Hello everyone!
First of all - this is my first post here, so if I'm doing something wrong, please, correct me.
Three days ago i dropped my ALE-L21 into water closet (don't ask). I dismantled it and put into rice for 2 days. Today I decided to check if phone will start normally, but there is a following problem:
The phone is stuck into bootloop - after turning it on I see only the brand logo and after every 1 minute it vibrates for a while, the screen goes black and the brand logo appears once again. I tried to get it into recovery mode, but nothing happens. (none of button combination: holding power, power+volup or power+volup+voldown works. The phone always try to reboot)
I plugged it to PC and the only thing I can do is to get into fastboot (bootloader unlocked, phone rooted, but USB debugging is off, so adb doesn't see the device).
Any ideas of how can I fix that? Maybe just volume button is broken? Should I try to clean volume&power flex? Maybe there is an alternative solution to turn usb debugging mode on? Then I could try to recover it manually, with adb.
Flash the correct firmware in fastboot.
Szabi01 said:
Flash the correct firmware in fastboot.
Click to expand...
Click to collapse
How can I do that?
I can run fastboot by power+vol_down, but probably USB-debugging is turned OFF. ADB doesn't see any devices plugged in.
turbotramp said:
How can I do that?
I can run fastboot by power+vol_down, but probably USB-debugging is turned OFF. ADB doesn't see any devices plugged in.
Click to expand...
Click to collapse
If you pc doesn't recognize phone with adb or fastboot commands in fastboot you propably have some broken hardware.
But you can try this stuff if it recognize something.
Go to fastboot and flash TWRP with "fastboot flash recovery (recovery_filename_here).img" then try power + vol up, if it doesn't work you can try to extract UPDATE.APP app and flash system.img, boot.img, cust.img in fastboot. If TWRP works use this to re-install stock firmware https://forum.xda-developers.com/honor-4x/how-to/install-emui-4-1-4x-4c-g-play-g-play-t3515702.
Ok. Fastboot recognized my device, so I installed everything what you mentioned. Everything went 'OKAY', as it printed in cmd, but still there is no change. Whatever I am doing it freezes at brand logo and after some time reboots.
But I used branded ROM, which I downloaded from huawei website - it is the only one that not gives me "balong" error.
Any ideas before I give back my Huawei to the official service? Maybe there is some way to diagnose volume_up button?
Hi, I bought a second hand zte axon 7 a2017. I want told it was rooted or anything. Power button is squashed in so got it for cheap so bought it. Phone runs fine on stock rom and for restarting etc I use mi pop and power button can still be used by poking it hard at an angle with stick etc. I'm familiar with rooting, flashing etc but it is the first time I'm using zte so it's bit different.
Issue is I want to root it to get rid of bloatware etc. I downloaded Root Check app and it says it is rooted and busybox is installed but there is no super user app. Funny thing is I have no means to check if bootloader is unlocked and can't even boot to bootloader mode as it just gets stuck at zte logo when I try to boot to bootloader mode from recovery mode. I get to recovery mode by restarting the phone from mi-pop and holding the volume up button. I don't even think there is custom recovery installed too which I don't know how that's possible as my understanding was custom recovery needs to be installed earlier in order to root.
Can someone please throw some light and give me some guidance. I want to go full stock but rooted and want custom recovery too just so that i can make a nandroid back up.
I'm on Mi favor 4.0
ZTE_A2017V1.0.0.B07.0
Thank you in advance
I'm on the US variant so I'm not too familiar with yours. I would suggest starting from stock, and downloading MiFlash, and the latest MiFlash edl package for your variant.
Jay_Nz said:
Hi, I bought a second hand zte axon 7 a2017. I want told it was rooted or anything. Power button is squashed in so got it for cheap so bought it. Phone runs fine on stock rom and for restarting etc I use mi pop and power button can still be used by poking it hard at an angle with stick etc. I'm familiar with rooting, flashing etc but it is the first time I'm using zte so it's bit different.
Issue is I want to root it to get rid of bloatware etc. I downloaded Root Check app and it says it is rooted and busybox is installed but there is no super user app. Funny thing is I have no means to check if bootloader is unlocked and can't even boot to bootloader mode as it just gets stuck at zte logo when I try to boot to bootloader mode from recovery mode. I get to recovery mode by restarting the phone from mi-pop and holding the volume up button. I don't even think there is custom recovery installed too which I don't know how that's possible as my understanding was custom recovery needs to be installed earlier in order to root.
Can someone please throw some light and give me some guidance. I want to go full stock but rooted and want custom recovery too just so that i can make a nandroid back up.
I'm on Mi favor 4.0
ZTE_A2017V1.0.0.B07.0
Thank you in advance
Click to expand...
Click to collapse
Okay, couple o' things:
- If your bootloader is unlocked, there should be a screen when your turn on the phone that says 'Your phone can't be checked for corruption. Please lock the bootloader' which is there for around 10 secs. If you use the volume buttons from there you should be able to select recovery or bootloader
-It is possible that you don't even have a working bootloader mode. IN CASE THAT YOU DON'T HAVE THE SCREEN I PREVIOUSLY TALKED ABOUT, try with adb: install adb, enable usb debugging, authenticate in the phone, "adb reboot bootloader". If it reboots into the bootloader (Should say START in green plus some text) then you can unlock the bootloader. But follow a guide before attempting that, or you'll risk a brick
-Having the stock recovery doesn't necessarily mean that the phone is not rooted. If you have the stock recovery it could be because the previous owner simply rooted it, used it, then flashed the stock recovery and sold the phone like that. Which is really weird in itself
-What you should do to recover from this mess is use MiFlash. Find a package called "A2017_NOUGAT_FULL_EDL" (might have a version number somewhere, just use the most recent). Enable OEM unlocking and USB debugging, then issue "adb reboot edl". The phone seems off but it's not. Now unpack the file and install it to the phone with MiFlash.
After you reflash the system you can proceed with a guide. If you get the warning screen when you turn on the phone then your bootloader is already unlocked and you can proceed with installing TWRP (maybe via axon7tool) then flashing Magisk.
Hi all,
I've installed LineageOS on my mate 9, using their own tutorial, and with a stock recovery.
Everything ran smoothly for a couple of weeks. Today however my phone would not turn the screen on, just minutes after it worked fine. So, I rebooted manually by holding the power button.
Did not work, but instead: my phone is stuck on the 'your device has been unlocked and can't be trusted' + your device is booting now... screen. But it does not boot.
I can't go into the stock recovery mode, using power + volume up.
I can get into fastboot mode, but my pc (which I used to root my phone) does not recognise it using adb, while it did earlier. sometimes a fastboot command (fastboot devices) works and lists a code.
But if I try fastboot flash system and the filename for the lineageOS img, it sends the first package but does not seem to write, writing system 1/4 lasts for ever without anything happening. The phone also stays in the white fastboot screen during this event.
Can someone help me solve this? Is there a solution?
Mate 9
dekraan said:
Hi all,
I've installed LineageOS on my mate 9, using their own tutorial, and with a stock recovery.
Everything ran smoothly for a couple of weeks. Today however my phone would not turn the screen on, just minutes after it worked fine. So, I rebooted manually by holding the power button.
Did not work, but instead: my phone is stuck on the 'your device has been unlocked and can't be trusted' + your device is booting now... screen. But it does not boot.
I can't go into the stock recovery mode, using power + volume up.
I can get into fastboot mode, but my pc (which I used to root my phone) does not recognise it using adb, while it did earlier. sometimes a fastboot command (fastboot devices) works and lists a code.
But if I try fastboot flash system and the filename for the lineageOS img, it sends the first package but does not seem to write, writing system 1/4 lasts for ever without anything happening. The phone also stays in the white fastboot screen during this event.
Can someone help me solve this? Is there a solution?
Click to expand...
Click to collapse
In fastboot mode does it tell you the phone is still unlocked and frp is unlocked?
Newrooter22 said:
In fastboot mode does it tell you the phone is still unlocked and frp is unlocked?
Click to expand...
Click to collapse
Did not try that! It is at a repairshop at the moment, they feel it is a software problem, but I guess mainly because I dropped the word 'custom rom'.
I've got a couple clues that suggest it might be a fried chip: I get Command not allowed errors when trying several fastboot commands, and I also get a remote:flash write failure when I try to flash a ramdisk.img or system.img.
Hope to hear from the shop today or tomorrow, and will update afterwards!
I have this exact issue on my huawei y6 2018, i can access to the emui recovery mode, and have bootloader unlocked.
Hi, just bought a phone for my son secondhand, it's going to be sold again if I can't fix this! The phone was sold cheap as it had software issues (of course) so I figured I could fix these and get it going (install custom recovery, ROM etc). I'm slightly stumped at the moment, so maybe you can help me.
The phone's defaulting to the bootloader screen, lots of info on this but the key thing I noticed was that it says 'the device is locked status code: 2'.
Clicking 'start' takes me a 'warning unlocked bootloader screen' then it runs through the 'hello moto' startup screen and back to bootloader
Clicking 'recovery' - there is definitely no working recovery on it, I just a get the dead robot with 'no command' underneath.
Clicking 'Factory Mode' allows me so far through the startup (after the bootloader unlocked warning), and you can get so far through setting it up, but because the battery is so low (it's permanently on with the bootloader when plugged in) it never seems to charge up enough, and either way the screen freezes at or around the final setup steps and then it reverts back to bootloader. I thought if I got into developer options and security, I could enable the USB debugging, OEM unlock etc, but no go there.
I've installed Motorola USB drivers but it doesn't seem to be registering on the PC (Windows 10).
There is some suggestion on other forums (less reputable!) that the locked status code may mean the bootloader has been relocked, but this seems contrary to what the phone is telling me.
Any ideas welcome, thanks - it's a lovely phone, just not much use at the moment.
GitManMatt said:
Hi, just bought a phone for my son secondhand, it's going to be sold again if I can't fix this! The phone was sold cheap as it had software issues (of course) so I figured I could fix these and get it going (install custom recovery, ROM etc). I'm slightly stumped at the moment, so maybe you can help me.
The phone's defaulting to the bootloader screen, lots of info on this but the key thing I noticed was that it says 'the device is locked status code: 2'.
Clicking 'start' takes me a 'warning unlocked bootloader screen' then it runs through the 'hello moto' startup screen and back to bootloader
Clicking 'recovery' - there is definitely no working recovery on it, I just a get the dead robot with 'no command' underneath.
Clicking 'Factory Mode' allows me so far through the startup (after the bootloader unlocked warning), and you can get so far through setting it up, but because the battery is so low (it's permanently on with the bootloader when plugged in) it never seems to charge up enough, and either way the screen freezes at or around the final setup steps and then it reverts back to bootloader. I thought if I got into developer options and security, I could enable the USB debugging, OEM unlock etc, but no go there.
I've installed Motorola USB drivers but it doesn't seem to be registering on the PC (Windows 10).
There is some suggestion on other forums (less reputable!) that the locked status code may mean the bootloader has been relocked, but this seems contrary to what the phone is telling me.
Any ideas welcome, thanks - it's a lovely phone, just not much use at the moment.
Click to expand...
Click to collapse
OK, some progress, I have now unlocked the bootloader, so have the UNLOCKED Status Code:3 which is good, unfortunately has not yet helped with my issues. I can't use ADB, but MFastboot tool is working, so can run commands from that (hence me getting to that stage). Tried reinstalling firmware, may try and do this again now bootloader unlocked....
slightly further along...
GitManMatt said:
OK, some progress, I have now unlocked the bootloader, so have the UNLOCKED Status Code:3 which is good, unfortunately has not yet helped with my issues. I can't use ADB, but MFastboot tool is working, so can run commands from that (hence me getting to that stage). Tried reinstalling firmware, may try and do this again now bootloader unlocked....
Click to expand...
Click to collapse
I have now managed to flash stock firmwares using Mfastboot tool, but hasn't unfortunately fixed the boot up issues. However, I have now worked out how to access the recovery, by reading other posts on different Motorola phones:
boot to bootloader, power+vol down
in bootloader select recovery using the volume up/down buttons, press power button to select
phone boots into 'recovery,' showing the dead android with no command
at this point hold down the power and volume up, then release volume up but keep power held down
phones boots, by magic, into android recovery, where you can factory reset, wipe cache adb sideload and install from SD card
I now need to try and get a flashable recovery to sideload, as the attempts to flash it don't work for me. The OS I seem to be on is reteu 7.1.1, so I will try and go for a lower version, and see if that allows me to flash the custom recovery I desperately need.
But....things are improving slowly....:laugh:
GitManMatt said:
I have now managed to flash stock firmwares using Mfastboot tool, but hasn't unfortunately fixed the boot up issues. However, I have now worked out how to access the recovery, by reading other posts on different Motorola phones:
boot to bootloader, power+vol down
in bootloader select recovery using the volume up/down buttons, press power button to select
phone boots into 'recovery,' showing the dead android with no command
at this point hold down the power and volume up, then release volume up but keep power held down
phones boots, by magic, into android recovery, where you can factory reset, wipe cache adb sideload and install from SD card
I now need to try and get a flashable recovery to sideload, as the attempts to flash it don't work for me. The OS I seem to be on is reteu 7.1.1, so I will try and go for a lower version, and see if that allows me to flash the custom recovery I desperately need.
But....things are improving slowly....:laugh:
Click to expand...
Click to collapse
Never try to downgrade using stock firmware.
tyamamoto said:
Never try to downgrade using stock firmware.
Click to expand...
Click to collapse
OK thanks, I read that, but didn't realise it was a thing....should I be able to sideload a custom rom using ADB?