Develop Bugs

[Q] What to do after rooting?

So..I'm pretty noobish at all this, after doing my research I've finally rooted my phone wanting to mess with setCPU, flashing roms, and getting custom themes and boot animations, unfortunately i spent all my time figuring out how to simply root and nothing beyond..
i'd be grateful if anyone could post threads or just help in general with the above topics

Become a flashaholic like the rest of us. BTW once start you can't stop.
Best advice I can give is to read, read, read and then read some more. Trust me the answers to your questions are in the 1000000s of pages.
Myn's ROM is very good. But I like Caulkins ROM the best with netarchy's 4.2.1 kernel. You don't want to use setCPU with 4.2.1 its not needed.
Just my 2 cents.
And then for some real fun start playing with the CM 6.1 RC1. That's were the fun really begins.
Sent from my PC36100 using XDA App

R1pTheJacka said:
So..I'm pretty noobish at all this, after doing my research I've finally rooted my phone wanting to mess with setCPU, flashing roms, and getting custom themes and boot animations, unfortunately i spent all my time figuring out how to simply root and nothing beyond..
i'd be grateful if anyone could post threads or just help in general with the above topics
Click to expand...
Click to collapse
The first thing I did was to start flashing custom ROMS. In the early EVO days, there weren't many choices. Now, there are tons of good options out there, so get to flashin'! You'll also get lots of good ideas hanging out in the themes and mods forum. Stroll around in the "post your screens" thread and you'll be blown away by what some folks have accomplished.
Just my thoughts, of course, I suspect you'll get lots of other suggestions.

yea unfortunately lots of these terms are like a foreign langauge to me =\
after looking up the process of installing roms i see lots of people are saying do a nandroid back up and then copying the rom, radio/WIMAX/PRI/NV updates and kernel
the definitions/translations for that?

Different parts of your phone have their own embedded software that can and doses get upgraded. For example, when you get a major update from Sprint, either OTA (over the air) or donwloaded to your PC and run from there, it not only updates your operating system (Android) and all the other little apps, but frequently your cell receiver/transmitter (radio or baseband), 4G receiver/transmitter (WiMAX) get their own software updates as well. Custom ROM creators frequently exclude these from their packages, so you have to update them separately.
Nandroid is a backup functionality you have once the phone is rooted. It is available through RECOVERY. So if you boot your phone into the BOOTLOADER by holding down the VOL DOWN and powering up, you should be able to choose RECOVERY by using VOL UP and VOL DOWN keyes as arrows, and POWER button as SELECT (or ENTER). Once in RECOVERY mode, there are several options, including backup/restore. The backup IS the nandroid backup everyone mentions. It creates an image of your phone's current setup. If you mess things up later on and the phone system is damages, you can recover by restoring this image to your phone.
Hope this helps.

R1pTheJacka said:
So..I'm pretty noobish at all this, after doing my research I've finally rooted my phone wanting to mess with setCPU, flashing roms, and getting custom themes and boot animations, unfortunately i spent all my time figuring out how to simply root and nothing beyond..
i'd be grateful if anyone could post threads or just help in general with the above topics
Click to expand...
Click to collapse
This is my first time quoting and I am pretty noobish myself...I don't know these terms either even though I spent all that time trying to root...I still haven't found out how to use a custom rom or boot, I'm a little clueless even after reading for quite awhile. :/
Sent from HTC EVO 4G via xda app

jacoballen22 said:
This is my first time quoting and I am pretty noobish myself...I don't know these terms either even though I spent all that time trying to root...I still haven't found out how to use a custom rom or boot, I'm a little clueless even after reading for quite awhile. :/
Sent from HTC EVO 4G via xda app
Click to expand...
Click to collapse
Using a custom ROM (or kernel) or boot animation is done through "flashing." Flashing is done via Recovery which can be accessed by the steps listed in a post above. I use the Amon Ra recovery and there are directions how to isntall this elsewhere on the site. I copy the ROM (or kernel or boot anim) to the root of my SD Card, boot into recovery, nandroid backup, wipe caches, wipe data, then I can specify an option to boot from zip on sdcard. (don't remember if it's high-level menu item or not) Anyway, find a Recovery you like (Clockwork or Amon Ra) and there will be specific directions on everything you can do on that Recovery's thread.
This is really a condensed version and there's way better and more thorough advice in Development and Q & A forums in stickies. I highly recommend reading those.

Did you know that you can change the whole look of the phone just by changing the system font? And it's real easy too
Sent from my blah blah blah blah

I know how to get to recovery but I don't know which one I have..and wiping data and cache does what exactly (I've wiped my battery stats before because someone said it helps your battery life)
Sent from HTC EVO 4G via xda app

jacoballen22 said:
I know how to get to recovery but I don't know which one I have..and wiping data and cache does what exactly (I've wiped my battery stats before because someone said it helps your battery life)
Sent from HTC EVO 4G via xda app
Click to expand...
Click to collapse
If you're using rom manager, it will tell you at the top what recovery is currently installed.
Hopefully you didn't "just" wipe battery stats - there's a process;
It should be done as follows (copied/summarized from the cyanogen wiki found here);
Battery recalibration
1. Charge the phone to full battery; let it keep charging until the battery says it is fully charged. Do not just wait until the light is green, it isn't always fully charged, causing a lot of inaccuracies. (You can check by going to: Settings -> About Phone -> Status -> Battery Level = Full.)
2. Wipe battery stats with Amon_Ra or ClockworkMod recoveries.
NOTE: To have the most accurate of battery stats, reboot the phone immediately after wiping the battery stats and wait for it to boot completely to the desktop. Once your entire boot is done and you have full access to the phone, go ahead and pull the charger and continue with this troubleshooter.
1. Do not charge the phone until after draining the battery completely, resulting in it automatically shutting off.
2. Recharge the phone completely and then use as you normally would.

I am surprised that no one has posted this yet.
Keep in mind, this is reference to the HTC Dream/G1 which is one of, if not the first offered Android Phone. This article explains what root is, how it was established and definition of terms. I hope this helps.
http://forum.xda-developers.com/showthread.php?t=513061
This is the informative link, which can answer a lot of questions. Just keep in mind the commands/button combos and such are different on the EVO, but in all respects is the same animal.
http://forum.xda-developers.com/showthread.php?t=543081
And then finally, the wiki with all of the answers for the HTC Subsonic/EVO
http://forum.xda-developers.com/wiki/index.php?title=HTC_Supersonic&useskin=vector

