Related
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
Hello all
I suspect that either my Nexus has a hardware fault (internal memory) or I bricked it somehow.
For the past few weeks the phone has been getting stuck on the google boot screen quite a lot - It takes several attempts
to start up each time so I've been trying to keep the battery from running down.
The other day while I was attempting to switch roms I put the stock img on my SD card but when I went to flash it CWM
couldnt mount my (internal) SD Card. Senior forum member Caliban2 suggested that it could be my recovery so I installed CWM 6.0.0.7 non-touch using fastboot and, like magic, the phone started up -though I suspect this may have been luck.
I rebooted the phone out of curiosity and it got stuck on the google boot screen - no amount of battery pulling and restarting could coax
it back to life, so I went into CWM again to discover that it could not mount the SD Card, I was getting the 'cannot mount' and 'E:Unable to open ums lunfile(no such file or directory)' error messages. My windows 7 PC could see the phone but said that their was non memory inserted. Out of curiosity I installed CWM 5.0.2.0 but that produced the same results.
So now my phone appears dead, is the internal memory or something related to it is broken? I have seen things on here about using an unbricking tool in Debian Linux or flashing stock using odin but I confess that I have not tried these solutions and don't fully understand them (yet).I wussed out and dropped the phone into a local repair workshop, I imagine they will be trying these same steps themselves and they say it will take them a few days to get back to me.
My problem is that I need a phone for work and I gave my backup phone (HTC Hero) to my dad recently. Should I just take the plunge
and go out today and buy a new phone? Or is there a reasonable chance that these guys can fix my nexus s, or that I might be able to?
I'm a relative 'noob' at this so I thank you all for your advice in advance, it's much appreciated.
Derek
Do a search for flashing fastboot images. Download the 4.0.4 fastboot image from google and flash it as directed through fastboot. This may sort out your problems.
Afterward, if necessary, format the /sdcard too. I would do this afterward so that maybe you can get a backup of all the stuff on it before it's gone forever.
Thanks, will do. It's in the shop at the moment, I suspect this is probably what they're doing now.
Perhaps subconsciously I'm just looking for someone to tell me it's irreparable so I can rush out
and pick up a Galaxy Nexus.
Harbb said:
Do a search for flashing fastboot images. Download the 4.0.4 fastboot image from google and flash it as directed through fastboot. This may sort out your problems.
Afterward, if necessary, format the /sdcard too. I would do this afterward so that maybe you can get a backup of all the stuff on it before it's gone forever.
Click to expand...
Click to collapse
Hey Harbb
Just wanted to give you an update on this, got it back from the shop who said they would need to send it to Samsung for a hardware repair, didn't expect it to work but fastbooted the stock bootloader, radio and image to the device and it's now working!
I've already moved onto a Galaxy Nexus on contract but at least now I can make a bit of money back off my old phone.
Thanks again for the advice
Derek
Harbb said:
Do a search for flashing fastboot images. Download the 4.0.4 fastboot image from google and flash it as directed through fastboot. This may sort out your problems.
Afterward, if necessary, format the /sdcard too. I would do this afterward so that maybe you can get a backup of all the stuff on it before it's gone forever.
Click to expand...
Click to collapse
Hi Guys.
I'm at my wit's end with a new Huawei Honor I received for Christmas. It comes with Gingerbread 2.3.6 preloaded but you can upgrade to ICS 4.0.3. It's my first android phone so I didn't really know what I was doing but I decided I'd upgrade.
It said I could upgrade my phone up to ICS 4.0.3 from Gingerbread 2.3.6 so I was keen as it seemed like the obvious choice. I didn't download any custom ROM or anything like that, nor did I root the phone because
A) I didn't know how
and
B) I didn't want to make a bollocks of my first smartphone 2 days after getting it.
I was also wary about where I got these upgrades from and so only used upgrade files from the official Huawei site. First off I tried using the ICS upgrade offered on the Huawei website for my phone.
That's where I ran into problems. Every update (bar the wrong one, in keeping with my luck) gets to about 25% (There's no percentage bar, only a pink line) and says update failed and I have no choice other than to take out the battery and restart the phone. It doesn't do the phone any damage but it doesn't update either.
The update that actually worked is for a non-camera version of my phone that I didn't even know existed. I must have mixed up the two while downloading. That explains why the camera doesn't work but I don't know why my contacts deleted (Backed up prior to upgrade) or my cellular internet service is completely gone.
I tried downgrading back to 2.3.6 with the official Huawei file again but ran into the same UPDATE FAILED! problems as with the installation of the correct ICS file.
Downloading process was;
(1) Downloading the file to my computer
(2) Unzipping it
(3) Transferring across to the phone by USB into a folder entitled "dload"
(4) Going into Settings > Storage > Software Upgrade > SD Card Upgrade
The phone then restarts before getting to around 25% complete and inevitably failing.
I just want it back working on Gingerbread. If it can work on ICS then great I'm not too pushed. I just want to be able to take photos and tweet/check football scores on the go again. I'd like my contacts back too but I'd say that's a lost cause at this stage. Just annoyed that I made such a mess of it trying to upgrade when there was nothing wrong with it in the first place.
I tried linking to the download files but as a new user I can't external link. All the files are the U8860 files from huawei device dot com though.
Any help you guys and gals could give me would be very much appreciated.
Gnicireland said:
Hi Guys.
I'm at my wit's end with a new Huawei Honor I received for Christmas. It comes with Gingerbread 2.3.6 preloaded but you can upgrade to ICS 4.0.3. It's my first android phone so I didn't really know what I was doing but I decided I'd upgrade.
It said I could upgrade my phone up to ICS 4.0.3 from Gingerbread 2.3.6 so I was keen as it seemed like the obvious choice. I didn't download any custom ROM or anything like that, nor did I root the phone because
A) I didn't know how
and
B) I didn't want to make a bollocks of my first smartphone 2 days after getting it.
I was also wary about where I got these upgrades from and so only used upgrade files from the official Huawei site. First off I tried using the ICS upgrade offered on the Huawei website for my phone.
That's where I ran into problems. Every update (bar the wrong one, in keeping with my luck) gets to about 25% (There's no percentage bar, only a pink line) and says update failed and I have no choice other than to take out the battery and restart the phone. It doesn't do the phone any damage but it doesn't update either.
The update that actually worked is for a non-camera version of my phone that I didn't even know existed. I must have mixed up the two while downloading. That explains why the camera doesn't work but I don't know why my contacts deleted (Backed up prior to upgrade) or my cellular internet service is completely gone.
I tried downgrading back to 2.3.6 with the official Huawei file again but ran into the same UPDATE FAILED! problems as with the installation of the correct ICS file.
Downloading process was;
(1) Downloading the file to my computer
(2) Unzipping it
(3) Transferring across to the phone by USB into a folder entitled "dload"
(4) Going into Settings > Storage > Software Upgrade > SD Card Upgrade
The phone then restarts before getting to around 25% complete and inevitably failing.
I just want it back working on Gingerbread. If it can work on ICS then great I'm not too pushed. I just want to be able to take photos and tweet/check football scores on the go again. I'd like my contacts back too but I'd say that's a lost cause at this stage. Just annoyed that I made such a mess of it trying to upgrade when there was nothing wrong with it in the first place.
I tried linking to the download files but as a new user I can't external link. All the files are the U8860 files from huawei device dot com though.
Any help you guys and gals could give me would be very much appreciated.
Click to expand...
Click to collapse
I think you'll have to use this downgrade patch first, before you can go back to gingerbread.
http://forum.xda-developers.com/showthread.php?p=33000395&highlight=b930+downgrade#post33000395
after you download the upgrade patch, its just the same as installing any other firmware.
1) copy the dload folder to sd card
2) go to settings and disable fast boot
3) shut down phone
4) start the phone while holding the + and - and power button at the same time
if you did all this, then normally you'll get a screen that says firmware upgrade. If this is finished, download the official gingerbread rom or ice cream sandwich rom from the huawei device site, and do the process all over again.
and if you really want ice cream sandwich, I recommend to follow this after you have your gingerbread working again:
http://www.teamandroid.com/2012/08/01/update-huawei-u8860-android-403-ics-official-firmware/
hope it helps!
vincentdecaster said:
I think you'll have to use this downgrade patch first, before you can go back to gingerbread.
http://forum.xda-developers.com/showthread.php?p=33000395&highlight=b930+downgrade#post33000395
after you download the upgrade patch, its just the same as installing any other firmware.
1) copy the dload folder to sd card
2) go to settings and disable fast boot
3) shut down phone
4) start the phone while holding the + and - and power button at the same time
if you did all this, then normally you'll get a screen that says firmware upgrade. If this is finished, download the official gingerbread rom or ice cream sandwich rom from the huawei device site, and do the process all over again.
and if you really want ice cream sandwich, I recommend to follow this after you have your gingerbread working again:
http://www.teamandroid.com/2012/08/01/update-huawei-u8860-android-403-ics-official-firmware/
hope it helps!
Click to expand...
Click to collapse
Thank you very much. I could really have used you last night. Unfortunately I followed the advice of someone else who seemed like they knew what they were talking about on a different forum. I rooted the phone and was told to replace a file in the image folder to get cwm. I did everything he said to and now I can only access pink screen although my device is not recognized on the computer despite downloading the abd drivers. I get an error message reading "Image signature verify fail" A similar problem has come up a few times on a couple of different forums on here but none of the solutions suggested have worked for me.
I know that ye lads are developers not a free help service but everyone on the other forums suggested I ask here as you guys mess around with mod ROMs so much getting back to stock would be child's play.
Basically now I'm stuck with:
A rooted Huawei U8860
An "Image signature verify fail" warning
ICS software that is for a slightly different make to mine causing bugs
Access only to pink screen
No recovery mode
A phone that is not recognised when connected to my computer by USB in pink screen mode
I've tried searching a good few terms such as "Huawei U8860 firmware update fail" "ABD not recognised by PC" "Huawei Honor ABD files" all of which have brought me no joy.
Like I said I know yous like modifying ROMs and not helping Android noobs who can't even read what they're downloading but I'm really stuck here. The closest place to my house that is certified to fix Huawei phones is a good 20+ miles away and they want €30 with no guarantee they'll be able to fix it. I'm a music student I just can't afford it. Thank you again and hopefully you can help me a bit further with this nightmare. It's been like this since a couple of days after Christmas.
Gnicireland said:
Thank you very much. I could really have used you last night. Unfortunately I followed the advice of someone else who seemed like they knew what they were talking about on a different forum. I rooted the phone and was told to replace a file in the image folder to get cwm. I did everything he said to and now I can only access pink screen although my device is not recognized on the computer despite downloading the abd drivers. I get an error message reading "Image signature verify fail" A similar problem has come up a few times on a couple of different forums on here but none of the solutions suggested have worked for me.
I know that ye lads are developers not a free help service but everyone on the other forums suggested I ask here as you guys mess around with mod ROMs so much getting back to stock would be child's play.
Basically now I'm stuck with:
A rooted Huawei U8860
An "Image signature verify fail" warning
ICS software that is for a slightly different make to mine causing bugs
Access only to pink screen
No recovery mode
A phone that is not recognised when connected to my computer by USB in pink screen mode
I've tried searching a good few terms such as "Huawei U8860 firmware update fail" "ABD not recognised by PC" "Huawei Honor ABD files" all of which have brought me no joy.
Like I said I know yous like modifying ROMs and not helping Android noobs who can't even read what they're downloading but I'm really stuck here. The closest place to my house that is certified to fix Huawei phones is a good 20+ miles away and they want €30 with no guarantee they'll be able to fix it. I'm a music student I just can't afford it. Thank you again and hopefully you can help me a bit further with this nightmare. It's been like this since a couple of days after Christmas.
Click to expand...
Click to collapse
hmm, I think I can help you with that.
you'll need an SD card reader, but basically every laptop has one nowadays. so, if you can access your SD card on the pc,
1)put the dload folder of the ICS non-camera version you used on the SD card
2)then put it back in the phone
3)hold the + and - volume buttons and power button in until the firmware installation starts
if that worked, you'll be able to do the steps I said earlier to go back to gingerbread.
good luck!
vincentdecaster said:
hmm, I think I can help you with that.
you'll need an SD card reader, but basically every laptop has one nowadays. so, if you can access your SD card on the pc,
1)put the dload folder of the ICS non-camera version you used on the SD card
2)then put it back in the phone
3)hold the + and - volume buttons and power button in until the firmware installation starts
if that worked, you'll be able to do the steps I said earlier to go back to gingerbread.
good luck!
Click to expand...
Click to collapse
No that didn't work unfortunately. It won't go to the installation screen it will only go to pink screen when I do Power + -
Gnicireland said:
No that didn't work unfortunately. It won't go to the installation screen it will only go to pink screen when I do Power + -
Click to expand...
Click to collapse
and does it help if you take out your battery for about 10-12 mins ?
vincentdecaster said:
and does it help if you take out your battery for about 10-12 mins ?
Click to expand...
Click to collapse
Nope that doesn't work either. I've had to send it back to Huawei to be repaired. I appreciate the help though. I'll thank your posts.
Hi, folks,
After many, many attempts, I finally was able to root my Verizon LG Enact/VS890/FX3, using NewKingrootV4.50_C120_B220_xda_release_2015_07_22_105243.apk, which I got from this forum about a week ago... for which I heartily thank Zero Sparks. Finally able to uninstall a lot of the crapware I didn't want, and to install several root-only apps which I did want.
The thing I'm having trouble with now, is finding custom ROMs for the phone. It's running KitKat, so it's not ancient, and if I can't use anything but the stock ROM, so be it. But I'm dying to try flashing Lollipop or even Marshmallow. It has to be a very specific ROM for that phone, because of the slide-out QWERTY keyboard... the wrong firmware wouldn't function properly. And there are a lot of bogus sites out there which want you to "complete a survey" or "sign up for one of these offers", but they never give you the download, it's just an endless circle of phishing sites... with lots of malware for my system, I'm sure. I'd much rather trust you folks on here, if you have anything.
I'm in the same boat, would love to upgrade off of 4.1.2 but can't find anything to use.
Additionally, a previous owner (bought off ebay) apparently unlocked the bootloader and replaced the stock recovery with something I don't recognize. When holding down power and vol down I see this:
Rooted
*********************************************
FACTORY HARD RESET
*********************************************
Permanently Erase User Data & Reset Settings?
Press Power key to confirm, and Volume Down or Up key to cancel
So not only can't I find a ROM to use, I can't even upgrade the stock ROM due to it not passing the root check. And I can't use stock recovery since it was replaced by the above. Anyone see this before?
I wish there was better support for the VS890 around, but I can't even find the original recovery / ROM image to flash.
UsualNoise said:
I'm in the same boat, would love to upgrade off of 4.1.2 but can't find anything to use.
Additionally, a previous owner (bought off ebay) apparently unlocked the bootloader and replaced the stock recovery with something I don't recognize. When holding down power and vol down I see this:
Rooted
*********************************************
FACTORY HARD RESET
*********************************************
Permanently Erase User Data & Reset Settings?
Press Power key to confirm, and Volume Down or Up key to cancel
So not only can't I find a ROM to use, I can't even upgrade the stock ROM due to it not passing the root check. And I can't use stock recovery since it was replaced by the above. Anyone see this before?
I wish there was better support for the VS890 around, but I can't even find the original recovery / ROM image to flash.
Click to expand...
Click to collapse
In my research, I could have sworn I came across a site that had the original "stock" LG software for download, but I can't find it now. The closest I come is this LG link that will give you the firmware -- and the VS890 is on their list: http://www.mylgphones.com/latest-lg-phones-firmware-update-model-version-date
I don't know if that might restore your stock recovery, at least. But have you tried doing the "factory reset" they offer, in this recovery app? Typically, this often restores the phone to whatever it was shipped with... which in your case, is just what you want. And there might be a method out there to un-root, I've seen that option in some of the better apps, like the "LG One-Click Root" found here. Then (if you're on Verizon, anyway), you could snag the OTA upgrade to 4.4.2, like I have... and root it again with the method I found.
ADDED LATER: Look in SuperSU, you should find an option for Permanent UnRoot.
Mr2nSmith said:
But have you tried doing the "factory reset" they offer, in this recovery app? Typically, this often restores the phone to whatever it was shipped with... which in your case, is just what you want. And there might be a method out there to un-root, I've seen that option in some of the better apps, like the "LG One-Click Root" found here. Then (if you're on Verizon, anyway), you could snag the OTA upgrade to 4.4.2, like I have... and root it again with the method I found.
ADDED LATER: Look in SuperSU, you should find an option for Permanent UnRoot.
Click to expand...
Click to collapse
Thanks for responding. Unfortunately my issue isn't the rooting of the OS (which I can undo, and have), it's the fact that the bootloader was unlocked and original recovery was replaced with that custom one I listed above. And yes, I did the 'factory reset', which reset everything to the original state of 4.1.2 ... but it didn't remove the custom recovery. Because of that, I can't ever upgrade via normal means (get the 0x13 error when I try).
Same deal with SuperSU, unrooting simply removes root access in the 4.1.2 OS, doesn't affect recovery. And, since there is no CMW / TWRP custom recovery option for VS890 I can't even attempt replacing the existing recovery. I'm stuck at this point unless someone figures out 1) where the stock recovery and firmware are located, and 2) a method to safely flash it to the phone. It sucks, I like this phone but it has some severe limitations. It also won't work with my Pebble watch, which is what prompted this whole endeavor in the first place (trying to upgrade to KitKat).
UsualNoise said:
Thanks for responding. Unfortunately my issue isn't the rooting of the OS (which I can undo, and have), it's the fact that the bootloader was unlocked and original recovery was replaced with that custom one I listed above. And yes, I did the 'factory reset', which reset everything to the original state of 4.1.2 ... but it didn't remove the custom recovery. Because of that, I can't ever upgrade via normal means (get the 0x13 error when I try).
Same deal with SuperSU, unrooting simply removes root access in the 4.1.2 OS, doesn't affect recovery. And, since there is no CMW / TWRP custom recovery option for VS890 I can't even attempt replacing the existing recovery. I'm stuck at this point unless someone figures out 1) where the stock recovery and firmware are located, and 2) a method to safely flash it to the phone. It sucks, I like this phone but it has some severe limitations. It also won't work with my Pebble watch, which is what prompted this whole endeavor in the first place (trying to upgrade to KitKat).
Click to expand...
Click to collapse
Have you tried simply finding and uninstalling the custom recovery? I know you said it was unfamiliar to you, but it has to be in there somewhere, under some name. And once it's removed, the phone would revert to its stock recovery. This is a great little phone, even if you can only get it to KitKat, don't give up.
Mr2nSmith said:
Have you tried simply finding and uninstalling the custom recovery? I know you said it was unfamiliar to you, but it has to be in there somewhere, under some name. And once it's removed, the phone would revert to its stock recovery. This is a great little phone, even if you can only get it to KitKat, don't give up.
Click to expand...
Click to collapse
The bad news: I would have no idea how to 'find' the custom recovery unfortunately.
The good news: I solved my problem! Although I couldn't update the OS via normal means (network) or via PC connection, I was able to manually flash KitKat (4.4.2) myself successfully. Here's what I did:
1) I downloaded the drivers for the phone from LG's site and installed them.
2) Connected the phone, it went into 'install' mode first where a drive appeared in my computer that contained the Verizon Upgrade Assistant.
3) Ran the upgrade assistant, it found the phone and downloaded the new firmware (.cab file). The upgrade assistant would not apply the update, unfortunately. I don't know if it was because of my bootloader issue or not, but I was at a dead end. Temporarily.
4) Tried following the procedure here but it didn't work with the current LG tools available. However it did point me in the right direction for
5) I found the LGFlashTool. I followed the instructions on that site. First went into download mode (powered off, removed battery, inserted battery, held vol up and down while plugging in the USB cable - *make sure it's a good cable!!*), then in the flash tool dialog itself I entered the .cab file name, selected [ CDMA, Diag, 33000 ], left what was auto-filled in version (but deleted the .cab extension) and hit the CSE Flash button. Next dialog I tried reading phone info, but it crashed (didn't fill me with confidence). Restarted, got back to that dialog, hit START. Next dialog, selected my country and language, hit OK. Then it popped up a new LG update window that actually did the update / flash.
Shockingly, it successfully worked. I was preparing myself for a bricked phone, but it worked ... AND fixed my bluetooth connection issue with my Pebble watch.
I have no idea if this procedure would work for custom ROMs or not (and I'm not going to press my luck and try), so I can't recommend it for non-stock stuff, but at least it's a way to flash a known working ROM for the LG Enact. Hopefully this helps someone else down the road. This was the first firmware flashing endeavor I've undertaken where I didn't already know someone else did it successfully first. Thus, my trepidation.
UsualNoise said:
The bad news: I would have no idea how to 'find' the custom recovery unfortunately.
The good news: I solved my problem! Although I couldn't update the OS via normal means (network) or via PC connection, I was able to manually flash KitKat (4.4.2) myself successfully. Here's what I did:
1) I downloaded the drivers for the phone from LG's site and installed them.
2) Connected the phone, it went into 'install' mode first where a drive appeared in my computer that contained the Verizon Upgrade Assistant.
3) Ran the upgrade assistant, it found the phone and downloaded the new firmware (.cab file). The upgrade assistant would not apply the update, unfortunately. I don't know if it was because of my bootloader issue or not, but I was at a dead end. Temporarily.
4) Tried following the procedure here but it didn't work with the current LG tools available. However it did point me in the right direction for
5) I found the LGFlashTool. I followed the instructions on that site. First went into download mode (powered off, removed battery, inserted battery, held vol up and down while plugging in the USB cable - *make sure it's a good cable!!*), then in the flash tool dialog itself I entered the .cab file name, selected [ CDMA, Diag, 33000 ], left what was auto-filled in version (but deleted the .cab extension) and hit the CSE Flash button. Next dialog I tried reading phone info, but it crashed (didn't fill me with confidence). Restarted, got back to that dialog, hit START. Next dialog, selected my country and language, hit OK. Then it popped up a new LG update window that actually did the update / flash.
Shockingly, it successfully worked. I was preparing myself for a bricked phone, but it worked ... AND fixed my bluetooth connection issue with my Pebble watch.
I have no idea if this procedure would work for custom ROMs or not (and I'm not going to press my luck and try), so I can't recommend it for non-stock stuff, but at least it's a way to flash a known working ROM for the LG Enact. Hopefully this helps someone else down the road. This was the first firmware flashing endeavor I've undertaken where I didn't already know someone else did it successfully first. Thus, my trepidation.
Click to expand...
Click to collapse
Good for you! See, you don't give up, and you get a happy ending.
It's a shame no roms for ours enact, its a cute qwerty android phone...please Can someone tell me how to enter recovery mode ? I bought this phone 2 day's ago but i haven't signal i want to do a wipe cache.. .sorry for my English.. .
Androide3 said:
It's a shame no roms for ours enact, its a cute qwerty android phone...please Can someone tell me how to enter recovery mode ? I bought this phone 2 day's ago but i haven't signal i want to do a wipe cache.. .sorry for my English.. .
Click to expand...
Click to collapse
Wish I could help you, but I never could do that on mine... had to use a sideload tool to do it from my PC. BUT -- I have two suggestions for you. First, download and install the KingRoot tool, to root the phone... it's called NewKingrootV4.50_C120_B220_xda_release_2015_07_22_105243.apk, and I think there is a link earlier in this thread which you can use to find and download it. You'll have to install it manually, then run it. (Don't bother with the "Purify" portion, you don't need that for now.) Your phone will now be rooted, by the only method that ever worked for me. Next, go to the Play Store, and download an app called "Quick Reboot", from Phong IT. This is a root-only app (hence the need to root, first) which includes a "Recovery" option. Try that out, and see what happens.
UsualNoise said:
The bad news: I would have no idea how to 'find' the custom recovery unfortunately.
The good news: I solved my problem! Although I couldn't update the OS via normal means (network) or via PC connection, I was able to manually flash KitKat (4.4.2) myself successfully. Here's what I did:
1) I downloaded the drivers for the phone from LG's site and installed them.
2) Connected the phone, it went into 'install' mode first where a drive appeared in my computer that contained the Verizon Upgrade Assistant.
3) Ran the upgrade assistant, it found the phone and downloaded the new firmware (.cab file). The upgrade assistant would not apply the update, unfortunately. I don't know if it was because of my bootloader issue or not, but I was at a dead end. Temporarily.
4) Tried following the procedure here but it didn't work with the current LG tools available. However it did point me in the right direction for
5) I found the LGFlashTool. I followed the instructions on that site. First went into download mode (powered off, removed battery, inserted battery, held vol up and down while plugging in the USB cable - *make sure it's a good cable!!*), then in the flash tool dialog itself I entered the .cab file name, selected [ CDMA, Diag, 33000 ], left what was auto-filled in version (but deleted the .cab extension) and hit the CSE Flash button. Next dialog I tried reading phone info, but it crashed (didn't fill me with confidence). Restarted, got back to that dialog, hit START. Next dialog, selected my country and language, hit OK. Then it popped up a new LG update window that actually did the update / flash.
Shockingly, it successfully worked. I was preparing myself for a bricked phone, but it worked ... AND fixed my bluetooth connection issue with my Pebble watch.
I have no idea if this procedure would work for custom ROMs or not (and I'm not going to press my luck and try), so I can't recommend it for non-stock stuff, but at least it's a way to flash a known working ROM for the LG Enact. Hopefully this helps someone else down the road. This was the first firmware flashing endeavor I've undertaken where I didn't already know someone else did it successfully first. Thus, my trepidation.
Click to expand...
Click to collapse
I did as you said, but I'm still on 4.1.2:crying:
I downloaded the December factory image and updated the same way I always do:
fastboot flash bootloader bootloader-walleye-mw8998-002.0073.02.img
fastboot reboot-bootloader
fastboot flash radio radio-walleye-g8998-00253-1809191716.img
fastboot reboot-bootloader
fastboot update image-walleye-pq1a.181205.002.zip
After the standard update flow, the device rebooted and gave me the usual verified boot Orange warning screen, then I pressed power twice to move past it and the device loaded into the bootloader with "ERROR: LoadImageAndAuth Failed: Load Error" at the bottom.
Now when I try to boot, I don't get the verified boot screen, just the bootloader with "ERROR: Slot Unbootable: Load Error"
The bootloader no longer enumerates as a USB device, so I can't try reflashing the bootloader or flashing it to slot B (I am on slot A) or anything else. It does still say "Device State: unlocked" but I can't seem to do anything else.
I have tried multiple USB A->C cables and a USB C->C cable and multiple host machines, but none of them will get the Pixel 2 to show up in Device Manager.
Have I had a hardware failure? Is this any kind of known issue and is there any way to recover it?
Thanks.
same here. found any fix?
I also had the same issue. I have not yet been able to find a solution, tried multiple PCs and even tried booting into Linux and still got nothing. I talked to google support and they are cross-shipping me a replacement device right now. However, if anyone found a fix that would be great so I don't lose the data on my old phone (yes I know I should've been doing backups).
Edit: Was on a Google Pixel 2, going from September to December security patch. Tried updating using the flash-all.bat without the -w flag set. Completely stock except for a Magisk install.
Never found a fix, but once I described the symptoms Google was very quick to offer a warranty replacement. I was upgrading from the August image to the December image.
Hi! Just for info - I got to same situation, but I was able to fix it but I don't know, how I did it I was trying to fix it all evening, but without success. So I let phone turned on till morning. Phone was totally discharged at morning, only notification LED was blinking red, when I was trying to turn phone on. So I chared it with original charger about half hour, then connect it to PC and it was detected, so reflash update and my phone is alive again...
Maybe this will help to someone
To successfully root on the Dec update you must use Magisk v18.0
[2018.12.8] Magisk v18.0 - Root & Universal Systemless Interface [Android 5.0+]
If you've used an older version, you'll get a boot loop into Recovery.
Side load / install the uninstaller from @topjohnwu's page linked above.
Then side load / install again with v18.0
Use the uninstaller first.
I'm in the same boat, tried flashing dec factory image over my october install (failed on step 4/5) now fastboot is broken and I have the same "ERROR:Slot unbootable: Load Error".
drmason said:
I'm in the same boat, tried flashing dec factory image over my october install (failed on step 4/5) now fastboot is broken and I have the same "ERROR:Slot unbootable: Load Error".
Click to expand...
Click to collapse
Does your desktop/ laptop recognize your Pixel 2 in bootloader mode?
If it does, then there is almost 99% chance you can get it to boot up with some flashing.
If it doesn't there's literally no way for us to recover it.
yuva_cool said:
Does your desktop/ laptop recognize your Pixel 2 in bootloader mode?
If it does, then there is almost 99% chance you can get it to boot up with some flashing.
If it doesn't there's literally no way for us to recover it.
Click to expand...
Click to collapse
yeah i guessed so, so i initiated a replacement with the google support, went without an issue. Flashing stuff for years, but this is the first that went down.
Also tried to deplete the battery, didn't work for me... won't turn on at all anymore.
I too have been flashing since the last 2 years. But this was the first time everything went to hell. I mean this is ridiculous. And as far as I have noticed many people are facing this issue after flashing the December patches. I'm guessing something on the Google's end messed up things.
I applied for a repair and they picked up my device. Will know in a few days if they are kind enough to repair it for free.
yuva_cool said:
I too have been flashing since the last 2 years. But this was the first time everything went to hell. I mean this is ridiculous. And as far as I have noticed many people are facing this issue after flashing the December patches. I'm guessing something on the Google's end messed up things.
I applied for a repair and they picked up my device. Will know in a few days if they are kind enough to repair it for free.
Click to expand...
Click to collapse
Kind? I hope it's not a thing of kindness. As far as I know a unlocked bootloader doesn't void warranty... and they provide 24 month of warranty so I expect a free replacement.
My replacement should be arriving soon and if they will charge me the full price again this will be my last pixel I guess. Also they didn't argue or asked more questions at all on the hotline after I told them it died after flashing december patch. I guess they know whats going on...
See here:
https://forum.xda-developers.com/pixel-2/help/bricked-pixel-2-locked-bootloader-t3876792
or here:
https://forum.xda-developers.com/pixel-2/help/slot-unbootable-load-error-device-locked-t3842095
my mobile is bricked too! This seems to be a horrible problem for a few of us
I got mine completely repaired for free. They couldn't recover my data but they did get it up amd running. They even changed my display as it was very muched burned in and also changed the smi tray. I didn't even report these 2 issues. Im actually very happy with their response. Got the device back in 8 days. Loving the Pixel team.
same thing happen to me just now, currently my pc cant detect the phone, seems like dead end.
koax88 said:
same thing happen to me just now, currently my pc cant detect the phone, seems like dead end.
Click to expand...
Click to collapse
Claim for an RMA. They are approving for bootloop issues. I guess December patches screwed up things for a lot of us.
yuva_cool said:
Claim for an RMA. They are approving for bootloop issues. I guess December patches screwed up things for a lot of us.
Click to expand...
Click to collapse
the thing is, i bought it from 3rd party seller, because google not selling pixel in my country. is there any other way for me to fix this phone? or let google fix it for me?
tried linux, and multiple setup of usb cables, still nothing.. and i havent sleep yet.. any advice? is there any other way to force pc to recognized pixel bootloader? im at lost now
I have the same problem after flashing the Dec factory image on my pixel 2.
And Here is a detail that is not mentioned above. The 'flash-all' script failed and show：
Sending 'vendor_a' (359956 KB) FAILED (Write to device failed in SendBUffer() (Unknown error))
and now your phone still can be recognized by windows or not?
koax88 said:
the thing is, i bought it from 3rd party seller, because google not selling pixel in my country. is there any other way for me to fix this phone? or let google fix it for me?
Click to expand...
Click to collapse
They do rma even you dont bought it in Google store.
In my case they asked me several things about the failure, rooting and all that stuft. After proofing my words with my imei and online logged in data the gave me a RMA.
Thanks to Google. Best support for me.