Develop Bugs

[Q] HTC Desire HD stuck in bootloop. Will not go past htc logo, total inactivity

My DHD is stuck on HTC logo. Happened after trying to flash leedroid from cyanogenmod 7. previous flashes were successful. Now when i turn it on, the only thing it can do is show htc logo screen.
- The screen wont turn off
- None of the buttons do anything when pressed (including power off)
- Cannot go to recovery, bootloader or use fastboot
- Cannot access SDCard when plugged in the phone to my laptop (recognises a device connected though!)
Going to send it back to the network provider for fixing but i'm sure it is not covered warranty.
Please help me with things I can try to somehow get it anywhere besides the blank htc screen (white background with green htc).....
Much appreciated

With the USB connected there should be a split second where you can type adb reboot recovery to get back into recovery...
You could also try removing the battery and then replacing the battery while to have your finger on the vol- key. That might get you into the boot loader...

yea, like the 'Drew442' said, take the battery out, hold vol down and press power for 1-2 secs. That will take u to bootloader. Select Recovery and that'll take you to CWM Recovery. Then you can restore a nandroid, or flash a new ROM.
I've done this ALOT, once i did it approx 10-15 times in one day (lots of experimenting )!!! dont worry,

CodeNameUnknown1 said:
yea, like the 'Drew442' said, take the battery out, hold vol down and press power for 1-2 secs. That will take u to bootloader. Select Recovery and that'll take you to CWM Recovery. Then you can restore a nandroid, or flash a new ROM.
I've done this ALOT, once i did it approx 10-15 times in one day (lots of experimenting )!!! dont worry,
Click to expand...
Click to collapse
Last night I done that 10+ times after my touch screen was toty unresponsive due to flashing a mod. I suggest what the two posters suggested. I don't it will be wise sending it back.
Sent from my Desire HD using XDA App

similar issue - but can't get to cwm
Hi,
I have a similar issue produced by similar circumstances. Mine was during switch from regular ext3 ROMs to an ext-4 CM7 based ROM. To be precise, it was during my attempted flash of an ext-4 friendly version of CWM 3.0.2.8
Now I can get to HBOOT menu by pulling the battery and booting with volume "-" , but when I select "recovery" I can NOT get to CWM recovery very worried. selecting recovery sends me to the white screen with the green HTC logo indefinitely, until battery pull.
What can I do? I have years of *nix use, but this is my first Android smartphone (well i had an HD2 for a couple weeks, and LOVED android so bought the inspire / desire hd) and I've had no problems following tutorials, and experimenting. But I am new, so maybe I'm not trying something that's obvious to all ofyou
is there ANY way to manually flash a bootable ROM to my phone? or force install CWM?
I need help.. so sad.. no phone at all now, as I got rid of my iphone 4 after loving this phone so much!

You can flash a cwm 3...... Recovery from Fastboot then load cm7 rom. As long as you can access the bootloader you're ok, the phone isn't bricked. Download a cwm recovery 3 series and put the .img file in the tools folder of your sdk then turn the phone on in fastboot bootloader mode then open a command prompt on your pc. Navigate to your tools folder then type...... fastboot flash recovery nameofrecovery.img
Then fastboot reboot-bootloader
That ought to do it.
Sent from my Motorola Startac running Atari 2600 software!

Well, if you have ENG S-OFF, then you can flash CWM recovery manually .. LINK
IF you dont have ENG S-OFF, or if it fails again, then i suggest trying to put the official 1.32 FW ROM - LINK
flashing 1.32 would be more productive in that case that flashing CWM fails, since its easily rootable (Visionary+)

thanks! will try~
@CodeNameUnknown1 - i do have s-off, but I tried running "install-recovery-windows.bat" with cwm 3.2.0.0, to no avail.
For the brief moment the batch file is running, the terminal window says something about not being able to write the file. It is so fast I can't read it properly.
@pwraggcan - I will give the sdk method a shot. didn't know about it, since I used a "one-click" method initially to root my device and proceeded with rom manager from inside...
thanks! I hope it works!!

Google search for guidance on installing sdk or search within the xda forum. There will be plenty of guides.
Sent from my Motorola Startac running Atari 2600 software!

