Can't Get Into Recovery Mode - G Pad 8.3 Q&A, Help & Troubleshooting

Following the steps provided by Team Win on http://teamw.in/project/twrp2/213, I flashed the pre lokid recovery img that they provided, however I can't access it, I get "Secure booting Error! Cause: boot certification verify"
My firmware is V50020d(seems to be a troublemaker)
Command used
Steps Taken:
1. Enter adb shell
2. Get root using su
3. dd if=/sdcard/openrecovery-twrp-2.8.0.1-awifi.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
How I try to enter recovery mode:
Power + Down, Release Power, Press and Hold Up + Power, Release All Three, Press Power again and again

Here are some suggestions:
First, go here
1. If you don't have root, see the instructions in the above thread to run ioroot.
2. To flash TWRP, follow the instructions in Step 3 of the first post.
3. After that, you can update to one of the later versions of TWRP here. TWRP 2.7.1.0 seems stable, not sure about the latest one
3. After you do that, you will probably want to flash your boot environment back to 4.2.2 base to avoid problems with AOSP roms that you might want to install later. If you're only going to use stock-based roms, you probably won't want to do this. Look here for instructions for that here.

woody1 said:
Here are some suggestions:
First, go here
1. If you don't have root, see the instructions in the above thread to run ioroot.
2. To flash TWRP, follow the instructions in Step 3 of the first post.
3. After that, you can update to one of the later versions of TWRP here. TWRP 2.7.1.0 seems stable, not sure about the latest one
3. After you do that, you will probably want to flash your boot environment back to 4.2.2 base to avoid problems with AOSP roms that you might want to install later. If you're only going to use stock-based roms, you probably won't want to do this. Look here for instructions for that here.
Click to expand...
Click to collapse
The linked provided only works for 20a and 20b, do you have a mehtod that works for 20d?

Oh, you will need to edit the .bat file to change the reference to 20b to 20d. That should do it.

woody1 said:
Oh, you will need to edit the .bat file to change the reference to 20b to 20d. That should do it.
Click to expand...
Click to collapse
So now the message is "Device Unlock, so Boot Success" however still no recovery mode.
Am I better off going back to stock and trying again?

kidanime3d said:
So now the message is "Device Unlock, so Boot Success" however still no recovery mode.
Am I better off going back to stock and trying again?
Click to expand...
Click to collapse
I just did this recently, starting with a stock recovery of 20d and ending up with root and TWRP, so I know this should work. First, do you have root? When you ran the bat file to install TWRP, did it appear to run successfully?

kidanime3d said:
So now the message is "Device Unlock, so Boot Success" however still no recovery mode.
Am I better off going back to stock and trying again?
Click to expand...
Click to collapse
Getting in to the recovery also seems to have a problem if the device has a cable plugged in. I find that If I do an adb reboot recovery and then I unplug the device it will enter recovery. I believe this issue is fixed in later recoveries but the one that you should now have on your device will not properly boot recovery with a cable connected.

woody1 said:
I just did this recently, starting with a stock recovery of 20d and ending up with root and TWRP, so I know this should work. First, do you have root? When you ran the bat file to install TWRP, did it appear to run successfully?
Click to expand...
Click to collapse
Flash stock via the LG Support Tool, then did everything again and now running CM11 M10
Beer

muiriddin said:
Getting in to the recovery also seems to have a problem if the device has a cable plugged in. I find that If I do an adb reboot recovery and then I unplug the device it will enter recovery. I believe this issue is fixed in later recoveries but the one that you should now have on your device will not properly boot recovery with a cable connected.
Click to expand...
Click to collapse
You were right adb caused an issue for some reason.
Beer

Related

[RECOVERY](Updated 2-8-14) Official ClockworkMod Recovery 6.0.4.7

