{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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.
Code:
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your 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.
Supported Models:
Galaxy A12s SM-A127F and M12 SM-M127F.
Download & Guide:
1. Unlock your bootloader.
2. Download A12s : a12s.
3. Reboot to download mode and flash vbmeta_disabled.tar in USERDATA slot and click start, Device will reboot to recovery mode prompting you to wipe data so wipe data and reboot to download mode again.
4. Put the TWRP TAR for your device with Odin in the AP slot and click start.
5. Reboot to recovery via recovery key combo (Vol up + power + USB connected).
6. Disable encryption:
- Go to Advanced > Terminal, type: multidisabler.If vendor complain about free space left on device, will attempt to resize vendor. and it ask to - Run multidisabler again!.- Type: multidisabler again. will see - Finished. when done.- Go back to Wipe > Format Data > type yes.- Reboot to recovery.7. Flash magisk apk in twrp.
8. Reboot to system, Enjoy.
Note:
To disable encryption manually:
You need to replace fileencryption=ice with encryptable=ice only in userdata line (maybe rest lines) in vendor/etc/fstab.exynos
To avoid stock recovery restoration manually:
Rename system/recovery-from-boot.p to recovery-from-boot.p.bak
Click to expand...
Click to collapse
Support:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Telegram:
https://t.me/twrp_a_m_series
Bugs:
- Encryption not fully working.
Thanks:
TWRP team
@ianmacd for multidisabler
@physwizz for testing
Sources:
Kernel tree
Device tree
Changelog:
10.12.2021 - Initial Release.
Thanks for your great work.
When I flash the vbmeta_disabled.tar Odin fails to flash it. Any ideas?
P.S.: My phone is Samsung galaxy M12, baseband version M127GDDU2AUH1. I rooted it using the modified magisk from this link. Patched the whole AP file with this magisk app before flashing.
mdbshuvo said:
When I flash the vbmeta_disabled.tar Odin fails to flash it. Any ideas?
P.S.: My phone is Samsung galaxy M12, baseband version M127GDDU2AUH1. I rooted it using the modified magisk from this link. Patched the whole AP file with this magisk app before flashing.
Click to expand...
Click to collapse
You don’t need it
physwizz said:
You don’t need it
Click to expand...
Click to collapse
When I flashed the recovery, Odin says Pass and the phone tries to boot into recovery. After the boot logo, the screen goes black (It doesn't turn off though). When I connect the phone to PC, the phone seemed to be on. I can run all sorts of adb comands in it, though the screen remains black.
mdbshuvo said:
When I flashed the recovery, Odin says Pass and the phone tries to boot into recovery. After the boot logo, the screen goes black (It doesn't turn off though). When I connect the phone to PC, the phone seemed to be on. I can run all sorts of adb comands in it, though the screen remains black.
Click to expand...
Click to collapse
I think you are on updated bootloader.
U3 and U4 kernel here for testing
a12s u3 & u4 kernel (Exynos 850)
physwizz a12s u4 kernel version 6 For both u3 and u4 Built using a127f U4 source code For OneUI 3.1 ( also works for GSIs) Samsung securities disabled More CPU governors Conservative, On-demand, Userspace, powersave, performance, energy_step...
forum.xda-developers.com
Will this work on A12 ,not the S model ?
sarmale2020 said:
Will this work on A12 ,not the S model ?
Click to expand...
Click to collapse
No
Does this support U3 Baseband?
Will update
Drobly said:
Does this support U3 Baseband?
Click to expand...
Click to collapse
Will update it soon
afaneh92 said:
I think you are on updated bootloader.
Click to expand...
Click to collapse
Hi afaneh92,
I have same problem. Bootloader was unlocked, phone was rooted via patched magisk.
I used your twrp-3.6.0_11-2_afaneh92-a12s, but I didn't install vbmeta_disable.tar - it didn't work in Odin.
Now after odin action with your twrp version I have a blank screen.
What can I do now? What does your sentence mean?
Would be great to get a solution.
Regards
bricked_it_quick said:
Hi afaneh92,
I have same problem. Bootloader was unlocked, phone was rooted via patched magisk.
I used your twrp-3.6.0_11-2_afaneh92-a12s, but I didn't install vbmeta_disable.tar - it didn't work in Odin.
Now after odin action with your twrp version I have a blank screen.
What can I do now? What does your sentence mean?
Would be great to get a solution.
Regards
Click to expand...
Click to collapse
Its ok to post on what firmware you are and exact model!
afaneh92 said:
Its ok to post on what firmware you are and exact model!
Click to expand...
Click to collapse
Whoops yes sorry.
SM-A127F/DSN
SM-A127F_1_20211015071934_58q81hxl4y_fac.zip
Is this enough information for you? Don't have more access on information becuase of blank screen, can just access DL mode. I could try to reinstall stock ROM if necessary for you.
Edit: via Odin I reinstalled my rooted fw.
Base band version: A12FXXU3AUI1
Security patch from 01.10.2021
If you need more information, please let me know.
Regards
bricked_it_quick said:
Whoops yes sorry.
SM-A127F/DSN
SM-A127F_1_20211015071934_58q81hxl4y_fac.zip
Is this enough information for you? Don't have more access on information becuase of blank screen, can just access DL mode. I could try to reinstall stock ROM if necessary for you.
Click to expand...
Click to collapse
This show only model, if date is correct might be the October patch. U3 or 4. Wait for new twrp. Need to update kernel.
afaneh92 said:
This show only model, if date is correct might be the October patch. U3 or 4. Wait for new twrp. Need to update kernel.
Click to expand...
Click to collapse
Maybe this helps you:
AP_A127FXXU3AUJ5_CL22565658_QB44784085_REV00_user_low_ship_MULTI_CERT_meta_RKEY_OS11.tar.md5
Base band version: A12FXXU3AUI1
Security patch from 01.10.2021
Additional information: I didn't check any options in Odin like Nand Erase, because that was not mentioned in your manual.
Thanks in advance, paypalled some coffees for you.
bricked_it_quick said:
Maybe this helps you:
AP_A127FXXU3AUJ5_CL22565658_QB44784085_REV00_user_low_ship_MULTI_CERT_meta_RKEY_OS11.tar.md5
Base band version: A12FXXU3AUI1
Security patch from 01.10.2021
Additional information: I didn't check any options in Odin like Nand Erase, because that was not mentioned in your manual.
Thanks in advance, paypalled some coffees for you.
Click to expand...
Click to collapse
thanks
bricked_it_quick said:
Maybe this helps you:
AP_A127FXXU3AUJ5_CL22565658_QB44784085_REV00_user_low_ship_MULTI_CERT_meta_RKEY_OS11.tar.md5
Base band version: A12FXXU3AUI1
Security patch from 01.10.2021
Additional information: I didn't check any options in Odin like Nand Erase, because that was not mentioned in your manual.
Thanks in advance, paypalled some coffees for you.
Click to expand...
Click to collapse
new twrp based on U4 is up, please report back.
afaneh92 said:
new twrp based on U4 is up, please report back.
Click to expand...
Click to collapse
Should I try it too? I had the similar issue and you mentioned it may have to do something with updated bootloader.
Though my baseband version - M127GDDU2AUH1
Thank you.
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tested Working on A750F, A750FN, A750G and A750GN - 22/03/20
This Guide is outdated now..
It "ONLY" works on the initial One UI 2 update that started rolling out in March 2020
It has issues on the june patch. So "DO NOT" report bugs if you are on the june patch.
Use this at your own risk. I am not responsible for any damage that may happen to your device.
Make sure to have the official firmware downloaded for your device in case anything goes wrong.
This will void your warranty
This will also trip the knox counter.
Installation Guide
1. Unlock The bootloader
2. Boot into download mode
3. Using Odin, Flash Magisk_patched_boot.tar in the "AP" Slot.
4. Reboot download and flash Twrp recovery using odin in AP slot.
5. Reboot to TWRP and "FORMAT" , not wipe the data.
6. Flash Magisk-v20.3.zip
7. Reboot to download and flash Officialrecovery.tar in "AP" slot.
8. Reboot your device.
DOWNLOADS
Magisk Boot Img - http://www.mediafire.com/file/m9dwiww6i492xl6/Magisk_patched_boot.tar/file
Official recovery - http://www.mediafire.com/file/nhrj8060rbv43rm/Officialrecovery.tar/file
Notes:
1. Only Magisk v20.3 is tested, other versions may/may not work. Report if other versionswork, I will update OP.
2.This "WILL NOT" install Twrp on your device as Twrp is not updated and it will cause bootloops.
3. Failing to follow and steps mentioned above, you will end up in a bootloop.
Please DO NOT Share direct link to these files, Share The link to this post.
Feedback is Highly appreciated
Hit the Thanks Button
Credits:
Me for finding this method
@ashyx for Building Twrp
And Teamwin
Download link ??
Kumarranveer_RK said:
Download link ??
Click to expand...
Click to collapse
I just realized that xda did not upload the files due to size limit, I have updated OP.. Check it
These files work on the A750G/DS. Or they're just for the F version
JHAM2005 said:
These files work on the A750G/DS. Or they're just for the F version
Click to expand...
Click to collapse
They are confirmed working on A750F and A750GN, if possible, try and report for A750G
Thanks bro .. rooted my a7 2018 (Android Q) .. No issues Till now
well i did flash magisk patched boot, and succesfully flashed TWRP,
but i get this weird problem in twrp part, where my internal storage shows 0 MB in twrp.
and rebooting it, device goes into download mode all by itself.
what should i do now? wipe the internal storage or format it by Writing yes.?
nanodroid.cyberbot said:
well i did flash magisk patched boot, and succesfully flashed TWRP,
but i get this weird problem in twrp part, where my internal storage shows 0 MB in twrp.
and rebooting it, device goes into download mode all by itself.
what should i do now? wipe the internal storage or format it by Writing yes.?
Click to expand...
Click to collapse
Its mentioned in the op please read it carefully format it by typing yes. And install magisk zip from sd card
Can we use the TWRP 3.2.3-1 listed here: https://forum.xda-developers.com/galaxy-a7/development/recovery-twrp-3-2-3-1-galaxy-a7-2018-t3876798
You did not give a link to which TWRP version you used. So just asking.
sameermanas said:
Can we use the TWRP 3.2.3-1 listed here: https://forum.xda-developers.com/galaxy-a7/development/recovery-twrp-3-2-3-1-galaxy-a7-2018-t3876798
You did not give a link to which TWRP version you used. So just asking.
Click to expand...
Click to collapse
No other twrp is available for our device.. So, yes this one
thanks! work like a charm
I downloaded the Indian version and installed it on an a750 FN and it works ....
I will keep trying more things
good job
Delete
The Root works perfectly on the A750G/DS, the only thing that does not work properly is the TWRP, does not recognize the internal memory, only recognizes the SD card
PD... An Official Recovery query is only for version F and GN or also works in G/DS versions
how could I return my battery at the original state? Im having fast drain ..
Hi! I have followed the steps correctly and rooted my Samsung Galaxy A7 2018. However, whenI restart my device, it always got stuck on download mode. Any help I can get?
Equinoxx17 said:
Hi! I have followed the steps correctly and rooted my Samsung Galaxy A7 2018. However, whenI restart my device, it always got stuck on download mode. Any help I can get?
Click to expand...
Click to collapse
This happens when you don't flash magisk zip file, did u flash that after installing twrp? And after that did u install stock recovery? Try this, if it does not work, start from scratch again.
KChoudhry said:
This happens when you don't flash magisk zip file, did u flash that after installing twrp? And after that did u install stock recovery? Try this, if it does not work, start from scratch again.
Click to expand...
Click to collapse
I did flash magisk after installing TWRP. I also installed the stock recovery. But still, it goes back to download mode when I restart my phone.
Equinoxx17 said:
I did flash magisk after installing TWRP. I also installed the stock recovery. But still, it goes back to download mode when I restart my phone.
Click to expand...
Click to collapse
You need to start from scratch then
KChoudhry said:
You need to start from scratch then
Click to expand...
Click to collapse
I guess I'll be staying at Android Pie for now. I think I'll be waiting for other alternatives that doesn't boot into download mode when restarted. Somehow, I thank you for sharing info on how to root Samsung Galaxy A7 2018.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Proudly Presents
Another Exclusive Release
Supported Model
Blu View 2
B130DL
Recoveries
TWRP_10 Recovery
Roms
GSI Roms ?
Info
Patched-lk.img contains the Orange State Boot warning Patched out
Patched-boot.img & Patched-vbmeta.img Are Pre-Rooted Images
BootLoader Unlock
MtkClient
Recovery Download & Device Tree
Device Source
A-Team Website
A-Team Supported Devices
TeleGram Live Support
A-Team Digital Solutions
Contributors
Thanks to @bkerler for MtkClient
orb_selektor said:
Please read and respect the rules, no duplicated threads
Thanks
Click to expand...
Click to collapse
I'm sorry what ??
PizzaG said:
I'm sorry what ??
Click to expand...
Click to collapse
Sorry my bad, nevermind
I’m sorry, but, where are the patched images? Are they on GitHub?
Also, are they stock or TWRP?
Jakefusion said:
I’m sorry, but, where are the patched images? Are they on GitHub?
Also, are they stock or TWRP?
Click to expand...
Click to collapse
TWRP_10 is on github in the release section. I'll have to see what I did with the other images and get them up
Jakefusion said:
I’m sorry, but, where are the patched images? Are they on GitHub?
Also, are they stock or TWRP
Click to expand...
Click to collapse
I made my own image files from Firmware with build number QP1A.190711.020
And build version
V10.0.05.05.05.02
at the moment twrp isn't exactly functional so you need to install with mtkclient. Also it's not exactly apparent but you need to do this with the battery removed. If anyone wants I can make a guide better detailing the bootloader unlock process.
Put the attachments in the mtkclient folder.(vbmeta is included with mtkclient)
Backup your existing partitions using
python mtk r boot,lk,vbmeta boot.img,lk.img,vbmeta.img
Write new partitions using
python mtk w boot,lk,vbmeta boot.p.img,lk.p.img,vbmeta.img.empty
(If python fails try just using py)
install patched magisk from here
https://raw.githubusercontent.com/v...9e22fa276698f6c03bc1168df2c10/app-release.apk
Thanks PizzaG for the unlock process.
Before someone installs twrp can they make a backup of their recovery for me?
python mtk r recovery recovery.img
Could be python or py depending on your system
Also I am working on getting gsis or other custom ROMs on the device. Lack of fastboot and fastbootd make it a pain but I got one gsi to boot (network issues though)
i dont get it.
matthewdwheelersr said:
i dont get it.
Click to expand...
Click to collapse
got that little booger tho!
matthewdwheelersr said:
got that little booger tho!
Click to expand...
Click to collapse
i LOVE YALL CODE HEADS!!! I did soft brick it once, soft brick tho. big difference between a soft and a hard brick... If it wasn't for y'all code heads I wouldn't be able to live like I do. I love y'all man. this phone i had fun with its janky shtanky buttheads! Turning phones into GANGSTERS!!!
Technically maybe two soft bricks. bootloop with no logo tho... im just so happy guys...ya know it?
Hi, so I got this phone as a backup.
I tried putting in another sim card, but it said invalid.
Any idea if rooting would help? Or is this more of a hardware incompatibility?
zph0eniz said:
Hi, so I got this phone as a backup.
I tried putting in another sim card, but it said invalid.
Any idea if rooting would help? Or is this more of a hardware incompatibility?
Click to expand...
Click to collapse
SIMLock. Nothing you can do besides use it on TracFone for a year. I've seen GSIs remove sim locks before but it's been a while,and it was on Kroger Wireless in the Sprint days. Maybe it will work maybe it won't.
mateo121212 said:
I made my own image files from Firmware with build number QP1A.190711.020
And build version
V10.0.05.05.05.02
at the moment twrp isn't exactly functional so you need to install with mtkclient. Also it's not exactly apparent but you need to do this with the battery removed. If anyone wants I can make a guide better detailing the bootloader unlock process.
Put the attachments in the mtkclient folder.(vbmeta is included with mtkclient)
Backup your existing partitions using
python mtk r boot,lk,vbmeta boot.img,lk.img,vbmeta.img
Write new partitions using
python mtk w boot,lk,vbmeta boot.p.img,lk.p.img,vbmeta.img.empty
(If python fails try just using py)
install patched magisk from here
https://raw.githubusercontent.com/v...9e22fa276698f6c03bc1168df2c10/app-release.apk
Thanks PizzaG for the unlock process.
Click to expand...
Click to collapse
Finally by booting the livedvd directly on my computer instead of in VirtualBox I got mtkclient to work and stop getting the EMI 12 byte error.
Then I made a successful backup and proceeded to flash the two files you attached. The third I assumed should be an empty file so I touched an empty file into existence before writing.
I assumed I need to boot up the phone in order to flash the patched magisk you provided. The phone screen stayed black. Using lsusb shows that the phone is in a bootloop since it appears and disappears from the list of devices.
I flashed back the backup images and the phone, as expected, boots up but is not unlocked or rooted.
What am I missing here to get my B130DL rooted?
BluPhoneHome said:
Finally by booting the livedvd directly on my computer instead of in VirtualBox I got mtkclient to work and stop getting the EMI 12 byte error.
Then I made a successful backup and proceeded to flash the two files you attached. The third I assumed should be an empty file so I touched an empty file into existence before writing.
I assumed I need to boot up the phone in order to flash the patched magisk you provided. The phone screen stayed black. Using lsusb shows that the phone is in a bootloop since it appears and disappears from the list of devices.
I flashed back the backup images and the phone, as expected, boots up but is not unlocked or rooted.
What am I missing here to get my B130DL rooted?
Click to expand...
Click to collapse
Did you follow the instructions on the mtkclient github to unlock the bootloader first? Does your firmware match the files I posted? The blank vbmeta is in the download of mtkclient no need to make one. If your firmware does not match mine I can patch the files manually if you attach them and make sure to let me know what firmware or I can walk you through doing it yourself.
Useful links
Creating your own patched boot.img guide.
https://topjohnwu.github.io/Magisk/install.html
Creating your own patched lk.img (the orange state is what you need to remove)
https://www.getdroidtips.com/orange-yellow-red-state-warnings-mediatek/
mateo121212 said:
Did you follow the instructions on the mtkclient github to unlock the bootloader first? Does your firmware match the files I posted? The blank vbmeta is in the download of mtkclient no need to make one. If your firmware does not match mine I can patch the files manually if you attach them and make sure to let me know what firmware or I can walk you through doing it yourself.
Click to expand...
Click to collapse
Custom build version is BLU_B130DL_V10. 0.05.05.05.02_FSec
Build number QP1A.190711.020
This appears to match yours.
I'll need to reread the unlock bootloader part.
Thanks for the super fast reply!
BluPhoneHome said:
Custom build version is BLU_B130DL_V10. 0.05.05.05.02_FSec
Build number QP1A.190711.020
This appears to match yours.
I'll need to reread the unlock bootloader part.
Thanks for the super fast reply!
Click to expand...
Click to collapse
https://github.com/bkerler/mtkclient#unlock-bootloader
mateo121212 said:
Did you unlock the bootloader first
Click to expand...
Click to collapse
No I did not. And it appears I first need to backup boot and vbmeta, reboot phone, install patched magisk, adb push boot.img and install boot.img using magisk, pull boot.img back off phone and save as boot.patched before unlocking bootloader. Or do I just skip to the unlock bootloader section?
BluPhoneHome said:
No I did not. And it appears I first need to backup boot and vbmeta, reboot phone, install patched magisk, adb push boot.img and install boot.img using magisk, pull boot.img back off phone and save as boot.patched before unlocking bootloader. Or do I just skip to the unlock bootloader section?
Click to expand...
Click to collapse
Since you have same firmware you don't need to do magisk first. Just follow unlock procedure then flash the 2 modified files and blank vbmeta and reboot and install patched magisk apk. If your interested I created a magisk module that enables gesture navigation. Working on a debloat module as well.
Hey just wanted to say thanks to all that worked to get this going, y'all got my Alcatel tetra rooted, or some of y'all were in on that project and now my view 2, and I was just curious to see if it would work, so I attempted this whole process, on tcl a3 a509dl, took out the boot lk vbmeta, from mtkclient, and backed up those files for tcl then created magisk patch and lk patch and reflashed and it work, anyway again thank you
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
An essential tool for anybody that loves to modify their Android device is a good custom recovery. TWRP has been around since the invention of the wheel back in 1996 and has been providing modders with all kinds of great tools.
Code:
/*
* Your warranty is... still valid?
*
* 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 RECOVERY
* 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.
*/
Installation instructions:
Spoiler
Flash the ZIP through your CWM/TWRP recovery
Known issues:
Spoiler
Nothing so far...
Download:
Spoiler
below!
Device-specific tree: https://github.com/project-deviceresurrection/twrp_device_samsung_arubaslim
cant you also just make a tar archive easily?
like one u can flash through odin...
Ricky Thunderfox said:
cant you also just make a tar archive easily?
like one u can flash through odin...
Click to expand...
Click to collapse
i could ...
by the way..if you have this device..can you check if this device boots this twrp?
notnoelchannel said:
i could ...
by the way..if you have this device..can you check if this device boots this twrp?
Click to expand...
Click to collapse
Sure. Ill try doing it today but i cant say for sure. So if today i cant ill try tomorrow... Also in case you didnt know if you create a TWRP tar u dont need to add md5 extension
i cant seem to get it to flash through odin...
Any links how to root + install old custom recovery?
Ricky Thunderfox said:
i cant seem to get it to flash through odin...
Any links how to root + install old custom recovery?
Click to expand...
Click to collapse
gonna make a tar
Here ya go
notnoelchannel said:
Here ya go
Click to expand...
Click to collapse
I already made a tar but odin keeps saying
[ODIN3]
PRODUCT: GT-I8260
VERSION: I8260XXAPA1
HW REV : 8
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: OFFCIAL
usb_read() transaction failed!
odin: oops!
when i try to flash it will just be stuck on the flashing process
which odin version do i need?
EDIT: it does the same with your tar file
Ricky Thunderfox said:
I already made a tar but odin keeps saying
[ODIN3]
PRODUCT: GT-I8260
VERSION: I8260XXAPA1
HW REV : 8
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: OFFCIAL
usb_read() transaction failed!
odin: oops!
when i try to flash it will just be stuck on the flashing process
which odin version do i need?
EDIT: it does the same with your tar file
Click to expand...
Click to collapse
odin 3.07 atleast
EDIT: IT BOOTS!
(it just takes a while to flash)
Ricky Thunderfox said:
EDIT: IT BOOTS!
(it just takes a while to flash)
Click to expand...
Click to collapse
thanks for testing!
notnoelchannel said:
thanks for testing!
Click to expand...
Click to collapse
Since it boots now.. is there anywhere i can send you a DM or something? I'd like to help you with this device and possibly other devices too
I have a small community of friends who mess with mostly Samsung devices and we've learned a bit about some of the internals of the bootloader aswell as some other strange oddities.
Ricky Thunderfox said:
Since it boots now.. is there anywhere i can send you a DM or something? I'd like to help with this device and possibly other devices too
I have a small community of friends who mess with mostly Samsung devices and we've learned a bit about some of the internals of the bootloader aswell as some other strange oddities.
Click to expand...
Click to collapse
you can on XDA ( I think)
or on Discord: notnoelchannel#0655
but sorry, i don't take twrp device requests
notnoelchannel said:
you can on XDA ( I think)
or on Discord: notnoelchannel#0655
but sorry, i don't take twrp device requests
Click to expand...
Click to collapse
Added you... btw i didnt wanna make a request haha.
i just wanted to know if youre interested
Works on Samsung Galaxy Core i8260 too
Thank you very much! TWRP 3.0.2-0 ended up in a bootloop when flashed via zip and heimdall no matter what... even for both old and new versions. However, this newer TWRP worked for me (flashed with heimdall)!
Just a small thing, I wanted to look at the source code, but your link is broken unfortunately... could you fix it?
Update: TWRP works, but it does not let me to boot into system again. With this recovery `/sdcard` is renamed as `/emmc`, not sure if this is related. I can turn back into an older TWRP, but that would be a pity... perhaps do you know what's the issue? I have seen some ROMs not booting with some newer TWRP versions, but I can't boot stock Samsung either.
@Ricky Thunderfox what ROM are you running, just in case? Do you have double-sim or single-sim?
aat596 said:
Works on Samsung Galaxy Core i8260 too
Thank you very much! TWRP 3.0.2-0 ended up in a bootloop when flashed via zip and heimdall no matter what... even for both old and new versions. However, this newer TWRP worked for me (flashed with heimdall)!
Just a small thing, I wanted to look at the source code, but your link is broken unfortunately... could you fix it?
Update: TWRP works, but it does not let me to boot into `/system` again. With this recovery `/sdcard` is renamed as `/emmc`, not sure if this is related. I can turn back into an older TWRP, but that would be a pity... perhaps do you know what's the issue? I have seen some ROMs not booting with some newer TWRP versions, but I can't boot stock Samsung either.
@Ricky Thunderfox what ROM are you running, just in case? Do you have double-sim or single-sim?
Click to expand...
Click to collapse
github took down the account so sorry, i can't release the source code
and yes, I made this for i8260
GT-I8260 = arubaslim
also yeah, I'll fix the "/emmc" bug
Thank you very much! Just mention me when it's ready!
notnoelchannel said:
github took down the account so sorry, i can't release the source code
and yes, I made this for i8260
GT-I8260 = arubaslim
also yeah, I'll fix the "/emmc" bug
Click to expand...
Click to collapse
github took down the account so sorry, i can't release the source code
Click to expand...
Click to collapse
Maybe GitLab or other hosting solution would be feasible? Otherwise, just PM me (as long as you still have the source on computer, of course)
Hey there, I'm also interested in the device tree for this device
Please upload it somewhere, it would be funny to resurrect this old device
MLX said:
Hey there, I'm also interested in the device tree for this device
Please upload it somewhere, it would be funny to resurrect this old device
Click to expand...
Click to collapse
https://github.com/unlegacy-devices/twrp_device_samsung_arubaslim Here yall go
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
riceDroid for Pixel 4a [sunfish]
What is riceDroid?
* Ricedroid is a FREE OPENSOURCE Android Operating System based on LineageOS and crDroid, that aims to provide necessary "ricing" aka customizations for ANDROID while being fast and stable. This operating system is highly inspired by Oxygen OS (10-11) and nothingOS, we strive to make things different but not too far from AOSP.
What is RiseUI?
* RiseUI is the name for our firmware skin/user interface.
Terminology
* The term \'rice\' is used to describe a person's unix desktop where \'ricing\' is an act where someone customizes their desktop such as the changing icons, panels or system interface.
source: https://jie-fang.github.io/blog/basics-of-ricing
Based on Android 13 | Tiramisu QPR1
What's working?
Most basic stuffs
Bugs and Issues
Please tell me with a logcat attached
Variants available
PIXEL build (only) - comes with full pixel gapps
Device specific changes
Initial build
Credits
Michael Bestas
Changelog
Source Changelog
Download link
Click Here!
Android OS version: 13.0.0_r30
Security patch level: February 2023
Build author/Device Maintainer: xioyo
Firmware source code: https://github.com/ricedroidOSS
Firmware created by: The ricedroidOSS Team
Screenshots of ROM
If u like my work and willing to help me for paying the server feel free to donate here: https://www.paypal.me/sufiyan777
Boot image: https://drive.google.com/file/d/14HBlB-8ZZgOOA3bFG6fMnRX0i7b2855y/view?usp=sharing
Nice rom
Thanks for this rom, great phone control mods,,seems to run a full 7-10 degrees warmer then stock at 97f , I will give it a chance to settle down a little and then see where its at, also is it missing the camera app or Iam i just not seeing it? Thanks update,,,, i just installed stock gcam from the play store runs fine, update ,, temp settled down to 94-95 on idle, acceptable,, battery drain was pretty high in standby, I recorded 8 percent /hour . Anyone else have this?
Any firmware requirement prior to flashing (13.0 image from google)? Apply via ADB sideload method?
13 firmware for sure, and I don't recall if it's via adb side load or just a flash all bat file
hammered58 said:
13 firmware for sure, and I don't recall if it's via adb side load or just a flash all bat file
Click to expand...
Click to collapse
Thanks man. Unfortunately, I couldn't get it to flash. I did flash the latest factory image from google, then tried sideloading this. No-go. I also tried extracting the boot.img, flashing that, then trying to sideload. Still no dice. No biggie, I'll just wait until someone can clue me in
tnicko said:
Thanks man. Unfortunately, I couldn't get it to flash. I did flash the latest factory image from google, then tried sideloading this. No-go. I also tried extracting the boot.img, flashing that, then trying to sideload. Still no dice. No biggie, I'll just wait until someone can clue me in
Click to expand...
Click to collapse
Ok you could try this
Fastboot -w. This wipes data
Fastboot flash boot boot.img.
Reboot recovery and adb sideload rom
I think when you boot into the recovery it will be stock recovery
Hth
hammered58 said:
Ok you could try this
Fastboot -w. This wipes data
Fastboot flash boot boot.img.
Reboot recovery and adb sideload rom
I think when you boot into the recovery it will be stock recovery
Hth
Click to expand...
Click to collapse
Yeah I tried that. Clean flashed stock, then used riceDroid boot.img. Booted in that without issue, enabled ADB, then adb sideload riceDroid...zip. It flashed without error, but then bootloops a few times before booting itself back into recovery. Strange...
tnicko said:
Yeah I tried that. Clean flashed stock, then used riceDroid boot.img. Booted in that without issue, enabled ADB, then adb sideload riceDroid...zip. It flashed without error, but then bootloops a few times before booting itself back into recovery. Strange...
Click to expand...
Click to collapse
Don't forget the fastboot -w before all the other steps
I think that's the key,, but I have know to be wrong !! Lol
tnicko said:
Yeah I tried that. Clean flashed stock, then used riceDroid boot.img. Booted in that without issue, enabled ADB, then adb sideload riceDroid...zip. It flashed without error, but then bootloops a few times before booting itself back into recovery. Strange...
Click to expand...
Click to collapse
Factory reset done?
Seems like I forgot to push boot.img in post.
Sorry for my mistake and will include from new update onwards. And yeah a new update is coming
Unknownbitch said:
Factory reset done?
Click to expand...
Click to collapse
Yup.
I just used a payload extractor to grab the boot.img. I'll try again once the update drops
tnicko said:
Yeah I tried that. Clean flashed stock, then used riceDroid boot.img. Booted in that without issue, enabled ADB, then adb sideload riceDroid...zip. It flashed without error, but then bootloops a few times before booting itself back into recovery. Strange...
Click to expand...
Click to collapse
Try sideload with twrp, i got booted when install it trough twrp
Unknownbitch said:
Seems like I forgot to push boot.img in post.
Sorry for my mistake and will include from new update onwards. And yeah a new update is co
Click to expand...
Click to collapse
Hbmsvmanager fixed??
Unknownbitch said:
Seems like I forgot to push boot.img in post.
Sorry for my mistake and will include from new update onwards. And yeah a new update is coming
Click to expand...
Click to collapse
Hi guys! Anyone have a full customization list of this Rom?
M.E.A said:
Try sideload with twrp, i got booted when install it trough twrp
Click to expand...
Click to collapse
I didn't even think of TWRP because I haven't touched it in years. I thought it wasn't updated to work with the later Pixel phones. Sheesh....well, I'm up and running on stock, albeit rooted, so I kind of don't feel like starting from scratch again. But I'll definitely give it a go one of these days.
M.E.A said:
Hbmsvmanager fixed??
Click to expand...
Click to collapse
yep
Marcia8246 said:
Hi guys! Anyone have a full customization list of this Rom?
Click to expand...
Click to collapse
It have a lot of customisations if u want the ss of all join in the tg group i will share it there
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
OS:
LineageOS 20.0
Devices supported:
Lenovo Xiaoxin Pad 2022 (China) (4/64 and 6/128)
Means no radio support and no haptics.
Kernel:
4.19.275, Source @ GitHub
Bugs:
Not found
Installation:
Flash via TWRP as zip, if any troubles with installation, please format super and flash super_1.img from ZUI firmware to super partition.
FLASH ON YOUR RISK!!!
lineage-20.0-20230521-UNOFFICIAL-tb128fu.zip
Please donate if you want to support my work.
Can you provide kernel source, device trees and vendor trees?
after flashing and testing for a bit i noticed that Shim level is way higher than on stock or any gsi i have used
the higher the brightness, the worse the situation is.
after opening and closing any app, its back to normal a bit better but shim is still very high and noticable compared to any gsi or stock
turned off the device (didnt shutdown) after a minute or so, turned on, it flickered and shim is back until opening any app
if you are interested in more details or logs, let me know
i will have this build flashed for at least few days to test
hi! thank you for feed back.
brightness value are default. not device related. pls check vendor overlay.
Atm dont have pbty to share device/vendor.
Kernel is here https://forum.xda-developers.com/t/...tb128xu-kernel-sources.4583191/#post-88570739 dtb and dtbo are used from stock.
you may want to add direct github kernel link to main post since its required by xda gpl rules, your post may get banned and we definately dont want that xD
heineken78 said:
Kernel is here https://forum.xda-developers.com/t/...tb128xu-kernel-sources.4583191/#post-88570739 dtb and dtbo are used from stock.
Click to expand...
Click to collapse
Hi! Thanks for sharing your work on the forum. As per the post above, we require a direct link to the kernel source in the first post to ensure GPL compliance. As a courtesy, I've edited the first post and added that for you (from the source link you have mentioned in your other thread), so you're good to go. But please remember to do so in the future whenever you're creating threads sharing your development work.
Regards,
shadowstep
Senior Moderator
any updates?
LOS-20.0-20230611v2-UNOFFICIAL-tb128fu.zip
uhhhh
Psyl0w said:
LOS-20.0-20230611v2-UNOFFICIAL-tb128fu.zip
Click to expand...
Click to collapse
i kinda "semi-hard bricked" the tablet... not with the ROM, but in some other way, can you pm me on telegram if you could help?...
and i cant properly flash lineage now, it crashes the moment i start flashing it.., flashing super_1 to super doesnt fix it
welp, after flashing all the partitions manually, i ended up in crashdump, thats my "semi-hard brick", only stock flobal fw kernel works, any other kernel, zui, CAF, crashdump...
flashed stock kernel from global fw and lineage booted, everything is laggy (also thanks to my semi-hard brick), i guess this tablet can just go to the shelf...
oh **** and i dont have wifi unless i flash stock vendor with stock kernel :| and the display doesnt rotate at all, even if i force landscape, it stays in portrait.. bug of stock kernel. please help, i just dont know what to do, flashing zui from qfil doesnt help too...
tqmatvey said:
flashed stock kernel from global fw and lineage booted, everything is laggy (also thanks to my semi-hard brick), i guess this tablet can just go to the shelf...
Click to expand...
Click to collapse
actually before flashing stock vendor, it doesnt lag
Hi!
Thank you for your work! I wanna flash Lineage OS in this tablet but I dont know how to do it. Can someone tell me where I can find TWRP and how to flash it?
Thanks
Hi everyone! Hope you are fine
I tried to flash Lineage OS today and I couldnt do it. I flashed TWRP (no root) but it couldnt flash zip. It just said It couldnt do it.
I tried to flash super.img but i dont know where are the super partition to format. I went to wipe menu of twrp and there wasnt a super partition, just “ART/Dalvik”, “SD card”, etc, but nothing called “Super”.
Anyway I tried flash super1.img from original firmware with twrp flashing image menu and after reboot I saw black screen with Qualcomm Crashdump text. In flash menu I could see a “super_…” partition but there wasnt it in wipe menu.
After that I prayed to all Saints to restore global rom and I had good luck and thats all.
As can you see I need a little tutorial to do it, If any caritative person wanna share his knowledge please thank you
PD: i dont flash any rom since I had my last android device five years ago. I just used CWM, zip files and thats all. I see that this procedures are more difficult nowadays
@ajesushn use lineage recovery, unzip, flash to recovery, reboot to lineage recovery, fastboot mode > flash super_1.img, sideload latest lineage, reboot recovery so that it switches slots, flash other stuff you need (gapps, microg, magisk) you choose, format data , boot to system
for now quite sad that the device trees aren't public, would love to get crdroid working for the tb128fu
tqmatvey said:
@ajesushn use lineage recovery, unzip, flash to recovery, reboot to lineage recovery, fastboot mode > flash super_1.img, sideload latest lineage, reboot recovery so that it switches slots, flash other stuff you need (gapps, microg, magisk) you choose, format data , boot to system
for now quite sad that the device trees aren't public, would love to get crdroid working for the tb128fu
Click to expand...
Click to collapse
Thank you for the recovery. Just a doubt: there are 2 lineage20 zips. Which works better? I read your replies and the update seems that give more issues than fixes
ajesushn said:
Thank you for the recovery. Just a doubt: there are 2 lineage20 zips. Which works better? I read your replies and the update seems that give more issues than fixes
Click to expand...
Click to collapse
as i clearly mentioned, my issues were caused by another thing, not lineage related, latest lineage 20 works perfectly
Thank you. Install LineageOS successfully. Everything works great and very fluid. I haven't found any problem so far.