new to the brick club? - Transformer TF300T Android Development

Okay, after years of modding dozens of android devices and even editing a few kernels I find I may have bricked a tf300t doing something stupid . Installed jb cwm, no issues, clockwork mod 10.1, gapps, rebooted, nice CM screen, then 'oh crap, I didn;t unencrypt data' as it asks me for unlock code. No worries, type it in, accepted, and CM goes into endless loop.
Go back to cwm, try to wipe data, can't mount /DATA. Tried an ADB shell format, format isnt in this version. Went to restore backup, crap, whatever I did manage to wipe included backup.
Reflashed CM, reboot, no I don't get past ASUS screen.
Thoughts? Target practice time?
Thibble..

Although the TF300T forums are very, VERY friendly, this is still the Dev section.
You may get an answer quicker through Q&A section
(and sorry, I do not know how to help you out)

(Fastboot Flash) the latest TWRP version, do full wipes (except storage lol) and then try to clean install CM, CWM was the cause of many problems before...
btw contact a Mod to move this to Q&A Section

thibbledorf said:
Okay, after years of modding dozens of android devices and even editing a few kernels I find I may have bricked a tf300t doing something stupid . Installed jb cwm, no issues, clockwork mod 10.1, gapps, rebooted, nice CM screen, then 'oh crap, I didn;t unencrypt data' as it asks me for unlock code. No worries, type it in, accepted, and CM goes into endless loop.
Go back to cwm, try to wipe data, can't mount /DATA. Tried an ADB shell format, format isnt in this version. Went to restore backup, crap, whatever I did manage to wipe included backup.
Reflashed CM, reboot, no I don't get past ASUS screen.
Thoughts? Target practice time?
Thibble..
Click to expand...
Click to collapse
Hi !
Please, can you take a look here ? ...maybe it help you :good:

-angel* said:
(Fastboot Flash) the latest TWRP version, do full wipes (except storage lol) and then try to clean install CM, CWM was the cause of many problems before...
btw contact a Mod to move this to Q&A Section
Click to expand...
Click to collapse
Thank you! Yes after I posted I saw my mistake and then ...what...edit /delete won't let me delete....I went looking for the idiot stamp to hit my forehead with.

I'd probably try fastboot, flash/install official asus firmware

Related

[Q] gapps REMAINS no matter what i do (cyanogen 6)

First of, to not make everyone dismiss this question...
This is NOT another problem involving missing gapps.
The problem is, no matter what i do (factory reset/clear cache/clear dalvik + remove ANY TRACE of the google apps from the sdcard, and then reboots before installing a basic version of cmod6), i still cant get rid of those damn google apps.
Seems right not that they are installing on their own from absolutely nowhere(!)?
Doesn't matter what i do, have tried to look at every possible scenario from where the cmod flash-process finds, installs, and puts a copy in system/apps-folder without any success at all.
Posted this issue a few days ago, got no answer and then i marked it as solved, but it weren't. Just one single time did i manage to get the flashing to leave a clean copy, but haven't been able to reproduce that since then.
It is car home, gmail, latitude, maps, navigation, places and voice that is stuck in there. Does anyone have any idea of what to do?
Have, except the above, tried to clean out the sdcard completely, plus download+md5check the latest rom...didn't work. Also tried with verification and script assets ON when flashing directly from clockwork, and have tried to flash from rommanager aswell. same results.
Gonna buy a new sdcard tomorrow since im using the stock one which isn't that great (so it needs to be changed sometime anyway), because all i can think of now is if the card itself is bad and clockwork cant read from it properly. Longshot, but im just that badly out of ideas.
Sorry about this wall of text, but that pretty much explains every aspect i tried with no success of removing them. Desperately seeking for help about this now.
You might be able to wipe the system partition completely via fastboot although I don't know if this is a smart thing to do. Than you would be able to do a clean install without Gapps.
You can also try to flash a different rom boot up and then flash cyanogen mod again or you can manually delete the apps from the system partition either with root explorer or with adb while in recovery.
And are you absolutely sure that there are no Gapps in the rom file?
The install script of all CyanogenMods have a backup function for the gapps lol
So also if u wipe all and reflash the rom, the installer backup the gapps, then format system, then install rom and restore gapps..
If u want remove all gapps, just format the /system partition from the clockworkmod recovery (the option its under mounts and storage)..After that, install the rom zip
TheGhost1233 said:
You might be able to wipe the system partition completely via fastboot although I don't know if this is a smart thing to do.
Click to expand...
Click to collapse
'fastboot erase system' is completely safe to do, and a very good idea
andQlimax said:
If u want remove all gapps, just format the /system partition from the clockworkmod recovery (the option its under mounts and storage)..After that, install the rom zip
Click to expand...
Click to collapse
If you want to do this from Amon's recovery (no clear system option), flash the attached update (unsigned).
andQlimax said:
If u want remove all gapps, just format the /system partition from the clockworkmod recovery (the option its under mounts and storage)..After that, install the rom zip
Click to expand...
Click to collapse
Sorry for being such a slow replyer lol, have completed the personalized rom-package and are about to flash it right about now (...or when i got an answer).
First of, before doing it...that answer were really awesome, just curious, there is no way that will brick the base filesystem in any way? In other words, formating /system trough cwork is "completely safe"?
I ofc know things always can go wrong, like the phone bursts into fire or my apartment gets blown away by nuclear war...but it wont mess with anything by default making a restoration towards working state a pain in the lower back?
EDIT: Thought this could make me sound like a damn nervous user, which im not...but the hate i would have at not being able to use my phone during workhours exceeds all measurements known to man. it would get really really boring, not kidding.

