• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [Boost Mobile] [ROM] n00b (B10 based) VIII.II FULL Install 1/23/2013

This phone is fairly new, from the Philippians? I did find this for you though. Not a lot, but something.
CloudFone Excite 320g - mobile9

click this to know about my android...here CloudFone Excite

There is rooting method of my android is download a binary using apps poot.apk and ministro.apk... :) the only thing i want to install is cwm so i can backup my stock rom...i dont know on how to open the bootlooder of this...
 
Upvote 0
probably the gps configuration. Some roms don't have that issue because the gps config is different, and when I was on this one, I found an app on the Play Store that fixes the configuration to North America and it sped it up drastically, but not as drastically as the roms that already had it implemented. My rom (HaloBean) has the gps fix, so the gps locks on pretty fast. I'm not sure about other roms that may have the fix.

Hope this helps, and welcome to AndroidForums! :D


NINJAEDIT: Found the app...
https://play.google.com/store/apps/details?id=org.fastergps&hl=en
 
  • Like
Reactions: 706male
Upvote 0
Can someone port this rom to the htc evo design i loved this rom and still run it on my warp i would love to use this rom on the design ill zip my root system if you need it to build off of and theres an oc kernal available for our phones but the dev and forums for my device are pretty much dead i dont see too many people posting anymore i hope someone can help us put
 
Upvote 0
I hope I'm in the right place for this problem.

First off, I am impressed with this forum and the folks that run it. What I've done so far........back up...rooted, CWM, and NoobVIII.II...test and then MrBobo's Personal Bloatware on a ZTE Warp.

The messaging app worked fine in test........after "bloatware" I have to force close when I try to read a message. I am not familiar with all the terminology yet so forgive me if I am not explaining it correctly. I love the ROM and with a few exceptions.......like the Ovuview app....hehe... its perfect for me the way it sits. I have followed the instructions twice and still have same results in the end. Leaving for out of state run tomorrow for a week but will be checking as I can. Thanks so much for what you do!!
 
Upvote 0
I hope I'm in the right place for this problem.

First off, I am impressed with this forum and the folks that run it. What I've done so far........back up...rooted, CWM, and NoobVIII.II...test and then MrBobo's Personal Bloatware on a ZTE Warp.

The messaging app worked fine in test........after "bloatware" I have to force close when I try to read a message. I am not familiar with all the terminology yet so forgive me if I am not explaining it correctly. I love the ROM and with a few exceptions.......like the Ovuview app....hehe... its perfect for me the way it sits. I have followed the instructions twice and still have same results in the end. Leaving for out of state run tomorrow for a week but will be checking as I can. Thanks so much for what you do!!

