So here's the scenario. Hopefully I don't leave anything pertinent out...
Galaxy S3 w/Sprint. Phone is rooted but has the stock ROM on it. The phone doesn't need to be rooted, but I figured something like wifi tether might come in handy at some point. I rooted it such a long time ago I honestly don't remember how I did it. However, the screenshots of the Odin program look somewhat familiar so I'm guessing it was something with that.
When I boot into recovery mode, it says CWM-based recovery v5.5.0.4 and has the standard CWM menu.
This, of course, means I can't get the OTA update that came out a few months back.
So, in order to get the stupid prompt to stop bugging me to update, I need to flash the phone with something. I'd be fine using an updated version of the Stock ROM, or would be happy to put something like CM10 on there. I don't want anything experimental so I'd go with the stable version.
This leads me to three questions.
1) What would you recommend as far as a ROM to flash when comparing stock vs CM vs whatever else. I'm fine with the stock feature set and stability is the top priority.
2) When I flash whatever ROM I flash, how much of the phone needs to be wiped? All the apps will have to be reinstalled, but does it also have to wipe things like photos and such?
3) How do I do the flash? All of the tutorials I see assume you're starting with an unrooted phone, which I'm not. Do I just copy the ROM Zip file over, do one of the wipes and then do the install from zip? I'm just looking for the basic steps to follow since I"m already rooted and have a recovery already there.
THANKS for any help so I can finally get this straightened out!!!
1.It depends on your likings. Play with different ROMs.
2.Just a wipe before to flash the ROM.No need to wipe photos and videos.
3.Yep.Put the ROM on your SD card,wipe your phone and then flash it.
Hope that helps
Sent from my GT-I9300 using xda app-developers app
kelemvor33 said:
This leads me to three questions.
1) What would you recommend as far as a ROM to flash when comparing stock vs CM vs whatever else. I'm fine with the stock feature set and stability is the top priority.
2) When I flash whatever ROM I flash, how much of the phone needs to be wiped? All the apps will have to be reinstalled, but does it also have to wipe things like photos and such?
3) How do I do the flash? All of the tutorials I see assume you're starting with an unrooted phone, which I'm not. Do I just copy the ROM Zip file over, do one of the wipes and then do the install from zip? I'm just looking for the basic steps to follow since I"m already rooted and have a recovery already there.
THANKS for any help so I can finally get this straightened out!!!
Click to expand...
Click to collapse
1) The standard answer is: try them all out and see if you like one or the other. But I'll be nice and also say that if you're looking for something stable, I'd recommend The People's ROM. It's a TW-based ROM with a lot of customization, but it's very stable and has a large user base. They're always willing to help someone out (as long as you search before asking).
2) It really depends what you're flashing. I always recommend what I call a "so fresh, so clean-clean flash," which means wiping /data, wiping /system, and cache and dalvik cache. You won't lose your photos, but you will lose all apps and their associated data (save games, etc). The reason I recommend wiping system (which others might not suggest), is that different ROMs have different mods associated with them, and as an end-user of the ROM, you have no idea if your previous ROM is leaving behind files in /system that won't play nicely with your new ROM. So I typically wipe system as well as data and the caches.
3) You're in luck. I have a previous post that explains #3 is pretty good detail. Since you have verified that you have CWM, you can skip the first section where I talk about that. I have quoted it below:
kay131108 said:
ok..can u pls be a little more specific..i if i press the three buttons with volume down is just an android in download mode..so what do i do next?...clockworkmodrecovery
Click to expand...
Click to collapse
Ok, let's start at the very beginning (it's a very good place to start).
Before we get started, I'm going to make the following assumptions:
You successfully rooted your phone through Odin.
You currently have a custom recovery (either TWRP or CWM).
You have a Rom you'd like to flash on either your internal storage or your SDcard (I'd recommend the SDcard, but that's your prerogative).
If either of the first two is not true, I'd recommend going back to qbking77's thread and check out the videos on how to use Odin to gain root and a custom recovery.
If number 3 above is not true, download a ROM (nor someone new to flashing/custom Roms, I'd recommend Freeza's stock rooted Rom, as it's identical to stock TW, but just with Root). Once you download a Rom, check it's md5sum to verify that it's a good download. Copy the file to your SD card and get ready to flash (make sure you have decent battery life left, I try to keep at least 50% or more when flashing Roms, although it shouldn't take too long.
I'll give directions on how to flash a Rom below. The instructions will be for TWRP, but CWM has similar options/settings
Turn your phone completely off (hold down power for 3-5 seconds)
Boot your phone into recovery. Hold Up, Menu, and Power for a few seconds (until SAMSUNG appears on your screen and the phone vibrates)
Make a Nandroid backup. I can't emphasize this enough. In flashing, it's almost a certainty that one time, something will mess up. When that happens, you want to be able to restore a backup. In TWRP, just go into Backup Menu and choose where you want it (internal vs. External storage). It takes my phone a few (5-10) minutes to completely backup my data.
In TWRP, click the wipe button, then system. This will completely wipe the Rom from your phone. Doing this will allow you to get a "clean" install, without any settings or leftover files from your old Rom getting in the way. Instead, you could only wipe data (factory reset), which is good enough for most Roms. I'd still recommend a system wipe, though.
Also while in the Wipe menu, wipe Cache and Dalvik Cache.
Go back to the TWRP main menu.
Click Install, then find your Rom zip file (may have to switch from internal to external storage).
Let TWRP do it's thing.
If you're installing a TW-based Rom, chances are it had gapps already installed. If not, you should now flash the correct gapps package from goo.im. Make sure you're flashing the correct one, as if you don't, your google apps will force close upon use.
Reboot into system and give it time to boot (first boot sometimes takes a couple of minutes).
Set up your phone the way you like.
These should be the directions to follow whenever you flash a new Rom. Some Roms have the Aroma installer, so you'll have more options once you choose to flash the Rom zip, but those are typically easy to follow (and vary from Rom to Rom, so I won't be able to give you a good guide on that).
Hope this helps!
Click to expand...
Click to collapse
And lastly, you don't have to lose all your apps. You can use Titanium Backup (TiBu) to restore your apps. You just have to be careful not to restore any system apps, as they tend to not play well between Roms. I have quoted my previous post about TiBu down below so you can review some features/warning about TiBu.
Ok, first I'll describe what you did and how that (most likely) messed up your phone. Then I'll describe what you can do to fix it.
Problem
It seems like your original flash of CM10.1 went smoothly. It must have been something to do with your Titanium Backup (TiBu) restores. More than likely, you tried to restore too much. In TiBu, the different apps have different colors: Red, Yellow, Green, and White. In the menu, you can see the following Legend:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
White: User Application. These are apps that you installed from the Play Store or sideloaded by directly installing an apk. These are safe to restore.
Red: System Application. These are system files that heavily rely on which Android version (4.1.x vs. 4.2.x) and whether you're on TW or AOSP. I always try to avoid restoring these backups (even when just upgrading to a newer version of the same Rom). Some people will say that you can restore the Data only for these, but my motto is: caution will help prevent mistakes (ground-shaking, I know).
Green: System Service with Useful Data: These are system apps that have useful information (such as User Accounts, etc.). I treat these the same as Red Backups, but am a bit more likely to restore the data of them (green means go, right?).
Yellow: These backups are system data that can be restored as an xml file. These are inherently safer than the red and green ones, and I say restore away (I always restore my Call Log, Messages, and Wi-Fi Access Points).
The reason you were getting FCs was restoring a red or green backup. This can sometimes work, but has a lot of potential for issues when switching between TW and AOSP Roms. Most likely something in your /system folder is messed up due to restoring an app. Even when you flash a new Rom, it just overwrites items in your System folder, it doesn't wipe /System. So whatever is wrong in your /System folder is still there, regardless of what you flash.
Click to expand...
Click to collapse
Related
I am following this forum closely since few months, and think I should do more with with my Defy now! I have already rooted my phone but I am still on stock Eclair. I really, really want to try CM7 but though I am quite tech-savvy, there are some things which I am still unable to get into my head! So I need someone to help me, in plain English, with the following:
1 If I install CM7, or any ROM, and then decide to go back to stock, can I?
2. I guess I can using a nandroid backup, right? BTW, what is nandroid backup?!
3. AFAIK, nandroid backs up the current ROM so that if things go wrong it can be reverted, right? If yes, how to perform a nandroid backup on Defy? How easy is it? How much of space does it take in the SD card?
4. What is sbf, recovery etc.? Why are they needed? What are the specific versions I need based on my phone:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Offtopic:
5. If I perform a 'Factory Reset', will I lose root?
Please help me understand all these; from what I have read so far everything seems so confusing!!
1. CM7 requires Froyo(2.2) based SBF in order to install. So you must be on official Froyo(released via your phone over OTA by your network) or have flashed Froyo. Once you FLash or upgrade your phone through either of these methods, you cannot downgrade back to 2.1. In the case of official it is not problem, and because official 2.2 is being rolled out, you can probably safely upgrade by flashing one of the stable official SBF's from any of the versions offered on the forums, you probably want to look for ROM users from your country to get an idea if the SBF the ROM is based on works in your region without much hassle.
2. Others will need to answer the Nandroid thing, I know as much as I use Nandroids to make a back up of MY phones state as a way to go back to how my phone was prior to me messing with it, but I am not clear on how you can use a Nandroid from another persons phone on your own. I always just flashed the latest SBF that was Deblured. I am currently using the most recent "Nordic" SBF and CM7, I flashed the SBF and installed the CM7 zip file from recovery.
3. See #2
4. SBF as far as I know is the actual firmware that the phone uses, this set of code tells the phone what does what when it comes to the phones hardware. The files have a base Android on them that they work from which can be with Blur or without Blur(Motorolas GUI shell for Android). So some SBF's come with 2.1, some with 2.2 and soon 2.3.
The Android version is the software side of things, and this can vary depending on how the ROM you are using is made(I think) This is why your SBF will have different numbers associated with it(because these SBF's vary from carrier to carrier and from country to country, some have Blur, some do not, some are set up for particular GSM ranges for 3G etc) and your Android will have a separate number.
It is a bit confusing and my knowledge is kind of limited so I may in fact me kind of mixed up on some of these things. Take what I say with a grain of salt.
Recovery is a small app that allows you to use a custom recovery(which is not included with Motorola phones) which is a method to insall ROMs. You need to root and install recovery to start making real changes to your phone.
Hope some of this information helps, I have bricked my phone quite a few times learning how to modify it and I would suggest going ahead and trying things and making a few mistakes so you know how to unfuck your gear as some of the kind contributors have mentioned before.
Fear not, go forth and flash that little bugger to it's full potential.
abhi.eternal said:
I am following this forum closely since few months, and think I should do more with with my Defy now! I have already rooted my phone but I am still on stock Eclair. I really, really want to try CM7 but though I am quite tech-savvy, there are some things which I am still unable to get into my head! So I need someone to help me, in plain English, with the following:
1 If I install CM7, or any ROM, and then decide to go back to stock, can I?
2. I guess I can using a nandroid backup, right? BTW, what is nandroid backup?!
3. AFAIK, nandroid backs up the current ROM so that if things go wrong it can be reverted, right? If yes, how to perform a nandroid backup on Defy? How easy is it? How much of space does it take in the SD card?
4. What is sbf, recovery etc.? Why are they needed? What are the specific versions I need based on my phone:
Offtopic:
5. If I perform a 'Factory Reset', will I lose root?
Please help me understand all these; from what I have read so far everything seems so confusing!!
Click to expand...
Click to collapse
i'm new too but not new to Android...
1. Yes. And you can downgrade to 2.1 again. I did!
2. The clue is in the name, all your phones current data, apps and rom are stored on the nand memory within your Defy. The Nandroid backup takes a snapshot of all this data and stores the information from each partition on your sdcard.
3. Nandroid backup is easy. I recommend the 2nd init auto installer...that also installs recovery (custom) and is needed for cm7. Backups vary in size...mine are usually around 450mb.
4. SBF's are just official rom files, in a format readable/flashable with RSD Lite. You are on the same version as i started on. The order i went in was...
Code:
1. Root.
2. Install 2nd init. recovery installer. http://forum.xda-developers.com/showthread.php?t=1032212
3. Boot into recovery and select Backup/Restore and make a backup.
4. Download a 2.2 fixed sbf like the nordic one.
5. Download CM7. (Place in same directory as your nand backup. sdcard/clockworkmod/backups.)
6. Boot into 2nd init menu and select to boot 2nd init by default.
7. Select custom recovery and restore the cm7 nandroid.
7.5. Wipe data from custom recovery.
8. Reboot Defy while holding volume up.
9. Plug in usb and start up RDS Lite. Select fixed sbf you downloaded and press start. Once finished it will boot into CM7. (I had to pull battery after RDS Lite finished)
5. I don't think you lose root as i'm sure superuser is installed to system partition which isn't wiped when factory reset.
Oh also just for future reference. If you ever mess up (no recovery possible) or need to restore for warranty just look for the 2.51 full sbf for your region or operator and flash it with RDS Lite. You end up with a factory fresh phone and can start again
just the kind of post i need this, just one question,
you say backup/restore, I have installed 2init, but I cant see this option. Does this have a different name, or am I totally looking at the wrong menu?
ahh got it, i just needed to mess first
really stumped,
I am trying to install the leaked froyo uk build. I have installed the moto drivers and the rsd lite.
I put the .sbf in the rsd lite and connect my phone.
It sees my phone fine, but when I try to flash it just fails straight away.
I have tried enable/disabled usb debugging , but that makes no difference. Have tried wipe, but again no change,
what am I doing wrong?
Thanks in advance
Do you not get an error message? What is your current rom?
Jakethepeg said:
really stumped,
I am trying to install the leaked froyo uk build. I have installed the moto drivers and the rsd lite.
I put the .sbf in the rsd lite and connect my phone.
It sees my phone fine, but when I try to flash it just fails straight away.
I have tried enable/disabled usb debugging , but that makes no difference. Have tried wipe, but again no change,
what am I doing wrong?
Thanks in advance
Click to expand...
Click to collapse
For flashing with RSD you MUST be in bootloader mode.
Hold down volume up as you boot the phone, you will get some white text on a black screen. After this, plug your phone in via USB to your comp, once RSD reads it, load the sbf, and then start the flashing process and wait until it is completely finished and either boots your phone, or instructs you to boot manually.
The text on the phone will change as the process starts.
Hi Erra
thanks for that, I have been trying to flash in bootloader mode but I still get the message unable to flash.
Ephumuris, I am using stock uk 2.51
Are you using the latest version of RSD Lite?
You installed the motorola drivers?
Sent from my Defy on CM7.
Jakethepeg said:
really stumped,
I am trying to install the leaked froyo uk build. I have installed the moto drivers and the rsd lite.
I put the .sbf in the rsd lite and connect my phone.
It sees my phone fine, but when I try to flash it just fails straight away.
I have tried enable/disabled usb debugging , but that makes no difference. Have tried wipe, but again no change,
what am I doing wrong?
Thanks in advance
Click to expand...
Click to collapse
Would RSD Lite even recognize the phone without drivers installed?
From where can we get the latest version of RSD Lite?
Ok tried again, for the first time, managed to make a nandroid backup, (something that also wouldnt work ).
Still getting an error though, when I try and flash, interestingly though, my rsd lite, doesn't seem to be able to load roms, with their full name, (i have to shorten it to uk.sbf or something along those lines).
Tried to flash the froyo uk tmoby leaked rom (11 version), and the error message I get is Failed flashing process (0x7100); phone connected.
Version I am on for rsd lite is 4.9 multiflash/ multi flex.
Thanks again for all your help and patience
Feel such a noob with this, I never had this many issues with my old xm5800
the version of rsd lite is compatible with 2.51 isnt it?
Or do i need to grab an older version, just noticed this got released in march.
ephumuris said:
i'm new too but not new to Android...
1. Yes. And you can downgrade to 2.1 again. I did!
2. The clue is in the name, all your phones current data, apps and rom are stored on the nand memory within your Defy. The Nandroid backup takes a snapshot of all this data and stores the information from each partition on your sdcard.
3. Nandroid backup is easy. I recommend the 2nd init auto installer...that also installs recovery (custom) and is needed for cm7. Backups vary in size...mine are usually around 450mb.
4. SBF's are just official rom files, in a format readable/flashable with RSD Lite. You are on the same version as i started on. The order i went in was...
Code:
1. Root.
2. Install 2nd init. recovery installer. http://forum.xda-developers.com/showthread.php?t=1032212
3. Boot into recovery and select Backup/Restore and make a backup.
4. Download a 2.2 fixed sbf like the nordic one.
5. Download CM7. (Place in same directory as your nand backup. sdcard/clockworkmod/backups.)
6. Boot into 2nd init menu and select to boot 2nd init by default.
7. Select custom recovery and restore the cm7 nandroid.
8. Reboot Defy while holding volume up.
9. Plug in usb and start up RDS Lite. Select fixed sbf you downloaded and press start. Once finished it will boot into CM7. (I had to pull battery after RDS Lite finished)
5. I don't think you lose root as i'm sure superuser is installed to system partition which isn't wiped when factory reset.
Click to expand...
Click to collapse
When is the time to do full wipe??
Oops i missed that. Straight after the step of restoring the cm7 nandroid.
Step 7.5. Wipe data from custom recovery.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Disclaimer: We are not responsible for any damages on your device.
Original Slim Features:
The Real Dark Slim
Notification drawer & lockscreen Shortcuts
SlimPIE
Customizable NavBar
QuickSettings custom Shortcuts
Full hardware key rebinding!
SlimCenter
..and much more!
Need to find a feature? Want to see screenshots? Check out SlimBean's features!
Changelog
Find our latest Changelog go here
Chat with the slim team and other slim users
IRC: #slimusers @ freenode
New to IRC? Don't have a native app? Try the Freenode web client [link] or the Firefox extension Chatzilla [link]
Google+ [link]
Twitter [link]
Facebook [Link]
Installation instructions
For Most Users
Please keep in mind if a special instruction is needed it will be noted in the Changelog
Download the latest build from [here]
Gapps ( if you don't have it already) from [here]
!Recommended! Full wipe, and manual format /system
Flash ROM and the gapps you want, reboot
FAQ
Check out out FAQ before posting! Keeps more common questions answered in one place!
To get root working go to Settings/Developer options/
Then change the option "root access" to "apps and adb".
Help us out!
If you want to help us by translating slim to your language check out Crowdin.net and submite your translations.
Or consider a donation.
Thanks!
You can find the full list of credits here
Source
Please visit here for the rom source code.
Kernel source can be found here
XDA:DevDB Information
Slim Bean jfltetmo [stable 2.2], a ROM for the T-Mobile Samsung Galaxy S 4
Contributors
blk_jack
ROM OS Version: 4.3.x Jellybean
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 2.2
Stable Release Date: 2013-12-03
Created 2013-08-18
Last Updated 2013-12-08
SlimBean 4.3 stable 2.2
Stable 2.2 is live! Please read the Changelog for more details including proper upgrade/installation methods, as well as notes on activating root and restoring with Titanium Backup.
Changes, Features & Fixes:
Changelog for stable 2.2
SuperUser security fixes
Several BT fixes
Selinux security ehancements
LID control fix
some translation upstrem
nearly all device got device and kernel updates
Please note these builds are under heavy development!
Known issues
Headset in-call mic uses phone
HDR Camera mode may need improvements, but should at least work
4.3 mini-FAQ
Q) I'm stuck at the boot logo and/or a boot loop!
A) Make sure you use TWRP 2.5.0.2. TWRP 2.6 and other recoveries can cause boot loops & hangups
Q) Root doesn't work!
A) From a clean build you need to enable root access for Superuser itself. This is different from 4.2.2 in which Superuser by default had root access on a new install. To do this, go to Settings -> Developer options -> Root access. If an app attempts to request root access before Superuser itself has access, it may cause problems with that app in the future where root requests are silently denied.
Q) Titanium Backup isn't restoring apps!
A) Change the backups folder to storage/emulated/legacy.
If you use Philz recovery 5.10.0 you must upgrade to 5.11.0 or you will lose radio!
Since the SGS4 is so new, development is happening very rapidly. This should be taken into consideration when flashing any 4.3 AOSP-based builds on the device. Known issues will be listed here.
I can't seem to get past the bootloop. rebooting repeatedly doesn't seem to do anything. if I go back to recovery, it won't even let me wipe. can't mount data. I have to go back and factory reset, then reboot into recovery to get wiping to work again. then I can get back to the o.s.
quickquest88 said:
I can't seem to get past the bootloop. rebooting repeatedly doesn't seem to do anything. if I go back to recovery, it won't even let me wipe. can't mount data. I have to go back and factory reset, then reboot into recovery to get wiping to work again. then I can get back to the o.s.
Click to expand...
Click to collapse
Something is definitely wrong on your end. You're gonna have to give me more info, like your recovery and what steps you did to install the ROM.
If it's stuck at the boot logo, try wiping dalvik cache.
Sent from my SGH-I337M using Tapatalk 4
I guess wasn't as clear as I thought. i can get the system to boot once, but trying a reboot, it will bootloop.
I'm using the latest twrp, wipe everything but extsd, format system, install 4.3 and 4.3 gapps. I can get it to boot and everything looks good from there. however, if I reboot, it gets stuck in the bootloop. pulling battery or long press power to turn off and boot again doesn't help. I can get to recovery, but if I try to wipe cache and dalvik, it says something about cant mount /data and says it failed. then I have to go back to format system. after I do that, the text on screen says I may have to reboot recovery to access /data. then I can get it to boot again. of course I have to reinstall all of my apps again.
if I do anything that requires a reboot, it will start to bootloop again, and I have to format system to get /data to mount.
quickquest88 said:
I guess wasn't as clear as I thought. i can get the system to boot once, but trying a reboot, it will bootloop.
I'm using the latest twrp, wipe everything but extsd, format system, install 4.3 and 4.3 gapps. I can get it to boot and everything looks good from there. however, if I reboot, it gets stuck in the bootloop. pulling battery or long press power to turn off and boot again doesn't help. I can get to recovery, but if I try to wipe cache and dalvik, it says something about cant mount /data and says it failed. then I have to go back to format system. after I do that, the text on screen says I may have to reboot recovery to access /data. then I can get it to boot again. of course I have to reinstall all of my apps again.
if I do anything that requires a reboot, it will start to bootloop again, and I have to format system to get /data to mount.
Click to expand...
Click to collapse
The lack of /data in recovery worries me the most. That's definitely not good and I'm not sure how that would be happening.
Are you doing all this w/ your device plugged in? Can you try not plugging it in if that's the case?
EDIT: I've had an issue where sometimes on reboot w/ my device plugged in I need to wipe dalvik to continue booting. I'm not sure why this is at the moment but it's always fixed if I reboot to recovery and wipe dalvik cache.
i started not plugged in at 75% batt. I installed, activated, and installed all apps. ran titanium backup, and it said something about restoring android I'd. clicked yes, and at reboot it started to loop. tried wiping everything but system, didn't want to reinstall apps. tried to reflash zip, but failed because it couldnt mount /data.format system worked. reinstalled all apps. I thought maybe titanium backup hosed it somehow so i stayed away from it. wanted to change font with ifont. reboot looped again. wiping gave /data error again. format system worked without reflashing zip. got it running, oddly enough with the changed font.
the second format was plugged in, as at that point I was down to about 45% batt. As long as I don't reboot, everything seems good. hesitant to reboot again in case it loops.
quickquest88 said:
i started not plugged in at 75% batt. I installed, activated, and installed all apps. ran titanium backup, and it said something about restoring android I'd. clicked yes, and at reboot it started to loop. tried wiping everything but system, didn't want to reinstall apps. tried to reflash zip, but failed because it couldnt mount /data.format system worked. reinstalled all apps. I thought maybe titanium backup hosed it somehow so i stayed away from it. wanted to change font with ifont. reboot looped again. wiping gave /data error again. format system worked without reflashing zip. got it running, oddly enough with the changed font.
the second format was plugged in, as at that point I was down to about 45% batt. As long as I don't reboot, everything seems good. hesitant to reboot again in case it loops.
Click to expand...
Click to collapse
From what I'm reading there are issues w/ TWRP 2.6. Downgrade to TWRP 2.5 and your issues should go away.
I couldn't find twerp 2.5, so I installed cwm 6. now i can't get past the bootloop no matter what. I'm not getting an error about /data, but nothing, not even a format system will get the damn thing to boot to o.s.
I went through and formatted everything in the mounts menu one by one. still nothing.
I spoke too soon. now I'm getting an error when trying to format system that says cwm can't mount /data or /android.secure and /sdcard
now I seem to be soft bricked. I can't get it to go past the Samsung galaxy s4 screen. can't format.
quickquest88 said:
I couldn't find twerp 2.5, so I installed cwm 6. now i can't get past the bootloop no matter what. I'm not getting an error about /data, but nothing, not even a format system will get the damn thing to boot to o.s.
I went through and formatted everything in the mounts menu one by one. still nothing.
Click to expand...
Click to collapse
You sure you don't have a bad build?? None of my testers are having these issues. Grab it here & flash it w/ goomanager or odin/hemidall http://goo.im/devs/OpenRecovery/jfltetmo
thanks fro the link. twrp 2502 got me out of the softbrick. with cwm, nothing seemed to work to get it past the samsung screen.
twrp got me to the point that i can at least get it running again, however, not even 2502 fixes the original issue of being unable to reboot. this time after getting 4.3 installed, i rebooted at the screen asking what language. it didnt get past the samsung screen. went back into recovery and wipe/format data/yes and then reboot. that got me back into the o.s.
this is really strange, i wish i knew more about developing. as long as i dont reboot, im ok. good thing this isnt windows, or id be in trouble, hah!!
I had no problems installing with the latest regular version of CWM from ROM Manager. Got root working just by tinkering around in superuser in settings... Not sure what I did but root works. Overall very very nice for a beta release!
I have one inane question(hope I didn't miss it somewhere): is the setting for lock screen rotation removed? It seemed to me to be buggy on cm10.2 anyway. Also can't remember if the phone app rotated to landscape in 4.2.2 build, but I think it did. Again, meaningless issues really, just wondering.
Thanks for the hard and awesome work!
Loving the beta build! It's almost fully stable! All convenient features are working as should!
I wants to say Great job! Got it all set up to find the camera won't work. Give error "Can't connect to camera". I thought OK, I'll try focal. Did the same thing initially then soft bricked the phone. Had to start from scratch.
I did notice as I scrolled through app list in TB that it didn't list a camera app at all.
Bowmanspeer said:
I wants to say Great job! Got it all set up to find the camera won't work. Give error "Can't connect to camera". I thought OK, I'll try focal. Did the same thing initially then soft bricked the phone. Had to start from scratch.
I did notice as I scrolled through app list in TB that it didn't list a camera app at all.
Click to expand...
Click to collapse
It'll be under Gallery2
Sent from my SGH-I337M using Tapatalk 4
Flashed 8/20/13 using TWRP 2.5.0.2. No problem, other than some freezing apps here and there. Cleared caches, fixed permissions, and all seem fine now.
Will now run it through my battery tests, etc.
Thank you blk_jack!
I'm not sure what happened to my phone. Apparently twrp 2.6 caused some weird issue that wasn't fixed by reflashing with another recovery.
I had to Odin back to stock (freaked me out cause first Odin attempt failed, second passed, then I had to go back and format system again), and upgrade from there. Now it works like it should, rebooting and everything with oudhs.
Sent from my SGH-M919 using xda app-developers app
quickquest88 said:
I'm not sure what happened to my phone. Apparently twrp 2.6 caused some weird issue that wasn't fixed by reflashing with another recovery.
I had to Odin back to stock (freaked me out cause first Odin attempt failed, second passed, then I had to go back and format system again), and upgrade from there. Now it works like it should, rebooting and everything with oudhs.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
This is a notice for others on TWRP 2.6. Please read the OP (post 3 specifically). It has been updated to contain a mini-FAQ for 4.3 that should solve 99% of the issues I'm seeing on XDA.
Any way to get stock DPI?
Sent from my Nexus 7 using Tapatalk 4
I cant wait til the ota comes out to try out lollipop. I've read some articles that it can be flashed via the "official" way a.k.a. the fastboot way but i need to wipe all data. I already have a unlocked boot loader so maybe theres a way to skip the formatting? I found an article that i can edit the fastboot flash script to not wipe my device but its noted that its not guaranteed to work. Have anyone tried this yet? Maybe just like updating roms that dont need wiping the device?
The androidpolice webpage http://www.androidpolice.com/2014/1...ilable-for-the-2013-wifi-nexus-7-and-nexus-5/
And
http://www.howtogeek.com/176284/how...-without-waiting-by-flashing-a-factory-image/
Just did the update to Lollipop dev preview from the last "L" preview without wipe (via editing out the -w from the script). Haven't had a problem doing this before, aside from having to unfreeze stock Chrome (I use Chrome Beta) and uninstalling CF.Lumen drivers. So far, it's working fine for me. However, the boot animation stayed on quite a bit longer than usual before it reached the "Android is upgrading" screen. It was on the boot animation for a good 3-5 minutes, so don't consider hard resetting it so soon.
Update: I ended up having to do the "SetupWizard" fix to restore notification pull-down functions, and possibly Google syncing related features.
http://www.androidpolice.com/2014/0...at-refuses-to-pull-down-after-android-update/
Good luck with the upgrade without wipe.
divadkha said:
Just did the update to Lollipop dev preview from the last "L" preview without wipe (via editing out the -w from the script). Havent had a problem doing this before, aside from having to unfreeze stock Chrome (I use Chrome Beta) and uninstalling CF.Lumen drivers. So far, its working fine for me. However, the boot animation stayed on quite a bit longer than usual before it reached the "Android is upgrading" screen. It was on the boot animation for a good 3-5 minutes, so dont consider hard resetting it so soon.
Update: I ended up having to do the "SetupWizard" fix to restore notification pull-down functions, and possibly Google syncing related features.
http://www.androidpolice.com/2014/08/07/how-to-fix-missing-home-and-recents-buttons-and-notification-shade-that-refuses-to-pull-down-after-android-update/
Good luck with the upgrade without wipe.
Click to expand...
Click to collapse
Thank you for your information. But in your case its android l to android l which is not quite a huge jump. But I'm from kitkat to lollipop. Will that be any difference?
ImjuzCY said:
Thank you for your information. But in your case its android l to android l which is not quite a huge jump. But I'm from kitkat to lollipop. Will that be any difference?
Click to expand...
Click to collapse
You don't HAVE to wipe data before updating to a new OS version but from my personal experience I very strongly believe that wiping the data will give a more reliable update in the long term and have less chance of buggy user installed apps. One thing to think about is the fact that an OTA will NOT ever wipe data. With "minor" updates (like 4.4.3 to 4.4.4) I just fastboot flash the system image and whatever else is necessary which will keep all of the user apps installed and all the settings intact. With "major" OS updates I sometimes but not always do a factory reset from inside TWRP which will not wipe the storage then use TWRP to go into the bootloader and flash whatever from there. With the flash_all batch file modified you could flash the factory image (L preview) and have a clean install and not have your storage wiped. If you instead fastboot flash the bootloader, boot and system images separately instead of using the flash_all batch file you don't replace the custom recovery (TWRP) with the stock recovery. If you don't have a custom recovery installed and want a clean install you have no choice but to wipe everything. Save what you want from your storage to your computer. If you do have a custom recovery make a backup (nandroid) first. But... my personal opinion is that an OTA will not be as reliable as a clean install, again, not that I always do a clean install. Another thing to think about is how important is a clean install now anyway, the official 5.0 update isn't too far down the road. Do what feels comfortable for you, you have multiple choices.
wantabe said:
With "major" OS updates I sometimes but not always do a factory reset from inside TWRP which will not wipe the storage then use TWRP to go into the bootloader and flash whatever from there.
Click to expand...
Click to collapse
Thanks for your detailed explanation. But I have a question. You said you sometimes do a factory reset from TWRP *which will not wipe storage*. But according to TWRP's website, factory reset means wiping everything. Isn't it? Or you mean the sdcard partition?
ImjuzCY said:
Thanks for your detailed explanation. But I have a question. You said you sometimes do a factory reset from TWRP *which will not wipe storage*. But according to TWRP's website, factory reset means wiping everything. Isn't it? Or you mean the sdcard partition?
Click to expand...
Click to collapse
Yes and no! Doing a factory reset from your device settings "Settings/Backup & reset" will absolutely wipe Everything on your device. If you do a factory reset from inside TWRP it will Not wipe your device storage. When you open TWRP and tap on "Wipe" the screenshot shows what you will see. Excuse the screenshot, it's hard to get the camera to focus on a shiny screen. The only way to do a factory reset/wipe data that I know of without wiping the storage is with a custom recovery.
wantabe said:
Yes and no! Doing a factory reset from your device settings "Settings/Backup & reset" will absolutely wipe Everything on your device. If you do a factory reset from inside TWRP it will Not wipe your device storage. When you open TWRP and tap on "Wipe" the screenshot shows what you will see. Excuse the screenshot, its hard to get the camera to focus on a shiny screen. The only way to do a factory reset/wipe data that I know of without wiping the storage is with a custom recovery.
Click to expand...
Click to collapse
Oh! Thank you very much for the explanation. Wiping data partition means clearing all user installed apps right? If its true then I rather wait for the ota. I don't wanna waste too much time on backing up and restoring apps. Thanks anyway
ImjuzCY said:
Oh! Thank you very much for the explanation. Wiping data partition means clearing all user installed apps right? If its true then I rather wait for the ota. I don't wanna waste too much time on backing up and restoring apps. Thanks anyway
Click to expand...
Click to collapse
Correct! Wiping the data will always remove the user installed apps. Wiping from inside your device settings or from inside TWRP will determine if your storage gets wiped. Don't forget... there is more than one way to flash a factory image, in this case the Android L preview, without wiping any data.
1. Modify the flash_all.bat that is inside the factory image with a text editor (notepad) removing the text -w. Takes like 5 seconds to modify the text.
fastboot flash bootloader bootloader-flo-flo-04.04.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-razor-lpx13d.zip
fastboot flash bootloader bootloader-flo-flo-04.04.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot update image-razor-lpx13d.zip
2. Fastboot flash the bootloader, boot and system images.
Either way it takes longer for android L to boot up the first time than it does to flash the images. Just saying!
Backup it all! (Before execution of some operations that can cause data loss)
You just need to download this tool.
If your bootloader is really unlocked, then they'll be no problems out there!
Make sure your Nexus Device is connected to your Computer with a MicroUSB-Cable!
But do never use a slack joint cable! They'll cause many problems there!
Launch the Toolkit and it should detect your Tablet!
Go to the Installation-Guide on the Main-Menu and then install the GoogleADB-Driver.
That's the 1st(2nd?) ever time i'm using the USB-Icon on a Post!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
Go to the BackUp-Menu and execute a full-Android ADB-Backup
Make sure your device is connected to the Computer!
And after the backup then make sure the BackupFile is there to make sure that to avoid a Blank 0B-File or no file at all!
If you've got any questions left then ask me anytime! Anytime you ever want!
All the best!
❤Hannah(❤❤❤!)
---------- Post added at 07:41 PM ---------- Previous post was at 07:39 PM ----------
Hannah Stern said:
Go to the BackUp-Menu and execute a full-Android ADB-Backup
Click to expand...
Click to collapse
Sorry! What i mean is the Full N'Android /W/ Backup!
All the best,
Hannah:laugh:
I'm so disconcerted right now. I have the Verizon LG G3, everything stock but rooted, and just recently was fiddling with the Bump bootloader bypass. Everything was going well, and I remember this thread from a while back because I'm heavy on customizing my phone. Long story short, I download the "Clean Lockscreen" mod, flashed it, and now I get a "unfortunately the process com.android.systemui has stopped" when I boot up my phone. Skips the lockscreen, the home pages load up normally, but the only thing I can interact with is the Power Menu and the "Ok" to dismiss the "unfortunately..." message.
(mod was directly from http://forum.xda-developers.com/lg-g3/themes-apps/theme-g3-clean-look-kk-4-4-2-t2834442)
Short of factory resetting, is there any quick dirty fix that will let me stop having a panic attack? I'm so lazy/dumb for not having a backup, but I was so eager to start flashing things I couldn't be bothered to set one up. I gambled and lost. Hard.
Also, is there anyway to extract my photos before, worst case scenario, I do have to factory reset? I have so many pictures since I bought this phone that losing them all because of this little mistake is what's driving me crazy, on top of losing every little tweak I did here and there for the past few months.
Lastly, if I do factory reset, does that also erase everything on my SD card? The Quick Circle case is on there pretty snug.
**My theory is that someone with a Verizon LG G3 V10B (didn't update because I was afraid to lose root) has the original file that whatever the "Clean Lockscreen mod" file replaced, and I can just flash that and be sane again** please please please
TL;DR --> Verizon user, got Bump, got excited, started flashing things with no backup (dumb dumb dumb), going crazy, now hoping that I can replace that one thing I flashed with the stock original and be fine (whatever the Clean Lockscreen mod changed)
BE VERY CAREFUL READING THIS POST, IF YOU FOLLOW MY SUGGESTIONS AND LOSE YOUR PICTURES FOR ANY REASON I AM NOT RESPONSABLE.
~ You shoulda done a backup.
Just booting into recovery is 90% of the work needed to do a backup, The other 10% of the work is just clicking "backup" and waiting 15 seconds. (You were just lazy/impatient, Not dumb.)
~ Did you flash a mod that was specifically for your exact model?
~ Can you still get into your custom recovery?
~ Before you try anything in my list I would first see if you can locate the stock lockscreen files on the internet for your model and flash them back onto your phone.
~ The FC issues you're having is usually related to not having the proper permissions.
If you can still go into recovery, Boot into recovery and wipe the Cache, Dalvik cache, & go to advanced and click fix permissions.
~ It looks like to me that your launcher may be pooched.
(In my experience the lockscreen/keyguard seems to be tied to the actual launcher/UI itself, Which is why I believe your UI is broken)
Because you can't install a new launcher in the operating system I would try and find a flashable .zip version of another launcher, like nova launcher or something and flash that in recovery.
~ I'm 99% sure a Factory reset won't help your situation.
I'm almost positive you're gonna have to re-flash your firmware to return your phone to working condition.
~ Try a dirty flash, Using same type of rom. (YOU "COULD" LOSE YOUR PICTURES DOING THIS, BUT PROBLY WON'T, Use as one of your last resorts)
Try and find a flashable .zip rom that is flashable in recovery, One that is the same type as your current rom and try a dirty flash "without" wiping anything.
Only flash using the recovery without wiping "OR YOU WILL LOSE ALL YOUR PICS", Also if you flash using your PC it WILL DELETE EVERYTHING.
(If your current rom is stock or stock based rom, Find a stock/stock based .zip based rom and dirty flash in custom recovery)
(If your current rom is AOSP based rom, Find a AOSP based .zip based rom and dirty flash in custom recovery)
After you dirty flash, Backup your pictures & anything else you may need then do a clean flash.
~ There are apps that can recover "deleted/inaccessible" data. (THIS IS ABSOLUTLY LAST RESORT, DON'T TRY THIS UNTIL YOU HAVE ABSOLUTLY NO OTHER OPTION.)
When you delete something off a storage device, It doesn't delete the actual data, It deletes the operating systems directories where the said info is stored, Resulting in what looks like to the operating system as "empty space" Which it actually isn't.
If you "have to" wipe your phone before being able to recover your pictures, Avoid installing ANYTHING you can (If/when possible) until you recover your pictures if you have to wipe your phone, Because anything that goes on your phone while your stuff is deleted CAN be overwritten. (You're gonna have to google a bit to find what apps are capable of this on android.)
Hi,
I searched online for 2 hours but I see a lot of mixed, outdated articles, videos. For example Hasoon's app link doesn't work, or the cyanogenmod installer link for your phone is giving me 404.
I don't want to do something stupid so can someone tell me or show me a guide on how to install this?
My phone is from Rogers (contract ended). I just want a fast and light weight android without bloatware and nice features.
Will I have to find a cyanogenmod release from someone who use Rogers, or can you use the same build on that's built for M8 regardless of your phone company?
Thanks a lot.
Have you done anything to the phone yet (unlock bootloader, s-off, root, etc.) or still just fully stock?
Is the phone currently on Lollipop? You'll want updated hboot to run current CM12.1.
Don't bother with toolkits and the like. The toolkits haven't been updated in over a year, contain obsolete files, and that will cause you more problems than anything. The steps are not that hard to do "manually", and that is a much better learning process. The toolkits shortcut that learning process; putting you in a position to get into a jam, with no knowledge of how to get out of it.
Thanks a lot for replying. I unlocked the bootloader, s is off, but I don't know how to root. I think it's superSU right? If so, I assume I will do this by installing this zip after I flash the cyan mod?
I downloaded these to my phone:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I assume I just have to format/adv format everything and install these zip files using TWRP, right? If so, that wasn't hard
But I have another problem. I don't have an SD card or OTG cable to store these zip files outside the phone. I have usb flash memory/stick, HDDs but AFAIK I need OTG cable to use them with my phone.
Also another thing that concerns me is the new Android version is coming next week, right? So should I wait for it and use that cyan mod?
Are you able to get OTA updates with cyan as easily without having to flash your phone every time?
Thanks again
lachdanan said:
Thanks a lot for replying. I unlocked the bootloader, s is off, but I don't know how to root. I think it's superSU right? If so, I assume I will do this by installing this zip after I flash the cyan mod?
Click to expand...
Click to collapse
No need to flash SuperSU to root after flashing CM.
Go into Developer's Options in phone's settings (may need to tap version number 7 times to make Dev Options appear) then turn on root there.
lachdanan said:
I assume I just have to format/adv format everything and install these zip files using TWRP, right? If so, that wasn't hard
Click to expand...
Click to collapse
Before doing anything, make a TWRP backup of your current (presumably stock Sense) ROM.
Then backup any user data you want to keep, by method of your choice (Titanium Backup, cloud, copy to PC, etc).
Then do a wipe. I would only recommend the default Wipe option (user data, cache and Dalvik) in TWRP. Right in TWRP, it says "most of the time, this is the only wipe you will need" (or words close to that effect) and it says that for good reason.
You certainly don't want to wipe "everything". If you wipe internal storage, you will lose the TWRP backup I just told you to make. Plus you will wipe the ROM and gapps zips you are going to flash, if you put them on internal storage.
Some folks swear by wiping system when flashing ROMs. I don't like this, since if for some reason the ROM fails to flash, you are then stuck with no OS (although you will have a TWRP backup, that I just told you to make). If you run into problems, you can always wipe system later and flash again. But honestly, after many ROM flashes on several different devices, and I've never once had to wipe system, that I recall. Unless of course the ROM instructions require to wipe system. If that is the case, follow the instructions.
After default wipe, flash the ROM, and flash gapps. Then reboot.
lachdanan said:
But I have another problem. I don't have an SD card or OTG cable to store these zip files outside the phone. I have usb flash memory/stick, HDDs but AFAIK I need OTG cable to use them with my phone.
Click to expand...
Click to collapse
I don't follow what the problem is. It looks like you have the files on a PC. Just connect your phone by USB, then copy and past the files to the phone's internal storage.
Don't know why you want to store the files "outside the phone" (and not on the PC) unless you are talking about wiping internal storage. Again, it isn't necessary to do that.
lachdanan said:
Also another thing that concerns me is the new Android version is coming next week, right? So should I wait for it and use that cyan mod?
Click to expand...
Click to collapse
It usually takes a bit of time for a new Android version to be ported over to a respective device. Than a bit more time, for it to be fairly stable. So its up to you, but I say why wait. You can always flash again when CM13 (or whatever its going to be called) is released on the M8.
One of the things about flashing ROMs, is it can be addictive. So if you have the urge and time to do it now, just do it!
lachdanan said:
Are you able to get OTA updates with cyan as easily without having to flash your phone every time?
Click to expand...
Click to collapse
I actually don't use CM on the M8, so check the CM thread for any discussion on this.
Even if OTA updates aren't functional (no idea if they are or not), you can often download and "dirty flash" new updates (like nightlies). Dirty flash, means you just wipe cache and Dalvik and flash the ROM, keeping user data. Its very fast, since you don't need to setup the phone again.
Although, sometimes a dirty flash won't work, and you need to do a full flash. When CM13 comes out, you will probably need to do a full wipe before flashing it. And likewise, you probably won't want to do an OTA update to CM13 either.
Thanks a lot man, you cleared many of my questions. Regarding the storage, sorry they are already on my phone, so the phone has internal storage and another separate storage? I thought HTC One M8 had a single storage inside so if you delete things, everything is deleted.
But since you said don't delete system, then this is not an issue?
Also by system, does it mean actual stock android system files? Won't these files conflict with CM's own system files? Or if they are bloated with time, usage etc, then this will leave these unnecessary files behind?
Thanks again
lachdanan said:
Regarding the storage, sorry they are already on my phone, so the phone has internal storage and another separate storage? I thought HTC One M8 had a single storage inside so if you delete things, everything is deleted.
Click to expand...
Click to collapse
Nope, the storage is actually partitioned into something like 41 separate partitions: system, hboot, recovery, radio, data, boot, and (of course) many more.
So when you say you want to wipe "everything" I said you don't want to do this, and I really mean it.
Plus, one of the Advanced wipe options in TWRP is the removable SD, which most folks will not want wiped, most of the time.
So again, use the default wipe option in TWRP. Only pick the Advanced options, if you know exactly what you are doing, and fully understand the result of wiping that selection.
The "default" TWRP wipe just wipes user data, cache and Dalvik. Internal storage (which is data/media) is actually not touched, and that is most likely where you placed the ROM and gapps files (plus its the default location for TWRP backups, Titanium Backup and some other things).
lachdanan said:
But since you said don't delete system, then this is not an issue?
Click to expand...
Click to collapse
Correct.
lachdanan said:
Also by system, does it mean actual stock android system files?
Click to expand...
Click to collapse
If you are still on the stock ROM (haven't flashed any ROM yet, was I assume is the case) then YES, system partition is where the actual stock ROM (stock Android system files) are currently located.
lachdanan said:
Won't these files conflict with CM's own system files? Or if they are bloated with time, usage etc, then this will leave these unnecessary files behind?
Click to expand...
Click to collapse
Nope, when a ROM is successfully flashed, it will wipe system, then install the new ROM on the system partition.
This is another reason why I say its not necessary to manually wipe system in TWRP. It will happen anyway when you flash the ROM. But if for some reason the ROM fails to flash (not unheard of, for various reasons), you will still have have a working phone if you didn't wipe system.
Thanks. I made a stupid mistake before reading your last post, now it seems like my phone's data storage is completely empty I restarted into bootloader and added TWRP to it again using Windows. But then I chose restart on that bootloader menu and now the phone screen is stuck in HTC android boot screen. I couldn't turn the phone off or restart. Do you know how to fix this?
I managed to fix it and now I am in cyan Looks really good, I will be customizing it now but it feels snappy
Thanks again man