Database Develop

.Img file extracter

My default browser went foobar on me when i tried to go into the about menu.
Could someone upload the 2.1 apk and odex pls.
Thanks
EDIT: Changed the topic name to reflect the newly found utility that helped me recover my files since. I had no current backup and did not want to start from scratch. Figured it could help if you ever find yourself in that situation or want to extract files from other rom backup.

nm 10 chars

Unyaffs
Did some digging around and found a nice utility to extract the files from the .img. Extracted the system.img from the stock rom unpackaged it with unyaffs.
Here's the utility
Code:
Usage: unyaffs name_of_file.img
WARNING **This will extract all the files in the working directory**

[Root] on V20B_CIS&V20O_DEU

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...

[SOLVED]How to convert system.sin to system.img?

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 ?

[Q] Extract sytem.sin

I need some help, I don't seem to be able to extract the sytem.sin, then I get a gZ archive witch I can't open with 7zip, annyone has a method that works? or a ext4 extractor?

extract system.sin from archive, then use flashtool and option sin editor, it will make .ext4 file...and last step use ext2explore-2.1.65 and open ext4 file

ArmaNineTSeven said:
I need some help, I don't seem to be able to extract the sytem.sin, then I get a gZ archive witch I can't open with 7zip, annyone has a method that works? or a ext4 extractor?
Click to expand...
Click to collapse
as our friend said, the procedure is that easy, and that was complete, just for making your burdun a bit lighter, this is link for that explorer you need at the last step
wish you luck bro
http://sourceforge.net/projects/ext...xt2explore-2.1.65.zip/download?use_mirror=dfn

hoping to make a stock based rom for LT30p so we can keep the polished stock rom, with maybe some nexus look-a-like xp I'll see

No need for the ext2 explorer.
Once you have dumped the data in flash tool just use that ext4 file as the working file for your Rom in dsixdas kitchen
Sent whilst sat on the toilet.

I put the system.ext4 in the original update folder , but still get this: Ensure there is at least one ROM under the 'original_update' folder!

ArmaNineTSeven said:
I put the system.ext4 in the original update folder , but still get this: Ensure there is at least one ROM under the 'original_update' folder!
Click to expand...
Click to collapse
Make sure you read the instructions in the kitchen OP and post 2
Sony Xperia 2011-12 devices, specifically:
- TX, P, U, Sola
- Active, Arc, Arc S, Mini, Mini Pro, Neo, Neo V, Neo L,
Play, Ray (follow steps below):
- Can only build ROM without boot.img
- 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
- OR If using Nandroid backups: Rename system.yaffs2.img to system.img
- Use this system.img in kitchen's original_update folder
- WARNING - If using a ROM made from system.sin (not Nandroid), it
is recommended to flash from the temporary (fastboot) Clockwork
Recovery, rather than the regular Clockwork Recovery, otherwise
device may not boot (possibly because custom recovery files in
system folder are not added to ROM? e.g. recovery.tar).
Click to expand...
Click to collapse

[Q] Trying to restore stock firmware, aborted each time

