Related
I'm starting a new thread because it doesn't necessarily fall in to unlocking of the phone (as I've been asked).
I'm guessing any new purchases of this phone will have the recovery/download 3 button combo feature completely disabled.
The reason why I say this is that I've been to 5 different stores between yesterday and today (with the most recent one having a stock amount of 9 phones) and here are my findings:
Every single boxed up phone has the feature disabled. (All I did was have them install the battery (no sim or anything) and pass the phone to me).
However, every one of those 5 stores that I went to, I did it flawlessly on their demo phones.
So my guess is, as the demo phones would have been the first batch Bell provided (and some being on display before any actual product released to the public), all subsequent batches of these phones will have this feature disabled.
I went to 2 different best buys that have ample stock of the phones because it is onsale this week, and none of them worked... nor did they work at the future shop I attended or the 2 bell stores (including the one I purchased and returned initially).
But every single demo did.
So if anyone got their hands on the very first batch of phones and it works then you're a lucky one. For the rest of us, I think we are S.O.L.
There's got to be a way to do it... Anyone know a Bell Representative or better yet a person inside samsung that will leak that info to you?
Heck I don't even want to unlock the phone. I'll stay on Bell's network, I just want to be able to load new versions of Android without any risk of bricking my phone.
Thank you! It was annoying reading all those posts abt this in that thread.
And I'm not too sure that the new phones don't have it. There have been a few people on the thread that have said that they got the phone at launch, and it didn't have the feature, but when they went to return it and get a new one (from the new shipment) it was fine...
So really I dont think its very easy to tell if its gonna work or not...
I think I'll wait til september to buy the phone.
I don't care too much about custom roms and the like, the stock one is fine, but Bell has a history (See the i7500L) of not updating their firmwares in a timely fashion. The i7500L is still on 1.5. Terrible if you ask me, considering the "open-source" feel of android.
So there are rumours, I don't know if its true or not, that bell is going to have an official 2.2 update in september. Maybe then I'll buy it and by then all phones will have the 3 button combo on them.
I just went to a local future shop here, and the phone representative contacted their Bell Rep, who was at another store, he couldn't do it on the phones they had there, but promised to call Samsung on Monday to find out if their is an alternate way.
Maybe you have to hit a reset button along with it. I remember doing something similar on my old HTC diamond phone, maybe this is the same thing (sort of).
Too bad, I loved this phone all the 4 days I had it (up until reading about the 3 button combo). I sort of miss it.
I just put a call in to Samsung to find out why some work and some don't, they said because the phone was so new that I had to call a number specifically set up for support on the Galaxy S but they are only open Monday to friday..
So hopefully with all this calling around I'm doing something will be figured out.
I got my Vibrant on launch day, 3 button combo didn't work. Swapped it out for a new one, from a new shipment last Thursday (august 12th) 3 button combo works.
arr0ww,
Can you confirm what i've been reading on wiki then?
It states:
"Note: There are many Bell I9000M floating around with this feature disabled, without the Download Mode enable you wont be able to restore from a failed firmware flash. We highly recommend you to take it back and exchange it for a model that can work properly with the 3 button combination. The first batch from around Aug 5 or Serial # ending with 6000000 have the 3 buttons combo disabled, the new batch after Aug 11 with Serial # ending with 6500000 have the working 3 buttons.
example of full Serial # 89302610202006500000"
Do your last 7 digits end with 65 and not 60?
Also, where did you get yours exactly? I think if its close to me, I'll just pop by that store and get it (assuming your somewhere in the GTA).
I got mine first thing Launch morning. My serial is 59XXXXX. 3 button combo IS working.
it shouldn't be hard to fix the issue. from what i've read, and people have said, the 3-button combo is written into the SPL part (256kb) part of the Nand. all we would theoretically have to do is flash our SPL with some else's 3-button enabled SPL. now two of my friends bought their phones same day as me, and have theirs enabled, and both are rooted, so it's not hard to get our hands on a copy.
i have posted another thread in the software technical section about this and haven't gotten any replies (maybe it's the wrong section). the g1 users flash their spl, but they don't talk about how to make an image of the current spl. so i'm stuck here. i know it can be done, just don't know how yet.
apparently nandroid backup doesn't backup the spl, so that's useless to us. from the SPL backup kit for the g1 users, i read the batch file, and it reads specific hex addresses in the nand and writes them to a file, but i would assume these addresses are different for our nand. so once again, useless.
For all those that have their 3 button disabled... can you confirm if your serial ends with 60XXXXX? Maybe its limited to just that batch of s/n's.
As for wang1chung.. hopefully its a simple fix.. but i'll refuse to buy one again unless I get one that is confirmed working or easily fixable to get it working without a cable.
Thanks
Electroz said:
I got mine first thing Launch morning. My serial is 59XXXXX. 3 button combo IS working.
Click to expand...
Click to collapse
it is possible the bug was only in the batch with numbers ending in 60xxxxxxxx
since the ones on 59xxxxxxxx works, and 65xxxxxxxx works
that seems to be the logical sense
this would be nice
problem is, no one has been able to get a way to extract, and flash back the good SPL to the bad phones
wang1chung said:
it shouldn't be hard to fix the issue. from what i've read, and people have said, the 3-button combo is written into the SPL part (256kb) part of the Nand. all we would theoretically have to do is flash our SPL with some else's 3-button enabled SPL. now two of my friends bought their phones same day as me, and have theirs enabled, and both are rooted, so it's not hard to get our hands on a copy.
i have posted another thread in the software technical section about this and haven't gotten any replies (maybe it's the wrong section). the g1 users flash their spl, but they don't talk about how to make an image of the current spl. so i'm stuck here. i know it can be done, just don't know how yet.
apparently nandroid backup doesn't backup the spl, so that's useless to us. from the SPL backup kit for the g1 users, i read the batch file, and it reads specific hex addresses in the nand and writes them to a file, but i would assume these addresses are different for our nand. so once again, useless.
Click to expand...
Click to collapse
Hey guys, are you still able to start in recovery mode with a cable and ADB. I would like to know cause my G-sensor is dead and I went to Best Buy to exchange it and the phones were all lacking this mode.
I didn't swap ysterday because of this but I have to do something before aug. 20. After that I will have to see with bell what they want to do and it will surely go for a repair. I would prefer to have a new one working right away but the lack of recovery mode is discouraging me.
my s/n is 52xxxxx and 3button is disabled
sp991, recovery mode is still accessible via adb to those with the 3button disabled.
allgamer, i only suggested that as no one else had suggested anything else? i assumed it would be possible since the g1 users can read their spl via the command " pmemdump -a 0x8c000000 0x40000 " and save it to a .nb file to update later. maybe this would be better accomplished in the hands of talented coders/developers.
Mine is 64xxxxx and it is disabled.
adb works.
I exchanged my first i9000m coz the download mode wasn't working.
The second one I got two days ago goes into download/recovery mode without problem!! This one has IMEI ending with 65xxxxxx and manufactured in Aug.
I also tested new one at Bell store today which had IMEI # 65xxxx as well, but it didnt go into download mode. The guy at the store said it was the newest batch as they received it yesterday, and now i'm totally confused....coz I thought all newer batchs are download mode enalbed..
sp991 said:
Hey guys, are you still able to start in recovery mode with a cable and ADB. I would like to know cause my G-sensor is dead and I went to Best Buy to exchange it and the phones were all lacking this mode.
I didn't swap ysterday because of this but I have to do something before aug. 20. After that I will have to see with bell what they want to do and it will surely go for a repair. I would prefer to have a new one working right away but the lack of recovery mode is discouraging me.
Click to expand...
Click to collapse
do you have any other best buy store that you can go to?
try testing with the Download mode, it's easier than testing with the Repair mode
the Download mode kicks in right away, after you put in the battery, and do the 3 button test
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S/Vibrant_GT-I9000M
check the wiki for some visuals
you can do it even with the plastic back and screen protector on top
trueimage said:
Mine is 64xxxxx and it is disabled.
adb works.
Click to expand...
Click to collapse
ADB will always work, but it's useless if it gets bricked
good to know 64xxxxxxxx is not good
so i guess batches between 60xxxxxxxx to 64xxxxxxx are bad?
since the 59xxxxxxxx were good, and 65xxxxxxxxxx are also good
karakake said:
I exchanged my first i9000m coz the download mode wasn't working.
The second one I got two days ago goes into download/recovery mode without problem!! This one has IMEI ending with 65xxxxxx and manufactured in Aug.
I also tested new one at Bell store today which had IMEI # 65xxxx as well, but it didnt go into download mode. The guy at the store said it was the newest batch as they received it yesterday, and now i'm totally confused....coz I thought all newer batchs are download mode enalbed..
Click to expand...
Click to collapse
that's exactly what we are trying to find out, to see if there is any pattern
but if the one you tested with 65xxxxxxxxxxx didn't work, then i guess we can't really identify it via the serials numbers, and only can be tested manually.
Try downloading the new firmware for bell the JH2 that you can download via Kies this might fix the 3 button combo for people have issues. as the recovery screen is a bit different. give your a warning now that you have entered the system menu. the old recovery screen did not have this.
Someone that can't get into recovery should try this update..
no dice, just updated
EDIT: what's worse is i thought it would've at least helped with the gps lag, and now i can't find my location at all. under the gps performance testing option, i can't pickup any satellites whatsoever.
i'm pissed now, as i needed it to go on a roadtrip tomorrow
I have a Galaxy S as shipped by Bell Canada. It doesn't have the 3 button download mode so I'm staying away from 3rd party roms for now.
It is unlocked and rooted. All has been well until today. I had it off for a while to use the SIM in another phone. When I turned it back on it asked for the SIM unlock code. I Dismissed that and checked the phone, all seemed well other than no SIM activation. I turned it off and removed the SIM and now it won't boot. I get the usual logo, the song, and for a long time the S logo. If I wait long enough it then appears to be off. If I press the back or menu key they will light up but that's it. I can't do anything else other than pull the battery.
I tried the hard reset with holding volume down and tap the power button. That only turns it back on with the same problem. The actual SIM is fine and working in another phone.
Is there anything I can do? If I could hard reset it I'd take it back to the store but I hesitate for now while it still contains my data.
this is a problem i have just posted about a couple of mins ago
but i can get it recovery mode and fatory reset with the vol up, home and power
then it will boot but obviously i have to then reset everything from scratch which is really annoying so anyone got any idea re this
lucky for you that you can get into recovery. Right now I'd be happy with a hard reset, it doesn't take long to rebuild the setup. I'd like to know who decided to remove the recovery mode, that's evil and keeps me from simply resetting the device.
its all the apps re downloading and installing them and resetting up accounts and swype and all that lot need a fix asap
do you know what version of andoid you are running
yes but at least you can get a working phone again, I can't without being able to get into any boot menus. Honestly it only takes 30 minutes to setup again from scratch. I'm on 2.1 and what I find at least on my HTC when it had 2.1 is that I setup the google account, let it sync contacts etc, then from Market Downloads I'll see listed all my apps that were previously installed. As long as I don't leave that screen I can install each app one after the other. Or a proper backup....
Any other magic key combos to reset this thing???
did you try hooking up to kies?
Yes but that does nothing since it never fully boots.
3rdcoast said:
I have a Galaxy S as shipped by Bell Canada. It doesn't have the 3 button download mode so I'm staying away from 3rd party roms for now.
It is unlocked and rooted. All has been well until today. I had it off for a while to use the SIM in another phone. When I turned it back on it asked for the SIM unlock code. I Dismissed that and checked the phone, all seemed well other than no SIM activation. I turned it off and removed the SIM and now it won't boot. I get the usual logo, the song, and for a long time the S logo. If I wait long enough it then appears to be off. If I press the back or menu key they will light up but that's it. I can't do anything else other than pull the battery.
I tried the hard reset with holding volume down and tap the power button. That only turns it back on with the same problem. The actual SIM is fine and working in another phone.
Is there anything I can do? If I could hard reset it I'd take it back to the store but I hesitate for now while it still contains my data.
Click to expand...
Click to collapse
Same thing happened to my phone, but a factory reset did nothing. The internal SD card gave out. Phone is now sent away for 3 - 6 weeks awaiting repair.
my phone did this to me today too, I was just about to post about this when I saw this thread.
So its an SD Card problem? theres no hope of getting it fixed without sending it in?
Yes I think it is the internal card meaning there isn't anything good enough to reset to. I walked the phone over to the store and I'll have to wait for new stock next week. Actually I'm lucky they will exchange it since I bought it outright which apparently is "against policy" even though they list a no contract full price. We'll see how it goes next week but overall I despise the telco industry in this country.
3rdcoast said:
Yes I think it is the internal card meaning there isn't anything good enough to reset to. I walked the phone over to the store and I'll have to wait for new stock next week. Actually I'm lucky they will exchange it since I bought it outright which apparently is "against policy" even though they list a no contract full price. We'll see how it goes next week but overall I despise the telco industry in this country.
Click to expand...
Click to collapse
i went to best buy today to try and exchange it, and apparently they only have a 14 day exchange policy with phones despite it saying 30 day on the receipt, anyhow i phoned samsung and they said i have to go through bell, even though im using the phone on telus, so that should be interesting.
So all the people that are having this problem have the Bell model?
Today i got mine off eBay, as soon a i turned it on, i get exactly the same thing.
It wont load into Android, i see that galaxy S logo and then black screen.
If i go into recovery i see "cant mount SD Card".
The more is search this forum the more i see that all the people with this problem are owners of the Bell i9000M model.
I seriously think they have some defect with the manufacturing line of the phone.
Have you guys installed any firmware on your phone before this happened?
mine is like that out of the box.
Mine is the same Bell model. There seems to be some issues with them which makes the lack of download mode even more dangerous. Right now it doesn't feel like the warranty is going to cover us for problems not our fault. I hope they replace it next week but if it still lacks download mode I'll remain nervous.
Seems like everyone is with the Bell model but my questions is:
Have you guys installed another firmware than the factory one which caused this to happen?
Are you running Stock?
We need to try and narrow this down as i am seeing too many posts about this issue, and they are with the Bell model.
clubtech said:
Seems like everyone is with the Bell model but my questions is:
Have you guys installed another firmware than the factory one which caused this to happen?
Are you running Stock?
We need to try and narrow this down as i am seeing too many posts about this issue, and they are with the Bell model.
Click to expand...
Click to collapse
i put new firmware on it last week, can't remember what it was but it was upgraded through kies so it's one samsung pushed to me, not a froyo unstable one.
bigc_13 said:
i put new firmware on it last week, can't remember what it was but it was upgraded through kies so it's one samsung pushed to me, not a froyo unstable one.
Click to expand...
Click to collapse
Thanks. if it was pushed to you via Kies i assume you were running stock JH2.
So it just stopped booting out of the blue?
To the OP: have you install any firmware on your device before this happened?
clubtech said:
Seems like everyone is with the Bell model but my questions is:
Have you guys installed another firmware than the factory one which caused this to happen?
Are you running Stock?
We need to try and narrow this down as i am seeing too many posts about this issue, and they are with the Bell model.
Click to expand...
Click to collapse
I haven't flashed any 3rd party roms. I did do the official update via Keis which even at the store today they reminded me that I should do the update.. That update seemed to go well and has been working for over a week until I turned it off for an hour. It still isn't clear if the disabled 3 button mode is hardware or software related but we all seem to have that in common too. So before they dismiss the whole thing and we get hosed over technicalities such as unlocking it should be clear that there are clear defects in these phones as far as I can tell.
I want to be comfortable that I'm not left out of hundred of dollars just because I choose to buy it outright and not be tied to contracts. Samsung has to play nicely because it is their phone. Bell has to play nicely because they are bringing them in and distributing to retail. What carrier I use should be irrelevant because the problems are not related to usage.
FYI, the clerks went off for conference to decide if I somehow got the phone against policy. Either they trust my story or I got mine moments before they got the memo about not selling outright.
clubtech said:
Thanks. if it was pushed to you via Kies i assume you were running stock JH2.
So it just stopped booting out of the blue?
To the OP: have you install any firmware on your device before this happened?
Click to expand...
Click to collapse
Same here, stock JH2 from Kies. Not rooted. Boots to Galaxy S logo, then black screen. Mine is sent in for repair... Almost two weeks now.
Seeing more and more of this being posted. There is obviously some issues with this phone.
clubtech said:
Thanks. if it was pushed to you via Kies i assume you were running stock JH2.
So it just stopped booting out of the blue?
To the OP: have you install any firmware on your device before this happened?
Click to expand...
Click to collapse
Our posts crossed..
Yes I believe mine had the JH2, the official keis offered firmware. I was looking forward to the biggie update at the end of the month so wasn't about to risk bricking before then. Irony stepped in anyway.
I'm a bit nervous until I get a new one. At that point if the 3 button mode still doesn't work I'll remain nervous that I'll get another potential brick.
edit-> yes, I simply shut it down for an hour or two to use the SIM in another phone to test that phone. At next boot it died. I knew something was wrong when the logo stayed up for much longer.
I have the 3 buttons enabled so it is not related to the 3buttons being disabled, however when i boot into recovery it clearly displays an error that it can not find the internal SD.
There is definitely something wrong with the Bell Galaxy S corrupting itself.
I bought mine from an eBay seller, he is saying the phone booted fine when he shipped it but when i opened the box today i only got this black screen after logo.
Gladly the seller will take it back.
Maybe this is why there are shortages everywhere in Canada. I hope the caught this up and are fixing it with the new batch.
So I was in Verizon today because of software issues. I still have the same phone but all they could say is pull the battery every night. So the lady tells me, my software is behind. I'm like "what, how?" She says "Its a known issue and an update has been pushed for the phone. Depending on when you got the phone, the new software will be pushed through." Apparently, thousands of people have gotten this "Update" I will call this week and see what the deal is.
Update like version 1.02?
not to sure..it was some lady which means she probably has no clue what the hell she's talking about so just sit and wait for a text from verizon wireless or the "Uploading Logs" screen. She said it will either be pushed OTA (over the air) or you will get a notice saying to bring your phone in which I think wont happen. 0lus the software has been released since April 1st so I'm guessing this is a load of bull.
Well, I had my phone turned off all day while i was out. I got back home, turned it on, and got a text from 475-6. It says BREW://----- idk what it said. Im guessing the update? not to sure. Phone info says..
Software Version: 1.0.1 (4704.0)
Radio firmware: v0.4.727
Model 119
Kinuser1 said:
Well, I had my phone turned off all day while i was out. I got back home, turned it on, and got a text from 475-6. It says BREW://----- idk what it said. Im guessing the update? not to sure. Phone info says..
Software Version: 1.0.1 (4704.0)
Radio firmware: v0.4.727
Model 119
Click to expand...
Click to collapse
Hmm I did abit of research about BREW. It's actually,Binary Runtime Environment for Wireless.
Brew (Brew MP) is an application development platform created by Qualcomm, originally for CDMA mobile phones.
As a software platform that can download and run small programs for playing games, sending messages, and sharing photos, the main advantage of Brew MP is that the application developers can easily port their applications among all Brew MP devices. Brew MP acts between the application and the wireless device on-chip operating system in order to allow programmers to develop applications without needing to code for system interface or understand wireless applications.
Click to expand...
Click to collapse
Sauce: http://en.wikipedia.org/wiki/Binary_Runtime_Environment_for_Wireless
Hmm... Hack via brew?
My phone software is the same as yours (1.0.1, etc...). I haven't received a text like that though. Did you follow the link in the text? I would be nervous clicking it unless I knew it was really from Verizon.
It's not a link at all. It usually says
"BREW:06:07---YADA YADA YADA."
(Just making up numbers but you get the point.)
Actually you cannot "hack" using brew. The brew message is sent over a wireless network. Unless you want to hack the network, go right on ahead
I think these messages are for the "Developmental" process of the phone since it originally had the "KIN" software. Not this "M" Bullsh*t
I'll do some research. I have time freeing up on me now since I'm getting school work done quicker. I will try to develop some sort of application to "Pull out" the information we need. If this is to techy for you, just put it this way. "I'll try to hack the phone" I've had a lot of success in hacking phone WITHOUT turning to the source of the internet/Bitpim. Technology is one of the things I know most about. I'm 15 and all I do is look for ways to hack. So far successful. As for this KIN 2m, not so much. So I turned to this forum so I could get some tips for stuff that i might not have done yet. Well, for today, I have nothing.
Kinuser1 said:
I will try to develop some sort of application to "Pull out" the information we need. If this is to techy for you, just put it this way. "I'll try to hack the phone"
Click to expand...
Click to collapse
As a matter of fact, i found it opposite to techy, better said "abstract". Can you explain in detail the Pull out attempt process?
I just wanna know, can handle tech terms.
Okay..well heres how it goes. We have to somehow get the kin into a "hidden" software writing screen(you should know what i mean) EVERY phone has one of these...AKA...enV touch..you hold clear..power..vol up and down and that brings the phone to a downloading screen and waits to be plugged into the drivers on the computer. But the kin is different...there arent any drivers as of right now.
Kin has that mode, indeed. It was labeled as "Download mode" both in QPST, Bitpim and several other tools.
Unfortunately, being switched ON by software (i guess that's the only way, or the only one available atm) made my phone reboot after a little while (maybe 1-2 mins), so it could be protected by the phone manufacturer. Also, no special effect was shown on screen, like you can see on other phones examples (with SERIAL and USB labels with a colours background).
On the other hand, QPST and other tools could get a backup of the NVitems on memory, and not the memory itself (they fail to). Messing with this made my last attempt a brick, so... not happy about them.
Hmm... MY Kin Came with 1.01
1.01 is the latest version.
I was on the latest CM13 nightly (was waiting a bit to go to 14.1) So I went to bed last night and my phone did a reboot as I was setting my alarm. Didn't think too much of it, crap happens. I waited for it to come back fully into the OS, which it did, checked my alarm. Noticed something strange I got the CM Updater notification in the statusbar ("There are new updates available" - CM14.1-12-02 or something), which I thought was weird that's the first time it's said that, and I've checked the CM Updater before and since the 14.1 switch there's been nothing there. As it should, I imagine, not try to update major versions like that. Anyways I dismissed it and went to bed (this entire thing is PROBABLY entirely unrelated, but I found it's timing interesting at least).
Woke up a few hours later to my phone getting really hot, and stuck in an infinite boot loop. It never gets passed the first Google screen. If I let it go it'll sit there for several minutes and maybe reboot. I was able to get into the bootloader, choosing Boot Recovery though sends me back to the Google bootup screen where it never progresses, doesnt have the blue text in the top that says booting into recovery..
Was able to get into the phone with fastboot so I tried flashing the latest recovery I had installed TWRP-3.0.2-2-angler. Still wouldn't boot into it, sometimes it would get to the TWRP recovery loading page, and then sit there for a couple minutes, then reboot.Tried flashing it a few times with fastboot with no success.
Erased userdata with fastboot, then did a full factory reflash of several images, MDB081 - MTC20l (factory images I know I've used in the past to recover, had them saved). Rebooted and I still can't get into the OS (stuck at first Google logo). Interesting the stock recovery though loads.
Flash an older TWRP recovery I had saved twrp-2.8.7.2-angler . Was able to get into recovery finally - kind of. Sometimes it still locks up and wont let me swipe to enter TWRP. The first time it let me in it asked me for my decryption password - I didn't have a password - had a swipe and fingerprint setup only. Got in again and first thing I tried doing honestly is erasing (formating) all my data, thinking if I'm going to have to warranty this phone or sell it broken, I want to make sure my data is wiped. Also I figure after that I can try to reinstall CM etc like I would a completely fresh build. It complained about not being able to mount the partition and locked up in TWRP then eventually auto rebooted. Got in again and tried to do a basic wipe, it said it cant find /sdcard then said it wiped, and then froze, auto rebooted again after a few seconds.
To note : All fastboot commands seem to execute with "OKAY" status, no errors reported anywhere, it always finds the device too.
I can't seem to get anywhere with this phone. Everything I try to do in recovery is met with freezes and reboots. It seems like maybe the internal emmc has taken a dump.
Problem is I'm literally 3 days out of the 1 year warranty from when I received my phone, and having tried to work with Huawei support previously, I'm 100% certain they won't help. I came across a few threads on here similar to mine recently without any real resolution other then RMA'ing it. I figured I'd post here for a last desperate attempt if anyone has any other suggestions, because I don't know what I'll do. The Pixel XL is ungodly expensive, and conveniently out of stock. And I don't think I could talk myself into buying another Huawei anytime soon after this.
Any suggestions?
the.root said:
I was on the latest CM13 nightly (was waiting a bit to go to 14.1) So I went to bed last night and my phone did a reboot as I was setting my alarm. Didn't think too much of it, crap happens. I waited for it to come back fully into the OS, which it did, checked my alarm. Noticed something strange I got the CM Updater notification in the statusbar ("There are new updates available" - CM14.1-12-02 or something), which I thought was weird that's the first time it's said that, and I've checked the CM Updater before and since the 14.1 switch there's been nothing there. As it should, I imagine, not try to update major versions like that. Anyways I dismissed it and went to bed (this entire thing is PROBABLY entirely unrelated, but I found it's timing interesting at least).
Woke up a few hours later to my phone getting really hot, and stuck in an infinite boot loop. It never gets passed the first Google screen. If I let it go it'll sit there for several minutes and maybe reboot. I was able to get into the bootloader, choosing Boot Recovery though sends me back to the Google bootup screen where it never progresses, doesnt have the blue text in the top that says booting into recovery..
Was able to get into the phone with fastboot so I tried flashing the latest recovery I had installed TWRP-3.0.2-2-angler. Still wouldn't boot into it, sometimes it would get to the TWRP recovery loading page, and then sit there for a couple minutes, then reboot.Tried flashing it a few times with fastboot with no success.
Erased userdata with fastboot, then did a full factory reflash of several images, MDB081 - MTC20l (factory images I know I've used in the past to recover, had them saved). Rebooted and I still can't get into the OS (stuck at first Google logo). Interesting the stock recovery though loads.
Flash an older TWRP recovery I had saved twrp-2.8.7.2-angler . Was able to get into recovery finally - kind of. Sometimes it still locks up and wont let me swipe to enter TWRP. The first time it let me in it asked me for my decryption password - I didn't have a password - had a swipe and fingerprint setup only. Got in again and first thing I tried doing honestly is erasing (formating) all my data, thinking if I'm going to have to warranty this phone or sell it broken, I want to make sure my data is wiped. Also I figure after that I can try to reinstall CM etc like I would a completely fresh build. It complained about not being able to mount the partition and locked up in TWRP then eventually auto rebooted. Got in again and tried to do a basic wipe, it said it cant find /sdcard then said it wiped, and then froze, auto rebooted again after a few seconds.
To note : All fastboot commands seem to execute with "OKAY" status, no errors reported anywhere, it always finds the device too.
I can't seem to get anywhere with this phone. Everything I try to do in recovery is met with freezes and reboots. It seems like maybe the internal emmc has taken a dump.
Problem is I'm literally 3 days out of the 1 year warranty from when I received my phone, and having tried to work with Huawei support previously, I'm 100% certain they won't help. I came across a few threads on here similar to mine recently without any real resolution other then RMA'ing it. I figured I'd post here for a last desperate attempt if anyone has any other suggestions, because I don't know what I'll do. The Pixel XL is ungodly expensive, and conveniently out of stock. And I don't think I could talk myself into buying another Huawei anytime soon after this.
Any suggestions?
Click to expand...
Click to collapse
It's an ongoing thing with these 6P's and 5X's. Some have been able to fully recover and others like myself were not. Here is a guide that might be able to help you if you haven't come across it yet. Good luck..
http://forum.xda-developers.com/android/help/guide-revive-angler-bootloop-t3454938/page6
Check Warranty Status:
http://consumer.huawei.com/us/support/warranty-query/index.htm
BIGSAMDA1ST said:
It's an ongoing thing with these 6P's and 5X's. Some have been able to fully recover and others like myself were not. Here is a guide that might be able to help you if you haven't come across it yet. Good luck..
http://forum.xda-developers.com/android/help/guide-revive-angler-bootloop-t3454938/page6
Check Warranty Status:
http://consumer.huawei.com/us/support/warranty-query/index.htm
Click to expand...
Click to collapse
Thanks. I came across that. I tried flashing MMB29P as well as several other factory images without success. My problem now it seems no matter what I flash I cannot get back into recovery anymore. Even if it's stock or if it's TWRP (any version - including 3.0.2.0 as they suggest), so I don't really get passed step 4-5 in that guide. I guess she only had so many reads left in her, sigh.
WEIRD @ warranty link. It says from my S/N that it's valid until 2017-02-17. I don't know how, I purchased it 2015-10-22, it shipped 2015-11-24, and I got it 2015-11-30. Unsure how/why that would've gotten extended until February. I'm concerned they'll get it back then deny it once they figure that out, or figure out it's been unlocked/flashed. When I first got the phone i had issues with it charging, I narrowed it down to the USB C->C cable being faulty, and contacted Huawei. They absolutely refused to replace just the cable. Said I had to ship the whole phone back and it'd take AT LEAST 3-4 weeks to get it back. I argued with several people on the phone there (their support 100% refuses to give you their name or transfer to their supervisors btw), and finally asked google support to pull some strings and get in contact with someone there to replace a simple freaking cable - no one cared at all - spent several hours trying and got nowhere. I'm /done with Huawei. I think my best bet is to probably find out how well that American Express extended warranty claim works, I've never actually had to use it before. IDK what I'll do after that. Sad this is a common problem with these phones exactly one year out, so even if I wanted to buy a used one on eBay I'd risk the same thing shortly thereafter.
I'll keep the phone powered off for a while and try some more flashing later see if I can get back into recovery to try the rest of his steps in that article. It's not looking promising anymore.
Well being that it's a known issue, like I said, I myself ran into this fiasco, had phone rooted and running custom rom. I myself couldn't get into recovery but was able to flash all factory images and relock bootloader manually. I then called Huawei and played dumb telling them that I had updated my phone to the latest firmware via OTA and then it went into bootloop. They never asked if it was unlocked and I never volunteered to tell them either. I had bought my 6P through Best Buy and still had receipt Incase they'd asked for it which they didn't. All they did was ask for IMEI # along with Ser # and verified that it was still under warranty, then they emailed me a return label. I shipped phone to them and in a matter of like a week or so I had a brand new device in hand. Build date on it was August, 16, 2016. So far running good but let's see for how long.
BIGSAMDA1ST said:
Well being that it's a known issue, like I said, I myself ran into this fiasco, had phone rooted and running custom rom. I myself couldn't get into recovery but was able to flash all factory images and relock bootloader manually. I then called Huawei and played dumb telling them that I had updated my phone to the latest firmware via OTA and then it went into bootloop. They never asked if it was unlocked and I never volunteered to tell them either. I had bought my 6P through Best Buy and still had receipt Incase they'd asked for it which they didn't. All they did was ask for IMEI # along with Ser # and verified that it was still under warranty, then they emailed me a return label. I shipped phone to them and in a matter of like a week or so I had a brand new device in hand. Build date on it was August, 16, 2016. So far running good but let's see for how long.
Click to expand...
Click to collapse
Hmm interesting. Maybe their US support has improved since last year. So it was brand new not refurbished? Did you get the full retail box set? I bought mine directly through Huawei, so I would like to think that they would have accurate warranty data, but perhaps not. I will consider RMA'ing it to them if it's really a new one. It's either that or a 550$ refund from my credit card company. I haven't tried fastboot lock yet, will do that when I give up on all else lol (and need to return it), but hopefully that will work if the rest of the emmc is hosed.
Yeah, mine came in a new box, sealed like day one. I was surprised thought I'd be getting a refurbished device but I can honestly say it was a brand new one. And I don't blame you on trying to get the device to a working state. I tried everything and it's mother before giving up and finally relocking bootloader and sending it in.
BIGSAMDA1ST said:
Yeah, mine came in a new box, sealed like day one. I was surprised thought I'd be getting a refurbished device but I can honestly say it was a brand new one. And I don't blame you on trying to get the device to a working state. I tried everything and it's mother before giving up and finally relocking bootloader and sending it in.
Click to expand...
Click to collapse
Just called them. They won't accept it back without a proof of purchase. I have to send in the proof of purchase before they'll approve the RMA and then I get the shipping label/information. And "they can't look it up by S/N, doesn't matter if the website says it's in warranty". LOL. Sounds about right from what I remember of their support. They say their website is inaccurate, and cant ever verify/lookup that I bought the product directly from them. Maybe I'll try back tomorrow to see if someone else will help but it's unlikely from the sounds of it. She did say this is very common problem however, knew all about it.
Damn, That truly sucks..I would definitely give them a call again and see if I get a different rep. I was lucky with the one I got, he basically knew it was an ongoing thing and really didn't give me a hard time. He didn't even ask for a receipt, about the only thing he asked was that if the bootloader was locked or unlocked and when I told him it was locked, he then proceeded with the RMA procedure.
BIGSAMDA1ST said:
Damn, That truly sucks..I would definitely give them a call again and see if I get a different rep. I was lucky with the one I got, he basically knew it was an ongoing thing and really didn't give me a hard time. He didn't even ask for a receipt, about the only thing he asked was that if the bootloader was locked or unlocked and when I told him it was locked, he then proceeded with the RMA procedure.
Click to expand...
Click to collapse
Yeah I played dumb and all, didn't help. She didn't ask me any real questions she was convinced of the problem just from my description. She also said it's 12 months from the date I purchased it and not when I received it in the mail (so since they took 5-6 weeks to get it to me - preorder madness - I don't get that time back in the warranty) lol. Not like it matters now, just to further comment on how crappy their support/warranty is (in my experience).
I'll follow up if I have any more luck unbricking the device or warrantying it for that matter.
Good luck on either with the warranty or bringing it back to life.
I also have problems such as your support Huawei says four weeks of waiting
Got a recovery image to boot finally (after like 10x attempts at flashing one). Tried doing the nandroid backup as that guide suggests, says it cannot find/mount /sdcard and freezes/reboots. Tried going into wipe -> advanced and repairing internal storage and data and it was an invalid partition or something. Tried repairing system and it locked up again. Tried formatting them with fastboot and didn't work. Tried installing the latest 7.0 factory image for the hell of it, nadda. Relocked the bootloader successfully. Giving up. Filed an claim online with my credit card company (most do a +1 year extended warranty), we'll see how that goes, if I get lucky they'll approve the claim and let me keep the phone. May pick up a used 5x or something.
the.root said:
Got a recovery image to boot finally (after like 10x attempts at flashing one). Tried doing the nandroid backup as that guide suggests, says it cannot find/mount /sdcard and freezes/reboots. Tried going into wipe -> advanced and repairing internal storage and data and it was an invalid partition or something. Tried repairing system and it locked up again. Tried formatting them with fastboot and didn't work. Tried installing the latest 7.0 factory image for the hell of it, nadda. Relocked the bootloader successfully. Giving up. Filed an claim online with my credit card company (most do a +1 year extended warranty), we'll see how that goes, if I get lucky they'll approve the claim and let me keep the phone. May pick up a used 5x or something.
Click to expand...
Click to collapse
I would stay away from the 5X as well..lol They are going through the same thing the 6P is going through. It's all over Reddit and XDA as well. I'm currently using the 6P but I'm waiting on the One Plus 3T to arrive. I have a few other devices to play with but I'm still using the 6P waiting for the 7.1.1 update to drop in a few days to see how that goes.
BIGSAMDA1ST said:
I would stay away from the 5X as well..lol They are going through the same thing the 6P is going through. It's all over Reddit and XDA as well. I'm currently using the 6P but I'm waiting on the One Plus 3T to arrive. I have a few other devices to play with but I'm still using the 6P waiting for the 7.1.1 update to drop in a few days to see how that goes.
Click to expand...
Click to collapse
Oh what the **** . That sucks. My wife owns a 6P and my son has a 5x. So our house is a ticking time bomb of failure. Maybe I'll buy a Note 7 and finish the job. I have my old Nexus One and Tmobile G1, both still power on last time I checked. I've gotten rid of all other past cell phones we've had unfortunately. Used to have so much trust in the Nexus lineup
the.root said:
Oh what the **** . That sucks. My wife owns a 6P and my son has a 5x. So our house is a ticking time bomb of failure. Maybe I'll buy a Note 7 and finish the job. I have my old Nexus One and Tmobile G1, both still power on last time I checked. I've gotten rid of all other past cell phones we've had unfortunately. Used to have so much trust in the Nexus lineup
Click to expand...
Click to collapse
Lmao.. Yeah I would stay away. Also you have to throw in the fact that the devices only have support until at least Sept. of 2017, then unless you're flashing custom roms your basically stuck.
BIGSAMDA1ST said:
Lmao.. Yeah I would stay away. Also you have to throw in the fact that the devices only have support until at least Sept. of 2017, then unless you're flashing custom roms your basically stuck.
Click to expand...
Click to collapse
Yeah I mean I've always liked the Nexus devices because they always seem to have a good strong developer/modding community. I don't know the definition of a stock - anything. I recently converted my wife & son over to Nexus from Samsung's because I got frustrated with how they now lock down their phones. I have no doubt the 6P/5x (if they survive that long lol) will still be one of primary devices in this community to receive new OS/etc (cyanogenmod/whatever) well past the September EOL. Just look at the older Nexus phones still some of the first to receive the CM14.1 builds.
the.root said:
Yeah I mean I've always liked the Nexus devices because they always seem to have a good strong developer/modding community. I don't know the definition of a stock - anything. I recently converted my wife & son over to Nexus from Samsung's because I got frustrated with how they now lock down their phones. I have no doubt the 6P/5x (if they survive that long lol) will still be one of primary devices in this community to receive new OS/etc (cyanogenmod/whatever) well past the September EOL. Just look at the older Nexus phones still some of the first to receive the CM14.1 builds.
Click to expand...
Click to collapse
Exactly.. That's why I'm still keeping mine and hoping it doesn't decide to go on the fritz again.
It was a lazy autumn day that fateful afternoon when my Asus Zenfone
3 beeped and told me another occasional FOTA update was ready,
"Estimated time: 10 minutes". I pushed "accept."
Then the reboot ... loading ... reboot ... loading cycles began.
(I don't remember the exact words. It was a month ago and I only now
have regained my composure to write about it.)
Holding down the power button forever didn't help, and one cannot just
take out the battery anymore. It was my first cellphone mid-life
crisis.
Normally geographically astute me got on the wrong bus but at least in
the right direction, got off at this big river on the map that was
easy to follow no matter what mental state, and finally made it to the
Asus Royal Service Center or whatever it is called, in Taichung, TW.
I agreed they could wipe everything off my phone and indeed they fixed
it. Yes it was still under warranty and no I didn't "root" it.
Moral of story: from now on I will only check for updates when I am
nearby their service center and not expecting any important calls, etc.
(I see the version it happened with,
https://www.asus.com/zentalk/forum.php?mod=viewthread&tid=184831
was not recalled, meaning the problem only affected me.)
I figured out how to roll back to any firmware I need. Got back my lovely 13.16.5.49 version and with no help from worthless ASUS, who wouldn't even do it even if I RMA it. Apparently they said I should go see a "3rd party phone repair shop, they should be able to do it". What a joke.
Messerschmitt262 said:
I figured out how to roll back to any firmware I need. Got back my lovely 13.16.5.49 version and with no help from worthless ASUS, who wouldn't even do it even if I RMA it. Apparently they said I should go see a "3rd party phone repair shop, they should be able to do it". What a joke.
Click to expand...
Click to collapse
Would you share the rollback method with us, mere mortals?
Just flash the recovery version of the firmware version you want to downgrade to, after which you will have to flash the full firmware image of that firmware version.
Do note that a factory reset might be needed if the phone does not boot after.