6uPMAH said:
Different parts of your phone have their own embedded software that can and doses get upgraded. For example, when you get a major update from Sprint, either OTA (over the air) or donwloaded to your PC and run from there, it not only updates your operating system (Android) and all the other little apps, but frequently your cell receiver/transmitter (radio or baseband), 4G receiver/transmitter (WiMAX) get their own software updates as well. Custom ROM creators frequently exclude these from their packages, so you have to update them separately.
Nandroid is a backup functionality you have once the phone is rooted. It is available through RECOVERY. So if you boot your phone into the BOOTLOADER by holding down the VOL DOWN and powering up, you should be able to choose RECOVERY by using VOL UP and VOL DOWN keyes as arrows, and POWER button as SELECT (or ENTER). Once in RECOVERY mode, there are several options, including backup/restore. The backup IS the nandroid backup everyone mentions. It creates an image of your phone's current setup. If you mess things up later on and the phone system is damages, you can recover by restoring this image to your phone.
Hope this helps.
Click to expand...
Click to collapse
so the primary point of the nandroid backup is to have the ability to go back to the stock ROM if i choose or even if something screw up while installing a new ROM?

Brutal-Force said:
I am surprised that no one has posted this yet.
Keep in mind, this is reference to the HTC Dream/G1 which is one of, if not the first offered Android Phone. This article explains what root is, how it was established and definition of terms. I hope this helps.
http://forum.xda-developers.com/showthread.php?t=513061
This is the informative link, which can answer a lot of questions. Just keep in mind the commands/button combos and such are different on the EVO, but in all respects is the same animal.
http://forum.xda-developers.com/showthread.php?t=543081
And then finally, the wiki with all of the answers for the HTC Subsonic/EVO
http://forum.xda-developers.com/wiki/index.php?title=HTC_Supersonic&useskin=vector
Click to expand...
Click to collapse
good looks! the terms are IMO the most important thing to get a hold of

R1pTheJacka said:
so the primary point of the nandroid backup is to have the ability to go back to the stock ROM if i choose or even if something screw up while installing a new ROM?
Click to expand...
Click to collapse
Is Nandroid back up the same that Titanium pro back up does?
fachadick said:
Did you know that you can change the whole look of the phone just by changing the system font? And it's real easy too
Sent from my blah blah blah blah
Click to expand...
Click to collapse
How do you do this?
fachadick said:
If you're using rom manager, it will tell you at the top what recovery is currently installed.
Click to expand...
Click to collapse
I have 2.5.0.1. Is this the recovery that you would have to reboot in if something goes wrong and what does the numbers mean?
TIA!

