<del>So I have been searching the forums for a couple hours trying to solve this problem
I flashed cyanogen 4.0.3 tonight and got my phone hung up at the g1 screen
i can get into the bootloader but not recovery...i followed the instructions to install adb but since my computer won't even detect the phone when it is plugged in i can't seem to use that to get to recovery
I am betting there is a simple solution to this but all of the solutions i have found thus far have involved using adb
I am sorry if this has come up alot and i fully understand the frustration of having to see an endless sea of the same question but i am honestly stuck</del>
Never mind I got it working
Related
Hey guys its been a while since I've even tried to fix my phone cause everyone was saying its dead. But I've been reading stories of people coming back from the G1 logo. So i could really use your help.
Heres the problem, A while back I dropped my old G1 and had to get a new one. Upon looking for the video I used last time to root my phone, I couldn't find it. I searched high and low but to no avail. I figured any video would work as long as it rooted me. So I started up the video. however once i was "done" with it i noticed nothing had changed. So i figured the video was garbage and found another one and started it up. I know, STUPID. Well when i booted my phone after wiping and flashing. It stayed on the G1 logo. I knew the worst had happened. So now i don't know what to do. There have been one or two occasions that I've gotten it to boot loader. So i know i can get there. but what do i do when I get it?
Also, no, I never got to flashing raido's or anything like that. I thought I wasn't rooted so i didn't move on.
I know it was long but I'm getting all the info out there. Please help, I think its possible, and if it is I want my phone back!!!
What were you installing by the way?
EDIT: Made a mistake, thought you were able to boot into recovery.
He does not get to recovery, but into bootloader mode (cam + power on). This is good, as there is a good chance to recover from that.
Try the first section of this guide:
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod
You have to flash the correct dreamimg.nbh via bootloader. You might need a Goldcard to do so, in certain countries, but lets just hope that is not the case (would be more work...)
€: Some more Info on Bricking your device with Radio/SPL updates, so take care: http://forum.xda-developers.com/showthread.php?t=655097
The guide on cyanogens wiki is considered dangerous at the optional update to HardSPL
Hi everyone,
I have in the past switched roms on my Galaxy S before, therefore the issue of bricking my phone is something that doesn't intimidate me too much. However, this time i'm really stumped, and I turn to the gurus here at the forums, hoping a solution can be found.
I had just gotten my phone back from getting its screen repaired (which makes this especially irritating), and my carriers had flashed my phone back to their stock version of android, meaning gingerbread with a lot of bloatware. I decided straight away that I wanted to root my phone today, although I was away from my PC. I had my laptop with me (Macbook Air), but I had never done any flashing from it before, not to mention ever using Heimdall before (I had always flashed with Odin). I downloaded everything, and then I made my first mistake: I flashed a speed mod kernel (I believe it was a froyo kernel), and after reboot my phone wouldn't go past the splash screen. I could still get into recovery and download mode. Then I decided to try playing it safe, and I downloaded stock firmware packages for Heimdall fro the forums here. I tried flashing JVS on my phone, going exactly by the instructions written in that same thread that I found the packages, but the flash didn't succeed. Instead, I got an error message saying the PIT file didn't reach the end of the transfer (or something like that...) and the phone rebooted. After that attempt, the phone went black. Nothing works anymore except for download mode. Now I thought that as long as download mode works, I'll be ok, so I tried flashing different packages through Heimdall, and eventually when I got home I tried using Odin on my PC. The problem is, my PC doesn't recognize my phone anymore (even though the drivers are installed and I never had an issue with that before), so I'm pretty much stuck with a brick for now.
I really don't want to go back to my carrier again, and hope to get my phone back in working order without paying too much. I still think there's hope as long as download mode works.
Does anybody have any suggestions what I might be able to do? Since my PC doesn't recognize my phone (and therefore Odin doesn't either), the only semi-working option left is using Heimdall somehow, but as to how to use it, I'm in the dark.
I would really appreciate any help you guys can give me. Thanks a lot!
Aaron
first try reinstalling the drivers and try again. if you can get download mode, should be repaired.
Thank you very much!!!
I knew that download mode was a good sign, but I started freaking out as soon as Odin wouldn't recognize my phone, since it never has had that problem. Reinstalling the drivers did the trick, and flashing worked.
Sometimes the simplest solution is the best. Again, thanks a lot!
commandozzz said:
Thank you very much!!!
I knew that download mode was a good sign, but I started freaking out as soon as Odin wouldn't recognize my phone, since it never has had that problem. Reinstalling the drivers did the trick, and flashing worked.
Sometimes the simplest solution is the best. Again, thanks a lot!
Click to expand...
Click to collapse
We are here to help.
OK folks, I know some of you are going to jump straight down my throat, but please, back off and stick to the friendly forums that this used to be where anyone would help anyone.
the story so far is that I once loved my Nexus One, I've had it since launch, I have ran Cynogen Mod 7 for a couple of years, I have had MUI roms running, I have played with various kernels, updated radio, upgraded hardware, all was going wonderfully.
the one thing I could never get was full SU!! Heck knows why!!
I then started getting random problems and downloaded the original google frf83 software and flashed the phone via update.zip using amon-ra recovery.
I thought all was well after this, as my phone received 3 OTA updates and now my phone is on...
Android 2.3.6
Baseband 32.41.00.32U_5.08.00.04
Kernel 2.6.35.7-59465-g42bad32 ([email protected] #1)
Build GRK394
I noticed that in the Status (settings) it was displaying my old sim card number, which is not the number for the sim in the phone now. his I thought was odd and that something had gone wrong.
So as most of us would do, I went to boot AmonRa recovery and it wasnt available, it had been overwritten with the default recovery; ok lets just ADB and reflash it, I hadnt used ADB for a couple of years because I did everything through AmonRa's awesome recovery!!
So off I go, install the SDK, all the appropriate packs including the USB driver, just like I did when I originally flashed the phone with the recovery image!
But an old problem came back that I hadnt even been bothered about because I always put stuff on SDcard via a card reader!!
I have had consistent problems with my nexus one for some time now in regards to the USB drivers, no matter what I do the phone will not install and I believe it could be some conflict in the device.
I am running Vista Ultimate (fully registered) and no matter what I do I cannot get the Nexus One to install. It will only display as unknown device, which is absolutely useless.
I have browsed every post and tried everything I have found, and yet nothing is working. I have used devmgmt, I have tried the roll backs, I have tried to install every driver available to get it working. I have uninstalled the device, updated drivers after fresh install attempts, I have even formatted my laptop thinking it may have had a corrupt OS and bought Vista Ultimate.
I am not a complete noob and I have been around these forums for some years, but I never thought I would have to cry out like a 4ucking Noob with such a seemingly simple problem, but it is not simple, I have done everything I can possibly find!!
I must get the USB working in order to get the recovery back, I can access my phones default recovery but it will not work when trying various roms as update.zip!!
I have tried the terminal commands on the phone to install the recovery.img but I do not have SU access and the phone point blank refuses.
I have attempted to change and remove the recovery files reffered that are causing the revert to default recovery, but shock.. I cannot delete because of insufficient permissions. I cannot ADB because the USB driver refuses to install.
So if I cannot change the files due to permissions, I cannot ADB because of USB, I cannot get to Ra's recovery because of bootfiles, I cannot use default recovery to update.zip... I am absolutely losing my mind and I'm going nuts browsing the forums for the second week running, yes I am now on day 12 of trying to fix this problem and at a complete loss...
Can someone please help??
I will even allow remote access to pc because I am that desperate to resurrect my beloved Nexus One.
I also have a Galaxy I9000 without 3 button download mode but that is an entirely different story!!
Please just someone, come to an oldskoolers rescue, and yes PAYMENT will be given to the knight in shiny armour!!
You could try on another computer which doesn't run Vista
tommert38 said:
You could try on another computer which doesn't run Vista
Click to expand...
Click to collapse
Or just use fastboot instead of adb...
His Nexus One isn't recognized by the computer, so that won't help unfortunately. Also, I've never heard of build GRK394..
tommert38 said:
His Nexus One isn't recognized by the computer, so that won't help unfortunately. Also, I've never heard of build GRK394..
Click to expand...
Click to collapse
Install the drivers for fastboot already Jeez and then read How to use android for dummies.
hi everybody,
I'm stuck!
I' tried everything I can think of, I've search hi and lo and I cant find a fix for my problem. My phone for the last several months has been working flawlessly with twrp/trickdroid but since there dosen't seem to be any more support for trick droid I decided to put another rom on the phone. Now I've never had an issue doing things this way but something is screwed up and I could use someone who is smarter than me help. I wiped the phone and now I cant get my phone and pc to communicate. Everytime I try to adb sideload i get an error stating device not found. twrp recovery is still on the phone and i can still boot into the boot loader if needed. I just cant put my new rom on the phone. I've done everything i can think of, searched everywhere i think possible. this isn't my first android that iv modded but it is the first time i haven't been able to find a solution for my problem. please help!
Run a ruu exe
Sent from my HTC One using Tapatalk
Hi XDA community,
I'm scared out of my mind. Tried rooting for the first time ever, but don't actually know what I'm doing. Using various guides I found in these forums, I:
1. Used HTCdev to unlock the bootloader
2. Used ADB to install TWRP 3.0.2-0
3. Used TWRP to install UPDATE-SuperSU-v2.76.zip
Once that finished, my phone tried booting up (the white HTC logo) but now it has the red development build text at the bottom.... and then it gets into an infinite boot loop.
I don't know how to fix my phone. Please someone here with guidance, please help.
I've got the same identical issue.
I was able to get out of the boot loop by holding volume up and power, and I got back to download mode. From there, since the SU update I tried to install boot looped me (I was following this tutorial), I jumped ahead and just installed cm13 as I was planning to.
This install went fine, but then I ran into the issue of the rom not recognizing my sim card. I've been researching this problem and I guess I need to update my baseband? I tried for hours but I do not know how to accomplish this, and couldn't figure it out for the life of me. This thread on the cyanongenmod forum seemed to be the closest thing to help I could find, but still it didn't help very much.
So at this point now I'm trying to back out and unroot my phone and get everything back to factory settings; it doesn't feel worth it anymore to me since I've just had trouble every step of the way. I've been trying to follow this post to get back to at least a usable factory rom. But I can't even get this one to install because I cannot access my phone through adb while it's in download mode. Furthermore the instructions are just confusing me because I'm not so versed in the nomenclature of these procedures.
Is there anyone that can help me get back to complete stock t-mobile sense? Or if not, help me get my cm13 rom to recognize my sim card so I can at least have my phone working in some capacity? I'd be tremendously grateful of either. I'm really in over my head here and quite scared I won't be able to figure this out.