yashsingh1/xdaforums huggingface dataset:
[Android General] sc00bs:
Hi Guys

Am having a problem migrating my kids Clash of Clans village from my unrooted Nexus 7 running on a restricted profile. I would like to move their villages to a new tablet for them to use but am unable to do so because the restricted profiles on Android does not link to a Google+ profile and you need a Google+ acount to link up the app on the new device.

I was thinking, if I can back up their COC progress on the restricted profile and restore it onto a new regular profile on my Nexus 7, I can then link to a Google+ profile and I will be able to migrate their village to the new device.

I tried to use Carbon Backup to do this but it was unable to back up COC, Carbon says that it is unable to back up the App Data (it can backup other apps data but not COC's).

I would prefer not to have to Root my Nexus unless I really have too. Does anyone have any other suggestions as to what app I could use to back up COC to restore onto my new profile, can I do this without rooting?

Thanks

JohnB
[Android General] Pathera:
I think youll need root ... titanium backup

Gesendet von meinem GT-I9300 mit Tapatalk
[Vibrant General] waihung0626:
Thanks a sharing
[Vibrant General] skinzy98:
Let me know who ports what so we can get the original galaxy's back to life. Now if only I could build...
[Vibrant General] Black_Eyes:
Can you tell me how to Port Omni while taking CM as base? :confused: :rolleyes:
[Vibrant General] skinzy98:
To take cm as a base would involve decompiling and recompiling for all the framework files to work so as of now no. But why use cm as a base though?
[Vibrant General] Black_Eyes:
Don't have OMNI base :p

---------- Post added at 08:53 PM ---------- Previous post was at 08:29 PM ----------

@skinzy98 i was porting Mokee but systemUI force close ?

Any help please ?

---------- Post added at 08:54 PM ---------- Previous post was at 08:53 PM ----------

@skinzy98 i was porting Mokee but systemUI force close ?

Any help please ?
[Vibrant General] skinzy98:
Omni can be ported from the i9000. Is the system ui force closing in then other mokee thread? Also make sure everything was a clean download and make sure everything was done correctly
[Vibrant General] Black_Eyes:
I tried normal porting (replace framework , app , media , fonts )

Rom booted but systemUI force close

---------- Post added at 10:51 PM ---------- Previous post was at 10:50 PM ----------

I tried normal porting (replace framework , app , media , fonts )

Rom booted but systemUI force close :silly:
[Vibrant General] skinzy98:
Oh well that's probably why. You can't replace the certain frameworks with another ROM because each ROM is unique. It is built with certain features for each rom. If you'll follow the guide it should work fine.
[Vibrant General] smokey155193:
tried to port miui , stuck at boot screen, used miui by gtbluesky for i9000 and cm 10.1 for vibrant.
[Vibrant General] skinzy98:
Is miui 4.3 or 4.2?
[Vibrant General] smokey155193:
4.2.2
[Vibrant General] skinzy98:
Well then you need to download 4.2 ROM and use it to port it
[Vibrant General] skinzy98:
The is numbers have to be the same
[Vibrant General] waihung0626:
Can you port this rom:

http://xdaforums.com/showthread.php?t=1874086
[Vibrant General] skinzy98:
Possibly. Right now porting from fascinate and captivate and epic is questionable I'm still working on them booting
[Vibrant General] Galaxy3HELL:
Port from fascinate is very easy. I ported PA from fascinate, but its CMDA and you will not have Data and Network. Port only from i9000 or Galaxy S 4G, and try to keep clean developer section.

Dont port every ROM from i9000, port 1-2 ROM's so you can update it faster.

Thanks for you guide.

:) :) :) :) :)
[Vibrant General] skinzy98:
Ever ported from captivate. I've been working on getting dirty unicorns going and for some reason won't boot but I can't seem to get a log of the boot process from anybody.
[Vibrant General] Galaxy3HELL:
I can port it, but i dont know if anybody is still using 4.3.1 Android version. bye :)