Your problem is not so easy to isolate... Software bugs (anomalies) happen all the time. I'm not sure how you've flashed the ROM. Did you wipe everything? including formatting the Micro SD card? (of course before you format the card, make sure you back up your personal stuff first (nandroid backup, music, pics, etc.)

I would recommend not flashing the Bloatware then. You can manually add any App from the Bloatware Zip file that you like. And hopefully, anything weird happening may go away. Do them one at a time through the File Explorer. Just click on the app and select install. If you haven't done it already, it should prompt you to change your settings to install from "unknown" source.
 
  • Like
Reactions: OlderGuy
Upvote 0
Thank you Lilbit and xman95 for the quick response. Only thing on the SD was ROM and the bloatware, wipe/format, ROM only with personal contacts added this time around. I didn't know I could add from bloatware zip individual apps by folder/file. I sure got lots more reading to do. :) Will play that next to find which file is the problem. Also discovered one or more of those drained the battery pretty quick.......anyway thanks and I'll take the advice.
 
Upvote 0
I would also go with what xman95 has suggested. Check those apk's in the bloatware zip one by one.
Almost has to be the problem.

bloatware zip is about 10 months old so many of the apps are several versions back, not sure why that would cause an issue like this though, I would do a dalvik and cache wipe after rebooting to recovery before I took any drastic measures.

Also, had to LOL at the comment about ovuvue, I left a couple odd ones in there just to be goofy, feel free to delete the ones you don't want for sure!
 
  • Like
Reactions: OlderGuy and LilBit
Upvote 0
OK, after reading several parts of this thread, I'm ready to take the plunge... well, almost. Being a true root n00b, I want to know more about the 2 apps that seem to be essential to the process: Titanium Backup & nandroid. Both say they require root. Heh... how can I do a Titanium backup before rooting my phone-- actually, how do I do a pre-rooting backup? Is another backup app needed to start with? Would My Backup work? If so, can TB retrieve the data?

About nandroid... how is it used in the rooting process & what does it do? Play Store lists several nandroid apps. Which is the best?

:p
 
Upvote 0
OK, after reading several parts of this thread, I'm ready to take the plunge... well, almost. Being a true root n00b, I want to know more about the 2 apps that seem to be essential to the process: Titanium Backup & nandroid. Both say they require root. Heh... how can I do a Titanium backup before rooting my phone-- actually, how do I do a pre-rooting backup? Is another backup app needed to start with? Would My Backup work? If so, can TB retrieve the data?

About nandroid... how is it used in the rooting process & what does it do? Play Store lists several nandroid apps. Which is the best?

:p

Well I'll try my best to keep it simple, being as I to was once a root n00b too.
Titanium backup to be of any good, you will need to buy it. It works free, but the best and most beneficial part of TB (short for titanium backup) is the fact you can do mass installs and backups without any nags, meaning nothing is needed, you just tell it backup selected apps, you choose in a list, hit the little checkmark thing at the top, and sit back and let it do it's thing.
The free one makes you hit ok before and/or after each app you are backing up, so the money is very well spent if you drop the rughly $6 on the app. It was $10 or $12 when I bought it but I don't regret it one bit.

Secondly a nandroid backup is just that, a huge big backup, of your os. Think of it this way, you have a windows install, and you to make a backup of your desktop, files and folders, how things are set, and have an exact mirrior image of what you have now as a backup.....a nandroid is just that. It makes an exact mirror image backup of your settings, apps, system stuff etc.. then when you restore it it's as if you never left or wiped your data at all, and I mean everything, such as placement of widgets, on said screens and so on, it's a "mirror" image backup, so everything is back where you riginally placed it.
DO keep in kind though a few things, firstly a nandroid backup most always and will be bigger in size, and the naming scheme cannot have any spaces in it, ie: MY backup, it has to be MY_backup or MYbackup (no spaces).
Also with a nandroid backup you have to use what's called a recovery, or kernel recovery. There are different ones out there, and different flavors as well of those, such as agat, twrp (a gui interface kinda), cwm (clockwork mod) to name a few, and those have different variants of themselves also, so it HAS to be restored with the "same" recovery you made it with. If you use say EL29, you can't use say EL26 to resore it, it has to be EL29. (you will get that as you go along and will understand what I mean later)

Example: if you use agats to make a nandroid backup on monday, then install a new rom but this time you use EL29, then say a few days later you want to go back to the older nandroid backup, you can't use EL29 to restore it, you have to use agats because that is what you backed it up with, so you'll have to install agats again to restore the nandroid.

On an easier note though we have titanium backup, which doesn't require any specifics such as a version of a recovery and so on. You simply just backup apps+data and your done, and can install TB on another rom, then restore your apps again. TB does not keep the screens setup and such though, so it's a matter of just installing apps, and setting the screens back up. I do it in a matter of 5-8 mins, from recovery+install of rom+tb+setup.

I also would recommend highly about backing up system apps and restoring them because there are so many different layouts of how people make roms and such, so putting system apps in different spots can really muck things up. I would recommend doing apps+data only, that will keep yours settings and stuff like saves in games.
If your really that dead set on backing up system apps also, I would then suggest putting them in a per folder setup.....so if you back up say a Touchwiz rom and it's system apps and settings, then make a folder called TW or Touchwiz, and place those files in that folder. Same goes for Cm version, cm9, cm10, and so on, don't mix and match with system apps and data, you will most always ru into issues, ESPECIALLY if you mix TW with CM stuff, boy howdy can that be a HUGE dilema and mess!!!
I say this from "PERSONAL experience :)

It really depends on what your specific liking is.

I'd suggest trying one at a time and playing with it. It may take a week or even a month to figure out how to do each one, but you will end up learning and benefiting from it in the long run. So say try the harder one, which would be a nandroid backup, using a recovery of your choice. Make a backup, delete it, make another one, delete it, until you get the hang of it and are comfortable with it. Making those and deleting those won't mess your system up at all.

As for rooting, I don't have this phone anymore....I have a Epic 4g touch, but these days it is really hard to brick a phone now.....it's fairly easy to unbrick a phone if it is bricked, and you always have forums.

I have rooted like 3 different phones, the Prevail, the warp and this Epic 4g touch.
 
  • Like
Reactions: aimzzz
Upvote 0
Well I'll try my best to keep it simple, being as I to was once a root n00b too.
I would give you a big kiss if not for my turkey breath...

In your opinion, which nandroid app is best? I wasn't completely clear... with nandroid, is an image the only choice, or are there options to backup specific items such as apps + data?

If I don't care about backing up the system files, is TB enough, or would I still need nandroid?

I'm not expecting worse-case scenario, but I had to go back to the pre-root settings, would I prepare by just backing up SD card & if needed, do the basic factory reset thing?

Edit:
I installed TB but it won't start unless I root... so here goes...

More info on nandroid would be appreciated, but maybe I just have to try after the root attempt
 
Upvote 0
I would give you a big kiss if not for my turkey breath...

In your opinion, which nandroid app is best? I wasn't completely clear... with nandroid, is an image the only choice, or are there options to backup specific items such as apps + data?

If I don't care about backing up the system files, is TB enough, or would I still need nandroid?

I'm not expecting worse-case scenario, but I had to go back to the pre-root settings, would I prepare by just backing up SD card & if needed, do the basic factory reset thing?

Edit:
I installed TB but it won't start unless I root... so here goes...

More info on nandroid would be appreciated, but maybe I just have to try after the root attempt

Well a nandroid is "normally" done with a recovery, not an app.
It's built into almost every recovery I can think of, and it can be a handy tool if used correctly, namely the having to flash with the exact recovery is just a pain for me personally.
In the recovery part it's under like backup or backup/recovery or something.
Pretty simple really, just go to that section, and use what's on the list, like backup, click that and then toggle down to where it says backup, backup, then reboot.
You will have to rename it once you get booted back up if you want it to have a different name though.

As far as I'm concerned TB is the best way, just doing apps+data......and yes TB need root :)

Go on youtube and try searching for "Titanium Backup tutorial" or somthing like that and you should find a few videos explaining what things can be done with TB.....it's pretty extensive as to what it can do, so it's MY preferred choice of backup.
 
  • Like
Reactions: aimzzz
Upvote 0
MrBobo is perhaps the best rom dev around, very prompt on relies and fixing issues in his roms, so stick with this rom, it's the best one out there in my opinion.
Just wish he was in the epic 4g touch arena, we could use some good roms and rom devs over there.

Maybe best to find out what his new phone is & buy that one ;)
 
