Did you hard brick your Verizon Note 2? Flashed the wrong boot loader, now you're bootlooping and ODIN can't save you??
We all know a ton of users who have had this happen to them, I read it all the time. After stumbling upon another post I figured I had a chance. The instructions are clear but I want to build upon them with my own experience.
So first off many, many thanks to KOBOL for posting his guide which is buried below a ton of other posts in this General Section. I wouldn’t have a working phone without his work!
A bit of background info: I flashed a T-Mobile Note 2, 4.3 ODIN Image for My Verizon Note 2 because I wasn't paying attention... All I saw: "4.3 stock/rooted/deodex with 4.1.2 bootloader" (which I have) and "no wifi fix needed & stock kernel running smooth" (I have wifi fix & custom kernel, both which cause constant reboots) SO... I flashed it and boot-looped. "Good job, dumb dumb" I thought to myself as I gazed upon my hard bricked phone. No ODIN restore could get me out of this one, and I tried for 2 hours...
Then I found Kobol's post on unbricking your phone. I read the instructions, I was very confused at first as to how I was going to get this accomplished, so I am writing up this re-tutorial with new instructions. Make sure you have precision screwdrivers, flat and philips head.
Continue to Post #2 to Unbrick your i605!!
Instructions for Unbricking Hard-bricked i605
1a) DOWNLOAD THIS - It contains an IMG file you'll need to restore your 4.1.2 Bootloader, also contains 2 pictures of the resistor you'll need to short. More on that later.
1b) The above download is all you need if you're on 4.1.2.If you're on the newer 4.3 MJ9 Bootloader, download this too and use that IMG instead. the 4.1.2 download is necessary because of the pictures. Not 56k friendly. I will edit when KOBOL reviews this and allows me re-upload his pictures as a separate download.
2) Download and install win32diskimager. it'll write those image files to the micro SD card properly. DO NOT JUST DRAG AND DROP THE IMG... YOU MUST WRITE IT WITH AN IMAGING PROGRAM
3) Write the downloaded IMG file to the Micro SD using win32diskimager. Select the source and destination, that's it super easy. Make sure Micro SD is at least 2GB. I used a 32GB it was the only one I had and it worked fine, no need for exactly 2GB micro SD.
4) Open phone, no need to completely dismantle to the screen.... many good videos can be found on youtube. Take out every screw you can see and remove the rear outer plastic casing.
5) Once the board is exposed, remove the black screw that holds the speaker assembly to the phone. Remove and place speaker aside.
6) Remove 2nd screw on the right side along the skinny motherboard strip. Remove all wifi connectors/lcd connectors/camera connectors, etc. The motherboard can now be removed completely.
7) Gently remove the speaker/power button, the power button has a mild adhesive to hold it to the phone, as does the headphone speaker. Peel them off and out of the phone.
8) remove the charging port board from the phone housing, that too has adhesive, peel up carefully and place aside. You'll need this outside and plugged into the board eventually as well.
On to Post #3.
9) TRICKY PARTS... I flipped the board over to expose the resistor KOBOL shows us to short. ** Picture is in the 1st download for 4.1.2 Bootloader ** I then plugged in the phone's LCD cable (the cable that comes out on the top right when viewed from behind; above where the volume rocker is) The motherboard should be flipped over exposing the resistor, the LCD cable is barely long enough to let the phone housing lie flat beside it, which you don't want. You'll want to prop the sceen vertical so you can see it when you do the next few steps. I used an external drive butted against the front of the screen that had rubber feet so it wouldn't slide and scotch tape.
10) Re-attach the power button/headphone speaker to the motherboard. Also plug in your prepared SD card.
11) Place the battery next to the battery terminals, swing the power button over on top of the battery. With one hand, you should be able to hold the motherboard from sliding while your holding both the battery to the terminals, and the power button to the battery. I did this with my left thumb to hold the motherboard from sliding, my left middle finger holding the battery against the contacts of the motherboard, and my left index finger to push the power button which is on top of the battery.
12) place your smallest precision screwdriver on the resister KOBOL shows you in the picture. Using a screwdriver with the other hand sure beats having to a) solder, good luck! KOBOL is a solder pro and I don't have any soldering irons with tips THAT small, and b) beats using a paper clip or something silly. The screwdriver shorts the resistor with minimal effort. Make sure you apply MILD pressure to the screwdriver to ensure your touching both sides of the resistor's contacts. My screwdriver was exactly the width of the resistor, don't be using grandpa's 1' long screwdriver on that motherboard.
13) READY?!?! OK!! with the resister shorted by the screwdriver in 1 hand, the battery held in place and the power button ready to be pressed in the other... start counting to 5 as soon as you feel the click of that tiny little button. Hold the power button; if you let go, you might slip and now the battery won't be supplying power to the phone, aka this operation will fail.
** Make sure you know how to count to 6 properly, none of this '123456' super-speed counting like we did playing hide and seek growing up. Listen to the tick of a clock if you can or start a timer somewhere. **
14) After counting to 5, remove the screwdriver, I'd suggest keeping the power button held, the phone won't turn off (just like booting the phone for real; holding it after the phone turns on, the phone still turns on right?) And it prevents the battery from disconnecting.
15) If you're lucky, you'll see some text on your screen saying SD something something in red and saying it wrote the file. I was way too excited that this worked and I forgot what it said to be honest. Pretty much it'll be the 1st thing your phone displays that isn't a boot-looping logo!
16) Go ahead and relax. Let the battery disconnect from the board. You can go ahead and semi-reassemble you're phone to test. I placed the board back in the phone housing, plugged in power button/headphone speaker, speaker phone/charing port & circuit, camera, etc... plugged in all wires/connectors, and make sure to put those 2 black screws back in before placing housing back on... (1 for speakerphone/charging port, one for the board)
Post #4
17) Power up your phone and you should be greeted with the "Verizon has detected..." blah blah unauthorized software. AWESOME AND CONGRATS! Pull the battery and boot to Download/ODIN mode.
** NOTE ** I have NO IDEA if you can downgrade during this process, no one in KOBOL's thread had yet to confirm as of this writing. Flash whatever you're coming from, you went this far to Un-brick your phone, why do it again? If you went to 4.3, deal with it and restore 4.3 Coming from 4.1.2? restore 4.1.2 then! Besides SafeStrapping is coming soon
18) Restore your phone with a working ODIN image, whether it be a stock keis image, your favorite ODIN image (root66 ODIN is great) etc. etc.
19) After the ODIN restore is complete, you may boot loop but this is normal, you need a factory reset. Pull battery, boot recovery, do a factory reset. You'll be OK now!
20) BASK IN THE GLORY OF YOUR RESTORED VERIZON GALAXY NOTE 2!
I'm sorry I don't have any of my own pictures, it was nerve-racking enough just to get through this and have enough hands to do it. Waking up my girlfriend so I can ask her "hold the battery just like this..." at 2 AM would have been a bad idea..
MANY, MANY, MAAAANY thanks to KOBOL for engineering this very clever recovery process... I would be out a phone right now or shopping online for JTAG devices. All the while be at work with no phone tomorrow and the next day while I wait for a replacement phone to arrive. To think I have insurance and most likely would have been fine to get a replacement (sent rooted & unlocked phones back several times no issues) I did this all so I wouldn't be without my phone for 36 hours!!
May this guide be helpful to even ONE PERSON... please give thanks, and more importantly, message KOBOL and ask him how to send a donation, I will be doing so myself!
Best of luck to all. :good:
Excellent DIY post! Thank you for sharing your experience and methods!
In your final comments are you mentioning this will also allow you to downgrade for those who did the 4.3 OTA update?
If someone would help me put setup my micro sd for the flash i would try a downgrade. I dont have a micro sd to sd adapter for my laptop.......
I tried this for a bout a 2 hours. I got a white screen a few times. Weird thing is I couldn't get it to boot and when I finally did I was able to boot into Odin mode only
Sent from my LG-VS980 using xda app-developers app
Were you attempting to downgrade? Once you got into ODIN, could you actually download ROMS?
iooooooc said:
Were you attempting to downgrade? Once you got into ODIN, could you actually download ROMS?
Click to expand...
Click to collapse
Yea I was attempting to downgrade. I noticed the resistor was broken so now I need to fix the resistor and try this again
Sent from my LG-VS980 using xda app-developers app
bigshotrob22 said:
Yea I was attempting to downgrade. I noticed the resistor was broken so now I need to fix the resistor and try this again
Sent from my LG-VS980 using xda app-developers app
Click to expand...
Click to collapse
Can't wait...took my phone apart last week and had the same reaction you did in KOBOL's original thread (this crap is WAY to small)...I am looking forward to see if this downgrade is possible. I will keep you posted if I get around to trying this method before you get the chance to fix that resistor...
iooooooc said:
Can't wait...took my phone apart last week and had the same reaction you did in KOBOL's original thread (this crap is WAY to small)...I am looking forward to see if this downgrade is possible. I will keep you posted if I get around to trying this method before you get the chance to fix that resistor...
Click to expand...
Click to collapse
Sounds good. I got a message to appear on the screen but right after the screen went crazy and that's when I noticed the resistor was broken.
Sent from my LG-VS980 using xda app-developers app
bigshotrob22 said:
Sounds good. I got a message to appear on the screen but right after the screen went crazy and that's when I noticed the resistor was broken.
Click to expand...
Click to collapse
Aww shucks, yea that puppy is really tiny so best of luck. When it's time to remove it you can nuke it real quick with a soldering iron and pull it off with tweezers. Pre-tin the new resistor and then blast it onto the board. that'll be pretty tricky.
FYI to those who continue onwards to fix their phones... do not short it while giving it power for more than 5 seconds. KOBOL mentioned that in his original post and I headed to it, it appears that resistor can be damaged so be careful. I guess after several hours of attempts it gave out. Best of luck, bigshotrob22.
OffTheChainz said:
Excellent DIY post! Thank you for sharing your experience and methods!
In your final comments are you mentioning this will also allow you to downgrade for those who did the 4.3 OTA update?
Click to expand...
Click to collapse
Thank you! I didn't mean to insinuate that a 4.3 downgrade could be possible with this method, more like I was mentioning people were contemplating doing it. If I was on the 4.3 bootloader I'd have tried it, I think this is more of a backdoor homebrew j-tag to restore. I'm interested to see if it can be done too!
Any tips on shorting this? I'm going to test this for a downgrade this weekend.
Sent from my RM-915_nam_usa_228 using Tapatalk
roflcoptersoisoi said:
Any tips on shorting this? I'm going to test this for a downgrade this weekend.
Sent from my RM-915_nam_usa_228 using Tapatalk
Click to expand...
Click to collapse
I plan on using a pair of fine tip tweezers...
Be careful!
roflcoptersoisoi said:
Any tips on shorting this? I'm going to test this for a downgrade this weekend.
Click to expand...
Click to collapse
iooooooc said:
I plan on using a pair of fine tip tweezers...
Click to expand...
Click to collapse
I had used a very small precision screwdriver, like one you would get in an eye glass kit. It worked just fine for me. You don't need to grab the sides of the resistor, there is enough metal on top of it to short it with a screwdriver. Just be careful, everyone.
I don't know how you'd get a new resistor on the board, that is a bit beyond my technical abilities. Maybe with a magnifying glass, a needle-tipped soldering iron and a very steady hand??
I have successfully unbricked two Sch-I605 by writing image to sd card . One I used a usb jig for 5 seconds the other by using three buttons to get in download mode I did not have to short resistor and those two were bricked.after screen said sdcard is loaded to emmc I pulled battery then reflashed with odin. One was on 4.3 the other was 4.12. Thanks to all involved for making this possible. I now have two working notes with unlocked bootloaders.
Sent from my SGH-T889 using Tapatalk
How did a jig work... doesn't USB jigs put you in download mode...
Sent from my SCH-I605 using Tapatalk
Same issue, different solutions? Unlocked 4.3??
jkiwitt said:
I have successfully unbricked two Sch-I605 by writing image to sd card . One I used a usb jig for 5 seconds the other by using three buttons to get in download mode I did not have to short resistor and those two were bricked.after screen said sdcard is loaded to emmc I pulled battery then reflashed with odin. One was on 4.3 the other was 4.12. Thanks to all involved for making this possible. I now have two working notes with unlocked bootloaders.
Sent from my SGH-T889 using Tapatalk
Click to expand...
Click to collapse
Please explain the conditions the phones were in a bit more, I'm curious as to how you did it without the resistor trick. I was able to boot my phone to download mode but I couldn't flash it with ODIN for PC because it would write fail. Perhaps I could have re-flashed the phone by using the SD only, no resistor shorting necessary?
I think the resistor shorting is for people who are truly F'ed and have no Download mode, booting etc. I would love to get more clarification on this. I'll append my original post/guide and leave out the entire disassembling process and just have the users use the SD image KOBOL provided.
There's a few scenarios I can imagine:
1) Bricked like I was, flashed right phone, but wrong carrier firmware. Download mode only, can't write anything to NAND, boot-looped constantly - SD Card re-image Only?
2) Bricked with NO use-able interface. Download mode is toast, no life from phone whatsoever. (Perhaps flashed not only wrong carrier bootloader like I did, maybe user flashed completely different phone firmware?!) - Resistor trick??
3) Bricked via flashing correct firmware that is somehow corrupted. ODIN froze mid-flash, cable unplugged accidentally, etc. - SD Card re-image Only?
I would like to verify the repairable condition of any bricked state so I can at least know exactly what to do to fix it. The opening line of my OP is "flashed wrong firmware now you're bootlooping?" but there are so many ways to make this happen that require different solutions.
Let me know about those 2 phones when you can, thanks. and WAIT A SEC... I just noticed your statement, "I now have two working notes with unlocked bootloaders." So did you unlock 4.3 with this method?!
Did my research, looks like a jig forces download mode yes? so I see 3 things happening...
1) you CAN access Download Mode manually with 3-button power up. No ODIN flashing can save you but the SD Card trick works. I did the resistor method anyways because I didn't try it with SD-Only. This is still a soft brick I guess, if it can be fixed via SD and not a teardown. Worked for me because I had correct phone, but improper carrier firmware so Download Mode still worked??
2) you CAN'T get to Download Mode so you use a jig which forces Download Mode. I'm assuming if Download Mode can't even be accessed pre-jig or pre-resistor attempt... how is the firmware capable of being re-written from SD?
3) you CAN'T access Download Mode and you don't have a jig, so you use the resistor technique. It sort of does what the jig does only forces it at the board level and requires a teardown.
Next time I F-up my phone, I'll try and restore it via SD-Only. Otherwise, we might be able to skip this resistor-technique and use a jig instead. More info on USB Jigs here
jkiwitt said:
I have successfully unbricked two Sch-I605 by writing image to sd card . One I used a usb jig for 5 seconds the other by using three buttons to get in download mode I did not have to short resistor and those two were bricked.after screen said sdcard is loaded to emmc I pulled battery then reflashed with odin. One was on 4.3 the other was 4.12. Thanks to all involved for making this possible. I now have two working notes with unlocked bootloaders.
Sent from my SGH-T889 using Tapatalk
Click to expand...
Click to collapse
Could you please clarify? I just attempted the three button method and was able to access download mode, but nothing will write from my SD card. Is there another step I need to do to get the .img to write once I am in download mode? I am attempting to downgrade from 4.3 to 4.1.2
Related
Alright, so I very stupidly got curious and took apart my x10.
After putting it back together (very carefully and precisely) when I turned the phone on the screen lights up in the background but briefly displays colored scan lines in random directions for about a second. I've taken it apart and put it back together multiple times to assure I've attached all the cables and wires.
The thing is that the phone works since my computer recognizes it (i can hear the USB charge sound), and I managed to maneuver my way into the notification area and enable USB Connect and was able to view the SD card contents on my computer.
What could possibly be wrong? I didn't damage anything while taking it apart since I was very careful, but the screen just doesn't display anything. I'm very confused.
It would be nice to be able to fix this with some opinions instead of bringing it in and paying $100 to fix it or sending it in and having to wait 2 months.
Thanks in advanced.
forum.xda-developers.com/showthread.php?t=668132
Maybe you can get some help here! Good luck!
Sent from my X10i using XDA App
Thanks for the link, I've posted in that thread also.
I'd still like to get some opinions in here tho.
So I dropped my viewsonic gtab on the floor accidentally and I when I picked it back up and tried to power on the device (since it was on before i dropped it) it would refuse to power back on. When I connect the charger the charging light does come on and another interesting thing when I connect the USB cable from my computer to the tablet windows 7 recognizes the device in device manager as "APX" with an exclamation mark.
My question is if I NVflash it will it work again (maybe this is the perfect opportunity to flash zyhongs honeycomb rom) .
UPDATE: I would like to add when i hold down volume down(-) and power button I dont see the screen flicker or anything is the screen damaged?(there are no cracks on screen) its funny b/c windows does see the device and the device plugin noise "occurs"
Thanks!
Good Luck and let us know what happens. I would guess that if the LCD is turning on it should work; otherwise a hardware problem.
I dropped mine too and it would not boot. It was late night so didn't do anything, the next day I noticed that the headphone jack was messed up. It still had the headphones plugged in and must have taken the full impact. I pulled the headphones out and then it booted ok but the sound was not working. 2 days later sound came back but the headphone jack is totally busted.
Will open it up next weekend and see if I can fix anything.
dropped gtab wont boot (APX mode)
Yea Ill post the results here Ill nvflash it later tonight most likely tomorrow morning. I think it looks fixable APX mode requires device to turn on. No crack seen, and if charge light comes on I think its a soft brick so I will reflash with custom recovery (CWM) and a custom rom (honeycomb rom for gtab) but if you find something let me know and also how to open the back cover of a gtab lol!
thanks
gtablet in apx mode installed drivers bat file issue
So I got the driver installed windows recognizes my tablet thanks to the recovery drivers i have every file in one folder the only problem that remains is when i run the bat file a error happens in which it says nvflash is not recognized I attached a screen-shot below
(UPDATE) new message after moving stock rom tapntap1.2 files in same folder
Ok so I decided to move all files into one folder including the image files ( of tapntapv1.2) which is what i should have done now when I run the bat file the result is a little better but its still producing errors I have a screenshot of the incident below :
Please Help
Thanks
new message when running "bat" file
Ok so after rerunning the bat file and rearranging files in NVFLASH folder i get this new message:
screenshot below:
techlawsam said:
Ok so after rerunning the bat file and rearranging files in NVFLASH folder i get this new message:
screenshot below:
Click to expand...
Click to collapse
Can not open the screnshot. Not sure what you are combining & rearranging. I recommend starting over by redownloading NVFlash (1.2 stock rom) w/cwm presinstalled from here. http://viewsonic-gtablet-for-dummies.webs.com/nvflash.htm . It extracts all in one directory...no rearranging required.
Al
dropped tablet, screen wont turn on (APX mode)
Oh sorry the most recent post i made with the screenshot was the only screenshot in the post what i meant by rearranging file were the img files and all the files for NVFLASH and NVFLASH_gtablet folders respectively. Ill try the website you gave me hopefully my screen isnt cracked ...
flashing tablet with NVflash produces same error
ok after using the website you gave me I still get the same error as I had before where it has an error copying over the image and bootloader
I have attached the screenshot
techlawsam said:
ok after using the website you gave me I still get the same error as I had before where it has an error copying over the image and bootloader
I have attached the screenshot
Click to expand...
Click to collapse
Appears NVflash is having a problems writing the BCT parition. BCT is very important. We'll look at some options, but first, lets digress for a minute. Still no video on the tab? Check this post http://forum.xda-developers.com/showthread.php?t=1202111 and report back if it helps you get video back.
dropped gtab , screen doesnt come on and is in APX mode
aabbondanza said:
Appears NVflash is having a problems writing the BCT parition. BCT is very important. We'll look at some options, but first, lets digress for a minute. Still no video on the tab? Check this post http://forum.xda-developers.com/showthread.php?t=1202111 and report back if it helps you get video back.
Click to expand...
Click to collapse
Ill most likely open it tommorow and will check it out thanks
Dropped Gtab , screen wont turn on, device in APX mode
So I have decided not open up my gtab for many reasons including the fact that I am not experienced enough and when I put everything back together and the device still doesn't work it wont be in condition to be returned or anything
Is there still another way software wise (i.e ADB , nvflash) does anyone know why screen wont turn on my device does turn on and APX mode is enabled?
techlawsam said:
So I have decided not open up my gtab for many reasons including the fact that I am not experienced enough and when I put everything back together and the device still doesn't work it wont be in condition to be returned or anything
Is there still another way software wise (i.e ADB , nvflash) does anyone know why screen wont turn on my device does turn on and APX mode is enabled?
Click to expand...
Click to collapse
More than likely your screen going out is related to one of 2 things. Either when you dropped it, the video cable came loose inside & just needs reseated or the drop damaged something on a chip level which would not be fixable by anything software.
honestly, opening your tablet up is not as hard as it seems. Just like people were saying before take 4 screws out and use a credit card to pop the case apart (there are 3 clips per side). I have opened my tablet many times during the installation of the internal gps module and it is really not too hard. I can say that the first time you open it, it is harder to get the clips to pop with a credit card. Just keep trying you will get it.
sorry i didnt post for a while school started up and also the fact i didnt want to put the effort things are winding down and Im thinking to do this for these two days. I think the hardest part for me is on how to remove those four rubber "Shoes" without ripping them in half really...and what type of screwdriver is needed to open the case up?
Thanks again
Alright i finally did my own reading removed the rubber pads and i removed the screws still haven't popped the case but i figured it will be super easy with a credit card. I am wondering the video cable is the cable to the right of the photo with the different color wires correct? So I should just unplug and plug it back in?
viewsonic gtab cover off
Screen Conenctor(s)
techlawsam said:
Alright i finally did my own reading removed the rubber pads and i removed the screws still haven't popped the case but i figured it will be super easy with a credit card. I am wondering the video cable is the cable to the right of the photo with the different color wires correct? So I should just unplug and plug it back in?
viewsonic gtab cover off
Click to expand...
Click to collapse
There are 2 connectors. One connects to the motherboard & the other connect to the screen. It could be either that needs reseatd. See the attached pdf.
View attachment 766810
Dang more surgery and opening :/ now I gotta be careful. What tool opens those screws(golden) at the outer perimeter of the board? I dont think a phillips or flathead would do the job maybe a "L-key" ?
All phillips in the photo
techlawsam said:
Dang more surgery and opening :/ now I gotta be careful. What tool opens those screws(golden) at the outer perimeter of the board? I dont think a phillips or flathead would do the job maybe a "L-key" ?
Click to expand...
Click to collapse
Unless they've changed something, all the ones in the photo are philips. Take a photo of what you see & attach it to a post
opened the case up and reseated coupler
ok opened it up, i found the coupler with the multicolored wires loose so i just pushed it out with a flat head gently and then pushed it back in the other coupler closest to it with the silver sheilding did not look like it moved and looked tight and secure i did not touch. I put the cover back on screws, pads pushed the power button(battery seems to die very quickly for some reason as well so connecting charger) and the device is still not turning on should I maybe push the reset button on the board?
hi all, i have a motorola razr the uk version on t-moblie and i had updated my phone to ics leaked version blur_version.651.167.26.xt910.retail.en.eu, and my headphone jack didnt work anymore but long story short i tired to go back to gingerbread so i could send my phone to get repaired, biggest mistake i made so far. but now it wont boot, i dont think theres a rom on there anymore, it stays on the big red M screen then goes black, i can get to recovery mode and ap fastboot but when i try to put a new rom on it says e:validation failure i think it has system at the front of that. i havent had a phone for 2 days now its driving me nuts. so is there anything i can do to fix this??? oh im a noob at this so dont understand much of it lol
thanks in advance
nemox92 said:
hi all, i have a motorola razr the uk version on t-moblie and i had updated my phone to ics leaked version blur_version.651.167.26.xt910.retail.en.eu, and my headphone jack didnt work anymore but long story short i tired to go back to gingerbread so i could send my phone to get repaired, biggest mistake i made so far. but now it wont boot, i dont think theres a rom on there anymore, it stays on the big red M screen then goes black, i can get to recovery mode and ap fastboot but when i try to put a new rom on it says e:validation failure i think it has system at the front of that. i havent had a phone for 2 days now its driving me nuts. so is there anything i can do to fix this??? oh im a noob at this so dont understand much of it lol
thanks in advance
Click to expand...
Click to collapse
Well, you're with your razr out of the charger 'bout 2 days now. You've probably a bricked device. [low battery. cannot program]
To flash an ICS rom (yes, you can't flash GB anymore) you'll need a factory cable.
Check dev section for an index thread and you'll find there all you need to put your razr working again.
If you have a phone jack defect you'll have to send it to motorola services. Just put the original system on it (ICS) send it and cross fingers. Most times it works.
Cheers
pedrotorresfilho said:
Well, you're with your razr out of the charger 'bout 2 days now. You've probably a bricked device. [low battery. cannot program]
To flash an ICS rom (yes, you can't flash GB anymore) you'll need a factory cable.
Check dev section for an index thread and you'll find there all you need to put your razr working again.
If you have a phone jack defect you'll have to send it to motorola services. Just put the original system on it (ICS) send it and cross fingers. Most times it works.
Cheers
Click to expand...
Click to collapse
i can charge it and from fastboot it says battery ok and ok to program, would you be able to put the link please? and thank you for replying
nemox92 said:
i can charge it and from fastboot it says battery ok and ok to program, would you be able to put the link please? and thank you for replying
Click to expand...
Click to collapse
Hi
You've all the files indexed here
http://forum.xda-developers.com/showthread.php?t=1840296
Sent from my XT910 using xda premium
I made an active cable by cutting off the rubber around the micro USB jack on my RAZR charging cable. I took out the transparent plastic over there (it was a pain, the wires inside are not to be damaged in an ideal situation). Then took out half of that metal piece that surrounds it, its made out of the parts - a longer one which you will have to bend and a shorter one that comes off.
After that i took a wire and cooked it on the RED wire on one end, and the free slot next to the white wire at the other end. Then I took another wire and cooked it on the metal piece at one end and the multi-wire coat inside the cable at the other end. It took me about two hours, being extra-careful and discovering what to do while doing it (theres not much room for maneuvering inside the micro usb jack). That took care of my empty battery.
First i disected an old usb cable, opened up the phone and charged it directly (black wire on the minus pin under the battery connector, and red wire on the plus pin under the battery connector). It used to work just fine until a failed flash.
I need to get the pictures off my phone, its 100% bricked. I took it into Sprint and they couldn't fix it. I can't turn it on, can't get into recovery, absolutely nothing. Please help!
Anyone?
scottmail said:
Anyone?
Click to expand...
Click to collapse
Im sorry but i think you're SOL, if the phone is in an unbootable state then there is no way of getting your pictures off it, just a friendly word of advice, either have all pictures save to the Micro SD or back it up (auto upload) using Google+/Dropbox Etc.
PhyscoAssassinx said:
Im sorry but i think you're SOL, if the phone is in an unbootable state then there is no way of getting your pictures off it, just a friendly word of advice, either have all pictures save to the Micro SD or back it up (auto upload) using Google+/Dropbox Etc.
Click to expand...
Click to collapse
Pretty much my thoughts on the matter, as well. Even if you can revive the phone via a process like Jtag, you'll most likely end up losing everything that's stored on the phone. You might try shooting a PM to XDA member Zarboz regarding the issue, as he has a Jtag RiffBox and is familiar with the process.
Also, I saw your other post regarding the phone dying on you. Have you tried charging the phone for an extended period of time? I've seen some wonky cases on here where the phone died and acted as though it were bricked, only to power back up after being charged for awhile.
Sent from my EVO using XDA Premium 4 mobile app
I ran into the same issue with a 2 month old Evo. Try this:
Pop off the upper back cover. Get a torx screwdriver, remove the screws holding on the opaque charcoal-colored cover that goes over the camera. using the edge of something not too sharp, gently push the left side of the grey cover to the right *GENTLY* to get the clip on the right side to release. Now, using that same tool, pry the grey cover from the bottom slightly. Be careful, as there's adhesive attached to the cover and camera lens. Now, once you've removed the grey cover, you'll see a wiring harness with 3 pairs of wires in the bottom right corner. use something to remove that harness very carefully - this is going to be an actual 'battery pull'. 10 seconds later, press the harness back into place *DO NOT FORCE IT*. Now, try powering the phone on.
This fixes my phone for however long as I leave that charcoal cover off of it. As soon as I put it back on, watching logcat I believe it's triggering a faulty thermal sensor which there isn't a fix for. I was able to pull all my wife's stuff off her phone as well as factory reset it before I send it off to HTC>
Edit: Fixed! Well, temporarily. I've ordered a new power button to replace the sticking one. Until then, I've managed to unstick it for now.
While I'm fairly sure it's dead dead, I figured I'd ask here before giving up.
Background: Best Buy refurbished AT&T i717 with Beanstalk 4.4 flashed. It worked amazingly after switching from 4.2 to 4.4, but one day it froze and restarted into a bootloop. If left alone, it shows the Samsung logo and then goes to a black screen. If plugged in, it vibrates several times, shows the charge indicator momentarily, and then starts vibrating again. It will boot into download mode, but restarts itself after 3 seconds. It will not boot into recovery no matter how I try.
So first question: Is there anything I can do to revive it? I'm making due with a worn out Captivate Glide right now, but I'd like my Note back.
Second question if not: Are there any cool projects I can reuse the parts of my Note on?
If you can get into download mode I'd try hooking it up to a windows machine with Kies installed. Do an emergency recovery and bring it back to stock. If that doesn't work, idk. You will probably need your serial number though.
Sent from my SAMSUNG-SGH-I717 using Tapatalk
bryanizmir said:
If you can get into download mode I'd try hooking it up to a windows machine with Kies installed. Do an emergency recovery and bring it back to stock. If that doesn't work, idk. You will probably need your serial number though.
Sent from my SAMSUNG-SGH-I717 using Tapatalk
Click to expand...
Click to collapse
The device auto reboots after 3 seconds when I get it into download mode. Otherwise, I would have already tried that. Unfortunately, I don't have the device's original serial number either, as the refurbisher didn't think that was important to note on their sticker.
fox689 said:
The device auto reboots after 3 seconds when I get it into download mode. Otherwise, I would have already tried that. Unfortunately, I don't have the device's original serial number either, as the refurbisher didn't think that was important to note on their sticker.
Click to expand...
Click to collapse
The serial number will be under the battery.....sounds as if maybe your power button is sticking.
Sent from my SGH-I717 using xda app-developers app
dparrothead1 said:
The serial number will be under the battery.....sounds as if maybe your power button is sticking.
Sent from my SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
That sticker no longer exists. It was removed and replaced by the refurbisher. Also, normal boot does not cycle. It just hangs. I have to remove the battery and replace it to get the device to show the Samsung logo again. I've also removed the bezel/back that covers the mainboard of the device to check the power button. It doesn't seem to stick.
Can I get a stuck power button? Stuck power button anybody?
Even though it may sound or even feel ok, you could have a stuck power button. Flick the back of your phone a few times and see if it helps. Then go to Best Buy and say "WHAT THE [email protected]#K"
Sent from my SAMSUNG-SGH-I527 using xda app-developers app
captemo said:
Can I get a stuck power button? Stuck power button anybody?
Even though it may sound or even feel ok, you could have a stuck power button. Flick the back of your phone a few times and see if it helps. Then go to Best Buy and say "WHAT THE [email protected]#K"
Sent from my SAMSUNG-SGH-I527 using xda app-developers app
Click to expand...
Click to collapse
Well, my 2 year replacement plan ran out a month ago. This was my second refurb for various hardware failures (first the audio port, and then the USB) I had to switch out the USB board on this one just a few weeks ago actually, thanks to the design flaw of it being on the bottom, but it ran just fine afterward until now. Is there a way to bypass the power button, short of removing it, that I can use to test?
fox689 said:
Well, my 2 year replacement plan ran out a month ago. This was my second refurb for various hardware failures (first the audio port, and then the USB) I had to switch out the USB board on this one just a few weeks ago actually, thanks to the design flaw of it being on the bottom, but it ran just fine afterward until now. Is there a way to bypass the power button, short of removing it, that I can use to test?
Click to expand...
Click to collapse
Only 2nd replacement? My wife and I both have the 717 with BB warranty, I've gone thru 4 she went thru 5 of them. So chances are you got one of.ours She's getting a S5 on Friday, but I can't find a suitable alternative for this beast yet waiting for the lg g pro 2 if it ever comes out. Sorry I went off topic
Sent from my SAMSUNG-SGH-I717 using Tapatalk
bryanizmir said:
Only 2nd replacement? My wife and I both have the 717 with BB warranty, I've gone thru 4 she went thru 5 of them. So chances are you got one of.ours She's getting a S5 on Friday, but I can't find a suitable alternative for this beast yet waiting for the lg g pro 2 if it ever comes out. Sorry I went off topic
Sent from my SAMSUNG-SGH-I717 using Tapatalk
Click to expand...
Click to collapse
I'm pretty easy on my phones, physically. When I did a trade in on my HTC Inspire to buy the Note, the BB employee was in complete shock that I'd carried it daily for nearly 1 1/2 years.
I'm actually looking forward to the Note 4 this fall. Lots of good buzz coming from side channels. Although, I've started considering settling for the S5 or Note 3 now that my Note is dead.
Looking at the contacts, the power and volume buttons are thru hole soldered about 6mm apart... $3 on ebay for a replacement button. I might try my luck with my soldering iron. If that doesn't work, I'll start looking for ways to put this big screen to use in some DIY projects.
Ok, thanks everyone for the suggestions! I took the board off and attempted to unsolder the contacts. No go, need to buy a high temp soldering iron. BUT, I mashed the button really hard with a screw driver and it seems to have (temporarily) fixed the button. I've ordered a new button and it should be here soon. Hoping this temp fix keeps until.
fox689 said:
Ok, thanks everyone for the suggestions! I took the board off and attempted to unsolder the contacts. No go, need to buy a high temp soldering iron. BUT, I mashed the button really hard with a screw driver and it seems to have (temporarily) fixed the button. I've ordered a new button and it should be here soon. Hoping this temp fix keeps until.
Click to expand...
Click to collapse
You are braver than I. Many just take some alcohol and a qtip to clean connection, but obviously you are a bit on the mad scientist side. I can only imagine your phone looks a little frankenstein ish.
Sent from my SAMSUNG-SGH-I527 using xda app-developers app