Fastboot command to get Product ID of your device - Xiaomi Redmi 2 Questions & Answers

Hello all !
I just wanna know that if there is a bootloop in a device and you cannot get product ID of your device to unlock bootloader so is there any other way that you can get product ID of your device. I can access the fastboot of my device .
FYI: I have tried contacting the particular device site through email. I have tried almost everything . If any one knows any fastboot command to get device/Product ID of the device it would be of great help.
Thanks in advance

up

fastboot getvar product

dmmbbs said:
fastboot getvar product
Click to expand...
Click to collapse
tnx
this working

Related

[Q] Bricked and clueless ..

ok have an Iconia tab a500 here from a friend, he tells me he put in wrong adapter.
I think its bricked ..
ALready read alot of stuff here and did try some things but cant seem to find the correct solution .
I can connect in apx or fastboot and adb recognizes it also these all come up as hardware..
i dont have cpuid and thing is locked also and have usb debugging prob and isnt rooted ...
Bootloader = V0.0312-ics
if i start up i get " boot veriefied failed"
i found some downgrading method on here "method 2" but when i do it and he reboots i get the message "abort illegal blabla"
I would really appreciate if someone could help me point me in the right direction to start.
Using win7
also .. for repairing this thing ... i never came across such a complicated tablet .. djeez
Thx in advance
Grtz
Dhont said:
ok have an Iconia tab a500 here from a friend, he tells me he put in wrong adapter.
I think its bricked ..
ALready read alot of stuff here and did try some things but cant seem to find the correct solution .
I can connect in apx or fastboot and adb recognizes it also these all come up as hardware..
i dont have cpuid and thing is locked also and have usb debugging prob and isnt rooted ...
Bootloader = V0.0312-ics
if i start up i get " boot veriefied failed"
i found some downgrading method on here "method 2" but when i do it and he reboots i get the message "abort illegal blabla"
I would really appreciate if someone could help me point me in the right direction to start.
Using win7
also .. for repairing this thing ... i never came across such a complicated tablet .. djeez
Thx in advance
Grtz
Click to expand...
Click to collapse
how do you get fastboot with the ics bootloader??? Just wondering out loud!
you can try fastboot first see this thread and try flashing the recovery.img there
http://forum.xda-developers.com/showthread.php?t=2092414
run fastboot devices command and see if it returns you a ?
if it does go ahead and run the erase commands for userdata and cache
then flash cwm_recovery.img
kk
dibb_nz said:
how do you get fastboot with the ics bootloader??? Just wondering out loud!
you can try fastboot first see this thread and try flashing the recovery.img there
http://forum.xda-developers.com/showthread.php?t=2092414
run fastboot devices command and see if it returns you a ?
if it does go ahead and run the erase commands for userdata and cache
then flash cwm_recovery.img
Click to expand...
Click to collapse
Yes in fastboot it ruturn the "? fastboot"
my Bootloader that shows up when in fastboot says on acer screen :bootloader v0.03.12-ics rest of screen is black
in fastboot when i do oem unlock says in my terminal that it worked .. and on the pad the acer logo apears ..
if i ask for version it says 4.0
if i ask for serial he says : Kal-E1001
i read on site here that yer usb\UID has much to do with cpuid... my usb\uid is something like SB\VID_0502&PID_3201\5&1dd2df13&0&1 if fastboot connected i see it with usbdeview
if connected in usb recovery i see USB\VID_0955&PID_7820\5&1dd2df13&0&1 in deview
how to these relate to cpuid? or they have something to do with the kal-E1001?
Also i live in Belgium ... so i cant figure out wich or what packages to download but i got several yes .. prolly all ...
JUst info i wanted to give ..
But thx for the File gonna try that 1 now
Dhont said:
Yes in fastboot it ruturn the "? fastboot"
my Bootloader that shows up when in fastboot says on acer screen :bootloader v0.03.12-ics rest of screen is black
in fastboot when i do oem unlock says in my terminal that it worked .. and on the pad the acer logo apears ..
if i ask for version it says 4.0
if i ask for serial he says : Kal-E1001
Click to expand...
Click to collapse
bootloader version v0.03.12-ics this is the stock bootloader which is locked
i read on site here that yer usb\UID has much to do with cpuid... my usb\uid is something like SB\VID_0502&PID_3201\5&1dd2df13&0&1 if fastboot connected i see it with usbdeview
if connected in usb recovery i see USB\VID_0955&PID_7820\5&1dd2df13&0&1 in deview
how to these relate to cpuid?
Click to expand...
Click to collapse
This is what you need to see "0502" under VendorID and 3325 "ProductID", so again the numbers you posted arent the right ones
you need Linux to get your cpuid - there IS no other way for you now
see eppeP's method in the guide or the sticky in general by srbeen
Until you do this your tab will remain bricked -
Last resort - you might ask your friend to run usbdeview from his PC
dibb_nz said:
bootloader version v0.03.12-ics this is the stock bootloader which is locked
This is what you need to see "0502" under VendorID and 3325 "ProductID", so again the numbers you posted arent the right ones
you need Linux to get your cpuid - there IS no other way for you now
see eppeP's method in the guide or the sticky in general by srbeen
Until you do this your tab will remain bricked -
Last resort - you might ask your friend to run usbdeview from his PC
Click to expand...
Click to collapse
There is also the option of building against the Windows Driver Kit using MSVC.
This have the slight disadvantage of having to download about 1300MB (MSVC+WDK) and no instructions if you don't have any idea how to compile.
Besides having to have Windows...

