Tried to upgrade the ROM on an M1000 to 2003 SE from a 1.600 version and wound up with the following symptoms.
Only able to see the bootloader (v1.06, but computer recognises the device when in the USB cradle)
HimaUpgradeUT will run as far as the screen saying what ROM it's replacing (though it says that there is nothing on the device itself). Then when I press "next" it just hangs on the erasing ROM 0% screen until I get an Error 112.
Tried using two different computers and still get the same error.
Tried different HimaUpgradeUTs and still get the same error.
Tried hard resets, soft resets, reinstalling ActiveSync, disabling ActiveSync etc.
Going insane and need suggestions. Help!
I think your best bet is to revert to the original ROM. I thought it was on this forum, but I just looked and can't find it, but...
http://www2.orange.co.uk/servlet/Sa...096364420640&product=Feature&t=Product#answer
Should get you to the ROM download page on ORANGE UK, where you have a choice of with and without MMS ROM images.
If you can get your 'phone back - that might be a start.
Richard
Edit - just tried the link and it isn't that good. Go to 'Your phones features'.
Sadly I've already tried that. But it won't accept anything. Thanks for the suggestion though.
I at a loss as to what exactly the problem is. I've checked the log file from the HimaUpdateUT file and it keeps trying to erase the original ROM but can't. Which is weird because there doesn't seem to be anything on the device. I wish there was better logging by the program.
I'm starting to consider exploring Bootloader commands to see what I can find.
did you put your device in BOOTLOADER MODE?
PROCEDURE: PRESS ON/OFF POWER BUTTON-SOFTRESET BUTTON-NAV PAD
Yep. In fact I can't get it out of bootloader mode. Have hard reset it several times.
Hi,
do you have SD card???
buzz
Ironically I just ordered one before I fried the device. I guess using it to transfer the ROM image is a possibility. It looks difficult though.
Related
Obviously I'm a n00b I just got my 8525 yesterday, right away I upgraded to WM6 went all day today with it working fine, I installed a PockMSN and Windows Live anyways to keep it short I FIGURED I WOULD just RE-INSTALL Windows Mobile 6 to get a fresh phone (didnt know hard reset did the same) Actually it was the 3rd time I flashed the OS and RE-UPGRADED to WM6 to get a fresh phone!!!!
~heres the trouble~
In the middle of the reinstalling WM6 I accidentally reset my computer, didnt realize it right away and, got ERROR 260 I believe, anyways I followed the directions, took out the battery and reset, plugged the USB back and RAN the Offical WM6 Rom of HTC site again and it keeps getting stuck EVERYTIME at 11%, I have tried it like 10 times and it gets stuck at 11%, and I get the same ERROR. Says Communication error 260. I have tried everything I know reset the computer, changed USB cords, and Nothing, everytime it gets stuck at 11%!!!!!!
Any Ideas about how to get my 2 day old Hermes back??
(I know i did a n00bish thing and I am sorry)
same place everytime!!
I tried to reinstall Active Sync, changed USB cables, switched USB ports, nothing!! I keep getting ERROR 262 (thought it was 260 at 1st) and wont get past 11% says no connection. I do notice everytime i try this process, Active Sync isnt connected, but the Hermes is connected to the computer! Cause if it cant read the hermes it wouldnt be able to even start the update process. But 11% everytime its stops
nicknowsky said:
I tried to reinstall Active Sync, changed USB cables, switched USB ports, nothing!! I keep getting ERROR 262 (thought it was 260 at 1st) and wont get past 11% says no connection. I do notice everytime i try this process, Active Sync isnt connected, but the Hermes is connected to the computer! Cause if it cant read the hermes it wouldnt be able to even start the update process. But 11% everytime its stops
Click to expand...
Click to collapse
Perhaps you could try to flash using the sdcard method. So you would not be connected to a pc anymore. Who knows, it could solve your problem. I know one case where installing an official rom cured also a similar problem.
Quick summary of the sdcard method:
Use an empty sdcard formatted in FAT32
Copy the RUU_Signed.nbh file containing the OS to the card and rename it: hermimg.nbh
Enter bootloader mode (OK + POWER + Softreset). Normally, after the 3colors screen, you will get "Loading" followed by a description of what is on the card.
When ready, press power and... wait...
Good luck (The phone is NOT connected to the pc)
sounds good but I dont have a MicroSD card reader to do that. And I am using an Offical HTC WM6 ROM, thats all I ever used was the offical WM6 Rom from the AT&T site. Like I said, I was able to install WM6 already, but me being a complete idiot was Flashing the upgrade ROM to get the Hermes back to fresh phone factory settings. But I accidentally reset the computer in the middle of Flshing and since then I have never been able to get it to install again, everytime I turn on the phone I am stuck at the Tri-Color Screen, I am able to restart the upgrade process, but it stops at 11% says ERROR 262 and no connectivity!!
please anybody knows anything, this is the only thing I got, my mom got it for me! We cant afford to get a new one, or even fix it, it was a special present!
nicknowsky said:
please anybody knows anything, this is the only thing I got, my mom got it for me! We cant afford to get a new one, or even fix it, it was a special present!
Click to expand...
Click to collapse
Ok. I am a bit annoyed if you cannot try the sdflash method (BTW you can ask somebody having a PC to prepare the card for you.)
There are different things you can flash on your hermes. Radio, OS, Splash screens, Extended Rom,.... The most tricky thing is the radio rom as a failure there has a higher probability to brick your pda.
This is why i believe it is very dangerous to flash right away without some readings and understanding about what you do. i hope you had some experience here.
Did you first install hardspl (olipro 2.10 )? This is not mandatory but is a very good protection against bricking. (here the excellent guide of mrvanx: http://www.mrvanx.org/cms/index.php?option=com_content&task=view&id=30&Itemid=27 )
Did you flash also a radio rom? (Was it included in the "package" you wanted to flash?) If yes, i am a bit anxious that a stop at 11% is a problem... BUT, if you flashed a radio rom, it goes very, very, very... slowly. And gives the feeling that it freezes. For the "radio" part it is normal . I hope you did not stop the process too soon.
Once again, try the sdcard method. Or try to flash an official rom (most of the time containing a radio part...) and be patient. Can take till 25 minutes.
If this does not work, do not panic yet. Others had also problems before you: go there and start reading : http://forum.xda-developers.com/showthread.php?t=286755 and here http://wiki.xda-developers.com/index.php?pagename=Hermes_Unbrick
There is a hope to solve your problem. Good luck
Try to flash a radio ROM, turn the device on and if it stays at the bootloader screen (the tri colour screen) make a note of the version displayed. Hook up the device with USB cable, dont worry about activesync.
Download and unzip a radio ROM upgrade (try this one), run the exe, select your bootloader version on the screen....follow the screens through and see if it works.....radio roms take ages to flash so DO NOT disconnect your device.....if it doesnt work you most likely have a corrupted radio bootloader.............which is likely since the radio flash takes the longest ammount of time the reset probably occurred halfway through this.................unlucky
Give it a try though.
The lesson to learn here is to READ THRICE and flash once.....never ever disconnect your device out of impatience (which i suspect has happened many times on a radio flash) and be carefull these devices are expensive
mrvanx said:
The lesson to learn here is to READ THRICE and flash once.....never ever disconnect your device out of impatience (which i suspect has happened many times on a radio flash) and be carefull these devices are expensive
Click to expand...
Click to collapse
I could not say better
I know, the MicroSD method is nice, but when I got the phone the guy gave me a MicroSD card, but not the regular SD card to read it on computers ( i do have a card reader) Guys a super appreciate the replies> I am gonna try everything rite now, but real quick is my Hermes FUCT??? or is this error fixable??? It is just losing communication everytime at the exact same place, it just seems like something is fixable, but my sorry luck i cant get over the hump!! I will let ya'll know ASAP
okay, here is the thing, Every Hermes ROM update utility I have downloaded wont work, i start it and the VERIFY INFO ON HERMS windows appears about 2 minutes late I get ERROR 260 and it exits! Now when I use the OFFICAL WM6 upgrade ROM from the ATT/HTC site it seems to read the HERMES and wanna start the upgrade process, but thats where it ends at 11% No other RUU I have used or tried has even gotten that far, I just get ERROR 260 before it starts and I have to exit.
What it looks like is I cant communicate with my HERMES at ALL!! Active Sync wont see, only when I reset my computer and reset the HERMES and I plug it in a different USB port, it says Installing New Hardware and HTC USB something and then Hardware has installed and is now ready to use. But Active Sync wont recogniZe it
I'm sorry to tell you that but i think you ****ed up your phone and it is as useless as my ****ing jasjam.
please give us some detailed info s about your hermes like IPL SPL GSM STATUS....
When I am in Tri Color Mode I see.......
HERM100
IPL-1.04
HERM100
SPL-2.03
and SERIAL at bottom, then USB when I plug it in to my computer
I had upgraded to WM6 before on it, but me being a impulsive FOOL, i flashed it again to get me back to Factory Setting (didnt know HARD RESET did the same) and I accidentally RESET my computer in the middle of ROM Upgrading and ever since I cant get past 11% when I try to do it again (using the OFFICAL WM6 ROM from HTC)
and I cant get any communication with mtty although I dont know much about that app, I get a CANT load screen appear
is your phone KITL enabled.
hold the COMM manager button + POWER button + OK button (the one on the left side under the jog wheel) and reset with stylus.
if you see KITL dialogue then it is KITL enabled (MY bricked jasjam is KITL disabled)
if it is KITL enabled then read : http://wiki.xda-developers.com/index.php?pagename=PB_KITL_HERMES and your phone will be just fine.
if it is not then your phone is ****ed up just like mine
HA HA, me and my phone guy (well the guy who I bought my Hermes from) HAVE FOUND A FIX to get the phone outta Bootloader Mode and back into OS!! in my case WM6!! I have to do it 1 more time to fully confirm the method!!!!!!!! My friend is calling "SHOCKING THE PHONE" but not really shocking anything!! I am reluctant to share the method, but this site needs more people to actually HELP out others
nicknowsky said:
HA HA, me and my phone guy (well the guy who I bought my Hermes from) HAVE FOUND A FIX to get the phone outta Bootloader Mode and back into OS!! in my case WM6!! I have to do it 1 more time to fully confirm the method!!!!!!!! My friend is calling "SHOCKING THE PHONE" but not really shocking anything!! I am reluctant to share the method, but this site needs more people to actually HELP out others
Click to expand...
Click to collapse
Hey dude!
Would you kindly provide me the sulotion.
I would appreciate it.
nicknowsky said:
HA HA, me and my phone guy (well the guy who I bought my Hermes from) HAVE FOUND A FIX to get the phone outta Bootloader Mode and back into OS!! in my case WM6!! I have to do it 1 more time to fully confirm the method!!!!!!!! My friend is calling "SHOCKING THE PHONE" but not really shocking anything!! I am reluctant to share the method, but this site needs more people to actually HELP out others
Click to expand...
Click to collapse
Mmm... do i understand correctly your post? Are you hesitating to help others because your method is risky, or because you express some exasperation about people on this site? In this case, do not forget that all people here are exchanging ideas, questions etc on a totally free base without any obligation. In the limits of there knowledge. Encountering a problem after flashing a device is the only responsability of the user. We just try to help. But i prefer to believe that you found a method, still risky, that you need still to test
That said, it seems that there are an increasing number of hermes encountering a problem with the radio part. It seems that stopping a flash at 11% is a symptom of that. See some consolidation of those problems here: http://forum.xda-developers.com/showthread.php?t=349461
I hope you will find a solution for your problem and moreover i hope that none of you bought a hermes second hand with an already radio part problem. If so try always to get your money back...
I AM trying to confirm my method BEFORE i share it, because it might work on mine, and I dont wanna screw anyones hermes up more
nicknowsky said:
I AM trying to confirm my method BEFORE i share it, because it might work on mine, and I dont wanna screw anyones hermes up more
Click to expand...
Click to collapse
Why don't you answer my PMs????
Please tell me your sulotion and let me try that if you have any
Hi,
I have a problem with my HTC HD2, thing is that the phone it's not booting correctly, all i got when i power on the device, it's an emty white screen... without the green HTC letters.
I got installed a cooked ROM, BsB Beast 6.1, with radio 2.12.50.02_2, and i was running Android from SD when all this **** started, two weeks ago. The phone battery ran out while i was on Android, a couple of hours later... i got home and plugged the phone for charging. When i pressed the power button, the phone boots with that blank screen.
I can get into the bootloader, and it's showing this info (whitout the underscores):
PB81100 HX-BC
SPL-1.42.HSPL XE
_____________0x05
_____________0x30
CotullaHSPL
I've tried many different things and none seems to do anything at all:
- First of all, i did a hard reset. The process ends OK but the phone stays doing the same
- Then, i tried to flash again the same ROM i was using. I was unable to do that by using CustomRUU and PC connection. The phone it's detected by the PC, and the bootloader screen shows that it's conneted by "USB". Then, i executed the CustomRUU app, following all the steps and, when the phone should start flashing the progress bar doesn't get past 0%, both the phone display and PC. After a few minutes, CustomRUU gives an error saying "timeout" connection. I've tried to do this from different USB ports and different PCs with the same result.
- After those fails, i tried to flash again the cooked rom from SDCARD. The process ends OK, saying "Update Complete". Then, i rebooted the phone but the blank screen remains the same way. That cooked ROM doesn't have radio.
- After that, i decided to flash a stock ROM. First, i tried to make a "Task 29" to the phone, but i got the same problem than with the cooked ROM. The progress bar doesn't get past 0%. With the stock ROM the problem was the same again. Then, i tried to flash the stock ROM from SDCARD. The process stops at X% saying 0018003 RADIO - FAIL. I've got this error each time i try to flash a ROM with radio or a radio itself.
- I was able to do a "task 29" by using MTTY, but nothing changes when i try to flash any ROM after that.
- i've tried to upgrade my HSPL, by using both HSPL2 and HSPL3. Both programs detects my version of HSPL, then the process starts and ends saying "Succesfully done" but nothing changes in my bootloader, it's still saying that i got 1.42.HSPL
Since i can get to the bootloader, i hope to have any chance to get this device back to life.
I've readed some posts here and within other forums, i've tried with many different cooked or stock ROMS but nothing works
I hope to find help here, thanks in advance and, sorry if my speaking it's not 100% correct
yet another "i was running android and...........now my phone won't boot".. thread. makes me glad i don't bother with android...tried it once and had to hard reset, never touched it since, heh.
for the sticking at 0%,and timeouts etc, try and always enter bootloader yourself, then wait for serial to become usb, and then run customruu. this way you can also visually confirm hspl is there(or not there, depending what you are doing) and it should cure certainly the timeouts.
if i were you, i'd concentrate on getting back to stock, and start over.(only skimmed your post, i'm mobile, so sorry if i say something you already did.)
get into bootloader, get rid of hspl if it s there,(run hspl2 and choose 1.66.0000) then back into bootloader(you should soon get used to holding vol down as each stage completes to reenter bootloader) then try flash your CORRECT stock rom via usb. if that fails try it using the sd card method.
Thanks for answering, samsamuel.
I haven't looked into the Android section for threads with the same problem i got, maybe i should have started that way
Each time I enter the bootloader, i'm doing as you've said (believe me... in these days i've become a "master" on pushing power button with vol. down )
I always wait for the bootloader to finish loading, then i plug the phone to my PC, wait again for "Serial" turns into "USB" and, then, start the flashing process.
I'll try to do what you said with HSPL2, to select 1.66.000. Each time i've tried with different HSPLs, i've selected 1.66.HSPL or 2.08.HSPL... so, i guess i should try with that.
I'll be updating this thread as soon as i got news.
/me edit
I must to say, that Android was running "fine" (some minor problems when trying to wake up the phone, but nothing critical apart from this disaster). By the record, i didn't have installed dual boot... the phone always boots into WinMo
Hi again,
I have tried to update my SPL to 1.66.000 without success, despite what HSPL2 says ("Succesfully done")
Any thought about this? I can't understand why those programs are saying "OK" but are doing nothing
thanks in advance
not seen it first hand but have read several threads where the update seems to work but nothing changes. not really sure as to cause or cure, sorry.
I wonder if is there a way to make HSPL2 / HSPL3 to leave traces or any log of what they are doing... in order to see why my phone is ignoring them
Little bump, looking for more help
Is this the right subforum to post this things?
Well i have been looking all over for help with my phone. I have figured out that i tried to flash a rom without unlocking my bootloader. Well im running windows 8.1 and for some reason i couldnt get my computer to recognize the phone at all. After using 3 or 4 different guides i gave up for a few days so not to get too aggrivated. I mean its my own fault but my back up phone sucks lol. So i borrowed my wifes laptop running win 7. I Followed this guide androidforums.com/optimus-l9-all-things-root/807569-guide-security-error-fix.html. For the first time since i started trying to solve my issue everything seemed to work got the s/w screen to appear in reverse and using the cmd prompt that says wiating for device then starting the .bat file from the download it says on the bat cmd prompt that everything worked. well at the bottom its says done then comes up with C:\fastboot\yours. i have been browsing google but i havent been able to find what i am supossed to do with the yours file. i tried putting a kdz file into the file location and running it from that but no luck. after a few min the phone auto reboots and comes back with the security error screen and not the backwards one. i have tried doing the hard reset at the point but no luck. if someone could please help with what i need to do with the fastboot/yours area that would be awesome. Or at least point me in the right direction cuz google isnt wanting to be my friend with the searches.
Android noob in training:
Sobih
help
Well i have tried several times now with using my wifes windows 7 laptop. i can get everything to work with the screen coming up backwards and in the command prompts it says that the fastboot is done then loads the command fastboot/yours which with the file i downloaded that file was empty. really unsure on what i need to do at this point. from the guides i have read it seems that im at like a step or 2 from getting the phone to work but after 30 seconds while still plugged in it reboots and loads the secruity error screen. from what i have read i should be able to do a factory reset by holding the volume and home button and then pressing the power for 3 seconds but it just reboots into the error. any help would be much appreciated i really dont want to have to buy a new phone.
Seems like that guide is more for when flashing a recovery on the locked bootloader and things go wrong. It was suggested a few posts down on the first page of that guide that if your problem happened when you were trying to flash a rom you might want to follow this : http://androidforums.com/optimus-l9-all-things-root/792689-guide-unbrick-manual-update-updated.html or http://forum.xda-developers.com/showthread.php?t=2085344 (the xda one seems more complete) .
sigh
Well im still stuck on the security error screen. i got the phone to boot into the backwards fastboot screen 1 time and cant remember how to do it again. i can boot into the s/w upgrade mode. if i go to use the lg support tool being that im in the united stats my options is upgrade recovery or help. well if i go to upgrade recovery im told that my phone has the latest upgrade already. if i try and use the moduptest that come in a lot of the unbricking guides it makes me turn the internet back on even with having hte shttps and everything else that is listed in the various folders. i only have the omap44 on my device manager 1 time but there is also 2 lg mobile modems. im thinking my issue lies with the fact thta i dont have the adb file for the device manager. i have donwloaded and uninstalled various times but still no luck. i dont remeber how i got the phone to the backwards fastboot but i remember i was following a guide and the op had to open one file and while that one was stuck on "waiting for device" he opened another one becasue that was the only way he could get it to connect. Any help would be awesome. not trying to rely on everyone else but after several weeks trial and error im at my wits end with it.
thanks
sobih
This problem has been driving me absolutely mental. About 2 months ago, I tried to root my Galaxy Tab 4 8.0 by T-Mobile (it was an old device anyways), I used the Odin method, and while it was installing, it said that the process was successful, and I saw it all come through. However, when my device restarted, it was stuck at "Starting apps..." for about an hour, so I tried restarting. Then it was stuck on the T-Mobile logo for 1.5 hours. I did a hard wipe/reset, and it was fine... for about a week.
The funny thing about it is, after I did the hard reset, certain bugs would happen, a different bug each time. (For example, Google Play apps would be stuck at "installing", screenshots wouldn't save, apps would crash repeatedly, etc) So if I tried to restart, it wouldn't fix it, but instead it would bootloop. I have to hard reset/wipe my whole system each time it happens, and it drives me up the friggin wall.
I saw online that you can try flashing your system by installing the default drivers onto your computer, and install it on your system through Odin. (or something like that, I'm not that professional at mobile technology) Awesome. Just one problem.. I have looked everywhere and I can't find the driver specifically for my system. I have looked for the driver ever since the problem got worse and I found out about this information, but I found nothing.
If anyone has any idea on how you can help, please respond as soon as you can. Thank you very much.
iamnekro said:
This problem has been driving me absolutely mental. About 2 months ago, I tried to root my Galaxy Tab 4 8.0 by T-Mobile (it was an old device anyways), I used the Odin method, and while it was installing, it said that the process was successful, and I saw it all come through. However, when my device restarted, it was stuck at "Starting apps..." for about an hour, so I tried restarting. Then it was stuck on the T-Mobile logo for 1.5 hours. I did a hard wipe/reset, and it was fine... for about a week.
The funny thing about it is, after I did the hard reset, certain bugs would happen, a different bug each time. (For example, Google Play apps would be stuck at "installing", screenshots wouldn't save, apps would crash repeatedly, etc) So if I tried to restart, it wouldn't fix it, but instead it would bootloop. I have to hard reset/wipe my whole system each time it happens, and it drives me up the friggin wall.
I saw online that you can try flashing your system by installing the default drivers onto your computer, and install it on your system through Odin. (or something like that, I'm not that professional at mobile technology) Awesome. Just one problem.. I have looked everywhere and I can't find the driver specifically for my system. I have looked for the driver ever since the problem got worse and I found out about this information, but I found nothing.
If anyone has any idea on how you can help, please respond as soon as you can. Thank you very much.
Click to expand...
Click to collapse
What you read in the internet means re-flashing your stock rom (system), that is the fix for your problem, the way to do it is to download and install Samsung USB drivers if you hadn't done that already, and Download stock rom from here or here search your model number in the search box and choose the stock rom based on your country, and flash with Odin, it's pretty much the same way you tried to root using CF-ROOT method:
1-you boot into download mode (volume down + home button + power button)
2-and then connect your phone to PC.
3-open Odin and uncheck everything except "auto reboot" and "F. Reset Time" (you should find it like that already), make sure your phone is recognized by Odin, you will see a blue box with a message saying "0:[COMX]" where X is a number.
4-press AP (or PDA in some versions) locate your stock rom which should be in .md5 format, and choose it, then 5-press start.
6-wait for the process to finish (takes a while) and then the phone should reboot itself and you will get a message in Odin saying "Reset!"
PS: you must register on the sites to download..bad thing i know but it's obligation.
Searched both of these websites for the drivers, found nothing.. I've been searching the internet for hours and not one driver was found. Extremely disappointed.
iamnekro said:
Searched both of these websites for the drivers, found nothing.. I've been searching the internet for hours and not one driver was found. Extremely disappointed.
Click to expand...
Click to collapse
Give me your model number.
Sorry found it in the thread title
@iamnekro
That is the link from the first site:
SM-T337T latest firmware android 5.1.1
That is the link from the second site:
SM-T337T latest firmware android 5.1.1
Obviously you didn't search at all...LOL
PS: It's called Stock Firmware or Stock ROM.... not Drivers
Register on any of the sites first to download.
And press the thanks button please
Regards Migo
I'll have to close the thread.. my computer isn't that advanced and is low on space anyways...
iamnekro said:
I'll have to close the thread.. my computer isn't that advanced and is low on space anyways...
Click to expand...
Click to collapse
It doesn't need any advanced computer and only the size of the stock rom and Odin, it's no big deal.
I only want my Wogiz WX40 to work properly again. It somehow got into a booting loop and I spent many hours figuring out how to flash it due to drivers acting unexpectedly, incorrect instructions for my device and so on.
I finally got it to flash with stock software I got from needrom using SP Flash Tool. However 1) none of the bottom keys work now and 2) it looks as if the resolution is set too high for the device and I think there is also some slowness when using the phone. I have tried clicking upgrade firmware and formatting the entire flash and using different versions of the software and the result is always the same - the bottom keys not working in particular makes it unusable. I tried downloading the stock rom from another location but after downloading it said I needed a password.
So what is the next thing I can try? I'm at my wit's end here and just want it to work again. Thanks for all help.
Anyone know what I should try? For example what custom RAM + firmware might I want to try? At this point I don't care what it is as long as it works. It's a MT6580 device if that helps.
God, I FINALLY got it working.
In case there's anyone else that runs into this: My mistake was getting the stockrom from needrom, every one of those roms for this phone is bad. Get the rom from shareas.us and use SP Flash Tool to flash it, and even then you have to try to get the one that isn't password protected with no password. Leave the battery in, turn the phone off, use option "format + download" in the software and click download BEFORE you connect the phone, NOW connect the phone and after a little while it will start downloading. Disconnect the phone when it's done and switch it on, it will take a REALLY long time to boot up the first time but it should then work.
That's what came from hours of trying to get it to work. The tutorials etc. online are so confusing, even some incorrect instructions like saying I should take out the battery that are completely false and I would never have gotten it to work if I paid more attention to them. I don't ever want to go through something like that again. I finally have my phone back.