yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] Falenone:
Did OTA work or you did a clean/dirty flash?

Edit: Ended up downloading the whole package and dirty flashing it.

Does it have ART instead of Dalvik now?
[G4 Q&A, Help & Troubleshooting] Evoluti0n:
Hi all, need help here, phone is stuck at aat mode after taking out from box, i understand that u shld hold the power button n click on normal boot, but the problem is the phone dont have a normal boot at all.. help me pls..
[Sony Xperia E3] ShanePunk123:
Well I suppose sony isn't supporting this device.... In the latest news, sony has announced lollipop 5.1 for many devices including M2 by july.... But has not mentioned anything about E3, leaving it out of the picture totally.... :eek:
[Sony Xperia E3] lexiyuri:
Hi [MENTION=6076834]ShanePunk123[/MENTION]

About updates the issue Is not just for Xperia E3. Indeed, Xperia T3 and 2015 Xperias like E4 and E4g are not listed for upgrade at this date.

In real terms, Xperia E1 is the less updateable of the remaining 2014 Xperias due to low ram (just 512 Mb). But we dont know. Sony can drop it all 2014/2015 E series and just update T3, or update all the 2014 remainings and 2015 newcomings.

At this moment we can assure or have the good feeling (in terms of hardware) for get lollipop in Xperias E3, E4, E4g and T3 , because they have the required to run lollipop. May be they jump to 5.1 directly overriding or avoiding 5.0.2. Idk that

Currently is an active AOSP 5.1 developer program for the Xperias E3 and T3, so, this is a tiny bit of light in our dark. For AOSP in this models, Camera is not working but other functions are working at least normally as possible, but AOSP is not intended to be a daily usable ROM. And CM guys are working in CM12.1 but theres no stable CM12.1 for us. Instead. 2013 devices and older have an active CM12 development with good stability. Damn DRM and Sony drivers ¬¬

So....Be happy because some 5.0.2 Xperia users are annoyed with the bitter lollipop because of extreme heating, no wifi, no select sound configurations, low battery life and other uncomfortable issues that didnt happen when they were sweet chocolateys. These users are going to jump to 5.1 in July and the jumping is easy for them because they have at least lollipop.

Now, keep in mind that Android M is coming and I have my doubts about reaching M. Maybe lollipop (or kitkat) is going to be the latest and final android version for our E3, other mid rangers and oldest high end Xperias.
[Sony Xperia E3] entony80:
I hope that sony will update a device about 10 months and does not adopt policies like HTC who abandons its customers. I hope that Sony will not do so, otherwise, I do not buy a Sony product. We look at other manufacturers like Motorola that are upgrading the Moto X (2013), not only Samsung also updates its products dated, so I hope that the projects we are active on FXP to our devices have a future update.
[Sony Xperia E3] Densho64:
Maybe it has to do with the internal storage. Remember the Xperiia M4 Aqua 8 GB version? That thing only has about 1.33 free space(1.75 with removed bloatware). Imagine the E3 with just its less than 4 GB... Android 5 uses way too much space. The only one I think still has a chance is T3. I'm pretty sure E4 is already set on the update map.
[Sony Xperia E3] entony80:
I installed AOSP and no problem with internal memory, I got a htc desire hd with a memory of 1.5 GB and is now updated to cm12.1 unofficial without having any problem of memory. Look here like mom sony treats its customers, should be ashamed, I am unhappy with my purchase ... at ever again :crying: :crying: :crying:
[Sony Xperia E3] lexiyuri:
Lets make noise on the twitter account [MENTION=5448027]SonyMobile[/MENTION]news, [MENTION=1346574]SonyXperia[/MENTION] and related

See my example and make noise with me

FOR OUR E3 WITH LOLLIPOP: TODO EL MUNDO A LA CARGA!! Everybody make some noise

-This is a scream to call the masses and make our voices louder and be heard!!
[Sony Xperia E3] vinay:
Yes you are right.

