Hello, I tried today to s-off my desire but failed so i gave up but ended up with the usb-brick issue, no problems here, lots of tutorials, but I accidentally updated my phone OTA from HTC and now I don't have amon-ra recovery anymore, only the android recovery which needs signed packages. I do have the SU app installed, so I guess my phone is still rooted, but I am unable to install a recovery in order to unbrick my phone. The only thing that is working is "fastboot", but can't flash a new rom, can't flash a new recovery.
Any ideas? I really don't want to sent my phone to a service...
LE: If I try to install any app from any source, including Market, my phone restarts, fast restarts actually...
tried unrevoked? this installs clockwork recovery mod.
or android flasher -attched
doesnt your phone needs to be ON with unrevoked? from there you must plug it in whith unrevoked opened on your PC.
But you can always try. I highly doubt your phone is unfixable, itll be allright.
Tried to re-root my phone but because my usb connection doesn't work anymore, the unrevoked program doesn't "see" my phone. The only thing that i need, in my opinion is an root explorer packed as a signed zip that the original android recovery can flash and i may be able to regain usb functionality.
you should try a differnt PC and do the process. I had a similar issue sometime back and when I changed the PC i was working on it worked.
That doesn't make much sense because the problem is in my phone, not in my computer...
Latest update: I prepared my phone for service, managed to flash a shipped rom without root, so there is no sign on it that I rooted it or flashed another custom rom/recovery. Still can't access the phone via usb so unrevoked still not a solution. Any new ideas before I say bye-bye to my Desire ?
HyperL said:
That doesn't make much sense because the problem is in my phone, not in my computer...
Latest update: I prepared my phone for service, managed to flash a shipped rom without root, so there is no sign on it that I rooted it or flashed another custom rom/recovery. Still can't access the phone via usb so unrevoked still not a solution. Any new ideas before I say bye-bye to my Desire ?
Click to expand...
Click to collapse
You should try this :
- usb debugging mode ON
- install VWM ( virtual ware machine ) and boot with the .img of the hboot needed at http://alpharev.nl
- the device should be plugged and the aplharev hboot pushed with the last clockworkworld recovery
if not working, unfortunately not so many solutions but you still can try to unbrick the usb and then you will "unrevoked" easily your desire !
Take a look on alpharev developers chat for bricked phones
Hope it helps
My last piece of work
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Nothing posted on xda or other android forums worked so today I handed my Desire to my carrier because I still have warranty . I hope they don't find any of my modifications , I did un-rooted it so it should be stock enough for them
Something I do not understand :
Last time I USB bricked my phone, I went to hboot, then fastboot, and entered the fastboot commande :
Code:
fastboot oem enableqxdm 0
as stated in many tuto.
This re-enables the USB, and then, you may again flash any recovery via unrevoked.
Actually that command re-enables the micro-sd controller, not the usb.
Related
Hi!
I just tried to change from RCMixHD (D2EXT) to CM7.
As first, I flashed the AlphaRev CM7 image via Android Flasher and right after that the newest radio version via recovery (32.54.00.32U_5.14.05.17). Since the radio is flashed, i was unable to flash anything in recovery mode, so i decided to format everything, wipe all data so that I just lost my current ROM. It still didn't work, so i decided to reflash the Recovery via Android Flasher and now I can't even boot into the recovery menu. For now I can only boot into the HBOOT and use the fastboot. I got Micro-SD adapter to put anything to my SD-Card, but currently i got no idea what to do. Are there any ROMs i can flash with fastboot?
Got any hints to unbrick the recovery?
Current overview of information:
Desire is S-OFF
No current ROM (full data wipe)
Recovery unbootable (stucks at AlphaRev splashscreen)
HBOOT bootable
SD Card formatted with 5,5gb FAT32 and 2gb EXT4
Got Android SDK installed on my computer
Flash CWM 2.5.0.7 or amon ra via fastboot, make sure it's the desire version and md5 matches. Then install a rom.
Sent from my HTC Desire using XDA Premium App
Or go back to stock with RUU for your phone and start again
Thanks for now!
Just flashed the CWM manually with fastboot and i can boot into the recovery again.
However, the recovery is still hanging up when I do any actions related to the sdcard. No update.zip, no manual chooses possible, no wipe.
But for me, it looks like it's not the sdcard which currently ****s up everything, it seems to be the phone itself. I can still mount my sd in recovery, i can also format everything manually, but as soon as i try to install or choose a factory reset, the recovery ends up in a black screen.
--------
edit:
Okay. Looks like i fixed it now by wiping dalvik, battery stats, cache and then wiping data.
Still confused why it works now, but thank you for pushing me into the right direction. Now i can get everything back to work. Thanks!
why hello there!
Has been a while since i had to recover a phone from a worst case scenario, so i thought i could just revive this thread, as there is no desire 310 subforum yet
Rooted it successfully, read a lot of threads regarding MTK-based phones and thought i might be able to get more out of it, as i wasn't completely fine with 4.2.2 installed on a brand new phone.
However, i ended up with trying to install a custom recovery as described [here(would be a link if i were allowed to post them)]. The whole process gave no error, everything looked fine, ending with a "success!"-message, followed by a reboot, showing just the HTC splash... and a reboot... and a reboot... and.. well i guess you know what happened next.
Based on a whole lot of different threads, this might not be the end of my phone, as i can still see the [preloader(would be a picture if i were allowed to link it)] in my device manager, which basically means "hi, i'm not completely dead and you might find a way to recover me".
The question is: how?
I tried out SP Flash tool and MTK Flash tool so far. both programs find the phone when i get it ready to download my previously made backup (hey. i might not exactly know what i'm doing there, but at least i saved everything before i wrecked it! ).
The problem is: I just get an[error message(look above)] about some failed download to SRAM sorcery, which sounds cool and important but doesn't give me a clue about what i'm doing wrong or how to fix it. (cable ok tested 3 different cables, including the one the device was shipped with, also tested it on my PC running win 8.1 x64 and another one running win 7 x86)
Does anyone have an idea how i could get at least a working bootloader/recovery back to my device?
Tell me if you need any extra information
I also link an attachment including the log file created by SP Flash Tool.
View attachment SP_FT_Dump_05-31-2014-12-45-24.zip
Well. That's it. Thanks in advance for anything that may be posted in here
edit:
pictures mentioned above
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi guys, i have decided to get my desire back to stock and i have the asian RUU that i download from xda.
I am rooted with s-off and amonra recovery. Im on the Stock rooted ROM w/ A2SD.
1) Went to fastboot and into fastboot_USB mode and then ran RUU from PC
2) at arnd 59% it gave me an error error 110: File Open Error (is this a RUU corrupted of what?)
3) Then it went into a half-bricked mode where theres 4 exclaimation marks on the 4 corners
lucky i managed to recover into last working state again. (adb coundnt detect my phone; it works with my S2)
I went on to format phone from Settings, but my apps, etc are still there.
Can anyone tell me what to do and where to start?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What hboot partition have you.got?
Sent from my HTC Desire using xda premium
i didnt touch the partition table. i just ran alpharev s-off only.
just tried this downgrading tool.
http://forum.xda-developers.com/showthread.php?t=768256
how it stucks at the green HTC logo w/ white background.
Tried to run a RUU but error 170 USB error
EDIT: Somehow everything went smoothly on my laptop and im back to stock. but i gotta un s-off.
S-off:
Ran the Same RUU but now error 131: Customer ID error, however when i went into bootloader, its already S-off
ok just a summary of what happened and issues i faced and resolved for future references
Im coming from stock rooted ROM w/ app2sd, root, s-off, amonra recovery and i wanna go back to stock.
*I lost my gold card as my sd card was corrupted.
1) Ran the downgrade tool from this thread: http://forum.xda-developers.com/showthread.php?t=768256 (luckily i passed w/o the goldcard)
2) When booting up, i was stucked at the green HTC logo
3) Ran the RUU file: RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00. 32U_5.11.05.27_release
from http://forum.xda-developers.com/showthread.php?t=695667
4) At this stage, ROM, recovery is back to Stock. Except s-off.
5) Using help from this link : http://forum.xda-developers.com/showthread.php?t=1275632
flashed the bravo_downgrader and HBOOT became alpharev unlock and I ran the same RUU
6) I used the same RUU but it says Customer ID error but when i checked my bootload, i was alrdy S-on
Hello devs,
my HTC Desire Z broke over night.
The phone still works, boots and runs as expected, but the Screen is dead, although the Touchscreen is still working (PatternUnlock working and so on).
I want to send it in for warranty repair, but I still have flashed Clockwork Recovery with S-OFFand Cyanogen 9 RC1 and root.
That's the reason why I want to flash the original image PC10IMG via fastboot.
How can I access the bootloader and boot into fastboot?
I tried:
Volume Down and waiting long enough (~45s) and then pressed Power to access Fastboot, but it doesn't work.
(I think the clockwork menu is presented instead of the android bootloader menu, which I don't know by minds).
Debug mode is off on the phone, so "adb reboot fastboot" does not work
Can someone with a Desire Z and Clockwork Recovery flashed give an step-by-step instruction how to boot into fastboot if your screen is dead?
Thank you in advance.
me|kor
Here you go, perfect guide for you: [GUIDE] Returning to stock, unroot. Also with broken screen/digitizer
-Nipqer
Nipqer said:
Here you go, perfect guide for you: [GUIDE] Returning to stock, unroot. Also with broken screen/digitizer
-Nipqer
Click to expand...
Click to collapse
That's what I tried already, but sadly it doesn't work due to Clockwork Recovery I think.
My device reboots when I press power after one minute, which makes sense if this screenshot represents my menu.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In the ClockworkMod in this screenshot is fastboot not listed and I couldn't find a screenshot of the advanced menu nor the complete menu structure where fastboot was listed.
I'm using the most recent version of Clockwork Rom Manager and Recovery Image
Should be 5.0.2.7 I think.
You don't need to use recovery at all with my guide.
You can go straight to fastboot mode, from powered down, by holding the Trackpad while powering on, then you can use your computer to talk to it and send a rom to flash.
-Nipqer
Nipqer said:
You don't need to use recovery at all with my guide.
You can go straight to fastboot mode, from powered down, by holding the Trackpad while powering on, then you can use your computer to talk to it and send a rom to flash.
-Nipqer
Click to expand...
Click to collapse
Thank you very much I didn't knew the Trackpad shortcut and didn't find / oversee it in your guide.
That was the one I needed.
You made my day!
:fingers-crossed:
Yeah I don't think I mentioned it in my guide, as the guide is also written for Ace/Glacier, which don't have trackpads.
I'm glad you managed to get it sorted
-Nipqer
Hi guys,
I can't flash any ROM/Kernel/whatever file via Bootloader/ODIN & Recovery. Worst still I can't access Recovery now.
My Nexus can goto Bootloader or ODIN mode but once i started to push files to it, it will just freeze. Please refer below for photos:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
BEFORE
AFTER
My Gnex was on the latest Paranoid ROM and Franco kernel.
Timeline:
1. It just went into bootloop when I am just browsing the internet.
2. Went to Recovery to clear cache. (that's my mistake, should have waited longer for my device to boot :crying
3. Still bootloop.
4. Went to recovery to flash stock kernel as I suspect it's kernel fault.
5. Kernel flash failed as it the operation was aborted and restarted. Bootloop again.
6. Done battery pull and went to Recovery to Restore my backup Nandroid.
7. Flashing halfway and it frooze.
8. Can't access Recovery anymore.
9. Tried to restore stock rom using ODIN. Failed at NandWrite as the screen froze as the above image.
10. Tried WugfFresh to restore back to stock rom and failed again as the screen froze.
So guys, can i conclude that my motherboard is the culprit here?
Thanks in advance.
Are you able to get into the bootloader? Have you tried manual fastboot flash of factory images?
ual4720 said:
Are you able to get into the bootloader? Have you tried manual fastboot flash of factory images?
Click to expand...
Click to collapse
Hi,
Yes, I am able to get to bootloader.. the problem is when i start to do fastboot flash the factory images (using WugFresh).. the screen will start to freeze with double image as per my 1st post...
:crying:
d3vils said:
Hi,
Yes, I am able to get to bootloader.. the problem is when i start to do fastboot flash the factory images (using WugFresh).. the screen will start to freeze with double image as per my 1st post...
:crying:
Click to expand...
Click to collapse
Sound like there is a possibility of corrupt nand partition .... though that is usually unlikely unless you are an extreme flashaholic ... but still possible
but the guy above is suggesting use the fastboot commands manually rather than using the toolkit as it sometimes makes a difference
As in manually flash the recovery in the bootloader then see if you can get into recovery, but there are many avenues that you can take to see where you can get with this. There are many places that explain how to do this step by step on the web.
Also you should always try switching usb ports and usb cables as sometimes it will cause issues
I know i used the same usb port with the same usb cable to flash my n7 and gnex multiple time then one day it just stopped working switched the port and cable then it started working again.
But other than that I don't know much about is a possible JTAG but I really doubt that will help at all since the device does does get into bootloader and odin just freezes....
cmaag said:
Sound like there is a possibility of corrupt nand partition .... though that is usually unlikely unless you are an extreme flashaholic ... but still possible
but the guy above is suggesting use the fastboot commands manually rather than using the toolkit as it sometimes makes a difference
As in manually flash the recovery in the bootloader then see if you can get into recovery, but there are many avenues that you can take to see where you can get with this. There are many places that explain how to do this step by step on the web.
Also you should always try switching usb ports and usb cables as sometimes it will cause issues
I know i used the same usb port with the same usb cable to flash my n7 and gnex multiple time then one day it just stopped working switched the port and cable then it started working again.
But other than that I don't know much about is a possible JTAG but I really doubt that will help at all since the device does does get into bootloader and odin just freezes....
Click to expand...
Click to collapse
corrupt nand partition... that's an interesting theory... will explore on the solutions on the manual fastboot commands...
thanks!!
My phone: Asus Zenfone 3 Deluxe NON PRO with the snapdragon 820 2.15ghz CPU..
When I try to enter fastboot mode my phone just goes nowhere and sits there. If I hard reset the phone it turns on again.. Calls and works but take one picture with camera and it shuts off.. gets the picture oddly.
Ive installed ADB on my PC and I'm about to start seeing if I can talk to the phone in fastboot even though the phone itself shows nothing at all. This happened during a failed upgrade and has NOT been able to upgrade since. I'm on 6.0 still.. failed 7.0
My question: Is there a certain way I should attempt to flash the files using ADB? I do have the RAW files from Asus support..
I'm going to post a couple pictures and a short video if needed to make this easier to understand for anyone reading this, I'm just going to try some simple commands first in ADB and see if the phone responds first. I have a feeling this could make everything much much easier if it does.
Try to enter fastboot or flash from here?
I have no recovery that I know of my phone goes totally dead when its in recovery mode and doesn't seem to respond to anything at all BUT.. When I plug in a cable it makes the connecting sound over the PC.. I'm about to try a few different scenarios of trying to enter fastboot other than manually with the side buttons but if that doesn't work what are my odds of repairing my file system from this state? I can get into MOST of the files in the LS.. but not all I do not have root access but I can get into pretty much everything else just FYI. If anyone has any questions or advice feel free to chime in at anytime.
I got into fastboot using command.
I assume its pretty straight forward from here I'll just post the steps I'm about to take or links to what guide or guides I follow just in case anyone else suffers from this in the future.
I used the commands in the following order :
adb devices (to start the server)
adb shell (to get connected to the phone)
reboot bootloader (to reboot into fastboot)
When the phone rebooted it looked stuck on the Asus logo but once it settled I tried the command :
fastboot devices (BAM it showed up instantly)
Now I have downloaded some RAW STOCK and TWRP files I'm I'm planning to restore my factory 6.0 ROM.
If this is successful then I plan to make a backup... and then sleep before I play more lol
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
BWPHonda said:
I assume its pretty straight forward from here I'll just post the steps I'm about to take or links to what guide or guides I follow just in case anyone else suffers from this in the future.
I used the commands in the following order :
adb devices (to start the server)
adb shell (to get connected to the phone)
reboot bootloader (to reboot into fastboot)
When the phone rebooted it looked stuck on the Asus logo but once it settled I tried the command :
fastboot devices (BAM it showed up instantly)
Now I have downloaded some RAW STOCK and TWRP files I'm I'm planning to restore my factory 6.0 ROM.
If this is successful then I plan to make a backup... and then sleep before I play more lol
Click to expand...
Click to collapse
Were you able to repair your CP? im still looking for ways to back up my data before proceeding