Database Users

Just Rooted... Noob Question

Can I take off terminal emulator now?!
Also, which CPU control thing is recommend? I want to be able to set the CPU way down when the screen isn't on and maybe overclocked it to 1.2 when on.
Thanks guys

Don_Perrignon said:
Can I take off terminal emulator now?!
Also, which CPU control thing is recommend? I want to be able to set the CPU way down when the screen isn't on and maybe overclocked it to 1.2 when on.
Thanks guys
Click to expand...
Click to collapse
you can remove Terminal Emulator. IT is "Safe" to do that, but i wouldn't recommend it. IT's a lightweight program and has benefits out of the Ying-Yang. It basically acts a ADB interface from with on the device.
And to over clock the phone you'll need to flash a new Kernel, and get a program called SetCPU to manage the overclocking/underclocking.
Just make sure to do a nandroid backup before flashing anything.
And it'd be a good idea to install Recovery 3.0.0.6, and you might want to heavily consider flashing the Engineering HBoot

neidlinger said:
you can remove Terminal Emulator. IT is "Safe" to do that, but i wouldn't recommend it. IT's a lightweight program and has benefits out of the Ying-Yang. It basically acts a ADB interface from with on the device.
And to over clock the phone you'll need to flash a new Kernel, and get a program called SetCPU to manage the overclocking/underclocking.
Just make sure to do a nandroid backup before flashing anything.
And it'd be a good idea to install Recovery 3.0.0.6, and you might want to heavily consider flashing the Engineering HBoot
Click to expand...
Click to collapse
Sorry... More Noob questions...
Nandroid backup makes a copy of the way my phone is now, correct? So, if something happens, I can flash my current settings and get back to where I was?
Recovery 3.0.0.6 is just the stock recovery ROM?
And, I can flash the latest custom ROM without having to get the first version of it, right?

Don_Perrignon said:
Sorry... More Noob questions...
Nandroid backup makes a copy of the way my phone is now, correct? So, if something happens, I can flash my current settings and get back to where I was?
Recovery 3.0.0.6 is just the stock recovery ROM?
And, I can flash the latest custom ROM without having to get the first version of it, right?
Click to expand...
Click to collapse
-Yes
a Nanadroid back up is a snap shot of your OS in it's current state. So if you should have a problem you can revert back to a safe point and try again or wipe your hands and stay clear of what ever it might be.
-sort of
Recovery images are a section of the OS that handles ROM management, and flashing themes, fonts and stuff like that.
and you need a recovery image to flash a ROM, and depending on which style (2.3 v 2.2) ROM you use depends on which Recovery image you need. 3.0.0.6 will handle both.

Thank you very much.

Don_Perrignon said:
Thank you very much.
Click to expand...
Click to collapse
No problem, glad i could help.

nevermind.........

How easy is it for a good chip to get bricked?

If you have advice or an opinion I would appreciate it, thanks. I guess the phone I had earlier had a bad chip, ended up with a fail-PU. From reading= bad chip. not looking to get another one.

dirtyreturn said:
If you have advice or an opinion I would appreciate it, thanks. I guess the phone I had earlier had a bad chip, ended up with a fail-PU. From reading= bad chip. not looking to get another one.
Click to expand...
Click to collapse
The good chip is harder to brick, but still VERY possible.
When you root it just take your time.
-When you wipe the phone do it from the recovery image
-when you need to fix permissions do it from the recovery image
-flash the recovery image via ADB
-flash the OS via the recovery
-flash the g/apps via recovery (if needed)
just basically don't use a 3rd party app to do what you need to do in recovery and you should be okay.

Clockworkmod recovery, right? Or is that the third party app you metioned?

dirtyreturn said:
Clockworkmod recovery, right? Or is that the third party app you metioned?
Click to expand...
Click to collapse
There is nothing wrong with the Clockwork Recovery image. It's actually the one that i use. I know there is another on in the Dev section that alot of people are liking. I would just veer away from the App that you can download in the market. It seems like a lot of people have connections between that and their eMMC chips failing. I'm not saying it's koush's fault, it's so popular because the app is good. Just not on our devices.

So clockworkmod is fine? I appreciate you're help. You had said it causes some problems on this type of phone, what kind? Is another recovery `better `?