Only way to get lollipop is by rising our voice.

Let,s do this.
[Sony Xperia E3] t-shock:
For this s*itty move, I gave my E3 to my dad and I bought lumia 535. F*CK YOU SONY. WE DESERVE UPDATES!!!
[Sony Xperia E3] MrGKanev:
I think that we shoud try it but lets make a real massege and do it corectly. :)
[Sony Xperia E3] hell_lock:
Hey guys. I am trying to compile some aosp roms here for d2203 and d2202. So if you're interested in testing them just let me know..

PS- you should have a fast internet to download the roms.. my internet sux so I cant download them from my server :/
[Sony Xperia E3] ChetanLokhande:
I would like to try them, give the downloading site or thread site.

You said d2202 so can i try it in my d2212?
[Sony Xperia E3] vinay:
did you mean d2212 and d2202 because d2203 and d2202 does not make sense.?
[Sony Xperia E3] entony80:
I am interested in testing

PS - I'm testing the latest AOSP that load on FXP but obviously have no camera and data connection, solving these small things can be a rom for everyday use because it's stable and fast
[Sony Xperia E3] hell_lock:
I can give it a shot fixing those bugs..

Btw.. can anyone upload e3 5.1 binaries on github??

http://developer.sonymobile.com/kno...e/open-devices/list-of-devices-and-resources/
[Sony Xperia E3] hell_lock:
I'll first make it for d2203. Then port it to our device..

So initially I'll test boot it on d2203 and if it works then port.
[Sony Xperia E3] thenemis:
u may clone from https://github.com/SuperBenevolent/ and maybe overwrite with newer version from site, if needed. (and then pull and request with upgraded files)
[Sony Xperia E3] entony80:
I can help, but test a rom why are not capable of using Github. If I spiegni or give me a guide I can try
[Sony Xperia E3] vinay:
[MENTION=4449607]hell_lock[/MENTION] should i upload now. cuz [MENTION=4584101]thenemis[/MENTION] gave you link.
[Sony Xperia E3] vinay:
[MENTION=4449607]hell_lock[/MENTION] about to my previous experince with cm11 of lte varriants i know that for porting it to our devices need to work on kernel/ramdisk and maby we need to work on rom for RIL only. after that only bug,s by fxp will be needed to be fixed.

but however this is lollipop and i have tested on kitkat.
[Sony Xperia E3] kvsriram91:
Great!

What about D2212? :crying:
[8525, TyTN, MDA Vario II, JasJam General] martialalmac:
I'm new to this site, and have searched as much as I can but I can't for the life of me find what I'm after.

I have 6 Vodafone V1605's - 1 of them has the latest ROM update which has the Messaging and Security Feature Pack the others don't. Having looked in the downloads section there is only the 2.3.0 version. I've called Vodafone who have told me that it "SHOULD" be available for download this July (so not too long to wait) but can anyone point me in the direction of where to get it? or wil I just have to be patient...

Is it possible to extract the ROM update off my 3.3.0 device and reflash it onto the others?

Thanks in advance...
[8525, TyTN, MDA Vario II, JasJam General] Fredde87:
It used to be one Vodafones website but they removed it a couple of days ago. I still have a copy though and I can upload it to a webserver if someone sends me ftp details.
[8525, TyTN, MDA Vario II, JasJam General] DoubleVision:
I am not 100% if this is the ROM you are speaking about but I bumped into this file on a blog:

See blog page: http://blogs.conchango.com/kenibarwick/archive/2007/06/21/Vodafone-release-the-V1605-_2800_HTC_2D00_Hermes_2F00_TyTn_2900_-update-_2E002E002E00_.aspx
[8525, TyTN, MDA Vario II, JasJam General] dapprman:
Vodafone have a downlaod site for updates/firmware upgrades ? This just for Sweden ? Else anyone have the URL ? as vodafone.co.uk is pretty useless for device support.
[8525, TyTN, MDA Vario II, JasJam General] Nagata:
http://wiki.xda-developers.com/index.php?pagename=BA_FTP_Site
[8525, TyTN, MDA Vario II, JasJam General] martialalmac:
Thanks DoubleVision - that seems to be the file I need!! Thanks to all of you for your replies. I'll upload it later today so that others can get it...