phillip623 said:
Is Nandroid back up the same that Titanium pro back up does?
How do you do this?
I have 2.5.0.1. Is this the recovery that you would have to reboot in if something goes wrong and what does the numbers mean?
TIA!
Click to expand...
Click to collapse
Nandroid isn't the same thing as titanium, think of nandroid as an image, sort of like a disk image or a windows restore point. Once restored, it will take you back to exactly where you were at the time of the backup.
The numbers that you see in Rom Manager represent the recovery version. You currently have clockworkmod version 2.5.0.1 installed.
It's been spelled out above, and elsewhere through the forums, but I'm bored and I want to clean up this post anyway (I tried that new 8whatever keyboard again - still hate it. And before I cleaned it up, this post was three paragraphs of broken english), so here are some basic steps spelled out on what to do immediately after rooting, along with some terms.
The first thing you want to do once rooted is go into rom manager, and towards the bottom, hit the option that says "Flash Alternate Recovery". Once you do this, you'll notice at the top where it used to say Current Recovery: ClockworkMod 2.5.0.1 it will now say Current Recovery: Ra Recovery 1.8.0.
Now close out Rom Manager, and turn off the phone. Turn it back on while pressing down on the volume. The screen with the skateboarding Andy's will show up - this is the hboot screen. Among other things, this screen will tell you the version of hboot you're running, and whether you're S-ON or S-OFF. There may be a few different options listed here, but we're only interested in the one that says Recovery.
Select Recovery. The phone will reboot, and you should end up on a screen with green text. At the top it will say Android System Recovery, and all the way at the bottom, it will say Build : RA-evo-v1.8.0 From here select Backup/Restore. There are a few options, but note the two important ones - Nand backup, and Nand restore. Select Nand backup. It will ask if you're sure, so say yes. It will take awhile and the bottom of the screen will fill with dots. When it's done select Return then Reboot System Now. Congratulations, You just performed your first Nand Backup using Amon Ra recovery.
When you can, mount your phone as a drive, and go into folder inside the nandroid folder on your sdcard. You'll see a folder with today's date. Copy it somewhere safe on your computer. If you're interested, you can look in that folder and note the wimax.img file - this is where you're backing up the infamous RSA Keys (I'm not explaining what that is here, just know that you REALLY want to have this backed up, and kept somewhere safe). once the copying is done, unmount as a drive, and disconnect from your computer. Congratulations, now it's playtime.
Use either Titaniaum Backup or MyBackup Pro to back up all of your apps and data. Mybackup Pro will also backup call logs and text messages and things like that - I'm pretty sure Titanium does also, but I'm not sure. Your contacts should be backed up to google for easy restoration later.
Head over to the dev section and find a ROM that appeals to you. You can go with completely stock rooted if you want (which is essentially where you are now, but stock rooted would have the latest OTA updates when they come out), or stock with some tweaks to Sense, or non Sense at all (the most popular of these is CM, which rebuilds Froyo from the ground up.) Sense refers the stock launcher called Rosie, as well as some buried functionality in the phone - for example the mail, calendar, and dialer apps look and act different between Fresh and CM roms. Sense is a UI developed by HTC to go over what is commonly referred to as vanilla android/AOSP. AOSP stands for Android Open Source Project and is what google released on the n1, CM is an AOSP rom. Also, you're looking for a Deodexed rom (as opposed to odexed) so you can theme it later if you want.
Once you find a rom you like, download it to the root of your sd card (you may want to download it on your computer and move it to your sdcard). Refer to the above to get back into recovery, but this time instead of selecting Backup/Restore, select Wipe. Select Wipe data/factory Reset and let it do its things, then select Wipe cache, and let it do it's thing, then select Wipe Dalvic-cache, and let it do it's thing. What you've just done is erased all of the personal and superfluous data that was in the phone - you want to make sure that when you load the new rom, you're loading it on an empty slate, and that there's nothing of your old data left that could possibly corrupt something in the new rom. Some people say to wipe all of those options 2 or even 3 times each - I don't buy that though. Also, don't worry about the other wipe options you had there. Not needed now.
So once you've wiped, hit return, and select Flash zip from sdcard. It will pull up a list of .zip files found on the root of your sdcard. select the rom you just downloaded, and let it install. This may take a while. Don't freak. Once it's done, select Reboot system now. This will take a while too, maybe even a few minutes. Don't freak. Once it eventually boots up, restore all of your stuff with either Titanium or MyBackup Pro. Congratulations, You just flashed your first rom.
Now head over to the themes and apps section. Find a theme that interests you. Make sure its compatible with your rom (either sense or cm) and download it. Flash this the same way you flashed your rom, but you may or may not need to wipe first. Always refer to the op of those threads for specific instructions.
Finally and most importantly - head over to the thread in my sig and find a new font you like. All the cool kids are doing it. When you find one you like, copy it to your sdcard and flash it the same way you've been flashing everything else. You don't need to wipe anything for those though.
Tips;
1: never forget to wipe. As a rule, when flashing roms, you'll be wiping what people refer to as all three - that means wipe data/factory reset, wipe cache, and wipe dalvic cache. When flashing kernels or themes, you'll generally just be wiping cache and dalvic cache. Again though, always refer to the instructions in the op in which you found whatever it is your flashing.
2: if you'll be flashing both themes and roms, and possibly kernels, never flash in the same recovery session. So rom first, full reboot, then kernel, full reboot, then theme, full reboot. In that order, wiping and rewiping as needed.
3: give you're rom at least a few days before you give up on it, most need time to settle into your phone so to speak, and need a few battery cycles to get to peak performance, which brings up to
4: You should wipe your battery stats whenever you flash a new rom. Remember you saw that option under Wipe back in recovery? Well now you get to use it. I posed the link and process above in the thread.
5: At this point most people use Amon Ra instead of clockworkmod because there seems to be uncertainty as to weather or not clockworkmod correctly wipes. ONLY Amon Ra backs up the wimax.img, clockwork does not.
6: rom manager is a graphical front end for clockworkmod. A lot of people still use it to flash, becasue it's so easy to use, it can be used to download roms directly in the app, and doesn't require the zip file to be on the root of the sdcard - it van be anywhere on the card. Don't forget though, you can download the rom through the app if you want, but still switch to amon ra to flash it.
7: you cannot restore a nand backup you make with amon ra with clockwork, and you cannot restore a nand backup you make with clockwork with amonra.
8: on the off chance you need to change your hboot version for any reason, you can only restore nand backups with the same hboot version that they were backed up with. NOTE, were talking about hboot here, not recovery.
Damn, that was a lot of of text. Sorry about that.

i would recommend reading this thread: http://forum.xda-developers.com/showthread.php?t=790427
i have only been in the android world for about 3 months now, and was able to root and flash custom roms with ease within a few weeks of getting my evo. its really not hard at all once you understand the process.
as far as what rom to flash, that depends on the user. different rom have different features. if i were you, i would recommend reading the specs on each rom before flashing. some may have features missing, such as 4G, full camera support and such. And usually all that info is provided in the thread along with the rom. so, pay attention to that.
as for me, the goal for rooting was to do certain things that was only possible with root. such as, Nandroid backup, ShootMe, Wifi Tether and to disable some of the Sprint apps. so, i am using a stocked rooted rom. it is what it says. the same stock rom as the factory but rooted.
a lot of ppl use various custom roms to get better battery life. battery life on stock roms have improved quiet a bit lately. at least in the past 3 months, i have noticed a big improvement. hope this helps answer some questions.
and remember to always do a nandroid backup. i also use My Backup Pro to backup my Call Logs, SMS & MMS.

few questions about flashing ROMs..
1. i still have to backup all my contacts,apps,etc, i have titanium backup pro and if i back them all up how do i get them back once the new ROM is flashed?
2. I know im supposed to do a nandroid backup but do i need those special recovery images first? (AmonRA/Clockwork)
3. What's the purpose of ROM M...anager in all of this?

ok, so titanium pro will backup everything, even how your homescreen is set up.
the nandroid is for if there is a problem, or if you want to go back. ALWAYS HAVE AT LEAST ONE BACKUP MADE WITH AMON AT ALL TIMES OR YOU COULD PERMANENTLY LOSE 4G (FOREVER, NO FIX EVER)
rom manager can control clockwork recovery while booted up in a touch screen interface. it removes the need to use the annoying volume keys. doesnt work with amon.
i would highly reccomend amon to you. it is just that much better, but doesnt work with rom manager. volume keys arent that hard anyways. use amon.
ONCE AGAIN, ALWAYS HAVE AT LEAST ONE AMON BAKCUP AT ALL TIMES, AND ALWAYS BACKUP BEFORE DOING ANYTHING EVEN SLIGHTLY CONSIDERED MODDING. SERIOUSLY, TAKE 4 MINUTES OUT OF YOUR DAY TO WATCH DOTS APPEAR, AND SAVE YOURSELF 200 DOLLARS OR HOURS OF SETTING STUFF BACK UP. SERIOUSLY. DO IT.

Thanks for the detailed and informative post! This should be in the question and answer thread. I'm finally able to change my font and onto ROMS. I'll reply back once I'm on a normal keyboard.

R1pTheJacka said:
few questions about flashing ROMs..
1. i still have to backup all my contacts,apps,etc, i have titanium backup pro and if i back them all up how do i get them back once the new ROM is flashed?
2. I know im supposed to do a nandroid backup but do i need those special recovery images first? (AmonRA/Clockwork)
3. What's the purpose of ROM M...anager in all of this?
Click to expand...
Click to collapse
1. all your contacts are backup-ed on your google account. when you sign on to the google account after you flash a new rom, the contacts will be automatically downloaded to the phone. so, no further work needed to be done there. i use My Backup Pro to backup my SMS/MMS and Call logs. I think it is very similar to Titanium. Basically you use the program to backup the stuff you need onto your SD Card. Then, once you have flashed your new rom, you install Titanium or the My Backup Pro and use the Restore feature to restore what you need. As far as Apps go, I found that it was better to use App Brain, since that keeps a log of all the apps install on the phone, its usually a breeze to re-install all of them through that.
2. Amon RA & Clockwork perform the same function. you use either to flash custom roms, perform nandroid backups, etc. so, once you root your phone, you will need to install one of these.
3. ROM Manager.. does what the name says it does. you can change the rom on your phone using that utility app. But i think the Amon Ra/Clockwork Recovery method is the preferred way of changing out roms.

[Q] Evo 4G Doesn't Like to Boot in New ROMs

Most of this info may be extraneous, but I'll throw it in here just in case.
A few days ago, I decided to root my Evo 4G from the stock, 2.2 OS (HTC Sense?) using the Unrevoked website (using a PC running XP). It worked fine and got me rooted. Trouble began to arise when I attempted to install new ROMs such as CM-6 and Salvage. I decided to fork out a few bucks and pay for the ROM Manager Pro app, thinking that it would save me considerable hassle. After downloading the most recent CyanogenMod 7.0.0-RC2 through the app, I selected the "Install Gapps as well" option but did NOT check "Wipe Data and Cache" before letting the app do its work of installing and flashing and whatever for me. Upon completion of the installation, my phone then automatically rebooted normally, but became stuck on the boot image of the android on the skateboard with the spinning arrow. I let that sit for about 6 hours (I went to bed) thinking it was just first-time setup before I battery-pulled and booted into recovery, restored my original settings, and started over. This time I did everything the same except remembered to check "Wipe Data and Cache," as an online tutorial told me I ought to when switching from stock to another ROM, and it installed and booted correctly. I ran CM-7 for a day before deciding to try out a different ROM, downloading and installing it through the same interface, ROM Manager Pro. Everything went well until it got stuck, again, at the boot image. After about 30 min I battery-pulled and tried to restore back to CM-7, only to be greeted by another endless boot image. I was able to restore back to my original backup, but am now back to square one. What the heck am I doing wrong?
EDIT: That original backup I mentioned was made immediately after rooting the phone in preparation to install CM-7.
Sorry my technical knowledge is grossly lacking, I just got into this game. Patience and any help is GREATLY appreciated.

When switching from one rom to another, it is always important to remember to wipe data and cache. There are a few rare cases that it is not necessary to do this, but I really recommend that if you are just starting out, wipe them both for good measure until you learn enough that you can tell when you can get away with not wiping. Also, I know that one common problem that people experience with Rom Manager is that Unrevoked contains the Amon_RA recovery image, and Rom Manager is designed to with with the Clockwordmod recovery. In Rom Manager, you should be able to see which one you are currently using, and you should also be able to use Rom Manager to download and flash the latest Clockworkmod recovery. I too use Rom Manager as a convenient way of making sure that my rom is up to date, and to download roms, but I recommend that when you want to change roms, you do it by booting into recovery mode, and performing the wipe and install manually, as I have found that this method will help prevent errors like boot loops. I hope this helps!
P.S. Feel free to PM me if you ever need any help.
Sent from my DESTROYED Evo using XDA Premium app

So, for example, if I wanted to restore back to my CM-7 backup, would I want to boot into recovery and just restore to the backup or re-flash the ROM, then boot into recovery and try to restore it? I'm still getting the endless boot image.
Oh, and I am running clockworkmod, as per the instructions for ROM Manager.
Thanks for the quick reply!

Move CM7-RC2.zip and the gapps.zip (or whatever its name; ex: filename.zip) to the root of your SD card by plugging it into your computer via USB and mounting it as a drive. Go ahead and exit all that.
Turn off your phone.
Hold volume down + power.
Go to Recovery.
Wipe the following: data/factory reset, cache, (in Advanced, accessed from same menu) wipe dalvik.
Go back.
Install .zip from SD.
Choose your .zip(s) [CM7, Gapps] from your card, flash, and presto!
I'm not too experienced with ROM Manager as I do not use it whatsoever, but I know the above stated method should work perfectly.
Furthermore,
I'm not sure if a format_all.zip should be used here with CM7. If someone who knows would like to chime in about this, that'd be great.

totalanonymity said:
Move CM7-RC2.zip (or whatever it's name; ex: filename.zip) to the root of your SD card by plugging it into your computer via USB and mounting it as a drive. Go ahead and exit all that.
Turn off your phone.
Hold volume down + power.
Go to Recovery.
Wipe the following: data/factory reset, cache, (in Advanced, accessed from same menu) wipe dalvik.
Go back.
Install .zip from SD.
Choose your .zip from your card, flash, and presto!
I'm not too experienced with ROM Manager as I do not use it whatsoever, but I know the above stated method should work perfectly.
Furthermore,
I'm not sure if a format_all.zip should be used here with CM7. If someone who knows would like to chime in about this, that'd be great.
Click to expand...
Click to collapse
This is the way I would flash any roms that you want from here on out.
I have used CM7 and have not had to use the format.zip from calk, so I don't think it is absolutely necessary, but it probably wouldn't hurt.
Sent from my DESTROYED Evo using XDA Premium app

I recommend flashing the format all zip whenever switching ROMs. It completely formats the various partitions and leaves a blank slate for the new ROM to be installed. I also recommend using ROM Manager to flash Amon_Ra recovery and do everything manually instead of using ROM Manager. People seem to have a lot less problems with Amon, and I have never had any issues flashing ROMs or kernels or anything with it.
You won't be able to restore a Clockwork backup with it but it never hurts to just flash a new ROM and restore your Titanium backups, assuming that you made them.

Wow, thanks all for the fast replies!
Ok, I now have Destroyer installed and working (finally!), but I am experiencing the apparently common black-on-black text box problem. I downloaded the .zip to be flashed to fix this, but am not sure how to proceed. Do I just do the exact same thing as flashing a new ROM entirely or is there something special I need to do to let the phone know that it is an update?

RossGoldenstein said:
Wow, thanks all for the fast replies!
Ok, I now have Destroyer installed and working (finally!), but I am experiencing the apparently common black-on-black text box problem. I downloaded the .zip to be flashed to fix this, but am not sure how to proceed. Do I just do the exact same thing as flashing a new ROM entirely or is there something special I need to do to let the phone know that it is an update?
Click to expand...
Click to collapse
Not sure with ROM Manager but you can flash that from recovery the same way you flash a ROM. I'm sure there is an option in ROM Manager to flash it, I just couldn't tell you where. Do not wipe anything before flashing that though. Only wipe when flashing ROMs and kernels.

Go back into Recovery and flash that .zip the exact same way you flashed the ROM. Minus the data wipe.
Others: Does he wipe cache/dalvik as well? I've seen some posts say to do that when flashing mods that are flashable .zip and some don't. I've done both ways and seen no negative consequences (as of yet).

Yeah, that last post was dumb, I clicked "Submit" before I tried anything on my own. Flashing it the exact same way minus data wipe worked perfectly, though the prediction boxes for input in the market app (when you hit "search" and start typing, the things that drop down to give suggestions) still appear to be black on black. Bleh.
Also, the Dalvic wipe before installing was a good idea; I don't know for sure if it made a difference but a good habit to get into.
EDIT: By the way, this has got to be the least grammatical/spelling errors in a forum thread I've ever seen. I think I may like this site...

Wiping the cache and dalvik most likely isn't necessary but it can never hurt.

RossGoldenstein said:
Yeah, that last post was dumb, I clicked "Submit" before I tried anything on my own. Flashing it the exact same way minus data wipe worked perfectly, though the prediction boxes for input in the market app (when you hit "search" and start typing, the things that drop down to give suggestions) still appear to be black on black. Bleh.
Also, the Dalvic wipe before installing was a good idea; I don't know for sure if it made a difference but a good habit to get into.
EDIT: By the way, this has got to be the least grammatical/spelling errors in a forum thread I've ever seen. I think I may like this site...
Click to expand...
Click to collapse
I'm really new to this stuff myself (rooted for the first time ~2 days ago) and so I'm unsure how to further fix the blacked out predictions in the Market. Perhaps you could try contacting those within the thread of the ROM you downloaded, specifically citing that you installed the initial blacked out fix so that they don't redirect you back to the fix you've already applied, testing your patience and furthering your wait for perfection.
Aye, this site has got to be full of some of the most fluent English-speaking persons I've found on the internet.

[Q] Crashing apps and loss of service?!

Hey guys, long time browser, first time poster, but not a reason for celebration, alas.I come to you guys out of frustration after hours of being unable to solve my issue cruising the interwebs, and the thread title kinda says it all.
To start from the beginning, I recently delved into the rooted world by means of towelroot (kitkat 4.4.2), installed xposed framework, got the modules XBlast and XPrivacy, and you might have guessed, fiddled around with each. Everything was fine and dandy until I was having issues receiving/making calls through an app (LINE, if you know it), and so I attempted to figure out what the issue was, very much assuming XPrivacy to be the culprit. Couldn't get it to work, which is when I decided to restore my backup I made using Clockwork. Should have been nice and smooth sailing, but...
Upon having it "restored" I booted on into it, which is when I got smacked in the face; as soon as I'm booted, most, if not all, my apps are reporting that they have stopped working by a bombardment of error messages in endless succession, making just browsing the home screens almost impossible. Also with this barrage came the lack of cell service, a nice white n' slashed out circle in what should be my bars of signal. I tried again to restore my phone from my backup. Same issue, but I did notice during the recovery it made mention of something like "secure_android" missing? This sent me on my hours of head banging, turning up *possible* resolutions, which didn't work. I've tried flashing the stock bootloader, gapps, and nothing. Now, my data and apps are all still there and I can get into recovery without issue, it's just the pain of not being able to actually using any of it.
I have debugging switched on on my phone, but do not have some sort of adb app installed on it, nor could I access any market place to try. I'm not so sure I would be able to install anything on my phone given my current circumstances, anyway.
Please, if any of you out there have some idea as to what is going on, I'm all eyes (as ears on a forum don't work so well)! If there are any details I may have omitted and so on, just let me know and I'll supply it--
Thank you all so much in advance for any possible steps that may resolve this issue!

Fingerless said:
Hey guys, long time browser, first time poster, but not a reason for celebration, alas.I come to you guys out of frustration after hours of being unable to solve my issue cruising the interwebs, and the thread title kinda says it all.
To start from the beginning, I recently delved into the rooted world by means of towelroot (kitkat 4.4.2), installed xposed framework, got the modules XBlast and XPrivacy, and you might have guessed, fiddled around with each. Everything was fine and dandy until I was having issues receiving/making calls through an app (LINE, if you know it), and so I attempted to figure out what the issue was, very much assuming XPrivacy to be the culprit. Couldn't get it to work, which is when I decided to restore my backup I made using Clockwork. Should have been nice and smooth sailing, but...
Upon having it "restored" I booted on into it, which is when I got smacked in the face; as soon as I'm booted, most, if not all, my apps are reporting that they have stopped working by a bombardment of error messages in endless succession, making just browsing the home screens almost impossible. Also with this barrage came the lack of cell service, a nice white n' slashed out circle in what should be my bars of signal. I tried again to restore my phone from my backup. Same issue, but I did notice during the recovery it made mention of something like "secure_android" missing? This sent me on my hours of head banging, turning up *possible* resolutions, which didn't work. I've tried flashing the stock bootloader, gapps, and nothing. Now, my data and apps are all still there and I can get into recovery without issue, it's just the pain of not being able to actually using any of it.
I have debugging switched on on my phone, but do not have some sort of adb app installed on it, nor could I access any market place to try. I'm not so sure I would be able to install anything on my phone given my current circumstances, anyway.
Please, if any of you out there have some idea as to what is going on, I'm all eyes (as ears on a forum don't work so well)! If there are any details I may have omitted and so on, just let me know and I'll supply it--
Thank you all so much in advance for any possible steps that may resolve this issue!
Click to expand...
Click to collapse
Sounds like your backup was a downgrade (old version).
I would suggest doing a factory reset, test it. If that doesn't do it, use Odin to flash stock firmware (which can be found in the general section stickies).

