Hey guys and gals.
Been playing with my new v410 and wanting to run adoptable storage.
Fully rooted and funning cm13. I have enabled the adoptable storage option with a 64gb sd card and when the tablet is on it works perfectly. Problems come when in TWRP. i know 2.8.5.0 does not have support for adoptable but 2.8.7.0 seems to work...at least kind of when it wants.
I have tried a port of 3.0.0.0 but it does not work well at all and locks up when trying to access the SD while its Adopted. Anyone know if there is a port that is currently working? I'm sure it would help a few people on here.
What is adoptable storage
Can u tell me ware the from is an what recovery u r using...I just rooted my tablet an can't find any rooms or recovery for the v410
Related
Has anyone been able to install xposed on the moto g4?
taxi333 said:
Has anyone been able to install xposed on the moto g4?
Click to expand...
Click to collapse
I recently got the discounted Amazon version, unlocked bootloader, flashed it to Motorola stock (no Amazon crap) installed twrp, rooted the phone and finally installed xposed version86 all from the XDA threads for this device and the base xposed install thread. Easy as pie!
zinchalk said:
I recently got the discounted Amazon version, unlocked bootloader, flashed it to Motorola stock (no Amazon crap) installed twrp, rooted the phone and finally installed xposed version86 all from the XDA threads for this device and the base xposed install thread. Easy as pie!
Click to expand...
Click to collapse
Hi, which Xposed version? arm, arm64 or x86?
arm works for me
odd as the processor is 64 bit
I'm trying to flash the Xposed zip, but I added an SD card as adoptable storage and can't figure out how to flash it from TWRP. TWRP doesn't see the storage (because it's encrypted, I'm assuming). Does anyone know how I can go about flashing the zip? Also, is there a reason to use the arm zip over the arm64 zip if this phone has a 64 bit processor?
beano311 said:
I'm trying to flash the Xposed zip, but I added an SD card as adoptable storage and can't figure out how to flash it from TWRP. TWRP doesn't see the storage (because it's encrypted, I'm assuming). Does anyone know how I can go about flashing the zip? Also, is there a reason to use the arm zip over the arm64 zip if this phone has a 64 bit processor?
Click to expand...
Click to collapse
Put the xposed.zip in the same directory as your adb and fastboot files, not on the SD card.
put it in the main storage on the phone or use MTP from TWRP and install it from your PC
http://www.androidinfotech.com/2016...-j7-prime-g610m-marshmallow-install-twrp.html
I was looking around online for a possible recovery and came across this twrp for j7 prime G610 M. It is a unofficial twrp. Actually theres 2 twrp files.. im not sure who made the twrp recoverys but it might work.. i know what caught my eyes was in earlier versions of cwm and twrp there was encryption blocking the mounting of internal storage and external storage.. in theses 2 twrps it says nothing about the encryption and says you can mount both storages and flash zips from them. Im not sure if this is the same recovery that was already posted here before or if its someone elses builds of twrp.
This is my phone information hopefully this twrp works id love to make a back up and flash supersu.
Official or Unofficial, twrp cannot mount data if it's encrypted.
TWRP just doesn't support Samsung encryption at the moment.
hi friend
ashyx said:
Official or Unofficial, twrp cannot mount data if it's encrypted.
TWRP just doesn't support Samsung encryption at the moment.
Click to expand...
Click to collapse
Hello friend sorry for asking this .... this patch makes it work properly this twrp?
Sorry for asking that but i am newbie and i want to install a custom rom on sm-g610m / ds
Greetings from Costa Rica Central America.
I've given my girlfriend my Nexus Player updated to 7.1.1 with StickMount running for an NTFS formatted hard drive. Anyways at night lately it's been going to TWRP on her automatically. I am assuming there is some kind of OTA update. So this leads to two questions:
1) Which directory is this update stored in and I'm assuming I can flash it in TWRP, right?
2) Should I reflash SuperSU after the update in order to ensure root is maintained?
Thanks so much in advance.
As the title states, is there any way to achieve root on the newest build for the US996 unlocked version? I have the bootloader already unlocked, but unfortunately it had already been updated to the latest software, I can get TWRP to install just fine but when I try to install Magisk after wiping data in twrp, I keep getting the same problem on bootup where it says "Encryption unsuccessful" and the only way I can get around that is by flashing back to 100% stock and factory resetting. Am I missing something? Is there any way to get around that problem? I also tried installing a custom rom based on stock (alpha rom) but that didn't work either, any help is appreciated.
well for anyone wondering, I was able to get root and a custom ROM installed. Instead of wiping data like so many guides say to do, I put magisk and the alpha ROM file on an external SD card, skipped decryption in TWRP, mounted the SD card, and installed the ROM and magisk. Didn't have to bother with encryption or anything weird. I made sure to do it after a clean install to minimize any problems that may arise from not wiping. I haven't found a way to do it without an external SD card sadly.
@rusty815, thanks for following up on your own thread with the solution. I just cancelled a purchase for an H918 after reading too late that it won't take the dirtycow root exploit after H91810j, and just bought a US996 instead. I don't know what update the US996 will be on, so if I do end up with US99610n, your post will be very helpful.
Need Help!! LG V20 US99610n
rusty815 said:
well for anyone wondering, I was able to get root and a custom ROM installed. Instead of wiping data like so many guides say to do, I put magisk and the alpha ROM file on an external SD card, skipped decryption in TWRP, mounted the SD card, and installed the ROM and magisk. Didn't have to bother with encryption or anything weird. I made sure to do it after a clean install to minimize any problems that may arise from not wiping. I haven't found a way to do it without an external SD card sadly.
Click to expand...
Click to collapse
I have that same phone and same firmware. Could you please submit the links for what you used to root your phone?
Please OP be our savior and post how to root the vs996 and install twrp on 10n
Hi! I've updated my device to Oreo and I'm wondering if there is a way to root it. Kinda of a newbie here, rooted my LG G2 and LG L3 E400 using guides.. can someone help me please?
Download Magisk, patch the bootloader, copy it off to your PC, flash it back on in fastboot, job jobbed.
dj9364 said:
Hi! I've updated my device to Oreo and I'm wondering if there is a way to root it. Kinda of a newbie here, rooted my LG G2 and LG L3 E400 using guides.. can someone help me please?
Click to expand...
Click to collapse
You can root it the same way as on Nougat, make sure bootloader is unlocked, flash TWRP 3.1.10 and latest SuperSU and you are done...just this.
Works flawless, i already did it on mine.
Guys is possible to root the phone without sd card?
Dottorfox said:
Guys is possible to root the phone without sd card?
Click to expand...
Click to collapse
There is a problem in twrp with oreo, after the first time you boot in oreo, twrp can't mount /data partition, so to root you must format data (NOT WIPE), flash magisk or SU and then reboot. After the boot you can't no more mount data in recovery. Probably the fix will come.
Dadda98 said:
There is a problem in twrp with oreo, after the first time you boot in oreo, twrp can't mount /data partition, so to root you must format data (NOT WIPE), flash magisk or SU and then reboot. After the boot you can't no more mount data in recovery. Probably the fix will come.
Click to expand...
Click to collapse
There is no doubt that fix will come because S9 has the exact same problem and it got fixed already. We have to wait for US997 variant to get an update so devs can start working on this issue.