Related
Gentlemen,
Has anyone managed to get this thing working, and which drivers/profile did they use? I accidentally stumbled on a sale, and didn't pick up the normal one, but the "universal" - since I had expected it was the newer, better version.
Well, little did I know... I can connect to it, but there's no data coming through (read - no key presses register on the device at all). I've raised a ticket, but that could take a while - and I want to use it!
So, any pointers?
EDIT: See Bottom of Post for Details concerning Flashing a Fix for 3 Button Issue
Hi All,
After a framework-res.apk file mucked up my boot and basically bricked my SGS (stuck on black screen with lit up buttons), I found out unfortunately that my Download/Recovery Modes were 'disconnected' or 'disabled' as some have put it. I use the term disconnected because it is reachable using ADB but NOT the Three Button Method.
After scouring the interwebs for a solution, I was left unhappy and deeply regretful for the silly moderation gone wrong.
My phone was not registering on ADB ("device not found") and hence I couldn't push a new framework-res back in.
After reading up on Wiki, I found that a certain Batch of SGS phones were released with this disconnection of Three Button Boot for Recovery/Download. I found a number of cases existing within the 60-64 range and can confirm that it also existed with mine which was 58.
For others wondering. I purchased mine with Optus in Australia from a retailer around the 18 August.
If you don't know what numbers I'm talking about, check out the IMEI number on your phone/box and it should say XXXXXX/XX/$$XXXX/X. The numbers corresponding with $$ are the numbers youre looking for.
It seems that the issue is mostly haunting the 60-64 range but I can confirm mine was 58.
Edit: Users have reported that 'haunted' phones exist outside of the 60-64 range as mentioned previously. It seems like there is no distinguishing IMEI for the affected phones. I'm afraid you will have to just open the box and try the 3 buttons.
My solution unfortunately was no magic trick, I took the phone back to retailer claiming ELF (Early Life Failure). I received a replacement "70" range one with full functionality.
To confirm again, the procedure is.
1. Power Off Machine
2. Press Menu (Middle Button), holding it
3. Press Volume Up, Also holding it
4. Press Power, Holding it
---- Wait for Samsung Galaxy S Splash
5. Release Power, Holding onto the first two buttons
6. Phone will Boot into Recovery Mode at which point you can release all buttons
To put it Black and White. If you are one of the unlucky folk who are stuck with a 'disconnected' device, I highly recommend taking it back to your retailer and obtaining a replacement. It will be too late when your device 'bricks' and you have no backdoor into the system. When explaining to retailer, make sure you explicitly point out that it is a feature of the phone that whilst not advertised, is expected and a necessity. A simple firmware upgrade through Kies could potentially brick your device for eternity and this is a basic procedure expected to function correctly on your SGS. Hence, a replacement with full functionality is definitely and utterly deserved and within the scope of the Australian Competition & Consumer Commission (ACCC).
EDIT: I explain this on page 2 for another user, figured it is probably helpful for the original post.
Usually, there is a 14 day policy regarding goods deemed unfit or 'problematic' and you can get a replacement with RETAILER. After those 14 days, the responsibility lies with the manufacturer and you must chase up Samsung instead. Your retailer I'm sure will be aware of this. My advice is to act fast and as soon as possible.
Since the problem cannot be induced by user carelessness or intentionally, theoretically you can still chase up the retailer after 14 days, but since you do not have statutory backing, it may be more difficult. a lucky dip of sorts.
If it does get that far, you do have the law on your side and a simple complaint letter to the ACCC demanding assertion of 'Quality of Goods' under Trade Practices Act is the appropriate next step. Photocopy the letter and showing it to your retailer should show them youre serious and convince them to replace your device. If not, go through with it, don't be scared and enjoy a Tribunal Hearing. Let the law work for you because remember you deserve a phone with full functionality.
Just wanted to share my experience and knowledge to anyone else cursed with the same problems as I.
Regards,
EDIT: Far as we can tell for now, there has been no official 'fix' (although) Samsung Canada have recognised the issue and said they will look into developing firmware or software fixes for it. As for 'third party fix', I am unaware of any successful current techniques. As a warning, if someone does develop one, please be reminded that it will void your warranty, and in the case of failure, your phone will definitely brick since you cannot 3 button boot.
Thanks to Davidke, "I found "official" samsung download mode instructions. Feel free to tattoo it to the face of whomever told you it wasn't a "supported" feature.
This is a screen shot from the Samsung Kies Firmware Restoration panel.
It comes up like this in the very rare circumstance where a previous firmware update has failed.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
"
It seems that there have been mixed reports from users contacting Samsung Technicians across the world. Whilst some have shunned this as being a feature sold with the device, others in Canada and Optus (Australia) have said that Samsung recognises it as a fault and is working to resolve it for the affected devices.
Thanks to Bigl666, "Samsung Mobile: Canada Some of you have reported to us that there is an intermittent software issue affecting the Galaxy S and “recovery mode” functionality. We’ll be announcing a downloadable software update shortly. Thank you for your patience."
At the same time, Samsung Representatives have been implying that the feature has been disabled on purpose. A Australian Forum (Whirlpool) has a survey which reports almost a 1 in 3 SGS device has being 'disabled'.
EDIT: There has been a fix released in the android development forum that proclaims to fix the 3 button issue by flashing a new bootloader into the device, overriding the old one through use of Odin. It is risky as with all flashing, but relatively straightforward and user-friendly. It may or may not be compatible with your variant of the SGS. Please read the guide carefully.
http://forum.xda-developers.com/showthread.php?t=785201
Thanks to Richthofen for the brilliant insight and effort.
Thanks!
just a minor clarification.
We've done much research and we noticed the 3 button problem can be on any batch of phones, even when they have newer / older IMEI, it's not specific to any date releases.
Because we have and I personally have tested phones from the same batch and some works meanwhile the others doesn't work.
It appears that in samsung's production line, one of their machines loading the firmwares are not configured properly, thus pushing out units with the buttons disabled
unfortunately this is not something their QA department checks (it's so obvious) so in the same batch of phones you'll have a mix of good and bad ones.
so, the only way to really find out if it work, is to test it first before you pay for it.
i had the three button problem on my galaxyS
and i tried to give it back to optus
but they said they can't change for me because it is not what samsung prefer user to use and that will void the warranty.
i bought it for 8days already and what do you prefer me to do?
use the accc law or just use the galaxy without 3 button.
As a international student, i don't know too much on the law
please give me a suggestion.
SUNNY911002 said:
i had the three button problem on my galaxyS
and i tried to give it back to optus
but they said they can't change for me because it is not what samsung prefer user to use and that will void the warranty.
Click to expand...
Click to collapse
I find that very strange, as I know for a fact that Kies supports this very procedure (well, actually several variants of it, depending on device type) when it detects a problem during flashing. It even has a guide showing you how to switch the phone to Recovery Mode using that Vulcan nerve pinch we all know and love, and then reconnect it to attempt recovery (note that box under the device list in the firmware updater that says "List of Devices Requiring Firmware Recovery"?).
So I am quite sure this IS the official way to recover your phone from a misflash (I'll leave it up to you to define 'misflash' ) and I believe Optus are just scaremongering and/or trying to sidestep replacement costs and effort.
I would say: go for a replacement, and if the rep asks why, you can quote me on this. Just don't mention Download Mode 'cause that ISN'T covered...
Hi Sunny,
Miki is correct. It is a basic recovery procedure that is hardcoded into phones for a purpose that is within the scope of end user day to day use. It is a function that is expected to work and hence the money you pay for it gives you the right to access and utilise said feature.
1. Demand that they replace it with one that has this function. Tell them you risk bricking your phone when upgrading firmware through KIES (Samsung Software) without this feature. They are inexplicably forcing you to never upgrade your phone software in the future because you risk critical data loss by bricking. Tell them that.
2. If they continue to refuse tell them to call up Samsung and find out themselves. Tell them, you don't want to take this route but if necessary you will take it up with the ACCC.
3. If they still refuse, Go to ACCC website or call them and go to the "For Consumers" area and find the lodging a complaint form. Write up a short and detailed letter in the complaint and give evidence of other SGS that do come stock with this function. You paid for the same right and you were misled by the retailer. Since this function cannot be 'fixed' into the device, you demand a replacement.
You can go as far as to say that everyone else who bought this phone stock has this function and its discriminatory for them to not allow you to exercise the same right.
3a. Photocopy your letter along with the complaint forms and fill it out with the retailer details. Take it in and let them know that you will send it in and see them at Tribunal Hearing if you have to unless they replace it for you.
4. Most retailers are like you and me and will definitely give in by now, but if not, then go and send it in and wait to hear from ACCC.
I can't stress to you how important it is to be aggressive especially when you are not in the wrong.
Good luck Sunny.
How do you find out for sure whether the phone has got this recovery mode enabled? My IMEI number is not one of those within the range numbers you mentioned. It's a stock phone and I haven't done any firmware upgrades thus far.
shanghai01 said:
Hi Sunny,
Miki is correct. It is a basic recovery procedure that is hardcoded into phones for a purpose that is within the scope of end user day to day use. It is a function that is expected to work and hence the money you pay for it gives you the right to access and utilise said feature.
1. Demand that they replace it with one that has this function. Tell them you risk bricking your phone when upgrading firmware through KIES (Samsung Software) without this feature. They are inexplicably forcing you to never upgrade your phone software in the future because you risk critical data loss by bricking. Tell them that.
2. If they continue to refuse tell them to call up Samsung and find out themselves. Tell them, you don't want to take this route but if necessary you will take it up with the ACCC.
3. If they still refuse, Go to ACCC website or call them and go to the "For Consumers" area and find the lodging a complaint form. Write up a short and detailed letter in the complaint and give evidence of other SGS that do come stock with this function. You paid for the same right and you were misled by the retailer. Since this function cannot be 'fixed' into the device, you demand a replacement.
You can go as far as to say that everyone else who bought this phone stock has this function and its discriminatory for them to not allow you to exercise the same right.
3a. Photocopy your letter along with the complaint forms and fill it out with the retailer details. Take it in and let them know that you will send it in and see them at Tribunal Hearing if you have to unless they replace it for you.
4. Most retailers are like you and me and will definitely give in by now, but if not, then go and send it in and wait to hear from ACCC.
I can't stress to you how important it is to be aggressive especially when you are not in the wrong.
Good luck Sunny.
Click to expand...
Click to collapse
THANKS A LOT
I bought it for 10 days already and can i still return it to optus?
TMJ: use the three button method and attempt to boot your phone into recovery mode. If you succeed, then you are fine. If not, you may have one of the bad batch. I confirmed and explained the steps to enter Recovery Mode using three button method in the first post.
Sunny: Usually, there is a 14 day policy regarding goods deemed unfit or 'problematic' and you can get a replacement with RETAILER. After those 14 days, the responsibility lies with the manufacturer and you must chase up Samsung instead. Your retailer I'm sure will be aware of this. My advice is to act fast and as soon as possible.
Since the problem cannot be induced by user carelessness or intentionally, theoretically you can still chase up the retailer after 14 days, but since you do not have statutory backing, it may be more difficult.
Hope it works out for you
To shanghai01, i bricked my phone yesterday and i give it back to optus which i said i dont know what happen. they help me to send it to samsung and check for it. If there is any problem, they will change a new one for me.
Will I be charge for any fee, because i purchase it within 14 days. i should have the right to change it, is that right?
I'm trying to find some offical Samsung documentation that shows how to access the recovery mode.
Mine doesn't respond to the three button method and my retailer won't replace it, saying it's not a supported feature.
same problem after JP3 v2
I had the same problem after flashed the JP3 Rooted Clockworldmoded V2 ROM.
The download mode not work but from adb shell i was able to reboot into it.
I decided to flash eclair.
It worked, flashed the device. After that i used the one click root for i9000, it rebooted into recovery and stucked. Cannot apply update.zip, no reboot. There was no way out. If i removed the battery, after rebooted into recovery again. With adb i was able to reboot into bootloader mode, but i dont have ROOT, Recovery and Download mode!
Phone works, but what can i do to Root, or to get into download mode?
Because its not rooted adb shell do not allow any reboot commands.
How can i resolve this problem?
krisz222 said:
I had the same problem after flashed the JP3 Rooted Clockworldmoded V2 ROM.
The download mode not work but from adb shell i was able to reboot into it.
I decided to flash eclair.
It worked, flashed the device. After that i used the one click root for i9000, it rebooted into recovery and stucked. Cannot apply update.zip, no reboot. There was no way out. If i removed the battery, after rebooted into recovery again. With adb i was able to reboot into bootloader mode, but i dont have ROOT, Recovery and Download mode!
Phone works, but what can i do to Root, or to get into download mode?
Because its not rooted adb shell do not allow any reboot commands.
How can i resolve this problem?
Click to expand...
Click to collapse
samsungs sync or update program should be able to that there is a way you maybe can check http://forum.xda-developers.com/showthread.php?t=766589
Sunny, it should be covered as part of Early Life Failure.
You should not be expected to pay any kind of fee.
shanghai01 said:
TMJ: use the three button method and attempt to boot your phone into recovery mode. If you succeed, then you are fine. If not, you may have one of the bad batch. I confirmed and explained the steps to enter Recovery Mode using three button method in the first post.
Sunny: Usually, there is a 14 day policy regarding goods deemed unfit or 'problematic' and you can get a replacement with RETAILER. After those 14 days, the responsibility lies with the manufacturer and you must chase up Samsung instead. Your retailer I'm sure will be aware of this. My advice is to act fast and as soon as possible.
Since the problem cannot be induced by user carelessness or intentionally, theoretically you can still chase up the retailer after 14 days, but since you do not have statutory backing, it may be more difficult.
Hope it works out for you
Click to expand...
Click to collapse
Hello,
A perhaps rather silly question...After you test the 3 button method and it works, how do you end it? Since I just want to test not change anything....
Chryssa
Is this firmware fixable?
Is this firmware fixable?
I would assume it's a feature of the firmware in some way (rather than being a hardware issue).
I'm sure you've worked it out by now Chryssa, but you use the volume up and down button to select reboot now and then press the middle home button. It will auto reboot and bring you back to android.
Mate far as I can tell from my research the problem cannot be reprogrammed by end users or actually so far there has been no documentation observing any success with fixing this problem. To be honest I'm not sure if we have the means to modify firmware and if we did it is definitely out of the scope of our warranty. That is, it would definitely void our warranty
Sent from my GT-I9000 using XDA App
Would be really very useful to find some Samsung official reference to the Recovery mode feature.
Some dealers just tell the excuse "this is not an official feature documented in the manuals" and refuse to change the phone.
So far I have not been able to find it in any official document or reference on Samsung website.
Anybody can help?
this is something very userful
http://forum.xda-developers.com/showthread.php?t=769715
i encourage people from Australia, UK, NZ, and any other nations having problem with Galaxy S to post on the facebook walls of your respective countries
Has anyone tried this method?
1. Take out your sim card, sd card, battery and open Odin3.
2. Put the battery in.
3. Plug in USB. (the phone will power on to that screen)
4. Hold down both Volume keys, and then push power. Hold it and dont let go.
5. Wait for it to go black.
6. When it goes black the 2nd time release power and keep holding the Vol Down and Vol Up.
or even just Power + Vol Down?
"Official" recovery mode instructions
I found "official" samsung download mode instructions. Feel free to tattoo it to the face of whomever told you it wasn't a "supported" feature.
This is a screen shot from the Samsung Kies Firmware Restoration panel.
It comes up like this in the very rare circumstance where a previous firmware update has failed.
*Note: My phone is one that cannot do the 3 button combo. BUT, when I got this panel in Kies it finally worked. Just that time. Though kies failed to recover my firmware, Odin 3 did. After recovery, I can no longer go into recovery or download.
*Note2: The screen shot says to switch to "recovery mode", yet the instructions it gives are for "Download mode". Probably a typo...
O.K., I'm getting pretty desperate - I have an Axon 7 (A2017U) that I need to sell by, like, this weekend, and I'm having trouble restoring it to stock. Well, actually, I guess I'm having trouble now figuring out how to relock the bootloader, as I've got Nougat on there, and have apparently lost the ability to execute fastboot/ADB commands.
Here's exactly what's happened, so far:
1. I bought the phone; unlocked the bootloader (by downgrading from MM B27 to MM B20), and when I was done, ended up with an A2017U that had an unlocked bootloader on it; was rooted with TWRP, and had MM B29. All was cool.
2. Until I used it for about 8 or 9 days. I'm a tractor-trailer driver, and I keep all my music on my phone, so I can plug the phone into my truck's stereo & listen to it while I drive. About 8 or 9 days was all I could take of the Axon 7's distorted speaker/auxiliary jack output (sounds like gain is turned up to 11, on a scale of 1-10!). So, I bought a refurbished (looked completely brand-new, honestly) Moto X Pure Edition (2015). I HATE the current trend of taller/narrower phones, plus I need/want something that Xposed works on.
3. Since I'm gone away from home for weeks at a time, I missed the 30 day return window at Newegg, where I originally purchased the phone, and so now I need to sell it.
4. I flashed three files, via TWRP, in an effort to return to stock; A2017UV1.10B32_bootstack_by_DrakenFX.zip; A2017UV1.10B32_StockSystem_by_DrakenFX.zip, and finally A2017UV1.10B32_StockRecovery_by_DerakenFX.zip. This left me with a device that boots into Nougat, but I can't seem to figure out now how to relock the bootloader. I need to get rid of that unlocked bootloader warning screen. If I press the power key while that screen is displayed, the little (Linux) penguin appears. After 5 or 10 seconds, it goes away, and the phone boots into Nougat. I can get into the stock recovery, and I can get ADB to recognize the phone, when ADB or the Axon 7 Tools program tries to reboot the phone into EDL mode, ADB & fastboot report no devices are connected (adb reboot edl does nothing, except turn the phone screen black, and then ADB reports no devices are connected)
How do I go about returning this thing completely stock, so that I can sell it, and any potential buyer hasn't a clue I unlocked the bootloader/rooted it, and it gets OTA updates, just like when new? FYI; I don't care if it has MM B27 (what it had when I took it out of the box); MM B29, or Nougat B32 (what it's got now) - I just want it to be stock, with a locked bootloader, and the ability to receive/take OTA's.
I quit my job today, because I just wasn't getting enough miles at my employer to make enough money, and I'm starting a new (driving) job on Monday. Orientation is in Oklahoma City, OK, and I have very little cash on hand, at the moment, so I need to get this phone set up and listed on Craigslist, like, tomorrow! Any help anyone can give me would by greatly appreciated by me!
Thanks!
Dennis
Use the toolkit
dmw_4814 said:
O.K., I'm getting pretty desperate - I have an Axon 7 (A2017U) that I need to sell by, like, this weekend, and I'm having trouble restoring it to stock. Well, actually, I guess I'm having trouble now figuring out how to relock the bootloader, as I've got Nougat on there, and have apparently lost the ability to execute fastboot/ADB commands.
Here's exactly what's happened, so far:
1. I bought the phone; unlocked the bootloader (by downgrading from MM B27 to MM B20), and when I was done, ended up with an A2017U that had an unlocked bootloader on it; was rooted with TWRP, and had MM B29. All was cool.
2. Until I used it for about 8 or 9 days. I'm a tractor-trailer driver, and I keep all my music on my phone, so I can plug the phone into my truck's stereo & listen to it while I drive. About 8 or 9 days was all I could take of the Axon 7's distorted speaker/auxiliary jack output (sounds like gain is turned up to 11, on a scale of 1-10!). So, I bought a refurbished (looked completely brand-new, honestly) Moto X Pure Edition (2015). I HATE the current trend of taller/narrower phones, plus I need/want something that Xposed works on.
3. Since I'm gone away from home for weeks at a time, I missed the 30 day return window at Newegg, where I originally purchased the phone, and so now I need to sell it.
4. I flashed three files, via TWRP, in an effort to return to stock; A2017UV1.10B32_bootstack_by_DrakenFX.zip; A2017UV1.10B32_StockSystem_by_DrakenFX.zip, and finally A2017UV1.10B32_StockRecovery_by_DerakenFX.zip. This left me with a device that boots into Nougat, but I can't seem to figure out now how to relock the bootloader. I need to get rid of that unlocked bootloader warning screen. If I press the power key while that screen is displayed, the little (Linux) penguin appears. After 5 or 10 seconds, it goes away, and the phone boots into Nougat. I can get into the stock recovery, and I can get ADB to recognize the phone, when ADB or the Axon 7 Tools program tries to reboot the phone into EDL mode, ADB & fastboot report no devices are connected (adb reboot edl does nothing, except turn the phone screen black, and then ADB reports no devices are connected)
How do I go about returning this thing completely stock, so that I can sell it, and any potential buyer hasn't a clue I unlocked the bootloader/rooted it, and it gets OTA updates, just like when new? FYI; I don't care if it has MM B27 (what it had when I took it out of the box); MM B29, or Nougat B32 (what it's got now) - I just want it to be stock, with a locked bootloader, and the ability to receive/take OTA's.
I quit my job today, because I just wasn't getting enough miles at my employer to make enough money, and I'm starting a new (driving) job on Monday. Orientation is in Oklahoma City, OK, and I have very little cash on hand, at the moment, so I need to get this phone set up and listed on Craigslist, like, tomorrow! Any help anyone can give me would by greatly appreciated by me!
Thanks!
Dennis
Click to expand...
Click to collapse
Just one question - Did you try stuff, like Viper4Android, or using the Qualcomm DAC? maybe you could've ended up using the QC DAC and avoided having to buy an older phone and having to sell this one...
Or you could've tried custom ROMs which use a different driver and stuff.
I'm saying this because the AKM DAC has far different output than the Qualcomm one. I've read that it has like 80 Ohm internally, which would mean that it uses a bunch of voltage. while the Qualcomm one has less than 10 AFAIK. Not a real difference when using headphones (Even 32 Ohm 'phones don't really make any of the two sound louder than the other) but everyone says that one is much louder on lower impedances like 16 Ohm or less.
to try this, you can go to Sound, and put it on Standard mode. Or use the QS tile on MiFavor 5.0
But it seems like you just wanna get rid of it. If that's the case, you can use the toolkit like the guy above me said. There are guides also, but I think the toolkit works too. If you relock and you have tge stock recovery and the phone doesn't DFU brick or whatever, it will get OTAs. But I recommend you to download the latest A2017U Nougat MiFlash folder and flash it via miflash to make it completely stock before attempting to lock it.
lafester said:
Use the toolkit
Click to expand...
Click to collapse
Tried that - no joy.
When I try to flash back to stock, I'm given two options - B15 N & B19 N. I choose B19 N, and it downloaded to my PC last night. It fails every time when I try to flash it. It tells me that EDL device is connected, launches MiFlash, and when I paste the directory to the file I'm trying to flash, then press flash, I'm invariably greeted with errors, mostly about "cannot read hello packet"; "trying to reset status", and finally I get an error, with the statement, "Object reference not set to an instance of an object".
Any further suggestions?
Choose an username... said:
Just one question - Did you try stuff, like Viper4Android, or using the Qualcomm DAC? maybe you could've ended up using the QC DAC and avoided having to buy an older phone and having to sell this one...
Or you could've tried custom ROMs which use a different driver and stuff.
I'm saying this because the AKM DAC has far different output than the Qualcomm one. I've read that it has like 80 Ohm internally, which would mean that it uses a bunch of voltage. while the Qualcomm one has less than 10 AFAIK. Not a real difference when using headphones (Even 32 Ohm 'phones don't really make any of the two sound louder than the other) but everyone says that one is much louder on lower impedances like 16 Ohm or less.
to try this, you can go to Sound, and put it on Standard mode. Or use the QS tile on MiFavor 5.0
But it seems like you just wanna get rid of it. If that's the case, you can use the toolkit like the guy above me said. There are guides also, but I think the toolkit works too. If you relock and you have tge stock recovery and the phone doesn't DFU brick or whatever, it will get OTAs. But I recommend you to download the latest A2017U Nougat MiFlash folder and flash it via miflash to make it completely stock before attempting to lock it.
Click to expand...
Click to collapse
I'm not exactly sure what you mean by "Qualcomm DAC" - what is that?
No, I don't necessarily WANT to get rid of the phone - I still actually have a few days left during which time I can request a return/refund from Amazon for the Moto X Pure Edition - but it kind of now would benefit me more if I can sell the Axon 7 in the next day or two, rather than wait 5 or 6 days for a refund from Amazon.
I generally prefer stock ROMs on my phones, as opposed to heavily customized ones. I know those other ROMs sometimes work better, but I'm just kind of "anal" like that, LOL!
These are the errors I get in MiFlash, through the tookit:
[0.00 COM4]:[COM4]:start flash.
[2.01 COM4]:cannot receive hello packet,MiFlash is trying to reset status!
[4.52 COM4]:cannot receive hello packet,MiFlash is trying to reset status!
[7.02 COM4]:try to reset status.
[7.04 COM4]: object reference not set to an instance of an object.
I got it sorted out. I reflashed TWRP onto the device, then flashed this "A2017UV1.0.0B29_RollBackModded.zip" from here: https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484.
After doing that, I was able to relock the bootloader, so all appears normal/stock, now. I'm on MM B29, now.
Thanks to anyone who chimed in here with suggestions.
Dennis
dmw_4814 said:
I'm not exactly sure what you mean by "Qualcomm DAC" - what is that?
No, I don't necessarily WANT to get rid of the phone - I still actually have a few days left during which time I can request a return/refund from Amazon for the Moto X Pure Edition - but it kind of now would benefit me more if I can sell the Axon 7 in the next day or two, rather than wait 5 or 6 days for a refund from Amazon.
I generally prefer stock ROMs on my phones, as opposed to heavily customized ones. I know those other ROMs sometimes work better, but I'm just kind of "anal" like that, LOL!
Click to expand...
Click to collapse
Look, normal phones have a DAC integrated on the CPU itself, somewhere on the CPU die. a DAC is a digital to analog converter is a thingy that converts digital signals (8-bit or 10-bit) to analog signals (volts, amps) and therefore needs to have very low noise and stuff. The DAC embedded on the CPU has a bunch of noise so the current trend is to add an additional DAC on another package, somewhere on the SoC. In this case this DAC is an AKM AK4xxx. This one is very good for high-end headphones, but not for some other stuff.
I assume your phone doesn't work? If it does, put the sound mode on Standard, and try it. if not I can help some xd
Choose an username... said:
Look, normal phones have a DAC integrated on the CPU itself, somewhere on the CPU die. a DAC is a digital to analog converter is a thingy that converts digital signals (8-bit or 10-bit) to analog signals (volts, amps) and therefore needs to have very low noise and stuff. The DAC embedded on the CPU has a bunch of noise so the current trend is to add an additional DAC on another package, somewhere on the SoC. In this case this DAC is an AKM AK4xxx. This one is very good for high-end headphones, but not for some other stuff.
I assume your phone doesn't work? If it does, put the sound mode on Standard, and try it. if not I can help some xd
Click to expand...
Click to collapse
LOL; yeah, I know what a DAC is - I'm pretty into audio stuff, and have been for many, many years. I just wasn't sure if you were talking about a setting on the phone somewhere, or some app to utilize a Qualcomm DAC, instead of whatever the phone was defaulting to.
In any case, since I've got the ROM issue sorted out (returned to stock), I think I'm just going to go ahead and list the phone on Craigslist; see if anyone local is interested in it. Thanks.
dmw_4814 said:
LOL; yeah, I know what a DAC is - I'm pretty into audio stuff, and have been for many, many years. I just wasn't sure if you were talking about a setting on the phone somewhere, or some app to utilize a Qualcomm DAC, instead of whatever the phone was defaulting to.
In any case, since I've got the ROM issue sorted out (returned to stock), I think I'm just going to go ahead and list the phone on Craigslist; see if anyone local is interested in it. Thanks.
Click to expand...
Click to collapse
Okay then lol
I'd try the other DAC first but it seems like you wanna get rid of it anyways
hello, my first post, I bought a Nexus 6P from ebay. It has an unlocked bootloader (I get the warning when I turn it on) and the os build number is "angler-userdebug 8.1.0 OPM3.171019.01445.3998 dev-keys". there are applications that are not uninstallable: Better Bug, Nexus Logger, Traceur, and Volta. My question is, is this device suitable for personal use the way it is? any other information and/or suggestions are appreciated.
sarmid said:
hello, my first post, I bought a Nexus 6P from ebay. It has an unlocked bootloader (I get the warning when I turn it on) and the os build number is "angler-userdebug 8.1.0 OPM3.171019.01445.3998 dev-keys". there are applications that are not uninstallable: Better Bug, Nexus Logger, Traceur, and Volta. My question is, is this device suitable for personal use the way it is? any other information and/or suggestions are appreciated.
Click to expand...
Click to collapse
I am not sure about the rom version.
https://developers.google.com/android/images#angler
It sounds like somebody sold you a former test model from Huawei.
I can obly assume, that they sold remaining units, but after I searched a bit about those applications I can, like I said, only give you a vague assumption.
The important questions are -
Is the phone functional?Meaning: bootloop, sudden reboots, battery problems?
Are you able to use adb/fastboot? - > Is your phone being recognized by the command 'fastboot devices'?
Did you get a notification that is your system can be updated?
The unlocking of a bootloader isn't a reason to be distinctively suspicious?
But, if you are not satisfied with the phone in whatever way, you can demand to be refunded in regard of the unlocked bootloader with the argument, that the seller has tampered with it and should wrote it in the description.
I bought a phone a while ago and were unsatisfied with it, so I argued with the above mentioned and got my money back.
This was even from somebody private and there are no refund policies, besides the buyer protection.
If you have not passed thr chance and don't want to have a phone, which somebody has used most likely to flash a custom rom or recovery to root same phone, then go for it.
It is not a 100% bulletproof argument, but ebay excepted it, at leat in my case.
If you are okay with the device and adb/fastboot are working, in a way that you for example can test some commands, whicj you have to look up, but __don't flash anything__ as long as you are unsure of the condition.
If you want to remove these apps, you have to look them up, which is expandable and which isn't, before removing them.
And lastly - if you want to remove them, you have to root your phone (tutorials find you here en mass, the same goes for adb/fastboot usage).
But the same goes here for testing a ADB and fastboot usability, please.
If you decide to keep it, then you can remove system apps (>before a search if you phone goes boom..), aith this app for example
https://www.apkmirror.com/apk/jumobile/system-app-remover-root/system-app-remover-root-7-1-release/
With this, you are able to backup the apps if you want to remove them.
Some apps, especially the so-called 'bloatware' is from now on then, quite resistant.Just empty the trash, which you find in the app's menu.
Titanium Backup, a very, very versatile application, is fir example capable of backing up your entire apps including data, but I think, you have "some" pointers now and can give it (with carefulness) your own try.
Have fun & good luck
so, this phone died for me in 2017, and have been in a drawer since then. then i thought why not ask. so long story short if i remember correctly: bought it new. i rooted it since all the cool kids do that. then i did some update i think. and then in the winter of 2017 in beginning it just started behaving weirdly for me and then it turned off and all kinds of shenanigans. cant restart using different methods, sometimes it blinks, sometimes that bios menu comes up. blabla. so i tried to send it to the local repairshop that the seller used. but since i had it rooted they refused to fix it. so now i have a phone that costed 600 euro + 70 euro in service cost and it doesnt work. and then its been in a drawer since then.
i took it out, had it and the battery in a freezer for a while like some has said on internet didnt work.
anyway. does anyone here know any tips? if i want to flash the room can that be possible? or is this a lost cause? was this a common problem with note 4? i loved it and it crushed my heart when it stopped working. i still have a few months of pics etc on it from back then that ive never been able to get out. i attached it to the computer now and the computer makes a sound but nothing more.
any tips?
darknessviking said:
so, this phone died for me in 2017, and have been in a drawer since then. then i thought why not ask. so long story short if i remember correctly: bought it new. i rooted it since all the cool kids do that. then i did some update i think. and then in the winter of 2017 in beginning it just started behaving weirdly for me and then it turned off and all kinds of shenanigans. cant restart using different methods, sometimes it blinks, sometimes that bios menu comes up. blabla. so i tried to send it to the local repairshop that the seller used. but since i had it rooted they refused to fix it. so now i have a phone that costed 600 euro + 70 euro in service cost and it doesnt work. and then its been in a drawer since then.
i took it out, had it and the battery in a freezer for a while like some has said on internet didnt work.
anyway. does anyone here know any tips? if i want to flash the room can that be possible? or is this a lost cause? was this a common problem with note 4? i loved it and it crushed my heart when it stopped working. i still have a few months of pics etc on it from back then that ive never been able to get out. i attached it to the computer now and the computer makes a sound but nothing more.
any tips?
Click to expand...
Click to collapse
Sounds to me like either dead emmc or misconnection.
If it's just? misconnection there are tips (increasing the pressure by cardboard).
Can you access download mode?
Sometimes it shows there "dead emmc".
I somewhere read about a testing app.
Gotta search.
Where in Europe are you?
In the German Android-hilfe forum there is a member who fixes that.
Either exchanging the emmc or resoldering it.
If the chip is dead probably the data are lost.
afaik flashing the stock ROM deletes data.
It's a known problem, yes.
bmwdroid said:
Sounds to me like either dead emmc or misconnection.
If it's just? misconnection there are tips (increasing the pressure by cardboard).
Can you access download mode?
Sometimes it shows there "dead emmc".
I somewhere read about a testing app.
Gotta search.
Where in Europe are you?
In the German Android-hilfe forum there is a member who fixes that.
Either exchanging the emmc or resoldering it.
If the chip is dead probably the data are lost.
afaik flashing the stock ROM deletes data.
It's a known problem, yes.
Click to expand...
Click to collapse
Excellent feedback and assessment @bmwdroid . Thank you for sharing.
I only wish to add that there is a way to flash Samsung firmware while keeping user data. Of course, this method wouldn't be effective when it comes to emmc hardware failure so Im posting it for general information purposes only.
If you have downloaded the firmware for your Samsung Galaxy device you’ll find 2 CSC binaries with *.tar.md5*extension (namely CSC and Home_CSC ) inside along with BL, AP, and CP.*CSC*and*HOME_CSC*are necessary for different purposes, and you have to choose one or the other depending on your goal.
CSC –*If you flash the CSC file, it’ll perform a*factory reset*of your Galaxy device and wipe all data while installing a new firmware to bring your device to the same*state as it was when you purchased it. Go with CSC if you want a*clean installation.
HOME_CSC*–* On the other hand, if you want to*keep your Samsung phone’s data and settings*even flashing the stock firmware, you can select the HOME_CSC file.