Desperate for help - myTouch 3G, Magic Android Development

I'd like to say, straight off the bat, that I have searched relentlessly, with only hints of success, but nothing actually turning up fruitful.
My problem is this:
tonight i decided to try out Cursorsense, it looked simple enough. I flashed my radio and SPL, and got ready to flash the new rom.
As I stared up the AmonRA recovery image (1.5.2 H), it suddenly restarted, and went into a boot-loop.
*I have read suggestions of flashing "permanently" but I am unaware how to do this.
*I have read about wiping the system, but this does nothing.
*attempts to use "fastboot update" give me an error of "failed to load update.zip" or a series of completely garbled text and other crap.
*attempts to use "fastboot boot" using either a new version of AmonRa's recovery image, or a stock sapphire image, give me an error of
booting... FAILED (remote: reproduce boot image with on-flash ramdisk error)
I find myself sleepy, and at a loss. I might be missing something fundamental, but I do need your help in seeing this.
This wouldnt be such a terrible issue if this wasnt a phone I use for work, but... so it goes.
Regards, and thanks in advance for any help.

pal, you need the *hero* AmonRA's recovery!

okay! There's some solid help now, would this solve my biggest (and pretty much only) problem, of the RA-Sapphire freezing/hanging and suddenly rebooting?
I say only problem, as I've just bought a card reader, so I can at least bypass the process of getting files onto the SD.
Regards

retrograde said:
okay! There's some solid help now, would this solve my biggest (and pretty much only) problem, of the RA-Sapphire freezing/hanging and suddenly rebooting?
I say only problem, as I've just bought a card reader, so I can at least bypass the process of getting files onto the SD.
Regards
Click to expand...
Click to collapse
Your phone is rebooting because the new radio doesn't support the Sapphire recovery, you need to use the Hero recovery.

Related

The G1 Night Light (READ FIRST IF YOU BRICKED YOUR PHONE)