[Q] Permanent problem with Unlocking Bootloader Nexus S

Hi guys,
I searched forums, web with no positive results. So I start a new thread. Here is the situation: one day my Nexus S (Worldwide edition) froze on restarting with the Google Logo on the screen. Every time I try to turn the phone on it stacks at Google logo. When in the fastboot mode the status is Locked. Every time I try fastboot oem unlock I get Phone’s prompt with Yes or Not to unlock bootloader and after choosing Yes, the status doesn’t change to Unlock. Tried on Linux, Mac, Windows (drivers installed successfully), the same result. Tried to force Flash Stock + Unroot in Wugfresh, doesn’t work due to the Locked Bootloader.
typing "adb devices" in cmd (should return the device number) shows:
List of devices attached
......
Empty line above
Any word of advise how to force Unlocking the Bootloader would be greatly appreciated. Please help. Thank you!
alpheus said:
Hi guys,
I searched forums, web with no positive results. So I start a new thread. Here is the situation: one day my Nexus S (Worldwide edition) froze on restarting with the Google Logo on the screen. Every time I try to turn the phone on it stacks at Google logo. When in the fastboot mode the status is Locked. Every time I try fastboot oem unlock I get Phone’s prompt with Yes or Not to unlock bootloader and after choosing Yes, the status doesn’t change to Unlock. Tried on Linux, Mac, Windows (drivers installed successfully), the same result. Tried to force Flash Stock + Unroot in Wugfresh, doesn’t work due to the Locked Bootloader.
typing "adb devices" in cmd (should return the device number) shows:
List of devices attached
......
Empty line above
Any word of advise how to force Unlocking the Bootloader would be greatly appreciated. Please help. Thank you!
Click to expand...
Click to collapse
It looks like your device is not recognized in Fastboot mode...
Have you turned on USB Debugging while connecting PC and Allow in Device when Prompt some message ..
Go to fastboot mode and write this command... fastboot devices
If it will give you a message like this
List of devices
1235456785164
Then your devices is successfully recognized...:good:
It is not recognized by adb devices, but:
fastboot devices - gives the following output:
ERROR: could not get pipe properties
3331E6EBCA6000EC fastboot
Click to expand...
Click to collapse
fastboot oem unlock - gives the following:
ERROR: could not get pipe properties
...
FAILED (remote: Erase Fail)
finished. total time: 4.753s
Click to expand...
Click to collapse
alpheus said:
It is not recognized by adb devices, but:
fastboot devices - gives the following output:
fastboot oem unlock - gives the following:
Click to expand...
Click to collapse
Pretty sure you have a bad USB cable, the error means the fastboot binaries are working on PC but can not connect to device, often this is due to a bad USB cable or port
Try a new cable, one you can verify works transferring data
demkantor said:
Pretty sure you have a bad USB cable, the error means the fastboot binaries are working on PC but can not connect to device, often this is due to a bad USB cable or port
Try a new cable, one you can verify works transferring data
Click to expand...
Click to collapse
Thanks, I tried 3 different cables on 3 different operating systems, with the same problem unlocking the fastboot. When I send fastboot oem unlock the device opens a prompt with Yes or No choice, but after choosing Yes, it stays Locked
Something indeed is strange...
So fastboot is for bootloader and adb is for within os and in recovery.
Try booting into recovery and see if adb works, also boot normal into your bootloop and see if adb works there too
demkantor said:
Pretty sure you have a bad USB cable, the error means the fastboot binaries are working on PC but can not connect to device, often this is due to a bad USB cable or port
Try a new cable, one you can verify works transferring data
Click to expand...
Click to collapse
demkantor said:
Something indeed is strange...
So fastboot is for bootloader and adb is for within os and in recovery.
Try booting into recovery and see if adb works, also boot normal into your bootloop and see if adb works there too
Click to expand...
Click to collapse
Loading into basic recovery and trying to wipe data/factory reset - doesn't work. adb devices returns the following output:
./adb-linux devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
****empty line here****
Somehow, adb doesn't recognize the device, whereas fastboot devices shows it.
Is there a way to flash new bootmode with the currently locked bootloader?
Thank you!
alpheus said:
Loading into basic recovery and trying to wipe data/factory reset - doesn't work. adb devices returns the following output:
./adb-linux devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
****empty line here****
Somehow, adb doesn't recognize the device, whereas fastboot devices shows it.
Is there a way to flash new bootmode with the currently locked bootloader?
Thank you!
Click to expand...
Click to collapse
I am damn Sure What's Your problem is, ADB is not working..
PROCEDURE:-
1) Download My attachement and unzip it and Place it in Folder...
See image 1.png
2) Go to that folder and Press CTRL+SHIFT+ Right click on mouse and Select Open Command Window here..
See image 2.png
3) Now type here Fastboot devices and Now you will get Those list of devices Number..
See image 3.png
If Everything will be done as Procedure and you will get List of devices Number... Now, You type those command for Unlocking bootloader and Root Your Devices...:good:
Hope this Guide will help..
UPDATE (resolved)
Here is an update. Hope this would help others with similar issue, as I've read many threads and folks complaining that they weren't able to unlock fastboot and further root their Nexus S, and who can't boot the phone, which stacked with Google Logo (soft loop). This was the case with my device and finally I got it resolved. I've read some guy tried to hit the phone and after that he was able to boot phone normally. It related to some hardware electrical circle issue. Anyways, I tried to hit my phone by placing it under the direct sun in balcony for some time until the phone got hot and then power it on. And ooops, my phone started booting passed by that Google Logo which was the good sign. Once the phone booted up, I went ahead and activated USB debugging and restarted the phone into the Fastboot mode. while the phone was still hot and in Fastboot mode I run "fastboot oem unlock" and hey, fastboot is Unlocked! Again, this was done while the phone was hot, any previous attempts (read above) weren't successful. From that point, I went ahead and rooted my Nexus S by Nexus Root Toolkit, available on wugfresh.com/nrt, without a slightest problem. Now my phone is fully rooted, bootable and working fine. I thank all who replied to my thread and tried to help and hope this info would help someone with the similar issue.
Rushabh22 said:
I am damn Sure What's Your problem is, ADB is not working..
PROCEDURE:-
1) Download My attachement and unzip it and Place it in Folder...
See image 1.png
2) Go to that folder and Press CTRL+SHIFT+ Right click on mouse and Select Open Command Window here..
See image 2.png
3) Now type here Fastboot devices and Now you will get Those list of devices Number..
See image 3.png
If Everything will be done as Procedure and you will get List of devices Number... Now, You type those command for Unlocking bootloader and Root Your Devices...:good:
Hope this Guide will help..
Click to expand...
Click to collapse
Thank you for your help and suggestions.
Q Mobile X 32
bootloader oem unlock problem
plz help
Q-mobile said:
Q Mobile X 32
bootloader oem unlock problem
plz help
Click to expand...
Click to collapse
Wrong device thread..
Try here..
https://forum.xda-developers.com/showthread.php?t=2363923
Setting.Out said:
Wrong device thread..
Try here..
https://forum.xda-developers.com/showthread.php?t=2363923
Click to expand...
Click to collapse
can you help me in rooting Qmobile x32
Q-mobile said:
can you help me in rooting Qmobile x32
Click to expand...
Click to collapse
That thread didn't help?
Here's what the guide says...

