Database Info

[Q] Is there a way to install temporary recovery on SGR

Hi I am a new member on this forum, though I had been browsing this forum for long long time, I had not registered. Recently I had the courage to root and install omnirom on my phone (as my phone is getting old, i was ready to take the chances of bricking my device. I verified my device with eMMC brick bug tester and my device is frees from that bug, probably as my motherboard was changed under warranty). After toying with omnirom, I am back on stock rom. I went to Samsung Service Center and got my factory firmware installed for Rs 225/- (I had taken nandroid backup with epsilon 6.0... version of CWM, but it missed preload partition and restored the backup with philz recovery and my preload partition was erasaed and have to go for SSC).
I have few queries regarding the SGR, please help me with them:
1. Is there a temporary recovery for SGR (ie, can be flashed with stock recovery and returns back to stock on reboot. The zip file has to be maintained on SD card)
For SGS2: http://forum.xda-developers.com/galaxy-s2/general/guide-root-unroot-stock-ics-firmware-t1501719
2. In order to restore the partition on my own, I tried and searched net for recovery using testdisk and had taken a file image of the SGR internal flash disk. I opened it with testdisk, but testdisk was not able recognise the partitions I tried EFI GPT as suggested and Intel partiton table type and both did not work. Do you know the partition table type for this?
recovery link: http://www.df.lth.se/~jokke/androidfilerecovery/
3. I was just curious if becoming root (on adb shell) is just running su, thought I would copy su binary from superuser zip ro sdcard and run it with the path, but it just runs and nothing happens (I need this to remove few samsung apps esp, vlingo. I plan to do it from recovery -> adb shell -> su and delete apk & odex files).
This has been a great forum and helped me a lot. Thank you guys for all your effort.

Guide: How to decrypt data in TWRP for Le Pro 3 AI

As you all know we have been searching for ways to root the Le Pro 3AI but failed. There are even 2 twrp but you can't really do much with them. TWRP 3.1 did not even start for me but 3.0.3 worked but what's the real problem? You can't mount /data and also i found another partition named /custom. It always fails to mount and there is no way to format it.
When you enter TWRP it ask for a password to decrypt. Simply click cancel and go to wipe, advanced wipe and check the data partition. Select repair file system and change it to ext2 and then back to ext4. Reboot to twrp again I don't think this is necessary but better take precautions. Now go to mount and select data you will see that you can actually mount it(~24000mb) .
You can also enable MTP to copy files to your phone in recovery such as .zips. I hope this helps you in way. I hope the devs find a way to make it possible to flash custom ROMs for this phone without any message appearing during boot and that there is no problem with imei. Thanks for reading and don't give up with this phone else it will be money down the drain. If I helped press the thanks button.

how did you install the TWRP?
im a noob in this

okay! so after attempting to install TWRP my phone bricked haha
i had to flash again the rom. geez!
i better not attempt again.

twrp isn't really a problem. it works for the most part, just cant be perma flashed, only booted. you can still flash zips via sideload as it is though, so that was never a *huge issue*. thing is, modifying system partition on official builds (25, 28) will cause security lockup. kernel needs to be patched, and prolly bootloader for this to be bypassed, and it seems its not easy. consequently root will fail too. on 27 though, you can easily boot twrp and flash a custom zip (except root), so there is nothing preventing you from removing bloat. even xposed works. you can even flash 27 kernel on both 25/28 and clean them too using same flashable zips. as far as custom rom goes, yeah, no, mtk device. prolly not gonna happen. be happy if you get root eventually.

sikica133 said:
twrp isn't really a problem. it works for the most part, just cant be perma flashed, only booted. you can still flash zips via sideload as it is though, so that was never a *huge issue*. thing is, modifying system partition on official builds (25, 28) will cause security lockup. kernel needs to be patched, and prolly bootloader for this to be bypassed, and it seems its not easy. consequently root will fail too. on 27 though, you can easily boot twrp and flash a custom zip (except root), so there is nothing preventing you from removing bloat. even xposed works. you can even flash 27 kernel on both 25/28 and clean them too using same flashable zips. as far as custom rom goes, yeah, no, mtk device. prolly not gonna happen. be happy if you get root eventually.
Click to expand...
Click to collapse
can you tell me the procedure on installing twrp?
i really wanted to enable multi window via adb when on recovery mode.
thanks

