My XT1575 just decided to go into a bootloop a week ago on its own, literally. I was just checking traffic on Google maps when I noticed it started to lock up. Finally, I see the Motorola splash screen, and that was the beginning of it. Went into recovery mode and tried a factory reset, clear cache partition, etc. but no luck. I've tried everything under Android 6.0 here but it continues to bootloop no matter what I do.
It's not rooted and the bootloader is locked, so I don't think I can even install TWRP or any custom recovery. I have never even though of enabling USB debugging so that's out of the question. What's odd is after trying all sorts of things, sometimes, after the phone has been off for a while I would power it on and it would actually boot into the Welcome screen. Shortly after that though, it locks up and starts bootlooping again. I don't know what else I can do about this or if it's recoverable. I hope someone can help. If it's of any significance, when in recovery mode, at the top I see what I think is the firmware it's currently on -- motorola/clark_retus/clark 6.0/MPHS24.49-18-4/5. Please help!
Update - After having my XT1575 powered off overnight, I powered it on this morning and it was able boot all the way into the Welcome screen, setup, etc. Right away I went and turned on USB Debugging and Allow OEM unlock. Tried rebooting and again it fails to boot. What's weird is it randomly seems to boot when it wants, and something must be corrupt but I just don't know what it could be. Does anyone have any ideas?
Don't unlock the bootloader.
If it is locked and behaving that way you should be able to get a warranty fix out of Lenovorola. If you unlock the bootloader you void your warranty, and they might choose to not honor it even if you say the problem started before.
Painful and slow as it might be, I'd recommend working with the manufacturer on this one.
jason2678 said:
Don't unlock the bootloader.
If it is locked and behaving that way you should be able to get a warranty fix out of Lenovorola. If you unlock the bootloader you void your warranty, and they might choose to not honor it even if you say the problem started before.
Painful and slow as it might be, I'd recommend working with the manufacturer on this one.
Click to expand...
Click to collapse
Yes undo what you just did an follow this guy
jason2678 said:
Don't unlock the bootloader.
If it is locked and behaving that way you should be able to get a warranty fix out of Lenovorola. If you unlock the bootloader you void your warranty, and they might choose to not honor it even if you say the problem started before.
Painful and slow as it might be, I'd recommend working with the manufacturer on this one.
Click to expand...
Click to collapse
I'm afraid it's too late for the bootloader, since it was one of the things I was trying out of desperation. After trying fastboot flashing the stock firmwares, I still get bootloops and strangely enough I was able to use the phone the other day for several hours before it started bootlooping again Thing is, it seems to behave differently at random times. Sometimes it makes it all the way up to the "Android is upgrading" screen but then freezes and reboots.. Other times it locks up at the Motorola splash screen and reboots.. And sometimes it even boots all the way up, is usable for a little bit, then begins bootlooping on its own.
I'm just wondering if something is corrupt software-wise (boot? system? etc?) or if it's a hardware issue. How do I even tell at this point?
iflyimpilot said:
I'm afraid it's too late for the bootloader, since it was one of the things I was trying out of desperation. After trying fastboot flashing the stock firmwares, I still get bootloops and strangely enough I was able to use the phone the other day for several hours before it started bootlooping again Thing is, it seems to behave differently at random times. Sometimes it makes it all the way up to the "Android is upgrading" screen but then freezes and reboots.. Other times it locks up at the Motorola splash screen and reboots.. And sometimes it even boots all the way up, is usable for a little bit, then begins bootlooping on its own.
I'm just wondering if something is corrupt software-wise (boot? system? etc?) or if it's a hardware issue. How do I even tell at this point?
Click to expand...
Click to collapse
The random nature of what you're describing does sound like hardware. Consider a full restore where you fastboot flash everything back to stock of you haven't already.
Check logs. See if you're getting anything in last_kmsg. Use an app like syslog if you aren't used to pulling them, though you might have to use adb if you aren't getting through boot all the time.
jason2678 said:
The random nature of what you're describing does sound like hardware. Consider a full restore where you fastboot flash everything back to stock of you haven't already.
Check logs. See if you're getting anything in last_kmsg. Use an app like syslog if you aren't used to pulling them, though you might have to use adb if you aren't getting through boot all the time.
Click to expand...
Click to collapse
Thanks for replying. I've tried fastboot flashing everything and even going into recovery and clearing cache partition as well as doing a factory data reset. I'm afraid it may very well be hardware. I'll try your suggestion about the logs.
Is 'last_kmsg' a line I should be looking for in the log? If so, what would I need to see in order to determine whether or not it's a hardware problem?
iflyimpilot said:
Thanks for replying. I've tried fastboot flashing everything and even going into recovery and clearing cache partition as well as doing a factory data reset. I'm afraid it may very well be hardware. I'll try your suggestion about the logs.
Is 'last_kmsg' a line I should be looking for in the log? If so, what would I need to see in order to determine whether or not it's a hardware problem?
Click to expand...
Click to collapse
/proc/last_kmsg is a log file that should get written to if a kernel panic causes a reboot in theory. In practice I find it is often blank even after a random reboot.
iflyimpilot said:
I'm afraid it's too late for the bootloader, since it was one of the things I was trying out of desperation. After trying fastboot flashing the stock firmwares, I still get bootloops and strangely enough I was able to use the phone the other day for several hours before it started bootlooping again Thing is, it seems to behave differently at random times. Sometimes it makes it all the way up to the "Android is upgrading" screen but then freezes and reboots.. Other times it locks up at the Motorola splash screen and reboots.. And sometimes it even boots all the way up, is usable for a little bit, then begins bootlooping on its own.
I'm just wondering if something is corrupt software-wise (boot? system? etc?) or if it's a hardware issue. How do I even tell at this point?
Click to expand...
Click to collapse
going by that logic the thing that you should have done was get a factory image from moto and flash to stock using moto tools if that failed at fixing it then send into moto it might not be lost yet but the more you progress the more less likely to replace the phone moto is...
it sounds like something is going bad could be ram emmc or the soc
What i would do is get into discussions with lenovo to see if they can get you fixed up. if you unlocked the bl they know be straight with them. if you get nowhere and no rom you load can fix it sell as parts replace at your expense...
Related
Hey guys, i received a Samsung Focus i917 rev 1.3 from a guy who wanted to put that phone back to factory state. Im dont have a lot of experience on windows phones other than the HTC versions. Anyway, i performed a factory reset on the phone but the data didnt deleted at all. Now, i understand as far as i know that those phones need the SD card in order to work fine. That phone didnt have one, but it was working though. Thing is i decided to flash it with stock ATTJK2 and when i flashed it everything went fine. But the phone now stays on the Samsung logo for some minutes and reboots. When i say this case is different is because i can get to download mode as many times as i want, i can perform factory reset using hardware buttons and everything. In fact, i even installed MAGLDR and a custom rom trying to solve this but even though everything went well phone is still stuck on that logo. So my question is, should i insert a working SD for that phone and then flash it? Is it worth the try? Or is this phone just a brick? Cus my guess unbricking it wont solve it since the phone can reach download mode.... Help please and thanks for your help as always
enelyam said:
Hey guys, i received a Samsung Focus i917 rev 1.3 from a guy who wanted to put that phone back to factory state. Im dont have a lot of experience on windows phones other than the HTC versions. Anyway, i performed a factory reset on the phone but the data didnt deleted at all. Now, i understand as far as i know that those phones need the SD card in order to work fine. That phone didnt have one, but it was working though. Thing is i decided to flash it with stock ATTJK2 and when i flashed it everything went fine. But the phone now stays on the Samsung logo for some minutes and reboots. When i say this case is different is because i can get to download mode as many times as i want, i can perform factory reset using hardware buttons and everything. In fact, i even installed MAGLDR and a custom rom trying to solve this but even though everything went well phone is still stuck on that logo. So my question is, should i insert a working SD for that phone and then flash it? Is it worth the try? Or is this phone just a brick? Cus my guess unbricking it wont solve it since the phone can reach download mode.... Help please and thanks for your help as always
Click to expand...
Click to collapse
You can definitely try inserting a SD card and see. I'd say it's definitely worth trying. It would be best to match the original SD card it had, if possible. But even so, remember it's not guaranteed it will work.
If you'd search the forum for "stuck in loop" or "stuck at samsung logo" you'd see it's not a rare problem, unfortunately.
I have same problem with two different phones, the one started with be stuck in the loop. No matter what I have tried it will not break the loop, everything flashes fine but never boots. Second one started out working, but factory default wouldn't completely clear data. Very odd...
Well, seems like these phones are not worth a penny then. Its incredible that something like that could happen to a smartphone, So many things that go wrong with them, Im going to put them in the no no list togheter with the Razr. Worst phones to deal with... And yes ive seen its very common to find this issue. Which is why i think theyre worthless
enelyam said:
Well, seems like these phones are not worth a penny then. Its incredible that something like that could happen to a smartphone, So many things that go wrong with them, Im going to put them in the no no list togheter with the Razr. Worst phones to deal with... And yes ive seen its very common to find this issue. Which is why i think theyre worthless
Click to expand...
Click to collapse
I'd say that is your experience and your perspective. Normally, you are NOT supposed to flash custom ROMs and you have been warned that if you do it you RISK bricking your phone. This is a new platform and the process of flashing is not yet 100% understood.
I've warned folks several times about flashing MAGLDR, it seems that only *some* phones have this "stuck" issue and in 99% cases they are related to flashing custom roms. To add more, no one has a fix (not even the guru's), which tells me the issue is most likely unfixable by software (much like an old bios reflash, might require taking out a chip). It might be a later batch of phones that use a specific chip, it might be something else. Point is you're flashing something on your own risk. And saying the phones aren't worth a penny just because you don't want to accept the risk of doing something potentially dangerous is a bit stretchy. And that's my perspective. To add on that, all phones should be looked for the capabilities and what they do, not just for modding. Focus has a replacement for the custom roms, you can achieve the same by installing packages yourself, without unnecessary risks.
Well, im sorry if something was misunderstood. I didnt mean to hurt feelings in here M8. But the thruth is that the phone was completely stock, i just wanted to delete the old data. So decided to flash it with official ATT firmware, it wasnt custom firmware. But since the phone didnt wanted to delete the data after factory reset(which for starters its odd) i tried flashing it and it flashed perfectly according to the flashing software. But it was stock Att, and the phone got stuck in samsung logo after the flash. Never made it further, i mean its not an unusual issue around here so thats why i said that. After that happened is when i tried to install MAGLDR, which installed perfectly also. But when i tried to flash a rom the phone just did the same, stuck in samsing logo also. In fact, i can still flash whatever i want on it, it goes to download mode perfectly, but no matter what i flash on it, it will stay on the samsung logo after that... Anyway, my bad on saying that those phones are not worth it. There maybe more people willing to have a phone which they wont know if it will boot when they turn it off, or maybe not delete their data when they wan to factory reset the phone. Im not one of those thats all. But i do respect your work dont get me wrong, its just that some odd situations like this makes people think twice when buying a phone.
Right mate, I get your point. No harm
If it makes any difference, happened to my wife's phone during normal Zune update, got the logo-loop. Was fixed by reflashing stock rom. Painful, but it worked. In your case it seems something was wrong with the flash, not being able to delete data after factory reset is indeed at least weird. Sorry you had a bad experience, I guess some of those happen every now and then...
Hello,
I am having issues finding what the problem is on my phone. The problem all started when I rooted and installed a custom rom on my galaxsy s5. It worked perfectly for a couple of months. Then I started noticing this weird issue whenever I plugged in any headphones the phone would automatically restart. I didn't really look into the problem like that and just kept it the way it was, since I used bluetooth alot.
The problem progressed to the point that when it restarted itself it would go into a boot loop. I would have to take out the battery wait a few seconds then plug it back in. At this point I decided to restore back to stock firmware. But this made the problem worse. Now its a 15% chance the phone boots up normally, and 85% chance it boots to a black screen. By black screen I mean it boots up normally but I cannot see anything on the screen. I hear the sounds, and touch still works.
If I am lucky and it boots up normally it works perfectly for a few hours. Then at randomly when I put the phone to sleep it restarts itself. There is no reason I can think is causing this problem.
Phone Info:
Model: G900T 16GB
Firmware: Stock 5.0
Flashed With: Odin 10.x.x
Please help me diagnose my problem so I can fix it.
Possible Hardware Issue:
Digitilizer/LCD : Black screen explains this. But also if I do not put the phone to sleep it will work for days. Boot screen, Download Mode, Recovery all work without problem.
Internal Memory - Could be, that means I have to throw the phone away. But wouldn't nothing also work...
Click to expand...
Click to collapse
Possible Software Issue:
Corrupt Rom/Cache: Flashed several different kinds of stock rom, all with same result. Used recovery to delete cache.
Virus: Yeah leaning towards this.. Maybe somehow hooked itself to the core aspects of the phone.
Recovery/Download Mode Corrupt: This part of the phone is corrupt. 15% chance of booting to recovery. And Download Mode doesn't delete all user data.
Click to expand...
Click to collapse
Flash the correct PIT file along with (Same time) as a stock ROM, if the problem persists, hardware is the issue
*Detection* said:
Flash the correct PIT file along with (Same time) as a stock ROM, if the problem persists, hardware is the issue
Click to expand...
Click to collapse
um.. maybe you are right. Motherboard most likely huh.
You had really serious problem, do you try Initializing via kies3 already?
dimas03 said:
You had really serious problem, do you try Initializing via kies3 already?
Click to expand...
Click to collapse
I will try as a last resort, since 5.1.1 is unrootable. You know whats weird I am not having any issues now. I will let it stay like this until it gives me a problem. As a computer science major this is pissing me the fck off. Not being 100% sure that it is a hardware problem.
Hey all,
First post here on XDA and I'm hoping someone with more experience than me will be able to give me a hand! Until last week or so, I was running an up-to-date version of Lollipop (5.1.1), when my tablet started randomly freezing up on me, requiring "soft resets" to get it going again, or simply shutting off on me. Thinking it was software related, I tried wiping the cache with no success, so ended up doing a full factory reset. The issues *seemed* to clear up for a day or so, but came back, and so figuring it was Lollipop related, I wiped out the OS and installed CM12.1 (which was my first experience working with ADB and fastboot, and first time installing a non-stock ROM) with a TWRP recovery. A few days later, the freezing and shutting down issues began popping up again, with the shutdowns *usually* happening during sleep, but the freezing happening at anytime from initial "Google" logo to boot animation, to the middle of running an app. I had made a backup on TWRP when I got CM12.1 configured the way I wanted it, so I performed a soft reset when it froze on me, and booted into the bootloader. The tab kept freezing in the TWRP window before I could select a restore, so out of desperation I tried just doing a factory reset from within TWRP. Long story short, something must have happened during that reset, because it kept hanging on the boot screen. I thought I may have unknowingly messed something up, so I tried downloading and flashing a stock KitKat (4.4) ROM from Google's site, but kept encountering bootloader errors during the flashing and ended up only being able to boot to the bootloader screen (apparently got a faulty 4.3 bootloader in that ROM, which gave me a headache until I was able to get straightened out). I have been able to get a stock bootloader (4.23) up and running now, along with a stock recovery (going with Lollipop now, so stock for LMY47V) going, but that's it. I've tried flashing the stock lollipop image via shell script (I'm running a Fedora 23 machine), via individual commands, and via "fastboot update -w factory_image.zip" without success. ADB sideload still works via recovery, but I wasn't able to sideload the OTA packages for 5.1 either. The common errors that pop up seem to indicate an error (corruption? fragmentation?) on the cache partition, but I'm not a dev when it comes to Android, so I'm at a loss here... I keep getting "E: failed to mount /cache (Invalid argument)", and other errors associated with accessing/opening files further down the /cache tree. Would this error be more likely to be a hardware issue, or would it be a software/firmware issue? I've had similar errors before with USB drives, when they would start to bad and partitions begin failing, but have always been able to rebuild them and get my data back. If something like this is happening on my N7 and the cache partition has indeed become somehow corrupted and failed (but not physically....), is it possible at all to rebuild partitions on Android in a similar manner? I've scoured the web, but haven't been able to find anything that can help me out with something like that, so I figured my best bet before condemning the N7 to the junk drawer was to see if any of the pros around here had any words of wisdom that *might* get me back up and running. Thoughts and advice much appreciated!!
Thanks!
(Oh, I apologize for the lengthy post, but I wanted to be sure to provide enough background info..... Sorry for the lengthy read!!)
Honestly that sounds more like a hardware problem than a software problem.
During the early stages of booting, everything that happens is extremely deterministic - meaning that it should be completely repeatable in terms of the order & timing in which activities occur.
So, for it to behave erratically during early boot suggests that it is not software, but marginal hardware. If hardware is barely meeting logic levels or timing requirements, a small amount of random noise (which is always present) can cause a fault to occur at any time - and that sounds approximately like what you are observing.
Further, you replaced your ROM entirely and the problem persists - again suggesting that the problem is hardware, not software.
The most cost effective way of dealing with repair of a $200 tablet is - unfortunately - disposing of it and buying a replacement.
Sorry.
Thanks for the reply!! Shoot, that's what I was leaning towards too. What is the life expectancy of these tablets? I mean, I got 3 good years of use out of it, so I'm not going to complain, but it seems like they should have lasted longer... Would it be worthwhile to maybe grab a cracked screen N7 off eBay for parts and try to get my tab working with those parts maybe? I'm hoping the rumors are true about Google coming out with a new tab this fall, but I'd love to get mine working before then lol...
This is the second time I get this message. First time was on stock Android 7.0. next time, ~2 weeks later on stock Android 7.1.1. To revive my phone I had to perform a factory reset twice.
What causes this message? Is it software or hardware related? I assumed the former, but the fact that it happened twice after a reset and on a new version made me wonder...
I'm heading to a country without 3G coverage and barely any WiFi, so if this happens then, I'm screwed on 2 levels: -Loss of pictures, due to not able to back-up -Not able to reset, since that requires WiFi.
Anyone else who had this issue? Any recommendations, RMA?
Full error message: "Decryption unsuccessful" The password that you entered is correct but unfortunately your data is corrupt. To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google account"
Thx.
You can set the phone to back up without wifi if you are good with that I've had my phone since December I have not had that happen odd.
Sent from my Nexus 6P using Tapatalk
gjkrisa said:
You can set the phone to back up without wifi if you are good with that I've had my phone since December I have not had that happen odd.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
And how would you do that? Can't seem to find any way to do that...
In Google photos there is in settings also drive after that I believe the rest of settings will back up w/o wifi I know photos will
Sent from my Nexus 6P using Tapatalk
Dytoonn said:
This is the second time I get this message. First time was on stock Android 7.0. next time, ~2 weeks later on stock Android 7.1.1. To revive my phone I had to perform a factory reset twice.
What causes this message? Is it software or hardware related? I assumed the former, but the fact that it happened twice after a reset and on a new version made me wonder...
I'm heading to a country without 3G coverage and barely any WiFi, so if this happens then, I'm screwed on 2 levels: -Loss of pictures, due to not able to back-up -Not able to reset, since that requires WiFi.
Anyone else who had this issue? Any recommendations, RMA?
Full error message: "Decryption unsuccessful" The password that you entered is correct but unfortunately your data is corrupt. To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google account"
Thx.
Click to expand...
Click to collapse
Did you experience any random reboots?
When you say stock you confirm that it's full stock (no root and running google's kernel) ?
rchtk said:
Did you experience any random reboots?
When you say stock you confirm that it's full stock (no root and running google's kernel) ?
Click to expand...
Click to collapse
Never had any troubles with random reboots.
My phone froze, got unresponsive. I had to restart, and when it tried to boot I got this message. This happened twice.
No root, standard kernel. Bootloader not even unlocked.
Dytoonn said:
Never had any troubles with random reboots.
My phone froze, got unresponsive. I had to restart, and when it tried to boot I got this message. This happened twice.
No root, standard kernel. Bootloader not even unlocked.
Click to expand...
Click to collapse
That's it. Storage corruption and the decryption unsuccessful is a consequence of your problem.
Sorry but that looks like a defective device.
ram/emmc/power, it's hard to find without root/twrp. Unless an update got wrong but I don't think that would show these symptoms.
First, I would also raise a PR on google to see what they suggest: https://source.android.com/source/report-bugs.html
You really need to backup your data and have a backup phone in case the following gets you a brick..
I'd actually try flashing factory images (you won't be able to flash recovery image but others yes ). Make sure to record the messages returned on your PC to see if something went wrong. The update process is a bit dumb, it goes on even if errors are encountered so even if it finishes it doesn't mean much.
Once the device is flashed, if it boots, you could try filling your data partition by moving big files using usb transfer. When its full, reboot and see what's happening.
If you are short on time, prepare the RMA process...
edit: oh btw, I'm sure people would be interested to get the information displayed in bootloader mode (power on the phone by pressing volume down)
rchtk said:
That's it. Storage corruption and the decryption unsuccessful is a consequence of your problem.
Sorry but that looks like a defective device.
ram/emmc/power, it's hard to find without root/twrp. Unless an update got wrong but I don't think that would show these symptoms.
First, I would also raise a PR on google to see what they suggest: https://source.android.com/source/report-bugs.html
You really need to backup your data and have a backup phone in case the following gets you a brick..
I'd actually try flashing factory images (you won't be able to flash recovery image but others yes ). Make sure to record the messages returned on your PC to see if something went wrong. The update process is a bit dumb, it goes on even if errors are encountered so even if it finishes it doesn't mean much.
Once the device is flashed, if it boots, you could try filling your data partition by moving big files using usb transfer. When its full, reboot and see what's happening.
If you are short on time, prepare the RMA process...
edit: oh btw, I'm sure people would be interested to get the information displayed in bootloader mode (power on the phone by pressing volume down)
Click to expand...
Click to collapse
Thanks for your reply.
I sent it for an RMA, so unfortunately not able to do what you described. Couldn't chance it getting this error message when abroad.
Curious though if they will grant an RMA, nothing much is looking wrong at the moment. Hope they will, because else I'm screwed.
If they don't, though, I'll see if I can get the information displayed in bootloader mode.
I'm having the same issue.
Same message, only I'm BL unlocked, rooted and twrp.
It happened twice. Once on 7.1 DP1, and again on DP2.
Once I get into recovery, the system is encrypted, and I can't do a thing.
I'm going to try and back up to a flash drive, and try to mount that in twrp if it happens again.
rwj5279955 said:
I'm having the same issue.
Same message, only I'm BL unlocked, rooted and twrp.
It happened twice. Once on 7.1 DP1, and again on DP2.
Once I get into recovery, the system is encrypted, and I can't do a thing.
I'm going to try and back up to a flash drive, and try to mount that in twrp if it happens again.
Click to expand...
Click to collapse
Recent Twrp now supports full disk encryption so you should be able to see your files? And even do a backup from there. Take twrp 3.0.2-3
rchtk said:
Recent Twrp now supports full disk encryption so you should be able to see your files? And even do a backup from there. Take twrp 3.0.2-3
Click to expand...
Click to collapse
Strange, that's exactly the version I'm using.
rwj5279955 said:
Strange, that's exactly the version I'm using.
Click to expand...
Click to collapse
Weird. I don't have twrp so I can't check but you should see your data. Maybe the partition needs to be mounted (I think it is by default though). No /data/media ? /sdcard is the same but as a virtualized FAT file system to be able to be access from Windows. Could be that /sdcard is empty in twrp but /data/media shouldn't.
rchtk said:
Weird. I don't have twrp so I can't check but you should see your data. Maybe the partition needs to be mounted (I think it is by default though). No /data/media ? /sdcard is the same but as a virtualized FAT file system to be able to be access from Windows. Could be that /sdcard is empty in twrp but /data/media shouldn't.
Click to expand...
Click to collapse
I'll have to look if it happens again.
I only remember trying to access /sdcard. Empty
https://twrp.me/faq/datamedia.html
Same issue , rooted and twrp noto e4 plus , any help ? Idk what's is going on
Joeykatie said:
Same issue , rooted and twrp noto e4 plus , any help ? Idk what's is going on
Click to expand...
Click to collapse
If I understand this thread flash custom kernel like ElementalX to unencrypt your device.
Hey folks,
I did not find anything on this issue, seems to be rather unique. Let me describe the problem.
This is my father's Axon 7 and he wanted me to get him a different ROM on there, which I did, and it worked smoothly until today. It kept crashing, freezing and was literally unusable for unknown reasons.
So since he was going to be gone for the next few days, I had no choice but to remove the ROM and data and reflash it. HOWEVER I did not delete the internal storage since I did not think it would be necessary. Sitting in the setup, I had issues getting through it, it will not pop up the keyboard to let me type the wifi password neither does it let me pass through if I wanted to use mobile data. It simply gets stuck. Sometimes random android processes tend to crash and put me at the start of the setup and I can't get to the settings which does prevent me from enabling USB-debugging or OEM unlock.
If I try to get into the recovery (which is still on there) it will simply get stuck on the screen that says ZTE, did not work through fastboot either, same issue.
(I do personally think that some app data is corrupted and causes the issue, since I wiped everything except internal storage and I still have major issues)
So here am I, stuck. I hope someone can enlighten me, or tell me how stupid I am and point me at something completely obvious. Thanks
OmegaFighter said:
Hey folks,
I did not find anything on this issue, seems to be rather unique. Let me describe the problem.
This is my father's Axon 7 and he wanted me to get him a different ROM on there, which I did, and it worked smoothly until today. It kept crashing, freezing and was literally unusable for unknown reasons.
So since he was going to be gone for the next few days, I had no choice but to remove the ROM and data and reflash it. HOWEVER I did not delete the internal storage since I did not think it would be necessary. Sitting in the setup, I had issues getting through it, it will not pop up the keyboard to let me type the wifi password neither does it let me pass through if I wanted to use mobile data. It simply gets stuck. Sometimes random android processes tend to crash and put me at the start of the setup and I can't get to the settings which does prevent me from enabling USB-debugging or OEM unlock.
If I try to get into the recovery (which is still on there) it will simply get stuck on the screen that says ZTE, did not work through fastboot either, same issue.
(I do personally think that some app data is corrupted and causes the issue, since I wiped everything except internal storage and I still have major issues)
So here am I, stuck. I hope someone can enlighten me, or tell me how stupid I am and point me at something completely obvious. Thanks
Click to expand...
Click to collapse
well, you can use EDL maybe?
The fastest way out is downloading the A2017G_FULL_EDL file from our Russian friends and use MiFlash while in EDL mode to flash the cluster**ck of a phone that you have.
The closest thing I've seen was a friend's Galaxy Grand 2 (like 5 years old) that maybe had a part of the system corrupted or a slightly dead eMMC. a bunch of stuff just crashed for no apparent reason. I reflashed the system and it got fixed for some time, then it started doing some weird sh!t again (after booting, you have an 80% chance that it will just freeze forever, hard reboot needed). But let's hope for the best and see if you can recover it by reflashing stock totally. If it still doesn't work you might be able to relock the BL and claim the warranty
Choose an username... said:
well, you can use EDL maybe?
The fastest way out is downloading the A2017G_FULL_EDL file from our Russian friends and use MiFlash while in EDL mode to flash the cluster**ck of a phone that you have.
The closest thing I've seen was a friend's Galaxy Grand 2 (like 5 years old) that maybe had a part of the system corrupted or a slightly dead eMMC. a bunch of stuff just crashed for no apparent reason. I reflashed the system and it got fixed for some time, then it started doing some weird sh!t again (after booting, you have an 80% chance that it will just freeze forever, hard reboot needed). But let's hope for the best and see if you can recover it by reflashing stock totally. If it still doesn't work you might be able to relock the BL and claim the warranty
Click to expand...
Click to collapse
Hey,
After a long day I managed to fix it, I was able to use the adb in fastboot and could reinstall the recovery and managed to run it, deleted internal storage and reinstalled everything. Seems to have done the trick. I hope it will keep working now.
OmegaFighter said:
Hey,
After a long day I managed to fix it, I was able to use the adb in fastboot and could reinstall the recovery and managed to run it, deleted internal storage and reinstalled everything. Seems to have done the trick. I hope it will keep working now.
Click to expand...
Click to collapse
good