Related
All the boot loop problems I searched for are all rooted/flashed/etc.
My sisters Atrix is stock on 2.2, getting continues boot loop all of sudden this morning. Battery pulls are no help.
Is there anyway I can fix this without a factory reset?
Probably the same chance Poland has winning the Euro 2012...
Not sure if possible.
Won't go in safe mode. Tried clearing the cache partition. Nothing helped.
If I could get into safe mode I'm sure I could fix it, phone has not been messed around with so probably some stupid app caused this.
Very frustrating.
KingKuba13 said:
Safe mode
Click to expand...
Click to collapse
The hell are you talking about? This isn't Windows! The only way an app could mess with the system would be if it had root. And if you're completely stock, you won't have that.
nerfman100 said:
The hell are you talking about? This isn't Windows! The only way an app could mess with the system would be if it had root. And if you're completely stock, you won't have that.
Click to expand...
Click to collapse
Can't a rogue/virus/malware app mess with the system?
What could be causing this if its stock?
I'm more familiar with windows/ms dos.
Well, my money would be on Poland vs your Atrix,...
Anyway, what MIGHT work is to save the /data partition then follow the various instructions to reflash from square one (and end up with as close as you can get to what it was), then restore /data and pray. You might need (or want) to put an unlocked bootloader and real recovery on while you are doing all this. You should not need to touch /sdcard.so just leave hi, alone.
Start here for some suggestions on what is going on.
http://forum.xda-developers.com/showthread.php?t=1690842
Also, there are some good stickies in the General Atrix area.
You will really need to understamd what you are doing here, and not just follow a recipie. So spend some time understanding how fastboot and recovery work.
P.S., if you have an external sdcard in, pull that and see if it helps.
EDIT: If there is something super important on it, I would get somebody who knows what they are doing to extract iy for you.
exwannabe said:
Well, my money would be on Poland vs your Atrix,...
Anyway, what MIGHT work is to save the /data partition then follow the various instructions to reflash from square one (and end up with as close as you can get to what it was), then restore /data and pray. You might need (or want) to put an unlocked bootloader and real recovery on while you are doing all this. You should not need to touch /sdcard.so just leave hi, alone.
Start here for some suggestions on what is going on.
http://forum.xda-developers.com/showthread.php?t=1690842
Also, there are some good stickies in the General Atrix area.
You will really need to understamd what you are doing here, and not just follow a recipie. So spend some time understanding how fastboot and recovery work.
P.S., if you have an external sdcard in, pull that and see if it helps.
EDIT: If there is something super important on it, I would get somebody who knows what they are doing to extract iy for you.
Click to expand...
Click to collapse
I don't want to mess around with it too much since its my sisters phone. There's some important things on there but I guess life can go on without them.
If I do factory reset and update it to GB, is there anyway to choose 2.3.4 instead of 2.3.6 without rooting it. Read too many complaints about 2.3.6....
Why won't it let me into safe mode? Hold both volume buttons down after dualcore logo when the motorola animation starts right....
Did factory reset, phone working again.
There's no blur widgets and lot less icons on the phone than originally bought brand new, contacts came back eventually but for some reason all Google Plus profiles were added to contacts, never had that before.
Surprisingly all my pics and videos are still there which is nice.
Probably take me a week to get it even to close to tip top shape as before. :\
Wished I remember all the little tweaks I did for the last year.
Was just wondering if there is anyway to disable this because it is very annoying. Friend got a hold of it and thought it would be funny to reset it. Its useless in my opinion. Anyways is it possible?
CocaFoca said:
Was just wondering if there is anyway to disable this because it is very annoying. Friend got a hold of it and thought it would be funny to reset it. Its useless in my opinion. Anyways is it possible?
Click to expand...
Click to collapse
I'm wondering the same thing my brother. And can it be done unr00ted? I don't want someone being malicious screwing my phone over.
CocaFoca said:
Was just wondering if there is anyway to disable this because it is very annoying. Friend got a hold of it and thought it would be funny to reset it. Its useless in my opinion. Anyways is it possible?
Click to expand...
Click to collapse
foundingfathersfan2 said:
I'm wondering the same thing my brother. And can it be done unr00ted? I don't want someone being malicious screwing my phone over.
Click to expand...
Click to collapse
There was another thread started about this shortly after the phone was released. Is it true it erased your SD card as well?? There were a couple reports that it had for them. I made sure to back up my phone and routinely continue to do so in the off chance that someone does get a hold of it and unknowingly erases everything. This is a TERRIBLE "feature" and someone had said there was a file on a previous phone they had that was able to be edited to disable this, but as far as I know hasn't been found on the G3 yet. Though I'm not a dev by any means I plan on diving into the system files at some point, and hopefully can find something online to point me in the right direction... Believe me, I'm sure if I or someone else does find a way to disable it you will definitely see a thread for it, more than likely in the "General" section :good: Worst.....Feature.....Ever.....
I am OK with the 10 times then wipe...
If I had a friend do that to me, we would no longer be friends.
THEbigSWEEN said:
There was another thread started about this shortly after the phone was released. Is it true it erased your SD card as well?? There were a couple reports that it had for them. I made sure to back up my phone and routinely continue to do so in the off chance that someone does get a hold of it and unknowingly erases everything. This is a TERRIBLE "feature" and someone had said there was a file on a previous phone they had that was able to be edited to disable this, but as far as I know hasn't been found on the G3 yet. Though I'm not a dev by any means I plan on diving into the system files at some point, and hopefully can find something online to point me in the right direction... Believe me, I'm sure if I or someone else does find a way to disable it you will definitely see a thread for it, more than likely in the "General" section :good: Worst.....Feature.....Ever.....
Click to expand...
Click to collapse
Yes it is true about the ten times wiping the sd card. I tried it for myself bored at an airport and it wiped everything. Would love to turn this off somehow.
wwevoxnj said:
Yes it is true about the ten times wiping the sd card. I tried it for myself bored at an airport and it wiped everything. Would love to turn this off somehow.
Click to expand...
Click to collapse
See this is horrible. I can kind of understand the security purpose behind it and figured it would only wipe internal storage but SD as well with no option to turn off?! This should be something you CHOOSE to happen after 10 failed attempts. Especially if you have that one A$$hole "friend" (I'm sure a lot of you are picturing him now ) who thinks something like this would be hilarious.....Every time....
THEbigSWEEN said:
See this is horrible. I can kind of understand the security purpose behind it and figured it would only wipe internal storage but SD as well with no option to turn off?! This should be something you CHOOSE to happen after 10 failed attempts. Especially if you have that one A$$hole friend (I'm sure a lot of you are picturing him now ) who thinks something like this would be hilarious.....Every time....
Click to expand...
Click to collapse
I was on my last attempt one day while my phone was in my pocket, using knock code. So this makes me nervous about wiping it again accidentally.
THEbigSWEEN said:
There was another thread started about this shortly after the phone was released. Is it true it erased your SD card as well?? There were a couple reports that it had for them. I made sure to back up my phone and routinely continue to do so in the off chance that someone does get a hold of it and unknowingly erases everything. This is a TERRIBLE "feature" and someone had said there was a file on a previous phone they had that was able to be edited to disable this, but as far as I know hasn't been found on the G3 yet. Though I'm not a dev by any means I plan on diving into the system files at some point, and hopefully can find something online to point me in the right direction... Believe me, I'm sure if I or someone else does find a way to disable it you will definitely see a thread for it, more than likely in the "General" section :good: Worst.....Feature.....Ever.....
Click to expand...
Click to collapse
Yes... This actually happened to my M8 while it was in my pocket. The screen came off sleep and I pocket swiped the wrong pattern. When I pulled the phone out EVERYTHING was gone.
I thought it was ridiculous that it gave you 10 tries... now that I know it wipes your phone, that's scary and not nearly enough.
I would much rather it just give you 3 or 4 tries and then require a backup pin or for you to type in or your google account password. It should never be able to wipe my phone unless I tell it too.
wow that is a serious shipping bug. I'm taking my phone lock off right now. They designed with guest log-on they so you hand your phone to somebody else to use and they designed it like that? Sounds like another enhancement for g3 tweakbox...set failed logon attempts to 10,000 with time delays in between.
---------- Post added at 05:06 AM ---------- Previous post was at 04:14 AM ----------
I found this http://repo.xposed.info/module/com.hamzah.lockscreentweakbox
---------- Post added at 05:36 AM ---------- Previous post was at 05:06 AM ----------
I installed the xposed module. I set it to unlimited but I also had the g3 tweakbox setting to show number of attempts. The number was still at ten max and I was unable to (can't wipe no backup) try more than 10 attempts.
After five, mine requires you to type a phrase to continue, so pocket shouldn't do it. And after that, you can use a pin or account info by selecting the bottom button that says forgot my code.
I certainly agree it should be a setting though.
Sorry this an old thread, but I would like to know as well. My toddler sometimes get a hold of my phone, and it ends up being factory reset. I hate this feature. If I have a issues with someone taking my phone and trying to access to it, I rather go through Google (phone locater) and erase it from there
ccrickets77 said:
Sorry this an old thread, but I would like to know as well. My toddler sometimes get a hold of my phone, and it ends up being factory reset. I hate this feature. If I have a issues with someone taking my phone and trying to access to it, I rather go through Google (phone locater) and erase it from there
Click to expand...
Click to collapse
The following is out of the box thinking and speculative since it's possibility of success depends on what happens if you completely wipe your recovery partition so that you no longer had any kind of recovery: neither stock nor custom. And knowing you couldn't easily get recovery back without flashing the 10B TOT. There'd be other possibilities to get it back, but I'd just flash the TOT under most circumstances.
You would have to be temporarily be rooted to do so.
This is the way I would go about it if I were interested in such a thing:
1. Restore to stock 10B KitKat by flashing the 10B_03 TOT using the .DLL that's extracted from the 35B KDZ (assuming you're on the 35B or higher stock unrooted ROM).
2. Root the phone with the Stump app.
3. Use TWRP Manager from the Play Store to install TWRP custom recovery.
4. Create a flashable zip from the individual partitions extracted from whichever stock ROM KDZ you wanted to be on, such as 47A Marshmallow.
5. Leave the stock recovery partition out of the zip, and adjust the updater-script to wipe the existing recovery partition on the phone.
6. Flash the ROM zip you've created. Once you exit TWRP, you won't have a recovery partition anymore, which as far as I know would be what would perform the actual factory reset. You'd still have the download mode partition because that's separate.
If someone triggered what would normally be a factory reset by guessing the wrong lock code 10 times, the phone would reboot and likely maybe have a blinking LED which would require you to either pull the battery or hold the power button in for 10-15 seconds or so to force the phone to boot.
If I were going to test such a method, I'd use the built in LG Backup to back up all my user apps and data and move everything I want to save from my internal storage to my MicroSD card, then I'd eject the card and leave it until done testing.
Then upon following the steps to do all this, I'd test the theory out immediately by setting a secure lock screen and using the wrong password/PIN/pattern 10 times and make sure you can recover the way I described by pulling the battery or holding down the power button long enough.
No sense restoring apps or even putting your Google account info in while testing this.
At the worst, you'd have to flash the 10B TOT or any KDZ such as 47A again to recover, or very worst have to follow QHSUSB_BULK 9008 mode recovery directions which would also make use of the TOT file.
If you decide you're brave enough to test, I'd be willing to make the flashable zip for you.
You can uncheck "Android Device manager" under Settings --> Security --> Device Administrators ... i done for Lenovo vibe mobile !!!
Hello,
Today, I came back home and put my phone on my desk.
I went outside the room for a couple minutes, and when I came back, the phone was turned off.
I thought the battery got emptied, so I plugged the phone to the charger. The phone turned on, but instead of my custom start screen, the default Cyanogenmod screen was up.
Then, I got the "Encryption Unsuccessful" message, saying the only way to recover my phone is to wipe it and hope google backed enough stuff.
Now, I still haven't used the button on the bottom of the screen. I went to the recovery mode, thinking maybe I could back up stuff before I wipe everything.
My question is: Is there a way to restore back my phone without wiping everything? I tried to back everything up to the SD card, but the backup stopped once it reached the /data folder, which I assume, is the source of the problem. Can the problem be solved by formatting the /data folder from the recovery mode? I also currently don't have any clockwork backups, thus I cannot use recovery to restore everything to the way it was.
Please help, I have very important information on my phone and I'd hate to lose it.
The data folder is where all your information is stored. There are many threads where people have tried to recover data from a brick, I've not heard a single success.
You could just try flashing the exact same rom you already had, without a wipe. That might cure any system issues but won't help corrupt data.
It sounds like your phone has suffered a partition corruption or failure.
boomboomer said:
The data folder is where all your information is stored. There are many threads where people have tried to recover data from a brick, I've not heard a single success.
You could just try flashing the exact same rom you already had, without a wipe. That might cure any system issues but won't help corrupt data.
It sounds like your phone has suffered a partition corruption or failure.
Click to expand...
Click to collapse
And what could possibly cause that?
As I said, I didn't do anything special or risky to the phone. The Cyanogenmod has been installed on it for a year and a half, so I don't think that's the problem.
Is there a way to extract some folders from the phone? I tried to plug it with a USB to the computer, but aside from the name, all information is unknown.
Also, will flashing the exact same rom will work? And what do you mean by "won't help corrupt data"? How do I know which data is corrupted?
And as I asked, will formatting the /data folder through the recovery mode will work? Can it cause damage?
I'm sorry for asking so many questions, I'm trying to be really careful with that and I need to fully know what I'm doing.
Thank you for replying.
Try ADB pull or aroma file manager in recovery, but if data partition is corrupt then your data is already lost.
boomboomer said:
Try ADB pull or aroma file manager in recovery, but if data partition is corrupt then your data is already lost.
Click to expand...
Click to collapse
It says "device not found". does that mean my data is lost?
And can you please answer my other questions?
Thank you for your help.
Edit: In case I do have to reset my phone, can someone guide me how to do it step by step?
I don't want something to mess up and get no help or wait hours for an answer.
FlyingPotato said:
or wait hours for an answer.
Click to expand...
Click to collapse
Take it to a service centre and pay them to help you.
okay nvm, I used the button on the bottom and it did the trick.
I should probably start backing up things more often because right now I use a backup from a year ago.
Thank you for your help.
I think I'm screwed here. My tablet locked up and I force-powered it down. When it restarted, it went into a soft bootloop and won't load the OS. I'm able to get to my custom recovery and attempted to restore a backup I made in TWRP, but every time I try to restore it displays the screen shown in attached Pic 1, gets to 20% and reboots the tablet. I tried installing a custom ROM and got pretty much the same error (see Pic 2). I can't even wipe the device for some odd reason. All it does is reboot the system. I can get to the screen shown in Pic 3, but I'm not quite sure what my options are. Do I need to factory reset, or do I have a paperweight. I'll sideload if I have to, but I'm not sure of the best way to do this. I'm throwing myself on everyone's mercy here! AAAAAAAGH!
When all else fails, flashing the factory image with fastboot usually will solve the problems.
Sent from my SM-T820 using XDA-Developers Legacy app
jd1639 said:
When all else fails, flashing the factory image with fastboot usually will solve the problems.
Sent from my SM-T820 using XDA-Developers Legacy app
Click to expand...
Click to collapse
I tried flashing the factory image and it appears to have crapped out. See attached image. I think I got a real problem here .
Joe_6pak said:
I tried flashing the factory image and it appears to have crapped out. See attached image. I think I got a real problem here .
Click to expand...
Click to collapse
Think this is a better screencap.
Interesting that bootloader and recovery flash but then nothing else. Try downloading the factory image again. I have seen downloads being corrupted before.
jd1639 said:
Interesting that bootloader and recovery flash but then nothing else. Try downloading the factory image again. I have seen downloads being corrupted before.
Click to expand...
Click to collapse
Think I should stick with Nougat or download the original factory image (5.0, LRX21Q) that it shipped with? I've also heard rumors that it may be a faulty USP port or cable. Thoughts?
It should not matter which version of the factory image. It possibly could be a bad cable. Also, use the usb ports in the back of the computer, not the front, if you're using a pc. I haven't seen this being a problem with nexus devices but it has been on some samsung devices and odin.
jd1639 said:
It should not matter which version of the factory image. It possibly could be a bad cable. Also, use the usb ports in the back of the computer, not the front, if you're using a pc. I haven't seen this being a problem with nexus devices but it has been on some samsung devices and odin.
Click to expand...
Click to collapse
Okay. I used the back USB port and a different cable and I tried flashing the latest Nougat image. Went through without a hitch and it started up but hung on the splash screen and kept rebooting. Flashed the original image and the tablet started up but I got the dreaded "Enter your password" screen. Had NO idea what my password was, so I entered the first PIN that I thought I may have used. Well, that wasn't it, so it took me to a Factory Reset screen because it said I had corrupt data. After a lengthy "erasing" screen, the tablet fired up and I'm back where I started on Day 1. I have no idea if I am still rooted or if my custom recovery survived, but I'm kinda glad the thing at least got started again. My bootloader is still unlocked, and I made sure the "Enable OEM Unlock" box was checked in developer options. Since I just use this for games, email, video watching and an occasional Facebook glance, I'm really not concerned if I'm rooted or not. Obviously I'd like to be, but I'd rather make sure the tabled is updated by a download from Google first. I think my use of Flashfire is what screwed me up in the first place.
Long story short, I'm back up and running, but its 2014 all over again. Will I be able to take the factory update from Google with an unlocked bootloader, and will it be to the latest version of Android? Do you think my custom recovery survived, and is it worth the bother to root and flash it for a (mostly) gaming device? The only thing I can think of that I would want root for is Stickmount (to transfer files) and to get Google Assistant (which I'm pretty sure that I could back-door through Nova Launcher). Oh, yeah, and the adblocking. Let me know what you think. I TRULY appreciate the help, and I'm glad this resource is out there for noobs like me to make it through the Google menagerie.
By the way, does anyone think that going from system to systemless root is what may have caused this?
I'm glad you're up and running. System or systemless should not have made a difference. I'm sure you no longer have a custom recovery or are rooted. I'm guessing you will get an OTA update from Google
jd1639 said:
I'm glad you're up and running. System or systemless should not have made a difference. I'm sure you no longer have a custom recovery or are rooted. I'm guessing you will get an OTA update from Google
Click to expand...
Click to collapse
It took the update just fine. No Google Assistant, but I'll keep trying. Thanks a bunch. REALLY couldn't have done it without your help!
Joe_6pak said:
It took the update just fine. No Google Assistant, but I'll keep trying. Thanks a bunch. REALLY couldn't have done it without your help!
Click to expand...
Click to collapse
Google removed Assistant support from tablets
The Auto Rotation worked on Miui, and then Lineage when I flashed it. But YouTube didn't work
Then I wanted to try Pixel experience, youtube still didn't work, then auto rotate didn't work
Then I tried Havoc, my favorite UI so far; youtube finally worked, but auto rotate still didn't work, and now Fire Emblem wouldn't install via APK or show up as compatible in the play store...
I want to know if there's a fix for auto rotate or a lightweight rom that will give me rotate and spare me from app issues.
Chocolina said:
The Auto Rotation worked on Miui, and then Lineage when I flashed it. But YouTube didn't work
Then I wanted to try Pixel experience, youtube still didn't work, then auto rotate didn't work
Then I tried Havoc, my favorite UI so far; youtube finally worked, but auto rotate still didn't work, and now Fire Emblem wouldn't install via APK or show up as compatible in the play store...
I want to know if there's a fix for auto rotate or a lightweight rom that will give me rotate and spare me from app issues.
Click to expand...
Click to collapse
Probably caused rotation bug yourself, dont remember exactly now, but you wiped partition you shouldnt have wiped. Maybe vendor partition, im not 100% sure. Just flash stock rom, get everything working again, and dont wipe what you not supposed to wipe. Do it only on cache, data, system. Also, be sure to follow guides exactly when flashing stock rom, you can easily brick the device if you relock bootloader or do other mistakes.
Edit. Remembered, its persist partition. You wiped it and lost all your sensors. There is absolutely no reason to wipe it. Just do everything as suggested in tutorials and everything will work as its supposed to.
Plekst said:
Probably caused rotation bug yourself, dont remember exactly now, but you wiped partition you shouldnt have wiped. Maybe vendor partition, im not 100% sure. Just flash stock rom, get everything working again, and dont wipe what you not supposed to wipe. Do it only on cache, data, system. Also, be sure to follow guides exactly when flashing stock rom, you can easily brick the device if you relock bootloader or do other mistakes.
Edit. Remembered, its persist partition. You wiped it and lost all your sensors. There is absolutely no reason to wipe it. Just do everything as suggested in tutorials and everything will work as its supposed to.
Click to expand...
Click to collapse
Any wiping I did was Dalvik, Internal, Data, System, and Cache, and if you can even count it, SD and OTG. There were no options to wipe vendor. Maybe vendor got overwritten, but I never specifically went to an option where I could wipe or delete any partitions. Everything I do/did was is in the Wipe or Install menu, with the exception of language change.
But now everything is destroyed because the mi flash tool bricked my device. I now learned that what the tool is known for, but being my first Xiaomi devices, it's not exactly on the user manual or common knowledge that Xiaomi likes bricking devices. I only heard of it after I started having problems
I wasn't cautious about the actions I was making because never before had I owned a device I couldn't recover from, including bricks. So I figured anything I did, I could just reverse it and go to stock
Chocolina said:
Any wiping I did was Dalvik, Internal, Data, System, and Cache, and if you can even count it, SD and OTG. There were no options to wipe vendor. Maybe vendor got overwritten, but I never specifically went to an option where I could wipe or delete any partitions. Everything I do/did was is in the Wipe or Install menu, with the exception of language change.
Click to expand...
Click to collapse
Well thats how it happens. You delete persist partition and you lose sensors. And im 100% sure thats what happened to you. So doesnt matter what you think you did or didnt, fact is it happened. Flash stock rom and fix it.
Plekst said:
Well thats how it happens. You delete persist partition and you lose sensors. And im 100% sure thats what happened to you. So doesnt matter what you think you did or didnt, fact is it happened. Flash stock rom and fix it.
Click to expand...
Click to collapse
Flashing stock rom is what bricked my device
Chocolina said:
Flashing stock rom is what bricked my device
Click to expand...
Click to collapse
Again, didnt follow guide properly then. Everyday hundreds of people do these things and nothing bad happens. Probably choose bad settings in flash software, like lock bootloader again
Plekst said:
Again, didnt follow guide properly then. Everyday hundreds of people do these things and nothing bad happens. Probably choose bad settings in flash software, like lock bootloader again
Click to expand...
Click to collapse
Im not arguing my ineptitude, you're right...
But the official flashing tool shouldn't be bricking devices regardless if there is or isn't a locked bootloader option, and should probably warn the user before hand the risks.
The flashing tool is supposed to be saving people from bricks, not causing them. Until I bricked my device, I wasn't seeing the "oh man I bricked my device using this" or "don't do this you'll brick your device" comments, it wasn't until after I did, did I have to search my issue.
But I've had time to sit down and tinker, I did manage to get it up and running regardless that the bootloader was locked.
Now my biggest regret is how I had to mangle the paint job just to get the damn thing open. By far one of the most difficult covers I had to remove
Chocolina said:
Im not arguing my ineptitude, you're right...
But the official flashing tool shouldn't be bricking devices regardless if there is or isn't a locked bootloader option, and should probably warn the user before hand the risks.
The flashing tool is supposed to be saving people from bricks, not causing them. Until I bricked my device, I wasn't seeing the "oh man I bricked my device using this" or "don't do this you'll brick your device" comments, it wasn't until after I did, did I have to search my issue.
But I've had time to sit down and tinker, I did manage to get it up and running regardless that the bootloader was locked.
Now my biggest regret is how I had to mangle the paint job just to get the damn thing open. By far one of the most difficult covers I had to remove
Click to expand...
Click to collapse
It shouldnt, same as you shouldnt be flashing custom made roms by random developers. Yet we do . If you only use phone as it was supposed to be used, and flash only official firmwares you will never brick.
Plekst said:
It shouldnt, same as you shouldnt be flashing custom made roms by random developers. Yet we do . If you only use phone as it was supposed to be used, and flash only official firmwares you will never brick.
Click to expand...
Click to collapse
Can you give backup files persistant twrp ? I lost my sensors too.. flash to stockrom is so harmful ..