Database Develop

[ROM][CWM] Honeycomb 3.1 - Touchwiz UX - WIFI - DEODEXED (Updated 7/22/2011)

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.

[Q] [S.O.S.] A rare MILESTONE brick situation!

Fellow androiders,
I believe I am in a really rare brick situation that no matter how I try, it still does not show any turn around.
[Introduction]
I bought a Korean version Milestone(Moto Qrty, as they put], and I took it to China. Because the original phone did not support sending Chinese text message, plus, too much telco provided apps are making the phone sluggish, I decided to follow my friend advice, to switch to widely available open-sourced Froyo (I wanted the CM).
[Problem]
I thought that the flashing process would not be too difficult and I could handle it by myself. But, it turns out that I have become a victim of an overly simplified version of flashing guide. I don't know what exactly have done wrong, after successfully rooted the phone, I vaguely remember that I have used CM ROM for Droid, instead of CM ROM for Milestone.
And that made my phone a brick. My phone will turn on, but will restart again and again after M logo(So-called M boot loop).
[Background information of the Phone and my PC environment]
Phone Model: A853
Original Bootloader version: A0.20
Original Android System: Froyo
RSD lite version: 5.3.1. (later switched to 4.6 due to the suspicion of RSD bug)
Operating System: Windows 7 64 bit, English
[What I have tried so far]
I have tried to follow many tips on the internet. Tips from Korean websites, from Chinese websites, and from English websites. Basically, these tips will let you flash back to the original ROM by using RSD lite.
But, no matter what I try, it will not fix the boot loop problem.
I've tried to
1) Bring the phone to the original status [did not work.]
- flash the bootloader into A0.20 (the original bootloader) with RSD lite;
(bl_a020_umts_sholesumts_skt_consumer_replacer.sbf)
- flash with original Froyo sbf (following the advice from Korean websites, flashed Clair first, and then flashed Froyo) with RSD lite.
(A853_2.1(Eclair).SBF / A853_2.2.1(Proyo).SBF)
* According to what Koreans say, it would make your phone into the original status, will even remove signs of root.
2) Used many combination of following bootloader and ROMs
- flash the bootloader into 90.78ch
(BL_9078_umts_sholes_GC_HS_Consumer_replacer.sbf)
- flash the bootloader into 90.78
(BL_9078_umts_sholes_HS_Consumer_replacer.sbf)
- GOT221 ROM
(GOT_RTEU_2_2_1FULL.sbf)
- And some other un-name-able ROMs
SGC_U2_03.04.0_USASHLSGCB1B2B5008.0R_PDS06A_HWp2a_1FF.sbf
3) Used many different OpenRecovery Variations
OpenRecovery v1.46
OpenRecovery 3.3
OpenRecovery GOT mod v2.1
4) Restore Nandroid backup which I made right before I made my phone brick.
5) Cleaned data/cache/dalvic as I do every flash, and tried boot without SIM card and SDCard.
[Some discoveries and successes]
- With 90.78ch + GOT2.2.1, it will show "Android" screen, but it will reboot as soon as the phone OS interface show up.
- According to my friend, when he flashed back to the original bootloader A0.20 + original froyo Rom, it showed TelCo Symbol "T" once (which is the booting screen right after M).
[Final Comment]
What I really want to know is that is it the time I give up on it? or is there any value of pursuing other knowledge on bring this phone back?
I really need this phone, and it will take some times to save money to buy another smartphone, I would really really appreciate if you can help me bring this phone back to normal.
Thank you.

some users reported problems with sdcard. try to boot without sdcard, and wipe everything after or before the flash process.
and i don think it's hard bricked...

Sir, I have tried so, somehow, I did not have lucks other had.

roofghost said:
Sir, I have tried so, somehow, I did not have lucks other had.
Click to expand...
Click to collapse
So you've tried flashing different bootloaders, with no success? I always thought flashing another bootloader version different from your own was risky.
If not, you can just try flashing the SBF from here: http://android.doshaska.net/rootable , then installing OpenRecovery, rooting the phone, flashing a custom ROM, etc.

..... my bad

I have the same issue,
in recovery there is message when wiping data/factory reset:
E:Error in CACHE:fota/log
(no space left on device)
I am wondering, if I move CACHE to SD would it help??
Yesterday I have installed original Rom (shols~) and phone booted once to android and when I have rebooted it, there is M bootloop again.
Please help me

skadude66 said:
So you've tried flashing different bootloaders, with no success? I always thought flashing another bootloader version different from your own was risky.
If not, you can just try flashing the SBF from here: android.doshaska.net/rootable , then installing OpenRecovery, rooting the phone, flashing a custom ROM, etc.
Click to expand...
Click to collapse
Thanks, did not work.
I have a feeling that the "doshaska" will know how to solve this. Anyone know how to contact or PM him?
Thanks.

By the way,
in this case, is there anyway can fix the brick via "console" in the OpenRecovery?
Thanks.

So... you have open recovery and can get to the console...
What happens if you copy CM to the updates folder and flash CM?

zeppelinrox said:
So... you have open recovery and can get to the console...
What happens if you copy CM to the updates folder and flash CM?
Click to expand...
Click to collapse
Yes, I can enter OpenRecovery and can get to the console.
And,
sorry about the CM, I think I will have to try that again and let you know then.
Is there any CM ROM you want me to try? (Hopefully with a reliable instruction. If you are busy, you can just leave this part, I will look for myself about the instruction.)
Truly thank you and glad to see new reply under this topic.

