[Q] Nexus S 4G - A Soft, Squishy, Brick. - Nexus S Q&A, Help & Troubleshooting

Good day, XDA.
Recently, I became the proud owner of a Nexus S 4G, primarily because whomever had the phone prior to me had decided that flashing a GSM rom onto their Nexus S 4G would be a good idea. Needless to say, and as you can all probably guess, this did not benefit the functionality of this phone.
So lets start from the top, the phone is able to power on and boot up, it is running 2.3.6 stock. About phone reads the following:
Model Number: Nexus S
Android Version: 2.3.6
Baseband Version: Unknown
Kernel Version: 2.6.35.7-gf5f63ef [email protected] #1
Build Number: GRK39F
It has no SU binary. While powered up in this mode, it can charge VIA usb, but is unable to be seen by the computer with debugging mode on, or with debugging mode off. Neither option would seem to result in the phone being picked up by either Windows or Linux (Odd that it charges fine though. I did confirm this was not a "Charge Only" cable.)
Moving on, I can boot into fastboot, where I am presented with the following:
Product Name - Herring
HW Version - Rev 03 (JTAG)
Bootloader Version - I9020XXKA3
Baseband Version - I9020XXKF1
Carrier Info - SPR
Lock state - Unlocked.
At the bottom when booting into fastboot, it shows me "USB Control Init", followed immediately by "USB Control Init End". The computer does not see the device when plugged in here either. So no pushing fastboot or adb commands.
Booting into recovery, I am presented with Andy, standing next to a White triangle with a yellow exclaimation mark in it. After fiddling around with the power and volume buttons, I am eventually presented with a screen that states
"Android system recovery <3e>". Oh boy! Stock recovery. How lucky I am. It has the option to apply update from /sdcard, but these need to be signed; and it seems every update.zip file for the Nexus S 4G that I can find makes the assumption that you are on the previous android version, and will not flash if you are not.
So here is where I currently am. I can download zip files over wifi and attempt to push them out to the phone, but there is no PC connectivity, which seems to hinder my attempts at making it work a bit better. I will admit, I am new to the Nexus S (Having never used one before), and to the Samsung devices rooting community (Having been exclusively HTC prior to this). So I might be missing something; does anyone have any thoughts on where to go from here? Sorry for the long post.

SoberSquid said:
Good day, XDA.
Recently, I became the proud owner of a Nexus S 4G, primarily because whomever had the phone prior to me had decided that flashing a GSM rom onto their Nexus S 4G would be a good idea. Needless to say, and as you can all probably guess, this did not benefit the functionality of this phone.
So lets start from the top, the phone is able to power on and boot up, it is running 2.3.6 stock. About phone reads the following:
Model Number: Nexus S
Android Version: 2.3.6
Baseband Version: Unknown
Kernel Version: 2.6.35.7-gf5f63ef [email protected] #1
Build Number: GRK39F
It has no SU binary. While powered up in this mode, it can charge VIA usb, but is unable to be seen by the computer with debugging mode on, or with debugging mode off. Neither option would seem to result in the phone being picked up by either Windows or Linux (Odd that it charges fine though. I did confirm this was not a "Charge Only" cable.)
Moving on, I can boot into fastboot, where I am presented with the following:
Product Name - Herring
HW Version - Rev 03 (JTAG)
Bootloader Version - I9020XXKA3
Baseband Version - I9020XXKF1
Carrier Info - SPR
Lock state - Unlocked.
At the bottom when booting into fastboot, it shows me "USB Control Init", followed immediately by "USB Control Init End". The computer does not see the device when plugged in here either. So no pushing fastboot or adb commands.
Booting into recovery, I am presented with Andy, standing next to a White triangle with a yellow exclaimation mark in it. After fiddling around with the power and volume buttons, I am eventually presented with a screen that states
"Android system recovery <3e>". Oh boy! Stock recovery. How lucky I am. It has the option to apply update from /sdcard, but these need to be signed; and it seems every update.zip file for the Nexus S 4G that I can find makes the assumption that you are on the previous android version, and will not flash if you are not.
So here is where I currently am. I can download zip files over wifi and attempt to push them out to the phone, but there is no PC connectivity, which seems to hinder my attempts at making it work a bit better. I will admit, I am new to the Nexus S (Having never used one before), and to the Samsung devices rooting community (Having been exclusively HTC prior to this). So I might be missing something; does anyone have any thoughts on where to go from here? Sorry for the long post.
Click to expand...
Click to collapse
what model is your nexus s? i9020A i9023 ect..? the link below has a ton of stock roms for various nexus s versions and most are flashable via Stock Recovery
http://forum.xda-developers.com/showthread.php?t=1063664

It is the SPH-D720, my appologies for leaving that out. Unfortunately, it seems the D720 has the misfourtune of not having a fully flashable ROM listed on that page.

SoberSquid said:
It is the SPH-D720, my appologies for leaving that out. Unfortunately, it seems the D720 has the misfourtune of not having a fully flashable ROM listed on that page.
Click to expand...
Click to collapse
Its a shame it wont connect to adb because that's one of the few nexus s that has signed images flashable via fastboot.
Sent from my Nexus S using xda premium

Indeed. It is quite odd - It can boot into fastboot, download mode, etc just fine, but it isn't picking it up at all on the PC. I'm thinking it has to do something with the kernel-mode USB drivers, prehaps there are different drivers used for the CDMA and GSM varients? It is a bit frustrating because it would be a fairly simple fix if fastboot could pick it up.

SoberSquid said:
Indeed. It is quite odd - It can boot into fastboot, download mode, etc just fine, but it isn't picking it up at all on the PC. I'm thinking it has to do something with the kernel-mode USB drivers, prehaps there are different drivers used for the CDMA and GSM varients? It is a bit frustrating because it would be a fairly simple fix if fastboot could pick it up.
Click to expand...
Click to collapse
You might want to try reinstalling the drivers, I use an apple computer & they dont require those drivers so i cant be much help there. Here's another link to check out. Pete Alfonso makes roms from the Nexus S and has the original signed software images for the Nexus S 4g and some other stuff that might help you... http://download.peteralfonso.com/crespo4g

Hmm, looking at his site, he has quite a lot of good stuff, most of it requires a non-stock recovery though. The Nexus S 4G (When it came out), was running 2.3.4, in contrast to the normal Nexus S. I wonder, Since my phone is currently reading on a GSM rom/radio, could I flash the phone to 2.3.3 (Android 2.3.3/GRI40/XXKB1 Radio/KA3 Bootloader), use gingerbreak to gain SU, install CWM, and possibly flash back to a proper baseband and rom from there? Or is that really looking at mucking things up?

SoberSquid said:
Hmm, looking at his site, he has quite a lot of good stuff, most of it requires a non-stock recovery though. The Nexus S 4G (When it came out), was running 2.3.4, in contrast to the normal Nexus S. I wonder, Since my phone is currently reading on a GSM rom/radio, could I flash the phone to 2.3.3 (Android 2.3.3/GRI40/XXKB1 Radio/KA3 Bootloader), use gingerbreak to gain SU, install CWM, and possibly flash back to a proper baseband and rom from there? Or is that really looking at mucking things up?
Click to expand...
Click to collapse
I wouldnt flash any rom with a bootloader not made for your phone.
---------- Post added at 01:22 PM ---------- Previous post was at 01:18 PM ----------
scott8281 said:
I wouldnt flash any rom with a bootloader not made for your phone.
Click to expand...
Click to collapse
you might try this flashable update... Look down towards the bottom of the page... they are flashable via stock recovery.... http://forum.xda-developers.com/showthread.php?t=1063664 D720:
Android 2.3.4 (Build GRJ06D/PRKC9 Radio/KC5 Bootloader)
2.3.4 (GRJ06D) -> 2.3.4 (GRJ22)
2.3.4 (GRJ06D) -> 2.3.5
2.3.4 (GRJ06D) -> 2.3.7
Android 2.3.4 (Build GRJ22/PRKD8 Radio/KC5 Bootloader)
2.3.4 (GRJ22) -> 2.3.5
2.3.4 (GRJ22) -> 2.3.7
Android 2.3.5 (Build GRJ90/PRKE5 Radio/KC5 Bootloader)
2.3.5 -> 2.3.7

Tried all 3 of those, they state the following:
-- Install /sdcard/Download ...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
I believe all 3 of those are expecting you to be on the prior android version, and when it sees that you are not, it fails.

SoberSquid said:
Tried all 3 of those, they state the following:
-- Install /sdcard/Download ...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
I believe all 3 of those are expecting you to be on the prior android version, and when it sees that you are not, it fails.
Click to expand...
Click to collapse
Well crap! im officially out of ideas... Best of luck to you, Im certain that with your phone able to boot into bootloader that its fixable

