Device:
Prime xt1625-ss g4 BL unlocked with 7.0 amz NPJS25.93-14-4 march update.
Error:
Flashed 7.0 ret NPJS25.93-14-4-8 update and bricked it "Unauthorized SW".
Temp Fix:
Flashed it with RSD with the bootloader.img and gpt.bin from 8 and everything else from 4 , it boots and works.
Observations:
Unlock Warning screen "ID: bad key" why?
Questions:
1. Any OTA update will brick it again? **UPDATE** OTA'd to NPJS25.93-14-4-5 Lock Ads returned, boots and functions. **
2. What other firmwares can be flashed besides amz specific?
3. Can it be downgraded to the -4 version since the bootloader is from the -8 ret version, no way out if it bricks?
Thanks in advance
CHownclown said:
Error:
Flashed 7.0 ret NPJS25.93-14-4-8 update and bricked it "Unauthorized SW".
Temp Fix:
Flashed it with RSD with the bootloader.img and gpt.bin from 8 and everything else from 4 , it boots and works.
Click to expand...
Click to collapse
What do you mean with yout temp fix, i have the same problem the phone says "Unauthorized SW" with each Official ROM. Im using LOS 14.1 but sometimes the phone heats up (Charging and when i am playing some game like Clash Royale)
Can you post a step by step guide? plz.
xtir82 said:
What do you mean with yout temp fix, i have the same problem the phone says "Unauthorized SW" with each Official ROM. Im using LOS 14.1 but sometimes the phone heats up (Charging and when i am playing some game like Clash Royale)
Can you post a step by step guide? plz.
Click to expand...
Click to collapse
Are you running an Amazon Prime Ad Offer xt1625-ss?
I meant temp fix as it wouldn't boot.
It would start into recovery with the "An attempt to flash Unauthorized Software has been detected contact customer service" notification and will not boot. By mixing the newer bootloader with the older image it booted. This is a temporary fix and potentially unstable as all get out, historically a OTA update bricks the device yet again. In this instance an OTA did NOT brick the device and it functions fine with ads returning.
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
After Nougat OTA Update Moto x Play while restarting device says Warning Bootloader Unlocked.
Help to get Stock Logo for this issue.
bharattony said:
After Nougat OTA Update Moto x Play while restarting device says Warning Bootloader Unlocked.
Help to get Stock Logo for this issue.
Click to expand...
Click to collapse
Extract the boot logo from zip and flash via fastboot.
You can successful to update official it's in unlocked bootloader I am getting error in middle of installation I also unlocked bootloader
nitingarje24 said:
You can successful to update official it's in unlocked bootloader I am getting error in middle of installation I also unlocked bootloader
Click to expand...
Click to collapse
He mean to say he want a inlock warning disabled boot logo
Urgent help needed as I'm leaving the country at the end of the week o any help is appreciated!
Just successfully rooted my device:
Black, Unlocked, PRA-LX1, UK, Dual SIM
After doing so successfully, I attempted to flash LineageOS from the following link:
https://forum.xda-developers.com/p8lite/p8-lite-2017-development/rom-lineageos-15-1-hi6250-devices-t3811583
Although when I completed Step 6 on the Installation guide and rebooted the phone, I started seeing the message:
------------------
ERROR MODE
Attention!
Please update system again
(Green Android picture)
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
------------------
Despite this, I didn't receive a box with my phone due to being second hand, and I didn't see the model number on the receipt as it was from a reselling store. I didn't remember to note down the specific model number
It'd be extremely helpful if someone could possibly help just from the device description above as I'm not sure if it's safe for me to just attempt to flash every stock rom for every other LX1 device out there.
---------------------------------------------------------------
Update:
To restore this, I connected via fastboot with a working USB & flashed an original stock recovery in the video found here
(Just in case their download link ever goes down, I have uploaded the same copy to my MEGA, found here)
The recovery installed fine when using the command
fastboot flash recovery oeminfo.img
Click to expand...
Click to collapse
Whenever trying to flash any other recovery such as twrp before this fastboot stuck on a loading icon.
The stock recovery seems to be downloading the original firmware, too.
PRA-LX1C432B202 is presumably the model.
Both the bootloader and FRA were unlocked when everything else was inaccessible.
Looks like the custom ROM's recovery that you've flashed is not compatible with PRA-LX1. Try to flash stock recovery. If not working, then flash stock firmware.
Thanks @Botar230!
I didn't see your comment until just now after deciding to edit this post since I've gotten a step closer to restoring my device.
Your solution was the method I used although I didn't know my phone model, so I found a random solution which just worked for my device, and the eRecovery seems to be downloading the stock firmware anyways. Thanks again
Before flashing this lineage os you should update to EMUI8 to get treble support, i suppose you was running EMUI5, hence the error mode.
My device was using Oxygen OS Pie official version OTA 43 and the I got the notification for OTA 46 update.
Having an unlocked bootloader and TWRP codeworkx recovery 3.2.3-0, I removed the compatiblity.zip from the OTA, like the other times I did, and tried to flash it, which resulted into a failure. But after rebooting to bootloader and flashing the original oneplus recovery image, I tried to flash the zip again. Which also failed. I have no root, or modifications done to the system. However upon reboot I got the unlocked bootloader warning but nothing else showed up. I couldn't access the recovery nor the bootloader. Fastboot or ADB was unable to detect any device. So I was stuck with a Hard Brick.
After that I downloaded cheeseburger_23_O.13_170803 MsmDownloadTool 4.0 from the unbrick thread and followed the instructions. It completed successfully and I have stock Oneplus 5 on Oxygen OS 4.5.8 and Android 7.1.1 however system update was available to Oxygen OS 5.1.4 and I tried to install it, which failed. I unlocked the bootloader, installed twrp official 3.2.3 and tried again, which also failed with E3005: exit code 7
I tried flashing codeworkx recovery but it results into a black screen at the recovery and a continuous blue light at the LED — like when it was when Hard bricked. I don't understand what to do anymore. Also Bootloader has changed:
Product Name: QC_reference_Phone
Variant : MSM UFS
Bootloader Version: (it is blank)
Baseband Version: (also blank)
Serial Number: (present, same as what it used to be)
Secure Boot: yes
Device State : Unlocked
Did I miss something while Unbricking?
EDIT:
I don't know if something was wrong with my bootloader or unbricking, but I fixed the issue by using an updated version of unbrick tool from: Here
Some information is till missing from the bootloader screen ie. baseband version and bootloader version, but I could update to latest OTA at least.
Kj1594 said:
My device was using Oxygen OS Pie official version OTA 43 and the I got the notification for OTA 46 update.
Having an unlocked bootloader and TWRP codeworkx recovery 3.2.3-0, I removed the compatiblity.zip from the OTA, like the other times I did, and tried to flash it, which resulted into a failure. But after rebooting to bootloader and flashing the original oneplus recovery image, I tried to flash the zip again. Which also failed. I have no root, or modifications done to the system. However upon reboot I got the unlocked bootloader warning but nothing else showed up. I couldn't access the recovery nor the bootloader. Fastboot or ADB was unable to detect any device. So I was stuck with a Hard Brick.
After that I downloaded cheeseburger_23_O.13_170803 MsmDownloadTool 4.0 from the unbrick thread and followed the instructions. It completed successfully and I have stock Oneplus 5 on Oxygen OS 4.5.8 and Android 7.1.1 however system update was available to Oxygen OS 5.1.4 and I tried to install it, which failed. I unlocked the bootloader, installed twrp official 3.2.3 and tried again, which also failed with E3005: exit code 7
I tried flashing codeworkx recovery but it results into a black screen at the recovery and a continuous blue light at the LED — like when it was when Hard bricked. I don't understand what to do anymore. Also Bootloader has changed:
Product Name: QC_reference_Phone
Variant : MSM UFS
Bootloader Version: (it is blank)
Baseband Version: (also blank)
Serial Number: (present, same as what it used to be)
Secure Boot: yes
Device State : Unlocked
Did I miss something while Unbricking?
EDIT:
I don't know if something was wrong with my bootloader or unbricking, but I fixed the issue by using an updated version of unbrick tool from: Here
Some information is till missing from the bootloader screen ie. baseband version and bootloader version, but I could update to latest OTA at least.
Click to expand...
Click to collapse
try a different recovery like "Oreo" and if doesn't help then use unbrick tool
Himanshu.Shukla said:
try a different recovery like "Oreo" and if doesn't help then use unbrick tool
Click to expand...
Click to collapse
I did try to install codeworkx twrp recovery, for the Oreo build but it was giving me a hard brick, ie. A black screen and a blue LED when trying to boot to recovery. But as I said, using Unbrick tool v4.0.8 I was able to restore to Oxygen Os 5.1.7 and then everything worked fine.
I am just unsure why it didn't work with Oxygen Os 4.5.8
I mean, with a locked bootloader and a freshly installed OS, you should be able to get OTA updates, right? But the system update was failing. So maybe there was something wrong with the partitions? I don't know. The bootloader in the older Unbrick tool was different than stock. Maybe that was a fault, well, I'll never know. But all I'm saying is, newer Unbrick Tool worked wonders for me.
I believe we all know here how hard flashing Nokia 6 phones are... they are unbelievably a PITA.
I have a TA-1025 Nokia 6, 7.1.1 Nougat. I have been trying to fix it for 3 days now with no success. Originally tried to reflash stock boot image at first with little success so I could flash Magisk. Ended up wiping out entire System partition and trying to reflash, getting nowhere. I then flashed a B02_Homebrew.zip which ended up with stock recovery and no root at all (and no ability to flash magisk despite having unlocked bootloader. great.) Downgraded bootloader again and am now stuck and unsure how to proceed.
Note I CANNOT get QFil to work without EDL mode, which requires me to tear my phone apart.
Any suggestions? Does anyone have any certified knowledge of how to fix and reflash stock Nokia 6? I don't want to take it to a dealer because they will update it and make it unrootable (and probably won't be able to even touch it since bootloader is unlocked.)
ATM, all I can boot to is TWRP recovery or Download Mode.
Help?
Dantheman221 said:
I believe we all know here how hard flashing Nokia 6 phones are... they are unbelievably a PITA.
I have a TA-1025 Nokia 6, 7.1.1 Nougat. I have been trying to fix it for 3 days now with no success. Originally tried to reflash stock boot image at first with little success so I could flash Magisk. Ended up wiping out entire System partition and trying to reflash, getting nowhere. I then flashed a B02_Homebrew.zip which ended up with stock recovery and no root at all (and no ability to flash magisk despite having unlocked bootloader. great.) Downgraded bootloader again and am now stuck and unsure how to proceed.
Note I CANNOT get QFil to work without EDL mode, which requires me to tear my phone apart.
Any suggestions? Does anyone have any certified knowledge of how to fix and reflash stock Nokia 6? I don't want to take it to a dealer because they will update it and make it unrootable (and probably won't be able to even touch it since bootloader is unlocked.)
ATM, all I can boot to is TWRP recovery or Download Mode.
Help?
Click to expand...
Click to collapse
just download the Full OTA update in the thread section.
must downgrade first ur recovery to nougat then install update via recovery.
You can use TA-1021.
If you want Nougat Ver. then use Nokia OST.
Dantheman221 said:
I believe we all know here how hard flashing Nokia 6 phones are... they are unbelievably a PITA.
I have a TA-1025 Nokia 6, 7.1.1 Nougat. I have been trying to fix it for 3 days now with no success. Originally tried to reflash stock boot image at first with little success so I could flash Magisk. Ended up wiping out entire System partition and trying to reflash, getting nowhere. I then flashed a B02_Homebrew.zip which ended up with stock recovery and no root at all (and no ability to flash magisk despite having unlocked bootloader. great.) Downgraded bootloader again and am now stuck and unsure how to proceed.
Note I CANNOT get QFil to work without EDL mode, which requires me to tear my phone apart.
Any suggestions? Does anyone have any certified knowledge of how to fix and reflash stock Nokia 6? I don't want to take it to a dealer because they will update it and make it unrootable (and probably won't be able to even touch it since bootloader is unlocked.)
ATM, all I can boot to is TWRP recovery or Download Mode.
Help?
Click to expand...
Click to collapse
my Nokia 6 phone is also bricked. Please share if you find a solution.
Dantheman221 said:
I believe we all know here how hard flashing Nokia 6 phones are... they are unbelievably a PITA.
I have a TA-1025 Nokia 6, 7.1.1 Nougat. I have been trying to fix it for 3 days now with no success. Originally tried to reflash stock boot image at first with little success so I could flash Magisk. Ended up wiping out entire System partition and trying to reflash, getting nowhere. I then flashed a B02_Homebrew.zip which ended up with stock recovery and no root at all (and no ability to flash magisk despite having unlocked bootloader. great.) Downgraded bootloader again and am now stuck and unsure how to proceed.
Note I CANNOT get QFil to work without EDL mode, which requires me to tear my phone apart.
Any suggestions? Does anyone have any certified knowledge of how to fix and reflash stock Nokia 6? I don't want to take it to a dealer because they will update it and make it unrootable (and probably won't be able to even touch it since bootloader is unlocked.)
ATM, all I can boot to is TWRP recovery or Download Mode.
Help?
Click to expand...
Click to collapse
First flash stock recovery, then boot into stock recovery and flash latest OTA
Link for latest OTA got from Telegram (TA-1025 ) : https://android.googleapis.com/packages/ota-api/package/5d91fc596557fecf1ba49b9321b446c64e3acd06.zip
Note :Your bootloader will be remained unlocked. don't worry
Sharashchandra said:
First flash stock recovery, then boot into stock recovery and flash latest OTA
Link for latest OTA got from Telegram (TA-1025 ) : https://android.googleapis.com/packages/ota-api/package/5d91fc596557fecf1ba49b9321b446c64e3acd06.zip
Note :Your bootloader will be remained unlocked. don't worry
Click to expand...
Click to collapse
I'm stuck in EDL mode now, any fixes or tips on how to flash/patch? QFIL is saying 'Failed to switch to EDL Mode'
Dantheman221 said:
I'm stuck in EDL mode now, any fixes or tips on how to flash/patch? QFIL is saying 'Failed to switch to EDL Mode'
Click to expand...
Click to collapse
Is phone is totally dead?? what you are getting when you insert charger? how pc is detecting your device (go to device manager)?
Sharashchandra said:
Is phone is totally dead?? what you are getting when you insert charger? how pc is detecting your device (go to device manager)?
Click to expand...
Click to collapse
It shows up as a QualComm COMM port device. But before you get your hopes up, every time I have tried to flash it, it says "Failed to switch to EDL mode" :-/.