thanks
hey guys.
in the end i loaded stock rom (1.32) and went from there. worked perfectly.
was trying to do the sdk method (seemed similar to how I rooted my asus transformer - abd etc..) but I keep getting a missing dll error. followed all kinds of guides on rectifying it, but no dice.
anyway, stock rom was faster fix in the end.. lol.
thanks again!!!

Glad it worked for you. I actually prepared a zip file to upload for you with the necessary drivers and files if you needed it but hey.... you're sorted now, so all good.
Sent from my Motorola Startac running Atari 2600 software!

i got a problem here..
my friend recently update his unroot phone to GB with OTA update.. but after the update finished,his phone restarted and got into infinite bootloop..
in this thread,someone said that it can be solved by using stock pd98img.zip
can anyone help me how to do it? because the OP at http://forum.xda-developers.com/showthread.php?t=905003 said to use the visionary+ first.. but the problem is his phone can't past the bootloop. is there any solution to manually install the stock 1.32 ROM?
thanks

Follow the downgrade guide in the development section. That will sort you out. Make a gold card then flash the pd98img.zip. That will reinstall the stock rom.
Sent from my Motorola Startac running Atari 2600 software!

pwraggcan said:
Follow the downgrade guide in the development section. That will sort you out. Make a gold card then flash the pd98img.zip. That will reinstall the stock rom.
Sent from my Motorola Startac running Atari 2600 software!
Click to expand...
Click to collapse
why i must make a goldcard first? my friend's phone isn't a branded one..
and what about the version number? does it matter?
i kind of lost here..
Sent from my Desire HD using XDA App

Just flash a version which match yr country version or a wwe will do too. Mine also isnt a branded phone, but i also have to do a goldcard too, kinda weird, lol...

sneef said:
hey guys.
in the end i loaded stock rom (1.32) and went from there. worked perfectly.
was trying to do the sdk method (seemed similar to how I rooted my asus transformer - abd etc..) but I keep getting a missing dll error. followed all kinds of guides on rectifying it, but no dice.
anyway, stock rom was faster fix in the end.. lol.
thanks again!!!
Click to expand...
Click to collapse
I think that missing dll is located in the platform-tools folder and you could copy it to the tools folder (at least in my case with a similar error). Or you could use adb from the platform-tools folder. Works for me.

sneef said:
hey guys.
in the end i loaded stock rom (1.32) and went from there. worked perfectly.
was trying to do the sdk method (seemed similar to how I rooted my asus transformer - abd etc..) but I keep getting a missing dll error. followed all kinds of guides on rectifying it, but no dice.
anyway, stock rom was faster fix in the end.. lol.
thanks again!!!
Click to expand...
Click to collapse
hi ! , i'm an xda noob....
cant get past the htc screen ....
i tried the install-recovery-bat but to no avail..
dint quite get how you loaded the stock rom (1.32) ... can you please post a link to some guide.. i will be greatful.. thanks

hi,
having same problem as sneef there,
only can go to bootloader, can get into recovery
but then i flash recovery using the eng s-off guide and now i can go to recovery (cwm)
but still it cant boot to the rom, i have tried to flash 3 4 roms with no avail.. all stucked in the htc boot logo
this happened to me after flashing superwipe.zip
any solution please?
nb: i have already format and repartition my sd card

interqd said:
hi,
having same problem as sneef there,
only can go to bootloader, can get into recovery
but then i flash recovery using the eng s-off guide and now i can go to recovery (cwm)
but still it cant boot to the rom, i have tried to flash 3 4 roms with no avail.. all stucked in the htc boot logo
this happened to me after flashing superwipe.zip
any solution please?
nb: i have already format and repartition my sd card
Click to expand...
Click to collapse
Have you tried the stock ROM?

