Related
Yesterday my phone's battery died from not charging it and I didn't think too much of it. I plugged it back in to charge however and it automatically booted up...into the boot loader with a message saying "No Image File!" (figured out this was because its checking the microsd card for a rom - I usually flash over usb). Tried to flash another ROM and it appeared to be working but after the reboot (before you get to the stylus configuration screen) just went back to the bootloader and gave the same message.
So, has anyone encountered this before? Looks like the ROM isn't storing anything (and my phone is essentially dead) but perhaps I need to do something simple to fix it.
Thanks in advance!
It's been posted a few times, but it's rare. Try flashing a stock rom over usb.
Hey, appreciate the help!
Tried it and no dice however. Looks like the message I was recieving (No Imaging File!) was from it looking for an Image off the SD card (I always flash off of USB so I had never seen this). Tried to initiate a hard reset from the boot loader as well but it just gets stuck on the "This operation will delete all your..." screen and pressing Volume Up does nothing.
So I tried to flash the ROM found at http://forum.xda-developers.com/showthread.php?t=429843 and am still stuck where it reboots back to the boot loader after the flash.
Maybe try flashing with the sd card removed; you could also try task 29. Sorry, I have no other ideas.
Edit: And I know I've posted this in similar threads (lol), but maybe your vol down button is stuck. If that's the case, any time you reset the device, it will go into bootloader. I can't think of any other reasons you phone isn't booting up properly (other than, like, the phone is toast).
Hey, yea last night attempted to flash without it in as well as from the SD card. Neither worked.
So I kept searching and was reading all about mtty (and task 29) and that looks like the way to go. Couldn't get things to work properly on my Windows Server 2008 R2 box so I'm going to try it from an XP box here in a bit and can hopefully get everything connected.
If anyone is curious, I found this thread describing the use of mtty: http://forum.xda-developers.com/showthread.php?t=540290
Well, took it to work where I have an XP machine and plugged it into the USB port. It didn't turn on automatically (which it has been when supplied with power) which was kind of weird. So I hit power and voila, it loads the ATT ROM I flashed last night.
Not sure what fixed it (I don't think it was a stuck key, but who knows) but its working now. Thanks for your help Ted.
Yesterday my phone started acting up. All running process crashed and not many was able to start. I had to constantly click "force close". I think this started after I installed the Google+ app, but not sure.
I have tried uninstalling all unnecessary apps, without luck. I then tried wiping to factory settings by using the Android menu, but without any changing. I then tried by holding vol+ and power, going in to recovery and wiping both to factory and app cache. This doesn't change anything either. By googling I can see some suggests to hold vol- and power, to get to a another wiping-functionality but this just boots my Nexus S to normal state - no menu appears.
Has anybody an idea of what I can do?
Edit: more info; if I click "Report" and investigate the message sent to Google, I see that error has something to do with SQLite-relatet classes. Which makes some sense, alot of my changes are reset each time the phone is rebooted. For instance did I miss a call a couple of hours before the phone went crazy - this is shown at each boot in the notification area eventhough I clear the area and/or goes to missed call section
Factory reset via menu does delete all your "custom" apps, so I'd say it's not one of the existing apps causing problems.
The way you describe function after your factory reset sounds like factory reset didn't work properly.
If you feel safe I'd recommend rather flashing 2.3.4 again using either Odin or the OTA zip from Google (requires open bootloader).
I think you're right that factory reset doesn't do what is expected. Once I click it, the phone reboots and shows the Android guy next to an unwrapping package. This lasts only 2 seconds, then it reboots itself again and goes into normal phone mode (where all the app-crashing starts again).
I have not flashed or rooted my phone before, but I will consider this now since my NS is pretty much a brick. Thank you for your swiftly response.
Edit: Shouldn't I get a menu, when I push and hold vol- button, while turning on the device? Right now it just boot as normal.
Before you use odin....try going into rom manager a reflashing clockwork! Ive had that android dude on my screeen but reflashibg via rom manager always fixed it. Try that
Sent from my Nexus S using XDA Premium App
Wow my Nexus has totally shut me out.
I cannot use ClockworkMod unfortunately since I am not able to root my phone. It is not detectable via USA (when I use vol+/pwr and connect USB). I am unable to check the USB Debugging option on the phone. Each time I check it, go to home-screen and back to the menu, it has de-selected it again. Also I noticed when I read the info that is sent to Google for all those app-crashes I get, I see SQLiteException and error in an SQLite.java file. So it seems like some database layer is broken.
I read one could copy the ClockWork.img to my phone and use the standard recovery option to flash the img (I think). But when I go into the recovery menu, the file is gone. When I boot the phone again, it has deleted the .img file - eventhough if I copy it to several different folders, they are all gone :-(.
I feel pretty screwed at the moment. How can I else wipe all data?
I'd recommend to check if your device is correctly identified in windows. Missing USB drivers might cause problems. Get the latest drivers and a guide from here.
If you succeed booting into fastboot properly (vol up and power) you can follow this guide. Get the latest cwm recovery.img here.
Last option would be to boot into download mode (vol up + vol down + power + plugging in usb cable) and use Odin from samfirmware.com
--
All options require correctly working USB drivers.
I managed to unlock the bootloader, by quickly turning on USB-debugging (before any processes started to crash) and install the drivers from this post:
http://forum.xda-developers.com/showpost.php?p=6819751&postcount=4
A reboot later, I got this message:
"System UIDs Inconsistent
UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable."
Right below was a button saying "Im feeling lucky" (??)
I installed ClockworkMod using fastboot and tried "Fixing permissions" with no luck. I will try some ROM later on, and hope it will bring my phone back
Normally this error happens when you have a faulty app ruining your system, formating/deleting whole sdcard does usually fix this.
rentaric said:
Normally this error happens when you have a faulty app ruining your system, formating/deleting whole sdcard does usually fix this.
Click to expand...
Click to collapse
I can safely mount USB-storage and format the whole bunch?
I been sweating over this stupid issue all day now, all I want is a fac-reset :´(
Edit: "format /sdcard" using CWM didn't do anything
DennisRP said:
I can safely mount USB-storage and format the whole bunch?
I been sweating over this stupid issue all day now, all I want is a fac-reset :´(
Edit: "format /sdcard" using CWM didn't do anything
Click to expand...
Click to collapse
See I'm no expert on this whole thing. At this point I'd just flash a whole new system via Odin. Prolly not the smartest or safest option, but that's what I'd do because I don't know better. If that wouldn't fix it either, I'd return the phone on warranty
I was looking at Odin from the start, since nothing else seemed to be working.
So right now I got started on Odin. Followed the .pdf steps and flashed the bootloader at first succesfully. I was asked to remove the battery and re-connect my NS. Began downloading "pda" and "phone", but at around 10% a big fat red "fail" message appeared and now I just see the Google-logo on startup. I still cant flash any roms via fastboot.
Im too tired too right now, been working with this for 14 hours straight. I will look at it tomorrow evening. Thanks for your help rentaric
Weird, you're not the first one who had trouble running Odin using their guide.
Overall it's pretty simple.
Enter download mode. Vol up vol down and power at the same time while plugging in the USB cable. Start Odin, should show a yellow colored box with a port number. Uncheck everything but reset timer and auto reboot. Unzip the correct zip file from samfirmware.com (check if you got i9020 or i9023 and get the universal Odin exe), apply file from the folder accordingly. Bootloader and bootloader. Phone and modem. Pda and pda. Csc can remain empty (will change carrier info in fastboot).
Double check md5 hash to avoid broken files.
Sent from my Nexus S using XDA App
rentaric said:
Weird, you're not the first one who had trouble running Odin using their guide.
Click to expand...
Click to collapse
Of course I did not go to bed, how should I be able to sleep with a broken phone .
The firmware suggested on samfirmware.com for my phone, was 2.3.3 and some other version (my phone was 2.3.4.2/GRJ22 or something similar, I suspect that might be the cause. Also I unchecked everything, that might also have been of importance). The flash will always fail when everything was downloaded - it then said something about "remote" and "Loke" and then fail. But as I mentioned, I had succesfully flashed boot.img (2.3.3) thus no boot occured now. I googled the correct bootloader, used fastboot and was booting succesfully again.
I began looking more into the sdcard, as error-messages was leading me this way. To compress 4 hours of investigations into a few lines, it seems as my PBA is malfunctioning as other xda-members have experinced. Only solution is sending the phone to Samsung for a PBA replacement. I purchased the phone in Bestbuy USA and the danish Samsung partners are not too joyfull about this - I will contact Samsung and hope they can help me.
I experinced the exact same thing as this poor guy - http://forum.xda-developers.com/showthread.php?t=993403
Every thing you try to do to /sdcard is worthless.
Formatting (USB/using CWM/using adb shell linux commands) says "Succes" but nothing happens.
Copying files says "Succes" but nothing happens. If I boot phone into CWM, mount usb and upload new rom/apk/whatever and try to do a "install update.zip" it fails with some mounting errors.
Im ready to go cry in a corner - I really want this to be fixable via software, but I probably have to realize that this is a hardware issue.
Apparently Samsung doesn't offer worldwide warranty for cellularphones :´(. God it sucks to pay repair-expenses on a 1 month old mobile.
I've been all over the forums and threads trying to find ways to fix this s3. Failed at every turn, so here it is. This s3 has had CM on it forever, like over a year now. I haven't explicitly tried to perform any updates. I woke up one morning at it was stuck on the splash screen with the little blue CM guy with a static white circle on his chest, but that's as far as it'll get.
I can get into ClockworkMod Recovery (6.0.3.1), but can't mount the sdcard to get at backups, or do much else for that matter.
I can get into Odin Mode, but every singe thing I have tried to flash fails - and I think I've tried them all. I've tried the usual steps, update drivers, switch cables, switch usb ports, etc. to no avail.
I can get to an adb shell in recovery, is there a way to flash a stock image from there?
Since it's in this weird soft-brick state, the hard brick solution of putting a boot img on the external sdcard don't seem to work.
mjunior25 said:
I've been all over the forums and threads trying to find ways to fix this s3. Failed at every turn, so here it is. This s3 has had CM on it forever, like over a year now. I haven't explicitly tried to perform any updates. I woke up one morning at it was stuck on the splash screen with the little blue CM guy with a static white circle on his chest, but that's as far as it'll get.
I can get into ClockworkMod Recovery (6.0.3.1), but can't mount the sdcard to get at backups, or do much else for that matter.
I can get into Odin Mode, but every singe thing I have tried to flash fails - and I think I've tried them all. I've tried the usual steps, update drivers, switch cables, switch usb ports, etc. to no avail.
I can get to an adb shell in recovery, is there a way to flash a stock image from there?
Since it's in this weird soft-brick state, the hard brick solution of putting a boot img on the external sdcard don't seem to work.
Click to expand...
Click to collapse
Before ditching the phone, I'd suggest trying a JTAG service. You can find them on eBay for $30-50. Saved my S3 from a hardbrick from flashing the wrong firmware (Sprint version on Verizon S3).
mjunior25 said:
I've been all over the forums and threads trying to find ways to fix this s3. Failed at every turn, so here it is. This s3 has had CM on it forever, like over a year now. I haven't explicitly tried to perform any updates. I woke up one morning at it was stuck on the splash screen with the little blue CM guy with a static white circle on his chest, but that's as far as it'll get.
I can get into ClockworkMod Recovery (6.0.3.1), but can't mount the sdcard to get at backups, or do much else for that matter.
I can get into Odin Mode, but every singe thing I have tried to flash fails - and I think I've tried them all. I've tried the usual steps, update drivers, switch cables, switch usb ports, etc. to no avail.
I can get to an adb shell in recovery, is there a way to flash a stock image from there?
Since it's in this weird soft-brick state, the hard brick solution of putting a boot img on the external sdcard don't seem to work.
Click to expand...
Click to collapse
Try flashing the latest TWRP ODIN image. http://techerrata.com/file/twrp2/d2vzw/openrecovery-twrp-2.7.0.0-d2vzw.tar
If that is able to flash, then use the Format Data/Cache option under wipe and see if that works. If not, you may need to use a pit file with a ODIN image to completely reformat the device, and reflash it.
ddggttff3 said:
Try flashing the latest TWRP ODIN image.
If that is able to flash, then use the Format Data/Cache option under wipe and see if that works. If not, you may need to use a pit file with a ODIN image to completely reformat the device, and reflash it.
Click to expand...
Click to collapse
Great suggestions, thank you.
I had tried both already, but your menion of TWRP reminded me that it was the closest I got to signs of life so I tried it again. Odin acts like it flashed successfully, even reset the device, but the device never actually took the image.
I didn't know much about pit files until the other day, and tried that also. I did try again and the format seems to work with the pit but any attempt to flash something subsequently results in the same failures.
Thanks for responding.
mjunior25 said:
Great suggestions, thank you.
I had tried both already, but your menion of TWRP reminded me that it was the closest I got to signs of life so I tried it again. Odin acts like it flashed successfully, even reset the device, but the device never actually took the image.
I didn't know much about pit files until the other day, and tried that also. I did try again and the format seems to work with the pit but any attempt to flash something subsequently results in the same failures.
Thanks for responding.
Click to expand...
Click to collapse
Remember too after you flash the odin file, you will most likely have to boot into stock recovery and do a factory reset, otherwise it won't boot, but will bootloop marvelously.
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 all! I have exhausted every avenue I can think of, with now hitting a roadblock attempting to repartition the device.
I took this phone to get its physical structure repaired as well as the screen. It took them 6 hours. When I got the phone back they said the "software crashed" and that they attempted firmware flashes to no avail.
The phone is in a constant Boot Loop. It will sit on the Samsung splash screen for a minute, go to a blue screen which tells me it is installing a system update, then an Android figure comes up saying Error. It does this over and over again. I hit the power and volume up key to quickly look at the commands it was throwing out and saw it was unable to access certain directories which I assume is the reason for the failure.
So I reflashed this phone with my relevant firmware using Odin. No firmware or combination of files and methods has brought this phone back.
I was hoping for some help with this project. I want to resurrect this phone, it's a great phone. I would love the satisfaction of doing it myself than at a store.
lexlex121 said:
Hi all! I have exhausted every avenue I can think of, with now hitting a roadblock attempting to repartition the device.
I took this phone to get its physical structure repaired as well as the screen. It took them 6 hours. When I got the phone back they said the "software crashed" and that they attempted firmware flashes to no avail.
The phone is in a constant Boot Loop. It will sit on the Samsung splash screen for a minute, go to a blue screen which tells me it is installing a system update, then an Android figure comes up saying Error. It does this over and over again. I hit the power and volume up key to quickly look at the commands it was throwing out and saw it was unable to access certain directories which I assume is the reason for the failure.
So I reflashed this phone with my relevant firmware using Odin. No firmware or combination of files and methods has brought this phone back.
I was hoping for some help with this project. I want to resurrect this phone, it's a great phone. I would love the satisfaction of doing it myself than at a store.
Click to expand...
Click to collapse
Sometimes after flashing via Odin, it is necessary to boot into stock recovery and factory reset then wipe cache partition then reboot. This doesn't always solve bootloop after flashing via Odin but it is a common solution.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Sometimes after flashing via Odin, it is necessary to boot into stock recovery and factory reset then wipe cache partition then reboot. This doesn't always solve bootloop after flashing via Odin but it is a common solution.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
I don't understand how to get into recovery mode. The phone, when the charger plugs in, attempts to boot all the time.
I know the Recovery mode key combo but I have no idea to power off this phone. I've let the battery run.