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.
Related
Hello. Please help me. my phone can not use the rom manage. I have used one once, but can not be used again. when I turn on the program, still connected 3g/wifi but nothing more happened at all. I have copied the program into the correct directory. My phone rooted.This phenomenon occurs after I Flast 2.1
What doesnt work? Does it not install? Why are you copying the app at all? Why not install from Market?
I installed the application from Market but I can not use the rom manage.
I don't know!
duongthanhcong said:
I installed the application from Market but I can not use the rom manage.
I don't know!
Click to expand...
Click to collapse
Rom Manager*
You have to be rooted to use it.
You can't expect people to help you if you don't tell them the problem.
So its installed, did you flash the clockworkmod? Should be the top most option.
dcontrol said:
You can't expect people to help you if you don't tell them the problem.
So its installed, did you flash the clockworkmod? Should be the top most option.
Click to expand...
Click to collapse
Also, did you download it from the market, or did you steal the pro version from online? I am asking because you said "I copied it to the right directory"
Maybe I understand his/her problem. Rooted, installed RM but cannot install Clockwork?
Few options here, search for the standalone update.zip with Clockwork and do it that way OR wait a few hours and try again.
The 1st choice I had to do once because RM wasn't liking my phone and the 2nd choice sometimes the server is down.
First, my phone t959 rom UVJI6 normal. Then my rom to version 2.2 T959UVJFD. I do not feel satisfied so I returned to the Odin 2.1.
My phone has a normal root and fix lag.
but then, I could not manage to use the rom again.
Sorry for my english level is limited. I'm from Vietnam
blizzard1017 said:
Maybe I understand his/her problem. Rooted, installed RM but cannot install Clockwork?
.
Click to expand...
Click to collapse
Yes. this is my problem. How do I do now?
Thanks!
If youre trying to flash another rom you need to disable the lagfix first.
Sent from my SGH-T959 using XDA App
My assumption is you have OCLF, try removing it then giving it a go.
Google a clockwork update zip that is pushable with ODIN, I found one the other day. I MAY have it still but I am not sure and I honestly have no clue where I found it, wasn't xda I am about 90% sure. It is not really a solid fix but will get you to where you have CWM. Rom Manager will not recognize you have it installed but when you go to enter recovery mode it will enter into CWM.
Did you by chance also flash a custom kernal? When I tested out a few I noticed my phone did the same thing, my knowledge currently doesn't expand far enough to know if they can even be related though. I am still learning a lot myself.
blizzard1017 said:
My assumption is you have OCLF, try removing it then giving it a go.
Google a clockwork update zip that is pushable with ODIN, I found one the other day. I MAY have it still but I am not sure and I honestly have no clue where I found it, wasn't xda I am about 90% sure. It is not really a solid fix but will get you to where you have CWM. Rom Manager will not recognize you have it installed but when you go to enter recovery mode it will enter into CWM.
Did you by chance also flash a custom kernal? When I tested out a few I noticed my phone did the same thing, my knowledge currently doesn't expand far enough to know if they can even be related though. I am still learning a lot myself.
Click to expand...
Click to collapse
(See attachment)
Master™ said:
(See attachment)
Click to expand...
Click to collapse
Always living up to your name...
I had mine fixed up through some trial and error hopefully this gets the OP in the right direction.
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.........
title = question
dongimin2 said:
title = question
Click to expand...
Click to collapse
Don't see why not, as they're not dependent on each other. One way to find out though
kjy2010 said:
Don't see why not, as they're not dependent on each other. One way to find out though
Click to expand...
Click to collapse
How do I not have my own thread in my sig and you do? :/ only one way to fix this. . . . .
REMOVE IT NOW OR I KILL YOU!!! lol jk
um if u delete the apk's and you do a system wipe, it bricks your device. still, could u boot into CWM even if the main OS (android) is bricked?
dongimin2 said:
um if u delete the apk's and you do a system wipe, it bricks your device. still, could u boot into CWM even if the main OS (android) is bricked?
Click to expand...
Click to collapse
Yes you can in fact, back up in cwm before you delete system stuff and you can respite your system from there.our if you didn't back up, you can still bit in to cwm and flash a clean rom
Isn't the only way to brick it by deleting the boot partition in recovery without an operational system partition installed? Or does cwm not have an option to self terminate? Ie "I cannot self terminate" ( Said in ahnold shwatzenhagga voice)
Sent from my Nexus One using Tapatalk
android01 said:
Isn't the only way to brick it by deleting the boot partition in recovery without an operational system partition installed? Or does cwm not have an option to self terminate? Ie "I cannot self terminate" ( Said in ahnold shwatzenhagga voice)
Sent from my Nexus One using Tapatalk
Click to expand...
Click to collapse
Nah.. that's just going to wipe your kernel and OS side boot image out. You'll still have CWM and the ability to install a new rom. In fact, the device will likely boot into recovery without a valid boot image though i wouldn't test it!
On the amon recovery app used on the evo 4g phones, you normally would wipe both system and boot before a new rom is installed.. CWM just doesn't get that in depth with wiping options as it should.
Check this out for some very good reference...
http://www.addictivetips.com/mobile...plained-boot-system-recovery-data-cache-misc/
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
Is there any way to install a ROM into recovory mode, similer to what the Ubuntu Touch Duel Boot installer does but with different ROMs
I have unlocked the bootloader and rooted my device, I have Windows and Ubuntu if adb tools are required and the device is quickly on hand to test
The OS has not been flashed (To my knowlage) and is using the stock ROM the device came with
Thank you in advance
Are you asking if you can install a ROM in recovery partition? If so I doubt it as it would be to small for an OS
Otherwise can you clarify a bit?
demkantor said:
Are you asking if you can install a ROM in recovery partition? If so I doubt it as it would be to small for an OS
Otherwise can you clarify a bit?
Click to expand...
Click to collapse
Yes, sorry if I'm being a bit dumb :silly: but that's the idea of it, like what the Ubuntu Touch Installer app can do but for something else (Like cyanogenmod just to try it) if that's possible
Never used Ubuntu touch installer so I'm not sure how it works, but I can't imagine any OS being able to fit inside the recovery partition, is it maybe that it allows for a dual boot option?
demkantor said:
Never used Ubuntu touch installer so I'm not sure how it works, but I can't imagine any OS being able to fit inside the recovery partition, is it maybe that it allows for a dual boot option?
Click to expand...
Click to collapse
Maybe, but I could access it though the recovery mode option, I might have just booted from recovery and stored the OS elsewhere (I really don't have knowlage of how stuff works or I would have made an account here ages ago)
Well there are some devices with dual boot options but I don't believe anyone has made this for the nexus 10 to date
A simple way of having this is to create a nandroid backup of a ROM on your device and whenever you want to change, boot to recovery, make backup of current ROM, wipe, restore backup of other ROM, reboot
May not he ideal but only takes a few minuets to do
demkantor said:
Well there are some devices with dual boot options but I don't believe anyone has made this for the nexus 10 to date
A simple way of having this is to create a nandroid backup of a ROM on your device and whenever you want to change, boot to recovery, make backup of current ROM, wipe, restore backup of other ROM, reboot
May not he ideal but only takes a few minuets to do
Click to expand...
Click to collapse
Ok thanks, I'll get a device that supports duel-booting when I can afford it (Nexus 5 here I come) Ubuntu Touch doesn't work too well for me
To the best of my knowledge there is one main developer out there who does this mod, maybe ask him if he is willing to support the nexus10
demkantor said:
To the best of my knowledge there is one main developer out there who does this mod, maybe ask him if he is willing to support the nexus10
Click to expand...
Click to collapse
If you give me a username or Email, I'll see what I can do
@KINGbabasula
is this a project you would be willing to take on? MULTI-ROM for Nexus10?
demkantor said:
@KINGbabasula
is this a project you would be willing to take on? MULTI-ROM for Nexus10?
Click to expand...
Click to collapse
Not now, maybe in some time, now I'm not able to it ,sorry
KINGbabasula said:
Not now, maybe in some time, now I'm not able to it ,sorry
Click to expand...
Click to collapse
Well it was worth a shot, thanks anyway for at least looking at this