Database Develop

[Q] Galaxy tab nighmare :s

Hi guys.
I kinda mad a big mistake. I have a galaxy tab p1000 and mistakenly flashed a firmware which belongs to p1010. Yeah silly!!!!!! The flash was successful but it totally killed the tab. It will not boot at all no power whatsoever. I left it in the charger for like two hours nothing
is there hope?? Or did that firmware do damage to the tab?? Can i repair it myself or does it need to go to be revived at samsung. Or i hung myself???
Help please.

Have you tried booting into download mode? Once you do, flash it back to stock. You can find stock ware in the dev section. Doubt its truly bricked.
Sent from my SGH-T849 using XDA App

Yeah i have tried the two button combo. Power button and volume down but i get no response. I duno wsup. I cant get power on the damn thing??? Cant get into download mode : s

Try what was done in this post...it seems that even though the screen was blank, he was actually in download mode, and able to flash.
http://forum.xda-developers.com/showthread.php?t=949794&highlight=download+mode

Yeah i have read the post and tried but my tab is not coming on at all. It isnt recognized in odin. Just lying there like a brick. If i can get it going somehow????
Sent from my GT-P1000 using XDA App

mngarogore said:
Yeah i have read the post and tried but my tab is not coming on at all. It isnt recognized in odin. Just lying there like a brick. If i can get it going somehow????
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
Just curious...
If you just bricked your tab, why does your Signature show that you're using a GT-P1000 to post?

Well i am lucky to have 2 tabs and galaxy s. Imma a samsung fanboy/man. And it pains me to know i might have bricked one tab. If u will be so kind n give me a solution??
Sent from my GT-I9000 using XDA Premium App

Thinking that your battery has been ran out.
Just left it to charge for 4-5 hours and try again.
Bricking the device isn't such easy. I made unbelieveble things with my tabs but got it to work again. But I also stucked to that battery thing.

Did you flash the bootloader as well? If you did and the bootloader goes out to lunch, then the Oden/Heimdall tools won't be of much use. In such a case you might be able to find some instruction on how to use a JTAG module to fix the tab. Though, taking the device apart is probably not a trivial thing.

I flashed the tab with firmware from the p1010 tab and mines p1000. So im assuming it erased everything. How much can a service repair cost??Cause if there is no option apart from jtag. I have to to send it in!!!!!
As i cant get any response whatsoever. Left it overnight charging, plugged it into the comp restarting stuff. Tried tricking it by plugging galaxy s and tab at the same time. But nothing.?????

[Q] Bricked my phone. Help please

Downloaded decrappified 1.1. Computer has a bad usb port and i think it disconnected before it was finished downloading. At this point the phone became stuck in cwm, so I erased user data and reset settings. The phone then said i had a bad sim card, but two replacements didnt fix it. I bypassed the sim card with up, down, search, home and the decrappified seemed to have flashed, but the phone now resets itself every 30 seconds or so.
I'd like to at least get this phone back to stock so i can take it in. been using my wifes old purple curve for the last 2 months. Any help would be appreciated. Thanks.

nesta111 said:
Downloaded decrappified 1.1. Computer has a bad usb port and i think it disconnected before it was finished downloading. At this point the phone became stuck in cwm, so I erased user data and reset settings. The phone then said i had a bad sim card, but two replacements didnt fix it. I bypassed the sim card with up, down, search, home and the decrappified seemed to have flashed, but the phone now resets itself every 30 seconds or so.
I'd like to at least get this phone back to stock so i can take it in. been using my wifes old purple curve for the last 2 months. Any help would be appreciated. Thanks.
Click to expand...
Click to collapse
My wife told me if I bricked my phone, I would have to go back to using the Cricket Wireless phone we had. YUCK. "Again" she says as she is reading over my shoulder. Anyhow.... stay calm, all is fine. In the forums there is a way to fix it. The phone is unbrickable. LG thought of everything. So diagnose the issue, and look in the forums. You will probably need ADB and stock programming, you can search our forums for ADB and you should track it all down. If you run into issues you can go to IRC the channel we have there is #lgrevolution and someone might be there to help you. It took Cubed 5 minutes to fix my phone, but it took 5 hours for him to come on IRC. I will try to dig up somethings. But you will need ADB so go get that.

