Related
Hi there, I'm new to the forum but have been rooting for about a year. Here is my problem...
I was running stock firmware on my SGS3 and went through the standard cm10 root/rom install process. I flashed CMW with Odin, booted to recovery, installed cm10, jb gapps, cleared cache and delvik cache and rebooted. All the above processes worked fine and once it boots into JB, nothing seems to work. My home button does nothing, the top status bar is blank, no wifi, no keyboard (the process just crashes when I attempt to type).
I know this isn't an issue with CM10 on the SGS3 as this works for most people but does anyone have any ideas on how to remedy this? This may be a unique issue as I can't seem to find anyone else experiencing this.
Also...
I should also mention that I've tried a restore in recovery, reinstalled cm10, blah blah blah, and same results. I've also tried the cm10.m2 roms with the identical results. After reboot I don't even get the welcome wizard. It just boots right into the blank, default JB home screen and starts popping up process failure errors. I can navigate around (though the home button doesn't work) but can't use the keyboard etc.
Am I missing something? Is there a way for me to do a clean restore and try again?
Some technical info:
ClockworkMod Recovery v5.8.4.7
cm-10.0.0-d2att.zip
gapps-JB-20121130-signed.zip
Did you do a complete wipe? Data, cache, Davlik , System and then install cm10.
Coming from stock you need to fully wipe.
Sent from my SAMSUNG-SGH-I747 using xda premium
Machoscrawn said:
I should also mention that I've tried a restore in recovery, reinstalled cm10, blah blah blah, and same results. I've also tried the cm10.m2 roms with the identical results. After reboot I don't even get the welcome wizard. It just boots right into the blank, default JB home screen and starts popping up process failure errors. I can navigate around (though the home button doesn't work) but can't use the keyboard etc.
Am I missing something? Is there a way for me to do a clean restore and try again?
Some technical info:
ClockworkMod Recovery v5.8.4.7
cm-10.0.0-d2att.zip
gapps-JB-20121130-signed.zip
Click to expand...
Click to collapse
Your clockworkMod is out of date to run CM10 & the gapps. Upgrade to the latest clockwork mod, then the latest CM then the latest Gapps and you should be good to go.
dynamiclynk said:
Did you do a complete wipe? Data, cache, Davlik , System and then install cm10.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Thanks for the reply. This is what I did...
(Main cwm menu) -wipe cache partition
(Advanced) -wipe dalvik cache
+++go back+++
-reboot system now
Is there something additional I should clear?
Kweli87 said:
Your clockworkMod is out of date to run CM10 & the gapps. Upgrade to the latest clockwork mod, then the latest CM then the latest Gapps and you should be good to go.
Click to expand...
Click to collapse
Thanks for the reply,
How do i update to the latest clockworkMod? Do you happen to have a URL? I think I found the latest 6.something, but they all seem to be in .iso format.
You can't go from stock rom to CM10 without clearing factory reset thing in CWM.. I don't know the exact text string it uses but it should be right on top of clearing cache.. It looks like you only cleared cache and flashed a new rom.
i386W7 said:
You can't go from stock rom to CM10 without clearing factory reset thing in CWM.. I don't know the exact text string it uses but it should be right on top of clearing cache.. It looks like you only cleared cache and flashed a new rom.
Click to expand...
Click to collapse
Sorry I may have missed mentioning that. The first thing I did was the -factory restore/reset
If updating CWM doesn't help, I'd recommend re-downloading the CM10 zip and verifying the MD5 hash. It could be that the download got corrupted somehow...
goodtimes50 said:
If updating CWM doesn't help, I'd recommend re-downloading the CM10 zip and verifying the MD5 hash. It could be that the download got corrupted somehow...
Click to expand...
Click to collapse
Two questions:
1) What is the best way for me to update cwm?
2) I've seen this MD5 hash recommendation here and there. I have no idea what that means. How would I "verify the MD5 hash".
Machoscrawn said:
Two questions:
1) What is the best way for me to update cwm?
2) I've seen this MD5 hash recommendation here and there. I have no idea what that means. How would I "verify the MD5 hash".
Click to expand...
Click to collapse
Flash one of the rooted stock ROMs. Preferably an ICS one since you are on an older cwm. Wipe data, cache, dalvik. Download ROM manager from the play store. Update your recovery to the latest through that. Than flash back to cm10.
BAM1789 said:
Flash one of the rooted stock ROMs. Preferably an ICS one since you are on an older cwm. Wipe data, cache, dalvik. Download ROM manager from the play store. Update your recovery to the latest through that. Than flash back to cm10.
Click to expand...
Click to collapse
Ok thanks! I'm going to give that a shot and see how it goes.
Machoscrawn said:
Ok thanks! I'm going to give that a shot and see how it goes.
Click to expand...
Click to collapse
Ok so I tried flashing a stock rooted ICS ROM and now I'm stuck on the Samsung logo boot screen. Here is the method I tried, using Odin. http://forum.xda-developers.com/showthread.php?t=1739426
I used the "Bell Image (This works with Canadian Virgin Mobile SGH-I747M) - Old Image I747MVLALH1 (ICS 4.0.4)"
After flashing I booted into the stock recovery and cleared the cache partition then rebooted. Still stuck on the Samsung boot screen.
UPDATE: I just let it sit on the Samsung logo boot screen and it eventually loaded into ICS.
Machoscrawn said:
Two questions:
1) What is the best way for me to update cwm?
2) I've seen this MD5 hash recommendation here and there. I have no idea what that means. How would I "verify the MD5 hash".
Click to expand...
Click to collapse
1) I believe Rom Manager (from the Play Store) can do this.
2) Basically an MD5 value is generated when the file is created and is usually listed on the download page (on get.cm look for "md5sum" right under the download link for each build). There are apps that create an MD5 value from the file that you download and compare against the original to ensure that it's intact. If the values don't match, something's wrong with the file. Check out FastSum (there are lots of others out there too).
goodtimes50 said:
1) I believe Rom Manager (from the Play Store) can do this.
2) Basically an MD5 value is generated when the file is created and is usually listed on the download page (on get.cm look for "md5sum" right under the download link for each build). There are apps that create an MD5 value from the file that you download and compare against the original to ensure that it's intact. If the values don't match, something's wrong with the file. Check out FastSum (there are lots of others out there too).
Click to expand...
Click to collapse
Ok cool. Well i have downloaded ROM Manager but when I try to flash the latest recovery and it gives me a list of devices, mine isn't there. The only S3 listed is "Galaxy S3 (MetroPCS)". The list itself looks incomplete, maybe only 20 devices listed. I've rebooted the phone since installing ROM Manager but the list still only shows the one SGS3.
Machoscrawn said:
Ok cool. Well i have downloaded ROM Manager but when I try to flash the latest recovery and it gives me a list of devices, mine isn't there. The only S3 listed is "Galaxy S3 (MetroPCS)". The list itself looks incomplete, maybe only 20 devices listed. I've rebooted the phone since installing ROM Manager but the list still only shows the one SGS3.
Click to expand...
Click to collapse
Try to download GooManager and select the Flash Roms option, it will prompt you, select *Find one for me* reboot into recovery try to wipe/reset and reinstall the ROM and gapps and see if it works
wally3614 said:
Try to download GooManager and select the Flash Roms option, it will prompt you, select *Find one for me* reboot into recovery try to wipe/reset and reinstall the ROM and gapps and see if it works
Click to expand...
Click to collapse
Ok I tried the Goomanager route. When I'm in recovery doing the install of the rom, I get a FAILED error right after it tries updating partition... I've tried installing from internal and external sd with the same results...
I've attached a screenshot. Well I attempted to with my webcam, hopefully it's semi-readable.
Machoscrawn said:
Ok I tried the Goomanager route. When I'm in recovery doing the install of the rom, I get a FAILED error right after it tries updating partition... I've tried installing from internal and external sd with the same results...
I've attached a screenshot. Well I attempted to with my webcam, hopefully it's semi-readable.
Click to expand...
Click to collapse
Well at least you have the proper twrp definitely try and re download the ROM, carefully make sure it is absolutely the correct ROM(I rushed once, thought I was sure n dl'd the wrong one and bricked my older s3) if u have the slightest break during DL this can happen. I KNOW it is frustrating but worth it in the end
wally3614 said:
Well at least you have the proper twrp definitely try and re download the ROM, carefully make sure it is absolutely the correct ROM(I rushed once, thought I was sure n dl'd the wrong one and bricked my older s3) if u have the slightest break during DL this can happen. I KNOW it is frustrating but worth it in the end
Click to expand...
Click to collapse
Alright, I downloaded the latest stable (the only one) build of CM 10 from get.cm. Removed the current version from my internal sd and tried the process again. Same error...
So again, I'm now using GooManager, TeamWin Rocovery v2.3.1.0, CM10 Stable. Doing a factory reset, then wiping system, then install cm10, this is where it fails.
Any way that I can restore everything on my phone completely to stock and start from scratch? Anything else you/anyone can recommend?
Machoscrawn said:
Alright, I downloaded the latest stable (the only one) build of CM 10 from get.cm. Removed the current version from my internal sd and tried the process again. Same error...
So again, I'm now using GooManager, TeamWin Rocovery v2.3.1.0, CM10 Stable. Doing a factory reset, then wiping system, then install cm10, this is where it fails.
Any way that I can restore everything on my phone completely to stock and start from scratch? Anything else you/anyone can recommend?
Click to expand...
Click to collapse
If youre looking to completely start over. Just grab an unrooted stock .tar from one of the links somewhere around here, put your phone in download mode and let it flash. Clean slate.
DISCLAIMER:::: This Is my second thread.I AM A LOWLY NOOB..PLEASE GREAT ONES HELP::
Rather than bury this question in another long thread I made another if I am wrong in this please delete or move to proper thread(mods).
Anyway.
As stated before my phone keeps having hard resets. I believe its due to improper installation due to recovery. I am currently on CWMR v6.0.1.2
I want to know if there is a way to update this to a more up to date version so that I may install and run the wicked sensations v.4 or any other modern ROM. I was running a older version of PHANTOM Blaze (last years or so model) I really am new to the rooting game and I am trying to understand the lingo as I want to help others unlock the power and potential of their "smartphones".I guess what i need to know is how do I update from the version of CWMR i am running to one with ODIN (a newer model). I think if I do this I can destroy the random hard resets.
Any advice? (thanks will be given.)
I do not believe your resets are caused by the recovery at all. Also CWM has nothing to do with Odin, two separate programs. CWM works with the phone itself. Odin is a program which you run on your computer and connect your phone to the computer and you put the phone in download mode. There is a Mobil Odin also available.
To answer your question the easiest way to update CWM is to download Rom Manager app from Google Play Store. Within that app it gives you the ability to check for updates for CWM and flash it right through the app.
Sent from the future via Tapatalk 4
Notice the very first on top thing once you open Rom Manager.
View attachment 2037396
Sent from the future via Tapatalk 4
edfunkycold said:
I do not believe your resets are caused by the recovery at all. Also CWM has nothing to do with Odin, two separate programs. CWM works with the phone itself. Odin is a program which you run on your computer and connect your phone to the computer and you put the phone in download mode. There is a Mobil Odin also available.
To answer your question the easiest way to update CWM is to download Rom Manager app from Google Play Store. Within that app it gives you the ability to check for updates for CWM and flash it right through the app.
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
so any idea whats causing the hardresets..i updated my cwm like you said now what?
It says i now have Rom Manager premium v5.5.2.8 and teh current recovery is: Team Win Recovery Project. Im not sure what I should do now.
M F Money said:
DISCLAIMER:::: This Is my second thread.I AM A LOWLY NOOB..PLEASE GREAT ONES HELP::
Rather than bury this question in another long thread I made another if I am wrong in this please delete or move to proper thread(mods).
Anyway.
As stated before my phone keeps having hard resets. I believe its due to improper installation due to recovery. I am currently on CWMR v6.0.1.2
I want to know if there is a way to update this to a more up to date version so that I may install and run the wicked sensations v.4 or any other modern ROM. I was running a older version of PHANTOM Blaze (last years or so model) I really am new to the rooting game and I am trying to understand the lingo as I want to help others unlock the power and potential of their "smartphones".I guess what i need to know is how do I update from the version of CWMR i am running to one with ODIN (a newer model). I think if I do this I can destroy the random hard resets.
Any advice? (thanks will be given.)
Click to expand...
Click to collapse
You can use the Rom Manager App to install the latest CWM recovery (see this thread)
Can you boot into recovery mode? If you can, Naddict has created recoveries that are able to be flashed from the recovery itself. That might be one was to upgrade to the latest. Also, CNexus has created an aroma installer that can switch recoveries on the fly. It's a really neat program, but also requires access to recovery mode.
topherk said:
You can use the Rom Manager App to install the latest CWM recovery (see this thread)
Can you boot into recovery mode? If you can, Naddict has created recoveries that are able to be flashed from the recovery itself. That might be one was to upgrade to the latest. Also, CNexus has created an aroma installer that can switch recoveries on the fly. It's a really neat program, but also requires access to recovery mode.
Click to expand...
Click to collapse
i can go to recovery but what is it taht is causing the hard resets?
M F Money said:
i can go to recovery but what is it taht is causing the hard resets?
Click to expand...
Click to collapse
I seriously doubt that Recovery is causing reboots.
Did you restore any data or apps from Titanium Backup?
Any apps you recently installed that might be causing it?
topherk said:
You can use the Rom Manager App to install the latest CWM recovery (see this thread)
Can you boot into recovery mode? If you can, Naddict has created recoveries that are able to be flashed from the recovery itself. That might be one was to upgrade to the latest. Also, CNexus has created an aroma installer that can switch recoveries on the fly. It's a really neat program, but also requires access to recovery mode.
Click to expand...
Click to collapse
i can go to recovery but what is it that is causing the hard resets?
M F Money said:
i can go to recovery but what is it taht is causing the hard resets?
Click to expand...
Click to collapse
Most likely your reboots are caused by rogue app and or bad data. The only way to isolate this is by reflashing the rom on a full clean install. Then loading apps all fresh not from a backup.
Sent from the future via Tapatalk 4
edfunkycold said:
Most likely your reboots are caused by rogue app and or bad data. The only way to isolate this is by reflashing the rom on a full clean install. Then loading apps all fresh not from a backup.
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
What Ed said.
I'm 90% sure you've been restoring data (or not wiping enough when flashing the new ROM).
My standard procedure when flashing a ROM (even when just upgrading my current ROM to a new build) is the following:
Investigate ROM: If a ROM catches my eye, I always read the 1st post in great detail to understand the ROM and it's features. I also look for things like "known bugs" and installation instructions. I then read the last 5-10 pages of the thread to see what the users have to say about the ROM (bugs, issues, fixes, etc). Once I understand the pros and cons of the Rom, I decide if I want to flash it. A lot of "noobs" on here don't read the last 5-10 pages and get into trouble when flashing because of it. I always read at least that much and recommend doing so to others.
Download ROM and check md5sum: I download the ROM to my computer, check the md5sum, and copy it to my phone. Then I check the md5sum again.
Make a backup: Just in case (and it's saved me many a time).
So Fresh and so Clean Clean Wipe: Wipe /data, /system, cache and dalvik cache. This removes all remnants of my previous OS (/system) and any app data that could be left behind (/data). Sometime, if I'm looking for a really fresh start, I'll wipe the internal memory. But that's typically not necessary.
Install Rom: If the ROM has an Aroma installer, I just follow the instructions on it. They're typically straight forward. If there's no Aroma installer, I just flash the ROM and let it do it's thing. If it's an AOSP Rom, I also flash the appropriate gapps, which you don't have to do for TW Roms (gapps are included for them).
Re-download your Apps from Play Store: I know it's quicker to just hit "restore" on TiBu, but since you're having issues with reboots, that's the last thing you should try. The Play Store keeps a record of all of your previously-installed apps, so it's easy to re-install them.
If you follow the above, you shouldn't have any issues with your Rom (that aren't ROM-related).
If you're interested, you can also troubleshoot what was causing the reboots:
Slowly restore data to your apps that need it: Here is where you want to be very careful. In TiBu, if you just go through and restore all data for all apps, you won't know what's causing boot loops. What I'd do is prioritize your data restores. Restore the ones you need most often.
Restore one App's data: If there's an App that must have data restored (game saves), restore only that app's data.
Check to see if the phone has reboot problems: Use the phone normally for a while (a few hours) and see if it reboots. If it doesn't then that app wasn't the cause of the bootloops.
Rinse and Repeat: Repeat steps 2-3 for each app you must have the data restored for. Many apps, like Dropbox, don't need their data restored, you just need to log in again. Again, prioritize which apps you need to restore.
Hope you get your reboots worked out!
Ok I wrote this for the OP of my ROM because the issues some people were PMing me about were just plain out dumb, This phone has been out quite a long time and still almost every thread I goto, you got people flashing in way's I didn't even know were possible and posting weird issues that were not being reproduced by the community. so I'm just gonna post this guide for all the developers sake and in hopes the people that actually need this information, receive it before posting and clogging up development threads
If you're having issues on rom's that no one else is reporting, or the DEV has not reproduced on his phone, read the following.
1) Full wipe
2) Do not restore System data or data from CWM
3) Do not dirty flash from other ROM's
4) When was the last time you did a odin to stock? this is important in my opinion and I'm not saying you need to do one but I just want to explain that custom zip's that I make and other dev's make in the shape of "roms" only affect
a few partitions on your device, other's do not get touched and can get messy/corrupt over the months (This explains why the GPS icon disappears in some peoples cases during rom switch) and this is why I get posts in this thread about people wondering why their baseband hasn't been updated after flashing my rom when my post states "MF1"
With this being said my personal rule of thumb is to odin to stock latest and then boot into stock recovery and factory reset, wipe cache/dalvik (BACKUP YOUR SD CARD TO YOUR COMPUTER), this gives your phone fresh partitions everywhere, a fresh system to root and the latest bootloader (which you need for any AOSP 4.2 rom). This is also a good time to unlock your phone if you have not already, then reroot and install custom recovery, update the recovery if need be and flash again on a brand new system. here are my steps
1) backup all user apps and data with titanium backup, DO NOT BACKUP SYSTEM APP'S
2) backup internal storage onto PC
3) Odin to stock latest
4) wait for phone to boot then reboot into stock recovery and full wipe and clear all cache
5) reboot and root the phone and custom recovery
6) flash away and put what you need on your internal storage back onto your phone via usb, see my 2nd set of instructions below
this fixes more issues then you will realize. some of the way people flash rom's on XDA and complain to me with problems is rather funny considering I have the install instructions in the OP, not to mention many of you rooted your phone when you first got it in the ICS 4.0.4 day's and haven't done an odin to stock jellybean to update all your partitions including your bootloader, now I will go over my every day flashing step's.
1)backup all USER APPS/DATA with titanium backup, DO NOT BACKUP SYSTEM APP'S (skip this if you did a odin flash to stock)
2)reboot recovery
3)nandroid (skip this if you did a odin flash to stock)
4)factory reset, wipe system, wipe both cache/dalvik
5)install rom
6)boot system
7)*(OPTIONAL) reboot to install a kernel now if needed, always wipe cache/dalvik and fix permissions after installing a kernel
8)setup phone and download titanium backup from the market
9)restore all user apps and data (you will have to put the titanium backup folder that is backed up on your computer back onto your internal storage via usb first)
Every 6 months, backup internal storage to PC and I odin to stock, much like formatting a computer
6 months is actually a long time considering how much I flash, but this device can take a beating let me tell you =P
I DO THIS WITH EVERY ROM I INSTALL, AOSP or TW
Great info, that is actually my same process when I have an issue with anything
Good read. A lot of common sense for seasoned flashers, will be great for people who are unsure.
Sent from my SGH-T999 using xda app-developers app
KorGuy123 said:
Good read. A lot of common sense for seasoned flashers, will be great for people who are unsure.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
thanks man, hoping this gets a sticky.
Danvdh said:
thanks man, hoping this gets a sticky.
Click to expand...
Click to collapse
I'll add it to my sticky
Galaxy S3 / AoCP / V4A / Turbocharged
s3 unrooting issues
I have been having some big problems with unrooting my telus SGH I747 Galaxy s3. I have flashed the stock rom using odin, did a factory reset and wiped cache and everytime i reboot it loads up the same roms i had on there at first. I have had a lot of issues with roms as well such as slow messaging times, echoing voice calls using AOKP and when i use an AOSP rom i cant connect to my phone carriers data connection at all. I read this form and decided its probably a good idea to re root as you said due to updates or whatever else but now im runing into this issue. I have ask on other forms and no one seemed to have heard of this issue. If anyone has any ideas or knows a fix i would really appreciate the help.
Custom ROM data issue
dannyteo14 said:
I have been having some big problems with unrooting my telus SGH I747 Galaxy s3. I have flashed the stock rom using odin, did a factory reset and wiped cache and everytime i reboot it loads up the same roms i had on there at first. I have had a lot of issues with roms as well such as slow messaging times, echoing voice calls using AOKP and when i use an AOSP rom i cant connect to my phone carriers data connection at all. I read this form and decided its probably a good idea to re root as you said due to updates or whatever else but now im runing into this issue. I have ask on other forms and no one seemed to have heard of this issue. If anyone has any ideas or knows a fix i would really appreciate the help.
Click to expand...
Click to collapse
So scrap the unrooting issue i have that figured out now, i just reinstalled the rom and again it doesnt have data, it is the deadly venom rom, anyone else that i know who is using this rom has absolutely no problem. I have tried a few fixes i have found via youtube, google, etc.... but none were successful. If anyone knows a fix or has any ideas please let me know.
I have an I747M S3 from a friend and trying to get it back to stable stock. It had lost it's IMEI and some NVdata corruption but I was able to resolve that searching the forums, But it has issues with apps crashing and rebooting quiet frequently. It can sometimes go feeling pretty stable ofr awhile then just kind of blows up. I have cleared away the flash counter and restored factory stock images from Odin and Keis, still having the issues. Is there a partion or something that could be getting missed? Or possible further problems related to the NVdata issues?
if you have any ideas I would appreciate it.
I used twrp to back up system, data, and boot, should I still use titanium back up to back up anything else, or is that enough to be relatively safe?
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
I rooted my Galaxy Note 10.1 2014 Edition (P600) tablet using CF AutoRoot. I ran odin and flashed the two tars. (autoroot mj4 and stock recovery mj4).
Next I decided to put TWRP on, so i opened odin and flashed TWRP. It worked fine for a few days, then suddenly i lost root on some of my applications. I opened up TWRP and tried to flash Super SU again and it had a problem clearing the cache. It then wouldn't mount the cache at all. Meaning my tablet wouldn't boot.
I managed to fix it by running autoroot again and flashing the stock recovery, but now i have issues with my tablet only working for about 5-10 minutes, then it restarts itself. I'm assuming the cache might be corrupted and it ends up getting filled and then crashes. After about 5 minutes, it freezes and then goes to a black screen and restarts itself.
Can anyone help me fix this?
you should try this method : http://forum.xda-developers.com/showpost.php?p=53125229&postcount=409
lightman33 said:
you should try this method : http://forum.xda-developers.com/showpost.php?p=53125229&postcount=409
Click to expand...
Click to collapse
As i said previously, that's the method I used.
SPV2010 said:
As i said previously, that's the method I used.
Click to expand...
Click to collapse
Try reflash stock recovery, clear cache, davik cache and data, let it boot up then power down and start over with re root method again. MAKE SURE you use the correct CF autoroot for the p600 device.
you are saying you loose root after a few days, did you remove or freeze knox apps ?
see previous message advice, you should restart with a full wipe and full flash and it should be ok. An other way is to flash a custom already rooted and knox freed.
hope it will help you, good luck.
I lost root after a few days, not that i lose root. It happened the first time and from then the problems started occurring. I froze knox applications (all 8 of them).
I did a logcat using adb to see what errors occurred and i got an error saying
Fatal Signal 7 <SIGBUS> at 0xb6a3cc64 <code = 2>, thread (changes).
Unable to open connection to debuggerd: Connection refused.
Click to expand...
Click to collapse
Does anyone know what this error means and how to fix it? I heard its a data alignment problem, but not sure how to fix it, but i assume a full format would do it.
SPV2010 said:
I lost root after a few days, not that i lose root. It happened the first time and from then the problems started occurring. I froze knox applications (all 8 of them).
I did a logcat using adb to see what errors occurred and i got an error saying
Does anyone know what this error means and how to fix it? I heard its a data alignment problem, but not sure how to fix it, but i assume a full format would do it.
Click to expand...
Click to collapse
I would say a corruption would cause this and until you reformat, otherwise, you're going to get it again. Data corruption could cause many "unknown" errors, so you should reformat and do a clean install.
Whats the best way to format if you havent got a custom recovery,stock recovery? Odin? (scary)
My issue is I get rooted ,freeze up knoxes but then when I go to install TWRP (any ver.) it doesn't take..
sorry to piggy-back but it sounded similar to my situation
Hey guys, I have the p600 and was running stock NIL1 and decided to root. I ran in to all kinds of issues, very similar to what you are experiencing but managed to fix it so haven't had the instability. I believe you're missing a crucial step. I wasn't able to mount system or wipe cache until I did this.
Here's what I recommend:
Odin back to stock recovery
Boot to stock recovery and perform a factory reset and clear cache, this part was important
Reboot to download mode
CF Auto root again
Flash TWRP
Flash rom of your choice, I'm running http://forum.xda-developers.com/gal...opment/p600ueucni1-pure-stock-rooted-t2896910 and it works great!!
Hope it works for you!!
majorassface said:
Hey guys, I have the p600 and was running stock NIL1 and decided to root. I ran in to all kinds of issues, very similar to what you are experiencing but managed to fix it so haven't had the instability. I believe you're missing a crucial step. I wasn't able to mount system or wipe cache until I did this.
Here's what I recommend:
Odin back to stock recovery
Boot to stock recovery and perform a factory reset and clear cache, this part was important
Reboot to download mode
CF Auto root again
Flash TWRP
Flash rom of your choice, I'm running http://forum.xda-developers.com/gal...opment/p600ueucni1-pure-stock-rooted-t2896910 and it works great!!
Hope it works for you!!
Click to expand...
Click to collapse
Hey What TWRP was it?
Me too! ......Ill let you know Thanks