Upvote 0
something awful happened... I selected the ROM file on my SD card. It started running, but stopped w/ msg that the correct signature wasn't present & aborted. I was going to try again. Restarted phone holding down power button & volume bar. A white square came up that says FTM. I can't turn phone off now. What went wrong??? What is FTM? F#% the monkey???

Should I take battery out, or what?

EDIT:
Pheeew! Popped the battery & rebooted. Everything is back where it was before I did anything. Now to retry rooting. Maybe my first try didn't work bec my ROM DL got corrupted along the way or something. Will do new DL if it doesn't work this time.

What did I do to get FTM? And WTF is FTM?
 
Upvote 0
something awful happened... I selected the ROM file on my SD card. It started running, but stopped w/ msg that the correct signature wasn't present & aborted. I was going to try again. Restarted phone holding down power button & volume bar. A white square came up that says FTM. I can't turn phone off now. What went wrong??? What is FTM? F#% the monkey???

Should I take battery out, or what?

EDIT:
Pheeew! Popped the battery & rebooted. Everything is back where it was before I did anything. Now to retry rooting. Maybe my first try didn't work bec my ROM DL got corrupted along the way or something. Will do new DL tomorrow if it doesn't work this time.

What did I do to get FTM? And WTF is FTM?

I asked the same thing a while ago!

