Database Develop

[Q] Camera error after GB update

Hi
I've upgraded to 2.3.3 and my camera doesnt work anymore. The screen comes black for a few seconds and then the message "Camera error. Cannot connect to camera" appears. The flashlight is also doesnt work. I have some MoDaCo firmware HTC Sense before, as I remember...
Help me to fix it, please.
Thanks

Flash newer radio.

Jack_R1 said:
Flash newer radio.
Click to expand...
Click to collapse
Could you tell me how to do it, pls? What is the last version of radio? How to check it?

Settings / About / Baseband
If the version is 4.06 / 5.08 / 5.12 (the version is in the middle of the long string there) - then there's some other problem in the system. If the version is 4.02 or 4.04 - then you need to go to Developers forum, open any Gingerbread ROM thread, and see the instructions for flashing Radio. Or look at my signature.

Jack_R1 said:
Settings / About / Baseband
If the version is 4.06 / 5.08 / 5.12 (the version is in the middle of the long string there) - then there's some other problem in the system. If the version is 4.02 or 4.04 - then you need to go to Developers forum, open any Gingerbread ROM thread, and see the instructions for flashing Radio. Or look at my signature.
Click to expand...
Click to collapse
The Baseband Version is 32.41.00.32U_5.08.00.04
What I'm thinking is could it be the problem because my Nexus had non original firmware before the GB update, and maybe I didnt make some important thing which blocking my camera now? Maybe I need to re-flash the radio with some original image? I'm totally NOOB in all these things...

Your radio is 5.08 - which means it's updated and the problem is elsewhere.
If you didn't upgrade to Gingerbread from a clean FRG83G build, but from some other build - you'll need to reflash the ROM. You can do it if you have unlocked bootloader. Read Wiki, it has the guide for installing custom ROMs - execute it, and use Gingerbread stock build from one of the threads in Development forum.

Jack_R1 said:
Your radio is 5.08 - which means it's updated and the problem is elsewhere.
If you didn't upgrade to Gingerbread from a clean FRG83G build, but from some other build - you'll need to reflash the ROM. You can do it if you have unlocked bootloader. Read Wiki, it has the guide for installing custom ROMs - execute it, and use Gingerbread stock build from one of the threads in Development forum.
Click to expand...
Click to collapse
Thanks for your advices. Just upgraded the radio to 5.12 via fastboot. The camera still not work Will try to flash to original state...

ok, i've tried to rollback to original FRG83, se-flashed boot, recovery, but no luck - camera didnt started. Hovewer, i tried the flashlight torch and it started to work (it didn't like a camera before), so I'm sure now the camera issue is the software now - not a hardware.
Does anybody have some advices?

P0MkA said:
ok, i've tried to rollback to original FRG83, se-flashed boot, recovery, but no luck - camera didnt started. Hovewer, i tried the flashlight torch and it started to work (it didn't like a camera before), so I'm sure now the camera issue is the software now - not a hardware.
Does anybody have some advices?
Click to expand...
Click to collapse
How did you flash frg83? via passimg or you flashed rooted rom from dev section? If you didn't use passimg method you should try wiping everything (cache, dalvik, factory reset) from the recovery.
BTW, if you have custom recovery you should be able to restore nandroid backup (which I assume you did;P ) and see if there is this problem too.
Cheers!

k_myk said:
How did you flash frg83? via passimg or you flashed rooted rom from dev section? If you didn't use passimg method you should try wiping everything (cache, dalvik, factory reset) from the recovery.
BTW, if you have custom recovery you should be able to restore nandroid backup (which I assume you did;P ) and see if there is this problem too.
Cheers!
Click to expand...
Click to collapse
i've flashed frg83 using fastboot. And updated to 2.3.3 via recovery (RA-passion-v2.2.1). And yes, I wiped everything using the recovery. Unfortunately, I do not know what is nandroid backup, so I didnt do it
Hope there is a way to get my camera back to work... Could you tell me what to do, step by step, to make my Nexus fully functional with the 2.3.3 firmware, please!

P0MkA said:
i've flashed frg83 using fastboot. And updated to 2.3.3 via recovery (RA-passion-v2.2.1). And yes, I wiped everything using the recovery. Unfortunately, I do not know what is nandroid backup, so I didnt do it
Hope there is a way to get my camera back to work... Could you tell me what to do, step by step, to make my Nexus fully functional with the 2.3.3 firmware, please!
Click to expand...
Click to collapse
I'd love to, but unfortunately I don't know what causes this problem at the moment I think it wouldn't hurt to try loging what is going on when you open camera.apk. Try adb logcat from your pc or install "alogcat" from market, start camera app and paste here the log file.
Lesson for future always do nandroid backup You can do this from recovery, it will do phone's memory image Then you can always revert back to what you had before flashing new rom

