Related
Hey,
So i used the SRK tool to try and root my VIE-L09C40 (P9 Plus)
Something seemed to happended during the rooting procedure and when i entered e-recovery it said it had to Download a new version, but couldnt connect to internet via wifi.
Any ways it seemed to work after a while but now i have no keyboard at all, so i cant literally start my phone.
it starts, boots the EMUI 5.0 logo and goes through the information a terms, i click the ok button and thats fine.
Next it tells me to sign in to my wifi, i select my wifi and when i go to type the password all i have is google voice as a keyboard, ive searched and searched but cannot find a way around it, also the frp has tripped on phone so i cannot log in to my google account without a keyboard.
How can i get around this?
do i have to flash parts of firmware?
any help would be great, i sent it away to hauwei and they say warranty void due to software!, can only assume something wrong was flashed?
Waiting for phone to be returned now, please help
I had the exact same issue last night as well. No keyboard and only an option to enter details with voice.
Ended up with an essentially bricked phone. Couldn't find any info on the problem online, so I have to improvise.
I'm starting from scratch after formatting etc. using stock oeminfo, recovery and rolling back to Marshmallow. (fingers crossed ADB will let me, because it was giving me errors before)
Will let you know if I'm successful and the steps I took.
=====================
tolerant said:
Hey,
So i used the SRK tool to try and root my VIE-L09C40 (P9 Plus)
Something seemed to happended during the rooting procedure and when i entered e-recovery it said it had to Download a new version, but couldnt connect to internet via wifi.
Any ways it seemed to work after a while but now i have no keyboard at all, so i cant literally start my phone.
it starts, boots the EMUI 5.0 logo and goes through the information a terms, i click the ok button and thats fine.
Next it tells me to sign in to my wifi, i select my wifi and when i go to type the password all i have is google voice as a keyboard, ive searched and searched but cannot find a way around it, also the frp has tripped on phone so i cannot log in to my google account without a keyboard.
How can i get around this?
do i have to flash parts of firmware?
any help would be great, i sent it away to hauwei and they say warranty void due to software!, can only assume something wrong was flashed?
Waiting for phone to be returned now, please help
Click to expand...
Click to collapse
dmccort said:
I had the exact same issue last night as well. No keyboard and only an option to enter details with voice.
Ended up with an essentially bricked phone. Couldn't find any info on the problem online, so I have to improvise.
I'm starting from scratch after formatting etc. using stock oeminfo, recovery and rolling back to Marshmallow. (fingers crossed ADB will let me, because it was giving me errors before)
Will let you know if I'm successful and the steps I took.
=====================
Click to expand...
Click to collapse
Good luck, i did read that it might be possible to install the base firmware back to it and then update again.
Im sure we are not the only people this has happened to and if you succesfully do this, maybe consider making a full step by step guide so to help others.
Fingers crossed
:good:
Will do my best.. So far it's been a major. I've managed to flash a working stock ROM and boot up. But there are a few things to smooth out. Such as, I have no IMEI number now and the build is C900, also the bootloader is modified.
To get it to boot I had to use DC- Phoenix to flash a factory firmware(Chinese) which I had to pay for. Then I flashed a stock vie-l09c432b181 ROM over the top.
To repair the IMEI I'll have to use HCU, which I'll have to pay for as well. But that's ok. If I can get my original IMEI back, I can use the original unlock code I got earlier this year, otherwise I'll have to get a new one based on a new IMEI.
I can repair the bootloader and region code using twrp etc. so that's not a problem.
I'm actually using the phone to write his reply, so I can at least use it.
Once I have it all 100% working I'll try to put together a full step by step.
Cheers.
Well, I have a working phone. But, it'snot stable. Having trouble with mobile connection, sms, mms, 4g etc not staying connected. So wont be doing any write-ups just yet.
Not until it's stable.
I'm wanting to return it to complete stock now. And that requires trying to find an oeminfo file for C706 (New Zealand).
Will add more as I get there. Sorry.
I had the same problems. All I did is updated the phone with the firmware you want via Twrp . Be warned that it will replace the recovery back to stock. Also clear the cache and etc.
I had a similar issue with SRK tool, bootlooping, won't flash new firmwares, lost all the stock apps and diagnostic tools.
I'm now stuck on a TEST-KEYS build with no NFC or Bluetooth.
My solution was to throw the piece of junk in a drawer, forget about it and I went and bought a Pixel XL instead - a phone that is properly supported and gets updates quickly.
After much messing and a headache I finally got to c432b370
And everything back to normal
tolerant said:
After much messing and a headache I finally got to c432b370
And everything back to normal
Click to expand...
Click to collapse
How did you succeed?
I am stuck on TEST-KEYS but I am not able to flash other roms on it. When I go to recovery, the update process stops after a while
Sent from my VIE-L09 using Tapatalk
Hey,
I was running Android P Beta, and had an OTA update today.
As it's been said on the beta topic, it apparently put me back on Oreo (the pattern lock is different on P).
But now I can't unlock the phone with the pattern at boot. When I put it the right pattern, it gives me a black screen, and ask me to unlock again.
So nothing's coming up, no wifi, no backup etc.
Does anyone have an idea on how to solve this **** ?
Thanks guys.
Deeptwix said:
Hey,
I was running Android P Beta, and had an OTA update today.
As it's been said on the beta topic, it apparently put me back on Oreo (the pattern lock is different on P).
But now I can't unlock the phone with the pattern at boot. When I put it the right pattern, it gives me a black screen, and ask me to unlock again.
So nothing's coming up, no wifi, no backup etc.
Does anyone have an idea on how to solve this **** ?
Thanks guys.
Click to expand...
Click to collapse
Boot to Recovery mode. Wipe/factory reset and reboot system.
koschey_immortal said:
Boot to Recovery mode. Wipe/factory reset and reboot system.
Click to expand...
Click to collapse
Thanks for your answer.
I know I could do that, but I'd like to be able to get some data back first (like whatsapp messages).
Whichi is why I'm trying to find a workaround, but so far it's not really a success.
have you tried android unlock my phone method?
Go to google and sign in. Then go to find/locate my device and then check the option unlock my phone. It will help surely.
Styleshman said:
have you tried android unlock my phone method?
Go to google and sign in. Then go to find/locate my device and then check the option unlock my phone. It will help surely.
Click to expand...
Click to collapse
i think that OTA update on Android P is in real "Android 0 8.1 June Update", as mentioned here, if this true that's the reason why you have problems
Hi everyone, some weeks ago I converted my A2 in 6X because I wanted to test MIUI. Yesterday, dealing with an update my phone get into a bootloop. Well, I used MiFlash to fix it but I selected "flash and lock" (yes, I know, I'm stupid).
The main thing is that I'm in a Chinese ROM with lock bootloader and when I try to unlock it I get error 86023.
I dont know what to do. I've thought about test point to flash Xiaomi.eu but I'm not sure bcause the bootloader is locked.
Someone with a posibble solution? Thanks
Welcome to the Club
Same thing happened to me.
You can now choose between China Developer or Stable.
I tried many progs and tutorials to unlock the bootloader but no way.
If you need GooglePlayStore, CalenderSync and ContactsSync:
https://androidfilehost.com/?fid=818070582850489460
I'm now on stable V10.3.6.0.PDCCNXM and all is working quite well.
rafamb281 said:
Hi everyone, some weeks ago I converted my A2 in 6X because I wanted to test MIUI. Yesterday, dealing with an update my phone get into a bootloop. Well, I used MiFlash to fix it but I selected "flash and lock" (yes, I know, I'm stupid).
The main thing is that I'm in a Chinese ROM with lock bootloader and when I try to unlock it I get error 86023.
I dont know what to do. I've thought about test point to flash Xiaomi.eu but I'm not sure bcause the bootloader is locked.
Someone with a posibble solution? Thanks
Click to expand...
Click to collapse
It didn't happened to me for myself, but I just asked this question to get better knowledge about bootloader stuffs:
As I understood the current problem is this:
You need to unlock your bootloader again, there is just (as much as I know) 2 ways to approach, which both of them will not help you:
1. Unlocking as a A2 : but your device is not a A2 anymore, so the device will not be unlocked by this method.
2. Unlocking as a 6x : but this one won't be successful either since the dedicated unlocking program asks for a real 6X device with a registered IMEI number by factory, which in your case is NOT.
So, you will be left just with the options that need no Unlocked Bootloader, as mentioned above, like Chinese Stable versions. ( That in my opinion it does NOT sound awful. )
(BTW, every day comes with new procedures, maybe you can find a new method to unlocked the bootloader again, there was times that many expertise told, after stucking in ARB4 trap, you just need to find a suitable Trash for your device!, but now we all know that there is plenty new ways to deal with it).
sz.hatef said:
It didn't happened to me for myself, but I just asked this question to get better knowledge about bootloader stuffs:
As I understood the current problem is this:
You need to unlock your bootloader again, there is just (as much as I know) 2 ways to approach, which both of them will not help you:
1. Unlocking as a A2 : but your device is not a A2 anymore, so the device will not be unlocked by this method.
2. Unlocking as a 6x : but this one won't be successful either since the dedicated unlocking program asks for a real 6X device with a registered IMEI number by factory, which in your case is NOT.
So, you will be left just with the options that need no Unlocked Bootloader, as mentioned above, like Chinese Stable versions. ( That in my opinion it does NOT sound awful. )
(BTW, every day comes with new procedures, maybe you can find a new method to unlocked the bootloader again, there was times that many expertise told, after stucking in ARB4 trap, you just need to find a suitable Trash for your device!, but now we all know that there is plenty new ways to deal with it).
Click to expand...
Click to collapse
not the imei, it asks for 6x serial number which device is a2. you have to find someone who has authorized mi account to unlock this device. it is only way for now
q0kHaN said:
not the imei, it asks for 6x serial number which device is a2. you have to find someone who has authorized mi account to unlock this device. it is only way for now
Click to expand...
Click to collapse
And how I can find someone with one?
rafamb281 said:
And how I can find someone with one?
Click to expand...
Click to collapse
Authorized Customer Services, or a friend who works there
It is very possible that they can restore your phone (and as well your bootloader) as what it was in factory.
sz.hatef said:
Authorized Customer Services, or a friend who works there
It is very possible that they can restore your phone (and as well your bootloader) as what it was in factory.
Click to expand...
Click to collapse
R u talking about contact with Xiaomi? Or another service?
I tried it here http://unlock-unbrick.com/, but they also couldnt help me.
rafamb281 said:
R u talking about contact with Xiaomi? Or another service?
Click to expand...
Click to collapse
Yes, exactly.
Hello my friends, i managed to unlock the bootloader of my converted A2/6X.
I tried several times to switch from stable china to developer china but from 9.8.15 to 9.9.3 no one worked.
After installing one of the developer roms, the phone only shows the boot screen for 2 seconds and turns off, with charger it boots endlessly or shows the green battery symbol after some minutes.
One thing that works, is using a rubber band to fix "Vol+" and connect phone via usb or charger, mostly after 5-10 minutes it will enter the "Miui-Recovery", then you can start "Mi-Assistent" in the "Miui-Recovery" and flash back the stable china, so luckily no need of EDL.
After flashing the last 9.9.3 rom and the phone was all screwed up, again. I tried the original "miflash_unlock-en-2.2.624.14" and it worked.
I have done this "thousand" times before with all available unlock tools I found but never succeeded before.
Download: miflash_unlock-en-2.2.624.14
https://xiaomifirmware.com/downloads/download-mi-unlock-2-2-624-14-windows/
https://androidfilehost.com/?fid=889764386195916630
Now I tried to boot into recovery “fastboot boot twrp_wayne.img” but it didn't work, because the phone reboots or turns off after 2 seconds.
So I flashed the china stable via fastboot (worked), let it boot up, no setup, reboot to enter fastboot and flashed successful the orangefox-twrp.
Hope somebody can also unlock his bootloader or maybe it was just luck.
puxxi2004 said:
Hello my friends, i managed to unlock the bootloader of my converted A2/6X.
I tried several times to switch from stable china to developer china but from 9.8.15 to 9.9.3 no one worked.
After installing one of the developer roms, the phone only shows the boot screen for 2 seconds and turns off, with charger it boots endlessly or shows the green battery symbol after some minutes.
One thing that works, is using a rubber band to fix "Vol+" and connect phone via usb or charger, mostly after 5-10 minutes it will enter the "Miui-Recovery", then you can start "Mi-Assistent" in the "Miui-Recovery" and flash back the stable china, so luckily no need of EDL.
After flashing the last 9.9.3 rom and the phone was all screwed up, again. I tried the original "miflash_unlock-en-2.2.624.14" and it worked.
I have done this "thousand" times before with all available unlock tools I found but never succeeded before.
Download: miflash_unlock-en-2.2.624.14
https://xiaomifirmware.com/downloads/download-mi-unlock-2-2-624-14-windows/
https://androidfilehost.com/?fid=889764386195916630
Now I tried to boot into recovery “fastboot boot twrp_wayne.img” but it didn't work, because the phone reboots or turns off after 2 seconds.
So I flashed the china stable via fastboot (worked), let it boot up, no setup, reboot to enter fastboot and flashed successful the orangefox-twrp.
Hope somebody can also unlock his bootloader or maybe it was just luck.
Click to expand...
Click to collapse
Amazing Dude. [emoji108][emoji108][emoji108][emoji108][emoji108] Congratulations.
Most of the time I am the guy helping people out. This time I think I did something pretty dumb.
I have an old "beater" P9 plus that I was using as a casual gaming device. Most of the apps I was using were beginning to no longer be supported because for some reason the device NEVER updated. Any time I check for a possible update the phone stated it was up to date. After much searching I discovered that this device SHOULD have updated quite a few times.
I used firmware finder to find a supported update and the first one went somewhat unexpected. The firmware was downloaded and put in the correct folders but kept failing after 5%. I decided that the next thing to do was to find a cool rom and go through the process of unlocking and installing TWRP. I usually try to install the latest TWRP. This turned out not working at all so I went for an older version and it booted into TWRP, however it found the update and installed it!
I kind of wanted to keep it stock, but updated stock so I went for a bigger upgrade to Android 7 firmware. This only worked partially and (stupid and I know better) forgot to do a backup. I did not know that TWRP was gone and root was gone. The battery died and I rebooted like normal and there was a much improved interface. However, a good bit of stuff stopped working like bluetooth and the boot screen was in red stating the device can't be verified and ended up in something like a NOR905 test keys build. I did a backup, selected a downgrade package that was checked and "updated" to the downgraded firmware through Project Menu. It successfully stated it was 100% complete.
Now it is stuck on the boot screen for an unlocked device.
What works (or is possibly a good thing):
The hardware keys can get me to the bootloader (fastboot)
ADB recognizes the device is in fastboot
Phone is Unlocked
FRP is unlock
What doesn't work:
Everything else. All I have is fastboot and an unlocked bootloader. I can try to flash recovery but that never boots, it just stays suck on the recovery boot screen. The system will not boot at all.
UPDATE:
I broke down and spent the money to use the DC-Phoenix software to unbrick the phone. Several of the options for firmware did NOT work. The one file set that did work was to use this firmware:
VIE-L29_C900B101_Firmware_countryValue_Nonspecific_Android_6.0_EMUI4.1
Then use this as the customization:
update_data_C900B101_hw_default
The phone originally started out as VIE-L29C636B130. This changed it to VIE-L29C900B101 and is on EMUI 4.1 android version 6.
Now the fun part is going to see if I can find a version of TWRP that will work and see if I can root it. Maybe even try a custom ROM. We'll see though. The device is just an old beater for fun. But at least, she's not broken anymore. Guess I'll grab a beer and celebrate my "unbricked" device.
I need help too. So, I own a Moto G5s plus sanders. I unlocked its bootloader the day I got it. Didn't keep any backup and rooted it. I Also installed dot os based on android 11. But my 4G Volte connection was finicky. So, I decided to use a Volte zip patch. But, anyways I flashed the zip via TWRP and tried to reboot. But the phone didn't turn on after that. After a few minutes to my shock I understood that I hardbricked my mobile. No button combos, nothing worked. Anyways in my desperation I found a YouTube video showing the use of blankflash to revive a phone and lo and behold I used the procedure to again restore my device. It booted to the fastboot interface. But my happiness was short lived. My baseband was unknown at this point and the bootloader was I dunno downgraded to 0.5 inplace of 2.12. But, more importantly the unlock status was lost. I unlocked it again and all went well. I could even flashed TWRP. but then I realised I couldn't upgrade my bootloader. I couldn’t do anything. It's always gives a "security downgrade", "preflash validation failed" and "permission denied" error. I even tried RSA official rescue tool from Lenovo but even it was unsuccessful. It was never unsuccessful before that. Not even with a unlocked bootloader. I researched for days and tried custom ROMs. I flashed stock images. Nothing brought back my baseband and IMEI. When I type "fastboot oem unlock critical" it gives me permission denied error with a message. "Need OEM signed bootloader." I think the blankflash bootloader is the root of all evil. I need to change it and therefore I need to enter the edl mode. I have tried all adb commands and fastboot commands. The phone reboots okay after those commands but never goes into edl mode whatsoever. I am also ready to do a controlled hardbrick of my device to go into the edl mode so that I can use my device again with a proper bootloader and a properly working fastboot. Please help
i think this vid will help
Greetings everyone. Sorry if I posted this in the wrong forum. Please move this in appropriate forum if I made a mistake. Believe me, for the last 7 days I have searched all of xda and internet, followed innumerable guides, FAQs and workarounds and none worked. So, as a last resort I am starting this thread
Device: Motorola Moto G5s Plus XT1804 ......4GB _64GB variant
Problem: 1) Baseband not found (unknown) Original Baseband: M8953_52.61.07.98R SANDERS_INDIADSDS_CUST
2) IMEI 0 (Sim cards are not detected).
I bought this refurbished phone about an week ago after my last LG went kaput. I was happy by the build quality of the phone. But it only ran Android 8.1 Oreo. So, I decided to put a custom ROM in it. I am not exactly a newbie to the world of CyanogenMods, Lineage OSes and Pixel Experiences. Or, so I thought. Anyways, after a lot of searching I finally decided on Dot OS 5.2 Official Android 11 version. The ROM looked very pleasing and the reviews looked positive. So, I got the unlock key from Motorola website, unlocked the bootloader, put in official TWRP recovery in it. Everything went like a breeze and in all that excitement I forgot to take a backup of the persist, efs and other partitions. A very costly mistake it seems. DotOS booted fine and looked really fresh till I found that there is a small cross near the SIM card network signal triangle up righthand side corner and the signal is only LTE and not VOLTE. I was using a Vodafone Sim card at the time. Although VOLTE option was enabled in SIM settings. To confirm my doubts regarding VOLTE I switched to a JIO Simcard and alas I was not able to make a call without redirecting through the horrid JIO calling app. VOLTE was indeed not working. So, I looked up for a fix and I found a Volte ZIP file from here https://www.google.com/url?sa=t&sou...0QFnoECBAQAQ&usg=AOvVaw0YgJvCjQWXXV8WQSJkxBOK . This was the starting of my troubles. I flashed the universal VOLTE fix zip from TWRP and it flashed fine. On rebooting, I found to my shock that my phone was not turning on. I pressed and held the power key and there was no sign of life. I couldn’t go to the fastboot bootloader or recovery. Only the white led blinked at the top when connected to the charger. My phone was apparently hard bricked. I searched frantically for a solution in this forum and YouTube wherein I found that one can bring it back to life by doing a blankflash. Found the blankflash file here https://www.google.com/url?sa=t&sou...wQFnoECAsQAQ&usg=AOvVaw1eVdBWGVFr8aiqLdP-ZkeT followed the instructions and it flashed my bricked device back to fastboot. I was relieved for a moment but the next I found that the Bootloader version has downgraded from BL C2 07 to BL C0 05. I knew something was wrong as bootloader downgrade shouldn't be possible. Also the unlock and rooted status were also lost and the baseband was unknown at this point. Anyways the device was recognised as a fastboot device and I tried to flash the stock ROM latest version using the fastboot. But, only then I realised there was something wrong with the bootloader. It gave errors like security downgrade, permission denied, preflash validation failed, remote command failed. At this point I was truly confused and worried. Why would it think the latest bootloader to be a security downgrade to a supposedly old bootloader and prevent me from flashing it. However it did flash the other files like gpt.bin for partition, oem.img, boot.img, system.img sparsechunks and everything else. I booted back to Android 8.1 Oreo and everything seemed working except my IMEI now read zero and my Simcard was not recognised by the device. After that I again unlocked my bootloader. Somehow the original unlock key worked and the bootloader screen said flashing unlocked but the bootloader didn't behave like an unlocked bootloader. The TWRP installed fine but couldn’t install the latest Pixel Experience. The flash screen said PE 11 was for Sanders and my device is (blank no name). I tried both the normal and plus and both behaved similarly. Lineage OS unofficial builds behaved similarly. I again tried Dot OS and Arrow OS and both installed fine except there was no signal. For a moment I tried to forget about the bootloader but concentrated on recovering my IMEI and Baseband but I couldn’t. For nearly 5 days I tried different guides including a detailed guide using Validus Sanders ROM but none worked. My EFS folder has files around 12 megabytes but my Persist seems deleted at zero bytes. The IMEI keeps changing between null, zero and unknown depending on the 20 something ROMs I tasted on this device. At this point, I am at a loss. This was to be my main phone and I am financially crunched. I can't buy another phone right now. I think that blankflash bootloader is corrupted and it is giving me permission denied errors. Even Magisk won't work properly. I even tried using the official rescue and smart assistant tool by Lenovo and it failed at 47 percent. I tried in different computers and Win7 to Win 11 OSes but it was of no use. I also tried getting a QCN file but I couldn’t get one for the device to recover the IMEI. Please suggest something if anyone of you can save this poor device of mine. Thanks in advance
Raghaov said:
i think this vid will help
Click to expand...
Click to collapse
Thanks for the quick reply but my phone is soft bricked now. It was hardbricked and I uses a faulty blankflash bootloader to bring it back to life. My device is softbricked now. I have lost my baseband and I have no IMEI. I cannot take calls and no mobile data. Can you show me a way to go to edl mode in my device. Thanks again.
can your phone turn on if yes can you root it with magisk
if yes then pls tell me i will tell you
I can do everything except calling and mobile data. Yes, I have rooted with Magisk and have root access. But my baseband is unknown and my IMEI is showing zero. I can't call or access mobile data. Although I can use wifi
I have tried what is shown in this video already. Didn't work
I think the blank flash bootloader was corrupt or of a different region.
so go to magisk manager and on top-right corner you will see setting click the button right next to it and click on reboot to edl
I didn't even knew that. Trying asap. Will update
Doesn’t work. Reboots back to system.
Updated Magisk to latest and tried both edl and download mode like you said brother. Everytime boots back to system. Am I missing something. The phone was not connected to the PC at the time
I am on stock Oreo now. Rooted and twrp installed
An interesting observation while installing Xposed, it gave an error that the device is not rooted properly
I have an untouched dump file for my model. The whole thing. Could you please guide me how I can restore my smartphone from that.
can you flash it through adb sideload fastboot twrp etc
I don't know but I sold the device. I bought a new one. Thanks @Raggaov for the help.
you're welcome