Get product ID using fastboot

Hello all,
while doing the update, the phone fell into the loop. I decided therefore to use fastboot to reinstall the system. Unfortunately, to unlock fastboot, I need a product ID, which can not I get by dialing *#*#1357946#*#*. So I ask: Is there any other method by which the product will obtain ID phone?
Regards
use program huaweiproductidgenerator it generates your product id : http://rootjunkysdl.com/?device=Huawei P8 Lite
please help me
My phone does not boot it is in fastboot mode
It hangs at logo
I can't obtain the product ID
please send me the product ID or
Bootloader code
Details;
Model: Huawei Ascend G630-U10
Please send me the product
Becky pac said:
please help me
My phone does not boot it is in fastboot mode
It hangs at logo
I can't obtain the product ID
please send me the product ID or
Bootloader code
Details;
Model: Huawei Ascend G630-U10
Please send me the product
Click to expand...
Click to collapse
http://rootjunkysdl.com/files/Huawei P8 Lite/Huawei unlock bootloader.zip
can u please help me generate bootloader unlock my phone is in bootloop
Huawei g526-L11
please help me to get my Huawei product id,
Model No: U9500
you can dial *#*#1357946#*#* and copy it manually. It is a pretty short number. For me the product code generator did not work
Edit: sorry did not Read about the bootloop
My phone fell down in water after that my IMEI no become NUll & Sound & Video is not working any one can help to solve this issue & product ID not generating
model No kiw-l21
please help me to get my Huawei product id,
Model No: PLE-701L
majdicher said:
please help me to get my Huawei product id,
Model No: PLE-701L
Click to expand...
Click to collapse
Please remove your IMEI
are you out of your don't ask questions just delete your serial number and IMEI
JuCeLo said:
1. Boot phone into "Fastboot&Rescure Mode"
2. Plug phone cable into PC and your phone.
3. Open Windows Explorer and open cmd in the folder where you installed ADB.
4. Type
Code:
fastboot devices
.
5. Now any Number is displaying and on the right of it is "fastboot" displaying.
Thats it!
- Windows 10 Home
Click to expand...
Click to collapse
No that is not it, at least in my case.
please help me to get my Huawei product id,
Model No: MHA-L09B
[email protected] said:
please help me to get my Huawei product id,
Model No: MHA-L09B
Click to expand...
Click to collapse
What you get in the display when you dial on the dial pad the following?
*#*#1357946#*#*
kilroystyx said:
What you get in the display when you dial on the dial pad the following?
*#*#1357946#*#*
Click to expand...
Click to collapse
Unfortunately my phone is bricked.... so thats why i cant get the product id.
[email protected] said:
Unfortunately my phone is bricked.... so thats why i cant get the product id.
Click to expand...
Click to collapse
Can you reboot into bootloader with current bricked status?
I can go into fastboot mode but its locked, so what i want to do is unlock it so i can use and fastboot rom to fix the phone.
[email protected] said:
I can go into fastboot mode but its locked, so what i want to do is unlock it so i can use and fastboot rom to fix the phone.
Click to expand...
Click to collapse
Before that you can try force update via dload folder, did you already tried?
Already tried that. When a i try that, the phone displays a red lightning... Its basically not charging. Agter that it goes into the huawei logo screen and freezes.
Please, can get me the unlocked code for:
Huawei G535-L11
SN: Y4M7N15320003434
IMEI: 864045022778773
Thanks a lot!
help
please help me
huawei p8 lite ale-l21