Cheers.
[8525, TyTN, MDA Vario II, JasJam General] Fredde87:
I can confirm that the url on that blog is the officail vodafone rom I have as well.

The officail vodafone websites for ROMs is hidden at http://s131209249.online.de/vodafone_software/index.htm

They dont link to it from their website, they only send it to you if you need a rom. They dont post all roms on that site either, I will post the FTP link when I get home (wednesday) so you can browse with an ftp client and see all their roms (original, updates etc).
[8525, TyTN, MDA Vario II, JasJam General] aicon:
Hello Freddie,

Can you still post the FTP link for Voda? I need either the launch ROM or update for the 1605 and I can't download it from rapidshare. For some reason rapidshare keeps telling me I'm already downloading something else from their site (I'm not) and I've been trying for days now.

I'd really appreciate it if you let me have voda's ftp address. Thanks.
[G4 Q&A, Help & Troubleshooting] PunishedSnake:
Anyone get a good slimport adapter?

Going to be at a hotel this week would love since mhl love
[G4 Q&A, Help & Troubleshooting] PunishedSnake:
Bump
[G4 Q&A, Help & Troubleshooting] NJ72:
Hey,

I had a play with my SlimPort adaptor today, works a treat with the G4. Nice refresh rate too. I have the Kanex one. You can get it from amazon, ebay and from Kanex themselves at KanexLive.com.

Nice slim form factor too. Works without external power but also has a micro USB port for charging as well. My only unknown is whether it will support USB OTG as well using that port - I don't think Slimport supports that so probably a no, but I'll have a play later and let you know.

Cheers,

NJ

UPDATE: USB OTG doesn't work, if you wanna use it as a workstation you'll need a Bluetooth keyboard and mouse :)
[G4 Q&A, Help & Troubleshooting] diamond12:
I have bought 2 on eBay, didn't have problems with either but the sellers no longer have them. Items 181322353837 and 311183296532.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Q&A, Help & Trouble] jessepcook:
I was trying to install a custom firmware and it failed for some reason. Now I'm stuck in on the logo.

I have tried about 7 or 8 different stock firmwares on Odin, 3 of them failed because they were the wrong region, and 5 were successful but still stuck in on the logo.

ROMS Tried:

BTU-T520XXUAOD2-20150603140459

T520UEUANI1_T520XARANI1_XAR

T520UEUAOD1_T520XARAOD1_XAR

T520UEUAND1_T520XARAND1_XAR

T520UEUANF4_T520XARANF4_XAR

T520UEUANK1_T520XARANK1_XAR

I read from another thread that all I have to do is clear the cache/dalvik cache. I tried to do this through adb but adb devices does not show any devices, it just comes up blank. Android Studio won't download platform tools or the Google USB drivers either so maybe that's why its not detected?

This tablet was purchased in the US.

If someone can provide me with a STOCK rom that will work or help me figure out adb to clear the cache that would be awesome.

Thank you!
[Galaxy Tab Pro 12.2, 10.1, 8.4 Q&A, Help & Trouble] cloud71:
You should only flash the region your device is made for. Hopefully you have custom rom like twrp, go into that and wipe delvic and cache , that may fix boot prob
[Galaxy Tab Pro 12.2, 10.1, 8.4 Q&A, Help & Trouble] jessepcook:
I only flashed the UK ROM because I couldn't find the US ROM. It turns out that the US ROM is labelled "Cellular South" which is far from obvious. And in terms of TWRP I think that went away when I tried to flash stock. I can try to flash TWRP back with Odin tomorrow and see if it will take though.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Q&A, Help & Trouble] onebelo:
Have you tried using Kies to do emergency restore? I had soft-bricked my 10.1 when I got it trying to root. Wasn't paying attention and accidentally tried flashing the CF-auto-root file that was for my phone (Note 4) to the tablet. Found the stock rom but all the ones I found was taking like 8-10hrs to download.

