Alright, so I obviously jumped into this a little too fast.
Right now I'm stuck at the bootloader. I tried to flash another rom, it got to about 12%, and then failed. Since then I cannot reboot into wm. I have tried tons of other roms, to no avail. I don't know why but they only get to about 1%, then the phone shuts down and the load fails.
I have tried the stock rom, and custom roms. I'm not really sure where the problem lies.
It also doesn't find my device in Sync Center. So, nearly ever tutorial says "Make a connection" as one of the first steps. I cannot do this...
Anyone have any idea's on what I can do?
Tyler
Do you have a microsd card under 2gig? If so, put the rom on the card and flash it that way instead of through USB. You have to name the file TITAIMG.nbh. Much easier way to flash. It is all in the Wiki.
http://wiki.xda-developers.com/index.php?pagename=TitanProblems
I tried that method, but actually, I didn't notice that it has to be under 2gb. Mine is 4gb. So I have to one that small? What is the reason behind that?
Tyler
I think it is because the driver needed to handle the high capacity cards (anything over 2 gig) doesn't work in the bootloader mode. I'm sure if you search around, you'll find the exact answer.
Well I just ran up to walmart and grabbed a 2GB card.
Loaded up what is supposed to be the stock rom, and no luck. It goes the gray screen, says loading for half a second, then quickly flashes "No Image File" I think, its so fast I can barely read it.
I named the file correctly. I have no idea what is going on. Now I just need to have my phone work correctly.
I was trying to get GPS to work.
Right now I have boot loader 2.07, do I need to alter that to load a stock rom? I wouldn't think so. And if I do, how do I load it, if my PC won't connect to the phone.
I'm stupid, lol..
Tyler
Ok, finally! Haha, I loaded the stock ROM on there. I didn't have the new SD card formatted correctly, had the wrong unit size. Jeez. Anywho, now on to try again..
Tyler
hellonfire said:
Alright, so I obviously jumped into this a little too fast.
Right now I'm stuck at the bootloader. I tried to flash another rom, it got to about 12%, and then failed. Since then I cannot reboot into wm. I have tried tons of other roms, to no avail. I don't know why but they only get to about 1%, then the phone shuts down and the load fails.
I have tried the stock rom, and custom roms. I'm not really sure where the problem lies.
It also doesn't find my device in Sync Center. So, nearly ever tutorial says "Make a connection" as one of the first steps. I cannot do this...
Anyone have any idea's on what I can do?
Tyler
Click to expand...
Click to collapse
If I am not mistaken, it must be under 2 Gigs because it has to be formatted in Fat32. If I am not mistaken, Fat32 only supports up to 2Gigs. Has anyone tried to partitiion the card as a 2 Gig partition in Fat32 with 1024 Allocation size.
I used to have that error when it reached 12%, actually twice with two different causes. This first one only applies if you are running Windows through an emulator or virtual machine. (could be Fusion, Parallels, etc.. on a mac or Linux)
1. Actually with a Treo 700WX ... The cause was an old version of Parallels, apparently it would "share" the USB port with the MAC OSX, each time it was "OSX's turn" it would timeout the firmware update. This was fixed by going into the configuration and setting USB for "GUEST ONLY." The problem I had was that I had selected "ASK ME EACH TIME." (while updating the firmware, your USB is temporarily disconnected and lost, without the firmware parallels would not detect it)
Another solution to this error, is to update parallels to the newest version. (the newer versions handle EVERYTHING much better.)
2. The other firmware update Issue I had, also with a 700WX, was a bad USB cable. (yes they can and do inadvertently go bad without apparent cause
hellonfire said:
Ok, finally! Haha, I loaded the stock ROM on there. I didn't have the new SD card formatted correctly, had the wrong unit size. Jeez. Anywho, now on to try again..
Tyler
Click to expand...
Click to collapse
I see so many people here with that same problem, and that is the problem I had with the SD for a while. Did you resolve the 12% issue?
I haven't tried to flash anything via the USB cable again, so I'm not sure.
But I do have another issue.. I cannot run the ##778 command. When I do, and hit talk, I get no edit button. Am I screwed?
Tyler
Just updating to keep myself records now.. Haha.
Anyways, flashed again to stock Verizon everything, the 6.1 WM stuff. Everything now works, called in a got the correct Home SID, MIN1, MIN2 numbers. But now I still have no internet.
When I type in the username and pass they provide, its like my phone does not save it. If I type it in, finish, ok. Then immediatly check the settings again, they are blank.
Anyone?
Tyler
Install DCD's Verizon (or whichever carrier you use) carrier cab. Data won't work without it.
I had already done that. But I called in, again, and they reset my internet, and now everything works.. but alas, no friggin GPS, which was the whole point of this ordeal. I downloaded the GPSToggler, and no help. I'm going to try to revert back to an older version first, and try all this again. I think during my troubles, I got a 6.1 Verizon release, which would cause it not to work. correct?
If not, I found another thread detailing how to do it within the 6.1 rom, any idea on this? Not sure if I trust it..
Tyler
Ok. Now using wm 6.5 It rocks, but still no GPS..
Tyler
Yes if you flashed a Verizon 6.1 rom then your gps will be locked. You need to downgrade then flash custom again.
Yeah, I figured that out. But I was going to do the aGPS fix, but... none of the links in the Wiki work anymore.
Tyler
what links do you need?
drewcam888 said:
what links do you need?
Click to expand...
Click to collapse
I finally got them to work. Thanks for the offer though. I'm about to try the aGPS setup. Wish me luck. Haha.
Oh, and so far, I've been through about everr DCD rom, settled on 3.2.6 Everything else had bugs it seemed like.
And all the WM6.5 Roms are way to slow and buggy. Does anyone have any other recommendations for a clean, functional rom? I could use a little more stuff then DCD provides, but I know I could cook my own...
Tyler
Bah, this is BS. I am now convinced there is no way to get GPS working.
I have just done the aGPS setup, everything went fine, but still no GPS locks.
Yes I have Location on. Yes, I have all the External GPS settings correct. I'm using Google maps, maybe I'll try another program.
What gives?
Tyler
I cannot find a ROM that works with google services for the f*cking life of me. OK! Sooo, rooting was painless. Intalling firefirefirefirefire was a pain in the ass cause I didn't have the "original cable" or whatever, got TWRP installed in the same way. By downloading and imputing a bunch of commands into command promt windows 8.1. Got the drivers working all that jazz. Everything seems ok, in that respect. I'm running TWRP version 2.2.2.1 which is a bit out dated I realize, I always seem to get compabatability errors or something... Sometimes the keyboard doesn't work, sometimes google play services dont work. I'm very close to twisting my tablet into a painful million pieces.
Does anyone know of any roms with google services compatible software for team win recovery project 2.2.2.1 that would work today, or that would update itself or something?!?! I've tried a hundred diferent trial and error shots and I'm ripping my damn hair out. I dont need anything fancy, I just need it to work. Please, please help.
I can't even complain about anything because if was going to, I should have done it before I goofed up. first strike was letting it goof the region. Fine. But what killed it was not flashing the image while moving to ics. It stayed at cleaning for like 40 minutes, and I turned it off. I'm certain I have the us version.
I am hoping someone can throw me a bone about what may have come after installing the image, as well as if there's some sort of command I can enter to push that skipped img file. Or if I can use the data from another one to fix this one. also if I can push something in adb to fetch the region. Or if there are gods, a region free update. Or a program that can flash via recovery and not in a normal boot.
I have a couple different versions of ics on the device, one wants a signature, and the other says something doesn't match and aborts it. Reading around I hear vaguely about how people with the same device managed to fix it, and the ones who have posted working links to drivers or zips, I have tried them to no avail. When the other one gets here, I'm hoping I can get the update zip from that and maybe click away at the screen until I get some type of results.
Also, is there any type of information on what hardware part all of this is stored on? Maybe I can replace that.
Maybe someone can point me in the right direction. Though, I'm sure someone might have shed light on some of it, and it's buried under a bunch of tablet s advice...
Hello all!
First of all, I am no developer.
Long story short.. I purchased an HTC 10 because I was sick and tired of my at&t galaxy s5 being bootlocked. I received the 10 and set out the next day to root it. I followed a video on youtube (not saying that the info was not correct...I may have done something wrong...not trying to discredit anybody) to the letter and lo and behold I ended up in a bootloop. My heart probably came close to a complete blockage at this point. This bootloop lasted maybe a minute before it would reboot. So... In my infinite wisdom I chose to relock the bootloader. Oh Boy!!! Fun times were ahead for me!! As soon as I relocked said bootloader, the bootloop increased its timing to about 1 point 5 seconds. I remember waking up on the floor in the fetal position. Now I am stuck with a phone that adb will not recognize. It does however recognize the device at the fastboot devices prompt. So my question is this.... Is this a salvageable phone? If so, How would one go about fixing this problem?
*** Relocked ***
htc_pmew1 pvt S-ON
os-2.28.617.8
I would prefer that the money I spent on this thing would amount to something more than a small ant bed.
Any help at all would be greatly appreciated. Also I have been doing a lot of digging around and (I may be wrong) but. I could not find this scenario in the forums here. I apologize if this has already been covered.
...So..after looking around for a bit more, I discovered out that there is a way to flash a ruu/zip from an sd card. I have tried multiple times with what I thought were the right ones. As I am unable to boot into recovery, I feel I am limited as to what I should do. I have read about that I should wipe dalvik but I am very limited in my knowledge on an android system and would prefer to not mess this phone up anymore than it already is. I was trying to root and I used TWRP as the recovery but I never made it to the end before it started the loop. The Phone is an htc 10 unlocked version. and it just constantly reboots about 3 seconds apart. ADB says no device connected, so I cannot execute commands that way... really at a loss here. all the tutorials I have read refer to using and and being able to boot into rrecovery. when i boot into recovery, I get an immediate reboot and the 3 second bootloop forever. Is there a way to use twrp to somehow resolve this?Is there a tool that will help me at least get into recovery mode?
SOLVED... Ran across Batchtool by sneakyghost. Quite the bunch of tools there! Ended up solving my problem by placing the stock RUU in the root folder as the batch tool. Before I could not install from a factory RUU (would not recognize the phone through ADB or install the RUU. After the install of the batch tool I was able to get a clean install back to my factory settings.. Now I am free to mess it up again!!
BIG THANKS TO SNEAKYGHOST!!!!!
I'm unsure why the batch tool has worked for you and the sdcard method didn't - getting fastboot to work and all the bits and pieces together (drivers, Windows VCRedist, correct fastboot, correct adb) is usually more error prone than just identifying the correct zip and placing that in your sdcard root.
At this time, I'm a bit in a "scratch my head" mood, thinking this is weird. Same zip? Really the same zip didn't work from sdcard but would work in fastboot? I think I haven't come across that myself yet (non booting phones are a daily thing, almost).
I wish I had the time to analyze your steps with you, so I could gain understanding as to why that happened, so I can use that in the future, but alas! I have no time for XDA and deep digging around in issues of other people. Lately I can't even solve my own phone's problems anymore due to too many other things going on.
Well, glad it worked for your phone, anyhow. I'll keep this in mind for the next one messing up his/her phone.
Hey all,
I've never rooted a phone before so since I have a spare model, I figured I'd give it a go.
Hearing about this forum, I checked it out and was sent to the Sony site. I understand I needed to unlock the bootloader first, which I did and can confirm I get that alert as my phone starts about it not being safe.
Hint for future readers: don't do this in a virtual environment, I had issues doing this until I used an actual computer and not a VM (mods and folks with more experience: feel free to correct me on this or shed some light). To be clear, I have a separate host running Proxmox (Type I hypervisor) and was able to forward my USB connection to test with ADB and such. I do most things in a virtual environment to not mess up my physical computer.
This was all done last week. Well today, Monday, I decided to continue with my rooting excursion, only to run into the issue I am currently facing.
After many, many Google attempts and following whatever links in this, I finally found this link. Well, I was within a VM, downloaded the linked flashing tool, and ran the first two commands:
- adb devices
- adb reboot bootloader
After doing this, my phone turned off and I wasn't sure what to expect, so I pressed the Power button to see what would happen - nothing. So then I remembered that Friday I was having issues communicating with my mobile phone in the VM to unlock the bootloader in the first place, so I figured I'd try to move it to my physical computer....then I was stuck on a reboot cycle!
To be clear, my issue is that I am stuck on a boot loop. It prompts the error of the device being unsafe, waits 5 seconds, then displays the Sony splash screen. Rinse, wash, repeat; same thing.
I have a Sony Xperia XA1 (G3123) model.
Can anyone shed some light?
Am I screwed?
Please halp!
I dug around a bit more, found this link but the issue is that I cannot boot into anything, at least not that I'm aware of.
tryingToSurvive said:
I dug around a bit more, found this link but the issue is that I cannot boot into anything, at least not that I'm aware of.
Click to expand...
Click to collapse
have you tried installing a custom recovery?
this may help https://forum.xda-developers.com/xa1-ultra/development/g3221-built-sources-t3622886
keifus.rahn said:
have you tried installing a custom recovery?
this may help https://forum.xda-developers.com/xa1-ultra/development/g3221-built-sources-t3622886
Click to expand...
Click to collapse
Hey @keifus.rahn for following up.
I did find that thread after continued poking, which I am still checking now. And I eventually made a post on there just now discussing my current dilemma.
I downloaded the Flashtool but didn't understand how it worked, nor do I still yet. I tried debugging it and the issue is that the "java -version" call doesn't work within the directory's own structure. I do have java installed on my test Linux VM though.
Past that, I tried with the latest boot.img as well as the recovery.img that I found. I think that the build numbers are off, or maybe I am just not understanding where I am lacking.
You can look at the bottom of the last page for a breakdown of what I did:
https://forum.xda-developers.com/xa...21-built-sources-t3622886/page94#post80481385