Hi experts!
Is there an available factory image of the latest firmware for griffin xt1650-03 for download? I unlocked my boot loader and tried to flash custom firmware now I am stuck in boot loop. My phone was nougat and updated via OTA last week before I decided to unlock boot loader. I tried loading the latest image I got from firmware.center but I am getting Downgrade version and verification failed when flashing stock partition and not loader. Please help
Note: I did this my wifi became unusable after my last OTA (mac 02:00:00:00) and thought using custom firmware would help
And I did not make a back up
Get it in fastboot mode, flash TWRP and root it. That might work.
I am in exactly the same position as OP, although I have successfully installed TWRP and have open bootloader from which I can boot into TWRP no probs. I didnt do a backup (will never again make this error!!)
The problem arises when I try to flash (any) files over to device I get the "Downgrade version and verification failed" like OP when flashing stock Telus rom (telus phone) or any other rom/files.
Rebooting brings me back to the moto unlocked bootloader page (horrible!) and the only way out is to get key combo or fastboot into bootloader/recovery etc.
Tried flashing multiple images as whole or bit by bit, always get the same bad validation message. Finding it hard to believe this 700dollar phone is a brick after literally following MotoS own 'unlock your bootloader' instructions. Never had issues like this on OPO, S6, S7, LG etc.
PC shows android device connected, nothing in the two empty folders that appear. TWRP confirms I have no OS installed and throws me back to bootloader.Wondering if locking bootloader again will allow me to install 'stock' ROM or at least recovery? I have reached my android knowledge limit and am not sure where to go from here, any help much appreciated!
OK. This happened to me. The way that I solved it was by flashing the RETUS NPL86.25.15 and then flashing the OTA 25.17-3-3 through twrp. Although I think I could've saved the headache if the original instructions included flashing the OEM.bin but anyways. That's what I did. Hope it helps.
Thanks. I did try flashing the oem.bin but got partition name error.
Can you link to the files you mention I think it's a kernel and then an OTA image? Thanks again in advance.
What I mean is that when I first started flashing the RETUS rom the instructions skipped that part so I ended up flashing most of the file system without something so it would never boot but it wouldn't loop it'd just hang. So basically you flash everything and then include the OEM.bin after you do the system chunks
Related
Hi! I've managed to brick my device (d610ar) badly, i think
the device doesn't boot normally (message "Secure booting error! Cause: boot certification verify.", and i am stuck there), can't charge it with the wall charger, and the only thing that works is download mode; but flashing a kdz with LG FlashTool (the way i went back to stock a few times) says flashing and at 2% (or 3% sometimes) it says that doesn't find the device, that i have pull out the battery to reconnect my device again and when i do that it does the same thing on a loop, asking to do it again later..
the funny thing is that it appears on device manager on windows, on com port 11 for example, but the FlashTool doesn't recognize it..
so, i can't flash any kdz and doesn't boot.. i've read around here in xda to enter fastboot to fix it, but.. can this device enter fastboot? i couldn't do it, tried adb too and couldn't make the device visible..
i, before this happened, had multirom installed, rebooted to recovery and deleted secondary roms to install in primary rom cm12.1.. there started to happen strange things when rebooted normally to configure it..
after a while trying to boot found around here in xda too that i could enter twrp recovery via hardware keys to reinstall again, so got into it and installed a flashable zip to come back to stock KitKat directly, that have worked for me before..
after that rebooted and i can't do anything else than download mode..
i kinda figured that the problem must be that multirom injected the boot sector after installing the stock flashable zip, and when i did that restored the stock aboot and abootb (these, modified carefully, allowed us to unlock bootloader and flash recoveries, etc, etc.. ; by the way, many thanks to the devs that discovered it and made the guides!)..
now i have read the instructions for flash via fastboot the stock boot.img and so pass the security verification, but i can't enter it..
so, what do you think that could be the next step? or is it really hard bricked and i should forget about it? i'm really hoping to recover it but i don't know what else to do..
sorry for the bad english, not my primary language
thanks for reading and i am hoping to hear some suggestions!
He is not hard bricked you need to flash stock boot and reunlock bootloader if you have custom recovery still installed, but go first with the eazy way search xda about lg flash tool stuck at 2% there some guides to help you get kdz flashed
Thank you very much!
numpea said:
He is not hard bricked you need to flash stock boot and reunlock bootloader if you have custom recovery still installed, but go first with the eazy way search xda about lg flash tool stuck at 2% there some guides to help you get kdz flashed
Click to expand...
Click to collapse
Thank you very much! You made me realize why wasn't working..
Because of you, i started to search threads related with the "flashtool stuck at 2%" and one of the things to look at was a txt file to see what was the problem.. there i found out that the lg FlashTool recognized my device as LGD618..
That's when i realized that i must've messed up when i flashed a lollipop flashable zip for the D618(a while ago), "converting" my cellphone on that model.. so when i connected on download mode and put the LGD610 kdz the comparison of cellphone model and binary model didn't match..
Solution was to flash LGD618 kdz, boot up normally, install towelroot, install supersu, edit a line on build.prop
from persist.multisim.config=dsds to persist.multisim.config=none
rebooted and that's it.. everything works perfectly now! i won't be doing stuff to it for a while
probably will stay stock like that, because now i will be using an OnePlus One in a few days and the G2 mini will be used by my mother, i think..
Thanks again! You saved my device for being bricked forever
i glad i could helped you :good:
I tried installing kitkat having installed lollipop and did not work, also I tried installing lollipop and nothing. Well I think this update lollipop are adding some kind of lock to disallow downgrade or upgrade by KDZ. I try other methods, unlocking bootloader, and install a aboot.img, bricked my phone. I recommend that you do not attempt to unlock the bootloader and install any system image that is not official, or may end up with a dead device.
Hello there,
I was having trouble flashing a custom rom on my Oneplus X. I'm not an expert on these things but I've been rooting phones for years (following directions, etc). I'm rooted, unlocked bootloader, etc. From TWRP I tried flashing several roms including Sudamod 6.01, unofficial CM13 and 12.1, and Exodus. Nothing worked. I kept getting like "E: error executing updater binary in zip".
Foolishly, I didn't have my glasses on when I found this page here: https://forums.oneplus.net/threads/e-error-executing-updater-binary-in-zip.387944/ . Users there appeared to have success "updating the firmware", so I attempted to follow suit. Accordingly I downloaded and flashed the following file: https://www.androidfilehost.com/?fid=23991606952604019 linked in the thread. Not seeing well, I didn't realize this was for OPO, not OPX. I admit I didn't quite understand what "updating the firmware" meant in this case--ordinarily I would have thought that meant updating a ROM, but since that was exactly what OP was having trouble doing I assumed it must have been some other BIOS type system I didn't know about (foolish, I know).
After flashing that zip I still couldn't install a ROM. The next thing I tried was to update TWRP. I downloaded an update to 3.0.1 on my PC and transferred it over via USB without rebooting TWRP and updated it. Still couldn't install roms.
The next thing I tried was to do a data wipe. Still didn't work. Finally, I thought I'd try rebooting TWRP (first time I rebooted since upgrading to 3.0.1).
I've been bricked ever since. I still appear to have connectivity with my PC via fastboot but no ADB. When I hold down VOL- and PWR it might give me a little vibration pulse, but the screen doesn't come on. It doesn't appear to be booting no matter what I do. I've tried installing different recoveries (via fastboot), including stock, TWRP version 2.8.7.0 and 3.0.1. Though it reports to finish flashing, when I try fastboot boot <filename.img>, but then it said "cannot load 'recovery'"
So right now I'm just lost. Can something be done?
(deleted)
Did you see this thread? http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
If not, you'll find what you want I think
(deleted)
pedrof1991 said:
That thread is for unbricking hard bricked devices (that mean that you won't even get a boot logo, or recovery, or fastboot, etc.) but OP's device is only softbricked because we can boot into recovery and flash stuff :]
Click to expand...
Click to collapse
Then try flashing last OOS
Nexx_ said:
Then try flashing last OOS
Click to expand...
Click to collapse
You were right, the OP's is hardbricked... I misread the last bit of the tread.:/
The the link you post should be it OP CHECK THE LIST POSTED BT NEXX
try flashing Twrp in fastboot again in fastboot mode iff you can get in to fastboot.
Thanks all. I followed the hard unbricking thread. Worked. Saved me a couple hundred bucks. Learned stuff.
Model:XT1521 Retasia(Indian)
So let's get on with the story
I own a moto e 2 4g variant. I unlocked the bootloader of the device,installed a custom recovery and flashed a custom ROM. Everything went well;I was trying a new ROM almost everyday(5.1.1 and 6.0.1) until one day when I decided to go back to stock ROM.I downloaded the official 6.0 stock ROM,installed it and started the device.The phone booted,went straight to recovery and showed erasing.The problem starts here.It showing eraseing and rebooted after some time and I thought that it's going to boot up into stock 6.0.But I was wrong.The phone booted and again did the same thing and this went on in a loop.So I decided to try it once more.This time I did two more things prior to installing the ROM;
Fastboot erase all
Fastboot erase system - w
Till then in bootloader it showed official in software status.But after those two erase commands it started showing modified.
Even then the result was the same I.e.showing erasing and rebooting.So I thought that I will go back to custom ROM for the time being.all went well,phone booted up but there was no signal.The phone was not accepting any Sims. I went to bootloader and immediately found out the cause.It was showing not found under baseband.So I seperately flashed a modem but to no luck.As of now I have tried all stock rims available(5.0.2,5.1.1,6.0) but the device is not booting up.
Any help will be highly appreciated.
Thanks in advance.
This happened to me with CM13, the same thing happened with the baseband number, and I couldn't even enter in the recovery, so I had to manually flash the Stock ROM via adb. It happened to me again when I tried to root my phone even with the systemless root, the phone just doesn't boot up, I'd recommend you to flash the basebands found in the forums, if that doesn't fix it, you'll have to manually flash the stock rom via adb or you can use the easy tool, it's fairly simple if you follow the steps, I'll leave the links bellow.
Easy tool flasher
Basebands
Filz0r said:
This happened to me with CM13, the same thing happened with the baseband number, and I couldn't even enter in the recovery, so I had to manually flash the Stock ROM via adb. It happened to me again when I tried to root my phone even with the systemless root, the phone just doesn't boot up, I'd recommend you to flash the basebands found in the forums, if that doesn't fix it, you'll have to manually flash the stock rom via adb or you can use the easy tool, it's fairly simple if you follow the steps, I'll leave the links bellow.
Easy tool flasher
Basebands
Click to expand...
Click to collapse
Used the flashing tool.But in every mode of flashing,the bootloader flashing and boot.img flashing is showing some error.But rest all are flashing succesfully.Still in bootloader it is showing baseband not found.And when I boot the device,the bootloader screen comes up,followed by a black screen and the cycle repeats.Any help would be appreciated.
Edit:My moto e 2015 is a LTE RETASIA(Indian) model.In the baseband link you provided,XT1521 RETASIA version's baseband is not available.
Fastboot flash bootloader bootloader. Img
Rename motoboot img
Sent from my MotoG3 using XDA-Developers mobile app
first.act.line said:
Fastboot flash bootloader bootloader. Img
Rename motoboot img
Sent from my MotoG3 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thanks I will try that.
gauthamkithu said:
Model:XT1521 Retasia(Indian)
So let's get on with the story
I own a moto e 2 4g variant. I unlocked the bootloader of the device,installed a custom recovery and flashed a custom ROM. Everything went well;I was trying a new ROM almost everyday(5.1.1 and 6.0.1) until one day when I decided to go back to stock ROM.I downloaded the official 6.0 stock ROM,installed it and started the device.The phone booted,went straight to recovery and showed erasing.The problem starts here.It showing eraseing and rebooted after some time and I thought that it's going to boot up into stock 6.0.But I was wrong.The phone booted and again did the same thing and this went on in a loop.So I decided to try it once more.This time I did two more things prior to installing the ROM;
Fastboot erase all
Fastboot erase system - w
Till then in bootloader it showed official in software status.But after those two erase commands it started showing modified.
Even then the result was the same I.e.showing erasing and rebooting.So I thought that I will go back to custom ROM for the time being.all went well,phone booted up but there was no signal.The phone was not accepting any Sims. I went to bootloader and immediately found out the cause.It was showing not found under baseband.So I seperately flashed a modem but to no luck.As of now I have tried all stock rims available(5.0.2,5.1.1,6.0) but the device is not booting up.
Any help will be highly appreciated.
Thanks in advance.
Click to expand...
Click to collapse
u have to flash a official rom with propper way and remember u cannot flash old bootloader on the new bootloader it will definatly brick ur phone so if ur bootloader working do not replace it with old one for more info u can go in official rom section of this site and bootloader section.....good luck
vishalgupta.vns said:
u have to flash a official rom with propper way and remember u cannot flash old bootloader on the new bootloader it will definatly brick ur phone so if ur bootloader working do not replace it with old one for more info u can go in official rom section of this site and bootloader section.....good luck
Click to expand...
Click to collapse
Thanks buddy but unfortunately I have tried that.:crying:
OK guys, thread cleaned.
No more flame from anyone please, no more garbage.
OP please provide as much details as possible. Everyone else, you can ignore the OP if you want, but do not come in here just to flame.
Thanks.
Hi, just wondering if anyone can share his/her signed boot.img from stock rom RETMX, the one I tried to flash with fasboot ends in: (bootloader) signed with bad key. The phone boots, and i can flash roms with twrp and stuff, but when in stock, trying to install OTA gets in error due to the bad key.
edit: Going into more reasoning, I realize that the main cause of the OTAS not installing, is because i've already taken the last update, and that probably messed with the gpt.bin, because when trying to flash it, the fastboot console says that I'm trying to downgrade, and aborts. So my only hope to restore this to total stock is if someone with an untouched twrp backup can share his backup with me. It needs to be in the latest update of RETMX. I would really apreciate it. Thanks.
I've been trying to do so for a week, but just can't do it.
I've tried two way:
I've locked the bootloader from fastboot-mode, shutdown and then got into BROM-mode to re-flash the "boot", "recovery" and "vbmeta" (tried "dtbo" too) images. Then I enter the recovery, I format the data and after that it gives me the "normal" corrupted recovery error.
I've also tried to flash the partitions and lock the bootloader through the same fastboot "session" but I just can't get it done.
I'm on OOS11 A19 (european), I haven't ever upgraded to anything over C.01 (I read that C.05 and beyond would break the BROM-mode). A guy on YouTube did it with A13/15 (indian) but I don't know if it's because of this. This is the first phone I ever mod and sure this is a nightmare (I'm coming from an unofficial PixelExperience).
pasqchia84 said:
I've been trying to do so for a week, but just can't do it.
I've tried two way:
I've locked the bootloader from fastboot-mode, shutdown and then got into BROM-mode to re-flash the "boot", "recovery" and "vbmeta" (tried "dtbo" too) images. Then I enter the recovery, I format the data and after that it gives me the "normal" corrupted recovery error.
I've also tried to flash the partitions and lock the bootloader through the same fastboot "session" but I just can't get it done.
I'm on OOS11 A19 (european), I haven't ever upgraded to anything over C.01 (I read that C.05 and beyond would break the BROM-mode). A guy on YouTube did it with A13/15 (indian) but I don't know if it's because of this. This is the first phone I ever mod and sure this is a nightmare (I'm coming from an unofficial PixelExperience).
Click to expand...
Click to collapse
Okay brother, seems like you have flashed wrong boot img. Flash this boot img. Hopefully your issue will be fixed.