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.

[Completed] Recovery Permission Error

Hi @all
i have successfully compiled twrp recovery from source with ubifs support for my device & i can do backup with it & all other features but i am not able to restore those backup whenever i try to restore the backup the the system gets formatted but the recovery can't write or make directory inside system or data folders with "mkdir(): Permission denied" error & even with root shell a can't make folders inside /system or /data when they r mounted & i don't have any clue why this is happening cause i am building from source for the first time so am new to it
Please if anyone can help me with this
my device is mt6571 with ubifs system
here is the twrp log of the error http://pastebin.com/nbh0rJbi
Thanx in advance

Hi,
Thanks for using XDA Assist You can post your issue in this Thread [DEV]How to compile TWRP touch recovery and fellow members will help you there
Good Luck !

Thanx @jackeagle i have tried there before but with other issue but they could not solve it & i was left wandering i will try again with this one

[ROOT+TWRP] Pre rooted boot.img and custom TWRP and Philz for WIKO JERRY

This is my first post-after spending hours researching and drinking a million cups of coffee I managed to
create a pre rooted boot.img file for my wiko Jerry. I also modified a Philz recovery image and a TWRP with otg mouse support
(I cannot use hex editor to enable touchscreen- so it will have to do).
Simply rename to recovery.img and boot.img (choose between philz and twrp) and flash with SP flashtool.
These can be flashed separately or together whilst maintaining the existing system.img or as part of a new flash with a new system.img.
It is important to install superSU right after the recovery flash- this is best done via philz or TWRP
(save the apk to your SD card either before or after the flashing) Then choose the install option from the new custom recovery.
The app will appear on your list- do not check the root with kingo or root-checker before you install Super SU or it will say the phone isn't rooted.
Super SU will giver permissions to the adb shell (kingo) or rootchecker and then these two methods can verify the root properly !!!!!!!!
Here are the files-
Scatter file MT6580- https://drive.google.com/open?id=1GXYt925OetnJnRhHgcscJcW51sI56Atf
PHILZ recovery for wiko Jerry- https://drive.google.com/open?id=1KC9hMhCeoNIEZcvTQDNdsDMCazd0JCiP
TWRP with OTG mouse support- https://drive.google.com/open?id=1t9uBQ39C3H-_6VUGaNuSd7tz5x4t7H5V
Pre rooted boot.img- https://drive.google.com/open?id=1JYCo9Z_57Rh39sLNEHD_0X1goiuJPDOI
Any further questions please PM me or reply to this thread.
Thank-you,
Rumble_Fish

Hey Rumble_Fish,
This is my very first post on this forum (although I've lurked for a while) and I'm glad I've found your thread. I've been pulling my hair out trying to root my WIKO Jerry and so far I've been unsuccessful. Unfortunately the links you helpfully provided are dead so I'd very much appreciate a re-up!
Would you be willing to help me out with the rooting process? I've tried every method I could find but to no avail. I'm completely new to rooting so I might have made some noobish mistakes.
What I've done/tried so far:
- Unlocked bootloader and enabled USB Debugging in the phone's developer options
- Installed ADB/Fastboot drivers (although my device isn't detected in fastboot mode)
- Run every 1 click root software solution (including APK's) under the sun (unsuccessfully)
- Install MTKdroidTools (which couldn't create a scatter file)
- Install Android USB drivers (although I'm unable to install Android Bootloader Interface)
Why do I want to root this phone so badly? I want to be able to recover my files (mostly photos) after a factory reset using Diskdigger and for that I need root access.
I hope I haven't left anything out and I hope you're willing to help a newbie out! Thanks a million in advance!
Kind regards,

can you repost the link because the links are dead

Problems after Magisk update - can only enter download mode and recovery

Hey there,
I am currently struggeling with my Samsung Galaxy S7 (Exynos) device, running on superman rom (Android 8).
What happened?
For root I´m using Magisk Manager and for banking apps I have Magisk hide running. Then the program told me that there is an update (Magisk App) available. So, as always and recommended, I choosed "Direct Install" but that failed for some reason. OK I thought´, no problem. Later I wanted to reboot my phone but it didn´t. The screen says "Downloading.... Do not turn off device!". I only can enter "Download Mode" and "Recovery Mode via TWRP".
What I tried so far:
1) Wipe cache/dalvik --> not successful
2) Tried to do a factory reset via twrp --> not successful
3) Tried to flash BL via Odin --> not successful
At this time I realised that the same problem occured to my Galaxy Tablet SM-T580. So I came to the point that I did something wrong with updating magisk on both devides.
What I also tried next:
4) Tried to delete magisk modules via twrp --> not successful
5) Tried to uninstall magisk through twrp by downloading the latest Magisk app and rename it to "uninstall.zip" as recommended in installation guide --> Not successful because of Error installing zip file: Unsupported /Unknown image format (unpacking image format)
What can I do next?
Can anyone please help me, since I have two bricked devices now????