Here is the official ClockworkMod Recovery 6.0.4.7 non-touch images and touch images for the Nexus 10 enjoy :cyclops:!
Credit goes to Koush for releasing the official ClockworkMod Recovery images
These are safe to flash via fastboot.
Non-Touch
http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.4.7-manta.img
Touch
http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.4.7-manta.img
These can be flashed via fastboot using the following commands:
Code:
fastboot flash recovery /path/to/.img
fastboot reboot
Once again enjoy :victory:!
Note: To get the recovery to stick on reboot when Clockworkmod Recovery asks you if you want rename flash-recovery.sh or similar say "Yes", this will allow you to keep Clockworkmod Recovery installed permanently (Unless you flash a different recovery image) when you reboot your phone.
These reboot randomly as well. I've been trying to get TWRP to work, but TWRP is doing the same thing. Nothing in dmesg or last_kmsg to help either. :/
Also sdcard mount does not work nor anything reading from sdcard... only thing working is adb sideload.
Dees_Troy said:
These reboot randomly as well. I've been trying to get TWRP to work, but TWRP is doing the same thing. Nothing in dmesg or last_kmsg to help either. :/
Click to expand...
Click to collapse
zedomax said:
Also sdcard mount does not work nor anything reading from sdcard... only thing working is adb sideload.
Click to expand...
Click to collapse
Ok that is really bizare, both CWMR and TWRP are not working right and encountering similar issues regarding random reboots and mount issues. Whats odd is other people are experiencing random reboots during regular use even when not in recovery. I'm starting to believe that something Google might have to put out at fix for software wise may be needed.
So I take it no more "booting" the temporary ones posted before for the Nexus 4/Nexus 10? We can go ahead and "flash" these ones right?
zedomax said:
Also sdcard mount does not work nor anything reading from sdcard... only thing working is adb sideload.
Click to expand...
Click to collapse
i cant even get the sideload to work to get SU installed. Its driving me crazy. I keep trying it over and over again with the same result. As soon as i go over to recovery it unmounts from the computer then the sideload command fails due to computer losing connection with it. "Device not found"
Tried both CWM versions now .5 and .6
Not my first time around the block with rooting :-/
Used heimdall suite to flash my GS2.. any way to get it to push the .zip file for SU over to the phone? Push the recovery img then push the .zip maybe?
So I never even ended up trying to sideload anything, I just flashed the official recovery, then went immediately to recovery from fastboot, and once there I just flashed the SU zip and now I have root. Of course, CWMR doesn't work (i.e. if I use Quick Boot to boot to recovery it just takes me to the stock recovery, and if I try to go to recovery from fastboot manually, I just get the dead android w/red triangle).
Jayrod1980 said:
Finally got it... helped to just get the supersu on the root of the device. I used the fastboot commands to get to cwm touch and then I quickly installed it through the interface. I couldn't sideload. The device won't recognize adb when I'm in fastboot mode at all. I don't know what I was doing wrong in that instance, but using cwm briefly let me install supersu. Thanks for your help! Surprising this is so buggy considering it's a nexus... and it's not the nexus that's excluded from AOSP. Go figure!
Click to expand...
Click to collapse
I had to do it this way in order to get root. Finally.. been working on this for like 5ish hours now.. what a pain. Hopefully there will be an easier route for everyone else and a CWM that does not reboot in 20ish seconds soon. Good luck to everyone that goes this route.. it takes a lot of trial and error
snunez said:
Hopefully there will be an easier route for everyone else and a CWM that does not reboot in 20ish seconds soon.
Click to expand...
Click to collapse
I'm sure there will be, probably by the end of the weekend, if not sooner
I took apart CWM touch 6.0.1.6 and fixed reboot after 20 sec
I took the stock recovery.img from https://developers.google.com/android/nexus/images#mantarayjop40c, unpacked it, copied over the recovery binary from cwm touch 6.0.1.6 and resource files into the ramdisk... repacked it, and voila... no more reboots!
I'm sure Koush will eventually figure out what's going on with his automatic build system... my manually made recovery seems to work ok.
Please have at it (and feel free to thank me and report bugs), and if you want a tgz of my "unpacked" recovery I'll upload as well. You can also just unpack my uploaded file and see where the differences are yourself.
I've done recovery mods in the past for the G1, G2, and Gnexus when stuff like this happens when a device first comes out and recoveries have bugs in them.
Just "fastboot flash recovery $file.img" to try it out. I've got it running on my nexus 10 already and it hasn't rebooted (I succesfully installed CWM-SuperSU-v0.98.zip from http://forum.xda-developers.com/showthread.php?t=1538053 )
damien667 said:
I took the stock recovery.img from https://developers.google.com/android/nexus/images#mantarayjop40c, unpacked it, copied over the recovery binary from cwm touch 6.0.1.6 and resource files into the ramdisk... repacked it, and voila... no more reboots!
I'm sure Koush will eventually figure out what's going on with his automatic build system... my manually made recovery seems to work ok.
Please have at it (and feel free to thank me and report bugs), and if you want a tgz of my "unpacked" recovery I'll upload as well. You can also just unpack my uploaded file and see where the differences are yourself.
I've done recovery mods in the past for the G1, G2, and Gnexus when stuff like this happens when a device first comes out and recoveries have bugs in them.
Just "fastboot flash recovery $file.img" to try it out. I've got it running on my nexus 10 already and it hasn't rebooted (I succesfully installed CWM-SuperSU-v0.98.zip from http://forum.xda-developers.com/showthread.php?t=1538053 )
Click to expand...
Click to collapse
Great work! If you could post the unpacked version I'd appreciate it. I was trying to build a fixed version without success and would like to compare.
So,
Am I right in thinking...
cd to the adb tools folder where the sdk is saved.
I need to unlock the boot loader via fastboot oem.
Then copy your file to the same directory on my Mac
Then type in the command line you suggested with the correct filename?
After that I will be rooted
Swype'd at pace from my Galaxy S2
Here's my working tree
The-Kevster said:
Great work! If you could post the unpacked version I'd appreciate it. I was trying to build a fixed version without success and would like to compare.
Click to expand...
Click to collapse
I used this tool to unpack and re-pack the image: https://github.com/huaixzk/unpackbootimg.git
Attached is my current working tree as a tar.gz
Edit: the tool in that git repo is missing a step to gunzip | cpio the ramdisk... I made a shell script to do that for me when unpacking and repacking
Edit2: I added the wrapper scripts I made for posterity
damien667 said:
I took the stock recovery.img from https://developers.google.com/android/nexus/images#mantarayjop40c, unpacked it, copied over the recovery binary from cwm touch 6.0.1.6 and resource files into the ramdisk... repacked it, and voila... no more reboots!
I'm sure Koush will eventually figure out what's going on with his automatic build system... my manually made recovery seems to work ok.
Please have at it (and feel free to thank me and report bugs), and if you want a tgz of my "unpacked" recovery I'll upload as well. You can also just unpack my uploaded file and see where the differences are yourself.
I've done recovery mods in the past for the G1, G2, and Gnexus when stuff like this happens when a device first comes out and recoveries have bugs in them.
Just "fastboot flash recovery $file.img" to try it out. I've got it running on my nexus 10 already and it hasn't rebooted (I succesfully installed CWM-SuperSU-v0.98.zip from http://forum.xda-developers.com/showthread.php?t=1538053 )
Click to expand...
Click to collapse
Wow! It worked perfectly... You are a genius. No more random reboots in recovery! Thank you. I have one question... Are you able to do the same for TWRP for the Nexus 10, if possible?
Underworld79 said:
Wow! It worked perfectly... You are a genius. No more random reboots in recovery! Thank you. I have one question... Are you able to do the same for TWRP for the Nexus 10, if possible?
Click to expand...
Click to collapse
I could probably do it to TWRP as well (later today, it's sleep time for me)... however, I don't know where the latest nexus 10 recovery image is from them (considering it's not in this forum).
so can I permanently flash this now instead of fastboot?
damien667 said:
I took the stock recovery.img from https://developers.google.com/android/nexus/images#mantarayjop40c, unpacked it, copied over the recovery binary from cwm touch 6.0.1.6 and resource files into the ramdisk... repacked it, and voila... no more reboots!
I'm sure Koush will eventually figure out what's going on with his automatic build system... my manually made recovery seems to work ok.
Please have at it (and feel free to thank me and report bugs), and if you want a tgz of my "unpacked" recovery I'll upload as well. You can also just unpack my uploaded file and see where the differences are yourself.
I've done recovery mods in the past for the G1, G2, and Gnexus when stuff like this happens when a device first comes out and recoveries have bugs in them.
Just "fastboot flash recovery $file.img" to try it out. I've got it running on my nexus 10 already and it hasn't rebooted (I succesfully installed CWM-SuperSU-v0.98.zip from http://forum.xda-developers.com/showthread.php?t=1538053 )
Click to expand...
Click to collapse
Well I just flashed your version of the recovery, and after doing "fastboot-mac reboot" and rebooting, I tried rebooting to recovery via adb, and unfortunately it brought me back to the dead android red triangle screen. In fact, I can't even get to CWMR at all. Anyone else??
And to be clear, I have successfully rooted, so at this point I'm just trying to get a functioning version of CWMR on the tablet, if possible.
Did you try holding power and pressing Vol+ when booting recovery? That's how you enter stock recovery.
Randomwalker said:
Did you try holding power and pressing Vol+ when booting recovery? That's how you enter stock recovery.
Click to expand...
Click to collapse
Yeah I know that, but I'm not trying to enter stock recovery, I'm trying to enter the custom recovery (which is the supposed "stable" one by damien) which I've installed. And it only let me access CWMR immediately after flashing it. However anytime afterwards I simply cannot access it again:
1) tried "adb reboot recovery" and it brings me to the dead android w/red triangle
2) tried getting to recovery via the Quick Boot app, and the same thing happens
3) tried getting to recovery via the normal holding buttons down to get to bootloader, then going to recovery manually from there, and a no-go as well.
In the end, all that happens is I have to toggle the buttons once I get to the dead android screen, and the menu for the stock recovery appears, which allows me to reboot. But as for CWMR, it is nowhere to be found. WTF.
Did you reboot after installing CWM? If so, did you remove install.sh, that will restore the stock recovery?

[Q] Root for Sony T2 ultra Model #D316

I have looked all over and see some threads overlapping other threads, however I am not finding anything for the D5316 Model. I am running Android 4.4.2 Build Number 19.1.A.0.486 The kernel version is from Thu Jul 17 10:07:21 2014. I would like to root and get recovery on it to try a faster rom and get rid of the Sony bloatware. If you have been successful or I missed a link on how to do that please point me in the correct direction...... Thank you in advance.
Kinz1980 said:
I have looked all over and see some threads overlapping other threads, however I am not finding anything for the D5316 Model. I am running Android 4.4.2 Build Number 19.1.A.0.486 The kernel version is from Thu Jul 17 10:07:21 2014. I would like to root and get recovery on it to try a faster rom and get rid of the Sony bloatware. If you have been successful or I missed a link on how to do that please point me in the correct direction...... Thank you in advance.
Click to expand...
Click to collapse
you can try all root methods available i.e giefroot, rootkitxperia, easy root tool, etc. find them in the cross development section
Chena_22 said:
you can try all root methods available i.e giefroot, rootkitxperia, easy root tool, etc. find them in the cross development section
Click to expand...
Click to collapse
EDIT: Apparently, it's working now. All I had to do was reflash the ftf file in flashtool and it was able to keep the custom recovery and boot the phone past it....go figure.
Thanks for posting this, I am having some trouble myself and it's really frustrating. I am able to flash both CWM and TWRP. I am even able to boot into these recoveries but I cannot get the damn thing to boot past it. Pretty sure it's the kernel but I cannot find a place that will tell me step by step as to getting custom recovery on the model of this phone. I am still on 4.4.2. Can you please point me in the right direction?
bor3d2damax said:
EDIT: Apparently, it's working now. All I had to do was reflash the ftf file in flashtool and it was able to keep the custom recovery and boot the phone past it....go figure.
Thanks for posting this, I am having some trouble myself and it's really frustrating. I am able to flash both CWM and TWRP. I am even able to boot into these recoveries but I cannot get the damn thing to boot past it. Pretty sure it's the kernel but I cannot find a place that will tell me step by step as to getting custom recovery on the model of this phone. I am still on 4.4.2. Can you please point me in the right direction?
Click to expand...
Click to collapse
So you were able to root your d5316?
Kinz1980 said:
So you were able to root your d5316?
Click to expand...
Click to collapse
Yes I was! I can get you the instructions if you want.
bor3d2damax said:
Yes I was! I can get you the instructions if you want.
Click to expand...
Click to collapse
Yes, please do! Also did you get recovery figured out? I am wanting to use xposed.
Kinz1980 said:
Yes, please do! Also did you get recovery figured out? I am wanting to use xposed.
Click to expand...
Click to collapse
Yes,
Basically what you have to do is download Dual Recovery and put it on your SD card or internal storage on the phone. Download Supersu 2.40 and do the same thing. Then go to the CWM recovery thread and download that. Follow the instructions there. Once you finish following the instructions just boot into CWM recovery, then flash Dual Recovery. Reboot the phone and wait until you see the green light. Press the down key once you see the green light. It should take you into TWRP. After that flash Super Su and then you reboot and let it boot all the way, done. Make sure you are bootloader unlocked and have working ADB AND FASTBOOT on your PC
bor3d2damax said:
Yes,
Basically what you have to do is download Dual Recovery and put it on your SD card or internal storage on the phone. Download Supersu 2.40 and do the same thing. Then go to the CWM recovery thread and download that. Follow the instructions there. Once you finish following the instructions just boot into CWM recovery, then flash Dual Recovery. Reboot the phone and wait until you see the green light. Press the down key once you see the green light. It should take you into TWRP. After that flash Super Su and then you reboot and let it boot all the way, done. Make sure you are bootloader unlocked and have working ADB AND FASTBOOT on your PC
Click to expand...
Click to collapse
Let's back up for a second.....
Give me a breakdown one more time from the very beginning.
1.unlock the bootloader
2. Download "dual recovery"and place on sd card
3. Download superuser and place on sd card
4. Install cwm recovery
5. Flash the dual recovery.....why? Is there something wrong with cwm?
6.Flash superuser
At what point is the phone rooted? Does flashing SU do that? I have used tools in the past on other phones. This is my first Sony phone.
If you care to, or the time to...could you please paste the links to each step (assuming I have them all correct or I am not missing something)
I really appreciate you helping this much I was ready to give up on this phone, cause I couldn't get any help! :what::banghead:
just the topic I was looking for!
mind if I follow this? I just bought this phone yesterday. Looking for a way to get Lollipop on it.
I was hoping to get a reply by now. Which model# do you have
I just flashed FXP ASOP 2/23 after I was able to get 2/08 running on the device and now the device won't boot past the android logo. I can get it flashboot mode and rewrite the 3 imgs (boot, system, and user data) however it still won't boot.
Any Ideas?
hoonu said:
I just flashed FXP ASOP 2/23 after I was able to get 2/08 running on the device and now the device won't boot past the android logo. I can get it flashboot mode and rewrite the 3 imgs (boot, system, and user data) however it still won't boot.
Any Ideas?
Click to expand...
Click to collapse
I am just trying to get root and recovery
I was able to get root by doing the following.
Flash the cwm boot.img. You will not be able to boot android but you will be able to boot to recovery.
Flash the dual recovery from cwm. Go ahead and flash supersu zip as well.
Reboot. Wait till you see the green light (not pink) flash and press the volume down button to boot to twrp or volume up to boot phils recovery.
I used twrp. Once in TWRP, I flashed the rooted stock firmware (mainly to restore a fully working boot.img), and reflashed dual recovery from twrp. Also flash the newest supersu zip.
Maybe a easier way, but worked for me.

Unable to mount partitions after flashing TWRP on Nexus 7 (2013, WiFi, flo)

I just bought this device a week and I haven't even rooted I wanted to install Cyanogenmode and follow through the instructions and flashed TWRP through fastboot commands from Windows7 using Minimal ADB and Fastboot [8-28-15].
I got the TWRP recovery but I am not sure what have I done wrong, when I am in the TWRP recovery, it does not show any partitions so I am unable to install any ROM on it.
I have also tried to use this thread: http://forum.xda-developers.com/nexus-7-2013/nexus-7-2013-qa/mount-recovery-t3064562 when I flash the given recovery from fastboot commands from this thread, the recovery get stuck with bootloop. So then I restored it back to the original TWRP 2.8.7.0.
So at this point now I can only access bootloader and the recovery which does not show partitions.
At this point Is it possible for me to go back to the stock ROM somehow? Please advice. Otherwise I might be able to return it because I have only bought it few days ago.
SOLVED: To get TWRP to work, I flashed the original stock ROM from here https://developers.google.com/androi...s/images?hl=en using adb. I then flashed this TWRP multirom https://s.basketbuild.com/filedl/dev...o_20150630.img
This allowed TWRP to work.
Thanks to Batfink33 and lynnux
You can follow this guide to flash the newest factory image: http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/. You should just download the latest factory image from: https://developers.google.com/android/nexus/images?hl=en the one in the guide is outdated.
Join the club, I did the same thing you did with the same results(even flashing the multirom twrp after flashing the regular one, and getting the recovery bootloop). I happened to find the same instructions theminikiller posted above after pulling my hair out trying to figure out what went wrong.
This post http://forum.xda-developers.com/showpost.php?p=62275723&postcount=558 explains what's going on. If you do the above and then flash the multirom twrp it should work fine, it did for me. I also reformatted system in adb after erasing everything, not sure if that was necessary or not.
lynnux said:
Join the club, I did the same thing you did with the same results(even flashing the multirom twrp after flashing the regular one, and getting the recovery bootloop). I happened to find the same instructions theminikiller posted above after pulling my hair out trying to figure out what went wrong.
This post http://forum.xda-developers.com/showpost.php?p=62275723&postcount=558 explains what's going on. If you do the above and then flash the multirom twrp it should work fine, it did for me. I also reformatted system in adb after erasing everything, not sure if that was necessary or not.
Click to expand...
Click to collapse
Did the multirom TWRP work for you? I get a bootloop in TWRP when I flash that multirom TWRP posted.
Batfink33 said:
Did the multirom TWRP work for you? I get a bootloop in TWRP when I flash that multirom TWRP posted.
Click to expand...
Click to collapse
It worked for me, but only after erasing everything via adb and reflashing all the stock images. I got the bootloop when I flashed the regular twrp first, then the multirom twrp. Also, I'm using the most recent multirom twrp from June (I believe).
lynnux said:
It worked for me, but only after erasing everything via adb and reflashing all the stock images. I got the bootloop when I flashed the regular twrp first, then the multirom twrp. Also, I'm using the most recent multirom twrp from June (I believe).
Click to expand...
Click to collapse
Yay, it works for me now. I had to install the stock ROM using adb then flash the multirom TWRP. Thanks!
Batfink33 said:
Yay, it works for me now. I had to install the stock ROM using adb then flash the multirom TWRP. Thanks!
Click to expand...
Click to collapse
Thanks for your replies here. Could you please give me the link to the multiroom Recovery that had worked for you? Also did you installed Cynageon mode after getting the mutliroom TWRP working? Please advice
a4abbas said:
Thanks for your replies here. Could you please give me the link to the multiroom Recovery that had worked for you? Also did you installed Cynageon mode after getting the mutliroom TWRP working? Please advice
Click to expand...
Click to collapse
To get TWRP to work, I flashed the original stock ROM from here https://developers.google.com/android/nexus/images?hl=en using adb. I then flashed this TWRP multirom https://s.basketbuild.com/filedl/de...//multirom/flo/TWRP_multirom_flo_20150630.img
This allowed TWRP to work.
Batfink33 said:
To get TWRP to work, I flashed the original stock ROM from here https://developers.google.com/android/nexus/images?hl=en using adb. I then flashed this TWRP multirom https://s.basketbuild.com/filedl/de...//multirom/flo/TWRP_multirom_flo_20150630.img
This allowed TWRP to work.
Click to expand...
Click to collapse
Is it required to enable Developer options at some point of flashing it successfully? I am in China and here the google is blocked i bought this tablet and I can not get through the first screen that ask me to connect the wifi (no option to skip it unless i connect to wifi) then after loading it gets error message that it is failed to connect to internet. So just understand that I can not goto the device options right now. So is it possible to flash cynagonmode rom without enabling developer option. Please advice
a4abbas said:
Is it required to enable Developer options at some point of flashing it successfully? I am in China and here the google is blocked i bought this tablet and I can not get through the first screen that ask me to connect the wifi (no option to skip it unless i connect to wifi) then after loading it gets error message that it is failed to connect to internet. So just understand that I can not goto the device options right now. So is it possible to flash cynagonmode rom without enabling developer option. Please advice
Click to expand...
Click to collapse
No, it's not required. Just turn off your device. Then to boot into the bootloader hold volume down + power button until it's done booting. From there you can follow other guides to unlock the bootloader and installing custom recovery and Rom's.
theminikiller said:
No, it's not required. Just turn off your device. Then to boot into the bootloader hold volume down + power button until it's done booting. From there you can follow other guides to unlock the bootloader and installing custom recovery and Rom's.
Click to expand...
Click to collapse
I have tried to do it. But the device is not being recognized with the ADB tools on my PC. Any ideas? Could it be because of the USB debugging option?
a4abbas said:
I have tried to do it. But the device is not being recognized with the ADB tools on my PC. Any ideas? Could it be because of the USB debugging option?
Click to expand...
Click to collapse
When you are in the bootloader it doesn't matter if you have USB debugging enabled or not. It could be a problem with your driver's.
theminikiller said:
When you are in the bootloader it doesn't matter if you have USB debugging enabled or not. It could be a problem with your driver's.
Click to expand...
Click to collapse
You must be right, it make sense.

NEED HELP

I have a brand new Pixel XL from Verizon that I received today and was successful in unlocking. However, I tried to root and now I am stuck on bootloop. I cannot post in DEVELOPMENT because I haven't posted here in years (haven't had ANDROID in a while). Can anyone help? I am able to access via fastboot (I believe) but I must be flashing the wrong images. I don't want to brick this nice new day-old device. I have been at it for 5 hours via research on my own, but now I am looking for someone that can help me via P.M. or what it may take. I really want to get back to enjoying this device! Thanks in advance!
bdsuser said:
I have a brand new Pixel XL from Verizon that I received today and was successful in unlocking. However, I tried to root and now I am stuck on bootloop. I cannot post in DEVELOPMENT because I haven't posted here in years (haven't had ANDROID in a while). Can anyone help? I am able to access via fastboot (I believe) but I must be flashing the wrong images. I don't want to brick this nice new day-old device. I have been at it for 5 hours via research on my own, but now I am looking for someone that can help me via P.M. or what it may take. I really want to get back to enjoying this device! Thanks in advance!
Click to expand...
Click to collapse
Read the third post in the thread below to get set up and back to stock. Then we will work on root. If you tried to root and you bootlooped it then you used the wrong​ SU.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242
1. Download a ROM. A stock version is probably in the forums somewhere if that's what you want.
2. Download TWRP image and zip from the TWRP thread.
3. Download SuperSU from the SuperSU thread.
4. Download a vendor image. There's no "official" vendor image thread AFAIK, but you can grab one from the Pure Nexus rom thread. NMF26V is compatible with all 7.1.1 ROMs & stock.
Now you have two options:
Fast: Put the ROM, TWRP(zip only), SuperSU and vendor image on USB flash drive, then connect the USB 3 to USB C adapter to your flash drive. Don't connect it to the phone yet. An external HDD/SSD should also work if that's all you've got.
Slow: While in TWRP(Instructions below) push the ROM, TWRP(zip only), SuperSU and vendor image files to your phone through ADB with "adb push C:\file_path\ /sdcard/" sans quotes. You will need to do this for each file, or alternatively push a folder containing the four files. adb file transfer is very slow.
5. Boot your phone to the bootloader, and connect it to your computer. This can be achieved by holding volume down and power from an off state.
Note: If your device is still bootlooping you won't be able to get to the bootloader. Hold volume up and power until the device shuts off to get out of the bootloop temporarily, then boot to bootloader.
6. In a command window, "fastboot boot twrp.img"
7. Connect your flash drive to your phone if you chose that option, or push the files through adb if you chose that option
8. Flash TWRP zip, ROM and vendor image. STAY IN TWRP
9. Return to TWRP's home screen > advanced > file manager. Scroll down until you see 'fstab.marlin'(in the root '/' directory). Tap on 'fstab.marlin' and delete it. Skipping this step means SuperSU won't install.
10. Flash SuperSU zip, reboot to system and you're done.
SDK
TonikJDK said:
Read the third post in the thread below to get set up and back to stock. Then we will work on root. If you tried to root and you bootlooped it then you used the wrong​ SU.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242
Click to expand...
Click to collapse
Just thought I'd update you...And I know I sound like I have no idea what I'm doing but traditionally I've never had issues like this But I am trying to get ADB to show the flash-all command. The one I have installed doesn't show that feature so I can't follow the tutorial. If you have a direct link to what I may be missing I would appreciate it otherwise I will update you once I figure it out.
bdsuser said:
Just thought I'd update you...And I know I sound like I have no idea what I'm doing but traditionally I've never had issues like this But I am trying to get ADB to show the flash-all command. The one I have installed doesn't show that feature so I can't follow the tutorial. If you have a direct link to what I may be missing I would appreciate it otherwise I will update you once I figure it out.
Click to expand...
Click to collapse
The link to the proper adb and fastboot are in the post i pointed you to.
Help with root and TWRP
TonikJDK said:
The link to the proper adb and fastboot are in the post i pointed you to.
Click to expand...
Click to collapse
Thanks for your assistance. I now have root installed and I think I'm good except for one thing. I keep thinking TWRP is installed but for some reason when I reboot to bootloader, then select reboot recovery mode, it takes me to android recovery. I am used to recovery taking me to TWRP. I know TWRP works but I feel like I'm temporarily flashing it each time or something. I even installed the twrp app and I see I can flash zips that way, etc, but I wanted to know if you knew how to make the phone boot to TWRP in recovery? Or is that necessary?
bdsuser said:
Thanks for your assistance. I now have root installed and I think I'm good except for one thing. I keep thinking TWRP is installed but for some reason when I reboot to bootloader, then select reboot recovery mode, it takes me to android recovery. I am used to recovery taking me to TWRP. I know TWRP works but I feel like I'm temporarily flashing it each time or something. I even installed the twrp app and I see I can flash zips that way, etc, but I wanted to know if you knew how to make the phone boot to TWRP in recovery? Or is that necessary?
Click to expand...
Click to collapse
I dont do it that way on this phone. TWRP and SU are modifying the same parts of the phone, and there are cases where it could conflict. Rare, not a big deal, but since i don't need TWRP installed i don't.
To install it ypu first boot to it.
Fastboot boot twrpFilename.
Then from within TWRP you install the TWRP zip.
Make sure it is TWRP RC1
All set
Thanks again for your help. I am running pure ROM as I mentioned and I seem to like it. Do you K or if Franco works with Pure or do you have a suggestion on a good rom/kernel? Is there anything else that you can suggest I should be using with the new phone? I remember there used to be tools that you could install that allowed you to customize the system even further but the name escapes me. . Is there anything like that or even a theme tool which is a must have when you are rooted and running custom roms? No big deal if not. Very happy with where I stand now. Really appreciate you getting me back up and running!
You are most welcome. I don't ROM so I don't know what kernels work with what roms for sure. But my understanding is that they are all pretty universal. I run stock with Franco.
Other than that i dont mod much. Ad blocker, black themes and a few adjustments to Franco.
TonikJDK said:
You are most welcome. I don't ROM so I don't know what kernels work with what roms for sure. But my understanding is that they are all pretty universal. I run stock with Franco.
Other than that i dont mod much. Ad blocker, black themes and a few adjustments to Franco.
Click to expand...
Click to collapse
Perfect! Thanks yet again. Have a great remainder of the day!
bdsuser said:
Thanks again for your help. I am running pure ROM as I mentioned and I seem to like it. Do you K or if Franco works with Pure or do you have a suggestion on a good rom/kernel? Is there anything else that you can suggest I should be using with the new phone? I remember there used to be tools that you could install that allowed you to customize the system even further but the name escapes me. . Is there anything like that or even a theme tool which is a must have when you are rooted and running custom roms? No big deal if not. Very happy with where I stand now. Really appreciate you getting me back up and running!
Click to expand...
Click to collapse
Im running pure and elementalx with excellent results.
?Tapped from my pure pixelXl?
have you ever seen an issue where the phone boots to twrp even though everything was working fine? It starts happening if I do a restart. Then no matter what it boots into TWRP unless I wipe again? I believe it's happening after I flash root but I'm going out of my mind with trial and error. Any help would be appreciated.
bdsuser said:
have you ever seen an issue where the phone boots to twrp even though everything was working fine? It starts happening if I do a restart. Then no matter what it boots into TWRP unless I wipe again? I believe it's happening after I flash root but I'm going out of my mind with trial and error. Any help would be appreciated.
Click to expand...
Click to collapse
HELLO!!! I understand any frustrations you may be having, as the pixel devices have changed a good bit for us as far as development. Anyways. I'm just going to throw some knowledge out there, then proceed to help get you up and running!
You couldn't post in the development section because of your post count, but even if you could, it would have been in the wrong section and it would have been removed, or moved to the questions section.
Also, I see someone has pointed it out earlier, but I'll say it again just to make sure everything is clear. The command you were running "fastboot boot TWRP.img" only boots TWRP temporarily. You are suppose to have two files, one IMG file and one zip file. You boot the IMG file, then once you're in TWRP, you flash the zip file, then reboot to recovery and you will have installed TWRP properly.
With root, flashing wrong files or using the outdated root method will cause boot loops. The correct way to root (again already been said) is the get TWRP up and running, delete the fstab file (see earlier post) then flash SuperSU and reboot. Just throwing this out there Incase someone comes across it, if you manage to boot loop your device due to to rooting, you can fastboot flash franco's kernel and it will fix the bootloop (,but you won't have root) this isn't the correct way to fix it, but it will get you back up and running without downloading the large factory image.
***About to edit this post to continue giving more info***
Here is a correct guide and good template to get you running.
start by flashing a clean factory image, then let it boot and get it set up.
Reboot to fastboot, fastboot boot TWRP IMG then flash TWRP zip using the latest versions (RC1 is latest, pm me for more info).
Reboot the phone to recovery to ensure TWRP stuck.
Go-to advanced, file manager in TWRP and find the fstab.marlin file and delete.
Then you can go ahead and flash the latest SuperSU (I use 2.79 sr3) and when it's done reboot to system and verify root.
After rooting you can go ahead and flash a kernel if you want, I use elemental which you can flash in TWRP, but see the kernel instructions prior to flashing.
Reboot and you have a nice stock ROM with root and kernel.
For flashing Roms, kind of follow the same template, most Roms require you to flash part of or the whole latest factory image.
If your on a clean install, go ahead and install TWRP as mentioned above.
Then use TWRP to install whatever ROM you want per ROM developer instructions.
Side note, some Roms replace the TWRP with cwm or stock recovery, so it's always nice to flash the TWRP zip after flashing a ROM.
After flashing ROM, boot to system to make sure all is well, then boot back to recovery and follow instructions above for root/kernel.
As far as the problem you're having now, it usually comes from flashing outdated SuperSU images. Do a search for 2.79 sr3 and use it to root (pm me if you need help)
You might have to start clean one more time, And flash factory image.
noidea24 said:
HELLO!!! I understand any frustrations you may be having, as the pixel devices have changed a good bit for us as far as development. Anyways. I'm just going to throw some knowledge out there, then proceed to help get you up and running!
You couldn't post in the development section because of your post count, but even if you could, it would have been in the wrong section and it would have been removed, or moved to the questions section.
Also, I see someone has pointed it out earlier, but I'll say it again just to make sure everything is clear. The command you were running "fastboot boot TWRP.img" only boots TWRP temporarily. You are suppose to have two files, one IMG file and one zip file. You boot the IMG file, then once you're in TWRP, you flash the zip file, then reboot to recovery and you will have installed TWRP properly.
With root, flashing wrong files or using the outdated root method will cause boot loops. The correct way to root (again already been said) is the get TWRP up and running, delete the fstab file (see earlier post) then flash SuperSU and reboot. Just throwing this out there Incase someone comes across it, if you manage to boot loop your device due to to rooting, you can fastboot flash franco's kernel and it will fix the bootloop (,but you won't have root) this isn't the correct way to fix it, but it will get you back up and running without downloading the large factory image.
***About to edit this post to continue giving more info***
Here is a correct guide and good template to get you running.
start by flashing a clean factory image, then let it boot and get it set up.
Reboot to fastboot, fastboot boot TWRP IMG then flash TWRP zip using the latest versions (RC1 is latest, pm me for more info).
Reboot the phone to recovery to ensure TWRP stuck.
Go-to advanced, file manager in TWRP and find the fstab.marlin file and delete.
Then you can go ahead and flash the latest SuperSU (I use 2.79 sr3) and when it's done reboot to system and verify root.
After rooting you can go ahead and flash a kernel if you want, I use elemental which you can flash in TWRP, but see the kernel instructions prior to flashing.
Reboot and you have a nice stock ROM with root and kernel.
For flashing Roms, kind of follow the same template, most Roms require you to flash part of or the whole latest factory image.
If your on a clean install, go ahead and install TWRP as mentioned above.
Then use TWRP to install whatever ROM you want per ROM developer instructions.
Side note, some Roms replace the TWRP with cwm or stock recovery, so it's always nice to flash the TWRP zip after flashing a ROM.
After flashing ROM, boot to system to make sure all is well, then boot back to recovery and follow instructions above for root/kernel.
As far as the problem you're having now, it usually comes from flashing outdated SuperSU images. Do a search for 2.79 sr3 and use it to root (pm me if you need help)
You might have to start clean one more time, And flash factory image.
Click to expand...
Click to collapse
There is absolutely no need to delete the fstab file anymore. That only needed to be done when TWRP was still alpha 2, and almost three versions of su earlier.
ALL roms replace TWRP with stock recovery unless you are using lineage then you will get Cyanogenmod recovery, so reflashing TWRP before booting into system is a must.
If you are flashing root and or custome kernel and end up in a bootloop, flashing the stock boot.img to both slots via:
'fastboot flash --slot _a boot boot.img'
'fastboot flash --slot _b boot boot.Img'
will fix the issue and you will be able to boot up just fine. Again you will have to reboot into TWRP from the bootloader and reflash the zip. When you are done flashing the boot.img's you might as well just
'Fastboot boot TWRP-file.img'
Then install the zip!

