I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
Click to expand...
Click to collapse
First and foremost, you need to set up TWRP recovery. (IMPORTANT) Working TWRP recovery is here. TWRP FOR SAMSUNG F62
After successfully flashing the TWRP recovery, follow the below steps to flash GSI to this device.
REQUIREMENTS
1. ANY GSI IMAGE (NOT ZIP, EXTRACT THE SYSTEM.IMG AND PLACE IT IN SDCARD) (https://developer.android.com/topic/generic-system-image/releases)
2. DynaPatch (FOR FLASHING THE GSI TO SYSTEM DIRECTLY)
Instructions for install dynapatch.zip (IMPORTANT)
boot the device into TWRP recovery mode.
Then from the menu, select wipe then advance wipe and there select (dalvik, data, cache) and swipe to wipe them.
Now who place the downloaded dynapatch.zip to the main directory of SD card and in TWRP recovery select this storage of SD card and swipe to flash the dynapatch. It will take some time so be patient.
When flashing done, Tabdi reboot option and there you have to tap reboot recovery so that your recovery will be rebooted.
Instructions for flashing GSI (only follow these steps after following above dynapatch steps)
After following above steps, now from the menu, select wipe then advance wipe and there select (dalvik, data, cache) options and swipe below to wipe them.
Now place the any downloaded GSI onto your SD card Main directory. (place only the "System.img" extracted from GSI ZIP, not the GSI ZIP. You can extract the system.img by using win RAR Or 7zip).
After placing the GS, sign out app install button from the TWRP recovery. At bottom you will see install IMG Button. TAP IT TO SEE PLACED system.img
Now tap the plsced system.img and then you will be able to see few options there. From that options, tap system image option.
Now swipe to confirm flash. It will take few minutes so be patience at least for 10 minutes.
After flashing done. Tap back button and select wipe data from the TWRP menu and type yes to confirm wipe.
Now reboot system. You will see no OS installed, ignore that.
And that's it. You have successfully installed the GSI to the Samsung Galaxy F62. DOUBTS?
Related
****edit: It appears that the option "format /system" which is tucked away in a sub menu did the trick and erased the rom.
I am trying to completely delete a rom I have installed which is CyanogenMod 11 but it seems to stay no matter what, or I'm not doing it right.
First I go into recovery with the power+vol down and choosing recovery.
I have ClockworkMod 5.8.1.5.
From there I choose the wipe data/factory reset and also the wipe cache partition and wipe dalvik cache.
Then I choose the install zip from sd card to install Blackout_ICS_Incredible_v4.0.zip
After following the installer instructions and rebooting it goes back to CM11...
Any ideas how to wipe CM11 from my device?
Thanks :good:
Netanel1 said:
****edit: It appears that the option "format /system" which is tucked away in a sub menu did the trick and erased the rom.
I am trying to completely delete a rom I have installed which is CyanogenMod 11 but it seems to stay no matter what, or I'm not doing it right.
First I go into recovery with the power+vol down and choosing recovery.
I have ClockworkMod 5.8.1.5.
From there I choose the wipe data/factory reset and also the wipe cache partition and wipe dalvik cache.
Then I choose the install zip from sd card to install Blackout_ICS_Incredible_v4.0.zip
After following the installer instructions and rebooting it goes back to CM11...
Any ideas how to wipe CM11 from my device?
Thanks :good:
Click to expand...
Click to collapse
Try formatting with fastboot.
Boot your device into fastboot and type these commands
Code:
fastboot devices
Just to be sure ur devic is connected
Code:
fastboot format system
Code:
fastboot format data
Code:
fastboot format boot
If the above doesnt work, susbtitute
Code:
format
with
Code:
erase
4EXT Recovery 1.0.0.6 R2
try changing the recovery via bootloader, download latest 4ext recovery zip then rename it to PD98IMG and place it to your root directory of your sdcard. Then go into bootloader it will automatically detect zip file and will ask you for update, press volume up to start the update, reboot and your done. After flashing new recovery go into recovery and then wipe/format from there format all partitions except sd card. When done go back to main menu and select info to see the free space/size of all partitions.
Device: HTC Desire HD
ROM: CM11 M8.1
Recovery: 4EXT 1.0.0.6 R3 build 8
If it helped you then pressing then press the thanks button.
Heya there
My phone is stuck at boot (Samsung screen)
When I go to recovery mode it says "Failed to mount /efs"
I tried various guides online, including flashing a rom using odin from this link
I am not sure what version my recovery is but the options I have there are:
* reboot system now
* apply update from adb
* apply update from external storage
* wipe data/factory reset
* wipe cache partition
* apply update from cache
I can't access my phone from the phone (as in copy a .zip).
What are my choices?
I tried flashing all kinds of recovery / bls I found in some guides, but perhaps I need a step-by-step assistance so I can report success/fail and continue from there.
Cheers,
Alex
Never seen this before but I found this somewhere..
http://zidroid.com/how-to-fix-failed-to-mount-efs-for-galaxy-s3-gt-i9300/
Kinda long guide, but it would work
Sent from my Galaxy Note II using Tapatalk
Greetings users,
I am new to XDA but when I was looking around here and there i found that users has been facing several issues regarding bootloop or bootscreen struck problem. Then I found people on facebook struggling from the same problem. So what I lastly found is a basic and easy solution for this.
Follow these steps and it will take you out.
1) Firstly install Philz Touch Recovery so that you could enter custom recovery menu to make some patches.
Please note: You might need to enable USB debugging to install Philz Touch.
2) Now after you have installed Philz Touch Recovery, Go to recovery mode.
* Wipe Data/Factory Reset
* Clean to Install a New ROM
This will clear the whole things in the smartphone that needs a change.
3) For security, once again, Clear Cache and Clear Dalvik Cache.
4) Now everything has been cleared from the smartphone.
5) Now, make a reboot in recovery again and install your ROM from ZIP.
Note: What I have found is that, you have to put the ZIP file in SdCard1 or extSdCard outside any folder. Generally the recovery don't take it from the folders and might cause some bug.
For those who are using TouchWiz Revolution 7
It has some serious bugs and issues, I have tested it on specific more than two or three GT-i9082 devices.
I have also reported some bugs from it, please have a look over them HERE.
Anyone who got a bootloop/bootscreen struck, follow these.
1) Firstly install a Stock ROM of GT-i9082 using ODIN.
2) Now open and start the phone (it will take sometime to open and the stock rom will patch the original odex and library files)
3) Now Go to Settings > About > Click 6-7 times on Build to enable Developers Mode
4) Now Enable USB Debugging and Allow Mock Locations from Developers Options.
5) Now Install Philz Touch Recovery using ODIN.
6) Enter the recovery menu and perform:
* Wipe Data/Factory Reset
* Clean to Install a New ROM
7) For security, once again, Clear Cache and Clear Dalvik Cache.
8) Reboot in recovery again and install TouchWiz 7 from external Sdcard.
9) Profit!
Note: Allow 4-5 minutes after you have installed new rom after Boot Screen starts.
QUICK LINKS:
ODIN v3.07
Philz Touch Recovery
There is a thanks button out there :good:
1. Download resources:
a. Download the rom UL USER, leave it there and do nothing to it yet.
b. Download the twrp.zip file https://mega.nz/#!l8BXgaDL!Y1AH5TM9jKI5r6LtEKFN_4Po105glHNR602yVDipfF8 (if you still have twrp installed beforehand)
c. Magisk 20.0 https://github.com/topjohnwu/Magisk/releases/download/v20.0/Magisk-v20.0.zip
2. Proceed:
Do not update the UL USER rom from the device's interface (SYSTEM UI), power off, boot into TWRP. Select install zip in the following order:
a. Rom UL USER
b. Twrp.zip
c. Magisk v20.0 (or exit the main menu, select Advanced, install root also)
Done, exit the main menu select advanced wipe, wipe cache, dalvik.
Reboot the device.
Done.
By chicken
This did not completely work for me going from .35 to .64. All the steps completed successfully but when I rebooted the phone, Magisk was not installed so I didn't have root. I was able to then boot to TWRP and successfully install Magisk, but I don't know why it didn't work the first time. Anyone else try this? Did it work as intended for you?
One other thing I noticed - TWRP no longer has an option to wipe the cache under wipe > advanced, only for Dalvik/ART cache. Why?
Wish I would have tried this before i updated and lost root, i flashed a root boot.img with fastboot now im bricked and don't know what to do.
EDIT: got twrp did a factory reset and im in now.
dungnghien said:
1. Download resources:
a. Download the rom UL USER, leave it there and do nothing to it yet.
b. Download the twrp.zip file https://mega.nz/#!l8BXgaDL!Y1AH5TM9jKI5r6LtEKFN_4Po105glHNR602yVDipfF8 (if you still have twrp installed beforehand)
c. Magisk 20.0 https://github.com/topjohnwu/Magisk/releases/download/v20.0/Magisk-v20.0.zip
2. Proceed:
Do not update the UL USER rom from the device's interface (SYSTEM UI), power off, boot into TWRP. Select install zip in the following order:
a. Rom UL USER
b. Twrp.zip
c. Magisk v20.0 (or exit the main menu, select Advanced, install root also)
Done, exit the main menu select advanced wipe, wipe cache, dalvik.
Reboot the device.
Done.
By chicken
Click to expand...
Click to collapse
In my experience after install back twrp reboot back to recovery (twrp) before flashing magisk .
Does this work when updating to A10?
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.
C:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Features:- TWRP boots
- Decryption works
- Rom flashing should work
- Backups should work
- Flash partition should work
- Format/wipe data works
- Backup Restore
- Fastbootd
- System and vendor image flash should work
- Decryption works only in Android 11. Decrytprion for later versions of Android WIP
-USB-OTG - I cannot test, because I have not a USB-OTG cable. Please, send me a result to PM
Note: boot takes about one minute - it required by decryptionInstall guide:You can install it from fastboot using command
Code:
fastboot flash recovery_$(slot) path_to_recovery/recovery.img
Or you can directly boot it:
Code:
fastboot boot path_to_recovery/recovery.img
Download:Link
Sources:
angpysha/android_device_OnePlus_Nord_N100 at android-11 (github.com)
Thanks:hellisabove - for initial device tree
infectedmushi - for device tree for OnePlus 8 with working encryption
TeamWin
Reserved
Reserved
I've tried to boot / flash this on my BE2013. It's just stuck on TWRP splash screen, but with ADB active and seemingly usable.
thomaskmaagaard said:
I've tried to boot / flash this on my BE2013. It's just stuck on TWRP splash screen, but with ADB active and seemingly usable.
Click to expand...
Click to collapse
Disregard. It seems I should have been armed with more patience. People should note it might take quite a while for it to load up.
thomaskmaagaard said:
Disregard. It seems I should have been armed with more patience. People should note it might take quite a while for it to load up.
Click to expand...
Click to collapse
Oh, yes. I forgot to write that boot takes about one minute. Thanks
Thanks for releasing this. Used it this weekend on OnePlus Nord N100 Model BE2013 Oxygen OS 11.0.10.BE83BA
# TWRP recovery-3.7.0-11-08012023 worked for multiple flashed
Was working fine flashing 4 or 5 ROMs to taste test them. CAOS rom worked like a charm. Nothing else worked. Somewhere along the line I deleted a logical partition to make room for Pixel Experience. It suffered flickering / dimming issues so reflashed CAOS.
TWRP was working so well I flashed it to my phone.
# TWRP recovery-3.7.0-11-08012023 stopped being able to mount volume
Then TWRP couldn't mount the partitions for writing anymore. Volume showed 0 bytes available. Fastboot could not recreate logical partitions. Weird thing was I could write a test file in /system but I couldn't flash /system. Fastboot error messages said it could not find partition or there was no room left. Somehow TWRP's ADB shell could get into the /system partition but its flashing could not ?!?
# TWRP recovery-3.7.0-11-08012023 did not see USB drive through OTG cable
Tried to access ROM through USB drive through OTG cable. TWRP could not mount it.
# Recovery
* Had to use MSM tool to cover phone to Stock today.
* After recovery, I flashed CAOS using Fastboot instead of TWRP because I'm not sure if I did something wrong or if TWRP wasn't working properly.
# Can't boot after TWRP backup (no restore)!?!
I booted into TWRP through fastboot boot twrp.img so that it wouldn't write anything. Used TWRP to do a backup and saved backup to external sd card (not the /sdcard directory but the separate external sd card).
So I didn't flash recovery or anything else. I did a backup to an external sdcard. I did not flash or write anything to the phone's memory.
Now when booting it gets stuck on the logo!?!
How do you recover from that?
Looking at /tmp/recovery log shows that twrp wasn't able to mount /data /product
This recovery works well, it flashs every partition except the super partition you can flash it with the terminal of the recovery.
There is one obstacle, which is you need to replace stock product with gsi product to be able to flash lineage 19.1, and to be able to flash larger ROMs you need to delete the system_ext partition (I suppose ). I will attach it to my reply.
The second obstacle is the backup when restored it show some bugs. and the last one is that Android 13 is a little bugy in this slot unlike the other slot.
I flashed successfully the super image with this recovery, thank you guys.
Hi guys, I have good news for you, this recovery works in both slots ( with boot _A10 and boot_A11), so weird but true.
This recovery is fully working, I mean you can flash Zips and IMGs and you even use its built-in terminal to pull or push partitions.
There is one problem which is the resizing, you can do it with CMD command
fastboot resize-logical-partition system_a 4210000000
or
fastboot resize-logical-partition system_b 4210000000
And this can be done anly by flashing the product_a, product_b and the system_ext_b partitions with small size IMGs like product_gsi.img(you need to put this file in the adb-fastboot folder) . (you can flash it in product_a, product_b and system_ext_b. It does not serve anything, it just reduces the size of this useless partitions. You can find it with a working adb-fastboot tool.
Well, this TWRP is flashing Magisk, and I can make a backup, but when I want to restore the backup, errors occur, including the bootloop. Has anyone encountered this problem?