Related
OK, so I just got my Nexus S4G two days ago, and I'm ready to root. My phone out of the box has 2.3.4 on it.
I follow this tutorial: http://www.droidfiles.us/nexus-s-4g/root-nexus-s-4g/ the link to which was provided by a good XDA'er. I get the bootloader unlocked and install CWR (recovery-clockwork-3.0.2.4-crespo.img) and that goes fine.
That's when things stop going fine.
First, I try to create a Nandroid backup, and that process seemingly completes fine until i note that the process says it couldn't mount /data. I don't worry about it.
So, I go to Mounts and Storage to prepare to push SuperUser.zip and I tell CWR to "Mount USB Storage" and I wait as directed, but the USB storage never mounts. I try mounting USB Storage and mounting /sdcard, neither of which work, so I can't push SuperUser.zip.
Figuring I did something wrong, I decide to restore from Nandroid, only to have CWR tell me that the MD5 checksum is incorrect and now I have no clean, base Nandroid to restore to.
Then I do some digging, and discover that there's a new CWR for the NS4G at Koush's site and I download the file (recovery-clockwork-3.1.0.0-crespo4g.img) from there, push it to my phone using fastboot's recovery command and start it up.
It doesn't work.
Clicking any of the options (like mounting partitions, or restarting/powering down the phone) causes the screen to go blank and just display the CWR logo in the middle of the screen. The only solution to get out of those loops is to pull battery and restart.
So, now, I'm wondering what to do.
I go back into fastboot, relock the bootloader and I now wait for a reliable root method to root a 2.3.4 NS4G on a Mac.
My questions are:
Where can I get a stock ROM to completely start over from scratch and even remove the recovery I've installed <-- found a base ROM here: http://forum.xda-developers.com/showthread.php?t=1078213
Is there a fully reliable way to root the NS4G on a Mac, and if so how? (I've looked at this thread: http://forum.xda-developers.com/showthread.php?t=878446 and it looks problematic as well).
Look in the dev section, stickies at top, the one talking about ns4g cdma. You have the su zip already. Put the cwm 3024 img file in the same directory as fastboot. You won't use adb. Boot into bootloader and do the fastboot command to unlock. Phone is wiped. Boot into phone normally and log in with gmail. On the phone, mount the device as usb so you can just copy the su zip to the root of the sd card.unmount phone on the Mac side then the phone side. Boot phone into bootloader. Do the command to fastboot the cwm into the phone again. Once finished, choose recovery on bootloader. It will boot into cwm. Choose install zip from card. Choose pick zip. Install su. Reboot into normal phone. Download busybox and a file manager you like that can handle root. With file manager, go to /system/etc and look for the sh file mentioned in the guide and add .old to the end of the file. If su pops up asking for permissions then you know everything is working. Boot into bootloader again. Install cwm again then choose recovery again. Once in cwm do wipe of caches and factory reset and dalvik. Go back and do backup with nandroid. Boot into normal phone. Sign into google again. Update profile and prl them you should be set. Pretty much that's what I did and it worked the first time around.
Follow the Mac guide in the link
herbthehammer said:
Look in the dev section, stickies at top, the one talking about ns4g cdma. You have the su zip already. Put the cwm 3024 img file in the same directory as fastboot. You won't use adb. Boot into bootloader and do the fastboot command to unlock. Phone is wiped. Boot into phone normally and log in with gmail. On the phone, mount the device as usb so you can just copy the su zip to the root of the sd card.unmount phone on the Mac side then the phone side. Boot phone into bootloader. Do the command to fastboot the cwm into the phone again. Once finished, choose recovery on bootloader. It will boot into cwm. Choose install zip from card. Choose pick zip. Install su. Reboot into normal phone. Download busybox and a file manager you like that can handle root. With file manager, go to /system/etc and look for the sh file mentioned in the guide and add .old to the end of the file. If su pops up asking for permissions then you know everything is working. Boot into bootloader again. Install cwm again then choose recovery again. Once in cwm do wipe of caches and factory reset and dalvik. Go back and do backup with nandroid. Boot into normal phone. Sign into google again. Update profile and prl them you should be set. Pretty much that's what I did and it worked the first time around.
Follow the Mac guide in the link
Click to expand...
Click to collapse
I'm going to give your method a try. Thank you for your rapid response...
I see the subtle change you suggested: simply rebooting after unlocking and pushing recovery, and moving SU to the device via USB. Wish I'd thought of that.
(I'm still concerned about the Nandroid issue I reported. But I'll have to avoid any new ROMs for the time being, until I can get an answer for my Nandroid problem...)
My first nandroid choked. After root and final recovery install, I cleared all the caches it was *****ing about the first time, went in normally to make sure everything was okay, then went back and nandroid and no errors the second time. I probably will just stay with rooted stock but I would not flash other stuff until the dust settles and many of the bugs are worked out of the roms and kernels before jumping in.
TonyArmstrong said:
I'm going to give your method a try. Thank you for your rapid response...
I see the subtle change you suggested: simply rebooting after unlocking and pushing recovery, and moving SU to the device via USB. Wish I'd thought of that.
(I'm still concerned about the Nandroid issue I reported. But I'll have to avoid any new ROMs for the time being, until I can get an answer for my Nandroid problem...)
Click to expand...
Click to collapse
If cwm mount won't work then boot into the phone normally and copy over the file like usual is the only other quick and easy way to do it that I could think of at the moment the snafu happened. Yeah the way I did it might not have been the most efficient way but it got me past the hurdle that cwm made quickly. In the end, the result is the same so no big deal.
I don't know if cwm backs up wimax keys so I did it manually. There's a post on how to do it, I don't know if it's in this section. It might be dev?
I wanted to flash PSX Pure Speed Experiment 4.4 rom but I got the " Failed. E:Error executing updated binary in zip '/sdcard/psx_mako_kk_v1..." message mentioned in the OP. I tried the solution posted there, which was to download a patched multirom version of TWRP recovery using the flashify app from the play store. This all seemed to work out fine, and I booted into recovery to flash the rom. Now, this could just be due to my ignorance because the version of TWRP I flashed is 2.6.3.2 (I originally had 2.3.0.1 I believe), but when I wiped my phone, then went to install, there wasnt anything listed in the root of my sd card folder. I tried rebooting TWRP and when I tried again it listed a folder named TWRP there but nothing else. Subsequent reboots yielded nothing. At this point I dont even want to flash the 4.4 rom, I just want to reflash my old CM10.1 rom and be done with it. Any help is greatly appreciated
sropedia said:
I wanted to flash PSX Pure Speed Experiment 4.4 rom but I got the " Failed. E:Error executing updated binary in zip '/sdcard/psx_mako_kk_v1..." message mentioned in the OP. I tried the solution posted there, which was to download a patched multirom version of TWRP recovery using the flashify app from the play store. This all seemed to work out fine, and I booted into recovery to flash the rom. Now, this could just be due to my ignorance because the version of TWRP I flashed is 2.6.3.2 (I originally had 2.3.0.1 I believe), but when I wiped my phone, then went to install, there wasnt anything listed in the root of my sd card folder. I tried rebooting TWRP and when I tried again it listed a folder named TWRP there but nothing else. Subsequent reboots yielded nothing. At this point I dont even want to flash the 4.4 rom, I just want to reflash my old CM10.1 rom and be done with it. Any help is greatly appreciated
Click to expand...
Click to collapse
Reboot the phone and then connect it to your PC and check to see if the PSX ROM file is there. If not, redownload the file and save it in the root of the SDcard. As for the TWRP folder that has nothing in it, delete it. Then try to boot into recovery and flash the PSX ROM, also just making sure that the checkbox for "System" in mount section is unchecked. BTW, is your a multiROM patch for TWRP?
taodan said:
Reboot the phone and then connect it to your PC and check to see if the PSX ROM file is there. If not, redownload the file and save it in the root of the SDcard. As for the TWRP folder that has nothing in it, delete it. Then try to boot into recovery and flash the PSX ROM, also just making sure that the checkbox for "System" in mount section is unchecked. BTW, is your a multiROM patch for TWRP?
Click to expand...
Click to collapse
Thanks for the reply, but when I try to mount my phone, my computer acknowledges that I've connected a device with a sound, but it doesnt show up as a storage device. when I go into devices and printers I can find my phone but it only shows up as an ADB device
And yes to answer your question it is a multiROM patch for TWRP
sropedia said:
Thanks for the reply, but when I try to mount my phone, my computer acknowledges that I've connected a device with a sound, but it doesnt show up as a storage device. when I go into devices and printers I can find my phone but it only shows up as an ADB device
Click to expand...
Click to collapse
Do you have "USB debugging" checkbox, in Developer Options, checked? Also, try reboot your PC and reconect your phone to see whether it shows up as a storage device.
sropedia said:
I wanted to flash PSX Pure Speed Experiment 4.4 rom but I got the " Failed. E:Error executing updated binary in zip '/sdcard/psx_mako_kk_v1..." message mentioned in the OP. I tried the solution posted there, which was to download a patched multirom version of TWRP recovery using the flashify app from the play store. This all seemed to work out fine, and I booted into recovery to flash the rom. Now, this could just be due to my ignorance because the version of TWRP I flashed is 2.6.3.2 (I originally had 2.3.0.1 I believe), but when I wiped my phone, then went to install, there wasnt anything listed in the root of my sd card folder. I tried rebooting TWRP and when I tried again it listed a folder named TWRP there but nothing else. Subsequent reboots yielded nothing. At this point I dont even want to flash the 4.4 rom, I just want to reflash my old CM10.1 rom and be done with it. Any help is greatly appreciated
Click to expand...
Click to collapse
ok when you wiped your rom did you just do a factory reset or a internal sd wipe as well. Also you should try and use 2.6.3.3. Also you have to remember where it is you save your stuff or place everything in 1 specific folder. May I suggest you start over with downloading rom and putting it in a folder created by you like !Flash... using "!" will ensure its the first folder you see.
Also your error also can be fixed by simply rebooting your recovery as its been what I used to fix that error
playya said:
ok when you wiped your rom did you just do a factory reset or a internal sd wipe as well. Also you should try and use 2.6.3.3. Also you have to remember where it is you save your stuff or place everything in 1 specific folder. May I suggest you start over with downloading rom and putting it in a folder created by you like !Flash... using "!" will ensure its the first folder you see.
Also your error also can be fixed by simply rebooting your recovery as its been what I used to fix that error
Click to expand...
Click to collapse
I did a full wipe like I usually do. I would use a different version of TWRP if I knew how to change it from within TWRP. I have a follder titled ROOT that I keep all my ROMs and whatnot in, but the problem is that literally none of the folders in my internal storage are showing up from within TWRP. I can't check to see if USB debugging is enabled because theres no operating system on my phone; like I said, I did a full wipe. The fact that no folders show up also means that it doesnt recognize the backup I had. My computer still won't recognize my phone as a storage device after mounting in TWRP. Maybe I'm doing something in the wrong order? Restarting my computer didn't help.I really need to get my phone working on ANY ROM, and I appreciate all the help so far
Guys i got my oneplus 5 in the mail yesterday and I like it, but I think i ****ed up...big time. please somebody help me out.
i was following this guide: https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877
to root my oneplus 5 so i can use Adaway. Ive rooted and installed a custom rom many times on my oneplus one before so I didn't really have any issues.
but then when I got to "Gaining root access" part, I was a little confused because I wasn't sure what step to take, so i Just did the stuff from the top. I think somewhere along the way I ****ed up and for some reason all my folders are gone except for android. (ie downloads, notifications, alarms, ringtones, music, pictures, etc folders are gone)
even when i take a picture, it just disappears because it has nowhere to save to... . when I plug it in with file transfer mode, there is literally only 1 folder, look at this picture: http://imgur.com/a/F49v0
is there anything I can do to fix this? or did i just GG no re 540$? I know i'm a ****ing stupid ass ****ing low life piece of **** dumbass **** head.
If worse comes to worse, I still got like 13 days left to return it if possible? Do u think they'll accept a return or replacement from me?
****
when I go to google and try to download an image, it says It can't be downloaded because of missing SD card. wtf is going on?!
EDIT UPDATE: okay now my phone is stuck on boot screen with the 1+ symbol. any1 know how to help me out?
onepluslover69 said:
Guys i got my oneplus 5 in the mail yesterday and I like it, but I think i ****ed up...big time. please somebody help me out.
i was following this guide: https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877
to root my oneplus 5 so i can use Adaway. Ive rooted and installed a custom rom many times on my oneplus one before so I didn't really have any issues.
but then when I got to "Gaining root access" part, I was a little confused because I wasn't sure what step to take, so i Just did the stuff from the top. I think somewhere along the way I ****ed up and for some reason all my folders are gone except for android. (ie downloads, notifications, alarms, ringtones, music, pictures, etc folders are gone)
even when i take a picture, it just disappears because it has nowhere to save to... . when I plug it in with file transfer mode, there is literally only 1 folder, look at this picture: http://imgur.com/a/F49v0
is there anything I can do to fix this? or did i just GG no re 540$? I know i'm a ****ing stupid ass ****ing low life piece of **** dumbass **** head.
If worse comes to worse, I still got like 13 days left to return it if possible? Do u think they'll accept a return or replacement from me?
****
when I go to google and try to download an image, it says It can't be downloaded because of missing SD card. wtf is going on?!
EDIT UPDATE: okay now my phone is stuck on boot screen with the 1+ symbol. any1 know how to help me out?
Click to expand...
Click to collapse
Try to reboot into TWRP and format everything, including internal storage. Then flash any ROM and reboot.
If this doesn't work, you'll have to start all over again. Do a complete revert to stock.
Download the stock OP5 OOS 4.5.4 zip.
Download OnePlus stock recovery.
Reboot into fastboot/bootloader mode.
Flash stock recovery.
Boot into stock recovery.
Do a full wipe of /system and /data and /data/media (internal storage).
Sideload the full zip you downloaded in step 1 and flash it via stock recovery.
Reboot your phone.
easy
http://forum.xda-developers.com/attachment.php?attachmentid=3761904&d=1464187934
MrKhozam said:
Try to reboot into TWRP and format everything, including internal storage. Then flash any ROM and reboot.
If this doesn't work, you'll have to start all over again. Do a complete revert to stock.
Download the stock OP5 OOS 4.5.4 zip.
Download OnePlus stock recovery.
Reboot into fastboot/bootloader mode.
Flash stock recovery.
Boot into stock recovery.
Do a full wipe of /system and /data and /data/media (internal storage).
Sideload the full zip you downloaded in step 1 and flash it via stock recovery.
Reboot your phone.
Click to expand...
Click to collapse
i'm downloading a rom right now. btw I thought the latest OP5 OOS rom was 4.5.3?
huaiyue said:
easy
http://forum.xda-developers.com/attachment.php?attachmentid=3761904&d=1464187934
Click to expand...
Click to collapse
might I ask what exactly does this zip do?
update: solved everything by following khozam's method! that guys a ****ing beast. saved my ass. cheers
Sideload cannot read zip file
MrKhozam said:
Try to reboot into TWRP and format everything, including internal storage. Then flash any ROM and reboot.
If this doesn't work, you'll have to start all over again. Do a complete revert to stock.
Download the stock OP5 OOS 4.5.4 zip.
Download OnePlus stock recovery.
Reboot into fastboot/bootloader mode.
Flash stock recovery.
Boot into stock recovery.
Do a full wipe of /system and /data and /data/media (internal storage).
Sideload the full zip you downloaded in step 1 and flash it via stock recovery.
Reboot your phone.
Click to expand...
Click to collapse
Followed the steps. Everything works fine until sideload. I constantly get error in CMD prompt: cannot read...
I tried removing the zip file extension, dragging the file into command prompt. What am I doing wrong?
I have the same problem as OP where I foolishly deleted storage and now all I have is the android folder on the phone and cannot save files, nor download certain apps from the play store.
Thank you in advance...
sawihsiwi said:
Followed the steps. Everything works fine until sideload. I constantly get error in CMD prompt: cannot read...
I tried removing the zip file extension, dragging the file into command prompt. What am I doing wrong?
I have the same problem as OP where I foolishly deleted storage and now all I have is the android folder on the phone and cannot save files, nor download certain apps from the play store.
Thank you in advance...
Click to expand...
Click to collapse
Can you try formating first using the flash tool? If you accedentally deleted all folders even those in the root branch of the phone, It will generate the necessary files on your phone i think. Then you can simply flash twrp using the tool and should see the folders in twrp. Otherwise you can flash the full ota to generate them
sawihsiwi said:
Followed the steps. Everything works fine until sideload. I constantly get error in CMD prompt: cannot read...
I tried removing the zip file extension, dragging the file into command prompt. What am I doing wrong?
I have the same problem as OP where I foolishly deleted storage and now all I have is the android folder on the phone and cannot save files, nor download certain apps from the play store.
Thank you in advance...
Click to expand...
Click to collapse
Theoretically you should also be able to issue the following command in Recovery:
Code:
adb push -p [COLOR="Red"]<full zip path>[/COLOR] /sdcard/
Then select the zip from there. If you still get the read error, can you try rebooting into normal mode and issuing the same command?
Thank you for your help. huaiyue's storage fix zip file actually did the trick. I was able to restore everything back to normal. So thank you and thanks to huaiyue.
If anyone ever faces this again, Just follow below mentioned steps..
1: Flash TWRP
2: Got to Wipe and FORMAT data this will Decrypt you... AND let's you access your internal storage again..!
3: Now copy stock rom and FLASH.. This makes you ENCRYPTED again.
4: Now everything should be back to normal, just flash twrp again and enjoy..
Go to TWRP ----> select DATA (check it) ---> DONT swipe to wipe but click on REPAIR OR CHANGE FILE SYSTEM and select EXT 4. After that, reboot to twrp and data is recognized as normal sdcard..
That SD card fix helped but I want to know, what caused this?
---------- Post added at 12:03 AM ---------- Previous post was at 12:00 AM ----------
huaiyue said:
easy
http://forum.xda-developers.com/attachment.php?attachmentid=3761904&d=1464187934
Click to expand...
Click to collapse
thankyou so much dude!
Hi,
I'm currently using the Skipsoft Android Toolkit to unlock flash TWRP onto my device. I've followed to first steps (install drivers, backup device and unlock bootloader) to the letter and everything went smooth.
Now the final part of installing TWRP is not going so well. Flashing the custom recovery works as expected and I end up in the TWRP menu. However, as soon as I reboot my phone and try to go back to the recovery via Advanced Reboot --> recovery, I end up in the default One Plus Recovery Menu. Now the tool mentioneds when this process fails, renaming the Recovery Restore Files is recommend to prevent the system from flashing the stock recovery on boot (what happens to my device). I follow this option in which I end up back in TWRP, flash a zip named 'permanent-recovery.zip' (while read only mode is turned off in TWRP) and reboot my device. Still when I use Advanced Reboot to open recovery, I end up once again in the Stock Recovery.
Is there anyone who could tell me where I am going wrong and how to solve this issue?
Thanks in advance
Rawrden said:
Hi,
I'm currently using the Skipsoft Android Toolkit to unlock flash TWRP onto my device. I've followed to first steps (install drivers, backup device and unlock bootloader) to the letter and everything went smooth.
Now the final part of installing TWRP is not going so well. Flashing the custom recovery works as expected and I end up in the TWRP menu. However, as soon as I reboot my phone and try to go back to the recovery via Advanced Reboot --> recovery, I end up in the default One Plus Recovery Menu. Now the tool mentioneds when this process fails, renaming the Recovery Restore Files is recommend to prevent the system from flashing the stock recovery on boot (what happens to my device). I follow this option in which I end up back in TWRP, flash a zip named 'permanent-recovery.zip' (while read only mode is turned off in TWRP) and reboot my device. Still when I use Advanced Reboot to open recovery, I end up once again in the Stock Recovery.
Is there anyone who could tell me where I am going wrong and how to solve this issue?
Thanks in advance
Click to expand...
Click to collapse
The basic "mechanics" of what happens seems to still be as follows:
As your phone is delivered with Stock OS, it has these two files installed:
Code:
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
I know from looking at mine when I got it that it had /system/recovery-from-boot.p installed. If it's there, it is run when it runs at boot.
To stop that behavior you have to get rid of those files before you reboot the first time from recovery or else recovery will be replaced with the stock image. I'm aware that supposedly the custom recovery supposedly renames either one or the other or both of these but am not convinced it does this or whether installing root (either Magisk or SuperSU) does it. Either way, since you're stuck with the problem, either from file-manager in TWRP if that's all you can boot to, you need to rename /system/recovery-from-boot.p to something like /system/recovery-from-boot.p.orig and maybe the other one /system/etc/install-recovery.sh to /system/etc/install-recovery.sh.orig as well.
Once even the .p file is gone, it's not going to rewrite recovery. You must, of course, be rooted before you can touch those files although if you can sideboot TWRP, it seems like you are rooted while it is booted and "should" have access to system files if you can mount system rw.
I've fixed it this way on other phones. On this one, installing the "official" TWRP and Magisk did it. When I booted into /system after installing Magisk, I looked for the .p file and found it renamed to /system/recovery-from-boot.bak.
I found a link for a Samsung s8 for the same purpose. It's probably identical. http://www.teamandroid.com/2017/04/25/install-galaxy-s8-twrp-310-recovery/3/
Click to expand...
Click to collapse
I looked into those two files while in TWRP and noticed I only had the recovery-from-boot.p file. This was already in fact renamed to recovery-from-boot.p.bak. I renamed it once again (just to be sure) and after flashing the .zip I mentioned earlier, the TWRP did not last another reboot...
Can I after flashing TWRP again, immediately flash Magsik? I intended to hold off rooting because the rom I was going to install has Magisk build into it. I don't want to create a conflict when flashing later on. Is this going to be an issue?
@hachamacha I've reread your post and wondering if rooting my device is even going to make a difference right now? Since I'm already able to rename files in the system directory, would it even make a difference?
Rawrden said:
I looked into those two files while in TWRP and noticed and only had the recovery-from-boot.p file. This was already in fact renamed to record-from-boot.p.bak. I renamed it once again (just to be sure) and after flashing the .zip I mentioned earlier, the TWRP did not last another reboot...
Can I after flashing TWRP again, immediately flash Magsik? I intended to hold off rooting because the rom I was going to install has Magisk build into it. I don't want to create a conflict when flashing later on. Is this going to be an issue?
Click to expand...
Click to collapse
To me, it doesn't sound like a conflict to re-install Magisk over itself in FOS and see if that helps. The real "action" that counts is all about whether you've already booted into the OS after installing TWRP and then how you go about getting rid of the .p file without doing a regular reboot via the OS. Even installing the FOS ROM should get rid of the .p file (rename it), so something else is going on. I'll look around some more and update this if I can.
By the way: Depending upon how exactly you got from TWRP to the OS the first time, it could already have rewritten the stock recovery by the time you noticed *.p file renamed to *.bak.
OK: I recalled how I did this without a problem: I wrote instructions somewhere but have no idea where. This is what I think I did:
1) fastboot flash recovery recovery.img (custom/TWRP)
2) fastboot boot recovery.img (so force it to load recovery without a traditional reboot).
3) install ROM from that point and after done just hit the reboot button (or install Magisk from that point and hit reboot).
Click to expand...
Click to collapse
---------- Post added at 09:26 AM ---------- Previous post was at 08:59 AM ----------
Rawrden said:
@hachamacha I've reread your post and wondering if rooting my device is even going to make a difference right now? Since I'm already able to rename files in the system directory, would it even make a difference?
Click to expand...
Click to collapse
Just saw this note:
Anytime you're in TWRP, you're automatically "rooted" for the time you're there. It's integral to TWRP having permissions to do anything like install etc. If you just "loaded" TWRP (as in fastboot boot twrprecovery.img) then you'd be rooted, but when you rebooted to the system, you'd be unrooted. While you were in TWRP, in theory you could make file system changes to the /system partition (a) if TWRP lets you mount it rw which I think that first swipe does and b) if you can see the correct files in it's file manager.
So it "seems" like those file changes should be actual file changes to the correct place. Keep in mind that while booted in TWRP, TWRP may have it's own ./system/ that has nothing to do with the OS's ./system folder, so you've got to be able to mount the OS's ./system. TWRP's ./system is already fine and of no importance for this. I can boot mine into TWRP and look around to try to clear this up, but it might not be crystal clear to me either.
The output of a TWRP terminal emulator "mount" command might be of use but it will be messy. Maybe if you can do this in emulator from TWRP:
# mount | grep system, and look at that output, perhaps put it in this post, it'd be of help. The mounted rw ./system we need is going to be the same one you'd see from adb shell or terminal emulator while booted from the OS. My guess is that the one we don't want from TWRP's perspective will be mounted as /system (params...) and that the the OS's system either will not yet be mounted and you'll have to go to mounts and mount it and then look at the output of the mount cmd again to figure out what it was mounted as. Sorry about how complicated this explanation has become. Anyway: The ./system that corresponds to the OS is the only one we care about.
There's no easy way to explain it so I'll leave it hidden to spare anyone having to look at it:
I just booted into TWRP and used terminal emulator and file manager to explore:
findings: While in TWRP, using terminal emulator to do a
$ df and then a $ mount command shows no ./system mounted specifically. // maybe not a surprise.
// TWRP just mounts it's root / file system and there is a /system folder, just not a specific mount point for it.
// TWRP does not auto mount the OS's ./system partition by default. It depends what you're going to do there.
Without going into "mounts" and clicking on /system, it won't even try to mount /system for the OS.
If you can get that mount to work in read/write mode, then you should be able to see the ./system mount using terminal emulator as such.
$ mount | grep -i system (and look specifically for ./system on the right side of whatever appears).
In theory you should be able to make changes to the OS's /system partition now. When you're done, unmount it. (I'm assuming all this works from TWRP, a dodgy assumption)
At this point: I'm just trying to figure out how TWRP does things like installs OS zips to the /system & /data partitions which it is clearly successfully able to do. It could do it without mounting anything because it could use the linux dd command, which just writes to the /dev name. OR: It could mount /system and use it. I'm not sure which.
hachamacha said:
OK: I recalled how I did this without a problem: I wrote instructions somewhere but have no idea where. This is what I think I did:
Quote:
Code:
1) fastboot flash recovery recovery.img (custom/TWRP)
2) fastboot boot recovery.img (so force it to load recovery without a traditional reboot).
3) install ROM from that point and after done just hit the reboot button (or install Magisk from that point and hit reboot).
Click to expand...
Click to collapse
I followed these steps and I managed to install FreedomOS without any issues. My phone booted normally and after a few complimentary steps I booted back into recovery and... TWRP! No more stock recovery. Thanks a lot!
Just one more question: TWRP currently asks whether it is allowed to install itself as a system app. Now I assume it is already a system app, but I'm not expert at this so I can't say for sure. Would you recommend me to install TWRP as a system app?
Rawrden said:
I followed these steps and I managed to install FreedomOS without any issues. My phone booted normally and after a few complimentary steps I booted back into recovery and... TWRP! No more stock recovery. Thanks a lot!
Just one more question: TWRP currently asks whether it is allowed to install itself as a system app. Now I assume it is already a system app, but I'm not expert at this so I can't say for sure. Would you recommend me to install TWRP as a system app?
Click to expand...
Click to collapse
Great! Glad that worked. I guess it's all about how that first boot to the OS occurs.
Anyway: Your question, I'm assuming is about TWRP "Manager" the app? If so, yes, it should be a system app. The thing is that "Official TWRP Manager" doesn't really do much of use that you wouldn't just as soon do from fastboot, so it's not critical and nothing other than TWRP manager will "not work" regardless of what you designate it. All saying it's a system app does is puts a slot for it in Magisks "root table".
Cheers.
hachamacha said:
Great! Glad that worked. I guess it's all about how that first boot to the OS occurs.
Anyway: Your question, I'm assuming is about TWRP "Manager" the app? If so, yes, it should be a system app. The thing is that "Official TWRP Manager" doesn't really do much of use that you wouldn't just as soon do from fastboot, so it's not critical and nothing other than TWRP manager will "not work" regardless of what you designate it. All saying it's a system app does is puts a slot for it in Magisks "root table".
Cheers.
Click to expand...
Click to collapse
Done! Can I just say how grateful I am to you for helping me out with this? Your answers have been extremely detailed and I've learned quite a few things. Unfortunately I can only thank your posts once, because you've earned more than that. Thanks again and keep being awesome!
Hi there,
I'm hoping someone can help me with a few issues after I've gone through the bootloop fix that was posted a while ago.
I've got the phone up and running (YAY!) but it's really slow. I understand there is a zip file that can be "side loaded" but I'm not sure how that's done. I boot into the recovery mode but it asks for a password. When I cancel and just go to install there are no files that can be found, even though I copied the file into several directories on the phone.
The second thing is that despite being set to US English I don't seem to have assistant anymore. Has this happened to anyone else?
Thanks.
Did you flash the latest performance fix image from xcnathan??
Sent from my Nexus 6P using XDA Labs
mdfarazb2 said:
Did you flash the latest performance fix image from xcnathan??
Sent from my Nexus 6P using XDA Labs
Click to expand...
Click to collapse
I loaded the image on the phone.
Rebooted the phone into recovery mode.
Tried to install it, but I wasn't able to find it in any directory.
madclancrew said:
I loaded the image on the phone.
Rebooted the phone into recovery mode.
Tried to install it, but I wasn't able to find it in any directory.
Click to expand...
Click to collapse
Did you click the "install/flash image" button in the lower right corner?
Sent from my Nexus 6P using XDA Labs
mdfarazb2 said:
Did you click the "install/flash image" button in the lower right corner?
Sent from my Nexus 6P using XDA Labs
Click to expand...
Click to collapse
I don't have an install/flash image in the bottom right.
The Install button is located at the top left, there are no files when I go in there, and the directory list seems like it's missing stuff.
There is also Wipe, backup, restore, mount, settings, advanced, and reboot.
on the advanced screen i have copy log, fix contexts, file manager, terminal reload theme and adb sideload.
madclancrew said:
I don't have an install/flash image in the bottom right.
The Install button is located at the top left, there are no files when I go in there, and the directory list seems like it's missing stuff.
There is also Wipe, backup, restore, mount, settings, advanced, and reboot.
on the advanced screen i have copy log, fix contexts, file manager, terminal reload theme and adb sideload.
Click to expand...
Click to collapse
When you browse your internal storage, you see no files/folders? Completely blank? That means you probably need to factory reset your phone once... Wipe everything including the internal storage, and did you get an option at the startup of twrp, the read only settings? And slide to confirm? Did you slide that button?
Sent from my Nexus 6P using XDA Labs
mdfarazb2 said:
When you browse your internal storage, you see no files/folders? Completely blank? That means you probably need to factory reset your phone once... Wipe everything including the internal storage, and did you get an option at the startup of twrp, the read only settings? And slide to confirm? Did you slide that button?
Sent from my Nexus 6P using XDA Labs
Click to expand...
Click to collapse
I see some directories, but no files and some directories are missing.
When I boot into recovery mode it asks for a password. I click cancel and then swipe right to keep going.
madclancrew said:
I see some directories, but no files and some directories are missing.
When I boot into recovery mode it asks for a password. I click cancel and then swipe right to keep going.
Click to expand...
Click to collapse
Yup... You're doing right... After going into Install section there's no option in lower right corner named flash zip or flash image? Just Bedside select storage.
Sent from my Nexus 6P using XDA Labs
mdfarazb2 said:
Yup... You're doing right... After going into Install section there's no option in lower right corner named flash zip or flash image? Just Bedside select storage.
Sent from my Nexus 6P using XDA Labs
Click to expand...
Click to collapse
I do see that button.
I have the file saved to the root>sdcard>Download folder. (based on the file structure from the app I'm using on the phone.
But when I'm in the recovery mode and I look in the file structure I go to sdcard and there are no subfolders.
My root directory has boot, cache, data, dev, etc, license, oem, proc, recovery, res, root, sbin, sdcard, sideload, supersu, sys, system, tmp twres, usb-otg, vendor.
Almost all the folders contain no further sub folders.
madclancrew said:
I do see that button.
I have the file saved to the root>sdcard>Download folder. (based on the file structure from the app I'm using on the phone.
But when I'm in the recovery mode and I look in the file structure I go to sdcard and there are no subfolders.
My root directory has boot, cache, data, dev, etc, license, oem, proc, recovery, res, root, sbin, sdcard, sideload, supersu, sys, system, tmp twres, usb-otg, vendor.
Almost all the folders contain no further sub folders.
Click to expand...
Click to collapse
Hello! I have the EXACT same issue in TWRP.
---------- Post added at 04:56 PM ---------- Previous post was at 04:53 PM ----------
under "select storage" it shows (0M) for internal
HEY! fixed it by downloading official TWRP and fastboot flashing it.
stewwmann said:
HEY! fixed it by downloading official TWRP and fastboot flashing it.
Click to expand...
Click to collapse
Where did you get the official TWRP from?
madclancrew said:
Where did you get the official TWRP from?
Click to expand...
Click to collapse
https://twrp.me/Devices/
madclancrew said:
I do see that button.
I have the file saved to the root>sdcard>Download folder. (based on the file structure from the app I'm using on the phone.
But when I'm in the recovery mode and I look in the file structure I go to sdcard and there are no subfolders.
My root directory has boot, cache, data, dev, etc, license, oem, proc, recovery, res, root, sbin, sdcard, sideload, supersu, sys, system, tmp twres, usb-otg, vendor.
Almost all the folders contain no further sub folders.
Click to expand...
Click to collapse
Oops your twrp problem then... flash the official one as suggested by stewwmann... and try again if it still doesnt work do a complete wipe including internal storage and then flash that image again via otg or fastboot pushing your file...
mdfarazb2 said:
Oops your twrp problem then... flash the official one as suggested by stewwmann... and try again if it still doesnt work do a complete wipe including internal storage and then flash that image again via otg or fastboot pushing your file...
Click to expand...
Click to collapse
Ok. I'm obviously screwing this all up.
I downloaded the file, and then went to the boot screen. I entered: ./fastboot flash recovery twrp-3.1.1-0-angerl.img that worked fine. Then I rebooted the bootloader. Then tried to go into recovery and it attempted to load, paused, rebooted and then went to normal bootup. So you're suggesting at this point that I wipe the phone and reinstall the entire 7.1.1 as well as the twrp recovery, and the bootloop fix. Then I should be able to download and install the zip file that will help with the speed issue.
madclancrew said:
Ok. I'm obviously screwing this all up.
I downloaded the file, and then went to the boot screen. I entered: ./fastboot flash recovery twrp-3.1.1-0-angerl.img that worked fine. Then I rebooted the bootloader. Then tried to go into recovery and it attempted to load, paused, rebooted and then went to normal bootup. So you're suggesting at this point that I wipe the phone and reinstall the entire 7.1.1 as well as the twrp recovery, and the bootloop fix. Then I should be able to download and install the zip file that will help with the speed issue.
Click to expand...
Click to collapse
What!? After flashing the recovery you weren't able to boot into the recovery? Something is wrong I think.. maybe you entered wrong command while flashing... As you said that worked fine so did you see something like "completed in xx.xx seconds" ? After flashing the recovery? You you have, it should be working fine..
mdfarazb2 said:
What!? After flashing the recovery you weren't able to boot into the recovery? Something is wrong I think.. maybe you entered wrong command while flashing... As you said that worked fine so did you see something like "completed in xx.xx seconds" ? After flashing the recovery? You you have, it should be working fine..
Click to expand...
Click to collapse
Yeah...it didn't work. I'm going to probably have to start from scratch I think. Though this is the third or fourth time I've had to do this.
madclancrew said:
Yeah...it didn't work. I'm going to probably have to start from scratch I think. Though this is the third or fourth time I've had to do this.
Click to expand...
Click to collapse
Before you start over,try renaming the official TWRP to just that(TWRP) That's what their website suggests. From their site:
adb reboot bootloader
You should now be in fastboot mode.
Download the correct image file and copy the file into the same folder as your adb and fastboot binaries. Rename the image to twrp.img and type:
fastboot flash recovery twrp.img
fastboot reboot
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
stewwmann said:
Before you start over,try renaming the official TWRP to just that(TWRP) That's what their website suggests. From their site:
adb reboot bootloader
You should now be in fastboot mode.
Download the correct image file and copy the file into the same folder as your adb and fastboot binaries. Rename the image to twrp.img and type:
fastboot flash recovery twrp.img
fastboot reboot
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Click to expand...
Click to collapse
Ok. After a few more installs it finally booted into the twrp recovery. But it still can't see anything within the directories. I'm on Install Zip, and there are no files and no sub directories within root or SDcard. Image source is internal.
madclancrew said:
Ok. I'm obviously screwing this all up.
I downloaded the file, and then went to the boot screen. I entered: ./fastboot flash recovery twrp-3.1.1-0-angerl.img that worked fine. Then I rebooted the bootloader. Then tried to go into recovery and it attempted to load, paused, rebooted and then went to normal bootup. So you're suggesting at this point that I wipe the phone and reinstall the entire 7.1.1 as well as the twrp recovery, and the bootloop fix. Then I should be able to download and install the zip file that will help with the speed issue.
Click to expand...
Click to collapse
Ok. So I am going to have to wipe the phone and install again. I just want to make sure I'm doing this right.
I will restart the phone into bootloader, then reinstall the entire OS from the start. (PATH="$PATH:/user.../ ./flash-all.sh)
That will reinstall the OS from the file I downloaded from Google.
From there I will then reinstall TWRP recovery and their fix. Then, once I've booted up the phone I will load the zip file onto it, and it should become visible in the file directory in the recovery mode.
Am I right in this?
Thanks for your help.