[Q] Stuck in Bootloop *done all the basics to fix*

First let me say...its been awhile since I have posted here, I love the auto search based on the title of a post lol. That is awesome. Needless to say I didn't find anything related to my issue...
Here we go,
I have had my phone rooted forever and a day. I have only ever used fresh roms since It's been rooted. ( about a week after launch ) The issue popped up about a few months or so ago with one of his updates. No matter how i tried to download or install it would always bootloop. I have done the full data, dalvic, cache wipes and got the same results. I figured *f* it and just went back to my nandroid of the old version and forgot about it.
There have been several releases that I have tried from fresh that did the same thing. I figured tonight I would try the synergy rom for something new and to see if my phone would take it. I was using clockwork mod for my recovery. I did a nandroid of my phone and away I went.
I flashed amon_ra since that is synergy's recovery of choice and went through the whole process.
3 hours later...here I am with a phone still stuck in a bootloop when i try the rom and now I learned for some reason that amon_ra nandroid restore is not compatiable with the ones from clockwork that i have on my phone. *quick edit* I have also tried downloading several other roms, and am having the same issues.....even tried redownloading the same roms several times thinking it was a corrupt download or something.
There was one restore available that took me back to what seems to be an unrooted phone. I still have access to the recovery and am able to flash roms, but all the sprint crap is back and I don;t have superuser on the phone anymore.
So there is my story. I am an old hand at flashing and know how to wipe and all that before installing and i seem stuck to use this OG sprint crap for the rest of my contract, unless one of you wonderful phone guru's can point me in the right direction.
~owl
There's a thread here with the SU 3.0
install that, go to menu in the app, make sure that permission is toggled on
HipKat said:
There's a thread here with the SU 3.0
install that, go to menu in the app, make sure that permission is toggled on
Click to expand...
Click to collapse
Well at least i can get SU back on the device...
any more advice as to why the phone is refusing to flash any rom??
Maybe try a superwipe script or wipe everything like boot and all except SD card
Sent From My Pocket
{ParanoiA} said:
Maybe try a superwipe script or wipe everything like boot and all except SD card
Sent From My Pocket
Click to expand...
Click to collapse
+1
I usually wipe everything 3 times in Amon then a superwipe zip after that.
Gotta be clean
YEah, do a wipe of everything except SDCard: and Battery stats, if you're not fully charged. Wipe Cache and Dalvik-Cache a few times each. I don't use superwipes myself, but anyhow, after that, flash a stock ROM. Make a nandroid of it, if your phone boots up fine.
Then go back, wipe everything again and flash the ROM you want to use.
I really want to thank all of you that have taken the time to post some ideas here for me, but as of right now I have had no love from my phone with any of them.
It will flash a radio just fine, flash wimax fine as well, but no love for the ROMS.
Anymore ideas out there??

Problems with cwm after installing paranoid android rom