A simple kernel flashing would fix the problem, extract the original boot.img of your current ROM, and flash it via TWRP.
Cause it is clearly a problem with your boot.img, if that didn't work (I'm sure it will), then just dirty flash your current ROM.
P.S. If you are encrypted, you might encounter an error doing a simple factory reset, you'll have to format the whole data partition.

Hi @Mohamedkam000,
many thanks for your help. After hours of browsing the web and trying various methods I was able to get my 2nd device (Samsung Galaxy Tab A from 2016) back to life.
What I did: I installed the latest samsung mobile phone drivers on my PC then I connected the tablet to it. I was able to access the internal memory and in the folder "data" Magisk put a backup of the original boot.img. So I installed this "boot.img" via TWRP and voila.......everything works fine again
I´m very happy now.
But unfortunately this method didn´t work with my Samsung Galaxy S7. I just couldn´t find any boot.img file on the phone.
Mohamedkam000 said:
A simple kernel flashing would fix the problem, extract the original boot.img of your current ROM, and flash it via TWRP.
Cause it is clearly a problem with your boot.img, if that didn't work (I'm sure it will), then just dirty flash your current ROM.
Click to expand...
Click to collapse
How do I have to do this? Sorry I´m a little unexperienced so could I get a kind of an step by step guide please?
Mohamedkam000 said:
P.S. If you are encrypted, you might encounter an error doing a simple factory reset, you'll have to format the whole data partition.
Click to expand...
Click to collapse
Don´t understand this. Could you please explain again?
Thank you so much already.
Kind regards,
cap.

