[Q] Can't access bootloader at all. Please help! - HTC One X

Hi guys
I've searched the forum for something like this but I'm coming up empty handed. But then again, I'm freaking out a bit.
I just tried flashing ARHD 9.7.0 and I've hit a big snag... For a bit of background, I was previously running ARHD 9.4.2 with the Endeavoru-Faux123-010b3 kernal. The battery was at 35% when I started the process...
I downloaded the zip, put it onto my SD card and rebooted into CWM. No worries there.
Did a wipe/factory reset and wiped the cache aswell. No worries there.
I did NOT flash the boot.img in the zip as I believed it would work okay with the current kernel (possibly the issue)
Went to install zip from SD card and chose the zip to install. AROMA starts up and I go through the familiar install process. No problem there.
I checked the reboot now option in AROMA and let it reboot. This is where the fun begins...
I get the beepy boopy start up sound and let it sit there because, as we all know, first boot can take a while. 10 minutes later, it's stuck at the HTC One splash screen. So I thought I'd reboot into CWM and start over like I've done with other ROM/kernal incompatibilities.
So I hold down the power button, let the three lights blink and the screen go blank and hold down the volume down button. And it goes back to attempting to boot up. I've tried different combinations of holding the buttons down and letting them go and hell, I've even sat there hammering the volume down button while it starts up! Still, I can't get into the bootloader.
Obviously, no bootloader, no ADB connection so I can't go through CMD and can't re-flash the kernel.
I'm currently sitting here looking at it. The USB cable is plugged in and the orange light is lit up so I hope it's charging. I'm at a loss here guys. Please, if anyone can give me some help, I will be most appreciative.

I'm really sorry to have wasted your time. It worked eventually after about 50 tries! :laugh:
Looks like it ws a kernel incompatibility.
But out of curiosity and for anybody else who gets this problem and really can't boot into the bootloader, what would be the steps involved in recovering a device in that state? I'd rather look like a knob in public as long as something constructive comes from it. :silly:

It's a bit tricky to get into hboot after a forced reboot, I think we've all been there

Just avoid the problem altogether by flashing the boot.img inside the zip first to make sure that it boots. Once up and running, flash your custom kernel and modules.

Try this http://forum.xda-developers.com/showthread.php?t=1734365
And don't let go when reboots keep hold of buttons and it should go to bootloader
Sent from my HTC One X using xda premium

Related

[Q] defrost freezes in reboot, but starts normal

