Database Users

[ROM] Generic (America) arc S/LT18a v2.3.4/4.0.2.A.0.42

For the few people who have LT18a (NAM) arc s phones.
Generic, unbranded American (NAM) Xperia arc s/LT18a ROM extracted through Update Service, run through SEUSdecrypt, repackaged with Bundle Package in Flash Tool.
Version: v2.3.4, 2011 December
Baseband: 8x55A-AAABQOAZM-20328D-56
Kernel: 2.6.32.9-perf [email protected] #1
Build: 4.0.2.A.0.42 [upgradeable over-the-air to build .62 while maintaining root]
{
"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"
}
NOTE: All 2011 Xperia firmwares EXCEPT build .62 can now be rooted directly using DooMLoRD's zergRush:
This works on ANY Xperia arc S (LT18a/i).
Your arc S does NOT have to be rooted.
Your arc S does NOT have to be bootloader unlocked.
This does NOT re-lock a SIM unlocked phone (unlocking is ONCE and PERMANENT).
This does NOT unlock your bootloader.
This WILL wipe your phone & root. Backup first.
You MUST have BOTH PC Companion and Update Service installed. MIRROR: http://jp1.ca/androidstuff
Download: http://www.mediafire.com/?br23299mb2l27 (262.27 MB, single flashtool file)
Please do NOT mirror files.
Also confirmed using TrevE's Logger Test App that this firmware does NOT contain the privacy invading rookit by Carrier IQ.

Is this the general ROM (no shi* installed)?
Thanks

Unablept said:
Is this the general ROM (no shi* installed)?
Thanks
Click to expand...
Click to collapse
That's what "Generic, unbranded..." means...

ROM for LT18i generic unbranded
If i update to this ROM would i be able to connect my cell to 3G connection. The thing is i bought this on ebay in Singapore and when it comes i realized that bands in america are different. however i read before that this cellphone is quadriband and that supposed to make it available to connect but i needed to changed the ROM somehow. Can this Rom change that? thanks.

