So, I've read a lot about it, found a method I liked (used the visionary permroot from the Unlockr.com), and now I have successfully Permarooted and have S=Off on my MT4G.
Now what?
[Q. 1.]I know that seems dumb, but what is the FIRST thing I should do once I have root access? Should I set up the ADB through the Android SDK? Should I get CW3 to do a Nandroid backup? I know how to do those things, I just don't know which one I should do first.
[Q. 2.]Ultimately, I want to upgrade to custom ROM, preferably a Gingerbread port. Unfortunately, I've read that most of the ports have buggy wifi among other things, so here's another question, anyone know a good Stock mySense ROM with some extras like overclocking and such?
[Q. 3.] Although I'm very clear on what S=Off and Root access are, what they do, and why I want them, they steps beyond that are foggy. I'm not sure what the difference between a kernel and a ROM is or whether I need one or both to do what I want to do (see Q2). I also don't know/understand what flashing is/does. I'm not expecting anyone to explain all that in here (unless you want to), but could you point me to some resources where I can learn what those things are so I understand what the hell I'm doing?
corruptsmurf said:
So, I've read a lot about it, found a method I liked (used the visionary permroot from the Unlockr.com), and now I have successfully Permarooted and have S=Off on my MT4G.
Now what?
[Q. 1.]I know that seems dumb, but what is the FIRST thing I should do once I have root access? Should I set up the ADB through the Android SDK? Should I get CW3 to do a Nandroid backup? I know how to do those things, I just don't know which one I should do first.
[Q. 2.]Ultimately, I want to upgrade to custom ROM, preferably a Gingerbread port. Unfortunately, I've read that most of the ports have buggy wifi among other things, so here's another question, anyone know a good Stock mySense ROM with some extras like overclocking and such?
[Q. 3.] Although I'm very clear on what S=Off and Root access are, what they do, and why I want them, they steps beyond that are foggy. I'm not sure what the difference between a kernel and a ROM is or whether I need one or both to do what I want to do (see Q2). I also don't know/understand what flashing is/does. I'm not expecting anyone to explain all that in here (unless you want to), but could you point me to some resources where I can learn what those things are so I understand what the hell I'm doing?
Click to expand...
Click to collapse
1. I say flash a new recovery image (CWM 3.0.0.6) and make a full backup. I also copy my backups to my PC because it's happened to me before that the one on the sd card gets damaged and can't be restored from (aborts because of md5 checksum mismatch). I do recommend the android SDK and ADB because they can be quite handy. Also, while you're still on the stock kernel, you might consider doing the gfree stuff to unlock your SIM and get universal CID. You run it exactly the same way you did the root.sh in theunlockr.com method - easy as cake.
2. I don't know about any sense roms, so I'll let others suggest those. I honestly think you should drop Sense and go with CyanogenMod, but to each his own.
3. Try the XDA Wiki, link up at the top. I'll bet there's tons of stuff there that will make for great bedtime reading. Since you mentioned a few things specifically, I'll throw some stuff at you:
The ROM is all the system files that compose your phone's operating system. Flashing is the process of installing any sort of firmware image (a rom, a recovery image, etc). Basically, you're writing files to the system. As you probably know, this is usually done via CWM recovery. It can also be done through fastboot if you have the engineering bootloader and the android SDK.
The kernel is the central component of most operating systems. It is a bridge between applications and the actual data processing done at the hardware level. Every ROM has a kernel. When you flash a rom, the kernel files will be flashed with it. You can flash another kernel afterwards to replace the one already in the ROM, provided that it's compatible with the ROM.
jdkoren said:
1. I say flash a new recovery image (CWM 3.0.0.6) and make a full backup. I also copy my backups to my PC because it's happened to me before that the one on the sd card gets damaged and can't be restored from (aborts because of md5 checksum mismatch). I do recommend the android SDK and ADB because they can be quite handy. Also, while you're still on the stock kernel, you might consider doing the gfree stuff to unlock your SIM and get universal CID. You run it exactly the same way you did the root.sh in theunlockr.com method - easy as cake.
2. I don't know about any sense roms, so I'll let others suggest those. I honestly think you should drop Sense and go with CyanogenMod, but to each his own.
3. Try the XDA Wiki, link up at the top. I'll bet there's tons of stuff there that will make for great bedtime reading. Since you mentioned a few things specifically, I'll throw some stuff at you:
The ROM is all the system files that compose your phone's operating system. Flashing is the process of installing any sort of firmware image (a rom, a recovery image, etc). Basically, you're writing files to the system. As you probably know, this is usually done via CWM recovery. It can also be done through fastboot if you have the engineering bootloader and the android SDK.
The kernel is the central component of most operating systems. It is a bridge between applications and the actual data processing done at the hardware level. Every ROM has a kernel. When you flash a rom, the kernel files will be flashed with it. You can flash another kernel afterwards to replace the one already in the ROM, provided that it's compatible with the ROM.
Click to expand...
Click to collapse
Thanks for the info; yesterday I got my ADB working and today I'm going to use gfree to get radio S=Off, Super CID, and Unlocked SIM. After that, I'll probably do a backup, then get the engineering bootloader, then do another backup. After making copies of all pertinent files, I'll THINK about upgrading my kernel or ROM haha.
Related
Allright, Ive been pretty active in the xperia forums here and at htcpedia, but on sunday my xperia got stolen. I was hoping to get the Rhodium but Vodafone Insurance are up tight, in the end I bartered myself to a Vodafone Htc Magic. I like using Andoid and loved playing on the Hero, so I thought it was worth a shot.
I've been trailing through the internet looking for how tos and all sorts, but it seems with Android there are thousands of different ways of doing everything! I went on the Unlockr which gave me a really useful guide to flashing and rooting etc, but it seems that a lot of the stuff is now not in fashion and superceded by other methods.
I'd like to know how to root (heard there was a Cyanogen app on the market), backup (not sure why I should backup but there we go), partition (whether I use Linux swap or W/E, apparently something else is faster, and I don't have Ubuntu) and flash a new rom or update. Finally I'd like to know what sort of rom would be recommended, obviously Ive looked at Cyanogen and would like to flash it, as well as Donut.
Thanks in advance!
update: seen a similar thread but the link provided as a solution looks way too compliacted for me. There are some who ask you to download SDK and stuff, but the Unlockr didnt seem to say that. Also reading Cyanogen's thread, his barebones rom won't include google apps. How can we back these up? Argh I'm so lost.
anyone helpe me?
HazzBazz said:
anyone helpe me?
Click to expand...
Click to collapse
Hi HazzBazz.
I used this method to root my phone:
http://lifehacker.com/5339901/get-root-access-in-android-with-one-click
Follow this to install the custom cyanogenmod rom:
http://www.cyanogenmod.com/rom/cyanogenmod-4-1-999
If you have volume issues after doing the update then this is how to fix it:
http://forum.xda-developers.com/showthread.php?t=568891
Note: when you flash the recovery image of the stock operating system, it will revert back to the old one after a reboot. You will need to flash the recovery image again to put it back. Once cyanogen's rom is installed, the recovery image will stay the same.
Also: Make sure you perform an nandroid backup and make a copy of the nandroid folder that is on your sd onto your pc. Just in case.
I really reccomend you to download the SDK file, you will need one of it's tools sooner or later. Plus adb is a great way to do almost everything in your phone, i use it for almost all. check this link http://forum.xda-developers.com/showthread.php?t=532719
I have rooted my phone through the one-click-root method and haven't ahd a problem. I would recommend it as it is the easiest way to do it.
Then you will need to partition your sdcard - i use parted (a tool from the android SDK) as i find it the best method. follow this tutorial to guide you right through it
http://forum.xda-developers.com/showthread.php?t=534714 (it is made for a dream so it asks you to go to the console and type in the phone - just boot into recovery mode, plug in the sapphire to the computer and access it through adb (with command prompt) and then just follow the instructions.)
if you want to install hero roms (or almost any rom for that matter) you should also update your radio and spl to the latest version. check this thread for hero Q&A http://forum.xda-developers.com/showthread.php?t=534461 and this one http://forum.xda-developers.com/showthread.php?t=537365;
Above all you just have to do a bit of reading and experimentation with your phone. Read the forums here and on the dream board and it should get you up and running in a couple of days. just involves a bit o patience in the begining but hey, we all went through it. check also this links/tutorials
http://forum.xda-developers.com/showthread.php?t=513061
http://forum.xda-developers.com/showthread.php?t=529062&highlight=Hero
Good luck and have fun with your new phone - one of the best gadgets I ever bought in my life!
I have an unrooted hero I have had since launch day. I am now thinking about rooting my hero with use of the latest Sprint leak. my understanding is if you update to the leak of even the official builld whenever that may come out, it will close all current rooting holes available. I guess that doesn't mean in the future there won't be other possibilities. do these new build give the same sense of stability as the official roms because we can now use an official 2.1 kernal?
so from what I have been reading there appears to be only one Rom that is based on the current 2.1 leak and that is flipz Rom? I have a few questions or statements before I do anything to my phone. one, will this help get rid of the lag when typing? two, I need to make sure Bluetooth is still going to work as I have a home phone that I connect my cell to when I enter the door. if I decided to flash back to the official release, is that possible?
dbldown768 said:
I have an unrooted hero I have had since launch day. I am now thinking about rooting my hero with use of the latest Sprint leak. my understanding is if you update to the leak of even the official builld whenever that may come out, it will close all current rooting holes available. I guess that doesn't mean in the future there won't be other possibilities. do these new build give the same sense of stability as the official roms because we can now use an official 2.1 kernal?
Click to expand...
Click to collapse
As of right now; many people are cautious about testing the latest 2.1 leak; because of the concerns you expressed earlier -- having your phone unrooted by the 2.1 leak when you flash the new update. So, with that said; the current 2.1 ROM's are all pretty stable. This new leak, however probably is as well, but again... I don't know whose all tested it, for fear of loosing root access.
dbldown768 said:
so from what I have been reading there appears to be only one Rom that is based on the current 2.1 leak and that is flipz Rom?
Click to expand...
Click to collapse
No. Damageless ROM's are also based on the latest Sprint leaks. All ROM's you see should tell which ROM they are based off of. Almost all 2.1 ROM's are currently built from any of the Damageless ROM's -- just read the front page of the ROM you're looking into.
dbldown768 said:
I have a few questions or statements before I do anything to my phone. one, will this help get rid of the lag when typing? two, I need to make sure Bluetooth is still going to work as I have a home phone that I connect my cell to when I enter the door. if I decided to flash back to the official release, is that possible?
Click to expand...
Click to collapse
1. Possibly. The lag problem is relative to the person/device. Not everyone experiences this problem. However, turning off "Vibrate when typing" apparently helps with the lag issues. YMMV.
2. Please see first post I made.
Thanks for the quick reply. I'm investigating the best way of rooting my phone. I see there are a few ways listed on the wiki, but then i just ran across Fresh Kitchen (http://geekfor.me/new-release/fresh-kitchen-105)? This is suppose to root your phone for you? Is this a stable way of rooting or should i just use the command line mehods? Also, i have read that you should do a nandroid backup of your phone? Not sure if fresh is doing this for you? The other thing i should mention is that i just have a stock microSD card, so I dont plan on using app2sd, i dont think this is a problem correct?
I also see people load their roms using their microSD card and just putting some update.zip file on there. Is this the standard procedure once you root your phone and get a rom loaded?
Actually, Fresh 2.1, and 2.1.1 are the only ones as of right based off of the newest leak (signed with release keys rather then test), Damageless and Treve are currently working on improving DCUpdater, DConfig, and building a new ROM from the release-keys build.
As far as how to root, I recommend the command line method. While the auto-root methods are nice, actually doing it yourself will give you some experience with things you're gonna be using.
Yes, loading the update.zip to the root of the SDCard is the standard way to flash.
No, not using Apps2SD is not a problem, most people use it because they have a faster SDCard, which gives better performance when loading apps.
A Nandroid backup is something that you will do before you flash any update.zip (At least you're supposed to). It's basically an "Image" of your phone exactly how it was the point in time that you made it, so if you flash something and everything goes horribly wrong, you can restore said nandroid, and it will be like it never happened. (The exceptions are flashing a radio and screwing with the PRL/PRI, nandroid doesn't touch those.)
dbldown768 said:
Thanks for the quick reply. I'm investigating the best way of rooting my phone. I see there are a few ways listed on the wiki, but then i just ran across Fresh Kitchen (http://geekfor.me/new-release/fresh-kitchen-105)? This is suppose to root your phone for you? Is this a stable way of rooting or should i just use the command line mehods? Also, i have read that you should do a nandroid backup of your phone? Not sure if fresh is doing this for you? The other thing i should mention is that i just have a stock microSD card, so I dont plan on using app2sd, i dont think this is a problem correct?
Click to expand...
Click to collapse
Fresh's kitchen will allow you root your phone and yes it's stable. However, it's best you try doing it via ADB commands, as there will come a time when you'll want to create things for the community and wished you had prior experience using it. I recommend you trying to root via this tutorial HERE If you follow the directions, you shouldn't have any problems whatsoever.
Stock card is perfectly fine; you're able to use Apps2sd, but don't have to.
dbldown768 said:
I also see people load their roms using their microSD card and just putting some update.zip file on there. Is this the standard procedure once you root your phone and get a rom loaded?
Click to expand...
Click to collapse
To try out different ROM's -- the process is to download the file (which is a update.zip file in itself), but has been renamed to match the name of the ROM. All you have to do is; copy to your sd card, boot into recovery, flash ROM from the sd card, reboot.
abcdfv said:
Actually, Fresh 2.1, and 2.1.1 are the only ones as of right based off of the newest leak (signed with release keys rather then test), Damageless and Treve are currently working on improving DCUpdater, DConfig, and building a new ROM from the release-keys build.
Click to expand...
Click to collapse
There's your real answer. Thanks.
I'm having a hard time understanding why i would need the flash recover image in this tutorial (http://forum.xda-developers.com/showthread.php?t=583291)? I understand i would want to do a backup of the current phones state, but why would i flash anything before actually making this backup? Maybe i'm not understanding the process correctly, but i just want to get "su" ability and then do the nandroid backup? Is the nandroid backup an app i use?
Nandroid is built into the recovery image you're flashing. Before flashing the recovery image, there is no way for you to nandroid.
thanks! after watching the youtube video posting that mad more sense. So i know there is a chance of bricking your phone during all of this, where does that chance increase? Is it during the flashing of the customs roms, not so much the rooting process?
It is safe to say once the "official" 2.1 android comes out there will always be a custom rom based on it? meaning that if chosen by developers here there could be a build off the "official" 2.1 with the only difference is the rooted user is still allowed? I know that most dev are going to change the build in someway to "improve" on what the official build is done.
The only proven way to brick this phone is by flashing a GSM radio, or by having a failed RUU. I've never heard of anyone getting a "true" brick from rooting/flashing ROMs.
Yes, once the official build is released, all ROMs from then on are most likely going to be based of off it.
Ok, stupid question. I just followed the guide to rooting my phone, doing the nandroid backup and copying the backup to my pc. There are a lot of guide to root, but how to you actually flash the custom rom? I saw something about holding down the 'home' button when starting up? Does this bring you to the recovery image again? Do the roms have to be named something specifically?
Place the ROM in the root of your sdcard, and boot into recovery by holding Home+Power. From then select the "Flash update.zip" option and it will show all of the .zip files in the root of your sdcard. Just pick which one you want to flash.
great! thanks for all the help.
ok, so i decided to load damage's sprint leak that would still give me root access, well it doesnt boot. just goes to the "sprint now" screen and reboots over and over again? any ideas?
Did you wipe data and Dalvik?
Anytime you go from one ROM version to another (1.5 to 2.1, 2.1 to 1.6, 1.6 to 1.5, etc etc) you have to wipe, or if there's major changes between rom versions.
what do you wipe the data? i just picked the flash from zip file from sd card?
In recovery there's a catagory for wipe. Wipe data and Dalvik, then reflash and you'll be fine.
cool. thanks. trying that now.
so everything is working now. So i know one of the main benefits of having a rooted is phone is wifi teathering. Are apps like this in the market place or only on here?
There's Easytether and PDAnet. I haven't tried Easytether, since last I've heard it's x86 only, but PDAnet was a horrible experience. I just flashed an Eris based ROM, broke my PRI, and it enabled the built in USB tethering.
dbldown768 said:
so everything is working now. So i know one of the main benefits of having a rooted is phone is wifi teathering. Are apps like this in the market place or only on here?
Click to expand...
Click to collapse
go to market and download barcode scanner
open up barcode scanner and go here and then just point the camera at the qr code and it'll download to your phone.
remember to check 'unknown sources' > setting > applications
wifitether 1.6. works flawlessly on either fresh or damageless latest 2.1
All I want to do is upgrade to Froyo 2.2 and retain root so that I can use Wireless Tether. I've been reading several different EVO/Android forums but it seems like the more I read, the more confusing it gets. I'm still a noob, but here are my questions so I hope someone can lay it all out in the open for me.
Currently, my EVO has Unrevoked3 applied so I'm running on the "updated" 2.1, and I have root access and wireless tether is working as of now. Phone specs are:
Firmware version: 2.1-update1
Baseband version: 2.05.00.06.10
Build/Software number: 1.47.651.1
PRI version: 1.40_003
PRL version: 60665
1) What is the best/most reliable way for me to update to 2.2? Can I use Unrevoked Forever to do so? Or do I have to use some manual method? Toast's method? ROM Manager?
2) I read the steps for installing on the Unrevoked site, but I don't understand the terms it uses. It says to "flash from custom recovery". First of all, how do I access this custom recovery tool or whatever? Second, some ppl said they use a ROM Manager. Other sites say to "boot into recovery". Still, some instructions say boot into Clockwork....How do these method differ? Or are they the same? Which do I use???
3) One post says "After you unrevoke4, you can use your custom recovery image to flash a rooted 2.2 stock rom". I dont understand. A ROM is an image...so how can I use an image to flash another image?? makes no sense =\
4) Is "recovery" an app/tool that is already on the phone (or needs to be downloaded), and if so how do I access it? Or is it a ROM image?
5) After unrevoked is done, do I accept the OTA firmware update (i think it's the ugrade to Froyo update that keeps popping up)?
6) Which ROM needs to be installed? The zip that Unrevoked is going to install, or HTC Stock Froyo 3.26.651.6 [Rooted][Deodex'd], or both?
7) What is PRI and PRL and why are ppl so concerned about getting those updated? Will they get updated automatically once Frodo is installed?
8) Same deal with the Wimax and Radio updates. What do they do? Why do ppl want to retain them so badly, and if they are so important, why don't the updated ROMs or OTAs have them included?
9) What's the difference b/t a Nandroid backup and a Titanium backup? And which one should I do?
Please help! Thanks!
one does not simply walk into Mordor.
So I can identify with the OP. I don't know many of those same things, but I am slowly learning through reading these forums.........
However........that comment was quite amusing, also very accurate......... Ya that made my night
Sent from my PC36100 using XDA App
1) What is the best/most reliable way for me to update to 2.2? Can I use Unrevoked Forever to do so? Or do I have to use some manual method? Toast's method? ROM Manager?
Use Simpleroot to fully root. Then flash SteelH's 2.2 Stock Rooted ROM/
2) I read the steps for installing on the Unrevoked site, but I don't understand the terms it uses. It says to "flash from custom recovery". First of all, how do I access this custom recovery tool or whatever? Second, some ppl said they use a ROM Manager. Other sites say to "boot into recovery". Still, some instructions say boot into Clockwork....How do these method differ? Or are they the same? Which do I use???
Power + Volume Down while the phone is off boots your into the bootloader. You can then enter your custom recovery from there. Or you can use Rom Manager/Spare Parts to boot into recovery directly within your phone. Clockwork is a custom recovery; AmonRa is the other custom recovery. Use either one.
3) One post says "After you unrevoke4, you can use your custom recovery image to flash a rooted 2.2 stock rom". I dont understand. A ROM is an image...so how can I use an image to flash another image?? makes no sense =\
You need to install a custom recovery, ie AmonRa or Clockwork (an image) so you can flash a ROM (another image)
4) Is "recovery" an app/tool that is already on the phone (or needs to be downloaded), and if so how do I access it? Or is it a ROM image?
Recovery is already in your phone, but you need to flash a custom recovery after you root. Simpleroot will allow you to flash a custom recovery on the last step.
5) After unrevoked is done, do I accept the OTA firmware update (i think it's the ugrade to Froyo update that keeps popping up)?
Not relevant, when you are on 2.2, you won't be notified of OTA updates. After you root, NEVER accept any OTA. Wait for the updated rooted roms.
6) Which ROM needs to be installed? The zip that Unrevoked is going to install, or HTC Stock Froyo 3.26.651.6 [Rooted][Deodex'd], or both?
Don't use Unrevoked. Root using Simpleroot and flash your downloaded ROM afterwords.
7) What is PRI and PRL and why are ppl so concerned about getting those updated? Will they get updated automatically once Frodo is installed?
No one can really prove that an updated RPI/RPL affects your phone in positive ways. Your RPL will be updated. RPI will be 1.34 after Simpleroot, this forum just figured out how to get 1.40 RPI today (go read the dev forum)
8) Same deal with the Wimax and Radio updates. What do they do? Why do ppl want to retain them so badly, and if they are so important, why don't the updated ROMs or OTAs have them included?
Wimax and Radio updates improves your 4G/Radio/Data performance. They should be flashed after you flash your rom.
9) What's the difference b/t a Nandroid backup and a Titanium backup? And which one should I do?
Nandroid backup creates a complete image of your phone. Titanium backup only backs up your apps.
Speak friend and enter...
Speak friend and enter!
OK then, all the LOTR references aside, I was in your shoes not to long ago. You could have done a little more reading or googling (something like "how to root EVO"), as these forums usually contain a number of threads with titles something like "Moron-proof guide to....."
Anyway. Unrevoked seems to be considered a somewhat incomplete root according to most ROM threads (I don't know the details to speak intelligently on
the matter).
Here is what I did, and it worked well.
1) Get SimpleRoot. This will let you root your phone for real.
NOTE: I don't know if you need to get rid of unrevoked before this; maybe someone more knowledgeable can chime in on this one.
2) Step 2 of SimpleRoot is to flash recovery. There are two options; I chose RA. There are a few threads that talk about pros/cons of each.
For simplicity sake, I think of "recovery" as a program that lets you do lower lever system stuff, like flash files, do backups, etc. The general way to reach it is to hold VolDown while powering up you phone, then selecting "recovery".
Anyways, after you've flashed recovery, you'll be able to flash whatever ROM you want.
3)If you want stock 2.2 get THIS. Get the radios as well. Generally there are instructions with the ROMS, READ THEM.
You should have three zips. Put them on your sdcard. Then in recovery select flash from zip file (or something like that). Do that for all three with reboots in between.
You should now have the latest stock ROM and radios.
There are a ton of other ROMs out there. NO one will be able to tell you which one is the best, so don't ask.
Wireless Tether - the newest version is floating around here somewhere (pre7). It works well with the rooted stock 2.2
The PRL/PRI debate is still going on. You can read the million threads and see if you want to worry about it. I don't.
As far as backup goes, the more knowledgeable folks can speak to the details. A simple way of describing it is nand backup (from recovery) is like a ghost of your system, where as Titanium is more of an apps/settings kinda thing.
I strongly suggest reading the guide threads to gain more insight.
And, of course, I didn't come up with any of this stuff. If you find anyone's work helpful, then you should thank/donate to them.
EDIT: Hehe, looks like I was second in the helpful line.
That pretty much answers it all.
I can address #7.
Once Frodo is installed into mount doom he must cast the ring into the fiya.
Quickly though. For the creature gollum lays await in the shadows of every crevice left behind.
You must upgrade your puke ridden leggings and ingest some pain reducing ibuprofen for maximum connectivity with the force.
There I go switching epics again..
PLEEEASE STICKY!!!!!!!!
Then I could always find this thread in a hurry when I'm in a bad mood and need a pick me up.
This thread has brought great joy to my life. Expect me to bump it about once a week.
It's funny that I have no clue how to do this, because I full-rooted my EVO with the first firmware and never looked back. I've just been running custom recovery and custom roms ever since. I need to root a friends phone soon, so I guess I'll have to learn.
After much lurking and wiki reading I would like this stickied as well.
To get Frodo 2.2, you would have to write a novel, placing him in a setting similar to The Terminator. From there, create a back story on how his first version was inferior and lacking superior abilities, dubbing the need for a new version. After that have a fight scene of him going against his creator, thus needing to make him version 2.2. The non violent version. From there he would have the dramatic speech in a weird code of language.
Simple root, click click, RA, click. Power button volume down. Wipe, wipe. wipe. rooted rom zip, radio zip, reboot, power button volume down wimax zip, reboot.
After that Frodo will walk away into the sunset, in search of the future version of him, Frodo 3.0 - Fighting in the conquest of his arch nemesis, Apple Conner.
Quiksmage said:
one does not simply walk into Mordor.
Click to expand...
Click to collapse
Dammit Bilbo, you beat me to punch
Can I get frodo as well?will this give me wifis?
Sent from my HTC Evo using Tapatalk.
I did a PaSSIMG FRG33 version, but I can not root with universal androot also can not return to the version of PASSIMG FRF91, indicates that it is old version. Anyone know?
As it stands, if you want root you're back to having to unlock the bootloader.
You could try: http://forum.xda-developers.com/showthread.php?t=726258 and seeing if you can revert to FRF91 afterwards.
Try?
But someone made with good results?
You should have rooted FRF91, installed a custom recovery, and then used an update.zip format of FRG33 to update to update the system and boot.
kam187 said:
You should have rooted FRF91, installed a custom recovery, and then used an update.zip format of FRG33 to update to update the system and boot.
Click to expand...
Click to collapse
No work recovery with update.zip. Android exclamation!
Also, i can not install passimg frf91, indicat that is a old version
Androith said:
No work recovery with update.zip. Android exclamation!
Also, i can not install passimg frf91, indicat that is a old version
Click to expand...
Click to collapse
Android exclamation is STOCK recovery. Kam is saying "custom recovery" like Clockworks or RA.
Ok,
I got it, but unlocking fastboot to install the superboot. Now I have total control
Now we have to wait to close lock
Thanks!!
Which version of superboot should we be using to root this frg33?
The superboot FRF91
http://www.mediafire.com/?4nnez0uddqk519r
Thanks a lot. I opted not to wait for a new 1-click version. Unlocked the bootloader by cmd prompt. It was weird though. I thought when I was reading about superboot that all you had to do was dbl-click it from windows, but I ended up having to run it for cmd prompt, too. Either way, I'm rooted now. My only remaining question has to do with the custom recovery stuff. I flashed the "latest clockwork recovery" in ROM Manager. Then I flashed the modaco rooted/deodexed/busybox/etc. version of frg33. Is that all I need for my phone to be "safe" at this point? I guess ROM manager let's me flash just about any of the custom ROMS, but if one hangs on load, I just wanna make sure everything is restoreable.
BTW....Android clearly has the best and most helpful community of users that I have ever seen!!!
makelegs,
Glad you got it all worked out and are truely unlocked and rooted. As long as you nandroid, you are safe on what ever yoy wan to do. The dreaded, botched radio flash is probably the only way to get hurt. At least that is my understanding.
That's the funny thing.... I am completely confused about "nandroid." I can't figure out if nandroid is a general concept or something very specific. I have a couple of complete backups performed with clockwork, but nowhere in my "recovery" area have I seen the word NANDROID. So I'm pretty sure, at this point, that if the fit hits the shan I have a plan-b, but nobody ever says "be sure to 'some other kind of' backup." They always say "be sure to nandroid." Am I taking this too literally??? or have I overlooked a step in this process?
I even paid for the premium Rom Manager upgrade so that I could try out different ROM's, but I have this sneaky suspicion that I oughta get closure on the whole "nandroid" thing before I get too carried away.
You've been a lotta help.
makelegs said:
That's the funny thing.... I am completely confused about "nandroid." I can't figure out if nandroid is a general concept or something very specific. I have a couple of complete backups performed with clockwork, but nowhere in my "recovery" area have I seen the word NANDROID. So I'm pretty sure, at this point, that if the fit hits the shan I have a plan-b, but nobody ever says "be sure to 'some other kind of' backup." They always say "be sure to nandroid." Am I taking this too literally??? or have I overlooked a step in this process?
I even paid for the premium Rom Manager upgrade so that I could try out different ROM's, but I have this sneaky suspicion that I oughta get closure on the whole "nandroid" thing before I get too carried away.
You've been a lotta help.
Click to expand...
Click to collapse
Can't speak for Clockwork but on Anom the backup goes in /sdcard/nandroid/DEVICEID/dated-subdir
Each time you make a backup using nandroid, it's a new directory.
And you can NOT restore a nandroid made from a different recovery from what I've read. If you make it with Clockwork you gotta restore it with Clockwork.
makelegs,
It has become a general term with the advent of Rom Manager/ClockworkMod. If you look at the top of the Clockwork screen when in recovery, it say nandroid. The term generally means a full image backup of your phone as opposed to just backing up apps/data. In the nandroid the OS and all else is backed up. So, I wouldn't give it a second thought.
What khaytsus said is the only important thing. Restore thru whichever recovery you backed up with. Clockwork to Clockwork or Amon to Amon.
Amon is put into the nandroid file on your sd and Clockwork is put into Rom Manager under Backups. Although, you can get to them a couple different ways in Clockwork. Thru Install Rom From SD Card or Manage and Restore Backups. Also by booting into Clockwork Recovery. You probably already know that if you use Clockwork.
Ken
Is it actually probable that 1 click might be made to work for 33? It doesn't seem like there are many other users with stock/33 like myself. I feel like a horses ass for flashing it and screwing up my protected apps. All through the incremental updates that led us from 2.1 to froyo went thru easily with no paid apps issues so I didn't have my guard up for this one. (Unless they all had a modded fingerprint status which I starting to think I may remember them having, whatever, this is a bummer...)
Maybe it will be updated, but the folks on frg22 (i think) have been waiting even longer. I was just too busy and OCD to wait it out.
It was probably only ever a matter of time before I went the unlocked bootloader/root route. This was just the catalyst for me. I learned an awful lot in the process. Alas, my phone is back to "normal", but running modaco's rooted/deod/busy/frf91 finger/etc... version of FRG33. And I now realize that if I had just flashed the clockwork recovery to begin with, when I was 1-click rooted on frf91, then this whole thing would've been substantially less of a PITA for me.
Good luck!
FRG33
I got caught out i had 1 click root with cm6
But then installed FRG33 not realising i would lose root if i reverted to it after i had done a backup of cm6 .
I had a lot of things including adfree working on FRG33 prior to recovery .
I think the universal androot app uses the "exploid" method which indeed was patched in FRG versions. But I believe someone on the forum reported that FRG22 or FRG33 was still vulnerable to the "rageagainstthecage" root exploit.
Can someone here verify whether FRG83 is still rootable using "rageagainstthecage"?
You can try the instructions for rooting FRG33 in the Wiki on FRG83.
Okay, so I've been reading for a couple days now, and I know the exact process that I want to take to Permaroot my MT4G and get S=Off, and I understand very clearly what those terms mean and why I want them.
Once I started looking into what to do beyond that, I got really, really confused.
If someone could refer me to somewhere so I can read more, I would really appreciate it.
For starters, I don't understand what flashing is. I also don't know what pushing files via the adb is. I don't know what the difference between a ROM and a kernel is.
^^^^All of those would be helpful
I guess I'm just confused about what to do now. Should I now set up the SDK on my PC and configure the ADB? Or should I flash Clockworkmod and do a nandroid backup? Neither?
Once I've done that, should I find a kernel, a ROM, or both? I know I want Gingerbread, I want OC capability, and I it stripped down (missing bloat), but I also want stability and for things like WiFi to work. On top of all of those questions I posted above, does anyone have any recommendation for a ROM/kernel like that?
Sorry about all the questions, and thanks.
corruptsmurf said:
Okay, so I've been reading for a couple days now, and I know the exact process that I want to take to Permaroot my MT4G and get S=Off, and I understand very clearly what those terms mean and why I want them.
Click to expand...
Click to collapse
Well that i a good start. Good to see some reading before the jump in feet first.
corruptsmurf said:
Once I started looking into what to do beyond that, I got really, really confused.
If someone could refer me to somewhere so I can read more, I would really appreciate it.
Click to expand...
Click to collapse
That's why we're here.
corruptsmurf said:
For starters, I don't understand what flashing is. I also don't know what pushing files via the adb is. I don't know what the difference between a ROM and a kernel is.
^^^^All of those would be helpful
Click to expand...
Click to collapse
Edited: added Later
ADB is a commander center/protocol (if you will) that allows you to control your phone via a PC/Mac/Linux. You can push files which would be taking the file and "pushing" to the phone. Or "pulling" files from the phone and putting them on the computer. It's simply as it states, pushing and pulling the files.
To see what a Kernel is read This.
A ROM is the phones physical Operating system. Similar to what Window, Mac or Linux world be.
corruptsmurf said:
I guess I'm just confused about what to do now. Should I now set up the SDK on my PC and configure the ADB? Or should I flash Clockworkmod and do a nandroid backup? Neither?
Click to expand...
Click to collapse
Before you can flash Clockwork Mod you need to root your phone and turn s=off. For one of the methods, - before you can start you need to set up the ADB (Android Debug Bridge). See my signature for the quickest and most painless way to get that set up. You will also need VISIONary.apk. A quick Google Search will find it for you. Link
corruptsmurf said:
Once I've done that, should I find a kernel, a ROM, or both? I know I want Gingerbread, I want OC capability, and I it stripped down (missing bloat), but I also want stability and for things like WiFi to work. On top of all of those questions I posted above, does anyone have any recommendation for a ROM/kernel like that?
Sorry about all the questions, and thanks.
Click to expand...
Click to collapse
If you want a 2.3 based ROM you will need to flash Recovery image 3.0.0.6, link can be found in my signature, and hit up the development section to read reviews on different ROMs. I personally like the plain AOSP look so that leave Cyanogen(mod). But i know TeamRoyal has put together some newer ROMs that i haven't tampered with yet.
I do everything on my phone through CWM (clockworkmod) or terminal emulator, so there's no need for a PC, unless to download the files and transfer them to my SDcard, as I don't understand adb. Anyways, I'm gonna explain this very short and sweet cuz I was once in your shoes, and remember how much I had to read to understand something That could've been explained so simply.
Think of it this way. You're building the software version of a car. Now, if the whole car is the ROM, then the engine is what would be the kernel. And flashing would then be another word for installing , Now, a toyota with a ferrari engine, would be a custom ROM. While a toyota with a ferrari engine and BMW insignias all over it would then be a custom themed ROM.
**Remember, you can never install a car on something, but you can always install something in a car**
Ex. You can never flash a ROM on a kernel, but you can always flash a kernel on a ROM.
Anyways, first off, you will need CWM recovery to flash. Get it from the market. In the app itself, flash (this is the "flash" in the app) recovery 3.0.0.6. This will flash (this flash is not in the app) anything; any ROM, any kernel, etc. as long as its a FLASHABLE ZIP.
To boot into the recovery (the place you do flashing), hold both volume down and power buttons down as you either turn on or restart your phone. The screen you see is the bootloader. Choose recovery using the volume buttons, and use the power button to select it.
Going to flash a new ROM? Do a factory reset (in recovery), wipe cache (in recovery), and wipe delvik cache (this is in advance in recovery). Then install zip. Its pretty straight forward from there.
Going to flash an updated ROM, skip factory reset (as this deletes all data on your phone) and do the rest.
After you've flashed the ROM, you can now flash the kernel.
Note that, kernels are ROM specific. Read what kinds of ROM's the kernel is for before you flash it.
There, easy as pie, yeah? Hope that helped.
I recommend cyanogenmod 7 (Gingerbread based ROM) with faux's kernel (Gingerbread based kernel)
Sent from my HTC Glacier using XDA App
corruptsmurf said:
Okay, so I've been reading for a couple days now, and I know the exact process that I want to take to Permaroot my MT4G and get S=Off, and I understand very clearly what those terms mean and why I want them.
Once I started looking into what to do beyond that, I got really, really confused.
If someone could refer me to somewhere so I can read more, I would really appreciate it.
For starters, I don't understand what flashing is. I also don't know what pushing files via the adb is. I don't know what the difference between a ROM and a kernel is.
^^^^All of those would be helpful
I guess I'm just confused about what to do now. Should I now set up the SDK on my PC and configure the ADB? Or should I flash Clockworkmod and do a nandroid backup? Neither?
Once I've done that, should I find a kernel, a ROM, or both? I know I want Gingerbread, I want OC capability, and I it stripped down (missing bloat), but I also want stability and for things like WiFi to work. On top of all of those questions I posted above, does anyone have any recommendation for a ROM/kernel like that?
Sorry about all the questions, and thanks.
Click to expand...
Click to collapse
Neidlinger's got your back.
1. Glad you're reading before doing. What a welcome change of pace!
2. Flashing is the process of installing new software. We "flash" it to the phone's memory.
3. ADB is using a computer to control the phone via command-prompt from DOS. Push is a command which sends a file from your computer to your phone. Do a search, there are lots of good guides on ADB. TrueBlueDrew made one just recently that I highly recommend.
Here's Drew's thread. Don't forget to hit his thanks button! - http://forum.xda-developers.com/showthread.php?t=928370
4. Start with Clockwork Recovery and a nandroid backup. That's good practice. CWR2 is compatible with Froyo (2.2) ROMs. CWR3 is compatible with Gingerbread (2.3) ROMs. CWR 3.0.0.6 is compatible with BOTH. Very convenient.
5. I say start with CM7. It's extremely stable, even though it's still in development. A ROM is a complete OS replacement for the phone. ROMs contain kernels, which control the most basic hardware, such as processor. If you flash a custom kernel on your stock ROM, you can overclock it more. You can also flash custom kernels on top of custom ROMs for different battery life, clock speed, etc.
To be honest I don't even bother with custom kernels since this phone is so damn fast out of the box I really don't see the point.
QUICK TIPS FOR CM7 - On your first boot, let it sit for 5-10 mins before setting up. There are background processes running and interrupting can harm stability. BEFORE you sign into google for the first time, after it's finished sitting, reboot. This will clear out any wifi glitches and give you smooth sailing.
Have fun!
BTW, I think most ROM's have a kernel already built in. People install custom kernels because they can have fixes for bugs, help with battery life, overclocked frequencies, no lags, etc. Otherwise, you can just flash the ROM, and if you're satisfied with the kernel its running on, then obviously you'll have no need to flash a custom kernel.
Sent from my HTC Glacier using XDA App
Uchennadi said:
BTW, I think most ROM's have a kernel already built in. People install custom kernels because they can have fixes for bugs, help with battery life, overclocked frequencies, no lags, etc. Otherwise, you can just flash the ROM, and if you're satisfied with the kernel its running on, then obviously you'll have no need to flash a custom kernel.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
This is pretty much spot on. The developers have included kernels that they feel make the OS preform at it's peak. and most of them will allow for overclocking. However on some of them you may need to use a program called "setCPU" to adjust the frequencies. Cyanogen(mod) will have this built into the ROM natively. However most of the veterans will not promote running your phone in an over clocked status 100% of the time. most of us leave the phone at 1Ghz or slower. There are physical reasons, ie the constant expansion and contract of the chip isn't good for the mother board.
If i were you i'd stick with the Stock Kernel and leave it running as it. That way the developer can adjust their ROM, if you use an 3rd party kernel they aren't familiar with the coding so it's not going to act correct.
I'm not putting down what the kernel coders do, they do an awesome job. but for a n3wb i'd leave well enough alone.