dirtyreturn said:
So clockworkmod is fine? I appreciate you're help. You had said it causes some problems on this type of phone, what kind? Is another recovery `better `?
Click to expand...
Click to collapse
i have no problem with the Clockwork Recovery Image.
i have a problem with the Clockwork ROM Manager. It seems as if that is linked to failing chips.

I'm still pretty new, could you explain a little further? How does software ruin a chip? Is it by what the program does?

dirtyreturn said:
I'm still pretty new, could you explain a little further? How does software ruin a chip? Is it by what the program does?
Click to expand...
Click to collapse
The program runs a series of scripts that tells the phone what to do. If those scripts don't mount firmware, software, hardware properly to each other items might not be written correctly.

hm. So the developer writes a multi device program? I've rooted by using the downgrade post than the gfree method. In you're first post you had the procedure step by step-if you have some time could you explain further?

dirtyreturn said:
hm. So the developer writes a multi device program? I've rooted by using the downgrade post than the gfree method. In you're first post you had the procedure step by step-if you have some time could you explain further?
Click to expand...
Click to collapse
The developer in part doesn't right different programs since the phones handle the scripts pretty much in the same fashion. The framework is pretty much the same. the recovery images are different. So those are written differently. But since our eMMC chip is buggy we need to make sure we mount them correctly. Thus just booting into recovery v. using the application.
Download your OS of choice
push the OS to your SDcard , or copy and paste
Verify the MD5SUM of the download
boot into recovery
do a nandroid backup
wipe your handset / factory restore
flash the OS
Flash the g/apps as needed
reboot system.

No ADB (shell) when in Recovery?

Does ADB not work when in recovery?
When my N7 is in recovery mode (CWM) my PC (Win7) doesn't see any attached USB devices and "adb shell" obviously tells me "no devices found".
My N7 is rooted, unlock bootloader, has CWM (non touch) installed and when in "regular", normal boot I can perfectly "shell in" via adb, just not in CWM recovery....
Does CWM not support that as of yet, or am I doing something wrong?

Not sure. Adb works fine for me in cwm
Sent from my Nexus 7

Why did you installed CWM into your tablet, instead of loading it ONLY when you need to? That is the proper approach.

bagofcrap24 said:
Not sure. Adb works fine for me in cwm
Click to expand...
Click to collapse
OK, so it might just be something I'm doing wrong.
TECK said:
Why did you installed CWM into your tablet, instead of loading it ONLY when you need to? That is the proper approach.
Click to expand...
Click to collapse
Counter question: Why not?
You don't have to decide what's the proper way to do things for me, I think I know what I'm doing - also I might need it (or at least it's supposed root adb shell access) everytime I go to recovery, so why keeping the need to have to "fastboot boot" it everytime instead of just booting into it?
Also - as said above - adb and fasboot both work fine, just not in CWM.
I might try another driver, maybe that'll help.

HellcatDroid said:
You don't have to decide what's the proper way to do things for me, I think I know what I'm doing.
Click to expand...
Click to collapse
The proper way is to tempload CWM, not install it. You want to be special and do it your way, feel free to... nobody is stopping you. Since you know what you are doing, then you should not have any issues.
HellcatDroid said:
I might try another driver, maybe that'll help.
Click to expand...
Click to collapse
What's wrong with using the default Google USB drivers? They work properly.

TECK said:
What's wrong with using the default Google USB drivers? They work properly.
Click to expand...
Click to collapse
See first post, not working in CWM for me right now.
Might not be the drivers, if you have any real help to give, feel free to share.

I would not use other drivers, except the Google USB ones provided on their developer site.
Based on my experience, you can have only headaches if you replace stock recovery with CWM. That's the main reason why I always temp load it, instead of physically install it. I know it is convenient to have it installed, but how often do we use it? Very rarely. The less I tweak on the phone, the safer it is. Are you running 6.0.1.0 on your tablet?
First, do you see the Android 1.0 driver marked as invalid in device manager?
If yes, then the fix is easy... Follow the procedure I posted in my signature to properly install the ADB drivers.
Do you have any "fancy" drivers installed, like Samsung, Unsigned from XDA, etc.? Get rid of all of them, if you do and make sure you ONLY deal with Google drivers.
If not, this is what I would do in this situation: I would install the Google factory image (straight from console, no crazy toolkits) and restore everything back to normal. Then, I would test the stock recovery and see if everything works as expected. After that, I would tempload CWM 6.0.1.0 and see if there are any issues. I know is a ****ty deal, especially if you have lots of customizations on your tablet. The goal is to see if you can run all proper commands while using the stock recovery. If you cannot, that's a different ball game.

