So I wiped my phone in TWRP, flashed the factory image, booted, flashed TWRP, sideloaded 30O, booted, pushed and flashed SuperSU, booted, made a nandroid backup, and booted again and set up the phone.
Anyway, I can't double tap to wake anymore, and the other gestures don't work unless the screen was very recently turned off, otherwise all gestures I do seem to pile up and only activate once I manually press the power button and enter the lock screen. Also, capacitive buttons aren't any brighter. I haven't tested anything else from the 30O changelog, but either I did something worng or this update is garbage
I don't have those issues, it must be something on your end. My cap button lights aren't any brighter, but that doesn't bother me, I know where they are so I don't need them bright.
Transmitted via Bacon
timmaaa said:
I don't have those issues, it must be something on your end. My cap button lights aren't any brighter, but that doesn't bother me, I know where they are so I don't need them bright.
Transmitted via Bacon
Click to expand...
Click to collapse
I restarted my phone to recovery and wiped the dalvik cache, and cache, and upon booting up I noticed a download arrow telling me to download and install 30O, but as you can see everything seems as it should in the "About phone" pane, and some of the changelog fixes have been applied like the "OK Google" and speaker volume during calls...
Did you flash the official OTA or the modified one?
Transmitted via Bacon
timmaaa said:
Did you flash the official OTA or the modified one?
Transmitted via Bacon
Click to expand...
Click to collapse
The one from android authority, so official, yeah? I'm going to return my phone to stock and let it install the update on it's own before I start flashing stuff, we'll see if everything is as it should including the capacitive key brightness. I thought was very thorough, and I didn't get any errors, so I don't know what went wrong...
Same as me. Already on the new update, but the annoying message keeps poping out to tell me to update!
Sent from my A0001 using XDA Free mobile app
Its an incremental update guys
Humm I tried to install it but not installing through twrp. ?
Sent from my A0001 using XDA Free mobile app
I did the adb sideload and everything is working good. I Dont see any change in the capacitive buttons brightness which is not a problem.
Sent from my A0001 using XDA Free mobile app
---------- Post added at 12:36 AM ---------- Previous post was at 12:33 AM ----------
tssphysicsboi said:
Humm I tried to install it but not installing through twrp. ?
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
How did you try to flash the zip. You must use adb sideload not just copying to phone and flash if that is what you did.
Sent from my A0001 using XDA Free mobile app
vamshi88 said:
I did the adb sideload and everything is working good. I Dont see any change in the capacitive buttons brightness which is not a problem.
Sent from my A0001 using XDA Free mobile app
---------- Post added at 12:36 AM ---------- Previous post was at 12:33 AM ----------
How did you try to flash the zip. You must use adb sideload not just copying to phone and flash if that is what you did.
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
I wiped the phone in TWRP, flashed the factory image using EddyOS's flash-all factory image, booted, sideloaded 30O using the stock recovery, booted, set up the phone, and everything was working as it should.
IDK why double tap to wake got ****ed among other things when I sideloaded the OTA update using TWRP as I got no errors.
Anyway, I installed the incremental update as well, I didn't realize it was a different "incremental" update the first time around. The capacitive buttons are the same, it doesn't bother me, I know where they are, they're fine indoors, and the screen itself sucks in direct sunlight anyway. I just got paranoid as things were going wrong initially and the blasted devs said they did something to make them brighter, who knows what's up with that...
rickyx32 said:
IDK why double tap to wake got ****ed among other things when I sideloaded the OTA update using TWRP as I got no errors.
Click to expand...
Click to collapse
in my case the double tap to wake was working fine until i interestingly found that it was disabled in settings yet still working, just had to check and uncheck now its fine, just a glitch i guess.:cyclops:
Also no issues with gestures may be just a bad flash, try clearing cache and dalvik. or may be flash again.
@vamshi88 @timmaaa Sigh, for some reason I cant flash TWRP recovery anymore after sideloading 30O using the stock recovery and installing the incremental update not sure if the incremental update has anything to do with it though...
Edit: It shows that everything went okay when I flash it but when I reboot to recovery only stock recovery is there... I need coffee...
C:\Android\android-sdk\platform-tools>fastboot flash recovery openrecovery-twrp-2.7.1.1-bacon.img
target reported max download size of 536870912 bytes
sending 'recovery' (12260 KB)...
OKAY [ 0.388s]
writing 'recovery'...
OKAY [ 0.158s]
finished. total time: 0.547s
rickyx32 said:
@vamshi88 @timmaaa Sigh, for some reason I cant flash TWRP recovery anymore after sideloading 30O using the stock recovery and installing the incremental update not sure if the incremental update has anything to do with it though...
Click to expand...
Click to collapse
did you try fastbooting twrp.
vamshi88 said:
did you try fastbooting twrp.
Click to expand...
Click to collapse
Yeah man,
C:\Android\android-sdk\platform-tools>fastboot flash recovery openrecovery-twrp-2.7.1.1-bacon.img
target reported max download size of 536870912 bytes
sending 'recovery' (12260 KB)...
OKAY [ 0.388s]
writing 'recovery'...
OKAY [ 0.158s]
finished. total time: 0.547s
I got it to work, I had to go into developer options and uncheck the "Update CM recovery", what I don't get is why it was overriding TWRP if the system updates had already been installed long before...
rickyx32 said:
Anyway, I can't double tap to wake anymore, and the other gestures don't work unless the screen was very recently turned off, otherwise all gestures I do seem to pile up and only activate once I manually press the power button and enter the lock screen.
Click to expand...
Click to collapse
Mine did this. A power off and then back on again sorted it - I did have to wait 15 mins whilst it "optimized" all of my apps. Guess the drawback of running ART.
Related
Hey guys. For some odd reason I'm having issues with my AT&T HOX. I was running the Sense 5 rom and everything was running great. I was going to flash a battery % mod so, I held the power button down to get to the reboot menu to go into recovery. Well I accidently tapped the power off button instead of reboot. Crap! No problem, I thought. When I powered the phone back up again, the phone just sat on the HTC Quiet Brilliantly screen and wouldn't go any further. So, I held down the power button to force it to shut down, held the volume down key to go to the bootloader and then into TWRP. I couldn't get into TWRP. The phone would get to the TWRP splash screen and then reboot. But then it wouldn't even go back into android. It would just stay at the HTC screen. The only way I could get it into android was to RUU the phone. I flashed TWRP 2.3.3.0 on it via adb but now I still can't get into TWRP. The phone goes into a boot loop on the TWRP splash screen. I tried to do a fastboot wipe cache but that didn't help at all. Any suggestions?
You flashed recovery with adb..? You need to flash it with fastboot. Always check the md5 of your files to make sure they're good
Sent from my HTC One X using xda app-developers app
Haha, sorry, I meant fastboot. I flashed it with fastboot. When it didn't work the first time. I re-downloaded twrp and flashed it again. Same results.
Sent from my HTC One X using Tapatalk 2
Did you run the RUU? Which one? Running a RUU will restore stock recovery.
Also, the command is fastboot erase cache. Is that what you did?
Yes, I ran the AT&T 3.18 ruu. Don't worry I have s-off. The phone booted up fine after I ran the AT&T ruu. I then wanted to flash TWRP so I could install a different rom. I went to the bootloader and flashed TWRP 2.3.3.0. I flashed it with the OneX toolkit. I also did a fastboot erase cache when it didn't want to boot into TWRP. When I try to get into TWRP, it gets to the splash screen of TWRP, then the screen flashes for a second and it won't go any further. It keeps doing that until I force the phone to shut down. I am using the phone now but on 3.18 and I can't root it. I am stock. EWW!
Sent from my HTC One X using Tapatalk 2
I'm not a big fan of toolkits. They let you skip over learning things you really need to know.
Try downloading the twrp image, check the md5 to be sure it downloaded correctly, and flash in fastboot manually.
It's possible something isn't working right with the toolkit.
iElvis said:
I'm not a big fan of toolkits. They let you skip over learning things you really need to know.
Try downloading the twrp image, check the md5 to be sure it downloaded correctly, and flash in fastboot manually.
It's possible something isn't working right with the toolkit.
Click to expand...
Click to collapse
Just a few minutes ago, I re-downloaded TWRP again and flashed it with fastboot flash recovery. It said it was successful but, it is still doing the same thing. TWRP acts like it wants to boot but it won't. It gets to the splash screen and then it will just blink on and off, on and off until I force the phone to shut off.
Dang I've never seen anyone have that problem so far... That's weird.. You're doing everything correct and you sound knowledgeable.... Have you tried different twrp versions? Maybe try goo manager...
And I'm not questioning your intelligence and mean no disrespect, but are you 100% its the Evita version of twrp?
Sent from my One X using Tapatalk 2
InflatedTitan said:
Dang I've never seen anyone have that problem so far... That's weird.. You're doing everything correct and you sound knowledgeable.... Have you tried different twrp versions? Maybe try goo manager...
And I'm not questioning your intelligence and mean no disrespect, but are you 100% its the Evita version of twrp?
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Thanks man, haha, yeah I am 1000% sure it is an evita recovery. I thought about trying CWM just to see if the situation changes. Before I do that, I may try goo manager.
Yay!! I was able to flash CWM, get into it and flash SuperSU. I don't really care for CWM but at least i got SOMETHING to work. I may try TWRP again just to see if it will work.
Egrier said:
Yay!! I was able to flash CWM, get into it and flash SuperSU. I don't really care for CWM but at least i got SOMETHING to work. I may try TWRP again just to see if it will work.
Click to expand...
Click to collapse
Now that recovery is working again, you should be able to switch using goo manager.
iElvis said:
Now that recovery is working again, you should be able to switch using goo manager.
Click to expand...
Click to collapse
I tried re-downloading from a different source and flashing TWRP 2.3.3.1 again....Fail. It does the same thing. Flashed CWM again, works like a charm. What the heck is going on??
Egrier said:
I tried re-downloading from a different source and flashing TWRP 2.3.3.1 again....Fail. It does the same thing. Flashed CWM again, works like a charm. What the heck is going on??
Click to expand...
Click to collapse
Try fastboot erase cache again
Did you use Goo Manager?
iElvis said:
Try fastboot erase cache again
Did you use Goo Manager?
Click to expand...
Click to collapse
I will try fastboot erase cache. No, I flashed it with fastboot flash recovery.
Edit: Still a no go with TWRP :/ I guess I'm sticking with CWM for now.
Egrier said:
Hey guys. For some odd reason I'm having issues with my AT&T HOX. I was running the Sense 5 rom and everything was running great. I was going to flash a battery % mod so, I held the power button down to get to the reboot menu to go into recovery. Well I accidently tapped the power off button instead of reboot. Crap! No problem, I thought. When I powered the phone back up again, the phone just sat on the HTC Quiet Brilliantly screen and wouldn't go any further. So, I held down the power button to force it to shut down, held the volume down key to go to the bootloader and then into TWRP. I couldn't get into TWRP. The phone would get to the TWRP splash screen and then reboot. But then it wouldn't even go back into android. It would just stay at the HTC screen. The only way I could get it into android was to RUU the phone. I flashed TWRP 2.3.3.0 on it via adb but now I still can't get into TWRP. The phone goes into a boot loop on the TWRP splash screen. I tried to do a fastboot wipe cache but that didn't help at all. Any suggestions?
Click to expand...
Click to collapse
What about erasing cache?
Sent from my HTC One XL using xda app-developers app
Megadoug13 said:
What about erasing cache?
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
I have erased it. Doesn't work.:banghead:
Sent from my HTC One X using Tapatalk 2
Egrier said:
I have erased it. Doesn't work.:banghead:
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
I would try Goo Manager, then give up if it doesn't work. CWM is okay for this phone now.
iElvis said:
I would try Goo Manager, then give up if it doesn't work. CWM is okay for this phone now.
Click to expand...
Click to collapse
Been there did that. Still won't work. Going to forget it and stick with CWM for now.
Installation:
Unlock your phone at www.htcdev.com
Boot phone into fastboot
Perform command fastboot flash recovery recovery-clockwork-6.0.4.4-m4.img or the recovery.img file name
Boot into HBOOT and select recovery
Root:
Download http://download.clockworkmod.com/superuser/superuser.zip
Flash it in recovery
Download:
Main - http://d-h.st/Sft
Flyhalf205 said:
This is a test for anyone who has the phone.
I'll fix it up and get you guys TWRP and CWM Touch once we verify this one works.
Download:
http://d-h.st/sJH
Thanks
Github: https://github.com/Flyhalf205/android_device_htc_m4
Click to expand...
Click to collapse
Hey Flyhalf!
I just flashed your recovery. but when entering recovery I only get HTC-screen with small pink text "Entering Recovery..." and nothing happens.
flashing was successful:
fastboot flash recovery recovery.img
sending 'recovery' (7880 KB)...
OKAY [ 1.088s]
writing 'recovery'...
OKAY [ 2.106s]
finished. total time: 3.194s
any ideas?
I can confirm also - doesn't boot.
Help this man to build you guys a working recovery! He makes miracles happen! He has my personal backing!
Sent From My HTC One via Someone's Room
hasoon2000 said:
Help this man to build you guys a working recovery! He makes miracles happen! He has my personal backing!
Sent From My HTC One via Someone's Room
Click to expand...
Click to collapse
How can we help ?
Should I donate some euro`s ?
I think we have to wait for a update of the recovery he developed in post 1, then it is possible to look forward and give some help.
theodorius123 said:
Hey Flyhalf!
I just flashed your recovery. but when entering recovery I only get HTC-screen with small pink text "Entering Recovery..." and nothing happens.
flashing was successful:
fastboot flash recovery recovery.img
sending 'recovery' (7880 KB)...
OKAY [ 1.088s]
writing 'recovery'...
OKAY [ 2.106s]
finished. total time: 3.194s
any ideas?
Click to expand...
Click to collapse
I cant help notice that he said don't flash it, just boot it and it looks like you flashed it.
Try booting the img rather than flashing it.
Hopefully it will work. Good luck!
Sent from my HTC Desire using Tapatalk 2
scutworker said:
I cant help notice that he said don't flash it, just boot it and it looks like you flashed it.
Try booting the img rather than flashing it.
Hopefully it will work. Good luck!
Sent from my HTC Desire using Tapatalk 2
Click to expand...
Click to collapse
If it doesn't work flashing it, then it won't work booting it either.
Flyhalf suggested booting it, using the fastboot boot file.img command, so that it's temporary.
CNexus said:
If it doesn't work flashing it, then it won't work booting it either.
Flyhalf suggested booting it, using the fastboot boot file.img command, so that it's temporary.
Click to expand...
Click to collapse
Ahhh, I see. Thanks for clearing that up.
I intend to buy one of these soon: is anybody closer to getting root yet?
Sent from my HTC Desire using Tapatalk 2
scutworker said:
I intend to buy one of these soon:
Click to expand...
Click to collapse
I was able to get R/W on /system - also pushed SuperSU to system/app and binaries - but SuperSU is not working, cant find binaries. no idea whats the problem.
the bigger problem I have is the boot.img I use right now to get R/W - its from a pre-production unit and WiFi is not working
As I wrote here: I'm waiting for an actual boot.img...
theodorius123 said:
I was able to get R/W on /system - also pushed SuperSU to system/app and binaries - but SuperSU is not working, cant find binaries. no idea whats the problem.
the bigger problem I have is the boot.img I use right now to get R/W - its from a pre-production unit and WiFi is not working
As I wrote here: I'm waiting for an actual boot.img...
Click to expand...
Click to collapse
Thanks.
You should contact this chap here on xda: he has a new mini and wants to help.
Good luck.
scutworker said:
Thanks.
You should contact this chap here on xda: he has a new mini and wants to help.
Good luck.
Click to expand...
Click to collapse
thanks! but I'm in contact with Zarboz, so when he will be able to dump the boot.img from this guy, he will (hopefully) let me know.
I'm not able to do those things
scotty2000 said:
How can we help ?
Should I donate some euro`s ?
I think we have to wait for a update of the recovery he developed in post 1, then it is possible to look forward and give some help.
Click to expand...
Click to collapse
Need some testing time with a one mini owner or a one mini to test on
Sent from my SCH-R970 using xda premium
What phones can use it?
Sent from my Lenovo A690 using xda app-developers app
Zarboz said:
Need some testing time with a one mini owner or a one mini to test on
Sent from my SCH-R970 using xda premium
Click to expand...
Click to collapse
what are the risks? really dont want my phone to be worse then now
theodorius123 said:
what are the risks? really dont want my phone to be worse then now
Click to expand...
Click to collapse
need a user without a tampered boot sector so that we can get you the stuff you need for wifi etc
My phone is stock without any manipulations. So what can I do ? Hope it is not too big risk, cause there is no factory Rom out now I think, which we can use to flash back...
Sent from my HTC One mini using xda app-developers app
scotty2000 said:
My phone is stock without any manipulations. So what can I do ? Hope it is not too big risk, cause there is no factory Rom out now I think, which we can use to flash back...
Sent from my HTC One mini using xda app-developers app
Click to expand...
Click to collapse
I've got two images for system but I need about thirty minutes n teamviewr I have something precooked that's verified working
Sent from my SCH-R970 using XDA Premium 4 mobile app
Zarboz said:
need a user without a tampered boot sector so that we can get you the stuff you need for wifi etc
Click to expand...
Click to collapse
mmmmh. that makes sense :good:
If we can get this recovery with just adbd running properly then we can flash it to someone's phone, dump the boot.img, make it insecure to get root and flash it to someone else's phone and then dump the stock recovery to get a proper custom recovery
Maybe if @Flyhalf205 replied to this we could get something going
Okay. So where do we stand now. So the recovery does not boot in the OP? And @theodorius123 how are you mounting RW the system?
My One has been acting up lately. It started out that I couldn't turn off WiFi. I would turn it off but it would turn itself back on shortly thereafter. It has nothing to do with WiFi optimization or anything like that...I've fiddled with all those settings. Anyway, I updated to 38R thinking it might fix things, but no such luck. So I fire up titanium backup in preparation for a full wipe and find out that my device is no longer rooted. On top of that, TWRP is gone as well. No big deal, reflash TWRP and re-root. Nope. ADB says that TWRP flashes successfully, but when I boot into recovery I get the standard Cyanogen recovery instead of TWRP. Any thoughts?
Have you tried flashing stock and starting from scratch?
Did you remember to uncheck the option for updating fastboot with system update as well?
Sent from my Nexus 7 using XDA Premium HD app
Admeisterz said:
Have you tried flashing stock and starting from scratch?
Did you remember to uncheck the option for updating fastboot with system update as well?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Unfortunately I missed the fastboot update bit. Did I **** myself with that?
If you could access CWM do a factory reset, and hopefully that clears up your problems, if not go back to stock via: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
the only reason why i could think that it'd say flashing is successful is it's flashing to the wrong partition (which doesn't make any sense), or the bootloaders locked, which it isn't since from your post it says you had TWRP installed, but try going back to stock fully via fastboot, then installing twrp and such.
Hi all.
Can anyone lend a hand to help me get my phone rooted again? I had originally rooted it when it first turned up, by using the guide on these forums. Since then I (stupidly) did the OTA upgrade not thinking about losing root. I went from 33r to 38r. The first I knew was when Titanium back up wouldn't back up.
My problem is that neither of my computers (desktop - XP) (Laptop - Windows 7) will now see my phone. They will both make a sound when connecting via the USB cable but neither of them show the phone via My Computer. I've un-installed/installed the drivers again and I have tried putting the phone in Fastboot and clicking on Unlock Bootloader, via the Toolbox V3, but the phone will only "reboot" to the home screen. I'm needing a bit of help from someone who knows what they are doing
Thanks in advance for any help... Foz
Once you unlock the bootloader, I don't think you need to unlock it again. If you lose root after an OTA, I think all you need to do is reflash superuser from recovery. And don't touch those toolboxes. They don't help you learn to solve these problems by yourself.
Sent from my A0001 using XDA Free mobile app
I've tried that but it fails...
Turn off phone.
volumedown and on
phone enters cyanogen recovery
apply update
internal storage
(locate to SuperSU -v2.02.zip
INSTALL FAILS.
OKay
reboot system, back to my normal settings/homescreen.
I have SuperSu on my phone BUT get the warning that no binary is installed and I need to re root, hencmy posting here.
adamfoz said:
I've tried that but it fails...
Turn off phone.
volumedown and on
phone enters cyanogen recovery
apply update
internal storage
(locate to SuperSU -v2.02.zip
INSTALL FAILS.
Click to expand...
Click to collapse
If re-downloading the zip doesn't work you should try a newer SuperSU version.
meekrawb said:
If re-downloading the zip doesn't work you should try a newer SuperSU version.
Click to expand...
Click to collapse
I believe I have the latest version from the play store ( 2.14).
adamfoz said:
I believe I have the latest version from the play store ( 2.14).
Click to expand...
Click to collapse
Should have clarified, you should try a newer version of the zip.
download.chainfire.eu/supersu
Just looked again when in cyan recovery. The Supersu is 2.02 and yet google says I have the 2.14 installed.... (and I have to wait betweening posting arrggghh) Ok, Ill have a play and see what happens. thanks guys
adamfoz said:
Just looked again when in cyan recovery. The Supersu is 2.02 and yet google says I have the 2.14 installed.... (and I have to wait betweening posting arrggghh) Ok, Ill have a play and see what happens. thanks guys
Click to expand...
Click to collapse
I think your problem may be that when you installed the OTA, you also clobbered any custom recovery that was there. Next time, uncheck the option to install recovery.
sparkdroid said:
I think your problem may be that when you installed the OTA, you also clobbered any custom recovery that was there. Next time, uncheck the option to install recovery.
Click to expand...
Click to collapse
So... Do I bite the bullet, factory reset and......?
Sent from my A0001 using XDA Free mobile app
adamfoz said:
So... Do I bite the bullet, factory reset and......?
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
no flash twrp or any custom recovery in adb and then you can flash the root zip.
I'm following this guide for rooting http://forum.xda-developers.com/showthread.php?t=2788632 .
I'm assuming that I'm doing things ok to a point, as the CMD prompt is saying adb version is 1.0.32 but when i put the phone in fast boot, and type "fastboot devices" the phone will show up in the cmd prompt. Its when I "fastboot oem unlock" and"fastboot reboot", the phone will reboot as normal. No setting up of the phone. All my apps and settings are still there, indicating to me that something is wrong :/
I'm assuming that my drivers are ok otherwise I wouldn't be seeing the above in the cmd prompts but...
Can someone tell me if my mobile should show up in "my computer" ? it has in the past, but no longer does. and I'm wondering if this could have someing to do with my problems??
Thanks again..Foz
If your rooted, you have already unlocked the boot loader unless you relocked it. Did you? If not don't worry about unlock and flash custom recovery and flash supersu zip
I did have a rooted phone until I did an ota update. This lost my root and i have been trying to get root back, but I'm having no luck. Im guessing if I am still struggling tomorrow night, ill factory reset. I have recent back ups so...
Sent from my A0001 using Tapatalk
adamfoz said:
I did have a rooted phone until I did an ota update. This lost my root and i have been trying to get root back, but I'm having no luck. Im guessing if I am still struggling tomorrow night, ill factory reset. I have recent back ups so...
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
All you need to do is flash SuperSU again. It's normal to lose root during an OTA update.
EDIT: didn't read properly. Have you gotten TWRP to flash yet?
Transmitted via Bacon
Nope. As in post 12. Phones connecting to the pc, its not wiping any data etc after any commands for unlocking boot loader
Sent from my A0001 using XDA Free mobile app
adamfoz said:
Nope. As in post 12. Phones connecting to the pc, its not wiping any data etc after any commands for unlocking boot loader
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Why are you trying to unlock the bootloader again though? Did you relock it manually at some point?
Transmitted via Bacon
timmaaa said:
Why are you trying to unlock the bootloader again though? Did you relock it manually at some point?
Transmitted via Bacon
Click to expand...
Click to collapse
I'm (wrongly) assuming bootloader needed unlocking again after the ota update because twrp would not install again. I assumed the whole phone needed all 3 processes to gain root again.
Sent from my A0001 using XDA Free mobile app
adamfoz said:
I'm (wrongly) assuming bootloader needed unlocking again after the ota update because twrp would not install again. I assumed the whole phone needed all 3 processes to gain root again.
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
The bootloader shouldn't lock again unless you do it yourself. The recovery (unnecessarily because you can uncheck the 'update cm recovery' option in Developer Options to keep your custom recovery) and root (no way around it) are lost during the OTA but the bootloader should remain unlocked. What response do you get when issuing the following command?
Code:
fastboot oem device-info
Please paste the results here.
Transmitted via Bacon
As soon as I'm home, I'll let you know.....
Thanks
Sent from my A0001 using XDA Free mobile app
Is there any way to root without using a pc like I did with my G3 using Stumproot?
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?