yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Mega] Silesh.Nair:
Lots of models. I think every model except at&t mega which has a locked bootloader. One that comes to mind is SGH-i527M.
[Samsung Galaxy Mega] snouki:
When do you upload new build? Nightly or weekly? Thann you so much
[Samsung Galaxy Mega] Silesh.Nair:
It should be weekly.
[Samsung Galaxy Mega] starmaster10:
The i527m like Silesh.Nair has mentioned as that is the version i have and will test this latest rom and see if it works on the i527m now as if it works on the i9205 it usually works on the i527m model. :good:

Update: Tried to flash the rom and it failed..so it looks like the i527m will have to be added to the assert line also. :)
[General Questions and Answers] SD_2007:
Is there any way to Install android 4.4.2 on my Micromax A92?
[General Questions and Answers] sathish_in:
Install 4.4.2 on Micromax a92

No such custom ROM (4.4..2) available for Micromax A92 some one can develop one. at present 4.2.2 is only avaliable
[Verizon HTC One (M7)] jessbowring:
Sent my phone back for pink camera issue. Returned to stock locked but left s-off. They repaired without issue. Main rear camera was replaced and upper board replaced. 100% improvement. They did update my software to 4.3 which I had expected. Glad I left soff.
[RAZR i Q&A, Help & Troubleshooting] klf_xxx:
where can i find stock ROM for razr i Motorola JB 4.1.2 EU firmware?
[RAZR i Q&A, Help & Troubleshooting] Chamelleon:
http://sbf.droid-developers.org/download.php?device=13&file=310
[HTC Desire S] ohj_17:
Hello guy here in phils, may i ask if where can i buy his one???

thanks
[HTC Desire S] jmcclue:
Ebay
[HTC Pico (Explorer)] arunudayan:
Hi,

I recently installed akya's nextgen ROM (Arom based ICS 2.3.5) and then used "m2sd data enable" to move app data to sd-ext. Now my phone has a peculiar problem that it restarts abruptly many times (-20-30 times) in a day.

Previously too I had tried m2sd script with bullet-sense and fly ROM and had the same abrupt restart problem.

So , today I reinstalled nextgen ROM, removed mount2sd script from init.d folder and pasted ungaze scripts as per the instructions in the ungaze forum and everything now looks ok. My internal memory now shows as 1.7 gb available (I had made a 2 gb ext-4 partition).

The only problem now I have is that some google applications went missing. When I tried to reinstall gmail and hangouts from Play store, I get error messages like Invalid package/ cannot install package etc. Though as a workaround I have configured gmail in the default mail client.

Did anybody else faced the same issue?
[HTC One S] kingdom369:
i installed viper and then it loaded the viper UI and stufff, then i flashed the viper kernel, after that, it doesnt load phone, but has orange indicator.

what happened, cuz i flashed everything correctly
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] Software Guru:
Hi guys and gals

I was unfortunately sent 2 of these devices by O2 (damn shame I am so unlucky!!!), I have waited a month and they have not asked me to send it back so it's up for grabs

I have not unlocked it or updated the ROM, infact it is sitting in a sealed environment on my desk

Email any offers to iali@ssp-uk.com, I will consider anything

I will charge £20 for UK postage and international will be calculated upon destination

Thanks

:D
[HTC One S] kingdom369:
cannot load my phone after flashing viper kernel, and it flashed successfully....

on the computer, it says device not connected, please help, i dont want to brick my phone again, after doing all the instructions correctly.
[HTC One S] Kin93:
I've the same problem on MaximusHD. On Windows HTC Sync recognizes the phone but i've no idea how to access to the internal storage; on Linux, it gives me MTP error.
[HTC One S] Kin93:
Bad News Everyone: why my One S is seen as CD ROM drive? Even if i uninstall and reinstall the drivers, Windows sees it as CD ROM and MTP Device. I don't now what to do.