Ahh, well thanks anyway for trying to assist! Anyone else have ideas on how to fix this, or anyone else experience this before?

Assuming I cannot recover this, as it is slowly looking fairly unrecoverable, does anyone have a recommended JTAG service (Preferably in the US)? I'm not aware of any around my area. I did see a few online, but I'm unsure as to how trustworthy any of them are...

Did you try the roms listed here?
http://forum.xda-developers.com/showthread.php?t=1078213
Hmm. Without fastboot its tough to flash a rom, Did you try the factory data reset option in your settings, IS it showing error?

you're lucky i just did this last week.
seems that jerk flashed a gsm radio to that phone.
what you'll need to do is ODIN the phone to flash the CDMA radios back. you can find that HERE just follow the steps in that program and then you should be booting 2.3.4.
from there take the updates from sprint to get back to 2.3.7.
something about flashing a gsm radio hosed the MEID of my new phone, so keep that in mind. you may need to repair it afterwards before you can use it on sprint.
if you need help get back with me but that program should do the trick for you.

saranyan said:
Did you try the roms listed here?
http://forum.xda-developers.com/showthread.php?t=1078213
Hmm. Without fastboot its tough to flash a rom, Did you try the factory data reset option in your settings, IS it showing error?
Click to expand...
Click to collapse
Tried those; those were the ones listed on Peter Alfonso's Site (Who I assume is BuglessPete? Like I said, I'm new in this section ). Unfortunately the Odex/Deodex require signature verification to be off, and the other updates are only partial updates, so they make the presumption you are on the prior Android revision, and promptly fail signature verification if you are not, so yeah unfortunately none of those had worked :/
thedudejdog said:
you're lucky i just did this last week.
seems that jerk flashed a gsm radio to that phone.
what you'll need to do is ODIN the phone to flash the CDMA radios back. you can find that HERE just follow the steps in that program and then you should be booting 2.3.4.
from there take the updates from sprint to get back to 2.3.7.
something about flashing a gsm radio hosed the MEID of my new phone, so keep that in mind. you may need to repair it afterwards before you can use it on sprint.
if you need help get back with me but that program should do the trick for you.
Click to expand...
Click to collapse
Thanks much - I downloaded the program, ran setup.exe, installed all of it (Wow, this looks familiar from way back when I had a Samsung Moment, lol.). Threw the phone into download mode and waited. Unfortunately, it went downhill from here - It just sits there stating "Detect Port...", and shows disconnected. In Windows, under device manager, I went to view>devices by connection, then expanded out to my USB Port Hub. I don't show any devices there. So it seems that my phone is simply not being picked up by my computer - I did verify the USB cable I had was a data cable, and not a charge-only cable. And while hard to see them, the pin connectors in the charging port on the phone look good.
When I go into download mode (Or fastboot, for that matter), it shows the following on the screen, which I think is part of the cause of this issue:
"USB Control Init"
"USB Control Init End"
These happen right after one another. I'm not really sure why the USB controller wouldn't be working in this case, but I think whomever had the phone before me (in an attempt to fix an issue), decided to restore this phone back to stock using the I9020T files. I believe the Nexus S GSM variant may have a different USB controller in it, which is causing the drivers to malfunction on the CDMA variant, but I could be wrong. I haven't seem something like this occur before, lol.

Here are some fancy photos:
Download mode (Plus the error message given):
http://i.imgur.com/T4wOE.jpg
USB Port:
http://i.imgur.com/COAhb.jpg
Its an odd error, and looking online, some others who had it just had a bent usb port, but mine appears to be good, and all 5 pins look A-OK.
(Also, as a side note: Man, look a the viewing angles on that thing in the second shot, you can still see the error from the first pretty clearly. That is awesome.)

SoberSquid said:
Here are some fancy photos:
Download mode (Plus the error message given):
http://i.imgur.com/T4wOE.jpg
USB Port:
http://i.imgur.com/COAhb.jpg
Its an odd error, and looking online, some others who had it just had a bent usb port, but mine appears to be good, and all 5 pins look A-OK.
(Also, as a side note: Man, look a the viewing angles on that thing in the second shot, you can still see the error from the first pretty clearly. That is awesome.)
Click to expand...
Click to collapse
In download mode it should show up as a Samsung diag modem or something like that.
I'll bet it's your cord or usb port on your PC. Can you try a different port or cable?
Sent from my Nexus S 4G using xda premium

Tried different ports (And different computers, My linux box is the same) - I have also been through 3 different cords trying this. - That message comes up immediately, even if there is no USB cable connected.

SoberSquid said:
Tried different ports (And different computers, My linux box is the same) - I have also been through 3 different cords trying this. - That message comes up immediately, even if there is no USB cable connected.
Click to expand...
Click to collapse
are you seeing any com port at the bottom of the window? mine is com4

SoberSquid said:
When I go into download mode (Or fastboot, for that matter), it shows the following on the screen, which I think is part of the cause of this issue:
"USB Control Init"
"USB Control Init End"
These happen right after one another. I'm not really sure why the USB controller wouldn't be working in this case, but I think whomever had the phone before me (in an attempt to fix an issue), decided to restore this phone back to stock using the I9020T files. I believe the Nexus S GSM variant may have a different USB controller in it, which is causing the drivers to malfunction on the CDMA variant, but I could be wrong. I haven't seem something like this occur before, lol.
Click to expand...
Click to collapse
and don't worry about that error, mine says that too

Related

Bricked Wind Mobile G2x - Need help understanding why

