Hello guys I have a new problem...
Yesterday I bought a cheap T-Mobile G1 as a replacement for my HTC Sensation. It was rooted and it had a "official pershoot sapphire'' or something rom. I wasnt fully satisfied with it so I wanted to flash a Sense Rom. So I Dled Sense_LX2.7 and flashed it through the recovery after wiping the cache, battery and dalvik and stuff. i thought this would be good enough cause this was the way I used to do it with my HTC Hero a couple months ago and that always worked. But now after flashing the rom, it stucks at the T-Mobile G1 bootscreen. Flashing another rom wont work. What am I doing wrong guys?
check ur radio and spl versions???
all the roms here have these warnings....which versions would support it....
check that by turning off the device, press camera+power....
SenseXL use these SPL/radio
This rom should be used with 2708/2825 + 1.33.0013/0013d(Recommended)
Click to expand...
Click to collapse
From the sound of your problem. You do not have the correct SPL/radio. As alokated said. Check your SPL/radio. Then flash them using ezTerry process.
and make sure to wipe everything before flashing another rom....
G1 freezed at white screen!
Hi all,
I really need a help here. I have a G1 rooted with CM rom ver5. it was working fine since 3 months but suddenly now the phone doesnt boots up, it goes to white screen with 3 droid skaters and highlight on Hboot. It is freezed then and nothing can be done. I removed battery and tried booting by home + power ; camera+power etc etc . nothing happens it goes to that screen only. i have amons recovery and also nand backups in sd card. but the system doesnt let me go any where!! Please help......
Related
Hello,
I managed to install the CyanogenMOD recovery image through flashrecc 090909.
I wiped all the data and following another tutorial I installed directly cyanogenMOD ROM 1.4.xx. I restarted the phone and it won't boot, the Orange logo remained there for 40 minutes, after which I restarted it.
I wiped all the data again.
I installed update.zip, the phone restarted and the recovery console popped automatically with the message Formatting CACHE, and it's doing that for an hour and counting.
What should I do?
Did I bricked it? or is it a soft brick, if so how can I make boot? ANY ROM, not specially the cyanogenmod.
Hope I didn't bought me a 250Euros paperweight :|
Thanks, ARthur.
A link to the the tutorials you followed could help me in seeing where you went wrong. From reading it, the part that confuses me, is the Orange Logo. Of which are you speaking of?
what was the update.zip you installed, it sounds like the htc image or the radio or maybe an spl, after you can use the recovery console (basically like 30 seconds of formatting cache on the screen) you can flash the rom.
The Orange Logo is actually the main Android software's image. When you turn it on, depeneding from where you bought it, the operator logo/company usualy is onscreen.
(Before you see the android logo)
BUT I think I was to in a hurry, I have the Dev software now workingm I fell asleep and now it works, just have to try the same with CyanogenMOD.
update.zip is the HArdSpl / older HBOOT
m3s_4ev3r said:
The Orange Logo is actually the main Android software's image. When you turn it on, depeneding from where you bought it, the operator logo/company usualy is onscreen.
(Before you see the android logo)
BUT I think I was to in a hurry, I have the Dev software now workingm I fell asleep and now it works, just have to try the same with CyanogenMOD.
update.zip is the HArdSpl / older HBOOT
Click to expand...
Click to collapse
Best thing you can do is a complete reinstall of the spl radio and of course the rom i recomend using a old cyanogen mod this should fix and problems if nt unroot and reroot the phone hopefully wont come to that
I'm new to this whole flashing custom ROMS business. I have a CDMA HTC Hero 2000 and I downgraded to the original 2.1 before the update just fine, rooted my phone just fine. Then I tried to flash Aloysius to it using instructions I found here: [Complete Guide] How To Flash A Custom ROM To Your Android Phone With ROM Manager + Full Backup & Restore | Android News, Reviews, Applications, Games, Phones, Devices, Tips, Mods, Videos, Podcasts - Android Police
After all was said and done, my phone starts to boot with the "HTC quitely brilliant" logo, following by "SPRINT the Now network" logo and after it shows "Now" for many seconds (as it normally does before pulling up the home screen), it reverts back to the HTC logo and repeats this process until I remove the battery.
I removed the microSD and attempted to boot, same thing. Then I held down HOME+BACK+POWER to do a manual hard reset, this took a little longer but again had the same result.
I may just cry now. Please help!!
Run the official sprint ruu, and see what that does for u. Then read the rooting guide here on xda and try it. I personally recommend amon ra recovery to flash roms, rom manger never seemed to work right. Feel free to pm for more help, dont worry u prob arent bricked unless u flashed a gsm rom (which aloysius isn't)
Sent from my HERO200 using XDA App
That's a bootloop not a brick You could try downloading a different rom and flashing it in recovery, nandroid restoring - if you made one, or flashing the same rom again. just wipe your phone before (data/cache/dalvik)
Didn't get a chance to get on here until now but I fixed it last night.
I did this by going back into reboot recovery mode (by pressing HOME and POWER), going to partition settings, COMPLETELY wiping everything on the sd card, mounting the USB and dragging a new ROM .zip file onto it. (I tired this twice without completely wiping and the phone continued to have problems booting.
The flash worked fine that time and all has been well. Turns out the first one I was trying to apply to it was just an upgrade.
Thanks everyone for your help, makes perfect sense now.
chrisdegraw said:
Didn't get a chance to get on here until now but I fixed it last night.
I did this by going back into reboot recovery mode (by pressing HOME and POWER), going to partition settings, COMPLETELY wiping everything on the sd card, mounting the USB and dragging a new ROM .zip file onto it. (I tired this twice without completely wiping and the phone continued to have problems booting.
The flash worked fine that time and all has been well. Turns out the first one I was trying to apply to it was just an upgrade.
Thanks everyone for your help, makes perfect sense now.
Click to expand...
Click to collapse
Four key words to remember when trying out any new rom
Nandroid is your friend!
additionally, you should always remember to wipe before loading a new rom!
Enjoy!
Yeah, don't ever panic, that was, as everyone said, a bootloop by textbook definition. I've never seen a brick before, but I'm damn sure it won't get as far as the Sprint logo. The only way to brick a CDMA Hero is to flash a GSM Radio/Bootloader to it.
First I have searched and searched and can't find anything similar to my problem.
G1
CM 5.0.8
RA 1.7
DangerSPL
I had cm5 running on my phone just fine for the last month or so and today my battery was about to die so I shut my phone off and when I went to turn it back on it sticks on the G1 boot screen. I can boot into recovery and fastboot but it will not but past the first boot screen. Is this something I did? Is there a way to fix it without starting scratch?
Did you backup your ROM? If yes, try restoring it.
I just re-flashed the ROM and it works fine. But I did a wipe and my screen saver is the same and google apps is still installed? Is that supposed to be like that after a wipe?
When you re-flashed your ROM and you did not do a full wipe of your data everything stay.
I did do a full wipe, catch, and everything and just flashed CM5 not the G-apps flash and I still have it along with the wallpaper being the same don't really know if this is relevant to the ROM but as far as I know when you wipe it puts the phone back to factory besides the recovery, radio, and SPL. Google apps can't be a part of the ROM either so I'm actually confused.
Oh and I re-partitioned my SD as well before the wipe so I pretty much started fresh but in all reality I didn't?
sometimes google backs everything up so when you re-flash to anything with same firmware as your last rom, and once you sign into google it will automatically install apps you previosly had and restore some settings such as Backgrounds and stuff... since you flashed the same exact rom, im assuming once you signed into google it just had your previous settings saved and restored it like a good friend would
HAHA made me chuckle! Thanks for the help guys! Glad to know google is my good friend! Still confused on why it just crashed like that :/ but as long as it's fixed is all that counts and not bricked
Hmmm.. When I did a full wipe of mine and flashed a new android version, I had to re-install all again!!!! and some of my data was also lost
boscharun said:
Hmmm.. When I did a full wipe of mine and flashed a new android version, I had to re-install all again!!!! and some of my data was also lost
Click to expand...
Click to collapse
Yes that would be correct.
htc dream stuck on boot screen
hi
i was tryng to update my htc dream rogers, firstly i used wrong dreaimg.nbh file my rogers changed into t-mobile g1, then itried again i was installing spl then phone stuck on sartup tmobile g1 screen, nothing works Home + power, Camera + power , power, dosen't work tell how to recovery my phone..
it just stuck on t-mobile g1 screen..
plz hepl me....
nothing is working tell me how to start it back, when sipmle powetr on or try to do any reset it just stuck on g1 start up screen.... plz plz help me ............................... it just stuck on t-mobile g1.... nothing happen...........................
Sorry for bad news, but I suppose you created a brick, i.e. there is no chance to re-animate your phone except with JTAG ...
can he still flash an nbh file? maybe try the orange nbh to re-flash via fastboot? or will it not let him do that because he has wrong/stock software installed?
Yep. No fastboot after Power+Cam. Sounded like a bad news brick indeed.
Hello !
I wanted to install EXT4 2.1.3RC4 but i don't understand what makes it messed up .. It actually shows that it is installed and then when it reboots and returns to the Recovery, there is a problem with the Recovery - like sometimes all the text is disappeared or sometimes the screen is blank !
PLEASE HELP ME OUT WITH THIS PROB
and yeah there is one more prob with my HTC Incredible S .. i tried to flash custom ROMs but some of them were stuck in the first boot after installing the ROM in the Recovery .. It's actually gets stuck in boot loop .. The HTC screen appears and after sometime it reboots and again the HTC screen appears .. This happened for like most of the ROMs i tried to install ..
PLEASE HELP ME OUT WITH THIS PROB TOO
hmmmm, install 4EXTRecovery 2.1.0 the final one... and check if that works, and then try to flash a stable ROM, (maybe a sense 2 Rom)...
actually i wanted to go for Sense 3.0 ...
and yeah 2.1.0 version works fine in my cell !
The issue has been resolved...
It seemed that he could flash roms with sense 2.0 or 2.1 without any problems, but then he couldn't flash the 4ext recovery, as it did not seem to work, all it would do is give a blank screen, wherein the recovery would run but the text wasn't visible at all...
He first formatted his SD card...
Flashed 4extrecovery 2.1.0 final version. And it worked...
Next he flash VU 2.35 ROM. And power off the device after the flash from the recovery itself.
Went back into recovery again (keep in mind he hasn't started his phone, it actually ends up in boot loops) and flashed the unity v3 kernel.
Power off Tue device again and power on... Voila!!! It worked....
Some cpu's tend to be a little diff. than others. So some can bare the alterations made to their frequencies and voltage while others can't. Hope it goes well with all the IncS users....
P.S. Helped him out chatting online
The fix u asked for the backlights....
Edit: works on 2.37.... Confirmed
Rizzu user hope the phone is fixed and running well now
I tried to flash the boot image for my first custom rom using easy kernel flasher, and my Vivid is now stuck at the white HTC screen. I then realized that I had used rom manager to flash CWM, even though I had already flashed the custom CWM from the superguide. Is this what caused my phone to hang at the HTC screen?
Is it safe to pull my battery? What is the next step, repeat step 2 from the superguide and then reflash the new kernel and rom?
I apologize if this has already been answered, I just haven't seen this exact question elsewhere and I don't want to pull my battery without being sure that I won't brick my phone or make my problem worse.
Rom manager does not work for our phones. That is why your phone is stuck. I remember another post like this. The guy pulled the battery and flashed the new cwm image without rom manager and it worked. I believe you would start at step two to correct your issue. Let us know how it goes for you.
Ok I pulled the battery and put it back in and now it won't boot at all. The power light flashes orange and then nothing happens. I'm getting a bit more worried about this now.
androuglas said:
Ok I pulled the battery and put it back in and now it won't boot at all. The power light flashes orange and then nothing happens. I'm getting a bit more worried about this now.
Click to expand...
Click to collapse
Alright, so I just did the same exact thing you did... updated CWM from ROM manager and tried to backup the ROM, hung at HTC screen. I haven't gone through the steps to reverting my CWM yet but I did get it to boot. Pull the battery, put it back, boot into HBOOT and let it do its thing, go to fastboot and then reboot. Give it a minute. Mine came back, set for a while at the boot image but it came back.
I just did the whole thing again but with out the HBOOT process and it worked too. Didn't take nearly as long as before at the boot image. Try both or see if you can't get to recovery from HBOOT. I'm pretty new to the Vivid since this is my wifes phone and its a lot different from my Inspire, the process of everything that is
Now reading your 1st post again, I didn't do the exact thing you did but close...
I tried again and it went in to h-boot, and i was able to reinstall the custom vivid CWM. But now I'm not sure if the kernel flash which started all this worked. Is there a way to find out while in recovery?
Should I reboot the phone now, or just flash the rom I was planning on flashing originally? Or should i try to return everything to stock and start all over?
cbronson41 said:
Alright, so I just did the same exact thing you did... updated CWM from ROM manager and tried to backup the ROM, hung at HTC screen. I haven't gone through the steps to reverting my CWM yet but I did get it to boot. Pull the battery, put it back, boot into HBOOT and let it do its thing, go to fastboot and then reboot. Give it a minute. Mine came back, set for a while at the boot image but it came back.
I just did the whole thing again but with out the HBOOT process and it worked too. Didn't take nearly as long as before at the boot image. Try both or see if you can't get to recovery from HBOOT. I'm pretty new to the Vivid since this is my wifes phone and its a lot different from my Inspire, the process of everything that is
Now reading your 1st post again, I didn't do the exact thing you did but close...
Click to expand...
Click to collapse
Thanks man. I got into recovery and fixed the CWM problem, but now I'm not sure what kernel I have running so I don't know if its safe to reboot.
Though I know how to use CWM I couldn't tell you how to check your kernel and whatnot from there. Best thing I can think of, or what I'd do, would be to wipe everything out and restore a nandroid, granted if you have one I've never really messed with kernels untill now so I don't even know if that would work
I realized I could just reflash the kernel while I was in recovery. It hung at the htc screen on the reboot like before, but i just pulled the battery, went back into recovery, flashed the rom, and now everything is working perfectly with the new rom. What a relief.
I think the original kernel flash may have actually worked, and I just freaked out when it hung at the htc screen and assumed it was because of the rom manager/cwm thing. It may have been fine all along.
Here is something that will help with flashing kernels.
http://forum.xda-developers.com/showthread.php?t=1423151
Flash Image GUI
ok i did the same thing awhile ago, i flashed new CWM then insatlled rom ...the Kernal did load thats the reason you got the white screen ..so just go ahead and load your rom you should be fine