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.
Related
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?
As done some weeks ago for the G1 now there is a success in de-bricking a Magic 32A
http://forum.xda-developers.com/showpost.php?p=6260574&postcount=510
Cheers,
bart99
woow! great job! cheers ; ))
Very good news, congrats bart99 and ezterry for de-bricking both Dream and Magic
could it be a way to break Perfect SPL?
sychie said:
could it be a way to break Perfect SPL?
Click to expand...
Click to collapse
That was the first thing i tought when started to read this thread!!! Hope so!
yes it should work, with jtag its possible to load a different spl to ram and then execute it
for mor info post on the other topic, ezterry did something similiar
bart99
Wow you guys are actually considering doing this to a functioning magic just to get root? daredevils
Anyway, great work!
Well if the goldcard method is not working for someone, this could be their solution(if they have enough knowledge of course ).
eyegor said:
Wow you guys are actually considering doing this to a functioning magic just to get root? daredevils !
Click to expand...
Click to collapse
and here I have jtaged other peoples working dreams to give them root
not yet tried a magic.. but will likely in the near future
I like to send my MyTouch Fender to someone to have it unbrick it; If anyone can please let me know. I live in the US but can mail it anywhere.
ezterry said:
and here I have jtaged other peoples working dreams to give them root
not yet tried a magic.. but will likely in the near future
Click to expand...
Click to collapse
i would love to try it on the htc magic 32A.
cmarti said:
I like to send my MyTouch Fender to someone to have it unbrick it; If anyone can please let me know. I live in the US but can mail it anywhere.
Click to expand...
Click to collapse
lol. be careful with that. you might not get it back.
anyways, i'd be scared to try this. it seems like a few things could go wrong and you might just end up being out of one phone. probably need REAL steady hands.
r3s-rt said:
lol. be careful with that. you might not get it back.
Click to expand...
Click to collapse
heh
It is also assuming (seems likely but I don't think we can promise it) that the fender has the same jtag ports as the 32a/32b phones..
Also since there is so much problems rooting these things.. (And even the root now seems to be with the original kernel only) what will happen when it meets my jtag hack?
basically:
* If you are lucky it will just become a 32a/EBI1 w/ headphones.. [no I don't think I see a problem with that]
* a bit less lucky it will become a 32a/EBI1 w/ useless headphone jack
* even less lucky whomever is rooting it gets to chase down the fender firmware to make it go.. and additional radio hacks
* and unlucky damages a trace removing glue from the magics main board. (the rogers magic 32a has some brown epoxy that is hard as a rock filling the gap between the processor and ground shield over the jtag points.)
r3s-rt said:
lol. be careful with that. you might not get it back.
anyways, i'd be scared to try this. it seems like a few things could go wrong and you might just end up being out of one phone. probably need REAL steady hands.
Click to expand...
Click to collapse
Honestly I don't mind if it gets lost, It's paper weight anyway now...
cmarti said:
Honestly I don't mind if it gets lost, It's paper weight anyway now...
Click to expand...
Click to collapse
Same situation here as well. I'd love for someone to help me unbrick - it just goes straight to trying to update the radio but then the screen fades out and it hangs. Sigh.
Tereno said:
Same situation here as well. I'd love for someone to help me unbrick - it just goes straight to trying to update the radio but then the screen fades out and it hangs. Sigh.
Click to expand...
Click to collapse
So via some experimenting on my JTAGed dream I think I understand where the issue some people are having with the radio flashes on the 6.x radio.
When you flash a radio the SPL loads the radio image file into ram and calls a 'radata' command in the radio bootloader. The exact location and size are passed to the radata function.
* The 1.33.* SPLs load the radio image this near 0x103B5300;
* The 1.76.2007 SPL loads the radio image near 0x19500000
This major change in memory location appears to be important. The 6.x radio will loop forever validating the image when it is loaded at the lower memory address.. while flashes as usual at the higher address.
This means if you still have 1.33.2010 installed and flash a radio it will fail.
Flashing via fastboot this will get stuck (maybe fade the screen) until you pull the battery/usb; then boot the device as normal.
However if you do this via recovery: recovery will set the SPL boot mode to flash the radio from cache; and since the radio flash fails to ever return this setting is never cleared. Thus every time you boot the radio attempts and fails to flash.
(This appears to be many peoples problems if you really have 1.76.2007 and stuck in radio flash mode [boot mode 4] my guess is the radio.img has some bit errors or newly formed bad block in /cache.. causing the signature check to fail [despite the radio.img being validated when the zip file was opened via recovery].. I have seen this on one Dream I de-bricked)
-------
PS: the 6x radio is a no go on the dream.. blue light mode goes.. and with some prodding via JTAG I can softboot a SPL or re-flash a 3x or 2x radio.. but that is about the extent of what appears to work.
anyone willing to give my tmobile mytouch 3g a shot?
Not sure the radio/spl that is on it now since its bricked only get splash screen
But when I got the phone it was
spl: 1.33.06 30000
26i
willing to send it to anyone
Press and hold volume down and press Power. Can you get into fastboot? If so, you're not bricked.
Me too Success unbrick my touch 3g 1.2
Ezterry you are genius, as i follow your guide,with a lot of pain process,trial and error, i built my own JTAG wiggler interface and with a little mods.
everything has working..Good Job Ezterry..
now i can smile .
good job brother
bart9984 said:
As done some weeks ago for the G1 now there is a success in de-bricking a Magic 32A
http://forum.xda-developers.com/showpost.php?p=6260574&postcount=510
Cheers,
bart99
Click to expand...
Click to collapse
I am success too with Tvalls Mytouch 3 g..but cant send it back ,cause shipping so expensive here in Indonesia,,
Really sorry
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?
*32a New Radio 6.35 Sapphire/Magic only*
magic 32a old radio here http://forum.xda-developers.com/showthread.php?t=776929
g1/32b magic here http://forum.xda-developers.com/showthread.php?t=776922
------------------------------------------------------------------------------
Well I managed to figure out with a lot of reading and sleepless nights compiling source how to build a recovery for you PS3 guys.
It's based wholly on PSFmod recovery for hero.
Thanks klutsh for the git source. Thanks kakaroto for the pl3 source. Thanks Cyanogen for the kernel source(I'm using my modified 6.35 CM kernel)
I posted this in my kernel thread and those that tried it say it works, I have no PS3 myself.
If you let me know about updates in this thread I can re-compile for you.
PSFreedom Recovery for New Radio Sapphire
MD5: 1a8a1e063fc9af5efb3ec780d9b802bd
Here are the custom bins that I compiled with psfreedom pl3 bins
psfmod for 32A
hey man once again,
a few minutes ago i tried to load a custom payload from here -> http://www.psfreedom.com/wiki/HTC_Hero with u'r recovery, but it gives me an error.
i've checked the error log and it seems to be something related with this: -> PSFreedom gadget: Error: Payload size is more than the maximum allowed of 3808
i attach here my error log, it will possibly help you
thanks in advance
H3llSp4wN said:
hey man once again,
a few minutes ago i tried to load a custom payload from here -> http://www.psfreedom.com/wiki/HTC_Hero with u'r recovery, but it gives me an error.
i've checked the error log and it seems to be something related with this: -> PSFreedom gadget: Error: Payload size is more than the maximum allowed of 3808
i attach here my error log, it will possibly help you
thanks in advance
Click to expand...
Click to collapse
Oh those aren't compatible, I compiled all the payloads myself, I guess I should post them. Back in a bit.
Edit: some on that page are ok, the pl3 ones of kakaroto
so.. what does this do for you PS3 owners?
carz12 said:
so.. what does this do for you PS3 owners?
Click to expand...
Click to collapse
Allow us to enter in recovery mode, being able to load some homebrew.. Most people use it to load "backups"
xiserre said:
Allow us to enter in recovery mode, being able to load some homebrew.. Most people use it to load "backups"
Click to expand...
Click to collapse
ok, something sony should have allowed anyways
carz12 said:
Oh those aren't compatible, I compiled all the payloads myself, I guess I should post them. Back in a bit.
Edit: some on that page are ok, the pl3 ones of kakaroto
Click to expand...
Click to collapse
are the payloads you compiled compatabile with the psfmod for the Evo?? and if so which one includes the hermes v4? I'm just trying to get MOH and MMA working
Young_e said:
are the payloads you compiled compatabile with the psfmod for the Evo?? and if so which one includes the hermes v4? I'm just trying to get MOH and MMA working
Click to expand...
Click to collapse
It looks like just one set of payload files for all the psmod recoveries, but I have no idea what is what with those, I don't even own a ps3
it's work on 32b???
I get paranoid about flashing anything other than roms so I'd just like to double-check with someone who's done it.
I have a Roger's HTC Dream, with RA-dream-v1.5.2R, Radio-3.22.26.17, and hboot-1.33.2005. From what I remember, it's a 32A radio, and flashing Sapphire roms will work ok, but will flashing this recovery image work on this phone or will it produce a brick?
Thanks
capebretonsux said:
I get paranoid about flashing anything other than roms so I'd just like to double-check with someone who's done it.
I have a Roger's HTC Dream, with RA-dream-v1.5.2R, Radio-3.22.26.17, and hboot-1.33.2005. From what I remember, it's a 32A radio, and flashing Sapphire roms will work ok, but will flashing this recovery image work on this phone or will it produce a brick?
Thanks
Click to expand...
Click to collapse
Brick, you have to have the 6.35 radio and matching spl, this is only for new radio sapphire/magic, I though there was a g1 or 32a old radio version in the other thread.
miguelchico said:
it's work on 32b???
Click to expand...
Click to collapse
no it doesnt
what about 32B
i don't see a 6.35 radio for that
do i even need that
will it work?
or has a 6.35 radio for 32B not been developed yet?
Hey Carz, I am using the Magic 32A old radio, I see you added the link up top for it, appears to be the original wich is dated 9/07, or is this for your new comp with the new payloads?
I know that, but I have no old radio device to test on, one of my magics bricked during the 2.1 update of rogers
Is it possible to use the hermes v4b payloads with this recovery?
That sucks, always worrying bout brickin. I have tried flashing both the v3 for 32a and the other one .kAroshi made with the pl3 and both just hang on the htc magic screen. On the recovery screen says 32a, my phone is the mytouch with the 35mm jack, so it is 32a right? Pretty sure it is. Dont remember what I finally flashed with in the first place! Trying to get back to there at least!!
psfmod for 32A
hy guys,
it seems there was released a few days ago a new version of psfmod recovery for hero (psfMod-hero-0.9.7.1.img),i dont know what improvements were made this time. but is there any kind soul who can port this for our 32A devices ?
very grateful once again
H3llSp4wN said:
hy guys,
it seems there was released a few days ago a new version of psfmod recovery for hero (psfMod-hero-0.9.7.1.img),i dont know what improvements were made this time. but is there any kind soul who can port this for our 32A devices ?
very grateful once again
Click to expand...
Click to collapse
0.9.7.1
[27/10/2010]
fixed Eris boot & prop issues
no updates for ours yet, its the pl3 payloads and pl3 itself that gets the updating and I pull from git every morning, nothing has changed yet.
thanks man
UPDATE WITH INFORMATION AND LINKS ON HOW TO AVOID PROBLEMS
Through the posts and information that has been brought to my attention your Hboot is not really of significance, it is just your partitions. You can update your Hboot and maintain older partitions.
I bet you're wondering how to discover if you have these partitions. I owe the credit to this command to XhausX. "A petty reliable way to tell is by your /proc/mtd table. If 'cat /proc/mtd' shows an erase size of 20000 you have the old set up. If it shows 40000 you have the new one".
Once you know whether you have the old or new your options are as follows
OLD Partition: Flash Clockwork mod 2.5 or use the unmodified version of Amon_ra found here http://forum.xda-developers.com/showthread.php?t=705026&highlight=Amon+Recovery+Custom . Also be aware that you can flash the Amon_ra found in clockwork mod because it is unmodified.
NEW Partition: Flash the updated clockwork recovery mod (3.0) or use a modified version of the recovery found in Zikronix thread here http://forum.xda-developers.com/showthread.php?t=829045
Although this is a temporary solution I urge everybody to reach out to developers and offer assistance or bring to their attention the danger of the multiple partitions. I'm unaware if you can put a check into software that would install recoveries but I'm sure it wouldn't be too hard if xhausx script can already distinguish them. Hopefully you all head my warnings. HAPPY ROOTING and GOOD LUCK!
ORIGINAL QUESTION READ ABOVE FOR INSTRUCTIONS
This is going to be in many ways a general warning that will bring something I realized today to the attention of everybody and simultaneously will bring a developer forward to answer the questions I'm about to present. I have a similair thread in the Q & A forums but I wanted to get more coverage for this so that a ton of people don't kill their phones or lose their RSA keys accidentally (have lost mine and it sucks if you live in a 4g area!).
Amon_Ra is a fantastic recovery and has been at 1.8 for a while. In the Hboot 2.2 and 2.10 thread the author brings forth the fact that the partitions for these Hboots has changed and that the modified Amon_ra is made to compensate for this. It is labeled as Amon_ra but it is not truly 1.8 but instead a modified version.
What i take this to mean is that the partitions, where certain information is stored on our phone, was changed for these Hboots and thus the recovery had to be altered to backup and flash information to these new locations. Clockwork mod has now been updated to 3.0 and it fixes this. I'm assuming it scans your phone to see which Hboot you have and acts accordingly.
Now, for the problem
Clockwork mod has an option to flash Amon_ra. However, if you have Hboot 2.2 or 2.10 and this flashes an older Amon_ra or an unmodified for these new hboots(it is much easier to flash recoveries this way and I know i'm not the only one who does it) then if you attempt to nandroid or flash a rom you could very well bork it.
I have searched and found no documentation CONTRARY to this. If there is, point me in that direction and I'll be on my way to check it out and remove this post but I want to make sure nobody accidentally ruins their phone while changing recoveries.
My suggestion to this problem, and if it is in fact a problem I'll be attempting to get into contact with the developers and see if they have a solution. I think it's just a bad idea to have varying versions of Amon_ra floating around that are labeled the same without actually knowing which is for which Hboot.
Thanks for reading and if you have any input please add, I just want to avoid people messing up their phones. I have been through 3 refubs and gone through the rooting process various times and I just want to make sure some noobies don't lose a ton of money in tough economic times because of a simple oversight like this. If the need be we need to put warning out there about this.
Me and TrevE are the ones that discovered this whole thing.
We msg'd both amon_ra and koush and amon quickly threw together a fix. And I tried cw's new recovery on an old and new evo on the new evo it seemd to work but on the old evo it would only back up the boot.img so im all for getting this sorted out...and it is a real problem
here is the work me and treve did
http://forum.xda-developers.com/showthread.php?t=843342
The issue is that the "modified one" from the thread reports version 1.8, the version you can "officially" download is 1.8 but i assure you they are VERY different.
The poster below states he uses 1.8 on his 2.02 evo but the question is what version...of 1.8. Yes it has been reported that some of the older evo's that managed to get the 2.xx hboots can use the "official" amon_ra and it works....and it might...however the newer evos some of which are 003 and 004 that have hboot 2.xx need to use the "modified" one
this is where the issue lies
Its old news that you cannot use anything but Amon_Ra 1.8 on hboot 2.02 and 2.10. DOnt use Clockwork. Sure clockwork fixed it but still needs more testing, from what Ive read. It might be deemed safe, but why not use what works, Amon_RA
NVM I answered my own issue.
mroneeyedboh said:
Its old news that you cannot use anything but Amon_Ra 1.8 on hboot 2.02 and 2.10. DOnt use Clockwork. Sure clockwork fixed it but still needs more testing, from what Ive read. It might be deemed safe, but why not use what works, Amon_RA
Click to expand...
Click to collapse
Do you even read what he wrote???
davenukem said:
This is going to be in many ways a general warning that will bring something I realized today to the attention of everybody and simultaneously will bring a developer forward to answer the questions I'm about to present. I have a similair thread in the Q & A forums but I wanted to get more coverage for this so that a ton of people don't kill their phones or lose their RSA keys accidentally (have lost mine and it sucks if you live in a 4g area!).
Amon_Ra is a fantastic recovery and has been at 1.8 for a while. In the Hboot 2.2 and 2.10 thread the author brings forth the fact that the partitions for these Hboots has changed and that the modified Amon_ra is made to compensate for this. It is labeled as Amon_ra but it is not truly 1.8 but instead a modified version.
Click to expand...
Click to collapse
the poster that said you can only use Amon_ra on hboots 2.2 and 2.10 is incorrect. You can only use a CERTAIN VERSION OF AMON_RA on hboot 2.2 and 2.10. Disregard his post.
I'm not being mean bud but this is incorrect and will only help people mess up their phones.
mroneeyedboh said:
Its old news that you cannot use anything but Amon_Ra 1.8 on hboot 2.02 and 2.10. DOnt use Clockwork. Sure clockwork fixed it but still needs more testing, from what Ive read. It might be deemed safe, but why not use what works, Amon_RA
Click to expand...
Click to collapse
I think what he is trying to say is that there are 2 different versions of "amon ra 1.8" which are both different.
One version fixes the partitions on the newer hboot, and the other one does not.
So, what he is saying is rename the newer amon ra to 1.8.1 or something so that people know they are flashing the right one.
BTW... autoroot has it built it.
davenukem said:
the poster that said you can only use Amon_ra on hboots 2.2 and 2.10 is incorrect. You can only use a CERTAIN VERSION OF AMON_RA on hboot 2.2 and 2.10. Disregard his post.
I'm not being mean bud but this is incorrect and will only help people mess up their phones.
Click to expand...
Click to collapse
amon_ra 1.8 works fine on 2.2 hboots. can't say the same about 2.10 because that isn't my version. I have 2.2 and not issues with 1.8
kthejoker20 said:
I think what he is trying to say is that there are 2 different versions of "amon ra 1.8" which are both different.
One version fixes the partitions on the newer hboot, and the other one does not.
So, what he is saying is rename the newer amon ra to 1.8.1 or something so that people know they are flashing the right one.
BTW... autoroot has it built it.
Click to expand...
Click to collapse
Ok that makes alot more sense.
See, more testing needs to be done. If what you say is true then perhaps it's only the 2.10 hboot with these new partitions? I think the Amon_ra developer needs to communicate with Koush and discover HOW koush figured out how to distinguish between which phone had which partitions. Realistically though, this is a horrible move by HTC, it's bad enough there are so many hardware revisions floating around.
lithid-cm said:
amon_ra 1.8 works fine on 2.2 hboots. can't say the same about 2.10 because that isn't my version. I have 2.2 and not issues with 1.8
Ok that makes alot more sense.
Click to expand...
Click to collapse
davenukem said:
See, more testing needs to be done. If what you say is true then perhaps it's only the 2.10 hboot with these new partitions? I think the Amon_ra developer needs to communicate with Koush and discover HOW koush figured out how to distinguish between which phone had which partitions. Realistically though, this is a horrible move by HTC, it's bad enough there are so many hardware revisions floating around.
Click to expand...
Click to collapse
In HTC's eyes its working for them... messing up the dev community from rooting... but that my friend is only short lived.
lithid-cm said:
amon_ra 1.8 works fine on 2.2 hboots. can't say the same about 2.10 because that isn't my version. I have 2.2 and not issues with 1.8
Click to expand...
Click to collapse
but what version of 1.8 see my post i updated above
davenukem said:
the poster that said you can only use Amon_ra on hboots 2.2 and 2.10 is incorrect. You can only use a CERTAIN VERSION OF AMON_RA on hboot 2.2 and 2.10. Disregard his post.
I'm not being mean bud but this is incorrect and will only help people mess up their phones.
Click to expand...
Click to collapse
Oh I was confused at the time I posted. I thought you meant something other than Amon RA 1.8. When I rooted my phone, I was told in the guide to use AmonRA 1.8 because the lesser version was no good. Because like you said the partitions are different in 2.02 and 2.10. Which in turn (again like you said ) can render the 4g obsolete and unresolvable and the inability to possibly flash roms.
Its gonna suck when us older hardware versions need to get phones repaired. Damn u HTC lol
Sent from my Evo CM6
lithid-cm said:
amon_ra 1.8 works fine on 2.2 hboots. can't say the same about 2.10 because that isn't my version. I have 2.2 and not issues with 1.8
Click to expand...
Click to collapse
It is the partition setup, or to be more specific MTD, that matters. The hboot version was thought to be the culprit at first but now we know it is doesn't matter.
So the hboot does not matter when it comes to this. It is all your partition setup.
Sent from my PC36100 using XDA App
Then I must be using the new amon ra version since I rooted my phone using this method:
http://forum.xda-developers.com/showthread.php?t=829045
So is there any downside to upgrading to the latest 3.0.0.2 ClockworkMod Recovery on an older HBOOT version? Will I have issues restoring from older nandroid backups?
martonikaj said:
So is there any downside to upgrading to the latest 3.0.0.2 ClockworkMod Recovery on an older HBOOT version? Will I have issues restoring from older nandroid backups?
Click to expand...
Click to collapse
yes because depending on all sorts of variables. in fact i couldnt get cw the new version to work with old hardware and it was acting goofy in new hardware.
the only reason we require the use of the "modified" recovery like haus said is because the partition structure changed. and really has nothing to do with the hboot.
zikronix said:
yes because depending on all sorts of variables. in fact i couldnt get cw the new version to work with old hardware and it was acting goofy in new hardware.
the only reason we require the use of the "modified" recovery like haus said is because the partition structure changed. and really has nothing to do with the hboot.
Click to expand...
Click to collapse
So i should stick with 2.5.1.2 for now? lol
I flashed 3.0.0.0 when it came out, and it led to all kinds of crazy issues. It worked just fine in the recovery menu etc. but i ended up having some bootloops and such.
Also, ROmManager is prompting that 3.0.0.2 of CWM is available. thoughts?
How about providing links to the proper version of Amon_Ra's recovery in the OP? Granted, it'd be nice if he changed the version number, but having the right one somewhere obvious would be nice in the meantime.
Thought I would mention that I flashed clockwork from rom manager. Works fine on my 2.2. Just did a back and some flashing. All goof
Sent from my PC36100 using XDA App