Had this M8 for a few months now after bringing it back from a bad software install by another user (here http://forum.xda-developers.com/htc-one-m8/help/m8-qhsusbbulk-rebooting-t3437240), was on a stock rom up until 2 weeks ago (restored from a nandroid backup provided by user on xda) until all apps seemed to force close constantly, I also could not connect to any mobile network, kept complaining of no sim card, no imei and unknown baseband. Tried a reset and a restore from the nandroid backup, neither of these worked, the phone would turn on and would get to the HTC boot screen then black screen continually, no amount of restore or reset fixed it, I also formatted and repaired the file system a few times, again made no difference.
Ended up going on to a custom rom which has worked for about 2 weeks up until today, again being presented with force closes in apps and the mobile network again will not work, complains of no sim card as before.
I'm thinking the nand (where the actual system and data partitions are) is basically dying and is not working correctly, anyone experienced similar?
Reflash of firmware via fastboot oem rebootRUU and another restore of a stock rom via twrp has fixed it once again, still clueless on why this randomly continues to happen
Related
Hi All, I come begging for help after exhausting all of my options and searches for similar issues.
I have a CDMA Galaxy Nexus Stock 4.0.2 but rooted (I installed CWM).
I woke up to my phone stuck in the boot loading screen; it just kept looping over and over. I shut off the phone restarted it and the phone was practically unuseable, it ran very very slow. Now I haven't done anything recently or installed any apps. The only app I installed was a modified MMS app (one of the Inverted Black ones), but that was 2 weeks ago and everything was running fine since then. (However since I'm not on a deodexed Rom, I knew there could be issues).
Well I of course switched back to the stock MMS app that I had manually backed up and that did not help. Now my phone would load, it would get to my homescreen, but it would then say something along, "service is not working, wait, close, or ok?" I'd hit wait and within 2 minutes my phone would automatically reboot and then go into a a sort-of bootloop (it would just show the boot.img and loop).
I then tried to restore two Nandroid back-ups (which were basically bone stock and made months ago) and both worked, except it would say secure.img not found or something like that. I was still able to boot up and use these back ups, but then within 5 minutes I would get the same error and then the phone would reboot.
After retrying them I decided to to just go bone stock and wipe and do a factory reset. This worked and everything seemed fine until I went to turn on wi-fi.
I would wait for wi-fi to turn on and eventually it would just quit and then reboot the phone. I did this 3 times in a row to confirm that it was indeed wi-fi causing these rebooting issues.
Now here's the thing, right now my phone is working as I have purposely tried not to touch the wi-fi (I need to use my phone) . Data, voice, mms/sms all work. But I literally have no idea why wi-fi would be causing my OS to go crazy?
My last resort is to flash the stock toro.img but I was hoping you guys could help me before I get to that point.
As of right now even though I did a data wipe/factory restore my phone is still rooted (rooted apps all work) and my bootloader is still unlocked. (I renamed the secure.bootloader file as per the instructions when using fastboot to load CWM).
Please help me troubleshoot this, Thanks guys.
I don't know if you have tried but maybe try flashing a rom after a data wipe
angelino0919 said:
I don't know if you have tried but maybe try flashing a rom after a data wipe
Click to expand...
Click to collapse
I'm thinking about doing this as well since I will probably have to flash back to stock. I just want to make sure I can get back to stock since I am still covered by warranty and insurance (assuming they do not check to see if my phone has an unlocked bootloader).
JayBeezy802 said:
I'm thinking about doing this as well since I will probably have to flash back to stock. I just want to make sure I can get back to stock since I am still covered by warranty and insurance (assuming they do not check to see if my phone has an unlocked bootloader).
Click to expand...
Click to collapse
Well you can always relock the bootloader. I doubt you will have to go back to stock though
Hey, guys!
I am in a desperate need of help. Here's my situation:
I've got an HTC Desire (obviously), which reboots every time the ROM starts. It all began after I decided to move back to a Sense ROM after having been testing ICS for the past couple of weeks. So, I flashed RCmix S - a ROM I knew to be stable and working snappily on my phone. Everything went well, I restored my apps with Titanium and then decided to remove some of the junk stock apps. When this was done, I restarted the phone, only to be faced with a series of reboots every time I got glimpse of the Sense UI (i.e. seconds after unlocking the SIM card).
I thought this might be a ROM-related issue, so I tried another one - Supernova. Same thing. Tried flashing it several times after full wipe always. No luck.
During the whole process I switched HBOOTs a few times - from stock, to Fatsys (IN2SD), back to stock. Tried several recoveries (AmonRA, 4Ext touch).
Even flashed official RUUs at least 3 times in order to get the phone back to its factory state. Once the stock ROM worked fine. Then I went on to root it and tried flashing one of the customs ROMs again, which, predictably, began rebooting just after SIM unlock.
I thought this might be connected to problems with the SD card, so I reformatted it completely - 6,8 GB FAT32 + 1 GB Ext4, using GParted. All by the book.
No I've got a clean SD (removed all the previous folders), but it doesn't seem to solve the problems.
Can anyone, please, think of something that I could do in order to get my phone back?
P.S. I forgot to mention, that my phone is S-Off. It struck me as strange, though, that it stayed S-Off even after flashing the RUUs.
New development: this morning, after successfully creating a Gold Card, I went on to try and flash a 2.2 RUU again. This time, however, the installer announced it was unable to access certain files and thus the flash process had failed. Meanwhile, the phone itself displayed a triangle and an exclamation mark on the 4 corners of the screen. I no long can access Recovery or the Bootloader. Help me, please!
Never mind, I managed it myself.
Had something really weird happen to my S3 guys.
Running teamwin and the Liquid-Smooth ROM. Been that way for 5 months since I bought it with no problems until now.
Plugged the phone up to the charger last night before bed. Woke up and wondered why the charging light was still yellow so I kicked the screen on and it was charging at an extremely slow rate (Around 40mA). Unplugged the charger and the phone made a tone I had never heard before. Noticed two small "glitches" or "artifacts" in the display rendering around the clock area on the home screen. Attempted browsing around the phone. App drawer opened and closed fine but EVERY process or app I would try to launch would crash so I rebooted, and that brings me to where I am now.
The ROM will NOT boot. The phone just sits there at the Galaxy SIII splashscreen. I can boot to Odin/recovery just fine and the internal SD filesystem appears intact and browse-able. Tried totally nuking the data section. Wiped Dalvik/Cache, did factory reset and then wiped the ROM. Tried re-installing the ROM and even re-flashing the radio and it still doesn't boot past the splashscreen.
While I was in recovery it also told me, "Your phone doesn't appear to be rooted. Would you like to install SU?", which is strange because the phone WAS rooted.
Thinking this thing mysteriously turned itself into a paperweight. Any ideas?
Please install a different Non-Liquid Rom. But for best results, First ODIN back to stock and then go from there. Use Root 66 Stock image.
agree with odin flashing root66 firmware. factory reset FIRST though. you will likely be forced to if you dont, and once stock recovery is flashed back on it will wipe internal sd.
if you still have issues after that i would suspect a hardware failure.
Sent from my T-Mobile MyTouch 3G Slide(HTC Espresso) using Tapatalk 2
Just FYI guys I got it back about an hour after posting this.
Even after wiping both caches, performing a factory reset, fixing permissions and finally nuking the ROM it still would not boot. I then put in a spare SD, used recovery to copy everything from internal to external to save all my valuable data and only after wiping the internal SD was I able to get the phone to boot again after re-installing the ROM.
I then transferred all valuable files back to internal SD, restored from a recovery backup and then was good to go. A bit strange but I got it working again.
Eventually I might upgrade from LiquidSmooth but I like it and have no reason to change for now.
Hi guys,
Bought a 2nd hand T705Y, after factory reset and getting accounts and apps running after 2 days I noticed I couldn't turn on BT. A day after I get Camera Fail msg with camera app.
Stock 4.4.2 rom rooted with cf. Following online instructions I tried clearing cache, wiping cache and factory reset. Nothing helped. Finally I restored original phone firmware with Kies and everything was working again.
Now 2 days later again… both BT and Camera are giving me grief again with same symptoms.
Anyone hear of this?
Surely not HW problem as both worked fine immediately after reflashing firmware.
Any suggestions? I was thinking trying a ROM to see if that avoids any software problem presented by stock rom.
If the EFS partition has become corrupt it could cause problems. It contains important data for wifi, Bluetooth and network.
I had a problem with my radio, couldn't connect to the network. Restored the EFS partition and all was well.
See if someone can make a backup of it in recovery and you can flash it back.
Back yours up first though as it contains your IMEI too.
Wouldn't the reflashing of stock firmware by Kies include refreshing the data in that partition? Or if I installed custom roms?
Roms don't contain that data. Stock or otherwise.
Sent from my SM-T805 using XDA Free mobile app
Finally figured out what was causing this. It seems camera fail pop up appears whenever I have the kitkat sd write hack to platform.xml you know the adding of <group gid=”media_rw” />.
Once the line is added, reboot. Camera fail pop up appears. Line removed, reboot and the pop up is gone.
So instead of adding the line I replaced the entire section with just above line and both functions work now.
Hi
Kind of same problem
After about a week i get camera failed warning. How can I resolve it.
I'm a newbee!!!
I have a T-805
Anybody else with this problem? My 6 Pro gets soft bricked with the
SD1A.210817.036.
It loses the signal (Tmobile) then restarts to recovery saying
“Cannot Load Android System. Your Data May Be Corrupt” It gives me the option to "Try again." or to "Factory data reset."
Device Completely stock
This is what I have done
1
Try Again (Same behavior)
2
Factory Reset (Multiple times), would let me finish the setup but as soon restores my data and apps happens all over again.
3
Sideload Rescue OTA (SD1A.210817.036.) same ****
4 now with heavy weapons
Unlocked bootloader, manually flashed factory images (Unlocked) the factory image it's an older version but seems to work perfectly (I'm able to set up and restore my data, but the phone automatically downloads the OTA update and the same thing all over.
5
Got a device replacement (Hella lucky they had my device in stock)
6
Different new Pixel 6 Pro Same behavior as soon the OTA hits and finishes to restore my apps.
7
Tried Manually flash, use the online google tool with different builds (tried the Tmobile stock)
Always the same problem.
There's any way to wipe/repartition only the System portion? I remember having something similar back in the days with an S2 and was able to fix it with a Reflashing of the PIT partition through Odin
Any suggestions?
Only thing I see consistent is the data being restored. That data could be corrupted. Not sure if that's possible. Try setting up as new device or from a different backup.
I think"new device" is the way to go. Over the years I've found some apps don't work with a new update.
Points 5 and 6 suggest that it's something to do with your data and app restore causing the issue.
How modified was your previous device?
Just got my Pixel 6 Pro yesterday. I have had to restore 3 times. The first two were from a back up and the third time, from scratch and the same thing is happening. It took a while for the third time to happen (over night and a few hours into the day) and I thought I was safe and put a screen protector on and then bam! Just before it happens I get a lot of the Google apps like phone app and some heat app crashing, then it reboots and says Android is corrupt.
Corrupted data error message after December update
Hi! Is everyone else here struggling with Corrupted data error message after December update? Pixel asks to wipe data, but even if you do, it still do the same on the next reboot. There's Reddit thread about that going on:
forum.xda-developers.com