Hi guys
First some details about the S3:
Model: GT-i9300 (International)
ROM: Custom (Omega v34)
Kernel: SiyaKernel v1.6
FW ver: 4.1.2
The boot loop happened freakishly :silly:. I'm saying it because, yesterday the S3 was working fine. I went to sleep and upon waking up found the S3 in a boot loop with the "Samsung i9300" and the black screen background.
I've been using the custom rom since 1 month without any issue. All I did yesterday (out of the ordinary), was to install a few updates of a few apps like AllShare/Facebook etc.
I'm able to boot into Recovery as well as Download mode. The Download mode shows:
Product Name: GT-I9300
Custom Binary Download: Yes (2 Counts) - I'm guessing this is the binary counter
Current Binary: Custom
System Binary: Custom
Had created a Nandroid backup, so tried restoring from it. Tried advanced restoring with boot first, but the phone restarted midway and then had the boot loop again. After that I tried a normal restore, same thing happened.
I've gone through a few similar posts here, but couldn't find an exact match for mine. Hence, I created this thread. For one, the details in the Download mode are different from others (in some the product or the other was missing, but all are showing in mine). So, I'm guessing my boot partition is still intact (I'm a noob, so, I might be wrong).
What are my options here:
Can I flash a newer ver of custom rom on it?
Will wiping data/factory reset help?
How about Cache Partition/Devlik cache?
Or should I flash a stock rom?
Also, if any other option available and in what order?
Any help will be really appreciated with a big THNX :good::angel:
Just go to download mode, flash a stock rom.. root it again and flash a custom rom (if you like)
Factory resetting wont help, nor wiping caches and dalvik cache
Sent from this girl who's an Android Nerd
saywhatt said:
Just go to download mode, flash a stock rom.. root it again and flash a custom rom (if you like)
Factory resetting wont help, nor wiping caches and dalvik cache
Sent from this girl who's an Android Nerd
Click to expand...
Click to collapse
Thnx for the info :good: . Will give it a try and revert back with the result
Fingers :fingers-crossed:
yup. flashing stock rom with odin and start all over again is ur best chance
I tried installing Stock Rom from the Download mode using ODIN.
Followed this thread http://tutorialfor-android.blogspot.in/2012/08/how-to-flash-firmware-to-galaxy-s3-via.html
Did everything, but ODIN returns as FAIL. What am I doing wrong? Am using ODIN v3.07..
Downloaded the stock rom from SamMobile..
The snapshot:
{
"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"
}
HELP!!!!!!
Use XDA instructions .
http://forum.xda-developers.com/showthread.php?t=1671969
BASICS
http://forum.xda-developers.com/showthread.php?t=1927113
jje
JJEgan said:
Use XDA instructions .
http://forum.xda-developers.com/showthread.php?t=1671969
BASICS
http://forum.xda-developers.com/showthread.php?t=1927113
jje
Click to expand...
Click to collapse
Thnx a lot buddy:good:. Will check and let you know how it went. Maybe post in that same thread for more help
Hey buddy "JJEgan". Tried what you had mentioned. Went to the respective threads and did exactly what was advised in them. But the end result was the same.
This time around I used an older ver of ODIN 3.04. This time the update process moved ahead a bit more. But after a while I got an error msg:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXDLK1_I9300ODDDLI7_I9300DDDLJ1_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..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> system.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
I'm not sure what to make out about the issue. At wits end. Could you help me find a solution?
Sudden death, your NAND is dead, replace the motherboard under warranty
anirmj said:
Hey buddy "JJEgan". Tried what you had mentioned. Went to the respective threads and did exactly what was advised in them. But the end result was the same.
This time around I used an older ver of ODIN 3.04. This time the update process moved ahead a bit more. But after a while I got an error msg:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXDLK1_I9300ODDDLI7_I9300DDDLJ1_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..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> system.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
I'm not sure what to make out about the issue. At wits end. Could you help me find a solution?
Click to expand...
Click to collapse
Try this ,
1. go to http://checkrom.com download the latest resurrection rom , make sure you have usb drivers installed
2.go into download mode in your phone and flash this rom through odin 3.04 ( administrator mode)
3.once everything is done it should boot into cwm recovery after that wipe data/factory rest and wipe cache partition and then reboot system
4. if everything goes well it should boot into the resurrection rom
Good Luck!
why would resurrection work if the stock rom didn't?
Glebun said:
why would resurrection work if the stock rom didn't?
Click to expand...
Click to collapse
when i had a bootloop .. the stock rom didnt work but when i flashed the resurrection rom it did .. so maybe it may work for him too .
Just wanted to ask. Are there any other options that I might have before taking the mobile to the customer care?
I have read somewhere that a PIT file could resolve issues. Can that work in this scenario? If so, which file to use and what are the perils of using such a file?
Also, buddy "galaxy3lover", when you talk about resurrection rom, can you guide me to the exact FW that you are talking about? The link that you have provided contains a lot of links. Which one should I download from?
http://checkrom.com/download/ scroll down gt - 19300 if you are using the international model ... and then checkrom v6.zip
galaxys3lover: Tried ur resurrection rom, but its a no go.
Other than that also tried the PIT file/re-partitioning method but that too failed.
Searched a lot but couldn't find any other methods for my soft brick. So, is it really game over, even though mine is not a hard brick? Isn't there any other way to fix the issue?
Well if the nand and bootloaders are fine, Odin should be able to just flash it.
Try Kies firmware initialization
xSpeced said:
Well if the nand and bootloaders are fine, Odin should be able to just flash it.
Try Kies firmware initialization
Click to expand...
Click to collapse
Yeah, no harm in trying that as well. Its interesting to note that where ODIN failed can KIES come to the rescue?
Stay tuned for the answer
No even KIES turned out to be a dead end. It begun and stopped with an error. Tried emergency recovery but failed again.
Guess the only option left for me now is take it to the Service Center...
anirmj said:
No even KIES turned out to be a dead end. It begun and stopped with an error. Tried emergency recovery but failed again.
Guess the only option left for me now is take it to the Service Center...
Click to expand...
Click to collapse
You have void warranty so be prepared .
jje
JJEgan said:
You have void warranty so be prepared .
jje
Click to expand...
Click to collapse
Yeah, I always knew about that final outcome
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 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
Hi XDA.
There are several thread about PIT/Partition/ brick/ mounting problem etc.
i spent over 2 days to fix my international GT-I9300 16GB white.
i think there is not much left about PIT on not only XDA but on other websites. Which I didn't read.
some of them are scary like. don't check partition box in odin or motherboard will be dead or that's it your phone is junk/ send it to service center. blah blah blah........
but all you need to do is downgrade you boot loader..........yes.***********THAT'S IT*********
tried millions of method (yes almost million) but nothing work. and i don't want to anyone else spend that much time on it
(back on topic)
here is how i did it.
download all files at last of this post
1. Put your phone on download mod (volume down+home button+power and than volume up)
2.open odin and select option *auto reboot*re-partition*f.reset time *Nand erase all(don.t worry just do it*unless you have other option*)
3.select **GT-I9300.PIT** as pit file(DO NOT SELECT ANY OTHER ONE)
4. click start(after finishing task phone will reboot )
5.now download CF-Root for SGS3 v6.4 from here-------> http://forum.xda-developers.com/showthread.php?t=1695238
6. again put phone in download mode and root your phone with CF-Root (file you downloaded)
7.now put ***Restore_Bootloader_XXBLFB** ZIP file on your sd card and flash it using phone recovery (cwm)
8.now download any 3 part official firmware for your phone and flash with odin ..
that's it
method above worked for me on my SAMSUNG GALAXY S3 GT-I9300 WHITE 16 GB but i still take no responsibility
for any damage to your phone or to your Dog/cat during process.
Thank you
Hope it'll work for you
sorry for my bad english.
In your post you link to the Old rooting method from Chainfire he hasn't supported that thread for around a year now, he moved to a new version of rooting, link is in my signature that is the better rooting method to use unless with your process it requires that you use the old rooting method.
Yes my process required this old root TAR file as it comes with cwm recovery. The new one does not. And as I mentioned up you need recovery to flash bootloader. So in this way you saving time to flash recovery after rooting.
Anyway after recovering your phone you can use new root file from chainfire to re root 3 part firmware which you flashed in recovering process.
Enjoy android
ManojKBanga said:
Yes my process required this old root TAR file as it comes with cwm recovery. The new one does not. And as I mentioned up you need recovery to flash bootloader. So in this way you saving time to flash recovery after rooting.
Anyway after recovering your phone you can use new root file from chainfire to re root 3 part firmware which you flashed in recovering process.
Enjoy android
Click to expand...
Click to collapse
Partition Info flashing[PIT] works but bootloader is a problem! ANy other option to may the system works as earlier???
This zipped can not be flashed from Stock Recovery. It says its signature can not be verified! I do not know what to do now. Can not get my bluetooth bhai!
You need CWM recovery to flash this file. Read carefully bhaisaab
and iam not sure what you mean bluetooth not working. Explain more.
ManojKBanga said:
You need CWM recovery to flash this file. Read carefully bhaisaab
and iam not sure what you mean bluetooth not working. Explain more.
Click to expand...
Click to collapse
Sorry for not seeing CWM. I am using stock recovery! Bluetooth icon has gone into gray color, I can not make it green[try to turn ON, it will go to OFF position]. Above all, my csc folder is missing. May be it's the culprit!
found csc folder by making my IMEI into that 049... by flashing ITV rom explains in other thread. I didn't worry much I know I will get back IMEI as I didn't break my efs. flash back thereafter 4.3 swc then to indian xxemh4 4.1.2. my network, wifi, gprs work fine, I got my CSC folder back.
but I still have my Bluetooth non functional and mobile is as laggy as that of 4.3.
another problem is both UART & USB change automatically to modem everytime phone booted!
Hi! I'd like to try your method, but this is what happens in the first step:
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Erase...
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I can not flash anything. My phone, as I've read is not bricked, just semibricked.
Thanks in advance!
THX
thx a lot, i solved the problem on my s3
SOLVED
SignalX said:
my phone is International GT-i9300 16gig White too
i have access to download mod only, there's no recovery menu
after doing 1 - 4 steps according to the first post, when i want to do step 5 & 6 [flashing CF-Root] i'll get this error in Odin:
{
"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"
}
and this is what my phone show:
anyone knows what should i do now?
Click to expand...
Click to collapse
You say your phone is international GT-19300 but in your photo of download mode it say's product name SGH-T999
Plz delete........
Mementii said:
Hi! I'd like to try your method, but this is what happens in the first step:
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Erase...
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I can not flash anything. My phone, as I've read is not bricked, just semibricked.
Thanks in advance!
Click to expand...
Click to collapse
Same problem here, any help?
Thnx in advance
ManojKBanga said:
Hi XDA.
There are several thread about PIT/Partition/ brick/ mounting problem etc.
i spent over 2 days to fix my international GT-I9300 16GB white.
i think there is not much left about PIT on not only XDA but on other websites. Which I didn't read.
some of them are scary like. don't check partition box in odin or motherboard will be dead or that's it your phone is junk/ send it to service center. blah blah blah........
but all you need to do is downgrade you boot loader..........yes.***********THAT'S IT*********
tried millions of method (yes almost million) but nothing work. and i don't want to anyone else spend that much time on it
(back on topic)
here is how i did it.
download all files at last of this post
1. Put your phone on download mod (volume down+home button+power and than volume up)
2.open odin and select option *auto reboot*re-partition*f.reset time *Nand erase all(don.t worry just do it*unless you have other option*)
3.select **GT-I9300.PIT** as pit file(DO NOT SELECT ANY OTHER ONE)
4. click start(after finishing task phone will reboot )
5.now download CF-Root for SGS3 v6.4 from here-------> http://forum.xda-developers.com/showthread.php?t=1695238
6. again put phone in download mode and root your phone with CF-Root (file you downloaded)
7.now put ***Restore_Bootloader_XXBLFB** ZIP file on your sd card and flash it using phone recovery (cwm)
8.now download any 3 part official firmware for your phone and flash with odin ..
that's it
method above worked for me on my SAMSUNG GALAXY S3 GT-I9300 WHITE 16 GB but i still take no responsibility
for any damage to your phone or to your Dog/cat during process.
Thank you
Hope it'll work for you
sorry for my bad english.
Click to expand...
Click to collapse
I tried all that but it gets stuck at <ID:0/012> Added!!
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Erase...
did anyone succeed ?
having same issue (write operation fails) any help
_Choy said:
Same problem here, any help?
Thnx in advance
Click to expand...
Click to collapse
I'm also having this trouble with my GT-i9300 16GB
Same trouble!!!
This happenned to me too..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Erase...
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any Solution????
help
Mementii said:
Hi! I'd like to try your method, but this is what happens in the first step:
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Erase...
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I can not flash anything. My phone, as I've read is not bricked, just semibricked.
Thanks in advance!
Click to expand...
Click to collapse
hi I get the same prablem how did u fix this prablem please
nassiry said:
hi I get the same prablem how did u fix this prablem please
Click to expand...
Click to collapse
this problem can only be fixed with box us z3x or riff box
Same unsolving problem here
I can't get rid of "Complete(Write) operation failed" too (samsung galaxy i9300).
Can't do nothing on Odin 3 , with PIT file or CF-root
Odin FAIL !
HELP ! SOS !
On CWM Clock Work Mod Recovery, the message trying to reset / wipe factory data is "E:Can't mount /cache/recovery/"
romuloff said:
I can't get rid of "Complete(Write) operation failed" too (samsung galaxy i9300).
Can't do nothing on Odin 3 , with PIT file or CF-root
Odin FAIL !
HELP ! SOS !
On CWM Clock Work Mod Recovery, the message trying to reset / wipe factory data is "E:Can't mount /cache/recovery/"
Click to expand...
Click to collapse
as i know, you have a problem with motherboard or emmc chip, need replacement.
i have one with the very same problem you have described
{
"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"
}
TWRP 3.1.0-0 Released
Mar 10, 2017
https://twrp.me/site/update/2017/03/10/twrp-3.1.0-0-released.html
Below you will find my builds of TWRP custom recovery for the Tab A. Latest build is 3.1.0-1
I have updated SM-T350/355 and SM-T550/T555 to TWRP v3.1.0-1.
Disclaimer: you flash these at your own risk. Knox counter will be tripped. Having the stock firmware to hand is also advised.
Update 13/3/2017: New TWRP 3.1.0-1 build for Marshmallow. Reboot to recovery loop, finally fixed!
Update: New TWRP 3.0.2-1 build for Marshmallow. Touch issues now properly fixed.
Instructions:
Flash with ODIN 3.10.7 in the AP slot.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding the other buttons.
You should now see TWRP recovery.
FAILURE TO IMPLICITLY FOLLOW THE ABOVE WILL RESULT IN TWRP BEING REPLACED WITH STOCK RECOVERY. I WILL NOT ENTERTAIN ANY POSTS RESULTING FROM FAILURE TO PAY ATTENTION TO THE ABOVE
NOTE: ON SOME ANDROID 5.1.1/6.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
LOLLIPOP:
TWRP 2.8.7.0
SM-T350
www.androidfilehost.com/?fid=24052804347801968
SM-T355
www.androidfilehost.com/?fid=24052804347801969
SM-T357
www.mediafire.com/download/w9u33fap6lk14pm/twrp-2.8.7.0-t357.tar
SM-T550
www.androidfilehost.com/?fid=24052804347801970
SM-T555
www.androidfilehost.com/?fid=24052804347801971
SM-P550/P555
www.androidfilehost.com/?fid=24052804347803920
SM-P350/P355
www.androidfilehost.com/?fid=24052804347829376
TWRP 3.0.2-1
twrp_3.0.2-1_sm-t555
MARSHMALLOW ONLY
TWRP 3.0.2.1
twrp_3.0.2-1_sm-t350_mm_9816
twrp_3.0.2-1_sm-t355_mm_9816
twrp_3.0.2-1_sm-t550_mm_7816
twrp_3.0.2-1_sm-t555_mm_5816
twrp_3.0.2-1_SM-P550_mm_15816
twrp_3.0.2-1_SM-P555_mm_15816
MARSHMALLOW ONLY
TWRP 3.1.0-1
twrp_3.1.0-1_sm-t350_18317
twrp_3.1.0-1_sm-t355_16317
twrp_3.1.0-1_sm-t550_13317
twrp_3.1.0-1_sm-t555_13317
NOUGAT
TWRP 3.1.1-1
twrp_3.1.1-1_sm-t355_251117
To root.
Flash the latest supersu below with twrp.
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Device tree: github.com/ashyx/
PLEASE LEAVE FEEDBACK IF YOU FIND MY WORK USEFUL. THANKS.
Read more: http://galaxy-tab-a.boards.net/thread/6/recovery-twrp-t350-355-p355#ixzz4FXGLWDE8
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
Update: New TWRP builds for Marshmallow. Touch issues now properly fixed.
twrp_3.0.2-1_sm-t550_mm_7816
twrp_3.0.2-1_sm-t555_mm_5816
i tried to flash the newest MM version on my SM-T550, but i get this:
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1100)..
<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> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Size)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
twrp for p555 mashmallow?
pwild said:
i tried to flash the newest MM version on my SM-T550, but i get this:
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1100)..
<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> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Size)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
FIXED, https://www.androidfilehost.com/?fid=24591000424952906
ashyx said:
FIXED, https://www.androidfilehost.com/?fid=24591000424952906
Click to expand...
Click to collapse
Thank you! now its working.
stayfidz said:
twrp for p555 mashmallow?
Click to expand...
Click to collapse
In the works.
.
Can someone post up the SM-T350/355 P550/555 stock MM recovery images?
Specifically I could do with the SM-T350 first.
ashyx said:
Can someone post up the SM-T350/355 P550/555 stock MM recovery images?
Specifically I could do with the SM-T350 first.
Click to expand...
Click to collapse
As usual nobody bothers.
UPDATE: TWRP for the SM-T350 (Marshmallow only)
https://www.androidfilehost.com/?fid=24591000424953305
ashyx said:
As usual nobody bothers.
UPDATE: TWRP for the SM-T350 (Marshmallow only)
https://www.androidfilehost.com/?fid=24591000424953305
Click to expand...
Click to collapse
Can I flash which twrp for SM-P550 Marshmallow? Thanks.
tuuquy said:
Can I flash which twrp for SM-P550 Marshmallow? Thanks.
Click to expand...
Click to collapse
Lollipop version may still work on MM for P550.
Thanks for the great efforts..
Can the twrp for SM T355 mm be used for SM T355Y mm?
+1
semantsen said:
Thanks for the great efforts..
Can the twrp for SM T355 mm be used for SM T355Y mm?
+1
Click to expand...
Click to collapse
I would expect so.
Recovery image for SM T355Y mm
https://mega.nz/#!05g3EDYQ!ye6Pyn1WX4WDDfj0HQqDzLatvPWkkHWi8NldxvwtFio
semantsen said:
Recovery image for SM T355Y mm
https://mega.nz/#!05g3EDYQ!ye6Pyn1WX4WDDfj0HQqDzLatvPWkkHWi8NldxvwtFio
Click to expand...
Click to collapse
Are you saying it didn't work?
ashyx said:
Are you saying it didn't work?
Click to expand...
Click to collapse
I did not try it yet. I will try and let you know.
---------- Post added at 10:24 PM ---------- Previous post was at 09:26 PM ----------
Well!
SM T355 mm TWRP also works well for SM T355Y mm. :good:
I did root afterwards,
Thanks,
+1
Does anyone have to TWRP for the p550 Marshmallow? i tried all the others and they don't work.
cannot boot system
Yesterday I successfully flashed twrp for my tab (sm t355y)
I flashed supersu and used titanium and debloated and got a space of upto 850 mb
Then as a convenience I downloaded Quick Reboot from play store
using Quick Reboot I successfully entered recovery mode
There started the problem
I tried reboot to system but again rebooted to twrp only!
I switched off and tried but it always went to twrp.
I tried twrp file browser but it did not show system
as a last resort I had to flash stock rom and booted to system
now the question is what could have caused this? I doubt I should not have used Quick Reboot. Should I have used button sequence? Shall try again and see..
semantsen said:
Yesterday I successfully flashed twrp for my tab (sm t355y)
I flashed supersu and used titanium and debloated and got a space of upto 850 mb
Then as a convenience I downloaded Quick Reboot from play store
using Quick Reboot I successfully entered recovery mode
There started the problem
I tried reboot to system but again rebooted to twrp only!
I switched off and tried but it always went to twrp.
I tried twrp file browser but it did not show system
as a last resort I had to flash stock rom and booted to system
now the question is what could have caused this? I doubt I should not have used Quick Reboot. Should I have used button sequence? Shall try again and see..
Click to expand...
Click to collapse
I've heard of the issue before when using reboot utilities.
If it happens again reflashing twrp with autoreboot enabled should reset the flag.
ashyx said:
I've heard of the issue before when using reboot utilities.
If it happens again reflashing twrp with autoreboot enabled should reset the flag.
Click to expand...
Click to collapse
So one thing is clear. Quick Reboot caused this.
No use of reboot utility. Only button sequence to boot twrp.
Now I am on stock recovery. Will have to re flash and use button sequence only..
Thanks,
{
"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