Device Status : locked, IMEI :null, signature verification failed - Lenovo K8 Note Questions & Answers

Whenever i am switching on my Lenovo K8 plus mobile device :
I am getting a blinking screen with this information ---
AP fastboot flashmode
Product/varient :null
serial number :null
IMEI :null
Console : null
battery Status : Ok
Engineering
Software Status : null
transfer mode : cable not connected
Device status : Locked
I tryed installing custom ROM after wiping data/factory reset and wiping cache but my installation is getting aborted with this information :----
Supported API 3.
E : Footer is wrong
E : Signature Verification failed
E: Error 21
Installation aborted

sumit_trivedhi
sumit_trivedi said:
Whenever i am switching on my Lenovo K8 plus mobile device :
I am getting a blinking screen with this information ---
AP fastboot flashmode
Product/varient :null
serial number :null
IMEI :null
Console : null
battery Status : Ok
Engineering
Software Status : null
transfer mode : cable not connected
Device status : Locked
I tryed installing custom ROM after wiping data/factory reset and wiping cache but my installation is getting aborted with this information :----
Supported API 3.
E : Footer is wrong
E : Signature Verification failed
E: Error 21
Installation aborted
Click to expand...
Click to collapse
I had same problem.

Root and repair imei any Qualcomm tool ..

Related

flashtool problems

Doesnt work
on flash tool i get these erorrs:
03/051/2012 19:51:43 - ERROR -
03/051/2012 19:51:43 - ERROR - Error flashing. Aborted
03/051/2012 19:51:45 - ERROR - Drivers need to be installed for connected device.
03/051/2012 19:51:45 - ERROR - You can find them in the drivers folder of Flashtool.
how do i sort this out i have installed the drivers

I am stuck with fastboot mode error : failed (remote flash write failure)

I am stuck with fastboot mode error : failed (remote flash write failure)
I am using a G3 phone. Which appeared to have a IMEI of d855 but its motherboard is of 850. I tried to flash kdz for 855 on it.. but now its stuck in fastboot mode with fastboot mode error : failed (remote flash write failure) . Whatever I've tried to do.. The same error appears.. any go around this error ??.. Please any help would be appreciated.. Thank you

HELP Please! Oneplus 3 Not booting

