Hello!
I just finished installing Pixel Experience Plus through the guide on the PE wiki, followed it step by step.
However, after installation, I've been sitting at the Google logo with a loading bar under it for like 8 or 10 mins aprox.
The only difference to other guides and videos was that when in the PE recovery, the first line of code that appeared in the log was E:
Is there anyone with the same issue? Or a fix to this?
Thanks in advance!
The guide in question: https://wiki.pixelexperience.org/devices/sweet/install/
I had that as well. Rebooted and then it worked.
Related
Hi all,
I'm afraid this is a plea for help!
My P9 (EVA-L09) was working fine with the factory image and i rooted it and it worked fine.
I then attempted to follow the debrand guide to get Android 7 and this worked OK except i was missing the EMUI apps (camera, clock etc). So i updated to another Android 7 image (B822?) at which point i was left with no keyboard.
I then tried to flash the old firmware back on and my phone wouldn't boot.
I followed all of the DC phoenix instructions and it still wouldn't boot so i then used DC phoenix to install the factory image and this worked.
From this point i was able to install B136 and then numerous other versions upto the Android 7 one again but no keyboard once again.
The strange thing is that at this point i can no longer lock or unlock the bootloader it says wrong key, and whenever i do a factory restore i don't get the 'out of box experience' where it asks you to connect to the wifi etc.
I just want i working up to date phone, preferably on Android 7 but if not that is no problem.
Would someone that knows a bit more about android be kind enough to teamveiwer on and help me please?
Thanks
Ben
Also, i have just tried to install the current firmware from the Huawei site and this also fails, sits at 5% installing update and goes nowhere...
Sorry, to correct myself the error when trying to unlock bootloader is "remote: command not allowed"
Hey Guys,
so first of all i have a OnePlus 3T and tried to OTA the new Oreo Update. I just followed the steps from a post here, installed a customized TWRP and so on. Then i got the error, that the "package" is for OnePlus 3T and my Phone is a OnePlus 3. There was someone on the net who just removed the phone validation to install the zip File. I was really sure, that i have downloaded the right OTA File. But after rebooting i couldnt do anything.
Now i just tried to unbrick my phone with MSMDownload Tool but stuck on ChechHwID Failed! Phone: MSM8996, Image: MSM8996Pro. I think the issue is the same above. My phone thinks itself that he is a OnePlus3 instead of a 3T. What should i do? Using the repairTool for the 3 or staying at the 3T repairTool and fix it differently?
Thanks for help,
Musti222
Musti222 said:
Hey Guys,
so first of all i have a OnePlus 3T and tried to OTA the new Oreo Update. I just followed the steps from a post here, installed a customized TWRP and so on. Then i got the error, that the "package" is for OnePlus 3T and my Phone is a OnePlus 3. There was someone on the net who just removed the phone validation to install the zip File. I was really sure, that i have downloaded the right OTA File. But after rebooting i couldnt do anything.
Now i just tried to unbrick my phone with MSMDownload Tool but stuck on ChechHwID Failed! Phone: MSM8996, Image: MSM8996Pro. I think the issue is the same above. My phone thinks itself that he is a OnePlus3 instead of a 3T. What should i do? Using the repairTool for the 3 or staying at the 3T repairTool and fix it differently?
Thanks for help,
Musti222
Click to expand...
Click to collapse
Have you find any solution I am facing a similar problem?
junaid124 said:
Have you find any solution I am facing a similar problem?
Click to expand...
Click to collapse
https://mega.nz/#!Q1YnTTAT!gnLf6NEkSRy7W-WY8J0H2SmJJLzO91-vReKx7B1VVpI
TLDR; Black screen, been rooting/flashing for YEARS, I've tried all common troubleshooting procedures. Help?
EDIT: FIXED
Guide I used - HERE
My steps for Windows 10 - HERE
I was originally going to request a fix, but I managed to figure it out via a life saving Unbrick guide which you can read (link above). The process was a tad bit different for me, so for those with Windows 10, my post in that thread outlines exactly what I did step by step (link above)
OnePlus 3T running ResurrectionRemix build 03042018
Cause:
- Flashed incorrect FW (Open Beta 34) ontop of RR build 04162018
Symptons:
- Black screen
- No reaction from any button presses
- No reaction from any source (computer / outlet)
- No LED's of any kind
Special thanks to anyone involved in making such a wonderful tutorial, and the tools provided. You saved me from having to buy a new phone lol
Not sure if you're mistaken, but the latest Open Beta for the 3T is 25, not 28 nor 34. These are for the OnePlus 3. You should never flash any intended for the 3 on the 3T.
Hi guys so I bought an unlocked phone from someone and after I did a factory reset I realized that the bootloader was unlocked. and when I tried to actually figure out how to flash a ROM that would help me fix the green tint on the screen ( i never figured out how) I realized that the ROM is custom. I tried to install Whatsapp and other apps and it wouldn't work. Please help me fix the phone so I'm not stuck with an unusable phone. The build installed is coral-userdebug 11 RQ1A.201205.....xxxxxx how do I fix this? Bonus points if I can install that degreenify thing with the app/ROM found on xda
Kderant said:
Hi guys so I bought an unlocked phone from someone and after I did a factory reset I realized that the bootloader was unlocked. and when I tried to actually figure out how to flash a ROM that would help me fix the green tint on the screen ( i never figured out how) I realized that the ROM is custom. I tried to install Whatsapp and other apps and it wouldn't work. Please help me fix the phone so I'm not stuck with an unusable phone. The build installed is coral-userdebug 11 RQ1A.201205.....xxxxxx how do I fix this? Bonus points if I can install that degreenify thing with the app/ROM found on xda
Click to expand...
Click to collapse
Hey, this thread is for Google Pixel 1, that is Sailfish and you seem to have an Google Pixel 4 XL, that is a Coral. Use "https://developers.google.com/android/images" link to find the stock rom for your device along with the instructions to flash the same. Happy Flashing
Hi! I followed the official guide for Samsung Devices.
Installation
The Magic Mask for Android
topjohnwu.github.io
Here is the collection of photos I have to provide context: https://drive.google.com/drive/folders/1EzruHWAtZEmosrrr6tt9CQKpy9F-Kick?usp=sharing
Other context: I had installed LineageOS for my device following this guide (https://wiki.lineageos.org/devices/gta4xlwifi/install) previously and it worked without any issue
Okay, so. As seen in 1.png, I got to that step in the guide for Magisk. I loaded up the firmware files I had (my tablet is Wifi only so no CP firmware to load) plus the patched AP file (2.png). I hit start and it eventually returned on my pc "<OSM> All threads completed. (succeed 1 / failed 0)" as seen in 3.png. However, on my tablet, it rebooted from what you see in 4.png to what you see in 5.png.
Out of fear of having messed it up, I haven't unplugged it from my pc, nor have I closed any tools or pages I have referred to. If you have any suggestions on where I've messed up or if I have messed up elsewhere, please let me know. I am a relative novice and did follow the guide as tightly as I could, so I cannot pinpoint where I messed up alone.
There's this guide in the Tab S6 Lite forums:
https://forum.xda-developers.com/t/howto-unlock-and-root-the-galaxy-tab-s6-lite.4132289/
It's slightly different to the official instructions, so maybe try that.
Over there you can probably also find info or get help on how to fix your current predicament with the vbmeta error.