device not unlocked cannot install image oneplus 2

Hi Guys,
My OnePlus 2 has this issue where if i restart the phone it gets stuck on the Boot Screen which shows OnePlus Logo powered by Android.
I can boot my phone to Fastboot and i can only boot into the phone by using command "fastboot continue"
When i try to use command "fastboot oem unlock" the phone reboots and gets stuck on the OP logo
Fastboot oem device-info shows
... INFO Device tampered: true
INFO Device unlocked: false
INFO Device is_verified: false
INFO Charger screen enabled: false
INFO Display panel:
INFO console_locked: 1
INFO exec_console_unconsole: 0
OKAY
and if i try to install twrp recovery by using the command "fastboot flash recovery recovery.img" i get the following message
sending 'recovery' (25956 KB)... OKAY
writing 'recovery'... FAILED (remote: device is locked. Cannot flash images)
Please help
http://forum.xda-developers.com/oneplus-2/general/guide-oneplus-2-mega-unbrick-recover-t3397257
I have tried all those methods and none of them worked for me
pankaj2m said:
I have tried all those methods and none of them worked for me
Click to expand...
Click to collapse
Go to oneplus website & download official rom zip file. Push it into sdcard using fastboot. Go to stock recovery (vol_down + power) & flash the zip file.
I can't boot into to recovery hence can't flash.. I have the official rom zip from oneplus but can't flash it as I can't boot into recovery.. That's the problem
Can anyone please help me with this?? :'(
pankaj2m said:
Hi Guys,
My OnePlus 2 has this issue where if i restart the phone it gets stuck on the Boot Screen which shows OnePlus Logo powered by Android.
I can boot my phone to Fastboot and i can only boot into the phone by using command "fastboot continue"
When i try to use command "fastboot oem unlock" the phone reboots and gets stuck on the OP logo
Fastboot oem device-info shows
... INFO Device tampered: true
INFO Device unlocked: false
INFO Device is_verified: false
INFO Charger screen enabled: false
INFO Display panel:
INFO console_locked: 1
INFO exec_console_unconsole: 0
OKAY
and if i try to install twrp recovery by using the command "fastboot flash recovery recovery.img" i get the following message
sending 'recovery' (25956 KB)... OKAY
writing 'recovery'... FAILED (remote: device is locked. Cannot flash images)
Please help
Click to expand...
Click to collapse
Try the first method in this page https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Its worked in my mobile, when i lost everything (even fastboot also gone). Its surely work. It will flash Oneplus 2 official recovery. You should ensure that your device is detected in your computer and Its shows as Qualcomm 9008
eldos777 said:
Try the first method in this page https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Its worked in my mobile, when i lost everything (even fastboot also gone). Its surely work. It will flash Oneplus 2 official recovery. You should ensure that your device is detected in your computer and Its shows as Qualcomm 9008
Click to expand...
Click to collapse
I followed the all the 3 methods from the post you mentioned.
When i run MSM8994DownloadTool and START, it just stays there. I waited for 1hr for something to happen but nothing.
It Doesnot work for me.
For now, i use Fastboot Continue command in fastboot in case my devices shuts down
pankaj2m said:
I followed the all the 3 methods from the post you mentioned.
When i run MSM8994DownloadTool and START, it just stays there. I waited for 1hr for something to happen but nothing.
It Doesnot work for me.
For now, i use Fastboot Continue command in fastboot in case my devices shuts down
Click to expand...
Click to collapse
Thats means your device is not detected, Did you check device manager in your computer? Is is showing your mobile as Qualcomm 9008?? If it is not please follow the steps on the website, I already given. No need wait 1 hr. If your device is detected, then you can see a green line, and it will finish within 5mnts.
eldos777 said:
Thats means your device is not detected, Did you check device manager in your computer? Is is showing your mobile as Qualcomm 9008?? If it is not please follow the steps on the website, I already given. No need wait 1 hr. If your device is detected, then you can see a green line, and it will finish within 5mnts.
Click to expand...
Click to collapse
Hi Eldos,
In device manager it shows as RELINK HS-USBQDLoader 9008 (COM8)
i followed your instructions but it still does not work. When i run the MSM8994DownloadTool, it does not do anything.
Anything else i can try. I am stuck in this big problem. When my phone switches off, the only way i can boot is by going to FASTBOOT and running command "fastboot continue" only then my phone boots.
Please help.
Thanks,
Pankaj
pankaj2m said:
Hi Eldos,
In device manager it shows as RELINK HS-USBQDLoader 9008 (COM8)
i followed your instructions but it still does not work. When i run the MSM8994DownloadTool, it does not do anything.
Anything else i can try. I am stuck in this big problem. When my phone switches off, the only way i can boot is by going to FASTBOOT and running command "fastboot continue" only then my phone boots.
Please help.
Thanks,
Pankaj
Click to expand...
Click to collapse
Can you come in Team Viewer??
eldos777 said:
Can you come in Team Viewer??
Click to expand...
Click to collapse
Yes, sure.. how do i talk to you?
pankaj2m said:
Yes, sure.. how do i talk to you?
Click to expand...
Click to collapse
Give me your Teamviewer ID and Password
eldos777 said:
Give me your Teamviewer ID and Password
Click to expand...
Click to collapse
ID: 527533613
Password: 6953
pankaj2m said:
Can anyone please help me with this?? :'(
Click to expand...
Click to collapse
PM me
Problem Solved
Deep problem
I have gone through all the unbrick guides, even with a Oneplus technician but we weren't able to unbrick it. I'm guessing that after the oxygen 3.0.2 update, I wiped out the partition (not sure). The phone was unlocked with some TWRP version before that. I totally forgot to update it the right way. I can get use fastboot to go into the OS, but trying to flash doesn't work since it's locked. Trying to unlock it supposedly works but it remains locked. We tried the Qualcomm drivers, installed the certificates and the device is seen as Qualcomm 9800 yadda, yadda, yadda, but the MSM8994DownloadTool.exe doesn't detect the device, therefore it stays there doing nothing. Yes, we changed the developer options in the settings but nothing seems to work. The LTE doesn't work properly either...it shows an exclamation mark, so I have to switch to 3G. I'm in dire need of help, and if anyone can help me, you'd certainly qualify for a master tech support agent or something cause not even they could help me with this. Thanks in advance if any of you can help! I'm using a Windows 10 on a Mac, using Parallels VM...
CharlieVasquez said:
I have gone through all the unbrick guides, even with a Oneplus technician but we weren't able to unbrick it. I'm guessing that after the oxygen 3.0.2 update, I wiped out the partition (not sure). The phone was unlocked with some TWRP version before that. I totally forgot to update it the right way. I can get use fastboot to go into the OS, but trying to flash doesn't work since it's locked. Trying to unlock it supposedly works but it remains locked. We tried the Qualcomm drivers, installed the certificates and the device is seen as Qualcomm 9800 yadda, yadda, yadda, but the MSM8994DownloadTool.exe doesn't detect the device, therefore it stays there doing nothing. Yes, we changed the developer options in the settings but nothing seems to work. The LTE doesn't work properly either...it shows an exclamation mark, so I have to switch to 3G. I'm in dire need of help, and if anyone can help me, you'd certainly qualify for a master tech support agent or something cause not even they could help me with this. Thanks in advance if any of you can help! I'm using a Windows 10 on a Mac, using Parallels VM...
Click to expand...
Click to collapse
I finally got the MSM tool to detect the phone. While still in Qualcomm mode, I disconnected it and connected it to the to Mac usb ports and kept clicking on the tool to start. The green lights finally showed and I'm waiting to see what happens. I will keep you updated.
CharlieVasquez said:
I finally got the MSM tool to detect the phone. While still in Qualcomm mode, I disconnected it and connected it to the to Mac usb ports and kept clicking on the tool to start. The green lights finally showed and I'm waiting to see what happens. I will keep you updated.
Click to expand...
Click to collapse
K, I finally booted normally into the OS, went back and rooted the phone. Now we're good to go again. Not even the tech support agents were able to help me with this one.

