Database Info

[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!

[Completed] sm-g870a root attempt / stuck in android recovery

Hello everyone,
First of all I would just like to thank everyone and anyone in advance for any help at all they can give me. I would also like to says thanks for this awesome community with all this great information you all share! I am certain there are probably thousands of others who have asked for help with a very similar situation. Through all my research these SM-G870A phones seem to be a bit more problematic than most and less common as well, so I decided to open up a thread in hopes this will help more than just myself someday.
I attempted to root my Samsung galaxy S5 active AT&T (SM-G870A) last night and I have gotten in over my head on this one. I am a novice root android user obviously. I attempted to follow this guide from muniz_ri:
https://forum.xda-developers.com/at...to-root-g870aucu1aoa1-4-4-4-2-7-2015-t3025119
I think his guide is great, but it was the wrong one for me since I didn't already have root.
I didn't take my time and do enough research before attempting this and I know better than to do stupid things like that I really do. My phone has the OTA firmware 6.0.1 on it, so I don't think I should have tried to gain root access in this way unfortunately for me. I completed the first 4 steps and odin successfully completed flashing the G870A_NE4_Stock_Kernel, but now all my phone will do is boot up into android recovery over and over again. I believe this is referred to as boot looping.
I have tried wipe data/factory reset/reboot and I have tried wipe cache partition followed by rebooting with no luck. No matter what I seem to attempt I just get booted right back into android recovery.
I have done alot of reading all over the web, but mostly here at XDA and at this point I am lost about what I should do to recover my phone back to working condition. I would be satisfied just having my phone back with root or no root at this point. I think it is just boot looping from what I understand. I have searched everywhere for an original copy of the 6.0.1 firmware so I could flash it back with Odin, but no luck so far. It was really stupid of me not to make some kind of copy of my firmware and stuff first before trying this. I do have one thing that might help me, but I am not sure. I have a backup of my phone made using Samsung smart switch software on my SD which I copied over to my computer. I am going to continue researching and attempting to fix my phone anyway I can, if anyone would be willing to help me in any sort of way I would greatly appreciate that so much! If there is anymore information you would like me to provide please just ask!
It looks like some others having similar issues on their Samsung galaxy phones were able to resolve them by flashing the correct cf auto root file. I checked for a file on the cf auto root site that might work for my phone, but they don't have (SM-G870A) available. I did however find SM-G870W for 6.0.1 here
Here is the Odin log from the CF Auto Root attempt:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-kltecanactive-kltevlactive-smg870w.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> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
Its not super clear, but here is what my phone shows after attempting CF Auto Root (SM-G870W) on my (SM-G870A) phone in download odin mode.
{
"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"
}
After further researching apparently this CF auto Root (SM-G870W) file wont work for my (SM-G870A) phone, because my build number is different. Here is all the info for the current OTA firmware installed on my phone.
Jan. 12, 2017 •What's new: Android device security updates
•Android version: 6.0.1
•Security patch level (SPL): December 1, 2016
•Baseband version: G870AUCS2DPK3
•Kernel version: 3.4.0-9723602
•Build number: MMB29M.G870AUCS2DPK3
•File size: 27.7MB
•Previous versions required: G870AUCU2DPK2

Update:
After many hours of reading and researching the web, I now have a better understanding of root, roms, firmwares etc.. which is great! I was able to find and save alot of info and files for the sm-g870a! What finally saved me from default booting into recovery mode was an excellent post here on XDA by AptLogic that I am thankful for! If you find yourself on the journey for knowledge that I am currently on then I hope my beginners post helps you in some way! You can find Aptlogic's post about how to downgrade Marshmallow 6 back to Lollipop 5 right here. It completely solved my problem! It is exactly what I have spent hours and hours looking for!
Good Luck Guys!

galaxy j7 2016 SM-J710FN PROBLEM

Hi guys , good evening to all of you.
i have galaxy j7 sm-j710fn , the phone keep rebooting after ( samsung galaxy j7 (6) powered by android ) then few seconds and the phone restart again.
i tried to flash stock firmware by using odin , os 6.0.1 , everything is okay , flash done , but the same problem "" phone keep restarting ""
i when i try to access to stock recovery , a blue screen with a droid , and under the droid thing , it says : installing system update then Eraze ... then installing system update then Eraze , forever
i said , why i didn't install custom recovery , so i installed TWRP
when i try to wipe dalvik and cach and system or data a page of errors show's up
{
"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"
}
when go to mount it looks like all things are not mounted !!!!!!!!!!! thats why recovery can't spot the storage
help guys , what should i do ?

Maybe eMMC/Pit File problem
I no Nothing about this
So Wait for an expert

qounik said:
Maybe eMMC/Pit File problem
I no Nothing about this
So Wait for an expert
Click to expand...
Click to collapse
yes , i think its PIT FILE
but i did not find firmware with pit file for my phone

HACKIMTOSH said:
yes , i think its PIT FILE
but i did not find firmware with pit file for my phone
Click to expand...
Click to collapse
Search deep in Google
Maybe your luck will favour You
I once found Pit for my GT9192

qounik said:
Search deep in Google
Maybe your luck will favour You
I once found Pit for my GT9192
Click to expand...
Click to collapse
yeah, i'm trying so hard to find the pit file but the problem is samsung mobiles names are so closed to each other , even google goes crazy

help please anyone ? i'm trying but nothing

ODIN LOG
<ID:0/006> 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/006> Odin engine v(ID:3.1203)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> cm.bin
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

I managed to something similar to my phone a while back. Only solution that i found was restoring the phone using Samsung Smart Switch app on PC. There are a few stepts the app tells you to do, after that it flashes the stock firmware, modem, recovery...evrything.

sesamo said:
I managed to something similar to my phone a while back. Only solution that i found was restoring the phone using Samsung Smart Switch app on PC. There are a few stepts the app tells you to do, after that it flashes the stock firmware, modem, recovery...evrything.
Click to expand...
Click to collapse
i tried it before ......... smart switch restore the phone and no error during Procedure
when the phone reboot , boom........same problem....keeep restarting
i need PIT file for this phone , anyone ?

Looks like you've flashed the wrong recovery to me.

ashyx said:
Looks like you've flashed the wrong recovery to me.
Click to expand...
Click to collapse
Don't we have only one recovery??? That official one TWRP?

qounik said:
Don't we have only one recovery??? That official one TWRP?
Click to expand...
Click to collapse
Is your device a J7 or ON8?
Please post the full specs of your device from the device itself.

Bravoo do not work......Why break the device?

Not sure what kind, but my N8010 is bricked.

I picked up a 2nd hand n8010 a LONG while back, back when they were still relevant.
I had been using it peacefully, on all stock software the way i got it, and had upgraded my phone, so i left it off for a long while, about a year or two now. Just yesterday, I decided to fully charge and open it. So far so good.
Then the bootlogo shows up. It started looping, black screen, wait a bit, back to logo until battery dies.
I decided to leave it be for a bit charged. Still nothing, so i decided to enter recovery mode, but nothing happened. The backlight DOES flash for a second or two, but then it's back to the bootlogo shenanigans.
Now i have noticed after fully charging the device, it just stays stuck on the bootlogo, without flashing or looping. It is open right now.
I tried to flash TWRP 2.8.6.0 for GT-N8010, log says it succeeded, but there is nothing:
Code:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1205)..
<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> recovery.img
<ID:0/003> efs.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
<ID:0/004> Added!!
I tried to flash a stock rom. It was a turkish N8010, So i picked up TUR-N8010XXUCMG1-2013101145051. Here is the failed repartition log:
Code:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1205)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have also tried to reflash a PIT file. Same repartition fail error. Weird thing to note is that while the device IS a 8010, the Odin Mode shows N8005 but i have no clue why.
One more thing to note: not booting to anything for ~5 minutes makes windows prepare SAMSUNG Device drivers, and shows on Device Manager as an MTP device.
Other than that I have tried
Flashing the following roms for diversity: XSG-N8010XXUDNF3-20141017163909 & N8010XXUCMK2 (no date)
Flashing I9300_Repair_efs.tar
Using device's own PIT, and the infamous Note10_PIT.zip copy from a N8000
Using Odin 3.12, 3.14.1 and 3.13.1, and trying all of the above reflash steps with each version
I'm okay with wiping everything, I have 0 important data left in it.
If i missed anything please ask, i will reply as soon as possible! I want to know how to solve if possible, or if my nand is gone