BWolf56 said:
Sounds like your backup was a downgrade (old version).
I would suggest doing a factory reset, test it. If that doesn't do it, use Odin to flash stock firmware (which can be found in the general section stickies).
Click to expand...
Click to collapse
Thanks for responding! I did try a wipe data/factory reset via CWM, then restored from there. Didn't work. I'm not sure if there is a particular order in how it should be done such as "factory reset, reboot phone into recovery, restore" or if I should be able to get away with "factory reset, restore", the latter being what I did. I also got a hold of a bootloader file and modem base band for build I747UCUFNE4, if those would be useful in any way.
If it's of any help, I somehow got the Unofficial Omni ROM 4.4.4 to work without any issue, but not quite happy enough with the overall interface of it, yet slowly adapting having installed a touchwiz launcher just to hold me over.
I've tried locating the backup CWM created on my phone so that I could store it on my computer and generate another backup as from what I read, the unpaid version only allows you one at a time, but had no luck digging through my directories. I'm currently investigating this online nandroid backup thing to see if there's anything to it.
I've also come across some file labeled "I747UCUFNE4_Stock_Rooted_Deodex" which is a zip, but I'm reading ODIN uses tar as it's compression of choice? Does this mean I should flash this file via recovery, or? Also, the file size is a whopping 920MB or so... that normal? (Edit: this is where I found the file http://forum.xda-developers.com/showthread.php?t=2788357 which says to flash in recovery)
Thanks again for your response! I was really thinking my problem would just be glanced over.

