I haven't found any solutions to my problem on here, so I figured I'll have to try and make my own solution. Basically I want to take the MT3G stock, vanilla, retail COC10 build, and add root and tethering. That's the probably number 1 requested feature that people want, and I'm trying to find the solution for at least myself, if not to help others. I don't want all the extras and, no offense, garbage that is in all these other ROMs. I understand there's a need for that for some people, but I'm looking for just a clean, retail image for my MT that is very similar to the JF builds. Add root and netfilter/iptables. I'm aware JF added other things, but I don't want those. So here's my ideas for a solution...
I've got an obsession with this new 1-click Root program. I was able to get Cyanogen's 1.4 Recovery on my MT3G without flashing anything else, it's quite a nice trick for now. I've downloaded the original MT3G shipping COC10 image/update.zp and know that as long as i'm not off flashing Radio and SPL i'm pretty much safe. I did a nandroid backup anyway.
I'm going to for the first time try and dabble in ROM development/tweaking. I found in a thread on here someone mentioned how easy it was to add root on the stock ROM. Link to that particular post: http://forum.xda-developers.com/showpost.php?p=4333604&postcount=38
I haven't tried that just yet as i'm on a PPC Mac so no easy way to do it except trying VirtualPC with XP which isn't perfect. So, here starts my questions...
If the assumption of a "rooted" recovery image could work to put the SuperUser apk in, I should be able to do this, right? Again, remember I'm on Cyanogen's 1.4, but still have my stock, retail myTouch COC10.
Most of the commands listed to do over the ADB could probably be done in the recovery's console, correct? I will have no computer to do anything today, but I will have VNC/RDP access to my Mac with VPC/XP to do anything that may require a computer to compile. I figure then i can package it up and email it to myself, should I need to do that.
Now if that takes care of the root half of what I'm doing, how about the tethering... I understand haykuro has compiled a kernel that pretty much everyone is using in their ROMs that has netfilter enabled in it. How would I get access to that particular kernel so that I could use it as say a simple Update.zip much like the one for the Dream/ADP/G1 that is here: http://code.google.com/p/android-wifi-tether/wiki/ADP15KernelUpdate
If that is something in these forums, I haven't found it yet. So please, point me in the right direction. Assumably, with a kernel update and the root added, I would have everything I need, right? I'm not saying I want to break into the MT3G official update and start compiling it as an all-in-one ZIP that could be easily flashed to. That's out of my knowledge. But I would like to at least have the steps so that maybe it can be reproduced for the (apparently) minority out there that would like to stay as vanilla as possible.
UPDATE:
Okay, so I found a boot.img here (http://cluster.physik.uni-freiburg.de/~kuhnen/android/android.html) and I thought to myself what exactly IS the boot.img? That's not the SPL, right? or is it? Is it just the kernel? I never thought about it before, I was always flashing it, but never knew WHAT it did. If the file I found that is for vodafone works fine with the myTouch system, then I may have solved the other half of my problem. Seriously, anyone able to help? Or at least let me know what BOOT.IMG is.
Or even better yet, can't I just yank the BOOT.IMG/kernel out of haykuro's ION R2? Is it a hard task to do that? I would assume that the Ion was just the myTouch rebranded before the myTouch came out. So the kernel couldn't have changed much, if at all, since then. And since haykuro did enable tethering on that kernel, I could assumably use that, right?
Related
Here is a version of JF's RC33 1.41 without the multi-touch kernal included.
This one is JF's RC33 build modified with the PRE-MT kernal (1.31). It includes all the goodies that are standard with JF's builds and was recompiled from his source. This update does include the 1.41 recovery image.
ALL CREDIT GOES TO JESUS FREKE for providing us with the source for his modified ROM's
If you are interested or do not know what JF has added to the original images check this link
Just like JF's RC33 build this does not include the radio update which can be found here(MD5:CF8714D273FB0274574D9E3831E11FDD) this will need to be flashed separately in any order. To revert the radio you WILL NEED TO FLASH BACK TO RC29 THROUGH THE DREAMIMG.NBH file that can be found here
RC33 PRE-MT Kernal (MD5:97167BFDD7957F4D95C1538410003146)
http://drop.io/qyyqvmd#
*UPDATED* RC33 PRE-MT Kernal 1.42 Recovery image, No Amazon MP3, No Stock Email, no Term Emulator (which can be downloaded from the market, the author has been making changes so I didn't want to include it)
http://drop.io/689ghtm#
(MD5:F1B80E314926C7409DDCA6C0EE107626)
Save the zip file to your sdcard named update.zip, boot into recovery mode (home + power), and then press alt+s. I must recommend that you also do a wipe in recovery mode (alt+w) before applying the update as most of the esoteric issues that arise seem to be from not wiping. This will clear all your data/settings/apps, and you will have to re-register once it boots back up.
Again THANKS JESUS FREKE
Cool thanks for this, glad to see it worked out.
Do you think I would need to do a wipe going from mt rc33 to no-mt rc33?
Doesn't seem like such a large zip is necessary.
Does the MT really alter so many files?
Hopefully there will be a mini version that does the same thing
Only the Kernal is changed so if you want you can extract the boot.img and use the flash_image tool to re-image it over your current one. JF has a thread about the flash_image tool and how to use it at this link
The reason it's so large is because its a full ROM you can flash from RC29 etc. You could probably get away with not wiping but I have to recommend it since 90% of the issues people run into doing the updates seem to end up with a wipe so why not skip the issues. Its easy so re-sync contacts and reload apps.
Hahha thanks, so then the only diff is in the boot.img? Cool.
So I could just switch boot.img's and flash whenever I want to switch between normal and MT?
Ima try it righttt now
Any chance for a ADP1.1 No Multi-Touch ROM? Please?
why would any1 one want it without the multitouch?
Because of few problems with the MT version.
I just used fastboot to flash the image nd I gotta say, touch is workin great.
I like it better this way for sure.
Im gonna wait til multitouch gets fixed up and then ill try it again.
Thers is any "problem" with the multi-touch except that devs are not making apps for its kernal. Therefore some apps may act funny.
I personally don't use the MT at all so I don't want it throught the OS. And I don't know if its in my head but the pre-MT kernal seems to give me better battery life.
topdnbass said:
I just used fastboot to flash the image nd I gotta say, touch is workin great.
I like it better this way for sure.
Im gonna wait til multitouch gets fixed up and then ill try it again.
Click to expand...
Click to collapse
Good to hear. Flashing the boot.img is really all that's needed but I wanted to make a full update just for the exercise etc since this is fairly new to me and fastboot might be more difficult for some.
Yeah It's not really a problem.
I figured it's good that both ways are on here now though.
Thanks again!
If youre already running jf rc33 do you need to do a wipe?
Ah, apparently I didn't announce mine with enough fanfare
Oh well, it is a fun exercise.
Uh, and so why would I ever want or need this flash? Dead thread. Nothing added and of no value.
But nice try. Must really like your iPhone and your paycheck...
learningmore said:
If youre already running jf rc33 do you need to do a wipe?
Click to expand...
Click to collapse
you will probably be fine without a wipe but i recommend wiping when flashing
quietlurker said:
Ah, apparently I didn't announce mine with enough fanfare
Oh well, it is a fun exercise.
Click to expand...
Click to collapse
Glad you got the issues worked out as well. not trying to be disrespectful or anything but I told people i would make up a ROM so i did and figured it might as well have some instructions in case someone needs them. I did see that you had put one up but at the time thekills was complaining about the browser so I went ahead with my version.
and it is a fun exercise
Edited:double post
justanothercrowd said:
you will probably be fine without a wipe but i recommend wiping when flashing
Click to expand...
Click to collapse
Ok i flashed without wiping everything is running good. Phone is much more responsive touch wise. Everything else still works great. Thanks to you and JF
Gadzks said:
Uh, and so why would I ever want or need this flash? Dead thread. Nothing added and of no value.
But nice try. Must really like your iPhone and your paycheck...
Click to expand...
Click to collapse
There were request from a number of people for a non multi-touch version. If your not interested simply don't use it.
And as for the other comments....lol
justanothercrowd said:
Glad you got the issues worked out as well. not trying to be disrespectful or anything but I told people i would make up a ROM so i did and figured it might as well have some instructions in case someone needs them. I did see that you had put one up but at the time thekills was complaining about the browser so I went ahead with my version.
and it is a fun exercise
Click to expand...
Click to collapse
No worries. If you keep updating your branch in the future, you may want to be sure and change the ro.modversion in the build.prop file.
I'm not sure where to post this thread, I'm picking here because I believe if I can be helped, it'll be by the people here. This morning I followed the guide posted by Haykuro to get "real" root on the Rogers. However, I made the most basic mistake of noobdom and didn't bother to check that this was for my phone. It's not, it's for the Dream. I can still boot into fastboot, but through the guide I flashed the new radio which I think is completely incompatable with the Magic, so to start, could someone post the original Rogers radio? Please don't clutter up the thread with "ur an idiot" type posts, trust me, you can't possibly call me anything I haven't called myself for the past half hour. I want to punch myself in the face, but I'm a bleeder.
Here is the post http://forum.xda-developers.com/showpost.php?p=4271500&postcount=1
Here are the SPLs. But I'm not sure that will help you out, I think you may have to send it in.
Clinton
Thanks, I don't think those contain radio.img though, unless I'm wrong?
If you can still get into fastboot your best bet is probably to restore a nandroid backup from someone's untouched rogers handset.
that should fix everything and reset your phone to how it was.
I have the wiped nandroid backup posted by Skittleguy on my computer, so I'll try that in a few and post my results shortly.
Restoring the Wiped Nandroid Backup didn't work, I don't think that it's updating the radio, which is why I think that if I flash the original radio back first and then do the tutorial again using a Magic recovery, that I might be okay. I'm just thinking out loud here though.
So wait, do you own a Rogers Magic (32A)? If you do, then it should work (using it right now as a matter of fact). Just make sure that you use a 32B compatible recovery.
What should work? The wiped nandroid backup?
Reflashing the radio. From what I understand, this root method essentially turns the Rogers phone into a "32B" Magic. You still have all the memory and goodies, but you should now be able to flash any 32B rom onto your phone. And for that reason, you need to use the 32B compatible recovery and then you can flash any 32B rom.
And for future reference, Nandroid does not back up your radio. To the best of my knowledge, there is no way of getting the Rogers radio unless you probably do some hardware modding.
Edit: Post 100!
Alright, I'm flashing a 32B Rom as we speak.
Okay, my phone flashed, and it's working just fine with a 32B Rom. Although now, I wonder what I did, because it wouldn't boot before. In the mad dash that has been the last hour, I'm sure (obviously) that I did something wrong, but I don't know what. Thanks everyone for your replies, and Skittleguy especially thank you for verbally slapping me back into reality! Mod, you can lock this thread down.
I noticed that no one has set up a guide in this section on how to un-root and restore to factory for Warranty return/exchange purposes.
Below is a guide for the 1.29 Original:
http://theunlockr.com/2009/10/03/how-to-unroot-the-htc-hero/
Here is the Factory Restore for the 1.56 ROM:
http://forum.xda-developers.com/showthread.php?t=608434
Untested Theory:
Restore original Nandroid that you made after you first rooted your phone, that should put you at
a rooted 1.56
Then RUU to 1.56 and you should be factory.
Do not RUU from 2.1 to 1.56 because you are more likely to have issues.
If you can't deal with the minor bugs that are in the current DamageControl v2.0r2 then you might want to RUU restore, however I would suggest to wait it out because an offical 2.1 update might have to be rooted differently than what we have now. I prefer the Dev route.
I'm lucky that I didn't flash a custom ROM that wasn't a Sprint build, so my PRI didn't get messed up but if you did then go here, from dfbonney:
http://forum.xda-developers.com/showthread.php?t=654119
The posts below should also help understand how all this stuff has been gathered.
Most of us dont need a guide since we know that if we use RUU will restore the phone to un-rooted factory settings...
The Nandroid back up you make after your root will capture Root stuff, since it is done after the fact.. so it restoring the nandroid will not unroot (is that a word?)
Only way to unroot is with RUU, some people have an issue (50/50) after you flash the Flipz Radio update. Though it could be linked to running a 2.1 Rom and trying to RUU with 1.5.
I do belive they found a way to reflash each of the partition images individually and bring the phone back to life.
Let's do this!
Darkshneider said:
Most of us dont need a guide since we know that if we use RUU will restore the phone to un-rooted factory settings...
Click to expand...
Click to collapse
Kcarpenter thanks for pointing out what I asked. The above mentioned by Darkshneider is obvious as a stand alone quote but in the case from 2.1 back to 1.5 there may or may not be issues, how to be certain?
I would like this thread to help people who are having problems revert back to something functional in the event of a failure or a freak development like the PRI mismatches that have been happening. I know people here are supposed to be "DEV" savvy but not everyone is at the same experience level.
Let's try have as little guesswork as possible involved and try to get things in order. I don't think that's too much to hope for.
I'm fairly certain my post can help those who've bricked their devices... it should be stickied or in the same post...
http://forum.xda-developers.com/showthread.php?t=654119
GURUGTS said:
Kcarpenter thanks for pointing out what I asked. The above mentioned by Darkshneider is obvious as a stand alone quote but in the case from 2.1 back to 1.5 there may or may not be issues, how to be certain?
I would like this thread to help people who are having problems revert back to something functional in the event of a failure or a freak development like the PRI mismatches that have been happening. I know people here are supposed to be "DEV" savvy but not everyone is at the same experience level.
Let's try have as little guesswork as possible involved and try to get things in order. I don't think that's too much to hope for.
Click to expand...
Click to collapse
If you are asking what issues are there if you go from 2.1 back to 1.5? Well, the only one I ever had was with the market not letting you see Protected apps. This was a bigger pain than I thought it would be and the fix is a little tedious.
Some people have issues with restoring Nandroid's, but I believe that is usually because they are running low on SD Storage space for the Nandroid to expand as it is copied to the phone.
The PRI Stuff shouldn't be a HUGE issue, unless you want to use Sprint TV and Navigation and those Sprint Apps. Persinally I hate Sprint TV, picture is to fuzzy and the way they break the eppisodes into 5.5 minute clips gets on my nerves. Then they want you to pay for the good cartoons...bastards!
I think Google Navigation is just as good as Sprints...minus the Voice and the interface isn't as pretty...but Ill take it.
Will restoring with RUU also put the original dialer taskbar and anything else you changed back??
redlinethecar said:
Will restoring with RUU also put the original dialer taskbar and anything else you changed back??
Click to expand...
Click to collapse
Si. Oui. Ja. And Yes.
I noticed there is a guide on fixing the 110 error and a guide on how to unroot using your sdcard but not a general one covering the basics of unrooting with the RUU.
This should definitely be written up all in a post and included in the guide wiki.
i agree so users like me won't annoy people with thousands of questions when I need to get it done lol
redlinethecar said:
i agree so users like me won't annoy people with thousands of questions when I need to get it done lol
Click to expand...
Click to collapse
lol, noobs asking questions that are readily availble will never stop, at least the wikis give us a single location to direct them to...
Welcome to XDA redline!!
Please ask away, search first but if you can't find something we are here to help!
Hello XDA community, I'm sort of a noob when it comes to advanced things such as radios and kernals etc. I have a rooted HTC Aria S-On running CM7 but that's basically all I know how to do is easy simple things like what I've done to my Aria. But the issue is a friend of mine was trying to update his HD2 to an ICS ROM but (according to him) he wiped everything down to the MAGLDR. Radio, kernal, ROM etc. He basically has no idea what he's doing with it, most experience with this kind of thing he's had is clicking a button to jailbreak an iPod or two. What I'm trying to do is figure out how to get the correct radio and kernal for the phone, and install ClockworkMod recovery and CM9 on it. Any help would be appreciated
follow the guide below, should be what you're looking for. Mind you this is assuming your NAND and not running it from the SD.
http://forum.xda-developers.com/showthread.php?t=1044830
Many thanks man, didn't find that thread during my searches. One more thing, Nandroid isn't installed anymore either, would that be just a simple search for a DL link for the HD2 and install through the USB flasher in the MAGLDR?
yeah it should be, if I'm understanding you correctly...worst case I would just go from start to finish from the guide below so I don't leave anything unturned. Follow this guide before following the the previous one (that one assumes you did this already).
http://forum.xda-developers.com/showthread.php?t=893948
Thanks again, happy I can return the phone without it being a $200 paperweight
lol no problem
I am trying to attempt messing with this type of thing for the first time so noob handling will be required. My reason is simply my phone is a nice wallpaper display three days after the ota from tmobile 1.63.531.2 710rd.
I began by trying to follow:
http://forum.xda-developers.com/showthread.php?t=1505999
To no avail. Of course I noticed afterwards that for some reason it says to turn s-on in the header... exactly the opposite what what I need to flash the phone back to (PG59IMG_Doubleshot_TMOUS_1.28.531.9_Radio_10.48.9007.00U_10.12.9007.07_M2_release_201815_signed.zip) I have had problems with the phone ever since its first ota a year or so ago. With this latest ota the phone is more or less bricked as of the phone using power saver when I went to sleep last night... Wont call or check into the network...no dial tone. Took me 3-4 restarts for it to even show the antenna symbol and the 4g icon in the taskbar.
My phone is set as S-on for now. The only instructions I have found through the search tool relay how to do it to the sensation... I believe that is the mytouch 4g not slide. However I have the slide which is doubleshot. So my question is, is this instruction on http://forum.xda-developers.com/showthread.php?t=1192300 safe to use with the doubleshot since the (T-Mobile branded HTC myTouch 4g Slide ( doubleshot ) Developers Reference) page links to it indirectly. Using the link at the top of the how to S-on after s-off... again the opposite of what I need so I tried following the link at the top of that page " Guide to Installing S-off, Unlocking, ClockWork, Root, SuperCID & S-on " which takes you to the s-off instruction page for the sensation (Link: http://forum.xda-developers.com/showthread.php?t=1192300 )...I am guessing that it will work and sensation refers to HTC sense, but I don't care to make the mistake of doing it wrong and bricking my phone due to being derp.
I know there is a bit of overdone explanation and redundancy in the addresses I have left here. I am just trying to cover all my bases thanks for the help in advance.
The short and sweet is I need a link by link list with instructions on how to step my phone back for multiple reasons. First the recent OTA more or less broke my phone and I don't want a refurb phone with inferior parts from Assurion...(They were in class action lawsuits for this in the past.) nor do I want to pay 130$ for said replacement. Next from what I just read the 1.63 update has some serious security compromises that are awaiting response from HTC for an update. Basically it gives full accesses to all your data to include your sim and SD card contents to all apps. Regardless of user specified/agreed permissions.
Following ANY routine or procedure for another phone is just too dangerous & will never work anyway. The bad part being you may very well create a brick in the process. If you have the MT4G SLIDE, this is where you will get all that you need so don't even consider other threads.
Since you've done the OTA & are sitting at Hboot 1.63.XXX now you will HAVE to get S-Off before you can go back to your previous Hboot. To DO that you will have to follow the instructions HERE.
If all you are wanting to do is start flashing ROMs, then the instructions you need are HERE.
Keep us informed & we'll try to help if you need it. Good Luck!
WeekendsR2Short said:
Following ANY routine or procedure for another phone is just too dangerous & will never work anyway. The bad part being you may very well create a brick in the process. If you have the MT4G SLIDE, this is where you will get all that you need so don't even consider other threads.
Since you've done the OTA & are sitting at Hboot 1.63.XXX now you will HAVE to get S-Off before you can go back to your previous Hboot. To DO that you will have to follow the instructions HERE.
If all you are wanting to do is start flashing ROMs, then the instructions you need are HERE.
Keep us informed & we'll try to help if you need it. Good Luck!
Click to expand...
Click to collapse
Thanks for the hasty post reply any other suggestions...I have win7ult 64bit. Or will will juopunutbutter work even though they have the below disclaimer?
"Supported Operating Systems:
We only support Windows 7 32bit or Ubuntu 12.04 (and newer) 32bit, you may use a LiveCD if you have the wrong OS installed natively. Win XP 32bit might work for you but we do not support it as we did not test on it."
Also, this, "Be on the Stock RUU and be rooted (have superuser flashed). No other ROMs are supported, Fresh ROM will not work regardless of what you have read elsewhere."
-I am not rooted. Which is something else I want to accomplish so I can set up firewalls that block certain things.
Oh btw provided I can get this phone working again I am also going to attempt to reflash my older mytouch 3g... back to original as well that thing worked better than any of the current phones for my purposes before it got the update prior to the 2.2.1... the original update didn't work with adobe which is fine with me, people need to move on from adobe's garbage anyway. Specifically with the old mytough 3g though that really did add functionality at the sacrifice of sanity since it slowed the phone down so much. On that note though I may just put on a custom if I can get comfortable with this stuff. The last time I looked at a pc this hard was back in win98se when you had to know how to do tricks to make it faster like modifying available rame to twice as much above and below physical ram and a few other tweeks I have long forgotten.
That brings me to another question. If I go custom rom and unlocked this looming threat of brick is weighing in on me. If a phone is bricked is it possible to recover using some of the same tools that bricked it in the first place... flash install original rom as a fix? Just trying to see how much margin of error I have to work with.
Thanks again.
PS who do we talk to about backing off all the java on the site since it is so compromised right now? This sight has more java permissions than most sights of ill reput... though I have been reading these forums off and on for a while so I trust it more than most with this much tracking. I doubt patch 11 actually fixed the issue...since the day before they said it would take two years or more to actually resolve the java zero day exploit.
You should be fine with your pc, I used a 64bit win7 too. If you're worried dual boot linux.
Your my touch 3g is rooted diferentley, go to that forum for details, its not true radio soff but its close enough.
If you brick it its dead, depending how it was bricked jtag could bring it back to life or this phone is part of the unbricking project which will fix some other bricks. Problem is people use brick as a term that means a whole lot of things so its hard to answer. Usually a brick is forever dead, most people don't actually brick their phone though and usually have to be neglecting things to do it.
As for java... just read up on a bunch of trustworthy places for more info and understanding
Sent from my HTC Vision using xda premium
I'm afraid I just don't know about Win 7 64bit and how it will react but I'm sure there has to be a person or two around with experience concerning that OS. It may very well work fine. I CAN tell you that the "wire trick" (junoptobear?) will work fine on MikTouch because that's what I used. It's a stripped down GB stock ROM which is all you're really looking for. Why....I don't know.
As far as bricking goes, there's not a GREAT deal to worry about as long as you follow all instructions to a tee. You REALLY don't have to even have S-Off to flash ROMs as you read in that link. You just need to flash the kernel after you flash the ROM. It WILL limit a few things you can do but not ROM flashing.
When it comes to rescueing a bricked device though, there are only a very few instances that can be done as far as I know. But I'm no developer either. But if you can make it to your bootloader and/or recovery you not bricked. It may be a hardware of software issue but most of the time you can come back from those.
As far as the Java issue you spoke of goes, you may be able to get an answer to that one by PM'ing one of our moderators or admins.
I want to step it back to previous versions because they worked better...primarily the first version... Also, I am not seeing a guide that refers to doing it to the 1.63 patch. keyboard hasn't swyped right since the first ota update. Also my intent is to root an older version so I can remove crapware like dt sync, friend stream, kidzone, tmobile mall, tmobile tv, tmobile setup, telenav gps, and zinio reader.
X-Lander said:
I want to step it back to previous versions because they worked better...primarily the first version... Also, I am not seeing a guide that refers to doing it to the 1.63 patch. keyboard hasn't swyped right since the first ota update. Also my intent is to root an older version so I can remove crapware like dt sync, friend stream, kidzone, tmobile mall, tmobile tv, tmobile setup, telenav gps, and zinio reader.
Click to expand...
Click to collapse
It's a simple flashing process but you HAVE to achieve S-Off first with the "Wire Trick". You can flash it forward without S-Off but not backwards. Does it work at all or is it just frozen to some point in the boot process? Can you access your SDcard? Can you boot to Hboot & recovery? These are a couple of things you will have to be able to do to go forward if I understand you correctly.