k_myk said:
I'd love to, but unfortunately I don't know what causes this problem at the moment I think it wouldn't hurt to try loging what is going on when you open camera.apk. Try adb logcat from your pc or install "alogcat" from market, start camera app and paste here the log file.
Lesson for future always do nandroid backup You can do this from recovery, it will do phone's memory image Then you can always revert back to what you had before flashing new rom
Click to expand...
Click to collapse
Yeah... backuping is a cool thing.... It is just my first experience with the Android phone... Maybe will find some kind of solution for this...

Well... Problem stays... However I've found few interesting things. As I've mentioned above, after the 2.3.3 update the camera and flashlight doesnt work enymore. But I've installed Z-DeviceTest and found that after the reboot this app (which provides the hardware test) sees the camera and flashlight! But, unfirtunately, doesnt able to test it. Moreover, if to start some torchlight widget directly after the reboot, the flashlight works!!! But it is not after the camera start... So, maybe someone will find this information useful.

@Pomka
have you found the Satu Solution yet ?
mmm. i guess you borrow from somebody the nandroid back up and restore it...
then u will know whether it is a hardware issue or Software Issue.
Logic ?

sevensaints said:
@Pomka
have you found the Satu Solution yet ?
mmm. i guess you borrow from somebody the nandroid back up and restore it...
then u will know whether it is a hardware issue or Software Issue.
Logic ?
Click to expand...
Click to collapse
Stupid actually. Its stay the same, not working....
found the solution!
http://forum.xda-developers.com/showthread.php?t=717870&highlight=frf91
You have go go back to stock ROM.....then camera Happy Trigger Finger!
yeah...
1. Go back to stock through HBOOT
2. Flash back ur fav ROM - mine-MIUI AU
pls click thanks

[MOD][CWM][Bell][Gobstopper] Stock 2.2.2 for Bell Updated 10/01/2011

Disclaimer: You may brick your phone. NOT for AT&T
​
Reminder: Make sure your phone has enough battery charge to flash this, it's larger than normal.​Hi,
Here is a huge CWM zip that restores your Bell phone to stock 2.2.2. I have tested it on my phone several times and it worked perfectly, there is still the chance that something may go wrong, but I am feeling confident in it.
What this does is similar to my app or scripts, it puts my backup of Bell's 2.2.2 partitions on your phone, but instead of using dd, it uses tenfar's CWM and flash_image. Some partitions are HUGE, and take a while, your phone is not locked up.
This has been updated to include the Bell bootloader for 2.2.2 and the radio for 2.2.2.
EDIT: This has been updated again to ram fix the boot and recovery partitions if there is a ram problem.
It writes to partitions 1, 2, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 17. 3 is left out because it's your pds partition, and data and cache have no relevant content. You must factory reset after using this to clear those. So, that's your boot, recovery, system, webtop, cdrom, preinstall, and several other partitions. This is to get back to stock Bell 2.2.2, it's not just a boot/system replacement, if that is a fruitcake, this is a gobstopper.
Please note: This restores your Bell phone to stock condition, that means you won't be unlocked, CWM will be overwritten with the stock recovery. It will be just like you bought it. If you want to keep flashing things in CWM with the unlocked bootloader, then immediately after flashing the stock zip, flash the unlock and fix zip. If you don't then you will have to reflash an unlocked bootloader, and reflash CWM recovery, which is time consuming any annoying, it doesn't mean you will be permanently locked again. I had to spell that out to the folks that don't really understand this stuff. At all.
If you want root after installing this, just install Superuser.apk from the market.
Bell_FR_2.2.2.zip (Froyo not France)
(md5 e431b4cc3ba7e3a27b6aad6982a31066)
Cheers!​Oh, I forgot to mention, this is not quite stock, there are su and sudo binaries in /system/bin. Just install Superuser.apk to be rooted. they haven't been a problem for doing an OTA yet, but they are easy enough to remove if it comes up.
unlocked-fixed-Bell-2.2.2.zip
Mirror: unlocked-fixed-Bell-2.2.2.zip​