So i used Kies and under Tools, selected Firmware Upgrade and Initialization. PUt in my serial number and model number and had tablet in "Downloading mode" and was able to recover the tablet that way. When i tried doing the Emergency restore, it wouldn't recognize device as being connected so I had to try the other options for it work.
[Xperia Z3 Q&A, Help & Troubleshooting] mrnannu:
My phone taking too much time to complete full charge. It takes 2.20 hour

What is the problem?

Also tried charging into switch off mode but same result may b it takes 2 hour, its too much. I have also use a z3 compact but those time quick charge working perfectly. Why this happening with my Sony Xperia Z3 (6653).

Is there any solution?

Thanks in advance [emoji4]
[Xperia Z3 Q&A, Help & Troubleshooting] heywheelie:
The Z3 has a much bigger battery than the Z3C. on the Z3 the battery only quick charges for the first 60% and then charges normally to protect the battery. No idea why it takes longer with quick charge on than off.
[Xperia Z3 Q&A, Help & Troubleshooting] mrnannu:
Ok. That means it's normal?

What about your phone?
[Xperia Z3 Q&A, Help & Troubleshooting] Entropy512:
Specifically, it's approximately a 3000 mAh battery, and the charge current is limited to 1500 mA (or 0.5C)

So a bit over 2 hours is exactly what you'd expect - it's by design due to the completely nonreplaceable battery (since the phone is waterproof, it's even harder to replace than in other phones with a "nonreplaceable" battery, so Sony is conservative about not abusing the battery).

z3c is a bit strange, since Sony actually charges at 0.7C up to around 60% even though it's a smaller battery/device (less able to dissipate heat)
[Xperia Z3 Q&A, Help & Troubleshooting] LeParkour012:
Strange. My Z3 charges from 20% to 100% under an hour.
[Verizon Samsung Galaxy S 4] looneyk:
I rooted my s4 and installed twrp a long time ago used the phone for a little while then stashed it away. It had the following rom installed I545VRVFNC5 stock root oder I believe it was 4.4.2. The other night I installed flash fire and attempted to flash I545_OC1_Stock_rooted_rom mdk. It flashed ok but now I'm getting the verizon warning message and I can't bypass. I can no longer boot into twrp. I think the bootloader is still unlocked, padlock is unlocked upon boot. How do I get myself out of this message?
[Verizon Samsung Galaxy S 4] XxD34THxX:
Try to Odin back to MDK, if you had TWRP... If that doesn't work, nc5. You can't do custom ROM's like Cynanogenmod, but you have a limited amount of freedom with safestrap.
[Verizon Samsung Galaxy S 4] SnyderGuy:
The open padlock means the firmware you have installed is custom and not stock, doesn't mean your boot loader is unlocked. I would simply boot into download mode and re-image your device back to MDK, if that's where you were. What's your current boot loader version?

Sent from my SCH-I545
[Verizon Samsung Galaxy S 4] pizza_pablo:
I am using an MDK S4.

I can bit to room, but cannot reboot to recovery.

Corrupted recovery after update via TWRP app.

How exactly, do I re-image my device back to MDK?

Do I use this stock MDK ROM? http://xdaforums.com/galaxy-s4-verizon/development/rom-i545oc1-5-0-1-100-stock-mdk-t3097902

Do I put it in the BL or AP box in ODIN?
[Verizon Samsung Galaxy S 4] XxD34THxX:
No, that is a ROM. You need the stock official software.

http://xdaforums.com/showthread.php?t=2289325

SHOULD be that one...

Put that in AP
[Verizon Samsung Galaxy S 4] pizza_pablo:
I just read it all. Looks like fun!

I sure would like to know what I did wrong. I only used the TWRP app to update TWRP.
[Verizon Samsung Galaxy S 4] XxD34THxX:
That I cannot answer since I do not have MDK. My assumption is a corrupted download of TWRP or a partial install that was interrupted for some reason.
[Verizon Samsung Galaxy S 4] pizza_pablo:
That may have been the case, since my connection was weak.

I'm just about to do the deed and I checked phone info and the bootloader is now I545VRUFNK4, vice MDK.

Here I go....
[Verizon Samsung Galaxy S 4] pizza_pablo:
Well....I tried these to .tar files with no luck:

http://www.rwilco12.com/downloads.p...Galaxy S4 (Verizon) (SCH-I545)/Stock ROMs/TAR

https://www.androidfilehost.com/?fid=22979706399752783

I did get the "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."

Now, I no longer have the option to cancel Download Mode and bot ROM.

I didn't want to do anything in Kies, for fear of taking an OTA.

Do I have any options?

Even just taking an OTA and selling a former MDK treasure?
[Verizon Samsung Galaxy S 4] XxD34THxX:
This seems to be happening a lot. A LOT. Before you try kies, go into device manager and uninstall the Samsung USB drivers. Then download the DRIVERS ONLY from Sammobile/Samsung. THEN use Odin with a full wipe and repartition of MDK. If you get the same message again, then you have lost the MDK bootloader, and will have to repeat the process with an nc5 tar, which will loose custom ROMs, but you will have root and safestrap.
[Verizon Samsung Galaxy S 4] pizza_pablo:
OK. So I am going to uninstall Kies, just for safety sake. Uninstall the Samsung PC drivers. Reinstall the PC drivers.

Use ODIN to flash this http://www.rwilco12.com/downloads.php?dir=Files/Devices/Samsung%20Galaxy%20S4%20%28Verizon%29%20%28SCH-I545%29/Stock%20ROMs/TAR in the AP box. Sacrifice a chicken and dance with snakes.

What do you think may have caused the bootloader to change?

At this point I guess any use of the phone will be a positive and somehow retaining MDK will be a miracle.

Thanks, for your assistance, as I am at a loss, at this point!
[Verizon Samsung Galaxy S 4] XxD34THxX:
that is a .gz, so make sure to unip it/ delete that extension so Odin can use it.

My assumption is you may have accidently flashed the entire nk4, not just one with the MDK stuff still in.
[Verizon Samsung Galaxy S 4] pizza_pablo:
I used the link file, from my last post.

After I unzip it, delete the " .gz "

Got it. Thanks, again!
[Verizon Samsung Galaxy S 4] pizza_pablo:
So I just looked at the computer file and there was no .gz extention on the file I flashed thru ODIN.

It was not zipped, either.

On the xda page that you link, there was another choice on thier link. It was titled "one click". It is an .exe, titled "SCH-I545_MDK_562219_Stock_Restore.exe" .

What could ODIN do with this?

The other file I found, that I tried, but no change, was titled "VRUAMDK_NoWipe.tar.md5" .

Do you have any other suggestions,please?
[Verizon Samsung Galaxy S 4] XxD34THxX:
Use the Full wipe in this thread:

http://xdaforums.com/showthread.php?t=2301259

If that does not fix anything you have either

A)Hard Brick(unlikely since the device is semi-working)

