Hi all,
Got a mobile that we dont know the previous Gmail account this was registered with. Therefore, I need to bypass the FRP to recover the mobile and use it for testing purposes. Accidentally, I upgraded it to EMUI 10 and after fixing several softbricks, I have no clue how to downgrade it to EMUI 9.
Goals:
Rollback EMUI 10 to 9 on Huawei 20x C185
Abuse flaws on EMUI 9 to bypass FRP
Do all via Linux tools (preferably console)
Firmware
EVR-L29 C185 EMUI 10
https://mega.nz/#F!zRUGFKyZ!je09cCOdJRPePDvykLwJCQ
http://www.mediafire.com/file/m7l6xlqe4se0u7s/dload.zip/file
Fail attempts
Enter upgrade mode and dload a previous C185 EMUI 9.0.x or EMUI 9.1.x (via OTG cable + microSD card). This always produces the same error: Software upgraded failed!
Try to change country to have chances to flash different firmware.
Logs:
Code:
> fastboot oem get-build-number
...
(bootloader) :EVR-L29 10.0.0.180(C185E6R3P3)
OKAY [ 0.011s]
finished. total time: 0.011s
> fastboot getvar vendorcountry
vendorcountry: hw/meafnaf
finished. total time: 0.019s
Any idea?
Try Hisuite
sunrider07 said:
Try Hisuite
Click to expand...
Click to collapse
hey @sunrider07,
apparently you need to enable HDB options to use HiSuite, right? Tested HiSuite on Linux emulated via Wine. I was able to use the Huawei tool but I couldn't hook up the mobile to the app. Have you used HiSuite to downgrade the bootloader? If so, it is really needed to have adb connection? Remember my phone is protected via FRP.
This is the way to enable HDB (Huawei ADB dev options):
4. Go to device setting and enable USB Debugging. You can follow our guide on how to enable USB Debugging on Huawei phones.
5. Connect HiSuite to your mobile.
6. HiSuite will automatically shows a system update on your device.
Click to expand...
Click to collapse
Being blocked by FRP, HDB switch cannot be enabled so i am not sure if HiSuite can be used
{
"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"
}
My phone is fully stock and unmodified.
And yes, HDB must be enabled for the app to connect.
I was able to downgrade my phone just two days ago and everything works as expected
sunrider07 said:
My phone is fully stock and unmodified.
And yes, HDB must be enabled for the app to connect.
I was able to downgrade my phone just two days ago and everything works as expected
Click to expand...
Click to collapse
Thanks for your answer. Unfortunately, I do need to find another way to perform a downgrade on the bootloader and base image to EMU 9.0 where there are public and known vulnerabilities to overcome FRP. Otherwise, I will need to wait until a FRP bypass is public, or reverse engineering the HiSuite software to find some fastboot commands to see if I can leverage any of these. It seems I am stuck with it.
Apparently I found this video from 5 days ago: https://www.youtube.com/watch?v=USvi-1O2Y6o
Anyone knows well the mode USB upgrade?
--
mac231us said:
I saw that too. I too need to downgrade but cannot as usb is not connecting. I can connect to one of the Hisuite versions through wlan option but it cannot be used to change the system (only through usb). Cannot do system recovery (says take it to service center)
Yes video shows if you go into usb mode through recovery (which I can) you can use the MRT tool to flash the rom. I plan to look into it. Otherwise I might just take it to a service center in an upcoming overseas trip (still almost 2 months away)
Click to expand...
Click to collapse
Do you know where to download this MRT tool? It seems like super unprofessional tool without github repo.
mac231us said:
Separately in my case-The device is not recognized when connecting through usb to the computer (usb ports, cable, windows version, drivers etc all tried-the device type and name is not recognized. OTG usb works but that is only for backups, backup restore and dload method to upgrade-which cannot be used to downgrade to 9.1 or 9.0 from 10.0) Fastboot commands are severely limited in 10 as my device country vendor is unknown. The device works fine otherwise (calls, mms, apps, internet, themes) Device cannot be registered at Huawei as unknown device though I can register in themes. With dload I can switch back and forth between 10.0.0.180 and 183 or even a lower 10 but not to 9 series.
Click to expand...
Click to collapse
Dont own a Windows10 laptop to use HiSuite, looking for one to see if I can connect it via WiFi. Did you mention you can use all these calls, mms, apps, internet, themes? In this case, we have different issue.
Can you run this command?
Code:
$ fastboot getvar vendorcountry
vendorcountry: hw/meafnaf
finished. total time: 0.019s
mac231us said:
Surprised there is no way to fastboot erase and install firmware-I heard you need a service rom to completely redo the phone.
Click to expand...
Click to collapse
The MRT tool must use a fastboot command too. We can always reverse this tool to extract the command. Do you have the tool?
In this video there are downloading links:
MRT sw
--
anyone able to bypass the frp?
Related
hello , all of you.
i'm from Iran and i repair my imei successfully!
i want to share my solution way to you , my dears!
if your imei repaired with my way , please pray for me.
solution:
you need to use digma sofia (phone tool 191).
first , root your phone.
second , install intel drivers for your pc
thirth , use adb to set your phone to diag mode.with this command: adb shell
su (after enter this , grant supersu from phone)
setprop system.at-proxy.mode 1(1 for sim 1 and 3 for sim2)
After this commands , in pc's device manager , you see the intel virtual android port.if you see , continue.
open phone tool and use it with sofia's pdf help.
Note:for who persons that port dont open (freeze in settings(1/3) : You are using android 6.Yes?!
Android 6 dont allow to ports to open.you will need to downgrade to android 5.just in android 5 you will be able to use phone tool and ports will be active.
My this Note , saves you life , man.yes?!i tried one week in android 6 and ports Dont active.Dont try my brother.just Downgrade to 5 and use phone tool.
Downgrade:
Download this downgrade firmware with your pc and transfer it with cable to your phone.unplog cable and system will be show notification to update.accept it.or you can use adb sideload or use sd card update wia recovery.just flash that downgrade zip file and you will be in lollipop.after use phone tool in lollipop and repair imei with that , upgrade to marshmallow again with above way and use factory reset after upgrade!
Downgrade m to l firmware:
search google: how to downgrade asus zenfone 2 and download UL-Z00A-WW-52.20.40.196-user.zip from asus site.
Note: for sim 1 , use setprop 1 and for sim 2 , use setprop 3
i'm from iran!
Thanks
Worked?!
AlexBBxelA said:
Thanks
Click to expand...
Click to collapse
hello.youre welcome.it worked for you bro?!
rezasedgi said:
hello.youre welcome.it worked for you bro?!
Click to expand...
Click to collapse
it works for everyone ze550ml as well as ze551ml. Do keep few things in mind.
sometime tool have conflict with drivers. if phone tool hangs or do not work. uninstall all drivers. restart pc and install asus usb drivers from asus website. and use again.
do use setprop 1 and 3 as suggested in thread.
if still fails flash developer rom and try again
sukhwant717 said:
it works for everyone ze550ml as well as ze551ml. Do keep few things in mind.
sometime tool have conflict with drivers. if phone tool hangs or do not work. uninstall all drivers. restart pc and install asus usb drivers from asus website. and use again.
do use setprop 1 and 3 as suggested in thread.
if still fails flash developer rom and try again
Click to expand...
Click to collapse
no brother.dont need to flash developer room , if your corrent room is root.
just put phobe in diag mode.with command : adb shell
su (after enter this command , grant root access from phone)
setprop system.at-proxy.mode 1(1 for sim 1 and 3 for sim2)
after this command , phone connects to pc with android virtual port(in device manager , in ports , it will be shown).this way is just work in android 5.if you are in android 6 , you must downgrade to android 5 and try.port will be open with phone tool and it dont be freeze in settings(1/3).
about drivers: drivers must be intel soc drivers.in windows 7 you install that drivers normally.in windows 8 and 8.1 and 10 you must disable driver signature(search google for that).
rezasedgi said:
no brother.dont need to flash developer room , if your corrent room is root.
just put phobe in diag mode.with command : adb shell
su (after enter this command , grant root access from phone)
setprop system.at-proxy.mode 1(1 for sim 1 and 3 for sim2)
after this command , phone connects to pc with android virtual port(in device manager , in ports , it will be shown).this way is just work in android 5.if you are in android 6 , you must downgrade to android 5 and try.port will be open with phone tool and it dont be freeze in settings(1/3).
about drivers: drivers must be intel soc drivers.in windows 7 you install that drivers normally.in windows 8 and 8.1 and 10 you must disable driver signature(search google for that).
Click to expand...
Click to collapse
are you trying to increase your post counts? seems you didn't read what i posted. i was just posting tip not seeking any clarification. and as u said no need to flash service rom. i wasn't saying you definitely need to flash service rom. i said if above methods fails or give errors then only flash service rom and try again.
sukhwant717 said:
are you trying to increase your post counts? seems you didn't read what i posted. i was just posting tip not seeking any clarification. and as u said no need to flash service rom. i wasn't saying you definitely need to flash service rom. i said if above methods fails or give errors then only flash service rom and try again.
Click to expand...
Click to collapse
yes you are true!my mistake.i'm sorry man!
Hello guys, i really hope someone can help me. I do al step, unlock bootloder, root, and flash service raw file. (of course i installed all kind of driver). Phone tool software not connect to the port. i have the intel port as i saw on youtube or on this forum and several discussion, but not work. i also tried with a windows 10 and windows 7 64bit . nothing to do. there is a solution?
Not work for me
IMEI "null"
Freeze in "Try different settings 1/3", but I use Android Lollipop and installed all drivers necessary.
I from Brazil, I no speak english, I am sorry for me english.
Help me please!
1.Need selinux permissive
2. On Android 7.1.2 based not working, need 6.0.1- 5.0
3. If freeze then need delete /config folder froom root filesystem then reboot and try again
hi my friends, I do all the steps, I did the downgrade and used Digma Sofia, I put both imei Sim1 and Sim2 but only change the Sim 1, the sim 2 keep same, I repeat the process but I dont make change the imei sim2
BORETS24 said:
1.Need selinux permissive
2. On Android 7.1.2 based not working, need 6.0.1- 5.0
3. If freeze then need delete /config folder froom root filesystem then reboot and try again
Click to expand...
Click to collapse
That didn't work with me bro
BORETS24 said:
1.Need selinux permissive
2. On Android 7.1.2 based not working, need 6.0.1- 5.0
3. If freeze then need delete /config folder froom root filesystem then reboot and try again
Click to expand...
Click to collapse
Serial lost (0123456789ABCDEF), i need restore the valid serial
larguiman said:
hi my friends, I do all the steps, I did the downgrade and used Digma Sofia, I put both imei Sim1 and Sim2 but only change the Sim 1, the sim 2 keep same, I repeat the process but I dont make change the imei sim2
Click to expand...
Click to collapse
adb Shell
su
setprop system.at-proxy.mode 1(1 for sim 1 and 3 for sim2)
setprop system.at-proxy.mode 3
and try again
when i connect the phone as intel virtual port, "access denied" so imei can not be changed
{
"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"
}
Don't get hung up on the confirmation, just enter the first 13 digits of the imei number and press the "execute" button
Hello guys,
I received the following unbrick tool from my supplier in Shenzhen - China and wanted to share it with you since I noticed that many people are desperate to fix their RM6 and swap it to EU.
The process is super easy:
1) Download & extract the following .zip
https://mega.nz/file/ntBSxDKa#h9vUPGoWVyqtyDYWYmSgz8bE1_vNimBMAqTp9csvv-w
2) Make sure all the drivers are installed correctly (Qualcomm, EDL etc...)
3) Open the MiTool application
4) in MiTool, select the folder images
5) Put your phone in EDL mode
6) Once connected, Click flash - the brushing process will start automatically.
7) Once done, force reset and VoilĂ !
There's an alternative as well: MultiportQLoader
I haven't tried it myself, feel free to try it and share the steps.
Im sorry if any details aren't clear, but I'm typing this while driving xD
Good luck and would appreciate a shout-out on insta @Out.Geeked ^^
THANK YOU SIR
To ask a dumb question, but is this only the 6 or for the pro as well?
Works for both
Thank you so much, it work after someone help me erase flash
Outgeeked.net said:
Works for both
Click to expand...
Click to collapse
Yeah I checked the model number against the box it came in and gave it a shot, now it shows the RM logo and then reboots to the bootloader lmao this phone legit hates me
*edit*
So I think either I'm doing something wrong or this phone is actually messed up. Checked the drivers, tried 2 other cables, all my USB ports and still all it does is briefly show the white "System Rebooting" screen and then the RM logo for about 20 seconds and then reboots to fastboot/bootloader.
MiFlash shows "couldn't find flash script" but otherwise looks like it goes through the reflash process completely but QLoader always fails with an error "Unknown chunk type cac2"
Does this unbrick method require the bl to be unlocked?
anyone lost their imei after doing this? hahahha
i did lost my imei, but manage to repair it but... it still doesnt detect mobile network idk what to do now lol
Nocturne Seigneur said:
anyone lost their imei after doing this? hahahha
i did lost my imei, but manage to repair it but... it still doesnt detect mobile network idk what to do now lol
Click to expand...
Click to collapse
Did you ever find a way to recover your IMEI? Turns out that I'm in the same situation as you with a lost IMEI
CyberWolf92 said:
Did you ever find a way to recover your IMEI? Turns out that I'm in the same situation as you with a lost IMEI
Click to expand...
Click to collapse
loool welcome to the club xD, I didn't found any solution yet, i will tell u once confirmed, for now i can write imei but mobile network still not functioning
Does it actually work?
According to the file name, it's EU V3.10.
I thought we should apply the NA/Asia version.
cannon3025 said:
Does it actually work?
According to the file name, it's EU V3.10.
I thought we should apply the NA/Asia version.
Click to expand...
Click to collapse
yes it does work, some ppl lose imei some not idk why, mine lose imei and cant connect to any mobile network right now T^T
after u unbrick it, u can flash via local update to v4.13 i did that working fine
Nocturne Seigneur said:
yes it does work, some ppl lose imei some not idk why, mine lose imei and cant connect to any mobile network right now T^T
after u unbrick it, u can flash via local update to v4.13 i did that working fine
Click to expand...
Click to collapse
After you update to V4.13, your phone still no IMEI right?
How about flashing it again?
cannon3025 said:
After you update to V4.13, your phone still no IMEI right?
How about flashing it again?
Click to expand...
Click to collapse
its gone, forever lol
i just gave my phone to someone else to fix this, if he can.
[Guide] Restore Lost IMEIs / Repair Network or Radio Issues
I accidentally restored TWRP backup of another Zuk Z2 phone on my new pgone and in this process over-wrote the EFS partition. This left me with a phone having no IMEI, no mac for Wifi and Bluetooth. Effectively No Network on phone. Worried, I...
forum.xda-developers.com
this maybe work, havent test it out
Since we have the partition layout & the correct firehose, it should actually be a good practice by anyone wanting to play with their phone (BL unlock, root, dev, etc) to first dump the critical partitions.
That way, you can always restore. Example: EFS, misc, persist, etc.
Thanks for your help
When I use MiFlash shows "couldn't find flash script"
Can you please help
My RM6pro restarting all time to fastboot mode after I tried to relock bootloader and oem
Now I need to solve this issue by using this tools
I am beginner
Thanks
Same issue for @CyberWolf92
Alaryani said:
Thanks for your help
When I use MiFlash shows "couldn't find flash script"
Can you please help
My RM6pro restarting all time to fastboot mode after I tried to relock bootloader and oem
Now I need to solve this issue by using this tools
I am beginner
Thanks
Click to expand...
Click to collapse
Select the images folder and then hit flash.
Mine is alive again, no more problems.
I think I know why a lot of people have probably bricked their device after flash from CN to Global. If you do a local update, let the device REboot until the end. After the restart it uses the update.zip again. I think a lot of people did a factory reset immediately after the reboot (like me in Recovery) and the system can no longer find the update.zip.
Therefore, let the update run through, reboot until you are back in the system. Then you can do a factory reset.
Outgeeked.net said:
Select the images folder and then hit flash.
Click to expand...
Click to collapse
When I selected images folder shows "couldn't find flash script"
{
"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"
}
And when I go to edl mode my phone disappeard from list devices in MiFlash.
but still showing in driver manger
What driver needs for this issue "Make sure all the drivers are installed correctly (Qualcomm, EDL etc...)" what else I need?
also when i did it on fastboot mode i face this massge
Alaryani said:
When I selected images folder shows "couldn't find flash script"
View attachment 5329645
And when I go to edl mode my phone disappeard from list devices in MiFlash.
View attachment 5329643
but still showing in driver manger
View attachment 5329647
What driver needs for this issue "Make sure all the drivers are installed correctly (Qualcomm, EDL etc...)" what else I need?
also when i did it on fastboot mode i face this massge
View attachment 5329661
Click to expand...
Click to collapse
you must be in edload mode not fastboot
Hi guys !
I've just get back my Motorola Z2 play i borrow to one of my friend, but after many trials it seems to be a bit of broken (talk about it below), and after seeking a lot of thread on internet, i feel blocked and i need any advice or help.
Here's the original situation :
- The bootloader has been unlocked in the following way (with fastboot oem get_unlock_data method, then retrieve the key from motorola website)
then, AICP 16.1 has been flashed.
- Everything worked fine except bluetooth can't be used anymore, it can't be activated anymore i didn't know why. (i get back the phone at this step)
- As i appreciate using bluetooth, i tried to upgrade AICP, flash it again and wipe cache/data to check if bluetooth become available again but it never happened.
So i tried to flash the official Motorola ROM and my issues started...
After flashing with this official ROM from Motorola (ALBUS_OPSS27.76_12_25_23_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC), phone worked well but i wasn't impossible to use any Google services (if i opened play store it says : "Impossible Connection, an issue has happened while trying to connect to google servers" every time, same error if i wanted to check updates and so on...)
I saw a post on internet that say to relock the bootloader to get the phone fully encrypted and to be trusted from google servers, so i did it using fastboot oem lock. (this is a huge mistake...i know...)
It didn't change anything and google services raise the same error, but now i'm unable to flash any other rom or anything... moreover, OEM unlocked tick on the phone menu is greyed out, i tried to let it connected to internet for ~10days but it doesn't change anything.
When i tried to unlock bootloader again to allow me to flash another rom (i wanted to try lineage os), i got those error :
Code:
fastboot oem unlock "CODE_FROM_MOTOROLA"
(bootloader) invalid boot state
OKAY [ 0.007s]
Finished. Total time: 0.010s
but also
Code:
fastboot flashing unlock
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options.
OKAY [ 0.009s]
Finished. Total time: 0.010s
but Allow OEM Unlock is still greyed out after 10days connected to the Wifi at home.
The current situation is, i can't unlock bootloader BUT, i can boot on TWRP for example. But when i try to flash anything it raises an error because bootloader is locked.
Is there any way to get out of this lock/unlock issues to be able again to flash a new custom ROM ?
Thanks a lot for your advices
motorbass said:
Hi guys !
I've just get back my Motorola Z2 play i borrow to one of my friend, but after many trials it seems to be a bit of broken (talk about it below), and after seeking a lot of thread on internet, i feel blocked and i need any advice or help.
Here's the original situation :
- The bootloader has been unlocked in the following way (with fastboot oem get_unlock_data method, then retrieve the key from motorola website)
then, AICP 16.1 has been flashed.
- Everything worked fine except bluetooth can't be used anymore, it can't be activated anymore i didn't know why. (i get back the phone at this step)
- As i appreciate using bluetooth, i tried to upgrade AICP, flash it again and wipe cache/data to check if bluetooth become available again but it never happened.
So i tried to flash the official Motorola ROM and my issues started...
After flashing with this official ROM from Motorola (ALBUS_OPSS27.76_12_25_23_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC), phone worked well but i wasn't impossible to use any Google services (if i opened play store it says : "Impossible Connection, an issue has happened while trying to connect to google servers" every time, same error if i wanted to check updates and so on...)
I saw a post on internet that say to relock the bootloader to get the phone fully encrypted and to be trusted from google servers, so i did it using fastboot oem lock. (this is a huge mistake...i know...)
It didn't change anything and google services raise the same error, but now i'm unable to flash any other rom or anything... moreover, OEM unlocked tick on the phone menu is greyed out, i tried to let it connected to internet for ~10days but it doesn't change anything.
When i tried to unlock bootloader again to allow me to flash another rom (i wanted to try lineage os), i got those error :
Code:
fastboot oem unlock "CODE_FROM_MOTOROLA"
(bootloader) invalid boot state
OKAY [ 0.007s]
Finished. Total time: 0.010s
but also
Code:
fastboot flashing unlock
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options.
OKAY [ 0.009s]
Finished. Total time: 0.010s
but Allow OEM Unlock is still greyed out after 10days connected to the Wifi at home.
The current situation is, i can't unlock bootloader BUT, i can boot on TWRP for example. But when i try to flash anything it raises an error because bootloader is locked.
Is there any way to get out of this lock/unlock issues to be able again to flash a new custom ROM ?
Thanks a lot for your advices
Click to expand...
Click to collapse
Your original issue was because you upgraded from stock Oreo, which if you would have spent the 5 minutes reading you would have known that A11 roms all require stock Pie modem.
As for your current situation, i don't think you can get out of this one; you might try your hand with Lenovo Moto Smart Assistant or try putting the pie update into the phone to force the updater to upgrade you but you really have put yourself in a weird situation. Your phone is now
1. Locked
2. On the stock rom
3. Without the original recovery
So the bootloader is ****ing confused as to what to do
Hi !
First of all, thanks a lot for your answer.
To be honest i simply used this thread when first upgraded to AICP ( https://forum.xda-developers.com/t/discontinued-rom-11-0-offical-aicp-16-1-albus.4335535/ ), so sorry i wasn't aware about any requirements about the stock Pie modern you mentioned.
Meanwhile, i already have a look with LMSA tool, everything is recognized but it can't load/flash anything as the bootloader is locked/broken.
motorbass said:
Hi !
First of all, thanks a lot for your answer.
To be honest i simply used this thread when first upgraded to AICP ( https://forum.xda-developers.com/t/discontinued-rom-11-0-offical-aicp-16-1-albus.4335535/ ), so sorry i wasn't aware about any requirements about the stock Pie modern you mentioned.
Meanwhile, i already have a look with LMSA tool, everything is recognized but it can't load/flash anything as the bootloader is locked/broken.
Click to expand...
Click to collapse
{
"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"
}
I know nowadays a short attention span is rewarded, but reading all the way through to the end is usually worth it. If LMSA can't save you then you have officially bricked your phone (unless you find some exploit) OEM Unlock remains unavailable because the image you flashed isn't signed, and as such the phone has gone into FLASHING_LOCKED instead of OEM_LOCKED; i'm pretty sure you can guess the difference between those two.
One last hail mary would be the updater and P; since OTA's are signed you may be able to unlock your phone again (and this time custom roms WILL work! How about that)
Yeah it's my mistake.. i've just focused on the first post tutorial rather than reading the whole posts before. I also dislike people doing this but this time it's me haha..
(You right i'm into Flashing_locked status.)
Unfortunately Update menu tell me i'm already up to date, don't know if it's related that also any google services says it can't connect to google servers.
i'm afraid OTA update will work again.
motorbass said:
Yeah it's my mistake.. i've just focused on the first post tutorial rather than reading the whole posts before. I also dislike people doing this but this time it's me haha..
(You right i'm into Flashing_locked status.)
Unfortunately Update menu tell me i'm already up to date, don't know if it's related that also any google services says it can't connect to google servers.
i'm afraid OTA update will work again.
Click to expand...
Click to collapse
That is probably because your particular region did not get Pie; search through this forum, there's a way to force the updater to recognize the OTA
Hi, is there any alternatives to rescue my device? i can not enter to fastboot, nor to recovery.
In miflash i have no active connection. Is there any solution, or did i just make it dead?
only shows mi logo (powered by android)
My theory is that my EFI bootloader was written in memory, therefore my bootloader is gone after restarting windows.
(interestingly there is no bootloader unlocked indication, as before.)
mdve123 said:
Hi, is there any alternatives to rescue my device? i can not enter to fastboot, nor to recovery.
In miflash i have no active connection. Is there any solution, or did i just make it dead?
only shows mi logo (powered by android)
My theory is that my EFI bootloader was written in memory, therefore my bootloader is gone after restarting windows.
(interestingly there is no bootloader unlocked indication, as before.)
Click to expand...
Click to collapse
Sorry to hear that, please share your steps to disaster to let others know how to avoid this.
I assume that you used default Windows installer that broke your ufs gpt, instead of the installer you should have been used dism.
At this stage only a service may help you, they will put the device in edl mode and flash a stock firmware.
I think the only way to bring it back to life is to get it into EDL mode and force flash stock rom.
but to get to EDL first have to get to fastboot, i dont think it will work, also tried...
mdve123 said:
but to get to EDL first have to get to fastboot, i dont think it will work, also tried...
Click to expand...
Click to collapse
That is one way to get EDL, the other one is with a special USB plug if your device permit this, or open the back case and short two special test points on motherboard before power up to enter the EDL.
After you have your device in EDL mode you will need a tool to flash a stock image but as well you will be required to use a special program to authenticate, known as firehose, that kind of program should be signed by Xiaomi, this is why you need to go to an "authorized" service, which paid the signing authorization to Xiaomi.
serdeliuk said:
That is one way to get EDL, the other one is with a special USB plug if your device permit this, or open the back case and short two special test points on motherboard before power up to enter the EDL.
After you have your device in EDL mode you will need a tool to flash a stock image but as well you will be required to use a special program to authenticate, known as firehose, that kind of program should be signed by Xiaomi, this is why you need to go to an "authorized" service, which paid the signing authorization to Xiaomi.
Click to expand...
Click to collapse
Very useful info thank you! Just ordered a deepflash cable, hopefully i will find a workaround to flash in EDL.
If not, i'll try to get it done under warranty. I do not want to risk a keylog or a scam.
I bricked my tablet in the same way, only I can enter fastboot mode, by mistake when flashing a rom I did not change the option to lock the bootloader, now my pad 5 only turns on in fastboot mode, I don't have access to anything else , it does not let me flash with xiaomiflash because it says that it cannot proceed with the bootloader locked
RoyPH9903 said:
I bricked my tablet in the same way, only I can enter fastboot mode, by mistake when flashing a rom I did not change the option to lock the bootloader, now my pad 5 only turns on in fastboot mode, I don't have access to anything else , it does not let me flash with xiaomiflash because it says that it cannot proceed with the bootloader locked
Click to expand...
Click to collapse
You should download the latest MIUI Stable Fastboot update corresponding to your region (global, eeaor other) from this thread https://forum.xda-developers.com/t/miui-updates-tracker-xiaomi-pad-5-nabu.4328591/ , decompress the tgz file with 7zip or another software, and then, with your device in fastbboot mode, execute the flash_all.bat file within the folder you extracted. This should work even with a locked bootloader.
Good luck
I get this error
{
"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"
}
RoyPH9903 said:
I get this error
View attachment 5883229
Click to expand...
Click to collapse
Well, maybe I was wrong and you need an unlocked bootloader for this method to work. You could try to unlock it again with MiUnlock https://en.miui.com/unlock/download_en.html . Otherwise, I am out of idea.
I tried it and it didn't work, it tells me that I have to enable my miui account.
RoyPH9903 said:
I tried it and it didn't work, it tells me that I have to enable my miui account.
View attachment 5883255
Click to expand...
Click to collapse
Well, then I'm out of ideas. Maybe you should see what the seller's support can do.
Dear Experts,
I'm trying to rewrite lost IMEI after flashing stock rom (No backup). Tried everything in my sleeve. I am trying to find out how to enter in Meta mode so I can use the SN write tool or Modem meta. Tried following things:
adb reboot meta - nothing happening except reboot.
Vol button combo - nothing but fastboot and recovery.
Root - bootloader/oem can't be unlocked
Tried verity of tools nothing happening.
Brom mode - TP needs to be connected all the time (This is how I flashed the Rom).
Does any of you guys know how to activate Meta mode in this device. Seems nobody shared that detail over internet. Please help..
Thanks in advance.
eb60700 said:
Dear Experts,
I'm trying to rewrite lost IMEI after flashing stock rom (No backup). Tried everything in my sleeve. I am trying to find out how to enter in Meta mode so I can use the SN write tool or Modem meta. Tried following things:
adb reboot meta - nothing happening except reboot.
Vol button combo - nothing but fastboot and recovery.
Root - bootloader/oem can't be unlocked
Tried verity of tools nothing happening.
Brom mode - TP needs to be connected all the time (This is how I flashed the Rom).
Does any of you guys know how to activate Meta mode in this device. Seems nobody shared that detail over internet. Please help..
Thanks in advance.
Click to expand...
Click to collapse
Please head on to download the official tool
mvikrant97 said:
Please head on to download the official tool
Click to expand...
Click to collapse
I did it from the same website, but still not detecting.
eb60700 said:
I did it from the same website, but still not detecting.
Click to expand...
Click to collapse
Please make sure you have all the required drivers installed. If not please just install HMD Device Kit and it will install all the necessary drivers or you can manually install drivers from here.
Hi mvikrant97,
Sorry for the belated reply, I have installed HMD Device Kit drivers as per your link. but still its not detecting by Modem meta or SN Writer tool. While I connect the switched off phone this shows up in device manager.
{
"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"
}
Thanks for the helping hand mate.
eb60700 said:
Hi mvikrant97,
Sorry for the belated reply, I have installed HMD Device Kit drivers as per your link. but still its not detecting by Modem meta or SN Writer tool. While I connect the switched off phone this shows up in device manager.
View attachment 5822495
Thanks for the helping hand mate.
Click to expand...
Click to collapse
Were you able to connect device before when it was in working condition?
It also seems like the cable you are using is malfunctioned or the device USB port itself.
I'm sorry but I will have to ask you questions to diagnose the problem.
mvikrant97 said:
Were you able to connect device before when it was in working condition?
It also seems like the cable you are using is malfunctioned or the device USB port itself.
I'm sorry but I will have to ask you questions to diagnose the problem.
Click to expand...
Click to collapse
As I have mentioned before, I flashed this device with stock ROM using the same usb cable by triggering Test point in Brom Mode, So I highly doubt this is because of the faulty usb cable. Thereafter I lost my IMEI, but fortunately I had one IMEI noted down beforehand. I am trying to rewrite that IMEI so that I can use my SIM. Seriously what is this Meta Mode? This means nokia G10 doesn't support Meta Mode?
Please feel free to ask any question or suggestions mate.
eb60700 said:
As I have mentioned before, I flashed this device with stock ROM using the same usb cable by triggering Test point in Brom Mode, So I highly doubt this is because of the faulty usb cable. Thereafter I lost my IMEI, but fortunately I had one IMEI noted down beforehand. I am trying to rewrite that IMEI so that I can use my SIM. Seriously what is this Meta Mode? This means nokia G10 doesn't support Meta Mode?
Please feel free to ask any question or suggestions mate.
Click to expand...
Click to collapse
You will need Pandora Tool to fix up the IMEI.
But as much I know you need to have the backup beforehand to fix the issue.
You may refer to the video below
Thanks for the heads up. Looked up the tool, seems expensive than the G10 itself. Still wondering why the phone is not detected though.
eb60700 said:
Thanks for the heads up. Looked up the tool, seems expensive than the G10 itself. Still wondering why the phone is not detected though.
Click to expand...
Click to collapse
Maybe because the phone does not support Meta mode