Many people complain that they have "bricked" their phones when they really haven't. This thread will hopefully help reduce the questions on all of our useful threads.
How to tell if your phone is bricked:
1.) When you try to turn it on, nothing happens?
2.) Camera+Power does nothing.
3.) Home+Power does nothing.
4.) You flashed the SPL BEFORE the radio
If you answered yes to any of the above 4, you are bricked. You probably need a new board in the phone. Read more here: http://forum.xda-developers.com/showthread.php?t=516440 It has been confirmed that you WILL brick your phone if you attempt to downgrade your radio after flashing the new SPL. Not sure why you would want to anyways...
How to tell if you just need to re-flash:
1.) Your phone is stuck on the g1 logo
2.) Your phone is stuck in a boot loop
3.) Home+Power boots into recovery
If you answered yes to the above then you are NOT bricked. You have the G1 Night Light. This is (usually) a very easy fix.
The usual scenario is: You just upgraded your radio and/or the SPL on your phone and now you are trying to turn it on with no luck.
How to fix: After you upgrade your radio and/or SPL, you need to wipe a rom on the phone. For a plain almost stock feeling rom, checkout http://jf.andblogs.net/2009/05/24/jfv151-images-are-out/ if you are looking for hero, checkout the tutorial at g1upgrade.com.
I have also noticed when you flash hero, it will stay on the g1 logo for 5 or 6 minutes and then it'll finally start loading. Make sure your not being impatient and give it several minutes if you have just flashed a rom.
Last step:
If you have installed a new radio, then spl, then a new rom and you STILL get the g1 screen. Try it all over again. You probably didn't do something right. You don't need to ask questions in 30 different threads, your issue is not unique. You just need to search for some answers.
*Saved for future posts*
Edit:
Thanks! Updated.
I flashed the SPL before the radio whenever Haykuro released the Hero ROM and I didn't brick my device. Guess that I just got lucky. Thank goodness I know better now. haha
it's possible you flashed the radio prior to the SPL, only a loooong ways back.
Another thing to try if you are having issues is:
su
rm -r /system/sd/*
I was stuck in a boot loop and a quick ext3 wipe did the trick. The command should be able to be ran from console or terminal. You may need to mount /system with:
mount -t -rw,remount -o yaffs2 /dev/block/mtdblock3 /system
You would need to type that in between the commands above . I ran across this in another post but i think this is a good spot for it too .
Duplicate post...
thanx
At least I know now how to tell if I bricked my phone or just flashed it badly thanks for this.
youneek said:
How to tell if you just need to re-flash:
1.) Your phone is stuck on the g1 logo
Click to expand...
Click to collapse
many people who flashed the new SPL before the radio are stuck at the G1 splash logo, but cannot get to recovery or spl bootloader / fastboot mode regardless of what they do, so this bit might be misleading...
they aren't technically "bricked" b/c it's loading the radio rom, but it never hands off to the SPL, so there is currently no way of reloading either of those to make the device do anything useful -- essentially a brick
alapapa said:
many people who flashed the new SPL before the radio are stuck at the G1 splash logo, but cannot get to recovery or spl bootloader / fastboot mode regardless of what they do, so this bit might be misleading...
they aren't technically "bricked" b/c it's loading the radio rom, but it never hands off to the SPL, so there is currently no way of reloading either of those to make the device do anything useful -- essentially a brick
Click to expand...
Click to collapse
This is exactly what happened to me, it was a brick, sent for repair and they replaced the mainboard.
I have fixed 2 phones that had no recovery and stuck at the g1 screen. If someone has this problem message me and I'll help you fix.
Good Job
Sorry this is off topic. But...
Thank you for this thread!
Ok,
By the way, has anyone figured out what The difference in the baseband is?? I have a U in mine...
youneek said:
I have fixed 2 phones that had no recovery and stuck at the g1 screen. If someone has this problem message me and I'll help you fix.
Click to expand...
Click to collapse
really? if it can't get to recovery / fastboot mode nobody has published a fix w/o a hardware swap.
what's your method?
I will buy a bricked one off ebay and post the steps I do to get it back. I can only fix the "Night Light", I can't fix a truly bricked phone (yet).
digital006 said:
This is exactly what happened to me, it was a brick, sent for repair and they replaced the mainboard.
Click to expand...
Click to collapse
How and where did you sent for repair and how much does it cost? I have a bricked MyTouch3G at this moment. Did HTC took it?
not bricked just weird!
ok been reading on here ,not sure if i need to just reflash everything or sd issuse?i put the new raidio,then spl on !then put jacxrom on my phone worked great!then ran for a day.then tryed cyanogenmod 4.0 and loaded fine but got force closed issues at the google sign in so i wipe and went to jachero 1.2 loaded fine went to logo android and then htc ,but then the screen went to blank .like the as said g1 night light .so i went back to jacxrom 1.3 it loaded fine got stuck in t mobile g1 screen .ok i flashed again same thing. but this is the part if i take my memory card out it will boot up just fine!then put memory card back in but lol all apps are missing have reinstall them. i wipe every time.i have the latest raidio 22.19.26I).,spl 1.33.2005 .also the jacxrom is running fine when phones on .so any help please thanks .also when i put the spl on it loaded then said reboot so i did. after went back to recovery at the bottom it said formatting cach... but was setting there for a while so took battery out then booted phone .was it suposse to say done or not ! hope dont make any mad thanks for the info
bump
hey help me plz i have big problem
i forget hit alt+w when i install SPL then i press alt+s when SPL install i out battery then i put it my mobile don’t want open and when i holding down the Home and Power button don’t open recovery mode and i holding the End key and the Camera button don’t open boot loader plz help me plz
You aren't going to get any help with sentences that atrocious. Can you be more clear?

Ok, I give up --- cant get out of G1 bootie, skateboards & CM/JF recovery -- help

G1 DREAM (really is a dream, right now, a little bad one a little embarrassing)
been 5 mos since I took root via Cyanogenmod's latest G1 stable and last theme was PHRASh Then I thought about checking out
some other themes and clockwork orange caught my eye... Orange is my favorite color, so wehen I saw there was some Orange theme I must've had a dare encounter with myself-- i recall actually installing the Orange theme..... when i asked the phone to flash the theme, it went into permanent G1. Gave it about 12 minutes. Rebooted into recovery (home menu power) and then did what I think got me in deep droid doo doo -- I attempted to restore to my last backup whch was the day before (and ironically the BEST backup i ever made I had it all humming so nice and fast) Guys -- instead of hitting restore to last backup... I actually hit nandroid backup. I know. That was a really bad day and its been a worse 50 hours. I know -- and Ive learned -- OK?
Since that time.... 50ish hours Ive lost track of what Ive done, but its a potpourri
bootloader is dev spl skateboarding, recovery is Cyanogenmod JesusFreke 1.4 recovery.
DREAM DREA100 PVT 320
HSPL10.95.3000
CPLD-4
RADIO 2,22.19.361
OCT 29 2008
SERIAL0 -- (fastboot i have fastboot as well)
at first flash of bootloader it says "NO IMAGE FOUND!"
If I press Home when it restarts in perpetual cyclical hell I get into CMJF recovery. I have executed every single option numerous times -- and have not been able to successfully flash anything else -- and now I dont know WHAT to flash. I even tried to go back to root!
If I dont press Home or Camera, I get this....
the awful permanent G1 screen. Forever and ever.
I have Wiped backed up, tried to get update.zip and just about ANYTHING into my sdcard but I dont think they have been successful installations to flash. I am not ADB enabled yet. Surely someone knows what this is all about and I am willing to take a flame for posting in the wrong forum if I can get something out of this, I will pitch in later and help y'all keep these forums in workin' order!
every optioon on the recovery screen which is recovery CM and JF 4.2
When I try to load files according to the instructions in xda and cm i cannot get it in fast enough on the g1 running on the frozen G1 screen because I dont known the time of mount the SDCARD has and when it begins (I know it opens for a while and then closes)
So i got droidexplorer and its almost impossible to get the file in there. I can get it in, and see it, and reboot the phone (and computer)( restore usb connection and I see the update.zip on the sdcard. Then I unmount the phone and reflash and it says something about not being able to find the file.
Whats next? Please dont assume I know what I am doing, I am sure you can tell -- but I am really good at following instructions!
Hello anyone?
I have been up all night trying to fix this phone and i am still not able to do so. I
I cannot get into recovery anymore ------
i am stuck on the hardspl and I have found fastboot again. But I cannot use frastboot if I cannot get any commands into it. Anyone?
ok i get it -
thanks for the help guys! I now have my phone working at a blitzing pace and i am leaving it alone for now. I dare myself to leave it unchanged for a week. Thanks mostly to one of the Dudes on Cyanogenmod.com -- who helped me piece together the missing parts.
Actually -- let me summarize even if only I am reading this
Androids levels of defenses are 1. HardSPL 2. Recovery and 3. normalcy. Lose normalcy (Ok, a beauty of a ROM) you have recovery to get the ROM back -- but the trick is -- can you get the necessary IMG file on your SDcard to update.zip with? Can you figure out ADB and push the update.zip? Can you figure out Fastboot and what it REALLY does and what you can and cannot do with FB? If you can do any of these or FB with ADB, then you have a good chance. Just dont lose the HardSPL. If you give up after frustration and while grinding your teeth waving a white flag, flash the DREAIMG.img file, then you have given up root and FB. But at least you are at RC29, the level where the froot can be found. It is weird hanging out in Android 1.0 lemme tell ya. Feels so 1980'ish with bellbottoms in late decline.
But now its android time at CM with Phrash.
Later

[Q] ***G1 screenshot for your troubleshooting perusal!***

Hi guys,
*Information contained in screenshots*
Posted a topic about a non-rooted G1 with only access to fastboot and hboot.
I was told that I would have to flash a signed ROM to solve my problem but unfortunately, after proceeding through the full ROGERS G1 downgrade guide by Haykuro, the problem still persists.
The only thing that could have gone wrong during the rooting process is the installation of the wrong recovery through flashrec (it only allowed for remote install for a 32a install).
Here is a screenshot of the phone in hboot for you to get all the info (spl, radio etc.) and a pic of the phone's screen past the splashscreen.
Anybody know how screwed I am?
adramelch said:
Hi guys,
*Information contained in screenshots*
Posted a topic about a non-rooted G1 with only access to fastboot and hboot.
I was told that I would have to flash a signed ROM to solve my problem but unfortunately, after proceeding through the full ROGERS G1 downgrade guide by Haykuro, the problem still persists.
The only thing that could have gone wrong during the rooting process is the installation of the wrong recovery through flashrec (it only allowed for remote install for a 32a install).
Here is a screenshot of the phone in hboot for you to get all the info (spl, radio etc.) and a pic of the phone's screen past the splashscreen.
Anybody know how screwed I am?
Click to expand...
Click to collapse
you're not screwed at all if you can fastboot. esp. on an unrooted g1.
do me a favor, on the screen with the exclamation point, open your keyboard and push ALT+L.
That'll get u a menu, do a data wipe.
Thank you! That solved it but now everytime the phone is turned off and is turned back on. I get to that famous screenshot of death.
Any clue?
Thank you for your reply! Much appreciated.

[Q] Possibly Bricked Sensation Help Please!! (Noob)

Hello all, I'm hoping there are some sincere members will to help out a total noob.
I picked up my sensation and stumbled upon this website, in order to find a way to "jailbreak" my phone (I use that term lightly, I was a previous iPhone user and so far know very little, if nothing, about android development.
Lets get to it, to start I was attracted to installing this rom.
http://forum.xda-developers.com/showthread.php?t=1098849
At the time of noticing this post, my phone was brand new-- I read carefuly and understood that I should follow this post.
http://forum.xda-developers.com/showthread.php?t=1192300
I correctly (to my knowledge) Installed S-Off, ClockWork, Root, SuperCID..
While waiting for the Revolution rom to download, I started fooling around with my phone, noticed I was having Wifi errors -- would not connect, constantly trying to obtain IP address..
So heres where I think I goofed, I preformed a factory reset from my device, completely wiped the SD, -- did not fix wifi problem. I returned to the post about installing S-off, CWR, etc...
And understood that, "IF YOU ARE EXPERIENCING WIFI ERROR.
Currently the only way to fix this is to flash Stock Rom again or Custom Rom."
I then proceeded to follow STEP 4 in that guide in attempt to reinstall stock rom.
I was directed to this thread
http://forum.xda-developers.com/showthread.php?t=1074559
and downloaded
RUU_Pyramid_BM_1.35.666.1_Radio_10.50.9007.00U_10. 12.9007.21_2M_release_200555_signed
As I understood BM to stand for Bell Mobility (my carrier).
I went through the process, failed. I now have a black screen with HTC logo in the middle with exclamation marks in all four corners. There is a progress bar that is at approximately 90%. No matter what I've tried I cannot return to the boot menu.
At this point I am almost certain I've bricked my phone (fail), but if theres any possible way of fixing and returning to factory settings and fixing my wifi error I would greatly appreciate any help.
If I'm pretty much screwed I'd like to know where to go from here? Will I have to purchase a new phone.
Apologies if this post has been covered, (I did search the forums) but I've grown desperate and am certainly worried.
Please Help!!! What do I do?
sounds bad...you cant get to the fastboot menu at all? not even after a battery pull?
No, not after a battery pull or sdcard switch (idk if that does anything or not, but I tried it.)
hmmm....methinks its bricked...and we have no jtag or download mode :/
the only other option it to try to flash an eng hboot for fastboot commands, or an older RUU from the sd card.
it seems to me the only course of action is using a pg*****.img from the sd card and keep trying to access fastboot, or just return for repair
when its in this htc logo with exclimation screen, can you run ANY adb commands?
I'm going to try an older RUU, and no I cannot run any adb commands because the command prompt flashes for only a second.
One thing, when I pull out the USB
PVT Pyramid S-OFF
HBoot 1.17.0011
Radio 10.12.9007.21_2M
eMMC-boot
*date/time*
RUU
will flash on the screen for a moment, this is the only time (other than battery out) when it is not on HTC Logo with exlamations..
(soo bricked yeah?, feels good man.)
Obviously my warrantee is voided right, so how can I send in for repair? Will I end up having to purchase a new phone?..
dont just run a .bat or exe for commands, go to run>cmd and type commands manually, and see what it returns, espicially if you get return on "adb device" (no quotes)
also, if it shows the software info, it *should* flash any RUU/recovery files on the sd card, and then you can use CWM or TWRP to get a little farther...
im dl'ing an RUU to lookin to something else that might help, but if you dont mind a little work, you might be able to get it going again
if its easier, just pm me and i can help you out of the threads, with quicker response
Anything I can do to get it working again, just remember I'm really new, I'll catch on quick, but I've only been at this stuff a day! Also wanted to thank you properly, since I have yet too. So thanks for the help so far.
So, silly me, I can somewhat run adb commands now. But adb is not showing my device, however I type the commands
"fastboot reboot-bootloader"
"fastboot reboot"
and it reboots it, but returns it to the exclamation screen,
"fastboot getvar cid" seems to also be working, (I only know limited commands, from the tutorial)
awesome, that means you still have a chance!
ok gimme a moment, im checking something as we speak
EDIT* also, thanks for the "thanks"
ok try these commands (though they might not work on your hboot) and reply the output:
fastboot oem partition_test
fastboot oem test_emmc
these are to make sure there are no issues with any tables
also is this a bell sensation? if so, you will have to superCID to install the latest EU RUU, which may solve all your problems
also, this is the easiest way to flash an RUU for you (MUST BE SuperCID!):
http://forum.xda-developers.com/showpost.php?p=11441747&postcount=1
Output..:
C:\adb>fastboot oem partition_test
... INFO[ERR] Command error !!!
OKAY [ 0.019s]
finished. totla time: 0.019s
C:\adb>fastboot oem test_emmc
... INFO[ERR] Command error !!!
OKAY [ 0.021s]
finished. total time: 0.022s
And yes, bell sensation.
blerg, i thought it might output the errors, but thats more of a pc issue, not the phone
give the manual RUU a shot, seems to be the easiest/best chance atm, but try to supercid first
http://forum.xda-developers.com/showthread.php?t=1192300
go to step 4
I will give the manual RUU, which RUU do you suggest I try?
RUU_Pyramid_HTC_Europe_1.45.401.2_Radio_10.56.9035 .00U_10.14.9035.01_M_release_208857_signed
bottom of the list in the first post
http://forum.xda-developers.com/showpost.php?p=13698101&postcount=1
So I actually downloaded
RUU_Pyramid_HTC_Europe_1.24.401.1_Radio_10.39.9007 .00P_10.11.9007.09_M2_release_190934_signed
and ran it off my desktop and it restored my phone ! Yay! So its working fine right now (I think there was just an issue with the BM RUU) .. except for the wifi... my wifi is still not working...
Thanks for you help again.. You got my this far, so if you're ready to give up on me go ahead, but I would really like to sort this issue out..
Not quite sure where to go from here, but so thankful the phone is not bricked!
Should I update to the one you posted? I had previously downloaded this
this RUU is better, as for the wifi, lemme find the best wifi fix patch for ya
lol im also at work right now and VERY bored, so this is an excellen time killer
also, this RUU might fix the wifi problem, but if not, you will need to install clockwork recovery or teamwin recovery to flash the .zip of the wifi fix
EDIT* also, try turning off fastboot, reboot the fone, then wipe dalvik cache in recovery and boot back in, then check the wifi
if the wifi still doesnt work, give this a shot:
http://forum.xda-developers.com/showpost.php?p=15867636&postcount=42179

I wiped my OS by mistake…

Hi everyone. I've got some trouble with my phone (HTC One A9s) and I really hope there's somebody out there who could help me, I'm kind of desperate.
I've got TWRP recovery, unlocked bootloader and S-ON.
So here's what happens: I had been flashing some stuff on my phone with TWRP recovery, and hours after that, my SIM card just stopped getting any signal. My cell phone only said "No service" "Emergency calls only". So, thinking it happened because of the things I had flashed (it was just emoji updates for my keyboard, I really doubt now that it caused the problem), I started looking for solutions. And I made the worst mistake ever: I started wiping some stuff on TWRP recovery… and then I realized I also wiped the OS. So obviously now I can't turn on my cell phone, I can only boot it on TWRP recovery, download mode or bootloader. Since HTC One A9s is a pretty rare model, there's not much information about it on the internet. But I could find some stock ROMs in .zip format, and I tried installing them one by one by renaming them and putting them in my external SD card and entering download mode. None of them worked. One showed a CID mismatch error, another one showed a MID mismatch error, and the other two showed RU header errors.
So now I've been trying to figure out what I could do:
1. I could try to install the ROM that showed a CID mismatch error if I could modify the CID itself, but I can only do that with S-ON, and I can only get it if I have root and the cell phone on, which I can't do because I have no OS.
2. I could keep looking for a stock ROM that actually worked, but I think there aren't any more apart from the ones I already found.
3. From what I've read, I could try to edit the android-info.txt file of the ROMs that showed a mismatch error, but I just don't know where and how to find that file.
I really really need help please. I'm desperate, I know I made a huge mistake and I don't know how to fix it now. Please help me :crying: :crying: :crying:

Categories

Resources