Hi,
I'm a real neewbie so please be gentle.
I've rooted my phone and put defrost 5.4 on it.
Works good and i'm figuring out how things work.
I found out now that when i reboot the phone it gets stuck in starting up.
The colors exploding from the left and the right side to become a "X", but then after a while the x is not made any longer and after half an hour it is still trying to make an X.
Take out the battery, put it back and start the phone and it starts normal.
When i install something from the "defrost setup" its downloaded and when i press install the phone restarts, it is unpacking the file, reboots and then gets stuck again.
Have to take out the battery to start the phone again.
What can be the couse of this??
Just found out that also a "normal start" ends up in a endless bootscreen.
The only way to start the phone is take the battery out, put it back and press "start".
Do a full wipe and try another ROM is my first suggestion.
So idid a wipe, after that a recovery (had to start all over again) but the endless bootscreen still remains.
???
1) Find a new ROM and put it on the root of your SDCARD
2) Boot into Recovery by pressing BACK and the POWER button
3) Perform a full wipe (data/factory reset) and cache
4) Flash the new ROM
5) Boot the phone
If you still have problems post logcat.
i've cleaned and whiped (i think) almost everything.
Installed a fresh defrost 5.6.
Installed the defrost apps addon, the phone reboots and a screen apears with a android an a box with an arrow out.
Text is passing by, the phone reboots and starts up.
So far so good, but when i restart or reboot the phone its hangs in this endless lashing coulorfull screen.
I've tried to make a "logcat".
Hopefully it tells you more than it tells me.
i am having the same problem.
first off all: you can press power + volume down + optical joystick to restart phone.
no need to remove battery
my last logcat (with Error filter): www wog-fds.de/log_bootloop.txt
i started to have this problem when i redid the unrevoked process (dont really remember why, thou).
thx for help
edit: not sure but the first logcat looks like somethings missing
heres anotherone without filter www wog-fds.de/log_bootloop2.txt
thx
OK, maybe this is getting somewhere.
I also did a re-revoke, but i do know why.
the first attempt to root my phone ended up in a small disaster.
At the end of the proces i found out that i have a SLCD screen and not an AMOLED, so my phone was as good as dead.
Thanks to someone on a Dutch forum i was able to get my phone back to life.
After that i rooted my phone with the latest version of unrevoked, and this time i was succesfull.
But now i am encountering this problem and it is no fun.
I have at the moment nothing running on the phone because after a re-re-reinstallation i can start all over again with al the apps and so on.
It hangs at the final stages of the boot it looks like.
I had a similar problem when I was messing around with my old framework.
So why you're getting it, I have no idea.
First thing is first Bud
Download DeFrost 5.7 And use the latest version (Illuminate some issues to start with)
What your saying is the Boot Animation (The Multi Colour X animation "Nexus Boot Animation"
You get a boot loop on there....
How long have you left it trying to boot? the first boot after a Reflash does take alot longer than normal as it has to write to a number of files first.
(This only occurs on a New ROM or a Reflash of the frameworks)
So first off Lets Get that latest ROM on the SD Card:
Use w/e method you need to to get it on there
Turn the Phone Off "Where going to load recovery"
Press the Down Volume Key and press the power button Once.
You will see a white screen with Android images at the bottom:
Press the Volume down once (Recovery) when this is highlighted press the power button
Where now in a black screen Press Volume Up and Power
(We should now have a Blue Menu (Am taking it by the issues you talk about your using Clockwork Recover.......)
Go down to Apply sdcard:update.zip
And press the power button. So where now Clock Work Recovery
(If you dont have Clockwork i.e. Fake Flash Update.zip maybe someone can post it for me, Limited for time in work, But search for Fake FLash Clockwork if you dont have it.
Then go down to Wipe Date/Factory Reset
Select the only line that is Populated.
Go back to main menu and go to install Zip from SDCard and press the OJ
Select Choose Zip from SDCard.
Find you ROM and press the OJ
Wait some time and press the back button a few times, and select the reset option?
DO NOT INSTALL NO MODS OR THEMES, THIS CAN ONLY BE DONE AFTER A FULL BOOT OF A CLEAN ROM.
Leave it some time, as the first boot is always the longest.
Fingers crossed you should be OK.
What your talking about is a problem with the ROM (as the bootanimation is called by the ROM)
dave7802 said:
DO NOT INSTALL NO MODS OR THEMES, THIS CAN ONLY BE DONE AFTER A FULL BOOT OF A CLEAN ROM.
Click to expand...
Click to collapse
That'd be my guess too. If you try to apply a mod before you've let the ROM unpack itself it does exactly as you describe.
What your saying is the Boot Animation (The Multi Colour X animation "Nexus Boot Animation"
You get a boot loop on there....
How long have you left it trying to boot? the first boot after a Reflash does take alot longer than normal as it has to write to a number of files first.
(This only occurs on a New ROM or a Reflash of the frameworks)
I've installed the defrost.
After it came in full working conditions i've added the defrost add-on.
Phone shuts down, starts again in the screen with the one doid and a box with an arrow out.
Some writing apears and the phone starts again.
The colours apears and making a cross and this goes faster and faster and then a screen where i have to enter my sim-unlockcode and the phone is up and running.
So far so good.
When i now switch the phone off or give it a reboot ( in the screen after a long press on the powerbutton) the phone starts in the white screen with HTC logo, then the colours apear making a cross, but after time this goes slower and slower until the cross is not ever made again.
The colours appear trying to make a cross and diappear and comming back again, and this goes on for ( i left it once for 1/2 an hour)
I will give it a go with the 5.7
thanks for the help.
Really, i heave my phone for one month now and it is my first android thing.
Never worked with linux etc etc.
What does "press the OJ" means ??
oj = optical joystick
@dave7802
thanks for the answer but i have the bootloop also when i do a manual restart without flashing anything.
i use defrost 5.7
i did a restart after flashing
bye
strange thing to happen. it must be in the ROM because it wasn't happening on the stock ROM.
so try another ROM some like cyanogen or opendesire. is it happening also?
Wel, i've come to the point that i think "WTF", it works and the only thing is the start/reboot.
I'm not going to re-re-re-re sign in to my google account, and not want to re-re-re-re-enter my mail account again.
Thanks to "olaxe" i know how to start the phone wthout taking out the battery.
anyway, everybodie, thanks for reading etc.
OK so you guys are still having the same issue.
Can we provide as much info as possible,
As i use DeFrost 5.7 and i just done a normal reboot and its working fine,
if its a problem with the ROM everyone would have the issue,
All i can think is a MOD you have installed is conflicting,
So some info you can provide:
What MODS are you running / installing, like Super Circle Battery, or Custom HAVS and SVS?
What version where they developed for?
i.e. are you installing MODS that where developed for an older version of defrost? as the frameworks change on each version and so do the HAVS and SVS
If your not flashing anything how about installing it?
It could be an app you used worked for an older version, and since the update its no longer working?
olaxe
thanks for the answer but i have the bootloop also when i do a manual restart without flashing anything.
i use defrost 5.7
i did a restart after flashing
Click to expand...
Click to collapse
You say you have not flashed anything? and then you said you restarted after flashing? i dont follow?
What settings are you using and apps do you have installed?
What are you doing in clockwork recovery, are you wiping then installing JUST DEFROST then letting your system start up?
or
Are you flashing a couple of things like defrost and super circle battery?
Dave,
A nephew, who ownes a desire and is "into android" from the moment of the first googlephone, was going to root my desire.
The great misstake (we found out after we've dit it) was that he used a version of unrevoke witch was mend for use with amoled and i own a slcd.
So my phone would'nt show anything anymore. Only the bootscreen when pressed vol down and power.
I've followed several advises of diehards, have put "this.zip" on the sdcard, "that.zip" and even "ifthisdon'twork.zip" shoot me.
All i got in the bootscreen was "no image" "no image or wrong image" and "version is older".
After a week a guy on a dutch forum told me to download some files to my computer, take the sdcard out of the phone, connect the phone to the computer and then type the following:
3. Typ in je commandprompt:
code:
1
2
3
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip rom210.zip
After that the phone came back to live and i was happy as a child.
After that i did the unrevoked thing with the latest version and the phone was rooted.
Put the sdcard back, formatted it whitin the phone and after that i placed the defrost 5.4 on the root of the sdcard.
Did the full wipe, dalvikwipe and flashed the defost 5.4
After a while i had the defrost up and running.
In the defrost setup i found the defrost addon.
downloaded it (all IN the phone) and after that pressed "install".
The phone shuts down a screen appears with the one droid and a box, the phone restarts and is up and running.
Then i found in the defrost setup a file "no adds"
Installed that to and then the troubles start.
Hangs in the bootscreen.
I can only start the phone when the power is completely turned of ( battery out) or with vol down, power and trackball pressed at the same time.

[Q] Help! Unlocked bootloader, installed CWM, now phone won't boot

I used the GN Toolkit V2.2 to unlock the bootloader, after installing the adb drivers via PDANet. I flashed Clockwork Mod on as well, and was going to install the Android Revolution ROM. I thought I had already copied the zip file to the internal storage, but when I tried to flash it from inside CWM, it said no files were found. (May have copied it before wiping device, I can't remember). So I restarted so I could copy the zip file again and then flash it. However when starting, it seemed to be stuck on the startup screen, with all the flashing blocks of color fading in and out. After a while stuck on there I couldn't do anything so I did a battery pull to restart. At this point, I can start normally or into recovery mode. If I try to start normally, (or go into recovery mode and choose restart from the submenu), it shows the black screen with the white Google logo, and the unlocked icon, stalls for a few seconds, then does a short vibrate and reloads the logo again. It will keep doing this and not go any further. I tried doing an additional data wipe from recovery mode but that didn't help, and I tried to do USB mount from recovery mode, hoping to copy the Revolution zip file and flash it over, but it couldn't mount. I'm starting to panic a little bit, did I brick or otherwise mess my phone up? What can I do? Any help is REALLY appreciated.
Thanks so much and I hope this is the right forum.
I dont have the answer but I wanted to post to calm you. This happens a lot.....multiple times to me on my android devices. You live and learn next time, do a backup in cwm before wiping data and flashing new stuff
Im sure someone will post shortly to solve your problem
Well ok that is reassuring thanks. I downloaded the Google factory ROM from the code.google.com and was able to flash that on my phone with GN Toolkit. It is trying to boot right now, still on the colorful screen. I think maybe I didn't give it enough time last time around? At least I'm past the black and white logo screen. So I'll let it sit for a few minutes and see what happens.
Edit: I let it run for a couple minutes, and it blacked the screen for a sec, showed the white Google logo again, and then went into the colorful startup screen again. I think it's working now so that's a relief.
If someone finds this thread in the future with a similar issue: Don't battery pull during start up and be patient if you don't want to freak yourself out haha. But as spitefulcheerio said, it will be okay so just don't panic. Thanks again.
Make sure you do a Factory Reset in STOCK recovery after unlocking the bootloader. THEN install CWM. learned that one the hard way. skipped a step after doing the oem unlock.
Yes, first time will take awhile on the boot animation.
And, as long as you see the google logo, you are ok, even if it freezes on that. They designed this phone to be easy
Sent from my Galaxy Nexus Bugless Beast 4.0.3 lte +franco#6
Guess all I needed was a psychological confidence boost, thanks for everyone for being supportive I thought I just threw a few hundred bucks away. But I got Revolution installed, phone and rooted and runs like a dream. Thanks all around!
mynameismolotov said:
I used the GN Toolkit V2.2 to unlock the bootloader, after installing the adb drivers via PDANet. I flashed Clockwork Mod on as well, and was going to install the Android Revolution ROM. I thought I had already copied the zip file to the internal storage, but when I tried to flash it from inside CWM, it said no files were found. (May have copied it before wiping device, I can't remember). So I restarted so I could copy the zip file again and then flash it. However when starting, it seemed to be stuck on the startup screen, with all the flashing blocks of color fading in and out. After a while stuck on there I couldn't do anything so I did a battery pull to restart. At this point, I can start normally or into recovery mode. If I try to start normally, (or go into recovery mode and choose restart from the submenu), it shows the black screen with the white Google logo, and the unlocked icon, stalls for a few seconds, then does a short vibrate and reloads the logo again. It will keep doing this and not go any further. I tried doing an additional data wipe from recovery mode but that didn't help, and I tried to do USB mount from recovery mode, hoping to copy the Revolution zip file and flash it over, but it couldn't mount. I'm starting to panic a little bit, did I brick or otherwise mess my phone up? What can I do? Any help is REALLY appreciated.
Thanks so much and I hope this is the right forum.
Click to expand...
Click to collapse
cancerouspete said:
Yes, first time will take awhile on the boot animation.
And, as long as you see the google logo, you are ok, even if it freezes on that. They designed this phone to be easy
Sent from my Galaxy Nexus Bugless Beast 4.0.3 lte +franco#6
Click to expand...
Click to collapse
mynameismolotov said:
Guess all I needed was a psychological confidence boost, thanks for everyone for being supportive I thought I just threw a few hundred bucks away. But I got Revolution installed, phone and rooted and runs like a dream. Thanks all around!
Click to expand...
Click to collapse
To provide some technical details on why it takes longer the first boot and appears to "hang" at boot animation ...
During the boot animation, the /data/dalvik-cache directory is built up for each application loaded on the device. This occurs during the very first boot. If the /data partition is wiped, the dalvik-cache directory is also wiped and will have to be rebuilt on the first boot. All subsequent boots will be quicker as this directory has already been populated.
Whenever loading a new ROM or performing the fastboot oem unlock command, the /data partition is generally wiped which takes with it dalvik-cache and results in the delayed initial boot time while the dalvik-cache directory is re-populated.
Hope that makes sense and fills in a few blanks on the why Android appears to "hang" at the boot animation during first boot after the /data partition is erased or the /data/dalvik-cache directory is erased.

[Q] Please help! Stuck and can't use phone.

This morning I was using font installer to change my system font . I guess somewhere along the way something got messed up because when I went to reboot it gets to the boot animation and turns off. Not exactly a boot loop but useless anyway. I could just go into recovery and reflash. The problem is I can't get the phone into recovery. I use TWRP. I hold volume up and down and power, the TEAM Win blue screen and logo comes up but then what do I do? If I keep holding it down then it just goes into that mode where it vibrates every second and nothing happens.if I let go then the blue logo screen goes away and it tries to boot up normally again. What am I missing here? Why can't I get into recovery so I can reflash... Thanks for all Your help guys!
have you tried using adb commands? Also if you have not gotten into recovery as of now you just have to keep trying with the vol and power key buttons you will get it.
ADB choices
Plug phone into pc and type adb reboot recovery and hope for the best
I think you might be able to reflash/reinstall the recovery using adb commands and that might work too. Worst comes to worst, you could try using ODIN to restore your recovery or whole phone, but you'll probably lose anything not on SD.
And I haven't used font installer in ages, but I had issues with it on my SGSII because I think it flashes system files; I know it doesn't help now, but I'd stick to using font apks, since our phones support that.
Russian smashed across the interwebz from my Galaxy S2.
Sometimes this happens with fonts that are not designed for whichever version of android you are running. Its not all of them believe me, as well as this is honestly an easy fix. This is why I believe in knowing everything about your phone prior to doing stuff to it and knowing how to escape 90% of the issues that may come your way.
Thanks alot. the annoying part is that TWRP blue screen comes up but nothing happens. It just kinda flashes like a crt tv off and then goes into the vibrate every second thing. I typically do alot of reading and research prior to doing anything and I used to use the font app before on the HD2 so I was suprised this happened. I guess you live and learn. I just thought that was one of the benefits of having a recovery so you Could fix stuff like this. it doesn't help if you Can't even get into recovery. I never had this problem with Cwm Recovery.
I got it to work! I guess it's all about the timing for when to release the buttons to get into recovery. I flashed the rom back and all is well. Or at least getting there. Thanks everyone for the help. Hopefully this thread will help someone else in the future. Lesson Learned: Don't give up on trying to boot into recovery. It will work. You just have to release the power and volume button at just the right time to get everything going. Lesson 2: Don't use the font installer app....

[Q] hard brick s2

If any one can help with any idea I would really appreciate it.
So I let my little brother play my s2 and he completely ran the battery out.
now I have left it on the charger over night, when i go to boot into recovery. You feel the phone vibrate then see the samsung for a split second, and if you keep holding the power you just feel the phone keep vibrating. The screen never turns back on. Now I know it works because i was able to boot recovery once, when i did that i just tried a full wipe and reboot. phone kept boot looping, so i pulled battery, but now i cant get into download mode or recovery.
Please help, or atleast let me know that its not fixable
thanks
You are supposed to let go of power after the first vibration. ?
Try downloading a stock ROM (.tar format, I believe) and flashing it, using ODIN. That worked for me when I bricked my SGH-T989.
I later had to install a new recovery, but you can play around and see what needs doing.

VM Soft-Bricked...I know...

Well, guys was doing pretty well there for a second, I had just installed CarbonROM, was tweaking to my heart's content. Flashed a bad file in an attempt to improve speaker clairity, and boom stuck on the HTC boot logo.
Popped open the back, unplugged the battery, rebooted into HBOOT, rebooted into recovery and attempted to restore one of my backups I took right before flashing the bad zip. Failed. Can't load the data partition.
Ok, got the RUU file from this thread: http://forum.xda-developers.com/desire-816/general/ruu-htc-desire-816-a5chl-ruu-file-t2920254
Downloaded, put on root of SD card, renamed, rebooted to HBOOT, it picked it up, seemed to flash it, but it also seemed to go faster than it should. I'm suspecting it failed as well.
So now I've just got my phone sitting in recovery. Unable to mount the data partition.
Any clue on what I can do now? Hoping I haven't bricked this sucker...
Ok, my persistence paid off....Mods feel free to close this thread, I came up with a fix.
For anyone else in the same rut, this is how I fixed it...
Downloaded stock recovery from this link: https://drive.google.com/file/d/0B4NAwrQOaS7QVkxFYnhFZmhjOGc/view
Flashed stock recovery from Fastboot.
Loaded into stock recovery, key combo'd Volume UP + Power, got to the menu. Did a factory reset. Guess it reset partition mount points or something.
Rebooted to Fastboot, flashed TWRP, rebooted to recovery, restored a backup, and bam I'm back!
kenmoini said:
Ok, my persistence paid off....Mods feel free to close this thread, I came up with a fix.
For anyone else in the same rut, this is how I fixed it...
Downloaded stock recovery from this link: https://drive.google.com/file/d/0B4NAwrQOaS7QVkxFYnhFZmhjOGc/view
Flashed stock recovery from Fastboot.
Loaded into stock recovery, key combo'd Volume UP + Power, got to the menu. Did a factory reset. Guess it reset partition mount points or something.
Rebooted to Fastboot, flashed TWRP, rebooted to recovery, restored a backup, and bam I'm back!
Click to expand...
Click to collapse
Haha I had this same problem before, was ready to send my phone back. I was so scared and it wasn't working for like 3 days.
FoxyDrew said:
Haha I had this same problem before, was ready to send my phone back. I was so scared and it wasn't working for like 3 days.
Click to expand...
Click to collapse
Yeah, note to self, never get a phone without a removable battery. The sticky pads under the back cover while I was popping it off were annoying. Thankfully my phone was only down for a few hours.
kenmoini said:
Yeah, note to self, never get a phone without a removable battery. The sticky pads under the back cover while I was popping it off were annoying. Thankfully my phone was only down for a few hours.
Click to expand...
Click to collapse
This phone has a non-removable battery. You don't need to take out anything, all you do is hold volume up + the power button for 10 seconds or more. It will ALWAYS hard power off no matter what state the phone is in.
Also, what file did you flash over to improve the speaker clarity which broke your phone? I spoke to you about this earlier in my CarbonROM thread. I actually was able to fix the boomsound issue and there is no more crackling in my speakers. I'm going to post how to do it when I get home.
Edit: SORRY! Volume UP, not DOWN. Got mixed up
LiquidPlacidity said:
This phone has a non-removable battery. You don't need to take out anything, all you do is hold volume up + the power button for 10 seconds or more. It will ALWAYS hard power off no matter what state the phone is in.
Also, what file did you flash over to improve the speaker clarity which broke your phone? I spoke to you about this earlier in my CarbonROM thread. I actually was able to fix the boomsound issue and there is no more crackling in my speakers. I'm going to post how to do it when I get home.
Edit: SORRY! Volume UP, not DOWN. Got mixed up
Click to expand...
Click to collapse
I tried Vol Up/Down + Power for at least 30 seconds, was just stuck at HTC logo screen and I could feel the phone getting hotter so instead of having it run down the battery I decided to pop off the top. The back is meant to be non-removable but starting at the SD/SIM slot...slot, a guitar pick works great to undo the clips. Used a credit card to separate the sticky pads from the back. Pulled out the battery cable from the mainboard and reseated it, started it back up in HBOOT.
I flashed some sorta ZIP that's used with the HTC One M8 phones, figured if they have BoomSound it'd help too but noooope, haha. Can't remember what it was called. Did a lot of searching, tried Viper4Android, that sucked, tried tweaking the DSP, nothing came close to the original.
Sharing my own bricking experience
I'm a newbie, but I wanted to share my own experience from a few days ago. I bricked my VM/USA 816 when I was restoring a ROM backup of CM12 over a stock ROM. I was stuck on the CM12 blue "alien head" boot screen. I tried to get into the recovery screen by holding down power & volume, but it would only reboot and load CM12 again and not TWRP.
After a couple of hours of trying to get into recovery and deciding not to wait for the battery to drain because I thought the blue CM12 logo might burn into the screen. I decided to try to remove the cover and unplug the battery. I started at the SIM/SD Card slot trying to pop the cover off a little with a small screw driver to get a credit card(CC) between the cover and phone. Once I got it started I moved clockwise(cover side up) around with either a bent CC or a smaller cut up piece of CC to pop the tabs. I wasn't very gentle since I knew I wasn't going to return the phone and I bought the phone from VM with account balance so I didn't feel like I was really going to waste $300. Thank HTC the plastic cover is very forgiving. Once you get past the HTC logo you have to worry about the sticky tape around the bottom half of the phone where the battery is located. The bent CC was the best tool here and as I said earlier I wasn't very gentle while pulling off the cover once the tabs were loose.
Once I had the cover off I didn't know how to unplug the battery connector so I decided to pry the battery out. Once I did that I could see that the connecter pops up. I plugged the battery back in but the phone tried to load CM12 again. I don't remember if I had to press power button to turn on phone or it started when I connected the battery. I got back into the same state as before with a boot loop with no way getting back into recovery. So I unplugged battery again and connected the phone to my PC. I could see the screen the flashing between the charging screen and TWRP, but I couldn't get into recovery with buttons or screen touches. I then went into a command window on my PC to try the adb command. First I did a "adb devices" then I did a "adb reboot recovery" to get into TWRP. Once in TWRP I did an advanced wipe and installed CM12, gapps and supersu again from my ext SD Card. I'm not sure but I may have done a format of the internal storage just to be safe. Once I was up and running again I replaced the cover starting again clockwise from the SIM/SD Card corner and all the way around the phone till you get near the SIM/SD Card slot and have to replace the flap which is held in place by the cover/phone.
I hope this helps anyone who runs into the same problem.
kenmoini said:
Well, guys was doing pretty well there for a second, I had just installed CarbonROM, was tweaking to my heart's content. Flashed a bad file in an attempt to improve speaker clairity, and boom stuck on the HTC boot logo.
Popped open the back, unplugged the battery, rebooted into HBOOT, rebooted into recovery and attempted to restore one of my backups I took right before flashing the bad zip. Failed. Can't load the data partition.
Ok, got the RUU file from this thread: http://forum.xda-developers.com/desire-816/general/ruu-htc-desire-816-a5chl-ruu-file-t2920254
Downloaded, put on root of SD card, renamed, rebooted to HBOOT, it picked it up, seemed to flash it, but it also seemed to go faster than it should. I'm suspecting it failed as well.
So now I've just got my phone sitting in recovery. Unable to mount the data partition.
Any clue on what I can do now? Hoping I haven't bricked this sucker...
Click to expand...
Click to collapse
You have to flash and use CWM 6.0.5.1 and wipe the same partitions that were backed up in your STOCK nandroid backup.
Once you do this, reboot to hboot. Enter fastboot. Flash the stock recovery. Wipe the data/cache/dalvik. Reboot and go to hboot again. (Your device won't be able to boot yet.) Enter fastboot again.
Flash CWM (ONLY CWM) and make sure it flashes by flashing it twice back to back without leaving fastboot at any point.
Boot into recovery and once loaded reboot into hboot once more then go once again to fastboot and flash Philz Recovery with the same double flash process.
Now boot into it, mount as a USB and create a clockworkmod/backup folder on the device root directory since Philz Recovery doesn't use the buried part of the system like CWM.
Drag and drop your stock root nandroid backup. Use Philsz recovery to restore it. Boot up and your phone will boot after 3-5 minutes.
Flash back CM11/12 if you'd like.
Sent from my 710C using XDA Free mobile app
kenmoini said:
Ok, my persistence paid off....Mods feel free to close this thread, I came up with a fix.
For anyone else in the same rut, this is how I fixed it...
Downloaded stock recovery from this link: https://drive.google.com/file/d/0B4NAwrQOaS7QVkxFYnhFZmhjOGc/view
Flashed stock recovery from Fastboot.
Loaded into stock recovery, key combo'd Volume UP + Power, got to the menu. Did a factory reset. Guess it reset partition mount points or something.
Rebooted to Fastboot, flashed TWRP, rebooted to recovery, restored a backup, and bam I'm back!
Click to expand...
Click to collapse
Hello
Thank you for sharing your solution.
I have a problem which is described in this thread: http://forum.xda-developers.com/des...im-boots-fastboot-t3316255/page3#post65409302.
My questions to you:
1. My bootloader is locked. Is it possible to flash stock recovery on it?
2. I tried to flash official rom but I received the message "Partition update fail!". Can what you did, resolve this problem?

Categories

Resources