Related
This is a port of the ClockworkMod Recovery V3.0.0.5 for Folio100.
Almost everything is functional except some minors issues.
Known issues :
boot part is not backup when using Backup / Restore.
Update 1 : Cache is mounted at start
Installation instructions :
Download : update.zip
- Copy the update.zip to a sdcard
- Follow the same procedure as explain in this post for the FolioMod
- Don't need to wipe.
- After reboot, enter recovery again to see the change
Click to expand...
Click to collapse
Usage :
- ( VOL + ) and ( VOL - ) key to highlight the menu
- ( HOME ) key to select
Click to expand...
Click to collapse
THANKS to:
Koush : the original creator of ClockworkMod
Dexter_nlb : for the great work he makes with the FolioMod
All the peoples who help me on cyanogenmod irc channel
wolfx said:
This is a port of the ClockworkMod Recovery V3.0.0.5 for Folio100.
Almost everything is functional except some minors issues.
Known issues :
partitions do not mount automatically at startup
boot part is not backup when using Backup / Restore.
Installation instructions :
Usage :
THANKS to:
Koush : the original creator of ClockworkMod
Dexter_nlb : for the great work he makes with the FolioMod
All the peoples who help me on cyanogenmod irc channel
Click to expand...
Click to collapse
this will be so great, good joob and keep em comming. Next stop Gingerbread
Installed it just aminute ago worked great. I played around a bit, i formated system, data, cache and dalvik cache. I also tryed format boot but that was a no go. In the first clockwork 3 releases there was also this problem with boot. i cant remember if it was the same error, but its fixed now so that it works correct. I also flashed FolioMod from clockwork iwth out any problems. Really nice work
Great Job!! Now we just need some AOSP/CM7 love
Can I use it with stock rom too? Tnx
Great work thanks alot for taking the time to do this
girello71 said:
Can I use it with stock rom too? Tnx
Click to expand...
Click to collapse
I don't try backup / restore (nandroid) with stock rom maybe it work, but when i try to flash stock rom it skip the different part and don't write anything.
However, what could be interesting if backup / restore work is to make a backup of a fresh install stock rom with the last update include.
boqonx said:
Great Job!! Now we just need some AOSP/CM7 love
Click to expand...
Click to collapse
I currently work on the CM7, but be patient, it's more complicated than for recovery.
Of course dude, take your time and slowly churn that tasty gingerbread dough
wolfx said:
I currently work on the CM7, but be patient, it's more complicated than for recovery.
Click to expand...
Click to collapse
Finaly, one more rom builder. We need some options to choose from. Wish you the best of luck. And if you dont mind, maybe from time to time post progress on your work. If you need some beta testing, im there
Back to square 0
Hi,
Based on the positive response i started to install the ClockworkMod recovery. As i got the error message that there was no space on the device i did a factory reset (i have 1.3c). Now the installation of the ClockworkMod looked ok. But after i rebooted the device nothing happened (blank screen). Only the initial screen shows (with pressing the on/off-vol+ buttons) after this just a blank screen. Also if i press within the 3 sec the on/off and vol+ the screen goes blank. So i guess i have now a bricked folio and i will start to read up how to unbrick.
BTW i do not know if i did something wrong or there is/was some particularities with my configuartion or that the clockworkmod still needs some work..
Butchi said:
Hi,
Based on the positive response i started to install the ClockworkMod recovery. As i got the error message that there was no space on the device i did a factory reset (i have 1.3c). Now the installation of the ClockworkMod looked ok. But after i rebooted the device nothing happened (blank screen). Only the initial screen shows (with pressing the on/off-vol+ buttons) after this just a blank screen. Also if i press within the 3 sec the on/off and vol+ the screen goes blank. So i guess i have now a bricked folio and i will start to read up how to unbrick.
BTW i do not know if i did something wrong or there is/was some particularities with my configuartion or that the clockworkmod still needs some work..
Click to expand...
Click to collapse
If you delete the update.zip for clockwork recovery you will have normal recovery. When installing clocwork you pu the zzip to root of exterenal sd card boot to recovery do system update, device reboots, now you have to do the system update again, your now in clockwork recovery
Butchi said:
Hi,
Based on the positive response i started to install the ClockworkMod recovery. As i got the error message that there was no space on the device i did a factory reset (i have 1.3c). Now the installation of the ClockworkMod looked ok. But after i rebooted the device nothing happened (blank screen). Only the initial screen shows (with pressing the on/off-vol+ buttons) after this just a blank screen. Also if i press within the 3 sec the on/off and vol+ the screen goes blank. So i guess i have now a bricked folio and i will start to read up how to unbrick.
BTW i do not know if i did something wrong or there is/was some particularities with my configuartion or that the clockworkmod still needs some work..
Click to expand...
Click to collapse
Not sure you bricked it, you can use the fastboot method to flash the recovery again, then you can use the recovery to flash a full rom.
Btw, where do we have fastboot access? I thought what we have is the tegra bootloader which is quite risky to enter? (heard of the story of ppl getting stuck in the bootloader with no way to get out)
boqonx said:
Btw, where do we have fastboot access? I thought what we have is the tegra bootloader which is quite risky to enter? (heard of the story of ppl getting stuck in the bootloader with no way to get out)
Click to expand...
Click to collapse
you can access fastboot by pressing POWER x 3 ( attention : 3 times only not 4) then VOL UP when the folio start. I use it everyday to flash recovery.img or boot.img with no problems.
Usage :
place the recovery.img or boot.img in the same directory as fastboot then from a shell navigate to your fastboot directory and us the following command :
for recovery:
Code:
./fastboot flash recovery recovery.img
for boot:
Code:
./fastboot flash linux boot.img
you can use the -w option to wipe data and cache
for reboot :
Code:
./fastboot reboot
wolfx said:
you can access fastboot by pressing POWER x 3 ( attention : 3 times only not 4) then VOL UP when the folio start. I use it everyday to flash recovery.img or boot.img with no problems.
Usage :
place the recovery.img or boot.img in the same directory as fastboot then from a shell navigate to your fastboot directory and us the following command :
for recovery:
Code:
./fastboot flash recovery recovery.img
for boot:
Code:
./fastboot flash linux boot.img
you can use the -w option to wipe data and cache
for reboot :
Code:
./fastboot reboot
Click to expand...
Click to collapse
So if we flash recovery.img thru fastboot we should be able to boot in to clockwork recovery via rom manager?
wolfx said:
Usage :
place the recovery.img or boot.img in the same directory as fastboot then from a shell navigate to your fastboot directory and us the following command :
Click to expand...
Click to collapse
Thanks for all the responses but i go step by step (hopefully "unbricking" my folio).
I was able to get to the display of the line "Starting Fastboot USB download protocol, please execute 'fastboot' command" (by pressing 3times the power button).
I connected the folio with USB to my PC (Win7) but the needed driver could not be found in the PC.
So i have a couple questions.
-Is the PC-driver part of the SDK? or how can i get the driver?
-I guess that with the PC i can copy via USB the recovery image to the fastboot directory. Is this correct? How else can i get the recovery image to the fastboot directory?
-Is the recovery image the "Folio stock image for full restore to stock rom" Dexters thread
Hope i can get some more help with restoring my system.
nickwarn said:
So if we flash recovery.img thru fastboot we should be able to boot in to clockwork recovery via rom manager?
Click to expand...
Click to collapse
Rom manager don't work with this recovery for now, official support must be added by Koush in rom manager before. I will commit the source to him when recovery is finalized.
Butchi said:
Thanks for all the responses but i go step by step (hopefully "unbricking" my folio).
I was able to get to the display of the line "Starting Fastboot USB download protocol, please execute 'fastboot' command" (by pressing 3times the power button).
I connected the folio with USB to my PC (Win7) but the needed driver could not be found in the PC.
So i have a couple questions.
-Is the PC-driver part of the SDK? or how can i get the driver?
-I guess that with the PC i can copy via USB the recovery image to the fastboot directory. Is this correct? How else can i get the recovery image to the fastboot directory?
-Is the recovery image the "Folio stock image for full restore to stock rom" Dexters thread
Hope i can get some more help with restoring my system.
Click to expand...
Click to collapse
For driver :
- Download the android SDK here
- Edit "<your-android-sdk-folder>/usb_driver/android_winusb.inf"
- Add the following after [Google.NTx86] (or [Google.NTamd64] if 64 bits windows)
Code:
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
- start your folio in fastboot mode and plug in. Win will not find the right driver to use
- Force driver installation : click update driver -> have disk -> point to "<your-android-sdk-folder>/usb_driver/android_winusb.inf"
- Choose bootloader driver
After this you normally can use fastboot place in : <your-android-sdk-folder>/tools
For the recovery.img you can use the one include in the update.zip or one from FolioMod.
Hope it can help you
I am still not there...
Again thanks for all the help and support
OK I installed the SDK (and the JRE as it was also a requirement). But i did not find the USB driver so far (which is strange because i had connected the folio with the PC earlier).
While doing all that i discovered that somehow the ClockworkMod Recovery was installed correct. I could get the expanded ClockworkMod menu. (Using the power button and simulteaneous the Vol+ button within the 3 sec. And whatever i selected update or recovery, i got to the ClockworkMod menu.) This looked promissing.
So i put an update.zip on the sdcard (dextermod 1.3b).
In the menu i selected 'apply sdcard:update.zip'. After this i got the screen (white text) Confirm install? THIS CAN NOT BE UNDONE and (yellow text) 7 lines with '-No', one line with '-Yes - install /sdcard/update.zip' and 3 more lines with '-No'.
After selecting the 'Yes' line i got the following messages:
--Install from sdcard...
Finding update package...
Opening update package...
Installing update...
Installation aborted
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Strange enough, even after the update was aborted, the system started again after i selected to reboot in the ClockworkMod menu. Wow. Who knows what happened may explain this. But nice for me the system works again (till the next time).
Looking very nice. Just flashed it and made a backup
HI,
2 of my PC (Windows 7 64) does not see my transformer in USB Debug mode. I installed the 64 bit Dell driver on each PC. Could someone provide me with some options to try.
Is there a way to completely reset the Transformer to stock without USB or being able to load a kernel from SD card?
2 ways to reset -
If you can boot then go into settings --> backup and reset --> factory data reset.
If you can't, hold volume-down then press power, and wait till wipe data appears, use vol keys to select it.
and search for the Universal Naked Drivers, those may help.
Thanks. That seemed to wipe the user settings and data, but not the recovery app "CWM-based Recovery v5.5.04 roach-tf101-r2". As a result the following happened after I reset.
System reboots
System comes up clean and runs setup (wifi, gmail account, etc).
System downloads firmware update.
System reboots to install update
Android appears and runs for a few seconds
Mesages appear: CWM-based Recovery v5.5.04 roach-tf101-r2
Finding update package, opening update package, Verifying update package
E: failed to verify whole-file signature
E:signature verification failed
Installation aborted
At this point the TF still will not install zip from sd card since as you told me before I need a different recover and is not found by the PC with a naked driver.
However, the unit is functional.
Any other options to root and get a new recovery installed and finally a new ROM.
Note: the PC does see the TF if I am in the recovery. However, as soon as boot the TF and enable USB debug the TF us not seen.
To go back to totally stock including stock recovery, download and flash an official ROM from Asus website.
baseballfanz said:
To go back to totally stock including stock recovery, download and flash an official ROM from Asus website.
Click to expand...
Click to collapse
I have no problem doing that, but how do I do it if I cannot connect the TF to PC via USB or load a zip file via recovery? Both of these do not work!
Did you update cwm via ROM manager? That's the issue there, you can run Roach2010's fix to fix that.
If terminal emulator app works you can flash a downloaded and extracted
(through es file explorer) recoveryblob with
Code:
su
dd if=/sdcard/recoveryblob of=dev/block/mmcblk0p4
reboot
Then you have working recovery and can either flash ROM or Stock.
Thanks for all the replies.
I finally got it working. It took me forever to understand that having a recovery that could only read from the internal memory was not a big deal. I created a folder on the internal sd and dropped in the zip for the external version of CWM . I rebooted and loaded the new restore and from then on I could load ROMs from my external uSD card. I am now happily running the latest version of Revolver.
Jerry
Hi,
I have a Pioneer XDP-100R (hi-res music player) running android 5.1. I tried to root with SuperSU. At the end it asked to reboot my device. Now it's stuck on the android boot logo.
I can access the recovery menu (next track + power). A message is displayed: "E:Can't open /dev/block/platform/msm_sdcc.1/by_name/misc (permission denied)".
If I choose Wipe Data/factory reset, I get:
-- Wiping data...
Formatting /data...
Formatting /cache...
Data wipe complete.
"E:Can't open /dev/block/platform/msm_sdcc.1/by_name/misc (permission denied)".
I get pretty much the same when I try to "wipe cache partition".
None of the two actually make a difference.
Previous track + power is supposed to get me to the fastboot menu but it's stuck on the linux logo.
I had made a backup with adb beforehands but I can't restore it. adb won't see my device unless I select the option "apply updates from adb", but in that case, the only command it accepts is adb sideload.
I have not installed a custom recovery as my device is too rare. I never managed to find a stock rom or custom rom for my device so I can't even flash another one.
Has anyone any clue?
Thanks heaps
Hello,
please ask here:
http://forum.xda-developers.com/android/help
I have almost finished setting up new Redmi 6.
After rooting, getting TWRP on the phone I have reinstated all apps trough TitaniumBackup. I have reinstated too many apps from TB and at some point I have removed 1 or 2 apps too many that I thought are only from TB...
Inside TB I went into system apps and deleted apps wit: Backup copy [APK + backup]. Before I realised that apps with backup were actually original Xiaomi appswas too late, I had few warnings later and phone rebooted but couldn't boot into system.
This way I got rid of:
com.android.providers.telephony
com.android.phone
I could recreate what I have removed going into old phone and seeing which apps are backed up from system...
Can you help me to get apps back trough TWRP or FASTBOOT?
USB debugging was still on last time
My SD card is formatted as part of internal storage
TWRP File Manager can browse ROOT folder
It is newest ROM for Redmi6, [V10.3.6.0.OCGMIXM_], can someone provide copy of APKs please?
When in TWRP I mount system only, and try to [wipe dalvik] I get messages:
Failed to wipe dalvik
Updating partition details...
df /external_sd > /tmp/dfoutput.txt process ended with ERROR: 1
df /external_sd > /tmp/dfoutput.txt process ended with ERROR: 1
...done
Unable to mount storage
I almost will not loose any data, but:
if I can I'd like to move missing apps back to /app/data/ OR /system/app/ ? to recover system so it starts
if need be I will flash Xiaomi ROM and start from scratch but will loose many h of hard work on de-bloating etc [I hope that flashing original ROM will be easy since TWRP is working fine]
During TWRP - ADB sideload:
HTML:
adb install com.android.phone.apk
error: device '(null)' not found
- waiting for device -
What can I do???
-------------------------------------------------------------------------------------
Turns out I had to flash original stock
Xiaomi guide is terrible and out of date, so:
there are prerequisites required, like ADB, drivers, that is well explained on Xiaomi site, then...
download original stock for fastboot >>> unpack folder XXX sitting inside 2 archives [it's not zip] >>> download/install and run XiaoMiFlash.exe >>> SELECT button - navigate to unpacked folder XXX >>> attach mobile >>> refresh = device will appear on list >>> FLASH
Read official xiaomi instructions on flashing original ROM just in case something will get updated
Why not any other way?
In TWRP it asked me for a password at the start
I couldn't get /system/ or /data/ mounted, wiped or formatted.
I have seen folks giving advice on how to do it, but often it didn't make sense or it didn't work.
I would be risking bricking new device by other methods & I had no more than 3 pictures to loose on flashing ROM and hours spent on doing up.
Interesting is, there really wasn't even one working advice on how to mount i.e. /system in TWRP when password is missing in booted operating system [like my case, I couldn't find any info on that, all at some point were going to advice to do something that required mounted /system or /data]
But then I just finished whole process of flashing stock ROM; I have set [1. simple password] then [PIN], went to TWRP, tried to use OS password/PIN and it didn't work, it didn't remove encryption .
----------------------------------------------------------------------------------------------------------------------------------------------
Found a solution on how to root the phone after all above.
After another Original stock ROM 10.3.6.0.OCGMIXM flash with XiaoMiFlash.exe, phone will automatically restart and start OS
But... I didn't let it to boot
Once it restarted I have pressed Vol- [button down] and waited for fastboot to load [no need to hold power button]
Installed TWRP 3.0.0.0
Restarted
Hold Vol+ [button up]
TWRP loads
CANCEL if asks for password
----------------------
INSTALL boot.img [when you flash stock ROM it is inside folder, just copy it across]
in MOUNT tick /vendor & /system
use back button to exit MOUNT
INSTALL Magisk 19.3.zip
clean dalvik cache and swipe
I have once again restarted to RECOVERY/TWRP
------------------------
When OS booted I couldn't run/start Magisk APK/aplication. Screen blinked and that's all. Root not working.
download Magisk Manager [7.3.4 in my case] from web & install
I could start application this time & it asked me to install something extra - I have chosen to install it right away
Magisk reboots phone
Now phone was finally rooted
---------------------
I used external USB attached to phone with files so I didn't need to copy files to phone.
This is much more convenient as after restarting to TWRP first time there is nothing on the phone and you would have to sideload.
---------------------------
Below is LibreOffice doc with ADB commands to uninstall bloatware. In the column next to uninstalling commands, are commands to instal same app back [I do not know will this always work since I tried only on few] [some missing - you can create it yourself]
Potentially further down the list there are more necessary apps. Uninstalling them did not cause problems in my set up, but sometimes they might be needed for less important stuff...
https://www.dropbox.com/s/xpfeh4wx1nv5dlf/Bloatware removal + SD as internal.ods?dl=0
Requirements​install ubuntu on your pc
Download This lineage image, if you want google apps download BVG if you dont want google apps download BVS Make sure to download arm64 not a64 note if you want a pre-rooted lineage OS choose lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS-vndklite.img.xz
Download This GSI make sure to download system-roar-arm64-ab-vndklite-gapps.img.xz or system-roar-arm64-ab-vndklite-vanilla.img.xz These are pre-rooted GSI'S
And Download This FILE We will need it later
==============================================================================================================================
BEFORE WE PROCEED IM NOT RESPONSIBLE FOR BRICKING YOUR DEVICE
extract everything in the same folder right click open in terminal
reboot into download mode voulme up + power
Ok now we"ll need to install heimdall on your ubuntu machine by opening the termanil and typing sudo apt install heimdall-flash
type in the terminal heimdall flash --SYSTEM sysnull.img
system will reboot, go into download mode again
now write heimdall flash --SYSTEM system-roar-arm64-ab-vndklite-gapps.img --VBMETA avbnull.img
or if you downloaded the one without GAPPS Write heimdall flash --SYSTEM system-roar-arm64-ab-vndklite-vanilla.img --VBMETA avbnull.img
Boot into stock recovery and do a factory reset
install Termux and download this TWRP image and rename it to r.img
open Termux and type su
Now Write dd if=/sdcard/Download/r.img of=/dev/block/bootdevice/by-name/recovery
if you saved the TWRP image to your internal storage type dd if=/storage/emulated/0/Download/r.img of=/dev/block/bootdevice/by-name/recovery
ok now reboot into TWRP (power + vol up)
wipe dalvik art, cache, system, data, cache
and move the LineageOS image from your pc to your INTERNAL STORAGE THERE WILL BE A FILE NAMED TWRP PUT IT THERE SD CARD WILL NOT WORK IF YOU FLASH IT FROM AN SD CARD THERE WILL BE A STORAGE PROBLEM AND YOU WONT BE ABLE TO INSTALL ANY APPS
Click select storage (click on internal storage)
Click on install image
and now just flash LineageOS and make sure to choose system image
Thanks to @Hex_101 For the rooting tutorial !!
Edit: I Stopped Using The Phone and Switched To An Iphone 14 Pro Max
works fine
Hello, I've been trying to install LineageOS on my device (SM-A207F), and I've followed every instruction so far, but I'm stuck while trying to flash heimdall sysnull.img
After I typed in heimdall flash --SYSTEM sysnull.img in the terminal, I've persistently got this error:
Session begun.
Downloading device's PIT file...
ERROR: Failed to receive end PIT file transfer verification!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
I've unlocked the bootloader and enabled USB debugging.
I'm using Ubuntu 22.04 LTS (on VirtualBox, Windows 11), also very new to custom ROM, I've only successfully installed LineageOS on an S5 (SM-G900H).
Edit: Solved
I entered the wrong Download Mode (step #2), I thought the Download Mode was the one when I'm supposed to press Volume Up on the same recovery mode to unlock the bootloader (pressing volume up & down together and connecting the cable), turns out I'm supposed to enter Download Mode from the Stock Recovery (pressing volume up & power button)
And probably because I used Ubuntu on a VM
Wurd4Wurd said:
works fine
Click to expand...
Click to collapse
Hi, may I know which version of LineageOS did you install?
I've managed to successfully flashed LineageOS ( lineage-19.1-20221122-UNOFFICIAL-arm64_bgN-secure.img.xz ) but my phone keeps rebooting while setting up.
jfr07 said:
Hi, may I know which version of LineageOS did you install?
I've managed to successfully flashed LineageOS ( lineage-19.1-20221122-UNOFFICIAL-arm64_bgN-secure.img.xz ) but my phone keeps rebooting while setting up.
Click to expand...
Click to collapse
you downloaded the wrong version. you can find it at https://sourceforge.net/projects/andyyan-gsi/files/lineage-19.x/History/ and make sure to download lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS-vndklite.img.xz use ctrl + f to find it faster. and then flash it again, and it should work perfectly fine.
also if you want root permissions make sure to install phh superuser, flashing Magisk will brick your device.
jfr07 said:
Hello, I've been trying to install LineageOS on my device (SM-A207F), and I've followed every instruction so far, but I'm stuck while trying to flash heimdall sysnull.img
After I typed in heimdall flash --SYSTEM sysnull.img in the terminal, I've persistently got this error:
Session begun.
Downloading device's PIT file...
ERROR: Failed to receive end PIT file transfer verification!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
I've unlocked the bootloader and enabled USB debugging.
I'm using Ubuntu 22.04 LTS (on VirtualBox, Windows 11), also very new to custom ROM, I've only successfully installed LineageOS on an S5 (SM-G900H).
Click to expand...
Click to collapse
Use Dualboot instead of VirtualBox, you can find tutorials on youtube but you'll need a spare USB drive
Wurd4Wurd said:
Use Dualboot instead of VirtualBox, you can find tutorials on youtube but you'll need a spare USB drive
Click to expand...
Click to collapse
Yes I've overcome this problem since my second post where my phone keeps rebooting
Wurd4Wurd said:
you downloaded the wrong version. you can find it at https://sourceforge.net/projects/andyyan-gsi/files/lineage-19.x/History/ and make sure to download lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS-vndklite.img.xz use ctrl + f to find it faster. and then flash it again, and it should work perfectly fine.
also if you want root permissions make sure to install phh superuser, flashing Magisk will brick your device.
Click to expand...
Click to collapse
Okay this version works, but I seem to encounter a problem. Everytime I try to open Storage in Settings, the Settings App crashed, and whenever I try to install an App from Play Store, it says that I don't have enough storage. Does it have something to do with this on the original thread?
Sinshro said:
and move the LineageOS image from your pc to your INTERNAL STORAGE THERE WILL BE A FILE NAMED TWRP PUT IT THERE SD CARD WILL NOT WORK IF YOU FLASH IT FROM AN SD CARD THERE WILL BE A STORAGE PROBLEM AND YOU WONT BE ABLE TO INSTALL ANY APPS
Click to expand...
Click to collapse
jfr07 said:
Okay this version works, but I seem to encounter a problem. Everytime I try to open Storage in Settings, the Settings App crashed, and whenever I try to install an App from Play Store, it says that I don't have enough storage. Does it have something to do with this on the original thread?
Click to expand...
Click to collapse
It's a common issue. Try following these steps:
1. Boot into TWRP
2. Go to Advanced
3. Click on Fix Contents and confirm
4. Reboot
Wurd4Wurd said:
It's a common issue. Try following these steps:
1. Boot into TWRP
2. Go to Advanced
3. Click on Fix Contents and confirm
4. Reboot
Click to expand...
Click to collapse
I thought I made mistakes throughout the process so I tried re-doing everything from the beginning and it finally works without storage issues. Thank you so much for your help, especially pointing out the correct OS image, such a lifesaver
Okay so I've encountered another problem and it looks like a critical one
- My phone's battery was drained, I only realized after trying to boot it up without realizing the battery's at 0 capacity
- It went through the Lineage OS boot animation and went back off
- I charged it and tried to boot it up, then the charging animation comes on
- When I long-pressed the power button, it only showed the charging animation without any other responses.
- The animation keeps going during the charging process, but even after I ejected the charger and tried to boot it up, it still only showed the battery capacity (without the charging animation) and no other responses
- So now I'm stuck with the phone in a battery showing state, pressing Volume Up + Power Button & Volume Down + Power Button does nothing
- I'm currently trying to charge it to full capacity to see if it will actually respond with something after being completely charged
Has anyone ever come across similar situation?
UPDATE: Pressing Volume Up, Volume Down, and Press Button altogether works while in the battery charging state and it booted up normally, so it doesn't look like an actual problem for now
jfr07 said:
Okay so I've encountered another problem and it looks like a critical one
- My phone's battery was drained, I only realized after trying to boot it up without realizing the battery's at 0 capacity
- It went through the Lineage OS boot animation and went back off
- I charged it and tried to boot it up, then the charging animation comes on
- When I long-pressed the power button, it only showed the charging animation without any other responses.
- The animation keeps going during the charging process, but even after I ejected the charger and tried to boot it up, it still only showed the battery capacity (without the charging animation) and no other responses
- So now I'm stuck with the phone in a battery showing state, pressing Volume Up + Power Button & Volume Down + Power Button does nothing
- I'm currently trying to charge it to full capacity to see if it will actually respond with something after being completely charged
Has anyone ever come across similar situation?
UPDATE: Pressing Volume Up, Volume Down, and Press Button altogether works while in the battery charging state and it booted up normally, so it doesn't look like an actual problem for now
Click to expand...
Click to collapse
Good to hear, I was so worried that it will also happen to my a20s.
Wurd4Wurd said:
Good to hear, I was so worried that it will also happen to my a20s.
Click to expand...
Click to collapse
There's another bug on my phone that I haven't found any solutions yet, on phone calls the phone doesn't have any audio input or output (microphone & handset/speakerphone). But WhatsApp calls work just fine. Does this also happen to your device?
I've tried fixing contents through TWRP but it didn't fix the problem
Does it work on the SM-A207M/DS? I have seen the hardware of both phones and they are identical, the only diference being a letter in the model number, which says the region in which was sold in.
jfr07 said:
There's another bug on my phone that I haven't found any solutions yet, on phone calls the phone doesn't have any audio input or output (microphone & handset/speakerphone). But WhatsApp calls work just fine. Does this also happen to your device?
I've tried fixing contents through TWRP but it didn't fix the problem
Click to expand...
Click to collapse
I haven't found a solution to this.
try disabling Disable audio effects, and enable Use alternate way to detect headsets, Force headset switch, and Force-disable A2Dpp offload and then restart your phone.
aerglass said:
Does it work on the SM-A207M/DS? I have seen the hardware of both phones and they are identical, the only diference being a letter in the model number, which says the region in which was sold in.
Click to expand...
Click to collapse
I don't know much about this phone. Add me on discord maybe I can help you. lib#0520
Wurd4Wurd said:
I haven't found a solution to this.
try disabling Disable audio effects, and enable Use alternate way to detect headsets, Force headset switch, and Force-disable A2Dpp offload and then restart your phone.
I don't know much about this phone. Add me on discord maybe I can help you. lib#0520
Click to expand...
Click to collapse
sorry if itype bad (i am typing one handed because my right hand broke)
i installed it on to a broken (that has no wifi or bluetooth, idk why) samsung galaxy a20s from latin america (SM-A207M/DS) which seemed that it was going to no work but it worked perfectly, i have some problems with lineage though, i could fix the phone but i do not care so whatever. I have another samsung galaxy a20s that works fine.
Using this method i flash twrp and repack stock system.img by deleting install-recovery.sh and recovery-from-boot.p
Now i'm have stock rom with twrp
Maybe have methods install system root to stock rom without modify boot.img?
I'm add phh-su to bin and su to xbin and add su.rc to init but phh su can't work with stock rom
minakriss said:
Using this method i flash twrp and repack stock system.img by deleting install-recovery.sh and recovery-from-boot.p
Now i'm have stock rom with twrp
Maybe have methods install system root to stock rom without modify boot.img?
I'm add phh-su to bin and su to xbin and add su.rc to init but phh su can't work with stock rom
Click to expand...
Click to collapse
Did you flash the stock system.img via TWRP? I can't seem to do the same. If you have the zip that you flashed, can you upload it here? It means a lot to me. Thanks
I can send u patched system.img for flash via TWRP if u can send me version of previous installed stock Samsung rom
minakriss said:
I can send u patched system.img for flash via TWRP if u can send me version of previous installed stock Samsung rom
Click to expand...
Click to collapse
A207FXXU2BTH2 Binary 2, Android 10 and region is the Philippines SMA
i need the non-superuser lineage 19.0 and it does not exist on https://sourceforge.net/projects/andyyan-gsi/files/lineage-19.x/History/