Hi all,
I installed CM14 on my OP3 but now after 5days somthing has happen.
The phone doesn't start I can see the logo and after that I see some check that it does.
cache : failed
boot: failed
boot-aging: failed
system: failed
Tried to do "technobuzz net / unbrick-oneplus-3"
But it doesn't work.
In fastboot under
Fastboot mode
PRODUCT_NAME - msm8996
VARIANT - MTP UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - ********
SECURE BOOT - enabled
Device state - locked
So I can't flash any thing and the recovery menu is not there.
I can only start the phone in Fastboot menu but no more.
Can anyone help my?
Can I boot some bootimage and login to CM14?
thefuse said:
Hi all,
I installed CM14 on my OP3 but now after 5days somthing has happen.
The phone doesn't start I can see the logo and after that I see some check that it does.
cache : failed
boot: failed
boot-aging: failed
system: failed
Tried to do "technobuzz net / unbrick-oneplus-3"
But it doesn't work.
In fastboot under
Fastboot mode
PRODUCT_NAME - msm8996
VARIANT - MTP UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - ********
SECURE BOOT - enabled
Device state - locked
So I can't flash any thing and the recovery menu is not there.
I can only start the phone in Fastboot menu but no more.
Can anyone help my?
Click to expand...
Click to collapse
same here
Is there any way to get the device state -locked to unlocked without having the OS?
C:\adb>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) Have console: false
(bootloader) Selinux type: <none>
(bootloader) Boot_mode: normal
(bootloader) Kmemleak_detect: false
OKAY [ 0.094s]
finished. total time: 0.095s
C:\adb>
I got it back from the repair yesterday, and they replaced my motherboard because of faulty motherboard.
install mod-twrp via fastboot
http://forum.xda-developers.com/devdb/project/dl/?id=21835 and install OxygenOS 3.2.6/3.2.8
You simply plug it into a pc and type fastboot oem unlock to unlock the device, then flash TWRP and reflash the OS
cache : failed
modem : failed
boot: failed
boot-aging: failed
system: failed
md5checksum: failed
I have same problem, i was on OOS b9
I flashed TWRP but can not restart to recovery, and also I flashed stock recovery but same problem ,
Any suggestion
Regards
almuhajir said:
cache : failed
modem : failed
boot: failed
boot-aging: failed
system: failed
md5checksum: failed
I have same problem, i was on OOS b9
I flashed TWRP but can not restart to recovery, and also I flashed stock recovery but same problem ,
Any suggestion
Regards
Click to expand...
Click to collapse
Unbrick guide, you will have to flaah these files manually.
Puddi_Puddin said:
Unbrick guide, you will have to flaah these files manually.
Click to expand...
Click to collapse
I got this problem after using (guide mega unbrick guide hard bricked)
http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
Yes. Boot into fastboot and see of windows device manager shows Kedacom. If it does boot into https://www.google.nl/amp/www.howto...signed-drivers/amp/?client=ms-android-oneplus then install http://www.technobuzz.net/download-oneplus-3-usb-drivers/ now go to device manager it still shows kedacom. (Im not fully sure) but there should be a option if you right click it to change it to Oneplus drivers. Try to play yourself with thid method. I had it aswell and fixed it. I cant give you a fully guide since im not homeless yet..
Puddi_Puddin said:
Yes. Boot into fastboot and see of windows device manager shows Kedacom. If it does boot into https://www.google.nl/amp/www.howto...signed-drivers/amp/?client=ms-android-oneplus then install http://www.technobuzz.net/download-oneplus-3-usb-drivers/ now go to device manager it still shows kedacom. (Im not fully sure) but there should be a option if you right click it to change it to Oneplus drivers. Try to play yourself with thid method. I had it aswell and fixed it. I cant give you a fully guide since im not homeless yet..
Click to expand...
Click to collapse
Dear,
its not show Kedacom with me
What does it show then? Otherwise try to manually flash these files.
Puddi_Puddin said:
What does it show then? Otherwise try to manually flash these files.
Click to expand...
Click to collapse
I'll try to flashed manually, i'll give you feedback
almuhajir said:
I'll try to flashed manually, i'll give you feedback
Click to expand...
Click to collapse
Otherwise well go back to the basics
1. Boot into fastboot type "Fastboot devices" does it show up? No? > Device Manager try to see if it shows something with Kedacomm.
2. Fastboot devices shows up? > Go to the unbrick program it has a file with all partitions. Flash the missing ones that you get on your screen manually, i assume that you know how fastboot works.
3. System boots yay! But no wifi Reflash OOS but dont boot! Go to Fastboot and type this
"fastboot erase modemst1"
"fastboot erase modemst2"
If you still didn't manage to fix it try to explain as clearly ss you can with what you are doing and what you have tried.
Puddi_Puddin said:
Otherwise well go back to the basics
1. Boot into fastboot type "Fastboot devices" does it show up? No? > Device Manager try to see if it shows something with Kedacomm.
2. Fastboot devices shows up? > Go to the unbrick program it has a file with all partitions. Flash the missing ones that you get on your screen manually, i assume that you know how fastboot works.
3. System boots yay! But no wifi Reflash OOS but dont boot! Go to Fastboot and type this
"fastboot erase modemst1"
"fastboot erase modemst2"
If you still didn't manage to fix it try to explain as clearly ss you can with what you are doing and what you have tried.
Click to expand...
Click to collapse
Thanx dear,
the problem now still in
cache : failed (dont have it)
modem : ok flash it via fastboot
boot: failed try but not show ok
boot-aging: failed (dont have it)
system: failed (dont have it)
md5checksum: failed (dont have it)
almuhajir said:
Thanx dear,
the problem now still in
cache : failed (dont have it)
modem : ok flash it via fastboot
boot: failed try but not show ok
boot-aging: failed (dont have it)
system: failed (dont have it)
md5checksum: failed (dont have it)
Click to expand...
Click to collapse
Either Method 1 or Method 2 has these files. Try to navigate the folders. Then manually flash them. If you really cant find them ill send you them later this day or tomorrow since im not home. To be exact your device does showup under fastboot devices.
Puddi_Puddin said:
Either Method 1 or Method 2 has these files. Try to navigate the folders. Then manually flash them. If you really cant find them ill send you them later this day or tomorrow since im not home. To be exact your device does showup under fastboot devices.
Click to expand...
Click to collapse
Many thanx dear,
now i download Method 2, i hope to get repair,
Thanx
almuhajir said:
Many thanx dear,
now i download Method 2, i hope to get repair,
Thanx
Click to expand...
Click to collapse
It will, it is software based.. If your device shows up under Fastboot then there is no problem If you have no wifi on boot make sure to post what i said before, keep in mind your device will be at 3.2.1 OOS.

