Related
hello everyone.
I am still within my 30 day return period with my 8125. I need to exchange it because my keyboard is loose!
I updated ROM to the new IMATE, lost all WIFI , so reverted back to the cingular rom that is on the xda FTP , and I need to get the splash screens back to factory, i dont want to raise any brows when i return this thing.
can anyone help? my days are numbered!
thanks!
in an exchange in a shop they won't know how to check such minor details out. especially when it's not a software fault you are returning for.
chill
joe (the returns master)
hey joe.
i am sending the phone back to cingular.
they are shipping me a replacement and charging me for it, i get my money back when they recieve this phone at the warehouse.
he said they get the phone, restore it to factory settings, and then mark it as a refurb.
will they see this IMATE rom and ROM updates and give me some bull**** for that?
thanks for your response.
dan
Hope this previous post helps
http://forum.xda-developers.com/viewtopic.php?t=44068&highlight=cingular+8125+splash+screen
there other posts, I think it possible. I know how you must feel - sort of mess I get myself into
Hope this too - change splash on charmer and wizard.
http://forum.xda-developers.com/vie...r=asc&highlight=cingular+splash+8125&start=25
button wrote in the post
"That's my modest attempt to make the process easier...
Just put your 320x240 true color 24-bit .bmp, 'portrait' orientating image file named 'splash.bmp' and attached tool in the same folder, and run 'splash_bmp_to_wizard.exe'. Be sure, that ActiveSinc is connected.
wizSplash - new ver., splash backup is added. Before replacing splash image, put new file 'splash.bmp' into 'C:\wizSplash' folder.
Before you launch it, please disable firewall, antispy, antivirus, brandmauer..etc software! "
i used buttons tool to change the IMATE splash screen.
aparently no way to get rid of HTC's. this should do.
thanks guys
make sure you lock it again before sending it back.
All the best
When I was thinking of upgrading the ROM on my O2 badged XDA-mini-S, I was wondering what would happen if I had to return the device under warranty with the upgraded ROM.
I came to the conclusion that I have insurance on the phone, so any problems and my device will go for a swim before I pay the £20 excess and get a brand new device.
This also stops the network arguements that the any damage was caused by the upgrade or the infamous "ware and tear"
I just bought a Note 4 from a pawn shop. I checked the IMEI with as many online free checking services that I could find. After I connected it to wifi, I started getting these pop ups saying that the phone is owned by Rent-A-Center and it needed an unlock code. I did a little searching and I guess this is a fairly new thing as of a few months ago. I was able to return it to the pawn shop and cancel the transaction, so I was lucky, but other people who have had their phones for months are all of a sudden getting these messages and being left with no real recourse.
I know this is part of the risk when buying a used phone, but I wanted to see if anyone knows a work around for this? I saw some people were able to install CM and then had no more problems. Someone else was talking about deleting certain partitions that don't get wiped during a factory reset. So does anyone have some good info on this problem??? And just a warning to anyone buying a used phone, you might want to call Rent-A-Center and ask them if they have anything to do with the IMEI number in question. If they are going to lock out a phone, they should find a way to be listed on the free checking services.
Here is a good thread with some info
Found this thread here on XDA
http://forum.xda-developers.com/android/help/rent-center-locked-galaxy-s5-t3070877
It has some good info about various ways to get around the problem. I just wonder if RAC will eventually blacklist these phones instead of just having a software lock.
First off, I just wanted to thank you guys for always being so helpful. It's really nice to have people like you to discuss things with.
I just bought a used Nexus 6P, and it seems to suffer from the battery shutoff issue once it gets below ~10%. The original owner bought directly from the Google Play store in Sept 2016, so it's still under warranty with Google, and I believe that means I should be able to RMA it.
Before I do anything, I'd like to have as much info as possible to make this go as smoothly as possible; I'm traveling out of the country at the end of May and I need a device that works pretty much flawlessly by then, so timing is a factor.
Question 1
If I make a Nandroid backup in TWRP, move it to my computer's Hard Drive, copy it onto the RMA replacement, and restore it, that would very quickly restore me to where I was with my current phone without any issues, correct?
If it matters, I'm unlocked, stock-rooted on 6.0.1 (MTC20L), stock kernel, and TWRP (v3.0.3.0 iirc.) I used Nexus Root Toolkit for all of this.
Question 2:
Besides the ones I've listed below, what common Nexus 6P issues do I need to watch for when I get my RMA device?
Device overheating
Bootlooping
Random Reboots
Powers down once battery is below __%
Microphone / call quality issues
Screen discoloration issues
Bent / broken volume buttons
Screen separating from device
Wifi / radio / bluetooth / gps issues? (not sure if this is relevant)
Question 3:
How does the RMA process actually work?
To RMA, do I just call the Nexus / Google support line, give them my IMEI, explain that I'm having the battery shutoff issue and request they send me a warranty replacement?
Are there additional steps I'll need to take because I'm not the original owner?
Do I have to send Google my phone for them to send me the replacement, or do they send me the replacement first and then I send them my current device once the replacement arrives?
What's the typical turnaround time between making the RMA request and receiving the new device?
Anything else I should know?
kwest12 said:
First off, I just wanted to thank you guys for always being so helpful. It's really nice to have people like you to discuss things with.
I just bought a used Nexus 6P, and it seems to suffer from the battery shutoff issue once it gets below ~10%. The original owner bought directly from the Google Play store in Sept 2016, so it's still under warranty with Google, and I believe that means I should be able to RMA it.
Before I do anything, I'd like to have as much info as possible to make this go as smoothly as possible; I'm traveling out of the country at the end of May and I need a device that works pretty much flawlessly by then, so timing is a factor.
Question 1
If I make a Nandroid backup in TWRP, move it to my computer's Hard Drive, copy it onto the RMA replacement, and restore it, that would very quickly restore me to where I was with my current phone without any issues, correct?
If it matters, I'm unlocked, stock-rooted on 6.0.1 (MTC20L), stock kernel, and TWRP (v3.0.3.0 iirc.) I used Nexus Root Toolkit for all of this.
Question 2:
Besides the ones I've listed below, what common Nexus 6P issues do I need to watch for when I get my RMA device?
Device overheating
Bootlooping
Random Reboots
Powers down once battery is below __%
Microphone / call quality issues
Screen discoloration issues
Bent / broken volume buttons
Screen separating from device
Wifi / radio / bluetooth / gps issues? (not sure if this is relevant)
Question 3:
How does the RMA process actually work?
To RMA, do I just call the Nexus / Google support line, give them my IMEI, explain that I'm having the battery shutoff issue and request they send me a warranty replacement?
Are there additional steps I'll need to take because I'm not the original owner?
Do I have to send Google my phone for them to send me the replacement, or do they send me the replacement first and then I send them my current device once the replacement arrives?
What's the typical turnaround time between making the RMA request and receiving the new device?
Anything else I should know?
Click to expand...
Click to collapse
I recently did and RMA for a bad screen.
1. You can do the restore, but I would only restore the data partition. No need to restore the partitions.
2. Check for screen response everywhere on the screen. In the developer option turn on "show screen touch". Make sure all points on the screen are good. My first replacement had a ¼ inch band that showed no response.
3 You can do it online. They will ask for a credit card and the will send an advance replacement with a shipping return label.
kwest12 said:
First off, I just wanted to thank you guys for always being so helpful. It's really nice to have people like you to discuss things with.
I just bought a used Nexus 6P, and it seems to suffer from the battery shutoff issue once it gets below ~10%. The original owner bought directly from the Google Play store in Sept 2016, so it's still under warranty with Google, and I believe that means I should be able to RMA it.
Before I do anything, I'd like to have as much info as possible to make this go as smoothly as possible; I'm traveling out of the country at the end of May and I need a device that works pretty much flawlessly by then, so timing is a factor.
Question 1
If I make a Nandroid backup in TWRP, move it to my computer's Hard Drive, copy it onto the RMA replacement, and restore it, that would very quickly restore me to where I was with my current phone without any issues, correct?
If it matters, I'm unlocked, stock-rooted on 6.0.1 (MTC20L), stock kernel, and TWRP (v3.0.3.0 iirc.) I used Nexus Root Toolkit for all of this.
Question 3:
How does the RMA process actually work?
To RMA, do I just call the Nexus / Google support line, give them my IMEI, explain that I'm having the battery shutoff issue and request they send me a warranty replacement?
Are there additional steps I'll need to take because I'm not the original owner?
Do I have to send Google my phone for them to send me the replacement, or do they send me the replacement first and then I send them my current device once the replacement arrives?
What's the typical turnaround time between making the RMA request and receiving the new device?
Anything else I should know?
Click to expand...
Click to collapse
1) You can restore boot, system, and data. I suggest manually flashing the Vendor.img. However, you must remove the lock screen security completely. Due to the security measures regarding fingerprint sensor integrity, anything related to it's functionality is not covered by a TWRP backup. Restoring a TWRP nandroid on another device will make its fingerprint sensor malfunction. Perform the steps in post #9 of the thread linked below to have a working fingerprint sensor on the replacement device after restoring a TWRP nandroid:
https://forum.xda-developers.com/showthread.php?t=3307734
3) From what I've read on XDA, you need the original receipt from the Google Play transaction. So email the buyer and ask for their receipt.
Sent from my Nexus 5X using Tapatalk
can anybody confirm that when you send your device to Google we need to lock the bootloader flash stock recovery and img?
Also when chatting with google support should i tell them i am unlocked bootloader?
can somebody link the google chat support messaging I don't want to call them by phone.
AndrewM3 said:
can anybody confirm that when you send your device to Google we need to lock the bootloader flash stock recovery and img?
Also when chatting with google support should i tell them i am unlocked bootloader?
can somebody link the google chat support messaging I don't want to call them by phone.
Click to expand...
Click to collapse
You need to go completely stock including flashing stock images and lock your bootloader. Don't tell them you unlocked it, there is no need to bring up something like that if they don't ask.
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
Just few days before i have fixed the bootloop issue that have become in my asus zenfone ze505kl by erasing modemst1, modemst2 and fsg files but then I realized that i didnt take any backup to restore qcn file. I have searched in internet but i couldn' t find any files that correspond for my phone. If anybody can help me i will be appreciate.
Please help me, i cant find still, i m searching. . I have found msm8939 qcn file but its not working for me. It cause bootloop error in my phone. Are there another solutions that i can apply for this issue ?
Same here, m8 - through the same rabbit hole as you. As a matter of fact, no QCN files will work anymore. As far as I've concluded from my unsuccessful journey (2 yrs+) the modem chip is damaged probably due to some physical shock or gradual wear. Yet, I don't confirm it is actually the case, and the bootloop causes reboots too early to even catch logs to see what causes this. Anyone's best bet would be to catch logs on serial port; ttyHSL0; that is, if one has such a hardware to catch that in the first place. ASUS service center has those, so they can know. I don't know what you did already, been 4 months+ for you, if those guys told you that they're going to do some risky move on the motherboard that might damage it permanently - I think you should let them do it - just keep around cash for buying a phone for primary use just in case.
Pro Tip:
If you still want to use it "up to its potential" without the SIM facilities, buy a cheapo phone with WiFi Hotspot feature, tether your Zenfone with its hotspot, answer phone calls and sms on the cheapo, do everything else on the Zenfone. That is how I'm doing it till now, and trust me, you'll really find it tasteful [actually, this method in one way elevates privacy and anonymity up to a very good level - bright sides of things...].