Related
I have rooted my Telus LG Optimus LTE (P935) successfully.
It is just the CyanogenMod 10.1 recovery image that isn't working for me.
I get the
Code:
---------------
Secure booting Error!
Cause : boot certification verify
-------------------------
------------------------------
Enter the fastboot...
Enter the fastboot...
Long time no see!
-------------------------------------------------
message when I boot to recovery.
Is there a simple fix for this i.e. use an different Cyanogen Mod, or my phone isn't really rooted at all and I think it is, or...?
The phone boots into the Telus ICS just fine, works ok and all, but if I want the thing to be upgradeable over time, I think I don't want to just rely on Telus to keep it up to date, do I?
lorax1284 said:
I have rooted my Telus LG Optimus LTE (P935) successfully.
It is just the CyanogenMod 10.1 recovery image that isn't working for me.
I get the
Code:
---------------
Secure booting Error!
Cause : boot certification verify
-------------------------
------------------------------
Enter the fastboot...
Enter the fastboot...
Long time no see!
-------------------------------------------------
message when I boot to recovery.
Is there a simple fix for this i.e. use an different Cyanogen Mod, or my phone isn't really rooted at all and I think it is, or...?
The phone boots into the Telus ICS just fine, works ok and all, but if I want the thing to be upgradeable over time, I think I don't want to just rely on Telus to keep it up to date, do I?
Click to expand...
Click to collapse
You have to unbrick; final answer. No other way around it. Just pick one of the numerous guides here in the general section and follow it.
Unbrick? But it's not bricked...
lordcheeto03 said:
You have to unbrick; final answer. No other way around it. Just pick one of the numerous guides here in the general section and follow it.
Click to expand...
Click to collapse
Thanks for that, but I just want to confirm that even though I have superuser installed and working, and ClockWorkMod is installed and working, and when I boot the device normally it loads up into Ice Cream Sandwich just fine, and everything works great, I STILL have to follow a full "Unbrick" procedure just to get a "proper" recovery.img onto the device?
I'm not afraid of ADB / command line, but if you say "do the unbrick", well, OK, but could you recommend a SPECIFIC guide? The one I used to get where I am is this one:
http://forum.xda-developers.com/showthread.php?t=1554255
as recommended in this post:
Root Telus P935? post #13
So could you advise if I should retry that method or if I should try a different method, which one might be most likely to leave me with a LG Optimus LTE with a more-current version of Android than 4.0.4, AND leave the device with the ability to update to subsequent Android releases (either stock or Cyanogen?)
I am just trying to avoid a lot of fruitless trial and error if there's a known "best way" to do what I'm trying to do.
lorax1284 said:
Thanks for that, but I just want to confirm that even though I have superuser installed and working, and ClockWorkMod is installed and working, and when I boot the device normally it loads up into Ice Cream Sandwich just fine, and everything works great, I STILL have to follow a full "Unbrick" procedure just to get a "proper" recovery.img onto the device?
I'm not afraid of ADB / command line, but if you say "do the unbrick", well, OK, but could you recommend a SPECIFIC guide? The one I used to get where I am is this one:
http://forum.xda-developers.com/showthread.php?t=1554255
as recommended in this post:
Root Telus P935? post #13
So could you advise if I should retry that method or if I should try a different method, which one might be most likely to leave me with a LG Optimus LTE with a more-current version of Android than 4.0.4, AND leave the device with the ability to update to subsequent Android releases (either stock or Cyanogen?)
I am just trying to avoid a lot of fruitless trial and error if there's a known "best way" to do what I'm trying to do.
Click to expand...
Click to collapse
I haven't asked and I am only assuming that you are on an official version of ICS, right? If that is the case, it is fully possible to have root privs yet fail to flash a working recovery.
The thing is; if you are trying for a custom recovery, such as TWRP or CWM, then most assuredly you must unbrick. On the official ICS releases, having root privs means nothing as far as flashing a custom recovery is concerned.
Flashing a custom recovery+ROM will not hinder your ability to update either your custom ROM or upgrade to any (unlikely) future LG update.
As for which method is best, I personally say that ANY of them work as I have tried each one listed on this board and have encountered not one single problem. My personal recommendation is Hereric's guide, but in general, they all do just about the same thing. Other members do not share my "luck" as problems have been experienced with each method. The most important thing is to read through the guide a few times before starting it. One thing I will recommend is that since you have a P935, whichever method you choose, make sure you use a P93x .kdz instead of the Korean SU640 .kdz. I mean, it will work with either one, but there are a few minor gremlins that can pop up if you use the SU640 .kdz to unbrick.
lordcheeto03 said:
I haven't asked and I am only assuming that you are on an official version of ICS, right? If that is the case, it is fully possible to have root privs yet fail to flash a working recovery.
Click to expand...
Click to collapse
Yes, the official Telus ICS. It was installed using the Windows LG upgrade tool.
lordcheeto03 said:
On the official ICS releases, having root privs means nothing as far as flashing a custom recovery is concerned.
Click to expand...
Click to collapse
That is what I was looking for confirmation of... I will unbrick.
lordcheeto03 said:
Flashing a custom recovery+ROM will not hinder your ability to update either your custom ROM or upgrade to any (unlikely) future LG update.
As for which method is best, I personally say that ANY of them work as I have tried each one listed on this board and have encountered not one single problem. My personal recommendation is Hereric's guide, but in general, they all do just about the same thing. Other members do not share my "luck" as problems have been experienced with each method. The most important thing is to read through the guide a few times before starting it. One thing I will recommend is that since you have a P935, whichever method you choose, make sure you use a P93x .kdz instead of the Korean SU640 .kdz. I mean, it will work with either one, but there are a few minor gremlins that can pop up if you use the SU640 .kdz to unbrick.
Click to expand...
Click to collapse
Thanks very much for this detailed response... I'll get to it this evening and post back when I've done it.
Cyanogenmod 10.1 now stuck at boot screen
I have got Cyanogen 10.1 installed, now it's stuck on the cyan (I just got that!) boot logo (the circle with the hexagon screen with the moving spokes) and left it in that state far longer than should have been necessary for first boot... should I not have used 10.1?
lorax1284 said:
I have got Cyanogen 10.1 installed, now it's stuck on the cyan (I just got that!) boot logo (the circle with the hexagon screen with the moving spokes) and left it in that state far longer than should have been necessary for first boot... should I not have used 10.1?
Click to expand...
Click to collapse
Shouldn't matter which ROM you install. I'd wipe everything and try it again; or try a different ROM. You should be good to go once you've unbricked.
first boot with cm 10.1 will take about 10 minutes if i remember right, its probly not stuck on logo, just wait and let it install., if u leave it on logo for 30 min and its not booted redownload/flash it again.
Thanks; managed to get it installed
KronicSkillz said:
first boot with cm 10.1 will take about 10 minutes if i remember right, its probly not stuck on logo, just wait and let it install., if u leave it on logo for 30 min and its not booted redownload/flash it again.
Click to expand...
Click to collapse
I had to flash / boot a few times... another tip is that in order for the "boot to recovery" to work, you first have to do a full wipe: once I realized that I was able to get various cyanogenmod firmwares onto the device and if I had problems, had to do a wipe then I could use the recovery firmware to try another.
As topic says, is there a custom recovery available for R819 ?
I found TWRP for Chinese R819T version, but is it compatible also with the R819 ?
samusalo said:
As topic says, is there a custom recovery available for R819 ?
I found TWRP for Chinese R819T version, but is it compatible also with the R819 ?
Click to expand...
Click to collapse
Not yet. Dees_Troy is working on it now, he got an R819 a day or two ago. (Edit: oops, he doesn't have his yet, he was just working with someone else.)
I just got mine earlier today. Right now I am trying to get a complete return-to-stock package from Oppo. Yeah, I could extract everything and eventually build one myself, but it's SO much easier when the manufacturer provides it for you. Unfortunately it's the weekend and the Oppo guys are in a complete different timezone than I am. I think that was the main reason Dees_Troy is halted too - Trying to boot the image using "fastboot boot" doesn't work, and he's (understandably) nervous about flashing a recovery when he doesn't have a return-to-stock image.
Edit: FYI, motochopper works for rooting. It's a royal pain to get it working with this device on Windows machines, but on Linux, you only need to get ADB running by adding 0x22d9 to ~/.android/adb_usb.ini
Entropy512 said:
Not yet. Dees_Troy is working on it now, he got an R819 a day or two ago. (Edit: oops, he doesn't have his yet, he was just working with someone else.)
I just got mine earlier today. Right now I am trying to get a complete return-to-stock package from Oppo. Yeah, I could extract everything and eventually build one myself, but it's SO much easier when the manufacturer provides it for you. Unfortunately it's the weekend and the Oppo guys are in a complete different timezone than I am. I think that was the main reason Dees_Troy is halted too - Trying to boot the image using "fastboot boot" doesn't work, and he's (understandably) nervous about flashing a recovery when he doesn't have a return-to-stock image.
Edit: FYI, motochopper works for rooting. It's a royal pain to get it working with this device on Windows machines, but on Linux, you only need to get ADB running by adding 0x22d9 to ~/.android/adb_usb.ini
Click to expand...
Click to collapse
What about Kernel SOurces and Other Trees ?
GuneetAtwal said:
What about Kernel SOurces and Other Trees ?
Click to expand...
Click to collapse
https://github.com/oppo-source/R819-Kernel-Source-4.2
MediaTek's kernel build system gives me a headache... It's a mess. Also, there are some nasty licensing conflicts between various files there. It's better than no source at all, but there are some issues a few of us are in contact with Oppo to resolve. (Oppo has been EXTREMELY cooperative so far.)
The biggest problem is that right now fastboot won't allow you to flash or boot any kernel images, whether normal boot or recovery. This means that if you hose up a device by flashing a bad recovery or kernel, you've got a brick. Supposedly Oppo is also working on fixing this too.
I successfully wrote a test TWRP image that Dees_Troy provided me, but I'm not going to make it public for the following reasons:
1) MTK's dumchar driver used to read/write kernel and recovery partitions does not do any size enforcement. Backing up a kernel in recovery will result in a 4GB backup image at the moment... I've figured out how to fix the driver, however:
2) Being unable to recover from bricks using fastboot means that this thing is extremely dangerous
3) The fstab is probably still not right for the device
The biggest blocker is 2) above - once that's resolved it should be a matter of only a few days.
Edit: I was partially wrong. It's not possible to flash recovery from fastboot, but you can flash replacement boot images.
Entropy512 said:
https://github.com/oppo-source/R819-Kernel-Source-4.2
MediaTek's kernel build system gives me a headache... It's a mess. Also, there are some nasty licensing conflicts between various files there. It's better than no source at all, but there are some issues a few of us are in contact with Oppo to resolve. (Oppo has been EXTREMELY cooperative so far.)
The biggest problem is that right now fastboot won't allow you to flash or boot any kernel images, whether normal boot or recovery. This means that if you hose up a device by flashing a bad recovery or kernel, you've got a brick. Supposedly Oppo is also working on fixing this too.
I successfully wrote a test TWRP image that Dees_Troy provided me, but I'm not going to make it public for the following reasons:
1) MTK's dumchar driver used to read/write kernel and recovery partitions does not do any size enforcement. Backing up a kernel in recovery will result in a 4GB backup image at the moment... I've figured out how to fix the driver, however:
2) Being unable to recover from bricks using fastboot means that this thing is extremely dangerous
3) The fstab is probably still not right for the device
The biggest blocker is 2) above - once that's resolved it should be a matter of only a few days.
Edit: I was partially wrong. It's not possible to flash recovery from fastboot, but you can flash replacement boot images.
Click to expand...
Click to collapse
WEll it is same as Xperia C's Source and other Leaked Source :/ i Don't know why Mediatek don't make a Simple Filesystem like that of Nvidea and Qualcomm
i think it comes with cwm right,thats what a developer told me:fingers-crossed:
Zpik said:
i think it comes with cwm right,thats what a developer told me:fingers-crossed:
Click to expand...
Click to collapse
No, it does not. Stock Android "3e" recovery.
There's a TWRP image nearly ready, but who knows when it will be fully ready for public consumption. I won't be working on it (or anything else) at all this week for various reasons.
I felt compelled to register here and post my success on getting LineageOS installed on my Verizon VK810 4G Altev LG G Pad tablet. It would not have been possible without this forum and the users who contribute, both with information and with uploads. I initially tried rooting with KingRoot and the OTA updated OS I had from Verizon but the app said there were 63 requests for rooting my device. Forget that idea. After also trying iRoot which wasn't working, I used the LG Flash Tool to downgrade to VK81035A and then was successfully able to root that. SuperSu definitely helped with the process. My guess is, even though both were Android 5.0.2, mine had OTA patches that I guess caused issues for rooting. Installing TWRP was a hassle though. None of the v500 TWRP images worked for me and many of the custom TWRP versions that I found on here did not work for me. You would not imagine the number of times I thought I bricked my device because I kept getting "Secure Booting Error! Cause: boot certification verify" errors. However, what did work for me was, using Platform-tools and VK810_twrp_2.7.0.1.zip for TWRP. For some reason, the other versions posted here did not work for me. It did take me a while to figure out how to get into TWRP because I kept using the Power-VolUp key combinations and it kept bringing me to what looked like LG's recovery menu. I didn't realize that the screen is actually fake and you have to click "Factory Reset/Wipe" on there to get into TWRP. It actually took me a long time to figure that out. With TWRP installed, I searched for ROMs that I could use that were newer than Android 5.0.2 and ended up downloading LineageOS as it came up for the VK810 and since VS500 ROMs weren't allowed to be installed. Now to be fair, the LineageOS Rom that I used (lineage-14.1-20171228_233442-UNOFFICIAL-vk810.zip) is pretty glitchy. The display likes to blink a lot, many apps crash on it and there is no cellular data working for me, but I assume that will possibly be fixed in the future and at least now, I can customize more than I could on stock. On first install, I also lost my root and forgot to install the GApps package from the Lineage website. Anyway, hope this helps at least one person here. Nothing was one-click for me, but I did learn a lot about the process of rooting and flashing, and now better than to automatically allow OTA updates. I do hope LineageOS or another ROM keeps updating for the VK810 because this tablet does not seem that popular and I would like to see Oreo. Thank you everyone for your help!
XDAnonymous said:
I felt compelled to register here and post my success on getting LineageOS installed on my Verizon VK810 4G Altev LG G Pad tablet. It would not have been possible without this forum and the users who contribute, both with information and with uploads. I initially tried rooting with KingRoot and the OTA updated OS I had from Verizon but the app said there were 63 requests for rooting my device. Forget that idea. After also trying iRoot which wasn't working, I used the LG Flash Tool to downgrade to VK81035A and then was successfully able to root that. SuperSu definitely helped with the process. My guess is, even though both were Android 5.0.2, mine had OTA patches that I guess caused issues for rooting. Installing TWRP was a hassle though. None of the v500 TWRP images worked for me and many of the custom TWRP versions that I found on here did not work for me. You would not imagine the number of times I thought I bricked my device because I kept getting "Secure Booting Error! Cause: boot certification verify" errors. However, what did work for me was, using Platform-tools and VK810_twrp_2.7.0.1.zip for TWRP. For some reason, the other versions posted here did not work for me. It did take me a while to figure out how to get into TWRP because I kept using the Power-VolUp key combinations and it kept bringing me to what looked like LG's recovery menu. I didn't realize that the screen is actually fake and you have to click "Factory Reset/Wipe" on there to get into TWRP. It actually took me a long time to figure that out. With TWRP installed, I searched for ROMs that I could use that were newer than Android 5.0.2 and ended up downloading LineageOS as it came up for the VK810 and since VS500 ROMs weren't allowed to be installed. Now to be fair, the LineageOS Rom that I used (lineage-14.1-20171228_233442-UNOFFICIAL-vk810.zip) is pretty glitchy. The display likes to blink a lot, many apps crash on it and there is no cellular data working for me, but I assume that will possibly be fixed in the future and at least now, I can customize more than I could on stock. On first install, I also lost my root and forgot to install the GApps package from the Lineage website. Anyway, hope this helps at least one person here. Nothing was one-click for me, but I did learn a lot about the process of rooting and flashing, and now better than to automatically allow OTA updates. I do hope LineageOS or another ROM keeps updating for the VK810 because this tablet does not seem that popular and I would like to see Oreo. Thank you everyone for your help!
Click to expand...
Click to collapse
Wow thank you so much I thought it was me having issues. I have a 410vk and as you said nothing was one click. I hope to continue to try and get root on the G Pad. Still an awesome device.
Sent from my LG-H932 using Tapatalk
XDAnonymous said:
I felt compelled to register here and post my success on getting LineageOS installed on my Verizon VK810 4G Altev LG G Pad tablet. It would not have been possible without this forum and the users who contribute, both with information and with uploads. I initially tried rooting with KingRoot and the OTA updated OS I had from Verizon but the app said there were 63 requests for rooting my device. Forget that idea. After also trying iRoot which wasn't working, I used the LG Flash Tool to downgrade to VK81035A and then was successfully able to root that. SuperSu definitely helped with the process. My guess is, even though both were Android 5.0.2, mine had OTA patches that I guess caused issues for rooting. Installing TWRP was a hassle though. None of the v500 TWRP images worked for me and many of the custom TWRP versions that I found on here did not work for me. You would not imagine the number of times I thought I bricked my device because I kept getting "Secure Booting Error! Cause: boot certification verify" errors. However, what did work for me was, using Platform-tools and VK810_twrp_2.7.0.1.zip for TWRP. For some reason, the other versions posted here did not work for me. It did take me a while to figure out how to get into TWRP because I kept using the Power-VolUp key combinations and it kept bringing me to what looked like LG's recovery menu. I didn't realize that the screen is actually fake and you have to click "Factory Reset/Wipe" on there to get into TWRP. It actually took me a long time to figure that out. With TWRP installed, I searched for ROMs that I could use that were newer than Android 5.0.2 and ended up downloading LineageOS as it came up for the VK810 and since VS500 ROMs weren't allowed to be installed. Now to be fair, the LineageOS Rom that I used (lineage-14.1-20171228_233442-UNOFFICIAL-vk810.zip) is pretty glitchy. The display likes to blink a lot, many apps crash on it and there is no cellular data working for me, but I assume that will possibly be fixed in the future and at least now, I can customize more than I could on stock. On first install, I also lost my root and forgot to install the GApps package from the Lineage website. Anyway, hope this helps at least one person here. Nothing was one-click for me, but I did learn a lot about the process of rooting and flashing, and now better than to automatically allow OTA updates. I do hope LineageOS or another ROM keeps updating for the VK810 because this tablet does not seem that popular and I would like to see Oreo. Thank you everyone for your help!
Click to expand...
Click to collapse
Can you link where you got the ROM? Is anyone actively working on it? Really too bad the vk810 never got much love, great little device. Been awhile since I've done anything with it, it's my dad's so I got it rooted on 5.0.2 and just kinda left it alone. What prompted me to come back to this forum is screen mirroring won't work. The tablet sees TV and vice versa, it tries to connect but never completes the connection, just kicks back to satellite TV after a couple of seconds of black screen. Don't suppose you tried casting on that lineage build?
AirForceOnes0010 said:
Can you link where you got the ROM? Is anyone actively working on it? Really too bad the vk810 never got much love, great little device. Been awhile since I've done anything with it, it's my dad's so I got it rooted on 5.0.2 and just kinda left it alone. What prompted me to come back to this forum is screen mirroring won't work. The tablet sees TV and vice versa, it tries to connect but never completes the connection, just kicks back to satellite TV after a couple of seconds of black screen. Don't suppose you tried casting on that lineage build?
Click to expand...
Click to collapse
I got the ROM from the Invisiblek ROMS site under /roms/lineage-14.1/vk810/ (Can't post the link as I'm currently under 10 posts)
It's definitely a start. There is screen glitching, and no LTE service (Wi-Fi only), so it definitely limits the tablet. I have not done much with it as it was a hassle just to get the root within the OS to work correctly. Some apps aren't detecting root when the OS is trying to give it to them.
XDAnonymous said:
I got the ROM from the Invisiblek ROMS site under /roms/lineage-14.1/vk810/ (Can't post the link as I'm currently under 10 posts)
It's definitely a start. There is screen glitching, and no LTE service (Wi-Fi only), so it definitely limits the tablet. I have not done much with it as it was a hassle just to get the root within the OS to work correctly. Some apps aren't detecting root when the OS is trying to give it to them.
Click to expand...
Click to collapse
It'll have to wait until/if LTE is ever functional then, my parents don't have internet other 4g out in the sticks lol. Google took me right to it, thanks. Will keep it bookmarked just in case
I'd like to write about my experience too as it took me some time to finally get the device up and running.
I will describe what I wanted to do, what mistakes I've made and what should've been the correct way.
The device itself is LG G Pad 8.3, Verizon LTE variant aka vk810
Initally I received it in a bricked state, on launching it showed the "Secure booting error" message and that's it.
1) Unbricking
The goal was to install an official LG system image and restore the tablet to a working state.
Basically, I did everything according to the steps outlined here: https://forum.xda-developers.com/lg-g-pad-83/general/vk810-4g-reliable-to-root-install-t3283027
Installed LG drivers
Downloaded the LG Flash Tool 2104
Downloaded a KDZ image
Plugged the device in the download mode into the PC and installed the KDZ using the flash tool
At that point I got a fancy idea to install a non-stock Android on this tablet.
2) Lineage OS
I chose this OS for my tablet, because it seems to be the current standard for non-stock Android installations.
I followed these installation instructions: https://wiki.lineageos.org/devices/v500/install
BEWARE: that page is for v500, so it won't work for vk810.
Lineage doesn't support vk810 officially. A mistake I've made was assuming that I can just roll along with a v500 installation. Actually, you kinda can, but for me it resulted in Wi-Fi not working and my device's MAC address being 02:00:00:00:00:00.
3) Rooting
I was quite confused here too: there are different rooting methods, and some of them can be applied in different ways.
Ultimately I found Stump to be the most comfortable for me: https://forum.xda-developers.com/lg...root-stump-root-lg-g3-sprint-verizon-t2850906
It works fine on this device and uses a very straightforward process: download APK to your PC, connect the tablet to the PC, "adb install <filename>.apk", then launch the app and that's it. It had to go through the bruteforce process to root, which took several minutes.
4) TWRP
I don't remember what exact TWRP I installed initially, but it was a 3.x version, and I encountered an issue where it couldn't mount any of the tablet's partitions. That was quite a pain in the ass.
For a while I resorted to using an older version, 2.7.x, and it worked fine.
Ultimately what I'm the most happy with is this: https://forum.xda-developers.com/lg-g-pad-83/general/vk810-twrp-3-1-1-0-unofficial-t3691551
The lesson learned here is that, again, you need to make sure stuff you install is compatible with your device.
Ultimately, after making mistakes at each step of the process, I figured out everything, and just followed the installation instructions on the Lineage page I linked earlier.
* Flash stock rom
* Root using Stump
* Enable USB debugging on the tablet, install Stump via adb and root the device
* Install vk810 variant of TWRP 3.2.1-0 via adb
* Reboot to recovery (turn off the tablet -> hold Volume Down + Power -> you should get a factory reset menu after the LG logo -> select factory reset, then confirm it and you'll be booted into TWRP. That factory reset is fake after you have TWRP installed)
* Wipe everything
* adb push the lineage / lineage's su / opengapps onto the device
* Install lineage, then su and opengapps and you're good to go
Main lesson learned: it is CRUCIAL to make sure stuff you install is compatible with your particular device. Do not assume that you can use another version, even if it is made for a device of the same family.
Just to provide an update here, this is where the ROM that I used came from: https://updater.invisiblek.org/vk810
The latest version at this time seems to be this: lineage-17.1-20200329-UNOFFICIAL-vk810.zip
XDAnonymous said:
Just to provide an update here, this is where the ROM that I used came from: https://updater.invisiblek.org/vk810
The latest version at this time seems to be this: lineage-17.1-20200329-UNOFFICIAL-vk810.zip
Click to expand...
Click to collapse
Thanks for all the great information, but I have the VK810 that has usb connection problems. It will connect, but it keeps dropping (it cannot be trusted with usb cord). I have wanted to root, twrp, magisk and other things just to play around to see what it can do or how far I can go with it. I am not afraid to trash it. Have you or anyone else had this problem? I have reset it, wiped it out, factory settings, but nothing seems to help that usb port. I was thinking that reflashing the rom might help. Any advice is appreciated.
https://www.getdroidtips.com/twrp-recovery-motorola-moto-e6/
None of my recoveries have worked for the E6, but I'm being linked as a developer for a working TWRP recovery. if you came from this link, DO NOT use my builds. I've deleted the links to my builds anyway. Someone else got OrangeFox working on the forums. Go check it out and use that one instead.
I tried it but sadly it didn't work - I tried to use it as a temporary boot but it simply booted into the the normal E6 OS
TristianX said:
I tried it but sadly it didn't work - I tried to use it as a temporary boot but it simply booted into the the normal E6 OS
Click to expand...
Click to collapse
Crap, I gotta see if there's a way I can get logs then. But you usually can't get logs unless you can boot into a custom recovery...
Gimme a bit to think about this
I tried this image;
https://unofficialtwrp.com/twrp-3-3-1-root-moto-e6/
This process too
https://forum.xda-developers.com/moto-e6/how-to/rooting-e6-surfna-t3965659
and then of course your image from this post.
They all indicate they flash ok from the fastboot status but when it should boot/temp boot/or replace recovery it simply puts me back into normal boot up. I'm using the t-mobile variant with firmware PCB29.73-65-3
Ohhhh I'm excited to see where this can go!
My buddy just sent me a PM and brought up a good point. When dirty porting, I didn't even think to check if the recoveries were both 64 bit. This could be the reason why it's not booting. I'm gonna have another go at this later today and post up another test image for you all if I can figure something out.
Also, just as a heads up, this is for the QUALCOMM MODEL E6. Not sure if there's a MediaTek international model, but this isn't for that.
Well when you post back I'll deff give it a try.
I'm gonna try porting from a different phone, some kind of Aquarius model. It has the same chipset and is 64 bit too.
Also, to those that werent able to flash/boot from it, you unlocked your bootloader right? Forgot to mention that it needs to be unlocked for this to work
I haven't had a chance to give this a go. I'm making sure I understand everything and the risks. More than willing to give it a shot tho
In the process of dirty porting TWRP again to the E6. The only issue is I now have Windows on my PC (for very important personal reasons) and Carliv Image Kitchen is only available on Linux. Here's the steps I need to take to get you guys the 2nd "alpha" of TWRP:
1) Beat Broken Arrow in Payday 2 so I can go back to Linux
2) Download the recoveries/image kitchens for everything again to do the port
3) Do the dirty port and upload it
Currently I'm working on step 1, but it should be done by the end of this night.
NEW RECOVERY IS UP!!! Go download Attempt 2 and see if it gets you any further. If that breaks, try Attempt 3.
Got a moto e6 recently just as an Android device to experiment/mess around with (Mostly been into iOS and Jailbreaking) and stumbled across this thread. Whats the current situation with this? Is the TWRP port working?
Tim0xff7 said:
Got a moto e6 recently just as an Android device to experiment/mess around with (Mostly been into iOS and Jailbreaking) and stumbled across this thread. Whats the current situation with this? Is the TWRP port working?
Click to expand...
Click to collapse
Attempt 1 didn't work, waiting on someone to try Attempt 2, and if that doesn't work then 3. If you want to help (I'd really appreciate it) unlock your bootloader and try to boot/flash into one of the images I gave
I'd love to help! Bootloader is already unlocked so I'll try flashing and then get back to you with results
Some observations so far:
-Using fastboot to boot an image flat-out doesn't work. I'd hazard a guess and say it's due to Pie requiring system-as-root and the boot image not utilizing a ramdisk, but honestly I don't really know.
-The init executable from the stock recovery is 32-bit, and everything I've seen so far indicates an entirely 32-bit build for the E6. Using 64-bit TWRP bases probably won't work; the second and third attempts linked in the first post do not boot, and attempts to boot to recovery with them flashed will fail, with the phone continuing on to boot the system regularly, which in turn restores the stock recovery image.
-On the other hand, with what I believe is your first build, and my own test using the standard E5 TWRP as a base, I can get as far as the TWRP splash screen, where it locks up indefinitely.
-I've also tried creating my own device tree based on the E5 tree and building from scratch without any further success, although in fairness I've only been at it for a couple of hours.
FEGuy said:
Some observations so far:
-Using fastboot to boot an image flat-out doesn't work. I'd hazard a guess and say it's due to Pie requiring system-as-root and the boot image not utilizing a ramdisk, but honestly I don't really know.
-The init executable from the stock recovery is 32-bit, and everything I've seen so far indicates an entirely 32-bit build for the E6. Using 64-bit TWRP bases probably won't work; the second and third attempts linked in the first post do not boot, and attempts to boot to recovery with them flashed will fail, with the phone continuing on to boot the system regularly, which in turn restores the stock recovery image.
-On the other hand, with what I believe is your first build, and my own test using the standard E5 TWRP as a base, I can get as far as the TWRP splash screen, where it locks up indefinitely.
-I've also tried creating my own device tree based on the E5 tree and building from scratch without any further success, although in fairness I've only been at it for a couple of hours.
Click to expand...
Click to collapse
PM me. I've got a buddy who's more into kernels and things like that that can probably help us. I'd like to help too, but I can't promise much as I've never done kernel development before
Any headway on this front?
Hey OP, I got it to boot to the TWRP logo, but it won't fully boot into recovery. is there something I'm missing? sorry, I sorely want to install liveboot again on my device, and I feel like I'm being an idiot with some huge oversight on my part haha. is it functional?
---------- Post added at 08:56 PM ---------- Previous post was at 08:55 PM ----------
I'm only asking because I've sat at the TWRP logo for more than half an hour sorry to bug you
Daltonyx said:
Hey OP, I got it to boot to the TWRP logo, but it won't fully boot into recovery. is there something I'm missing? sorry, I sorely want to install liveboot again on my device, and I feel like I'm being an idiot with some huge oversight on my part haha. is it functional?
---------- Post added at 08:56 PM ---------- Previous post was at 08:55 PM ----------
I'm only asking because I've sat at the TWRP logo for more than half an hour sorry to bug you
Click to expand...
Click to collapse
The TWRP is not working. None of them are. The original poster has said in some recent comments that they plan on buying the E6, so maybe in the future we may get a fully working TWRP. I sure hope so, because my E6 has been collecting dust in my drawer for about a month now. I've been content with my G6 and G7 Power but I can't stand such a nice but unused phone.
Since Visible is pretty much giving away the e6 with any old trade in maybe the op will finally get one.
Moto G Stylus Metro PCS brand:
I'm brand new to this subject so please forgive any ignorance. I'm decent with linux but new to android stuff.
Tried flashing the latest weekly build of OmniROM - now seems to be stuck at boot screen and won't go past. I am coming from latest OTA update from Motorola.
Phone was not rooted prior to starting this.
I also accidentally wiped slot A with my factory image on it (oops).
TWRP did not ask for any decryption key so I ran:
fastboot erase userdata
and this seemed to fix errors that I was getting while flashing with respect to denying access.
What I've done:
-Unlocked bootloader
-Installed TWRP 3.5.0-10 from the g-stylus forum.
-wiped and formatted via TWRP
-flashed 5/23 weekly build of OmniROM
Now no matter what I do or what slot I flash to it will not get past the Omni boot load animated screen. I've run this for almost 2 hours and nothing happens.
Any ideas?
Thanks!
nutsnax said:
Moto G Stylus Metro PCS brand:
I'm brand new to this subject so please forgive any ignorance. I'm decent with linux but new to android stuff.
Tried flashing the latest weekly build of OmniROM - now seems to be stuck at boot screen and won't go past. I am coming from latest OTA update from Motorola.
Phone was not rooted prior to starting this.
I also accidentally wiped slot A with my factory image on it (oops).
TWRP did not ask for any decryption key so I ran:
fastboot erase userdata
and this seemed to fix errors that I was getting while flashing with respect to denying access.
What I've done:
-Unlocked bootloader
-Installed TWRP 3.5.0-10 from the g-stylus forum.
-wiped and formatted via TWRP
-flashed 5/23 weekly build of OmniROM
Now no matter what I do or what slot I flash to it will not get past the Omni boot load animated screen. I've run this for almost 2 hours and nothing happens.
Any ideas?
Thanks!
Click to expand...
Click to collapse
Weekly builds may be unstable. I'm actually curious on how you got a hold of such build for the this device. Most, if not all ROMs are unofficial for the stylus and updates for each rom varies by contributed developers.....
However, you say you're decent with Linux. I'm sure there's some developers here that would help you with various tools to learn on how to make your own version of any type of OS.
As for OmniRom, I'd probably ask @vache for some help, for he has his own unofficial version.
Also, I recommend that you have the latest platform tools and the moto software tool if you don't have these yet...
nevermind I got it working. I was flashing p2pstate.bin directly (somehow this works?) when instead I was supposed to extract the image files and flash the respective files.
Seems to boot up now. Thanks!
nutsnax said:
nevermind I got it working. I was flashing p2pstate.bin directly (somehow this works?) when instead I was supposed to extract the image files and flash the respective files.
Seems to boot up now. Thanks!
Click to expand...
Click to collapse
That's good you got it to work. One developer once told me, when all else fails, think outside of the box. You'll eventually get it to work somehow
I have your solution cuz I went through the same thing.. you have to start out with stock Android 10 so you have to be bootloader unlocked and rooted that way you can downgrade your software and it's only the super images that you have to downgrade.. so just flash your supers and you'll be fine but they have to be stock Android 10 it doesn't matter what firmware version because you're keeping the same modem file