I tried to flash the Mate 10 with sigmakey, im sure i used te correct firmware and the process completted successfully but the cellphone now is dead, wont turn on, no signs if charging but a little red light blinks when i connect it to the charger, i can't enter VOL - and connect via USB to enter Fastboot but the PC still recognize the fastboot device. I tried to use the fastboot but always says "Remote: command not allowed"
Is there a chance it can be revived? or is complety dead
i have flashed some devices like samsung, lg etc.. I dont have much experience flashing yet, i'm strarting in the subjet
Si hay alguna forma estaría muy agradecido
Thanks in advance.
jakio334 said:
I tried to flash the Mate 10 with sigmakey, im sure i used te correct firmware and the process completted successfully but the cellphone now is dead, wont turn on, no signs if charging but a little red light blinks when i connect it to the charger, i can't enter VOL - and connect via USB to enter Fastboot but the PC still recognize the fastboot device. I tried to use the fastboot but always says "Remote: command not allowed"
Is there a chance it can be revived? or is complety dead
i have flashed some devices like samsung, lg etc.. I dont have much experience flashing yet, i'm strarting in the subjet
Si hay alguna forma estaría muy agradecido
Thanks in advance.
Click to expand...
Click to collapse
What were you flashing with sigmakey?
Sent from my ALP-L29 using Tapatalk
royhanks3 said:
What were you flashing with sigmakey?
Sent from my ALP-L29 using Tapatalk
Click to expand...
Click to collapse
A Mate 10, ALP L09, it had the option so i tried.
jakio334 said:
A Mate 10, ALP L09, it had the option so i tried.
Click to expand...
Click to collapse
Were you trying to downgrade? It sounds like you were on a new bootloader firmware and flashed an old bootloader firmware. This always ends up in a brick. You'll have to replace board (or try test-points, not sure if anyone tried that yet.)
ante0 said:
Were you trying to downgrade? It sounds like you were on a new bootloader firmware and flashed an old bootloader firmware. This always ends up in a brick. You'll have to replace board (or try test-points, not sure if anyone tried that yet.)
Click to expand...
Click to collapse
Have the test points been found yet? Also, his situation seems different since he can still access fastboot somehow
Sent from my ALP-L29 using Tapatalk
royhanks3 said:
Have the test points been found yet? Also, his situation seems different since he can still access fastboot somehow
Sent from my ALP-L29 using Tapatalk
Click to expand...
Click to collapse
Ah right. Hard-brick only gives you USBSER
There are schematics which refer to test point, but I haven't opened mine up to check where it actually is.
You can google for "HL1BLAM VER.C schematic" and you should find it.
ante0 said:
Were you trying to downgrade? It sounds like you were on a new bootloader firmware and flashed an old bootloader firmware. This always ends up in a brick. You'll have to replace board (or try test-points, not sure if anyone tried that yet.)
Click to expand...
Click to collapse
It was in a bootloop, i tryed a hard reset but didnt work, so i decided to flash it, but it didnt start anymore.
jakio334 said:
It was in a bootloop, i tryed a hard reset but didnt work, so i decided to flash it, but it didnt start anymore.
Click to expand...
Click to collapse
Ah
Can you use any fastboot commands?
Like:
fastboot oem lock-state info
fastboot oem get-build-number
fastboot oem get-product-model
On Sigma key website only paid version 129 dollars for huawei edition... Why try sonething that expensive??
ante0 said:
Ah
Can you use any fastboot commands?
Like:
fastboot oem lock-state info
fastboot oem get-build-number
fastboot oem get-product-model
Click to expand...
Click to collapse
Sorry fo the late response,
Yes, for some reason i can still use some Fastboot commands
it says
(bootloader) FB Lockstate: Locked
(bootloader) USER Lockstate: Locked
(bootloader) System 8.0.0.38(012R)
but in the get-product-model says
(bootloader) ALP-L29 but the model is ALP-L09
So i asked to the owner of the phone, he said he tried to activate the dual sim by changin the model.
I didnt know that, the only thing he said it was stuck in a bootloop, not knowing that detail i installed the ALP-L09 firmware its when became dead.
Sigma Pack 3?
I have same problem but I don't know where we can find the board
Thanks
---------- Post added at 10:57 PM ---------- Previous post was at 10:55 PM ----------
ante0 said:
Were you trying to downgrade? It sounds like you were on a new bootloader firmware and flashed an old bootloader firmware. This always ends up in a brick. You'll have to replace board (or try test-points, not sure if anyone tried that yet.)
Click to expand...
Click to collapse
Where we could find the board since I have same problem
ah2hamed said:
I have same problem but I don't know where we can find the board
Thanks
---------- Post added at 10:57 PM ---------- Previous post was at 10:55 PM ----------
Where we could find the board since I have same problem
Click to expand...
Click to collapse
Gem-flash or through DC-Phoenix. Both require testpoint.
If Gem-flash you'd have to use IDT (which can be found there too). I suppose DC-Phoenix is easier as they have board and bootloader files.
When you are on board firmware you need to follow some steps to get a functioning phone. Any deviation from those steps will usually lead to no imei/no network.
1)Flash oeminfo (own backup) from fastboot
2)Backup modemnvm_system, modemnvm_factory and modemnvm_backup using adb pull from a command prompt (/dev/block/bootdevice/by-name/modemnvm_system and so on)
3)Flash backed up modemnvm_system, modemnvm_factory and modemnvm_backup from fastboot
3)Modify and brand with HCU (check everything but those that erase/flash empty board) (remember to fill vendor and cust)
4)Unlock sim with HCU
5)Read Bootloader code if you ever used HCU to get code before
6)Download and flash service firmware from androidhost.ru using a OTG cable and a memory stick
Easiest way for step 1 if you have no backup of oeminfo is to just dump and
and flash the one on your phone right now, then use HCU to get a new unlock code.
Related
Stuck on "Connect to the network to activate device" after flashing official ROM
So my phone started randomly rebooting a few days ago and after a few tries to fix it, I managed to brick it altogether (seemed dead except for the red EDL led flashing when on charger). After DIY'ing a deep flash cable, I was able to get the PC to recognize it and flash the latest official stable Kenzo MIUI. I'd tried Kate before, but that just led to bootloops. Anyway, finally the phone booted normally and I went through the regular initial setup, until I got to this one screen, which reads:
Connect to the network to activate device
Your device is associated with an existing Mi Account (#########). Connect to the network to verify the device.
Connect to Wi-Fi or insert a SIM card.
Click to expand...
Click to collapse
Then it eternally tries to connect to the network and never does. I have 2 options below: Connect to Wi-Fi and Search for SIM card. The problem is that the Wi-Fi option detects no networks (there's definitely a few available) and the SIM is already inserted (it asked me for a PIN) and is visibly detecting a signal, but no mobile data is activated. The installation even asked for permission to send an automated SMS at some point, which succeed (and I even got a reply, which I can't read) but that did nothing to remedy the situation.
I can't leave this screen at all and the device isn't activating either WiFi or mobile data.
What gives?
My bootloader is locked and TWRP isn't installed, btw. I'd never fiddled with the stock ROM before this little adventure and everything I've flashed since has been official.
Make sure you're connected to WiFi with reasonable speed.
You must use the same MI account to login which was used earlier, i.e. before the brick.
Try flashing with option clean all lock through EDL once again.
If none of the above options work, try these :
> Find help on this thread http://en.miui.com/thread-424945-1-1.html
> RBFsoft tool to unlock (Unofficial)(tested by me)
> Visit service center last resort.
VaibhavKumar07 said:
Make sure you're connected to WiFi with reasonable speed.
Click to expand...
Click to collapse
I'm not, I already mentioned the phone detects no networks.
VaibhavKumar07 said:
You must use the same MI account to login which was used earlier, i.e. before the brick.
Click to expand...
Click to collapse
I intend to, but I don't even get the option.
VaibhavKumar07 said:
Try flashing with option clean all lock through EDL once again.
Click to expand...
Click to collapse
It's what I did in the first place.
VaibhavKumar07 said:
If none of the above options work, try these :
> Find help on this thread
> RBFsoft tool to unlock (Unofficial)(tested by me)
> Visit service center last resort.
Click to expand...
Click to collapse
Thanks for trying to help, but I'm not trying to unlock the phone or skip the activation, I'm trying to go through with it. To clarify, my only issue is that my phone is not connecting to the internet.
Typing that out, I'm guessing I should attempt to flash a modem.
Akkuron said:
I'm not, I already mentioned the phone detects no networks.
I intend to, but I don't even get the option.
It's what I did in the first place.
Thanks for trying to help, but I'm not trying to unlock the phone or skip the activation, I'm trying to go through with it. To clarify, my only issue is that my phone is not connecting to the internet.
Typing that out, I'm guessing I should attempt to flash a modem.
Click to expand...
Click to collapse
Okay, I got it let me know the model number of your device 2015116 or 2015161.
It's written on the box of the device.
VaibhavKumar07 said:
Okay, I got it let me know the model number of your device 2015116 or 2015161.
It's written on the box of the device.
Click to expand...
Click to collapse
Sadly the box is 2500km away right now. I can PM you the product page that shows the exact make+ROM if that helps you identify the model.
edit: It is the Kenzo version according to the product page on the shop at least.
Akkuron said:
Sadly the box is 2500km away right now. I can PM you the product page that shows the exact make+ROM if that helps you identify the model.
Click to expand...
Click to collapse
Yeah send pm
So I've flashed a ROM that lets me bypass the initial activation screen and access the phone's settings. My fear has been confirmed that the phone has lost the IMEI/baseband info etc.
Is there a way to find the IMEI except the phone's box so I can follow a guide to fix this?
You have a Redmi note 3 pro aka Kenzo, LHOCNDD means it came with the Chinese version of the ROM installed.
But to recover your device first try to clean flash & lock the ROM you have, also mention the package name ( Try flashing Chinese developer )
I know you may feel this is an inappropriate solution but you'll require unlocked bootloader enter developer options to flash using fastboot commands.
So, right now you can't flash modem files NON-HLOS.bin or a full ROM with fastboot commands http://en.miui.com/thread-469662-1-1.html or http://en.miui.com/thread-250455-1-1.html
Now the only option you have is to unlock unofficially http://en.miui.com/thread-345728-1-1.html , after you recover your device you can lock it & factory reset.
But remember not to use commands Fastboot flash aboot emmc_appsboot.mbn & Fastboot flash abootbak emmc_appsboot.mbn if you have unlocked bootloader unofficially.
---------- Post added at 07:31 PM ---------- Previous post was at 07:19 PM ----------
Akkuron said:
So I've flashed a ROM that lets me bypass the initial activation screen and access the phone's settings. My fear has been confirmed that the phone has lost the IMEI/baseband info etc.
Is there a way to find the IMEI except the phone's box so I can follow a guide to fix this?
Click to expand...
Click to collapse
Okay, so which ROM did you flash MIUI 7? mention package name & http://en.miui.com/thread-375213-1-1.html use this guide to recover IMEI if you don't have the box I doubt if there's IMEI written on the label as our device has a non-removable battery.
So, you need the box & don't proceed in a hurry without proper instructions.
I've found the IMEI number and almost got through the instructions in the link you posted. My problem is when the time comes to use WriteDualIMEI(W+G_eMMC) it asks for 2 IMEI numbers and not one. Pressing start does nothing with only one of them typed in, but I my box has no second number on it.
edit: ROM that first let me in was official 7.2.3 which is apparently the only version that didn't require validation, now I'm on the rooted Sphinx ROM from that link though.
Akkuron said:
I've found the IMEI number and almost got through the instructions in the link you posted. My problem is when the time comes to use WriteDualIMEI(W+G_eMMC) it asks for 2 IMEI numbers and not one. Pressing start does nothing with only one of them typed in, but I my box has no second number on it.
edit: ROM that first let me in was official 7.2.3 which is apparently the only version that didn't require validation, now I'm on the rooted Sphinx ROM from that link though.
Click to expand...
Click to collapse
Don't make any changes to the current setup, let me gather some info & get back to you.
By the way, dual sim variant will have 2 IMEI numbers.
Edit: First, let me know the baseband & IMEI shows unknown or 0?
---------- Post added at 02:12 AM ---------- Previous post was at 01:27 AM ----------
If it shows 0, then write same IMEI in both slots & proceed.
Shows up as unknown. I've read it's supposed to have 2 IMEIs but only 1 is on the box (and the sticker inside the device).
Akkuron said:
Shows up as unknown. I've read it's supposed to have 2 IMEIs but only 1 is on the box (and the sticker inside the device).
Click to expand...
Click to collapse
Follow this guide & recover EFS
https://forum.xda-developers.com/redmi-note-3/how-to/flash-recover-efs-snapdragon-t3406789 then write IMEI same in both slots.
VaibhavKumar07 said:
Follow this guide & recover EFS
https://forum.xda-developers.com/redmi-note-3/how-to/flash-recover-efs-snapdragon-t3406789 then write IMEI same in both slots.
Click to expand...
Click to collapse
Flashing the 2 modemst files through fastboot just caused a bootloop.
edit: got out of the bootloop by flashing a stock developer ROM (miui9) and now my baseband is recognized. My IMEI numbers are a mix of unknowns and 0s. Problem is the phone isn't rooted now.
Should I flash TWRP and root it with that, or just try to flash that rooted Sphinx ROM again? Don't wanna brick it again now that we're getting somewhere.
Akkuron said:
Flashing the 2 modemst files through fastboot just caused a bootloop.
Click to expand...
Click to collapse
Can you run the command fastboot oem device-info & send the result?
Sent from my Redmi Note 3 using Tapatalk
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.008s]
Akkuron said:
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.008s]
Click to expand...
Click to collapse
*Deleted*
---------- Post added at 05:25 AM ---------- Previous post was at 04:55 AM ----------
Please don't edit posts, just send a new reply.
As you're on MIUI 9 Global ROM, unlock right away if you have official permissions.
If not http://en.miui.com/thread-345728-1-1.html unlock unofficially & skip EFS restore, proceed to write IMEI.
when you flash a ROM provide the name of the package.
Writing the IMEI doesn't work because I don't have root permissions on the stock global ROM (kenzo_global_images_7.11.6_20171106.0000.00_6.0_global). Is there a way to enter diagnostic mode without it, or should I just root?
Update: Rooted, but WriteDualIMEI(W+G_eMMC) gives me a "No diag port" error, despite detecting the port (COM11) that the phone is connected on. Device Manager confirms as it recognizes it as "Qualcomm HS-USB Android DIAG 901D (COM11). Tools like QPST and RF NV Manager can interface with the phone normally. I tried writing the IMEI through RF NV Manager, but it only went into IMEI2. IMEI1 is "unknown" still.
Akkuron said:
Writing the IMEI doesn't work because I don't have root permissions on the stock global ROM (kenzo_global_images_7.11.6_20171106.0000.00_6.0_global). Is there a way to enter diagnostic mode without it, or should I just root?
Update: Rooted, but WriteDualIMEI(W+G_eMMC) gives me a "No diag port" error, despite detecting the port (COM11) that the phone is connected on. Device Manager confirms as it recognizes it as "Qualcomm HS-USB Android DIAG 901D (COM11). Tools like QPST and RF NV Manager can interface with the phone normally. I tried writing the IMEI through RF NV Manager, but it only went into IMEI2. IMEI1 is "unknown" still.
Click to expand...
Click to collapse
Hold on, you're making the situation worse.
Is the bootloader unlocked & USB debugging enabled?
type adb devices to check communication.
I'll try to find some other solution, so have patience.
Only proceed on your own if I'm dead.
VaibhavKumar07 said:
Hold on, you're making the situation worse.
Is the bootloader unlocked & USB debugging enabled?
type adb devices to check communication.
I'll try to find some other solution, so have patience.
Only proceed on your own if I'm dead.
Click to expand...
Click to collapse
Fastboot oem device-info says the bootloader is locked, but I'm pretty sure I'd unlocked it at some point.
USB debugging is enabled.
ADB devices detects the phone normally.
Akkuron said:
Fastboot oem device-info says the bootloader is locked, but I'm pretty sure I'd unlocked it at some point.
USB debugging is enabled.
ADB devices detects the phone normally.
Click to expand...
Click to collapse
ROM version, Bootloader unlock method & when did you unlock?
---------- Post added at 03:39 PM ---------- Previous post was at 03:32 PM ----------
Did you restore EFS before writing IMEI?
I ordered a Redmi note 4 through Amazon India, came out alright, all properly sealed and everything but one thing caught my attention is that on developer settings the phone unlock status says it's already unlocked! How can this be possible?
That's weird. Did you call a customer service centre? If I'd receive such product my first though would be to confirm if the Mido I got is a refurbished one or 1st hand. And even if it's one, then the Xiaomi guys should have relocked it... Maybe it's a software bug, try restarting. And the ultimate way to confirm is to use your PC, and you know the rest I hope.
Well, if you feel you can replace it (maybe) talk to amazon guys and confirm if they cover such thing in their replacement policy. Good luck.
MayankMathur said:
That's weird. Did you call a customer service centre? If I'd receive such product my first though would be to confirm if the Mido I got is a refurbished one or 1st hand. And even if it's one, then the Xiaomi guys should have relocked it... Maybe it's a software bug, try restarting. And the ultimate way to confirm is to use your PC, and you know the rest I hope.
Well, if you feel you can replace it (maybe) talk to amazon guys and confirm if they cover such thing in their replacement policy. Good luck.
Click to expand...
Click to collapse
How to check if it's refurbished via PC?
Maybe you have RN4x, it is default unlocked... You can check your box, if it is with chinese language you have 4x, if you have with english lang. it is RN4 Global version and it is locked default...
Edit: also check if it is Snapdragon 625 version or maybe it is MTK?
Sent from my Redmi Note 4x
kurogami95 said:
How to check if it's refurbished via PC?
Click to expand...
Click to collapse
You have to check if the bootloader is really unlocked or not. For this download this zip - https://drive.google.com/open?id=13Sjej5zIJPm_yiJQOVR4rEocwbhDc9oh
Unzip in pc and inside the platfrom-tools folder hold shift and right click.
In the menu it should say, open command prompt here or open powershell here.
click on the provided item (whatever of both it shows)
now, boot your device in fastboot by switching it off and holding down the power and volume down. Once the fastboot mode is open, connect your device via cable to your pc.
Now if you opened a command prompt window then type in -
Code:
fastboot devices
This command will show the connected fastboot devices. If nothing is printed on screen on executing command, then try reconnecting.
then type -
Code:
fasboot oem device-info
But if you have powershell then type in
Code:
.\fastboot devices
and
Code:
.\fastboot oem device-info
This will return some data and now you have to check the first two parameters saying "device tampered" and "device unlocked".
If device unlocked says true, then that means someone had actually used the device before. and if device tampered says true, then definetly someone has tested out your device, by doing all kinds of stuff like installing roms etc.
Use the mi flasher and flash the most current xiaomi rom. Your rom is probably a vendor rom, which is bad.
MyNameIsRage said:
You have to check if the bootloader is really unlocked or not. For this download this zip - https://drive.google.com/open?id=13Sjej5zIJPm_yiJQOVR4rEocwbhDc9oh
Unzip in pc and inside the platfrom-tools folder hold shift and right click.
In the menu it should say, open command prompt here or open powershell here.
click on the provided item (whatever of both it shows)
now, boot your device in fastboot by switching it off and holding down the power and volume down. Once the fastboot mode is open, connect your device via cable to your pc.
Now if you opened a command prompt window then type in -
This command will show the connected fastboot devices. If nothing is printed on screen on executing command, then try reconnecting.
then type -
fasboot oem device-info
But if you have powershell then type in
But if you have powershell then type in
.\fastboot devices
and
This will return some data and now you have to check the first two parameters saying "device tampered" and "device unlocked".
If device unlocked says true, then that means someone had actually used the device before. and if device tampered says true, then definetly someone has tested out your device, by doing all kinds of stuff like installing roms etc.
Click to expand...
Click to collapse
Thanks for making it easy for me. ?
Sometimes sellers unlock bootloader to flash other roms version. It's usually on online selling where there is Chinese roms on devices and buyers want global version.
As allready ppl stated, check by adb fastboot to see if its really unlocked.
Sent from my Redmi Note 4 using Tapatalk
MyNameIsRage said:
You have to check if the bootloader is really unlocked or not. For this download this zip - https://drive.google.com/open?id=13Sjej5zIJPm_yiJQOVR4rEocwbhDc9oh
Unzip in pc and inside the platfrom-tools folder hold shift and right click.
In the menu it should say, open command prompt here or open powershell here.
click on the provided item (whatever of both it shows)
now, boot your device in fastboot by switching it off and holding down the power and volume down. Once the fastboot mode is open, connect your device via cable to your pc.
Now if you opened a command prompt window then type in -
Code:
fastboot devices
This command will show the connected fastboot devices. If nothing is printed on screen on executing command, then try reconnecting.
then type -
Code:
fasboot oem device-info
But if you have powershell then type in
Code:
.\fastboot devices
and
Code:
.\fastboot oem device-info
This will return some data and now you have to check the first two parameters saying "device tampered" and "device unlocked".
If device unlocked says true, then that means someone had actually used the device before. and if device tampered says true, then definetly someone has tested out your device, by doing all kinds of stuff like installing roms etc.
Click to expand...
Click to collapse
Please can you help me? I got a Xiaomi Mi A1 and I noticed the bootloader was already unlocked, when I relock it the phone refuses to come on because I found out that "device tampered" is saying true. Please how can I get it back to false? Thank you
chuckychux said:
Please can you help me? I got a Xiaomi Mi A1 and I noticed the bootloader was already unlocked, when I relock it the phone refuses to come on because I found out that "device tampered" is saying true. Please how can I get it back to false? Thank you
Click to expand...
Click to collapse
You should contact xiaomi for this. And the seller from which you bought it. Because 98% of companies aren't allowed to sell phones with unlocked bootloader. Just leave it as it is. Tampering it by yourself would mean that you yourself did something to phone, which u haven't (not much, what u did is ok) . So getting in touch with the company and the provider would be a better option.
---------- Post added at 07:42 AM ---------- Previous post was at 07:41 AM ----------
chuckychux said:
Please can you help me? I got a Xiaomi Mi A1 and I noticed the bootloader was already unlocked, when I relock it the phone refuses to come on because I found out that "device tampered" is saying true. Please how can I get it back to false? Thank you
Click to expand...
Click to collapse
Or you can just unlock the bootloader once again to possibly make the phone functional
MyNameIsRage said:
You should contact xiaomi for this. And the seller from which you bought it. Because 98% of companies aren't allowed to sell phones with unlocked bootloader. Just leave it as it is. Tampering it by yourself would mean that you yourself did something to phone, which u haven't (not much, what u did is ok) . So getting in touch with the company and the provider would be a better option.
---------- Post added at 07:42 AM ---------- Previous post was at 07:41 AM ----------
Or you can just unlock the bootloader once again to possibly make the phone functional
Click to expand...
Click to collapse
I have unlocked it again and it's working again, but my problem now is that I can't get Ota updates on my phone and is there a way I can change "Device tampered" from true to false? Thank u
chuckychux said:
I have unlocked it again and it's working again, but my problem now is that I can't get Ota updates on my phone and is there a way I can change "Device tampered" from true to false? Thank u
Click to expand...
Click to collapse
Did u install twrp? If no then flash fastboot rom
MyNameIsRage said:
Did u install twrp? If no then flash fastboot rom
Click to expand...
Click to collapse
I didn't install twrp, if I flash with fastboot will it be locked? And how will I do it
chuckychux said:
I didn't install twrp, if I flash with fastboot will it be locked? And how will I do it
Click to expand...
Click to collapse
Most probably yea. Also you should report this in mi a1 forums as well. And you can google to find instructions for flashing update via fastboot.
Dear all,
I bought Mi Pad 4 and it was running well, and I want to update the ROM. The device is comes with Locked bootloader.
I unlocked my Mi Pad 4 using MI Unlock. And when I try to relock it using "fastboot oem lock" command, it become suddenly comes with black screen with written: "The system has been destroyed. Press power button to shutdown".
So I entered the fastboot mode and try some command/solutions:
- My device status is locked:
E:\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.006s]
finished. total time: 0.006s
- I can't unlock it using Mi Unlock:
- Flashing using MiFlashalso not allowed since it is still locked:
- I tried to unlock using fastboot, also failed:
E:\adb>fastboot oem unlock
...
FAILED (remote: Token Verify Failed, Reboot the device
)
finished. total time: 0.003s
- The faastboot screen in my mi pad is only for around 10 Second. After that it goes to "The System has been Destroyed" stage...
Any help is appreciated, because I cant use it anymore...
Why did you even want to close the BL again?!? I dont understand anyone who does that.
And AFAIK you can flash an original Image from Xiaomi even with locked BL. But I have never done it and the guide shows a working phone..
http://en.miui.com/thread-835254-1-1.html
You need the Mi-Flash Tool. And these damn Indian people with their fake titles on youtube.. The title is english and the freaking video is hindi or whatever.. SO ANNOYING!!!
Hi, the tutorial you gave is for 'normal' xiaomi phone, where it boot normally (even its BL is locked).
In my case, I cant load the BL (It said: Destroyed). The only thing I can do is restart to fastboot state, and after 20 seconds it goes again to Destroyed state.
Ok, so I have read some other threads and what seems the "only" solution is to unlock the bootloader again.. But the other people had no problem running "oem unlock".. And you get an error, what is kinda strange.
What happens in MiUnlock? Error?
Hi, I think the main problem is current status is "The System has been Destroyed", therefore it cannot load the BL.
Meanwhile, the BL is in Locked status. So it need to be un-locked first, so I can load the new ROM.
MIUnlock is error, it said: "Current account is not bound to this device", which is strange, because previously I unlocked using it before.
I assume MIUnlock said this because the status of "System destroyed"...
Never lock if there is not 100% Xiaomi official rom inside, and better use MiFlash with "clean all and lock" option for locking.
Thanks for your suggestion. Will do that after I fix this problem..
I think you have a bricked device.. Some devices have this "test-pins", where you can enable some debug-bridge and there you could flash it (mi5 or redmi5 was that in that thread). I dont know if the Pad4 has such Pins and you would have to open the whole device.. (its not something you can access from the outside).
But I dont know if the Pad has these test-pins, just because another Xiaomi device had it..
Noted on that, but too risky for me to open the case..
Any other solution would be really appreciated.
thE_29 said:
But I dont know if the Pad has these test-pins, just because another Xiaomi device had it..
Click to expand...
Click to collapse
On some devices you have to login your Mi Account with MiFlash when flashing in EDL mode and account needs special permissions.
P.Kosunen said:
On some devices you have to login your Mi Account with MiFlash when flashing in EDL mode and account needs special permissions.
Click to expand...
Click to collapse
Yup, and I cant do that since cannot load the BL, because it's "Destroyed" right now..
Up.
Does anyone have the solution on this?
Thanks.
Seemed "bricked" to me, welcome to the bricked world dude, I have had 2 beautiful paper holder on my desk.
mac_erot said:
Up.
Does anyone have the solution on this?
Thanks.
Click to expand...
Click to collapse
The only solution was already posted several times -> open device, find test-pins, use them and flash ROM. And yet, you still ignore it everytime. THERE is no other solution for bricked devices.
And: NEVER close the bootloader again on NON official ROMs.
2 ways to try out...
1st run
"fastboot flashing unlock"
2nd
"fastboot oem reboot EDL"
Or this link if the command doesn't work
https://www.google.com/amp/s/forum....e-how-to-reboot-to-edl-fastboot-t3394292/amp/
go to service centre they will be able to restore the device using edl i hope
I tried also all solutions, but nothing helped. EDL, fastboot, etc.
If there is a way to unlock the BL again I can go on. Otherwise there will be no chance for me to get it running.
Has anyone got a solution how I can unlock the BL again? Or flash with locked BL?
Thanks!
maluc said:
I tried also all solutions, but nothing helped. EDL, fastboot, etc.
If there is a way to unlock the BL again I can go on. Otherwise there will be no chance for me to get it running.
Has anyone got a solution how I can unlock the BL again? Or flash with locked BL?
Thanks!
Click to expand...
Click to collapse
Looks like it is straightforward to remove the back cover. Perhaps you can find the EDL test points on the motherboard?
https://www.youtube.com/watch?v=RZpj0k9HKTQ
Is there no possibility to enable USB Debugging without entering the miui surface?
maluc said:
I tried also all solutions, but nothing helped. EDL, fastboot, etc.
If there is a way to unlock the BL again I can go on. Otherwise there will be no chance for me to get it running.
Has anyone got a solution how I can unlock the BL again? Or flash with locked BL?
Thanks!
Click to expand...
Click to collapse
Edl with test points should work, try some different ones, maybe the ones you are trying are wrong
---------- Post added at 06:47 AM ---------- Previous post was at 06:47 AM ----------
Also, try to run fastboot erase vbmeta
Hello everyone,
I want to unlock boot loader on my LG G PAD IV 8 (V533).
I did the OEM unlock in setting of developer options, But I couldn't reboot to bootloader and fastboot mode.
I tried:
1) adb reboot bootloader -> it reboots normally
2) Volume down and power and release power and hold all keys down --> IMEI display
3) Hold volume Up and connect USB --> Download mode (no fastboot)
4) Volume down and power and release power and hold back power --> factory reset
How can I enter to fastboot mode on this device so I can unlock the device? I don't find the key combination.
Thanks
Did you fimd any imfo on this yet???
Same situation. I did exactly the same thing you did and just found your post now.
No way at all to ROOT or Unlock LG V533 Bootloader ??
eggmama said:
Same situation. I did exactly the same thing you did and just found your post now.
Click to expand...
Click to collapse
Hi,
Looks like the Canadian variant of the LG GPad IV 8.0 is unrootable or unable to unlock the bootloader. However, the US T-Mobile variant (V530) which is essentially the same specs, is rootable according to other XDA post https://forum.xda-developers.com/g-pad-x-80/how-to/guide-root-lg-g-pad-v530-newbies-t3901485
Should any new info come up regarding this variant, feel free to post it here. Thanks
I just flashed 8.1 with a Korean kdz. onto an LG-V533 using LGUP Dual Mode. Next I will see about recovery, but for now pleased with the results. I got tired of searchig for American firmware with identical hardware.
mindlery said:
I just flashed 8.1 with a Korean kdz. onto an LG-V533 using LGUP Dual Mode. Next I will see about recovery, but for now pleased with the results. I got tired of searchig for American firmware with identical hardware.
Click to expand...
Click to collapse
Could you please tell us where to download it and how to flash? There's any tutorial around?
mindlery said:
I just flashed 8.1 with a Korean kdz. onto an LG-V533 using LGUP Dual Mode. Next I will see about recovery, but for now pleased with the results. I got tired of searchig for American firmware with identical hardware.
Click to expand...
Click to collapse
Did you simply use the LGUP Dev mode and flash the Korean kdz onto the V533 or did you modify anything somehow? Would like to try it but not familiar with flashing LG devices, only ZTE and HTC
That's correct. I am going from memory here, but i know i did not make any alterations of any kind prior. It will repartition the device and i'm not certain if you can revert.
I did it for a friend and it works well. You'll wind up with a few weird Korean apps. The ones you can't uninstall just use adb or app manager.
I am pretty sure the selection i used was "download" and it gave a warning about repartitioning. So obviously i did it. I think it froze during initial boot. I recall waiting far too long and just force rebooted and all was well. I am much more comfortable flashing a Motorola or Samsung myself. I've cross flashed a few Lg's now and they seem to work well.
Even though i spend a lot of time making sure it can work, you may get different results. Make sure it's charged good. I learned that one already. Let me know how it goes!
After your cross-flash, 3g/lte works? Your IMEI remains the same as original IMEI?
Thanks.
mindlery said:
That's correct. I am going from memory here, but i know i did not make any alterations of any kind prior. It will repartition the device and i'm not certain if you can revert.
I did it for a friend and it works well. You'll wind up with a few weird Korean apps. The ones you can't uninstall just use adb or app manager.
I am pretty sure the selection i used was "download" and it gave a warning about repartitioning. So obviously i did it. I think it froze during initial boot. I recall waiting far too long and just force rebooted and all was well. I am much more comfortable flashing a Motorola or Samsung myself. I've cross flashed a few Lg's now and they seem to work well.
Even though i spend a lot of time making sure it can work, you may get different results. Make sure it's charged good. I learned that one already. Let me know how it goes!
Click to expand...
Click to collapse
---------- Post added at 08:51 AM ---------- Previous post was at 08:49 AM ----------
Please let me know if you tried, fail or not. Thanks.
fuzzmania said:
Did you simply use the LGUP Dev mode and flash the Korean kdz onto the V533 or did you modify anything somehow? Would like to try it but not familiar with flashing LG devices, only ZTE and HTC
Click to expand...
Click to collapse
Sorry. I did it and it was successful
By this do you mean your IMEI remained the same (original IMEI)?
I would like to cross-flash in order to unlock the bootloader, then install TWRP. Thank you. Could you give more details about
(1) Your original model. I assume it was LG-V533 Canada Rogers or Telus.
(2) After cross-flashing, the model changed to ...? Have you tried "adb reboot bootloader" . Inside bootloader: "flashboot oem unlock"?
mindlery said:
Sorry. I did it and it was successful
Click to expand...
Click to collapse
sintoo said:
By this do you mean your IMEI remained the same (original IMEI)?
I would like to cross-flash in order to unlock the bootloader, then install TWRP. Thank you. Could you give more details about
(1) Your original model. I assume it was LG-V533 Canada Rogers or Telus.
(2) After cross-flashing, the model changed to ...? Have you tried "adb reboot bootloader" . Inside bootloader: "flashboot oem unlock"?
Click to expand...
Click to collapse
I have no idea. I did it to upgrade the OS and my buddy never intended to put in a SIM. I will see if i can get him to check. Pretty sure his ex has it now. But i'll check out the imei if possible. Should be able to tell by the first 9 digits. I never attempted unlocking the bootloader either Sorry i cannot help much beyond that.
---------- Post added at 03:16 PM ---------- Previous post was at 02:36 PM ----------
sintoo said:
By this do you mean your IMEI remained the same (original IMEI)?
I would like to cross-flash in order to unlock the bootloader, then install TWRP. Thank you. Could you give more details about
(1) Your original model. I assume it was LG-V533 Canada Rogers or Telus.
(2) After cross-flashing, the model changed to ...? Have you tried "adb reboot bootloader" . Inside bootloader: "flashboot oem unlock"?
Click to expand...
Click to collapse
I have no idea. I did it to upgrade the OS and my buddy never intended to put in a SIM. I will see if i can get him to check. Pretty sure his ex has it now. But i'll check out the imei if possible. Should be able to tell by the first 9 digits. I never attempted unlocking the bootloader either Sorry i cannot help much beyond that.
hrh0001 said:
Hello everyone,
I want to unlock boot loader on my LG G PAD IV 8 (V533).
I did the OEM unlock in setting of developer options, But I couldn't reboot to bootloader and fastboot mode.
I tried:
1) adb reboot bootloader -> it reboots normally
2) Volume down and power and release power and hold all keys down --> IMEI display
3) Hold volume Up and connect USB --> Download mode (no fastboot)
4) Volume down and power and release power and hold back power --> factory reset
How can I enter to fastboot mode on this device so I can unlock the device? I don't find the key combination.
Thanks
Click to expand...
Click to collapse
Hello
Does anyone have any active custom rom links/tutorials for V533 and V497? seems all online are down or gone? Thx
My A03s isnt showing the OEM Unlock option is developer settings, even though its unlocked
Which model?
Swyen said:
My A03s isnt showing the OEM Unlock option is developer settings, even though its unlocked
Click to expand...
Click to collapse
Is it the mediatek one? Oem unlock doesn't matter anyway. I've had 2 of these phones and you can just plug it in to a tool like mtkclient and boom you've unlocked the bootloader with no oem option. Unlocktool can also network unlock that phone too.
r1pp3d2 said:
Is it the mediatek one? Oem unlock doesn't matter anyway. I've had 2 of these phones and you can just plug it in to a tool like mtkclient and boom you've unlocked the bootloader with no oem option. Unlocktool can also network unlock that phone too.
Click to expand...
Click to collapse
Which sim unlock tool do you recommend? Thanks.
magi44ken said:
Which sim unlock tool do you recommend? Thanks.
Click to expand...
Click to collapse
Unlocktool can network unlock it for sure. I've done two of the A03s's with it.
r1pp3d2 said:
Unlocktool can network unlock it for sure. I've done two of the A03s's with it.
Click to expand...
Click to collapse
You mean this web site: https://unlocktool.net?
magi44ken said:
You mean this web site: https://unlocktool.net?
Click to expand...
Click to collapse
Yep, that's the one. It's a really good tool for cheap.
r1pp3d2 said:
Is it the mediatek one? Oem unlock doesn't matter anyway. I've had 2 of these phones and you can just plug it in to a tool like mtkclient and boom you've unlocked the bootloader with no oem option. Unlocktool can also network unlock that phone too.
Click to expand...
Click to collapse
how did you manage to boot it into BROM? I cant seem to get it into BROM.
Swyen said:
how did you manage to boot it into BROM? I cant seem to get it into BROM.
Click to expand...
Click to collapse
I don't know if you figured it out but to get into brom you do exactly as the mtkclient tells you too. I didn't get it working in windows but I used the boot DVD that is listed on the github mtkclient page. My model is sm-a037u from MetroPCS. The software tells you to power off the phone. Then plug the USB cable into the computer and then before you insert the USB cable into your phone hold down both volume buttons at the same time. I did get the bootloader unlocked with mtkclient but kept getting an error about the vbmeta or something so I had to flash back my backup I made with mtkclient. I think I just flashed back the boot.img and the vbmeta. I have not messed with it since. I tried flashing the magisk patched bootloader but got the same error I believe. Make sure you do a full backup except for maybe the user data partition to save time. I read another thread here on xda about I think the f instead of u model in where they patched the whole stock rom image with magisk or a certain part of it. If I ever try it again I will do a write up about it. Also to speed up the backup use a USB 3 port on your computer.
DaRkSkYxP said:
I don't know if you figured it out but to get into brom you do exactly as the mtkclient tells you too. I didn't get it working in windows but I used the boot DVD that is listed on the github mtkclient page. My model is sm-a037u from MetroPCS. The software tells you to power off the phone. Then plug the USB cable into the computer and then before you insert the USB cable into your phone hold down both volume buttons at the same time. I did get the bootloader unlocked with mtkclient but kept getting an error about the vbmeta or something so I had to flash back my backup I made with mtkclient. I think I just flashed back the boot.img and the vbmeta. I have not messed with it since. I tried flashing the magisk patched bootloader but got the same error I believe. Make sure you do a full backup except for maybe the user data partition to save time. I read another thread here on xda about I think the f instead of u model in where they patched the whole stock rom image with magisk or a certain part of it. If I ever try it again I will do a write up about it. Also to speed up the backup use a USB 3 port on your computer.
Click to expand...
Click to collapse
Try installing libusb. When you run it, (with mediatek drivers installed), plug in your phone from a powered off state. Do NOT hold any buttons.
If using a laptop, you might want to use a mouse.
To install the filter, you need to see it in the list and it will only appear for about 2 seconds. You need to quickly select it then install.
Once you do that, search for the A03 frp tool which will include your scatter file and an app that crashes and allows to erase a partition with frp system files. But i think it also gives you flashing capability. I am going to try it now.
If you have issues you need to turn off anti virus (anyone with some experience should know the basics and how to deal with issues such as tossing computer into large inferno etc). Use windows 10. 11 may not work.
Ok so I was able to successfully flash the modified (magisk patched) boot.img and I replaced it in the firmware package found here:
Samsung A037F U1 (A037FXXU1AUI7) Dead Boot Repair Scatter EMMC Dump File
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
I used this set of files to make the process possible:
Samsung A03s FRP All Android version.rar
drive.google.com
In the photo you'll notice things seemed to have gone well... but the phone now just boots to download mode.
I changed connection from UART to USB in the provided flash tool. Maybe that was my mistake. I must admit i am not too good at doing this stuff and am usually taking advantage of other people's ideas. Any help would be appreciated. I will continue to work on this and see if I can make it work. The phone I am using is SM-A037W and it has the latest firmware available that is available at the time of this posting
I'm thinking maybe I need to flash vbmeta with a certain flag but only recall doing that from powershell... somehow.
mindlery said:
Ok so I was able to successfully flash the modified (magisk patched) boot.img and I replaced it in the firmware package found here:
Samsung A037F U1 (A037FXXU1AUI7) Dead Boot Repair Scatter EMMC Dump File
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
I used this set of files to make the process possible:
Samsung A03s FRP All Android version.rar
drive.google.com
In the photo you'll notice things seemed to have gone well... but the phone now just boots to download mode.
I changed connection from UART to USB in the provided flash tool. Maybe that was my mistake. I must admit i am not too good at doing this stuff and am usually taking advantage of other people's ideas. Any help would be appreciated. I will continue to work on this and see if I can make it work. The phone I am using is SM-A037W and it has the latest firmware available that is available at the time of this posting
I'm thinking maybe I need to flash vbmeta with a certain flag but only recall doing that from powershell... somehow.
Click to expand...
Click to collapse
Try fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
r1pp3d2 said:
Try fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
Click to expand...
Click to collapse
Just use the original vbmeta.img from the backup? Don't need to edit it?