---------- Post added at 06:06 PM ---------- Previous post was at 05:13 PM ----------

DirtyUnicorn 4.0 will be uploaded tommorow.

I must say, its great ROM, if 4.4.x version come, i will surely port it.

Thanks :)
[Vibrant General] skinzy98:
I can port it as I was doing it first just wondering if you had ever tried. I will set up the thread once a successful boot take place. I was just asking if you had
[Vibrant General] Cooptx:
Galaxy S 4G isn't good to port from. The hardware is similar, but somebody throw a frag into the software. It is a jumbled mess, we don't have GPS working at all over there and it is just a bad device to port from.

Questions:

Is it better to port from a built from source ROM as the base, or will I be okay using CyanAOSP as a base?

I am going to try to port PA from i9000...
[Vibrant General] Galaxy3HELL:
well, for my way porting isnt matter, clean CM or CyanAOSP, what ever you preffer.
[Vibrant General] Cooptx:
Is your way the way described here? and is it necessary to sign the zip?
[Vibrant General] Galaxy3HELL:
yes, its same, if you extract ROMs, you must sing them, but if you are working in zip. formats, no need to sing, just flash.
[Vibrant General] skinzy98:
He's right. As you are porting to the 4g it wouldn't matter. I use cm mainly for my main files for the port. But good gosh that phone is a mess. Mg aunt had it and I took a look at it then put it back cuz it was terribly supported by Samsung. If I started working with that phone could you test it for me?
[Vibrant General] Cooptx:
Possibly. But then I would have to stop work on the Vibrant. I get one or the other :P I am sure plenty of people in the S4G forum will test for you though.
[Vibrant General] Galaxy3HELL:
- Vibrant is having great support here, lots of ROMs.

- But we are missing good kernel.

- Somebody should build a good kernel :P
[Vibrant General] skinzy98:
Cannondale used to have a good kernel and so did ts1506. I know the vibrant has good support I'm saying the 4g didn't and still doesnt
[Vibrant General] Cooptx:
4G has great support from [MENTION=4571512]daothanhduy1996[/MENTION] he is going crazy with source built roms and he has been for a while. We just can't figure out the GPS...
[Vibrant General] cannondaleV2000:
I might try to build a kernel for the vibrant later and get you guys going. I'm eventually going to do the in brick mood with soldering and stuff. But i might have time to do a vibrant kernel this weekend
[Vibrant General] waihung0626:
I waiting your new vibrant kernel!:good:

but,you have time up the kernel?
[Vibrant General] Cooptx:
How do we go about getting this guide sticked?
[Vibrant General] dzee206:
i just hope people don't abuse it and clutter up the dev section with unsupported, abondoned threads. remember folks its a privilege to release roms to the community not a right..
[Vibrant General] skinzy98:
I learned that lesson the hard way. But now that my parents know I want to program when in get older they're OK with it
[Vibrant General] Cooptx:
Yeah, my parents aren't too keen with the amount of time I spend doing this stuff. I think I am going to stick with the three ROMs I have and maintain them in order to cut down computer time. Also going to have to cut down on how offer I check up on XDA :(
[Vibrant General] skinzy98:
Just check it on your phone either using the app or tapatalk. But yeah now that I've pretty much decided that's what I'm gonna do when I go to college they're OK with it
[Vibrant General] Cooptx:
They know that this is what I want to do. Lost my phone for a week :P I will do weekly ports if ROMs are updated.
[Vibrant General] waihung0626:
ROM the port only be a need to use these files come form vibrant?

bml_over_mtd

bml_over_mtd.sh

erase_image

file_contexts

flash_image

make_ext4fs

boot.img

usr all files

system\lib\modules all files

Modify files:

build.prop and updater-script

