I recently got my Nexus 6 back with a new (to me) motherboard installed. After allowing multiple OTA updates to the current (March 2017) firmware, getting my apps installed and setup, etc., I went to make some changes to the /system partition.
Knowing that /system is mounted read-only normally, I downloaded the current copies of adb and fastboot, as well as TWRP. I booted my phone into fastboot, ran fastboot boot twrp.img, mounted /system, and used adb to make a change. I then booted normally, but didn't see the effect of the change, so I checked with adb, and the change wasn't there. OK, that could be a few things, so I went back into TWRP, and -- this is where it gets weird -- saw the change.
Yes, if I boot up on TWRP and mount /system, I see whatever changes I have made to the /system partition visible when running TWRP, but when I boot the stock bootloader, I don't see any of them. It is behaving as if there are two /system partitions: one visible when booting with TWRP and the other visible when booting with stock.
I've never seen this before. Any thoughts?
NoelJB said:
...
Knowing that /system is mounted read-only normally, I downloaded the current copies of adb and fastboot, as well as TWRP. .
I've never seen this before. Any thoughts?
Click to expand...
Click to collapse
Is TWRP the latest version 3.1.0.0?
Did you use a recent rootexplorer?
For instance prev, version ES file explorer does not work with recent Android.
When booting TWRP-recovery normally the system partition needs to be mounted manually.
Why do you use adb to make changes to system, instead of the file manager of TWRP?
> Is TWRP the latest version 3.1.0.0?
Yes.
> Did you use a recent rootexplorer? For instance prev, version ES file explorer does not work with recent Android.
Not rooted, hence using TWRP to edit the /system partition.
> When booting TWRP-recovery normally the system partition needs to be mounted manually.
Yes, hence my comment about mounting /system.
> Why do you use adb to make changes to system, instead of the file manager of TWRP?
What would it matter? The contents of /system shown by the TWRP file manager are identical to those shown by adb shell. My problem is that the contents don't match what I see when booting with the stock bootloader. As I said, it is as if TWRP were showing one /system partition, and the stock bootloader were showing another.
NoelJB said:
... adb instead of the file manager of TWRP.....
What would it matter?.
Click to expand...
Click to collapse
.... using a shell and an 2nd device is rather different. I prefer the filemanager; it's more direct.
Sorry no more thoughts....
Lemme guess...
You're on the bone stock kernel...
If that's the case... There's a thing that keeps stuff from working... I wish I could be more help but... It's been almost 2 years since I've seen this...
I THINK you can flash any other kernel and it will solve your problem... Or maybe one of the root solutions would do it too...
Sent from my Nexus 6 using Tapatalk
did you solve it?
Related
Hi developers. I am sorry for posting this. I spent the last week trying to solve it by myself with no hope. This is my second time installing something on a phone, but it is my only phone, so I beg anyone for a help...
-What I did:
Some days ago I downgraded to this ROM C5503_10.1.1.A.1.310_GLOBAL-LTE.ftf to use DoomLord rooting script. I did it with flashtool for linux and I applied his .bat step by step in the terminal since windows would not detect my phone.
It worked. I had root for some days, but I was still annoyed by sony default android. So I decided to install Cyanogenmod.
I unlocked the device with sony official system and wen't straight to this instructions, before the first reboot
wiki.cyanogenmod.org/w/Install_CM_for_yuga
I booted succesfully in CWM, followed everything as it says there. But that's where weird things happened:
-The problems:
-The backup
I tried, it wouldn't mount /sdcard. Since I don't understand much about this, I thought it was normal. The next choice was sdcard1, I backed up there. Or so I thought...
-The factory reset
I factory reset, again, not mounting sdcard. Here is the message that shows when I try this now:
can't mount /data!
Error mounting /sdcard.android_secure
Skipping format...
Data wipe complete.
Since it said it is complete, I went on installing the zip file from my sdcard1. Both CM 10.2.1 (dogo, the right one for my phone) and the appropriate GAPPS.
Now it loops on the CM loop animation and I have to remove the battery...
-The restore problem
It still boots on the recovery mode. So I tried recovering my backup from sdcard1. But the image name is 1970.01.01.00.03.16. And it says "md5 mismatch"
I tried flashing again the stock rom with flashtool. The proccess goes on but nothing happens. I still have CWM and the boot loop.
I read elsewhere someone with a similar problem who solved using sony "emma" software. I installed it, it won't even recocnize my phone.
It recocnizes that there is a phone, but don't know which one.
But that has alway been the case with windows. I haven't been able to do anything in windows other then accessing the sdcard (when the phone worked).
Is there something I can do? I imagine that somehow, for some reason, the /data and /sdcard partitions got corrupted. I imagine I would need to repartition this and install again, but I have no idea how this happens on phones...
I can mount /system /cache and /storage/sdcard1. just /data I can´t. Says "error mounting /data"
This is my only phone and a vey recent $400 thing. I was very stupid to do that withouth a replacement and really need this phone. I greatly appreciate any help...
I found this post forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/ searching the internet. Is it possible that this would solve my problem? or would it finish bricking the phone?
Here's what you'll need:
Working recovery, basic knowledge of adb & the shell
Parted (download here)
stock PB31IMG.zip
Note also that I had run unrevoked forever (so my phone was S-OFF) ... I'm not sure if that's required or not.
So, grab parted from the link above. Now you need to extract the individual binaries from the .zip (the 6 files in the sdparted folder within the zip), ideally to your android-sdk\tools directory. Now push all 6 files (adb push [file] /sbin/). Next, we need to make them useable, so go into the shell (adb shell). Change to your /sbin/ directory, and run: chmod 0755 <file> on each of the 6 files.
Now, we need to fix the partitions. This is assuming that the partitions are there, just the wrong format (which is what happened to me .. I accidentally made them FAT32 instead of ext). So, run the following: parted /dev/block/mmcblk0 mkfs ext2. It will ask if you want to continue, hit yes. When it asks for the partition number, enter 1. Next, when it asks for the format, enter ext2. Let it do its thing. Now, once it's done, run parted again. This time, enter partition 2 (everything else is the same).
Click to expand...
Click to collapse
Hello guys, i need a little help.
I was looking for some tutorial to unlock dev cameras on my xt1225. I found one tutorial and he said to edit Build.prop, i'm noob at this, so I downloaded a file manager and entered in /system/, copied build.prop for backup, and edited the original build.prop. I restarted my phone and now i'm stuck in the boot screen.
I don't know for what reason but ADB (properly configured) does not show any device connected to the PC so I can't use the commands adb pull and adb push.
I have tried copy the backup of build.prop and overwrite the modified one, but no sucess (I did it in TWRP file manager)
I'm using XT1225 5.0.2 Stock ROM.
Edit: So, i tried to change his permissions (or think that i tried, in twrp filme manager with chmod command,), now the phone runs the boot animation and turn black, before he did not do it, before he just stuck in the white screen with motorola logo. (Tried chmod 644, 755, 777)
Sorry for bad english.
Neblue said:
Hello guys, i need a little help.
I was looking for some tutorial to unlock dev cameras on my xt1225. I found one tutorial and he said to edit Build.prop, i'm noob at this, so I downloaded a file manager and entered in /system/, copied build.prop for backup, and edited the original build.prop. I restarted my phone and now i'm stuck in the boot screen.
I don't know for what reason but ADB (properly configured) does not show any device connected to the PC so I can't use the commands adb pull and adb push.
I have tried copy the backup of build.prop and overwrite the modified one, but no sucess (I did it in TWRP file manager)
I'm using XT1225 5.0.2 Stock ROM.
Edit: So, i tried to change his permissions (or think that i tried, in twrp filme manager with chmod command,), now the phone runs the boot animation and turn black, before he did not do it, before he just stuck in the white screen with motorola logo. (Tried chmod 644, 755, 777)
Sorry for bad english.
Click to expand...
Click to collapse
I don't know about the chmod command, but the TWRP "Fix Permissions" does not work with our current (old) version of TWRP. It just messes up the phone.
1) since you have TWRP, did you make a back-up? If so, restore that. Problem solved.
(If no back-up, why not? That's one of the reasons we use TWRP, so we can restore a good backup when we screw something up.)
2) If you have TWRP, that means your bootloader is unlocked. GOOD.
Boot back into recovery, reflash your ROM. Problem solved.
Reboot, make sure everything is OK, then make a TWRP back-up!
EDIT: OOPS. I see you are using stock 5.0.2, not custom ROM. OK, I hope you made a backup. See #1.
There may be other solutions but all the ones I find seem to involve pushing new files to your phone and you say you can't do that...
______
Also in our version of TWRP, if you wipe cache do NOT attempt it from the "install" prompt (There's an option there to wipe cache. Ignore it.) Only wipe Cache from the "Wipe" section/Advanced Wipe/checkmark Cache and Dalvik Cache. (Even though we use ART, habits die hard.)
OK, I restored a backup following your thread, but before, searching for a solution, I formated the cache/data partition from f2fs to ext4 (so dumb), there's a way to undo it? There's no f2fs wipe option in twrp, I think I'll need to wait to a new version of twrp? Or flashing with rsd lite will do it?
Everything is working fine.
Thanks for your answer.
Sent from my XT1225 using XDA Free mobile app
Neblue said:
OK, I restored a backup following your thread,
Everything is working fine.
Thanks for your answer.
Click to expand...
Click to collapse
Glad your phone is back up and running! Aren't you glad you made a back-up?
Not sure about the F2Fs stuff. I haven't messed with it.
Yes, I agree we need a newer version of TWRP. I would gladly donate money toward to the developer!
Hi guys, I've been using TWRP for a long time, but this one is a bit of a head-scratcher for me. I'm running stock Android MMB29S on my N6, unlocked bootloader, and unrooted. I decided to install TWRP 2.8.7.1 and then root it with Beta supersu 2.66. The fastboot flashing of TWRP went fine the first time, and I opted to leave TWRP read-only. But I didn't install supersu right afterwards. Rather, I rebooted into system first, and downloaded supersu. When I attempted to reboot into recovery again to flash supersu, I'm finding out that stock recovery has overwritten TWRP. Ok, no problem, I re-flashed TWRP, but this time I allowed it to modify the system (instead of read-only). Now, I'm unable to see anything under /sdcard or any of the other folders when I go to flash the zip. Under the "Mount" Menu, I see that only "cache" is checked. Didn't want to mess with anything there.
Rebooting into system now gives me the "Your device is corrupted..." spiel, which I'm not concerned about, but I really do need to be able to see files in TWRP. Would re-installing TWRP be an option or even a different version of it?
mount system. if its still empty after that, use twrp to locate the right place in the filesystem. yes, like a file explorer app twrp can act
The solution to my problem was actually as simple as just removing the lockscreen passcode. I was wondering why TWRP was asking for that in the first place. Once I removed the lockscreen PIN and went back into TWRP I was able to see all the files. Happily rooted now. :good:
Thanks to @seadersn and @SGCMarkus, Markus's new TWRP makes things extremely simple now.
What you need:SGCMarkus's TWRP
fstab.judypn with forceencrypt set to encryptable.
magisk
and the .magisk file
Instructions:
1. Follow the instructions to boot and install TWRP on SGCMarkus's TWRP thread
2. While you're still in TWRP, mount vendor and push the fstab.judypn with:
Code:
adb push path/to/fstab.judypn /vendor/etc
3. Format data via TWRP.
4. Push the .magisk to /data (For dm-verity reasons. It will restore the fstab.judypn with forceencrypt enabled) with:
Code:
adb push path/to/.magisk /data
5. Flash Magisk.
You're done! No bootloops this time. XD
i want to try this at some point. When i did before, the screen was black. Thanks for the guide!
I need to get US pie on my device but will be doing this
i got some issues..
i cant mount system_root and i saw there is no /system_root/system/priv-app folder... so i took modified LGSettings.apk to sd card and i put it to /system/system/priv-app/LGSettings... then i format userdata in fastboot,i got twrp loop.....
dreamss29 said:
i got some issues..
i cant mount system_root and i saw there is no /system_root/system/priv-app folder... so i took modified LGSettings.apk to sd card and i put it to /system/system/priv-app/LGSettings... then i format userdata in fastboot,i got twrp loop.....
Click to expand...
Click to collapse
Flash the magiskpatched boot img included in the files
I just had my bootloader unlocked. I am trying to install TWRP, but if I flash stockpiemagisk.img or TWRP-judypn-2019-07-01.img then use the buttons to choose a factory reset I just get bootloops. I select yes both times, just like normal and it loops until going to a fastboot screen. I can then flash the original magisk_patched.img I got from the guy who unlocked my bl, but no TWRP. Even he wasn't sure why this is happening. Any ideas anyone?
Also, in case its related, I lost download mode and can't get that back even by flashing an original backup of laf_b or the lgup compatible laf. I had download mode and flashed Pie before the bl unlock...
Edit: I got download mode back. Turns out when he was unlocking the bootloader he flashed abl_b incorrectly. Once I flashed it correctly DL mode works... Now for TWRP...
NVM.... found the problem...
I have an issue. After clearing the userdata procedure, this attached images is what I get. It's a reddish boot-up screen. The Active Slot also defaulted to B (as opposed to A). I have a fastboot-loop. I am wondering where I went wrong. I completed a successful procedure on another device hours ago. LGUP does not function as well. The phone defaults to Fastboot.
I am able to get to TWRP but the fastboot-loop has changed. The image attached is what I get. I suppose in my attempt to remedy, the wrong Laf files have been flashed. It's V405UA20a
Hello mister
Actually is it possible to flash this stockpie.img on a V406EBW ?
Regards
Fred
avaie said:
I have an issue. After clearing the userdata procedure, this attached images is what I get. It's a reddish boot-up screen. The Active Slot also defaulted to B (as opposed to A). I have a fastboot-loop. I am wondering where I went wrong. I completed a successful procedure on another device hours ago. LGUP does not function as well. The phone defaults to Fastboot.
Click to expand...
Click to collapse
I have exactly the situation you described (fastboot loop + pink letters screen when I try to get into DL mode). If you've managed to rectify this, can you please give me directions. Thanks.
crubbish said:
I have exactly the situation you described (fastboot loop + pink letters screen when I try to get into DL mode). If you've managed to rectify this, can you please give me directions. Thanks.
Click to expand...
Click to collapse
Hi - I eventually lost root and the system factory-reset after an attempt to boot into TWRP. I have scheduled to have VLAD reflash the entire phone. My bootloader is unlocked though but don't think much can be done. There might be other variables that might be affected.
If there is a guide to using Octoplus, it will be appreciated. It also seems telegram is the new medium for development.
avaie said:
I have scheduled to have VLAD reflash the entire phone. .
Click to expand...
Click to collapse
That's what I plan to do as well. Thanks for responding!
crubbish said:
That's what I plan to do as well. Thanks for responding!
Click to expand...
Click to collapse
All the best.
will try out to follow up this info
When I follow step 3 "Format data via TWRP", at the end of the format it says:
"Updating partition details...
...done
Full SELinux support is present.
WTP Enabled
Formatting Data using mke2fs...
Done.
You may need to reboot recovery to be able to use /
data again.
Updating partition details...
...done
UNABLE TO MOUNT STORAGE, DECRYPTION NEEDED FIRST"
I don't think that's good... Or is it?
Please Clarify/Help
I have managed to get TWRP installed and working but did not notice to do this. I went ahead and used Android already only to find that I need to do this.
I have booted into TWRP but cannot select vendor to mount it. Everything except system and vendor (and USB-OTG because there is not attached) will let me check them. But not vendor.
Do I have to go all the way back and re-install TWRP and to this before I do ANYTHING else? Do I have to do this while I am still in TWRP loaded from the image on my PC?
I realize this will loose all I have done within Android and that is the price I pay for not reading in detail. But I want to make sure this is the last time.
Thanks!
Not What I Expected - Decryption Failed!
I went ahead and re-installed TWRP from fastboot per the Markus thread After rebooting back into TWRP I then followed instructions in the 1st post here.
I could not mount vendor but I saw messages saying it was busy. So I assumed it was not unmounted and went ahead with the push to /vendor/etc. It reported successful from adb. And in TWRP file manager I can see a file named /vendor/etc and in the terminal I can cat its contents which look like what I see on my PC.
I then wiped the /data only using advanced wipe and it used makefs, not format.
I then pushed .magisk to /data and it too reported successful from adb.
I then flashed magisk and that seemed successful as well. Inside to TWRP's file manager, I was able to see the .magisk and various folders under /data. This seemed promising enough.
I finally rebooted to system and got shown what is in the attached screenshot. At that point, I had no option but to agree to the reset. When I touched that button, I was returned to TWRP. So I powered off from TWRP and tried to restart the phone. Once again I get the same decryption unsuccessful.
So I seem to be in a TWRP loop. How to proceed? Thanks
whitedavidp said:
I went ahead and re-installed TWRP from fastboot per the Markus thread After rebooting back into TWRP I then followed instructions in the 1st post here.
I could not mount vendor but I saw messages saying it was busy. So I assumed it was not unmounted and went ahead with the push to /vendor/etc. It reported successful from adb. And in TWRP file manager I can see a file named /vendor/etc and in the terminal I can cat its contents which look like what I see on my PC.
I then wiped the /data only using advanced wipe and it used makefs, not format.
I then pushed .magisk to /data and it too reported successful from adb.
I then flashed magisk and that seemed successful as well. Inside to TWRP's file manager, I was able to see the .magisk and various folders under /data. This seemed promising enough.
I finally rebooted to system and got shown what is in the attached screenshot. At that point, I had no option but to agree to the reset. When I touched that button, I was returned to TWRP. So I powered off from TWRP and tried to restart the phone. Once again I get the same decryption unsuccessful.
So I seem to be in a TWRP loop. How to proceed? Thanks
Click to expand...
Click to collapse
Well, as they say, if at first... I went through the steps here again. I made sure I hit the format button instead of wipe. And I made triple sure that everything was where it seemed to need to be and looked right. When I finally rebooted to system, I am now in Android setup as expected. To see if there is still encryption (ie, TWRP can see and backup /data) remains to be seen. Cheers
whitedavidp said:
Well, as they say, if at first... I went through the steps here again. I made sure I hit the format button instead of wipe. And I made triple sure that everything was where it seemed to need to be and looked right. When I finally rebooted to system, I am now in Android setup as expected. To see if there is still encryption (ie, TWRP can see and backup /data) remains to be seen. Cheers
Click to expand...
Click to collapse
Sadly, once finished with a minimal Android setup I went back into TWRP and /data shows nothing. In backing up, it shows /data as 0 bytes. So I presume this means I am still encrypted. Is there no way out of this hell? Thanks
whitedavidp said:
Sadly, once finished with a minimal Android setup I went back into TWRP and /data shows nothing. In backing up, it shows /data as 0 bytes. So I presume this means I am still encrypted. Is there no way out of this hell? Thanks
Click to expand...
Click to collapse
Here's the thing I would try. Load up LGUP and reload a stock kdz. Make sure that before you begin futzing with the phone, you are booting from Slot A.
Then retrace all the steps carefully. And don't set up anything on the phone until you have reached nirvana (bootloader unlocked, unencrypted, Magisk installed).
You'll get there.
[NG]Owner
I recently bought an unlocked Pixel 5 from Amazon, only to discover it is (apparently) a VZW that was carrier unlocked, and so the OEM Unlock is not available. I am slowly making my peace with that fact, but am curious how much leeway I have to get at lease *some* more control.
When I boot into stock recovery, I have the option to mount /system. I am hoping this means I can pull, edit, and then push the build.prop and possibly other files as well. Perhaps also push the superuser binary. However, I am unable to detect my phone when I mount /system.
My system specs:
Windows 10 Pro
Version 21H2
OS Build 19044.2728
I have installed the latest drivers from Google.
I am able to detect and interact with my device in both ADB and Fastboot.
I was hoping being able to mount /system in the recovery menu meant I could use ADB shell and browse around the /system folder and tweak a few things. However, my computer behaves as though NOTHING is attached when I go into recovery. No "drivers not found" messages, no mysterious unidentified anything showing up in device manager.
Can anyone give me guidance as to how to get this working? Or am I not understanding how this is supposed to work?
Pixels do not have a recovery partition.; recovery lives in /boot alongside ramdisk and system kernel. Recovery is largely unnecessary from a modding perspective because of the ease of which we can directly flash device partitions.
Ok, but I can boot into stock recovery via "adb reboot recovery". From there I have the option to "Mount /system". I am hoping to be able to do that, then use adb to pull and then alter the build.prop file.
I can not flash device partitions because I cannot unlock the bootloader (I apparently have a Verizon phone.)