Hey all, been poking around the forums and trying out various WM and Android ROMS and they all seem to work beautifully, kudos to the devs.
I seem to be running into a bit of a problem though.
My phone is an MP6900 (Vogue 100) from Bell. And while the roms work great, the second my phone goes into standby mode (when not attached to my comp) the phone resets.
I have tried four different roms, two android and two WM and the problem persists.
Also hard resets, battery removal etc etc to no avail.
I also tried to roll back the radio as that got updated when I went to my stock rom previously.
And to boot I can't seem to flash back to the stock ROM anymore, while I was able to even just yesterday. I get Error 262, for whatever reason.
I was wondering if anyone else has run into this issue and could point me in the right direction.
And I did a search on the forum (pre-registration) but couldn't find anything, sorry if this has been brought up before.
Again, great work on all of the ROMs! I had no idea phones had come this far. (Sad to say but true lol)
JustinHTC said:
Hey all, been poking around the forums and trying out various WM and Android ROMS and they all seem to work beautifully, kudos to the devs.
I seem to be running into a bit of a problem though.
My phone is an MP6900 (Vogue 100) from Bell. And while the roms work great, the second my phone goes into standby mode (when not attached to my comp) the phone resets.
I have tried four different roms, two android and two WM and the problem persists.
Also hard resets, battery removal etc etc to no avail.
I also tried to roll back the radio as that got updated when I went to my stock rom previously.
And to boot I can't seem to flash back to the stock ROM anymore, while I was able to even just yesterday. I get Error 262, for whatever reason.
I was wondering if anyone else has run into this issue and could point me in the right direction.
And I did a search on the forum (pre-registration) but couldn't find anything, sorry if this has been brought up before.
Again, great work on all of the ROMs! I had no idea phones had come this far. (Sad to say but true lol)
Click to expand...
Click to collapse
Sounds like a dying battery to me.
It worked fine in the original Windows though so that's why I am a bit baffled.
what happens if you put your device in bootloader and try to flash to stock? Error 262 is a connection error. basically happens whenever some event interrupts the flashing process (a dead battery will cause this). If you haven't yet, try to flash to stock via the method in this post (bootloader and then flash)
Tried that, didn't work. Just gets to 31% and pops 262 no matter how I try to do it.
The odd thing is though that I can flash any other ROM just fine.
Would reformatting the SD card work?
Figured it out. I used the 0.41 ROM to unlock the phone which was causing the issues. I reflashed with the 2.3.1 and everything works fine.
JustinHTC said:
Figured it out. I used the 0.41 ROM to unlock the phone which was causing the issues. I reflashed with the 2.3.1 and everything works fine.
Click to expand...
Click to collapse
0.41 was reportedly having tons of issues, you should have started from there
Glad you got it working.
So here's my story of what's going on and hopefully a solution can come out of it.
Got my phone used it for a bit. I used the root and debloat found here: http://forum.xda-developers.com/showthread.php?t=2282367 and everything went fine. Waited a day or so and decided to flash LiquidSmooth ROM with KToonzes 7.2.13 . Again everything working fine. I then flashed 7.7.13 Ktoonzes and lost bluetooth functionality as far as the phone is concerned but the music portion is fine. My brother convinced me that the Google Edition ROM is where its at and I was having that bluetooth issue so why not. I flashed the AOSP Ktoonzes instead of the TW so my phone bricked. I did the ODIN back to stock with: http://forum.xda-developers.com/showthread.php?t=2261573&highlight=odin . When that went through and my phone was doing its set up, my wifi wasn't turning on. I continued by using the root and debloat again to reinstall the recovery. I recovered my phone to right before I flashed the Google Edition, and my bluetooth is not even finding my car in pairing mode at all at this point.
Thanks for reading and thanks in advance for any recommendations to fix this issue.
Well,hello there! So,i got this phone as a gift a while ago(from Italy),everything was working fine but one day i got a bootloop and phone would just hang at the ''TIM'' logo...I thought it was just a bug,i deleted the data/cache but nothing,left it for 4 hours and nothing happened...After searching everywhere for a copy of the stock rom with no luck,i went ahead and installed the A460 stock rom and i was surprised that it booted,but only with one problem,the touchscreen is not working and i cannot use an OTG cable to control it with mouse/keyboard. Could it be the the hardware,or the software (i guess that a460 has a different touchscreen and the drivers are different in the rom)? If someone could provide me with a copy of the stock rom it would be welcome. Have a nice day!
So I wanted to try out Pie on my device and I already had TWRP installed. I went through the process of formatting to remove the encryption, then I flashed the ROM + Gapps I then booted in and it was working fine. I then flashed the standalone Nougat bootloader so that I could use the fingerprint. All was still working fine until I tried to charge it. It would say "Charging slowly" and it was charging very slowly, and even managed to drain faster than it could fill even when not using it. At some points I did manage to get charging rapidly but then without even moving the device it would go back to charging slowly. I have now changed to a different ROM which is Oreo and it definitely seems more consistent so far but I still do have trouble getting it to charge quickly. Before I flashed the new ROM yesterday I was not having any problems charging. Does anyone know what could be the cause of this issue and how I can resolve it?
I had latest stock firmware and everything was working fine except it wasn't getting any updates so I decided to flash Linneage. I followed instructions, made sure to flash the copy-file on both slots etc. Everhything seemed fine untill I left my home and didn't have access to wifi, then I noticed that data didn't want to work. It showed having 4g connection (full strength) but it was so slow that I couldn't even check speed because the homepage barely load. There was a connection but since it was so slow I received timeouts almost everything I tried. I also noticed that bluetooth didn't work. It would connect/disconnect every 3 seconds from my bt headset. This was "fixed" by disable google on my phone. Very strange.
I thought It might have to do with Linneage so I tried Pixel experience. Exact same problem there.
I thought maybe the linneage files I flashed to both slots were bad so I reflashed stock rom. Now I have the same problem with stock rom as well. I eventually used the MSM tool and reflashed the latest stock firmware, locking the bootloader and all that. Still having the same problems. These two problems were non existant before any of this.
I've tried my sim in a different phone, even made sure the apns are the exact same on my working phone and my op6t.
Is there any other way to make sure the phone is completely factory restored other than MSM tool? Now I'm running stock oxygen, no root, locked bootloader etc but the problem persists. What is my next step to try?