Yeah, that blackberry is one hell of a leap backwards, nevermind the comments i get for carrying a purple phone. Even the wife likes to poke fun.
Ive been looking through the archives some and not sure what route to go, not farmiliar with ADB but i'll start looking into that.

nesta111 said:
Yeah, that blackberry is one hell of a leap backwards, nevermind the comments i get for carrying a purple phone. Even the wife likes to poke fun.
Ive been looking through the archives some and not sure what route to go, not farmiliar with ADB but i'll start looking into that.
Click to expand...
Click to collapse
Decrappified is a Froyo Rom, the Revo is now on Gingerbread. Either restore your back up, or download and install GingerVolt Rom.

mtmichaelson said:
Decrappified is a Froyo Rom, the Revo is now on Gingerbread. Either restore your back up, or download and install GingerVolt Rom.
Click to expand...
Click to collapse
If you didn't make a back up, there is a nandroid in the the development section. When did you get your phone? How long ago did you root it? Do you have Froyo or Gingerbread? If you had Ginger, of course Mt is right, you would do the Gingervolt. But you gotta take it back to your stock to get rid of decrap. Most of your answers will be in the Development section of our forums.

I didn't make a back up, so that isn't an option. I rooted and then broke the phone 2 to 3 months ago, i am not sure if that was before gingerbread or not. I guess i'll search the development section for answers on getting back to stock.

markapowell said:
My wife told me if I bricked my phone, I would have to go back to using the Cricket Wireless phone we had. YUCK. "Again" she says as she is reading over my shoulder. Anyhow.... stay calm, all is fine. In the forums there is a way to fix it. The phone is unbrickable. LG thought of everything. So diagnose the issue, and look in the forums. You will probably need ADB and stock programming, you can search our forums for ADB and you should track it all down. If you run into issues you can go to IRC the channel we have there is #lgrevolution and someone might be there to help you. It took Cubed 5 minutes to fix my phone, but it took 5 hours for him to come on IRC. I will try to dig up somethings. But you will need ADB so go get that.
Click to expand...
Click to collapse
I disagree. I Hard Bricked my Revo. Won't get into details as it's not important and I managed to find a local seller via Craigslist for same day replacement.
What happened is a flash occurred that should've failed, but didn't. The power button would no longer function and the 'failsafe' usb, no battery recovery method would not even work either. I would get a quick response when pulling the battery with USB plugged in, but then it would fail beyond that. Have since then destroyed the board due to some very private files located on internal board that were 'in transition' and couldn't chance being recovered by other parties for security purposes. I do, however, have a nice parts phone, such as screen, body, and battery cover.
Anyhow, moral to the story.. YES, the Revo CAN BE BRICKED!
-Cybie

Cybie257 said:
Anyhow, moral to the story.. YES, the Revo CAN BE BRICKED!
-Cybie
Click to expand...
Click to collapse
Nicely done! Now help this poor guy fix his. ; )
Also, if it was closer to 3 months ago then it was going to be froyo, right? Find the v4 stock and flash that. I'd link the thread but I'm on my Revo. : /

I found a rooted stock rom posted by thecubed, currently downloading that to my sd card. Anyone see a problem using that? Also found some tot files for stock. I think i had ver 6, but my phone wont let me check. Does it make a difference which one I use if i go that route?

nesta111 said:
I found a rooted stock rom posted by thecubed, currently downloading that to my sd card. Anyone see a problem using that? Also found some tot files for stock. I think i had ver 6, but my phone wont let me check. Does it make a difference which one I use if i go that route?
Click to expand...
Click to collapse
You are nit making this easy, lol. You should have the v6 version. I would go to the tot file. Also you would have had froyo, but after a month it should have updated to ginger bread. So go get the v6, then I would check phone status and see if there is an update. majority of us got the gingerbread update, if you don't there isinfo on how to do it. If you do, there is the one click tool kit that will get your phone rocked out.
Sent from my VS910 4G using xda premium

Cybie257 said:
I disagree. I Hard Bricked my Revo. Won't get into details as it's not important and I managed to find a local seller via Craigslist for same day replacement.
What happened is a flash occurred that should've failed, but didn't. The power button would no longer function and the 'failsafe' usb, no battery recovery method would not even work either. I would get a quick response when pulling the battery with USB plugged in, but then it would fail beyond that. Have since then destroyed the board due to some very private files located on internal board that were 'in transition' and couldn't chance being recovered by other parties for security purposes. I do, however, have a nice parts phone, such as screen, body, and battery cover.
Anyhow, moral to the story.. YES, the Revo CAN BE BRICKED!
-Cybie
Click to expand...
Click to collapse
Bull****!!! I tried absolutely everything to try and brick this phone in order to get a replacement and I was able to recover every single time... what did you do.. I got to know in case this phone sucks also???