FTM = File Transfer Mode
 
Upvote 0
I did a 2nd download of the ROM zip-- result is same as my first ROM file DL... when I ran the install, I got the following msg:

--Install /sdcard...
Finding update package...
Opening update package...
Verifying update package...
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted.

I did a 2nd DL when I got above msg from 1st file-- thought maybe 1st was corrupted. Here's how I did DLs... I DL'ed from this thread to my PC, transferring file to DropBox. Then I transferred it from DropBox to SD card.

Any suggestions? Is there some kind of permission I need to change? I did check the Unknown Sources box to allow installation of non-market apps. No change.
 
Upvote 0
Download straight to your desktop, then transfer straight to your SD card.

By the way, welcome to AndroidForums! :D

I messed up one of my recent rom updates by transferring a file through my cloud storage account, and renaming it while I was downloading to my Warp while in the management app, thus corrupting the download for EVERYBODY (its fixed now, thankfully). Also, you are on the ZTE Warp N860, right? otherwise installation will abort to protect your device from bricking.
 
  • Like
Reactions: MrBobo and aimzzz
Upvote 0
About your questions about Root and Nandroid, they're two different things.

First, you have root. It gives you administrative rights to the Linux filesystem, which is Android (Android is Linux-based, and thus is Open-Source). Root is merely the term used for the permission acquired by the device, and this is achieved through placing an "SU" (for SuperUser) binary in the system by making use of security flaws in the system. That is where you see those apps called SuperUser or SuperSU in the Play Store and such. The apps do not root your phone, but make use of the binary by acting as a manager to control what apps are given root permissions and which are not. For example, in Titanium Backup, if you were rooted then the first time you open the app you would see a prompt from your superuser app asking if you want to allow or deny the app from having access to the installed SU binary file. If granted, you can make use of the app and back up your apps and such. If denied, the app is prevented from using the binary and is denied permission to access your phone's system.

Next, you have NANDroid. This is done through use of a custom recovery (like ClockWorkMod or TWRP [TeamWin Recovery Project]), and will let anyone with root access make a complete system backup. It lets you create a backup of every piece of information on your phone, and it can be restored later whenever you want. You need to achieve root first before you can use a custom recovery, however. The apps you see that make Nandroid backups in the market... useless without root and a custom recovery. The apps make use of the custom recovery to manage the backups just like the superuser apps manage permission. Nothing more, nothing less :)
 
  • Like
Reactions: aimzzz
Upvote 0
Wikipedia said:
Android rooting is the process of allowing users of smartphones, tablets, and other devices running the Android mobile operating system to attain privileged control (known as "root access") within Android's subsystem.
Rooting is often performed with the goal of overcoming limitations that carriers and hardware manufacturers put on some devices, resulting in the ability to alter or replace system applications and settings, run specialized apps that require administrator-level permissions, or perform other operations that are otherwise inaccessible to a normal Android user. On Android, rooting can also facilitate the complete removal and replacement of the device's operating system, usually with a more recent release of its current operating system.
As Android derives from the Linux kernel, rooting an Android device is similar to accessing administrative permissions on Linux or any other Unix-like operating system such as FreeBSD or OS X.
Root access is sometimes compared to jailbreaking devices running the Apple iOS operating system. However, these are different concepts. In the tightly-controlled iOS world, technical restrictions prevent
installing or booting into a modified or entirely new operating system (a "locked bootloader" prevents this),
sideloading unsigned applications onto the device, and
user-installed apps from having root privileges (or from running outside a secure sandboxed environment).
Bypassing all these restrictions together constitute the expansive term "jailbreaking" of Apple devices. That is, jailbreaking entails overcoming several types of iOS security features simultaneously. By contrast, only a minority of Android devices lock their bootloaders
 
Upvote 0
Wow! Thanks for quick response!

Definitely Warp N860. I'm doing DL to desktop as we speak. When you said "transfer straight to your SD card", do you mean via Bluetooth or USB?

Thanks for the welcome :)
I've messed with my PCs a lot but never had the urge to do anything to the phone... until I stumbled into this forum. You guys have me itchy to get started.
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones