yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Pocket] streambinder:
As someone already might know, I'm streambinder, from MoltenMotherBoard team.

I have already followed some projects for the GT-S5300, but especially kept in contact

with some of the events related to the porting of ROM and Kernel sources for BCM21553 chipset based devices.

In this precise moment, the sources in my possession allow you to be able to compile

a bugfree CWM 5.0.2.8 (based on CyanogenMod 7 code) with a kernel based on the Samsung stock one.

The only - fundamental - problem was due to the fact that unless I hadn't used the prebuilt INIT binary

token in the Samsung stock firmware boot.img, the phone would not work - or, better, boot up.

This means that until the situation - regarding this issue - doesn't change, our access to the porting of custom ROM

would be barred.

Recently, I decided to give Cori another chance and rework my sources, looking at the wonderful work brought

by the BroadcomCM team on CyanogenMod 9 (in particular, thanks to [MENTION=4686683]bieltv.3[/MENTION] and [MENTION=2386505]Alberto96[/MENTION]) and [MENTION=3877378]psyke83[/MENTION] on CyanogenMod 11.

They've not only been able to run these two ROMs in a more or less crude way, but this developer has been able to write

the necessary strings to make the INIT binary of some of these BCM21553 devices opensource.

Strong of this informations, I readjusted some of the sources of BroadcomCM's CyangenMod 9, which includes

all the progress carried out by both the team and psyke83, in order to make them work even on Cori,

and am now next to the first test of the CWM 6.X.X.X, based on IceCreamSandwich code.

At the same time, [MENTION=5669389]akhbh[/MENTION] is working on the KitKat code based CWM.

I hope I can give more information about any progress as soon as possible.
[Samsung Galaxy Pocket] akhbh:
The General Discussion thread for non-development issues is here:

*.[DISCUSSION] CyanogenMod 11 For Galaxy Pocket GT-S5300 Discussion Thread
[Samsung Galaxy Pocket] streambinder:
Made a first test of CWM based on CyanogenMod 9 code.

It seems it cannot flash it as it weighs so much compared to its partition configuration value: in fact, the maximum boot partition size is set up to 5.0MB, but the compiled boot.img weighs 5.3MB.

Will have to resize its weight in order to make it fill into the partition.

[MENTION=5669389]akhbh[/MENTION], have you had any complication in these terms, with CyanogenMod 11 sources?

[MENTION=3877378]psyke83[/MENTION], what do you suggest to do? Do you think an increasement of boot partition would be a better idea?
[Samsung Galaxy Pocket] akhbh:
No, I didn't faced those complications. My boot.img weighted around 4.5 MB in lzma compression mode. In gzip, it increased to more than 5 mb.
[Samsung Galaxy Pocket] streambinder:
Perfect.

Which kernel have you based your build on?
[Samsung Galaxy Pocket] akhbh:
Well, I took the GeTux kernel for cori, had to change the board name though and then compile it. CWM was booting even before changing the board name but there was no reaction from the phone on trying to boot cm9/cm11

And after changing board name, a black screen on trying to boot

Another info: When tried to merge cori source into the bcm21553 common one, it did compile but gave bootloop of GT-S5300 logo on trying to boot as well as when trying to go in CWM.

Bieltv.3 recommended to use cori source instead of the bcm21553 common one so we used cori sources
[Samsung Galaxy Pocket] streambinder:
I suggest to use our Kernel sources for now, too: it will automatically bypass few errors/issues/bootloops that we cannot now fight with.

The most important thing is to make INIT working from sources (hope it will be working

on my CM9 sources, too) and check that every our configuration is correctly working and

making Cori boot into recovery.

Once we'll make it perfectly working without any kind of issue, will be the right time to try

to make Cori supported with the BC21553-common kernel.
[Samsung Galaxy Pocket] akhbh:
Okay, I will use your kernel sources and try if something is changed once I reach home. For now, I neither have this device nor a PC, as I'm in another city.

Will be keenly watching your work. Will start after reaching home around the end of September :)
[Samsung Galaxy Pocket] streambinder:
No problem, mate.

Here you have every source in my possession:

platform_kernel_samsung_cori