Fingerless said:
Thanks for responding! I did try a wipe data/factory reset via CWM, then restored from there. Didn't work. I'm not sure if there is a particular order in how it should be done such as "factory reset, reboot phone into recovery, restore" or if I should be able to get away with "factory reset, restore", the latter being what I did. I also got a hold of a bootloader file and modem base band for build I747UCUFNE4, if those would be useful in any way.
If it's of any help, I somehow got the Unofficial Omni ROM 4.4.4 to work without any issue, but not quite happy enough with the overall interface of it, yet slowly adapting having installed a touchwiz launcher just to hold me over.
I've tried locating the backup CWM created on my phone so that I could store it on my computer and generate another backup as from what I read, the unpaid version only allows you one at a time, but had no luck digging through my directories. I'm currently investigating this online nandroid backup thing to see if there's anything to it.
I've also come across some file labeled "I747UCUFNE4_Stock_Rooted_Deodex" which is a zip, but I'm reading ODIN uses tar as it's compression of choice? Does this mean I should flash this file via recovery, or? Also, the file size is a whopping 920MB or so... that normal? (Edit: this is where I found the file http://forum.xda-developers.com/showthread.php?t=2788357 which says to flash in recovery)
Thanks again for your response! I was really thinking my problem would just be glanced over.
Click to expand...
Click to collapse
I meant factory reset without restoring.
But now that you're back up and running, there's no need for it (unless you flash another ROM). You could flash NE4 if you wanna get back on the official ROM but there are also tw custom ROM which you can look into (you're currently using an aosp one).
As for the 920mb, yeah.. That's Sammy at its best, bloating their ROMs.

BWolf56 said:
I meant factory reset without restoring.
But now that you're back up and running, there's no need for it (unless you flash another ROM). You could flash NE4 if you wanna get back on the official ROM but there are also tw custom ROM which you can look into (you're currently using an aosp one).
As for the 920mb, yeah.. That's Sammy at its best, bloating their ROMs.
Click to expand...
Click to collapse
You think it would be safe to do a factory reset and try to restore just the data from my recovery? Or is it possible that the data is somehow the issue with everything going wonky?
I'm very new to the ROM thing, Omni was easy to get up and running, but actually playing with a ROM was more of a last ditch effort to see if the problem would be resolved that way and give any sort of indication as to what the issue was (still haven't the sllightest). It's currently not rooted (at least according to my root checker) and the towelroot method doesn't seem to work on it. I kinda need to be rooted if I wanted to make a nandroid, I really want to make a back up of what I currently have set in case I screw the pooch trying to get things back to "normal", yet I'm afraid of overwriting my only recovery and losing whatever data is embedded, though I'm not too deeply saddened by the thought of not having chat histories and whatnot, it would just be nice to have. Perhaps you have thoughts, or anyone else out there, on the matter? I know my first step would be to at least root my current ROM, then back up, I found this as a means to root Omni (http://forum.xda-developers.com/showthread.php?t=2672160), but how do I determine whether I'm using an ARM based or x86 based device?
Good to know the file size for the stock ROM is considered normal. I didn't even consider carrier/Samsung bloat to have such a huge impact.
Thanks, yet again!

[Q] IMA Idiot

I've been a flashaholic for years. But this evening I bit off more than I can chew and get my 7A into a borked state:
http://www.oppoforums.com/threads/t...out-for-oppo-find-7a.17952/page-8#post-229284
I did that. things got weird and brick like. I ran the "split" scripts to restore the normal 7A partition layout, but something is missing. I was able to restore my backup but systemui and sundry other bits crash perpetually. The device is borked.
Is there a solid procedure for getting the partition tables all sorted and proper as I assume that's where things are hosed? I have access to a second 7A I could use of cloning is possible...dunno. I'm out of my depth on this particular mess.
Thanks!

If you followed the tutorial you will have a full backup of all critical partitions in the unified folder of your sdcard for manual restoring of your partitions.

The log is full of "Couldn't backup Critical Partitions." Running the split scripts and restoring from my backup results in a phone that cosntantly crashes in systemui and sundry other components. I assume I screwed up somewhere*.
* by which I mean due to impatience and a lack of progress feedback I assumed the thing and hung and rebooted too soon.

I managed to do something similar, the unified layout wasn't working correctly where I'd tried to insert modified boot.img into different nightlies and I didn't back up as I wanted a fresh start anyway.
To be honest I don't remember exactly what I ended up doing but I'm around 80% sure it was this or at the least hopefully this will give you more to work with.
See the thread here
Install the modified TWRP and install the modified CM rom. At this point it seems like you could leave it and probably have a working phone.
Otherwise flash the original TWRP back, and remove the SD Card, you ought to be able to format everything.
Install whatever rom and hopefully everything will be back to normal.
Otherwise if you're still receiving those errors it could well be the backups are done for, might be worth trying flashing the original rom over your backup and see how that treats you.

I got it sorted out and documented the process on the oppo forums...fun times.
Sent from my X9006 using XDA Premium 4 mobile app

[OFFICIAL][RECOVERY] Cannibal Open Touch v3.0 Alpha Builds (latest: Alpha 11)

Cannibal Open Touch 3.0 Alpha 11
Disclaimer:
While we try to test our work as much as possible, it is always a possibility that something could go wrong and screw up your phone. We are not responsible for any damage that is done to your device, either directly or indirectly, as a result of using Cannibal Open Touch or any other Project Open Cannibal projects. Any damage done to your device is your responsibility and your responsibility only. We do this for fun, and we simply like to share our work.
What is Cannibal Open Touch?
Cannibal Open Touch is a custom recovery (like ClockworkMod or TWRP), created purely out of love for the platform and the desire to contribute something cool to the community. The name embodies everything that Cannibal Open Touch is. We take what we believe are the best features of popular recoveries like TWRP and ClockworkMod and, well, cannibalize them along with rolling out our own features.
Features:
Full Touch UI
Complete theme support, including app for management of themes (we'll get to that in a sec)
On-device backup and restore
Backup and restore via ADB
Much much more planned!
Bugs:
During installation, the standard Android installing icon gets displayed instead of the custom dialog box.
If you find a bug, please do not report it here! Instead, report it in the GitHub repository!
Screenshots
See the Screenshots tab above. (Or click me if you're using Tapatalk!)
Nandroid has been replaced!
Nandroid is in fact gone, and has been replaced with a much more robust backup solution. Backups can now be made either with ADB (the recommended way) or via the new Backup and Restore item in the main menu. Backups made via the built-in menu can be copied to a PC and restored via ADB, and backups made via ADB can likewise be copied to your device and restored using the Backup and Restore menu.
Code:
adb backup -f mybackupfilename.ab boot system data cache
You can also restore said backup by using adb, like so:
Code:
adb restore mybackupfilename.ab
Downloads:
Cannibal Open Touch bacon builds (latest: CannibalOpenTouch-2.99.11_bacon-2015041308.img)
How to install:
Download the latest Alpha image
Reboot to bootloader:
Code:
adb reboot bootloader
Flash the image with fastboot
Code:
fastboot flash recovery /path/to/downloaded/recovery.img
Boot into recovery mode
Alternatively, you may boot the image instead of flashing it:
Code:
fastboot boot /path/to/downloaded/recovery.img
Changelog:
3.0 Alpha 10 (2.99.10
Themes are now stored in /cache/cot/themes to fix an issue introduced with FDE.
3.0 Alpha 9 (2.99.9)
Real menu scrolling! (but volume keys still work)
All backup/restore operations now verify that you want to take action
Resized UI to be more usable on all device resolutions
Themes can now display a battery charge indicator (depends on individual theme settings)
3.0 Alpha 8 (2.99.8) (not released)
Not released
3.0 Alpha 7 (2.99.7)
On-device backup and restore
3.0 Alpha 6 (2.99.6)
Complete theme support
Recovery settings (Theme settings and Unsigned ZIP flashing)
The preceding list is not 100% complete. See the project source code page for the full commit list.
Cannibal Open Touch themes app:
We are currently seeking Alpha testers for an app that will let users download and choose themes without rebooting to recovery mode. Currently there are 20 slots open. If you wish to join please PM me. The only requirement is you must have a Google+ account and are willing to submit proper bug reports, should any arise.
Cannibal Open Touch Themes:
You can now make your own themes for Cannibal Open Touch! See the example themes (it's pretty self-explanatory). Themes must be installed in /sdcard/cot/themes/theme_name (or /data/media/cot/themes/theme_name) in order to work. Please feel free to submit pull requests to have your custom themes added to the theme repository. They will also be packaged and made available to download via the Cannibal Themes app (mentioned above)!
Contribute to Project Open Cannibal
If you like our work and want to see more, consider a donation to the project!
Project Open Cannibal gerrit: http://review.projectopencannibal.org
Credits:
tdm, for the superb touch code (and lots more)
sblood86, for joining the project and leading the charge to greatness
thenameisnigel, for picking up our webhosting while I was gone
anyone else who has ever contributed to any Android-related project
XDA:DevDB Information
Cannibal Open Touch, Tool/Utility for the ONEPLUS ONE
Contributors
drewwalton19216801, thenameisnigel, Sblood86, tdm, CyanogenMod, Koush and many others
Source Code: https://github.com/ProjectOpenCannibal/android_bootable_recovery-cm
Version Information
Status: Alpha
Created 2014-10-10
Last Updated 2015-04-13

Reserved for future use

Sorry but never need this recovery i think. Without Nandroid is a no go here.

Interesting perspective on nandroid

any screens?

So what happens if your out away from your PC and you flash something that goes wrong. No backup on your phone to restore...thanks but no thanks.
Edit: In addition what if you're not by your PC and you want to make a backup before flashing something? You have to wait till you get home? Kind of defeats the fact that these are cell phones and not tied to a cord.
Sent from my A0001 using XDA Free mobile app

Thanks for your work! This will get intresting by time, I think

bp328i said:
So what happens if your out away from your PC and you flash something that goes wrong. No backup on your phone to restore...thanks but no thanks.
Edit: In addition what if you're not by your PC and you want to make a backup before flashing something? You have to wait till you get home? Kind of defeats the fact that these are cell phones and not tied to a cord.
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Short answer: one should not be messing with one's phone while away from their computer.
Long answer: we're weighing the logistics of adding on-device backup capabilities to Cannibal Open Touch. There are serious legitimate data security concerns that do weigh heavily on our decisions in regard to this subject.

gd6noob said:
any screens?
Click to expand...
Click to collapse
Please read the entire post. Specifically the section labeled "Screenshots"

drewwalton19216801 said:
Short answer: one should not be messing with one's phone while away from their computer.
Long answer: we're weighing the logistics of adding on-device backup capabilities to Cannibal Open Touch. There are serious legitimate data security concerns that do weigh heavily on our decisions in regard to this subject.
Click to expand...
Click to collapse
You're kidding I hope...
I find my self out with my wife while she's shopping and while I'm sitting waiting for her I'll check out XDA to see if there is anything new and never have a problem or even a second thought about flashing something because I have a backup.
I'm 100% sure I'm not the only person that flashes things while away from my PC.
No disrespect meant but without on-device backups this recovery sounds better suited for a land line phone than a cell phone.

bp328i said:
You're kidding I hope...
I find my self out with my wife while she's shopping and while I'm sitting waiting for her I'll check out XDA to see if there is anything new and never have a problem or even a second thought about flashing something because I have a backup.
I'm 100% sure I'm not the only person that flashes things while away from my PC.
No disrespect meant but without on-device backups this recovery sounds better suited for a land line phone than a cell phone.
Click to expand...
Click to collapse
Nope not kidding.
And if that backup that you didn't give a second thought about somehow got corrupted without your knowledge you'd be toast.

drewwalton19216801 said:
Nope not kidding.
And if that backup that you didn't give a second thought about somehow got corrupted without your knowledge you'd be toast.
Click to expand...
Click to collapse
True, but the odds of that happening?
If it did I would try one of the other four I have on my phone and at least their there to try. Also since way back to the Verizon Moto OG Droid I've NEVER had a backup corrupted.
But hey...good luck with your recovery!

I like the idea behind it to backup on the pc. But as others said already i dont want to miss the nandroid as i am doing many backups on my otg while at work or waiting. Maybe you should consider to give both options nandroid or PC.

bp328i said:
True, but the odds of that happening?
If it did I would try one of the other four I have on my phone and at least their there to try. Also since way back to the Verizon Moto OG Droid I've NEVER had a backup corrupted.
But hey...good luck with your recovery!
Click to expand...
Click to collapse
I can see both sides of the discussion as legitimate. I have had nandroid backups corrupt more than once due to flawed media. While inconvenient, other files on the device worked and I was not toast.
The philosophical argument is interesting but I suspect ultimately will not be compelling to most in the community. Another piece of code that I am not interested in using.
I certainly appreciate the efforts in producing the recovery and the spirit in which it is shared.

Coug76 said:
I can see both sides of the discussion as legitimate. I have had nandroid backups corrupt more than once due to flawed media. While inconvenient, other files on the device worked and I was not toast.
The philosophical argument is interesting but I suspect ultimately will not be compelling to most in the community. Another piece of code that I am not interested in using.
I certainly appreciate the efforts in producing the recovery and the spirit in which it is shared.
Click to expand...
Click to collapse
I 100% agree, I love seeing new development and by no means am I trying to put the OP down or discourage his/her efforts.
I use to develop/theme for the OG Droid, HTC Eris, HTC Thunderbolt, and and posted up a few mods for the OnePlus One as well. I just don't have the time to put in anymore.
I'm 100% sincere when saying good luck with the recovery.

Coug76 said:
I can see both sides of the discussion as legitimate. I have had nandroid backups corrupt more than once due to flawed media. While inconvenient, other files on the device worked and I was not toast.
The philosophical argument is interesting but I suspect ultimately will not be compelling to most in the community. Another piece of code that I am not interested in using.
I certainly appreciate the efforts in producing the recovery and the spirit in which it is shared.
Click to expand...
Click to collapse
We see both sides as well. As stated earlier we are definitely weighing adding on-device backups back in to Cannibal Open Touch, but no guarantees (and definitely no ETAs ).
We've been doing recovery development for a fairly long time (since 2011, in fact) so we have to weigh the needs and wants of the users with legitimate security issues (as well as the needs and wants of the Cannibal dev team). The official CyanogenMod recovery (which this is mostly based on) does not (and will never) do on-device backups for this reason, so we also have to take that into consideration.

drewwalton19216801 said:
We see both sides as well. As stated earlier we are definitely weighing adding on-device backups back in to Cannibal Open Touch, but no guarantees (and definitely no ETAs ).
We've been doing recovery development for a fairly long time (since 2011, in fact) so we have to weigh the needs and wants of the users with legitimate security issues (as well as the needs and wants of the Cannibal dev team). The official CyanogenMod recovery (which this is mostly based on) does not (and will never) do on-device backups for this reason, so we also have to take that into consideration.
Click to expand...
Click to collapse
No official recoveries that ship on phones make on-device backups so that's nothing new.
But you're making a recovery for people who flash ROM's, Kernel's, and all types of different Mods. Most of which are downloaded straight to their phone so (in my opinion) you're making a recovery that does not do one of the main things someone who flashes custom firmware is looking for I mean who wants to go to their PC every time they want to try a different ROM, kernel, smooth scrolling mod, or even a themed lockscreen?
But again good luck, I just don't see this project going very far without on-device backups. If this project does pick up speed without on-device backups I'll be the first one to eat my words...
Best of luck to you and thanks for sharing.

bp328i said:
No official recoveries that ship on phones make on-device backups so that's nothing new.
But you're making a recovery for people who flash ROM's, Kernel's, and all types of different Mods. Most of which are downloaded straight to their phone so (in my opinion) you're making a recovery that does not do one of the main things someone who flashes custom firmware is looking for I mean who wants to go to their PC every time they want to try a different ROM, kernel, smooth scrolling mod, or even a themed lockscreen?
But again good luck, I just don't see this project going very far without on-device backups. If this project does pick up speed without on-device backups I'll be the first one to eat my words...
Best of luck to you and thanks for sharing.
Click to expand...
Click to collapse
After speaking with the other Cannibal devs, we've decided we are going to go ahead and provide an on-device backup solution but it needs to be noted that on-device backups present a serious security risk.

bp328i said:
No official recoveries that ship on phones make on-device backups so that's nothing new.
But you're making a recovery for people who flash ROM's, Kernel's, and all types of different Mods. Most of which are downloaded straight to their phone so (in my opinion) you're making a recovery that does not do one of the main things someone who flashes custom firmware is looking for I mean who wants to go to their PC every time they want to try a different ROM, kernel, smooth scrolling mod, or even a themed lockscreen?
But again good luck, I just don't see this project going very far without on-device backups. If this project does pick up speed without on-device backups I'll be the first one to eat my words...
Best of luck to you and thanks for sharing.
Click to expand...
Click to collapse
drewwalton19216801 said:
After speaking with the other Cannibal devs, we've decided we are going to go ahead and provide an on-device backup solution but it needs to be noted that on-device backups present a serious security risk.
Click to expand...
Click to collapse
Pretty much what Drew said... bp328i brings up the same issues that I did when I first noted that there was no backup solution when we started porting the themes over to this new recovery fork and we can all see how this is a concern. The project is afterall for the users though; I personally can't tell you how rarely I flash anything these days. The thing is IF you are using an on-device backup solution you're taking security into your own hands and you have to be prepared for compromises to occur. My best recommendation is to use 2-step verification if you aren't already (for everything that offers it) and move backups off the device as soon as possible so that you don't become one of those that's threatened by the hypothetical backup reader.

Your advice on the subject is greatly appreciated. You have brought an interesting POV to the subject of backup security.