Okay, so ICS is great, and I love it but I really want everything to work. I am getting into developing, and have been learning a lot. I want to make a custom gingerbread rom, and I am on 906. Currently just deodexed and rooted. I want to use this as my base for the rom. I flashed the deodexed rom to my phone because I accidently flashed MAVRom on the non-safe partition (had CWM instead of Safestrap). How would I get the .zip to customize it? The deodexed "rom" is here http://forum.xda-developers.com/showthread.php?t=1554916 but if you aren't using 906 already whats the point, because the system isn't in it, just app and framework. What would be the easiest, or best, way to get this on the road?
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?
Hi, I wanted to flash Slim Bean 4.2.2 ROM but I want to keep the stock samsung apps that came with the phone, is it possible to install them somehow? If not all then could you please tell me what ones I can install?
Thanks in advance,
Nik
nosurlife said:
Hi, I wanted to flash Slim Bean 4.2.2 ROM but I want to keep the stock samsung apps that came with the phone, is it possible to install them somehow? If not all then could you please tell me what ones I can install?
Thanks in advance,
Nik
Click to expand...
Click to collapse
you can extract the apps apk files from your nandroid tar backups of your original samsung rom, then try installing some of them.
make a full nandroid backup of your current stock rom first. make a full nandroid backup of your slim rom before trying to install old stock apps.
some of the apps have no odex component and are compatible with JB 4.2.. those are the ones you can install.
I run stock quick office, for example.
you can find some of the apps in the captivate themes and apps forum.
be careful about installing any system apps that will overwrite a newer version on you current rom, e.g., camera, email, contacts, etc. this is not a good idea.
laughingT said:
you can extract the apps apk files from your nandroid tar backups of your original samsung rom, then try installing some of them.
make a full nandroid backup of your current stock rom first. make a full nandroid backup of your slim rom before trying to install old stock apps.
some of the apps have no odex component and are compatible with JB 4.2.. those are the ones you can install.
I run stock quick office, for example.
you can find some of the apps in the captivate themes and apps forum.
be careful about installing any system apps that will overwrite a newer version on you current rom, e.g., camera, email, contacts, etc. this is not a good idea.
Click to expand...
Click to collapse
Ok thanks. Will have a look.
I flashed a ROM for the One wanting a menu button. Unfortunately, this ROM was not specifically for a Sprint HTC One, but for the other One variants. Now my data connection is broken, and my phone constantly restarts itself, independent of the ROM I'm using ( I've flashed at least 3 ROMs to confirm this). Is there anything I can do to specifically re-flash the radio/prevent the constant restarting?
You should have backed up the ril files on your /system/lib/ first before flashing a different variant.
you should find a couple of files in /system/lib/ named libril* and ends with a .so extension... Now what you need is copy those from a stock sprint ROM and replace the ones on the custom ROMs.
Riyal said:
You should have backed up the ril files on your /system/lib/ first before flashing a different variant.
you should find a couple of files in /system/lib/ named libril* and ends with a .so extension... Now what you need is copy those from a stock sprint ROM and replace the ones on the custom ROMs.
Click to expand...
Click to collapse
I just flashed viperBoy's stock ROMS both odexed and deodexed and got the same thing (still not working). I don't think it is the libril* files. Out of curiosity, what are they for?
Originally Posted by Riyal
You should have backed up the ril files on your /system/lib/ first before flashing a different variant.
you should find a couple of files in /system/lib/ named libril* and ends with a .so extension... Now what you need is copy those from a stock sprint ROM and replace the ones on the custom ROMs.
Click to expand...
Click to collapse
I just flashed viperBoy's stock ROMS both odexed and deodexed and got the same thing (still not working). I don't think it is the libril* files. Out of curiosity, what are they for?
Click to expand...
Click to collapse
Have you had a look in here?
Sprint HTC One forums
(sorry, was going to post a link to the forums root but the c&p failed)
Sent from my HTC One using xda app-developers app
I'm looking for a ZIP flashable stock rom so I can use in multiboot that is not rooted. Every rom I find is pre-rooted....
slekkas said:
I'm looking for a ZIP flashable stock rom so I can use in multiboot that is not rooted. Every rom I find is pre-rooted....
Click to expand...
Click to collapse
stock non rooted, then flash the factory image. besides that, there wont be any unrooted stock roms. most real roms are made with aosp, not stock. since thete is no usable code to build stock. so, they take stock roms, take them apart, and add supersu to it and other stuff. they dont actually "build" stock roms.
simms22 said:
stock non rooted, then flash the factory image. besides that, there wont be any unrooted stock roms. most real roms are made with aosp, not stock. since thete is no usable code to build stock. so, they take stock roms, take them apart, and add supersu to it and other stuff. they dont actually "build" stock roms.
Click to expand...
Click to collapse
Because I need to install as multiboot I can only install a zip file in recovery... I can only use fastboot for the primary rom which I don't want to touch...
To be honest I don't care if the rom is stock or aosp as long as it's not rooted... That's all that matters.
slekkas said:
Because I need to install as multiboot I can only install a zip file in recovery... I can only use fastboot for the primary rom which I don't want to touch...
To be honest I don't care if the rom is stock or aosp as long as it's not rooted... That's all that matters.
Click to expand...
Click to collapse
well, there are many aosp roms, the majority of them are not rooted until you flash the supersu file as well. terminus is my favorite one. one question, why do you need a non rooted rom? if its for a business or for an app, you will appear rooted until you flash the factory image.
simms22 said:
well, there are many aosp roms, the majority of them are not rooted until you flash the supersu file as well. terminus is my favorite one. one question, why do you need a non rooted rom? if its for a business or for an app, you will appear rooted until you flash the factory image.
Click to expand...
Click to collapse
My satellite provider has an app but I need to be unrooted in order to run it. I thought the best way would be to install a second rom that is unrooted and use it for this. Thank you for taking an interest to help BTW.
So you are telling me even if I install this terminus rom and I don't root I won't be able to use the app?
slekkas said:
My satellite provider has an app but I need to be unrooted in order to run it. I thought the best way would be to install a second rom that is unrooted and use it for this. Thank you for taking an interest to help BTW.
So you are telling me even if I install this terminus rom and I don't root I won't be able to use the app?
Click to expand...
Click to collapse
since you are on multiboot, i honestly dont know. i do know that many have to unroot to use certain apps, so the get rid if root. but the apps usually think they are still rooted, until they flash the factory image. anyways, good luck!
You could try using a root cloak.
Problem already resolved.
http://forum.xda-developers.com/showthread.php?t=3164939