sikica133 said:
twrp isn't really a problem. it works for the most part, just cant be perma flashed, only booted.
Click to expand...
Click to collapse
I could flash only 3.0.3 . 3.1 never worked for me. Can't even boot.

i never said it could be flashed. it could be booted into. there are plenty of guides around how to boot recovery using fastboot (google fastboot boot recovery.img). once there, you can simply use adb sideload, or integrated file manager to clean system apps and reboot back into os. if you are using 25/28 u'll need to play a bit more to get everything up and running (imei issues), on 27S (multilanguage rom) this is pretty straightforward and no fixing is required

adb devices and uninstall system app
adb devices and uninstall system app
minimal_adb_fastboot_1.4.3_portable --- download androidfilehostcom/?fid=457095661767103465
cmd-here.exe
adb devices
adb shell
pm uninstall -k --user 0 [apk name]
com.letv.agnes
com.icoolme.android.weather
com.letv.android.bugreporter
com.letv.android.carservice
com.letv.android.ecoProvider
com.letv.android.letvyellowpage
com.letv.android.ota
com.letv.android.client
com.letv.android.quicksearchbox
com.letv.android.telextra
com.letv.android.usermanual
com.letv.app.appstore
com.letv.bsp.crashhandler
com.letv.bugpostbox
com.letv.lesophoneclient
com.letv.letvshop
com.singulariti.niapp
com.sohu.inputmethod.sogou.leshi
com.tencent.android.location
sina.mobile.tianqitongletv
com.autonavi.minimap
com.tencent.reading
com.le.share.pro3ai
com.letv.games
com.android.calendar
com.android.noisefield
youtubecom/watch?v=TSwBsw6MgiA
Gapps apk
fex-net/934605209940/246920922 - 4pda
lucky patcher.apk install -- delete all google applications
1-GoogleBackupTransport.apk install and Give all permissions in menu applications
2-GoogleLoginService.apk install and Give all permissions in menu applications
3-GoogleServicesFramework.apk install and Give all permissions in menu applications
4-Phonesky.apk install and Give all permissions in menu applications
5-PrebuiltGmsCore.apk install and Give all permissions in menu applications
İ LOVE TURKEY

Monster 00 said:
As you all know we have been searching for ways to root the Le Pro 3AI but failed. There are even 2 twrp but you can't really do much with them. TWRP 3.1 did not even start for me but 3.0.3 worked but what's the real problem? You can't mount /data and also i found another partition named /custom. It always fails to mount and there is no way to format it.
When you enter TWRP it ask for a password to decrypt. Simply click cancel and go to wipe, advanced wipe and check the data partition. Select repair file system and change it to ext2 and then back to ext4. Reboot to twrp again I don't think this is necessary but better take precautions. Now go to mount and select data you will see that you can actually mount it(~24000mb) .
You can also enable MTP to copy files to your phone in recovery such as .zips. I hope this helps you in way. I hope the devs find a way to make it possible to flash custom ROMs for this phone without any message appearing during boot and that there is no problem with imei. Thanks for reading and don't give up with this phone else it will be money down the drain. If I helped press the thanks button.
Click to expand...
Click to collapse
can you help me enable multi window?
It says that I need to mount system first at the recovery.
Please help me. Thanks a lot.

[RECOVERY] Henk's TWRP Recovery