drt054 said:
Bull****!!! I tried absolutely everything to try and brick this phone in order to get a replacement and I was able to recover every single time... what did you do.. I got to know in case this phone sucks also???
Click to expand...
Click to collapse
Jeez, I know, I just took him at his word, no need to fight over it. Lol. When cubed told me it was unbrickable he said he did everything possible too, and the secret to fixing it was dependent on how the phone acted, what lights were on, what the screen did, because each one had its own fix. I had a mismatch md5 and it said in the instructions don't turn off your phone. I did and caused it to brick. But there was a section in our forum to fix that brick. And with cubes help and mt laughing at me,we got it fixed.
Sent from my VS910 4G using xda premium

This whole situation was answered by mt. Just flash a gingerbread ROM either the stock v7 or gingervolt And you're good to go.
Sent from my VS910 4G using xda premium

Beamer9408 said:
This whole situation was answered by mt. Just flash a gingerbread ROM either the stock v7 or gingervolt And you're good to go.
Sent from my VS910 4G using xda premium
Click to expand...
Click to collapse
Got it unrooted and back to stock! The phone still resets itself every minute or so. Not sure if that is because I manually forced it past the sim card setup screen. Anyway, at least I can now take it into verizon. Thanks all for the help.

Glad to hear you're making progress. You may still want to go the ADB route and put zv6 on. I understand getting the Over The Air push upgrade to zv7 will then get you the upgraded radio. I haven't heard any other method for getting the radio.
I found my own noob way to brick a Revo, not in a good way.
Sent from my VS910 4G using Tapatalk

Bait-Fish said:
Glad to hear you're making progress. You may still want to go the ADB route and put zv6 on. I understand getting the Over The Air push upgrade to zv7 will then get you the upgraded radio. I haven't heard any other method for getting the radio.
I found my own noob way to brick a Revo, not in a good way.
Sent from my VS910 4G using Tapatalk
Click to expand...
Click to collapse
That kind of makes no sense flash the v7 tot it will get you to gingerbread get rid of your reboot issue. Also I wouldn't take the phone to Verizon unless you don't have cwm recovery in your phone cause more than likely they are going to try And factory reset your phone which will then boot into cwm recovery. Either way you're going the long way about fixing that phone.
Sent from my VS910 4G using xda premium

Old posts like these (below) lead me to believe the radio is only OTA. Of course it's old info and things may have changed. I didn't follow the TOT thread/s as closely since my phone behaved and did the OTAs fine. Realized I forgot there was a radio update on zv6. That's partly why I was paying attention to mentions of radio upgrades and it was taking a while to get root for zv6.
http://forum.xda-developers.com/showpost.php?p=18947155&postcount=1111
mtmichaelson said:
The radio is not inside the boot.img. It is stored in a different partition, and lg has done a fine job of covering it up, so it is difficult to tell.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=18843721&postcount=91
mtmichaelson said:
My roms already had the update except for the updated radio and boot.img (kernel & ramdisk). I will update the boot.img in the roms, but lg has covered up the radio mount point, so the radio may have to be updated through the actual update.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=18907274&postcount=25
drt054 said:
Only other option will be to downgrade or ugrade using LGNPST. Or wait, one of the other Members is attempting to get the v7. Tot file then can just use LGNPST to upgrade.. or MTMichaelson will be posting Gingervolt some time today which will have everything except new radio.. that you need to flash through LGNPST or the OTA update.. the radio that is along with the firmware.
Click to expand...
Click to collapse
Edit: Realize re-reading I need to clarify. My POV was just regarding his method and maintaining all features, not the reboot issue per se.

Right the tot is everything...sorry wasn't trying to be a **** might be how it came out though.
Sent from my VS910 4G using xda premium

No problem
Sent from my VS910 4G using Tapatalk

