Hi all, Its been almost 2 years since i did an OTA update on my play and bricked it. Using the first patch that came out to fix this problem of phone not booting, i "destroyed" the bootloader or something or RadioRom and my phone does not accept any sim. it was originally unlocked.
Has anyone come up with a way to revive the play to make calls or something. cos its really depressing having a phone jus lying there wasting away, only to be brought out when needed for navigation or games.
Someone please helppppppppppppppppppppppppppppppp
Assuming your radio/sim is in working condition, I don't particularly see how bricking your phone can cause the phone to act like that. Have you tried flashing the stock firmware on again after it was bricked? And have you tried reunlocking the phone and putting on a custom rom/kernel?
jayact~ said:
Assuming your radio/sim is in working condition, I don't particularly see how bricking your phone can cause the phone to act like that. Have you tried flashing the stock firmware on again after it was bricked? And have you tried reunlocking the phone and putting on a custom rom/kernel?
Click to expand...
Click to collapse
about 2 years back, shortly after this phone came out, a problem was noted with OTA updates on unlocked bootloader.
The phone was bought "sim-free" or factory unlocked depending on which nomenclature is correct.
With an unlocked bootloader, the OTA update caused the phone to go dead.
in a haste to get the phone working again, a patch was released which broke the radio rom but got your phone to boot again. i believe the initial patch was released by BLAGUS.
well that killed my radio and now, no sim inserted works.
I reinstalled the stock firmware on it. tried several variants from different regions in the hope that it might work. was getting help from Wazz, Blagus and Bin4ry but seems they've moved on to more important projects now.
2 years ago, I would've brought my phone to the carrier. While your warranty would have been voided, you still should've been able to tell them that it is THEIR fault that it's not working since it was their OTA update that broke the phone. At the very least, they should've been able to get you a discount on a replacement Xperia Play, or at least I think they would have if they wanted to keep a happy customer.
Waqas said:
about 2 years back, shortly after this phone came out, a problem was noted with OTA updates on unlocked bootloader.
The phone was bought "sim-free" or factory unlocked depending on which nomenclature is correct.
With an unlocked bootloader, the OTA update caused the phone to go dead.
in a haste to get the phone working again, a patch was released which broke the radio rom but got your phone to boot again. i believe the initial patch was released by BLAGUS.
well that killed my radio and now, no sim inserted works.
I reinstalled the stock firmware on it. tried several variants from different regions in the hope that it might work. was getting help from Wazz, Blagus and Bin4ry but seems they've moved on to more important projects now.
Click to expand...
Click to collapse
Alright, I understand now. I wish I knew more, so I could help you out.
Was this the patch you used? I believe I used this ftf to relock my bootloader when my phone was bricked after I accepted an OTA update, just as you did. My radio never had any issues, though.. That said, my phone was sim-locked, since I have the R800x, so maybe that has something to do with it..
Related
I know that they do a slow roll out process for the OTA's, and all. But, anyone have any clue as to how long the process may take? I have a 6 day old straight from the play store gnex. Not root, or nothing completely stock still.
It depends but should be under a week if not sooner.
It's frustrating that on this phone you need an unlocked bootloader to install a downloaded update package. I didn't bother to unlock my phone when I first got it since with my N1 it wasn't necessary. Having to wait sucks...
pfmiller said:
It's frustrating that on this phone you need an unlocked bootloader to install a downloaded update package. I didn't bother to unlock my phone when I first got it since with my N1 it wasn't necessary. Having to wait sucks...
Click to expand...
Click to collapse
you dont have to unlock your bootloader.
you just have to wait for the OTA update to get to your phone. they roll out in batches and are not done all at once.
Yep, supposedly they started rolling out JB already ..
i havent got jack Sh!t yet here in the NYC area
Zepius said:
you dont have to unlock your bootloader.
you just have to wait for the OTA update to get to your phone. they roll out in batches and are not done all at once.
Click to expand...
Click to collapse
I know, that's exactly what I'm complaining about though. With my completely stock N1 I didn't have to wait. I know in the past for some people it took weeks before the OTA got to them. Not cool.
I got myself a wildfire s a short while ago, so I could teather my galaxy tab 10.1 (my S2 was stolen). It seemed a good idea at the time, to get a cheap, small Android phone, for this purpose and just making phonecalls.
I knew the phone had limited storage, but at the time wasn't really an issue.
I unboxed it, started it up, put my sim card in, and away I went. ( I bought it sim - free brand new from carphone warehouse )
once set up, it informed me there was an ota update, which went fine, no problem. I continued to set the phone up with my favorite softwares, and everything was great.
This is where the problem started.
A few weeks later, It told me there was new update, so update i _TRIED_ . And failed. It told me that the firmware on the phone was not HTC, and would not be updated.
Not a problem, I dont care, i thought. It does all i need to do, and I didnt really want to do a full reset on it, so I didnt bother for a couple of months, it was fine.
Eventually, I started to find the tiny storage quite irritating, so got myself a class 10 8GB SD card, and looked into using somthing like Data2SD.
No problem, Iv rooted a few phones, so did the required reading into getting root and s-off. Easy ( I thought ).
I took myself off the htc dev, to download the unlocked bootloader today, and attempted to install. UH-OH.. Error 190 .. Wrong firmware version.
I decided now was as good a time as any to hard reset, as it would happen anyway, and retry the ota update..... FAIL!
I contacted HTC, and they said I would have to send off for repair ( I guess I could, its stock, unmodded in any way yet ) but that would mean I would be without my phone.
then I tried this : http://forum.xda-developers.com/showthread.php?t=1445867&page=1
didnt work. I need the new 2.33.401.3 software, but im stuck on 1.33.401.3 (Android 2.3.3)
Is there a way to root and s-off the older firmware as HTC DEV now require you to have the newer firmware to unlock the bootloader, or atleast manually flash the newer firmware??
Plz help me, before i chuck my phone in the sink!
Thanks,
Dave
Get the RUU of 2.13.401.whatever from somewhere (You'll find it in the 'Shipped marvel rom collection' at the top of the dev section) and run that first before you you run the unlockable bootloader one and tell us what happens
This worked perfectly. Thankyou. I downloaded the HTC EU rom, for 2.13.401.3, Flashed it in, and the rest worked.
Thanks again,
Dave
Hi, digitalwarfare
you flashed this
RUU_Marvel_S_HTC_Europe_2.13.401.3_Radio_47.23c.35.3037_7.54.39.28M_release_236989_signed.exe
or this
Marvel_S_HTC_Europe_2.13.401.3_Radio_47.23c.35.3037_7.54.39.28M_release_236989_signed_ROM.zip
What are the differences, please?
As the title states, has anyone's 2013 n7 bricked after the 5.0.2 update when flashing a factory image instead of the OTA? Mine bricked after taking the 5.0.1 OTA, but i now have it back from Asus after repair and am wanting to flash the factory image to 5.0.2. However, if anyone has experienced bricking as a result of this (or 5.0.1 or 5.0) being flashed and not just the OTA, which we know is bricking devices, then I will stick with 4.4.4 for now.
Thanks
You can not brick a Nexus 7 unless you somehow screw up the bootloader and can no longer enter the bootloader.
khaytsus said:
You can not brick a Nexus 7 unless you somehow screw up the bootloader and can no longer enter the bootloader.
Click to expand...
Click to collapse
Well then some form of that must be happening due to or in very strange coincidence with the 5.0, 5.0.1, and 5.0.2 updates - just ask those of us whose tablets turned off only to turn on and be stuck at the google logo with so far zero solution for fixing it other than a hardware replacement. My tablet was at ASUS's repair factory for almost a month and had the motherboard replaced. This was after a "successful" OTA update to 5.0.1 that worked for a few days and then died. This has happened more than just infrequently to many members on here recently.
So what I would like to know is is anyone experienced the same "successful update" and then a few days later a dead tablet via factory image flashingof 5.0+. We already know that taking the OTA to 5.0+ might be a problem, and before I flash up to 5.0.2 I'd like to hear if anyone did a manual factory image flash and still had the die a few days later issue, despite not going via OTA.
Norcalz71 said:
Well then some form of that must be happening due to or in very strange coincidence with the 5.0, 5.0.1, and 5.0.2 updates - just ask those of us whose tablets turned off only to turn on and be stuck at the google logo with so far zero solution for fixing it other than a hardware replacement. My tablet was at ASUS's repair factory for almost a month and had the motherboard replaced. This was after a "successful" OTA update to 5.0.1 that worked for a few days and then died. This has happened more than just infrequently to many members on here recently.
So what I would like to know is is anyone experienced the same "successful update" and then a few days later a dead tablet via factory image flashingof 5.0+. We already know that taking the OTA to 5.0+ might be a problem, and before I flash up to 5.0.2 I'd like to hear if anyone did a manual factory image flash and still had the die a few days later issue, despite not going via OTA.
Click to expand...
Click to collapse
I don't understand the obstinance regarding official LP flashing. OTA has been pulled from the shelf, lots have killed their devices with it, so it's obvious something seriously wrong is going on. I've been flashing CM and other custom roms derived from LP without problems. Why insist on incantations? This is not the first time Asus screws up with its firmwares! LP ain't nothing special that's worth it.
graphdarnell said:
I don't understand the obstinance regarding official LP flashing. OTA has been pulled from the shelf, lots have killed their devices with it, so it's obvious something seriously wrong is going on. I've been flashing CM and other custom roms derived from LP without problems. Why insist on incantations? This is not the first time Asus screws up with its firmwares! LP ain't nothing special that's worth it.
Click to expand...
Click to collapse
So you are saying LP Roms/factory images should be just fine, provided they don't go OTA? I'm sure most are, my concern is if anyone has experienced a failure hours/days after flashing to LP
Norcalz71 said:
So you are saying LP Roms/factory images should be just fine, provided they don't go OTA? I'm sure most are, my concern is if anyone has experienced a failure hours/days after flashing to LP
Click to expand...
Click to collapse
Given previous experiences with Asus JB on another model, I'd avoid anything "official" like the plague, and wait till major bugs are swatted. Clearly, I'm not saying "LP Roms/factory images should be just fine." But I've been flashing custom roms based off LP, and nothing out of the ordinary has happened. They work fine. What I don't get is people would insist on flashing the crappy OTAs Asus has been putting out in the face of so much bricking.
Asus doesn't put out updates for the N7; Google does.
Telyx said:
Asus doesn't put out updates for the N7; Google does.
Click to expand...
Click to collapse
I don't see the difference. Just because Google funded and marketed the device doesn't make it less Asus. An Asus is an Asus is an Asus, whether you buy it at Staples or in China. I seriously doubt the firmwares are 100% (or 10% for that matter) Google unless one can prove to the world otherwise.
I haven't bricked mine, and I manually updated using the 5.0.1 (and then 5.0.2) image on Google's site. However, I also have an unlocked boot loader (It was unlocked about an hour after we got it home, and hasn't been locked since) and modified /system partition. I have always manually updated the software images from fastboot.
You're saying Asus makes aosp? No. Google makes the software for nexus devices.
Asus assembled the hardware. Google makes the software (aside from proprietary drivers, of which Asus made only audio and "sensors").
Asus has very little to do with the n7 aside from the fact that they put it together.
jshamlet said:
I haven't bricked mine, and I manually updated using the 5.0.1 (and then 5.0.2) image on Google's site. However, I also have an unlocked boot loader (It was unlocked about an hour after we got it home, and hasn't been locked since) and modified /system partition. I have always manually updated the software images from fastboot.
Click to expand...
Click to collapse
Mine will remain unlocked from now on. I took it from 4.4.2 back to 4.4.4 (since after repair it was back to original and wiped) via fastboot, and will probably wait awhile longer to update it via fastboot to 5.0.2. No more OTA for me though.
Hey everyone.
I'm running on completely Stock 5.1.1 OK1 on my Note 4 and just recieved the official MM OTA update last night. Due to my phone having a lot of junk and being laggy I decided to flash the official firmware from any external method to have a clean install of the os. I heard about Samsung Kies which makes a back up of your phone and installs the latest os, I installed and backed up my phone last night but it didn't seem to give me an update on the os, it said "This is the latest version" (5.1.1 COK1).
My main concern about this is. I've bought this phone from Pakistan (used phone but in brand new condition) and I'm currently living in Malaysia and I have no idea who was the previous owner of this phone. In Kies it shows the phone number different than what I have (maybe its the Sprint phone number?).
What if my carrier is locked by having a clean install? Or any sort of other related issue occurs.
Please take some time to enlighten the facts from your knowledge, will highly appreciate it.
Regards.
waiting for official release bro. If rom is released on sammobile, see the icon kies highlighted on the right.
zincbros said:
waiting for official release bro. If rom is released on sammobile, see the icon kies highlighted on the right.
Click to expand...
Click to collapse
Yeah but you totally missed my question here.
Its not that I don't want to do some research myself, I'm a student and I'm busy most of the time. So if anyone can take out their precious time to answer my question I'd really appreciate the help.
If you're concerned about your phone or sim getting lock..you can just use galaxy tools apk v3.1.5 & then upgrade the apk to v3.1.8 & it will unlocked it for you... but i doubt it will lock you down... maybe you can just try to back your rom completely & restore if any issues encounter
it's dependent on the way that they unlocked the phone, someone in vietnam has been locked after updated the phone, but my phone was not.
zincbros said:
it's dependent on the way that they unlocked the phone, someone in vietnam has been locked after updated the phone, but my phone was not.
Click to expand...
Click to collapse
And I have no idea how my phone was unlocked, I just bought it like this. I can see the Sprint phone number on Samsung Kies maybe I should write an email to Sprint asking them to unlock it using that Sprint phone number?
My P6P (on T-Mobile) was working fine for me on the November release.
I did not sideload the December release.
With the January release, I started to notice significant radio issues.
I am seeing the same issue with the February release and after taking a look, I see that the radio has NOT changed between January and February. (But is a different radio from the November update)
I would definitely like to try flashing the November radio, but my Pixel bootloader is locked and can't be unlocked since it is still carrier locked. (I am working on that.)
In the meantime, is it possible for someone to make a custom OTA sideload package with just the November radio in it for those with locked bootloaders?
The 12L radio is different. I flashed it yesterday (12L factory image) and Signal is back to normal, and switching from Wifi to LTE/5G is much better than it's ever been on my 6 Pro. but its only been 24hours, but worth a try/
Good to know, but if I don't want to go 12L... again, could someone create a custom OTA sideload package with just the radio from 12L?
If this is even possible, which I'm dubious of, you might want to think twice. With a locked bootloader, your recovery options are more limited, so if someone creates such a custom OTA zip (again, if that's even possible to work with an unlocked bootloader), and something goes seriously wrong, it might be either more difficult or impossible to recover.
I would think (and could be completely wrong), that in the event of an issue, I'd be able to flash the original full OTA sideload package to recover.
chp said:
I would think (and could be completely wrong), that in the event of an issue, I'd be able to flash the original full OTA sideload package to recover.
Click to expand...
Click to collapse
I just wanted to add, I tried flashing a different radio in December after flashing that image before it got pulled, and my phone wouldn't boot (but my bootloader was unlocked so I was able to save it but I wouldn't try it). I suggest you unlock your bootloader and flash 12L on both slots. That's what I did yesterday. Just kind of kill 2 birds with one stone by wiping, reflashing, and using a new build/radio (3 birds I guess?)
Creating a custom OTA won't work. That will break the cert chain and the phone won't validate it and install it.
chp said:
I would think (and could be completely wrong), that in the event of an issue, I'd be able to flash the original full OTA sideload package to recover.
Click to expand...
Click to collapse
It depends on how badly things went wrong. I would hope so, too, but would be a bigger gambler than someone who has the bootloader unlocked in the same situation. But of course, if you had an unlocked bootloader, you could flash only the radio.img without any customization needed. But as @TonikJDK indicates, the question is effectively moot, anyway.
TonikJDK said:
Creating a custom OTA won't work. That will break the cert chain and the phone won't validate it and install it.
Click to expand...
Click to collapse
Interesting. I didn't realize that was in place (signing of the various components such as radio+recovery+bootloader+image), and that the checking was disabled as part of the bootloader being unlocked.
chp said:
and that the checking was disabled as part of the bootloader being unlocked.
Click to expand...
Click to collapse
I could be wrong, but to clarify, the phone still checks the OTA to make sure it's valid even with an unlocked bootloader.
No one * bothers creating a custom OTA to install their ROMs as it would be more trouble than it's worth to do it that way.
What the unlocked bootloader gets us is the ability to install things in other ways than the normal OTA process.
* Other than possibly more fully developed custom ROMs such as GrapheneOS and such might use the normal OTA method since you can re-lock the bootloader once you're on it - I have no first-hand experience with GrapheneOS other than reading their site and what other users have said about it.
roirraW edor ehT said:
I could be wrong, but to clarify, the phone still checks the OTA to make sure it's valid even with an unlocked bootloader.
No one * bothers creating a custom OTA to install their ROMs as it would be more trouble than it's worth to do it that way.
What the unlocked bootloader gets us is the ability to install things in other ways than the normal OTA process.
* Other than possibly more fully developed custom ROMs such as GrapheneOS and such might use the normal OTA method since you can re-lock the bootloader once you're on it - I have no first-hand experience with GrapheneOS other than reading their site and what other users have said about it.
Click to expand...
Click to collapse
Ah yes, you're right. I was overthinking it. The sideload OTA does have a cert, so without the private key, we wouldn't be able to create a new cert to match the custom OTA contents.
I also use T-Mobile and was always using the November radio image whilst still updating everything else to the latest release. I was in the same boat as you with the November radio image working so much better than the others. Granted, right now I'm using the 12L beta radio image as it's (thankfully) much better than the others.
But yeah, with an unlocked bootloader you can flash whichever radio image that you want - even if it's from a different release than your current Android build. It won't cause problems if you know what you're doing and only takes a few minutes. Feel free to shoot me a message once your bootloader is unlocked if you need any help with this.
NippleSauce said:
I also use T-Mobile and was always using the November radio image whilst still updating everything else to the latest release. I was in the same boat as you with the November radio image working so much better than the others. Granted, right now I'm using the 12L beta radio image as it's (thankfully) much better than the others.
But yeah, with an unlocked bootloader you can flash whichever radio image that you want - even if it's from a different release than your current Android build. It won't cause problems if you know what you're doing and only takes a few minutes. Feel free to shoot me a message once your bootloader is unlocked if you need any help with this.
Click to expand...
Click to collapse
Thanks. I've been with Android and Pixel/Nexus for a long time, and other than needing to brush up, I'm still familiar with the ins-and-outs to flashing, etc.
My Pixel 6 Pro is carrier locked, and would have to be unlocked before I could unlock the bootloader. I was just hoping to make my Pixel 6 Pro usable again without having to try to get it unlocked.
Since my radio issues started with the January update, I was hoping the February update would fix things. At first it did seem better, but then the poor behavior returned. And when I realized that the radio was unchanged in February from January, that explained things.
chp said:
My Pixel 6 Pro is carrier locked, and would have to be unlocked before I could unlock the bootloader. I was just hoping to make my Pixel 6 Pro usable again without having to try to get it unlocked.
Click to expand...
Click to collapse
I feel ya. That's partially why I started buying my phones from the company that makes them (and also because my phone carrier stopped offering any interesting upgrades after being with them for a few years lol). But supposedly, a quick text chat with a T-Mo representative via the T-Mobile app can get your device carrier unlocked via the SIM card if you're polite with the whole thing and ask the right questions. I'm not sure if anything specific needs to be asked or stated, but you could always give that a shot. I just quickly skimmed through a post from someone who did that the other day but I didn't give it too much thought since my device is factory unlocked.
But I wish you the best of luck with your phone service!