Damn, nice work as always, man! This should come in handy for lots of us Bell Atrix users that feel left out. Lots will appreciate this!

When you say without amnesia are you talking about the bootstrap or are you talking about a user who is using the bell_ihop and then installs cwm and then reboots and looses recovery?
So a 2.3.4 bootloader and radio will work find booting a 2.2.2 bell ?

Will you eventually be able to compile a zip for Bell gingerbread?

IrshaadH said:
Will you eventually be able to compile a zip for Bell gingerbread?
Click to expand...
Click to collapse
the problem would be hosting it, not sure how he would be able to do that.
akurit said:
When you say without amnesia are you talking about the bootstrap or are you talking about a user who is using the bell_ihop and then installs cwm and then reboots and looses recovery?
So a 2.3.4 bootloader and radio will work find booting a 2.2.2 bell ?
Click to expand...
Click to collapse
keeping in mind that this is only for the recovery with unlocked devices, what he means is that the CWM recovery that tenfar put out has a problem with int'l phones (pretty sure it's all int'l) where IN recovery (not just the normal ROM, like the problem we had before) only 300 and some mb of RAM is available. since this zip is over 300mb, it can't all load into your RAM properly with normal recovery.
NFH found this bug, and patched recovery for us so as to fix the RAM problem. the two files attached are fixed recoveries for the two separate MBR versions of int'l devices.
to find what version you should use, connect to phone via ADB and then
Code:
adb shell
su
cat /proc/cmdline
and then search for the part of the output where it says "tegrapart=mbr:" and read that. it should have either "1100" or "d00" somewhere in it, use the CWM zip attached that has your respective output.
hope that clears up your question, if you have any further ask them in here.

IrshaadH said:
Will you eventually be able to compile a zip for Bell gingerbread?
Click to expand...
Click to collapse
Hi,
I believe y2whisper may be working on something like that. The point of getting back to stock 2.2.2 is to be able to apply the final OTA for Bell GB. Certainly something similar can be done for any firmware you want to flash.
Cheers!

i flashed the d00 and I do maintain unlock however no cwm just stock recovery with no menus.
tried it again and it work
but seems like i have to fastboot flash it each time i want to use recovery

akurit said:
i flashed the d00 and I do maintain unlock however no cwm just stock recovery with no menus.
tried it again and it work
but seems like i have to fastboot flash it each time i want to use recovery
Click to expand...
Click to collapse
I know what you are talking about, but I got that with a stock bootloader.
If you are going to be using CWM recovery with this 2.2.2, then flash the boot file for d00 as well, it gives you the ram fix and for some reason it doesn't cause that issue.
Cheers!
Here is an international CWM recovery, it detects the 1100 vs d00 tegraparts and installs the right recovery for it.
CWM_INT_Recovery.zip
(Just use it with whatever CWM recovery you are using now, it will update it with the ram fixed one.)

NFHimself said:
I know what you are talking about, but I got that with a stock bootloader.
If you are going to be using CWM recovery with this 2.2.2, then flash the boot file for d00 as well, it gives you the ram fix and for some reason it doesn't cause that issue.
Cheers!
Here is an international CWM recovery, it detects the 1100 vs d00 tegraparts and installs the right recovery for it.
CWM_INT_Recovery.zip
(Just use it with whatever CWM recovery you are using now, it will update it with the ram fixed one.)
Click to expand...
Click to collapse
ohhh, that's a nicely scripted installer you got there. i think that would be quite handy for int'l users trying to flash custom kernels, is it possible to apply that script to select the correct boot.img out of two for the right tegrapart? if that's possible i think you should hit faux/edgan up with that script and let them apply it to their int'l kernels so users can just use on CWM to install it.

raybond25 said:
ohhh, that's a nicely scripted installer you got there. i think that would be quite handy for int'l users trying to flash custom kernels, is it possible to apply that script to select the correct boot.img out of two for the right tegrapart? if that's possible i think you should hit faux/edgan up with that script and let them apply it to their int'l kernels so users can just use on CWM to install it.
Click to expand...
Click to collapse
Hi,
Sure, it's just replacing the word recovery with boot and having the right boot images in the file.
Cheers!

yes its zipping now. off to bed but tomorrow I will back up my stuff and attempt to flash to see if it works.
@akurit
I forget off the top of my head but there is a file that you just have to delete to prevent that. the file just flashes the old recovery on every reboot. get rid of that and you will be fine.

