The camera won't connect anymore, Wi-Fi won't turn on and the SD card wont mount. How did this get approved by google??
Edit:
To get the OTA to work properly and flash the correct kernal, your CID must be changed to GOOGL001. If you have the GPE device, you don't need to do anything, but if you have a converted GPE then you must change your CID if you want OTA's. This was not made clear in the RUU thread, it was mentioned that changing your CID was optional if you had one of the listed CID's, but it is not optional, but a requirement if you want the OTA's to work.
Everyone that has changed there CID's reflashed the OTA and everything flashed fine, whereas anybody that had not modified there CID had the problem with the kernal.
Psosmith82 said:
The camera won't connect anymore, Wi-Fi won't turn on and the SD card wont mount. How did this get approved by google??
Click to expand...
Click to collapse
maybe you had a bad download?
HRodMusic said:
maybe you had a bad download?
Click to expand...
Click to collapse
I used the download linked from the discussion thread. Put on phone storage, rebooted into recovery and applied the update from phone storage.
Same results with OTA.
Sent from space.
Psosmith82 said:
I used the download linked from the discussion thread. Put on phone storage, rebooted into recovery and applied the update from phone storage.
Click to expand...
Click to collapse
Checked the MD5 before?
Extremer2903 said:
Checked the MD5 before?
Click to expand...
Click to collapse
Used the OTA provided by graffixnyc
Extremer2903 said:
Checked the MD5 before?
Click to expand...
Click to collapse
The signature verification wouldn't apply the update if it saw mismatches.
Archon810 said:
The signature verification wouldn't apply the update if it saw mismatches.
Click to expand...
Click to collapse
Odd.. I had no problems using the OTA zip.. Did you guys try wiping data?
graffixnyc said:
Odd.. I had no problems using the OTA zip.. Did you guys try wiping data?
Click to expand...
Click to collapse
I tried wiping data, still had the same problem. I am reflashing the RUU and will try the ota again. If it doesn't work after the 2nd try, i will just wait for google to send the OTA to me. Wiping data sucks, have to redo everything
Psosmith82 said:
The camera won't connect anymore, Wi-Fi won't turn on and the SD card wont mount. How did this get approved by google??
Click to expand...
Click to collapse
I wonder if this is also being experienced by any other users or if this is specific to your software config and/or some glitch while writing the firmware. I assume you haven't yet tried wiping your /data partition, right?
willverduzco said:
I wonder if this is also being experienced by any other users or if this is specific to your software config and/or some glitch while writing the firmware. I assume you haven't yet tried wiping your /data partition, right?
Click to expand...
Click to collapse
I wiped data and still had problems. I'm working on starting over right now
Then problem should be wiped/not wiped, I think. Anyway, trying with this error stuff is always an excited challenge with me, try to deal with it like that to reduce percentage of throwing your devices away .
Also you need to be FULLY stock.. that includes the stock kernel. If you are running a custom kernel some kernels flash libs and modules. EVERYTHING NEEDS TO BE STOCK
graffixnyc said:
Also you need to be FULLY stock.. that includes the stock kernel. If you are running a custom kernel some kernels flash libs and modules. EVERYTHING NEEDS TO BE STOCK
Click to expand...
Click to collapse
Mine is fully stock. I have an unlocked HTC one, and i flashed the GPE conversion RUU. Does the CID need to be changed to the Google CID
Psosmith82 said:
Mine is fully stock. I have an unlocked HTC one, and i flashed the GPE conversion RUU. Does the CID need to be changed to the Google CID
Click to expand...
Click to collapse
that's a really good question Psosmith
Only thing I can think of on my example is I had 'CF.lumen' installed... Other than that, I had (your) completely stock GPE conversion.
Troubleshooting...
Sent from space.
Is the problem from the update zip or ota+
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Android The Greek said:
Is the problem from the update zip or ota+
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I figured out the problem. I flashed the new RUU that graffix posted with 4.4.3. The Kernal in the OTA is not updating like it should, it stays on the kernal that was made in March. The new Kernal has a date of Thursday May 22nd. So for whatever reason, the OTA is not flashing the new Kernal, which is why all those things were broken. If you use the RUU update, it will flash the new kernal, and everything works as it should.
You'll know right off the bat at first boot. With the OTA, the boot animation hangs and it hangs on the home screen. With the RUU flash, everything is buttery smooth.
Something tells me this problem is occurring for people who actually have a retail M8 that they dirty-flashed using a GPE RUU.
Does anyone with an honest-to-God GPE that was purchased from Google have this problem? If so, this is huge.
Android The Greek said:
Is the problem from the update zip or ota+
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The update worked fine on my device and I used it for the conversion RUU. odd.. I used that very same OTA file. very odd...
Related
Hey guys, I see some of you are bricking or not being able to update.
You can use this to flash to I897UCJH7 OTA.
Use Clockwork recovery to flash it...
Cognition is currently being rebuilt on top of this, deodexed and all that fun stuff.
This flashes the system folder, kernel, and modem.
Download:
http://www.ponack.net/designgears/JH7_OTA.zip
Let me know how the GPS works for you guys!! I have gotten it to lock in my basement!!
Could you tell us what differences are in this and the JH7 we've had for a while? I assume the GPS is supposed to work better but anything aside from that?
Sent from my Samsung Captivate using Tapatalk Pro (No FC on posts like the official XDA app!)
Cheers! Thanks DG!
bts0uth said:
Could you tell us what differences are in this and the JH7 we've had for a while? I assume the GPS is supposed to work better but anything aside from that?
Sent from my Samsung Captivate using Tapatalk Pro (No FC on posts like the official XDA app!)
Click to expand...
Click to collapse
not sure of all the changes, but lots of files had different checksums..
Thanks for this dg.
Sent from my Samsung Captivate w/Voodoo using Tapatalk
Damn looks like I'm flashing for like the billionth time today.
designgears said:
not sure of all the changes, but lots of files had different checksums..
Click to expand...
Click to collapse
Awesome. Hopefully it will make Cog even better than it already is. Can't wait to try out the gps
Sent from my Samsung Captivate using Tapatalk Pro (No FC on posts like the official XDA app!)
Test.
Sent from my SAMSUNG-SGH-I897 using XDA App
Thanks DG! I've been looking for this.
Thanks so much for this!
Quick question though... if my phone already says it is at JH7 even after a 100% OTA update and had the Update Failed message, could I still flash this with Clockwork and have it function properly?
UberGoat said:
Thanks so much for this!
Quick question though... if my phone already says it is at JH7 even after a 100% OTA update and had the Update Failed message, could I still flash this with Clockwork and have it function properly?
Click to expand...
Click to collapse
sure can!!!
Tested and it works! thanks!
If I do encounter problem, I'll let you know.
Should I wipe data and clear cache prior to doing this? What are the implications of wiping my previous rom.
I am getting installation aborted from Recovery Mode. Any suggesstions?
WTF!!!!!!
do i need to uninstall lag fix first?
i forgot to uninstall lag fix. and flash this file.
now after the startup ATT and samsung logo, i just got a black/blank screen!
what do i do now?? how do i uninstall lag fix when i only getting a black/blank screen???
netnerd said:
WTF!!!!!!
do i need to uninstall lag fix first?
i forgot to uninstall lag fix. and flash this file.
now after the startup ATT and samsung logo, i just got a black/blank screen!
what do i do now?? how do i uninstall lag fix when i only getting a black/blank screen???
Click to expand...
Click to collapse
Mmm I'm not sure but... mine was stock ( did odin ) before I flashed this.
if a battery pull doesnt get it to work, then I would reflash JF6 with Odin, flash this JH7 OTA with Rom manager.
Im about to try to disable lag fix first, then flash and if it bricks it then ill flash to stock JF6 first.
Thank you DG. I needed the update because for some reason the one click installer thing wouldn't allow OTA updates. But your one click installer is still a huge help when needed.
First, breath, you are not bricked yet. Search in here for odin one click. Follow the instructions. You will most likely need to do method 3 for your download mode. (remove battery, sim, sdcard /replace battery /hil vol+ and vol- while simultaniouslyplugging in the usb cable) Once you get flashed back to stock you can try again.
Sigh after so many tries to update I went back to cognition with leaked jh7. Guess I'll be flashing again once I get off work tomorrow.
Sent from my SAMSUNG-SGH-I897 using XDA App
Stephenv1971 said:
First, breath, you are not bricked yet. Search in here for odin one click. Follow the instructions. You will most likely need to do method 3 for your download mode. (remove battery, sim, sdcard /replace battery /hil vol+ and vol- while simultaniouslyplugging in the usb cable) Once you get flashed back to stock you can try again.
Click to expand...
Click to collapse
thanks Stephenv1971 !
i almost have a heart attack! haha
just flashed back to stock rom using Odin 1 click!
I was wondering if it will be safe if you update via OTA with a custom Open script Recovery such has TWRP would be safe, I do not want to get any issues while updating to Android 4.3 when it is available like soft bricking.
andyabc said:
I was wondering if it will be safe if you update via OTA with a custom Open script Recovery such has TWRP would be safe, I do not want to get any issues while updating to Android 4.3 when it is available like soft bricking.
Click to expand...
Click to collapse
You have to be stock to get the google updates. No custom recovery at all.
zelendel said:
You have to be stock to get the google updates. No custom recovery at all.
Click to expand...
Click to collapse
Have you tested it?, I am not sure if it could be possible since TWRP is OpenScriptRecovery so the system should be able to just get the OTA update to flash like nothing is wrong or anything.
I can restore the stock recovery using the Nexus Toolkit.
Sent from my Nexus 4 using xda app-developers app
andyabc said:
Have you tested it?, I am not sure if it could be possible since TWRP is OpenScriptRecovery so the system should be able to just get the OTA update to flash like nothing is wrong or anything.
I can restore the stock recovery using the Nexus Toolkit.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
It is well known that it will not work on none official recoveries. It will also not work if you are rooted. There are threads around about this.
zelendel said:
It is well known that it will not work on none official recoveries. It will also not work if you are rooted. There are threads around about this.
Click to expand...
Click to collapse
What do you mean that it will not work if your rooted?, will it give you some error or something on the stock recovery?
Sent from my Nexus 4 using xda app-developers app
andyabc said:
What do you mean that it will not work if your rooted?, will it give you some error or something on the stock recovery?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Ok it seems it will flash but you will lose root.
http://forum.xda-developers.com/showthread.php?t=2145848
zelendel said:
Ok it seems it will flash but you will lose root.
http://forum.xda-developers.com/showthread.php?t=2145848
Click to expand...
Click to collapse
Will OTA Rootkeeper help?, I have that installed just in case there is an update has I am fully aware that the update will replace the system partition.
Sent from my Nexus 4 using xda app-developers app
andyabc said:
Will OTA Rootkeeper help?, I have that installed just in case there is an update has I am fully aware that the update will replace the system partition.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
To be honest I have no idea as I never do OTA updates. No real point.
zelendel said:
To be honest I have no idea as I never do OTA updates. No real point.
Click to expand...
Click to collapse
Ok, I found a really useful thread though: http://forums.androidcentral.com/htc-one/282447-install-ota-update-twrp-recovery.html
Looks like that stock recovery is the first thing to do.
Sent from my Nexus 4 using xda app-developers app
andyabc said:
Ok, I found a really useful thread though: http://forums.androidcentral.com/htc-one/282447-install-ota-update-twrp-recovery.html
Looks like that stock recovery is the first thing to do.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Even though that is for a different device and a completely different OTA set up. Being fully stock is always the best bet. Like I said I never do OTA and on a nexus it is almost completely pointless as the 4.3 update will be available in a flashable zip file with in a matter of hours in not less.
zelendel said:
Even though that is for a different device and a completely different OTA set up. Being fully stock is always the best bet. Like I said I never do OTA and on a nexus it is almost completely pointless as the 4.3 update will be available in a flashable zip file with in a matter of hours in not less.
Click to expand...
Click to collapse
So you can just flash the zip 100% on a custom recovery?
Sent from my Nexus 4 using xda app-developers app
andyabc said:
So you can just flash the zip 100% on a custom recovery?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yeah. Once the devs have gotten their hands on it there will be a rooted zip in a matter of hours of release that can be flashed like a normal custom rom
zelendel said:
Yeah. Once the devs have gotten their hands on it there will be a rooted zip in a matter of hours of release that can be flashed like a normal custom rom
Click to expand...
Click to collapse
Awesome, I am just going to flash the stock recovery so when the update is available the data will not get wiped.
Sent from my Nexus 4 using xda app-developers app
If your using twrp v2.5.0.0 when we get the ota update you can use it to update and it will flash it fine it will also detect that you don't have root and will ask you if you want it restored
From my BLACKED OUT N4
spaceman860 said:
If your using twrp v2.5.0.0 when we get the ota update you can use it to update and it will flash it fine it will also detect that you don't have root and will ask you if you want it restored
From my BLACKED OUT N4
Click to expand...
Click to collapse
So the OTA update would just work?, all well I have the stock recovery flashed at the moment anyway so when the OTA updates stop I will flash the recovery back and then install a custom rom with 4G and USB Host supported also having all the good tweaks like the camera tweak.
Sent from my Nexus 4 using xda app-developers app
I had CWM on my rooted Nexus 4, and the OTA for android 4.3 came along, and worked fine! Android asked to reboot to install the update, so I agreed, and the reboot loaded CWM which flashed the update. I lost root however, but it was easy to put back.
Has anyone done the OTA to 4.3 while having TWRP recovery? I wonder which of the two recoveries is better at handling OTA updates ... some folks say never attempt OTA with a custom recovery, but CWM has always handled it fine on my Nexus 4 (I've done different over-the-air updates around 3 times now).
sordna said:
Has anyone done the OTA to 4.3 while having TWRP recovery? I wonder which of the two recoveries is better at handling OTA updates ... some folks say never attempt OTA with a custom recovery, but CWM has always handled it fine on my Nexus 4 (I've done different over-the-air updates around 3 times now).
Click to expand...
Click to collapse
I am also interested about doing an update to 4.3 with everything stock except for TWRP, and am waiting to hear other people experiences before I try it. I see that the following shows one recommended method (Scenario #2), although I am not sure exactly how to do it. I am curious as to why this is any different than doing it OTA:
http://forum.xda-developers.com/show....php?t=2145848
pjc123 said:
I am also interested about doing an update to 4.3 with everything stock except for TWRP, and am waiting to hear other people experiences before I try it. I see that the following shows one recommended method (Scenario #2), although I am not sure exactly how to do it. I am curious as to why this is any different than doing it OTA:
http://forum.xda-developers.com/show....php?t=2145848
Click to expand...
Click to collapse
From what I am reading now, it's going to work. You will loose root and might loose TWRP, but if you have unlocked bootloader you can flash them both again. I'd say go ahead and let us know if you lost both root and TWRP or just root.
sordna said:
From what I am reading now, it's going to work. You will loose root and might loose TWRP, but if you have unlocked bootloader you can flash them both again. I'd say go ahead and let us know if you lost both root and TWRP or just root.
Click to expand...
Click to collapse
Actually, what I am reading now from a lot of people is that it is not necessary to download the file, and just do the OTA, as there is no difference. If I were to lose TWRP it is an easy enough process to get it back. As far as rooting, I am waiting for Koush to upgrade his superuser app, as I switched from SuperSU a while back (Both developers are having a tough time with 4.3). I am also waiting for things to settle down with all the 4.3 bugs and app upgrades. Maybe in a few weeks; there is just way too many issues.
pjc123 said:
Actually, what I am reading now from a lot of people is that it is not necessary to download the file, and just do the OTA, as there is no difference. If I were to lose TWRP it is an easy enough process to get it back. As far as rooting, I am waiting for Koush to upgrade his superuser app, as I switched from SuperSU a while back (Both developers are having a tough time with 4.3). I am also waiting for things to settle down with all the 4.3 bugs and app upgrades. Maybe in a few weeks; there is just way too many issues.
Click to expand...
Click to collapse
No need to wait, you can switch back to SuperSU, the latest version (1.51) has been working perfectly with 4.3 for me.
BTW I just installed BootUnlocker for nexus devices, a great app that can lock/unlock your boot loader from within android without wiping your data!
UPDATE: don't need anyone testing this anymore as it is not fixing most reboots
Can someone who is running custom recovery and has bad/frequent reboots install the attached file and see if it alleviates your reboots?
Please let me know what version of the OS you are running and if you are on JSS15J or JSS15Q, whether you updated via factory image or OTA.
I am 99.99% sure nothing bad will happen to your system. This will not disable your ability to get OTAs, nor change any system files, nor affect touchscreen, nor affect GPS, ...
I'm running a version of cm which has worked better than stock but still a daily reboot. What is this file going to alter / Will it work on cm?
Sent from my Nexus 7
joeshmoo said:
I'm running a version of cm which has worked better than stock but still a daily reboot. What is this file going to alter / Will it work on cm?
Click to expand...
Click to collapse
If it works, it should work ok with CM as long as you run it in TWRP.
It doesn't actually touch the ROM. It uses the kernel to reset the DDR3 memory timings and allows the system to retrain.
Thanks, I like to know what I'm flashing. Just flashed, will report back.
Sent from my Nexus 7
getting desperate and flashing this to try..
Didn't work. Just had my first reboot.
Sent from my Nexus 7 using Tapatalk 2
fkfs9 said:
Didn't work. Just had my first reboot.
Click to expand...
Click to collapse
Could you tell me what OS you are running and whether you've run an OTA before?
sfhub said:
Could you tell me what OS you are running and whether you've run an OTA before?
Click to expand...
Click to collapse
I'm on 15Q odex stock ROM. I never had an ota before.
I rooted and unlocked the boot loader and flash this ROM yesterday.
Just had a reboot on mine as well.
Running build 8 of this:
http://forum.xda-developers.com/showthread.php?t=2391779
[ROM][CM10.2][4.3][CyanogenMod FLO Kangs][DJL10.2][LINARO][Build 8][2013/08/25]
Ok, then it looks like this won't fix the random reboots.
Sorry, back to your regularly schedule program.
sfhub said:
Ok, then it looks like this won't fix the random reboots.
Sorry, back to your regularly schedule program.
Click to expand...
Click to collapse
Thanks for trying
Sent from my Nexus 7 using Tapatalk 4
joeshmoo said:
Thanks, I like to know what I'm flashing. Just flashed, will report back.
Sent from my Nexus 7
Click to expand...
Click to collapse
Don't you mean you like to know who you are flashing?
Sent from my Nexus 7 using xda app-developers app
im on clean rom with elemental x 1.2 and i have never had a reboot or anything bad happen since. i did have issues on stock 4.3 with small tweaks but since clean rom i have had no issues whatsoever
Edit also was on slim bean flo and had same issues so it's something messed up in the rom i would assume and not the software version it self
KiaraTheDragon said:
im on clean rom with elemental x 1.2 and i have never had a reboot or anything bad happen since. i did have issues on stock 4.3 with small tweaks but since clean rom i have had no issues whatsoever
Edit also was on slim bean flo and had same issues so it's something messed up in the rom i would assume and not the software version it self
Click to expand...
Click to collapse
can i flash clean rom without losing data or apps? im on modded stock rom + elementalX
I haven't had a reboot since the newest update.
Sent from my Nexus 7 using xda app-developers app
Realizing I can't unlock my bootloader via motopocalypse because its latest OTA and I can't GSM unlock it for use on US carriers. Am I stuck on stock with Verizon?
xlxcrossing said:
Realizing I can't unlock my bootloader via motopocalypse because its latest OTA and I can't GSM unlock it for use on US carriers. Am I stuck on stock with Verizon?
Click to expand...
Click to collapse
You can GSM unlock regardless of OTA version. There are a few stock-based ROMs out there for Safestrap once you root.
Sent from my XT907 using Tapatalk 4
OK I didn't have any luck with the radiocomm app and editing the nv item. I have root currently but that's it. I've never flashed a ROM without an unlocked bootloader so can you direct as to how this works as well as describing "safestrap".
xlxcrossing said:
OK I didn't have any luck with the radiocomm app and editing the nv item. I have root currently but that's it. I've never flashed a ROM without an unlocked bootloader so can you direct as to how this works as well as describing "safestrap".
Click to expand...
Click to collapse
http://blog.hash-of-codes.com/how-to-safestrap/
Thanks for the info. One question. Since virtual ROM slots use storage as would the stock system am I able to create a virtual ROM, install a custom ROM and delete the stock system?
I've used safe strap on the og RAZR and the d4... it does use the internal SD storage space... and I do not believe you can delete the stock slot nor flash anything on the stock slot... tho it may differ on this device...
Sent from my XT907 using xda app-developers app
xlxcrossing said:
Thanks for the info. One question. Since virtual ROM slots use storage as would the stock system am I able to create a virtual ROM, install a custom ROM and delete the stock system?
Click to expand...
Click to collapse
I wouldn't do that because the ROM slots depend on the stock boot.img to run. However, there is a restore procedure that should work. You can set up a slot, flash the ROM, set it up, and then back it up. Once you have it backed it up, you can restore (not flash) over your stock slot. Then you can delete the custom slot. I've never used this procedure, but I have seen quite a few people do this with success.
I see you're saying you can end up using your stock slot through this method. Basically what I want to know is if I flash a ROM on a virtual slot does my old stock ROM just sit on my sys partition without being used?
xlxcrossing said:
I see you're saying you can end up using your stock slot through this method. Basically what I want to know is if I flash a ROM on a virtual slot does my old stock ROM just sit on my sys partition without being used?
Click to expand...
Click to collapse
Yeah, supposedly you can use your stock slot. I'll post the link to the post on DroidRzr.com where it's discussed. Don't quote me on this, but I think it does sit there unused. The other slots only use its boot image. I'm pretty positive it doesn't do anything else when you boot into the safe side.
http://www.droidrzr.com/index.php/topic/11600-installing-custom-rom-to-stock-using-ss-312/
That app didn't work for me at all. Each time I installed to a ROM slot it would boot to a black screen, couldn't ever get a ROM to load. A bunch of people had the same issue. Tried reinstalling the slot multiple times before giving up. This phone has given me hell since I got it. Motorola phones are really locked down.
xlxcrossing said:
That app didn't work for me at all. Each time I installed to a ROM slot it would boot to a black screen, couldn't ever get a ROM to load. A bunch of people had the same issue. Tried reinstalling the slot multiple times before giving up. This phone has given me hell since I got it. Motorola phones are really locked down.
Click to expand...
Click to collapse
What ROMs were you trying? There are very few SS compitble ROMs out there. The app can still work for you, as far as making backups,etc.
I tried slimbean. I didn't know there was a requisite for what ROM you could flash. I'm selling the phone I'm not terribly concerned any more.
xlxcrossing said:
I tried slimbean. I didn't know there was a requisite for what ROM you could flash. I'm selling the phone I'm not terribly concerned any more.
Click to expand...
Click to collapse
Yeah, with SS you can only flash SS compatible ROMs. Slim Bean is not SS compatible. Either way, good luck with the sale.
RikRong said:
I wouldn't do that because the ROM slots depend on the stock boot.img to run. However, there is a restore procedure that should work. You can set up a slot, flash the ROM, set it up, and then back it up. Once you have it backed it up, you can restore (not flash) over your stock slot. Then you can delete the custom slot. I've never used this procedure, but I have seen quite a few people do this with success.
Click to expand...
Click to collapse
I asked about this before and couldn't get confirmation that this could be done. Suppose someone on droidrzr.com might know for sure? I want to do just as you say with a debloated stock "plus goodies" ROM and then restore over the stock slot.
HemRoyd said:
I asked about this before and couldn't get confirmation that this could be done. Suppose someone on droidrzr.com might know for sure? I want to do just as you say with a debloated stock "plus goodies" ROM and then restore over the stock slot.
Click to expand...
Click to collapse
The person that did the write up on DroidRzr did it and know other people have done it. I never did it but it makes sense that it should work. Just have utility or XML ready if something goes bad.
With a rooted, but locked bootloader, I will still be able to flash a SS rom that allows me to tether?
At this point, that and debloating are my main reasons for rooting.
I'm looking to upgrade from a Thunderbolt to a Razr M. I want to make sure I'm not trading one set of problems for a new set.
FirePsych said:
With a rooted, but locked bootloader, I will still be able to flash a SS rom that allows me to tether?
At this point, that and debloating are my main reasons for rooting.
I'm looking to upgrade from a Thunderbolt to a Razr M. I want to make sure I'm not trading one set of problems for a new set.
Click to expand...
Click to collapse
Yep. You can tether on stock actually... If you're on a share everything, you get it out of the box, otherwise you need to do a hack using sqlite editor or something
Sent from my Nexus 7 using Tapatalk 4
So which ROMs are safestrap compatabile with the locked bootloader? I am trying to help a friend with his phone unfortunately he took the ota update and his bootloader will stay locked for the moment. That said I rooted and installed safestrap so I'm looking to install a compatible ROM and get this phone on straight talk with a ST SIM card. Any suggestions?
Sent from my XT875 using XDA Premium 4 mobile app
Just FYI: https://forums.oneplus.net/threads/cm-11s-44s-ota-is-out.173057/
...didn't see the typical insta-thread here, heh.
Greetings friends,
Happy Weekend! Thanks to our buds at Cyanogen, a new OTA will be rolling out to your phones starting today. This new release includes some new fixes such as a resolved SSLv3 POODLE security issue and updated touchscreen firmware.
The OTA will be released slowly and therefore some regions might receive it before others. Once you’ve received your OTA please let us know what you think! Any further issues you may find can also be reported directly to Cyanogen.
Here’s a comprehensive list of changes you’ll find in this update:
Fixed issues with memory causing screen artifacts
Fixed issues with random reboots and instability
Fixed issues with WiFi and modem crashes
Fixed issues with Filesystem
Fixed issues with “black bar”
Fixed issues with persist partition corruption
Fixed issues with AT&T VoLTE
Click to expand...
Click to collapse
Edit: Forgot to mention... this includes a new modem, I know people are always interested in that.
As a side note, I've been running the build as part of an early access test for a few days now... has been extremely solid for me.
Edit again: LINKS!
• Link to the OTA: http://builds.cyngn.com/fota/incremental/bacon/cm-bacon-ac1ccf7921-to-5fa8c79c0b-signed.zip
MD5: 684bc3eb256f06a912505628551cba24
Super mini guide: As long as your system is stock, flash away in stock or custom recovery. I always re-flash the SuperSU zip immediately following, YMMV.
• Link to the OTA with a modified script (by @gianton) for installing regardless of system changes: https://mega.co.nz/#!EdBQ1Y4C!P85kyvVp1iR_I4IiuLKPxGBqskE3fueWe0OGAFidGEg
MD5: 3b5729b07200c0e53a02f6b1225fc79c
FAQ (since people are allergic to reading and searching):
1. ZOMG WHY NO WIFI AFTER OTA?: Because you used a custom kernel and didn't clean up your system files properly. Either follow that kernel threads instructions for OTA-prep'ing or flash back to that kernel.
2. I don't run CM 11S but I can totally flash this CM11S update, right?: No. If you want to flash the 44S OTA update, get yourself to CM11S 38R.
Zip file?
Inviato dal mio OnePlus One
Lolli......Oh wait <.< (Joke post)
Should have grab the zip.
hunter0389 said:
Should have grab the zip.
Click to expand...
Click to collapse
I did, but... as someone that hasn't tested for CM before, I'm not entirely clear on their position of a tester sharing. I wouldn't want to piss anyone off unnecessarily.
dmarden said:
I did, but... as someone that hasn't tested for CM before, I'm not entirely clear on their position of a tester sharing. I wouldn't want to piss anyone off unnecessarily.
Click to expand...
Click to collapse
I understand. Since the OTA is out, would you mind sharing the zip?
Got this link off Android Police article....
http://builds.cyngn.com/fota/incremental/bacon/cm-bacon-ac1ccf7921-to-5fa8c79c0b-signed.zip
blkhwkz said:
Got this link off Android Police article....
http://builds.cyngn.com/fota/incremental/bacon/cm-bacon-ac1ccf7921-to-5fa8c79c0b-signed.zip
Click to expand...
Click to collapse
Great, that makes me feel much better about posting it. I added your link to the OP.
If I update this new build will it break my root ?
vikramdhani said:
If I update this new build will it break my root ?
Click to expand...
Click to collapse
Not in any meaningful way. Just have the SuperSU zip on your phone and flash it after you flash the OTA.
going to be constantly refreshing for OTA. Currently on stock, unrooted, and planning on leaving it that way for now, can the zip be flashed in stock recovery?
dmarden said:
Great, that makes me feel much better about posting it. I added your link to the OP.
Click to expand...
Click to collapse
can i install with twrp?
zipper for TWRP?
mobbarley said:
going to be constantly refreshing for OTA. Currently on stock, unrooted, and planning on leaving it that way for now, can the zip be flashed in stock recovery?
Click to expand...
Click to collapse
I flashed it in TWRP, so I assume stock recovery is also fine.
nicola1989 said:
can i install with twrp?
Click to expand...
Click to collapse
Yes.
mittimus said:
zipper for TWRP?
Click to expand...
Click to collapse
The one in the OP is identical to the one I received as a tester and I flashed it in TWRP.
How do I keep root?
Sent from my A0001 using XDA Free mobile app
Crinkypops said:
How do I keep root?
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
I just keep the SuperSU zip on my phone and flash it immediately after the OTA whenever they come out.
dmarden said:
I just keep the SuperSU zip on my phone and flash it immediately after the OTA whenever they come out.
Click to expand...
Click to collapse
Perfect. Flashing now through TWRP.
Sent from my A0001 using XDA Free mobile app
mobbarley said:
going to be constantly refreshing for OTA. Currently on stock, unrooted, and planning on leaving it that way for now, can the zip be flashed in stock recovery?
Click to expand...
Click to collapse
If it contains "signed" it is flashable by stock too
Flashing the ZIP from AP did not work....going to reboot and try again.
reinert012 said:
Flashing the ZIP from AP did not work....going to reboot and try again.
Click to expand...
Click to collapse
Please also elaborate on "did not work" if it fails again... it's identical to the test build ZIP I received which flashed fine. Did you make any system modifications (if so, those will need to be reverted probably)?