So now that we are bootloader unlocked and can install ClockworkMod recovery as opposed to SafeStrap. What my question is is that can we now flash the old roms with CWM or do we have to wait for roms to be made specifically with CWM? Since the roms work with the phone i assume there is a difference in how CWM flashes the roms so if that is true can we modify the rom to be flashed with CWM and if so can someone either direct me to a guide or explain it to me?
I apologize in advance if i am horribly wrong in my interpretation of the process i am still new at flashing roms and this is the only phone i have been able to do this with.
Thank you,
Gage
I have installed batakang rises through CWM with no issues. Just be sure to do a nandroid backup and mount /system before flashing the zip files. I also wiped /system /data and /cache before flashing.
Sent from my MB886 using Tapatalk 2
Thank you
dhack21 said:
I have installed batakang rises through CWM with no issues. Just be sure to do a nandroid backup and mount /system before flashing the zip files. I also wiped /system /data and /cache before flashing.
Sent from my MB886 using Tapatalk 2
Click to expand...
Click to collapse
thank you very much i was missing the step of mounting /system before installing the rom now it works great.
dhack21 said:
I have installed batakang rises through CWM with no issues. Just be sure to do a nandroid backup and mount /system before flashing the zip files. I also wiped /system /data and /cache before flashing.
Sent from my MB886 using Tapatalk 2
Click to expand...
Click to collapse
Does Batakang Rises work with AT&T? I thought Joker would, but it wasn't getting any AT&T signal at all.
Both of those work for att. I've ran both.
Sent from my JokerMATRIX HD MAXX
Related
I've a problem changing rom from cyanogenmod to any other rom; if I flash the new one from clockwork I've a boot loop, with all the roms I've tried.
The only thing I can do is go back again to cyanogenmod or flash the whole stock rom, loosing all internal sd card contents, and then install the new rom; but I've to root the stock to install clockwork again.
I hope anyone can understand my bad english, sorry.
Please help! ;-)
Byez.
Inviato dal mio Transformer TF101 usando Tapatalk
Did you do the three wipes before installing? What cwm version do you have installed? The new one with the touch interface would only install MIUI and nothing else for me. Every other rom caused a bootloop. Reverting to cwm 5.0.2.7 solved it for me.
Sent from my Optimus 2X using Tapatalk
in CM /system is EXT4 but stock/some other ROMs use EXT3, so reverting to stock via a nandroid (something I've tried & seen fail) or flashing a ROM thats updater script doesn't format the partition to the type it needs will fail as you'll just overwrite the contents of the EXT4 partition & have a kernel that only supports EXT3, hence bootloops
There a flashable zip files that just format /system (and other partitions too) to whichever you need in one of the stickys in the development section, have a look in here & do some reading in those threads to see if this is the problem you are having or if I'm way off base
as with everything, backup before you mess with it
(I'm pretty new to the P990 so could be missing something)
Tnx, I will look for the script and I think the problem is just the ext4.
Thanks, I will let you know. ;-)
Inviato dal mio LG-P990 usando Tapatalk
smashman42 said:
in CM /system is EXT4 but stock/some other ROMs use EXT3, so reverting to stock via a nandroid (something I've tried & seen fail) or flashing a ROM thats updater script doesn't format the partition to the type it needs will fail as you'll just overwrite the contents of the EXT4 partition & have a kernel that only supports EXT3, hence bootloops
There a flashable zip files that just format /system (and other partitions too) to whichever you need in one of the stickys in the development section, have a look in here & do some reading in those threads to see if this is the problem you are having or if I'm way off base
as with everything, backup before you mess with it
(I'm pretty new to the P990 so could be missing something)
Click to expand...
Click to collapse
This ^^
Sent from my LG-P990
I use the 3.2 HC method to root my P7320 with ICS4.04 (Hong Kong version), after flash the CWM recovery into the tab I boot into the recovery mode and choose to install the zip file from SDcard, but it said( E: Can't mount /sdcard/ ). I have already copy the superuser.zip into the sdcard's root directory but cannot find it to install, any idea if I have done something wrong?
Many thanks!
Wrong section, anyways try reflashing the recovery, or remount sdcard.
Sent from my Xperia'ed One X+
panpjp said:
Wrong section, anyways try reflashing the recovery, or remount sdcard.
Sent from my Xperia'ed One X+
Click to expand...
Click to collapse
I have flash for several times but still same. The option on the recovery is mount /efs, mount /data, mount /system but it shows error mounting /data, others seems no change. The CWM recovery v5.5.0.4
Jimmywwk said:
I have flash for several times but still same. The option on the recovery is mount /efs, mount /data, mount /system but it shows error mounting /data, others seems no change. The CWM recovery v5.5.0.4
Click to expand...
Click to collapse
For my know, ROOT P7320 LTE is use odin, and not install by CWM.
U can see by this thread:
http://forum.xda-developers.com/showthread.php?t=1401100
Problem Fixed, Thanks All!
Jimmywwk said:
Problem Fixed, Thanks All!
Click to expand...
Click to collapse
How did you fix it?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
How did you fix it? I want to know it too. I get P7320 E: Can't mount /sdcard/
for my galaxy i957 i used http://forum.xda-developers.com/showthread.php?t=1287205 that on honeycomb but im going to try it again on my ice cream version
Question if I do a factor reset on my MotoX DEV Ed. 4.4.2 updated with unlocked bootloader, TWRP, SuperSU will I need to reinstall TWRP and SuperSU or will I retain TWRP and SuperSU?
A factory reset just wipes /data (via recovery). It doesn't do anything to recovery or to /system. Put those two together and you have your answer.
CartlandSmith said:
And when you have TWRP installed, it doesn't even completely wipe data since your Nandroid backups survive a factory reset. I just did one and was surprised to see that.
Click to expand...
Click to collapse
"Data" in this case is the /data partition. Backups are stored on the SD card, which is a separate partition.
Sent from my Nexus 10 using Tapatalk
CartlandSmith said:
thanks I did eventually figure that out. So /data is apps, settings, contacts, texts, call logs. Anything else?
Click to expand...
Click to collapse
Correct.
Sent from my XT1060 using Tapatalk
kbluhm said:
"Data" in this case is the /data partition. Backups are stored on the SD card, which is a separate partition.
Sent from my Nexus 10 using Tapatalk
Click to expand...
Click to collapse
No it isn't. The /sdcard is /data/media. The reason that TWRP and CWM do not format this during a factory reset is that they are setup not to. They don't actually format when you do it, they do a "rm -rf" of everything except /data/media, unless you select the option to wipe everything, in which case, they actually format it.
I flashed Reincarnation for GT-S5570I as steps and it didn't boot why???
Accually, I really don't have 10 posts to post on our fourm so i think you could help me.
Right?
Did you wipe? Most people say they did everything and they don't wipe. And are you using CWM or stock recovery? That's another mistake people often make.
I wiped factory data and data partition and using CWM v.5
Sent from my GT-S5570i using xda app-developers app
Btw, It has an installation while flashing and it was written that it's for galaxy Y but the topic that i got link from was on Galaxy mini GT-S5570I android development fourm
Sent from my GT-S5570i using xda app-developers app
Are you using this http://forum.xda-developers.com/showthread.php?t=2649487 recovery or which?
And the text at installation can say anything, it's a matter of changing a line in the updater script. You can make it say Galaxy S5 and work on s5570i.
I think just wiping data isn't enough. You might want to wipe everything like /data, /cache and /system.
Also (this is important), remember to mount all partitions before flashing the kernel first (wiping /system probably removes the kernel, just in case) and then flashing the ROM.
In the installation it says Galaxy Y GT-S5360, but the necessary porting has been done so it is safe to flash for our phone. You can edit it not in the updater-script but in some txt files related to the Aroma Installer.
Sent because I <3 Aerith
Ok, Thanks, Guys
Sent from my device GT-S5570I with my own words
Yes, I use this Version of CWM
Sent from my device GT-S5570I with my own words
NightRaven49 said:
I think just wiping data isn't enough. You might want to wipe everything like /data, /cache and /system.
Also (this is important), remember to mount all partitions before flashing the kernel first (wiping /system probably removes the kernel, just in case) and then flashing the ROM.
In the installation it says Galaxy Y GT-S5360, but the necessary porting has been done so it is safe to flash for our phone. You can edit it not in the updater-script but in some txt files related to the Aroma Installer.
Sent because I <3 Aerith
Click to expand...
Click to collapse
Updater script should mount everything and unmount everything when finished.
ast00 said:
Updater script should mount everything and unmount everything when finished.
Click to expand...
Click to collapse
I don't know if it does, just mount to be sure.
Sent because I <3 Aerith
Allright guys,
If tried to reflash it and was done and on it's fourm someone said that he was on boot for 3 hours!!!!!
Sent from my device GT-S5570I in my own words
I updated my twrp from 2.7.1 to 2.8.3.0. I haven't flashed a rom in a while, so I don't know for sure that it was working on the old one but I did install CM11 using 2.7.1. Now with 2.8.3 when I go into recovery and wipe is says it worked, but in red there is the error: "E: unable to mount /system".
I tried to repair it with twrp, using format /system as ext4, then wipe and it seems to work and mount correctly, but if I restart, into recovery the /system no longer mounts and gives the same error if I try to wipe it. When I select repair, it says the partition is 0mb. When I format as ext4 it then shows as the correct size (~1.8GB).
So bottom line is that when I try to flash a new rom, it gets stuck at the formating /system step. I think the problem is with twrp but I'm not sure. Any ideas what to do?
I have a T-mobile HTC one M7. It was CM11, but everything is wiped. TWRP 2.8.3. S-off unlocked bootloader.
Thanks!
modman21 said:
I updated my twrp from 2.7.1 to 2.8.3.0. I haven't flashed a rom in a while, so I don't know for sure that it was working on the old one but I did install CM11 using 2.7.1. Now with 2.8.3 when I go into recovery and wipe is says it worked, but in red there is the error: "E: unable to mount /system".
I tried to repair it with twrp, using format /system as ext4, then wipe and it seems to work and mount correctly, but if I restart, into recovery the /system no longer mounts and gives the same error if I try to wipe it. When I select repair, it says the partition is 0mb. When I format as ext4 it then shows as the correct size (~1.8GB).
So bottom line is that when I try to flash a new rom, it gets stuck at the formating /system step. I think the problem is with twrp but I'm not sure. Any ideas what to do?
I have a T-mobile HTC one M7. It was CM11, but everything is wiped. TWRP 2.8.3. S-off unlocked bootloader.
Thanks!
Click to expand...
Click to collapse
first of all the most reliable version of TWRP recovery is stil 2.6.3.3 or 2.6.3.4, most of the users on here would agree with me on that, newer is not always better.
Also, have you tried the format data option, select wipe then format data button, be warned though, this will wipe everything including your sdcard (internal) if this option works you will then have to sideload or push a rom to your device before you can flash.
Seanie280672 said:
first of all the most reliable version of TWRP recovery is stil 2.6.3.3 or 2.6.3.4, most of the users on here would agree with me on that
Click to expand...
Click to collapse
Agree 100% but CM11 require at least 2.7.0.8 to be flashed (block:by-name) and recommended version of twrp to flash CM11 is 2.7.1.2 http://wiki.cyanogenmod.org/w/Install_CM_for_m7
If not flashing a rom like CM11 still recommend using 2.6.3.3/.4 even if there are newer version.
They are talking about this in ARHD thread.
Seems a updater script problem.
Read here and below!
http://forum.xda-developers.com/showpost.php?p=57985309&postcount=84878
My 2 cents
Fain11 said:
They are talking about this in ARHD thread.
Seems a updater script problem.
Read here and below!
http://forum.xda-developers.com/showpost.php?p=57985309&postcount=84878
My 2 cents
Click to expand...
Click to collapse
Thanks for the link. I tried to find similar threads, but couldn't. They are having the same problem but with a different rom (I was trying to flash Sky Dragon android L). The solution on that thread was to use TWRP 2.6.3.3, but some people reported having no problems with 2.8.3. The install instructions for Sky Dragon say use the latest twrp but doesn't specify a version. I guess I could try TWRP 2.6.3.3 but I'm not sure if it will work since CM requires 2.7.1.
The other solution was to mount the partition manually before flashing using the terminal in recovery. This command was suggested:
Code:
run_program("/sbin/umount", "/system");
Haven't tried any of these solution myself. After 3 hours and wiping my entire data partition by accident, I USB-OTG copied my nandroid backup to my phone and did a complete recovery. Luckily the restore process didn't care about mounting /system. I may try this again with manual mounting, but likely I will wait for a twrp update. I'm not sure if twrp 2.6 supports usb-otg so it will be a pain in the ass if I wipe /data again by accident.
Random side note for anyone googling this, if you accidently wipe all the data from your sdcard and have to copy the nandroid backup for twrp, the the restore function won't recognize the files unless they are in exactly the right directory. The best way to get this is to copy the entire TWRP directory when saving your backup in the first place so you can just copy it back. If you didn't do that then just run a nandroid backup of the blank sdcard and it will recreate the folder structure for you. Then you copy the files into the correct folder.
alray said:
Agree 100% but CM11 require at least 2.7.0.8 to be flashed (block:by-name) and recommended version of twrp to flash CM11 is 2.7.1.2 http://wiki.cyanogenmod.org/w/Install_CM_for_m7
If not flashing a rom like CM11 still recommend using 2.6.3.3/.4 even if there are newer version.
Click to expand...
Click to collapse
Exactly this. I do not know the exact reason CM needs 2.7.1 so therefore I don't know if Sky Dragon needs it as well. The instructions just say use the latest twrp.
http://forum.xda-developers.com/showthread.php?t=2400161
Seanie280672 said:
first of all the most reliable version of TWRP recovery is stil 2.6.3.3 or 2.6.3.4, most of the users on here would agree with me on that, newer is not always better.
Also, have you tried the format data option, select wipe then format data button, be warned though, this will wipe everything including your sdcard (internal) if this option works you will then have to sideload or push a rom to your device before you can flash.
Click to expand...
Click to collapse
I did wipe my entire data partition (by accident), but I did not try to format it as ext4. I did format /system to ext4 (so now the partition was displaying correctly as ~1.8gb). The used the twrp repair, then wipe It seemed to work, but if I restarted right then, without even trying to flash the rom, the /system would not mount on reboot to recovery and would show as 0mb. I used all reasonable combinations and permutations of the wipe, repair and format functions on system, nothing worked.
I finally copied my nandroid backup via usb-otg and recovered back to cm11.