Has anyone else experienced this issue? My phone was running hot and draining battery fast. I looked at my battery stats and Android system was the culprit. I booted into recovery and wiped my cache. When I rebooted I was met with this error message and I am unable to connect to data. Texts and calls still work.
I factory reset and restored a backup only to be met with the same issue.
Sent from my Moto Z (2) using Tapatalk
Did you wipe /oem?
Uzephi said:
Did you wipe /oem?
Click to expand...
Click to collapse
I wiped everything, factory reset and was still having the issue. I ended up going to the Sprint store to see if maybe it was a Sim issue, got a brand new sim, still no dice. I had a technician come out and look at it (cool guy, he works for assuron and actually helped develop slim rom) and he was stumped. After spending over an hour on the phone with "advance tech support" and still unable to obtain data I left the store feeling defeated.
At this point I was weighing my options and considering just getting a new phone but I'm tapped after the holidays. I went home, did another full wipe, including system and flashed the November hybrid ROM from a completely clean slate. I'm happy to say 24hrs later and everything is working perfectly!
Thank you guys for all the work you put into this community and have a Merry Christmas.
If you wipe oem, then factory reset, you cannot provision your phone when on a Sprint rom using Sprint. The configuration app is on our oem partition. The Nov rom joemossjr made has it in /system as that is how other models work.
Uzephi said:
If you wipe oem, then factory reset, you cannot provision your phone when on a Sprint rom using Sprint. The configuration app is on our oem partition. The Nov rom joemossjr made has it in /system as that is how other models work.
Click to expand...
Click to collapse
That makes sense. I did wipe oem to get rid of all the Sprint bloatware.
filthyfnj24 said:
That makes sense. I did wipe oem to get rid of all the Sprint bloatware.
Click to expand...
Click to collapse
I have a debloated Sprint November update oem partition if you want working WiFi calling. I'll upload the image and edit this post in a couple hours for you. You would just "fastboot flash oem oem.img" most versions of fastboot should be able to sparse the image correctly. It does on my Ubuntu 17 computer...
https://drive.google.com/open?id=182S41iRFfXBi3buCKCxD580ujbPrLG7N extract the partition image, boot to fastboot and run "fastboot flash oem oem.img" I know linux will parse it correctly, but windows might now depending on the version of fastboot you're running.
Edit: sorry for late reply. Had some CTS integrity issues and had to redo it then just decided to pull the whole partition again. If safety net is a must for you, you might need to factory reset. OEM will stayed modified. Only apps are the essentials for WiFi calling and provisioning. All the Sprint bs is gone. I really hate how much junk they try to force install after every factory reset...
Related
Hi Guys,
I have CID__001 in the UK and received the JB update this morning - great, I've been waiting for it for months, that's why I didn't bother rooting my phone like i did with my desire.
So my phone boots up and EVERYTHING keeps crashing. com.android.phone, android.process.acore, gapps, htc sync etc. Constant error messages, so i can't get rid of them to do anything. The SIM card won't prepare, the home screens never load so I can't access my apps, the battery is draining like crazy, I can't sync my contacts because sync crashes, I called the phone from my landline, the landline phone rang, but the HOX didn't. I also can't access my files on the phone through the computer, the computer recognises it's there, but when i click on it it says 0 files. I don't have a backup, but if i have to lose them to get my phone working, so be it. It's completely messed up.
I have rebooted several times, also in safe mode, but it always happens. I also tried running the RUU because I now have HBOOT 1.36 but it told me it was the wrong RUU and wouldn't update.
I wanted to copy the update file onto the external storage and rename it update.zip so I could flash it from recovery, but i can't access the files through the phone or the computer so that was a bust.
I cleared the cache from the recovery menu, still no joy.
I haven't done a factory reset yet, because I don't want to lose everything and I don't think it would work if I get all the crashes in safe mode.
I need some help, I've got some experience rooting/flashing etc, I did it a lot on my desire, but I am stuck here. I'd like to be able to fix it myself, as all HTC will do is send me a refurbished phone, charge me for the pleasure and I'll lose my data anyway.
My bootloader is unlocked, but I never rooted or flashed anything on it, it was purely stock with an unlocked bootloader.
Any suggestions? I really don't know where to go from here. Typical that I didn't meddle with my phone so I could have the official update and it messes up my phone.
Have you got stock recovery or custom?
Sent from my HTC One X using xda premium
stock
Could be you need a factory reset which is what i would do.
Yep, its gonna have to be a factory reset, if it still don't work contact HTC clearly a fault of theirs, cant see how unlocked bootloader can play a part..
Are you 100% its stock coz you can't clear cache from stock recovery... You need custom recovery.
Sent from my HTC One X using xda premium
Factory reset worked
Yes, my recovery is definitely stock. There aren't many options, but erase cache is one of them.
Factory reset worked. I have lost everything, had to reset from the fastboot screen (not sure what it's called) because it would not work from the phone settings - whatever was necessary to factory reset my phone kept crashing. Resetting from there also formatted my external storage, all my photos and music and everything are gone.
Really annoyed at HTC right now. I waited patiently for months, could have easily rooted and flashed a custom JB ROM but I waited and their update has caused me to lose everything.
Does anyone know why this would have happened or have heard of it happening to other people?
On the up-side...Jelly Bean is now rolling out in the UK!
cec24 said:
Yes, my recovery is definitely stock. There aren't many options, but erase cache is one of them.
Factory reset worked. I have lost everything, had to reset from the fastboot screen (not sure what it's called) because it would not work from the phone settings - whatever was necessary to factory reset my phone kept crashing. Resetting from there also formatted my external storage, all my photos and music and everything are gone.
Really annoyed at HTC right now. I waited patiently for months, could have easily rooted and flashed a custom JB ROM but I waited and their update has caused me to lose everything.
Does anyone know why this would have happened or have heard of it happening to other people?
On the up-side...Jelly Bean is now rolling out in the UK!
Click to expand...
Click to collapse
probably there was a problem with some other apps on the phone, so maybie that wasn't htc fault. But wasn't mass storage working? If yes you could backup everything before doing factory reset.
cuzzo94 said:
probably there was a problem with some other apps on the phone, so maybie that wasn't htc fault. But wasn't mass storage working? If yes you could backup everything before doing factory reset.
Click to expand...
Click to collapse
My phone showed up under my computer, but when I tried to access it, it said 0 files...I tried. Failed, but tried.
I'm having this really bizzare issue with my HTC rebooting not in a traditional bootloop per say but the phone will only reboot when i get into the OS itself. Before I explain exactly here is my device details when the event started:
Unlocked Bootloader
TWRP Recovery
Root Access
Stock AT&T Sense 6 Rom Android 4.4.2
So nothing crazy. I was experiencing a slow down in my data speeds so I figured why not just reboot the phone and see if that helps any. After I did I want to say 10 seconds later my phone rebooted. It was strange but i thought nothing of it......until it happened 4 more times and then wouldn't stop. I was able to temporarily stop it but doing a full wipe and flashing a GPE Rom but as soon as i reboot my device it starts again. I've tried just about everything from cache wipe, dalvik cache wipe, and even changing my recovery to Philz but nothing has helped. And since there still isn't a RUU for the M8 yet i cant convert it to stock for warranty because I cannot remove the tamper. Can anyone help me? I'm really trying not to have to pay for another device. Working for AT&T only has its perks from a monthly bill perspective lol
bnicsk8guy said:
I'm having this really bizzare issue with my HTC rebooting not in a traditional bootloop per say but the phone will only reboot when i get into the OS itself. Before I explain exactly here is my device details when the event started:
Unlocked Bootloader
TWRP Recovery
Root Access
Stock AT&T Sense 6 Rom Android 4.4.2
So nothing crazy. I was experiencing a slow down in my data speeds so I figured why not just reboot the phone and see if that helps any. After I did I want to say 10 seconds later my phone rebooted. It was strange but i thought nothing of it......until it happened 4 more times and then wouldn't stop. I was able to temporarily stop it but doing a full wipe and flashing a GPE Rom but as soon as i reboot my device it starts again. I've tried just about everything from cache wipe, dalvik cache wipe, and even changing my recovery to Philz but nothing has helped. And since there still isn't a RUU for the M8 yet i cant convert it to stock for warranty because I cannot remove the tamper. Can anyone help me? I'm really trying not to have to pay for another device. Working for AT&T only has its perks from a monthly bill perspective lol
Click to expand...
Click to collapse
twrp, wipe, dalvik/cache/data/system, flash rom, if you don't wipe system some stuff can find its way over and may be causing issue. Is this an at&t phone? There is an att ruu.
an0ther said:
twrp, wipe, dalvik/cache/data/system, flash rom, if you don't wipe system some stuff can find its way over and may be causing issue. Is this an at&t phone? There is an att ruu.
Click to expand...
Click to collapse
It is an AT&T device. I'm sure I've done a system wipe and like I said sometimes my device will work okay but as soon as i reboot it, its back at it again. And thanks for the info! I wasn't aware the RUU for the AT&T version as available
bnicsk8guy said:
It is an AT&T device. I'm sure I've done a system wipe and like I said sometimes my device will work okay but as soon as i reboot it, its back at it again. And thanks for the info! I wasn't aware the RUU for the AT&T version as available
Click to expand...
Click to collapse
At&t 1.58 RUU
http://forum.xda-developers.com/showthread.php?t=2757462
Well, when i try to make or receive a call the phone not response, the phone take H+ as signal in that moment, but the signal drops.
When I try to call does not even get to dial, just runs out of tone and hangs after 30 seconds,
This started shortly after trying to customize my cellualr with andromeda when I modified the layers, my cell phone was reset every 5 minutes until it reached a bootloop from which it came out only forcing off with vol - and power button.
I remove the layers, uninstall andromeda and I stop having that problem, but a few days later I realized that I could no longer link calls. I'm almost sure that caused it
Today just as I got up I was determined to do the formatting process
i Installed the global version of android 8.0 which is what I had previously.
I set the phone and surprise, I could link call, I proceeded to turn it off to put twrp and magisk since I am very fan of having my system completely modified.
The second surprise of the day comes when installing TWRP told me the post that I had to give in format data, so that my data was not encrypted.
This caused my system to be deleted and when I installed Magisk and rebooted for obvious reasons, I was sent to bootloop.
I reloaded the system and it does not let me link calls again.
I really surrendered to this situation, I did the process of fasboot with the system a couple of times more to see if it worked like the first time, but I still have the problem.
The cell pohne is released from the company and is from Telcel Mexico.
It is in its compilation free of company with android 8.0, I have no problem with loss of imei or base band. I have all the services of my sim least calls.
mobile data 4G lte, I can receive and send messages, only calls I have this case, the motorola support team as always a few potatoes, that's why I come here where there are people with more knowledge to see if someone has an answer to my problem
Sorry if i dont write well in english but it isnt my 1st language
If you have the firmware for your phone, you should do a clean install, then factory reset after the install. Boot it, do a quick setup, don't set any lock screen security until after you have flashed twrp and rooted.
41rw4lk said:
If you have the firmware for your phone, you should do a clean install, then factory reset after the install. Boot it, do a quick setup, don't set any lock screen security until after you have flashed twrp and rooted.
Click to expand...
Click to collapse
I did that, I actually deleted the whole system from twrp and installed the firmware by fastboot, and at the end it still does not work u.u
angefco said:
I did that, I actually deleted the whole system from twrp and installed the firmware by fastboot, and at the end it still does not work u.u
Click to expand...
Click to collapse
No, not like that. Do you have a complete flashall? If you have a complete firmware for your phone with a flashall, use it to go to a clean stock setup, not a hybrid mix and match.
41rw4lk said:
No, not like that. Do you have a complete flashall? If you have a complete firmware for your phone with a flashall, use it to go to a clean stock setup, not a hybrid mix and match.
Click to expand...
Click to collapse
Well i only do the script for flash the system.
what i need ? :c
Why i cant upload an image
Hello, everyone!
I just installed Android 10 onto my Pixel 3 XL a couple of hours ago and I've noticed battery drain and some lag. Is a factory reset suggested at this point, since I flashed a new Android version?
Edit:
I had animations removed under "Accessibility" and I toggled it back on, then I turned Dev. Options on and switched animations to .5x and the problem seems to have went away. I'll have to update you all on battery life later. Still, the question remains... Is a reset suggested?
I just also did the ota update and now my pixel 3xl is stuck on a Google splash screen. Did I just somehow brick my phone?
animeva said:
I just also did the ota update and now my pixel 3xl is stuck on a Google splash screen. Did I just somehow brick my phone?
Click to expand...
Click to collapse
Had to enter stock recovery and reboot myself, mine was black screen. After that i was good
razrlover said:
Had to enter stock recovery and reboot myself, mine was black screen. After that i was good
Click to expand...
Click to collapse
Were you on the latest beta before the update? My update file was only 5.5mb. Went pretty quickly.
is it worth factory resetting device with this latest update?
Jay01 said:
is it worth factory resetting device with this latest update?
Click to expand...
Click to collapse
No, if you used the ota through phone, google would of already done maintenance before the install, ie, removed incompatible apps settings and features.
Has anyone flashed the factory image? If so what one did you use. I can't flash the the 10 factory image. The only was I can get it is to flash the Pie factory image, and then take the OTA. Not sure why I get an error every time I try to flash 10.
animeva said:
I just also did the ota update and now my pixel 3xl is stuck on a Google splash screen. Did I just somehow brick my phone?
Click to expand...
Click to collapse
This happened to me too. After about five bootloops I finally got it to boot, but it booted back to B6, and the update said it couldn't install. I tried again, and all went well the second time.
bobbyphoenix said:
This happened to me too. After about five bootloops I finally got it to boot, but it booted back to B6, and the update said it couldn't install. I tried again, and all went well the second time.
Click to expand...
Click to collapse
Ive tried the update 3 times now and every time it has been stuck at the boot. I would have to turn off and try to restart around 3-5 times for it to go back to Android Pie. So still unable to update to Android 10.
Ill try it one more time later and see if maybe they changed the update a bit
animeva said:
Ive tried the update 3 times now and every time it has been stuck at the boot. I would have to turn off and try to restart around 3-5 times for it to go back to Android Pie. So still unable to update to Android 10.
Ill try it one more time later and see if maybe they changed the update a bit
Click to expand...
Click to collapse
I don't know if this had anything to do with it but I disabled my ad blocker and I cleared all recent apps and then when I tried it the second time it worked so maybe make sure everything is clear and you have no ad blocker enabled.
For small updates like monthly security patches or version increases of 0.1 or 0.0.1 I usually don't worry about doing a clean install since the changes are usually pretty minimal. For large updates I like to do a clean install just for piece of mind that all the crap that built up on my phone over the past year is gone, to eliminate the general issues that pop up with dirty installs, and having a squeaky clean fresh install just feels nice once in a while.
jmartin72 said:
Has anyone flashed the factory image? If so what one did you use. I can't flash the the 10 factory image. The only was I can get it is to flash the Pie factory image, and then take the OTA. Not sure why I get an error every time I try to flash 10.
Click to expand...
Click to collapse
I updated 9->10 like I normally do each month by dirty flashing the full image (not full OTA) so I would say you do not need to do a factory reset. I did not previously install any of the betas. Although the install took longer and was different (fastbootd) it completed and booted to system the first time. It may just be time for a fresh install, meaning leave the wipe flag in the flash-all script and let it erase your user data.
v12xke said:
I updated 9->10 like I normally do each month by dirty flashing the full image (not full OTA) so I would say you do not need to do a factory reset. I did not previously install any of the betas. Although the install took longer and was different (fastbootd) it completed and booted to system the first time. It may just be time for a fresh install, meaning leave the wipe flag in the flash-all script and let it erase your user data.
Click to expand...
Click to collapse
I was doing a complete wipe.
(Update) I finally got it to do a full factory image flash with a complete wipe. The only thing I changed was, I switched from Slot B to Slot A. Not sure if that was even the issue, but It worked, and now My Pixel 3XL is running really well. No issues that are being reported.
bobbyphoenix said:
I don't know if this had anything to do with it but I disabled my ad blocker and I cleared all recent apps and then when I tried it the second time it worked so maybe make sure everything is clear and you have no ad blocker enabled.
Click to expand...
Click to collapse
i didnt install any 3rd party ad-blocker apps on the phone before... if there is any, it would be google's out of box one... i doubt they have one out of the box.
Im too nervous to do this update again only for it to brick again right now
animeva said:
i didnt install any 3rd party ad-blocker apps on the phone before... if there is any, it would be google's out of box one... i doubt they have one out of the box.
Im too nervous to do this update again only for it to brick again right now
Click to expand...
Click to collapse
Suit yourself, but if your adb/fastboot binaries are all up to date (July 2019) and you are flashing the full image (not the OTA image), then you should have no issues at all. There are many guides on how to do this properly and the procedure is no different now than with 9. Also, there is no "change" coming to make the install smoother because there is nothing to fix. If your bootloader is unlocked this phone is virtually un-brickable.
v12xke said:
Suit yourself, but if your adb/fastboot binaries are all up to date (July 2019) and you are flashing the full image (not the OTA image), then you should have no issues at all. There are many guides on how to do this properly and the procedure is no different now than with 9. Also, there is no "change" coming to make the install smoother because there is nothing to fix. If your bootloader is unlocked this phone is virtually un-brickable.
Click to expand...
Click to collapse
if i do a full image, not the OTA version, does that require a factory reset?
animeva said:
if i do a full image, not the OTA version, does that require a factory reset?
Click to expand...
Click to collapse
No, but you do need an unlocked bootloader. If you are unlocked go ahead and flash the full image. Be sure to do a version check of your adb/fastboot. Sometimes you can get into trouble if you have old versions in a different location. You need to be sure you are running version 29.0.2 (July 2019). If you did not lose all your user data on past attempts, do a dirty flash (removing the -w flag from the flash-all.bat file). If you already lost your data, then just run the script as-is. GL.
Edit: If you were trying to update 9->10 using an OTA, that is probably your issue. The full image will properly reformat your file system for 10.
Hey there,
let me start off by saying that I don't own an XL, but a non-XL 3a. Since my question seems to apply to both devices (similar/same components), I'll try my luck here.
Recently, my 3a got stuck in SystemUI crashes and I tried every solution that came to mind and others suggested over at the 3a section (check my profile if curious, basically locked BL, fully stock, no ADB), but nothing solved the issue.
However, I didn't factory reset yet, but I'm confident that it would fix it. On the other hand, It'll also wipe my storage.
----
Long story short, the only option I can think of is to recover my files with a data recovery app/program after I have wiped/factory reset my phone.
Did anybody ever successfully used such an app on a Pixel or similar (A/B) partition layout? Is it even possible/viable? Are there special prerequisites to consider?
It goes without saying I'll make sure to overwrite as few sectors as possible, if any. I can accept some files getting lost in the process, but want to keep whatever I can recover.
Thank you for reading.
Your biggest issue is going to be the fact that the storage is encrypted. So even if you do wipe the phone, I don't think anything will be recoverable since it won't be readable.
Your data will not be recoverable after the factory reset... because it was encrypted. Part of the factory reset will wipe the encryption key (that will not be recoverable since it will be regenerated on the first boot) so your data is surely lost. You are in the worst possible scenario for data recover, honestly your best bet is probably just factory reset and accept that the data is gone forever.
xnifex said:
Your biggest issue is going to be the fact that the storage is encrypted. So even if you do wipe the phone, I don't think anything will be recoverable since it won't be readable.
Click to expand...
Click to collapse
acejavelin said:
Your data will not be recoverable after the factory reset... because it was encrypted. Part of the factory reset will wipe the encryption key (that will not be recoverable since it will be regenerated on the first boot) so your data is surely lost. You are in the worst possible scenario for data recover, honestly your best bet is probably just factory reset and accept that the data is gone forever.
Click to expand...
Click to collapse
Well, damn. Thanks nonetheless, I didn't even think about that.
I'll try to fiddle with the phone one last time, maybe I'll get it unlocked somehow (I can only get 7 or 8 dots
of my pattern connected before the UI crash kicks in...). This is literally the only thing that separates me from the storage.
This has to be the most infuriating small obstacle with the biggest effect for me.
Since you're stock, might get lucky if your software is good on your second slot. You'll have boot into fastboot mode abs try the command "fastboot continue" from command line on a computer. Plenty of fastboot guides online if you've never used it.
Credit to this thread: https://www.reddit.com/r/GooglePixel/comments/5cbc9m/bricked_pixel_xl/
brandontowey said:
Since you're stock, might get lucky if your software is good on your second slot. You'll have boot into fastboot mode abs try the command "fastboot continue" from command line on a computer. Plenty of fastboot guides online if you've never used it.
Credit to this thread: https://www.reddit.com/r/GooglePixel/comments/5cbc9m/bricked_pixel_xl/
Click to expand...
Click to collapse
Man, if that works out, I'd be insanely glad. Have to get my hands on my friend's laptop first though.
I mean, the UI just started crashing after I checked for an OTA without downloading, then changing the wallpaper. That was literally it. Hadn't I rebooted, I would have been able to still unlock with my fingerprint between each crash.
Here's hoping that ADB sideloading OTAs left that slot option intact.
Will definitely update this post; at the very least, thank you for your suggestion.
Update: "fastboot continue" as well as switching boot slot parameters aren't allowed on this locked bootloader.
ADB sideloading caused slots to switch anyway, and both slots seemed to be affected from the SystemUI crashing. Will edit my original thread with a conclusion now.