Development [AOSP-11] [OFFICIAL] Samsung SM-A125F TWRP - Samsung Galaxy A12

DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS
Install instructions:
1. Download an arbitrary SM-A125F firmware zip package on SamMobile.com, whose Android version is 11. I used A125FXXU2BVB4 firmware.
2. Clean install firmware (means, no magisk boot module, etc. Flash with ODIN full firmware (BL, AP, CP and CSC _A125FXXU2BVB4*.TAR.MD5. Tick in ODIN options: NAND ERASE; Re-partition. Make sure AUTO REBOOT is OFF!!!
3. Let ODIN flash all, on completion, click reset, disconnect and connect USB, Select recovery.img (below post) in AP slot, and nulled VBMETA.img (below) in USERDATA slot. again; Make sure AUTO REBOOT is OFF!!!
4. Let ODIN flash all. Once all succeeded; Hold <VolDn> + <Power> to shut down, then Hold <VolUp> + <Power> to reboot to TWRP
5. Once TWRP has booted, do full factory reset (wipe caches and data). After that, format data completely. Reboot to recovery once done.
6. Once TWRP has re-booted, go to advance, terminal and execute command: multidisabler.
This will protect data partition from becoming encrypted again, and secure recovery partition from being replaced.
7. Reboot to system, and setup device as normal. After this, you could install Root or what ever you want.
Important: device must boot directly to recovery or stock recovery will be restored if you boot direct to OS.
8. Enjoy!
What is working:
Mounting, flashing *.img to superpartitions, MTP also fixed now.
What is not working:
ADB sideloading;
You tell me...
Samsung Galaxy A12
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
Device tree: https://github.com/edward0181/android_device_samsung_a12
Kernel tree: https://github.com/00p513-dev/android_kernel_samsung_a12

10/05/2022
Rebuild kernel to fix issues with dynamic partitions. Backups and flashing img now doesn't break twrp and doesn't reboot anymore.
17/04/2022
Updated with latest FSTAB issues.
Will fix not being able to flash GSI to system partitions etc.
Will be online in TWRP.ME downloads soon, but below post is most recent.
https://eu.dl.twrp.me/a12/ Can be flashed from current recovery (TWRP) as IMG into recovery slot.
12/04/2022
Rebuild from A125FXXU2BVB4 firmware. Updated kernel to custom kernel. Modified FSTAB points to flash *.IMG files to dynamic partitions. Fixed FBE decryption of data partition.
04/10/2021
Updated to fix being able to install GSI in system-image partition. See below post
15/09/2021
* Fixed MTP, mount points of Dynamic_Partitions. All is working now, except Decrypting. As mentioned earlier, not important now as you can use OTG, or External_SD or MTP.
15/09/2021
* Redid whole tree, fixed partition errors. Works as system_root.
* FSTAB fixed
Still data decrypt issues, MTK is a pain... not important now, when using external_sd
20/08/2021
* Fixed FSTAB issues.
* Fixed Sideload and ADB issues
* Mounts of partitions fixed
Still to do: Decryption of DATA partition failing as soon as stock ROM is factory resetted. WIP.
09/08/2021
Initial entry; decrypt isn't working.
Is still Work in Progress.
to be updated

For those who wants to install GSI, etc:
Boot to recovery, flash IMG and select what partition you want to flash to.
No need for aditional tools with latest update.

And for the a125M?: ((

Elholas said:
And for the a125M?: ((
Click to expand...
Click to collapse
Both run on same hardware. Test and you tell me hihi. I only have A125F to test.

But will that not generate an error when flashing or could it damage the cell phone? I'm not sure

edward0181 said:
Both run on same hardware. Test and you tell me hihi. I only have A125F to test.
Click to expand...
Click to collapse
But will that not generate an error when flashing or could it damage the cell phone? I'm not sure

edward0181 said:
DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS
Install instructions:
1. Download an arbitrary SM-A125F firmware zip package on SamMobile.com, whose Android version is 11
2. Flash by Heimdall by PIT partitions or by Odin by BL, AP, CP, and CSC tar packages
3. Back to the stock ROM > go to Developments settings > allow OEM unlocking (Developments settings could be enabled by tapping 7~10 times somewhere in About Device)
4. If OEM unlocking is unseen to you, take software updates first
5. Also inside Developments settings, enable USB debugging
6. Download the TWRP image, and unzip.
7. Hold <VolUp>+<VolDn> with device tethered to USB-C with your PC
8. Hold <VolUp> to unlock OEM
9. Hold <VolUp>+<VolDn> again with device not disconnected of USB-C
10. Press <VolUp> without holding to enter Download mode
11. Open ODIN to flash the downloaded TWRP in AP slot with my TWRP image.
12. Hold <VolDn> + <Power> to shut down, then Hold <VolUp> + <Power> to reboot to TWRP
Important: device must boot directly to recovery or stock recovery will be restored if you boot direct to OS.
13. Enjoy!
What is working:
Mounting, flashing, sideloading.
What is not working:
Decrypting USERDATA
You tell me...
Device tree: https://github.com/edward0181/android_device_samsung_a12
Click to expand...
Click to collapse
Any pictures of the twrp it self? I'm curently testing something on android 10 and I don't want to revert back to android 11 yet.
Thanks.

LAST_krypton said:
Any pictures of the twrp it self? I'm curently testing something on android 10 and I don't want to revert back to android 11 yet.
Thanks.
Click to expand...
Click to collapse
{
"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"
}

will can i flash gsi roms using this twrp?

Yes You can flash roms.

Idk what I'm doing wrong but when I flashed twrp image through odin I just get to the samsung secured by knox with a normal warring that I'm not using samsungs official software. I'm going to try something else.

Never mind, just held vol up for a min and it works.

LAST_krypton said:
Idk what I'm doing wrong but when I flashed twrp image through odin I just get to the samsung secured by knox with a normal warring that I'm not using samsungs official software. I'm going to try something else.
Click to expand...
Click to collapse
Remove tick auto reboot, flash with odin. Once done disconnect usb and hold power and vol down till black screen. Release and direct vol up and power till you get into twrp.

edward0181 said:
Remove tick auto reboot, flash with odin. Once done disconnect usb and hold power and vol down till black screen. Release and direct vol up and power till you get into twrp.
Click to expand...
Click to collapse
For me it wount boot in to twrp untill i flash the vbmeta.

It installs like any twrp, right? I installed android 11 by Odin and my question was if it only put the image in AP to have the twrp, and in that case, all rom gsi are compatible?

LAST_krypton said:
For me it wount boot in to twrp untill i flash the vbmeta.
Click to expand...
Click to collapse
Could be. I’ve pre rooted my device with magisk to overcome this

edward0181 said:
Could be. I’ve pre rooted my device with magisk to overcome this
Click to expand...
Click to collapse
Yea, just tested you need to flash a vbmeta or pre disable dm-verity

<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1207)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> RQT_CLOSE !!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
:c

Elholas said:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1207)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> RQT_CLOSE !!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
:c
Click to expand...
Click to collapse
Is that on the A125M ?

Related

[Q] Leaked P3100 Stock ROM

Hi All,
I got hold of the leaked P3100 Stock ROM from Sammobile , googling for "P3100XWALD2_P3100OJVALD3_OJV" courtesy Hotfile.
{
"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"
}
I see within the download 4 md5 package for pushing through ODIN 1.85.
Need confirmation what goes where in ODIN for pushing this over serial interface?
Please help!
Some more Googling gave me the following:
1. Bootloader is the module that loads built-in recovery ( Stock / CWM ).
2. PDA is the firmware version that contains the android OS and system apps. ( Platform/PDA )
3. Phone is the modem version ( Modem/Radio ) - Secondary firmware that controls the network connectivity (2G/3G, wireless & Bluetooth).
4. CSC is the connection data could be network locked or supporting a specific region.
When you are updating they should all be updated to whatever firmware you choose via ODIN in md5 format.
If you are using odin they get flashed separately.
Flashing through ODIN 1.85 took 3:54 & top box said "FACCTORYFS".
<ID:0/020> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_P3100XWALD2_CL448962_REV04_user_low_ship.tar.md5 is valid.
<OSM> PLATFORM_P3100XWALD2_CL448962_REV04_user_low_ship.tar.md5 is valid.
<OSM> MODEM_P3100XXLD4_REV_04_CL1128355.tar.md5 is valid.
<OSM> CSC_OJV_P3100OJVALD3_CL448962_REV04_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/020> Odin v.3 engine (ID:20)..
<ID:0/020> File analysis..
<ID:0/020> SetupConnection..
<ID:0/020> Initialzation..
<ID:0/020> Get PIT for mapping..
<ID:0/020> Firmware update start..
<ID:0/020> MLO
<ID:0/020> NAND Write Start!!
<ID:0/020> Sbl.bin
<ID:0/020> param.lfs
<ID:0/020> boot.img
<ID:0/020> recovery.img
<ID:0/020> system.img
<ID:0/020> userdata.img
<ID:0/020> modem.bin
<ID:0/020> Transmission Complete..
<ID:0/020> Now Writing.. Please wait about 2 minutes
<ID:0/020> Receive Response form LOKE
<ID:0/020> cache.img
<ID:0/020> hidden.img
<ID:0/020> RQT_CLOSE !!
<ID:0/020> RES OK !!
<ID:0/020> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/020> Removed!!
Just realised bootloader may not be be reqd for this P3100 message during boot is nomore just GTab2...which is OK.
GSM functionality confirmed & this is P3100 working ROM using ODIN.
hello
could you give me your lienpour stock rom? thank you.
edit:it's good I found;-)
Hello,
I just purchased a P3100 here in China, but alas all of the Google apps are inaccessible. Thus, I flashed ClockworkMod Recovery and then the cwm-root-gtab2.zip Root Package. I then loaded the four md5 files into Odin and tried to run them all at once, but it failed. However, if I load and run just the Platform/PDA, then it successfully installs and I get a nice clean install with full access to Google apps. If I tried to run the other three md5 files individually, it also fails. But because I nevertheless have full overall functionality (including my 3G through my SIM card), then I shouldn't worry too much about the other three md5 files failing to install?
Actually, I've just noticed that my total disc space is 1.97GB, 687MB of total RAM, and 1.9GB of device memory. So something is obviously amiss.
Prcls77 said:
Hello,
I just purchased a P3100 here in China, but alas all of the Google apps are inaccessible. Thus, I flashed ClockworkMod Recovery and then the cwm-root-gtab2.zip Root Package. I then loaded the four md5 files into Odin and tried to run them all at once, but it failed. However, if I load and run just the Platform/PDA, then it successfully installs and I get a nice clean install with full access to Google apps. If I tried to run the other three md5 files individually, it also fails. But because I nevertheless have full overall functionality (including my 3G through my SIM card), then I shouldn't worry too much about the other three md5 files failing to install?
Click to expand...
Click to collapse
Prcls77 try flashing Singapore image for P3100 from http://www.sammobile.com/firmware
This single md5 image had PDA & CSC included.
I suggest you wipe data using CWM & wipe all cache , reboot to download mode
Push the Singapore image & let it reboot , check sdcard partition size, if you see size is less, just run the stock factory reset from recovery menu...you should get back your original setting.
thedeamon said:
Prcls77 try flashing Singapore image for P3100 from XlinkX
This single md5 image had PDA & CSC included.
I suggest you wipe data using CWM & wipe all cache , reboot to download mode
Push the Singapore image & let it reboot , check sdcard partition size, if you see size is less, just run the stock factory reset from recovery menu...you should get back your original setting.
Click to expand...
Click to collapse
thedeamon,
I'm currently downloading the Singapore version of 4.04; the file name is P3100XXBLE3_P3100OLBBLE2_XSP.zip (couldn't find 4.03). Is this the one you are referring to? If I unzip this, will it be the single .md5 image you are referring to? If yes, do I load it in Odin as PDA or CSC? Or do I just install the whole .zip file in download mode from my external SD card?
Thank you kindly in advance.
P.
Extract the md5 on a folder in your PC/Laptop, push the file using ODIN 1.85 keeping phone in download mode.
On the same session in ODIN, you may choose to repartition the TAB with correct P3100 pit file from the link below:
http://www.mod2xtreme.com/showthread.php?11722-Download-OPS-amp-PIT-files ( ensure to tick "Re-partition" & load the correct P3100 PIT file )
This will ensure you have a clean factory image loaded in the TAB.
Hope this helps!
Thanks thedaemon!
I wiped data/factory reset and wiped cache through CwM. I then flashed the .md5 file as PDA in Odin along with the pit file. The pit file failed, but the .md5 file was successful and I now have a clean version of 4.0.4. I now have 4.59GB total internal stora space which is certainly better than the 2GB. Overall I'm pretty happy and can l live with this. However, I'm now considering flashing CyanogenMod 9!

Help: My SM-G920F strange display and no flashing after root,

hi
hi,
phone came to me with 5.1.1 latest build of EE-UK
G920FXXU3QOJF_G920FEVR3QOJF_EVR
I root with
S6_UniKernel_v8-0001-ODIN
now download mode give strange issue here are pics
http://www.4shared.com/download/IOp...6ae669f7568a293d60885275688d80d795f&lgfp=3000
http://www.4shared.com/download/E9y...a9b8785cf4e8f45a6d864fc174d5cca195f&lgfp=3000
flashing is also giving error in odin3 v3.10
here are logs of flashing
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920FXXU3QOJF_G920FEVR3QOJF_G920FXXU3COJ2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin engine v(ID:3.1005)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> SingleDownload.
<ID:0/010> sboot.bin
<ID:0/010> NAND Write Start!!
<ID:0/010> cm.bin
<ID:0/010> boot.img
<ID:0/010> recovery.img
<ID:0/010> system.img
<ID:0/010>
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I also try to recover with smart switch emergency recovery but failed, it gives me no emergency code
please suggest me as early possible, phone is brand new and just unbox it,
is it some kernel issue with new build ?
urgent help will be highly appreciated,
thanks regards
About the lights... i don't know what to say, it's strange.
Try to reboot to download mode again (Press Volume Down + Power for about 10 seconds to exit and after the screen goes black, press Volume Down + Home + Power to get into download mode again).
Download an Odin flashable custom recovery (TWRP or PhilZ) and flash it using Odin. In options tab of Odin UNCHECK Auto-Reboot. After installing, exit download mode and when the screen goes black again, press and hold Volume Up + Home + Power. Now you should boot into one of the recoveries you have just installed.
Now, download a custom kernel from XDA (it could be arter97 kernel, Adam kernel or any other) and install it in the recovery.
Now you should be able to boot.
P.S.: To install the custom kernel you have to transfer the file into the device somehow. So, if you install PhilZ, use sideload installation (it is located in the Install zip context in PhilZ) for the kernel zip, and if you choose TWRP, connect the phone to the PC, go to Mounts, disable MTP and then reenable it and your PC should now recognize the phone. Then transfer the kernel zip into internal memory and install.
Villa_Man said:
About the lights... i don't know what to say, it's strange.
Try to reboot to download mode again (Press Volume Down + Power for about 10 seconds to exit and after the screen goes black, press Volume Down + Home + Power to get into download mode again).
Download an Odin flashable custom recovery (TWRP or PhilZ) and flash it using Odin. In options tab of Odin UNCHECK Auto-Reboot. After installing, exit download mode and when the screen goes black again, press and hold Volume Up + Home + Power. Now you should boot into one of the recoveries you have just installed.
Now, download a custom kernel from XDA (it could be arter97 kernel, Adam kernel or any other) and install it in the recovery.
Now you should be able to boot.
P.S.: To install the custom kernel you have to transfer the file into the device somehow. So, if you install PhilZ, use sideload installation (it is located in the Install zip context in PhilZ) for the kernel zip, and if you choose TWRP, connect the phone to the PC, go to Mounts, disable MTP and then reenable it and your PC should now recognize the phone. Then transfer the kernel zip into internal memory and install.
Click to expand...
Click to collapse
thanks for reply, I appreciate it
I install "twrp-2.8.7.1-zeroflte.img" than power of phone than boot into recovery, At recovery it shows trwp logo than black screen than logo(bootloop) but there is no recovery menu, I noted that color are showing normal when it shows twrp logo not like when it is download mode(good sign) ,
update: I flash stock recovery than instal twrp and result in successfully boot into twrp, when i try to install adam kernel it gives me error
E: Error executing updater binary in zip '/sdcard/sm-g920f_Adam.Kernel.2.0.cwp.zip
E: Error flashing zip '/sdcard/sm-g920f_Adam.Kernel.2.0.cwp.zip
Update partition details
E:unable to mount ' /system'
....done
than i wipe cache, dalvik cache and system , after that adam kernel successfully installed but problem is still there,
here is pic of in twrp , you can see display is normal
http://www.4shared.com/download/Jeh...c96207d729645cbd9ee34776c82af38e95f&lgfp=3000
nsnobel2 said:
thanks for reply, I appreciate it
I install "twrp-2.8.7.1-zeroflte.img" than power of phone than boot into recovery, At recovery it shows trwp logo than black screen than logo(bootloop) but there is no recovery menu, I noted that color are showing normal when it shows twrp logo not like when it is download mode(good sign) ,
Click to expand...
Click to collapse
Don't use the .img. Install the .tar.md5 of TWRP 2.8.7.2. You can download it if you search for zeroflte on www.twrp.me (devices).
Or you can try arter97's PhilZ Touch Recovery in .tar format.
Thanks villa for your suggestion, I update my 2nd post , pls read and suggest me
nsnobel2 said:
Thanks villa for your suggestion, I update my 2nd post , pls read and suggest me
Click to expand...
Click to collapse
Hmm, I guess the system partition was erased even if it failed in Odin.
Install a Custom ROM (like Arrow ROM or Crisscross which you can find at Edge forums) and it should be ok.
The kernel would have worked if you had the system partition intact.
Villa_Man said:
Hmm, I guess the system partition was erased even if it failed in Odin.
Install a Custom ROM (like Arrow ROM or Crisscross which you can find at Edge forums) and it should be ok.
The kernel would have worked if you had the system partition intact.
Click to expand...
Click to collapse
I already start downloading this custom rom,
http://forum.xda-developers.com/galaxy-s6/development/rom-pure-stock-extralite-v1-0-t3232498
hope this will work,
nsnobel2 said:
I already start downloading this custom rom,
http://forum.xda-developers.com/galaxy-s6/development/rom-pure-stock-extralite-v1-0-t3232498
hope this will work,
Click to expand...
Click to collapse
This is good, too.
I hope you will solve the problems.
Villa_Man said:
This is good, too.
I hope you will solve the problems.
Click to expand...
Click to collapse
net was so slow why so I am replying late, I install this file and after reboot phone shows samsung logo than restart
now what should I do?
Does your phone shows the bootanimation or only SAMSUNG GALAXY S6?
Gesendet von meinem SM-G920F mit Tapatalk
justgamer01 said:
Does your phone shows the bootanimation or only SAMSUNG GALAXY S6?
Gesendet von meinem SM-G920F mit Tapatalk
Click to expand...
Click to collapse
yes it shows "Samsng Galaxy S6 powered by android" and a red line upper left corner " Kernel is not seandroid enforcing"
here is pic you can see some blur
http://www.4shared.com/download/vkP...f010f2355f11851cda264c7acf955eab95f&lgfp=3000
nsnobel2 said:
net was so slow why so I am replying late, I install this file and after reboot phone shows samsung logo than restart
now what should I do?
Click to expand...
Click to collapse
Did you wipe the Cache, Data and System before installing the file?
EDIT: After seeing the last image, I suggest reinstalling the bootloader. Something is not right with those lights.
https://drive.google.com/folderview...sharing&tid=0B40ItdHKfkyQd1hJQXVDU3dDU2c#list
Download this firmware. Before installing it with Odin, go in TWRP and wipe Cache, Dalvik Cache, Data and System. And then close the recovery mode and enter download mode. Be sure to use the latest version of Odin which is 3.10.7 (you can download it here: http://forum.xda-developers.com/attachment.php?attachmentid=3446301&d=1440131361). After checking is everything is set up, put all the files provided in the zip into the correct place and start the operation. And a note, to be sure it will be alright, put the phone on a table or something while doing the operations and do not move the cable while it installs in Odin, it might give you a fail.
P.S.: If at the end it will give you an error at installing the modem, do not panic, restart download mode and install only the CP file which contains modem.bin.
Villa_Man said:
Did you wipe the Cache, Data and System before installing the file?
Click to expand...
Click to collapse
I did not but it ask for during flash the rom,
Dont know what happened but suddenly phone starts and go to main menu, it is normal but when I start the phone same error occurs, no normal start with splash screen and same strange screen in download mode
nsnobel2 said:
I did not but it ask for during flash the rom,
Dont know what happened but suddenly phone starts and go to main menu, it is normal but when I start the phone same error occurs, no normal start with splash screen and same strange screen in download mode
Click to expand...
Click to collapse
I edited my last post, look at the words I added.
Villa_Man said:
Did you wipe the Cache, Data and System before installing the file?
EDIT: After seeing the last image, I suggest reinstalling the bootloader. Something is not right with those lights.
https://drive.google.com/folderview...sharing&tid=0B40ItdHKfkyQd1hJQXVDU3dDU2c#list
Download this firmware. Before installing it with Odin, go in TWRP and wipe Cache, Dalvik Cache, Data and System. And then close the recovery mode and enter download mode. Be sure to use the latest version of Odin which is 3.10.7 (you can download it here: http://forum.xda-developers.com/attachment.php?attachmentid=3446301&d=1440131361). After checking is everything is set up, put all the files provided in the zip into the correct place and start the operation. And a note, to be sure it will be alright, put the phone on a table or something while doing the operations and do not move the cable while it installs in Odin, it might give you a fail.
P.S.: If at the end it will give you an error at installing the modem, do not panic, restart download mode and install only the CP file which contains modem.bin.
Click to expand...
Click to collapse
I have this file in my pc
G920FXXU3COI9_G920FBTU3COJ1_G920FXXU3COI9_HOME.tar.md5
but it is only 1 file not 3 or 4 files including bootloader file? is you file consists of 4 files? and should i use pit file too?
Deleted
System.img cannot complete flash it gives error, flashing stuck here almost 3-4 minutes than failed, here is pic
http://www.4shared.com/download/iCK...10754c07a4a514e5830f94c352d25d5595f&lgfp=3000
I did not use pit file , should I?
update: Just flash csc file and than flash all 4 files again and result was same as you told me that at the end it will give error at installing modem here are logs
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin engine v(ID:3.1100)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Set PIT file..
<ID:0/010> DO NOT TURN OFF TARGET!!
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> SingleDownload.
<ID:0/010> sboot.bin
<ID:0/010> NAND Write Start!!
<ID:0/010> param.bin
<ID:0/010> cm.bin
<ID:0/010> boot.img
<ID:0/010> recovery.img
<ID:0/010> system.img
<ID:0/010> modem.bin
<ID:0/010> Transmission Complete..
<ID:0/010> Now Writing.. Please wait about 2 minutes
<ID:0/010> FAIL!
<ID:0/010>
<ID:0/010> Receive Response from boot-loader
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/010> Removed!!
Click to expand...
Click to collapse
later I install cp file but still failed here are logs
<ID:0/010> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin engine v(ID:3.1100)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> SingleDownload.
<ID:0/010> modem.bin
<ID:0/010> NAND Write Start!!
<ID:0/010> Transmission Complete..
<ID:0/010> Now Writing.. Please wait about 2 minutes
<ID:0/010> FAIL!
<ID:0/010>
<ID:0/010> Receive Response from boot-loader
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
now at phone startup following message shows with yellow triangle
" An error has occurred while updating the device software us the Emergency recovery function in the Smart Switch PC software"
nsnobel2 said:
now at phone startup following message shows with yellow triangle
" An error has occurred while updating the device software us the Emergency recovery function in the Smart Switch PC software"
Click to expand...
Click to collapse
There must be a way to install the modem...
Try to extract the modem.bin from the CP zip and rename it to modem.bin.tar. Try to install it then in the same AP or CP slot in Odin (you can try to install it either on AP or CP and see which one works).
Villa_Man said:
There must be a way to install the modem...
Try to extract the modem.bin from the CP zip and rename it to modem.bin.tar. Try to install it then in the same AP or CP slot in Odin (you can try to install it either on AP or CP and see which one works).
Click to expand...
Click to collapse
I just install that custom rom again and phone is again in menu , PhoneInfo.apk shows following details of softare
Bootloader version:
G920FXXU3COI9
BASEBAND VERSION
G920FXXU3COJ2
PDA
G920FXXU3QOKX
CSC
G920FOJP3QOL1
if u need any details than tell me pls
nsnobel2 said:
I just install that custom rom again and phone is again in menu , PhoneInfo.apk shows following details of softare
Bootloader version:
G920FXXU3COI9
BASEBAND VERSION
G920FXXU3COJ2
PDA
G920FXXU3QOKX
CSC
G920FOJP3QOL1
if u need any details than tell me pls
Click to expand...
Click to collapse
So now your phone works?
Well if now everything is ok, I guess I don't need anything more.

Galaxy s6 sboot.bin error Odin (Softbricked)

I Tried multiple times to flash with odin but never with success, allays with the same error:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin engine v(ID:3.1203)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> SingleDownload.
<ID:0/010> sboot.bin
<ID:0/010> FAIL!
<ID:0/010>
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Help would be appreciated.
Continue to try with diferent versions of sw. Also do try to instal twrp thru odin and see if that makes it boot
Have you tried to select nand erase all or bootloader update?
Until you have a successful flash do not try to select nand erase all or efs clear!
You could try bootloader update
lenovot said:
Continue to try with diferent versions of sw. Also do try to instal twrp thru odin and see if that makes it boot
Have you tried to select nand erase all or bootloader update?
Until you have a successful flash do not try to select nand erase all or efs clear!
You could try bootloader update
Click to expand...
Click to collapse
Thanks for helping me.
I tried flashing it with twrp it gave me a PASS, but after that it booted to the samsung logo kept showing that. So stuck in boot logo.
I tried to boot ones with the Samsung animation boot screen. but after that it showed the Samsung boot loop again.
I have not use nand erase or bootloader update. But I have use The BL option when selecting a firmware, that may screwed it up.
[UPDATE] It works again!, well kinda .... I have no touchscreen input anymore haha well atleast one step closer
Try to find your region using the serial number on the back of the phone or your imei. After that download and flash the sw from that region if it boots but you still dont have touch imput, flash twrp again and see if that has a touch imput if does do a full backup, boot, system efs etc and save it as is by otg on a stick or on your pc.
if you get touch in twrp you could also try to flash a custom rom and see if that helps. Something like samstock.
lenovot said:
Try to find your region using the serial number on the back of the phone or your imei. After that download and flash the sw from that region if it boots but you still dont have touch imput, flash twrp again and see if that has a touch imput if does do a full backup, boot, system efs etc and save it as is by otg on a stick or on your pc.
if you get touch in twrp you could also try to flash a custom rom and see if that helps. Something like samstock.
Click to expand...
Click to collapse
I have tried the factory reset option and now it just shows the boologo again, (invinite loop and the rtwp does not seem to fix it this time)
I have downloaded the https://updato.com/firmware-archive-select-model?record=6BE751A3C8BA11E69215FA163EE8F90B version
but my phone region was united emirates, and that does not seem to add up with the firmware...
I keep getting the same odin error and I am about to break the thing in 2
What should I do?
Have you tried smartswitch? At first if it doesn't connect try to install smartswitch on the phone. Install it on the phone and after that on your pc and see if it gives you an update
lenovot said:
Have you tried smartswitch? At first if it doesn't connect try to install smartswitch on the phone. Install it on the phone and after that on your pc and see if it gives you an update
Click to expand...
Click to collapse
Yeah tried that did not work the device is not showing in the list of recovery devices, can't install anything on the phone anymore, because it stuck in bootloop.
Use samfirmware to find your fw, nougat eventually and flash it. If you have made a backup of your efs do try to make a repit. Be careful to use the pit file for your sw. You can try to repit it even with a diferent fw as long as they all match. Get the fw from samfirmware and find the pit for it flash it with nand erase all bootloader update after that if it boots and it.s ok then ok if not flash twrp, restore efs and flash again the fw normal without pit bl update and nand erase. This is what i did with mine when i was trying to brand it to a network.

S6 stuck on Samsung logo screen; Recovery mode = no, Odin mode = yes

I've got a Samsung Galaxy S6 (SM-G920F) which stucks on the Samsung logo screen after booting (Samsung Galaxy S6 powered by Android). I got it from a friend, he doesn't know what happened. Knox wasn't affected so it was just stock.
First I thought it was a dead battery because the phone didn't do anything. Only when the charger was connected, it would show a charging empty battery but no percentage. But after a hour in the charger I could boot into the Samsung logo where it get stuck (still no battery percentage however). I can also boot into download/odin mode. But I can't boot into recovery.
I already tried to flash the latest firmware for the S6 (PHN Netherlands G920FXXU6ERF5 https://www.sammobile.com/firmwares/galaxy-s6/SM-G920F/PHN/download/G920FXXU6ERF5/226355/) but that didn't help. It still doesn't boot and I still can't boot into recovery. Should I use some other options in Odin?
I also tried to flash TWRP, but even then I can't boot into recovery.
Flashing both stock firmware and TWRP give no error in Odin.
I found this guide:
https://forum.xda-developers.com/galaxy-s6/help/guide-downgrade-sm-g920f-nougat-to-t3639253
I want to try this, but I already get stuck in step 5.
5. Open SkipSoft Android Tool Kit and wait until you see the main menu. Then go to the installation folder of this tool and you should see an "INPUT" folder. Copy ONLY the boot.img, cache.img, recovery.img and system.img into that folder.
Click to expand...
Click to collapse
When I go to the installation folder (I'm not on the computer right now, something in C:\Program Files\nameofprogram ) there is no INPUT folder.
And in step 6, on my screen there is no option for 99. I got something like this: (picture is from google, not exactly what I got. But almost the same)
{
"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"
}
So I don't know what these steps do. Can't I just make the flashable file with winrar or 7zip or something?
Are there other options I can try? What can cause this behavior? Is it a faulty bootloader? If so, can't I just reflash just the bootloader?
Maybe I should try to flash 5.0.2 or 5.1.1, but I can't find these files on sammobile and updato.com. I found the original url to sammobile but those aren't working anymore:
5.0.2: G920FXXU1AOE3 G920FPHN1AODQ PHN
http://www.sammobile.com/firmwares/download/47427/G920FXXU1AOE3_G920FPHN1AODQ_PHN/
5.1.1: G920FXXU2BOGB G920FPHN2BOG8 PHN
http://www.sammobile.com/firmwares/download/52406/G920FXXU2BOGB_G920FPHN2BOG8_PHN/
Or can someone help me to get the 5.0.2 and/or 5.1.1 files for the G920F?
Typing 99 in the menu worked for me. Even though I also didn't see the corresponding option. It seems to be an update command, downloading the latest packages of adb, adb-fastboot and magisk.
Can you verify that you tried starting recovery mode IMMEDIATELY after flashing the TWRP? The original system seemed to override any changes, if you give it the chance to reboot normally.
Yes I tried TWRP with auto-reboot in Odin and immediately press VOL_UP+POWER+HOME after auto reboot. And TWRP with auto-reboot unchecked. So flash TWRP, force reboot with VOL_DOWN+POWER+HOME switch to VOL_UP+POWER+HOME before the Samsung logo appears. Bot both methods won't let me boot into recovery.
When I try to flash this rom:
G920FXXU3DPBG_G920FPHN3DPB2_PHN
I get this error in Odin (tried v3.10.6 and v3.12.4_4)
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920FXXU3DPBG_G920FPHN3DPB2_G920FXXU3DPB6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img
<ID:0/004> cm.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Why?
Phone says:
Code:
[CM] SW REV. CHECK FAIL. DEVICE: 6, BINARY: 3
Hi,
Were you able to figure out what the issue was? I'm in the exact same situation and have tried similar things with no success. I've kind of given up on it being a software issue at this point..
Nope, I'm going to sell it for parts.
Markos said:
Nope, I'm going to sell it for parts.
Click to expand...
Click to collapse
This happened to me after trying to get unstuck from a bootloop. I think I solved it by flashing it again a couple more times. And I remember it taking quit a while to actually boot up when it finally did.
I already flashed it a lot of times. Both original firmware as TWRP. Nothing helped.
I wanted to try early stock rom but can't find downloads
Markos said:
Or can someone help me to get the 5.0.2 and/or 5.1.1 files for the G920F?
Click to expand...
Click to collapse
I just want to suggest the SamMobile. Hahaha.
heidisteen said:
I just want to suggest the SamMobile. Hahaha.
Click to expand...
Click to collapse
As I said, they don't have it anymore
Markos said:
As I said, they don't have it anymore
https://youtu.be/zXSHe3oorIM
Click to expand...
Click to collapse
I found a video about fixing Samsung Galaxy Android system issues, sound helpful with you.

Help, I messed up! [Samsung SM-P905 UK version]

Have a Note Pro 12.2. Was wanting to install Lineage 16.0 OS on it.
Went into recovery and did a wipe/install.
Was able to root it using Odin.
Downloaded the Lineage files onto an SD card
Downloaded TWRP on the tablet with Google Play
Flashed the boot.img file to recovery
When I try to reboot into recovery, I get a Set Warranty Bit : Recovery on the startup screen and it just hangs there
I think I did originally backup the recovery file, but I cant seem to find it now. Its not on the SD card for the device where I thought it was.
Weirdly,
Booting regularly gets me the same screen
Booting into recovery gets me this screen (obviously)
Booting into bootloader gets me this screen too
I can't seem to power it down either, all key options just seem to loop back to the
bad recovery message.
It no longer 'connects' via USB to my computer either.
Can anyone please help me try to get this back? I can provide any additional info as well.
Im currently trying to find the original firmware for this device, but I haven't been very successful yet.
I would be very grateful for any information or links or help you could offer.
Thank you.
I opened the back just now to pull the battery.
When I replace it, and turn it back on, it goes to the same screen.
You're the second this year to post this problem, and nobody seems to have a fix.
Was thinking of putting a custom rom on mine, but this has put me off that idea.
Revert back to stock
To get your tablet back to a running state and revert everything back to stock, you'll want to use one of these two stock firmwares from the Sammobile site. I picked these two out based on the fact that you said you had a UK device. The firmware in the first link is from 2017, while the second link contains a firmware from 2016.
Personally, I have had no luck getting any of the recent firmware from any of the regions to install on my SM-P905 through ODIN; I get errors about partition sizes. However, installing older firmware from other regions works just fine. Try either of the two links and if the latest one for UK doesn't work, try the other one.
From 2017: https://www.sammobile.com/firmwares/galaxy-note-pro/SM-P905/BTU/download/P905XXSABQC1/127655/
From 2016: https://www.sammobile.com/firmwares/galaxy-note-pro/SM-P905/BTU/download/P905XXUABPG4/89307/
A successful installation of the firmware will reset your bootloader, recovery, and rom back to stock Lollipop. You will be able to use your tablet at that point, although give it a good long time to boot the very first time. This will give you a clean slate to try and install Lineage 16, or any other rom of your choice.
Thanks for the info, Shardsx, I'm downloading them now.
OK, an update.
I let the device power down completely on the Set Warranty Bit : Recovery screen until it died.
I then plugged the tablet into the usb on my desktop, and I was able to press power and the vol down (Recovery screen? It says Odin mode) again, but I havent been able to do much with it through Odin or Kies programs for reflashing the firmware.
If I press power and vol up, I get the same Set Warranty Bit : Recovery screen.
ricosuave95 said:
OK, an update.
I let the device power down completely on the Set Warranty Bit : Recovery screen until it died.
I then plugged the tablet into the usb on my desktop, and I was able to press power and the vol down (Recovery screen? It says Odin mode) again, but I havent been able to do much with it through Odin or Kies programs for reflashing the firmware.
If I press power and vol up, I get the same Set Warranty Bit : Recovery screen.
Click to expand...
Click to collapse
Please elaborate a little on why you haven't been able to do much with it through Odin. In your first step, you said you let the device power down completely until it died, which makes it sound like you drained the battery. You'll want plenty of battery power for this process, so charge your device up. It sounds like you do know how to get into Download/Odin mode, so I won't ask about that. Instead, tell us a little bit more about what you're doing in Odin. Are you loading the firmware using the AP button? Which of the two files are you trying to load? Are you unzipping the firmware file first so that you're flashing the *.tar.md5 file? Are you waiting the appropriate amount of time for the firmware to unpack within Odin before attempting to flash anything? (This step takes a long time too) Are you able to successfully start the firmware upload? What results are you getting? Are you leaving the Odin options as stock when you do this?
I havent had much time to work on it.
Once I do, I'll post and update to it, and your questions.
Thanks
OK, so initially, I let the device die down so that there was nothing left on the battery - I was unable to shut it off. When it would reboot, it always gave me that same Set Warranty Bit : Recovery screen.
I charged it completely, and was able to boot into the download mode, but initially, I couldnt get it to register when I plugged into the USB.
Here is what the recovery/download mode said...
Product Name: Samsing SM-P905
Current Binary: Samsung Official
System Status: Custom
Knox Warranty: Void 0x1 (0)
Qualcomm Secureboot: Enable (CSB)
RP Swerv: S1, T1, R1, A1, P1
Secure Download: Enable
UDC Start
After a few reboots, it did though, and Odin was able to see it.
When I ran Odin, with both firmwares, they both gave me the Invalid EXT4 Image error... I then read online that I probably needed to reflash the PIT file for it.
I tried but was unsuccessful in reading mine off the device using a couple of tools., but I did find one in this thread that I tried... https://forum.xda-developers.com/showthread.php?t=2758925
It didnt seem to work.
I rebooted the device a couple of times, and with one of the firmwares above, it would fail almost immediately with the same EXT4 error, saying something about the volume size being different (40960 vs 204800 ish), the second one, however, seemed to carry on further, almost 3/4 the way through the process before it failed with the same (volume size too big). I think that the PIT I used was incorrect, which is why I was asking for my specific one in another thread. I cant seem to find hardly any PITs for this device.
I also tried using Kies, as after one reboot, it said on screen to use it to recover firmware, but while it did connect to PC via USB, Kies did not detect it, either before the PIT and after.
Heres the Odin error mesage for the second firmware that lasted a while...
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1101)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> modem.bin
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> FAIL! (Ext4)
<ID:0/003>
<ID:0/003> Complete (Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And the first firmware that failed immediately:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1101)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> boot.img
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> FAIL! (Ext4)
<ID:0/003>
<ID:0/003> Complete (Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks to the help from nowheretohide and shardsx, I was able to get my tablet restored to factory... Used Odin and the file provided here:
https://forum.xda-developers.com/showthread.php?t=2758925&page=2
Now, because I obviously messed it up so bad the first time, and am now gun shy, can anyone help me install Lineage 16.0 with a step by step?
ricosuave95 said:
Thanks to the help from nowheretohide and shardsx, I was able to get my tablet restored to factory...
Now, because I obviously messed it up so bad the first time, and am now gun shy, can anyone help me install Lineage 16.0 with a step by step?
Click to expand...
Click to collapse
Don't be gun-shy. You now have almost all the tools to recover from similar issues in the future.
I'm using Odin 3.11 for these instructions. Assumptions I'm making is that you have already downloaded a working version of TWRP for this tablet (remember, the absolute latest versions on the official TWRP site are not compatible with our tablets. Go through the TWRP site and look at the compatibility page for our tablet, or use Valera's custom TWRP).
Step 1: Charge up that tablet.
Step 2: Get into Download mode.
Step 3: Open up Odin. Leave options as default. The one you should really double-check is to make sure that "Re-Partition" is not checked or enabled.
Step 4: Click the AP button and load the TWRP recovery image, and then upload it to your tablet through Odin. Your tablet will reboot automatically reboot. You might as well enter Recovery at this point.
Step 5: I usually store the the ROM images on an external SD card. Inside Recovery, I usually like to do an advanced wipe and wipe out /system /data /cache to . Then, I'll flash the ROM image from the external SD card. After the flash, just reboot the tablet and wait until Android starts up.
I apologize for not providing screenshots. I'm doing this off the top of my head but generally that's what I do to load new ROMs.
The above steps will get you a barebones Android. You'll still have to flash Google's stuff on top if you want to go that way, but basically repeat Step 5 but replace it with the recommended Google packages and that should get you set up pretty good.
I think it was the fact that I used a different version of TWRP. Oops.
Will try again using the correct tools now.
Also, I think Ill go with CRdroid - I'd just like to have a speedier tablet with no Samsung bloatware and maybe a little better battery life, since I replaced the batteries not long ago.
Thank you all!
Got it running with CRdroid, was a little laggier than I liked and some apps were crashing...
Tried lineage 16.0 and found it much better.

Categories

Resources