mtmichaelson said:
Decrappified is a Froyo Rom, the Revo is now on Gingerbread. Either restore your back up, or download and install GingerVolt Rom.
Click to expand...
Click to collapse
yep, that was all it took. I downloaded gingervolt and the reboot problem went away. Hopefully a new sim card will get it back up and running. Thanks again for everyones help.

[Q] Phone bricked?

hey guys i searched and havent really found anything that matched quite what i had going on so here we go... I was 95 percent through flashing the ICS rom it got through the hboot section and rebooted.. on the screen i saw two arrows in circular form above a phone .. and something was definitely being downloaded.. then the phone went black, doesnt go into hboot, doesnt a charging light when plugged in , but is picked up by the computer, ie. connection noise. Im in no way a noob at flashing roms , but something is definitely wrong with my phone.. Any ideas? It was charged full battery by the way.. it does glow in a dull light when i push volume down and power, or power alone...

Your phone indeed seems to be bricked. The identification noise from the computer may just mean that your USB is receiving power from the battery.
When my friend had a similar problem with his Amaze, he went to the HTC service center and they replaced his phone after keeping it for 4 days

So taking it to bestbuy to get it serviced is probably the only alternative, since its insured through them... lol just my luck

I brick mines as well. If you love your device stay away ics for now .
Sent from my Galaxy Nexus using xda premium

Dxtra said:
I brick mines as well. If you love your device stay away ics for now .
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
That's not fair to say. There's plenty of users that flashed without bricking their devices.
I followed the alternate directions here and had no issues.

Dxtra...I was able to do it no problems...saying to stay away is not at all accurate unless u cannot fully comprehend the instructions...never tell ppl to shy away from improvements because u urself did not succeed just offer warning...it is the linux way
Sent from my HTC PH39100 using XDA

meatwad0222 said:
Dxtra...I was able to do it no problems...saying to stay away is not at all accurate unless u cannot fully comprehend the instructions...never tell ppl to shy away from improvements because u urself did not succeed just offer warning...it is the linux way
Sent from my HTC PH39100 using XDA
Click to expand...
Click to collapse
I'm not the only one with a brick device, there's plenty more on here. Our phone is a pretty expensive device if you got the money and you want to take the risk go ahead. Why would I tell anyone to flash when is not safe to.
Sent from my Galaxy Nexus using xda premium

Dxtra said:
I'm not the only one with a brick device, there's plenty more on here. Our phone is a pretty expensive device if you got the money and you want to take the risk go ahead. Why would I tell anyone to flash when is not safe to.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Not sure why you keep posting it's not safe. I think I've seen like 3 people who've screwed it up out of probably 100+ installs. PirateGhost has released an ICS RUU which is completely noob proof so even unrooted users can get some ICS love before the OTA update.

As far as im concerned each one of us is responsible for what happens to our phones, warnings are put for a reason.. ive jailbroken, rooted the hardest of phones .. it was just my time for the inevitable to happen. I get my phone back in three days and you can be sure ill be back here again doing crazy rooty stuff to my phone no rom or dev should be held responsible for what ive done ..
Sent from my MB860 using Tapatalk

dusty2422 said:
Not sure why you keep posting it's not safe. I think I've seen like 3 people who've screwed it up out of probably 100+ installs. PirateGhost has released an ICS RUU which is completely noob proof so even unrooted users can get some ICS love before the OTA update.
Click to expand...
Click to collapse
Saying something is noob proof will inevitably prove that some where some noob will sow its not noob proof. I'll admit there were a few moments of panic when I flashed the zip method pg released. When that happened I just breathed deep and took my time and everything worked great in the end. I personally feel that what the devs have put out there is fairly safe as long as the directions are followed exactly.
Sent from my HTC PH39100 using xda premium

Dxtra said:
I'm not the only one with a brick device, there's plenty more on here. Our phone is a pretty expensive device if you got the money and you want to take the risk go ahead. Why would I tell anyone to flash when is not safe to.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I don't have the money to buy tons of new devices....its about knowing ur own limitations...do not criticise a devs hard work when it is proven to work...no its defenitly not idiot proof but it is very easy...I've done it to 3 phones already with no problems...the devs are not responsible for bricked phones
Sent from my HTC PH39100 using XDA

yea i must say it was a hundreed percent my fault in bricking my device so im not mad at anyone..and as far as the money goes its not a super big deal..i always make more o and btw im gonna be getting my replacement today and im gonna try this all again aft6er reading everything again and again and agian o and again lol

