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)?
Related
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
I was on stock F240L20D, 4.4.2 Kitkat, rooted, PhilZ Touch 6 installed. I've tried some ROMs before but reverted back to this one. So, basically, I've been to the recovery several times, but only used the ADB method to access it, and I've made several backups too.
However, one thing that happened today has frustrated me completely. Long story short, I thought about making a backup again, although this time, I used the power keys to get to the recovery instead of the ADB method, backup completes successfully, nothing wrong just yet, but just as I tap on 'Reboot System Now', it boots back in to recovery.
I've tried everything, tried using all the ADB commands, even going through all the options in the recovery, but it always seems to boot back in to the recovery. Really can't figure out what's happening. Any help would be extremely appreciated.
UPDATE: So I've flashed a KDZ, the Lollipop one using the LG Flash Tool. It's taking a bit too long to start, currently stuck at the U+ Lte logo. I hope it gets fixed.
UPDATE 2: It says Android is upgrading, YES YES!!!!! This is so exciting, but I'm still not convinced.
With most of cwm version after 6.4.7, any time you use power + volume up to access the recovery, you will get the boot loop. Go here and down load the zip file from the first post. Flash the zip and you should be go to go.
http://forum.xda-developers.com/showthread.php?t=2619403
PROBLEM SOLVED.
So at first I used Kingroot to rood my device, and it failed, but then i just realized few days later that Kingroot was installed and used root checker to check and said that it does have root access. After that decided to change the Kingroot to SuperSU by following this video https://www.youtube.com/watch?v=WevWdErXWy4 (It's the SuperSU Me app). I then updated SuperSU binaries and restarted the phone, and now its stuck at the loading screen. I tried hard resetting my phone but it would only show the screen with the android logo and shapes in its belly for about 2 second and go back to the stuck logo screen. Now I'm wondering if there's any fix for it, and if there's no fix then I'm going to try resetting it through this http://lgg3root.com/lg-g3-root/how-to-unrootunbrick-lg-g3/ guide and I was wondering if I should download and use the bell stock factory firmware (I have a virgin mobile version).
Edit: fixed to be more clear.
I Nid 2P said:
So at first I used Kingroot to rood my device, and it failed, but then i just realized few days later that Kingroot was installed and used root checker to check and said that it does have root access. After that decided to change the Kingroot to SuperSU by following this video https://www.youtube.com/watch?v=WevWdErXWy4 (It's the SuperSU Me app). I then updated SuperSU binaries and restarted the phone, and now its stuck at the loading screen. I tried hard resetting my phone but it would only show the screen with the android logo and shapes in its belly for about 2 second and go back to the stuck logo screen. Now I'm wondering if there's any fix for it, and if there's no fix then I'm going to try resetting it through this http://lgg3root.com/lg-g3-root/how-to-unrootunbrick-lg-g3/ guide and I was wondering if I should download and use the bell stock factory firmware (I have a virgin mobile version).
Edit: fixed to be more clear.
Click to expand...
Click to collapse
if you can get into recovery you can probably do it without unbricking. to you have stock recovery or twrp or what? If you have stock recovery then boot into recovery and just run it and itll hard reset your phone, if you have twrp or something just download the flashable rom of your choice (there are stock modded roms too if you like stock) put it on an sdcard and wipe and install that rom.
if you don't know how to get into recovery then make sure your phone is off (if ur not sure do a battery pull and put it back in). hold volume down and power button until the screen comes on. when it comes on let go of vol down and power and then push vol and power again and hold again until you see the writing)
btw if you do a stock recovery hard wipe then you will lose root.
I also faced this problem...
Sent from my SM-E500H using Tapatalk
Problem solved. I just flashed the stock firmware onto my phone and it fixed the stuck on logo problem.
So, i recently have tried flashing Xposed on the MM 6.0.1 on G920P a.k.a Sprint S6
( ALL_SPT_G920PVPU3CPB6_G920PSPT3CPB6_CL7280193_QB8664149_REV02_user_low_ship.tar )
I have root and recovery, but Xposed doesnt seem to comply with me.
from multiple sources or builds.
And each Xposed file that i've tried so far that i've been flashing over and over again, rinse and repeat.
( Flash Stock through Odin, Go through setup process on the phone, Reboot Back to Download mode to Flash TWRP, Reboot, Back to TWRP to Flash Xposed, Once flashed i Restart it again, back to the s6 screen to becoming a black screen bootloop, thus having me restart the whole flashing process again )
from android file host website. And Default xda unofficialy build on this website.
xposed-v79-sdk23-arm64-by-romracer-20151218
xposed-v80.0-sdk23-arm64-custom-build-by-wanam-20160211 - ABDYASAR 7.8MB
xposed-v80.0-sdk23-arm64-custom-build-by-wanam-20160211 - SANOC 7.8mb
xposed-v80.0-sdk23-arm64-custom-build-by-wanam-20160211 -WANAM 7.8MB
xposed-v80-sdk23-arm64-by-romracer-20160202
It would go from the Galaxy S6 Boot Menu startup to black screen and bootloop back to the original BootMenu or screen.
NO LED cycles nothing, but i can access Download Mode and Recovery But Updating Nor Uninstalling doesn't do anything to the rom, it just keeps boot looping unless i Flash the Stock back into place.
I'd like to have Xposed working i havent found a version for me that would work for this but i would really appreciate if everyone could help out.
IAmTechFreq said:
So, i recently have tried flashing Xposed on the MM 6.0.1 on G920P a.k.a Sprint S6
( ALL_SPT_G920PVPU3CPB6_G920PSPT3CPB6_CL7280193_QB8664149_REV02_user_low_ship.tar )
I have root and recovery, but Xposed doesnt seem to comply with me.
from multiple sources or builds.
And each Xposed file that i've tried so far that i've been flashing over and over again, rinse and repeat.
( Flash Stock through Odin, Go through setup process on the phone, Reboot Back to Download mode to Flash TWRP, Reboot, Back to TWRP to Flash Xposed, Once flashed i Restart it again, back to the s6 screen to becoming a black screen bootloop, thus having me restart the whole flashing process again )
from android file host website. And Default xda unofficialy build on this website.
xposed-v79-sdk23-arm64-by-romracer-20151218
xposed-v80.0-sdk23-arm64-custom-build-by-wanam-20160211 - ABDYASAR 7.8MB
xposed-v80.0-sdk23-arm64-custom-build-by-wanam-20160211 - SANOC 7.8mb
xposed-v80.0-sdk23-arm64-custom-build-by-wanam-20160211 -WANAM 7.8MB
xposed-v80-sdk23-arm64-by-romracer-20160202
It would go from the Galaxy S6 Boot Menu startup to black screen and bootloop back to the original BootMenu or screen.
NO LED cycles nothing, but i can access Download Mode and Recovery But Updating Nor Uninstalling doesn't do anything to the rom, it just keeps boot looping unless i Flash the Stock back into place.
I'd like to have Xposed working i havent found a version for me that would work for this but i would really appreciate if everyone could help out.
Click to expand...
Click to collapse
Did it work. Ive only noticed a tad bit longer boot up the 1st time but all good.
i've tried most of them and i tried v80.0 or v80 and i got one part success half i didnt which was from it i got to the LTE spectrum screen and it just would go past that before it would just be the led flashing and bglank screen, i waited about and hour and still nothin changed from that screen.
Nevermind i made an update
This is what i've managed so far.... what am i missing here?
So here's what i"d take place in order to attempt a flash of Xposed Framework.
I start with Pre- Downloading the files for the MM 6.0.1 Stock Rom, it's in the forums Somewhere.
TWRP ( New_S6_Spr_TWRP_MM_Bootloader2 ) a.k.a 3.0.1
(This is a special version only for the Sprint SM-G920P and is meant to be flashed with Odin)
SuperSU 2.68 a.k.a ( BETA-SuperSU-v2.68-20160228150503 )
and obviously, Odin ( Odin3 v3.10 )
The steps that are taken place.
1st. I'd Boot my device into download/odin mode.
or
( while the device is powered off, i press and hold the home+power+volume down buttons.
and from there I'd be taken to a light blueish screen saying "Warning", and i follow through by pressing volume up)
2nd.
Once the device is in download/odin mode, and ready to go, i'd take my phone, plug it into my windows PC and open Odinv3 and from there
i'd select in odin, or i'd click the "AP" button and select the, tar file.
After that has been flashed thoroughly, I'd then proceed with the follow on screens, the 1st reboot and it updates or it says
Optimizing app 1 to 30.... the 2nd reboot where the hand free activation commences and
from that 3rd time it reboots and boots up again, i'd follow up with my login information.
3rd. once my device has been fully booted from the 2nd part, i'd then shut it down or restart it into "download mode again" and connect it to my pc again
and from there i'd load odin, and search or i'd find where I downloaded the special "TWRP .tar" or recovery file
and select the "Ap" option again and press start Afterwards.
After it flashes, right when its done i automatically hold the home+power+volume up buttons,
turn the device off and hold home+power+volume up and your should get some red text in the upper left hand corner with recovery not enforcing, that's okay dont be worried,
and from there it should boot into and be brought into TWRP...finally lol.
Now that's where you can flash SuperSU
4th. I'd leave my phone connected to my pc until, it's fully booting into twrp or i'd just connect it once im in the recovery.
I let my pc detect my phone and i'd copy both of these files.
SuperSU 2.68
and
Xposed
4th. After its copied, i'd go back into my phone, i tap install, and i select supersu and let it run, afterwards, i press reboot.
And let it sit for about another 2 minutes to do its own thing. Afterwards. once the phone is fully booted up.
I'd then go back into recovery, and flash Xposed and i'd wait about another 2-3 minutes for it to cycle
from the LTE Spectrum Screen to the, torquise colored screen where it's finally optimizing apps from 0 to 331.
5th. Once done, i'd finally have my advantage to install what i'd like which i'm doing as of right now still testing it out.
P.S if you do what i do for the SnapPrefs Module then i'd take in high note that before you flash the Xposed to download latest Snapchat 9.26
log in, once logged in then proceed with the rest and download XInstaller to downgrade from 9.26 to 9.17.1.0 to take full advantage of Snapprefs coolness.
upon note so far, after installing the modules, i rebooted my phone and it boots until it hits the LTE Spectrum screen and it has a light blueish pusling cycle and im stuck here.
maybe i can try another version. to be continued...
If you need any help feel free, i will try as best as i can, as i am a n00b but i have plenty of free time and have some decent knowledge about this.
After , i went back into recovery, i went to uninstall xposed thru the other flash file and its says optimizing 0 to 36 items and it booted so far, mayber after i flash the cache again and reinstall i should be fine but until further notice...tbc
Alright after a good amount of time i;ve finally concluded that the versions i;ve tired from xposed were the ones from the OFFICIAL thread and id always bootloop with that puling blue led and black screen, BUT with Wanams Xposed Version 80, and 79 they worked EXCEPT i can only get to the LTE SPecturm white boot screen and it does nothing from there BUT when i flash 80.1 it completely pulls through with the boot and completes but i had forgotten to mention that for some people on aanother thread that Xinstaller may leave you with bootloops and as it did for me thats exactly what happened. But i m still confused as to why the officials dont work by wanams does even after wiping cache,and dalvik cache multiple times and uninstall and reinstalling xposed.
Does yours still bootloop or did it finally pull through?
Hello, everyone!
The problem is that when booted, the phone only vibrates and turns off immediately. The screen never enables, LED for charging never enables. When connected to a charger, just vibrates. Tried to follow the steps here : installed the Soc driver, plugged the phone, tried to power it off - device manager recognized the phone for a couple of seconds and then it's gone.
Long story short: I tried to install official firmware upgrade using TWRP > Install > .zip. The installation was going on for a couple of minutes and then the screen blacked out. Since then, the phone does not boot.
So, I got bored of my Android 5 and decided to install a custom ROM, but I had to upgrade official firmware before that.
At first, I dove into how to install custom ROM tutorials, so I did the rooting first:
I downloaded a BootLoaderUnlocker program from the official Asus website and unlocked the BL. Then, I followed a tutorial for one-click-root, and succeded. Then I installed TWRP and flashed the Recovery to the latest available img for my phone and tried to install the Lineage OS 14.1 but got status 7 error, meaning something is incompatible.
This post states, that in order to install Lineage OS 14.1 I have to have a firmware at least MM 4.21.40.xx which is Android 6, so I went to the official Asus website and downloaded the Firmware upgrade. Since, I probably had the wrong BL at that point, I flashed the bootloader with TWRP for Z00A (Lollipop) 2.8.7.3 from here, which is the same website from which the post suggest to download a BL for MM (Android 6). I thought, since I currently have the Lolipop, should install the BL for that, just to be sure. Then I started the firmware upgrade, which rebooted the phone into the BL, I didn't think, and just pressed Normal Boot and the phone booted as usual in the old Android. Then I tried to initiate the instalation again but couldn't (it's supposed to auto-detect the file in the storage root), so I got an idea to just boot the Recovery, maybe it will continue. So, I did that, and the TWRP showed up (I forgot about it already and thought that the instalation would just continue), so I just pressed Install and chose the firmware upgrade zip manualy. The installation was going on for a couple of minutes and then the screen blacked out.
Since then, the phone does not boot. If I try to, it vibrates like it is going to boot, but then nothing happens (not even a logo).
I even tried to disconnect the battery: removed all the screws, removed the back panel and manually disconnected it. When I put it back the phone vibrated like it was going to boot, but nothing happened again.
P.S. I tried to boot into the Recovery, but that just does not work, and even did not work before the firmware upgrade (I googled, that I must press power and volume up and hold until the logo appears, but that doesn't happen).
upd: plugged into the charger, periodically shows the battery icon on the screen.
upd: I went to a service and the dude said I might have screwed up the `preLoader`, so some might say it's a disastah
https://forum.xda-developers.com/showthread.php?t=3452785
Sent from my ASUS_Z00AD using Tapatalk
Resolved
So, I went to a service and turns out I messed up the PreLoader, that boots the BootLoader. Sometimes this cannot be restored and costs a bunch of money to replace the memory block, but I got lucky and got the phone repaired.
P.S. Do not install official firmware with programs like TWRP, use only your manufacturer's SoftWare