Awesome work! This makes it much easier to get back to 2.2.2

Its installing now!
now at some point the install stopped and I think I saw it say status 0 and then recovery rebooted. so I am not sure what happened there.
ive rebooted with no problems. and its uploading now. if someone is willing to test this out (a bit difficult for me since I am already on 2.3.4) let me know. and will send you the link. would like to see a proper install before i share it with the masses.

This is why hehee
tenfar said:
......
Please Remove install_recovery.sh located in your /system/etc/ ,so that the recovery will not be overwrite to stock one.........
Click to expand...
Click to collapse
now it remains unlocked and I have recovery even if i reboot... but the ram issue still exists

y2whisper said:
Its installing now!
now at some point the install stopped and I think I saw it say status 0 and then recovery rebooted. so I am not sure what happened there.
ive rebooted with no problems. and its uploading now. if someone is willing to test this out (a bit difficult for me since I am already on 2.3.4) let me know. and will send you the link. would like to see a proper install before i share it with the masses.
Click to expand...
Click to collapse
i could test it for you, i should be able to tell if it works alright or not, since i'm starting from an AT&T build of 2.3.4. would i have to head back to stock Bell using Gobstopper before i use your package too? i got a whole buncha time on my hands this week, so i should be able to test it however you want.

anyone try flashing the bootloader and radio?

kevnb said:
anyone try flashing the bootloader and radio?
Click to expand...
Click to collapse
Hi,
I have tested it, no problems, but went back to IHOP and the ram-fixed bootloader for 2.2.2 in the OP so recovery will work.
Also, the file install_recovery.sh located in your /system/etc/ doesn't exist in the Gobstopper, so that isn't causing recovery to be generated by patching boot.
Cheers!

So its when flashing the webtop that the install stops with the error code. when i boot up all is ok but a reboot later and recovery is gone (as in you select it and it just boots into android). reflashing cwm recovery fixes that.
I have tried swapping the webtop files to no avail. going to keep trying. any ideas are welcome

y2whisper said:
So its when flashing the webtop that the install stops with the error code. when i boot up all is ok but a reboot later and recovery is gone (as in you select it and it just boots into android). reflashing cwm recovery fixes that.
I have tried swapping the webtop files to no avail. going to keep trying. any ideas are welcome
Click to expand...
Click to collapse
Hi,
What recovery are you using, if it's not ram fixed you are going to run into situations where you don't have enough space to flash it.
Cheers!

ahhhh.
you know i was wondering if that was it. I even repackaged the recovery thinking it would be the cause.
I don't believe I was ram fixed at the time of the backup. So I am thinking either, have custom recovery flashed in that spot, or change the order to where recovery gets flashed after.

Bricked Tab???? HELP

HELP! I am so scared...somebody help me!
I tried to installed the Overcome kernel but didn't like it, as each time I boot up, that voice comes up.
And plus, a few of my original apps was lost (including Market). So I thought i'd install with Odin again the:
CF-Root-TAB7_XX_OXA_JQ1-v3.3-CWM3RFS.tar
And now, when i switch on the tablet, it'll boot with the animation and sound, but then a blank screen.
I can manage to boot into ClockworkMod recovery. Can i be saved? Please somebody help me!
Thanks

geoyakult said:
HELP! I am so scared...somebody help me!
I tried to installed the Overcome kernel but didn't like it, as each time I boot up, that voice comes up.
And plus, a few of my original apps was lost (including Market). So I thought i'd install with Odin again the:
CF-Root-TAB7_XX_OXA_JQ1-v3.3-CWM3RFS.tar
And now, when i switch on the tablet, it'll boot with the animation and sound, but then a blank screen.
I can manage to boot into ClockworkMod recovery. Can i be saved? Please somebody help me!
Thanks
Click to expand...
Click to collapse
If you can boot into CWM, then you should easily be able to get into Download mode as well. You can go back to the stock image for your Tab, or try and reflash a different rom via CWM... sounds like just a bad flash for a soft brick..

pvtjoker42 said:
If you can boot into CWM, then you should easily be able to get into Download mode as well. You can go back to the stock image for your Tab, or try and reflash a different rom via CWM... sounds like just a bad flash for a soft brick..
Click to expand...
Click to collapse
Hi there, thanks for reply back to me.
I've managed to actually get it going again, by reflashing to the Overcome kernel.
However, some apps has disappeared and also the market.
Anyways, i wish to revert the whole thing back to stock, kernel and firmware. Is there a way I can do this via Kies?
Let me know what information regarding my tab you need. I believe it is the CPW (GSM) UK version.
cheers

