Hello.
I have been browsing the forums here and doing searched and reading some helpful information but long story short....
I have managed to soft brick my G1. I can power the phone on but I am frozen at the Tmobile G1 splash screen. I do not have a card reader and I have no idea how to use the adb.
Can anyone simply the method of resolving this issue? I would greatly appreciate it and would be forever in your debt.
-Thank you
well, it sound like you may have a little more than a soft brick...
try starting it while holding down HOME. this should boot into recovery. if it does not, then it sould like you have a real brick. i did that to a g1 once, it involved flashing *danger spl*.
if you do indeed have a real brick, there is some hope, but not much. search around the g1 forum for the jtag threads. there are some people working on it, and it sounds like someone may have figured it out, but it's a VERY technical solution requiring taking the phone apart and attaching it to your computer via a special cable.
good luck
if you're in need of a replacement phone, i've found craigslist to be an excellent resource. i've bought 2 phones on there in the last week. a cliq for $100 and a mytouch 1.0 for $85 both in VERY good condition.
Thanks for the reply. I've already been browsing around craigslist hah.
Going to do some much reading, reading and more reading then writing up a good plan before I try this again if at all.
I jumped in with both feet without the necessary research and it bit me in the ass .
Related
So my HTC VZ6900 (Vogue) was acting up two days ago and I could tell it was a software issue and has not done any real research on the device till yesterday! Here is my story...
HTC started acting up while at school on Monday and was not doing great. I tried a soft reset but nothing worked... Booo. I tried removing the battery and waiting a few minutes and it took an entire 90 minutes + to get past the WM 6.0 screen! Once it got to the today screen the touch feature was none responsive so I could not really access anything. Soft keys worked. Couldn't get anything and the phone would not connect to the network.
Tuesday morning I took it to the Verizon store before I went to work. I had brought my old phone because I was not sure what was wrong. I personally thought it was a software problem, and figured that if that was the case Verizon would hard reset the phone or at least give me a replacement. Wrong. The clown at the desk took my phone and word for word quotes here: "Ah, yeah this thing is dead you’re going to have to get a new phone. Oh! Wait you have insurance you can pay $50 and they will give you a replacement."
I am a studying to get a PHD in electrical engineering and my gut told me this was not the case... So I said no thank you to the insurance and ask him to switch my phone to my old phone that being my old envy which still works perfect. When I went to leave they tried to take my HTC touch to which I protested and they complied. To work I go...
Well it was a quiet day so I had lots of free time and decided to Google VZ6900 problems, after about 10 minutes of searching I came across XDA-Developers! Did a little searching and saw that some people had similar problems. Figured out how to hard reset my phone (This was not a problem all of my contacts were saved to windows live!). Phone resets and it’s like brand new. I had seen these ideas of Custom ROM's and decided to do a little reading. After about 20 minutes I decided that it would not be hard to upgrade my ROM, loaded coke loader and followed the Verizon directions, 20 minutes later BAM running WM6.5 custom ROM. Hm I began to wonder, will Verizon be so nice as to activate this for me? I know they love to lock everything down so that they will get paid. I walk back to the store at 430 and proceed to wait 25 minutes to talk to a different person. I was explaining that their Tech earlier had told me the phone was broken beyond repair and that in fact he had just been lazy and refused to even attempt to fix the phone. They did not like this one bit. They told me I would have reset to the original Verizon settings. Though what he intended was that I needed to run the Verizon ROM with its own customization. So I asked the guy if he could get the other Tech who had helped me earlier to come into the conversation and he was somewhat upset at this time, but complied.
"Hey your back, oh wow this is the new Windows Mobile Cool!"
"Yeah I spent the better part of the day fixing my phone, now switch my phone back"
"Um... I do not know if I am supposed to do that. Um."
"Remember this morning when you told me to file an insurance claim for a broken phone?"
"Yeah, don’t have to do that anymore but I cannot activate an unlocked phone"
"Yes but telling me to file an insurance claim for a broken phone when it was not actually broken is insurance fraud"
"Oh... well we are not supposed to do this but I'll make an exception"
Two minutes later that had it all up and running and I was out the door without any problems.
Thanks to everyone who has contributed to the information I used, it saved me a great deal of time!
I have had my treo 750 for only 4 years or so, lately it's been freezing up while texting, it also takes a while for the time to adjust when I wake up the screen, and finally the screen, once in a while, will go squirrelly after a soft reset, kinda diagonal?? You can still make out the picture but it's seriously distorted. I've spent a couple late nights on here trying to download different things but I am a little overwhelmed. I'm lost amid hard spl's, and rom's.
I didn't realize how attached to this phone I have become and I cant afford another smart phone right now.
If someone could point me in the right direction, I would be so grateful. If it means the phone is dead, so be it. I hate to give up on it. Please advise, and thanks, what an interesting site.
Can anyone advise me if this phone is done or worth working on?
Hello XDA forum! I am new here but I have enjoyed reading through many of the great posts you have available. I have a problem and I'm hoping you can help me. I'm learning quite a bit about the android OS and dabble in some minor tablet repairs but I still consider myself a noob, especially after reading some of the more technical posts! I have a couple of tablets here that are locked up after too many pattern attempts and I'd like to do a factory reset, but I just can't seem to get them into recovery mode. All the normal keystrokes yield no results. For example:
Tablet 1 is a 7" Noria by Chromo that identifies by my computer MID-X15. It's recognized in device manager as being installed with correct drivers. To the best of my knowledge USB debugging is not activated as I have tried both Multi Tools and platform-tools adb, while the device is not shown on either program. I have also tried numerous different key combinations from a powered-down state (vol - & vol + with power, just vol + and power, just vol - and power, and repeatedly pressing different combinations both at and before the manufacturer splash screen). The internet has proven to be less than helpful as I'm on my 3rd hour of forum surfing. I have never flashed a tablet before and I'm not precisely sure if can be done without USB debugging on or without being able to access the system. I am perfectly willing to purchase a TF card and attempt the process but there's not a ton of information about this relatively obscure little tablet.
Tablet 2 is a Klu by Kurtis. It is also a 7" tablet and I have the same problems with the USB debugging being off. On this device I can get into the screen with the android on his back with the red exclamation mark, but the recovery console never starts. Numerous hours of surfing and countless attempts at alternate keystrokes have also yielded no results.
If someone would be so kind as to offer a few suggestions or point me in the correct direction I would seriously appreciate it. Thank you so much!
(close to) 24 hour bump. Hopefully someone may have a suggestion for me. Thanks in advance!
One more bump. Anyone?
Unfortunately, after researching both tabs, I have found that neither tablet is very good quality.
Chromo Noria - This is a very well-known tablet to be problematic for no reason at all, and once this problem occurs, nobody has discovered how to retrieve the system.
Curtis KLU - This also is not the greatest tablet ever. Fortunately, I've found this thread for you to take a look at - it contains instructions on how to boot ClockworkMod.
Hope this helps.
Thank you for the link, thenookieforlife3! I will read over that and give it a shot. I realize these tablets are virtually worthless. It's one reason I don't mind experimenting on them with some more aggressive techniques if any exist. The biggest problem is just getting into the darn things to do anything (aggressive or not, lol). Perhaps something in that thread will give me a technique I can use.
I'm still open for other suggestions as well. These are throw-aways so I'm willing to get creative. I'm wishing there were jumpers or, heck, a couple traces i could short out with a screwdriver to force it back to a factory setting, lol.
[email protected] said:
Thank you for the link, thenookieforlife3! I will read over that and give it a shot. I realize these tablets are virtually worthless. It's one reason I don't mind experimenting on them with some more aggressive techniques if any exist. The biggest problem is just getting into the darn things to do anything (aggressive or not, lol). Perhaps something in that thread will give me a technique I can use.
I'm still open for other suggestions as well. These are throw-aways so I'm willing to get creative. I'm wishing there were jumpers or, heck, a couple traces i could short out with a screwdriver to force it back to a factory setting, lol.
Click to expand...
Click to collapse
I can see that. It's always fun to be aggressive every once in a while.
Don't we all wish that there was a hardware method to factory restore our devices? :laugh:
Am I right?
I too have been tinkering with a chromo noria 7" tablet in my spare time, as my son got one of these last christmas and its been stuck in a boot loop for no reason for almost six months now. Today I decided to play and discovered that adb could see it while it was boot looping and tried adb reboot recovery command and to my surprise it booted the recovery menu. That being said, does anyone know what I can flash from there cuz a wipe/factory reset does not fix the loop. Any advice would be happily welcome and im sorry if I'm posting wrong in any way. Hope at least my findings are helpful.
Sent from my Moto G using XDA Free mobile app
Hi,
I realize many of you will state this has been asked before but I really can't find a fix for the phone so I thought maybe it's best to ask my own question and describe the issue.
So I work in a small company dealing with recycled mobile phones. I've been there about a year and a half, I had no training as it was just me and another guy, so it was just google and a lot of help from this site, so thanks guys for all the great help as I've got most of my answers from previously asked questions. I'm not a complete noob, but still have lots to learn.
This question I will keep related to the Moto G. So in my company we managed to pick up around 20 Moto G XT-1032. However around 6 of them seem to have software issues, after a factory reset (after testing) 6 got stuck on a boot loop. So I searched around and found 'http://forum.xda-developers.com/showthread.php?t=2542219' which I followed and managed to flash the software back to 4.3, I had issues on an XP computer but after trying with a windows 7 it seemed to work and the phone booted up. The 6 which got stuck in a boot loop had previously been factory reset as I could see it was at the factory set-up when I turned them on. So I was quite confused why 6 would get stuck.
So today I actually finally figured out to move to a windows 7 laptop which allowed me to actually flash the phones. After flashing the phone back to 4.3 I tested the phone and all seemed fine, so as these are to be sold I had to factory reset them again (resetting through the standard settings, no special code). So once again they all seemed to get stuck in a bootloop, but instead of an actual bootloop it shows the Motorola logo and then the screen goes black but I can see the backlight is still on, then it just sits there as long as I leave it, over 4 hours so far.
I have attempted a second flash on one of the phones and it's done the same. I'm downloading UK firmware for the xt1032 not the dual sim version. I've held the power button for 120 seconds as someone mentioned that on some random thread. Managed to get to restart and got into the android bios thingy (not sure what it's actually called, hopefully you'll understand what I mean) and attempted a factory reset but it just gets stuck on the black screen (still can see the backlight is on).
I'm now out of ideas, I really don't know what else to try. I'd really appreciate if someone could shine some light on this and what could possibly be causing the issues. The phones look brand new and are known as '14 day returns' meaning someone has returned it from new after 14 days, they are then fully tested by the manufacturer before being sold to companies like ourselves. If it was one phone I'd suspect maybe a hardware issue but because it's 6 I'm just thinking this would be a strange coincidence.
I'd be interested to hear from anyone who could give me advice on, unlocking, flashing and anything else which could help me at my place of work. I work with Sony's, HTC's, Lumia's, Samsung's and Motorola's, and also every now and again ZTE and Huawei's. So feel free to contact me if you think you could offer me any advice, all is welcome.
Thanks for reading, and thanks in advance to any advice.
Chris
kimber015 said:
Hi,
I realize many of you will state this has been asked before but I really can't find a fix for the phone so I thought maybe it's best to ask my own question and describe the issue.
So I work in a small company dealing with recycled mobile phones. I've been there about a year and a half, I had no training as it was just me and another guy, so it was just google and a lot of help from this site, so thanks guys for all the great help as I've got most of my answers from previously asked questions. I'm not a complete noob, but still have lots to learn.
This question I will keep related to the Moto G. So in my company we managed to pick up around 20 Moto G XT-1032. However around 6 of them seem to have software issues, after a factory reset (after testing) 6 got stuck on a boot loop. So I searched around and found 'http://forum.xda-developers.com/showthread.php?t=2542219' which I followed and managed to flash the software back to 4.3, I had issues on an XP computer but after trying with a windows 7 it seemed to work and the phone booted up. The 6 which got stuck in a boot loop had previously been factory reset as I could see it was at the factory set-up when I turned them on. So I was quite confused why 6 would get stuck.
So today I actually finally figured out to move to a windows 7 laptop which allowed me to actually flash the phones. After flashing the phone back to 4.3 I tested the phone and all seemed fine, so as these are to be sold I had to factory reset them again (resetting through the standard settings, no special code). So once again they all seemed to get stuck in a bootloop, but instead of an actual bootloop it shows the Motorola logo and then the screen goes black but I can see the backlight is still on, then it just sits there as long as I leave it, over 4 hours so far.
I have attempted a second flash on one of the phones and it's done the same. I'm downloading UK firmware for the xt1032 not the dual sim version. I've held the power button for 120 seconds as someone mentioned that on some random thread. Managed to get to restart and got into the android bios thingy (not sure what it's actually called, hopefully you'll understand what I mean) and attempted a factory reset but it just gets stuck on the black screen (still can see the backlight is on).
I'm now out of ideas, I really don't know what else to try. I'd really appreciate if someone could shine some light on this and what could possibly be causing the issues. The phones look brand new and are known as '14 day returns' meaning someone has returned it from new after 14 days, they are then fully tested by the manufacturer before being sold to companies like ourselves. If it was one phone I'd suspect maybe a hardware issue but because it's 6 I'm just thinking this would be a strange coincidence.
I'd be interested to hear from anyone who could give me advice on, unlocking, flashing and anything else which could help me at my place of work. I work with Sony's, HTC's, Lumia's, Samsung's and Motorola's, and also every now and again ZTE and Huawei's. So feel free to contact me if you think you could offer me any advice, all is welcome.
Thanks for reading, and thanks in advance to any advice.
Chris
Click to expand...
Click to collapse
Before I start: DISCLAIMER: I DO NOT TAKE ANY RESPONSIBILITY FOR YOUR ACTIONS BY FOLLOWING MY INSTRUCTIONS. YOU ARE FULLY RESPONSIBLE FOR YOUR ACTIONS.
Now we got that out of the way...
Try upgrading to 4.4.2: http://sbf.droid-developers.org/phone.php?device=14 (Get the firmware here)
Use the thread you mentioned: http://forum.xda-developers.com/showthread.php?t=2542219
hi everyone,
im really new to xda so im not sure if this is where i should be posting this but hopefully someone can still help me out..?
well i bought this verizon s3 off ebay about a month or so ago- refurbished for a fairly cheap price, and it was running fine the whole time. then one of my friends told me about custom ROMs and how easy it was to get. He told me to root my device and he would do the rest. After about an hour i got root access through saferoot and was quite pleased with myself. I didnt give it to him yet, and i havent installed any ROMs myself either (A couple days went by waiting for his response) when suddenly my device started lagging quite a lot. I just quickly closed my apps and pressed restart, and now i cant turn it on!
Apparently i couldve bricked it? i know i potentially voided the warranty but it was past a year already. i dont understand how it couldve happened, nothing happened during the rooting process- everything went very smooth. So what can i do now? Is it bricked? How can i unbrick it? Is it the battery? the screen? the power button? It doesnt boot AT ALL. no vibration, but the red LED lights up when plugged into the computer WHEN THE BATTERY IS OUT.
Im really at a loss here so any information would be greatly appreciated. Thanks.
evobug666- long time apple user (not too pleased with android so far...):fingers-crossed: