[Q] Disaster Recovery - HTC One X

Help Please..i really need ur special help,
i have been trying flash a new custom ROM by using ARHD 17.0 n after completion of flashing the firmware to update my Hboot from 1.12 to 1.36, i did not manage to flash the custom ROM since my phone failed to reboot. it stuck and hang at the HTC logo.
after a few research on the forum, i found a threat that might help me with my problems. from the threat ''[TUT] Disaster Recovery - How to recover from nearly everything [Updated 28/04/2012]'', it say that i need to clear the cache on the fastboot. i have tried but the same problems still occurs.
in addition my battery goes very low and i failed to flash any ROM since low battery. i have done the power down steps more than 20 times but my battery still did not charge.
in summary,
1- i still stuck at reboot where it still hang on the HTC Logo even after i clean the ROM cache
2- i still cannot charge my phone even after several times power down and on repeatedly more than 20 times.
i realy need help here, since i realy dunno wut to do even after applying what have been advised in the threat. really hope that someboody can help me with it.

Use this script to charge phone. Did you flash the boot.img?

TToivanen said:
Use this script to charge phone. Did you flash the boot.img?
Click to expand...
Click to collapse
yes i did flash the boot.img after i flash the CWM recovery..

Related

Samsung Logo Keeps Flashing, wont boot HELP

Never thought I'd be the one to create a thread like this..
After I flashed the OKV4 ROM, strange things started to happen (this was after a full wipe). Apps kept force closing, etc. Later that day, when I picked up my phone, I saw the samsung logo flashing over and over. Making me unable to enter recovery.
Download mode still worked though and I proceeded to flash a stock firmware via ODIN. This did not help. Oh, and the Odin flash succeeded, without rebooting my phone though...
So, I'm still stuck with my phone which can't seem to get out of this strange loop.
HELP :C
I remember reading somewhere here that if you have flashed a diff FW now and then a possibility the last recent kernel is still in the system folder etc....this is maybe the cause of the bootloop.
Since you had confirmed going to download mode is possible..this may work logically... Why not do the following :
Get your phone rooted via Recovery (there is a thread here by The-E)..Once done flash arco68's CWM Recovery....Boot to recovery n do this :
Factory Format....Wipe n Clear including Delvik...Then go to Mount n Storage wipe every single folder...System...Data...Etc (this will wipe every single data left behind but I assure you the CWM will not be wiped) once done reboot n put the device into DL mode and use Odin to flash back to the stock FW.
From this moment the recovery will be replaced by stock version and the stock FW will be restored....once it boot up..Walla as I had done this over two times :
Best of Luck !!
Sent from my GT-I8150 using xda premium
I think you misunderstood me :/
This isn't the ordinary bootloop where the boot animation plays. It resets literally 2 seconds after starting. This makes me unable to enter the recovery at all. Thanks for the effort tho.
Tl;dr:I can not enter recovery mode.
treUse said:
I think you misunderstood me :/
This isn't the ordinary bootloop where the boot animation plays. It resets literally 2 seconds after starting. This makes me unable to enter the recovery at all. Thanks for the effort tho.
Tl;dr:I can not enter recovery mode.
Click to expand...
Click to collapse
Hi Bro...
I already discuss it in this Tread couple a days a go
You not alone bro
I ask The-E to mention all Wonder user to get safety flashing
Until this time we didn't get way to fix it yet

Phone Re-Locked, Charge low need help