Can you make me a favor?
- Flash using Wotan client.
- Repair using SEUS (just to download files in blob_fs folder.
- decrypt and create bundle from SEUS files in blob_fs
?
I just want to check if SEUS will repair it, my LT18a is prototype, so can you try to do it? I'm not sure about the SI numbers for US generic If you be so kind, I really appreciate it, if you want I will pay $$ Paypal just for the help.

E15i said:
Can you make me a favor?
- Flash using Wotan client.
- Repair using SEUS (just to download files in blob_fs folder.
- decrypt and create bundle from SEUS files in blob_fs
?
I just want to check if SEUS will repair it, my LT18a is prototype, so can you try to do it? I'm not sure about the SI numbers for US generic If you be so kind, I really appreciate it, if you want I will pay $$ Paypal just for the help.
Click to expand...
Click to collapse
SEUS always repairs phones, regardless of whatever firmware is on it.
However, it will not always download the current firmware you have on the phone. It may download your region's current firmware.

Toymaker0 said:
If i update to this ROM would i be able to connect my cell to 3G connection. The thing is i bought this on ebay in Singapore and when it comes i realized that bands in america are different. however i read before that this cellphone is quadriband and that supposed to make it available to connect but i needed to changed the ROM somehow. Can this Rom change that? thanks.
Click to expand...
Click to collapse
No, it will not change the hardware of your phone. It is probably quadband, but that doesn't mean it has the correct band. It will not work on AT&T, maybe TMo, but I am not sure. It all comes down to hardware and SIM card, not so much ROM.
I have a LT18a Arc S that works on AT&T 3G here in the US. LT18i = international, LT18a = Americas (and possibly a hand full of other countries). I'm relocating to Singapore next month for a while, I have my fingers crossed that it will get 3G there. I can't seem to find what bands the Singapore carriers use. Then again I haven't really looked too hard. If it doesn't work, I'm sure I can find something over there worth buying.

In the end I used 4SE from simlock.com, they have a GEL and US variants, GEL=less bloatware, its Generic for Latin Americas.
Sent from my X10a using XDA App

Place bros... Reupload this file... Megaupload is dead i can download file snif, snif

Rod GTI said:
Place bros... Reupload this file... Megaupload is dead i can download file snif, snif
Click to expand...
Click to collapse
There are MULTIPLE upload sites... use another one.

All the new links given are dead
All the new links given are dead. Can you please upload it again preferably "Mediafire" would be very much appreciated. Thank you for you rkind atention and help.
BTW, I can you this tool to downgrade my LT18A from Adroid 2.3.4 build 4.0.2.A.0.62 to 4.0.2.A.0.42 rooted right?

Hey just to let you guys know that I can't hit any of the download sites. There all gone.
Cheers.

fluxgfx said:
Hey just to let you guys know that I can't hit any of the download sites. There all gone.
Cheers.
Click to expand...
Click to collapse
nhuii said:
All the new links given are dead. Can you please upload it again preferably "Mediafire" would be very much appreciated. Thank you for you rkind atention and help.
BTW, I can you this tool to downgrade my LT18A from Adroid 2.3.4 build 4.0.2.A.0.62 to 4.0.2.A.0.42 rooted right?
Click to expand...
Click to collapse
MediaFire has a 200MB limit. I'm uploading to another site. Will update the first post once the links are available.
You can flash any build as long as you don't downgrade from v2.3.4 to a lower version (v2.3.3 or v2.3.2).

Download link updated.

mate bluechipj...
can I use this to downgrade my arc s LT18i? it is currently on android version 2.3.4,baseband 64, build number 4.0.2.A.0.62
i just want to have a root access.
my plan is to downgrade to .42, then root with zergrush exploit or iclick rooting and lastly update via OTA to .62 and hopefully the root access is still there.
do you think this will work out? Coz ive just read from your thread on LT15i that some people are able to do it with their arc. but here on arc s, still no feedback if somebody able to do it. any idea mate? thanks in advance

waup said:
mate bluechipj...
can I use this to downgrade my arc s LT18i? it is currently on android version 2.3.4,baseband 64, build number 4.0.2.A.0.62
i just want to have a root access.
my plan is to downgrade to .42, then root with zergrush exploit or iclick rooting and lastly update via OTA to .62 and hopefully the root access is still there.
do you think this will work out? Coz ive just read from your thread on LT15i that some people are able to do it with their arc. but here on arc s, still no feedback if somebody able to do it. any idea mate? thanks in advance
Click to expand...
Click to collapse
Short answer: yes.
OTA updates maintain root. Will update post #1.
Flash .42, root with zergRush, force an OTA update in Settings / About.

originally posted by bluechipJ
Short answer: yes.
OTA updates maintain root. Will update post #1.
Flash .42, root with zergRush, force an OTA update in Settings / About.
Click to expand...
Click to collapse
so my model number will become LT18a on .42, if i successfully updated OTA will it go back to LT18i on .62? and whats the real difference between LT18a and LT18i? yeah, literally its the a and the i w/c is america and international, but what I mean is the phone itself,. Is there some changes in the phone settings or any functions? coz im afraid that it wont work (i mean the basic function of calling, texting and data internet) here in my country in asia. can you pls make it clear for me. thank you very much
and btw, is there any technique or procedure to successfully updated via OTA? coz ive read that some people claims that OTA is not available on their phone and the system says its already updated.

Any chance i can get LT18i? I did a mistake in my phone n goes to bootloop, after that, i flash it with this LT18a (my mistake not make backup for the stock rom). I dont hv any problem with this rom, but i think i need the LT18i rom if want to get warranty... ( my phone root but with locked BL). Thanks in advance
Sent from my LT18a using xda premium

waup said:
so my model number will become LT18a on .42, if i successfully updated OTA will it go back to LT18i on .62? and whats the real difference between LT18a and LT18i? yeah, literally its the a and the i w/c is america and international, but what I mean is the phone itself,. Is there some changes in the phone settings or any functions? coz im afraid that it wont work (i mean the basic function of calling, texting and data internet) here in my country in asia. can you pls make it clear for me. thank you very much
and btw, is there any technique or procedure to successfully updated via OTA? coz ive read that some people claims that OTA is not available on their phone and the system says its already updated.
Click to expand...
Click to collapse
As stated in the first post...
This works on ANY Xperia arc S (LT18a/i).
Click to expand...
Click to collapse
Any firmware can be flashed onto any phone and everything will work, including data. (Will require manual setup of Settings / Wireless / Mobile Networks / APN. Or backup your existing settings with APN Backup and Restore: https://market.android.com/details?id=com.riteshsahu.APNBackupRestore&hl=en) All firmwares contain both software radios for "i" and "a". However, hardware radios are fixed. You cannot make an LT18a into an LT18i by flashing firmware or vice versa. However, an LT18i will still get "i" 3G in an "i" zone with an "a" firmware and vice versa.
As long as there is an update available for the firmware (which there is for USA .42), you can update over the air while maintaining root as long as you have not modified or removed any system files.
e.g. changed themes, fonts, notification bar, widgets, etc.
If you install an "a" firmware, it will continue to update to the next "a" firmware and vice versa.
munjep said:
Any chance i can get LT18i? I did a mistake in my phone n goes to bootloop, after that, i flash it with this LT18a (my mistake not make backup for the stock rom). I dont hv any problem with this rom, but i think i need the LT18i rom if want to get warranty... ( my phone root but with locked BL). Thanks in advance
Click to expand...
Click to collapse
I don't have any saved LT18i firmwares but there are many more of them all over the forum (Hong Kong, Nordic, UK, etc.)
Download Wotan Server (free) and flash one.

how can I create the .ftf file out of LT18a file that you upload. coz its in RAR file format and contains the files that supposed to be the content of .ftf?

[FTF][Stock][4.4.2]Xperia Z2 Tablet SGP521 - LTE [17.1.A.2.69][1281-5556][Global]

My first ever contribution, always been a leech until now.
Instructions
Download from below
Flash with flashtool
Details
Device: Xperia Z2 Tablet - LTE
Model: SGP521
Version: 17.1.A.2.69 - stock
Customisation: 1281-5556 (Global LTE)
Changes - coming from 17.1.A.2.55
Probably not many, the last fw was 17.1.A.2.55 (only 14 iterations behind this), but judging by the speed they threw this out it probably fixes critical bugs/security
Vastly improved touch responsiveness (.36 = unusable, .55 = barely acceptable, .69 = pretty good!)
Much faster at everything (not tried benchmarking)
Let me know if there are other changes and I'll list them here
DISCLAIMER
Use at your own risk! I'm not responsible if your cat gets run over after (or before) you download my files, unless I'm driving in your area (I don't like cats).
Download
Mega.co.nz
dev-host part_1 part_2 part_3 [you need all 3 parts]
Torrent [removed due to low usage]
Screens
View attachment 2727439
View attachment 2727440

Stability seems to have degraded.
I never noticed any random reboots before in about 3 weeks of use, but I've just had one with this fw.

Ricky D said:
Stability seems to have degraded.
I never noticed any random reboots before in about 3 weeks of use, but I've just had one with this fw.
Click to expand...
Click to collapse
Can you share an about phone/tablet screenshot ? and software info screenshot also... ?

ImAnurag said:
Can you share an about phone/tablet screenshot ? and software info screenshot also... ?
Click to expand...
Click to collapse
Now included in first post

Is Root available for this FW?

UserX10 said:
Is Root available for this FW?
Click to expand...
Click to collapse
This FW is NOT rooted.
If you unlock your bootloader and use DooMLoRd's kernel then you can obtain root.
That at the minute is the ONLY way to root this device regardless of FW..

BUT - I already posted a question in this respect in Doomlord's CWM recovery thread - it is very much possible that Doomlord's kernel & recovery is NOT compatible with the .69 firmware! So... *eerie music* *ghostly voice* B R I C K D A N G E R!
As you can read in that thread, prerequisite is a .55 firmware.
But perhaps someone clears this up.

hasenbein1966 said:
BUT - I already posted a question in this respect in Doomlord's CWM recovery thread - it is very much possible that Doomlord's kernel & recovery is NOT compatible with the .69 firmware! So... *eerie music* *ghostly voice* B R I C K D A N G E R!
As you can read in that thread, prerequisite is a .55 firmware.
But perhaps someone clears this up.
Click to expand...
Click to collapse
Judging by the very small increment number between the two firmwares and without going and looking it up I would place a high probability that the base stock kernel hasn't been changed and would, therefore, custom kernel compatibility is implied.
If you have the .55 fw or can obtain a 'About tablet' page view from that fw, you can compare the kernel versions to the screen in the OP and take a gamble.
But, in my opinion, the risk of bricking low, assuming you don't do something out of the ordinary.

Ricky D said:
Judging by the very small increment number between the two firmwares and without going and looking it up I would place a high probability that the base stock kernel hasn't been changed and would, therefore, custom kernel compatibility is implied.
If you have the .55 fw or can obtain a 'About tablet' page view from that fw, you can compare the kernel versions to the screen in the OP and take a gamble.
But, in my opinion, the risk of bricking low, assuming you don't do something out of the ordinary.
Click to expand...
Click to collapse
Checked it with this FW .69 and the modified Kernel from DooMLoRD for the .55 Kernel. Worked like a charm...

This FW did fix touch screen issue a little bit, still the screen edge got very poor touch sensitive.

Anyone have sg512 ftf fw. 69? Can this be crossflashed? Thanks.
Sent from my SM-N900W8 using XDA Premium 4 mobile app

No, can't be crossflashed!
FTF must be for the exact model of the tablet.
Up to now only few people have the update, so we must wait for someone being so nice to upload an FTF...

Thanks.
Sent from my SM-N900W8 using XDA Premium 4 mobile app

Can anyone tell me the md5? I'm getting an error when starting flashing (checking header).
"Processing of loader.sin finished with errors."
I have drivers installed, no other errors. Using Windows 8.1 (unsigned drivers mode).
Edit: I didn't have USB debugging turned on. All good now. Flashtool should warn about that.
hasenbein1966 said:
No, can't be crossflashed!
FTF must be for the exact model of the tablet.
Up to now only few people have the update, so we must wait for someone being so nice to upload an FTF...
Click to expand...
Click to collapse
By exact model you just mean SGP521 right? Mine is 1281-1439 but that should be fine?

xsacha said:
By exact model you just mean SGP521 right? Mine is 1281-1439 but that should be fine?
Click to expand...
Click to collapse
SGP521 is the model
1281-1439 is the software customisation
This ftf will work with ANY SGP521, but will change the customisation to 1281-5556. If you have any network provided or region specific apps preinstalled on your fw you will NOT have those in the new fw as this is a 'generic global' fw meaning bare bones for worldwide release.

Does the bootloader need to be unlocked for flashtool to work?
Also where does one find that software number 1280-xxxx i can't find it anywhere

pyro2677 said:
Does the bootloader need to be unlocked for flashtool to work?
Also where does one find that software number 1280-xxxx i can't find it anywhere
Click to expand...
Click to collapse
Bootloader status has no relevance when using ftf files in flashtool, nor will it change the status of your bootloader.
The software customisation number is in the 'secret' service menu. To access it open the dialer and dial
Code:
* # * # 7 3 7 8 4 2 3 # * # *
equal to:
* # * # S E R V I C E # * # *
You should fin the customisation in there somewhere.

AWESOME, just what i wanted to hear. Legend going to update since i'm still stuck on .36 and it's not updating for me.

If you have any network provided or region specific apps preinstalled on your fw you will NOT have those in the new fw as this is a 'generic global' fw meaning bare bones for worldwide release.
Click to expand...
Click to collapse
So does this mean I will get trouble with the Xperia Lounge App in terms of region-specific content that won't be offered?

take55 said:
So does this mean I will get trouble with the Xperia Lounge App in terms of region-specific content that won't be offered?
Click to expand...
Click to collapse
To be honest I'm not sure. I don't use Xperia Lounge.
The app could obtain your region information in a number of ways:
The network you're connected to (including foreign networks when roaming)
The network associated with your SIM card
Your WAN IP location
GPS location
FW customisation region
The SIM and network methods would only work if the device is a LTE/HSPA+ device and has a SIM card inserted so is highly unlikely.
The FW Customisation is also prone to errors as I'm certain Sony know some handsets are moved across regions, also regions could be quite wide stretching making pushed local content irrelevant.
IP location and GPS location seem like the most likely methods of determination, at least if I were writing the app I'd use one of these.
If I'm right then the customisation will NOT affect your local content offered through Xperia Lounge.
Finally, the region coding is only relevant to Sony so it is senseless for 3rd party apps to use the region codes, therefore, all 3rd party apps should be unaffected by changing of the region customisation.
**All above to the best pf my knowledge but even I am wrong sometimes**

[HOW-TO][FIX] Fix No Network/Baseband Missing/No IMEI

Fix No Network/No SIM Registered/IMEI Missing/Baseband Missing​
The Problem
On flashing a certain ROM, Kernel or both, some users experience one of the following:
No network signal.
Dialing *#06# shows blank IMEI number.
Unknown Baseband version in the About Phone page of settings.
No SIM Card registered.
How to Fix
There are four options:
Try restoring a Nandroid Backup of a previously working ROM.
Flash stock baseband using Flashtool.
Download and install FlashTool from HERE.
Download the Stock FTF Files from HERE.
Open FlashTool and boot your phone into Flashmode.
Choose the downloaded firmware and exclude all except Baseband as shown in the figure below. You can choose whether to wipe your data/cache.
{
"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"
}
Click next and wait for the flashing to be done.
Use the Baseband fix by @dipesh1502.
Download and flash the following ZIP using CWM/TWRP/Philz.
Download it HERE
Thanks to @dipesh1502 for creating this Flashable ZIP.
Alternatively, I've created an FTF for Xperia SP C5302 variant having only Baseband (<1MB). You can download it from HERE.
Flash it using Flashtool.
Hopefully the Baseband problems would be solved by doing any one of the above four fixes!
Hit Thanks if I Helped YOU, my friend!! :angel:​

Moved

or you can reflash rom via CWM Touch or TWRP, not Philz, at leat it works for me

cipetonk said:
or you can reflash rom via CWM Touch or TWRP, not Philz, at leat it works for me
Click to expand...
Click to collapse
I've tried that but with no result. I tried flashing all the ROMs that I had at that time with no luck! Glad that it works for you though

I can't fix the issue until I flashed C5303 Baseband (Generic SG, my own FTF), and resulted in stuck at C5302 Indian 12.1.A.1.201 (not receiving 12.1.A.1.205). Compilation of Indian FTF may have tons of issue, as USA C5302 FTF does work perfectly on my C5303.

chewlohseng said:
I can't fix the issue until I flashed C5303 Baseband (Generic SG, my own FTF), and resulted in stuck at C5302 Indian 12.1.A.1.201 (not receiving 12.1.A.1.205). Compilation of Indian FTF may have tons of issue, as USA C5302 FTF does work perfectly on my C5303.
Click to expand...
Click to collapse
I guess different variants of Xperia SP have different basebands. So you can't fix the issue until you flash its own baseband. Correct me if I'm wrong.
And I don't know about the difference in FTFs of different regions. I've used only Indian FTFs so far.

Vinay_FXG said:
I guess different variants of Xperia SP have different basebands. So you can't fix the issue until you flash its own baseband. Correct me if I'm wrong.
And I don't know about the difference in FTFs of different regions. I've used only Indian FTFs so far.
Click to expand...
Click to collapse
I wish it is, but I saw a C5302 user flashing Indian .207 update for C5302 and got the same problem.
Also it's pretty weird that my SP (C5303) flashing USA .201 and .205 for C5302 HSPA+ works perfectly with no baseband problem. While both can't run when I flash Indian C5302. More like compilation have issue because with USA and SGP FTF (SGP is mine), verification is automatically disabled while Indian version is enabled. Based on what I saw when tryingbto compile FTF, any Android version after 4.0.x, will have to disable verification checks while compiling and also when flashing. I disabled verification check while flashing Indian C5302 FTF manually and it fails every time. Maybe it's time for fix, as if this continues it'll annoy darn lots of users because of baseband issue and thus SIM not detected.
P.S. Sorry for long post. Just to get my point across clearly as far as I can.

http://forum.xda-developers.com/showthread.php?p=49196336
Follow second option....it worked for me

chewlohseng said:
I wish it is, but I saw a C5302 user flashing Indian .207 update for C5302 and got the same problem.
Also it's pretty weird that my SP (C5303) flashing USA .201 and .205 for C5302 HSPA+ works perfectly with no baseband problem. While both can't run when I flash Indian C5302. More like compilation have issue because with USA and SGP FTF (SGP is mine), verification is automatically disabled while Indian version is enabled. Based on what I saw when tryingbto compile FTF, any Android version after 4.0.x, will have to disable verification checks while compiling and also when flashing. I disabled verification check while flashing Indian C5302 FTF manually and it fails every time. Maybe it's time for fix, as if this continues it'll annoy darn lots of users because of baseband issue and thus SIM not detected.
P.S. Sorry for long post. Just to get my point across clearly as far as I can.
Click to expand...
Click to collapse
Thanks for the info!! Itss time for me to try out the USA firmwares

Vinay_FXG said:
I guess different variants of Xperia SP have different basebands. So you can't fix the issue until you flash its own baseband. Correct me if I'm wrong.
And I don't know about the difference in FTFs of different regions. I've used only Indian FTFs so far.
Click to expand...
Click to collapse
can you direct me the link of 12.1.A.1.207 fw for india .... i couldnt find it on stock firmware thread

To my knowledge there is no FTF for .207, at least I've not seen any. It is an OTA update i guess. I guess you'll have to flash .205 for now [emoji106]

Nice tutorial :fingers-crossed:

Levered said:
Nice tutorial :fingers-crossed:
Click to expand...
Click to collapse
Thanks bro [emoji4]

Thanks a lot bro .. the last option worked like a charm..!!!!!!

HorNy555 said:
Thanks a lot bro .. the last option worked like a charm..!!!!!!
Click to expand...
Click to collapse
Really glad that it worked for you :fingers-crossed:

Vinay_FXG said:
Fix No Network/No SIM Registered/IMEI Missing/Baseband Missing​
The Problem
On flashing a certain ROM, Kernel or both, some users experience one of the following:
No network signal.
Dialing *#06# shows blank IMEI number.
Unknown Baseband version in the About Phone page of settings.
No SIM Card registered.
How to Fix
There are four options:
Try restoring a Nandroid Backup of a previously working ROM.
Flash stock baseband using Flashtool.
Download and install FlashTool from HERE.
Download the Stock FTF Files from HERE.
Open FlashTool and boot your phone into Flashmode.
Choose the downloaded firmware and exclude all except Baseband as shown in the figure below. You can choose whether to wipe your data/cache.
Click next and wait for the flashing to be done.
Use the Baseband fix by @dipesh1502.
Download and flash the following ZIP using CWM/TWRP/Philz.
Download it HERE
Thanks to @dipesh1502 for creating this Flashable ZIP.
Alternatively, I've created an FTF for Xperia SP C5302 variant having only Baseband (<1MB). You can download it from HERE.
Flash it using Flashtool.
Hopefully the Baseband problems would be solved by doing any one of the above four fixes!
Hit Thanks if I Helped YOU, my friend!! :angel:​
Click to expand...
Click to collapse
Does this fix works whith xperia Z1?

weiderwin said:
Does this fix works whith xperia Z1?
Click to expand...
Click to collapse
You can use the FTF file for the Z1 and flash only the baseband! Options 3 & 4 are exclusively for XSP. :fingers-crossed:

Vinay_FXG said:
You can use the FTF file for the Z1 and flash only the baseband! Options 3 & 4 are exclusively for XSP. :fingers-crossed:
Click to expand...
Click to collapse
I did it but it does't work

thanks man it's a very Hopefully
I use option 4 and my Baseband problem solved :good:

What to do with BaseBand Fix.zip
3. Use the Baseband fix by @dipesh1502.
Download and flash the following ZIP using CWM/TWRP/Philz.
Download it HERE
Thanks to @dipesh1502 for creating this Flashable ZIP.
4. Alternatively, I've created an FTF for Xperia SP C5302 variant having only Baseband (<1MB). You can download it from HERE.
Flash it using Flashtool.
Click to expand...
Click to collapse
BaseBand Fix.zip from step from above contains 2 folders (System and META-INF); What do you do with either this zip file or its contents. For sure it does not go into the firmwares folder (since it is not picked up by the flashtool). The same thing goes for the alternate method of step 4; placing that in the firmwares folder yields nothing - it is not listed in the flashtool thereafter. I have the latest version of the tool and also the version prior to that. Please say what I am doing wrong because obviously I am doing something crazy

[GUIDE]ROOT Your LG Marshmallow ROM With Systemless ROOT. No More ExFAT Issues!

This is not a fix for already persisting issues. If you're currently dealing with ExFAT (or BT) issues, Systemless ROOT will not help you. Bring your device in a state where you don't have these issues by flashing a stock ROM matching exactly your variant and location. Then use Systemless ROOT using a custom recovery.
Unlocked Bootloaders Only
Confirmed working by me on a H815-EUR bought in Germany.
UPDATE: Confirmed to be working on following MM ROMs:
H815 EUR 20A/C/D Germany
H815 EUR 20B Poland
H815 EUR 20A Croatia
Please report if this works for you according to this scheme: H815-EUR-20A-GERMANY
Legend
Blue: Device Model
Black: Device region
Red: Firmware Version
Green: Location
Simple:
After flashing or updating to a stock LG MM ROM, boot into TWRP and flash Chainfire's Systemless ROOT 2.67. It'll automatically backup, patch and flash the Kernel. It'd be great if you could confirm by giving details about your device, e.g. "H815-EUR Germany" or "H815-EUR Poland" etc.
As stated by @Chainfire in his thread:
If you are coming from a SuperSU install in /system, you must re-flash the stock system partition contents prior to installing this.
If you are coming from a SuperSU system-less install, you must re-flash the stock kernel prior to installing this.
If TWRP tells you SuperSU is not installed, and asks you to install it, do not do it, you will break things!
Future updates will be significantly less painful
Click to expand...
Click to collapse
With the introduction of TWRP 3.X.X., this is no longer an issue. TWRP will no longer ask to install SuperSU if it detects a Marshmallow ROM.
For G4 (H815) users:
You have to reflash the latest stock KDZ or .zip (modem, system, boot - restart recovery - bootloader) if you're currently dealing with exFAT issues. Then you can fire up TWRP and flash Systemless ROOT 2.67.
The reason why you might want to use this method to root instead of simply flashing a pre-patched Kernel is differences in ROM versions. As it happened to me, on my H815-EUR from Germany, I received the MM update. It was called "20A" for some reason, but it has the same fixes and updates as 20B. So it's not to be confused with the early 20A build from Poland! Quick as I am, I flashed the repacked boot.img for 20A by @cile381 and lost exFAT support, and somehow corrupted ADB, since cile381's repacked kernel was built from and for the Poland 20A build.
I hope this'll help you =)

Great, but if it's not necessary to flash a modified boot image anymore, do we could have root permission with Android MM, by flashing a modified system image (with supersu injected) by using the DD method with Android 5.1 running? This can be helpful for people who can't unlock the bootloader

Andrea__93 said:
Great, but if it's not necessary to flash a modified boot image anymore, do we could have root permission with Android MM, by flashing a modified system image (with supersu injected) by using the DD method with Android 5.1 running? This can be helpful for people who can't unlock the bootloader
Click to expand...
Click to collapse
No, that's not true. You still need a modified boot.img. With this method, you basically create your very own patched kernel, from the boot.img extracted from your very device.
MM still requires a patched/repacked kernel.
EDIT: Ok, now I see where the confusion came from. Misleading title.

thank you ! very useful ...
i have a question :
why ,with a phone (bootloader unlocked) with MM 6 ,it's possible to easily have a root .......but the locked device no ? ===> but instead of use TWRP , by injecting only the SuperSU with adb fastboot (or kdz pack?) for locked device???

Basically, Marshmallow has very strict security restrictions. The stock kernel won't allow any modifications. That's why we need a modified (vulnearable) one. You can simply flash a modified kernel onto a bootloader unlocked device. But since you can't flash custom boot.img's on locked devices, people with non-unlockable devices currently have no way to root their MM devices.
More details can be found in this XDA article.

very very interesting what you have said ,thank you for sharing and help
i didn't know MM...
that's mean ther NEVER have a chance for a root of MM with locked bootloader !!! if i have correctly understood ...
the only way is to unlock this damned bootloader ......or downgrade to LP by LG-UP (kdz) and then root with fastboot method ??? i'm true ???
i just discover this LG G4
in the past i have had a LG optimus series ...with old methods and full possibilities !
i begin to believe that it's the begining of the dead of android development if all manufacturers and google "lock" and add too many securities on these news devices with "hard" methods ...

Haha, sure! You're welcome =)
I wouldn say "never". There's always a chance that a genius will find a way. You also need to factor in the relatively young age of the G4.
To the last part: Yeah, it's getting harder and harder. But nothing unexpected. Remember, power users like us do only make up a very small, almost insignificant amount of all the Android users out there. I'm sure most people don't even know what Android is. Google just went full on Spock and said "Thee needs of the many outweigh the needs of the few or the one" :laugh:

ho my god ...sh** ........
imagine the future LG G5 (and others manufacturers ) with bootloader locked !!!! and if they never want to unlock with these new security politic........and this damned MM for original firmware more and more securised ==> we all profoundly have it on ours ass !!!
otherwise there are big chance to hard brick devices with bests devs attempts ...
Sorry for my bad words ,but this xda article that you previously have given to me ,make me really afraid !!!!!!! ...
Another big question :
when we have done MM update on G4 ,i have read that it's possible to easily downgrade to LP with LG-UP ....but full upgrade ??? it change this new MM bootloader with LP one ? for to have the possibility to root with locked bootloader ...

"While horror for us XDA people, it's better for the general public." This is how I think Google and OEMs justify their decision (which I find questionable tbh). But enough of that. Let's keep it on topic. I'd love to see reports from you whether it worked or not. Please include your ROM version, device and the country it was bough in. E.G. H815-EUR v20A Germany.
Btw. This just happened
{
"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"
}

Just used this on LG G4 H81520A, ( bootloader officially LG Unlocked ) went sweet as a nut.

I think if you flashed the repacked 20B boot.img it's possible you wouldn't have had ExFat issues. German 20A is Polish 20B. When you mismatch boot.img's you have ExFAT issues.
Systemless root is certainly nice though. I wasn't aware there was an automated tool now. Will make getting root after a new release even easier now

I'm not worried about the G5 to be honest. The LG v10 makes it as easy as on Nexus to unlock the bootloader: Look here. Sorry for offtopic, but it really fitted for me .

MickyFoley said:
I'm not worried about the G5 to be honest. The LG v10 makes it as easy as on Nexus to unlock the bootloader: Look here. Sorry for offtopic, but it really fitted for me .
Click to expand...
Click to collapse
If it is only for the T-Mobile variant they are probably at the same (if not worse) point that the G4 is. At least we can officially unlock some devices...

nitrous² said:
"While horror for us XDA people, it's better for the general public." This is how I think Google and OEMs justify their decision (which I find questionable tbh). But enough of that. Let's keep it on topic. I'd love to see reports from you whether it worked or not. Please include your ROM version, device and the country it was bough in. E.G. H815-EUR v20A Germany.
Click to expand...
Click to collapse
ok ,sorry for out of topic ...
i keep you thread preciously whe i will decide to unlock my bootloader thank again and again !
MickyFoley said:
I'm not worried about the G5 to be honest. The LG v10 makes it as easy as on Nexus to unlock the bootloader: Look here. Sorry for offtopic, but it really fitted for me .
Click to expand...
Click to collapse
i like your optimism ! i want to believe ...

I never had exfat problem with cile381 repacked kernel as autoprime stated it only happens if boot. Img mismatches. Other than that maybe this method could solve exfat problem on cm13?

@i-m: exFAT-issues of CM13 should be solved at 7th of December :
Code:
g4: vold: enable native exfat support (android_device_lge_g4-common)
g4: build exfat driver (android_kernel_lge_msm8992)

autoprime said:
I think if you flashed the repacked 20B boot.img it's possible you wouldn't have had ExFat issues. German 20A is Polish 20B. When you mismatch boot.img's you have ExFAT issues.
Systemless root is certainly nice though. I wasn't aware there was an automated tool now. Will make getting root after a new release even easier now
Click to expand...
Click to collapse
I did that too. I mean, flashing repacked 20B on German 20A. I then no longer had issues with exFAT formatted cards, but ADB was still "corrupted", meaning it wouldn't let me authorize my PC and the option to de-authorize was no longer available in the developer settings menu. Of course, might as well be an isolated case.
i-m said:
I never had exfat problem with cile381 repacked kernel as autoprime stated it only happens if boot. Img mismatches. Other than that maybe this method could solve exfat problem on cm13?
Click to expand...
Click to collapse
Sure you hadn't. But if you read OP closely, you'll see why some people, me included, had issues. No, it will not solve exFAT issues for CM13.
MickyFoley said:
@i-m: exFAT-issues of CM13 should be solved at 7th of December :
Code:
g4: vold: enable native exfat support (android_device_lge_g4-common)
g4: build exfat driver (android_kernel_lge_msm8992)
Click to expand...
Click to collapse
It was still broken when I tried the nighlty from December 7th.

Followed OP, root is working.
Still can't use my SD Card as on rooted 5.1:
- in FX Explorer I need to set a bookmark to a mounted location somewhere deep in the root filesystem,
- Lightroom says SD Card not available.
But this is a Marshmallow specific problem, isn't it?

Jens1969 said:
Followed OP, root is working.
Still can't use my SD Card as on rooted 5.1:
- in FX Explorer I need to set a bookmark to a mounted location somewhere deep in the root filesystem,
- Lightroom says SD Card not available.
But this is a Marshmallow specific problem, isn't it?
Click to expand...
Click to collapse
Apps have to be updated for proper support for SD cards. I switched to Solid Explorer because FX hasn't been updated for months.

Jens1969 said:
Followed OP, root is working.
Still can't use my SD Card as on rooted 5.1:
- in FX Explorer I need to set a bookmark to a mounted location somewhere deep in the root filesystem,
- Lightroom says SD Card not available.
But this is a Marshmallow specific problem, isn't it?
Click to expand...
Click to collapse
This is not a fix for devices that ran into SdCard issues. This is supposed to help you prevent exFAT issues from happening. The pre-requisite is an alread working device without exFAT issues.
This is specifically for Marshmallow devices. I'm surprised your device booted up after this Systemless ROOT patches your Marshmallow FW's kernel.

SM-G9550 Tomato Rom +Factory Bootloader/Tomato Bootloader+Root [Odin]

Hello,
here i upload my Tomato Rom 5.0 inkl Factory Bootloader . That one has no root because i dont know how to root that one. SD load is disabled in recovery but adb stock on boot enabled. If anyone knows how to do this please write me
Tomato Rom inkl Factory BL and Recovery
https://mega.nz/#!JjpzTbDJ!NoFKsh2V-TvAVY2KXpq6306z4SK0SkmlF4Y3QIhO-M0
Tomato Rom 5.0 , That version is untouched the Version from GFan , downloaded from very slow baidu Server in over 4 Hours ---- You can get it here from Mega
https://mega.nz/#!o2JlnD7a!Ftd9O38_xNoNaRjDDmyut24BT61ysw-l-b8iiB452Bo
Factory abl.elf and xbl.elf here from SM-G9550 You can flash this Tar in AP from Odin
https://mega.nz/#!NmZiHJAT!S4Hyiv6qnUWPmlPPJLCmM9jWH5I5aYjNmErA_6uD2ys
you can replace that two with any stock xbl abl from 9550 china/tgy
The next days i will upload all roms for 9550 that exist

Any info about this ROM? Features, ChangeLog, Bugs?

http://bbs.gfan.com/forum.php?mod=v...age=1&filter=typeid&typeid=12871&typeid=12871
from that tomato rom i took the system and replaced it from factory rom
{
"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"
}

@partcyborg @elliwigy what is going on here?
Sent from my SM-G955U using Tapatalk

progro420 said:
@[email protected] what is going on here?
Click to expand...
Click to collapse
I have no idea he was calling it samfail before I asked him to stop. Idk about you guys but that screenshot looks fuzzy and ancient to me. Like the first sampwnd did with eng system and aqcf combo boot.
The eng kernel does NOT boot on our devices. It gives an error of something like "please install user Firmware" if you flash it. I know this first hand. I also know it's NOT public firmware and hasn't been given out anywhere online.
My guess is it's an old combo boot/kernel as those are labeled as "ENG BOOT AND ROOT" all over the internet before the combo factory firmwares were common. If you search XDA you will find threads where elliwigy is *****ing about the exact same issue of people telling him they have eng boot when it's always combo.
In short, I don't believe a word of it . Confident enough in that statement that I'll happily eat crow if he has some magic eng boot that works
Hey maybe it charges to 100% and has unlocked bootloader too! I ???

That Version is for 9550 Versions.
That AP comes from that image:Tomato-G9550-QJ8-v5.0-freeODIN(线刷版)
in the complete Tomato are these Files:
CSC_WIPE_Tomato-G9550-QJ8-v5.0-odin.tar.md5
CSC_Tomato-G9550-QJ8-v5.0-odin.tar.md5
CP_G9550ZCU1AQJ8_CP7863601_CL12302925_QB15438164_REV00_user_low_ship_MULTI_CERT.tar.md5
BL_G9550ZCU1AQJ8_CL12302925_QB15438164_REV00_user_low_ship_MULTI_CERT.tar.md5
AP_Tomato-G9550-QJ8-v5.0-free-odin.tar.md5
Its easy to create Roms for that phone. you can inject Custom System.img in stock AP. You only need to replace them with own System.img.ext4 and only need is to retar it with 7zip. then reflash that with Odin. That method works with 9550 and i bet with 955/950 versions too. I already creating my rom list for 9550 to publish here. These Roms are all from China and the Soul Rom 835 comes with Playstore and prerooted .

012345678 said:
That Version is for 9550 Versions.
That AP comes from that image:Tomato-G9550-QJ8-v5.0-freeODIN(线刷版)
in the complete Tomato are these Files:
CSC_WIPE_Tomato-G9550-QJ8-v5.0-odin.tar.md5
CSC_Tomato-G9550-QJ8-v5.0-odin.tar.md5
CP_G9550ZCU1AQJ8_CP7863601_CL12302925_QB15438164_REV00_user_low_ship_MULTI_CERT.tar.md5
BL_G9550ZCU1AQJ8_CL12302925_QB15438164_REV00_user_low_ship_MULTI_CERT.tar.md5
AP_Tomato-G9550-QJ8-v5.0-free-odin.tar.md5
Its easy to create Roms for that phone. you can inject Custom System.img in stock AP. You only need to replace them with own System.img.ext4 and only need is to retar it with 7zip. then reflash that with Odin. That method works with 9550 and i bet with 955/950 versions too. I already creating my rom list for 9550 to publish here. These Roms are all from China and the Soul Rom 835 comes with Playstore and prerooted .
Click to expand...
Click to collapse
So only works on Chinese variants with unlocked bootloader
Sent from my SM-G955U using Tapatalk

progro420 said:
@[email protected] what is going on here?
Click to expand...
Click to collapse
its clearly listed for G9550 not a USA variant..
partcyborg said:
I have no idea he was calling it samfail before I asked him to stop. Idk about you guys but that screenshot looks fuzzy and ancient to me. Like the first sampwnd did with eng system and aqcf combo boot.
The eng kernel does NOT boot on our devices. It gives an error of something like "please install user Firmware" if you flash it. I know this first hand. I also know it's NOT public firmware and hasn't been given out anywhere online.
My guess is it's an old combo boot/kernel as those are labeled as "ENG BOOT AND ROOT" all over the internet before the combo factory firmwares were common. If you search XDA you will find threads where elliwigy is *****ing about the exact same issue of people telling him they have eng boot when it's always combo.
In short, I don't believe a word of it . Confident enough in that statement that I'll happily eat crow if he has some magic eng boot that works
Hey maybe it charges to 100% and has unlocked bootloader too! I ???
Click to expand...
Click to collapse
you wouldnt get the "fuzzy screen" as with original SamPWND in a screenshot lmao.. most likely his upload or something.. screenshots should always look normal..
either way, not for usa variants as op stated
---------- Post added at 11:07 AM ---------- Previous post was at 11:06 AM ----------
progro420 said:
So only works on Chinese variants with unlocked bootloader
Click to expand...
Click to collapse
yes.. you can see the model in the thread title.....

It works with the us att variant too but I don't trust it knox is 2.8 and says shared device it has systemlink files and they dump your SIM and track u with a virtual SIM

elliwigy said:
its clearly listed for G9550 not a USA variant..
you wouldnt get the "fuzzy screen" as with original SamPWND in a screenshot lmao.. most likely his upload or something.. screenshots should always look normal..
either way, not for usa variants as op stated
---------- Post added at 11:07 AM ---------- Previous post was at 11:06 AM ----------
yes.. you can see the model in the thread title.....
Click to expand...
Click to collapse
Seems it works on at&t also Lol
Look at the post above mine
Sent from my SM-G955U using Tapatalk

This is part of the build prop

Im guessing they attack thu the pre installed google drive intall a update to google sevices , to sideload ****

Hello
So, I have the G-9550 Hong Kong variant.. I bricked it and need to Odin flash firmware back to the phone.. Is this rom safe or no.? If not is there a better alternative. I haven't found anything. I'm in the U.S. on T-mobile. Thanks for your help..!

jdizzle98 said:
So, I have the G-9550 Hong Kong variant.. I bricked it and need to Odin flash firmware back to the phone.. Is this rom safe or no.? If not is there a better alternative. I haven't found anything. I'm in the U.S. on T-mobile. Thanks for your help..!
Click to expand...
Click to collapse
you can reflash, to be sure not get trapped in FRP you need to flash CHINA ABL.elf and XBL.elf
its already the version 6 out.

Mark805 said:
It works with the us att variant too but I don't trust it knox is 2.8 and says shared device it has systemlink files and they dump your SIM and track u with a virtual SIM
Click to expand...
Click to collapse
Virtual Sim is for Samsung Data Store. A Service for Asians. You can connect all over the World with charged virtual Sim

012345678 said:
Virtual Sim is for Samsung Data Store. A Service for Asians. You can connect all over the World with charged virtual Sim
Click to expand...
Click to collapse
FullScreen Photo For V5
https://drive.google.com/file/d/1raRQ0WTuyez3uMrhcurKVyoOsmhqNsFH/view?usp=sharing

kin201303 said:
FullScreen Photo For V5
https://drive.google.com/file/d/1raRQ0WTuyez3uMrhcurKVyoOsmhqNsFH/view?usp=sharing
Click to expand...
Click to collapse
thanks.

SM-G9550 oreo update
Have you recieved the oreo update yet for your SM-G9550. If so could you do a system img and boot img pull so I can port it.
012345678 said:
Hello,
here i upload my Tomato Rom 5.0 inkl Factory Bootloader . That one has no root because i dont know how to root that one. SD load is disabled in recovery but adb stock on boot enabled. If anyone knows how to do this please write me
Tomato Rom inkl Factory BL and Recovery
https://mega.nz/#!JjpzTbDJ!NoFKsh2V-TvAVY2KXpq6306z4SK0SkmlF4Y3QIhO-M0
Tomato Rom 5.0 , That version is untouched the Version from GFan , downloaded from very slow baidu Server in over 4 Hours ---- You can get it here from Mega
https://mega.nz/#!o2JlnD7a!Ftd9O38_xNoNaRjDDmyut24BT61ysw-l-b8iiB452Bo
Factory abl.elf and xbl.elf here from SM-G9550 You can flash this Tar in AP from Odin
https://mega.nz/#!NmZiHJAT!S4Hyiv6qnUWPmlPPJLCmM9jWH5I5aYjNmErA_6uD2ys
you can replace that two with any stock xbl abl from 9550 china/tgy
The next days i will upload all roms for 9550 that exist
Click to expand...
Click to collapse

012345678 said:
you can reflash, to be sure not get trapped in FRP you need to flash CHINA ABL.elf and XBL.elf
its already the version 6 out.
Click to expand...
Click to collapse
please where to get that and how to flash? i cant flash anything to s8+ with HK firmware. it is giving me binary blocked by frp. No oem unlock, bl unlocked with crom already, google account removed, but still cant flash twrp or patched boot or whatever custom.