[Q]E988 Boot certification verify

I have kitkat 4.2.2 stockbase, rooted, trying to install cwm but stuck in the secure booting error boot certification verify.
Previously i installed rom manager app and flash the cwm from the app. After reboot to recovery, only stock recovery that showed, then i reboot to system, install freegee in order to flash the cwm but fail as freegee doesnt support gpro kitkat.
After that i install gpro kitkat recovery and flash the cwm from the app, success, reboot to recovery but stuck on the error.
I uninstalled rom manager and freegee, but still no luck to get the flashed cwm recovery,stuck in secure booting error.
Any suggestion or thread reference? Why is very difficult to install custom rom on this device?i plan to install carbon rom :crying:
Thank you in advance.
hotmatua.parulian said:
I have kitkat 4.2.2 stockbase, rooted, trying to install cwm but stuck in the secure booting error boot certification verify.
Previously i installed rom manager app and flash the cwm from the app. After reboot to recovery, only stock recovery that showed, then i reboot to system, install freegee in order to flash the cwm but fail as freegee doesnt support gpro kitkat.
After that i install gpro kitkat recovery and flash the cwm from the app, success, reboot to recovery but stuck on the error.
I uninstalled rom manager and freegee, but still no luck to get the flashed cwm recovery,stuck in secure booting error.
Any suggestion or thread reference? Why is very difficult to install custom rom on this device?i plan to install carbon rom :crying:
Thank you in advance.
Click to expand...
Click to collapse
Start from 4.1.2 stock, root, use freegee to bypass lockdown, flash latest TWRP then flash Lollipop ROMs... There is info about everything on the forums.
ShadySquirrel said:
Start from 4.1.2 stock, root, use freegee to bypass lockdown, flash latest TWRP then flash Lollipop ROMs... There is info about everything on the forums.
Click to expand...
Click to collapse
Thank you very much Shady.. Please be kindly to review steps that i should execute when flashing to Carbon Lollipop with regards to my current state (rooted 4.4.2. stock Kitkat):
Prerequisite:
- LG Flash Tool 2014 installed in PC
- LG United Mobile Driver (i use v3.11.3) installed in PC
- Stock firmware E98810e_00.kdz (Indonesia Jellybean) -- Jellybean stock base is required to cater modem/wakelock issue
- Stock firmware E98820c_00.kdz (Indonesia Kitkat)
- ROM Manager (for current state backup/restore)
- Freegee (to cater LG security issue after success flash)
- Towelroot (to root device after success flash)
- TWRP (for recovery tool after success flash)
- Downloaded ZeKrnl 1.7 Build 11/28 - https://forum.xda-developers.com/optimus-g-pro/development/rom-e980-ze-krnl-1-6-t3255975
- Downloaded ZeKrnl 1.6 - https://forum.xda-developers.com/optimus-g-pro/development/rom-e980-ze-krnl-1-6-t3255975/page4 (to cater camera issue after flashed to Carbon)
1. Flash CWM via ROM Manager
2 Execute Backup Current ROM to sd card via ROM Manager and save copy to PC
3. Backup manual for files, apks, contacts to sd card and save copy to PC
4. Copy ZeKrnl 1.7 zip & ZeKrnl 1.6 zip to sd card
5. Turn off phone, plug usb cable to phone
6. Press & hold Volume keys (Up + Down) then plug the other end of usb into PC to until download mode showned
7. Run LG Flash Tool with administrator privilege
8. Flash E98810e firmware into the device till success
(After Success Flash to Andro 4.1.2 JB):
9. Install towelroot and root the device
10. Install freegee to cater LG security issue
11. Install latest TWRP
12. Reboot into recovery mode
13. wipe system, data, cache, dalvik cache
14. flash ZeKrnl 1.7
--Camera issue
debug.composition. type=dyn --> debug.composition. type=gpu using build prop editor and/or flash ZeKrnl 1.6 kernell
https://forum.xda-developers.com/optimus-g-pro/development/rom-e980-ze-krnl-1-6-t3255975/page8
--Deep Sleep issue
https://forum.xda-developers.com/optimus-g-pro/development/rom-e980-ze-krnl-1-6-t3255975/page10
-- SD Card issue
https://forum.xda-developers.com/optimus-g-pro/development/rom-e980-ze-krnl-1-6-t3255975/page12
-- Kernel parameter tuning sampel
https://forum.xda-developers.com/optimus-g-pro/development/rom-e980-ze-krnl-1-6-t3255975/page14
Btw looks like you are the only person that still active in this thread...really appreciate it...thank you very much
You're complicating it too much, to be honest
Just do it this way:
1. flash stock 4.1.2 and keep it that way
2. root, install Freegee, install initial recovery (twrp, cwm, doesn't mater), update it to TWRP from forums (2.8 version is preferred)
3. you're ready to flash create stock backup and flash roms.
If I remember, all those changes are already implemented in both SlimLP and Carbon. Slim has newer kernel and gpu drivers, and that's it.
So you are saying i just flash the rom as is without any further change?Noted shady...i will inform you the result
ShadySquirrel said:
You're complicating it too much, to be honest
Just do it this way:
1. flash stock 4.1.2 and keep it that way
2. root, install Freegee, install initial recovery (twrp, cwm, doesn't mater), update it to TWRP from forums (2.8 version is preferred)
3. you're ready to flash create stock backup and flash roms.
If I remember, all those changes are already implemented in both SlimLP and Carbon. Slim has newer kernel and gpu drivers, and that's it.
Click to expand...
Click to collapse
Ive tried your suggestion with the following result:
a. Flash to stock 4.1.2 (v10e) : success but then the master file i downloaded is gone
b. Root, install freegee, initial recovery: success
c. Update to twrp 2.8 using twrp manager: success
d. Flash to Carbon: fail, canot enter recovery mode with message secure booting error,boot certification verify
So i just rollback to kitkat stock
hotmatua.parulian said:
Ive tried your suggestion with the following result:
a. Flash to stock 4.1.2 (v10e) : success but then the master file i downloaded is gone
b. Root, install freegee, initial recovery: success
c. Update to twrp 2.8 using twrp manager: success
d. Flash to Carbon: fail, canot enter recovery mode with message secure booting error,boot certification verify
So i just rollback to kitkat stock
Click to expand...
Click to collapse
So, you can't boot TWRP at all? It seems that TWRP you installed isn't lokified. Are you sure you've installed TWRP 2.8? I remember flashing it directly via flashify on my device and it worked.. Also, check TWRP thread for lokified zip, I think someone posted that.
Edit: you see now why almost everyone abandoned this device
ShadySquirrel said:
So, you can't boot TWRP at all? It seems that TWRP you installed isn't lokified. Are you sure you've installed TWRP 2.8? I remember flashing it directly via flashify on my device and it worked.. Also, check TWRP thread for lokified zip, I think someone posted that.
Edit: you see now why almost everyone abandoned this device
Click to expand...
Click to collapse
Yes, i cant boot twrp, i used twrp manager apk,i think its not lokified.
hotmatua.parulian said:
Yes, i cant boot twrp, i used twrp manager apk,i think its not lokified.
Click to expand...
Click to collapse
After installing freegee's twrp, reboot to recovery. Then, it might be OK.
After that, reboot system and use flashify, the free version will do.
You can either choose to download the file or chose from your internal / external memory.
I'm using the latest version TWRP 3.0.2.0.
If it doesn't work at first, go back to start and try again...
g0at1 said:
After installing freegee's twrp, reboot to recovery. Then, it might be OK.
After that, reboot system and use flashify, the free version will do.
You can either choose to download the file or chose from your internal / external memory.
I'm using the latest version TWRP 3.0.2.0.
If it doesn't work at first, go back to start and try again...
Click to expand...
Click to collapse
Thanks for respond, i have to download the jb stockbase again as the file used for lg flash tool is missing, looks like flashtool keep it somewhere...btw, when i use flashtool to flash the jb stock (offline mode), it.doesnt complete 100%, at 99% device was successfully boot and normal but state in flashtool screen is 99% and message to.retry is showned up.
Fyi, after flashed to jb, i cant execute fastboot flash command, the result is waiting for any device, but adb devices command return expected result. Enable debugging setting is already checked also.
Quiet interesting this device...salut to programmers of this device...
hotmatua.parulian said:
Thanks for respond, i have to download the jb stockbase again as the file used for lg flash tool is missing, looks like flashtool keep it somewhere...btw, when i use flashtool to flash the jb stock (offline mode), it.doesnt complete 100%, at 99% device was successfully boot and normal but state in flashtool screen is 99% and message to.retry is showned up.
Fyi, after flashed to jb, i cant execute fastboot flash command, the result is waiting for any device, but adb devices command return expected result. Enable debugging setting is already checked also.
Click to expand...
Click to collapse
G Pro doesn't support fastboot commands (or is really limited in that field, I'm not sure what to say/think), due to some mess LG made. Mine didn't even want to 'adb reboot bootloader', it simply rebooted device back to system, and was pain in the ass for many things because It has custom download mode, it has custom boot sequence, everything is locked down... everything is different from everything else you're used to. Thank God back then a+b OTA system didn't exist, we'd never get any AOSP support not...
Do as g0at1 said - flash TWRP from Freegee, boot it to make sure it works, reboot back to system and flash newer TWRP from Flashify or any other tool like that one. I did have E988 (just Taiwan variant), and never had that much issues, nearly every time it was a straightforward 'flash JB KDZ, root it manually, Freegee, newer TWRP, backup, flash ROM', and trust me, that one was "revived" many times.
In the end, if even that doesn't help, flash CWM from Freegee, and update it with Philz Touch for E980. I think it will support Lollipop ROMs without any issues, just don't ever boot directly into it if you're not ready to mess with dd from recovery mode - always use adb.
hotmatua.parulian said:
Quiet interesting this device...salut to programmers of this device...
Click to expand...
Click to collapse
This device was one of the hardest devices to work with... and I had Note N7000 with bad MMC which nearly bricked five times running unrooted stock firmwares Samsung provided. And Tegra-based Galaxy S2 clone with many hardware and software issues on stock... And many nameless devices with chips made by "big" vendors, like Allwinner, Rockchip etc which got some older CyanogenMod version builds with some or even complete success... And I never, never had that much issues porting stuff to any of these above, as I had with G Pro. Heck, working on a overclocking and underclocking for G Pro took me nearly two months of coding, testing, scratching everything off and starting from the beginning to just get it to some functional level and make it work as intended... and when I look at that code, I still have a feeling that it isn't completed and that some fixes are still necessary. I won't even start with GPU issues, I've spent more time than I'd like to admit on patching sessions.
ShadySquirrel said:
G Pro doesn't support fastboot commands (or is really limited in that field, I'm not sure what to say/think), due to some mess LG made. Mine didn't even want to 'adb reboot bootloader', it simply rebooted device back to system, and was pain in the ass for many things because It has custom download mode, it has custom boot sequence, everything is locked down... everything is different from everything else you're used to. Thank God back then a+b OTA system didn't exist, we'd never get any AOSP support not...
Do as g0at1 said - flash TWRP from Freegee, boot it to make sure it works, reboot back to system and flash newer TWRP from Flashify or any other tool like that one. I did have E988 (just Taiwan variant), and never had that much issues, nearly every time it was a straightforward 'flash JB KDZ, root it manually, Freegee, newer TWRP, backup, flash ROM', and trust me, that one was "revived" many times.
In the end, if even that doesn't help, flash CWM from Freegee, and update it with Philz Touch for E980. I think it will support Lollipop ROMs without any issues, just don't ever boot directly into it if you're not ready to mess with dd from recovery mode - always use adb.
This device was one of the hardest devices to work with... and I had Note N7000 with bad MMC which nearly bricked five times running unrooted stock firmwares Samsung provided. And Tegra-based Galaxy S2 clone with many hardware and software issues on stock... And many nameless devices with chips made by "big" vendors, like Allwinner, Rockchip etc which got some older CyanogenMod version builds with some or even complete success... And I never, never had that much issues porting stuff to any of these above, as I had with G Pro. Heck, working on a overclocking and underclocking for G Pro took me nearly two months of coding, testing, scratching everything off and starting from the beginning to just get it to some functional level and make it work as intended... and when I look at that code, I still have a feeling that it isn't completed and that some fixes are still necessary. I won't even start with GPU issues, I've spent more time than I'd like to admit on patching sessions.
Click to expand...
Click to collapse
:good::good::good::good: salut to you...the true programmer..never quit..yes im agree with you...i had played with nexus 1,2,3 before but never found something like this...
OK then, i will try g0at1 suggestion, hopefully it works... Like you said its only JB, root, freegee, newer twrp, backup, flash custom
Update
I couldnt wait to try again,i cant download the jb stock for a while due to internet quota limitation, so i did this:
1. Flash to stock that i still have v20c 4.4.2
2. Reboot to stock recovery then reboot to system
3. Run roottool.kitkat batch script (found from http://www.gadgetstroop.com), reboot to recovery, sideload installation of root script with result success
4. Reboot to system, run Root Checker to ensure device has been rooted
5. Install cwm recovery with GPro Kitkat Recovery 6.0.4.4 with result success
6. Reboot to cwm recovery success and do nandroid backup
7. Reboot to system, install flashify, download latest twrp official 3.0.2 and flash it using flashify: success
8. Reboot to recovery, now the recovery become twrp
9. Install package Carbon 5.1 unofficial: fail with message "cant install this package on top of incompatible data"
hotmatua.parulian said:
Update
I couldnt wait to try again,i cant download the jb stock for a while due to internet quota limitation, so i did this:
1. Flash to stock that i still have v20c 4.4.2
2. Reboot to stock recovery then reboot to system
3. Run roottool.kitkat batch script (found from http://www.gadgetstroop.com), reboot to recovery, sideload installation of root script with result success
4. Reboot to system, run Root Checker to ensure device has been rooted
5. Install cwm recovery with GPro Kitkat Recovery 6.0.4.4 with result success
6. Reboot to cwm recovery success and do nandroid backup
7. Reboot to system, install flashify, download latest twrp official 3.0.2 and flash it using flashify: success
8. Reboot to recovery, now the recovery become twrp
9. Install package Carbon 5.1 unofficial: fail with message "cant install this package on top of incompatible data"
Click to expand...
Click to collapse
You forgot to wipe system, data and caches.
ShadySquirrel said:
You forgot to wipe system, data and caches.
Click to expand...
Click to collapse
Hehehe,..thats what i thought at 1st place when it comes to fail..so i reboot to system again, reboot to recovery and try again but the result is still the same....cant install on top of icompatible data..
P.S: now downloading your slim lp 5.1 beta unofficial and i want to try it 2morrow...
hotmatua.parulian said:
Hehehe,..thats what i thought at 1st place when it comes to fail..so i reboot to system again, reboot to recovery and try again but the result is still the same....cant install on top of icompatible data..
P.S: now downloading your slim lp 5.1 beta unofficial and i want to try it 2morrow...
Click to expand...
Click to collapse
I use SlimLP for a long time because it's the only one that works smoothly for me. You might not have any trouble flashing it Through the latest TWRP.
Have fun!
g0at1 said:
I use SlimLP for a long time because it's the only one that works smoothly for me. You might not have any trouble flashing it Through the latest TWRP.
Have fun!
Click to expand...
Click to collapse
Finally carbon installed successfully after I repeat the step very carefully including your reminder bout wiping...
Thank you very much, I will consult any bugs I found..
Half Day 1 issue:
- Scrambled screen layout each time booting
- Camera unstable/crash, also with apps camera mx and open camera
- i think batt is draining faster than kitkat stock
- i feel internet via wifi is slower than kitkat stock
- phone call, other person cant hear my voice
Just flashed SlimLP..Gosh its so slim and smooth...thank you very much...there issue bout the camera and scrambled screen each time I reboot the system, which camera apps I should use?

Categories

Resources