Fail on PIT often wrong size 16gb / 32 gb firmware used .

JJEgan said:
Fail on PIT often wrong size 16gb / 32 gb firmware used .
Click to expand...
Click to collapse
So i should find firmware for my 16gb model?
Recovery doesnt flash either, it just does RQT_CLOSE and takes 00:01 second to flash so it isnt actually flashing... When i reboot into recovery it goes black screen as i mentioned
I'll try look for firmware for my particular model, thank you

UPDATE: I found another pit. its for n8010 16gb, still the same PIT error.
I also tried TUR N8010XXUDNF3_N8010OJVDNF3-20140614 which is also tz.img fail.
I tried all of the above again with Odin 3.09, also same result except for TWRP.
TWRP now "flashes" and takes time to flash, like it's supposed to be. But booting to recovery still is a black backlight.

which is also tz.img f
You flash TAR through Odin not IMAGE .

JJEgan said:
which is also tz.img f
You flash TAR through Odin not IMAGE .
Click to expand...
Click to collapse
But i am, i am flashing .tar.md5, i do not extract. The log just shows tz.img before failing.
{
"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"
}
If you mean .tar.gz, i also tried renaming and it outright didnt work.
I never extract .tar files while flashing, unless if its twrp.

Are you using the Original Samsung USB cable you should .
You could find Philz Recovery on here flash that and then use it to update to TWRP .

Hello, i have 2 original cables. One that came with the box and one that i bought off of an official samsung store. Just in case the one i purchased was problematic, I found the one that came with the box, and tried it.
The issue persisted, so i do not think i have a problem there.
I did get a version of philz recovery and try to flash it, but it was the same was TWRP. Flashed as normal, I went to recovery, it gave black screen for 1-2 seconds, reboot.
I'm starting to believe I have a hardware failure. I dont think it would flash and still not work if it werent broken.
Thanks for sticking with me. If you have any more suggestions i am willing to try. But worse come to worse i will replace the motherboard and try an emmc replacement on the dead board as practice.
Just one question: Is it possible that i could trick the bootloader to booting from ExtSD? Maybe if EMMC is dead, i could boot from my 8gb microsd.

Bad emmc usually posts in Odin as Nand fail .

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

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 ?