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 !!
Related
My phone was working perfectly with an older version of the evil hero rom so 2 days ago I decided to update to the newest version which is v2xx or w/e and ever since then I have not been able to either go past the green mytouch boot up screen or If it does boot I cant login into my google account if I skip that step I can browse the web fine over 3g and wifi but cant login into the account...I have tried many different memory cards I have unrooted and re-rooted my phone like a million times now...if someone can just tell me whats going on...I flashed the engineering spl too .2005...I would post in general but it seems as if that section does not get as many hits as does the android development.
First of all.
If you were having several issues PRIOR to trying that laundry list of steps to go about solving the problem...YOU CONTINUED TO GET IN OVER YOUR HEAD! That's admirable that you made an (unsuccessful) attempt to go about fixing said issue on your own; but not worth it.
You were stuck on the SPLASH SCREEN - not locked in bootloop. Typically, if you didn't WIPE before an upgrade, that splash screen should remain for roughly 5-10 minutes depending on the range of changes made in the upgraded version of the ROM. Also, if you follow the developers thread on ROM features, you might want to re-read or properly describe exactly what you did, saw and tried to do ---> IN THAT THREAD!
My suggestion: Assuming that you backed up your ORIGINAL NANDROID from the stock "Cupcake" version of the OS...restore that backup, then start all over from the basics.
Reignzone said:
If you were having several issues PRIOR to trying that laundry list of steps to go about solving the problem...YOU CONTINUED TO GET IN OVER YOUR HEAD! That's admirable that you made an (unsuccessful) attempt to go about fixing said issue on your own; but not worth it.
You were stuck on the SPLASH SCREEN - not locked in bootloop. Typically, if you didn't WIPE before an upgrade, that splash screen should remain for roughly 5-10 minutes depending on the range of changes made in the upgraded version of the ROM. Also, if you follow the developers thread on ROM features, you might want to re-read or properly describe exactly what you did, saw and tried to do ---> IN THAT THREAD!
My suggestion: Assuming that you backed up your ORIGINAL NANDROID from the stock "Cupcake" version of the OS...restore that backup, then start all over from the basics.
Click to expand...
Click to collapse
Yo I did all of that im using the nandroid backup right now and I said I unrooted my phone and started from scratch and am still having the same issue and I always wipe before a new flash...its just frustrating that i cant login into the google account and the rom works fine other than that
also i never said that I bricked the phone or something the recovery is working and all...I have done all the basics I have the partitions and what not...the only reason Im posting here is to see if anyone know if certain mytouch's made after a day are having problems with root I saw it in some thread some where but wasnt able to find it I think it was mytouch's made after July 26th?
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.
I hope I am not wasting anyones time by posting something that may be and I hope is a simple fix, but I have a problem with my Verizon Xoom, a 602 (without the 4g upgrade- don't even have verizon service) that I can't figure out- and it's not for lack of searching. I have been rooting my devices and running custom Roms since my HTC Touch, (a big thank you to all of you here at xda for all the knowledge and instruction I have been able to leach) but I am very much still a noob with only the vaguest since of how Linux, android or the devices themselves actually work- and that is especially true of my xoom with all its post release changes in storage and whatnot since I bought mine, so please don't flame me to hard if this is just my ignorance- I promise you I'm not just being lazy, I just can't figure this one out. I have been running EOS for a while now without a hitch, and recently installed 150 when it became available. everything was fine until a couple of days ago when it started freezing on unlock which just took turning the screen off and back on to fix, but every app started crashing, some periodically and some such as android.process.acore, browser, and google play that won't open at all. I use Team Win's recovery and tried a wipe and reinstall, but same thing. When I try to fix permissions I get a failure with the message "E: Unable to chown '/data/app/com.google.android.youtube-2.apk' 1000 1000". Also when I try to wipe internal storage I noticed everything was still there even though my recovery was saying I had a successful wipe. I switched to clockworkmod recovery and tried to use eraseData file in the folder to wipe the old way but that didn't seem to work either (which I'm not even sure I did right but figured I better get some advice first anyway), and when I tried to flash EOS 3 stable it won't get past the EOS boot animation at all. If anybody out there knows whats up and has the time to point me in the right direction it would greatly appreciated... Thanks
Wowzers! When all else fails ... unroot / re-root. That will wipe everything.
EDIT: 12/23/2012 3:19AM.. Doing a little research I figured out what the issue was. Used Brian Gove's Guide
[How To] Reset your phone in order to return to Verizon(Updated 12/11/2012)
From Step 5 Onwords and everything works great.
.. I am still stumped on exactly what happen. I am almost positive it was because of the new file structure..
Just Proves that with a little patience and smarts anyone can use the resourced and tools here to solve their own android problems without bothering anyone haha.
Thank you all for your articles and Merry Xmas / Happy Holidays to Everyone!!
now.. I gotta unlock my boot loader and start all over..
Soft Brick.....
I was looking around and I cant seem to find a post that really solves my problem.
I have a Verizon S3 that I rooted and flashed to CyanogenMod Nightly build and everything was working great.
I used Rom Manager Premium and it updated me to update to CMW 6023. I went ahead and updated.
I saw that there was an update for my Daily As well 12/22/12 so I went ahead and used Rom Manager to download it and install it for me like It did with my last 16 Roms. That Rom had some strange things going on so I flashed to an older rom 12/20/12 and that rom was buggy as well.
Finally I decided that I should just stop with the Daily's and use the stable. When I loaded the Stable things started to still act strange. Mostly the Keyboard would not work and keep crashing. I decided then to just reload my original backup from Verizon.
Before I went in to recovery i took a look at my files and backed everything up. However then I noticed something that was not there before, a folder /0 with most of my main files inside.
I went into CWM v6.0.2.3. and tried to do a restore to my original nandroid backup from verizon but it looks like it failed.
It Says "Error While Restoring System" and kicked me back to CWM
Now when I reboot all I see is the White "Samsung Galaxy s3"
Did I Screw the pooch on this? Kinda nervous haha.
I am Posiive its a Soft Brik and hoping there is a way to fix it.
I can however get to Download mode. If anyone knows a great guide to help me reflash with Odin that would be fantastic.
thanks guys, been a long time reader and this is the first problem I have really had.
I apologize if this has already been over in a post.
Just a quick step breakdown would be great. I am really hoping that I didnt brick my phone.
Thanks for the help and Merry Christmas / Happy Holidays to everyone.
So a couple of months ago, i rooted my phone (Gs3 Sgh-T999). And last month i finally decided to download a ROM. After doing so it was going great until my phone would reboot and get stuck on the reboot screen. So i would end up having to factory data reset and loosing all of my apps and stuff. After a while, i couldnt take it anymore. So with research i thought i just needed to update my firmware. So i did. And for about 2-3 weeks. Everything went fine. Then it started once agian. So i would boot into safe mode and delete the app i recently installed. One i started do that, I had no reboot issues. And i stopped downloading apps in general. And it worked... Until today. It rebooted and got stuck. I lost my cool and got furious. So i told myself, tommorow, im going to download a new rom. But i thought occured and i wondered what if it just does it on the other rom. So what i need to know, is, is it the rom or my phone and certain apps in general making it reboot? The rom im using is AOKP Jelly Bean Rom. 4.1.2 My firmware is T999UVDMD5. If there is any suggestions or help you can give me, please do so, idk how much more i can take. Thank you.
hi there
i think there might be a firmware glitch so I request you to restore the whole phone and try to use the cyanogen mod <I THINK IT MIGHT WORK ON YOUR PHONE>
< NEVER TAKE THE UNSTABLE OR NIGHTLY >
KIBS2173 said:
hi there
i think there might be a firmware glitch so I request you to restore the whole phone and try to use the cyanogen mod <I THINK IT MIGHT WORK ON YOUR PHONE>
< NEVER TAKE THE UNSTABLE OR NIGHTLY >
Click to expand...
Click to collapse
What do you mean by use cyanogen mod. I'm still learning but I am familiar with who they are. But what you want me to download, is it firmware or a ROM?