Nexus 9.
Running M preview 2, clean flashed a few days ago. Rooted, TWRP installed, ElementalX kernel. I just started getting this message on the splash screen during boot.
"Your device is corrupt. It can't be trusted and may not work properly.
Visit this link on another device: g.co/ABH"
It boots fine and works fine. No other symptoms, at all.
Does anyone know what this is?
I searched XDA and did a more general Google search and found nothing.
Thanks, in advance.
Having the same issue except it doesn't boot. I've had it unlocked for a while. Just flashed M v2 yesterday. Wanted to root just now. Ran "sh root-mac.sh" and started getting this error.
joehouin said:
Having the same issue except it doesn't boot. I've had it unlocked for a while. Just flashed M v2 yesterday. Wanted to root just now. Ran "sh root-mac.sh" and started getting this error.
Click to expand...
Click to collapse
same problem here.... only on my nexus 6. Anybody have a solution?
i found a solution download Nexus root toolkit v2.0.5.
download the preview v.2
Use Flash stock+ Unroot
Flash it again and you fine..
to enable fastboot, but you mobile in bootloader!!
pricedpizza said:
same problem here.... only on my nexus 6. Anybody have a solution?
i found a solution download Nexus root toolkit v2.0.5.
download the preview v.2
Use Flash stock+ Unroot
Flash it again and you fine..
to enable fastboot, but you mobile in bootloader!!
Click to expand...
Click to collapse
Hello, do you mind sharing the link to preview 2, i googled it but didn't see an exact mention of "preview v.2"
Is it one of the ones found on this link?
https://developers.google.com/android/nexus/images#shamu
Thanks in advance,
Julian
I have this same message on my Nexsus 6. Neither Google, Motorola or Sprint can help me get my phone to turn on again. It's past the one year warranty, so no one will replace it. Can anyone help me?
cam30era said:
Nexus 9.
Running M preview 2, clean flashed a few days ago. Rooted, TWRP installed, ElementalX kernel. I just started getting this message on the splash screen during boot.
"Your device is corrupt. It can't be trusted and may not work properly.
Visit this link on another device: g.co/ABH"
It boots fine and works fine. No other symptoms, at all.
Does anyone know what this is?
I searched XDA and did a more general Google search and found nothing.
Thanks, in advance.
Click to expand...
Click to collapse
I hit the same message loading CM13 on a Nexus 9. Google explains here - support.google.com nexus answer 6185381? I wiped all partitions and loaded stock Marshmallow - the error disappeared. After re-flashing TWRP 3.0.2 the "corrupt" error came back. I then rooted with BETA-SuperSU-v2.66 which got rid of the error. Have since added Google account, updated apps etc. Still booting without error.
So would you say twrp is the reason it gives that error? I rooted my phone today, but when I went to my recovery to check to see if I indeed had a nandroid back up, I didn't... I made one using titanium backup, but didn't show in twrp. Anyhow, about that error message... I didn't know what to do after I had the pop up error message so many times... so i just unrooted my Nexus 6p. I really would like to keep my phone rooted, but I didn't like seeing that concerning error message. Any ideas of what I can do. I would be starting from scratch again. Any links would help! Thank you in advance.
Related
Hello,
I have rooted my Xoom 2 ME and installed Safestrap 3.12 as explained here.
Apparently something went wrong after I tried to restore a backup to the Stock ROM Slot. I now have the Blue (instead of Red) Motorola Logo when I boot, followed by error messages telling me the "UI System" and "Configure" Applications have stopped.
Trying to solve the problem, I did a factory reset from the Stock Recovery Boot and now I see that I have lost all my Safestrap Backups and Slots.
So I have no backups to restore and no other Slots than the Stock ROM, which I cannot boot.
What are my options ?
Any help would be greatly appreciated.
Thanks.
A quick update on this
I'm having help form runandhide05 who is amazingly kind with me, answering all my questions in PM.
I have a Wi-Fi only 8.2 Xoom 2 bought in France so I have flashed this ROM : 0.268.4.MZ607.Retail.en.FR.
I could boot but when I tried to update OTA it failed. It downloads, start updating and fails so I am stuck in 3.2.2.
Also whenever I reach the page of an application in the Android Market, the Android Market quits.
Finally adb doesn't see my device.
I've tried flashing another ROM with the same result : 0.281.8.MZ607.NonEFIGSRetail.en.EU
All this is very new to me, I feel like I have learned a lot in 24 ours but I really have no idea were to go to solve this and feel like I am asking a lot to runandhide05 at the moment so if anyone as "qualified" as him had any idea to help it would be amazing.
… again runandhide05, thank you so much for all your help so far.
Problem solved !
The update succeeded when done via the "Motorola Device Manager" on PC.
After that I could use Google Play without it to quit and adb saw my device again.
I re-rooted and re-installed Safestrap with no troubles.
I'm on 4.4 right now and I just reviewed the ota but when it finished downloading, it went stock recovery and just said "error". Obviously I was pissed so I then went the adb root but that wouldn't work either. Something about it not being able to find "update.zip" when it is clearly in the same folder. After that I decided to flash a custom recovery, not clockwork but the other one. Whenever I try to go that route it still says it failed. I have been looking at posts and none have helped so far.
I am rooted, I don't have busybox/xposed, I am using art. I read something about having to have all of the stock apps. I had a modded playstore on here but I didn't work so I re-download one and installed it, could that have anything to do with my problems? And if so, where can I find another playstore app?
also, this is what it says in the custom recovery: /system/framework/core-libert. Jar unexpected E:Error executing updater in zip I tried googling but to no avail.
That modded play store might have changed some system files that prevent the update. You can try flashing one of the stock 4.4.2 Roms available in the android development forums. I used the one by bigxie.
Sent from my Nexus 5 using Tapatalk
Thanks man. Should I use an odex or deoxdex? And what's the difference?
I have this problem too....i'm rooted and get the error logo when i try to update too.....
paulbadassbriant said:
I have this problem too....i'm rooted and get the error logo when i try to update too.....
Click to expand...
Click to collapse
Try what the guy who replied to me said, it worked for me
Hi guys, I have a problem with a one plus one that can't exit from bootloop.
I just tried to flash a stock firmware (11S) and the one plus restoretool but with no success. I can only acced recovery and fastboot. The device is also unlocked. Can it be a hardware problem? Thank u for your help.
BlackSkorpion said:
Hi guys, I have a problem with a one plus one that can't exit from bootloop.
I just tried to flash a stock firmware (11S) and the one plus restoretool but with no success. I can only acced recovery and fastboot. The device is also unlocked. Can it be a hardware problem? Thank u for your help.
Click to expand...
Click to collapse
You don't give much detail as to what happened or what you were doing prior to your bootlooping. I suffered from a bootloop that took me several months to finally resolve on the very device I'm responding to you with. I was able to resolve it by installing the latest Oxygen OS from the OPO forums. I followed the directions exactly, then after booting into Oxygen it turned out that my WiFi and Bluetooth were refusing to turn on. After several attempts and force close reboots I was able to get them to function. Then I reinstalled TWRP, then flashed CMOS12, then finally CM which I'm using now. BTW for more detail look for my post about it in this forum. Hope this helps.
Odysseus1962 said:
You don't give much detail as to what happened or what you were doing prior to your bootlooping. I suffered from a bootloop that took me several months to finally resolve on the very device I'm responding to you with. I was able to resolve it by installing the latest Oxygen OS from the OPO forums. I followed the directions exactly, then after booting into Oxygen it turned out that my WiFi and Bluetooth were refusing to turn on. After several attempts and force close reboots I was able to get them to function. Then I reinstalled TWRP, then flashed CMOS12, then finally CM which I'm using now. BTW for more detail look for my post about it in this forum. Hope this helps.
Click to expand...
Click to collapse
Hi, i dont know what happened before because the Phone is not mine, is of the gf of a friend. I can reach fastboot and recovery and I also changed the recovery to twrp and installing a new rom, but bootloop still is running. What can i do else?
BlackSkorpion said:
Hi guys, I have a problem with a one plus one that can't exit from bootloop.
I just tried to flash a stock firmware (11S) and the one plus restoretool but with no success. I can only acced recovery and fastboot. The device is also unlocked. Can it be a hardware problem? Thank u for your help.
Click to expand...
Click to collapse
Do you have a backup? try restoring just the system and the data of your backup.. i used to flash the boot too but as far as i know flashing boot doesn't solve the issue (still bootloop-ing). if you are still in bootloop and really have no idea, try consider a full reset of your phone (all except your custom recovery, ofc) and flash a new flashable.zip rom.. (data+media also wiped) you can always copy files to your phone while in recovery by mounting a usb drive, in case you don't have a zip on your phone. of course, this is not the solution, and is not recommended, but take this as your last choice if any other method didn't work
hope it helps!
Kevin1705 said:
Do you have a backup? try restoring just the system and the data of your backup.. i used to flash the boot too but as far as i know flashing boot doesn't solve the issue (still bootloop-ing). if you are still in bootloop and really have no idea, try consider a full reset of your phone (all except your custom recovery, ofc) and flash a new flashable.zip rom.. (data+media also wiped) you can always copy files to your phone while in recovery by mounting a usb drive, in case you don't have a zip on your phone. of course, this is not the solution, and is not recommended, but take this as your last choice if any other method didn't work
hope it helps!
Click to expand...
Click to collapse
I dont have a backup, so i also tried yet everything you said. I dont have to save datas, so i flashed everything new, but still dont work. I also tried to flash everything from oneplusrecoverytool that in any difficult situations helped me, but in this case it did not worked. Is there any radical solution to get this Phone working? (i can install twrp and reach fastboot, but after installing something, it's always in bootloop. ?
i have the same problem , don't know what to do , i even used the tool to return to stock
maybe an overheat problem? i don't know
Gentlemen, please try the method I suggested above in my response. Go to the OPO forums and follow the procedure to switch to Oxygen OS exactly as they lay out. As long as you're unlocked and can get to the bootloader and recovery you aren't hard-bricked and will be able to eventually fix your handsets. I know from personal experience, because as I mentioned this device was hopelessly stuck in a bootloop for months before I was able to get it running again. Do a search for my previous post for instruction and as I said follow the guide to installing Oxygen to the letter. More than likely you've got several corrupt partitions and this method will resolve it. Once you've got your handset successfully running again on Oxygen you can then begin to flash other ROMs with no issues. For some reason the Oxygen OS is more robust in that it will boot up when there are issues with these corrupted partitions when CM based ROMs won't. I believe the title of my previous post was "hopelessly stuck in bootloop (solved)". I hope this helps.
Odysseus1962 said:
Gentlemen, please try the method I suggested above in my response. Go to the OPO forums and follow the procedure to switch to Oxygen OS exactly as they lay out. As long as you're unlocked and can get to the bootloader and recovery you aren't hard-bricked and will be able to eventually fix your handsets. I know from personal experience, because as I mentioned this device was hopelessly stuck in a bootloop for months before I was able to get it running again. Do a search for my previous post for instruction and as I said follow the guide to installing Oxygen to the letter. More than likely you've got several corrupt partitions and this method will resolve it. Once you've got your handset successfully running again on Oxygen you can then begin to flash other ROMs with no issues. For some reason the Oxygen OS is more robust in that it will boot up when there are issues with these corrupted partitions when CM based ROMs won't. I believe the title of my previous post was "hopelessly stuck in bootloop (solved)". I hope this helps.
Click to expand...
Click to collapse
i tried your solution but nothing changed i also tried this procedure http://forum.xda-developers.com/one...lusrecovery-tool-v1-0-restore-t2991851/page23 , the process is success but at the reboot the phone is always in bootloop
still same problem here =/
Download the latest fastboot image from here: http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
Then go here: http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471 follow step #8
Hi all ,
hopefully last chance here to stay my kindle alive.
What happened ? -> i updated the cm nightly to newest version. Worked well except of googel services end. Ok . Thought install newest GAPPS. Run to recovery mode load the newest zip file Gapps installed them and reload.
Everything looked well Check all the apps after while in screen then the login sreen came up and - it reacted not anymore to anything and after while the cm screen come up again and load and same procedure begins.
Checked to come via adb to it but unfortunately the device is known but with unauthorized so i cant do anything.
Someone an advice or hint for me??
Thanks a lot in advance
BR
Cyber
cyberurmel said:
Hi all ,
hopefully last chance here to stay my kindle alive.
What happened ? -> i updated the cm nightly to newest version. Worked well except of googel services end. Ok . Thought install newest GAPPS. Run to recovery mode load the newest zip file Gapps installed them and reload.
Everything looked well Check all the apps after while in screen then the login sreen came up and - it reacted not anymore to anything and after while the cm screen come up again and load and same procedure begins.
Checked to come via adb to it but unfortunately the device is known but with unauthorized so i cant do anything.
Someone an advice or hint for me??
Thanks a lot in advance
BR
Cyber
Click to expand...
Click to collapse
Hi Guys,
today it worked and i came to the recovery mode. Dont know why i didnt get it yesterday.. perhaps too excited....
Great that you solved the problem.
Friends and android geeks,could someone tell me the solution for my problem?
I have a htc one m8whl device and its unlocked and rooted now. I have a twrp 3.0.2 recovery installed on my device.
problem:
I face problem when flashing a cyanogenmod13-nightly os through twrp.
everytime i flash it , it shows "failed".
sanjeevikrishna said:
everytime i flash it , it shows "failed".
Click to expand...
Click to collapse
It doesn't just say "failed", it should give you an error code, like code 7 or something. Get back with the error code please.
thank you for replying
RAZERZDAHACKER said:
It doesn't just say "failed", it should give you an error code, like code 7 or something. Get back with the error code please.
Click to expand...
Click to collapse
Now the problem is actually solved. The error(sry did not notice the code) occurred only when i flashed the rom from usb-otg.
It was solved when i tried flashing from sd-card.
And i would be happy to know some good custom Roms for my htc one m8whl.
Thank you.
sanjeevikrishna said:
Now the problem is actually solved. The error(sry did not notice the code) occurred only when i flashed the rom from usb-otg.
It was solved when i tried flashing from sd-card.
And i would be happy to know some good custom Roms for my htc one m8whl.
Thank you.
Click to expand...
Click to collapse
CyanogenMod is if you like near stock android with some features on top.
ERROR 7;
RAZERZDAHACKER said:
CyanogenMod is if you like near stock android with some features on top.
Click to expand...
Click to collapse
Thank you dear friend.
I tried to find out the error code that occurred in previous sessions and it was ERROR:7 as you suggested. It happened with me when i tried to install NusenSeven for sprint m8 as well.
Additionally, I tried installing a couple of ROMS
1) BadBoys for m8 and
2) Wolla for m8.'
Both were installed successfully but unfortunately the Radio was not working. Plus both these Rom's kept on restarting multiple times in an hour for the whole day. Even-though it had many cool customisation's i couldn't use it.
Finally, i returned back to cm-13.0 nightly but Still it has two major problem
1) the Radio is down .
2) problem with the Gapps. ( I flashed the Gapps properly after the rom , but when i start my device i cannot find any apps from Gapps package. NOTE: There was a flash successful message on flashing gapps ).
kindly help me.
thank you in advance.