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.
Related
I need some serious help ...
I rooted with Z4root, and it worked great, and EASY!!!!!
I downloaded and bought the RoM Manager from the Market because after weeks of reading, reading, and reading some more, I just couldn't bring myself to install a RoM myself. The only 2 RoM's that popped up for me was PlayfulGod & Cyanamogen 7.
I first chose Cyan... and it was great except the Market was gone, and a few other things didn't work all of a sudden. Then when I tried to change with RoM Manager it kept saying I needed to get the newer version. Long story short, I was finally able to switch over to PlayfulGod via RoM Manager. It's been a long few days, I don't remember what it was that made me want to go back to Cyan, but I figured I could just download a new Market and all would be fine. So, RoM Manager again ... download Cyan, install, backup. While it was backing up I went to sleep.
When I woke up this morning, my phone was in a looping bootmode! I get the movie thing that Cyan boots up with, then the android guy - then the movie again, android guy, movie android, over and over. I can't even get to the Volume Down, End, Power spot. When I try, I get the Huawei screen and that's all it'll do.
I was too scared to "flash" a RoM myself, and now I am completely lost. Please help me fix my phone ...
~Ky
txheart0711 said:
I need some serious help ...
I rooted with Z4root, and it worked great, and EASY!!!!!
I downloaded and bought the RoM Manager from the Market because after weeks of reading, reading, and reading some more, I just couldn't bring myself to install a RoM myself. The only 2 RoM's that popped up for me was PlayfulGod & Cyanamogen 7.
I first chose Cyan... and it was great except the Market was gone, and a few other things didn't work all of a sudden. Then when I tried to change with RoM Manager it kept saying I needed to get the newer version. Long story short, I was finally able to switch over to PlayfulGod via RoM Manager. It's been a long few days, I don't remember what it was that made me want to go back to Cyan, but I figured I could just download a new Market and all would be fine. So, RoM Manager again ... download Cyan, install, backup. While it was backing up I went to sleep.
When I woke up this morning, my phone was in a looping bootmode! I get the movie thing that Cyan boots up with, then the android guy - then the movie again, android guy, movie android, over and over. I can't even get to the Volume Down, End, Power spot. When I try, I get the Huawei screen and that's all it'll do.
I was too scared to "flash" a RoM myself, and now I am completely lost. Please help me fix my phone ...
~Ky
Click to expand...
Click to collapse
With any cyanogen mod you Have to flash google apps separate. That will solve for market problems. Since you have to flash GAPPS you might as well re download whichever cm7 check the md5 checksum and reflash that. You can find videos on youtube that give you a step by step of the flashing and backup process. Just search around the web.
Can somebody help me I love cyanogen mod and I'm trying to update my ascend to cm7.2 but it failed everytime I try any ideas please
Sent from my M860 using XDA App
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!
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:
I had some time available today for a change and so attempted to do a long overdue update to jelly bean. Catastrophe! I dont know really where to start trying to solve the problem though I have spent my entire day off (sic) (NOT SICK!) prior to an all night 12 hour slog at work...not happy...no phone and I'm on call...ooops So now you know what a bit of a prat I am perhaps someone out there in XDA land can forgive me and point me in the direction of help pages or suggestions to get me communicating again.....please...
I rooted and unlocked my phone a long time ago and have not been back to change things for ages so anything I knew back then isn't worth knowing. I've been trying to resolve a boot loop after trying to follow :
http://www.android.gs/update-htc-sensation-cm10-1-rc2-jelly-bean-4-2-2/
i followed these instructions carefully and the only issue I had with the files to install was that the CM10.1 file wasn't available so I went with 10.2
so the first question would be....is this file incompatible. I assumed it was just the next release with some improvements?
I have ClockworkMod Recovery installed and have tried endless times to get this thinkg to work but even dropping back to an earlier version of cyanogen mod 9 my phone loops shortly after loading the cyanogen screens....
Any pointers from you guys would be a great help. I'm sure you're going to want more information from me so I'll stop here and hope someone responds
all the best and thank you in antcipation
Hi,
As a general rule recoveries that work with cm9 do not work with cm 10.1.
Ensure that you have the proper recovery version and should you still have the issue, please ask here
All the best !!
Okay I've got this weird problem since updated to awesome recovery/kernel. Whenever there is CM/Omni involved, my phone starts acting weird. Okay, listen to this.
First of all, everything seems normal after clean install. Then I install some of urgent apps (total commander, whatsapp - that's all). After a day or two my phone starts to act weird - it's rebooting itself and bootloops. I turn it off and on again - boots to os, then after a few minutes another reboot into bootloop. Okay... I thought it was because I didn't have the ext4 partition. Formatted into ext4 from recovery, installed Omniroom from 2 sept. and suprisingly it went good for two days! I installed some more apps and used it regularly - but it happend again. Reboot, bootloop, manualy reboot, worked fine for a minute, another reboot into bootloop. I thought that my SD card was damaged. h2testw claimed that it was perfectly fine. Now I wanted to install some stock 2.3.5 into it... I couldn't even pass the HTC screen because it keept rebooting itself...
Tell me what can I do to make this piece of... functional again? I ordered new phone, but it will arrive within next 14 days at best, and I still need the functioning android phone. Any advice, help is appreciate: links to a flashable stock roms, links to a fucntioning omni/cm rooms, any help on how to install them... thanks in advance
mclpl said:
Okay I've got this weird problem since updated to awesome recovery/kernel. Whenever there is CM/Omni involved, my phone starts acting weird. Okay, listen to this.
First of all, everything seems normal after clean install. Then I install some of urgent apps (total commander, whatsapp - that's all). After a day or two my phone starts to act weird - it's rebooting itself and bootloops. I turn it off and on again - boots to os, then after a few minutes another reboot into bootloop. Okay... I thought it was because I didn't have the ext4 partition. Formatted into ext4 from recovery, installed Omniroom from 2 sept. and suprisingly it went good for two days! I installed some more apps and used it regularly - but it happend again. Reboot, bootloop, manualy reboot, worked fine for a minute, another reboot into bootloop. I thought that my SD card was damaged. h2testw claimed that it was perfectly fine. Now I wanted to install some stock 2.3.5 into it... I couldn't even pass the HTC screen because it keept rebooting itself...
Tell me what can I do to make this piece of... functional again? I ordered new phone, but it will arrive within next 14 days at best, and I still need the functioning android phone. Any advice, help is appreciate: links to a flashable stock roms, links to a fucntioning omni/cm rooms, any help on how to install them... thanks in advance
Click to expand...
Click to collapse
if you want to install older roms or stock you`ll need to fastboot an older recovery check this out http://forum.xda-developers.com/showthread.php?t=1415223 you only need to do PART 3 : Add a Recovery section
now you should be able to flash non-aw3som3 roms cm10 RC2 and below/ICS/Jellybean/Stock jaggyjags roms either way will get a functioning phone back for you, remember to wipe everything apart from sdcard once in recovery then install whichever rom