I tried to install ARHD 7.1.0 and ended up in boot-loops. So I did many factory resets and that didn't do the trick. Re-flashed it, no use.
Then I tried to erase cache. Nothing
After all that frustration I then tried to do the RUU again. That requires to Re-Lock the phone and makes the CWM un-accessible. I am an idiot trying to do the RUU (thank God I didn't had enuf battery) even though i had a higher version.
So now I know my mistake
I didn't flash the "boot.img" for the ARHD 7.1.0. So that's why i got boot loops. But I got to know this mistake when I Re-Locked the phone. Now it wont charge with the screen off cuz it boots up to the Bootloader
I see the Red Notification ON but I dnt think its charging that. I am stuck and running out of options. Please help me in any way. I have the Super Wipe and the ARHD 7.1.0 Rom in the SD card but can't access the Recovery. Please help me
Anyone care to help? :/

Bad flashing caused big problems

Hi guys I´m going to go mad because of flashing a new kernel on my HTC One X.
At first the infos:
Unlocked at HTCDev
Had the CWM 5.8.40 Recovery (HAD!)
Faux Kernel 7m (didn´t work at the first time but after a reflash everything was ok)
Viper X 2.7.1 Custom Rom (UC+UV)
SoundEnhancer Mod 18
At first: I´m more like a silent reader and I´m trying to learn as much as possible so I´m not an expert.
Today I tried to flash the newer Faux Kernel 10m on my One X but forgot to erase the cache afterwards. It got stuck at the HTC One Logo
So like at the 7m Kernel I retried but this time it got stuck again at the HTC One Logo.
I read the Disaster Recovery Tutorial Thread and tried the fast and easy things but they didn´t work eitther.
I accepted the fact that I had to recover the phone with my backup which was from the stock rom with nothing on it.
After restoring the boot gif changed to the original one but it still got stuck at the HTC One Logo. This time I erased the cache.
After that I had to use a RUU but I just took the newest one because I didn´t get the idea how to match the cid with the RUU-numbers.
I did as it was written here in Method 2. But I didn´t see the Notification: "FAILED (remote : (00000006))".
I relocked the phone and it restarted but now it´s in the bootloop and doesn´t get detected neither by the RUU exe nor by the cmd. So I can´t get back to the recovery and can´t get detected by the RUU.
How can I fix my phone to end this misery?
I hope someone can wirte a step-by-step guide so everybody who has the same problem can solve it.
Greetings
Beyazid
When you flash a new kernel, all you have to do is place modules zip in phone storage, put phone in bootloader, connect to computer, flash boot.img, go into recovery and flash modules. If you don't flash boot.img, the phone won't boot. Try going into bootloader by pressing volume down and power at the same time and holding it, flash viper boot.img via fastboot kit, full wipe and reflash rom. I've messed up a few times but this has always worked for me.
Beyazid said:
Hi guys I´m going to go mad because of flashing a new kernel on my HTC One X.
At first the infos:
Unlocked at HTCDev
Had the CWM 5.8.40 Recovery (HAD!)
Faux Kernel 7m (didn´t work at the first time but after a reflash everything was ok)
Viper X 2.7.1 Custom Rom (UC+UV)
SoundEnhancer Mod 18
At first: I´m more like a silent reader and I´m trying to learn as much as possible so I´m not an expert.
Today I tried to flash the newer Faux Kernel 10m on my One X but forgot to erase the cache afterwards. It got stuck at the HTC One Logo
So like at the 7m Kernel I retried but this time it got stuck again at the HTC One Logo.
I read the Disaster Recovery Tutorial Thread and tried the fast and easy things but they didn´t work eitther.
I accepted the fact that I had to recover the phone with my backup which was from the stock rom with nothing on it.
After restoring the boot gif changed to the original one but it still got stuck at the HTC One Logo. This time I erased the cache.
After that I had to use a RUU but I just took the newest one because I didn´t get the idea how to match the cid with the RUU-numbers.
I did as it was written here in Method 2. But I didn´t see the Notification: "FAILED (remote : (00000006))".
I relocked the phone and it restarted but now it´s in the bootloop and doesn´t get detected neither by the RUU exe nor by the cmd. So I can´t get back to the recovery and can´t get detected by the RUU.
How can I fix my phone to end this misery?
I hope someone can wirte a step-by-step guide so everybody who has the same problem can solve it.
Greetings
Beyazid
Click to expand...
Click to collapse
there are infinite posts about how to fix this and tutorials too if you use the search button, anyways
1- why using faux 7m when there is already 10m ?
2- hold power+vol dwn
3- go to recovery (hboot not fastboot)
4- go to mounts and storage, mount storage usb
5- copy to your sd all the files excluding the boot.img from faux
6- flash rom then modules then type in cmd "adb reboot-bootloader" (without quotes),
7- choose fastboot in bootloader then flash boot.img and erase cache
@VCek: I flashed this before the Versions 10 and 11 came out
Thanks for the infos. I´ll use them the next time. But now I can´t reach the bootloader anymore because I locked the phone with "fastboot oem lock" and because of that I can´t do anything but go to the fastboot mode. The recovery is locked or in other words: I can´t use the CWM Recovery anymore.
If I click the recovery mode this happens: vvvvvv(dot)vidup(dot)de/v/l1vVH/ (make a dot instead of the word "dot" and change the V´s to W´s, I´m not allowed to post outside links right now)
The next step should be the unlocking I guess. Right? But how can I do that?
Edit: I was able to unlock the phone again so it should be easier from now on but your steps didn´t work for me. I reflashed the Viper X Rom and reflahed the Kernel without the boot.img in it. But I didn´t get the point which boot.img I should flash. Both of them or just the Rom boot.img?
Edit2: After a long day I was able to solve the Problem with the right RUU. After all it was easier than I thought and I should have done that at the beginning

[Q] Htc wildfire rooting issue

Ok so guys i had just rooted my htc wildfire s (or atleast thought i rooted it ) and was trying to install a cyanogen mod ROM , it would not install ,if it would install it would be stuck at the htc logo screen , now i thought this would be the fault of recovery so i decided to install another recovery and flash that with cmd (fastboot flash recovery recovery.img) but then when i booted in recovery it would show me the pink recovery, i got a little scared and flashed another recovery and now the recovery will not even boot . it will just go on htc logo and black screen , i tried many different recoveries but no avail , it is in s-on right now , please forgive me if this sounds noobish i really am a noob at this .please provide me with a solution and tell me if it is bricked and if i can repair it by taking it to a software shop and asking them to do it for me (Just advise me if i can come back from this)
Flash the first recovery, which actually worked, and if it installs, wipe everything and flash a basic CM7 rom. It'll work. It's just soft bricked don't worry.
parasthakur37 said:
Flash the first recovery, which actually worked, and if it installs, wipe everything and flash a basic CM7 rom. It'll work. It's just soft bricked don't worry.
Click to expand...
Click to collapse
actually i gave it to a software store , he said he couldn't do it as the files were not to be found ... i think it might have been bricked but seeing as i can access h-boot only and when i turn on the phone it only stays on the htc logo screen and does not proceed can you call this bricked . ? i tried the first recovery as you mentioned but it was no use ... i tried relocking and unlocking bootloader again but it seems as if that was unnecessary as nothing different happened .. im still waiting for an answer
This is really very weird.
Check this out
http://forum.xda-developers.com/showpost.php?p=28646721&postcount=5
Start from square one, unlock the bootloader, flash the recovery, if one doesn't install, try another, at least one will surely work, and then flash a new rom.
All the best.
Remember, android can never be bricked, there is always a way out.
parasthakur37 said:
This is really very weird.
Check this out
http://forum.xda-developers.com/showpost.php?p=28646721&postcount=5
Start from square one, unlock the bootloader, flash the recovery, if one doesn't install, try another, at least one will surely work, and then flash a new rom.
All the best.
Remember, android can never be bricked, there is always a way out.
Click to expand...
Click to collapse
thank u for the quick reply but i donot know how but i just flashed an old recovery and voila it worked .. now i am a little scared to proceed please guide me what to do to bring back the stock rom ...
ITS DONE
i finally got it to work thank u so much i used jelly king rom on it and it worked DDDDD
Press thanks.

xperia play bricked? pls help

hi all im hoping u can help me i have an xperia play which i tryed to root using cynogen mod 12 but it fails on install it will then reboot and show the blue cynogen logo but sit thier untill battery pull. i can access cyonogen recovery but thats all. ive tried installing other roms such as 9, 10 and 11 but all do the same thing (although 11 does seam to install/unpack).
i unlocked the bootloader and rooted the phone successfully. i also used flashtool to flash the boot.img.
i have heard i could fix the problem by sideloading another better recovery tool but i dont know how to do that. as off now im stuck in cynogen recovery.
any advice you could give would be greatfully appreciated, at this point im completely out of ideas and if you need anymore info i would be happy to provide it
thanks in advance
Hi,
It would be nice if you linked the exact ROM you tried to flash on you phone. It sounds like the boot.img is incorrect.
You can try flashing this kernel forum.xda-developers.com/showthread.php?t=1804003 . This one is for ICs roms(4.0.x).
Or this one - for Jelly Bean versions(4.1-4.2) - forum.xda-developers.com/showthread.php?t=1861970 .
All you have to do, is boot into fasboot mode and flash the given .img file as boot.img. (The difference between 480p and 720p kernels, are that 480 can't capture 720p videos, but sometimes 720p kernel doesn't work with all roms).
hi tnx for the help the rom i tried to install was cm-12-20150314-UNOFFICIAL-LegacyXperia-zeus
i think your idea would work but im unable to boot into fastboot mode as i used flashtool before and it doesnt recognise my phone anymore ( i dont know if i can use ADB as that option is available on my boot loader)
if you could provide me with a link to how to flash a new .img/rom using another way other than flash tools that would be really helpful. im sry to be such a noob, i have rooted every phone i had and never encountered this problem before and am completely stuck.
tnx again for your help
ok ignore my last msg i managed to flash the .img in fastboot no problem but now it wont let me into recovery mode so i think im stuck in some infinate boot loop no matter how many times i click volume down it just reboots after about 2 mins, anything i can do about that or am i now really bricked?
tnx again for your help
rob17zero1 said:
ok ignore my last msg i managed to flash the .img in fastboot no problem but now it wont let me into recovery mode so i think im stuck in some infinate boot loop no matter how many times i click volume down it just reboots after about 2 mins, anything i can do about that or am i now really bricked?
tnx again for your help
Click to expand...
Click to collapse
Well you could try to return to point zero by flashing your phone to stock rom and try to begin from there.
You can do that by using flashtool and downloading stock ROM from these forums.
BTW, you can enter flash mode by inserting usb cable and holding search button(i think, you can try other buttons). Your LED has to turn green, blue is fast boot.
Also if your flashtool give you errors, download earlier version (see some other threads about flashtool, there are links to older version). Maybe it doesn't recognize your phone, because of the new version, i've had problems with it too, but i had to download old version and everything started to work as expected.

Categories

Resources