platform_device_samsung_cori

Keep in contact with me, as I will need some informations by you.

Anyway I'm now making another build, keeping some not so much important binaries excluded, so that I can make the compiled boot.img fill into our little Cori's boot partition. I know it's a dirty workaround, but if it works, I'll use it untill [MENTION=3877378]psyke83[/MENTION] will suggest me a better way to do.
[Samsung Galaxy Pocket] cleverior.ipul:
have u tried to build cwm v6 from cm9 source ??
[Samsung Galaxy Pocket] streambinder:
Of course, mate. I'm working on it, right now.

It doesn't seem to boot, strange if the same INIT binary sources are working for [MENTION=5669389]akhbh[/MENTION].

#UPDATE

In order to troubleshoot, I'll give you some info.

For his build I used these sources:

platform_kernel_samsung_cori

platform_device_samsung_cori

android_device_samsung_bcm21553-common

Applied some lines on our bcm21553-bootimg.mk, too, in order to exclude parted and mke2fs and make the compiled boot.img weigh less.

[MENTION=4929006]cleverior.ipul[/MENTION], can you link me your kernel sources, as akhbh said he used your ones for CM11.

[MENTION=5669389]akhbh[/MENTION], which modifies have you applied in order to compile CWM based on CM11 code? Which device tree?

#UPDATE 2

Attached my compiled boot.img.

If anyone of you would extract it (you can easily use this tool: bootimgtools - read how to use it in the README) and make a diff with the CM11 one (just extract the ramdisk of both boot.imgs and - in the terminal - use this command: diff -urN /path/to/cm9/ramdisk /path/to/cm11/ramdisk > diff.patch), would make to me a huge favour.

Let me know.
[Samsung Galaxy Pocket] akhbh:
I think we didn't had significant changes. Perhaps the same as totoro. But, that resulted in the internal_sd not mounting error in cwm.

Sadly, as said before, I am away from my home city and can't provide the files to you and can't do the boot.img diffs as well :(

Try to ask psyke83, he might have a solution for that
[Samsung Galaxy Pocket] streambinder:
Then, if you didn't make any massive change upon the sources, then I'll only try using your kernel.

Can you give me your kernel sources, mate, please? :)
[Samsung Galaxy Pocket] akhbh:
Currently, I can provide you the boot.img only. For the sources, [MENTION=4929006]cleverior.ipul[/MENTION] can provide the kernel sources coz as said earlier, his kernel is used. Well, we were working together to bring cm11 but weren't successful
[Samsung Galaxy Pocket] streambinder:
Ok, please send it to me, will compare it with my package. ;)
[Samsung Galaxy Pocket] akhbh:
Here it is:

http://www.4shared.com/zip/1nKFbOJ2ba/ccccGetux_CM11.html
[Samsung Galaxy Pocket] cleverior.ipul:
here the link source https://github.com/cleverior/android_kernel_samsung_cori

i've changed the board name. If your device can not boot after using the zImage from this source, then rename init.bcm21553.rc to init.gt-s5300.rc.
[Samsung Galaxy Pocket] akhbh:
[MENTION=5889675]streambinder[/MENTION], what is grom? As bieltv.3 said that init built grom for cori is required to fix adb over cwm recovery. If adb gets working, then possibly the black screen while booting cm11 might get fixed
[Samsung Galaxy Pocket] streambinder:
Sincerely don't what are you talking about.

Anyway, have to try to understand where's the problem with the not-booting CWM.

Will try with your sources and let you know. ;)
[Samsung Galaxy Pocket] akhbh:
What problem are you encountering? A black screen or bootloop? Coz at the start, I was getting a black screen on cwm
[Samsung Galaxy Pocket] streambinder:
Stuck at Samsung bootsplash.

In charger mode, the battery icon compares for an instant, and then stuck again at Samsung bootsplash.
[Samsung Galaxy Pocket] akhbh:
At start, I tried making a temp cwm v6.0.5.0 but it wasn't successful as that black screen came up and nothing happened. Then made a permanent cwm and again a black screen.

Then did some editings in the ramdisk and then it worked.

