Related
hi everybody you guys are geniuses!
i m new to this whole spartphone thing! i just bought my htc evo and i m trying to root it but i don t even know the basics! what is a flash and how do i flash? what is sd configuration and how do i do that! how do i do backup ;nandroid backup?what is a kernel and how to put it into my rom!! basicly i need all the info from the begining until i run a custom rom! i really need help on this one! thank you!
Google is your friend
_MetalHead_ said:
Google is your friend
Click to expand...
Click to collapse
+1
There are plenty of people around here that like to help, but asking to have the entire android guide spelled out for ya is a bit much. Go search and read up on what you can understand, then read a little further. When it starts to get confusing again, come back and ask a specific question or two. You will get a lot more help that way.
That s why I m asking! I did look it up, and it s confusing
Sent from my PC36100 using XDA App
utzu said:
That s why I m asking! I did look it up, and it s confusing
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
You gotta look up the tutorials. Flashing means moving something to your SD card and installing it.
unrevoked is kinda advanced since ur brand new..search on youtube for how to root evo 4g
swyped htc supersonic
stay stock
Google the basics . Most people don't have time to explain everything to you. There is a lot to learn, and I would advise you to not mod your phone unless its something you like to do. Your home work too google.
What is : nand recovery, back up, restore
What is: flashing
What is: recovery
What is: sd card, what is stored on it
What is a : rom
What is a :kernel
How do I flash them?
Learn what a ".apk" file is
What two recoveries do you have to choose from?
What is root? And its history (where it came from)
What is "su command"
What is "s" off and "s" on
Like I said, if you don't like too do this stuff and aren't a geek like the rest of us then I wouldn't bother, it takes a lot of reading and learning, one thing we all have in common is we are all still learning.
Sent from my netarchy_toast, froyo beast of a machine evo!
Honestly, I would love to help, but you are asking too much. It takes weeks, months, even years to get fully acquainted with android and hacking it, especially if this is your first smartphone. If I were you, I would enjoy being stock for now. Once you figure out how to use either terminal or command prompt (Mac or pc, in that order) then maybe start making gradual changes. If you need ANY actual help, pm me as you would not be the first noob i helped. I consider it my duty (ha). Take developments from the experts, give info to the noobs. Really, get familiar with everything, look up some stuff, watch some videos, and if you still need any help, shoot me or another one of the experienced and helpful devs at the xda a pm (private message. Click their name and it will give you the option.) and you will be helped, I garuntee it.
utzu said:
hi everybody you guys are geniuses!
i m new to this whole spartphone thing! i just bought my htc evo and i m trying to root it but i don t even know the basics! what is a flash and how do i flash? what is sd configuration and how do i do that! how do i do backup ;nandroid backup?what is a kernel and how to put it into my rom!! basicly i need all the info from the begining until i run a custom rom! i really need help on this one! thank you!
Click to expand...
Click to collapse
Hahahaha really! I mean c'mon did you even read any of the sticky's (threads at the very top of the forums)? Youll be amazed that all or most of your answers are there..
Heres a link to get you started read the page and click the links and read some more.
http://forum.xda-developers.com/wiki/index.php?title=HTC_Supersonic&useskin=vector
Not picking on ya but you need to understand the basics on yor own because its likely your phone will get messed up if you dont, and you are the only one to blame if it does. Thays why its important to fully understand what you are doing, remember flashing anything to your phone WILL void the warrantee if you screw up so be carefull.
Read for a month!
Read up on everything for a month, then start your EVO hacking experience!
Here are a few that are great starting points:
Common Misconceptions and Info
HTC EVO WIKI
How To Use These Forums
How To Search XDA
Helpful/Popular Threads
REMEMBER! - Any question you are thinking to ask, has most likely been asked and answered before on these forums SO SEARCH!
Good luck, and welcome!
I would start here http://forum.xda-developers.com/showthread.php?t=706411
once you get that done the custom recovery is installed things will be much easier
I used that root method one my replacement evo and it worked just fine.
BrianDigital said:
I would start here http://forum.xda-developers.com/showthread.php?t=706411
once you get that done the custom recovery is installed things will be much easier
I used that root method one my replacement evo and it worked just fine.
Click to expand...
Click to collapse
This is if the OP does NOT have Android v2.2.
OP - If you go this route you will need to downgrade in Regaw's 2.2 ROOT METHOD, but stop before using unRevoked.
I am in an overly good mood today so i will help out with some basic information
What is : nand recovery, back up, restore - A nand back up is basically a way to back up your phone its rom and settings. a nand restore uses the a nand back up you made to put your phone back to where is was when you made the nand back up (think about a restore point on a windows computer very similar concept).
What is: flashing - Flashing is the process used to install system files. this is usually done through a recovery which i will get into below. the reason it is called flashing and not installing is because it needs to be done through recovery and is a slightly different process but in more basic terms it is basically installing your rom or radio or other system critical pieces onto the phones internal memory.
What is: recovery - a recovery is basically a program that lets you access some advanced system features, these include nand back up and restore, wiping cache, data, and dalvik, and the ability to flash (install) certain files to your phone. to get into a recovery with your phone off hold volume down and the power button you will load to a white screen with several options (this is the hboot or bootloader) select recovery.
What is: sd card, what is stored on it - Out of the gate your sd card is set up as it should be. their are a few reason you might change this however with 2.2 it has become less of a need and i recommend just leaving it be. The main reason people configure there sdcards is to allow a script called apps2sd to work. what this does is it allows you to store all your apps on the sd card they are normally stored on the phones internal memory. Froyo or 2.2 (the android os version on your phone) has the ability to allow apps to move to your sd card through the settings. now this doesn't work for all apps as it has to be turned on by the app creator but many it will. Because of this i would leave your sdcard alone while you learn the ropes.
What is a : rom - a rom is basically the operating system of your phone. what a rom does is replace the default os with a custom one that has been tweaked or built by a developer. this is the piece of the phone you interact with.
What is a :kernel a kernel is basically the software that translates what you do in the rom to the hardware. think of it as the phones steering wheel. you let the phone to do this and the kernel interprets it so the hardware knows what to do,
How do I flash them? To flash files is relatively easy you place them on the root of your sd card (basically drag and rop onto the sd card but not in any folder). then you boot into the recovery. in the recovery you shoudl be able to find the options to wipe cache, wipe data/factory and wipe dalvik. you select each of these and then yuo select flash .zip from sd. next you scroll to the file you want to flash (the rom or kernel etc you want) and select it (normally power button) you should then flash the rom. once it is flashed select back until you see reboot phone and then reboot it and you should boot up with your new rom.
What is "s" off and "s" on - s on and s off is basically the way you can tell you are rooted in the bootloader (or hboot i talked about above) at the very top you should see one of these options. what these mean is whether your phone requires a signed file (s on) or whether it can flash unsigned files (s off). for now just consider a signed file as an official file with an unsigned file being unofficial or modded.
Now hopefully this explains a bit of the basics better and gives you enough information to better understand what is going on. My recommendation is to take the steps to root flash etc 1 at a time it is easy to read through all the instructions and go wow this is confusing. it really isnt as bad as it seems and as long as you follow each step you should be fine. just do exactly what each step tells you to do and dont worry about the next steps till you are there. you still have a lot to learn and the best way you can learn it is by searching the forums think of it as your library.
many people are glad to help however as you can see from some of the posts it is expected that you at least try to learn and research things for yourself. if you get stuck on something ask and you will normally get an answer just try remember if you cant take the time to search and research things you shouldn't expect others to take the time to help. i'm not saying you did i ma jsut giving advice for the future.
anyway best of luck and hopefully this will get you in the right direction.
NOTE: i have "dumbed" down some of the explanations to give the jiest of the idea with out getting to technical so for those that are more technical it is on purposse.
Well everyone the dinc2 community has treated me well but I have moved on to the htc rezound please do not hesitate to still pm questions though I'm hoping I can find a volunteer to take over this thread. I'll miss you guys cuz for the most part it was a very mature forum and ill pop in once in awhile to say hello. Good luck if anyone would like to give back to this community and take over this thread pm and ill pm a mod. god bless
I thought it maybe fun to have a light and humorous side to this also so everyone keep your eyes out for funny posts that can make our quote of the day:
if you guys see any posts that make you chuckle pm me and I will put it here and credit you for finding it
Anyone looking to root your incredible2 that is on 2.3.4 with the.98 hboot please see here: http://forum.xda-developers.com/showthread.php?t=1298990 then after your hboot is downgraded follow the instructions on rivera82falcons thread,linked below
hey guys I'm attempting to get a thread started to get all the basic info out to the newcomers that they will need to start there modding a flashing journey. I'm also hoping this will help cut down on the repetitive questions and useless posts mucking up our forums. This is and always will be a work in progress, so this is just a start there will be much more info added as time goes on.
First thing if your not rooted yet everything you need to know is in this thread by rivera82falcon http://forum.xda-developers.com/showthread.php?t=1219246
Next up is how to flash a custom rom: http://forum.xda-developers.com/showthread.php?t=1263756 by AgalychnisCallidryas
Another thing is the gingerbread ruu. If your phone comes with froyo I would reccommend following the directions on this page before trying to root because unrevoked is becoming increasingly harder to find. Also this can get you out of some pretty sticky situations if you mess up badly enough: http://www.androidpolice.com/2011/0...8-605-4-same-as-the-official-gingerbread-ota/
wanna try a different radio? Head over to gu1dry's thread: http://forum.xda-developers.com/showthread.php?t=1134451
Its my opinion that every flasher should have adb setup on their computer, it will bail you out of a bootloop, tell you why its happening and do all kinds of other awesome stuff. here is an excellent thread from nephron to get you on your way, its from another phones forums but everything except the drivers apply to us, obviously install the correct drivers for your phone: http://forum.xda-developers.com/showthread.php?t=532719
for those of you who use aosp roms, just about everyone prefers the miui camera over the aosp stock one and here it is with instructions. Thanks pacerguydon: http://forum.xda-developers.com/showpost.php?p=17691395&postcount=11
if your market is missing apps, check this out: http://forum.xda-developers.com/showthread.php?t=1275574 thanks knipp
those of you who want to learn java and general scripting here is a few good tutorials that artvandelay440 dug up:http://forum.xda-developers.com/showpost.php?p=17691710&postcount=13
for the up and coming themers here is where to get brut.alls apktool:http://code.google.com/p/android-apktool/ if anyone can find me a good noob friendly tutorial for apktool let me know and I'll post it.
tommytomato created a fantastic super tool called android utility, you can decompile apks sign them and do all kinds of good stuff. Really the ultimate themeing tool: http://forum.xda-developers.com/showthread.php?t=1167623 if your thinking of doing mods and themes of your own you should check this out, tommy is a modding master and extremely helpful to new themers
wanna changer your splash screen or boot animation? Have a look at 06stangs thread here: http://forum.xda-developers.com/showthread.php?t=1161543
if your running an aosp rom you can change the carrier label here's how: http://forum.xda-developers.com/showthread.php?t=1221882 thanks to artvandelay440
running a sense rom? Go here for a new lockring: http://forum.xda-developers.com/showthread.php?t=1260128 thanks to jwhetstone02
our friend knipp21 has started modding miui lockscreens check it out: http://forum.xda-developers.com/showthread.php?t=1288566
before getting my incredible2 I had an inspire, the one thing I missed about the inspire was 4ext recovery,well now we have it. Big thanks to madmaxx80 for the awesome recovery: http://forum.xda-developers.com/showthread.php?t=1267540
here is a great tool for undervolting, it provides an easy to use gui, please read up on the pros and cons of undervolting before attempting and remember you must have a kernel that supports undervolting to use this. It will not work on the stock kernel. Thanks to chad0989 for this: http://forum.xda-developers.com/showthread.php?t=1190004
here is setcpu a tool for overclocking, your kernel must support overclocking and this should not be used in conjunction with any other overclocking apps. Thanks to coolbho3000 for this, and please guys consider purchasing the donate version of this: http://forum.xda-developers.com/showthread.php?t=505419
here is a very educational thread similar to this one, its from the thunderbolt forums but most of the info applies to us as well. Its a very well put together thread and super informative. I reccommend you guys check it out because its a good read. Big thanks to loonatik78 for putting it together: http://forum.xda-developers.com/showthread.php?p=16695064#post16695064
another thing I would like to stress to the new people, xda has a thanks button, and now you can even use it right from the xda app, don't be greedy with it guys if someone helps you click thanks.
I would like this thread to become a community effort, if there is anything you guys feel should be here dont hesitate to let me know. This is my small effort to give back to a community that gave me so much so I will gladly try to answer any and all questions in an effort to keep our forums clean. No matter how stupid you think the question may be pm me and I'll try to help. I may not always have your answer but will most likely be able to point you in the right direction. see post three for frequently asked questions
Pm me for any and all questions as well.
Sent from my Incredible 2 using xda premium
this q and a section will be a work in progress as well. If anyone has suggestions for questions that you think should be here, by all means let me know.
Q: I think I bricked my phone what should I do?
A: calm down 99 percent of the time people think they are bricked they really aren't. If your device shows any sign of life your chances are good that your ok. If you can access hboot by holding volume down and power while the device is off your in good shape you can still flash the ruu and get back to stock.
Q: I put the ruu on my sdcard but hboot cannot find it
A: when flashing anything from hboot it must be named exactly PG32IMG.zip and yes it is case sensitive. Also if you have to rename the file, if doing it on a computer be careful because a computer will automatically add a .zip to the end of it and hboot will not recognize it.
Q: I flashed a kernel a now my "insert issue here" don't work
A: did you flash an aosp kernel on a sense Rom or vice versa? If so things will not work as they should always make sure the kernel you are flashing is compatible with your Rom.
Q: will sense apps and widgets work on aosp roms?
A: short answer is no
Q: my phone is stuck in a bootloop what should I do?
A: some time in your flashing career you will encounter a bootloop, there are a couple of ways to fix this number one is start adb (which every Rom flasher should have set up in my opinion) and type adb reboot recovery and hit enter then once in recovery you can reflash and try again. Your other option is to pop the battery out, put it back in then hold volume down and power to get into the bootloader once there select recovery. If you can not navigate in the bootloader that means the PG32IMG.zip is on your sdcard still. Remove that and it will let you navigate the bootloader. If you have no way to remove that .zip pop out your sdcard boot into bootloader select recovery then pop your card back in.
Q: what is the best Rom out there?
A: there is none its all a matter of opinion. Just a warning, don't start a new thread asking this question you will be flamed into oblivion and the mods will lock it. I've seen it a million times
Q: I just flashed an aosp Rom (miui, cm7, omgb) why is my earpiece volume so low?
A: as of now this is a known issue for our aosp Roms, the tiamat kernel is said to fix it.
this is the start of my q and a and it is far from complete, if you think there is something important that is not here by all means let me know.
Ok guys here is some basic terms you should be familiar with before rooting and flashing
1. Flash or flashing, basically just means to install something from recovery or bootloader
2. Rom- the word rom is kind of an outdated term (read only memory) because we can in fact write to it, nonetheless a rom in the simplest of terms is basically your operating system.
3. Kernel- the kernel is the heart of your o.s. It basically communicates with your software and hardware, wifi and processor speed are a few examples of things your kernel controls among many other things. Sense kernels should not be used on aosp roms and vice versa things will not work as they should.
4. Overclocking- to increase your processors stock speed to increase performance
5. Underclocking- pretty self explanatory underclocking is used to help save battery
6. Undervolting- to decrease your voltage to save battery. Undervolting is a slightly controversial topic some people swear by it and others say it can actually decrease your battery life. Undervolting can cause stability issues so educateyourself before attempting.
7. Radio- basically the software that works with your hardware to give you your signal and mobile network, on other phones they are also reffered to as modems
8. Aosp- android open source project, aosp roms are roms built from the original google source code, some examples of these are cm7, miui, omgb, these are typically lightweight roms that you can customize yourself, they are preffered by many users because of the great battery life and performance
9. Sense roms- these are roms based on an original htc rom, sense is th ui that htc adds to android, sense roms have many nice apps and widgets, and usually are packed with eyecandy, however many people say that sense it a resource hog and needs a lot more ram to run than aosp roms
10. Port- a port is a rom or theme originally made for another device but made to work with ours
11. Wipe- it is usually recommended to wipe before flashing a rom, but not always mandatory, read the forum of the rom your flashing to see if a wipe is recommended or not. Some roms will wipe data automatically some will not. A wipe is just basically giving you a clean start like when you first got the device and is done in the recovery menu. When in doubt wipe, you will run into less issues.
12. Ruu- an ruu is a stock signed rom that is flashed in hboot, an ruu is your get out of jail free card, if you mess your phone up too bad an ruu will bring your device back to its stock state
13. Hboot_ this is basically your bootloader from hboot you can enter recovery, do a factory reset, and flash an ruu, a radio, and other things not flashable in recovery
there is some more basic definitions that I overlooked, see post 28 by artvandelay440
How about some basic definitions? Sense, AOSP, Rosie, kernel, recovery, md5 sum, etc.
How, when, and why to wipe.
How to perform a battery calibration.
Don't restore system data when moving to a different ROM or updating to a new framework.
ontophantoms said:
How about some basic definitions? Sense, AOSP, Rosie, kernel, recovery, md5 sum, etc.
How, when, and why to wipe.
How to perform a battery calibration.
Don't restore system data when moving to a different ROM or updating to a new framework.
Click to expand...
Click to collapse
yes good idea. Definitely will do. I also plan to add a miscellaneous goodies section including commonly used apps like miui camera. And links to kernels and other good stuff. Like I said this thread is a wip I just wanted to get a start on it tonight. I'm not at home now and I'm doing this on my touchpad so its quite tedious. Will work on it a lot more tomorrow. Thanks for the input
Love this idea for a thread. I know this will be a stop that noobs and even seasoned vets will make. Thanks for taking the time to put something like this together!
Thanks for setting this up!
It's really helpful to us newcomers, who inevitably ask a question that will annoy the seasoned members. There is so much info buried in threads with many pages that it's hard to read it all and not overlook something along the way.
Having all the start-up info, and maybe a list of well-known bugs for each rom, in one place will be great!
Woot! Got a sticky!
Sent from my Incredible 2 using xda premium
+1 For the best idea ever. Great job.
I think you should spice it up a bit I'll add more later lol. Good thread guys.
For the first post you can start it like this:
Rooting your phone (Achieving S-OFF)
Please read and re-read rivera82falcons execellent write up located here:
http://forum.xda-developers.com/showthread.php?t=1219246
Flashing a custom ROM to your device
Please read AgalychnisCallidryas thread on how to manually flash a ROM located here:
http://forum.xda-developers.com/showthread.php?t=1263756
Please note that you don't need to back up every user app with titanium backup, some people only like to backup apps that have data, such as games.
It's also important not to back up system apps (apps that came with the phone). Restoring those apps may cause system failure.
Setting up ADB
Nephron has a full set of instructions on how to set up ADB, you can find the thread here:
http://forum.xda-developers.com/showthread.php?t=532719
Finding the ROM that's right for you
This is one of those threads that may be sensitive to some. I find that finding the best ROM depends on your tastes. When ROMs are released they generally have bugs. Some may be deal breakers, like not having MMS working, or something small like not having a particular tweak installed or an application force closing. You really have to download the ROM and take it for a test drive.
Read through the threads on feedback. Generally, if you see the same bug being mentioned it probably is plagued through every ROM install.
GSM functionality of the phone is important to some, but not most. Generally, if you download a ROM that's based off of the original ROM it should work fine. But if you are downloading a port from another device expect that feature not to work.
Don't be afraid to flash a ROM. The worst that can happen is it will throw your phone into a soft brick (bootloop). Simple way to fix it is restore a backup you made or flash a ROM that you know is solid.
Creating a backup (nandroid) of your device
Your phone at this point must be rooted, and the ROM you are running has to be rooted.
Get Rom Manager from the market. Install the latest recovery that it prompts you with - If you've already installed clockwork mod then proceed.
In ROM Manager:
1. Scroll down to Backup Current ROM
2. Name it what you like, like backup_09192011
3. Let it back up. The more data you have the longer it takes.
In recovery: (You cannot assign names in recovery)
1. Boot into recovery
2. Go to backup and restore
3. Choose backup
To restore a nandroid backup - Wiping data, cache, and dalvik isn't necessary.
1. Boot into recovery
2. Go to backup and restore
3. Choose restore
Useful Applications:
http://androidcommander.com/ great for deleting or replacing apps on the fly. Windows interface, simple to use.
Here are a few more additions:
Replacement camera app for those that don't like to use the stock camera that came with CM 7 or other AOSP Roms.
This Click me Miui camera app works great, just remember to go into the camera settings after installing and select 8mp as the picture size. It can be installed as either a separate camera app or as a replacement to the stock camera.
To install as a add on, just install the apk as a you would any other app. Download to your sd card and install.
To replace the stock camera app, rename the downloaded apk to "camera" (without the quotes) and using root explorer (make sure and select R/W) move the renamed apk to system/app and replace the stock camera apk (first though, make a copy of the stock camera app and add .bak onto the end and store this copy on your sd card, I make a folder named storage so I know where my .bak files are at).
Now that the camera apk is in the system/app folder, the permissions and ownership will need to be changed.
Long press on the camera apk and in the popup menu select permissions,
You will want to change it to look like this:
Read Write Execute
Owner x x
Group x
Others x
After changing the permissions, scroll to the bottom of the popup menu and select "change owner"
You will want to change the ownership so that it reads"
Owner 0 - root
group 0 - root
Select OK and your done. Reboot and you will know have the Miui camera installed.
Wallpapers:
Click me
More to follow later.
Awesome guys keep em coming. I didnt expect this thread to explode so quickly great job guys. Anyonr tutorials or info you guys add i will link to in the op. I will typically update the thread every night around midnight eastern time. Thanks guys.
Sent from my Incredible 2 using xda premium
I always see lots of beginning android users who want to learn Java/xml/whatever to begin building. I made a list of some coding tutorials-they might be of some help to a newcomer who wants to learn.
JavaScript for Android:
http://www.youtube.com/playlist?list=PL34F010EEF9D45FB8
General Introduction to learning Android development:
http://developer.android.com/guide/developing/index.html
General Coding:
http://www.codecademy.com/#!/exercise/0
From around XDA:
making your own boot animations: http://forum.xda-developers.com/showthread.php?t=1096068
ADB workshop and guide, including edited path variables: http://forum.xda-developers.com/showthread.php?p=9959449
How to decompile/edit/sign/recompile apks with APK Manager:http://forum.xda-developers.com/showthread.php?t=695701
how to use APK Edit (apk tool with custom GUI): http://forum.xda-developers.com/showthread.php?t=890199
Editing with NinePatch (.9.png) images: http://forum.xda-developers.com/showthread.php?t=1192207
Great thanks!
Sent from my Incredible 2 using xda premium
Add how to change boot animations and splash screens? (my thread)
Sent from my ADR6350 using Tapatalk
Sure will thanks
Sent from my Incredible 2 using xda premium
oxlong27 said:
Sure will thanks
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
Maybe the how to on hulu? I dont think many use it...but it won't take up too much space right and the how to for renting movies from the market (posted somewhere as changing permissions to mu from Su temporarily)
But seriously this is a great job. I didn't expect all this lol. I'm glad we are trying to save our community.
I came to the Eris and it already had a community. We built this one and it needed some leadership. Way to take charge bro
Unlike the Eris all our devs would rather have their own site and that's ok. But ppl haven't been mature about it. I like the devs like tazz and the way he does things. Just the way I am lol.
Sent from my Incredible 2 using xda premium
I never expected it to take off like this either, but im definately glad everyone likes this and will continue to work hard on it thanks again guys. Will update tonight with links to your suggestion
Sent from my Incredible 2 using xda premium
Another thing.
Some questions would be answered of you tried it yourself.
Like "how does this app work" open the darn thing and find put...if you're still lost in the sauce come ask here. Please research and try yourself first.
Sent from my Incredible 2 using xda premium
knipp21 said:
Another thing.
Some questions would be answered of you tried it yourself.
Like "how does this app work" open the darn thing and find put...if you're still lost in the sauce come ask here. Please research and try yourself first.
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
yes very good point knipp I want this thread to be informative and educational not a hand holding experience. I have no problem helping anyone that is willing to help themselves but it makes my skin crawl when I see a post that says “wanna root someone please give me detailed instructions" and I have seen a lot of them.
Since a lot of people have asked me about TWRP 2 for Epic Touch and SGS2 devices, here's the deal:
1) I don't own an Epic Touch or a SGS2 device of any kind.
2) As some may be aware, many Samsung devices do not have and/or properly use a recovery partition. Instead the recovery is packed as a second ramdisk or as a separate recovery.rc in the same ramdisk in the boot image. This means that every time you install a new ROM or kernel, you will get stuck with whatever recovery is included with the boot image.
3) We do have a process that lets you inject TWRP into boot images that are still using the dual ramdisk setup typically found in CM7 boot images. I believe that somewhere along the development path of CM9, the boot image packing method changed to a single ramdisk with 2 init files (recovery.rc). This type of setup is much more difficult (if not impossible) to do "injection" and since I don't have a device in hand to work with I have no plans to attempt to create an injection method for this new type of boot image. The injection process still appears to work on CM7 boot images and some kernel devs for SGS2-type devices have not moved to the new method (yet).
4) We now have code that compiles in CM9. This new code base is much simpler to get started with - you just replace the bootable/recovery folder with the TWRP source code and grab a copy of our slightly modified 1.20 busybox code and you're ready to compile TWRP after adding a few build flags to your BoardConfig.
5) The TWRP source code is all public, including the GUI. It's pretty easy to compile and work with and we have a nice guide to help you out here: http://tinyw.in/nP7d
If you need help integrating TWRP into your builds or have questions about compiling TWRP, feel free to find us in #twrp on Freenode. TWRP works very well with thew GooManager app and if you host your ROM on http://goo.im, your users can receive notifications of ROM updates and easily download and flash the update almost like a regular OTA update. In addition, http://goo.im now supports automatic differential zip creation. You upload an update to your ROM and goo will create a zip with just the changes. Your users get smaller downloads, faster installs, and less wear and tear on the device since only the updated / deleted files get replaced, but this functionality is only easy to use with a supported recovery like TWRP. Please consider adding TWRP to your builds and using http://goo.im and GooManager! All of this functionality is free to you and your users!
If you're feeling really adventurous, you're welcome to install this for the Epic Touch after installing a copy of CM7. I was told by a tester that it was working fine but use at your own risk and be prepared to Odin / heimdall a working boot image if something goes wrong! Note that backups and restores done in TWRP / CWM are not easily interchangable!
http://goo.im/devs/OpenRecovery/epictouch/openrecovery-twrp-2.1.2-epic4gtouch-signed.zip
I can probably create the same kind of a zip for SGS2 International if someone is willing to stop by #twrp on Freenode to test it. I do know that someone has successfully tested a ramdisk on the SGS2 with Exynos so TWRP should work on this device with relative ease.
Also note that it appears for the time being that most Samsung devices released in the USA where all team win members live, are going to be using Qualcomm chipsets instead of Exynos. This means that the only Samsung device that's readily available in the USA that uses the new boot image methods is the Epic Touch. We have a release for the AT&T Galaxy Note and Skyrocket but both of these devices use the Qualcomm chipset which uses a "normal" and separate recovery partition.
No idea what this is about but I got the second post! Woot
Thanks for letting us know about this but we don't have a working cm7 anyway.... do we? I haven't seen one. Also, if I'm reading this correctly, it seems to me any dev who wanted to could repack twrp in any Rom at release. But why would they? Not to take away from the work done by all the twrp team but when I had it on my evo shift it was buggy and rarely formatted everything properly. Has this been fixed or was it a device specific issue?
Sent from my SPH-D710 using xda premium
abadasstanker69 said:
Thanks for letting us know about this but we don't have a working cm7 anyway.... do we? I haven't seen one. Also, if I'm reading this correctly, it seems to me any dev who wanted to could repack twrp in any Rom at release. But why would they? Not to take away from the work done by all the twrp team but when I had it on my evo shift it was buggy and rarely formatted everything properly. Has this been fixed or was it a device specific issue?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
There is a working CM7 for the E4GT. It's posted over at Rootzwiki. TWRP worked fantastically on my Evo and Evo 3D. Glad to see we have another option besides CWM. Hopefully we can get past the bricking issue with ICS roms and I can throw this on my phone permanently.
Thanks Dees_Troy!
Agree worked awesome on my e3d looks to be great
Thanks for this
Sent from my SPH-D710 using xda premium
Team win ftw!!
Sent from my SPH-D710 using xda premium
I love using TWRP and goo.manager on my cm9 touchpad. So easy to use. Glad our amazing devs have more options.
Just wanted to say I used TWRP on my 3D and Nexus S and was my favorite recovery hands down. Would love to see it come to the Epic Touch.
Sent from my SPH-D710 using Xparent ICS Blue Tapatalk 2
I'm going to second everyone that likes twrp. I also enjoyed the recovery very much and it was the one thing I missed when moving to e4gt. I can't wait for source on ICS. If someone doesn't build it into a kernel, I'll be doing some kernel research and building it for myself.
Sent from my SPH-D710 using Tapatalk 2
This is great news I'm tired of not having a working recovery on ics
abadasstanker69 said:
Thanks for letting us know about this but we don't have a working cm7 anyway.... do we? I haven't seen one. Also, if I'm reading this correctly, it seems to me any dev who wanted to could repack twrp in any Rom at release. But why would they? Not to take away from the work done by all the twrp team but when I had it on my evo shift it was buggy and rarely formatted everything properly. Has this been fixed or was it a device specific issue?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
first off the evo shift is an older lower end phone, so performance on any recovery besides cwm which is so basic is probably iffy. TWRP has been pretty amazing on the evo3d and also on my Gnex, and if it gets ported in any working for on the e4gt id be happy to use it for my wife's phone.
if i understood this correctly, twrp recognized the issue with a constant recovery on the e4gt, and they are basically giving us the source to build it into our roms instead of the the stock recovery, so its atleast there on install. it would be nice to see the developers working on cm9 on this phone integrate it into the rom.
This does sound like a step in a good direction but I have to ask....
How do we not have working recovery? It takes literally 45 seconds extra to flash EL26 and then reflash current after the backup is made...sure it isn't "ICS recovery" but it's the result I'm interested in..
are we this lazy that a less-than-one-minute procedure is worth whining about?
Not taking a shot at anybody.. just sayin. I see people complain about this more than anything and they could have made 10,000 backups with the time that they were posting complaints about it.
Especially now that stock kernels can flash...let's let it go.
Kebetz said:
This does sound like a step in a good direction but I have to ask....
How do we not have working recovery? It takes literally 45 seconds extra to flash EL26 and then reflash current after the backup is made...sure it isn't "ICS recovery" but it's the result I'm interested in..
are we this lazy that a less-than-one-minute procedure is worth whining about?
Not taking a shot at anybody.. just sayin. I see people complain about this more than anything and they could have made 10,000 backups with the time that they were posting complaints about it.
Especially now that stock kernels can flash...let's let it go.
Click to expand...
Click to collapse
i want a working one already because i dont have the means to get mobile odin, and im rarely home, i came from the og epic and most of my flashing was done on the go. Now im lucky to update my rom once a week. A working recovery that wont brick my phone is a huge plus for people on the go
Kebetz said:
This does sound like a step in a good direction but I have to ask....
How do we not have working recovery? It takes literally 45 seconds extra to flash EL26 and then reflash current after the backup is made...sure it isn't "ICS recovery" but it's the result I'm interested in..
are we this lazy that a less-than-one-minute procedure is worth whining about?
Not taking a shot at anybody.. just sayin. I see people complain about this more than anything and they could have made 10,000 backups with the time that they were posting complaints about it.
Especially now that stock kernels can flash...let's let it go.
Click to expand...
Click to collapse
I don't mind flashing the EL26 Stock CWM kernel at all. With Mobile Odin it literally takes a minute tops. But I like having the best on my phone and IMO the best recovery out right now is TWRP. It's always worked REALLY well for me. Not one single issue ever. Add in the other features, like compressing backups to save space which may not be a big deal with this device but anyone who's used Sense 3.0 could testify how awesome that feature is. Along with being able to theme every aspect of the recovery and as a themer I just love that option. That's just to name a few. So again, in my case it's not about being lazy but more about wanting the best available for my phone. So if TWRP is a possibility I would love to see it.
I have to agree with tiffany. It is more about the recovery itself. I use mobile odin and take no issue with the current methods but I also would like to have TWRP running on my phone. Hopefully source is released soon and we can take advantage of this. Thank you for posting the links for it and hopefully one of our devs can help to make this happen.
Ok, I admit, odining back to el26 isn't something to complain about for normal flashing. But when trying to alter system files to get the result you are looking for can become somewhat frustrating when a boot loop occurs. Normally a battery pull and a quick flash gets you back in the game. In my experience though, as I'm sure other cracks flashers can agree, sometimes you just have to flash something new, right before you step out the door. Lo and behold you realize you have just set yourself up for failure, failure to boot that is. As I stated in another thread, a lot of folks have busy lives and don't spend every moment reading xda, all they want to do is grab what's hot and flash it with the same procedure as every other Android device that they have come to know and love. In my opinion, working recovery = happy forums. And soon enough we will, and when we do, I want to be sporting TWRP.
Sent from my SPH-D710 using Tapatalk 2
Why all the fuss over something that you use for 5-10 minutes when you flash a ROM, theme, etc.? How much time are you spending in Recovery?
The next thing you know people will want the "Download" mode to be themed and "prettied up" too.
Does anyone remember what it took to customize phones 4-5 years ago? Oh wait, this is XDA, I forgot it's the land of "gimme gimme gimme" and hardly ever about "thank you" or "how can I help you with that?". Users just want to be "alpha" testers so that they can have the newest, hardly do they ever upload logcats, dmesg logs, or help in troubleshooting.
-Daryel
daryelv said:
Why all the fuss over something that you use for 5-10 minutes when you flash a ROM, theme, etc.? How much time are you spending in Recovery?
The next thing you know people will want the "Download" mode to be themed and "prettied up" too.
Does anyone remember what it took to customize phones 4-5 years ago? Oh wait, this is XDA, I forgot it's the land of "gimme gimme gimme" and hardly ever about "thank you" or "how can I help you with that?". Users just want to be "alpha" testers so that they can have the newest, hardly do they ever upload logcats, dmesg logs, or help in troubleshooting.
-Daryel
Click to expand...
Click to collapse
Sure this is true of some but I get thanked all the time for the work I do. There will always be the gimmie gimmie gimmie people, no matter what your doing.
And yeah if I could theme download mode I probably would. Just the way I am.
graffix31 said:
I love using TWRP and goo.manager on my cm9 touchpad. So easy to use. Glad our amazing devs have more options.
Click to expand...
Click to collapse
For those who haven't seen this in action, its worth a look. It is nice to open up goomanager and see all of the latest ROMs and versions that are hosted in goo. You can select the ROM you want and the script flashes it for you and IT WORKS! It is very slick. I would love for a dev to take this on!
Would love to see a themed download mode
Sent from my SPH-D710 using Tapatalk
I have had my G2 for about 18 months and have been running into a lot of issues recently. I've decided to fix those issues by rooting & getting a new ROM installed. I'm a tech savvy guy, but have not done anything on the phone end due to not wanting to break whats working. I've decided to go with the Mimicry 1.3.2 ROM since the install process uses Aroma and is very straight forward. Before I pull the trigger, I just want to make sure I have all the steps clear so that I don't go "Oh sh**" in the middle because I missed a step. There's also a couple of steps that I'm not clear on. Here's what I researched:
-Root phone using HTC's bootloader unlocker
-Format phone's flash memory to EXT4
--What is the best app to do this with? Will my phone work with Gingerbread after I make this change?
-Download Mimicry 1.3.2 and Google Apps put the zip files on my phone (not SD card)
-Power off phone and then push the volume down and power buttons together and choose to install the ROM
-Answer prompts in Aroma (including installing WiFi calling)
-Flash Google apps
--How exactly is that done?
-Restart phone and start setting up apps again.
Does that look correct and is there anything that I'm missing? Thank you in advance for your help.
Well first off I would stay away from HTC official unlocked bootloader, its worthless and will give you headaches in the future
use the wiki to root, either follow the wiki in cyanogen or here on xda, if you even slightly tech savvy it will be easy
following that guide you will have clockwork recovery, but I suggest moving to 4ext recovery, among many reasons is the ability to format to ext4. Otherwise the next easiest way to format would be to flash a super wipe script with ext4 format written to it (just search xda and you'll find it easier)
Now after you are rooted with an engineering s-off hboot consider flash the .19 radio, not super important but many find this to have the best reception and battery life.
Next make sure your SD card is fat32, I also suggest an ext4 partition there as well (easily done through recovery) but skip the swap
Now feel free to flash mimicry, and may I add this is one other best ICS Roms for the vision, and blk_jck is a very helpful Dev as well.
Good luck, if you run into issues there will be answers all over xda, just search a bit, happy flashing!
Sent from my Nexus 7 using xda premium
Thanks
Thanks for the heads up on the HTC bootloader. I'll check out the Wiki on how to PermRoot my phone.
Mimicry, recovery, soft bricks, and new ROM
Agree with demkantor, the step-by-steps so painstakingly described in cyanwiki are your best bet.
Likewise, using 4ext in place of clockwork is also my recommendation, as I've used both now and
find the latter more polished and stable.
I recently rooted and updated for the first time. Got successfully as far as ICS using cyan's instruction,
then decided to use mimicry after reading about the radio updates etc posted by madmaxx. I think the sequence in which i
carried these out was flawed, because after updating the radio instruction sets, I re-flashed mimicry to take advantage of the
updated radio features and to install the wi-fi telephony; that was my downfall. I got caught in a boot-loop. Oh sh*t, indeed.
I could not, for the life of me, get past the HTC white screen. Being a total noob, I had no
idea where to go to next. I searched this website and cyan's a lot, and realised the term for what I now had was a 'soft
brick' or 'semi brick'. Could not get the device to be recognised via ADB, and could not access the sdcard directory.
I scratched my head for a few days (I had bought another phone prior to playing with the old G2), and came up with the
idea of just accessing the sdcard via my laptop, directly. In the midst of this, I turned on the phone (after taking the card
out), and voila, the phone now cycled into engineering hboot !
I subsequently was able to edit the sdcard directly via the laptop (using an micro sd card adapter), and removed the pc10?.img file
that was left over the radio update. Having recovered to this point, I re-flashed mimicry 1.3.1 (via 4ext) and so was able to get a completely
functional phone again.
The point of all of the is this: 1. To all the previous post-ers, both here and at cyanwiki...You guys rock. Can't say that enough. Even more:
2. A 'soft brick' may be anything but...a little bit of not-very-complicated experimentation afterward can pay off big time. Lastly, I tried
mimicry 1.3.2, but kept getting a heap of error messages. Needless to say, I was a bit spooked by the previous stuff-up, so I quickly reverted
to 1.3.1, which appears to be 100% stable (IMHO).
Cheers
1.3.2 adds few framework level changes and no device level changes. Definitely nothing that should cause errors or problems booting anyway.
Sent from my HTC Vision using xda premium
Good Info
timram said:
Agree with demkantor, the step-by-steps so painstakingly described in cyanwiki are your best bet.
Likewise, using 4ext in place of clockwork is also my recommendation, as I've used both now and
find the latter more polished and stable.
I recently rooted and updated for the first time. Got successfully as far as ICS using cyan's instruction,
then decided to use mimicry after reading about the radio updates etc posted by madmaxx. I think the sequence in which i
carried these out was flawed, because after updating the radio instruction sets, I re-flashed mimicry to take advantage of the
updated radio features and to install the wi-fi telephony; that was my downfall. I got caught in a boot-loop. Oh sh*t, indeed.
I could not, for the life of me, get past the HTC white screen. Being a total noob, I had no
idea where to go to next. I searched this website and cyan's a lot, and realised the term for what I now had was a 'soft
brick' or 'semi brick'. Could not get the device to be recognised via ADB, and could not access the sdcard directory.
I scratched my head for a few days (I had bought another phone prior to playing with the old G2), and came up with the
idea of just accessing the sdcard via my laptop, directly. In the midst of this, I turned on the phone (after taking the card
out), and voila, the phone now cycled into engineering hboot !
I subsequently was able to edit the sdcard directly via the laptop (using an micro sd card adapter), and removed the pc10?.img file
that was left over the radio update. Having recovered to this point, I re-flashed mimicry 1.3.1 (via 4ext) and so was able to get a completely
functional phone again.
The point of all of the is this: 1. To all the previous post-ers, both here and at cyanwiki...You guys rock. Can't say that enough. Even more:
2. A 'soft brick' may be anything but...a little bit of not-very-complicated experimentation afterward can pay off big time. Lastly, I tried
mimicry 1.3.2, but kept getting a heap of error messages. Needless to say, I was a bit spooked by the previous stuff-up, so I quickly reverted
to 1.3.1, which appears to be 100% stable (IMHO).
Cheers
Click to expand...
Click to collapse
Thanks for that info. I am taking a look at the Cyanogen Wiki and seeing what I have to do. I'm thinking that I will jump directly to Mimicry 1.3.2 instead of installing Cyanogen 9 first. Hopefully that file doesn't hang out there and causes that boot loop to happen to me (thanks for that explanation, BTW).
So do I have to use that ClockworkMod to load the ROM, or does EXT4 do the same thing (as far as loading the rom goes)?
...where thanks is due
many thx, blk jack, I should have specifically mentioned your awesome contributions as well, and
have remedied with thanks meter as i came/come across it.
Will re-try the 1.3.2 shortly. If I run in to the same glitches, I will try and make note of the specific errors
(or any other bugs, for that matter) and let you know.
Use the following guide, it is incredibly simple yet swift. Contains root methods for both the DesireZ and the T-Mobile G2 :
http://wiki.cyanogenmod.com/wiki/TMobile_G2:_Rooting
Checking it out now
iamnoobie said:
Use the following guide, it is incredibly simple yet swift. Contains root methods for both the DesireZ and the T-Mobile G2 :
Click to expand...
Click to collapse
I'm actually looking at that wiki right now. I just finished backing up all the contents on my SD card. I can't backup the apps on my phone since it's not rooted, and I can't use a backup app unless I'm root. So it looks like that is a catch 22. Personally, I don't mind wiping everything anyways since I'm going to be making the jump to ICS. I guess I'll have to beat all those levels in cut the rope again :crying:
@deadeye
actually, the only important bits are your contacts, sms's, phone logs, etc (if these matter to you), which i think you can backup via gmail. Additionally, any other (or all) files on the SD card, you should be able to just copy directly onto a folder in your laptop or desktop (see the post I made above). HTH.
timram said:
@deadeye
actually, the only important bits are your contacts, sms's, phone logs, etc (if these matter to you), which i think you can backup via gmail. Additionally, any other (or all) files on the SD card, you should be able to just copy directly onto a folder in your laptop or desktop (see the post I made above). HTH.
Click to expand...
Click to collapse
Thanks for that. I've now downloaded the Android SDK and am now trying to test the connection to my G2 using adb. So far, no connection. Grrrr. I'm looking around now to see how to get my phone detected by adb since it doesn't seem to have anything on the cyanogen wiki.
you downloaded adb.exe from within the sdk right? find the folder it is in (usualy platform tools) hold shift right click within the folder and choose open command here
now type adb devices, you should se some letters and numbers that means you good if not need to trouble shoot some more
alternatively you can change the path within enviromental variables so you can open a cmd anywhere
Sent from my HTC Vision using xda premium
HTC Sync
demkantor said:
you downloaded adb.exe from within the sdk right? find the folder it is in (usualy platform tools) hold shift right click within the folder and choose open command here
now type adb devices, you should se some letters and numbers that means you good if not need to trouble shoot some more
alternatively you can change the path within enviromental variables so you can open a cmd anywhere
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
I tried the adb devices command and it didn't return any connected devices. Looking in the xda wiki, they are saying that I need to have HTC Sync installed. I'm downloading that right now. They probably should put that in the cyanogenmod wiki also.
I got my phone detected by adb! I did some preliminary checking and I think I should be good to go on rooting. I think I will root my phone tomorrow when I have plenty of time to troubleshoot any issues that my come up.
This is just the thread I was looking for. I'm also an old (60) tech-savvy guy who has never rooted his phone, and was nervous about which set of rooting instructions (cyan-wiki or Setherio/Strawmetal?; the latter is more recently updated, seems a bit more detailed, and has newer versions of some utilities) which recovery, ClockworkMod or ext4, and which ROM, Cm9 unofficial or mimicry or even AOKP...
You all seem to feel cyan-wiki instructions better (right?) ext4 and mimicry... Shall I go for it? Last suggestions?
Thanks,
Dave
Sent from my T-Mobile G2 using xda app-developers app
prairie-dad said:
You all seem to feel cyan-wiki instructions better (right?) ext4 and mimicry... Shall I go for it? Last suggestions?
Click to expand...
Click to collapse
Cyan wiki worked for me! (strawmetal didn't - I blame myself though).
ext4 and mimicry are what I'm running now (after going through CWM, CM 7.2 and CM9 RC1 & RC2) and I'm very happy with both. Mimicry is great!
prairie-dad said:
This is just the thread I was looking for. I'm also an old (60) tech-savvy guy who has never rooted his phone, and was nervous about which set of rooting instructions (cyan-wiki or Setherio/Strawmetal?; the latter is more recently updated, seems a bit more detailed, and has newer versions of some utilities) which recovery, ClockworkMod or ext4, and which ROM, Cm9 unofficial or mimicry or even AOKP...
You all seem to feel cyan-wiki instructions better (right?) ext4 and mimicry... Shall I go for it? Last suggestions?
Thanks,
Dave
Sent from my T-Mobile G2 using xda app-developers app
Click to expand...
Click to collapse
setherios guide is just for the downgrade process
the cyanogen wiki, xda wiki, and strawmetals pdf guide are all more or less the same guide, just writen a tad differently
as for the recovery 4ext is far superior but feel free to switch recoveries later if it complicates thing, very easy to do
as for a rom choice there are many good ones and it will be hard to recommened one so try a few, make nandroid backups, and see where your prefernce lies. if you like ics then my personal opinions are elitemod ics or mimicry, both are great. don't care much for sense so you will have to explore by yourself on those (you will need the dz hboot if you want any sense roms - easily done)
if you want gingerbread try ilwt or elitemod cm7 (this is still the rom I almost always use, even curently)
have fun, read, read some more, search when stuck... this is should all be easy as you say your tech savvy - happy flashing!
Sent from my HTC Vision using xda premium
minor glitches, but rooted and s-off fine
demkantor said:
setherios guide is just for the downgrade process
the cyanogen wiki, xda wiki, and strawmetals pdf guide are all more or less the same guide, just writen a tad differently
as for the recovery 4ext is far superior but feel free to switch recoveries later if it complicates thing, very easy to do
as for a rom choice there are many good ones and it will be hard to recommened one so try a few, make nandroid backups, and see where your prefernce lies. if you like ics then my personal opinions are elitemod ics or mimicry, both are great. don't care much for sense so you will have to explore by yourself on those (you will need the dz hboot if you want any sense roms - easily done)
if you want gingerbread try ilwt or elitemod cm7 (this is still the rom I almost always use, even curently)
have fun, read, read some more, search when stuck... this is should all be easy as you say your tech savvy - happy flashing!
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
all went well till the very, very, very end. I went to reboot into clockwork recovery, and...nothing doing! holding down the trackball, volume down and power...and waiting and waiting...just got me into the bootloader with no option to go to recovery...just reboot, reboot the boot loader, and power down.
So I thought, maybe I somehow failed to get the recovery img where I wanted it...no big deal. I logged onto the old Market (this is 2.2, after all) and purchased 4ext (which is what seems to be everyone's choice) and installed it. Then I said I wanted to reboot with mimicry and gapps, hit "go," and...it rebooted into ClockworkMod Recovery...where it now sits, I assume backing up the existing system. Mimicry 1.3.2 and gapps images were sitting on my sdcard root, btw.
Very odd, and a little perplexing...I will wait it out a while before powering off and up again.
any thoughts? Must I remove clockwork mod manually (I assume that when I installed 4ext it made itselfthe default recovery method...) or does 4ext just sit atop Clockwork Mod...and what I am seeing now is normal...? I've been waiting a few minutes now, and see nothing but the Clockword Mod icon, the top hat.
Sigh...but pretty clearly almost all the way home.
Thanks to all,
dave
I've never used an app to install a recovery, always used fastboot.
But to answer your question 4ext does replace clockwork, it does not sit on top of it. Just downloading the app well... downloads the app. You must then go into the app and choose to download and install the recovery, after this from within the recovery flash your ROM (and gapps etc. If needed)
I have the 4ext app just for the purpose of supporting the Dev as anything that does me good deserves my money but I really have never bothered much with it so off hand I can't tell you the exact steps to do this but I'm sure it s very straight forward.
Good luck and let us know how all turns out
Sent from my Nexus 7 using xda premium
darn ClockWorkMod/4ext clash!
demkantor said:
I've never used an app to install a recovery, always used fastboot.
But to answer your question 4ext does replace clockwork, it does not sit on top of it. Just downloading the app well... downloads the app. You must then go into the app and choose to download and install the recovery, after this from within the recovery flash your ROM (and gapps etc. If needed)
I have the 4ext app just for the purpose of supporting the Dev as anything that does me good deserves my money but I really have never bothered much with it so off hand I can't tell you the exact steps to do this but I'm sure it s very straight forward.
Good luck and let us know how all turns out
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thanks...I sat and looked at it for a while, then hit power, and up came the ClockworkMod menu...and did nothing. When I asked _it_ to load a zip from the sdcard...it still sat there stupidly...nice menu but no action. so I rebooted with trackball/volume-down and power...and still can't get to the bootloader menu...the only way is to attach via usb, and do adb reboot bootloader...which gives me a bootloader menu showing no recovery app...just the same options as before. ugh. I wonder what the recovery.img is...? I went through the steps of installing 4ext...and it said it had installed itself.
well, I will poke around a tad more...midnight now...at least I have a working phone on 2.2, rooted, S-OFF, etc.
dave
---------- Post added at 07:33 AM ---------- Previous post was at 06:42 AM ----------
prairie-dad said:
Thanks...I sat and looked at it for a while, then hit power, and up came the ClockworkMod menu...and did nothing. When I asked _it_ to load a zip from the sdcard...it still sat there stupidly...nice menu but no action. so I rebooted with trackball/volume-down and power...and still can't get to the bootloader menu...the only way is to attach via usb, and do adb reboot bootloader...which gives me a bootloader menu showing no recovery app...just the same options as before. ugh. I wonder what the recovery.img is...? I went through the steps of installing 4ext...and it said it had installed itself.
well, I will poke around a tad more...midnight now...at least I have a working phone on 2.2, rooted, S-OFF, etc.
dave
Click to expand...
Click to collapse
Mimicry is booting now. All good. I ended up using the clockwork mod version, 3. something, that I installed when following (too slavishly?) the CM wiki's instructions (otherwise excellent!) Then (and now) I have problems booting into the bootloader, and it doesn't show a recovery option... Running 4ext (which I purchased) seems to be great (looks really useful) until rebooting...when CWM comes up instead.
I kept using volume up or down to pick what I wanted, then pushed the power button to select...wrong! It's the trackball you click, which I only hit upon by accident. Once I got that working, I flashed mimicry and Gapps, and I am off to the races again.
Thanks to all, but I want to figure out what is with recovery for the future.
What buttons do I push to get to bootloader...so far all I have gotten to work is via USB cable and "dab reboot boot loader."
dave
Three times now I have bricked my Samsung S3 (SGH-T999) by flashing a new Rom that should work ok. I flashed my recovery with Multiboot v2.11 (http://forum.xda-developers.com/showthread.php?t=2684052). Booted into Recovery, created the new Rom, selected the new Rom, installed the new Rom and attempted to boot into th new Rom. at that poin t my phone went dark, it would not power up no matter what I did. Plugged in I would see the object "qhsusb_dload" in the Device Manager (Windows 7). From there I learned it was bricked. I have been able to recover in all instances
Can anyone possibly shed some light on what might be going on??
Thanks,
Robert
First thing I'm noticing is you are using multi boot for the I747. Probably doesn't matter much but you really can't know for sure. We gave our own multi boot thread btw.
The only other thing is the roms. You need to tell us exactly what you flashed, how you flashed and what recovery you used. (Links can be a big help so we don't have to spend extra time verifying that we understand correctly which ones you are referring to.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
DocHoliday77 said:
First thing I'm noticing is you are using multi boot for the I747. Probably doesn't matter much but you really can't know for sure. We gave our own multi boot thread btw.
The only other thing is the roms. You need to tell us exactly what you flashed, how you flashed and what recovery you used. (Links can be a big help so we don't have to spend extra time verifying that we understand correctly which ones you are referring to.
Click to expand...
Click to collapse
Doc,
Thanks for your reply. My phone is a Samsung S3 (SGH-T999 T-Mobile). To start with, I already had TWRP 2.8 installed.
I followed this link for a starting point: http://forum.xda-developers.com/showthread.php?t=2646528
Recovery File: https://www.androidfilehost.com/?w=files&flid=12831 (d2tmo-twrp2.7-mb-v2.11.zip)
Flashed the new Recovery from the old recovery. No problems installing or using the new recovery.
I had tried Android Revolution HD from (http://joyofandroid.com/10-best-custom-roms-samsung-galaxy-s3/) and soon realized that was for the i9300. Needless to say that bricked my phone the first time. Flashed everything back to stock.
Next I tried FlashingDroid from the same link as above with the same results.
In the Multiboot TWRP 2.7 I would simply do the following:
- Create the Rom Space using the img option
- Set the Rom to the newly created space.
- Flash the new Rom.
- Set Boot to new Rom.
All seemed to go ok, but when it rebooted it was bricked. My phone would not power on either on battery or plugged in. When plugged in I would see an unloaded device named "qhsusb_dload". From what I briefly read on that, it is a very distinct indication that your phone is bricked.
From that point I would image my sd card with a debrick image, reboot into download mode and reflash back to stock...
If there is a better way, please direct me to the correct docs.
Thanks,
Robert
I tried yet again from a fresh flash with the same results. Somethings not right can anyone shed some light on what I might do to be able to use this Multiboot option?
Robert
Never heard of "FlashingDroid" but it is also an i9300 rom. The ONLY roms you should be using are ones in our Development and Original Development sections. Everything in our forums here is as safe as your going to get. (There's always some risk when flashing). I highly recommend Against flashing anything from any other site or Google search.
I didn't look to verify, but I'm betting every rom on that page you linked is for the i9300. Pretty much every time you see something about the S3 online, they are talking about the i9300. They will specifically refer to the model number and/or carrier otherwise.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Doc,
What I really do not understand is how this is bricking my phone. One would think if I reset the Multiboot options back to Internal away from the new Rom I created that it would still be able to boot my original Rom? Isn't that one of the reasons to have a Multiboot feature?
Robert
I'm not completely sure on that one tbh. I do know that just because it's not internal and it's on your SD card, those i9300 roms are not going to work. (I don't use multi boot so I'm not really well versed on how it all works, but if it has to symlink partitions for example, when you try to reboot to the internal rom it would need to reset those links, but if they are linked to the wrong partitions, it probably wouldn't boot at all. Keep in mind that is more a guess, but the logic seems right to me.
Bricks occur because when flashing an i9300 rom, it flashes the kernel to the wrong partition. (One of the bootloaders if I remember right). So if it does operate using symlinks, it'll try to access the bootloader and will get redirected to the i9300 kernel resulting in the inability to boot.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
I never heard of multiboot what is it? Is it like a custom recovery. By the way I heard the best custom recovery that is really safe is ClockworkMod you can even flash it as a zip so that it isn't permanent. Bit I'm using it and I haven't found anything wrong with it so far. It even tells you when the ROM isn't the right one for your phone. (Status 7) so that you don't brick your phone.
Just wanted to give you a heads up.
Sent from my SGH-T999 using XDA Free mobile app
I highly suggest reading all the stickied threads for starters. Multi boot has its own thread in development. Cwm is not the only recovery, none are permanent (in the way I'm guessing you referred to it) and all will throw status errors when necessary. All the recoveries are good. Just comes down to personal preference.
Sent from my SAMSUNG-SGH-I747 using Tapatalk