Related
OK, I might get trolled unrelentlessly, but right now I don't care...
The girlfriend loved the look of some of these themes, and asked me to install one. I didn't realize at the time that not being on a TW-based ROM that it would fail as badly as it has.
At this point in time, I can get into the OS, see her home screen. Google acct info is completely gone, home button does not work, and no matter what order of operations I use in terms of bringing this thing back to life will work. HELP.
TB will fail to restore ACTUAL settings for "Account", etc. If/when it does finish, the phone boots straight to boot-animation, but does not go any further, period.
I've been at this for 2hrs now, and I'm getting nowhere. Do I need to install a TW-based ROM, THEN wipe again and install AOSP like she had before?
For clarification, I've tried wiping EVERYTHING, including full reset in CWM.
The problem is that I get a FC on "False.4.1.2-eng-nocoast.20121030.123453", and the status-bar is completely gone. I can use TB to remove the "False" apk, but I can't find a way to get the status bar back. I've tried installing the ROM fresh after full wipe of all caches, plus factory-wipe from within CWM. All this amounts to is the ROM booting to its splash-screen without continuing, OR getting to Android, but the home button doesn't work, and there is no way to associate a Google account with it at that point in time. I thought I could remedy this by simply having TB update.zip run before first boot after fresh install, but even though it allows the Play store and other Google apks to install, it won't let me associate an account for Google. The list consists of Exchange and something else.
Basically - I need to know if this means I have to Odin back, start over...or if there is some way to get the phone to recognize the 2 missing components without doing that.
I do have one nandroid, but it was done right after the initial realization of failure with the theme install, so it essentially puts me back to square-one.
You need to be on a tw rom; as that theme is tied into the tw framework.
What you should do is:
-do a full wipe in recovery
-download / flash your tw rom of choice
-flash the theme
In the future, tw / aosp themes are meant to be used on the respective rom source.
teh roxxorz said:
You need to be on a tw rom; as that theme is tied into the tw framework.
What you should do is:
-do a full wipe in recovery
-download / flash your tw rom of choice
-flash the theme
In the future, tw / aosp themes are meant to be used on the respective rom source.
Click to expand...
Click to collapse
Would this enable me to then flash back to an AOSP ROM?
disturbd1 said:
Would this enable me to then flash back to an AOSP ROM?
Click to expand...
Click to collapse
After you do the full wipe in recovery, you could flash any rom, tw or aosp that you wanted; so yessir.
teh roxxorz said:
After you do the full wipe in recovery, you could flash any rom, tw or aosp that you wanted; so yessir.
Click to expand...
Click to collapse
As I mentioned, I've tried doing a full wipe in recovery, and flashing the ROM she had before, to no avail
disturbd1 said:
As I mentioned, I've tried doing a full wipe in recovery, and flashing the ROM she had before, to no avail
Click to expand...
Click to collapse
What recovery are you using? If you flash twrp and wipe the system, along with the caches and factory, that will definitely be the end of that.
And you flashed the same rom with the theme?
teh roxxorz said:
What recovery are you using? If you flash twrp and wipe the system, along with the caches and factory, that will definitely be the end of that.
And you flashed the same rom with the theme?
Click to expand...
Click to collapse
Using CWM 6, touch version. Yeah, wiped everything, and flashed same ROM. Did not flash that theme again.
disturbd1 said:
Using CWM 6, touch version. Yeah, wiped everything, and flashed same ROM. Did not flash that theme again.
Click to expand...
Click to collapse
If you're able to get into the os, I would install the goo manager app > menu > install open script recovery > install twrp recovery. Then boot into recovery, make sure to wipe the system. That should do it, cuz just seems something isn't wiping. Additionally, I may re-down that rom if its giving you issues; did you modify the zip at all?
teh roxxorz said:
If you're able to get into the os, I would install the goo manager app > menu > install open script recovery > install twrp recovery. Then boot into recovery, make sure to wipe the system. That should do it, cuz just seems something isn't wiping. Additionally, I may re-down that rom if its giving you issues; did you modify the zip at all?
Click to expand...
Click to collapse
I'll give that a try. I didn't modify the ROM; I never do, I just install them. It's the Liquid Smooth AOSP, and it has been just that up until I had my "senior moment" last night.
disturbd1 said:
I'll give that a try. I didn't modify the ROM; I never do, I just install them. It's the Liquid Smooth AOSP, and it has been just that up until I had my "senior moment" last night.
Click to expand...
Click to collapse
Ha, well they'll creep up on all of us at some point. Though install the twrp recovery, make sure to wipe both caches, factory reset, and system > install the rom, no theme, and you should be good to go, bro.
teh roxxorz said:
Ha, well they'll creep up on all of us at some point. Though install the twrp recovery, make sure to wipe both caches, factory reset, and system > install the rom, no theme, and you should be good to go, bro.
Click to expand...
Click to collapse
So, I got TWRP 2.3 on, wiped everything, flashed the ROM, Gapps, and ran Fix Permissions (which resulted with "failed"), and rebooted. Same story - goes into Android, home button doesn't work, and no Google account associated with the phone. Also, no menu option to add one. There is only "Corporate" and "Email".
disturbd1 said:
So, I got TWRP 2.3 on, wiped everything, flashed the ROM, Gapps, and ran Fix Permissions (which resulted with "failed"), and rebooted. Same story - goes into Android, home button doesn't work, and no Google account associated with the phone. Also, no menu option to add one. There is only "Corporate" and "Email".
Click to expand...
Click to collapse
When you boot into the os, you have supersu and allows the usage of root apps?
teh roxxorz said:
When you boot into the os, you have supersu and allows the usage of root apps?
Click to expand...
Click to collapse
This particular ROM uses a different SU app that I hadn't seen before using it, but I have the same phone with the same ROM, and it runs as the title says, "Liquid Smooth". So it's not an issue with the ROM or how it was packed. I'm trying a different ROM now, to see if I have better luck.
disturbd1 said:
This particular ROM uses a different SU app that I hadn't seen before using it, but I have the same phone with the same ROM, and it runs as the title says, "Liquid Smooth". So it's not an issue with the ROM or how it was packed. I'm trying a different ROM now, to see if I have better luck.
Click to expand...
Click to collapse
I was going to suggest trying a different wrong, because the instructions I gave you should have worked, not to say you're doing it wrong. If i remember, that was was ported, so it could have inherent issues, or some unknown ones; I haven't flashed it yet, so I can't advise. Flash aokp, I know everything is working there.
teh roxxorz said:
I was going to suggest trying a different wrong, because the instructions I gave you should have worked, not to say you're doing it wrong. If i remember, that was was ported, so it could have inherent issues, or some unknown ones; I haven't flashed it yet, so I can't advise. Flash aokp, I know everything is working there.
Click to expand...
Click to collapse
OK, here's the latest:
-Wiped everything in TWRP - caches, system, data, basically every option for wiping in the menu.
-Flashed AOSP ROM by codefireX, yet another that I've used before, and has worked almost flawlessly for me.
-Flashed JusTunBean's Aroma installer for gapps, been using it for months with no issues.
-Boots to OS, home button now works, and the status bar is there. Immediately get a FC on Gmail, without opening any apps.
-Still no Google account, and no option within "Accounts" to add one. <----main problem at this point.
disturbd1 said:
OK, here's the latest:
-Wiped everything in TWRP - caches, system, data, basically every option for wiping in the menu.
-Flashed AOSP ROM by codefireX, yet another that I've used before, and has worked almost flawlessly for me.
-Flashed JusTunBean's Aroma installer for gapps, been using it for months with no issues.
-Boots to OS, home button now works, and the status bar is there. Immediately get a FC on Gmail, without opening any apps.
-Still no Google account, and no option within "Accounts" to add one. <----main problem at this point.
Click to expand...
Click to collapse
Nothing in the menu button to add accounts?
And with that aroma installer, are you adding the thing for the account setup, that prompts you for the gmail account etc? I don't use the aroma installer, but I know it lets you select which packages to install, and you may not be installing it.
teh roxxorz said:
Nothing in the menu button to add accounts?
And with that aroma installer, are you adding the thing for the account setup, that prompts you for the gmail account etc? I don't use the aroma installer, but I know it lets you select which packages to install, and you may not be installing it.
Click to expand...
Click to collapse
Nothing at all in the menu for it :/
The gapps installer menu is Aroma-driven, but it has its own menu. It's designed to let you choose which gapps you want installed "inverted", and what, if any, additional features you'd like added. I've tried everything from completely foregoing installing them altogether, to installing all of them. There is no menu option for adding account setup.
Since all else had failed just Odin back to stock and reroot. Then you should be good to go. You also might have something on the internal sd card that is not playing nice. So id wipe that too then use odin. Make sure you get any pics etc saved first so you don't lose them.
G-Nexus Sent
disturbd1 said:
Nothing at all in the menu for it :/
The gapps installer menu is Aroma-driven, but it has its own menu. It's designed to let you choose which gapps you want installed "inverted", and what, if any, additional features you'd like added. I've tried everything from completely foregoing installing them altogether, to installing all of them. There is no menu option for adding account setup.
Click to expand...
Click to collapse
That's really weird. Have you tried installing just the gapps zip without the installer?
---------- Post added at 01:10 PM ---------- Previous post was at 01:09 PM ----------
ifly4vamerica said:
Since all else had failed just Odin back to stock and reroot. Then you should be good to go. You also might have something on the internal sd card that is not playing nice. So id wipe that too then use odin. Make sure you get any pics etc saved first so you don't lose them.
G-Nexus Sent
Click to expand...
Click to collapse
That's the last thing I was gona have him do, but avoiding it if possible.
I figured it out. It had nothing to do with remnants of whatever messed it up in the first place. For the first time since I've used that specific gapps installer - it has failed me. You were right when you said it should be creating a google account prompt as a result of installing the gapps (I always thought that was part of the ROM, not the gapps zip).
I loaded the previous version of the gapps zip, it still uses Aroma, and it worked like a charm.
Thanks a TON for the persistence responses, I sincerely appreciate it. Nothing like looking like an ass to your girl when you think you know your Android...heh
Holy hell, I've lost a lot of sleep, Batman.
Cheers :good:
I have a Verizon GNex, Toro. I was running PA 3.60 4.2.2 and all was fine, but I go the bug for 4.3
I flashed FTL 4.3 rom for toro, had it booted up the first time, and was loading apps and setting up my phone, when it froze after about 15 minutes and I had to pull battery.
I tired to reboot but it got stuck on Google logo for 10-15 each time, nothing would happen, so I wiped and tried to restore my old backups, all of them failed, i try to restore everything but data and is it says successful in TWRP (v2.5.0.0) but when I go to reboot system it hangs again on the Google logo for long periods of time, I've waited upwards of 15 minutes.
I still have the PA 3.60 files in my downloads so I tried to wipe and flash it back on my phone, again it hangs at the Goggle logo and wont go past it.
I can get to the bootloader, I can get to TWRP, but nothing else.
Any advice on what I should try next?
Do I need to flash a stock image? I'm at work at the moment so I will have to wait till later to do it, but at home I have a Mac, which makes things that much more confusing for me.
mhport2 said:
I have a Verizon GNex, Toro. I was running PA 3.60 4.2.2 and all was fine, but I go the bug for 4.3
I flashed FTL 4.3 rom for toro, had it booted up the first time, and was loading apps and setting up my phone, when it froze after about 15 minutes and I had to pull battery.
I tired to reboot but it got stuck on Google logo for 10-15 each time, nothing would happen, so I wiped and tried to restore my old backups, all of them failed, i try to restore everything but data and is it says successful in TWRP (v2.5.0.0) but when I go to reboot system it hangs again on the Google logo for long periods of time, I've waited upwards of 15 minutes.
I still have the PA 3.60 files in my downloads so I tried to wipe and flash it back on my phone, again it hangs at the Goggle logo and wont go past it.
I can get to the bootloader, I can get to TWRP, but nothing else.
Any advice on what I should try next?
Do I need to flash a stock image? I'm at work at the moment so I will have to wait till later to do it, but at home I have a Mac, which makes things that much more confusing for me.
Click to expand...
Click to collapse
Did you flash the new bootloader before you tried to flash the 4.3 ROM? I've heard that it is unnecessary but I would highly recommend using the bootloader designed for the current version of Android. What were the exact steps you took to flash the new 4.3 ROM?
I'm beginning to suspect that people are either getting bad downloads or the data cables being used are not working properly which is causing bad flashes. This is just speculation, but I am using the data cable supplied with my phone and have yet to have one single problem flashing the 4.3 ROM.
jaizero said:
Did you flash the new bootloader before you tried to flash the 4.3 ROM? I've heard that it is unnecessary but I would highly recommend using the bootloader designed for the current version of Android. What were the exact steps you took to flash the new 4.3 ROM?
Click to expand...
Click to collapse
No, I did not flash a new bootloader, I followed the FTL steps he posted except for wiping cache and davilk cache.
Instructions:
1) Download ROM:
Dev-Host: http://d-h.st/s7b
2) Download Gapps:
Dev-Host: http://d-h.st/UDe
Source: http://forum.xda-developers.com/show...38&postcount=1
*** Goo.im Gapps for 4.2.2 did not work. Use other Gapps at your own risk! ***
3) Download SuperSU:
Dev-Host: http://d-h.st/h3h
4) Backup Device
5) Flash the zips in order
Click to expand...
Click to collapse
jaizero said:
Did you flash the new bootloader before you tried to flash the 4.3 ROM? I've heard that it is unnecessary but I would highly recommend using the bootloader designed for the current version of Android. What were the exact steps you took to flash the new 4.3 ROM?
I'm beginning to suspect that people are either getting bad downloads or the data cables being used are not working properly which is causing bad flashes. This is just speculation, but I am using the data cable supplied with my phone and have yet to have one single problem flashing the 4.3 ROM.
Click to expand...
Click to collapse
I downloaded the files directly from chrome on the phone. Is that a problem? That is how I have done most of the ROM's I have ever downloaded.
Try this..
Boot into recovery
Factory reset
Wipe dalvik/cache
Install ROM
Install Gapps
Install SU zip
Reboot
The first boot can take a few minutes so be patient. You'll sit at the "Google" screen for a minute or two then the "android" boot animation for 2-5 minutes. I also wouldn't recommend restoring any backups as I ran into some issues doing this. If you can get the ROM to boot do a fresh install of all your apps from the Play Store.
I never flashed the bootloader and I have had zero problems with flashing and booting 4.3. I dont know what people are doing to have issues. One thing I can think of is after flashing everything and you select restart device, it gives you this option that doesnt usually show up. I cant think of the wording. Something about "erasing flash something or other". there is a whole list of "No" and one line of "erase....". Are people clicking the option to erase and get problems from it? I always just select to go back and it restarts.
jsgraphicart said:
I never flashed the bootloader and I have had zero problems with flashing and booting 4.3. I dont know what people are doing to have issues. One thing I can think of is after flashing everything and you select restart device, it gives you this option that doesnt usually show up. I cant think of the wording. Something about "erasing flash something or other". there is a whole list of "No" and one line of "erase....". Are people clicking the option to erase and get problems from it? I always just select to go back and it restarts.
Click to expand...
Click to collapse
The OP is using TWRP which is what I used and I got no such options.
---------- Post added at 11:47 AM ---------- Previous post was at 11:45 AM ----------
mhport2 said:
I downloaded the files directly from chrome on the phone. Is that a problem? That is how I have done most of the ROM's I have ever downloaded.
Click to expand...
Click to collapse
It could be, I can't speculate on that as I have only downloaded the files to my PC.
jaizero said:
The OP is using TWRP which is what I used and I got no such options.
Click to expand...
Click to collapse
Oh. I never use TWRP. I have never liked it. I dont know how TWRP handles stuff then.
jaizero said:
Try this..
Boot into recovery
Factory reset
Wipe dalvik/cache
Install ROM
Install Gapps
Install SU zip
Reboot
The first boot can take a few minutes so be patient. You'll sit at the "Google" screen for a minute or two then the "android" boot animation for 2-5 minutes. I also wouldn't recommend restoring any backups as I ran into some issues doing this. If you can get the ROM to boot do a fresh install of all your apps from the Play Store.
Click to expand...
Click to collapse
I have tried this a few times now, it just hang at the Google Logo, I have waited 15 minutes now, that shouldn't be right.
mhport2 said:
I have tried this a few times now, it just hang at the Google Logo, I have waited 15 minutes now, that shouldn't be right.
Click to expand...
Click to collapse
My next suggestion is going to be a /system wipe. Not sure If you want to go this route but if you choose to (at your own risk)..
Boot into recovery
Factory reset
wipe dalvik/cache
wipe /system
install ROM
install Gapps
install SU zip
reboot
As a warning if this doesn't work you will not have a booting system. You will be forced to reinstall an older factory image via fastboot.
Do you have a 4.2.2. ROM saved on your SD card that you can install? It might be a good idea to get a booting system first before trying anything else from this point on.
Still nothing works, I formatted all data and do not have an OS at this point.
When I get home I will adb sideload a 4.2.2 rom and gapps (Most likely Mmuzzy for the time being) from my mac and install it in TWRP. I've done this before and it should work and get me out of this mess.
Thanks for your help.
mhport2 said:
Still nothing works, I formatted all data and do not have an OS at this point.
When I get home I will adb sideload a 4.2.2 rom and gapps (Most likely Mmuzzy for the time being) from my mac and install it in TWRP. I've done this before and it should work and get me out of this mess.
Thanks for your help.
Click to expand...
Click to collapse
did it work? i am also having this problem but when i go into my bootloader it tells me my device is tuna even though its a toro if that matters. and to make things wierder when i try to adb it says i dont have fastboot even though i had it less than 3 hrs ago when i was flashing the rom.(supernova) it worked then i shut off and rebooted the next morning and i just get stuck at the google logo. if anyone can help me i would appriciate it.
Hey everyone,
the thread (http://forum.xda-developers.com/showthread.php?t=2383146) for the CleanROM doesn't provide any instruction on the installation process.
Does anyone know a guide where this ROM is explained?
Right now I am on stock 4.4.2 unlocked & rooted + SuperSU and BusyBox.
I also fully backuped all my apps with the Helium App to Google Drive, so I hope I'm ready to go for a custom rom.
best regards,
daZza
I was just in the middle of posting almost the exact same thing. I have a nexus 7 2013. when I download the cleanroom to the tablet then try to install it from the recovery screen it just says "install failed"
Is there a way to install this from a PC?
I guess now we wait?
When you install a rom, do a complete wipe first after backing your stuff up then install rom. If it says install failed, unmount system
looney2388 said:
When you install a rom, do a complete wipe first after backing your stuff up then install rom. If it says install failed, unmount system
Click to expand...
Click to collapse
Unmount from what?
I tried "wipe data/factory reset" and "wipe cache partition", is that considered "a complete wipe?
The easiest way I have found to install any custom rom is with a custom recovery, TWRP. You can find your way by using Goo Manager, available from the Play Store for free. Google is your friend and I am sure a search for TWRP and/or Goo Manager will make you happy. I have Clean Rom on my Nexus 7 and it is really nice. If you are unlocked and rooted you should have zero problems..
There is no instructions because it's very standard way to install. Not trying to be mean but the expectation on XDA is that you will do at least some homework before starting to flash ROMS.
You should be on 4.2.2 already for the best install of CR.
Assuming you are rooted and have a custom recovery. (if you are not gets Wugs Tookit which walk you right through the process of unlocking, rooting and installing TWRP)
1 download CleanROM to your device or download it and transfer it to your device using a PC
2 boot into recovery. Get quick boot from the play store to make booting into recovery easy (you might need to be rooted for this, not sure). Other wise power off and then boot up holding the power button and Vol down button until you get the Google logo.
3 In TWRP go into Wipe
You only need to do the Swipe to Factory Reset - which means you lose all your apps and settings. It will fundamentally be like when you bought it. (If you haven't unlocked your device yet, when you unlock you will lose your data).
To Wipe swipe to Factory Reset. No need to do anything else with system, format data, etc. The install of CleanROM format System as part of the install. (I've probably done 25 installs of CR and I've never needed to do anything other than Swipe to Reset.
4 Click on the home Icon in TWRP to go the home page in TWRP
5 Go into Install
6 Navigate to where you downloaded CleanROM
7 Select it by tapping on it
8 Swipe to confirm flash.
When it finishes, you are done. Hit reboot system and you will be in CleanROM. You will need to go through the Google Setup again. Profit
I had a deuce of a time trying to install CleanROM last August after just getting my Nexus 7. My SOP is to erase boot, cache, recovery, system and userdata (what would be considered overkill, but I do it to ensure everything's clean), which I did before flashing the first custom recovery. Under CWM, the installation would leave me in an eternal boot animation. Under TWRP, the Aroma installer would simply freeze. Scott and I e-mailed back and forth a number of times, and he'd never heard of anyone with the same problem. Then I found under CWM, it worked fine if I first formatted /system and then the option to format /cache and /data.
Pandae said:
I had a deuce of a time trying to install CleanROM last August after just getting my Nexus 7. My SOP is to erase boot, cache, recovery, system and userdata (what would be considered overkill, but I do it to ensure everything's clean), which I did before flashing the first custom recovery. Under CWM, the installation would leave me in an eternal boot animation. Under TWRP, the Aroma installer would simply freeze. Scott and I e-mailed back and forth a number of times, and he'd never heard of anyone with the same problem. Then I found under CWM, it worked fine if I first formatted /system and then the option to format /cache and /data.
Click to expand...
Click to collapse
Dude these are people new to flashing. You are misleading people about what they 'should' do. The people looking for 'guides' are going to end up nuking the OS and will be in this forum asking about being bricked.
Your information is outdated. Clean ROM has not been on Aroma since V2 (maybe even before 2.0) and yes you are in the VAST minority of people having problems installing CleanROM coming from stock, or really any ROM if they did a 'clean' install.
I'm no expert, I'm good at following directions, and I have been flashing ROM's/Kernels/Mods/Themes on six devices now over the last 4 years. I'm on XDA just about everyday in the development threads reading the problems that other people are having and getting help with my own problems. AOSP, AOKP, CM, Paranoid, I've run them all.
TWRP is the Recovery recommended by the Dev of CleanROM.
A normal clean install is cache/dalvik/reset data. 99% of the time that is all you need. It's done in one step in TWRP. On the Wipe page in TWRP -Swipe to reset, done. That's why the Devs for TWRP made it one step. It is the recommended way to install a ROM.
Read just about any Dev's ROM thread and this is what they will say to do this as the recommended CLEAN install. The install to do if you are trying to solve a problem, if you only wiped Cache/Dalvik, what is called a Dirty Flash. People do a dirty flash to avoid having to restore their device and if you are only changing version of the same ROM, it's usually OK, But the first advice for any kind of instability will be did you do a "clean install".
Some Devs will add to format system to their instructions for installing their ROM. But just about all ROMs now format system as part of the install. But it hurts nothing to do it, it just typically not needed.
To go a step further you can format data which will wipe all user/app data that hasn't been wiped yet. This is given as advice when more basic trouble shooting steps have failed. Format Data is under under the Wipe Section in TWRP. It will ask you to confirm that is what you want to do because it is not a typical step in doing a 'clean' install.
At this point most people who still are having problems or just want to feel like they are starting with a CLEAN setup will just 'go back' to stock, take the OTA's if they need/want to, and then re-root and flash the ROM they want.
UNLESS you are trying to solve a very specific problem, most likely under the guidance of someone seriously knowledgeable (Dev), you do not need to do more than this.
ezas said:
Dude these are people new to flashing. You are misleading people about what they 'should' do. The people looking for 'guides' are going to end up nuking the OS and will be in this forum asking about being bricked.
Your information is outdated. Clean ROM has not been on Aroma since V2 (maybe even before 2.0) and yes you are in the VAST minority of people having problems installing CleanROM coming from stock, or really any ROM if they did a 'clean' install.
I'm no expert, I'm good at following directions, and I have been flashing ROM's/Kernels/Mods/Themes on six devices now over the last 4 years. I'm on XDA just about everyday in the development threads reading the problems that other people are having and getting help with my own problems. AOSP, AOKP, CM, Paranoid, I've run them all.
TWRP is the Recovery recommended by the Dev of CleanROM.
A normal clean install is cache/dalvik/reset data. 99% of the time that is all you need. It's done in one step in TWRP. On the Wipe page in TWRP -Swipe to reset, done. That's why the Devs for TWRP made it one step. It is the recommended way to install a ROM.
Read just about any Dev's ROM thread and this is what they will say to do this as the recommended CLEAN install. The install to do if you are trying to solve a problem, if you only wiped Cache/Dalvik, what is called a Dirty Flash. People do a dirty flash to avoid having to restore their device and if you are only changing version of the same ROM, it's usually OK, But the first advice for any kind of instability will be did you do a "clean install".
Some Devs will add to format system to their instructions for installing their ROM. But just about all ROMs now format system as part of the install. But it hurts nothing to do it, it just typically not needed.
To go a step further you can format data which will wipe all user/app data that hasn't been wiped yet. This is given as advice when more basic trouble shooting steps have failed. Format Data is under under the Wipe Section in TWRP. It will ask you to confirm that is what you want to do because it is not a typical step in doing a 'clean' install.
At this point most people who still are having problems or just want to feel like they are starting with a CLEAN setup will just 'go back' to stock, take the OTA's if they need/want to, and then re-root and flash the ROM they want.
UNLESS you are trying to solve a very specific problem, most likely under the guidance of someone seriously knowledgeable (Dev), you do not need to do more than this.
Click to expand...
Click to collapse
I'm hardly "new" to flashing, and note what I said: "last August," when CleanROM was still using Aroma. Duh.
Under CWM, trying to format "data" after I've done a full wipe produces an error, which right now escapes me. But formatting /system and then /cache and /data works. Like I said, it's considered overkill by most, but it's how I got CleanROM to install. Why is my 2013 N7 unusually affected, as was the first one I had to exchange for a bad pixel? You tell me. It's probably the same reason a supposed small minority of units have had touchscreen, GPS and reboot problems. But I know what works on mine, and my unusual situation is all I'm relating. I'm not advising the guy to do anything I have, or to pass herbs over his N7 to improve his luck. Duh.
CWM is my preference. TWRP may have certain advantages, but I prefer CWM's interface. And I could never get CleanROM to install under it anyway. You tell me why that happens, "Dude."
Please I think both of you have valid points. I just want mine to work and "whippin it out and slapping it on the table" solves nothing
I am pulling my hair out because NOTHING I am trying is working, it just seems that working on these things goes like this...
1. install cleanroom 2.6, in order to do this you will need TWRP if you don't have TWRP see next step
2. install TWRP in order to do this you will need fastboot if you don't have fastboot see next step
3. install fastboot in order to do this you will need clock work mod if you don't have CWM see next step
4. in order to have clock work mod you either need a cleanroom 2.6 installed (see step 1) or a F%^$^%$G!! PhD in tablet engineering
I have spent 20 hours now trying to get this to come online and work and it seems that every time I get one step forward I need to take 10 steps back and read 20 pages online which ends up being either obsolete or for a different tablet or is not for me at all.
Everyone on these forums speak from a place of complete understanding having already done this a million times. I have wasted so much time on this stupid tablet and I could sure use a hand straightening it out.
right now my tablet will NOT install new programs. so installing goo manager, fastboot on the tablet is not an option. I can get into CWM and monkey around in there. I can download the TWRP.img to the tablet and also to my PC. I also have cleanroom 2.6 on the tablet in .zip form but it will not install.
I am not adverse to reading, but there is 4 years of reading all over the internet and I have no clue where to even start to find something relevant to solve my problem. All the reading I have done so far has brought me to a half bricked tablet, a little life experience would go a lot further for me than trying to figure this out on my own in the abyss that is the internet
---------- Post added at 12:39 PM ---------- Previous post was at 12:24 PM ----------
But formatting /system and then /cache and /data works.
Click to expand...
Click to collapse
No, it doesn't, I do not have TWRP installed on the tablet (cause im too stupid to figure it out). here is what I am doing
1. start in recovery mode
2. Mounts and Storage
3. Format system >>> Yes
4. Format Cache >>>> Yes
5. Format Data >>> yes
I tried changing "unmount data" to mount
still every time I try to install cleanROM2.6 the android man falls over and I get a red ! in his chest, it keeps saying installation aborted.
---------- Post added at 12:45 PM ---------- Previous post was at 12:39 PM ----------
But formatting /system and then /cache and /data works.
Click to expand...
Click to collapse
No, it doesn't, I do not have TWRP installed on the tablet (cause im too stupid to figure it out). here is what I am doing
1. start in recovery mode
2. Mounts and Storage
3. Format system >>> Yes
4. Format Cache >>>> Yes
5. Format Data >>> yes
6. go back
7. wipe Data factory reset
8. wipe cache partition
9. advanced
10 wipe dalvik cache
I even tried changing "unmount system" to "mount system"
still every time I try to install cleanROM2.6 the android man falls over and I get a red ! in his chest, it keeps saying installation aborted.
I am at the end of my rope, now it is bricked, it just sits on a black screen with "google" in the middle. I can still get into clockwork recovery mode.
If I try and use wugfresh thing it will not recognize the device connected.
Aside from getting into a geek fight, is there anyone on these forums I can go to with this problem?
Did you get my PM? To avoid wasting time troubleshooting, I'd use fastboot to wipe, then use CWM to format /system, /cache and /data+/data/media.
I just got it and I responded
Now we're set on the right road, finally! Bonne chance, mon ami.
looney2388 said:
When you install a rom, do a complete wipe first after backing your stuff up then install rom. If it says install failed, unmount system
Click to expand...
Click to collapse
Thanks, that's all I needed to know. Worked like a charm and was done after a few minutes. I just wasn't sure what kind of wipe I need to do in TWRP and if I need to re-unlock or re-root the device after installing the custom rom. Sorry for the late response
Thought I'd try out the encryption in AOKP on my Nexus 7 (2013) and decided I didn't like it. I read that a "factory reset" in TWRP was supposed to remove it, although it would nuke all my files, sdcard, apps, etc. No problem, the thing is brand new so nothing really on it. After wiping however, when I boot into recovery now, TWRP is still asking for the encryption PIN. I thought I would just get into the shell over ADB and see what's going on but not able to do that either. I just get "?????????" when trying to view the device with "adb devices". I read something about erasing userdata, system and cache from fastboot and also another piece of info about flashing the stock recovery back to it, but not sure that's the best route. Any thoughts? Thanks.
eris170 said:
Thought I'd try out the encryption in AOKP on my Nexus 7 (2013) and decided I didn't like it. I read that a "factory reset" in TWRP was supposed to remove it, although it would nuke all my files, sdcard, apps, etc. No problem, the thing is brand new so nothing really on it. After wiping however, when I boot into recovery now, TWRP is still asking for the encryption PIN. I thought I would just get into the shell over ADB and see what's going on but not able to do that either. I just get "?????????" when trying to view the device with "adb devices". I read something about erasing userdata, system and cache from fastboot and also another piece of info about flashing the stock recovery back to it, but not sure that's the best route. Any thoughts? Thanks.
Click to expand...
Click to collapse
A factory reset from inside TWRP does NOT wipe internal storage/sdcard. If you want to wipe everything you can either do it from inside TWRP with "advanced wipe" or just do a normal factory reset from Settings/Backup and reset. If you fastboot flash the userdata and cache images that would also be like a factory reset. If you wipe/erase the system you will need to fastboot flash the system image or flash a rom BEFORE you try and reboot.
wantabe said:
A factory reset from inside TWRP does NOT wipe internal storage/sdcard.
Click to expand...
Click to collapse
Sorry, I meant to say I did the advanced wipe and smoked the data partition. I was going to go back and edit my post but it wouldn't let me do it for another five minutes and I went off and did something else. When you say "fastboot flash" the system image, do you mean re-install TWRP with "fastboot flash recovery twrp.img" ?
I tried a different comp and was able to get to the device over ADB so I pushed aokp_flo_jb-mr2_milestone-1.zip over ADB to /sdcard and did the same with gapps-jb-20130813-signed.zip. TWRP installed them OK, but after reboot, the zygote process now keeps trying to restart com.google.android.setupwizard which errors out with a dialog box which says "Unfortunately, Setup Wizard has stopped". I touch "Ok" but the dialog just comes back. Looks like I've made a real mess of things.
Should I just go find the stock OS image and recovery image and flash them over?
eris170 said:
Sorry, I meant to say I did the advanced wipe and smoked the data partition. I was going to go back and edit my post but it wouldn't let me do it for another five minutes and I went off and did something else.
Click to expand...
Click to collapse
I'm pretty sure that wiping data from inside advanced wipe will have wiped everything, that should have been enough to get rid of your encryption.
eris170 said:
When you say "fastboot flash" the system image, do you mean re-install TWRP with "fastboot flash recovery twrp.img" ?
Click to expand...
Click to collapse
No. The system image I was talking about is from the factory image. You have to extract/unzip the factory image a couple times before you can see the zip folder with all the images ( boot (kernel), cache, recovery, system and userdata). You had mentioned in your first post "erasing userdata, system and cache." If you erase system you will need to replace it otherwise your device does not have an os (operating system) anymore. One of many ways to replace it would be to fastboot flash the system image (fastboot flash system system.img) that is extracted from the factory image.
eris170 said:
I tried a different comp and was able to get to the device over ADB so I pushed aokp_flo_jb-mr2_milestone-1.zip over ADB to /sdcard and did the same with gapps-jb-20130813-signed.zip. TWRP installed them OK, but after reboot, the zygote process now keeps trying to restart com.google.android.setupwizard which errors out with a dialog box which says "Unfortunately, Setup Wizard has stopped". I touch "Ok" but the dialog just comes back. Looks like I've made a real mess of things
Click to expand...
Click to collapse
. I've always used the stock rom on my Nexus devices so I'm not much help with anything else. But... just from looking at the names on the zips you installed I'm guessing the "jb" means Jelly Bean and the gapps you installed are almost a year old. So... WTH? ; )
eris170 said:
Should I just go find the stock OS image and recovery image and flash them over?
Click to expand...
Click to collapse
I think in your case the easiest thing to do would be to flash the factory image and start over. You will then need to reinstall TWRP and then use TWRP to install/flash the supersu zip. My advice would be to do lots of research before flashing custom roms and custom kernels. After you get back to the factory rom you really need to use TWRP to do a backup (nandroid) BEFORE you flash any custom roms and kernels, with that done it will be easy as hell to get back to stock after experimenting with whatever! Don't rely on toolkits, install the android sdk and learn adb fastboot commands, it's not hard, hell even I can do it!
[TUTORIAL]Download Factory Images Nexus 7 FLO - Restore back STOCK - With latest version KitKat 4.4.4
I've never used this but looks interesting. [TOOL] 06/22/14 One Click Factory Restore 4.4.4 KTU84P (dead or alive)
wantabe said:
. I've always used the stock rom on my Nexus devices so I'm not much help with anything else. But... just from looking at the names on the zips you installed I'm guessing the "jb" means Jelly Bean and the gapps you installed are almost a year old. So... WTH? ; )
Click to expand...
Click to collapse
Meh.. I like running the older stuff because it's usually faster... I mean as long as there isn't some gaping vulnerability in it.
wantabe said:
I think in your case the easiest thing to do would be to flash the factory image and start over.
Click to expand...
Click to collapse
Thanks for the link that saved me some time! Downloaded an flashed and encryption is finally gone. \o/ . Should be all good now.
eris170 said:
Meh.. I like running the older stuff because it's usually faster... I mean as long as there isn't some gaping vulnerability in it.
Thanks for the link that saved me some time! Downloaded an flashed and encryption is finally gone. \o/ . Should be all good now.
Click to expand...
Click to collapse
One of the great things about android is having the ability to change what you don't like and for the most part it isn't hard to do. I did notice with the update to 4.4 better performance and fluidity on both my N5 and N7 so it might be worth checking out at some point. I didn't care for some of the changes like the ui sounds with the 4.4.1 update but it's all easy to modify. Anyway.. glad you got it sorted out.
Hi! I was playing around with my phone and I might have wrecked it somehow. My twrp is password protected, which I have no clue what it is, and therefore can't install roms or restore backups. The phone is not booting into the rom no matter what I do either. Twrp boots everytime I power on my device.
Please help!
Flash stock image and stock recovery (and wipe cache). Then after if it will boot into OOS recovery just click "reboot now".
Were you able to get into twrp? The password is usually the one you set up for your login to andriod system.
If you can get in, then no need worry. i had exact experience last week. Just remember to clear both cache, system, and data. Just keep internal storage intact. Then try to flash stock rom without rooting.
See if you can get it.
The cause of having this issue may due to flashing rom without uninstallng magisk first.
Good luck.
stellarroar said:
Hi! I was playing around with my phone and I might have wrecked it somehow. My twrp is password protected, which I have no clue what it is, and therefore can't install roms or restore backups. The phone is not booting into the rom no matter what I do either. Twrp boots everytime I power on my device.
Please help!
Click to expand...
Click to collapse
Siljorfag said:
Flash stock image and stock recovery (and wipe cache). Then after if it will boot into OOS recovery just click "reboot now".
Click to expand...
Click to collapse
Stock image is the stock OOS rom right?
lyrebird said:
Were you able to get into twrp? The password is usually the one you set up for your login to andriod system.
If you can get in, then no need worry. i had exact experience last week. Just remember to clear both cache, system, and data. Just keep internal storage intact. Then try to flash stock rom without rooting.
See if you can get it.
The cause of having this issue may due to flashing rom without uninstallng magisk first.
Good luck.
Click to expand...
Click to collapse
The twrp password is known only to god because I've tried every pin/password I have ever used on all roms I've tried so far but none of them work. Which is why I can't flash any rom as my storage is encrypted. Most of the times I have a pattern lock set but that can't be mapped to a password can it?
I decided to start from scratch and installed stock recovery and then adb sideloaded first the stock Nougat OOS and then later 5.1.1 stock OOS, but both times in vain. Both times the phone gets stuck on the startup setup saying "just a sec", endlessly. On the very first activity it shows a message, that disappears in a few seconds, saying "Disabled or missing download manager. Can't download voice pack". How can I fix this? Help please.
stellarroar said:
I decided to start from scratch and installed stock recovery and then adb sideloaded first the stock Nougat OOS and then later 5.1.1 stock OOS, but both times in vain. Both times the phone gets stuck on the startup setup saying "just a sec", endlessly. On the very first activity it shows a message, that disappears in a few seconds, saying "Disabled or missing download manager. Can't download voice pack". How can I fix this? Help please.
Click to expand...
Click to collapse
I would fully wipe, then format, but make sure you have the contents from your storage backed up externally. This is the only way to insure there's nothing left over from previous flashes. And then sideload 5.1.1-full update, you should be good from there. I had the same issue after flashing a OOS custom build.
Sent from my ONEPLUS A5010 using XDA Labs
blas4me said:
I would fully wipe, then format, but make sure you have the contents from your storage backed up externally. This is the only way to insure there's nothing left over from previous flashes. And then sideload 5.1.1-full update, you should be good from there. I had the same issue after flashing a OOS custom build.
Sent from my ONEPLUS A5010 using XDA Labs
Click to expand...
Click to collapse
Formatting everything did the trick. I thought sideloading OOS would implicitly do that but I was wrong. Thanks a lot man! Now is there any way I can keep my device unencrypted going ahead? I don't want Twrp to ask me for a password when I'm booting it.