So, the phone is bricked. I have the same problem as the OP. I Lost access to Hboot while flashing ICS. I accidently sent it to recovery after Hboot update...and it never recovered LOL. Anyone know a good de-bricking service or know how much it will cost if I send it back to HTC or AT&t to fix it? I bought mine at the AT&T store, so no protection plan. I'm gonna get another device anyway (from Best Buy this time), but it would be great to have the Vivid back as a backup.

I bricked my phone Sunday night, still not 100% sure what I did wrong but it did what yours is doing now. I simply called the AT&T exchange by mail and used the factory warranty. Granted I guess there is a slight chance they could find out it was rooted (if they can somehow get it to recover or even turn on) but it got me a replacement... Food for thought.
Btw I got the new one and used the RUU and it worked seamlessly.
Sent from my HTC PH39100 using xda premium

bsSkunkApe said:
So, the phone is bricked. I have the same problem as the OP. I Lost access to Hboot while flashing ICS. I accidently sent it to recovery after Hboot update...and it never recovered LOL. Anyone know a good de-bricking service or know how much it will cost if I send it back to HTC or AT&t to fix it? I bought mine at the AT&T store, so no protection plan. I'm gonna get another device anyway (from Best Buy this time), but it would be great to have the Vivid back as a backup.
Click to expand...
Click to collapse
I did the same thing, selected recovery right after successful HBoot update. Then afterwards, each and every restart shows searching sd card with a black background. After several attempts of pulling battery, reinsert and power button + vol down, I was able to get back into HBoot. From there I immediately flash recovery through fastboot and now am happily on ICS.
If you did the same and phone boots up with the searching sd screen, there is a shot of bring it back.

