Related
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!
Has anyone figured out how to repair this error yet??? i've spent 4 days reading forums and google and whatnot and still i cant get this problem fixed. either solutions are for i9000 and not for infuse so procedures and roms are different. those who have infuse have not solved this error so i have no steps to follow. i've flashed like 7 different roms (some stock some modded) and nothing! i'm at my wits end i've been on and off on fixing this phone since 2013..... and anyone help me figure this out?? i'll answer all questions asap!
marielacvn said:
Has anyone figured out how to repair this error yet??? i've spent 4 days reading forums and google and whatnot and still i cant get this problem fixed. either solutions are for i9000 and not for infuse so procedures and roms are different. those who have infuse have not solved this error so i have no steps to follow. i've flashed like 7 different roms (some stock some modded) and nothing! i'm at my wits end i've been on and off on fixing this phone since 2013..... and anyone help me figure this out?? i'll answer all questions asap!
Click to expand...
Click to collapse
What's the consequence of this error? What are you doing when this error comes up? Any other messages?
I remember this one popping up before while flashing and it not meaning anything. Everything flashed fine. Mind you, this may have been with my primary phone, I cannot remember.
This Infuse thread may be of some help (or not, let me know):
http://forum.xda-developers.com/showthread.php?t=1581977
joel.maxuel said:
What's the consequence of this error? What are you doing when this error comes up? Any other messages?
I remember this one popping up before while flashing and it not meaning anything. Everything flashed fine. Mind you, this may have been with my primary phone, I cannot remember.
This Infuse thread may be of some help (or not, let me know):
http://forum.xda-developers.com/showthread.php?t=1581977
Click to expand...
Click to collapse
Consequence of the error is odd... I plugged my phone one night and left it charging in the morning the phone was off... When I wanted to turn it back on I got this error. This is not the only error.... I get another one E:copy_dbdata_media:Can't mount SDCARD
As for the link I've read that thread over and over and it was of no help because I did everything he did and still no results
marielacvn said:
Consequence of the error is odd... I plugged my phone one night and left it charging in the morning the phone was off... When I wanted to turn it back on I got this error. This is not the only error.... I get another one E:copy_dbdata_media:Can't mount SDCARD
As for the link I've read that thread over and over and it was of no help because I did everything he did and still no results
Click to expand...
Click to collapse
Sounds like a hardware error. Are you able to go into download mode? How about recovery? Do you have CWM, TWRP, or stock recovery? If you have the first two are you able to make and restore backups, and otherwise access the SD cards?
Finally, are you running stock, or a custom ROM? I see you mentioned earlier that you switched ROM's so even if it's happening with stock, then it's becoming less of a software issue in my thoughts. But if you have full access in recovery, then that would squash those thoughts. At that point, I would try to find a working ROM.
joel.maxuel said:
Sounds like a hardware error. Are you able to go into download mode? How about recovery? Do you have CWM, TWRP, or stock recovery? If you have the first two are you able to make and restore backups, and otherwise access the SD cards?
Finally, are you running stock, or a custom ROM? I see you mentioned earlier that you switched ROM's so even if it's happening with stock, then it's becoming less of a software issue in my thoughts. But if you have full access in recovery, then that would squash those thoughts. At that point, I would try to find a working ROM.
Click to expand...
Click to collapse
Yes I can go into Download mode and I'm able to flash successfully it just won't reboot afterwards.... It gives me the errors. The only recovery I can go into is the stock Android blue text menu. My phone is rooted and before this error I had cwm... After the error and trying to flash and recover I can't access cwm. I've tried gtgs unbrick stock rom, entopy's kernel, a couple of modded roms like aeon or legend and nothing I get the same results... Same error. But all flash successfully. Right now I'm in stock GB rom
marielacvn said:
Yes I can go into Download mode and I'm able to flash successfully it just won't reboot afterwards.... It gives me the errors. The only recovery I can go into is the stock Android blue text menu. My phone is rooted and before this error I had cwm... After the error and trying to flash and recover I can't access cwm. I've tried gtgs unbrick stock rom, entopy's kernel, a couple of modded roms like aeon or legend and nothing I get the same results... Same error. But all flash successfully. Right now I'm in stock GB rom
Click to expand...
Click to collapse
If you don't have ClockWorkMod I am assuming you are flashing all your ROMs through download mode. I thought that only stock ROMs were available for that. I learn something new everyday.
Anyways, it may be that Download mode is silently getting the write error when it comes to that partition. Did you try putting CWM back on?:
http://forum.xda-developers.com/showthread.php?t=1107881
I am really curious if you can access your (internal) SD card outside the boot process. If the partition table is shot, there is a process that repartitions everything, which in theory gets everything back to normal. It involved Odin, but I forget what the file was called. Pretty sure it was CWM itself, but I'm not sure (first reboot after installed whatever through Odin, I remember a voice alerting me to please wait while partitions are updated - about 5 minutes). I will have to look it up when I get home.
joel.maxuel said:
If you don't have ClockWorkMod I am assuming you are flashing all your ROMs through download mode. I thought that only stock ROMs were available for that. I learn something new everyday.
Anyways, it may be that Download mode is silently getting the write error when it comes to that partition. Did you try putting CWM back on?:
http://forum.xda-developers.com/showthread.php?t=1107881
I am really curious if you can access your (internal) SD card outside the boot process. If the partition table is shot, there is a process that repartitions everything, which in theory gets everything back to normal. It involved Odin, but I forget what the file was called. Pretty sure it was CWM itself, but I'm not sure (first reboot after installed whatever through Odin, I remember a voice alerting me to please wait while partitions are updated - about 5 minutes). I will have to look it up when I get home.
Click to expand...
Click to collapse
i tried putting cwm in by itself and it stays in starting connection indefinitely....this is when i just put a /tar file in odin under PDA. if i put the whole rom in with pit included and pda and phone files it's successful. this is the report i get after installing a rom with cwm included:
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I997UCLB3-CWM-root-deodex-extras.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I997UCLB3-CWM-root-deodex-extras.tar.md5 is valid.
<OSM> PHONE_UCLB3.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> cache.rfs
<ID:0/004> NAND Write Start!!
<ID:0/004> factoryfs.rfs
<ID:0/004> modem.bin
<ID:0/004> zImage
<ID:0/004> modem.bin
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response form LOKE
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
after my phone reboots i get this message in the screen:
---installing package...
finding update package...
opening update package...
verifying update package...
installing update...\
successfully installed package.
---copying media files----
E: failed to mount/dbdata (file exists)
E:copy_dbdata_media: Can't mount/db data your storage not prepared yet, please use UI menu for format and reboot actions.
media files copy failed.
--wiping cache...
formatting/cache...\
cache wipe failed.
----appling multi-csc...
installing multi-csc
applied the csc-code 'att'
successfully applied multi-csc.
from here i proceed to wipe data/factory reset from the menu.
----wiping data...
formatting/data...
formatting/dbdata...
E: format_volume: rfs format failed on /dev/block/stl10
Deleting meta data
formatting /cache...
data wipe complete.
if i try anything else i get
E:failed to mount/sdcard (file exists)
that's pretty much where i'm at right now....... it seems i have little to no communication with the internal sd card.
marielacvn said:
that's pretty much where i'm at right now....... it seems i have little to no communication with the internal sd card.
Click to expand...
Click to collapse
That's what it's looking like. Your cache partition looks fine, so must be your root partition (or whatever holds kernel and core bootstrap). If it was a desktop computer I would say either the partition table is bunged up or the tail end of the hard drive is inaccessible. I am stumped on how to get to the former. I will look at home for the Odin CWM file I had so you don't have to flash a whole ROM. It may just sit still forever like the CWM install you have (or it may not work at all because mine may be designed for i997R - Rogers kernel), but it's worth a try, since it's the only thing I can think of.
joel.maxuel said:
That's what it's looking like. Your cache partition looks fine, so must be your root partition (or whatever holds kernel and core bootstrap). If it was a desktop computer I would say either the partition table is bunged up or the tail end of the hard drive is inaccessible. I am stumped on how to get to the former. I will look at home for the Odin CWM file I had so you don't have to flash a whole ROM. It may just sit still forever like the CWM install you have (or it may not work at all because mine may be designed for i997R - Rogers kernel), but it's worth a try, since it's the only thing I can think of.
Click to expand...
Click to collapse
I'll pretty much try anything at this point.... Haven't used the phone in almost a year so I'll practically try anything. Kind of a bummer no solution still exists for this.... I'm thinking it might just be a hardware thing either way I'm standing by...
marielacvn said:
I'll pretty much try anything at this point.... Haven't used the phone in almost a year so I'll practically try anything. Kind of a bummer no solution still exists for this.... I'm thinking it might just be a hardware thing either way I'm standing by...
Click to expand...
Click to collapse
This is what I was thinking of:
http://forum.xda-developers.com/showthread.php?t=1197248
You are probably with AT&T so this would be a bad idea. It won't brick your phone, but weirdness occours like soft reboots. So with that in mind, try this link:
http://forum.xda-developers.com/showthread.php?t=1698367
...and download Entropy512's CWM red. If this doesn't load, I don't know where to go next.
joel.maxuel said:
This is what I was thinking of:
http://forum.xda-developers.com/showthread.php?t=1197248
You are probably with AT&T so this would be a bad idea. It won't brick your phone, but weirdness occours like soft reboots. So with that in mind, try this link:
http://forum.xda-developers.com/showthread.php?t=1698367
...and download Entropy512's CWM red. If this doesn't load, I don't know where to go next.
Click to expand...
Click to collapse
first link:
i downloaded Entropy512's Daily Driver / Red CWM Recovery, flashed it and this was the summary i got from odin:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> 2012.04.05-ODIN-Entropy_DD-GB-zImage.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<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> zImage
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
<ID:0/005> Added!!
after reboot i get this error
E:failed to mount /dbdata (invalid argument)
----copying media files...
E:failed to mount /dbdata (file exists)
E:copy_dbdata_media:can't mount /dbdata your storage not prepared yet, please use UI menu for format and reboot actions.
media files copy failed.
i also tried the same for Zen Arcade's Infusion-Z / Red CWM Recovery
2012.05.20-ODIN-Infusion-GB-Zen-CoreA-16.rar
2012.05.20-ODIN-Infusion-GB-Zen-CoreB-14.rar
same results....
as for link 2 and rooting with rogers my results were.....
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> PDA_UXKG3_rooted_no_bootloaders_v2.tar.md5 is invalid.
<OSM> End...
it was a no go.....
Try the Infused Gingerbread kernel one, after putting an AT&T stock rom back on. Guess I should have been more specific, if you were to try the Rogers route. Think it will have the same issue, but the above file is the one I used for CWM.
Sent from my MyTouch 4G Slide using XDA Free mobile app
joel.maxuel said:
Try the Infused Gingerbread kernel one, after putting an AT&T stock rom back on. Guess I should have been more specific, if you were to try the Rogers route. Think it will have the same issue, but the above file is the one I used for CWM.
Sent from my MyTouch 4G Slide using XDA Free mobile app
Click to expand...
Click to collapse
Just did it...same result....i think i'm throwing the towel in.... maybe a year from now i'll come back to it and see if anything has changed... j/k but really i think we gave it a real go. i'm always open to more ideas but for now i think its possibly fried inside... thanks for all the help though!!
No problem. Best of luck!
Sent from my MyTouch 4G Slide using XDA Free mobile app
a bit late on the reply but you might want to use the unbrick / Return to stock method in http://forum.xda-developers.com/showthread.php?t=1705260. I had this issue too trying to install new rom. This should at least get you passed the error onto working phone if it's not hardware malfunction. From there you can install cwm and do whatever. Hope this help.
if your infuse is the AT&T one you can try this as well http://forum.xda-developers.com/showthread.php?t=1524081
Young_Azul said:
if your infuse is the AT&T one you can try this as well http://forum.xda-developers.com/showthread.php?t=1524081
Click to expand...
Click to collapse
I never tried the one click version of it before.. but the normal Heimdall was a bit confusing for me compare to Odin. If I had not use Odin before Heimdall then maybe I would have gotten used to it..
scmfxt said:
I never tried the one click version of it before.. but the normal Heimdall was a bit confusing for me compare to Odin. If I had not use Odin before Heimdall then maybe I would have gotten used to it..
Click to expand...
Click to collapse
normal Heimdall is confusing but the one click isn't confusing if you read what's on the OP but that sad this is that it doesn't have root :/ and what i have noticed is when odin doesn't want to recognize your phone heimdall will....and just to get root and recovery i flashed twice with heimdall second time for the boot loaders...then i flashed through odin for the root with recovery version
marielacvn said:
after my phone reboots i get this message in the screen:
---installing package...
finding update package...
opening update package...
verifying update package...
installing update...\
successfully installed package.
---copying media files----
E: failed to mount/dbdata (file exists)
E:copy_dbdata_media: Can't mount/db data your storage not prepared yet, please use UI menu for format and reboot actions.
media files copy failed.
--wiping cache...
formatting/cache...\
cache wipe failed.
----appling multi-csc...
installing multi-csc
applied the csc-code 'att'
successfully applied multi-csc.
Click to expand...
Click to collapse
I remember fixing this problem by flashing (Odin) a "dbdata.rfs.tar" file from one of these forums. It was long ago so I don't quite remember where it was and what exactly my steps were. As far as my memory goes, I flashed I997UCLB3 via odin and then flashed "dbdata.rfs.tar". That fixed this problem. I will attach the "dbdata.rfs.tar" file on this post, hope you find a solutions :S. Sorry if you have already tried it >.<
driverless said:
I remember fixing this problem by flashing (Odin) a "dbdata.rfs.tar" file from one of these forums. It was long ago so I don't quite remember where it was and what exactly my steps were. As far as my memory goes, I flashed I997UCLB3 via odin and then flashed "dbdata.rfs.tar". That fixed this problem. I will attach the "dbdata.rfs.tar" file on this post, hope you find a solutions :S. Sorry if you have already tried it >.<
Click to expand...
Click to collapse
i've tried it already by decided what the hell i'll give it one last try again.....still nothing i'm now convinced that this is a hardware problem and not software. thanks again for the comment!
Cheers
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.
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.
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 ?