Ok, there don't seem to be many, if any stock images to revert to if you need to restore and send back your phone. Especially if you have a custom rom like me.
I DO NOT ACCEPT ANY RESPONSIBILITY IF YOUR BREAK YOUR DEVICE, CAUSE WW3 ETC
Can someone just check over this. I think it will work but I can't guarantee it. Once we know it works, we can get people to extract various images so we all have something to restore to.
1) Download the CWM image: DOWNLOAD
We need to do it this way because ROM Manager requires root
2) Use fastboot to unlock the bootloader on the device. At the same time, this will wipe the phone to the clean stock image:
fastboot oem unlock
4) Use fastboot to boot CWM, NOT flash it. This will temporarily boot into CWM, however it will not flash it to your device:
fastboot boot recovery-clockwork-5.5.0.2-maguro.img
5) Once in CWM, go to backups and perform a full device backup
6) Reboot your device. If you want, lock the bootloader to return to how it was when you got it:
fastboot oem lock
7) Upload the backup for all to use
Click to expand...
Click to collapse
Now, technically that will have created a backup of every stock image on this system, correct?
If so, that should give us all something to restore to, should you need to send it back for any reason. To restore you would need to:
1) Download a backup and put it onto /sdcard/ of your rooted phone
2) Use fastboot to boot into CWM as above if you haven't flashed it. If not, just boot into CWM Recovery
3) Go to backups and restore the backup from above
4) *Not sure if recovery.img will have been restored. If not, use a stock recovery.img
5) Use fastboot to lock the bootloader:
fastboot oem lock
Click to expand...
Click to collapse
This should take us back to stock. The only thing I see it not flashing is the recovery.img. Not too sure how we can get that, however perhaps the Peter Alfonze recovery.img would work
Appreciated if someone could give this a second opinion and their thoughts
Evostance said:
Ok, there don't seem to be many, if any stock images to revert to if you need to restore and send back your phone. Especially if you have a custom rom like me.
DO NOT ATTEMPT THIS YET. NEED TO GET IT CHECKED OVER FIRST
Can someone just check over this. I think it will work but I can't guarantee it. Once we know it works, we can get people to extract various images so we all have something to restore to.
Now, technically that will have created a backup of every stock image on this system, correct?
If so, that should give us all something to restore to, should you need to send it back for any reason. To restore you would need to:
This should take us back to stock. The only thing I see it not flashing is the recovery.img. Not too sure how we can get that, however perhaps the Peter Alfonze recovery.img would work
Appreciated if someone could give this a second opinion and their thoughts
Click to expand...
Click to collapse
Hmm, that's a good idea, BUT we can also boot in the CWM image and from there dd all partitions. I only don't know if you boot with fastboot boot, that img file is mounted on the usual boot partition
Yes, that should save all partitions, including sytem, data, boot, radio, recovery etc. I'm just not sure if you will be able to backup data partition since it's auto-mounted in recovery (otherwise you wont be able to see the content of virtual SD card):
Code:
0 /tmp ramdisk (null) (null) 0
1 /system ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/system (null) 0
2 /cache ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/cache (null) 0
[B]3 /data auto /dev/block/platform/omap/omap_hsmmc.0/by-name/userdata (null) 0[/B]
4 /misc emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/misc (null) 0
5 /boot emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/boot (null) 0
6 /recovery emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/recovery (null) 0
7 /sbl emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/sbl (null) 0
8 /xloader emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/xloader (null) 0
9 /radio emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/radio (null) 0
To be honest this is very bad solution in Samsung Galaxy Nexus. Also I'm not sure why HSMMC devices are flagged as EMMC. I tried contacting with koush about it but no answer from him. OK, sorry, no more hijacking your thread
netchip said:
Hmm, that's a good idea, BUT we can also boot in the CWM image and from there dd all partitions. I only don't know if you boot with fastboot boot, that img file is mounted on the usual boot partition
Click to expand...
Click to collapse
That was my only concern
mike1986. said:
Yes, that should save all partitions, including sytem, data, boot, radio, recovery etc. I'm just not sure if you will be able to backup data partition since it's auto-mounted in recovery (otherwise you wont be able to see the content of virtual SD card):
Code:
0 /tmp ramdisk (null) (null) 0
1 /system ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/system (null) 0
2 /cache ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/cache (null) 0
[B]3 /data auto /dev/block/platform/omap/omap_hsmmc.0/by-name/userdata (null) 0[/B]
4 /misc emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/misc (null) 0
5 /boot emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/boot (null) 0
6 /recovery emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/recovery (null) 0
7 /sbl emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/sbl (null) 0
8 /xloader emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/xloader (null) 0
9 /radio emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/radio (null) 0
To be honest this is very bad solution in Samsung Galaxy Nexus. Also I'm not sure why HSMMC devices are flagged as EMMC. I tried contacting with koush about it but no answer from him. OK, sorry, no more hijacking your thread
Click to expand...
Click to collapse
I know its not an ideal solution, but if we can get this to work, at least it gives us an option in the short run
Nobody got any other views?
Why other views? It will simply work, even with mounted data partition.
mike1986. said:
Why other views? It will simply work, even with mounted data partition.
Click to expand...
Click to collapse
That'll do! Now, just need to get someone to do it before they flash a custom rom...
I haven't flashed anything yet. I can wipe and make a nandroid backup, if it is needed.
matt2053 said:
I haven't flashed anything yet. I can wipe and make a nandroid backup, if it is needed.
Click to expand...
Click to collapse
Please!
Sent from my Galaxy Nexus using Tapatalk
Ok, so if you want to go back to stock quick and dirty, this should do the trick.
1. Download this zip.
2. Extract to /sdcard/clockworkmod/backup
3. Boot into ClockworkMod recovery.
4. Restore backup "maguro_4.0.1"
http://www.mediafire.com/?7k9076axlyg7r7u
Thanks. I might need this as I have a few dead pixels and I'm looking to return and get a new one.
matt2053 said:
Ok, so if you want to go back to stock quick and dirty, this should do the trick.
1. Download this zip.
2. Extract to /sdcard/clockworkmod/backup
3. Boot into ClockworkMod recovery.
4. Restore backup "maguro_4.0.1"
http://www.mediafire.com/?7k9076axlyg7r7u
Click to expand...
Click to collapse
Downloading and saving just for the sake of saving it you never know.
Sent from my Galaxy Nexus using xda premium
Could someone please confirm it works? Thanks!
Sent from my Sensation using XDA App
matt2053 said:
Ok, so if you want to go back to stock quick and dirty, this should do the trick.
1. Download this zip.
2. Extract to /sdcard/clockworkmod/backup
3. Boot into ClockworkMod recovery.
4. Restore backup "maguro_4.0.1"
http://www.mediafire.com/?7k9076axlyg7r7u
Click to expand...
Click to collapse
Where did you get that zip from?
Sent from my Galaxy Nexus using Tapatalk
Evostance said:
Where did you get that zip from?
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I made it. I am still in factory stock, so I just did a factory reset and made the backup.
Sent from my Galaxy Nexus using XDA App
matt2053 said:
I made it. I am still in factory stock, so I just did a factory reset and made the backup.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Top guy! Thanks a lot
Let us know if you manage to flash back to stock successfully using this.
This will definitely work for rooted users and the stock recovery from PeterAlphonzo's images can be fastbooted back on if desired. A couple notes of caution though:
After restoring this backup, you will still be rooted and therefore not completely stock.
The radio is not backed up and restored by CWM and cannot be extracted using DD because it comes up all FF bytes in the image rendered. This shouldn't be of critical importance to most users because the radio is not typically altered by user modifications anyway, so this still gives you your best method of restoring a stock configuration until an official set of images is made available.
cellzealot said:
After restoring this backup, you will still be rooted and therefore not completely stock.
Click to expand...
Click to collapse
If you mean unlocked, that's what fastboot oem lock is for.
Ok, by using various images, zips etc posted on here. I've managed to get the phone back to the stock unrooted rom, stock kernels etc and the stock recovery.
I'll post a tutorial up later
Related
can any dev. make this happen for our EVO 4G please? I included a link to the thread were the mod is. This mod enables a person to decide how big the partitions in their phone should be. (ei system, data, cache, etc). Its awesome but I just have it on my hero which i gave to my brother and it wouldn't hurt that everyone could have more space for apps on their phone.
Thanks everyone!!!
http://forum.xda-developers.com/showthread.php?t=754805
I found a dmesg for your evo
# dmesg|awk '/0x.+: "/{ print }'
Code:
<5>[ 4.290466] 0x00003f360000-0x00003ff60000 : "wimax"
<5>[ 4.305419] 0x00003ff60000-0x000040000000 : "misc"
<5>[ 4.306518] 0x000004240000-0x000004740000 : "recovery"
<5>[ 4.312377] 0x000004740000-0x0000049c0000 : "boot"
<5>[ 4.315979] 0x0000049c0000-0x00001a7c0000 : "system"
<5>[ 4.730438] 0x00001a7c0000-0x0000247c0000 : "cache"
<5>[ 4.916748] 0x0000247c0000-0x00003f360000 : "userdata"
it has an extra partition to the g1 ( wimax )
see below for working version v1.5.7
Sounds really great! Thank you, Firerat.
But FR-CustomMTD-v1.5.6-Evo4G.zip is not downloadable to me. The site says its set to private.
Firerat said:
FR-CustomMTD-v1.5.6-Evo4G.zip
that zip contains
73d5ba178ffd702c9b963e9de9b4d5bc FR-recovery-v1.5.6-Evo4G-CustomMTD_S.zip
f468aefb7ad1f86b24c0156fb81a36c2 FR-boot-v1.5.6-Evo4G-CustomMTD_S.zip
89b4e67b87f5337e19c2d7dc95e87055 FR-remove-v1.5.6-Evo4G-CustomMTD_S.zip
Click to expand...
Click to collapse
ywjkid said:
Sounds really great! Thank you, Firerat.
But FR-CustomMTD-v1.5.6-Evo4G.zip is not downloadable to me. The site says its set to private.
Click to expand...
Click to collapse
oops,
http://www.mediafire.com/?0ae7y9sekpb3s
b74d178e7ed698879b555123ea494377 FR-recovery-v1.5.7rc1-CustomMTD_S.zip
331c1b31bbc007fa7c3a9ff01c9301dd FR-boot-v1.5.7rc1-CustomMTD_S.zip
ab946b6b9aa83554c452d3d5face18d4 FR-remove-v1.5.7rc1-CustomMTD_S.zip
its a generic version, which _should_ suit all devices with msm_nand
it collects every partition from dmesg
few little bits I want to do, then I'll bump it up to v2
RC1 is not working for me. After flashing FR-recovery-v1.5.7rc1-CustomMTD_S.zip, my RA-recovery 1.8 is broken and generates errors like
E: Can't find MISC:
E: Can't mount CACHE:recovery/command
E: Can't mount CACHE:recovery/log
E: Can't open CACHE:recovery/log
Firerat said:
oops,
http://www.mediafire.com/?0ae7y9sekpb3s
b74d178e7ed698879b555123ea494377 FR-recovery-v1.5.7rc1-CustomMTD_S.zip
331c1b31bbc007fa7c3a9ff01c9301dd FR-boot-v1.5.7rc1-CustomMTD_S.zip
ab946b6b9aa83554c452d3d5face18d4 FR-remove-v1.5.7rc1-CustomMTD_S.zip
Click to expand...
Click to collapse
ywjkid said:
RC1 is not working for me. After flashing FR-recovery-v1.5.7rc1-CustomMTD_S.zip, my RA-recovery 1.8 is broken and generates errors like
E: Can't find MISC:
E: Can't mount CACHE:recovery/command
E: Can't mount CACHE:recovery/log
E: Can't open CACHE:recovery/log
Click to expand...
Click to collapse
Ok, I think I see the problem
Not at home right now,
But in the mean time you should be able to flash the remove zip and return to stock
Looks like a copy paste fail and I'm excluding userdata what I shouldn't be
May also be escaping when I shouldn't be
If you have problems flashing the remove zip you can mount cache manually via adb shell
( you can also flash_image a standard recovery.img via adb shell )
Thanks. Just reflashed recovery and restore the nandroid and everything is fine. I am glad there is no permanent damage done. Cannot wait for the working version!
Firerat said:
Ok, I think I see the problem
Not at home right now,
But in the mean time you should be able to flash the remove zip and return to stock
Looks like a copy paste fail and I'm excluding userdata what I shouldn't be
May also be escaping when I shouldn't be
If you have problems flashing the remove zip you can mount cache manually via adb shell
( you can also flash_image a standard recovery.img via adb shell )
Click to expand...
Click to collapse
ywjkid said:
Thanks. Just reflashed recovery and restore the nandroid and everything is fine. I am glad there is no permanent damage done. Cannot wait for the working version!
Click to expand...
Click to collapse
new version here
http://www.mediafire.com/?7w9sh54lm3mwi
9074fde94c8e534585da4adaa5e59e14 FR-AutoMTD_partitionPatcher_v1.5.7.tar.bz2
919db3e671d0688af9824f37b16ccc87 FR-boot-v1.5.7-CustomMTD_S.zip
05828d98920540c711e06abe5028388f FR-recovery-v1.5.7-CustomMTD_S.zip
changed the 'remove' option
to revert to the stock MTD layout set system size to 0 in mtdpartmap.txt and flash the recovery patcher
e.g.
echo "mtd 0" > /sdcard/mtdpartmap.txt
Great! now the recovery error is gone and the mod is working on my EVO, beautifully. More than 600M for /data. Thank you so much, Firerat. You're the best!
Code:
df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 207.4M 0 207.4M 0% /dev
tmpfs 207.4M 0 207.4M 0% /mnt/asec
/dev/block/mtdblock4 240.0M 195.1M 44.9M 81% /system
/dev/block/mtdblock6 637.6M 374.7M 262.9M 59% /data
tmpfs 8.0M 4.0K 8.0M 0% /app-cache
/dev/block/mtdblock6 637.6M 374.7M 262.9M 59% /cache
PS. It seems /cache and /data now share the same space. It is new to me. Does that mean there is only one size need to specify in mtdpartmap.txt?
Firerat said:
new version here
http://www.mediafire.com/?7w9sh54lm3mwi
9074fde94c8e534585da4adaa5e59e14 FR-AutoMTD_partitionPatcher_v1.5.7.tar.bz2
919db3e671d0688af9824f37b16ccc87 FR-boot-v1.5.7-CustomMTD_S.zip
05828d98920540c711e06abe5028388f FR-recovery-v1.5.7-CustomMTD_S.zip
changed the 'remove' option
to revert to the stock MTD layout set system size to 0 in mtdpartmap.txt and flash the recovery patcher
e.g.
echo "mtd 0" > /sdcard/mtdpartmap.txt
Click to expand...
Click to collapse
ywjkid said:
Great! now the recovery error is gone and the mod is working on my EVO, beautifully. More than 600M for /data. Thank you so much, Firerat. You're the best!
Code:
df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 207.4M 0 207.4M 0% /dev
tmpfs 207.4M 0 207.4M 0% /mnt/asec
/dev/block/mtdblock4 240.0M 195.1M 44.9M 81% /system
/dev/block/mtdblock6 637.6M 374.7M 262.9M 59% /data
tmpfs 8.0M 4.0K 8.0M 0% /app-cache
/dev/block/mtdblock6 637.6M 374.7M 262.9M 59% /cache
PS. It seems /cache and /data now share the same space. It is new to me. Does that mean there is only one size need to specify in mtdpartmap.txt?
Click to expand...
Click to collapse
you still need to specify size of cache , the minimum is 2mb
on your phone /cache is actually a bind mount of /data/cache
its there if anything needs to use it, for instance your rom may want to put dalvik-cache in /cache/dalvik-cache
it will actually be on /data, the advantage is that you can make better use of what was free space on /cache
That's indeed a nice advantage. A million thanks. Now I can throw everything in the phone storage without worrying about the space.
Firerat said:
you still need to specify size of cache , the minimum is 2mb
on your phone /cache is actually a bind mount of /data/cache
its there if anything needs to use it, for instance your rom may want to put dalvik-cache in /cache/dalvik-cache
it will actually be on /data, the advantage is that you can make better use of what was free space on /cache
Click to expand...
Click to collapse
Noob tutorial
THIS IS SO COOL. THANK YOU SO MUCH FIRERAT.
Hope this mod helps everyone. Just like it is helping me
Thanks anyone.
TUTORIAL FOR NOOBS
In TERMINAL:
1. for Fresh Evo 3.4.0.1: echo "mtd 210 3" > /sdcard/mtdpartmap.txt *****(you can do less than 210 for cm6 if you desire)*****
2. adb shell reboot recovery
In RECOVERY MENU
1. nandroid backup
2. wipe data/factory reset
3. wipe cache
4. wipe Dalvik-cache
5. flash fr-recovery.zip
6. wipe data/factory reset
7. wipe cache
8. wipe Dalvik-cache
In TERMINAL
1. adb shell reboot recovery
In RECOVERY MENU
1.2*. IF YOU GET A CACHE ERROR DO NOT ALARM IT MEANS SOMETHING WENT WRONG. ALL YOU NEED TO DO IS WIPE DATA, CACHE, AND DALVIK-CACHE AND FLASH fr-recovery.zip and then when it finish flashing - adb reboot recovery - from terminal
1.3** IF YOU DID NOT GET THE ABOVE ERROR GO TO STEP 2
2. flash ROM (or nandroid backup)
3. flash app (I.E. cm6 google apps)
4. flash kernal (if one)
5. flash fr-boot.zip
6. reboot
7. DONE!!! AND ENJOY THANKS TO FIRERAT (DONT FORGET TO THANKS HIM)
If you want to update/install a kernal
In TERMINAL
1. adb shell reboot recovery
In RECOVERY MENU
2. wipe cache
3. wipe Dalvik-cache
4. flash KERNAL
5. flash fr-boot.zip
6. reboot
7. Sit and let EVO turn on
*****for reset partitions--- echo "mtd 0" > /sdcard/mtdpartmap.txt**** (IF YOU WANT TO GO BACK TO STOCK) and flash the FR-AutoMTD_partitionPatcher then flash any ROM you want or NANDROID BACKUP
+++IF I DID ANYTHING WRONG UP THERE FEEL FREE IN CORRECTING ME +++
mrcamposd said:
THIS IS SO COOL. THANK YOU SO MUCH FIRERAT.
Can anyone post a tutorial for noobs?
Or is this the same as for the HERO?
Hope this mod helps everyone. Just like it is helping me
Thanks anyone.
Click to expand...
Click to collapse
I can confirm the process is the same as for the HERO.
mrcamposd said:
THIS IS SO COOL. THANK YOU SO MUCH FIRERAT.
*****for reset partitions--- echo "mtd 0" > /sdcard/mtdpartmap.txt**** (IF YOU WANT TO GO BACK TO STOCK) and flash the FR-AutoMTD_partitionPatcher then flash any ROM you want or NANDROID BACKUP
Click to expand...
Click to collapse
How do I flash this? It doesn't show up in the list of zip files in recovery. I tried renaming it and extracting it but it doesn't look like it's in a flashable format.
antiphon said:
How do I flash this? It doesn't show up in the list of zip files in recovery. I tried renaming it and extracting it but it doesn't look like it's in a flashable format.
Click to expand...
Click to collapse
i think you just need to rename the file's extension to xxxxx.zip (because .zip's are the one you flash in recovery), but then again I have not used that file. So not responsible for damages or anything. Try it at your own risk buddy.
mrcamposd said:
*****for reset partitions--- echo "mtd 0" > /sdcard/mtdpartmap.txt**** (IF YOU WANT TO GO BACK TO STOCK) and flash the FR-AutoMTD_partitionPatcher then flash any ROM you want or NANDROID BACKUP
+++IF I DID ANYTHING WRONG UP THERE FEEL FREE IN CORRECTING ME +++
Click to expand...
Click to collapse
FR-AutoMTD_partitionPatcher , is linux shell script to shoehorn the boot patcher into a rom zip ( so the end user dosn't need to flash the boot patcher , its automagic ) ,, you don't really need it
to get back to stock layout,
do the mtd 0 thing
nand backup
flash the recovery patcher
format system cache and data ( I recommend clockwork recovery )
reboot
nand restore ( providing the backup will fit stock ! )
flash boot patcher
your done
Note, v1.5.7b is newer
Had this working well on my Hero, so I'm looking forward to putting this on my new Evo as well!
Doesn't Calkulin have an evo version posted?
Sent From My HTC Evo 4G Using Tapa Talk Pro!
Hello, this is my first post but been seeing lot of threads here with lot of help, so I thank you all before you start helping me.
I have my HTC One X, tried to update to Jelly Bean using Dragon's ROM, all went fine but the phone got stuck on HTC logo.
Since that I can only start on recovery (ClockWork Mod 5.8.4.0), HBOOT (0.94) or fastboot.
There is no way I can access the SDCard from recovery to flash the rom.
I tried factory reset with no luck, wipe cache, wipe data.../factory reset. all with no luck! Every time I try to format my sdcard it says:
"Formatting /sdcard/.android_secure..."
"Error mounting /sdcard/.android_secure!"
"Skipping format..."
If I try with "mounts and storage" then "format sdcard":
"Formatting sdcard..."
"Error mounting /sdcard!"
I must say that I can use "Mount USB storage", did format with FAT32 on Windows & Mac, no luck. Also tried using parted with adb shell, formatting on ext2, but no luck.
Here is my "recovery.fstab":
~ # cat /etc/recovery.fstab
# mount point fstype device [device2]
# /recovery emmc recovery
# /boot emmc boot
# /system ext4 system
# /cache ext4 cache
# /misc emmc misc
# /sdcard vfat /dev/block/sda1 /dev/block/sda
# /internal_sdcard vfat /dev/block/mmcblk0p14
# /data ext4 userdata
# /devlog ext4 devlog
/recovery emmc /dev/block/mmcblk0p5
/boot emmc /dev/block/mmcblk0p4
/cache ext4 /dev/block/mmcblk0p13
/data ext4 /dev/block/mmcblk0p15
/sdcard vfat /dev/block/mmcblk0p14
/system ext4 /dev/block/mmcblk0p12
/misc emmc /dev/block/mmcblk0p17
------------
And here my fstab:
~ # cat /etc/fstab
/dev/block/mmcblk0p13 /cache ext4 rw
/dev/block/mmcblk0p15 /data ext4 rw
/dev/block/mmcblk0p12 /system ext4 rw
/dev/block/mmcblk0p14 /sdcard vfat rw
---------------
There is no way that ClockWork Mod can read my internal card for installing any zip. Any help would be really appreciated, even I would pay if necessary.
Thanks in advance for all the great work you guys do, and hope to get my phone back working!
If you mean the skydragon rom, ypu have to update hboot to use it.
And for the mounting problems... Try reflashing recovery.
I saw "fastboot oem format" somewhere and I aint sure what it does, but it might be worth a try.
Sent from my HTC One X using xda app-developers app
TToivanen said:
If you mean the skydragon rom, ypu have to update hboot to use it.
And for the mounting problems... Try reflashing recovery.
I saw "fastboot oem format" somewhere and I aint sure what it does, but it might be worth a try.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Hello, thanks for the fast answer.
I tried the oem format and this is the result:
prosacalatform-tools prosaca$ ./fastboot oem format
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.017s]
finished. total time: 0.017s
I just want to get my phone working, does not matter what ROM or whatever, just want it working hehe.
I tried also reflashing recovery with no luck.
I don't know what left to do...
poloivan said:
Hello, thanks for the fast answer.
I tried the oem format and this is the result:
prosacalatform-tools prosaca$ ./fastboot oem format
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.017s]
finished. total time: 0.017s
I just want to get my phone working, does not matter what ROM or whatever, just want it working hehe.
I tried also reflashing recovery with no luck.
I don't know what left to do...
Click to expand...
Click to collapse
Someone could please tell me how do I restore my phone as it came?
I have downloaded a RUU, my version main is: version-main: 1.28.161.9
When I click the RUU it does nothing, someone please help?
Thanks.
You have to relock bootloader first: fastboot oem lock.
Then run RUU with admin rights.
Sent from my HTC One X using xda app-developers app
TToivanen said:
You have to relock bootloader first: fastboot oem lock.
Then run RUU with admin rights.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Thank you all.
I have fixed my phone running the correct RUU.
Right now I am using Android Revolution HD 9.8. How can I update my HBOOT to run Android Revolution HD 18.0?
Best regards.
Two choices: Use a JB RUU or flash the correct firmware for your cid.
Hi,
About a month I used rom AR and I was aware of her faults (which yesterday revealed that it is not true), that when I restart, phone must be connected to the pc, and start bootloader via fastboot and the Command Promt flash boot.img dissected from ROM. Fortunately ROM, stable, so I followed all the time does not restart.
Yesterday I got a taste for change (and I wanted to get rid of the problem) and I downladed at first 4.4 ROM from xda taktik then 4.3JB and finally cyangen mod 7.2 Problem unfortunately stayed at all the same. When restarting HTC logo flashes and then turns off the display and starts "black" will flash this is over, unless we do the above procedure via the bootloader.
Does anyone an idea how to fix it?
Thnx
Have you format system + data + cache in mount and storage after wipe data cache and dalvik cache? Try this, if not success I think the only way is download the latest ruu and run it. You will be go back to stock. And we can use tools to root and flash custom recovery.
Sent from my Desire HD using Tapatalk
@Pilsner12 what the state of your phone bootloader..?, is that just unlocked with s-on..?, or already s-off..?, and what a custom recovery you used..?
if your phone is just unlocked with still s-on...did you already flashing a boot.img from the rom.zip that you already installed..?
to JJeamy:
bootloader is s-on, with touched clockworkmod 5.8.1.5, ROM cyanogen mod 7.2
if I standartly restart phone, didnt start. I must connect phone to pc, run bootloader, than fastboot and from pc via command prompt "send" boot.img (prepared from cm7.2) than phone restart and start correctly.
to pauleversham:
I will try it again (but I thing everythning expect SD card was formated, wiped, etc..) If I run RUU rom, I lost root permision, or is it possible get rooted RUU?
Pilsner12 said:
to JJeamy:
bootloader is s-on, with touched clockworkmod 5.8.1.5, ROM cyanogen mod 7.2
if I standartly restart phone, didnt start. I must connect phone to pc, run bootloader, than fastboot and from pc via command prompt "send" boot.img (prepared from cm7.2) than phone restart and start correctly.
to pauleversham:
I will try it again (but I thing everythning expect SD card was formated, wiped, etc..) If I run RUU rom, I lost root permision, or is it possible get rooted RUU?
Click to expand...
Click to collapse
so...you mean that you've already/ always flashing boot.img from the rom.zip itself after installing the rom from recovery...and that's mean your phone already can booting normally..right...?, so where's the problem exactly..?
anyway..if the problem you asked is...why you must always do a flashing boot.img manually after installing any new custom rom to boot normally is bacause you're still had s-on flag on your bootloader..that's why bootloader can't give permission to a custom recovery for flashing boot partition..
if you wanna running RUU...then you should be relocked your bootloader first..and that's mean your will return to the stock..so to rooting it again...you must unlocking your bootloader again..
Everytime, when I flash new rom, I have to flash boot.img. I know that. But problem is when I only restart phone, I need to flash boot.img otherwise phone doesnt start.
Today I find out:
- in clockworkmod I try to make a backup. Everything went great (back up boot image, recovery, system, data, android secure, cache) , but at the end I got a message: "No sd-ext found. Skipping backup of sd-ext."
Before AR rom I had many other roms and backing up and restarting without flashing wors fine.
The last hint which you give me is my last solution. I wouldnt lose my root privileges. I had a lot of trouble to get it..
Pilsner12 said:
Everytime, when I flash new rom, I have to flash boot.img. I know that. But problem is when I only restart phone, I need to flash boot.img otherwise phone doesnt start.
Today I find out:
- in clockworkmod I try to make a backup. Everything went great (back up boot image, recovery, system, data, android secure, cache) , but at the end I got a message: "No sd-ext found. Skipping backup of sd-ext."
Before AR rom I had many other roms and backing up and restarting without flashing wors fine.
The last hint which you give me is my last solution. I wouldnt lose my root privileges. I had a lot of trouble to get it..
Click to expand...
Click to collapse
maybe you can try it to installing and using a different custom recovery..like 4ext or twrp..
I would like to try use another custom recovery, but how I can Unistall cwm ? I didnt find any manual..
Pilsner12 said:
I would like to try use another custom recovery, but how I can Unistall cwm ? I didnt find any manual..
Click to expand...
Click to collapse
you don't need to uninstall it..just flashing a new one (like twrp or 4ext) through fastboot..then cwm will be replaced with that..
JJeamy said:
you don't need to uninstall it..just flashing a new one (like twrp or 4ext) through fastboot..then cwm will be replaced with that..
Click to expand...
Click to collapse
could you please post link, where is .zip file. I found only programs on market or .apk..
Are you booting the boot.img or flashing it? Also, recoveries are not zips, they are imgs.
Pilsner12 said:
could you please post link, where is .zip file. I found only programs on market or .apk..
Click to expand...
Click to collapse
This is a link for 4ext touch recovery here.., extract this zip file first to get recovery.img file
This is a link for TWRP touch recovery here..
just flash this recovery.img file through fastboot.. "fastboot flash recovery the_name_of_recovery.img"
JJeamy said:
This is a link for 4ext touch recovery here.., extract this zip file first to get recovery.img file
This is a link for TWRP touch recovery here..
just flash this recovery.img file through fastboot.. "fastboot flash recovery the_name_of_recovery.img"
Click to expand...
Click to collapse
Thank you for links, recovery is alerady fleshed, but problem is not fixed.
(btw: 4ext looks gorgeous )
here is log:
Starting recovery on Thu Feb 20 20:57:47 2014
framebuffer: fd 3 (480 x 800)
Welcome to 4EXT Recovery Touch
by madmaxx82
Preparing boot.. 0I:start load volumes..
Preparing boot.. 0 Preparing boot.. 0 Preparing boot.. 0I:st.f_bsize: 4096
Preparing boot.. 0 Preparing boot.. 1I:st.f_bsize: 4096
Preparing boot.. 1I:st.f_bsize: 4096
Preparing boot.. 1 Preparing boot.. 1 Preparing boot.. 1I:st.f_bsize: 4096
Preparing boot.. 2recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /recovery emmc /dev/block/mmcblk0p21 (null)
2 /boot emmc /dev/block/mmcblk0p22 (null)
3 /cache ext3 /dev/block/mmcblk0p27 (null)
4 /data ext3 /dev/block/mmcblk0p26 (null)
5 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
6 /system ext4 /dev/block/mmcblk0p25 (null)
7 /system_lib ext3 /dev/block/mmcblk0p28 (null)
I:end load volumes..
I:Completed outputting fstab.
Irocessing arguments.
Preparing boot.. 2I:Checking arguments.
Command: "/sbin/recovery"
ro.build.date=Sat Nov 10 16:53:16 CET 2012
ro.build.date.utc=0
ro.product.model=Desire HD
ro.product.brand=htc_wwe
ro.product.name=htc_ace
ro.product.device=ace
ro.product.board=spade
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HTC
ro.product.locale.language=hdpi
ro.product.locale.region=
ro.board.platform=msm7x30
ro.build.product=ace
ro.com.android.dateformat=MM-dd-yyyy
net.bt.name=Android
ro.serialno=SH18KRX02893
ro.baseband=26.14.04.28_M
ro.carrier=HTC-GER
ro.bootloader=2.00.0029
init.svc.choice_fn=stopped
init.svc.offmode_charging=running
init.svc.detect_key=running
init.svc.adbd=running
init.svc.recovery=running
ext.version="1005.8.0"
ext.feature.version_check=yes
ext.build=0
ext.edition=ng
Ireparing..
Preparing boot.. 2Irep sys1: 0
Preparing boot.. 2Ireparing.. fin
Preparing boot.. 2 Configuring settings..
Your configuration settings:
Using button backlights level: 80
Restore: MD5Sum checks: enabled
Backups: generate MD5Sums: enabled
Backups: mode: tar
Backups: exclude /cache: disabled
Backups: exclude dalvik-cache: disabled
Backups: include lib: enabled
Preserve theme: enabled
Hide useless directories: disabled
Haptic feedback: enabled
Haptic feedback strength: 28
Timezone: configured
Using 24h-hour time format
I:theme propok
Recovery is ready..
I:have tz_data
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
Irocessing 4EXT Control file...
4EXT Recovery Updater v2.4.6b
Processing..
Mounting sdcard..
I:Backup path: /sdcard/clockworkmod/backup/2014-02-20-00.05.02_CyanogenMod7.2.0ace
I:Backup mode: custom
Calculating space needed..
Space needed to complete: 654 MiB
Free space on your sdcard: 8264 MiB
Backing up boot image...
Including /system/lib
Backing up system_lib...
backup mode: tar
Backing up system...
Writing 4EXT info for filesystem ext4
Backing up data...
Writing 4EXT info for filesystem ext3
Backing up .android_secure...
Backing up cache...
Writing 4EXT info for filesystem ext3
Generating md5 sums...
tar: removing leading '/' from member names
-- Installing: /sdcard/Download/4EXT_Recovery_Touch_v1.0.0.6_RC1.zip
Finding update package...
I:Update location: /sdcard/Download/4EXT_Recovery_Touch_v1.0.0.6_RC1.zip
Opening update package...
Installing update...
Installation aborted.
Critical error! Installation aborted!
Canceling pending actions and booting UI
Pilsner12 said:
Thank you for links, recovery is alerady fleshed, but problem is not fixed.
(btw: 4ext looks gorgeous )
here is log:
Click to expand...
Click to collapse
what do you mean problem is not fixed..?, is that you mean you can't installing 4ext recovery..?, or problem about installing custom rom..?
JJeamy said:
what do you mean problem is not fixed..?, is that you mean you can't installing 4ext recovery..?, or problem about installing custom rom..?
Click to expand...
Click to collapse
Problem is if I want restart, or Start phone, I have to connect phone to pc, go to fastboot, and via command prompt send to phone boot.img prepared from my custom rom.
Othervise phone didnt start.
Pilsner12 said:
Problem is if I want restart, or Start phone, I have to connect phone to pc, go to fastboot, and via command prompt send to phone boot.img prepared from my custom rom.
Othervise phone didnt start.
Click to expand...
Click to collapse
that's weird thing..i think there's something wrong with your phone partition..
maybe you wanna try it to return your phone to the stock first by running a RUU..to fix that problem...after that
you can tried to fully rooting again for gaining s-off using AAHK2 script by Phiber2000 from here..
JJeamy said:
that's weird thing..i think there's something wrong with your phone partition..
maybe you wanna try it to return your phone to the stock first by running a RUU..to fix that problem...after that
you can tried to fully rooting again for gaining s-off using AAHK2 script by Phiber2000 from here..
Click to expand...
Click to collapse
Thank you for help, and link with this rooting instruction. I will do that in next week, becouse of time and I will let you know how it ends.
Pilsner12 said:
Thank you for help, and link with this rooting instruction. I will do that in next week, becouse of time and I will let you know how it ends.
Click to expand...
Click to collapse
So yesterday I ran RUU and now restart bug is fixed. I am happy for it!
But I have respect from rooting process. Last time it takes me a lot of weeks..
Please help me!!! i'm italian and i don't speak very well english Language
My HTC Desire hd don't start!!!!!!!!
I have CWM TOUCH 5.8.0.0
In starting my HTC Desire HD is blocked in white screen with green logo HTC
When i start RUU....... .exe (much version) the installation fail: error 140
I hope in you!!!!!!!!!
I have too Asus Padfone 2: with FRAMAROOT :good::good::good::good::good:
Please help me for my HTC Desire HD
I append in this post 4 images of my HTC DHD
Bacchione said:
Please help me!!! i'm italian and i don't speak very well english Language
My HTC Desire hd don't start!!!!!!!!
I have CWM TOUCH 5.8.0.0
In starting my HTC Desire HD is blocked in white screen with green logo HTC
When i start RUU....... .exe (much version) the installation fail: error 140
I hope in you!!!!!!!!!
I have too Asus Padfone 2: with FRAMAROOT :good::good::good::good::good:
Please help me for my HTC Desire HD
I append in this post 4 images of my HTC DHD
Click to expand...
Click to collapse
Please help me
Hello friends,
I have tried to flash every update of the Miroslav's rom unsuccessfuly. These are the metods I have tried:
SWETNES METHOD: ...Format system partition FIRST then flash ROM, then format cache, then do a FACTORY RESET (format data). First boot takes almost 10 min so be patient...
Click to expand...
Click to collapse
NOTZIPPY METHOD: ...After flash and reboot my phone did not get past the cm logo, I noticed a lot of errors in logcat , so I reboot into recovery and formatted cache and rebooted again, them ROM booted
Click to expand...
Click to collapse
MR.201 METHOD: ...factory reset then just flash the rc1 rom. gaaps is not needed as miroslav already added light gaaps...
Click to expand...
Click to collapse
_CRASS_ METHOD:
As for installing here is exactly what I did:
1) soft reboot to recovery
2) backuped everything through clockwork recovery
3) cleared cache
4) cleared dalvic
5) factory reset
6) install miroslav rom
7) rebooted...it got stuck on the CM logo
8) After about 10 minutes of no go I pulled battery
9) booted to clockwork recovery
10) factory reset
11) installed miroslav rom
12) installed latest kitkat gapps from CM website
13) rebooted
14) after 3-4 minutes I was in the pin screen of CM
Click to expand...
Click to collapse
LILOWEK METHOD: ...There was no rhyme or reason of why it installed. I simply installed it with gapps. No go. Format, clear all cache, install with gapps. Still the same. Did it again, and this time it went through. It booted in about 3 minutes. I suggest if you are having problems installing it to boot to just do it over and over as it will likely take at some point...
Click to expand...
Click to collapse
_CRASS_ METHOD ON RC2:
Installed it today.
Wiped factory data.
Wiped cache
Wiped dalvic
installed miroslav rom
installed gapps
and it booted right away.
Click to expand...
Click to collapse
REALYPSSD METHOD:
It took 2 tries:
Wiped System
Wiped factory data.
Wiped cache
Wiped dalvic
installed miroslav rom
installed gapps
Doing that didn't work, waited 15-20 minutes, was stuck at the CM logo.
Then I tried without flashing GAPPS, and it worked. I flashed GAPPS after I'd initially booted up once.
Click to expand...
Click to collapse
After I tried all these methods, I only softbricked the phone and had to unbrick it. I have a LG NITRO HD P930 and I use Philz Touch 6.19.3. SWETNES user suggest to use CWM 6.0.1.5 because he says CWM 6.0.4.5 has a lot of bugs, and MIROSLAV says he uses CWM 6.0.4.8 (I can't find it)
Also I want to know if in case I flash it successfuly, the rom MUST boot inmediatly first to LG logo then to CM logo or I have to wait watching the LG logo booting over and over for some minutes??
Any comments, suggestions?
Thank you guys.
I am having the same issue as OP
You did not try my suggestion Try flashing the rom then the gapps with adb sideload after wiping everything.
i use philztouch cwm and have had no problem flashing 4.3/4.4 roms with it. i also rooted my n what not when it was on ICS. i think the option in developer section to update cwm wich gave me the newest 6.0.4.8 i think but have been using philztouch till now.
Ive only wiped everything and flashed rom with no problems so far
Thank you for your comments.
Truepeace said:
You did not try my suggestion Try flashing the rom then the gapps with adb sideload after wiping everything.
Click to expand...
Click to collapse
Yeah, I noticed your method but I am kinda stupid and realy dont get clear the steps. I found this guide to flash via sideload and I wonder if it will work with philz touch:
http://android-revolution-hd.blogspot.mx/2013/12/ow-to-use-adb-sideload.html
xxAirwickxx said:
i use philztouch cwm and have had no problem flashing 4.3/4.4 roms with it. i also rooted my n what not when it was on ICS. i think the option in developer section to update cwm wich gave me the newest 6.0.4.8 i think but have been using philztouch till now.
Ive only wiped everything and flashed rom with no problems so far
Click to expand...
Click to collapse
So you recomend Philz Touch?
chortiman said:
Thank you for your comments.
Yeah, I noticed your method but I am kinda stupid and realy dont get clear the steps. I found this guide to flash via sideload and I wonder if it will work with philz touch:
http://android-revolution-hd.blogspot.mx/2013/12/ow-to-use-adb-sideload.html
So you recomend Philz Touch?
Click to expand...
Click to collapse
Maybe you got the same case as I am. Try to use CWM touch 6.0.1.5 . Then factory reset, format /system , then flash the rom. Loading might take several minute(mine was 10 min) then it will boot up properly. I already use philztouch,cwm 6.0.4.5,latest twrp but all of them not working for me in flashing this rom.
Here, I include the attachment for cwm touch 6.0.1.5 in case you're wondering where you want to find it.put it in the root of your sd card.
Then just run adb . Next, run the following command in the adb cmd :
adb shell
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p13
Best of luck, not all guide work for many people and devices
chortiman said:
Thank you for your comments.
Yeah, I noticed your method but I am kinda stupid and realy dont get clear the steps. I found this guide to flash via sideload and I wonder if it will work with philz touch:
http://android-revolution-hd.blogspot.mx/2013/12/ow-to-use-adb-sideload.html
So you recomend Philz Touch?
Click to expand...
Click to collapse
I wonder if this has to do with the way the phones r "unbricked" ? But personally yes I say latest philztouch. Worked great for me. I have latest cwm installed right now 6.0.4.9 & I can't backup so I'll be going back to philztouch.
Another try
I would try hereric's unbricking guide.
Start on step 9, and instead of flashing the provided KDZ use the v10i , download it at lg-phone-firmware.com/index.php?id_mod=17
Good luck
xxAirwickxx said:
I wonder if this has to do with the way the phones r "unbricked" ? But personally yes I say latest philztouch. Worked great for me. I have latest cwm installed right now 6.0.4.9 & I can't backup so I'll be going back to philztouch.
Click to expand...
Click to collapse
Well, I have used the latest philz and it has not worked for me so I will try using CWM 6.0.1.5. And well, it is very complicated to me that stuff about the unbricking because of the "baseband" and other things I dont understand and everybody mentions. I am beginning to believe that it HAS to be flashed over an specific baseband, or am I getting it wrong?
Mr.201 said:
Maybe you got the same case as I am. Try to use CWM touch 6.0.1.5 . Then factory reset, format /system , then flash the rom. Loading might take several minute(mine was 10 min) then it will boot up properly. I already use philztouch,cwm 6.0.4.5,latest twrp but all of them not working for me in flashing this rom.
Here, I include the attachment for cwm touch 6.0.1.5 in case you're wondering where you want to find it.put it in the root of your sd card.
Then just run adb . Next, run the following command in the adb cmd :
adb shell
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p13
Best of luck, not all guide work for many people and devices
Click to expand...
Click to collapse
I will try with this CWM 6.0.1.5. Thank you very much for the download So, with this method I can flash the RC3 directly? the 10 minutes you mention are with the LG Logo screen booting up over and over?
danilo96 said:
I would try hereric's unbricking guide.
Start on step 9, and instead of flashing the provided KDZ use the v10i , download it at lg-phone-firmware.com/index.php?id_mod=17
Good luck
Click to expand...
Click to collapse
The link you provide mention a P936 and mine is a P930. If I install this, will the phone work allright? As I was saying to xxAirwickxx, is it necesary to install this previously to flash the miroslav's rom???
Thank to every one for helping me to get a stable rom in my phone. I really apreciate it. :good:
chortiman said:
Well, I have used the latest philz and it has not worked for me so I will try using CWM 6.0.1.5. And well, it is very complicated to me that stuff about the unbricking because of the "baseband" and other things I dont understand and everybody mentions. I am beginning to believe that it HAS to be flashed over an specific baseband, or am I getting it wrong?
I will try with this CWM 6.0.1.5. Thank you very much for the download So, with this method I can flash the RC3 directly? the 10 minutes you mention are with the LG Logo screen booting up over and over?
The link you provide mention a P936 and mine is a P930. If I install this, will the phone work allright? As I was saying to xxAirwickxx, is it necesary to install this previously to flash the miroslav's rom???
Thank to every one for helping me to get a stable rom in my phone. I really apreciate it. :good:
Click to expand...
Click to collapse
It's not necessary, but the KDZ provided is not the most recent build of the GB, the v10i is most recent.
There's no problema flashing it, there is the p930, the p935 and the p936 which are all variants of the same phone, 930 is for america 935 for canada and 936 for europe i believe.
I couldn't install SphinX , always got bootloop or it booted but some system apps like phone didn't start...
Try that and you will probably succed
also , i use PhillZ and i have no problema :laugh:
In order to flash via sideload, I use this guide very easy once you install everything (android sdk and components)
http://forum.xda-developers.com/showthread.php?t=2318497
I tried hard and failed miserably
Well, its been a while since I started this thread. I tried the adb sideload, tried the CWM 6.0.1.5, tried a clean flash (factory reset, format system), waited boot loops for over 30 minutes and nothing. I did not flash KDZ v10i because that process has been always a pain to me. I will get back to CM 10.1.3 + Wind kernel + adreno drivers (the most stable configuration I know) and wait and see if miroslav fix this issue.
Thank you all for your time.
Yeah,I have tried all this methods but no luck......Just got the LG logo bootloop everytime!!(btw,my phone is su640)
I think people have changed there partition sizes in the past that is why the rom is failing to flash - here is mine and I can flash it
adb shell su -c "df"
Filesystem Size Used Free Blksize
/dev 383.8M 128.0K 383.6M 4096
/sys/fs/cgroup 383.8M 12.0K 383.8M 4096
/mnt/asec 383.8M 0.0K 383.8M 4096
/mnt/obb 383.8M 0.0K 383.8M 4096
/mnt/fuse 383.8M 0.0K 383.8M 4096
/system 662.3M 537.7M 124.6M 4096
/cache 157.6M 6.7M 151.0M 4096
/data 2.2G 935.6M 1.2G 4096
/persist 7.9M 4.9M 3.0M 4096
/mpt 15.8M 10.5M 5.3M 1024
/tombstones 71.9M 68.3M 3.7M 4096
/firmware 64.0M 22.8M 41.2M 16384
/modem 199.8M 27.7M 172.0M 4096
/mnt/media_rw/sdcard0 29.7G 16.9G 12.8G 32768
/mnt/secure/asec 29.7G 16.9G 12.8G 32768
Thanks for helping figure that out.
Sent from my LG-P930 using Tapatalk 2
Finally it works!
After having my su640 kdz(30D/4.1.2)，I'm finally succeeded！:victory:
notzippy said:
I think people have changed there partition sizes in the past that is why the rom is failing to flash - here is mine and I can flash it
adb shell su -c "df"
Filesystem Size Used Free Blksize
/dev 383.8M 128.0K 383.6M 4096
/sys/fs/cgroup 383.8M 12.0K 383.8M 4096
/mnt/asec 383.8M 0.0K 383.8M 4096
/mnt/obb 383.8M 0.0K 383.8M 4096
/mnt/fuse 383.8M 0.0K 383.8M 4096
/system 662.3M 537.7M 124.6M 4096
/cache 157.6M 6.7M 151.0M 4096
/data 2.2G 935.6M 1.2G 4096
/persist 7.9M 4.9M 3.0M 4096
/mpt 15.8M 10.5M 5.3M 1024
/tombstones 71.9M 68.3M 3.7M 4096
/firmware 64.0M 22.8M 41.2M 16384
/modem 199.8M 27.7M 172.0M 4096
/mnt/media_rw/sdcard0 29.7G 16.9G 12.8G 32768
/mnt/secure/asec 29.7G 16.9G 12.8G 32768
Click to expand...
Click to collapse
Was able to flash Miro's cm11 Final with this method. Worked first time like a charm.
(My post explaining what I did)
http://forum.xda-developers.com/showthread.php?p=55404877
Sent from my LG-P930 using Tapatalk 2
Well, I decided to flash my phone and forgot that it was encrypted.
Went to TWRP, and wiped everything that it could, but it was stuck in '/data'. This means that my phone got pretty much reseted but the 'data' partition didn't.
The problem now is that I cannot install any ROM. I tried a lot of methods to remove the encryption and some worked, for example:
mke2fs -t ext4 /dev/block/mmcblk0p19
Click to expand...
Click to collapse
This meant that I could restart TWRP without having to put the PIN to decrypt it. But still, It kept failing on me, when trying to install a new rom, with the error:
unable to wipe 'data' -- unknown filesystem 'auto'
unable to format to remove encryption
Click to expand...
Click to collapse
I have no idea of what to do. I tried with DD also, to rewrite the blocks, but it just brought my encryption back.
Can anyone please help me ?
try to flash raw file with asus flashtool