Related
[PROBLEM SOLVED]
Ive been flashing back and forth to different builds trying which is better. I made sure I took the cautions not to flash builds that would brick my phone. There were 4 times that I soft bricked my phone but I was able to revive it. However, my little game has come to an end with this last one. The fault was this guide: http://forum.xda-developers.com/showthread.php?t=817186.
Little did I know, by doing a repartition and not loading anything to the NAND resulted in the bootloader not being installed. (Devices like this should have a ROM programmed to recover from these errors, think Gigabyte) Upon reset, the phone went out and didn't turn back on. ODIN reports success. Now the phone cannot turn back on, no matter what battery pull method I use, I get nothing on the screen. So much for fail-safe protocols Samsung has implemented, if there are even any. Poorly engineered!
EDIT:Thanks for all your suggestions guys. So yes this phone was definitely bricked beyond any software repair. I was going to JTAG it but I figured there MUST to be some hardware bootloader implemented. I went ahead and did the USB JIG and surprise, it booted from the hardware bootloader. I used ODIN to flash JFD and it works now. So my guess is samsung did implement a fail safe, which is the USB trick and forces the phone to boot from hardware. If that is true, this phone is brick proof, provided that all electronics still work.
EDIT 2: I am wrong about the bootloader being hardware. Some say it is flashable, so it is possible you can get a real TRUE brick and must need JTAG to revive it. Fortunately for me, I was able to use the USB JIG method to get it back up and running. Too bad, a new phone would've been nice.
Not poorly engineered, just poorly made user input.
Yes true, but samsung should have taken into account accidents like this will happen then they dont have control over who administers their update. People have bricked their phones by doing the factory update. When I design systems like these, I always make sure there is a fail safe backup that the user cannot modify. I am sure samsung has one and maybe they just dont let us access it.
I sometimes encounter the same error message but I never repartition. Luckily, i never clicked on it in Odin.
But you have to realize that most of those bricks are because people modified their phones from factory (ie. Voodoo and OCLF). Odin, a program used by internal Samsung engineers, was never meant for the public and shouldn't be used unless you know how to use it.
I agree, there should be an absolute fail safe if worse comes to worse, but the point I am making here is Samsung isn't wrong in this case.
When you violate warranties and experiment you tacitly accept responsibility for your actions. To not do so is not an act of rebellious ire...it is an act of denial.
Manufacturers do not, nor can not prepare for all scenarios because the possible number of scenario's to cover are legion. I don't see it as realistic especially for them to prepare for brick scenario's created by using a leaked internal engineering tool that the community has figured out largely through trial and error either. OTA and Mini Kies bricks they are responsible for, for obvious reasons, and Samsung and T-Mobile have taken responsibility for these scenarios because they are ones of their making.
XDA is not a place where people file warranty complaints (though some do complain). It is a place where people experiment, hack, and customize smartphones. Though some manufacturers do a better job than others at getting out of our way here (Samsung hasn't done so bad here relative to say Motorola), I don't think any of them particularly "care" about such community efforts in any meaningful sense. And why should they?
By modifying our devices aren't we quite clearly saying we're taking matters into our own hands? You have to balance your strong desire to tinker with the reality of where responsibilities lie.
These phones are some of the most difficult Android phones to brick. Anecdotally and statistically shown to be. Not impossible of course, but quite difficult. I feel for your bad experience but at least consider shouldering some of the blame.
Thank god i am too scared to use odin. The deepest i go is clockwork recovery, but good luck with your paperweight.
Too bad the SGS is so light, it wouldnt make a good paperweight, or even a brick.
but seriously, the warranty is there to protect users which this happens to, assuming it wasnt voided by hacking the phone. Are you asking samsung to take into account that you would hack the phone and provide a way back after you have a bad hack and probably make themselves liable by providing that way back in case it does not work properly?
I want to be clear that I am not blaming samsung for this but I thought samsung could have done a better job. Ill admit, this phone was the first phone that impressed me in years and as an engineer, I am hardly ever impressed; other engineers will get my point. I wish they had some soft of fail safe mechanism. For us who like to tweak things, I get we get what we deserve. But what about those who dont like to tweak and still brick their phones? i.e. those who use Kies Mini and still brick. I still have warranty on the phone and I'll try to take it up with Tmobile, hope they don know much about flashing. BTW, I tried using the other program but no go. All the drivers were installed, rebooted computer...nothing. I think it is because I have W7 64 and not 32?
Have you tried the jig method of getting into dl mode?
engineer14 said:
Thank god i am too scared to use odin. The deepest i go is clockwork recovery, but good luck with your paperweight.
Too bad the SGS is so light, it wouldnt make a good paperweight, or even a brick.
but seriously, the warranty is there to protect users which this happens to, assuming it wasnt voided by hacking the phone. Are you asking samsung to take into account that you would hack the phone and provide a way back after you have a bad hack and probably make themselves liable by providing that way back in case it does not work properly?
Click to expand...
Click to collapse
Keep on flashing, and eventually Odin will probably save your butt
Don't be scared of it, it works great. And it is safe to use.
========================================
I'm really sorry about your phone man, I didn't know that you had to NAND before re-partition, thank god I've never checked that but I might have in the future had you not shared this with us, so thanks a lot!
I guess your loss is everyone elses gain
No I havent tried the Jig method. The thread says that I need to have at least the samsung screen, so some kind of activity. This phone is just off, nothing comes on, no buttons, no screen...just dead. I think when I followed that guide, it told be to repartition and then reboot with the "PDA" field empty. So the phone rebooted when it finished formatting without installing anything. Now the NAND is at a "blank" state and I do not have any bootloader on there. Anyone know of a method to install a bootloader without the phone turning on?
I might be a little too far out of my element here but I think I found a guide to remove the sdcard and format it via pc one time when I was in a similar situation. I am at work currently and I also cannot remember if I have the link saved.
Maybe some phone expert in your city may help you to install the bootlaoder. I think it's called jtagging, I'm not sure though.
Sent from my SGH-T959 using XDA App
trdexalbee said:
I want to be clear that I am not blaming samsung for this but I thought samsung could have done a better job. Ill admit, this phone was the first phone that impressed me in years and as an engineer, I am hardly ever impressed; other engineers will get my point. I wish they had some soft of fail safe mechanism. For us who like to tweak things, I get we get what we deserve. But what about those who dont like to tweak and still brick their phones? i.e. those who use Kies Mini and still brick. I still have warranty on the phone and I'll try to take it up with Tmobile, hope they don know much about flashing. BTW, I tried using the other program but no go. All the drivers were installed, rebooted computer...nothing. I think it is because I have W7 64 and not 32?
Click to expand...
Click to collapse
Just call Tmobile and tell then that you were upgrading to froyo 2.2 using Kies mini and it froze...
I had a black screen once. I was flashing in odin and knocked the cable loose. I think I had to remove the battery, open odin, plug the usb cable in, then install the battery and possibly hold a key down on the phone. I believe the download screen then came up. Otherwise the phone would not respond nor would any lights come on
trdexalbee said:
I want to be clear that I am not blaming samsung for this but I thought samsung could have done a better job. Ill admit, this phone was the first phone that impressed me in years and as an engineer, I am hardly ever impressed; other engineers will get my point. I wish they had some soft of fail safe mechanism. For us who like to tweak things, I get we get what we deserve. But what about those who dont like to tweak and still brick their phones? i.e. those who use Kies Mini and still brick. I still have warranty on the phone and I'll try to take it up with Tmobile, hope they don know much about flashing. BTW, I tried using the other program but no go. All the drivers were installed, rebooted computer...nothing. I think it is because I have W7 64 and not 32?
Click to expand...
Click to collapse
Depending on which drivers you installed (and there seem to be quite a few floating around) you might need to disable Driver Signature Checking in 64bit Windows OS's if the drivers are not signed. The easiest way I've found to do this is with EasyBCD . Install it, run it, click Advanced Options and enable loading of unsigned drivers. Do this before loading a potentially unsigned driver and you're good to go.
Just a tip, and my lengthy diatribe on responsibility was more to stem the potential tide of trolling such a thread is likely to generate than dump on you. I know what it's like to brick things. I've been bricking stuff for 30 years lol.
masterotaku said:
Depending on which drivers you installed (and there seem to be quite a few floating around) you might need to disable Driver Signature Checking in 64bit Windows OS's if the drivers are not signed. The easiest way I've found to do this is with EasyBCD . Install it, run it, click Advanced Options and enable loading of unsigned drivers. Do this before loading a potentially unsigned driver and you're good to go.
Just a tip, and my lengthy diatribe on responsibility was more to stem the potential tide of trolling such a thread is likely to generate than dump on you. I know what it's like to brick things. I've been bricking stuff for 30 years lol.
Click to expand...
Click to collapse
To disable driver signing, you ONLY need to run a single command and then reboot. And this applies to both Windows 7 and Vista.
Also to the OP.
You say you have no bootloader, but can't find ANYWHERE in this thread that says you were attempting to flash a bootloader. In fact, you can **** up partitioning, and your bootloader is still in tact. Been there, done that.
Do this. Plug the phone in, and leave it charging for about 30 minutes. Pull the phone off, hold the volume buttons, and plug the phone into a computer. See what happens. I had a ****ty situation end up happening to me, that I couldn't get the phone on for about 30 minutes. I had already even called T-Mobile for a replacement.
Thanks for all your suggestions guys. So yes this phone was definitely bricked beyond any software repair. I was going to JTAG it but I figured there MUST to be some hardware bootloader implemented. I went ahead and did the USB JIG and surprise, it booted from the hardware bootloader. I used ODIN to flash JFD and it works now. So my guess is samsung did implement a fail safe, which is the USB trick and forces the phone to boot from hardware. If that is true, this phone is brick proof, provided that all electronics still work.
trdexalbee said:
Thanks for all your suggestions guys. So yes this phone was definitely bricked beyond any software repair. I was going to JTAG it but I figured there MUST to be some hardware bootloader implemented. I went ahead and did the USB JIG and surprise, it booted from the hardware bootloader. I used ODIN to flash JFD and it works now. So my guess is samsung did implement a fail safe, which is the USB trick and forces the phone to boot from hardware. If that is true, this phone is brick proof, provided that all electronics still work.
Click to expand...
Click to collapse
This "hardware" bootloader as you are calling it, is the exact bootloader that you can flash and TRULY brick your device. It is NOT a failsafe in the way in which you are referring. Please, please don't call it this. There are plenty of users on this forum that are clueless. The jig method, is a hardware jump point that Samsung has built in to allow you to get to download mode situations where the button method does not work.
As I mentioned earlier, you didn't flash a bootloader. Nor did you full on brick your device. Glad your device is back to normal now though.
my apologies then, it would be easier if samsung gave us the schematics, but that would never happen. So when we use odin to flash, we are not flashing the bootloader as well? Is the bootloader located on another ROM that is not easily accessible? I guess ROM would be the incorrect term since you stated you can "flash" the bootloader.
Edit: Im stuck in bootloader with the only option to press power on is fastboot. and from there i cannot select any options because the navigation is broken. Im looking to restore it to factory so i can take it to the sprint store to have replaced. Please help me! Most likely an autorun from fastboot or a computer pushed through usb command promt that i can take over the phone. PLease HELP!
Have you tried the ruu? Its an executive file that you run from your computer and it restores your phone to stock. I've never had to run it so I cant tell you the exact details of how it works, but that could do the trick. I think there is a way also via using fastboot commands, but someone more intelligent then I will have to provide you with links. Also have you tried putting unrevoked forever s-on on your sd card and naming it PC36100.img then butting into hboot and letting it scan for that? Once it finds it, it should flash it on its own, then once youve done that, you can pull your sdcard again, delete that PC36100.img and put the PC36100.img that returns you to stock on your sdcard then boot into hboot again. It should find that image then flash you back to stock.
Ill try that. My down button is definatly either stuck, disconnected or something. When i press the up button and power it will Vibrate 5 times.
Ok i got the zip to load but my down and up buttons do nothing. is there a way i can have recovery auto run? or edit the hboot so that it automatically runs the recover.img?
Update: It's stuck in bootloader i guess... I restart and the volume down is stuck im pretty sure so it always goes to that. I have it hooked up to my computer, can i push commands through usb to it in bootloader menu...
Fastboot
...
....
Sim-lock
etc.
my only working option is to click power and have the fastboot initiate and then give me an option [1] ........ that i am unable to highlight or get to because of the stuck down button.
y0ungcitty said:
Ill try that. My down button is definatly either stuck, disconnected or something. When i press the up button and power it will Vibrate 5 times.
Ok i got the zip to load but my down and up buttons do nothing. is there a way i can have recovery auto run? or edit the hboot so that it automatically runs the recover.img?
Update: It's stuck in bootloader i guess... I restart and the volume down is stuck im pretty sure so it always goes to that. I have it hooked up to my computer, can i push commands through usb to it in bootloader menu...
Fastboot
...
....
Sim-lock
etc.
my only working option is to click power and have the fastboot initiate and then give me an option [1] ........ that i am unable to highlight or get to because of the stuck down button.
Click to expand...
Click to collapse
all you need is fastboot mode, from there you can run the RUU
xHausx said:
all you need is fastboot mode, from there you can run the RUU
Click to expand...
Click to collapse
What driver do i need for the device?
For some reason its not showing up as ready to do it.
The htc sync drivers
y0ungcitty said:
What driver do i need for the device?
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App
Both my volume keys are broken so I took my evo apart and used a thin metal to push the spring that controls the keys and load up a nandroid. Hope this helps.
alexisprz said:
Both my volume keys are broken so I took my evo apart and used a thin metal to push the spring that controls the keys and load up a nandroid. Hope this helps.
Click to expand...
Click to collapse
Load up nandroid?? im so out of the whole evo scene. can i have a link or procedure.... sorry for being a big noob.
If I can remember, running the stock ruu exe will do everything for you without any need for you to do anything with the phone to help it. Just make sure you have the htc sync program installed. Next make sure the phone is on and running (not in hboot or recovery). Plug the phone into the computer with the data cable. Make sure it's only in charge mode. Run the ruu exe. Be patient because it might take some time to start up. Make sure you have nothing running in the background on the pc. No antivirus or anything and I do mean anything. Don't touch or move the phone or cable while the ruu is running or you might risk bricking the phone if the connection between the phone and pc is interrupted. Don't let the computer go to sleep or standby. Make sure your phone's battery has a full charge. The ruu will make the phone reboot into upload mode. Then it will upload all the stuff the phone needs to be put back to factory. It might reboot the phone a few times. This is normal. You don't have to worry about the broken volume buttons interfering with ruu.
Lastly, make sure you remove your sd card before you get to the store to let the tech check it out. Don't offer any additional information. Just tell them the volume buttons stopped working and you did a full factory reset before you got there.
After running the ruu, don't sign into google account so your personal information won't be on the phone and none of the programs you bought will show up in the market. You should have a backup old phone with you so you or they can activate it for you in case they want to keep or swap it out. If they give you a refurb, power it up and test it at the counter to your satisfaction BEFORE you leave the counter and store. I noticed something wrong with the refurb they gave me and I'm glad I didn't walk away. The tech fixed the problem with the refurb (uneven backlighting on the screen). I was able to use my old screen with the refurb's guts and my screen didn't have any flaws in it.
You do what you want but this is my suggestion based on my experience with exchanging a defective phone. I have full insurance and or tep so it was a hassle free experience.
herbthehammer said:
If I can remember, running the stock ruu exe will do everything for you without any need for you to do anything with the phone to help it. Just make sure you have the htc sync program installed. Next make sure the phone is on and running (not in hboot or recovery). Plug the phone into the computer with the data cable. Make sure it's only in charge mode. Run the ruu exe. Be patient because it might take some time to start up. Make sure you have nothing running in the background on the pc. No antivirus or anything and I do mean anything. Don't touch or move the phone or cable while the ruu is running or you might risk bricking the phone if the connection between the phone and pc is interrupted. Don't let the computer go to sleep or standby. Make sure your phone's battery has a full charge. The ruu will make the phone reboot into upload mode. Then it will upload all the stuff the phone needs to be put back to factory. It might reboot the phone a few times. This is normal. You don't have to worry about the broken volume buttons interfering with ruu.
Lastly, make sure you remove your sd card before you get to the store to let the tech check it out. Don't offer any additional information. Just tell them the volume buttons stopped working and you did a full factory reset before you got there.
After running the ruu, don't sign into google account so your personal information won't be on the phone and none of the programs you bought will show up in the market. You should have a backup old phone with you so you or they can activate it for you in case they want to keep or swap it out. If they give you a refurb, power it up and test it at the counter to your satisfaction BEFORE you leave the counter and store. I noticed something wrong with the refurb they gave me and I'm glad I didn't walk away. The tech fixed the problem with the refurb (uneven backlighting on the screen). I was able to use my old screen with the refurb's guts and my screen didn't have any flaws in it.
You do what you want but this is my suggestion based on my experience with exchanging a defective phone. I have full insurance and or tep so it was a hassle free experience.
Click to expand...
Click to collapse
I already have a pre activated but i cannot get the phone to start without going into the Power+Down Menu... Can i run RUU from that? im not able to get it running on Android
I don't know. Something worse could happen but there's also a chance it might work. I am guessing ruu would tell it to reboot into upload mode. If the phone couldn't get into that mode the ruu might stop. This is just speculation. If you knew that the tech wouldn't bust you for having root, then I'd say to just take it in. It's a big risk in my opinion.
I don't know if there is a img file to fastboot flash a stock recovery. I don't know if that would help. Need to figure out a way to get the s-on and push stock back into it, or at the very least get s-on in hboot.
I'm thinking that because if the button is broke, and you can't get the phone past the hboot screen, then maybe the tech might not want to waste anymore time on it and just order a replacement. The hboot screen would be the only thing he could get into. I don't know but I think it could be helpful, maybe, if adb or something else could push an original rom into it at the screen it's stuck in. I think if you tried, if it wasn't working, the phone and adb wouldn't be communicating like normal and adb would not continue. I am guessing pushing a stock recovery wouldn't turn s-on. It would be great if it did.
I would say that talking with one of the devs that has got their hands dirty in hboot and fastboot, might give better advice. Perhaps they know of a way to force things into the phone that the general public wouldn't normally need to know or do. I am no expert. I suggest talking to people that developed in those areas. Didn't toast work with that?
I don't know what else to suggest. I'm running out of ideas.
I just had another idea. What if you could get a pc36img.zip, or whatever it's called, into root of the card and the phone will want to flash it. Only snag I can think of is I think hboot will ask if you want to flash or update or whatever it's called. That might be the down button. Maybe someone could run with that idea?
I would say read the rooting articles and see if you can adapt what they are saying to push stock everything back in instead of trying to root.
Even if you can't get the updated rom to install, if it can be pushed into the phone and the phone is made to boot like normal, the phone "should" try to apply it if anyone can get it to boot normally. I'm thinking that's another way to cover your ass.
If all else fails, then I would suggest to say a little prayer before going to the store and hope for a tech that isn't going to be a **** about it. Don't get an attitude towards the employees because that could make things much more difficult for you. A seasoned dev or a tech might be the only people that could help. Going into the irc channel for the evo and hanging around in there might get you hooked up with someone that could help more than the people that hang in the forums. I don't see serious devs hanging around the forum and bullshitting with the people there. Go where they might be, in irc. Be cool with them, don't be aggressive or flaky. If you are nice/cool with them, they might take the time away from what they are working on to help you.
herbthehammer said:
I just had another idea. What if you could get a pc36img.zip, or whatever it's called, into root of the card and the phone will want to flash it. Only snag I can think of is I think hboot will ask if you want to flash or update or whatever it's called. That might be the down button. Maybe someone could run with that idea?
I would say read the rooting articles and see if you can adapt what they are saying to push stock everything back in instead of trying to root.
Even if you can't get the updated rom to install, if it can be pushed into the phone and the phone is made to boot like normal, the phone "should" try to apply it if anyone can get it to boot normally. I'm thinking that's another way to cover your ass.
If all else fails, then I would suggest to say a little prayer before going to the store and hope for a tech that isn't going to be a **** about it. Don't get an attitude towards the employees because that could make things much more difficult for you. A seasoned dev or a tech might be the only people that could help. Going into the irc channel for the evo and hanging around in there might get you hooked up with someone that could help more than the people that hang in the forums. I don't see serious devs hanging around the forum and bullshitting with the people there. Go where they might be, in irc. Be cool with them, don't be aggressive or flaky. If you are nice/cool with them, they might take the time away from what they are working on to help you.
Click to expand...
Click to collapse
thanks! were can i go to find this irc? ive gotten a recovery image on the evo's root micro sd in a pc3600 or w.e zip and gotten it to ask me if id like to run it but it wont go any further than that because i cant chose the option. I have a bit of nail glue and im thinking about trying to glue a hair pin to the down button and giving it a pull while i try and run or maybe i can break the button and say oh well... and then from there do it. I dont have any hex or w.e screw driver that are small enough to open the case and do the option described in page one of this forum. Thank you everyone for the help! and keep the ideas coming. I refuse to let this turn out bad, worst comes to worst ill replicate water damage or something and fry the damn thing. then bring it in as a brick.
Any guru's have a quick idea because i want to do this swap.. im so sick of the palm pre. Its like a baby compared to android.
The irc info should be on one of the stickies at the top of the forum. Shouldn't it say something like join us at #evo or something like that.
This is where you can be opening a can of worms, so you've been warned. You can go to sears I think and the tool section and I think they might sell those wierd screwdrivers. I found one that worked for my macbook's harddrive brackets. It's long, has a black handle and generally different colored caps on top of the handle. I kinda doubt radio shack would have it but you could try. Oh, and get a guitar pick to use a the tool to separate the two halves of the phone. I wouldn't use anything else or it might f up the plastic and be obvious you was inside. Maybe look for an evo teardown video somewhere to show you what to expect. Don't force anything!
herbthehammer said:
The irc info should be on one of the stickies at the top of the forum. Shouldn't it say something like join us at #evo or something like that.
This is where you can be opening a can of worms, so you've been warned. You can go to sears I think and the tool section and I think they might sell those wierd screwdrivers. I found one that worked for my macbook's harddrive brackets. It's long, has a black handle and generally different colored caps on top of the handle. I kinda doubt radio shack would have it but you could try. Oh, and get a guitar pick to use a the tool to separate the two halves of the phone. I wouldn't use anything else or it might f up the plastic and be obvious you was inside. Maybe look for an evo teardown video somewhere to show you what to expect. Don't force anything!
Click to expand...
Click to collapse
Thanks I baught a T5 screw driver that will be here the 10th or the 11th and im excited to crack it open haha. Ill let you know the updates of what happens and how the sprint reps react. To w.e damage i decide to throw at it
y0ungcitty said:
Thanks I baught a T5 screw driver that will be here the 10th or the 11th and im excited to crack it open haha. Ill let you know the updates of what happens and how the sprint reps react. To w.e damage i decide to throw at it
Click to expand...
Click to collapse
Came in. and i opened the phone up jiggled the down button got it unstuck and then I was able to re-flash a custom rom so im just going to use this phone untilll it really ****s the bed again.
hello all, first let me just say yeah im a noob and yeah i tried searching.
so like the rest of the world i hated win 6.5 more than anything. seriously. probably something like 1. hitler 2. win 6.5 3. snakes
finally i managed to install win 7, but however the battery is just way to short, some numbers wont be recognized, marketplace isnt open in my country, etc. frankly im ****ing tired of all of this. now i want to remove it and again try to install android on NAND. if not maybe just settle for win 6.5 i dont know.
EDIT
to clarify:
-basically ive searhed everywhere
-i have the offical rom and i want to install that
-i cant connect my phone to zune,
-so when i run the offical htc rom, it just says connect your phone
You need to either flash a stock ROM via sd card method or via bootloader (hold vol down key during power-on, then flash with normal exe from windows).
so, just to be clear,
you got a device with Win mobile on it which you seem to have a massive dislike for and wrongly make an assumption that everyone else doesnt like it, then in a hugely disrespectful manor you compare it to hitler, quite what you are thinking is anyones guess but it might be worth considering a change of manor is perhaps in need
Then attempted to install WP7 without fully reading everything.
Then try and install an original ROM without Fully reading everything
I think That about sums it up
So, in the intrest of sanity, go here
http://forum.xda-developers.com/showthread.php?t=1074233
read it all, and if you have an issue reply in that thread
Couple of pointers to help your days on XDA dev out, if there is a thead open on an issue use it, dont make a new one because it makes it harder for people who actually search for things to find what they are loooking for and its a pain for people who try an help because we are forever repeating ourselves
Secondly, when you make a tread it gave you a list of threads already out here with a similar name, if you didnt see anything relivent its because your use of title is pretty poor, Its windows phone 7 or WP7, Noob isnt a word most of us use
Thirdly, if you can not use the XDA search then use google, (i find it much more accurate) i just searched google using this string
XDA DEV LEO WP7 FLASH ORIGINAL
and the third one down took me straight to that thread above
XDA DEV is pretty obvious, LEO is the listed device name thats on this site WP7 is the OS then FLASH ORIGINAL is the subject matter im searching for
Keep it short, like bullet points, not a long story
So, head over there an folk will be happy to help you out, including myself
I hope i didnt sound rude and off hand, im simply nudging you in the right direction
Neo84 You need to either flash a stock ROM via sd card method or via bootloader (hold vol down key during power-on, then flash with normal exe from windows).
ok, thanks for you reply. sorry to ask but what is a stock ROM? is that like an official ROM from HTC?
also tried to hold down the volume key, get the coloured screen, but then cant do anything. where would one find the "normal exe"? thanks for your willingness to help out someone not as experienced as yourself
and dazza, my good man i do appreciate the nugde, but do find it a bit harsh.
you got a device with Win mobile on it which you seem to have a massive dislike for and wrongly make an assumption that everyone else doesnt like it,
-everyone i spoke to agrees, including the guy who sold it to me for almost nothing (bought for 1100 US 6 months before) because he hated it like no other
then in a hugely disrespectful manor you compare it to hitler, quite what you are thinking is anyones guess but it might be worth considering a change of manor is perhaps in need
-well irony doenst work online my bad, haha seriously noone in ther right mind would compare the 2 and/or accuse someone of doing so
Then attempted to install WP7 without fully reading everything.
-i did, it works almost perfectly, reading on these forums ive seen plenty of ppl having issues, so yeah its close to perfect, except the battery drain (which still works for a full day so i can charge at night)
ive searched google, xda and god knows what. and after trying all, my good old hd2 still wont connect maybe in the end its not worth the time and effort, just leave WP7 on there (it is in fact pretty sweet) and buy an offical android next time! however i do feel i have the right to be a bit angry. winmo 6.5 isnt worthy of selling for a high price in 2010.
anyways, thanks for your help, i will check out those links and see where it takes me just remember that not everyone is as experienced as yourself, a friendly heads up works wonders sometimes
I appologise, it was not supposed to come across rude, harsh is perhaps an accurate way of putting it, remember that some of us take a lot of time out of our lives to go over these things, infact some have even added entries in to the Wiki for just such issues (check leo wiki section) and im sure you can imagin that repeating yourself over and over can be quite frustrating!
I completely agree that a "heads up" is always needed, which is why ive nudged (perhaps with a prod or two ) you in the right direction, those few tips can save you a lot of hassle in the future, the google one especially as i know only too well that the XDA search is crap
Hello to all good guys in xda-developers forum.
This is my very first post and I really feel desperate and need your kind help.
New Acer iconia with stock firmware 3.2.1 was nicely running this morning until I tried to root the device.It was supposed to be very simple process and not to get into dirty complicated procedures but the gingerbreak.apk did not work as expected so I tried alternative methods.What I read in various forums was that the gingerbreak application is not able to root the new firmwares version so I tried to downgrade the firmware to 3.0.1.
Downloaded the Acer stock recovery firmware EUUs_SBK_Acer_A501_0.017.01_PA_ATT.exe and attempted to flash onto my tablet .I think I did all necessary pre-installation checks.The process started but it stopped on 10 percent for about 30 minutes without any progress.Only Acer logo was displayed and 'entering file downloading mode' at the top of the screen.
After long time no change I finally gave up and unplugged the device from the USB port and restarted but nothing works since then.
1. No vibration on Start
2. Black screen
3. No new USB device appear on my PC
4. No sign of any activity other then power button light
I guess the original firmware was wiped but the new firmware was not flashed...for whatever reason...perhaps the worst scenario.
I will really appreciate If anybody may give me advice how to fix it.
So it turns on but does not display anything? Have you tried to hold the power button and volume down button at the same to when you turn it on to try to get it into recovery. Also there is a little reset button on the side you can try to push.
Sent from my A500 using xda premium
tried all those thinks.All kind of tricks I could find on the net.The problem is that the device is not showing up in the device manager e.g not detected as USB device of an y kind....
acera500 said:
tried all those thinks.All kind of tricks I could find on the net.The problem is that the device is not showing up in the device manager e.g not detected as USB device of an y kind....
Click to expand...
Click to collapse
Try this thread. Look about halfway down, and you'll see almost the exact thing you did, and how this guy got it going.
http://forum.xda-developers.com/showthread.php?t=1291747
Basically you can run a search for APX in the main forum threads and find some other posts, but hopefully this will get you going.
I pulled this from the general forum (eventually), but you can also search the Q&A main forum page as well, and the dev forum.
Another link;
http://forum.xda-developers.com/showthread.php?t=1255519&highlight=apx&page=2
If its new just return it to the store for another one.
Sent from my A500 using xda premium
Acer or the store did not brick it
i THINK If you mess with the rom on your tablet and... BRICK your device .. you should tough it out and fix yourself... Acer or the store is not responsible for this .But then you could also argue that if they had not locked the bootloader this type of bricking would not happen..
So i say go above and beyond to try to fix it from the help on here.. if that fails.. THEN Maybe exchange it.. Its wrong to brake something then expect someone else to foot the bill. Yes im to honest for my own good at times... Acer has also been known to repair .
If you bought a extra warranty all of the above in my book is out the window.. Make them replace it ..
GIGGLES..
Good luck on getting it repaired ..and be more careful next time..
Piece of cake to fix if you kept you USB serial number (from the downgrade tool)???
===== If you have your USB serial number ====================
1. Lets assume you know your USB serial number. If not, then you might be able to get it from your registry.
2. Download my flashing tool at http://forum.xda-developers.com/showpost.php?p=20680452&postcount=137
a. Open up the readme.pdf for the instructions on how to flash
3. KEEP your acer unplugged and run the program
4. The program will install the APX flash drivers and will tell you to plug in the USB. Ignore this step. It will not work. In the instructions skip steps 3, 8, 9, 10.
5. Eventually the flashing tool will timeout because you do NOT have the tablet connected. It will then display a message box telling you how to use a paperclip and the power button to get you into APX mode. THIS IS THE secret to getting the tool to flash your ACER. However, once you get it into APX mode you will need your USB serial number (without it, you are fubar).
a. Plug in the tablet to your computer with the USB and paperclip yourself to fastboot.
6. Now in step 11, enter your USB serial number
7. Now just follow the rest of the instructions.
====== NO USB Serial number ==========
If you do not have your USB serial number than you are going to be out of luck, unless you have ever connected the device to your computer. If you did, then your registry will have a history containing your serial number.
Google usbdeview tool and download it. This will show the serial number of any USB device you've connected to your computer.
===== No Serial number, never connected it, what to do ==========
If you have no serial number and cannot get it, then hopefully you can get to recovery mode (power & volume) and flash using a signed update.zip from ACER. Download one of the update.zip's and put it on your external SDCard and then boot to recovery.
=== Bricked and No serial number, never connected, and you fubar'ed the recovery image ===
If you never connected your table to the USB and your computer to get the USB serial number then you are NOT going to be able to flash it to fix it.
If you fubar'ed the recovery image then you won't be able to get into recovery to run the ACER update zip.
At this point, you can still get your tablet into APX fastboot mode using a paperclip and the power button. But I know of NO way to flash it without the USB serial number and I know noway to get the USB serial number from the APX driver. I've tried and looked at getting the serial number from just APX mode, but I cannot determine how to get it. Someone out there might know.
Hope this helps,
TD
Your CPUID can also be found in the uid.txt file in your cwm backup folder - /mnt/external_sd/clockworkmod/backup/ - just remember to drop the 0x when you need to enter it
erica_renee said:
i THINK If you mess with the rom on your tablet and... BRICK your device .. you should tough it out and fix yourself... Acer or the store is not responsible for this .But then you could also argue that if they had not locked the bootloader this type of bricking would not happen..
So i say go above and beyond to try to fix it from the help on here.. if that fails.. THEN Maybe exchange it.. Its wrong to brake something then expect someone else to foot the bill. Yes im to honest for my own good at times... Acer has also been known to repair .
If you bought a extra warranty all of the above in my book is out the window.. Make them replace it ..
GIGGLES..
Good luck on getting it repaired ..and be more careful next time..
Click to expand...
Click to collapse
Honestly if more people returned bricked phones/tablets etc... they would quit locking them down... the you broke it you fix it because they want to keep people from doing things they should be able to do with THEIR system they bought... In other words I completely don't agree with this at all.. If everything was unlocked and such then I would support the you fix it, but then again we wouldn't be running into these issues now would we. But then again Most people need people to babysit them and tell them what they can and can't do with what they own..
wade7919 said:
Honestly if more people returned bricked phones/tablets etc... they would quit locking them down... the you broke it you fix it because they want to keep people from doing things they should be able to do with THEIR system they bought... In other words I completely don't agree with this at all.. If everything was unlocked and such then I would support the you fix it, but then again we wouldn't be running into these issues now would we. But then again Most people need people to babysit them and tell them what they can and can't do with what they own..
Click to expand...
Click to collapse
@wade7919. You clearly have never worked in IT support on a hardware level.
Or maybe, I am barking up the wrong panty-leg?
If you bought a high dollar corvette, GM will support it. If you add an aftermarket chip, and your engine blows, do you expect GM to fix it? No. I wouldn't expect it either. Not their problem. Just because you can add a chip, doesn't mean you should do it.
That's why they try to lock bootloaders. To prevent users from doing things they shouldn't. Unlock them, and it opens a whole world of issues based on "open source". God help us if they unlock bootloaders.....
Not sure what you are getting at. I am under the belief, if you broke it, you fix it. Take responsibility for one's own actions. Shouldn't take the panzy pussyass way (no offence Erica and werecaltf), and return it for replacement. Suck it up, and learn from experience. Otherwise, the next device, you'll do the same stupid thing again.
I like things the way they are. Difficult, but not impossible. That separates the people with balls (again Erica and wercatlf, no offense), from the sheep.
But if you fubar the device, own up to it, and fix it. Don't pawn it off to somebody else (return it). And if you don't have the brain cells to have a backup plan before you start... Well, don't shed tears over it. Own up, throw the testosterone in the garbage disposal, and fix it.
Somebody give me a zanex...
And people, stop using Gingerbreak!!!!!!
Why locking a bootloader will cost ACER billions
Moscow and wade7919, you both make good arguments.
But it is what point of view you're coming form. If I bought a car and changed the RIM's on all 4 wheels and the engine blew up, would GM refuse to honor the warranty?
However, if I put jet fuel and alcohol in for gasoline and blew the engine why would they honor the warranty?
So, the question here is does rooting a device cause actual damage to the device thereby preventing rooting saves them warranty issues? Or is the device also considered to include the software and is covered under warranty?
I'm not taking sides here, but you both are making very good points but with different examples at different points of view.
So, lets look at other items and see if we can draw a parallel. If I buy a brand new Dell computer and send it in for Warranty and there is nothing wrong with the hardware they charge me (correct?). So if I fubar the OS or load something that caused the damage I pay for it or fix it. If there is actually a hardware failure then they cover it under warranty.
So, why does an Android MFG take the warranty one step further and include the OS and take steps to lock it so you cannot change it? Well, this is because nobody owns the OS (it's open source) therefore they take ownership of the build. Because there's no Microsoft to blame, they lock the software and consider it to be part of the overall device (Apple claimed this in their lawsuit). So, in the MFG's mind, there is no difference from the screen, keyboard, or the firmware & software.
So the question is what do you think should be covered under warranty? Most people think it should be just the hardware like a PC. Others see the whole device which includes the OS.
My point of view:
What follows is my rant and my opinion (you are warned )
In my opinion, I had NO problem until they decided to lock the bootloader. I have no problem with them claiming warranty from A-Z and if I change anything they won't warranty it. No problem, I understand that and accept full responsibility. But by ACER locking the bootloader they went too far.
To me this would be like GM welding the hood shut on my car. Better yet, it would be like me waking up one morning and opening my garage to get in my car and discover that during the night GM welded the hood shut. This, in my opinion, is illegal. Matter of fact, in my opinion, it violates US Federal hacking laws because they enter a system and destroyed data. I eventually think OEM's will get a class action suit filed on them for this.
Secondly, Windows 8 is going to be the game changer. OEM's can now make a hardware device and sit behind only warranting the hardware. You have a problem with the OS, call MS. Also, there is a HUGE (I mean HUGE). Did I mention HUGE, demand for tablets in business. Businesses will NOT put a device that has all these consumer games and social networking loaded into the workforce. There are billions in business applications that can be made, but you cannot sell them if they only run on a tablet that cannot have games removed etc.
Example might help: Medical field <- Think of all the applications a tablet can be used to save costs in hospitals. Do your really want your doctor or nurse etc using this tablet on facebook? Insurance company's, law firms, retailers, traveling sales, etc etc (Government). The list goes on.
Developers will see this huge opportunity and will write applications because they can sell them to A-Z and the business buying them will buy them because they can remove facebook and gmail from their company owned tablets. Now, as more and more developers move to Windows they'll drop Android. Want another example, read about Netflix and the issues they have had supporting a fragmented Android OS. So, business applications will move to Windows, but you might say so what, the consumer market is still there. True, but all you need is one killer application that everyone will want and for that to only be on Windows 8. Want some examples, here's my list, NFL (or sports), Netflix, Skype (gee owned by MS now isn't it?), or something new.
Bottom-line is this, if ACER and the others want to lock their bootloaders then they have just taken themselves out of the game for any business sales. Can you imagine walking into a boardroom showing the Government how your new VA application will save the VA Hospitals millions next year alone and improve veterans healthcare. Your application runs on any HC Android tablet. Everything is smoking, going great, as you hand your tablets, ACER a500', around the room. They are loving it. You just hit 'pay-dirt', then someone says hey I see these ACER's have gmail, facebook, blah blah. We cannot have government employees using tablets with those applications loaded, your installer removes them doesn't it? Silence enters the room, all eyes are focused on you. Your mind see millions escaping which were just within your grasp, you pause, you think, and you say YES General as you grab your Motorola Xoom and say 'that's why we recommend you buy nothing but Motorola.'. ACER just kissed millions in sales goodbye (oh and this is a true story).
i do believe acer should lock the bootloader on there devices.
However thee are things I would be doing with my tab if it were not locked.
Acer should give us the ability to flash the bootloader and not use the proprietary software. Lock that software to there bootloader.for there protections.
Give us a wway to unlock it..AT OUR OWN RISK..
So it should be locked but have a way to unlock it with the end user understanding they are totally on there own ..
I would be OK with voiding my warranty.
@Dean,
"So if I fubar the OS or load something that caused the damage I pay for it or fix it. If there is actually a hardware failure then they cover it under warranty."
Yes, that is true. Bootloaders are locked, to prevent completely stupid idiots, from doing things they absolutely no idea what the sam hell they are doing.
The issue is, should we be able to return a device, after we fubarred it? Against warranty? To say, Hey, your weakness allowed me to do it.
Just because the ability to do it exists, and we can quote a thousand instances, It doesn't mean we should, and to shirk responsibility. And pass it off to the main individual.
The fact is, the policies and regulations are there, and we should abide. And if we don't, we have to own up and deal with it.
And if we don't, then we are no better than the low life of the world. The scum.
Moscow Desire said:
@Dean,
"So if I fubar the OS or load something that caused the damage I pay for it or fix it. If there is actually a hardware failure then they cover it under warranty."
Yes, that is true. Bootloaders are locked, to prevent completely stupid idiots, from doing things they absolutely no idea what the sam hell they are doing.
The issue is, should we be able to return a device, after we fubarred it? Against warranty? To say, Hey, your weakness allowed me to do it.
Just because the ability to do it exists, and we can quote a thousand instances, It doesn't mean we should, and to shirk responsibility. And pass it off to the main individual.
The fact is, the policies and regulations are there, and we should abide. And if we don't, we have to own up and deal with it.
And if we don't, then we are no better than the low life of the world. The scum.
Click to expand...
Click to collapse
Very well put.I do know of a few people who have sent there device to acer after messing it up installing rom and telling acer.acer still fixed it free.
Honesty is always best
The evils of rooting
I'm still missing something here, why locking a bootloader does anything. Go get a Mortorola Xoom (not the FE) and you run the unlock OEM. It tells you that you are unlocking it. It tells you that you unlock it at your own risk. You cannot relock it until it is 100% back to stock. It asks you three times are you sure.
Locking the bootloader and treating everyone as an idiot is the problem. Just do what Motorola does, and stop being everybody's keeper. If they want to 'Police' this then you should have to call ACER and they fax you a form. You give DNA to prove who you are and fax it back. Then you go to a mandatory rooting class, that lasts for 5 days, where ACER preaches to you the sins of rooting. Then you have to take and pass a test. Then and only then, after passing the test you get a certificate. Then you call back, give them your certificate ID. Now they give you the secret key to unlock only your tablet.
That's the ticket,
TD
Bottom-line, it's not that they locked the boatloader, it's that you cannot unlock it. Like I said, go out to your driveway some morning and find that GM welded the hood to your car shut because they think you are stupid and shouldn't be opening the hood. Mind you that YESTERDAY, and at the time your bought it, it was not welded shut. That ladies and gentlemen is what ACER did with their OTA.
Moscow Desire said:
@wade7919. You clearly have never worked in IT support on a hardware level.
Or maybe, I am barking up the wrong panty-leg?
If you bought a high dollar corvette, GM will support it. If you add an aftermarket chip, and your engine blows, do you expect GM to fix it? No. I wouldn't expect it either. Not their problem. Just because you can add a chip, doesn't mean you should do it.
That's why they try to lock bootloaders. To prevent users from doing things they shouldn't. Unlock them, and it opens a whole world of issues based on "open source". God help us if they unlock bootloaders.....
Not sure what you are getting at. I am under the belief, if you broke it, you fix it. Take responsibility for one's own actions. Shouldn't take the panzy pussyass way (no offence Erica and werecaltf), and return it for replacement. Suck it up, and learn from experience. Otherwise, the next device, you'll do the same stupid thing again.
I like things the way they are. Difficult, but not impossible. That separates the people with balls (again Erica and wercatlf, no offense), from the sheep.
But if you fubar the device, own up to it, and fix it. Don't pawn it off to somebody else (return it). And if you don't have the brain cells to have a backup plan before you start... Well, don't shed tears over it. Own up, throw the testosterone in the garbage disposal, and fix it.
Somebody give me a zanex...
And people, stop using Gingerbreak!!!!!!
Click to expand...
Click to collapse
Okay comparing A Tablet or PHone to a car is stupid... Compare it to a Desktop Computer or Laptop... Companies do not lock them down so you can not use different OS's now do they.. They offer Backups to restore the system back to how it was with recovery partitions dont they? or they offer the choice to buy whatever OS you want to install correct? they don't limit you to say just Windows or *NIX do they? But we don't see laptops or desktops locked down to where you can't upgrade your system yourself or anything else... and any dumdass can do that without an issue most of the time. and there is more issues with viruses and crap on computers than phones or tablets...
So before you start making statements like compare this to that learn what to compare to first. If you mess something up on a hardware level sure pay for it.. if you mess something up on a software level because they decided to Babysit people its their fault. and if you think its the persons fault because they decided to open up a PRODUCT that they bought and own then you are one of the people that need babysitting and like everyone telling you what to do and how to do it. Go to an apple product then.
---------- Post added at 07:07 PM ---------- Previous post was at 06:51 PM ----------
Also if you really brick your device you can always give
http://paranoidandroid.us an email to findout about getting it fixed
wade7919 said:
Okay comparing A Tablet or PHone to a car is stupid... Compare it to a Desktop Computer or Laptop... Companies do not lock them down so you can not use different OS's now do they.. They offer Backups to restore the system back to how it was with recovery partitions dont they? or they offer the choice to buy whatever OS you want to install correct? they don't limit you to say just Windows or *NIX do they? But we don't see laptops or desktops locked down to where you can't upgrade your system yourself or anything else... and any dumdass can do that without an issue most of the time. and there is more issues with viruses and crap on computers than phones or tablets...
So before you start making statements like compare this to that learn what to compare to first. If you mess something up on a hardware level sure pay for it.. if you mess something up on a software level because they decided to Babysit people its their fault. and if you think its the persons fault because they decided to open up a PRODUCT that they bought and own then you are one of the people that need babysitting and like everyone telling you what to do and how to do it. Go to an apple product then.
---------- Post added at 07:07 PM ---------- Previous post was at 06:51 PM ----------
Also if you really brick your device you can always give
http://paranoidandroid.us an email to findout about getting it fixed
Click to expand...
Click to collapse
I still like my car comparison
I make the car comparison to illustrate a point, because when I compare tablets to a PC everyone piles on *****ing about MS.
Bottom-line it doesn't matter if it's a blender or a PC. I own it, you own yours and I can do what I want with mine as you can with yours. Now, again I have a BIG(did i mention BIG issue with them changing it on me after I bought it.
To get back on topic, is the original poster still out there?? Has any of this helped? Are you still bricked?? Give us an update so we know if anything worked or you still need help.
The device was returned and accepted for replacement by the shop.Got new one and feel very nervous to start rooting procedure over.I was really lucky that they did not charge me anything but I really want to know what I did wrong so I don't brick my new device again.
I will provide further details soon about my computer OS and firewall settings and perhaps we may figure out what I did wrong.
To all good guys who send me them suggestions and solutions I wanna say big THANK YOU !!!
Your help is really priceless and thrilled me deeply. Will update topic soon
Happy New Yer to all Android fans!!!
So...Back on the subject.
My device was purchased in Japan and its current firmware version is
Acer_A500_7.009.03_AAP_CUS6JP
Q1. Can I flash US or World Wide firmware version on that device.
Q2. Does anybody know the Acer's ftp download server address for Japan
Q3. I think its a good idea to dump my original stock firmware but it seems there is no way doing that prior rooting.So..kinda stuck .any suggestions appreciated.
P.S. I'm thinking about flashing the latest Rooted rom 3.2.1 V3 by timmiDean (thanks for your hard work) I read the instructions very carefully and I think that everything will go smoothly but just in case (considering the specific Japanese firmware version)
would appreciate any further directions by the author.
Thanks
Stupid thing is that I can do everything to it aside from getting it to boot all the way to work! I tried reflashing OEM roms and I tried custom roms. They all work just fine and it just won't boot all the way. I can turn it on and off, use format option, download mode and magldr. I keep my sim out and memory card. Before this all happened I always used OEM OS. Last thing I did was check my bank account, close the browser and click the power button to turn it into sleep mode. Few weeks ago I did have an issue with it for a day. It kept turning on and off constantly boot to random points. Mostly to the AT&T screen. It would boot all the way rarely and I got it to stay on a couple times for about 10 mins to copy all my stuff from it. Is it possibly something to do with the hardware being a POS and Just crapping out for no reason because cell phones are poorly made expensive bricks?
I've seen this issue across the forum several times. Unfortunately, just one case seemed to "return" to life, without understanding the reasons behind the "lapse".
What I can suggest you can do (and feel free to disagree) is get in touch with Cottula (creator of MAGLDR) and see if you can help you. You can send him the phone, maybe he can analyze it and get something out of it.
GL, mate, and if you find a solution, I'm sure other folks here would be glad to hear it.
Ahhh ok thats what I figured. I browsed a bit, but most of what I saw is people couldn't do anything. I didn't see anyone saying they could do as much as what I can do with it. I'll try your advice and see if maybe he could help. I took apart the phone to see if maybe someone came loose, though I saw nothing. Clean as a whistle. What I think maybe happen is it burnt up finally. I notice at times it would run extremely hot, mostly when I'm talking on it for more then an hour.
Well, for your sake I hope it's not burned out (hardware issue). I hope it has some software component that's screwed and that has a chance of being investigated and maybe fixed.
Also, the getting hot while talking/browsing for periods more than 30 min it's a known issue. It's however supposed to be quite warm, but not actually really hot, if you know what I mean. It it however possible that exposing the phone to higher temperatures to cause hardware issues.
In any case, I wish you good luck. Who knows?
I gave AT&T a call to see what they could do. The software warranty is 6 months past and she wasn't able to override anything that much passed over. Though I was able to get my 2 years wavered and get a early upgrade. So I got myself a Xperia Ion. I'm happy I don't have to put up with a flip phone for another 4 months. lol
I tried working on my focus a bit more playing with zune and other programs I found. Though I don't see it coming back to life trying all the different ROMs. I would think to make it work again is to re-flash the actual phone bios itself. Just like a computer starting it still uses DOS then loads the OS. I don't know how a phone works to much, but I'd assume same process. Something to do with the root-root of the phone telling it to be stupid and not boot properly.
Another note, where is the best place to sell this to get some money out of it? Screen and other pieces of its hardware are 100%. Should I try ebaying it?
I had a similar issue, last thing i did was removing the SD card before re-flashing the MGLDR and custom ROM