Ayuda de algun experto mi telefono se quedo en esto y no enciende.
Error: boot certification verify
--------------------------------------------
460: secure booting error
460: cause: boot certification verify
--------------------------------------------
I don't now speak very good english.
Can you boot into Download mode and flash your device's KDZ?
Sent from my D620r [Stock 4.4.2]
not download not recovery
Vagelis1608 said:
Can you boot into Download mode and flash your device's KDZ?
Sent from my D620r [Stock 4.4.2]
Click to expand...
Click to collapse
I can not get to download or recovery and my PC does not recognize it off.
My phone is the LG logo appears and turns off again giving the error message.
thejarolmh said:
I can not get to download or recovery and my PC does not recognize it off.
My phone is the LG logo appears and turns off again giving the error message.
Click to expand...
Click to collapse
how do you try to enter the download mode ? because i did it wrong first time and stuck about 2 hours...
I have the same problem now i wanted to back to stock it showed this error. How to fix it :/
Related
Hi all..... i have a problem rooting my phone Alcatel OT-918(without any thing) when i flash the recovery.img this error pops up
"Eboot error 16008
android partition size changed..... etc"
and the flashing progress doesnt start
i have rooted before with the same pc and the same drivers installed and works well but i wiped cache from recovery and then the phone fails to boot and after many trys to fix boot i reinstall stock rom with alcatel upgrade tool and after that cant root it again cuz of the error 16008.... can any one help me plz ......thnx in advance
ot918 recovery
Bassem.Outlandish said:
Hi all..... i have a problem rooting my phone Alcatel OT-918(without any thing) when i flash the recovery.img this error pops up
"Eboot error 16008
android partition size changed..... etc"
and the flashing progress doesnt start
i have rooted before with the same pc and the same drivers installed and works well but i wiped cache from recovery and then the phone fails to boot and after many trys to fix boot i reinstall stock rom with alcatel upgrade tool and after that cant root it again cuz of the error 16008.... can any one help me plz ......thnx in advance
Click to expand...
Click to collapse
amigo tengo el mismo problema con un ot918 no se si encontrastes alguna solucion si me puedes ayudar porfa y gracias
1.LG G2 stuck at boot logo.
2.Cannot enter download Mode
4.cannot enter fastboot mode
5.Phone not detecting in the computer either windows or linux! (only ADB SIdeload - assert failed: run_program("/tmp/loki.sh") == 0 assert failed: run_program("/tmp/loki.sh") == 0)
Accidentalmente actualice vía OTA estando rooteado
No entra en "Download Mode"
No sale haciendo Wipe Data desde Recovery ni Factory Reset desde Combinacion de Botones.
Please close the thread, problem solved
That's not the way.
Although you've found the solution to your issue, user might search the forum for the same issue and the will either pm you or make another thread.
You can at least write how you've fixed it.
nulling fota partition and misc if needed from twrp is one way.
1° http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
- First this to get the qhsusb mode
2°http://downloads.codefi.re/autoprime/LG/LG_G2/D802/Stock_Firmware/10b_16G_partitions
-Second: I downloaded this files and used this guide; http://forum.xda-developers.com/showthread.php?t=2582142 for put the files in the phone, after this i can enter to the recovery TWRP and use ADB Push to move a ROM to the phone.
3°http://forum.xda-developers.com/showthread.php?t=2451696
- This to fix the booting and enter to the ROM
Sorry for my english.
Dear all
I just got v10 [H901] t-mobile ver from friend its info:
Android:5.1.1
Build no.:LMY47V
Software version:H90110c
Root:yes (rly!!)
BL: dunno [can't enter ]
Recovery: stuck at stock
1. Tried to use LG bridge to update stuck at remove battery and retry bla bla
2. Tried to use LGUP all ver model is unknown
3. Tried to enter BL using fastboot phone boots normal adb works perfect but don't boot to BL ever
4. Tried to use power+vol down phone boots normal as i said wtf that phone
5. Tried to flash twrp using flashify shows error scure boot error 1002 modifed then boots normal
Please guys help me or tell me way to damage that phone
Btw i loved that phone but its so hard to modify!!
Thanks in advance
BR
3andala said:
Dear all
I just got v10 [H901] t-mobile ver from friend its info:
Android:5.1.1
Build no.:LMY47V
Software version:H90110c
Root:yes (rly!!)
BL: dunno [can't enter ]
Recovery: stuck at stock
1. Tried to use LG bridge to update stuck at remove battery and retry bla bla
2. Tried to use LGUP all ver model is unknown
3. Tried to enter BL using fastboot phone boots normal adb works perfect but don't boot to BL ever
4. Tried to use power+vol down phone boots normal as i said wtf that phone
5. Tried to flash twrp using flashify shows error scure boot error 1002 modifed then boots normal
Please guys help me or tell me way to damage that phone
Click to expand...
Click to collapse
you may read here just for more information about h901 : https://forum.xda-developers.com/tmobile-lg-v10/general/unbrick-h901-f600l-board-2017-t3635697
samy2015 said:
you may read here just for more information about h901 : https://forum.xda-developers.com/tmobile-lg-v10/general/unbrick-h901-f600l-board-2017-t3635697
Click to expand...
Click to collapse
Many thanks bro but my v10 boots normal np
I just can't update or enter bootloader dunno why
But download mode boots & recovery boots os boots perfect too
Any help please ?
I was trying to install LineageOS rom on my Walton Primo GH7.
My Step
1st OEM unlock (successfully)--
Code:
fastboot flashing lock
2nd Flash recovery (successfully)---
Code:
fastboot flash recovery twrp-x.x.x-x-zl1.img
3nd Reboot---
Code:
fastboot reboot
After reboot my phone show a message
Orange State
Your devices has been unlocked and can't be trusted
Your devices will boot in 5 seconds
Click to expand...
Click to collapse
then 25 seconds reboot the phone and show the message again and again.
i believe you have a bootable custom recovery , if yes flash stock or any custom rom available for it via recovery
as i know the command to unlock bootloader is fastboot oem unlock
if recovery isn't booting after booting in to system , try to boot directly in to recovery
shahrior said:
Code:
fastboot flashing lock
Click to expand...
Click to collapse
As far as I know, this is the command used on Nexus devices in order to re-lock the bootloader, whereas the code to unlock it is
Code:
fastboot oem unlock
After this you should reboot your phone (which will be formatted), re-enabling developer options and ADB and then rebooting to fastboot and flash your custom recovery (but first you'd just boot to custom recovery and take a full backup)
After reboot my phone show a message then 25 seconds reboot the phone and show the message again and again.
Click to expand...
Click to collapse
That message is completely normal after unlocking the bootloader, do not try to re-lock it or you could have a red state, and that is bad
But how ? How to boot directly in to recovery ?
Hi All,
I have same problem with my Ulefone Armor 2S. I can't even turn it off... Just rebotting constantly with message:
Orange State
Your devices has been unlocked and can't be trusted
Your devices will boot in 5 seconds
Click to expand...
Click to collapse
when I try to type any fastboot command in cmd then it only shows
<waiting for any device>
Click to expand...
Click to collapse
What can I do??
I've got it
This description come from: https://forum.xda-developers.com/android/development/root-ulefone-armor-2-easy-rooting-t3780055
I changed link to correct ROM
We Need:
SPFlashtool: https://spflashtools.com/windows/sp-flash-tool-v5-1728
Ulefone Armor 2s ROM: https://www.needrom.com/download/ulefone-armor-2s/
The software is quite of auto-explained. Please, Do not use the Ulefone's SPFlashtool, use the one I provided. (I DID NOT CREATE IT)
Shut off your phone
In SPFlashtool set the ''scatter-loading file'' inside the ROM zip, Click ''choose'' and locate it.
Keep it ''Download Only''
Click ''Download'', SPFlashtool will be waiting for your device. (REMEMBER YOU NEED THE DRIVERS I QUOTED ABOVE FOR ALL PROCESSES)
Plug your phone.
Wait until SPFlashtool say it is finished.
After that your phone is brand new.
Bom, estou com o mesmo problema no meu Vernee Apollo, porém a minha situação vai além. Na inicialização ele aparece a mesma mensagem, porém não consigo entrar em modo recovery por que quebrei o botão de volume mais do celular, então tudo que for pra ser feito nele precisa ser feito pelo computador. Fora isso ele reconhece no computador mais não reconhece os drivers então fica com se não estivesse conectado assim não respondendo os comandos do ADB FLASBOOT, alguém por favor consegue me ajudar com o problema.
Well, I have the same problem with my Vernee Apollo, because my situation is going down. At startup it appears the same message, so I can not get into recovery mode because I broke the volume button more than the phone, so everything that is to be done in it needs to be done by computer. Other than that he recognizes on the computer but he does not recognize the drivers so he is not connected so if he does not respond to ADB FLASBOOT commands, somebody can help me with the problem.
me too somebody please help
Please help for orange state
Dear Expert Friends
I was trying to root my Chuwi H9Air Tablet. I did flash with TWRP 3.2.2.0.But TWRP interface do not get any command either touch or buttons
so I can not install Magisk 18.0 to finalize the rooting and device stuck on Orange State not go back or further.
Please Help
Thanks
shahrior said:
I was trying to install LineageOS rom on my Walton Primo GH7.
My Step
1st OEM unlock (successfully)--
Code:
fastboot flashing lock
2nd Flash recovery (successfully)---
Code:
fastboot flash recovery twrp-x.x.x-x-zl1.img
3nd Reboot---
Code:
fastboot reboot
After reboot my phone show a message
after this my phone is not turning on
please help meee
Click to expand...
Click to collapse
adrub said:
I've got it
This description come from: https://forum.xda-developers.com/android/development/root-ulefone-armor-2-easy-rooting-t3780055
I changed link to correct ROM
We Need:
SPFlashtool: https://spflashtools.com/windows/sp-flash-tool-v5-1728
Ulefone Armor 2s ROM: https://www.needrom.com/download/ulefone-armor-2s/
The software is quite of auto-explained. Please, Do not use the Ulefone's SPFlashtool, use the one I provided. (I DID NOT CREATE IT)
Shut off your phone
In SPFlashtool set the ''scatter-loading file'' inside the ROM zip, Click ''choose'' and locate it.
Keep it ''Download Only''
Click ''Download'', SPFlashtool will be waiting for your device. (REMEMBER YOU NEED THE DRIVERS I QUOTED ABOVE FOR ALL PROCESSES)
Plug your phone.
Wait until SPFlashtool say it is finished.
After that your phone is brand new.
Click to expand...
Click to collapse
Yea I tried that but my problem is that the boot screen shows up and when it starts the process everything is fine but my phone won't stay in the boot screen and will reboot after 10 to 15 seconds only to show me the same boot screen with the same result after that.
So to put it simple: I can't do the method because the phone reboots to fast and so the Flash Tool can't make it's job. I would need something that would freeze the screen for example.
Can you Help in any way?
i have same problem
i installed twrp in my micromax q4310
everything goes fine
but when i rebooted my device
it shows a message saying " orange state
your device has been unlocked and can't be trusted
your device will boot in 5 seconds "
and after 5 seconds it reboot again with same message then again and again until my device discharged completely i am not able to go in recovery mode also the fastboot commands not recognising my device
please help
arpitmishraethicalhacker said:
i installed twrp in my micromax q4310
everything goes fine
but when i rebooted my device
it shows a message saying " orange state
your device has been unlocked and can't be trusted
your device will boot in 5 seconds "
and after 5 seconds it reboot again with same message then again and again until my device discharged completely i am not able to go in recovery mode also the fastboot commands not recognising my device
please help
Click to expand...
Click to collapse
I have the same problem. Nobody knows the solution?
O_state not entering recovery
arpitmishraethicalhacker said:
i installed twrp in my micromax q4310
everything goes fine
but when i rebooted my device
it shows a message saying " orange state
your device has been unlocked and can't be trusted
your device will boot in 5 seconds "
and after 5 seconds it reboot again with same message then again and again until my device discharged completely i am not able to go in recovery mode also the fastboot commands not recognising my device
please help
Click to expand...
Click to collapse
I have the same mobile, I used magisk and patched my boot image then used adb to flash it {without any custom recovery)}
Also I unlocked my bootloader then when reboot my phone, orange state error comes but my phone reboots normal and works fine.
I have then wanted to install twrp but my mobile does not let me, every time I go to recovery, it either boots my phone back or if I use adb it does not show my mobile in it.
I will be grateful if any expert can help me install twrp, cwm any custom recovery through which I can install xposed.
Also one thing is that when I use normal bootloader commands, it doesn't work.
But I use....
Fastboot -i 0x2a96 flash ...
Anything
It works , please guide me to fix the orange state or help me install custom recovery.
Also, I tried flashing, it showed success but didn't reboot to recovery, it again rebooted into normal
Waiting for expert advice......
????
My phone:
Micromax Canvas 2 2017 Q4310.
I was a big fan of Android 1 of canvas and I did most of experiments on it so I decided to get it's upgrade.
Anyone please help , also spflash tool doesn't detect my phone and I have latest drivers installed.
I have "Orange state" on a Blackview BV9000Pro-f device.
After unlock bootloader and flash TWRP impossibile the restart in recovery mode.
Can give me somebody, any idea???
Orange State is just a info message for bootloader is unlocked. however, you can remove this message (just cosmetical, this does not fix any problems)
- new: 'Orange State' disabler
if you wanna get rid of the waiting time flash the 'Orange State disabler'
WARNING: experts only! do not try this if you don't know how to unbrick your device
- make a backup of lk.bin (bootloader)
- install orange_state_disabler_v0.3.zip from TWRP
- flash lk.bin from SP Flash Tool (in case you bricked your device)
--- 'Orange State' disabler v0.3 ---
##### Created by XopmoH97 : ) #####
source: orange_state_disabler_v0.3.zip
i have same problem for my unit INFINIX HOT 9 PLAY X680B
Orange State
Your devices has been unlocked and can't be trusted
Your devices will boot in 5 seconds
to clarify: Orange State has nothing to do with. boot-loop must have other causes. most likely dm-verity prevents boot because of flashing modified partition (like TWRP)
in order to disable dm-verity one must generate avb-disabled vbmeta.img from python avbtools
if device doesn't have vbmeta partition one must patch boot.img with Magisk Manager
aIecxs said:
to clarify: Orange State has nothing to do with. boot-loop must have other causes. most likely dm-verity prevents boot because of flashing modified partition (like TWRP)
in order to disable dm-verity one must generate avb-disabled vbmeta.img from python avbtools
if device doesn't have vbmeta partition one must patch boot.img with Magisk Manager
Click to expand...
Click to collapse
Does we really need to generate avb-disabled vbmeta.img from python avbtools?
Flashing stock vbmeta like fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img does not work?
haven't tested but from my understanding the above fastboot flags are for flashing purposes only, in order to allow flashing vbmeta_disabled.img, and not for disabling AVB itself. please correct me if i am wrong
Good night, I have been bricked my device for over 5 days, I was trying to install the Custom ROM pixel experience, but when I installed the TWRP the wifi would stop working and I had the brilliant idea of installing another recovery inside. from TWRP itself and to go further wrong I still unintentionally blocked the bootloader, now I've tried to flash several MiFlash and none successfully, I took it to a technician and he tried a test point and also couldn't make it work, can anyone give a light that I'm already desperate without knowing what else to do
andrenunesnachtigall said:
Good night, I have been bricked my device for over 5 days, I was trying to install the Custom ROM pixel experience, but when I installed the TWRP the wifi would stop working and I had the brilliant idea of installing another recovery inside. from TWRP itself and to go further wrong I still unintentionally blocked the bootloader, now I've tried to flash several MiFlash and none successfully, I took it to a technician and he tried a test point and also couldn't make it work, can anyone give a light that I'm already desperate without knowing what else to do
Click to expand...
Click to collapse
Does it boot? Fastboot modd working? What about recovery mode (i think itsnot working too)?
antoine62 said:
Does it boot? Fastboot modd working? What about recovery mode (i think itsnot working too)?
Click to expand...
Click to collapse
Boot directly into fastboot mode and do nothing else
andrenunesnachtigall said:
Boot directly into fastboot mode and do nothing else
Click to expand...
Click to collapse
Then flash the stock rom?
Edit: You already tryed
What append when you try to unlock the bl ?
Do the other slot can boot?
antoine62 said:
Then flash the stock rom?
Edit: You already tryed
What append when you try to unlock the bl ?
Do the other slot can boot?
Click to expand...
Click to collapse
I can't change the command line slots, but now I have a person in my city who can fix via TeamViewer a person who has an authorized Xiaomi account, I hope it works.
Help me!!!
andrenunesnachtigall said:
I can't change the command line slots, but now I have a person in my city who can fix via TeamViewer a person who has an authorized Xiaomi account, I hope it works.
Click to expand...
Click to collapse
Hi Bro, could they help you with the phone unlock? the same thing happened to me and if they could help you I need you to help me, I've been trying to fix my phone for more than 1 month ?
The same thing has happened to me for a few weeks and I don't know what to do, and try everything, could you shed some light?
IvanKRATOS said:
Hi Bro, could they help you with the phone unlock? the same thing happened to me and if they could help you I need you to help me, I've been trying to fix my phone for more than 1 month
Click to expand...
Click to collapse
Bro, You can unbrick your device by flashing. First you need to remove back shell of your device then you need to flash your device in EDL MODE (EDL = Emergency Download ) . If you want help you can meassage me . i will provice you with Flash file & Instructions
I also brick my phone, what i did was unlock the bootloader again, connect to miflash, flash the stock rom, wait like 10 minutes, and force the reboot on reboot went again to fastboot, on the folder plataform tools of adb, go to cmd, and write "fastboot set_active a" , force the reboot again (pushing the power on/off button like 20 secs) and it boot
tecatelt said:
I also brick my phone, what i did was unlock the bootloader again, connect to miflash, flash the stock rom, wait like 10 minutes, and force the reboot on reboot went again to fastboot, on the folder plataform tools of adb, go to cmd, and write "fastboot set_active a" , force the reboot again (pushing the power on/off button like 20 secs) and it boot
Click to expand...
Click to collapse
Bro. you can unbrick your device by using EDL method. you can search it on google
I have bricked my phone 2 months ago, and even xiaomi repair center said there's nothing they can do. I have the same situation with OP, it keeps rebooting to fastboot mode, and EDL flashing does NOT work for me. The repair center said that the only hope of the phone is getting the full motherboard assembly replaced.
Live.
https://youtu.be/4FzAayrllsY
Did you try erase and flash via qfil + edl. The IMEI/Mac addresses and efs data needs to be re written but I think it will fix ur brick atleast. From wat I understood u have locked the bootloader back after flashing a custom rom. Secure boot will not allow the custom rom's to boot with bootloader locked coz the signatures do not match the phone's factory signature burned into the phone's bootloader.
This could help u understand:
https://source.android.com/security/verifiedboot/boot-flow
Note: each time u flash the phone via qfil or edl in general restart the phone in edl mode, qcom phones are allowed to be flashed via edl mode only for the first try after putting the phone in edl mode, the second and the following times u try u will get a Sahara fail error.
Sapper Morton said:
For now it's better to avoid locking the bootloader, since Fastboot is the only flashing auth free method.
Click to expand...
Click to collapse
How does the boot loader get locked? I'd like to know so I don't inadvertently do it.
pode me ajudar ? estou com o meu mi a3 brickado e já flashei varias vezes mais quando vai inicializar aparece a tela erasing depois do android one e já desliga e volta pra tela de fastboot.
MOD EDIT: Please post only in English according to the FORUM RULES,translation added below:
Can you help me? I'm with my mi a3 brickado and já Flashei several times more when it will boot appears the erasing screen after android one and já turns off and back to fastboot screen.
barth2 said:
How does the boot loader get locked? I'd like to know so I don't inadvertently do it.
Click to expand...
Click to collapse
It is highly recommended to lock the bootloader by flashing fastboot rom via MiFlash, as it has basically no chance of getting bootloop caused by any unauthorized modifications, just remember to set active slot to a before flashing to prevent any problems.
Plaese help me.
I can't get stock android booting. Flashed via MiFlash. Always back to fastboot.
Can anybody help me with that please?
gborfitz said:
Plaese help me.
I can't get stock android booting. Flashed via MiFlash. Always back to fastboot.
Can anybody help me with that please?
Click to expand...
Click to collapse
Does the flashing procedure success? What does the MiFlash says when finished flashing?
Try switching to active slot to a before flashing.
MarcusMario0605 said:
Does the flashing procedure success? What does the MiFlash says when finished flashing?
Try switching to active slot to a before flashing.
Click to expand...
Click to collapse
Miflash gave me a success message. Finally got stock booted changing active slot to a and flashing again.
Thank you very much for your reply!
gborfitz said:
Miflash gave me a success message. Finally got stock booted changing active slot to a and flashing again.
Thank you very much for your reply!
Click to expand...
Click to collapse
I have a same problem here... But i can't change my active slot to "a"... Please help! Thank you!