Related
Hey here goes my nexus 7 grouper has some how got corrupted and the only thing that is still working is fastboot, However the usual recovery using the google stock roms i ether get signature mismatch or unknown error code (really useful error code).
Currently running bootloader 4.23 and was using stock android 4.4.3 before it all went oh so wrong.
I have tried flashing it back to stock with the nexus root toolkit and the flash batch file provided by google and both have failed.
Is there a way to force a flash to ignore all signatures and i will go back to an earlier rom from google that worked properly?
or do i need a new tablet as Asus support has been less than useful?
Cheers
Support
ScoTTisH-GingeR said:
Hey here goes my nexus 7 grouper has some how got corrupted and the only thing that is still working is fastboot, However the usual recovery using the google stock roms i ether get signature mismatch or unknown error code (really useful error code).
Currently running bootloader 4.23 and was using stock android 4.4.3 before it all went oh so wrong.
I have tried flashing it back to stock with the nexus root toolkit and the flash batch file provided by google and both have failed.
Is there a way to force a flash to ignore all signatures and i will go back to an earlier rom from google that worked properly?
or do i need a new tablet as Asus support has been less than useful?
Cheers
Click to expand...
Click to collapse
Hello,
Hvae you tried flashing a recovery though fastboot? Once you have done this you should be able to sideload a new rom and BAM your done.
See here for fastboot flashing a new recovery: http://teamw.in/project/twrp2/103
See here for sideloading in recovery: http://teamw.in/ADBSideload
[email protected] said:
Hello,
Hvae you tried flashing a recovery though fastboot? Once you have done this you should be able to sideload a new rom and BAM your done.
See here for fastboot flashing a new recovery
See here for sideloading in recovery:
Hey Scott cheers for the reply here is the result of the attempting to flash twrp.
C:\nexus\4.4.4>fastboot flash recovery openrecovery-twrp-2.7.1.1-grouper.img
sending 'recovery' (8502 KB)...
OKAY [ 1.039s]
writing 'recovery'...
FAILED (remote: (FileWriteFailed))
finished. total time: 3.863s
Any more ideas or am i binning my nexus?
Click to expand...
Click to collapse
ScoTTisH-GingeR said:
Hey here goes my nexus 7 grouper has some how got corrupted and the only thing that is still working is fastboot, However the usual recovery using the google stock roms i ether get signature mismatch or unknown error code (really useful error code).
Currently running bootloader 4.23 and was using stock android 4.4.3 before it all went oh so wrong.
I have tried flashing it back to stock with the nexus root toolkit and the flash batch file provided by google and both have failed.
Hello,
My August 2012 Nexus 7 got same issue.
Boot loop up to animated circles or Android update.
Rooted. CWM recovery. Stock ROM 4.4.3
General remark/ the device was getting really slow in spite of regular use of Lagfix.
Fastboot OK. That is in fact the only way to power off the device.
Wipe Data / Factory reset had no effect on bootloop.
Errors trying to flash official Factory image through adb: example " recovery.sig files not found". I tried to flash them individually
I tried the Nexus Toolkit: Error trying to load a factory image. Error trying to return to stock recovery.
I suspect a memory issue.
Finally I just return this morning the device to ASUS France, after requesting a Return Agreement.
No more warranty; I wonder if the resulting cost are worst this action if tablet is not reparable.
I am really upset.
Click to expand...
Click to collapse
Hello,
Have you tried the steps to flash a system imagem, all you need is to have access to fastboot. Please visit: https://developers.google.com/android/nexus/images for instructions on how to do this.
I hope these steps help, If you need further assistance you can email me at [email protected]. Be sure to place case number N140811561 in the subject line for reference.
Regards,
Scott
ASUS Customer Loyalty
Motherboard issue
[email protected] said:
Hello,
Have you tried the steps to flash a system imagem, all you need is to have access to fastboot. Please visit: https://developers.google.com/android/nexus/images for instructions on how to do this.
I hope these steps help, If you need further assistance you can email me at [email protected]. Be sure to place case number N140811561 in the subject line for reference.
Regards,
Scott
ASUS Customer Loyalty
Click to expand...
Click to collapse
-----------------------------------------------------------------------------------------------------------
I just got the answer from Ename, ASUS repair contractor in France.
Motherboard got problems. Need replacement.
Total cost 192 €.
Basically I have better to buy a new one.
That is really bitter after just 2 years .....!!!!!
Is the 2013 model more robust?
marcelin99 said:
-----------------------------------------------------------------------------------------------------------
I just got the answer from Ename, ASUS repair contractor in France.
Motherboard got problems. Need replacement.
Total cost 192 €.
Basically I have better to buy a new one.
That is really bitter after just 2 years .....!!!!!
Is the 2013 model more robust?
Click to expand...
Click to collapse
Hello,
The Nexus 7 21013 is slightly lighter, has a better resolution (1920 x 1200 pixels), adds a rear camera and sports the Qualcomm Snapdragon S4 Pro APQ8064 with 2048 MB RAM. So it is a nice increase in the specs. With a your repair cost of 192 it might be better to consider upgrading your Nexus experience. If you need further support feel free to email me at [email protected] with case number in the N140820223 subject line.
Regards,
Scott
ASUS Customer Loyalty
Is there a way to remove the warning on boot, after the bootloader has been unlocked. Thanks
ShaunWinSC said:
Is there a way to remove the warning on boot, after the bootloader has been unlocked. Thanks
Click to expand...
Click to collapse
No, but why does it matter? It will go away if/when you re-lock it for whatever reason.
just4747 said:
No, but why does it matter? It will go away if/when you re-lock it for whatever reason.
Click to expand...
Click to collapse
It really doesn't matter. I just would like a cleaner boot cycle. Plus I know the MXPE is able to remove this warning.
There is no way around it right now. I had a kernel on my N6 that didn't show the message so it could come sooner or later, but it doesn't hurt anything. It's only a warn. There are three stages, I think; yellow, orange and red.
fury683 said:
There is no way around it right now. I had a kernel on my N6 that didn't show the message so it could come sooner or later, but it doesn't hurt anything. It's only a warn. There are three stages, I think; yellow, orange and red.
Click to expand...
Click to collapse
what do you mean? My warning is in orange.
collinjm01 said:
what do you mean? My warning is in orange.
Click to expand...
Click to collapse
http://www.androidauthority.com/verified-boot-warnings-in-android-6-0-marshmallow-650368/
ShaunWinSC said:
Is there a way to remove the warning on boot, after the bootloader has been unlocked. Thanks
Click to expand...
Click to collapse
.
After reading info on Android Security in this link you should know more about Verified Boot.
.
http://source.android.com/devices/tech/security/verifiedboot/verified-boot.html
.
.
Techie info about SafetyNet anti-tamper detection here.
https://koz.io/inside-safetynet/
.
Interesting reading about what info Google is now able to pull from youe device.
It's an eyesore no doubt about it but I hardly reboot so it's somewhat bearable.
^^^ why did you bump a thread that died November 11 :lol:
Someone found a way to get rid of this message a while back on the 5X. It worked perfectly for me on that phone. I imagine the method would be the same on the 6P. If someone wants to give the img files a shot from the below link and report back, it might be exactly what we are looking for.
http://forum.xda-developers.com/showpost.php?p=63826602&postcount=7
The command to flash the file is:
fastboot flash imgdata imgdata.img (replace "imgdata.img" with the actual name of the img file)
I'd test it myself but I JUST setup my brand new 6P and don't feel like spending the evening troubleshooting if something goes wrong.
sn0warmy said:
Someone found a way to get rid of this message a while back on the 5X. It worked perfectly for me on that phone. I imagine the method would be the same on the 6P. If someone wants to give the img files a shot from the below link and report back, it might be exactly what we are looking for.
http://forum.xda-developers.com/showpost.php?p=63826602&postcount=7
The command to flash the file is:
fastboot flash imgdata imgdata.img (replace "imgdata.img" with the actual name of the img file)
I'd test it myself but I JUST setup my brand new 6P and don't feel like spending the evening troubleshooting if something goes wrong.
Click to expand...
Click to collapse
I happen to be in the middle of a replacement process for my 6P and still have the old and new devices. I just finished using one of those img files to get rid of my fiance's boot warning on her 5X and decided to try it out on the 6P I'm sending back to Google. Unfortunately, it looks like it wouldn't flash at all. After attempting to write the file, I get an error that reads "FAILED (remote: permission denied!)". I also only have the bootloader unlocked and no other modifications, so I'm going to mess some stuff up and report back.
Edit 1: A modified system image did not make a difference as it displayed the same error message. I'm going to back up the rest of my stuff I need off the phone and try to flash one of the zips instead in TWRP.
Edit 2: Looks like flashing in TWRP was a no-go as well. I don't have the unlocked bootloader warning anymore, but the red corrupted device warning is still there. I guess it's not possible for now.
j.bruha said:
I happen to be in the middle of a replacement process for my 6P and still have the old and new devices. I just finished using one of those img files to get rid of my fiance's boot warning on her 5X and decided to try it out on the 6P I'm sending back to Google. Unfortunately, it looks like it wouldn't flash at all. After attempting to write the file, I get an error that reads "FAILED (remote: permission denied!)". I also only have the bootloader unlocked and no other modifications, so I'm going to mess some stuff up and report back.
Click to expand...
Click to collapse
Thanks for this update! Will look forward to seeing you post back...while it's not life or death to me it is a rather silly and pointless message by the 100th time I've seen it lol so I would disable it in a heartbeat if I could
just4747 said:
No, but why does it matter? It will go away if/when you re-lock it for whatever reason.
Click to expand...
Click to collapse
No? How about Ya there should be maybe the cause they have a remove mod for the 5x over in the 5x XDA side.
Maybe the same process cause I wondered this question myself
Sent from my Nexus 6P using XDA Free mobile app
j.bruha said:
I happen to be in the middle of a replacement process for my 6P and still have the old and new devices. I just finished using one of those img files to get rid of my fiance's boot warning on her 5X and decided to try it out on the 6P I'm sending back to Google. Unfortunately, it looks like it wouldn't flash at all. After attempting to write the file, I get an error that reads "FAILED (remote: permission denied!)". I also only have the bootloader unlocked and no other modifications, so I'm going to mess some stuff up and report back.
Edit 1: A modified system image did not make a difference as it displayed the same error message. I'm going to back up the rest of my stuff I need off the phone and try to flash one of the zips instead in TWRP.
Edit 2: Looks like flashing in TWRP was a no-go as well. I don't have the unlocked bootloader warning anymore, but the red corrupted device warning is still there. I guess it's not possible for now.
Click to expand...
Click to collapse
The /imgdata partition is commented out in fstab in the boot.img. If I modify the boot.img, would you be willing to flash the boot.img and then try one of the /imgdata modification files once more?
In case you are willing, here is the boot image with /imgdata uncommented: http://www.mediafire.com/download/cwpfkjgqyw9bwcx/Stock_NoEncrypt_uncomment-imgdata_Kernel_6.0.1.zip
MD5Sum: 94f9bc6b01f7294b8835d9f28b7c6ed3
You can flash it in TWRP, or extract the boot.img from the zip and flash it with fastboot in bootloader mode.
You need a custom bootloader to remove this. No kernel will take care of it for you. The warning message is within the bootloader.img. The 5x and the 6p are completely different phones. Regardless of the fact that they are both Nexus devices. What works for one will not necessarily work for the other.
Sent from my XT1080 using Tapatalk
Yeah, I've been quickly discovering that over the past 2 days. Very different phones indeed.
bouchigo said:
The /imgdata partition is commented out in fstab in the boot.img. If I modify the boot.img, would you be willing to flash the boot.img and then try one of the /imgdata modification files once more?
In case you are willing, here is the boot image with /imgdata uncommented: http://www.mediafire.com/download/cwpfkjgqyw9bwcx/Stock_NoEncrypt_uncomment-imgdata_Kernel_6.0.1.zip
MD5Sum: 94f9bc6b01f7294b8835d9f28b7c6ed3
You can flash it in TWRP, or extract the boot.img from the zip and flash it with fastboot in bootloader mode.
Click to expand...
Click to collapse
Just a side note for all who will wonder or ask for the hell of it I tried
Nexus 5x mod file to remove this on a 6p and it doesnt ..was worth a shot.But it did when I had the 5x
Sent from my Nexus 6P using XDA Free mobile app
androidddaaron said:
Just a side note for all who will wonder or ask for the hell of it I tried
Nexus 5x mod file to remove this on a 6p and it doesnt ..was worth a shot.But it did when I had the 5x
Sent from my Nexus 6P using XDA Free mobile app
Click to expand...
Click to collapse
Yeah, I tried it earlier in the morning, and no go. I believe the /imgdata partition does not exist in the N6P, that's most likely why it was commented out from fstab.
Sent from my Nexus 6P using Tapatalk
SyCreed said:
hey guys i don't want to open a new topic cuz i think it's related here -
If i go back to fully stock, and re-lock the bootloader + factory reset after those operation, no one actually can know if the device was rooted or unlocked right?
Click to expand...
Click to collapse
Correct, if you do that it will be like out of the box.
Hello,
Bought a Nexus 6P the other day and now attempting to install CM13, latest official snapshot. Of course, I ran into issues., and I am in dire need of help.
I unlocked the bootloader via Fastboot. Then installed the latest TWRP, also using Fastboot. All fine so far. Then I tried flashing CM13, which first failed because I missed to wipe the data/cache. I realised my mistake, re-did it and successfully flashed CM13.
The installation process was successful, yet when I boot the phone up and it finishes loading CM, I get the following error message:
"Android-system
An internal problem has occurred. Contact the manufacturer if you want more information."
Why is this happening? And more importantly, how do I fix it?
I did try and ignore the warning and proceeded to install OpenGAPPS from TWRP. As soon as CM loads up again however, there is an infinite stream of Google Play Service and "first time setup" crash messages, making the phone unusable.
On a related note. The guide at https://wiki.cyanogenmod.org/w/Install_CM_for_angler tells me to "update the vendor.img", but it never tells me how I figure out which Build ID I need for my version of CM13. The guide hints at MTC19V, but I am not sure if this is right. I did try flashing this, but nothing changed.
Please advice, I am stuck.
First off you need to figure out what Vendor you need, this can be done by going to about phone/ settings and looking at what security patch level you are on. The latest is August and that would be vendor image MTC20F. you can google search or go to androidfilehost.com to download that or any other vendor image.
To flash you boot into TWRP and choose install and then choose install image in the bottom right hand corner then you choose the file and select Vendor image, then flash and you're all set.
Here's a lazy link for the last 2 vendor files: http://download.dirtyunicorns.com/files/misc/vendor_images/angler/
You need to flash CM13 and Gapps before booting and not separately.
Like the above post you need to check what vendor you need.
Wickidmasshole said:
First off you need to figure out what Vendor you need, this can be done by going to about phone/ settings and looking at what security patch level you are on. The latest is August and that would be vendor image MTC20F. you can google search or go to androidfilehost.com to download that or any other vendor image.
To flash you boot into TWRP and choose install and then choose install image in the bottom right hand corner then you choose the file and select Vendor image, then flash and you're all set.
Here's a lazy link for the last 2 vendor files: http://download.dirtyunicorns.com/files/misc/vendor_images/angler/
Click to expand...
Click to collapse
Ahh, I see. That makes sense now. Thanks!
therock3181 said:
You need to flash CM13 and Gapps before booting and not separately.
Like the above post you need to check what vendor you need.
Click to expand...
Click to collapse
Really? I didn't think it would matter. Anyways, even with this part fixed, would it not continue to claim being corrupted? I understood it as if CM itself has an issue and not GApps.
Wickidmasshole said:
First off you need to figure out what Vendor you need, this can be done by going to about phone/ settings and looking at what security patch level you are on. The latest is August and that would be vendor image MTC20F. you can google search or go to androidfilehost.com to download that or any other vendor image.
To flash you boot into TWRP and choose install and then choose install image in the bottom right hand corner then you choose the file and select Vendor image, then flash and you're all set.
Here's a lazy link for the last 2 vendor files: http://download.dirtyunicorns.com/files/misc/vendor_images/angler/
Click to expand...
Click to collapse
Actually, latest is from 2nd April. The only later builds of CM I see for this phone is Nightlies.
therock3181 said:
You need to flash CM13 and Gapps before booting and not separately.
Like the above post you need to check what vendor you need.
Click to expand...
Click to collapse
Sadly, I still get the warning once CM finishes loading. It did however get rid of the infinite crashes. Progress!
I was saying the latest available vendor.img was from august. I use DU so i don't know how far behind CM nighties are.
NodCom said:
Actually, latest is from 2nd April. The only later builds of CM I see for this phone is Nightlies.
Sadly, I still get the warning once CM finishes loading. It did however get rid of the infinite crashes. Progress!
Click to expand...
Click to collapse
The current GitHub for angler on cyanogen is showing mtc20f updated ten days ago. So if your nightly was built after that, then it would be that Vendor image.
Gizmoe said:
The current GitHub for angler on cyanogen is showing mtc20f updated ten days ago. So if your nightly was built after that, then it would be that Vendor image.
Click to expand...
Click to collapse
I am only willing to use stable builds, not nightlies.
Next time do some research before you just start flashing stuff.. especially since 5x and 6p came out Google updates every month.
So the best thing to do when you buy a new device is read and learn and i learned on both devices the best thing you can do first is flashing the latest factory images.
Also i find it strange that the first thing you flash on a nexus is cm, but that's all up to you of course. There are so many great roms out there that are way better then cm in my opinion.
Sent from my Nexus 6P using XDA-Developers mobile app
Pollie81 said:
Next time do some research before you just start flashing stuff.. especially since 5x and 6p came out Google updates every month.
So the best thing to do when you buy a new device is read and learn and i learned on both devices the best thing you can do first is flashing the latest factory images.
Also i find it strange that the first thing you flash on a nexus is cm, but that's all up to you of course. There are so many great roms out there that are way better then cm in my opinion.
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
I agree. CM was great on the N4 and N5 but not so much on the 6P
NodCom said:
I am only willing to use stable builds, not nightlies.
Click to expand...
Click to collapse
Why would I care which release you prefer? You asked how you messed up flashing CM and people responded. It's because of mismatched Vendor images. And no one seemed to know for sure which one it is so I looked for you. I've compiled CM with the right proprietary blobs and I have had no stability issues.
Just wondering if anyone has looked into this, and what it could possibly mean for our device if we could be merged. Apparently there's no need for special kernel modules, bootloader edits, or KEXEC, and I think it would be pretty cool to be able to use multi ROM to boot back and forth between stock and AOSP.
Why don't you explain what this is and provide a few links?
lafester said:
Why don't you explain what this is and provide a few links?
Click to expand...
Click to collapse
https://www.xda-developers.com/efidroid-is-a-second-stage-bootloader/
This article was the first I'd heard of it. But it does seem like it might be something easy to implement. It's basically multi ROM, but without all the requirements.
Looks interesting.
is it possible to dualboot into that one OS called sailfish or something? even ubuntu mobile?
gecko702 said:
is it possible to dualboot into that one OS called sailfish or something? even ubuntu mobile?
Click to expand...
Click to collapse
This is to make the phone able to boot two different working roms. Say, you will be able to boot stock or RR without changing roms in TWRP. It won't boot roms that haven't been ported to our phone...
This is very, very interesting. I love the thought of just using LineageOS or RR for everyday things and then just switching to stock when I want to use media and enjoy the fantastic sound.
I'm not a developer, but I'd like to help/contribute in any way possible if someone's working on bringing unofficial support to the Axon 7.
jimbo77 said:
This is to make the phone able to boot two different working roms. Say, you will be able to boot stock or RR without changing roms in TWRP. It won't boot roms that haven't been ported to our phone...
Click to expand...
Click to collapse
Very true. However, it makes ROMs easier to port and for more people to test, as then people can try them out without wiping their phone each time they want to try.
I was able to port and build right up until the last step where you generate lk.img and fastboot it to the phone. I'm running Linux inside a virtual machine and it doesn't seem to want to communicate, though adb does work.
I might try on the weekend to boot linux off a hard drive and see if it will work..
In the mean time, if someone else wants to try to build, it's really simple just follow these two guides:
https://github.com/efidroid/projectmanagement/wiki/[EFIDroid]-Getting-Started
https://github.com/efidroid/projectmanagement/wiki/[EFIDroid]-Porting-a-new-device
I tried again, but when I fastboot the generated lk.img to the phone, it just turns off instead of loading the splash screen.
I used the TWRP recovery .img for the create_device step. Maybe that's unacceptable, though it built the lk.img without error.
Anyone else trying this?
twoi said:
I tried again, but when I fastboot the generated lk.img to the phone, it just turns off instead of loading the splash screen.
I used the TWRP recovery .img for the create_device step. Maybe that's unacceptable, though it built the lk.img without error.
Anyone else trying this?
Click to expand...
Click to collapse
Did you try this fix for arm64 devices?
https://github.com/efidroid/projectmanagement/issues/89
Seems you need to dump aboot to check what's the correct address for LK to boot.
Edit: also did you try using freeza Beastmode boot.img? Probably that's better
Thanks for the reply.
I dumped aboot and replaced the address but sadly it just makes the phone reboot, I used the beastmode boot.img at the same time.
I'm a bit in over my head at this point hah, but someone in that thread had the same results..
twoi said:
Thanks for the reply.
I dumped aboot and replaced the address but sadly it just makes the phone reboot, I used the beastmode boot.img at the same time.
I'm a bit in over my head at this point hah, but someone in that thread had the same results..
Click to expand...
Click to collapse
Yeah that's he creator of Efidroid... Why don't you reply to that issue tracker and add the Axon 7 to the list of devices that don't boot because of the arm64 arch
twoi said:
Thanks for the reply.
I dumped aboot and replaced the address but sadly it just makes the phone reboot, I used the beastmode boot.img at the same time.
I'm a bit in over my head at this point hah, but someone in that thread had the same results..
Click to expand...
Click to collapse
yes you are on right track
twoi said:
Thanks for the reply.
I dumped aboot and replaced the address but sadly it just makes the phone reboot, I used the beastmode boot.img at the same time.
I'm a bit in over my head at this point hah, but someone in that thread had the same results..
Click to expand...
Click to collapse
have you replied or keep track of this
https://github.com/efidroid/projectmanagement/issues/89
the dev was asking for something
Druboo666 said:
have you replied or keep track of this
https://github.com/efidroid/projectmanagement/issues/89
the dev was asking for something
Click to expand...
Click to collapse
I'll try the suggestion of using lk_origdtb.img. I'll have to ask about his instructions to rebuild lk.img, I'm not sure how to repack it.
This might get me close http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
But this is lower level than I'm used to, I'm not sure which file(s) constitutes the ramdisk.
twoi said:
I'll try the suggestion of using lk_origdtb.img. I'll have to ask about his instructions to rebuild lk.img, I'm not sure how to repack it.
This might get me close http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
But this is lower level than I'm used to, I'm not sure which file(s) constitutes the ramdisk.
Click to expand...
Click to collapse
you should contact with the dev he may help you OP3 and A7 got same chipset so yeah it will help
I tried lk_origdtb.img and the repacked lk.img (Image.gz-dtb) but got the same results, device reboot.
I would love someone else to try this. If you have linux and coding experience at all I think you could manage building it.
twoi said:
I tried lk_origdtb.img and the repacked lk.img (Image.gz-dtb) but got the same results, device reboot.
I would love someone else to try this. If you have linux and coding experience at all I think you could manage building it.
Click to expand...
Click to collapse
you can contact @npjohnson or @m1cha with your compiled LK or boot maybe they can help
as they have fix Nexus 6P LK with no uefi boot
Requesting guidance before I brick my phone.
I currently have bootloader unlocked, twrp installed, and my nexus 6p rooted. I'm running 7.1.2. I've also changed a line in the (build.prop) provisions in order to tether free (since I am on at&t)
Basically, I'm wanting to install pure nexus. I have the custom rom file and the vendor image file.
Before I install from, I'm wondering if I need to unroot first? Also curious if how "shamu" will affect things since I'm on Angler.
Thanks!
Okay you need to stop everything you're doing and read this topic until you know what is what.
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page577
First of all, you obviously wouldn't flash a Shamu package on Angler. That's a great way to brick your phone, permanently.
Read every single step in that guide above, even if you don't think it's pertinent to what you're trying to do. Read it a second, third, fourth, fifth time until you know the steps by heart. Until you know what's next.
Also, download the correct Angler zip file and DO NOT FLASH A SHAMU ZIP ON YOUR PHONE.
help
RoyJ said:
Okay you need to stop everything you're doing and read this topic until you know what is what.
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page577
First of all, you obviously wouldn't flash a Shamu package on Angler. That's a great way to brick your phone, permanently.
Read every single step in that guide above, even if you don't think it's pertinent to what you're trying to do. Read it a second, third, fourth, fifth time until you know the steps by heart. Until you know what's next.
Also, download the correct Angler zip file and DO NOT FLASH A SHAMU ZIP ON YOUR PHONE.
Click to expand...
Click to collapse
Any help on flashing back to stock using TWRP? I unlocked the bootloader and rooted my device (never made a backup till after but still proved to be of no help as it wont work when trying to restore) lesson learned for sure. but i cant boot the device up however i still have access to twrp recovery how can i go back to stock so i can start from scratch?? :crying:
Filly2 said:
Any help on flashing back to stock using TWRP? I unlocked the bootloader and rooted my device (never made a backup till after but still proved to be of no help as it wont work when trying to restore) lesson learned for sure. but i cant boot the device up however i still have access to twrp recovery how can i go back to stock so i can start from scratch?? :crying:
Click to expand...
Click to collapse
You can follow the original advice I posted above. Read that thread I linked. It's ALL covered there. No sense in me writing everything up here when all you need to do is click the link I posted and follow the return to stock sections. There's even one for maintaining your data. Read the thread. It covers literally everything.
..
RoyJ said:
You can follow the original advice I posted above. Read that thread I linked. It's ALL covered there. No sense in me writing everything up here when all you need to do is click the link I posted and follow the return to stock sections. There's even one for maintaining your data. Read the thread. It covers literally everything.
Click to expand...
Click to collapse
Sorry I don't mean to bug man but I'm so lost. I'm trying to find what you are referring me to but I'm not finding the info I need I haven't been on here too often so this is like a pain in my rear so far. Plus I'm a very hands on kinda learner so I need some like handicapped help lol If you don't mind I don't want to pester anyone...
I was able to load pure Nexus. I didn't realize there was a pure nexus rom with Angler on it.
My main question was if I had to reverse the root. But I'm good to good now.
Rom loaded, vendor image loaded, and Google Apps loaded.