Sorry for my bad english.
[HTC One S] Kin93:
Up.

Inviato dal mio tostapane utilizzando Tapatalk
[Sony Xperia ZR] jagratjoshi:
How many people Don't like android 4.3 please tell to Sony

1.Consuming too much power and affecting battery life.

2.Scrolling is very noisy so need too much repolish user interface.Project butter isn't works. Every application is not smooth e.g - in clock move from world clock to timer breaks, home screen, gallery, slide show is bad.

3.Some applications run in background always live in notification bar eg - Uc Web background download always shows in notification bar "Uc Web is running tap to more information "

4. Bugs with Blutooth, wifi, nfc

5. With this operating system applications run problematic not perfectly like chrome

6. Old camera UI was excellent - excellent..look and functionality.New UI looks very very bad and decreased quality.

7.Problem with video recording.

8. New Keyboard app is very very bad We want old keyboard.

9. Ram management is bad.
[Sony Xperia ZR] shysparrow:
Dude..!! Y don't u just downgrade it and forget it..

None of your above stated problems is being faced (atleast by me)

A cure for you ---- To fix it, Read it.. Just don't Post it, to Blame it.. Got it?

De-bloat/ Kill apps u don't use or never ever use. Battery life on 4.3 is insane runs all day for me with 20-25% drainage (average call, texts, emails on exchange) no issues at all. (Root it / Calibrate the battery for actual reading). Project butter does what it is suppose to. No lags at all. U need Lag Fix. Use Adblocker kill stupid apps delete system apps (only if u r aware of what u r deleting).

No bugs at all with Bluetooth/ wifi or NFC I use all of them in daily life and works like a charm. In other words now I can skype on wifi instead on 4g LTE (on my BB Q10) on 4.2.2 I faced too many problems. Chrome was recently updated and stable now.

For the rest release your stress and go for a different device.

I believe in -

"If u own it, u can control it" ;)

Good Luck!
[Sony Xperia ZR] jagratjoshi:
Hey dude I for your kind information I wanna tell you that according Sony new policy a phone can't be downgrade even on Sony care and I not want root it
[Sony Xperia ZR] avik735:
Use flash tool to downgrade it, u won't need to root it.
[Sony Xperia ZR] smooth_gl:
Before going back to 4.2 try to flash again 4.3 because you are the only one who experience problems.
[Moto G Q&A, Help & Troubleshooting] pestrit:
Hello everyone,

my Moto G came finally yesterday. I immediately proceeded with factory reset -> upgrade to Kitkat v4.4 and tried to encrypt the device prior to installing the apps and configuring the phone. However, during encryption, i lost power source for a while (20sec). Moto has never finished encryption task and now, i'm not able to boot anymore. After booting the phone, after i enter SIM pin and then decrypt PIN, moto g just displays green android cartoon for a second and then hangs with blank little-backlighted black display. I can go to fastboot menu, however, none of the options (Normal, Factory, Recovery) works, they always lead to the same blank black display....

It looks that it's seriously bricked, anyone knows if there is a chance to fix this? Device has not been unlocked neither modified in any way....

Thanks in advance for any help,

P.
[Moto G Q&A, Help & Troubleshooting] The "A" Factor:
If it's Booting then it's not fully Bricked ...

Most probably the power cut happened during system read/write operation and has corrupted the /System or /Boot Partition, And I guess it can't be fixed easily .

But the good news is that you can take it to Service center and tell them that this happened all of sudden during update (you can skip the power failure part ;) ) , and they will either repair it or most probably give you a new device !!!

So just chill and take your device to service center ASAP !
[Moto G Q&A, Help & Troubleshooting] pestrit:
thanks for your answer. i just wonder if there is any other way how to fix it manually. I'm completely disappointed with this Kitkat encryption process. If the ecnryption would have been caused by the short power outage of phone even the device was fully charged, it's really shameful...

