Related
Did you flash Haykuro's radio to be able to run those great 32B roms on your 32A Magic? Do you want to be able to undo this and revert to your good old 32A radio?
How :
- Download and unzip this (md5 : 5C6DA74ECB33E8AF0116E06763B63467)
- Boot into spl and fastboot
- Type in the following:
Code:
fastboot flash hboot hboot.img
fastboot flash radio Radio_HTC_PVT_32A_3.22.20.17.img
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash recovery recovery-RAv1.2.0H.img
- POWER OFF (not reboot, power it off) THE DEVICE. (you can do this using the corresponding button [it says it on the screen] or just pull the battery [make sure everything is done flashing of course])
(if you don't boot into recovery or accidentally rebooted, just pull the battery [if you notice top left it should read "FASTBOOT" or "FASTBOOT USB" if it's plugged in] you're not bricked, you just need to access recovery, not standard boot ;P)
- Hold down the HOME button and power it on, you should boot into recovery mode.
- Wipe data/factory reset
- Flash your 32A rom/restore an 32A nandroid backup.
It works! Thank God! All the 32B roms were working like crap for me. Thanks much for all the hard work!
I had the same feeling ^^
I'll wait for the 32A kernel source to be released so I can add tethering etc. myself.
skittleguy said:
It works! Thank God! All the 32B roms were working like crap for me. Thanks much for all the hard work!
Click to expand...
Click to collapse
from that comment i guess you answered a question of mines in the other thread. so going to the 32B roms had lotta problems, bugs for our 32A
NguyenHuu said:
from that comment i guess you answered a question of mines in the other thread. so going to the 32B roms had lotta problems, bugs for our 32A
Click to expand...
Click to collapse
Yes. Very, very much so. I tried a few 32B ports and noticed alot of lag. I also noticed that you could flash Dream roms, but again, the lag and unresponsiveness (and home screen reboots) made it a hair-pulling experience.
My advice: don't bother.
Thank you!!
shouldnt the roms be working faster as they are designed for 32B (less ram), and 32A has 288mb....
so overall, shouldnt the device perform faster?
zidane said:
shouldnt the roms be working faster as they are designed for 32B (less ram), and 32A has 288mb....
so overall, shouldnt the device perform faster?
Click to expand...
Click to collapse
I "think" that you will only be able to use 100mb of your RAM.
To be confirmed by someone who did the "downgrade".
oh i didnt think of that
that does make sense unfortunately!
waiting for someone to confirm...
Thanks so much for this Amon_Ra. I had problems (understatement) with the other ROM's, Cyanogen's stable 32B port worked okay, but even that was pretty slow on my phone. I'm happy to be back running your 32A Rom.
Thanks Amon_RA. Your ROM is far faster than any of the 32B versions out there, even with Compcache and all the other stuff turned on.
Great work and looking forward to your next ROM version!
Here's a bit of a silly question, but is the hboot for this method modified, since its 2009 but allows Nandroid restores? Or was there a change in the recovery that allows it?
is this loss of ram reversed by switching back to the first radio?
rajeevsudra said:
is this loss of ram reversed by switching back to the first radio?
Click to expand...
Click to collapse
Yes. Running my phone with my original Fatal1ty Hero port, and it's still fast as ever.
I'm just wondering, but what is the total amount of memory actually available to a 32A phone? Sorry if it's a stupid question, but I'm just paranoid over whether switching from radio to radio has diminishing effects over memory
xsupernoob said:
I'm just wondering, but what is the total amount of memory actually available to a 32A phone? Sorry if it's a stupid question, but I'm just paranoid over whether switching from radio to radio has diminishing effects over memory
Click to expand...
Click to collapse
on my 32A the actually available memory is:
MemTotal: 197144 kB
Physical memory is 288MB, memtotal gives you the ram available to linux kernel.
In this case, switching the radio rom implies switching the used kernel.
The kernel for 32B initializes the ram memory size which is available on those boards, which is 192MB total, hence the almost 100MB less memory available to running kernel and applications.
daldroid said:
on my 32A the actually available memory is:
MemTotal: 197144 kB
Physical memory is 288MB, memtotal gives you the ram available to linux kernel.
In this case, switching the radio rom implies switching the used kernel.
The kernel for 32B initializes the ram memory size which is available on those boards, which is 192MB total, hence the almost 100MB less memory available to running kernel and applications.
Click to expand...
Click to collapse
Okay, thanks! It seems like my phone has recovered all of it's memory
Thanks for the recovery radio Amon_RA
I cant wait for you to make tethering possible when they release the source
Hurrrrryyyy upppp
Why wont they release it already ?
Oh wow.. I didn't even realise people were flashing radio on their 32A's in the first place!
I am trying to root my mytouch and I cannot get it to work. I tried the goldcard method and it will not come up with the serial number when i try to pull it up in the cmd prompt under adb devices. IVe been trying for a couple hours looking at all these threads and nothing is working please help!
It would be very helpful to specify your exact model of the MT3G as well as the information displayed on the FastBoot screen.
I have the
32b
hboot -1.33.0006
radio 2.22.23.02
Its the mytouch 3g(not 1.2 or fender edition)
What SPL are you trying to flash, the 0006 is a perfected SPL, so you'd need to downgrade to say a 2005 Engineering SPL.
By the way, when it comes to goldcards its important to know that not all SD cards are compatible, if one fails to mount after the hex process, then you may just have to try a different brand/model of SD cards. (Kinda like how I would have used my 1GB as a gold card, but it wouldn't work, instead had to use my Sandisk 4GB).
Also what threads/procedures have you been trying to follow thus far?
Honestly I have no idea how to downgrade the SPL, I was looking at every post to crate the goldcard and None of them are working for me. Im not even getting to the point of where i can do any hex editing. It will detect the device under the fastboot through command prompt, but when i try to make sure I get the serial number under adb devices it will not work.
Hrm refrain from trying anything til I find a resource link. You may just need to have a single guide from scratch.
Which android is on the device btw (1.5, 1.6?)
K, based on the thread here : http://forum.xda-developers.com/showthread.php?t=649281
Should give some tips on how to use adb, fastboot, etc.
And here's a MyTouch3G Rooting guide (updated)
http://theunlockr.com/2009/08/22/how-to-root-the-mytouch-3g-or-g1-in-one-click/
I have the same SPL and had no problems rooting using the 1.5 downgrade method then flashing the recovery image.
There's a pretty good how to thread that has all steps from downgrading to cupcake to loading a new rom.
Only thing I'd change is I'd use the recovery in my sig.
http://forum.xda-developers.com/showthread.php?t=586363
Im running 1.6 on there now. Its the stock rom. I will try this link out and let you know how it goes. Thanks!
I was able to get the recovery and everything loaded. I am trying to load a new rom and once it gets past the flash screen it seems to keep like rebooting i guess would be the way to describe it? do you have any recommendations for a 32b rom? I was looking for one with at least 2.0 and id like to have sense on there.
jmoney1037 said:
I was able to get the recovery and everything loaded. I am trying to load a new rom and once it gets past the flash screen it seems to keep like rebooting i guess would be the way to describe it? do you have any recommendations for a 32b rom? I was looking for one with at least 2.0 and id like to have sense on there.
Click to expand...
Click to collapse
I prefer superd, but am currently using Blue Magic, both can be found in the G1 dev forum. Eclair will be laggy since there's no hardware acceleration yet, and sense will kill your ram.
I just use the roms in G1 because they mostly work on 32b, and most roms in the magic dev forum are 32a.
I wont suggest any 2.1 eclair/sense rom as of now. but I'd say this eclair rom is super nice http://www.mediafire.com/?tzjwo12nzky or jsut wait a couple days maybe less and it will be perfected for now I suggest this rom as it is fast and easy to use load up
WIPE all options
-first install this one http://www.androidspin.com/downloads.php?dir=htcclay/&file=FastTest3.0.2RH.zip
-then this one on top of it (just install) http://www.androidspin.com/downloads.php?dir=htcclay/&file=FastTest3.0.3RH.zip
-
Sorry if this is already being discussed in our G1 forums, had a look but one thread created was closed (therefore hope I'm not doing something I shouldn't be by opening this one, apologies if so!)
I found the link for an untouched OTA Froyo update for the myTouch 3G:
http://android.clients.google.com/packages/ota/tmobile_opal/e059adc603a3.signed-opal-ota-60505.e059adc6.zip
I read the forum over there and they talk of perhaps needing another file, as the update supposingly comes in 2 parts. Is it the case that we need a different radio/spl etc? What is the next step for us?
Hopefully one of our genius developers can get this working and ready to flash on our G1's, an official Froyo!
Wohoo!
Well it looks like it's flashable OOTB. It does contain a new radio image, but I'm not sure how that would work with 1.33.2005/whatever safe SPL is...
I guess stage one is removing the radio and flashing?
Then testing the radio with engineering SPLs?
AdrianK said:
Well it looks like it's flashable OOTB. It does contain a new radio image, but I'm not sure how that would work with 1.33.2005/whatever safe SPL is...
I guess stage one is removing the radio and flashing?
Then testing the radio with engineering SPLs?
Click to expand...
Click to collapse
Im not too sure myself, hopefully the Dev's seethis soon and offer their input on how we get this working on our devices!
cd993 said:
Im not too sure myself, hopefully the Dev's seethis soon and offer their input on how we get this working on our devices!
Click to expand...
Click to collapse
Im guessing they are either working on it now or we are the only ones home on a sunday afternoon lol
All the magic (pun intended) seems to be going on in this thread.
From what I've looked at thus far:
The kernel is built from the latest update in ASOP; at a new starting offset. Since the Dream source has no code to backup this alternate offset; and no configuration for trout in the ramdisk the new rom has the boot image will not work.
You can try to take the rom w/o radio/hboot and run it on a CM6 kernel.. this may operate.
As for the radio update.. it works with 1.33.2003/1.33.2005 as any 2.22.x radio however cm6 kernels fails to initialize the 3d graphics region that the radio moved and the phone reboots (RA-Recovery and adp1 1.6 rom boots without issue on the new radio)
Last HBOOT.. its a perfected HBOOT (it will work on the dream with a 2.x radio so dangerSPL rules apply) however if you are not very very careful you can get stuck..
In short at the very least some coding it required to get the same benefits as the Magic users will have.
I'm really excited bout this...perhaps recompiled with latest nightly CM kernel could work....!!!
ezterry said:
From what I've looked at thus far:
The kernel is built from the latest update in ASOP; at a new starting offset. Since the Dream source has no code to backup this alternate offset; and no configuration for trout in the ramdisk the new rom has the boot image will not work.
You can try to take the rom w/o radio/hboot and run it on a CM6 kernel.. this may operate.
As for the radio update.. it works with 1.33.2003/1.33.2005 as any 2.22.x radio however cm6 kernels fails to initialize the 3d graphics region that the radio moved and the phone reboots (RA-Recovery and adp1 1.6 rom boots without issue on the new radio)
Last HBOOT.. its a perfected HBOOT (it will work on the dream with a 2.x radio so dangerSPL rules apply) however if you are not very very careful you can get stuck..
In short at the very least some coding it required to get the same benefits as the Magic users will have.
Click to expand...
Click to collapse
ezterry, join us here http://www.stinto.net/pages/chat.htm?id=4hlqu
and anyone else who wants to/is knowledgable
ezterry said:
From what I've looked at thus far:
The kernel is built from the latest update in ASOP; at a new starting offset. Since the Dream source has no code to backup this alternate offset; and no configuration for trout in the ramdisk the new rom has the boot image will not work.
You can try to take the rom w/o radio/hboot and run it on a CM6 kernel.. this may operate.
As for the radio update.. it works with 1.33.2003/1.33.2005 as any 2.22.x radio however cm6 kernels fails to initialize the 3d graphics region that the radio moved and the phone reboots (RA-Recovery and adp1 1.6 rom boots without issue on the new radio)
Last HBOOT.. its a perfected HBOOT (it will work on the dream with a 2.x radio so dangerSPL rules apply) however if you are not very very careful you can get stuck..
In short at the very least some coding it required to get the same benefits as the Magic users will have.
Click to expand...
Click to collapse
one point of your thing here is wrong. i don't know about the others, they're probably right knowing you.
In the chatroom i posted, I successfully booted this ota with a cm kernel. duh.
I also booted a cm kernel WITH the tmobile-provided ramdisk. weird.
jcarrz1 said:
I also booted a cm kernel WITH the tmobile-provided ramdisk. weird.
Click to expand...
Click to collapse
I'm a bit surprised about this... but all that is needed to correct any issue is a init.trout.rc (seems most of the needed init logic is in init.rc)
we need a working sense ui 2.2 rom with bluetooth and touch focus
ezterry said:
I'm a bit surprised about this... but all that is needed to correct any issue is a init.trout.rc (seems most of the needed init logic is in init.rc)
Click to expand...
Click to collapse
that's it?? and then the tmobile kernel will work on a g1?
XIPRELAY2010 said:
we need a working sense ui 2.2 rom with bluetooth and touch focus
Click to expand...
Click to collapse
I guess i heared theat somwhere...:-D
sorry for OT...
jcarrz1 said:
that's it?? and then the tmobile kernel will work on a g1?
Click to expand...
Click to collapse
no the ramdisk will.. the kernel is compiled without dream support.. and at a different offset than usual.. this will take some poking and re-build from asop to make a similar kernel.. the problem with using the CM kernel is I suspect that there is additional ram make available by the new radio+kernel configuration.
so what do i have to download and what do i have to do with it, to run it on my G1?
ezterry said:
no the ramdisk will.. the kernel is compiled without dream support.. and at a different offset than usual.. this will take some poking and re-build from asop to make a similar kernel.. the problem with using the CM kernel is I suspect that there is additional ram make available by the new radio+kernel configuration.
Click to expand...
Click to collapse
I agree on that speculation... you mean you haven't tried it yet? i thought you did...
jcarrz1 said:
I agree on that speculation... you mean you haven't tried it yet? i thought you did...
Click to expand...
Click to collapse
I tried and failed to boot the kernel on a dream; and I looked at the source code; and noted the new boot offset.. Just booted it with a CM kernel now
Edit: Camera works, seems smooth.. wifi error.. need to inject root
woot, thank you!
XIPRELAY2010 said:
we need a working sense ui 2.2 rom with bluetooth and touch focus
Click to expand...
Click to collapse
No we don't.
ezterry said:
I tried and failed to boot the kernel on a dream; and I looked at the source code; and noted the new boot offset.. Just booted it with a CM kernel now
Edit: Camera works, seems smooth.. wifi error.. need to inject root
Click to expand...
Click to collapse
is there any improvement on memory/memory management with this change?
Hi, I'm new to the forum and first post. I used to think I was smart, not so much anymore...and here's why.
1. I have an s-on 1.5 hboot cdma Sprint Evo 3d that I originally rooted using this method. http://forum.xda-developers.com/showthread.php?t=1239821
I have flashed synergies, cleanrom, miui, cyanogen, and mean rom. The last rom I was with before the issues was mean rom. I saw the new Mean Rom ICS, downloaded it, and noticed that the phone was really glitchy.(this particular rom was advertised with vm ics leak free) http://forum.xda-developers.com/showthread.php?t=1645211.
2. Heres where the fun begins. I thought I may have downloaded a bad kernel so I used flash image gui to try and get the recommended kernel...didn't go too well. then saw the 2.17 file to PG86IMG workaround and tried that...I couldn't get that to work either. at this point I was pretty frustrated with the way my screen was acting up, not recognizing inputs, or only working in landscape, so I decided that restoring my phone back to stock would be the best bet. I couldn't have been more wrong.
3. im running windows 8 beta, so some functionality and compatibility is out the window here at this point...meaning fastboot, sdk, apk do not function correctly (or at least not for me...) in this OS. So I downloaded the VMware trial and the latest version of Ubuntu and got the fastboot and all that going on there. it was at this point I was able to relock my phone using some of the more popular workarounds for the issue on this forum. However, when I RELOCKED, I also received a SECURITY WARNING. at this point I could not get past the bootloader. I did unlock it, but now its worse...
4. I've spent the last couple of days trying to get the phone to work to no avail...Here's where I'm at now. New sd card. superwiped. Twrp v 1.1.1(I like the tp). I CAN voldwn/pwr to boot. It CAN go into recovery. It CAN talk to my computer in ubuntu, but if you decide to help me by giving me Ubuntu script, please dumb it down for me. It CANNOT boot any roms past the HTC screen. I have tried loading various roms and such with an equal amount of success.
5. So here is what im hoping for. An outcome in which I still have the Evo3d, S-off, and a solid rom. What I need is the assistance to get my phone to load and boot any rom at all. Thanks in advance.
try fastboot boot boot.img
in the zip of your rom there should be a boot.img try to fastboot flash boot boot.img ( put a copy of the file in the directory you run adb from) its what i had to do i am running virtuous ics rom works perfectly on my phone not one glitch yet but i need s-off if you can help i even had the same bootloader error that you had when i tried to relock
Thanks, that actually did it. I set the .img file to the android folder in linux, ran the 'fastboot flash boot boot.img' command and it booted like no other, lol. Now im like you, still wanting to get to S-off but cant figure out how to load a stock rom or even which one I should get. I did flash an anthrax kernel (rc2.1 zram rls) if that matters. do you happen to know which rom to flash?
I'd like to bring TWRP 2.2 to as many variants of the rather fragmented Sapphire platform as possible. I could use some direction to live repositories containing healthy copies of the kernel and proprietary files for CM7 and any tips developers experienced with this platform might have for building 32A and 32B versions as well as the Frankenstein Fender and 1.2 devices.
I happen to have a Fender to test with but, will need volunteers to test builds on the 32A and 32B devices.
Yaaaaaaay
Sent from my HTC Magic using xda premium
xanda143 said:
Yaaaaaaay
Sent from my HTC Magic using xda premium
Click to expand...
Click to collapse
Well, I'm hoping that will be the response. IF I can get it to build nicely and fit TeamWin will likely take over official support and users will be able to access it via GooManager. Already added the WFS as the first MDPI device and the HeroC was a close second.
Well, last I check teamwin recovery project needs to be built in ics.
tvall said:
Well, last I check teamwin recovery project needs to be built in ics.
Click to expand...
Click to collapse
TWRP can be built in either ICS or Gingerbread and they are working to make sure it builds fine with JB as well; however, it was originally designed around Gingerbread and is often most successful with those sources and I'm not aware of any healthy ICS builds for the Dream or Sapphire. Some encouraging works in progress maybe but, nothing I'd want to build a recovery around.
My ics repo is healthy enough to build recoveries as long as you change the kernel. (Never got it to build in gb) Already started on twrp. Want me to upload what I have?
tvall said:
My ics repo is healthy enough to build recoveries as long as you change the kernel. (Never got it to build in gb) Already started on twrp. Want me to upload what I have?
Click to expand...
Click to collapse
If you have something you think is worth uploading it's beyond me to stop you. As I understand it there are some extremely stable and low bug ports of Gingerbread for the Dream/Sapphire platform and quite the handful of kernels. I've been inspecting the publicly available source for as many kernels as I can as I'm aware supporting each fragment of the Sapphire platform properly can be a little tricky. Having a Fender I'm all too familiar with how barmy the device can behave with a kernel that wasn't designed for it. I've built TWRP in GB and ICS and I know that there have been successful builds using JB. It usually isn't too problematic if you're familiar with the device and source.
The only issue I have with my twrp build is it defaults to using /data as if its the sdcard. Probably an issue with my config files.
tvall said:
The only issue I have with my twrp build is it defaults to using /data as if its the sdcard. Probably an issue with my config files.
Click to expand...
Click to collapse
It might be. I'm not really sure why it would mistake the SD card for an MTD partition without provocation tho. TWRP usually requires minimal configuration. You usually need to accommodate for it's linked nature and to provide the device resolution. It usually only gets crazy when you have extra MTD partitions for things like WiMAX, efs and pds.
If you can pull the log from /tmp and a dmesg there is a good chance I might be able to tell you what's going on.
Well... I'm lazy and you seem to know what you're doing, so you'll probably get it done before I find out what's wrong. I'd love to help you with this project. I also have a fender (actually its my girlfriends, but she let's me mes with it)
Regarding kernels, you should only need one for 32b (and fender), I don't know much about the 32a. And you shouldn't need anything fancy. I would use ezterry's 2.6.34 kernel because it seems incredibly stable.
tvall said:
Well... I'm lazy and you seem to know what you're doing, so you'll probably get it done before I find out what's wrong. I'd love to help you with this project. I also have a fender (actually its my girlfriends, but she let's me mes with it)
Regarding kernels, you should only need one for 32b (and fender), I don't know much about the 32a. And you shouldn't need anything fancy. I would use ezterry's 2.6.34 kernel because it seems incredibly stable.
Click to expand...
Click to collapse
I've always had charging issues with ezterry kernels, the Fender and Gingerbread. It fails to properly recognize the 1A AC charger and quick charge, every time. I believe this is specific to the Fender/1.2 I think the only one I remember working well was some old mod for the fender/1.2 specificly. I'm trying to track it down. I think I'll need a 32A, 32B and Frankenstein 32A/B (Fender/1.2) build to make sure everyone is covered. I believe that this platform uses offmode charging in recovery so it's kinda important that the kernels properly support changing for their host device. I believe the software I'm running now in recovery and system both have flawed kernels as the poor thing takes forever to charge.
They charge while they are actually off. that's handles by either the radio or spl I think. I had a bricked fender that couldn't get into hboot or anything that I used for spare parts and battery charging.
tvall said:
They charge while they are actually off. that's handles by either the radio or spl I think. I had a bricked fender that couldn't get into hboot or anything that I used for spare parts and battery charging.
Click to expand...
Click to collapse
I believe it's using recovery like the Wildfire S. The SPL boots to a special offmode charging state in recovery when the device is supplied power while off-line. There are service binaries to deal with this request in recovery and it will hard-lock the device if it isn't handled properly. I only remember this because this feature was broken much earlier on my device with faulty recovery software and I've since run into issues on a handful of HTC devices that utilise this solution and recovery software that wasn't setup properly.
It's fairly easy to test as all you have to do is disable the feature in the recovery init and it will cause the device to hard lock when it's plugged into a power source. It will illuminate the amber led as if it's charging but, the state will never change and it will remain locked after power is removed. Occasionally the device will panic and reboot but, you usually have to remove the battery to get it to shut down afterwards, especially if the service to detect button presses is also disabled in the recovery init.
The lines I'm talking about look like this:
Code:
service offmode_charging /sbin/offmode_charging
+ disabled
oneshot
service detect_key /sbin/detect_key
+ disabled
oneshot
I also just checked and yes, under the ezterry based kernel currently powering CronMod on my Fender the device fails to properly recognize the 1A input from the AC charger. If I used that source unmodded to build a recovery for the Fender/1.2 offmode charging would take forever. I believe it works fine on 32A and 32B devices, it's only the hybrid 32A/B devices that are afflicted but, as I said I recall a fix having been found I just have to track it down.
It charges with a bad spl/radio flash that can't boot into anything at all. So charging is not handled by the recovery.
tvall said:
It charges with a bad spl/radio flash that can't boot into anything at all. So charging is not handled by the recovery.
Click to expand...
Click to collapse
You'll forgive me if I choose to base my development off of data from the manufacturer and my own experience with numerous HTC devices instead of the behaviour of a broken device I've never seen. As I can reproducibly break offmode charging on the device by flashing a recovery image with the service disabled in the init I find it hard to accept that the recovery partition isn't involved in the process. I find it far more likely that you may have an incompatible radio/hboot combination that doesn't boot but, still loads offmode charging properly as this mode isn't reliant on a healthy SPL/Radio.
Can you get me a recovery with it disabled? I want to test this
tvall said:
Can you get me a recovery with it disabled? I want to test this
Click to expand...
Click to collapse
I'm not sure if I can provide one right away but, I'll gladly provide some for testing. You could also resurrect your lame device with a little JTAG magic. A malformed HBOOT/Radio flash isn't lethal, just extremely inconvenient.
WoefulDerelict said:
I'm not sure if I can provide one right away but, I'll gladly provide some for testing. You could also resurrect your lame device with a little JTAG magic. A malformed HBOOT/Radio flash isn't lethal, just extremely inconvenient.
Click to expand...
Click to collapse
I don't have the tools, soldering skills, or money to jtag. Its lethal if you don't have that.