I realised when I ask questions, I always lump them into one paragraph, so I thought maybe I number them.
These questions are about boot animations.
1. What are the risks of installing/flashing a boot animation, if any?
2. For the I9305, where are the boot animations located? (I'm rooted, I searched for the files in Root Explorer, and there were some, namely bootanimation, bootsamsungloop and bootsamsung)
3. Can the boot animations that are made for other devices work on this device?
Thank you to those who answer my questions.
1. As far as i know there are no risk on putting custom boot animations since it won't replace any system files.
2. I don't know where it is really located on i9305 but it should be the same... on mine it's located on systemroot/data/local/.
(Custom boot animation requires a custom kernel by the way.)
3. I'm not quite sure on this but it may work since custom boot animations are just zip files.
OK, some more questions,
1. Do you need a custom kernel to modify the status bar and stuff?
2. I read more about boot animations, it seems that you can flash them through CWM without a custom kernel. Is that true?
3. What are the benefits and risks of flashing a custom kernel?
Hit thanks if I helped you! Sent from my awesome i9305!
herobrine_second said:
OK, some more questions,
1. Do you need a custom kernel to modify the status bar and stuff?
2. I read more about boot animations, it seems that you can flash them through CWM without a custom kernel. Is that true?
3. What are the benefits and risks of flashing a custom kernel?
Hit thanks if I helped you! Sent from my awesome i9305!
Click to expand...
Click to collapse
1. Nope. You need a custom framework such as Jkay's framework to modify the status bar. I just don't know if jkay's framework will work on the i9305 you can try searching the forums for a custom framework for the i9305 and see if you can modify the status bar.
2. Oh right you can just flash them through cwm. Kinda forgot sorry lol.
3. Risk of a custom kernel? Hmm... i think there are none, in fact custom kernels are way more better than stock kernels in my opinion. I've been running a custom kernel 3 weeks after i got my s3 and i've not encountered a single problem so far. Benefits of running a custom kernel really depends on how you configure it.
SignetSphere said:
1. Nope. You need a custom framework such as Jkay's framework to modify the status bar. I just don't know if jkay's framework will work on the i9305 you can try searching the forums for a custom framework for the i9305 and see if you can modify the status bar.
Click to expand...
Click to collapse
Jkay's framework works like a charm, but with Samsung based ROM's (JB 4.1.2).
Ok, one last question (hopefully)
If I flash the stock Samsung ROM (if I feel like I want to), will all my mods I've flashed be erased, and returned to stock Samsung? Like, if I have installed boot animations, status bar mods, root, custom kernel, will all these be gone? Will I return to stock Samsung ROM like out-of-the-box? (I understand that if you flash a ROM, that is either the same ROM or an updated version of it, you wouldn't have to erase data, wipe cache to install the ROM right?) I know that CWM will not be gone, I will have to flash stock recovery, but this i'm not 100% sure.
herobrine_second said:
Ok, one last question (hopefully)
If I flash the stock Samsung ROM (if I feel like I want to), will all my mods I've flashed be erased, and returned to stock Samsung? Like, if I have installed boot animations, status bar mods, root, custom kernel, will all these be gone? Will I return to stock Samsung ROM like out-of-the-box? (I understand that if you flash a ROM, that is either the same ROM or an updated version of it, you wouldn't have to erase data, wipe cache to install the ROM right?) I know that CWM will not be gone, I will have to flash stock recovery, but this i'm not 100% sure.
Click to expand...
Click to collapse
I'm not quite sure what you mean but i think i've tried it once. I was on EMMA2 firmware and I upgraded to EMC2 via Mobile Odin Pro. I think it only kept my apps, settings and some mods but i encountered some problems so what i did it start from scratch and restored some apps by using Titanium Backup. And CWM won't be gone as long as you don't flash another custom recovery or the stock recovery.
My point here is if you want everything to go smoothly is...
1 Backup everything via Nandroid.
2. flash the stock rom
3. root it
4. Install any mod you want may it be a custom kernel, rom, framework etc.
This way you won't encounter any problems while flashing a new stock ROM. But hey my understanding could be wrong Better search the forum deeply since more users might answer your question properly.
herobrine_second said:
Ok, one last question (hopefully)
If I flash the stock Samsung ROM (if I feel like I want to), will all my mods I've flashed be erased, and returned to stock Samsung? Like, if I have installed boot animations, status bar mods, root, custom kernel, will all these be gone? Will I return to stock Samsung ROM like out-of-the-box? (I understand that if you flash a ROM, that is either the same ROM or an updated version of it, you wouldn't have to erase data, wipe cache to install the ROM right?) I know that CWM will not be gone, I will have to flash stock recovery, but this i'm not 100% sure.
Click to expand...
Click to collapse
As far as I know, restoring/flashing stock ROM will erase everything on your internal memory, cause flashing stock ROMs are trought/with Odin (*.tar or *.md5 file). So, be careful what you're doing!
But what I understand is if you flash a ROM that is an update or the same version of the ROM that you are on, your data doesn't wipe, oh well, I learnt something new today.
Hit thanks if I helped you! Sent from my awesome I9305!
I used this boot enablemod install to get them working and just flash the boot files
http://forum.xda-developers.com/showpost.php?p=31833122&postcount=4
---------- Post added at 05:31 PM ---------- Previous post was at 05:22 PM ----------
More info here aswell, i think if the animation is not compatible you just get a black screen.
http://forum.xda-developers.com/showthread.php?t=2077101
http://forum.xda-developers.com/showthread.php?t=1053250
http://forum.xda-developers.com/showthread.php?t=1494591
http://forum.xda-developers.com/showthread.php?t=2063280
Harthouse said:
As far as I know, restoring/flashing stock ROM will erase everything on your internal memory, cause flashing stock ROMs are trought/with Odin (*.tar or *.md5 file). So, be careful what you're doing!
Click to expand...
Click to collapse
nah, flashing with odin doesn't wipe data. but you'll need to do it manually anyway, same as flashing any rom
Thanks to everyone who answered my questions! (basically everyone who posted in this thread-except me) But I have read from many places (on XDA, AndroidForums and many other places) that if you are upgrading from a ROM, or flashing the same ROM, you do not need to wipe data unless the developer asks for a wipe.
yup, I was talking about flashing a different ROM.
SignetSphere said:
1. As far as i know there are no risk on putting custom boot animations since it won't replace any system files.
2. I don't know where it is really located on i9305 but it should be the same... on mine it's located on systemroot/data/local/.
(Custom boot animation requires a custom kernel by the way.)
3. I'm not quite sure on this but it may work since custom boot animations are just zip files.
Click to expand...
Click to collapse
Do you know a good custom kernel that supports custom boot animations for i9305?
check the dev section
Anybody knows a stable custom rom for this model?
maharu567 said:
Anybody knows a stable custom rom for this model?
Click to expand...
Click to collapse
You can check the Android Development section of the forum for this device, and under the Index there are many.
Related
Pretty basic release. This is a deodexed version of the touchwiz wifi update.zip available in this thread: http://forum.xda-developers.com/showthread.php?t=1167250
I have not changed anything else in this ROM (though I am now working on a more streamlined touchwiz ROM using this deodexed version)
So no, this ROM is not meant to improve performance or fix any bugs from the stock touchwiz update. A deodexed ROM simply makes it possible/easier for devs to create patches that can address these issues, make themes, etc.
Warning: I am not responsibile for any damage you do to your device from flashing this update. Please be careful and follow the instructions below, and use at your own risk!
md5: 5a6a04a24f7f799b1b122d9e445110b2
Uploaded 7/22/2011: http://www.multiupload.com/WTU98VP2D5
-Fixed WiFi issue (thanks to DocRambone for the fix)
-Fixed /system not being wiped properly during update
Installing:
Download and place somewhere on your /sdcard directory
Boot into CWM
Wipe Dalvik Cache
Wipe /data and /cache (you can skip this if you had flashed the r4-7/19/2011 previously)
Install this zip from sdcard
---
Rooting:
Flash su_busybox_misc-sam_tab_10.1-051511.zip using CWM / Rom Manager: http://droidbasement.com/galaxy/tools/su_busybox_misc-sam_tab_10.1-051511.zip
---
Before reporting any bugs please make sure you have followed these directions. If you are getting a boot loop you most likely missed one of the steps above.
If you are getting the "service temporarily unavailable message" you need to sign into your google account, it should go away after you do that
Have fun themeing and modding!
~Shev
Thanks to:
pershoot - for the update.zip and the rooting zip
mughalgxt - for finding and sharing the stock touchwiz update
Does this mean i am the first...
To try this.....HMMMMM - let me sleep over it.
Oh - what the heck!
is this intended to be any less laggy or faster than other roms? Thanks for your hard worK!
Interesting....very interesting. Might have to give this a look-see...
rvrugg90 said:
is this intended to be any less laggy or faster than other roms? Thanks for your hard worK!
Click to expand...
Click to collapse
No, this update will make it possible to create and use modified versions of the apps + framework resources contained within the touchwiz ROM (i.e create themes, etc)
Damnit i just want panning and zooming working is it working on this one maybe deoxing it helped it work somebody willing to tesT?
Nice work here.
xSunny said:
Damnit i just want panning and zooming working is it working on this one maybe deoxing it helped it work somebody willing to tesT?
Click to expand...
Click to collapse
Are you talking about the special tilt / pan control? Just tested that, still doesnt work, but it may be possible now to patch the problem if someone can find it (in the deodexed resources).
Yeah I like the zoom feature, that's why I went back to the stock 3g touchwiz rom
Yeah i still didnt go back to stock 3g im just hoping somebody can find it in this deoxed rom but lets see
Can you pleaseeeee hook me up with the 3g touchwiz .zip??? IV looked everywhere! My tab is sooo slow with the wifi version but the 3g version, even with errors, was smoking fast! Thanks!
je2345 said:
Yeah I like the zoom feature, that's why I went back to the stock 3g touchwiz rom
Click to expand...
Click to collapse
Sent from the best phone on the planet (SGS2) running the best ROM on the planet (Cognition S2)!
Do I need to flash root, right after flashing the ROM? I tried to flash, without rooting right after and got caught in a boot loop. Restoring right now...but would like to flash touchwiz
roborob1969 said:
Do I need to flash root, right after flashing the ROM? I tried to flash, without rooting right after and got caught in a boot loop. Restoring right now...but would like to flash touchwiz
Click to expand...
Click to collapse
I don't think it really matters when you flash root bro. Make sure you are using pershoots tools pack though.
roborob1969 said:
Do I need to flash root, right after flashing the ROM? I tried to flash, without rooting right after and got caught in a boot loop. Restoring right now...but would like to flash touchwiz
Click to expand...
Click to collapse
The linked root zip is optional, you don't have to flash right after, you can flash it whenever (but dont use any of the other rooting zips available for this tab, the linked one is the only compatible version). Your bootloop is probably caused by not wiping /data+/cache or the davlik cache. Follow the instructions in first post.
daddymatt said:
Can you pleaseeeee hook me up with the 3g touchwiz .zip???
Click to expand...
Click to collapse
Enjoy.
http://www.megaupload.com/?d=XBAH8X7P
Followed the steps in the first post and it bootloop on me during the anime startup. I ODIN back to stock and then tried and the same. I then ODIN KFC stock, root and installed ROM Manager and followed the OP and still bootloop...
nakedninja42 said:
Followed the steps in the first post and it bootloop on me during the anime startup. I ODIN back to stock and then tried and the same. I then ODIN KFC stock, root and installed ROM Manager and followed the OP and still bootloop...
Click to expand...
Click to collapse
Did you try without ROM Manager the first time? If not try that first to be sure. Also provide device info please (wifi/3g/io/retail/v). I have not had any other reports of bootloops from people that were wiping data+cache+dalvik properly. You can try formatting /system (under CWM mount / storage menu option) if you are still getting this after manually doing everything through CWM at boot.
are you sure thats the 3G version? I went to download it and my pc sees it as exactly the same as the new wifi version... thank you sooo much for it either way! good looking out!!!
SellswordShev said:
Did you try without ROM Manager the first time? If not try that first to be sure. Also provide device info please (wifi/3g/io/retail/v). I have not had any other reports of bootloops from people that were wiping data+cache+dalvik properly. You can try formatting /system (under CWM mount / storage menu option) if you are still getting this after manually doing everything through CWM at boot.
Click to expand...
Click to collapse
Wifi Retail, Locked Bootloader
I am downloading it again to make sure its nothing weird with the zip. Every time I have flashed it was CWM not in the ROM Manager. Should I try that instead?
nakedninja42 said:
Wifi Retail, Locked Bootloader
I am downloading it again to make sure its nothing weird with the zip. Every time I have flashed it was CWM not in the ROM Manager. Should I try that instead?
Click to expand...
Click to collapse
No if its not working in CWM it wont work if you do it through ROM manager. Redownload and verify the md5 hash from the original post. Boot into CWM recovery, wipe everything mentioned and retry.
Hi everyone, I put a thread up a few weeks ago to ask if anyone would help me get rooted, so that i could put a different rom on my note.
i got a few PM's from some helpful people, but not enough back and forth messages to get me started.
so my question is....
Is there anyone online at the moment, that would help me get rooted.
Im not stupid so you wont have to keep explaining step by step.
I just want someone to guide me to exactly what it is i need.
i can happily add anyone on either skype, msn or whatever else you use, to guide me through it.
I really hope someone online at the moment is willing to help me. :good:
First of all, it is not enough to be just rooted for you if you want flash a new custom rom!
You must be on a safe kernel FIRST if you want avoid BRICK
I assume that you are on stock ICS. So if you are ona stock ics, be careful!
The easiest way for you to flash a custom rom is (assuming that you are on ics):
−Go to settings> about phone > and check which rom you have (for ex. IMM76D.XXLRT - that means that you have xxlrt rom, or xxlrq or something else, if you are not sure put a screenshot, we will help you)
−Then go to : http://forum.xda-developers.com/showthread.php?t=1901191 And download a safe kernel depending on which rom you are. Place it on internal SD card.
− Go to stock recovery (VolUp+Home+Power, wait till samsung gt-n7000 logo appear, then realase all three buttons)
−when you are in recovery - "update zip from sd card" , choose your safe PhilZ kernel from internal SD card, then flash it. Now you are on a safe kernel, but dont do any actions (like flashing, wiping etc.) Yust reboot your device.
−Now in app drawer you will see a new icon called SuperSU. That means you are rooted.
- If you want to be 100% sure that you are on a new safe kernel, try reboot in recovery (volup+home+pwr) now you will se a new CWM6 recovery (it is different from stock, grey background color, if you not seeing it then somethings wrong, dont perform any actions in stock recovery, and ask for further help).
−Now you are ready for flashing your new rom (read OP in rom thread, and folow instructions for flashing written from devs)
If you are on stock GB, then steps are little different (we will discusing it later, now going in bed, it is little late in my time zone
If you do not understand exactly what you're doing, do not flash anything, better to read the sticky threads first, and the Q & A section of the forum, there are a lot of similar questions and answers
djoni_gitara said:
First of all, it is not enough to be just rooted for you if you want flash a new custom rom!
You must be on a safe kernel FIRST if you want avoid BRICK
I assume that you are on stock ICS. So if you are ona stock ics, be careful!
The easiest way for you to flash a custom rom is (assuming that you are on ics):
−Go to settings> about phone > and check which rom you have (for ex. IMM76D.XXLRT - that means that you have xxlrt rom, or xxlrq or something else, if you are not sure put a screenshot, we will help you)
−Then go to : http://forum.xda-developers.com/showthread.php?t=1901191 And download a safe kernel depending on which rom you are. Place it on internal SD card.
− Go to stock recovery (VolUp+Home+Power, wait till samsung gt-n7000 logo appear, then realase all three buttons)
−when you are in recovery - "update zip from sd card" , choose your safe PhilZ kernel from internal SD card, then flash it. Now you are on a safe kernel, but dont do any actions (like flashing, wiping etc.) Yust reboot your device.
−Now in app drawer you will see a new icon called SuperSU. That means you are rooted.
- If you want to be 100% sure that you are on a new safe kernel, try reboot in recovery (volup+home+pwr) now you will se a new CWM6 recovery (it is different from stock, grey background color, if you not seeing it then somethings wrong, dont perform any actions in stock recovery, and ask for further help).
−Now you are ready for flashing your new rom (read OP in rom thread, and folow instructions for flashing written from devs)
If you are on stock GB, then steps are little different (we will discusing it later, now going in bed, it is little late in my time zone
If you do not understand exactly what you're doing, do not flash anything, better to read the sticky threads first, and the Q & A section of the forum, there are a lot of similar questions and answers
Click to expand...
Click to collapse
I think i've just got rooted using this method....
http://rootgalaxynote.com/galaxy-no...on-galaxy-note-gt-n7000-no-computer-required/
i followed the video step by step and it all went well, i then done the kernal as well which come with it.
so my question is.... how am i sure if the rooting went well? and how do i go about putting a rom on.
i like the look of this 1....
http://rootgalaxynote.com/galaxy-note-roms/sweet-ics-rom-for-galaxy-note-gt-n7000-note-2-gallery/
I've sent you a PM mate :good:
@djoni_gitara - excellently advised
Sent from my GT-N7000
jeetu1981 said:
@djoni_gitara - excellently advised
Sent from my GT-N7000
Click to expand...
Click to collapse
Jeetu can you help me please?
as i said in my earlier post, i've got rooted via the method in the other post.
its all worked and ive got the 3.0.15 frankel kernal
how do i go about getting a good rom now?
Are you on ics?
Check this- http://forum.xda-developers.com/showthread.php?p=30810194
And see if your kernel is safe to wipe and flash, I guess Franco kernel below v4 is not.
Flash some safe kernel and you will be good to flash any custom rom.
Edit- yes, you need to change kernel, check post #3 of this thread to change kernel- http://forum.xda-developers.com/showthread.php?p=30574729
Once on safe kernel you can boot in cwmr and flash any rom after full wipe.
Sent from my GT-N7000
yes, before i rooted my note, i was on 4.0.4
i've done the root via the method in the link in my previous post, and also installed the 3.0.15 frankel kernal.
i just want to know how to go about installing a nice rom now.
and also how do i change the kernal if i need to, as i know some roms work better with different kernals.
I'm going to send you a PM mate.
HOW TO PREPARE i9070 CUSTOM ROMS TO WORK ON 9070P
disclaimer as usual - everything on your own responsibility still, seems to be quite safe, the worst ever happened is no gsm signal if using not appropriate /lib/tee folder files. no soft/hardbricks reported (yet )
technical details - scroll a bit down
----
part 1: /system/lib/tee folder to replace
Jelly Bean Stock ROMS and ones based on Samsung Stock ROMs (Harshjelly, PureVanilla, LightJB..)the most important information: in order to get i9070P Jelly Bean modded stock ROMs working, you have to:
1. download this file: http://d-h.st/vUw
2. save the file on your sd card (preferably external sd, not the internal memory)
3. flash your desired rom, do all neccessary wipes and so on, but DON'T REBOOT YET!
4. you have to install the zip downloaded in step 1 (don't confuse the order of steps 3 and 4, otherwise your rom won't work for 9070P, ie. you won't have any radio modules working - gsm, wifi, bt)
5. reboot and enjoy
tested by users on various modded stock roms (read all the pages); the one above works on stock-based ROMs only,
----
CyanogenMod ROMs
for CM10, CM10.1 and CM10.2 file here: http://d-h.st/E9e
proceed exactly as steps described above
thx Mr.xD97 - files for /system/lib/tee extracted from his rom here http://forum.xda-developers.com/showthread.php?t=2278169
according to hannez_r
Tee folder from JB 4.1.2 TW works on CM11.
Click to expand...
Click to collapse
- thx for the info
-------------------------
part 2: the build.prop incompatibility:this happens if you attempt to flash custom roms straight from your 9070P stock ROM. once you successfully flash any i9070 ROM, you won't be bothered with the issue (until you reflash your stock ROM with odin again)
in case flashing of your target rom ends immediately with an error ("assert failed: getprop....") then you have to do something with your build.prop. The explanation for that happening is: there are build.prop entries stating that the phone is "9070P" and the updater-script prevents your target ROM from being flashed to an uncompatible device (not an "9070")
possible solutions:either: 1. grab some build.prop editors prior to flashing anything and change all occurences of "9070P" to "9070" and "janicep" to "janice". like this one: https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor or just edit your build.prop manually.
or: 2. unzip the target ROM .zip file, go to \META-INF\com\google\android and erase the lines starting with "getprop" (do NOT use windows notepad - it breaks the file, use notepad++ instead), save the edited updater-script and push it to the sd card. you're ready to flash the ROM
3. [automatically, to be tested] - waiting for your reports. ; use the build.prop.to.9070.zip to spoof your build.prop to i9070 model; it's a CWM flashable that should change the contents of your build.prop automatically. all credits for the script go to the author of this post: http://forum.xda-developers.com/showpost.php?p=19093919&postcount=20 - remember, not tested yet, in case you still get an assert:getprop error after flashing this .zip, try rebooting recovery and install the ROM .zip then method 3 most probably not working, so don't test unless you have lots of spare time to play with your phone
--------
source and inspiration:
I found that in galaxy ace 2 i8160/L/P forum - you have to replace /system/lib/tee folder (or 3 files inside) in order to flash custom roms made for i9070: there it is: http://forum.xda-developers.com/showthread.php?t=2159250
BUMP.
situation changed a lot. i9070P owners - try solution above
---
no more time today
btw. forgot to tell - take Gingerbread version of suppressed, no one knows what happens when you try with JellyBean version!
Woooow thank you
Gesendet von meinem GT-I9070P mit Tapatalk 2
If I understand properly, I should be able to download JetMod ROM. Replace the three files in the ZIP “tee” directory, “cops_ta.ssw, custom_ta.ssw, smcl_ta_8500bx_secure.ssw”, with the same named files currently in my phone, go to TWRP, Wipe System, Wipe Cache, Wipe Dalvik Cache, Factory reset, then install JetMOD zip?
Does this seem correct?
purplepizza said:
If I understand properly, I should be able to download JetMod ROM. Replace the three files in the ZIP “tee” directory, “cops_ta.ssw, custom_ta.ssw, smcl_ta_8500bx_secure.ssw”, with the same named files currently in my phone, go to TWRP, Wipe System, Wipe Cache, Wipe Dalvik Cache, Factory reset, then install JetMOD zip?
Does this seem correct?
Click to expand...
Click to collapse
yes, exactly. that way works for suppressed amoled/megatheme and for custom roms for ace 2 (ofc for ace 2 they use their /tee files respectively). so no reason it shouldn't work for jetmod.
---------
BTW curious to ask if anybody dared to flash any custom JB rom over recovery to 9070P? guinea pigs needed
You are awesome! Jetmod works great! Thank you!
thanks!!
Oh thank you very very much! I have one question... Now it is not possible try to flash a Jelly Bean rom for 9070 ok.. But in future owners of 9070P will get Jelly Bean probably this method will work also for Jelly bean custom roms for 9070?
FollonSaxBass said:
Oh thank you very very much! I have one question... Now it is not possible try to flash a Jelly Bean rom for 9070 ok.. But in future owners of 9070P will get Jelly Bean probably this method will work also for Jelly bean custom roms for 9070?
Click to expand...
Click to collapse
most probably - yes.
------
btw. I tried to run NFC on suppressed, but no go - deodexed NFC.apk, NFCTestmode.apk and Tag.apk, pushed to /system/app and set permissions, but still no way to run NFC. in case You people have any ideas, let me know fortunately not a dealbreaker to me.
adamuadamu said:
most probably - yes.
------
btw. I tried to run NFC on suppressed, but no go - deodexed NFC.apk, NFCTestmode.apk and Tag.apk, pushed to /system/app and set permissions, but still no way to run NFC. in case You people have any ideas, let me know fortunately not a dealbreaker to me.
Click to expand...
Click to collapse
If you have a native i9070p ROM... search the system folder for any file that contains nfc in the name, and copy it from the native i9070p ROM to suppressed. P.S. use windows search function
Another question: after flashing a custom rom for 9070 on 9070P is flashed also the kernel for 9070... Can we use kernel of the rom or we should change te kernel with CoCore-P? Thank you for the reply
FollonSaxBass said:
Another question: after flashing a custom rom for 9070 on 9070P is flashed also the kernel for 9070... Can we use kernel of the rom or we should change te kernel with CoCore-P? Thank you for the reply
Click to expand...
Click to collapse
as long as the kernel you currently use works OK - no need to worry; but check your CPU usage as some users reported excessive CPU usage all the time for older cocore kernels. I can confirm that cocore 4.1(for non-NFC version) and cocore-P don't have that issue
--
still no luck with NFC - the files I used are the only ones that can have anything in common with nfc. it gets even worse upon reboot as the NFC service app pops up FC window every three seconds and doesn't stop until I deleted it and rebooted again :|
adamuadamu said:
as long as the kernel you currently use works OK - no need to worry; but check your CPU usage as some users reported excessive CPU usage all the time for older cocore kernels. I can confirm that cocore 4.1(for non-NFC version) and cocore-P don't have that issue
--
still no luck with NFC - the files I used are the only ones that can have anything in common with nfc. it gets even worse upon reboot as the NFC service app pops up FC window every three seconds and doesn't stop until I deleted it and rebooted again :|
Click to expand...
Click to collapse
Are you sure you included all the libs ?
You also need to include all the NFC system apps as well
My life has more downs than ups, but I try to keep it a balance.
CallMeVentus said:
Are you sure you included all the libs ?
Click to expand...
Click to collapse
thanks for the suggestion. forgot to compare the differences in libs between 9070 and 9070P roms. will look into it
I have never flashed a new ROM. I want to try JetMod. It seems more I search, more restoring options are presented. (TWRP Restore or TB) Can someone recommend the safest and easiest method for restoring user apps and settings (SMS, MMS, & Contacts) on the new ROM? I have a TB and TWRP back up.
purplepizza said:
I have never flashed a new ROM. I want to try JetMod. It seems more I search, more restoring options are presented. (TWRP Restore or TB) Can someone recommend the safest and easiest method for restoring user apps and settings (SMS, MMS, & Contacts) on the new ROM? I have a TB and TWRP back up.
Click to expand...
Click to collapse
For Contacts I use the in-built backup feature....and SMS and MMS I usually use MyBackup Root for stock Messaging , otherwise when I'm using GO SMS Pro I use its in-built backup feature
My life has more downs than ups, but I try to keep it a balance.
Karsten95 said:
You are awesome! Jetmod works great! Thank you!
Click to expand...
Click to collapse
I must admit I tried Jetmod without success. Does not boot. Just startup screen being displayed.
I tried with default kernel and with cocore-P 1.0 kernel. Nothing worked. Might be something wrong with the installation (using TWRP in cocore-P 1.0). Installing system files seems to take just a fraction of second. And I suspect nothing was actually copied. I also tried replacing Aroma updater with the "regular one". Still the same...
Suppressed 2.2+2.5 worked. But it is not really my taste Should have tried 3.0 instead. But I would really like to try Jetmod. Any hints about the recovery?
Does CWM recovery for i9070 (non-P) http://forum.xda-developers.com/showthread.php?t=1987313 work for P devices? Anyone tried?
LaizyJumper said:
I must admit I tried Jetmod without success. Does not boot. Just startup screen being displayed.
I tried with default kernel and with cocore-P 1.0 kernel. Nothing worked. Might be something wrong with the installation (using TWRP in cocore-P 1.0). Installing system files seems to take just a fraction of second. And I suspect nothing was actually copied. I also tried replacing Aroma updater with the "regular one". Still the same...
Suppressed 2.2+2.5 worked. But it is not really my taste Should have tried 3.0 instead. But I would really like to try Jetmod. Any hints about the recovery?
Does CWM recovery for i9070 (non-P) http://forum.xda-developers.com/showthread.php?t=1987313 work for P devices? Anyone tried?
Click to expand...
Click to collapse
well, probably someone that's using jetmod on 9070P will tell you how to do it. but to be sure: did you start with 3.0, run the android wizard->rebooted to recovery->installed->3.1->rebooted to system->rebooted to recovery->installed 3.2 ? AFAIR when I was using i9070(non-P) I had to proceed these steps as flashing 3.0 + upgrades without reboots in the meantime caused bootloop or similar
as far as CWM is concerned - 1. it's temporary 2. it's meant for JB roms 3. never tried it on 9070P due to the fact TWRP always worked for me
Thank you very much adamuadamu... It worked very well for me... I installed jetmod 3.0 and i've done all the update to 3.2.2 without any problem
So none tried to do the same thing with Jelly Bean roms right?
FollonSaxBass said:
Thank you very much adamuadamu... It worked very well for me... I installed jetmod 3.0 and i've done all the update to 3.2.2 without any problem
So none tried to do the same thing with Jelly Bean roms right?
Click to expand...
Click to collapse
I'm pretty sure JB ROMs will have the same issues that GB non-P ROMs had....and we don't have the JB /system/tee files and kernel to deal with it
My life has more downs than ups, but I try to keep it a balance.
CallMeVentus said:
I'm pretty sure JB ROMs will have the same issues that GB non-P ROMs had....and we don't have the JB /system/tee files and kernel to deal with it
My life has more downs than ups, but I try to keep it a balance.
Click to expand...
Click to collapse
I think the lib/tee files are the main concern at the moment to get JB ported.
I have downloaded official kernel sources for i9070. And it includes config for 9070P as well. I managed to build the 4.1.2 kernel image for 9070P. But I don't really want to test it myself. I am not confident that it won't brick my device
So far, most of brave ones who have tried 9070 JB image on P-device have got a brick. If anyone could explain the reason, would be nice.
Does anyone know, if the reason is wrong kernel? Or is there something else in the JB installer that causes that. Some hboot partition or something?
Modem partition?
What i have done in the last 24 hours:
1. Updated to 4.3 on stock ROM
2. Unlocked bootloader on my Z1
3. Flashed "PhilZ Touch 6" dual bootloader (idk what "dual means" :S) (Dec 3 2013 version)
4. Used the built in root tool in "PhilZ" to root my phone and installed the corresponding app "SuperSU"
Questions:
Does bootloaders come with a custom kernel?
My bootloaders "About" says its made for the "Z" (not Z1). Did i **** up or is this incorrect?
If i flash kernel (for my device) via CWM will i break something?
Does roms require a certain kernel?
Can i flash .img files via CWM or is it required that the file is .zip?
I see kernels on the forum that advertise being 4 kitkat, do i need to flash that kernel WITH a kitkat rom to use that kernel?
Why shuld i flash a kernel?
As CM is not officially supported on the Z1 yet is there a cool alternative rom i can use?
Thats all the Q's i came up with, hope you can help me answer my ridiculous questions and wish me luck on my first android phone! :good:
bump
I won't get my device until tomorrow, but there a few things I could explain:
Some ROMs need to have a specific kernel. You cannot use Stock kernel with Cyanogenmod, or vice versa. Custom kernels are often a good idea to flash if you want some extra optimizations, you can get extra performance and save battery life with an enhanced kernel.
As for an alternative ROM, why don't you just check out the dev forums? There are Cyanogenmod ROMs, they're just unofficial.
Also, did you back up your TA? Otherwise, you'll be in for some real big trouble.
kusanou said:
I won't get my device until tomorrow, but there a few things I could explain:
Some ROMs need to have a specific kernel. You cannot use Stock kernel with Cyanogenmod, or vice versa. Custom kernels are often a good idea to flash if you want some extra optimizations, you can get extra performance and save battery life with an enhanced kernel.
As for an alternative ROM, why don't you just check out the dev forums? There are Cyanogenmod ROMs, they're just unofficial.
Also, did you back up your TA? Otherwise, you'll be in for some real big trouble.
Click to expand...
Click to collapse
****, i did not backup my TA. What does that mean for me?
I read in some threads that TA only gives you the option to revert back to absolute factory defaults. As i am having no problems i dont see why i would do that.
Edit: Thats wierd, my TrackID still works after unlocking bootloader, flashing recovery and rooting. Am i super lucky?
mrzone64 said:
****, i did not backup my TA. What does that mean for me?
I read in some threads that TA only gives you the option to revert back to absolute factory defaults. As i am having no problems i dont see why i would do that.
Edit: Thats wierd, my TrackID still works after unlocking bootloader, flashing recovery and rooting. Am i super lucky?
Click to expand...
Click to collapse
It's mostly needed for Bravia engine stuff, as well as the BIONZ image processor. I guess if you don't care too much about that, and you don't have any reason to have to go back to absolute factory settings in the case of a warranty return, then it should be fine.
Is it or is it not possible to install PA/CM and the like and use a masterpatch to get a rom working on the i537at&t or no custom fun for me?
NGD1 said:
Is it or is it not possible to install PA/CM and the like and use a masterpatch to get a rom working on the i537at&t or no custom fun for me?
Click to expand...
Click to collapse
No custom roms :crying: this locked bootloader means no cwm, no cm, no pa, no cwm, nothing custom no ifs ands or buts. The only roms available are stock based and imho it's more worth it to try to start learning how to decompile and modify system apks because that's the only real way to get the aosp feel back on this phone. Obviously you're gonna want to deodex your stock rom before you can really do anything major.
Nope. Only TW based roms and there aren't even any of those for this phone! Quite disappointing
You can get TWRP, so there's that.
thisisapoorusernamechoice said:
No custom roms :crying: this locked bootloader means no cwm, no cm, no pa, no cwm, nothing custom no ifs ands or buts. The only roms available are stock based and imho it's more worth it to try to start learning how to decompile and modify system apks because that's the only real way to get the aosp feel back on this phone. Obviously you're gonna want to deodex your stock rom before you can really do anything major.
Click to expand...
Click to collapse
http://blog.hash-of-codes.com/downloads/safestrap/
TWRP for bootlocked phones is called Safestrap. (See link)
It runs in the boot image right after daemons start!
Did deodexing work on your i537? Anything I need to know?
OctopusRift said:
http://blog.hash-of-codes.com/downloads/safestrap/
TWRP for bootlocked phones is called Safestrap. (See link)
It runs in the boot image right after daemons start!
Did deodexing work on your i537? Anything I need to know?
Click to expand...
Click to collapse
Use this thread if you're on NE3 or earlier, I can confirm it works as long as you follow the instructions which are easy and straightforward. (It says to use CWM but I promise it works just fine from SafeStrap).
If you are on NH3 use this thread, I can't confirm personally that it works but it sounds simple and has entirely positive feedback.
So yes deodexing works.