Related
Hello sir,
I rooted my phone with z4root, tried with adb made easy, but didnt work. even super 1-click root didnt seem as rooted.
I rooted my phone after downgrading to (android2.2) V10B_00.kdz, even installed super user. Then i copy the cyanogen_thunderg-ota-eng.mik.zip to SD root. then i copy recovery-RA-GNM-thunderg-1.1.0.img
Then i rebooted into recovery mode using adb made easy even with recovery key [home+power+vol down]. but it just reset to factory settings only.. i even tried with flash_image & recovery.img.. same response.. i even tried with Megatron-v1.
How can i flash my rom to a custom rom..
I use LG Optimus P500
Also, can i root my phone from android 2.2.2?
Please HELP! :-(
Thanks
It seems recovery was not flashed properly. Try manually flashing recovery rather than using adb made easy.
Try this to install recovery.
2.2.2 can be rooted using app. Check out the Dev forum for info.
Sent from my LG-P500 using XDA App
1) Make sure that you have collected all needed information about recovery installation
2) Check if you really rooted your phone ("superuser" application should be installed and if you try write command "su" in adb shell or terminal emulator window with question about allowing sudo access should appear)
3) Than follow all steps in manual for your selected recovery.
mihir287 said:
It seems recovery was not flashed properly. Try manually flashing recovery rather than using adb made easy.
Click to expand...
Click to collapse
i tried with SuperOneClickv1.9.1-ShortFuse.Drivers.. but the result is...
Root mode
Code:
SuperOneClick v1.9.1.0
Checking drivers...
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Getting OS Version...
2.2.2
OK
2.2.2
Pushing psneuter...
1311 KB/s (585731 bytes in 0.436s)
OK
chmod psneuter...
OK
Running psneuter...
OK
***IF IT KEEPS LOOPING, TRY DISABLING USB DEBUGGING NOW***
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
error: more than one device
FAILED
Shell root mode
Code:
SuperOneClick v1.9.1.0
Checking drivers...
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Getting OS Version...
2.2.2
OK
2.2.2
Pushing psneuter...
1311 KB/s (585731 bytes in 0.436s)
OK
chmod psneuter...
OK
Running psneuter...
and seems like hanged..
i tried with other versions of this too.. not rooted!
i tried this in Android 2.2.2, coz rforums told me it works. what should i do now?
ungaze said:
Try this to install recovery.
Click to expand...
Click to collapse
while giving that, it says
Code:
su
sh /sdcard/rf.sh
permission denied. coz am not rooted.. so can u pls tell me how to root in 2.2.2?
rforums said:
2.2.2 can be rooted using app. Check out the Dev forum for info.
Sent from my LG-P500 using XDA App
Click to expand...
Click to collapse
please can u link me that sir.... i searched but showg lots of results.. cant find the exact one :-/
The_ERROR said:
1) Make sure that you have collected all needed information about recovery installation
2) Check if you really rooted your phone ("superuser" application should be installed and if you try write command "su" in adb shell or terminal emulator window with question about allowing sudo access should appear)
3) Than follow all steps in manual for your selected recovery.
Click to expand...
Click to collapse
i have all the recovery files copied to SD root. i installed z4root & rooted before, then i even installed superuser.apk, & copied the su-v1 su-v2 su-v3 to SD root.. and while rebooting with 3 key (recovery key) mode, it just resets to factory default settings :-/ why like this? whats wrong?
Have you tried gingerbreak? it's for gingerbread but it worked on my froyo.
You can root 2.2.2 using GingerBreak.
For CustomRecovery: install ROM Manager and click "Flash Clockworkmod recovery". In a few secs you will have the clockworkmod recovery installed.
22VIN said:
You can root 2.2.2 using GingerBreak.
For CustomRecovery: install ROM Manager and click "Flash Clockworkmod recovery". In a few secs you will have the clockworkmod recovery installed.
Click to expand...
Click to collapse
im doing it now in 2.2.2, still process going on.. but how long it will take to finish? its hanged at
Code:
chmod GingerBreak
OK
Running GingerBreak
n0f3a6 said:
im doing it now in 2.2.2, still process going on.. but how long it will take to finish? its hanged at
Code:
chmod GingerBreak
OK
Running GingerBreak
Click to expand...
Click to collapse
Use chainfire's apk version. It's easier.
Did it work?
tahahawa said:
Use chainfire's apk version. It's easier.
Click to expand...
Click to collapse
thanks buddy,.. rooting on 2.2.2 worked with gingerbreak.. now trying to flash rom
22VIN said:
Did it work?
Click to expand...
Click to collapse
i highly recommend gingerbreak it works i think it works in all devices.. good job..
:-( now only LG screen is available :-( no more recovery mode.. after power off, when i turned on, it showing LG logo for 2-3 secs, and restarts :-( i think my ROM is empty how can i recover my LG? :-( please help!!!! i was trying with ROM manager, then i saw superuser new version froyo. so after installing, it restarted.. thats how it happened!!
n0f3a6 said:
:-( now only LG screen is available :-( no more recovery mode.. after power off, when i turned on, it showing LG logo for 2-3 secs, and restarts :-( i think my ROM is empty how can i recover my LG? :-( please help!!!! i was trying with ROM manager, then i saw superuser new version froyo. so after installing, it restarted.. thats how it happened!!
Click to expand...
Click to collapse
Is there a recovery program from LG? Fastboot/Bootloader/Download mode?
tahahawa said:
Is there a recovery program from LG? Fastboot/Bootloader/Download mode?
Click to expand...
Click to collapse
is it necessary to install Android SDK to recover my phone?
n0f3a6 said:
is it necessary to install Android SDK to recover my phone?
Click to expand...
Click to collapse
Just the drivers I think.
It's finally here! TWRP recovery for the Fire TV 1. Most likely, I will not be updating this thread with new releases, as the prerooted ROMs will always contain the latest version. This thread is just here so people on Fire OS 3 can install TWRP and people on rooted but locked bootloader Fire TV 1's can get recovery initially installed.
As usual, this WILL void your warranty and I am NOT responsible for anything you do with this. Installing it properly won't brick your Fire TV, but doing stupid things with it might.
Installing this requires root. If you are not rooted, figure that out first.
Installation for Unlocked Bootloader
Make sure you are on a FULLY unlocked bootloader. From within FireOS and after running su run this:
Code:
cat /proc/cmdline
And MAKE SURE unlocked_kernel=true is present! If it is not, you are NOT fully unlocked and you must Fully Unlock first!
Make sure you are on at least 51.1.4.0 ROM and the latest CWM installed.
Copy the bueller-twrp_3.0.0-6.img file to /sdcard
From within adb shell, use su to become root, and run this command (are you sure you did step 1?)
Code:
dd if=/data/media/0/bueller-twrp_3.0.0-6.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
From outside adb shell, reboot to recovery
Code:
adb reboot recovery
TWRP should load, you can install a FireOS5 prerooted ROM now.
Installation for Locked Bootloader
This requires that you are on at least version 5.0.5 and rooted.
Copy the bueller_recovery_vX.zip file to /sdcard
From within adb shell, use su to become root, and run this command (replace vX with the actual version you downloaded)
Code:
sh /data/media/0/bueller_recovery_vX.zip
Reboot
Notes
This includes bootmenu. For everyone that loved the old bootmenu with Comic Sans, I'm sorry to disappoint you, but the Comic Sans is gone. When the FireTV boots, it will present you with the bootmenu where you can leave it alone and it will boot normally or you can select recovery and it will boot in to recovery. You do need a USB keyboard to interact with the bootmenu. To force it to boot in to Recovery, you can create a file /cache/bootmenu_recovery.
DHCP for Ethernet is enabled, and if there is enough demand I may add in wifi at some point. The IP address should show up in the top left corner.
USB storage and USB keyboard/mice should all work. Hotplugging works, so you should be able to plug and unplug devices as needed.
You can use a USB keyboard, mouse, or the mouse emulator to interact with it. To use a keyboard, you can use the arrow keys to move the cursor and the enter key to select buttons. Sliders don't require sliding, so you can just hit enter/click on them. To use the mouse emulator, use adb shell and then run the program mouse and follow the instructions.
ROMs
Recovery must be included in all ROMs. If you want to develop a ROM, please contact me about including recovery in it.
Installing zips
You can push zips to /sdcard, put it on a USB storage, or use adb sideload. Do note you need adb version 1.0.32 to use adb sideload.
Stuck in a loop?
If you cannot boot normally and keep going back to the bootmenu, wipe Cache from Wipe -> Advanced Wipe.
Source Code
You can find the source code here:
https://github.com/androidrbox/firetv-2ndinit
https://github.com/androidrbox/android_bootable_recovery
WARNINGS
It is extremely important you never reboot after a failure. This will most likely lead to a brick. If recovery is hung, you can use adb shell to run
Code:
killall recovery
to restart it
It is also extremely important to never reboot after wiping /system.
Finally, thanks to everyone who has donated to me.
Changelog and Downloads:
July 7, 2016 - v2 (md5sum: 8f65187cb0cbc190a7d64f512ae3ede2)
This is the updated version with TWRP 3.0.0-7.
July 4, 2016 - TWRP Image 3.0.0-7 (md5sum: cda1a1c1cdd3e25a1caa86f5a5de1eee)
May 20, 2016 - v1 (md5sum: 9208d81fd07cff9952de5be33c62f730)
This is for use by people who have FireOS5 and are rooted.
This includes 2ndinit version a7a48c and TWRP version 3.0.0-6.
May 20, 2016 - TWRP Image (md5sum: 5dc83370046e5b50755ddb55fe8424ad)
This is for use by people who have FireOS3 and CWM and is TWRP version 3.0.0-6.
thanks so much rbox! just tested it and i can confirm that my firetv 1 with fireos3 and fully unlocked bootloader just installed twrp successfully - woot!
i still have the old boot menu though with comic sans..?
mrchrister said:
thanks so much rbox! just tested it and i can confirm that my firetv 1 with fireos3 and fully unlocked bootloader just installed twrp successfully - woot!
i still have the old boot menu though with comic sans..?
Click to expand...
Click to collapse
For unlocked bootloaders, this step JUST installs recovery. You need to install the prerooted rom to get the new bootmenu.
got you, downloading now
Sent from my iPhone using Tapatalk
I successfully dd'ed the recovery image onto my ftv with unlocked bootloader but attempting to boot it causes the TWRP logo to show for a few seconds, then the screen goes black and the cycle repeats. Any idea how to fix this?
ssgelm said:
I successfully dd'ed the recovery image onto my ftv with unlocked bootloader but attempting to boot it causes the TWRP logo to show for a few seconds, then the screen goes black and the cycle repeats. Any idea how to fix this?
Click to expand...
Click to collapse
If you unplug the power and replug it, it should boot normally, then you can see if the recovery log got saved, /cache/recovery/last_log and pastebin it.
The log at /cache/recovery/last_log is from CWM from the last time I flashed a new rom.
ssgelm said:
The log at /cache/recovery/last_log is from CWM from the last time I flashed a new rom.
Click to expand...
Click to collapse
Can't really explain why it would be doing that. Can you connect via adb?
I am not on ethernet right now. When I get a chance I'll do that and see if I can connect. Thanks so much for your work on this!
ssgelm said:
I successfully dd'ed the recovery image onto my ftv with unlocked bootloader but attempting to boot it causes the TWRP logo to show for a few seconds, then the screen goes black and the cycle repeats. Any idea how to fix this?
Click to expand...
Click to collapse
I'm also getting this, what can I do?
here's last_log
gehx said:
I'm also getting this, what can I do?
Click to expand...
Click to collapse
Can you connect via adb?
rbox said:
Can you connect via adb?
Click to expand...
Click to collapse
yep, that's how I pulled last_log
gehx said:
yep, that's how I pulled last_log
Click to expand...
Click to collapse
I meant while recovery is running.
rbox said:
I meant while recovery is running.
Click to expand...
Click to collapse
recovery never fully loads, i just get the twrp splash screen over and over and over again...it's in a loop
gehx said:
recovery never fully loads, i just get the twrp splash screen over and over and over again...it's in a loop
Click to expand...
Click to collapse
Yes. But have you tried using adb...
rbox said:
Yes. But have you tried using adb...
Click to expand...
Click to collapse
I'm not sure what IP to use?
gehx said:
I'm not sure what IP to use?
Click to expand...
Click to collapse
The same one the firetv would be using when it's booted... via ethernet of course.
rbox said:
The same one the firetv would be using when it's booted... via ethernet of course.
Click to expand...
Click to collapse
the connection times out:
adb connect 192.168.1.6
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
unable to connect to 192.168.1.6:5555: Operation timed out
Click to expand...
Click to collapse
gehx said:
the connection times out:
Click to expand...
Click to collapse
Can you pull the log again? It should say the ip in it actually.
rbox said:
Can you pull the log again? It should say the ip in it actually.
Click to expand...
Click to collapse
new last_log
it shows 192.168.1.8; I'm unable to adb connect to that IP too
Hello,
My apologies if I've posted this thread in the wrong section.
I bricked my One Plus X trying to install the Nougat Nightlies update. I accidentally wiped off the entire data include internal storage so now I cannot boot or restore to the old image. The OS is gone and the phone gets stuck at the boot screen.
The plan was to install the One Plus recovery and then install the OOS3.1.4. I managed to install the One Plus Marshmallow recovery using adb -- the issue is when I try to push the Oxygen OS 3.1.4 image to the internal storage it gives me this error message
Code:
C:\adb>adb push OnePlusXOxygen_14_OTA_019_all_201611071506_03f73e21449d4d31.zip /system/
failed to copy 'OnePlusXOxygen_14_OTA_019_all_201611071506_03f73e21449d4d31.zip'
to '/system//OnePlusXOxygen_14_OTA_019_all_201611071506_03f73e21449d4d31.zip':
Read-only file system
I cannot run adb as root it effectively complaints about the phone being in production mode so I'm honestly out of ideas on how to fix this.
It was pretty stupid of me to attempt to flash my phone w/o prior knowledge of rooting. I just want my phone to go back to the older version.
Any help is greatly appreciated.
Thank you.
VayneSpotting said:
Hello,
My apologies if I've posted this thread in the wrong section.
I bricked my One Plus X trying to install the Nougat Nightlies update. I accidentally wiped off the entire data include internal storage so now I cannot boot or restore to the old image. The OS is gone and the phone gets stuck at the boot screen.
The plan was to install the One Plus recovery and then install the OOS3.1.4. I managed to install the One Plus Marshmallow recovery using adb -- the issue is when I try to push the Oxygen OS 3.1.4 image to the internal storage it gives me this error message
Code:
C:\adb>adb push OnePlusXOxygen_14_OTA_019_all_201611071506_03f73e21449d4d31.zip /system/
failed to copy 'OnePlusXOxygen_14_OTA_019_all_201611071506_03f73e21449d4d31.zip'
to '/system//OnePlusXOxygen_14_OTA_019_all_201611071506_03f73e21449d4d31.zip':
Read-only file system
I cannot run adb as root it effectively complaints about the phone being in production mode so I'm honestly out of ideas on how to fix this.
It was pretty stupid of me to attempt to flash my phone w/o prior knowledge of rooting. I just want my phone to go back to the older version.
Any help is greatly appreciated.
Thank you.
Click to expand...
Click to collapse
Anyhow ,do you have access to custom recovery ?
Sent from my MotoG3-TE using Tapatalk
[email protected] said:
Anyhow ,do you have access to custom recovery ?
Sent from my MotoG3-TE using Tapatalk
Click to expand...
Click to collapse
Yes I do have the CM Nightly recover but it doesn't boot due to the <dtb not found> error message.
VayneSpotting said:
Yes I do have the CM Nightly recover but it doesn't boot due to the <dtb not found> error message.
Click to expand...
Click to collapse
Install the latest TWRP using Adb then ? https://dl.twrp.me/onyx/twrp-3.0.3-0-onyx.img.html
Whats the error while you try to install the recovery ?
Open Adb:
Type "adb reboot bootloader"
fastboot flash recovery twrp.img
[email protected] said:
Install the latest TWRP using Adb then
Whats the error while you try to install the recovery ?
Open Adb:
Type "adb reboot bootloader"
fastboot flash recovery twrp.img
Click to expand...
Click to collapse
Holy moly. The latest twrp recovery worked perfectly. I installed the OS 3.1.4 and it's working perfectly fine.
Not a big deal but I was just wondering if there's a way to switch back to official One Plus recovery rom without messing with the OS?
Many thanks dude!
VayneSpotting said:
Holy moly. The latest twrp recovery worked perfectly. I installed the OS 3.1.4 and it's working perfectly fine.
Not a big deal but I was just wondering if there's a way to switch back to official One Plus recovery rom without messing with the OS?
Many thanks dude!
Click to expand...
Click to collapse
Yeah there is ,let me figure out and do some searching
OrangeFox Recovery Project
Code:
Your warranty is now void. * * We're 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 recovery * 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.
OrangeFox is FREE SOFTWARE
Supports MIUI and Custom Roms
Credits
* OrangeFox Recovery Project Team
* @LUNARIO, who did ALL the work, but sadly opened a thread violating the rules and the link to Recovery was deleted and the thread moved. Original here.
FEATURES:
* Touch Screen every single time
* Decryption works
* Fixed Error 7 while clean or dirty flashing (starting from version 6)
* Migrate backup installation (starting from version 6)
* OTG support
* ROM Flashing works 100%
* F2FS Support
* Fastboot commands supported
NOT WORKING FOR NOW:
* Fastbootd
* ADB Sideload
* Backing up and restoring Image Flash (system-vendor-product)
DOWNLOAD
Version 6 - Google: https://drive.google.com/file/d/1eHM9ST9ni-55bbT3z-TGSZQsgE3KYr9s/view
OLD VERSION DOWNLOAD
Version 4 - Google: https://drive.google.com/file/d/1Qq6hqaEOstxajOC7Y6AGeRYajhMWjttL/view
Version 0 - Sourceforge: https://sourceforge.net/projects/or...x-R11.0_0_Alpha-Unofficial-surya.img/download
INSTALLATION
1. Download the OrangeFoxRecovery IMG file to your PC.
2. Restart your POCO X3 in Fastboot mode (Power+Vol Down)
3. Use ADB and type in the following command:
Code:
fastboot flash recovery "OrangeFox-R11.0_6_Alpha-Unofficial-surya.img"
4. After it is installed successfully, type in this command:
Code:
fastboot boot "OrangeFox-R11.0_6_Alpha-Unofficial-surya.img"
5. The device will automatically reboot into OrangeFox Recovery after installation (allow this to happen)
6. Enjoy!
Version Information
Status: Alpha
Alpha Release Date: 2020-10-14
Does it support dd commands to backup/flash persist.img?
I tried but after I flashed xiaomi eu and went back to recovery, the touchscreen would't work
hope this gets updated i like this recovery
olujnap316 said:
hope this gets updated i like this recovery
Click to expand...
Click to collapse
here you can download updated version, I have this flashed for around one week... so far so good, but still adb sideload not working... dunno what other bugs are there... I am flashing with this NitrogenOS.... zero problems for me so far...
jeryll said:
here you can download updated version, I have this flashed for around one week... so far so good, but still adb sideload not working... dunno what other bugs are there... I am flashing with this NitrogenOS.... zero problems for me so far...
Click to expand...
Click to collapse
yes i saw that on telegram. but why is it not updated on this thread.
olujnap316 said:
yes i saw that on telegram. but why is it not updated on this thread.
Click to expand...
Click to collapse
oh, you were talking about the thread itself, sorry... but the recovery itself will work the same regardless number of posts here on xda or telegram... I personally don't care where are new versions announced...
Not affiliated
olujnap316 said:
yes i saw that on telegram. but why is it not updated on this thread.
Click to expand...
Click to collapse
Because sadly I am not the developer and I cannot post Telegram links here.
I can update manually, as long as any of you guys DM me the link to the Telegram group, so I can join.
@jeryll @olujnap316
Can anyone of you guys provide the Telegram link for me to update the thread more often?
Best regards,
billabongstaff said:
Because sadly I am not the developer and I cannot post Telegram links here.
I can update manually, as long as any of you guys DM me the link to the Telegram group, so I can join.
@[email protected]
Can anyone of you guys provide the Telegram link for me to update the thread more often?
Best regards,
Click to expand...
Click to collapse
@POCox3OfficialUpdates just search that on telegram, they posted the latest orangefox there
Thank you
olujnap316 said:
@POCox3OfficialUpdates just search that on telegram, they posted the latest orangefox there
Click to expand...
Click to collapse
Thank you, man.
I appreciate it.
I'll try to keep the thread updated.
Best regards,
Are there any written instructions anywhere on how to run the adb tools and commands precisely? Total noob here
nikolaos8 said:
Are there any written instructions anywhere on how to run the adb tools and commands precisely? Total noob here
Click to expand...
Click to collapse
of course there are, you can use Google search with the exact query you posted here and you can then choose where to start learning or click here...
nikolaos8 said:
Are there any written instructions anywhere on how to run the adb tools and commands precisely? Total noob here
Click to expand...
Click to collapse
Very good for Beginners. ▼
For ADB
https://android.tutorials.how/adb-commands/#adb_devices_command
For FASTBOOT
https://android.tutorials.how/fastboot-commands/
Update.
New build is up.
Version 6.
Fixes error 7 while clean or dirty flashing.
Backup migration now works.
Cheers.
Thanks guys. Made small instructions video for the absolute noobs (me included).
Tools used: https://developer.android.com/studio/releases/platform-tools
Instructions on adb commands and flashing:
1. Bootloader Unlocked
2. Download the latest Orangefox boot.img from first post and put it into a dedicated folder in your computer.
3. Go to the folder where you have put the Orangefox-file. Now open a command window inside that folder. To do that hold together "Shift + Right click" on any empty white space inside the folder and then select "Open PowerShell Window Here" or "Open Command Window Here" (depends on your pc).
4. Enter fastboot mode by holding together "Volume Down + Power" and connect your device to your computer
5. Enter the terminal command in command line: >>fastboot flash recovery OrangeFox-R11.0_6_Alpha-Unofficial-surya.img
(Needs to be exactly as the name of the file, in case developer uploads new version with new name)<<. Attention: Do not restart your device otherwise Xiaomi's original recovery might overwrite Orangefox!
6. After, device will reboot into Oangefox recovery.
Video Tutorial: https://youtu.be/E7fl_02Kgc8
I had also downloaded the latest Magisk zip (not Manager) from here: https://github.com/topjohnwu/Magisk/releases and placed it into the device before flashing Orangefox, so that i flash Magisk directly from recovery (as we left it above), in order to ensure it will not lose Orangefox installation after reboot.
In case it does not automatically reboot, hold +VOL + Power Button in order to reboot into the new orangefox recovery and install magisk zip from there ( do not forget to have it downloaded somewhere on your device before initiating the procedure)
Thanks everyone, especially OP for his contributions!
Factory reset /wipe prevents userdata to be decrypted? For twrp after you do a factory reset you have to format userdata even without password/pin inside the OS.
Can i backup persist partition with this recovery?
Hi!
I'm getting the error "Failed to map file" while I try to flash Magisk in this recovery.
Any help?
Hope this recovery will be official soon ! I don't know why there is no stable built yet of twp or yours ! I'm waiting for it to flash !
Jess182 said:
Can i backup persist partition with this recovery?
Click to expand...
Click to collapse
Yes you can using dd.
TWRP FOR THE A52 5G! (With issues)
Help needed!
Are you someone that has ported TWRP before without any issues?
Or are you someone that knows how to fix any problem that has been listed in the 'Additional Notes' section?
PM me. We can work together to fix the issue(s)
Note
Code:
* Your warranty is now void.
*
* 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 doing this to your device
* 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.
Additional Notes
Code:
THIS RECOVERY IS NOT FULLY TESTED!
There are atleast these issues:
1. MTP Does NOT work. (Not with computer or with OTG)
2. NO access to your SD cards
3. Incorrect resolution (TWRP is 1080x1920, phone is 1080x2400)
4. Temperature sensor doesn't work.
THERE MIGHT BE MORE ISSUES I DO NOT KNOW OF! FLASH AT YOUR OWN RISK.
How to install?
First of all you need an unlocked BL. This is extremely easy to do and there are a lot of guide online.
Download recovery.tar (TWRP) from this post.
Select the AP slot in Odin
Disable auto reboot in Odin
Flash
Credits
TeamWin Recovery Project
Source code:
Minimal TWRP AOSP: https://github.com/minimal-manifest-twrp/platform_manifest_twrp_aosp
Device Tree for the a52 5g: Can't upload because of 25mb+ kernel file. Will make a custom kernel soon
Thank you so much for your work on TWRP. Waited for it a year
GiulianoB said:
Thank you so much for your work on TWRP. Waited for it a year
Click to expand...
Click to collapse
No problem.
Hi,
Firstly, thanks for doing this!
Secondly, I've been trying to flash a zip (BluetoothLibraryPatcher) but I cannot find a way to get TWRP to read a zip file. Things I've tried:
From the device itself: The data partition is encrypted. twrp decrypt (in the TWRP terminal) says "No crypto support was compiled into this build".
From ADB Sideload: It gets stuck on "Starting ADB sideload feature..." for 5 minutes, then fails.
From MTP/USB OTG: As you say in your post, neither MTP from PC nor from a USB flash drive works.
Would you have any idea of how I can get TWRP to read a zip file to install?
Thanks!
ByteSizedBit said:
Hi,
Firstly, thanks for doing this!
Secondly, I've been trying to flash a zip (BluetoothLibraryPatcher) but I cannot find a way to get TWRP to read a zip file. Things I've tried:
From the device itself: The data partition is encrypted. twrp decrypt (in the TWRP terminal) says "No crypto support was compiled into this build".
From ADB Sideload: It gets stuck on "Starting ADB sideload feature..." for 5 minutes, then fails.
From MTP/USB OTG: As you say in your post, neither MTP from PC nor from a USB flash drive works.
Would you have any idea of how I can get TWRP to read a zip file to install?
Thanks!
Click to expand...
Click to collapse
Hey, you can use commands by just being on the home screen of TWRP. ADB push <file location and name> /sdcard
ByteSizedBit said:
Hi,
Firstly, thanks for doing this!
Secondly, I've been trying to flash a zip (BluetoothLibraryPatcher) but I cannot find a way to get TWRP to read a zip file. Things I've tried:
From the device itself: The data partition is encrypted. twrp decrypt (in the TWRP terminal) says "No crypto support was compiled into this build".
From ADB Sideload: It gets stuck on "Starting ADB sideload feature..." for 5 minutes, then fails.
From MTP/USB OTG: As you say in your post, neither MTP from PC nor from a USB flash drive works.
Would you have any idea of how I can get TWRP to read a zip file to install?
Thanks!
Click to expand...
Click to collapse
Btw, afaik the encryption problem isn't something I can remove.
This is fantastic to see! Nice work.
Have you tried any custom ROMs with this? Do any of the current custom ROMs (like Lineage OS) support A52 5G, or are we still a far way away from that?
biscuitpants said:
This is fantastic to see! Nice work.
Have you tried any custom ROMs with this? Do any of the current custom ROMs (like Lineage OS) support A52 5G, or are we still a far way away from that?
Click to expand...
Click to collapse
Hey. I've not started a custom ROM yet. I've been busy with school mostly. I will probably start developing Lineage OS as the first custom rom.
Things405 said:
Hey. I've not started a custom ROM yet. I've been busy with school mostly. I will probably start developing Lineage OS as the first custom rom.
Click to expand...
Click to collapse
Good luck and thanks again for your effort
Hey! I found this on GitHub and I was wondering if it's you. Your post is still saying "Will upload in a minute". Thanks!
MeowNyaaa said:
Hey! I found this on GitHub and I was wondering if it's you. Your post is still saying "Will upload in a minute". Thanks!
Click to expand...
Click to collapse
Yep thats me. I can't upload a kernel file on github as its 25mb+ So the device tree won't be complete without it. I'll change the post.
Things405 said:
Yep thats me. I can't upload a kernel file on github as its 25mb+ So the device tree won't be complete without it. I'll change the post.
Click to expand...
Click to collapse
I recommend using Git LFS for that, more info about it here: https://git-lfs.github.com/
I created a device tree myself long time ago as well, was just missing the kernel
I may sell my U1 for the Dual Sim model so I can root. I need parts of this lol
Any progress?
I just can't wait for LineageOS
@Things405 I have GitHub pro if you want someone to host the device tree on there... I'm on https://github.com/SImPilotAdamT/
Also by A52 5G do you mean the A526B?
Also for some reason I can't unlock the bootloader in my device... I have the A526B international model. https://forum.xda-developers.com/t/unable-to-unlock-the-bootloader-a52-5g-sm-a526b.4476861/
TWRP 3.7.0 is out with the support for decryption on Android 12 to be able to backup firmware. Pls update, thx
I'm sorry to have left you guys hanging! I've been too busy with personal stuff but I will get back on this as soon as possible.
flashed in A526BXXU1AUAH, when press buttons for recovery, it freeze on boot logo
does this also work for the a52s 5g version?
LuzzyKins said:
does this also work for the a52s 5g version?
Click to expand...
Click to collapse
No, the version you should be looking at is: https://forum.xda-developers.com/t/recovery-official-twrp-3-7-0-2-for-galaxy-a52s-5g.4488419/