Hey All, have google and googled for the past week but nothing specific to this issue I'm having.
I want to restore my stock firmware so I can get OTA updates! I didn't make any sort of backup when I began playing with different roms. I have htc_039 unbranded aus htc one. Bootloader has been unlocked with S-on and TWRP installed.
Downloaded Deevans/bugsys nandroid backup that matched my phone details (http://forum.xda-developers.com/showpost.php?p=41368105&postcount=375&nocache=1&z=2030115523399023) but there isn't any sort of instructions on installing these.
When i have tried to flash the rom I get "installation aborted" and when playing with fastboot it has given me messages that it cannot find certain .txt files (something like android.txt and a few other ones.
Could someone please tell me what im doing wrong or list the instructions to install this? I don't know if I have to lock the phone again, restore the recovery file first, no idea!!! Or is there anyway to turn the Android Revolution 12 image to get OTA (i dont think so)?
If you need any further phone info I will post.

Can anyone help with this?
When I try to flash the file in TWRP it starts and stops at "Updating partition Details".
What have i not setup right? Have been using these resources:
http://www.androidpolice.com/2010/0...nandroid-backup-and-clockworkmod-rom-manager/
http://www.addictivetips.com/mobile/how-to-perform-and-restore-a-nandroid-backup/
http://www.redmondpie.com/how-to-ba...android-using-clockworkmod-recovery-tutorial/
http://www.redmondpie.com/how-to-in...recovery-on-your-android-smartphone-tutorial/
http://androidteen.com/how-to-restore-htc-one-to-stock-firmware/#Nandroid
???

Hi,
I'm new to the htc one so not sure here but from what I understand and anyone please correct me if wrong - but if it's Deevans nandroid 1.29.980.2 (Australia unbranded) it's a CWM backup and I don't think they work in TWRP.
So think you would have to flash CWM, then flash "restore" nandroid from CWM or find a TWRP nandroid.
Also think you need s-off before you do ota as no way to gain s-off with revone on updated hboot 1.54 yet.
Hope this helps.

pjc21 said:
Hi,
I'm new to the htc one so not sure here but from what I understand and anyone please correct me if wrong - but if it's Deevans nandroid 1.29.980.2 (Australia unbranded) it's a CWM backup and I don't think they work in TWRP.
So think you would have to flash CWM, then flash nandroid from CWM or find a TWRP nandroid.
Also think you need s-off before you do ota as no way to gain s-off with revone on updated hboot 1.54 yet.
Hope this helps.
Click to expand...
Click to collapse
Thank for the reply
I have tried to install this with CWM which gave me those first missing ".txt" files. I will give it another go with CMW and post the results.
I will also S-OFF before doing the above.

Phone is now S-off and put CWM as the loader. Tried the zip file again and says:
Finding update package
Opening update package
Installing update...
Installation aborted.
I have also downloaded the file twice to confirm its not corrupted and it opens through winrar with no problems.
Any other suggestions?

jgt777 said:
Phone is now S-off and put CWM as the loader. Tried the zip file again and says:
Finding update package
Opening update package
Installing update...
Installation aborted.
I have also downloaded the file twice to confirm its not corrupted and it opens through winrar with no problems.
Any other suggestions?
Click to expand...
Click to collapse
I would try restore it like a backup, so unzip and put files in your CWM backup folder.
Not sure how CWM backup folder looks but in TWRP it's like /sdcard/TWRP/BACKUPS/... or /data/media/0/TWRP/BACKUPS/...
So I would try unzipping and copy files (boot, data, recovery, system) to /sdcard/CWM/BACKUPS/folder/put files in here - then boot to recovery and try "restore" option and browse to backup folder. You could probably copy the files to any folder on the sdcard and restore from recovery not sure.

pjc21 said:
I would try restore it like a backup, so unzip and put files in your CWM backup folder.
Not sure how CWM backup folder looks but in TWRP it's like /sdcard/TWRP/BACKUPS/... or /data/media/0/TWRP/BACKUPS/...
So I would try unzipping and copy files (boot, data, recovery, system) to /sdcard/CWM/BACKUPS/folder/put files in here - then boot to recovery and try "restore" option and browse to backup folder. You could probably copy the files to any folder on the sdcard and restore from recovery not sure.
Click to expand...
Click to collapse
Thanks for your suggestion and that was going to be my next question. The file I mentioned in the first post is x.xxx.xxx.zip (x as the numbers) and inside that zip is a folder with the same name x.xxx.xxx and inside that folder are all the files.
I tried putting the folder only in CMW but wont detect it, tried it with the .zip file and fails. Have now just put all the files into the folder and tried again with same failure.
There is a very long error in the recovery.txt file it made, don't know if its any use but the first line that pops out is:
Starting TWRP 2.6.0.1 on Fri Aug 2 06:23:49 2013
BOARD_HAS_NO_REAL_SDCARD
I put the file into this link if you know of anything, makes little sense to me. http://pastebin.com/Tvp2Qp2X

jgt777 said:
Thanks for your suggestion and that was going to be my next question. The file I mentioned in the first post is x.xxx.xxx.zip (x as the numbers) and inside that zip is a folder with the same name x.xxx.xxx and inside that folder are all the files.
I tried putting the folder only in CMW but wont detect it, tried it with the .zip file and fails. Have now just put all the files into the folder and tried again with same failure.
There is a very long error in the recovery.txt file it made, don't know if its any use but the first line that pops out is:
Starting TWRP 2.6.0.1 on Fri Aug 2 06:23:49 2013
BOARD_HAS_NO_REAL_SDCARD
I put the file into this link if you know of anything, makes little sense to me. http://pastebin.com/Tvp2Qp2X
Click to expand...
Click to collapse
Are you using TWRP recovery? or CWM recovery?

pjc21 said:
Are you using TWRP recovery? or CWM recovery?
Click to expand...
Click to collapse
I have now tried both TWRP and CWM and fails, also have installed ROM manager and another one I cant recall from play store. Also booted into recovery and went to the 'restore' option from the menu but cant find any directories..
I dont know if this has anything to do with it but noticed in the contents of the file:
ARCHIVE: cache.ext4.tar
ARCHIVE: data.ext4.tar
ARCHIVE: system.ext4.tar
boot.img
cache.ext4.tar.a
data.ext4.tar.a
nandroid.md5
recovery.img
recovery.log
system.ext4.tar.a
system..ext4.tar.b
Not to get ahead of myself but HTC ONE is ext2or 3 by default, its not something simple as having to change it to ext4? Its just something that stood out.

Just done google search on CWM backup location and seems to be /sdcard/clockworkmod/backup - so you could try copy the zip and/or files there and try restore from CWM recovery and see if that works.

pjc21 said:
Just done google search on CWM backup location and seems to be /sdcard/clockworkmod/backup - so you could try copy the zip and/or files there and try restore from CWM recovery and see if that works.
Click to expand...
Click to collapse
Interesting that there was no 'backup' folder inside that folder. Have created it and putting the files and zip in there now.
Was also googl'n and found this article:
http://miuiandroid.com/community/th...d-restore-error-while-restoring-sd-ext.15611/
Someone mentioned to now open the zip file when it downloads. I'll try your suggestions and this and let you know what happens tomorrow.
Thanks again

Morning,
Have downloaded the .zip file again twice and put it onto the SD and clockwork Mod backup folder and it has aborted again.
Any ideas on what to try from here?