A bit stuck here. I have a MyTouch which I previously rooted using a goldcard and had installed a Hero ROM on it. This worked fine but performance was terrible, so I attempted to go back to a simple ROM I found on these forums.
After installing the new ROM, the phone booted up but froze on the splash screen. This has been the situation ever since:
Back+Power gets me fastboot. Can use fastboot to talk to device.
Any attempts to "fastboot boot" a recovery rom results in reboot to splash screen.
Any attempts to Home+Power to go to recovery rom after fastboot loading it results in splash screen.
While in fastboot, 'adb devices' returns nothing (is that normal?)
Since I can still get to fastboot I have hope that this can be fixed without sending it in, but everything I can think of to try just puts me back on the splash screen.
I've already had to pay for repairs once, would love not to do it again. Please help?
Yeah, you should be ok if you can fastboot. What's your current radio and spl? If you're coming from cursor is it possible that you still have a hero radio spl combo installed and therefore 32a recovery Roms won't work? Or if you've already reverted to a magic radio spl then are you sure you're using the magic recovery and not the old hero recovery?
I tried something similar. I couldn't boot to any new AmonRA recovery ROM, but I tried an older version (v1.3.2 I think) and finally it booted to that recovery ROM. After that I could flash SPL to xx.2010 and flash to a new ROM. After I got new SPL and ROM, I could boot to the newest AmonRA recovery ROM (v1.5.2), but for some reason I've never been able to flash the recovery ROM
im going to hazard a guess here and say this is due to having the hero rom normally requiring you to have ur sd card formatted into fat32 ext and swap! i imagine you have gone ahead and flashed a new rom without re-formatting these, as this will cause rom to BOOT LOOP, and secondly have you wiped data/factory reset before flashing new rom
redmdc said:
im going to hazard a guess here and say this is due to having the hero rom normally requiring you to have ur sd card formatted into fat32 ext and swap! i imagine you have gone ahead and flashed a new rom without re-formatting these, as this will cause rom to BOOT LOOP, and secondly have you wiped data/factory reset before flashing new rom
Click to expand...
Click to collapse
This sounds very likely that this is the problem ...
if you say what hardware you have so we can maybe help?
had the same issue
had to flash sappire.nbh
the run relentess rooter v1.2.3
then upgrade to latest version v1.5.2
good luck
try and not power into fastboot FIRST, instead, try booting into RECOVERY FIRST AND FLASHING A ROM FROM THERE (has to be on the SDCARD...) tell me how it goes ok?
Related
Okay, so here's my issue. I have a Mytouch (Tmobile branded) and I was following a guide on the internet for how to root it and install custom roms and somehow in the guide I downloaded and flashed the recovery image with recovery-RA-dream-v1.2.3.img instead of the freakin' mytouch specific recovery image. I have found the right one now but the recovery image is loaded and I don't know how to change it if I can't boot into my phone. I can get to the recovery partition and it can wipe my phone and restore default, etc. but it won't load any custom ROMs. How do I load the proper recovery image? Like from a terminal or something? My phone isn't bricked is it, at least hard bricked?
Well it looks like I might be able to do this from terminal, like flash the recovery partition with the correct one on the sd card. Any way of how to do this, or what I'd need to put in the terminal?
Heyyyyy, I figured it out! I just loaded a SAPPIMG.nbh image and I'm going to reload the recovery from there. Thanks though haha I like figuring it out for myself anyway. The symptoms of this issue before I noticed the build was wrong was it wouldn't get past the green HTC MyTouch screen, even after 30 mins. Hope this helps you all.
Okay so I'm back again, this time with the recovery image RA-sapphire-v1.6.2G and it's not loading cyanogen roms. I can boot into the recovery and all is well until I try to load a custom rom. I reboot and all it does is hang still on the Mytouch logo, and I waited over 2 hours so it's not me being impatient. When I flashed the accidentally wrong dream recovery image did I change the radio with it? What am I doing wrong?
I'm mildy retarded sometimes. I was trying to install the update.zip over nothing instead of the 1.6 base. It's working now. The guide I was using just sucked. Love it! Thanks guys for all your hard work!
I flashed the radio that's given in the CM7 Alphafied Kang 9 and used this method to flash the radio:
http://forum.xda-developers.com/showthread.php?t=1178143
now it's stuck on the HTC screen and when I go to the bootloader it just tries to flash the radio again without letting me do anything else. I'm really sad cause I just lost my job and if this gets bricked, idk what I will do
Ok so I took the SD Card out before going into the bootloader and now I have command of it. Should I do a factory reset? I tried doing a recovery but is only giving infinite boot loops.
I would just wipe everything and flash a different radio.. I would also pull the battery, then try recovery again...
Fixed it. Everythings cool now. Thanks!
hello, I have a problem with a desire s phone which keeps booting into recovery mode when i turn it on. here's my step by step of what I did that got me into this predicament.
the phone had a stock 1.48 asia rom 0.98.0002 bootloader locked, and unrooted. so first I ran revolutionary had no problems there, had a revolutionary logo on my bootloader afterwards and the bootloader version was now 6.98.0002 or something I forget. anyway the next thing i did was I downloaded the stock euro rom 2.10.401.9 and extracted the rom.zip then renamed it to PG88img.zip copied it to the memcard ran fastboot, then fastboot automatically installed the zip after installation restarted the phone, now the phone was stuck on the white htc screen, so I ran recovery press the power and vol up and did a factory reset, had no luck with it still stuck on htc screen, now after reading a lot of threads, downloaded the ENGpg88img bootloader flashed it using fastboot and it was successful, the revolutionary logo was gone and the bootloader was now 6.98.0000 ( PG880000) but now when I rebooted the phone it would go directly back to recovery!! So the next thing i did was ran the euro rom again from the memcard thru fastboot and it updated the bootloader to the newest version and had a "locked"on top of the screen, so i did a boot unlock using htcdev and now its unlocked, then downloaded the clockwork recovery for saga then flashed it using fastboot with no problems. so now when I turn on the phone it goes straight to clockwork recovery! So last thing I did which also failed was I downloaded a pre rooted stock rom euro 2.10, placed it on memcard installed the zip from clockwork recovery then wiped all the data, dalvik cached and all then rebooted. But it still went back to clockwork recovery now I'm stumped. Really need help on this one.
long story short, I can only use fastboot, and if I use clockwork mod recovery to mount system i can do some adb commands. i also tried putting it in fastboot and ran an official RUu but I always get error 150. any help would be greatly appreciated.
It seems that your chip is gone. I have the same problem (boot looping) and had to try reclamation by phone provider. Find thread with "boot looping", or "white screen". You will find some software for a searching of your chip. Finaly all depends on your mobile vendor
yeah i thought it was the chip, but after 3 days of tinkering with it and reading a lot of threads i finally got everything back to normal. thanks for replying though zdech
batmite said:
yeah i thought it was the chip, but after 3 days of tinkering with it and reading a lot of threads i finally got everything back to normal. thanks for replying though zdech
Click to expand...
Click to collapse
Could you tell us how you solved it?
batmite said:
yeah i thought it was the chip, but after 3 days of tinkering with it and reading a lot of threads i finally got everything back to normal. thanks for replying though zdech
Click to expand...
Click to collapse
Hi, I have the same problem with HTC Desire.
Could you tell how you solved this please?
I don't know if he did what he wrote, but a big mistake was the last step.
batmite said:
So last thing I did which also failed was I downloaded a pre rooted stock rom euro 2.10, placed it on memcard installed the zip from clockwork recovery then wiped all the data, dalvik cached and all then rebooted. But it still went back to clockwork recovery now I'm stumped. Really need help on this one.
Click to expand...
Click to collapse
he installed ROM and wiped afterwards. Of course it fails at booting ;-)
If you really are in the same situation like him, wiping first and install ROM afterwards should solve the problem ;-)
Sent by my fingers to your head.
eyahl said:
I don't know if he did what he wrote, but a big mistake was the last step.
he installed ROM and wiped afterwards. Of course it fails at booting ;-)
If you really are in the same situation like him, wiping first and install ROM afterwards should solve the problem ;-)
Click to expand...
Click to collapse
Have to disagree with you there, what he said was
installed ROM
wiped DATA
wiped CACHE
rebooted
The ROM ZIP would have been flashed into SYSTEM not DATA, so wipe shouldn't have caused a problem
question is did BOOT flash ok?
I used Hasoon2000's HTC All-In-One Kit to root my phone. That all worked.
The issue came when i flashed a new kernel. I placed the boot.img from King Kang's new ROM (http://forum.xda-developers.com/showthread.php?t=1959099)
Anyway, When i boot I get the HTC, quietly brilliant logo, and this in red letters "This build is for development purposes only. Do not distrubute... "
i can boot into recovery (pwr+ vol down)
And i get the ***TAMPERED*** AND ***unlocked*** tags at the top
I don't know where to go from here...
Thanks for the help.
Also, whenever i boot into recovery or factory reset, neither succeed.
This was probably known info, just wanted to add it.
ccamwilkins said:
Also, whenever i boot into recovery or factory reset, neither succeed.
This was probably known info, just wanted to add it.
Click to expand...
Click to collapse
You mentioned in your original post that you could boot into recovery, so is that not working now? Factory reset might've fubared the recovery piece, so you could do one of two things:
1) download the original RUU version for your phone, relock your phone, and flash the RUU and start over.
2) try reinstalling TWRP.
This whole thing sounds like trying to install a kernel or fastboot flash a boot.img without SuperSU correctly installed. This is what happened to me when I first unlocked my phone and tried to fastboot flash the CM10 boot.img after failing the flash from recovery twice. Without that super-user permission, bad things tend to happen. If you decide to continue on with reinstalling TWRP, make sure SuperSU.zip is flashed successfully from
TWRP, then try your rom/kernel combination again (or even a different combination if you're apprehensive).
BEWARE: sometimes partially flashing these things can corrupt your sd card. I had to reflash the original RUU to fix my phone BEFORE I rerooted and flashed a rom/kernel.
Have you fastbooted a SU to your phone after you rooted and unlocked? I'd imagine you did if you followed the toolkit.. So your on 2.20... Just download cleanrom 5.1 on your computer. Mount sdcard via recovery and drag cleanrom onto phone. Flash entire rom in recovery. I bet it works
Once your on a stable rom, download king kang from your phone. Download flashgui. Open flashgui app, navigate to king kang and let it find the boot img and flash it for you.. Once successful, immediately boot into recovery and flash entire rom through twrp.
Success
Sent from my One X using Tapatalk 2
I have a one sv which:
is k2 ul
normally boots only to HTC screen (no quietly brilliant) and stays there till the end of times
shows tampered locked, which i now changed unlocked status (htcdev)
s-on
has twrp recovery on, but swipes fail mostly
flashing roms in twrp recovery show success but result is still HTC logo without being quietly brilliant
can not be ruu-ed beucause the ruus i find are i think older than required
hboot 2.21, radio 1.18 version
s-off fails because tho fastboot recognizes phone, adb doesnt in fastboot mode and in bootloader pc thinks it is not attached (tried xp, 7, 8.1 and many different drivers)
i am not sure if usb debugging was on before the phone crashed
so i can't put an older ruu because of s-on, i can't get s-off because rumrunner and moonshine can't work without adb, and basically that is it.
does anyone PLEASE have any idea what to do?
and yes, the warranty is over and the phone has gone to the warranty twice with bootloop before.
After flashing a rom, did you also flash the boot.img of the rom with fastboot cmd?
Thats necessary, because you are S-on.
And what TWRP is installed?
old.splatterhand said:
After flashing a rom, did you also flash the boot.img of the rom with fastboot cmd?
Thats necessary, because you are S-on.
And what TWRP is installed?
Click to expand...
Click to collapse
yes i did.
twrp 2.6.3.2
now i have made such progress that twrp tells me it cannot mount int sd and when booting, phone stays on the htc logo for some seconds and then switches off. i believe i have actually made it worse (didnt think that could happen).
EDIT: so i formatted the storage like this http://forum.xda-developers.com/showthread.php?t=2576897 and it BOOTED
EDIT2: the phone now kind of works IF it boots. half of booting times it just switches off, the other half it switches off and then reboots and works. i think something is still kind of not good but i dont have the b***s atm to poke it more.
thank you all for your potential help.
What rom did you use?
Please also perform a full wipe (without internal/external sd) in recovery under Wipe -> Advanced
old.splatterhand said:
What rom did you use?
Please also perform a full wipe (without internal/external sd) in recovery under Wipe -> Advanced
Click to expand...
Click to collapse
it was this one http://forum.xda-developers.com/showthread.php?t=2512742 which is, as i understand, your work, thank you very much, donations will happen when im a tincy bit richer
and i will wipe some time later when im at home and courageous enough.
You can also try to restore this TWRP backup.
great news! today the phone restarted itself and froze on the logo. i tried to start twrp but it froze on that logo too. tried to do a factory reset, which removed the "tampered" sign until next reboot but that was about it.
now i can't reflash twrp or anything at all, with the error remote: image update error. oh please save me again.
Does not sound good.
You can boot into bootloader? Is it locked or unlocked? Did you reflash the recovery to check if you can boot into it?
looks bad indeed.
i can boot into bootloader, which is unlocked. and please specify what do you mean by reflashing the recovery (pardon my stupid brain)
When in bootloader, connect your phone to fastboot and try to flash recovery again.
If you can't get into recovery, i don't know, if there is much i can do for you
fastboot basically tells me to go f* myself with the error "remote: image update error" what ever I try to flash. right now Im trying to find a way to reflash twrp from ext sd. not doing so great
Well, about your country flag i suggest you speak (or you can at least read) russian language.
Go to 4pda.ru and look for the posts of "MikG". He has made zip files, similar to RUU. They are flashed from bootloader/Ruu mode. Maybe they can bring your phone back to life.
I can't tell you how to use this files, because i don't speak russian.
I'll try, thanks.
edit: and it just refuses to cooperate. it kind of does something in bootloader, but still doesnt boot past htc logo or if i try recovery, it stays on teamwin logo. i dont know if im doing something wrong or what... maybe i'll wait for the 4.2.2 hboot 2.21 radio 1.18 ruu then because i really dont know what else i could do.