Related
So basically I have my nexus 5 and it’s completely stocked. I don’t want to root or do anything that could prevent me from receiving OTA updates?
What are the steps to update my phone rom stock 4.4 to 4.4.1.
Thanks
I found this video very helpful.
http://www.youtube.com/watch?v=rfZ4f5Bdgfc&list=FLJJ5N1JCwlum5OdXVTemjHw&index=2
richport29 said:
I found this video very helpful.
http://www.youtube.com/watch?v=rfZ4f5Bdgfc&list=FLJJ5N1JCwlum5OdXVTemjHw&index=2
Click to expand...
Click to collapse
I have a nexus 5.
rayoubi said:
I have a nexus 5.
Click to expand...
Click to collapse
Exact same process.
---------- Post added at 06:05 PM ---------- Previous post was at 06:04 PM ----------
Obviously use the Nexus 5 4.1.1 ota
Be patient and receive the update directly from Google as an OTA within a week, or so. There might need to be a revision to this update, due to issues with the new radio seeming to not get good signal strength and so forth, which is why Goofle sends it out incrementally.
Sent from my Nexus 5 using Tapatalk
F n a I've never seen so many dopes in a row
http://forum.xda-developers.com/showthread.php?p=47369234
jd1639 said:
F n a I've never seen so many dopes in a row
http://forum.xda-developers.com/showthread.php?p=47369234
Click to expand...
Click to collapse
People need to search first, but that guide doesn't work for everyone.
My phone wouldn't reboot into actual recovery...it came up saying "No error" or some nonsense and wouldn't get into recovery. It makes the guide useless.
hotleadsingerguy said:
People need to search first, but that guide doesn't work for everyone.
My phone wouldn't reboot into actual recovery...it came up saying "No error" or some nonsense and wouldn't get into recovery. It makes the guide useless.
Click to expand...
Click to collapse
The guide is not useless. If you can't boot into recovery you're doing something wrong or your recovery is borked. If its borked you can fix it.
jd1639 said:
The guide is not useless. If you can't boot into recovery you're doing something wrong or your recovery is borked. If its borked you can fix it.
Click to expand...
Click to collapse
Oh, I didn't realize the guide explained how to fix it if something happened to your recovery. If so, I redact my statement.
(Obviously that's sarcasm and I don't redact my statement, since it doesn't do that)
My phone is completely bone-stock. I haven't rooted or unlocked. It doesn't boot into recovery using the method listed in the guide, and booting into the system menu and selecting Recovery just boots the phone normally for me.
hotleadsingerguy said:
Oh, I didn't realize the guide explained how to fix it if something happened to your recovery. If so, I redact my statement.
(Obviously that's sarcasm and I don't redact my statement, since it doesn't do that)
My phone is completely bone-stock. I haven't rooted or unlocked. It doesn't boot into recovery using the method listed in the guide, and booting into the system menu and selecting Recovery just boots the phone normally for me.
Click to expand...
Click to collapse
Then your recovery is broken. Look at the how to flash factory images sticky in General and fastboot flash a fixed recovery.
Nothing to do with the fact that this is another OTA thread when there is an OTA sticky. The guide is not useless, your phone is.
rootSU said:
Then your recovery is broken. Look at the how to flash factory images sticky in General and fastboot flash a fixed recovery.
Nothing to do with the fact that this is another OTA thread when there is an OTA sticky. The guide is not useless, your phone is.
Click to expand...
Click to collapse
And, as I mentioned, I haven't modified a thing on the phone. If my recovery is broken, it was broken from the factory.
And, again, the guide had nothing to do with that. If anyone else has the issue (which people are having, according to a few other topics I've seen), the guide makes no account for it -- for anyone with the issue, the guide is of no help.
hotleadsingerguy said:
And, as I mentioned, I haven't modified a thing on the phone. If my recovery is broken, it was broken from the factory.
Click to expand...
Click to collapse
I never said it was anything to do with what you had done or when it had broken.
hotleadsingerguy said:
And, again, the guide had nothing to do with that. If anyone else has the issue (which people are having, according to a few other topics I've seen), the guide makes no account for it -- for anyone with the issue, the guide is of no help.
Click to expand...
Click to collapse
And why would it? It also doesn't help people with a smashed screen or broken volume buttons. The guide is a guide to do what needs to be done on a fully working phone. It does NOT need to cover every fault that someone might have that prevents them doing the things in the guide. The fact your phone is broken bears no relevance to the usefulness of the guide. Besides, I already advised you what you could try to fix it.
Anyway, this thread is a duplicate and I have requested it be closed.
hotleadsingerguy said:
Oh, I didn't realize the guide explained how to fix it if something happened to your recovery. If so, I redact my statement.
(Obviously that's sarcasm and I don't redact my statement, since it doesn't do that)
My phone is completely bone-stock. I haven't rooted or unlocked. It doesn't boot into recovery using the method listed in the guide, and booting into the system menu and selecting Recovery just boots the phone normally for me.
Click to expand...
Click to collapse
hi
i am a noob. my phone is also compleely stock. not rooted and locked. i just activated with my carrier and downloaded speedtest. thats it. i have android sdk and platform tools and universal naked driver with adb support installed on my pc.
Code:
adb boot recovery
takes me to recovery. and i side loaded from there. :good:
:crying:
Hello there!
I have a really serious problem with my TF300T. I had the newest bootloader installed with 4.4 enabled TWRP recovery. I had the 2014.01.07. CM 11 nightly installed and was running fine. I have seen, that there are some never releases so decided to update. I downloaded the newest nightly yesterday and pressed power button. Selected reboot and then selected Recovery.
And here comes the problem!
The tablet bricked himself! It did restart but got into a bootloop I cannot get through the Asus splashscreen. I tried POWER+VOLD DOWN, I cannot get into fastboot or recovery. The tablet keep rebooting, no boot to android either. I tried power off, no success. I tried the reset button. I removed battery, still the same.
As I have never done anything to the bootloader, I did not consider making NVFLASH backup, as it is a risky operation. Shame on me...
How could it happen????? Does cyanogenmod alter Bootloader partition to reboot into recovery??? What the hell??
Please help me somehow! I dont know what to do, I tried all I could! Maybe APX? or only Asus RMA??
yours,
dpeti said:
:crying:
Hello there!
I have a really serious problem with my TF300T. I had the newest bootloader installed with 4.4 enabled TWRP recovery. I had the 2014.01.07. CM 11 nightly installed and was running fine. I have seen, that there are some never releases so decided to update. I downloaded the newest nightly yesterday and pressed power button. Selected reboot and then selected Recovery.
And here comes the problem!
The tablet bricked himself! It did restart but got into a bootloop I cannot get through the Asus splashscreen. I tried POWER+VOLD DOWN, I cannot get into fastboot or recovery. The tablet keep rebooting, no boot to android either. I tried power off, no success. I tried the reset button. I removed battery, still the same.
As I have never done anything to the bootloader, I did not consider making NVFLASH backup, as it is a risky operation. Shame on me...
How could it happen????? Does cyanogenmod alter Bootloader partition to reboot into recovery??? What the hell??
Please help me somehow! I dont know what to do, I tried all I could! Maybe APX? or only Asus RMA??
yours,
Click to expand...
Click to collapse
No, sorry, you won't be able to use APX mode without have making the NvFlash backups beforehand.
is this possible? I'm now afraid to update to newer cm11 versions...
aplopeanu said:
is this possible? I'm now afraid to update to newer cm11 versions...
Click to expand...
Click to collapse
Yeah, Ive seen it happen to multiple people across the forums idk what the actual bug is though.
cmendonc2 said:
Yeah, Ive seen it happen to multiple people across the forums idk what the actual bug is though.
Click to expand...
Click to collapse
so basically ... don't update CM11 until this is fixed right?
aplopeanu said:
so basically ... don't update CM11 until this is fixed right?
Click to expand...
Click to collapse
Im not sure It only happened to a few people in addition to OP of this thread. Im not upgrading to be safe, but maybe the dev should look into it.
cmendonc2 said:
Im not sure It only happened to a few people in addition to OP of this thread. Im not upgrading to be safe, but maybe the dev should look into it.
Click to expand...
Click to collapse
Yea I'm doing the same thing...btw if you birck it...changing the motherboard will unbrick it?
aplopeanu said:
Yea I'm doing the same thing...btw if you birck it...changing the motherboard will unbrick it?
Click to expand...
Click to collapse
In theory, yes. But many people consider it easier to RMA it.
cmendonc2 said:
In theory, yes. But many people consider it easier to RMA it.
Click to expand...
Click to collapse
RMA?
aplopeanu said:
RMA?
Click to expand...
Click to collapse
Send it back to Asus and pay the repair costs.
Hello everyone. I'm beginning to have a few system problems, (their leader being an overheating system). I'm likely going to have to return the device to Verizon. If so, I'll need to return to stock ROM. I'm running 4.3 OTA and have already hardbricked the device once. I know that with the 4.3 OTA update, flashing options have been restricted. I currently can't put phone in recovery mode. I trip the flash counter and get a message about unauthorized firmware being detected.
That being said, given my situation, is there any tried and true method to return the phone to the original out of the box status?
Thank you in advance for your time and knowledge.
TwistedPoet said:
Hello everyone. I'm beginning to have a few system problems, (their leader being an overheating system). I'm likely going to have to return the device to Verizon. If so, I'll need to return to stock ROM. I'm running 4.3 OTA and have already hardbricked the device once. I know that with the 4.3 OTA update, flashing options have been restricted. I currently can't put phone in recovery mode. I trip the flash counter and get a message about unauthorized firmware being detected.
That being said, given my situation, is there any tried and true method to return the phone to the original out of the box status?
Thank you in advance for your time and knowledge.
Click to expand...
Click to collapse
Probably you need to pick the hard brick option, but I give you both:
SOFT BRICK - able to get to download mode
http://forum.xda-developers.com/showthread.php?t=2586319
------------------------------
HARD BRICK - phone not turn on
http://forum.xda-developers.com/showthread.php?t=2581166
buhohitr said:
Probably you need to pick the hard brick option, but I give you both:
SOFT BRICK - able to get to download mode
http://forum.xda-developers.com/showthread.php?t=2586319
------------------------------
HARD BRICK - phone not turn on
http://forum.xda-developers.com/showthread.php?t=2581166
Click to expand...
Click to collapse
I had previously neglected to even attempt to upload the recovery.img. (Huge Oversight). However, I ran it successfully (at least I thought), rebooted the phone into recovery mode and still received same yellow triangle error message.
TwistedPoet said:
I had previously neglected to even attempt to upload the recovery.img. (Huge Oversight). However, I ran it successfully (at least I thought), rebooted the phone into recovery mode and still received same yellow triangle error message.
Click to expand...
Click to collapse
Now if you able to boot into recovery you need to follow the exact steps here:
SOFT BRICK - able to get to download mode
http://forum.xda-developers.com/show....php?t=2586319
Just flash recovery will not fix the issue.
buhohitr said:
Now if you able to boot into recovery you need to follow the exact steps here:
SOFT BRICK - able to get to download mode
http://forum.xda-developers.com/show....php?t=2586319
Just flash recovery will not fix the issue.
Click to expand...
Click to collapse
http://forum.xda-developers.com/show....php?t=2586319 - (Dead Link....404 Error)
Please pardon my ignorance but those instructions don't appear to be helpful for restoring the ability to turn the phone on in recovery mode or for getting the phone back to 4.1.2 firmware. Again, please forgive my inability to grasp this.
TwistedPoet said:
http://forum.xda-developers.com/show....php?t=2586319 - (Dead Link....404 Error)
Please pardon my ignorance but those instructions don't appear to be helpful for restoring the ability to turn the phone on in recovery mode or for getting the phone back to 4.1.2 firmware. Again, please forgive my inability to grasp this.
Click to expand...
Click to collapse
That's because there's no way to go back, you are stuck on the 4.3 update.
All you can run is stock 4.3 firmware. It's literally posted everywhere in these forums, and if you searched first you would have found all the answers you needed before you started flashing things that will brick your phone.
This is what you have to do to get a functioning phone again:
http://forum.xda-developers.com/showthread.php?t=2586319
After that, read everything here to understand what you're limited to and what can be safely flashed to the 4.3 update:
http://forum.xda-developers.com/showthread.php?t=2639337
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
That's because there's no way to go back, you are stuck on the 4.3 update.
All you can run is stock 4.3 firmware. It's literally posted everywhere in these forums, and if you searched first you would have found all the answers you needed before you started flashing things that will brick your phone.
This is what you have to do to get a functioning phone again:
http://forum.xda-developers.com/showthread.php?t=2586319
After that, read everything here to understand what you're limited to and what can be safely flashed to the 4.3 update:
http://forum.xda-developers.com/showthread.php?t=2639337
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for that but the title of my post should have indicated that I have done some significant searching. I've already restored the phone to working condition. It was the EZ Unlocker that bricked me. I did neglect in my joy of returning my phone from the dead to flash the recovery.img. I flashed it today and am still unable to get recovery mode. I'm following the SoftBrick guide that buhohitr posted and I'm hoping that I don't find myself in a bootloop afterwards. The second link you provided is very thorough and informative. I bookmarked it for future reference.
At last I got to know lot of things from this thread as I'm new to this trade.
TwistedPoet said:
Thanks for that but the title of my post should have indicated that I have done some significant searching. I've already restored the phone to working condition. It was the EZ Unlocker that bricked me. I did neglect in my joy of returning my phone from the dead to flash the recovery.img. I flashed it today and am still unable to get recovery mode. I'm following the SoftBrick guide that buhohitr posted and I'm hoping that I don't find myself in a bootloop afterwards. The second link you provided is very thorough and informative. I bookmarked it for future reference.
Click to expand...
Click to collapse
Update - With some very helpful guides and a little but of explanation, I was able to return to stock ROM, which returned my ability to boot into recovery mode. I also successfully flashed Safe strap Recovery onto my device. After looking at the guide about which custom ROM's can be flashed onto the phone, I'm considering using one but I am a tad hesitant. I know very very little about framework, kernels and modules. So, I guess we'll see. Thanks for the simply excellent links and your time!!!!!
Hello all. So need help getting my bearing straight with my TF300T. Mother's tablet I just have it modded for ease of use and now I am lost since it has been awhile.
Tablet is running CM 10.2 with TWRP 2.5.0.0. I don't know what the bootloader is currently on the device. The device is also not being recognized by my computer. I would like to backup her files and get it on CM 11 M5.
I am guessing I need to first figure out what bootloader i am on correct? How do i go about doing this? Next step is to upgrade to TWRP 2.7.0.0 correct and then system wipe and flash CM11? If somebody could either help me out with directions or point me in the right direction it would be great. Extremely familiar with the Samsung scene and just haven't touched this tablet in god knows how long.
Ok so turned off USB debugging and now can see the tablet on the computer. Now how do i go about finding out about the bootloader and updating it.
Edit found that is is US_epad-10.6.1.27.5-20130902
Now I'm a little lost again. http://forum.xda-developers.com/showthread.php?p=49258989 doesn't have the bootloader I mentioned above. Not sure what the safest way to proceed is.
Aali1011 said:
Now I'm a little lost again. http://forum.xda-developers.com/showthread.php?p=49258989 doesn't have the bootloader I mentioned above. Not sure what the safest way to proceed is.
Click to expand...
Click to collapse
You will need to install TWRP 2.7.0.0 to continue. I wrote a guide here: http://forum.xda-developers.com/showpost.php?p=48508679&postcount=7
cmendonc2 said:
You will need to install TWRP 2.7.0.0 to continue. I wrote a guide here: http://forum.xda-developers.com/showpost.php?p=48508679&postcount=7
Click to expand...
Click to collapse
WOW dude my bad. Can't believe I skipped over the first line in that thread and didn't proceed forward. MY GS3 is giving me "insufficient storage space" issues so android overload right now.
Now stupid question i am on a unlocked bootloader aren't I since i am running a custom rom and what not?
Aali1011 said:
WOW dude my bad. Can't believe I skipped over the first line in that thread and didn't proceed forward. MY GS3 is giving me "insufficient storage space" issues so android overload right now.
Now stupid question i am on a unlocked bootloader aren't I since i am running a custom rom and what not?
Click to expand...
Click to collapse
Yes, your bootloader is unlocked. You can flash the new TWRP from your old one.
cmendonc2 said:
Yes, your bootloader is unlocked. You can flash the new TWRP from your old one.
Click to expand...
Click to collapse
Hmmm go figure. Wonder how I managed to do that when the Asus app was giving me all sorts of issues Thank you for the clarification though. I was lost for a good while.
Hello guys. I have a Galaxy S3 (Verizon). Specifically, a SCH-I535. It is running Android 4.3. It has been rooted before, when it had 4.2, but after I did the update, I still have the SU app, but I can't use it because im not rooted. (I think) So hypothetically, say I wanted to install CyanogenMod. Could I? If so, what version? I have Android 4.3. Is it still possible to root? Thanks for any help.
bio4554 said:
Hello guys. I have a Galaxy S3 (Verizon). Specifically, a SCH-I535. It is running Android 4.3. It has been rooted before, when it had 4.2, but after I did the update, I still have the SU app, but I can't use it because im not rooted. (I think) So hypothetically, say I wanted to install CyanogenMod. Could I? If so, what version? I have Android 4.3. Is it still possible to root? Thanks for any help.
Click to expand...
Click to collapse
You can root 4.3 using saferoot, but you cannot flash CyanogenMod or any other AOSP based ROMs. You can only flash 4.3 Touchwiz ROMs using safestrap. You need to be on the ML1 version of 4.3, not the NC1 version. Everything you need to know can be found in the below linked thread:
http://forum.xda-developers.com/showthread.php?t=2639337
landshark68 said:
You can root 4.3 using saferoot, but you cannot flash CyanogenMod or any other AOSP based ROMs. You can only flash 4.3 Touchwiz ROMs using safestrap. You need to be on the ML1 version of 4.3, not the NC1 version. Everything you need to know can be found in the below linked thread:
http://forum.xda-developers.com/showthread.php?t=2639337
Click to expand...
Click to collapse
\
Ok so my next question, how do I tell if I have NC1, or ML1? Also, will this void my warranty? It says Saferoot will not. Sorry, im such a noob.
bio4554 said:
\
Ok so my next question, how do I tell if I have NC1, or ML1? Also, will this void my warranty? It says Saferoot will not. Sorry, im such a noob.
Click to expand...
Click to collapse
Go to your about phone screen and look at your baseband version and build number and see what the last 3 characters are. And your warranty is only good for 1 year from the original date of purchase, which I would assume has long since passed. So I wouldn't worry about this voiding your warranty.
landshark68 said:
Go to your about phone screen and look at your baseband version and build number and see what the last 3 characters are. And your warranty is only good for 1 year from the original date of purchase, which I would assume has long since passed. So I wouldn't worry about this voiding your warranty.
Click to expand...
Click to collapse
Ok thanks so much! I have rooted my phone after flashing ML1, and now I was wondering if I could install CWM Recovery? If so, how? Thanks for all the help.
bio4554 said:
Ok thanks so much! I have rooted my phone after flashing ML1, and now I was wondering if I could install CWM Recovery? If so, how? Thanks for all the help.
Click to expand...
Click to collapse
Check out my first response to you in this thread. You cannot install any kind of custom recovery on ML1. Safestrap is basically your custom recovery. Click on the link in my first response and read up. In the thread I linked you will find a link about Safestrap and a bunch of information you will need.
landshark68 said:
Check out my first response to you in this thread. You cannot install any kind of custom recovery on ML1. Safestrap is basically your custom recovery. Click on the link in my first response and read up. In the thread I linked you will find a link about Safestrap and a bunch of information you will need.
Click to expand...
Click to collapse
Ok, so basically I installed Safestrap, Rooted, and all was well. Then I went and looked for some custom Touchwiz ROMs, and found this one.
CoolROM 8 Core Edition
I downloaded it, created a new ROM slot on Safestrap, flashed it to the phone with safestrap, then rebooted. First off, the Samsung logo that appears right when you turn on, with the open padlock, is gone. For a split second, a white line appears. Then it goes to the Safestrap, I hit continue, it does first boot like normal, and gets stuck on the samsung logo again. "The last one before android appears". I pulled battery, rebooted. Same as first time, except it booted into android. The setup appears, and now another problem pops up. I cant turn on WiFi. It says turned off, I press the toggle button, but it doesnt turn to the ON state. Please help! I really want to use CleanROM!
bio4554 said:
Ok, so basically I installed Safestrap, Rooted, and all was well. Then I went and looked for some custom Touchwiz ROMs, and found this one.
CoolROM 8 Core Edition
I downloaded it, created a new ROM slot on Safestrap, flashed it to the phone with safestrap, then rebooted. First off, the Samsung logo that appears right when you turn on, with the open padlock, is gone. For a split second, a white line appears. Then it goes to the Safestrap, I hit continue, it does first boot like normal, and gets stuck on the samsung logo again. "The last one before android appears". I pulled battery, rebooted. Same as first time, except it booted into android. The setup appears, and now another problem pops up. I cant turn on WiFi. It says turned off, I press the toggle button, but it doesnt turn to the ON state. Please help! I really want to use CleanROM!
Click to expand...
Click to collapse
Look in the OP of the safestrap thread. Every time you flash a ROM though safestrap you have to also flash the kernel modules in the same flashing session in order for WiFi to work.
landshark68 said:
Look in the OP of the safestrap thread. Every time you flash a ROM though safestrap you have to also flash the kernel modules in the same flashing session in order for WiFi to work.
Click to expand...
Click to collapse
Omg thank you so much landshark,you have helped me so much. I now have a rooted S3 with Safestrap, and CleanROM 8.1. Everything is working fine. Now my final question(probably not), is there any possible way at all to unlock the bootloader on this thing? If not, is there anyone working on something like that? If not at all, that's ok. Im still satisfied with it so far. Thanks again. Also, on Safestrap, after I hit continue it has a kind of delay before the boot animation is shown(AKA it starts up). Is there any way to change this?
bio4554 said:
Omg thank you so much landshark,you have helped me so much. I now have a rooted S3 with Safestrap, and CleanROM 8.1. Everything is working fine. Now my final question(probably not), is there any possible way at all to unlock the bootloader on this thing? If not, is there anyone working on something like that? If not at all, that's ok. Im still satisfied with it so far. Thanks again. Also, on Safestrap, after I hit continue it has a kind of delay before the boot animation is shown(AKA it starts up). Is there any way to change this?
Click to expand...
Click to collapse
Not possible at all to unlock the bootloader, you are stuck with it. As far as I know, no one is working on trying to figure out a way to unlock the bootloader. All attempts at finding an exploit to unlock the bootloader have not had any success. The bootloader on the S4 was locked down in the same way before the S3, and that hasn't been cracked yet either.
As far as changing the delay on start up with safestrap, best to ask that question in the safestrap thread as I have never used safestrap and just read the thread to stay informed.