Anyway, I bought it from Amazon in US and it's not being sold yet here in Slovakia so not sure if the international warranty will apply or if they will be able to fix this model here.. Definitely will try to ask at least.
[Moto G Q&A, Help & Troubleshooting] pestrit:
Issue fixed using Motorola great support - Only thing that needed to be done was to perform external reset by following https://motorola-global-en-uk.custh..._id/96459/p/30,6720,9050/kw/reset/action/auth

perfect, issue solved, gonna encrypt again :D
[Moto G Q&A, Help & Troubleshooting] aradalien:
reset

Interesting bookmarked that link may come in useful some time. :o
[G2 Q&A, Help & Troubleshooting] willbs94:
My LG G2 att variant would not boot after installing Grievous RSL 4.0. I believe I had the wrong twrp installed. I am stuck and cannot boot to android. I can boot to download mode but lg flash tools does no good because the model number does not match and says it is d802. Any help would be greatly appreciated. I cannot boot to recovery. I have only a black screen when not booting to download mode...
[G2 Q&A, Help & Troubleshooting] Funkym0nkey:
Check if you have adb access when you are on black screen.
[G2 Q&A, Help & Troubleshooting] willbs94:
No adb or fastboot access with the black screen. I have tried all night. Idk what else to do. I did the Linux option and now it says null next to imei and product number is blank when trying lg flash tool. For some reason I cannot get the lg launcher program to work either...
[G2 Q&A, Help & Troubleshooting] dily816:
Here some answer to fix your brick phone

I hope these site can help you with adb setup and fix the download mode so you can do recovery.

http://www.androidheat.com/adb-fastboot-install-drivers-setup/

http://xdaforums.com/showthread.php?t=2451696
[G2 Q&A, Help & Troubleshooting] Robban:
Fix

I know how to fix this, Ive got the same problem once before.

Download FlashTool.1.0.54, start UpTestEX and choose CS_EMERGANCY in PhoneMode in the top right cornor and take CDMA as type to the left.

And flash the right .kdz file for your model.

It will work. Cheers!
[G2 Q&A, Help & Troubleshooting] slackwaresupport:
where is the kdz file??? i am at this point.. mine is totally bricked. all i can find is tot files
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] squabeggz:
I'm having an issue where my WiFi connection drops. Tab still says connected but I get no throughput. All other wireless devices still work. I have to toggle the wifi on the tab on and off to reconnect. Router is an actiontec C1000A.

I've read other threads where people had similar issues and exchanged tablets for new ones only to have them do the same. Router is good, it works with all my other devices without issue. What good is a WiFi only tablet if the WiFi sucks eggs?
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] Geordie Affy:
Well my wifi has been brilliant, the only issue I had was that although my wifi router was working with every other device and even my Note 10.1 it didnt want to play youtube videos on it. So I changed connection to my other broadband and it worked a treat so even though your router works with other devices it doesn't mean the tablet is faulty just that the router and tablet don't like each other.

Best way to try this is go to a friends house and try their connection or go to a coffee shop where they have free wifi and hopefully you will see wifi doesn't suck eggs lol. Anyways hope your problem gets sorted.
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] kkretch:
Are you just complaining or are you asking for help?............ If your asking for help please tell us if you are using 2.5 or 5ghz, b, g, n, ac, channel #. Many things can cause wifi issues and sometime a monitoring app from the play store like "Wifi analyzer" can help narrow down whats really going on.
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] squabeggz:
Im asking for help by complaining. :p I'll get some more detailed info on my network and post it up later.
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] squabeggz:
My modem/router was set to auto detect... I used wifi analyzer to set it to a less crowded fixed channel. I also turned off 802.11n. It had b, g and n simultaneously... Now it's just b and g. So that's 2.4 GHz? I don't have super Internet, so no real need for "n". I'll report back after I see if this changes anything. The security is WPA2-Personal...don't know if that has any effect. Any other ideas are appreciated.
[Moto X Q&A] polg_polg:
Its 1053 or 1058 or...?