DISCLAIMER
Code:
The usual disclaimer with an extra warning, this recovery
WILL automatically modify your phone on first boot.
While this should be an entirely safe modification
it is always possible your phone is in a broken state
either on a software or hardware level causing further problems.
This recovery should under no circumstances be flashed
for the first time on a bricked phone
as the automatic changes might damage it further.
ONLY FLASH THIS ON A PHONE IN GOOD CONDITION!
By flashing this recovery you consent to a vendor partition
being created and to take full personal responsibility of any damage
the usage of this recovery may cause rather than blaming it on me.
ABOUT
This modified TWRP is the recovery image i have been using on my personal OnePlus 3T for the past month, with the increasing popularity of system-as-root roms and the issues this causes for older zip files (Such as Google Apps not flashing with wrong arm version errors) i have decided that it would be worth sharing with the community. This recovery image is a ramdisk modification of the TWRP supplied by the LineageOS Unofficial Treble Port Project (Similar to how SHRP is a ramdisk modification of existing TWRP images). Because this is not a source modification (and neither has TWRP been compiled from source) you can find the original source code in their topic. I hope this recovery will be useful to those who often flash multiple kinds of roms and want one recovery that does it all. It has been tested on the Oxygen OS 4, 5 and 9 firmwares and should have great compatibility with all of them.
Included Features
Automatic Vendor Partition Creation and full Treble support
WARNING: Because this recovery will automatically create the vendor partition it should exclusively be used on devices in good conditions. In the very rare case that bricks occur you can revert the change using the MSMDownloadTool (This can only be used on healthy hardware). If you are unsure about the condition of your device or if your device is currently in a bricked state it is best to use another recovery. I am not responsible for further damage to your phone.
Originally the TWRP image provided by the Treble project needs you to type in the 'treblize' command followed by manual reboots, I have automated this process. From the moment you first boot this recovery the vendor partition will automatically be created and the recovery reboots automatically in a new recovery session (This is not a crash and only happens once). If vendor partition has been detected you will be able to see /treblized as a directory on your phone (This is done in RAM and only visible during your recovery session). The vendor partition does not conflict in any way, you can use and pass safetynet on regular roms at will as it is invisible to a rom using a non treble kernel. Before flashing GSI roms please first flash a proper vendor partiton (This can be done by flashing the LineageOS treble rom the regular way).
/system and /system_root hybrid for maximum compatibility!
This is one of my main reasons for sharing this recovery publicly, i have modified the /etc/fstab file to be able to both mount to /system and to /system_root. This means that older zips that expect /system now work again without breaking compatibility with newer system as root or GSI roms. This is one recovery that can do it all! Inside the root folder you will find a flashable zip called Mount-System.zip. This can be used before incompatible zips to mount the /system partition correctly. This tool will automatically detect system-as-root if present and mount /system to /system_root/system, if not present it mounts /system to /system_root. You should prefer this method over the mounting options found in the menu, these should only be used for unmounting system. Keep in mind that by doing this you are messing around with scenario's the original developers have not foreseen and while flashing these previously broken zips is now possible you cause issues in your ROM. Always flash these previously incompatible zips with care and make a backup first! Do not use this Mount-System.zip to flash new roms, those are best flashed in an unmounted state. The same applies for Magisk and any other system-as-root compatible zips. If you are flashing regular roms my fstab changes will be enough and mount-system will not be needed.
Magisk + Magisk Manager on the ramdisk
In the / directory alongside the other zip files you will find Install-Magisk.zip and Manage-Magisk.zip, these can be used to both install and recovery from Magisk related issues. You no longer need to worry about keeping a copy of Magisk at hand after wiping the data or when you are in need of a downgrade, with this a copy of Magisk and a GUI management tool is always available to you directly from the recovery's root folder.
Persist Backup Tool
It is very important that you keep a spare backup of your persist partition, even the MSMDownloadTool will not be able to repair this as it is unique to your device. In addition devices with persist issues (Sensors, LTE, IMSEI, Wifi, not working / blank) should not use the MSMDownloadTool at all since it can leave you with an unbootable phone. Flash the Backup-Persist.zip file (Found in the recovery's root directory) to automatically create a copy of your persist partition stored on your sdcard so you can easily back this up to a secure location. Persist is even more important than backing up the EFS! An EFS backup alone will NOT recover your phone in the case of persist corruption!
Download
Modified Files
This project contains work from
TWRP Base Image and original Treblize scripts : The Unofficial LineageOS Treble Project
Install-Magisk.zip : Magisk
Manage-Magisk.zip : Magisk Manager Recovery Tool
Known issues
Before uploading i did extensive testing, in some scenario's i managed to cause a hard crash of the recovery image, this is not related to any of the included tweaks but seems to be an issue with flashing a rom when you have just formatted partitions. I advice to always reboot after a partition format or before flashing a system rom to ensure that everything is in a state it can be properly mounted. If you did trigger this white light crash do not fear, your device is not bricked (Unless whatever you flashed bricked it). You should be able to turn it off using the power button after which it will boot up just fine and you can try flashing again.
​

<deleted>

henk717 said:
Before uploading i did extensive testing, in some scenario's i managed to cause a hard crash of the recovery image, this is not related to any of the included tweaks but seems to be an issue with flashing a rom when you have just formatted partitions. I advice to always reboot after a partition format or before flashing a system rom to ensure that everything is in a state it can be properly mounted. If you did trigger this white light crash do not fear, your device is not bricked (Unless whatever you flashed bricked it). You should be able to turn it off using the power button after which it will boot up just fine and you can try flashing again.
Click to expand...
Click to collapse
Might not be restricted to just your recovery.
This happens to me on official TWRP as well, when I restore a system image from a backup. It gets stuck on a white light, and I have to hard reset it. The restore does seem to work though.

I flashed the backup persist but did not found the file it should create. Where is it located? Thanks in advance

It should be located in the main directory of your storage and be called persist.img.
However when i just did another test i noticed the zip gives a 255 error that does not happen on the zip on my gitlab.
I am unsure how this difference happened but generated a new img file where i tested and verified all the zip's manually, if you run into the 255 error please redownload and reflash.

[TWRP] TWRP 3.4-0-0 For Blu G90 G0310WW [MT6765][Android 10]

First released twrp for BLU G90 phone.
Whats working:
Adb
Mtp
USb-OTG
MicroSD
Flash Image
Mount System , Vendor, product (contents of SUPER).... mount allows reading the partitions, but was not able to write to them
Back-Up/Restore to/from usb (or micro sdcard).... Due to size of super.img needed to format card ext4
Logcat
Screenshot
Known bug:
**Solved with new tree file**--data decryption is not working, so not able to read or backup internal storage.--
Built with Minimum Manifest _branch 10.0 :
https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni
Kernel source :
https://github.com/mrmazakblu/Blu_G90_G0310WW_stock_kernal
Device Tree :
New
GitHub - mrmazakblu/device_PBRP_BLU_G90_G0310WW at TWRP
Contribute to mrmazakblu/device_PBRP_BLU_G90_G0310WW development by creating an account on GitHub.
github.com
Download :
Releases · mrmazakblu/device_PBRP_BLU_G90_G0310WW
Contribute to mrmazakblu/device_PBRP_BLU_G90_G0310WW development by creating an account on GitHub.
github.com
Old
https://github.com/mrmazakblu/device_TWRP_BLU_G90_G0310WW
Download : https://github.com/mrmazakblu/device_TWRP_BLU_G90_G0310WW/releases

ADB Sideload is also broken.

Shananiganeer said:
ADB Sideload is also broken.
Click to expand...
Click to collapse
Most likely due to no able to read/ write to /data there is no place to temp store the zip.
Working on alternative options at the moment, as I am having trouble getting build correct to make decrypt.
Alternative is a modified /vendor.img, so device is not encrypted. But this of course is less secure.

I reformatted /data so it was unencrypted, but still couldn't use adb sideload. I was able to use adb push to put files onto the phone, but that didn't end up mattering as without rw to /system I can't install gapps XD. I'll have some time this weekend to take a look at things and try and help debug the decryption.

Appearently, this build is only missing data decryption.
Spoke with TWRP maintainer, they said this is working as intended. Super.img partitions are not currently meant to be mounted as r/w.
After I asked about flashing GApps, I was informed that there might be changes to TWRP source to allow mounting as r/w sometime sooner or later.

mrmazak said:
Appearently, this build is only missing data decryption.
Spoke with TWRP maintainer, they said this is working as intended. Super.img partitions are not currently meant to be mounted as r/w.
After I asked about flashing GApps, I was informed that there might be changes to TWRP source to allow mounting as r/w sometime sooner or later.
Click to expand...
Click to collapse
so it may seem we are waiting on how to affectively be able to modify the dynamic partitions before we can see a fully successful root. I am fairly new to these things so might be looking at it wrong.

Ivisibl3 said:
so it may seem we are waiting on how to affectively be able to modify the dynamic partitions before we can see a fully successful root. I am fairly new to these things so might be looking at it wrong.
Click to expand...
Click to collapse
To modify it "live" yes maybe.
You can modify the extracted system, as I did , using linux mount, and flash the system back modified, just like a gsi rom.
But for root, can't say.

On the latest build, was able to mount /system r/w. And successfully change the contents of it.
The patches in twrp source is not finished yet, so normal zip installs are not coded. But using adb shell (or TWRP terminal ) seem to be working.
This New build to be uploaded on github device source, as release "test build 9"

I have the G90 Pro and would love to be able to edit the build.prop file... the phone has a ridiculously low number of volume steps for media, 7.
Is there any way to boot into TWRP temporarily and edit the file, just to see if that will increase the steps? (by adding ro.config.media_vol_steps=30 for example)

johnsag49 said:
I have the G90 Pro and would love to be able to edit the build.prop file... the phone has a ridiculously low number of volume steps for media, 7.
Is there any way to boot into TWRP temporarily and edit the file, just to see if that will increase the steps? (by adding ro.config.media_vol_steps=30 for example)
Click to expand...
Click to collapse
Well, the first thing I'm concerned with here is , I'm not sure if THIS TWRP will work on the g90 pro.
But it might be possible. I was able to mount system as r/w on my g90 in TWRP.
You would need to fastboot flash --disable-verity vbmeta and vbmeta_system to prevent red state bootloader lockout.

Ok I've found one potential bug and have a question you may be able to answer. With your build of TWRP I cannot access fastbootd. Running adb/fastboot reboot fastboot just puts me back into recovery. To change images I've been doing the following:
1. Enter bootloader and flash stock recovery you provided in your other G90 thread
2. Enter fastbootd and flash the image
3. Re-enter bootloader and flash twrp
The question I have is, how can the super partition be increased? I tried to flash the LOSQ build with gapps, but the image is > half the size of the super partition. I want to take 1GB away from the userdata partition and add it to the super partition instead. Do I mount the stock super.img in Linux and modify it to be 5GB, adjust the partitions on the eMMC so the new img will fit, flash the new super.img from bootloader, and then go into fastbootd and flash LOSQ? Where does modifying BoardConfig.mk with the new size fit in? If you don't know or don't wanna bother answering that's cool, I've been doing some digging trying to get to the bottom and I'm just not understanding how to adjust the new dynamic partition scheme.

Shananiganeer said:
Ok I've found one potential bug and have a question you may be able to answer. With your build of TWRP I cannot access fastbootd. Running adb/fastboot reboot fastboot just puts me back into recovery. To change images I've been doing the following:
1. Enter bootloader and flash stock recovery you provided in your other G90 thread
2. Enter fastbootd and flash the image
3. Re-enter bootloader and flash twrp
The question I have is, how can the super partition be increased? I tried to flash the LOSQ build with gapps, but the image is > half the size of the super partition. I want to take 1GB away from the userdata partition and add it to the super partition instead. Do I mount the stock super.img in Linux and modify it to be 5GB, adjust the partitions on the eMMC so the new img will fit, flash the new super.img from bootloader, and then go into fastbootd and flash LOSQ? Where does modifying BoardConfig.mk with the new size fit in? If you don't know or don't wanna bother answering that's cool, I've been doing some digging trying to get to the bottom and I'm just not understanding how to adjust the new dynamic partition scheme.
Click to expand...
Click to collapse
The stock /product partition is not needed in non stock roms. Google gsi flashing guide tells show to delete logical partition product.
Code:
fastboot delete-logical-partition product
This is probably what is needed.
Don't know about your plan to increase stock super.img. no idea about why you mention boardconfig.mk

This TWRP is before the patch for TWRP fastbootd, so it is not included. I have resynced source, and will see if new build works, or not. If it does will post new release.

I mentioned BoardConfig.mk because the size of the super partition is listed there, but you were totally right about the product partition and I was able to flash LOSQ+gapps after deleting it. Thanks for the assist, and your work on porting TWRP to this awesome device! Will continue to keep an eye on your work as TWRP finalizes their support for Android 10.

Will this work for the G90 Pro? My guess is not but figured I'd ask

KryptekKnight said:
Will this work for the G90 Pro? My guess is not but figured I'd ask
Click to expand...
Click to collapse
I assume not. But if you send device stock recovery, I can try to bring it up. But cannot test it, I don't have the device.

mrmazak said:
I assume not. But if you send device stock recovery, I can try to bring it up. But cannot test it, I don't have the device.
Click to expand...
Click to collapse
Would you be able to compile a Gcam pretty for this phone? I would be willing to supply you with whatever is within my means to provide

KryptekKnight said:
Would you be able to compile a Gcam pretty for this phone? I would be willing to supply you with whatever is within my means to provide
Click to expand...
Click to collapse
I have no idea about gcam

johnsag49 said:
I have the G90 Pro and would love to be able to edit the build.prop file... the phone has a ridiculously low number of volume steps for media, 7.
Is there any way to boot into TWRP temporarily and edit the file, just to see if that will increase the steps? (by adding ro.config.media_vol_steps=30 for example)
Click to expand...
Click to collapse
Sorry OP.....
I need to get 01 post of your topic to report on custom recoveries on the G90 Pro.
For new users, you should know about the Android 10 permission structure.
In TWRP or PBRP, through the File Manager, it is not possible to copy files to the superpartition. But you can copy files from the superpartition to the internal SD card.
Therefore, to modify files from the super partition, it will be necessary to extract the super partition and extract system-product-vendor to then carry out the modifications and repackage.
Using Havocv3.11 the volume issue dissapears...........

Well all, thanks to @lopestom , we may soon have a new device tree to build recovery from , and data decryption is working on first test img. New recovery would be pbrp instead of twrp.

cant access system partition in twrp

hey i want to install a custom rom (gsi) so i hope some people can help me out
main info: i have a ulefone note 9p with mediatek 6762 (runs with mediatek 6765 android scatter) and android 10.
this twrp is a twrp 3.4.0. built for ulefone note 9p i downloaded from here:
unofficial twrp 3.4.0 Root Ulefone Note 9P - unofficial twrp
download unofficial twrp 3.3.1 root Ulefone Note 9P, user who own Ulefone Note 9P can root it by following the below instructions
unofficialtwrp.com
after going to the painful procedure of unlocking bootloader flashing stock and twrp modified rom + rooting the device
i stuck at the procedure to install a gsi image via twrp.
i already know that the device must be unrooted and i have already gained some experiences in flashing the rom
even after a few softbricks, so i will try installing this image with a stock rom and twrp after i received the help i need.
i use a sd card because twrp always disappears when i transfer a file via my phone and i land on stock recovery.
this problem solves when i root my phone via magisk. as i heard flashing gsi's dont work in a heavy modified state (like with magisk),
so a sd card solved this problem to run files on recovery mode without file transfer and rooting.
the problem i have is the following: i followed some instructions saying to wipe some data first in advanced wipe
- also the system partition which is not available. after that tried to install the image directly. as it finds the rom from my sd card i have to select the partition type to flash image
i only have boot recovery and super available but i need the system partition. i looked in the internet further (the painful process) and it gave me some hints going to mount.
there it finds the system partition but when i set a checkmark on it nothing changes, so this hint didn't helped me.
what should i do now? i'm stuck in some dead end and i don't know what to do it seems like this is the only way for me to get it work.
please help.

i think i found something. since my phone is rooted i also tried to delete system apps which also don't work. i tried many system app removers but it always give error. i think the problem lies in permissions that are not given to this phone. how can i get full access to \ system to gain full permission rights? i also have busybox installed btw

You've to mount the /system partition as RW in order to access this storage location.
Example code:
Code:
adb devices
adb shell "su -c 'mount -t auto -o rw,remount /system'"