Database Develop

HOWTO: flash custom GB and JB roms for 9070P (NFC)

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?

Can't Install Roms HELP PLEASE! Huawei U9000 Problems!

Hi I am new to this "romming" business. For my u9000 I installed UtterChaos kernel .32. Most to the roms require .35 kernel. And when I try to install SUT LR 1.8 it never works with windows 8 64 bit. I do have CWM Recovery, and I do have superuser permissions. But for some reason when I try to flash a different kernel like CK Kernel Lebay edition, the whole device gets stuck at boot. Yes I have wiped data, cache and davlik. before doing so. I had to then remove the batteries and put them back to start the phone in download mode to replace the boot image from a back up then go do a CWM restore. And I have tried doing factory resets but the UC kernel boot wont change.
Bottom line is, I AM LOST and I will be using this phone for a long time and I can use a way out of this and I need to find a very fast and stable rom with all working features.
What I have:
- .32 kernel
- UtterChaos kernel
- Custom SU
- CWM Recovery
What I need (please help):
- To get rid of UC kernel (boot, etc...)
- .35 kernel (if possible)
- SUT LR for Windows 8 64bit (if possible)
- A really good rom for heavy gaming, performance, stability, something other than GB (preferably JB or ICS)
I may be asking for too much, and sorry if I am, but I can use some help with this phone right about now.
Thanks in advance!

My answer
You can get 35.7 kernel here, depending on what rom you wish to use. Just flash it along with your preferred rom.
http://forum.xda-developers.com/showthread.php?t=1919097&highlight=kernel
For the rom, it really depends on your preference, because the performance is mostly the same between all the JB roms, smooth enough if you don't install lots of apps that stay in the background. Currently, I'm using the XperienceXperia JB rom. It's about as good as the other JB roms, just with Xperia stuff. Also, make sure that you don't put too much load on it, because it might freeze. No kind of software would be able to magically turn our phone into a gaming powerhouse, because it has an old, outdated gpu to start with. So, don't think about running games like Asphalt 8, because it probably wouldn't run.
http://forum.xda-developers.com/showthread.php?t=2479460
I'm not aware of a Win8 x64 compatible SUT LR, but I don't think you'd need it for anything besides flashing stock roms.
By the way, what rom are you using now? If you flash a cm10 (JB) designed kernel to a GB rom, it would definitely cause problems.
Sorry for the long reply, I don't know how to make it simpler.

THANKS
Hi thanks very much I am using the stock rom. Thank you sir :good:
And I suppose for any rom I flash the corresponding kernel first before I flash a rom?

2nd answer
_ikhan_ said:
Hi thanks very much I am using the stock rom. Thank you sir :good:
And I suppose for any rom I flash the corresponding kernel first before I flash a rom?
Click to expand...
Click to collapse
I'm not sure about the order myself, but I usually flash the rom first, then the kernel. I do this everytime I want to flash a rom, and I've never had any problems. Have you tried flashing one of the JB roms for this device? If you haven't tried, remember to wipe data and cache before flashing the rom, and backup your current rom just in case something goes wrong.

[Q] Howto: Fresh and clean install of official 4.1.2

Hi,
I own a Galaxy Note GT-N7000.
I never rooted it, just used two official updates provided by Samsung and then flashed the original 4.1.2 using Odin.
I have rooted my older Android phones (San Francisco) and used to try all kinds of ROM's on many Windows Mobile phones - I am not a exactly a noob, I just did not mess with my Note, because I am happy with it just like it is and because it is my work phone, which needs to be 100% working.
However, battery life is getting shorter (so I just ordered a new original Samsung battery) and, worse, the phone is getting more and more unresponsive.
This is the real problem: whenever I want to do something, it takes like 1-2 seconds, if not longer, before the phone reacts. This is very annoying. I don't have that many apps installed (I just stick with my preferred ones, instead of betting on sheer quantity). Still, the other day, the phone complained that there is no free space to install upgrades of some apps.
To make it short: how can I install a clean original 4.1.2 as if my phone was just purchased, i.e. with a clean flash?
Before you flame me and tell me I should spend the next month reading the forum: I already did!
I am afraid of the brick bug, so I guess that doing a wipe of the flash is not an option, as i guess that the bug has not been fixed by Samsung on 4.1.2. On the other hand, I do not want to root my phone, to install some custom kernel, to then wipe the flash and revert to the official ROM, risking to activate the counter, etc. Not that I don't know my way around flashing, soldering, building the flash dongle or even JTAG - I just don't have the time and nerve.
So my simple question: How do I securely wipe the flash and install a clean official 4.1.2 ROM on my phone, getting rind of 2 years of garbage files and God knows what else is slowing down my phone.
Many thanks for those guiding my way - I don't want to believe that there is a planned obsolescence in course, like Samsung building a timer that makes the phone get slower and slower...
Cheers,
vma

