Related
Hey Guys,
A friend of mine has asked me to look at a Wildfire that has a problem with it. It takes ages to boot then the screen goes black and comes up with a force close to witch the phone doesnt respond then eventually reboots and starts again.
I can get access to HBOOT but the HBOOT is S-ON and as far as i know the ROM is not rooted. It looks to be the stock 3 ROM but of which version i dont know.
I have tried clearing the storage but this still doesnt work.
The device still has the stock recovery on it so no clockwork etc.
Is there anyway i can get a new ROM on the device and try to get it to boot.
The HBOOT reads:
BUZZ PVT SHIP S-ON
HBOOT-0.80.0007
MICROP-0622
TOUCH PANEL-ATMELC03_16ac
RADIO-3.35.15.31
Any help would be great appreciated
Dazman85
Dazman85 said:
Hey Guys,
A friend of mine has asked me to look at a Wildfire that has a problem with it. It takes ages to boot then the screen goes black and comes up with a force close to witch the phone doesnt respond then eventually reboots and starts again.
I can get access to HBOOT but the HBOOT is S-ON and as far as i know the ROM is not rooted. It looks to be the stock 3 ROM but of which version i dont know.
I have tried clearing the storage but this still doesnt work.
The device still has the stock recovery on it so no clockwork etc.
Is there anyway i can get a new ROM on the device and try to get it to boot.
The HBOOT reads:
BUZZ PVT SHIP S-ON
HBOOT-0.80.0007
MICROP-0622
TOUCH PANEL-ATMELC03_16ac
RADIO-3.35.15.31
Any help would be great appreciated
Dazman85
Click to expand...
Click to collapse
just flash cyanogen mod and try if it works (it should work)
http://download.cyanogenmod.com/get/update-cm-7.0.3-buzz-signed.zip
anonimo95 said:
just flash cyanogen mod and try if it works (it should work)
http://download.cyanogenmod.com/get/update-cm-7.0.3-buzz-signed.zip
Click to expand...
Click to collapse
You have to run unrevoked 1st http://unrevoked.com/
Then add any rom you want (roms are like pokemon gotta collect and play with them all)
I`ve just de-branded mine (hated the boot screen) and flash it daily with a new rom
anonimo95 said:
just flash cyanogen mod and try if it works (it should work)
Click to expand...
Click to collapse
How do i flash this with the stock recovery as unrevok doesnt find the phone as it doesnt boot into android
Thanks
Daz
Dazman85 said:
How do i flash this with the stock recovery as unrevok doesnt find the phone as it doesnt boot into android
Thanks
Daz
Click to expand...
Click to collapse
Turn the usb debugging on (on wildfire).
Go to settings/applications/development/usb debugging check box.
bharatgaddameedi said:
Turn the usb debugging on (on wildfire).
Go to settings/applications/development/usb debugging check box.
Click to expand...
Click to collapse
this isnt possible as the device will not boot into android. it gets past the boot screen then the screen goes black and shows a dialogue box saying process system is not responding, the phone freezes and becomes unresponsive then it will eventually reboot and start the process again.
is there anyway i can flash a oem rom on the device from HBOOT or any other method, the phone is NOT rooted, or S-OFF and does NOT have a custom recovery. It is a stock phone.
Thanks
Daz
Dazman85 said:
this isnt possible as the device will not boot into android. it gets past the boot screen then the screen goes black and shows a dialogue box saying process system is not responding, the phone freezes and becomes unresponsive then it will eventually reboot and start the process again.
Click to expand...
Click to collapse
Yes true.
Try to boot into safe mode. During reboot , just press and hold the trackpad just when it says HTC quietly brilliant logo untill a long vibration occurs. Maybe this will not solve the problem since it persisted even after hard reset. But give it a try.
I think if u get a single oppurrunity to boot into OS, u may flash the WWE ECLAIR ruu. Utilize if u get one.
Sent from my HTC Wildfire using XDA App
Hi,
I had a evo 4g lying around, power it on, but only HBOOT comes, Android doesnt load.
It doesnt have S-OFF, how shall I proceed
SUPERSONIC EVT2-2 SHIP S-ON
HBOOT - 0.79.0000
APR 2010
, Andriod doesnt boot up, the phone powercyles
I would try running an old ruu that matches the hboot. Then u can use the unrevoked method of rooting.
Sent From My Pocket
Thanks, any instruction on how to do this?
Which rru should I try?
How to flash rru?
funky12 said:
Thanks, any instruction on how to do this?
Which rru should I try?
How to flash rru?
Click to expand...
Click to collapse
Download and install the HTC fastboot drivers to your computer from
http://unrevoked.com/rootwiki/doku.php/public/revolutionary
Also, make sure HTC sync is not installed on the computer.
Download to your computer either
https://rs893tg.rapidshare.com/#!do...182851|R~07CB57D22079C8F4C3FEFB08CBF8423F|0|0
or
http://www.fileserve.com/file/MMtRakr
or probably this one.
http://www.fileserve.com/file/PckGRqz
These should be able to be rooted later using unrevoked.
Turn off the phone and connect the phone to your computer, then hold the volume down + power buttons at the same time. Hit the power button once the phone powers up and FASTBOOT is highlighted. It should now read FASTBOOT USB in red. Run either of the RUUs from your computer and see what happens.
^^^^ +1 ^^^^
Sent From My Pocket
UPDATE:
Thanks guyz, I loaded the HTC RRU ROM, it completed successfully, not my phone is stuck at "HTC evo 4G" white screen, adroid doesnt boot up, and in recovery too my phone is stuck at the same white screen
Any clue, how to proceed?
funky12 said:
UPDATE:
Thanks guyz, I loaded the HTC RRU ROM, it completed successfully, not my phone is stuck at "HTC evo 4G" white screen, adroid doesnt boot up, and in recovery too my phone is stuck at the same white screen
Any clue, how to proceed?
Click to expand...
Click to collapse
Volume down + Power button
What is your hboot version and radio number?
hboot - 2.16.0001
radio- 2.15.00.0808
mar 8 2011
Any Luck guys, can anyone help
http://forum.xda-developers.com/showpost.php?p=18399552&postcount=2
Then root the phone again using revolutionary.
http://revolutionary.io/
Concordium said:
http://forum.xda-developers.com/showpost.php?p=18399552&postcount=2
Then root the phone again using revolutionary.
http://revolutionary.io/
Click to expand...
Click to collapse
If the first step doesn't at least boot into the Operating system, or recovery with an exclamation point for you, then you may have a hardware issue.
shortydoggg said:
If the first step doesn't at least boot into the Operating system, or recovery with an exclamation point for you, then you may have a hardware issue.
Click to expand...
Click to collapse
It's very possible. This zip just completely wipes everything and, for me, was able to resolve a seemingly unfixable issue that I was having for almost two months. But yeah, if that step doesn't work then he will need to take it to Sprint.
I have a Dinc2 on Froyo. I had got S-off using AlphaRevX. No problems here. I got hold of Gingerbread 2.3.3 (PG32IMG_RUU_Vivo_W_VERIZON_WWE_2.18.605.4_Radio_1.09.01.0622_NV_VZW1.92_release_200325_signed)
Yesterday, when I flashed it it flashed Ok except that the Bootloader and TP were bypassed. Now I am unable to root it and if I reboot into recovery (the battery has to be pulled out and put back else it boots normally). If I select recovery it flashes one screen and then the second screen just hangs. The recovery screen is still Green (not orange). The phone is working fine in GB and the version is shown as 2.3.3. It is faster and the battery life also seems to be longer. I guess the Bootloader and TP were not installed since AlphaRevX had changed the version of HBOOT. I still have S-off.
Two questions:
1. Is there a way to fix this.
2. If I flash the Chinese ROM and go to 2.3.4 then will it fix the problem. Also, do all the files-ROM, Radio & GoogleApps (sequentially of course) have to be named PG32IMG?
You may have to find a new version of CWM, and flash via boot loader.
Although, I may be wrong. Hopefully you'll get more answers.
Sent from my Incredible 2 HD using Forum Runner
Ya load another recovery. Also try pressing the vol - and power when it goes to the second screen. I thought I bricked my of since and did that out of anger and the crappy normal recovery came up
Sent from my ADR6350 using xda premium
faehsemc said:
Ya load another recovery. Also try pressing the vol - and power when it goes to the second screen. I thought I bricked my of since and did that out of anger and the crappy normal recovery came up
Click to expand...
Click to collapse
No luck with <Vol> + <Power> from 2nd screen.
I was able to enter the HBOOT mode without having to pull the battery out. I took this chance to note the contents
----AlphaRevX----
VIVO_W XB SHIP S-OFF RL
HBOOT-6.13.1002
RADIO-1.09.01.0622
Apr 1 2011, 18:34:39
HBOOT
<normal three options>
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
HBOOT USB
IMAGE CRC
reload another recovery - sounds Greek + Latin to me.
@TYLERLAWOHN; where do I get the newer CWM.
It has been suggested that I do a factory reset and then reload. Seems that TP is the culprit. My query is that will a factory reset put paid to the prl and/or the crack (both CDMA and GSM).
http://forum.xda-developers.com/showthread.php?p=15981566
Choose one of these. It's cwm. Probably an older version but if it flashes the recovery then all you need to do is a restore
sgiitk said:
No luck with + from 2nd screen.
I was able to enter the HBOOT mode without having to pull the battery out. I took this
----AlphaRevX----
VIVO_W XB SHIP S-OFF RL
HBOOT-6.13.1002
RADIO-1.09.01.0622
Apr 1 2011, 18:34:39
HBOOT
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
HBOOT USB
IMAGE CRC
reload another recovery - sounds Greek + Latin to me.
@TYLERLAWOHN; where do I get the newer CWM.
It has been suggested that I do a factory reset and then reload. Seems that TP is the culprit. My query is that will a factory reset put paid to the prl and/or the crack (both CDMA and GSM).
Click to expand...
Click to collapse
Reply deleted
faehsemc said:
http://forum.xda-developers.com/showthread.php?p=15981566
Choose one of these. It's cwm. Probably an older version but if it flashes the recovery then all you need to do is a restore
Click to expand...
Click to collapse
Thanks for saving my bacon. Picked up the red. Installed recovery. Back to Froyo. Should I risk the Chinese 2.3.4, or will the AlphaRevX HBOOT again baulk me?
Don't know man, bit if it does you can re download the red and should be able to start over.
Sent from my ADR6350 using xda premium
I have finally managed. The full story is
1. Used the PG32IMG route for the Verizon version (PG32IMG_RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.4.zip) and the recovery (red). Of course had to disable fastboot etc..
2. Then installed the two superuser files. (su-bin-3.0.3.2-efghi-signed.zip and superuser-3.0.7-efghi-signed.zip) through recovery.
3. Had to get Astro file manager to get the apk installer going from SD Card.
4. Titanium Pro not installing, even with busybox installed it was the same.
5. Moved the Devanagri fonts to the system/fonts director, so obviously have ROOT.
6. Installed clockworkmod. It restored 26 apps. Only a few were missing.
Installed the latest freebie version of Titanium.
7. Ookla speedtest was not working so reinstalled it from Titanium.
System seems to be working fine. Faster and lower power consumption.
Still unable to save/restore contacts to from Google.
faehsemc said:
you have an Incredible S Hboot for the Inc 2... i think you need to look for a new RUU altogether and get the original Hboot back...
Click to expand...
Click to collapse
I have that same hboot and I never even smelled a DInc s ROM.
Are you sure that's a different one then yours?
I may be wrong but,
I think it's a Revolutionary hboot and unless you did the clip, it's the same as yours.
cac2us said:
I have that same hboot and I never even smelled a DInc s ROM.
Are you sure that's a different one then yours?
I may be wrong but,
I think it's a Revolutionary hboot and unless you did the clip, it's the same as yours.
Click to expand...
Click to collapse
You are right, It's the revolutionary... I was stupid and thinking that we need to downgrade from 98 to 97 and then thinking 97 was the hboot number...
Sent from my ADR6350 using xda premium
Yea watch vzw come up with a 1003 bootlocker.
Or try some kind or OTA AppHolized disabling of the SD card.
I'm having some trouble with an Evo I purchased from a friend. I knew it bootlooped before I purchased it. He has not used it in a long time and it looks like new.
Known Device details:
SUPERSONIC EVT3 SHIP S-ON
HBOOT-2.16.0001
MICROP-041f
TOUCH PANEL - ATMELC03-16ac
RADIO-2.15.00.0808
Mar 8 2011, 17:02:15
NOT ROOTED.
Symptoms:
Device will turn on and have the white HTC evo 4g screen, but will then power off and power back into the HTC evo 4g screen repeatedly.
Holding down and power boots into bootloader no problem.
GOAL:
To fix this device without upgrading the Hboot so that I may have s-off and root via revolutionary.
Any suggestions here?
Thanks in advance.
Download this file and run it from a windows computer:
http://tinyw.in/wGfq
It should flash your phone back to factory stock and keep the 2.16 hboot. Even if you were to get 2.18, it can be unlocked and rooted anyway. If you don't like that file, go to http://goo.im/stock/supersonic/ruu and pick your favorite one.
Thanks for your response, however my problem was actually fixed by wiping the data through the bootloader. Then I rooted via revolutionary so it.was actually really easy, hopefully someone else can benefit from this thread. I didn't think a data wipe would fix it but hey, I'm not complaining.
Sent from my PG86100 using Tapatalk 2
didnt work
noob here, RUU cant even recognize my unrooted EVO, wiping it only give me 5 minutes of phone use before boot loops started over. and i have to manually wipe the phone through bootloader. cant even access recovery. please help. HBoot 2.18.0001 please and thank you!
Hey Lunch.
Have you tried flashing a custom recovery? Is your phone even rooted yet?
Sent from my HTC EVO 4G running JMZ's CM10 ROM.
boot loop
Lunchbawckz said:
noob here, RUU cant even recognize my unrooted EVO, wiping it only give me 5 minutes of phone use before boot loops started over. and i have to manually wipe the phone through bootloader. cant even access recovery. please help. HBoot 2.18.0001 please and thank you!
Click to expand...
Click to collapse
I have had the boot looping issue for a few months now... could not access internet or gps without the phone rebooting. It had to be some sort of heat issue, because I did get the damn thing to work by turning my car's AC on high and holding my phone in front of the vent so I could use the gps long enough to tell the Road Rangers where the hell I was with a flat tire. I brought it in to a Sprint service center and they replaced it (just got it today) with a refurb no questions asked. IMO, If your phone has the same issue, no amount of wiping and recovery will fix it. I tried 6 different roms, unrooted and returned to stock, and still had the same issue as soon as the phone started to hit the 3g data network. Working on getting root back now on the replacement.
Hello.
I just got a used One V, which was rooted by the previous owner (with xda firmware). I want to clean everything off of it (in case he put some malware on it).
I did the 'factory reset' (on a normal boot). Does that remove anything that would have been installed on a root-boot? I booted to root, and tried to wipe, but it failed (couldn't mount /sdcard). I don't have a card yet, and I'm concerned that malware might be the same as on a computer -- tries to infect added storage.
So, I'm just wondering if this phone is now absolutely stock (well, stock-rooted), or if there's still something I need to do.
Here are the details (note that this is after the wipe):
CDMA
model: PK76300
Hardware version: 0002
Software version: Stock-Rooted 1.10.652.6 710RD
Android 4.0.3
htc Sense 4.0
PRIMOC PVT SHIP S-ON RL
HBOOT-1.57.0000
RADIO-1.00.00.0928
eMMC-boot
Jun 18 2012, 10:22:43
Team Win Recovery Project 2.6.3.0
Mike-K said:
Hello.
I just got a used One V, which was rooted by the previous owner (with xda firmware). I want to clean everything off of it (in case he put some malware on it).
I did the 'factory reset' (on a normal boot). Does that remove anything that would have been installed on a root-boot? I booted to root, and tried to wipe, but it failed (couldn't mount /sdcard). I don't have a card yet, and I'm concerned that malware might be the same as on a computer -- tries to infect added storage.
So, I'm just wondering if this phone is now absolutely stock (well, stock-rooted), or if there's still something I need to do.
Here are the details (note that this is after the wipe):
CDMA
model: PK76300
Hardware version: 0002
Software version: Stock-Rooted 1.10.652.6 710RD
Android 4.0.3
htc Sense 4.0
PRIMOC PVT SHIP S-ON RL
HBOOT-1.57.0000
RADIO-1.00.00.0928
eMMC-boot
Jun 18 2012, 10:22:43
Team Win Recovery Project 2.6.3.0
Click to expand...
Click to collapse
If you have a custom recovery, Just boot into it, and Wipe Data, Cache, and Dalvik Cache. It will clear any Malware if there is any.
parthinhell said:
If you have a custom recovery, Just boot into it, and Wipe Data, Cache, and Dalvik Cache. It will clear any Malware if there is any.
Click to expand...
Click to collapse
That's what I used (and it failed).
To get it to work, do I need to put in an SD card? Or, is there another way to wipe (if I really need to as root).
Might be because of that, Just buy one Sd card it is cheap, you get an 8gb one for around $6.
WTF is root-boot? chill nothing....reboot recovery-wipe system
cybervibin said:
WTF is root-boot? chill nothing....reboot recovery-wipe system
Click to expand...
Click to collapse
That's what I call booting as root (as opposed to a regular boot). Is there a better term?
I'd still like to know if the wipe that I did on a regular boot erases everything installed on a root-boot. I figure that it should, but I don't like to assume.
If you can't boot into recovery and wipe the stuff mentioned above there's something weird going on for sure. Try reflashing the recovery maybe? Try latest twrp.
I also don't know if there's such a thing as root or non root boot. Either you have root or you do not. How you boot up shouldn't make a difference. At least on phones I've had.
leekohlbradley said:
If you can't boot into recovery and wipe the stuff mentioned above there's something weird going on for sure. Try reflashing the recovery maybe? Try latest twrp.
Click to expand...
Click to collapse
I never said anything about not being able to boot.
I also don't know if there's such a thing as root or non root boot. Either you have root or you do not. How you boot up shouldn't make a difference. At least on phones I've had.
Click to expand...
Click to collapse
Ok, that sounds good! (That's the first response that relates to my primary concern.)
My term 'root-boot' arose because I thought that I should make a distinction between the power-up that happens from a few-second push on the power button (a regular boot) and the one you get from holding the power button and volume-down button for many seconds (a root-boot). And, after researching Android a bit more, I think that I was mistaken. It's just the unlocked bootloader or the custom recovery that I was talking about - right? So, is there a term for when you boot into the bootloader/recovery?
This is my first smartphone, so I'm learning stuff daily.
Mike-K said:
I never said anything about not being able to boot.
Ok, that sounds good! (That's the first response that relates to my primary concern.)
My term 'root-boot' arose because I thought that I should make a distinction between the power-up that happens from a few-second push on the power button (a regular boot) and the one you get from holding the power button and volume-down button for many seconds (a root-boot). And, after researching Android a bit more, I think that I was mistaken. It's just the unlocked bootloader or the custom recovery that I was talking about - right? So, is there a term for when you boot into the bootloader/recovery?
This is my first smartphone, so I'm learning stuff daily.
Click to expand...
Click to collapse
yep its really simply
boot bootloader
boot recovery
just like the ADB commands.
adb reboot bootloader
adb reboot recovery