Develop Bugs

[Q] Need Help, Phone stuck on boot up

I have had Cyanogenmod 7 for some time now, but ever since yesterday it is stuck on the Cyanogenmod boot screen and does nothing. I can get into Clockworkmod Recovery, but I am scared to do anything past that for fear of messing something up. Do you all know something I could try to get my phone back working (It is an HTC Inspire on AT&T)
Thanks

Ellimistopher said:
I have had Cyanogenmod 7 for some time now, but ever since yesterday it is stuck on the Cyanogenmod boot screen and does nothing. I can get into Clockworkmod Recovery, but I am scared to do anything past that for fear of messing something up. Do you all know something I could try to get my phone back working (It is an HTC Inspire on AT&T)
Thanks
Click to expand...
Click to collapse
Do you remember anything that happened/changed between when it was working and when it wasn't? S-ON or S-OFF?
Since you can get into CWM, I would just flash a new ROM. In fact, I would first dirty flash the same ROM over the one you've got first to see if that fixes it. If that doesn't work, clean flash a different ROM.

bananagranola said:
Do you remember anything that happened/changed between when it was working and when it wasn't? S-ON or S-OFF?
Since you can get into CWM, I would just flash a new ROM. In fact, I would first dirty flash the same ROM over the one you've got first to see if that fixes it. If that doesn't work, clean flash a different ROM.
Click to expand...
Click to collapse
What's the easiest way of going about this, I haven't ever done anything past the initial root and flash

Just put the ROM to be flashed on the SD card, it's a zip - and then choose to "install from zip" and navigate to it in Recovery. You could find a superwipe .zip file - which cleans all caches etc - on this forum, and that will give you the assurance that your phone is squeaky clean for when you flash the ROM zip file.
Just make sure your phone is - preferably - fully charged. The only thing that can go wrong is the battery running out while flashing .
If for whatever reason it still doesn't get past the bootloop, re-flash or try flashing a different ROM.
There are plenty of really good ROMs for the HD in the ROM sub-forum, for a rock-solid alternative, look at the Android Revolution ROMs.

Ellimistopher said:
What's the easiest way of going about this, I haven't ever done anything past the initial root and flash
Click to expand...
Click to collapse
Download the ROM (make sure it's the exact same version as the one you first flashed) onto your computer. Get the ROM onto your phone, either by using an sdcard adapter or by booting into CWM and mounting the sdcard on the computer. In CWM, wipe cache and dalvik, then install the ROM zip. Reboot. (If you're S-ON, say so; there are a couple extra steps.)
If that doesn't work, do it again with a different ROM. Also, instead of wiping only cache and dalvik, also wipe system and data. You will lose all your installed apps and saved data.
Sorry, but I can't give exact step-by-step CWM instructions because I don't use CWM.

So all I did was reflash the exact same file that I already had on my SD card, and that worked. Cleared the data/caches and I'm back online. Thanks for the help.

Weird Problem flashing Roms