dizzyraider said:
I did the same thing, selected recovery right after successful HBoot update. Then afterwards, each and every restart shows searching sd card with a black background. After several attempts of pulling battery, reinsert and power button + vol down, I was able to get back into HBoot. From there I immediately flash recovery through fastboot and now am happily on ICS.
If you did the same and phone boots up with the searching sd screen, there is a shot of bring it back.
Click to expand...
Click to collapse
Fraid it doesn't search for anything. I posted in the threads and tried everything I could think of and everything that was suggested. Though there isn't much you can do besides keep removing the battery and trying vol dn + pwr. Just a black screen.
Just a few things I tried (removed battery each time)- vol down + power (no sd card in) = blank black screen
vol down + power (with sd card and PH39IMG file) = blank black screen
vol down + power > boots to blank black screen, wait few seconds > press power button (like I'm going to fastboot) > plug into computer > type fastboot command into command prompt = command prompt says waiting for device
I always read the directions and threads a bunch of times before doing anything. Did lots of reading, google-ing, and searching. Fraid it bit the dust. I appreciate the help though. This is the first device snafu I've had. I've never had to send a phone in for any kind of warrantee work before. Hence my question above about getting it fixed.
Just in case, if it were to boot to that screen, what would I want to do? Just the PH39IMG? Or is there some other procedure?

Dxtra said:
Why would I tell anyone to flash when is not safe to.
Click to expand...
Click to collapse
Who TOLD you to flash the phone??? When I got my first android phone, a Samsung Fascinate, I LOVED the phone but nervous AS HELL that I would brick the phone. And I read, and read, and REREAD, trying to make sure I understood everything so that when I went looking for help, I at least could say, "Yes, I already tried this, this, and this".
I think the key thing to all of this is in two-fold - one, as someone stated before, this is a developer's forum. If you work on your car, and forgot to put oil in it, are you going to blame your mechanic? If you change your brakes and did not do something correctly, causing an accident, are you going to blame the car manufacturer??? Two, it states in MANY places, before you post, READ, READ, READ. It was actually ADVISED to NOT FLASH this ROM...
From this point forward, it almost seems as if there needs to be a waiver release to download roms, stating you will not ridicule nor torment the developers. And though I had heard about it but never seen it before, as I am on my 4th Android phone, there definitely are a few VERY NOTICEABLE disrespectful and ungrateful individuals in this forum. If you were my kid, and acted like that to me for something I GAVE YOU, I would do the same as PG - TAKE IT WAY and forget you.

Is my Captivate bricked?

I trying loading using Odin but it got stuck at "Setting up connection"
I then restarted PC and did it again and this time it went 2 more steps and then the screen became completely GREEN
Then I did the whole exercise again and now the screen became PINK
Now I am not even able to get into DOWNLOAD MODE...and neither do I see [mobile]![PC] icons.
Nothing happens. Is my phone now really bricked?
Please help! I am now worried about this

If the phone shows signs of life then its not bricked.

Also please don't create multiple threads on the same problem. It just clutters the forums even more.

I think I do not see any signs. It does not show anything on the screen even after trying download mode or recover mode. Powering on the phone also does nothing. I even kept the phone on charging the whole night but during the charging I did not see the usual green battery animation.
Is there anything left? Looks like I literally destroyed my working phone running 2.2. just by trying to upgrade it to 2.3 through Kies and then later using Odin.
I am very disappointed that how poor Samsung support is that a mere upgrade attempt destroys the phone. I had bought this phone 18 months ago by paying 540 $ and I now see it go down the drain

You can attempt contacting samsung if it was messed up with Kies but doubt they would do anything. But Kies is crap anyways. You can how ever attempt (or pay someone) to apply Unbrickable Mod (Adam Outler or MobileTechVideos.com)

there is one last thing you can try.
start odin on pc
take battery out of phone
put battery in
hold both volume buttons
plug USB cord in from pc to phone
if odin box turns yellow press start to flash a firmware!
it very rarely happens that you can do this but if you can, congratulations.

What odin u using ?

prbassplayer said:
You can attempt contacting samsung if it was messed up with Kies but doubt they would do anything. But Kies is crap anyways. You can how ever attempt (or pay someone) to apply Unbrickable Mod (Adam Outler or MobileTechVideos.com)
Click to expand...
Click to collapse
Thanks for the reply.
Will the "jig" hack work? My phone is totally unresponsive. No matter what I press nothing displays on the phone.

devangxda said:
Thanks for the reply.
Will the "jig" hack work? My phone is totally unresponsive. No matter what I press nothing displays on the phone.
Click to expand...
Click to collapse
Doubtful but no harm in trying
Sent from my ICS powered Captivate using Tapatalk

rkkaranrk said:
What odin u using ?
Click to expand...
Click to collapse
I897UCKK4 Odin One Click - Stock, CONTAINS Bootloaders, Re-partition, Full Wipe mentioned by XDA member 4-2ndtwin.
Am i left with just JTAG as the only hope?

devangxda said:
I897UCKK4 Odin One Click - Stock, CONTAINS Bootloaders, Re-partition, Full Wipe mentioned by XDA member 4-2ndtwin.
Am i left with just JTAG as the only hope?
Click to expand...
Click to collapse
UBM is better.

prbassplayer said:
UBM is better.
Click to expand...
Click to collapse
UMB..watching the videos looks like i will need some hardware hacker to fix it. Do you suggest a hardware novice should try it or leave it to the professional?

devangxda said:
UMB..watching the videos looks like i will need some hardware hacker to fix it. Do you suggest a hardware novice should try it or leave it to the professional?
Click to expand...
Click to collapse
You need decent soldering skills, else pay a professional.
Sent from my ICS powered Captivate using Tapatalk

I contacted Adam and he has agreed to offer his expert services. Now the problem is that I am in India and I can ship it to US but it will cost me dearly when he ships back because of the Indian custom rules. They will tread my repaired phone as a new one and add 15% duty costing me more than original phone cost.
So I am thinking of sending it through my friend who is visiting US later this month. However, I was looking around and found this link.
http://forum.xda-developers.com/showthread.php?t=1000175
Do you think this is something I should try? I already have good Arduino UNO toolkit.

devangxda said:
I contacted Adam and he has agreed to offer his expert services. Now the problem is that I am in India and I can ship it to US but it will cost me dearly when he ships back because of the Indian custom rules. They will tread my repaired phone as a new one and add 15% duty costing me more than original phone cost.
So I am thinking of sending it through my friend who is visiting US later this month. However, I was looking around and found this link.
http://forum.xda-developers.com/showthread.php?t=1000175
Do you think this is something I should try? I already have good Arduino UNO toolkit.
Click to expand...
Click to collapse
What you should know is Jtaging requires you to solder 6 very small spots vs UBM is 2 spots (I believe) and UBM will make your phone umbrickable. You could find a tech near you live that's good with a solder gun? Adam has a thread explaining the method.
Sent from my ICS powered Captivate using Tapatalk

Have you tried to force the phone into downloading mode using adb?
Using Doc's Master ROM v7: Cappy edition

KangKilla said:
Have you tried to force the phone into downloading mode using adb?
Using Doc's Master ROM v7: Cappy edition
Click to expand...
Click to collapse
No. I have not.
(a) How can it be done. I already have the Android SDK installed on my PC.
(b) My phone is totally non-responsive...it is totally blank black screen. Will adb work?

Adb requires phone on or in recovery
Sent from my ICS powered Captivate

they say it cant happen

well, i read all the time how nexus devices are unbrickable and maybe (hopefully) im wrong! so i been running stock rom rooted for a few days actually since yesterday i flashed back to stock and rooted only and flashed cwm recovery thats it. today (actually just a little while ago) i was messing around and was running antutu benchmark with stock then i flashed franco r53 kernel using his auto flash method in his app. no sooner that i started the test in antutu phone went completely black. will not respond to anything. so i said well maybe i can connect usb and get it to go into fastboot so i got lucky (or so i thought) soon as i plugged it in i saw red light at the bottom and battery charging icon. so i press power and volume down and was able to get into fastboot, i was kinda happy about this. i flashed back to stock wiped everything first wipe boot wipe cache wipe recovery wipe system flash bootloader reboot bootloader and flashed the system img and boot img and all that went thru succesfully. but it still will not boot it goes in and out red light battery icon google image. so i tried again flash stock images locked bootloader and fastboot reboot nothing i unplug usb goes straight black screen and wont respond. plug back in get red light and battery icon in and out back and forth between icon and black screen with red light. so i know allot of people get complacent in thinking that because you have a nexus you cannot brick but it is possible to brick this phone. or maybe someone can tell me im wrong. lol anyways just posting this here for people to think twice and not get so comfortable thinking you cannot brick a nexus. tommorow ill take the phone to t-mobile and get another one. and no i wont tell them it was my fault! (< for that one guy) lol good night!

I read lot about "antutu benchmark" as it's bad for Nexus 4 and cause this problem!.
hope somebody can help you out.

maddoggin said:
well, i read all the time how nexus devices are unbrickable and maybe (hopefully) im wrong! so i been running stock rom rooted for a few days actually since yesterday i flashed back to stock and rooted only and flashed cwm recovery thats it. today (actually just a little while ago) i was messing around and was running antutu benchmark with stock then i flashed franco r53 kernel using his auto flash method in his app. no sooner that i started the test in antutu phone went completely black. will not respond to anything. so i said well maybe i can connect usb and get it to go into fastboot so i got lucky (or so i thought) soon as i plugged it in i saw red light at the bottom and battery charging icon. so i press power and volume down and was able to get into fastboot, i was kinda happy about this. i flashed back to stock wiped everything first wipe boot wipe cache wipe recovery wipe system flash bootloader reboot bootloader and flashed the system img and boot img and all that went thru succesfully. but it still will not boot it goes in and out red light battery icon google image. so i tried again flash stock images locked bootloader and fastboot reboot nothing i unplug usb goes straight black screen and wont respond. plug back in get red light and battery icon in and out back and forth between icon and black screen with red light. so i know allot of people get complacent in thinking that because you have a nexus you cannot brick but it is possible to brick this phone. or maybe someone can tell me im wrong. lol anyways just posting this here for people to think twice and not get so comfortable thinking you cannot brick a nexus. tommorow ill take the phone to t-mobile and get another one. and no i wont tell them it was my fault! (< for that one guy) lol good night!
Click to expand...
Click to collapse
If it's easy to take back do it. However couple of folks have got it fixed by opening the backplate and disconnecting/reconnecting battery terminals.
Almost 90%+ people having this issue were running Antutu.

Why would you think its a good idea to flash a custom kernel on to stock?

There are tons of threads about this, do some searching your phone is not bricked, also to the poster above me there is nothing wrong with flashing a custom kernel over stock.
Sent from my Nexus 4

http://forum.xda-developers.com/showthread.php?t=2128392

XxSilent22xX said:
There are tons of threads about this, do some searching your phone is not bricked, also to the poster above me there is nothing wrong with flashing a custom kernel over stock.
Sent from my Nexus 4
Click to expand...
Click to collapse
Actually that is incorrect, it is not okay. Most Devs will post comparable kernels, or flash your own kernel on to this rom at your own risk on every rom thread op. Stock only supports its own kernel, so while some kernels might work as a stock replacement kernel, it is never a good idea to flash a custom kernel on to a stock rom unless the Dev says otherwise.

This for the help. I'll try this tomorrow morning. Of course I tab a search bit could not find the threads. I hit red light and it took me to legacy phone. I type brick in search fort n4 and nothing. So I never saw those threads about this issue. So thanks. And ive never had a problem with running custom kernels on stock ROM. Never! Lol
Any ways thanks for help! Can moderator close this thread please! Thanks!
Sent from my Galaxy Nexus using xda premium

And then u guys say that a removable back cover is not a deal breaker
There are a lot of times when u need to reset the phone by taking the battery out
Sent from my GT-N7000 using xda app-developers app

Franco R53 is fine on stock - running it here with minimal other changes (I.e. root + email security policy hack)
I've updated every Franco kernel and all seen OK. Perhaps the benchmark related hardware failure is worth looking closely at.
FWIW, if you're back to stock, lock the bootloader and send it back as it sounds hardware to me.
Daern
Sent from my Nexus 4 using Tapatalk 2

synergeticink said:
Actually that is incorrect, it is not okay. Most Devs will post comparable kernels, or flash your own kernel on to this rom at your own risk on every rom thread op. Stock only supports its own kernel, so while some kernels might work as a stock replacement kernel, it is never a good idea to flash a custom kernel on to a stock rom unless the Dev says otherwise.
Click to expand...
Click to collapse
:sigh: No. Franco says his kernel supports the stock ROM. In fact, stock is the standard to test a kernel on. Unless a ROM is created with very specific additions that rely on a custom ramdisk to function, there is nothing wrong with it. Even then, it's not really wrong, you'll just have some missing features.

Charge your phone?
Im pretty sure you get the red light if your device has not enough power to display the screen.. Put your phone on charge through the main plug

qazibasit said:
And then u guys say that a removable back cover is not a deal breaker
There are a lot of times when u need to reset the phone by taking the battery out
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
So true man so true!
Sent from my Galaxy Nexus using xda premium

This happened to me, except I was bone stock. You need to hold down all 3 buttons at the same time; several times, and then try to get into the bootloader. That's what worked for me. Once you're in the bootloader you can flash the stock image(s) via fastboot.

qazibasit said:
And then u guys say that a removable back cover is not a deal breaker
There are a lot of times when u need to reset the phone by taking the battery out
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Holding down the power button for five seconds is the equivalent to pulling the battery, is it not? That is how it has been on other devices with non-removable batteries.
Sent from my Nexus 4

OniV2 said:
Holding down the power button for five seconds is the equivalent to pulling the battery, is it not? That is how it has been on other devices with non-removable batteries.
Sent from my Nexus 4
Click to expand...
Click to collapse
if this is true then why do i need to pull the phone apart and disconnect the battery and reconnect? apparently this is a known issue and has happened to others and taking phone apart and disconnecting battery and rconnecting it fixes the issue. unfortunately i dont have the right tools to do this so i will be taking my phone to t-mobile this morning. thanks for all the help guys. really appreaciate all the responses i got.

At times the power button wont work. In some cases of soft bricks. I have this issue since i had HD2.
Sent from my GT-N7000 using xda app-developers app

estallings15 said:
:sigh: No. Franco says his kernel supports the stock ROM. In fact, stock is the standard to test a kernel on. Unless a ROM is created with very specific additions that rely on a custom ramdisk to function, there is nothing wrong with it. Even then, it's not really wrong, you'll just have some missing features.
Click to expand...
Click to collapse
That's exactly what I said in my last post. Next time the op needs to clarify if the custom kernel supports stock. But regardless I was correct.

OniV2 said:
Holding down the power button for five seconds is the equivalent to pulling the battery, is it not? That is how it has been on other devices with non-removable batteries.
Sent from my Nexus 4
Click to expand...
Click to collapse
The service manual says ten seconds but yes it fully cuts power from the battery.

So sitting in my car waiting for t mobile store to open I decide to plug phone in to car charger since I know this will be first thing t mobile does and lo and behold phone booted up and start working. Battery drained to 0 and charging now. Go figure
Sent from my Nexus 4 using xda premium