Ok so I have kind of a strange problem and i dont think its with cwm. I always make nandroid backups before flashing new roms as a precaution but in this case it did no good I recently installed Paranoid Android on my phone to try out Jelly Bean. It is pretty awesome But it is a little buggy with a few of the apps i like to run (rom toolbox and dropbox being the major ones). After restoring all my apps i decided to restore my messaging data. That caused the rom to not boot past the google screen. So I decided to go back to Black Ice AOKP with my backup. Didnt work, gave me the "error while restoring /data!". I also just recently updated to CWM Touch 6.0.0.5. I also tried an earlier backup with the same problem. I decided to use fastboot to flash a different CWM (5.8.*.* touch and regular) and basically has the same issue just a different response (could not find data.img, cache.img, and boot.img). Because i use Titanium backup anyway i decided to just wipe and flash Black Ice but when i do it boots for about 30 seconds and then the phone restarts. I tried this multiple times doing multiple formats to no avail. Just for sh*ts i decided to try to wipe and reinstall Paranoid Android. IT BOOTED!! But the weird thing is is that all my apps were still there including my messaging data that borked the install to begin with :/ Anyway to make a long story short, my phone is now working but im afraid that i can't restore my backup or even install a new rom without issues. It seems that CWM will not properly wipe my phone anymore. I am wondering what this new rom could have installed that would cause these issues? I didnt flash any new radios or bootloaders so i dont think that is an issue. Please help!! lol I would like to go back until this rom gets further development or AOKP goes to JB. Any help is appreciated. Thank you for your time
-Erik
I really don't think the ROM caused your recovery to not work correctly. Have you tried a different recovery, like TWRP?
Oh, and any problems you're having with apps on Paranoid can be easily fixed by changing what mode they display in via Paranoid Settings.
shode, ndomeopu
Thanks For The Quick Replies! My Swype Has Decided Too Capitalize Every Word And I'm Not Going Too Fix It Lol.. Anyway I've Tried Changing Modes With Rom ToolboxAnd It Made No Difference. i Will Try With Drop Box. It Seems Like Maybe This New Rom Messed With The Permissions And That's Why i Can't Properly Format? The Thing Is Is That CWM Worked Fine Before Booting This Rom. And i definitely Understand That My Conclusions Don't Make Sense But Neither Does The Problem Lol. i Guess What My Question Is Is Why Do The Previous Versions Off cwm That Worked Before Not Work Now? i Will Give The Other Recovery a Shot And Let You Know But i Prefer cwm Just Because It's What i Know And Had Always Worked... Until Now Of Course. Also i Don't Consider Myself anewbie At Thus Stuff But i Am Definitely No dev Lol. Any Suggestion Is Welcome. Thanks!
jesusice said:
Oh, and any problems you're having with apps on Paranoid can be easily fixed by changing what mode they display in via Paranoid Settings.
Click to expand...
Click to collapse
Silly Me For Not Thinking Of Changing The Settings. dropBox Now Works But My Swype Is Still Messed Up
Swype works fine for me at 320 dpi and phone mode. Which is the Gnex's default settings so if an app gives you issues try those settings. I'm not too sure about CWM, it's been a while since I've used it. If you want to try TWRP the easiest way is to just install Goo Manager and go to Flash ROMs and in the additional options select Flash Open Recovery Script.
well swype in general worked.. maybe its just my browser. Anyway I installed TWRP, makes me wonder why I wanted to keep CWM It worked.. im back to the old rom. Quick question.. does it save the backups to /sdcard like CWM? I thought it said it backed up to /data/media which means if i completely wipe /data ill lose my backups. Also does this mean I dont have as much space for backups? Thanks for your help.
Gimmemabrewski said:
well swype in general worked.. maybe its just my browser. Anyway I installed TWRP, makes me wonder why I wanted to keep CWM It worked.. im back to the old rom. Quick question.. does it save the backups to /sdcard like CWM? I thought it said it backed up to /data/media which means if i completely wipe /data ill lose my backups. Also does this mean I dont have as much space for backups? Thanks for your help.
Click to expand...
Click to collapse
/sdcard and /data/media are the same thing. I'm sure there's a better technical explanation but I think it's symlinked or something. So wiping data or factory reset in recovery will not wipe your SD contents. From within the ROM it might.