geoyakult said:
HELP! I am so scared...somebody help me!
I tried to installed the Overcome kernel but didn't like it, as each time I boot up, that voice comes up.
And plus, a few of my original apps was lost (including Market). So I thought i'd install with Odin again the:
CF-Root-TAB7_XX_OXA_JQ1-v3.3-CWM3RFS.tar
And now, when i switch on the tablet, it'll boot with the animation and sound, but then a blank screen.
I can manage to boot into ClockworkMod recovery. Can i be saved? Please somebody help me!
Thanks
Click to expand...
Click to collapse
LOL. FYI, your Tab is not haunted. That voice that you refer to, is basically an indicator that the file-system on the Tab is being converted from RFS to EXT4 (what some would affectionately refer to as the lag-fix). You should have left it to continue. That's the reason we ask people to let it finish booting before doing anything else. As always, when it comes to flashing a new firmware/kernel, it's always better to read up and know what to expect.
Anyway, by the looks of it, you might have a corrupted file-system, since you keep shutting it down mid-conversion. That's the reason "the voice" keeps coming back. If you'd allowed it to complete, it should not have returned.
Secondly, flashing the Overcome Kernel alone will NOT remove the Market application. If you were already on the CF-Root kernel, it might remove the CF-Root specific applications like the CwM "app" (and not the recovery functionality, mind you...) and the Tweaks app as these apps were created by ChainFire specifically for his kernel.
Best advice would be to re-flash a stock firmware first, to get your Tab into a clean system. From there, you can continue to to install the kernel of your choice (like ChainFire or Kouxudaxi's fine kernels as well.... these kernels, if I'm not mistaken, do not do automatic EXT4 conversions)
If you're unsure of how to do this, refer to the guide in teamovercome.net and it'll guide you in basic re-stocking (but using our Stock safe package which will provide you with the Gingerbread-based JQ1 firmware).

LOL, +100000000000000000000000 thepitbull...

thepittbull said:
LOL. FYI, your Tab is not haunted. That voice that you refer to, is basically an indicator that the file-system on the Tab is being converted from RFS to EXT4 (what some would affectionately refer to as the lag-fix). You should have left it to continue. That's the reason we ask people to let it finish booting before doing anything else. As always, when it comes to flashing a new firmware/kernel, it's always better to read up and know what to expect.
Anyway, by the looks of it, you might have a corrupted file-system, since you keep shutting it down mid-conversion. That's the reason "the voice" keeps coming back. If you'd allowed it to complete, it should not have returned.
Secondly, flashing the Overcome Kernel alone will NOT remove the Market application. If you were already on the CF-Root kernel, it might remove the CF-Root specific applications like the CwM "app" (and not the recovery functionality, mind you...) and the Tweaks app as these apps were created by ChainFire specifically for his kernel.
Best advice would be to re-flash a stock firmware first, to get your Tab into a clean system. From there, you can continue to to install the kernel of your choice (like ChainFire or Kouxudaxi's fine kernels as well.... these kernels, if I'm not mistaken, do not do automatic EXT4 conversions)
If you're unsure of how to do this, refer to the guide in teamovercome.net and it'll guide you in basic re-stocking (but using our Stock safe package which will provide you with the Gingerbread-based JQ1 firmware).
Click to expand...
Click to collapse
Hi there,
Thank you so much for your time in replying - I've managed to install what i believe is stock Gingerbread from Samsfirmware. So everything looks back to normal... tho i have posted another Question, with all my firmware details so I can be reassured I am back to stock.
So sorry, I panicked so badly last night..ha!

You have also special thread with many scenarios how to fix your tablet if anything goes wrong.
It helped me yesterday to revive my Galaxy Tab. Just suddenly it started freezing and restarting, after 3 weeks working perfectly on Overcome. Nothing changed, or updated, nothing installed for days, and all what was ever installed are programs I already have on my two other Android phones, it simply froze in the middle of work. Wipe didn't work, changing file system didn't work, etc...
Read the thread: http://forum.xda-developers.com/showthread.php?t=1133590
Very good material.

