Database Users

Phronsis Rom Installation help required.

Friends, I am newbie in custom roms. Phronesis rom seems good and easy to install. Even being easy to install, I was unable to install Phronesis rom. The steps that I followed to install this rom are given below.
1) Downloaded Phronesis v6.2 rom from OP and copied it to SD Card.
2) Booted into TWRP recovery.
3) Selected "Wipe" option in the recovery menu.
4) Selected Advanced wipe.
5) From this menu I selected system, data, cache and delvit/art cache.
6) After selecting above options I swiped to wipe.
7) After this I went back to main recovery Menu.
8) From recovery menu I selected Install.
9) From here I chose Phronesis v6.2 rom from SD card storage.
10) Installation started and a bar started to load on the bottom of screen.
And after a few seconds (10 to 30 sec) my phone restated and stuck on note 3 logo.
At the end I didn't have any option but to re-flash stock firmware using odin.
It is the horror story of my note 3.
Please tell me where I have done wrong.

Read the FAQS and Q&A for the rom.
Especially the Q&A regarding TWRP
Did you go through Aroma installer ??

No sir, aroma installer did not start. My phone restarted spontaneously without going into aroma installer.

I have a similar Problem. I think this is caused by an incompatible (old) bootloader. I still use stock Android 4.4.2. When reading about how to install Phronesis I also stumble upon "update to 5.x first" to get a current bootloader.
Unluckily I'm not sure howto update the bootloader manually - but this could be the solution.

http://forum.xda-developers.com/galaxy-note-3/general/direct-download-bootloaders-modems-t3258803

Use TWRP 2.8.. latest version doesn't work. Check the MD5, is possible that the downloaded file is corrupted

You should really change the thread title to : Please spoon feed me, because i don't want to read at least the first thread page of the rom I'm trying to install !

Bootloop after installing TWRP and trying to start xposed

Hi there,
I followed all the instructions but I didnt read the part where it tells you that you have to install something so it can boot again. It seems that I am now unable to boot. I was really hoping that someone can help me.
I tried to install it after the first failed boot attempt but it didnt change anything.
Thank you in advance for your help.

It seems like you've installed the official build of xposed framework which is not compatible with most of Samsung devices.
You need to download the unofficial build for Samsung from here http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
TWRP should be accessible if you've installed it correctly by holding the Power, Vol up and home button at the same time.
If it boots to TWRP, go to mount the mount USB storage and place the downloaded version of Xposed on the phone then unmount USB storage and install it.
That's all

Themohd is correct
Also, there is some verity opt zip which i needed to install with twrp for disabling encryption
And remember to flash supersu v2.65+ for MM,I lost my moto droid maxx to that.

Hello everyone! New member here.
I'm posting because I experienced something similar to this.
I was flashing TWRP from pure stock but missed a certain step (provided below). When TWRP loaded, it seemed like it couldn't detect any of the partitions on my S7 Edge, so I restarted it to system and ended up in bootloop.
Here is the step from the TWRP guide:
Step: 8. Hold [Volume Up] + [Home] buttons near the end of the flash, and keep holding them until you are in recovery
Guide: http://forum.xda-developers.com/s7-edge/development/recovery-official-twrp-hero2lte-3-0-0-0-t3334084
So my question is, what does step 8 do exactly? Was it significant enough to cause the bootloop on my phone or could it have been something else? I was doing this because I want to flash Xposed Framework.
EDIT: After thinking about it, I'm sure step 8 brings you straight to recovery instead of booting into system then restarting manually into TWRP. So now I'm wondering this, what caused TWRP to not detect any of the partitions? In detail, TWRP showed all the partition sizes as "0 MB" when I went to a certain page (forgot what exactly lol). But I will follow the instructions step-by-step and get back to you guys.

[Solved][Using TWRP] ERROR 7 WHILE iNSTALLING TREBLE ROM

