Related
I read these forums for a couple of days before I rooted, and have read them again for this problem for about 6 hours. I am unable to figure out what my situation is, and I'd like your help. Bear with me here...
I had successfully rooted my phone and loaded Cyanogen before the Google C&D (not sure of exact version number). For some unknown reason, my phone suddenly refused to accept phone calls and would send them to voicemail. I checked and rechecked all my settings, even disabling my voicemail altogether. I also noticed that many menu items also changed at this time. My send button no longer brought up the dialer, and my home button stopped bringing the phone to the home screen. Holding the power button only yielded options for reboot and power off. Airplane mode could only be accessed through the settings menu. I decided that I should unroot the phone and start fresh with Cyanogen's new instructions.
I downloaded sappimg.nbh and followed the directions here: http://theunlockr.com/2009/08/22/how-to-unroot-your-mytouch-3g/
This was successful, and when I booted again, it brought me to the screen that you get before you activate the phone. Now, I don't have a data plan, so I was unable to activate the phone with my google account. I decided I would go ahead and reroot the phone and follow the new Cyanogen directions using the original factory image first, then installing the new Cyanogen update on top of it to keep the original google apps. Here is where I discovered the problem: Holding HOME and POWER to get to recovery boot brings me to the very terrifying screen with the triangle/exclamation mark on it. At this point, while I realize there are still actions I can take, I want to make sure that this is ok before I do anything. I don't want to brick my phone, and I am already unable to get to the recovery boot.
Info:
SAPPHIRE PVT 32B SHIP S-ON G
HBOOT-1.33.006 (SAPP30000)
CPLD-10
RADIO-2.22.19.261
fishscale said:
I read these forums for a couple of days before I rooted, and have read them again for this problem for about 6 hours. I am unable to figure out what my situation is, and I'd like your help. Bear with me here...
I had successfully rooted my phone and loaded Cyanogen before the Google C&D (not sure of exact version number). For some unknown reason, my phone suddenly refused to accept phone calls and would send them to voicemail. I checked and rechecked all my settings, even disabling my voicemail altogether. I also noticed that many menu items also changed at this time. My send button no longer brought up the dialer, and my home button stopped bringing the phone to the home screen. Holding the power button only yielded options for reboot and power off. Airplane mode could only be accessed through the settings menu. I decided that I should unroot the phone and start fresh with Cyanogen's new instructions.
I downloaded sappimg.nbh and followed the directions here: http://theunlockr.com/2009/08/22/how-to-unroot-your-mytouch-3g/
This was successful, and when I booted again, it brought me to the screen that you get before you activate the phone. Now, I don't have a data plan, so I was unable to activate the phone with my google account. I decided I would go ahead and reroot the phone and follow the new Cyanogen directions using the original factory image first, then installing the new Cyanogen update on top of it to keep the original google apps. Here is where I discovered the problem: Holding HOME and POWER to get to recovery boot brings me to the very terrifying screen with the triangle/exclamation mark on it. At this point, while I realize there are still actions I can take, I want to make sure that this is ok before I do anything. I don't want to brick my phone, and I am already unable to get to the recovery boot.
Info:
SAPPHIRE PVT 32B SHIP S-ON G
HBOOT-1.33.006 (SAPP30000)
CPLD-10
RADIO-2.22.19.261
Click to expand...
Click to collapse
you can't really brick your phone when flashing a rom, well you can, but you have to try really hard. The same thing happened to me the first time. You can flash the recovery again using fastboot, if you had an engineers spl. Since you still have the perfect spl, you will more than likely have to do the one click root again. Just reboot the phone, and you will have the stock donut rom. Downgrade to cupcake, then do the unlockr's method again.
As tazz mentioned, this is no problem - by flashing the sappimg.nbh you also flashed the recovery and lost your root.
As this is the cupcake sappimg, what you need to do now is to go on with activation, then flash the recovery again using the 1 click method and go on from there.
If you do not have a data plan, try bypassing the google activation described here
flash recovery again if u can go into fastboot mode
I believe that I have cupcake (1.5), not donut.
So, if I understand correctly, unrooting the phone means I lose the ability to go into recovery boot using HOME + POWER. I am still able to go into fastboot when pressing BACK + POWER or VOL DOWN + POWER. However, I am not clear on whether or not I will be able to flash recovery using fastboot this way. If I just load a recovery .img file on the sdcard, will I be able to use fastboot to flash it? I was under the impression that I would only be able to do this if I could use recovery boot. Also, since I most likely do not have an engineers SPL, will this work? And finally, how do I check the SPL?
I should clarify when I say check the SPL. I mean, how can I be certain that the SPL I load won't brick my phone? As far as I know, uploading a new hboot is a good way to brick it, no?
u need to root your phone again.. when u installed the SAPPIMG.nbh u unrooted your phone.. now u need to root again.. being able to fast boot doesn't mean u have root.. a unrooted phone can access fast boot...
Got it working!
I was doing it correctly, I was just unable to get it to root at first. Took 3 tries, then I was able to boot into recovery mode. Thanks for all your help!
My magic was on the official sense UI, then yesterday I use the goldcard+RUU method to get it to something like this:
SAPPHIRE PVT 32A ENG S-OFF H
HBOOT-1.76.2007 (SAPP10000)
CPLD-12
RADIO-6.35.08.29
Aug 21 2009, 18:19:15
Then when I tried to flash a new rom, it got the error at line 2 and installation aborted. I was using fastboot trying to get the cm recovery on it. then one things led to another... I can't remember much coz it was really late at night I kinda dozed off.
Anyway, my magic is not stuck at the boot screen. No matter what I press: back+power, vol down+power, menu+power, it's STAYED AT the BOOT SCREEN.
Is there anything I can do now? I would be grateful if you guys can give me some instructions!
Okay, after reading more on the forum, I think I screwed up during the SPL flash. So, is that it? My Magic is bricked? I can just throw it to the trash now?
annalee said:
Okay, after reading more on the forum, I think I screwed up during the SPL flash. So, is that it? My Magic is bricked? I can just throw it to the trash now?
Click to expand...
Click to collapse
well, if you didn't flash the radio first, and then the spl ( what spl did you load, anyway?) then yea, it may be inescapable
this one: update-hboot-1762007-signed
how to determine if it is a real brick?
Thanks for reading anyway.
annalee said:
Okay, after reading more on the forum, I think I screwed up during the SPL flash. So, is that it? My Magic is bricked? I can just throw it to the trash now?
Click to expand...
Click to collapse
I performed a SPL flash, the phone rebooted ,it took long time rebooting so i got panicked i pulled out the battery ( wasn't a smart move ).
tried to start the phone.. now i was stuck at the first splash screen.
-pulled out the battery and back again start the phone... stuck at the first splash screen or boot looping endlessly,
-did all possible key combinations to get in fastboot, recovery mode... nothing.
-cried for help, got directed to a post similar to mo my case... worked for me hope it dose for everyone else.
here is what i did (followed):
-On the PC, i ran the command 'fastboot boot recoveryimage.img'.
-At this point the command says 'waiting for device' (or something like that).
-I removed the battery.
-I Connected USB.
-I inserted the battery.
-I booted the phone while holding the HOME key.
-The phone still froze at the first splash screen, but then suddenly, the waiting fastboot command detected the phone and booted the recovery image!
flashed again but this time checked step twice before i check it a third time, and flashed the SPL and radio and the rom.
thanks for posting ...
but this method doesn't seem to work on mine
i called htc care they said they might need to replace the motherboard?
Htc care fixed it for free and sending it back to me by dhl tomorrow (still free)
Hi all, noob here
I have a Nexus One which had v2.3.4 installed. I tried to unlock using the Amon_RA method WITHOUT having root access.
At first it looked that I got a successful unlock operation, but now when I try to re-start the device I can't get past the 'X' logo with an unlock image at the bottom. Sometimes the device vibrates a couple times, sometimes it doesn't
I don't know what to do, have tried downgrading to Froyo and redo things from there but I get nothing back.
Please help this poor noob fella, been stuck with one crappy feature nokia phone for the past couple of days now and it's driving me crazy. i don't care if I end up with a eclair, froyo, gingerbread system, unlocked or not, I just need a phone that works at all!
have you got a link to this method?
how are you trying to load froyo? an IMG file in hboot? if so what happens when you do that?
I followed a link I found here at xda, which I came across from search google, the exact page I don't have with me.
not fixed into froyo, just trying to get ANYTHING that works.
scotty, total noob here, how cant I get to hboot?!?!?
scotty, when booting to bootloader screen i get the 3 androids at the bottom and:
*** unlocked ***
NEXUSONE PVT SHIP s-ON
BOOT-0.35.0017
MICROP-0c15
TOUCH PANEL-SYNT0103
RADIO-5.00.00.04
Jun 14 2010, 12:02:27
FASTBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
now, i started to mess with my N1 as it started to act funny once I tried using a 8GB card
Really, ANY help is appreciated
hboot is gotten to by selecting bootloader from the menu you showed,or via power+vol down from a powered off state.
again,how were you trying to "downgrade to froyo"?
i dont have a nexus 1,so youre going to have to find that page again if i have any hope of helping you figure it out.
alternatively,you could post your questions here,in the nexus one android development forum. im sure someone there will know.
http://forum.xda-developers.com/forumdisplay.php?f=559
scotty I've tried loading FROYO on hboot, also by booting the phone with the VOL DOWN + POWER. It APPEARS as if the process of reading the passimg.zip file works, but then when i reboot I once again get to the 'X' + unlock image. SOMETIMES, the phone shakes about 6 to 7 times, a couple of times the camera flashes.
I have tried FRG33 & FRG83 on the thing.
any help is appreciated
Has bought from the USA of HTC Inspite 4g (AT&T). Wanted to receive Root, S-OFF, Rom manager with ClockworkMod. Has started to do to change an insertion. Has received goldcard. After an overload phone has started to change an insertion. This process proceeded 2 hours (in the end of process there was a black screen). I have decided to overload phone. Has stopped process. After that problems have begun. Root, S-OFF, Clockworkmod I have received. But after reboot of phone it does not work about 10 minutes. 5 minutes at it absolutely black screen, then the white screen with an inscription of HTC simultaneously work 3 minutes the motor, loading of 2 minutes then begins. Process of switching-on or reboot of phone proceeds 10 minutes. Tried to replace an insertion once again. After that changes nothing. Did before setting of an insertion full surep wipe. It has not helped. I still have a problem. I want to enter into engineering menu HBOOT. I push down+power. I wait for 5 minutes (phone so is overloaded). I enter in HBOOT, but thus buttons (volume up and down, power) any more do not work. As to me to receive normal phone. I can not HBOOT make in it recovery. Where to me to take for HTC INspire 4G (AT&T) PD98IMG.zip. Also help me with the instruction. How to apply this file in RECOVERY.
I'm having a hard time with your English (or is it just fed into google translate?).
It looks like you installed the ENG hboot on a later model device that is incompatible.
You need to get it to boot (it will eventually) and put the newer hboot back on it. You can do this through ADB from a console. Here are the instructions:
http://paste.pocoo.org/show/495273/
@ Gene Poole
I had a hard time with his English too, but I understand exactly what he is saying because I did the same thing. I will try to re-explain it and hopefully someone can help us out.
In a nutshell, it sounds like we both flashed an Engineering HBoot starting with a stock US ATT Inspire 4G that came with Gingerbread. Specifically, what I did was I followed a guide on Cyanogenmod's wiki for the Inspire 4G which gave direction to downgrade to Froyo, root, and setup to use eng hboot. This apparently was a huge mistake. After the downgrade, when rebooting or powering on the phone, nothing would happen for a long time (black screen for 5 - 10 minutes, i.e. phone was off), then, screen would turn on with white background and HTC logo and phone would vibrate non-stop for several minutes, and eventually, phone would turn on. After the downgrade and making it to the home screen, I copied CM7 zip on to the SD card and rebooted into recovery via adb. Same exact weird process happened with phone being off for several minutes, then vibrating, then eventually i made it to cwm recovery. After installing CM7 and rebooting, same crazy startup process and made it into CM7 home screen.
I was hoping once CM7 was installed that the crazy startup process would disappear but it didn't. I saw afterwards in a CM forum that this happened to someone else and they had asked if the wiki could be updated to point to the Ace hack kit guide to rooting the Inspire 4g (which mentions that eng hboot shouldn't be used with the phone I had as configured). I then rebooted into bootloader via adb and after crazy startup and fastboot did not work at all (fastboot devices returned nothing). Further still, no buttons work in hboot at all (Vol Up, Vol Down, Power).
At this point, I could still get into the phone, but I wanted to try to undo everything I did and start over using the Ace hack kit. I then tried to use the Ace hack kit to unroot the phone by using the ATT GB RUU. The process seemed to go pretty far, but after a reboot, the phone never came back, and that's where I am currently. If I start the phone, it does crazy startup but never fully boots...stays on white HTC screen forever...which means I can't use adb (to my knowledge). I was able to get to hboot by putting elastics around volume down button and waiting a very long time, but it looks like hboot is still the eng hboot because none of the buttons work and I can't use fastboot. I was hoping that as part of RUU flashing that hboot would be restored to original one. I put the RUU (PD98IMG.img) on SD card, but again I can't get to it because buttons don't work.
So, it sounds like spv4 above is in a very similar boat. I have no idea what else to try. Only thing I can think of is if it's possible to somehow modify an RUU to start automatically when getting to hboot without any user input.
If anyone has any suggestions, I am more than willing to try anything. Thanks very much.
EDIT: So, as I was typing this post earlier, I had been "sitting" in hboot the whole time. When I was done, I looked at phone and PD98IMG.zip was been applied to phone automatically! Don't know if this was common knowledge or not, but everything updated OK. When it was done, hitting the power button to reboot didn't work, but I just removed battery and when putting it back in, phone booted normally back to what looks like stock RUU. Hopefully this info helps someone else.
JayB059 said:
@ Gene Poole
EDIT: So, as I was typing this post earlier, I had been "sitting" in hboot the whole time. When I was done, I looked at phone and PD98IMG.zip was been applied to phone automatically! Don't know if this was common knowledge or not, but everything updated OK. When it was done, hitting the power button to reboot didn't work, but I just removed battery and when putting it back in, phone booted normally back to what looks like stock RUU. Hopefully this info helps someone else.
Click to expand...
Click to collapse
Great! Glad you got it back, but you could have saved a lot of time.
The main problem is that the ENG hboot (or pre-GB hboots) doesn't recognize something in the hardware of the new phones. The end result is that the hboot runs at about 50x slower. It eventually gets booted, and once booted to an OS (either the main OS or the recovery OS) it runs fine since hboot has exited and passed control to the OS. So anytime hboot is in control, things crawl at a snail's pace.
Because the OS runs fine and hboot has exited, it is possible to overwrite the hboot partition from the booted OS. That's what you are doing in the instructions that I posted a few posts back. Once the correct hboot is installed, all is fine.
I agree that someone needs to update the cyanogenmod wiki. It's way out of date.
I'm currently experiencing the same problem.
I followed the instructions on how to downgrade using a goldcard, successfully rooted and i also flashed TrickDroid on it, but every time i turn the device on i have to hold the power button for 20 seconds and wait 10 minutes till the HTC logo appears, then it takes 2 minutes vibrating and i seriously can't deal with this.
can you please tell me how to fix this?
Revolver95 said:
I'm currently experiencing the same problem.
I followed the instructions on how to downgrade using a goldcard, successfully rooted and i also flashed TrickDroid on it, but every time i turn the device on i have to hold the power button for 20 seconds and wait 10 minutes till the HTC logo appears, then it takes 2 minutes vibrating and i seriously can't deal with this.
can you please tell me how to fix this?
Click to expand...
Click to collapse
Find the fix in the guide in my signature....you need to have basic knowledge of adb commands. If you need further help just let me know. :good:
Moved to Q & A section.
Sent from my Galaxy Nexus using Tapatalk 2
Hi,
I need some help. I have 2 EVO's with similar problems, but different symptoms.
It all started when I tried to flash them to Boost using CDMA workshop! I know I should of stopped when i messed up the first one, but I'm a slow learner, and, I was successful with an EVO Shift, but the EVO 4G is a lot harder. Anyway, I now have 2 semi bricked phones and need some help.
The first one is stuck in the white screen bootloop, it comes on and shows HTC EVO 4G, goes black for a few seconds and then starts again. It has,
HBOOT 2.10.0001
RADIO 2.15.00.11.19
I have tried flashing a PC36img.zip from the sd card and I ran RUU image version 3.70.651.1, via USB cable which went through the entire process. The RUU says, Congratulations. Your ROM update has been completed. Your phone is now ready for use. At which time it goes straight back into bootloop.
The second phone has a black screen with htc in the middle and a triangle in each corner, it just sits in this state. It has,
HBOOT 2.16.0001
RADIO 2.15.00.85.02
When i run the RUU, it says if the phone has the 4 triangles, it means the RUU failed and rerun the RUU, which I have done with the same result.
I'm figuring I messed up something deeper than the RUU fixes, I realize i got way out of my depth on these 2 phones, the shift went so easily, I thought these would be the same.
I have read many forums and tried everything that has been suggested, with no positive results, any help would be greatly appreciated.