So, wanted to use my old pixel 2 xl but USB only works for charging. PC won't detect it, used dozens of cables and different computers.
I have latest carbon image and root. Wanted to boot twrp.img and then flash the twrp.zip since it used to be that way.
Any hints on this please? Because using apps says partion doesn't exist. I recall it used to be the "issue". That's why we had to boot twrp first and then flash it.
Maybe there is a different solution now.
Any help would be much appreciated.
This is not possible without USB. When the device reboots, RAM is cleared and nothing is "held" in NVRAM for the boot process. The device will either boot the image currently in the boot partition, or if commanded, will live boot the image you specify.
It -is- possible to write images to /boot using root, but keep in mind that since Magisk does not support the compression used for the stock recovery kernel, flashing TWRP to /boot will result in a device that can only boot TWRP.
i see, ok, so, sorry the stupid question in advance.
What if i write twrp .img to boot, then it always boots from twrp, but since i have twrp.zip and a rom.zip in media i can flash .zip to recovery partition and then reboot to recovery and flash rom.zip?
Or is this just to dumb to even ask.
hfmls said:
i see, ok, so, sorry the stupid question in advance.
What if i write twrp .img to boot, then it always boots from twrp, but since i have twrp.zip and a rom.zip in media i can flash .zip to recovery partition and then reboot to recovery and flash rom.zip?
Or is this just to dumb to even ask.
Click to expand...
Click to collapse
Not a dumb question. However, flashing TWRP will result in a device that can only boot TWRP. This applies even if you flash a ROM to a slot.
The best alternative I've found is to run LineageOS. This is because that ROM includes its own recovery that can flash non-Google zips. Further, its updater not only doesn't require a usb cable it also gracefully handles Magisk.
Unfortunately, LineageOS isn't Carbon, and Carbon doesn't include a built-in updater. In your case, you may have no choice but to use a USB cable.
Related
Hello I'm new to the nexus line and recently upgraded form a SGS. my phone is Rooted, unlocked boot loader and running the most recent version of CWM 5.5.0.4. I'm running the GSM version of the Nexus.
My question is how do I flash the my first rom? When I boot into recovery and click install zip from SDcard i get "E: Can't mount /sdcard/" I am also unable to mound the data partition within. windows drivers are installed for both fastboot and adb so I can flash that way, i'm just wondering what the exact steps are and if that error mounting data is normal.
I also downloaded the most recent franco.Kernel as I want to run that, I know how to flash that with fastboot but wasnt' sure if that is how you would flash a rom with the nexus, on the SGS i used to use odin.
Thanks and sorry for the noobness.
How did you "unlock fastboot" and "root" and "install CWM"? Did you use one of the "Tool Kits"?
Do you have ROM Manager installed on your device?
yiannisthegreek said:
How did you "unlock fastboot" and "root" and "install CWM"? Did you use one of the "Tool Kits"?
Do you have ROM Manager installed on your device?
Click to expand...
Click to collapse
Sorry, Yes I have ROM Manager installed and its' paid for.
I unlocked my boot loader using fastboot oem unlock, I rooted by using an app because I couldn't mount the data partition in recovery so had to use some app some guy made that downloaded the su.zip from clockwork and flashed on it's own.
I installed CWM using fastboot.
fastboot flash recovery recovery.img
it's the dam data partition that i'm really having trouble with, i'm just wondering if this is normal, all the posts on the web say to flash a zip by choosing "choose zip from scard" but mine wont mount???
I should also mention that my entire device is encrypted.....that is whats causing it isn't it?
I'm not 100% sure but it could be that you flashed the wrong recovery.
According to this thread
http://forum.xda-developers.com/showthread.php?t=1357642
the recovery for the GSM version is 5.5.0.2 and not 0.4.
I would flash the correct recovery then try again.
You can not mount sdcard from CWM recovery (don't ask me why, I don't know.. maybe because it is not supported yet ..)
anyway, do like me, use CWM 5.5.0.2 and then try again toflash zip files .. It works for me
P4p3r1n0 said:
You can not mount sdcard from CWM recovery (don't ask me why, I don't know.. maybe because it is not supported yet ..)
anyway, do like me, use CWM 5.5.0.2 and then try again toflash zip files .. It works for me
Click to expand...
Click to collapse
He posted it on his Google+ account here:
https://plus.google.com/112476065271141473049/posts
I'm starting to think it's my encrypted phone, technically when I boot I have to decrypt the device before it boots into android.
I'm going to factory reset and see if that helps. I have a feeling that is what my problem is
OK so that was the problem, the data partition was encrypted (now that I think of this it makes sense that it wouldn't mount) anyways, for whatever reason a factory reset from android wouldn't work. I removed the "recovery-from-boot.p" file from my system folder originally so the CWM image would remain in tact.
anyways, I flashed the original recovery over the CWM recovery, preformed a factory wipe (which is the only way to decrypt your phone) then flashed CWM back on and now I can mount the data partition
what a pain in the ass, guess I wont be encrypting the phone any time soon, I wish there was an option to decrypt the drive and then get into recovery....wouldn't have this issue.
spectre85 said:
OK so that was the problem, the data partition was encrypted (now that I think of this it makes sense that it wouldn't mount) anyways, for whatever reason a factory reset from android wouldn't work. I removed the "recovery-from-boot.p" file from my system folder originally so the CWM image would remain in tact.
anyways, I flashed the original recovery over the CWM recovery, preformed a factory wipe (which is the only way to decrypt your phone) then flashed CWM back on and now I can mount the data partition
what a pain in the ass, guess I wont be encrypting the phone any time soon, I wish there was an option to decrypt the drive and then get into recovery....wouldn't have this issue.
Click to expand...
Click to collapse
It is possible now on 4.1.2 to decrypt the device. You must provide a password for dectypting (chane from unlock pin to passw).
Hello forum,
i'm currently trying to find the best software solution for my Xperia Z1 Compact and i already got close to what's possible.
I found this ROM which is working almost perfectly except that it overrides the recovery with a dual recovery with an older TWRP version which prevents me from doing critical flashes and backups.
I only need TWRP 3.0.2 on /recovery, nothing else like PhilZ or anything else.
When i flash TWRP 3 for Z1C and reboot to recovery or press Vol-Up when booting i get a blackscreen boot loop which can only be fixed by flashing an old TWRP or wiping the entire phone from fastboot.
Another problem is that updater-script formats /system and /data to ext4 and mounts them like that which is a problem because i'd like to have F2FS on all of my partitions.
I already tried removing /kernel/ and /dualrecovery/ from the .zip and modifying updater-script to not format both patititons and mount them as F2FS, but when trying to flash this modded .zip it fails to flash (probably because an integrity check?).
So what i need to do is:
Remove recovery from .zip
Remove kernel from .zip
Modify updater-script to not format any partitions and mount them as F2FS
Any help, resources and tipps are appreciated. I'm running Windows 10 x64 but i don't think i'm able to build a ROM on my own as i have only little programming experience.
SinusStudios said:
Hello forum,
i'm currently trying to find the best software solution for my Xperia Z1 Compact and i already got close to what's possible.
I found this ROM which is working almost perfectly except that it overrides the recovery with a dual recovery with an older TWRP version which prevents me from doing critical flashes and backups.
I only need TWRP 3.0.2 on /recovery, nothing else like PhilZ or anything else.
When i flash TWRP 3 for Z1C and reboot to recovery or press Vol-Up when booting i get a blackscreen boot loop which can only be fixed by flashing an old TWRP or wiping the entire phone from fastboot.
Another problem is that updater-script formats /system and /data to ext4 and mounts them like that which is a problem because i'd like to have F2FS on all of my partitions.
I already tried removing /kernel/ and /dualrecovery/ from the .zip and modifying updater-script to not format both patititons and mount them as F2FS, but when trying to flash this modded .zip it fails to flash (probably because an integrity check?).
So what i need to do is:
Remove recovery from .zip
Remove kernel from .zip
Modify updater-script to not format any partitions and mount them as F2FS
Any help, resources and tipps are appreciated. I'm running Windows 10 x64 but i don't think i'm able to build a ROM on my own as i have only little programming experience.
Click to expand...
Click to collapse
I don't know much, but I am surprised that flashing twrp 3 causes that problem. What method are you using? Try using Rashr to flash twrp 3 img, then try to boot to recovery. If vol up doesn't work, try vol down, (that's what works for me). Somehow I don't think you'll be able to just remove those things from the ROM and have it flash fine. Your better chance is to get twrp flashed, then figure out the F2FS, etc. Also, there are custom kernels for stock-based roms, and don't forget that twrp 3 is not official on Z1compact, so read threads thoroughly to make sure what you're trying to do is supported. I know many of us have twrp 3 on our phones, so I would look more into that.
Hi,
I had the same issues and maybe this helps.
- install your rom and go into dual recovery and choose twrp
- in twrp go to install and choose "IMG" and not "ZIP"
- you can now install the new twrp version via install !
Maybe you should not flash that ROM because it seems to contain malware. Have a look into the thread.
So I almost ****ed up trying to flash a custom rom on my redmi note 8. I had to wipe my whole system image so I had no os installed there. I did almost accidentally wipe my whole internal storage. So twrp would've been gone aswell. So I could've thrown my phone in the trash can, right? Or is there a way to get twrp on a phone with no os and nothing on it? Or maybe even flash a rom? Idk I'm kinda new to this whole topic. What can you do if your phone is completely wiped? No os, no twrp, nothing.
Edit: I just figured out that wiping the internally storage doesn't remove twrp. But still would there still be a way to save your phone with twrp removed and no os? Basically a completely blank device?
Re: @Johnny3_3
Can you boot to twrp by long pressing POWER and VOL UP?
According to your description, your bootloader has been unlocked. But maybe you can't boot with only a boot without ramdisk. Go to fastboot and flash the right fastboot ROM for your phone. Then flash, and go to TWRP using the key combo. Don't use fastboot boot command. Then do anything you want.
Yuki1001 said:
Re: @Johnny3_3
Can you boot to twrp by long pressing POWER and VOL UP?
According to your description, your bootloader has been unlocked. But maybe you can't boot with only a boot without ramdisk. Go to fastboot and flash the right fastboot ROM for your phone. Then flash, and go to TWRP using the key combo. Don't use fastboot boot command. Then do anything you want.
Click to expand...
Click to collapse
Hey, im sorry I think I didn't explain it that well. I have havoc installed already. I just wanted to know what I could have done if I had no os and no twrp installed.
Re: @Johnny3_3
Wiping Internal storage will not wipe the recovery partition.
Once you wipe system partition, you maybe can't boot with a boot that has no ramdisk.
If you have no OS and no TWRP, you can only boot into fastboot and flash images.
If you wipe system, recovery, data, internal storage, cust, you will only be able to boot into fastboot.
If you want to flash twrp on device without OS, just flash the TWRP img file through fastboot.
Johnny3_3 said:
Hey, im sorry I think I didn't explain it that well. I have havoc installed already. I just wanted to know what I could have done if I had no os and no TWRP installed.
Click to expand...
Click to collapse
Get into fastboot mode and flash/boot the recovery with Fastboot - ADB Tools.
There is also an app on github called "Xiaomi ADB Fastboot Tools" I used that to do everything on my phone.
Yuki1001 said:
Re: @Johnny3_3
Wiping Internal storage will not wipe the recovery partition.
Once you wipe system partition, you maybe can't boot with a boot that has no ramdisk.
If you have no OS and no TWRP, you can only boot into fastboot and flash images.
If you wipe system, recovery, data, internal storage, cust, you will only be able to boot into fastboot.
If you want to flash twrp on device without OS, just flash the TWRP img file through fastboot.
Click to expand...
Click to collapse
OK. And what i need to do now? I have Samsung Galaxy A6 and the same problem as @Johnny3_3, but idk how i can now use the phone without enythong in there!!! Pls help me figure out what i should to do in this situation.
~GTHX
Because i dont have the twrp and os on my phone... it just looping the logo of samsung galaxy A6 blablabla....
GTHX2021 said:
OK. And what i need to do now? I have Samsung Galaxy A6 .....
Click to expand...
Click to collapse
This topic is for XRN8.
Better is to ask in the right A6 topic, because the procedure to flash twrp is not the same
Yuki1001 said:
Re: @Johnny3_3
Wiping Internal storage will not wipe the recovery partition.
Once you wipe system partition, you maybe can't boot with a boot that has no ramdisk.
If you have no OS and no TWRP, you can only boot into fastboot and flash images.
If you wipe system, recovery, data, internal storage, cust, you will only be able to boot into fastboot.
If you want to flash twrp on device without OS, just flash the TWRP img file through fastboot.
Click to expand...
Click to collapse
Hi, I have the same problem with my OnePlus 5T. I've tried many times flashing TWRP but it doesn't boot up
Test version of custom Team Win Recovery Project version 3.5.2_11.0 for OnePlus Nord N100 (Android 11 Only).
Everything works, except for:
MTP, .img firmware (for this you need to flash the full super.img image) and decryption of the Data section.
If anyone can modify this version of the recovery, we are very grateful to the future.
In the meantime, whoever wants to test or try it out, an image will be attached to the post. You can both boot (fastboot boot twrp.img) and flash (fastboot flash recovery_a twrp.img and fastboot flash recovery_b twrp.img).
I ask you to answer about all the problems found and write either to me personally or in this topic.
Is there any newer version of this? i find this one freezes the phone a lot. thanks
I ran this TWRP for the OnePlus N100 in fastboot and it worked but I can't see any files. I've installed Android 11.
I'm trying to install Magisk zip but in TWRP I only see the folder tree and no files.
Do I need to install TWRP and not just run it from fastboot?
If I need to install it do I pick slot a or b or both?
Thanks for any help.
onlycash said:
I ran this TWRP for the OnePlus N100 in fastboot and it worked but I can't see any files. I've installed Android 11.
I'm trying to install Magisk zip but in TWRP I only see the folder tree and no files.
Do I need to install TWRP and not just run it from fastboot?
If I need to install it do I pick slot a or b or both?
Thanks for any help.
Click to expand...
Click to collapse
do not install it. I installed it and it bricked my device. I needed to flash the stock recovery.
Halphix said:
do not install it. I installed it and it bricked my device. I needed to flash the stock recovery.
Click to expand...
Click to collapse
It installed fine on my BE2013. Not extremely useful without the missing features though.
thomaskmaagaard said:
It installed fine on my BE2013. Not extremely useful without the missing features though.
Click to expand...
Click to collapse
Can you install Magisk zip with this TWRP on your BE2013?
.
onlycash said:
Can you install Magisk zip with this TWRP on your BE2013?
Click to expand...
Click to collapse
Honestly I haven't even tried flashing anything because I already have magisk and i had some issues with safety net that I didn't want to risk having to fix again.
thomaskmaagaard said:
Honestly I haven't even tried flashing anything because I already have magisk and i had some issues with safety net that I didn't want to risk having to fix again.
Click to expand...
Click to collapse
How did you install the Magisk zip file?
.
onlycash said:
How did you install the Magisk zip file?
Click to expand...
Click to collapse
I didn't. I patched firmware boot image and flashed through bootloader. However I just tried flashing from TWRP.
I put the zip on external SD because this version doesn't support decryption of data partition. I then entered the "mount" menu in TWRP and mounted external SD and then tapped "select storage" and selected external SD.
You should be able to flash it now. It didn't give any errors, but i didn't uninstall magisk first so don't know how well it actually worked.
I also don't know if you can do anything without external SD or without root access already.
thomaskmaagaard said:
I didn't. I patched firmware boot image and flashed through bootloader. However I just tried flashing from TWRP.
I put the zip on external SD because this version doesn't support decryption of data partition. I then entered the "mount" menu in TWRP and mounted external SD and then tapped "select storage" and selected external SD.
You should be able to flash it now. It didn't give any errors, but i didn't uninstall magisk first so don't know how well it actually worked.
I also don't know if you can do anything without external SD or without root access already.
Click to expand...
Click to collapse
Thanks.
That's very interesting...
You've given me a few good ideas.
I'll report back and let you know if it worked.
.
onlycash said:
Thanks.
That's very interesting...
You've given me a few good ideas.
I'll report back and let you know if it worked.
.
Click to expand...
Click to collapse
If you go with the boot image method I wouldn't mind helping you out.
thomaskmaagaard said:
I didn't. I patched firmware boot image and flashed through bootloader. However I just tried flashing from TWRP.
I put the zip on external SD because this version doesn't support decryption of data partition. I then entered the "mount" menu in TWRP and mounted external SD and then tapped "select storage" and selected external SD.
You should be able to flash it now. It didn't give any errors, but i didn't uninstall magisk first so don't know how well it actually worked.
I also don't know if you can do anything without external SD or without root access already.
Click to expand...
Click to collapse
I had high hopes...
I fastbooted the TWRP, I didn't install it but I don't think that would make a difference.
I put the Magisk zip on the external SD card and from within TWRP I had no problem mounting the SD card but I still couldn't see any files, just a folder tree, and every folder empty.
When you run TWRP and mount the SD card can you see the files within the folders on the card?
.
onlycash said:
When you run TWRP and mount the SD card can you see the files within the folders on the card?
Click to expand...
Click to collapse
Yes. It is important that you tap "select storage" and select "micro sd". After i did that i entered "flash" and immediately saw folders and zips on my external sd. In file manager i could see all files and even deleted some from there.
From root directory it's in /external_sd not in /storage.
Edit: Even though i also don't think installing TWRP makes a difference, i don't know if that's the case.
I should mention i used "fastboot flash recovery xxx.img" not "... recovery_a" or "... recovery_b".
I don't know if this changes something with access
Honestly patching boot image is probably less of a headache. I can even send the images pre-patched if you want. Just one fastboot command
I'd need to know your phone variant and update version.
thomaskmaagaard said:
Honestly patching boot image is probably less of a headache. I can even send the images pre-patched if you want. Just one fastboot command
I'd need to know your phone variant and update version.
Click to expand...
Click to collapse
Well, I don't think you have the file I need.
My N100 is a model BE2015, build number 11.0.1BE82CF
I just fastbooted TWRP again and I'm mounting and selecting external_sd but still zero files.
If I flash the TWRP with "fastboot flash recovery xxx.img" is there a way to reverse it if I ever need to?
Again thanks for the help.
.
onlycash said:
My N100 is a model BE2015, build number 11.0.1BE82CF
Click to expand...
Click to collapse
Well that might be the problem. That's a carrier locked phone, right? I'm not really familiar with those. I just know they are complicated to mod.
Not sure if you'll even be able to flash recovery and I'm surprised you can fastboot boot. But in theory, (at least on unlocked phones) if you can flash TWRP, you can flash stock recovery from firmware package.
I saw a quite extensive and fairly complicated guide to fully unlock a carrier phone here on XDA, but don't know how well it works or if you have followed any of these steps.
Edit: Also found this, looks like it works with your device: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4245499/
thomaskmaagaard said:
Well that might be the problem. That's a carrier locked phone, right? I'm not really familiar with those. I just know they are complicated to mod.
Not sure if you'll even be able to flash recovery and I'm surprised you can fastboot boot. But in theory, (at least on unlocked phones) if you can flash TWRP, you can flash stock recovery from firmware package.
I saw a quite extensive and fairly complicated guide to fully unlock a carrier phone here on XDA, but don't know how well it works or if you have followed any of these steps.
Edit: Also found this, looks like it works with your device: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4245499/
Click to expand...
Click to collapse
Let me start by saying my phone is both SIM unlocked and bootloader unlocked.
The post you linked is talking about the same phone as me but the last post in that thread has an ominous post from someone on Android 11 bricking after trying that. I'm not sure if that works if you're already on 11.
I still can't understand why the TWRP can't see files on my SD card. I think the two missing elements are the fact that you have TWRP flashed to your phone and you're rooted already.
I really can't understand why being rooted would have anything to do with TWRP seeing the files on the SD card so I'm leaning toward it being flashed that's the difference.
I would like to try flashing TWRP but I'm still unsure how, plus I'm guessing I have no recovery if that goes awry.
If I could just get the zip fashed it should patch my boot.img and give me root fairly easily.
Does anyone have any suggestions as to ways back if the TWRP flash goes bad plus just what command do I use to flash it and what happens to the other slot?
.
Okay, so...
I have now tried flashing stock boot and stock recovery on both a and b, verified no root access, then trying "boot twrp.img"
Still able to see files on micro sd.
I then attempted to flash magisk zip to verify this method working.
Didn't seem to work at first, but i think this was due to me messing something up with active slot. Fastbooted into twrp again and flashed magisk again and it works.
So, in short; This absolutely works on a BE2013, but this recovery might not play well with your BE2015.
OP asks about potential problems so maybe you'll have luck messaging him and you could investigate together? Just a suggestion.
I'm sorry, but I really don't know how to help with that model. It's problematic that there's no firmware payload available. If you find one or if you can somehow dump the boot image from the phone then I'd be optimistic and happy to help any way I can.
onlycash said:
How did you install the Magisk zip file?
.
Click to expand...
Click to collapse
I have the BE2011 model. Useful on this variant?
Hello,
I recently tried to flash a custom rom on my poco f3, but I couldn't install twrp, because I didn't have the option to install it when i boot to it.
So I followed some instructions online and formated data partition to ext2, and then back to ext4. Now I can't copy any files to the phone storage and can't do anything else.
I can reboot to fastboot, and I can boot to twrp, but it's pretty much useless because I can't sideload anything, and can't install twrp anyways.
Did I do something wrong? Is it easily fixable?
Thanks in advance.
f2fs?
aIecxs said:
f2fs?
Click to expand...
Click to collapse
I don't understand what you mean, sorry. I'm newbie.
Should I format the data partition to f2fs？
Idk depends on ROM. MIUI is f2fs
aIecxs said:
Idk depends on ROM. MIUI is f2fs
Click to expand...
Click to collapse
Oh. I tried a different twrp version and could install it on the phone. Now flashed crDroid and it said my system was broke so had to factory reset. It is working now. Thanks.
But now I can only access the crDroid recovery, how can I install back twrp? if I try to fastboot boot twrp.img it simply reboots back to system.
try to boot TWRP from other slot maybe? (don't forget to switch back)
Code:
fastboot --set-active=other
fastboot boot twrp.img
if that fails just flash TWRP into vendor_boot partition, and restore vendor_boot.img from crDroid right after