Her is my questions:
1.if i unpack some rom and change file...say i replace camera with some new camera files....then repack..will it install?
2.if i nandroid back up and post file here will everyone be able to use it or its only for my serial......will ppl have my phone number? i understand thy would get all my contacts and stuff
3.i wipe..then i install a rom...so i have it running
ppl on forum say flash...some specific file...do i do it in recovery or do i just unzip it to root?
Ty
sivadin said:
Her is my questions:
1.if i unpack some rom and change file...say i replace camera with some new camera files....then repack..will it install?
2.if i nandroid back up and post file here will everyone be able to use it or its only for my serial......will ppl have my phone number? i understand thy would get all my contacts and stuff
3.i wipe..then i install a rom...so i have it running
ppl on forum say flash...some specific file...do i do it in recovery or do i just unzip it to root?
Ty
Click to expand...
Click to collapse
I'm not a developer but this is what I THINK:
1- Before you can use a rom you've created you must first run it through a program that signs it. Your phone will not recognize an unsigned rom and may brick it.
2-I've created nandroids but never had to use one, so IDK.
3- Do it in recovery or through adb commands (usually only if your having problems flashing in recovery or you're a developer).
...hope this helps and someone please correct me if I've mistated anything.
....duplicate post. Sry.
1.if i unpack some rom and change file...say i replace camera with some new camera files....then repack..will it install?
You need to sign it with a signing program. You also should zipalign any of the apk's you've added.
2.if i nandroid back up and post file here will everyone be able to use it or its only for my serial......will ppl have my phone number? i understand thy would get all my contacts and stuff
yes... but your google account would be on there too and all of your numbers and personal information. I don't suggest doing this...
3.i wipe..then i install a rom...so i have it running
ppl on forum say flash...some specific file...do i do it in recovery or do i just unzip it to root?
I don't know what you're asking.
sivadin said:
3.i wipe..then i install a rom...so i have it running
ppl on forum say flash...some specific file...do i do it in recovery or do i just unzip it to root?
Click to expand...
Click to collapse
Yes, do it in recovery as you would a ROM. No wiping.
Related
this thread is open to help newbies to install the 2.1 custom rom with the simples way..
you also can discuss any problem here..
dont mess the dev thread with a dumb question...
thanks to "Perceval from Hyrule" for the original tutorial..
this is revise version for 2.1
INSTALLATION FOR 2.1 AOSP
Before attempting anything, make sure you have AT LEAST 50% of battery charge. Don't try anything with low battery, you can abort the flashing and brick your device !!!
Please make sure you're also running a 2.1 rom (Generic, nordic, official, custom...)
1st step:
make sure your computer is adb debugging ready..
in case in need for command execution..
- Download Android SDK
You don't need to save the entire archive (but you can), you just need the Tools folder (because it contains ADB, the Android Debug Bridge we need to install files).
2nd step:
- On x10 :
Enable USB debugging (Setting > Applications > Development).
Root your device. easiest way by using z4root.
Download and install Busybox (from Market), make sure it says "Done!".
3rd step:
install xrecovery for recovery menu.
xrecovery a.k.a recovery menu
4th step:
option 1:
Download rom.
2.1 AOSP ROM (make sure 2.1 since this tutorial is for 2.1)
extract the rom (u will get 2 folder + 1 files)
upload the file into your sd card root(sdcard/*.zip)
rename the *.ZIP to Update.ZIP
*the 2 folder contain application which u can install if u like
option 2:
Download rom.
2.1 AOSP ROM (make sure 2.1 since this tutorial is for 2.1)
extract the rom (u will get 2 folder + 1 files)
upload the file into your sd card root(sdcard/*.zip) or in any folder u like
*the 2 folder contain application which u can install if u like
5th step:
boot into recovery menu (by restart and hit few times back button when "SONY ERICSSON" word appear)
backup your original rom(in case u want to restore next time)
hit full wipe
option 1:
hit install update.zip from SD card
option 2:
hit install custom zip
search for the custom zip in folder where u save it
hit the zip file
after reboot, u will get custom rom installed in your X10
good luck ;-)
TIPS
1-u can do like rendeiro2005 said by creating rom folder and put the rom collection in it..
so if u want to change or try other rom just choose zip file from the particular folder...
this require using step from option 2
2-another one, by creating folder which contain backup image..
u can collect your friends backup image and put in one folder..
if u want to try, just restore the particular image file using backup/restore option in recovery menu and choose the backup image file..
collection of custom rom backup file for recovery menu:
2.1 Custom ROM AOSP by jerpelea & zdzihu
2.1 Shipped ROM 002 Full by jerpelea
2.1 Shipped ROM 002 Light 002 by jerpelea
Eternity by SEMPITERNAL
Xten by rabetionline
X10 Eminence by XperiaX10iUser
[2.1 AOSP THEME] X10 AOSP Theme by rmourar
Android 2.1 Gingerbread Style by Thijs96
for testing purpose only (not fully work)
MIUI tehnical preview by jerpelea
Gingerbread 2.3 PREVIEW rom by zdzihu
p/s: anyone who want to contribute their customize custom rom using backup image and list here can either pm me or response in this thread..
for use with recovery menu only..
Hi bro,
Only two calls on your excellent tutorial:
1. No need to put the rom in the root of the sdcard. I, for example, to distinguish the roms, I`ve created a folder "Rom" in the root and put the roms in there.
2. It is not necessary to rename the *. zip file.
When we entered the xRecovery, you can go to "install Custom Zip> zip Choose Custom from sdcard>" Now in my case I a. .. "Roms >........" and I intend to choose
rendeiro2005 said:
Hi bro,
Only two calls on your excellent tutorial:
1. No need to put the rom in the root of the sdcard. I, for example, to distinguish the roms, I`ve created a folder "Rom" in the root and put the roms in there.
2. It is not necessary to rename the *. zip file.
When we entered the xRecovery, you can go to "install Custom Zip> zip Choose Custom from sdcard>" Now in my case I a. .. "Roms >........" and I intend to choose
Click to expand...
Click to collapse
thanks for the info..
i forgot we have 2 ways of installing...
reupdate..
fyzm345 said:
thanks for the info..
i forgot we have 2 ways of installing...
reupdate..
Click to expand...
Click to collapse
it`s not a different way.
i think that way would be more simple (for me at least) `couse you can have different roms puted on the same directory without, everytime that you want to install one change his name to default.zip
but...great TUT (clap your hands floks)
Since i haved installed the 2.1 AOSP, my recovery were deleted !
So i install the xrecovery.apk but it doesnt work (don't fin the SD Card), so i paste the 3 files with root explorer but nothing to do... the recovery doesn't work at all =(
Bluewall said:
Since i haved installed the 2.1 AOSP, my recovery were deleted !
So i install the xrecovery.apk but it doesnt work (don't fin the SD Card), so i paste the 3 files with root explorer but nothing to do... the recovery doesn't work at all =(
Click to expand...
Click to collapse
its work actually...
try repeat the paste 3 file and make sure the file is exist..
also when paste make sure u hit the mount r/w button in root explorer..
It says make sure you are 2.1 but I'm not im 1.5...... basically I'm stock X10..... and i want to flash so does it matter if I'm 2.1 or not. Because it doesn't make since that you say make sure your 2.1 but I'm flashing to get 2.1
Tchem said:
It says make sure you are 2.1 but I'm not im 1.5...... basically I'm stock X10..... and i want to flash so does it matter if I'm 2.1 or not. Because it doesn't make since that you say make sure your 2.1 but I'm flashing to get 2.1
Click to expand...
Click to collapse
hah...
get it...
actually, to make the xrecovery works, u need to use 2.1...
u can try this flashing tool and reflash your x10 into version 2.1 1st..
http://forum.xda-developers.com/showthread.php?t=825201
after flash finish, then u follow the step at this thread...
*credit to Bin4ry for the tool and link...
Ahhhhh so that's what I'm doing wrong. But I'm already rooted so can I flash as you say even after I'm rooted and everything will work smoothly?
Tchem said:
Ahhhhh so that's what I'm doing wrong. But I'm already rooted so can I flash as you say even after I'm rooted and everything will work smoothly?
Click to expand...
Click to collapse
yeah...
lets fix it..
u already mess the guide actually...
so let start over again...
make sure u flash ur phone into 2.1...
did u already flash into 2.1??
No I have to wait till my wife gets home she has the phone with her. I'm working out the prelimerarys so when she gets home I can jump right into it.
Tchem said:
No I have to wait till my wife gets home she has the phone with her. I'm working out the prelimerarys so when she gets home I can jump right into it.
Click to expand...
Click to collapse
okay...
u need to flash it to 2.1...
after that, u can follow tutorial from this thread...
since my country is almost 2 a.m, i cant help u for this moment..
i will catch up with u tomorrow...
Just wondering
Hey guys
well i was trying to install 2.1 ASOP, but i notice that i cant do it because i have the dual boot to 2.2.1
Do you guys have a solution so i can use all 3?? or should i just reflash my phone to enjoy 2.1 ASOP or should i stay with my dual boot and play with froyo??
Marazao said:
Hey guys
well i was trying to install 2.1 ASOP, but i notice that i cant do it because i have the dual boot to 2.2.1
Do you guys have a solution so i can use all 3?? or should i just reflash my phone to enjoy 2.1 ASOP or should i stay with my dual boot and play with froyo??
Click to expand...
Click to collapse
Install all 3?! Yes you can...if you want you can install WM and iOS
Now mre seriously.
If you want to install 2.1 you have to format sdcard to one partition only. 2.1 doesn't work with more than 1.
Then you can flash...follow this guide to do so
Sent from my Xperia AOSP using XDA App
I want to recover my x10!! It stays on boot screen of Eternity build 002!!!!! PC companion dont work. Anyone that help me will have his name in my signature in big!! PLEASE!!!
PlayGunsta said:
I want to recover my x10!! It stays on boot screen of Eternity build 002!!!!! PC companion dont work. Anyone that help me will have his name in my signature in big!! PLEASE!!!
Click to expand...
Click to collapse
reinstall trhough SEUS?!
+1
thanks for the easy guide.
is there any way how to upgrade without using usb???
I have everything installed minus custom rom, I'm hesitant because I'm running different firm ware does this matter. I see most custom are .204 and mine is like .506, I'm running a Rogers x10a I do believe. Any suggestions is greatly appreciated.
Sent from my X10a using XDA App
So I was bored at work and did something stupid. Now I'm wondering if there is some way to fix it without having to flash my entire phone.
Is there someway a single file can be deleted using a CWM update zip. The file is the ported version of google now and having installed it using root explorer it is stopping my phone from booting entirely.
The file is "system/app/velvet.apk".
If anyone is experienced at CWM and knows how this can be achieved then I would be extremely grateful.
SOLUTION: Flashed a stock nandroid backup of the system, managing not to lose my data.
jcspecs said:
So I was bored at work and did something stupid. Now I'm wondering if there is some way to fix it without having to flash my entire phone.
Is there someway a single file can be deleted using a CWM update zip. The file is the ported version of google now and having installed it using root explorer it is stopping my phone from booting entirely.
The file is "system/app/velvet.apk".
If anyone is experienced at CWM and knows how this can be achieved then I would be extremely grateful.
Click to expand...
Click to collapse
I would imagine you could use adb to delete the file. Install the Android SDK on your computer and use adb shell to delete the offending file from bootloader mode. Havent tried it before myself, but I believe that's what adb is for amongst other things?
p.s. You should post this in Q&A forum and you might get a better response. This is not dev related.
salada2k said:
I would imagine you could use adb to delete the file. Install the Android SDK on your computer and use adb shell to delete the offending file from bootloader mode. Havent tried it before myself, but I believe that's what adb is for amongst other things?
p.s. You should post this in Q&A forum and you might get a better response. This is not dev related.
Click to expand...
Click to collapse
Ok will try it at work, or at home. Thanks for the suggestion. Will post in the Q&A forum as well.
Velvet.apk isn't that the voice reg. From jellybean,that shouldn't stop your phone from booting.the app would only FC.
Adb or reflash as suggested above
Tell someone to make it cwm flashable. Boot to recovery and flash. Make a new thread or ask for this a mod to rename it.
Something like this " make velvet.apk cwm flashable".
Cheers
Sent from my GT-I9300 using xda premium
Hey guys,
do you know how i can directly reboot into recovery and flash a .zip file via script for terminal emulator?
I think you know the ROMManager, you can download updates there, it automatically reboots into recovery and flashes without asking the .zip file, how can i realize that via script for the terminal emulator? cuz i want to create a updater for my and my friends roms
Is there any way to realize that?
Thanks,
Glenn
No answers? Please!
fd1999 said:
No answers? Please!
Click to expand...
Click to collapse
wich phone do u have?
have u installed the recovery image the rom manager has got?
jiffer1991 said:
wich phone do u have?
have u installed the recovery image the rom manager has got?
Click to expand...
Click to collapse
So, first, GlenniBoy and I, we're working on a new project. Currently we're using CWM.
fd1999 said:
So, first, GlenniBoy and I, we're working on a new project. Currently we're using CWM.
Click to expand...
Click to collapse
as u said the rom manager contains the feature u want to use on the terminal for the roms want to use.
check out the rom manager apk with the apk tool
u might find a hint in there (a script or something) because i guess something like that has to be there
Did it work?
We didn't know, I'll try it later, but already pressed Thanks
Hi All,
Do anyone can help me to find a way to backup and clone the ROM ?
I have 50 Galaxy Tab and need to clone the ROM that I have setted to the other and need the easier way.
Is it possible with Fastboot ?
Thank you in advance.
-JFK- said:
Hi All,
Do anyone can help me to find a way to backup and clone the ROM ?
I have 50 Galaxy Tab and need to clone the ROM that I have setted to the other and need the easier way.
Is it possible with Fastboot ?
Thank you in advance.
Click to expand...
Click to collapse
Hello there,I think u don't need to clone anything just transfer "rom".zip from PC to that divice which u want to have that rom,
Or just download it again on other divice!
Vinchenzo13 said:
Hello there,I think u don't need to clone anything just transfer "rom".zip from PC to that divice which u want to have that rom,
Or just download it again on other divice!
Click to expand...
Click to collapse
Thank you for your reply.
How to made the "rom.zip" ?
-JFK- said:
Thank you for your reply.
How to made the "rom.zip" ?
Click to expand...
Click to collapse
Mostly ppl download rom's,what kind rom u want,I can hook u up with some links
-JFK- said:
Hi All,
Do anyone can help me to find a way to backup and clone the ROM ?
I have 50 Galaxy Tab and need to clone the ROM that I have setted to the other and need the easier way.
Is it possible with Fastboot ?
Thank you in advance.
Click to expand...
Click to collapse
Sort of difficult to understand your question, but I think what you want to do is backup your current ROM and then flash it to 50(!) other galaxy tabs. Use CWM recovery and select "backup." Let it run. When it's finished, the backup file will be in a folder called "clockworkmod" (it's several large files in a folder). Copy this folder to the other tablets (same file structure) and in CWM recovery choose "restore." (it's right next to backup).
BTW- If you don't have root you'll need to do that first; you can then install CWM recovery with the ROM Manager app from the play store. It won't work unless you have root first.
If none of that made sense, you need to read a lot more of this forum before you flash anything on your tablets (since you can damage/brick your tablets if you're not aware of what you're doing).
slack04 said:
Sort of difficult to understand your question, but I think what you want to do is backup your current ROM and then flash it to 50(!) other galaxy tabs. Use CWM recovery and select "backup." Let it run. When it's finished, the backup file will be in a folder called "clockworkmod" (it's several large files in a folder). Copy this folder to the other tablets (same file structure) and in CWM recovery choose "restore." (it's right next to backup).
BTW- If you don't have root you'll need to do that first; you can then install CWM recovery with the ROM Manager app from the play store. It won't work unless you have root first.
If none of that made sense, you need to read a lot more of this forum before you flash anything on your tablets (since you can damage/brick your tablets if you're not aware of what you're doing).
Click to expand...
Click to collapse
The goal is to not have to root, install CWM...
Starting from a brand new Galaxy tab and with a quick action get it cloned.
I spend too much time to root, install CWM and then my backup.
There is another way ?
-JFK- said:
The goal is to not have to root, install CWM...
Starting from a brand new Galaxy tab and with a quick action get it cloned.
I spend too much time to root, install CWM and then my backup.
There is another way ?
Click to expand...
Click to collapse
Sorry, but there's no other way. But it's really not that much time. You just pointed out that it's 3 steps. It will take a day or less.
firstly i request all moderators of xda in grand 2 forum,
as i am unable to post on developement section,
i am posting the thread here..
plz move it to developement section.
ok now back to topic,
try at your own risk!
i will not be responsible if anything happens to your phone
To all the users who have succesfully rooted grand 2,
there can be a way to install (flash) recovery on your phone!
i was exploring the system and i found a file in "/system" folder
called "recovery-from-boot.p"
i THINK this is the file that causes problem!
you may delete it or rename it...(renaming is safer)
once you delete it, you may flash custom recovery via ODIN
and even if the recovery gets currupted or if you cant boot into recovery, you can simply boot normally and restore the renamed or deleted file!!!
and then once again you may try to flash custom recovery from ODIN (as stock gets deleted as soon as you modify recovery-from-boot.p file)
press thanks if this post helped!
dindt find any file like u wrote.... plss provide specific path.. so we can try
Rakesh251 said:
dindt find any file like u wrote.... plss provide specific path.. so we can try
Click to expand...
Click to collapse
Its located here:
bro no such file is available.. this wont help to solve .and still custom recovery not available for grand2
how would u know that it won't help..
i only post threads as i know what i am doing.
the file which i uploaded up there is taken from MY PHONE ITSELF i.e galaxy GRAND 2..
and That FILE (recovery-from-boot.p) IS present on my phone and i m using Stock rom and not any other rom..
Same with me... none of them named exactly like you mention above.
Sent from my SM-G7102 using XDA Premium 4 mobile app
it only appears on a Stock UN-ROOTED firmware..
In order to inject custom CWM there isnt a necessity to root device.
so firstly we need to remove file that I mentioned in my previous post and inject recovery.
and via that recovery,
we can flash a custom kernel that automatically roots device!
vrushabh sutar said:
it only appears on a Stock UN-ROOTED firmware..
In order to inject custom CWM there isnt a necessity to root device.
so firstly we need to remove file that I mentioned in my previous post and inject recovery.
and via that recovery,
we can flash a custom kernel that automatically roots device!
Click to expand...
Click to collapse
Dude, if the FILE just appears in STOCK UNROOTED FIRMWARE , so how can we delete that.
Coz, to delete a /system file, we need ROOT access.
NOT POSSIBLE.
And in rooted version, the FILE is not available :victory:
00hacktheworld00 said:
Dude, if the FILE just appears in STOCK UNROOTED FIRMWARE , so how can we delete that.
Coz, to delete a /system file, we need ROOT access.
NOT POSSIBLE.
And in rooted version, the FILE is not available :victory:
Click to expand...
Click to collapse
Thank you for replying.
I know that it can't be deleted,
but one may understand the importance of that ".p" file and understand its working, as it plays a vital role in booting up recovery...
the only thing I wanna let users understand is that,
stock recovery includes that file and
it got deleted when rooted because the rooting package (eg. CF root) didnt contain the .p file
when I studied that strange file,
it consisted of mapping and accurate memory address as well as accurate size of stock recovery image in bytes,
so that whn new recovery gets flashed, it verifies with the .p file!
and talking abt modifying the .p file,
we must create a custom linux binary with zerglings and packed into .tar file which gets flashed to phone via Odin!
for build creation you can use this tool..
http://www.xda-developers.com/android/comprehensive-guide-to-the-android-build-process/?__utma=60652090.747738090.1398670920.1400078979.1400132113.21&__utmb=60652090.0.10.1400132113&__utmc=60652090&__utmx=-&__utmz=60652090.1400132113.21.12.utmcsr=google|utmccn=%28organic%29|utmcmd=organic|utmctr=%28not%20provided%29&__utmv=-&__utmk=163283131
So I found the reason behind this
It is a file used by Software Update Application to flash updates.
If you want proof go-to the data folder of the SOFTWARE UPDATER and there will be a 3mb file. Copy it to pc and open using winrar. You can see many files including boot.img.
So the author of this thread was about to update his/her phone when he found the file :thumbdown:
SO MYSTERY SOLVED
SCOOBY DOOBY DOOO
Sent from my SM-G7102
i didnt't get what you are on to...
i noticed that the Update Package (i.e the OTA) easily jumps over all the restrictions imposed by Bootloader(locked one) and gets easily flashed to the phone...
therefore the whole matter is now pointing out to the 'ro.build.fingerprint' as well as Verification of MD5 hashes linked directly to Flashing InstructionSet