Related
Hi I have just recently unrooted my phone and back to stock with stock boothloader and recovery.
I did this because I am just patiently
Waiting for the ICS update.
My questing is...how do I lock the OEM on my phone? I know you could but I want to know how. And ....if I do that....WOULD IT WIPE MY PHONE?
I want to relock my OEM, but keep all my apps on my phone.
So again, if I lock my OEM, would it wipe my phone?
PS. I have 19020A
Sent from my Nexus S using XDA App
Don't think it wipes ur phone... maybe I'm wrong but here ya go
>Fastboot Device
>Fastboot OEM Lock
Sent from my Nexus S using xda premium
Yup it will wipe everything
Sent from my HTC Sensation 4G using XDA App
mathkid95 said:
Yup it will wipe everything
Sent from my HTC Sensation 4G using XDA App
Click to expand...
Click to collapse
fastboot oem lock
Locking doesn't wipe anything. Unlocking wipes.
Sent from my Nexus S using xda premium
You don't have to lock bootloader to recieve OTA updates, unlocked bootloader just allows you to flash something via fastboot (usually CWM). Just be unrooted and have stock recovery, as I do. This way you can always flash CWM, make a nandroid backup and flash someting else...without losing any data (you don't unlock bootloader).
Ahhh damnit. Thanks krohn, had a bit of a brain freeze there.
Sent from my HTC Sensation 4G using XDA App
dan542 said:
You don't have to lock bootloader to recieve OTA updates, unlocked bootloader just allows you to flash something via fastboot (usually CWM). Just be unrooted and have stock recovery, as I do. This way you can always flash CWM, make a nandroid backup and flash someting else...without losing any data (you don't unlock bootloader).
Click to expand...
Click to collapse
Yea, why lock the bootloader? It doesn't need to be.
I thought locking the bootloader DID wipe. I guess I myself am mistaken too. (It would tell you though when you go to do it.).
Lastly, don't you think it's a little earlier to be going back to stock for the ICS update when it's not even announced as far as it being done and the phone; nor, is it announced of when the phone itself will be coming out. And, it won't be sometime till after that as well.
Just my opinion.
(You also didn't need to go unroot if you were stock rooted with no modifications).
Its just that I have lots of apps and I want to have them for when ICS comes out.
And....idk....I just figures if I am not rooted I might-as-well OEM lock just invade..if I might need to...for warenty
Sent from my Nexus S using XDA App
Nah your good on that... while it's rooted and awaiting the OTA... give your phone some Cyber air... over clock it with an app... install a better radio.. do something =]
Sent from my Nexus S using xda premium
BlackHawkA4 said:
Yea, why lock the bootloader? It doesn't need to be.
I thought locking the bootloader DID wipe. I guess I myself am mistaken too. (It would tell you though when you go to do it.).
Lastly, don't you think it's a little earlier to be going back to stock for the ICS update when it's not even announced as far as it being done and the phone; nor, is it announced of when the phone itself will be coming out. And, it won't be sometime till after that as well.
Just my opinion.
(You also didn't need to go unroot if you were stock rooted with no modifications).
Click to expand...
Click to collapse
Yes, you can be rooted, but you'll have to have stock recovery and you'll lose root with OTA update.
Sent from my Nexus S using XDA App
dan542 said:
Yes, you can be rooted, but you'll have to have stock recovery and you'll lose root with OTA update.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
You don't need stock recovery. Stock recovery is not checked with an assert and is not patched, it is deleted and flashed using a full image. You can flash the OTA with CWM without any issues.
You will lose root in one of two scenarios with the OTAs, it recursively chmod's /system or formats /system (full update, not incremental). At this point all you need to do it flash the su binary again though to regain root access.
krohnjw said:
You don't need stock recovery. Stock recovery is not checked with an assert and is not patched, it is deleted and flashed using a full image. You can flash the OTA with CWM without any issues.
You will lose root in one of two scenarios with the OTAs, it recursively chmod's /system or formats /system (full update, not incremental). At this point all you need to do it flash the su binary again though to regain root access.
Click to expand...
Click to collapse
Ok
Sent from my Nexus S using XDA App
Looks like I might have corrupted the cache. How do I go about fixing this?
Fastboot flash the stock cache image
Sent from my Nexus 5 using Tapatalk
rootSU said:
Fastboot flash the stock cache image
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
My device is locked. Is there a way to do it without losing data?
Never mind. It somehow fixed itself.
After I upgrade to Lollipop 5.1, my T-Mobile SIM card cannot be recognized, and called Google Support, they can only recommend me to do a factory reset, which I don't want to do it until I can have my stuff backup.
Any thoughts what else I can try?
yakuzu said:
After I upgrade to Lollipop 5.1, my T-Mobile SIM card cannot be recognized, and called Google Support, they can only recommend me to do a factory reset, which I don't want to do it until I can have my stuff backup.
Any thoughts what else I can try?
Click to expand...
Click to collapse
1. try a friend's/family members SIM and see if it works in your device
2. try putting your SIM in a friend's/family member's phone
Elluel said:
1. try a friend's/family members SIM and see if it works in your device
2. try putting your SIM in a friend's/family member's phone
Click to expand...
Click to collapse
Yeah, it can recognize.
After the Lollipop upgrade, my baseband also said "unknown"
What should I do now?
yakuzu said:
Yeah, it can recognize.
After the Lollipop upgrade, my baseband also said "unknown"
What should I do now?
Click to expand...
Click to collapse
Wipe cache and then flash radio.img using fastboot while in the bootloader
Elluel said:
Wipe cache and then flash radio.img using fastboot while in the bootloader
Click to expand...
Click to collapse
hhmmm.. I did that too, maybe except wipe cache.
how do i wipe cache? this is a unrooted device and prefer not to root it.
yakuzu said:
hhmmm.. I did that too, maybe except wipe cache.
how do i wipe cache? this is a unrooted device and prefer not to root it.
Click to expand...
Click to collapse
Root access only applies within Android (irrelevant in bootloader and recovery).
You can flash cache.img or wipe it in recovery.
Elluel said:
Root access only applies within Android (irrelevant in bootloader and recovery).
You can flash cache.img or wipe it in recovery.
Click to expand...
Click to collapse
I download the .tgz from Google https://dl.google.com/dl/android/aosp/hammerhead-lmy47d-factory-6c1ad81e.tgz
I don't see any cache.img
Also don't have recovery installed.
yakuzu said:
I download the .tgz from Google https://dl.google.com/dl/android/aosp/hammerhead-lmy47d-factory-6c1ad81e.tgz
I don't see any cache.img
Also don't have recovery installed.
Click to expand...
Click to collapse
Extract that file.
You can wipe cache in stock recovery. You do have a recovery.
Elluel said:
Extract that file.
You can wipe cache in stock recovery. You do have a recovery.
Click to expand...
Click to collapse
Thanks!
What else do I need to load other than cache.img? I prefer not to lose all my user data (please no factory reset)
bootloader-hammerhead-hhz12f.img flash-all.sh* image-hammerhead-lmy47d.zip
flash-all.bat flash-base.sh* radio-hammerhead-m8974a-2.0.50.2.25.img
Archive: image-hammerhead-lmy47d.zip
inflating: android-info.txt
inflating: cache.img
inflating: boot.img
inflating: recovery.img
inflating: userdata.img
inflating: system.img
Click to expand...
Click to collapse
yakuzu said:
Thanks!
What else do I need to load other than cache.img? I prefer not to lose all my user data (please no factory reset)
Click to expand...
Click to collapse
Well, you want the bootloader and the radio too.
Aerowinder said:
Well, you want the bootloader and the radio too.
Click to expand...
Click to collapse
I got this error:
Code:
fastboot flash cache cache.img
target reported max download size of 1073741824 bytes
erasing 'cache'...
FAILED (remote: not supported in locked device)
finished. total time: 0.073s
yakuzu said:
I got this error:
Code:
fastboot flash cache cache.img
target reported max download size of 1073741824 bytes
erasing 'cache'...
FAILED (remote: not supported in locked device)
finished. total time: 0.073s
Click to expand...
Click to collapse
Unlock bootloader
Sent from my Nexus 5 using XDA Free mobile app
Lol
31ken31 said:
Unlock bootloader
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
How about no?
it said void the warranty and seriously I just want my ****ing SIM card to work, why is it too damn complicated!? Isn't this pushed by Google OTA and verified that it won't brick any devices?
yakuzu said:
How about no?
it said void the warranty and seriously I just want my ****ing SIM card to work, why is it too damn complicated!? Isn't this pushed by Google OTA and verified that it won't brick any devices?
Click to expand...
Click to collapse
Your not bricked. Not even close
Sent from my Nexus 5 using XDA Free mobile app
31ken31 said:
Your not bricked. Not even close
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Sure, but why would Google push an update that break someone's SIM card recognition?
And now I have to fix it myself???
yakuzu said:
Sure, but why would Google push an update that break someone's SIM card recognition?
And now I have to fix it myself???
Click to expand...
Click to collapse
If it was on googles end it be happening to many many more devices. All it takes is one piece of corrupted data in a ota to screw it up. Bright side is it is fixable. You can unlock then relock if needed.
Sent from my Nexus 5 using XDA Free mobile app
31ken31 said:
If it was on googles end it be happening to many many more devices. All it takes is one piece of corrupted data in a ota to screw it up. Bright side is it is fixable. You can unlock then relock if needed.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I don't think it's the OTA issue, because I reflash mine with copy from google.com and still issue. I honestly think their Android 5.1 Lollipop update just simply don't work on this Nexus 5. I think there are many revision of Nexus 5 and this is probably an oversight from Google.
yakuzu said:
I don't think it's the OTA issue, because I reflash mine with copy from google.com and still issue. I honestly think their Android 5.1 Lollipop update just simply don't work on this Nexus 5. I think there are many revision of Nexus 5 and this is probably an oversight from Google.
Click to expand...
Click to collapse
Mine works great with 5.1 and I have had the same lost baseband issue. Being I'm rooted I can flash anything I want and can fix it in minutes. But only other option is send it in. They will fix it and probably wipe it too.
Sent from my Nexus 5 using XDA Free mobile app
31ken31 said:
Mine works great with 5.1 and I have had the same lost baseband issue. Being I'm rooted I can flash anything I want and can fix it in minutes. But only other option is send it in. They will fix it and probably wipe it too.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Just call them and they refuse to take it from me. They said passed the warranty. That's so BS! They obviously ruined my phone with their software OTA.
What are my options now?
Voice and text will work fine, but the data doesn't actually seem to connect. An exclamation point will show where data should be. If I flash back to stock 5.x, mobile data works. I will note that it shows LTE, while it seems slow for sure though.
I've done the usual troubleshooting like reset factory wipe, clear cache and davik. I previously wasn't ever rooted, but have since during troubleshooting..... I checked/confirmed APNs....
One theory is that my persisent and/or data/misc folders/files are corrupt from an OTA somehow.
How do I obtain "stock from factory" root files to start over?
It seems something in this file configs must only be compatible with 5.x and not 4.x ?
Just brainstorming.....
Did you downgrade bootloader and radio as well?
Also, doesn't seem to be a problem with /persist.
Sent from my Nexus 5 using Tapatalk
Yes, is that where I went wrong?
I did the manual "method 2" with all of the stock files hammerhead-krt16m_4.4 and also tried hammerhead-ktu84p_4.4.4:
fastboot flash bootloader C:\androidimage\bootloader.img
fastboot reboot-bootloader
fastboot flash radio C:\androidimage\radio.img
fastboot reboot-bootloader
fastboot flash system C:\androidimage\system.img
fastboot flash userdata C:\androidimage\userdata.img
(Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked.)
fastboot flash boot C:\androidimage\boot.img
fastboot flash recovery C:\androidimage\recovery.img
fastboot erase cache
fastboot flash cache C:\androidimage\cache.img
Click to expand...
Click to collapse
beekay201 said:
Did you downgrade bootloader and radio as well?
Also, doesn't seem to be a problem with /persist.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Prodeje79 said:
Yes, is that where I went wrong?
I did the manual "method 2" with all of the stock files hammerhead-krt16m_4.4 and also tried hammerhead-ktu84p_4.4.4:
Click to expand...
Click to collapse
Nope, actually, downgrading both bootloader and radio is the right thing to do.
Did you try to use HSDPA, instead of LTE?
Sent from my Nexus 5 using Tapatalk
I did not as I figured those auto settings have always worked for me and should continue to do so.
beekay201 said:
Nope, actually, downgrading both bootloader and radio is the right thing to do.
Did you try to use HSDPA, instead of LTE?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
For some reason, my M8 rebooted and now it's telling me it's data is corrupted even though I put in the right password. In recovery, it says "Cannot mount /data" when I tried to factory reset.
Stock, S-On. 5.0.1.
TheForceUnleashed said:
For some reason, my M8 rebooted and now it's telling me it's data is corrupted even though I put in the right password. In recovery, it says "Cannot mount /data" when I tried to factory reset.
Stock, S-On. 5.0.1.
Click to expand...
Click to collapse
Boot to bootloader. Run the fastboot command
Fastboot oem task 28
Then reboot.
Sent from my HTC6535LVW using Tapatalk
dottat said:
Boot to bootloader. Run the fastboot command
Fastboot oem task 28
Then reboot.
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
Did not work. Still tells me the same thing.
TheForceUnleashed said:
Did not work. Still tells me the same thing.
Click to expand...
Click to collapse
OK. Now try this
Fastboot oem task 29
Sent from my HTC6535LVW using Tapatalk
dottat said:
OK. Now try this
Fastboot oem task 29
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
Still not effective.
TheForceUnleashed said:
Still not effective.
Click to expand...
Click to collapse
Well...if that combo and the s-on ruu doesn't help it you need a new board. Sorry man.
Sent from my HTC6535LVW using Tapatalk
I am having this problem in addition to phone randomly rebooting. I have latest RUU w SF patch and Firmware .9. RUU and Restore will fix it and now discovered formatting /Data plus Restore will fix it. Can I do anything else to stop it or is the phone croaking?
Thanks
schneid said:
I am having this problem in addition to phone randomly rebooting. I have latest RUU w SF patch and Firmware .9. RUU and Restore will fix it and now discovered formatting /Data plus Restore will fix it. Can I do anything else to stop it or is the phone croaking?
Thanks
Click to expand...
Click to collapse
Are you using any rooted apps that could be causing it? Letting the battery die while using apps etc? Can you wipe it and run it stock for a couple days without restoring apps?
Sent from my XT1575 using Tapatalk
dottat said:
Are you using any rooted apps that could be causing it? Letting the battery die while using apps etc? Can you wipe it and run it stock for a couple days without restoring apps?
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Are you using any rooted apps that could be causing it? Xposed and mods would be my best guess.
Letting the battery die while using apps etc? Nope
Can you wipe it and run it stock for a couple days without restoring apps? Yes. Was looking for a simple fix but if I must, I have to give that a try.
Think I'll start with Xposed and disabling the Mods first.
Thanks and especially for the RUU's when all else fails.