Main:
Ok, so I was waiting until i got a new phone so i can root my g2, well never happened as my g2 decided to randomly freeze up and restart and get stuck in boot loops either on the LG logo, or freeze on the T-mobile splashscreen and restart infinately. So now i got a new phone and i want to root the old one, But first up I need to figure out what is causing the random boot loops, freezing, and shut offs. It's a T-Mobile variant
ALSO: IT WAS NEVER ROOTED, So it's not a root related issue.
NOTES:
plugging it in help increase chances of escaping loop
It doesn't require a plug in to fix but it helps.
Reboot/Glitching occur when phone is in use and out of use.
Phone works normally otherwise but suffers these glitches
Phone has be factory reset twice
Phone has no external damage
Possible Internal:
Broken L. speaker due to rain
Maybe water damage from steam (phone was on counter as i showered a few times)
possible battery issue
Maybe a bit of drop damage as i did drop it a bit, but it was in a tech21 impactology case, and it remains not cracked
I have a similar issue. The phone will loop the LG logo, but only sometimes--at other times it will poop android's boot animation until it decides it wants to boot normally.
It happens in every ROM(ota or cuatom) even after flashing the stock .tot file about 4 times, so it's clearly a hardware defect for me & probably you too. I read the logs & saw rtc blah blah time will be lost on reboot & other errors. During normal use it randomly freezes prior to rebooting itself, though it reboots even while idle for long periods.
Unfortunately I don't have a solution for your problem besides restoring the stock image.
http://forum.xda-developers.com/showthread.php?t=2432476
After that you can trade the phone in, sell it, or send it to LG.
Powered By "Yeeart!"
So If i reflash to STOCK will it work for a short time normally and in x weeks/months resort to it's retardism of loops
pvt900 said:
So If i reflash to STOCK will it work for a short time normally and in x weeks/months resort to it's retardism of loops
Click to expand...
Click to collapse
It fixed my problem temporarily, but not too long afterwards all the issues came crawling back. For this reason I suggested ditching the phone completely unless you really want LG to examine it.
Powered By "Yeeart!"
Since i own 2 G2's is it worth my time re flashing to stock and then rooting the phone, cause i plan to run my sim carded phone as my normaly device and my root would handle experiment tech uses and hacked apps/superuser apps and such stuff
pvt900 said:
Since i own 2 G2's is it worth my time re flashing to stock and then rooting the phone, cause i plan to run my sim carded phone as my normaly device and my root would handle experiment tech uses and hacked apps/superuser apps and such stuff
Click to expand...
Click to collapse
I've heard of the random reboot issue. Fixes have been created and detailed. Please give me the following info, and I can help you resolve the problem:
Current Baseband Version
Current Bootstack / Modem
Root status in recovery
Current ROM and Carrier
Current Recovery
I'm having the exact same issue with my D800. I was rooted and had run a couple of ROMs but returned to stock right after I started experiencing the reboots. Unfortunately, the return to unrooted stock - and upgrade to lollipop - didn't fix the random reboot issue.
I've noticed that when my phone shuts off I typically need to hold down the power button at least a min to get it back up and running. And when I get it back up and running the battery stats show a substantial drop in battery - between 5-10%. I took it to a local shop and they said it was a bad motherboard. I've read some threads about shorting some pins on the MB and then reinstalling pieces of the boot image piece by piece and then use the LG Flash tool to reinstall the OS.
I haven't tried it out yet but is this the fix you have in mind @dmezh?
jkeats20 said:
I'm having the exact same issue with my D800. I was rooted and had run a couple of ROMs but returned to stock right after I started experiencing the reboots. Unfortunately, the return to unrooted stock - and upgrade to lollipop - didn't fix the random reboot issue.
I've noticed that when my phone shuts off I typically need to hold down the power button at least a min to get it back up and running. And when I get it back up and running the battery stats show a substantial drop in battery - between 5-10%. I took it to a local shop and they said it was a bad motherboard. I've read some threads about shorting some pins on the MB and then reinstalling pieces of the boot image piece by piece and then use the LG Flash tool to reinstall the OS.
I haven't tried it out yet but is this the fix you have in mind @dmezh?
Click to expand...
Click to collapse
What I had in mind is a multi-step solution that didn't involve opening the device - we can try it, and if it doesn't work then I guess you should try it. I've never actually heard of the pin-shorting, can you post links to the threads?
Anyways, this is roughly what we can try (I can give you all the files you need if you give the info from my first post):
1. Get to fastboot
2. Reflash laf, recovery, boot, modem, sbl1, and a bunch of other things
3. Reboot to download mode
4. Reinstall the kitkat TOT
5. Install custom recovery and wipe all partitions
6. Kitkat TOT again
7. Factory reset (yes, even though this is a fresh install)
8. Reflash laf, recovery, boot, modem, sbl1, and a bunch of other things AGAIN
I've tried these steps before on a friend's VS980 and they seemed to fix the problem. I know that this seems overly complex, but it has been documented in other threads. Provide the info, I'll get the files, and let's get started.
I have all of the D800 files I need to restore the KitKat partitions downloaded here:https://www.youtube.com/watch?v=_d5b_osUTug but am not sure how to get the phone into a mode that I can flash the .img files I have into the right locations. I follow what you are proposing I do - just not sure how to get there.
Current Baseband Version: M8974A-AAAANAZN-1.0.19.128
Current Bootstack / Modem - not sure
Root status in recovery: not rooted stock lollipop
Current ROM and Carrier: 5.0.2 AT&T
Current Recovery: Stock Recovery
Here's the link to the hardware shorting pins post: http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
jkeats20 said:
I have all of the D800 files I need to restore the KitKat partitions downloaded here:https://www.youtube.com/watch?v=_d5b_osUTug but am not sure how to get the phone into a mode that I can flash the .img files I have into the right locations. I follow what you are proposing I do - just not sure how to get there.
Current Baseband Version: M8974A-AAAANAZN-1.0.19.128
Current Bootstack / Modem - not sure
Root status in recovery: not rooted stock lollipop
Current ROM and Carrier: 5.0.2 AT&T
Current Recovery: Stock Recovery
Here's the link to the hardware shorting pins post: http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
Click to expand...
Click to collapse
The pin-shorting manually puts the device into a Qualcomm fallback mode, but this is not necessary if we can just get it to go to fastboot (the images can be flashed from there as well). The only time I've been in fastboot on the G2 was when I flashed a VS980 recovery on an LS980 with AutoRec. Fastboot is triggered if any of a set of five partitions are corrupted.... so we may need to corrupt a partition. I'll try this on one of my devices first before I instruct you to do it.
dmezh said:
The pin-shorting manually puts the device into a Qualcomm fallback mode, but this is not necessary if we can just get it to go to fastboot (the images can be flashed from there as well). The only time I've been in fastboot on the G2 was when I flashed a VS980 recovery on an LS980 with AutoRec. Fastboot is triggered if any of a set of five partitions are corrupted.... so we may need to corrupt a partition. I'll try this on one of my devices first before I instruct you to do it.
Click to expand...
Click to collapse
Did you have a chance to try this out? It sounds like a good way to get the phone into fastboot but am reluctant to try without knowing if it's going to work. Thanks for your suggestions so far - and no rush on getting back I have a working backup phone at the moment.
Related
So I recently purchased my AT&T Galaxy S4 with MDL baseband. I rooted and installed TWRP via motochopper. I then loaded Kangabean 4.2.2 and everything was great. Got notification for OTA update to 4.3 and decided might as well load Kangabean 4.3 as opposed to dealing with the OTA notification. I did so (after formatting internal SD and performing factory reset) and now my phone won't boot beyond the Galaxy S4 splash screen. I restored a nandroid backup of the original software and was able to boot the phone once, but couldn't load the custom rom again, nor can i load into the stock rom anymore either. Does it sound like my phone may have a hardware failure? Would attempting to restore through odin be the next logical step? I'm by no means an expert with these sort of things but my S2 has never given me any sort of grief when flashing various roms in the past. Any advice would be greatly appreciated. Thanks in advance!
Try a different kernel, also, pull the battery for 5 min, it will boot.
TheAxman said:
Try a different kernel, also, pull the battery for 5 min, it will boot.
Click to expand...
Click to collapse
Yeah I left the phone off with the battery removed all night - didn't want to boot this morning. I'm also noticing an oddity with TWRP - it's for some reason asking for a password on startup even though I've never set one. It also gives an error when attempting to wipe the phone or re-flash
id try odin
Don't Odin yet. If you can get into recovery see if you can flash a new recovery onto the phone. Try this http://forum.xda-developers.com/showthread.php?p=41746967
jd1639 said:
Don't Odin yet. If you can get into recovery see if you can flash a new recovery onto the phone. Try this http://forum.xda-developers.com/showthread.php?p=41746967
Click to expand...
Click to collapse
It will not let you past the password, been there, it will only do simulated flashes.
Odin is his only option.
So I managed to flash back to stock with odin. I was then able to re-root and re-install recovery. Something is still wrong here though. I was able to load kangabean 4.3, but when i installed the SIM card (kept it out to prevent OTA updates) the phone would no longer boot. I then re-flashed with odin, re-rooted, installed sim, THEN loaded the rom and it worked.... For a while. I had the phone plugged in to my laptop as i had recently transferred some ringtones to the internal SD. I powered down the phone. It seemed to shut the OS down but it then displayed a battery symbol with a rotating circular animation, as if it was trying to show that it was charging the battery. The phone froze in this state.
Another thing that I've noticed is that when this phone freezes, it gets warm. It also tends not to respond well until i've let it cool down. I'm now having difficulty booting the phone after re-flashing with odin. It loads to the white screen with AT&T logo and hangs (and gets warm). I plan to leave the phone alone with battery removed for the day and attempt to reboot or re-flash with odin later.
I find it odd that the rom that i flashed would stop working if i've flashed the rom with the sim removed from the phone, then introduced the sim to the phone after the flash is complete. Is this normal? I'm also unsure if my phone has faulty hardware, or maybe there's some sort of software glitch that's causing it to hang and overhead (like an infinite loop caused by faulty software).
I think if / when I can get it working with the stock rom again, I'll root it and run it for a while and see what it does. I never intended to run this phone with the stock rom as I prefer vanilla android.
I'm wondering if there's something wrong with the kernel. Perhaps I should re-download the ROM and re-install it. I'm not sure but I think the kernel is responsible for charging issues. Perhaps a bad kernel WOULD explain why the phone sometimes freezes at the "battery charging" logo? I'm somewhat at a loss as to what to do. I could try exchanging it through AT&T. If so, I hope they nave another one in their stock that has the MDL baseband as I know I'd be screwed with the current one...
Squidbert said:
So I managed to flash back to stock with odin. I was then able to re-root and re-install recovery. Something is still wrong here though. I was able to load kangabean 4.3, but when i installed the SIM card (kept it out to prevent OTA updates) the phone would no longer boot. I then re-flashed with odin, re-rooted, installed sim, THEN loaded the rom and it worked.... For a while. I had the phone plugged in to my laptop as i had recently transferred some ringtones to the internal SD. I powered down the phone. It seemed to shut the OS down but it then displayed a battery symbol with a rotating circular animation, as if it was trying to show that it was charging the battery. The phone froze in this state.
Another thing that I've noticed is that when this phone freezes, it gets warm. It also tends not to respond well until i've let it cool down. I'm now having difficulty booting the phone after re-flashing with odin. It loads to the white screen with AT&T logo and hangs (and gets warm). I plan to leave the phone alone with battery removed for the day and attempt to reboot or re-flash with odin later.
I find it odd that the rom that i flashed would stop working if i've flashed the rom with the sim removed from the phone, then introduced the sim to the phone after the flash is complete. Is this normal? I'm also unsure if my phone has faulty hardware, or maybe there's some sort of software glitch that's causing it to hang and overhead (like an infinite loop caused by faulty software).
I think if / when I can get it working with the stock rom again, I'll root it and run it for a while and see what it does. I never intended to run this phone with the stock rom as I prefer vanilla android.
I'm wondering if there's something wrong with the kernel. Perhaps I should re-download the ROM and re-install it. I'm not sure but I think the kernel is responsible for charging issues. Perhaps a bad kernel WOULD explain why the phone sometimes freezes at the "battery charging" logo? I'm somewhat at a loss as to what to do. I could try exchanging it through AT&T. If so, I hope they nave another one in their stock that has the MDL baseband as I know I'd be screwed with the current one...
Click to expand...
Click to collapse
TheAxman said:
Try a different kernel, also, pull the battery for 5 min, it will boot.
Click to expand...
Click to collapse
//
Squidbert said:
.
Another thing that I've noticed is that when this phone freezes, it gets warm. It also tends not to respond well until i've let it cool down. I'm now having difficulty booting the phone after re-flashing with odin. It loads to the white screen with AT&T logo and hangs (and gets warm). I plan to leave the phone alone with battery removed for the day and attempt to reboot or re-flash with odin later.
Click to expand...
Click to collapse
If you're on the stock AT&T rom and you're getting stuck on the AT&T boot logo try the following:
Power off your phone and hold down Volume Up, Center Home, and Power buttons together.
Once you see the Galaxy S4 splash - Keep holding down Volume Up and Center Home buttons but let go of Power button.
Choose the wipe datafactory reset. This will wipe your phone completely but it should boot after.
Hope that helps.
Well I've been toying around with this thing and much to my surprise, I have CM10 running stable w/o any issues booting! I think I would prefer to run Kangabean 2.05 (android 4.3) though. Assuming that the kernel could be a likely cause of the OS not booting, could someone recommend a suitable kernel for that rom? It appears to come packaged with the "KT" kernel...
Another thought i had was perhaps TWRP wasn't adding the loki feature to the roms that i was trying. I upgraded from 2.5x to 2.6. Hasn't seemed to have made a noticeable difference though.
Would the fact that CM10 runs absolutely flawlessly with no issues booting at all possibly help narrow down why the other roms that I'm flashing only load up the first time but fail at the "Galaxy S4" splash screen on subsequent reboots? Admittedly I'm a relative noob to roms and such but up until now i've been able to muddle my way through things and eventually figure them out. I'm not having the greatest luck with this one!
Squidbert said:
Well I've been toying around with this thing and much to my surprise, I have CM10 running stable w/o any issues booting! I think I would prefer to run Kangabean 2.05 (android 4.3) though. Assuming that the kernel could be a likely cause of the OS not booting, could someone recommend a suitable kernel for that rom? It appears to come packaged with the "KT" kernel...
Another thought i had was perhaps TWRP wasn't adding the loki feature to the roms that i was trying. I upgraded from 2.5x to 2.6. Hasn't seemed to have made a noticeable difference though.
Would the fact that CM10 runs absolutely flawlessly with no issues booting at all possibly help narrow down why the other roms that I'm flashing only load up the first time but fail at the "Galaxy S4" splash screen on subsequent reboots? Admittedly I'm a relative noob to roms and such but up until now i've been able to muddle my way through things and eventually figure them out. I'm not having the greatest luck with this one!
Click to expand...
Click to collapse
TWRP does not now and has never added LOKI to any ROM or Kernel. Only OUDHS CWM auto-LOKIs. You have to use A pre-LOKIed Kernel or flash the LOKI DokI script to LOKI anything with TWRP. You can do a search to find the LOKI DOKI script and how to use it.
fatah
hi my phone is galaxy s4 at&t i337 rooted but not installed recovery the phone was working good suddenly i deleted at&t software updater after that the phone rebooted it's self and then stuck in at&t boot logo won't bootup please help
TheAxman said:
Try a different kernel, also, pull the battery for 5 min, it will boot.
Click to expand...
Click to collapse
galaxy s4 i337 stuck on at&t bootAnimation
i tried everything but still same please help my phone is not booting up
fatahmusse said:
i tried everything but still same please help my phone is not booting up
Click to expand...
Click to collapse
Flash the stock firmware.
samsung galaxy s4 i337
thank you i flashed to mf3 everything is ok
fatahmusse said:
thank you i flashed to mf3 everything is ok
Click to expand...
Click to collapse
Glad to hear
What's currently happening is my phone will boot and work normally except it appears the radio is not working then after 60-120 seconds freeze for a second then reboot. Wifi does work but I just see an x for the cell network signal and if I take out the SIM I get no notification. Curiously if I'm using the camera it seems to delay the rebooting by a few minutes.
I've tried http://forum.xda-developers.com/showthread.php?t=2432476 LG G2 Stock Firmware (Go Back to Stock) to no success, I was able to flash, it removed TWRP but I get the same symptoms anyway.
I've tried flashing the Rogers modem and this did not make a difference.
When I noticed this problem was when I was installing/testing some xposed modules, although it seems strange that they could break the phone in this way.
I've run out of ideas and although my phone isn't bricked per say it's near useless if it's going to reboot every minute or two. The phone doesn't reboot if I leave it in download mode or TWRP so this makes me think there's some hope.
Assuming it's not against the rules I'll PayPal anyone who comes up with the fix $50 CAD because right now I'm hooped.
Did you download and try flashing the exposed disabler zip file?
Sent from my LG-D803 using XDA Premium 4 mobile app
Of course there is hope!
All you gotta do is just download this ROM...
http://forum.xda-developers.com/showthread.php?t=2451592
Download it with your PC, then connect your phone to the PC to transfer the file.
The TWRP and flash it and that should fix it all.
Good luck
Do you have a gmail widget on your lockscreen? (Was worth a shot since others have reported varying issues with gmail widgets on the lockscreen).
I lost my recovery when I tried to go back to stock, and I can't seem to install any apps. I'm trying "upgrade recovery" from the LG Mobile Support Tool to see if that works. Otherwise I guess I have to find out how to root and flash a recovery entirely over ADB
I was able to restore the stock recovery and factory reset but that still didn't resolve the issue. Can someone provide a /system/ partition dump of a d803? I'm assuming there's something broken in there but I don't think flashing a ROM will solve that since flashing stock didn't seem to.
mrsocksfox said:
I was able to restore the stock recovery and factory reset but that still didn't resolve the issue. Can someone provide a /system/ partition dump of a d803? I'm assuming there's something broken in there but I don't think flashing a ROM will solve that since flashing stock didn't seem to.
Click to expand...
Click to collapse
If flashing to stock didn't work then your phone may as well be defective...
crzykiller said:
If flashing to stock didn't work then your phone may as well be defective...
Click to expand...
Click to collapse
It's not a paperweight yet, I can adb. I rooted it through adb I'm just not sure what the xposed module broke. It has to be something that persists across flashing stock but I don't have anything to compare against.
EFS. Flash or push your backed up EFS.
Steamer86 said:
EFS. Flash or push your backed up EFS.
Click to expand...
Click to collapse
I don't have one. I made a backup in TWRP but ended up losing it when trying to fix things :silly:. I believe I can still see my IMEI if that's any sign of things not being completely ****ed.
Hi I have LG G2 D802 . My problem is that my phone hangs a lot . I did hard reset but problem didnt go. After hard reset i tried to install custom built rom but still same problem. Then I re installed lolipop 5.0.2 still the same problem .. now
i have downgraded to kitkat and again same problem .. Even now when it hangs It turn off completely like it got bricked or something but it work some time and again after some use it hang.. now i have hardreset my device and putted on standby mood but phone was working fine after some use phone hanged again . I dont understand what is the problem with my LG G2
I am having the exact same problem on stock 4.4.2 with my D803. I have random reboots every few minutes. I suspect it is a hardware issue since the problem persisted even after returning to stock using kdz. Unfortunately, I don't have an EFS backup.
I have tried multiple other ROMS (CM12.1, DU, Cloudy 3.2 and 3.3) and all are even less usable than stock (reboots while I am doing the initial setup).
Any suggestions? I don't know what else to try and am ready to buy a new phone now as this G2 is basically unusable... I'd greatly appreciate any help.
mrsocksfox said:
It's not a paperweight yet, I can adb. I rooted it through adb I'm just not sure what the xposed module broke. It has to be something that persists across flashing stock but I don't have anything to compare against.
Click to expand...
Click to collapse
If you have restored it to stock ....... and you still have the problem, u may have a short somewhere in the phone. The only thing that remains the same is the hardware .... u have changed the software
Long story short (I can go into more detail if needed):
Had a stock rooted rom with a zv8 radio/modem on sprint. I successfully flashed the Optimus 2.2 rom with the new ZVA (Sprint Spark) modem and everything was fine and dandy and working perfectly for a few hours. Then i was a dummy and restored apps from my previous roms using mybackup and one of those apps was the xposed installer with a few different modules.
Phone froze, rebooted and would no longer attatch to a network. No signal, just a red x. No radios work, not even wifi or bluetooth. If the screen goes blank the phone will freeze and bootcycle. Or if it is on for more then a minute, it will freeze and turn off and get stuck in a bootloop.
Recovery worked. I tried everything. Flashing other roms, with the appropriate radios of course, and restoring my backup with the appropriate radio. Nothing works, and ive had the same issue with each and every rom and radio.
I finally whipped out lgflashtool and returned to stock unrooted to no avail. Same issue, except now my touchscreen is not responsive, which means no adb to reroot and the pc doesn't recognize the phone while booted. Now im aware of a method using Ubuntu to get a custom recovery on these when all else fails, but is it worth my time if there is no fixing my issue?
Also, how much can you do with the lgflashtool? Can i flash different radios or root using it?
Worst case scenario i will take my phone to sprint and get a warranty replacement. The only issue with that is, while the rootchecker in download mode shows "unrooted" , the boot animation on the stock .tot image is an lg one, not the Sprint logo one and i feel like the service person would catch on. Any idea on how to change that as well?
Thanks in advance guys! Im kind of freaking out that im running out of options.
Bump
dantheman9703 said:
Long story short (I can go into more detail if needed):
Had a stock rooted rom with a zv8 radio/modem on sprint. I successfully flashed the Optimus 2.2 rom with the new ZVA (Sprint Spark) modem and everything was fine and dandy and working perfectly for a few hours. Then i was a dummy and restored apps from my previous roms using mybackup and one of those apps was the xposed installer with a few different modules.
Phone froze, rebooted and would no longer attatch to a network. No signal, just a red x. No radios work, not even wifi or bluetooth. If the screen goes blank the phone will freeze and bootcycle. Or if it is on for more then a minute, it will freeze and turn off and get stuck in a bootloop.
Recovery worked. I tried everything. Flashing other roms, with the appropriate radios of course, and restoring my backup with the appropriate radio. Nothing works, and ive had the same issue with each and every rom and radio.
I finally whipped out lgflashtool and returned to stock unrooted to no avail. Same issue, except now my touchscreen is not responsive, which means no adb to reroot and the pc doesn't recognize the phone while booted. Now im aware of a method using Ubuntu to get a custom recovery on these when all else fails, but is it worth my time if there is no fixing my issue?
Also, how much can you do with the lgflashtool? Can i flash different radios or root using it?
Worst case scenario i will take my phone to sprint and get a warranty replacement. The only issue with that is, while the rootchecker in download mode shows "unrooted" , the boot animation on the stock .tot image is an lg one, not the Sprint logo one and i feel like the service person would catch on. Any idea on how to change that as well?
Thanks in advance guys! Im kind of freaking out that im running out of options.
Click to expand...
Click to collapse
try to flash kdz via flash tools
gembo said:
try to flash kdz via flash tools
Click to expand...
Click to collapse
I've done this. But I found one from a new source and I'll try it again. Would I need to flash the radio again? Thank Thank you for the help.
So this issue has persisted throughout wiping data/factory resetting. I'm really not sure what this is.
Basically what happens is that my phone will gradually get slower and slower until it freezes and then reboots. However, after it reboots, it will go into a boot loop. What I will then need to do is basically wait it out by shutting it off. Then, I wait for an hour (maybe more) before I try turning it back on again, at which point it returns to normal.
Any idea? I thought it might be a memory leak? But how would that affect rebooting? I'd like to also mention that at one point my recovery somehow disappeared as well. I managed to re-flash TWRP using Flashify, but I haven't dared going back into the recovery, because last time when I had lost my recovery, I ended up thinking that I had to wipe my phone completely (because even Download Mode wasn't working correctly).
By the way, I'm running an AT&T LG G2 d800, on the "d80010q" firmware 4.2.2. I'm rooted, with Xposed modules running, as well as the camera mod flashed. No other modifications have been made except for buildprop and systctl (kernel) changes through android tuner.
Same issue
Hello,
I am having this exact same issue. Did you ever find a fix for this? I have been searching for hours. I have tried numerous things, flashing back to stock with lg flash tool, installing different roms, it happens on all roms.
Thanks
I restarted my S4 this evening and now it won't boot past the SAMSUNG logo. I have tried a variety of things to get it going but none have worked.
1) Soft boot
2) Pulled battery and let it sit awhile
3) Tried to boot into Safe Mode (stuck on the same spot with no indication of going into safe mode)
4) Wipe cache from CWM recovery mode
5) Reboot from CWM recovery mode
Everything is pretty well backed up but after looking at my sdcard it appears that my camera reverted to internal memory about a month ago so I am after any ideas to get those images.
My phone is rooted and running an old 4.2.2 stock Android OS with USB debugging enabled. I was wondering if by re-flashing the OS it might fix the boot issue and be able to recover the images. Or maybe even flash CM. Or maybe some other thing. I found something about adb but I don't want to do anything else yet until someone more savvy than me weighs in.
Unless it's a hardware issue, then flashing a ROM might work.
The other option is to try a reflow. Reflow means heating your phone up so that the solder becomes liquid and any cracks in the solder (which can cause a bad contact), or any piece that isn't seated right, will be remedied.
did u tried to flash stock firmware using odin?
Deleted
I got it going. I first spent a number of hours getting to know adb which was a dead end because I couldn't get it to see beyond the base directory. I then just flashed the stock rom and everything was there including things that shouldn't be like apps, contacts and texts. The phone is back exactly where it was before it boot locked without having to mess with a single thing. I am grateful but a bit confused.