About this:

amazon Motorola-Moto-Unlocked-Phone-Warranty/dp/B00E92AV2W/ref=cm_cd_ql_qh_dp_t
[Verizon Samsung Galaxy S III] ThePagel:
I just need a second person to verify (Preferably trial run) if this is patched for sure or not.

I have had no luck figuring out how to work

loki_find-linux-x86_64

This is needed to get the offsets from the aboot.img to put into the

loki_patch.c

Then compile into a binary so it can flash the custom recovery into a .lok

I will not be asking djrbliss for help and I urge you to not bug him. Chances are this exploit has been patched and will not work for our bootloader. But if anyone gets bored and wants to try to figure it out who knows maybe our bootloader still has the exploit?

First order of business we need to figure out how to get the loki_find binary to read the offsets from the aboot.img or find a diffrent way to figure the offsets out.

Who ever figures that one out will need no help setting up the patch file and test it out.

Pull your aboot.img with adb (windows or Linux)

make sure you pull the aboot.img from the code below and not from /dev/block/mmcblk0p5

adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local/tmp/aboot.img
chmod 644 /data/local/tmp/aboot.img
exit
exit
adb pull /data/local/tmp/aboot.img

The next step is the one I am stuck on hopefully someone can figure it out.

source Links:

djrbliss GitHub

technical blog post

[LOKI] Bootloader hack official FAQ thread

Downloads:

loki-master.zip <--- from djrbliss GitHub

loki-master.7z <-- (mirrored my myself 1/22/14)

aboot.7z <-- Must extract (My aboot.img)

ADB Only (Windows)

ADB Only (Linux) <-- Plus instructions

bootimg_tools.7z -- Might help us (Not my work but I did create both of the read me files with original links)
[Verizon Samsung Galaxy S III] ThePagel:
<never know>
[Verizon Samsung Galaxy S III] Dadud:
Disregard
[Verizon Samsung Galaxy S III] ProtheusIRC:
Bump.
[Verizon Samsung Galaxy S III] ThePagel:
Disregard
[Verizon Samsung Galaxy S III] Dadud:
Yes. It is. I'll try flashing to stock tomorrow if it doesn't help
[Verizon Samsung Galaxy S III] ProtheusIRC:
This should be interesting.
[Verizon Samsung Galaxy S III] ThePagel:
I must of been to tired to read how to do this correctly last night. Will hopefully have a Loki zip for using non stock kernels when i get home. The aboot we were pulling was the wrong aboot. If so this will turn into a summary of what I did/ step by step on how you can do it if you want to get your superuser funk on.
[Verizon Samsung Galaxy S III] Dadud:
Great news.
[Verizon Samsung Galaxy S III] ProtheusIRC:
Keep us updated.
[Verizon Samsung Galaxy S III] cplking:
I feel dumb but what's all this mean? Lol
[Verizon Samsung Galaxy S III] Dadud:
It means if this all works, anyone who grabbed the 4.3 ota can use safe strap with non touchwiz based roms. At least, that's my understanding.
[Verizon Samsung Galaxy S III] cplking:
That'd be great cuz I'm going through aosp withdrawals lol
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Or for the more technical info, read:

http://xdaforums.com/showthread.php?t=2292157
[Verizon Samsung Galaxy S III] ThePagel:
You shouldn't feel dumb I took down the link that explained everything. In a nutshell this exploit will if it works edit cwm and twrp to work on the 4.3 bootloader and to flash edited roms to work with the new bootloader. Note that safestrap at least for the the being will not work with Loki. you will need to pick what you want more any ROMyou want but stuck to one ROM slot or a few ROM slots that only boot 4.3 tw ROMs. Just don't get your hopes up the only way this will work is if Samsung forgot to patch the exploit. The newer s4 bootloaders are patched. http://blog.azimuthsecurity.com/2013/05/exploiting-samsung-galaxy-s4-secure-boot.html?m=1