B) lost MDK.
[Verizon Samsung Galaxy S 4] pizza_pablo:
I used this one, the other night, with no change, but this time I will delete Kies and phone drivers, then reinstall phone drivers, before ODIN.

You're a champ!
[Verizon Samsung Galaxy S 4] pizza_pablo:
Do I remove the .md5 extension as well as the .gz and just leave the .tar on the end?

ETA: Well, I tried removing both extensions and ODIN would not take it. Received error pop up.

I tried, with no success, ODIN flashing the full wipe and no wipe tars, with no success.

Giving up for the night.
[Verizon Samsung Galaxy S 4] pizza_pablo:
I woke up in the middle of the night and something popped into my head and I couldn't get back to sleep, so here we go....

The phone was on Echoe v49 which is Lollipop and I didn't like it. So I decided to go to the last Echoe version that was KitKat, v34.

I flashed this https://www.androidfilehost.com/?fid=95747613655044521 Which apparently is T-Mobile based, and the v20 international patch.

What popped into my head was that maybe my phone was thinking it was a T-Mobile S4, because I picked the wrong kernel. At the time everything seemed to work, except sending SMS. I could make phone calls and receive SMS.

This is was got me out of bed. I went to my notes for the Aroma install, to see what kernel I chose. I recalled picking the stock kernel, which may have been T-Mobile, but my notes say that I picked KTOONES kerenel in Aroma and in the Patcher, picked ADD VZW FILES AND BUILD PROP and NO KERNEL.

