Related
A long time ago I rooted my phone and put CM9 on it. I decided I wanted to go back and try Jelly Bean (from factory then go outwards).
I had a difficult time with the CM flash and found one that worked, and thought I was good to go.
My phone: gt-i9020a nexus s
Product name: Herring
HW version 16
boot loader: i 9020xxkl
carrier att
fastboot enabled
unlocked state.
I can launch the official 2.3.6 (Build GRK39F), from google
then the OTA updated kicks in and the phone is stuck at 'boot' Google logo on the screen.
I have done the information below and the same keeps happening...
link: http://forum.xda-developers.com/showthread.php?t=1586845
first of all, the VQ8PQk is a patch file, not a full rom. So flashing that on something else than 2.3.6 will never work. Get into clockworkmod recovery wipe wverything from the mounts and storage menu, and then flash this file : http://android.clients.google.com/pa...o/ZD3PyN0t.zip and THEN this : http://android.clients.google.com/pa...o/hR7QFEtn.zip
and other steps I could try to work around, none of them seem to work.
Am I missing anything?
Thanks!
Use the full factory rom images (sojuaxxxx) from Google.
https://developers.google.com/android/nexus/images#sojua
Follow the instruction on that page (scroll up). If using Windows, use 7zip (or similar util) to expand the .tgz file, open content of "flashall.sh" and execute the commands one at a time.
Code:
fastboot flash bootloader bootloader-crespo-i9020xxlc2.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo-i9020uckj1.img
fastboot reboot-bootloader
fastboot -w update image-sojua-jro03e.zip
The last command will wipe all data and install new 4.1.1 rom.
Edit: install CYGWIN to have linux-like commands (works with tar, adb, fastboot) in windows.
Do you have a backup (preferrably CWM backup) that you have prior to trying to get JB working? If so keep that handy, and preferrably store it on the PC. Titanium backup can ease migrating apps after a wipe and is highly recommended, so do one of these too if you havn't already.
After you make sure you have a solid backup with the information that you want/need on the phone, i would just start fresh. The best way to do this is to do a factory image flash (note: you want sojua if you have the 850MHz variant which is from AT&T). Flashing these will wipe all user data and the /system partition, the sdcard won't be touched. Basically you download it, extract it, then hook up your phone in fastboot mode and do the commands as written in the text file (or run it as a script if you know how). I've described it in more detail elsewhere as have others, doing a search should give results pretty quickly
This will become a factory install of android as given by google, in your chosen version. I'd go straight ot JB and then you can see how much you like it. CWM backup data can be extracted if you lost some crucial information in the flashing and all your apps and their data can be easily restored with titanium backup.
morning update
_android_ said:
Use the full factory rom images (sojuaxxxx) from Google.
Follow the instruction on that page (scroll up). If using Windows, use 7zip (or similar util) to expand the .tgz file, open content of "flashall.sh" and execute the commands one at a time.
Code:
fastboot flash bootloader bootloader-crespo-i9020xxlc2.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo-i9020uckj1.img
fastboot reboot-bootloader
fastboot -w update image-sojua-jro03e.zip
The last command will wipe all data and install new 4.1.1 rom.
Click to expand...
Click to collapse
running linux, no cygwin needed
did this again this morning..and i'm stuck on the google boot screen with the unlocked padlock on the bottom.
how long should this run (20 minutes now)
I have tried the roms from that page, the 2.3.6 is the only rom that I was able to get working..
lost_man said:
running linux, no cygwin needed
did this again this morning..and i'm stuck on the google boot screen with the unlocked padlock on the bottom.
how long should this run (20 minutes now)
I have tried the roms from that page, the 2.3.6 is the only rom that I was able to get working..
Click to expand...
Click to collapse
Make sure you use the sojua versions.
Do you mean you finish all the steps and upon reboot, it's stuck on Google boot screen?
What do you mean by you can only get 2.3.6 working? It went past Google boot screen?
** ran 'flash-all.sh" see if that changes anything, nothing like a script to rule out human error.***
**** that was a mistake...now phone is not turning on, the screen is dead...when i plug in USB chord, nothing is detected no state change on the phone. When I press buttons no state change nothing changes on the screen. I actually think my phone is a true brick, not a software glitch that is fixable....any suggestions now? ****
lost_man said:
** ran 'flash-all.sh" see if that changes anything, nothing like a script to rule out human error.***
**** that was a mistake...now phone is not turning on, the screen is dead...when i plug in USB chord, nothing is detected no state change on the phone. When I press buttons no state change nothing changes on the screen. I actually think my phone is a true brick, not a software glitch that is fixable....any suggestions now? ****
Click to expand...
Click to collapse
Some (quite a few) Nexus S seemed to be vulnerable to Jelly Bean/CM10 update in that the mainboard is toast. I think the only option is to send back for warranty repair. There are some threads on rigging some kind of adapter cable but that will definitely void your warranty (physical mod).
Doesn't sound good, there have been instances where the flash storage has given up and ends up needing a new SoC (the whole mainboard) and similar issues. Some more information would be good to diagnose this better though.
-Take the battery out for 5 minutes, place back in, can you get into fastboot?
-Can you flash recovery and radio? Can you enter recovery?
-After the "fastboot -w update ...." command, what messages do you see on the phone (at the bottom)?
If you can't get the phone to turn on at all after a good 5 minutes without the battery inserted, give AdamOutlers resurrector a shot. A nice phone call to samsung might be a good idea if you're still within 12 months of purchasing. Hopefully it all turns out okay.
-Take the battery out for 5 minutes, place back in, can you get into fastboot?
-Can you flash recovery and radio? Can you enter recovery?
-After the "fastboot -w update ...." command, what messages do you see on the phone (at the bottom)?
If you can't get the phone to turn on at all after a good 5 minutes without the battery inserted, give AdamOutlers resurrector a shot. A nice phone call to samsung might be a good idea if you're still within 12 months of purchasing. Hopefully it all turns out okay.
Click to expand...
Click to collapse
Did all of the above, nothing. adamoutliers does not see a device connected.
lsusb shows nothing
dmesg shows my device disconnect, after the failed boot, no reconnect.
I'm headed out for a few hours, I will leave battery out, and phone disconnected but i'm thinking it's toast. Att will send an RMA phone to me, they gave me a choice of samsung focus (I asked how a windows phone was similar to an android?) or a samsung galaxcy II skyrocket...I'll try samsung next..
Thanks for all the help!
lost_man said:
Did all of the above, nothing. adamoutliers does not see a device connected.
lsusb shows nothing
dmesg shows my device disconnect, after the failed boot, no reconnect.
I'm headed out for a few hours, I will leave battery out, and phone disconnected but i'm thinking it's toast. Att will send an RMA phone to me, they gave me a choice of samsung focus (I asked how a windows phone was similar to an android?) or a samsung galaxcy II skyrocket...I'll try samsung next..
Thanks for all the help!
Click to expand...
Click to collapse
How do i close this thread? It's done, the phone is dead...rma...
So, where to start?
I'll start with my broken screen:
1 -new screen ordered (complete assembled LED+digitizer)
2 -installed the new screen, put phone back together and turned ON
3 -phone immidiately went into bootloop!
4 -did some google research and found this site and figured out how to get into bootloader (vol down+pwr)
5 -bootloader works fine, but left it on too long with phone not on charger (battery might have died?) phone not turning on and red LED blink while in charger
6 -ordered new battery, it arrived today. Phone got back on and into bootloader.
7 -unlocked bootloader by using the HTCDEV com site, and their method. worked fine!
8 -then turning phone back on after a failed restart after the bootloader unlock, and it wont turn on taking me back to stage 5
The phone was connected via usb during the bootloader unlock and the restart after. But I never got it back on
There is one thing I am curious about aswell - the phone get very hot around the SD-card slot and it smells warm electronics. I dont know if this is normal but I cant say I noticed this before when the phone was working. I am very sure that I re-assembled the phone correctly after replacing the LED+digitizer as both these parts came to me already assembled.So only thing I did was removing the screen case with the LED and digitizer and replacing it with the new one.
I really hope anyone have ANY input on this as I would really like to get my phone back on and working so I can root it.
Sverrebob said:
So, where to start?
I'll start with my broken screen:
1 -new screen ordered (complete assembled LED+digitizer)
2 -installed the new screen, put phone back together and turned ON
3 -phone immidiately went into bootloop!
4 -did some google research and found this site and figured out how to get into bootloader (vol down+pwr)
5 -bootloader works fine, but left it on too long with phone not on charger (battery might have died?) phone not turning on and red LED blink while in charger
6 -ordered new battery, it arrived today. Phone got back on and into bootloader.
7 -unlocked bootloader by using the HTCDEV com site, and their method. worked fine!
8 -then turning phone back on after a failed restart after the bootloader unlock, and it wont turn on taking me back to stage 5
The phone was connected via usb during the bootloader unlock and the restart after. But I never got it back on
There is one thing I am curious about aswell - the phone get very hot around the SD-card slot and it smells warm electronics. I dont know if this is normal but I cant say I noticed this before when the phone was working. I am very sure that I re-assembled the phone correctly after replacing the LED+digitizer as both these parts came to me already assembled.So only thing I did was removing the screen case with the LED and digitizer and replacing it with the new one.
I really hope anyone have ANY input on this as I would really like to get my phone back on and working so I can root it.
Click to expand...
Click to collapse
Pull out the battery then place again and after that try to go into bootloader ..
Also phone showing red light while charging ?
ahsan64 said:
Pull out the battery then place again and after that try to go into bootloader ..
Also phone showing red light while charging ?
Click to expand...
Click to collapse
I let the phone cool down (it get's very hot very fast!) and removed battery and replaced it again, phone ON and in bootloader now, thanks
The heat issue still remains tho, I wonder if this might be the source of this unstable situation with the phone not turning back on and then suddenly after a cooldown it does... any thoughts?
EDIT: Yes when this problem occurs the red LED blinks "on long" "off long" while the phone is in charger.
Sverrebob said:
I let the phone cool down (it get's very hot very fast!) and removed battery and replaced it again, phone ON and in bootloader now, thanks
The heat issue still remains tho, I wonder if this might be the source of this unstable situation with the phone not turning back on and then suddenly after a cooldown it does... any thoughts?
Click to expand...
Click to collapse
Are you using Stock Rom or Custom Rom ..
The heat issue is normal but sometime it's due to overclocking 2d/3d GPU ..
ahsan64 said:
Are you using Stock Rom or Custom Rom ..
The heat issue is normal but sometime it's due to overclocking 2d/3d GPU ..
Click to expand...
Click to collapse
The phone is completely stock except the replaced screen. I encountered the bootloop after replacing the screen and it's been like that since...
Sverrebob said:
The phone is completely stock except the replaced screen. I encountered the bootloop after replacing the screen and it's been like that since...
Click to expand...
Click to collapse
Two methods:
1: Follow this GUIDE if phone Hboot is 1.27 or 1.29 and flash any custom Rom .
NOTE: You can skip step 2(S-OFF PART) in above guide
2: Or just find official RUU and install it and see if phone boots ..
ahsan64 said:
Two methods:
1: Follow this GUIDE if phone Hboot is 1.27 or 1.29 and flash any custom Rom .
NOTE: You can skip step 2(S-OFF PART) in above guide
2: Or just find official RUU and install it and see if phone boots ..
Click to expand...
Click to collapse
Ok I will try this thanks!
Just got the phone back on and into bootloader, had to let it cool off again to get it on. I feel somewhat connected to the other thread in this forum - "Dead sensation" ...
Update :
I cant seem to access the sd card when I have my phone in Fastboot usb mode and since my rom is f**ked I cant boot into the phone either.
Also recovery fails, probably due to fastboot still active, any way to turn that off when I cant get past bootloader?
And if anyone know how I can access the sd card from phone on my PC I would appreciate it :/
De-assembled my phone again just to recheck all connectors etc, all seems just fine... really confused on whats up with this phone now :/
Sverrebob said:
Update :
I cant seem to access the sd card when I have my phone in Fastboot usb mode and since my rom is f**ked I cant boot into the phone either.
Also recovery fails, probably due to fastboot still active, any way to turn that off when I cant get past bootloader?
And if anyone know how I can access the sd card from phone on my PC I would appreciate it :/
De-assembled my phone again just to recheck all connectors etc, all seems just fine... really confused on whats up with this phone now :/
Click to expand...
Click to collapse
it would be better to use a ruu.exe and see how it goes then
http://forum.xda-developers.com/showthread.php?t=1672425
my bootloader reads as follows:
***relocked***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.27.0000
eMMC-boot
Jan 13 2012,17:33:34
my cid is HTC__Y13 and my version-main is 3.33.401.53
using this info I can only find this RUU: RUU_PYRAMID_ICS_HTC_Europe_3.33.401.53_Radio_11.76A.3504.00U_11.24A.3504.31_M
I dont know if this is correct, I dont see anything resembling my cid in there.
note: bootloader is relocked using
Code:
fastboot oem lock
as the http://forum.xda-developers.com/showthread.php?t=1672425 guide says. Following that guide now but is confused on the RUU to get. Gonna try with the RUU I have downloaded now and I'll let you know how it goes...
Sverrebob said:
my bootloader reads as follows:
***relocked***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.27.0000
eMMC-boot
Jan 13 2012,17:33:34
my cid is HTC__Y13 and my version-main is 3.33.401.53
using this info I can only find this RUU: RUU_PYRAMID_ICS_HTC_Europe_3.33.401.53_Radio_11.76A.3504.00U_11.24A.3504.31_M
I dont know if this is correct, I dont see anything resembling my cid in there.
note: bootloader is relocked using
Code:
fastboot oem lock
as the http://forum.xda-developers.com/showthread.php?t=1672425 guide says. Following that guide now but is confused on the RUU to get. Gonna try with the RUU I have downloaded now and I'll let you know how it goes...
Click to expand...
Click to collapse
Ok I completed the exe RUU file and it told me it was completed, STILL I only get green HTC logo and bootloop. Entering bootloader the pgone tells me the battery voltage is too low, will this prevent the phone from booting normally?
I have it on FASTBOOT AC now and hope it will charge, then I'll try to restart the phone and see if I can boot it.
Sverrebob said:
Ok I completed the exe RUU file and it told me it was completed, STILL I only get green HTC logo and bootloop. Entering bootloader the pgone tells me the battery voltage is too low, will this prevent the phone from booting normally?
I have it on FASTBOOT AC now and hope it will charge, then I'll try to restart the phone and see if I can boot it.
Click to expand...
Click to collapse
after charge use the command to reboot from bootloader if it fails normally
fastboot reboot
rzr86 said:
after charge use the command to reboot from bootloader if it fails normally
fastboot reboot
Click to expand...
Click to collapse
Tried that several times already, same thing happens, white screen with green HTC , goes into the usual bootloop.
Recovery from bootloader menu also end up the same way as above.
Factory reset aswell.
Also, every time I get into bootloader it does this check you can see on this screenshot here
{
"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"
}
Any inputs on this, or is this normal when the SD card is empty?
During the white bootloop screen with green HTC the SD card does get recogniced by my PC and shows up in explorer briefly before phone reboots again, so it cant be the SD card reader can it?
I consider myself pretty much advanced when it comes to techology and I have been reading up on all this stuff around phones and what you can do with them. I feel I have gotten a pretty basic understanding so far, and from my point I really does not see why my phone wont behave normal.
It kinda cooks down to some hardware fail, atleast in my opinion? I'm really at my wits end here
Sverrebob said:
Tried that several times already, same thing happens, white screen with green HTC , goes into the usual bootloop.
Recovery from bootloader menu also end up the same way as above.
Factory reset aswell.
Also, every time I get into bootloader it does this check you can see on this screenshot here
Any inputs on this, or is this normal when the SD card is empty?
During the white bootloop screen with green HTC the SD card does get recogniced by my PC and shows up in explorer briefly before phone reboots again, so it cant be the SD card reader can it?
I consider myself pretty much advanced when it comes to techology and I have been reading up on all this stuff around phones and what you can do with them. I feel I have gotten a pretty basic understanding so far, and from my point I really does not see why my phone wont behave normal.
It kinda cooks down to some hardware fail, at least in my opinion? I'm really at my wits end here
Click to expand...
Click to collapse
Hi, gonna try help out
firstly, your screen shot. that will always happen when you boot into the bootloader with an sd card in the phone. doesnt matter whats on it, it will always check it for those files if it detects it. its not an issue
Second, when you try to boot into recovery, does it ever make it? or does it always sit at the splash screen. ( the white background with the green htc letters.)
thirdly, if you are willing to unlock your bootloader again can you place the attached recovery.img and place it into your adb/fastboot folder, and then when in fastboot usb issue the command fastboot boot recovery.img , hopefully it will boot into 4ext recovery temporarily, and allow you to try get some system information. (assuming your new touch screen works ) you may get some warnings if/when 4ext boots up. make a note of all of them and reply to here please
heavy_metal_man said:
Hi, gonna try help out
firstly, your screen shot. that will always happen when you boot into the bootloader with an sd card in the phone. doesnt matter whats on it, it will always check it for those files if it detects it. its not an issue
Second, when you try to boot into recovery, does it ever make it? or does it always sit at the splash screen. ( the white background with the green htc letters.)
thirdly, if you are willing to unlock your bootloader again can you place the attached recovery.img and place it into your adb/fastboot folder, and then when in fastboot usb issue the command fastboot boot recovery.img , hopefully it will boot into 4ext recovery temporarily, and allow you to try get some system information. (assuming your new touch screen works ) you may get some warnings if/when 4ext boots up. make a note of all of them and reply to here please
Click to expand...
Click to collapse
I appreciate the reply
It have never gotten into recovery, it always stuck at the "splash screen" and have done so with both 4EXT and CWM.
thirdly: I unlocked the bootloader and put your attached recovery.img into the fastboot folder, ran the command with phone in "fastboot usb" and ended up on splash screen as always, it stays there for a few seconds then it goes black. It seems like the phone is rebooting but the screen remains black. I do, however, get the well-known sound of an usb device beeing attached and removed again, with a few seconds silence in between. Screen remains black. To solve this mysterious "bootloop" I remove the USB cable, gives it half a minute and do the vol-down pwr button method and then I am back in the bootloader again.
Just for fun I have tried the recovery menu in bootloader with the phone not connected to usb, same splash screen here. It just seems that my phone really dont want the recovery to work :/
extra info: figured out that the screen went black after one splash screen due to me pressing vol-down. It apparently does 3 reboots showing splash screen, then a couple mysterious black screen reboots and then another splash screen reboot three times... I have stopped this weird cycle now to save my poor battery, but it seems that it would just have continiued this behavior of 3 splash screen reboots - 2 black - 3 splash and so on...
weird!
ALSO; this is the response from fastboot command I get when trying to boot the recovery from there:
Code:
C:\android>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.493s]
booting...
OKAY [ 0.002s]
finished. total time: 1.495s
Sverrebob said:
extra info: figured out that the screen went black after one splash screen due to me pressing vol-down. It apparently does 3 reboots showing splash screen, then a couple mysterious black screen reboots and then another splash screen reboot three times... I have stopped this weird cycle now to save my poor battery, but it seems that it would just have continiued this behavior of 3 splash screen reboots - 2 black - 3 splash and so on...
weird!
ALSO; this is the response from fastboot command I get when trying to boot the recovery from there:
Code:
C:\android>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.493s]
booting...
OKAY [ 0.002s]
finished. total time: 1.495s
Click to expand...
Click to collapse
did you try to boot into safe mode?
once you will see the splash screen hold volume down until it gets you to the safe mode
see if it works
rzr86 said:
did you try to boot into safe mode?
once you will see the splash screen hold volume down until it gets you to the safe mode
see if it works
Click to expand...
Click to collapse
Thank you for the tip, unfortunately it didnt seem to work
I pressed volume down as soon as the splash screen appeared after I executed the <fastboot boot recovery.img> and it just hang there for a few seconds then the phone rebooted and I ended up in the bootloader again.
Hmmm. This is very strange indeed. My theory is that your internal partitioning may be messed up, so when the phone tries to boot things are not in the right place. But that doesn't explain why it won't fastboot boot, as fastboot boot should boot the .IMG into the ram and not attempt to flash it. It may well be down to a hardware fault. If your ruu ran without any errors then it should have fixed any partition errors. You could try extracting the boot.IMG from the ruu and use the fastboot boot boot.IMG command and see if that gets you any farther.
Also when your phone goes into the black after the splash screen, can you keep it connected to the PC and issue the command adb devices for me just a hunch I have
Sent from my Nexus 7 using Tapatalk 4
heavy_metal_man said:
Hmmm. This is very strange indeed. My theory is that your internal partitioning may be messed up, so when the phone tries to boot things are not in the right place. But that doesn't explain why it won't fastboot boot, as fastboot boot should boot the .IMG into the ram and not attempt to flash it. It may well be down to a hardware fault. If your ruu ran without any errors then it should have fixed any partition errors. You could try extracting the boot.IMG from the ruu and use the fastboot boot boot.IMG command and see if that gets you any farther.
Also when your phone goes into the black after the splash screen, can you keep it connected to the PC and issue the command adb devices for me just a hunch I have
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
So get this, tried to <fastboot boot recovery.img> again in order to obtain this black screen and do your <adb devices> and nothing! It's like the phone heard you and decided to "behave".....
It did 10 perfectly normal reboots with the splash screen every time, and the 4th and 5th time it even vibrated once...!
This whole charade is almost a little funny to me now, but clown phone or not, I'm not giving it up yet
I managed to google how-to extract the boot.img file from the RUU exe, it was a rather tidious operation
I found a very well explained guide on it here; https://sites.google.com/site/androidbyyorzua/home/tutorials/extracting-rom-files-from-htc-ruu
And not suprisingly all I got out of it was a error msg
Code:
C:\android>fastboot boot boot.img
creating boot image...
creating boot image - 3868672 bytes
downloading 'boot.img'...
OKAY [ 0.984s]
booting...
FAILED (remote: reproduce boot image with on-flash ramdisk error)
finished. total time: 0.999s
Something wrong with my phones RAM maybe?
EDIT: I tried the fastboot command to flash the rom.zip and this is how it went.
Code:
C:\android>fastboot flash zip rom.zip
sending 'zip' (436283 KB)...
OKAY [ 57.499s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
FAILED (remote: not allowed)
finished. total time: 57.819s
Tried it again with bootloader RELOCKED and it took alot more time and was slightly different, but still same error msg
Code:
C:\android>fastboot flash zip rom.zip
sending 'zip' (436283 KB)...
OKAY [ 57.685s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAILED (remote: not allowed)
finished. total time: 134.679s
Just as a quick intro, hello everyone. I'm new to the forum, but I've been reading from this site for a couple years now. Now that that's out of the way...to the real question.
So, my DNA committed suicide the other day and I received an HTC One M7 from a friend of mine who switched to apple. Yeah...he's stupid. But it's my gain. ANYHOW! It's a sprint HTC One m7 with the 1.57 hboot. I've come across an issue with trying to break this system open. Unlock went great along with TWRP recovery flash and superSU. No issues with any of that. HOWEVER! Somewhere down the line I believe my baseband and IMEI has been lost internally. I only come to this conclusion through research and finding a somewhat similar situation.
Currently, this is what's happening. I can enter bootloader and recovery just fine. The phone boots up just fine. But, once the phone is booted and I unlock the screen, all I get is a white screen with an HTC logo. Touch works, vibration works, it registers everything I do including the pull down (just to display header. it never actually pulls down), usb debugging icon, sounds, screenshot, PC recognizes device and everything. But it stays like this for about a minute or two and then restarts. It does this over and over.
I've been trying to s-off using rumrunner just to see if by chance it'd have success, but the phone won't recognize ADB. It will recognize fastboot commands perfectly, but not ADB. And yes...I use ADB commands in recovery I've tried every driver I could think of and every version of recovery and adb.exe I could find compatible. Because the computer won't recognize the phone in ADB, I can't get anywhere in rumrunner and because I can't access the main screen after unlocking the screen, I can't even use sunshine.
I'm at a total loss and I don't have any money for another phone. I really need some advice to get this fixed so I can flash a baseband and/or RUU and get this thing working with ViperONE. Please halp!
- Charles
You need to flash a stock ruu with fastboot and the imei will restore .
To see if the imei is still in the partition but the software doesn´t recognize it go in fastboot mode and type fastboot getvar all and the imei should be there.
Hello, I'm about to giving up,
Something happened to the phone and now it won't boot, it barely show the "ANDROID" logo when it restart itself. I can enter to the recovery menu, it doesn't have clockwork recovery nor twrp, just the basic recovery. So far I tried:
wipe data/factory - didn't work.
wipe cache partition - didn't work
apply update from adb: Adb just work with sideload and that's it, for everything else it shows closed. I tried sending the rom with sideload and it fails every time:
* failed to write data 'protocol fault (couldn't read status): Invalid argument' *
So I took my sdcard and copied the room there, so I tried
apply update from sdcard, it starts and in no time it says:
Installation aborted (APPLY_EXT).
I'm very frustrated right now, nothing works, it seems that the manufacturer did great effort on being the only one who can recover this phone, who appears to be from China, the MTK6582.
Fastboot? it doesn't show the device, it would be my last hope but no, since there is no adb, I cannot call fastboot, and the apply update from adb only work with sideload (yeah, f**k me).
The best course of action would be to throw it to the trash?
Thanks!
Hey, I'm in a similar position to you. However, I went about it with a slightly different route. The chip used in this phone is the MediaTek 6582 (I think?). I downloaded some tools from a thread on here that includes the 320 rom and the necessary software for flashing. I've flashed MediaTek devices before, the Huawei Ascend G610 and G700, both successfully. This one is giving me headaches, the damn device keeps disconnecting. HOWEVER, if you're lucky and you don't have the same problem with disconnecting hardware, you should be able to flash a new rom via the software. It'll take a while though. Also, I don't know what'll happen to your IMEI afterwards, so that's another possible headache (both the G610 and the G700 lost their IMEI info, but I'd taken steps to back them up beforehand so I could just restore them; here, there's no option to backup).
Here's the thread: http://forum.xda-developers.com/android/general/htc-mtk-cpu-flash-files-flashtool-t3114271
Let me know if you need help. I'm screwed in that the damn phone keeps disconnecting. Similar to you, no fastboot either. Plus, no RUU for this HTC. Hell, the internet barely knows this flipping phone.
Cheers, and good luck.
blitz9826
0Camus0 said:
Hello, I'm about to giving up,
Something happened to the phone and now it won't boot, it barely show the "ANDROID" logo when it restart itself. I can enter to the recovery menu, it doesn't have clockwork recovery nor twrp, just the basic recovery. So far I tried:
wipe data/factory - didn't work.
wipe cache partition - didn't work
apply update from adb: Adb just work with sideload and that's it, for everything else it shows closed. I tried sending the rom with sideload and it fails every time:
* failed to write data 'protocol fault (couldn't read status): Invalid argument' *
So I took my sdcard and copied the room there, so I tried
apply update from sdcard, it starts and in no time it says:
Installation aborted (APPLY_EXT).
I'm very frustrated right now, nothing works, it seems that the manufacturer did great effort on being the only one who can recover this phone, who appears to be from China, the MTK6582.
Fastboot? it doesn't show the device, it would be my last hope but no, since there is no adb, I cannot call fastboot, and the apply update from adb only work with sideload (yeah, f**k me).
The best course of action would be to throw it to the trash?
Thanks!
Click to expand...
Click to collapse
Ditto!!!
Hey guys I am having the exact same issue, luckily for me it is my Mrs who done her phone in and not mine . She has the HTC Desire 320, I believe she tried to root it on her own without even asking for advice, I think she used the app Kingo Root, she said she went to remove the root but when she uninstalled the app it didn't remove it. (LOL I told her well perhaps that's because there will be some way of removing it, aside from just uninstalling the app), anyway she proceeded not to care and carried on using her phone as normal for maybe a week or two at most, then about midnight one night, came down and said to me,
"my phone had an update and on restarting I just get a dead android, if you press the power button you get some options so I clicked erase"
Click to expand...
Click to collapse
I was like nice so basically you F***ed it!!!!, and for about 2 weeks now I have been endlessly reading post after post, forum after forum, trying rom after rom, RUU, all kinds of things.
Here is the situation, the phone will boot as far as the HTC logo, it will get stuck in a short loop and reset itself 4/5 times repeating the HTC logo, eventually it will end up at the dead android pic (the android on his back with the red exclaimation mark triangle) with the words 'no command'. From here I can press the power button once to get a list/menu of items (What I assume to be the recovery menu). I can backup data, I can restore the backed up data (both of which do nothing as I guess there is nothing really to back up), There is an option to restore from sd card (which I have tried numerous roms and to no avail have any been successful), I can erase the cache and I can also erase everything and recover, the erase side works fine, I did notice in each of these menu that if you press volume up to activate them and then press the power button once, then the writing dissapears and the android proceeds to have his moving atom type thing in his belly, saying 'erasing..', however even with them completed successfully, it still does not restore.
NOTE!!! If you choose the erase and restore method, once activated with volume up, press the power button to get the spinning atom and erasing... message, when this finishes the phone will reboot, it goes to the htc logo, resets itself, goes to the logo again and then just stays at a black screen (almost like a frozen state, I left it for quite some time and it never changed).
I should also note, which I didn't to begin with, but no matter how long I hold the volume down and power button, there is no such hboot/fast boot menu at all, if you hold the volume down and power button even after it displays the htc logo, the phone just proceeds to endlessly reset and loop through the same process forever.
The only thing I can seem to access with little success, is the ADB CMD prompt through the Android SDK,
Code:
adb devices
will indeed return the device (a set of numbers with the word sideload beside it)
Code:
adb usb
Apart from the odd fluke, this has seemed to fail everytime with either an error about a protocol or an error stating 'closed'
Code:
adb sideload "ROM_FILENAME.ZIP OR .IMG
Occasionally this will throw the protocol error, but generally succeeds and displays the 100% most of the time, however the phone doesn't even try, it just almost instantaniously returns the error message :
Code:
[B][I]Installation Aborted (APPLY_ADB_SIDELOAD)[/I][/B]
NOTE!!! That the android lays on his back with this error, but it only says error below not no command.
I am pretty sure that I already came across a solution very similar to the one you posted above, and I just couldn't get it to recognise the phone, the only way the RUU would work, was by completely removing the battery and plugging in the usb, however without the battery in the phone, it just constantly beeps via usb, so I guess it turns on, then off, then on, then off, forever!!! So the RUU fails everytime, if I leave the battery in and try, the RUU program does nothing whatsoever! So I am at a complete loss with it now.
Cheers
GunnerJnr
Any luck with unbriking the HTC?
Maybe this is the solution, good luck.
Search: How to Unbrick every MTK China Phone ! Preloader / SP Flashtool Fix [HD] on Youtube
Responds please.
http://forum.xda-developers.com/showpost.php?p=64659997&postcount=16
I think that you no tell true because I tried this method with volume keys and nothing. Flash tool still show error. Its impossible to write android without battery. I think really put your phone to rubbish or sell as lcd+digitizer parts I think just we must waiting for new custom rom flashable via stock recovery. 320 is still new model and developers no moke any custom rom. So maybe only HTC service may help, only in HTC Factory peoples know how install android and bootloader on hard bricked device.
Hi everyone. Thanks for your attention
I have a HTC Mini. Today I wasn't able to connect my phone into the wifi. Then, I restarted and afterwards the phone didn't boot at all. It goes only to the bootloader menu. Last two days I was looking for the solution. In the HBOOT menu when I tried to the factory reset it only jumps into the fastboot menu, same thing for the recovery. When I am in the fastboot menu, if I click on reboot, or reboot bootloader it just reboot and the HBOOT menu comes again.
However, my HBOOT menu is locked and when I wanted to try unlock it. following problem happen :
- when I connect the phone to a Mac, Fastboot Devices detect (but only fastboot, ADB devices return nothing) the phone and I could get the token for unlocking procedure, but when I load the the unlock token which sent to me by mail from HTCDEV, nothing happen. it just say everything was successful on Terminal, but nothing shows up on the phone to Confirm unlocking procedure and sometimes it hangs and if I try pushing the token again (the bin file), I receive an error, fail to splash the screen (something like this). However, I already installed the HTC Sync Manager and every other possible driver I could find on the internet.
When I use windows, after installing HTC Sync and all of the drivers several time, still the command for Fastboot devices or ADB Devices return nothing. I don't care about the phone data or anything. I just want to like Flash the whole operating system and everything . thats fine. But nothing is working properly.
Please guide me if you have any idea about this problem.:crying::crying:
It happened to me too. Same sh1t. Camera didn't worked so i decided to restart the phone...from that time same story like yours.
same here, but i have an idea
when i do fastboot getvar all my baseband says N/A indicating corrupt or missing radio rom
the correct radio should be Radio_1.29.40g on mine based on the RUU i have on hand (used before)
RUU attempts to get into different mode and fails
i have been unable to extract the files from the RUU