Finally re-sign up?
[Vibrant General] dzee206:
yeah thats pretty much it, cant really go wrong doing this. its straight forward and simple.
[Vibrant General] skinzy98:
Although you don't have to edit build.prop that just tells you the device name after you flash it
[Vibrant General] waihung0626:
Please forgive my English not good! I do it right?

---------- Post added at 03:50 PM ---------- Previous post was at 03:48 PM ----------

OK,thank U！
[Vibrant General] skinzy98:
What he's saying is yes those are about as good as it can get
[Vibrant General] dzee206:
dont worry bout your english its just fine and yes seems like you got it down. every thing you said is correct.
[Vibrant General] jellette:
oops, wrong post.
[Vibrant General] DSTNMZ:
can someone help

try to port this ROM for my use (ROM- http://xdaforums.com/showthread.php?t=2410699 and Semaphore Kernel ),starts well but an error message appears saying -- "unfortunately, the process com.android.phone has stopped" and after that will not let me do anything else

I made another port, the slimkat v4 and this works fine

could help solve the problem of the message above described

sorry for my bad English
[Vibrant General] dzee206:
this should help explain the issue a bit better as i suck at it lol....http://xdaforums.com/showpost.php?p=51224160&postcount=356

UPDATE: it could possibly be the kernel you used at fault, which version of semaphore did you use? if its 3.4.3 sv or even the v version it should work. older kernels built from source before march 2 can cause this issue from my experience.
[Vibrant General] skinzy98:
Yeah try using a different base ROM or wait for a newer base ROM build

sent from the bottom of a red solo cup
[Vibrant General] DSTNMZ:
Thanks

i use this -- Semaphore_KK_3.4.2sv I will try with another Kernel and base ROM thank you very much for your reply
[Vibrant General] skinzy98:
No problem if you don't mind my asking which device are you trying to port this for?

sent from the bottom of a red solo cup
[Vibrant General] DSTNMZ:
I try to do for the vibrant
[Vibrant General] skinzy98:
Alright well let me know how it goes

sent from the bottom of a red solo cup
[Vibrant General] DSTNMZ:
try various combinations of base and ROM:

Paranoid Android + cm11 basis including kernel -- starts well but does not mount the internal storage, after a reboot systemui stops and does not work

Paranoid Android + NeatKernel_vibrant_v1.06-[03-08] --- starts well but does not mount the internal storage

the same happened with the kernel Semaphore_KK_3.4.2v

Paranoid Android + Resurrection remix base/ kernel --- unfortunately the process com.android.phone has stopped

for now I will continue using the ROM slimkat until I learn a bit more about it
[Vibrant General] dzee206:
have tried this for mounting internal storage? http://xdaforums.com/showpost.php?p=44742840&postcount=5
[Vibrant General] skinzy98:
Are you copying the use folder over fro the base ROM to the port

sent from the bottom of a red solo cup
[Vibrant General] DSTNMZ:
I try but it's as if the memory was not there, appear only memory for applications

I copy this folder
[Vibrant General] dzee206:
thats weird i'll do a personal port of pa later on and see what happens. not at home right now so its gonna be a few hours before i can try but i'll report back with what happens and what rom/kernel i used.
[Vibrant General] skinzy98:
Just making sure are both the port ROM and the base ROM the same android version

sent from the bottom of a red solo cup
[Vibrant General] DSTNMZ:
thanks I would like to know your results if possible

greetings from México
[Vibrant General] dzee206:
every thing went smooth for me with pa no issues what so ever during the hour i ran it. what i used was pa from the I9000, for base i used vanir, as for kernel i used semaphore 3.4.3 v. it would be best to use vanir due to how its aosp just like pa and if you take a look inside system/share you'll see the the bmd and zone info folders which are for gps i believe, so using a cm base would just break gps. you must be over looking some thing during the process...
[Vibrant General] dzee206:
such a shame so many people are putting the ops info to use but only for personal use and not giving back to the community... now i see why most people keep this type of info for them selves.
[Vibrant General] skinzy98:
Or using it and saying they found w random guide online

clean installs are life. clean installs are love
[Vibrant General] nirogu325:
Thanks for the guide, [MENTION=4665640]skinzy98[/MENTION]. I managed to port the latest i9000 CM nightly to the Vibrant, but not all is well from the get-go. By only flashing the ROM, Wi-Fi doesn't want to turn on, if I flash the ROM + Semaphore kernel, the modem doesn't work, but the Wi-Fi does. If I flash the ROM, let it boot, then the kernel (after wiping both caches), then both modem and Wi-Fi works. Weird behavior, but it's better than nothing! All is now working in order. Screenshot attached. :highfive:

Edit: But meh, had to go back to my old nandroid. Looks like that nightly has some issues with the theming system. Themes do not stick properly.
[Vibrant General] skinzy98:
What kernel did you use originally for the port?

clean installs are love. clean installs are life
[Vibrant General] nirogu325:
The one from sada's 6/20 build over at the development forum.
[Vibrant General] skinzy98:
Try using a separate kernel aside from the one that is already packaged with it

clean installs are love. clean installs are life
[Vibrant General] nirogu325:
I did, I mentioned Semaphore earlier. It worked with that. Somehow internet videos breaks if I use a kernel that's not Semaphore. I think it may be related to bigmem and my cranky phone.
[Vibrant General] skinzy98:
Well make sure you're using the kcorrect version of semaphore. There are still two versions right? Like a v and an sv

clean installs are love. clean installs are life
[Vibrant General] nirogu325:
Yes. No issues on V (normal version). Issues appear on SV (version designed for SlimROMs). I think SV has bigmem. I wish to have Neat Kernel but with no internet video capability...it's a no-no. I am running the Gingerbread bootloader, and not the default one, do you think that might have an impact on this? (I have the default bootloader in a .tar just in case)
[Vibrant General] dzee206:
@skinzy98 thanks again bro for the tut wouldn't have been able to pull this off with out it. kind of was a pita to get up and running properly i had to swap out ril related files to get data working along with some hardware related files to fix screen rotation issue, with out it in landscape mode in goes into portrait mode and vice versa lol. damn thing bugged the hell out me...
[Vibrant General] skinzy98:
Awesome. What sgs2 you building for

clean installs are love. clean installs are life
[Vibrant General] dzee206:
it's actually a sgs2 rom ported over to my att note. I only bought the device cause my boy was selling it for cheap, 70$ got me the device with s-pen, with three spare cases, two USB cables, one wall charger, and a car charger and the best part not a single scratch on it. I got lucky on this deal.

Sent from my Half Baked Vibrant
[Vibrant General] epicboy:
This guide doesn't work for epic 4g. I ported a Rom over from vibrant to epic and it wouldn't install.
[Vibrant General] dzee206:
did you check to see if the updater-script matched up with the vibes such as this "mount("ext4", "EMMC", "/dev/lvpool/system", "/system");"? I've never tried to prt a rom from that device yet.

EDIT: I'll give porting from that device a shot, downloading schism 1.1-beta1 now. will report back with results.
[Vibrant General] epicboy:
i meant porting from vibrant to epic 4g. i own both devices and wanted to port spirit rom to it. but it wouldnt install. the updater script was messed up. maybe the use different terminology like you said..
[Vibrant General] dzee206:
same thing here just tried to flash it and it wouldn't install, i tried matching everything up in the updater-script and the build.prop, swapping out ril related files still no luck. the epic is a cdma phone might want to try porting a fascinate rom and see how things go or since you're compiling from source now try building it for the fascinate and port it over you may have better luck going that route.
[Vibrant General] skinzy98:
Their is a certain jar file you have to deco.pile, change, and then recompile to get it to work. I think it was the framework actually. I was gonna try porting cyanhacker a while ago but it was gonna take a decent amount of work to put it through and possibly not have everything working

clean installs are love. clean installs are life
[General Questions and Answers] nexasLT:
I rooted motorola motoluxe xt615 and after flashing to other rom it always boots into MBM Flash-mode and it always says "you enter flash mode because some error happens. Error code is 0202. Bootloader USB Init SECURE BOOT ENABLED. How can i fix this?
[General Questions and Answers] nexasLT:
Also when flashing it always fails at "Authenticate Android img..."
[General Questions and Answers] nexasLT:
bump
[General Questions and Answers] mel0man:
same the problem, how fix?
[Galaxy S 4 General] aresbv2000:
Ok guys...finally we have android 4.3 update for our I9506.You can download it from here.It's official but the download link is from terrafile.co since hotfile.com is closed for now.Flash at your own risk via Odin.

Here is a fast mega.co.nz mirror!!!
[Galaxy S 4 General] xenix96:
Currently downloading it .... i will see if Bootloader is locked/knoxed not dowgradeable ... will report you then:)
[Galaxy S 4 General] xenix96:
The results are attached!!!!