I was thinking that I had put a VZW version of TWRP onto a "T-Mobile" S4, getting me stuck to bootup in Download mode only, but still able to cancel Download and boot to system. Then I ODINed the VZW MDK stock firmware and am now with either Download mode or the yellow PC connected to phone screen, with the "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."

I woke up thinking that maybe I had a T=mobile kernel and when I lost TWRP and only had stock recovery, downloaded the VZW version of TWRP on top of T=Mobile install. But the note makes it look like I would have been OK as far as the phone thinking it was a VZW S4.

Sorry if rambling, just trying to pass as many details and thoughts as possible.

Do I have any options, now?

I downloaded the stuff to do Heimdall One Click and was thinking about trying that route, with a file named "SCH-I545_MDK_562219_Stock_Restore.exe"

I have a 32GB MDK VZW SCH-i545 S4 that is running fine on ECHOE v29. Can I copy anything from that phone and flash in ODIN to recover the 16GB (was MDK) VZW SCH-i545 that is stuck on Download mode only?

Is there any way to flash a NANDROID via ODIN or some other program from a PC thru ODIN?
[Verizon Samsung Galaxy S 4] XxD34THxX:
hmmm.. The Ktoonez kernal works on any s4. But if you flashed T mobile Files, which I don't think was the case since you flashed the Verizon stuff... I have never used Heimdall, so I can't comment on that. I don't know what to say. There might be a way to make a debrick image... Someone more experienced will have to help, sorry.
[Verizon Samsung Galaxy S 4] pizza_pablo:
No need to apologize! You have helped all you can. I appreciate it greatly!

I just want to ensure that I exhaust ALL possibilities of recovering the MDK, before I throw in the Kies upgrade towel.

I wonder if I'll get in hot water for starting a new thread.....
[Verizon Samsung Galaxy S 4] XxD34THxX:
You probably will. That said, if the Full wipe and re partition didn't work, Then either you have to go to nc5 or it will stay like that. My assumption is that flashing a tmo version of a ROM screwed it up, as the partitions are completely different and tmo does things a lot better...
[Verizon Samsung Galaxy S 4] pizza_pablo:
I don't think the TMO label on the Echoe ROM did it in. It was fine until I tried to reinstall TWRP. It was a learning experience, tho I'm not exactly sure what I'll be taking away.....

Well, instead of opening a new thread, I threw in the towel and decided to use Kies to restore, knowing that it would prob be Lollipop.

It wouldn't connect to Kies, so I did post #2, here http://xdaforums.com/galaxy-s4-verizon/help/soft-bricked-quick-advice-t3125781

Its now on the setup wizard. I'm plan to ensure its fully functional and sell it, in hopes of finding another MDK.

Thank you, so very much for your support!

ETA: Its fully functional. Checked out calls and SMS send and receive, GPS, WIFI and email. Good to go.

Within a half hour of operating, received the popup for Lollipop update. Delayed it for 23 hours. Installing Towelroot and Safestrap now, in an effort to maintain KitKat, to give buyers options.