sneef said:
Hi,
I have a similar issue produced by similar circumstances. Mine was during switch from regular ext3 ROMs to an ext-4 CM7 based ROM. To be precise, it was during my attempted flash of an ext-4 friendly version of CWM 3.0.2.8
Now I can get to HBOOT menu by pulling the battery and booting with volume "-" , but when I select "recovery" I can NOT get to CWM recovery very worried. selecting recovery sends me to the white screen with the green HTC logo indefinitely, until battery pull.
What can I do? I have years of *nix use, but this is my first Android smartphone (well i had an HD2 for a couple weeks, and LOVED android so bought the inspire / desire hd) and I've had no problems following tutorials, and experimenting. But I am new, so maybe I'm not trying something that's obvious to all ofyou
is there ANY way to manually flash a bootable ROM to my phone? or force install CWM?
I need help.. so sad.. no phone at all now, as I got rid of my iphone 4 after loving this phone so much!
Click to expand...
Click to collapse
I have tried like you describe holding the volume down but nothing happens. I have earlier had problems with the volume down in bootloader, but it has worked in htc sense. you know what the volume down problem is about? how it could be fixed?

Help urgent!!!!!!! Gn stuck on google symbol

So I was trying to put JB on my GN using this:
pcworld.idg.com.au/article/429778/how_update_your_galaxy_nexus_jelly_bean/[/url]
I reached to apoint where i had 4.04 yakju, but when I put the file to get JB, It said error and aborted, i went to wipe data and reboot, wipe data worked fine, reboot led me to the google home screen and is stuck there.
I can access fastboot. Recovery mode takes me to that android with the danger sign, doing another reset doesnt work, clicking reboot doesnt work.
I'm pretty nooby at this. I read a few other forums and they said something about flashing a new rom or something but I don't understand.
Please help! The phone isn't mine! Need help ASAP before owner finds out I messed up their phone, thanks!

If you can access fastboot and your bootloader is unlocked just flash a stock system image.
These are the reasons people shouldn't just one click everything they do. If you understood how fastboot worked you would be golden.

Reflash recovery. Then mount USB storage and then get a ROM on there and flash it.
Sent from my Galaxy Nexus using xda app-developers app

xjman said:
If you can access fastboot and your bootloader is unlocked just flash a stock system image.
These are the reasons people should just one click everything they do. If you understood how fastboot worked you would be golden.
Click to expand...
Click to collapse
The site I went to dumbed down everything, and all i had to do was input numbers into some program. I double checked what a fastboot was. I definitely don't know how to work that. I mixed up the fastboot with the bootloader...

how do i reflash recovery and get a rom on there? I know this is asking alot....sorry
My bootloader is unlocked but im not rooted. I will (figure out how to) root if needed.

Open up a terminal on your computer use fastboot to flash the recovery image.
Since you didn't take the time learn what you were doing to begin with, I would take the time now to go read. The answers are easily found with google, or searching this site.
Roughly, install adb and fastboot on your computer, load drivers for your phone, download the proper recovery and put it in the fastboot directory on your pc, plug in the phone boot to the bootloader
open term
./fastboot oem unlock
./fastboot flash recovery <nameofrecoveryimage>

I reached the fastboot part, but when i type in "fastboot flash recovery (file name) it says it cannot load file name...
What is the proper file that I should use? Running 4.04 YAKJU looking to just recover the phone back or switch to jelly bean, whichever is easier. (jelly bean if they are both the same)

okay okay okay, i think im almost there...got a rom and extraced it, i know how 4 files:
Boot 4,148KB
Recovery 4,478 KB
System 316,112 KB
Userdata 137,555 KB
Which one do I put for fastboot oem recovery (fileimagename)
Thanks