Huawei P9 lite Vns L23 bricked

Hello, im new to the forums and i would like to get some help with this huawei on what to do. I recieved this phone already bricked from a friend, so i would like to see if i can make it work again. I dont know how the phone got bricked and i have no idea of what to do. The problem is that the phone starts in the huawei logo and then goes to a black screen and turns itself off again. The phone doesnt make it past that point. I tried to make a reset from recovery, but it doesnt work. In download mode i tried to download the latest recovery, but it says failed to download. In fastboot mode the phone says "Phone unlocked" in red letters and "FRP locked" in green letters.
Any idea of what to do in order to recover the phone ?.
BrattPitlord said:
Hello, im new to the forums and i would like to get some help with this huawei on what to do. I recieved this phone already bricked from a friend, so i would like to see if i can make it work again. I dont know how the phone got bricked and i have no idea of what to do. The problem is that the phone starts in the huawei logo and then goes to a black screen and turns itself off again. The phone doesnt make it past that point. I tried to make a reset from recovery, but it doesnt work. In download mode i tried to download the latest recovery, but it says failed to download. In fastboot mode the phone says "Phone unlocked" in red letters and "FRP locked" in green letters.
Any idea of what to do in order to recover the phone ?.
Click to expand...
Click to collapse
Hello and welcome !
Just thinking you should try to start a fresh & clean install
rolling back to android 6 regardless of the current firmware.
Took a look inside the UNIFIED HELP THREAD but didn't find
any L23 rollback package...
However, I found another LINK that looks promising.
Good luck :fingers-crossed:
For further explanations try asking here.
Dadditz said:
Hello and welcome !
Just thinking you should try to start a fresh & clean install
rolling back to android 6 regardless of the current firmware.
Took a look inside the UNIFIED HELP THREAD but didn't find
any L23 rollback package...
However, I found another LINK that looks promising.
Good luck :fingers-crossed:
For further explanations try asking here.
Click to expand...
Click to collapse
Nice, i will try this and inform back later.
Dadditz said:
Hello and welcome !
Just thinking you should try to start a fresh & clean install
rolling back to android 6 regardless of the current firmware.
Took a look inside the UNIFIED HELP THREAD but didn't find
any L23 rollback package...
However, I found another LINK that looks promising.
Good luck :fingers-crossed:
For further explanations try asking here.
Click to expand...
Click to collapse
Well it didnt work. It says "incompatibility with this version"
BrattPitlord said:
Well it didnt work. It says "incompatibility with this version"
Click to expand...
Click to collapse
Hi,
you should use the follovinq commands in fastboot mode and then post the results please:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar version
fastboot getvar vendorcountry
Can you access Recovery ? (Power + Volume Up)
-Alf- said:
Hi,
you should use the follovinq commands in fastboot mode and then post the results please:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar version
fastboot getvar vendorcountry
Can you access Recovery ? (Power + Volume Up)
Click to expand...
Click to collapse
im new to this, so i put those commands in windows CMD with the phone connected or how ?
I can get to the stock recovery from huawei.
BrattPitlord said:
im new to this, so i put those commands in windows CMD with the phone connected or how ?
I can get to the stock recovery from huawei.
Click to expand...
Click to collapse
Use ADB commands.
Open developers option and turn on the USB debugging. Connect your device to PC in MTP/FILES mode. Run command
ADB reboot bootloader
(the device will reboot to fastboot mode)
Now you can type fastboot commands.
-Alf- said:
Use ADB commands.
Open developers option and turn on the USB debugging. Connect your device to PC in MTP/FILES mode. Run command
ADB reboot bootloader
(the device will reboot to fastboot mode)
Now you can type fastboot commands.
Click to expand...
Click to collapse
How do i turn debugging if the phone is bricked ? I cant get past the huawei logo. However, i do have access to fastboot mode.
BrattPitlord said:
How do i turn debugging if the phone is bricked ? I cant get past the huawei logo. However, i do have access to fastboot mode.
Click to expand...
Click to collapse
Oh, sorry, my mistake . Okay, install on your PC "Minimal ADB and fastboot" , open it , connect the device in fastboot mode, and run commands.

Categories

Resources