need E9+ flashtools firmware full for unbreack totualy is dead

hi pls share htc e9+ flashtools firmware
phone is soft breack
Operation : Check / Read Info [ v1.58 ]
1. Power Off Phone , Remove battery , Insert back
2. Insert USB cable. In some cases require hold BootKey
Wait for phone...
Phone found! [ 7 ]
Sync...
Inital Boot Ok!
BB_CPU_PID : 6795
BB_CPU_NME : [MediaTek] Helio[X10]|MT6795_S00
BB_CPU_EXT : 0xCA00 , 0x8A00 , 0x0000
Processing BROM stage
Settings for BROM configured!
SecCfgVal : 0x00000000
BromVer : 0x00FF
BLVersion : 0x0001
PreLoader : Active [ Boot with PL ]
BootLdrSS : NORMAL with PRELOADER
Processing DA stage
DA Select done, will use MTK_AllInOne_DA_v5.1624.16.07
Sending and initialize DA ...
[DA_ERROR] : SECURITYBOOT_BOOT_NOT_ACCEPTED
Boot Error!
Operation Failed
Elapsed: 00:00:28
Reconnect Power/Cable!

Repairing a corrupted boot on GT-P5210

Recently, I discovered that I had this old device in my drawers so I decided to take it out to see if I could get it running. It wasn't charging or turning on at all, so I took the back off and replaced battery and connector, nothing. So, after plugging it in to my computer, I noticed a weird device named "CLOVERVIEW", which searching that up, is usually associated with ASUS devices, which is really weird. I followed a guide to repair a dead boot, using a zip file provided here.
I put the files into the correct spots in Phone Flash Tool 4.4.4, yet I only receive an error when flashing. It appears the IFW file flashes fine, but the DnX FW does not. Log provided below.
----
06/20/23 23:13:48.280 INFO : Loading Flash file ...
06/20/23 23:13:48.280 INFO : Ready to flash!
06/20/23 23:13:49.317 INFO : Port 0/4: Start flashing BLANKPHONE flash file for
06/20/23 23:13:49.317 INFO : Port 0/4: IFW flash started - SN : CDC36BFD990D9446
06/20/23 23:13:49.361 INFO : XFSTK-PROGRESS 0
06/20/23 23:13:49.361 INFO : XFSTK-STATUS Detecting Intel Device - Attempt #0
06/20/23 23:13:49.361 INFO : XFSTK-PROGRESS 5
06/20/23 23:13:50.490 INFO : Port 0/4: XFSTK-STATUS SN: CDC36BFD990D9446 FW download is in progress ...
06/20/23 23:13:50.490 INFO : Port 0/4: XFSTK-PROGRESS SN: CDC36BFD990D9446 3
06/20/23 23:13:50.491 INFO : Port 0/4: XFSTK-STATUS SN: CDC36BFD990D9446 Softfuses Binary absent. Please provide binary.
06/20/23 23:13:50.491 INFO : Port 0/4: XFSTK-STATUS SN: CDC36BFD990D9446 FAIL
06/20/23 23:13:50.491 INFO : Port 0/4: XFSTK-STATUS SN: CDC36BFD990D9446 Errors encounter during FW download. Aborting ...
06/20/23 23:13:50.491 INFO : Port 0/4: IFW flash success - SN : CDC36BFD990D9446
06/20/23 23:16:51.438 ERROR : Port 0/4: Device on port 0/4 timeout to enum adb (TIMEOUT = 180)
----
I'm not exactly sure what to do from here, the device still appears in Device Manager and I can't do anything about it from this point.

Categories

Resources