The same thing is happening on trying to boot CM11. Can't figure out what's going wrong
[Samsung Galaxy Pocket] streambinder:
Once you come back home, please, send me the sources you used to make CM11's CWM booting and CM11 bootlooping.

Will take some code from it and will help you with CM11.
[Samsung Galaxy Pocket] akhbh:
Honestly, it could take me more than a month or may be more. Sadly though.

What about the boot.img I provided to you. Did you compare its ramdisk with yours?
[Samsung Galaxy Pocket] streambinder:
Nope, these two days I haven't had the possibility to do it: been so busy.

I hope to do it today. ;)
[Samsung Galaxy Pocket] streambinder:
Hey [MENTION=5669389]akhbh[/MENTION] and [MENTION=4929006]cleverior.ipul[/MENTION], I'm almost ready to restart working on this.

How are you in this terms?
[Samsung Galaxy Pocket] streambinder:
That happens when you're trying to sync over some repos which have

some locals changes.

If you don't care about the changes you've made locally, just manually

remove the folders of the repositories which are giving you such errors,

and then resync. In your case, it seems something in .repo folder got

corrupted, so I suggest to you to restart from the beginning the sync. :)
[Samsung Galaxy Pocket] akhbh:
Hey!!! Welcome back streambinder,

First up I suggest you to compare my boot.img with yours
[Samsung Galaxy Pocket] cleverior.ipul:
how about i remove local manifest from .repo ??
[Samsung Galaxy Pocket] streambinder:
How many repos does your local-manifest subscribe?
[Samsung Galaxy Pocket] streambinder:
[MENTION=5669389]akhbh[/MENTION], was that boot.img booting?

Cannot extract it as it isn't compressed as in gzip format. How is it compressed?
[Samsung Galaxy Pocket] cleverior.ipul:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="androidarmv6/android_device_samsung_totoro" path="device/samsung/totoro" remote="github" />
<project name="androidarmv6/android_device_samsung_bcm21553-common" path="device/samsung/bcm21553-common" remote="github" />
<project name="androidarmv6/android_hardware_broadcom_brcm_usrlib" path="hardware/broadcom/brcm_usrlib" remote="github" />
<project name="androidarmv6/android_hardware_broadcom_fmradio" path="hardware/broadcom/fmradio" remote="github" />
<project name="androidarmv6/android_kernel_samsung_bcm21553-common" path="kernel/samsung/bcm21553-common" remote="github" />
<project name="androidarmv6/android_vendor_samsung" path="vendor/samsung" remote="github" />
<project name="androidarmv6/android_device_samsung_tassve" path="device/samsung/tassve" remote="github" />
</manifest>
[Samsung Galaxy Pocket] akhbh:
It wasn't booting. A black screen while trying to boot. But it booted in recovery. Its compressed in "lzma" format. When compressed in gzip format, it exceeded the 5 MB mark...
[Samsung Galaxy Pocket] akhbh:
Can you explain this error? Its while compiling CM9 for totoro. Is its tree in correct state? My friend is asking for totoro coz he wants to learn compiling for totoro first and then he would turn for cori