So stay on 4.2.2 if you dont want Konx Warranty void ****!!!!
[Galaxy S 4 General] aresbv2000:
Dude...your knox warranty is ok.It should be 0x1 if is voided.

Do not root at this time.it will void your warranty.Wait for some knox friendly root method.Anyway...my i9505 had knox status 0x1 and i had it replaced in warranty (by Orange Romania) for a faulty display.
[Galaxy S 4 General] xenix96:
well i see that i am not voided knox cause i get before upgraded device to official state again. then its no problem.

the thing is i only wanted warn the rest before they upgrade to 4.3

cause i think when you upgrade with a device wich have custom state you will maybe receive a knox waranty void 0×1 after the upgrade.

cheers and have a nice christmass :)
[Galaxy S 4 General] aresbv2000:
Thank you.Merry X-Mas.
[Galaxy S 4 General] gaglax:
Can someone link to the knox topic of i5906, thx.
[Galaxy S 4 General] aresbv2000:
Man...if you downloaded already the file...please upload it to mega or something else because terrafile.co kills me.I`ve been trying to download the file for about 2 days.I get an error everytime i try to download it."Unknown network error". Thank you.Merry X-mas!
[Galaxy S 4 General] aresbv2000:
Maybe someone can help me.I tried to flash the 4.3 image on my i9506 but odin fails it.Everything is ok until it flashes "hidden" then odin says "fail".Why and what can i do to fix that.The phone doesn`t boot anymore.thank you.
[Galaxy S 4 General] ynl078:
would this France 4.3 firmware work here in uk
[Galaxy S 4 General] Gilg@mesh:
you guys should not install the official 4.3 update if you care about root and custom ROMS in future, wait for custom ROMS instead without the crap KNOX