capitarider said:
Hi @Mohamedkam000,
many thanks for your help. After hours of browsing the web and trying various methods I was able to get my 2nd device (Samsung Galaxy Tab A from 2016) back to life.
What I did: I installed the latest samsung mobile phone drivers on my PC then I connected the tablet to it. I was able to access the internal memory and in the folder "data" Magisk put a backup of the original boot.img. So I installed this "boot.img" via TWRP and voila.......everything works fine again
I´m very happy now.
But unfortunately this method didn´t work with my Samsung Galaxy S7. I just couldn´t find any boot.img file on the phone.
How do I have to do this? Sorry I´m a little unexperienced so could I get a kind of an step by step guide please?
Don´t understand this. Could you please explain again?
Thank you so much already.
Kind regards,
cap.
Click to expand...
Click to collapse
Glad your tablet revived again.
Magisk creates a backup of the boot.img found just before flashing magisk, it is compressed in gzip format, so you need to pull it, extract it, and push it back to the phone, then flash it.
The file is usually in /data/stock_boot_${SHA1}.img.gz
You can extract it using the built-in terminal of TWRP, if PC is not accessible at the moment by writing and executing the following command:
gunzip {stock-boot-name}.gz
Replace {stock-boot-name} with your backed-up boot name (without the curleybrackets), or you can use the following command:
gunzip *.gz
That'll extract the gzip archive, and the boot.img will be in /data of which you can navigate to it and flash it.
There's another guaranteed method, if you have the file of the ROM you're using right now, you can just open it (it's just a zip archive) and search for the boot.img of your specific phone model and flash it.
Another guaranteed method will be by flashing a custom kernel compatible with your current ROM, like Moro AiO kernel, of which has a wide support for ROMs starting from Oreo, and up to Q, AOSP, or stock-based, just in one file.
Moro's thread: Moro Kernel

you can't access kernel backup because TWRP does not support encryption and Magisk Manager might removed encryption in boot

aIecxs said:
you can't access kernel backup because TWRP does not support encryption and Magisk Manager might removed encryption in boot
Click to expand...
Click to collapse
Doesn't seem like he's encrypted, he found the boot backup of his tablet in /data so he has probably searched for a similar file on his S7, but since it is compressed, he won't find it solely.
Also he would've told us that his /data is empty or something.

start from scratch with older magisk, current 22 has bug
https://github.com/topjohnwu/Magisk/issues/4008

Thank you for your help.
I had a n old twrp backup on another external hard drive. I extracted the boot file and repached it with 7zip to boot.img and flashed through twrp. That also didn´t work for various times. TWRP always said "failed".
In the end I didn´t manage it to bring my phone back to live. Anyway, I decided to flash the latest LineageOS (Android 11) and now its running smooth again.
Thanks again.

Try using sp flash tools flashing the boot.img

Need custom recovery for Mobiistar C1 shine 4g mt 6739 device

Need custom recovery for Mobiistar C1 shine 4g mt 6739 device as m stuck need it urgently and want install android 10 gsi image my device has arm32 a only architecture some suggest me some good and lite gsi images please firstly I need custom recovery twrp please someone help.

It would be hard to support a 2018 device I guess.

[CLOSED] I Will build TWRP for your device!
I wanna build twrp for your device! Pls give info about your device! if possible give stock firmware!
forum.xda-developers.com

i can upload recovery.img file for if you want

its Mobiistar C1 shine (MT6739) arm 32bit a only supported device running on 8.1 i was some how able to root it but unable to install custom recovery if u can please build one for this device i will upload stock recovery.img in few minutes presently its bricked but i will recovery it because i have stock firmware and flashing tool of it....so dont worry just please build a custom recovery like twrp for this device asap if possible

Again: You request a TWRP build for your device going to this thread
[CLOSED] I Will build TWRP for your device!
I wanna build twrp for your device! Pls give info about your device! if possible give stock firmware!
forum.xda-developers.com

any custom recovery bro sorry for that (twrp)

my phone back running again i have flashed it with stock firmware recovery images i have attached earlier and so does phone details screenshot now present situation is 8.1 not rooted stock recovery and firmware so i hope if anyone can help i will be glad

installed latest magisk apk and .zip also by patching boot.img file and flashing that with sp tool to install magisk and got root privilege's

all now i want is proper running and fully functional custom recovery to install custom roms and mods

copvaibhav said:
its Mobiistar C1 shine (MT6739) arm 32bit a only supported device running on 8.1 i was some how able to root it but unable to install custom recovery if u can please build one for this device i will upload stock recovery.img in few minutes presently its bricked but i will recovery it because i have stock firmware and flashing tool of it....so dont worry just please build a custom recovery like twrp for this device asap if possible
Click to expand...
Click to collapse
I am not responsible for any wrongdoing by you. Always have ROM stock files. Any error, install stock recovery again.
First you need to unlock the bootloader if necessary! Unzip file attached and look 2 files.
Then, the installation plan:
0) Flash the TWRP with SPFT or fastboot;
1) Enter TWRP IMMEDIATELY without starting in the system, otherwise TWRP can revert to the stock;
2) When asked to enter the password, select Cancel;
3) Load the file with Magisk (look for any magisk19.zip for TWRP and the decryption file for EXTERNAL memory;
4) Flash Magisk immediately and then install the file data_decrypt_Mobiistar_C1_Shine.zip immediately;
5) Make FORMAT DATA - bottom left button - Type: YES. Go back to the TWRP menu;
6) Make Wipe: data, cache, dalvik (reset to factory settings! Save your data!);
7) Reboot to TWRP (password must not ask);
8) Restart on the system, root is received.

