Develop Bugs

Problem when upgrading to 4.4.4

Hello XDA,
I have SGH-T999 phone or T Mobile Samsung Galaxy S3 with CM 11 M8 snapshot and i am facing some major problems with it. Yesterday (7/14/14) i upgraded the rom to m8 snapshot and faced some problem after i loaded up my device. i had problem with my keyboard. i believe this is because i had flashed android l keyboard. But when this was happening i thought the problem i had was caused by the gapps. Thus i went on to download the 4.4.4 gapps. the problem still continued and also i could not use my menu and back button. So i backed up all my stuff including system data. i factory reset my phone and flashed the latest snapshot and the latest gapps. i started up my phone and it worked perfectly. I then recovered all my data and when i was asked to reboot my device i didn't. i first installed my xposed framework and then rebooted. From that point on my device is stuck in a boot loop and i cant fix it. Also when i pressed the power button, my device vibrated twice and then if i pressed it again it would vibrate once. I think the answer is to just restore the user data and not the system. if this is the answer is there anyway i can get my user dictionary and wifi connections back? Thanks.

You'll probably need to factory reset again to get it booting. Using an app such as titanium backup, only restore user data and apps. (Restoring dictionary and wifi connections should be ok). If you were previously on an earlier version of that rom, restoring all data should be ok, so im suspecting its probably got something to do with xposed framework.
I dont know a lot about xposed or cm though, so maybe someone else can verify all of that.

Thanks!
DocHoliday77 said:
You'll probably need to factory reset again to get it booting. Using an app such as titanium backup, only restore user data and apps. (Restoring dictionary and wifi connections should be ok). If you were previously on an earlier version of that rom, restoring all data should be ok, so im suspecting its probably got something to do with xposed framework.
I dont know a lot about xposed or cm though, so maybe someone else can verify all of that.
Click to expand...
Click to collapse
Thanks what you suggested worked. Thanks again

[SOLVED][Q] ART building bootloop - anyone else seen this?

Hi, Ive not long had my m9. When i got it it updated straight away and got the charging bug.
Since then I have s-off'd and tried various roms with not too much luck.
I now have a bug that occurs when i flash a new rom. This has happened when i flashed 3 different roms. Leedroid, Viper and android revolution. the rom flashes ok, then starts to boot, and builds art. It then finishes building art and starts to complete the boot process, and then it reboots and tries to build art again.
I flash back to my stock backup and everything is fine again. (apart from the damned charging bug)
Has anyone else experienced something similar?? am i missing something??

Go in twrp and make factory reset

just tried that, didnt work

Did you update your firmware? if you're still on 1.x firmware, those 2.x roms will reboot.

yeah. have tried matching roms to firmware and still get the same result. trying viper one currently. in a massive bootloop again. It boots enough to say "nfc service has stopped working" and thats what made me think it might be firmware, but it seems to make no difference.

cant even adb whilst its booting.. getting waiting for device.

What version of twrp are you using?

2.8.6.1

philicibine said:
2.8.6.1
Click to expand...
Click to collapse
Update to 2.8.7.0 and see if it continues.

I've solved this, and my charging issue. Finally!!
I decided to flash the earliest ruu I could find and then let it do all of the ota updates itself.
I then rerooted, flashed updated firmware and am now running leedroid.
Thanks for the help guys.

Has anyone managed to install 6.0.1 OTA on 100% stock device?

I am 100% stock, I repeat, 100% stock. The bootloader is unlocked. I got an OTA yesterday for 6.0.1 MMB29K but this morning I found my Nexus completely drained so I charged it and powered on. Seems it was drained by a bootloop. I tried flashing 6.0.1 manually again today with fastboot (bootloader.img, boot.img and system.img). I'd prefer to not reset my device until someone can confirm that something isn't wrong with 6.0.1. Thanks!

mertzi said:
I am 100% stock.... I'd prefer to not reset my device until someone can confirm that something isn't wrong with 6.0.1. Thanks!
Click to expand...
Click to collapse
Same here. 100% stock with unlocked bootloader.
I got the OTA update yesterday and got stuck in a bootloop on the 'spinny circles' animation after the 'optimising apps' stage. The only thing that was not completely 101% stock was that I had disabled several of the Google bloat apps like Docs, Show, News, etc. etc. Whether that makes any difference or not, I don't know.

im on stock 6.0 and my tablet doesn't boot up after the 6.0.1 update install.
its stuck in infinite boot loop.
tired clearing the cache partition from recovery but in vain!
any help?

Mine is 100% stock and upgraded to 6.0.1 without any problems.

strumf666 said:
Mine is 100% stock and upgraded to 6.0.1 without any problems.
Click to expand...
Click to collapse
Same here on mine...NO problems with the OTA update.

Still waiting on the OTA for my completely stock N7... I feel like mine is always at the back of the cue. Will let you know when I get the update of I have a problem with it.
Sent from my Nexus 7 using XDA Free mobile app

Just finished sideloading the ota on mine and I've had no issues on the tablet but I had issues on my laptop with a no protocol error so a heads up if anyone runs into that error.

