hello friends,
i unlocked my bootloader and flashed a custom Rom. i was experiencing problems and i decided to revert to stock google rom, i mistakenly locked the bootloader with twrp recovery installed and i now get the message that my phone is corrupt and cannot be trusted. The phone doesn't boot it stucksat the Google logo. I the tried unlocking but not successful,
is there any help for me? thanks in advance
Dont wanna be the bad news guy but I think you broke your device.
You can't do anything in the bootloader now. Try to do stuff in TWRP. If TWRP still functions normally we can do something.
HeroPlane said:
Dont wanna be the bad news guy but I think you broke your device.
You can't do anything in the bootloader now. Try to do stuff in TWRP. If TWRP still functions normally we can do something.
Click to expand...
Click to collapse
twrp cannot read the internal memory
Frenzy23 said:
twrp cannot read the internal memory
Click to expand...
Click to collapse
Then sorry dude, I don't know but I am sure there is a way to fix it.
Wait for more comments
Hi.
Go to:
http://www.androidbrick.com/download/unbrick-nexus-6p-angler/
And follow that guide ?
If it boots up just boot it. I face this corruption screen every day on 5X, I also have locked bootloader with TWRP onboard and no issues so far (stop talking bull**** that this will brick device, btw).
You said it can't read internal memory. What exactly it display (I assume it can't decrypt it)
Try to sideload random ROM and install it, then toggle OEM unlock.
Sent from my Nexus 5X using XDA Labs
Banan PL said:
If it boots up just boot it. I face this corruption screen every day on 5X, I also have locked bootloader with TWRP onboard and no issues so far (stop talking bull**** that this will brick device, btw).
You said it can't read internal memory. What exactly it display (I assume it can't decrypt it)
Try to sideload random ROM and install it, then toggle OEM unlock.
Sent from my Nexus 5X using XDA Labs
Click to expand...
Click to collapse
thanks
that's right twrp cant decrypt the device and also the file manager on the twrp is not able to read the files on the device, it also says no OS installed
it boots to the bootloader alright, but it stucks up on the google logo
rhaavin said:
Hi.
Go to:
http://www.androidbrick.com/download/unbrick-nexus-6p-angler/
And follow that guide
Click to expand...
Click to collapse
thanks ill give it a try and get back to you
I see no other option than full wipe and reflashing stock. So your data will be gone
Format /data in TWRP,
Reboot recovery,
Put any stock system image you have (system vendor, boot, recovery) to internal storage. (I assume you have at least one factory image on PC if not download),
Flash them in recovery (flash recovery last just in case)
Device SHOULD boot up.
Sent from my Nexus 5X using XDA Labs
I also tried to change my stock rom to custom rom. I don't know what happened, only twrp3_1_1_4Cores.img works on my device. I can install a custom rom but it doesn't boot into it. I cannot find any further informations about it. Can someone help me?
Related
Hi,
I Need help .
I have nexus 4 with stock ROM and stock recovery.
Two days after OTA update to Lollipop, the phone got stuck on boot-loop.
The problem is that on the phone i have a very important voice recording of a cop that says he will lie in court.
The court time is coming and i need that recording!
Everywhere i looked, no one has an idea how to recover a boot-loop'ed phone.
The 2 options that people recommended are:
1. RE-Flash the ROM.
Maybe it wont delete the files.
2. Wipe everything and hope that the file is recoverable with one of the software's.
A. What do you recommend?
B. Did someone try any of the recovering software's with any luck of actually recovering?
Your bootloader is locked, correct?
ashyossi said:
Hi,
I Need help .
I have nexus 4 with stock ROM and stock recovery.
Two days after OTA update to Lollipop, the phone got stuck on boot-loop.
The problem is that on the phone i have a very important voice recording of a cop that says he will lie in court.
The court time is coming and i need that recording!
Everywhere i looked, no one has an idea how to recover a boot-loop'ed phone.
The 2 options that people recommended are:
1. RE-Flash the ROM.
Maybe it wont delete the files.
2. Wipe everything and hope that the file is recoverable with one of the software's.
A. What do you recommend?
B. Did someone try any of the recovering software's with any luck of actually recovering?
Click to expand...
Click to collapse
If your bootloader is unlocked you can try flashing TWRP recovery which has a built in file manager and mtp function to copy files to computer. You can also try to "dirty flash" another lollipop rom which will not wipe the data, but may not work.
Yeah, this is the only option, however, this can only happen if his bootloader is unlocked
lolcakes203 said:
Yeah, this is the only option, however, this can only happen if his bootloader is unlocked
Click to expand...
Click to collapse
unfortunately, the bootloader is locked.
what are the chances that "Dirty Flash" wont delete the files?
and what rom should i flash? the same build or maybe try to flash kitkat insted...?
ashyossi said:
unfortunately, the bootloader is locked.
what are the chances that "Dirty Flash" wont delete the files?
and what rom should i flash? the same build or maybe try to flash kitkat insted...?
Click to expand...
Click to collapse
Unfortunately, as far as I know you can't flash any Rom's while your bootloader is locked. You need either fastboot or a custom recovery to flash a custom ROM and both need an unlocked bootloader.
theminikiller said:
Unfortunately, as far as I know you can't flash any Rom's while your bootloader is locked. You need either fastboot or a custom recovery to flash a custom ROM and both need an unlocked bootloader.
Click to expand...
Click to collapse
and flushing the same STOCK rom that i got as OTA should work or does it only work with custom ROM's?
i've looked again.
seems that the bootloader is unlocked!
so, should i flash a TWRP recovery?
ashyossi said:
i've looked again.
seems that the bootloader is unlocked!
so, should i flash a TWRP recovery?
Click to expand...
Click to collapse
Yes, after you've flashed twrp you should be able to access your files from a computer if you're booted in recovery.
soooooo.....
i flashed the TWRP Recovery.
very easy. no errors.
and it shows as the storage is completely empty! as if someone in all this time wiped everything...
so now, what recovery software do you know/used/heard of?
ashyossi said:
soooooo.....
i flashed the TWRP Recovery.
very easy. no errors.
and it shows as the storage is completely empty! as if someone in all this time wiped everything...
so now, what recovery software do you know/used/heard of?
Click to expand...
Click to collapse
When the storage is completely empty, are you booted in recovery, the bootloader or just trying to boot normally? When you say it's empty, do you actually see the device on your computer? If so, is it completely empty with no folders or files or anything, or just stock stuff?
Can you check mount and make sure all the storage volumes are mounted? It's usually blank when they are all manually unmounted.
*** NOTE: Please excuse my English.
*** WARNING: I'm not responsible if anything happens to your device, I'm just sharing my experience and what I did to fix my own phone. Proceed at your own RISK.
I bought my Nexus 6p 64gb and as soon as I took it out of the box, I went directly and followed the guide here. So i unlocked the bootloader, flashed TWRP as a custom recovery, flashed CM13 + OpenGapps.
I noticed that every time I boot my device I get this warning:
Your device is corrupt. It can’t be
trusted and may not work properly.
Visit this link on another device:
go.co/ABH
and it does not seem to be a normal warning because when my OS boots up it shows me this
"Android system:
There’s an internal problem with your device. Contact your manufacturer for details"
Later on when I updated to the latest nightly image my camera crashes and doesn't function properly. I also already has an issue with Bluetooth and "Bluetooth share" crashing but that was unrelated. Anyways I was crippled in my day to day usage. Then I thought that I need to fix this asap because it might cause performance/security/hardware problems in the future.
So basically the fix is you should flash the latest bootloader image and radio image. Personally I wanted to start clean and make sure I have no corrupted files so here is what I did,
1. What i did is erase all boot, system, kernel & recovery files by typing the below command using fastboot just incase they were corrupted,
(Note: YOU DONT NEED TO DO THIS STEP, but i prefer starting clean incase i had some corrupted files. YOU WILL ALSO LOSE ENCRYPTION DOING THE FIRST STEP)
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
Source: http://devs-lab.com/...i-nexus-6p.html
2. Then i flashed the latest factory images in this sequence using fastboot, which can be found here: https://developers.g...s/images#angler
(Note: 6.0.1 (MMB29M) was latest image at the time i did this. For people who are doing this for the first time, then you just need to download the image then extract the needed files from it)
fastboot flash bootloader bootloader-angler-angler-xx.xxx.img
fastboot reboot-bootloader
fastboot flash radio radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cache cache.img
fastboot flash vendor vendor.img
fastboot format userdata
fastboot reboot
Source: http://forum.xda-dev...operly-t3268407
3. From there i reflashed TWRP using fastboot, then flashed the latest beta SuperSU v2.62 at the time, and then CM13, then OpenGapps, then again reflashed SuperSU v2.62 just incase, lol. (Do not flash the version of SuperSU that TWRP offers to flash for you in order to give you root, it is not compatible and will cause problems. When using TWRP before you've actually flashed SuperSU 2.50+, when you attempt to reboot out of TWRP it will tell you that it's detecting that you don't have root and it will offer to root for you, skip past this.)
What got fixed ?
-FIXED, this won't show up anymore:
Your device is corrupt. It can’t be
trusted and may not work properly.
Visit this link on another device:
go.co/ABH
-FIXED, this won't show up anymore:
Android system:
There’s an internal problem with your device. Contact your manufacturer for details.
-FIXED, Camera is working !
-NOT FIXED, "Bluetooth share" still crashes but I think its unrelated to this issue.
Hope this helps everyone as it helped me, thanks.
Sent from my Nexus 6P using Tapatalk
\*O / Thank you !!
Thanks, but better option? Don't reboot.
Sent from my Nexus 6P using Tapatalk
bob_mord_les said:
\*O / Thank you !!
Click to expand...
Click to collapse
Ur welcome [emoji1]
Sent from my Nexus 6P using Tapatalk
Followed your guide, thanks, but the message "Your device is corrupt. It can’t betrusted and may not work properly." still appears during a CM boot.
The message "There’s an internal problem with your device. Contact your manufacturer for details" appears when I boot into recovery (TWRP)
The camera is working now.
Also, before I was able to flash CM-13 I had to do "WIPE >> Format Data" from TWRP, otherwise CM was exiting with error 7.
The following packages were used:
original 6.0.1 (MMB29P) factory image
BETA-SuperSU-v2.66-20160103015024.zip
cm-13.0-20160115-NIGHTLY-angler.zip
open_gapps-arm64-6.0-micro-20160115.zip
twrp-2.8.7.2-angler.img
I also noticed that when rebooting into factory image, the same warning message appears as well.
Any way to fix it or did I do something wrong?
Why are people trying to fix an non issue? To get rid of the message you need to relock the bootloader which is more of a risk if your rooted. Its a message that only appears for a few seconds when you reboot and you don't need to do anything to get past it.
There is no corruption and the phone is trusted by YOU as you unlocked it and nothing else cares. Where is the issue?
g_kos said:
Followed your guide, thanks, but the message "Your device is corrupt. It can’t betrusted and may not work properly." still appears during a CM boot.
The message "There’s an internal problem with your device. Contact your manufacturer for details" appears when I boot into recovery (TWRP)
The camera is working now.
Also, before I was able to flash CM-13 I had to do "WIPE >> Format Data" from TWRP, otherwise CM was exiting with error 7.
The following packages were used:
original 6.0.1 (MMB29P) factory image
BETA-SuperSU-v2.66-20160103015024.zip
cm-13.0-20160115-NIGHTLY-angler.zip
open_gapps-arm64-6.0-micro-20160115.zip
twrp-2.8.7.2-angler.img
I also noticed that when rebooting into factory image, the same warning message appears as well.
Any way to fix it or did I do something wrong?
Click to expand...
Click to collapse
It's just telling you what you already know. You modified your system partition yourself so don't worry about it.
https://support.google.com/nexus/answer/6185381?hl=en
XxMORPHEOUSxX said:
It's just telling you what you already know. You modified your system partition yourself so don't worry about it.
https://support.google.com/nexus/answer/6185381?hl=en
Click to expand...
Click to collapse
Thanks. I read it in the original Heisenberg's unlock guide and was surprised when I read this post that it was possible to get rid of the warning message without locking the bootloader .
I'm new here in the forum's..I usually just read and carry on..the one think I'd like to say is..I don't understand why people got to say 'why you doing that for, ya don't need to' far as I know..this an educational site to learn..if he wants learn how to get rid of the warning..I don't see any problems in that whatsoever.
The message "There is an internal problem with your device..." seems to be related to the security patch version. This was my biggest issue, the message I get when booting the phone was annoying and I knew it was not a big deal, but having an internal problem warning was concerning, flashing the vendor image was the solution for me. But if you like to start clean then I have the steps written, but if you update then again you'll get the warning when booting up.
Sent from my Nexus 6P using Tapatalk
zooman31 said:
I'm new here in the forum's..I usually just read and carry on..the one think I'd like to say is..I don't understand why people got to say 'why you doing that for, ya don't need to' far as I know..this an educational site to learn..if he wants learn how to get rid of the warning..I don't see any problems in that whatsoever.
Click to expand...
Click to collapse
I think what people are trying to say is the risk/reward for getting rid of the message is not worth it. Especially since its just a brief warning you only see during boot. Just flashing twrp recovery will give the red message. SuperSU will help get rid of it which is why the OP was able to remedy it. It will not work for everyone though. Modifying the bootloader is the only sure fire way to snuff it out for good and you would be a fool to try and mess with your bootloader for something aesthetic. That's how most real bricks happen, is when a bootloader gets corrupted.
XxMORPHEOUSxX said:
I think what people are trying to say is the risk/reward for getting rid of the message is not worth it. Especially since its just a brief warning you only see during bouot. Just flashing twrp recovery will give the red message. SuperSU will help get rid of it which is why the OP was able to remedy it. It will not work for everyone though. Modifying the bootloader is the only sure fire way to snuff it out for good and you would be a fool to try and mess with your bootloader for something aesthetic. That's how most real bricks happen, is when a bootloader gets corrupted.
Click to expand...
Click to collapse
I assume that most people know the drill..you proceed to test at your own risk..the how to in the first post seemed to have worked after it was tested by the author.
zooman31 said:
I assume that most people know the drill..you proceed to test at your own risk..the how to in the first post seemed to have worked after it was tested by the author.
Click to expand...
Click to collapse
Basically just flash SuperSU last in whatever sequence, and as long as it boots,the red message will be gone. But change anything after and it will probably come back. I have nothing negative to say about this thread. I originally posted the nexus link just so people can rest assured that it is not an actual problem and a normal, albeit annoying, side effect of modifying the Nexus 6p. Happy Flashing
XxMORPHEOUSxX said:
Basically just flash SuperSU last in whatever sequence, and as long as it boots,the red message will be gone. But change anything after and it will probably come back. I have nothing negative to say about this thread. I originally posted the nexus link just so people can rest assured that it is not an actual problem and a normal, albeit annoying, side effect of modifying the Nexus 6p. Happy Flashing
Click to expand...
Click to collapse
all i did was flash twrp and unlocked the bootloader and still got the red message. so all i have to do is flash supersu and root? to get rid of it?
TechMillz93 said:
all i did was flash twrp and unlocked the bootloader and still got the red message. so all i have to do is flash supersu and root? to get rid of it?
Click to expand...
Click to collapse
Yes. The SuperSU beta 2.66 is what I use.
XxMORPHEOUSxX said:
Yes. The SuperSU beta 2.66 is what I use.
Click to expand...
Click to collapse
so i just reflashed the vendor and now im in bootloop ;(
TechMillz93 said:
so i just reflashed the vendor and now im in bootloop ;(
Click to expand...
Click to collapse
Why did you flash vendor? Try clearing caches and then reboot. Let it sit for 10 min too while starting up.
XxMORPHEOUSxX said:
Why did you flash vendor? Try clearing caches and then reboot. Let it sit for 10 min too while starting up.
Click to expand...
Click to collapse
im good now i just reflashed all the images im good.
but i have to feflash twrp now, what would u recommend
systemless or traditional ?
TechMillz93 said:
im good now i just reflashed all the images im good.
but i have to feflash twrp now, what would u recommend
systemless or traditional ?
Click to expand...
Click to collapse
Systemless unless you want to use xposed otherwise it doesn't matter. Systemless just makes it so you can use root apps like android pay. I use the 2.66 systemless. The instructions are a little all over the place on that thread. You no longer need a modified boot.IMG. the SuperSU zip patches whatever boot.IMG you have. So all you need to flash is the supersu2.66 for systemless or the traditional zip if going that route.
XxMORPHEOUSxX said:
Systemless unless you want to use xposed otherwise it doesn't matter. Systemless just makes it so you can use root apps like android pay. I use the 2.66 systemless. The instructions are a little all over the place on that thread. You no longer need a modified boot.IMG. the SuperSU zip patches whatever boot.IMG you have. So all you need to flash is the supersu2.66 for systemless or the traditional zip if going that route.
Click to expand...
Click to collapse
so i dont need gapps etc?
its all in there?
After i boot in twrp with n preview asking a password for decrip device. I cannot install any kernel,need change anything?
You need to flash a modified boot.img for it to be able to decrypt properly, there's a link in section 2 of my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
There is an updated TWRP that you can flash that is able to read/write and doesn't ask for a password.
Heisenberg said:
You need to flash a modified boot.img for it to be able to decrypt properly, there's a link in section 2 of my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
I try but stuck in twrp first screen.
matheus_sc said:
After i boot in twrp with n preview asking a password for decrip device. I cannot install any kernel,need change anything?
Click to expand...
Click to collapse
Disable forced-encryption, and decrypt your 6P first. Here is my tutorial: http://www.droidorigin.com/decrypt-nexus-6p/
Once you have, you can flash TWRP easily.
matheus_sc said:
I try but stuck in twrp first screen.
Click to expand...
Click to collapse
What version of TWRP are you using?
Heisenberg said:
What version of TWRP are you using?
Click to expand...
Click to collapse
3.0.0.1, without format user data/decrypt, i cannot flash any kernel?
I made flash a kernel with flashfire app now all fine here.
I'm stuck too. What should I do? Did you figure it out?
Drewski_1987 said:
I'm stuck too. What should I do? Did you figure it out?
Click to expand...
Click to collapse
It is an issue with TWRP right now. It wouldn't work until you have disabled forced-encryption and decrypted your device.
Here is what you could do: http://forum.xda-developers.com/showpost.php?p=66354239&postcount=746
So does twrp work at all with the n previews? How does one root the previews without twrp? Looking at installing the fourth one, but I'm not willing to lose root.
I accidentally let the OTA try to update from Preview 3 to 4. It stuck on the TWRP splash screen 3.0.2-0 (I think). It didn't seem to fail or anything but it just would never go past that splash screen. I was being dumb, updating without access to a C to A cable so I thought I was screwed but I decided to try something else out. I hit the BP Tools button on the Bootloader menu and for some reason that booted my phone up like normal. I then tried to see if I could boot it up normally. No luck, same TWRP splash screen. BP Tools worked again, but I know its some developer setting and I don't want to mess with anything that could mess me up later. Does anyone know how to get past the TWRP screen? Also anyone know why BP Tools would boot but the regular boot wouldn't work? I guess this is what I get for being a dumbass. I knew I shouldn't but I get so damn excited about updates!
Thanks a lot.
51D7H3K1D said:
I accidentally let the OTA try to update from Preview 3 to 4. It stuck on the TWRP splash screen 3.0.2-0 (I think). It didn't seem to fail or anything but it just would never go past that splash screen. I was being dumb, updating without access to a C to A cable so I thought I was screwed but I decided to try something else out. I hit the BP Tools button on the Bootloader menu and for some reason that booted my phone up like normal. I then tried to see if I could boot it up normally. No luck, same TWRP splash screen. BP Tools worked again, but I know its some developer setting and I don't want to mess with anything that could mess me up later. Does anyone know how to get past the TWRP screen? Also anyone know why BP Tools would boot but the regular boot wouldn't work? I guess this is what I get for being a dumbass. I knew I shouldn't but I get so damn excited about updates!
Thanks a lot.
Click to expand...
Click to collapse
Same issue for me. Stuck on the splash screen with both 3.0.2-0 and 3.0.1-0.
Im here in N preview 4 also stuck on TWRP splash screen
Edit: i guess is because im encrypted
matheus_sc said:
I try but stuck in twrp first screen.
Click to expand...
Click to collapse
Drewski_1987 said:
I'm stuck too. What should I do? Did you figure it out?
Click to expand...
Click to collapse
DJBhardwaj said:
It is an issue with TWRP right now. It wouldn't work until you have disabled forced-encryption and decrypted your device.
Here is what you could do: http://forum.xda-developers.com/showpost.php?p=66354239&postcount=746
Click to expand...
Click to collapse
if you have a backup (titanium or nandroid), or don't mind starting from scratch you can make TWRP work with DP4 by:
fastboot erase cache
fastboot erase userdata
There's got to be a way to get around the encryption problem without decrypting the phone...
Would this work: when twrp asks for passcode to decrypt, say skip. Then take the SuperSU zip from my computer and put it on my phone via USB, and flash it from twrp.
Would it work even though twrp can't read my storage?
If your phone is encrypted, the only twrp that works is 3.0.0.0
You can use it to adb sideload supersu zip and root the phone. But won't be able to mount my partitions as it cant decrypt the phone.
Sent from my Nexus 6P using Tapatalk
asj0422 said:
So does twrp work at all with the n previews? How does one root the previews without twrp? Looking at installing the fourth one, but I'm not willing to lose root.
Click to expand...
Click to collapse
Look for CF Auto Root. This worked for me without TWRP on DP4.
mochamoo said:
Look for CF Auto Root. This worked for me without TWRP on DP4.
Click to expand...
Click to collapse
So you're encrypted and rooted on dp4? I might have to try that then...
asj0422 said:
So you're encrypted and rooted on dp4? I might have to try that then...
Click to expand...
Click to collapse
Yes.
Sent from my Nexus 6P using Tapatalk
I've had my Moto X Pure for over a few months now. After rooting it, i installed TWRP 3.0.2 and have had different roms and not come across any problems regarding a hard brick. I was using my phone on the CM 13 Rom, and it was bugging out, so i tried to reboot. After trying to reboot, it would come to the WARNING BOOTLOADER UNLOCKED SCREEN and not boot past that, let alone get into the actual loading screen. Now, i cant boot into twrp. When i try to enter recovery mode, it goes to the TWRP screen, and sits there without proceeding. I cant boot the phone, or boot into recovery. I can only boot into the bootloader. ANY AND EVERY ADVICE IS APPRECIATED THANK YOU!!!
Edit: I fixed it. had to manually extract and reflash some files from a very useful restore to stock tool.
http://forum.xda-developers.com/mot...ndows-tool-moto-x-style-pure-edition-t3199905
Thank you for all of the help so quickly.
kagarii said:
I've had my Moto X Pure for over a few months now. After rooting it, i installed TWRP 3.0.2 and have had different roms and not come across any problems regarding a hard brick. I was using my phone on the CM 13 Rom, and it was bugging out, so i tried to reboot. After trying to reboot, it would come to the WARNING BOOTLOADER UNLOCKED SCREEN and not boot past that, let alone get into the actual loading screen. Now, i cant boot into twrp. When i try to enter recovery mode, it goes to the TWRP screen, and sits there without proceeding. I cant boot the phone, or boot into recovery. I can only boot into the bootloader. ANY AND EVERY ADVICE IS APPRECIATED THANK YOU!!!
Click to expand...
Click to collapse
If your able to boot into bootloader you can try to reflashTWRP or flash the original recovery and the original system files.
kagarii said:
I've had my Moto X Pure for over a few months now. After rooting it, i installed TWRP 3.0.2 and have had different roms and not come across any problems regarding a hard brick. I was using my phone on the CM 13 Rom, and it was bugging out, so i tried to reboot. After trying to reboot, it would come to the WARNING BOOTLOADER UNLOCKED SCREEN and not boot past that, let alone get into the actual loading screen. Now, i cant boot into twrp. When i try to enter recovery mode, it goes to the TWRP screen, and sits there without proceeding. I cant boot the phone, or boot into recovery. I can only boot into the bootloader. ANY AND EVERY ADVICE IS APPRECIATED THANK YOU!!!
Click to expand...
Click to collapse
Can you get it into fastboot mode? If you can, it sounds like somehow the recovery is corrupt and you would need to use 'fastboot erase recovery' first, and then 'fastboot flash recovery recovery.img' (using the twrp .img flashable file of course)
I hope that does the trick. Only think I can think of other than that is look for the automated return to stock tool for the moto x 2015 and use that.
thanks
[email protected] said:
If your able to boot into bootloader you can try to reflashTWRP or flash the original recovery and the original system files.
Click to expand...
Click to collapse
fixed it thank you!
thanks
benjmiester said:
Can you get it into fastboot mode? If you can, it sounds like somehow the recovery is corrupt and you would need to use 'fastboot erase recovery' first, and then 'fastboot flash recovery recovery.img' (using the twrp .img flashable file of course)
I hope that does the trick. Only think I can think of other than that is look for the automated return to stock tool for the moto x 2015 and use that.
Click to expand...
Click to collapse
fixed it thank you!
kagarii said:
fixed it thank you!
Click to expand...
Click to collapse
Great news! You're very welcome. I was in that exact same situation with my old Xperia Z2. It's pretty scary.
kagarii said:
fixed it thank you!
Click to expand...
Click to collapse
Can you tell us what fixed it? Do you know if it was firmware related? Was it the recovery? I have multiple people on this device all on custom software, always interested to find the cause of these types of issues for future reference. And most importantly, glad you got it resolved!
Sent from my XT1575 using Tapatalk
DonKilluminati23 said:
Can you tell us what fixed it? Do you know if it was firmware related? Was it the recovery? I have multiple people on this device all on custom software, always interested to find the cause of these types of issues for future reference. And most importantly, glad you got it resolved!
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
I honestly have no idea what the problem was. But i downloaded and used someones lollipop restore to stock tool, literally restoring to the original state you got the phone in, and it worked. I believe it had something to do with the rom, and possibly some xposed modules i had installed, but there was nothing that actually messed around with the phone's system files. I couldn't access recovery in anyway whatsoever, but my advice to you is that if you ever need help because the phone is potentially hard-bricked, see if it connects to PC and if it does use the restore to stock tool.
kagarii said:
I honestly have no idea what the problem was. But i downloaded and used someones lollipop restore to stock tool, literally restoring to the original state you got the phone in, and it worked. I believe it had something to do with the rom, and possibly some xposed modules i had installed, but there was nothing that actually messed around with the phone's system files. I couldn't access recovery in anyway whatsoever, but my advice to you is that if you ever need help because the phone is potentially hard-bricked, see if it connects to PC and if it does use the restore to stock tool.
Click to expand...
Click to collapse
Were you on marshmallow before you used the restore to stock tool? I thought downgrading android versions was a no-no currently.
jDally987 said:
Were you on marshmallow before you used the restore to stock tool? I thought downgrading android versions was a no-no currently.
Click to expand...
Click to collapse
It's possible, through tools like this. I don't know too much of the topic.
jDally987 said:
Were you on marshmallow before you used the restore to stock tool? I thought downgrading android versions was a no-no currently.
Click to expand...
Click to collapse
Mine wouldnt let me factory reset in twrp to flash something else while on cr droid it jist vibrates now it wont even boot into cr droid ive try to flash another rom but nothing since recovery suddenly wont let me wipe. Any advice on whats causing this i have a 64 gb adopted sd catd also i think i accidently repartitioned sd card in twrp.
Sherrillface said:
Mine wouldnt let me factory reset in twrp to flash something else while on cr droid it jist vibrates now it wont even boot into cr droid ive try to flash another rom but nothing since recovery suddenly wont let me wipe. Any advice on whats causing this i have a 64 gb adopted sd catd also i think i accidently repartitioned sd card in twrp.
Click to expand...
Click to collapse
Old thread. But can you at least get into TWRP recovery? Why won't it let you wipe? Like what does it say?
jDally987 said:
Old thread. But can you at least get into TWRP recovery? Why won't it let you wipe? Like what does it say?
Click to expand...
Click to collapse
Nothing it just vibrates as soon as i hit factory reset then bootloops now it wont even go into recovery just fastboot screen but cant get fastboot to work at all and have all drivers android studio etc. Nothing will work need a new solution
It was hash kernel it corrupted all 64 gigs of storage and music etc. Had to return to stock via auto flash firmware.
Mine is XT1572 device. Since the mentioned tool was not available for this model, I took the chance with XT1575 tool. It did all the steps but the issue has become worse. Now, my device is automatically getting On and OFF in seconds and does not boot beyond the bootloader 'unlocked' warning screen. Please please please help !!!!
Hey guys I recently restored a nandroid on my 6p from a 7.1.1 rom but I get stuck on boot logo now when j go to recovery(TWRP) all my files are completely gone? and it says something about encryption ...did I brick my device? And if not what steps do I have to do to get back up and running again? Like download rom gapps and SuperSU all over again on my PC etc..? I know my bootloader is unlocked still and I have to be rooted still since I can go to twrp so any help will be appreciated thanks.
Jiggs82 said:
Hey guys I recently restored a nandroid on my 6p from a 7.1.1 rom but I get stuck on boot logo now when j go to recovery(TWRP) all my files are completely gone? and it says something about encryption ...did I brick my device? And if not what steps do I have to do to get back up and running again? Like download rom gapps and SuperSU all over again on my PC etc..? I know my bootloader is unlocked still and I have to be rooted still since I can go to twrp so any help will be appreciated thanks.
Click to expand...
Click to collapse
I am not exactly an expert, but I would recommend to flash back the latest image from Google...go back to completely stock and then if you want root and install TWRP again. Good news is your bootloader is still unlocked, so I don't think you are bricked. Good luck!
Pecata said:
I am not exactly an expert, but I would recommend to flash back the latest image from Google...go back to completely stock and then if you want root and install TWRP again. Good news is your bootloader is still unlocked, so I don't think you are bricked. Good luck!
Click to expand...
Click to collapse
Ok so should I use the Nexus root toolkit and start from scratch again? Yeah my bootloader is unlocked and I can see twrp so I must still be rooted ..just wiped my whole device that all thanks
Try re flashing the Vendor.img sounds like the vendor didn't get restored
Sent from my Pixel XL using Tapatalk
i would but everything (files etc.) are gone from my phone...so i would have to download and flash it thru my pc right? if not ill probably just flash a rom gapps the vendor of course and super su and see if it boots up to the rom
Yup just download the Factory Image and extract the vendor image and flash it with fastboot.
Or flash another ROM /Gapps/ Vendor
Sent from my Pixel XL using Tapatalk
Not clear. The files you had before restore are missing or you miss files from your backup? Twrp backup does not backup your /data/media.
White google logo hanging is a due to bad vendor files.