thanks bro for making recovery.img when installing magisk 19.zip its giving error on last step failed to mount /vendor/persist (invalid argument). done
after that i tried to install your data decrypt .zip after one reboot to recovery because i have tried before without reboot recovery once so this time rebooted and installed your data.zip file and again on the last step same error as magisk failed to mount /vendor/persist (invalid argument). done
after that i tried to format by typing yes but again same error failed to mount /vendor/persist (invalid argument).done
just to inform you i have formatted phone from inside by turning it on factory reset but nothing happened....and internal space is not mounting i some how managed to install these things via OTG USB but same error again and again. i am attaching screenshot also which i captured from other phone of mine.
kindly help asap

copvaibhav said:
thanks bro for making recovery.img when installing magisk 19.zip its giving error on last step failed to mount /vendor/persist (invalid argument). done
after that i tried to install your data decrypt .zip after one reboot to recovery because i have tried before without reboot recovery once so this time rebooted and installed your data.zip file and again on the last step same error as magisk failed to mount /vendor/persist (invalid argument). done
after that i tried to format by typing yes but again same error failed to mount /vendor/persist (invalid argument).done
just to inform you i have formatted phone from inside by turning it on factory reset but nothing happened....and internal space is not mounting i some how managed to install these things via OTG USB but same error again and again. i am attaching screenshot also which i captured from other phone of mine.
kindly help asap
Click to expand...
Click to collapse
This is Ok. I made TWRP fast and not remember if the stock partitions has \vendor\persist. So if has that's message is normal. Therefore messages about \vendor\nvdata;nvram;nvcfg is normal too. Very pacth zip files can delete that and the device cannot have IMEI.
First: Is good know the file TWRP worked;
- - You can't install any zip without FORMAT DATA first because FORMAT DATA process can view internal storage. If you don't FORMAT DATA maybe the zip file going wrong with MicroSD & OTG.
In this moment you understand: not use external storage! Put zip in the internal storage an try again.
About MTP: Has anything wrong wiht A8.1 & TWRP. Most devices with A8.1 and TWRP do not have access to MTP. I don't know what happens because I don't know why TeamWin was unable to resolve this.
Now you need put zip with adb command (search how to do) or use sileload on the TWRP.
PS: the picture attached by you show about decrypt. In the first moment you need acept modifications and password you press CANCEL.

lopestom said:
This is Ok. I made TWRP fast and not remember if the stock partitions has \vendor\persist. So if has that's message is normal. Therefore messages about \vendor\nvdata;nvram;nvcfg is normal too. Very pacth zip files can delete that and the device cannot have IMEI.
First: Is good know the file TWRP worked;
- - You can't install any zip without FORMAT DATA first because FORMAT DATA process can view internal storage. If you don't FORMAT DATA maybe the zip file going wrong with MicroSD & OTG.
In this moment you understand: not use external storage! Put zip in the internal storage an try again.
About MTP: Has anything wrong wiht A8.1 & TWRP. Most devices with A8.1 and TWRP do not have access to MTP. I don't know what happens because I don't know why TeamWin was unable to resolve this.
Now you need put zip with adb command (search how to do) or use sileload on the TWRP.
PS: the picture attached by you show about decrypt. In the first moment you need acept modifications and password you press CANCEL.
Click to expand...
Click to collapse
sideload is not starting forgot to mention it i have tried that also booted phone normal put the file in internal but in recovery cant have access to internal storage and yes i have press cancel first and that accepted modification but nothing happened no internal storage access only some how otg thats it i dont know what to do