[Q] Need help with flashing roms Galaxy s3

I tried flashing two different roms (synergy and chemistry) on my sprint galaxy s3. It turns on but then wont go past the "galaxy s III" logo. I just restored my backup and all is well but I really want to get multi window on this thing so I could really use some help as to what is not letting me boot up all the way. The last thing i messed around with rooting was my DroidX and with that it really mattered a lot which version of android you were flashing from. I have 4.1.2 the most recent update. Is that why these roms are not working? Any help would be much appreciated I am very excited to get a killer rom on this bad boy.
Did you clear /data, /system, cache, and dalvik cache before flashing? If not, what is your flashing procedure?
But no, the current version should not make any difference when flashing because you are clearing everything anyway
CNexus said:
Did you clear /data, /system, cache, and dalvik cache before flashing? If not, what is your flashing procedure?
But no, the current version should not make any difference when flashing because you are clearing everything anyway
Click to expand...
Click to collapse
I boot into recovery after i put the rom on to my sd card. Then wipe the factory data, cache partition, and delvik cache. I do those steps twice, then install the rom. The install seems to go fine, it always says successful at the end, it just wont go past that screen. Does it mater which version of clockworkmod I use?
You need to wipe /system too. A factory reset only clears app data, and thats no help if you're not wiping the OS as well because you're installing the new one on top of the old without cleaning up first...and thats why it wont boot because different pieces are getting mixed and not together with the files it should be with
It should say something like "format /system"
CNexus said:
You need to wipe /system too. A factory reset only clears app data, and thats no help if you're not wiping the OS as well because you're installing the new one on top of the old without cleaning up first...and thats why it wont boot because different pieces are getting mixed and not together with the files it should be with
It should say something like "format /system"
Click to expand...
Click to collapse
Thank you so much for your quick response. As far as I can tell, I am wiping everything I should be. I use clockwork recovery mod version: and the choices it gives you are: Wipe data/factory reset, wipe cache partition, and wipe dalvik cache. From all the instructional threads I've read, those are the only things you need to clear out before the install. My clockwork version is v5.5.0.4 which i think might be really old. Could that be my issue? Does it matter how I rooted it? I just tryed to put jellybomb v14 on it and it didn't even give me the galaxy s III logo. Luckily it booted back into recovery though. I really don't want to hard brick this thing.
Which recovery are you using?
For TWRP, I generally recommend formating system too.
Also, make sure to flash the rom zip and THEN the gapps.
A-Shin said:
Which recovery are you using?
For TWRP, I generally recommend formating system too.
Also, make sure to flash the rom zip and THEN the gapps.
Click to expand...
Click to collapse
clockworkmod v5.5.0.4
cchrisrollins said:
clockworkmod v5.5.0.4
Click to expand...
Click to collapse
Make the switch to TWRP v2.3.1.0 (newer ones I've heard have problems) but you will be thanking me later. It's way easier and much better than CWM... just an FYI for ya!
cchrisrollins said:
clockworkmod v5.5.0.4
Click to expand...
Click to collapse
I suggest trying a flash with TWRP. If you are unsure how to install TWRP, just download the Goomanager app, then choose install Open Recovery Script. But, before you install or change anything, look around a bit on how to install it. Make sure you follow directions step by step. After you have installed TWRP, try flashing again. Good luck!
Haha, so it looks like switching to twarp is something that i need to do, I'll start researching how to do that. I don't thing clockwork is causing the issues im having, but I could certainly be wrong. Since my phone is rooted, that also means the bootloader is unlocked rite?
cchrisrollins said:
Haha, so it looks like switching to twarp is something that i need to do, I'll start researching how to do that. I don't thing clockwork is causing the issues im having, but I could certainly be wrong. Since my phone is rooted, that also means the bootloader is unlocked rite?
Click to expand...
Click to collapse
Samsung bootloaders come unlocked by default, so yes
Easiest way to switch is to download Goo manager from the Play Store and have it install TWRP for you
Generally speaking, CWM is great on most devices, but for the S3 it's TWRP that's the best and easiest to use
And when flashing new roms, make sure to always format system, it prevents corrupted files from showing up because you would be installing the new system right on top of the old one if you don't
So I did as you suggested. I installed twrp from the play store. I made a backup on there so I should be ready to tryn flash again. The only thing is I use this phone for work all the time and if mess this thing up I'm gonna be in deep doo doo haha. So with the last several attempts failing, I'm a little apprehensive to try again. I'm going to re-odin and flash a different root just to be safe (I used team epic v5). Can you guys recommend a good root to use for my s3?
Sent from my SPH-L710 using xda app-developers app
cchrisrollins said:
So I did as you suggested. I installed twrp from the play store. I made a backup on there so I should be ready to tryn flash again. The only thing is I use this phone for work all the time and if mess this thing up I'm gonna be in deep doo doo haha. So with the last several attempts failing, I'm a little apprehensive to try again. I'm going to re-odin and flash a different root just to be safe (I used team epic v5). Can you guys recommend a good root to use for my s3?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
If you made a nandroid backup in TWRP (I'd recommend to put it on the external memory, but that's just me), you should be good to try any ROM you want (only Sprint ROMS). Just follow CNexus's post (linked for posterity). Wipe system as well as factory reset, cache, and dalvik, prior to installing the ROM.
cchrisrollins said:
So I did as you suggested. I installed twrp from the play store. I made a backup on there so I should be ready to tryn flash again. The only thing is I use this phone for work all the time and if mess this thing up I'm gonna be in deep doo doo haha. So with the last several attempts failing, I'm a little apprehensive to try again. I'm going to re-odin and flash a different root just to be safe (I used team epic v5). Can you guys recommend a good root to use for my s3?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
If you've already rooted, re-rooting isn't going to fix anything, so no need to go there.
As previously explained and detailed, do a full system wipe, and you'll be good to go.
Thank you guys so much for your very quick responses, thank you for bearing with my noobishness too haha. I am going to tryn reflash jellybomb tonight, I'll post on this thread how it goes (hopefully good).
So unfortunately it was the same result with the TWRP. Tryed doing it with a few different roms. Some roms will boot to the "Galaxy s III" logo and others like jellbomb wont even get that far. It just flashed the Samsung logo and that was it. It's gotta be something simple that im missing here, but I can't figure out what it is. On the jellybomb install afterwards TWRP did come up with a message that said something along the lines of: your phone doesn't appear to be rooted, would like to install bla bla bla. So that doesn't make sense, because I know that I do have root access. Feeling pretty frustrated because I'm doing everything the correct way. HELP!
cchrisrollins said:
So unfortunately it was the same result with the TWRP. Tryed doing it with a few different roms. Some roms will boot to the "Galaxy s III" logo and others like jellbomb wont even get that far. It just flashed the Samsung logo and that was it. It's gotta be something simple that im missing here, but I can't figure out what it is. On the jellybomb install afterwards TWRP did come up with a message that said something along the lines of: your phone doesn't appear to be rooted, would like to install bla bla bla. So that doesn't make sense, because I know that I do have root access. Feeling pretty frustrated because I'm doing everything the correct way. HELP!
Click to expand...
Click to collapse
It took me like 4-5 months to personally figure out that the problem was the kernel. You need to flash a kernel right after you flash the ROM. Either the stock kernels or better kernels like Anthrax will do. I know that for jellybomb, there's a kernel included in the Rom but for some reason,it got stuck on the gs 3 logo if I didn't flash another kernel.
Oh thank goodness there is something else I can try, I was out of ideas. Thank you!
Sent from my SPH-L710 using xda app-developers app
cchrisrollins said:
Oh thank goodness there is something else I can try, I was out of ideas. Thank you!
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
No prob, just hit dat thanks button do you know where to get the kernels?
Zin0 said:
No prob, just hit dat thanks button do you know where to get the kernels?
Click to expand...
Click to collapse
I tryed the KT47 AOSP Jellbean kernel after flashing jelly bomb and it did the same thing it did before, black screen after flashing the samsung logo
Now I did go into fix permissions and it did say failed, is that abnormal?
This is my exact procces:
1. boot into TWRP
2. factory reset
3. system wipe
4. cache wipe
5. Dalvik wipe
6. Install from external SD: jellybomb v14
7. Wipe cache/Dalvik
8. Install Kt47 kernel
9. Wipe cache/Dalvik
Anything wrong there?

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

Categories

Resources