Sent from my GALAXY S4+
[Galaxy S 4 General] RotteRotte:
Which root you have?
[Galaxy S 4 General] Gilg@mesh:
I'm still on 4.2.2 with root, I'm waiting for custom ROMs that I hope arrive soon for this phone.

http://xdaforums.com/showthread.php?t=2529064
[Galaxy S 4 General] RotteRotte:
This is an OK bootloader without problems?
[Galaxy S 4 General] Gilg@mesh:
yes, the problems comes with 4.3 on this phone. so better wait for 4.3 custom ROMs w/o the new bootloader.
[Galaxy S 4 General] xenix96:
Its true what hes says ---> if you care Root dont Flash 4.3 Firmware!!!

I tested it.

If you root with 4.3 you got mass "Knox alert messages" in android !!!!! and you void Knox warranty to 0x1 in bootloader!!!!

The other thing you can not use anymore Heimdall or Odin(dont support 4.3 firmwares!!!!!) to flash anything on your phone also kies 2.6 you can not use anymore ..............have to update to 3.2 .... <--- everything tested!!

After i recognized theres nothing to do on this "super 4.3 firmware" i tried in terminal with abd shell dd commands to downgrade the Bootloader to go back 4.2.2 and what is the result ^^ -->

Phone is now hardbricked got only blackscreen nothing boots up !!! and i am using now a Nokia 3710 Fold :) till 30.12.2013 then i get rechanged my I9506 by a new one from servicecenter....