$!> said:
im on stock 6.0 and my tablet doesn't boot up after the 6.0.1 update install.
its stuck in infinite boot loop.
tired clearing the cache partition from recovery but in vain!
any help?
Click to expand...
Click to collapse
6.0.1 running fine on my very stock unrooted N7/2013. Installed via OTA.

Bob Denny said:
6.0.1 running fine on my very stock unrooted N7/2013. Installed via OTA.
Click to expand...
Click to collapse
mine was never rooted,bootloader was never unlocked,nothing done to my tab which the manufacturer hadn't done!
it was fine till 6.0 update and i got a notification to download and install the new update i.e 6.0.1 which was around 63mb in size and now all my tablet is stuck in infinite boot loop till the battery drains.
tried clearing cache from recovery but in vain!
i don't want to format/factory reset as i have data which is very important.
any help would be much appreciated!

Yeah i'm having the same issue too. 100% stock 32gb Nexus 7 stuck on bootloop after installing the update.

Couldn't be lack of space in /system could it? Just a SWAG believe me.

The OTA worked fine for me on a stock, unlocked and unrooted razorg (LTE), coming from MRA58V.

I have the same issue. Stuck after app optimisation during boot. 100% stock, no root, not twrp recovery. I have the feeling that this is somehow connected to disabling google apps (applications-> disable, no titatium backup or the like), since it happened after I rebooted after disabling most of the google apps. Can someone who got 6.0.1. working flawlessly confirm that no google apps have been disabled in the system?

I'm rooted but I did notice that there is *0* mb left in /system after I updated to 6.01, maybe use the Uninstall System Apps app and delete Google Sheets Docs and Slide and see what happens?

I'm totally stock and never had an issues updating

OnePlus 3 - Android Oreo Camera Unknown Error!

Hi,
Today im facing a strange issue with camera
Actually all the applications related to camera are not working
It seems there is a problem in the physical camera it self !
Snapchat, instgram once i open its cam, original camera, and google camera..
It shows me this message
"Unknown Error"
My phone is already updated to stable version 5.0 which is oreo.

By the way, I already restart my phone, and also clear the data & cach of the camera : it doesn't work

Just to be safe, have you tried other ROM? If that still doesn't work, then try downgrading to Oreo. If all fails, then welp, at least you know that ROM isn't the cause of it.

dream2poet said:
By the way, I already restart my phone, and also clear the data & cach of the camera : it doesn't work
Click to expand...
Click to collapse
same happened with me on open beta 27.
i clean flashed ob 28, everything good so far.
try a factory reset or a clean flash.

I've had this issue before where I flashed nougat modem onto marshmallow and it gave me this error..it took accidentally wiping my phone to figure this out.
So try reflashing 5.0 rom or check whatever zip you flashed is not the culprit.

F4uzan said:
Just to be safe, have you tried other ROM? If that still doesn't work, then try downgrading to Oreo. If all fails, then welp, at least you know that ROM isn't the cause of it.
Click to expand...
Click to collapse
LELBOT said:
same happened with me on open beta 27.
i clean flashed ob 28, everything good so far.
try a factory reset or a clean flash.
Click to expand...
Click to collapse
tofuboi01 said:
I've had this issue before where I flashed nougat modem onto marshmallow and it gave me this error..it took accidentally wiping my phone to figure this out.
So try reflashing 5.0 rom or check whatever zip you flashed is not the culprit.
Click to expand...
Click to collapse
Thank you guys for helping me,,
I did Factory Reset (without internal storage) and all working fine now..
I think the problem happen because I did not do factory reset once i updated to Oreo

T-Mobile IMEI/baseband gone...help!

My mom has had a z2 force for almost 2 years...no issues, now all of a sudden data and wifi are gone and the phone doesn't have an IMEI. Seemingly after an ota update. As it's already old o figured I'd try to flash a rom to fix. I've tried returning to stock with the most recent flash all, the last flash all, tried installing lineage, tried installing 10 potato...nothing is working! Anything else I can try to get this working again???
I also tried to run other flashalls from xda, but didn't see a .bat file in the zip file....only a flash file...is there something else I'm missing? Sorry I'm not really proficient in motos

Mom wasn't dabbling in the dark arts known as pie was she? If not then you should be able to flash the latest TMO firmware then do a factory reset from recovery to restore the baseband.

She was still on Oreo when everything happened .....I attempted to flash the latest firmware, but still no luck...that's when I tried to install a pie rom---no luck there either

Draztik31 said:
She was still on Oreo when everything happened .....I attempted to flash the latest firmware, but still no luck...that's when I tried to install a pie rom---no luck there either
Click to expand...
Click to collapse
The trick to restoring baseband is the factory reset from recovery, not a reset from settings or anything else. As for trying to flash a pie rom, hopefully it was just a rom and not a pie firmware. If anything took from a pie firmware you might be sol.

It was just a rom, no pie firmware at all. I tried restarting from recovery and everything to no avail...is there a specific flashall you would recommend? I tried both the March and August T-Mobile ones...don't know if anyone has had success with a different one?