Develop Bugs

[Q] Problem with official JB update

Hey all,
Couple days ago i got the official update for my HTC ONE X to Jelly Bean 4.1.1.
I was extremely happy and installed it asap and the install worked great with 100% success.
Sadly , After the 1st launch the phone worked for couple seconds and then stuck for 2 seconds and just reboot it self , then it launched again and rebooted again after couple seconds.
It looks like a boot loop with official rom , I must say that the phone get to the "Desktop" main screen with the clock , but cant stay "alive" more then couple seconds and resets over and over.
FYI - When i enter Boot screen it doesnt reset , and when i plug the phone to the charger - it doesnt reset at all (even in the phone main screen - apps and stuff).
I dont wanna send it to repair because it can take up to 3 weeks without it.
I even started to think about Custom ROM , but i really want to avoid that when there's 4.1.1 official rom out there.
Any solution?
I will really appriciate that.
thx alot.

Does it stay enough for you to do a Factory Reset? If so do it (Both from Bootloader and from Settings) then you should have your phone good as new

Do a factory reset in bootloader menu,maybe it helps.....your phone is 100% stock now ?
Enter the bootloader menu by pressing and holding the power button and volume - button until it reboots into bootloader menu

I did factory reset both on settings and on boot screen , The problem doesnt solved.
My phone is 100% stock yeah.

Then i suggest you take it in for warranty ! If you unlock the bootloader and start rooting and custom romming you will definitely void the 100% warranty that you still have now !!!

Is there any option to Re-install the 4.1.1 update? or Roll back to 4.0.4 without unlocking the device?
Atm its 100% stock lock im reminding.

Rolling back to 4.04 is impossible without unlocking the bootloader. Installing the update again.....can't really answer that question ....sorry mate

doctorslay said:
Is there any option to Re-install the 4.1.1 update?
Click to expand...
Click to collapse
You can install the ROM from scratch if the RUU is avaliable, check htcruu.com.

[Q] Can't Install ROM's

I have tried to install [ROM][N7105] AOKP JB 4.2.1 [PUB] [FeB - 5] & the Nightly's on my 7105. It soft bricks every time. It tries to reboot after installing the roms and then flickers twice or so and goes black and has no more activity till I take the battery out and put it back. I have to install the stock rom through Odin to get it going again. I always do a factory reset & wipe cache before I install. What might I do to run custom roms? Thanks in advance for any help.

Hi. I have the same problem on my N7100. I could not install any custom rom. Tried CM 10.1 + gapps ( full wipe and cache wipe before install ) after install and reboot system screen flicks 2 times and goes black without any response. Must return to stock via Odin . Tried several times... result is the same. Before Note 2 used S3 and never had such problems with installing CM10.1. Hope someone will help.
Sent from my GT-N7100 using xda premium

I used my Note i717 and installed rom's on it all the issues as long as I didn't flash the wrong ones.

Any help?
Sent from my GT-N7100 using xda premium

I reckon these phones must be too new for us to get help.

My N2 screen flickers as well, just pressed the sleep button after awhile, and unlock it as usual via home screen.
Hope it works for you too

Your screen flickers after you install custom rom?

Almost every ROM I flash I have issues around booting. Some boot up how they should, but MOST don't...
I flash the rom and then I boot. The Samsung Note 2 screen shows but then flashes all crazy and stuff a couple times and then goes blank. I just wait a while and after a minute or so I start pressing the power button, and the screen will come up as it should on the lock screen or if its a brand new rom it will be at the set up screen.
What helps me to know when it has finished booting, is to connect the phone via USB to my Macbook, and when it is booted the mac will ask me to allow it access to the phone.
Just don't worry too much about it, coz it is ok and will work. Another way to see if it is finished booting is to wave your finger over the menu and back button, and it will light up when the phone has booted; you just have to keep trying to wake up the phone with button presses, but don't go crazy and keep pressing and/or holding buttons

Is there any custom ROM's for the Hong Kong version of the 7105 that I can try since the others won't boot?

[Q] Infinite boot loop out of nowhere.

I was using my phone earlier today and was attempting to extract an archived file with OfficeSuite 7. I had merely 400-500 of free space available at this point. After a few attempts and cancellations due to failure to extract I decided to restart my phone. Upon restarting it continuously will vibrate, show the Samsung logo for a moment, the screen will flicker off and it loops through that process all over again indefinitely. I can access download mode and recovery mode. I tried clearing the cache through recovery and removing the battery as well as smacking around the power button but it did not fix the problem.
I'm using stock TouchWiz Android 4.1.1 partly debloated, rooted, and stock recovery (because this ROM reflashes the stock recovery after a reset if a non stock recovery is installed).
I figure a factory reset might be the fix but I would need to extract my apps, settings, and SMS/all other data and I'm not sure how to do this with the phone in this condition and without an external SD card. Maybe I could flash ClockWorkMod, do a nandroid backup, and than extract this data with Titanium Backup? Can Titanium Backup do all that I am asking (I've barely used it)? Does anyone have an idea as to what the cause of the problem is to have this suddenly happen? I'm thinking it's the power button malfunctioning. The day prior twice my phone turned itself off.