The ROMs themselves will also need to be loki patch (that's the easy part)
[Verizon Samsung Galaxy S III] Dadud:
If I were to be the lab rat for testing this, this won't set off a qfuse and brick my phone will it, or is that to be found out as we go along? I have all the odin files to flash back to unrooted stock.
[Verizon Samsung Galaxy S III] ThePagel:
No it doesn't touch the boot loader. It tricks the boot loader to think any kernel you load is the stock kernel.
[Verizon Samsung Galaxy S III] Dadud:
Sounds good. i'll be defiantly helping you test this out.
[Verizon Samsung Galaxy S III] ProtheusIRC:
OK so what do I need to make a Loki patch? You mentioned that you were pulling the wrong aboot?
[Verizon Samsung Galaxy S III] ThePagel:
Besides the only fuse that can be triped on this phone is the warranty bit. I think that was proven by people fully over weighting there boot loader and making a revival from the hard brick.
[Verizon Samsung Galaxy S III] ThePagel:
Read the link its laid out for you
[Verizon Samsung Galaxy S III] ThePagel:
Don't bother trying unless you understand everything he says to do. If you don't you'll just waist your time like I did last night. I know what I need to do now but if you think you do as well I hope you get it!
[Verizon Samsung Galaxy S III] ProtheusIRC:
Well I understand that I need to pull my aboot. I also understand that I need to use my Ubuntu to download the repo so I can use Loki_patch. I am now trying to figure out how to do that. Then I'll patch my aboot so someone can flash.
[Verizon Samsung Galaxy S III] ThePagel:
Okay pump your breaks your going so fast you cannot see what's around the corner. First do not flash that aboot. You most likely will hard brick. Second thing is we are not patching the aboot but getting information from it.
[Verizon Samsung Galaxy S III] ProtheusIRC:
I never said I'd flash it. I can't as this is my only working phone and I don't want to mess it up. As I understand it,

I need to patch my aboot (after I pull it) with the command Loki_patch. Correct?

---------- Post added at 01:59 PM ---------- Previous post was at 01:57 PM ----------

I'm not a total noob and I want to help. I have exp with Ubuntu and android so work with me here.
[Verizon Samsung Galaxy S III] ThePagel:
Looked that way
[Verizon Samsung Galaxy S III] ProtheusIRC:
Pagel. Reread it man. I'll patch my aboot so SOMEONE can flash. Lol
[Verizon Samsung Galaxy S III] ThePagel:
I never accused you of being a noob. But you really need to read that link again because we are gathering information to put into Loki to flash.
[Verizon Samsung Galaxy S III] ProtheusIRC:
Ok, ok. Let's slow down here. I have Ubuntu, a little know-how and the desire. You have everything else lol. What can I do to help?
[Verizon Samsung Galaxy S III] Dadud:
i just watched a video on how to install loki on the S4 (http://www.youtube.com/watch?v=B36ZTUF8), it looks like we'll have to create a patched recovery and install it.
[Verizon Samsung Galaxy S III] ThePagel:
Anything I tell people to do especially potentially dangerous things i test on myself first. He made it very clear in that link how to get the flash utility ready and what to flash. If you do not understand it dosent mean your dumb or a noob it just means it needs to be explained in a diffrenet way. I am at work and do not have the time to explain.
[Verizon Samsung Galaxy S III] ThePagel:
After you get the information from aboot. This patch is not compatible with our phone as it stands.
[Verizon Samsung Galaxy S III] ProtheusIRC:
Ok bro. I won't argue. Keep us updated.
[Verizon Samsung Galaxy S III] Dadud:
Keep me updated as well, i'll test out anything you need tested. if it bricks my device, i wont be happy but i need an excuse to get a moto x so no harm done.
[Verizon Samsung Galaxy S III] ProtheusIRC:
It is extremely hard to brick it enough as to be non-functional. As long as you have the 4.3 Odin flashable, you can always Odin back and you'll be good.
[Verizon Samsung Galaxy S III] Dadud:
im prepared and ready for the unpredictable though.
[Verizon Samsung Galaxy S III] ThePagel:
Fail just like everything I have been doing in computer land as of late. op updated :crying:
[Verizon Samsung Galaxy S III] techfreak243:
i will test

i will test out as well. i am tired of using the 4.3 touchwiz roms and wanna use AOSP and i am not sure how that will work with the safestrap recovery. so if this allows me to flash a normal custom recovery then i am in for damn sure
[Verizon Samsung Galaxy S III] cplking:
I'm definitely getting bored of tw roms lol
[Verizon Samsung Galaxy S III] galaxys3_xda:
I hope someone more intelligent then myself can make this patch work. I am in dire need of some kit Kat lovin.
[Verizon Samsung Galaxy S III] cplking:
I second that lol
[Verizon Samsung Galaxy S III] ThePagel:
I'll post my aboot.IMG tonight in case anyone is having adb problems. The aboot.img in the first couple posts are not correct.
[Verizon Samsung Galaxy S III] ThePagel:
In fact can you two please change your first posts and remove the link to your aboot. I am positive it is not what we want so let's not have people download them.
[Verizon Samsung Galaxy S III] Dadud:
Done
[Verizon Samsung Galaxy S III] revasm:
Loki exploit not compatible

Hey everyone,

I'm sorry to bring bad news, but ML1 is hardened against the Loki exploit. boot_linux_from_mmc checks boot headers now, and aborts if they attempt to overwrite aboot. check_sig is different as well, but I didn't examine it more.

IDA results: https://gist.github.com/revasm/8572927
[Verizon Samsung Galaxy S III] ProtheusIRC:
Great. More bad news...
[Verizon Samsung Galaxy S III] ThePagel:
well that's to bad. Is there any way we can get a side by side of the patched s4 with our s3?
[Verizon Samsung Galaxy S III] ProtheusIRC:
As I understand it, if someone with a GPE (unlocked boot loader) S3 dumps their aboot, we can hack this boot loader, right?
[Verizon Samsung Galaxy S III] ThePagel:
Someone might but I doubt you or I could.
[Verizon Samsung Galaxy S III] ThePagel:
Added some downloads to the op + the sad news. Ill wait to change the op to say this wont work until I get a second on his findings. I have no doubt he is right but hey never know.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
This does not exist.
[Verizon Samsung Galaxy S III] Dadud:
Seeing as all hope Is lost, I think it's time to look into kexxec, and see if that will still work.
[Verizon Samsung Galaxy S III] podspi:
I got the S3 after the bootloader had already been 'unlocked', but isn't kexec what was used before it was unlocked? Any reason why the old kexec won't work, or am I misunderstanding what devs did "back in the day"?
[Verizon Samsung Galaxy S III] Dadud:
Hashcode made kexec Roms for the droid 3, and safe strap that managed to boost it up to 4.3 from 2.3 before everyone moved on to greener pastures. so in theory, we could be able to do the same.
[Verizon Samsung Galaxy S III] ProtheusIRC:
Am I thinking about a Dev Edition S3?
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Yup. There's only a Play Edition S4, not an S3. Is there even any documentation that the Verizon dev edition S3 received the 4.3 update? I couldn't imagine it sold well either.
[Verizon Samsung Galaxy S III] ProtheusIRC:
Since there is no documentation to the contrary, I believe it did. It is an S3, which needs 4.3 to support Galaxy Gear.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
I see it has received the 4.3 update. No guarantees that even means anything for you all with regular edition, locked bootloader S3.
[Verizon Samsung Galaxy S III] ProtheusIRC:
Well if we can get ahold of that aboot, then that would presumably be the end of our locked bootloaders.