Hey there forums.
I've been an active browser of XDA but never really created an account but I've done so to have assistance with a particular situation with my device.
So the other week, i had spent 150 dollars on a Sony Xperia XA F3115 from Vodafone, Australia and it turns out that the bootloader was locked because of Vodafone and i wasn't going to pay 50 dollars to unlock it. I alternated and browsed the internet (Mostly XDA but other sources aswell) to figure out if there were any methods of bypassing this, whether it be easy or not - I was willing to try anything that seemed like it had a chance to work, without a 100% failure rate. Reading responses to particular methods, i was drawn into one method of just reflashing the stock firmware onto the device and then rooting, flashing and doing everything from there (as the device was no longer locked by Vodafone at that point).
I have completed this task as of this morning, and the device booted successfully. As soon as i unlocked my device, i had received the general android setup window but half way through, i got spammed with "Name has stopped responding" countless times to the point where the phone was literally unusable, it would just pop up again right after closing it - So i decided to restart the device. This was probably a big mistake, it booted fine but it said "Android is updating" and had the whole "Applications updating 100 out of 255" stuff happening. Then it booted to the lock screen, which i had previously setup before i flashed the device which didn't really surprise me too much.
Then it rebooted. Now every single time i boot the device, it reboots to the "Optimizing apps blah out of blah" and then will reboot upon the notification bar popping up, but no lock screen. I decided that my best cause of action was to download another firmware and try that one instead, but I'm unable to boot my device into bootloader mode as it's impossible to happen. I turn off my device, plug it in and hold the volume down button but it refuses to work anymore.
Now that the situation has been explained, I'd really like your help to see if i can have this resolved. I'm baffled as to why Vodafone even locked it to begin with, since the phone was prepaid and had nothing to do with any sort of plans - nor was it even available as a plan. I don't have the money to buy a new phone, and they have already denied me a refund. I need this phone for work and the mistakes i made were stupid - Please, i need assistance. You're all hopefully more tech savvy than i am in the field of mobile phones.
Related
First of all this is my first attempt at rooting/reviving a Google phone. Although I have 10 +years of building computers etc. under my belt and I have owned multiple android devices since G1 launch so this should not be to hard to understand.
With that said. Here is my situation and as much knowledge as I have on how it arrived at the current state.
A friend of mine bought this Nexus on craigslist. It worked for a week or so, then would not boot up past boot screen icon (no lock on boot screen). I took it off his hands for $50.
Now I am able to get the phone in to the fastboot screen (when plugged in it reads 'fastboot usb'). I was also able to get into the the factory data reset screen. No matter the option I selected or cleared out it always returns me to the same frozen boot up image.
I downloaded SDK, superboot, drivers are installed (and updated ) and I have followed to the T all forum post on how to unlock the bootloader.
Everything goes great until... I get to this hiccup!! I am able to connect the device to and get a response with device pin number in command screen.
Then I type in 'fastboot oem unlock' and it gives me this terrific message:
... INFO[ERR] partition_read: :Failed to read page 261120 or it is em
INFOpty
INFO[DISPLAY_ERR] sp_custom partition: sp_custom_img_hd read err
INFOor!
INFO[DISPLAY_ERR] Can not load custom splash!
INFOLoading custom splash failed!
OKAY
What next????
I have also noticed that i get an interesting message when I first select bootloader on device, just for a second then returns to normal (pictures attached of this!)
One step I am unable to do that I believe may be the problem, since I have never been able to get past bootscreen on the device I have not been able to select the USB DEBUGGING option. Is there anyway around this?
If anyone is able to walk me through getting past this point and running vanilla 2.1 (I can take it from there ) I will donate $25 to this site as well as paypal you personally $25.. or you can have the entire $50 donated to the site
Thanks in advance for reading this post and helping a fellow Android lover!
Fix your Phone
I do not know if you will be able to fix it yourself but if you want you can contact google, send it in to them, and they will probably replace the phone for you. Assuming it has the standard 1 year warranty, you would be elligible for repairs and possibly google completely replacing your phone, giving you a new one. My G1 had problems and i tried fixing it myself with all kinds of stuff but eventually i contacted google and after i mailed it in they send me a new unit.
I am glad to see there are at least four other folks about sufficiently embarassed to lead with their apology. Enough pleasantries:
I am capable enough to root my device but am careful enough apparently to avoid triggering inadvertent boot sequences, to wit: I have certainly dropped my Verizon-flavored S in bootloader a few times and with patience I was able to return to a normal boot sequence with no harm/no foul.
Today I forced my imac to serve up its wireless connection to my device via bluetooth (because I accept the fact I need Verizon's signal strength but I refuse to relinquish even one more dollar to them than I absolutely must so I loaded down with Google voice, etc. and EVEN THOUGH I OWN THE PHONE of course I cannot go prepaid and have a 4G connecetion),... I know, stream-of-consciousness is annoying but I am only trying to create a little background).
SO, my otherwise find rooted S, soon after but NOT immediately following my ham-handed creation of the imac connection share via bluetooth it went into the following boot sequence:
1.BOOTLOADER
2. bootloader "ends" and it begins to "charge" based on iconography
3. user grows impatient and, since it always worked before, tries to manually force a normal boot
4. Google icon appears, Stylized X icon appears, home screen appears for an instant and then the display immediately reverts to the X
5. Repeat 4 ad infinitum.
I recognize the fact that I really am not qualified to be a part of this discussion, but, I am self-taught and making sincere effort and my experience is that pros recognize that and will offer a quick work of advice.
My thanks to anybody that took the time to read this post, good evening from Georgia.
1. It's certainly not dumb to ask a question
2. Could you give some more info on you device, like which rom you're running and with which kernel? And maybe what recovery you've got installed?
Me Gusta!
I've had my Oneplus One since the beginning of 2015, up until now it's been honestly fantastic, with very few issues whatsoever, certainly nothing that has bothered me at any rate. That's up until last night;
My phone was lying on my desk next to me with the screen on updating some applications whilst I was writing on my computer - suddenly, it starts to vibrate, one continuous long note, I naturally picked it up and looked at it, at which point the phone turn itself off in my hand. That was unfortunately the last I ever saw of my phone alive. This happened at about 6PM yesterday evening, since then I've tried everything within my power to get it to work. I can't access the bootloader, in order to get to fastboot (which would allow me to fix all my issues by enabling me to refresh the device), nor can I access my recovery. The phone turns on and displays nothing, it vibrates, but that's it.
The phone was running the latest COS13.1.1 update (X1) which I had flashed the day before, it was running the stock kernel for the ROM, the ROM was however rooted.
I know a fair amount about android, I also know a fair amount about the OPO, to me, I think something about the LOGO partition has gone wrong. The LOHO partition being responsible for the images shown in the bootloader, fastboot, splash screen etc.... I'm just not sure how that would have happened.
Either way, I don't know what to do, the one doesn't register to my computer in fastboot or adb , so both those routes seem closed. I primarily use a Mac for my work, I'm yet to try plugging the phone into a PC.
I've submitted a ticket to OP, and have spoken to an adviser who moved my case to a 'specialist', but I'm yet to hear back on that one.
Any help would be massively useful, because I need this phone for my work, and just general communication.
Thanks for reading,
Ben
Here, try this http://http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Gday everyone.
I just got this phone and since it was first powered on I've had issues. I will likely be going back to the carrier tomorrow and asking for a replacement, but wanted to put my experience down here. Ive looked at a lot of other threads, but all of them involve unlocking of bootloader, flashing etc - I havent done ANY of this (yet). Its fresh out of the box.
Location: Australia
Carrier: Optus
Model: MHA-L09 (cant access extended model number)
So first up, had issues connecting to the carriers in-store wifi, which uses a captive portal.
When I finally got it going I was presented with a Chinese site - id accept this usually considering it is Huawei.
This phone is a replacement for my dead Note4 and as such I wanted to restore apps, as I had no internet, I skipped the process.
Got back to my office and connected to my wifi fine, so decided to factory reset to get a fresh start.
Noticed that after reset the initial process was in a different order. Restored from Google and all apps downloaded, happy days for a couple of hours, just waiting for my service to port over.
2 hours later, I decide to restart the phone, it gets hung up on the Optus logo which is displayed before the reboot starts.
Hard reboot.
System loads, I figure I may as well see about a firmware update. Get 'Package installer isn't responding' errors. Try again, works, no updates available.
Go to google photos, get 'Package installer isn't responding' error.
At this point I think, f**k - what is going on here.
So I reboot into recovery to wipe the cache. This processes fine, but then the option to reboot the phone doesn't work.
Hard reboot.
Boots into recovery without me touching it.
Hard reboot. - happens again.
So then I think, fine ok, I've upset the balance, lets do a factory reset.
Factory reset hangs on 99% for over 30 minutes.
Against better judgement - hard reboot.
Now I have the EMUI logo with a nice round 0% under it... and that's where its staying.
Thoughts?
I have to fly interstate on the weekend and cant really afford unreliable comms. Should I ditch the Huawei?
Thanks all.
So - it seems that nowhere did i find a mention of the fact that if i plug it into my PC and goto the recovery mode, it loads eRecovery. Whilst this didnt actually work (I believe it only works for CN firmware) It did give me a shutdown option. I shut it down and started it again and im back into a fresh install.
Lets see how I go now...
Never restore backups from other phone.
Wow, helpful.
I didn't restore the backup from another phone, just apps, ie google downloaded the apps I selected.
The device is still performing poorly, even a standard reboot does not succeed, instead it hangs on the carrier logo before actually rebooting.
Ill take it back to the store tomorrow and ask for another one, im hoping Ive just gotten a dud.
Good evening,
Hate to bother everyone since you're all busy, however i've been trying for 2 days now to do a couple things with this new phone. This LG Aristo 2 was handed to me by a sister in law (not purchased from swappa); What we've been trying to do is have the Phone unlocked and used for T-mobile however it appears that no matter how much we try resetting the phone, booting the unlock app and being greeted with a "Unlock failed: Phone already unlocked" screen and using a different SIM. The phone will pick up the signal, turn to 'searching...' and then connect to the network again but not allow calls/data to go through, The APN settings are also correct.
So plan B is to reinstall the stock android software (kdz) from https://lg-firmwares.com/lg-lmx210ma-firmwares/; Unfortunately i'm always greeted with an error saying that it cannot complete. Unsure what else to do at this point, Any recommendations?
To clarify, the reason why I'm trying to ensure the unlock has been successful is because we plan to use for calls and data. Texting seems to work, the APNs are correct but data services and calls don't seem to go through, unsure why.
To unlock it via app, you can spend $7ish on eBay. It would take 2 days to get it unlocked.