Ok, so I've been flashing Roms since I first had the G1 but my step sons Galaxy S II is giving me fits as of late.
I've been working on it for over 2 days now and can not figure the problem even after reading through all the how to's and individual rom threads. I initialy rooted his phone back in April/May and had a early ICS phandroid rom on it. However I wanted to move him to JB. I've done the customary wipe data/cache but no matter what JB rom I flash it goes into what I believe is a bootloop. I've read several places it been said to let sit after flashing for 10 minutes so I let sit for 20 and it was still on boot (but no obvious point where you can tell it's looping).
When I went to restore his backup that would no longer boot at all, just a blank screen. So long story short I restored everything to stock then updated to ICS through keis. and tried the process again thinking it might need updated firmware/radio. Same thing happened and I had to restore stock and update through keis again. I am now at a complete loss as I update my phone (One S) and wifes (GSIII) atleast once a week on nightlies.
The one thing that I thought was odd is both on the original 2.3.6 and now 4.0.4 when I go into settings at search for update i get a message saying "no firmware". Not sure if that means anything but it didn't sound right to me.
Any help or suggestions would be overwhelmingly appreciated.

You will get different methods on here but for starters what recovery are you running. Thats problem 1 I guarantee for your bootloop. I use TWRP 2.3 which can be found by downloading goo.im and flashing it from the menu screen. You can also go to the forum here in development for the zip file.
When using TWRP or any touch recovery do not use the wipe scripts. Lets start there.... Since the method to flashing is basically the same all over its just the wiping procedure with the wrong recovery can be tricky

I'm using CWM 6.0.3 I believe he's at school so I don't have the phone to know the exact CWM version. It's also not the touch version. How should I go about wiping data/cache for his phone then? I've never used TWRP but going to assume if you've used one recovery it's pretty similar or self explanatory.

jhenson496 said:
I'm using CWM 6.0.3 I believe he's at school so I don't have the phone to know the exact CWM version. It's also not the touch version. How should I go about wiping data/cache for his phone then? I've never used TWRP but going to assume if you've used one recovery it's pretty similar or self explanatory.
Click to expand...
Click to collapse
I personally prefer that recovery and I'm running a cm 10 on my phone with no issues at never had anything. Yes it's rather simple to put on an even if you want to try the CWM touch recovery by all means go ahead
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2

Ok, I'll give TWRP a try when he gets home. I guess my next question would be is there a different way of wiping then with other phones?
Do I need the recovery to be touch (never heard of a recovery needing touch version)
Anything different then wiping dalvik, cashe and data? Also I've look around and do not see an actual JB radio. So I'm assuming the ULVH1 radio would work for ICS & JB.
I appreciate your help with this btw.

jhenson496 said:
Ok, I'll give TWRP a try when he gets home. I guess my next question would be is there a different way of wiping then with other phones?
Do I need the recovery to be touch (never heard of a recovery needing touch version)
Anything different then wiping dalvik, cashe and data? Also I've look around and do not see an actual JB radio. So I'm assuming the ULVH1 radio would work for ICS & JB.
I appreciate your help with this btw.
Click to expand...
Click to collapse
CHANGELOG for 2.3.0.0:
-Rebased onto AOSP Jelly Bean source code
-Rewrote backup, restore, wipe, and mount code in C++ classes for easier maintenance going forward
NOTE: backups from prior versions of TWRP are still compatible with 2.3
-ADB sideload functionality from AOSP is included in 2.3, see this link for more info
-Re-wrote fix permissions entirely in C++ and runs in a few seconds instead of a few minutes (thanks to bigbiff)
-Improvements to zip finding in OpenRecoveryScript (should be a lot fewer GooManager automation issues)
-Faster boot times
-Added charging indicator while in recovery (only updates once every 60 seconds)
While this update may not bring a host of new must-have features, this update is a significant re-write of much of the core TWRP code. AOSP Jelly Bean recovery source moved to mostly C++ code and now all of the "TWRP" code is fully rewritten into C++ as well. Now that we've laid this groundwork, we're in a much better position to pull in future AOSP recovery updates as well as implementing more great new features.
Since TWRP 2.3 is based on AOSP jelly bean sources, TWRP now uses recovery API 3 instead of 2. Some zips may no longer work if the developer is using an out-of-date update-binary. This API change should not be a problem on newer devices, but older devices will probably encounter several zips that need to be updated. If needed, you can try using this update-binary that was compiled with current sources. It goes in your zip file in the META-INF/com/google/android folder.
Click to expand...
Click to collapse
There is a lil something from the TWRP thread about the new recovery... basically its built off a JB which improves the features being used like wipes, fix permissions, backups etc. Its not that its solely touch but it was the direction most if not all recoveries have gone to basically preserve that power button and vol keys of our phones. It kinda makes sense...
So with updated technology just came a better way to use a recovery and since the SGII originally had wiping issues TWRP on this phone is made solely for this phone which cut out alot of issues. Now if you prefer a non touch may I suggest 5.0.2.7 w/darkside cache wipes and you would be ok as well. Honestly though I dont think anyone would be upset with TWRP its quite nice
TWRP Link - http://forum.xda-developers.com/showthread.php?t=1768742
Darkside Wipes - http://forum.xda-developers.com/showthread.php?t=1477955 (Only use with CWM 5.0.2.7)
CWM Touch(Latest) - http://forum.xda-developers.com/showthread.php?t=1844637

I would switch to Clockwork Recovery 5.0.2.7 which you can find in ROMmanager app. Thus, you can use TDJ's Darkside super wipe and cache wipe scripts which install very clean.
Finding his scripts might be a bit of a challenge but they are out there. I have them but not sure how i can get them to you... my dropbox isnt working.
if you do find those scripts, then the flash is simple...
reboot into recovery
Flash TDJ's Darkside SUPERWIPE
Flash your ROM or Gapps depending on what that OP says goes first
Flash Darkside CACHE wipe
Reboot, let is settle 10 mins reboot
That works with 5.0.2.7 where you have to mash the side buttons.. Ive installed a few JB and ICS roms this way, worked well for me.
Hit thanks if i helped

abesgs2 said:
I would switch to Clockwork Recovery 5.0.2.7 which you can find in ROMmanager app. Thus, you can use TDJ's Darkside super wipe and cache wipe scripts which install very clean.
Finding his scripts might be a bit of a challenge but they are out there. I have them but not sure how i can get them to you... my dropbox isnt working.
if you do find those scripts, then the flash is simple...
reboot into recovery
Flash TDJ's Darkside SUPERWIPE
Flash your ROM or Gapps depending on what that OP says goes first
Flash Darkside CACHE wipe
Reboot, let is settle 10 mins reboot
That works with 5.0.2.7 where you have to mash the side buttons.. Ive installed a few JB and ICS roms this way, worked well for me.
Hit thanks if i helped
Click to expand...
Click to collapse
My friend I linked the zips in the post right above yours

playya said:
CHANGELOG for 2.3.0.0:
There is a lil something from the TWRP thread about the new recovery... basically its built off a JB which improves the features being used like wipes, fix permissions, backups etc. Its not that its solely touch but it was the direction most if not all recoveries have gone to basically preserve that power button and vol keys of our phones. It kinda makes sense...
So with updated technology just came a better way to use a recovery and since the SGII originally had wiping issues TWRP on this phone is made solely for this phone which cut out alot of issues. Now if you prefer a non touch may I suggest 5.0.2.7 w/darkside cache wipes and you would be ok as well. Honestly though I dont think anyone would be upset with TWRP its quite nice
TWRP Link - http://forum.xda-developers.com/showthread.php?t=1768742
Darkside Wipes - http://forum.xda-developers.com/showthread.php?t=1477955 (Only use with CWM 5.0.2.7)
CWM Touch(Latest) - http://forum.xda-developers.com/showthread.php?t=1844637
Click to expand...
Click to collapse
Just saw that last part by Playa, sorry didnt mean to kang you haha... but hes got it down ^^^

Stuck on "starting apps" after OTA. I was on a rooted stock rom.

Hey guys I need help. Anyone have a link to the latest rooted stock rom? How is cynogenmod these days? Is it worth making the switch? Whats the most popular rom these days?

jkj said:
Hey guys I need help. Anyone have a link to the latest rooted stock rom? How is cynogenmod these days? Is it worth making the switch? Whats the most popular rom these days?
Click to expand...
Click to collapse
Freeza always has the latest stock rooted ROM over in this thread. It's always updated shortly after each OTA is dropped (currently at MB1).
You can see my setup in my sig. I like it a lot!
CM10.1 nightlies are good, and a lot of the AOSP (4.2.2) ROMs are really stable. There are a lot of reasons to stay with TW ROMs and a lot of reasons to move over to AOSP, AOKP, and other ROMs (MIUI, etc). My recommendation would be to update your recovery to the latest (see my sig for the link to the latest TWRP, search for the latest CWM) and just flash away. As long as you stick to Sprint ROMs and nandroid up whenever you can, it's getting difficult to brick your phone.

jkj said:
I downloaded the stock odexed zip and odin but it doesnt seem like the right file type for odin to flash?
Click to expand...
Click to collapse
First off, you're going to need to have a custom recovery, if you don't already have one (most people do after they originally flash their phone). There are many guides to do this, just follow one of qbking77's great tutorials. I'd recommend using TWRP, but the latest CWM works well also.
Now that you have a custom recovery, you can try the following and it might get you out of the bootloop:
In the custom recovery, clear (wipe) both cache and dalvik cache. Then reboot the phone (reboot menu -> system).
If the above doesn't work to get you through the bootloop, try the instructions below:
Now that you have a custom recovery, you need to get the files onto your phone. Since you cannot turn your phone on to download it or connect through USB, you'll have to do it through recovery. Since I use TWRP, I'll walk you through the menu's for that (CWM should be similar).
Connect USB cable to computer -> Mount Menu -> Mount USB Storage.
Now your computer should see a "removable disk" with the contents of your SD Card on it. Now you can copy the ROM you downloaded over to the SD Card.
Now that the file is actually on the phone, you can flash the ROM zip in recovery. Whenever you do this, it's best to do what is called a "full wipe" in the recovery. You'll lose all your apps, settings, etc but it's much better than having a paperweight. In TWRP, what I always do is the following:
1) Nandroid backup: I normally name it something along the lines of "2013-03-14 - ROM NAME - ROM VERSION." This way, when I look through my backups, I can easily see what I was running (what I'm restoring when I want to restore).
2) Wipe Menu - Factory Reset. This will wipe all custom data off of the phone. For me, this is a must before flashing any new ROM. Other people will "dirty flash" Roms on top of each other. For me, that's a recipe for disaster, as any leftover settings/code will inevitably interfere with the new ROM and will mess things up.
3) Wipe Menu - Dalvik Cache and Cache: If I recall correctly, the Factory Reset does both of these, but it doesn't hurt to do it again.
4) Install: This is where you find the ROM zip file you downloaded and install it. Should take less than a minute, but some larger ROMs could take a little longer (not 10 minutes, though).
3) Wipe Menu - Dalvik Cache and Cache: Again, not technically required, but I tend to wipe the cache and dalvik cache very often.
3) Reboot Menu - System: Pretty self-explanatory, but it'll reboot your phone and you can set it up all over again.
In the future, it's best to have Titanium Backup to back up apps and data (For me it's worth the cost to upgrade to Pro). I have mine set up to backup all data every night at 3 am, with a maximum of 5 backups per app. This gives me almost a week of backups that I can restore for every app I have installed. The only thing to keep in mind with TiB is that you can backup/restore system apps that won't work with a new ROM. For example, if I backed up the Samsung Connection Optimizer on the stock rooted ROM and tried to restore it to LiquidSmooth (a 4.2.2 AOSP ROM), it wouldn't work. In fact, it could mess things up on my new ROM. So you might want to pick and choose system apps (RED items) carefully when you're restoring. Next time you want to try out a new ROM (or if you need to restore again because of a bootloop), you can just restore your apps/settings through TiB and not go through 2 hours of setting up all your settings again (for me I like that I can restore all the wifi access spots settings... saves me from explaining why I need my friend's WEP key for the fifth time this month).
Anyways, this post has turned into a novel. Please let me know if you have any more questions (and CNexus or anyone else can correct anything that's wrong)

I got it going by wiping cache and data. I should've tried with just cache wiped. Its annoying to have to redo everything but better than a brick.

Now for some reason my wifi wont turn on. Reflashed again now I'm good to go.

[Q] Installing a rom

Ok, completely new with this. I did a basic root, got superuser cwm and busybox from my understanding. I used Samsung Galaxy Toolkit v7.0.0
I would like to install the MoAR onto my phone. But I'm not 100% sure how to do so. I have Odin v3.4, I was going to do it as a PDA file. But I don't see anything that says it's a .tar file.
If someone could point me in the right direction, or a video would be great.

jrodcamaro said:
Ok, completely new with this. I did a basic root, got superuser cwm and busybox from my understanding. I used Samsung Galaxy Toolkit v7.0.0
I would like to install the MoAR onto my phone. But I'm not 100% sure how to do so. I have Odin v3.4, I was going to do it as a PDA file. But I don't see anything that says it's a .tar file.
If someone could point me in the right direction, or a video would be great.
Click to expand...
Click to collapse
I'm going to assume you're able to boot into a custom recovery (CWM). I persoanlly use TWRP, but either will work well for this. If you can't go through the root process again, based on qbking77's thread. Check out the videos and learn how to use Odin to gain root and a custom recovery. (always good to take a refresher course).
Here are directions on how to flash a Rom below. The instructions will be for TWRP, but CWM has similar options/settings
Make sure the zip of the Rom you downloaded is on your externalSD Card or the root directory of your internal memory.
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 a certainty that at least 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, as you never know exactly what might be left over from your old Rom (especially when going from 4.1.X to 4.2.X or vice-versa).
Also while in the Wipe menu, wipe Cache and Dalvik Cache (can't hurt).
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.
MOAR rom already installed. If, in the future, you flash an AOSP Rom, 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 (such as the MOAR Rom) 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!

I could tell you but from what you're asking, honestly I think it's better not to and to force you to read a lot more. I am pretty new to this stuff too, joined this site in like march but I did about 3 weeks worth of reading before I rooted and flashed my first ROM. I'm not trying to be mean here but the question you're asking will be the least of your worries once you read a little more. I recommend you read this Q&A thread, it's also at the top of the Q&A forum.
Edit: It seems good guy topherk here gave you the info, I stand by what I said though, from a fellow newbie to another

jrodcamaro said:
Ok, completely new with this. I did a basic root, got superuser cwm and busybox from my understanding. I used Samsung Galaxy Toolkit v7.0.0
I would like to install the MoAR onto my phone. But I'm not 100% sure how to do so. I have Odin v3.4, I was going to do it as a PDA file. But I don't see anything that says it's a .tar file.
If someone could point me in the right direction, or a video would be great.
Click to expand...
Click to collapse
Download the rom on your pc and transfer it to your sd card or internal sd card on your phone. Don't put the rom zip file in any folders as it's easier to find, commonly referred to as the root of your sd card. Power off your phone if your still on stock, after it shuts down hold the volume up button+the home button and then hold power button, this will take you to your custom recovery. First thing to do once in your recovery is make backup of your current rom, make sure you have at least 3GB free space on either your sd or internal sd, some backups can be even bigger, if you don't have space it should tell you. After your backup is done, wipe cache, dalvik cache, factory reset and then flash your rom, after it's done and you see it was successful, fix permissions and reboot...you should be good to go at that point. If all is running well you can boot back into cwm, select restore and only restore /data, to get all your apps and their data back, fix permissions again and reboot. You can use titanium backup or my backup root /pro to restore apps and data but personally I don't prefer those methods. If you have any issues, restore your backup and try again.
I see I was slow again as topherk said everything and then some lol...still posting this just in case it helps at all.
Edit; just to throw it out there I'll tell you how I do things, once your more experienced this could make flashing roms, kernels, tweaks ect, easier. I always make a backup first before I switch roms. Then I simply wipe cache, dalvik cache, flash new rom and fix permissions....reboot and enjoy, this is known as a dirty flash, some roms don't dirty flash well, some work great.
Also I always 100% of the time download roms, kernels ect straight from my phone, never had a bad download that I'm aware of, I don't check md5 sums, I just verify the size of the dl matches what I dl'd. My dl's go to my download folder on my ext sd card so when I go into recovery, I know to look in my download folder on the ext sd card.
Other things to note about dirty flashing if you choose to do it, figure out your rom issues quietly and it can't hurt to try dirty flashing if you always remember rule#1.....make a backup first. If you get stuck in a boot loop, just pull the battery, put it back in and 3 button boot to recovery and restore your backup.

Yeah, the main reason I prefer a clean flash is that when people dirty flash, any and all problems will not be supported by the developer. And since the person is asking how to flash a Rom, I doubt that they'd know what to do with a FC. I'd prefer if they would do a clean flash until they get used to it. I do all my app backups in Titanium Backup, and even then I have to be careful not to restore something that might mess up the new Rom.
Anyways, I really liked your advice with the backups: if you're ever stuck in a bootloop, you can just restore your backup. I recently tried out a new Rom that I wasn't too fond of, and in a few minutes was back to my LiquidSmooth. No sweat.
Sent from my SPH-L710 using xda app-developers app

Install guide CleanROM 2.6?

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