Related
V20B (CIS)
V20O (DEU)
Root on V20B
information deleted
I used google translator and that's the result of the post above:
All items are strictly in the order do not jump over them and keep the sequence!
Spoiler (+ / -) (I advise you to read before flashing)
to the root of drive C:
Two. Download Attachment SmartFlashTool_External.rar (1.18 MB) Number of downloads: 37
and extract the root of drive C:
3. Download Attachment Superuser.zip (611.2 KB) Number of downloads: 51
and put ( no need to unpack ) File on the SD-card phone
4. Turn off the phone.
Five. We hold the Volume Up (+) and insert the USB cable one end into the computer, the other into the phone
6. We will have the text of S / W Upgrade Please wait while upgrading ...
Spoiler (+ / -)
7. Run the file B_SmartFlashTool_Extern.exe
Eight. Go to the tab ROM copy D / L
9. Select the two files that you extracted from the archive [PATCHED] BIN_LGP970AT-00-V20a-CIS-XXX-JAN-06-2012 +0.7 z
10. Check:
Spoiler (+ / -)
11. Click the Start button
12. Go to the process of the firmware, go to drink coffee \ tea shorter depart away from your computer to your phone
13. When you sign Download Comlete! Go to the phone
Spoiler (+ / -)
14. On the phone, we see the regime Recovery (touch it, the management of a finger)
15. Select install zip from sdcard
16. Then choose zip from sdcard
17. Prolistyvayem and choose Superuser.zip
18. Prolistyvayem and select Yes - Install SuperUser.zip
19. Select + + + + Go back + + + +
20. Choose wipe data / factory reset
21. Prolistyvayem and select Yes - delete all user data
22. Then reboot system now
That's it! Phone is loaded, if you do it right!
As a result, we have a firmware with the Root-V20A human touch and Recovery! Thank you all and good luck to you in the firmware!
Click to expand...
Click to collapse
Dont exactly know, what it does, but as far as I get it, it roots the device and installs CWM touch.
Credits go to poster, if it is successful.
Hey, thanks for posting here. Here is v20b : http://www.lgmobiles.com/gsm/download/P970 V20B(Gingerbread Version).rar
We don't have it for N version. I saw the russian forum and wanted to ask you about howvyou managed to root v20a before this method.
Sent from my LG-P970 using XDA App
this method is working just v20a(attachment patched bin file) right?
Where how I convert .kdz to .bin file?
I know russian very well.So i shortly translate all procedure done here.
They patched original 20A bin file , changing system recovery.img with clocworkmod recovery.img touch version.
Download 20A.bin extract it,and put somewhere in your computer.
and below there is a CWM flashable superuser.zip.
Download it and put to your Sd kart.Do not extract.
Then simply flash that patched 20A bin file with smart flash procedure posted here from radkor
http://forum.xda-developers.com/showthread.php?t=1448803
After finished flashing with smartflash tool go to cwm recovery and install superuser.zip
and you get rooted original 20A ginger.
Nice option for flashing and rooting
but we do not have 20N bin file yet.
we have only indian version 20B bin file, redpik posted it above
Thread moved
Unless it's a ROM or kernel you've created yourself, this doesn't belong in Development.
Doesn't SmartFlash auto erases all user data (factory reset at first boot)?
Okey... Maybe, tomorrow I will be a version (.bin) V20N
Sorry for my English
Kraaz said:
I know russian very well.So i shortly translate all procedure done here.
They patched original 20A bin file , changing system recovery.img with clocworkmod recovery.img touch version.
Download 20A.bin extract it,and put somewhere in your computer.
and below there is a CWM flashable superuser.zip.
Download it and put to your Sd kart.Do not extract.
Then simply flash that patched 20A bin file with smart flash procedure posted here from radkor
http://forum.xda-developers.com/showthread.php?t=1448803
After finished flashing with smartflash tool go to cwm recovery and install superuser.zip
and you get rooted original 20A ginger.
Nice option for flashing and rooting
but we do not have 20N bin file yet.
we have only indian version 20B bin file, redpik posted it above
Click to expand...
Click to collapse
Ok. Let me try to understand this. They replace "system recovery.img" which is reside in the original rom bin file with "cwm recovery.img" (where to get this file?) and then flash it using smartflash tool. So after reset by smartflah, cwm is already in the phone installed. Then all is easy, proceed to install superuser.zip, etc..etc.zip.
How is it possible to obtain root by inserting cwm in the rom while cwm itself require root to run? Also, what's the "system recovery.img" that got replaced. Is it important?
Please investigate more. Need more info on how "patching" is done too. I don't understand russian.
Sent from my LG-P970 using XDA App
SnegovikRZN said:
Okey... Maybe, tomorrow I will be a version (.bin) V20N
Sorry for my English
Click to expand...
Click to collapse
Can you help to make one for v20b? The link post above by redpik contain bin file for v20b. If succeed, we're going to have the 1st v20b rooted. Hell yeah!
Sent from my LG-P970 using XDA App
adxgrave said:
Ok. Let me try to understand this. They replace "system recovery.img" which is reside in the original rom bin file with "cwm recovery.img" (where to get this file?) and then flash it using smartflash tool. So after reset by smartflah, cwm is already in the phone installed. Then all is easy, proceed to install superuser.zip, etc..etc.zip.
How is it possible to obtain root by inserting cwm in the rom while cwm itself require root to run? Also, what's the "system recovery.img" that got replaced. Is it important?
Please investigate more. Need more info on how "patching" is done too. I don't understand russian.
Sent from my LG-P970 using XDA App
Click to expand...
Click to collapse
I guess you need to investigate more how android works. Flashing recovery image with the whole system in a bin file makes cmw part of the "original" firmware so,like recovery that only can erase all this one can read/write in the system files. Sounds normal. I read on Samsung forums that they get root for latest versions by flashing a patched odin file and then a su zip. I will try it
Sent from my LG-P970 using XDA App
adxgrave said:
Can you help to make one for v20b? The link post above by redpik contain bin file for v20b. If succeed, we're going to have the 1st v20b rooted. Hell yeah!
Sent from my LG-P970 using XDA App
Click to expand...
Click to collapse
Since Telcel's v20a is is just out, its going to be pretty good news if it works.
mihaiolimpiu said:
Doesn't SmartFlash auto erases all user data (factory reset at first boot)?
Click to expand...
Click to collapse
Yes it does.
Redpik said:
I guess you need to investigate more how android works. Flashing recovery image with the whole system in a bin file makes cmw part of the "original" firmware so,like recovery that only can erase all this one can read/write in the system files. Sounds normal. I read on Samsung forums that they get root for latest versions by flashing a patched odin file and then a su zip. I will try it
Sent from my LG-P970 using XDA App
Click to expand...
Click to collapse
Then we can say that this is universal method as long as cwm can be patch into the rom. Finding exploit is not necessary anymore. So, what's the function of the file replaced in the rom. Is it the original lg recovery method which is not available anymore if this we use this method?
Thanks for the explanation, I wonder why it hasn't be use before, maybe because lack of rom file in bin format?
Edit: downloading rom in your link, pls post how to proceed if you get hold of it.
Sent from my LG-P970 using XDA App
adxgrave said:
Then we can say that this is universal method as long as cwm can be patch into the rom. Finding exploit is not necessary anymore. So, what's the function of the file replaced in the rom. Is it the original lg recovery method which is not available anymore if this we use this method?
Thanks for the explanation, I wonder why it hasn't be use before, maybe because lack of rom file in bin format?
Edit: downloading rom in your link, pls post how to proceed if you get hold of it.
Sent from my LG-P970 using XDA App
Click to expand...
Click to collapse
The problem is that we don;t know how to extract .bin files and modify the content. Just the first post has the good link I posted the stock v20B so he would patch it
Redpik said:
The problem is that we don;t know how to extract .bin files and modify the content. Just the first post has the good link I posted the stock v20B so he would patch it
Click to expand...
Click to collapse
to get the files out of a kdz: grab them while someone is using the KDZ program to update their phone. The files are extracted and put into "C:\ProgramData\LGMOBILEAX\Phone" but as soon as the program detects no phone the entire directory is blown away. Too fast to grab the files. So either you update for real (in which case you have the time to grab the files) or you create a symbolic link between the C:\ProgramData\LGMOBILEAX\Phone folder and another folder you create say name it C:\test. What happens is that files get extracted and then \phone folder deleted when no phone is detected but the files remain on the \test folder. So you get your files which are a "model.dll" file (in p970 case i guess something like lgp970.dll) and a .wdb file which is the firmware. How to proceed though to tinker further with the .wdb file so as to get bin file and baseband still elludes me
I bet our rom cooker knew how to unpack and repack. So, anyone?
Sent from my LG-P970 using XDA App
jimakos29 said:
to get the files out of a kdz: grab them while someone is using the KDZ program to update their phone. The files are extracted and put into "C:\ProgramData\LGMOBILEAX\Phone" but as soon as the program detects no phone the entire directory is blown away. Too fast to grab the files. So either you update for real (in which case you have the time to grab the files) or you create a symbolic link between the C:\ProgramData\LGMOBILEAX\Phone folder and another folder you create say name it C:\test. What happens is that files get extracted and then \phone folder deleted when no phone is detected but the files remain on the \test folder. So you get your files which are a "model.dll" file (in p970 case i guess something like lgp970.dll) and a .wdb file which is the firmware. How to proceed though to tinker further with the .wdb file so as to get bin file and baseband still elludes me
Click to expand...
Click to collapse
update: doing some research and it seems to extract the bin files you need lgutils and the .dll file you get from the kdz extraction but I am not at home to look into it any further.
Stable ROOT METHOD found!
You don't need this, disabling LG MODEM DEVICE under modems makes UNLOCKROOT work on every firmware! TESTED on 20N german version!
Disabling LG MODEM DEVICE under modems makes UNLOCKROOT work on every firmware! TESTED on 20N german version!
Here is the proof
http://forum.xda-developers.com/showpost.php?p=22195743&postcount=417
Here are the drivers I used:
http://forum.xda-developers.com/showpost.php?p=22196019&postcount=21
I used Windows 7 32 bit, the original poster used Win7 64 bit...
Hi!
Since xda-univeristy arised i thought it would be nice to learn something about green droid
I am going to learn about tweaking and theming:and here comes dozens of my questions:
1. I have downloaded Official ics repack by N00BY0815
2. I extracted it and i have:
2 folders ( META-INF and System)
2 files boot.ing and system.img
How can i extract this system.img ?
I tried to use 7zip but it says that" it cannot open it as archive"
Thanks in advance and please for leniency
it can be opened with Diskinternals Linux Reader. if not. use "sgs2toext4.jar" to convert it to .img.ext4 and then open it
Nihiliu said:
Hi!
Since xda-univeristy arised i thought it would be nice to learn something about green droid
I am going to learn about tweaking and theming:and here comes dozens of my questions:
1. I have downloaded Official ics repack by N00BY0815
2. I extracted it and i have:
2 folders ( META-INF and System)
2 files boot.ing and system.img
How can i extract this system.img ?
I tried to use 7zip but it says that" it cannot open it as archive"
Thanks in advance and please for leniency
Click to expand...
Click to collapse
Everything for theming is in the System folder. All the APK's(Applications) Boot.img is probably the recovery image it installs. But to theme you would need to decompile the apks in the system folder
Everythink was in system folder in gingerbread, in this system folder i have only app folder with su.apk and bin folder with su file.
So files i need are in system.img
@broodplank1337 thanks for help, program works well, now i can begin
But first only one question, now i can extract files, but can i pack them using same tool ?
Nihiliu said:
Everythink was in system folder in gingerbread, in this system folder i have only app folder with su.apk and bin folder with su file.
So files i need are in system.img
@broodplank1337 thanks for help, program works well, now i can begin
But first only one question, now i can extract files, but can i pack them using same tool ?
Click to expand...
Click to collapse
I don't know much about S2 but can't you just use 7zip to make it an archive and flash it through rrecovery?
"Anger and intolerance are the enemies of correct understanding." -Mahatma Gandhi
Nihiliu said:
How can i extract this system.img ?
Click to expand...
Click to collapse
Hi. You can use dsixda's Android Kitchen for that.
Nihiliu said:
Everythink was in system folder in gingerbread, in this system folder i have only app folder with su.apk and bin folder with su file.
So files i need are in system.img
@broodplank1337 thanks for help, program works well, now i can begin
But first only one question, now i can extract files, but can i pack them using same tool ?
Click to expand...
Click to collapse
You can pack them with the android kitchen, install the zip, then you do this in terminal emulator to make the system.img file:
Code:
su
cat proc/mounts
now look up the system partition, in my case it's mmcblk0p14
Code:
dd if=/dev/block/mmcblk0p14 of=/sdcard/system.img BS=4096
This will dump the system partition to system.img (for example when making an odin image)
Been looking around and I cannot get info(or I may have missed it) on how to convert system.sin to system.img.
The reason I want the system.img is I'd like to try deodexing my own JB(HKversion) stock rom.
how can I manage it in dsixda's kitchen, it says I need a system.img or either one of the following:
The format for each ROM must be one of the following:
- system.img + optional boot.img/lib.img (e.g. stock ROM or Nandroid)
- ZIP file for a custom ROM (e.g. update.zip)
- ZIP file containing *.img (e.g. stock rom.zip)
- ZIP file containing shipped ROM in SYSTEM + BOOT folder format
- Working folder made with this kitchen (e.g. WORKING_old_rom)
What I've already done so far was pulled out the system.sin from an FTF and made it system.ext4 in flashtool. And I also have extracted all the system files but I don't know how to go from here LoL.
Thanks in advance for any inputs guys.
Rycon33 said:
Been looking around and I cannot get info(or I may have missed it) on how to convert system.sin to system.img.
The reason I want the system.img is I'd like to try deodexing my own JB(HKversion) stock rom.
how can I manage it in dsixda's kitchen, it says I need a system.img or either one of the following:
The format for each ROM must be one of the following:
- system.img + optional boot.img/lib.img (e.g. stock ROM or Nandroid)
- ZIP file for a custom ROM (e.g. update.zip)
- ZIP file containing *.img (e.g. stock rom.zip)
- ZIP file containing shipped ROM in SYSTEM + BOOT folder format
- Working folder made with this kitchen (e.g. WORKING_old_rom)
What I've already done so far was pulled out the system.sin from an FTF and made it system.ext4 in flashtool. And I also have extracted all the system files but I don't know how to go from here LoL.
Thanks in advance for any inputs guys.
Click to expand...
Click to collapse
Just rename it.
That works if you want to use system.sin in dsixdas kitchen to make your own rom.
The instructions say to rename system.sin to system.img
PS, in fact you can just use system.sin, check in the first post for supported devices, it tlks about what to do for sony phones
gregbradley said:
Just rename it.
That works if you want to use system.sin in dsixdas kitchen to make your own rom.
The instructions say to rename system.sin to system.img
PS, in fact you can just use system.sin, check in the first post for supported devices, it tlks about what to do for sony phones
Click to expand...
Click to collapse
- If using stock FTF for kitchen:
1) Unzip FTF file, extract the system.sin
2) Dump system image from system.sin w/ Flashtool
(Advanced-> SIN Editor)
3) Rename dumped file to system.img
mate, I tried renaming it and put it on "original_update" folder but still the file cannot be detected I still cannot create a working folder and says
CREATE WORKING FOLDER FOR ROM
==============================
Ensure there is at least one ROM under the 'original_update' folder!
Select an option:
s - Show supported formats
x - Abort, don't create working folder
Or press Enter to continue
?
I also tried renaming the flashtool's dumped data(system.ext4) to system.img but still to no avail.
Any other way aside from system.img thing?
Rycon33 said:
- If using stock FTF for kitchen:
1) Unzip FTF file, extract the system.sin
2) Dump system image from system.sin w/ Flashtool
(Advanced-> SIN Editor)
3) Rename dumped file to system.img
mate, I tried renaming it and put it on "original_update" folder but still the file cannot be detected I still cannot create a working folder and says
CREATE WORKING FOLDER FOR ROM
==============================
Ensure there is at least one ROM under the 'original_update' folder!
Select an option:
s - Show supported formats
x - Abort, don't create working folder
Or press Enter to continue
?
I also tried renaming the flashtool's dumped data(system.ext4) to system.img but still to no avail.
Any other way aside from system.img thing?
Click to expand...
Click to collapse
wait, let me boot into linux and I will check
gregbradley said:
wait, let me boot into linux and I will check
Click to expand...
Click to collapse
mate, btw I'm only using cygwin in win7 if that matters on my issue
Rycon33 said:
mate, btw I'm only using cygwin in win7 if that matters on my issue
Click to expand...
Click to collapse
No, it doesnt matter, I did it with that setup, but its much easier with a ubuntu dual boot.
What you did should work.
Extract system.sin
Dump it with flash tool to get system.ext4, rename to system.img and put in original input folder.
then choose create working folder....
try it again,
gregbradley said:
No, it doesnt matter, I did it with that setup, but its much easier with a ubuntu dual boot.
What you did should work.
Extract system.sin
Dump it with flash tool to get system.ext4, rename to system.img and put in original input folder.
then choose create working folder....
try it again,
Click to expand...
Click to collapse
thanks mate, after I re-do the dump-data in flashtool, now system.img(renamed from system.ext4) can be detected
got another question again, just to confirm what's the API level? is it 16 for Android 4.1.2? coz I only see 4.1.1 for level 16
Rycon33 said:
thanks mate, after I re-do the dump-data in flashtool, now system.img(renamed from system.ext4) can be detected
got another question again, just to confirm what's the API level? is it 16 for Android 4.1.2? coz I only see 4.1.1 for level 16
Click to expand...
Click to collapse
if you have the latest version of everything it should be OK.
Just give it a go and see...
I used the same setup I have for my latest release as I did for my original ICS release, so the api level should be OK
EDIT
I do love your sig pic, where did you get it from? Or did you make it yourself?
gregbradley said:
if you have the latest version of everything it should be OK.
Just give it a go and see...
I used the same setup I have for my latest release as I did for my original ICS release, so the api level should be OK
EDIT
I do love your sig pic, where did you get it from? Or did you make it yourself?
Click to expand...
Click to collapse
with regards to my sig banner, i got it from one of the post from G+ last time, here's a copy of the actual file -> https://dl.dropbox.com/u/28587036/Android/Android_Evolution.jpg
ok I used 16, another question , what will I do to the one file that was never deodexed? it is the playstationcertified.odex
Could not deodex the following (you can try to deodex these files again):
playstationcertified.odex
A summary of the deodexing has been logged in deodex_040813_020606.log
71 *.odex files remain in system/app
1 *.odex files remain in system/framework
Rycon33 said:
with regards to my sig banner, i got it from one of the post from G+ last time, here's a copy of the actual file -> https://dl.dropbox.com/u/28587036/Android/Android_Evolution.jpg
ok I used 16, another question , what will I do to the one file that was never deodexed? it is the playstationcertified.odex
Could not deodex the following (you can try to deodex these files again):
playstationcertified.odex
A summary of the deodexing has been logged in deodex_040813_020606.log
71 *.odex files remain in system/app
1 *.odex files remain in system/framework
Click to expand...
Click to collapse
I have always just left it in for my releases, but seeing as I dont use it, i have personally deleted both the file and the odex file.
I think its the same for all stock based roms...there will be some aditional sony security on that file as it enables you to download sony play station games so the kitchen is not set up to integrate the odex file into the original one.
gregbradley said:
I have always just left it in for my releases, but seeing as I dont use it, i have personally deleted both the file and the odex file.
I think its the same for all stock based roms...there will be some aditional sony security on that file as it enables you to download sony play station games so the kitchen is not set up to integrate the odex file into the original one.
Click to expand...
Click to collapse
oh ok.
mate, apologies for many questions, this is my first try so I'm still confuse of many things
so after I de-odexed, what's next?
> ADVANCED OPTIONS
11 - De-odex files in your ROM
12 - Tools for boot image (unpack/re-pack/etc.)
13 - Add /data/app functionality
14 - Add /etc/init.d scripts support (busybox run-parts)
15 - Unpack data.img
16 - Sign APK or ZIP file(s)
17 - Convert update-script or updater-script
18 - Plugin scripts
99 - Build ROM from working folder
0 - BACK TO MAIN MENU
basically I only want a deodexed ROM and the CWM and root retained
Rycon33 said:
oh ok.
mate, apologies for many questions, this is my first try so I'm still confuse of many things
so after I de-odexed, what's next?
> ADVANCED OPTIONS
11 - De-odex files in your ROM
12 - Tools for boot image (unpack/re-pack/etc.)
13 - Add /data/app functionality
14 - Add /etc/init.d scripts support (busybox run-parts)
15 - Unpack data.img
16 - Sign APK or ZIP file(s)
17 - Convert update-script or updater-script
18 - Plugin scripts
99 - Build ROM from working folder
0 - BACK TO MAIN MENU
basically I only want a deodexed ROM and the CWM and root retained
Click to expand...
Click to collapse
What do you want to do?
You cant do (12) use championshipswimmers kernel kitchen for that.
But i do suggest adding 14, and rooting it (thats in the main menu)
also, zipalign apks...but it will ask you to do that when you compile it
Other than that its up to you. Just try some different options out and see what you think...thats the best way to learn, if you see my releases, the first two versions were not released because I was learning and playing around with it
Make sure though that you dont use the updater script it produces, its wrong for our phones.
"Borrow" one from a working ROM in our dev section, just ask permission first.
Rycon33 said:
thanks mate, after I re-do the dump-data in flashtool, now system.img(renamed from system.ext4) can be detected
got another question again, just to confirm what's the API level? is it 16 for Android 4.1.2? coz I only see 4.1.1 for level 16
Click to expand...
Click to collapse
For android 4.1.2 api must be set @16 othervise it wont boot
Sent from my LT29i using xda app-developers app
gregbradley said:
What do you want to do?
You cant do (12) use championshipswimmers kernel kitchen for that.
But i do suggest adding 14, and rooting it (thats in the main menu)
also, zipalign apks...but it will ask you to do that when you compile it
Other than that its up to you. Just try some different options out and see what you think...thats the best way to learn, if you see my releases, the first two versions were not released because I was learning and playing around with it
Make sure though that you dont use the updater script it produces, its wrong for our phones.
"Borrow" one from a working ROM in our dev section, just ask permission first.
Click to expand...
Click to collapse
asterix005 said:
For android 4.1.2 api must be set @16 othervise it wont boot
Sent from my LT29i using xda app-developers app
Click to expand...
Click to collapse
ok mates, thank you very much, I managed to de-odexed my stock ROM:good:
This is what I did. Using flashtool, I dumped my system.sin file to get a ext4 file. Then I open it with ext4 reader and extracted the contents. I then placed it in a folder called 'system' and proceed with the android kitchen.
Humans have evolved to be smarter, but there's one thing we can't get rid off. It's human stupidity.
If you still want to deodex playstationcertified.odex rename it to com.playstation.playstationcertified.odex.
That did the trick for me in earlier firmware versions.
Sent from my phone using XDA Premium
i try many times but it's all show this
CREATE WORKING FOLDER FOR ROM
==============================
Ensure there is at least one ROM under the 'original_update' folder!
Select an option:
s - Show supported formats
x - Abort, don't create working folder
Or press Enter to continue
any idea or should i press enter to continue?
i try with system.img from xperia TX rom 1.67
lucky92 said:
i try many times but it's all show this
CREATE WORKING FOLDER FOR ROM
==============================
Ensure there is at least one ROM under the 'original_update' folder!
Select an option:
s - Show supported formats
x - Abort, don't create working folder
Or press Enter to continue
any idea or should i press enter to continue?
i try with system.img from xperia TX rom 1.67
Click to expand...
Click to collapse
why don't you press it an see?
anyway, have you used flashtool to extract the system.sin into an ext4 extension yet?
gregbradley said:
why don't you press it an see?
anyway, have you used flashtool to extract the system.sin into an ext4 extension yet?
Click to expand...
Click to collapse
i tried extract thee system.sin into ext4 and rename it to sysmtem.img but no luck
update: after re-dump system.sin and press countinue, it's seem ok, maybe my fault.
Thank you anyway :laugh:
Sorry but I have another question, after i make a flashable zip and flash through CWM, it always stuck at Sony logo, any idea ?
I am a complete noob in phones and androids and crap.
I'm not sure what on earth this thing is, it is a .7z file and has a folder called system.
It has all the files in the system folder and even as build.prop.
Does anyone know what a .7z file is and what can I do with the file in it.
And also I'm not sure what a deodex is...
Do I copy and replace the whole system file in my xperia SP?
I got it off here: (First post, highlighted with (NEW!)
http://forum.xda-developers.com/showthread.php?t=2452139
Link to the .7z file that I'm curious with:
https://docs.google.com/file/d/0ByYxifSPiyiMVGNqZmsydWpJVFE/edit
nobu1106 said:
I am a complete noob in phones and androids and crap.
I'm not sure what on earth this thing is, it is a .7z file and has a folder called system.
It has all the files in the system folder and even as build.prop.
Does anyone know what a .7z file is and what can I do with the file in it.
And also I'm not sure what a deodex is...
Do I copy and replace the whole system file in my xperia SP?
I got it off here: (First post, highlighted with (NEW!)
http://forum.xda-developers.com/showthread.php?t=2452139
Link to the .7z file that I'm curious with:
https://docs.google.com/file/d/0ByYxifSPiyiMVGNqZmsydWpJVFE/edit
Click to expand...
Click to collapse
odex file means the system keep in a bundle... it does not allow adv custamization.. some mod flash need deoxed yr system first or u maybe end up in bootloop... u need to deodex yr firmware before flashing the file... check the android development for proper guide...
the file u posted does not need to deodex... but it always a good things to deodex first... cheers :laugh:
flash the bootanimation(720x1280).zip one... i think that one for our xsp
[Q&A] [Stock ROM] Easy Stock Reset | Many Versions | Stock ROM + Recovery + Radio In
Q&A for [Stock ROM] Easy Stock Reset | Many Versions | Stock ROM + Recovery + Radio Included
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [Stock ROM] Easy Stock Reset | Many Versions | Stock ROM + Recovery + Radio Included. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Can' t Flash
Every time I try to flash the Optus AU reset onto my VODAPHONE AU M7, it either gets stuck at 10% if i do it with a full wipe, or 0% if I don't. Also, it never passes and MD5 verification, after multiple separate downloads.
Anyone know what to do?
Thanks.
TWRP back up of stock rom and stock recovery OTA 6.11.980.12
Crushalot
I have a TWRP backup of stock rom from OTA 6.11.980.12 (Optus Australia) if you are interested I can pm the link to you along with the stock recovery that came with that OTA, for you to make (when you have time ect) an aroma reset tool for Optus Aussie users that is current and only just pre Android L release for sense roms.
Let me know if that would help
Australian Optus Firmware & Nand of stock rom Rom
Crushalot
In case the mood takes you, and you one day feel like making an easy aroma reset for Optus Aussie users that will reset HTC m7-ul PNO7400 devices back to a (only just) pre Android L update, here is a TWRP back up of stock rom (ota 6.11.980.12) Optus Australia as, well as the Optus Aussie OTA 6.11.980.12 (contains stock recovery) 2x OTA links originally posted by deevan
TWRP Nand of stock rom Android 4.4.3, from ota 6.11.980.12 (Australia Optus)
mega.co.nz/#!BhBXBaBT!Fjsg4FNe3AzUCR-aTdiNOwM71zx6-zzKkVbuY-rZqWk
GREAT work BTW! I used your tool to successfully return my device to stock (for the purposes of updating my firmware) worked like a charm!!
firmware.6.11.980.10.zip 43.1 MB (by deeevan)
mega.co.nz/#!QlIjzZoA!R18LEGCFJ85YV91rgiViohqw-QCzXO4fVEVm9h4ab68
firmware.6.11.980.12.zip 19.1 MB (By deeevan)
mega.co.nz/#!N4oS3aSZ!z2aM04WPtN2p1d9cWnmwkBi6UY_sNCbDB0ZBDAe 2RMY
Im still under 10 posts so I cant post full links.
This may help ppl go back to stock in time for the Android L OTA push!
GREAT work BTW! I used your tool to successfully return my device to stock (for the purposes of updating my firmware) worked like a charm!!
Joeisgood99 said:
Crushalot
I have a TWRP backup of stock rom from OTA 6.11.980.12 (Optus Australia) if you are interested I can pm the link to you along with the stock recovery that came with that OTA, for you to make (when you have time ect) an aroma reset tool for Optus Aussie users that is current and only just pre Android L release for sense roms.
Let me know if that would help
Click to expand...
Click to collapse
You can make that your self
You want to I can help you
It's easy
1st time with help of @crushalot I made 4 reset Rom for India version
Make TWRP backup of Rom which you want to make stock Rom reset zip
Install ubuntu open ubuntu
Extract backup file in ubuntu
You need system folder + data/preload folder + stock Recovery + boot.img + radio.img (all files from same version)
Extract any of old reset Rom zip
Replace files and folders from New one
Now edit aroma script in meta-inf folderwith notepad +
Edit details Rom version radio version etc
Zip all files and folders
It's ready
yatindroid said:
Install ubuntu open ubuntu
Extract backup file in ubuntu
Click to expand...
Click to collapse
If you want to use windows instead of linux, you can extract twrp backup using cygwin. All you need to do is to rename your backup files adding .tar extension then extract them using cygwin
Code:
tar -xvf your_file_name.ext4.win.tar
eg. If you want to extract system.ext4.win000, system.ext4.win001 and data.ext4.win, rename them system.ext4.win000.tar, system.ext4.win001.tar and data.ext4.win.tar. Move the system backup files to C:\Cygwin\Home\UserName\backup\System and data backup to C:\Cygwin\Home\UserName\backup\Data
open a cygwin command prompt and change directory to the correct location:
Code:
cd C:\Cygwin\Home\UserName\backup\System
then in cygwin command prompt:
Code:
tar -xvf system.ext4.win000.tar
tar -xvf system.ext4.win001.tar
Code:
cd C:\Cygwin\Home\UserName\backup\Data
tar -xvf data.ext4.win.tar
Then you have 2 folders, One System folder and one Data folder you can use to make you reset rom.
alray said:
If you want to use windows instead of linux, you can extract twrp backup using cygwin. All you need to do is to rename your backup files adding .tar extension then extract them using cygwin
Code:
tar -xvf your_file_name.ext4.win.tar
eg. If you want to extract system.ext4.win000, system.ext4.win001 and data.ext4.win, rename them system.ext4.win000.tar, system.ext4.win001.tar and data.ext4.win.tar. Move the system backup files to C:\Cygwin\Home\UserName\backup\System and data backup to C:\Cygwin\Home\UserName\backup\Data
open a cygwin command prompt and change directory to the correct location:
Code:
cd C:\Cygwin\Home\UserName\backup\System
then in cygwin command prompt:
Code:
tar system.ext4.win000.tar
tar system.ext4.win000.tar
Code:
cd C:\Cygwin\Home\UserName\backup\Data
tar data.ext4.win.tar
Then you have 2 folders, One System folder and one Data folder you can use to make you reset rom.
Click to expand...
Click to collapse
Yes sir, that's exactly the method i use :good:
Thank you So MUCH!
I'll try that as soon as I get a chance, and report back
Cheers for the help. ?
yatindroid said:
You can make that your self
You want to I can help you
It's easy
1st time with help of @crushalot I made 4 reset Rom for India version
Make TWRP backup of Rom which you want to make stock Rom reset zip
Install ubuntu open ubuntu
Extract backup file in ubuntu
You need system folder + data/preload folder + stock Recovery + boot.img + radio.img (all files from same version)
Extract any of old reset Rom zip
Replace files and folders from New one
Now edit aroma script in meta-inf folderwith notepad +
Edit details Rom version radio version etc
Zip all files and folders
It's ready
Click to expand...
Click to collapse
yatindroid said:
You can make that your self
You want to I can help you
It's easy
1st time with help of @crushalot I made 4 reset Rom for India version
Make TWRP backup of Rom which you want to make stock Rom reset zip
Install ubuntu open ubuntu
Extract backup file in ubuntu
You need system folder + data/preload folder + stock Recovery + boot.img + radio.img (all files from same version)
Extract any of old reset Rom zip
Replace files and folders from New one
Now edit aroma script in meta-inf folderwith notepad +
Edit details Rom version radio version etc
Zip all files and folders
It's ready
Click to expand...
Click to collapse
alray said:
If you want to use windows instead of linux, you can extract twrp backup using cygwin. All you need to do is to rename your backup files adding .tar extension then extract them using cygwin
Code:
tar -xvf your_file_name.ext4.win.tar
eg. If you want to extract system.ext4.win000, system.ext4.win001 and data.ext4.win, rename them system.ext4.win000.tar, system.ext4.win001.tar and data.ext4.win.tar. Move the system backup files to C:\Cygwin\Home\UserName\backup\System and data backup to C:\Cygwin\Home\UserName\backup\Data
open a cygwin command prompt and change directory to the correct location:
Code:
cd C:\Cygwin\Home\UserName\backup\System
then in cygwin command prompt:
Code:
tar system.ext4.win000.tar
tar system.ext4.win000.tar
Code:
cd C:\Cygwin\Home\UserName\backup\Data
tar data.ext4.win.tar
Then you have 2 folders, One System folder and one Data folder you can use to make you reset rom.
Click to expand...
Click to collapse
Thanks Mate.
I will try on Ubuntu first as I use that about 90%of the time. I'll reply with results hopefully tomorrow! Excited to make my own easy reset with aroma.
Had to unlock bootloader via HTC token when my phone is S-Off...
My HTC M7 UL (PID)PNO7400, was rooted and later S-Off with fire water.
I had custom rom and recovery ect. After 6 months of this I wanted to update my firmware but for various reasons didn't want to do it via RUU so I found and used crushalots Easy Recovery Reset Tool.
This worked perfectly.
During the aroma install I chose NOT to install any firmware, just stock recovery and rom.
I also chose not to keep root as I believed that I may not be able to install OTA updates with rooted stock. (right or wrong?)
Immediately after everything was installed I was running stock 2.24.980.2 rom and recovery on 4.20.980.x firmware.
After relocking my bootloader via fastboot, there was no issues, my phone just downloaded several OTA in a row, installed each without a hitch, and about an hour and a half later I had a stock phone with the latest 6.11.980.12 firmware and software, with S-Off.
(BTW re locking the bootloader did not delete any of my data.)
As soon as this was finished I wanted to re install my beloved eragon rom, re gain root, and get my phone back the way it was pre the firmware update.
Having S-Off I thought this would be easy (fastboot flash recovery path/to/custom/recovery.img)
Didn't work.
Unfortunately I didn't keep a copy of the error message I got in terminal, however, I didnt have write permissions on that particular partition. (apologies to anyone trying to help as I know details are important here)
This stumped me, as I have rooted 3 other (older) HTC desire by getting S-Off then flashing custom recovery.img, (These phones were running 1.44 version of fastboot as opposed to my M7s 1.57) I tried to un lock the bootloader via fastboot commands just in case that worked post S-Off ie (fastboot oem unlock) but that didn't work. Firewater doesn't install its own bootloader so locking and unlocking via the s-off tool were not an option either.
I had to re apply to HTC for an unlock token and flash that before I could flash a custom recovery. I plan go back to stock again for the purposes of taking carrier OTA when my carrier starts updating with Android L, so would like to know if this is normal, if not how I possibly stuffed up.
Can any one explain why I had to unlock bootloader via HTC site when my phone is S-Off?
I'm interested in peoples thoughts/knowledge
Many thanks
yatindroid said:
You can make that your self
You want to I can help you
It's easy
1st time with help of @crushalot I made 4 reset Rom for India version
Make TWRP backup of Rom which you want to make stock Rom reset zip
Install ubuntu open ubuntu
Extract backup file in ubuntu
You need system folder + data/preload folder + stock Recovery + boot.img + radio.img (all files from same version)
Extract any of old reset Rom zip
Replace files and folders from New one
Now edit aroma script in meta-inf folderwith notepad +
Edit details Rom version radio version etc
Zip all files and folders
It's ready
Click to expand...
Click to collapse
Hi Mate.
Thanks again. A little help needed.
When extracting the .rar from the TWRP recovery I made, using terminal command line [7z x /path/to/some.rar] in ubuntu i get 4300 of this type of error
can not open output file system/bin/mkswap
can not open output file system/bin/mkswap
can not open output file system/bin/readlink...ect
Basically at the end I get a system folder with about 3 items in it, as 7zip .rar tool cant decompress most of the files from the .rar
Right clicking on system.ext4.win.000 and system.ext4.win001 and selecting 'Extract files here' or 'open archive' results in error "could not open 'xx'. Archive type not supported."
Are you able to give me more detailed instructions on how to extract/unpack the system.ext4.win.000 and system.ext4.win001
Do I need to change the file name before extracting ?
Extracting the files from crushalots tool and extracting the files from the new TWRP then replacing relevant files and changing the manifest to reflect said change in Easy Recovery tool seems quite simple, however Im having trouble just extracting the files....
Im missing something obvious.
Thanks.
Joeisgood99 said:
Hi Mate.
Thanks again. A little help needed.
When extracting the .rar from the TWRP recovery I made, using terminal command line [7z x /path/to/some.rar] in ubuntu i get 4300 of this type of error
can not open output file system/bin/mkswap
can not open output file system/bin/mkswap
can not open output file system/bin/readlink...ect
Basically at the end I get a system folder with about 3 items in it, as 7zip .rar tool cant decompress most of the files from the .rar
Right clicking on system.ext4.win.000 and system.ext4.win001 and selecting 'Extract files here' or 'open archive' results in error "could not open 'xx'. Archive type not supported."
Are you able to give me more detailed instructions on how to extract/unpack the system.ext4.win.000 and system.ext4.win001
Do I need to change the file name before extracting ?
Extracting the files from crushalots tool and extracting the files from the new TWRP then replacing relevant files and changing the manifest to reflect said change in Easy Recovery tool seems quite simple, however Im having trouble just extracting the files....
Im missing something obvious.
Thanks.
Click to expand...
Click to collapse
I simply extract system.ext4.win000 file in Ubuntu nothing more needed not a single error
its tar not rar !
Whoops! . Tar.
Thanks again I'll keep trying.
Did crushalot send you any written instructions? Are they in a thread somewhere, or just basically what you already posted?
Thanks for your time.
Joeisgood99 said:
Whoops! . Tar.
Thanks again I'll keep trying.
Did crushalot send you any written instructions? Are they in a thread somewhere, or just basically what you already posted?
Thanks for your time.
Click to expand...
Click to collapse
I asked some questions via PM he just replied that
ask anything when you stuck
yatindroid said:
I asked some questions via PM he just replied that
ask anything when you stuck
Click to expand...
Click to collapse
For anyone else following this thread atm I solved the problem by re naming the system file extension in TWRP recovery from . win to . tar. In some TWRP back ups there were 2 system folders. A system.4ext000.win and system. 4ext001.win I just merged them during the extraction process.
Also there was no Data/preloaded folder in crushalots reset tool or in any twrp backup I have made.
Haven't tested the modified reset tool yet but will let u all know if I did it correctly!
Joeisgood99 said:
For anyone else following this thread atm I solved the problem by re naming the system file extension in TWRP recovery from . win to . tar.
Click to expand...
Click to collapse
Exactly, see post #6
In some TWRP back ups there were 2 system folders. A system.4ext000.win and system. 4ext001.win I just merged them during the extraction process.
Click to expand...
Click to collapse
Exactly, there are 2 system archive because of the file size restriction. Merging them after extracting the files is correct.
Also there was no Data/preloaded folder in crushalots reset tool or in any twrp backup I have made.
Click to expand...
Click to collapse
Without /data/preload, your reset rom will not be ota update ready. You don't have /data/preload in your backup probably because you have unlocked the bootloader and did the nandroid backup after (unlocking bootloader erase /data/preload)
Joeisgood99 said:
For anyone else following this thread atm I solved the problem by re naming the system file extension in TWRP recovery from . win to . tar. In some TWRP back ups there were 2 system folders. A system.4ext000.win and system. 4ext001.win I just merged them during the extraction process.
Also there was no Data/preloaded folder in crushalots reset tool or in any twrp backup I have made.
Haven't tested the modified reset tool yet but will let u all know if I did it correctly!
Click to expand...
Click to collapse
In Ubuntu install 7zip software
don't rename anything just open with archive manager
system.4ext000.win open this
crushalot tool not have data/preload because most of tool was 3.xx version sense 5.5 that time preload files included in system folder
yatindroid said:
In Ubuntu install 7zip software
don't rename anything just open with archive manager
system.4ext000.win open this
crushalot tool not have data/preload because most of tool was 3.xx version sense 5.5 that time preload files included in system folder
Click to expand...
Click to collapse
Thanks again yatindroid
I already have 7zip installed, However there is no option in archive manager to extract anything with it. After cd to file location I can view the . win file in terminal using [7z l file. win] but the [7z x file.win - d folder/i-want/extracted/to] command outputs the same error as stated in above post.
Q1) That aside the last step in this whole process is to zip it all up again as a . zip, so I'll be changing the file extension anyway, so does it matter if I change the file extension from . win to .tar for the purposes of extracting? If so ease explain why.
Q2) the ONLY place I have found a data/preload folder is inside a firmware .zip extracted from an OTA. It's definitely not in any TWRP back up. Did you leave that detail out of your initial instructions? Can you please tell me where to get the /preload folder from if not from the same OTA the recovery.img comes from.
Q3) do I put the data/preload folder inside the system folder of the reset tool or have it separate, along with radio.img, boot. img, recovery.img and aroma files ect.
Thanks for your time.
---------- Post added at 09:46 AM ---------- Previous post was at 09:33 AM ----------
alray said:
Exactly, see post #6
Exactly, there are 2 system archive because of the file size restriction. Merging them after extracting the files is correct.
Without /data/preload, your reset rom will not be ota update ready. You don't have /data/preload in your backup probably because you have unlocked the bootloader and did the nandroid backup after (unlocking bootloader erase /data/preload)
Click to expand...
Click to collapse
Thanks array.
I replied to the other post before yours came up. Forgive me if I ask similar questions.
I'm assuming I just copy the /preload folder from the same OTA I get the radio and recovery. img from.
Do I put the /preload folder inside any other folder within reset tool for a 6.xx version or have it beside the system folder and .img files.
Regards and Thanks.
Joeisgood99 said:
I'm assuming I just copy the /preload folder from the same OTA I get the radio and recovery. img from.
Click to expand...
Click to collapse
It should work. The data/preload folder from an ota zip usually (afaik this is true for the dev edition version) include all /data/preload files. If its the same thing for your version then you should be fine. In /data/preload you should have these files:
YOUR_CID.XML
All the weather animations (mp4 files)
some .png files for photo editing
htc preloaded app like flashlight.apk and calculator.apk. You might have more app depending your version.
Do I put the /preload folder inside any other folder within reset tool for a 6.xx version or have it beside the system folder and .img files.
Regards and Thanks.
Click to expand...
Click to collapse
the folder must be in your_reset_rom.zip/data/preload
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
alray said:
It should work. The data/preload folder from an ota zip usually (afaik this is true for the dev edition version) include all /data/preload files. If its the same thing for your version then you should be fine. In /data/preload you should have these files:
YOUR_CID.XML
All the weather animations (mp4 files)
some .png files for photo editing
htc preloaded app like flashlight.apk and calculator.apk. You might have more app depending your version.
the folder must be in your_reset_rom.zip/data/preload
Click to expand...
Click to collapse
Thanks for your excellent and timely reply.
More Qs.
I now have all folders as per your above post. I have taken data/preload, boot.img radio.img and recovery.img straight from OTA. 6.11.980.10
However my stock nand was of 6.11.980.12.
Q1) So do you know if having a system folder derived from a slightly newer version work? As far as I know the .12 OTA was a patch for the 'no voice during call' bug. OTA. 6.11.xxx. 12 did not contain a radio.img AND I can't get a data/preload folder for that ota as I can only find a 6.11.xxx.12 firmware. Not the whole OTA, which is why I reverted to making a . 980.10 reset tool despite having a slightly newer NAND.
Q2) I have edited the updater script in META-INF to reflect new radio and Android version ect. Do I need to update the MANIFEST. MF?
Hope that was clear enough to understand.
A big THANKS for your Help and time!