Well, use OR's mount as usb function and plug into your computer.
Copy the latest CM7 (I think that's what you want - or any ROM really) to the updates folder.
Wipe all caches
Then apply the update
It should "just work"
I mean, the hardest part is getting into OR lol
I'm surprised that your battery hasn't died yet

zeppelinrox said:
Well, use OR's mount as usb function and plug into your computer.
Copy the latest CM7 (I think that's what you want - or any ROM really) to the updates folder.
Wipe all caches
Then apply the update
It should "just work"
I mean, the hardest part is getting into OR lol
I'm surprised that your battery hasn't died yet
Click to expand...
Click to collapse
Can I install CM7 on Froyo? I thought that was for the Android 2.3.
I have just flashed back to the original bootloader of A0.20 (it was 90.78 as I play around with it.), and flashed the original korean .sbf froyo. Just to follow your suggestion.
I will try to install vulnerable recovery. I think in this way, I can use OpenRecovery again.
About my batter, I purchased a separate battery charger.
I will keep my status updated as soon as I try this out.
Thanks.

same problem and flash so many rom My milestone can't acess sdcard on recovery mode and android os.
Sent from my Milestone using XDA App

guys same problem here, help us

[Q] JellyBam Stucks at bootscreen

Hello friends of the Optimus Black.
[Introduction]
Today i started the first time flashing and android phone. Before i modiefied & flashed firmwares of serveral AVM fritzbox devices to get more features. I use linux as my everyday OS, but installed Win7 because it seems to be easier when working with android devices.
[Problem]
My LG OB stucks at the bootscreen (flying rocket) after i installed the jellybam_p970.NIGHTLY_20121215.zip and gapps-jb-20121011-signed.zip.
I have used theese instructions:
[HOW TO]The Big N00B how-to! and [ROM 4.1.2 - 4.2] JELLYBAM [15/12] [Nightlies] [P970] [PA.AOKP.CM10] [ATOMIC] .
I do know how to handle the SmartFlash Tool to get bricked phone back to live.
One problem is, that iam not shure, if the used nightly rom is corrupt or if i may have used the wrong gaps file. I had to opent this thread, because iam not allowed to post in the developer section (which might be good, if the rom is corrupt)
Another problem is, that it id like to avoid a further unbricking-process with smarttool, just because it takes so much time to:
1. unbrick
2. turn on usb-debug
3. use blackjack to root
4. connect to wifi
5. register at google
6. install rom manager app
7. backup
8. factory reset (wipe)
9. flash
Is it possible to take a shortcut?
Many thanks for your help guys.
mellhen

Hopefully, there is faster way ! After more than 20-30 bricks i get bored with similar process to yours ;p
You just need to use THIS tool to convert your favourite stock firmware to smartflash format and patch it with CWM (recovery). Then, after flashing this converted firmware using SFT your phone will automatically reboot into recovery and you will be able to flash any ROM without rooting, installing cwm etc.
I don't remember exactly, but this tool should only work with v10-v20 firmware, so just download one from HERE from your country (or just with well working baseband) and let's simplify your life !

I have modified one. Many thanks for this tip. I will test it the next time the device bricks.
Do you know if i used the correct gapps file? I tried Version 10.
EDIT
[Problem solved]
After flashing an earlier nightly buld (14th of december) and the CM10 gapp file the OS starts.
Thanks for your help
mellhen

[Q] Installing ICS from CM7.2?

Hi,
Sorry if this seems like a dumb question - A bit confused from reading up all the info on upgrading to ICS on the p990.
Im running a volk custom kernel, and CM 7.2 - OS Version 2.3.7.
Whats the "best" way to upgrade to the new ICS? I tried running the LG software update but it doesnt go too well, fails after it tries to detect phone - even though it detects it initially.
Can I get the release that LG released with my setup?
Please advise.
Thanks!

Same situation here. I'm on official cm7.2 and would like to upgrade to ics. But don't think that useing official lg update tool is so good idea - it might brick your phone. It won't update to ics because you aren't running the official GB rom so lg update tool won't upgrade (correct me if i'm wrong).
Maybe the AIO tool would do the trick.
Anyways, people we need your advice!

LOL, use NVflash ICS rom like TG.

for me the best way is using the toolkit to install new partition, new bootloader and recovery
than boot into recovery and flash the room as usual

Thanks Wakata.
Much appreciated. I have tried downloading the toolkit but its always corrupt.. ill download the 7 zip format.
I take it that I will need to back everything up and wipe everything, install new partition, boot loadder and recovery(CWM??), then flash with the new rom and kernel?

I've also used the All-In-One P990-Toolkit to upgrade to ICS.
You can use 1. to backup your internal SD in case you need it later.
Then hit 4. to change the partition layout and after that 8. to flash the new unlocked bootloader. That's all.

Thanks again
Slight problem - I downloaded the 7z file, and extracted them, but cant seem to run the .cmd file? What am i doing wrong here?

scratch that last question.. for some reason the files are corrupt when i download them.. grrrr.

So I followed the instructions, and suprise suprise, I get an error -
Nvflash started
nvflash configuration file error: file not found
An error occured. Read above lines for details
Help please

Nevermind, I had a fiddle and flashed ics 6.0.xxx.. lets see how it goes. Hopefully I havent bricked it lol

Sorry, problem.
I first tried option 1, then 4, then 8.. after its all done, no errors - I boot the phone, and its stuck on the red LG logo.. I've left it there for around 10-15 mins with no luck? Help!

Haha, actually I figured it out. I did realise I didnt have a ROM! Doh! lol rookie mistake.
I downloaded this rom and kernel(1.4ghz OC) and its running pretty well, no bugs so far(touch wood)

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?