Twrp has built in file manager. Copy to sd, then to computer?
Otherwise look into ADB.

what is happening
strange I am have the same issues . from working great to now FC and rebooting . almost like it the power button malfunctioning but it is not. Its something more. I was running DocHoliday 4.3 and was great . then I tried Aamir Mod V2 UVDMD5 4.3 same great . but this morning noticed it kept rebooting for no reason . wiped reset, nothing . looped and looped . wipe/reset and re-flashed and it will only stay on for a mintue . and if sleeps will not turn it F/C as soon as I touch power button.. crazy ???
anyone having the same problems with any 4.3 ROMs ??

I'm having the problem on my S3, but I'm not on 4.3 yet....
I already had this issue once 2 weeks ago and I factory wiped and started over. Fast forward two weeks forward and it started again today. WTF?
Qverse said:
strange I am have the same issues . from working great to now FC and rebooting . almost like it the power button malfunctioning but it is not. Its something more. I was running DocHoliday 4.3 and was great . then I tried Aamir Mod V2 UVDMD5 4.3 same great . but this morning noticed it kept rebooting for no reason . wiped reset, nothing . looped and looped . wipe/reset and re-flashed and it will only stay on for a mintue . and if sleeps will not turn it F/C as soon as I touch power button.. crazy ???
anyone having the same problems with any 4.3 ROMs ??
Click to expand...
Click to collapse

insaneoctane said:
I'm having the problem on my S3, but I'm not on 4.3 yet....
I already had this issue once 2 weeks ago and I factory wiped and started over. Fast forward two weeks forward and it started again today. WTF?
Click to expand...
Click to collapse
Are you using TWRP? I had a similar issue, upgraded to newest TWRP 2.6.3.1 and it was fixed. Before this I tried everything, factory reset/modem upgrade/different roms.. and it wasn't working..other than a rooted touchwiz rom.
Give it a shot.. might work..
As per Perseus71:
Install TWRP 2.6.3.1. Then take a Nandroid.
Next wipe /Data. Then flash your Custom Rom. Wipe Dalvik + Cache after the Flash.

[Q] sm-T210 brick - screen doesnt detect

Ok
i updated the firmware with odin last version to this OFW T210XXANC2_T210OXXANC2_T210XXANC2_HOME.tar.md5
All worked fine and the tablet kept the data, etc.
Now i installed the cwm and the 'android-armeabi-universal-root-signed.zip' from it.
For some reasson the tablet now is bricked for unknown reassons and its screen doesnt respond to finger touchs.
The tablet buttons and sound and booting works, but because the screen doesnt detect touchings, i cant do anything.
I have tried to install other cwm versions etc, and to reinstall the firware, and also that pre-rooted firmware on this forums, reset factory from cwm, etc. No success unfortunatelly.
Please help

anybody ?
i have installed kitkat firmware, the screen doesnt respond touchs
i have installed last jelly bean firmware, the screen doesnt respond
i have installed stock firmware, stucked in the samsung logo
help !
rotation sensor works, buttons works.

same problem ....
arfgh said:
anybody ?
i have installed kitkat firmware, the screen doesnt respond touchs
i have installed last jelly bean firmware, the screen doesnt respond
i have installed stock firmware, stucked in the samsung logo
help !
rotation sensor works, buttons works.
Click to expand...
Click to collapse
You have installed a rom for ROmanian Tab 3 7' Wifi, if you rezolved the problem please let me know how you did it becouse i have the same proplem and i tried everything , i try to install - uninstall a lot of ROM'S Kernel but no response the TAB3 is suck in Samsung logo or TAB 3 Logo . Please Help with a working rom or kernel ...

I had this when playing around with stock kit kats italy to france holland then back to stock jely bean then nole kat rom
Flash the stock firware for yhe tab with odincheck auto restRt and ftime is only on
Right after its near the end off flashing its gonna reboot keepp cable connect still
And hold home button and volume up when it turns off from downloading screen
get in stock recovery mode wipe cache and factory wipe
And reboot system
As its reboot hold home and volume down to get downloading screen
check at top thats its both offical if yes power off and start up
If no reflash again and do the same then it work to setup
Most off the time 2 flashes off stock does the job

