Related
so I installed the latest CM12 Droid 4, and for some reason it's telling me I'm not rooted.
I was rooted in 4.1.2 using the razr utility for the XT894.
I first flashed original firmware
then did step 3 (root)
then installed safestrap using a 3.75 download link.
booted into recovery, installed latest CM12 nightly...
... but i can't get root access?
How do I restore root access now that I'm on 5.0.x?
Yes, I ENABLED root access in developer options. Still won't give root access.
Root Checker says:
Root access: no access
Su Found: system/xbin, system/bin
Hi,
After flashing CM12.1 you need to flash SuperSU:
http://forum.xda-developers.com/showthread.php?t=1538053
Actually, I didn't have to do that. I just started over again. I did try flashing SuperSU by downloading the APK they have linked on the playstore page, through SafeStrap Install ZIP function, but it didn't work.
I went with the Razr Utility and installed 4.1 with wipe. then reinstalled root. then I went and installed safestrap 3.75, followed by lollipop.
all is well now.
I think the cable extension i was using was causing packet loss issues of somesort, as i can touch the cable end and it cuts in and out. But the root process said it was completed successfully. I think it just didn't go through the cleaning process and left files over that caused a root loss of some sort.
It seems to be fine now.
Cm12 has it's own root, and is different from stock rom.
When device is in twrp recovery, it doesn't matter if Rom is Rooted or not.
Guessing it was a bad cm12 install, you didn't need to reflash firmware, just reboot to twrp, reinstall the Rom.
May need to redownload the Rom, and verify the md5 checksum.
To root Rom in twrp use
SuperSu flashable zip (UPDATE-SuperSU-v2.45.zip - 28 Jan 2015)
Sent from my XT907 using Tapatalk
sd_shadow said:
Cm12 has it's own root, and is different from stock rom.
When device is in twrp recovery, it doesn't matter if Rom is Rooted or not.
Guessing it was a bad cm12 install, you didn't need to reflash firmware, just reboot to twrp, reinstall the Rom.
May need to redownload the Rom, and verify the md5 checksum.
To root Rom in twrp use
SuperSu flashable zip (UPDATE-SuperSU-v2.45.zip - 28 Jan 2015)
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
if you look at my second post, I said I tried to install the SuperSU binary using recovery, and it did not do anything.
I just reinstalled the rom after wiping the partition to avoid any issues.
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
TWRP 3.2.1 Changelog: https://twrp.me/site/update/2017/12/09/twrp-3.2.1-0-released.html
Installation instructions: Use the official TWRP app (requires root), available here and here. If you already have TWRP installed, you can also download the latest available img and flash it from recovery.
DOWNLOAD (palman): https://dl.twrp.me/palman/
DOWNLOAD (v500): https://dl.twrp.me/v500/
More info: https://twrp.me/devices/lggpad83.html
Warning: builds for v500 require kitkat bootloader. If you are stuck on Lollipop bootloader, check this post.
Device source (palman): https://github.com/TeamWin/android_device_lge_palman
* The kernel in palman source is from 5.1 official build (source found here).
Device source (v500): https://github.com/TeamWin/android_device_lge_v500
* The kernel in v500 source is based on cm-14.1 sources.
XDA:DevDB Information
Team Win Recovery Project, Tool/Utility for the LG G Pad 8.3
Contributors
fefifofum, Dees_Troy, bigbiff
Source Code: https://github.com/omnirom/android_bootable_recovery
Version Information
Status: Stable
Created 2015-06-15
Last Updated 2017-12-10
Thanks very much for this! Great work! That is really nice that there is now official support for awifi/v500.
I assume the images are bumped?
Are the kernel sources for official twrp using your kernel sources?
Sources
This is the device repo for awifi/v500: https://github.com/TeamWin/android_device_lge_v500
The kernel in awifi/v500 repo was compiled from here, which is V50030A based.
This is the device repo for palman/v510: https://github.com/TeamWin/android_device_lge_palman
The kernel in palman/v510 repo is from 5.1 official build.
So, now we should be able to just flash the .img file directly within TWRP to update.
Deltadroid said:
So, now we should be able to just flash the .img file directly within TWRP to update.
Click to expand...
Click to collapse
Yes!
The repo for v510 is going to be renamed since it doesn't need to follow the "cyanogen" way, which is using the model name instead of the device name. That's why there is a little confusion with the names v500/awifi and v510/palman. The GPE repo will be named palman (which is the correct way) and the non GPE repo will stay as v500 (it should be called awifi), since almost every custom rom uses "cyanogen" way. If we wanted the non GPE to be named correctly we would need the devs of every custom rom to add an assert to their boardconfig so both, v500 and awifi, would be valid at installation time. It's just one line change.
Do we need to have TWRP recovery already flashed or can I just flash this recovery in the stock 20D with root?
Do we only need root access and flash the recovery using the TWRP manager from Play Store in stock 20D?
fefifofum, firstly, thanks for making an official TWRP for the V510.
Secondly, can you please enable backup of recovery partition?
luisbraz said:
Do we need to have TWRP recovery already flashed or can I just flash this recovery in the stock 20D with root?
Do we only need root access and flash the recovery using the TWRP manager from Play Store in stock 20D?
Click to expand...
Click to collapse
There are three ways to install TWRP explained at the installation details. Two of them require root and the third one requires twrp >= 2.8.4.0. Choose the one that is easier for you, they all should work.
aidfarh said:
fefifofum, firstly, thanks for making an official TWRP for the V510.
Secondly, can you please enable backup of recovery partition?
Click to expand...
Click to collapse
I could try, but it needs to go through gerrit. Why would you need to backup recovery partition?
fefifofum said:
Why would you need to backup recovery partition?
Click to expand...
Click to collapse
It's not strictly needed, but good to have for completeness. For example, if I flash a new version of TWRP and then find that's there a bug, I could just restore the previous version from backup. Of course, I could always just use fastboot or flashify to flash the old version, but it's nice to have the option.
fefifofum said:
There are three ways to install TWRP explained at the installation details. Two of them require root and the third one requires twrp >= 2.8.4.0. Choose the one that is easier for you, they all should work.
I could try, but it needs to go through gerrit. Why would you need to backup recovery partition?
Click to expand...
Click to collapse
I know, but I just want to be shure that this time I don't brick the tablet.
So you confirm that when we are stock with version 20D we just need root access? It's not necessary anymore a loky exploitable aboot?
Sorry for being a pain in the ass!
EDIT: Thank you @fefifofum for your work
I have installed the TWRP manager and selected install TWRP. Which version should I flash? The latest 2.8.1.0? And the twpr - awifi. img or the openrecovery - twrp - awifi. img?
I'm on stock 20d version with root. Thanks in advance.
aidfarh said:
It's not strictly needed, but good to have for completeness. For example, if I flash a new version of TWRP and then find that's there a bug, I could just restore the previous version from backup. Of course, I could always just use fastboot or flashify to flash the old version, but it's nice to have the option.
Click to expand...
Click to collapse
Old versions will still be available to download, so if a new version had issues you could always download and install an older version. No need to backup recovery I guess...
luisbraz said:
I know, but I just want to be shure that this time I don't brick the tablet.
So you confirm that when we are stock with version 20D we just need root access? It's not necessary anymore a loky exploitable aboot?
Sorry for being a pain in the ass!
EDIT: Thank you @fefifofum for your work
Click to expand...
Click to collapse
We don't need loki anymore, you just need to be on kitkat bootloader.
luisbraz said:
I have installed the TWRP manager and selected install TWRP. Which version should I flash? The latest 2.8.1.0? And the twpr - awifi. img or the openrecovery - twrp - awifi. img?
I'm on stock 20d version with root. Thanks in advance.
Click to expand...
Click to collapse
It looks like TWRP manager didn't update the images for the gpad. I will talk to them so they fix it and remove the old images, there should only be one version available: 2.8.6.0. Until then, please use the "dd" installation method.
fefifofum said:
It looks like TWRP manager didn't update the images for the gpad. I will talk to them so they fix it and remove the old images, there should only be one version available: 2.8.6.0. Until then, please use the "dd" installation method.
Click to expand...
Click to collapse
Thanks.
I think I'll wait for the TWRP manager update.
EDIT: Couldn’t wait and tried the dd method. For the first time, after thousands of attempts, I have the TWRP installed in the tablet!
luisbraz said:
Thanks.
I think I'll wait for the TWRP manager update.
EDIT: Couldn’t wait and tried the dd method. For the first time, after thousands of attempts, I have the TWRP installed in the tablet!
Click to expand...
Click to collapse
Glad to hear that! It seems the app TWRP manager cannot reach the new servers where official builds of TWRP are, so it's better not to use the app installation method to avoid installing old versions.
@fefifofum thanks a lot!!! I'm using slim alpha 4, what bootloader should I flash to solve the backlight problem? Thanks again
Pd: use rashr app to flash twrp, download .img and flash from internal memory, no problems. Don't use twrp manager.
bokoy said:
@fefifofum thanks a lot!!! I'm using slim alpha 4, what bootloader should I flash to solve the backlight problem? Thanks again
Pd: use rashr app to flash twrp, download .img and flash from internal memory, no problems. Don't use twrp manager.
Click to expand...
Click to collapse
I guess V50010B bootloader is what you need, but then you will probably have brightness issues while using this recovery.
New version
TWRP 2.8.7.0 released.
fefifofum said:
TWRP 2.8.7.0 released.
Click to expand...
Click to collapse
Hi all!
I have now TWRP 2.8.6.0 taken from here: http://forum.xda-developers.com/lg-g-pad-83/orig-development/recovery-twrp-2-8-2-0-v500-t2968472
Which are the differences between these recoverys? Which is the better to install?
Thanks!
Hey Guys! How to upgrade from this version? http://forum.xda-developers.com/lg-g-pad-83/orig-development/recovery-twrp-2-8-2-0-v500-t2968472
I have a v50020d model.
D4xel said:
Hi all!
I have now TWRP 2.8.6.0 taken from here: http://forum.xda-developers.com/lg-g-pad-83/orig-development/recovery-twrp-2-8-2-0-v500-t2968472
Which are the differences between these recoverys? Which is the better to install?
Thanks!
Click to expand...
Click to collapse
This one is official (without the quotes), doesn't require loki and is adapted to kitkat bootloader backlight. The other one you mention is adapted to jellybean bootloader backlight and requires loki. Just install the one that fits your needs.
cianz94 said:
Hey Guys! How to upgrade from this version? http://forum.xda-developers.com/lg-g-pad-83/orig-development/recovery-twrp-2-8-2-0-v500-t2968472
I have a v50020d model.
Click to expand...
Click to collapse
You have the install instructions on the first post. You can also download the image and flash it with THIS APP.
Because of the Locked Bootloader, the Stock Recovery cannot be replaced.
Safestrap Hijacks the boot process allowing for a custom recovery (TWRP)
In this custom recovery, Custom Roms can be installed, along with other functions that a custom recovery allows.
17 Aug 2015: Currently the newest version is Safestrap 3.75
Cm12 requires safestrap v3.75 (or newer)
3.75 is compatible with older roms.
stargo's Downloads
XT910: Safestrap-umts_spyder-v3.75.apk
XT912/XT908: Safestrap-spyder-v3.75.apk
XT894 (Droid 4): Safestrap-maserati-v3.75.apk
XT875 (Bionic): Safestrap-targa-v3.75.apk
Basic Install Instructions
Options for booting to Twrp Recovery
Backing up a Rom, Restoring a Backup
Creating a Rom Slot
Installing a Rom
How to install CyanogenMod on the Droid 4 Alt Directions @ wiki.cyanogenmod.org
Switching Active Rom
if you have a XT912 or XT894, There is a Modified Safestrap 3.75 for unused partitions (/preinstall & /webtop) by Mentor.37
XT894: http://forum.xda-developers.com/droid-4/development/wip-safestrap-3-75-unused-partitions-t3023932
XT912: http://forum.xda-developers.com/droid-razr/development/recovery-safestrap-3-75-unused-t3032675
Note: Mentor.37 has removed the Safestrap splash screen, so you must select reboot to recovery from rom or Boot to safestrap from Stock Boot Mode Selection Menu
Older Safestrap Versions
Saved
reserved
saved #2
Hi All / @bauner,
Does anyone know if there is a TWRP 2.8.7.0 or TWRP 3.0.2.1 available for our Note, that works in Android 4.4.4 (KitKat)?
I've found a TWRP 2.8.7.0 and a TWRP 3.0.2 which I believe @bauner very kindly wrapped up for us, to flash in ISORec. However when I flash 2.8.7.0 it shows as 2.8.1.0 when inside recovery.
I'm not sure if this has anything to do with ISORec, still trying to get my head around that. I understand that it separates the Recovery from the Kernel. But not sure if ISORec is supported on Android 4.4.4 (KitKat) ?
- when I flash 2.8.7.0 on KitKat, and then boot into Recovery, it shows up as 2.8.1.0?
Do those ISORec Recoveries look for a certain API / (SDK?) build of Android, and if it doesn't detect required version it doesn't flash?
I really need to get either 2.8.7.0 or 3.0.2.1 in order for Lanchon Re-Pit program to work... and happy with my build of KitKat until a stable Android 7.0 is out....
Cheers, Lister
Lister Of Smeg said:
Hi All / @bauner,
Does anyone know if there is a TWRP 2.8.7.0 or TWRP 3.0.2.1 available for our Note, that works in Android 4.4.4 (KitKat)?
I've found a TWRP 2.8.7.0 and a TWRP 3.0.2 which I believe @bauner very kindly wrapped up for us, to flash in ISORec. However when I flash 2.8.7.0 it shows as 2.8.1.0 when inside recovery.
I'm not sure if this has anything to do with ISORec, still trying to get my head around that. I understand that it separates the Recovery from the Kernel. But not sure if ISORec is supported on Android 4.4.4 (KitKat) ?
- when I flash 2.8.7.0 on KitKat, and then boot into Recovery, it shows up as 2.8.1.0?
Do those ISORec Recoveries look for a certain API / (SDK?) build of Android, and if it doesn't detect required version it doesn't flash?
I really need to get either 2.8.7.0 or 3.0.2.1 in order for Lanchon Re-Pit program to work... and happy with my build of KitKat until a stable Android 7.0 is out....
Cheers, Lister
Click to expand...
Click to collapse
In official cm11 the isorec recovery should work in builds after Mar 25, 2016.
If you don't use official cm11 then maybe the twrp 2.8.1.0 is the default recovery which is included in the kernel.
Maybe repit will also work with the older twrp version.
But make a backup of your rom on the external sdcard and also backup the files from your internal sdcard to your pc if something should go wrong
Hi @bauner,
First of all, thanks for the prompt reply... and apologies my delayed response back... Work has been a nightmare, been nearly a week Ive been trying to find time to sort phone out, backup data and so on... anyway....
Thanks for the sound advice, my Android 4.4.4 rom is sadly very out of date, as I was using the much loved Dirty Unicorn 8.2 (which hadn't been updated since sometime around 2015) and so therefore certainly didn't have ISORec support, if it at all??? I didn't go down the stock CM11 route, as I loved the tweaks that were in DU.
RePit may of worked, as it bawked out a couple of times, and couple of different errors. But my main error, which took some getting around... Was files and filesystem. It appeared a file got corrupt on the internal SD, and therefore could not be copied or removed. I eventually had to WIPE the partition completely (after copying what I could).
Bit the bullet, and upgraded to your great CM13 build as of now... I'm not a fan of Googles latest Material Design feel, and much prefered the retro (more colourful / 3D icons) of the older Android, ie: KitKat... that appears to have more features available to that OS. It appears no LP / MM / N have the kinda tweakability of yester-year roms.
Upgraded, RePit'd and got 1.5GB System, 6GB Data, and whatever is left (7GB) for internal SD Card. So I THANK YOU BAUNER for your advice, I'm all sorted now...
I'm prolly gonna stick with your CM13 / MM build now, until CM14 / N is stable (this is not a push or ETA... I appreciate your VAST EFFORTS and it's ready when its ready!!!) as I've found Apps that cater for bits from old OS, such as "Driving Mode" where it had built in TTS that would announce SMS / Incoming Calls, and other notifications. And various other visual elements...
Is it possible to restore a backup from a different partition table. Will it just fill those partitions with the data, or do you think it would look for the same size partitions and as they've increased, will fail to restore...
Cheers, Lister
bauner said:
In official cm11 the isorec recovery should work in builds after Mar 25, 2016.
If you don't use official cm11 then maybe the twrp 2.8.1.0 is the default recovery which is included in the kernel.
Maybe repit will also work with the older twrp version.
But make a backup of your rom on the external sdcard and also backup the files from your internal sdcard to your pc if something should go wrong
Click to expand...
Click to collapse
Lister Of Smeg said:
...
Is it possible to restore a backup from a different partition table. Will it just fill those partitions with the data, or do you think it would look for the same size partitions and as they've increased, will fail to restore...
Cheers, Lister
Click to expand...
Click to collapse
You can restore your backup without problems. It will not change the new partition sizes
Hi,
I have a somewhat general question about different OTA update application methods for OOS when Magisk and potentially TWRP is involved.
I'm still running 3T on 4.0.3 (as rooting with SuperSU broke OTA updates) and will be clean flashing Android P release once OP releases one.
Going forward, I'd like to be in a state where I have a Magisk-rooted phone, able to use TWRP, and receive OTA updates. Generally I've seen these two methods being recommended:
1) With TWRP:
a) download full image from OP site;
b) boot to TWRP, flash said image, followed by re-flashing TWRP as flashing full image restores stock recovery;
c) wipe dalvik & cache
d) reboot to TWRP & flash Magisk
2) Without TWRP:
a) restore stock recovery if using custom one;
b.1) restore stock boot image of currently installed android version by flashing it via fastboot; OR
b.2) restore stock boot image using Magisk's 'RESTORE IMAGES' option;
c) reboot and follow through with the OTA update from your phone menu (as you'd do normally with completely stock setup);
d) download stock boot image for the version you updated to, and patch it with Magisk Manager;
e) flash this boot image again using fastboot;
Now, my questions:
1. Which of the two methods above should be preferred?
2. Could either of the two methods used for OTA updates without losing data nor apps/settings?
3. Is there anything inherently different between flashing full image as in method 1) vs. going for the regular incremental OTA update as in method 2)?
4. for option 2), should b.1 OR b.2 be used? Magisk tutorials page seems to be recommending the latter.
I like to keep things simple, so if I'm going to install TWRP, then that's what I use for updates.
There's no benefit in swapping recoveries, especially since you end up with the same result.
By the way, it's been a long time since TWRP stopped patching kernels to prevent it being replace by the stock recovery. So, your step 1 is simpler:
a) download full image
b) flash it in TWRP
c) flash Magisk
And that's it. There's no need to wipe Dalvik or cache. I've not wiped either of these for years (and I've updated countless ROMs) and I've never had an issue requiring me to wipe them.
Sent from my OnePlus 3T using XDA Labs
Thanks for the reply.
Any idea if there's anything specific that needs to be taken care of depending on whether phone is encrypted or not?
Any specifics re. Android P releases, or old flashing methods should work the same?
laur89 said:
Hi,
I'm still running 3T on 4.0.3 (as rooting with SuperSU broke OTA updates) and will be clean flashing Android P release once OP releases one.
Click to expand...
Click to collapse
There is nothing stopping you from installing an Oreo version OOS (such as the latest stable 5.0.8). Who knows when stable P is coming. Maybe soon, maybe not that soon?
Just download the full zip, flash in TWRP, and flash Magisk right away (do not reboot before flashing Magisk). Same process BillGoss suggested in a previous reply.
https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
laur89 said:
Hi,
2) Without TWRP:
a) restore stock recovery if using custom one;
b.1) restore stock boot image of currently installed android version by flashing it via fastboot; OR
b.2) restore stock boot image using Magisk's 'RESTORE IMAGES' option;
c) reboot and follow through with the OTA update from your phone menu (as you'd do normally with completely stock setup);
d) download stock boot image for the version you updated to, and patch it with Magisk Manager;
e) flash this boot image again using fastboot;
Click to expand...
Click to collapse
I wouldn't mess with any of this. The phone is modded, and it seems that the above process is just trying to "trick" the system into thinking it has never been modded, so you can do an incremental update. For no actually benefit, and just making a much more complicated process.
Full zip makes for a cleaner install than incremental, anyway. You can keep your user data in either case, so again, you aren't gaining anything with incremental (versus full zip) OTA.
---------- Post added at 01:03 PM ---------- Previous post was at 12:55 PM ----------
laur89 said:
Any idea if there's anything specific that needs to be taken care of depending on whether phone is encrypted or not?
Click to expand...
Click to collapse
Well, are you encrypted, or not?
I've always had the phone encrypted, so can only say for certain about that condition. If it is encrypted, it will stay that way. There are a few TWRP builds that don't play well with encryption. But for the most part, just flash the update as stated previously, and you don't need to worry about encryption.
If decrypted, I believe flashing by TWRP will keep it that way. If you flash an update by stock recovery, I think it will force back to being encrypted. But again, I can't say for certain, as I've always been encrypted.
laur89 said:
Any specifics re. Android P releases, or old flashing methods should work the same?
Click to expand...
Click to collapse
The community beta P release is having issue with devices which are bootloader unlocked and encrypted. If the device is just one of those (or neither) and not both, then it seems to work fine in most cases.
For the stable P release, I'm guessing it will work the same as the "old flashing methods" which has been described above. But we won't know for certain, until a stable P build is released.