Related
So it appears that some people (myself included) are having issues with their new Nexus 7. Specifically, where it is failing to install the second OTA update, which brings the tablet to version JSS15J. The first update (which is almost instant) works, but the second 50+MB one fails after rebooting into stock recovery.
It is failing because the file "/system/app/PrebuiltGmsCore.apk" is failing the sha1 checksum check. Why is this happening? Because the tablet is looking for a different version of the file then what is installed on some of our tablets. Why do different people have different versions? I have no idea. But it's certainly an issue for a few people including myself. I tried various standard work arounds but came up with no fix to get the OTA update, as is, to install. Then I decided to see if that was the only issue present and develop a work around.
I'm pleased to say that:
1) The PrebuiltGmsCore.apk file is the only one that breaks the OTA update. Everything else is fine.
2) I was successful in fixing this by creating a custom OTA update zip and installing it on my tablet.
3) I'm providing this modified update.zip for people to load on their tablets if they are having the same issue.
A couple of notes first...
Obviously, flash this at your own risk.
You NEED TO HAVE A CUSTOM RECOVERY for it to work. TWRP has already been ported over, so install that first.
Once you are in custom recovery, flash this file just like any other update.
Lastly, you should only download/install this if you are having the problem where the second OTA update fails. If you are currently running JSS15J, this update will fail (as it should).
This is 98% stock OTA update. All I did was some minor tweaks to fix the issue. Specifically:
1) I removed both the check for the PrebuiltGmsCore.apk file as well as the patching of it (since this fails).
2) I took the full JSS15J version of PrebuiltGmsCore.apk and built it directly into the update.
3) I removed the parts of the OTA update that mess with custom recovery. It will not install the /system/boot-from-recovery.p or /system/etc/install-recovery.sh files.
Once you install this, your tablet should be running identically to one that didn't suffer this issue.
Outside of using this, the only other option (AFAIK) is to wait until Google releases the full factory images and flash everything manually.
A big thanks to ATGAdmin for providing the stock JSS15J system dump that let me extract the updated PrebuiltGmsCore.apk file.
So without further ado, here is the update:
http://core.routed.com/JSS15J-Update.zip
Enjoy, and let me know if you have any questions.
Question: was your nexus 7 missing the wallpaper that they've been marketing with?
Sent from my Nexus 4 using xda app-developers app
shredder47 said:
Question: was your nexus 7 missing the wallpaper that they've been marketing with?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yes.
And I bought mine from Best Buy, which seems to be a common denominator with both of those issues.
However, I just checked, and I have that wallpaper now after installing this update.
Yeah sounds like that's the common denominator... I'm out right now but I'll try this out when I get home, thanks man!
Sent from my Nexus 4 using xda app-developers app
Thanks so much! This worked for me after trying other options failed. Mine was from Best Buy also.
Oh, one other quick note:
As I wanted to leave this as close to the stock OTA update as possible, this WILL remove root. Technically, the 'su' binary will remain, but it will lose it's suid permissions. It will also remove the daemon launcher (which is installed as the install-recovery.sh file).
So make sure to flash the root zip after installing this update.
One more thing:
While there aren't many mods out there yet that will mess with the update, eventually there will be. This custom update will check and verify that everything else (except that one file) is stock. So if you made any other modifications to any other system file (ie: build.prop, etc.), it will fail just like any other OTA. Your best bet is to install this before tweaking.
Worked great man!
Also, your download was rather slow so if you don't mind I made a mirror on mega: https://mega.co.nz/#!aE4CwJZB!J7QtUlqXhthhZcpPOUriaQ_u861k7rAGdHffRCmkQao
I have one from best buy and it updated just fine (both updates). I guess it's just luck of the draw.
Sent from my Nexus 7 using Tapatalk HD
Nburnes said:
Worked great man!
Also, your download was rather slow so if you don't mind I made a mirror on mega: https://mega.co.nz/#!aE4CwJZB!J7QtUlqXhthhZcpPOUriaQ_u861k7rAGdHffRCmkQao
Click to expand...
Click to collapse
Awesome, glad to hear! And sure, that's perfectly fine with me.
It's on a 100Mb pipe, but the data center occasionally has some bad routing that makes certain destinations slow. Can't complain since I get a dedicated server for $59/month .
fosser2 said:
I have one from best buy and it updated just fine (both updates). I guess it's just luck of the draw.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Yeah, I believe it to be a minority of tablets. Maybe just a bad batch that all happened to get sent to Best Buy. As time goes on and more people get them we'll see how wide spread it is. I'm curious to see what Google's official fix will be.
Yeah, got mine from best buy too, the 2nd update stood at the boot screen. I just rebooted and it's back to normal
Sent from my Nexus 4 using Tapatalk 4 Beta
paranoid android85 said:
Yeah, got mine from best buy too, the 2nd update stood at the boot screen. I just rebooted and it's back to normal
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Did you check to see if the update worked? If your version is still JWR66N, then it failed and you will either need to flash this or wait for an official fix from Google.
phonic said:
Did you check to see if the update worked? If your version is still JWR66N, then it failed and you will either need to flash this or wait for an official fix from Google.
Click to expand...
Click to collapse
I brick my nexus. Can someone upload nandroid backup please?
phonic said:
... Why is this happening? Because the tablet is looking for a different version of the file then what is installed on some of our tablets. Why do different people have different versions? I have no idea. But it's certainly an issue for a few people including myself. ...
Click to expand...
Click to collapse
Interesting. My update worked (mostly because oldblue910 was doing it). LOL
I got mine at Walmart and noticed one of the box labels had been modified. There is an extra label covering one label on the box (also, there are labels on both ends). It is barely noticeable. I tried to remove the one on top (to peek) but it started to tear.
I theorize mine was part of a modification process. Do you think some of those failed units at Best Buy *might* have missed the modification process?
Bob Smith42 said:
Interesting. My update worked (mostly because oldblue910 was doing it). LOL
I got mine at Walmart and noticed one of the box labels had been modified. There is an extra label covering one label on the box (also, there are labels on both ends). It is barely noticeable. I tried to remove the one on top (to peek) but it started to tear.
I theorize mine was part of a modification process. Do you think some of those failed units at Best Buy *might* have missed the modification process?
Click to expand...
Click to collapse
I'm not really sure. After looking at the first OTA update that oldblue910 posted, it definitely indicates that it was modified by that. If so, it had to have initially passed that first check. Why some units fail the second check makes little sense to me. The lack of the official wallpaper is also weird.
Additionally, that first OTA clearly shows that these devices were rushed. The fact that they were sent out with developer keys is just really bad QA.
My device, hardware wise, seems to be perfect. So I don't want to roll the dice and try to get another one, especially if the only issue is some minor software glitch that I already corrected. I haven't had a chance to really play with it yet, as I've been spending my time backing up/restoring files, so I'll see how it goes.
Thanks for this. Bought mine at Best Buys too and had the update fail.
Edit: TWRP gave the option to fix SU after flashing that zip and it seemed to work. I'll probably refresh zip anyways but TB still works.
Sent from my Nexus 4 using Tapatalk 4 Beta
stab244 said:
Thanks for this. Bought mine at Best Buys too and had the update fail.
Edit: TWRP gave the option to fix SU after flashing that zip and it seemed to work. I'll probably refresh zip anyways but TB still works.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yes, you should reapply the root zip.
The OTA update does two things in this regard. It removes the two 'recovery recovery' files, and it also removes the suid bit from the su binary. The TWRP su fix will reapply the suid bit to 'su' (thus making it actually work), but it doesn't put back the SuperSU daemon launcher (/system/etc/install-recovery.sh). By applying the root zip again, it will fix both of these.
I thought about removing the part of the update that deletes this file, but again I wanted to keep it as stock as possible. Also, for people who hadn't rooted yet but do have a custom recovery, it would help keep it custom and not require them to manually remove those files that would (stock) reset the recovery back.
I also purchased mine at Best Buy, therefore I also have the problem.
What exactly does this 2nd update do? Is it a drastic improvement over JWR66N?
xene97 said:
I also purchased mine at Best Buy, therefore I also have the problem.
What exactly does this 2nd update do? Is it a drastic improvement over JWR66N?
Click to expand...
Click to collapse
If you are asking what files it changes, you can look inside the zip file and see all of that. It's fairly extensive. The vast majority are patches to many components of the operating system and included applications. The first OTA update was only a few hundred kilobytes, while this one is 50megs, so a lot was updated.
If you are asking what the end-user result or benefit is between the two, I am not sure. I spent most of my time working on trying to get the update working, and spent very little time using the tablet before I was successful. So I can't comment about whether the update improves anything. However, others have said that it did help to resolve some issues they experienced before hand.
In any case, the new N7 was released quite quickly and we know that the factory installed OS had some issues. The fact that there were two OTA updates before the device was even released show that Google needed to fix a lot of stuff. While future updates (Key Lime Pie anyone?) will be more optional as it focuses on enhancements and upgrades, these two updates are significantly more important.
phonic said:
If you are asking what files it changes, you can look inside the zip file and see all of that. It's fairly extensive. The vast majority are patches to many components of the operating system and included applications. The first OTA update was only a few hundred kilobytes, while this one is 50megs, so a lot was updated.
If you are asking what the end-user result or benefit is between the two, I am not sure. I spent most of my time working on trying to get the update working, and spent very little time using the tablet before I was successful. So I can't comment about whether the update improves anything. However, others have said that it did help to resolve some issues they experienced before hand.
In any case, the new N7 was released quite quickly and we know that the factory installed OS had some issues. The fact that there were two OTA updates before the device was even released show that Google needed to fix a lot of stuff. While future updates (Key Lime Pie anyone?) will be more optional as it focuses on enhancements and upgrades, these two updates are significantly more important.
Click to expand...
Click to collapse
Thanks for the clarification!
It seems the n9 is eligible. Anyone has tried or thinking of trying? I might try
Flashing it right now. Just going to miss root, so u can drop my DPI and restore some apps.
Edit: sweet!! Though you can't fine tune the size, it now has default a way to change screen size/DPI. Now I'm only needing root to restore some apps and data.
Works pretty well for me so far, except for the fact that kernel support for libusb is gone, which stops my Headunit app from working over USB.
No root yet.
Recovery is replaced with stock recovery after a reboot.
There is more discussion in popular phone threads, like the one for Nexus 6p.
dictionary said:
Flashing it right now. Just going to miss root, so u can drop my DPI and restore some apps.
Edit: sweet!! Though you can't fine tune the size, it now has default a way to change screen size/DPI. Now I'm only needing root to restore some apps and data.
Click to expand...
Click to collapse
mikereidis said:
Works pretty well for me so far, except for the fact that kernel support for libusb is gone, which stops my Headunit app from working over USB.
No root yet.
Recovery is replaced with stock recovery after a reboot.
There is more discussion in popular phone threads, like the one for Nexus 6p.
Click to expand...
Click to collapse
Do we have to be on stock to receive the notification?
I opted in for the Android N program. Received the OTA and installed but the install FAILED. Now I can't boot and can't install an image because my bootloader is locked. Am I screwed?
EDIT: It's stuck on the "Google" screen
greiland said:
I opted in for the Android N program. Received the OTA and installed but the install FAILED. Now I can't boot and can't install an image because my bootloader is locked. Am I screwed?
EDIT: It's stuck on the "Google" screen
Click to expand...
Click to collapse
Same thing happened to me. The ota failed about 1/4 of the way through. Luckily my bootloader was unlocked. After reinstalling the system image and booting up it failed a second time when installing the ota. I think the ota has some definite issues.
Try the Nexus Root Toolkit to return to stock.
mikereidis said:
Works pretty well for me so far, except for the fact that kernel support for libusb is gone, which stops my Headunit app from working over USB.
No root yet.
Recovery is replaced with stock recovery after a reboot.
There is more discussion in popular phone threads, like the one for Nexus 6p.
Click to expand...
Click to collapse
Well I don't think the kernel if it had libusb stopped supporting it.
Because this is pretty much what changed in it https://github.com/USBhost/FIRE-ICE/commit/b88667be3ca75cdfd67269e25fb43956d78004c9
the defconfig. I ripped the defconfig from the kernel image, and I applied the needed changes to my defconfig.
edit:
if you want the N defconfig here you go https://github.com/USBhost/FIRE-ICE/commit/afdf42bd4af6aa042b9d9997de91d3e60c9ccc7e
I also went the OTA route and then got stuck in a Google logo boot loop. Boot loader is locked so I am trying a factory reset. Factory reset just finished as I'm typing this. It took about 40 minutes!!!! Once again seems to be stuck on the Google logo.
Edit--
Was able to get into fastboot and install factory image! Used the Nexus Toolkit to unlock the bootloader and so far things seem to be going smoothly.
I got the OTA and it installed fine 2 bugs I have found are if you're watching YouTube and put it in split screen with hangouts and tap the hangouts screen the video will go black until you tap on the YouTube side and the other bug is that the device decided to randomly put itself in airplane mode but over all I am liking it
Sent from my Nexus 5X using Tapatalk
OTA fails for me with message stating "Android Beta Program Verification failed..." after the download. I've registered for the BETA program as normal and got the OTA notification. Same install method worked fine on my 6P. As stated above, looks like the OTA for the 9 has some issues...
USBhost said:
Well I don't think the kernel if it had libusb stopped supporting it.
Because this is pretty much what changed in it https://github.com/USBhost/FIRE-ICE/commit/b88667be3ca75cdfd67269e25fb43956d78004c9
the defconfig. I ripped the defconfig from the kernel image, and I applied the needed changes to my defconfig.
edit:
if you want the N defconfig here you go https://github.com/USBhost/FIRE-ICE/commit/afdf42bd4af6aa042b9d9997de91d3e60c9ccc7e
Click to expand...
Click to collapse
Has somebody released N kernel source ?
I don't think there is any /dev/bus/ directory, never mind /dev/bus/usb/... but I'd feel more positive about that if I had root to verify.
mikereidis said:
Has somebody released N kernel source ?
I don't think there is any /dev/bus/ directory, never mind /dev/bus/usb/... but I'd feel more positive about that if I had root to verify.
Click to expand...
Click to collapse
well Google did release the source for it but... they goofed on it
Check it out https://github.com/USBhost/FIRE-ICE/tree/android-tegra-flounder-3.10-n-preview-1
BTW my kernel works on the N preview
Couldn't flash mine, always have "missing system.img" and "unable to allocate -xxxxx bytes"... Didn't have much time, I will try again later. Do I need to come from clean stock to flash it ?
I registered my Nexus 9 for the beta and got the OTA. But it failed with an ERROR (android on it's back with a !). It then rebooted and gets stuck at the Google logo for hours. My Nexus 9 was completely stock on 6.0.1. I downloaded the factory image, but I cannot unlock the device to flash it. All guides seem to say I need to enable Developer Options and enable USB Debugging, but since I can't boot into Android, I can't go that far. Am I screwed?
naddie said:
I registered my Nexus 9 for the beta and got the OTA. But it failed with an ERROR (android on it's back with a !). It then rebooted and gets stuck at the Google logo for hours. My Nexus 9 was completely stock on 6.0.1. I downloaded the factory image, but I cannot unlock the device to flash it. All guides seem to say I need to enable Developer Options and enable USB Debugging, but since I can't boot into Android, I can't go that far. Am I screwed?
Click to expand...
Click to collapse
sorry to tell you but yep!
you can try talking to Google to see if they can fix it.
USBhost said:
sorry to tell you but yep!
you can try talking to Google to see if they can fix it.
Click to expand...
Click to collapse
So being straight laced and not rooting actually bricked my tablet? What the hell....
I'm a bit surprised there's no way to flash a factory image when the bootloader is locked. If security is a concern why not sign the factory image? Make it something we can sideload like an OTA update.
I am in the same boat!!!
naddie said:
So being straight laced and not rooting actually bricked my tablet? What the hell....
Click to expand...
Click to collapse
I am in the same situation. I figured that the software would be buggy but not actually brick my tablet. If anyone knows of a solution, I hope they post it here!! I would advise against installing this onto a Nexus 9 if anyone reading this is considering this firmware!!!
better33 said:
Couldn't flash mine, always have "missing system.img" and "unable to allocate -xxxxx bytes"... Didn't have much time, I will try again later. Do I need to come from clean stock to flash it ?
Click to expand...
Click to collapse
No, just wipe everything except internal. You have to extract the last image.sksmsksjssksm whatever zip. Then just fastboot flash each file individually.
Will I be able to recover if the Android N preview fails on my Nexus 9 by unlocking the bootloader and enabling USB debugging beforehand then install Android N preview?
kalinskym said:
Will I be able to recover if the Android N preview fails on my Nexus 9 by unlocking the bootloader and enabling USB debugging beforehand then install Android N preview?
Click to expand...
Click to collapse
In short, yes. You're basically leaving yourself a backdoor to flash a factory image should the Android N preview OTA takes a dump on you.
As my professor said to us in the laboratory: Do as I say, not as I do.
To be fair, I was hoping to do a no-wipe upgrade so I could experience Android N with all my stuff intact. I knew it was beta, but come on!
I could really use some help. I'm at the edge of my patience and have tried pretty much everything I can think of. I say near brick cause a phone without WiFi and BT is kinda useless.
Here's the back story. I had my previous xt1575 stolen. I purchased a used one off ebay. I received it, only to find it was bootloader unlocked, rooted. Not an issue in theory but I wasn't told that. Ok, upon trying the phone it worked but the battery would last 3 hours, it would have random reboots and would run so hot i could hardly hold the phone. I figured it was a faulty kernel. I flashed a new kernel and stock rom. Battery life went back to almost perfect but was off by about 20%. The random reboots were still an issue, but everything else seemed to work. A randomly rebooting phone is far from ideal. I figured I'd keep trying. Maybe it was a software issue. I would get random results with different roms. And the rebooting really seemed to occur when I had all my apps downloaded. So, I decided to run to flash again and run lean and see if with just the default apps whether it would reboot. After the flash, I waited a few hours, then BT and WiFi just stopped working. No go. The actual toggles revert to off position essentially immediately and neither turn on. I've since tried FDRs, different roms, different kernels, no luck. No idea what to do at this point. It could be hardware, obviously. It could be that the wifi chip was faulty and causing the overheating/battery drain from before, and finally after running so hot that one day before I flashed, it just did final damage to the chip that came to pass 3 days later. I don't know. It's possible but i somehow feel like it's a SW issue. I could send it back but it's complicated and i would really prefer to see if I can get this resolved. I've reflashed the modem bin files of stock roms, etc. Another issue i get often is when i try flashing, I get the writing 'boot'... (bootloader) Preflash validation failed FAILED (remote failure) and other such failures. Additionally, TWRP often just disappears. Aside from that, the OS, usually runs fine. I can't download apps obviously due to no WiFi, but everything else seems fine and I haven't had any reboots since the wifi/bt stopped working. I don't know if it's a partition issue, or hardware or what. I could use some advice. I'm at the limit of my patience and my knowledge here.
Let me know what you guys need and thanks ahead of time for your help.
vijn said:
I could really use some help. I'm at the edge of my patience and have tried pretty much everything I can think of. I say near brick cause a phone without WiFi and BT is kinda useless.
Here's the back story. I had my previous xt1575 stolen. I purchased a used one off ebay. I received it, only to find it was bootloader unlocked, rooted. Not an issue in theory but I wasn't told that. Ok, upon trying the phone it worked but the battery would last 3 hours, it would have random reboots and would run so hot i could hardly hold the phone. I figured it was a faulty kernel. I flashed a new kernel and stock rom. Battery life went back to almost perfect but was off by about 20%. The random reboots were still an issue, but everything else seemed to work. A randomly rebooting phone is far from ideal. I figured I'd keep trying. Maybe it was a software issue. I would get random results with different roms. And the rebooting really seemed to occur when I had all my apps downloaded. So, I decided to run to flash again and run lean and see if with just the default apps whether it would reboot. After the flash, I waited a few hours, then BT and WiFi just stopped working. No go. The actual toggles revert to off position essentially immediately and neither turn on. I've since tried FDRs, different roms, different kernels, no luck. No idea what to do at this point. It could be hardware, obviously. It could be that the wifi chip was faulty and causing the overheating/battery drain from before, and finally after running so hot that one day before I flashed, it just did final damage to the chip that came to pass 3 days later. I don't know. It's possible but i somehow feel like it's a SW issue. I could send it back but it's complicated and i would really prefer to see if I can get this resolved. I've reflashed the modem bin files of stock roms, etc. Another issue i get often is when i try flashing, I get the writing 'boot'... (bootloader) Preflash validation failed FAILED (remote failure) and other such failures. Additionally, TWRP often just disappears. Aside from that, the OS, usually runs fine. I can't download apps obviously due to no WiFi, but everything else seems fine and I haven't had any reboots since the wifi/bt stopped working. I don't know if it's a partition issue, or hardware or what. I could use some advice. I'm at the limit of my patience and my knowledge here.
Let me know what you guys need and thanks ahead of time for your help.
Click to expand...
Click to collapse
What image are you using? Make sure you are using MPH24.49-18-4 (the -4 is important and newer than the one that ends in 18-18 on Moto's site) with the May 1, 2016, security update from here and flashing each step manually using this post's instructions.
I could explain most of the issues individually you are seeing, unless you are already using the specific version I referenced, since they all seem to relate to improper or old version flashing, but it doesn't really matter because the answer to all of them is the same... Reflash the proper version making sure each steps results in an OKAY.
If I am way off base, then it is likely a hardware problem.
acejavelin said:
What image are you using? Make sure you are using MPH24.49-18-4 (the -4 is important and newer than the one that ends in 18-18 on Moto's site) with the May 1, 2016, security update from here and flashing each step manually using this post's instructions.
I could explain most of the issues individually you are seeing, unless you are already using the specific version I referenced, since they all seem to relate to improper or old version flashing, but it doesn't really matter because the answer to all of them is the same... Reflash the proper version making sure each steps results in an OKAY.
If I am way off base, then it is likely a hardware problem.
Click to expand...
Click to collapse
Well, first off thanks a lot for your help. I had installed that particular version, though it wasn't the one currently installed. But I followed all the instructions and steps and got success writes for all and it booted up but didn't recognize any wifi networks and i tried to toggle on the wifi and same as before. Nothing happens. Wifi simply won't turn on. Same for bluetooth. Looking more like a HW problem isn't it?
vijn said:
Well, first off thanks a lot for your help. I had installed that particular version, though it wasn't the one currently installed. But I followed all the instructions and steps and got success writes for all and it booted up but didn't recognize any wifi networks and i tried to toggle on the wifi and same as before. Nothing happens. Wifi simply won't turn on. Same for bluetooth. Looking more like a HW problem isn't it?
Click to expand...
Click to collapse
I mean I know HW can die at any time, and maybe it was already dying from before which caused the initial issues when I got the phone, but I just have this sneaking suspicion that it's not HW related. I can't shake that feeling. But every SW based solution I try doesn't seem to do the trick.
acejavelin said:
I could explain most of the issues individually you are seeing, unless you are already using the specific version I referenced, since they all seem to relate to improper or old version flashing, but it doesn't really matter because the answer to all of them is the same... Reflash the proper version making sure each steps results in an OKAY.
Click to expand...
Click to collapse
Actually when u have a chance, I'd love this. Been rooting, modding my phones for years but I've never gone past a certain level of understanding. I'm not by nature a code guy though I have enjoyed playing around with custom roms and stuff. Anyway, ya, no pressure and my priority is to see if I can get this fixed or should just send it back, but if you do have time afterwards, would love to know what the deal is.
Still hoping someone can help me out with this. Any ideas? I'd really appreciate it.
vijn said:
Still hoping someone can help me out with this. Any ideas? I'd really appreciate it.
Click to expand...
Click to collapse
us the restore to stock tool, then install twrp and flash trupure and without booting flash the updated modem
unitz0mbie said:
us the restore to stock tool, then install twrp and flash trupure and without booting flash the updated modem
Click to expand...
Click to collapse
Hmm. Definitely willing to try that. You wouldn't happen to have links to Trupure and the updated modem would you? And the Restore to stock tool is this I assume: CLARK_RETUS_5.1.1_LPH23.116-18_cid9_subsidy-DEFAULT_CFC.xml_SHAWN5162. Not sure what Trupure is. It's a custom ROM?
vijn said:
Hmm. Definitely willing to try that. You wouldn't happen to have links to Trupure and the updated modem would you? And the Restore to stock tool is this I assume: CLARK_RETUS_5.1.1_LPH23.116-18_cid9_subsidy-DEFAULT_CFC.xml_SHAWN5162. Not sure what Trupure is. It's a custom ROM?
Click to expand...
Click to collapse
https://forum.xda-developers.com/moto-x-style/development/rom-trupurex-fast-smooth-t3237155
scroll down u will find a link for a modem, and u just flash it aswell
trick is to to flash the rom and modem without booting. if u only boot rom u will no wifi/bt etc
unitz0mbie said:
https://forum.xda-developers.com/moto-x-style/development/rom-trupurex-fast-smooth-t3237155
scroll down u will find a link for a modem, and u just flash it aswell
trick is to to flash the rom and modem without booting. if u only boot rom u will no wifi/bt etc
Click to expand...
Click to collapse
That's so weird. Never heard of that before but will definitely try it. Thanks a lot.
unitz0mbie said:
https://forum.xda-developers.com/moto-x-style/development/rom-trupurex-fast-smooth-t3237155
scroll down u will find a link for a modem, and u just flash it aswell
trick is to to flash the rom and modem without booting. if u only boot rom u will no wifi/bt etc
Click to expand...
Click to collapse
And Trupure? That's a ROM I assume. Know where I can find that? I could research it obviously, but figured there's likely a couple different versions of it. Would rather get the one you recommend. - nevermind. I see that the link you provided was for trupure. Thanks a lot. Will let you know how it goes.
unitz0mbie said:
https://forum.xda-developers.com/moto-x-style/development/rom-trupurex-fast-smooth-t3237155
scroll down u will find a link for a modem, and u just flash it aswell
trick is to to flash the rom and modem without booting. if u only boot rom u will no wifi/bt etc
Click to expand...
Click to collapse
The thing is, I'm on 6.0. Secondly my TWRP keeps getting deleted. And I just tried flashing twrp again and now I'm getting this: sending 'recovery' (34434 KB)...
OKAY [ 0.753s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.773s
Not sure how to proceed. Not much I can do without a working recovery. Any ideas?
vijn said:
That's so weird. Never heard of that before but will definitely try it. Thanks a lot.
Click to expand...
Click to collapse
no problem, if u still have no bt u can find the specific files u need to flash
---------- Post added at 11:41 PM ---------- Previous post was at 11:39 PM ----------
vijn said:
The thing is, I'm on 6.0. Secondly my TWRP keeps getting deleted. And I just tried flashing twrp again and now I'm getting this: sending 'recovery' (34434 KB)...
OKAY [ 0.753s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.773s
Not sure how to proceed. Not much I can do without a working recovery. Any ideas?
Click to expand...
Click to collapse
what version of twrp are u using
---------- Post added at 11:43 PM ---------- Previous post was at 11:41 PM ----------
vijn said:
The thing is, I'm on 6.0. Secondly my TWRP keeps getting deleted. And I just tried flashing twrp again and now I'm getting this: sending 'recovery' (34434 KB)...
OKAY [ 0.753s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.773s
Not sure how to proceed. Not much I can do without a working recovery. Any ideas?
Click to expand...
Click to collapse
try using the restore to stock tool, it will remove twrp
and then u can reflash twrp
unitz0mbie said:
no problem, if u still have no bt u can find the specific files u need to flash
---------- Post added at 11:41 PM ---------- Previous post was at 11:39 PM ----------
what version of twrp are u using
Click to expand...
Click to collapse
3.0.2 i think. can't really check but i think that's what i remember from the last time i loaded it
Here's the thing, there seems to be a consistent issue writing to the boot partition and TWRP never lasts. I don't know all that much about this but I feel as though there's a part of the software that is constantly being deleted/overwritten and that may explain why the modem never stays and twrp never stays. Does that make any sense?
The return to stock tool gives the following 2 errors:
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.378s
and
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 149.569s
Obviously the second error is the end of the process. Can't go any further if it can't write the system. Super confused. Every time I install a new ROM another issue pops up.
unitz0mbie said:
no problem, if u still have no bt u can find the specific files u need to flash
---------- Post added at 11:41 PM ---------- Previous post was at 11:39 PM ----------
what version of twrp are u using
---------- Post added at 11:43 PM ---------- Previous post was at 11:41 PM ----------
try using the restore to stock tool, it will remove twrp
and then u can reflash twrp
Click to expand...
Click to collapse
Managed to get the restore to stock working. Restarted bootloader. Tried to flash twrp, and same error: writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.779s
vijn said:
Managed to get the restore to stock working. Restarted bootloader. Tried to flash twrp, and same error: writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.779s
Click to expand...
Click to collapse
is your bootloader locked?
unitz0mbie said:
is your bootloader locked?
Click to expand...
Click to collapse
to be honest, I don't even know any more. I've locked and unlocked it a bunch of times. Some tools I've used automatically lock or unlock it. At this point i just tried to unlock is using my key and got the following error: error: Command length (142) exceeds maximum size (64). So, ya, i have no idea what's going on. The bootloader page says device:locked, but the prebootloader page says bootloader unlocked.
unitz0mbie said:
is your bootloader locked?
Click to expand...
Click to collapse
I have to step away for a couple hours. I will be back. But regardless of how this goes, I just wanted to say thanks for trying to help with this stuff. I've never had so many issues with a phone before. My previous ones would occasionally give me some headaches, but not to this extent. Anyway, hopefully you'll still be around when i get back or will have some other recommendations.
sounds like your BL is locked man.
TWRP thread here
https://forum.xda-developers.com/u11/development/recovery-twrp-touch-recovery-t3617028
I clone the repo from @Captain_Throwback and built TWRP recovery for U11 (ocndugl).
It can work well but have some issue with OTG function and touch not work while boot into TWRP (press power button and unlock lockscreen could get touch back to work).
#built with ocndugl kernel, it may not boot on ocnuhl or ocndtwl variant
#version 1
twrp-3.1.1-0-ocn_TEST.img
https://www.androidfilehost.com/?fid=817550096634770756
#version 2
I fix the external_sd and otg issues but USB function still not work.
twrp-3.1.1-0-ocn_TEST_2.img
https://www.androidfilehost.com/?fid=817550096634772885
Well, when you create device files without a device and can't test what you build, you end up with a TWRP that isn't fully functional...
If I'm able to get one, I will certainly do my best to work out any of the issues and make sure the device gets official TWRP support. Thanks for testing my device tree.
Captain_Throwback said:
Well, when you create device files without a device and can't test what you build, you end up with a TWRP that isn't fully functional...
If I'm able to get one, I will certainly do my best to work out any of the issues and make sure the device gets official TWRP support. Thanks for testing my device tree.
Click to expand...
Click to collapse
Plz read the thread carefully. He lives in Taiwan and U11 is selling there for a couple of days, there are many user reviews on TW forums already. Next place comes to Hong Kong around 5/6th June and I pre-ordered an U11 6+128GB. Finger crossed.
TheEndHK said:
Plz read the thread carefully. He lives in Taiwan and U11 is selling there for a couple of days, there are many user reviews on TW forums already. Next place comes to Hong Kong around 5/6th June and I pre-ordered an U11 6+128GB. Finger crossed.
Click to expand...
Click to collapse
well, there is no information about that he lives in taiwan or not. so no need to read it carefully
Captain_Throwback said:
Well, when you create device files without a device and can't test what you build, you end up with a TWRP that isn't fully functional...
If I'm able to get one, I will certainly do my best to work out any of the issues and make sure the device gets official TWRP support. Thanks for testing my device tree.
Click to expand...
Click to collapse
Hope you could get one and maintain this device.
I'm still a noob with this :laugh:
Sent from my HTC One M9 using XDA Labs
DeeZZ_NuuZZ said:
well, there is no information about that he lives in taiwan or not. so no need to read it carefully
Click to expand...
Click to collapse
His home country stated Taiwan
Sent from my LG-D855 using XDA Free mobile app
TheEndHK said:
His home country stated Taiwan
Sent from my LG-D855 using XDA Free mobile app
Click to expand...
Click to collapse
yea saw that now, because it wasn't visible cause he's OP. didn't even knew taiwan sells it earlier, just remembered in EU it solds from first june I think
DeeZZ_NuuZZ said:
yea saw that now, because it wasn't visible cause he's OP. didn't even knew taiwan sells it earlier, just remembered in EU it solds from first june I think
Click to expand...
Click to collapse
No offense indeed and thanks Captain_Throwback for his hard working on HTC. In my experiences, HTC guys on xda board are usually nice and helpful, mostly better than those who I met on sony, samsung, lg xda board.
I've sent a pull request to https://github.com/CaptainThrowback/android_device_htc_ocn that fixes the sd card and screen not responding at first boot issues. The usb one I'll look at later, need to do some real life stuff for a bit
I expect the problem is in init.recovery.usb.rc as it sets mtp,adb
One thing though... whilst I can fastboot boot recovery.img I can't flash recovery with an unlocked bootloader but S-ON.
$ fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (34772 KB)...
OKAY [ 0.778s]
writing 'recovery'...
FAILED (remote: Not allowed on PRODUCTION device)
finished. total time: 0.778s
Flinny said:
I've sent a pull request to https://github.com/CaptainThrowback/android_device_htc_ocn that fixes the sd card and screen not responding at first boot issues. The usb one I'll look at later, need to do some real life stuff for a bit
I expect the problem is in init.recovery.usb.rc as it sets mtp,adb
One thing though... whilst I can fastboot boot recovery.img I can't flash recovery with an unlocked bootloader but S-ON.
$ fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (34772 KB)...
OKAY [ 0.778s]
writing 'recovery'...
FAILED (remote: Not allowed on PRODUCTION device)
finished. total time: 0.778s
Click to expand...
Click to collapse
interesting...looks like we'll need s-off sooner than later... when u fastboot boot it, is twrp still functional?
OMJ said:
interesting...looks like we'll need s-off sooner than later... when u fastboot boot it, is twrp still functional?
Click to expand...
Click to collapse
Yeah, backups to internal and sdcard is as far as I've gone. I might give flashing my SlimRoms build a go later.. or maybe I'll see if my built ramdisk with a few bootclass path alterations for stock boots first
I also got TWRP compiled and running, stuck at MTP and USB Mass storage too.
BTW, I rooted my device before flashing any custom recovery... using something about to be released in the Magisk forum
Guess I should open a TWRP thread with my mostly working version now that we have a working kernel . We can continue working on MTP/UMS, though I suspect MTP will require a patch or two in TWRP upstream to add support for configfs. I think fixing UMS will require kernel source.
Haha guys, I figured out the way to fix both UMS and MTP. Yay!
I provided the info to Captain, and him, nkk71 and I are working on it now
topjohnwu said:
Haha guys, I figured out the way to fix both UMS and MTP. Yay!
I provided the info to Captain, and him, nkk71 and I are working on it now
Click to expand...
Click to collapse
nice!
topjohnwu said:
Haha guys, I figured out the way to fix both UMS and MTP. Yay!
I provided the info to Captain, and him, nkk71 and I are working on it now
Click to expand...
Click to collapse
That's awesome!!
Flinny said:
I've sent a pull request to https://github.com/CaptainThrowback/android_device_htc_ocn that fixes the sd card and screen not responding at first boot issues. The usb one I'll look at later, need to do some real life stuff for a bit
I expect the problem is in init.recovery.usb.rc as it sets mtp,adb
One thing though... whilst I can fastboot boot recovery.img I can't flash recovery with an unlocked bootloader but S-ON.
$ fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (34772 KB)...
OKAY [ 0.778s]
writing 'recovery'...
FAILED (remote: Not allowed on PRODUCTION device)
finished. total time: 0.778s
Click to expand...
Click to collapse
BTW, I figured out that you must be flashing recovery in fastboot mode.
Boot into download mode, then you can flash the recovery without an issue
(reboot with power button down, or adb reboot download)
Interesting, that's new my last phone was a m9 :/
TWRP thread is up. Thanks @Flinny and @topjohnwu for helping work out the issues with TWRP!
Still hoping to be able to get my hands on one so I can maintain for it properly .
Captain_Throwback said:
TWRP thread is up. Thanks @Flinny and @topjohnwu for helping work out the issues with TWRP!
Still hoping to be able to get my hands on one so I can maintain for it properly .
Click to expand...
Click to collapse
I missed the m10.. after getting the m7/m8/m9 but I have to say I'm REALLY enjoying the u11 everything is just INSTANT.
I'm trying to unlock phone’s bootloader using
Code:
fastboot flashing unlock
, but getting error message:
Code:
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.021s
Checked fastboot devices command and it found my device connected.
I do not remember exactly, but think that USB debugging is off.
It's a phone with bootloop issue, so cannot get into recovery menu also.
Apologize is if it was already discussed.
jorgen.bumajnikov said:
I'm trying to unlock phone’s bootloader using
Code:
fastboot flashing unlock
, but getting error message:
Code:
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.021s
Checked fastboot devices command and it found my device connected.
I do not remember exactly, but think that USB debugging is off.
It's a phone with bootloop issue, so cannot get into recovery menu also.
Apologize is if it was already discussed.
Click to expand...
Click to collapse
Try this https://www.xda-developers.com/nexus-6p-bootloop-fix/
Sent from my Nexus 6P using Tapatalk
Minh Dao said:
Try this https://www.xda-developers.com/nexus-6p-bootloop-fix/
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Thanks, I saw this post and was trying to follow steps described there, but 9 steps is about unlocking bootloader and I cannot pass it...
Both OEM unlocking and USB debugging need to be enabled in Settings/Developer options before the bootloader can be unlocked.
redduc900 said:
Both OEM unlocking and USB debugging need to be enabled in Settings/Developer options before the bootloader can be unlocked.
Click to expand...
Click to collapse
in post I mention that it's phone with bootloop issue
And I told you why you can't unlock the bootloader.
redduc900 said:
And I told you why you can't unlock the bootloader.
Click to expand...
Click to collapse
so that's it - no way to make it work again at all? (
I tried this but I couldn't make it work.
rootmygalaxy.net/unlock-bootloader-on-huawei-devices/
which leads to
emui.huawei.com/en/plugin/unlock/detail
but no matter how hard I try, I keep getting:
"Please make sure the verification code and model number are correct. If your device has multiple IMEIs or MEIDs, please try another IMEI or MEID."
Try enabling OEM unlocking in developer options
Unfortunately can't when it's stuck bootlooping.
bcurran3 said:
Unfortunately can't when it's stuck bootlooping.
Click to expand...
Click to collapse
Follow the thread below, same one as before. You need to stick with this until it works.
https://forum.xda-developers.com/showthread.php?t=3640279
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Follow the thread below, same one as before. You need to stick with this until it works.
https://forum.xda-developers.com/showthread.php?t=3640279
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thanks. Yeah, I tried the freezer trick. In fact I put it in there and forgot about it for a week! HA! Didn't work. I'll need to try the hairdryer trick.
I'm REALLY hoping Google responds to the boot.img signature files request....that would make life so much simpler. I'm probably going to shelve this project for the 4th or 5th time and wait a few weeks. (I've been dealing with this since Feb or March.)
I did put in another call to Huawei today. The next available representative was nice but told me that Huawei global unlocks the bootloader for people in China but not the US. I had him open a case to get the bootloader unlock code and pass it up the chain. I doubt it will result in anything...but at least the request is officially in.
OP did you fix the boot looping issue? I am in the exact same spot - my phone is stuck in boot loop and my OEM is locked too
draxz said:
OP did you fix the boot looping issue? I am in the exact same spot - my phone is stuck in boot loop and my OEM is locked too
Click to expand...
Click to collapse
I just fixed my phone and thought I would post my method:
For the people with boot loader locked (You CANNOT do anything with it being locked) I just revived my phone:
You need to heat the phone by using a blow drier for about 5-10 mins while in boot loop - in my case I don't have a blow drier so I turned the stove to medium heat and kept the phone about 10 centimeters above the heat. After 10 mins the phone miraculously booted up and went to "Setup as new phone" (I had wiped the device earlier) after setting it up, I immediately went into the setting to unlock OEM and after 15 mins the phone went into the boot loop again. I followed the instructions on this page https://www.xda-developers.com/nexus-6p-bootloop-fix/, a huge thank you to XCnathan32 and voila the phone works. Thank you XCnathan32 and other, please thank him by clicking the thank you button on his page or by making a donation as a gift.
I wish I was having luck.
Over the past two weeks we've had multiple 100+ degree days in Los Angeles. I threw my 6p on the charger in my OUTSIDE office. The phone got hot as hell. I tried for days to get it to boot up with no joy. I did get the NO COMMAND screen a couple times. One time I actually got to it fast enough to interact and hit the right keys to go and wipe it again. (I wiped it months ago too.) One time I accidently hit install update from SD card (always makes me laugh as there is no SD card) and I think it said it was installing the update from the SD card (again I laughed) but my guess is that's just the default graphic to display from the menu choice even if it doesn't do anything.
Anyways, for 3-4 days in 103-111 degree heat I tried for multiple multiple hours. The phone would never boot to the setup screen for me to go and turn off the OEM unlocking. I thought maybe the cores were still going full bore since it was sitting on the charger and I tried pulling it off a few times...but the battery was never charged enough to do anything.
I'm still at a loss.
Any new developments or suggestions?
unlocked oem problem. help!
I tried everything. Heating. Draining. Freezing. Nothing works for me. I just need to unlock it so I can fix the bootloop issue. I badly need some help here guys. Thank you.
aphrodirish said:
I tried everything. Heating. Draining. Freezing. Nothing works for me. I just need to unlock it so I can fix the bootloop issue. I badly need some help here guys. Thank you.
Click to expand...
Click to collapse
If you bought your Nexus 6P via Google Store you can get a New Google Pixle XL even after the 1 Year device Guarantee
maybe your lucky enough
reddit.com/r/Nexus6P/comments/6y1tm2/official_6p_battery_shutdownbootloop_rma_thread
bcurran3 said:
I'm still at a loss. Any new developments or suggestions?
Click to expand...
Click to collapse
Get a good blow dryer or heat gun? A typical blow dryer will only reach ~140F on a good day. A decent heatgun will start around ~500F and go over 1000F. You're supposed to start with the device bootlooping and apply heat until the phone boots. My guess is you are not hot enough and/or not getting the heat to the right area on the back of the phone. Bear in mind this will just give you enough time to get into Dev Settings and toggle OEM Unlock so you can unlock your bootloader and flash a custom kernel like EX.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Update:
Based on "Google is replacing defective Nexus 6P units with Pixel XLs, but only in North America"
https://www.phonearena.com/news/Goo...h-Pixel-XLs-but-only-in-North-America_id98059
Just got off the phone with Google (10 hours ago) and confirmed they are replacing my dead/looping Nexus 6P out of warranty and swapping with a Pixel XL. It took me SIX MONTHS to get this resolved. I'm not happy about the time frame, but I guess I'm pseudo-satisfied with the end result.
For those who attempt a replacement, the KEY WORDS that seemed to make the customer service rep take notice was that mine started bootlooping after installing the 7.1.2 beta sometime in March. This is where her ears perked up and she started two "escalations" to get approval for "extend warranty" and replace my phone. Hope this helps you out.
The irony of this is, I'm going to give the Pixel XL to my wife, continue using my LG V20 for the moment, and try to determine if I want to spend the bucks on a Pixel 2 XL or a LG V30 later this year.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Try this
Try finding the OEM unlock code for your specific mobile from Huawei customer service site