copvaibhav said:
sideload is not starting forgot to mention it i have tried that also booted phone normal put the file in internal but in recovery cant have access to internal storage and yes i have press cancel first and that accepted modification but nothing happened no internal storage access only some how otg thats it i dont know what to do
Click to expand...
Click to collapse
Okay. Wait my free time and I'll create other TWRP for your device.
Reflash stock recovery if you want & test other file soon.
Update
\|/ Lucky file attached today. So install and test. You can install zip that I put before or Donwload acoording your device cpu has. Read instructions about that again.
Reference Download: https://forum.xda-developers.com/t/...ncrypt-disk-quota-disabler-11-2-2020.3817389/

thanks bro i dont know how it worked but it worked again i have to use otg but this time it worked by downloading different force disabler.zip after that i have formatted the data by typing yes it worked then again i flashed your disabler and new recovery image and phone booted magisk installed phone rooted.....thanks a ton i dont know how to say thanks you but thank you all .
can please suggest me as my mt 6739 is 32arm a only device some light gsi for my device actually i want custom mods in gsi so if u can suggest me which also supports my device i will be very thankful

copvaibhav said:
thanks bro i dont know how it worked but it worked again i have to use otg but this time it worked by downloading different force disabler.zip after that i have formatted the data by typing yes it worked then again i flashed your disabler and new recovery image and phone booted magisk installed phone rooted.....thanks a ton i dont know how to say thanks you but thank you all .
can please suggest me as my mt 6739 is 32arm a only device some light gsi for my device actually i want custom mods in gsi so if u can suggest me which also supports my device i will be very thankful
Click to expand...
Click to collapse
Look correct app to know about your device: Treble Info
You need try install AOSP 8 & 9: https://github.com/phhusson/treble_experimentations/releases
Look "bugs"; try solving; keep your time with experiments.....
After you can try LOS, RRMix, Havoc, etc.....
About this thread/ask help about Custom Recovery so Solved. @jerryhou85
Good Lucky!

system-arm-aonly-vanilla-nosu.img.xz
system-arm32_binder64-aonly-vanilla-nosu.img.xz
bro which file shpuld i download as i told you mine is 32bit arm a only (what is arm first link and arm32binder64 aonly difference) kindly tell.
just to clarify i have download both removed.xy from ext. and flashed from recovery system image but phone goes into fastboot after reboot and when rebooting in recovery at the top it shows no os installed.

lopestom said:
Okay. Wait my free time and I'll create other TWRP for your device.
Reflash stock recovery if you want & test other file soon.
Update
\|/ Lucky file attached today. So install and test. You can install zip that I put before or Donwload acoording your device cpu has. Read instructions about that again.
Reference Download: https://forum.xda-developers.com/t/...ncrypt-disk-quota-disabler-11-2-2020.3817389/
Click to expand...
Click to collapse
Sir it's stuck on password screen touch not working please fix it, I will always be grateful to you.

Honey2012 said:
Sir it's stuck on password screen
Click to expand...
Click to collapse
The first start need choose the CANCEL. I think you not know about TWRP (unofficial) and the process with device/TWRP without encryption/decryption process.
If you want that so send me some device to develop/have the possibility of getting that option.
Honey2012 said:
touch not working please fix it, I will always be grateful to you.
Click to expand...
Click to collapse
As you read, I not have your device in my hands!
Many 32bits and few 64bits devices have problem with touch screen from kernel. That's not my error! It's from device company.
I not know about touch screen work or not since copvaibhav not write about. But I won't fix this. There is also the possibility to use OTG and plug in a USB Mouse to use in TWRP.
There are solutions to fix the touch screen but I don't have the device and I don't have time to do it. Search and you will know. So solve it yourself and thank your self for it.
Ask copvaibhav for more process and using TWRP.