After successfully unlocking my device's bootloader, rooting and installing TWRP - by following this guide - I decided to flash LineageOS14.1 - or at least attempt to. I didn't flash the no-verity-opt-encrypt.zip file, but everything seemed to be working OK, until I booted into LineageOS, where it demanded a password I've got no damn idea about (nor do I remember ever setting - hell, I had just disabled the secure startup option). Since I could actually browse my SD card, I tried rebooting into recovery, which didn't help, as did my attempt at flashing no-verity-opt-encrypt.zip regardless if I selected to keep the system write only (I assume because the DRM thing already got triggered?).
I then attempted to flash a KDZ file (it was either H85020D or H85020A from here) which gave me an error (I don't remember the exact code - I'll update later). And so I managed to get myself stuck on download mode. Pulling the battery doesn't help, Every time I try to use LGUP it comes back with the same error. I tried reflashing twrp and unlock.bin but I still can't get past download mode.
Garfoth said:
After successfully unlocking my device's bootloader, rooting and installing TWRP - by following this guide - I decided to flash LineageOS14.1 - or at least attempt to. I didn't flash the no-verity-opt-encrypt.zip file, but everything seemed to be working OK, until I booted into LineageOS, where it demanded a password I've got no damn idea about (nor do I remember ever setting - hell, I had just disabled the secure startup option). Since I could actually browse my SD card, I tried rebooting into recovery, which didn't help, as did my attempt at flashing no-verity-opt-encrypt.zip regardless if I selected to keep the system write only (I assume because the DRM thing already got triggered?).
I then attempted to flash a KDZ file (it was either H85020D or H85020A from here) which gave me an error (I don't remember the exact code - I'll update later). And so I managed to get myself stuck on download mode. Pulling the battery doesn't help, Every time I try to use LGUP it comes back with the same error. I tried reflashing twrp and unlock.bin but I still can't get past download mode.
Click to expand...
Click to collapse
If you can get into TWRP still, I would try wiping the system and data. Then instead of LGUP, use uppercut (I'll link you to that if you need me to) to flash a KDZ to go back to stock
Related
I recently rooted my phone. That worked no problem. I then tried to install CyangenMod through BobZhome ROM's. I can't post the link but it's easily found on google. I tried installing his CM11. I used the CWM file he included and used the app he suggested. I loaded the file on to my SD Card and click on reboot to recovery in the app. My phone said Security Error under the LG symbol as it's booting. I've read many people that have the same problem. But my phone isn't able to do even the basic things they tried. I tried hard resetting it. It showed up with the logo and Security Error. I can't even put my phone into S/W mode. It just loads up the same logo and Security Error screen. I don't know what else to do.
You need to install fastboot and flash the uboot and xloader for your phone model, and whatever version of android your phone shipped with(If you don't remember, use ICS).
http://forum.xda-developers.com/showthread.php?t=2119090
Then once that is finished, you need to download a version of android for your model.
http://forum.xda-developers.com/showthread.php?t=2107971
Finally "Offline flash" the kdz file you downloaded.
http://forum.xda-developers.com/showthread.php?t=2085344
The reason this happened is that you have a locked bootloader, this needs to be unlocked in order to flash custom roms. It is especially hard for this phone.
I've searched through the forums, but haven't found an answer, so I'm starting a new thread.
I received a G Watch as a gift last weekend, and it had a problem on the initial configuration. It wasn't able to connect and download any updates, so I manually flashed the updated firmware. Everything is working fine, and I'm on build LDZ22D. I was able to use G Watch Restore Tools V9 to flash system and recovery (and, in fact, boot, although that didn't seem to do anything), which got my watch up to an earlier version.
I then tried LG G Watch Return to Stock LDZ22D to get to my current build. However, I'm notified that there's an update available, but I'm not able to install it. When I try to install it through the regular user interface, it boots to recovery.
I've tried using the stock recovery, but had no luck with getting anything other than the android with the sore tummy appearing. I've used TWRP to try to flash update.zip (the stock downloaded update) and also tried this image.
When I try to apply update.zip through TWRP recovery, it gives me an error.
E: Error executing updater binary in zip '/cache/update.zip'
Package expects build fingerprint of lge/platina/dory:5.1.1/LDZ22D/19259530:user/release-keys or lge/platina/dory:5.1.1/LCA43/2160025:user/release-keys; this device has lge/cm_dory/dory:4.4.2/KVT9L/561735d166:eng/test-keys
It looks like the release keys are set to a nexus 7 build number (I don't understand how that's even possible). Is there a way to rewrite those keys? I understand they're part of the digital signing process, but I'm not sure why they didn't reset when I used the return to stock tool to flash my current image, which is the actual LDZ22D build. I appear to have a key mismatch. I've tried reflashing boot.img, system.img, and recovery.img manually (the ones included in the return to stock download), but they don't seem to work.
I get the same error when I try to flash the update I downloaded through ADB sideload. I'm frustrated, since my watch gives me this error, then after I reboot, it goes ahead and downloads the update.zip again, killing my cell data plan.
I'd love any help or insight into this. Is there a way to turn off the verification of the keys, or write the actual keys associated with my build? I'm new to working with a watch, and I've got limited experience working with phones/tablets through custom recovery. I'm not interested in a custom rom for my watch - I just wanted to get it to run properly on the stock image, and had a whack at getting it set up through developer options instead of letting it error out when I first got it.
Thanks in advance!
Still working on it
Okay, after quite a bit more research, it appears that my recovery.img doesn't match the rest of the build. I've tried the LDZ22D recovery.img, but it doesn't respond to any user input.
I'm now trying the factory image files from this post.
It seems there are a few people having problems getting to LCA43 recently. If you have an unlocked bootloader by now, you can try this method (TWRP restore from my LCA43 system+boot backup).
Hope this helps.
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
My attempt to root my H930 went very wrong... So I started by unlocking the bootloader and flashing TWRP. After that I didn't manage to get in to TWRP. Instead it started to boot, but froze eventually. Now I can't get it to boot (It gets stuck on initial LG V30 screen), and I can't power it off. I can get into stock recovery (apparently it got far enough to replace TWRP) and download mode with hardware button combinations. But the download mode seems to be different from fastboot mode (looks different on phone, and fastboot can't find it) so I can't try to flash TWRP again. I also managed to get it into a check IMEI + S/N mode by holding all buttons at once...
I've tried flashing H93010f_00_OPEN_EU_OP_0925.kdz with LG UP/Uppercut (since I can get to download mode). It went fine but the situation is the same - no boot, no way to power off.
A factory reset from stock recovery doesn't help either.
Please advice..
Alright, I acually got in to fastboot mode even though I'm not quite sure how.. I basically first went in to download mode, and then pressed vol down + power to reboot, and ended up in fastboot mode. From there I flashed twrp again. And this time I managed to get in to TWRP. Since I didn't have a working ROM I went ahead and wiped all but external sdcard and tried flashing Boombox. It resulted in an "Error: 1"..
So I tried flashing H93010f_00_OPEN_EU_OP_0925.kdz from LGUP again, and now I'm back to a device that doesn't boot again.
Which root are you trying to flash? TWRP also is in alpha at the very best at this point. Can you extract the KDZ and use fastboot to flash the .img files inside, assuming they have .img files inside of the KDZ?
jcsww said:
Which root are you trying to flash? TWRP also is in alpha at the very best at this point. Can you extract the KDZ and use fastboot to flash the .img files inside, assuming they have .img files inside of the KDZ?
Click to expand...
Click to collapse
I'm not trying to flash any root. I was planning on flashing Magisk but never got that far. At this point I'm just trying to get a working phone. I read about extracing img files from kdz but the tool didn't work in my virtual WinXP machine so I'm trying to fire up a Win10 machine now (I'm on mac).
Meanwhile I tried flashing boot and system from "LGH930GAT-00-V10c-222-01-OCT-12-2017+0.zip" but that resulted in the phone automatically booting into TWRP... That can't be good.
egendomligt said:
I'm not trying to flash any root. I was planning on flashing Magisk but never got that far. At this point I'm just trying to get a working phone. I read about extracing img files from kdz but the tool didn't work in my virtual WinXP machine so I'm trying to fire up a Win10 machine now (I'm on mac).
Meanwhile I tried flashing boot and system from "LGH930GAT-00-V10c-222-01-OCT-12-2017+0.zip" but that resulted in the phone automatically booting into TWRP... That can't be good.
Click to expand...
Click to collapse
With some other phones, like Nexus devices. Flashing older boot images can cause bootloops. I don't know if this is the case with your device but it might be something to consider. Have you tried flashing the complete latest factory image to see if that solves the bootloop?
jcsww said:
With some other phones, like Nexus devices. Flashing older boot images can cause bootloops. I don't know if this is the case with your device but it might be something to consider. Have you tried flashing the complete latest factory image to see if that solves the bootloop?
Click to expand...
Click to collapse
Unfortunately I haven't been able to get able to get a hold of a KDZ other than for 10f. I'd like to try 10v.
I got the extraction tool working in a Win10 box now, and I'm trying to extract boot and system images from the 10f KDZ...
egendomligt said:
Unfortunately I haven't been able to get able to get a hold of a KDZ other than for 10f. I'd like to try 10v.
I got the extraction tool working in a Win10 box now, and I'm trying to extract boot and system images from the 10f KDZ...
Click to expand...
Click to collapse
Best of luck!
Nope, that didn't work either. fastboot threw an error telling me the system image was too big for the partition.. At least the system image from the 10c dump fit properly..
So I guess my best bets right now are to either get a hold of a 10v KDZ, or wait for something flashable through TWRP.. :/
Is there like a lastlog for system boot that would be reachable from TWRP/adb..? It would sure be nice to see whats going wrong...
egendomligt said:
Nope, that didn't work either. fastboot threw an error telling me the system image was too big for the partition.. At least the system image from the 10c dump fit properly..
So I guess my best bets right now are to either get a hold of a 10v KDZ, or wait for something flashable through TWRP.. :/
Is there like a lastlog for system boot that would be reachable from TWRP/adb..? It would sure be nice to see whats going wrong...
Click to expand...
Click to collapse
No clue!
Ok, I got it to boot again!
* I formatted data (not wiped) inTWRP - Not sure if this step was relevant
* Flashed stock recovery/boot/system from a KDZ dump called "LGH930GAT-00-V10c-222-01-OCT-12-2017+0" - found the link in some other thread here
* Rebooted and watched it boot - went in to "Android is upgrading..."-screen - rebooted - then booted normally.
Thanks for the help and a special thanks to @Perkash who helped me out through PM.
Hello,
I made a mistake when rooting the tablet (BTV-W09), I think related to using HiSuite to restore a backup which then basically left me without a working OS, since I needed to input an unlock code with no keyboard.
Long story short after trying many methods like "dload" via sdcard with firmware finder files or using HuRUUpdater via TWRP all I have right now is a completely clean tablet, no OS installed, all I can do is
1. Boot into fastboot but adb doesn't work I assume it only does when OS is installed, so this is completely useless for me. Also of course HiSuite doesn't recognize the tablet here or in any other mode whatsoever.
2. Boot into upgrade mode but it fails to flash UPDATE.APP from sdcard/dload. I'm using the same exact firmware I was using before this fiasco.
3. Boot into eRecovery but I don't get any options to factory reset, never did (and of course after wiping everything that's gone I guess if it ever could be enabled), I can only "download from internet" but it ALWAYS fails with getting package info error or something like that, apparently it's common for people to get this.
4. Boot into TWRP, but I cannot flash update.zip, it fails with "update package from zip failed"
I have the bootloader unlocked of course. And SDCard is working, 100% functional, no errors.
Is there any way to flash stock firmware on this thing or is it a paperweight now.
Thanks for you time
HuRuUpdater did the trick as explained here. Not sure if the NANDROID backup restore was necessary prior to that, probably yes as all the partitions were cleared.