I had the Photon Q with the SIM mod and CM 9 working for 2 mouth. But yesterday, I were using the cellphone when it reboot itself and get freeze on the unlocked bootloader warning. I try to power it of but y could not, the I let it there until batery drain (about 4 hours)
Now when I boot the cellphone it has an strange behavior. Some times it freeze on the unlocked bootloader warning, other time make a loop boot (show the warning and restart). Also some times it display strange colors on the screen when try to boot and many times it display a randomly sorted grey vertical lines and very few times (one of every 50 times) it boot the ROM but when i touch the screen it goes black.
i can not conect to phone by adb and can not enter recovery, but i can access to the fastboot (in fact the fast boot is working but do not display anything on the screen, i suppouse that the same happend with the recovery. but i can not use it if the screen is black)
I used the fastboot and RSD to flash the stock firmware, the phone return fail on every 4.0.4 ROM but it work with the 4.1.2. After the flash some times thes phone display the morotola and sprint logo and then start the handfree configuration, but when I touch the screen it goes to black again.
I do not know if it is bricked, I think that if i have access to the fastboot i can resurrect the phone. but is very strange the random behavior.
Do you have any idea what should I do?
Thanks.
PS: sorry for my bad english
Re-Strange behaviour
Hi there, one of my Q's (also sim modded) was doing a similar bootloop warning etc. I was screwing around with it a bit. It's all good now though.
The way to force power down/reboot is to hold "volume -" and the power button for 10-15 seconds. If you drain the battery, you will be stuck with more boot-loops due to a flat battery. If you plug the charger in & the LED is green, this means it is charging a dead battery, & will need to charge for a while.
By the way, I had issues on my other Q handset running CM, failing to read the mSD card, and causing freezes, boot loops etc, so I went back to stock. Pretty sure most of the trouble is due to the mSD card read/mount error.
Edit:
Come to think about it - my Q failed after I tried to restore my CM10.1 backup from the previous phone. I suggest this may be contributing to the issue, as you are also running CM.
With the black screen/boot loop, force reboot by holding "vol -" & power button for 15 seconds, release power, then immediately hold "vol +" so it forces boot to recovery (TWRP if you have it).
I restored a previous backup eventually, but TWRP was not working too well after the screwy boot-looping etc. I ran a factory reset from the phone menu once it was running again, then rebooted into TWRP.
Super User wouldn't install from TWRP after, so I pushed it across & installed from TWRP, now I'm about to update TWRP to 2.6.
Still want to have a go at another ROM on this handset, so I can compare it to my stock one. I'm pretty sure CM10.1 was part of the problem on the other Q with my mSD card failing, as it has been fine ever since on stock.
Try this:
Try using adb to fastboot into recovery, then push TWRP (again) onto your Q using this method by arrrghhh http://forum.xda-developers.com/showthread.php?t=1887070
Push Super User across onto your mSD & install that from TWRP as instructed also.
Restore a stock/custom backup from an earlier time if you have one, or flash a fresh download.
Let me know how you go.
P.S. make sure you have "USB Debugging" enabled in developer options in order to ADB fastboot recovery.
schmandroid said:
Hi there, one of my Q's (also sim modded) was doing a similar bootloop warning etc. I was screwing around with it a bit. It's all good now though.
The way to force power down/reboot is to hold "volume -" and the power button for 10-15 seconds. If you drain the battery, you will be stuck with more boot-loops due to a flat battery. If you plug the charger in & the LED is green, this means it is charging a dead battery, & will need to charge for a while.
By the way, I had issues on my other Q handset running CM, failing to read the mSD card, and causing freezes, boot loops etc, so I went back to stock. Pretty sure most of the trouble is due to the mSD card read/mount error.
Edit:
Come to think about it - my Q failed after I tried to restore my CM10.1 backup from the previous phone. I suggest this may be contributing to the issue, as you are also running CM.
With the black screen/boot loop, force reboot by holding "vol -" & power button for 15 seconds, release power, then immediately hold "vol +" so it forces boot to recovery (TWRP if you have it).
I restored a previous backup eventually, but TWRP was not working too well after the screwy boot-looping etc. I ran a factory reset from the phone menu once it was running again, then rebooted into TWRP.
Super User wouldn't install from TWRP after, so I pushed it across & installed from TWRP, now I'm about to update TWRP to 2.6.
Still want to have a go at another ROM on this handset, so I can compare it to my stock one. I'm pretty sure CM10.1 was part of the problem on the other Q with my mSD card failing, as it has been fine ever since on stock.
Try this:
Try using adb to fastboot into recovery, then push TWRP (again) onto your Q using this method by arrrghhh http://forum.xda-developers.com/showthread.php?t=1887070
Push Super User across onto your mSD & install that from TWRP as instructed also.
Restore a stock/custom backup from an earlier time if you have one, or flash a fresh download.
Let me know how you go.
P.S. make sure you have "USB Debugging" enabled in developer options in order to ADB fastboot recovery.
Click to expand...
Click to collapse
I tried it, but do not work.
I flash the stock ROM from fastboot and also flash several recoverys, but never boot any ROM and I think that i access to the recoverys but the screen is black then is very dificult to use it. Is strange beacouse some times screen displays perfect the unlocked bootloader warning, but never display anything on the fastboot or the recovery.
Witch part of the software have the video drivers that are used on the recovery and fastboot? I think that maybe is corrupted. how can i flash it again?
Thanks.
Hello. My sister has a Galaxy tab 2, and I rooted it several months ago. Today, after letting it on the charger last night, I find that the charging animation is on for a few seconds, then the device reboots and repeats the process. I couldn't connect to my laptop or get into recovery. I need to know what to do to fix it, do I use Odin and flash stock? Also, I'd like to put cyanogenmod 10 on it, what's the latest stable build, and how do you put it on the tab?
jrk190 said:
Hello. My sister has a Galaxy tab 2, and I rooted it several months ago. Today, after letting it on the charger last night, I find that the charging animation is on for a few seconds, then the device reboots and repeats the process. I couldn't connect to my laptop or get into recovery. I need to know what to do to fix it, do I use Odin and flash stock? Also, I'd like to put cyanogenmod 10 on it, what's the latest stable build, and how do you put it on the tab?
Click to expand...
Click to collapse
try to boot into recovery and wipe cache partition this might help you
and try latest aokp rom for tab 2 its great
I had recovery flashed, I somehow managed to fix this. I booted while holding the volume up and down buttons, then pressed, not held the power button. It wouldn't charge while it was on or off, so I powered off normally. It then started charging only when it was off. I used CWM's ROM manager to flash CWM, then backed up, wiped, and installed CM 10 stable. I'm a fan of Cyanogenmod, I've ran it on about every phone I've owned.
my nexus 4 was on temasek's unofficial cm12 build ver 6.1
recovery in use was recovery-philz_touch_6.59.0-mako
i decided to update the rom to build 6.5, so i downloaded the zip to my sdcard,
i had not made a nandroid bkp
after flashing the rom/gapps/superuser, wiping dalvik and cache, things went wrong
after that the phone would only show 'google', then freeze, then go blank, then again show 'google'. this is the first Loop i have encountered where the boot animation never even showed up.
after that in about 8 hrs, i tried all of the foll-
installing the stock images: my phone booted up the first few times i flashed stock images using fastboot, but after three times (because each time it successfully booted i would go back to recovery to try flashing the customromzip) my phone stopped booting up for stock.
it resolutely stayed stuck on the boot ani.
recovery: flashed many times, via sdcard and also via fastboot. no problem with the recovery
zips. absolute fail. nothing can get me past the 'google'
now there's another peculiarity, which makes me wonder if there is hardware damage involved in this softbrick story
after all this flashing my charge came down to 20%, so i tried to charge it (switched off, obviously, since it isn't booting up)
but every time i connect my charger, it boots up,and then shows me google, and freeze and restart..same old cycle
in a last ditch attempt to somehow charge my phone i have brought it to fastboot, and left it connected to my laptop. i don't know if this will work.
please help, also i am now considering using a toolkit, unified android or wugfresh (the latter, i have a previous bad experience with) to get my phone to atleast switch on with something.
should i use the toolkit or just take my brick to the servicecenter to check for damage to hardware
I am on Sprint. So I upgraded to OF6 through Odin. I dislike it plus Wifi Tether doesn't work (both Wifi Tether Router and the unlocker). Wifi tether works for about 10 minutes and then it will stop (shows it's still on but no more wifi)
So I downloaded Kitkat (ND2 and NK4). Factory reset the phone, wipe cache, go into download, set up Odin, connect the phone and hit start... aaaand it immediately fails. Phone shows SW REV CHECK FAIL. The phone still functions.
Any help?
You are locked. Since OD3 you can't downgrade to KitKat. Try installing a custom rom lollipop based, like MOAR.
I was in the process of giving up anyways xD Installed Pacman. Thank you for the information. I couldn't really find anything that verified that Sprint did this as well. It looked like only AT&T and Verizon -_-
Hi. Can I downgrade from OD3 if I installed a custom rom?
damntuco said:
Hi. Can I downgrade from OD3 if I installed a custom rom?
Click to expand...
Click to collapse
No you can't downgrade from OD3, a custom rom won't make any difference. Sprint chose to lock the bootloader for OD3 and any version after
What if you're unlocked on kitkat (MOAR) - and you choose to try out a custom rom that's using OD3 or higher? Can you still go back?
Bigjohn_S said:
What if you're unlocked on kitkat (MOAR) - and you choose to try out a custom rom that's using OD3 or higher? Can you still go back?
Click to expand...
Click to collapse
As long as it isn't the official rom via odin you will be good. It's the newer bootloader that prevent you from flashing back so as long as the rom you choose is a recovery flashable rom you're OK. The MOAR 6.2 thread has a link to the latest version of lollipop with the ability to have the unlocked bootloader. Oa6 I believe, I'd suggest you flash that and get on to MOAR 6.2, it's bad ass!
what does MOAR 6.2 bring? I like kitkat... keeping 'material design' to a minimum is my goal. (if I wanted a windows8 phone, I'd have bought one... pretty pastels and all!)
Bigjohn_S said:
what does MOAR 6.2 bring? I like kitkat... keeping 'material design' to a minimum is my goal. (if I wanted a windows8 phone, I'd have bought one... pretty pastels and all!)
Click to expand...
Click to collapse
Newer, faster, all around better imo but ymmv
banccalif said:
Newer, faster, all around better imo but ymmv
Click to expand...
Click to collapse
My problem is if "newer, faster" brings along "more material design crap", then I'm not interested. Yech. Flat, 2d, pastel color garbage needs to die ASAP.
Make a nandroid of your kk setup. Then Odin to OA6, no OD3 or OF6. If you don't like it, then go back to kk.
Thanks.
But I was on lolipop (stock) which is one of the reasons i personally went for moar 2.2
And I've looked for older versions of apks for some of my apps too - ones that tipped over the cliff with material design pastel blue and pink and yellow... OW my EYES!
Downgrade to 4.4
I can't get any 4.4 Rom to work with OF6. Is there anyway to make it work?
az1995 said:
I can't get any 4.4 Rom to work with OF6. Is there anyway to make it work?
Click to expand...
Click to collapse
No.
OF6 stuck?
So I was on OA6 G900P stock twrp and CF Odin rooted, and thought all was good (just updated from KK) and thought, hey, since I updated because of signal/modem issues, I might as well get the newest one. Odin flashed OF6, reboot, waited 45 minutes, still on boot logo. force reboot, waited 16 more minutes, still on Samsung logo... Figured crap, I got a bad flash...
pulled the battery, got to the stock boot menu, it said I was on baseband OA6, binary custom, system custom. I thought crap, it didn't do anything, no wonder it won't boot. So I went back in to Odin and did it again (while downloading another copy of the tar.md5 from a different source), flash went good, tried to flash CF root in Odin, failed. figured, oh well, I'll just add twrp and flash CF from there... twrp failed. Rebooted to see what I'd get, 30 minutes later, still on Samsung logo...
So I pulled the battery again, got back to the boot menu and over to the Odin screen, now it says binary official, system custom, then a big old message "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again."
Well, I don't have Kies installed, and the download page at Samsung won't load. from this thread, I take it I cannot downgrade at all, OA6 fails in Odin with fail(Auth). And on My S5 it says:
SW REV CHECK FAIL : [aboot]Fused 3 > Binary 1
Any ideas? I'm hunting an OD3 download from somewhere now. Kinda perturbed, as I researched for 5 hours yesterday to prep for this update from 4.4 (yes I just moved to OA6 this morning), and didn't even find this version until AFTER I had OA6 on my phone today, but nothing about any issues with OD3 or OF6 came up in searches. Now all I care about is getting the f'ing thing to boot.
Sort of a retarded policy to prevent ANY downgrade, what to they expect to do if they roll out a brick update, like has happened to various phones in the past? (fyi, I have been watching the loading bar for 15 minutes trying to "open" the download page for Kies on both samsung.com and samsung-kies.en.softonic.com and both still have a blank page)
***UPDATE - opening the download page in IE worked fine...
***UPDATE 2 - post Kies...
Kies comes back and tells me that my device is not supported by Kies 3. Multiple restarts later (every restart comes immediately to the same screen), I was able to get the Custom OS installation screen to come up, and pressing the volume up key got me back to Odin mode, withOUT the stupid firmware upgrade failed use Kies screen. At this time I have no idea what to try... I am hunting a download of OD3 to try, if not, then I will try OF6 again, plug the phone into the wall and let it sit on the boot logo until tomorrow and see if that works.
***UPDATE 3 - waiting on boot logo
New Download (again), new computer, new cable. Flash failed the first try (OF6), disconnected cable and plugged it back in same port to try again. Second flash attempt passed, now waiting on boot. I did not try to flash anything but the stock firmware this time. As I said, I just want the phone to work. If nothing works this time, I'll take it to a non-reseller Sprint store and see if they'll either update it for me or pass me a refurb.. Battery was full when I flashed it, so I'll wait till the battery dies tonight before giving up. (adb does not find the device while it is loading the boot logo, from previous devices, that tells me it is failing to load the boot loader, but I haven't done this but once in the last 16 months, so maybe I'm wrong). I did notice with flashing OA6 I had a boot sound on first boot after Odin and it took 12 minutes to get to the welcome screen, every flash of OF6 I have not had any sound on boot up.
***UPDATE 4 - amazingly fast battery drain from 90% black boot animation...
Well the battery tanked in about 1hr 15 minutes. I pulled the batter, SIM, and SD, then let it charge 7-12 minutes, reconnected to Odin, flashed the brand new 2.8.7.0 TWRP (in ODIN) and it worked... rebooted to TWRP and let it install root on exit, no idea if it succeeded, I can verify it moved the recovery image so TWRP would not get overwritten during boot though, but the last line (immediately after the "Installing SU..." line was on screen about 250ms before the phone rebooted... I've been watching the boot logo ever since, still no Android OS and still unable to detect the phone in ADB (in TWRP, it showed up without permissions, so I know if it ever boots I'll need to change those settings). Next test is to try a factory reset, if not that, then I'll try to restore the OA6 nandroid I took this morning.
***UPDATE 5 - restored OA6 nandroid
twrp let me in, I restored my OA6 nandroid, boot (took 0 seconds), system, and data only. Immediately on reboot (no prompt to root, good sign as I rooted before the nandroid), I had a startup sound! (noticed later that this only happened once) about 60 seconds later I had a big freaking white box with "System is not responding. Do you want to close it" and wait/ok buttons. I waited about 30-45 seconds as I started editing this post, then hit wait. it disappeared, and I saw cell signal 3/5 bars, and the battery % and charge icon at the top, then the screen went black. about 20 seconds after that I had a Samsung boot animation going at a reduced screen brightness (dark enough that I almost cannot see the animation). I'll pause typing now to wait and see what it does... repeat of the same, except I did not see the notification bar icons this time, and it rebooted after maybe 12 seconds of delay. This time I tapped ok... No difference. During all of this, none of the buttons on the phone appear to have any impact on what is going on. and ADB is not picking up the device during any part of this.
Back to TWRP and full restore of the backup (I took all 7 partitions in the backup), boot took 1 second this time... I've noticed that the CPU temp seems to sky rocket during the boot animation. this last time it went up to 68C, after I let the phone sit charging and finally got back into TWRP it was at 40C. 1 second for EFS restore and 2 seconds for modem. again, 60 seconds and the force close box came up, another 40 seconds and I saw the signal strength and battery% plus charge icon.
Back to TWRP again gave me my old TWRP vKT-2.8.4.2, ADB works again as well, so the restore is definitely overwriting the partitions. I pushed the OD3 de-odexed rom to my SD card and flashed it...
***UPDATE 6 - OD3 de-odexed
Ok, so I already typed this and then lost it... long story short, it upgraded android, then did the same crap, but I got a water droplet sound when clicking wait on the System is not responding, saw LTE data for a bit, then it rebooted any way, same crap. Going to reflash OF6 in ODIN and see if I can get anywhere with that, then try some roms... need to let the battery charge up a bit first though. Laterz, if there is another update, it will be a resolution, if not...
I guess this would be double posting, but I have a working phone and prefer to put what I did in a separate post, than to add it at the end of a bunch of troubles; The only thing not mentioned here but is above, I updated from 4.4 Alliance Rom to 5.0 OA6 stock via Odin, plus CF auto root via Odin, and ktTWRP (2.8.4.2) also via ODIN, as soon as the system came up to the welcome screen I rebooted to TWRP without doing anything and took a nandroid of all 7 partitions. And then updated to OF6 not knowing the new bootloader restrictions. The end problem was that OF6 did not boot. Below is a logging of what I did over the last 2 hours and the end result is that my OA6 nandroid is running with the OF6 bootloader? (not sure about this one), kernel? ( I think so), and modem. I am sure some of the more experienced guys around here would know. Personally I like to crack flash till I find something that works, then I might not flash again for 12-24 months, depending on if there were any bugs or not.
So here it is, I hope in the future someone somewhere is helped by this. If mods think this should be it's own post and chop out some of the useless parts to make it guide like, I approve of anyone else using this info and doing it.
wait times on boot up range from 10 minutes to 6 hours with no change. Any time something happens during boot it is always between 30 seconds and 12 minutes. Only while in recovery mode does ADB detect the device, with TWRP 70 it shows without permissions, with ktTWRP (42) it shows the device ID and allows access from adb.
flashed OF6 - Odin - AP
reboot - no audio - no boot
reboot - boot menu - factory reset
reboot - no audio - no boot
reboot - boot menu - wiped cache
reboot - no audio - no boot
flashed OD3 kernel - Odin - AP
reboot - audio - no boot
flashed cf auto root - Odin - AP
reboot for root install - straight back to Odin mode intentionally
flashed twrp 70 - Odin - AP
reboot - audio - no boot
reboot with vol+up - audio - no boot
reboot - twrp 70
flashed fusion 6.0 nightly 8/7/2015 - wiped cache and dalvik - reboot - got Fusion boot animation - no audio - yellow LED - after 8-9 minutes I got a blank screen - I pressed home and got "Unfortunately WFC Settings has been stopped" ok - "Unfortunately Phone has stopped" ok - blank screen - tap screen and capcitive buttons backlight comes on touch either bbutton, get vibration feedback, but nothing else, touch hardware buttons, screen goes off and on, but no other response. 30 seconds later Unfortunately phone has stopped, before I tap ok, I get a background image. Ambient light sensor appears to be able to dim screen brightness, no buttons give any visual effect, other than power button. No notification bar as of yet. 13-14 minutes after initial boot start up, the phone restarted itself.
reboot - loop? - Fusion boot animation - no audio - 4 minutes alter I got "fusion is starting" - lasted 25 seconds - then black screen with "Unfortunately, WFC Settings has stopped" ok - then phone - ok - then both again - ok, ok - blank black screen - 6 minutes later and several "unfortunately ... has stopped" I realized the screen had turned off. Turned it on, and there was a welcome screen with a crash screen on it, I went to type this and the screen went black, welcome screen did not come back, 10 seconds later - adb detected the device by name/ID an says unauthorized - system crashed - adb now shows all ??????? - unauthorized - long press power button brings up the reboot menu (has "settings" but when I press it, it just goes back to the blank black screen) - the only thing that worked from teh power menu was reboot (I would guess power off does too) even gives me the reboot screen with the spinning thing. during the reboot notification and before it actually restarts, ADB recognized the device again.
reboot - during boot up ADB goes to ???? unauthorized for 30-50 seconds, then shows correct system ID/name and unauthorized again - LED is off for the first time since flashing rom (did not even turn off when disconnecting from PC, connecting to laptop, disconnecting from laptop, plugging in to wall, disconnecting, plugging in to laptop...) - boot took 9 minutes 20 seconds - came up to android logo, then Fusion is Upgrading, shot through the apps r
eal quick, then everything stopped again...blank black screen, Amber LED back.
reboot - TWRP 70 - restore nandroid - system/data only OA6 stock - factory reset
reboot - waited 60 seconds before getting boot animation - waiting patiently to boot, ADB shows correct device name and unauthorized the entire time, no LED - waited 30 minutes, still on boot animation
reboot - TWRP 70 - factory reset - restore nandroid - boot/system/data OA6 stock
reboot - no audio - 40 seconds later - welcome preparing your device this may take 3-4 minutes came up - finalizing android upgrade after 30 seconds - update successful - LTE, setup wifi, EULA, software update screen, none found... tap and go.. skipped - add google and samsung. The Sprint filled my System up with crap... looks like it is working.
***UPDATE - 8/15/2015
I had some issues with system crashing again after the first reboot, but I waited on a blank black screen for about 16 minutes and everything loaded up. seemed to run fine, same issue next reboot... Instead of working on it, I flashed fusion ROM, never booted, I let it sit on the boot loader for 4.5 hours (fell asleep), then I flashed MOAR, I have not had any issues since. Checking a few other threads led me to believe I had lost IMEI, possibly the entire partition as I had all of the symptoms after a firmware update; however it is all there, or the restore of my OA6 nandroid put it back, not sure as I did not figure that out until much later on. Good thing I followed at least one smart rule... NANDROID before FLASH! good luck everyone.