Hi, I apologize up front for the long winded post, but I want to relay as much info as possible in the hope that someone can point out my mistake(s).
This is the 2nd android phone I have managed to brick in the past couple years.. The first was an old dream and I flashed the wrong update file for a different phone by accident, but at least I knew what I did wrong that time.
Fast forward to yesterday. I picked up a brand new LG Optimus 2X (LG-P999 = G2X) From Wind Mobile in Canada running android 2.2.2. I bring it home and load up super one click and it tells me I am rooted, great! After that I loosely followed these instructions: hxxp://wiki.cyanogenmod.com/wiki/LG_Optimus_2X:_Full_Update_Guide to get ClockworkMod Recovery installed via the market (free version).
First little hiccup was that when I opened the mod manager and tried to click on 'Flash ClockworkMod Recover' it gave me an error saying, "Error while downloading from Server. Please make sure that you have a stable internet connection, and that your SD card is inserted and has free space!". That's weird.. I have a brand new 2gb sd card and my 3g connection is working great.. I was able to sort that out by connecting to my home wifi connection and then this message disappeared. When flashing clockwork it asks for my model of phone and I choose the LG G2X from the list. Success! Although when I try to click on the option to boot into recovery -- nothing happens. Since I don't want to power off my phone, I download "Quick Boot" by Sirius Applications Ltd. and try to click the reboot option, but again, nothing happens. The recovery option also does nothing, whats going on here? I finally decide to power down my phone the "normal" way from the home screen.
I boot back up normally and realize that I didn't download cyanogenmod yet, so I go do that. I download update-cm-7.1.0.1-G2x-signed.zip for the T-Mobile G2x, even though mine is not T-Mobile, I read on the internet that I definitely have a G2x even though it is marketed as an LG Optimus 2X. I also download the Google apps gapps-gb-20110828-signed.zip.
Once the files are downloaded, I attempt to copy them up to the memory card, but windows explorer (Im using Windows XP) seems to lock up for a bit and I get a weird error: Cannot copy gapps-gb-20110828-signed.zip: The path is too deep. I have never seen this copy error before. I look it up on google and don't get much help, although it tells me what I already assume, that this error appears when your filename + path combo is too long. But its not too long! gapps-gb-20110828-signed.zip is on my desktop, and I'm copying to the root of F:\ !! The other weird thing is that this gapps-gb-20110828-signed.zip is only 6MB large. I have no problem copying the update-cm-7.1.0.1-G2x-signed.zip which is 93MB! I can copy any other file I throw at it.. BUT I CANT COPY THE GAPPS FILE !? I tried so many things at this point. I renamed gapps-gb-20110828-signed.zip to gapps.zip. I redownloaded it from the mirror. I tried copying it from the root of C:\ and another drive. I tried unzipping it and rezipping it. I always got the same error.
Finally I decided to copy the gapps file to the internal memory, and it copied without a problem. I wasn't sure if I could access that drive from recovery, but I decided to try it, even without gapps since I wasn't having much luck getting it onto the card. In hindsight, I should have maybe tried copying it to another sd card and also tried copying to the same sd card plugged into my computer via sd reader to see if the same problems existed. Even rebooting the phone and my computer would have been some good troubleshooting, but I wasn't aware of what would happen next.
I booted to recovery at this point (I can't remember if I booted via the rom manager link or if I rebooted and held the power and volume down button) and it came up as expected. I first made a backup of the existing system even though I didn't think I really needed it. Then I did the Wipe data/factory reset and Wipe cache partition. Finally, I loaded the cyanogenmod update and was surprised at how it loaded in mere seconds-- my old dream always took at least 1 or 2 minutes even for a smaller file. I then noticed an option to load a zip file from my the other storage (I can't remember the exact name of the option - but it was the place where the gapps file was). I loaded gapps without error and rebooted the phone.
It is at this point that I never booted back into anything again. If I remember correctly, it loaded the first LG symbol as usual, and then I saw another 'fancier' LG logo come up, with no animation or progress bar. I waited on this screen for more than 10 minutes, expecting that it would finally change to cyanogenmod, but nothing ever happened. No problem I thought, I can just boot back into recovery and try again without the gapps perhaps. No dice. I removed and replaced the battery, and then booted up with the power and volume down arrow held. I saw a LG symbol with progress bar, I saw a android character coming out of a box with a progress bar. I let go of the buttons. The phone rebooted. I tried again and again. Nothing.
At this time I was getting quite worried, but I had my phone plugged into the computer still and I noticed that everytime I got to the 'fancier' LG logo screen, the computer would recognize the phone via usb. I decided to see what the internet offered for solutions and I read lots and lots of info.
Everything boiled down to pulling out the battery, holding the volume up and down buttons and then plugging the usb to the computer. I installed all the necessary drivers and ran nvflash in an attempt to either install CWM or even the stock recovery. Getting the computer to recognize the phone properly was a chore in itself. Often it would come up saying 'Unrecognized usb device' or it would simply show up in the device manager with an "!". Sometimes when it showed up with the "!" I would right-click and uninstall it, then unplug and replug and install the driver again and that would work for a time or two.
The problem was that when I ran any commands I found for nvflash, it seemed to take forever to do anything. I mean I would be waiting, and waiting, and waiting, and all the command prompt would say is:
"Nvflash started"
One post I read somewhere said to just try a harmless command of "nvflash --sync" to see if the proper output appeared. I tried it a few times, but all I got was the same "Nvflash started", but then one time I noticed after a while it came up with a new line after that of "rcm version 0X20001". I tried nvflash at least 1000 times, no joke. I wasn't about to let this brand new phone beat me without a fight.
On one occassion I tried using the "One Click Recovery Flasher" that I found, and I attempted to load the stock recovery. The response from nvflash seemed to flow a little quicker this time and I got further in the process then ever before. Since it was now 4am I decided to let it do its thing and I would wake up and check it in the morning. I woke up at 10am and it was exactly where I left it. After 6 hours, I would have expected it to do SOMETHING! Here is what it said:
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 4
chip sku: 0xf
chip uid: 0x037c704243a08357
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
It apparently was unable to send the fastboot file for some reason. I could try 1000 more times but I am defeated at this point. I am planning to return the phone today and see what they say. If by chance I return it successfully, and I get the same model of phone, I will be super wary of trying to root it again. But I also don't want a phone that I can't "have fun with". Any comments or suggestions are most welcome. I would like to know what I did wrong so that I can learn for "next time". Other than the weird sd card error, I really think I did everything correct. At this point I am thinking there was either something wrong with the sd card or even with the phone itself. Regardless, I thank you for reading my story and I look forward to any helpful responses.
Cheers!
I'm also on wind. The first thing I did was use nvflash to get a recovery. Never never use ROM manager to flash recovery on the g2x. It's a fake flash. Also, try running a vm or dual boot to use Linux. Nvflash worked fine on Linux didn't try on windows. no drivers needed. It recognizes it without doing anything special.
Sdcard problem is because the 2GB card is under /emmc or /sdcard/_Externalsd our something on stock.
tahahawa said:
I'm also on wind. The first thing I did was use nvflash to get a recovery. Never never use ROM manager to flash recovery on the g2x. It's a fake flash.
Click to expand...
Click to collapse
Did the same thing. I am on Linux too, and everything was extremely simple.
BTW, I think Wind's LG doesn't have screen bleeding or rebooting issues. I've never had them.
It sounds like you didn't install the drivers for the APX mode. When you get the explanation mark you need to right click and say update driver, then says I will find myself and browse to the apx directory where you extracted the One Click program for NVFlash. Then when it says the driver is unsigned click yes to continue. Once the apx driver is properly loaded you can flash CWM and reflash any rom you want. Don't worry your phone is not bricked. It is almost impossible to truly brick a G2X.
Did you resolve this issue. I just encountered it myself. Are you in Toronto by any chance. [sigh]. This sucks. I hope you can help shed some light.
Did you see my advice above? Try that. Also try re downloading everything, including all nvflash files.
Sent from my LG-P999 using XDA App
Awesome. Nvflash unbricked the SOB. I used the youtube video (lookup this one: "How To Install CyanogenMod 7 Nightly on T-Mobile G2x after Nandroid Backup") and the G2x P999 ROM from cyanogen, and got my phone back. The video worked perfectly for me and I would recommend it (but of course don't blame me if anything goes wrong... why should I be different? . The T-mobile stuff bugs me though. I wonder why the cyanogen mod has their branding in it. Ah well.
Now that my phone works again, I can figure out how to get those annoying lines to stop moving all over the frickin' place. Then back up this ROM so I have something to recover to. And maybe try the cynaogen Optimus 2x ROM; although it does say in the file name that it is 990 and not 999. And maybe give the fine xda ROM a go (since I found the answer here).
Thanks to Wind Mobile for messing around with the names and making it confusing. The Optimus 2x by Wind is a P999 and the same as what T-Mobile has, and an Optimus 2x looks to be a 990 everywhere else in the world. I guess Wind never intended to make it easy to upgrade these phones from the start (and aren't offering an official Gingerbread, never mind Ice Cream Sandwich upgrade). Now it looks like they won't even be selling them any more. I guess they would cut into the profit of the new more expensive Galaxy when it comes out.
I know I won't use that ROM manager again. At least not for this phone. Wow!
Thanks again for the quick reply and sticking my nose back into the answer.
Regards,
BillR
tahahawa said:
Never never use ROM manager to flash recovery on the g2x. It's a fake flash.
Click to expand...
Click to collapse
Is this true of ROM Manager in general, or is this something particular to the G2x?
dmj2012 said:
Is this true of ROM Manager in general, or is this something particular to the G2x?
Click to expand...
Click to collapse
Just the g2x/optimus 2x.
theshowmecanuck said:
Awesome. Nvflash unbricked the SOB. I used the youtube video (lookup this one: "How To Install CyanogenMod 7 Nightly on T-Mobile G2x after Nandroid Backup") and the G2x P999 ROM from cyanogen, and got my phone back. The video worked perfectly for me and I would recommend it (but of course don't blame me if anything goes wrong... why should I be different? . The T-mobile stuff bugs me though. I wonder why the cyanogen mod has their branding in it. Ah well.
Now that my phone works again, I can figure out how to get those annoying lines to stop moving all over the frickin' place. Then back up this ROM so I have something to recover to. And maybe try the cynaogen Optimus 2x ROM; although it does say in the file name that it is 990 and not 999. And maybe give the fine xda ROM a go (since I found the answer here).
Thanks to Wind Mobile for messing around with the names and making it confusing. The Optimus 2x by Wind is a P999 and the same as what T-Mobile has, and an Optimus 2x looks to be a 990 everywhere else in the world. I guess Wind never intended to make it easy to upgrade these phones from the start (and aren't offering an official Gingerbread, never mind Ice Cream Sandwich upgrade). Now it looks like they won't even be selling them any more. I guess they would cut into the profit of the new more expensive Galaxy when it comes out.
I know I won't use that ROM manager again. At least not for this phone. Wow!
Thanks again for the quick reply and sticking my nose back into the answer.
Regards,
BillR
Click to expand...
Click to collapse
Never flash anything meant for p990. Period. Unless it states it is for both. cyanogenmod had no Tmobile stuff except wifi calling.
Sent from my LG-P999 using XDA App
tahahawa said:
cyanogenmod had no Tmobile stuff except wifi calling.
Click to expand...
Click to collapse
When I first started the phone a message came up asking me if I wanted to run something, and that I could go to the T-Mobile site later if I didn't want to. Now I have been playing with it for the last hour and haven't seen any other TM related stuff, so maybe it was just that one.
The very first time it runs you get that message from the wifi calling app. You should never see it again unless you do a factory reset.

[Q] Virgin Mobile Galaxy 550 root FAIL. :c

Hi there. I got me a samsung galaxy 550 from virgin mobile canada yesterday, and well, I kinda like it despite being a slow piece of hardware with a 320x240 screen but until I can get enough money to buy something better, I'm fine with this (the phone I had before was a nokia n95, so that's a step up.)
The problem is, I want to try out the official 2.2.1 rom from samsung, and the only way I can do that is to update via odin. actually, that's not the problem, but I want to make a backup of all the apps I've downloaded already, and I just can't get it rooted. at all. z4root, universal androot, superoneclick; they just don't work. the one that was the closest to getting it rooted was superoneclick, and even then it can't finish the job, so I'm stuck with superuser on an unrooted phone, and titanium backup won't work either, so I'm kinda stuck here.
What else could I do?
anyone? please?
6 days later...
You may have noticed this is a "development and hacking" forum. Your problem reads more like a user error than a development one.
I do not mean to say this thread does not belong. It is just that "they just don't work" is something like what a Windows-using grandmother would say.
What are the exact errors you are getting? Preferably, they should be copied and pasted from the terminal itself.
Jason_25 said:
You may have noticed this is a "development and hacking" forum. Your problem reads more like a user error than a development one.
I do not mean to say this thread does not belong. It is just that "they just don't work" is something like what a Windows-using grandmother would say.
What are the exact errors you are getting? Preferably, they should be copied and pasted from the terminal itself.
Click to expand...
Click to collapse
Well, z4root doesn't do anything after it says "running exploit", superoneclick gets stuck on "waiting for device", and the only time it managed to get superuser onto it, it couldn't root the device no matter if I updated it or not; universal androot says "FAILED NO FU GOO", both odin and heimdall fails to connect to the device, and ADB doesn't even see the phone no matter what mode it is. I can't seem to find how to boot into recovery mode (I only ever get instructions to boot into download mode).
ok now in odin I get "cannot open the usb serial port. code: 2". sometimes it's code 5.
Go to madteam.co...dedicated for G5 users,you will get help there at no time
Sent from my blek krupuk
First problem is ADB not seeing the phone. ADB is pretty necessary if you want to debug something. You will need to download LG's Windows driver for your phone if you use Windows. I will include the one I use for my Optimus V here.
On many LG phones it is impossible to boot into recovery or fastboot mode without modification.
Try zergRush from here first:
https://github.com/revolutionary
If not working, try GingerBreak from here:
http://c-skills.blogspot.com/2011/04/yummy-yummy-gingerbreak.html
You may want or need to compile these first which is going to add another level of complexity. Be patient.
The general idea is:
1.setup your drivers
2.get comfortable working with ADB
3.run temporary root
4.immediately flash recovery
5.immediately Nandroid backup everything in several places for safety
6.test Nandroid backup
7.make whatever modifications you like, including permanent root
That's not a lg phone.
Ok so I managed to install cyanogemod and everything's fine. now, I just wanna know, is there any way to enable multitouch on this thing? it's got a capacitive screen, but no multitouch. can that be fixed or is it really just a hardware issue?
Multitouch is not possible,a fake dual touch is possible.
Sent from my blek krupuk
lexobys said:
Multitouch is not possible,a fake dual touch is possible.
Sent from my blek krupuk
Click to expand...
Click to collapse
fake dual-touch?

[Q] Do I have a custom ROM and is it potentially causing my battery charging problem?

Hello, I'm a new owner of the AT&T HTC One X(L), purchased just yesterday from a previous owner. I'll try and make this thorough.
The problem is, I'm having a really hard time charging the device today after I let the battery drain all the way down from yesterday from when I purchased it. I've tried charging via USB to my laptop, directly to the wall, while its shut down, sleeping/idle, etc.. and nothing seems to get it charging quick at all. I'm using the stock HTC charger it came with, the previous owner had everything in the box and it's in great cosmetic condition.
The phone does charge some, but it was literally struggling to get between 20% and 35% for most of the day, and then later increased to 50% only to then drop back down again. And I haven't been using it at all, it's just sitting there trying to charge. How long should it reasonably take to charge this phone using the wall adapter?
Is there any chance the installed Android software (is there a custom ROM on the phone perhaps?) is causing this problem? The battery usage report says that 72% has been due to Android.. is that abnormally high by chance?
I've disabled all syncing, WiFi, screen brightness is on low, airplane mode, etc. In fact, the phone isn't even activated yet on my carrier. I've only used it thus far for WiFi at home, the browsing speed of which I'm happy with.
Some other stuff...
Recovery/bootloader reads:
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHP S-ON RL
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
Nov 26,2012
On the prior screen it also says "This build is for development purposes only, do not distribute outside of HTC, etc.." and then there's this little flashing "T" logo on the next white screen which shows up briefly before the phone boots up.
Any help would be much appreciated! Thanks for your time and patience.
You mentioned the "T" logo showing up during the boot process which leads me to believe it's running the T-Mobile Germany 4.2.2 stock ROM, which is technically a custom ROM in this context. The device should take about 3-4 hours to charge from zero to full. I personally think you've got a dodgy device. Have you contacted the seller regarding the issues you're having? Whoever had it previously didn't know what they were doing, it has a mismatched radio/firmware version for the ROM that's installed.
Sent from my Evita
timmaaa said:
You mentioned the "T" logo showing up during the boot process which leads me to believe it's running the T-Mobile Germany 4.2.2 stock ROM, which is technically a custom ROM in this context. The device should take about 3-4 hours to charge from zero to full. I personally think you've got a dodgy device. Have you contacted the seller regarding the issues you're having? Whoever had it previously didn't know what they were doing, it has a mismatched radio/firmware version for the ROM that's installed.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the reply. 3-4 hours from 0 to full is somewhat reassuring to hear, I assumed it wouldn't take more than an hour for some reason.
It's not the T-Mo "T" logo, it's a really different looking "T" that has a circle under it and the T flashes different colors. The T almost looks the same as the T in HTC. It only appears for a second or two and then the phone boots up. I need to take a picture of it with another device since it didn't work when I tried screen capturing that boot screen from the phone.
Is there anything else you can confirm one way or another from the info I've provided?
- So this isn't a different 3rd party custom ROM, just possibly one from T-Mo eventhough it's a branded ATT phone?
- Is this bootloader "unlocked" and is that why it says that and "tampered"? From what I've read, that's the standard msg it gives when that's the case, but isn't necessarily a red flag. Am I mistaken in my understanding though?
- Is 72% battery usage allocated to Android too high? If so, what should it be?
- Should I just try factory resetting it from the recovery screen?
droydr said:
Thanks for the reply. 3-4 hours from 0 to full is somewhat reassuring to hear, I assumed it wouldn't take more than an hour for some reason.
It's not the T-Mo "T" logo, it's a really different looking "T" that has a circle under it and the T flashes different colors. The T almost looks the same as the T in HTC. It only appears for a second or two and then the phone boots up. I need to take a picture of it with another device since it didn't work when I tried screen capturing that boot screen from the phone.
Is there anything else you can confirm one way or another from the info I've provided?
- So this isn't a different 3rd party custom ROM, just possibly one from T-Mo eventhough it's a branded ATT phone?
- Is this bootloader "unlocked" and is that why it says that and "tampered"? From what I've read, that's the standard msg it gives when that's the case, but isn't necessarily a red flag. Am I mistaken in my understanding though?
- Is 72% battery usage allocated to Android too high? If so, what should it be?
- Should I just try factory resetting it from the recovery screen?
Click to expand...
Click to collapse
Oh, I'm so dumb. I failed to look at your screenshots properly. The ROM that is installed is the Kickdroid ROM, which is a fully custom ROM that's based on the official Telstra release. The flashing T is the Telstra boot splash.
-Yes, if you see "unlocked" and "tampered" in your bootloader screen it means your bootloader is unlocked and you have root privileges. That's totally normal for a modified device.
-Under normal circumstances that amount of usage attributed to Android System world be considered high, but it all depends on how the phone is being used. If it's only been charging and nothing else has been active then I wouldn't worry very much.
-Under no circumstances should you ever perform a factory reset from the bootloader, it will corrupt your sd card. A factory reset should only be performed from within TWRP recovery, you can check if this is installed by selecting the recovery option from your bootloader. At this stage I don't think you should perform a factory reset until we've determined what you want from the device.
What would you like to get out of this device? Are you wanting to use custom ROMs or do you want to return it to stock?
Sent from my Evita
timmaaa said:
Oh, I'm so dumb. I failed to look at your screenshots properly. The ROM that is installed is the Kickdroid ROM, which is a fully custom ROM that's based on the official Telstra release. The flashing T is the Telstra boot splash.
-Yes, if you see "unlocked" and "tampered" in your bootloader screen it means your bootloader is unlocked and you have root privileges. That's totally normal for a modified device.
-Under normal circumstances that amount of usage attributed to Android System world be considered high, but it all depends on how the phone is being used. If it's only been charging and nothing else has been active then I wouldn't worry very much.
-Under no circumstances should you ever perform a factory reset from the bootloader, it will corrupt your sd card. A factory reset should only be performed from within TWRP recovery, you can check if this is installed by selecting the recovery option from your bootloader. At this stage I don't think you should perform a factory reset until we've determined what you want from the device.
What would you like to get out of this device? Are you wanting to use custom ROMs or do you want to return it to stock?
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the reply.
- Ok cool. I searched online for the Telstra logo and their T logo is for sure the one that I'm seeing. I'm assuming you don't suspect this to be the cause of the charging issue.
- So the device is unlocked and rooted, sounds fine as long as it isn't the source of the problem.
- I know this is a dumb question, but is there an ideal way for the phone to be charged? Does it need to be shut down completely for it to charge the fastest or even fully? Or can it be sleeping/idling and charge at the same rate? I've read about a variety of battery draining issues with respect to the HOX, but most are centered around WiFi and LTE uses where people were getting connected and disconnected which then caused a massive drain and bad overheating. I've yet to read something specifically about incredibly slow charging however.
My goals with this device:
- Just for it to function well and do the basics, I'm a very simple user.. calls, texts, and mild data use. I want to be able to charge it nightly within that 3-4 hour estimate and don't want any major battery issues and overheating. Today is literally my first full day with it and the first thing I needed to do was charge it, so I feel stuck at the beginning until this is resolved.
- I want to activate it on a wireless plan so it can really become my new phone, but I don't want to start this process if there's a permanent hardware or software issue with the device.
- I don't need to be on any custom ROM or on kitkat. I'm not a developer or anywhere close to being an Android wizard. I read that 4.2.2 is the last official update the HOX will receive, so I'd be absolutely fine with that. Sure, running kitkat or later Android versions might be nice down the road, but if it becomes clear that any custom ROM (now or in the future) is doing more damage than good, then I'd just want to be able to get it back to the 4.2.2 version HTC has released. I want to have that safety measure at bare minimum.
Under no circumstances should you ever perform a factory reset from the bootloader, it will corrupt your sd card. A factory reset should only be performed from within TWRP recovery, you can check if this is installed by selecting the recovery option from your bootloader. At this stage I don't think you should perform a factory reset until we've determined what you want from the device.
Ok thanks, I won't select the factory reset option from bootloader. However, I don't have an SD card in the phone and I don't think there's an SD slot on it unless I'm totally missing something?
I need to read about what TWRP recovery is and see if it's installed on my phone. Will need to get back to you on that once the phone has had more time to charge - I just want to let it sit undisturbed for 3-4 hours in shut down mode and see if it can increase past a 50% charge rate.
I only inquired about a factory reset thinking that it might be the safest way for me to start trying to troubleshoot the charging problem. It was just a random question I threw out there. I'm willing to do anything that could potentially improve my charging situation.
Whoever had it previously didn't know what they were doing, it has a mismatched radio/firmware version for the ROM that's installed.
- After reviewing my screenshots again, do you feel this is still the case? Is there mismatched software and radios afterall? And if so, would the factory reset via TWRP be one of your first suggestions to try and fix it?
- Do you think such mismatching software could potentially be the cause of its slow battery charging?
- Finally, is there any way for me to check to see if the battery itself is in good shape or faulty? Is there an app you could recommend I download where it can give me a detailed performance report which I could then share the results?
Thank you so much for your time, help, and continued patience.. it means a lot!
droydr said:
Thanks for the reply.
- Ok cool. I searched online for the Telstra logo and their T logo is for sure the one that I'm seeing. I'm assuming you don't suspect this to be the cause of the charging issue.
- So the device is unlocked and rooted, sounds fine as long as it isn't the source of the problem.
- I know this is a dumb question, but is there an ideal way for the phone to be charged? Does it need to be shut down completely for it to charge the fastest or even fully? Or can it be sleeping/idling and charge at the same rate? I've read about a variety of battery draining issues with respect to the HOX, but most are centered around WiFi and LTE uses where people were getting connected and disconnected which then caused a massive drain and bad overheating. I've yet to read something specifically about incredibly slow charging however.
Click to expand...
Click to collapse
The phone should charge fine while powered on, in fact I probably would recommend that because that way you can periodically check the progress. The slow charging could be due to a faulty battery or charger, not usually by a ROM though. The fact that it's unlocked should have absolutely nothing to do with it.
My goals with this device:
- Just for it to function well and do the basics, I'm a very simple user.. calls, texts, and mild data use. I want to be able to charge it nightly within that 3-4 hour estimate and don't want any major battery issues and overheating. Today is literally my first full day with it and the first thing I needed to do was charge it, so I feel stuck at the beginning until this is resolved.
- I want to activate it on a wireless plan so it can really become my new phone, but I don't want to start this process if there's a permanent hardware or software issue with the device.
- I don't need to be on any custom ROM or on kitkat. I'm not a developer or anywhere close to being an Android wizard. I read that 4.2.2 is the last official update the HOX will receive, so I'd be absolutely fine with that. Sure, running kitkat or later Android versions might be nice down the road, but if it becomes clear that any custom ROM (now or in the future) is doing more damage than good, then I'd just want to be able to get it back to the 4.2.2 version HTC has released. I want to have that safety measure at bare minimum.
Click to expand...
Click to collapse
You can leave Kickdroid on the phone, it will serve your needs and then some. However, you do need to do a little work to get the firmware up to date. You'll need to get s-off, which can be done pretty easily using the Rumrunner method. Then you need to flash the 2.15 firmware found in the beginning of this thread. You will need adb/fastboot installed on your PC, the easiest way is to Google search "minimal adb and fastboot", the first result will be the thread you're looking for. In order for adb/fastboot to work you need HTC drivers installed on your PC too, you can get those by installing HTC Sync Manager.
Under no circumstances should you ever perform a factory reset from the bootloader, it will corrupt your sd card. A factory reset should only be performed from within TWRP recovery, you can check if this is installed by selecting the recovery option from your bootloader. At this stage I don't think you should perform a factory reset until we've determined what you want from the device.
Ok thanks, I won't select the factory reset option from bootloader. However, I don't have an SD card in the phone and I don't think there's an SD slot on it unless I'm totally missing something?
Click to expand...
Click to collapse
There is no physical sd card slot. When people refer to the sd card we mean the virtual sd card (or internal storage).
I need to read about what TWRP recovery is and see if it's installed on my phone. Will need to get back to you on that once the phone has had more time to charge - I just want to let it sit undisturbed for 3-4 hours in shut down mode and see if it can increase past a 50% charge rate.
I only inquired about a factory reset thinking that it might be the safest way for me to start trying to troubleshoot the charging problem. It was just a random question I threw out there. I'm willing to do anything that could potentially improve my charging situation.
Click to expand...
Click to collapse
TWRP is a custom recovery that can be used for various tasks. You can make a full backup of your current system, you can restore a backup you've made. You can wipe the entire system (a task that takes place prior to flashing a ROM), or just parts. You can install a ROM, kernel, radio, or various other things.
Whoever had it previously didn't know what they were doing, it has a mismatched radio/firmware version for the ROM that's installed.
- After reviewing my screenshots again, do you feel this is still the case? Is there mismatched software and radios afterall? And if so, would the factory reset via TWRP be one of your first suggestions to try and fix it?
Click to expand...
Click to collapse
A factory reset won't help that issue, a factory reset basically removes all user data from the device. The mismatch is happening at a much lower level and can only be remedied by flashing the 2.15 firmware I mentioned above.
- Do you think such mismatching software could potentially be the cause of its slow battery charging?
Click to expand...
Click to collapse
No, I don't believe that is the case. Have you tried using a different charger and/or cable? It might be the charger that's the issue. You should only charge from an AC outlet as charging via usb from a PC or the like takes longer due to restrictions on the output.
- Finally, is there any way for me to check to see if the battery itself is in good shape or faulty? Is there an app you could recommend I download where it can give me a detailed performance report which I could then share the results?
Thank you so much for your time, help, and continued patience.. it means a lot!
Click to expand...
Click to collapse
I'm not familiar with any apps myself but I know there are many that claim to be able to report the health of the battery.
Sent from my Evita
timmaaa said:
You can leave Kickdroid on the phone, it will serve your needs and then some. However, you do need to do a little work to get the firmware up to date. You'll need to get s-off, which can be done pretty easily using the Rumrunner method. Then you need to flash the 2.15 firmware found in the beginning of this thread. You will need adb/fastboot installed on your PC, the easiest way is to Google search "minimal adb and fastboot", the first result will be the thread you're looking for. In order for adb/fastboot to work you need HTC drivers installed on your PC too, you can get those by installing HTC Sync Manager.
Click to expand...
Click to collapse
Thanks again for the reply and all the detail. This section appears to be my 'to do' list but I've been going around in circles with it for a few hours now with no results. The first problem is that Sync Manager on my computer won't recognize my device, it says no phone is plugged in yet my computer makes that alert sound when something new is connected via USB. I'm on a new Windows 8.1 laptop and can't figure it out for the life of me. Apparently this is an issue for others, as I've found out by cross reading HTC and Android forums about it. I don't know if there's some setting on the HOX itself I'm missing in order to start the sync process with my laptop or if it's a Windows issue, but I'm not getting anywhere.
I've read and followed the other pages you listed as well to do the S-off, ADB and fastboot, and ultimately the 2.15 firmware update, but even the 2nd step (S-off) fails because I can't get the darn Sync Mgr to work.
At this point, I would just like to get it back to how it was when the device was opened for the first time with Android 4.0.3. This is an AT&T branded phone for the USA, I don't want it to have anything to do with Telstra or Australian regions. I don't want any kind of custom ROM, radios, kernels, etc.
If I'm understanding you correctly, I can't factory reboot this to the way it originally came out of the box. By it being unlocked and rooted with technically a custom ROM, apparently it's past the point of no return.. I either get it to work via custom ROM or it'll be stuck as is.
I just want it to be true stock. And then once I'm comfortable with that and it's hopefully functioning better, I can then update it to the next Android releases that come directly from ATT. It's crazy how impossible that seems to achieve at this point.
droydr said:
Thanks again for the reply and all the detail. This section appears to be my 'to do' list but I've been going around in circles with it for a few hours now with no results. The first problem is that Sync Manager on my computer won't recognize my device, it says no phone is plugged in yet my computer makes that alert sound when something new is connected via USB. I'm on a new Windows 8.1 laptop and can't figure it out for the life of me. Apparently this is an issue for others, as I've found out by cross reading HTC and Android forums about it. I don't know if there's some setting on the HOX itself I'm missing in order to start the sync process with my laptop or if it's a Windows issue, but I'm not getting anywhere.
I've read and followed the other pages you listed as well to do the S-off, ADB and fastboot, and ultimately the 2.15 firmware update, but even the 2nd step (S-off) fails because I can't get the darn Sync Mgr to work.
At this point, I would just like to get it back to how it was when the device was opened for the first time with Android 4.0.3. This is an AT&T branded phone for the USA, I don't want it to have anything to do with Telstra or Australian regions. I don't want any kind of custom ROM, radios, kernels, etc.
If I'm understanding you correctly, I can't factory reboot this to the way it originally came out of the box. By it being unlocked and rooted with technically a custom ROM, apparently it's past the point of no return.. I either get it to work via custom ROM or it'll be stuck as is.
I just want it to be true stock. And then once I'm comfortable with that and it's hopefully functioning better, I can then update it to the next Android releases that come directly from ATT. It's crazy how impossible that seems to achieve at this point.
Click to expand...
Click to collapse
I should have been more clear, you don't actually want Sync Manager to work, you only wanted to install that to get the drivers. Your main obstacle is actually Windows 8.1, it isn't compatible with fastboot drivers. If you can get access to a PC with a lower version of Windows you should be fine. Then getting s-off should be pretty easy.
Kickdroid doesn't really have anything to do with the Australian region or Telstra as such. The dev merely used a Telstra ROM as a base to build Kickdroid onto.
Are you sure you actually want an at&t release? You may not be aware but at&t releases actually have features that are missing and deliberately broken. That's the only difference between running an at&t ROM and a non at&t ROM, you'll be missing features.
You can easily flash a ROM that is an earlier Android version without having to update the firmware on the device. You don't have to go back to ICS, anything that's from 4.0 up to and including 4.1 will be perfectly fine without any further modification. Have a look through our Android Development section and find one you think will suit you. There are plenty of ROMs in our development section that range from completely stock to customised. That's about as close to stock as you can get without getting s-off first.
Sent from my Evita
timmaaa said:
A factory reset should only be performed from within TWRP recovery, you can check if this is installed by selecting the recovery option from your bootloader.
Click to expand...
Click to collapse
I forgot to mention that I checked on this. When I selected Recovery from the bootloader screen, it took me to ClockworkMod Recovery v6.0.4.6 which I imagine you're familiar with in one way or another. It has 7 different options from its menu.. "reboot system now, install zip, wipe data/factory reset, wipe cache partition, backup and restore, mounts and storage, advanced". After researching it, I know it's a different app than TWRP so I didn't do anything with it per your advice.
You can use CWM if you want to, TWRP is better but it's entirely up to you. You can easily change by using this app:
https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools
Sent from my Evita
timmaaa said:
Kickdroid doesn't really have anything to do with the Australian region or Telstra as such. The dev merely used a Telstra ROM as a base to build Kickdroid onto.
Click to expand...
Click to collapse
Thanks for clearing that up. So it makes no difference if I have a Telstra or ATT logo on boot up. It just threw me for a loop is all because when you asked about it initially, I started thinking.. "yeah, why doesn't it have the ATT logo and does that have anything to do with my charging problem?"
timmaaa said:
Are you sure you actually want an at&t release? You may not be aware but at&t releases actually have features that are missing and deliberately broken. That's the only difference between running an at&t ROM and a non at&t ROM, you'll be missing features.
Click to expand...
Click to collapse
No, I'm not sure at all, that's why this is such a guessing game for me at this point. I'm just thinking that if I can just get things back to 'stock' first, then later I can move on and get involved in the custom ROM stuff if it sounds promising.
Ideally, I want to have freedom with my device and not be at the mercy of any carrier.. that's what interests me about Android to begin with, but right now I'm a little weary of what may be going on with my 'new' HOXL.
timmaaa said:
You can easily flash a ROM that is an earlier Android version without having to update the firmware on the device. You don't have to go back to ICS, anything that's from 4.0 up to and including 4.1 will be perfectly fine without any further modification. Have a look through our Android Development section and find one you think will suit you. There are plenty of ROMs in our development section that range from completely stock to customised. That's about as close to stock as you can get without getting s-off first.
Click to expand...
Click to collapse
Thanks, I will look at that section next. I like the idea that I can potentially get back to something earlier right now even with my current situation. I've been focused on trying to do all the steps you outlined yesterday to fix what I have currently. Of course I would like to be on the 'latest' ROM that makes the HOXL run most efficiently, but perhaps baby steps to start off with would be best.
My goal right now is to simply make sure all my software, firmware, radios, kernels match up. What you said in the beginning about my phone currently being mis-matched really stood out to me and I badly want to fix that. Logically, I absolutely must have a stable, synchronized OS at bare minimum.
droydr said:
Thanks for clearing that up. So it makes no difference if I have a Telstra or ATT logo on boot up. It just threw me for a loop is all because when you asked about it initially, I started thinking.. "yeah, why doesn't it have the ATT logo and does that have anything to do with my charging problem?"
No, I'm not sure at all, that's why this is such a guessing game for me at this point. I'm just thinking that if I can just get things back to 'stock' first, then later I can move on and get involved in the custom ROM stuff if it sounds promising.
Ideally, I want to have freedom with my device and not be at the mercy of any carrier.. that's what interests me about Android to begin with, but right now I'm a little weary of what may be going on with my 'new' HOXL.
Thanks, I will look at that section next. I like the idea that I can potentially get back to something earlier right now even with my current situation. I've been focused on trying to do all the steps you outlined yesterday to fix what I have currently. Of course I would like to be on the 'latest' ROM that makes the HOXL run most efficiently, but perhaps baby steps to start off with would be best.
My goal right now is to simply make sure all my software, firmware, radios, kernels match up. What you said in the beginning about my phone currently being mis-matched really stood out to me and I badly want to fix that. Logically, I absolutely must have a stable, synchronized OS at bare minimum.
Click to expand...
Click to collapse
The mismatch I mentioned earlier exists only for 4.2.2 ROMs, basically any 4.2.2 ROM requires a certain set of firmware to be installed otherwise the phone will suffer signal losses and random reboots.
As another easier option you could just install the Beastmode Reloaded kernel, which is also a workaround for those problems. That way you can keep the ROM that's already installed and be up to date.
Sent from my Evita
timmaaa said:
The mismatch I mentioned earlier exists only for 4.2.2 ROMs, basically any 4.2.2 ROM requires a certain set of firmware to be installed otherwise the phone will suffer signal losses and random reboots.
As another easier option you could just install the Beastmode Reloaded kernel, which is also a workaround for those problems. That way you can keep the ROM that's already installed and be up to date.
Sent from my Evita
Click to expand...
Click to collapse
I found this thread, I assume this is what you're talking about?
http://forum.xda-developers.com/showthread.php?t=2165880
I see on page 73 the link for the 3.5 version. Now I need to figure out how to install this. Do I first DL something onto my computer and then send it to the phone somehow with the USB cable, or am I suppose to do this directly on the HOXL? I've never flashed or installed anything like this before. I'll I've done thus far is install some apps from Google Play.
Yes that's the right one. You can download it directly to the phone, or download it to the PC and transfer it to the phone.
If downloading it to your PC and using TWRP recovery, you can connect your phone to the PC using a usb cable, select mount from the TWRP main menu, then select mount usb storage and your phone will show up as a removable drive on your PC. Copy the file across, eject the removable drive, unmount usb storage from the phone screen and then you can install.
Go back to the TWRP home screen and select install, navigate to the file and select it, swipe to install (at this point an aroma installer will commence, select the options you would like, don't let it reboot system at the end), select wipe cache/dalvik, swipe to wipe, hit back, hit reboot system. Now the phone will reboot into the OS again and that's it.
Sent from my Evita
timmaaa said:
Yes that's the right one. You can download it directly to the phone, or download it to the PC and transfer it to the phone.
If downloading it to your PC and using TWRP recovery, you can connect your phone to the PC using a usb cable, select mount from the TWRP main menu, then select mount usb storage and your phone will show up as a removable drive on your PC. Copy the file across, eject the removable drive, unmount usb storage from the phone screen and then you can install.
Go back to the TWRP home screen and select install, navigate to the file and select it, swipe to install (at this point an aroma installer will commence, select the options you would like, don't let it reboot system at the end), select wipe cache/dalvik, swipe to wipe, hit back, hit reboot system. Now the phone will reboot into the OS again and that's it.
Sent from my Evita
Click to expand...
Click to collapse
I downloaded the 3.5 zip file from page 73 directly to my phone.
And then I followed your install instructions exactly and now my phone keeps turning on and off without being able to boot all the way. It starts on the white "T" logo Telstra screen and then goes to the white HTC screen and then turns off again. It's been doing this nonstop for the last 20 minutes or so now. I'm assuming I have a big problem? The device is unusable at this point, it just keeps turning on and off and is getting very warm all over.
droydr said:
I downloaded the 3.5 zip file from page 73 directly to my phone.
And then I followed your install instructions exactly and now my phone keeps turning on and off without being able to boot all the way. It starts on the white "T" logo Telstra screen and then goes to the white HTC screen and then turns off again. It's been doing this nonstop for the last 10 minutes or so. I'm assuming I have a problem? The device is unusable at this point, it just keeps turning on and off.
Click to expand...
Click to collapse
There are a small number of devices for which Beastmode isn't compatible, it looks like you've lucked out and have one of those devices. Out of interest, which settings did you choose during the installer?
You can get out of the boot loop by just continuing to hold the volume down button, the next time the loop starts it should enter the bootloader.
At this point you have no choice but to flash another ROM, so I'd head to the development section I linked you to earlier and find a 4.1 ROM that you think you might like and flash that.
PS. I noticed you posted the same thing in the Beastmode thread too, duplicate posts are against the rules here on XDA.
Sent from my Evita
---------- Post added at 03:29 AM ---------- Previous post was at 03:24 AM ----------
Because you're s-on you are going to need to get access to a PC that runs a lower version of Windows, you need to have a working adb/fastboot environment. Flashing a ROM is going to require you to also flash the boot.img from the ROM zip using fastboot, this is a limitation on s-on devices with a hboot later than 1.14.
Sent from my Evita
timmaaa said:
There are a small number of devices for which Beastmode isn't compatible, it looks like you've lucked out and have one of those devices. Out of interest, which settings did you choose during the installer?
You can get out of the boot loop by just continuing to hold the volume down button, the next time the loop starts it should enter the bootloader.
At this point you have no choice but to flash another ROM, so I'd head to the development section I linked you to earlier and find a 4.1 ROM that you think you might like and flash that.
PS. I noticed you posted the same thing in the Beastmode thread too, duplicate posts are against the rules here on XDA.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the reply. I wasn't sure you were going to see this anytime soon, so I wanted to post it in that kernel thread as well just in case anyone was reading over there. I apologize for that.
I chose the default settings during installation.
Anyway, I've been holding down the volume button now for the last few minutes and it's not entering bootloader. The loop continues.
There's no other way to get to the bootloader apart from holding volume down or trying the volume down + power combination. I also added a little to my previous post which you'll need to read.
Sent from my Evita
timmaaa said:
There's no other way to get to the bootloader apart from holding volume down or trying the volume down + power combination. I also added a little to my previous post which you'll need to read.
Sent from my Evita
Click to expand...
Click to collapse
I saw the added parts, thanks. Problem is, this forum isn't allowing me to post or edit my previous posts until 5 mins have past, so it's a struggle trying to communicate.
I've also edited my post in the beastmode thread.
Anyway, I finally got into bootloader with the volume + power combo. Feels good to at least achieve that.
FYI, my bootloader screen looks the same as when I first got the phone a few days ago. Just wanted to include this info here.
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHP S-ON RL
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
Nov 26,2012
Just curious, now that I'm in bootloader, would it do me any good if I selected Recovery so it can then take me to Clockwork? And from there I could try rebooting? Or one of the other menu options?
At this point you have no choice but to flash another ROM, so I'd head to the development section I linked you to earlier and find a 4.1 ROM that you think you might like and flash that.
Because you're s-on you are going to need to get access to a PC that runs a lower version of Windows, you need to have a working adb/fastboot environment. Flashing a ROM is going to require you to also flash the boot.img from the ROM zip using fastboot, this is a limitation on s-on devices with a hboot later than 1.14.
Click to expand...
Click to collapse
I've found this ROM which looks fine. I'm not picky. I'd be happy with anything as long as it can get my device to function again.
http://forum.xda-developers.com/showthread.php?t=2244445
If there's a better 4.1 ROM you'd like to suggest, please feel free to do so.

[Q] USB burnet, phone half bricked, please help

Hello all,
I have had an MB865 (Atrix 2) for the last 3 years and one unfortunate day I burnet the USB communications chip inside. I could still charge the phone through the USB plug, but the communications were not possible since this moment on. I decided to risk it and upgrade the phone to Cyanogenmod unofficial release. I started doing that with the bootloader workaround app and in the process the phone got bricked -- only shows the large motorola badge in the beginning, but instead of loading normally it shows this for as long as the battery would last. I can still boot in fastboot with the buttons and load recovery.
What I have done so far in an attempt to salvage the phone:
1. Tried the procedure, listed on Motorola support web page for it -- the option if something goes wrong -- got the sdcard file, it gives me an error upon attempt to update. The error is "assert failed" and it shows a couple if files and then a "<filename>:user/release keys" - E: Error in /tmp/sideload/package.zip...
2. Tried all available flush images in the Motorola development site.
3. Tried flushing with some other downloaded files, apparently not official releases or not recognized as sdcard images.
Questions:
1. Is there a method of flushing (unlocking) the bootloader through fastboot (noUSB)?
2. If not (1), is there an official 2.3.5 sdcard file that anyone can point me to download and try to update throiugh sd card?
3. Is there any solution I have not thought of except sending the phone to Motorola (which would be pointless, since they would want me to pay more than I paid for the phone itself)?
Thanks in advance!
Drive4fun!
drive4fun said:
Hello all,
I have had an MB865 (Atrix 2) for the last 3 years and one unfortunate day I burnet the USB communications chip inside. I could still charge the phone through the USB plug, but the communications were not possible since this moment on. I decided to risk it and upgrade the phone to Cyanogenmod unofficial release. I started doing that with the bootloader workaround app and in the process the phone got bricked -- only shows the large motorola badge in the beginning, but instead of loading normally it shows this for as long as the battery would last. I can still boot in fastboot with the buttons and load recovery.
What I have done so far in an attempt to salvage the phone:
1. Tried the procedure, listed on Motorola support web page for it -- the option if something goes wrong -- got the sdcard file, it gives me an error upon attempt to update. The error is "assert failed" and it shows a couple if files and then a "<filename>:user/release keys" - E: Error in /tmp/sideload/package.zip...
2. Tried all available flush images in the Motorola development site.
3. Tried flushing with some other downloaded files, apparently not official releases or not recognized as sdcard images.
Questions:
1. Is there a method of flushing (unlocking) the bootloader through fastboot (noUSB)?
2. If not (1), is there an official 2.3.5 sdcard file that anyone can point me to download and try to update throiugh sd card?
3. Is there any solution I have not thought of except sending the phone to Motorola (which would be pointless, since they would want me to pay more than I paid for the phone itself)?
Thanks in advance!
Drive4fun!
Click to expand...
Click to collapse
1. The bootloader cannot be unlocked at all. USB or not.
2. The official update.zip files won't flash unless you're on stock, unmodified, unrooted ROMs.
3. No USB connection = no fastboot and/or FXZ flashing. It's as good as a hard brick unless you can replace the USB module inside the phone. It'd be much cheaper than purchasing a new device.
Thanks fro your quick reply...
1BadWolf said:
1. The bootloader cannot be unlocked at all. USB or not.
2. The official update.zip files won't flash unless you're on stock, unmodified, unrooted ROMs.
3. No USB connection = no fastboot and/or FXZ flashing. It's as good as a hard brick unless you can replace the USB module inside the phone. It'd be much cheaper than purchasing a new device.
Click to expand...
Click to collapse
Thanks again for you reply, 1BadWolf!
My thoughts were going in that direction, but I was hoping for a chance of some kind.
I figured I need to replace the whole main board, since the board is not modularized in MB865. I looked for some here and there and I might have a chance. Unfortunately nobody can guarantee you if the phones, which are usually sold for parts would have a good board, but I gotta try. The hardware on this phone is so good, that it is worth spending the time and money. I bought a Moto G to play with, but its camera doesn't seem to be as good as the one on the Atrix 2 and it doesn't have the HDMI port, although for Android development play is good enough and with DLNA server on it you can actually watch content in TV.

No operating system found.

Totally new to xda forum, and pretty much a noob. Nexus 5 (US model). I was trying to unroot my Nexus 5. I bought it from a friend who had rooted it using TWRP, and it was running CM. Anyway, I managed to completely wipe the operating system ... completely. It will boot using the power/volume down configuration, but when I try to start the phone, it says, "No operating system found." All the threads I have been reading (yes, I have done a lot of reading), assume a couple of things: 1) that the phone can get into Settings/Developer Mode; and, 2) that my PC finds my phone when I plug it in. I have tried the adb and fastboot driver downloads, and wound up with some weird app that was almost impossible to uninstall off my PC. Ten-something or other. I tried doing the flash-all thing, but got a message that there was no such command. Can anyone help me, either directly, or by links to what I need? Once again, I have no operating system on this phone. Thanks.
There's a cool tool kit called wugs nexus toolkit that will help some http://forum.xda-developers.com/showthread.php?t=1766475
Sent from my Nexus 5 using Tapatalk
---------- Post added at 01:04 AM ---------- Previous post was at 12:59 AM ----------
Also, here's mostly all the roms stock & custom here: http://forum.xda-developers.com/goo...dex-google-nexus-5-roms-kernels-mods-t2475401
Did you say you can still get into recovery? Because there's an unroot rom thats flashable somewhere... Itd take you to stock everything.....
Sent from my Nexus 5 using Tapatalk
I second that recommendation. With a caveat. Wugfresh's Nexus Root Toolkit is a superb piece of programming which should enable you to set up your PC with all the necessary drivers and also let you specify the ROM you want to install, download it for you, and install it. You should obviously take the latest MMB29V.
But...
I see that you've done a lot of reading, and I understand that Android is initlally hard to grasp, but please don't (a) think you'll never understand it and (b) think that NRT is the answer to all your problems - it isn't. There are lots of reports of people saying "NRT has broken my phone" either because the've used it incorrectly or because they've used it before Wug has had a chance to update it to cater for all the latest tweaks that Google have introduced (particularly on Marshmallow root). If you're careful, set up your drivers properly, and install the correct version for your phone (Hammerhead MMB29V), NRT should give you back a working phone. But after that, read more, and investigate manual update methods, which are particularly useful for installing the monthly security updates without losing your data or waiting for the OTA (over-the-air) rollout from Google.
In fastboot, but can't flash operating system
dahawthorne said:
I second that recommendation. With a caveat. Wugfresh's Nexus Root Toolkit is a superb piece of programming which should enable you to set up your PC with all the necessary drivers and also let you specify the ROM you want to install, download it for you, and install it. You should obviously take the latest MMB29V.
But...
I see that you've done a lot of reading, and I understand that Android is initlally hard to grasp, but please don't (a) think you'll never understand it and (b) think that NRT is the answer to all your problems - it isn't. There are lots of reports of people saying "NRT has broken my phone" either because the've used it incorrectly or because they've used it before Wug has had a chance to update it to cater for all the latest tweaks that Google have introduced (particularly on Marshmallow root). If you're careful, set up your drivers properly, and install the correct version for your phone (Hammerhead MMB29V), NRT should give you back a working phone. But after that, read more, and investigate manual update methods, which are particularly useful for installing the monthly security updates without losing your data or waiting for the OTA (over-the-air) rollout from Google.
Click to expand...
Click to collapse
I'm in the fastboot mode, and I can get into TWRP, but I can't get my PC to recognize the phone. I've followed every rabbit trail I can find, but the phone doesn't show up. The USB ports are fine, and all the USB drivers are up to date. This is what is on my phone screen:
FASTBOOT MODE
PRODUCT NAME - hammerhead
VARIANT - hammerhead D820(E) 32GB
HW VERSION - rev. 11
BOOTLOADER VERSION - HHZ12k
The rest is serial number and so forth. I can get into TWRP, but can't ADB Sideload because the phone is not showing up. Giving me an error 43.
" I've followed every rabbit trail"
Have you followed this one?
"Wugfresh's Nexus Root Toolkit"
kakid56 said:
Totally new to xda forum, and pretty much a noob. Nexus 5 (US model). I was trying to unroot my Nexus 5. I bought it from a friend who had rooted it using TWRP, and it was running CM. Anyway, I managed to completely wipe the operating system ... completely. It will boot using the power/volume down configuration, but when I try to start the phone, it says, "No operating system found." All the threads I have been reading (yes, I have done a lot of reading), assume a couple of things: 1) that the phone can get into Settings/Developer Mode; and, 2) that my PC finds my phone when I plug it in. I have tried the adb and fastboot driver downloads, and wound up with some weird app that was almost impossible to uninstall off my PC. Ten-something or other. I tried doing the flash-all thing, but got a message that there was no such command. Can anyone help me, either directly, or by links to what I need? Once again, I have no operating system on this phone. Thanks.
Click to expand...
Click to collapse
Yup use wugfresh toolkit ... download the factory image https://developers.google.com/android/nexus/images#hammerhead
and boot into bootloader.. then u knw what to do
kakid56 said:
I'm in the fastboot mode, and I can get into TWRP, but I can't get my PC to recognize the phone. I've followed every rabbit trail I can find, but the phone doesn't show up. The USB ports are fine, and all the USB drivers are up to date. This is what is on my phone screen:
FASTBOOT MODE
PRODUCT NAME - hammerhead
VARIANT - hammerhead D820(E) 32GB
HW VERSION - rev. 11
BOOTLOADER VERSION - HHZ12k
The rest is serial number and so forth. I can get into TWRP, but can't ADB Sideload because the phone is not showing up. Giving me an error 43.
Click to expand...
Click to collapse
I don't disagree with the NRT suggestion but am confused. Sorry if I'm missing something obvious. When you are in the bootloader, do you get a cmd response from "fastboot devices" (no quotes in the command)? ADB doesn't work from the bootloader as you probably know, but since you identify as a noob, thought I'd throw it out there. You can flash the system using fastboot commands if your PC recognizes (part of the confusion) the device in fastboot. If not, then you do need to get the drivers set up. If you just need adb/fastboot drivers, I recommend this which I used recently when NRT didn't seem to have the SDK version I needed for my N9 to sideload the latest OTA. Since it installs at the system level, you can place flashable files at the root of C rather than in a specific platform-tools folder. I'm on Windows 10; don't know if that makes any difference for this minimal install. As far as the flash-all. bat not working, that's not uncommon; the files can be extracted and flashed separately.
Sent from my Nexus 9 using Tapatalk

Categories

Resources