Hello my asus memopad me176c will not finish booting up.
The issue was caused by switching the runtime to ART because I thought it would run faster than dalvik. Is there ANY easy way to get my tablet up and running again? PLEASE help me ASAP!
You've use ART without unlocking the bootloader? RMA IT!
bravesoul said:
You've use ART without unlocking the bootloader? RMA IT!
Click to expand...
Click to collapse
What do you mean RMA it? What is RMA?
I have the same problem, but I doubt RMA is the only solution to this.
Any other ideas?
Also, could anyone explain why it breaks the device when switching to ART?
Why is there an option for this?
TheSwagMaster said:
Hello my asus memopad me176c will not finish booting up.
The issue was caused by switching the runtime to ART because I thought it would run faster than dalvik. Is there ANY easy way to get my tablet up and running again? PLEASE help me ASAP!
Click to expand...
Click to collapse
I did the same mistake, just wipe data partition (stock recovery will wipe internal sd data too, cwm will not.
Related
Hey there,
I got quite a serious problem. Since i updated to 5.1 my phone sometimes suddenly restarts, followed by a message which says "optimizing apps", which ranges from 30 to 150 apps. At first, it was no big problem, now it occures nearly every 10 minutes, so currently i can't really use my phone.
What i tried to do:
Factory reset, reflash 5.0 - 5.1.1 (every single image available)
The problem is still there.
Now my question, is it a Softwareproblem, which will be updated soon (should i try Android M (what about the warranty?))?
Or is it quite a serious hardwareproblem (i read somewhere that it could be because of overused RAM modules)?
I tried to use the searchengine, but i didnt find a specific thread in this subforum.
The optimising is a software issue caused by a random reboots. The reboot itself could be caused by anything though
danarama said:
The optimising is a software issue caused by a random reboots. The reboot itself could be caused by anything though
Click to expand...
Click to collapse
Thank you for your quick reply. I continued reading and as it seems there are quite a number of users with the same problems as me. Although no one has gotten a solution till now. It doesn't matter if it's a Nexus 4, 5 or 6 but all the Nexusphones seem to be affected once updated to 5.1 or newer.
Unluckily sending it in to repair is not a good solution because they told me it would take 2-4 weeks which is not possible for me... How can Google not release a proper update after 5.1.1 which fixes it? Are they so focused about Android M? I still can't overcome myself to install the Android M because i fear to lose my warranty.
Haabiii said:
Thank you for your quick reply. I continued reading and as it seems there are quite a number of users with the same problems as me. Although no one has gotten a solution till now. It doesn't matter if it's a Nexus 4, 5 or 6 but all the Nexusphones seem to be affected once updated to 5.1 or newer.
Unluckily sending it in to repair is not a good solution because they told me it would take 2-4 weeks which is not possible for me... How can Google not release a proper update after 5.1.1 which fixes it? Are they so focused about Android M? I still can't overcome myself to install the Android M because i fear to lose my warranty.
Click to expand...
Click to collapse
Dude, it's a Nexus. Warranty isn't an issue as long as you return to stock and relock before a warranty claim.
If flashing a factory image didn't fix it, either you're not wiping or formatting the cache correctly or you have a hardware issue.
Don't be so quick to blame Google when thousands of others, myself included, have taken the update without issue.
Evolution_Tech said:
Dude, it's a Nexus. Warranty isn't an issue as long as you return to stock and relock before a warranty claim.
Click to expand...
Click to collapse
Thanks, I didn't know that.
Evolution_Tech said:
If flashing a factory image didn't fix it, either you're not wiping or formatting the cache correctly or you have a hardware issue.
Click to expand...
Click to collapse
I did the factoryreset via fastboot, also i used the nexus toolkit to do a proper stock reset so i don't quite get how it could be an incorrectly done reset. So the hardware just breaks during the updateprocess?
Evolution_Tech said:
Don't be so quick to blame Google when thousands of others, myself included, have taken the update without issue.
Click to expand...
Click to collapse
I am usually quite quick in blaming others if there are also many people with excactly the same problem, sudden reboots with app optimization right after the update to 5.1 or 5.1.1, some even before at 5.0 or 5.0.1.
I'm going to try the Android M Update, maybe that will help.
Haabiii said:
Thanks, I didn't know that.
I did the factoryreset via fastboot, also i used the nexus toolkit to do a proper stock reset so i don't quite get how it could be an incorrectly done reset. So the hardware just breaks during the updateprocess?
I am usually quite quick in blaming others if there are also many people with excactly the same problem, sudden reboots with app optimization right after the update to 5.1 or 5.1.1, some even before at 5.0 or 5.0.1.
I'm going to try the Android M Update, maybe that will help.
Click to expand...
Click to collapse
Personally, I'd boot to bootloader and do:
fastboot format cache
Evolution_Tech said:
Personally, I'd boot to bootloader and do:
fastboot format cache
Click to expand...
Click to collapse
Already done and i also reflashed the whole cache image. I hope the Android 6 Update will help solve my issues. The problem is, that i usually get really upset about little stuff like that just because i don't get why it's happening.
I updated monday evening to the Android M Preview, for now it only restarted once to, as it said, install a update (?), since then no reboot at all. It worked like a charm yesterday. I really hope the problem is fixed that way.
Just wanted to let you know if you have a same problem.
https://youtu.be/TnKMB9pfC_E
This video explains what's happening
Sent from my SM-G925P using Tapatalk
And everything I really tried
Sent from my SM-G925P using Tapatalk
In the video we can't see the bootloop happening and when and how.. Could you please make it clear how and what happens?
DGooseman said:
In the video we can't see the bootloop happening and when and how.. Could you please make it clear how and what happens?
Click to expand...
Click to collapse
The device has no bootloader system data or internal. It needs to have those things reinstalled but phone refuses to install system without boot loader so i need to know if it is possible to install the full amdroid update package and possibly if i could replace the twrp with official android recovery to install official os that way. What happened in the first place is (my little stepbtothers device he asked me to root it) my lottle stepbrother saw there was an os update and told it to update and when he did it went to update but wiped the system cache data and the bootloader was inactive or something in preparation of the update and i need to fix it and will unroot and/or never root it again until he knows not to do that until im sure there are none left.
Sent from my SM-G925P using Tapatalk
pickles523 said:
The device has no bootloader system data or internal. It needs to have those things reinstalled but phone refuses to install system without boot loader so i need to know if it is possible to install the full amdroid update package and possibly if i could replace the twrp with official android recovery to install official os that way. What happened in the first place is (my little stepbtothers device he asked me to root it) my lottle stepbrother saw there was an os update and told it to update and when he did it went to update but wiped the system cache data and the bootloader was inactive or something in preparation of the update and i need to fix it and will unroot and/or never root it again until he knows not to do that until im sure there are none left.
Sent from my SM-G925P using Tapatalk
Click to expand...
Click to collapse
I dont have much experience with lg but i do have plenty with samsung devices
Sent from my SM-G925P using Tapatalk
If the phone has no bootloader, as you say, it's hardbricked.
If it's your situation see my guide here: http://forum.xda-developers.com/lg-l90/general/guide-unbrick-hard-bricked-l90-variants-t3173429
If not, you need to explain what's wrong with your phone, because in the video I can't see any bootloop.
Title says it all. Is there any known way to have root and device encryption still possible?
Thanks a lot.
plop12345 said:
Title says it all. Is there any known way to have root and device encryption still possible?
Thanks a lot.
Click to expand...
Click to collapse
Not currently. Unless you can trick the device into thinking it's fully charged and plugged in at the same time??
Jammol said:
Not currently. Unless you can trick the device into thinking it's fully charged and plugged in at the same time??
Click to expand...
Click to collapse
I never thought of this question, but good question. So root trips knox to stop encryption? Kinda lame if so.
Jammol said:
Not currently. Unless you can trick the device into thinking it's fully charged and plugged in at the same time??
Click to expand...
Click to collapse
Got it working with the stock ROM in the mean time. Just don't use TWRP to flash Magisk. Keep the stock recovery, Use Magisk Manager to patch boot.img (check tar format in settings) , then flash back via Odin, boot and factory reset. Done.
No luck with any custom ROM yet. Desperately looking for help. Would also pay quite a bit to have someone skilled looking into this. I don't want to keep the Korean ROM of my N950N
Nick216ohio said:
I never thought of this question, but good question. So root trips knox to stop encryption? Kinda lame if so.
Click to expand...
Click to collapse
No, flashing with TWRP requires to format data. That step loses encryption.
For some reason it's then impossible with Magisk or pph root to just reencrypt the phone from a custom ROM. It dies with invalid encryption and looses all your data when you try.
It's a bit different with SuperSU. Here it thinks encryption went well and tries to mount it on next boot, but then fails.
From my current knowledge it seems it needs stock recovery to recreate an encrypted data partition that actually works. That's the bit I'm stuck now...
plop12345 said:
No, flashing with TWRP requires to format data. That step loses encryption.
For some reason it's then impossible with Magisk or pph root to just reencrypt the phone from a custom ROM. It dies with invalid encryption and looses all your data when you try.
It's a bit different with SuperSU. Here it thinks encryption went well and tries to mount it on next boot, but then fails.
From my current knowledge it seems it needs stock recovery to recreate an encrypted data partition that actually works. That's the bit I'm stuck now...
Click to expand...
Click to collapse
On the Snap version, using SamFail gets rid of encryption. There's no way to encrypt for us with root because of the 80% short coming.
Jammol said:
On the Snap version, using SamFail gets rid of encryption. There's no way to encrypt for us with root because of the 80% short coming.
Click to expand...
Click to collapse
Ah crap, didn't even think of that issue
Anyway, at least to me a phone without reliable encryption is not usable as daily driver. I wonder why this gets so little attention. I spend some days now trying to resolve this, but there is not much information out there or I'm not capable to dig it up.
I couldn't even find a clear statement, what it actually is that prevents TWRP to mount encrypted /data on modern Samsung phones.
I known they do their own SOC based hardware encryption, but what is it that TWRP can't get? Does the trusted zone not release the key if a custom binary boots? I really like to understand a bit more on how this actually works.
Thanks
Figured it out: https://forum.xda-developers.com/galaxy-note-8/how-to/guide-how-to-root-device-encryption-t3742493
I am needing to send my device in to TMobile after trading for the 6t. I am rooted with Xposed on the latest stock OOS (3T). Would someone be able to let me know if there are any toolkits or simple steps to locking my bootloader and factory resetting the device?
Any help is greatly appreciated
Format the device in twrp (not talking about wiping but formating).
Or just use the Unbrick tool to completely reset everything back to stock. It removes and resets everything, including your bootloader status.
Thanks for being in the 3/T community and have fun with your new device!
0xPraeT0Rian said:
Format the device in twrp (not talking about wiping but formating).
Click to expand...
Click to collapse
For someone who don't know much this could result at a device with no Os.
Why not to use the standard factory reset from inside the device?
Sent from my ONEPLUS A3003 using Tapatalk
RASTAVIPER said:
For someone who don't know much this could result at a device with no Os.
Why not to use the standard factory reset from inside the device?
Click to expand...
Click to collapse
Yeah I have but the dm-verity is annoying it's coming up as not enforced I think, but my mom is trading in her 3T as well and I never unlocked her BL so it does not come up at all during boot.
Does anyone know if TMobile would void the trade-in because of that?
https://forums.oneplus.com/threads/...not-enforcing-at-boot-for-oneplus-3-t.735219/
This fixed my issue
Hello and thanks for your help. Somehow, on a reboot of my new 405QA I am stuck at the secure startup screen as seen in the attached image. I have no idea what this is, what it means, or how to get past it. I do not use anything but a swipe lockscreen so there is no fingerprint, pin, or pattern if that is what it seeks. I do not think I even enabled this "feature" but maybe it was turned on by default?
Anyhow, what can I do? I would like to preserve my system and I believe that if I fail to come up with what it wants, it will factory reset the phone.
Thanks for your help!
I gave up and went through the 30 tries until the thing factory reset. What BS. I never enabled this.
whitedavidp said:
I gave up and went through the 30 tries until the thing factory reset. What BS. I never enabled this.
Click to expand...
Click to collapse
This same thing happened to me when I first tried to unlock the bootloader and root the device. It is not an easy thing to do. I, like you, ran into roadblocks along the way. Lucky for me, I was upgrading from a Nexus 6 (still love that phone) that was operating just fine. So I could take my time and get the LG40 up and running how I wanted it to be (bootloader unlocked, unencrypted and rooted with Magisk) before I began setting it up.
Just be patient, and you'll get there too.
[NG]Owner
NGOwner said:
This same thing happened to me when I first tried to unlock the bootloader and root the device. It is not an easy thing to do. I, like you, ran into roadblocks along the way. Lucky for me, I was upgrading from a Nexus 6 (still love that phone) that was operating just fine. So I could take my time and get the LG40 up and running how I wanted it to be (bootloader unlocked, unencrypted and rooted with Magisk) before I began setting it up.
Just be patient, and you'll get there too.
[NG]Owner
Click to expand...
Click to collapse
How did you guys fix it? Same roadblock too
minecraftuser1999 said:
How did you guys fix it? Same roadblock too
Click to expand...
Click to collapse
You could try resetting the device using the button combination