Hi everyone, I need help over here as I'm stuck in the process of rooting & upgrading my Xperia TX (LT29i).
I have successfully downgraded the firmware & rooted it. However, I can't seem to find a stock ROM for Xperia TX (LT29i) 7.0.A.3.197 firmware. I just gone through all the hard ways to create a stock ROM myself & successfully flashed it. Perhaps bcuz of the improper build, my WiFi can't be turned on & there might be other problems coming up later.
Now I am also worrying that would it cause any prob to my phone. I followed this guide to create the ROM.
http://forum.xda-developers.com/show....php?t=1931189
& I took the META-INF folder from this custom ROM.
http://forum.xda-developers.com/show....php?t=2040989
Plz kindly help that if there's any resource to the stock ROM or any way to fix this, as well as have a look if there is any side effect from flashing that ROM. Many thanks! ><
You could try the repair phone option in SUS, with will reflash the stock firmware on your phone
One way to fix your problem is to copy /system/lib/modules/prima/prima_wlan.ko to /system/lib/modules/wlan.ko. An issue that I found with this solution, though, is the MAC address I got after copying the .ko file is different from what it was in stock. I can't figure out why. But regardless, your wireless LAN should work after you copy the file.
Montoyatok said:
You could try the repair phone option in SUS, with will reflash the stock firmware on your phone
Click to expand...
Click to collapse
Thx, I'm aware of this option. It's just that I want to know if what I did would create any prob to my phone in future, as well as if there's any stock ROM available on the forum. =)
chibikit said:
One way to fix your problem is to copy /system/lib/modules/prima/prima_wlan.ko to /system/lib/modules/wlan.ko. An issue that I found with this solution, though, is the MAC address I got after copying the .ko file is different from what it was in stock. I can't figure out why. But regardless, your wireless LAN should work after you copy the file.
Click to expand...
Click to collapse
Alright, will try. Thx. =) Do I've to keep the original file at the original location? Btw, is the way I'm building a ROM a proper way to do it? Do u know is there any ready-built stock ROM available?
Look in the very first thread of this section to find an index of every ROM and ftf
Sent from my LT30p xda premium app.
How do I customise the signature on xda premium app?
SCC2002 said:
Thx, I'm aware of this option. It's just that I want to know if what I did would create any prob to my phone in future, as well as if there's any stock ROM available on the forum. =)
Click to expand...
Click to collapse
Links to stock ROM FTFs are available in gregbradley's FAQ here under FTFs. You will need Flashtool to flash these to your phone.
Available stock-based TX ROMs are gregbradley's Assaye and travis82's 240 DPI stock ROM. I haven't tried either since I'm just fiddling about on my own, so I can't tell you how well those work, but Assaye is a good reference if you're trying to build your own stock-based ROM.
Alright, will try. Thx. =) Do I've to keep the original file at the original location?
Click to expand...
Click to collapse
I didn't do anything else except copy the file, so the original prima_wlan.ko is where I found it on my ROM.
Also, I've been watching this thread on similar problems with the Xperia V and a solution has been found. I'm planning on trying it out on my TX some time this week to see if it will solve my MAC address woes.
Btw, is the way I'm building a ROM a proper way to do it?
Click to expand...
Click to collapse
The thread you linked to are instructions on building ROMs for older Xperia phones. Steps 1 - 4 don't need to change for our phones, but the TX uses a different partition scheme (or something), and this means step 5 needs to be different since our system.sin's contents are actually in ext4 format, not YAFFS. A typical Windows installation will not be able to handle the file contents. You can use mounting utilities to read the file and copy them over to your Windows hard drive, but all symbolic file links will basically be destroyed.
Currently, I'm using dsixda's Android Kitchen to build my own stock-based ROM. It's really just a collection of utilities that allows me to make all the necessary file changes and edits that I want before generating a ROM .zip file that can be flashed in CWM. This really needs Linux to work, which is a plus because the file system used by Linux is usually ext4 by default, making it easy to work with the contents of the decrypted system.sin.
If you're planning to build a simple custom ROM, I suggest you read up on how to use dsixda's Kitchen, but keep the following in mind:
- the Kitchen works with a system.img file, which is really just the system.ext4 you get from decrypting system.sin
- the Kitchen will complain about not having a boot.img to work with. Ignore it; I don't think you're building a ROM with a custom kernel, so you don't have to worry about it.
- the default contents of META-INF that the Kitchen generates does not work with CWM for locked bootloaders on the TX. I don't think it works with unlocked bootloaders either. The solution is to stea-... err, borrow the update binary and updater-script from a working ROM zip and edit it for use on yours.
Also, read gregbradley's Assaye ROM thread and TiMiN8R's stock and deodexed ROM thread. They are using dsixda's Kitchen as well, and you can learn a lot about fiddling with stock ROMs from reading about the problems they encountered and how they fixed them.
Related
Hi Guys,
Seeking some help here, cause it must be easy. Surely there must be a way to dump the Stock ROM from the phone? (NOT backup)
I want to either:
- dump the stock ROM (i.e. not backup the ROM or such, just simply dump the stock from the hidden partition), or
- grab a ROM while it is being flashed by SEUS to the X1 (so i can make some updates and then flash that ).
I know I can use Pavel's ROMS here, but the one being flashed to my phone is 161MB, while the same one on Pavel's is 212MB. http://blog.fastgsm.com/sonyericsson/r3a-software-for-sony-ericsson-xperia-x1/
When the phone is being updated, there is a file copied to Program Files\SEUS\db\.. which is the same size as stated in SEUS (161MB), but this has no extension, and all the extensions I've tried (nbh (using kitchen tools tells me it's not valid), zip, rar) don't work. Maybe there's something there??
The tutorials and stickys, while excellent, either require a downloaded ROM already (backing up the ROM http://forum.xda-developers.com/showthread.php?t=462926) or don't quite cover what I need.
The question is how??
- SEUS version 2.9.6.12
Cheers...
I am looking for the same thing m8, i want to extract the new SPL 0.78 out of the update. But can't get in the file that's downloaded by seus . Maybe it's downloaded as binary data or encrypted in some kind of way
so i have a custom build over in the vogue forums but i would love to get it working on the hero, it is basically just a heavily customized version of AOSP so i took asop mod as a base and added my custom changes to it (that part i got) i then signed it and attempted to flash it to my hero, it got about half way through the installation and said i was missing and update script so if anybody can give me advice that would be awesome i would really love to get this build running on my daily phone.
thoughtlesskyle said:
so i have a custom build over in the vogue forums but i would love to get it working on the hero, it is basically just a heavily customized version of AOSP so i took asop mod as a base and added my custom changes to it (that part i got) i then signed it and attempted to flash it to my hero, it got about half way through the installation and said i was missing and update script so if anybody can give me advice that would be awesome i would really love to get this build running on my daily phone.
Click to expand...
Click to collapse
When you unzipped the ROM you should have seen some folders and a boot.img. There are some folders in the boot.img that need to be replaced along with the kernel for our phone. So just using a boot.img from another ROM might be the easiest. Otherwise you will have to unpack it, switch out files and repack with a kernel for our phone.
The update script is found in /META-INF/com/google/android/. You should be able to pull it from another ROM.
unCoRrUpTeD said:
When you unzipped the ROM you should have seen some folders and a boot.img. There are some folders in the boot.img that need to be replaced along with the kernel for our phone. So just using a boot.img from another ROM might be the easiest. Otherwise you will have to unpack it, switch out files and repack with a kernel for our phone.
The update script is found in /META-INF/com/google/android/. You should be able to pull it from another ROM.
Click to expand...
Click to collapse
ah i deleted the meta-inf folder thats probably what cause the problem
also am i able to have a folder that keeps things in /data like i am on the vogue or does it all have to be in the system?
I wanted to apply one of the battery mods to my captivate i896 (running the stock rogers rom), specifically version E.
I tried using the UOT Kitchen website at first but that failed. So then I tried to do it myself, but that also fails. Something seems to be going wrong when I try to apply the update.zip I have and I see no error output to help me trace it. Here's what I've been doing (when I tried it from scratch):
So I downloaded the related zip file from the second post, "scbm_E_grey_number.zip".
I then used "Android Theming and Tweaking" to get the framework file from my phone, and decompile it. I replaced the corresponding .png and .xml files from "scbm_E_grey_number.zip" to the appropriate folders in the decompiled folder from the ATT software. Then using the same software, I compile the framework apk again.
I then use the update.zip creator. I create a "framework" folder in the "placehere" folder for the update creator. Inside the framework folder I placed my new APK. I then ran the update creator to generate a new script, which copies from "framework" to "framework" on SYSTEM. Finally, I have it create the update.zip for me.
Everything is fine up to this point. I place the update.zip on my SD card, boot my phone into recovery, try to flash it...I get the following:
Code:
-- Install from sdcard...
Finding update package...
Opening update package...
Installing update...
Installation aborted.
I've tried this a few times with no luck
I'd like to figure this out in the hopes that I can do some mods of my own in the future, so any help would be great Thanks!
If you ever figuered this out please let me know too, i am having the same issue. I am using a Captive that I just restored with Odin. I unroot it and remove the applock on it. I get the same installation aborted issue. I then tried to install it with ClockWork recovery... that just crashed my phone and I had to reinstall again. So if anyone know what the problem is please chime in.
Can't theme the stock rom. It has to be a deodexed rom, which is essentially all of the custom ones. Also, don't flash mods through the stock 2e recovery, you want to do it through CWM.
TheEscapist said:
Can't theme the stock rom. It has to be a deodexed rom, which is essentially all of the custom ones. Also, don't flash mods through the stock 2e recovery, you want to do it through CWM.
Click to expand...
Click to collapse
Hmm I see, thanks for the info... there was no odex file for that particular file, so I thought I'd be lucky and it was possible :/
And, why should you use CWM to flash instead of the stock recovery?
ootz0rz said:
Hmm I see, thanks for the info... there was no odex file for that particular file, so I thought I'd be lucky and it was possible :/
And, why should you use CWM to flash instead of the stock recovery?
Click to expand...
Click to collapse
No problem. While on the topic, is that thanks button new, or am i just blind, and missed it all this time?
It's something about signatures, if I remember correctly, though, that may be 3e. I think part of it is that it's just typically done with CWM.
ootz0rz said:
I wanted to apply one of the battery mods to my captivate i896 (running the stock rogers rom), specifically version E.
I tried using the UOT Kitchen website at first but that failed. So then I tried to do it myself, but that also fails. Something seems to be going wrong when I try to apply the update.zip I have and I see no error output to help me trace it. Here's what I've been doing (when I tried it from scratch):
So I downloaded the related zip file from the second post, "scbm_E_grey_number.zip".
I then used "Android Theming and Tweaking" to get the framework file from my phone, and decompile it. I replaced the corresponding .png and .xml files from "scbm_E_grey_number.zip" to the appropriate folders in the decompiled folder from the ATT software. Then using the same software, I compile the framework apk again.
I then use the update.zip creator. I create a "framework" folder in the "placehere" folder for the update creator. Inside the framework folder I placed my new APK. I then ran the update creator to generate a new script, which copies from "framework" to "framework" on SYSTEM. Finally, I have it create the update.zip for me.
Everything is fine up to this point. I place the update.zip on my SD card, boot my phone into recovery, try to flash it...I get the following:
Code:
-- Install from sdcard...
Finding update package...
Opening update package...
Installing update...
Installation aborted.
I've tried this a few times with no luck
I'd like to figure this out in the hopes that I can do some mods of my own in the future, so any help would be great Thanks![/QUO
Flash perception
Click to expand...
Click to collapse
dfuse06 said:
Flash perception
Click to expand...
Click to collapse
Eh, I'm hesitant to flash a custom rom. I have a rogers captivate and don't want to be stuck with an at&t boot screen (in case I need for repair or whatever) and I don't want to be stuck with poor GPS performance (as mine works VERY VERY well right now).
ootz0rz said:
Eh, I'm hesitant to flash a custom rom. I have a rogers captivate and don't want to be stuck with an at&t boot screen (in case I need for repair or whatever) and I don't want to be stuck with poor GPS performance (as mine works VERY VERY well right now).
Click to expand...
Click to collapse
AT&T boot screen can be replaced, but you have to do a whole bunch of Odin stuff to get there. Also, that's because we(I'm on rogers as well) have a tweaked modem.bin. You can flash that, or one of the jupiter/JM9 fixes to get similar gps performance. But obviously, it's your choice. You are messing with a quite expensive piece of hardware. However, if you want to apply mods, you need to get a custom rom.
TheEscapist said:
AT&T boot screen can be replaced, but you have to do a whole bunch of Odin stuff to get there. Also, that's because we(I'm on rogers as well) have a tweaked modem.bin. You can flash that, or one of the jupiter/JM9 fixes to get similar gps performance. But obviously, it's your choice. You are messing with a quite expensive piece of hardware. However, if you want to apply mods, you need to get a custom rom.
Click to expand...
Click to collapse
I'd love to have a set of concise instructions detailing all that...but everything is all over the place and difficult to find :/ Right now I'm just mostly reading up on things and trying to learn
There's instructions in the dev forum. If I wasn't on my phone, I'd grab the link for you. As far as learning, you just have to spend hours and hours on here.
TheEscapist said:
There's instructions in the dev forum. If I wasn't on my phone, I'd grab the link for you. As far as learning, you just have to spend hours and hours on here.
Click to expand...
Click to collapse
Heh I've been trying. It's certainly a bit of a learning curve
Hi there folks,
I want to flash kernels on the go (Semaphore "regular" and Big Mem version) and using the least applications possible (i.e. without SGS Kernel Flasher, if possible).
So I'm looking for a way to flash them via the CWM .zip installation.
I know (think) that with the proper installation script inside the .zip, it should work OK. In fact, I've found this solution that achieves this, but it doesn't work in our phone (I've tried and the old kernels stays around), so probably I'm looking for something similar to that.
Would you let me know what you think?
PS: I've also found this one too, but obviously the kernel in my case is .tar so it won't directly work with CWM...
Thanks
Just out of curiosity, what's wrong with Kernel Flasher?
Dan_Aykroyd said:
Hi there folks,
I want to flash kernels on the go (Semaphore "regular" and Big Mem version) and using the least applications possible (i.e. without SGS Kernel Flasher, if possible).
So I'm looking for a way to flash them via the CWM .zip installation.
I know (think) that with the proper installation script inside the .zip, it should work OK. In fact, I've found this solution that achieves this, but it doesn't work in our phone (I've tried and the old kernels stays around), so probably I'm looking for something similar to that.
Would you let me know what you think?
PS: I've also found this one too, but obviously the kernel in my case is .tar so it won't directly work with CWM...
Thanks
Click to expand...
Click to collapse
I would love to help if you have posted this in the right thread.. this is the development thread!
myrddral said:
Just out of curiosity, what's wrong with Kernel Flasher?
Click to expand...
Click to collapse
Nothing, it works great, but I want to minimize the number of installed apps, so it'd be even greater to be able to flash it via CWM
fahad123 said:
I would love to help if you have posted this in the right thread.. this is the development thread!
Click to expand...
Click to collapse
Yeah, I thought this belonged here since CWM, flashing kernels and kernel flashing apps would be considered as development tools.
If I was wrong, please forgive and may a mod move it away
Thanks!!!
It is a question, there is a dedicated Question and Answer thread. HMMM WHERE SHOULD I PUT IT?
This might help you?
http://forum.xda-developers.com/showthread.php?t=1308448
Thanks!
Jarmezrocks said:
This might help you?
http://forum.xda-developers.com/showthread.php?t=1308448
Click to expand...
Click to collapse
Thanks James, that was awesome!
Sadly they don't have the Semaphore 1.9.1 kernels (regular and big memory) which are what I use.
Now that I think about... I'll download what they have and try replacing the zImage. Will let you know how it goes!
Great!
It worked!
I had to modify the installation script a little and replace the zImages with the corresponding ones and it flashed OK!
Thanks Jamez, you rock!
There are two kind of kernel!
You can flash kernel with odin, like (speedmodkernel o other).
You can flash in Cwm mode! Usually are in zip file and flash it in recovery mode! It must be specify, if you can use odin or cmw!
Pay attention to cm7/miui kernel!
They use a particular filesystem and they aren't compliant to stok rom!
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?