Greetings everyone! I have currently two issues where I can't get away from.
I'm currently unable to access download mode and recovery Mode due to Secure Booting Error 1003.
I can't format the phone either.
Only thing that I can do is access fastboot mode via doing recovery mode buttons method.
[470] fastboot_init()
[470] Loading keystore failed status 5 [570] USB init ept @0x8f20b000
[590] udc_start()
[690] -- reset --
[690] -- portchange --
[810] fastboot: processing commands
This is what appears on phone. At first I tried to root phone, didn't work, then I downgraded the phone and was able to root. Then I tried to root TWRP so I could flash the ROM and everything but somehow something didn't work that made me get secure boot error 1003. I tried to use flashify to flash images that probably weren't correct thus led me to be stuck on fastboot now. I downloaded SDK and ADB and I tried to erase laf.img and then try oem unlock with no success because it gave wrong command error.
I also tried LGUP method, the phone while on fastboot mode couldn't be found, even then when phone was on Android 5.0 rooted, It was unknown. So that method apparently didn't work out.
I'm still stuck here. Any help? Any ideas would be highly appreciated.
Try flashtool 2014 . Might not work with mm or higher kdz
I unbricked my G4 when lgup wouldn't recognise it and flashtool worked
Jason_L said:
Try flashtool 2014 . Might not work with mm or higher kdz
I unbricked my G4 when lgup wouldn't recognize it and flashtool worked
Click to expand...
Click to collapse
I gave a shot and it was unsuccessful. It says this:
The phone is disconnected from PC.
Connect the USB cable and wait a moment. Press the Retry button to resume the setting analysis process.
i got that spontaneously when i try to reboot and factory reset.It wasnt rooted so after i remove battery it works fine i'm not sure about that.
Related
Get rid of shutting down after "device corrupt" message - so possibility to gain root
Some of you might face the problem that whatever you do anything you change on your device in order to gain root even if your bootloader is unlocked your device is turning off after promting "device corrupt, etc..." message.
Sometimes you can't even unbrick with lg bridge cos' it can't see that your firmware has any problems.
Typical symptom of this problem that very interestingly your phone is not showing any corrupt messages during normal boot up even if your bootloader is unlocked (it should write some warnig message at every boot up).
Also when you "fastboot boot yourstockbootimage.img" it's booting up but writing some network related error then shuts down saying corrupt battery.
In order to root your phone you must be able to change the firmware a bit (tweak the boot image).
First of all you need to unlock your bootloader if you didn't do it yet: http://forum.xda-developers.com/lg-k10/how-to/unlock-bootloader-lg-k10-mtk-devices-t3486302
All you have to do is allow modifications in TWRP step 2.1 here: https://forum.xda-developers.com/lg-k10/how-to/friendly-root-method-lg-k8-k10-t3531223
It means the rest written under is fully unnecessary but i keep it just in case the above mentioned method would not work for someone:
Other requirements:
- lg up working with your device: http://forum.xda-developers.com/lg-k10/how-to/flashing-firmware-using-lg-t3517839
- kdz firmware
- twrp recovery of your device (usually you can find it in your favorite root thread or somewhere on xda)
Extract boot image from your firmware with lg firmware extractor (http://viid.me/qe7ufH). First you have to extract the ".dz" file and then the boot image form that ".dz" file.
Once you have your boot image (eg. boot_157696.bin) rename it to "boot.img"!
Put this "boot.img" on your sd card!
Flash this firmware (that you taken your boot image form!!!) on your phone with LG UP.
Boot up and see if it works also tick all the necessary options (oem unlock in developer options, usb debug,...)
Reboot to fastboot, check if your bootloader is still unlocked ("fastboot getvar all"). If it's locked unlock it!
Boot into your TWRP (fastboot boot twrp.img), you can allow it to read system.
Go to "install" (tick install image) and flash your "boot.img" form your sd card (naturally onto your boot partition).
Now before you reboot make a full wipe (fastory reset) in TWRP (wipe menu) then you can reboot to system.
After the "device corrupt" message it must be booting on and boot up normally and during every boot up there should be that message.
Now you can go and root your phone - always use that boot image you just flashed during the first step of the root process (recompress this boot image to gzip and ... read a rooting guide: http://forum.xda-developers.com/lg-k10/how-to/twrp-root-lg-k8-k350n-t3475807 there this should be "bootlz4_0.img")
There is no explanation why it works... wierd.
Hi.
I have this problem, corrupt device screen and continuous bootloops, I only have access to the download mode, but LG UP does not allow me to flash the .kdz even though I have the boot.img file on the sd card. It shows me the typical error at 9% of the process 'Error code = 0x81000304, CBasicFlash :: _func_LoadGptF - ErrorCode: 8222'. Would someone tell me what it is and how can I fix it?
I have tried to revive the cell phone in myriad ways and it is not possible for me.
I appreciate any suggestions.
Thank you very much.
Llony said:
I appreciate any suggestions.
Thank you very much.
Click to expand...
Click to collapse
This thread is not about bootloops but shutting down. Different subject. You should start a new thread about it.
However i looked at it, check out this comment:
http://forum.xda-developers.com/showpost.php?p=66135219&postcount=74
anyways if i were you i'd do a hard reset (http://www.hardreset.info/devices/lg/lg-k10/) and then i'd use lg bridge's update error recovery function (or you can change the order - first lg bridge, then hard reset).
Also make sure you chose "refurbish" when you use lg up and also make sure you are using the right kdz file (i recommend using lg mobile support tool to download your kdz - there is a possibility under options and upgrade recovery that using your imei it downloads the kdz to a hidden folder: http://forum.xda-developers.com/showthread.php?t=2395323)
I have bootloop with usb connected, without usb powered off
Llony said:
I have bootloop with usb connected, without usb powered off
Click to expand...
Click to collapse
I see... okay. However check out what i wrote above and one more thing: make sure you use usb 2.0 not any 3.0 ports.
I still do not find the solution, LG Up detects that it has installed the version k43010y, this version does not even exist! And I still give the error to 9% of the process. I do not know what to do to recover it
Llony said:
I still do not find the solution, LG Up detects that it has installed the version k43010y, this version does not even exist! And I still give the error to 9% of the process. I do not know what to do to recover it
Click to expand...
Click to collapse
Did you try lg bridge - update error recovery?
LG Bridge It does not give me the option to recover update error. And the LG flash tool before starting the process shows me 'contact the system administrator'. He does not let me get him back in any way.
Would it be possible to enter the fastboot mode through the download mode? So I guess I could try to flash an unmodified boot.
Thanks.
Llony said:
LG Bridge It does not give me the option to recover update error. And the LG flash tool before starting the process shows me 'contact the system administrator'. He does not let me get him back in any way.
Would it be possible to enter the fastboot mode through the download mode? So I guess I could try to flash an unmodified boot.
Thanks.
Click to expand...
Click to collapse
What do you mean it doesn't give you the option? I mean LG bridge, there is no update error recovery on the software update page? As in this video:
https://www.youtube.com/watch?v=b_GqAG02OXU
LG V20 910
On boot, it shows the LG logo, but does not start.
When I hold Vol up and plug in usb, the same thing happens
When I hold Vol down and plug in usb it does boot to fastboot
Factory reset gives a kernel crash error
adb does not recognize the device
fastboot via command prompt in windows does recognize it
LGUP does not recognize it
Is there a way for me to flash back to H91510e_00_VTR_CA_OP_1205.kdz with Fastboot, or is there another method to get download mode again?
How did you brick your phone? If you just turned it on one day and this happened, it is more than likely a hardware problem.
Since you say that you can get to fastboot -- I am guessing you were rooted since the H910 doesn't have fastboot without the engineering bootloader.
If so, then fastboot boot twrp.img
If TWRP will boot, you can fix your phone from that.
-- Brian
Its a 64 gb A1 variant. Everything was stock. It was on stock pie (update via OTA). I never tried unlocking bootloader as well as flashing custom rom.
3 day ago when i using it,suddenly it turn off and stuck at android one logo. I can go fastboot mode by pressing power+volume down.
I try to flash stock rom using mi flash tool,but as my bootloader is locked it show error. :crying:
Please help me out,it is my daily driver. :crying:
Use the fastboot oem unlock command and see what it does.
If the command is succesfully will trigger the factory reset of devices, but maybe you`ll get it to work.\
If the above command not working, maybe you can try to factory reset from recovery if you can boot into it.
In the end maybe a fastboot flash will do the trick.
punktnet said:
Use the fastboot oem unlock command and see what it does.
If the command is succesfully will trigger the factory reset of devices, but maybe you`ll get it to work.\
If the above command not working, maybe you can try to factory reset from recovery if you can boot into it.
In the end maybe a fastboot flash will do the trick.
Click to expand...
Click to collapse
I found this thread after i post this. Hope this will help me, though i am not try yet. I will update what happen. https://forum.xda-developers.com/showpost.php?p=78378088&postcount=43
use miunlock tool to unlock bootloader if you're not familiar with fastboot commands and as punktnet said unlocking bootloader will reset your device and erase your userdata and internal storage then maybe your device works fine if not then reboot it again in fastboot mode and flash stock firmware.
Facing similar issue. Am able to flash via test point method however still stuck when device is rebooted with this message;
Supported API: 3
E: Failed to clear BCB message: failed to FSync/dev/block/bootdevice/by-name/miscperation not permitted.
Any other solution?
WORKMEISTER said:
Facing similar issue. Am able to flash via test point method however still stuck when device is rebooted with this message;
Supported API: 3
E: Failed to clear BCB message: failed to FSync/dev/block/bootdevice/by-name/miscperation not permitted.
Any other solution?
Click to expand...
Click to collapse
This occurred to me today aswell :c I tried wiping all the data from recovery but the phone couldn't even end to wipe all. My phone went into a "erasing" screen for almost 1 hour when I decided trying to hold the power button, it rebooted but I still got into the bootloop :l my Xiaomi Mi A1 is not unlocked for bootloader so I can't flash it. I also tried with the mi unlocking but didn't go past 50% when it launched an error. Guess I'll die.
Can anyone help me out?
My asus selfie z00ud only opens fastboot mode. No bootloader, no recovery, no os. I tried flashing with flashall_aft.cmd but no success. At fastboot flash asdf asdf.img it says remote write failed and process intrrupts. I tried to flash twrp recovery. On screen it says successfully written over pc but no functioning on phone. When plug into adaptor it directly opens fastboot mode screen without pressing any button. On recovery mode shortcut it opens fastboot mode. Is their hardware problem? I tried with QFIL, but no success. Bootloder is locked and usb debugging was not on, when this fault came to my phone. Adb command only detects fastboot device.
Hey guys!
It's been a while since I've used my Mi A1. I turned it back on after a very long time and it was stuck on the android screen as if there was nothing to boot into so I tried booting into my recovery but there was nothing there either. I figured I probably formatted some stuff a while ago but I don't really remember what happened. Anyways, here's what I did next:
I could only boot into fastboot so I ran the command
Code:
fastboot boot path/to/tissot/twrp.img
but that didn't work.
So I flash the img to boot and tried rebooting to recovery but I was stuck on the android logo and again. I then again had to wait for my battery to run out before I could do anything else (I couldn't enter fastboot again. Only works when the phone is off for some reason)
I then erased the system partition using fastboot and tried booting into the recovery again but no luck. Can someone help me?
I know I messed up... big time. Someone save me
EDIT: Some more details
I tried two recoveries. The Pitch Black on XDA and also the standard "twrp-3.3.1-0-tissot.img" but had the same issue of getting stuck at the splash screen for both.
Also, I remember using Android 10 before all this happened.
EDIT 2: I ran the following commands:
Code:
fastboot set_active a
Code:
fastboot flash boot path/to/tissot/twrp.img
And I can now use the button combination to boot into recovery but I still get stuck on the splash screen
Hi,
have you fixed it? I face the same/similar issue, that I stuck at twrp splash screen after booting in twrp with fastboot
Code:
fastboot boot twrp-3.5.2_9-0-tissot.img
I have erased/formatted everything (userdata, cache, boot) and also tried to reflash the original rom with mi flash tool, but without success.
Any ideas?
MBR might be creating problem , try clean install with mi flash tool with official ROM .
@MIN313 Thanks for your response.
I tried to flash the official rom with the flash tool ( see here: https://forum.xda-developers.com/t/mi-a1-flash-sec-error.4139573/#_=_ ) .
xiaomiA1 said:
@MIN313 Thanks for your response.
I tried to flash the official rom with the flash tool ( see here: https://forum.xda-developers.com/t/mi-a1-flash-sec-error.4139573/#_=_ ) .
Click to expand...
Click to collapse
Does MiFlash recognize your phone? If not, try instaling ADB drivers nd disable driver enforcment,
To kick device out of diagnostic mode and into QDLoader you will need either:
1) A "deep flash" cable
2) Take the phone apart and bridge test points
There are guides online for both, you can Google. You can make deep flash cable yourself fairly easily with a spare USB cable. Testpoint location is found easily via Google and can be bridged with tweezers or small flat-head screw driver.
MIN313 said:
Does MiFlash recognize your phone? If not, try instaling ADB drivers nd disable driver enforcment,
To kick device out of diagnostic mode and into QDLoader you will need either:
1) A "deep flash" cable
2) Take the phone apart and bridge test points
There are guides online for both, you can Google. You can make deep flash cable yourself fairly easily with a spare USB cable. Testpoint location is found easily via Google and can be bridged with tweezers or small flat-head screw driver.
Click to expand...
Click to collapse
If Phone Showing Charging Only and Can't Even Transfer Data , Not Detected on Pc then will have to do EDL flash
My phone is recognized by MiFlash when I enter the fastboot mode
It is also shown with
Code:
fastboot devices
and I can boot into TWRP, but it stucks in splash screen of twrp.
Code:
fastboot boot twrp-3.5.2_9-0-tissot.img
I also tried older versions of twrp for tissot.
smilar issue, following attempts:
flashed with MiFlash, with or without EDL
flashed installing image with twrp
flashing after wiping dalwik, data, system and so on
flashed several type of ROM: official from xiaomi, crdroid, pixel, lineage
phone only booting with twrp (if installed) or stuck on mi logo