Install: /home/karthick/ROM/CM9/out/host/*

linux-x86/framework/mkstubs.jar Install: /

home/karthick/ROM/CM9/out/host/linux-

x86/framework/osgi.jar Install: /home/

karthick/ROM/CM9/out/host/linux-x86/

framework/screenshot2.jar Install: /home/

karthick/ROM/CM9/out/target/product/

totoro/root/res/images/charger/battery_

2.png Install: /home/karthick/ROM/CM9/

out/target/product/totoro/root/res/images/

charger/battery_charge.png Install: /home/

karthick/ROM/CM9/out/target/product/

totoro/root/res/images/charger/battery_

4.png Install: /home/karthick/ROM/CM9/

out/target/product/totoro/root/res/images/

charger/battery_fail.png Install: /home/

karthick/ROM/CM9/out/target/product/

totoro/root/res/images/charger/battery_

0.png Install: /home/karthick/ROM/CM9/

out/target/product/totoro/root/res/images/

charger/battery_5.png Install: /home/

karthick/ROM/CM9/out/target/product/

totoro/root/res/images/charger/battery_

1.png Install: /home/karthick/ROM/CM9/

out/target/product/totoro/root/res/images/

charger/battery_3.png Install: /home/

karthick/ROM/CM9/out/target/product/

totoro/root/init.gt-s5360board.bt.rc

Install: /home/karthick/ROM/CM9/out/

target/product/totoro/root/init.gt-

s5360board.fs.rc Install: /home/karthick/

ROM/CM9/out/target/product/totoro/root/*

init.gt-s5360board.gps.rc Install: /home/

karthick/ROM/CM9/out/target/product/

totoro/root/init.gt-s5360board.rc Install: /

home/karthick/ROM/CM9/out/target/*

product/totoro/root/init.gt-s5360board.se*

nsors.rc Install: /home/karthick/ROM/CM9/

out/target/product/totoro/root/init.gt-

s5360board.usb.rc Install: /home/karthick/

ROM/CM9/out/target/product/totoro/root/*

init.gt-s5360board.wifi.rc Install: /home/

karthick/ROM/CM9/out/target/product/

totoro/root/init.recovery.gt-s5360board.rc

Install: /home/karthick/ROM/CM9/out/

target/product/totoro/root/recovery.fstab

acp: file 'out/target/product/totoro/obj/ETC/*

recovery.fstab_intermediates/*

recovery.fstab' does not exist Install: /

home/karthick/ROM/CM9/out/target/*

product/totoro/root/ueventd.gt-

s5360board.rc make: *** [out/target/

product/totoro/root/recovery.fstab] Error 1

make: *** Waiting for unfinished jobs....

karthick@karthick-mostwanted:~/ROM/

CM9$
[Samsung Galaxy Pocket] streambinder:
Which device tree is he using?

It seems recovery.fstab path isn't correctly declared.
[Samsung Galaxy Pocket] streambinder:
Sorry, I no more own this device, so I announce I will stop development on my side.
[Samsung Galaxy Pocket] diestarbucks:
Thread has been closed at OP's request.
[Android Q&A, Help & Troubleshooting] Aspetazi:
Hi guys, I have a rooted LG su880. Can its gingerbread be updated to ice cream sandwitch or jelly bean.If yes, how. Please help.
[Android Q&A, Help & Troubleshooting] pulteb:
I believe Google said that they'll try to push L to gingerbread devices
[Android Q&A, Help & Troubleshooting] prashant13b:
Custom rom
[Android Q&A, Help & Troubleshooting] warlock9000nt:
http://www.idroidspace.com/5-best-custom-roms-for-lg-optimus-4x-hd-android-4-3-jelly-bean/
[Samsung Galaxy S Duos 2] androidify:
How To Root Samsung Galaxy S Duos 2

S7582​

​

Note: Make sure you have a Wi-Fi/internet connection to use this rooting app.

First, download the Root Master.apk here

Install it, look the ROOT大师 icon and open it.

Then tap the blue button, after that you’ll see a green button.

Tap the green button.

​

When the process is done reboot it manually.

After that download SuperSU app on GooglePlay. Note: You can convert SupeSu to system app

Install File Explorer (Root Explorer) then go to root folder of your phone

Find Kinguser.apk to /system/app/Kinguser.apk then delete it

Congratulations!​

Your phone is now rooted, you can download root checker on GooglePlay to check if your device is now totally rooted.​

Press Thanks! If I helped you. :)​
[Samsung Galaxy S Duos 2] bercerobry:
has anyone tried this method?
[Samsung Galaxy S Duos 2] androidify:
yes , many users in the Philippines, India, Thailand used this method
[Samsung Galaxy S Duos 2] bercerobry:
Its nice to try.. weird that no one posted a feedback. Rooting this fone is mainly for debloating I think. Habe you sucessfully debloted this with really unnecessary samsung apps that hogs resources?
[Samsung Galaxy S Duos 2] androidify:
they dont give feedback because many s duos 2 users are in their specific groups at facebook. their feedback are posted there. rooting s duos 2 can debloat your phone and also by adding tweaks to free up more ram
[Samsung Galaxy S Duos 2] bercerobry:
Okay. I can try that. But anyway what tweaks can I do to maximize the phone's resources..
[Samsung Galaxy S Duos 2] androidify:
once this rooting method works in your phone. please leave a feedback here. for others
[Samsung Galaxy S Duos 2] androidify:
you can use Greenify to free up your ram
[Samsung Galaxy S Duos 2] ramzidjoudi:
great work mate

it work for me without probleme

there is no Kinguser.apk in /system/app but irootsu.apk i delete it without probleme

:good::D:good:
[Samsung Galaxy S Duos 2] afraaa:
better to hit his thanks button beside feedback
[Samsung Galaxy S Duos 2] afraaa:
and thanks for intel

---------- Post added at 12:46 AM ---------- Previous post was at 12:44 AM ----------

What if we don't delete that apk ? i guess nothing happens right ?

works great and so easy ... thank u so much to share this . mine had kinguser ...
[Samsung Galaxy S Duos 2] suvo23:
When I install super su the it want to update and when I update it update failure. And also I checked through root checker . It's not root
[Samsung Galaxy S Duos 2] emulqi:
mediafire has blocked the apk

:crying:
[Samsung Galaxy S Duos 2] iamunique996:
The apk not found
[Samsung Galaxy S Duos 2] billytoro:
7582

not found apk file,place upload
[Android Q&A, Help & Troubleshooting] forgeting:
\

CPU : MTK6595

Display: 5.4'' 1920×1152

RAM: 2GB

ROM: 16GB/32GB/64GB

OS: Flyme 4.0 base on Android 4.4.4 supports ART

Camera: 20.7MP main camera

Battery : 3100mah

Price: ￥1799/16GB ￥2099/32GB ￥ 2399/64GB

Find from here：http://bbs.neonado.com/viewforum.php?f=12&sid=33a66d8d9bbf3145c679e01f90497e91
[Android Q&A, Help & Troubleshooting] e1to:
Just got the phone and love it..

LTE works with Rogers and Bell in Canada..

Not a big fan of Flyme ,I find it very buggy.

Im hoping for a cm rom of some sort. Would love to see something like the version on the onePlus .
[Android Q&A, Help & Troubleshooting] ThExSenatoR:
Agree. Phone is excellent, we only need a quality rom on it. However 4.0.4A is way better for me than 4.0.3A, but still faaar away from what I expected from this company.
[Android Q&A, Help & Troubleshooting] Supracer:
Ive been intrested in this phone for quite some time now and thinking of buying it.... I currently own a coolpad f1 and happy with it. The thing is a miss custom roms and modding from the xda community..... I see that the mx3 doesn't have any custom roms at all, same goes with the mx4?
[Android Q&A, Help & Troubleshooting] crunchor:
It would be perfect if they learn from OPO and has a custom rom other than their official rom. I read news and there is rumor about ubuntu touch team up with them, but seem like this will not really happen.
[Android Q&A, Help & Troubleshooting] Krystyna:
Meizu MX4 is a very good mobile phone, but I waited a month, still did not buy Meizu MX4, now I nearly bought Huawei honor 6.
[Android Q&A, Help & Troubleshooting] maxecume:
"Droidfish test" on Meizu MX4

[MENTION=3611536]e1to[/MENTION] [MENTION=233235]ThExSenatoR[/MENTION] [MENTION=371528]Everybody[/MENTION] !!

Could someone "benchmark" MX4 with Droidfish?

It could be "top" with its MT6595...

1) Install Droidfish on play. google:

https://play.google.com/store/apps/details?id=org.petero.droidfish

2) Clear all apps in background (hold home and swipe them away) and then run droidfish.

3) Press the menu button, invoke "Settings", choose "Threads" and select "Automatic", and then press back button to get back to chess board.

4) There is button with label "M" below chess board. Press it and choose "Analysis Mode". Analysis will start. Keep it running for about 1 minute.

5) After 1 minute passed, read and record the "nps:" number at bottom of the screen. This is the measurement I'm interested in. This value is a number of positions searched per second (in thousands). The higher the better.

6) IMPORTANT: To force program to STOP thinking, press "M" button again, choose "Two players" so that analysis will stop. Post the results here with rom information (optional). Stock rom is preferable but other roms are welcomed.

Thank you!
[Android Q&A, Help & Troubleshooting] wurx92:
1814k on my Meizu MX4 with Flyme 4.1.4A
[Android Q&A, Help & Troubleshooting] maxecume:
you're really f*cking great!!! ;) I've waited for that "evaluation" for more than a month... I send you a pm; have a"look"! thank you ;)
[Android Q&A, Help & Troubleshooting] julian77200:
Meizu MX4 Recovery mode?

I have an new MX4, but the Problem is, the Phone is Locked, because i have to often write an wrong pin. I would an Hard reset. I tried to press Vol+ and Power but nothing happens.

Pls help me, how i can go to the Recovery mode?
[Android Q&A, Help & Troubleshooting] JasonLeung:
The phone will reset all settings when you write 30 times wrong PIN , but data will be clear.
[Android Q&A, Help & Troubleshooting] ramachandram:
Use same key combination when switched off. Then it'll take to the recovery. But you need to have the update.zip file on the phone to make it work. Clear data and you'll have like a factory reset phone without losing all data on the memory. You'll lose all your apps though.
[Android Q&A, Help & Troubleshooting] aoleary:
Hi.

I dont own one of these, but looking to buy one, but the lack of a custom ROM is holding me back.

Apparently one can install a standard Android version, via this link:

Just delete all the spaces in the quoted text. Im not sure if its legit, and i have nothing to do with it, but you can try it anyway..
[Android Q&A, Help & Troubleshooting] chals91:
I think it´s a fake, because there are only 3 messages, no video in youtube (at least 1... but not, there isn´t anyone) and for download the rom they say you have to fill a test/quiz with your number and that makes you pay money with phone... the downloading page seems to be like fake too.... if this is real where are the forums here in XDA and links to MEGA, One Drive or Whatever?
[Android Q&A, Help & Troubleshooting] aoleary:
Sorry about that! I didnt download it myself, so I hadnt verified the authenticity of the files...
[Android Q&A, Help & Troubleshooting] PennyKnight:
There are 2 variants of this phone that I can find, the

M461

and the

M461U

.

Nether of them work with 4G/LTE on Rogers/Bell in Canada.

Bell has only 3G for both.

Rogers ether has 2G, or 2G/3G.

Where did you get your phone from and please post a screen shot of your 'About Phone' to validate your post .....

http://willmyphonework.net/
[Android Q&A, Help & Troubleshooting] android_94:
how can u do that, cause i try doing this but the device steel can't reset can you explain how to write 30 times wrong PIN
[General Questions and Answers] Michalica:
Hi all,

i got problem with my Jiayu G2F TD-SCMA (1280*720), accidentaly i installed new custom rom(lewa) for WCDMA(840*480) version of rom, to my TD-SCMA.

Sure, that rom dont boot proprely, then i realize it was bad rom, so i install back my backup with CWM. And then apear my bug with touchsreen.

It looks like it works still only at 840*480, just look at video, and screens. I gues its not hw problem, because it apear after installing wrong rom to my device.

-everythings other works fine

What i was try:

- using SP flashtool to flash official roms(2x versions), custom roms = no change

- format all smartphone using SP flashtool = no change

- install some calibration .apk's = no change

- get backup from my friend = no change

- and my fiend gues its not kernel problem, because he compared my kernel with his and its same

imgup.cz/image/X2E - androsenzor

imgup.cz/image/X2F - multitouch

youtube.com/watch?v=x-G85y3FBHg&feature=youtu.be - video of problem

my apologize, i dont have permission to add links to post.

Best regards.

Majkl
[General Questions and Answers] all00:
you have update your touch controller with wrong fw by flashing. it is still possible to flash it back, but you should have a loadable kernel with source of it. you should know a type of controller and find suitable fw (ex. on github). add fw in source code + add flash init block. in two words something like this. detailes you can google.
[General Questions and Answers] Killwish:
Bro flash stock Rom will solve this problem.
[General Questions and Answers] mousepad1:
Hi, I have the same problem, what is this please " Bro flash stock Rom" ?