First thing...greetings! Yes, I am a n00b (loved the video, though) and have searched for quite a while to hopefully resolve the issue I am currently burdened with. A thousand pardons if there is already another thread like mine, but I just couldn't find anyone with the same issues I am having.
First off, I started with rooting my phone. No problems.
Got my hands on ClockworkMod's ROM Manager. Downloaded Cyanogenmod 9 to my PC, and any other necessary programs to get this flashing underway. Opened up ROM Manager and proceeded to boot in recovery. This is where I think the problem originated. I wiped all that I needed (or so I think). It's entirely possible that I may have missed something. Not sure. After wiping it clean, I then went on to install the zip of cyanogenmod. All went well. Then the reboot. It starts up and gets to the loading screen with the really cool animation. 5 minutes. 10 minutes. It's constantly loading. I head on to google and search some possible culprits and solutions. There were suggestions to go back into recovery mode, but the thing is, when I try to get to that menu, it doesn't seem to pop up and goes right back to attempting to boot.
So, all things said...is there any possible solution? Any help would be greatly appreciated. And again, if there were any threads with my specific issue, many many apologies!
Thanks again!
Related
How to Ask Questions!
If your messing with your phone, eventually you will have a problem you cant solve on your own. We have all been there, its just part of modding your phone. but if you give some time and a little patience, most of the time its easy to get fixed.
FIRST: SEARCH!!!This means try searching a thread if its too long, or searching the entire G2X Section of the forum. (and we can tell if you really searched or if you just say you did to get rid of the people yelling at you) If you see nothing that relates to you, or you have tried all of that, then you can make a post, BUT FIRST...
Stuff to Try Before Posting:So... your having a problem with your phone... well there are a few things you can do to help fix most issues:
Go into CWM and clear Cache
try this first, it really does help solve most issues from within a rom
Make a Nandroid Backup and clear data
just do this as a test, make a backup and clear data. check to see if the problem still exists, if it fixes it then its something you installed/did to the rom that caused the problem.
if not then...
Try flashing a new ROM
even if you don't like it, even if you can never go back to gingerbread after ICS just try it to see if it fixes your problem. If it does then you can decide if ICS is worth the issue your having.
Clear App data/Reinstall App
If you having an issue related to a specific app, try going into settings and clearing that app's cache and data. if the issue still exists try uninstalling it then reinstalling it after a reboot.
If none of these things helped you, then its time to make a post.
Things to Include in your post:If your having an issue, many of us are willing to help to get it resolved, but first, you need to give us some useful information.
A good checklist to include in your post is the following:
Current Rom
Current kernel
If you have done ANY undervolting or overclocking.
If you had this problem before (either on other ROM's or previously on your current ROM)
If you wiped Cache
If you wiped Data
If you tried installing another ROM
Any other things you already tried (BE SPECIFIC!)
the more you include in the first post the better, too much information is MUCH better than not enough.
If you think the issue is related to a specific ROM, try posting in that ROM's thread in the development section, but please don't spend too much time there. If nobody can find a simple fix, move your discussion to a new thread in the Q and A section, don't clog up the Developer's thread with a single issue.
Once again, the more information you give us the better, and if you don't post the above, someone will most likely ask you those questions, or tell you to do those things first (or they just might ignore the question).
If you see any typos, or think of anything i could add or improve on please let me know.
t mobile lg g2x reeboting issue
Hey guys i recently tried flashing a new kernal to my lg g2x in xda development forum installation procedure went well but at the very end when you have to reebot in recovery it never rebooted back properly just got a blank screen with a notification buttons flashing at buttom of screen....... i just rooted my device so i was still running my stock rom and kernal....... what should i do to get my phone back working please help???
p999dw six digit spc code
Sorry about my weak English
i almost searched entire forum and i only get spc must be 000000. But it's not works. I live in Turkey. At first i can send spc 000000 in QPST but after when i bought the unlock code from ebay, i can't access anymore. Does anyone have an idea?
Thanks
My screen not reading my finger
Im not sure if this is the place i had to ask my question. My cell used to read my finger all the time but now it only does when i turn it on, afther it sleeps n i press the top botten to used it it wont read my finger no more. If i turn it of by taking the battery out and on again it reads my finger until it locks then it dosent. right now i have EB on the phone i cleard cache, system, dalvikcache, format/data. Ive restore basic rom then back to EB but nothing work it only reads my finger till it sleeps then it wont read it no more
PLEASE, WHAT CAN I DO??...
Oskar20022 said:
Im not sure if this is the place i had to ask my question. My cell used to read my finger all the time but now it only does when i turn it on, afther it sleeps n i press the top botten to used it it wont read my finger no more. If i turn it of by taking the battery out and on again it reads my finger until it locks then it dosent. right now i have EB on the phone i cleard cache, system, dalvikcache, format/data. Ive restore basic rom then back to EB but nothing work it only reads my finger till it sleeps then it wont read it no more
PLEASE, WHAT CAN I DO??...
Click to expand...
Click to collapse
I have the same problem and I can't find any way to fix it I am going to post a new thread about the problem.
Hi all...
I was watching, reading and was excited about cm 14.1 for my LG g2 which was running on lollypop.
What a mess I created for myself. Will explain step by step. I I would be thankful if anyone can teach me get out with it and back to LG rom lollypop.
1. I rooted my phone with one click tool.
2. Then I installed Twrp through play store app.
3. Download cm 14.1 for lg g2. The as well as open gaps.
4. Next thing I did rebooted to twrp recovery and clean it after taking back up. But was not able to flash cm 14.1. Also loaded gapps7. 1.
5. After so many trials nothing happened I even updated twrp to 2.8
6. Then I found twrp 3.0 and tried to flash it.
7. Suddenly my phone came to a stage Fastboot.
8. My computer stopped detecting it.
9. Then I re plugged it into the USB of my computer.
10. I found the partitions are there. But no system is there.
11. Even I don't know to sideload it.
12. Lg flash tool is not able to flash it.
I request if someone know the way to flash it with lg roam. I L be thankful.
Can anyone email me steps to do to get out of it.
My email is [email protected]
Thanks
Regards
Harpreet Singh
Hs-india said:
Hi all...
I was watching, reading and was excited about cm 14.1 for my LG g2 which was running on lollypop.
What a mess I created for myself. Will explain step by step. I I would be thankful if anyone can teach me get out with it and back to LG rom lollypop.
1. I rooted my phone with one click tool.
2. Then I installed Twrp through play store app.
3. Download cm 14.1 for lg g2. The as well as open gaps.
4. Next thing I did rebooted to twrp recovery and clean it after taking back up. But was not able to flash cm 14.1. Also loaded gapps7. 1.
5. After so many trials nothing happened I even updated twrp to 2.8
6. Then I found twrp 3.0 and tried to flash it.
7. Suddenly my phone came to a stage Fastboot.
8. My computer stopped detecting it.
9. Then I re plugged it into the USB of my computer.
10. I found the partitions are there. But no system is there.
11. Even I don't know to sideload it.
12. Lg flash tool is not able to flash it.
I request if someone know the way to flash it with lg roam. I L be thankful.
Can anyone email me steps to do to get out of it.
My email is [email protected]
Thanks
Regards
Harpreet Singh
Click to expand...
Click to collapse
This isn't the LG G2 forum.
http://forum.xda-developers.com/lg-g2
i have a samsung captivate i897.
i bought it sim free and unlocked from the states but i'm in the UK.
i recieved it already rooted running cyanogen mod and miui and have had it for 8 months. its worked perfectly the whole time.
until the past month i'd say its been radomly forcing closs on nearly everything.
i havent installed any new software or roms or anything or even dl any new apps so i cant figure out what would be causing the problem.
i tried checking for updateds on the muiu and it runs android 2.3.7
i'm not a tech person at all so i spoke to one of the tech guys at my local phone shop and he said i should try a factory reset.
so i guess i'm asking a few questions here:
1) does anyone have any idea what might be up with my phone?
2) can someone elplain to me the easiest/safest way to fix it?
please bear it mind i am a total noob at this tech stuff. i'll try to understand and cooperate as much as i can with those so kind to help me, but i'd really appreciate if people would help/point me in the right direction instead of giving me a short blunt answer which assumes i know all this tech stuff then locking my thread.
If it's already rooted & running a custom ROM, then you probably already have a custom recovery installed (probably clockworkmod). 1st thing would be to boot into recovery & do a backup. Then, you can try flashing any ROMs you want / factory reset / whatever, and restore your backup if you don't like the results.
-- Sent from my TouchPad using Communities
how do i know if i have clockwork mod installed (i've never seen it before, but then again if its on the boot menu where i've not been before)
for booting into recovery i just long press the power button (at least it works like this on my phone) > reboot > recovery > ok
then what should happen after i press "ok" ?
also just to state (if it helps) the options i get for rebooting are: normal, hot boot, bootloader & recovery.
i dont really feel confident to be flashing roms (mainly because i dont really know how/which are stable etc) on the other hand i do need to fix it. guess i'd like to try the factory reset first though..... under the assumption its slightly easier.
i thought factory reset would restore the phone back to stock settings? but the guy in the phone shop said it wouldnt? (not sure how reliable he is ;] )
found this thread here which seems kinda similar
http://forum.xda-developers.com/showthread.php?t=1264177&page=3
have tried uninstalling some apps to see if it helps.
the thing is with the problem is seems to occur randomly. the phone will work like perfect again for a few days then boom starts forcing close yet again.
only time will tell.
Hello.
First off i will start with the fact that i've read most of topics proposed by Google and Xda forum search, so please don't treat me like an idiot.
From what I've noticed there's quite a few people with similar problem - after going back to stock ICS everything was fine for a week then boom, this morning i wake up and my TF101 is refusing to turn on. First off I've thought its just a fail and i will fix it easily but now I'm seriously scared. So far I've wiped device around 10 times, and so did i tried to install other system software (I've had couple zip files with other rooms stored on my SD, and Clockwork recovery works fine except for the fact that when i use "Super wipe" from android revolver it's getting stuck on clearing DATA).
Some detailed info :
After installing energy ICS device does not even go to loading screen, just keeps on boot loop.
After installing CM10 there's no boot animation change...
After installing any ROM and rebooting there's this installation bar... it progresses instantly.
Did anybody had similar problem which they got fixed by some magic method... or should i just throw my transformer into the bin? I'm clueless now, hope you can help me out.
Regards Nekyo.
Edit : 2h later , Fixed it through the NVFlash... thanks for all support.
nekyo said:
Edit : 2h later , Fixed it through the NVFlash... thanks for all support.
Click to expand...
Click to collapse
You wait 2 hours and then complain there was no support?
If you run into a problem you can't fix on your own, you're not going to make many friends expecting people to jump on your issue within 2 hours.
This is XDA, basically a DIY forum, if you want support here, expect a few days delay for an answer that helps.
Hi! I realise this if my first post I'd like to tread lightly; but I'm about 4 days into solving my issues and I just want to finish it...
I've had my Nexus i9020a (bought from Koodo) since ~May 2012. I upgraded to ICS sometime in the summer and sometime in the last few weeks it has started rebooting. I hadn't been installing new apps, etc. I'm not sure what the cause is. I 'Factory Reset' today in an attempt to resolve the issue, thinking it may be a program gone AWOL; but it has rebooted a few times since. I *just* looked through rebooting FAQ on this site and have edited the first few features listed there. I'm not sure if it has worked yet, but I'll get back to you on that. For the record, the only programs I have installed now are Swiftkey 3, Handcent and Beats (DDR simulator, updated in November).
In the meantime, before I found the solutions here, I decided to take another shot at unlocking the bootloader and try installing... probably CyanogenMod.
Specs: Windows 7 64 bit with Nexus S I9020a (Koodo) running 4.0.4 (4.1.1/2 OTA haven't come through, despite dozens of attempts at clearing the GSF cache, etc)
So I've been using the Nexus S: Full Update Guide found at:
hxxp://wiki.cyanogenmod.org/wiki/Nexus_S:_Full_Update_Guide
(It won't let me post the link)
I've followed the guide for installing the Android SDK, gone to CMD and typed 'adb devices' and had it show up. Theoretically, the SDK should be running fine.
Next, I turned on the USB debug mode. Then I booted up the bootloader, plugged the NS into the PC... and despite not having issue when the it's turned on (driver installed properly) windows says drivers have not been found for the device. Thus, when I type fastboot devices, it comes up with nothing.
I've been, and will continue perusing forums for this, but so far I haven't seen anyone with this specific problem.
Edit: I have also gone to the directory with fastboot/adb and used cmd to reboot into the bootloader, only to have windows 'ding ding ding' an unrecognised device.
2nd Edit.
I've gotten a stage further! I'll keep the thread open because I may come across something and it's nice to write my issues down. Seems my head can wrap around the problem a bit better. Anyway, I installed PDAnet and BAM, it works. Onto getting CWM installed! Thanks for the, uh, help!
3rd Edit.
CyanogenMod 10.0 stable is booting for the first time!! It's taking a while... but I appear to be on the home stretch! Also, my phone didn't reboot for a few hours before I installed CM. So if I don't end up somehow bricking it... and I mean, this first boot is taking a heck of a long time... The animation sets me at least a bit at ease... maybe 4.0.4 will work out...
Edit 4
I forgot to clear the app and cache data before flashing the ROM to the phone and thus the issue... after a VERY tension filled moment of pulling the battery during first boot... I rebooted, cleared said data and reflashed the ROM. After a boot, I realised I forgot the GAPPS zip and fixed that. Now I'm running CM10 Stable!! I'm stoked that after months of putting it off cuz last time I did it I didn't get anywhere after many days, but now it's done!! Thanks again for such an awesome site!
Thanks for sharing your experience instead of just saying "Mods please delete this i solved my own problem" :good:
Ok first, I did a lot of research into the topic and spent more than a few months in thinking it over and seeing if I wanted to attempt this. In a day long research fest, I finally decided to just try rooting and installing my daily-driver Nexus 7 2013 Wi-Fi with CyanogenMod. I chose a method that wasn't too daunting, using the Nexus Root Tools to push the CM rom and finally into working... I used RootJunkie on YouTube, "How to Flash a rom with the Nexus Root Tool Kit plus make a Backup with one click" as a refrence, watchign and rewatching the video and all he referenced over and over.
I loaded the zips into the "Flash Zips" section (It loaded the GApps zip in first and then the CM image). It seemed to install without a hitch except the GApps weren't there. Figuring that it installed the GApps first and then wiped them, I redid the flash with the CM first and the GApps second. Now I'm stuck in the Cyanogenmod loading screen. Problem is, since it's hit the point where it installed everything and hasn't let me into the device, I haven't been able to enable USB debugging. Now the computer isn't able to recognize the device at all and I cannot push just the CM image to fix it nor can I restore factory since the computer doesn't recognize it.
I've attempted to boot into recovery mode, which just results in the android laying on its back with a red ! in a triangle over it. I'm sorry if this makes no sense but I'm slightly panicked because I can't afford to have this thing professionally fixed nor replace it at the moment and I use this tablet daily. Is there something I'm missing? I'm going to lay down for now and try to calm myself, letting the thing sit at the loading screen, hoping that it'll let me in after a while. What options do I have, I'm sorry if this is the wrong place, the wrong crowd... I've just browsed quietly and used XDA as my source for information for everything from rootig my first device to this and it seems I've overstepped my abilities in this.
Problem solved
I stepped away from my computer and tablet for an hour or two to calm down from a panic I was in and found that it let me into the bootloader finally where I flashed the stock image and then restarted the process.
I discovered my problem in trying to use the 'stock' level of GApps from opengapps when the Cyanogenmod wiki pointed directly for the 'nano' version. Sorting out a silly wizard crash later and my tablet is happy, healthy and working much better than the stock at the moment aside some setup I need to do.
Thread closed as OP solved his issue