I posted my problem on androidcentral earlier today, I'm not progressing anywhere with my situation, I've copied my original posts with some edits here. If you need more information for helping me to resolve this dilemma, ask right away.
I'm in deep****. It started when i tried changing the fonts on my galaxy s3, simple install and reboot. Now when it rebooted it got stuck on the Metro PCS logo screen, I turned it off and turned it on again, and same problem. Then I tried flashing my g3 with odin it said pass, but now my model number has disappeared from the samsung boot screen and it still has the same problem prior; before it said Samsung Galaxy S3 SGH-T999N, but now it just shows Samsung Galaxy S3. Prior to all this my phone was already rooted. I'm a noob and I need help. All the details I remember about my phone is that the carrier is Metro PCS, the model is SGH-T999N (a t-mobile variant) and the OS was Jellybean 4.1.2.
Thankyou for reading, please reply soon its urgent.
*Extra notes, I tried booting it up into recovery mode it shows splash screen for a brief moment and then completely turns off. It is still able to go in to download mode, also when the phone is completely off and charged in, the battery charging animation is still normal/unchanged before all this happened.
*Additional notes, when in download mode the information at the top left corner reads as:
ODIN MODE
PRODUCT NAME: SGH-T999N
CUSTOM BINARY DOWNLOAD: Yes (3 counts)
CUSTOM BINARY: Custom
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
tookutz said:
It failed to flash, I tried 3 times, here is the log of the 3rd/last attempt with that .tar file.
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVDLJA_T999TMBDLJA_T999UVDLJA_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> aboot.mbn
<ID:0/009> NAND Write Start!!
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<ID:0/009> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
What else can I try? I doubt I'll be able to replace it with the warranty by now.
Click to expand...
Click to collapse
tookutz said:
Isn't that only on verizon's variants? I don't remember anything having to do with the bootloader, but I did successfully root my phone, so maybe I did, I'm not completely sure.
*Edit, Could you also give me a detailed guide as to how I could reset it with Kies? I'm not sure if it will work or not, because in my first postt, if it wasn't clear, I think I used the wrong .tar which made the model number under the samsung boot screen, disappear.
Click to expand...
Click to collapse
tookutz said:
I'm still stuck on the KIES method, I removed my sd card and found that my titaniumbackup update.zip, also I found the folder where my KIES backup files are that I made on kies a few days ago. Please continue helping me.
*Edit, okay I found my IMEI through the google dashboard, it was also the same number on the sticker under the battery. FML. Okay so when doing the Kies method it asks me for the model name, I enter SGH-T999N, now it prompts to ask me for the s/n, I copy and paste in the IMEI, but it says that it is incorrect. PLEASE HELP
Click to expand...
Click to collapse
tookutz said:
I posted my problem on androidcentral earlier today, I'm not progressing anywhere with my situation, I've copied my original posts with some edits here. If you need more information for helping me to resolve this dilemma, ask right away.
Click to expand...
Click to collapse
You should use this forum
If you try KIES recovery try to follow this
you should try use this tool kit
Check this out! You , YES! you are an " Android ". Not your phone but U.
You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone
How to say Thank you? If you find any post helpful on XDA, click on their Thanks button
{
"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 are using XDA App or Tapatalk, long press on the post and select :good: Thanks Its easier to give "Feedback" in this manner than make an additional post.
xsenman said:
You should use this forum
If you try KIES recovery try to follow this
you should try use this tool kit
Check this out! You , YES! you are an " Android ". Not your phone but U.
You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone
How to say Thank you? If you find any post helpful on XDA, click on their Thanks button
If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks Its easier to give "Feedback" in this manner than make an additional post.
Click to expand...
Click to collapse
Thankyou for being the first person on here to reply and linking me to a very helpful thread, but I'm a noob can you please tell me what I'm exactly suppose to do? Like do i re-flash it to a stock version? I'm very new to this and I don't exactly know what all the terms mean yet.
tookutz said:
Thankyou for being the first person on here to reply and linking me to a very helpful thread, but I'm a noob can you please tell me what I'm exactly suppose to do? Like do i re-flash it to a stock version? I'm very new to this and I don't exactly know what all the terms mean yet.
Click to expand...
Click to collapse
you should first try the KIES method. following the guide, since you have mentioned it earlier, if that fails
Than you need to locate the original Stock ROM for SGH T999N to flash using Odin3 version 3.04 and up ( sometimes if you use wrong version or a poor USB connection ( wrong USB cable) , you could end-up with problem you had posted), as others meant for variants may not be compatible with yours that why its important you seek help in the S3 forum, for someone may have the same unit you have and may know where you can download it. You can Post in that forum, for help or search that forum for relevant info regarding your particular variant.
EDIT: you can down load the ROM http://www.samfirmware.com/
Country/Carrier Date Version
USA (T-Mobile) 2013 April 4.1.2 T999UVDMD5 Latest
USA (T-Mobile) 2013 January 4.1.1 T999UVDLJC
USA (T-Mobile) 2012 October 4.1.1 T999UVDLJA
USA (T-Mobile) 2012 October 4.0.4 T999UVALJ4
USA (T-Mobile) 2012 August 4.0.4 T999UVALH2
USA (T-Mobile) 2012 May 4.0.4 T999UVALEM oldest
Most of all Charge your phone fully, before attempting to Flash
The tool kit has guides that can help you download that ROM, so read it thoroughly as to how to use it.
Check this out! You , YES! you are an " Android ". Not your phone but U.
You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone
How to say Thank you? If you find any post helpful on XDA, click on their Thanks button
If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks Its easier to give "Feedback" in this manner than make an additional post.
xsenman said:
you should first try the KIES method. following the guide, since you have mentioned it earlier, if that fails
Than you need to locate the original Stock ROM for SGH T999N to flash using Odin3 version 3.04 and up ( sometimes if you use wrong version or a poor USB connection ( wrong USB cable) , you could end-up with problem you had posted), as others meant for variants may not be compatible with yours that why its important you seek help in the S3 forum, for someone may have the same unit you have and may know where you can download it. You can Post in that forum, for help or search that forum for relevant info regarding your particular variant.
EDIT: you can down load the ROM http://www.samfirmware.com/
Country/Carrier Date Version
USA (T-Mobile) 2013 April 4.1.2 T999UVDMD5 Latest
USA (T-Mobile) 2013 January 4.1.1 T999UVDLJC
USA (T-Mobile) 2012 October 4.1.1 T999UVDLJA
USA (T-Mobile) 2012 October 4.0.4 T999UVALJ4
USA (T-Mobile) 2012 August 4.0.4 T999UVALH2
USA (T-Mobile) 2012 May 4.0.4 T999UVALEM oldest
Most of all Charge your phone fully, before attempting to Flash
The tool kit has guides that can help you download that ROM, so read it thoroughly as to how to use it.
Check this out! You , YES! you are an " Android ". Not your phone but U.
You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone
How to say Thank you? If you find any post helpful on XDA, click on their Thanks button
If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks Its easier to give "Feedback" in this manner than make an additional post.
Click to expand...
Click to collapse
Thankyou again, I'll post there and see if anyone else has had the same problem.
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This rom is primarily for UK unlocked devices (BTU) but it will work in any other country code.
ROM version-JRO03H.***** XXALJL
Baseband- XXALJL
Csc-BTU I8190OXXALJ8
This is a full Uk firmware rooted.
Download the rom an odin from the provided link and unzip it .
Put your phone into “Download mode” by Shutting down your device ,the press and hold Home button+Volume-down+Power Button, once you get to the screen with a yellow triangle press “volume Up”.
Connect your device to the pc…
Open odin and select “ Pda” and browse to the location of the “rooted.tar” now press start in odin.
Flashing will take about 10 minutes.
Rom will not void your warranty nor will wipe your data, will not increase your download binary count er either.
Firmware has been tested in 2 devices, but I will not be responsible for any damage cause by it or from it. As always flash it at your own risk.
Rom Languanges*
en_GB;en_US;en_AU;en_IE;en_NZ;en_ZA;ko_KR;de_AT;de_CH;de_DE;fr_FR;fr_CH;bg_BG;cs_CZ;da_DK;
el_GR;es_ES;et_EE;fi_FI;ga_IE;hr_HR;hu_HU;is_IS;it_IT;lt_LT;lv_LV;mk_MK;nb_NO;nl_NL;nl_BE;
pl_PL;pt_PT;ro_RO;sr_RS;sv_SE;tr_TR;ca_ES;eu_ES;gl_ES;kk_KZ;ru_RU; sk_SK; sl_SI; uk_UA;
uz_UZ;az_AZ;hy_AM; ka_GE;es_US; pt_BR;
Keyboard support
en_GB;en_US;az;ca;cs;da;de;et;es;eu;el;fr;gl;ka;hr;it;is;kk;lv;lt;hu;nb;nl;pl;pt;ru;ro;fi;
sr;sk;sl;sv;tr;uk;ko;hy;bg
What are the advantages of flashing a rom designed for your country code/service provider?
Well for one you’re rom VERSION and CSC CODE will match therefore when there are official updates from Kies you should be able to just update.
Flashing a rom that was not made for your specific country code will work ,but you may find that your battery will drain faster, wireless performance is degraded etc ,this is because every rom made for a country id/provider also has a matching modem/baseband included, mess with that and you may find that your device will not perform as intended.
Some people may say: “I will flash any rom then just flash my country id/provider modem and that’s the problem fixed”
NO. Specific radios work specific matched (SYS)roms ( rill files) etc.
The rule is, your Baseband version should match the Build number, like so:
Baseband version-*****XXALJL
Build number- ******.*****XXALJL
Thanks to Avicohh, for all his advice and KEN for providing the devices!
Disclaimer:
If you don’t know what I’m talking about above I suggest you leave your device alone and do some research before attempting to flash it.
Firmware has been tested in 2 devices, but I will not be responsible for any damage cause by it or from it. As always flash it at your own risk.
DOWNLOAD HERE......
Thanks for your work.
I was wondering what are the optimizations this ROM brings to the official one except rooting?
Well im not from UK, im from Macedonia but my baseband and build number are xxajlj, so i can flash without problems?
Пратено со Tapatalk 2 од мојот SGSIII mini
vonuzu said:
Well im not from UK, im from Macedonia but my baseband and build number are xxajlj, so i can flash without problems?
Пратено со Tapatalk 2 од мојот SGSIII mini
Click to expand...
Click to collapse
Yes as you have the same baseband. The rom will work with all basebands its just optimized to the uk .
goodmamba said:
Thanks for your work.
I was wondering what are the optimizations this ROM brings to the official one except rooting?
Click to expand...
Click to collapse
The rom is stock as it was a test on rebuilding roms, but im currently writing a tutorial in how to build a custom rom.
I just flashed my sgs3mini with no problems, it was about 9min and it didnt wipe anything. Thanks faria
Пратено со Tapatalk 2 од мојот SGSIII mini
Perfect. I have a rooted s3 mini 1 day after i bought it Thanks alot from Sweden!
Hi, worked for my german Mini also. Just installed rSAP successful, the thing that was really missing! I will test function later today.
I get this:
Code:
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Cannot flash.
Any ideas?
imbehind said:
I get this:
Code:
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Cannot flash.
Any ideas?
Click to expand...
Click to collapse
Does ODIN recognize your phone? It should show something like 0:[COMxx] at the top left box (green colored).
If not you need to install drivers (KIES from samsung)
imbehind said:
I get this:
Code:
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Cannot flash.
Any ideas?
Click to expand...
Click to collapse
Are drivers installed :thumbup:
Guide on flashing this rooted ROM with Heimdall: http://forum.xda-developers.com/showthread.php?p=35903752#post35903752
quendil said:
Does ODIN recognize your phone? It should show something like 0:[COMxx] at the top left box (green colored).
If not you need to install drivers (KIES from samsung)
Click to expand...
Click to collapse
Yes, ODIN recognizes the phone (COM8) in second row first box from the left.
Kies/Drivers are installed.
Try another USB port with another cable if u have one, and exit kies because Odin & kies don't get along if running together. Try that see if that helps.
Sent from my GT-I8190 using xda premium
Worked perfectly with Romanian SGS3 Mini with the same baseband as in picture and the same info :good: Thank you :laugh:
Thanks for the ROM, it is the same as mine in Czech Republic
PDA - I8190XXALJL
PHONE- I8190XXALJL
CSC- I8190OXXALJ8
Well I hope it is the one, because you named the file that way (you have no CSC in the original post).
I also downloaded the original (unrooted rom) from the sammobile site.
The strange thig is that after flashigng with Odin both of these ROMs report
CSC: Unknown
Everything works, so I am not complaining but I am just curios as to why.
Thanks again for the rooted rom!
Thank you! I'm gonna try this right after I get the courage to flash my 3 day old phone
I'm using your V2 rom, had no problems so far only that software update won't allow it says that phone has been modified, will this ROM cure this problem?
Sorry for the noob question
Sent from my GT-I8190 using Xparent Blue Tapatalk 2
Build custom rom
faria said:
The rom is stock as it was a test on rebuilding roms, but im currently writing a tutorial in how to build a custom rom.
Click to expand...
Click to collapse
I would love to get your tutorial.. I want to start building custom roms too.
Hi, I received from a friend of Samsung two device with Tizen os, based on Galaxy S3. I would like to know if there is a method to flash android on one of them, to compare the difference. Thank you
This is the device model:
{
"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"
}
Sylar900 said:
Hi, I received from a friend of Samsung two device with Tizen os, based on Galaxy S3. I would like to know if there is a method to flash android on one of them, to compare the difference. Thank you
This is the device model:
Click to expand...
Click to collapse
did you try to flash S3's firmware?
So, I open Odin. Go to download mode on my device, connect with usb. Odin says: "<ID:0/004> Added!!"
Then I insert on PDA the .tar.md5 firmware file (I9300XXEMC2_I9300ITVEMC1_I9300XXEMC2_HOME.tar).
Then I click START, the screen of the device blinks once but odin says:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXEMC2_I9300ITVEMC1_I9300XXEMC2_HOME.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> Added!!
And nothing has changed..Ok? Thank you
1.
Remember differences between prototype/sample and retail devices...
So check if your device is retail... remove battery look on label...
"Not for sale" or something similar could be on label...
2.
Bootloader... maybe for Tizen Special Bootloader...
I have read short something about this somewhere forgotten...
Because Tizen is cra...
So the Question is, if you can generally update your Tizen devices with Tizen for instance...
Or you have never tried... Maybe other problem...
3.
Maybe better or safer choice is to use your Tizen devices with Tizen...
There are different Versions available... instead risk to brick your Tizen device, by stupid mistake.
4.
You could sell your Tizen device.
Best Regards
adfree said:
1.
Remember differences between prototype/sample and retail devices...
So check if your device is retail... remove battery look on label...
"Not for sale" or something similar could be on label...
2.
Bootloader... maybe for Tizen Special Bootloader...
I have read short something about this somewhere forgotten...
Because Tizen is cra...
So the Question is, if you can generally update your Tizen devices with Tizen for instance...
Or you have never tried... Maybe other problem...
3.
Maybe better or safer choice is to use your Tizen devices with Tizen...
There are different Versions available... instead risk to brick your Tizen device, by stupid mistake.
4.
You could sell your Tizen device.
Best Regards
Click to expand...
Click to collapse
Label says only:
MODEL: GT-I9300
FCC ID: A3LGTI9300A
SSN :I9300GSMH
RATED: 3.8V ; 2100mA
Made in Korea by Samsung
Can you help me? I will not sell the device, they was gift to me..
As you know I am Android Idiot... never used Odin... nor flashed any Android handset...
But I know little bit about Security problems with Bootloader...
Short Google search, because I have forgotten where I saw instruction on Tizen site...
https://wiki.tizen.org/wiki/OSDev/Flashing_to_device
Code:
Download the [B]lthor[/B] tool for [B]Linux[/B] PCs available at download.tizen.org/tools/lthor-tool/
Maybe Tizen handsets have special secured and locked only for Tizen devices...
So again...
You can update Tizen Firmware on your S3 ?
Never tried ?
Best Regards
I think partitions are not the same (Tizen and Android)
If you want to risk ... try to flash the pit file
Please... better sell Tizen device or share with Tizen Developers...
Instead doing brainless stxpid tests...
First official Tizen devices end 2013... beginning 2014...
Tizen Developer could develop for Tizen... :angel:
Also more usefull... in my eyes... dump Bootloader or whole memory from S3...
Maybe then more chance to port to S8500/S8530/S8600...
If you need S3 with Android... buy S3.
Or maybe some S3 user would exchange...
Best Regards
adfree said:
As you know I am Android Idiot... never used Odin... nor flashed any Android handset...
But I know little bit about Security problems with Bootloader...
Short Google search, because I have forgotten where I saw instruction on Tizen site...
https://wiki.tizen.org/wiki/OSDev/Flashing_to_device
Code:
Download the [B]lthor[/B] tool for [B]Linux[/B] PCs available at download.tizen.org/tools/lthor-tool/
Maybe Tizen handsets have special secured and locked only for Tizen devices...
So again...
You can update Tizen Firmware on your S3 ?
Never tried ?
Best Regards
Click to expand...
Click to collapse
Yes I updated Tizen Firmware ih this device today, so it isn't blocked.
I wont sell them because they are gift to me and I'm so correct with this.
Okidoki, if Tizenupdate success... then maybe Tizen Bootloader is secured to Download only Tizen stuff...
No idea...
If someone has Bootloader of Tizen or dumped Tizen Bootloader... We could maybe check...
Btw.
Found this about "Not for sale"... only as info.
http://forum.xda-developers.com/showpost.php?p=31587295&postcount=47
live demo unit
Click to expand...
Click to collapse
Best Regards
Can't you just install Android apps on the device ??
Or you want the whole Android experience ??
I remember seeing that Tizen devices can use Android's apps
Best Regards
mylove90 said:
Can't you just install Android apps on the device ??
Or you want the whole Android experience ??
I remember seeing that Tizen devices can use Android's apps
Best Regards
Click to expand...
Click to collapse
He wants to Flash Android on Galaxy S3 RD (Tizen),
and Tizen can run android apps only with Polaris App Player
AFAIK there is uboot working on this device, and it does not support ODIN. It does support THOR and might support fastboot. On legacy I9300 you will find SBOOT.
Dump dat stuff. Google for howtos.
Rebellos said:
AFAIK there is uboot working on this device, and it does not support ODIN. It does support THOR and might support fastboot. On legacy I9300 you will find SBOOT.
Dump dat stuff. Google for howtos.
Click to expand...
Click to collapse
Yes it support lthor.. Do you know if there is a possibility to flash android with this like Odin? Thank you
Not tested NO idea no Tizen device to check... but this looks interesting:
http://www.tizenexperts.com/2012/05/tizen-developer-device-boot-loader-special-user-mode/
Here are maybe some basics about Tizen Bootloader...
https://source.tizen.org/sites/default/files/tizen_porting_guide_2.0_alpha.pdf
Again.
I think it would be good idea to Backup BEFORE Tizen Bootloader from device...
Then you can check if similar to Android...
Otherwise your tests could lead to bricked Software dead device... with no use...
Best Regards
adfree said:
Not tested NO idea no Tizen device to check... but this looks interesting:
http://www.tizenexperts.com/2012/05/tizen-developer-device-boot-loader-special-user-mode/
Here are maybe some basics about Tizen Bootloader...
https://source.tizen.org/sites/default/files/tizen_porting_guide_2.0_alpha.pdf
Again.
I think it would be good idea to Backup BEFORE Tizen Bootloader from device...
Then you can check if similar to Android...
Otherwise your tests could lead to bricked Software dead device... with no use...
Best Regards
Click to expand...
Click to collapse
My friend on Samsung that sent me the devices told me that RD-PQ shares very same hardware with S3, but he doesn't know how to flash Android on it. Thank you
Rebellos said:
AFAIK there is uboot working on this device, and it does not support ODIN. It does support THOR and might support fastboot. On legacy I9300 you will find SBOOT.
Dump dat stuff. Google for howtos.
Click to expand...
Click to collapse
From tizen.org:
"For the Tizen platform, the boot loader
comes in two parts. The first part is the primary boot loader and the second part is the
secondary boot loader. The primary boot loader is the Samsung proprietary boot loader and is
also called s-boot. The secondary boot loader is the open source boot loader u-boot, which is
customized further for the Tizen platform. "
UPDATE:
This is the files that are in the System of the device, as you can see there is u-boot and s-boot. But how to launch s-boot and not u-boot bootloader?
https://www.dropbox.com/home/Public/Tizen_RD-PQ_System_20130423_1
Can you find the command list to open s-boot bootloader in s-boot-mmc.bin file? Thank you
Hi, Had you see these files?
Thanx, I am not registered on Dropbox...
I can not download...
Best Regards
adfree said:
Thanx, I am not registered on Dropbox...
I can not download...
Best Regards
Click to expand...
Click to collapse
for you: https://mega.co.nz/#F!WZcRiI6L!Z3rhLxpFnC53z9z0KYwWHw
Hi everyone. I have a big problem on my hands. I tried to install Jelly Bean 4.1.2 stock firmware (on Samsung S II) from SamFirmware via Odin. During the install process a "FAIL!" message appeared.
{
"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"
}
)
Here is the message list below:
<ID:0/013> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLSS_I9100OJCLS4_I9100XXMS2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/013> Odin v.3 engine (ID:13)..
<ID:0/013> File analysis..
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Get PIT for mapping..
<ID:0/013> Firmware update start..
<ID:0/013> boot.bin
<ID:0/013> NAND Write Start!!
<ID:0/013> factoryfs.img
<ID:0/013> __Xmit Write fail
<ID:0/013> XmitData Fail..
<ID:0/013> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I followed the installation instructions carefully:
Boot phone into download mode.
Load Odin.
Connect phone to computer via USB.
Click PDA and browse for file (mine is I9100XWLSS_I9100OJCLS4_I9100XXMS2_HOME.tar.md5).
Make sure default settings unchanged and Re-Partition is disabled.
Then I clicked "Start"
I have used Odin before and have successfully rooted and installed firmware on my phone in the past.
I just dont understand why this is happening.
At the moment I havent touched anything (my phone is still connected to my computer and Odin has been left as it is and not closed). As I am quite scared to brick it. The download bar hasnt moved.
Please help. My friend asked me to install this firmware on his phone so I am in seriously need urgently. Thanks
Hopper8's "Odin troubleshooting' thread. Find it, try as much of the stuff in the thread as you need to in order to get a successful flash.
MistahBungle said:
Hopper8's "Odin troubleshooting' thread. Find it, try as much of the stuff in the thread as you need to in order to get a successful flash.
Click to expand...
Click to collapse
Thanks. I read the guide (http://forum.xda-developers.com/showthread.php?t=2345831) but what I saw there was about flashing failing when the connection to Odin isnt working.
With me my connection works (Ive updated firmware before via Odin) but the thing is it failed in middle of process
Are there any options I can choose in Odin to reboot safely? It is still in Fail state and phone still connected to computer (I havent touched anything)
It can fail in the middle of a flash for all kinds of reasons (bad download, temporary break in the connection between phone/PC but not long enough to register on the PC side).
You don't really have any other choice than pull the plug & hope you can switch the phone off & get into download mode again/hope that you haven't hard bricked it.
One way or another you need to get a successful Odin flash away in order to fix it. Despite your protestations to the contrary, the stuff in that thread does apply to the situation you find yourself in. If you can still get into download mode once you've unplugged it/pulled the battery, I very much recommend you try everything in that thread (including trying different PC's if necessary; how many previously successful flashes you've had is irrelevant if you can't fix this phone). Unless you'd rather take it to a Samsung service centre & pay them an exorbitant amount of money to fix it ?
MistahBungle said:
It can fail in the middle of a flash for all kinds of reasons (bad download, temporary break in the connection between phone/PC but not long enough to register on the PC side).
You don't really have any other choice than pull the plug & hope you can switch the phone off & get into download mode again/hope that you haven't hard bricked it.
One way or another you need to get a successful Odin flash away in order to fix it. Despite your protestations to the contrary, the stuff in that thread does apply to the situation you find yourself in. If you can still get into download mode once you've unplugged it/pulled the battery, I very much recommend you try everything in that thread (including trying different PC's if necessary; how many previously successful flashes you've had is irrelevant if you can't fix this phone). Unless you'd rather take it to a Samsung service centre & pay them an exorbitant amount of money to fix it ?
Click to expand...
Click to collapse
I managed to get it working. I disconnected the phone and it fortunately was able to go into download mode and I installed a different stock firmware. Thanks for help
protein.synthesis said:
I managed to get it working. I disconnected the phone and it fortunately was able to go into download mode and I installed a different stock firmware. Thanks for help
Click to expand...
Click to collapse
I can get into download mode, Odin will just NOT complete the install of the galaxy S3 firmware it stays stuck at "system ext4" for hours...any thoughts - see attachment...ty
And you're posting in an I9100 thread why exactly ?
it was my usb cable
try a genuine Samsung usb cable (the white one). I tried the one that came with my galaxy tab 3 swapped out my cheapo usb cable and got past this error and got the orginal firmware back on my sgh-t999 S3
Pretty sure nobody here cares given you have a different device (this is obvious advice anyway - of course you try different USB cables, in particular genuine Samsung ones).
idiot
MistahBungle said:
Pretty sure nobody here cares given you have a different device (this is obvious advice anyway - of course you try different USB cables, in particular genuine Samsung ones).
Click to expand...
Click to collapse
why didnt you help out protein.synthesis with this info then? the error is the same fix across all the S3 variants.
Bigger idiot
I did help that individual, but that person lied about going through Hopper's thread in a methodical way, which will always recover a phone that's actually recoverable in this situation. And why did that person lie ? Because 95% of people who post here a ****ing lazy & want 'easy'. There is no ****ing easy in this situation.
Hopper's thread mentions the USB cable thing & 238 other troubleshooting steps dip****, which is why we refer anyone who has this issue with an I9100 to it. We're sick & tired of posting this **** over & over for people who are too ****ing lazy to search.
You should be posting in forums for your specific device, not wherever the **** you feel like it.
And you need to get your ****ing facts straight/get some reading/comprehension skills before you gob off in future you ****ing moron.
Also, FYI, the fixes are pretty much the same across all Galaxy series phones, but that is absolutely beside the point.
Basically same for me.
I've been trying to root my Samsung Galaxy S2 GT-i9100 XWLSW and every time I try to install a custom Kernel ODIN says:
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<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> zImage
<ID:0/005> __XmitData_Read ..
<ID:0/005> XmitData Fail..
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I need help
^^^
You need:-
1) To say please. We're not your servants :-/
2) To read my first post on the first page (after the OP). It refers to the 'tools' you need to fix this.
*Update*
Reviving this thread since it is still prevalent on google. Do you have Kies installed at the time of Attempting to flash with Odin? This is a common problem when trying to flash with Odin. Hope this helps for all those tearing their hair out over this!
once i got rid of my custom recovery things seemed to get better. I flashed cf auto root with odin 3.07 then flashed stock FW and i was back in business. Hopefully this will work for others.
jeepersmr said:
try a genuine Samsung usb cable (the white one). I tried the one that came with my galaxy tab 3 swapped out my cheapo usb cable and got past this error and got the orginal firmware back on my sgh-t999 S3
Click to expand...
Click to collapse
thanks a lot dude it fixed the error
AndroidInitiate said:
Reviving this thread since it is still prevalent on google. Do you have Kies installed at the time of Attempting to flash with Odin? This is a common problem when trying to flash with Odin. Hope this helps for all those tearing their hair out over this!
Click to expand...
Click to collapse
I had Kies installed and got this error:
<ID:0/005> __XmitData_Write
<ID:0/005> Complete(Write) operation failed.
when trying to flash my Note 5 with ODIN. I was using a Samsung USB cable but it was from an S5. I switched to the Note 5 USB cable and uninstalled Kies and I was able to overcome the error.
Thanks!
hay que cambiar el cable y listo
Charging your device can also help in case it resets because of it
YOUR BOOTLOADER IS LOCKED, NO CUSTOM RECOVERY, NO MARSHMALLOW,
{
"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"
}
NO CM, NO AOSP, NO TWRP, NO CWM, NO PHILZ, NO WHINING!
What does that mean?
Who Locks Them?
Want more info: eFuse
For those that are still curious: If we are serious about unlocking the bootloader
Don't need to de-brick? Scroll down and see "The Good News"
The Five Stages of OF1 Grief:
Denial: “Oh, no problem, I’m rooted!”
Anger: "Darn that Verizon."
Bargaining: “I’ll downgrade to Kit-Kat, if it will unlock my bootloader.”
Depression: “No CM-13? I can’t go on!”
Acceptance: “Next time I’ll do more research before buying a new phone.”
A list of common mistakes that cause boot loops or worse on stock ROM
Flashing TWRP, CWM, or Philz
Flashing a Custom ROM*
Flashing a Custom Kernel*
Flashing X-posed*
Flashing just about anything*
Uninstall System App
Uninstall System Priv-App
Convert System App to User App
Convert User App to System App
Uninstall System App That Was a User App But Got Converted To System App By User
Install a Font
Install a Bootanimation
TOUCHING ANYTHING THAT SAYS (ODEX)
Tweaking the Kernel*
Un-tweaking the Kernel*
This list could go on for a while, but I think you get the point:
*Without proper knowledge, see below.
Don't worry, there are options. Keep scrolling.
Mistakes that can cause a Hard brick:
1. Trying to downgrade your bootloader so you can unlock it and flash TWRP and install CM13
______________________________________________________________
Please try this first, before posting a HHEEELLLPP! thread.
If you are soft-bricked(boot loop):
Instructions:
Download firmware here: Firmware/Odin
Extract (unzip) the firmware file
Open Odin3 v3.10.7 (Other versions included JIC)
Boot device into Download Mode:
With the device powered down, press and hold Power & Volume Down buttons.
When warning appears, release and press Volume up to Enter Download (Odin) Mode.
Connect device and wait until you get a blue tab in Odin, upper left below ID:COM
Click the AP button and navigate to the extracted firmware and select it. Odin will verify the md5. This may take a little while.
Once verified click the start button. Sit back and wait. When finished you will see "PASS" and phone will reboot:
JOY
If you are Hard-bricked (unresponsive, not recognized by Odin):
NO JOY
See your local VZW dealer.
Or you could try this:
J-Tag
________________________________________________________________
The Good News
If you are rooted, have Kinguser SuperSu and Busybox installed, and are good at following directions look here:
or
or
or here:
and here:
Also Available:
Unsigned Kernel Module For OF1!
By @[SIZE="4"]klabit87[/SIZE]
Flashfire Install!
Extreme Battery Saving Method
By @[SIZE="4"]ATGkompressor[/SIZE]
So tell me. Who needs CM now?
Thanks to @stang5litre, @klabit87, @Albe95, @mohammad.afaneh, @Surge1223 and @ATGkompressor
for providing a means to improve our phones.
Myself and the others listed are NOT responsible
for the damage that YOU do to your phone!
See next post for additional notes.
Don't forget to
If you are having trouble with Odin, first try a different USB cable. Then try a different version of Odin. See link below.
I have attached a .pit file also. This is unverified, See link below.
Always follow the OF1 instructions in ROM link's.
Hint: FF = Flashfire = OF1
Take one: View attachment Statement.pdf
Older Odin Versions
Pit File
Don't forget J-tag [emoji106] [emoji2]
Sent from my SM-G935V using Tapatalk
stang5litre said:
Don't forget J-tag [emoji106] [emoji2]
Click to expand...
Click to collapse
Added It's actually a great video. I got a little misty :crying:
im always corrupt file when im download at sammobile, anyone have direct link pls
AnggaKun said:
im always corrupt file when im download at sammobile, anyone have direct link pls
Click to expand...
Click to collapse
Hey. In what way do you mean corrupt? Is Odin giving you an error?
bg260 said:
Hey. In what way do you mean corrupt? Is Odin giving you an error?
Click to expand...
Click to collapse
not at odin but when im try to extract it(firmware.zip) with using winrar.. it show text archive is corrupt :crying: can u help me pls
im got bootloop on of1 firmware when im instaling kernel A3 in stang5litre, im wanna flash it but when im download firmware at sammobile it always corrupt
#ask can if im flash using oc1 firmware? thank u :good:
AnggaKun said:
not at odin but when im try to extract it(firmware.zip) with using winrar.. it show text archive is corrupt :crying: can u help me pls
im got bootloop on of1 firmware when im instaling kernel A3 in stang5litre, im wanna flash it but when im download firmware at sammobile it always corrupt
#ask can if im flash using oc1 firmware? thank u :good:
Click to expand...
Click to collapse
First of all try the NOBL.tar.md5 alternative from above. Are you trying to extract from the zip? you don't need Winrar for that.
AnggaKun said:
not at odin but when im try to extract it(firmware.zip) with using winrar.. it show text archive is corrupt :crying: can u help me pls
im got bootloop on of1 firmware when im instaling kernel A3 in stang5litre, im wanna flash it but when im download firmware at sammobile it always corrupt
#ask can if im flash using oc1 firmware? thank u :good:
Click to expand...
Click to collapse
Since I'm in a good mood:
Firmware
I can't leave it there forever, though. Just please stop posting questions all over the forum. You made a mistake. A really big one. A little humility goes a long way.
bg260 said:
Hey. In what way do you mean corrupt? Is Odin giving you an error?
Click to expand...
Click to collapse
bg260 said:
First of all try the NOBL.tar.md5 alternative from above. Are you trying to extract from the zip? you don't need Winrar for that.
Click to expand...
Click to collapse
can u give me the link ? :crying: im sorry if im bother u sir xD
---------- Post added at 04:52 AM ---------- Previous post was at 04:51 AM ----------
bg260 said:
Since I'm in a good mood:
Firmware
I can't leave it there forever, though. Just please stop posting questions all over the forum. You made a mistake. A really big one. A little humility goes a long way.
Click to expand...
Click to collapse
okay im wanna to delete it sir :fingers-crossed::good: im sorry if im bother u
and thanks for all
this file is for ekstract? im try to extract it it say !
D:\Documents and Settings\PUTRA COMPUTER\My Documents\Downloads\I545VRUGOF1_I545VZWGOF1_VZW.zip: The archive is corrupt
! D:\Documents and Settings\PUTRA COMPUTER\My Documents\Downloads\I545VRUGOF1_I545VZWGOF1_VZW.zip: Unknown method in I545VRUGOF1_I545VZWGOF1_I545VRUGOF1_HOME.tar.md5
! D:\Documents and Settings\PUTRA COMPUTER\My Documents\Downloads\I545VRUGOF1_I545VZWGOF1_VZW.zip: The archive is corrupt
! D:\Documents and Settings\PUTRA COMPUTER\My Documents\Downloads\I545VRUGOF1_I545VZWGOF1_VZW.zip: No files to extract
help xD
---------- Post added at 07:04 AM ---------- Previous post was at 06:34 AM ----------
<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> aboot.mbn
stuck in there
Hey AnggaKun,
I'm not sure if this is your issue but I had a firmware extraction / zip issue..and could not figure it out. I tried on multiple machines until I narrowed down the problem. I had *BAD MEMORY* chip! I had to replace the memory and *VOILA* problem went away... Not sure if that is your issue.
-TimJ
AnggaKun;67808617]this file is for ekstract? im try to extract it it say !
......
help xD
Click to expand...
Click to collapse
AnggaKun said:
this file is for ekstract? im try to extract it it say !
D:\Documents and Settings\PUTRA COMPUTER\My Documents\Downloads\I545VRUGOF1_I545VZWGOF1_VZW.zip: The archive is corrupt
! D:\Documents and Settings\PUTRA COMPUTER\My Documents\Downloads\I545VRUGOF1_I545VZWGOF1_VZW.zip: Unknown method in I545VRUGOF1_I545VZWGOF1_I545VRUGOF1_HOME.tar.md5
! D:\Documents and Settings\PUTRA COMPUTER\My Documents\Downloads\I545VRUGOF1_I545VZWGOF1_VZW.zip: The archive is corrupt
! D:\Documents and Settings\PUTRA COMPUTER\My Documents\Downloads\I545VRUGOF1_I545VZWGOF1_VZW.zip: No files to extract
help xD
---------- Post added at 07:04 AM ---------- Previous post was at 06:34 AM ----------
<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> aboot.mbn
stuck in there
Click to expand...
Click to collapse
Try a different version of Odin. It definitely sounds like a computer problem. See next post.
View attachment Odin_v1.85.zip
View attachment Odin_v3.09.zip
View attachment Odin3_v3.10.5.zip
View attachment Odin3_v3.10.6.zip
View attachment Odin3_v3.12.3.zip
Good..
Anyone have link to download s4 verizon repair assistan? Im search for the link but i dont find the link.. someone say can fix the anggakun problem with using Samsung S4 verizon repair asistan.. :good:
@Rahmatkhairullah
Found this in a thread here somewhere. I have never been able to make it work. Have at it.
View attachment Verizon_Upgrade_Assistant.zip
I think I searched for Upgrade Assistant instead of Software Repair Assistant.
Anything else?
bg260 said:
Anything else?
Click to expand...
Click to collapse
The software upgrade assistant might be too outdated, I can't get it to run on my pc
can u reupload sir ? im sorry sir help me pls
View attachment 3817908
I think I searched for Upgrade Assistant instead of Software Repair Assistant.
AnggaKun said:
The software upgrade assistant might be too outdated, I can't get it to run on my pc
can u reupload sir ? im sorry sir help me pls
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"
}
In the spirit of moving custom ROM development along for the 2019 Galaxy Tab A 10.1 [SM-T510], here's a build of LineageOS 16.0 I just created based on the latest OEM firmware and @AndyYan's latest LineageOS 16.0 GSI. It's very much a work in progress, but it should hopefully help blaze the trail for even better work.
Notes:
The current process requires you to reset to factory defaults to remove file-based encryption. Remember to backup your data!
Custom kernels are specific to OEM releases, and this one is based on the February 2020 Update (T510XXS3ATB4).
Stock recovery will be replaced with my latest TWRP build for the SM-T510..
This is built with root support (enabled in Developer Options). To remove (and enable vendor spoofing), just run "/system/bin/phh-securize.sh" with root access.
This is unofficial and unsupported, so the usual caveats apply. Since we don't flash the bootloader, you should be able recover from any problems...but nothing is guaranteed.
Not working:
Support for file-based encryption
Downloads:
lineage-16.0-20200422-UNOFFICIAL-T510XXS3ATB4.tar.md5 (Odin tarball)
lineage-16.0-20200422-UNOFFICIAL-T510XXS3ATB4.zip (TWRP update)
Change Log:
20200422:
New private build of LineageOS GSI with April 2020 Security Patch.
Updated to the OEM T510XXS3ATB4 kernel and vendor partition.
20200405:
Fixed Double Tap to Wake feature (enabled in Phh Treble Settings).
Fixed crash on first two attempts to launch Phh Treble Settings.
New private build of LineageOS GSI with the above fixes (#663 & #1228).
20200324:
New LineageOS GSI build of treble_a64_bvN target with March 2020 Security Update.
Switched to ext2simg for sparse image conversion to improve Odin compatibility and reduce download size.
Updated to T510XXS2ASK5 kernel (November 2019 Update)
20200308:
MTP file transfers should now work even with USB Debugging disabled.
Charging after full shutdown will no longer hang during level-of-charge animation.
Updated to T510XXS2ASK1 kernel (November 2019 Update)
20191019:
Initial release based on lineage-16.0-20191017-UNOFFICIAL-treble_a64_bvN
Instructions:
From OEM stock firmware:
Unlock bootloader
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install custom ROM tarball (.tar.md5 file) to AP with Odin
If TWRP launches, factory reset with Wipe->Format Data and reboot to system. (Not necessary for incremental upgrades.)
From existing TWRP install:
Hold Power & Vol Up during restart to enter TWRP recovery
Factory reset with Wipe->Format Data. (Not necessary for incremental upgrades.)
Tap Install, select your update (.zip file), and then swipe to install
Reboot to system
Source:
android_device_samsung_gta3xlwifi
treble_build_los
Phh-Treble
treble_build_los
Donations:
Your support is always appreciated! Just click here.
I'm leveraging a ton of work done by @AndyYan and @phhusson for Treble GSIs, so please show them some love here and here!
Leaving my own donation link here if anyone's feeling like it: https://paypal.me/AndyCGYan
One thing to note: LineageOS includes LiveDisplay and Night Light which affect the tone of the display (I like colder displays), but on this device both features lag the UI horribly, probably due to lack of HW acceleration. In this case, try the build.prop trick here to make things perceptibly smooth.
Gapps?
Thanks for this great ROM. I have managed to get it installed on my Black Friday purchased device. However, it would appear no to come with any Google stuff (which I would expect). Normally I would install from OpenGapps but it don't think any of those of suitable. Can anyone advise me what would be suitable. I was looking for the equivalent of the Full package on OpenGapps.
uknetfreak said:
Can anyone advise me what would be suitable. I was looking for the equivalent of the Full package on OpenGapps?.
Click to expand...
Click to collapse
Check out my Nexus Stock ROM.
ahhhh how to install.. im first rooting,....(for galuxy tab a 10.1 rooting tutorial)
#EDIT, wrong ROM
Fairly certain I followed all the steps but it has been a very long time since I've used Odin. Here's the failure log. Any idea where I'm going wrong? Tried running Odin as Administrator, same results. Thanks in advance for any help.
edit: Just tried your Nexus ROM and same results
<ID:0/004> 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/004> Odin engine v(ID:3.1303)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 1487 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> product.img
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Works like charm! thank you so much for the great work, are you going to release TWRP zip update files for coming version? also any idea why the tablet can't be encrypted? on other note, gsmarena mention that the CPU is Exynos 7904, which is not correct, mine is Exynos 7885! which isn't 64bit as far as I can tell, any idea of there was some versions with Exynos 7904 released?
Magendanz said:
In the spirit of moving custom ROM development along for the 2019 Galaxy Tab A 10.1 [SM-T510], here's a build of LineageOS 16.0 I just created based on the September 2019 Update and @AndyYan's latest LineageOS 16.0 GSI. It's very much a work in progress, but it should hopefully help blaze the trail for even better work.
Notes:
The current process requires you to reset to factory defaults to remove file-based encryption. Remember to backup your data!
Custom kernels are specific to OEM releases, and this one is based on the September 2019 Update (T510XXU2ASI4).
Stock recovery will be replaced with my latest TWRP build for the SM-T510..
This is unofficial and unsupported, so the usual caveats apply. Since we don't flash the bootloader, you should be able recover from any problems...but nothing is guaranteed.
Not working:
Double-tap to wake
Support for file-based encryption
MTP only works when USB Debugging is enabled
Charging after full shutdown will hang during level-of-charge animation.
Downloads:
lineage-16.0-20191019-UNOFFICIAL-T510XXU2ASI4.tar.md5
Change Log:
20191019:
Initial release based on lineage-16.0-20191017-UNOFFICIAL-treble_a64_bvN
Instructions:
Unlock bootloader
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install custom ROM to AP with Odin
When TWRP launches, wipe data if installing for first time. (Not necessary for incremental upgrades.)
Reboot to system
Source:
android_device_samsung_gta3xlwifi
treble_build_los
Phh-Treble
treble_build_los
Donations:
Your support is always appreciated! Just click here.
I'm leveraging a ton of work done by @AndyYan and @phhusson for Treble GSIs, so please show them some love here and here!
Click to expand...
Click to collapse
---------- Post added at 05:46 PM ---------- Previous post was at 05:44 PM ----------
Had some issues with TWRP, turned out to be a bad cable, was crashing with Odin and heimdall on Linux, but at 85% changed the cable and everything worked fine also not USB-C to USB-C cable in my case it had to be USB-A to USB-C cable.
sc00bied00 said:
Fairly certain I followed all the steps but it has been a very long time since I've used Odin. Here's the failure log. Any idea where I'm going wrong? Tried running Odin as Administrator, same results. Thanks in advance for any help.
edit: Just tried your Nexus ROM and same results
<ID:0/004> 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/004> Odin engine v(ID:3.1303)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 1487 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> product.img
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Hi
I've flashed this Rom yesterday and it does seem to work relatively well.
There are some issues, though. Mostly stability. Also the Tablet thinks that it is a phone. How do I tell it that it's a Tablet?
So.. where do we go from here? What are the next steps? How is this Rom built? What is the process to build it?
Regards
demoneg said:
Had some issues with TWRP, turned out to be a bad cable, was crashing with Odin and heimdall on Linux, but at 85% changed the cable and everything worked fine also not USB-C to USB-C cable in my case it had to be USB-A to USB-C cable.
Click to expand...
Click to collapse
Just tried with a brand new C -> A cable plugged into a USB 2.0 port and same error. I was originally using the cable that came with the tablet. Not sure what to try next.
sc00bied00 said:
Just tried with a brand new C -> A cable plugged into a USB 2.0 port and same error. I was originally using the cable that came with the tablet. Not sure what to try next.
Click to expand...
Click to collapse
I ran into this (the Odin error on product.img) on the 2 T510's I picked up for my kiddos. Both were initially running the November update, and both upon first boot and setup patched to the December update (this was before I realized there was a Lineage build available).
I was able to successfully flash this build by first downgrading to the September Samsung release (T510XXU2ASI4). I just pushed that through Odin, and immediately entered download mode again post-install, and then install Lineage without an issue. This worked on both of the tablets I have.
I ended up paying for a 3 day pass on samfrew.com because the download speeds are horribly crippled. I would be happy to upload/host the OEM firmware files somewhere to help others if it's not against the rules.
whoiswes said:
I was able to successfully flash this build by first downgrading to the September Samsung release (T510XXU2ASI4). I just pushed that through Odin, and immediately entered download mode again post-install, and then install Lineage without an issue. This worked on both of the tablets I have.
Click to expand...
Click to collapse
OK, that's odd. I bought this one at Costco about a month ago and it shipped with and factory resets to September AS14 :/
I'd already downloaded that rom from samfrew and even tried to flash it after both this and the Nexus ROMS failed. Same results as those two and failed with the same error at product.img
I wonder if I'll need to roll back to an even earlier one, or would loading a ROM earlier than what's in the recovery be a bad thing?
FWIW, in order to unlock the bootloader I went through the "disable auto-updates, auto time adjust, set the time to the past/future manually" trick.
sc00bied00 said:
OK, that's odd. I bought this one at Costco about a month ago and it shipped with and factory resets to September AS14 :/
I'd already downloaded that rom from samfrew and even tried to flash it after both this and the Nexus ROMS failed. Same results as those two and failed with the same error at product.img
I wonder if I'll need to roll back to an even earlier one, or would loading a ROM earlier than what's in the recovery be a bad thing?
FWIW, in order to unlock the bootloader I went through the "disable auto-updates, auto time adjust, set the time to the past/future manually" trick.
Click to expand...
Click to collapse
Odd. I didn't have any issues with applying the ASI4 updates (just the BG, AP, and CSC files) with Odin 3.14.1. I don't think OEM unlocking comes into play for this part.
What "KG STATE" in download mode showing? Prenormal means the knox protection got tripped which is probably (part of?) your issue. I can't say more because I honestly don't know (first Samsung device since the Galaxy Nexus). If you're at ASI4, and download mode shows KG STATE: checking, then you're in the same place I was for a successful flash of Lineage.
Sorry I can't be of more help.
Whelp, thar's mah problem. KG state is Prenormal. No idea how I tripped it but this is my first sammy since the S2. I'll start googling and would welcome any advice on what to do to get to a better state.
Thanks! At least now I know what's borked :/
EDIT [SOLVED]: The clue was in Menendez's reply in post #6 of MossyT's guide where he indicates that wifi should be enabled on the restart immediately after the Volume Up long press to unlock, thus revealing OEM Unlock in developer options. The very first go around, I was able to see the option and must have borked a stdep before or during Odin. All subsequent attempts after doing factory resets, I failed to activate wifi on first boot and went straight to Odin. Until the OEM rom can phone home, KG will remain 'prenormal'. Simply turning wifi on and verifying OEM Unlock in devops, KG changed to 'checking' and the flash went through fine.
Thanks for pointing me in the right direction. My daily drivers are a Moto G5+ and X so I'm a bit rusty at the "samsung way"
Any Chance to get double tap to wake (dt2w) running?
There seems to be a solution:
github.com /phhusson/treble_experimentations/issues/663
dussl said:
Any Chance to get double tap to wake (dt2w) running?
There seems to be a solution:
github.com /phhusson/treble_experimentations/issues/663
Click to expand...
Click to collapse
For now you can flash magisk and run those commands via adb as root on each reboot.
I suppose at some point we either fix the init.rc or phh extends the phh treble app to also run the connection check command.
Is this ROM still being updated or worked on? Just curious been 2 months and nothing from the OP. Thanks.
I am on T510xxu1ASEF. Am I correct to assume I need to upgrade the Firmware to the september release and then install the rom? Or is it as simple as flashing the new rom? I have unlocked the bootloader and have stopped until I find out what to do.
Edited because I'm an idiot and kept saying kernel when obviously the file I downloaded from Samsung was full rom not just kernel.
dcillusions77 said:
Is this ROM still being updated or worked on? Just curious been 2 months and nothing from the OP. Thanks.
Click to expand...
Click to collapse
I'll update it with the latest kernel source when I get back from holiday, but I wouldn't expect much because there haven't been any GSI updates from @AndyYan.
Magendanz said:
I'll update it with the latest kernel source when I get back from holiday, but I wouldn't expect much because there haven't been any GSI updates from @AndyYan.
Click to expand...
Click to collapse
Ok thanks for all your work much appreciated