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?
Related
i cannot install anything in TWRP atm
it says "could not find ´META-INF/com/google/android/update-binary´in zip file.
Any bright ideas ?
Citroon said:
i cannot install anything in TWRP atm
it says "could not find ´META-INF/com/google/android/update-binary´in zip file.
Any bright ideas ?
Click to expand...
Click to collapse
It looks so simply but did you take a look to your rom zip? open with a zip explorer like winzip in /META-INF/com/google/android and here you must find this file
SubwayChamp said:
It looks so simply but did you take a look to your rom zip? open with a zip explorer like winzip in /META-INF/com/google/android and here you must find this file
Click to expand...
Click to collapse
it's not only with the roms, it's with everything
i've tried to flash new firmware, gapps and nothing works :/
well, what version of twrp do you use? try first with oficcial 3.0.2.0, bootloader unlocked? check usb debbugging and allow oem unlock in developer options, sometimes neccessary mount system or enable MTP in recovery
SubwayChamp said:
well, what version of twrp do you use? try first with oficcial 3.0.2.0, bootloader unlocked? check usb debbugging and allow oem unlock in developer options, sometimes neccessary mount system or enable MTP in recovery
Click to expand...
Click to collapse
im using the official 3.0.2.0, i currenly have no RoM installed so i can't boot into anything
Citroon said:
im using the official 3.0.2.0, i currenly have no RoM installed so i can't boot into anything
Click to expand...
Click to collapse
try first formatting data, wipe everything except where placed your rom zip (int or extSD), mount system and flash again
SubwayChamp said:
try first formatting data, wipe everything except where placed your rom zip (int or extSD), mount system and flash again
Click to expand...
Click to collapse
Tried that, still having the error:crying:
Citroon said:
i cannot install anything in TWRP atm
it says "could not find ´META-INF/com/google/android/update-binary´in zip file.
Any bright ideas ?
Click to expand...
Click to collapse
ok, go to format the data and then write YES, but u will lose your data, so, backup your files, and then restore them. should be working !!
StonebridgeGr said:
ok, go to format the data and then write YES, but u will lose your data, so, backup your files, and then restore them. should be working !!
Click to expand...
Click to collapse
Doesn't work either, this is really weird to me, i've been flashing for a few years now, and never encountered this issue before.
-also note that i'm not amazing at this
Citroon said:
Doesn't work either, this is really weird to me, i've been flashing for a few years now, and never encountered this issue before.
-also note that i'm not amazing at this
Click to expand...
Click to collapse
ok. which image did u flash? which guide did u followed to flash twrp ? ( because a newiest image of TWRP RECOVERY for mi max is up )
StonebridgeGr said:
ok. which image did u flash? which guide did u followed to flash twrp ? ( because a newiest image of TWRP RECOVERY for mi max is up )
Click to expand...
Click to collapse
i've tried about every RoM available.
I also want to note that i have flashed with this version of TWRP before (3.0.2.0)
StonebridgeGr said:
ok. which image did u flash? which guide did u followed to flash twrp ? ( because a newiest image of TWRP RECOVERY for mi max is up )
Click to expand...
Click to collapse
tried about every rom available, and other things just to see what would work and what wouldn't (nothing can flash)
im currently running 3.0.2.0 and have flashed with this version of TWRP before, but suddenly it stopped working
Citroon said:
Tried that, still having the error:crying:
Click to expand...
Click to collapse
Probably a bad flashing and you are needing repari partitions, for that I recommend start from beginning again:
- flash miui rom for fastboot (unpack zip rom in your adb folder for better performance, connect device to pc into mode fastboot, be sure device be recogniced typing; fastboot devices then right click mouse and execute like admin over "flash all".
- then to install rom you can flash again twrp via fastboot typing any place adb folder and placing file recovery.img this folder; fastboot flash recovery recovery.img
- then go to recovery with hardware keys and flash supersu v.2.79
SubwayChamp said:
Probably a bad flashing and you are needing repari partitions, for that I recommend start from beginning again:
- flash miui rom for fastboot (unpack zip rom in your adb folder for better performance, connect device to pc into mode fastboot, be sure device be recogniced typing; fastboot devices then right click mouse and execute like admin over "flash all".
- then to install rom you can flash again twrp via fastboot typing any place adb folder and placing file recovery.img this folder; fastboot flash recovery recovery.img
- then go to recovery with hardware keys and flash supersu v.2.79
Click to expand...
Click to collapse
oh boy, i guess im screwed for now then.
i only have access to a macbook for the next few days, tried installing fastboot on it but that's a complete nightmare
Citroon said:
oh boy, i guess im screwed for now then.
i only have access to a macbook for the next few days, tried installing fastboot on it but that's a complete nightmare
Click to expand...
Click to collapse
two things; I assume that trying to flash from extSD, if yes with file explorer of recovery copy to internal memory, maybe an issue to reading extSD, also you can to install a newer version of recovery 3.0.3.2 works sometimes for me and last here you have a reading page about install fastboot on mac (nightmare) http://www.stechguide.com/setup-adb-and-fastboot-on-mac-easy-step-by-step-guide/
SubwayChamp said:
two things; I assume that trying to flash from extSD, if yes with file explorer of recovery copy to internal memory, maybe an issue to reading extSD, also you can to install a newer version of recovery 3.0.3.2 works sometimes for me and last here you have a reading page about install fastboot on mac (nightmare) http://www.stechguide.com/setup-adb-and-fastboot-on-mac-easy-step-by-step-guide/
Click to expand...
Click to collapse
I finally got it working
I was so stubborn that I decided to install Windows Bootcamp on my mac
it was as simple as reinstalling TWRP and do a clean wipe, now i can install roms and all the other things as i please again.
-Thank you for your help!
Hello,
it seems to be that sth went wrong today. I wanted to factory reset my OP3 but right now nothing is working.
The initial set up was the following:
Unlocked bootloader with TWRP installed. Oxygen OS + several custom ROMs installed
What I did:
I deleted the data from system partition since I thought that they Oxygen OS system data will be deleted.
Problem:
Right now I get a encryption hint without the possibiity to factory reset my OP3 since I don´t get access to the data partition in order to upload a Oxygen OS .zip on my OP 3 from my PC.
What can I do in oder to factory reset my OP3 with the help of my PC? I want to install the OnePlus 3 OxygenOS Open Beta 28.
Search mega unbrick guide method 2 and then flash the last OnePlus recovery and then flash OB28
I managed to flash the most current Oxygen OS on my OP3 by doing a factory reset within TWRP and flashing the Oxygen OS .zip and Magisk 4.5.
BUT after rebooting, the file system seems to be encrypted again in TWRP (even allowing explicitly file modifications!). This means that I am not able to flash another .zip.
How can I manage that the file system remains decrypted also in TWRP?
I don't have access in TWRP to my files in oder to flash an OS Update and so on. It seems to be encrypted in TWRP. How can I manage to have access to all my files located in the internal flash?
king0r said:
I don't have access in TWRP to my files in oder to flash an OS Update and so on. It seems to be encrypted in TWRP. How can I manage to have access to all my files located in the internal flash?
Click to expand...
Click to collapse
If you boot OOS without any force encryption disabling mod them it will encrypt. It's not a problem at all if you use the right TWRP. Pick the TWRP from the Bluspark thread and you should be fine.
king0r said:
I don't have access in TWRP to my files in oder to flash an OS Update and so on. It seems to be encrypted in TWRP. How can I manage to have access to all my files located in the internal flash?
Click to expand...
Click to collapse
Well, there is a way to decrypt the device, but you'll lose everything. Reboot do fastboot and connect to pc, then type from CMD "fastboot erase userdata" or "fastboot format userdata"
Puddi_Puddin said:
If you boot OOS without any force encryption disabling mod them it will encrypt. It's not a problem at all if you use the right TWRP. Pick the TWRP from the Bluspark thread and you should be fine.
Click to expand...
Click to collapse
Please send me a link to the thread. I can't find it.
king0r said:
Please send me a link to the thread. I can't find it.
Click to expand...
Click to collapse
http://lmgtfy.com/?iie=1&q=Bluspark+oneplus+3t
If you pay attention, it also explains how searching in the internet works. It's littery the first result if you google "Oneplus 3 Bluspark".
I was already using
twrp-3.2.1-x_blu_spark_v8.61-op3_op3t.img !!!
BUT nevertheless I don't have access to any file (e.g. .zip) even using the newest version of the Bluspark TWRP. Every directory is listed with 0 Bytes.
When accessing TWRP an Error message comes up but I can allow file modifications. But this doesn't help to get access to any file.
Flash the stock recovery
http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img
Then after flash stock recovery boot to recovery all wipe (internal storage will be deleted). Done!
Flash official or Blu spark twrp. Go to Mount>check the internal storage.
madsponge26 said:
Flash the stock recovery
http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img
Then after flash stock recovery boot to recovery all wipe (internal storage will be deleted). Done!
Flash official or Blu spark twrp. Go to Mount>check the internal storage.
Click to expand...
Click to collapse
Thanks, but this means that I will lose all my data located on my phone??
Will at least the already installed OOS remain?
king0r said:
Thanks, but this means that I will lose all my data located on my phone??
Will at least the already installed OOS remain?
Click to expand...
Click to collapse
Well, if you can't access your data with TWRP then you are ****ed any way.
I can only not access the data in Recovery! In OOS no peoblems at all!!
I don't understand why in Recovery nö data access is possible.
I am having a problem it happened after I finally got to flash latest CosmicOS and set up a new password on my OP3. So, here’s what basically happened;
Once I got it up and running I noticed that home button and fingerprint sensor was completely disabled, then I tried to set up a new password (completely same password I used to decrypt my storage in TWRP 3.0.2-0) and fingerprint just in case but it didn’t react to me calibrating the fingerprint so I was like, ”alright, gladly I got a backup in TWRP”.
Once I rebooted to recovery it asked for a password as usually, once I typed that exact same password as before it just said wrong password, I tried it twice in case if I made a typo but still invalid password. And then I was panicing and pressed cancel and just rebooted back to OS.
I then removed all passwords there and booted back to recovery again, TWRP doesn’t ask for a password anymore but there’s a slider which says allow modifications or something similar and also there’s read only mode. When I slided the modification thing it just doesn’t show any of my files in sdcard folder when I go to ’Install’ tab but (0mb) instead. I even was able to browse and add files from my pc while phone was plugged in and in recovery mode, not anymore though.
Can anyone give me advice or help to get my oneplus 3 back in use? I have all the important files moved to my pc so I don’t mind losing files I have left in internal storage that much. Not if it’s necessary or easier workaround. thanks for reading this long-ass text :fingers-crossed:
EDIT: Issue SOLVED thanks to @AkR2014. I switched data partition from EXT4 to F2FS and then one more time back to EXT4 in TWRP's Wipe tab. (I was using latest blue_spark's TWRP-3.2.1-x version) and I was able to wipe data, system and both caches afterwards. After that I managed to flash new rom via USB-C to A with mounted USB flash drive on the other end and you know rest of the story. Do note that it WILL clear your internal storage so back up all the necessary files you need. And if you want to stay on F2FS data partition be sure to flash a ROM which supports it
EDIT2: There might be another way to mount your storage in TWRP but this is probably fail-proof method and worked for me
Oh and I couldn’t flash the Gapps in recovery after flashing the CosmicOs and nor I can’t now because of this haha. I can use my email though and send files through it from my another email if that helps
Vaahtopahvi said:
Oh and I couldn’t flash the Gapps in recovery after flashing the CosmicOs and nor I can’t now because of this haha. I can use my email though and send files through it from my another email if that helps
Click to expand...
Click to collapse
Try eng.stk's TWRP and clean flash ROM and Gapps.
tnsmani said:
Try eng.stk's TWRP and clean flash ROM and Gapps.
Click to expand...
Click to collapse
I couldnt find link for eng.stk TWRP, only people talking of it it. and what am I supposed to do with it once I get if you could explain? sorry for nooby questions
tnsmani said:
Try eng.stk's TWRP and clean flash ROM and Gapps.
Click to expand...
Click to collapse
Wait, I think I found it. But the question is can and do I need to update the latest eng.stk’s TWRP through fastboot? And if so, is there instructions topic somewhere?
So here's the latest update: I flashed twrp-3.1.1-2 via fastboot but once I go to recovery it still doesn't let me browse files in /sdcard and if I put new password in OS it doesn't match in TWRP. I have a OS where I can boot to but no Gapps installed.
People say formatting data in TWRP would work, I'm just scared if that doesn't work and won't let me boot to OS anymore (even though I have a TWRP back up which I made before wiping my OxygenOS system data and caches in my pc as well in my phone's storage atm) and I can't flash anything in recovery mode, is there anything I could do? I'm in desperate need of help right now.
In this CosmicOS i am using Android 8.1.0 and I'm afraid something isn't supporting it or so.
Vaahtopahvi said:
So here's the latest update: I flashed twrp-3.1.1-2 via fastboot but once I go to recovery it still doesn't let me browse files in /sdcard and if I put new password in OS it doesn't match in TWRP. I have a OS where I can boot to but no Gapps installed.
People say formatting data in TWRP would work, I'm just scared if that doesn't work and won't let me boot to OS anymore (even though I have a TWRP back up which I made before wiping my OxygenOS system data and caches in my pc as well in my phone's storage atm) and I can't flash anything in recovery mode, is there anything I could do? I'm in desperate need of help right now.
In this CosmicOS i am using Android 8.1.0 and I'm afraid something isn't supporting it or so.
Click to expand...
Click to collapse
As I said, flash eng.stk's TWRP. Simply flash the image to Recovery partition using the TWRP you already have. After that, wipe everything and clean flash the ROM. If anything goes wrong, you can use the Mega Unbrick guide method 2.
Here's the link to TWRP: https://forum.xda-developers.com/devdb/project/?id=15934#downloads
tnsmani said:
As I said, flash eng.stk's TWRP. Simply flash the image to Recovery partition using the TWRP you already have. After that, wipe everything and clean flash the ROM. If anything goes wrong, you can use the Mega Unbrick guide method 2.
Here's the link to TWRP: https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Click to expand...
Click to collapse
Thanks for the reply and link. I understood most of the parts except flashing the image to Recovery partition. Am I supposed to find the eng.stk’s TWRP from my Install tab in my current TWRP? Because it doesn’t show any files there. Also do I download the latest 3.2.1-x TWRP from the link you provided?
Vaahtopahvi said:
Thanks for the reply and link. I understood most of the parts except flashing the image to Recovery partition. Am I supposed to find the eng.stk’s TWRP from my Install tab in my current TWRP? Because it doesn’t show any files there. Also do I download the latest 3.2.1-x TWRP from the link you provided?
Click to expand...
Click to collapse
You will find TWRP 3.2.1-x v8.61 in the link I provided. Download that to your phone and save it. Restart your phone in recovery mode and in the current TWRP that you have, click the 'Install' button. By default, you will be shown zip files,if any. TWRP comes as an img file. So click the 'show img files' button at bottom right in TWRP and navigate to where you saved it and select it. Slide the bottom bar to install, you will be asked where to install it to. Select 'Recovery' and again slide the bar. It will be installed. To confirm, restart in recovery mode and check the version number of TWRP.
eng.stk's TWRP is compatible with OOS and custom ROMS. The offficial one doesn't work with some custom ROMs.
tnsmani said:
You will find TWRP 3.2.1-x v8.61 in the link I provided. Download that to your phone and save it. Restart your phone in recovery mode and in the current TWRP that you have, click the 'Install' button. By default, you will be shown zip files,if any. TWRP comes as an img file. So click the 'show img files' button at bottom right in TWRP and navigate to where you saved it and select it. Slide the bottom bar to install, you will be asked where to install it to. Select 'Recovery' and again slide the bar. It will be installed. To confirm, restart in recovery mode and check the version number of TWRP.
eng.stk's TWRP is compatible with OOS and custom ROMS. The offficial one doesn't work with some custom ROMs.
Click to expand...
Click to collapse
he is unable to mount storage via twrp , i have the sol but it will format your whole data / internal storage if your wiling to .
1 ) Go to twrp
2 ) wipe - > Advance wipe > change system file partation
3) if your on F2FS change to ext 4 or vice versa .
4 ) you will be able to mount sdcard
and dont flash this rom again , faceed same issue while flashing some oreo rom .
P.S : do it at your own risk .
AkR2014 said:
he is unable to mount storage via twrp , i have the sol but it will format your whole data / internal storage if your wiling to .
1 ) Go to twrp
2 ) wipe - > Advance wipe > change system file partation
3) if your on F2FS change to ext 4 or vice versa .
4 ) you will be able to mount sdcard
and dont flash this rom again , faceed same issue while flashing some oreo rom .
P.S : do it at your own risk .
Click to expand...
Click to collapse
Thanks man :highfive: I have really nothing to lose anyways so I gotta try that lol. How can I know whether I am on F2FS or EXT 4 though? And once it’s done can I access to my phone storage while it’s in recovery mode and just paste new rom to internal storage? Or do I need to push the rom via adb while in fastboot mode? Thinking to try out Paranoid rom which is based on Nougat, right?
tnsmani said:
You will find TWRP 3.2.1-x v8.61 in the link I provided. Download that to your phone and save it. Restart your phone in recovery mode and in the current TWRP that you have, click the 'Install' button. By default, you will be shown zip files,if any. TWRP comes as an img file. So click the 'show img files' button at bottom right in TWRP and navigate to where you saved it and select it. Slide the bottom bar to install, you will be asked where to install it to. Select 'Recovery' and again slide the bar. It will be installed. To confirm, restart in recovery mode and check the version number of TWRP.
eng.stk's TWRP is compatible with OOS and custom ROMS. The offficial one doesn't work with some custom ROMs.
Click to expand...
Click to collapse
Thanks for clarification tnsmani, appreciate the time you put into it. But as the person who replied to your text, I cannot mount the storage in TWRP which would prevent me of flashing pretty much anything on phone in TWRP.
Vaahtopahvi said:
Thanks man :highfive: I have really nothing to lose anyways so I gotta try that lol. How can I know whether I am on F2FS or EXT 4 though? And once it’s done can I access to my phone storage while it’s in recovery mode and just paste new rom to internal storage? Or do I need to push the rom via adb while in fastboot mode? Thinking to try out Paranoid rom which is based on Nougat, right?
Click to expand...
Click to collapse
yap you will be able to access your internal storage as well flash any thing you want from internal storage , no need to push via adb , use deskinfo app from playstore to check
the format of your data partition. yah try Omni 8.1.0 really awsome rom i am currently using. :laugh:
Vaahtopahvi said:
Thanks for clarification tnsmani, appreciate the time you put into it. But as the person who replied to your text, I cannot mount the storage in TWRP which would prevent me of flashing pretty much anything on phone in TWRP.
Click to expand...
Click to collapse
If you are able to boot into fastboot mode, you can install TWRP through ADB.
But you can not copy, paste in TWRP.
AkR2014 said:
yap you will be able to access your internal storage as well flash any thing you want from internal storage , no need to push via adb , use deskinfo app from playstore to check
the format of your data partition. yah try Omni 8.1.0 really awsome rom i am currently using. :laugh:
Click to expand...
Click to collapse
Great to hear that. Though I don’t have Gapps installed. Accidentally tried to flash the wrong one before the mounting problem occurred and now you know rest of the story :laugh:
I’ll try to find another way to check it though. Oh and as well as the ROM
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Unlocked bootloader is required.
This device has 2 "slots" for ROMs / firmware. TWRP will detect whichever slot is currently active and use that slot for backup AND restore.
There are buttons on the reboot page and under backup -> options to change slots. Changing the active slot will cause TWRP to switch which slot that TWRP is backing up or restoring.
You can make a backup of slot A, switch to B, then restore the backup which will restore the backup of A to slot B.
Changing the slot in TWRP also tells the bootloader to boot that slot.
Warning:
Do NOT switch slots unless you have installed copy-partitions-AB.zip or manually flashed the bootloader on both the slots:
This device comes out of the box with the bootloader installed only on the active slot (eg: bootloader_a).
Once you manually switch slots, your device will use the other bootloader partition (eg: bootloader_b) which is empty because of this factory setup therefore the device won't be able to boot in any way.
For this reason you should install the bootloader on your own on both the slots with fastboot or copy the currently installed one to the inactive slot by flashing copy-partitions-AB.zip at least once.
Note:
Decryption only works when TWRP is permanently installed.
Installation
To temporarily boot this recovery:
Code:
fastboot boot twrp-[B]version[/B]-[B]build[/B]-river.img
To permanently install it:
Temporarily boot TWRP
Put the TWRP image in your external SD Card or, in case you don't have one, push it to /data with adb this way:
Code:
adb push twrp-[B]version[/B]-[B]build[/B]-river.img /data/
Tap Advanced -> Install Recovery Ramdisk -> Navigate to /data or /external_sd and select TWRP -> Swipe to Install
If you previously installed Magisk: Select Fix Recovery Bootloop from Advanced to fix/avoid recovery bootloops
Done! Optionally you can delete TWRP from /data or from your external SD Card now.
Download
AndroidFileHost
XDA:DevDB Information
TWRP for Moto G7, Tool/Utility for the Moto G7
Contributors
Alberto97
Source Code: https://github.com/TeamWin
Version Information
Status: Beta
Created 2019-04-14
Last Updated 2019-07-02
I went insane to figure out decryption was not possible by just fastboot booting the image. I hope the hard work paid off
this is a blessing, i was working on twrp as well but hdd fail and it was music to my ears when it was mentioned this post went up in the tele group. so thanks bro
Awesome. Getting mine today now!! )
Sent from my LG-VS980 using Tapatalk
So here's my experience so far.
Backup, works just fine, afaik.
Restore, System,etc results in bootloop. Data restore, gets "extractTarFork() process ended with ERROR: 255"
Not sure if this is already known but figured id share what ive experienced. also feel free to tell me if im doing stuff wrong, it's been a while since i messed with android more than just using it.
Edit: This is with it perm installed.
Is this for all moto g7 versions
Hello
Very happy to see we now have TWRP. In the interest of avoiding bootloops though, I'll wait to install until it's more stable
BTW, I don't know if you guys get this, but on a us retail Moto g7 (unlocked bl obv) every time I try to boot an unofficial image I get
Code:
Command failed: remote error ' '
Any idea on what is happening?
Awesome!
This is exciting stuff. Can't wait to get busy working on it
sd86 said:
So here's my experience so far.
Backup, works just fine, afaik.
Restore, System,etc results in bootloop. Data restore, gets "extractTarFork() process ended with ERROR: 255"
Not sure if this is already known but figured id share what ive experienced. also feel free to tell me if im doing stuff wrong, it's been a while since i messed with android more than just using it.
Edit: This is with it perm installed.
Click to expand...
Click to collapse
Does flashing work?
Sent from my moto g(7) using XDA Labs
Alberto97 said:
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Unlocked bootloader is required.
This device has 2 "slots" for ROMs / firmware. TWRP will detect whichever slot is currently active and use that slot for backup AND restore. There are buttons on the reboot page and under backup -> options to change slots. Changing the active slot will cause TWRP to switch which slot that TWRP is backing up or restoring. You can make a backup of slot A, switch to B, then restore the backup which will restore the backup of A to slot B. Changing the slot in TWRP also tells the bootloader to boot that slot.
Decryption only works when TWRP is permanently installed.
Installation
To temporarily boot this recovery:
Code:
fastboot boot twrp-[B]version[/B]-[B]build[/B]-river.img
To permanently install it:
Temporarily boot TWRP
Put the TWRP image in your external SD Card or, in case you don't have one, push it to /data with adb this way:
Code:
adb push twrp-[B]version[/B]-[B]build[/B]-river.img /data/
Tap Advanced -> Install Recovery Ramdisk -> Navigate to /data or /external_sd and select TWRP -> Swipe to Install
If you previously installed Magisk: Select Fix Recovery Bootloop from Advanced to fix/avoid recovery bootloops
Done! Optionally you can delete TWRP from /data or from your external SD Card now.
Download
AndroidFileHost
XDA:DevDB Information
TWRP for Moto G7, Tool/Utility for the Moto G7
Contributors
Alberto97
Source Code: [url]https://github.com/TeamWin[/URL]
Version Information
Status: Beta
Created 2019-04-14
Last Updated 2019-04-14
Click to expand...
Click to collapse
I followed steps to unlock bootloader, then flashed stock AMZ river. Did a Google restore. Followed steps to install TWRP no issues. Follow steps exactly. Booted into system, no issues. Have not done a backup yet to test. Overall it went perfectly.
Thanks so Much!
Was able to install Magisk through manager. Again all went well and rooted. Successful backup ALSO made through TWRP.
clcombs262 said:
Does flashing work?
Sent from my moto g(7) using XDA Labs
Click to expand...
Click to collapse
I didn't test yet, I'm sure someone will and let us know
Edit: Flashing works, tested flashing Magisk 19 via zip and it installed correctly.
Sent from my moto g(7) using Tapatalk
sd86 said:
I didn't test yet, I'm sure someone will and let us know
Edit: Flashing works, tested flashing Magisk 19 via zip and it installed correctly.
Click to expand...
Click to collapse
Flashing works for me too....
Magisk v19 or v18.1 tho sends me into bootloops. Mind you, I'm running the RR GSI I flashed via TWRP
sd86 said:
So here's my experience so far.
Backup, works just fine, afaik.
Restore, System,etc results in bootloop. Data restore, gets "extractTarFork() process ended with ERROR: 255"
Not sure if this is already known but figured id share what ive experienced. also feel free to tell me if im doing stuff wrong, it's been a while since i messed with android more than just using it.
Edit: This is with it perm installed.
Click to expand...
Click to collapse
Did you restore "system" or "system image"? In the first case It's normal you get a bootloop, you changed the content of the system partition and that triggers verity. You can use "system image" that makes a bit per bit copy of the partition to avoid problems. Obviously that does not work if you manually changed even just a file.
TLDR: Just disable verity, you should be able to do that easily with Magisk.
About the extractTarFork() error instead it's something that I've seen on every device I used TWRP. I never figured out what means, I guess data was not backed up properly but I would not worry about that, it rarely happens. Just to know, did you backup on an external sd or internal storage?
B__B said:
Is this for all moto g7 versions
Click to expand...
Click to collapse
It is for all G7 variants. G7 Play/Power/Plus are different devices and require different builds.
I hope that answered your questione somehow (I'm not sure what you meant with 'versions').
I ment the for the basic g7 and thanks it helps that's what I have
Alberto97 said:
Did you restore "system" or "system image"? In the first case It's normal you get a bootloop, you changed the content of the system partition and that triggers verity. You can use "system image" that makes a bit per bit copy of the partition to avoid problems. Obviously that does not work if you manually changed even just a file.
TLDR: Just disable verity, you should be able to do that easily with Magisk.
Click to expand...
Click to collapse
This can be done with ADB interface as well....
Code:
adb disable-verity
Work moto g7 power??
Alberto97 said:
Did you restore "system" or "system image"? In the first case It's normal you get a bootloop, you changed the content of the system partition and that triggers verity. You can use "system image" that makes a bit per bit copy of the partition to avoid problems. Obviously that does not work if you manually changed even just a file.
TLDR: Just disable verity, you should be able to do that easily with Magisk.
About the extractTarFork() error instead it's something that I've seen on every device I used TWRP. I never figured out what means, I guess data was not backed up properly but I would not worry about that, it rarely happens. Just to know, did you backup on an external sd or internal storage?
It is for all G7 variants. G7 Play/Power/Plus are different devices and require different builds.
I hope that answered your questione somehow (I'm not sure what you meant with 'versions').
Click to expand...
Click to collapse
Internal and thank you very much for the information.
Sent from my moto g(7) using Tapatalk
Do I just flash the standard Magisk zip after installing TWRP? The install process seems to have broken Magisk within Android and it is no longer detected.
Omegapsy said:
Do I just flash the standard Magisk zip after installing TWRP? The install process seems to have broken Magisk within Android and it is no longer detected.
Click to expand...
Click to collapse
Yes, install Magisk after TWRP and yes, Magisk might no longer work after installing TWRP. This happens because of some patching Magisk does to the kernel that gets reverted when you tap on "Fix recovery bootloop".
I haven't had any time to play with my G7 but is there recovery Treble enabled? I'm assuming yes. Has anyone try any of the GSI's for PIe out there? or even the Q beta GSI?
Well. This was idiot-simple, too good to be true but it worked for me -- I did not create any of this, thanks to those who did, but this post may help other non-experts trying to cobble different suggestions from different threads into a solution for their device.
Again, I am on Miui 11.0.6 -- which I hate so much I was willing to risk a brick to get root.
I'd tried all XDA solutions at time of post for getting past the TWRP encryption password screen except for the one suggesting the use of a file called dummy.img which was beyond my understanding.
I used the file versions recommended by the experts here.
twrp_v323-4_nitrogen_nijel8-MOD.img (or whatever the latest version of that customized TWRP is) -- put it on your pc, install using fastboot / adb
latest orange fox zip from https://files.orangefox.tech/OrangeFox-Stable/nitrogen/ -- put it on your Micro SD Card, NOT your main phone storage.
latest magisk (version 20.1 at time of this post) -- put it on your Micro SD Card, NOT your main phone storage.
So. Install TWRP with ADB/Fastboot. In terms of TWRP getting overwritten by the stock recovery, there are several ways to ensure you boot back into TWRP but none of them worked every time for me apart from using the fastboot command: fastboot boot twrp.img (or whatever you called your TWRP file).
Once TWRP is installed and you're rebooted to it using the above command, all you have to do is hit cancel when the request for the password comes up, choose install, and then choose OrangeFox from the SD Card. (The SD card does not require a password).
OrangeFox -- God bless its creators -- automatically reboots and automatically decrypts your main storage -- eliminating all need for further tricks to retain custom recovery.
At that point, all you have to do is OrangeFox to install Magisk from the SD card, and then permit OrangeFox to wipe the dalvik cache and reboot to system.
All done!
Thanks to everyone here who actually created all these solutions. I realize anyone could have extrapolated what to do from existing threads and I may be oversimplifying, but being simple in tech terms myself, I thought it might be a time-saver for others like me.
it should be https://files.orangefox.tech/OrangeFox-Stable/nitrogen/
Thanks!
kruzyk said:
it should be https://files.orangefox.tech/OrangeFox-Stable/nitrogen/
Click to expand...
Click to collapse
Hi, sorry I missed your correction my thanks are six months late, updated the link! Best wishes