Stuck On Cyanogenmod Bootscreen

Long story short, I had recently installed the cyanogenmod to my phone, don't like it, tried to flash it back to the stock rom and the rom couldn't install. The installation wizard restarted the phone, now it's stuck on the cyanogenmod boot screen and the notification light lit as if im charging the phone, but it's not plugged up. The bad part about all of this is that the battery isn't removable so now I have to wait for phone to die I guess but is my phone now bricked? Once it dies can I recover from this by booting it up thru recovery mode?

atlJE said:
Long story short, I had recently installed the cyanogenmod to my phone, don't like it, tried to flash it back to the stock rom and the rom couldn't install. The installation wizard restarted the phone, now it's stuck on the cyanogenmod boot screen and the notification light lit as if im charging the phone, but it's not plugged up. The bad part about all of this is that the battery isn't removable so now I have to wait for phone to die I guess but is my phone now bricked? Once it dies can I recover from this by booting it up thru recovery mode?
Click to expand...
Click to collapse
I have the same issue. I suspect the person I let use it tried to use the options menu to reset the phone back to factory specs, which I was warned on here that would brick it, so mine is stuck in the round and round boot screen for CM. I think you're supposed to use the factory reset in CWM to delete personal stuff. I'm trying to figure out how to fix it and if I come up with something I'll let you know.

flash back to stock rom
atlJE said:
Long story short, I had recently installed the cyanogenmod to my phone, don't like it, tried to flash it back to the stock rom and the rom couldn't install. The installation wizard restarted the phone, now it's stuck on the cyanogenmod boot screen and the notification light lit as if im charging the phone, but it's not plugged up. The bad part about all of this is that the battery isn't removable so now I have to wait for phone to die I guess but is my phone now bricked? Once it dies can I recover from this by booting it up thru recovery mode?
Click to expand...
Click to collapse
Good thing is you are not "hard bricked" just "soft bricked." Press the power button and volume up and hold till your phone reboots then immediately press the volume button and power down button to enter recovery.Then do a complete wipe, factory reset, then and only then reflash your stock CWM backup of your stock Rom . Just guessing mind you ,because I do not know every single thing you did before trying to return to stock but you should always do a full Wipe or factory reset before flashing between different roms. If your trying to flash a stock image, not a CWM backup, of your firmware you'll need to first reflash your stock recovery and relock your boot loader.
Is your phone a single SIM or dual SIM? Dual SIM phones have allot more issues on Cyanogenmod . If yours is dual SIM I'd stick to stock Rom or sense based custom roms made for our device. By the way what didn't you like about CM if your on a single SIM phone? It had a few issues but with a few tweaks you can get it working great and it's alot less bloated than stock lollipop. I'm on unofficial 12.1 CM with the a5_chl single SIM and it's fine. Having said that I had to tweak several things and I exempt dual SIM versions from my reasons for me liking this Rom. I get that it's sadly alot buggier for those phones . Let me know how things go in fixing your issue and best of luck.
---------- Post added at 10:43 PM ---------- Previous post was at 10:02 PM ----------
Ddreth said:
I have the same issue. I suspect the person I let use it tried to use the options menu to reset the phone back to factory specs, which I was warned on here that would brick it, so mine is stuck in the round and round boot screen for CM. I think you're supposed to use the factory reset in CWM to delete personal stuff. I'm trying to figure out how to fix it and if I come up with something I'll let you know.
Click to expand...
Click to collapse
First thing, some friendly advice and I truly do mean friendly, not accusing, but you should never let anyone else touch your device when it's in custom recovery. They can seriously mess it up not just"soft brick" it like yours is now.
2nd thing is the factory reset in your custom recovery doesn't have anything to do with your personal files. It's to clean your system and its data so that you can do a fresh install of a different Rom. It's called a "clean flash." A dirty flash is when your upgrading the same custom Rom and you just flash it over the previous version without wiping then clear your Dalvik cache and reboot. These wipes leave your personal files on your internal and external SD card intact unless you specifically wipe then in your custom recovery . They just call it factory reset to make it familiar to the stock Roms use of the term in my opinion. When you have this"soft brick" you can press your power button and volume up to reboot then quickly press power button and volume down to enter recovery. Then factory reset or wipe Dalvik cache if not wanting to reset and reboot one or the other should get you back into your rom.
Hope this helps and good luck plus let me know if this works to resolve your issue. Be happy to help in any way because I have been there myself in the past. Bootloops, soft bricks,etc etc................... If you can name it, I've messed it up.