If you really want to enjoy the speed of your phone, IMO, you should go ahead and try CM /AOSP roms. They will give you some time out of the "slowness".
Just saying. On the other had if you want to be on the stock TW 4.1.2 rom, then doing a factory reset from the recovery will do the job. JB kernels for 4.1.2 seems to be safe to do a reset as there has not been cases of bricking on stock JB kernel.
But what my method would be to...
1. Install Philz kernel for JB using recovery and boot into recovery again... to get CWM recovery this time
2. Choose wipe data/factory reset ----> Clean for new rom install. (this will delete the current rom, data and cache)
3. Mounts and Storage -> Format Internal storage.
4. Mount USB storage and connect to PC... delete all files
5. Go to advanced menu and choose reboot download.
6. connect to PC and flash stock rom JB using odin,

Thanks for your reply.
However, you say:
nokiamodeln91 said:
On the other had if you want to be on the stock TW 4.1.2 rom, then doing a factory reset from the recovery will do the job. JB kernels for 4.1.2 seems to be safe to do a reset as there has not been cases of bricking on stock JB kernel.
Click to expand...
Click to collapse
While in another post it says:
"Warning :
Don't wipe anything from stock ICS recovery
Don't factory reset/Hard reset on stock ICS.
Don't flash any Wipe version of ICS ROM"
(http://forum.xda-developers.com/showthread.php?t=1424997)
This is what I don't get... Is it safe or not? Does this warning only apply to ICS, while JB is safe?
Cheers,
vma

Its applies only to ICS stock kernels. There is no evidence to prove that JB is safe. but Samsung seems to have suppressed the bug on JB kernels.

nokiamodeln91 said:
Its applies only to ICS stock kernels. There is no evidence to prove that JB is safe. but Samsung seems to have suppressed the bug on JB kernels.
Click to expand...
Click to collapse
Thank you for your kind help!
I will probably work on my Note this weekend.
Cheers,
vma

[Q] Custom kernel flashing (and bricking)

Hi all,
I have recently unlocked my bootloader and upgraded to 4.4.4 (Build 14.4.A.0.157).
Going thru the General section it seem that during the 4.2.2 to 4.3 era that there is a high chance of bricking the device when there is mismatch of baseband/firmware/kernel.
Is the issue still happening on 4.4.4 and is there anything I need to take note about when flashing custom kernel ?
I'm aware that stock ROMs (or variants) should go with stock kernel variants.
Thank you.

sayatsugu said:
Hi all,
I have recently unlocked my bootloader and upgraded to 4.4.4 (Build 14.4.A.0.157).
Going thru the General section it seem that during the 4.2.2 to 4.3 era that there is a high chance of bricking the device when there is mismatch of baseband/firmware/kernel.
Is the issue still happening on 4.4.4 and is there anything I need to take note about when flashing custom kernel ?
I'm aware that stock ROMs (or variants) should go with stock kernel variants.
Thank you.
Click to expand...
Click to collapse
-Dude if you already installed recovery then first of all take a full stock ROM backup. So if in future there goes something wrong you can flash it later.
-If you don't have recovery, then install it.
-Make sure you always flash ROM that are made for your device.
-DON'T ever flash different kernels to your device. Your pre-installed ROM may misbehave.
-If you want to use the ROM as a daily driver, make sure the ROM is pretty stable.
-Always try to clean flash the ROMs.
By wiping
Cache + Dalvic cache + Data + android secure + System
Dirty flash often lead to bootloops, soft brick etc.
-Hope this would be somewhat helpful for you.

[Q]Flashing the same rom makes the device unusable

Let's say i got a rom that performs amazingly,super fast tab switch,good at multi tasking,25k in benchmark.
Then I want to try a new rom,so I flash the new rom after cleaning my devide,as i should do.
But I don't like it or whatever and I want to return to the old one. But after I flash the old rom the performance is extremely bad,getting random systemui FC ,reboots,etc.
Why is this happening? Right now I'm running out of roms that I can use on my phone,as I cannot go back to the ones that I really liked. Please help
It also happens when a developer posts a new build of a rom. If i got the previous build installed and i flash the new one,the rom is broken again.

darkkfruit said:
Let's say i got a rom that performs amazingly,super fast tab switch,good at multi tasking,25k in benchmark.
Then I want to try a new rom,so I flash the new rom after cleaning my devide,as i should do.
But I don't like it or whatever and I want to return to the old one. But after I flash the old rom the performance is extremely bad,getting random systemui FC ,reboots,etc.
Why is this happening? Right now I'm running out of roms that I can use on my phone,as I cannot go back to the ones that I really liked. Please help
It also happens when a developer posts a new build of a rom. If i got the previous build installed and i flash the new one,the rom is broken again.
Click to expand...
Click to collapse
I use Philz recovery and before flashing a new rom i just simply hit Clean up to install a new rom.
I never faced any of the issue that u mentioned. Try following what i said.
If u are using a lollipop rom then u may face systemui FC ,reboots as there is a bug which is experienced by some users.

I tried every recovery, twrp with full device wipe,cwm with their wipe,and philz with full wipe and the one you mentioned.
The issues happen in every rom,wether it's 3.2,4.4 or 5.x.

darkkfruit said:
I tried every recovery, twrp with full device wipe,cwm with their wipe,and philz with full wipe and the one you mentioned.
The issues happen in every rom,wether it's 3.2,4.4 or 5.x.
Click to expand...
Click to collapse
Return to stock by flashing ftf through flashtool and start from beginning.