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...
does anyone know if there is a apk file or something so i could flash the my files app on my cappy that usually come on the cappy with the official firmwares? i just need some kind of file to do that because i dont like astro and es file manager, etc. even a link to somewere where this has been done before would help, thanks.
I don't have an answer for you, just a recommended alternative in case you cannot find My Files.
I put Dual File Manager on every rom I try.
View attachment MyFiles.apk
here is
I promise nothing
ok mabye not, i meant a .tar file so i can flash with odin3
sorry about that
Why did you just open a new thread for that???
Take this apk and follow any of the ways i described in that thread....and in the future DON'T OPEN NEW THREADS FORE THE SAME THING!
sorry, then how do i do that with the apk file? like how do i make that a tar file or something to flash it with odin
Check your other thread...i listed 3 options.
ROM Tools v2
Version 2 BETA
v2b (Officially v2)
Linux Script
by iamareebjamal
Automated Android script for extracting boot.img and bml15 partition
My PC has issues so I can't use it to build mods and scripts, also, I have a very slow internet connection. That's why I don't upload my ROMs. Provided, I build EACH and EVERY one of my mod on my mobile, including those long scripts with repeating commands and making it easy for other guys to use, I could've just created a script with two commands which rendered error if used incorrectly, but I make it noob proof in every way possible so that there are minimum errors from your side and if something gets wrong, you know what it is. Even uploading 5 mb of mod makes it very difficult as I have to reupload if it fails. Writing scripts on mobile is not easy, you'll know if you have done it, it takes hours. Also, these colorful and easy guides are also made on mobile by writing BB codes ONE BY ONE by hand.
I am telling you because a person day before yesterday posted my Amazing Sounds Mod in another forum without my permission. However, he has removed it now. My work is fully open sourced for you to learn and make your own mods. But taking part of my work and posting as yours is not appreciated.
The MOST you can give me is love, prayers and Thanks
Click to expand...
Click to collapse
Out of the time I was absent from XDA(13 hours ) , I was searching for a method of extracting the kernel from your ROM
Imagine, you want to extract boot.img from your ROM but don't know what to do, you don't have internet to download the stock or custom kernel or simply want to extract it?
I did not find anything except the solution of Android Kitchen but what if you want to do it on your android?
As a bi product of this search, I got a lot of knowledge about the partitions used by Android system and the blocks that define them.
I also got basic knowledge about Linux Scripting.
So, I created this script that backs up your boot.img and bml15.img partitions.
boot.img - kernel of your device
bootextractorv2.sh - Backs up your kernel
bml15.img - IMEI partition
bml15extractorv2.sh - Backs up your IMEI partition
Note:- SGY Toolbox also backs up and restores bml15_EFS.img. And that also with a nice user interface, I just created this mod, because I wanted to but I recommend newbies to use SGY Toolbox for backing up IMEI
However, I found no tool able to backup the kernel, so it may be very useful for some members
ChangeLog
Code:
*More Interactive
*More Intelligent
*Added Option to create Odin Flashable Tar package for kernel
*More Convinient
Requirements :
Root Acess
Busybox
Android device
Hands
Terminal Emulator or Script Manager
(Script Manager recommended)
Instructions
Script Manager Method (Easy):-
1. Download Script Manager.
2.Download desired script and place it on sdcard.
3. Open Script Manager and enable browse as root.
4. Go to the downloaded script and click on the green android icon(root) in the pop up window.
5. Click on Run. Follow Instructions and enjoy
Terminal Emulator Method (Hard):
1. Download Terminal Emulator.
2. Download desired script and place it in the root of the sdcard.
(You can place it anywhere else but the directory should not have spaces and you will have to change the commands accordingly)
3. Open Terminal Emulator and type (After every command you have to press enter)
Code:
su
And Grant Root Access
Then, type
Code:
sh /sdcard/bootextractorv2.sh
or
Code:
sh /sdcard/bml15extractorv2.sh
according to the the script you want to run
4. Now, follow the instructions on screen and enjoy
Download bootextractorv2.sh
Download bml15extractorv2.sh
Credits :
Miscellaneous Google search posts showing how to write Linux Script
Me for writing the script
Rafael.Baugis for source
Ryuinferno for guide
Reserved
I'll test on S5830 and report asap
edit: Script wouldn't run on S5830 with script manager. With terminal emulator it dumps an empty boot.img
daxanh said:
I'll test on S5830 and report asap
edit: Script wouldn't run on S5830 with script manager. With terminal emulator it dumps an empty boot.img
Click to expand...
Click to collapse
kernel partition of s5830 is different
Give me the Partition
And I will make the mod
V2 completed
Uploading ASAP
OP Updated
v2 released
nice work man...thaks a lot
Sent from my GT-S5830i using xda app-developers app
He didn't really mean the love and prayers.
Nabs Zains said:
He didn't really mean the love and prayers.
Click to expand...
Click to collapse
lol
ROFL
You disclosed my secret Nabs
:good: simple & important... all ace_i owner should get this before 'cooking' ur device...
nice tool for kernel backup... :good:
Doesn't work for me, S5830i stock firmware. If I use script manager method, a lot of "not found" messages, and finally the boot folder is empty. I give script manager root permission. And if I use a terminal emulator, the same error messages, finally there is a 5MB boot.img file, but "untouchable". I can not copy in any other folder. If I connect to PC, boot.img is missing. Appears again in the mobile when I disconnet the USB. I can not change file permissions with root explorer....
Also when the script ask if I want to create a zip file for recovery, I select 1 and I get "bad integer, run again"
Thank you
puntillero said:
Doesn't work for me, S5830i stock firmware. If I use script manager method, a lot of "not found" messages, and finally the boot folder is empty. I give script manager root permission. And if I use a terminal emulator, the same error messages, finally there is a 5MB boot.img file, but "untouchable". I can not copy in any other folder. If I connect to PC, boot.img is missing. Appears again in the mobile when I disconnet the USB. I can not change file permissions with root explorer....
Also when the script ask if I want to create a zip file for recovery, I select 1 and I get "bad integer, run again"
Thank you
Click to expand...
Click to collapse
You have busybox?
If no,
You can't run it
Yes, and the script founds it (it says). Finally I zipped boot.img with root explorer and that zip file could be copied to the PC. Guess the file is ok. Thanks.
puntillero said:
Yes, and the script founds it (it says). Finally I zipped boot.img with root explorer and that zip file could be copied to the PC. Guess the file is ok. Thanks.
Click to expand...
Click to collapse
Why you zipped it?
English is not my language. I explained that boot.img was untouchable. I tried to copy to computer and I always got writing errors. Rebooting wasn't useful. Permissions couldn't be changed with root explorer.. The file was there, but couldn't do anything with It. Tried to zip it and it worked, and I copied the zip to my computer..
puntillero said:
English is not my language. I explained that boot.img was untouchable. I tried to copy to computer and I always got writing errors. Rebooting wasn't useful. Permissions couldn't be changed with root explorer.. The file was there, but couldn't do anything with It. Tried to zip it and it worked, and I copied the zip to my computer..
Click to expand...
Click to collapse
Sure that there is problem in busybox applet sync
I don't know why script couldn't detect it
I don't know what the problem was. I installed, not without many problems, the last busybox available, and everything worked ok. Out of curiosity, I compared boot.img file extracted with "problems" and the boot.img extracted now cleanly, and are identical.
Regards
[Q] IMEI backup work on GT-S5570 Galaxy Mini???
Sent from East Borneo Isand use Honey Bear's Phone
S5570 has another partition table
So no
Sent from my GT-I9100 using muffin premium
I found this site on how to root my Touchpad:
http://forum.xda-developers.com/showthread.php?t=1390829
and this one on how to install CM onto it:
http://chrisbryson.blogspot.com/2013/09/how-to-install-android-on-hp-touchpad.html
But nothing mentions when/how to install CWM (or one of the ones listed below) as shown on the CM nightly page found below
-PhilZ Clockworkmod 6.0.4.7 (non-touch)(will backup and restore in both cwm and twrp format)
-Milaq's ClockworkMod 6.0.5.4
-Flintman's TWRP
http://forum.xda-developers.com/showthread.php?t=2592909
At what place would I flash the Recovery?
To install android you will create a folder on the touchpad called cminstall.
This folder contains the three files needed to install android - moboot, cwm and whichever version of android you prefer. Optionally you can flash gapps from this folder too.
There are much better tutorials on the web and this site than the ones you quote - the first is irrelevant to installng android, and there are better ones here on xda than the second.
Also the recoveries you mention are for installing kitkat which requires repartitioning of the file system. Prob best to stick to JB for now
Cheers
chris5s said:
To install android you will create a folder on the touchpad called cminstall.
This folder contains the three files needed to install android - moboot, cwm and whichever version of android you prefer. Optionally you can flash gapps from this folder too.
There are much better tutorials on the web and this site than the ones you quote - the first is irrelevant to installng android, and there are better ones here on xda than the second.
Also the recoveries you mention are for installing kitkat which requires repartitioning of the file system. Prob best to stick to JB for now
Cheers
Click to expand...
Click to collapse
I found a tutorial here:
http://forum.xda-developers.com/showthread.php?t=2147284
But when I attempt to extract the Acme Installer - I downloaded ACMEInstaller5M - but when I try to extract with 7Zip to the Nova Directory it keeps giving me an error?
You don't need to extract the acmeinstaller file, just place it in Program Files/Palm, Inc, open up a terminal window and enter in the command to run it.
Of course, you do this after you have set up your cminstall folder on the touchpad.
A word of advice - I find it useful to have 2 copies of the rom you want to flash - one in the cminstall folder, and one in the root folder of the touchpad. This is because sometimes the flashing process with acme can be a bit funny, and it automatically deletes the files in cminstall once its done. I've flashed a couple of touchpads with acme and Android hasn't installed properly, so having a backup somewhere else on the touchpad is useful.
Cheers
jo15765 said:
I found a tutorial here:
http://forum.xda-developers.com/showthread.php?t=2147284
But when I attempt to extract the Acme Installer - I downloaded ACMEInstaller5M - but when I try to extract with 7Zip to the Nova Directory it keeps giving me an error?
Click to expand...
Click to collapse
It's been awhile since I have had to use acme but I believe it is a jar file so either use a different browser to download or change the file extension from (.zip to .jar).
Unfortunately I am not at my PC but can check later if someone else is unable to confirm this.
sstar said:
It's been awhile since I have had to use acme but I believe it is a jar file so either use a different browser to download or change the file extension from (.zip to .jar).
Unfortunately I am not at my PC but can check later if someone else is unable to confirm this.
Click to expand...
Click to collapse
Its not a .jar or .zip, use as is...
Cheers
Hello, I think this would be the right subforum to post this thread but if it ain't feel free to move it where it belongs.
I'm helping out a friend which has an S5570I. His phone used to work but all of a sudden it didn't so he downloaded Odin and started to do god knows what with it following a YouTube video until it failed. End result: the phone seems to be soft-bricked.
In essence if started normally it would stay put in the Samsung logo, recovery can be accessed and the download mode apparently too. It was too bad this morning when I didn't see a procedure detailed here to (try to) restore the phone, so I'll try that when I have the chance.
Before knowing that it was bricked I was downloading the stuff necessary for a reflash, the questions I have are related to the firmware for the device.
I looked for the right firmware for it: matching model number and latest version matching current customization (just in case) which happens to be Movistar (Spain). I downloaded an archive with the firmware. Then I downloaded the latest version I could find of Odin (4.43 although I have 4.38 and 4.42 around here as well) and an OPS file for the model (named TASS_v1.0.ops).
So doing a dry-test here (without the actual phone) I did the following:
- Opened Odin (4.38 and later 4.43).
- Selected the OPS file.
- Checked the "One Package" option.
- Selected the tar.md5 file in the proper section.
And that's where Odin crashed, so at first I though "OK... bad firmware image?". I went on and downloaded a different one, customized for Spain as well but without any operator branding specifics; only to arrive at the same result. So the thing should be the image unless that other one was corrupted as well...
I started researching about that "tar.md5" format and it seems it should be a tar file (in ustar format) with the results of an md5sum execution appended to it.
Examining any of the firmware files I have through an hex editor I saw the output of the md5sum program in the end, which was expected, but then what should be a tar archive didn't seem to be (or I don't recognize its format). There is no magic number at 0x101, and the "file" utility in Linux recognizes the files as data instead or tar archives.
I'd like to know if anyone knows something about this, if there's anything wrong with the firmware or if those files were created in different way. I'd like to convert them to the appropriate format to use with Odin once/if the phone is debricked.
Thanks everyone for the time dedicated to at least read all this .
PS. I uploaded the files I have here to a hosting place so that you may download them if you wish to help out, here are the links (add https:// before the link because I don't seem to be allowed to post links just jet):
(S5570IBGMB2_S5570IXECMB1_XEC in SamMobile)
Link: copy.com/poYZ64CZLLvU
(S5570IXXMC1_S5570IOXXLK3_PHE in SamMobile)
Link: copy.com/onfqEYD3rQlw
PPS. By the way, how should I detect the phone when connected in download mode in the device manager? I'm unsure of what to look for there.