Related
Hello everyone,
Ok so I bought a brand new g2 on craigslist. Everything was working perfectly fine...until I decided to root it. I downloaded the necessary files and it all worked perfectly fine. Now I know some of you may bash me for this but thats not the reason im asking for help. I know I messed up by not reading more into depth ahead of time. I opened up visionary did the temproot, then proceeded to do the permroot. Phone rebooted but stayed stuck in the HTC logo screen. I seriously need help guys and I would greatly appreciate it if I could just make it work again. I went into the bootloader restored back to factory settings but same thing happens. I managed to get a copy of the original 2.2 stock rom for the g2 put it in the sd card then it seems like it updates fine..restarts a couple of times but stays in the htc logo again after like the second restart. I have the S-on...(prolly screwed). Anyway, im asking here because I searched a lot and I know there are other posts about people who ask this but then there are no concrete answers. I am wondering if there really is a way to fix it. Whether it be installing a custom rom or any other thing. If its not fixable as much as it hurts, Im going to have to put it up for sale and get at least something out of it (for parts or whatever). Any help is greatly appreciated. Thanks Guys
I will give gou 10 dollars! But hey do a search for visionary bootloop fix. There was a great guide on how to fix that. It will require you to learn about adb. Adb will be your friend for fixing things.
Sent from my HTC Vision using XDA App
lol
lol about the 10$...hey I greatly appreciate your help though...
Man, I just noticed there are lots of people stuck in this HTC logo screen. Having a hard time installing the damn adb......ahhhh this crap really sucks and its all my fault....hopefully there is someone out there who had the exact same problem and got it working.
ADB is quite easy to install actually, all you need to do is download the Android SDK, get the usb drivers, modifiy the inf files in the usb_drivers folder, and you're good to go.
As for rooting, I would suggest using the more updated gfree method.
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
I dunno why you have to modify anything. I plugged my phone in and everything just worked.
Sent from my HTC Vision using XDA App
Only $10!
Man i would've given you @ least $11.
If anyone is having trouble with adb (and I know that it can be a struggle), I'm writing a guide to try and help - http://forum.xda-developers.com/showthread.php?t=865685
It's not finished yet, but there's enough information in there already to perhaps help a few people out.
I cant use adb and visionary does not seem to work.
Is there a way to root the Gingerbread rom without having to get adb to work?
Because it will not work for me.
Far as I know you'll need adb. Keep trying. You'll get it. When I had a backflip over a year ago. I went crazy trying to understand how to root. Now adb is easy. Easier with win xp I think.
Sent from my T-Mobile G2 using XDA App
myphonesbetter said:
I cant use adb and visionary does not seem to work.
Is there a way to root the Gingerbread rom without having to get adb to work?
Because it will not work for me.
Click to expand...
Click to collapse
Unfortunately not; there are some "no adb required" guides but they tend to have a high brick rate.
How is adb not working for you?
Sent from my HTC Vision using XDA App
Idk ive always had problems with adb on my computers.
I was having a problem finding a driver but i found one on a youtube video from g2hacks.
Heres the link.
http://g2hacks.com/g2-drivers/g2-phone-windows-drivers-download/
Incase anybody else is loosing their mind clicking all the links in the how to's on this forum. which all just take you in circle. like getting the run around from an insurance company.
I seem to be recognizing ill try to push some files now.
myphonesbetter said:
Idk ive always had problems with adb on my computers.
I was having a problem finding a driver but i found one on a youtube video from g2hacks.
Heres the link.
http://g2hacks.com/g2-drivers/g2-phone-windows-drivers-download/
Incase anybody else is loosing their mind clicking all the links in the how to's on this forum. which all just take you in circle. like getting the run around from an insurance company.
I seem to be recognizing ill try to push some files now.
Click to expand...
Click to collapse
Did you not go to the wiki which has a step by step guide, including links?
Sent from my HTC Vision using XDA App
Yah my problem this time was that i didnt have a driver. but that link worked. none of the ones on this website would though.
Everywhere i read it says i have to downgrade first. i was following the guide but i have to install the original g2 OTA signed.
Now ive ran into the problem that every copy i try to download is corrupt. just my luck. a 30 min process takes 5 hrs. or more.
I got to the point where adb reboot my phone into bootloader after the the temp root and did not realize the update.zip would not work. now im afraid to turn my phone back on. i dont want to have to do everything over again.
Ok figured that out. Windows xp was set to hide file extensions so i was nameing is pc10img.zip.zip
Guess ill see what problem lies ahead. i swear i could write a 100 step write up of what i have to do for a 15 step write up.
Got it rooted. Just took all day. Could not let my phone win. LOL.
Havent spent that long on a phone since i installed android and full WP7 dual boot on my HD2.
I run xp x86 on a computer that came with vista. maybe thats why i was having a problem.
I was able to install the nand backup from my old phone right to this phone. just a million hours of tinkering. I cant imagine how frustrated the developers get trying to make these roms work. i bet there compulsive about it though.
If someone sees this please put these drivers on the how to sticky section.
All the other links either would not work for me or were broken.
myphonesbetter said:
Got it rooted. Just took all day. Could not let my phone win. LOL.
Havent spent that long on a phone since i installed android and full WP7 dual boot on my HD2.
I run xp x86 on a computer that came with vista. maybe thats why i was having a problem.
I was able to install the nand backup from my old phone right to this phone. just a million hours of tinkering. I cant imagine how frustrated the developers get trying to make these roms work. i bet there compulsive about it though.
If someone sees this please put these drivers on the how to sticky section.
All the other links either would not work for me or were broken.
Click to expand...
Click to collapse
XP and vista shouldn't matter with the chip architecture so long as it supports it. But then again if it didn't, it would not install at all, and if it did for some weird reason it would not boot so that wasn't your problem.
So about two weeks ago, while installing a new rom, I managed to format my storage before flashing the rom. After doing that, there obviously was no rom to flash. Or anything else for that matter. My phone now can only boot into recovery mode. When trying to turn it on, it goes as far as the google screen showing the unlock icon. I would surely appreciate any help from you guys. Thank you in advance and I apologize for anything noobish i have or undoubtedly will say in the future.
By the way, here is my set up:
Verizon Galaxy Nexus
Windows Vista 32 bit PC
Again, Thank you
I am not near my PC but you have to enter into fast boot mode and push your ROM.zip to your phone using adb
Sent from my Nexus 4 using xda app-developers app
When i last tried that, ADB would not recognize my phone
jaysondasher said:
When i last tried that, ADB would not recognize my phone
Click to expand...
Click to collapse
If you are running a custom recovery, ADB should work. You probably are having driver issues.
Fastboot, flash stock. If you're phone isn't being recognized, install drivers.
Sent from my Galaxy Nexus using xda app-developers app
cupfulloflol said:
If you are running a custom recovery, ADB should work. You probably are having driver issues.
Click to expand...
Click to collapse
ADB does work on a custom recovery. You're right, he's having driver issues, he's just too lazy to search. THIS QUESTION has been answered a zillion times and is well documented in efrant 101 stickied on General section.
a manta wrote this.
---------- Post added at 04:42 AM ---------- Previous post was at 04:39 AM ----------
peikojose said:
I am not near my PC but you have to enter into fast boot mode and push your ROM.zip to your phone using adb
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Go read efrant 101 sticked on General section, please.
jaysondasher said:
When i last tried that, ADB would not recognize my phone
Click to expand...
Click to collapse
Of course, fastboot mode doesn't have ADB. Only fastboot.
a manta wrote this.
I don't think it's a problem of me being "lazy". I have been searching for over 2 weeks to find a post that helped me, and I wasn't able to because people on here seem to assume you know exactly what you're talking about, and throw around fancy android lingo that I'm unfamiliar with.
But I have uninstalled the drivers I previously had for my nexus and am going to try again. I also deleted ADB I think, so I'll have to get that again.
So, I installed Samsung's drivers, then went to adb and tried to sideload a rom, but was given the error: "device not found". I had my phone plugged in and booted into the recovery mode. I dont know what I'm doing wrong.
To the OP i really hope you get things sorted out. But some advice if you really do not know anything about your device, about rooting or how to use your device in conjunction with a computer then you need to do a lot more reading and research. Using ADB, Fastboot and being able to have your computer recognize your Gnex is all the first essential part of beginning to unlock the bootloader and rooting the device. So you should be very familiar with this unless you either had someone else root your phone or you used a root toolkit which is the reason why you don't understand what the steps may be or the wording. Toolkit are the worst to use just because of that reason. Also the fact that you wiped your internal memory also leads me to believe you don't know what you where doing because before it deleted it it asked you 'are you sure'. Please spend some time reading and learning educate yourself, do not expect anyone to solve it for you. Every rom, every guide and post on here always starts off by warning you that you are solely responsible for what you are about to do. Read, read and read again.
Sent from the future via Tapatalk 4
jaysondasher said:
I don't think it's a problem of me being "lazy". I have been searching for over 2 weeks to find a post that helped me, and I wasn't able to because people on here seem to assume you know exactly what you're talking about, and throw around fancy android lingo that I'm unfamiliar with.
But I have uninstalled the drivers I previously had for my nexus and am going to try again. I also deleted ADB I think, so I'll have to get that again.
Click to expand...
Click to collapse
fancy android lingo?
This 'lingo' that gets tossed around is the basic knowledge one should know when customizing (rooting/flashing/modifying) their Android device.
Would you go and start modifying the engine in your car without some basic understanding of how it works, or what the parts are called and located?
Why would you treat your electronic devices any other way?
That post tells me you didn't even read the damn sticky I was talking about.
If you had read this, you would understand the "fancy android lingo" by now. And @jaysondasher, I have another link for you, here.
Have a nice day.
Don't boot into recovery. Boot into boot loader mode. Power and both volume buttons. Then, using fastboot flash stock.
Sent from my Galaxy Nexus using xda app-developers app
was able to get it figured out. Sorry if I frustrated any of you, but thank you for your help.
Sent from my Galaxy Nexus using xda app-developers app
Alright, so my phone is really messed up. I wiped my internal data in recovery intending to flash back to full stock using LGNPST. Only problem is...LGNPST is failing...repeatedly...using every .bin available. Luckily, I still have access to TWRP. Already been in IRC, autoprime told me to try side-loading a ROM using ADB. I've never used ADB before, and quite frankly, my attention spam is waning at this point and frustration is mounting and I'd like to get this done quickly and not have to do a ton of reading.
I have downloaded the adt-bundle-windows-x86 file that contains two files, one marked SDK, the other marked Eclipse. If someone could walk me through, starting from one of these two folders(eclipse or sdk), step by step what I need to do to sideload a ROM to get my phone functional again, I would be very appreciative. I'm going to start reading, see if I can figure it out right now, but my hopes aren't real high. This is very foreign to me and I'm sure someone could tell me how to knock this out in just a few steps.
Thank you in advance friends.
EDIT: If it's easier to do it over hangouts, give me your hangout contact and I'll send you a message.
latrotoxin1986 said:
Alright, so my phone is really messed up. I wiped my internal data in recovery intending to flash back to full stock using LGNPST. Only problem is...LGNPST is failing...repeatedly...using every .bin available. Luckily, I still have access to TWRP. Already been in IRC, autoprime told me to try side-loading a ROM using ADB. I've never used ADB before, and quite frankly, my attention spam is waning at this point and frustration is mounting and I'd like to get this done quickly and not have to do a ton of reading.
I have downloaded the adt-bundle-windows-x86 file that contains two files, one marked SDK, the other marked Eclipse. If someone could walk me through, starting from one of these two folders(eclipse or sdk), step by step what I need to do to sideload a ROM to get my phone functional again, I would be very appreciative. I'm going to start reading, see if I can figure it out right now, but my hopes aren't real high. This is very foreign to me and I'm sure someone could tell me how to knock this out in just a few steps.
Thank you in advance friends.
EDIT: If it's easier to do it over hangouts, give me your hangout contact and I'll send you a message.
Click to expand...
Click to collapse
It's been a while since I've done it. But follow this. http://www.theandroidsoul.com/how-to-install-adb-on-windows-full-guide/
I think it's pretty much how I did it
Edit use this one. It's simpler. http://dl.google.com/android/installer_r22.2.1-windows.exe
engine95 said:
It's been a while since I've done it. But follow this. http://www.theandroidsoul.com/how-to-install-adb-on-windows-full-guide/
I think it's pretty much how I did it
Edit use this one. It's simpler. http://dl.google.com/android/installer_r22.2.1-windows.exe
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2443185&page=5
THIS WORKED! lol. I didn't know about this until 45 minutes ago. Downloaded, ran the program and I'm back dude! I wonder why this method worked and LGNPST failed.
You should still install android if ur rooting. A good tip if u decide to is when ur done update ur path to include adb so u can adb from anywhere. It makes it alot easier
Sent from my LG-LS970 using Xparent Red Tapatalk 2
noXcape said:
You should still install android if ur rooting. A good tip if u decide to is when ur done update ur path to include adb so u can adb from anywhere. It makes it alot easier
Sent from my LG-LS970 using Xparent Red Tapatalk 2
Click to expand...
Click to collapse
Maybe your could expound on this? Thanks!
Are you talking about installing Ubuntu? If so it wouldn't be needed... You could just copy and paste adb.exe in any folder you need it in on Windows... If you're not going to develop then windows is fine
Sent from my LG-LS970 using Tapatalk 4
If you update your path environment. You dont have to change directories everytime you go to adb or fastboot.
An example would be like... ;c:\android\sdk\platform-tools
Sent from my LG-LS970 using Xparent Red Tapatalk 2
Hi guys, I was wondering if someone with experience would be able to help me (a noob) out.
Last night I wanted to upgrade from 4.4.2 with Franco Kernel on my nexus 7 2013 to 5.0.2 Lollipop. I suspected that the franco kernel would prevent me from upgradeing OTA and I determined I must flash it myself. I downloaded Wugfresh Nexus toolkit and followed the videos but my computer said something like "wugfresh.exe stopped working. windows will try to find a solution." The window closed and now my nexus 7 wont load past the google screen. I am able to reach fastboot mode but if I try to access recovery, there is simply an android figure with a red exclamation point over it. Wugfresh doesn't seem to be working for me as I keep getting "failed: command write failed no such device or address"
I'm really stuck. It doesnt look like I can use Wugfresh (soft-bricked/bootloop option) as I keep getting failed reports. I have attached a screenshot to help describe what I am talking about.
Lemme know if you have any suggestions on how to proceed or need any additional information from me. I'm really bummed out and I have all day today to try and fix it.
Best,
ljia4
Will this menu help?
I see from the first sceenshot I attached that cache, recovery and system failed. Should I just use the menu in the second screenshot to flash those?
Im scared I will break it irreparably if i do so.
Flash the system image from fastboot and stop using toolkits.
Edit: When I say flash from fastboot, I mean actually use fastboot from the Android SDK and NOT the "fastboot flash" option in the toolkit. If you don't know how to use fastboot, and I suspect you don't, just read one of the many adb/fastboot guides available on XDA. You shouldn't be rooting/ROMing/modding your Android devices if you don't know how to use fastboot.
http://forum.xda-developers.com/showthread.php?t=2277112
@ljia4- Well? Any luck?
_MetalHead_ said:
@ljia4- Well? Any luck?
Click to expand...
Click to collapse
Thanks for following up. I was able to experiment with the advanced menu on wugfresh and eventually flash recovery and system. Then I used ota updates to get lollipop.
Thanks for checking back, I appreciate your time and efforts. I'll !take sure to steer clear from modding/flashing from here on out!
ljia4 said:
Thanks for following up. I was able to experiment with the advanced menu on wugfresh and eventually flash recovery and system. Then I used ota updates to get lollipop.
Thanks for checking back, I appreciate your time and efforts. I'll !take sure to steer clear from modding/flashing from here on out!
Click to expand...
Click to collapse
Don't steer clear of it, just learn how to do it the right way! I think you'll find that understanding how to use fastboot is much easier than it seems, and knowing how to do this stuff is invaluable. Aside from the fact that you'll be able to do pretty much anything, you'll also know how to get yourself out of a bind should you find yourself in one. Seriously, give that guide I posted a read, and if you have any questions don't hesitate to ask.
Anyways, I'm glad you got your situation figured out (even if you still used a toolkit ).
^++
_MetalHead_ said:
Don't steer clear of it, just learn how to do it the right way! I think you'll find that understanding how to use fastboot is much easier than it seems, and knowing how to do this stuff is invaluable. Aside from the fact that you'll be able to do pretty much anything, you'll also know how to get yourself out of a bind should you find yourself in one. Seriously, give that guide I posted a read, and if you have any questions don't hesitate to ask.
Anyways, I'm glad you got your situation figured out (even if you still used a toolkit ).
Click to expand...
Click to collapse
When I got my Nexus 5 and used Wug's toolkit to root and install TWRP, I'd already read about fastboot commands. Watching the Live Log, and seeing it was doing exactly what the posts said you do with fastboot (just automating it), was a nice way to see that it really is as easy as "fastboot flash system system.img", etc.