Related
I just purchased nexus one . I have been trying to root the phone and put Cyanogen recovery image 1.4 & Cyanogen 5.0.5 test3 rom.
So far i unlocked the bootloader (Says unlocked at top in fastboot now).get the little unlocked padlock every time the phone starts up
When attempting to flash the recovery image now i get: an error that says "Failed....(not allowed)". and if i retry the same command right after, it says its starting to flash but freezes. Same thing happens when trying the rom file too.
Attempting to unlock the bootloader again i get the error "... FAILED (unknown status code)".
What is going on and how can i get this to work? any help would be greatly appreciated.
CM Recovery is for the G1, not the N1.
Get this one: http://forum.xda-developers.com/showthread.php?t=611829
Instruction to install on first post.
mrandroid said:
CM Recovery is for the G1, not the N1.
Get this one: http://forum.xda-developers.com/showthread.php?t=611829
Instruction to install on first post.
Click to expand...
Click to collapse
yeah but what is the difference between the regular recovery and the cyanogen recovery? i first rooted with the standard recovery, then afterwards saw the cyanogen and flashed that recovery to my phone. things seem to still work the same, and previous nand backups can be restored via the cyanogen version. but what exactly is the difference?
i did notice that the cyanogen nand backup adds an extra file in there called "cache". what data is contained on that vs the regular recovery WITHOUT that cache file?
RogerPodacter said:
yeah but what is the difference between the regular recovery and the cyanogen recovery? i first rooted with the standard recovery, then afterwards saw the cyanogen and flashed that recovery to my phone. things seem to still work the same, and previous nand backups can be restored via the cyanogen version. but what exactly is the difference?
i did notice that the cyanogen nand backup adds an extra file in there called "cache". what data is contained on that vs the regular recovery WITHOUT that cache file?
Click to expand...
Click to collapse
Again, the CM Recovery is not made for the N1, switch to the other one. Better options, newer and fixed scripts for the N1 and froyo.
mrandroid said:
Again, the CM Recovery is not made for the N1, switch to the other one. Better options, newer and fixed scripts for the N1 and froyo.
Click to expand...
Click to collapse
Ok I'll go back to the standard recovery. But again, that link you posted specifically says nexus only only and has the cyanogen recovery for download right below the regular recovery. And the cyanogen one has more menu options than the regular recovery. So I'm confused what the difference is.
These recovery images go back to the very first custom one made for the G1/Dream - JF Recovery - by JesusFreke. Cyanogen started from that, made it better, and released it as CM Recovery. AmonRA took the CM recovery, and made it even better. The major difference is that the Amon recovery has more options, layered menus for easier navigation, and it uses new scripts for Nandroid and a2sd backup. For the moment, the only recovery images that work with Nexus One are Amon and the Clockwork recovery made by Koush. I've never used that so I don't know what's different there.
The Cache backup is essentially unnecessary because, as the name implies, it's just the volatile cache held on the partition while the phone is operational. Every time you turn the phone on and make changes, the cache changes. So you don't really need a backup for it because it can be remade when the phone turns on after restoring a backup.
Edit: That Cyanogen recovery link under the regular one is just a themed version of the AmonRa Recovery. The two are exactly the same, but the Cyan themed one has a different background and colour scheme. Just look at the two screenshots.
OK i understand, the cyanogen version is just the same thing as regular but has the cm "look" and feel to it.
Alternative CyanogenMOD version with Cyan colors and CM Logo
Click to expand...
Click to collapse
RogerPodacter said:
OK i understand, the cyanogen version is just the same thing as regular but has the cm "look" and feel to it.
Click to expand...
Click to collapse
Exactly right.
I am almost too chicken to post because reading all the developer threads I feel like such a noob.
I recently rooted my Nexus One, thanks to a developer that created a painless one button rooting app. The problem is after downloading and installing many apps that require superuser access I am finding out that I am limited in what I can do without unlocking the bootloader.
I want to find a theme that replaces the standard white bar "which will cause screen burn" with a black bar.
I backed up all my apps, "Titanium Back Up"
I backed up my ROM??? "Maybe not" using a program call Rom Backup. "I have not figure out how to to nandroid backup "not sure the right name"
I googled found many procedures on unlocking the bootloader but I can not get it work.
Download ADK
Found a place that has Fastboot download it
I even found out I need to copy file from ADK folder to the Fastboot folder
Held down the power button trackball got the correct screen "even though my old eyes have a hard time reading the little character"
connected my phone
Ran the batch file
It returns saying wait for device.
The device is connected, in the right mode, my device manage says the is an Android device connected.......
But no matter what I do I can not get the screen warning me that to unlock my bootloader I void my warranty.
I found here some theme labled that hey work Nexus One 2.2 and I want to try them but Metamprgh will not load new themes on a radio that has a locked bootloader.
I am not worried about losing my warranty I live in Canada if I ever need warranty work it be a hassle anyway.
I thought unlock the bootloader.
When the phone powers up login my Google Account, reload Titanium Back up to restore my my phone.
Back up the Rom once more using Rom Backup if I want to recover my stock Rom
Run Metamorph and play with the themes
But I can not unlock the bootloader ....... "waiting for device"
How can I unlock the Bootloader, I there a more current method?
What can I be doing wrong I see a device in my Device Manager?
Will my method for restoring my phone work, never done a full phone wipe?
FYI this forum is scary there should but a developer and a Noob section.
You don't need to unlock your bootloader. My bootloader is locked and I'm rooted. It seems like you're missing superuser.apk. You need that too allow all of the programs like ROM manager and Titanium Backup root permissions. I'm not sure how the one click app works but I know that it probably should have installed the superuser application to allow those apps root access. Check and see if its in your application draw. You might want to try "one click rooting again" because it seems like it didn't work.
Side note: Titanium Backup does not back up your ROM. It just backs up apps and their data stored on your phone so it can be restored when you flash a new ROM. The way you back up your ROM is through the android custom recovery using the nandroid feature.
Thanks Magma,
Yes Superuser is installed.
A program wants superuser access I can grant it.
Metamorph does do several checks and it needs superuser access.
It is my understanding superuser access gives apps access to system hardware but if you want to use Metamorph to change the standard Android Shell that is going to modify your ROM and you will need and unlocked bootloader.
Here is what happens when I run Metamorph it finds the zipped files on my SD card, I select a file, it exacts the package, I say update al .... PLEASE WAIT for 20 or 30 minutes, it may then tell me to reboot but nothing happens my theme is still stock Android 2.2
This is where you can find out about and download the One Click Root App, it is in this section themes and apps.
It roots you device but leaves the bootloader alone
I know titanium backup just restores all your applications and data. The way I understand it if I ever need to do a master reset, I login Google, download Titanimum back up use it to restore every thing else. Yes which every ROM I was running will not be touched.
I am pretty sure I need to unlock the Bootloader.
But to unlock my Bootloader I just as I said get please wait I tried everything.
Alright man, you need the Android sdk for your OS so go to the android site and get the SDK, then install drivers for phone, and you NEED a custom recovery to do a NANDROID of the ROM, from what i understand your like me
have everything stock but with root privileges! and i from what i know as of now, unlockBoot loader gives you the option to do fastboot, if you want to continue messing around with stuff i highly suggest you flash custom recovery like Amon-Ra or even clockwork(from market) then go to Nandroid back up, then flash a custom rom like Enomther's Rom that is nice and stock clean stable, but still able to do themes
ilostchild said:
Alright man, you need the Android sdk for your OS so go to the android site and get the SDK, then install drivers for phone, and you NEED a custom recovery to do a NANDROID of the ROM, from what i understand your like me
have everything stock but with root privileges! and i from what i know as of now, unlockBoot loader gives you the option to do fastboot, if you want to continue messing around with stuff i highly suggest you flash custom recovery like Amon-Ra or even clockwork(from market) then go to Nandroid back up, then flash a custom rom like Enomther's Rom that is nice and stock clean stable, but still able to do themes
Click to expand...
Click to collapse
Wow lot to digest. I do have and install Android SDK the instructions in the tutorial I googled said I needed it, The Fastboot command needed files in the ADK directory.
The thing is since my command window did not see a device,
With your Nexus One in bootloader mode and connected to your computer via USB cable, go back to the command prompt and type “fastboot-windows oem unlock”.
Would even be able to flash anything?
At the end of the day I am very happy with Android 2.2 and I do not think I want custom roms at least for now. All I want is to get Metamorph to work so I can change how it looks.
try to type fastboot oem unlock
You do not need to unlock.
You used the one click root.
Now download Rom Manager and flash the Clockwork Recovery.
There, now you suddenly have a custom recovery, can flash custom roms, and flash custom themes on top of the roms.
And you still have a locked bootloader.
You don't even need to manually go into the recovery to flash your roms and themes, Rom Manager will do it for you. Chose the rom or update.zip file for the theme and it will automatically reboot and flash it for you.
From clockwork you can also make a backup of your phone. Through Rom Manager choose to back it up, and it will restart and do a nandroid backup for you automatically.
try to type fastboot oem unlock (Done but it just responds wait for device)
Now download Rom Manager Done and it seemed to back up my OEM Rom no problem and flash the Clockwork Recovery. Question is this over writing existing Nexus One ROM because as I said since really have nothing against OEM ROM I would like to keep it?
There, now you suddenly have a custom recovery, can flash custom roms, and flash custom themes on top of the roms. At this point my phone would be powered up with the Clockwork Recovery ROM? I want to use Metamorph to flash themes on top of the Nexus One ROM
And you still have a locked bootloader.Well if Clock Recovery does the job and at the end of the day I get OEM 2.2 ROM which I can theme with Metamorph I am ok never unlocking the Bootloader.
You don't even need to manually go into the recovery to flash your roms and themes, Rom Manager will do it for you. Chose the rom or update.zip file for the theme and it will automatically reboot and flash it for you.
Yes Understood I have the program
From clockwork you can also make a backup of your phone. Through Rom Manager choose to back it up, and it will restart and do a nandroid backup for you automatically. But as the questions above do I really what to keep the Clockwork Recovery ROM. I do not know what the Clockwork recovery ROM does but I do just want to theme my Nexus One OEM ROM.
So let me see if I got the steps straight.
Head to the download section find the Clockwork recovery ROM.
Copy it to my SD Card.
Open ROM Manager and install it.
Reboot my Nexus One, the ROM manager forces the Reboot and I will be running my phone with Special ROM, old version of Android?
Then do I load my back my OEM ROM and modify it with Metamorph?
or is what loading the Clockwork ROM actually do is it is not a full ROM when I load it with ROM Manager what it does is add to my existing OEM ROM. This process will then let me modify the ROM with themes. When I reboot after loading the Clockwork ROM I will find the phone looks and behaves the same as always "running Android 2.2" but the Clockwork ROM will add files and when I use Metamorph it will work......
............. Man I am such a noob, but i guess at one time we were all noobs.
You are still mixed up:
Clockwork is not a rom. It is just replaces the stock recovery.
To install the Clockwork Recovery you:
1. Download Rom Manager
2. Press the first item "Flash ClockworkMod Recovery"
Done, nothing has changed, except your recovery partition is now different, which allows the flashing of other stuff.
Anything you do from now on could wipe your curent install, so make sure things are backed up in case you want to go back.
Now from Rom Manager you can flash any other rom or update.zip
The biggest issue you might face is that I don't think you can theme the stock froyo rom. You will need a special de-odexed rom. So you would have to go to the development section and find a custom 'stock' rom. Then flash that one though Rom Manager.
Keep in mind, when you do all this, you will not get any OTA updates anymore either, unless you flash back to the real stock rom and the stock recovery. But most people don't care, since the custom roms will be updated eventually to the latest, if not before.
Clarkster said:
You are still mixed up:
Clockwork is not a rom. It is just replaces the stock recovery.
To install the Clockwork Recovery you:
1. Download Rom Manager
2. Press the first item "Flash ClockworkMod Recovery"
Done, nothing has changed, except your recovery partition is now different, which allows the flashing of other stuff.
Anything you do from now on could wipe your curent install, so make sure things are backed up in case you want to go back.
Now from Rom Manager you can flash any other rom or update.zip
The biggest issue you might face is that I don't think you can theme the stock froyo rom. You will need a special de-odexed rom. So you would have to go to the development section and find a custom 'stock' rom. Then flash that one though Rom Manager.
Keep in mind, when you do all this, you will not get any OTA updates anymore either, unless you flash back to the real stock rom and the stock recovery. But most people don't care, since the custom roms will be updated eventually to the latest, if not before.
Click to expand...
Click to collapse
I need to learn how to use the search better. If I had read this first I assume I could have updated the radio without unlocking the bootloader. arg.
Yes I did not understand, ROM Manager first entry is Clockwork Recovery.
You said I can install themes using ROM manager?
I click on "Install ROM from SD Card", I had a pretty scary moment not know what I am doing I tried it the phone reboot to an "exclamation mark and Android". I pulled the battery and it booted.
This make me wonder if yor find an unstable theme or ROM how can you use ROM manager to restore a backup?
Could the reason Metamorph did not work is having "Clockwork Recovery"?
AstroDigital said:
Yes I did not understand, ROM Manager first entry is Clockwork Recovery.
You said I can install themes using ROM manager?
I click on "Install ROM from SD Card", I had a pretty scary moment not know what I am doing I tried it the phone reboot to an "exclamation mark and Android". I pulled the battery and it booted.
This make me wonder if yor find an unstable theme or ROM how can you use ROM manager to restore a backup?
Could the reason Metamorph did not work is having "Clockwork Recovery"?
Click to expand...
Click to collapse
Sorry, but I am going to have to recommend you do a lot more reading in the development section, the wiki, and all the sticky posts. Don't try anything until you understand how linux works, partitions, bootloaders, how Android roms work, even how a metamorph works.
Spend a few weeks or a month reading about everything, through the whole threads before trying to jump in. That's how I learned everything.
You seem intelligent enough to do everything, but what you lack is an actual understanding of what those things are, so you just need to spend a lot more time on it.
When you do fully understand everything, it will be a breeze and you will enjoy it a lot more. You will be less likely to completely screw your phone, and if you do you will know exactly how to recover.
I need to learn how to use the search better. If I had read this first I assume I could have updated the radio without unlocking the bootloader. arg.
You saying yes it is true I need to unlock bootloader?
Sorry, but I am going to have to recommend you do a lot more reading in the development section, the wiki, and all the sticky posts. Don't try anything until you understand how linux works, partitions, bootloaders, how Android roms work, even how a metamorph works.
You maybe right, maybe I should give up for now. Learn to do a backup and restore using nandroid. Just not sure how much time I am willing to invest just to gain the able to put themes on my phone.
AstroDigital said:
I need to learn how to use the search better. If I had read this first I assume I could have updated the radio without unlocking the bootloader. arg.
You saying yes it is true I need to unlock bootloader?
Click to expand...
Click to collapse
Yeah, you shouldn't do anything yet, read up on stuff for fun until you know what is going on.
For instance, in what I quoted above, you understood the exact opposite of what he was saying.
He was upset that he didn't find out about this way to root before he unlocked. He didn't have to unlock and is now disappointed he did.
OP. What ROM are you currently running? Stock FRF91 or something else?
To my understanding you need a De-Odexed ROM to apply themes that modify the framework.
I've installed Amon Ra on my Nexus One as part of the process to get cyanogen running on it. I did the fastboot oem unlock + flash amon ra + manual update zip process.
Part of the reason was that for some reason I could never boot into clockwork recovery (yes I followed the wiki to the letter), and could only access the standard recovery (which doesn't allow custom roms, says the signature is invalid), the one in blue font. So I flashed amon ra instead and that worked fine.
Can I now flash back to clockwork, and even better, just do it via rom manager? Is there any risk or downside?
This is because I'm reading that amon ra doesn't have a wipe option, and that its better to wipe when you upgrade roms (or is that another fallacy or am I mis interpreting things)
cheers
1. If you didn't find and delete recovery-item-boot.p and install-recovery.sh, they will restore stock recovery when boot, regardless of what custom recovery you flashed.
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
Click to expand...
Click to collapse
2. You can change your recovery via ROM Manager, or manually. By the way, Amon RA Recovery has wipe option, of course. Where did you read that from?
LFact said:
1. If you didn't find and delete recovery-item-boot.p and install-recovery.sh, they will restore stock recovery when boot, regardless of what custom recovery you flashed.
2. You can change your recovery via ROM Manager, or manually. By the way, Amon RA Recovery has wipe option, of course. Where did you read that from?
Click to expand...
Click to collapse
1.) I'm pretty sure I'm booting into amon_ra, it has a nandroid backup option.
My attempt (fail) to install clockwork was exactly the same as how I successfully installed amon: via fastboot flash recovery /path/to/recovery-RA-nexus-v2.1.1-CM.img after unlocking the bootloader. I didn't manually find and delete those files you specified (wouldn't even know how TBH), just followed the Cyanogen wiki.
2.) Cool good to know. I suppose then there's no point in changing really. I was just reading posts and saw it referenced several times. Maybe they were out of date or early on in the piece.
Out of curiosity, is it worth wiping if you're just upgrading between the same version e.g. cyanogen 7.03 to future 7.04?
I much prefer Amon 2.2.1 It is 2.2.1 which is the latest version, not 2.1.1
Stay away from CW 3.+
Amon has a Data/Factory reset wipe for installing new roms, I wipe 5X with it. And, a Dalvik Cache and Cache options. Do those 5X also
If doing nightlies, just wipe the caches
Here is a link to a System Wipe zip you can flash from recovery. That is probably what they were taliking about. CW has that option and Amon will on the next version, I think.
http://forum.xda-developers.com/showthread.php?t=723844&page=1767
Ken
PS:
Otherwise, like mentioned you will default back to CW even if you flashed 2.2.1 thru Rom Manager on reboot.
Or, you can flash Amon thru fastboot and remove the two scripts mentioned above by LFact
Thanks mate I'll just keep using Amon
So you're saying to wipe I have to flash that zip, there's no way of just wiping it from the menu options before flashing the relevant ROM?
But in any event since I'm on CM7 I'll only be doing minor version bumps for the foreseeable future lol
I"m confused about the reboot issue: I can reboot into Amon at any stage. I haven't deleted those scripts. But you guys are telling me that unless I delete those scripts if I reboot I'll go back to stock recovery?
Sorry wrong thread.
Sent from my PC36100 using Tapatalk
@wintermute000
Yes, flash the system wipe zip from recovery like any zip. Only a few seconds. Hopefully , it will be in next Amon version.
Never an issue with Amon--
Get Quick System from market and use it to boot into recovery--exc app
Then you don't need Rom Mgr or CW--better that way
If you install Amon thru Fastboot or Terminal, it will not be erased on reboots--you still need to delete the two scripts mentioned before any rebooting
See post three on this link--DR has a flash able zip to do it--nandroid always first on this stuff
http://www.nexusoneforum.net/forum/...330-custom-recovery-wont-stick.html#post99962
wintermute000 said:
Thanks mate I'll just keep using Amon
I"m confused about the reboot issue: I can reboot into Amon at any stage. I haven't deleted those scripts. But you guys are telling me that unless I delete those scripts if I reboot I'll go back to stock recovery?
Click to expand...
Click to collapse
If you type
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
Click to expand...
Click to collapse
in terminal and it shows error message such as 'no file or directory', it means they were already removed. (I think ROM manager automatically remove them when flashing Clockwork recovery. When I changed to RA recovery, I found out those 2 files were gone)
If you're still curious about changing recovery, you can. I accomplished this yesterday by using Amon to flash a ROM with root access, then I downloaded CwM from the market. Installed the recovery using CwM. It's a simple process as long as you have root. As for going back to Amon, I haven't tried that.
Those files are gone (I didn't do rm, I just did basic ls in those directories). So I guess somehow during my Amon flashing it deleted it. Good to know.
Thanks for your patience all, I think I'll just stick to Amon then if I can just as easily wipe using a zip file if I need to. From what I've read I won't need to wipe anyway if I'm upgrading minor versions (i.e. CM7.03 to say 7.04 or nightly) and that's all I'm interested in doing. Hopefully by the time CM8 comes around I'll have taken the plunge on something dual core!!!
The whole reason I started investigating root/flash etc. was to give my N1 more legs until the price/performance point for the dual core phones gets to a better state, and its more than done that, I'm kicking myself for not doing it earlier. I guess once you're familiar with it then its a piece of cake, but I was reluctant for ages as I didn't want to screw up my PHONE (as opposed to say a tablet).
You don't need to remove those files since after you loaded Amon_RA, you installed CyanogenMod. Those files are used in Stock Android to replace whatever recovery you may have with the stock recovery on every boot.
I would still download the flashable zip that rugmankc linked to for formatting /system. Like I said in the CM forums, it normally isn't necessary when upgrading from minor versions, but sometimes it is the only thing you can do to fix a phone. I figure it is better to download it and never use it, then need it and having a hard time finding it.
+1 bass
@wintermute000,
I still wipe Dalvik Cache and Cache between nightlies. Seemed like the time or two I didn't do it, I had an issue.
The deal on using System Wipe if flashing new rom or if a lot of versions in between is:
When you flash a new rom it wipes system, but backs up some files from old rom first and reinstalls them as part of the new rom. After while things get cluttered, so a system wipe prolongs more serious issues. It has reduced the amount of times I need to do a complete wipe and/or sd card redos.
All Props to Temasek on this stuff
Ken
Hello,
I have recently purchased a Galaxy S Advance phone, and I am quite new to the android os.
I have read already many guides and forums about the whole process of rooting / flashing etc, so I have some knowledge of the terminology.
I already have a rooted phone with GB on it (yes, I know JB is about to come out officially ) and I wanted to change some of the UI elements.
I installed the rom manager app by koush, but yet to use it because I saw that in the past that the phone wasn't supported.
My question is: Does ROM Manager support this phone? Can I go ahead and flash CWM on it from the rom manager app, and then use it to flash other roms?
If not, which is the best solution to backup and replace roms? ODIN?
Thanks,
Одг: Is Galaxy S advance supported with Rom Manager? If Not, other ways to change ROM
YMatrix said:
Hello,
I have recently purchased a Galaxy S Advance phone, and I am quite new to the android os.
I have read already many guides and forums about the whole process of rooting / flashing etc, so I have some knowledge of the terminology.
I already have a rooted phone with GB on it (yes, I know JB is about to come out officially ) and I wanted to change some of the UI elements.
I installed the rom manager app by koush, but yet to use it because I saw that in the past that the phone wasn't supported.
My question is: Does ROM Manager support this phone? Can I go ahead and flash CWM on it from the rom manager app, and then use it to flash other roms?
If not, which is the best solution to backup and replace roms? ODIN?
Thanks,
Click to expand...
Click to collapse
Other way to change roms is custom recovery. On GB TWRP, on JB CWM.
Sent from Galaxy S Advance
Thanks fro your quick reply!
And what about ROM Manager? Does it work in this device?
YMatrix said:
Thanks fro your quick reply!
And what about ROM Manager? Does it work in this device?
Click to expand...
Click to collapse
I think it is not working. It is not supported. Way we install custom ROMs: download ROM zip, transfer to SD, then go to recovery and install it from there.
I checked TWRP supported devices list (tried to link it but forum wont allow new users to link ) and I don't see the galaxy advance S on their list either.
Is there a special mod version for this device?
And another question, if installed, will this wipe the current phone data or just the recovery loader? Since I want to backup my current ROM (+ contacts, settings etc.) before doing anything sketchy...
YMatrix said:
I checked TWRP supported devices list (tried to link it but forum wont allow new users to link ) and I don't see the galaxy advance S on their list either.
Is there a special mod version for this device?
And another question, if installed, will this wipe the current phone data or just the recovery loader? Since I want to backup my current ROM (+ contacts, settings etc.) before doing anything sketchy...
Click to expand...
Click to collapse
You have GB? Look here.
On I9070 recovery is on the same partition as kernel. So it can't be installed separatly. It is ported. You need to install this kernel, or CoCore. If you install with Odin - you will increase binary counter. For installation with ADB shell, or Terminal emulator (app from market) you need root - and it will not increase bc.
So I am guessing I will use the dd command line way since it doesn't increase the binary counter (why would we want to do that ).
Is it possible to backup the current ROM before flashing it with the TWRP modified ROM?
And another thing, since I will be using other ROMs, how can i add the TWRP recovery loader to them (you said that the recovery is on the same partition as the kernel, making me believe that each ROM I load will need to have TWRP on it)?
YMatrix said:
So I am guessing I will use the dd command line way since it doesn't increase the binary counter (why would we want to do that ).
Is it possible to backup the current ROM before flashing it with the TWRP modified ROM?
And another thing, since I will be using other ROMs, how can i add the TWRP recovery loader to them (you said that the recovery is on the same partition as the kernel, making me believe that each ROM I load will need to have TWRP on it)?
Click to expand...
Click to collapse
No, only JetMOD have embendend kernel too. And it have TWRP.
Hm, another thing. You better use non binary counter increaing root method. But it need you to flash whole firmware with Odin. And maybe you loose data. But if you do not do factory reset - it will be ok.
Sorry, I didn't understand your last post.
YMatrix said:
Sorry, I didn't understand your last post.
Click to expand...
Click to collapse
If you want to get TWRP with dd command you need to root your phone first.
There are 2 root methods. One that increase binary counter, and one that do not..
With one that do not increase - you need to flash whole firmware with Odin. And by doing that you might need to do factory reset. That will cause your data and app delete. You can try to boot, maybe it will be ok.
Oh, I already said I have a rooted device, so this wont be an issue.
What I asked was:
1) If I can backup my current ROM before installing the TWRP ROM you linked (in case something goes wrong).
2) When I install other modified ROMs, will they override the TWRP I installed, or just change the kernel system leaving TWRP in the recovery?
Одг: Is Galaxy S advance supported with Rom Manager? If Not, other ways to change ROM
YMatrix said:
Oh, I already said I have a rooted device, so this wont be an issue.
What I asked was:
1) If I can backup my current ROM before installing the TWRP ROM you linked (in case something goes wrong).
2) When I install other modified ROMs, will they override the TWRP I installed, or just change the kernel system leaving TWRP in the recovery?
Click to expand...
Click to collapse
Didn't pay attention.
You have backup option in TWRP, and you can restore it.
Custom roms do not have connection with kernel, just JetMod who do have kernel with TWRP too.
P.S. lol you confuse me. TWRP is kernel related, nothing to do with ROM.
When you want stock kernel back, just flash your firmware from sammobile.com.
So you need to change kernel to get TWRP. And with TWRP you do backup of system.
Sent from Galaxy S Advance
Bos manForu
Hmmmm, now I am a little confused.
Since I don't want to touch the kernel (yet), all I want to do is change the ROM (as in UI changes etc...).
I wanted to backup my current ROM and then load other ROMS.
I started off with ROM Manager because it seemed to answer what I wanted to do, but as you said ROM Manager doesn't support this phone and we went from there to TWRP.
Since I now get that TWRP is kernel related only and not ROM management, what would you advise right now for:
1) Backing up the current ROM
2) Loading other ROMs to the device?
YMatrix said:
Hmmmm, now I am a little confused.
Since I don't want to touch the kernel (yet), all I want to do is change the ROM (as in UI changes etc...).
I wanted to backup my current ROM and then load other ROMS.
I started off with ROM Manager because it seemed to answer what I wanted to do, but as you said ROM Manager doesn't support this phone and we went from there to TWRP.
Since I now get that TWRP is kernel related only and not ROM management, what would you advise right now for:
1) Backing up the current ROM
2) Loading other ROMs to the device?
Click to expand...
Click to collapse
You can do that only with TWRP.
And did you read ROM manager description?
* Flash your recovery to the latest and greatest ClockworkMod recovery.
Click to expand...
Click to collapse
For ROM manager you need custom recovery. And for I9070 that is embended in kernel. Full stop.
And it is connected to CWM, not to TWRP. We do not have CWM for Android 2.3.6. ported.
P.S. So to close this:
- You can't do any backup, installation of ROMs without custom recovery (in our case TWRP) on our phone.
- Custom recovery couldn't be installed separatly - it is embended inside kernel file - and has nothing to do with ROM.
It is clear now?
I think I got you now
1) CWM doesn't work on my phone because the recovery is attached to the kernel.
2) In order for me to backup my ROM I need to install the kernel with TWRP embedded (the one you linked me).
3) I also can't backup my current kernel without TWRP so in order for me to have TWRP I will be doing #2 without any backup? I am guessing this is the part where bricking has a chance of occurrence?
YMatrix said:
I think I got you now
1) CWM doesn't work on my phone because the recovery is attached to the kernel.
2) In order for me to backup my ROM I need to install the kernel with TWRP embedded (the one you linked me).
3) I also can't backup my current kernel without TWRP so in order for me to have TWRP I will be doing #2 without any backup? I am guessing this is the part where bricking has a chance of occurrence?
Click to expand...
Click to collapse
CWM = TWRP
Both are custom recoveryes. Not the same, but same purpose.
1) Our phone have same partition for kernel and recovery. So we can't install it separatly
2) You can backup kernel, but you will need Terminal emulator, and similiar command like instalation of other kernel
Code:
$ su
# dd if=/dev/block/mmcblk0p15 of=/sdcard/boot.bin
# reboot
This will backup your stock kernel on your sdcard. You can install it later this way (ofcourse if boot.bin file is on your sd)
Code:
$ su
# dd if=/sdcard/boot.bin of=/dev/block/mmcblk0p15
# reboot
You always can flash your stock kernel, Download mode do not have anything to do with kernel and recovery partition.
If this is little hard for you, just install custom kernel with TWRP. Or do not do anything. :laugh:
P.S. Trust me, you can't hard brick device with installing kernel. I am tester, and I flashed at least 10 non booting kernels, and 50+ booting ones.
I do trust you, just trying to get an understanding of how the things work on these devices.
So I now understand the backing up and flashing commands (I would like to know how you knew the mmcblk0p15 was the kernel partition for this phone), so where does the "Download mode" come in handy if u can flash directly from a terminal window?
If for some reason the flash wasn't successful, can you enter download mode and restore the backup you created?
YMatrix said:
I do trust you, just trying to get an understanding of how the things work on these devices.
So I now understand the backing up and flashing commands (I would like to know how you knew the mmcblk0p15 was the kernel partition for this phone), so where does the "Download mode" come in handy if u can flash directly from a terminal window?
If for some reason the flash wasn't successful, can you enter download mode and restore the backup you created?
Click to expand...
Click to collapse
Most likely you will have to flash whole firmware if something goes wrong. I told you what I know.
And if you can go in TWRP recovery, it can restore krenel with other things you backed up. And you can flash new kernel in TWRP too.
Somewhere is written what partition is for what. I do not know that. And developers told us what partition is for kernel and recovery.
I do not think that that thing with restoring downlaod mode will work. Newer tried or heard of it.
I tried to explain you, but maybe I was little confusing. :angel: My english is not great, and I didn't provide 1, 2, 3... steps explanation. Like I throw everything to you. :laugh::laugh::laugh:
:laugh: More or less I understand you :laugh:
So to sum up:
1) Create a backup of the current kernel
2) Flash Stock Kernel + TWRP
if all goes well....
3) Create full phone phone backup from TWRP
4) flash custom ROMs (or kernels) with TWRP
Hows that?
YMatrix said:
:laugh: More or less I understand you :laugh:
So to sum up:
1) Create a backup of the current kernel
2) Flash Stock Kernel + TWRP
if all goes well....
3) Create full phone phone backup from TWRP
4) flash custom ROMs (or kernels) with TWRP
Hows that?
Click to expand...
Click to collapse
That is ok.
And you backup old kernel that you can easy go back to stock one. Without flashing whole firmware, when you want stock. Like you want to go to service for warranty or something like that...
being that the m8 dev edition phones r getting lollipop update AS I TYPE THIS, I find myself prepping for when we get the update.. I've modified many system files, so I've got the stock odex Rom downloaded and was about to download stock recovery when I realized my laptop is toast and don't have access to Another cpu for quite awhile . I've flashed twrp over the stock recovery with Flashify with no problems, but wondering if flashing stock recovery back over twrp with flashify is any different or if anyone else has done so, and if there's any problems? (yes I know it's always recommended to use fastboot, but I can't, no pc) ... I've used flashify many times, just not putting stock recovery back... Any feedback is much appreciated..
bdizzle1686 said:
being that the m8 dev edition phones r getting lollipop update AS I TYPE THIS, I find myself prepping for when we get the update.. I've modified many system files, so I've got the stock odex Rom downloaded and was about to download stock recovery when I realized my laptop is toast and don't have access to Another cpu for quite awhile . I've flashed twrp over the stock recovery with Flashify with no problems, but wondering if flashing stock recovery back over twrp with flashify is any different or if anyone else has done so, and if there's any problems? (yes I know it's always recommended to use fastboot, but I can't, no pc) ... I've used flashify many times, just not putting stock recovery back... Any feedback is much appreciated..
Click to expand...
Click to collapse
I don't know if it will work but you can give it a try.
You can use alray's DevEd Rom Reset just select stock recovery
majmoz said:
I don't know if it will work but you can give it a try.
You can use alray's DevEd Rom Reset just select stock recovery
Click to expand...
Click to collapse
Can't use it, I'm on Verizon. Unless there's a stock Rom reset for VZW.. Just wrote the question here because it's a wider audience than the vzw forum, and generally speaking, if it'll work on 1 it should work on the other. Just looking for confirmation to c if anybody's done it before.
I figured that being that when I used flashify 2 flash twrp and it worked n wrote to the correct partition, it SHOULD work the other way around. Just never done it with a stock htc recovery.