Hey there. I've been using Candy5 for a bit, but kept a nandroid backup of stock. Today I restored stock (was working for a day) but when I tried to restore back my Candy5 nandrood backup from recovery it won't boot, and shows up a LG logo with 'Security error' under it. What may be the problem? I had to go to work and left my phone at home. Will look at it in a few hours,just wondering if you guys saw something similar? Any workarounds to that? Or how to fix it?
Jast flash aosp kernel Furnace od 777jon.
How do I that ? Can't access recovery because it won't boot. From what I've read so far D855 can't go into fastboot.
Have you tried with button combination volume down and power to boot in to recovery? If not then go into download mode with volume up and plug usb cable and reflash to stock rom with Flash Tool.
Didn't even know the combination exists, was used to it from former Sony phones, but it isn't working here.
Yup, reflashing stock now, thanks.
The problem prob was I installed recovery through AutoRec app. That seems to be for 5.0 only.
Which is the best recovery/kernel for 5.1.1?
Furnance and 777jon kernel both are good and work well on 5.1
reboot to recovery with hard keys (hold power+volume down, when see the LG logo, release and hold again keys, then you see the factory reset option, double yes)
flash your current rom again, (no need to GApps again, just rom) wipe cache+dalvik, reboot system.
AutoRec is the problem for me to see this error, and my solve
sorry for bad english
Related
After installing TWRP 2.6.3.2 (latest atm) I tried to flash the ROM CMB rc2 on my G pad. I am unable to post in that topic because of my low post count.
Everything went fine, though during the boot it just never stopped showing the boot screen/CMB logo (I am aware that the first time it is used to take a while). The thing I might have done wrong is before the new flash, is to erase everything at first. I didn't do that =(.
I am now unable to reach in through ADB. It just doesn't find the device. Any other way of booting in to recovery is unknown to me. I tried several times rebooting with a variety of button-combinations, but it just continues to the boot screen/logo. I dont even know if there even IS an button combination to boot into recovery.
Sadly when force-shutdown (holding the power button) it doesn't shut down. It restarts. I am now unable to shutdown my own tablet.
Help would be much appreciated. Thanks in advance!
Any additional info:
I have not flashed gApps right after, or any thing else for that matter.
I have installed TWRP from 2.6.3.0 => 2.6.3.1 => 2.6.3.2 in just about 3 minutes after each other. I was mistaken in the files, picked the #.1 in stead of the #.2 directly.
If there is any information I could provide extra that would help sort this out I would gladly do so.
jhjoosten said:
After installing TWRP 2.6.3.2 (latest atm) I tried to flash the ROM CMB rc2 on my G pad. I am unable to post in that topic because of my low post count.
Everything went fine, though during the boot it just never stopped showing the boot screen/CMB logo (I am aware that the first time it is used to take a while). The thing I might have done wrong is before the new flash, is to erase everything at first. I didn't do that =(.
I am now unable to reach in through ADB. It just doesn't find the device. Any other way of booting in to recovery is unknown to me. I tried several times rebooting with a variety of button-combinations, but it just continues to the boot screen/logo.
Sadly when force-shutdown (holding the power button) it doesn't shut down. It restarts. I am now unable to shutdown my own tablet.
Help would be much appreciated. Thanks in advance!
Any additional info:
I have not flashed gApps right after, or any thing else for that matter.
I have installed TWRP from 2.6.3.0 => 2.6.3.1 => 2.6.3.2 in just about 3 minutes after each other. I was mistaken in the files, picked the #.1 in stead of the #.2 directly.
If there is any information I could provide extra that would help sort this out I would gladly do so.
Click to expand...
Click to collapse
Your best bet would be to restore the factory firmware and start over. To do this, follow the instruction in this thread. The only change is that to enter Download Mode on the G Pad, you hold volume up and volume down while inserting the USB cable rather than just volume up.
Hi, I don't usually ask for help, because I can easily find the answer in Google, but this time I made an exception because I couldn't find a solution to this error.
There is a funny story about it, I updated to Lollipop 5.0.2 right after I got my tab, then I found KingRoot and rooted it, but then I noticed my tab was slowing down with it installed so I changed to SuperSU using a script, after that I decided that I wanted CM on this tab, I've found it, after I flashed the recovery and tried to restart into the recovery it appears this message (error : boot certification verify) above the LG logo.
Summarizing all that, I was an idiot and flashed a recovery AFTER I updated to 5.0.2 ?
The V410 can be downgraded to kitkat using the method in the linked thread, it is a long read. The kdz you have to use messes up aboot and internal storage, so it is a pretty long and involved process to get everything back to normal.
http://forum.xda-developers.com/g-pad-10/general/tutorial-lg-gpad-v410-5-1-to-4-4-t3232150
Greydus said:
Hi, I don't usually ask for help, because I can easily find the answer in Google, but this time I made an exception because I couldn't find a solution to this error.
There is a funny story about it, I updated to Lollipop 5.0.2 right after I got my tab, then I found KingRoot and rooted it, but then I noticed my tab was slowing down with it installed so I changed to SuperSU using a script, after that I decided that I wanted CM on this tab, I've found it, after I flashed the recovery and tried to restart into the recovery it appears this message (error : boot certification verify) above the LG logo.
Summarizing all that, I was an idiot and flashed a recovery AFTER I updated to 5.0.2
Click to expand...
Click to collapse
I just did the same thing (similar, after installing supersu for root, not remembering CM root is built in).
All I had to do to recover was:
1. Boot into recovery mode manually. Press volume down, then power and hold both, release the power button when the LG logo comes up, then instantly press the power and volume up buttons and hold (so now you are holding all 3 buttons). Just use volume down and power to select yes twice.
2. Once in recovery, I was able to flash an older CM13 rom/image I had (not even a stock one), booted, then just flashed my CM14.1 back, with its gapps, whip dalvik cache.
3. Reboot - when it asks to install supersu do not install option doesn't work, but the install option fails and it reboots for me.
Good to go.
I've got v-410 rooted in 5.0.2. Do I have to downgrade to KK in order to flash twrp (so I can go to another rom)?
Hi, I have a rooted s4 sgh m919. I am running twrp custom recovery. So I just flashed cm 13 nightly build for the s4 and it worked and ran through boot up and everything. Then I realized that I had stupidly forgotten to backup my apps(I though I had but it was a twrp backup). So I returned to recovery mode using adb because my up volume buttons dont work(biggest problem for me now) and used twrp restore of a backup I made before the new rom. Now I know that my twrp backups work because I have successfully restored before but that was using the same rom, this is the first time flashing a new rom. Since I am a noob, I didn't know that I have to factory reset and delvik cache wipe before I restored my backup since they were different roms. Now after booting up and getting past the boot animations it goes straight to a black screen with a bunch of "Unfortunately ______has stopped" for just about every single app I have including system apps and UI. I can boot into the download mode prompt(where it says volume up to download mode, down to reboot) but since my volume up button doesn't I cant boot into recovery or download and do a factory reset. I can boot into safe mode but I still get the same black screen with a bunch of "Unfortunately ______has stopped". I also can't do it through adb since I have no access to phone settings and when I connect to the computer, the computer make a sound recognizing something was plugged in but won't show my phone in the libraries and when I use "adb devices" my phone isn't there. I stored my backup onto my ext sd card if that helps. Is there anyway to get into recovery mode or even just do a factory reset without using volume buttons or the computer? And has anyone else had this problem and if so what is it called(hard brick, soft brick, bootloop.....). Thanks!
You need to fix your up-vol button.
There is also a special micro USB loopback plug which I think can make the device boot into a special firmware loader mode. Then you would use heimdall/odin to replace the firmware, but I have never done that.
As for what to call the problem, I say "dumb user with broken hardware". You knew that your up-vol button was broken and what would happen if you could not get into recovery. Now that it has happened you want a magical fix instead of doing what you already know you need to do. Sorry for honesty.
1st- buy a usb jigg, they go for less than $5 amazon, eBay etc.
2nd - while phone is powered off use the USB jigg to put it into download mode
3rd- use Odin to flash the latest ok3 firmware.
4th - use Odin again to flash cf auto root. (No need to check if it has root the recovery you flash should be able to root it)
5th- use Odin again to flash Philz touch cwm recovery.twrp causes lots of problems when flashing. Philz recovery has been flawless.
6th- flash any rom of your choice. If you can't get into recovery theres an app called quickboot that can put you in recovery as long as you're rooted.
So guys
I was on twrp and tried to flash a new rom but when it rebooted after the install, my Zuk z2 died.
It does nothing now. If I press the powerbutton for a long time it shortly vibrates for one second and the notification light also lights up for 1 second, but does not boot up. I tried volume combinations, don't work either.
What can I do guys?
Well, this guy managed to fix it
. Not sure if its the best way to fix it but it's still something
Effected said:
So guys
I was on twrp and tried to flash a new rom but when it rebooted after the install, my Zuk z2 died.
It does nothing now. If I press the powerbutton for a long time it shortly vibrates for one second and the notification light also lights up for 1 second, but does not boot up. I tried volume combinations, don't work either.
What can I do guys?
Click to expand...
Click to collapse
https://zukfans.eu/community/threads/how-to-unbrick-zuk-z2-from-diagnostic-port-900e.2856/ follow the steps
https://forum.xda-developers.com/lenovo-zuk-z2/how-to/deep-flash-revive-zuk-z2-hard-brick-t3577146
Use this if you didnt success from other methods.
tlxxxsracer said:
My video. The brick occurs when you usually backup a room with one version of twrp, flash another variant of twrp and then restore the nandroid from before.
Happened to me. Flashed MIUI, and then tried to restore a nandroid (not realising the TWRP changed).
Hope the video helps. Plus then you have a cable premade in case it happens again
Click to expand...
Click to collapse
Hello. Maybe you can give me some advice. I am stuck in engineering/diagnostics mode after I accidentally selected that option when I was in the bootloader trying to flash TWRP.
Basically, I had installed TWRP and Mokee 7.1.1. I wanted to check out the original chinese ROM so I relocked, flashed with QFIL, etc. I had first flashed MM, then I flashed latest chinese Nougat official.
I didn't like it, so I was trying to unlock the bootloader again, and in the process I ended up selecting the diagnostics/engineering mode. The phone was stuck there and I had no way of accessing the bootloader to reflash with QFIL or MiFlash
TO try to fix, I used the deep flash method you describe in the video, only I found it in zukfans. I was able to open the 9008 port, flash with QFIL/MiFlash. Even though both tools describe the flash as successful, on boot, it goes back to engineering mode.
How to I get out of there? Is my phone done?
Thanks!
Hello
I have recently rooted my LG G3 D855 and all went fine until i flashed TWRP, which i most certainly did wrong, and now i have no way of restoring the device since entering recovery presents me with the 2 prompts and afterward a blank screen and flashing red and blue LED. I tried holding VOL+ and plugged in the usb but it does not send me to download mode. Overall the phone does work, i mean it boots up fine and has all it's functions except the 2 mentioned above. I currently an on Lollipop 5.0 V21a. If anyone could guide me on where to look, since the best i have found is restoring back to custom which is not an option, I would appreciate it ALOT.