Model used: Lenovo Zuk Z2 plus
Alert: This method needs to format data. Try to have backups if possible.
Download both TWRP setups(new twrp and old twrp), factory2vendor.zip, vendor2factory.zip from this link:
https://forum.xda-developers.com/lenovo-zuk-z2/how-to/z2plus-treble-roms-flashing-reverting-t3778287
Quote:
Originally Posted by MRAGA (https://forum.xda-developers.com/lenovo-zuk-z2/how-to/z2plus-treble-roms-flashing-reverting-t3778287/page5)
I have asked about a solution for the various /vendor issues and haven't received any answer from anyone.
Finally I found out by myself how to fix it, and i'm here to share it with everyone.
If you're having problems when installing magisk, when trying to wipe (factory reset), if everything you try gives the /vendor failure and if you're trying to get rid of this new treble **** and want to go back to AEX 5.3 for now, here's what you should do:
1 - Format data (the option where you must type "yes" to confirm) on twrp, reboot your phone to recovery again.
2 - Now download the 4 files available in the original post (vendor2factory.zip; factory2vendor.zip; z2_plus_twrp_3.2.1-0_dmd.img and twrp-treble-1.img) and transfer them to your device.
3 - Now on your phone go to install and select install image. z2_plus_twrp_3.2.1-0_dmd.img and twrp-treble-1.img will show up. Install z2_plus_twrp_3.2.1-0_dmd.img. Reboot to recovery again.
4 - Try to flash vendor2factory. If it's successful, install twrp-treble-1.img and you're ready to go, explanation ends here.
5 - If it's Unsuccessful, install twrp-treble-1.img anyways and reboot to recovery again. Now try to flash Factory2Vendor_plus.zip and repeat steps 3 and 4. It should work. Even if it doesn't work, install z2_plus_twrp_3.2.1-0_dmd.img again and repeat steps 3 and 4.
Now you can get back to aex 5.3 and customize your device as before without any /vendor problems.
If this method works on phones other than zuk z2 then please mention in the comments. Thanks.

thanks mate

guyz_ahead said:
thanks mate
Click to expand...
Click to collapse
Happy to help bro :good:
If you used this method on any phone other than Lenovo Zuk Z2 plus and it worked then please do mention.

Awsome - v5.3 worked for me, then i tried to jump to v6 and 7 and failed.
This was the only thread which got me back to V5.3
I can't make calls for some reason, but that's a separate issue - just glad to be back on 5.3 finally.

nick2366 said:
Model used: Lenovo Zuk Z2 plus
Alert: This method needs to format data. Try to have backups if possible.
Download both TWRP setups(new twrp and old twrp), factory2vendor.zip, vendor2factory.zip from this link:
https://forum.xda-developers.com/lenovo-zuk-z2/how-to/z2plus-treble-roms-flashing-reverting-t3778287
Quote:
Originally Posted by MRAGA (https://forum.xda-developers.com/lenovo-zuk-z2/how-to/z2plus-treble-roms-flashing-reverting-t3778287/page5)
I have asked about a solution for the various /vendor issues and haven't received any answer from anyone.
Finally I found out by myself how to fix it, and i'm here to share it with everyone.
If you're having problems when installing magisk, when trying to wipe (factory reset), if everything you try gives the /vendor failure and if you're trying to get rid of this new treble **** and want to go back to AEX 5.3 for now, here's what you should do:
1 - Format data (the option where you must type "yes" to confirm) on twrp, reboot your phone to recovery again.
2 - Now download the 4 files available in the original post (vendor2factory.zip; factory2vendor.zip; z2_plus_twrp_3.2.1-0_dmd.img and twrp-treble-1.img) and transfer them to your device.
3 - Now on your phone go to install and select install image. z2_plus_twrp_3.2.1-0_dmd.img and twrp-treble-1.img will show up. Install z2_plus_twrp_3.2.1-0_dmd.img. Reboot to recovery again.
4 - Try to flash vendor2factory. If it's successful, install twrp-treble-1.img and you're ready to go, explanation ends here.
5 - If it's Unsuccessful, install twrp-treble-1.img anyways and reboot to recovery again. Now try to flash Factory2Vendor_plus.zip and repeat steps 3 and 4. It should work. Even if it doesn't work, install z2_plus_twrp_3.2.1-0_dmd.img again and repeat steps 3 and 4.
Now you can get back to aex 5.3 and customize your device as before without any /vendor problems.
If this method works on phones other than zuk z2 then please mention in the comments. Thanks.
Click to expand...
Click to collapse
Why just QPST 4.0 with retain userdata xml you save all userdata and update everything to new

[Fix] Internal memory shrank after root

Hi
First of all, thanks for the great job done here. I am a noob, but I try hard. I bought recently a Galaxy A40 dual sim, android 10. I rooted it following the post of topjohnwu on github. As my device does not have boot ramdisk, Magisk is in Recovery. All went well (apart the fact that root access appears inconsistent and not really linked to the way I boot (system or system with Magisk)).
So I started installed some stuff and remove others. But I just discovered that the internal memory shrank from 64 to 16 Go. According to topjohnwu ‘s page, I did something wrong. I searched a bit and found TWRP may be used to fix that.
I would like to know if it is right, if possible the procedure (for a noob), and to know if I will have to loose all my settings, apps installed, etc.
Many thanks in advance

Froyris said:
Hi
First of all, thanks for the great job done here. I am a noob, but I try hard. I bought recently a Galaxy A40 dual sim, android 10. I rooted it following the post of topjohnwu on github. As my device does not have boot ramdisk, Magisk is in Recovery. All went well (apart the fact that root access appears inconsistent and not really linked to the way I boot (system or system with Magisk)).
So I started installed some stuff and remove others. But I just discovered that the internal memory shrank from 64 to 16 Go. According to topjohnwu ‘s page, I did something wrong. I searched a bit and found TWRP may be used to fix that.
I would like to know if it is right, if possible the procedure (for a noob), and to know if I will have to loose all my settings, apps installed, etc.
Many thanks in advance
Click to expand...
Click to collapse
You will lose all your data, settings, and everything
Try formatting userdata in TWRP.
If that doesn't solve your issue, wipe userdata with adb (see if you can access all your storage), if still not, format again with TWRP.

Thanks a lot for your answer. I have not installed TWRP yet. Should I follow the TeamWin - TWRP page for Samsung Galaxy A40 (App Install Method or others) or the thread on XDA ([RECOVERY][OFFICIAL] TWRP for Galaxy A40 [A405FN] by Ponces)? I am not sure I understood the procedure described in this thread actually. In any case, a step by step procedure to install twrp would help a lot.

Froyris said:
Thanks a lot for your answer. I have not installed TWRP yet. Should I follow the TeamWin - TWRP page for Samsung Galaxy A40 (App Install Method or others) or the thread on XDA ([RECOVERY][OFFICIAL] TWRP for Galaxy A40 [A405FN] by Ponces)? I am not sure I understood the procedure described in this thread actually. In any case, a step by step procedure to install twrp would help a lot.
Click to expand...
Click to collapse
I'd definitely follow the xda thread you mentioned.
I personally do not own a Galaxy A40, but feel free to ask me about the steps you don't understand -- if I can't help you, you can always just ask them in the thread above.
Also, if you don't feel comfortable flashing TWRP, you could try wiping userdata via adb, see if that solves your issue, and then there's no need to fiddle around with flashing TWRP.

Fixed. Procedures:
- used TWRP app as my mobile is rooted
- downloaded TWRP image with the app
- patched this image with magisk
- flash the patched image with TWRP app
- TWRP is now the recovery mode, no wipe, no magisk lost
- Tried a backup in TWRP, ended by a "createTarFork() process ended with ERROR: 255”
- TWRP, wipe, advanced wipe, on data partition, repair or change, resize (following https://forum.xda-developers.com/galaxy-s8/help/galaxy-s8-16gb-magisk-root-fix-t3625025)
- Back to normal internal memory size; Magisk / root still there, data and apps still there.
Great!

Froyris said:
Fixed. Procedures:
- used TWRP app as my mobile is rooted
- downloaded TWRP image with the app
- patched this image with magisk
- flash the patched image with TWRP app
- TWRP is now the recovery mode, no wipe, no magisk lost
- Tried a backup in TWRP, ended by a "createTarFork() process ended with ERROR: 255”
- TWRP, wipe, advanced wipe, on data partition, repair or change, resize (following https://forum.xda-developers.com/galaxy-s8/help/galaxy-s8-16gb-magisk-root-fix-t3625025)
- Back to normal internal memory size; Magisk / root still there, data and apps still there.
Great!
Click to expand...
Click to collapse
thx for explaining so beautifully thx alot brother

[help needed] Recovering my phone

So I flashed LineageOS 18.1 and tried it a bit. I wanted OPlauncher in LineageOS but placed it in wrong root folder and now it won't boot.
I decided to just flash back stock OS because I like it more anyway. But when I flashed it in the recovery, i rebooted and it didn't work. It still shows the LineageOS boot animation and reboots after a while and goes back to lineage fastboot.
Then I flashed TWRP to install the stock OS through internal storage, that didn't work either.
Tried flashing on both A and B slot. No success.
In the end I only have TWRP and a boot animation from LineageOS.
Can someone tell me what to do to go back to complete stock?
Thank you!

bokkoman said:
Can someone tell me what to do to go back to complete stock?
Click to expand...
Click to collapse
Boot to TWRP, backup your data if you haven't done so already. (It will get wiped when you go back to OOS, and will need to be wiped to boot)
Option 1 (To stay, the route I always try first as it doesn't relock the bootloader):
- Fastboot Rom
- Fastboot Rom Thread
- I also cover this in my Installing LOS Guide.
- You might also see this post from that thread. You can create your own fastboot ROMs, as that thread as not been updated in a while.
Option 2 (This requires Windows, and will relock the bootloader)
- MSM Tool Thread. This will make your phone exactly as it was out of the box. Make sure you have the correct drivers installed.

OhioYJ said:
Boot to TWRP, backup your data if you haven't done so already. (It will get wiped when you go back to OOS, and will need to be wiped to boot)
Option 1 (To stay, the route I always try first as it doesn't relock the bootloader):
- Fastboot Rom
- Fastboot Rom Thread
- I also cover this in my Installing LOS Guide.
- You might also see this post from that thread. You can create your own fastboot ROMs, as that thread as not been updated in a while.
Option 2 (This requires Windows, and will relock the bootloader)
- MSM Tool Thread. This will make your phone exactly as it was out of the box. Make sure you have the correct drivers installed.
Click to expand...
Click to collapse
Thank you!
I went with the MSM tool, and with some struggle in the beginning with connecting (sahara error), it finally succeeded.
Device is back to normal.