It's been the drivers.
i installed the ones from the Android SDK and everything works now (had drivers d/l'ed from the Asus page so far).
TECK said:
Based on my experience, you can have only headaches if you replace stock recovery with CWM.
Click to expand...
Click to collapse
Based on my experience it doesn't really matter - unless you are going to use some special functionality CWM breaks (like the full device encryption on the S2 with GingerBread 2.3.x - and I got even that to work with an own build).
Bottom line: every one does things differently and something perfect for one might be suboptimal for the other.
TECK said:
That's the main reason why I always temp load it, instead of physically install it.
Click to expand...
Click to collapse
I love the option to be able to temp-boot a kernel, my Droids so far (Samsung Galaxy S2 and S3) didn't support that.
Tempbooting a kernel is perfect for testing a new build as you don't have to reflash a working one if the one you tried doesn't work
Though, it'd be just more work for me to tempload CWM everytime I need it, but as said, that's just me.
TECK said:
I know it is convenient to have it installed, but how often do we use it? Very rarely.
Click to expand...
Click to collapse
Negatory, I use it alot.
Mostly for the rooted adb shell access though, yet that's rather often - and also quite often away from my home computer with everything loaded and temploading without the kernel image.... hmm, not really
TECK said:
The less I tweak on the phone, the safer it is.
Click to expand...
Click to collapse
Safety is overrated (disclaimer: that's a joke )
For me it's more like "the more I mod the hell out of it, the more fun it is - and if everything breaks, I restore/reflash factory and start over".
CWM won't stay for too long anyways, eventually I'll smack my own kernel and own recovery-kernel onto it.
Time to check out those sources
TECK said:
Are you running 6.0.1.0 on your tablet?
Click to expand...
Click to collapse
Yeah.
TECK said:
Do you have any "fancy" drivers installed, like Samsung, Unsigned from XDA, etc.? Get rid of all of them, if you do and make sure you ONLY deal with Google drivers.
Click to expand...
Click to collapse
Nothing "fancy" but Samsung drivers, yes.
And getting rid of them is totally out of the question as my S2 and S3 won't work anymore, then.
But everything works now, got the Google SDK drivers for the N7 and the Sammy drivers for the rest and everything looks good
TECK said:
(straight from console, no crazy toolkits)
Click to expand...
Click to collapse
Yeah, that's exately how I do it, adb and fastboot all "by hand".
TECK said:
I know is a ****ty deal, especially if you have lots of customizations on your tablet.
Click to expand...
Click to collapse
All hail to the backups, just restore my data after the wipe :good:
Anyways, thanks for the help, after all it was that link to the tut that got me to install the Google SDK drivers

Help with wipe-rom-kernal for first time, If have donate button I can donate cpl$

Im not rich or I would have got a newer version tablet by now, but if anyone who helps has a donate button I have no issue donating a couple dollars to the person who helps me get this done, Thanks. Or just a couple dollar PP gift. better than nothing I guess.
I just want to be sure I dont mess anything up here. I have a nexus 7 wifi model.
I used NRT to unlock and root and all seems fine. Am I correct in this:
I use nandroid backup to backup first
Put ROM file on device (where do I put it?)
Wipe (is this done via nexus root toolkit or is ok do do in the custom recovery?)
Then what, boot into recovery and find the ROM and install it via recovery install button?
Then do I do the same with a kernal? Where do I put it?
Then done?
I know there are guides around but for a complete newbie I need to be sure cause I dont always see a complete fully explained step by step. Just like when I was stock not getting SU to work after rooting via nrt, I did read to flash SuperSU.zip, but had no idea how, then when I found the file and thought maybe install from recovery meant same as flash, I didnt know the message about messing the device up was normal so I was afraid at first.
THANKS to any replies,
Been unsure for days now trying to make sure my ducks are in a row before i commit to a ROM/Kernal. I want to CPU control for both under and overclocking etc. Mainly overclock just a little. I must say I love root already, got stuff to work I couldn't before

1. Create nandroid- there's a free app called something like nandroid on line - very simple to use
1a. I'd also recommend backing up with titanium backup app. It means you can keep your app data (e.g. game progress) when switching between ROMs, unlike a nandroid which is just a backup of your device as a restorable image
2. Put ROM file on device - ROM will be a .zip file, out it wherever you want, as long as you remember where it is
3. Put kernel anywhere on device - easiest to find a kernel with .zip format (recommend M-kernel)
4. Wipe - from custom recovery
5. Hit install in your custom recovery, I always flash kernel and then ROM, but I don't think it really matters
Install from recovery and flash are the same thing.
I'd recommend only flashing ROM or kernel and sticking with that set up for a few days, then flashing the other desired element. That way, if anything goes wrong then it's easier to pinpoint.
Good luck!!
Sent from my HTC Desire C using xda app-developers app

THANKS! Don't see a donate button, did you want anything?

No, of course not! God luck!
Sent from my Nexus 7 using xda app-developers app

butler0607 said:
5. Hit install in your custom recovery, I always flash kernel and then ROM, but I don't think it really matters
Click to expand...
Click to collapse
Actually that completely matters. Flashing a kernel before rom is worthless because the rom contains a kernel that will replace whatever you have just flashed.
If you want to run a custom kernel on a rom it is recommended to boot into the rom first before flashing the kernel.

Pirateghost said:
Actually that completely matters. Flashing a kernel before rom is worthless because the rom contains a kernel that will replace whatever you have just flashed.
If you want to run a custom kernel on a rom it is recommended to boot into the rom first before flashing the kernel.
Click to expand...
Click to collapse
If I just want root access and overclock should i just flash kernal and forget a rom?
can i revert back to stock kernal if need to? ask cause need to find a kernal that has V4L enabled for a usb camera app i use currently to use an inspection camera via usb on my tablet. I guess i need to read what various roms and kernals add. do i need to do both. Hard to know what to pick out of them, lol.
Thanks for advice.

Anyone know of a list to show ROMs with V4L enabled? None seem to mention it?

I have read and see different suggestions around on various sites. What all do I wipe? I have read cache, dalvik cache, plus other stuff. What all must I wipe before flashing a rom or kernel? I did a nandroid backup already.
PirateGhost, Ill donate a couple dollars if you help, thanks.
Thanks.

When going from one rom to a different one all you need to do in custom recovery is select factory reset.
This wipes out your currently installed apps, their settings, but doesn't touch your 'sdcard'
Wiping dalvik is pointless as it's automatically handled in the rom process, and cache is wiped in factory reset.
When switching kernels follow the instructions provided by the dev. If no instructions are provided, it's safe to assume you just flash without wiping anything.

When doing this, I'd recommend titanium backup too. When you do a factory reset, all apps are lost, but some data is kept (not sure on the details). Basically Titanium allows you to restore all your apps with data when you change ROMs.
Sent from my Nexus 7 using xda app-developers app

Pirateghost said:
When going from one rom to a different one all you need to do in custom recovery is select factory reset.
This wipes out your currently installed apps, their settings, but doesn't touch your 'sdcard'
Wiping dalvik is pointless as it's automatically handled in the rom process, and cache is wiped in factory reset.
When switching kernels follow the instructions provided by the dev. If no instructions are provided, it's safe to assume you just flash without wiping anything.
Click to expand...
Click to collapse
Thanks! Ill donate a couple dollars later today when I get back from the doctor.
I have not put any customs ROM(s) on yet, so is it the same still? All I have done so far is unlock/root with custom recovery and nandroid backup....
butler0607 said:
When doing this, I'd recommend titanium backup too.
Click to expand...
Click to collapse
Yeah I backed up the one app I needed to via TB, I just recently unlocked and rooted so lost most app data anyway and have only added one back so far. Thanks.

butler0607 said:
When doing this, I'd recommend titanium backup too. When you do a factory reset, all apps are lost, but some data is kept (not sure on the details). Basically Titanium allows you to restore all your apps with data when you change ROMs.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
No data is kept except what's on the sdcard. Mostly only game saves and some basic stuff. Apps databases are wiped during factory reset.

Pirateghost said:
No data is kept except what's on the sdcard. Mostly only game saves and some basic stuff. Apps databases are wiped during factory reset.
Click to expand...
Click to collapse
Thanks, Ill donate a couple bucks. had bad day yesterday so wasn't on much.

Is it normal for the donate link to be missing the regular PayPal security info on the browser?

eBandit078 said:
Is it normal for the donate link to be missing the regular PayPal security info on the browser?
Click to expand...
Click to collapse
I have no idea what this means.

Pirateghost said:
I have no idea what this means.
Click to expand...
Click to collapse
Maybe Ill just do it and change my password when finished. Thanks. Sorry not replied yet have been in a lot of pain Only a couple dollars but better than nothing I guess. Thanks for your help. Ill be back online tonight to do it.

eBandit078 said:
Maybe Ill just do it and change my password when finished. Thanks. Sorry not replied yet have been in a lot of pain Only a couple dollars but better than nothing I guess. Thanks for your help. Ill be back online tonight to do it.
Click to expand...
Click to collapse
Not forgot about you, had family issues, holiday etc, well did forget but I'll look into why it does that and figure it out. Sorry for delay.

i will do some thing with my relative new mia1

I want to mod my phone but I haven't modded this model, I want to do this thing:
Unlock via fastboot
Install twrp
Lineage os
Magisk (root)
No gapps ..an alternative like nogapps or fakegapps
Anything is possible?

KafkaG said:
I want to mod my phone but I haven't modded this model, I want to do this thing:
Unlock via fastboot
Install twrp
Lineage os
Magisk (root)
No gapps ..an alternative like nogapps or fakegapps
Anything is possible?
Click to expand...
Click to collapse
Yeah it's easily possible
Just look around XDA for info or even YouTube

berezker said:
Yeah it's easily possible
Just look around XDA for info or even YouTube
Click to expand...
Click to collapse
You think via modding like this the phone it's ok or there are some problem in the normally use? you think without Google it's ok this phone or there are some problems? lineage is ok? and the final question: you think with the support of the XDA community the phone will be updated again after the closure of the official support?
thanks

KafkaG said:
You think via modding like this the phone it's ok or there are some problem in the normally use? you think without Google it's ok this phone or there are some problems? lineage is ok? and the final question: you think with the support of the XDA community the phone will be updated again after the closure of the official support?
thanks
Click to expand...
Click to collapse
1. I've had this phone for more than 2 months now and I've been modding my phone ever since, no problems whatsoever.
2. I didn't try removing Google stuff from the phone but some people have done it. Search around for that as i don't know exactly.
3. Lineage and most other roms are perfectly fine. I personally Recommend AEX but Lineage is also very good.
4. I personally think the phone will still be supported even after official support is over since there's pretty much a new rom every other week so I don't think you need to worry about support for the next 2-3 years

berezker said:
1. I've had this phone for more than 2 months now and I've been modding my phone ever since, no problems whatsoever.
2. I didn't try removing Google stuff from the phone but some people have done it. Search around for that as i don't know exactly.
3. Lineage and most other roms are perfectly fine. I personally Recommend AEX but Lineage is also very good.
4. I personally think the phone will still be supported even after official support is over since there's pretty much a new rom every other week so I don't think you need to worry about support for the next 2-3 years
Click to expand...
Click to collapse
ok, thanks a lot mate

berezker said:
1. I've had this phone for more than 2 months now and I've been modding my phone ever since, no problems whatsoever.
2. I didn't try removing Google stuff from the phone but some people have done it. Search around for that as i don't know exactly.
3. Lineage and most other roms are perfectly fine. I personally Recommend AEX but Lineage is also very good.
4. I personally think the phone will still be supported even after official support is over since there's pretty much a new rom every other week so I don't think you need to worry about support for the next 2-3 years
Click to expand...
Click to collapse
ok, thanks a lot mate

for install the lineage os I must do some partition formatting in the twrp recovery?

KafkaG said:
for install the lineage os I must do some partition formatting in the twrp recovery?
Click to expand...
Click to collapse
Wipe system, data and cache
Install rom and twrp installer
Reboot again to recovery
Flash gapps and magisk
Reboot to system

berezker said:
Wipe system, data and cache
Install rom and twrp installer
Reboot again to recovery
Flash gapps and magisk
Reboot to system
Click to expand...
Click to collapse
sorry but, what do you mean with "twrp install"? the normal twrp recovery or another thing?

KafkaG said:
sorry but, what do you mean with "twrp install"? the normal twrp recovery or another thing?
Click to expand...
Click to collapse
I meant this
https://forum.xda-developers.com/mi-a1/development/recovery-twrp-3-1-1-0-touch-recovery-t3688472
It's called "Twrp installer"
You need to flash it immediately after you flash a rom because once you flash any rom, twrp will be overwritten by stock recovery so you have to flash twrp installer