nidza said:
You have also special thread with many scenarios how to fix your tablet if anything goes wrong.
It helped me yesterday to revive my Galaxy Tab. Just suddenly it started freezing and restarting, after 3 weeks working perfectly on Overcome. Nothing changed, or updated, nothing installed for days, and all what was ever installed are programs I already have on my two other Android phones, it simply froze in the middle of work. Wipe didn't work, changing file system didn't work, etc...
Read the thread: http://forum.xda-developers.com/showthread.php?t=1133590
Very good material.
Click to expand...
Click to collapse
Im very glad that the guide helps many ppl
@the Op : do me a fav and flash safe
Sent from my GT-P1000 using Tapatalk

k0sh said:
Im very glad that the guide helps many ppl
@the Op : do me a fav and flash safe
Sent from my GT-P1000 using Tapatalk
Click to expand...
Click to collapse
Yup, in future i will be more careful when flashing, so glad that my tablet is back to normal (albeit with the Italian release of GB ) but everything works fine.
Will do more reading on the forums before undertaking any more flashing, make sure i know what i am doing and which Rom is best for me to use.
Cheers
Sent from my GT-P1000 using XDA App

geoyakult said:
Yup, in future i will be more careful when flashing, so glad that my tablet is back to normal (albeit with the Italian release of GB ) but everything works fine.
Will do more reading on the forums before undertaking any more flashing, make sure i know what i am doing and which Rom is best for me to use.
Cheers
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
best reaction i never read

P990 stock rom zip

Hello pls where i can get P990 stock rom zip ( czech version ) in zip format... for me is better instalation.
Please answer fast
I have backup stock rom but if i flash it .... in boot screen freeze and after 5 sec restart phone

You'll first need to convert your file system to EXT3 first. CM is EXT4 and stock is EXT3. Flash this zip in recovery: http://android.modaco.com/topic/336...3-for-converting-your-device-er-back-to-ext3/
So you'll need to do this in recovery:
1. Wipe everything
2. Flash the BackToExt3 zip
3. Restore stock rom backup.
This should work.

Nice big thx this is easy and very fast

62.53 nicaoin
any idea, where to get stock rom for baltic states? Can't find my stock rom anymore..

janezzx said:
any idea, where to get stock rom for baltic states? Can't find my stock rom anymore..
Click to expand...
Click to collapse
http://lg-phone-firmware.com/index.php?id_mod=3 has made an index for lg kdz updates.
You can flash it with UpTestEX.exe or extract with LGExtract.exe then flash img with CWM recovery.

i made one:
http://forum.xda-developers.com/showthread.php?t=1617458

trapacska said:
i made one:
http://forum.xda-developers.com/showthread.php?t=1617458
Click to expand...
Click to collapse
trapacska, you are a legend! For months I have been troubled with my CM9 flashed phone, wishing I still had video etc, and couldn't get my phone recognised by any pc i attached it to. Your zip file has fixed all my problems in about 3 minutes! Thanks a million!

erm, i'm from Malaysia, which Rom should i use?

trapacska said:
i made one:
http://forum.xda-developers.com/showthread.php?t=1617458
Click to expand...
Click to collapse
I read this post above and cant go anywhere further because the silly rules do not allow noobsters to ask noobster questions ????
heres my problem,
I have P990 that came with froyo
the thing was working perfectly apart from front camera in Skype and silly old me, not being able to ask novice questions here (because you are not allowed) somehow managed to install the cryogen 9 naively thinking that this will fix the only problem I ever had. And then the world of unstability, locked and frozen screens, freezing, restarting, random uninstaling of apps, cameras not working, video freezing, music (what music??) not available and not even starting etc started to be my daily dose of my randomly properly working p990 phone.
Is there anyone kind enough to explain how to do stock rom as per above post install on top of my big mistake .
I have an unstable, unreliable (rooted ) P990 that is currently (very randomly) running cryogen 9 , I downloaded the 2 part files from trapacska's post (thanks for thinking of us mortals), I have 2 laptops , one with windows XP , one with windows 7 64 bit, a usb cable to connect laptop to the phone and I will to do anything to return my phone to some normality .
Please take me step by step or show me links how to do it and what other programs do I need in order to make my phone work as it is supposed to work.
Please understand that I do not understand what all this bellow means, and would really appreciate if anyone could explain or point to places where these things are explained ( please omit the first point, I found how to root elsewhere):
THIS IS 100% FACTORIAL STOCK:
-you have to root
-wipe data and cache NOW NOT NEEDED(built in format /system /data /cache)
-100% factorial stock kernel included
-baseband and recovery will not be changed
-if you have bootloop, try to flash backtoext3 first

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?