Related
I tried in every possible way to root, unlock the boot loader, with pc and without it, but every time i try to do something on my zenfone 5 it enter in csc mode instead of droidboot and I can't understand why, can someone help me?
My asus zenfone 5:
Lollipop 5.0
ASUS_T00P
M3.5.23-A500KL_10137
Build number: LRX21M.WW_Phone-12-4-5-58-20151013044030443_201501281349
kernel: 3.4.0-gfaefa92
http://dlcdnet.asus.com/pub/ASUS/ZenFone/A500KL/0530-1020_SIGNED_UnLock.zip
Unlocker for bootloader, this is made for kitkat but I tried it for lollipop and it worked, just check your screen when your phone restarts, you should see somelines there saying
Tampered = No
Authorized = No
Unlocked = Yes
for rooting, try downloading Kingroot on your phone.
Rikkuzen193 said:
Unlocker for bootloader, this is made for kitkat but I tried it for lollipop and it worked, just check your screen when your phone restarts, you should see somelines there saying
Tampered = No
Authorized = No
Unlocked = Yes
for rooting, try downloading Kingroot on your phone.
Click to expand...
Click to collapse
I have the same issue. In fact my phone is showing ERROR: invalid boot image and I can not access droidboot /bootloader or even recovery. I am newbee. please help.
Deleted
Droidboot: ZenFone 5 (A500CG / A501CG)
CSC: ZenFone 5 LTE (A500KL)
ERROR: invalid boot image csc mode ONLY
DIXIES or any expert who can HELP!!!
i have asus a500KL zenfone 5 tried software update after reboot got ERROR: invalid boot image
i am fairly experienced with root access, custom roms and have been trying to fix this issue for a few days.
I am able to get to csc mode, also powering off and entering BLUE SCREEN csc mode.
I have tried ALL the flash asus tools and everything. tried a few intels but they dont even begin to work as mine is an ARM.
fastboot recognises csc mode!!!
I can flash a boot.img but that is it, does not change the situation.
Everything else gets an error, something like ERROR: Security prevents this action or something about it being locked. I think it might mean the bootloader is locked and cant access anything pretty much.
I have tried every key combination under the sun. (Timing, P + (+), P + (-), P + (+ & -), in all combos and timing combos.
Power + Vol Down gets me to the SD Update option.
CLick the top to continue and the bottom to reboot.
I have tried both and they both take me to the ERROR: invalid boot image
im stumped.
Ive Messed with HTC, Samsungs, Sony, Huawei for gods sake, even iphones and have never come across an issue like this that is so impossible to fix. I think i may have hit my first brick.
Any help will be greatly appreciated.
Regards
jaza-g said:
I can flash a boot.img but that is it, does not change the situation.
Everything else gets an error, something like ERROR: Security prevents this action or something about it being locked. I think it might mean the bootloader is locked and cant access anything pretty much.
Click to expand...
Click to collapse
Did you flash boot.img in csc mode successfully (no error message on PC)?
If yes, and it is still stuck at invalid kernel screen, your A500KL may be broken.
DIXES said:
Did you flash boot.img in csc mode successfully (no error message on PC)?
If yes, and it is still stuck at invalid kernel screen, your A500KL may be broken.
Click to expand...
Click to collapse
Thats right. The boot.img was the only file I was able to flash in csc mode without error or failure, still unsuccessful in booting. All the issues are still the same. Is there any way of fixing this? If my bootloader was unlocked I think I would be able to restore it however am unable to unlock through csc mode I think!!! Every time I try and unlock bootloader it tries to boot the phone into recovery which it doesnt have and cant flash one with an unlocked bootloader I believe. Please help! Is this a brick/paper weight??
jaza-g said:
Thats right. The boot.img was the only file I was able to flash in csc mode without error or failure, still unsuccessful in booting. All the issues are still the same. Is there any way of fixing this? If my bootloader was unlocked I think I would be able to restore it however am unable to unlock through csc mode I think!!! Every time I try and unlock bootloader it tries to boot the phone into recovery which it doesnt have and cant flash one with an unlocked bootloader I believe. Please help! Is this a brick/paper weight??
Click to expand...
Click to collapse
There isn't unofficial bootloader unlock method for A500KL currently.
You have to unlock it with Unlock Device App from ASUS under system.
I can't help because I don't have A500KL, sorry.
DIXES said:
There isn't unofficial bootloader unlock method for A500KL currently.
You have to unlock it with Unlock Device App from ASUS under system.
I can't help because I don't have A500KL, sorry.
Click to expand...
Click to collapse
unlock device app is an ufficial relase from asus, but it invalide the garancy. And it is an apk file, so unuseful for bootload problems or bootload with flash locked...
so?...what we have 2 do for enable the flashing?
ManuelIvanov said:
I tried in every possible way to root, unlock the boot loader, with pc and without it, but every time i try to do something on my zenfone 5 it enter in csc mode instead of droidboot and I can't understand why, can someone help me?
My asus zenfone 5:
Lollipop 5.0
ASUS_T00P
M3.5.23-A500KL_10137
Build number: LRX21M.WW_Phone-12-4-5-58-20151013044030443_201501281349
kernel: 3.4.0-gfaefa92
Click to expand...
Click to collapse
im also facing with csc mode. i trying to find solution from all forums and seems no solution yet for csc mode. im so frustrating. If someone have solution please let me know :crying::crying::crying:
DIXES said:
Did you flash boot.img in csc mode successfully (no error message on PC)?
If yes, and it is still stuck at invalid kernel screen, your A500KL may be broken.
Click to expand...
Click to collapse
ManuelIvanov said:
I tried in every possible way to root, unlock the boot loader, with pc and without it, but every time i try to do something on my zenfone 5 it enter in csc mode instead of droidboot and I can't understand why, can someone help me?
My asus zenfone 5:
Lollipop 5.0
ASUS_T00P
M3.5.23-A500KL_10137
Build number: LRX21M.WW_Phone-12-4-5-58-20151013044030443_201501281349
kernel: 3.4.0-gfaefa92
Click to expand...
Click to collapse
Contact Me, if you want that's solution :
fb : Abip Maulanaa
Gm: [email protected]
line : abipmaulana
Haven't rooted a phone in a little but am generally pretty savvy. I can get into recovery, tried restoring factory settings and clearing cache, same result unfortunately. I tried running an Odin .exe I found in another thread but it just opens and closes.. :/
When in download mode, product name: SMN900V, System Status: Custom
Knox Kernel Lock: 0x0, Knox Warranty Void: 0x0, Qualcomm Secureboot: Enable (CSB), RP SWREV: S1, T1, A3, P1
Write Protection: Enable, UDC START
Any help anyone can offer or provide a working rom or flashable file to get me booted would be most appreciated! No idea what ROM or Android version he put on this thing (purchased from Swappa).
TIA!!
Re download Odin and tar file. Have you gotten Odin to flash anything or does it fail or do you mean Odin itself isn't working? It sounds like you didn't extract Odin files and just opened it.
Sent from my SM-N900V using XDA-Developers mobile app
I was able to flash a Verizon firmware (thru Odin) and get it booted but I don't have root (seller claimed he did beforehand). Sounds like I should start with unlocking bootloader or root first? Thanks for the response man, I appreciate all the help I can get!
Sent from my SM-N900V using XDA-Developers mobile app
Start with the root first. Can't unlock the bootloader without it.
Awesome is there a one click by chance or is it complicated?
Sent from my SM-N900V using XDA-Developers mobile app
DNak206 said:
Awesome is there a one click by chance or is it complicated?
Sent from my SM-N900V using XDA-Developers mobile app
Click to expand...
Click to collapse
I had installed jasmine rom and ended up having problems with certain apps not working due to the modified framework he was using. I used odin to flash the new OB6 & pit (returns to locked boot loader with stock lollipop rom). I took the OTA to OF1, then used the yemen 1 click root. At this point the only issue I have is trying to get a customer bootloader installed. The TWRP version 3.0.2-0 just leaves me stuck at boot loader and I had to reinstall the pit file to get phone to boot again. Hope that helps you. I like stock rom but am trying to get native tether to work, without customer bootloader I can't flash anything.
I just got note3 Verizon, I rooted it couple days ago. I am on tmobile, so far everything works with stock lollipop except hotspot. Contemplating on unlocking boot loader at the moment.
santas16 said:
I had installed jasmine rom and ended up having problems with certain apps not working due to the modified framework he was using. I used odin to flash the new OB6 & pit (returns to locked boot loader with stock lollipop rom). I took the OTA to OF1, then used the yemen 1 click root. At this point the only issue I have is trying to get a customer bootloader installed. The TWRP version 3.0.2-0 just leaves me stuck at boot loader and I had to reinstall the pit file to get phone to boot again. Hope that helps you. I like stock rom but am trying to get native tether to work, without customer bootloader I can't flash anything.
Click to expand...
Click to collapse
[threadjack]
I was fooling around with flashing custom recoveries from within a rooted ROM today, and found something useful - when I "got stuck at bootloader" because TWRP failed to boot. So long as the main ROM is still bootable and is rooted, you can clear the "always tries to boot the recovery" behavior the following way:
1) Pull the battery (and plug back in after a couple seconds)
2) Vol-Down+Home+Power (as if you are trying to enter Download mode)
3) When you get the Custom ROM Warning menu, choose Cancel (not Continue)
This clears the BCB (Boot Communication Block) in eMMC and the phone will thereafter attempt to boot normally, rather than continuing to try to boot the recovery again. The sequence #2-3 does not work if you don't start by pulling the battery - if you soft-boot by holding the Power button down (~ 15 seconds), the phone will always attempt to boot the (broken) recovery, whether you enter Odin mode or Cancel.
Well, that's the way my phone behaves at this moment. (I am using a older bootloader however - it is always possible that this is a bootloader behavior that changed in later versions). Anyway - if you get "stuck" again, this could save you some labor, rather than having to go back to Odin, flash everything, and re-root.
Having said that, I'm not sure what you would use as alternative custom recovery. You could do something like pull just the stock kernel from the OF1 and re-pack it into your own customization of TWRP to see if that changes anything. Thing is, I could have sworn I saw a report from someone who said they are using TWRP 3.0.2 with the OF1 bootloader successfully.
Are you using "twrp-3.0.2-0-hlte.img" ?
[/threadjack]
bftb0 said:
[threadjack]
I was fooling around with flashing custom recoveries from within a rooted ROM today, and found something useful - when I "got stuck at bootloader" because TWRP failed to boot. So long as the main ROM is still bootable and is rooted, you can clear the "always tries to boot the recovery" behavior the following way:
1) Pull the battery (and plug back in after a couple seconds)
2) Vol-Down+Home+Power (as if you are trying to enter Download mode)
3) When you get the Custom ROM Warning menu, choose Cancel (not Continue)
This clears the BCB (Boot Communication Block) in eMMC and the phone will thereafter attempt to boot normally, rather than continuing to try to boot the recovery again. The sequence #2-3 does not work if you don't start by pulling the battery - if you soft-boot by holding the Power button down (~ 15 seconds), the phone will always attempt to boot the (broken) recovery, whether you enter Odin mode or Cancel.
Well, that's the way my phone behaves at this moment. (I am using a older bootloader however - it is always possible that this is a bootloader behavior that changed in later versions). Anyway - if you get "stuck" again, this could save you some labor, rather than having to go back to Odin, flash everything, and re-root.
Having said that, I'm not sure what you would use as alternative custom recovery. You could do something like pull just the stock kernel from the OF1 and re-pack it into your own customization of TWRP to see if that changes anything. Thing is, I could have sworn I saw a report from someone who said they are using TWRP 3.0.2 with the OF1 bootloader successfully.
Are you using "twrp-3.0.2-0-hlte.img" ?
[/threadjack]
Click to expand...
Click to collapse
I get a different kind of stuck, I'm not going to try it again but it said the phone has detected software that is not authorized or something along those lines. I cannot just pull battery as it just repeats over and over. I actually do not ever get to enter any recoveries at all, it automatically detects that's it's not the original bootloader and tells me such. anyways, I had to reload the image and take the OF1 update again... all is working back to normal.
I had used "twrp-3.0.2-0-hltevzw-4.4.img" from the twrp manager app, flashed via app, restarted to end up having the error message immediately on bootup of device... no recoveries or anything could load. I would have to assume the 4.4 means kk version and that's why it didn't work?
santas16 said:
I had installed jasmine rom and ended up having problems with certain apps not working due to the modified framework he was using. I used odin to flash the new OB6 & pit (returns to locked boot loader with stock lollipop rom). I took the OTA to OF1, then used the yemen 1 click root. At this point the only issue I have is trying to get a customer bootloader installed. The TWRP version 3.0.2-0 just leaves me stuck at boot loader and I had to reinstall the pit file to get phone to boot again. Hope that helps you. I like stock rom but am trying to get native tether to work, without customer bootloader I can't flash anything.
Click to expand...
Click to collapse
Hmmm. Maybe I was reading something into your post that wasn't there. I assumed that you had also performed the retail-to-dev edition CID change "unlock" after you gained root on OF1. Is that wrong - did you simply flash a recovery after getting root?
In my case I flashed a non-bootable TWRP (dd of=/dev/block/mmcblk0p15...) onto the recovery; doing this tripped my Knox Warranty flag, but otherwise the bootloader didn't complain about unauthorized software. After figuring out how to clear the "always try to boot the recovery" near-disaster, I used a 2.8.x TWRP series custom recovery successfully (In addition to flashing the stock recovery back into place and verifying that it still worked) But this is on a truly ancient bootloader (MJ7), so maybe all bets are off about expecting later bootloaders to behave in this same fashion.
Still, the point of developer edition functionality is to allow for custom boot (& recovery) partitions, so it's surprising that you were getting warnings like that if your phone was in developer mode.
@santas16
Hey. For what it's worth, I was able to boot twrp-3.0.2-hltevzw-4.3.img from my SM-N900V ... with a MJ7 bootloader!
But not the hltevzw-4.4.img. (That could be due to the old bootloader however, I don't know for sure)
Note that my phone has the retail-to-deved CID change that puts it into developer mode. (I used @donc113 's executable with adb)
This allows unsigned boot or recovery partitions to proceed to load/execute, but it will burn your Knox Warranty flag (which is unimportant to me at this point). I think that is actually the expected behavior when the phone is in developer mode.
I've been flashing all sorts of recoveries without worrying whether they will boot or not (as I know I can get back into the rooted ROM to flash into place a working version)**
Probably the best advice about not getting stuck in the "continually tries to re-enter the recovery" mode is to NOT use "reboot to recovery" methods (in Safestrap, other recoveries, or root-privileged Apps (flashfire?)), but to always shut the phone down to a powered-off state, and just use the three-button startup method (Vol-Up+Home+Power) to enter the recovery. That way nothing is being written into the BCB that will make it want to loop back to a failed recovery.
cheers
** what was interesting is that I could successfully boot any of the MI9, MJ7, MJE stock recoveries on my MJ7 phone. Moreover, the bootloader would not pop up the yellow "Set Warranty Bit: recovery" message right before they loaded. The NC4 recovery would not boot to a menu, but it also did not present a "Set Warranty Bit: recovery" message. I presume this means that the boot layer is not looking for exact version matches, but rather just checking that the Samsung signing operation is correct. I could not boot OB6 or OF1 recoveries; somewhat curiously though, these attempts *would* throw the "Set Warranty Bit: recovery" error message even though they are validly signed Samsung recoveries. I don't know if it is a reasonable hypothesis, but I think that indicates that Samsung may have altered the details of their signing verification method someplace between NC4 and OB6 so that earlier bootloaders fail this check. Ugh. As if there weren't enough details already.
If your bootloader is still 0F1 then download flashify from Google and hit recovery and tap top twrp.. Your all set...sounds like a lot of craziness for nothing.
Sent from my SM-N900V using XDA-Developers mobile app
santas16 said:
I get a different kind of stuck, I'm not going to try it again but it said the phone has detected software that is not authorized or something along those lines. I cannot just pull battery as it just repeats over and over. I actually do not ever get to enter any recoveries at all, it automatically detects that's it's not the original bootloader and tells me such. anyways, I had to reload the image and take the OF1 update again... all is working back to normal.
I had used "twrp-3.0.2-0-hltevzw-4.4.img" from the twrp manager app, flashed via app, restarted to end up having the error message immediately on bootup of device... no recoveries or anything could load. I would have to assume the 4.4 means kk version and that's why it didn't work?
Click to expand...
Click to collapse
If you get the " not authorized or something along those lines" error, it means you're not unlocked.
If i modify the system partition, the recovery greets me with "dm-verity verification failed".
I do *not* get the message about the DRK being invalid. My phone works fine.
Is there a way to remove this cosmetic error?
sins07 said:
If i modify the system partition, the recovery greets me with "dm-verity verification failed".
I do *not* get the message about the DRK being invalid. My phone works fine.
Is there a way to remove this cosmetic error?
Click to expand...
Click to collapse
No promises...
http://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516
I suppose that will work but i want my system partition modified/themed the way it is
I've heard it has something to do with the efs partition inside /efs/prov_data/dmvt or /efs/prov_data/dev_root
Maybe i can recalculate the hash value for the system partition and inject it somewhere?
My DRK is fine. just wish to remove recovery error.
i'm on stock recovery and my unit will always boot because I have the G930P eng kernel with dm-verity disabled. Stock recovery still thinks dm-verity is enabled because it just says "dm-verity verification failed" which is normal when you modify the system partition. I'm only trying to figure out how to remove the dm-verity verification failed error.
i can do such repair remotely
I have a galaxy s7 and rooted my device and some security update, updated my phone now I'm stuck in a bootloop.
I have tried Samsung smart switch and it wont take my model name. What do I do next?
kenny08vt said:
I have a galaxy s7 and rooted my device and some security update, updated my phone now I'm stuck in a bootloop.
I have tried Samsung smart switch and it wont take my model name. What do I do next?
Click to expand...
Click to collapse
Go to recovery mode. factory reset. should boot now.
Hello, Is there any update about how to fix?
Any way to fool your kernel/recovery into thinking dm-verity is just fine?
Samsung s7 says dm-verify verification failed after been reset
[HELP] Trying to transfer my rig, now I get a "Verification Failed" message on boot!
This is urgent! Please help1
I tried to transfer my phone's rig to another of the same phone. A guide here said to use TWRP's backup feature. I failed at doing the Odin flash the first couple times and accidentally booted into the system. I got a "Verification Failed" screen, with the only options being factory reset, and power off/restart. I figured this would go away once I flashed TWRP right, so I did, did that backup, but I noticed the backup was only ~4GB. I tried to mount the Data partition, but it reports 0B and won't mount. Every time I boot I get the same screen. I don't know what to do and I have no phone... and I need my data.. Please help!!! EDIT I also can't access TWRP anymore, and the normal recovery says "successfully verify for dmverity hash tree"
SM-G935W8
EDIT EDIT: I managed to boot using the standard recovery's reboot option... But I don't want this to happen again. Is there an easy way?
Hello guys,
I'm locked out of my phone, I don't have a backup and I have very important files on this device, so I'll try whatever possible to try to access the files again, I know it's probably hard but I wanted to try asking in a post.
I don't have Root, I have Secure Boot enabled and OEM Unlock disabled.
I can unlock the secure boot when the phone starts without issues, it unlocks and sometimes boots up on the lockscreen, when it does it freezes for 2 to 5 seconds (so can't unlock with pin) and then goes back to the secure boot animation and it starts all over.
The cause that I suspect is software update, (Patch 2nd Jan '19 - CSC: OMN - Italy) OTA successfully updated the phone this morning and after 10/15h of use suddently rebooted (secure boot animation) and never booted again. Right before this happened I have downloaded an app from the Play Store called "Galaxy Button Lights 2" and I have also set a swipe pattern for lockscreen (that it's now required for secure boot as well), between these last two actions all this started to happen.
Another hypotesis is Secure Folder (It had given me problems freezing lately).
What I did try is:
Booting in safe mode
Wiping Cache
Reflashing the previous firmware via Odin (Patch Dec 2018)
I'll be trying to enable ADB taking this guide in consideration
Is there anyway that I could try to access the files again? Trying an older Firmware?
Is there a way to view error log and to disable the Galaxy Button app via ADB?
It might be possible trying installing TWRP, ROM or rooting?
Would I loose files by rooting or Installing TWRP/CWM?
ADB could help me, somehow, in pulling the files out?
How can I delete /data partition (without root)? Having the phone encrypted, flashing a ROM or deleting the /data partition would make me permanently loose access to my Internal Storage? Please, any help would be greatly appreciated.
anyone?
Anyone has a workaround to access the files? (Maybe dumping the images of /Data & other partitons? Phone encrypted...)
I don't mind tampering Knox, rooting or interfering (somehow) with SBoot, as long as I recover the files!