Again if you need root and dont want "knox warranty void" in your Bootloader STAY ON 4.2.2 !!!

Sorry for Caps :)

---------- Post added at 01:48 AM ---------- Previous post was at 01:41 AM ----------

Sure i can help you but you want really this 4.3 with "knox warranty void" in Bootloader ??

With odin and heimdall you cant flash 4.3 ... not supported!!

So if you dont care i can advice you how you update to 4.3 just do a post with text in it "yes help me please"

And dont blame if you want go back to 4.2.2 after updated to 4.3 :) .... cause its not possible by normal methods ... only with JTAG i think you can downgrade to 4.2.2 !!!

Also read here before you decide http://xdaforums.com/showpost.php?p=45666586&postcount=1

Cheers
[Galaxy S 4 General] mattish.91:
hello, have you found a solution to this? if you have please provide it, i got the same atm. Thanks
[Galaxy S 4 General] sorg:
While on 4.2.2, try to flash in Odin only following 3 parts: boot (don't mess with aboot!!), cache, system. Don't flash any other parts.

There parts are enough to fully upgrade to android 4.3.

It's better to avoid flashing modem from 4.3 because it has KNOX enabled bootloader image inside and may update it at any time by itself.

Probably, you won't be able to boot android with stock boot.img because of LKM authentication, but you may try. It won't brick your device. If you won't flash any other (except these 3) parts, then you always can boot into download mode and flash 4.2.2 parts ad still don't have any KNOX mentions in download mode.

Most likely, you will need custom kernel (boot.img) in order to continue to use old bootloader with android 4.3.
[Galaxy S 4 General] mattish.91:
Since i have no clue about what you mean by only flash three parts, i got one file and one file only, its a .md5. ho do i just flash some parts of it if even possible? and im not even sure i should flash that file since it's 4.3.

i would like to be pointed in the direction of a step to step help thingy, like i require this, and when i got it, do this. Thanks
[Galaxy S 4 General] nickytheshaft:
I flashed 4.3 and rooted to get my secmms out then flashed 4.3 again via Odin and no problems. Well my knox warranty is void but I don't give a damn. Des will find something for that.
[Galaxy S 4 General] RotteRotte:
Nice. I don't give a damn about KNOX either. But how did you root 4.3? Guide please? :D
[Galaxy S 4 General] xenix96:
You can use same root method to 4.3 like you used for 4.2.2
[Galaxy S 4 General] i900frenchaddict:
For me, using this same method with 4.3 ROM gives a temp root only, I mean I stop having root access if I reboot the device. So If I reboot,I go to recovery and flash the root .zip again.

(but Im using an E330s maybe that's the reason...)
[Galaxy S 4 General] xenix96:
Well the root.zip was originaly made for E330S so that should not be the problem.
[Galaxy S 4 General] falconik:
i900frenchaddict

I did use Samsung_Galaxy_E330_4.3 found on this forum, but it didn't work su was 1.43 and cant be updated and also it was in Chinese :cyclops: via recovery Philz_Touch__CWM_6.3.7_V5.15.0_unofficial_(fixed_preload) I did reflash ROOT_E330S_I9506 also found on this forum :good: and it can be updated via goggle play to latest version 1.86 root works even after restart :D

after update to 4.3 orange FR there was huge battery drain on sync to my exchange server, :confused: found someone with same problem on nexus4 and maybe it can be solved by the removing account, restart and setup account again, tomorrow I will try to setup account again....

some orange scrap that cant be removed, all data did remain on device so far so good :D