Stuck on Google screen
Background: GN is unclocked and rooted. I've had quite a few devices and have rooted them all and run custom ROMs. I am fairly familiar with all of the tools needed, but by no means an expert. I have the Android SDK with adb and fastboot installed on my Win 7 x64 machine as well as the samsung drivers. I loaded a Jelly Bean ROM the day after it was announced at Google I/O and ran it for awhile before I started having touchscreen issues. I removed the battery and restarted the phone and had no problems for about a week or so.
Problem: I started having touchscreen problems again, but figured it was perhaps due to the early version of JB that was ported over from the GSM version (I believe). I tried a few other versions that were released later and they would work for a few days and then the touchscreen issue would pop up again. At this point I started thinking it might be a hardware problem because if I twisted the phone (weird, but it worked) the touchscreen would respond. I flashed another version of the Jelly Belly ROM yesterday (//rootzwiki.com/topic/28677-rom-jelly-belly-v33-07122012-jellybean-411-pure-aosp-its-all-about-speed/") to see if it would work by chance. Unfortunately, I still encountered the touchscreen problem. After rebooting a few times my GN started bootlooping and would not load into Android.
Actions: At this point I tried to recover from a backup, but much to my dismay it failed (don't remember exact error). I tried a few other backups with no luck. I tried reflashing another ROM, no luck. Then I started seeing some errors when booting into recovery (E: can't mount cache/recovery/log. Around this time I also noticed I was getting errors with sdcard. I decided to take the phone back to stock using the verizon ICL53F factory image. I tried via numerous toolkits (Odin, Galaxy Nexus Toolkit and directly from fastboot) and have been unsuccessful. I've searched every forum and have literally tried everything I with no luck. I can flash new recoveries, but it doesn't solve my problem. Right now phone is back to stock with stock recovery and just bootloops at the Google screen.
I assume my phone is completely hosed, but am hoping someone might know something I don't and might be able to help me restore this phone.
Edit: I tried flashing an imm76k factory image via fastboot and was finally able to get in. I must have had a bad icl53f factory image...close call.

Stuck in a boot-loop

Hello everyone!
First of all, I would like to apologize, as these kind of issues have probably been talked about and solved a gazillion of times before, but the thing is, I'm having a hard time grasping the start and the end of this issue myself, as the phone that is stuck in a boot-loop isn't mine - it belongs to a friend of mine who somehow managed to get the whole thing bricked.
Anyhow, I'll start off with what I know;
His goal was to flash a new ROM (http://forum.xda-developers.com/showthread.php?t=1601543). He unlocked the bootloader and rooted the phone using these instructions; http://onexroot.com/one-x-root/how-to-root-one-x/). He succeeded in doing so and decided to move onto flashing the rom.
But the problems started when he read that he's first supposed to flash "Android Fastboot kit 2.1" onto the device, prior to flashing the device. And so he did. Or well, tried - what he told me was that he booted the phone into fastboot mode, then ran the "Install Boot.img" bat file inside the Fastboot Kit folder he downloaded and after that, the phone got bricked.
Now, my knowledge in this area isn't too great either, but I've flashed a few ROMs in my life before, so, I decided I'd do my best to help. But I have no clue on what steps he should take from here on.
To my understanding, he was running the official 1.29 version and he is still able to access the boot-loader as well as Clockwork Recovery mod. To my understanding, he didn't create a back-up of his previously working ROM and the phone won't show up in Windows Explorer while connected via USB either.
To my limited understanding, I should now try and install the rom onto his phone and once done, the whole thing should work - the only problem with that is the fact I can't get the ROM zip onto the SD Card right now, as explorer won't recognize it. So far, I tried using ADB to push the ROM file onto the phone, but every time I use the command "adb shell mount /sdcard" I get a "Device not foound" error. So, I'm kinda stuck here right now. If this even is the right way to solve the issue, that is.
So, like I said, I'm having a hard time grasping the start and the end of this issue myself, and if there is any additional information needed, I'll do my best to find out more about it - I do have the phone in my possession at the moment as well.
Thanks a lot to anyone who'll offer any kind of help!

Atraeh said:
Hello everyone!
First of all, I would like to apologize, as these kind of issues have probably been talked about and solved a gazillion of times before, but the thing is, I'm having a hard time grasping the start and the end of this issue myself, as the phone that is stuck in a boot-loop isn't mine - it belongs to a friend of mine who somehow managed to get the whole thing bricked.
Anyhow, I'll start off with what I know;
His goal was to flash a new ROM (http://forum.xda-developers.com/showthread.php?t=1601543). He unlocked the bootloader and rooted the phone using these instructions; http://onexroot.com/one-x-root/how-to-root-one-x/). He succeeded in doing so and decided to move onto flashing the rom.
But the problems started when he read that he's first supposed to flash "Android Fastboot kit 2.1" onto the device, prior to flashing the device. And so he did. Or well, tried - what he told me was that he booted the phone into fastboot mode, then ran the "Install Boot.img" bat file inside the Fastboot Kit folder he downloaded and after that, the phone got bricked.
Now, my knowledge in this area isn't too great either, but I've flashed a few ROMs in my life before, so, I decided I'd do my best to help. But I have no clue on what steps he should take from here on.
To my understanding, he was running the official 1.29 version and he is still able to access the boot-loader as well as Clockwork Recovery mod. To my understanding, he didn't create a back-up of his previously working ROM and the phone won't show up in Windows Explorer while connected via USB either.
To my limited understanding, I should now try and install the rom onto his phone and once done, the whole thing should work - the only problem with that is the fact I can't get the ROM zip onto the SD Card right now, as explorer won't recognize it. So far, I tried using ADB to push the ROM file onto the phone, but every time I use the command "adb shell mount /sdcard" I get a "Device not foound" error. So, I'm kinda stuck here right now. If this even is the right way to solve the issue, that is.
So, like I said, I'm having a hard time grasping the start and the end of this issue myself, and if there is any additional information needed, I'll do my best to find out more about it - I do have the phone in my possession at the moment as well.
Thanks a lot to anyone who'll offer any kind of help!
Click to expand...
Click to collapse
The latest Clockwork jobby will allow you to mount the sdcard as USB drive.
Other than that, you seem to be on the right track.

^ he's right
What you want to do is first download the 5.8.4.0 version of the endeavoru CWM recovery.
reboot to your bootloader, make sure you're in fastboot and flash the new recovery img.
After you have successfully flashed the new recovery, well... go to the recovery
On the recovery, tap mounts and storage, then tap Mount USB. VOILA!!!!!

Yeah, I forgot to mention that I've already tried mounting the SD Card via Clockwork Recovery - I get an error saying "Unable to open ums lunfile (No such file or directory exists). So that doesn't seem to be an option either, unless you have an idea on how to counter this?
EDIT: Ah, I see - he's using an older version. I'll get the latest one on board and give it a go. Will have to wait a bit for the phone to charge up first it seems though. Not enough battery to do it right now .
Thanks!

And voila! The phone is operational.
Thanks a lot for the help and, I just hope I never manage to half-brick my own HOX .

[GUIDE]How not to brick your device

Everyday I see posts about people Bricking( Soft bricking/Hard Bricking) their Xperia S, Ion,AcroS or any other Xperia.Most of the times it is because people know that they have to flash or root or to unlock bootloader but do not have a clear information about what it actually means
I am creating this thread in order to tell you what the terminologies actually mean and how to avoid these bricks
First things you should know:
What is Android??
Android is basically a linux based kernel Operating System for your phones(We probably have heard it a gazillion times)
What it actually means?
Android is an operating system for phones built on a linux kernel. Linux is nothing but a clone of Unix Operating System which is another operating system like Windows. One main feature of Linux is that it is open source unlike windows.
Example of Linux kernel based OS for computer includes Ubuntu
What is kernel?
Kernel is nothing but a bridge between your hardware and Software
What it actually means?
Kernel controls your software according to your systems hardware.So on a computer if you press a key(eg:a) on keyboard. Kernel tells the OS that the key a has been pressed and to interpret it accordingly.So on a phone if you touch the home button,The kernel tells your OS that home button has been pressed and to take action accordingly.
So now comes the question.What if you flash an incompatible kernel?
Simple. Think of your computer having nothing but the monitor and without any working hardware.(I have a keyboard with a defective 'm' key,irritates the hell out of me)...Same happens to your phone. Even the booting process needs the kernel and hence you get the dreaded Soft-Brick...
What is bootloader?
Bootloader is a partition on your device that tells the phone with OS to load
What it actually means?
In Windows you see C:,D: etc..one of them contain your windows folder. In linux,it is different in name,not the concept. In linux based OS like Ubuntu, the partitions are /boot,/home,/root,/system,/recovery.....just like c:,d:,e: etc....
in android stock, you will have /boot,/system,/root.../boot is nothing but the bootloader...and in our sony phones this /boot aka bootloader is locked
What does bootloader contain?
bootloader as the name suggests tells your phone which os to boot..in our case it is the stock rom or custom or whatever os u have on the phone. Pretty self explanatory.
What is Flashmode and fastboot?
Flashmode as the name suggests is a mode which allows you to flash stuff(ROM's,kernel etc) on your phone
Fastboot mode: fastboot mode is another mode on your phone that allows you to flash stuff as well as debug it
What it actually means?
Flashmode: Pretty self explanatory
fastboot: It is used by both flashtool as well as ADB. fastboot allows you to test your kernel or whatever you are flashing..
command: fastboot boot boot.img
This command will boot boot.img(containing kernel/recovery or both and ramdisk) on your phone but wont flash it i.e. a test run. If boot.img doesnt boot,you can just disconnect and restart
command: fastboot flash boot boot.img
This command will flash the boot.img on your phone and then start it with the new boot.img.
Now fastboot wont work with a locked bootloader.So you cannot flash anything on your phone that requires a fastboot flash if your bootloader or /boot partition on your phone is locked
What is flashtool?
Flashtool is a tool developed and maintained by Androxyde, Bin4ry ,Doomlord. This tool lets you do a lot of things to your phone but its main usage is to flash stock Roms, kernels or anything that comes in an ftf package on your phone
What it means to you?
If anything goes wrong. The first thing you would need is this tool to revert back to Stock ROM. So keep this tool ready in case you are entering into the world of flashing custom firmware
What all can go wrong?
Frankly a lot of things(including power cuts,battery going dead)..
What you can avoid?
First thing,read read and read...A custom ROM would have a list of compatible devices..Go through the post and see if your device is listed. If your device
is listed and compatible then you can proceed. Flashing an incompatible ROM will result in a soft brick or hard,depending upon what you are flashing
>Next check if ROM requires a locked bootloader or unlocked(Important)
>Next if you are planning on unlocking bootloader, its better to flash CWM first on your phone and then flash ROM through CWM
What is CWM?
CWM aka Clockworkmod is a custom recovery that allows you to do a host of stuff including flashing of ROMs or zip packages
What it means to you?
Every phone has a recovery partition just like i told in the partition section. However, Latest Sony phones including Xperia S,ION,Acro S do not have one. Now most phones have a stock recovery system which allows users to reset their phones if something goes wrong. But, just like Custom ROMs, We have Custom Recoveries like CWM aka ClockworkMod developed by Koush that has many more options like flashing packages,taking a backup.
So basically CWM would be used by you to take a backup of your current system first and then flash the ROM. Now if anything goes wrong and you get a softbrick, you can just go to CWM and restore your backup and voila!!your phone will be back to normal again
Key Points:
1. CWM needs root
2. Recovery partition is not included in Sony.So, CWM is incorporated into the kernel itself by the kernel developer. What this means to us is that we would need an unlocked bootloader for installing CWM as we would have to flash the CWM included kernel to the boot partition
>Next, Always double check the requirements of the ROM you are going to install(Important)
Ohh before i forget...What is this ROOT everyone talks about?
ROOT is nothing but administrative access to sensitive parts of your OS
What it means to you?
It is nothing but getting admin rights to your system,in our case its our phones. you wont have root access on your phones by default. one major reason for this is safety. So that people don't delete a system file by mistake and what not
With root you can do everything with your phone. Thanks to our devs, we have loads of methods available to root your phone. Good place to search would be the search button
Why are we talking about root??
Because it might be a prerequisite for your custom ROM or a part of another prerequisite for installing your ROM.
>Now double check requirements again. And don't skip any step
>Once you have met all the requirements. Lets start flashing.
Ok now what can go wrong. First low battery..phone went dead while flashing..solution: Please charge it atleast while you finish the other requirements
Laptop crashes(Very Bad luck)..Solution: Always prefer to have the ROM installed through CWM and a backup ready. If you are lucky enough, you will be able to boot into CWM to restore backup and start again.
If you are flashing through any other method, then dont worry, have flashtool ready and your stock firmware..(Check firmware before installing if its for your phone:Very Important)
Check Exclude TA partition in flashtool unless absolutely necessary
Note: If your phone is bricked, it is always better to flash your kernel first(personal opinion), Once that is done, you can easily flash the full firmware
And please wipe cache and dalvik cache after flashing a ROM through CWM: Half the people wont perform this step and then try to find solutions for the bootloop. You can do this either through the CWM or ADB. For ADB method, just search the forum
One last thing and very very important. For Phones running stock firmware with unlocked bootloader or custom FW based on stock kernel with unlocked bootloader. Don't do an OTA update as this will hardbrick your device. Better download an stock FTF of that firmware version and flash it via flashtools
If still your phone bricks then there is a very nice thread here http://forum.xda-developers.com/showthread.php?t=1849170 by Toledo_JAB on bricked phone recovery
In the next post i will add some more information like TA partition backup, some more info about Android..etc.....
In case i have forgotten anything or have given the wrong info, please let me know so that i can add/edit the OP

Reserved

Last one

may i recomend mesaging a mod or admin to pin this thread or are you already on that
Sent From The ACP HQ

Envious_Data said:
may i recomend mesaging a mod or admin to pin this thread or are you already on that
Sent From The ACP HQ
Click to expand...
Click to collapse
No bro.this is my first thread so don't know how to get it stocked

Dark Wraith said:
No bro.this is my first thread so don't know how to get it stocked
Click to expand...
Click to collapse
just PM a mod with a kind message (mod names can be found above the threads in a section)
( i dont realy know how but thats what people talk of so i assume asking a mod is the only way to pin a thread
not to hard to miss ;D
Sent From The ACP HQ

Envious_Data said:
just PM a mod with a kind message (mod names can be found above the threads in a section)
( i dont realy know how but thats what people talk of so i assume asking a mod is the only way to pin a thread
not to hard to miss ;D
Sent From The ACP HQ
Click to expand...
Click to collapse
Haha.. I'll ask if people read the thread mate and benefit from it..till now no such enthusiasm so we'll see

nice
nice

Add: -Don't clear emmc under clockworkmod. ;D
-SnowKatana ^_^~

Good
very easy to understand, Nicely explained...
I just want to know what is hard brick?

Can't get Sony Xperia Ion into recovery mode

Hey guys!
My friends might describe myself as tech savvy but I've never really gone into rooting or andorid devices in general. I'm currently following a guide on android (dot) gs (which I can't link to specifically, as this is my first post, I'm sure a quick search might show it) to install the 4.4. Pureslim Firmware. Up until now I've rooted it with this app called KingoRoot which seems to have done... something successfully. I'm at the point in the guide where I've downloaded the packaged firmware update onto the SD card, the next step is to set it into recovery mode, whipe it clean and use the data on the SD card to install the firmware. But here's the problem...
I can't get the Ion into recovery mode, I've tried some silly "press the powerbutton and volume up and volume down and do a backflip" things which didn't seem to work out, the apps in the guide on the android (dot) gs site on recovery mode for android devices (again, no link but you might know the page) point to don't seem to do much either, when I tell it to restart in recovery, it just reboots normally. I've also read a few times that the Ion doesn't even have a standard recovery mode, but that means there's no way for it to go into recovery as it is?
Hoped you guys could shed some light on this, thanks in advance! :good:

rustyg93 said:
Hey guys!
My friends might describe myself as tech savvy but I've never really gone into rooting or andorid devices in general. I'm currently following a guide on android (dot) gs (which I can't link to specifically, as this is my first post, I'm sure a quick search might show it) to install the 4.4. Pureslim Firmware. Up until now I've rooted it with this app called KingoRoot which seems to have done... something successfully. I'm at the point in the guide where I've downloaded the packaged firmware update onto the SD card, the next step is to set it into recovery mode, whipe it clean and use the data on the SD card to install the firmware. But here's the problem...
I can't get the Ion into recovery mode, I've tried some silly "press the powerbutton and volume up and volume down and do a backflip" things which didn't seem to work out, the apps in the guide on the android (dot) gs site on recovery mode for android devices (again, no link but you might know the page) point to don't seem to do much either, when I tell it to restart in recovery, it just reboots normally. I've also read a few times that the Ion doesn't even have a standard recovery mode, but that means there's no way for it to go into recovery as it is?
Hoped you guys could shed some light on this, thanks in advance! :good:
Click to expand...
Click to collapse
You have to unlock your boot loader first.then you have to install recovery.then you can be able to boot to recovery