I've owned this phone for about a year now, it's really lightweight and cheap and it get's the job done most of the time. The only problem sometimes is the small storage size. It wanted to install an update on my device for some time but it never could because my storage was full, I didn't really care. Until one day I removed a ****ton of files because I wanted some more space. I put my phone on the charger and I went to sleep, I did not turn it off. The next morning when I want to check my notifications, I notice my phone is off. I turn it on and immediately get booted into this EMUI Huawei eRecovery screen. It gives me 4 options: "Download latest version and recovery", "Wipe data/factory reset", "Reboot", and "Shutdown". The Reboot and Shutdown options don't to anything to get me out of the menu, it just comes back up when I start my phone again. And obviously I want to stay away from a factory reset until it's actually necessary. So I tried the first option, it asked me to connect to a wifi network, which I did. It gives me the message "Getting package info from server" for a while, and then it says "Getting package info failed". Does anyone have an idea what causes this and how to fix it?
Greetings,
Tot
Ps: I did not install any custom roms nor did I root the device
Related
Two days ago my wifes 1st generation Nexus 7 refurb started giving the "Unfortunately, NFC service has stopped" error. You click OK and the error instantly pops up again. There is a moment to click on something if you're fast and I've been able to click on settings but when settings opens it's nothing but a black screen with no options. This means that I can not enable usb debugging. I have tried quite a few different processes, ADB sideload, going through the bootloader, but they all seem to require usb debugging and the tablet is never recognized. The tablet is stock but I have no way of knowing what version of android it is currently running with the blank settings window (unless you can give me a tip on that). Have done two wipe/factory restores on it and the error comes up right at the first boot screen. I am willing to pursue any option to get this tablet in working order. Rooting, flashing, whatever but I am a novice in the world of android rooting. It was purchased off groupon (won't make that mistake again) and the 14 days are past so If I have to send it in, it's cash money out of our pockets.
Do I have any options? Thank you for your time!
Most frustrating of all is that everything else about the tablet seems to be functioning normally. I can install apps from google play. I can't really run many of them though.
notnorm said:
Most frustrating of all is that everything else about the tablet seems to be functioning normally. I can install apps from google play. I can't really run many of them though.
Click to expand...
Click to collapse
If the tablet has never been rooted, and the factory reset procedure seemed to complete successfully, then your symptoms suggest that something is wrong with the /system filesystem - which, for stock devices is never modified (always mounted read-only).
So that in turn suggests *perhaps* flaky hardware - probably the flash memory chip - that has gone awry and is the root cause of the problem.
It is conceivable that you could go through the process of unlocking the bootloader and re-flash a Google-provided "factory image", and that the problem will go away. But if the root cause is really a flaky flash memory chip, it will very likely return with a vengeance, and your efforts will be for naught.
There is something missing in your narrative, however - if the appearance of the "NFC Service has stopped" dialog on-screen prevents you from interacting with your (intended) foreground apps, how were you able to perform a factory reset and then follow that up with a tablet configuration? (e.g. to get Google credentials on the tablet so you could push apps to it by using a PC Web browser from the Google Play market).
If you are unfamiliar with rooting but still want to proceed with reloading the factory images, you will have to follow the Stock Recovery tutorial threads. Many users - especially those with Windows machines - seem to get stuck at this step, although truth be told that has nothing to do with Android, and everything to do with Windows Driver Installation Hell.
Note - specific to your situation.. You do not need to enable USB debugging to re-flash factory stock images. You only need to communicate with the device (booted into bootloader mode) with the "fastboot" program. For this you only need working USB hardware - not "adb".
good luck
BTW, note that you can perform a factory reset in the stock recovery without launching it from the O/S. The sequence is:
1) Turn the tablet off (not screen off, but powered completely off)
2) Boot into bootloader mode by holding Power+Vol-Down together (hold them down until android lying on its' back shows up - about 4 seconds)
3) Using the vol-up/vol-down button, select "Recovery Mode" on screen and press the power button
At this point the screen will go black. Wait about 10-13 seconds. The screen will remain black even though the stock recovery is now running. To get the screen to show the (stock) recovery menu,
4) press and release the Power & Vol-Up keys simultaneously.
The stock recovery menu should show now up. If it doesn't, try again. (After 60 seconds if you have done nothing, the tablet will reboot to the "normal" OS).
5) Use the on-screen menu to perform a factory reset (follow the directions on-screen for key usage).
Thank you so much for your response! The unanswered question is that I managed to put in the network info and what not during setup by hitting OK on the error and tapping the letter in the moment before the error popped up again. Not a fun task!
I've been trying to flash and after installing the google usb drivers it's still doing the <waiting for device> for infinity. I think I will have to bite the bullet and send it in. You saying that it might be a flash chip is kind of comforting because I think I might have bashed my skull against this issue forever before giving up!
Chris
flashed the wifi fix for the TMObile us version (from the X Note rom page)and was able to get out of the loop.
Hello i have been freaking out and researching this for hours. (found nothing)
What I did
https://www.youtube.com/watch?v=o9gL_4KNs_Q
I have T-Mobile.
Now when my phone boots up it keeps shutting off. stays on for 1-5 seconds
I then did a factory reset and cleared the cache.
I can some times get it to the home screen and flip back and forth on the different screens then it shuts off. I have seen I have superuser on in the apps but don't get a lot of time to check root before it shuts off.
I do have red text on the Samsung logo screen that says "kernel is not seandroid enforced" (Spelling)
What do I do?
Safe mode also shuts off.
I can get to download mode and recovery mode
I just cant get it to stay on .
Any help would be great thanks.
Additional info
Update more info: When I factory reset. I do get an error failed to mount /preloader (no files or directory) wording might be a bit off but that's about what it says.
does it restart in recovery/download mode?
does it restart when the plug in into a charger?
alamatnitotoy said:
does it restart in recovery/download mode?
does it restart when the plug in into a charger?
Click to expand...
Click to collapse
I guess I should have changed the wording. Its not rebooting it just shuts off.
No It does not restart when I charge it. But it does show the battery image and charges.
Update more info: When I factory reset. I do get an error failed to mount /preloader (no files or directory) wording might be a bit off but that's about what it says.
me too, if it doesnt reboot while charging means possible battery issue.
alamatnitotoy said:
me too, if it doesnt reboot while charging means possible battery issue.
Click to expand...
Click to collapse
Sorry for the miss communication.
Lets try this again.
I can plug the phone in and it charges while its turned off. you know the battery screen.
I can volume up, home and power For down load mode
I can volume down home and power (factory reset, cache delete so on)
I can get ODIN to connect but I cant flash the firmware I found. Maybe its the wrong firmware? Could you point me to what I need?
But when I just turn it on either charging or not it shuts it self off a few seconds later. Seems to happen after a message about auto time and date pops up. And when I say shuts down it just shuts off no like shut down screen or anything.
ok start again, please put all info so it wont be confusing:
what initiate the problem?
did you install a custom rom?
are you rooted?
what phone model are you using?
odin version?
have you tried flashing thru samsung switch? if not, try it
alamatnitotoy said:
ok start again, please put all info so it wont be confusing:
what initiate the problem?
did you install a custom rom?
are you rooted?
what phone model are you using?
odin version?
have you tried flashing thru samsung switch? if not, try it
Click to expand...
Click to collapse
Update:
I just got my phone back from Samsung. On Friday they told be they didn't fix it because it was rooted and said they are mailing it back. Well now I don't have a phone so I Saturday I went and got a new s7 edge from t mobile. Its now Wednesday and I get my phone from Samsung. I open the package all bummed wondering what I am going to do with this phone. I then see the phone is in a small blue draw bag thing I thought it was cool so I open it to look at it and I see my phone light it. The sim card and tray on taped to the back of the phone but my phone is on! I then sat here looking at it waiting for it to reboot. I put my sim card. Then a screen popped up saying reboot? and I click yes . I was so mad at myself but then it restarted and everything was ok. I installed root checker and I have root access. the phone has now been on for the last hour or so. Not sure if it was something Samsung did or taking the sim card out did something.
But now I have a rooted s6 edge plus rooted and a s7 edge. and out like 600 bucks
Best solution, use Samsung's Smart Switch software (download from their site) and restore to factory ROM and kernel (official Samsung version). If it is anything software related, this will definitely fix it.
in case you dont know the steps: open smart switch, connect device (make sure its detected), got to more > emergency software recovery & initialization > Device initialization > type in your exact model name at the bottom > then serial number (make sure you type it correctly > type ok, follow instructions, and let it do its thing .
Try this and let me know how it goes. Good luck.
its kernal issue try to flash a different kernal available for edge+
Hello All, So I have a friend's 930V here. She let the phone "try" install the latest verizon OTA a few days ago, best I can tell 8CRK1 (I know). It did not complete. I have been attempting to fix it for a few days now. I have only been able to get the phone to actually boot into recovery twice. All other attempts say either "erasing, then installing update" or just "installing update", neither of which ever complete. The phone then reboots, says "recovery booting" and does it again. But I can not get it to boot into recovery to wipe the cache.
I have flashed it several times using odin (v3.13.1 and v3.13.1_3B) with firmware (8CRK1, 8CRJ3 and Umodel 8CRJ2). They all complete and pass in odin, yet it will not boot.
Some it will not even turn on, so let it sit for a while, when I come back it will turn on
- Will ticking erase NAND and/or REPARTITION help?
- Should I force the PIT file (HEROQLTE_USA_VZW)?
I have even gone to trying the Verizon/Samsung software upgrade utility, which fails half way through and says phone disconnected (on the phone it says unsupported dev_type)
-I'm about to rip my hair out- Any advice would be awesome!
thanks
A-
the screen grab I've attached are from the 1 of the 2 times it actually got it into recovery
Hi Everyone -
Last night when I went to sleep I left my PH-1 plugged in and charging, and when I woke up this morning the phone had frozen with a black screen and status light still blinking. I restarted the phone and end up at a screen with "Cannot Load Android System. Your data may be corrupt". The boot cycle goes "Powered by Android" --> circles to square dot rotation --> restarts to "Powered by Android" --> to screen mentioned before with corruption. I have options to "Try Again" or "Factory Reset" and have selected "Try Again" about 20 times now with no luck.
Some pertinent facts:
Running latest official OS from Essential
Bootloader unlocked
Phone is encrypted
When I flashed the latest official OS about a year ago I used TWRP, but forgot to re-install TWRP after the flash
I am able to get to the Bootloader --> "Recovery" --> "No Action Screen" and then get to the actual recovery from there; I am now kicking myself for not reinstalling TWRP. My options on the recovery screen are "apply update from ADB option", "mount /system", or "Factory Data Reset" (as well as review logs and some other tests).
Most of the data on the phone is backed up, however there are still some items not backed up that I'd like to attempt to retrieve.
My Question - What are my options to try and salvage the data off the phone provided it is encrypted? I've seen some references to using ADB update to re-flash the original OS (I assume this is a dirty flash) but not wipe the data and my data would still be there after the install. I've seen references for that approach but not confident enough to know if it would apply for my case. In example, would this work even with the encryption? Alternatively, I expect I could reinstall TWRP via ADB update and try to work something out from there.
Thank you in advance for reading this! I appreciate any and all insight or recommendations of an approach to take. As you can see, I'm clearly a novice who has followed some tutorials, but definitely not advanced enough to have strong knowledge of all of Android's innards. Thanks again.
Hi, I have a Samsung Galaxy A52s 5G that goes into the following loop for two days:
boots up, waits for me to unlock the phone through the draw pattern, I unlock the phone, "Phone Starting" pops up, phone starts, I am able to navigate the phone and phone apps for something like 20 seconds and then it freezes.
Model Number: SM-A528B/DS
The firmware shown in recovery mode is the following: A528BXXS1CVI6
Why I am trying all this
This is my wife's phone. I thought she was backing up photos through google photos and she told me that she was doing it. Unfortunately, she was only uploading them on the local app and the backup was not working since her storage was full for several months. So, if there is a way to access her stuff from any Operating System please let me know. The problem, I think, is that I can't without unlocking the phone (of course).
Note
If I don't unlock the phone, the phone does not freeze but of course, I cannot do anything. Therefore, I suspect it is some thread that starts by default as soon as the phone is unlocked.
What I tried
I tried the following things:
Remove the SD/SIM card tray (just because it was easy)
I tried to boot my phone in Safe mode. I correctly entered in safe mode, the third-party apps were disabled but then the phone froze again.
I connected the phone to a laptop (running Ubuntu 22.04) and entered in recovery mode. Once in recovery mode, I tried basically all the options without any luck so far:
Reboot system now
Reboot to bootloader
Apply update from ADB:
I tried to download a firmware for my phone and then send it through ADB with the following command
`$ ./adb sideload ~/Downloads/A525FXXS4CVK4_A525FOXM4CVJB_HUI.zip`
and I got stuck at
`serving: '/PATH_TO/Downloads/A525FXXS4CVK4_A525FOXM4CVJB_HUI.zip' (~0%)" `
I don't know why
I did not try "Apply update from SD Card" yet
I did not try "Wipe data/factory reset" yet
I tried "Mount /system" but it got me the following error:"Error updating for slotselect"
I tried "Repair apps"
I tried "Run Graphics test"
I tried "Run Locale test"
I tried and then did "./adb reboot recovery" to test that I was able to reboot through adb and it did reboot the phone indeed.
Let me know if you have any ideas on what to try next.
Having a similar issue right here, please notify me what you did afterwards and if you managed to solve it
I am in the same situation and same try outs. Only one slight different. Phone does not start at all. Only "SAMSUNG" and "powered by android" logos. Then starts to bootloop again.
Did you find a solution?
@minidiable did you try to flash with Odin? You should have a try using CSC that avoid erasing data.
In any case, I'm coming back here to give my result after several try-outs and finally going to a Samsung Center.
My phone, entering in recovery mode, had from the begining a message at the bottom saying " E:[libfs_mgr]Error updating for slotselect ".
At Samsung Service Center they told me that this error may probably warn about motherboard failure. And after tearing down the phone and checked it, they changed the moterhboard. Sadly, All data lost. That's all.