Related
Hi,
I just spent the past 3 hours downloading Rodriguez' MIUI mod on my computer because my connection is so slow. I usually download ROMS straight from my phone.
This time however, about an hour in, I realised that OSX Safari will unzip the ROM as soon as it finishes downloading automatically. I got into Preferences>General and change that setting, but it seems as though it didn't come into effect because I changed the setting whilst the download was in progress.
Anyway, is there any other way I can compress the ROM (which is now a folder) through any terminal commands either on the phone or on the computer?
I've already tried compressing it normally like any other folder with MM's Gingerbread ROM I downloaded yesterday. When I flashed it, I bootlooped so....
Oh and I can't download it again. I'm on the brink of going over my bandwidth allowance.
Thanks!
Well, You can use WinRAR like application for MAC (I Don't use OS X) so cant specify.
Select all the files and compress it to zip! Done!
Donate to me by clicking the Thanks if I helped you!
In theory, it would just be to compress it normally with the use of any archiver program which compresses to a .zip file. Not too familiar with OS X, so I cannot guide you into what program you'll need and how to do.
You need to re-compress the ROM files and sign the ZIP.
Jack_R1 said:
You need to re-compress the ROM files and sign the ZIP.
Click to expand...
Click to collapse
Forge94 said:
I've already tried compressing it normally like any other folder with MM's Gingerbread ROM I downloaded yesterday. When I flashed it, I
bootlooped so....
Click to expand...
Click to collapse
i think the issue is signing... Can someone tell us how to sign a rom on osx?
rassawyer said:
i think the issue is signing... Can someone tell us how to sign a rom on osx?
Click to expand...
Click to collapse
Signapk? But i think signing a rom is not neccesary anymore... Just turn off signature verification in recovery or use 4ext
I have had the same situation. Safari extracted the file automatically.
After waiting for 3 hours until the download completed, because the website is restricting my download speed to 100 kb/s.
I tried zipping and compressing the file both by a Windows system and a Mac. IT DID NOT WORK.
I have to download the file again.
Hey there =)
I'm a proud owner of a Optimus 2x. I've rooted my phone and flashed the "stock rom" ( From this topic) and downloaded 2 Custom ROMs ( Thisone and another one from a dutch forum).
However, when I go to CWM and do a Backup and complete wipe, when I wan't to flash the rom (as said how to do it in the topics) I get things like this:
"Finding udate package. . .
Opening update package. . .
E:Can't open /sdcard/update.zip (bad)
Toggle signature verification: on/off
Toggle script asserts: on/off
I tried all possible options.
When I got the signature verification ON, then CWM says the signature is not verified
I worked with both V10A and V10B, both don’t work
What do I do wrong?
Killastyle said:
Hey there =)
I'm a proud owner of a Optimus 2x. I've rooted my phone and flashed the "stock rom" ( From this topic) and downloaded 2 Custom ROMs ( Thisone and another one from a dutch forum).
However, when I go to CWM and do a Backup and complete wipe, when I wan't to flash the rom (as said how to do it in the topics) I get things like this:
"Finding udate package. . .
Opening update package. . .
E:Can't open /sdcard/update.zip (bad)
Toggle signature verification: on/off
Toggle script asserts: on/off
I tried all possible options.
When I got the signature verification ON, then CWM says the signature is not verified
I worked with both V10A and V10B, both don’t work
What do I do wrong?
Click to expand...
Click to collapse
Try to select zip file from SD Card. If you have renamed the ROM to update.zip this should work fine, if that's the case the update.zip is corrupted.
I’ve already tried that to, doesn’t work. I suppose that a ‘’physical’’ MicroSD means one you can touch, so a real one (I got one and placed the ROMs on the MicroSD). I also tried making the .zip files a ‘’Read Only’’. I just keep getting the same screen that it doesn’t work.
And is there also a difference between a NANDROID backup and the backup I do in CWM?
Killastyle said:
I’ve already tried that to, doesn’t work. I suppose that a ‘’physical’’ MicroSD means one you can touch, so a real one (I got one and placed the ROMs on the MicroSD). I also tried making the .zip files a ‘’Read Only’’. I just keep getting the same screen that it doesn’t work.
And is there also a difference between a NANDROID backup and the backup I do in CWM?
Click to expand...
Click to collapse
Yes, you need a physical SD card. See if it gets mounted in CWM. Nandroid backup is the backup you do from the backup/restore menu in CWM.
If you keep getting the same screen you have not selected the zip file that contains the ROM. Your CWM is looking for update.zip that should reside on the root of your physical SD card. If you select choose zip you can navigate to the rom zip file you downloaded.
How can I check if it gets mounted in CWM? I can find the update.zip (I renamed the zip file myself to update.zip) When I check in Astro I go to "sdcard/_ExternalSD" and there is on the root of the external SD the update.zip package..
However, I've done a backup back to the standard rom and now I see the LGE-Version is back to LGP990-V10a. Here are all my specs:
Basebandversion: 1035.21_20110223
Kernel: 2.6.32.9
Buildnumber: FRG83G
LGE: LGP990-V10a .
Can you maybe explain to me step by step how I can do a custom rom again? I think I have to start from scratch again?
Killastyle said:
How can I check if it gets mounted in CWM? I can find the update.zip (I renamed the zip file myself to update.zip) When I check in Astro I go to "sdcard/_ExternalSD" and there is on the root of the external SD the update.zip package..
However, I've done a backup back to the standard rom and now I see the LGE-Version is back to LGP990-V10a. Here are all my specs:
Basebandversion: 1035.21_20110223
Kernel: 2.6.32.9
Buildnumber: FRG83G
LGE: LGP990-V10a .
Can you maybe explain to me step by step how I can do a custom rom again? I think I have to start from scratch again?
Click to expand...
Click to collapse
First off, if you install MCR Fr12 then go and update your baseband to the newest one. Follow these instructions: http://forum.xda-developers.com/showthread.php?t=1008070
Download the MCR Fr12 again to ensure that it's not corrupted, check the MD5 of the zipfile and compare it with the one stated in the first post.
Put the zipfile on the external SD card, no need to rename it.
Reboot into CWM, and (not having my phone here, so maybe I don't remember the exact phrases) advanced menu/toggle signature check off and wipe all data (cache/user/dalvik)
install zip from SD card (not apply update.zip) and navigate to the downloaded rom and press power to select it. This should install MCR Fr12 without problems.
Hope it helps.
Edit: Are you able to browse the SD from CWM ? If not try formatting the SD card in your PC as FAT(32).
I haven't done it this way before, so I'm gonna check it out
And I think I'm able to browse the SD from CWM, because when I do ''Install zip from SD card" i can navigate trough the maps I created and the update file is on the root. I will try this asap ! I hope this works thx
edit: How can I check the MD5 of the zipfile?
The: E:Can't open /sdcard/update.zip (bad)
can refer to a corrupted update.zip so try and download it again
Tayutama said:
The: E:Can't open /sdcard/update.zip (bad)
can refer to a corrupted update.zip so try and download it again
Click to expand...
Click to collapse
+1
Had this error many times on my old Hero
Tayutama said:
The: E:Can't open /sdcard/update.zip (bad)
can refer to a corrupted update.zip so try and download it again
Click to expand...
Click to collapse
So that means that all the 4 different times I downloaded the file it has gone corrupted?
Killastyle said:
So that means that all the 4 different times I downloaded the file it has gone corropted?
How can I check the MD5 files?
Click to expand...
Click to collapse
Maybe
Try searching for winMd5SumPortable, nice tool to check MD5 sums.
Killastyle said:
So that means that all the 4 different times I downloaded the file it has gone corropted?
How can I check the MD5 files?
Click to expand...
Click to collapse
Well it might refer to a corrupted download
What is the size of the file after you downloaded it?
Also regarding checking MD5 i use a program called HashTab.
It's a a small program that adds a tab when you check a files properties.
EDIT: also that error can also just be it looks for a file called update.zip but can't find it.
In windows you might see the file as update.zip but in reality it's called update.zip.zip and that also courses that error.
If you haven't renamed it, then choose install zip from SD card instead of install update.zip in CWM and then select the file
And still it doesn't work. I've checked the MDA on the file where I downloaded it to, then it's correct. However, as soon as I copy/paste or cut/paste the file to my MicroSD root, the MDA doesn't match anymore. Can that be the reason?
I might have the solution. When I do a full wipe via CWM, the base version goes back to V10a, maybe that is the solution. I will download the file directly to the MicroSD right now. I let you guys know if its working
Edit: omfg, I found out, I think it's working right now. I formatted and mounted the MicroSD via CWM, copied the file to the MicroSD and the MD5 was now still the same. Right at this moment my phone is writing it to the system. So it was probably the MicroSD not correctly formatted or such... Thx for all the help guys
Killastyle said:
I might have the solution. When I do a full wipe via CWM, the base version goes back to V10a, maybe that is the solution. I will download the file directly to the MicroSD right now. I let you guys know if its working
Edit: omfg, I found out, I think it's working right now. I formatted and mounted the MicroSD via CWM, copied the file to the MicroSD and the MD5 was now still the same. Right at this moment my phone is writing it to the system. So it was probably the MicroSD not correctly formatted or such... Thx for all the help guys
Click to expand...
Click to collapse
is there any update to this i also get this kind of error/
Hi All,
I'm relatively new to Android (had the Nexus 7 for about a year). My questions is this:
I have 4.2.2 currently loaded. When I orinally got the nexus 7, I used a toolkit to unlock the bootloader and root the device, so I could install SixAxis and a few other apps that required root.
What is the easiest way for me to now update to 4.3? Will the OTA update that is bound to show up on the device shortly work?
BTW This is the WiFi only Nexus 7, 16 GB and my main PC at home is a Mac.
Thanks.
Foxman2k said:
Hi All,
I'm relatively new to Android (had the Nexus 7 for about a year). My questions is this:
I have 4.2.2 currently loaded. When I orinally got the nexus 7, I used a toolkit to unlock the bootloader and root the device, so I could install SixAxis and a few other apps that required root.
What is the easiest way for me to now update to 4.3? Will the OTA update that is bound to show up on the device shortly work?
BTW This is the WiFi only Nexus 7, 16 GB and my main PC at home is a Mac.
Thanks.
Click to expand...
Click to collapse
Get it locked and unrooted to get OTA possiblt easiest way.
Otherwise flash the factory images:thumbup:
Sent using Nexus 7
basuraunak said:
Get it locked and unrooted to get OTA possiblt easiest way.
Otherwise flash the factory images:thumbup:
Sent using Nexus 7
Click to expand...
Click to collapse
Do you have a link of a guide that I could follow on how to flash the factory image?
Can I download the zip and then use the clockwork recovery i have installed to load the zip?
I don't think that having the bootloader locked or unlocked will really affect the OTA..
Am I right or am I right?
Foxman2k said:
Do you have a link of a guide that I could follow on how to flash the factory image?
Can I download the zip and then use the clockwork recovery i have installed to load the zip?
Click to expand...
Click to collapse
Just use wug's toolkit. Its over in the android development in the n7 section...
---------- Post added at 10:04 AM ---------- Previous post was at 10:00 AM ----------
drake90001 said:
I don't think that having the bootloader locked or unlocked will really affect the OTA..
Am I right or am I right?
Click to expand...
Click to collapse
I dont think having it unlocked will effect the ota (it hasnt in the past for me), but it sounded like he wanted to flash the factory image. I actually have a nandroid of it on my unlocked n7. Gonna flash the official and see if I can get the ota later...
I've taken OTAs no problem on an unlocked, rooted device with TWRP recovery. So you're fine.
Sent from my Nexus 7 using Tapatalk 4 Beta
Here you go for flashable zip :
http://forum.xda-developers.com/showthread.php?t=2376522
Sent from my Nexus 7 using xda premium
So I downloaded what I believe to be the right file, ab67ca07c4b2e03eca795ada10ff041b77fbb7bf.signed-nakasi-JWR66V-from-JDQ39.ab67ca07 (1).zip.
I then reboot my nexus 7 into clockworkmod revovery and select install zip, choose zip from sdcard, browse to the aboev file but then get an error:
It ends in (Status 7) Installation aborted.
What am I missing?
Also, just tried via adb sideload and that didn't work either.
Foxman2k said:
So I downloaded what I believe to be the right file, ab67ca07c4b2e03eca795ada10ff041b77fbb7bf.signed-nakasi-JWR66V-from-JDQ39.ab67ca07 (1).zip.
I then reboot my nexus 7 into clockworkmod revovery and select install zip, choose zip from sdcard, browse to the aboev file but then get an error:
It ends in (Status 7) Installation aborted.
What am I missing?
Click to expand...
Click to collapse
Did you install the aosp browser and rename the default browser apk and odex files or modify the buildprop file? Those must be as original to take the update. Also, you should have gotten a message about what failed when you get the Status 7 error. What else did it say?
Groid said:
Did you install the aosp browser and rename the default browser apk and odex files or modify the buildprop file? Those must be as original to take the update. Also, you should have gotten a message about what failed when you get the Status 7 error. What else did it say?
Click to expand...
Click to collapse
No to all of the above. I don't know what odex files or buildprop file would refer to, so I defintely haven't modified them.
It says:
Warning: No file_contextsVerifying current system...
assert failed: apply_patch_check("/system/bin/debuggerd", "a whole bunch of letters and numbers", "a whole bunch of letters and numbers")
E:Error in /sdcard/0/update rom/ab67ca07c4b2e03eca795ada10ff041b77fbb7bf.signed-nakasi - JWR66V - from - JDFQ39.ab67ca07 (1).zip
(Status 7)
Installation aborted.
Groid said:
Did you install the aosp browser and rename the default browser apk and odex files or modify the buildprop file? Those must be as original to take the update. Also, you should have gotten a message about what failed when you get the Status 7 error. What else did it say?
Click to expand...
Click to collapse
Foxman2k said:
No to all of the above. I don't know what odex files or buildprop file would refer to, so I defintely haven't modified them.
It says:
Warning: No file_contextsVerifying current system...
assert failed: apply_patch_check("/system/bin/debuggerd", "a whole bunch of letters and numbers", "a whole bunch of letters and numbers")
E:Error in /sdcard/0/update rom/ab67ca07c4b2e03eca795ada10ff041b77fbb7bf.signed-nakasi - JWR66V - from - JDFQ39.ab67ca07 (1).zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
Does it make a difference that my current build number in "about tablet" shows as JDQ39 and not JDFQ39 as above?
The problem file is 'debuggerd' in the /system/bin folder as it says in the error message. I had the same issue previously on the last N7 update. I had to get the original file from someone since the file had been replaced by another app (possibly Stickmount) or it can be extracted from the previous update to 4.2.2. I don't know about the JDFQ39 compared to the download file showing JDQ39, but that is the same file I downloaded. The (1).zip means you had previously downloaded the file and this is an additional d/l. That shouldn't be a problem, but you can delete the (1) if you want.
I'll try flashing through CWM and let you know if mine worked. If so, I can send you the right 'debuggerd' file.
Groid said:
The problem file is 'debuggerd' in the /system/bin folder as it says in the error message. I had the same issue previously on the last N7 update. I had to get the original file from someone since the file had been replaced by another app (possibly Stickmount) or it can be extracted from the previous update to 4.2.2. I don't know about the JDFQ39 compared to the download file showing JDQ39, but that is the same file I downloaded. The (1).zip means you had previously downloaded the file and this is an additional d/l. That shouldn't be a problem, but you can delete the (1) if you want.
I'll try flashing through CWM and let you know if mine worked. If so, I can send you the right 'debuggerd' file.
Click to expand...
Click to collapse
Ok great. I do have stickmount installed...
Well, I got the debuggerd error also. I'll try the backup debuggered file I used in the last update. Otherwise, I'll have to find the debuggerd file from 4.2.2. Any help out there?
Groid said:
Well, I got the debuggerd error also. I'll try the backup debuggered file I used in the last update. Otherwise, I'll have to find the debuggerd file from 4.2.2. Any help out there?
Click to expand...
Click to collapse
Glad I'm not alone lol
Still no joy. I think someone will have to get the right debuggerd file and get it to one us on a pm or email. Also, I noticed on my update try that the file was listed as JDQ39. ... and not the JDFQ39. ... that you saw.
Groid said:
Still no joy. I think someone will have to get the right debuggerd file and get it to one us on a pm or email. Also, I noticed on my update try that the file was listed as JDQ39. ... and not the JDFQ39. ... that you saw.
Click to expand...
Click to collapse
once we get the file, how do I replace the file with the debuggerd that is currently on the nexus?
What I will do is to copy the debuggerd file to the N7 internal storage root folder from my pc. Then I will rename /system/bin/debuggerd to debuggerd.bak (or whatever extension you want to add). Then I will copy the correct debuggerd file from sdcard to /system/bin and try the update again. I started a new thread asking for someone with an unaltered 4.2.2 debuggerd file to send it to me. If I get it I'll pass it along to you.
Groid said:
What I will do is to copy the debuggerd file to the N7 internal storage root folder from my pc. Then I will rename /system/bin/debuggerd to debuggerd.bak (or whatever extension you want to add). Then I will copy the correct debuggerd file from sdcard to /system/bin and try the update again. I started a new thread asking for someone with an unaltered 4.2.2 debuggerd file to send it to me. If I get it I'll pass it along to you.
Click to expand...
Click to collapse
Are you using a tool like ES File Manager to do the moving and renaming of files etc?
Guys Here I Present Some time of Work and For people Who are lazy this will help !!!
These zips and tar.md5's are for people who don't know how to start these are the latest OFFICAL CWM recoveries touch and non touch versions
These are the offical versions taken from the official site and I converted them to flasble zips and tar.md5's
P3100 Normal -----> flasble tar.md5 HERE
P3100 Touch ------> flasble tar.md5 HERE
P3100 Normal -----> flasble zip HERE
P3100 Touch -----> flasble zip HERE
-------------------------------------------------------------------------------------------------------------------
P3110 Normal ----->flasble tar.md5 HERE
P3110 Touch ------> flasble tar.md5 HERE
P3110 Normal -----> flasble zip HERE
P3110 Touch ------> flasble zip HERE
-------------------------------------------------------------------------------------------------------------------
P3113 Normal ------> flashble tar.md5 HERE
P3113 Touch ------> flashble tar.md5 HERE
P3113 Normal -----> flashble zip HERE
P3113 Touch -----> flashble zip HERE
-------------------------------------------------------------------------------------------------------------------
How to flash tar.md5'sFlash with Odin as PDA
How to flash zip filesFlash from exsiting recovery
please write the version number.
I think
GT-P3100 and GT-P3110: CWM 6.0.2.7
GT-P3113: CWM 6.0.2.3
Right?
Whats the point if I made my own with philz?
Sent from my LG-P690b using Tapatalk 2
Luigi2012SM64DS said:
Whats the point if I made my own with philz?
Click to expand...
Click to collapse
??
I love PhilZ more then CWM.
Awesome man thanks, for some reason the latest recovery, compiling from source, won't boot and hasn't booted for awhile for the p3113. Been using 6.0.2.3. +1 for the flashable zips, no easy way for people to tar files if they don't have a linux box!
CodyF86 said:
(..) +1 for the flashable zips, no easy way for people to tar files if they don't have a linux box!
Click to expand...
Click to collapse
Sure, it is easy now for Windows user - because of mythi have a look: http://forum.xda-developers.com/showthread.php?t=2387138
Android-Andi said:
Sure, it is easy now for Windows user - because of mythi have a look: http://forum.xda-developers.com/showthread.php?t=2387138
Click to expand...
Click to collapse
ah nice. Everytime I've tried to use a tar file made in windows though it never works out very well, but I'm sure that works, a-ok!
Godbless Ubuntu.
CodyF86 said:
ah nice. Everytime I've tried to use a tar file made in windows though it never works out very well, but I'm sure that works, a-ok!
Godbless Ubuntu.
Click to expand...
Click to collapse
I haven´t tried if it works No need to flash it at the moment. But i think it will work...
i only converted a recovery.img without problems to a recovery.tar.md5 using mythi´s script.
Android-Andi said:
I haven´t tried if it works No need to flash it at the moment. But i think it will work...
i only converted a recovery.img without problems to a recovery.tar.md5 using mythi´s script.
Click to expand...
Click to collapse
Oh im sure it works, Gonna try to see why the latest recovery isn't booting from source at some point soon.
Thanks for your support guys !!!!
P3113 Normal ------> flashble tar.md5
Click to expand...
Click to collapse
I keep getting "MD5 hash value is invalid" in Odin when trying to flash this
gooffeyguy said:
I keep getting "MD5 hash value is invalid" in Odin when trying to flash this
Click to expand...
Click to collapse
rename into recovery.tar.md5 and it will work
Thanks, that worked
That happens because @mythi changed the name of the file after he build the *.tar.md5
There is an md5 added into this file (for your safety) wich needs the same filename as at the buildingprocess. (sorry for my bad english i hope you understand)
Android-Andi said:
That happens because @mythi changed the name of the file after he build the *.tar.md5
There is an md5 added into this file (for your safety) wich needs the same filename as at the buildingprocess. (sorry for my bad english i hope you understand)
Click to expand...
Click to collapse
Or like I said remove the .md5 extension. Leave it as .tar. Thats easier I guess.
Android-Andi said:
That happens because @mythi changed the name of the file after he build the *.tar.md5
There is an md5 added into this file (for your safety) wich needs the same filename as at the buildingprocess. (sorry for my bad english i hope you understand)
Click to expand...
Click to collapse
Thanks It is safer to keep the md5 just rename recoveryXXXXX.tar.md5 to recovery..tar.md5
Links no longer open?
Sent from my GT-P3113 using Tapatalk HD
you can find links in first post here http://forum.xda-developers.com/showthread.php?t=2391355
Can I flash through stock recovery
Sent from my GT-P3110 using xda app-developers app
no, for *.tar.md5 you have to use odin.
for *.zip you need a custom recovery
Hello,
I currently have Tsunami X 5.6 android 4.2.2.
I want to update to Kitkat roms but I cant.
I get "status 7" error while trying to install.
I understood that it's because I have an old CWM recovery (6.0.3.2).
How do I update it?
Sorry for the n00b question..
Status 7 error is caused while the ROM’s updater script file checks to see if the phone model of your phone is compatible with the ROM you are installing called “asserts”.
How To Fix Statue error:
DO A NANDROID BACKUP if you haven't done so already just in case...
1. Copy the ROM zip file to your computer and extract it using your favorite unzipping software.
2. Once unzipped, browse to the META-INF/com/ google/android directory. You will find two files called “update-binary” and “updater-script”.
3. Rename “updater-script” to “updater-script.txt” and open with your favorite text file editor.
4. Get rid of the line starting with “assert” to next semi-colon. Usually this is the first line or one of the first lines at the top of the text file.
5. Save file.
6. Rename “updater-script.txt” back to “updater-script”.
7. Rezip all the files you’ve unzipped.
8. Copy the new, edited zip file to your phone.
9. Try re-installing ROM, now it should install fine without Status 7 error.
-MaoR- said:
Hello,
I currently have Tsunami X 5.6 android 4.2.2.
I want to update to Kitkat roms but I cant.
I get "status 7" error while trying to install.
I understood that it's because I have an old CWM recovery (6.0.3.2).
How do I update it?
Sorry for the n00b question..
Click to expand...
Click to collapse
If the previous answer is too complicated for you, just flash CM10.2 that will do proper partition for the latest ROMs and give you updated CWM recovery with which you can flash any KK rom. Just reboot once intonthe OS, then back to recovery and flash a KK rom. Don't forget to manually wipe /system before installing KK.
You will need to flash zip twice, as first time it will disolay warning of repartition and abbort with status 7. By next attempt it will work flawless.
pryerlee said:
Status 7 error is caused while the ROM’s updater script file checks to see if the phone model of your phone is compatible with the ROM you are installing called “asserts”.
How To Fix Ststue error:
DO A NANDROID BACKUP if you haven't done so already just in case...
1. Copy the ROM zip file to your computer and extract it using your favorite unzipping software.
2. Once unzipped, browse to the META-INF/com/ google/android directory. You will find two files called “update-binary” and “updater-script”.
3. Rename “updater-script” to “updater-script.txt” and open with your favorite text file editor.
4. Get rid of the line starting with “assert” to next semi-colon. Usually this is the first line or one of the first lines at the top of the text file.
5. Save file.
6. Rename “updater-script.txt” back to “updater-script”.
7. Rezip all the files you’ve unzipped.
8. Copy the new, edited zip file to your phone.
9. Try re-installing ROM, now it should install fine without Status 7 error.
Click to expand...
Click to collapse
tetakpatak said:
If the previous answer is too complicated for you, just flash CM10.2 that will do proper partition for the latest ROMs and give you updated CWM recovery with which you can flash any KK rom. Just reboot once intonthe OS, then back to recovery and flash a KK rom. Don't forget to manually wipe /system before installing KK.
You will need to flash zip twice, as first time it will disolay warning of repartition and abbort with status 7. By next attempt it will work flawless.
Click to expand...
Click to collapse
Thanks guys.
I actually did flash CM 10.2 just before even seeing the your comments.
It worked great and now I actually think on staying with this ROM lol..
It's very clean and nice.
Thanks again!