I am looking for a dev that can help me try and enable JIT on the SGS i have, a dalvikvm + libdvm.so and libnativehelper.so that should enable JIT. Could a dev with please create an update zip with these original files from our SGS (as a backup) and then sign these files as an update.zip and then do the same with the files i have attached - then try and flash them and see if you can get it to boot.
Please PM me if you have any questions or if you can successfully boot the phone.
(i am away from home for a few days and will not be able to try myself.. using hotel computer...)
Thanks
Sorry forgot to upload the files was watching the match. Will upload them in the next few minutes.
I already done compiled with JIT enable
copy files to my device, succesfully boot up but when I test with Linpack
MFLOPS was decrease, 6.65
before apply those files MFLOPS was 8.92
Hmm I might done somethings wrong?
FYI,
Maybe
Yes you may have made a mistake, could you please try with the files above.
can't boot for my i9000
Hang on boot loop
...
W/BootAnimationSEC( 2179): ms4631 - Repeat Loop Animation
...
Not working and NoooooO !! I can't remove those libs T_T
execute "su" got "Segmentation fault" -__-"
@bratfink May I? where did you got those files.
You can use my Custom Rom for this ;-) http://forum.xda-developers.com/showthread.php?t=724450
I just want to put those (essential) JIT enabled file. Or It will not work? if there're only those 3 files.
Just don't want to use custom ROM right now, it's base on European rom but I'm living in Asia. There're many tasks to do after use others region rom, for me.
@seraphimserapis Could you suggest the information that made me, to build my own custom rom, base on my region's rom. I googling, googling couple weeks ago but still can complete the jigsaw.
-_-" finally, I can recover my devices ...
@bratfink I think those files were dangerous, got stucked at the (big S boot screen), broke the "su" command so I can not restore the original one.
I must flash the Kernel back to LeShak kernel then restore those files. flash current again then device back to normal.
Hello all,
I hoping that someone here at xda can help me gain r/w access to the /system folder on a skeye.dart.
This is custom device (google will find it) that has Android ported and is currently running Android 2.1. It has a custom bootloader but will has the functionality to update the Android ROM from the sdcard. I am looking to hack the current ROM (update.img) so that I can write to the /system partition.
This is where the but comes in. Having searched high and low, I found the following thread:
HTML:
http://forum.xda-developers.com/showthread.php?t=1477845
This seemed to be what I needed as I had troubles with any Windows/cygwin process but I I am getting the following message when I try to split the img file:
Code:
[email protected]:~$ perl split_bootimg.pl update.img
Android Magic not found in update.img. Giving up.
I'm hoping someone can throw a bit of light on this for me? I can supply the zip file to anyone who's interested in having a look at this.
SKeye.dart
Just encountered batch of Skeye.dart mobile devices. They are running CE6.0. Is there a path to upgrade? How to convert to Android?
Any hints, ideas, links etc would be appreciated.
Ace 2 Gt-i8160L LATIN. How to install CM?
When I install CM, don't wok sim-card and not IMEI.
Restore IMEI don't helped.
This is modem or hw problems, i think.
Sorry my english is bad.
...
Replace tee folder in rom zip /system/lib with the one from stock rom
Sent from my GT-I8160 using Tapatalk
1) backup tee folder
2) On build.prop change all GT-I8160L to GT-I8160 (without L)
3) all wipes factory/cache/dalvik
3) Install CM_Xversion
4) Whith roo explorer replace tee folder
Enjoy.
2) also can delete assert :/
4) you can just replace in zip before flashing (just sayin)
Sent from my GT-I8160 using Tapatalk
When to alter ROM
teddytsen said:
2) also can delete assert :/
4) you can just replace in zip before flashing (just sayin)
Sent from my GT-I8160 using Tapatalk
Click to expand...
Click to collapse
Am located in New Zealand, and hence using model i8160L, running stock JB ROM
Am trying to modify / install Maclaw CM KK ROM -- but am having problems
-- it "reads" the ROM and "immediately" (afaik) but aborts installation
-- NO ERROR MESSAGES come up for any indication as to why it's aborting
Am trying to do the following -- appreciate any feedback to correct procedure if I'm making eny errors
(i) omitting any and all references to L in 8160L string -- should I restrict it to any particular lines? -- using Build.Prop Editor
-- the Settings/About Device shows it as an 8160, rather than an 8160L after the Build.Prop changes, but the boot screen still shows it as the 8160L -- but at least I don't get the error message about trying to install ROM on wrong device
(ii) before attempting installation, downloading the latest ROM, unzipping the ROM using 7zip, deleting "tee" folder
-- and pasting tee folder from the stock JB ROM installed on my phone
(iii) re-zipping the ROM using 7zip -- I notice I get a different MD5 to that llsted on the download page
(iv) attempting to flash the modified ROM in Recovery mode, but it aborts
Don't know enough to know if install procedure tries to validate the "to be installed" ROM's MD5 and aborts since it's different from that on the download page
Don't know what purpose of tee folder is -- is it to connect to local carrier?
How about if I try to install "unmodified" ROM (in its unmodified form) and once it's installed, if it does (?), replace the tee folder at that later stage, to check for ability to connect to carrier?
Do I need to unlock the SIM card first --- as that's also something I haven't done
(naturally, I've backed up and able to restore to what I had before attempting the install)
KiwiCool60a said:
Am located in New Zealand, and hence using model i8160L, running stock JB ROM
Am trying to modify / install Maclaw CM KK ROM -- but am having problems
-- it "reads" the ROM and "immediately" (afaik) but aborts installation
-- NO ERROR MESSAGES come up for any indication as to why it's aborting
Am trying to do the following -- appreciate any feedback to correct procedure if I'm making eny errors
(i) omitting any and all references to L in 8160L string -- should I restrict it to any particular lines? -- using Build.Prop Editor
-- the Settings/About Device shows it as an 8160, rather than an 8160L after the Build.Prop changes, but the boot screen still shows it as the 8160L -- but at least I don't get the error message about trying to install ROM on wrong device
(ii) before attempting installation, downloading the latest ROM, unzipping the ROM using 7zip, deleting "tee" folder
-- and pasting tee folder from the stock JB ROM installed on my phone
(iii) re-zipping the ROM using 7zip -- I notice I get a different MD5 to that llsted on the download page
(iv) attempting to flash the modified ROM in Recovery mode, but it aborts
Don't know enough to know if install procedure tries to validate the "to be installed" ROM's MD5 and aborts since it's different from that on the download page
Don't know what purpose of tee folder is -- is it to connect to local carrier?
How about if I try to install "unmodified" ROM (in its unmodified form) and once it's installed, if it does (?), replace the tee folder at that later stage, to check for ability to connect to carrier?
Do I need to unlock the SIM card first --- as that's also something I haven't done
(naturally, I've backed up and able to restore to what I had before attempting the install)
Click to expand...
Click to collapse
md5 sum change probably because you uncompressed and re-compressed file.
no you dont have to unlock carrier.
use total commander and delete first 3 lines in updater-script.(all before mount.. bahblablah) and then compress it, then try.
btw it doesnt show any status errors?
When to alter ROM cont'd
teddytsen said:
md5 sum change probably because you uncompressed and re-compressed file.
no you dont have to unlock carrier.
use total commander and delete first 3 lines in updater-script.(all before mount.. bahblablah) and then compress it, then try.
btw it doesnt show any status errors?
Click to expand...
Click to collapse
MANY MANY thanks for your very prompt reply, and further information
"status errors" -- as a result of ?? -- no status errors evident after rebooting with modfified Build.Prop
had lots of "fun" on my previous efforts with custom ROMs -- played with several on a Huawei G300 I had --
-- but, gee, this is an ongoing learning process -- now to learn about updater script !!!
(only learnt about Total Commander from your post - despite its high rating -- but note others have used other things for "text editing")
(but have discovered some TUTs on xda)
Reading more carefully through the posts I see it may be possible to flash the ROM, and then later, substitute the tee folder supplied in the Maclaw ROM with the stock JB one -- right?
I'll definitely learn more about updater-script, but I'll try to flash the ROM again without modifying the ROM === OK?
KiwiCool60a said:
MANY MANY thanks for your very prompt reply, and further information
"status errors" -- as a result of ?? -- no status errors evident after rebooting with modfified Build.Prop
had lots of "fun" on my previous efforts with custom ROMs -- played with several on a Huawei G300 I had --
-- but, gee, this is an ongoing learning process -- now to learn about updater script !!!
(only learnt about Total Commander from your post - despite its high rating -- but note others have used other things for "text editing")
(but have discovered some TUTs on xda)
Reading more carefully through the posts I see it may be possible to flash the ROM, and then later, substitute the tee folder supplied in the Maclaw ROM with the stock JB one -- right?
I'll definitely learn more about updater-script, but I'll try to flash the ROM again without modifying the ROM === OK?
Click to expand...
Click to collapse
-Dont care about ro.build.model. once assert is deleted you dont have to change it. And its not mandatory.
-I recommended total commander just because its the only root browser i have that shows the assert in 3 lines exactly. Unless es etc. You can also use other editors ^.^
-like when installation is aborted, it says status 7(or 0 etc)
Sent from my GT-I8160 using Tapatalk
Many thanks -- now for the "rest" and time for tee
teddytsen said:
-Dont care about ro.build.model. once assert is deleted you dont have to change it. And its not mandatory.
-I recommended total commander just because its the only root browser i have that shows the assert in 3 lines exactly. Unless es etc. You can also use other editors ^.^
-like when installation is aborted, it says status 7(or 0 etc)
Sent from my GT-I8160 using Tapatalk
Click to expand...
Click to collapse
Many thanks!! KK installed -- that was the "fascinating" thing -- no status errors on previous failed attempt at installation -- nothing
but now it's installed -- with GApps added, and now to "worry" about the rest of it all
unsurprisingly -- if tee does what I think it does -- but I can't find a TUT on that anywhere
-- so currently, I can't connect to my local carrier, so it's currently not a :"phone" as such
even more frustratingly, computer found phone when it was first plugged in, but now seems to have lost it!! time to reboot system
-- and, it's been a while since I used CM but I can't find extsdcard!!
Cm file manager?
Settings-general settings-access mode- root
Sent from my GT-I8160 using Tapatalk
Permissions
teddytsen said:
Cm file manager?
Settings-general settings-access mode- root
Sent from my GT-I8160 using Tapatalk
Click to expand...
Click to collapse
sorry, not used to that one -- for that matter, I tend to stay away from things affecting the system I don't know
so I'm lost in permissions in different apps -- can't find "paste" in CM file, and can't find RW permissions in ES!!
But you're being exceptionally patient! thanks, heaps
Lot easier than I thought -- and MANY thanks again
KiwiCool60a said:
sorry, not used to that one -- for that matter, I tend to stay away from things affecting the system I don't know
so I'm lost in permissions in different apps -- can't find "paste" in CM file, and can't find RW permissions in ES!!
But you're being exceptionally patient! thanks, heaps
Click to expand...
Click to collapse
Actually, it's a lot easier than I thought -- working phone, with KK installed -- without need to unlock carrier!!
Many thanks for the guidance, patience ....
and, of course, to the ROM developers
Repeated problems with Maclaw KK ROM
KiwiCool60a said:
Actually, it's a lot easier than I thought -- working phone, with KK installed -- without need to unlock carrier!!
Many thanks for the guidance, patience ....
and, of course, to the ROM developers
Click to expand...
Click to collapse
Many thanks for past help with intall procedure -- but have had repeated problems of late -- last installed ROM on March 9th -- could install several versions prior to that date, and use them successfully, but since then have been unable since I repeatedly get "Error searching for networks", and hence cannot connect to carrier, and hence unable to use phone as phone, though other functions seem to work OK, -- any ideas??
I know most people are on 4.4 by now, but I want to bring this tinkering I've done over the course of my Toro ownership over these 3 years to light!
So Here's Using the Final Google-Supported Build on Sprint's or Verizon's [Annoyingly] Left-Behind Variants and Getting by Verizon/Sprint's App "Compatibility Blocks" in the process!
What You'll Need
Official Google Takju/Yakju Images (I say Yakju since Google Wallet wont work anyways cuz Google Disabled it pre-4.4)
A custom ROM for the Version of Android you plan to use (ie: CM10.2 for 4.3.x or CM10.1 for 4.2.x or CM10 for 4.1.x or CM9 for 4.0.x)
ADB and Fastboot (Chances are if you're here you have these)
ClockworkMod for the variant you have (Sprint=toroplus, Verizon=toro, GSM=maguro Wait Why u reading this Maguro Users?)
A Galaxy Nexus (Any Variant)
Notepad++, Textwrangler, or any Text Editor of your choice
Zittoro's Tuna Converter Zip
7-Zip/WinRAR/File Roller/OS X Archiver
An Hour or less of your time
OPTIONAL: The Nexus Image for Your Variant for the Radios (If not already Updated)
RECOMMENDED: @madd0g 's BLE Libraries
Preparation of the Image
Unzip the tgz File Containing the Image Files as you would for a normal Image Install
If using WinRAR/7-Zip, open the ZIP file contained within and open with Notepad++ and edit these strings and save it back into the zip file
Code:
require board=tuna
If using Mac OS X or Linux's Built in Archivers, Unzip the ZIP File and Edit the text File and Edit These same strings and re-zip the folder so it looks (Almost) Unmodified, has the same files within as before
Edit the Flash-All.bat/sh and remove everything but these commands (Failure To Do So WILL Brick your Phone, double check multiple times, or... you know, copy and paste it from here! Assuming you are using the Yakju 4.3 Image)
Code:
fastboot oem unlock
fastboot reboot-bootloader
sleep 5
fastboot -w update image-yakju-jwr66y.zip
Triple Check you did everything (Dead Serious)
Now its time for the Fun Mod Part!
You know that allTuna-v4.3.zip i had you grab earlier? Open That in 7-Zip/WinRAR/Unzip it Under Mac or Linux
Remove Everything But the Variant Title You Have, Toro for Verizon, Toroplus for Sprint, and the META-INF File, we need that for Recovery to Read the new Zip
Edit The .sh File for your Variant and Remove the Lines that Involve
Code:
busybox sed -i 's/toro/maguro/' /system/build.prop
or whatever applies to your variant, AKA the first two commands in the file
Open your custom ROM and your alltuna zip side by side
Replace the files in the Alltuna.zip with the Custom ROM's versions, these will ensure they will work with your version of Android, the 4.3 version of alltuna is built with 4.3 and 4.4 in mind, but its always nice to grab newer, possibly more stable versions if they're avalible, right?
Re-Zip the Folder (If not opening Directly in WinRAR/7-Zip)
Final Stretch is Here!
Flash.bat/.sh, Run it but don't let your phone get to the welcome screen, in other words, when your phone reboots after the update flashes, pull the battery or something
Run this command to temporarily boot ClockworkMod
Code:
fastboot boot recovery-clockwork-6.0.4.3-toro.img
(toroplus in the case of Sprint, you should know this)
Flash AllTuna.zip that you modified!
Code:
adb sideload alltuna-4.3.zip
Reboot Back to the Bootloader and Lock your Phone! (Makes that ugly Lock not show up)
Code:
fastboot oem lock
Boot Up your phone into your new Stable GSM Modified ROM!
Optional Tidbits
Rooting Flash SuperSU 2.-- From Here
Credits
@Zittoro for Base Conversion Kit
@Chainfire for Root
Google for Nexus Images
Hi Everyone!
I have a Samsung Galaxy Nexus and last week after some issues I decided to format /system folder via TRWP (yes, I know...). The thing is that when I try to flash any new rom (I'm using AOKP custom rom) I get the error message of the title: "/temp/sideload/package.zip".
I've been researching and I found how to delete the 'asset' command from the file inside the rom, but I want to recover my model number in the phone so I don't have to do it everytime I flash a new Rom.
I guess there is something to modify in the system folder so asset command is ok when I'm flashing. I suppose I erased the model name after formating the system folder.
Thanks in advance for your help!
I want to add that erasing the asset command, doesn't work for me. I still have an error that aborts the installation.